Related
how is that possible. i used firefox and message app, then it suddenly rebooted, after starting up again i lost 30% (!) of akku.
litening 6.1 kh3, nimphetamine 2.1.3
thanks for every help
Transmitted from the galaxy "S2" using a Lite'ning
Got the same problem in the past two weeks for a few times.
The device rebooted, then accu percentage goes down 10 % or more, then the percentage goes UP! sometimes to the percentage it was before the reboot.
The device rebooted when doing nothing special, sometimes it reboots if it laid on the desk.
What to do now?
Kernel: speedmod t40 (but happened also with ninphetamine 2.0.5)
Rom: Lite'ning 6.1
don't know if it happened with stock rom, flashed litening two times to test is. but doesn't work.
I'll replace mine next week.
Any other suggestions?
@OP, try switching to a different kernel and see if that solve the problem. I was previously using ninphetamine and have the same problem as you. Worst is it auto-reboot too! After switching to stock kernel, everything is now fine.
11768 said:
@OP, try switching to a different kernel and see if that solve the problem. I was previously using ninphetamine and have the same problem as you. Worst is it auto-reboot too! After switching to stock kernel, everything is now fine.
Click to expand...
Click to collapse
Did you switch back to CF-Root (Stock?) or back to stock Rom with stock kernel?
Thanks, see if this works.
I've noticed that this is quite common with this phone. Also note that plugging in a USB jig will also decrease the overall battery percentage for some reason. I'm guessing all this is normal, the OS just redetects the battery levels upon startup. Try calibrating your batteries guys!
Sent from my non-Apple device via XDA App
try one of these kernels.The "Workaround Edition" versions might be worth a go.Read a bit first as it tells you that they are there incase you have problems with the release version.
http://forum.xda-developers.com/showthread.php?t=1179814
cr0wnest said:
I've noticed that this is quite common with this phone. Also note that plugging in a USB jig will also decrease the overall battery percentage for some reason. I'm guessing all this is normal, the OS just redetects the battery levels upon startup. Try calibrating your batteries guys!
Sent from my non-Apple device via XDA App
Click to expand...
Click to collapse
Did a calibration just 2 days ago and today the problem is back again. But I'll replace it anyway because I've another bug. If i knock the device on my hand then it turns off completely. I've seen this bug on youtube.
But if the battery problem persists on the new device I'll try another kernel.
Me also having the same problem but fixed it by using Lightng Rom 6.1 and calibrated my battery properly ofcourse
Replacement will arrive on monday via DHL express. Then I'll test if it's again with the new device.
sam911x said:
Me also having the same problem but fixed it by using Lightng Rom 6.1 and calibrated my battery properly ofcourse
Click to expand...
Click to collapse
I'll switch to LeoMar with CF Root 4.1 when my new SGS2 arrives tomorrow.
Lite'ning is dead for now. So won't use it anymore if there's no further progress on that rom.
You should test if it works either with CF Root and LR6.1 or another Rom with Ninph. Kernel and see if this works in any combination.
I have two galaxy s2s. one is i9100 and the other one is i777 on at&t.
SoD happened once on each phone. The i777 was running stock gingerbread and the i9100 was running resurrection remix 1.9.1 with the siyan kernal I believe.
The screen just wouldn't turn on so I just pulled the battery out (is it safe for the phone?)
This doesn't happen often,well just once each on each phone as stated before, but it does bug me as it makes me think there's something wrong with my phones, and pulling the battery out doesn't seem like it's good for the phone.
I searched around the forum a bit and saw other people are having this issue as well. And not just the galaxy s2, but other phones too.
only sleep of death in almost 10 months of use is when i tried xwlp9.
so no its not common
It's fairly common yes, a lot of people running non-stock ROMs get this. I had this ~25 times on numerous Resurrection Remix ROMs, but since v1.9 I haven't had this issue fortunately. If it's causing you a big problem, try fixing permissions from CWM recovery, that seemed to make a big difference when I was having the problem.
SOD usually occurs when the kernel UV the CPU or GPU a little to much. Not every device is the same and not handle same kernels, UV values etc
Sent from my GT-P6810 using XDA Premium HD app
From the sound of it, it seems to be a software problem.
I got it on the i777 which wasn't running a custom rom. But I think it could be caused by that battery management app that I installed.
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
It's normally a firmware issue, or a conflict between an app & the firmware. You'd find it's pretty rare for an 'untouched' (I.E not modded) phone running stock firmware to have SOD's. And obviously if you're flashing custom firmware that's constantly evolving/changing, then sometimes you're going to get SOD's, tho with most well crafted firmware these are fairly rare.
I reckon I've probably had <10 in the 8 mths I've had my phone & I've been running non-stock firmware the whole time save for the week I got my phone, which is nothing when stacked up against all the mucking around I've with my phone.
Edit to add - One way you can test to see if SOD's you're having are possibly hardware related is to do a completely clean install of stock firmware & see if they still happen. If they don't, then it's obviously whatever firmware you were running. If they do, then it might be hardware-related. Re: your question about pulling the battery after a SOD, normally this shouldn't cause you any problems (it's sometimes the only way you can successfully reboot the phone).
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
victorator said:
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
Click to expand...
Click to collapse
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Ray_Grey said:
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Click to expand...
Click to collapse
Or just flash the newer build. No SOD there.
wanewon said:
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
Click to expand...
Click to collapse
How about this?
I answered your question. Read the edit I made to my post.
wanewon said:
How about this?
Click to expand...
Click to collapse
MistahBungle said:
I answered your question. Read the edit I made to my post.
Click to expand...
Click to collapse
Thank you for the answer.
Since it's kinda hard to recreate the SOD. I'll reflash the rom and kernal and do a wipe and see if the SOD still happen
victorator said:
Or just flash the newer build. No SOD there.
Click to expand...
Click to collapse
Victorator, forgive my ignorance, but are you saying i should just flash the latest build, XWLPD, onto my fone rather than re-rooting it using a different kernel (i.e. CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip) in order to stop the SOD?
Never faced such issues ever.
Sleep of death
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
MX 007 said:
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
Click to expand...
Click to collapse
bah bye
SOD
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
?
darkm1st87 said:
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
Click to expand...
Click to collapse
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
tkrokod said:
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
Click to expand...
Click to collapse
Hi,
I'm also trying to solve this problem, since weeks.
My observations:
SOD happens most on higher battery status (e.g. more SOD's at 80% battery then at 20%
The Phone gets hot after SOD and also before the SOD comes.
While loading the Phone SOD's happen more often
The battery status drains rapidly while SOD (cause of the resulting heat)
My SOD's are independent of kernel, rom, firmware or what ever.
I think it's a hardware problem, but I've no warranty and what to solve the problem without changing the mainboard. It couldn't be a really defective of an important part, cause the phone works apart of this SOD-problem.
Maybe we could find out together howto solve these anoying sod's
Hey. Im trying to solve the SOD problem myself cause its been happening every day and its really annyoing since the phone isnt even a month old.
I got the newest cyanogen mod running.
The phones model is GT-i9100
Android is 4,2,1
I still have warranty on it, do you think I should go back to stock, go exchange my phone where I got it and see if the new one has SOD too or should I just try fixing it first.
Also apps I use constantly : go launcher and dragonvale
I have a 8 gb micro SD inside as well, dunno if that could cause this.
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
MaxPresi said:
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
Click to expand...
Click to collapse
Same problem here,
Try wiping dalvik Cache about 10 times ..it worked for me ...
I also had this problem ...but it got solved becaz I had a backup of good runing rom without SOD
Can you turn the phone on if it shuts down or do you have to remove battery? I had the problem only on Neutrino rom, but I didn't do a clean install so I thought it was that
I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix, with some of them the phone not started.
But I do not have this problem with the new kernel (3.1.10) .. or with CM9 nor the CM 10.1 Epinter. The problem with this kernel is when it heats up very much, the screen tearing.
And no, I do not need to remove the battery ... if I hit once as if I turn on the screen, he turn on himself.
I've tried to save the logcat with the application Catlog and put him to save every 1 line, but not the right ... he save the log a few minutes before turning off.
As the 3.1.10 kernel works, I believe that is not a hardware defect.
My memory is: 0x00EF (0xBEEF)
TegraTevision: A03 prime
Tegraparts: mbr: 1100:100:800
thanks ...
Hi may I ask if you resolved this problem as I have it to. Thanks
lisaamybeth said:
Hi may I ask if you resolved this problem as I have it to. Thanks
Click to expand...
Click to collapse
The post just above yours has a solution... read it.
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
lisaamybeth said:
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
Click to expand...
Click to collapse
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
lisaamybeth said:
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
Click to expand...
Click to collapse
In the post that I replied to, you only stated that you had issues with CM10.1/3.1.10 kernel, which is why my post was worded the way it was. you didn't specify that it was also with GB based ROMs as well. The only thing that makes sense at this point is a board/hardware related issue. As I briefly said in my last post, we all have different board revisions. We all won't see the same results. Thats why you see people talking about having screen tearing issues when others have no issue. I suspect its the same in regards to this issue.
My screen issues after powering on from sleep have been resolved with Firmware .475
Also mine. I no longer have any funky lines when I wake the device or other strange screen issues since updating.
So so nice. Performance is fantastic.
Sent from my Sony Xperia Z Ultra
brosenz said:
My screen issues after powering on from sleep have been resolved with Firmware .475
Click to expand...
Click to collapse
My battery took a nose dive since the upgrade.. I had issues at first, but they settled down. Now with the upgrade my battery is back to being crap again.
I thought for sure it fixed my SOD. Then five minutes ago, I turned off the phone to eat something. Five minutes later, hit the power button. Dead. Power + Up required as always.
The buttery life is amazing with new update !
Fixed my curtain issue
Sent from my C6802 using XDA Premium HD app
seem like fix my touch issues also:victory::victory:
Will I get an update even if xzu hast been officially released here?
Sent from my C6802 using Tapatalk HD
kramdens said:
My battery took a nose dive since the upgrade.. I had issues at first, but they settled down. Now with the upgrade my battery is back to being crap again.
Click to expand...
Click to collapse
It'll settle again after a couple of charges. This is something most ROM flashers here knows (not saying that you should've known, but now you do).
brosenz said:
My screen issues after powering on from sleep have been resolved with Firmware .475
Click to expand...
Click to collapse
The same. Additionally the Issue with the proximity sensor was resolved also (the screen did not switched on after phone was got from face )
Sent from my C6802 using xda app-developers app
Maybe that who cant fix issues got a defective device ??
avetny said:
Maybe that who cant fix issues got a defective device ??
Click to expand...
Click to collapse
Or maybe the bug(s) are still sticking (pretty common with ROM flashing). They should do a full reset/wipe after updating and see if that solves it.
LordManhattan said:
Or maybe the bug(s) are still sticking (pretty common with ROM flashing). They should do a full reset/wipe after updating and see if that solves it.
Click to expand...
Click to collapse
100% agree ! Always full wipe !
I think one of the new features is the smart dial
Now you can search through the dial pad in the phone.
Sent from my C6802 using xda app-developers app
I didn't experience SOD on the .471 either but my experience from other devices are as follows when it comes to narrow the problem down:
1. A rogue app. If the device suddenly starts to SOD after a couple of installations, then there's an app causing it to hang when entering deep sleep.
2. Excessive undervolting (not relevant for us yet). One SOD cause is too low voltage to the CPU, causing it to lock up when it enters deep sleep. The problem can also be connected with underclocking, for example to 100 or 192 MHz.
3. Hardware failure.
4. ROM problem. There are ROMs, even official ones that are prone to SOD.
The solution is to make a full wipe and then just wait and see what happens with the device when it is completely clean. If it still suffers from SOD even if nothing is configured, then it points to a hardware problem or ROM bug. Trying a different ROM can be worth a try.
If that still doesn't solve the problem, i.e. it continues to SOD regardless of ROMs - there is a hardware failure.
If it works fine after a full wipe but then starts to experience SODs when apps are installed etc, then there is a rogue app involved.
My longest uptime on the 471 was around 5 days and 6 hours before I updated to 475. No problems during that time.
E90 Commie said:
I didn't experience SOD on the .471 either but my experience from other devices are as follows when it comes to narrow the problem down:
1. A rogue app. If the device suddenly starts to SOD after a couple of installations, then there's an app causing it to hang when entering deep sleep.
2. Excessive undervolting (not relevant for us yet). One SOD cause is too low voltage to the CPU, causing it to lock up when it enters deep sleep. The problem can also be connected with underclocking, for example to 100 or 192 MHz.
3. Hardware failure.
4. ROM problem. There are ROMs, even official ones that are prone to SOD.
The solution is to make a full wipe and then just wait and see what happens with the device when it is completely clean. If it still suffers from SOD even if nothing is configured, then it points to a hardware problem or ROM bug. Trying a different ROM can be worth a try.
If that still doesn't solve the problem, i.e. it continues to SOD regardless of ROMs - there is a hardware failure.
If it works fine after a full wipe but then starts to experience SODs when apps are installed etc, then there is a rogue app involved.
My longest uptime on the 471 was around 5 days and 6 hours before I updated to 475. No problems during that time.
Click to expand...
Click to collapse
How do I do a full wipe with SOD? Sony Bridge and PC Connect both won't continue when I click on the "continue" button at the personal data loss screen (the personal data loss disclaimer box is checked).
I ran into this issue using a mac.
Sent from my C6802 using XDA Premium HD app
dobygot said:
How do I do a full wipe with SOD? Sony Bridge and PC Connect both won't continue when I click on the "continue" button at the personal data loss screen (the personal data loss disclaimer box is checked).
Click to expand...
Click to collapse
I do the full wipe from Settings. Now I have an unlocked bootloader and can't use either Sony Update Service or Sony Bridge and I prefer to have it that way. I trust FlashTool more.
Updating without full wipe using S-US/Bridge is a pretty sure way to experience problems.
Xiaomi Note 3 Pro 2/16GB
Hi,
i am currently on a nightly cm13 build. before i had the same issue on the snapshot build.
Used also different kernels but with the same results.
Issue is shown in the video below.
https://www.youtube.com/watch?v=HI43XX0WIpY
This happens probably once a day and only when i am waking up the phone from deepsleep with the fingerprint sensor.
The screen keeps being black for a second when this happens. When i turn off the screen and wake it up again, everything is fine.
What do you think, hardware or software issue?
EDIT: Just found out, that it could be potentially a LiveScreen issue on cm13
EDIT2: No, LiveScreen is not the problem
I'm also facing this issue. Are you using any custom kernel?
I'm using the Blaze kernel.
Yes, was using Blaze kernel as well but i tried different others as well.
I am now on Exodus ROM without these issues.
Seems to be a cm bug.
I've had the issue also while charging my phone last night.
CM13 with Redon kernel.
Scared the sh*t out of me...
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
MiripRedmoon said:
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
Click to expand...
Click to collapse
i know its long time ago, but could you repair the device?
screen glitches
same problem, flickering and mistyping too. Please anyone resolve, this has happened after the latest update
I had this issue, rom and kernel reinstall solved the problem. Maybe something is cached/crashed or both (the phone acted weird other ways too, random apps crashed and so on), before reinstall wipe cache, dalvik, data and system, then install the latest versions of the rom and kernel you want to use. Don't forget to flash firmware.
Since I did this everything is fine.