Froyo wakeup response - Hero, G2 Touch Q&A, Help & Troubleshooting

Has anyone used a froyo rom that has a really quick wake up (press button after screen is off)? Ive tried FV1.5 and Cronos 1.1 or 1.2 i forget and both of them have a bit of a slow wakeup (1+ seconds). Im too used to my kimera2.1 having like a half second wakeup. Thanks for any input

I'm using Froyd Villain with the latest Flykernel , screen off CPU @ 176 - 352, screen on @ 528 - 691. Flawless so far, less than 1/2 delay to wake-up I reckon , but only been using for 12 hours or so.
Sent from my HTC Hero using XDA App

Op, increase your sleep speed

I use the same speeds for all the roms i go thru. 176/528 and sleep at 176/352. Kimera and RCmix are the only roms that wake up practically instantly. Everything else one second or more

walkinhotdog said:
I use the same speeds for all the roms i go thru. 176/528 and sleep at 176/352. Kimera and RCmix are the only roms that wake up practically instantly. Everything else one second or more
Click to expand...
Click to collapse
Trust me, froyd is very particular about sleep speed and governor. Conservative governor works best in sleep.
Failing that, it could be hardware... sleep resume fine here on 19 MHz

Related

Overlocking with smartass

Hei guys, I'm really, really new to this.
I've just flash andy's port of CM7 based on 2.3.4. I'm having a really though time with the battery, it goes down 50% faster than on my previous 2.2.2 official Froyo from LG.
Anyway, this question is about overclocking.
So, inside CM7 settings there's this "Performance" menu, in which you can go to "CPU", I've set there smartass governor, minimum 122 and maximum 768.
What does that mean? Does that mean I'm overclocking my CPU? Does it mean that smartass will allow or push the CPU to 768 when it's needed? Do I need to do something else in order to achieve that? (i.e - use get the CPU at 122 while screen off and increase it according to demand up to 768). - that's what I'm after.
Any response on the topic(s) much appreciated.
Thanks.
Regarding battery - calibrate it with the app from the market
Regarding OC - yes, when you'll use the phone your cpu will run at 768 mhz (note that you might get kernel panics). Your minimum speed is pretty low and it will take a little longer to get to 768... you will see some skips or lags.
Oh, and yes! You're overclocking and smartass will do what you're looking for (idle-122/in-use-768).
Sent from my LG-P500 using XDA Premium App
I would kick the min up to 480. That usually gives you a good balance.
Sent from my LG-P500 using XDA App
Thanks for the fast response.
As for the battery, I tried calibrating it and still the same.
I'm reporting 10% (exactly) each 2 hours, in idle, screen off, everything turned off except mobile data on EDGE.
At this rate, the phone goes dry in exactly 20 hours with minimal to no use. This isn't normal.
It heats up when charging (more than usual).
In battery stats I have all the four ones (android system, cell, etc.) at 25%.
No apps installed.
Just a few hours ago I tried replacing the stock kernel of andy's with the latest from franco (16) and zram.
Exactly the same.
I don't know what else to do, I already reflashed it twice. Same results. I can't post to the development forum just yet (not enough posts).
I guess I'll just go ahead and try mik's port... although I wouldn't want to, I love this one, everything works perfectly except the battery thing.
Did you use google maps?
"Known bugs
[...]
- Google Maps is eating your battery, kill this app after using in Setting->applications
[...]"
i think smartass does automatically change your cpu's frequency when you need it..but your minimum frequency is too low..change it to 320 Mhz....and are you using 3g all time..??
Yes, used google maps but killed it. Second reflash didn't even install it and still the same problem.
No, I didn't use 3g at all.
I only kept mobile data active on EDGE. and as I said, it was in idle. it's like the phone was used 24/7 even in idle.
and why is my cpu to low? the phone works like a charm with that frequency.
Check the 2 g networks only box in settings-networks- mobile networks....that may be the reason
Sent from my LG-P500 using XDA App
It's checked alright. Like I said, I used it on the EDGE (2G) networks.
Anyway this doesn't matter anymore since I've switched to mik's rom.
you can give void# forever a try too...gives me two days battery life on moderate use...
Okay, I will.

[Q] overclocking with setcpu

Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
kscully said:
Is it safe to overclock the Touchpad using setcpu? I have it at 1.5 ghz and it seems to be working fine.
Click to expand...
Click to collapse
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Overclocking so far works well. I see no problems as of yet. Just make sure you OC with setcpu; frequencies do not show up in cmsettings when you try to OC there.
Sent from my HTC Glacier using XDA Premium App
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
mines not overclocked and has happened 4 times today. So, obviously not an overclock only problem. I will tinker around with it, but ive yet to tell myself...man, this needs to be speedier. Its run QUICK. far quicker than WebOS and its many 10second pauses (OCed to 1.7 and patched to boot..)
atapia984 said:
I have been reading about this all day. Some people have claimed that once your device goes to sleep it does not wake up unless you press the POWER + HOME buttons at the same time for 30 sec. I guess YMMV.
Click to expand...
Click to collapse
Haven't tested it yet, but some say it's a problem due to the "minimum cpu speed" setting when it goes to deep sleep. Something about it being too low and thus can't get out of sleep and setting the minimum higher (not sure of they value) should remedy that.
I'm using SetCpu with a OC of 1.5 and a minimum of 384 with no issues.
my question is should I click the box for set on boot?
i do. set on boot, min 384 max 1512, ondemand tcl
no sleep death, no lag, working great! (mind you im still on CM7 A1, by preference)
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
There's a fix to the Sleep of Death issue and that worked for me. I thought using SetCPU caused the sleep problem but that doesn't seem to be the case. I'm going to see how far I can overclock my TouchPad now
link
I'm running Setcpu at 384/1.7 with zero problems.
I was having issues at first with failure to wake from sleep but after I changed my min to 384 It has not failed once. All my little problems went away when I made this change. Been running for 12 days without a single need to reboot.
butikofer08 said:
What is the difference between ondemand and ondemandtcl settings? Also, any problems encountered running 1.7g I've only read people running 1.5g...
Click to expand...
Click to collapse
i run 1.5 purely for performance/battery conservation but it goes to 1.7 just as easily too.
also traditionally:
Ondemand - Both CPU cores freely move up and down as needed.
Ondemandtcl - prefers the use of CPU0 unless CPU1 is absolutely necessary for use, then it will kick in. otherwise it will remain idle
does anyone try alpha 3?
I saw people said touchpad freeze when using setcpu. Does it work well?
im oc with 1728 max and 192 min ondemand. no issues or sleep of death. im thinking of bumping it up to 1.8ghz like i have in webos.

[Q] ZenDroid-2.1.2 and Kernels

I don't have enough posts to ask this in the development thread.
I'm using ZenDroid-2.1.2 with the included Bali v1.8.8UV kernel.
This combo works great, but it will sometimes hang for 0.5-2 seconds before completing an action (opening an app, recognizing keyboard input).
This lag is really noticeable after coming CM7 with an OC kernel (I left because I need 911, GPS, and better battery life).
Any suggestions to get a snappier response? Should I try a different kernel?
Thanks!
Self-reply here.
I tried the Bali X 1.2 and and got sleep of death on stock settings. When I used set CPU at min 400 and max 1200 (both conservative) the battery went dead overnight from 78% and my alarm didn't go off.
Still looking.
I notice this too sometimes but it has never really bothered me. Some other kernels you can try are Stock KB5+Voodoo, DragonMODz, or Immortality.
DragonMODz is a good one, and while I've not used Immortality myself, I heard good things. Obviously none of these are really updated anymore but it's not really a big deal.
Jneal9-
I see you've got Bali X as your kernel in your sig. What settings do you use?

Icecream Sunday Final + Lag

I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Gooner88 said:
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Click to expand...
Click to collapse
hi you have to flash a kernel (you ll find all the information needed in the ic sunday topic)
i did do that and its far better
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
I'm having wake-up lag too! But I already gave up thinking that the SGA's CPU just sucks. Thanks for this info GerasVille, I did not think to tinker with the System settings of CyanoGen because of the "Dragons Ahead" prompt. I will try this smartass setting to see if the wake-up lag will be removed. It sucks when I have to send an emergency SMS and my phone is lagging like hell.
Anyway so let me get this straight. Does having the minimum CPU clocked at 122mhz mean that if the device is inactive, it dynamically clocks down the CPU to 122mhz to save battery? Hence the wake-up lag is caused by the CPU being clocked back up?
I'm also gonna try out slaidfastmod to see if it makes it even better.
You can put up with the lag and save a tiny bit of battery life, or speed up the CPU and lose some battery life. Whichever you feel is more useful. Personally I don't mind the small unlock delay. Happens on most phones low powered anyway.
Sent from a phone with an app.
Eniac77 said:
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Click to expand...
Click to collapse
The kernel that is currently installed is "2.6.35.7-perf-CL562111" Ketut-lenovo #4. I am not sure if it is an OC kernel.
GerasVille said:
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
Click to expand...
Click to collapse
I installed SlaidFastMod v2, set governor to Smartass and min CPU frequency to 245 MHz and this fixed the issue! It's much smoother when unlocking.
Is it safe to tick the "Set on boot" setting for CPU settings?

[Kernel]Unsecured, OverClocked, SmartAssV2, and Voltage Control[New Links 01.27.12]

Okay, I looked at what ziggy and cron247 did over on XDA and tried to make it better.
This kernel is unsecured, meaning adb connects with root.
It OverClock's up to 1.836MHz.
It has the SmartAss V2 governor.
It uses my ramdisk, not the one you have. I cannot forsee this being an issue. If it becomes one, let me know.
Updates:
Version 1.1.3 changes the version of lagfree, the old one was having issues. Also removes forcing the second CPU to be online which was causing choppiness.
Version 1.1.2 adds increased read ahead, writeback tweaks, decreased dirty ratio settings, simple I/O scheduler, and the lagfree governor.
Version 1.0.5 adds mpdecision fix by Mr X, thank you whoever you are, if you removed mpdecision, put it back. Also added voltage control for you UV lovers.
The only control program I have tested to work is AnTuTu CPU Master (Free), I have had issues with SetCPU and a few others. This one does speed, governor, and voltage all very well.
Get it here: AnTuTu CPU Master (Free)
The following problems seem to be fixed at this point: governor and speed settings not sticking, smartass staying at top speed, random reboots or bootloops overnight.
READ THE INSTRUCTIONS, THIS IS A SINGLE FILE
To install this kernel:
Copy the file to the root of your SDcard.
Reboot into recovery (CWR or AmonRa).
Flash the file from the SDcard.
At the end of the flash the phone will reboot to fastboot.
Once fastboot loads, tap PWR to get to HBOOT.
HBOOT will find the update and ask you to install.
Tap Vol Up to begin the install.
When it finishes it will say tap PWR to reboot. Do it.
After the phone boots remove the PH98IMG.zip file from your SDcard.
Use AnTuTu CPU Master (Free) to set min/max/gov/voltage.
Enjoy!
Thanks to ziggy and con247 for getting us started and having stuff out there for me to get ideas from.
Download:
Link: dsb9938 Kernel 1.1.3
MD5: a2558e70f9af572f43e258c9aedb4b40
Source on GitHub.
My favorite Rezound kernel so far. Haven't had one crash, even at max OC. Thanks so much guys at BAMF!
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
dccoh said:
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
Click to expand...
Click to collapse
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Argent36 said:
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Click to expand...
Click to collapse
It's kernel related; I'm running rezrom and had the same exact issue with my alarm running this kernel.
Do you think ziggys is more stable?.. or do I just need to find the right overclock/underclock settings?
I seem to recall seeing them have that problem on ziggy's - but I never had that problem on earlier versions of dsb's - so maybe it's just something that is fixable for the next release
*wanders off to test it again*
This is no doubt me doing things wrong that led to this, but I downloaded the kernel through the phone browser, then flashed it from the download directory on the internal SD. When I flashed Incredikernel from there it copied the PH98 to the sdcard, but no dice on this kernel until I copied it to the sdcard then flashed it.
I probably should have copied it to the sd card myself first anyway, but I figured I would let you know!
Well this morning - my alarm clock went off - I was able to snooze it - and then a few minutes later the phone went in to boot loops - had been running stable all weekend - once I pulled the battery the phone booted back up just fine.
we'll see if it repeats this behavior tomorrow morning or not...
Call recording support in the kernel?
timp123 said:
Call recording support in the kernel?
Click to expand...
Click to collapse
Nope, only Ziggy's kernel currently supports this.
I only set one alarm at a time usually, but I have one set to go off every morning at 7:30 & it has worked perfectly everyday for a few weeks now.
~John
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
sandman_nyc_316 said:
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
Click to expand...
Click to collapse
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
hgoldner said:
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
Click to expand...
Click to collapse
Thanks! How's your battery life been with those settings?
sandman_nyc_316 said:
Thanks! How's your battery life been with those settings?
Click to expand...
Click to collapse
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
hgoldner said:
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
Click to expand...
Click to collapse
Appreciate it. Gonna see what happens. Will update with my results. Thanks again!
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
zetsumeikuro said:
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
Click to expand...
Click to collapse
Good question. I haven't had a single bootloop since flashing this kernel after coming from Ziggy's. Been running this 192min/183max and UV'd -75 across the board and running great.
Hopefully I don't jinx myself.
Guys with bootloops/lockups...are you running any profiles?
Make sure you do a dalvik cache wipe....
Ziggy's would always lock up on me (multiple times per day) so I gave up on it. The only problem I have with this on (and this was a problem with Ziggy's too) is the min jumping to max.
My frequencies bounce on this kernel. It spends about equal time between the highest setting, and lowest setting. It works great other than that. My question is this bad for my CPU? I get great battery life, and performance, just scared the bouncing could be bad for the processor. Any help would be great.....
Sent from my ADR6425LVW using Tapatalk

Categories

Resources