I've been experiencing lockscreen lag on all of the froyo ROMs I've flashed so far.
Tazz
KaosFroyo
etc...
Is anyone experiencing this, and have you found a work around?
Yes, I have been experiencing a lag on tazz. I just flashed it yesterday.
Sent from my Eris using XDA App
I have noticed that since the adw launcher/launcher pro type launchers rotate when you unlock the screen in a different orientation, the unlock is delayed because the phone is busy re-orienting the home screen. I've turned off the home screen rotation (I use Launcher Pro) and the lag is gone.
I actually don't have any lock screen lag with Tazz. The only time I notice a lag is when I am getting an incoming call. It takes awhile for the answer button and caller id to show up on my screen. I always think I am going to miss the call.
I am using ADW and I don't have homescreen rotation on.
I get the lag on Tazz Froyo.
Absolutely no lag on Kaos with stock launcher (not an ADW fan here). Also, no lag on CELBfroyo with launcherPro.
Folks that report lag issues coming out of sleep should report their sleep profile used with SetCPU - that's a huge wildcard that is more about the kernel's variable-frequency clock stepping behavior than the ROM.
Particularly if you are using minimum clock speeds less than 245 Mhz, or if you are also restricting the max clock to a low value.
There seem to be some pathological behaviors (even in the 2.1 OC kernels) if you use too low a clock speed, where the kernel gets temporarily "stuck" at low frequencies - and they can happen even if you have set up a reasonable max frequency with the "ondemand" governor.
Not saying that's what is happening here - but it is a huge wildcard when folks start comparing their results.
bftb0
Remove SETCPU widget and turn off homescrren orientation, it stops launcher lag.
Turn up your screen off clock settings, you wont lag when getting a call either.
Sent from my FroyoEris using XDA App
sanpellegrino said:
I get the lag on Tazz Froyo.
Click to expand...
Click to collapse
what is the eris's stock speeds(non-root) sleep speeds
theboo7 said:
what is the eris's stock speeds(non-root) sleep speeds
Click to expand...
Click to collapse
I'm fairly certain it is 245min, 528max. It doesn't actually have profiles set up, just a running min-max.
Sent from my FroyoEris using XDA App
AdhvanIt said:
I'm fairly certain it is 245min, 528max. It doesn't actually have profiles set up, just a running min-max.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Oh okay Thanks. So that means we could set the sleep profile to 528 max, On Demand 40% threshold and 200 powersave bias, would make it do even better than stock eris? Concerning battery life
Try TazzFroyo v6 that was released yesterday.
redhooka said:
Try TazzFroyo v6 that was released yesterday.
Click to expand...
Click to collapse
Slightly lag but nothing unbearable by any means. The Eris hardware isn't cutting edge you know.
I have 160min on tazz for when I'm asleep and 486 or whatever max... 0 lag ever.
I use the SetCPU settings in the following link with my Eris running the Tazz Froyo ROM and have no lockscreen lag.
http://forum.xda-developers.com/showpost.php?p=7528238&postcount=4
I have my screen off settings at 122mhz - 528mhz lol no lag and I save so much battery.
I've had no lag issues with Tazz's Froyo. I'm using LauncherPro with no orientation (I hate landscape anyway) and the following SetCPU profiles:
Temp > 50 C 480 Max/122 Min
Battery < 40 % 480 Max/122 Min
Screen Off 480 Max/122 Min
Charging\Full 768 Max/528 Min
My linpack scores aren't very good, but everything runs quite snappy for me.
rycheme said:
I've had no lag issues with Tazz's Froyo. I'm using LauncherPro with no orientation (I hate landscape anyway) and the following SetCPU profiles:
Temp > 50 C 480 Max/122 Min
Battery < 40 % 480 Max/122 Min
Screen Off 480 Max/122 Min
Charging\Full 768 Max/528 Min
My linpack scores aren't very good, but everything runs quite snappy for me.
Click to expand...
Click to collapse
Not to mention he has fixed the camera and will be releasing v7 soon
Related
When I get a call, my Eris 'lags' or is really slow to pull up the 'caller id/answer' screen...aka-my phone starts ringing and they screen doesn't show anything until it has rung 2-4 times. At that point, I have only one or two rings to answer it until it goes to VM. I can answer with the hard button just fine, but can't see who it is calling when I do that...I am in marketing and it's VERY important for me to see who is calling before I answer.
Eris on Cricket service:
KaosFroyo V30
EPST settings have not changed since I rooted (the day root was discovered)
PRL is known good and has produced no issues until Froyo...
The first place to look is your setCPU profiles and settings. What are they?
710/122 on demand
Charge:
528/122
Failsafe:
480/122
That is it.
Have you tried bumping up your bottom line speed to like 250mhz?
meanm50 said:
710/122 on demand
Charge:
528/122
Failsafe:
480/122
That is it.
Click to expand...
Click to collapse
Priority values would be useful, but then again your low values don't seem that bad.
You are not using the SetCPU widget on one of your homescreens, are you? (A number of people have reported that causing problems, whereas just using setCPU with profiles and no widget use, things were fine).
I'm downclocking to 19 Mhz in KFV31, but I am using some of the setCPU advanced tweaks, and I probably also get fewer calls than you. (So far, no sluggish behavior on inbound calls when the phone is sleeping).
bftb0
I'm having the same problem but I do have the setcpu widget running. I'm going to remove it and see if that helps.
Sent from my Froyo Eris using XDA App
I will disable the widget and see if that helps. Thanks!
My lag got better when I turned launcher rotation off.
Wife has rotation turned off period, and there is no lag to speak of.
KaosFroYo on Eris with Ming font.
ADW rotation was already off...I actually don't like rotation. It always flips when I don't want it to.
I turned up my MIN cpu speed and that made the phone wake from sleep a little quicker, but the call issue is still there. I am thinking it has something to do with the actual dialer .apk used. I think it's Dialer One?
meanm50 said:
ADW rotation was already off...I actually don't like rotation. It always flips when I don't want it to.
I turned up my MIN cpu speed and that made the phone wake from sleep a little quicker, but the call issue is still there. I am thinking it has something to do with the actual dialer .apk used. I think it's Dialer One?
Click to expand...
Click to collapse
I'm not using the same rom, but i've had the same problem before. In setcpu, try these settings:
Max:748, min:604 - userspace
Screen off max: 604, min: 604 - performance
Macrodroid said:
I'm not using the same rom, but i've had the same problem before. In setcpu, try these settings:
Max:748, min:604 - userspace
Screen off max: 604, min: 604 - performance
Click to expand...
Click to collapse
The DEV doesn't even recommend using the "userspace" setting. And 604 as a minimum? Wow.
KaosFroYo on Eris with Ming font.
Has anyone tried this app? I'm getting improved battery life from how it handles the processor in idle mode. After 3 hours I normally would lose 10% being idle, now 2%. Using it the same with same background apps running. Its free too.
Sent from my Dell Streak using XDA App
I'm using SetCPU with similar results
default (1190/245), battery< 66 (768/245), battery < 33 (460/245), screen off (460/245)
also using "juice defender"
Radimus said:
I'm using SetCPU with similar results
default (1190/245), battery< 66 (768/245), battery < 33 (460/245), screen off (460/245)
also using "juice defender"
Click to expand...
Click to collapse
Are you on streak droid 1.5.1?
when I use setcpu it cause my device to reboot on it's own.
I uninstalled it and all is well now but want to put it back because it did really well for my battery life.
Forgot what frequencies I had set in the profiles but I was using on demand scaling.
I had charging/full oc'd, screen off between the lowest and something around 450, batt < 30% same thing, and temp > 50c between lowest and 768
I'll reinstall it now and set your profiles and see if that helps.
Also using adw.launcher
---UPDATE---
So i reinstalled SetCpu and changed the lowest from 128 to 245 and no longer rebooting.. think that was the issue.
fone_fanatic said:
Are you on streak droid 1.5.1?
when I use setcpu it cause my device to reboot on it's own.
I uninstalled it and all is well now but want to put it back because it did really well for my battery life.
Forgot what frequencies I had set in the profiles but I was using on demand scaling.
I had charging/full oc'd, screen off between the lowest and something around 450, batt < 30% same thing, and temp > 50c between lowest and 768
I'll reinstall it now and set your profiles and see if that helps.
Also using adw.launcher
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
...And does it still keep rebooting? I notice that on re-boot, it says max speed something like 768MHz, even though both slider bars are set to minimum.
I set screen on to be performance, put streak into standby and left in my pocket for an hour. I cam back to find my streak pretty warm abd the battery practically flat?? Don't know if this was a setCPU issue as it's never happened before???
odyseus said:
...And does it still keep rebooting? I notice that on re-boot, it says max speed something like 768MHz, even though both slider bars are set to minimum.
I set screen on to be performance, put streak into standby and left in my pocket for an hour. I cam back to find my streak pretty warm abd the battery practically flat?? Don't know if this was a setCPU issue as it's never happened before???
Click to expand...
Click to collapse
stick this file in sdcard
and start setcpu.
then menu device selection
Show other frequency sets
scroll down to Custom Frequencies
ok
ok
and it should work fine from then on in with steves O/C kernels( you only need do it once)
and it will set from 248 -1194Mhz if you want to add the extras over voltage O/C clocks from 1.51 then you can edit the setcpu.txt manually.
I don't use the last two as on mine I get worse scores than with 1194mhz so I didn't include them in that text file
yeaaah
Yeaah, CPU Tuner is awesome app. A set CPU frequency on my HTC Wildfire on 691 MHz and phone is faster
its a paid app so therefore i will not post any links. but there is some info about using it on the galaxy s devices and how we should avoid some settings and use others to dodge the bugs...
copy/pasted
Description:
SetCPU is a tool for changing the CPU settings (capable of overclock and underclock) on a rooted Motorola Droid, Nexus One, G1, G2, Samsung Galaxy S, or one of many other devices to improve performance or save battery.
SetCPU also allows you to set up profiles to change the CPU speed under certain conditions, such as when the phone is asleep or charging, when the battery level drops below a certain point, or when the phone's temperature is too high. See the screenshots for examples of how you might set up profiles.
SetCPU's wide feature set make it useful to beginners and enthusiasts alike. Accelerate your processor to unleash your phone's multitasking potential, or dial your CPU's speed down to save battery.
Have an HTC Sense device with a stock ROM or kernel? If you are having trouble getting your settings to "stick," press Menu > Disable Perflock. You still have to be rooted.
Galaxy S devices: ondemand scaling is recommended. There are issues with Galaxy S kernels that may result in crashes if conservative scaling governor is used, or if the sleep profile "max" value is set too low. Please do not set the sleep profile too low, and avoid using conservative scaling.
Requirements:
all Android versions
Recent changes:
2.1.0
- Significant UI and user experience revamp, including a new background for the widget, and new notification icons
- Added a quick priority swap button to the profile lists
- Significantly improved the reliability of autodetect on certain kernels
- Numerous bug fixes and crash fixes
Click to expand...
Click to collapse
I understand it's a paid app in the market. But if you're an XDA member you just go here:
http://forum.xda-developers.com/showthread.php?t=505419
It's not a secret...
Funny, the previous version of SetCPU specifically told Galaxy S users to use conservative scaling and that ondemand would cause crashes.
Now they're saying the reverse.
Edit: Well, I switched it to ondemand as the app dev suggested and the phone turned itself off a few minutes later...
Are we suppose to flash it thru cwr?
Edit: nm I got it.
Sent from my SGH-T959 using XDA App
Argh, ever since I installed this (even after uninstalling it) my phone keeps freezing randomly while asleep!
synaesthetic said:
Argh, ever since I installed this (even after uninstalling it) my phone keeps freezing randomly while asleep!
Click to expand...
Click to collapse
Do you have a profile for screen turn off? If you do disable it because the phone itself lowers the cpu while at sleep.
Sent from my SGH-T959 using XDA App
I have no profiles set. I tried doing the sleep profile but it caused some annoying lag when the phone was waking from sleep.
On demand profile settings do not work, my phone has crashed 2 times. SetCpu just doesn't work I guess.
Using Nero V 3 and set CPU isn't doing anything...max setting is set to 1000.
How did you guys get it to work and what are your settings?
Sent from my Galaxy S via XDA App
Those of us using SetCPU are using overclocking kernels. Some folks might be using DOW, but I am using JAC XMOD because I'm still on Eclair as all the 2.2 ROMs annoy me currently.
(At least until I get my Bionix Blackout for Nero v3 theme finished!)
Could anyone please tell me the settings and profiles that will give my x10 mini the best battery save? thanks
actually there is already a preset for that ..the "powersave" one..
Easy, just put both bars in 122880MHz..
Your phone are going to be rrrrreeeaaaallllyyy slow, but you save lots of milliamps
Use ondemand only. And set min to 122 and max to 600.
I use a profile when screen is off that set min to 128 and max to 320, ondemand too.
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Has anyone had problems with random freezes and reboots with SetCPU installed? I've had a couple random reboots, so for now I've uninstalled SetCPU to see if the problem goes away. I also have Advanced Task Killer installed but it wasn't set to kill tasks automatically.
raiderkilo said:
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Click to expand...
Click to collapse
Setting SetCPU like that is not very smart. For example, You have Your screen off, someone is calling You, what happens? You get the call ringer after few seconds (sometimes even 10-15!). Reminds of old Symbian versions? But just this. Next example - You have Your screen off, and You receive sms. What happens if You are using Handcent, and have to go to the app manually after phone wakes up? It takes ages... But if You have more than 1000 massages in Your inbox, and a new one come, and You get it after screen wakes up it can even lead to a reboot.
Lets add some random weird situations if You are listening to Your player while the screen is off... using some third party apps, etc...
Setting the minimum CPU for the screen off is not a good idea. Don't do that, or the phone will fail You in most unwanted cases.
so what are you guys using?
I am 122-600 on normal ondemand
and screen off on 122-256 ondemand
Anyone with better profiles?
just dont overclock!!!
why not? I see you are running 729/600.
WHY is your min 600?
Use smartass governor - auto profile, just upgrade to gingerbread.. best profile yet..
Set normal use 122Mhz-729Mhz 100% Priority
Set for charging: 122Mhz-245Mhz (or similar) - 100% Priority
Set for screen off 122-245 (or similar) - 100% Priority
^ this saved me battery when I used my phone for so much else besides calling and texting.
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
achyut said:
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
Click to expand...
Click to collapse
Only a handful devices supports being clocked to 825Mhz but it's very dangerous.
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
ruifung said:
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
Click to expand...
Click to collapse
Some have succeeded, but I doubt their phones lasted very long after that.
Just wondering, is the phones processor under the right side of the keyboard? cause after a few minutes @ 710Mhz, that area is hot. Since I switched to the smartass governor, it rarely is hot anymore (due to the fact it mostly spends time @ 245/320Mhz
Um... question?
Shouldn't the phone go into deep sleep when the screen is off with no cpu activity?
Also install cpu spy and see what the cpu is doing for how long.
https://market.android.com/details?id=com.bvalosek.cpuspy
1. The cpu does not make the most heat... it's the 3G radio.
2. Cpu should deep sleep automatically.
My OC prifile for mini pro:
Standard profile- 122 - 825mhz
If Battery < 15% then 122 - 600 "this gets rid of crashes due to low power OC"
Also.. i asked some of the developers that made the modules for overclocking and undervolting.
It's undervolting there is no upward voltage bump so it can't really nuke a cpu.
But you can nuke the power circuits if you use heavy internet on 3G and charge at the same time.
How can I put over 600 Mhz?
My SetCPU makes 600 Mhz the max. I want to put just on 700, but I can't. What is the problem?
@Felimenta97:
You don't have any overclock-enabler module installed/insmodded or if using any CM-based ROM, the corresponding setting is disabled.
I'm using smartass with 122-320 for screen off and ondemand with 320-729 for normal, no problems so far
The max MHz I could get was 729MHz, 748MHz worked but after some time the CPU got 'pegged' as said in the logcat
Tried the 825MHz setting that only caused a freeze and boot loop, forcing me to do some fast adb commands to get rid of the overclock
I recently updated my stock SCH-i605 to JellyBean's ROM build 21, with saber kernel. Now, once or twice a day, it will freeze after it's been in low power / locked for 10 minutes or more. When I try to unlock it, the screen turns on, and it is frozen as the last image that was displayed (e.g. I set it down and let it go to sleep, or lock it, from the web browser, and it then shows the page) It's completely frozen, and won't do anything. The only thing I've noticed is that it will do a quick single vibrate after holding down the lock or home button for a second. The only way to fix it is to take out the battery, since no other button combos work, like the force reset/shutdown.
Has anyone seen anything like this? Any ideas on what could be causing it or how to fix it?
Raise the minimum cpu speed up from 100. Some phones can't handle that low. Use the standard 200mhz minimum and you should be fine
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Raise the minimum cpu speed up from 100. Some phones can't handle that low. Use the standard 200mhz minimum and you should be fine
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I did set the minimum speed to 100MHz it one point, but switched it back to 200 shortly after. I just double checked, and its still set to the default 200. What else could cause this?
Also, I've noticed that it only happens when I leave it at an app, it's never frozen at the home screen. I've mostly had it freeze at settings and in the browser.
Slovedon said:
I did set the minimum speed to 100MHz it one point, but switched it back to 200 shortly after. I just double checked, and its still set to the default 200. What else could cause this?
Also, I've noticed that it only happens when I leave it at an app, it's never frozen at the home screen. I've mostly had it freeze at settings and in the browser.
Click to expand...
Click to collapse
Have you undervolted or underclocked anything? Messed with the gpu speed? Used the touch wake features?
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Have you undervolted or underclocked anything? Messed with the gpu speed? Used the touch wake features?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I'd overclocked and enabled touchwake, but the issue was actually forgetting to disable the ripple effect in with the AOSP lock screen enabled.
Slovedon said:
I'd overclocked and enabled touchwake, but the issue was actually forgetting to disable the ripple effect in with the AOSP lock screen enabled.
Click to expand...
Click to collapse
Glad you figured it out buddy. Cheers. Glad to see it wasn't even saber. Good to know. btw we've all made that lockscreen ripple sleep of death on aosp lock screen error. You're not alone haha
Sent from my SCH-I605 using Tapatalk 2