yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] Pangadaywalker:
I get a lot of juice when in deep sleep this way. 3 days with my usage is ok. 2 days when I get to browse a bit more. So it makes a huge difference for the way I use the phone.

---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------

-don't use xposed (never used)

-don't uv (don't do it)

-don't oc (never did)

-set gpu min to 320 mhz (just set but I believe minimum was 200mhz)

-use default hotplug (changed from optimized to this)

-try interactive governor if you have constant reboots (will wait to see what happens with above changes).

-if all fails make a fresh cm12.1 install - will do if everything else fails.
[Galaxy S 5 Original Android Development] djdana:
Not having a single reboot om V2 beta 2.running stock CM
[Galaxy S 5 Original Android Development] andip71:
Thanks.

This is in line with my experience. An pretty much up-to-date stock CM (not older than 2-3 days) is quite a guarantee for a stable system.

Andi
[Galaxy S 5 Original Android Development] andip71:
New beta

Hi all,

before I disappear over the weekend, a last update. Just maintenance, but might be important for system stability, so I would recommend to flash it.

Version 2.1-beta3

Note: Only for CM nightlies of 14.05. or newer (and custom roms having these new changes in)

12.06.2015

Kernel start script optimized again (apparently was too aggressive for some phones)

Enjoy

Andi
[Galaxy S 5 Original Android Development] Pangadaywalker:
Flashing just in case. :)
[Galaxy S 5 Original Android Development] Pollie81:
Probably uv and xposed **** what's causing all the reboot issues. As i mentioned before, i never had any reboot issues. I'm still loving your kernel as i always did! Good luck to you and your wife of course.
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Never had a reboot with your kernel.
[Galaxy S 5 Original Android Development] ZaneZam:
not even with zzmoove? would be great though :)
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Had zzmove and performance profile with 2 cores min for a few hours and no reboot.

Stock cm12.1 here. No xposed or other bs ;)
[Galaxy S 5 Original Android Development] HorstiG:
Or buy a Winphone :D
[Galaxy S 5 Original Android Development] andip71:
Baaaaah ?
[Galaxy S 5 Original Android Development] Fireworkerfp:
Settings?
[Galaxy S 5 Original Android Development] superleeds27:
Zzmove

Yank battery plus

Zzmove native hotplug

UV 25mv

GPU

Simple on demand

27-462

Row for both

1024 value

Touchboost - 1190
[Galaxy S 5 Original Android Development] Matthias1968:
Nightly 03.24 and Boeffla runs like hell. Very smooth. Best Kernel for me and my S5.

Gesendet von der Ruhr
[Galaxy S 5 Original Android Development] ScratMan38:
I kept playing with Swipe to Wake and Double Tap to Wake, and I could see that when in my pocket, my phone was active most of the time. Ratio was almost 20% Deep Sleep and 80% Active.

After setting wake gestures to Off, the ratio became 80% Deep Sleep, 20% Active.
[Galaxy S 5 Original Android Development] andip71:
Check which process caused this by using BetterBatteryStats.

My deep sleep with wake gestures on is still > 90%.

Andi
[Galaxy S 5 Original Android Development] Jakkomo77:
Hi all , my deep slepp with diffrent Roms are over 96- 98% .

now on new build CM12 99.24 %.

With gesture the slepp are 93.4%.

The Kernel is good , no Problems
[Galaxy S 5 Original Android Development] Gassity:
Guys, could you be so kind to share your optimal settings for the kernel with screenshots?
[Galaxy S 5 Original Android Development] ScratMan38:
I suppose you don't put your phone in your trouser's pocket with screen facing 'inside' (so screen in contact with your leg) ?

I made the trial with Swipe to Wake with phone left in my pocket for 1 hour :

* Case 1: phone in my pocket, screen next to my leg : Deep Sleep = 48%, Awake = 52%

* Case 2: phone in my pocket, screen facing outside, battery next to my leg : Deep Sleep = 94%, Awake = 6%

It seems the screen is detecting my leg and it triggers an interrupt. I can clearly see some "event" wakelock and synaptics processes draining the battery with Case 1.
[Galaxy S 5 Original Android Development] andip71:
Ok, might be if you do not use a case at all.

Well, then this touch function is not good for you. So in your case I recommend you do switch it off.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Yes, and that's why it would be nice to have the "single touch to wake" feature with timeout as in i9300 for easy wake up when the phone switches the screen off.
[Galaxy S 5 Original Android Development] andip71:
Yep, as you said "nice to have".

I can look into that, but without priority really. I also consider it as "nice to have", because all modern phones like OnePlus, LG etc. work the way it is implemented now.

Let's see what the future brings.

Andi
[Galaxy S 5 Original Android Development] XDAMaxe:
Hi Andi again ;)

what do you think about another 'nice to have' ?

.... erm, imo it is in fact more than that: I wanna focus on the (sammy neglected) UMS mode which was implemented in your S3 kernel and one could toggle within your config app. Any plans ?

btw: cm11-kernel is still running fine on 4.4.4-carbonrom while still experimenting with govs & schels - but so far I tend to stay with my all-time-favorite gov zzmoove with yanks extreme batt profile - [MENTION=3279788]ZaneZam[/MENTION] I love you too ... :o
[Galaxy S 5 Original Android Development] andip71:
Not possible. Samsung removed that "backdoor" that still worked on the S3 in newer roms.

They removed it already with the Samsung 4.4.x roms for other devices :(

Andi
[Galaxy S 5 Original Android Development] XDAMaxe:
ah, didn't know that this refers to custom roms+kernels too.

Seems to be Samsung's next step to castrate users choice how we use our phones - now I'm starting to believe why you don't use Samsung as your daily device. Anyway thanks for the information.
[Galaxy S 5 Original Android Development] andip71:
There is no way I will go for another Samsung in the near future anymore when I have the choice.

Unless they come back and remove all the bloat, unneccessary "security features" and change their attitude to make their devices developer-friendly again.

But to be fair: It is a Google limitation here, not Samsung. Also no way for UMS on the OPO at the moment...

Andi
[Galaxy S 5 Original Android Development] HorstiG:
3 days trial with Blisspop, Fusion and Temasek.

Mobile runs excellent, without any problem. :good:
[Galaxy S 5 Original Android Development] FlemishDroid:
Great to see you here. I used your Boeffla kernel on my S3.
[Galaxy S 5 Original Android Development] aegeuss:
This kernel works very well with official 25/03 nightly for 900f.

Thank you my Lord ;)
[Galaxy S 5 Original Android Development] DeKiesel:
Just to share my experience:

Great kernel, runs very smooth and battery life seems to be good. I came from KT as well and deinstalled the Ktweaker and Kmonitor via TiBa.

I use the smartmax governor and undervolted by -75v (-100 gave me reoccuring reboots) alspo multicore powersaving is on. Otherwise I use what Lord Boeffla said he was using a few pages earlier.

One question [MENTION=947981]Lord Boeffla[/MENTION], why does your kernel include multicore powersave if you recommend not using it? Just curious.

All in all I am very very happy with this kernel.
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Good morning ;)
[Galaxy S 5 Original Android Development] andip71:
Morning too.

Off and over ☺
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Have a great weekend ;)
[Galaxy S 5 Original Android Development] !crazy:
It is not right what he said. 320 is not the lowest frequency set by Samsung, but default idle frequency. It was like that on S4, and almost all kernels CM and Sammy based. The frequency drops to 200 here and there, but most of the time is spent on 320.

Wanted to say, reboots definitely have nothing do to with the low GPU frequency. I have tested that for a while, and I actually use your 27 MHz as the lowest for GPU, and I get no reboots, for days already, if I use interactive. I'm stick to it, because it is a great governor, and your performance settings for interactive is just how I configure interactive with few small lrrelevant differences.

Good that you have suggested people do disable dynamic file system, not because I think it could be a reason for reboots (it is definitely not. It is always off here, and I will get reboot soon - matter of hours - after switching to inteliactive.) but because people could lose data, or even damage file system if reboot happens while dynamic fs is on.

---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------

No UV, no exposed, and I always get reboots with other governors than interactive.

I still have to update my system and kernel to more recent one. Kernel is from 8th of June, CM 9th.

---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------

Seriously, fee hours and you think you have checked something? It can take 19 hours, or even a whole day without reboot, it is not people claim they have reboots every fee minutes. I presume you never leave system 'in ruhe' for longer than hour. You should consider that before advising people about stability/reboot issues.
[Galaxy S 5 Original Android Development] Gassity:
Confirm. Second day with Xposed+ -75mV UV + tripndroid + even 2800mhz cpu on interactive - no reboots at all. Latest AICP, latest Boeffla Kernel.

Other than that I've noticed that overclocking to 2800mhz gives even less antutu points than the stock one + when I'm on -25mV undervolting - it's more points in antutu again than on the stock voltage. Wth?
[Galaxy S 5 Original Android Development] !crazy:
Why is that strange? OC doesn't make wonders. When CPU overheats it throttles and runs on lower frequencies than if one uses lower highest frequency, which cpu can handle.

Every cpu unit is different. Some phones can maybe run 2.8 GHz without issues, even with performance governor, other cannot.

If you want to check how well your cpu can handle a frequency, just switch governor to performance and watch. Cpu has other methods to save energy and lower heat, like C states, so you'll probably notice it is not at all so bad or power hungry (performance governor I mean. I use it sometimes as a daily.), but the main reason I have mentioned this is that you actually have to stress the cpu. Switching to performance, and than doing nothing, or only tasks which are 'easy' will not help checking how good your cpu behaves on highest frequency.
[Galaxy S 5 Original Android Development] andip71:
Oc can lead to cpu heating up quickly. This triggers thermal throttling and then perfect is even worse...

On the dynamic fsync part: strong disagree for possible data loss.

Dynamic fsync implementation has a reboot hook. So even when the kernel has a kernel panic and needs to reboot, file system will be flushed before. This can even be nicely seen in kernel logs.

Have this implementation in my s3 kernels for more than two years and never got a data loss reported.

Was just for education and clarification [emoji3]

Andi
[Galaxy S 5 Original Android Development] !crazy:
AFAIK faux, which implemented dynamic fs (I hope I didn't imagine this.) told people not to use it, and recommends 'Auto FS Write back delay mode' - as called in his app, what should be same as stock Linux laptop_mode.

I can remember some S3, S4 users who lost their data. I cannot claim it was because of dynamic fs, but I know some of them were using it.

Ktoonsez disabled the option in his S4 kernel because of such issue.

How do you say flushing is guaranteed to happen? Phones can shut off before kernel panic even happened.

AFAIK even standard kernel caches and buffers have no mechanism which would guarantee data will be safely written to the disk.
[Galaxy S 5 Original Android Development] HorstiG:
I'm a big fan of Xposed, but I have to be honest, most of the problems come from it.

The few modules that I use, every function without reboots, mostly.:D :D
[Galaxy S 5 Original Android Development] HorstiG:
Microphone Quality

Now something more serious

Here a file in order to improve the quality of the microphone heavily.!!!

Copy to root/system/etc/ Attrib -rw-r-r (644). Rename bevor the org File in mixer_paths.org or what ever.

Reboot an test it with Soundrecorder. Realy great.

https://dl.dropboxusercontent.com/u/73964661/mixer_paths.xml

https://dl.dropboxusercontent.com/u/73964661/mixer_paths.rar
[Galaxy S 5 Original Android Development] Pangadaywalker:
I have no reboots again with new kernel and conservative and default hotplug. So far so good. Almost 2 days already.
[Galaxy S 5 Original Android Development] andip71:
No, there is never a 100% guarantee of course.

In worst case the flush would not work anymore. But in that case you would lose the data even without dynamic fsync. So I consider it safe. Of course everyone worried can disable it in the app ?

Woooooh. YOU write that? ?

Thanks

Andi
[Galaxy S 5 Original Android Development] Reechings:
Does your speakerphone work OK? My wife says she can't hear me still even though videos seem to record audio well.
[Galaxy S 5 Original Android Development] Pangadaywalker:
Still no reboots. Apparently looks much better and battery life is OK. Gonna keep this way for a week or more.
[Galaxy S 5 Original Android Development] HorstiG:
No Problems here.
[Galaxy S 5 Original Android Development] FlemishDroid:
I use xposed with lots of modules and I have no reboots at all on zzmoove with optimal now I use interactive with battery. Row and BFQ. My cpu is little bit oc and I use uv -50, I use EXT4 Tweaks and gpu is still at 27, vnswap at 500. Latest nightly and latest boeffla beta. This kernel is rock stable for me.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] Pangadaywalker:
Today for 24 hours I underclock GPU for 27mhz. So far so good. And all other options as declared before. Conservative with default hotplug.
[Galaxy S 5 Original Android Development] FlemishDroid:
I'm back on zzmoove for 2 hours now and I don't get any reboot...

I can only reproduce a reboot whit this kernel when I oc to maximum but that's normal because I got that on my S3 also. Maybe it's a problem with zzmoove in combination with a bad app? Strange that not every user has the reboots. I got one reboot with boeffla since it was available but I had that also when I was on stock rom and stock kernel so 1 reboot is not that bad I think. :)

My asv/psv level is only 1 so I always thought I had a bad S5 but it seems it's not that bad. My S3 had an asv level of 6.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] mrstabs:
I'm testing the battery saver preset profile on my phone. On TW it laggs the phone but doesn't seem to using CM12.1 (temasek) so far its looking good.
[Galaxy S 5 Original Android Development] FlemishDroid:
I better didn't post anything about reboots... :) I just had one on zzmoove while sending an email and multitasking with chrome beta and some other apps...which files you need?

boeffla-kernel.log:

https://www.dropbox.com/s/4uej28v2m31i350/boeffla-kernel.log?dl=0

It's a good thing now I can change values like uv and ext4 tweaks to stock values.

Zzmoove

Relax

Hotplug - optimised

Cpu was 300 - 2457

Gpu was set as 200.

Ext4 tweaks was on.

Vnswap @ 500

UV -50

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] Pangadaywalker:
Playing with Read Ahead now and apparently the best number reached was 2048kb. I thought I had reboots with this option before so I am testing to make sure it improves without sacrificing stability.
[Galaxy S 5 Original Android Development] andip71:
Yes, sure. Do that and let us know please.

Read ahead depends a lot on the sd memory used. While internal memory should be almost the same in all S5 (but even that we do not know), it is quite significant for the external sd card. For some 256 is the best, some claim 4096 is the best.

Andi
[Galaxy S 5 Original Android Development] Pangadaywalker:
My results. So I have a Samsung Class 10 with 16GB.

512: Read 43MB Write: 9.30MB

1024: Read 43MB Write 14,30MB

2048: Read 43MB Write 13MB

3072: Read 39MB Write 9MB

Always using A1 SD Benchmark with the Option of More Accurate (with Reboot).
[Galaxy S 5 Original Android Development] andip71:
So guys,

I am testing currently a slightly improved msm_adreno_tz GPU governor.

I noticed, the current one used by CM does not scale down to lowest idle frequency always.

So I just ported the governor over from the OnePlus One source, there it scales perfectly.

And now it seems, it scales down also much more nicely on the S5.

So if all further tests go fine, a new kernel is coming soon (not today anymore though!).

Andi
[Galaxy S 5 Original Android Development] htb2050:
Nice! Looking forward to it then.
[Galaxy S 5 Original Android Development] FlemishDroid:
Another reboot...while playing a game (Li-ning super smash)

https://www.dropbox.com/s/gspmg7oo98eyuof/boeffla-kernel.log?dl=0

https://www.dropbox.com/s/84xl29cotmnuumy/bc.log?dl=0

Official CM12.1 nightly 15/06/2015

Boeffla kernel 2.1 beta 3

Zzmoove

Zzmoove Relax

Row

Bfq

Ext4 tweaks disabled

Read ahead 1024 / 1024

CPU 300 / 2457

Hotplug: optimised

Multicore savings: off

UV light

GPU: msm_cpufreq

320 - 578

Touchboost: 1267

System tweaks: off

Vnswap: 500

Swapiness: 130

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] HorstiG:
And what's the point?
[Galaxy S 5 Original Android Development] Pangadaywalker:
From what i understood better governor for gpu but less battery since it will scale down faster and lower.
[Galaxy S 5 Original Android Development] andip71:
Ok, time to switch to interactive and double check there again?

I am in the process of convincing ZaneZam he needs a S5 to optimize his governor for this phone. It seems, it is required... :(

The point is: When nothing is to be done and system is idle, it is useless to keep GPU on 200 or even 320 MHz, it can and should go down to the lowest step (27 MHz in my kernel).

And yes, the point is quite clearly: Some battery savings. Whether they are significant - the time will show.

But this is the correct scaling behaviour and I was surprised the S5 did not scale down when idle nicely.

Andi
[Galaxy S 5 Original Android Development] andip71:
New update

Hi all,

new update available.

Version 2.1-beta4

Note: Only for CM nightlies of 14.05. or newer (and custom roms having these new changes in)

16.06.2015

Further kernel start script optimisations on ext4 tweaks

Changes to msm_adreno_tz GPU governor for better usage of idle frequencies (port from OnePlus One source basis)

Fix wrong CPU frequency used for "Power" preset in Boeffla-Config

Ramdisk updated to first official CM12.1 nightly of 16.06.15

Enjoy

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Choose another gpu governor!
[Galaxy S 5 Original Android Development] FlemishDroid:
I had 1 reboot on intelliactive on 12 hours...now I'm back on interactive.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Well, interactive is supposed to be 100% stable as the stock governor.

But the comment before was valid... why are you using such a weird GPU governor? I would strongly suggest msm_adreno_tz, especially after I improved it (hopefully) today in beta4.

Andi
[Galaxy S 5 Original Android Development] !crazy:
But that is not hour your kernel behaves with GPU!

Your kernel always scales to the lowest frequency when idle???

That is why I don't get this, what is this about?

It is true that Samsung and CM use that method for whatever reason since S4 I believe. That is at least what I am able to confirm. All Samsung ROMs including stock, and CM on S4, S5 implement such behaviour, where GPU usually 'idles' or waits on 320 MHz.

Maybe for to achieve better responsiveness, and maybe GPU has also some C power saving states?

However I haven't noticed any drawbacks in responsiveness or of any kind when I use governors/kernels which scale the frequency to the lowest one, so that is what I prefer if possible.
[Galaxy S 5 Original Android Development] andip71:
Correct. Standard GPU msm_adreno_tz governor behaviour on the S5 is to stay at 200-320 MHz when system is idle. What for?

And I modified it to go down to lowest configured frequency (in my case 27 MHz) when idle.

This makes for instance the adreno_idler by arter obsolete in my opinion.

Well, it is in latest beta4 kernels. We will see how it goes :)

Andi
[Galaxy S 5 Original Android Development] !crazy:
No, what I don't get is that your older kernel before beta 4 also go down to 27 when idle, with msm adreno tz governor?
[Galaxy S 5 Original Android Development] andip71:
It was not for me when I tried it.

Dont know why it was for you :)

Andi
[Galaxy S 5 Original Android Development] !crazy:
You say you saw GPU spending most of the time on 320 MHz on your kernels, before beta 4?

I can make a video if you want. Since I started using your kernel, I think last 2.0 beta, but I'm 100% that since beta one my gpu spends most of its time on 27 MHz.
[Galaxy S 5 Original Android Development] andip71:
When I have screen on, the GPU freq did not go down to 27 on my side, yes.

At least not when I tested it yesterday.

On my OnePlus phones it was different. So I diffed the governors here and there and put some changes in from the OPO governor.

After that I reached 27 MHz as well.

But - no need to do a video or something. I believe you when you say it. Question is how you checked it... I ran the simple shell script which arter provides in his adreno_idler thread in the OP. And here I clearly saw in an adb session... 200 MHz when screen on was minimum.

Anyways... with beta4 it is also fine for me, so hope for everyone.

Andi
[Galaxy S 5 Original Android Development] Jatinder Tiwana:
My phone is now f**cked I accidentally switched the GPU governer to hwm (the first one) and now phone reboots after just 10 seconds and I'm unable to open the boeffla app pls tell the solution guys??
[Galaxy S 5 Original Android Development] andip71:
Ts ts ts. This is not a recommended GPU governor :)

Solution is simple:

You go into recovery, and flash the reset.zip you find in /boeffla-kernel-data folder.

This will reset all kernel settings to default.

Andi
[Galaxy S 5 Original Android Development] djdana:
For the fix off the GPU frequency can I leave the governor etc on default??

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] !crazy:
Which fix please? Find an app which shows actual GPU frequency (System Monitor, System Tuner Pro, faux clock to name a few.) and check is the frequency going to the lowest one when not under load. If yes, and I'm sure it will be, everything is ok. Default governor is msm-adreno-tz, and yes this governor behaves well (in my case, and I see no reason why would it be different in your case.) so you should be fine with it.

---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------

As LB already suggested. In case you don't have it, and you found downloading, transferring to your phone in recovery bit troublesome, you can also just reflash your ROM, which you probably already have on the phone.
[Galaxy S 5 Original Android Development] andip71:
Just use standard msm_adreno_tz GPU governor (this is default) and you have the change automatically active.

But it is pretty much impossible he does not have it. The zip file is created again during every phone restart in case it was deleted before. So 99,9999% he has it in that folder.

Andi
[Galaxy S 5 Original Android Development] Pangadaywalker:
So for GPU I am getting 80% of time in SLUMBER and 18.83% in 27mhz.

What is slumber?? LOL
[Galaxy S 5 Original Android Development] ASHLEY117:
German engineering at it's finest!

Installed earlier and running fine. No reboots with the previous two beta's. Thank you again