Related
Hello all. Kinda new here, but I've been flashing my hero with roms from here for a while now. My latest attempt at a good rom is the VillainROM 12.0.0, this is my first time with a VillainROM, and I don't know if this bug exists in previous versions. In my opinion it is a very minor issue, but maybe not for someone else. I'm not a developer, so I don't know what could be causing it, and I don't know if I should be reporting bugs on the VillainROM site, or here, so I'm going to start here...
I downloaded the ROM from the VillainROM12.0.0 thread...
Install was flawless, worked perfectly.
The ROM runs extremely well in all functions, so no complaints there.
The only issue is a slight (10+ seconds) hang when I press the power button to turn on the screen to unlock it and the WiFi connection has timed out. Other ROMs I've used, including the stock ROM would come out of this sleep mode, and then try to reconnect to the WiFi, and they've done so with flawless success. However, this ROM does not, at least not for a minute or so.
This is how I can reproduce the problem, and it takes a while. I usually plug my phone into a charger at night and let it charge over night, and unplug it in the morning to head off to work or whatever. Once the screen turns on on its own after the external power source is disconnected (which all ROMs have done) the screen is unresponsive, and all buttons are unresponsive. The screen remains lit up on the lock screen stuck for at least 10 seconds, then goes black, then pressing the power button to turn the screen back on will restore the phone to an unlocked state (assuming it remembered the swipe action from when the screen was locked and stuck) but takes about another 5 seconds to come back on. This only happens if I have the WiFi radio on while the phone is sitting idle for an extended period of time (long enough for the radio to automatically go into its sleep mode perhaps?).
Here's the info from my phone...
Firmware Version: VillainROM9.0.0
Baseband Version: 63.18.55.06JU_6.35.09.26
Kernel Version: 2.6.29-ninpo-freqtwk{AT}titan-dirty-b7a296faninpo{AT}titan #39
Build Number: VillainROM12.0.0
Software Number: 3.32.405.1
Browser Version: 3.1
I'm not sure if this is just a fluke, if I should reflash and see if the problem persists. Anyone else able to reproduce this?
Again, if this is the wrong forum, please feel free to move it, and thanks XDA, this site is an awesome resource!
PS... I had to replace the at sign with {AT} in the Kernel Version due to Forum restrictions (It thinks it's an outside URL and I'm too green to be able to do that...)...
Are you running setCPU or OC Widget?
It look likes the lower CPU frequency is too low. Open SetCPU or Overclock Widget and increase it a little.
If you use profiles, in SetCPU:
> Check if you have a "Sleep Profile"
> Check if its frequences are too low.
> If yes, increase it.
It normaly happens when you have a 19Mhz - 2XXMhz on-demand sleep profile.
Increasing that 2XXMhz to 3XX or 4XX may solve the issue.
If not, try to reflash, or use VillainROM IRC at their website.
First your radio is a bit old. Try upgrading to the latest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
Second, especially regarding the wakeup issues, try my kernel for VR12 from here:
http://villainrom.co.uk/viewtopic.php?f=97&t=1928
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Turn up your minimum set cpu speed.
erasmux said:
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Click to expand...
Click to collapse
Pulser has no problems waking up at 19MHz with my kernel. Stable Min/Max frequencies are unique to each phone it has nothing to do with the kernel.
In theory I agree with you completely. But in practice with each kernel I get a different wakeup "performance" using the exact same frequencies. I always prefer setting the min to 160Mhz, but like many many others, in most kernels - including your kernel which comes with VR12 I get heavy wakeup issues which disappear only @ min 480. In other kernels (such as those by Radu) these wakeup issues still exist but are less pronounced (very very rare).
For me and others which have given my kernel a shot there have been no wake up issues @ min 160Mhz. Battery life and responsiveness also improved according to those who have tried my kernel (and optimizations).
BTW "my" kernel is just the HTC official kernel release + OC enable, so its more HTC's kernel than mine.
Like you said it is device dependent, ROM dependent, user dependent, everything.... I am just saying that until now I have not gotten any negative feedback on my kernel, and I think people should give it a shot and decide for themselves. Hopefully they will also be kind enough to share their experiences with me, so if there are problems I can try to fix them.
Thank you all for the suggestions. I do not use any OC utilities, it's the ROM as it was when I downloaded it. Barely any applications installed (some games, auto task killer, handcent...).
I've updated the radio to a version I found in a SenseHero 2.1 thread, but that radio broke MMS and some other data network features. I am in the US, on AT&T (I know, no 3G, but I'm ok with that ), will the radios listed work propperly on this network?
I was also able to reproduce the hanging issue by turning on the WiFi, browsing around the Market, and then exiting the market and turing off the WiFi. It seems that during the switch to the mobile network from WiFi is when something funky happens. Is there a way to get logs to show what might be going on?
First of all try the newest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
If 6.35.15.14 does not work well for you, try either 6.35.15.11 or 6.35.15.01 - If I am not mistaken they are all from the latest HTC release from different parts of the world, so one of them should work well for you.
If you want to get a log for the problem, use the adb logcat. Another simpler option to try and isolate the problem is check if reflashing the ROM (after a backup and a full wipe) solves the problem. Also check if the problem exists in other ROMs.
I have flashed the radio with the latest from the site as suggested (6.35.15.01 was no good when I flashed with that one before, caused all kinds of problems with MMS/SMS, and other network fuctions, but I didn't try that radio with the VillainROM). MMS and such still work, so that is good. I'm going to try to reproduce the other issue tonight, but that may have fixed the issue... I'll update the thread with the results.
Looks like the new radio did not solve the problem. Is the next step the new Kernel?
Sorry for the long delay in response...
The problem is still happening. I have now flashed with a different ROM (Chronos Droid 2.1.2) and the problem persists. However, the lockup doesn't seem to be as bad... Am I the only one with this problem? Should I change my wireless network settings to GSM only? Or leave it on Auto? I'll play around with that and see what happens. It just seems that changing from the mobile network to the WiFi network (and vise versa) is when the problem happens...
Nope, that didn't help. When I went to GSM only, I had no data network connection, and when I went to WCDMA only I had no connection at all. On GSM/WCDMA Only I have both... I wonder if it is something with this phone and the .29 kernel? But then wouldn't everyone here have this problem?
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
I don't see this being a kernel issue, I have a feeling its just a wifi issue on the new rom bases.
m4rk84 said:
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
Click to expand...
Click to collapse
Please let me know what happens.
I did not have these problems using the SenseHero ROMs (older Kernel), only Villain and now Chronos... :S I don't use any OC apps, just leave it all stock from the ROM. If I use one and increase the speed at sleep, (probably an obvious answer) will this drain the battery faster?
Still hanging. Does this have anything to do with wifi's android default sleep behaviour?
I'm having all kinds of lag issues when network queries are starting, especially during MMS/SMS operations. Could be a Handcent update, but the default messager thinger is also quite slow. I'm tempted to go back to an older ROM, this is getting frustrating...
I'm running CM6.1 RC2, and the past couple of days I have experienced excessive drain, mainly in the first 50%. I attached a picture of the issue. I went to spare parts battery history to see the network usage, since in the about phone battery usage cell standby was 84% of the battery usage, and under network usage there was just an entry for 0, using the most network. When I clicked on '0' the settings application crashed. Yesterday it dropped 35% in 2.5 hours, before it slowed down. It was ridiculous, never used to have this problem, and the battery is only a couple of weeks old so it has to be software. Today it is at 53% after 7.5 hours, which is pretty decent, but at around 70% I disabled 3g and background data to save some energy for a few hours. Is there any way of figuring out what is causing this, or should I reflash? Could it be a CM6.1 RC2 bug? Anyone else having this issue? Thanks in advance
BTW I have no idea why the dialer was so high in usage I only had like MAYBE 15 minutes total of voice calls in 2 hours. The 0 is what I'm concerned about.
Anyone? Bump? No one else is having the issue? Still happening to me on RC3.
I've been getting that problem too.
I used to have battery life of up to 4 days (Mostly standby), now I'm lucky if I get 1.5 (Same usage).
I went in to spare parts and it crashed for me too.
Battery drain here too since cm 6.1
Sent from my T-Mobile myTouch 3G Slide using XDA App
Well '0' is he system's ID, 0 is root. In the graph the blue is bytes sent, red is bytes received. Have you checked other usage like CPU usage? That might be a better indicator of what's using your battery. Then from there you can start to narrow it down to a specific process or app. I'm using the latest nightly and don't have that issue, never have. I use a bit more battery than I think I should but nothing crazy.
Do you have wifi or bluetooth on? Those drain your battery like no other.
I havent used wifi at all today, unplugged at around 6:30, it's 3:45 now and I'm at 63%, but from around 9:50 to 11:45 and then from 12:20 to 2:20 I had airplane mode enabled since the time without a signal was at 70%, very low signal area. So it seems like for only 4 hours or maybe 5~ of non airplane mode time I should be at above 63%. I only had wifi on for a half an hour today. I'm considering going back to stock for a few days just to see the battery life comparison, and then nandroiding back to CM6.1. I always end up going back to AOSP-based roms in the end. I don't have a data plan on my phone at the moment, getting it today I'm pretty sure, so could all of the blue be from the phone continuously trying to access a website? But other people said they have the same issue and I'm assuming that they have data plans, so that can't be too much related. Hmm.
I also checked cpu usage and such like you suggested, there were a lot of things listed but all but two of them were too small to even have a bar. The two that did have a bar visible were minuscule to put it lightly, so that can't be an issue. Battery use in the about phone area always has cell standby at the top, normally between 40 and 80%. It would seem like there is way too much cell communication going on, moreso than normal. Cell standby stays at the top in even high signal areas, so it's not the signal levels. Kind of stumped here.
Well if the cell is in standby then it's linked to a tower and awaiting activity. Every now and then it 'checks in'. If it's doing that too often then that could seriously drain the battery. You're right though, I'd just switch back. Trouble shooting the exact issue wouldn't be worth the time. Maybe try flashing it again later, could have just been a corrupt download that didn't flash properly.
After conditioning my battery religiously (full to empty with every charge cycle) I am back up to about 15 to 16 hours from full battery to system shut down which is way better than the 10-12 hours I was getting when I first loaded RC2. CR_OTA ROM gave me up to 24-30 hours off of one charge with the exact CPU/2g/3g/wi-fi "routine" as I am using with RC2. Tracked battery usage with System Panel app and RC2 has a steady and even drain pattern ... an even diagonal line down the graph (100% to 0%). Cell standby uses a ridiculous 40% of the battery from full charge! On the stock ROM System Panel app shows plateaus throughout the day when the phone screen is off/sleeping where battery use is virtually non-existent. I'm going to load RC3 today and track the cell standby and battery usage. This time I am not going to use setCPU and just let the ROM run as the CM team designed it to be used and see if anything has changed. I tried this with RC2 and the battery still trended absolutely evenly from 100% to 0%. I can live with a 16 hour battery cycle for the CM ROM because it is very smooth and never has a glitch. The stock ROM is smooth as well but it has some buggy behaviors that I just cannot stand for and it does not run the latest GAPPS.
I've noticed i have exacly the same problem(was actually gonna post it when i found this thread)
Needless to say that on eclair my battery lasted ~48 hours constantly, not its drained in max 24...
The highest I have EVER gotten was 24 hours, and that was on a cm6.1 nightly build, pre RC2. I loaded cr_mod and experienced a HUGE drain. I had airplane mode on, just to test, and it dropped 7% in an hour, in AIRPLANE mode, with no screen on time. I went into spare parts and looked at the usage, and sure enough, "running" was at the top, with 99% of the time spent without sleeping. This has never happened before though, so I can probably attribute that to my modifications. I deleted a few apk's and de-odexed it before I flashed it, and I have a feeling something I did corrupted something else, so I'll flash plain old cr_mod and see where that leaves me. I should probably get back into the habit of full charge/drain every cycle. I used to do that until my battery started lasting longer than I was awake for, so I always had to plug it in at around 15 to 30%. I'll run some more "trials" and see what's going on.
Also, on an unrelated note, I love the stock rom, I always love the sense UI, but I hate HTC_IME compared to the froyo Latin_IME, is there any way at all I could port the froyo Latin_IME to the eclair stock rom?
Edit: also, I flashed dumfuq's OC kernel over cr_mod, could that have been the culprit to the battery drain?
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
KCRic said:
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
Click to expand...
Click to collapse
Actually, by process of elimination, the kernel was the issue. I remember hearing about there being a bug in the older dumfuq kernels with something idle being null, I really don't remember but it had something to do with sleeping. I flashed pure CR_mod and then 3.5 dumfuq and I experienced the same issue where it wouldn't sleep. I flashed 4.0, but I think it's too soon to determine whether or not the same issue with sleep is occurring.
I tried doing what you said with LatinIME.apk, I even imported the lib file from /system/lib on CM6.1, but the it was nowhere to be found in the system when I booted. It wasn't under keyboard settings, and HTC_IME was gone. I figured it was an incompatibility between froyo and eclair, since the stock sense rom is eclair and the LatinIME.apk is from a froyo ROM. Do I have to something more than just adb push the apk and lib file? I also tried installing it with a file manager, and no surprise, problem parsing the package. It's a system apk so I didnt expect it to be able to install via a file manager. Do I have to use adb install instead of adb push? I'm wondering if htc IME is so wired into the system that it won't work that way. What if I rename LatinIME.apk to htcime.apk or whatever the name of HTCime is and see if that works, because the system may be is treating that as the stock android keyboard, rather than a third party one, because it is labeled touch input in settings, just like LatinIME in aosp roms.
I'll experiment some more I guess
edit: Nevermind, 4.0 is draining as well, albeit less rapidly. Ah well. I guess I'll have to go back to CM6.1 if I want to do overclock. Shame, I love sense so much.
ANOTHER edit: nevermind, you were right, it isn't the kernel at all. It happens when I turn wifi off. I'm assuming that's because I don't have a data plan so it's continually retrying a server that it can't access. I don't know why it didn't do this on the stock HTC kernel, but I'm pretty sure it's the issue. If I turn wifi AND mobile data connection off, it stays at normal drain as well. Well, I'm at 11% and my battery app is estimating roughly 1 hour and 20 minutes remaining, so I don't know if that's GOOD, but I'll give it a good full charge tonight and run it tomorrow. I hopefully will have data activated tomorrow so I can really test it.
Hey guys new to the slide forum but not new to the site. I come from the G1 thread and we had the similar problem. How is your battery life on a 2.1 ROM? I have my phone rooted with a Sense ROM and it has 2.2 and i do see a bad battery drain as well. I remember froyo ROMs battery life may not be the greatest yet. I remember that was always a big problem over there and it looks like it still hurts here. Have you tried setcpu settings?
Maybe this information will help, i forgot to mention last time i posted that i'm not using a HTC device, i'm using Samsung Galaxy S, and there are more ppl with this problem on our forum aswell, so maybe someone can use this information correctly, i mean, it's either a program that's doing this or some strange freaky froyo process that not everybody has? or idk..
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
KCRic said:
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
Click to expand...
Click to collapse
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
MusicMan374 said:
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
Click to expand...
Click to collapse
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
KCRic said:
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
Click to expand...
Click to collapse
Yeah that'd be cool. It must have something to do with that, since it's the cell radio sucking battery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I flashed 6.1.0 stable, battery drain seems to be slightly less. I'm still at around 5 or 10% below where I was at this time on stock, with 9.5 hours off the charger, current level 57%. Although, I did use airplane mode for almost 2 hours, so really I'm like 10 or 20% below where I should be. I just can't figure it out, cell standby is at like 80% usage in this ROM. It's ridiculous, is it the polling intervals or something? How can it be so much less battery efficient than stock?
I flashed 6.1 RC2 with a low battery and had trouble with battery life. TMO's service was acting very strange for a couple of weeks and my cell standby was consuming a lot of juice. Flashed 6.1 RC3 with a well conditioned full battery. At first I used no setCPU just to see how things would go ... 11 hours from full battery to empty. Added setCPU to RC3 and got 27+ hours out of a full charge. Either TMO fixed it's towers or RC3 was better with cell standby because my network usage was not cranking overtime like it had been. Finally, I flashed 6.1 stable with setCPU and I average around 22 to 24 hours on one charge.
One observsation - when I first flashed RC2 I was really into my phone again. I was constantly tweaking it and flipping through options, testing apps, digging new Gapps, etc. ... bottom line I was just using my device waaaaay more than usual and I think that played a huge role in my (supposed) poor battery performance. All seems to be well with 6.1 stable.
Hi all!
Since a few months ago, my Desire has been having two major issues:
- Huge battery drain in 2 to 5h time (unable to identify application responsible, powertutor reports android system or os - can't remember -, while built-in battery usage monitor reports either display or cell standby - the second appears especially when the phone is idle and supposedly sleeping). The few times I enabled airplane mode, I got double battery time, though it doesn't come close to former normal battery time.
- 3G connectivity loss, when going through no signal areas or when the phone is forced to switch between GPRS and 3G and vice-versa.
Regarding the second issue, I've already tried to enable GSM (auto-PRL) and the result is practically the same as having 3G enabled. Only factory resetting after enabling the former setting and choosing GPRS only, in Settings works in no signal downtime.
Nothing I've tried takes care of the battery draining issue, even hard-resets. I've already flashed different roms from Eclair to Gingerbread, from unrooted stock to root stock-based: no real change.
So after this rambling, my question what is more likely either some hardware malfunction or a software bug in the android system or in some application?
Anyway, I'll try to use systempanel or watchdog to try pinpointing the culprit.
Thank you.
Flash latest radio
Also worth thinking about the kernel, I had a similar thing to you, and it was because I flashed a different kernel to the one packaged with the rom.
I would also try a full wipe, ie cache, data, system etc. in recovery and installing something clean eg oxygen rom.
The suggestion above about the radio is definitely worth trying also I would check that your current ril is compatible with your radio version:
http://forum.xda-developers.com/showthread.php?t=902752
Hello! Sorry for not answering sooner.
I have been running the latest radio for at least one month, and it hasn't changed that much the issue.
Also, at some point, I did try another kernel, having seen that suggestion elsewhere in the forums. It also didn't change much.
Finally, I have also tried flashing and using the clean oxygen gingerbread rom. The battery time improved a bit, but didn't go back to normal.
Still, after seeing the results of systempanel monitoring, I will try flashing oxygen rom again because, perhaps with 2.3.4, whatever the issue is, it might have been fixed.
Try to calibrate your battery:
1.) Load phone till full when on
2.) Turn off and load to green led
3.) Turn completely on, turn off and load until green led appears
4.) Boot into recovery, wipe battery stats and now use phone as normal
No warranty for any damage.
Sent from my HTC Desire using XDA App
Did it start when you flashed something new?
Hello!
That is possible. However, I have flashed and formated the phone many times since then and there has been no change.
Also, I have been monitoring the cpu usage through systempanel as suggested in some other threads, throughout the last weeks and in average, there's no installed application going further than 10% cpu usage consistently. When seeing the history of usage, at the top I have the system process, which has an average consumption of 0.2% over one week.
So, the phone seems to be working normally, but when using the currentwidget app to see the current drawn from the battety in each instant, at the best I get 50-70 mA, at the worst I get 700-800 mA. On average, 300-500 mA consistently.
I think something is draining the battery consistently much more than normal and also causing the baseband or the radio subsystem to crash, when switching from 2G to 3G or vice-versa.
I have done everything suggested in this thread, except for flashing a new clean oxygen rom and I've got no result.
What could be causing this: some hardware problem?
Thank you for your patience.
Maybe try the battery in someone else's desire, that you know functions ok, and their battery in yours? Perhaps the battery is dying?
Since I haven't been able to find anyone with an HTC Desire and I can't be certain if the problem is with the battery itself, I'll just send my Desire for repair to HTC.
Hopefully, they'll find and solve whatever the problem is.
Thank you all, anyways.
I own the Sprint Samsung Epic 4G
Twice I have had a problem were after charging over night the phone is hot near the camera area and the phone is extremely laggy. I just power down the device and turn it back on and it works fine again. This has only happened in the span of 6 weeks. My sister has the same phone and she has not encountered this problem. Any suggestions?
Not sure if a reset will fix the problem and I wouldn't even know how to do it.
*Side not the volume will randomly drop down really low and I have to constantly raise the volume. Not a big issue but again after paying money in the amount they wanted I should have to deal with that.*
Somewhere around there is where the SOC resides I think. Would have to look at the pictures of it torn apart again to make sure. You might uninstall your apps one at a time or a few at a time - reboot and see what it does.
You might also go into settings>about phone>battery usage and see if something is using a lot of CPU cycles. Watchdog, OS Monitor, and a couple other programs will list specific apps and processes so you can tell exactly what's doing it. CPU Spy is a great tool to use too - it will show you what speeds your processor spends the most time at.
As far as the volume, you may inadvertently be turning it down. If not, you might root your phone (if you haven't done it yet) and slap on the stock EK02 rom, kernel, and modem. If that doesn't solve the issue then go back to stock EG30 - unrooted of course (sticky thread in the development section for this phone) and return it to the store. It might be a hardware issue.
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