Went through this with my Captivate. Had it replaced 3 times before I got one that didn't do it. Upgraded to the S2 in 12/11 and didn't have any SOD issues at all. Had to have it replaced in 10/12 because of charging port issues, but replacement has worked fine with rooted stock 4.0.3. That is, until this week. Had a SoD 4 days ago. Thought it was just an anomaly until I had another one today. Nothing new installed, normal usage. Man, what a PITA these are. Is it just Samsung phones that suffer SoDs?:crying:
Did you do the update to 4.0.4?
Phalanx7621 said:
Did you do the update to 4.0.4?
Click to expand...
Click to collapse
Nope. Nothing new installed in weeks beyond normal app updates. When I restarted the phone the batt was down to 40%, so something was seriously draining it before it went dead because it had been at 92% an hour before.
Miami_Son said:
Nope. Nothing new installed in weeks beyond normal app updates. When I restarted the phone the batt was down to 40%, so something was seriously draining it before it went dead because it had been at 92% an hour before.
Click to expand...
Click to collapse
Double check your Android Version
122ninjas said:
Double check your Android Version
Click to expand...
Click to collapse
Still on 4.0.3. Just went to check it after unplugging it an hour and a half ago. Dead again. rebooted and it was down to 74% batt and looking at the stats Android System was using 40% before it cut off. I noticed the same thing last time. What in the Android System could be causing so much activity that the phone drains the battery so quickly and just suddenly shuts off?
Maybe you're just rough on phones. My S2 is a very early model. Brother had it first and rooted/flashed all the time. I've had it for months doing the same thing. I've never had sod or force closed or anything. Currently on Dirty Root box and I don't even recall ever having to pull the battery before. Mines even been naked for over a month now without a single scratch, looks as new as day one.
Rough on phones? How do you mean? I never carry it in my pocket. The last 3 have always had a TPU cover and carried in a leather case. Always have screen protectors, never gotten wet or dropped. Nope, I'm very careful with my phones. This particular one I was satisfied to simply root it and leave it alone. Previous phones have all manner of custom ROMs installed with all kinds of framework and other tweaks. I did notice that I had JuiceDefender installed, which had run fine on my first S2. I'm guessing it might not be as compatible with ICS as it was with GB. Have removed it and hopefully the problem, as well.
SOD's here too
My wife has the S2 and has been having SOD's since the ICS update. Thinking the update to 4.04 would fix it, I updated it for her, but no dice. Replaced the battery too. I know this issue has been present for many sgs2's for a while now. Unfortunately, I was never able to find a solution. Since it is not my phone, flashing another ROM is not a solution. However, if anyone knows a solution for this(even if root is required), I am all ears.
Btw, to the OP, never had juiced defender installed on her device so not sure if that would really be the cause of your issue.
My honest opinion is that either it is an issue with the stock kernel/OS or an issue relative to the battery components (charge circuits/motherboard) with some devices.
Since I tend to err more on issues usually being in the software, my thought is that if and when JB is released for the ATT S2, this might alleviate this along with other issues, more importantly for those that are stock only oriented.
mastergflash said:
My wife has the S2 and has been having SOD's since the ICS update. Thinking the update to 4.04 would fix it, I updated it for her, but no dice. Replaced the battery too. I know this issue has been present for many sgs2's for a while now. Unfortunately, I was never able to find a solution. Since it is not my phone, flashing another ROM is not a solution. However, if anyone knows a solution for this(even if root is required), I am all ears.
Btw, to the OP, never had juiced defender installed on her device so not sure if that would really be the cause of your issue.
My honest opinion is that either it is an issue with the stock kernel/OS or an issue relative to the battery components (charge circuits/motherboard) with some devices.
Since I tend to err more on issues usually being in the software, my thought is that if and when JB is released for the ATT S2, this might alleviate this along with other issues, more importantly for those that are stock only oriented.
Click to expand...
Click to collapse
Flash back to 4.0.3 or 2.3.4
Sent from my GS4 running CM11 Kandy Kane
Haven't had an SoD since ditching Juice Defender. Still not going to update to 4.0.4, though.
Miami_Son said:
Haven't had an SoD since ditching Juice Defender. Still not going to update to 4.0.4, though.
Click to expand...
Click to collapse
4.0.4 causes sods
Sent from my GS4 running CM11 Kandy Kane
Following the 4.0.3 update (summer 2012 or so), I had SoD episode once or twice a month. I lived with it. I updated to 4.0.4 via OTA AT&T and had SoD everyday (sometimes 2-3x a day). I just rooted and installed AOKP and have been SoD-free since. I wont go back to stock AT&T.
122ninjas said:
4.0.4 causes sods
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
I know.:silly:
I saw a post on the AndroidCentral forums that said that disabling the AT&T Smart WiFi app fixed the SoD problem. The poster thought it came along with the 4.0.4 update. He also disabled most of the other AT&T crapware, so you might want to try disabling some of the other AT&T apps if disabling Smart WiFi doesn't fix the SoDs.
mvi57 said:
I saw a post on the AndroidCentral forums that said that disabling the AT&T Smart WiFi app fixed the SoD problem. The poster thought it came along with the 4.0.4 update. He also disabled most of the other AT&T crapware, so you might want to try disabling some of the other AT&T apps if disabling Smart WiFi doesn't fix the SoDs.
Click to expand...
Click to collapse
Yep, this right here. After I updated to 4.0.4 I was having 2-3 SoD's a day. Disabled Smart WiFi and all the other AT&T crapware and haven't had one SoD since.
I have the clean version of the 4.0.3 ROM that has none of the AT&T crapware, so that wasn't the issue. Since uninstalling JuiceDefender I have had zero issues.
Miami_Son said:
I have the clean version of the 4.0.3 ROM that has none of the AT&T crapware, so that wasn't the issue. Since uninstalling JuiceDefender I have had zero issues.
Click to expand...
Click to collapse
Its been known that jd causes issues and doesn't help at all ics+ and barely helps on -gb
Sent from my GS4 running CM11 Kandy Kane
It did help a lot on GB, but the problems quickly developed when I enabled it on ICS. Never again.
Related
I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
I can't speak on the new build, but I was running the 4.0 build and my battery ran down so quickly that I thought I left my gps running with a connection. I also was having quite a lot of issues with the rom, so I thought it was a fluke. I'm on 4.1 and it's been running much better, so hopefully the battery drain isn't as great.
Definitely sounds like you've got a runaway process or wake-lock occurring somewhere. Have a look around the processes and see if something's keeping the CPU running hard. Also run a dumpsys power from adb and see if something's keeping it from sleeping.
Im getting quite the opposite here. It's been almost a day and after moderate use I have a little over 50%. It's amazing because I would be getting half of that on a full charge in froyo.
Looks like it may have been the Widget itself.
But i am not sure, if i closed the running application of Battery Monitor it dropped down to -1 or -2 but then ten mins later its back up to -300.
The other possibility is when i kill the app the widget gets no information and defaults to a low number.
Thank you everyone for your input. I will keep on testing to find my battery killer.
I also may try uninstalling K-9 mail and reverting to the stock Mail client
It being on stock kernel and a lot of debugging features being enabled will do that to your battery.
Sent from my SCH-I500 using XDA App
A lot of people have reported poor battery life with K-9, FWIW, though the K-9 devs say there isn't an issue. I haven't used it myself so I can't really say... you could try this though:
https://market.android.com/details?id=org.r3pek.k9datakiller&feature=also_installed
4.1 drained my battery from 100% to 10% in about 4 hours today. But then I plugged in and rebooted and I had 40%, so I would imagine a battery stats wipe is needed on my phone.
My home button does not work as well, so I am going to re-install again and see if it fixes these issues.
Anyone else had the home button issue?
Edit: The re install fix the home button/lock screen issue. Will report back on the battery tomorrow.
Weird, my battery is AMAZING on Nameless. After 11 hours with using Screeble, with moderate use, I'm at 50%.
xwhofarted said:
I installed the Nameless v4 yesterday and v4.1 today.
On the Froyo roms my battery pull on idol was -2 to -10ma [i use battery monitor widget]
Now on the GB i am getting -100 to -275.
Is anyone else experiencing this kind of draw?
[I do understand that the GB is a wip]
Click to expand...
Click to collapse
I tried Nameless 4.0 and it used less than 20% during the first 6 hours.
Whenever I flash a new rom, it uses more power at first and less and less as you use the phone. Some people insist that you do not have to kill the apps especially on Gingerbread.
zas311 said:
Some people insist that you do not have to kill the apps especially on Gingerbread.
Click to expand...
Click to collapse
Assuming you're talking about task killers, "some people" = Google. With the exception of apps like Watchdog (which just notifies you of apps using excessive CPU, like >50%), task killers hurt more than they help -- they're all effectively scams.
Google's serious techy explanation:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.
An excellent, understandable article from Lifehacker:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
I thought I read somewhere (either the EC09 Leak thread on the Nameless v4 thread) that auto-rotate is causing 50% cpu for this EC09 leak, would that have something to do with battery drain?
http://forum.xda-developers.com/showthread.php?t=1131213&page=15
Thanks
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
xwhofarted said:
saw the one about auto rotate and turned it off, then i was in the -50 to -100
But that is still bad coming from froyo`s -2 to -10
So i went back to Com Rom and will be awaiting the best Devs on XDA to crack the Leak and make some fantastic ROMS, just like they did with Froyo!
Keep up the good work!
Click to expand...
Click to collapse
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Scrappy1 said:
I suggest disabling auto rotate, rebooting, and then never turning auto rotate on again. (even toggling on/off can get the events/0 process stuck at high cpu usage) Once I did this, the full bloated GB leak is spanking Froyo battery life.
This more than makes up for the poor contacts scrolling for this guy.
Also full bloated GB leak appears to be much safer for you SD card than other versions of the leak.
Click to expand...
Click to collapse
This. My battery life (and signal dBm) has been MUCH better even at work, which is notoriously hard on the battery due to being so well insulated.
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
sarkozy said:
I've had ZERO issues with the SD card so far, and it's a huge mystery what exactly is causing that. I ODIN'd the leak an hour after it was posted, then the NamelessV4 rom, then the NamelessV4.1 and haven't had a single issue. There needs to be a better process of defining it, and I'd be willing to bet it has something to do with the recovery the person used when it was flashed.
Click to expand...
Click to collapse
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
That's definitely what I'd be leaning towards. I also took the added (though not really needed) step of using the GB root exploit app, and confirming all was well before ever flashing CWM3.xx in ODIN, then going onto the nameless ROMs. I've actually tried to re-create the problem since I stuck in a spare 4GB card waiting for it to happen, but nothing so far.
Everything is so new, it's really all speculation for the time being. I personally don't think it's the ROM or the leak causing the problem, although it's obviously a factor. There are so many different combinations of recoveries being used (as if all of us read directions in full) and ROMs were flashed in different sequences that it's impossible to nail it down.
Aside from disabling auto rotate, I've had no complaints about the leak or ROM. I ran CM7 forever on my Eris before getting this Fascinate, and while I like it, it's a pain to deal with the missing functionality at times.
xwhofarted said:
I was one of the unlucky ones that had a 16GB get ruined. But i know it was my fault. i didnt odin the original leak i went from com rom to nameless and it botched my card. But i am lucky i had my POS BB Storm 2's 16gb. I also went and got a $10 4gb card that i now use when testing out the GB roms [better safe than sorry]
I will try that with the new rom and let you know what i am getting.
Click to expand...
Click to collapse
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
detox07 said:
I went from stock odin to nameless and my card was eaten alive...I followed the steps exactly as listed not missing one thing. So it has nothing to do with flashing from another rom
Click to expand...
Click to collapse
So, immediately upon flashing the sd card was corrupted?
It'd be nice if there was more cooperation among everyone to figure out the common problem. It seems like for all the trouble reports, there are as many or more of us with no issues. I can't see anything in logs that would tip off a problem, so it needs to be someone who has the issue.
I'm still leaning towards it being a recovery issue. It's odd that some people are saying the files still appear on the sd when viewed through the CWM interface.
Sent from my SCH-I500 using Tapatalk
Man, that would be awful if the CWM we were told to use is what is killing the SD cards, and a diffr version would have worked :O
I used the CWM linked in the nameless thread and no issue so far, but only 2 days so far.
I decided recently to do the OTA update to 2.3.5, and since then, I've been getting terrible battery drain. Overnight, I lose a few % per hour. I have to charge the phone everyday even if I don't use it. It says Android OS is draining most of my battery. I haven't noticed any significant improvements from 2.3.5, but I've noticed a few annoyances, like when I press back out of an application, it doesn't close it. I have to use my task manager.
Anyone know a fix to this without putting on another ROM/Kernel? I haven't done that since my Captivate, and I doubt I'm adept enough to do it at the moment.
CalvinL said:
I decided recently to do the OTA update to 2.3.5, and since then, I've been getting terrible battery drain. Overnight, I lose a few % per hour. I have to charge the phone everyday even if I don't use it. It says Android OS is draining most of my battery. I haven't noticed any significant improvements from 2.3.5, but I've noticed a few annoyances, like when I press back out of an application, it doesn't close it. I have to use my task manager.
Anyone know a fix to this without putting on another ROM/Kernel? I haven't done that since my Captivate, and I doubt I'm adept enough to do it at the moment.
Click to expand...
Click to collapse
Post in the proper forums for your phone? These are the forums for the AT&T SGH-I777, whick never had an official 2.3.5 release. Just UCKH7 (2.3.4) and UCKK6 (2.3.6)
Entropy512 said:
Post in the proper forums for your phone? These are the forums for the AT&T SGH-I777, whick never had an official 2.3.5 release. Just UCKH7 (2.3.4) and UCKK6 (2.3.6)
Click to expand...
Click to collapse
Calm down. I meant 2.3.6.
CalvinL said:
I decided recently to do the OTA update to 2.3.5, and since then, I've been getting terrible battery drain. Overnight, I lose a few % per hour. I have to charge the phone everyday even if I don't use it. It says Android OS is draining most of my battery. I haven't noticed any significant improvements from 2.3.5, but I've noticed a few annoyances, like when I press back out of an application, it doesn't close it. I have to use my task manager.
Anyone know a fix to this without putting on another ROM/Kernel? I haven't done that since my Captivate, and I doubt I'm adept enough to do it at the moment.
Click to expand...
Click to collapse
No.
The battery drain is a fairly common complaint with the 2.3.6 OTA update. As far as the back button, I havn't seen that mentioned, and I did not notice the behavior during the short time I experimented with the OTA update.
Your options are, 1) flash Entropy512's latest (12/21) daily driver kernel to see if this will stop the battery drain, 2) go back to stock UCKH7 and aviod the update, 3) flash a custom rom.
Flashing a custom rom is the best option in my opinion. There are guides to help you step by step.
CalvinL said:
Calm down. I meant 2.3.6.
Click to expand...
Click to collapse
In that case, why post your own thread instead of on one of the MANY threads discussing UCKK6 battery issues?
Entropy512 said:
In that case, why post your own thread instead of on one of the MANY threads discussing UCKK6 battery issues?
Click to expand...
Click to collapse
Which is why this one will be closed... NOW.
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.
Anyone who updated your SGH-I777 to ICS facing heating issues while downloading stuff from market or using internet over WIFI/DATA?
My phone has horrible heating issues after the upgrade from 2.3.6 to 4.0.3. Its terrible. My phone on GB was smooth like butter and never faced any kind of heating or lagging issues. but this ICS upgrade is just one ****.....
Please help me by sharing your experience while on WIFI or DATA connection.....
Mine has been doing that for a few months now. Since I started using AOKP. Anytime I use my phone for a few minutes it starts to get warm, getting hotter the longer I use it. I was worried at first, but got used to it. Like the camera whirring noise, I just ignore it mostly.
I am planning on getting a warranty replacement anyway sometime before the warranty runs out, so I haven't worried about it.
It could be a rouge app running all the time. Better Battery Stats will let you see if any apps are preventing your phone from sleeping. CPU spy will also let you see if your phone is sleeping. A rogue app generally causes battery drain too. I see the same battery life on ICS as GB for the most part.
Sent from my SGH-I777 using xda app-developers app
I don't think it has anything to do with the app running...... Its a very fresh installation and after the boot, I have tested downloading the say 5 apps from Playstore.The top portion of the device heats up big time. I am an android engineer and have rooted and applied custom roms on the devices but I am not willing to do that on this device becoz the Stock GB on SGH-I777 (2.3.6) is the best i have come across in terms of stability and efficiency. So just badly wanna go back to stock 2.3.6 but online I saw ppl facing problem when they downgraded to stock 2.3.4.....
I am still repenting on upgrading the device...uffff damn it
The only time I noticed anything like that was when I put my phone in the
mobile dock and using the GPS and it was a hot day plus it was charging.
Once I plugged into the regular house charger it cooled down
(even though it was still charging).
I guess they have overlocked the device and thats the reason y its heating up
I don't over clock my phone. I run AOKP with Fluxxi kernel, and don't touch the CPU speed, voltage, or governor settings. My phone didn't get hot like this on SHOstock, but pretty consistently on AOKP it heats up when ever I use it. I posted in another thread about heat issues that at the end of the day I had 13 hours up time, and less than 3% was at 800 MHz or above. The most common was deep sleep, 200, and 500.
I don't worry about the heat anymore, I got used to it. Most of the time its just warm, but if I get downloading a big file it gets really hot. It doesn't seem to affect the performance or battery life, so I don't worry.
Sent from my cm_tenderloin using xda app-developers app
AOKP and CM9 with Fluxi Kernel very heat when I played Nova 3.
Ever since the first ics leak came out its been on my phone and have had nothing but heat issues some to the point i worpped my sim card and back cover. Yes warrenty replaced it (the phone) not the back cover. So it is just something to deal with till jellybean is released. Hopefully they will have fixed it.
Sent from my SAMSUNG-SGH-I777 using xda premium
I had some problem on all the ics roms except shishir Rom. It's been good for 4 days so far. Keeping my fingers crossed.
Sent from my GT-I9100 using Tapatalk 2
Or stay on GB lol. I really didnt like how buggy ATT ICS seems to be with some apps like WordPress
I would love to go back to GB but scared use the ROMS that are available online.. I have done lot unlocking and rooting stuff on devices but i failed one time and thats what is holding from rooting/unlocking the device. Also I have realized that the custom ROMs are always buggy.....
Some people have had heating issues on ICS, and others not. Don't really know what the difference is. I suppose there could be some differences in the hardware.
Anyway, going back to gingerbread is relatively safe. You can go back to fully stock, or you can go back to stock plus root. Each of these options would be by flashing the firmware with Odin from a windows pc. Neither of these packages contain bootloaders, so the risk is minimal, almost non-existant. The packages are UCKH7, Gingerbread 2.3.4, although there is a UCKK6 plus root available also. You can use the guides linked in my signature, the one for returning your phone to the store for straight stock, and the one for flashing firmware without incrementing the flash counter for stock plus root.
Custom roms vary in stability. Some are extremely stable. I would say that SHOstock2 is as stable as about any rom I have ever used. It's certainly good enough for every day use. It is ICS though, and don't know how your phone would do with it. I have seen a few reports of overheating with it, although my phone rarely gets even warm to the touch.
Just wanted to echo 1) my phone also gets hot when being used heavily (wifi, bt, gps, data, sync, all on) but not to the point of concern. And 2) the reco of shostock2 3.1.0+ for stability.
Sent from my SGH-I777 using Tapatalk 2
vishalraop said:
I would love to go back to GB but scared use the ROMS that are available online.. I have done lot unlocking and rooting stuff on devices but i failed one time and thats what is holding from rooting/unlocking the device. Also I have realized that the custom ROMs are always buggy.....
Click to expand...
Click to collapse
creepyncrawly said:
Custom roms vary in stability. Some are extremely stable. I would say that SHOstock2 is as stable as about any rom I have ever used. It's certainly good enough for every day use. It is ICS though, and don't know how your phone would do with it. I have seen a few reports of overheating with it, although my phone rarely gets even warm to the touch.
Click to expand...
Click to collapse
One of the most stable, smooth GB roms is UnNamed 2.2.1, which you can check out HERE. I used it for a good while, but wanted to try ICS. Excellent, stable rom, with themes available.
...its called fried ice cream.
creepyncrawly said:
Some people have had heating issues on ICS, and others not. Don't really know what the difference is. I suppose there could be some differences in the hardware.
Anyway, going back to gingerbread is relatively safe. You can go back to fully stock, or you can go back to stock plus root. Each of these options would be by flashing the firmware with Odin from a windows pc. Neither of these packages contain bootloaders, so the risk is minimal, almost non-existant. The packages are UCKH7, Gingerbread 2.3.4, although there is a UCKK6 plus root available also. You can use the guides linked in my signature, the one for returning your phone to the store for straight stock, and the one for flashing firmware without incrementing the flash counter for stock plus root.
Custom roms vary in stability. Some are extremely stable. I would say that SHOstock2 is as stable as about any rom I have ever used. It's certainly good enough for every day use. It is ICS though, and don't know how your phone would do with it. I have seen a few reports of overheating with it, although my phone rarely gets even warm to the touch.
Click to expand...
Click to collapse
I did try your odin but unfortunately it didn't recognize my device at all. So I juts gave up on using your odin. I am not sure why odin is not detecting my phone. I am using SGH-I777 AT&T with ICS 4.0.3. Any idea whats the problem. Please note that I have not rooted this device and its always been on stock firmware/software.....
i m on AOKP rom with my i777, it does heat up a little bit (lcd top part and back near camera) when i m using 3g, wifi is ok..i wonder if the antenna is around there so its causing heat?
f4remix said:
i m on AOKP rom with my i777, it does heat up a little bit (lcd top part and back near camera) when i m using 3g, wifi is ok..i wonder if the antenna is around there so its causing heat?
Click to expand...
Click to collapse
You got it right. Thats exactly where I feel the heat on my device..... Trust me, I didn't feel any heating effect whatsoever when my device was on GB. So I m pretty sure that the hardware is all good and its the firmware/software thats screwing up the device.
Personally I found my phone got hot after setting up an exchange account on it. I also got massively reduced battery performance. Once I removed the exchange account operation returned to normal.
One or more of the apps (from the old GB install) that is running in the background causing it to heat up, I was ruuning into that issue when I first updated to ICS. I end up doing the factory wipe and reload every apps back on. Now I don't have that problem.
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
I am not having problems like you report at all. The only lockups I had were during the brief period when I ran under ART, and they went away completely after I switched back to Dalvik. Note that under ART my G3 got really hot...
That is what I think is causing most of these phones troubles. I think they were designed in a way that is prone to overheating issues. I also think the designers tried their best to avoid overheating through throttling - which causes some performance degradation, and doesn't always work anyway.
Minor assembly differences could be causing major differences in how different G3s heat-load. This could explain why some owners who have reported lockup issues like yours have gotten much improvement by exchanging their phone, which is what I suggest you do if you can.
moonfarm said:
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
Click to expand...
Click to collapse
I agree with Trent. Seems some G3s just don't run well. Mine runs great. I have it rooted with xposed and have removed the bloat and no issues at all. I couldn't be happier.
I've even played some games for the first time on my smartphone including Asphalt 8 and I've played it for about an hour non stop the other night while I had time to kill and still no issues, the game played great, phone didn't heat up and get laggy.... Nothing. It just played.
Hard to say really what's causing the issues for some, could be a funky device, maybe a factory reset would help... Maybe people also should take a look at what apps and widgets they have running as well prior to thinking the phone is junk lol not saying that's you, just an idea
- Tapatalked from the G3
moonfarm said:
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
Click to expand...
Click to collapse
No problems with mine.
What apps and widget are you using?
tech_head said:
No problems with mine.
What apps and widget are you using?
Click to expand...
Click to collapse
It's a pretty random problem, hasn't happened for a couple of days. I run a pretty lean system, not a lot of apps or widgets. Maybe getting rid of some bloat would help. Thanks all, nice to know it's not something everyone is going through. I'm enjoying the phone more than I thought I would, been on the S series since the first Galaxy Fascinate, so this was a bit of a leap. The combo of Knox and Touchwiz did me in...
Tim
I'm wondering if the accessibility service has anything to do with these random shutdowns. I've never turned on ART, but with several xposed mods, tweaksbox, and some debloating, my phone seemed stable for the first few weeks I owned it. One day I had a random reboot. It didn't happen again for a week or so, and then it happened once more. A few days later I noticed one of my tasker scripts (which reroutes gmail notification sounds through the headset iff the headset is connected) wasn't working. I checked the tasker accessibility service and it had turned itself off. After re-enabling it, my random shutdowns soon returned.
Anyone care to try ART with all accessibility services uninstalled? This would include talkback.