Related
Hi there,
First of all, I've read several threads about this subject trying stuff and hoping to find a permanent solution.
Second, my Desire info:
Android: 2.2
Rom: Rooted AMOLED HTC Desire Sense stock
Radio: 32.49.00.32U_5.11.05.27 // latest official.
Kernal: HAVS 2.6.32 for Sense Roms V5f
Softwarenumber: 2.10.405.2
Third, app's I've installed.
Advanced Task Killer (using before problem already.)
Astro
Barcode Scanner
CPU Tuner
Geenstijl (news feed)
GPS Status
Meebo IM
Move2SD Enabler
NU (news)
Rom Manager
Quadrant Advanced
Pingchat
Whatsapp
Otherwise, stockapps and some stock apps removed.
Now the problem. This did not happen on unrooted phone, did not happen before flashing radio and kernal.. seemed ok with these aswel, problems came 2 weeks after flashing radio and kernal.
I happen to notice that when the battery drops below 50-40 % it'll get very slow, unstable, not responding and eventually rebooting itself.. This has happened for around 4..5.. times now. In 2 cases, I had to remove the battery, let it cool and try again. Yesterday the area around the sd card got very hot and let it cool down with the back cap off.
Could the radio, and possibly kernal have anything to do with it? The kernal has overclocking though. Or would these problems disappear when I reroot?
I hope this is enough info.
Hoping to get an answer or solution! thanks.
It's probably because of the kernel.
Flash another one, preferably without OCUV stuff, and see how it goes.
I think i've found a reason / solution in another thread. Most likely reason will be CPU Tuner profiles.. when battery get's low.. it stood on extreme powersave.. changed this, and will report with results..
Yeah it might be, if the app "tells" the phone to decrease the voltage or increase the cpu frequency too much.
I bet you're suffering from the same overheating problem as every other Desire owner will suffer from. (if you bought it during summer and before)
prodygee said:
I bet you're suffering from the same overheating problem as every other Desire owner will suffer from. (if you bought it during summer and before)
Click to expand...
Click to collapse
A friend of me has it aswell.. but I bought it in august.. and didn't had any problems before.. but there's no solution for this?
It looks like ive got the same issue...
Im also using the latest radio and lambros r4 rom.
But im not using any cpu frequenzy stuff and also happens with miui roms
Is there any solution for this?
Sent from my HTC Desire using XDA App
ROM: Virtuous 1.0.2
Kernel: Virtuous Advanced 2.2.0
I'm having trouble with my screen struggling to turn on when I wake my phone if the cpu speed is anything above stock. If I push the power button once the capacitative buttons light and nothing else happens, if I push it a second time the lights turn off again and I briefy see my lockscreen flicker before my pained eyes
If I do this cycle many times over eventually I'll get lucky, but there's no pattern to the success and it's very frustrating.
The symptoms are similar to this thread: [Q] Phone unlocking screen issues. The method described there to solve the problem was to turn off on/off animations. I don't think this solution applied as I'm not using CM7.
I think the touchscreen input is recieved despite the screen itself having no picture - for example I can unlock my phone by swiping down (stock Sense lockscreen). If I touch the touchscreen in the right place to open the dialer while I've "unlocked" it in this way, when the phone finally wakes after frantic power button pushing, the phone will be in the dialer app.
I think it might be related to Sense as I tried a stock Sense from rmk - [ROM]Vision_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_12.5 0.60.24_26.08.04.16_M and overclocked using both Virtuous Advanced 2.2.0 and Pershoot's Kernel. In both cases I also had wake issues any time I tried to wake when the cpu was clocked above stock speeds (even 900MHz).
Further evidence towards a sense problem is that I don't have any issues when I'm at 1.4GHz when using CM7. I missed the sense apps too much to stay with CM7, however.
I have a workaround using CPU Tuner with a screen off profile of 246-806 Mhz, and I can then overclock freely afterwards. I can live with this but if anyone has an idea why this might be happening then I'd appreciate a solution.
As I've been lurking on XDA for a while but this be my first post, thanks to all you incredible developers who have made it possible for me to customise my phone in these fantastic ways.
Set your screen brightness to something greater than 50%. It's not a fix but a very reasonable workaround .
Sent from my HTC Vision using Tapatalk
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
The screen off issue is thoroughly discussed in the Virtuous kernel thread. I forget the exact explanation, but its got something to do with the CPU stepping while the screen if off.
The common fix is a SetCPU/CPU Tuner screen off profile, as you seemed to have discovered. But adjusting the governor type in addition to minimum CPU clocking seems to be the common solution used. I think the interactive governor seems to work best to prevent screen wake issues.
http://forum.xda-developers.com/showthread.php?t=967153
Yeah, I read that thread fairly extensively but the solutions there didn't help. I can easily replicate the problem by setting my cpu with the performance governor to anything above stock speed (i.e. the cpu will be at one single speed the entire time, I think?). The over 50% brightness solution works very well (at the expense of more noticeable battery drain)!
Atomcracker said:
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
Click to expand...
Click to collapse
I had seen the workaround mentioned on the CyanogenMod forums yesterday: http://forum.cyanogenmod.com/topic/20943-screen-doesnt-always-turn-on-from-sleep/
I have a Telus HTC Desire, S-OFF, CM7 r2 HBOOT, running RCMix S (tested with both 2.0 and 2.0.1).
On a recent road trip, using Navigation, after about 30 minutes on the road, my Desire rebooted. After taking it off my universal mount, I felt that the lower part of the phone was very hot. I have done numerous other tests with Navigation (mobile data on, bluetooth connected to car kit, obviously GPS on), and it keeps overheating within 20-30 minutes usage.
I've read a few threads here about Desires overheating when using the GPS, I was wondering if any other Telus users have experienced this problem?
After many overheats, I decided to put my Desire back to stock to warranty it (I've heard the motherboard needs to be changed..).
I am now S-ON, stock HBOOT, and back to a Telus RUU. Now I can't seem to make the phone overheat under the same circumstances.
So I'm wondering... Is it because of the RCMix S rom (overclocking??)? Should I still try to warranty it? And have any other Telus users experienced similar (with stock rom or otherwise)?
Any help or advice is appreciated, thanks.
guitarguy said:
I have a Telus HTC Desire, S-OFF, CM7 r2 HBOOT, running RCMix S (tested with both 2.0 and 2.0.1).
On a recent road trip, using Navigation, after about 30 minutes on the road, my Desire rebooted. After taking it off my universal mount, I felt that the lower part of the phone was very hot. I have done numerous other tests with Navigation (mobile data on, bluetooth connected to car kit, obviously GPS on), and it keeps overheating within 20-30 minutes usage.
I've read a few threads here about Desires overheating when using the GPS, I was wondering if any other Telus users have experienced this problem?
After many overheats, I decided to put my Desire back to stock to warranty it (I've heard the motherboard needs to be changed..).
I am now S-ON, stock HBOOT, and back to a Telus RUU. Now I can't seem to make the phone overheat under the same circumstances.
So I'm wondering... Is it because of the RCMix S rom (overclocking??)? Should I still try to warranty it? And have any other Telus users experienced similar (with stock rom or otherwise)?
Any help or advice is appreciated, thanks.
Click to expand...
Click to collapse
I have the same problem. I'm not on Telus, obviously, since I'm from Serbia. I'm on Telenor. Every rom i tried, including the mentioned RCMix S, LeeDrOiD, Cool Sensation, Cool Sense, Cool BravoS v1, and even Oxygen and dev null. Everytime when GPS is working, it just overheats and restarts. Maps or navigation working or not, it just restarts and loops until i pull out the battery and let it cool down. Does anybody know the solution to that?
Some help would really be appreciated.
Just a quick reply here for you guys,
I'm on Telus as well an have done numerous road trips with my Desire. Nav (GPS) running, music to car speakers through bluetooth, and the odd call to my Wife, fuel log entry etc.
I did notice the phone get warm but what concerned me was the phone not charging.
There is a thread on here about it, and after a quick search I couldn't find it so I take no credit for this but:
The thread pointed out that sometimes the desire, when plugged into an AC outlet in car mode would not go into ac chrge mode (1 ma charge). It would go into usb charge mode instead. Because of this the battery would run down quickly. The solution was set up your phone, once in it's cradle, leaving it plugged in power down.......wait.......reboot.....and it would then properly enter ac charging mode.
I tested this and it works, after an 8 hour BC road trip with everything running (and screen max brightness the whole time) my battery was still 100%, and as well my phone was not hot.
Can't remember if this was a gingerbread issue, custom kernel issue, etc. Like I said, quick response, I would have to search more to provide a more detailed answer.......but try this anyways.
I have a Telstra gsm desire running runnymede 5.3 with latest snq kernel and get the same prob. Have tried lots of roms only one that navigation works on without overheat reboot is miui roms. Shame cause I really like sense 3.5, and runnymede 5.3 is amazing smooth and fast so would love a fix for this bug.
My HTC Wildfire often shutdown while I'm using my phone especially but not limited to browsing and visiting the Android Market.
When I reboot my phone after the random shutdown, my battery level drain out even the battery is full before the random shutdown. I then shutdown my phone and switch on it after a few minutes, the battery level came back to the initial level, i.e. 75%. And if I switch on with my phone plugged, It switch on with 100% battery level.
I first encounter this problem after I had installed Go Launcher EX on my phone. The problem continues after I uninstalled Go Launcher EX and using LauncherPro.
Now I had rooted my phone on CM7 and this shutdown still haunts me, please advice.
Do you use a cpu manager?
If not, please check settings/cyanogenmod settings/performance/cpu/ What does it say?
does it shutdown, or does the screen simply turn black, while the led lights, remain on?
to be honest here, it sounds a LOT like the power issues on the HTC Touch Pro2.
While that device ran Windows, as to android on your device, it seems like there might be a cross-os programming error on these devices.
could you also check if this mainly happens when you were suppose to receive an sms or incoming call, while also using the internet?
If so, i think i might know where to look for a root-cause of this problem.
calyxim said:
Do you use a cpu manager?
If not, please check settings/cyanogenmod settings/performance/cpu/ What does it say?
Click to expand...
Click to collapse
I overclock my phone to 710Mhz and restore CPU settings on boot, Current governor is performance.
tazman998 said:
does it shutdown, or does the screen simply turn black, while the led lights, remain on?
to be honest here, it sounds a LOT like the power issues on the HTC Touch Pro2.
While that device ran Windows, as to android on your device, it seems like there might be a cross-os programming error on these devices.
could you also check if this mainly happens when you were suppose to receive an sms or incoming call, while also using the internet?
If so, i think i might know where to look for a root-cause of this problem.
Click to expand...
Click to collapse
It turns off completely. Most cause of the shutdowns are Internet browsing and visiting android market, no calls and messaging were made nor receive that time. However, the shutdown doesnt happen when I charge my phone. So is my battery faulty?
I found that when I overclocked my phone shut down and randomly rebooted. I had to drop it below 700 for it to be stable.
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
heavy_metal_man said:
I found that when I overclocked my phone shut down and randomly rebooted. I had to drop it below 700 for it to be stable.
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
Click to expand...
Click to collapse
But this nightmare haunts me before I root my phone, and it doesn't reboot, just shutdown
Then it may be a hardware problem. If it was a software issue a new rom should have fixed it. Have you got a warrentee? You may have to use it, but remember you may have to flash stock and s-on again or they might not accept it.
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
heavy_metal_man said:
Then it may be a hardware problem. If it was a software issue a new rom should have fixed it. Have you got a warrentee? You may have to use it, but remember you may have to flash stock and s-on again or they might not accept it.
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.
Click to expand...
Click to collapse
I had already purchased a new battery online. Just waiting it to reach my door step and I will check whether my battery is faulty or not. Thanks
ok good luck
I had the same problem with the phone i used before my wildfire, it's a SonyEricsson, have no idea what's the problem either
Using go launcher at the moment and apart from random restarts I don't have a problem like this. But then again I haven't played with the CPU settings yet. Also I know I'm a newb but you could try recalibrating the battery if it's displaying false statuses
Sent from my HTC Wildfire using xda premium
Reisen Udongein Inaba said:
Using go launcher at the moment and apart from random restarts I don't have a problem like this. But then again I haven't played with the CPU settings yet. Also I know I'm a newb but you could try recalibrating the battery if it's displaying false statuses
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Done battery calibrating but then phone shutdown itself during the process, I think might be the battery causing it.
I asked the sales person in a HTC store regarding this, might be hardware or faulty battery
I'm having exactly same issue. Did you solve it replacing the battery?
The problem solved!!
Yes, replacing the battery really does solve the problem
Below is the link to the battery I purchased. It's a third party extended battery with additional 200 mAh compared to the stock battery.
http://www.ebay.com.my/itm/New-YOOB...AU_MobilePhoneAccessories&hash=item19c5f6c3d3
marcostvz said:
I'm having exactly same issue. Did you solve it replacing the battery?
Click to expand...
Click to collapse
I don't know if a calibration would be able to solve your problem. I.e letting your battery be completely drained and recharge it to 100% while it's turned off, and do it again 2-3 times.
Sent from my HTC Wildfire using Tapatalk 2 Beta-5
Hi everyone,
I just flashed ARHD 7.0.2 on my Desire HD last night and I'm experiencing the following problem:
The CPU remains at 99-100% all the time, the battery drains excessively fast and the phone gets really hot.
Using "Watchdog Lite", I detected that when the CPU does not stay at 100% (after a battery-pull), the "Phone" process uses 0,0% of CPU.
However, for some reason, after a while it will jump up to 80-90% and stay there, causing the CPU to go berserk.
I suppose the heat-issue comes from the fact that the cpu works all the time at 100%.
The battery drain issue comes also from the CPU.
However, I do not know why the Phone process would suddenly go crazy and use that much cpu - and keeps doing it until the battery is dead.
I'm thinking it is because the ARHD 7.0.2 ROM is actually a stock Sensation XL base and thusly requires another RIL than the one that was on it before that.
Before flashing another RIL or radio I would like it very much if somebody could confirm that the fact that the Phone process goes crazy like that could very well be linked to the fact that the RIL and Radio don't match.
It seems obvious, but I don't know enough of the inner workings to verify this, so therefor: this thread
Thanks in advance to all!
sstm
The RIL should be pretty standard between HTC devices so that shouldn't cause any issues. Did you do a full wipe before the install?
Hello TransientMotion,
Yes I did a full wipe, I even cleared the battery stats for good measure.
I even formatted my SD-card to make sure nothing remained from some app somewhere.
The phone is as if I'd have bought it fresh out of the store with ARHD 7.0.2 on it (and rooted of course)
It's just weird to see that the "Phone" process is using this much cpu, even when on Airplane mode.
Thanks for you reply,
sstm
It may be worth trying out an earlier version of the rom just to see what happens. I used 6..3.1 before I switched over to ICS and never had any major problems with it. If that works fine then try newer versions until you get glitches again or it works without the drain
Hey,
I just found out that it is Llama (kebabApp 'location aware' application) who is causing the problem.
Whenever I leave an area and then re-enter it, the CPU goes berserk and stays that way as if some loop can never be interrupted.
I didn't have this problem on ARHD 6.3.1, but I didn't have the same Llama configuration on it either so I tried the Llama config on ARHD 6.3.1 and it did the exact same thing: cpu 100% and slowness all over.
So conclusion: Llama config is the culprit.
Anyways, thanks for you help TransientMotion.
sstm