Related
Hey.
My diamond is acting strangely. For example, right know it's on but later on today or during the night it will turn off. And each morning I have to take out the battery out for about one minute and then press the power on button to get it to start up. If I don't take the battery out and I press the power on button it doesn't start-up. It just remains off. Sometimes it just gets stuck at the start-up O2 screen. But after a few tries it starts up normally and works.
I don't want to have to do this each morning, like I've been doing for the last several days.. Has this ever happened to anyone else? Anyone know how to fix this?
Thanks.
no but I've been having a similar problem lately, my diamond seems to shut itself off almost right after WM boots. I figured it might be a battery problem because it seemed to happen only when it was running off the battery or right after I disconnected it from the charger so I threw on nuePowerCPL to check battery levels, disabled the backlight power management and it's been up and running for 2 hours straight ... when I exit neuPowerCPL I get a voice command error that says voice command had a problem starting, please re-run the application and the phone freezes. Totally stumped about the powering off though. It may have something to do with the power management, I think it seemed to happen most when the screen tried to shut itself off, not always during that time though. I've reflashed telus(my provider) shipped rom a few times and tried a few other roms, reformatted my internal storage, hard reset etc. Any help would be appreciated if it saves me a few bucks on a battery.
quick bump, i'm completely stumped here. I booted into the latest android image from MrPippy and the phone doesn't restart when it's unplugged like in winmo without the battery monitor running(in winmo my phone will stay on till the battery is completely dead, showing good power levels, only if the battery meter is running, otherwise it restarts within a few minutes regardless of if I'm touching it or not.).
So it works normally with Android?
Then it's seems to be a problem with Windows.. Have you tried flashing another ROM?
Goodluck.
Also, an update on my situation. Thankfully it appears to be working normally now. At least if during the night I turn it off and take out the battery. There hasn't been any unexpected shutdowns since I left the battery out on Sunday night. Tonight I'm going to leave it on, to see if leaving the battery out all night actually helps, or it just is suddenly working properly.
iknighty said:
So it works normally with Android?
Then it's seems to be a problem with Windows.. Have you tried flashing another ROM?
Goodluck.
Also, an update on my situation. Thankfully it appears to be working normally now. At least if during the night I turn it off and take out the battery. There hasn't been any unexpected shutdowns since I left the battery out on Sunday night. Tonight I'm going to leave it on, to see if leaving the battery out all night actually helps, or it just is suddenly working properly.
Click to expand...
Click to collapse
Yeah, I've tried running a few different stock roms, a few off ppcgeeks/everythingdiamond etc, re-flashed spl once or twice, repartitioned/formatted sd card. Even tried leaving my battery out overnight. Was thinking in a frost-free freezer, in a bag of rice tonight ...
):
And how would that help? lol
iknighty said:
):
And how would that help? lol
Click to expand...
Click to collapse
If there's any moisture in the battery the rice will pull it out and the cold helps arrange the polarity in the battery ... You never used to put dead batteries in the freezer to bring them back to life when you were a kid?
Well, no. I've never heard about that before. >.<
iknighty said:
Well, no. I've never heard about that before. >.<
Click to expand...
Click to collapse
Didn't work anyways. I just read another thread about a hard reset solving this but ... I've gone as far as completely repartitioning my internal storage + hard resets and that hasn't solved it. When I throw a multimeter on my battery the voltage is constant/consistent. At a total loss. As far as I can tell it seems like a blackhole in my battery between 0%-60%. Seems that once the battery drains itself to 60%, it's more like it's drained itself to 0%. When I plug the phone back in after it shuts itself off the battery is always reading 0% NOW, when I started troubleshooting this crap a few weeks ago it would power off any time (battery @ 94%) and I would power it back on to see windows reporting the same battery levels as when it shut off.
Update: I did a format w/mtty a day and a half ago and my phone hasn't restarted since (besides me restarting it, read ahead). The phone seems to be working fine for the most part but it seems the battery readings are never updated, it will sit w/an icon that says 94% in the taskbar all day, when I restart it it jumps down to 59% and stays there all day until another restart. Seems the only time I'm getting a reading from the battery is on first boot. Doesn't restart now though!
Good.
Unfortunately for my Diamond had a blank black screen when I turned the screen on this morning. ): After a couple of soft resets and after flashing another ROM it began working correctly. I'll see if it does the same tomorrow. :/
iknighty said:
Good.
Unfortunately for my Diamond had a blank black screen when I turned the screen on this morning. ): After a couple of soft resets and after flashing another ROM it began working correctly. I'll see if it does the same tomorrow. :/
Click to expand...
Click to collapse
Which ROM had the problems? Which is the new one?
I have the same problems with EnergyROM (September 20 release). My current guess is WM6.5 not working properly with power controller of Diamond.
Could be. :/ The first time it gave me problems I had a WM 6.5 rom, and this time I had also flashed a WM 6.5 rom.. When it re-began to give me problems it had BOGYSOFTS V6 ROM, I don't know about the first time. Now that you point it out all the times it has given me problems I had a WM 6.5 rom, but maybe it's just coincidence..
Now it's not even turning on. If I press the Power On button and leave in it's pocket after a while it becomes somewhat hot... I don't know what's up. :S
This randomly started happening to me about 4 months ago. I was out at some clubs and whenever i checked my phone it was off! I thought it was a battery issue at first as thats what it seemed like.
I think I just hit the phone on the soft part of my leg pretty hard a few times. I havn't had any issues since.
hey everyone my sister has a milestone and she is having trouble with the phone battery. she says that she fully changes the phone and then at any point, the phone shows the sign that the battery is discharged and then reboots... then the battery shows the charge again, I tried moving from stock to cyanogen which took the problem away for some days but today it happened again. what can it be help!
hmm. i dunno. anyone?
the weird thing is that she just got it back from warranty... the screen was not working
Sounds like a battery problem. I once had my phone show 1% battery-level for like 7 hours (!) before it shut down. Some other time it would show 100% even though it just had been charged for minutes (starting at 5%). I fixed both issues by recalibrating the battery (search the forum, there's lots of info, most OR even have a script for that). I also leave the phone connected to the charger a couple of hours longer even after it says it's fully charged.
But if the phone actually reboots even though the battery has been fully charged, it really sounds like a hardware problem.
try a new battery
Before buying new batteries, just try calibration.
For me, the mentioned case of shutting down with a so-called empty battery was happening only with a stock 2.1.
Since then this issue never occurred again. So a faulty battery is not necessarily the first answer.
I got my Nexus 7 at I/O this year and I've been happily using it for nearly a month now. I don't know if my device differs in any way from one you can get form google play other than the white back.
Last night I was plugged into my wall charger at around 14% battery and playing SongPop with my girlfriend when my screen just shut off. It was like when you hold the power button on a laptop and BOOM, everything is black. It wouldn't turn back on so I unplugged it and plugged it back in. Got a charging screen so I let it set for a bit.
I came back maybe 15 minutes later and I was at 9% battery, which was odd given I plugged into the wall at 14%. I played with the phone for maybe 30s after boot and it happened again, I saw some weird artifacts on the black screen as it quickly shut off and the speakers played an awful crackly screeching noise. Plugged it in again, came back a bit later, still at 9% and played with the device again, same issue only after a little more time.
I'm currently at work with my N7 plugged into my Galaxy Tab 10.1 charger and charging it from 0 to 16% currently. The device is on but I haven't been touching it (and I don't plan to until it's at 100%).
Has anyone else had this issue?
I cant tell if it's some way I'm touching the device that's causing it to shut down hard, some issue with the battery or charging that is causing a rapid battery drop or even a short in the way I'm holding it when it's plugged into the charger?
I don't really want to deal with ASUS warranty returns already, though I have been unable to find anyone else with the same issue through google, so I turn to you for advice and similar stories.
Mine did the same thing the second day I had it. Now it won't boot. I'm waiting for Google to send me a new one.
Sent from my ADR6400L using Tapatalk 2
Mine did something similar last night. It was at about 6% battery charge and all of a sudden the screen just went black. I went and plugged it in, but it wouldn't power on completely (the screen was on but there was nothing there). I started seeing really thin, small green lines running down the screen. I turned it off and on a couple of times, and finally it booted up. I left it plugged in for awhile, and I just took it out at work to use a bit and everything seems perfectly fine. I wonder if there are some firmware issues with the power management or something. I was all set to put in a return with Google, but it appears to be okay. I'll keep a close eye on it for the next couple of days (I've only had it for a week).
TrevSo said:
Mine did something similar last night. It was at about 6% battery charge and all of a sudden the screen just went black. I went and plugged it in, but it wouldn't power on completely (the screen was on but there was nothing there). I started seeing really thin, small green lines running down the screen. I turned it off and on a couple of times, and finally it booted up. I left it plugged in for awhile, and I just took it out at work to use a bit and everything seems perfectly fine. I wonder if there are some firmware issues with the power management or something. I was all set to put in a return with Google, but it appears to be okay. I'll keep a close eye on it for the next couple of days (I've only had it for a week).
Click to expand...
Click to collapse
After leaving mine off and charging at work to 100% it seems to be working fine. I used it all last night with no issues. I haven't tried wiggling around the usb cable yet in the port to see if that caused any issues.
Firmware issues sounds about right, some sort of low battery safety feature or something? Who knows. I'll update this thread if I continue to experience problems. I'm already past my ability to return to Google so I'm in no rush to warranty to Asus and lose a development tablet.
Recently updated from CM9 to jcsullin's CM11 (11-20140409). Most everything seems to be ok aside from an unusual battery issue, and I don't know what it's coming from. I've attached a screenshot with some battery stats to help out, but I can describe what was going on in this particular instance.
I've had my touchpad sitting on the touchstone nearly 100% of this time (only time it was not was when I picked it up and immediately returned it). At some point, loaded up and was playing Breach & Clear for a while. Finally stopped playing, and upon exiting, battery was reported at 1%. Now, I get that some things can drain the battery even while on a charger, but we're talking a span of maybe 60-90 minutes. At this point, I picked the pad up and the battery immediately went up to 100%, and I dropped it back onto the touchstone.
This is the second time I've had this happen. Yesterday, it actually shut itself off due to low battery when I picked it up. I turned it right back on, and it was reporting 100% (recovery also reports 100%). This morning, I reflashed the A6 firmware in case that was the issue, but it does not seem to have had any impact.
Really could use some advice here. I suspect the battery is more or less staying charged while on the touchstone, and that this is something related to bad reporting or (worst case) a defective tablet.
Thanks for any help.
Just a quick update. Shutting off the touchpad before leaving work, during the shutdown process, I saw the battery % drop from 100 to 0. As I was getting out the touchpad at work and turning it on, I got the battery-with-question mark symbol. Placed it on the touchstone and it booted itself. I decided to take it to recovery, and pulled it off the touchstone. Now, as I watch, the battery is changing % wildly. 100%, 29%, 0%, 67%, back to 100%, 0% again...
Really don't know what's going on. Did not have this happen on CM9. Could really use some help.
Edit: I just threw on a random game while off the touchstone to see what happened. Everything seemed normal, battery ran down to 93%. Exited the game, turned off the screen, and two seconds later it was shutting itself off with 0% battery. Immediately turned it back on, and it shows 93% again.
Did you do a clean install? Does the issue persist after reflashing?
Fresh install, used tptools to wipe and repartition the tablet, no WebOS, CM11 only. Reflashing A6 didn't help.
Still unresolved, possible more problematic.
I rotated my tablet from landscape to portrait and back (while on the touchstone) and it decided to shut itself off.
If anyone knows of/has similar issues (fixable or note), I'd really like to hear about it. Will be disappointed if it's dead, but it's better than spinning my wheels on it for something I can't resolve. If I have to buy a new tablet, I'd like to get it over with.
Edit:
Been a bit since I posted this, but I let the tablet sit for a bit. The battery stats are pretty crazy. Note that I've left it on the touchstone this entire time. I don't get why it's doing what it's doing at all. See newly attached screenshot.
there are 2 possibilities
1. your battery is ****ed, hardware issue, you cant fix unless you replace the battery
2. software issue, but from what you described, seems like you installed properly, so i would suggest to boot into webos (u gonna have to reinstall it), and use it for a few days to see if you get the same problem
- if you do get the same problem, then it's 100% ur battery is ****ed
- if no, then ur cm11 is messed up, try another rom
Ah well. Was hoping I might be able to fix it without any wipes.
I would think if the ROM itself was the issue, others with jcsullins' CM11 would have problems as well. Looks like that's not the case at this point. Perhaps I'll just retired the tablet and get a laptop.
Thanks for the input.
Hi, did you get anywhere with this?
I've got occasional battery percentage glitches on Jcsullins CM11 that I didn't get with the previous WebOS/CM9 setup. See attachment.
Sadly I don't have the time or motivation to launch a huge investigation by flashing ROMs, etc... Looking like I'll just restore WebOS and sell.
At this point, I can't get the thing to boot. I've had it on a charger for a month or two now. I've got the blinking home button. It booted once, but I wasn't in a position to hook it up to a computer and try to wipe it. I've not really put any energy into fixing it since.
I plan on getting it back on the touchstone at some point, and setting it next to my PC. If I ever get it to boot, I'm going to try to get webos back on it first thing, and go from there.
Thanks for the reply. I'm questioning the amount of time I'm spending tinkering with this 3.5 year old device when new tablets are so cheap.
Touchpads are still making a reasonable amount on eBay so sadly I think it's time to just restore webOS and move on. Shame because it runs 4.4 pretty well, at least as good as my Galaxy S3.
There a multiple cases where Z3 Compact suddenly off, and then cannot be boot at all (with any mean available). It randomly can be boot, in my case i charged it a long time (approximately one night), then i saw the LED lights lit hence the successful boot. But 5 minutes later, poof, it die again and cannot be boot. I plugged back to the charger, no LED light or respond whatsoever.
The second time i able to boot it, i reflash the stock rom using the PC Companion repair section. But the problem persist, which hint me that this is maybe a hardware problem. I found in the sony forum that the motherboard or the battery could be fail, OR the battery was too low to lit the LED light during charging (which seem illogical for my case which the phone dead with 100% battery).
In the end i sent it to the service center and the phone not currently held up in a ward for god know how long. The friendly assistant at the service center suggested the board or the battery were failed since the phone didn't respond with charging and reset charging.
Any comment from you guys about the possibility of board and battery failure will be appreciated
There a thread in the sony forum,
https:// talk.sonymobile.com/ t5 / Xperia-Z3-Compact/ Sudden-Death-of-Sony-xperia-Z3-Compact/ td-p/877345/page/5
and based on the thread there is a lot of case happen in Malaysia. So for future owner, watch out!
well, this is a similar case [i suppose] http://forum.xda-developers.com/z3-compact/help/bricked-z3c-help-t2952415
Well my Z3C used to be softbricked like you. Meaniez had post my thread about it right above.
The reason for this was the unrespond battery. In my case, I charged it for about 3->4hrs, started at 17%. Then it suddenly softbricked, plugged it to PC, the logo Xperia appeared, but it still remained the same. I took it to the store, their technicians found out that the battery wasn't gone at all, it was hibernate. So they charged it with high-voltage electric for hours, then it came back to life, just like we do the electric shock to save people.
I think my case will help you with a solution to safe your phone.
leonjun said:
Well my Z3C used to be softbricked like you. Meaniez had post my thread about it right above.
The reason for this was the unrespond battery. In my case, I charged it for about 3->4hrs, started at 17%. Then it suddenly softbricked, plugged it to PC, the logo Xperia appeared, but it still remained the same. I took it to the store, their technicians found out that the battery wasn't gone at all, it was hibernate. So they charged it with high-voltage electric for hours, then it came back to life, just like we do the electric shock to save people.
I think my case will help you with a solution to safe your phone.
Click to expand...
Click to collapse
Well, in your case, the phone responded when connected to PC. Mine didn't respond at all. Thanks though for your information.
You meant the logo Xperia didn't appear on the phone when you plugged it ?
fzl.abdulaziz said:
There a multiple cases where Z3 Compact suddenly off, and then cannot be boot at all (with any mean available). It randomly can be boot, in my case i charged it a long time (approximately one night), then i saw the LED lights lit hence the successful boot. But 5 minutes later, poof, it die again and cannot be boot. I plugged back to the charger, no LED light or respond whatsoever.
The second time i able to boot it, i reflash the stock rom using the PC Companion repair section. But the problem persist, which hint me that this is maybe a hardware problem. I found in the sony forum that the motherboard or the battery could be fail, OR the battery was too low to lit the LED light during charging (which seem illogical for my case which the phone dead with 100% battery).
In the end i sent it to the service center and the phone not currently held up in a ward for god know how long. The friendly assistant at the service center suggested the board or the battery were failed since the phone didn't respond with charging and reset charging.
Any comment from you guys about the possibility of board and battery failure will be appreciated
There a thread in the sony forum,
https:// talk.sonymobile.com/ t5 / Xperia-Z3-Compact/ Sudden-Death-of-Sony-xperia-Z3-Compact/ td-p/877345/page/5
and based on the thread there is a lot of case happen in Malaysia. So for future owner, watch out!
Click to expand...
Click to collapse
I am French, exact same thing happened to me last night (didnt boot, plugged it, pressed power/vol+, booted with red light blinking and when on lockscreen restarted automatically and did the same thing again in a loop, then stopped responding at all. Plugged it for the night, green light this morning. Unplugged, didnt boot. Waited, plugged it again, this time it booted up, and it's still working fine. Did a factory reset and erased my data in case I have to send it to repair. It's such a shame, I love this little phone.
I think I'm done. Sick with having to go to the centre, sick with their crappy excuses and most importantly sick with all the 'bad batch' problems - Glass cracked, Flap covers, and worst of all, sudden death? Gosh that's crazy. Btw I am from Malaysia and my phone last night have just officially been infected with the sudden death problem for no reason. I am pretty confident that even if they swap my phone with a new one, that would also be from the bad batch.
But again, this is just me. I hope yours would be much better because overall the phone is actually quite good given the size. Cheers
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
bilboa1 said:
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
Click to expand...
Click to collapse
I know I'm a bit late to the party, but a colleague of mine just contacted me about the same issue - phone rebooted and remains dead.
I have not yet had a chance to look into the phone itself, but according to him the internal storage would be full up to a few MB, which would explain the issue based on your investigation.
Will look into it further...
Dude,
I feel your pain, read what happened to me : http://forum.xda-developers.com/showthread.php?t=3037336
The phone went back in warranty, I just had to pay the postal service, nothing else.
They didn't told me what was the problem, but I think they replaced the motherboard.
Sent from my D5803 using XDA Free mobile app
FYI: Here's the report I received from them.
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
This just happened to me. For my exp, we have this problem when we charge with the magnetic cable. Correct me if I am wrong.
So happy to see this topic, hoping that there is the fix guide in this, however ...
can anybody helps me ?
laufersteppenwolf said:
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
Click to expand...
Click to collapse
Hi,
please do inform us when u find any solution cause i'm facing similar issue after using it for 6-7 months
shardul.phatak said:
Hi,
please do inform us when u find any solution cause i'm facing similar issue after using it for 6-7 months
Click to expand...
Click to collapse
Have you tried upgrading to 5.1.1 (23.4.A.0.546)? I had the same problem, where my z3c would only last an hour or so until the next sudden death and I'd have to wait a few days before being able to turn it on again (and will die after another hour).
Since I upgraded, it has only happened a couple times, and even then I could immediately turn it back on. While it's not a complete solution for me, at least my phone is usable now.
laufersteppenwolf said:
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
Click to expand...
Click to collapse
Well, This sudden death phenomenon happened to me as well this weekend, without any prior warning, since the phone is just 5 weeks old. I tried every possible fix suggested on the web, no response at all.
Now the phone has been shipped to a service centre in Athens, Greece, 350 km from where I live. Ought to have an update on phone;s status in approx. 10 days I was told. I keep my fingers crossed... From what I've read searching this matter during these past days, it seems more like a hardware issue (i.e. defective motherboard). If that's true, and since this phenomenon tends to grow steadily like an epidemic all around the globe (first SE Asia, now Europe) than it is a disgrace for SONY not to organize a recall...
Same issue here. Started few times and then hard brick. No flash mode, no fast boot, no charging... The girl from Sony support, after I've told her that i have an issue reported by many user on their support forums told me not to believe everything I see on the internet . I've been a Sony fan for many years but this denial of a manufacturing fault will make me reconsider...
This has been happening to me regularly now. The only way to get it to boot is to leave it on a charger for an hour or two. After an hour it will say it's charging again. Once it shows that it's charging, you can power it on. Pretty annoying, especially because when this happens to me, the battery will usually be over 90% full.
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
bilboa1 said:
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
Click to expand...
Click to collapse
My internal and external storage are both only half full and the sudden death bug continues to happen. Not sure it's related to storage. I've noticed that it only happens to me when the phone is sleeping with the screen off. I know sony did a lot of work to get the phone to use very little power when idle. Maybe it's related to the phone not being able to wake up? Does anyone know if this happens with non-stock ROMS as well?
penske said:
This has been happening to me regularly now. The only way to get it to boot is to leave it on a charger for an hour or two. After an hour it will say it's charging again. Once it shows that it's charging, you can power it on. Pretty annoying, especially because when this happens to me, the battery will usually be over 90% full.
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
My internal and external storage are both only half full and the sudden death bug continues to happen. Not sure it's related to storage. I've noticed that it only happens to me when the phone is sleeping with the screen off. I know sony did a lot of work to get the phone to use very little power when idle. Maybe it's related to the phone not being able to wake up? Does anyone know if this happens with non-stock ROMS as well?
Click to expand...
Click to collapse
Started happening to me a couple of weeks ago. Currently on SlimRom 4.4 and have been using this ROM for about a year now.
I was actually about to reflash a stock ROM until I saw this thread and now I don't know. Might have to call Sony.