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...
Hey all,
Noticed my battery level dropping pretty quickly even with SetCPU etc. underclocking my Desire when the screen is off. It seems it's the Suspend process using around 30% CPU for no reason. See screenshots attached.
Any ideas what could be causing this?
Thanks
Russ
It may be that System Panel itself is causing your issue.
See this thread.
Regards,
Dave
Having it simply installed would cause this? I don't usually leave the monitoring running unless I suspect something is up, that's the only reason it's running at the moment.
roakes said:
Having it simply installed would cause this? I don't usually leave the monitoring running unless I suspect something is up, that's the only reason it's running at the moment.
Click to expand...
Click to collapse
Probably not, but it may be skewing your results when you try to determine what's causing the problem. What about partial wake locks - is anything else keeping the phone from sleeping?
Regards,
Dave
Doesn't seem to be anything else. I'll keep an eye on it now that I have changed the priority setting on system panel.
It's definitely not SystemPanel. I have it and it's off and the suspend process is running wild.
esone1ll said:
It's definitely not SystemPanel. I have it and it's off and the suspend process is running wild.
Click to expand...
Click to collapse
Did you ever find out what was causing this? I'm finding the same thing on my phone twice this week.
turn off auto sync, toggle on off as needed, you can be running all sorts of data through system apps via 3G even when the phone is asleep/standby
Foxmeister had a point because suspend does show up as 10-30% consistent when you have hardware monitoring and logging enabled in many apps like System Panel.
-----------------------------------
- Sent via my HTC Desire -
pedaah said:
turn off auto sync, toggle on off as needed, you can be running all sorts of data through system apps via 3G even when the phone is asleep/standby
Click to expand...
Click to collapse
this isnt it. i had my phone in airplane mode all night and the "suspend" process started running at 10% CPU from 10pm to 6am when the battery died. if airplane mode was on the whole time, no way its caused by data/network
I am having the same issue, airplane mode was on but suspend is acting crazy. This has been killing me since I've flashed the new update for evo 4g for my rooted phone. 30% sucking from process has left me charging my battery twice a day. Please help if anyone can!
same issue here.
EVO ... Froyo 2.2
suspend ... according to watchdog ... is regularly registering at over 50%...
if i reboot the phone .. it will take care of the issue for a few hours or maybe a day ...
I'm having this problem too. Rooted with Myn's Warm ROM. Someone at AF said it was the Facebook app. I'm uninstalling that now...
...any other ideas?
Same problem. Rooted evo king bfs #9 kernel
I have "always on data" un checked and noticed this... Maybe apps are trying to sync but have no network connection...
Was having same issue with rooted stock rom. Recently flashed to Vaelpak 2.2 and hasn't happened yet...
So this still happens to me once in a while. I found if I'm in an area where I can connect to wi-fi, the suspend process drops to 0, after connecting to wi-fi. Other than that only a reboot will "fix" it for a while.
Anyone else have any updates?
I raised the flag on this issue in early august for my stock 2.2 EVO. I was basically ignored back then, so now that others are experiencing this, perhaps we can get enough info to submit to HTC for a fix. If it's affecting the EVO and the Desire, it probably affects all 2.2 Sense UI androids.
http://forum.xda-developers.com/showthread.php?t=759301
I'm in the same boat... I never noticed this problem, until Sunday. Now I have had the problem 3 times in 4 days. Reboot fixed each time, but seems to be coming back more often now.
I'm running VaelPak 2.2... Maybe gamer83 is onto something with it being Sense related /shrug...Has anyone running CM noticed this issue?
I am experiencing abnormally high suspend cpu activity too. The strange thing is it behaves when I am connected to a wifi network. It goes to crap when I am away. Not sure if means anything, but when I am away I have 4G on.
Make sure to star this issue:
http://code.google.com/p/android/issues/detail?id=11126
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!
I was wondering if anyone else was seeing this issue or knew what was causing it. My phone has for the longest time, been doing almost a hot boot on it's own, where I will notice the phone is at my desk, I see it come on by itself, menu and back buttons lit, and it looks like it reloads all the os. No errors, or crash errors, just on it's own. I have nothing stock uninstalled (everything on the phone is stock, rom included), did have some disabled via TB, but to test I allowed all services/apps to load as when I got the phone, still does the same thing, like every other day. I have the latest OTA, rooted, with the freeza update for LI3, running apex launcher pro and of course some apps/widgets like everyone else. This happens no matter what, but always on it's own. I have a widget that shows memory usage, and I'll have sometimes 300mb free, and once this "hot boot" the phone does, i'll be back at over 1.2 gb free, so I know it's reloading everything on the phone. is there any way of figuring out what is causing this, cause I know this isn't normal behavior. Any help would be great!
so I think I found the answer.. Via WIFI settings I had enabled under Advanced: Keep WIFI on during sleep, NEVER (increases data usage)... Of course when you'd then try to use your phone after some time, you'd notice it switch radios from 3/4G to WIFI, and sometimes it would take a few seconds to do that. When I had that option enabled the OS would reset itself after about a day of use, as I described above, not a full restart, no crash/force close errors, you'd just see the phone come on, and basically everything reloading.. After trouble shooting whether it was an app or something causing this, it was, I believe, the WIFI setting, since I changed it to keeping WIFI on "always" during sleep, in that advanced setting, the phone has not done the issue described. Going on 79 hours with no issues, which is the longest I've seen since noticing this problem.. So hopefully in the future if this happens to others, this method might be what was the problem/cure..
I always keep wifi on.. it seems to save a lot more power than 3g and its clearly faster =p.
Sent from my SPH-L710 using xda app-developers app
Hey guys I have searched and searched for a remedy for my problem, first off here is what I am running on my i9250:
ROM: Beanstalk 1.190
Kernel: KUBO-AK r46
Baseband: I9250UGLL1
Now the problem is this, all data (wifi and cell data) randomly disconnects when my battery is anywhere lower than 50% and gets increasingly annoying the lower it gets. I do not have any powersaving features enabled and yes I have changed the advanced settings in Wifi (Keep wifi on during sleep: checked to Always, Avoid poor connections: Unchecked, wifi freq band: 2.4ghz only, wifi optimization: unchecked; i guess that is a powersaving feature as well)
Still the problem persists. The other problem is, it happens to my cell data as well, when I wake the phone up (when it is under 50% or so) I see that only then the cell data starts to reconnect, and then I get all my whatsapp messages and emails all at once. (same goes with the wifi) Keep in mind though, when I have the phone plugged in and charging the wfi or cell data are active when the screen is switched off. The problem only occurs when the battery is below 50%.
Is there anything I can do about this, it gets really annoying because I have to wake the phone up and keep the screen on, in order to get messages. I know there is a widget that keeps the wifi active regardless of the battery level, but what about the phone data when I am out and about. I need to stay connected especially with emails and whatsapp because that is how clients stay in contact with me and it sucks when they send messages and I get nothing and they have to wait for me to check or wake up my phone for the data connection to re-establish whether it be on wifi or data.
Anyone knows how to fix this problem?
No one?
Have you tried changing your kernel? Sometime kernels can have weird affects on your device.
İ think this is one of kernel problems. Battery section is controlling by kernel. Find a kernel and use smartassv2 with sio.
Yes, I swapped around a few kernels and same effect. I really am at a loss.
amd-dude said:
Yes, I swapped around a few kernels and same effect. I really am at a loss.
Click to expand...
Click to collapse
it happens to me as well, not sure about the 50%, but when I am at home with 3G and wifi on very often if i turn on the phone the signal bars are grey and not blue and it seems that connectionwas lost during sleep and is being turned on again
btw, I am on stock 4.2.2
Try to format /system. And reflash. İf its not work, flash stock rom and flash custom rom. İm not sure if it will work.
Believe me, I have tried every wipe and every rom/kernel combo that is humanly possible
Then problem is hardware thats what I thought. Unfortunately. Technical support helps.