Since upgrading to Lollipop, both Xperia Z and Xperia Z3 stutter on audio playback over bluetooth. It works fine for a minute or so and after it starts stuttering, UI becomes unresponsive and FC, and many times I had to reboot in order to properly use the phone.
I need someone to point me in the right direction with this kernel issue. SysCtl doesn't make too much sense to me.
[WORKAROUND 1 in the second post]
[UPDATE] After more digging I found out that the Bluetooth Stuttering issue is Kernel related and it affects other brands like LG, Motorola. Governor on BT headset/receiver, while streaming jumps from normal 384 Mhz minimum FQ to 702 Mhz locking on that Frequency and that's why I didn't notice any stuttering on the BT receiver. As soon as I changed the min Fq to 384 (as it should be) the choppiness began as soon as I turned off the screen.
>>So, Bluetooth Receiver on BT version 3.0+EDR - on normal conditions (Governor Interactive - min 384 max 1512) stutters on screen off;
>>Bluetooth Speaker on BT version 4.0 - on normal conditions stutters even more aggressive (1 second of music every 3 seconds of nothing) and crashes the UI and renders the phone barely usable until reboot.
>>Another Issue is with an app (music or bluetooth share) that on the first run changes the governor, and with the kernel policy on sleep mode.
??? A fix might be in Kernel policy or sysctl???
[UPDATE 2] I think I'm looking at the issue completely wrong. I don't think the CPU needs to be forced to keep cores active in sleep states but I think the bluetooth driver (must be in devices/platform) must be kept hogging resources in screen off. Anyone with a brilliant idea? I just discovered where the cpu settings are so not much I can do.
[UPDATE 3] [Workaround 2] Disabling MPDecision will keep all 4 cores running with no excessive battery drain - I had no stutter in 2 hours of playback and also The Min FQ didn't change. So now, when I go out, I either turn on the Partial Wakelock or temporary disable the MP Decision. I've got some help from kernel devs and I'll try playing with the hotplugs sometime next week and maybe come with a real fix. If anyone with enough knowledge of kernel wishes to participate I'd be really grateful.
I have very limited knowledge on Kernel and I really need help - I'm now learning stuff. But, I'll compare KitKat SysCtl to Lollipop SysCtl to see if I find something that might help understand the issue and maybe come up with a fix. On KK I never had this kind of issues. If anyone can help me on this please PM.
Maybe this help
Hello
I can remember that is had a lot of stuttering on bluetooth with a speaker or with music regularly what is did, was let the phone run a default 468 Mhz instead of 384 Mhz, after that the problems were over.
I dont know of this will fix it but you can try it
Sovjet-Command said:
Hello
I can remember that is had a lot of stuttering on bluetooth with a speaker or with music regularly what is did, was let the phone run a default 468 Mhz instead of 384 Mhz, after that the problems were over.
I dont know of this will fix it but you can try it
Click to expand...
Click to collapse
I noticed this yesterday while I was playing with the governor. On xperia Z governor settings were jumping to min FQ of 702Mhz which has a huge impact on battery. Even on trickster settings wont stick for long. So far the issue isn't related to SND_Soc audio mapping, it's the crappy kernel implementation on multiple devices running 5.02 (LG, Motorola etc).
Workaround 1
The cause is the kernel after all or at least as far as I know.
The workaround is about creating a Partial Wakelock so the cpu stays active after screen off with this app.
It works. No more stuttering. As for speakers that require high sample rate I just switched the cpu governor to performance (for the Z3 mostly). The partial wakelock should work especially on bluetooth headphones. I also found an app that ads partial wakelocks here's the link : https://play.google.com/store/apps/d...arken.wl&hl=en
SysCtl diff between KK; LL
These are Kernel differences discovered in the SysCtl file - comparison made betwen Kitkat (KK) and Lollipop (LL) are these of any help?
Fs.epoll.max_user_watches KK 169642 LL 164219
Fs.file-max KK 183359 LL 181926
Kernel.dmesg_restrict KK 1 LL 0
Kernel.msgmni KK 877 LL 851
Kernel.threads-max KK 28653 LL 28429
Bump
Sent from my SPH-L900 using Tapatalk
Bump any fix made?
superspeedz32 said:
Bump any fix made?
Click to expand...
Click to collapse
Well, I worked around the issue so further investigation wasn't really necessary since it would take a lot of time.
Here is what I know so far:
Bluetooth streaming works flawlessly with aptX devices
It's kernel related - and mp decision
This is my daily driver for music http://forum.xda-developers.com/gen...h-receiver-t3212201/post63021706#post63021706 which now works flawlessly.
MP-Decision, while music streaming, upscales the min cpu fq to 702mb which means the CPU will drain a lot of battery. So, with Trickster or the cpu app of your choosing, lock the min fq to 384.
To avoid the stuttering (if you're using interactive governor), set the hispeed_freq @ 1134mb and go_hispeed_load of anywhere between 85-90 % default values are too power hogging and what i'm usually trying is to find a ballance between decent performance and battery saving.
In my experience interactive has the tendency to overheat the device much faster, which is why I'm now using the ondemand governor, but since now i'm using an aptx receiver I hardly have any issues with stuttering.
Anyway, feel free to PM me for more infos.
App name
Sebi673 said:
The cause is the kernel after all or at least as far as I know.
The workaround is about creating a Partial Wakelock so the cpu stays active after screen off with this app.
It works. No more stuttering. As for speakers that require high sample rate I just switched the cpu governor to performance (for the Z3 mostly). The partial wakelock should work especially on bluetooth headphones. I also found an app that ads partial wakelocks here's the link :
Click to expand...
Click to collapse
What was the name of the app ? It´s not on the store anymore. Thx in advice
Tenshinryu said:
What was the name of the app ? It´s not on the store anymore. Thx in advice
Click to expand...
Click to collapse
Wake lock power manager. Although I don't have that problem since the last fw update. Package Name eu.thedarken.wl
It helped me a lot so feel free to try it
Sebi673 said:
Wake lock power manager. Although I don't have that problem since the last fw update. Package Name eu.thedarken.wl
It helped me a lot so feel free to try it
Click to expand...
Click to collapse
Thanks I have installed it, but maybe one of you could help me with this idea: I would like to have Tasker execute the Partial_Wake_Lock via the Wake Lock Power Manager when Bluetooth is connected
I have come so far that Tasker starts the Wake Lock Power Manager, but I don´t know how to execute certain routines within the started app. Any ideas ?
Maybe someone at least knows how to start functions within a app with Tasker ?
Thanks in advance
UPDATE: I´ve managed it by myself
For those of you interested how - here´s what you need: Root, Tasker, Execute Locale App :
In Tasker
> Set Profile Bluetooth Connected
Task :
1.Run Application Wake Lock
2.Input > Trackball > Down, 5
3. Plugin > Execute Locale > !Input keyevent 66
That´s it.
Tenshinryu said:
Thanks I have installed it, but maybe one of you could help me with this idea: I would like to have Tasker execute the Partial_Wake_Lock via the Wake Lock Power Manager when Bluetooth is connected
I have come so far that Tasker starts the Wake Lock Power Manager, but I don´t know how to execute certain routines within the started app. Any ideas ?
Maybe someone at least knows how to start functions within a app with Tasker ?
Thanks in advance
UPDATE: I´ve managed it by myself
For those of you interested how - here´s what you need: Root, Tasker, Execute Locale App :
In Tasker
> Set Profile Bluetooth Connected
Task :
1.Run Application Wake Lock
2.Input > Trackball > Down, 5
3. Plugin > Execute Locale > !Input keyevent 66
That´s it.
Click to expand...
Click to collapse
ha awesome dude. you basically manually started the activity. but automatically ))))
Sebi673 said:
ha awesome dude. you basically manually started the activity. but automatically ))))
Click to expand...
Click to collapse
Yeah, I dunno, but I didn´t like the thought of doing that manually all the time I´m using Bluetooth frequently
But, maybe I found another solution to my BT stutter / disconnect problem: I installed Proximity Fix and couldn´t test in my car or my speakers, but my Gear Fit didn´t disconnect until now, like it did before
Update: No, no, no didn´t fix my problem. Wether the proximity fix nor the Wake Lock solution. I also did a factory reset.. I´m really eager to reroll to 5.1.1.
Related
worked great for a while then kept force closeing anyone haveing problems??
It seems to be working fine for me. One thing is that when I set the clock to 128 or something, the status displayed on the widget still shows 527. The performance is significantly slowed so I assume it's doing it's job.
Overall I think it's a nice little widget. Great for maxing out performance, and maxing battery life by limiting performance.
Phone:
Black G1
JF 1.51
Yup...me too
I will make the change but it sometimes does not refresh the gui. It will also not work if you reboot. (if i remember correctly) also tons of force closes. I am on 6.01 and have tried JF1.5 and am curently on HERO but have not had success with the widgets on the build yet so I dont have a confirmation.
Could someone post the previous version of this app please? The updated version on the market shows "problem loading gadget" on the Hero rom when you add it to the screen..previous versions worked without any problems. Thanks in advance.
edit: nm..fixed it..just had to run the odex optimization script and all is good again
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
what is a good configeration for over clock..i dotn want to mess up my phone??
I was thinking the same and should I have it on always max. Or what?
I've got mine set to 128Mhz min and 527Mhz max, it has drastically increased my battery life. Batter life barely drops 1% overnight.
Anyone have the Version before the 1.7 update. The new update doesnt seem to work on hero w/ Rosie.
You can grab the 1.6 apk from the Dev's Google Site (check the Files section).
1.7 doesn't work with Ion for me either
zgmf-x322a said:
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
Click to expand...
Click to collapse
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
IronCross1788 said:
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
Click to expand...
Click to collapse
The creator of the original Overclock app hasn't updated his application for even Cupcake build support yet. I thought he removed it from the market.
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yeah NeoBlade (thanks!) gave me the tip on that one yesterday. Seems to be helping a ton.
Min384Max527
Screen off Min128Max245
I can't find Overclock Widget in Market, was it removed?
I have the Overclock Widget and my question is, is it bad for my phone that while my screen is on i have it a min 527 max 527 then while screen off min 128 max 245... I've noticed that phone charges last longer but the useage of going back and forth determental to the phone? Thanks
coolbho3000 said:
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
Click to expand...
Click to collapse
Thanks, that would be of great help. Specially the battery profile settings. If you could also put a monitor, be it a widget or something on the notification bar it would be beyond awesome, or maybe a just notification of when the speed is changed and to what it was changed to.
Does anyobdy know if this SETCPU works on Hero ?
And must the app be on after i set the clock or can i close the app after ?
*bump* need to know
My last effort of improving the ondemand governor by implementing a dynamic sampling rate did not work out as I hoped. Thus I did switch back to ondemand and, with a sampling_rate of 40000 and an up_threshold of 80, XviD playback with MobyPlayer was fine and also FLAC playback with MortPlayer was ok. However, as Morfic and others have noted the GUI feels a bit sluggish with these settings and suggested to try a sampling_rate of 15000. I tried this before, however with a lower rate, playback with MobyPlayer has serious problems with cracks and stuttering sound. Exactly this was the motivation to try and implement this dynamic sampling rate in the first place.
So the question is, why does a lower sampling rate lead to these problems? Since a smaller sampling rate means a greater flexibility and responsiveness, missing the point in time when the frequency should be increase cannot be the cause. Also the polling function which determines the frequency change is relatively light-weight, thus the extra CPU load for calling this function more often should also not be the problem. The only reason I could think of was that maybe switching the CPU frequency at these fast rates might be the root of the problem.
Thus I took the ondemand governor and implemented an additional parameter 'min_timeinstate' defining a minimum time the CPU will stay in a certain frequency state before it will be allowed to switch frequencies again. This way one can have a fine grained polling by setting the sampling_rate to a low value without running into problems with these fast frequency changes.
I did some extensive testing with a sampling_rate of 10000, min_timeinstate of 40000 and up_threshold of 90 and FLAC, mp3 and video playback all seem to work flawlessly. So it seems the root of the problem was indeed that the CPU does not handle fast frequency changes well.
I tested several apps and games and so far I have not found anything that this governor cannot handle. Thus I dare to say that it seems to be the superior choice over ondemand.
Test it, torture it, try to break it - I am looking forward to your feedback.
Changes to the source: http://www.pastie.org/2586936
BUGFIX:
Fixed compilation error with 'lazy' chosen as default CPUfreq governor.
Bug fix: http://www.pastie.org/2587040
BUGFIX #2:
Added sysfs parameter 'screenoff_maxfreq' which when enabled will cause lazy to always select the maximum frequency while the screen is off.
Bugfix: http://www.pastie.org/2775900
No further patches will be published here. I have set up a git repo for all my tweaks. Each mod has its own branch to keep the tweaks cleanly separated and one can simply pull the latest patches from the corresponding branch.
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/lazy
now this sounds interesting
Did you try building with lazy as default?
EDIT: builds fine as option, but not default. Too eager to try it to go fix code.
Oh, you are right. That does not work. I will fix it.
Bug fix: http://www.pastie.org/2587040
do we have to wait for this to be implemented in netarchy etc to use it .. ?
theallian said:
do we have to wait for this to be implemented in netarchy etc to use it .. ?
Click to expand...
Click to collapse
Yes, unless you can compile a kernel yourself you will have to wait. I do believe that there's a testing Trinity TEUV kernel by Morfic in his thread with the new governor as an option if you want it now.
theallian said:
do we have to wait for this to be implemented in netarchy etc to use it .. ?
Click to expand...
Click to collapse
Check trinity thread, there are 2 kernels with it and cooler colors, closer to voodoo punchy (if not exactly punchy)
Sent from my Nexus S using Tapatalk
awesome work ezekeel!
its running great here with the teuv kernel and the lazy governor. no complaints as of yet.
youll have to wait for it to be compiled into netarchy, or compile it yourself. you can try it already compiled into the trinity teuv kernel found here http://forum.xda-developers.com/showpost.php?p=17839805&postcount=4304
Yep it's working awesome so far. Using morfic's teuv with lazy gov.
Code:
diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index 2c00088..b03d1e1 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -357,6 +357,9 @@ extern struct cpufreq_governor cpufreq_gov_performance;
#endif
#ifdef CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE
#define CPUFREQ_DEFAULT_GOVERNOR (&cpufreq_gov_performance)
+#elif defined(CONFIG_CPU_FREQ_DEFAULT_GOV_LAZY)
+extern struct cpufreq_governor cpufreq_gov_lazy;
+#define CPUFREQ_DEFAULT_GOVERNOR (&cpufreq_gov_lazy)
#elif defined(CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE)
extern struct cpufreq_governor cpufreq_gov_powersave;
#define CPUFREQ_DEFAULT_GOVERNOR (&cpufreq_gov_powersave)
seems to do the trick
Hi Ezekeel, an observation in the trinity thread mentioned that some games lagged really badly, i think it could be with too slow changes, due to your time delay feature. I'm not sure if it's feasible, but maybe a solution to this could be a dynamic time delay, longer for the lower frequencies (suited for music while screen off) and shorter for the higher frequency (for these intensive games).
Now I'm not a kernel guy, although I do wish to learn at some stage in the near future. This is just the product of some quick thinking, I have no idea if it is a workable theory or if it would just cause overhead and create more lag. Please let me know what you think though!
Sent from my Nexus S
Been running the TEUV kernel with the lazy governor on since last night and here are a few of my observations:
1) Amazing battery performance. During heavy use with pretty much everything on and the screen at maximum brightness, I lost a mere 6% over a 30 minute period. Turn the screen down and back to normal use? 1% over 2 hours. Not to mention the fact that for the first time in a very long time my phone charged to 99% and when pulled off the charger stayed there for a good amount of time.
2) Upon booting, things stutter a bit. Most likely due to the fact that a lot of things are trying to start fighting for resources and since its a UV kernel, there isn't as much power to go around. Its not horrible like using my MT3G was but its noticeable. Also, there is, again just after boot, about a .25 or .5 second delay between pressing icons and the subsequent action happening.
3) After that initial slowness, it runs extremely smoothly. Like buttah, as mike myers would say.
All in all, I'm quite fond of this governor. I've tried UV kernels before on my phone and it tends to dislike them. Like random reboots and random bootloop, dislike them. Perhaps its the rom, perhaps its morfic's coding, or perhaps its just the governor. Whatever it is the collaboration is absolutely phenomenal. Kudos.
Jonathon Grigg said:
Hi Ezekeel, an observation in the trinity thread mentioned that some games lagged really badly, i think it could be with too slow changes, due to your time delay feature. I'm not sure if it's feasible, but maybe a solution to this could be a dynamic time delay, longer for the lower frequencies (suited for music while screen off) and shorter for the higher frequency (for these intensive games).
Now I'm not a kernel guy, although I do wish to learn at some stage in the near future. This is just the product of some quick thinking, I have no idea if it is a workable theory or if it would just cause overhead and create more lag. Please let me know what you think though!
Sent from my Nexus S
Click to expand...
Click to collapse
I just downloaded and tried the two games which were mentioned in the Trinity thread, Fruit Ninja and Air Attack, and I am experiencing no problems at all with the reference kernel from my sig set to 100/800. So until more people report such problems I am inclined to believe that these are not directly related to the governor.
kenvan19 said:
2) Upon booting, things stutter a bit. Most likely due to the fact that a lot of things are trying to start fighting for resources and since its a UV kernel, there isn't as much power to go around. Its not horrible like using my MT3G was but its noticeable. Also, there is, again just after boot, about a .25 or .5 second delay between pressing icons and the subsequent action happening.
Click to expand...
Click to collapse
I think that is normal. The GUI starts up before all programs and settings are properly loaded. For example if I open the app drawer directly after boot, only the stock apps are visible and after some seconds all my apps appear one after another. It takes about 10s after the GUI has started until everything is setup.
Ezekeel said:
I just downloaded and tried the two games which were mentioned in the Trinity thread, Fruit Ninja and Air Attack, and I am experiencing no problems at all with the reference kernel from my sig set to 100/800. So until more people report such problems I am inclined to believe that these are not directly related to the governor.
I think that is normal. The GUI starts up before all programs and settings are properly loaded. For example if I open the app drawer directly after boot, only the stock apps are visible and after some seconds all my apps appear one after another. It takes about 10s after the GUI has started until everything is setup.
Click to expand...
Click to collapse
I personally think your new governor is working great. Only time will tell if its better on the battery. I really hope so. I'm hoping for at least another hour of use. is it possible?
Sent from my Nexus S using xda premium
dsellers2 said:
I personally think your new governor is working great. Only time will tell if its better on the battery. I really hope so. I'm hoping for at least another hour of use. is it possible?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I expect the battery runtime to be similar to ondemand. On the other hand, I have made the experience that modifying governors is a delicate business and seemingly small changes can have an unexpectedly large impact. So as you said, only time will tell.
If the sampling rate is 10000 and the min_timeinstate is 15000, will the governor not consider load changes until min time is over, but at the normal sampling intervals? Which would mean an essential 20000 in this state?
I was looking through the patch on pastie right now, but opera closed twice, so I figured I ask you instead.
Sent from my A501 using Tapatalk
morfic said:
If the sampling rate is 10000 and the min_timeinstate is 15000, will the governor not consider load changes until min time is over, but at the normal sampling intervals? Which would mean an essential 20000 in this state?
I was looking through the patch on pastie right now, but opera closed twice, so I figured I ask you instead.
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
When the frequency is changed the next sampling will be performed min_timeinstate µs later, after that sampling with the normal rate is resumed. So in your example, the first sampling after a frequency change will be performed after 15000 µs, after that every 10000 µs.
Hi EZkeel your governor implemented the latest TEUV kernel has helped improved my battery life by close to 20!, was getting around 10hrs of battery with heavy use. About 3+hrs of screen time, display set to auto. Was able to run for 13hrs today.
One day of testing so far but I haven't seen my phone charge to 99% or last over 13hrs until I put the latest TEUV kernel with lazy in. Will continue testing throughout the week. No compatibility issues with the apps so far. Was running on demand governor previously and with the previous version of TEUV
Thanks for your work on the governor development.
robin_77 said:
Hi EZkeel your governor implemented the latest TEUV kernel has helped improved my battery life by close to 20!, was getting around 10hrs of battery with heavy use. About 3+hrs of screen time, display set to auto. Was able to run for 13hrs today.
One day of testing so far but I haven't seen my phone charge to 99% or last over 13hrs until I put the latest TEUV kernel with lazy in. Will continue testing throughout the week. No compatibility issues with the apps so far. Was running on demand governor previously and with the previous version of TEUV
Thanks for your work on the governor development.
Click to expand...
Click to collapse
Looking at your screen shots vs what mine is and my 2nd most is gallery. Very confused as to why this is
Sent from my Nexus S 4G using xda premium
you may have a corrupt media file , so everytime your device syncs it gets stuck. clear your files.
turn off device, remove battery for 2mins.; try again
possibly flag the directories you don't want scanned with .nomedia file (there's an app to do this)
anyways excellent job Ezekeel, 2nd day and lets see what happens with battery life.
Hi,
I am having an issue where the screen takes a solid 1-2 seconds to power on after the phone has been sleeping/idling. Sometimes it's not so bad but it's becoming quite annoying, and sometimes I think the screen turns off again before it can show the lockscreen and I have to pull out the battery to fix it!
Cm7.1 stable w/cm7 kernel. Was happening on stock too.
Does anyone know a way around this? Widgetlocker doesn't seem to fix it
Thanks.
i am having a similar issue on Topogigi's v1.9, no issue on his 1.4 version, very annoying!
noticed with Topogigi's ROM since v1.9:
This issue is even worse when a call comes in: The fon will vibrate about 4-5 seconds before the screen turns on to shows the caller. Until then you can not see whos calling.
On Horsepower rc1 kernel and topo 1.9 I can't say I have noticed this issue.
Used fon was already running on v2.0 with RC1 kernel.
Also did a clean flash of the rom again to eliminate possible issues of other apps running. But this has no effect on the problem. It still persists: When a call comes in, the fon vibrates up to 5 seconds before the screen turns on. Even then, you first see the unlock screen and about a second later the screen with the incomming call. Reproducability 10/10 times. Notice that vibration for incomming calls has to be set as "always on" in settings to reproduce problem!
Extremely annyoing because call can not be answered or dismissed while fon keeps ringing! Already missed calls because called hung up before screen unlocked.
Don't know if its a kernel or rom issue...
Advice
The best way for you not to have troubles is to pick a stable rom and flash it!
If you are on Topogigi ROM, This has already been explaine in the FAQ.
Topogigi said:
Ladies and gentlemen, guys and gals, experts and noobs, here you will find a F.A.Q. collection for our ROM. Hope it will help.
Q6.But I'm still experimenting lags with overclock daemon on wakeup: how can I tune it to fit my needs at best?
A6.One of the best features of overclock daemon is that you can tune it as you like. If you don't want to see lags on wakeup, just raise a little the max frequency for sleep profile. If you want to mock SGS2 owners with astonishing Quadrant scores, raise the frequency to the max for wake profile and your phone will turn into a raging bull. It's up to you. Your interest is raising? Let's see how to do it:
Fire up ES file explorer (you will find it in my rom beginning with v. 1.6 release), open settings and check "Use Root Mode" and "Mount Filesystem" (you need to do it only once). Then exit settings and hit the highest icon on the left: you will be in the root directory of your phone. Navigate to /etc/andrev_oc, you will find six files there:
-sleep_gov: indicates which governor to use during sleep mode ("performance" or "powersave")
-wake_gov: governor for awake state ("performance" or "powersave")
-sleep(or wake)_max: max frequency to allow during sleep or wake (see frequencies below)
-sleep(or wake)_min: min frequency to allow during sleep or wake (see frequencies below)
Here there are the frequency values available on current kernel (Neoblaze 28092011):
1408000
1216000
1100000
1015000
800000
503000
389000
216000
Make your changes to the files listed above and save them.
Since overclock daemon is already up and running and it monitors these files at every screen state change, it should be enough to hit the sleep button, wait some seconds, and hit it again to wake your phone. Your new settings will be applied immediately.
You may want to check the actual CPU frequencies by using OS Monitor or SystemPanel App (download the freely from the Market).
Click to expand...
Click to collapse
Look in my signature. Download the Andrev OC app.
Set asleep maximum frequency to 800 or 1016.
Problem solved.
There is also an app for the Topogig ROM http://forum.xda-developers.com/showthread.php?p=18273457#post18273457
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
Hahaha, same timing
Problem solved here like described. Thank you guys!
p.s.: I really appreciate the work of topogigi and spica for roms and kernel. They run 1000x better than the stock roms so I would never follow an inappropriate advice to fall back on those. Must be the urge to reach the amount of 10 posts for some ppl to get access to the dev area...
hi, I have an N7000 with slimkat 4.4.2
sometimes the phone stops working (is like if some app is overloading) and starts heating so much that I need to remove the battery to restart the functionality (with almost 10% battery gone in the process)
Is there any app or any way to check if some service is running too long or is taking too much CPU and stop or restart it?
I ve had the same problem it comes from s bad cpu clocks setting.
Try to do a small underclocking.u will have more battery life and you'll have less cpu freezing. ( this was how i fixed this problem on my phone
My phone Gt-I8160 With Cm11 Developed by team canjica
My works : my YouTube Chanel called rubend447 ;D
If u want somethink : ask me, no problem.
thanks, should I pick any of the various app that can manage cpu freq or do you have one suggested for this problem?
zazolo said:
thanks, should I pick any of the various app that can manage cpu freq or do you have one suggested for this problem?
Click to expand...
Click to collapse
there are two paid apps (set cpu and faux 123 but i dont like them.) i prefer rom tolbox that works fine and has a lot of freatures.
Hello guys, how are you?
I would like to ask if you also have the same "problem" with your nexus 6. First of all, I come from an OnePlus One which was very smooth . I used to run CM + Franco Kernel but even stock CM (11 or 12) run nicely on it.
Now I'm using a Nexus 6 with the stock rom and the latest version of franco kernel (r26) but, for example, when I swipe the multitasking windows, I can see clearly a lag especially with the last one. Scrolling up and down is also laggy sometimes. Are you experiencing the same? I am running without the encryption and I already tried to disable Fsync; the launcher is the Google one.
Do you have any other sugestions?
Regards,
Rafael
I had this issue on Franco kernel. I went back to stock and the lags went away and battery life almost doubled
I have small lags here and there (sometimes seconds long freezes) but that's mostly due to me messing with kernel settings, trying out custom kernels and nightly ROM builds.
where you able to find out what was causing the lag and how to fx it? im having the same issue.
angourakis said:
Hello guys, how are you?
I would like to ask if you also have the same "problem" with your nexus 6. First of all, I come from an OnePlus One which was very smooth . I used to run CM + Franco Kernel but even stock CM (11 or 12) run nicely on it.
Now I'm using a Nexus 6 with the stock rom and the latest version of franco kernel (r26) but, for example, when I swipe the multitasking windows, I can see clearly a lag especially with the last one. Scrolling up and down is also laggy sometimes. Are you experiencing the same? I am running without the encryption and I already tried to disable Fsync; the launcher is the Google one.
Do you have any other sugestions?
Regards,
Rafael
Click to expand...
Click to collapse
phyba said:
I had this issue on Franco kernel. I went back to stock and the lags went away and battery life almost doubled
Click to expand...
Click to collapse
brando56894 said:
I have small lags here and there (sometimes seconds long freezes) but that's mostly due to me messing with kernel settings, trying out custom kernels and nightly ROM builds.
Click to expand...
Click to collapse
aniel300 said:
where you able to find out what was causing the lag and how to fx it? im having the same issue.
Click to expand...
Click to collapse
@ ALL who have this problem:
i had it too, and i was thinking that i have been the only one..went crazy because i didnt find the reason for this.
Solution:
1) You need the paid version of FKU
2) Open FKU, go into "CPU Manager"
3) Go into Governor Control
4) click on "input_boost_duration"
5) Change the value to: 1000000
6) Turn the button on for set on boot (so this value will be saved and applys again after a reboot)
7) then reboot the device, and voila
explanation:
on the stock kernel there is following setting:
if you touch the display, the Cpu will stay at 1497 Mhz for 3 Seconds and thats the reason why stock is smooth!
Franco changed this value for saving battery. his standard value is 0.04 Seconds on 1497 MHz, then it goes down to 300 if the cpu dont has to handle something.
So for example: if you scroll in the settings, and the CPU frequency goes so quickly down (after the 0.04 secs) there will be stutters
and with the 7 steps i mentioned above, you change the boost duration to 1 second. This means the device will not lag, because the CPU stays for 1 sec on 1497 Mhz and the battery impact isnt that big!
Please try this out and respond to me if it helped
aniel300 said:
where you able to find out what was causing the lag and how to fx it? im having the same issue.
Click to expand...
Click to collapse
Turns out, most of my problems were caused by the "Deep Darkness" CM theme. Builds of BlissPop and BenzoROM would be fine for a little while and then start to screw up, getting pissed off I would boot into CleanROM which didn't have any themes applied (I use MultiROM) and everything would work as expected for hours, no lags at all! I decided to switch to another theme in BlissPop to test my theory and voila no more lag!
GregNexus said:
@ ALL who have this problem:
i had it too, and i was thinking that i have been the only one..went crazy because i didnt find the reason for this.
Solution:
1) You need the paid version of FKU
2) Open FKU, go into "CPU Manager"
3) Go into Governor Control
4) click on "input_boost_duration"
5) Change the value to: 1000000
6) Turn the button on for set on boot (so this value will be saved and applys again after a reboot)
7) then reboot the device, and voila
explanation:
on the stock kernel there is following setting:
if you touch the display, the Cpu will stay at 1497 Mhz for 3 Seconds and thats the reason why stock is smooth!
Franco changed this value for saving battery. his standard value is 0.04 Seconds on 1497 MHz, then it goes down to 300 if the cpu dont has to handle something.
So for example: if you scroll in the settings, and the CPU frequency goes so quickly down (after the 0.04 secs) there will be stutters
and with the 7 steps i mentioned above, you change the boost duration to 1 second. This means the device will not lag, because the CPU stays for 1 sec on 1497 Mhz and the battery impact isnt that big!
Please try this out and respond to me if it helped
Click to expand...
Click to collapse
BEEN SEARCHING FOR A SOLUTION TO THIS FOR DAYS NOW AND THIS WORKED! THANKS! :good: