Develop Bugs

VillainROM 12.0.0 Wi-Fi system hang...

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...

[Q] [solved] Suddenly, horrible battery life out of nowhere

Hey guys,
I have been trying to solve this on my own for two days now, but I would like to consult the forum now.
So, I was running Pink Sense 1.8 for about 2 weeks with setCPU profiles and was getting satisfactory battery life. I had re-calibrated the battery info maybe 2 weeks before flashing the Pinky ROM (as described here: http://forum.xda-developers.com/showthread.php?t=755903).
All of a sudden, without any app installation or change to either the ROM or software/hardware settings I started getting horrible battery life. The battery would drain completely for less than 6 hours with GPS, 3G, and WiFi off.
*Another strange thing (which I don't know if it was related to my battery issue or not) was that when I would plug the charger it would turn the screen on but switch to the default clock app instead of the HTC sense homescreen. If I pressed home or back it would disappear. This would happen randomly and not always.
So, I figured it's time to jump ROMs and I decided on LeeDroid. I wiped cache, etc. and flashed the ROM. Out of the box the battery life was again pretty crappy (the battery was virtually disappearing in front of my eyes). I found some threads where it was suggested to disable market notifications and that slowed the battery drain a bit but it's still crappy.
I just charged it fully, 3G and WiFi off, and was with the screen off for 99% of the time and it still drained 18% battery in 1hour and 25 mins.
So, my question is - what the hell is going on???
Should I wipe battery info? Should I install a non-WiFi n rom? What more can I do?
I would really appreciate help and advice.
p.s. I am running the latest radio too.

wich radio have you the .23 drains the batery with my desire try with the .30_2
the battery life is better.
did you try reboot your phone maybe your optical joystick dead and drain your battery.

load any new apps recently?

cr1960 said:
load any new apps recently?
Click to expand...
Click to collapse
As I said, the problem appeared with absolutely no new apps installed and persists after flashing a new ROM.
How do I know if my optical joystick is dead? It still works if that's what you mean (although I don't like using it).
I will try flashing the 30_2 radio, thanks for that suggestion.

slyn4ice said:
How do I know if my optical joystick is dead? It still works if that's what you mean (although I don't like using it).
Click to expand...
Click to collapse
If it works he's not dead
after flashing your radio and if the battery still drain check if the rom you use has his own rules for the cpu freq. if you are in that case don't use cpufreq or something like that because of conflicts.
PS: Sory for my bad english

Sithlord31 said:
If it works he's not dead
after flashing your radio and if the battery still drain check if the rom you use has his own rules for the cpu freq. if you are in that case don't use cpufreq or something like that because of conflicts.
PS: Sory for my bad english
Click to expand...
Click to collapse
Thanks, I just flashed the 17_2 radio. It doesn't look like LeeDroid has any requirements for cpu frequencies. I will post an update after an hour.

slyn4ice said:
Thanks, I just flashed the 17_2 radio. It doesn't look like LeeDroid has any requirements for cpu frequencies. I will post an update after an hour.
Click to expand...
Click to collapse
There seems to be no change with 17_2 radio. 15% drop for 1h45m. I will go through a charge/recharge cycle and if nothing has changed I will flash the 30_2 radio.

Some people had the same effect. It happens when you flash your ROM while the phone is connected to power/charging. The battery stats simply get messed up.
An easy indication for this is if you charge the phone fully while powered on, LED is green, as soon as you unplug the charger the battery drops to some 90%.
The fix is easy too. If the phone is fully "charged" while on, disconnect the charger and switch it off. Then plug the charger in again. The LED should turn orange again and the remaining percentage will be charged. Wait until you have a green LED and your problems are hopefully gone.
Look out for the battery calibrating thread here for more info.
Hope that helps...
Mac

mmaacc said:
Some people had the same effect. It happens when you flash your ROM while the phone is connected to power/charging. The battery stats simply get messed up.
An easy indication for this is if you charge the phone fully while powered on, LED is green, as soon as you unplug the charger the battery drops to some 90%.
The fix is easy too. If the phone is fully "charged" while on, disconnect the charger and switch it off. Then plug the charger in again. The LED should turn orange again and the remaining percentage will be charged. Wait until you have a green LED and your problems are hopefully gone.
Look out for the battery calibrating thread here for more info.
Hope that helps...
Mac
Click to expand...
Click to collapse
Thanks for the suggestions. I always thought it would be better to flash with the ac adapter plugged.
I have tried the method you described above but it hasn't really solved any of the problems.
The battery drain is now at least manageable - i had 50% drop while sleeping for 6 hours (at least it didn't drain it completely). I am going to flash the 30_2 radio and try again.

slyn4ice said:
Thanks for the suggestions. I always thought it would be better to flash with the ac adapter plugged.
I have tried the method you described above but it hasn't really solved any of the problems.
The battery drain is now at least manageable - i had 50% drop while sleeping for 6 hours (at least it didn't drain it completely). I am going to flash the 30_2 radio and try again.
Click to expand...
Click to collapse
If you have access to a spare battery, maybe you can try that too?
Normally when I have unexplained problems with the phone, the last drastic step I would take is to wipe everything, data/app/cache. Do a nandroid backup first so that if that doesn't solve your problem you could always get back all your setups.
You could also try Titanium to help save your setup. But I would be careful with what I restore. The last thing I would want is to get the messed up setting back in.
I have noticed also whenever I flash a new rom, the battery seems to get worse. So I would always do a recalibration. The proper step is here:
http://forum.xda-developers.com/showthread.php?t=755903 (and wipe the battery status on the last power up before using).
Lastly, I would use as stock as possible first to see if it is things that I introduce that cause the problem.

pehkblui said:
If you have access to a spare battery, maybe you can try that too?
Normally when I have unexplained problems with the phone, the last drastic step I would take is to wipe everything, data/app/cache. Do a nandroid backup first so that if that doesn't solve your problem you could always get back all your setups.
You could also try Titanium to help save your setup. But I would be careful with what I restore. The last thing I would want is to get the messed up setting back in.
I have noticed also whenever I flash a new rom, the battery seems to get worse. So I would always do a recalibration. The proper step is here:
http://forum.xda-developers.com/showthread.php?t=755903 (and wipe the battery status on the last power up before using).
Lastly, I would use as stock as possible first to see if it is things that I introduce that cause the problem.
Click to expand...
Click to collapse
I think I can definitely confirm the radio is the problem. There is barely any battery drain in airplane mode (1% drain per hour with WiFi on). I am back to 32.43.00.32U_5.09.00.20 but it seems to drain battery faster than before.
Now that I think back, this battery problem started when i switched to the newer 32.47.00.32U_5.10.05.23 radio. No matter what I do now though even after rolling back to older radios it's still a problem. Damn it.

slyn4ice said:
I think I can definitely confirm the radio is the problem. There is barely any battery drain in airplane mode (1% drain per hour with WiFi on). I am back to 32.43.00.32U_5.09.00.20 but it seems to drain battery faster than before.
Now that I think back, this battery problem started when i switched to the newer 32.47.00.32U_5.10.05.23 radio. No matter what I do now though even after rolling back to older radios it's still a problem. Damn it.
Click to expand...
Click to collapse
Don´t know (because i never updated radios above .20 and have no problems with battery)...but...maybe flash a original ruu rom...and root again
maybe this help...with kind regards..Alex

Alex-V said:
Don´t know (because i never updated radios above .20 and have no problems with battery)...but...maybe flash a original ruu rom...and root again
maybe this help...with kind regards..Alex
Click to expand...
Click to collapse
that doesn't help, ive tried it already

TieT said:
that doesn't help, ive tried it already
Click to expand...
Click to collapse
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings and ... got a 5% drop in battery for 10 hours on standby (wifi off, setCPU set to 245Mhz when screen is off). This is unbelievable.
Anyways, here are lenik's blog posts about it:
http://lazydroid.com/2010/06/battery-life-improved/
http://lazydroid.com/2010/06/back-to-1-21-...ry-consumption/
I hope this helps other people out there!

slyn4ice said:
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings and ... got a 5% drop in battery for 10 hours on standby (wifi off, setCPU set to 245Mhz when screen is off). This is unbelievable.
Anyways, here are lenik's blog posts about it:
http://lazydroid.com/2010/06/battery-life-improved/
http://lazydroid.com/2010/06/back-to-1-21-...ry-consumption/
I hope this helps other people out there!
Click to expand...
Click to collapse
VERY nice results! Do you think that these RIL settings should work on any network/carrier?
It's very odd because today I noticed my battery performance dropping large, BUT before it was always great. I am also on LeeDrOiD 2.1, and while at home, with WiFi + BT on AND connected to my router + handsfree, I lose only about 3-4% an hour.
Today when I left the house and went shopping, I was in the store for 1.5 hrs and I had lost near 15%! I had even turned off Wifi so it wasn't trying to scan APs. Very very strange...
Anyways, I want to maybe try these RIL settings if it will work on any carrier. Does anyone know if I can edit build.prop while in recovery, or do I have to edit it in the ROM .zip then reflash the entire ROM?
Thanks for the post and hunting down a solution slyn4ice, I'm glad that it has helped you out big time!
*** EDIT *** - After looking more into my JuicePlotter graphs, I notice that the battery life gets killed when I am using APN / 3G / HSPA network. I would have thought Wifi would take more power, but that seems not to be so. I DID have "Network Mode" set to "WCDMA only" (in Mobile Network Settings) because I heard it might save battery not having to switch back and forth from EDGE to 3G, but I guess that didn't help...I've since switched it back, but need a lot of charging before I can test again.
Does anyone else notice that when they're on 3G/H the battery drops MUCH quicker than if you were connected to Wifi instead? This is just my last hurdle towards a PERFECT ROM!
Thanks in advance all!

3G uses waaay more power than WiFi. After all, the data usually travels long distances and needs to be amplified. This effect is pronounced especially if in the limit zones of 2G/3G coverage and you have 3G preferred, the phone boosts the power to maximum to maintain 3G.
Gsm Auto (PRL) prefers 2G if 3G coverage is too low. WCDMA Preferred tries to maintain 3G connection even if it means sacrificing battery life.
If you are constantly in good coverage zones, no problem, but to the people living on the edges of proper 3G coverage it meas a big hit to battery life, especially if the mobile data is used. This partly explains why some get superb battery life and others far worse.

Jgruar said:
3G uses waaay more power than WiFi. After all, the data usually travels long distances and needs to be amplified. This effect is pronounced especially if in the limit zones of 2G/3G coverage and you have 3G preferred, the phone boosts the power to maximum to maintain 3G.
Gsm Auto (PRL) prefers 2G if 3G coverage is too low. WCDMA Preferred tries to maintain 3G connection even if it means sacrificing battery life.
If you are constantly in good coverage zones, no problem, but to the people living on the edges of proper 3G coverage it meas a big hit to battery life, especially if the mobile data is used. This partly explains why some get superb battery life and others far worse.
Click to expand...
Click to collapse
Amazing explanation and reaffirmation of my thoughts Jgruar (JuicePlotter confirms it). I guess from my old WinMo days, I always remember Wifi being the power hog. I actually did change it back to GSM/Auto since that was the only change I made lately, but I thought I'd chime in while my device was charging back up, hoping for a reply just like that!
Thanks a bunch!

scar45 said:
VERY nice results! Do you think that these RIL settings should work on any network/carrier?
It's very odd because today I noticed my battery performance dropping large, BUT before it was always great. I am also on LeeDrOiD 2.1, and while at home, with WiFi + BT on AND connected to my router + handsfree, I lose only about 3-4% an hour.
Today when I left the house and went shopping, I was in the store for 1.5 hrs and I had lost near 15%! I had even turned off Wifi so it wasn't trying to scan APs. Very very strange...
Anyways, I want to maybe try these RIL settings if it will work on any carrier. Does anyone know if I can edit build.prop while in recovery, or do I have to edit it in the ROM .zip then reflash the entire ROM?
Thanks for the post and hunting down a solution slyn4ice, I'm glad that it has helped you out big time!
*** EDIT *** - After looking more into my JuicePlotter graphs, I notice that the battery life gets killed when I am using APN / 3G / HSPA network. I would have thought Wifi would take more power, but that seems not to be so. I DID have "Network Mode" set to "WCDMA only" (in Mobile Network Settings) because I heard it might save battery not having to switch back and forth from EDGE to 3G, but I guess that didn't help...I've since switched it back, but need a lot of charging before I can test again.
Does anyone else notice that when they're on 3G/H the battery drops MUCH quicker than if you were connected to Wifi instead? This is just my last hurdle towards a PERFECT ROM!
Thanks in advance all!
Click to expand...
Click to collapse
From what I understand you need to update RIL settings in the ROM and then flash the modified ROM. I just edited the /system/build.prop file in the Leedriod zip file and saved (didn't resign or anything). Flashed the ROM through ROM Manager recovery (I also tried flashing it through the normal recovery but it failed on the "verifying image" stage - I guess because I didn't resign the archive).
As far as the options themselves - only the last two should be carrier specific. I haven't researched anything about them, so I have absolutely no idea what they actually do. "lenik" just copied them from an official Softbank ROM.
God, i just checked JuicePlotter and i dropped 1% for 1h10m (everything off except the radio + setCPU to ~400Mhz when screen off). This is just crazy ... awesome ))))

Is the setting rom specific, or will it work om opendesire?
Sent from my HTC Desire using XDA App

slyn4ice said:
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings
Click to expand...
Click to collapse
LeeDroid ROM (LeeDrOiD_V2.1_A2SD+_.zip) build.prop includes:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
but no:
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
Just checked.

CM7 RC1 Experience

Hi all, this is my first post and I'm a n00b to rooting, but don't let that stop you from reading on since I'm an advanced user and hope I can add some value here. Honestly, don't know what took me so long to do this. Posting to the Q&A forum since I can't yet post to the RC1 Dev forum.
My main goals for rooting were to get out from under Sprint's downgrade of my Swype beta (I should never have installed that OTA update, duh), upgrade to GB, and get better performance (battery especially).
I tried lots of the GB ROMs so far and experienced some of the reported problems like cycling reboots, slow/non-responsive market, CM skate anim cycling, etc. Some ROMs had swype, some didn't and most produced the licensing issue discussed in these forums when trying to install the latest beta.
Long story short, I've found a very stable and fast performing combo that I thought I'd share, and ask a question about. Here's what I did:
In recovery, Format_all, wipe data, system, cache, dalvik.
Install RC1, install the latest GB google apps and restart.
3G performance was piss poor, and I want wimax (more Geeees!), so I installed the toast wimax kernel (and antipasto font which I'm loving), cleared caches again, restarted and now 3G performance was faster than I think it has ever been. [EDIT: WiFi now an issue] and GPS are fast and stable. Best part, I was able to download and install the very latest Swype beta on this ROM.
A couple things that need addressing though:
'Cell standby' is a somewhat high percentage battery drain which I'll try to tackle through other reported methods (could be wimax searching/standby?). That said, battery life is still very good and way better than sprint/sense, even under heavy/constant use.
USB issues: Enable USB debugging and notify. Icon shows in notification bar. Disable debugging, but leave notify checked. Debugging icon still shows. Tied to this is the inability to select the mount/charge options, which others have recently reported in the RC1 Dev forum. So can't mount to PC. Any updates on how to resolve?
WiFi is now non-functional on my office AP.
WiMax control settings not showing up since they aren't there with this ROM/kernel combo for some reason. Any/all ideas welcome on this point too.
Slow market downloads, even though speedtest shows 527kbps down.
Thanks again everyone for this great community!

I haven't had any luck with my phone on my office AP (3COM) since I got this darn phone. For some odd reason it gets the wrong gateway and I have to set it up manually from the terminal if I want to use it after connecting. Check your gateway when you connect and see what you are getting.

admang said:
[*]WiMax control settings not showing up since they aren't there with this ROM/kernel combo for some reason. Any/all ideas welcome on this point too.
Thanks again everyone for this great community!
Click to expand...
Click to collapse
WiMax isn't in RC1 yet. You can get an alpha build that Shinzul has up. Or wait until the Final release which should have WiMax and HDMI working.

Thanks, I'll check the gateway, and will check out Shinzul's alpha.
Had my first auto reboot today, and Sms is not working right (yes, less than 160 chars and not mms). Might have spoken too soon about this combo...
Sent from my PC36100 using XDA App

admang said:
Thanks, I'll check the gateway, and will check out Shinzul's alpha.
Had my first auto reboot today, and Sms is not working right (yes, less than 160 chars and not mms). Might have spoken too soon about this combo...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Wait till the final release. It will be more stable.
Sent from my Evo powered by MIUI

admang said:
A couple things that need addressing though:
'Cell standby' is a somewhat high percentage battery drain which I'll try to tackle through other reported methods (could be wimax searching/standby?). That said, battery life is still very good and way better than sprint/sense, even under heavy/constant use.
Click to expand...
Click to collapse
Keep in mind that the "Percentages" will always total a 100%. Something will always be big.
So to me I WANT TO See Cell Standby be high. That means nothing stupid in the OS is chewing it up. And Cell Standby isn't effected all that much except the Radio Firmware (and settings) !! So be careful what you wish for.

The problem for me is, on sense you can uncheck radio always on to remove that cell standby huge drain. On froyo you can use juice defender. But on cm7 you can do neither. So I need to turn it on and off manually. Very annoying, anybody have a solution?

If you install CM7 nightly build #6 (today's build), it now has support for WiMax and SMS splitting.

juice defender is failing me. and i reeeeeallly hate turning data on and off manually. any suggestions? i'm new to aosp so i'm a bit lost rigt now.

Just use the expanded notification bar and toggle data. You're not gonna be able to shut off the radio without airplane mode.
Sent from my PC36100 using XDA App

dkdude36 said:
juice defender is failing me. and i reeeeeallly hate turning data on and off manually. any suggestions? i'm new to aosp so i'm a bit lost rigt now.
Click to expand...
Click to collapse
Unfortunately I think some permissions changed within Android 2.3 which CM7 uses and JuiceDefender just doesn't work on it yet. You're only other option is to flash CM6 (Android 2.2) if you must have JuiceDefender working in ASOP.

IOInterrupt said:
Unfortunately I think some permissions changed within Android 2.3 which CM7 uses and JuiceDefender just doesn't work on it yet. You're only other option is to flash CM6 (Android 2.2) if you must have JuiceDefender working in ASOP.
Click to expand...
Click to collapse
ya it looks like thats the case. sucks cause it is taking a really high toll on my battery. i hope somebody will put it into one of the next builds soon.

Continuing from my OP, I'm now off RC1 and onto Nightly #12 with WiMax. WiMax when on is a huge battery drain and I'll be doing some post-reading to figure out if someone has found a way to set a WiMax antenna polling frequency so that it can sleep for periods when not connected.
That said, the WiMax is nice and fast...so I only enable it with the notification bar widget when I need speed or talk/data simultaneously. I also use a new version of Setting Profiles (Full version) to toggle the Wimax on/off based on where I am -- note that this is a test version sent to me by the developers as I've been helping them test this feature. So I don't know if it's in the latest market release version, but if you are a paid owner of that app, just email them and ask for it (although the updated market release is likely not far off if it's not out already).
With the XDA-sponsored SetCPU on and no WiMax, I'm actually getting great standby times in the double-digit number of hours, which has been a first for me with this phone! I know there are some great posts out there about manual conditioning of the battery, which I'm eager to try, and other useful battery-related posts.

I am running CM7 RC1 and I have to say I love it. The first couple of days after flashing I was experiencing terrible battery life. I mean 5 hours or less. I finally flashed Savage-Zen kernel and used the "smartass: governor in CM settings. My battery was better, but Cell Standby was still draining all the battery. I wiped the dalvik cache again and it helped some. but I think the best thing I did was disable google backup settings. Keep in mind before I flashed the kernel and battery life was horrible I wasnt using it heavily, WiFi was off completely, I toggled mobile data on and off as needed, and didnt let anything except for weather autosync. I had maybe 10 applications as well. Once I flashed Savage-zen, used smartass, and disabled Backup data to google servers. MY battery lasts over 2 days with moderate usage with mobile data always on and gmail and weather auto synced.
As far as bug-wise, the only thing I have experienced so far is sometimes there is a slight delay when unlocking the phone and getting the lockscreen to show. Sometimes when the button is pressed to unlock, the bottom touch buttons light up, but the lockscreen takes like 5 seconds to appear.
One more thing is the GPS icon stays in the notification area once it has been turned on and back off.
All in all I can say now that I have amazing battery life, I love CM7 and will not use anything else besides CM7. I cannot wait until the stable release is out. GO CyanogenMod Team!

[Q] Battery drain and 3G connectivity loss

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.

[Q] ARHD 7.0.2 "Phone" process keeping CPU at 100%

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