Someone please give me hope.
I've got this phone yesterday and it keeps turning itself off when locked. If my phone doesn't receive a "wake up signal" like a notificationn or isn't in charge it will turn off in around 5 minutes (measured with a clock). This is not a sudden shutdown or crash ,you can see the logo on the screen.
Neither safe boot nor factory reset solved the problem.
Returning it and buying it again at the same price is impossible now so i'm hoping for a fix before the return window ends.
Can Xiaomi fix my (and probably others) phone in less than a month or is better to throw the towel now and go for a full refund?
Oh.. Had a few unexpected shutdowns Yesterday.. and one today.. but it's Not reproduceable.
Have you tried to enable AOD? Maybe this is a workaround....
Yeah, even with AOD permanently on after around 5min the phone shuts off. I've also tried running the clock app in chrono mode in the background with no results.
Rightnow i'm trying to reinstall miui 12.0.2 cause i don't understand if this is an hardware problem or a software one.
Also we don't know how widespread this problem is, a lot of people are happy with their F£ but it's impossible not to notice a problem this serious
Just ordered the phone, will come in a week, what version of MIUI does it come with, Global stable or Global beta?
Bro try unlocking bootloader and installing xiaomi.eu
justboryata said:
Just ordered the phone, will come in a week, what version of MIUI does it come with, Global stable or Global beta?
Click to expand...
Click to collapse
Global stable
ApexPrime said:
Bro try unlocking bootloader and installing xiaomi.eu
Click to expand...
Click to collapse
i need my warranty to return the phone if the problem isn't solved and this is my second day using android so i don't have the confidence to do it
GranoTurc00 said:
i need my warranty to return the phone if the problem isn't solved and this is my second day using android so i don't have the confidence to do it
Click to expand...
Click to collapse
Are you using dual apps?
GranoTurc00 said:
Global stable
Click to expand...
Click to collapse
Xiaomi.EU on 12.6 is released with the gesture fixes as a fastboot ROM. You can give it a try.
ApexPrime said:
Are you using dual apps?
Click to expand...
Click to collapse
never tried
GranoTurc00 said:
Someone please give me hope.
I've got this phone yesterday and it keeps turning itself off when locked. If my phone doesn't receive a "wake up signal" like a notificationn or isn't in charge it will turn off in around 5 minutes (measured with a clock). This is not a sudden shutdown or crash ,you can see the logo on the screen.
Neither safe boot nor factory reset solved the problem.
Returning it and buying it again at the same price is impossible now so i'm hoping for a fix before the return window ends.
Can Xiaomi fix my (and probably others) phone in less than a month or is better to throw the towel now and go for a full refund?
Click to expand...
Click to collapse
I have the same problem. Got it yesterday, went to sleep and in the morning the phone was rebooted/crashed.
Had to put in Sim pin and Device pin again just like after a reboot.
I hope this gets fixed soon.
Same problem here, I have the f3 for ten days with MIUI Global 12.0.4 (Italian Country), several reboots (four) almost always at night under charge, but once even during the day in front of my eyes, another time I have found the smartphone completely turned off, at this point I don't know whether to ask for a refund because I don't know if it's a SW or HW problem
There are several users who are reporting this problem
Hmmm i think the update from yesterday solved the problem for me.
I didn´t have a reboot this night.
Edit: Had another reboot this night, so update didn´t help.
UPDATE: i've updated the phone to 12.0.4 and the problem still remains. i will ship it back to Amazon in a few days. Also the problem got even worse ( before update): it's the second time i've found the phone with 0 charge after one of those shutdowns. The "when isn't in charge" part of the OP is also wrong, in the last days the phone switched of even while charging
Had a reboot this night on 12.0.4
Before putting it definetly inside the box after factory reset i've tried to start the phone again and then lock the screen at the welcome page. After 10 mins i've found it turned off
Same problem for me. I wonder, does it also happen on xiaomi.eu rom? Hope its not a hardware fault.
Lownita said:
Same problem for me. I wonder, does it also happen on xiaomi.eu rom? Hope its not a hardware fault.
Click to expand...
Click to collapse
Pretty sure it´s just a software Problem. During my search for a solution i found out, the Poco x3 had the same problem.
xxxrekt said:
Pretty sure it´s just a software Problem. During my search for a solution i found out, the Poco x3 had the same problem.
Click to expand...
Click to collapse
That can't be, if it was a software problem all of us on MIUI will have the same experience. I think mine is a hardware problem cause is worse than anyone here. Also a lot of people do not have any problems so maybe is a QC issue on some component like the power management chip
I dont have any shutdowns or reboots at night, but i use an old charger with 800mA.
My Shutdowns come If i disable AOD.
Related
Anyone else having this problem?
The phone won't turn back on from what I think is locked because the screen is black, but none of the buttons do anything, I have to re-insert the battery and the phone will boot up with the power button. This happens almost every day.
Sounds like a problem with the digitiser/screen, and a candidate for a warranty return ?
Have you tried to switch it off (the screen with short press, not the power) and then on again with the power button? Sometimes it happens on my z too but its just a sw bug. Switch off and on helps here.
-- sent from htc z using xda app
I am able to lock and unlock with the power button normally.
tbalden said:
Have you tried to switch it off (the screen with short press, not the power) and then on again with the power button? Sometimes it happens on my z too but its just a sw bug. Switch off and on helps here.
-- sent from htc z using xda app
Click to expand...
Click to collapse
akira112 said:
Anyone else having this problem?
The phone won't turn back on from what I think is locked because the screen is black, but none of the buttons do anything, I have to re-insert the battery and the phone will boot up with the power button. This happens almost every day.
Click to expand...
Click to collapse
Could be a problem with the contacts on the battery -- perhaps the contact is loose, so when you bump the phone just right it loses power and shuts down.
I had this once last week. I left it sitting on the workbench in the garage for about an hour while I was out there and it became unresponsive to all buttons/keypresses.
A battery pull and it fired right up again.
It was -10C in the garage and the bench is metal. I chalked it up to getting too cold.
It hasn't done it again since I keep it in my back pocket (front pocket has claimed a few digitizers/LCDs in the past!).
akira112 said:
Anyone else having this problem?
The phone won't turn back on from what I think is locked because the screen is black, but none of the buttons do anything, I have to re-insert the battery and the phone will boot up with the power button. This happens almost every day.
Click to expand...
Click to collapse
This is definitely not an individual case as I saw so many DesireZ or G2 users in HK or China raised the same issues on the gfan forum (one of the China HTC forum).
My DesireZ is a genuine one with stock ROM. It happened 2-3 times already of what we called the "sleep dead" in China here.
I locked the phone then after a while when I tried to turn it on, all buttons became dead. Finally I have to pull out and insert the battery again to make the phone alive.
Some of the gfan forum members also encountered the same situation. Some of their phone are Euro version and some Asia Pac version but the cases are the same that means this problem are not only for a specific version. Some say it is becoz of temperature but I really don't think so. I am sure this is a bug......
Bring back to HTC is not a solution as this "sleep dead" phenomenon don't appear every minute. Mine has happened 3 times and I bought this DZ only about 2 weeks.
happened 2-3 times to me too, each time it was sitting in my pocket.
it's summer in Australia so i doubt its anything to do with being too cold.
hasn't happened for about a week now, so i kind of ignored the problem.
That is definitely not good news.
Mind is still stock from Bell, unlocked for use on Rogers.
I guess I may have to find a replacement phone soon.
manleyfu said:
This is definitely not an individual case as I saw so many DesireZ or G2 users in HK or China raised the same issues on the gfan forum (one of the China HTC forum).
My DesireZ is a genuine one with stock ROM. It happened 2-3 times already of what we called the "sleep dead" in China here.
I locked the phone then after a while when I tried to turn it on, all buttons became dead. Finally I have to pull out and insert the battery again to make the phone alive.
Some of the gfan forum members also encountered the same situation. Some of their phone are Euro version and some Asia Pac version but the cases are the same that means this problem are not only for a specific version. Some say it is becoz of temperature but I really don't think so. I am sure this is a bug......
Bring back to HTC is not a solution as this "sleep dead" phenomenon don't appear every minute. Mine has happened 3 times and I bought this DZ only about 2 weeks.
Click to expand...
Click to collapse
I encountered the same problem, so do my friends. Google maps causes the problem in 3 different phones.
Sent from my Desire Z
Anyone found a solution to this? Is it a s/w bug or a hardware issue? Thanks.
As far as I can tell, it's a hardware issue. Happened to me four times randomly before I took it in and exchanged at Bell. My new phone and the phone my friend got (at the same time as my first), has zero issues.
At the time, it didn't matter if it was cold, warm, fully charged, plugged-in, etc. It would do it randomly once every 1-4 days. It didn't even matter after I did factory reset (so software would not be an issue).
I have no idea what causes it but if you're getting the sleep-dead issue, I'd really recommend exchanging it if you can. Better to be safe than wait and find it's not an issue you can fix yourself.
I have a Bell stock Desire Z that has done this twice. First time it happened was when I tried wake it up in the morning after sleeping all night. The second time it was at a Christmas party. Just finished taking a picture. Went to take another shot, bang it was dead. Both times, pulled the battery and it came back to life.
Bought mine from Bell as well less than 2 weeks ago. Do they give any trouble to exchange it? Do they actually need me to factory reset it before returning/exchanging it?
sekhar_777 said:
Bought mine from Bell as well less than 2 weeks ago. Do they give any trouble to exchange it? Do they actually need me to factory reset it before returning/exchanging it?
Click to expand...
Click to collapse
I didn't have any troubles. I did a wipe and factory reset, then wipe again for security though. As long as you're only doing EXCHANGE (not refund), you have 30 days.
I must report that this issue happened on mine as well.
In JuicePlotter, the period where the unresponsiveness happened, juice plotter recorded no power.
(Either that or juice plotter only refreshes the graph when you open the app).
Happened twice within the first 48 hours of getting this phone. In day 3 now.
I have the same problem. It happend to me twice (in two weeks).
I would like to know if this is a software issue.
I still have the stock unmodified rom but am planning to install custom roms.
If this appears to be a hardware error, I should return my phone and get a new one. If it's a software thing, there will be a fix eventually, or I can just install a custom rom and be done with it...
anyone any idea?
Is there anyone with a custom rom who has the same problem?
Like I've said, I doubt it's a software issue (especially when it happens AFTER factory reset). But again, why take the chance? Better to be safe than sorry than be out $600.
happend to me today for the first time too... fully loaded, not pretty cold and stock rom on european version. it seems to simply being switched off. kind of sucks, as i'm having hardcase around which needs to removed everytime first.
mine too
it happened to me too. just after i started using maps and locations. i have it for a month now and this issue just started to surface the past 3 days...ohwell..hope we get a fix soon..or at least a "how to stop this issue" sometime real soon....:|
I was regularly using my G4, it was on cyanogenmod 13 nightlys for a good while now and i updated it every week or so. (haven't updated it in at least 10 days this time but it shouldn't be an issue) Suddenly the device turned itself off and went into a bootloop. I found a couple of weird things with this bootloop.
1. it wont boot into the device ever. it just shows the LG logo for a few seconds, goes black for a second then repeat.
2. I cant enter recovery mode, i used the button combination and go to the "factory reset" screen, selected 'yes' twice and i should have been sent to TWRP, which i have installed. But instead it just took a while on the yes/no screen and then blacked out, and rebooted back into the loop.
3. Sometimes it goes a bit further in the loop, and gets a little into the boot animation i have. I found that letting it run a longer time gets me a higher chance to see my little boot animation.
ive heard there was a hardware issue with LG G4's that were bought back in September of 2015 but i bought mine in June last year so i don't think that's the issue.
i didn't backup my phone for a long time so i'd love to get my files back! (otherwise I'm getting a new phone in a couple of days but i still need it until then)
Any and all help will be greatly appreciated! thanks!
What is your phone's S/N?
Sent from my LG-H815 using Tapatalk
I have the exact same problem, my phone died like this yesterday. The colder the phone is the longer it runs without rebooting so that might be a hint for you, although i have never seen it boot up completely. Maybe you can put it in the freezer or something like that. I was lucky because i just switched to cm13 and make backups of all my data the day before.
joelalmeidaptg said:
What is your phone's S/N?
Click to expand...
Click to collapse
no idea. I know it hits some within a specific range but i did check the back of the phone where the battery is and it says there H815 0506 twice H815 0430 once and H815 0508 and H815 0501 both once. Does this mean anything? how can i check the S/N if its in a loop?
helgenet said:
I have the exact same problem, my phone died like this yesterday. The colder the phone is the longer it runs without rebooting so that might be a hint for you, although i have never seen it boot up completely. Maybe you can put it in the freezer or something like that. I was lucky because i just switched to cm13 and make backups of all my data the day before.
Click to expand...
Click to collapse
heard about that, i didnt try freezer because that sounds kinda stupid and i dont feel safe doing it but i put it in front of my A/C and it cooled down but i dont think it made any special change.
SynderBlack said:
no idea. I know it hits some within a specific range but i did check the back of the phone where the battery is and it says there H815 0506 twice H815 0430 once and H815 0508 and H815 0501 both once. Does this mean anything? how can i check the S/N if its in a loop?
I saw my S/N in the box the phone came in, right above the IMEI (mine is 602).
Click to expand...
Click to collapse
I'm sorry but it seems you both have THE bootloop problem not a weird bootloop.. It does affect many more than "bought in September" devices. Actually more of the June devices..
Sorry.
joelalmeidaptg said:
I saw my S/N in the box the phone came in, right above the IMEI (mine is 602).
Click to expand...
Click to collapse
EPa said:
I'm sorry but it seems you both have THE bootloop problem not a weird bootloop.. It does affect many more than "bought in September" devices. Actually more of the June devices..
Sorry.
Click to expand...
Click to collapse
just checked the box, mines 506.
Damn that sucks! Any way confirmed to fix this issue? I dont think warranty will fix a boot loader unlocked phone.
SynderBlack said:
just checked the box, mines 506.
Damn that sucks! Any way confirmed to fix this issue? I dont think warranty will fix a boot loader unlocked phone.
Click to expand...
Click to collapse
People in the US and some European countries (ie Germany) didn't have a problem getting it fixed under warranty despite unlocked bootloader, root or even custom roms (because it's a known hardware issue unrelated to software).
Others did.
Try, you got nothing lose..
As for a fix, there is a process that involves disabling CPU cores, has worked for some. Check http://forum.xda-developers.com/showthread.php?p=67149552
EPa said:
People in the US and some European countries (ie Germany) didn't have a problem getting it fixed under warranty despite unlocked bootloader, root or even custom roms (because it's a known hardware issue unrelated to software).
Others did.
Try, you got nothing lose..
As for a fix, there is a process that involves disabling CPU cores, has worked for some. Check http://forum.xda-developers.com/showthread.php?p=67149552
Click to expand...
Click to collapse
I bought the phone as an international phone from a phone store. I dont have an LG center here and if i try to ask the store to fix it under warrently i'll probably get turned down because the bootloader is unlocked (you can clearly see that in the LG screen)
I will try talking to them but with ~20 days of warranty remaining i doubt my success chances are high
I brought mine from a phone store unlocked too (Carphone Warehouse in the UK) and it also had an unlocked bootloader running Cm13.
When it started suffering the bootloop problem they repaired it no questions asked. Worth a go.
Mine done that but wouldn't turn on after I took battery out I didn't try asking on here but no luck so I took it to insurance and I ended up with the g5 as they had no g4 repaired and ready to come back to me in 24 hours lol. Carphone warehouse ? big thanks to them now to wait for g5 to get some good stuff ... ?
Sent from my LG-H850 using Tapatalk
Hi,
I've got my op3 for 4 months.
The problem is the device shutdowns independently at least 3 times in one week. It dosnt have any noticeable trigger, time on the day or a specific event.
I couldn't found any helpful info online.
Does anyone got the same phenomena?
Tx.
AraleInterK said:
Hi,
I've got my op3 for 4 months.
The problem is the device shutdowns independently at least 3 times in one week. It dosnt have any noticeable trigger, time on the day or a specific event.
I couldn't found any helpful info online.
Does anyone got the same phenomena?
Tx.
Click to expand...
Click to collapse
Is it rooted ? What rom? Does it heat up? A bit more details would help to know if its software or hardware
v.konvict said:
Is it rooted ? What rom? Does it heat up? A bit more details would help to know if its software or hardware
Click to expand...
Click to collapse
No, its all original with stock firmware. The device dosnt have any heat issues. Btw its also without root. Completely stock.
AraleInterK said:
No, its all original with stock firmware. The device dosnt have any heat issues. Btw its also without root. Completely stock.
Click to expand...
Click to collapse
Well i sometimes find myself pressing the power button by mistake causing a restart. But if you are sure you not doing that then i suggest you flash stock 3.2.8 again if that doesnt help you might have to open a support ticket
v.konvict said:
Well i sometimes find myself pressing the power button by mistake causing a restart. But if you are sure you not doing that then i suggest you flash stock 3.2.8 again if that doesnt help you might have to open a support ticket
Click to expand...
Click to collapse
Tx, I will try it.
i also aware this.. but it actually happen when i use spigen ultra hybrid case.. button are easily press.. so when i sit and the phone is in the pocket, it tend to restart..
Any success?
I had the same problem like you.
The motherboard is probably faulty, get it replaced from the OnePlus support!
Hello everyone! Hope you're doing ok!
As the title says, I updated to MIUI 12.5.3 Global stable rom (from OTA) and then I started having issues with the fingerprint sensor, only working half of the time. Then, suddenly, it stopped working completely. I've read online that it has happened to many people on many devices. The only answer I can find is to flash xiaomi.eu rom on my phone. Does anybody knows if installing xiaomi.eu would help? Does anybody have had this same issue before?
My phone is 3 months old, I always use a case and screen protector, and I haven't dropped it strong. (It fell off of my hands a couple times, 2 or 3, but without any major impact, had a very safe landing haha so I doubt the fingerprint sensor broke.)
I'm trying to find any kind of solution to this problem, as I always use the fingerprint sensor
Thanks in advance!
redbeans92 said:
Hello everyone! Hope you're doing ok!
As the title says, I updated to MIUI 12.5.3 Global stable rom (from OTA) and then I started having issues with the fingerprint sensor, only working half of the time. Then, suddenly, it stopped working completely. I've read online that it has happened to many people on many devices. The only answer I can find is to flash xiaomi.eu rom on my phone. Does anybody knows if installing xiaomi.eu would help? Does anybody have had this same issue before?
My phone is 3 months old, I always use a case and screen protector, and I haven't dropped it strong. (It fell off of my hands a couple times, 2 or 3, but without any major impact, had a very safe landing haha so I doubt the fingerprint sensor broke.)
I'm trying to find any kind of solution to this problem, as I always use the fingerprint sensor
Thanks in advance!
Click to expand...
Click to collapse
I'm having the same problem, any fix?
Same problem, any fix???
I have bad news. I managed to install xiaomu.eu, I'm on MIUI 12.5.5 and sadly, the issue was not fixed. I thought that installing the most recent version of xiaomi.eu would solve the problem, but no...
I don't know if going back to MIUI 12.0 would solve it, as the problem appeared when I upgraded it to 12.5.3, but I won't try it for now because i'm kinda tired of re-setting my phone and apps lol.
If someone downgrades to MIUI 12.0, global or eu rom, and it solves the problem, please let us know!
it won't be solved by changing ROMs as it's an hardware issue. Go to the service centre and get it replaced
HIRA123 said:
it won't be solved by changing ROMs as it's an hardware issue. Go to the service centre and get it replaced
Click to expand...
Click to collapse
The thing is I'm not so sure its a hardware issue. The problem started when I updated to MIUI 12.5.3 and the fingerprint stopped working, and more people have the same issue after updating too.
But as changing the rom didnt work, I can assume maybe, in my case, is a hardware issue... And I doubt it tho, because I haven't dropped my phone as hard for it to broke.. unless the sensor is so weak it breaks with a little drop
I had the same issue, unlocked bootloader, flashed crdroid, and fingerprint stopped working, thought it was due to custom rom, flashed OG MIUI Firmware locked bootloader and fingerprint still wasn't working, claimed my phones warranty and the service center told me that they'd have to replace the fingerprint and the problem maybe with the motherboard as well.
So it is an hardware problem? Seriously?
darkangel123 said:
So it is an hardware problem? Seriously?
Click to expand...
Click to collapse
Yes, it's a hardware issue. Last week I brought my mi 11 lite to the service centre and they replaced the fingerprint module and it's working again
So why the fingerprint with the previous software still active?
Happened to me 2 days ago, phone was just 3 months old.
It's hardware issue,sensor on mine Mi 11 lite 5g died two months after I bought it.Flashing older roms won't help...In my country there is no way to raplace it so I've got other phone...
Im not use fingerprint use faceid
2 days ago my display start to flickering (constant small horizontal line flickering) all over the screen.
What i have done is
1. wipe cache partition
2. restart
3. safe mode
but no luck.
during startup boot, recovery mode or optimising app no flickering seen.
Never had this before (Android 11). after 3 week updated to Android 12. this issue happen.
is it probably Firmware issue? currently im on G988BXXSCEUL9 XME (Malaysia)
Try using different fixed frequency display rates and brightness levels.
blackhawk said:
Try using different fixed frequency display rates and brightness levels.
Click to expand...
Click to collapse
Tried turn off adaptive brightness
Change from 60hz to 120hz and back to 60hz
Turn off/on night light
Eyeshield off
Screen mode to natural
Resolution to 1080 and 720
No luck.
Guess try reflashing it. If you can downgrade do so. Maybe a mobo failure, if a downgrade solves the issue... leave it there.
If under warranty, send it in.
blackhawk said:
Guess try reflashing it. If you can downgrade do so. Maybe a mobo failure, if a downgrade solves the issue... leave it there.
If under warranty, send it in.
Click to expand...
Click to collapse
its not underwarranty anymore. tried factory reset also no luck.
does reflashing remove my esim carrirer data?
apecx92 said:
its not underwarranty anymore. tried factory reset also no luck.
does reflashing remove my esim carrirer data?
Click to expand...
Click to collapse
Not sure as I haven't had to do it. I rarely mess with the firmware if it's running good even to do updates. This N10+ is still running on Pie, the current load will be 2yo in June.
Alright thanks for the reply. I will just wait for next update hopefully it will fix. Otherwise i'll just buy new phone
apecx92 said:
Alright thanks for the reply. I will just wait for next update hopefully it will fix. Otherwise i'll just buy new phone
Click to expand...
Click to collapse
Not written in stone. Maybe a loose connector or it got corrupted doing the upgrade. A Samsung Experience center at a Best Buy might be able to find the issue and if firmware, reflash it.
blackhawk said:
Not written in stone. Maybe a loose connector or it got corrupted doing the upgrade. A Samsung Experience center at a Best Buy might be able to find the issue and if firmware, reflash it.
Click to expand...
Click to collapse
I downgraded back to Android 11 Nov 2021 build using Odin (my esim data doesnt get erase).
no more flickering screen after 2 hour of usage, i will keep monitor the display and update here again.
Hopefully its the Android 12 Firmware issue not my hardware.
apecx92 said:
I downgraded back to Android 11 Nov 2021 build using Odin (my esim data doesnt get erase).
no more flickering screen after 2 hour of usage, i will keep monitor the display and update here again.
Hopefully its the Android 12 Firmware issue not my hardware.
Click to expand...
Click to collapse
Could be either or a combination of both. Best shot is to not update/upgrade it again. It can run for many years like that.
Android isn't PC and anything from Pie up is reasonably secure as is.
With 11 you have more than enough security in place unless you do something stupid... which is how malware usually gets loaded.
Hi
I'm having the same issue in my s20ultra exynos G988b/DS and it's nearly 2 years old and in clean condition. got this problem last week and it wasn't under the warranty anymore service center said it was hardware and need to changethe display which cost ~$290 which i refused since the device is not even scratched and pretty sure must be a software thing.
Came across your post today, can you verify that problem has gone after the downgrade?
Thanks in advance.