Please don't eat me alive for this post. I just want to learn a bit. When I bought my s2 it came with gingerbread, everything worked super fine. And when the phone was lock and in deep sleep. I pressed the home or power button and the screen turned on very quickly. But then I move to ICS and i noticed the time of "waking up" is larger than it is on gingerbread while being in deep sleep. I tried stock ics and a bunch of other custom roms, Is it just me who notice this or this actually happens on ics?
Please don't reply with "move back to gingerbread" or something like that. I'm not complaining I just want to know if someone else feels this to....
~ ~
° °
----
plotinus said:
Please don't eat me alive for this post. I just want to learn a bit. When I bought my s2 it came with gingerbread, everything worked super fine. And when the phone was lock and in deep sleep. I pressed the home or power button and the screen turned on very quickly. But then I move to ICS and i noticed the time of "waking up" is larger than it is on gingerbread while being in deep sleep. I tried stock ics and a bunch of other custom roms, Is it just me who notice this or this actually happens on ics?
Please don't reply with "move back to gingerbread" or something like that. I'm not complaining I just want to know if someone else feels this to....
~ ~
° °
----
Click to expand...
Click to collapse
Yes, the average wake time on GB was about 650ms, in ICS its about 1000ms, this is how it works, there is nothing that custom kernel or ROM devs can do about the situation at the moment.
Home button lag has always been an issue, there is a fix for this issue incorporated into a a few roms and themes, maybe try one of them
what cpu governor are you using and are you on stock frequencies? I use 500mhz as a min (voltage diff between is 200 and 500 at lowest values is on 25mV for me) and this improved it slightly.. could be placebo though
viva.fidel said:
Home button lag has always been an issue, there is a fix for this issue incorporated into a a few roms and themes, maybe try one of them
what cpu governor are you using and are you on stock frequencies? I use 500mhz as a min (voltage diff between is 200 and 500 at lowest values is on 25mV for me) and this improved it slightly.. could be placebo though
Click to expand...
Click to collapse
I thought and read that home button lag refers to the moment I'm in an application and press the menu button to go to Home screen. The lag was because the phone kept waiting for another press to open voice commands. Am I right? I've read it somewhere around here..
And I've been using 200mhz min and 1200 max with ondemand governor. Stock values
~ ~
° °
----
plotinus said:
Please don't eat me alive for this post. I just want to learn a bit. When I bought my s2 it came with gingerbread, everything worked super fine. And when the phone was lock and in deep sleep. I pressed the home or power button and the screen turned on very quickly. But then I move to ICS and i noticed the time of "waking up" is larger than it is on gingerbread while being in deep sleep. I tried stock ics and a bunch of other custom roms, Is it just me who notice this or this actually happens on ics?
Please don't reply with "move back to gingerbread" or something like that. I'm not complaining I just want to know if someone else feels this to....
~ ~
° °
----
Click to expand...
Click to collapse
Which rom and kernel are you on?
Sent from my GT-I9100 using xda premium
I believe I read a while back in the CM9 thread, entropy512 said the 1000ms delay is hard coded deep in the ICS kernel code, and there is nothing much anyone can do about it, its up to Google.
Sent from my GT-I9100 using XDA
kilometers4 said:
Which rom and kernel are you on?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I've been on paranoidandroid, hidrogenICS, Epsilon project and stock ICS,fluxi kernel, siyah, speedmod, stock kernels and they've been the same. It's not much of a problem but I wanted to know if it was rom related or something else. Think I've found my answer thanks
~ ~
° °
----
TheReverend210 said:
I believe I read a while back in the CM9 thread, entropy512 said the 1000ms delay is hard coded deep in the ICS kernel code, and there is nothing much anyone can do about it, its up to Google.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Oh. I see, well, found my answer thanks for your help!
~ ~
° °
----
Try this way
its happend to me before and its gone !
if you have external SD card remove it and try again without it
i think the reason of this delay for me was the SD card .. it comes with 4 GB and class 4
i replaced it with 16 GB class 10 and everything is ok
if it was the same reason for you try any SD card with class higher than 4 .. class 10 recommended accurding to my experience
______________
if the reason was't the SD card .. i'm sorry because I'm trying to help
it only happens on ics its the way they have made it to save on battery
if you go to the market and get the the app called soft locker it will solve the prob :laugh:
JKAY's framework v 14.0 may help
jkay's framework has an option under set common lockscreen settings>> fast unlock
Related
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
Hello everyone. I am new to android and rooting ans these forums. Just bought a thunderbolt about a month ago and absolutely loving it. Being an iPhone jailbreaker, I immediately rooted my thunderbolt. So I've been playing around for the past few months and settled on cm7.
My problem is with lockscreen lag. When I click the lock button from screen on, the screen just very slowly dims out, much slower than when I ran stock or das bamf. Worse is that when I click the lock button from the blank screen soon after locking, it first shows what was on the screen for a second or two, then goes to the lockscreen. If I click the lock button from a black screen that has been locked for awhile, it slowly fades on before I can unlock it.
This is very annoying because I often lock then decide to unlock, and between the lock lag and unlock lag, I have to wait some 3 seconds. Dad bamf, stock, and omfgb all had very good lockscreen reaction time with no lag.
On the mr1 radio, cm7 rc0.6, tried rc1.1, same problem. Under timeout settings before screen goes to lock, I have both set to immediate. Furthermore I tried doing a complete wipe, dalvic, data, format system, reset battery, everything.
Is this normal or just my thunderbolt, any suggestions how to fix it?
LowFatBlood said:
Hello everyone. I am new to android and rooting ans these forums. Just bought a thunderbolt about a month ago and absolutely loving it. Being an iPhone jailbreaker, I immediately rooted my thunderbolt. So I've been playing around for the past few months and settled on cm7.
My problem is with lockscreen lag. When I click the lock button from screen on, the screen just very slowly dims out, much slower than when I ran stock or das bamf. Worse is that when I click the lock button from the blank screen soon after locking, it first shows what was on the screen for a second or two, then goes to the lockscreen. If I click the lock button from a black screen that has been locked for awhile, it slowly fades on before I can unlock it.
This is very annoying because I often lock then decide to unlock, and between the lock lag and unlock lag, I have to wait some 3 seconds. Dad bamf, stock, and omfgb all had very good lockscreen reaction time with no lag.
On the mr1 radio, cm7 rc0.6, tried rc1.1, same problem. Under timeout settings before screen goes to lock, I have both set to immediate. Furthermore I tried doing a complete wipe, dalvic, data, format system, reset battery, everything.
Is this normal or just my thunderbolt, any suggestions how to fix it?
Click to expand...
Click to collapse
Yeah, I had this same problem, but then I turned on the option for the tv animation on Device awake and it went away. It seemed much snappier.
Go to Settings > CyanogenMod Settings > Display > Screen-on Animation
Lag is probably from the cpu not kicking up to a faster speed in time to deal with the animation. Enabling that extra animation you mentioned most likely just gives it a little more time to kick up the cpu enough to stop the lockscreen itself from lagging.
yareally said:
Lag is probably from the cpu not kicking up to a faster speed in time to deal with the animation. Enabling that extra on you mentioned most likely just gives it a little more time to kick up the cpu enough to stop the lockscreen itself from lagging.
Click to expand...
Click to collapse
Yeah this is what I was thinking. So the animation is pretty much just a placeholder or something to look at (it still seems snappy with the animation on) until the CPU kicks in.
Yareally, so do you get this problem as well? How would you suggest I fix it? I am running imoseyon's lean minimalist kernel for cm7, its running at the "normal setting" which is undervoltes then overclocked to 1.41ghz. I've tried all the governors for it ondemandx, interactivex, smartass, all the same problem. Admittedly I haven't tried the stock kernel with "performance" governor. But I'm sure there are many people who use power saving governors who do not have to contend with this issue?
Sent from my ThunderBolt using XDA App
It's an issue with the kernel/kernel governor most likely and most of the kernels I believe for AOSP and GB Sense are based on Imoseyon's which from being on BAMF 2.x and CM that it's not the ROM's doing. The threshold for the cpu to raise the clockspeed on the initial wake of the lockscreen by default isn't enough to kick it up from 245mhz.
Pretty sure this issue has been around for quite a while, just most people (including myself) most likely figure the amount of effort to fix it would be more than the annoyance. Setting a profile to keep the min speed on screen off to 384mhz or whatever comes after 245 on the toggle scale would probably fix it, but obviously raise your clockspeed some. It could also be the undervolting while the screen is off is too low as well and so it causes it to lock up somewhat while the voltage rates go up a bit.
If someone hasn't mentioned it to Imoseyon or looked through the long thread of his Sense/CM kernel, then I would recommend doing that. I recommend reading first though. I've only tried his kernel and Nerozehl's but I know Nerozehl's was a fork of it and has the same issue. The governor settings are just a pain to deal with and it's probably something Imoseyon is already aware of, but just hasn't fixed it yet.
If you want to try a quick fix (for lag), use ondemandx and not the other governors. That might fix it right away.
The lockscreen taking a second to kick in though I think is a CM problem that will just get worked out eventually.
I have this too on the liquid aosp rom. I figured it was rom related because no kernel fixes it. I hope this gets fixed.
Turn Autobrightness off and try it for a while.
Mine did this until I updated to cm7 RC 1.5.2
Sent from my ADR6400L using XDA App
Absolute_Zero said:
Turn Autobrightness off and try it for a while.
Click to expand...
Click to collapse
i always have that off.... what kernel are you guys using?
fixxxer2008 said:
i always have that off.... what kernel are you guys using?
Click to expand...
Click to collapse
RC 1.5 is very snappy and seems to have fixed all the issues of lag. I would recommend trying that before anything else. I am not sure slayher updated it here yet, but if it's not, it's also on rootzwiki.
I am on CM7 and have never had that lag.
Sent from my ADR6400L using XDA App
yareally said:
RC 1.5 is very snappy and seems to have fixed all the issues of lag. I would recommend trying that before anything else. I am not sure slayher updated it here yet, but if it's not, it's also on rootzwiki.
Click to expand...
Click to collapse
Im not on cm7...im on liquid v2.6.
fixxxer2008 said:
Im not on cm7...im on liquid v2.6.
Click to expand...
Click to collapse
pretty sure he's pulling from the cm7 source, so technically you are
I am guessin whenever he pulls from the source again to update, it'll fix your issues.
Just wondering if there are any fixes out there for the lockscreen lag / delay that seem to be an ongoing issue in Samsung based ROMs.
For anyone not knowing what I mean, its the way that the homescreen appears briefly after waking the phone before the lock screen appears. Its not a big deal, but does look a little "unpolished". Its an issue, that, if I can fix, would solve one of my last remaining issues with the phone.
Try cm7,cm9 or miui. It wakes before you press home
Sent from my GT-I9100 using xda premium
I know they do, as I've tried them all... but I'm on a Samsung based ROM, and as I've got my phone set up exactly how I want it, I'll be staying on it. I'm using the Samsung based ROM because (shock horror) I quite like the way it looks, and is the most "fluid" / smoothest I've tried so far.
Any new about this delay?
Why is it happens? Maybe because the cpu clockdown or something so its take another second to wake the screen on?
PsyOr said:
Any new about this delay?
Why is it happens? Maybe because the cpu clockdown or something so its take another second to wake the screen on?
Click to expand...
Click to collapse
You can try to bump up the min to 500mhz
Sent from my GT-P7510 using xda premium
I'm trying to figure this out too,but no one seems to know the answer.
norpan111 said:
Try cm7,cm9 or miui. It wakes before you press home
Click to expand...
Click to collapse
What a load of BS. The S2 will always take at least 0.65 seconds to wake-up, no matter what Rom, kernel, whatever you use.
ionutz727 said:
I'm trying to figure this out too,but no one seems to know the answer.
Click to expand...
Click to collapse
Everybody knows the answer. There are countless threads already on this subject. Search for Entropy512 and his thorough explanation and don't believe people who say they have no lag.
Pfeffernuss said:
What a load of BS. The S2 will always take at least 0.65 seconds to wake-up, no matter what Rom, kernel, whatever you use.
Everybody knows the answer. There are countless threads already on this subject. Search for Entropy512 and his thorough explanation and don't believe people who say they have no lag.
Click to expand...
Click to collapse
I know there are many threads regarding this, I have myself one. One of my friends said to me that his s2 wakes up instantly after he presses the home/power button. It is also said that the new aokp roms solved this issue,and users reported this too. But there are others,like me, who still have the lag (1-2 seconds). So i guess i did something wrong with the installation of the roms or anything else. I can't figure it out.
Well,i tried both cm9 and miui roms and i still have the lag.
seems like it should be a 'lag' because the deep sleep mode, its save much more battery on idle..
i'v just notice it too, maybe it always was ...
correct me if i'm wrong...
PsyOr said:
seems like it should be a 'lag' because the deep sleep mode, its save much more battery on idle..
i'v just notice it too, maybe it always was ...
correct me if i'm wrong...
Click to expand...
Click to collapse
+1, ur very true ma8 as long as the phone is in perfect deepsleep mode this lag of 1~2 sec do remain and its nothing when compared to the better batt life with good deepsleep
PS- just check the same when ur phone is charging and u dont see that lag since its @ 200mhz always
PsyOr said:
seems like it should be a 'lag' because the deep sleep mode, its save much more battery on idle..
i'v just notice it too, maybe it always was ...
correct me if i'm wrong...
Click to expand...
Click to collapse
i know about deep sleep mode. but i don't understand why some people have this lag and others don't.
Maybe for them 1-2 sec ain't call 'lag'.
Until you'll see it in your own eyes, you could judge.. . I bet they didn't waited at least 10 sec to get into the deep sleep...
What I'm running:
Latest NEAK kernel + AOKP build 36.
Issue also occurred in Phonebricker + NEAK (sammy version).
My issue:
Occasionally the OS will get extremely slow, like you would expect if the phone were running at 100mhz or something. Everything continues to work, just reeaaallly slow. For instance, music playback gets very electronic-y as sounds are stretched out, tapping one of the capacitive buttons takes 5-10 seconds before vibration/feedback, and another 5-10 seconds before a menu pops up. I managed to get the NEAK configurator open and scrolled to the CPU tab, and it claimed I was at 1200mhz - though the phone didn't even get warm so I'm skeptical.
I'm guessing since I've done a full wipe between phone bricker + NEAK and AOKP + NEAK, the only thing in common are my apps and the NEAK kernel, so it stands to reason it would be one or the other causing this. My wife's GS2 is running AOKP + NEAK as well though and we haven't experienced this problem on it yet (but it's intermittent so it might be there, just hasn't happened yet). I'm currently running conservative governor + SIO, but it has also happened on conservative + NOOP.
While I could just change a bunch of sh!t and hope it goes away, I'm more interested in figuring out what's causing it, and fixing it properly. How can I figure out what's going on? What will log this kind of thing? What do you guys recommend?
Thanks!
this is really easy/simple. flash a different kernel. all devices are not created equally so you need to just try everything that we have and see which best fits your device.
if you had this issue on 2 different roms with the same kernel then you've answered this question in your post for yourself. it wasnt even necessary to post this dude. change kernels. done.
some phone like neak kernel, some phones dont. some phones like siyah, some phones dont. you cant "fix" that unless you get a different phone and try neak again. but even then it my not "fix" this issue because nothing is broken.
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Eckyx said:
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Click to expand...
Click to collapse
If you're undervolting when this issue is happening, change it back to regular voltage.
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Simba501 said:
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Click to expand...
Click to collapse
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Eckyx said:
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Click to expand...
Click to collapse
Stock & Siyah. My issue with it wasn't major; it just isn't as polished as GB. The difference is noticeable.
Sent from my Galaxy S2
When mine gets laggy, I usually pull out the battery and put it back after 10 min or so. If you are leaving the phone on more than 2-3 days at a time, that could really hurt the memory and phone performance. The phone usually runs on 300 mb but it will run about 700mb ram after 3 days (even force closing everything).
It is not mentioned so I just wanted to cover all bases
After posting about giving NEAK another try, I did. And within 10 minutes got an extreme lag slow down while typing. Didn't touch any settings kernel side. So I flashed siyah kernel and so far no problems. Sux too. I liked NEAK.
Sent from my SGH-I777 using xda premium
I have been running Siyah with Task's AOKP and have had zero lag and great battery. No UV or OC.
Sent from my SGH-I777 using xda premium
Posted this in NEAK thread but also posting it here:
I just installed the new AOKP, used kernel clean script and installed NEAK 2.0.5x, then went into the NEAK Pro config and changed my governor to Conservative and sched to SIO. Rebooted, opened Scramble with Friends and immediately got superlag.
Turning off the screen and waiting 20-30 seconds fixes it (long enough for the phone to go to sleep), but nothing else short of a reboot will help. I can leave it like that for an hour (if I don't let it sleep) and it'll still be uberslow.
Dear Comm
I am using my ACE since last summer, and am somewhat satisfied with it, especially since i use Link2SD.
Only thing bugging me regulary is a lag on the display - when i push the unlocker-key from the left to the right, i can see how the key is sliding over very choppy. And also switching from one homescreen to another is also very choppy (and somewhat annoying).
Later on again it can be ok again, sometimes, also when the phone has been locked. All very elegant and slidy - so a phone reboot won't solve the problem in general.
This phenomenon appears occassionally, no matter for how long the phone is running already.
I'm using this ROM: GingerReal 2.0
But i experienced this on the original Samsung ROM also...
I found a thread about this or a very similar issue here: click
But its just said that this is an general Gingerbread issue...
Can anyone confirm this and or give me a clue on how to solve this one?
Thanks all
Br Morph
TheMorpheus2000 said:
Dear Comm
I am using my ACE since last summer, and am somewhat satisfied with it, especially since i use Link2SD.
Only thing bugging me regulary is a lag on the display - when i push the unlocker-key from the left to the right, i can see how the key is sliding over very choppy. And also switching from one homescreen to another is also very choppy (and somewhat annoying).
Later on again it can be ok again, sometimes, also when the phone has been locked. All very elegant and slidy - so a phone reboot won't solve the problem in general.
This phenomenon appears occassionally, no matter for how long the phone is running already.
I'm using this ROM: GingerReal 2.0
But i experienced this on the original Samsung ROM also...
I found a thread about this or a very similar issue here: click
But its just said that this is an general Gingerbread issue...
Can anyone confirm this and or give me a clue on how to solve this one?
Thanks all
Br Morph
Click to expand...
Click to collapse
It's a problem with ace gingerbread roms
Sent from my HTC Explorer using XDA
To fix the lag when turning phone on, download setCPU and set the minimum frequency to 240
tomb20 said:
To fix the lag when turning phone on, download setCPU and set the minimum frequency to 240
Click to expand...
Click to collapse
Thank you tomb,
i will give it a try tomorrow ;-)
Gesendet von meinem GT-S5830 mit Tapatalk 2
like tomb20 said, set min cpu freq to 240 or higher [depends on you], bcoz like in unrooted stock roms, the phone goes down to 122 Hz, which causes the lag in waking up...
yesss! it's much better now - i set min mhz to 320 thow, since with 240 i still had laags sometimes.
[very recommended app]
//Edit @480 mhz for min. now - since i had screenlags with 320 also ocassionally...