Database Develop

[Announcement/Update] SetCPU Profiles w/ Manhattan Kernel

First of all, for anyone who has not yet tried the new Manhattan Project 1.6ghz kernel by Team Whiskey, i suggest you do so (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=821514). It is currently in alpha but so far has gotten outstanding feedback. Ive personally been running it and I'm not looking back.
Up until now its been well known that SetCPU profiles not only dont work on our phone, but also causes crashes and severe instability. However, SINCE I FLASHED THIS NEW KERNEL (and running Bionix Fusion 1.1), I have successfully profiled my phone. Here is what I've been running all day with absolutely no issues, and my phone running like LIGHTNING:
Main: 1600-200 Conserv.
Screen Off: 200-200 Conserv.
Temp > 50: 800-200 Conserv.
I posted these results in the kernel forum, but I also wanted to post them here for everyone to see because i know that the lack of SetCPU profiles has been a major complaint around here. If anyone would like to try this out and verify that it works for them also with this kernel, please post here, so everyone can finally enjoy the beauty of overclocking AND underclocking.
Once again, I'm running Manhattan Project Kernel and Bionix Fusion 1.1

Outstanding!

Appreciate the profiles. Should be a great help. I personally lowered my Temp to 40c but thats just my opinion

Excited to get the running will tell results soon!

So had my phone sitting for a bit, it became unresponsive and i think it had something to do with the sleep profile. I went ahead and changed it to 400/200 conserv for testing.

Awesome. But is the set on boot option still not working?
Oh and just an educated guess bit I would figure no Voodoo on this kernel. So disabling just in case before I update

YatimaMeiji said:
Awesome. But is the set on boot option still not working?
Click to expand...
Click to collapse
i dont even bother, its not really needed....even if its unchecked yoru settings are preserbed upon reboot
----------------
UPDATE #2: after 5 hours of no problems my phone finally started crashing, so i have may have spoken prematurely. But I'm stubborn, so Im still gonna try every damn combination possible until my phone tells me to go f*ck myself haha

I will post my feedback as well...
OP, are you running any lag fixes?

drizze99 said:
I will post my feedback as well...
OP, are you running any lag fixes?
Click to expand...
Click to collapse
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work

With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.

TopShelf10 said:
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
Click to expand...
Click to collapse
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz

jnp1974 said:
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
Click to expand...
Click to collapse
probably not going to help, but i certainly hope it does!!!

TopShelf10 said:
probably not going to help, but i certainly hope it does!!!
Click to expand...
Click to collapse
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
EDIT: I was testing different benchmarks with scaling on conservative, on-demand and performance to see if they altered my benchmark results. The difference was minimal, but I forgot to change scaling back to conservative and it wouldn't wake. When I pulled the battery, rebooted and checked SetCPU, it said conservative, but was stuck on performance. Changed to on-demand, left SetCPU, back in and changed to Conservative. It worked.

jnp1974 said:
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
Click to expand...
Click to collapse
dont be fooled, it can often work for a while before it shows its ugly side, be patient

I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
edit: for screen off don't be so stingy trying to set it to 200/200, if you need more battery life then get a bigger battery or spare batteries or Juice Defender , I usually set it to 200/800 and I have no issues.

TopShelf10 said:
dont be fooled, it can often work for a while before it shows its ugly side, be patient
Click to expand...
Click to collapse
I was fooled, ditching profiles altogether, boo

Can conferm that both profiles and set on boot work.
Sent from my Vibrant.

Mouahmong said:
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
Click to expand...
Click to collapse
i never check set on boot....what are your profile settings and what ROM/kernel are you running?

OK, I don't have mine OCLF yet but so far so good.
I have run Sleep profiles of 200/200 and 400/200 and the phone wakes up every time. I have gotten a txt message as well during my test and the screen lit up just like Bionix should! Will continue to kep messing with it....

turbosix said:
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
Click to expand...
Click to collapse
if it does so automatically then why is there an option to adjust "screen off" values?
Setcpu automatically scales between the high/low you set. SO if you let the main value stay at 1600-100..when the screen is off it will scale at a lower value of course cus you're not using the phone..but it wont stay at 200, because it has a Max of 1600! So depending on background processes it could scale back up to 4 or even 600 while screen is off
MY suggestions:
Download superpower battery saver from market, tweak to turn data on/off with screen and force ondemand cpu scaling
Download Autokiller--donate to get extra functions-- and set the value to Extreme or Ultimate when screen is off and Moderate or Optimal when it is on
I did that without setcpu profiles and it took 4 1/2 hrs to go from 81 % to 70
Im running Fusion 1.1 w/ Manhattan Project

[Q] Slow Screen Wakeup on Nameless ROM

Hi Guys,
After installing Nameless ROM nightly updates, I experience slow wake up screen problem.
Sometimes it takes good 3-4 seconds after pressing power button to wake the phone up and after it wakes up, suddenly goes to sleep mode. And if I now press power button, it wakes up in 1-2 seconds. Quicker than before, but still not the quickest.
Also, when phone rings most of the time it takes 5-6 seconds for screen to wake up and sometimes by the time you try answering/rejecting call, call has been missed.
I am currently on nameless-4.4.2-20140308-p880-NIGHTLY update.
Has anybody on LG Optimus 4X HD experienced this issue? Going through other forums, I also tried removing SD card and checking if this improves wake up time, but no joy.
Please shed some lights.
Thanks.

Same problems here. Never misses a call because of it though. I believe a way to decrease the time to wake up is to increase the CPU screen off values. This can be done by changing kernels and using trickster and all that, but I'd like to be able to do it from within the ROM. I asked the developer (@Evisceration) if he could add CPU screen off settings to the device control section. He said he liked the idea, so hopefully we'll see the function somewhere in the near future!
Sent from my Nexus 7 using Tapatalk

Nameless
Nameless has many bugs ... I was not happy with it ... I'm sorry for the developers work..

Flash iodak kernel to fix it
Sent from my Nexus 5 using Tapatalk

romulandu said:
Nameless has many bugs ... I was not happy with it ... I'm sorry for the developers work..
Click to expand...
Click to collapse
Hardly any bugs at all for me. If you encounter bugs on a ROM, it will be greatly appreciated if you report them to our devs so they can try to fix things!
This particular 'bug' (not really a bug though) is just due to a relatively low Max CPU Screen Off Freq and can be easily avoided by using another kernel or upping the freq if the current kernel supports it.

[Q] [OMNIROM] Phone takes long to wake up / screen does not light up

Hi folks,
I am using the latest (20140908) omni rom nightly build and I have the following issues:
I am getting called (ringtone) but the screen stays black for 5-10 seconds
Alarmclock: when it goes off, the screen stays black and i can't switch it off (very annoying)
Screen takes 2-3 seconds or more to light up after I press the power button
Any ideas on that?
Thanks!

adam recommends (well, used to, not sure if it's still the case) that you use a custom kernel, and he mentioned iodak's few times. remember to set max screen off frequency to 1ghz or so via trickstermod, so the device won't lag (default is 475 mhz which isn't quite enough) with wake-up when screen is off

Thanks, I'll try the frequency fix first (I have no modifications there whatsoever) and if it's not helping go with mourta kernel.

aktentasche said:
Thanks, I'll try the frequency fix first (I have no modifications there whatsoever) and if it's not helping go with mourta kernel.
Click to expand...
Click to collapse
you're only able to change screen off frequency on iodak-based kernels (mourta, iodak, cyodak, mahdi), not stock omni. good luck

I personally use Tasker to set performance governor for 5 seconds when a call comes.

That is also an interesting idea. I'll see how the phone performs with the next incoming call and if the problem still occurs I'll try it.
Until now I installed mourta 02/09 and I'm using abyssplugv2 governor. It does not have a max screen off frequency but the smoothness is much better already.

aktentasche said:
That is also an interesting idea. I'll see how the phone performs with the next incoming call and if the problem still occurs I'll try it.
Until now I installed mourta 02/09 and I'm using abyssplugv2 governor. It does not have a max screen off frequency but the smoothness is much better already.
Click to expand...
Click to collapse
I've the same problem on cyanogenmod with stock cm kernel. When i install another kernel such as iodak my 4x is faster and smoother. Try to install iodak and set the min cpu freq to 475mhz.

[Q] Small lags here and there

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:

[Fix] Lollipop Bluetooth Speaker stuttering Xperia Z, Z3 [Kernel Devs please help :)]

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.