hello. I have a galaxys s2 hercules t989 known as tmobile. the problem is that the cell overheats me much when I use it and when charging too. the same load power cycled only takes 2 days to load. heats up like an oven. someone will know the problem this past me and I can help?
I'm having the same problem, it's not as bad on stock roms as on custom roms not sure why.
I have the original jelly bean I 4.1 and I've put several original and custom rom and is still overheating. I think it is problem of romsfirst
You guys need to check CPU usage
Install CPU usage app and load the timeline (also press the second button to see system apps). You can see which which one is using the most CPU power and terminate it. If that fixes it, you can uninstall or disable that particular app.
ok. result will do that and post them. thanks
JoeGrimm said:
I'm having the same problem, it's not as bad on stock roms as on custom roms not sure why.
Click to expand...
Click to collapse
Custom ROMS + kernels may have overclocked GPU and CPU for a performance increase. This will cause your phone to get hot. Hot Hot...If you're stock, there is something running in the background as others have suggested. If it's a custom ROM, install something like Trickerster MOD and check to see what your CPU and GPU are set at...Anything over 1512 (CPU) and 266 (GPU) will cause increase in heat due to the processors running past their stock settings.
Governor
If your capable of changing the governor like CM or other Roms with custom Kernal's, find a setting that doesn't use a lot of juice all the time. I keep mine on Smartass or conservative if i'm not using it or charging it. I had the same issue before because I had it set to ondemand or performance. Hope that Helps
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
NOPE
I have the same problem but it isnt the battery thats heating up, if you take the back cover off, and feel the battery, it is not heating up. I did get this problem when i installed a custom rom, i had issues with that one including the battery life so i switched back to official jellybean 4.1.2 or whatever, and the battery is fine, does still get hot though but not as much, or maybe were all huluscinating
--- ALIENS
Related
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
NissanNick said:
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
Are these freezes ONLY happening when running o/c? If so, then your hardware might not like o/c speeds. Please clarify that it is not an o/c issue due to the information you provided above.
If you're stable and having no locking issues on stock, then flash ROMS/kernels and of the bat start boosting to o/c speeds then seeing instability, how/why are you ruling out it's not a o/c or hardware limitation?
NissanNick said:
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
I don't think sprint will swap your phone out just because you can't manage stable o/c speeds on your phone. LOL
Sounds like you need to do the classic Wipe 3X before flashing.
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
NissanNick said:
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
Click to expand...
Click to collapse
It's not the overclocking that causes your phone to go into sleep of death, it is the low end. 100 Mhz causes sleep of death on a lot of phones on a custom ROM. Set your minimum frequency to 200 Mhz and you will be fine. Don't change any of the stoick voltages.
Try using stock speeds (400-1000). Then work your way incrementally in both directions to see which frequency(ies) cause your issues. Each phone is unique, so find the sweet spot.
I get the black screen of death about twice a month running twilight 1.1.1. My phone runs 200-1000 with no undervolting and set on conservative. I'm just too lazy to bother playing with settings since I'm holding out for SRF 1.3 to release.
Im stone stock right now. Do you see an actual improvement in apps that need the extra O/C HP? I have one game I bought that seems to be a little choppy at times, 9mm HD, and Im not sure if its the games coding, the fact that it maybe having a problem with ICS, or just not enough hardware HP to be fluid.
I OC'ed when I first got the phone but quickly dropped it back to 1200. This phone doesn't need overclocking and if you are noticing lag in games it is most likely due to poor coding by the dev for either ICS or dual core phones or both. If it is lagging on a 1.2 GHz dual core and it is our hardware think about people running it on the Inc 2 with a 1 GHz single core processor and basically last years tech. Our phones should be fine to run most if not all games for about a half year or maybe a year before OCing will really be needed.
Why don't you just do it and find out? It's really hard to tell because no kernel is a stock kernel with 1.35 GHz / 1.4 GHz.
All these kernels featuring OC have additional features which means that it could be the features/tweaks that are fixing it rather than the OC itself.
zephiK said:
Why don't you just do it and find out? It's really hard to tell because no kernel is a stock kernel with 1.35 GHz / 1.4 GHz.
All these kernels featuring OC have additional features which means that it could be the features/tweaks that are fixing it rather than the OC itself.
Click to expand...
Click to collapse
Well,...Im just pretty content with how it performs in every other aspect, except for this one game bugs me a little. Ive been ROMed and O/Ced on this not too long ago, and TBH, theres always some sort of little thig that turns me off about it. A spontaneous reboot here, a F/C there, and I find myself going stock again. I would do it in a heart beat if it didnt mean having to set every last detail back up again when I unlock the phone.
And yes, being virtually OCD about this phone sucks, lol.
I have a question as well!
For those under-clocking or using UV kernels, do you see a noticeable improvement in battery life? I have a GSM sock GNex and the battery life is atrocious.
stevessvt said:
Well,...Im just pretty content with how it performs in every other aspect, except for this one game bugs me a little. Ive been ROMed and O/Ced on this not too long ago, and TBH, theres always some sort of little thig that turns me off about it. A spontaneous reboot here, a F/C there, and I find myself going stock again. I would do it in a heart beat if it didnt mean having to set every last detail back up again when I unlock the phone.
Click to expand...
Click to collapse
Should of unlocked the bootloader day one before playing with the phone your phone still remains stock. Just the bootloader is unlocked, you'll virtually feel no difference. Except the fact that you have to relock for warranty purposes later but you'll wipe everything so that is always good because you don't want to exchange a phone with all of your passwords.
@andythefan: Yes there is a huge battery difference. Visit the Franco Kernel thread in GSM forums for people's images of battery history.
Flash the James Bond kernel so your gpu will be upped to 384mhz. It is in the development section.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
@rbiter said:
Flash the James Bond kernel so your gpu will be upped to 384mhz. It is in the development section.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Click to expand...
Click to collapse
Other kernels also have this feature. A lot of them do.
@stevessvt: In the myriad different combo's I've flashed (ARHD, Franco kernel, APex Kernel, bigxie ROM, AOKP rom, stock kernel, OC/No OC, Unvervolting, and 1 other kernel I can't even remember) I've yet to encounter a single random reboot, FC, or battery pull. I've also flashed countless different mods and basebands, etc.
It's all about doing your homework and really reading through threads before flashing and making sure different stuff is compatible and doing nandroids.
I can honestly say running a non-stock rom/kernel makes a noticeable difference in response and performance in daily use. Its really all the Kernel IMO, ROM's just give you features. I've however never noticed anything from OCing.
@andyfan: what build are you on? 4.0.2 has the hands down best battery life, and 4.0.3 with the Franco Kernel is nearly as good as 4.0.2 was (4.0.2 for me meant ~3% drain in 8 hours)
andythefan said:
I have a question as well!
For those under-clocking or using UV kernels, do you see a noticeable improvement in battery life? I have a GSM sock GNex and the battery life is atrocious.
Click to expand...
Click to collapse
For now any phone usage will give you terrible battery life due to the high power consumption of the screen especially if when it displays white onscreen content. Average CPU usage is very low unless you're running benchmarks consistently. Therefore UV tweaks have low impact on usage battery life.
With that said if your battery is irregularly draining while idle something may be active in the background.
Franco has made many tweaks to his kernel to reduce idle power consumption. He's gotten it down to about less than 1% drain per hour which can give you over 2 days of idle battery life. Just for ****s and giggles I have achieved that with less than 30 minutes of screen time with LTE enabled.
Franco's kernel is the best I've used in terms of overall battery life but none of the OC/UV kernels have significantly increased my usage battery life.
Sent from my Galaxy Nexus using XDA App
Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?
shinesthru said:
Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?
Click to expand...
Click to collapse
Hopefully more people respond to this, as I'd like to know more details around the msm-dcvs governor. I had it enabled in Clark's 0.0.6 ROM, and I noticed it was pretty much locked at right around 1000-1500mhz. It wouldn't scale below that. I don't know if it was something in the ROM or not, but I used Voltage Control to scale the min down to 352mhz or whatever it is.
I changed the governor to ondemand and set as boot as service (was getting errors creating the init.d script) and it seems to be functioning fine now.
I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.
EndlessDissent said:
I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.
Click to expand...
Click to collapse
What has your battery life been like?
jhavron said:
What has your battery life been like?
Click to expand...
Click to collapse
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead
EndlessDissent said:
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead
Click to expand...
Click to collapse
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.
hayzooos said:
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.
Click to expand...
Click to collapse
With the stock CM10 kernel, as soon as I touch the screen, the frequency jumps to 1134MHz and stays there until you turn the screen off. Then, it drops to the min. speed until you turn on and touch the screen again, at which point it jumps back to 1134MHz and locks itself there.
With the KT747 kernel, the speed more-or-less limits itself to 702MHz, and it's nearly impossible to make it scale any higher. KToonsez refuses to acknowledge the problem, so it won't be fixed anytime soon.
I've gotten CPU Spy graph screenshots to illustrate the problems (comparing the stock ROM to AOSP ROMs while doing the same task), but all parties still deny the problems exist. I don't really know what to do to get them to fix it at this point, so I just gave up. I'm hoping it's just some JB driver issue and it'll be fixed when the official JB kernel source is released.
Hi Guys
Well i have install several ROMS wich as HO!NO! full throtlle, Cyanogenmod 9 an 10 stables and Nigthly edition, JellyBam and others that i not even remember and all of them always in some point they just reboots and im really hate it. I use wakelocks app and it works for a few days but eventually it reboot and he battery drain really fast, 8hours in EDGE and just a little chatting on whatsapp and a few calls.
i always wipe system, datvilks etc, im kind of new on this stuuuf but i think im doing it correctly.
Im starting to think that maybe its a hadware problem. Onces i ask some crappy tech gay in a store and he told me that i should buy another battery i dont know why, i thought that he just want to sell me the battery but i dont know.
Can anyone help me or recomend a ROM or something?
I just want a ROM that doesnt reboot and good battery life and i can do normal stuff. i dont care about overclocking or anything like that,
Thanks in advance
I would install a stock rom, either stock AT&T gingerbread or ICS for the Nitro and see if it still reboots. If it does, I think you have a hardware problem.
itiskonrad said:
I would install a stock rom, either stock AT&T gingerbread or ICS for the Nitro and see if it still reboots. If it does, I think you have a hardware problem.
Click to expand...
Click to collapse
I would go here first: http://www.att.com/esupport/article.jsp?sid=KB413885&cv=820
This will make sure you are 100% stock. Then if you are still having issues you know that it is a hardware problem. Just make sure you do a full wipe after install.
Sent from my LG-P930 using xda app-developers app
Sparcots miui ics port is the only rom that has zero bugs, black screens, or reboots for me. I've tried everything else.
Sent from my LG-P930 using xda app-developers app
Another potential issue is your SD Card.
I've also noticed lately that my Nitro sometimes randomly reboots. I run with the CM10 Nightlies. The other day, after installing a new nightly, it was really bad, almost constantly rebooting. I took out the battery, removed the SD card and let it sit for awhile (like 1/2 hour or so). Then I put everything back together, reinstalled the nightly and it's MUCH MORE stable now (still randomly reboots, but the instances are much less).
Give that a try and see if it helps at all.
Good luck!
Hi All!
I have LG P936 Optimus true hd with vodafone v20c firmware.
It`s regularly several spontaneous reboots per day. I saved logs with one reboot
03-13 17:03:41.993 F/libc ( 417): Fatal signal 11 (SIGSEGV) at 0x00000001 (code=1)
03-13 17:03:42.404 I/DEBUG (10445):
Click to expand...
Click to collapse
how it can be solved? Help please!
My solution has been to just stick with Gingerbread.. No rebooting, good battery life even with the stock battery, runs all the apps I need.
I do miss ics/jellybean, but I rather have a stable phone with great battery life than a pretty, unstable bleeding edge phone.
If anyone wants to build an awesome gingerbread/ics hybrid.. Then I am down. Lol.
Sent from my LG-P930 using xda app-developers app
Can you tell what happened based on the logs?
two P930s (NItro HD), one with hardware issues
I have two P930s. One of them is much more sensitive to ROM settings and I find I need to limit the CPU to 1200 Mhz or so to prevent random reboots.
The other one works well at full 1500 Mhz speed. This particular model seems to have inconsistent hardware build quality. It makes me reluctant to try any other LG devices (a relative has an LG dishwasher that has also been troublesome, with random shutdowns and error codes).
possible causes
1 - bad sd card
2 - bad flash
3 - unstable recovery .
for me , i have noticed the same , and found it fixed once i upgraded my recovery
1 - bad sd card
its rebooting without sd card
2 - bad flash
its rebooting on two v20c firmware what I used
3 - unstable recovery .
I use official kdz firmware only, not cwm
I' ve got the same problem. I've changed the sd card but it didn't work.
Similar issues here with a Nitro that a friend let me borrow while I'm waiting for parts for my other phone. Random reboots on several different ROM's including stock.
I'm going to try Kernel Tuner and up the voltage a little and see if the phone is more stable. wistlo mentioned limiting the CPU to 1200 Mhz and I think he may be on the right track. If the processor cannot handle being clocked to 1500, which is stock, then a common method (at least with PC's) is to either lower the Mhz or increase the voltage. Or both.
I just tried this a few minutes ago and I'll report back later.
budroid said:
Similar issues here with a Nitro that a friend let me borrow while I'm waiting for parts for my other phone. Random reboots on several different ROM's including stock.
I'm going to try Kernel Tuner and up the voltage a little and see if the phone is more stable. wistlo mentioned limiting the CPU to 1200 Mhz and I think he may be on the right track. If the processor cannot handle being clocked to 1500, which is stock, then a common method (at least with PC's) is to either lower the Mhz or increase the voltage. Or both.
I just tried this a few minutes ago and I'll report back later.
Click to expand...
Click to collapse
My phone was still unstable. I decided to try a stock Gingerbread ROM and it seems to run very, very well.
budroid said:
My phone was still unstable. I decided to try a stock Gingerbread ROM and it seems to run very, very well.
Click to expand...
Click to collapse
Yeah, i remember downgrading to GB to root, didn't use it muchzbut it never once rebooted.
Bought mine last week on ebay brand new (packages sealed and everything), i let it fully charged and started using it.
Came with stock ICS and has been constantly rebooting for the past week.
If i didn't live overseas and didn't have to pay so much money to clear through customs here i would have returned it, but i'm stuck with it and searching for help.
Funny thing is i've gamed on it for hours straight and stability tests for more than 2 hrs and it never rebooted. Then i'll whip out the keyboard to type a message or install an app on play store...or simple web browsing and BAM!....reboots
I've changed to 3 SD Cards even tried without it, still reboots.
All wireless signals off, reboot.
Different ROMS/Kernels, factory reset/wipe, Battery cover off, diff. governors I/Os, Underclocks & Overvolts, tried it all....except going back to GB.
It kind of irks me to know that i came from a GB phone to upgrade to a "new" phone that can only run on GB stable.
It always crashes during some really "stressLESS" stuff, lol. CPU scaling problem maybe?
Also, with no SD Card installed and on boot i get a "SD Card damaged. Try Reformatting" error. Is it normal to get this error with no SD installed?
squatch04 said:
...
Funny thing is i've gamed on it for hours straight and stability tests for more than 2 hrs and it never rebooted. Then i'll whip out the keyboard to type a message or install an app on play store...or simple web browsing and BAM!....reboots
...
Click to expand...
Click to collapse
This definitely makes me think you've got a CPU scaling problem. If you're doing something consistent, like playing a game or stress testing...The CPU will likely stay at a single frequency...But in your case, once you start doing some other activity (which very likely caused a CPU frequency change), the reboot occurs.
Definitely try installing SetCPU and set both the minimum and maximum frequency to something midrange, like 1.2GHz. This way you're locking the phone to a single value (no scaling) and not the max frequency so you won't overload it. Then do what you usually do when it reboots and If the phone stays stable, you'll know the problem is likely an issue with CPU frequency scaling. If it still reboots, at least you've removed one possible reason from the list.
Namuna said:
This definitely makes me think you've got a CPU scaling problem. If you're doing something consistent, like playing a game or stress testing...The CPU will likely stay at a single frequency...But in your case, once you start doing some other activity (which very likely caused a CPU frequency change), the reboot occurs.
Definitely try installing SetCPU and set both the minimum and maximum frequency to something midrange, like 1.2GHz. This way you're locking the phone to a single value (no scaling) and not the max frequency so you won't overload it. Then do what you usually do when it reboots and If the phone stays stable, you'll know the problem is likely an issue with CPU frequency scaling. If it still reboots, at least you've removed one possible reason from the list.
Click to expand...
Click to collapse
It was suggested in another thread that setting the governor to conservative 486 min 1404 max fixed the BSOD, so I tried it and haven't had a single reboot since I posted the last time. I was lucky if I got 30 min before trying it out.
I agree with you, definitely seems to be CPU scaling issue.
Conservative gradually increases the speed compared to the massive min to max spikes you'd get with ondemand.
I will try that with CM10.1 Rc2 with Wind Kernel. I got a few reboot when using my Calendar app for example, while low on battery.
Sent from my LG-P930 using xda app-developers app
radhames562 said:
Can anyone help me or recomend a ROM or something?
Click to expand...
Click to collapse
Try one thing: buy you a new microsd card and see if it helps
salimbaba said:
for me , i have noticed the same , and found it fixed once i upgraded my recovery
Click to expand...
Click to collapse
Tell me, plz, how can I do that? Now I have old 5.8.0.2 recovery. But since I dumped old 8Gb Sandisk and inserted 16Gb Sandisk I now had no reboots. But I want new recovery nonetheless
So after going through ton of different roms/kernels to fix the lag issue that makes my S3 slower than S2, I've finally figured out what is causing it. I can make the phone run smooth if I bump up the minimum freq to above 1ghz. At the moment I'm running 4.3 custom rom/kernel w/o KNOX so the max is at 1.5ghz. I played around with governor and they don't make much difference as long as the minimum has been bumped up. I've seen this happen on stock Note 2 when power saver mode is turned on even with battery on full. What can I do to fix this? I don't want my phone to be in idle at 1ghz for no reason. I will never be able to use the phone for more than 5hrs. Can someone tell me what I can do to make the governor to work as it should?
I've been thinking maybe flashing too many times with different ports could be the cause so I want to flash the stock using Kies but I want stock 4.2.1, not 4.3 with KNOX. How can I achieve this?