I have searched our Forum for anything on this phone overheating and there is one thread that I came across, but most people did not really have this issue at all. I mean in normal usage doing pretty much nothing my phone holds at 45-50C, given that is with all four cores operating, and if I play a game the cores have reached 70C and up, I am almost certain that is simply too high for this phone to be operating at. Also, even when I use eco mode the phone still idles around 40C and will reach temps as high as 64C. I am just wondering if I am alone or people have actually tested this also and have results similar to mine. I was hoping maybe there might be potential fixes for this or would I need to get a replacement device?
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Pony Express said:
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Click to expand...
Click to collapse
Yeah, I live in Arlington, TX. Yeah, I noticed the self-dim feature, but that happens way too much, and too often, I mean I rarely get to use the phone at 100% brightness and no phone should be like that in my opinion. I am just curious if other people are dealing with similar issues, but I am checking eco mode now and my temps on idle are 36C-38C, its when I actually use my phone as a quad core phone, shocking, that it gets waaay hotter. I mean its hot on the back of the phone when I touch there and when I check the temp with an app. I feel I should be able to use my quad core as a quad core when need be, not have it get so hot its unbearable to hold, plus I don't want to do any damage with it reaching 70C temps.
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
All og's get hot like that when playing games, etc. It is just how it is designed - like it or not / love it or leave it, lol.
I would have preferred they make the phone a little thicker with more heat sink so it could run full speed all the time when needed.
But they didn't. So, oh well. Maybe my next phone will fix that someday.
Jason
Sent from my LG-E970 using Tapatalk 2
Pony Express said:
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
Click to expand...
Click to collapse
Darn, I was hoping for something else, ha. Oh well, guess I will be dealing with that then, meh.. By any chance could you tell me your temps you are getting? So, I know what is normal for the device?
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Pony Express said:
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Click to expand...
Click to collapse
Yes, but this happen on wifi only with data and no sim card installed, I am waiting to get an at&t sim card, lol. Shouldn't have done it online, but it cost 99 cents, instead of $15 bucks in the store.
Good call... hope it helps !!
Pony Express said:
Good call... hope it helps !!
Click to expand...
Click to collapse
Well, the strange thing is that I reverted back to stock everything, no root, or unlocked boot loader, and my overheating issue has been solved.. Weird. I only get around 35C even doing a benchmark with all four cores running at the same time. I think the Base rom and kernels still have some bugs that need to be worked out. I idle at 22C now, woot!
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Pony Express said:
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Click to expand...
Click to collapse
Oh wow, I did not even know that was an issue, ha, well, thanks for the heads up on that and I think I have to send my phone off to LG sadly, according to AT&T, but when I get it back I will be looking into their new base rom, I did skim the thread a little, and I am glad to hear there is no overheating. I am not sure if it was a kernel issue or the base rom itself, which is puzzling.
You may have selected Sk8's kernel during The Base's installation. I can't speak for it myself, but it's different than the stock kernel and may have been causing the problem?
Speculation at best.
No worries, Its what I am doing right now, just speculating, I mean I actually selected both kernels in the base rom, and tested them out. I was trying to figure out what the issue was. I think it might not have left me do a clean install, as I did select Sk8's Kernel first. So, I am thinking that the kernel stuck, even when I did a full wipe, before reinstalling and using the other kernel. I also was getting Kernel crashes, and it kept showing up a kernel crash screen, and asked me to go into download mode to store the dump file on my computer. I am new to android/Linux things, I am far more familiar with Windows based things, but android is the freedom OS of mobile devices. I like the customizations and things you can do with it, lol. Its sweet, and I am learning everyday, so that I can possible become a Dev later on. I have ported some things before and I know other forms of coding, just not the required programming languages for Linux.
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
bleached45 said:
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
Click to expand...
Click to collapse
v1:
- initial release
v2:
- added GPU OC and UV settings
v2.1
- revert GPU settings until i get them more stable
- add voltage control via sysfs (use system tuner to select your custom UV settings)
- fix the black screen issue for alot of users
v2.2
- fast_charge on usb (icon will still show as slow charge but it will actually charge faster)
- cpu tweak to enable use of all freqs in high stress times like games and benchmarks
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Zekk98 said:
v1:
...
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Click to expand...
Click to collapse
Shows what I know, lol.
I was going by what I read for the Base ROM Aroma installer description, maybe the Base is still using an old version, but if you installed it on your own, then you should have been the latest.
Sorry, lol.
Related
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
Okay so I'm not 100% sure if this is a sure fix, but it seems to have worked for myself and my wife. We both were getting random reboots like crazy and it was getting very annoying. I remembered back in my windows mobile TP2 days that a lot of stuff gets stored on the SD card after constant flashing and tweaks. So in order to get a proper flash u normally would have to reformat ur SD card, wipe, wipe, wipe, and then flash ur ROM. That is exactly what I did with my phone as well as my wife's phone. I formatted our SD cards after backing everything up of course. I backed it up on an external harddrive, formatted, put everything back, formatted the phone with a super wipe zip I found somewhere in the development forum, installed a custom stock Rom I have been tweaking and then booted up my phone and have not had a single random reboot since. So as the title says, it is a possible fix. If u try it then please post so that other users can know if it is actually stopping the reboots or if It's just a placebo effect. Thanks and I hope I've helped someone who is extremely frustrated as I was with their 500 dollar phone randomly rebooting.
Sent from my Beastly EVO.. And did I mention it has 3D?
I fixed mine with a buisness card as a shim for the battery lol
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
Yeah my battery wasn't loose at all. My phone would also sometimes freeze up and when I rebooted it would just be a black screen. I had to pull the battery to get it working again. I tried the auto brightness fix bit my screen would go black sometimes and rebooting did not fix. I actually had to pull the battery out.
Sent from my Beastly EVO.. And did I mention it has 3D?
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Truth. I've never had random reboots and the only reboots I've done were solely manual because of these hardlocks from custom kernels.
If only my phone played nicely with kernels...
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
sgt. slaughter said:
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm leaning more towards HTC's screwed up source. As this problem wasn't present in their 2.3.3 source, at least with netarchy's kernel. There weren't nearly as many kernels to choose from but still.
I've heard a few people say the source was either incomplete or messed up somehow. We can only hope that HTC releases an updated software version with a new kernel so that they're obligated to release the source as well, and this time hopefully it will be complete.
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
I used a gum wrapper for mine
Sent from my PG86100 using xda premium
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Lucentio said:
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Click to expand...
Click to collapse
Ur on the exact setup as I am. Kernel and ROM. Stock kernel still did exactly what u mentioned above as well. After formatting my SD card I have yet to have it happen. It's been about 8 days since I formatted. After reading the posts I don't think formatting my SD card is a fix, but I too am leaning towards HTC kernel being messed up. I think sooner or later my phone is going to do it. My phone was doing exactly as u stated. Booting into the splash screen and not going past it. On some occasions my phone would either freeze up or just go black. The hard buttons would light up but not my screen. Hope this gets figured out soon.
Sent from my Beastly EVO.. And did I mention it has 3D?
Mine resets between the hours of 71-80 of being on
I'm having the same problem and I do not know how to solve it! I am so close to selling my Evo 3D and going to the SG II.
I have ran CleanRom and currently running Fresh. I have tried Mwalts kernel, Bcblends kernel, and stock kernel from Fresh stock. No matter what I tried, my phone ALWAYS resets between the hours of 71-80 of being on.
The reset happens only when I try to turn on the phone. It turns on, off really quick, then I hit the power button again, the lock screen comes on, then the phone resets. It is getting really annoying as I love having stability and this phone isn't stable at all.
Any ideas? I have exhausted everything I know. I'm running the exact same programs as I have on the Evo 4G and since it is resetting at the same hours always at the same time on different ROMS/Kernels, I'm pretty sure its not app issue. I also tried changing between the 3 radios and no change there. The only other option now is to do a fresh install of Fresh and use it stock and see what happens.
Rytt
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
ifly4vamerica said:
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
Click to expand...
Click to collapse
already try that
no luck it still keep rebooting while screen off
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
chad.goodman said:
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
Click to expand...
Click to collapse
He said that before you found the magic fix I'm pretty sure. Notice that was back from November. Lol
Sent from my PG86100 using xda premium
Huge Thanks
thank you so much for sharing your information my evo 3d was rebooting about every 30 min and i have just been dealing with it because i had took my evo4g into the sprint store because it was rebooting aboutevery 5-10min so they looked at it and couldnt figure it out so the gave me the evo3d for free and i put the sdcard that was in my evo 4g into my evo3d without having any idea that it was the sdcard causing all of my problems so the same thing started to happen to my new evo 3d started off about every day and eventually started to reboot every 30min and i just decided that all htc devices were like this so i have been dealing with it but today i said enough is enough and looked online and saw this thread and wiped my sdcard and sure enough no reboots yet its been about 3 hours so i think its fixed
i cant thank you enough i think it got corrupt from all of the flashing i was doing
son of a ***** right as i was about to hit post the mother ****er rebooted so its not my sdcard after all should i take it in to sprint what do you think ahhh i should have never posted anything it was going so well FML!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ps hboot 1.4 is the **** no more going to the computer to flash a rom stupid hboot 1.5
I've sometimes had trouble running custom kernels (reboots and strange behaviors) that were fixed when running the stock kernel. But, the stock kernel leaves a lot to be desired in overall performance, so I continue to kernel hop. But, from my lurking on the different ROM forums, it seems that stock is the way to go for stability at the sacrifice of performance.
I had problems with evo rebooting and that in a loop. Very annoying. For that i've changed several roms just to find out that it could probably be because of widgetsoid.
At first the rebooting after some time of use, 1-2 days. And if flashing a different kernel than the one with rom. I was going mad, the last reboot or series of constant reboot after the evo has turned itself on, has occured after i set the brightness to lowest value, it was late so i wanted a darker screen. Interesting it when i set lowest value in system or via leedroid tweaks in widgetsoid widget popup - value im at 12 %. Maybe i got the restarts because i went below 12? Since my brightness im above 12 in widgetsoid and minimal in system, my evo didn't reboot a single time.
Currently i'm at shawn3d rom. Later i'll try some other kernel and rom again and see if the reboots occured.
U get random reboots while using any brightness widget with custom roms. I've narrowed my 3d threshold for the reboots to be anything less than 5%.
No reboots if kept at or above 5% for me...
Sent from my PG86100 using Tapatalk 2
i have had success after formatting system/data/cache to ext4 in the ext4 recovery, i had random reboots and lockups while using twrp and not formatting to ext4, (in all honesty i doubt the twrp was too blame)
I'm running JT's vanilla GB [over Heimdall'ed stock EH03] on my fascinate.
I use my fascinate as my alarm clock, and I woke up this morning to a extremely choppy ringtone. < and that is is the understatement of the day.
Anyway, I try to press "dismiss" to dismiss my alarm, and it feels like the screen is not responding. I press the power button, and it takes probably like 5 seconds to complete the CRT animation. After that, I can see the screen is still on (hard to tell unless in the dark with the AMOLED), and it won't do a thing after that until I 3-button-combo or take out the battery.
As a side note, it was also doing this on my previous rom, SuperClean3 v8.1. One of the main reasons I switched back to JT's vanilla gb.
The first night the alarm worked fine. [2 days ago] Yesterday, I was watching some video files, I pressed the power button, I left for a few minutes, I came back and it was frozen. [Took foreverrrrrr for the CRT turn-on animation, and screen did not respond].
This is really really annoying, and I would really like to find out what is wrong with my phone.
One more thing I should mention.. this same kind of thing happened once in a while on the stock froyo firmware, when I bought it on craigslist. I would come to it sometimes and turn it on, and the lockscreen would show and the touchscreen wouldn't respond. I had to take the batt. out then cuz I didn't know about 3-button-combo.
The USB would only charge and not transfer files and only would charge.
So I sent it in cuz samsung said I had 1 mo. warranty left, and then they said they fixed everything in the ticked, and I got it back and it seemed to work. [the usb file transfer worked..]
So can anybody give me any advice? Like logcat? Would that tell me what is causing this problem?
Any help is appreciated!
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
k_nivesout said:
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
Click to expand...
Click to collapse
Thanks for the reply. I will look into this 'sleep of death' thing.
And I haven't edited my cpu settings. I went to superuser to be sure and the only apps listed are Superuser, Terminal Emulator, and Titanium Backup.
So I just went on a 1-hour trip, and when I got to where I was going, this happened to me again. The screen-on animation was slower than a slug on salt. 3-button-combo reset, I let it reboot, and it was fine.
I just got home 1/2 hr ago and it did it again.
Sigh.. well I only have like 2 apps that always run, 3G Watchdog and Equalizer. I've uninstalled 3G WD just to see if it does anything.
Edit: I will install ROM Manager and set the absolute minimum freq to 200mhz, and see what happens. That would make sense if it's messing up at 100mhz when the screen goes off, and then it's not able to think fast enough to up it back to 1ghz.
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have much expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
k_nivesout said:
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
Click to expand...
Click to collapse
My bad, I meant ROM Toolbox. It has lots of apps built in including a CPU slider. Anyhow disabling 100mhz did not fix anything. So tonight I will set the minimum frequency to 800 or even 1000 mhz because I want to see if that stops the freezing up. If it does, then I'll know it's a clock speed issue.
I should also mention I sent it in for USB repair. It wouldn't connect to PC, it'd only charge. I also mentioned to Samsung it would lock up every so often from waking up. They upgraded froyo to gingerbread and said it passed all tests, sent it back, I never stayed on the firmware they gave me long enough to see if it froze up.
So on the stock roms, do they underclock the cpu frequency by default??
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
k_nivesout said:
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
Click to expand...
Click to collapse
Lol, when I sent it in there was like half a month or so left on the warranty, the person said it expires at the end of this month [Dec] so I figure maybe a day or two.
What's the IRC channel info? freenode?
EDIT: I forgot to ask something. So you are saying, the stock firmware [EH03 or froyo EH09] runs the cpu clock constantly at 1GHz? Even when it's sleeping? Wouldn't that give bad battery life? [lol, speaking of batteries, I just got a new one and it's charging]
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
gotsflat4love said:
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
Click to expand...
Click to collapse
This is bad news indeed, since I am not even sure how many days I have on the warranty. But I think I will Odin EH03, and then set the alarm tonight. If I wake up and it's done it again, I will call up samsung and tell them and hopefully I have warranty.
But please, tell me, when you tried to turn on the phone did the CRT animation go very slowly? and then when you pressed power, it wouldn't come on again?
Edit 2: alright! I call samsung and I have warranty until Jan 9. Woot.. So I set up an RMA with samsung, I will Odin EH03 tonight. If I wake up to a choppy alarm and a non-responsive screen, I shall send it to samsung ASAP and I hope they gimme a brand new Fascinate. that would be awesome..
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
k_nivesout said:
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
Click to expand...
Click to collapse
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
So this morning, I woke up to my iPod's alarm, which I had set as a backup a few minutes after my Phone alarm should have gone off. I went to see if the phone was frozen, like I was hoping, so that it would reliably broken , but instead it was off. I turn it on, it shows the full green battery.. then it boots up like nothing was wrong. But I think that turning off randomly every night [which I assume it should do every time] is enough for Samsung to realize my phone really is screwed and that they need to do something about that.
So anyway, I printed out the label, packed my phone, and dropped my phone off at the local UPS drop off.
Hopefully I will be receiving some good news from samsung soon [i.e. that they will give me a replacement... ]
mvmacd said:
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
Click to expand...
Click to collapse
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
k_nivesout said:
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
Click to expand...
Click to collapse
1. I'm not the original owner
2. I'm not a Verizon subscriber. PagePlus Celluar [A verizon MVNO] is my service provider. They have much better plans, including monthly, and prepaid, if you ask me.
Kernel issue.
sent from my Sensation XD
Yess..
Good news! Got an email saying my phone has been shipped:
Code:
Original Problem:
TECHNICAL INQUIRY - PHONE FREEZING / LOCKED UP - FREEZE/DELAY BETWEEN MENU FUNCTIONS
Problem found:
BAD BGA COMPONENT
Solution:
REPLACED PBA
I guess the PBA is basically the motherboard? I suppose that could have been the cause of overnight freezing, and so my phone should be fixed.
Nice.. Just 2 days left on my warranty. Cutting it kinda close, I know lol
Very well done sir
sent from my Sensation XD
Alright So here it goes:
Problem: EVO 3D CDMA version constantly locks up when in a screen off state, making it where the unlock button does not work. (Holding down Volume -, Volume +, and Power reboots it) which can mean that it doesn't lock up it actually shuts off..maybe.
What I've tried: Somebody gave me the idea to take the 2.08 RUU and go back to stock, take OTA for 2.17 and reroot and unlock the bootloader using HTC's method (keep in mind i've been on hboot 1.5 the entire time). This didn't seem to help (although did fix a random reboot problem, but besides the point.)
I have also tried uninstalling any application relating to the Prox. Sensor (explanation in notes below)
Notes: I believe everytime that I have seen the issue, the screen has been locked and the phone has been put in my pocket. It virtually never happens when it is out in the open which leads me to believe maybe something with the proximity sensor.
Also this does not seem to be specific to any ROM, Although I have not flashed an AOSP ROM as of yet
Any ways any advice would be appreciated, because as you know a mobile device does spend quite some time in your pocket and it would suck to keep having to reboot it everytime I take it out.
even if you can't provide advice, thanks for reading
almost sounds like it would be a hardware issue with the power button itself... have you tried pulling the battery out and booting into your fastboot screen and into the rom itsself?
ther have also been reports of the handset itself being too warm for it to function...maybe try keeping it out in the open and then unlocking it and see how it works from there... post your results please... im curious now
wloftus said:
almost sounds like it would be a hardware issue with the power button itself... have you tried pulling the battery out and booting into your fastboot screen and into the rom itsself?
Click to expand...
Click to collapse
Yea I can do that easily. The power button works fine, I can keep unlocking/locking whenever, it's just whenever I lock the screen and then put it in my pocket, 95% of the time it tends to lock up (or shut off idk what exactly is going on yet) and then performing a hard reset or taking the battery out will boot it back up
see my edit about the over heating... you responded before i could post it fast enough lol
I had a similar issue. It turned out to be an app. In my case, opensignal maps which is a cell tower and WiFi location app.
Sent from my Clean and MeanROM 3D
wloftus said:
see my edit about the over heating... you responded before i could post it fast enough lol
Click to expand...
Click to collapse
Oh ok, Idk if that could be it. Using it I can leave it out in the open for hours (with wifi tether running and it charging at the same time) and it will unlock and function fine.
but without all of that, 5 min in my pocket and done, I get the lockups/shutoff
guitardoc64 said:
I had a similar issue. It turned out to be an app. In my case, opensignal maps which is a cell tower and WiFi location app.
Sent from my Clean and MeanROM 3D
Click to expand...
Click to collapse
Yea I thought it might have been an app, but ive uninstalled every app I could think might cause the problem so I don't know I can't rule that out though
notsointeresting said:
Oh ok, Idk if that could be it. Using it I can leave it out in the open for hours (with wifi tether running and it charging at the same time) and it will unlock and function fine.
but without all of that, 5 min in my pocket and done, I get the lockups/shutoff
Yea I thought it might have been an app, but ive uninstalled every app I could think might cause the problem so I don't know I can't rule that out though
Click to expand...
Click to collapse
i run the wifi tehter app as well and it will heat up your phone substantially putting in your poclet can be insulating it and then your body heat building it up further... but if you leave it out of your pocket and it performs fine... i would definitely explore that route....
wloftus said:
i run the wifi tehter app as well and it will heat up your phone substantially putting in your poclet can be insulating it and then your body heat building it up further... but if you leave it out of your pocket and it performs fine... i would definitely explore that route....
Click to expand...
Click to collapse
Yes it does, but I most definitely don't run it while in my pocket or in another concealed area. I was just giving an example of when it would be substantially hotter than when in it is in my pocket
notsointeresting said:
Yes it does, but I most definitely don't run it while in my pocket or in another concealed area. I was just giving an example of when it would be substantially hotter than when in it is in my pocket
Click to expand...
Click to collapse
it for sure does not heat up too much running the tether but the insulation of your pocket can be causing it... tether on monitors the battery temp... not the internal temp of the phone itself ... id be more inclined to lean to it over heating
wloftus said:
it for sure does not heat up too much running the tether but the insulation of your pocket can be causing it... tether on monitors the battery temp... not the internal temp of the phone itself ... id be more inclined to lean to it over heating
Click to expand...
Click to collapse
And I could go with that, but compared to using things like Wifi Tether I can tell it gets a lot hotter than when I take it out of my pocket and notice it won't turn on.
And I mean 2-3 Minutes and it locks up ,which is why I said it might be tied into the proximity sensor, and it hasn't been in my pocket every single time, but like 95% it has.
notsointeresting said:
And I could go with that, but compared to using things like Wifi Tether I can tell it gets a lot hotter than when I take it out of my pocket and notice it won't turn on.
And I mean 2-3 Minutes and it locks up ,which is why I said it might be tied into the proximity sensor, and it hasn't been in my pocket every single time, but like 95% it has.
Click to expand...
Click to collapse
againt you MAY be right.... i wont negate that... but the battery temp and the phone temp settings are totally different ill leave it at that bc thats all i can come up with but like i said again... you may be right... i still think it is an overheating on the core hardware of the phone itself....
what ROM?
what kernel?
any cpu control apps?
list of root apps?
il Duce said:
what ROM?
what kernel?
any cpu control apps?
list of root apps?
Click to expand...
Click to collapse
Currently using MeanROM, but have also seen the issue in my time using, CleanROM Reborn, and Eternity 3.0.
Always stock OTA Kernel at stock clock speeds.
There have been times when I have used SetCPU and times when I haven't, never a difference.
Root Explorer, Titanium Backup,SetCPU,SuperUser (of Course), Wireless Tether App,
notsointeresting said:
Currently using MeanROM, but have also seen the issue in my time using, CleanROM Reborn, and Eternity 3.0.
Always stock OTA Kernel at stock clock speeds.
There have been times when I have used SetCPU and times when I haven't, never a difference.
Root Explorer, Titanium Backup,SetCPU,SuperUser (of Course), Wireless Tether App,
Click to expand...
Click to collapse
fyi it's quite possible those ROMs set a LOW minimum (sleep) frequency, which SOME devices don't like. stock (like HTC stock) is 384000, but a LOT of devs set theirs to 192000 to conserve battery.
check here and report YOUR value:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
if it's 192000 that's likely your problem, set it to 384000. if it's already 384000 then it's something else, you ever looked at the scripts you have in init.d and what they're doing?
EDIT: and if you REALLY wanna know what's happening and what's erroring, hook up adb and watch the log, pull a last_kmsg, dmesg, etc. Maybe it would help narrow things down
il Duce said:
fyi it's quite possible those ROMs set a LOW minimum (sleep) frequency, which SOME devices don't like. stock (like HTC stock) is 384000, but a LOT of devs set theirs to 192000 to conserve battery.
check here and report YOUR value:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
if it's 192000 that's likely your problem, set it to 384000. if it's already 384000 then it's something else, you ever looked at the scripts you have in init.d and what they're doing?
EDIT: and if you REALLY wanna know what's happening and what's erroring, hook up adb and watch the log, pull a last_kmsg, dmesg, etc. Maybe it would help narrow things down
Click to expand...
Click to collapse
It was set to 486mhz
And I was going to pull a logcat, but since this seems to happen when in a pocket for some reason its hard to keep it connected to a cable lol, but ill try the others
seriously the most simplest of answera isa the one over looked.....it sounds too basic and the rest are over delving in to the matter sometimes the right answer is tho most simplest.....
wloftus said:
seriously the most simplest of answera isa the one over looked.....it sounds too basic and the rest are over delving in to the matter sometimes the right answer is tho most simplest.....
Click to expand...
Click to collapse
Well I think im going to go back to stock unrooted via RUU for a couple days, this will be the most obvious way to figure out if it is an overheating/hardware problem.
But in using the device, and seeing the conditions this problem arises in , it just doesn't feel like it. but hell you might be right lol , we'll see
notsointeresting said:
Well I think im going to go back to stock unrooted via RUU for a couple days, this will be the most obvious way to figure out if it is an overheating/hardware problem.
But in using the device, and seeing the conditions this problem arises in , it just doesn't feel like it. but hell you might be right lol , we'll see
Click to expand...
Click to collapse
Have you made any progress with this? I think I have the exact same problem you have. At first I thought it was because of the pocket, but now I figured out it only freezes if the screen is turned off and the phone is not connected to a charger.
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
sharky17 said:
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
Click to expand...
Click to collapse
I recently had the same problem. It would overheat constantly, especially when playing a game, and if you charged the phone and tried to use it at the same time, it would only overheat faster. I got my phone when it first came out as well. The tech made up something about a short in the power button, but they did end up replacing the phone for me. You'll have to go back to complete stock of course before bringing it into the sprint store. If you need any assistance getting your phone backed up or back to stock, shoot me a message.
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
sharky17 said:
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
Click to expand...
Click to collapse
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
chris674 said:
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
Click to expand...
Click to collapse
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
sharky17 said:
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
Click to expand...
Click to collapse
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
DXtremz said:
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
Click to expand...
Click to collapse
I would flash with the stock Rom and bring it back to Sprint. If u guys underclocked it and it still overheats, then I would think it is a manufacturer's defect. It doesn't make sense that the phone will still overheat with the cpu being underclocked.
Chris