Database Develop

[Q] Screen on Delay?

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...

[Q] SetCpu issues - freezes at max frequency

Hi everybody ...
I have a question regarding using SetCpu to a full potential and keeps on freezing whenever I set the clock to 1704 Mhz on main section of application. For your information regarding my GN
- LA4 ROOTED WITH CWM recovery ([ROM] [03.02] Chrack´s XXLA4)
and please refer to the screen capture of my about phone so you can see the kernel version etc... and also including the screen capture of the setting of SetCpu as well so anyone knows what I am not doing right in settings of SetCpu...
Every single time I set the clock to the max which is 1704 Mhz, m my phone freezes and had to reboot again !!.
Please carefully look at the screen captures and advice me what to do with these setting in SetCpu...
Thank you very much in advance !!

If it freezes, that means you've gone too high. Keep lowering it until you stop experiencing freezing.

@Seeker14491 --- YEAH thanks for your information much appreciated !

Performance profile crash

Hey guys,
at the moment I´m running up-to-date CM 12 Nightlies using stock kernel.
As stated in the title, my phone crashes when I select the "Performance" profile in the Performance Settings.
The phone does however NOT crash when I put the performance profile to "Balanced" or "Battery Saving"
The phone crashes a few seconds after I close every app and then put it into sleep.
I have got no changes made to any CPU settings.
I have not found any advice in making the settings work again properly by myself.
Not being able to use the "Performance" profile is not that big of a problem but at the same time it is pretty annoying, so I would be very happy if someone would share his knowledge about solving my problem.
Have a great day!

[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.

[TWRP ZIP] Underclock CPU without messing up mp-decision

First of all, all credits go to @Tomoms that kindly created the zip.
Our bacons are getting pretty old especially on the battery side. After using sultanxda rom that was underclocked to 1958 Mhz i noticed a nice improve of SOT without sacrificing performance too much .
Unfortunately, on every other ROM, changing frequencies trough kernel tweaking apps (ie kernel adiutor) results in Qualcomm mp-decision not behaving correctly, cores not going offline and frequencies scaling pretty much messing up.
This zip underclocks correctly your CPU to 1958mhz, without the need of any third party app, hope you ll find it useful.
Again, all credits go to @Tomoms

Let me add that the zip should be universal, that is, I expect it to work on all Oreo ROMs and probably on Pie/Nougat ROMs as well. If it doesn't work on certain ROMs, I'll update it to support all of them.

Flash it now. I'm running android 9 pie and it works for me. It reduces my overheating problem!!!!!
Thanks a lot!!!!!

Do you make GPU boost settings for gaming? i need this for not rooted phone.

@Tomoms can you make one For Oneplus 2.

Is this work on cyanogen os 13?

omgomgomg i was wondering about this for so long !
my fault for not checking this place for 2 years lol. I also used Kernel Adiutor which misbehaved at times, random overheating after settings failing to apply on boot, and noticed mdprecision erros in the logs
1958 MHz is also the frequency i used, how is this all a coincidence ^^
Is it possible to edit a value in the zip to underclock to 2.3 Ghz ? (i don't remember the exact number)
Not that i need it, just wondering. OPO currently pretty dead from weird cpu/power/battery issues, if this fixes I'll be ecstatic

so how do u make it back to default?

Can the number be set in the `anykernel.sh` file to any reasonable clock speed? such as 1750Mhz? Or does it need to be a specific multiple, or something?

sgtfoo said:
Can the number be set in the `anykernel.sh` file to any reasonable clock speed? such as 1750Mhz? Or does it need to be a specific multiple, or something?
Click to expand...
Click to collapse
It has to be a valid frequency of the OPO's CPU. You can find a list here: https://github.com/LineageOS/androi...174a0802/arch/arm/boot/dts/msm8974.dtsi#L1548

Not working on the microg build of lineage OS
The script runs fine with no errors but when I boot back to android the max CPU freq is still unchanged.
Not sure where I can find the debug log to post here,
Thanks.

ffff2 said:
Not working on the microg build of lineage OS
The script runs fine with no errors but when I boot back to android the max CPU freq is still unchanged.
Not sure where I can find the debug log to post here,
Thanks.
Click to expand...
Click to collapse
Updated zip that should work on newer ROMs:
https://mega.nz/file/VoURxIZD#l2bL5yS0cArj47ablsxHjuFLughHSPt1aORJR2F3T0k
EDIT: it underclocks all CPUs to 1,9 GHz, as in Sultan's ROM. Not tested but it should really work. If anyone tries it, please give me feedback

Tomoms said:
Updated zip that should work on newer ROMs:
https://mega.nz/file/VoURxIZD#l2bL5yS0cArj47ablsxHjuFLughHSPt1aORJR2F3T0k
EDIT: it underclocks all CPUs to 1,9 GHz, as in Sultan's ROM. Not tested but it should really work. If anyone tries it, please give me feedback
Click to expand...
Click to collapse
I had revived my account just to say thank you!
CPU frequencies seem to be working fine on most recent Lineage OS 17.1 and CPU info never shows usage above 1958 MHz.
It's amazing that this phone has survived 8 years, here's hoping it can survive 8 more.

Artos0131 said:
I had revived my account just to say thank you!
CPU frequencies seem to be working fine on most recent Lineage OS 17.1 and CPU info never shows usage above 1958 MHz.
It's amazing that this phone has survived 8 years, here's hoping it can survive 8 more.
Click to expand...
Click to collapse
What app are you using to check CPU clock speeds?

Artos0131 said:
I had revived my account just to say thank you!
CPU frequencies seem to be working fine on most recent Lineage OS 17.1 and CPU info never shows usage above 1958 MHz.
It's amazing that this phone has survived 8 years, here's hoping it can survive 8 more.
Click to expand...
Click to collapse
Can I flash the ZIP file through TWRP? How would I remove this app if necessary?

why new frequency not show? how to fix

Tomoms said:
It has to be a valid frequency of the OPO's CPU. You can find a list here: https://github.com/LineageOS/androi...174a0802/arch/arm/boot/dts/msm8974.dtsi#L1548
Click to expand...
Click to collapse
Tomoms said:
It must be the frequency obtained by multiplying 192MHz BCLK with the multiplier
Click to expand...
Click to collapse