yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] andip71:
Undervolting is never safe.

It is a constant root cause for random reboots and issues, while not having any significant positive effect.

In my newer kernels (OnePlus2 and 3) I refused to put any voltage interface in exactly due to this reason.

P.S Not saying this is the reason for your reboot issues, but I will not give support. Also, as stated on the support site, when I cannot replicate issues, I cannot investigate them.

And my last random reboot was, hm...., 6 months ago maybe?

It can have so many reasons, also non-kernel related ones. But the known ones are: overclocking, undervolting, or using a different governor than interactive.

Andi
[Galaxy S 5 Original Android Development] STk3000:
Ok Andi, noted those settings and will post any logs if I get another one
[Galaxy S 5 Original Android Development] j1gga84:
Everytime after the boeffla config was applied after a reboot the display colors get very warm, for my taste too warm (nearly yellow).

I like the "cooler" colors much more, how can I change it?

regards
[Galaxy S 5 Original Android Development] 2phazt:
Maybe you have something else active that changes the color temperature - live display for example.
[Galaxy S 5 Original Android Development] genziutek:
Change saturation in Boeffla Config.. Display+LED/Color control
[Galaxy S 5 Original Android Development] RootNightmareX:
Interactive is the most balanced governor ? Or which one is?
[Galaxy S 5 Original Android Development] andip71:
At least it is by far the most stable governor on the msm8974 platform.

And I would also claim, it is pretty balanced regarding performance and battery consupmtion.

It is my daily governor for long time (on OP3, and formerly on OPO).

Andi
[Galaxy S 5 Original Android Development] andip71:
Hi all,

kernel update is out.

Version 3.2-beta2

30.09.2016

Update: Updated with latest official CM kernel commits as of 30.09.16, 8am CET

Change: KCAL initialization changed (if switched to off, it should never do anything during bootup)

Change: Improvements to anykernel script (credits to Osm0sis)

Enjoy

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Is this commit https://review.cyanogenmod.org/#/c/163854 in the kernel ?

I don't want to increase the min brightness...
[Galaxy S 5 Original Android Development] RootNightmareX:
I have lagg in games that on touchwiz roms i didnt have like hearthstone.

Any help please?
[Galaxy S 5 Original Android Development] Arthur King:
It is not the kernel, i think thats normal on no-stock roms, if you want better experiencie for game you should stay in stock, it just works better idk why
[Galaxy S 5 Original Android Development] RootNightmareX:
So stock rom is the best option for games?
[Galaxy S 5 Original Android Development] STk3000:
Change the governor. I think stock has it locked on on-demand. You should try on-demand Governor.
[Galaxy S 5 Original Android Development] Arthur King:
Yeah, in my opinion and my experience stock its much better for gaming.
[Galaxy S 5 Original Android Development] htb2050:
If you don't even notice its effect then why do you worry.
[Galaxy S 5 Original Android Development] ScratMan38:
Looks like you didn't understand. This commit increases the minimum brightness of the screen. It has been added to Git directly as a workaround to satisfy a few users facing hardware failure ; but it degrades the user experience during the night by forcing too high brightness, reducing battery life too.

This other commit https://review.cyanogenmod.org/#/c/164226/ reverts it, but it looks like it doesn't go forward to be merged.

So I'm willing if the first commit is part of the kernel or only part of the ROM. If Boeffla kernel can override this commit, then I may update to latest nightly and flash latest Boeffla kernel to workaround this commit, keeping the normal brightness management. If the commit is part of the ROM and if kernel can't circumvent it, then I can't update.
[Galaxy S 5 Original Android Development] JulGer01:
Mimimi... So look for another ROM then. His lordship said there will be updates but no new features to the kernel on s5.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] ScratMan38:
Looks like my english is not good enough...

This commit : https://review.cyanogenmod.org/#/c/163854 SHOULD NOT HAVE BEEN MERGED !!! and it must be reverted.

I'm not asking for a new feature !
[Galaxy S 5 Original Android Development] JulGer01:
Well, it was merged and hopefully will stay that way! I like it! ?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
This is not a kernel code commit, this is a rom commit.

Nothing for me to merge.

Andi
[Galaxy S 5 Original Android Development] STk3000:
Have a good time, Andi [emoji8] [emoji8]
[Galaxy S 5 Original Android Development] j1gga84:
I have huge battery drain in latest CM13.0 with newest Boeffla. I think its because Boeffla kernel needs an update to be in line, correct?

If yes I am looking forward to the maintenance update next week :)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] !crazy:
Always check facts, always check wakelocks (at least system stats you have easily available in system menu, but there are plenty of apps which can show you info about wakelocks.) when talking about battery drain, otherwise thinking would be more like imagining.

---------- Post added at 03:37 PM ---------- Previous post was at 03:15 PM ----------

Has anyone here noticed issue with cpu hotplugging when using interactive governor? It was my default, but now I switched to zzmove because of the issue.

The issue is that mpdecision/hotplugging doesn't work properly. Either all cores are online, or only one while rest are stuck offline. Turning mpdecision off and on temporarily fixes the problem, but eventually everything ends with only one core being active shortly after (minute or so).
[Galaxy S 5 Original Android Development] andip71:
Nope. There aren't only two minor commits missing due to my holidays. And these cannot cause it.

Edit: meanwhile there are a few more commits, so there will be an update after I am back of course.

Are you underclocking?

Because mpdecision indeed has issues since approx May this year when underclocking below 2ghz.

Andi
[Galaxy S 5 Original Android Development] xcentricdave:
Can't connect to camera after cm-13.0-20161008-NIGHTLY-klte using Boeffla kernel (3.2-beta2).

Camera is fine with CM13 kernel.

I'm guessing that the commit 'fixing' a problem with MM camera blobs might be the issue (https://review.cyanogenmod.org/164580 klte-common: fix denial caused by mm camera blobs) might be implicated?

Modem/BL : G990FXXU1CPCH / G900FXXU1CPE2

cheers,

Dave
[Galaxy S 5 Original Android Development] j1gga84:
Yes, Boeffla needs an update but lord Boeffla is aware of that.

He was on vacation during the weekend and an update will come these days, patience ;)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] xcentricdave:
No impatience or demands! I just hadn't seen anyone raising the issue and was doing my bit putting fingers to keyboard to record the issue - just in case it was only me...

I'm happily rolled back to before the problem and will wait patiently:angel:

Respect to all devs and other people who give their time to these efforts voluntarily so that we all benefit.

cheers,

Dave
[Galaxy S 5 Original Android Development] andip71:
No no, I am indeed aware.

Just have my priorities at the moment to finish off things I already started.

So first I want to push out the OnePlus X OOS 3 kernel, and maybe from tomorrow on I can work on this changes again.

It will take much longer than usual, as the kernel has been completely rebased, which means I will have to start from zero.

Andi
[Galaxy S 5 Original Android Development] j1gga84:
Hi Andi, welcome back :)

I read it on your homepage but I want to ask you also here:

Is CM13.0 the last Cyanogen Mod you will support with boeffla kernel? Even if CM14.0 will become official and allthough the OnePlus One is even older than the S5?

regards
[Galaxy S 5 Original Android Development] andip71:
You are correct. CM13 will be my last kernel, even if CM14 becomes official I will not support the S5 anymore.

OnePlus One is a different story indeed.

While S5 was launched 24.02.14, the OnePlus One was launched 2 months later. But that is not the reason.

The reason is: OnePlus One has a much simpler and streamlined hardware (when it comes to e.g. charging driver, touchscreen driver, hardware support for gestures). So it is much more fun to develop on the One than on the S5. Not to speak about all the annoyances Samsung puts constantly in to make development hard (knox, efuses, flash counters etc).

I am tired of supporting Samsung with their attitude to not support developers.

That is the main reason I will dump the S5 but keep the OnePlus One. I am sorry, I know many will not like that message, but it is my final decision.

Andi
[Galaxy S 5 Original Android Development] andip71:
Hi all,

was a bit faster than expected.

So here we go for a stable release 3.2, which is supposed to be used for all CM based roms oder than 07.10.2016.

And the new beta 3.3-beta1 works on all newer roms, that use the MM kernel sources already.

In short - watch out which version you need to flash.

Version 3.3-beta1

10.10.2016

Note: This kernel is only for CM based roms which are newer or of 07.10.2016, for older rom take latest stable version !!

Update: Complete rebase accordingUpdated with latest official CM kernel commits as of 10.10.16, 8am CET - this includes the

big update to Samsung MM sources

Change: Built with Android MM standard toolchain version gcc 4.9

Version 3.2 stable

10.10.2016

Note: This kernel is only for CM based roms older than 07.10.2016, for newer roms take latest beta version !!

Update: Updated with latest official CM kernel commits as of 06.10.16, 8am CET

Change: Build script improvements

Enjoy

Andi
[Galaxy S 5 Original Android Development] venereo:
Professional as usual, thank you!
[Galaxy S 5 Original Android Development] afr33sl4ve:
I was gonna post that the camera is broken with 3.2-b2 and 20161009. However, I also just saw that you've already released updates!

You rock!

EDIT: Can confirm that 3.3-b1 solves camera issue.
[Galaxy S 5 Original Android Development] pakino2004:
RR remix 5.74 s5

Proximity sensor didn't work with version 3.2 kernel

Went back to the latest beta kernel and the sensor work again! Weird JFI

Greetings
[Galaxy S 5 Original Android Development] j1gga84:
For me it seems that battery lifetime is worse compared to the CM13 builds before the MM blobs kernel merge.. I will observe it further..

besides of that 3.3 beta 1 is running great :good:

regards
[Galaxy S 5 Original Android Development] andip71:
No code was changed in between. So yes, weird is all we can say.

Well, there are much reports about it. And also the CM development team is pretty much aware of it.

They hope it will rebalance over the time. Not sure whether this hope is valid or not.

Time will tell for sure.

Andi
[Galaxy S 5 Original Android Development] pakino2004:
No problem I'm satisfied with the beta version! I think there is not a big difference to the final one! Keep going! Thanks for all your efforts

Gesendet von meinem SM-G900F
[Galaxy S 5 Original Android Development] jimbomodder:
Can't find cm12.1 on downloads section on cm13

Sent from my SM-G900F
[Galaxy S 5 Original Android Development] andip71:
Under eol downloads in the downloads menu.
[Galaxy S 5 Original Android Development] andip71:
Hi all,

major overhaul of the CM13 kernel, I built it from scratch with cleaned commits based on latest CM13 sources.

Version 3.3-beta2

14.10.2016

Note: This kernel is only for CM based roms which are newer or of 07.10.2016, for older rom take latest stable version !!

Kernel completely built from scratch on latest CM-13.0 branch, eliminating lots of obsolete commits and code + fixing some cpu scaling issues of previous version

Update: Updated with latest official CM kernel commits as of 14.10.16, 8am CET

Change: Internal kernel busybox updated to latest version 1.25.1 (self-compiled from sources, www.busybox.net)

Change: Removed ramconsole again as last_kmsg on S5 was never of any help in the past

Change: Improvements to anykernel script (credits to Osm0sis)

Change: Build script improvements

Enjoy

Andi
[Galaxy S 5 Original Android Development] airidosas252:
Appreciated!
[Galaxy S 5 Original Android Development] Zigie:
Version 3.3 beta2 is causing a flickering display issue. I use Blisspop latest version.
[Galaxy S 5 Original Android Development] venereo:
All good here with CM
[Galaxy S 5 Original Android Development] Zigie:
Ok, with 3.2 beta2 I have no issues.
[Galaxy S 5 Original Android Development] venereo:
Don't you mean with 3.3 beta 1? When does the flickering happens?
[Galaxy S 5 Original Android Development] Zigie:
No 3.3 beta2. As soon I switch on the display it starts flickering several times.
[Galaxy S 5 Original Android Development] andip71:
Pure coincidence. Display drivers are not changed at all.

But Blisspop is also no reference, not sure if you should use latest beta already for Blisspop at all or 3.2 stable.

As there is no (new) flickering issue on CM, nothing to do.

Andi
[Galaxy S 5 Original Android Development] jjkrause1:
I'm a G900P user with no issues until now (other than self-inflicted ones).

Updated to cm-13.0-20161013-SNAPSHOT today via OTA (gapps updated automatically), flashed supersu, flashed Boeffla-Kernel 3.3-beta2, and updated to Boeffla app version 2.4.11. My camera and 5GHz wifi band stopped working. Reverting back to 3.2 stable fixes it for now, even though I know it's for older roms.

Just wanted to make you aware in case there's a bug on your end. If I didn't follow instructions correctly, feel free to bust my chops.
[Galaxy S 5 Original Android Development] venereo:
Supersu must be flashed after Boeffla
[Galaxy S 5 Original Android Development] Zigie:
Just retested. I have the flickering issue only with latest beta. Maybe it's an issue in combination with Blisspop. If CM is okay. I'll stay with 3.2 beta. It's okay.
[Galaxy S 5 Original Android Development] andip71:
No, there is no bug. This is expected behaviour.

Snapshot uses older code basis, i.e. older than nightlies of 07.10. - hence version 3.2 stable is the only version for you.

To all users of cm-13.0-20161013-SNAPSHOT:

You have to use 3.2 stable version as snapshot release is too old for latest Boeffla-Kernel beta releases !

Thanks

Andi
[Galaxy S 5 Original Android Development] da_makaO:
3.3 beta 2 has still the problem with the frequencys on the last cm13 (14.10.2016). the screen flickering was gone i think, but i reverted too soon without futher inspecting that combo.
[Galaxy S 5 Original Android Development] andip71:
What are you talking about? Which frequency issue?????

Andi
[Galaxy S 5 Original Android Development] j1gga84:
The CM team is aware of the screen flickering, please read in the official CM13 thread.

Not every device has this issue but [MENTION=2693412]haggertk[/MENTION] will upload a test build soon.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] da_makaO:
Entweder is core 1 und/oder 4 gleichzeitig auf der höchsten Mhz oder auf 1,5Ghz. Keine Ahnung woran das liegt! Ist auf jeden Fall seit komplett auf MM umgestellt wurde.

core 1 and/or 4 is else on full Mhz setting or on 1,5Ghz. Dont know why!
[Galaxy S 5 Original Android Development] andip71:
English please.

And yes, cm team is aware of this.

Andi
[Galaxy S 5 Original Android Development] The~Skater~187:
I'm currently running Resurrection Remix 5.7.4 with your 3.2 beta 2 kernel.

Am I correct to assume that is why I keep getting this on the last two betas?

Resurrection-Remix-BoefflaKernel-SM-G900P
[Galaxy S 5 Original Android Development] venereo:
Is it that difficult to backup current configuration and try clean one? Why bother developers with silly questions? Backup -> Install clean -> Check it for yourself
[Galaxy S 5 Original Android Development] The~Skater~187:
I have done this a few times. Tried different kernels and configs. Just wanted to make sure that's due to the older rom version.

Resurrection-Remix-BoefflaKernel-SM-G900P
[Galaxy S 5 Original Android Development] venereo:
But it's easy to make sure: install latest kernel on latest CM and you will know it's a RR problem. And no RR support here.
[Galaxy S 5 Original Android Development] pakino2004:
5.74 no camera error here with 3.2.1 boeffla s5 klte

Gesendet von meinem SM-G900F
[Galaxy S 5 Original Android Development] j1gga84:
The screen flickering issue seems to be gone hopefully with the next nightly but Boeffla needs an update for that :)

In next CM Nightly there are also some new kernel commits.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
This is not really true:

In CM world, supersu should not be flashed at all if there is not a strong reason for it. CM built-in superuser does everything much smoother.

But if you insinst in supersu, the sequence is usually:

- rom

- supersu

- boeffla

Well, all I can say here: These are the issues when roms like Bliss, RR, whatever else is used.

So it is private "luxury" to use these roms and face issues.

It is simple:

CM team changed kernel sources (and corresponding blobs) with nightly of 07.10.

If your custom rom still uses the older code base (this is again why I would not use these roms like Bliss, RR, whatever - as they update too slow), you are stuck with 3.2 stable kernel.

If your rom dev finally merges the big updates, you can use latest kernel version.

It is plain simple.

Yup. I am planning to push an update today itself.

Andi
[Galaxy S 5 Original Android Development] andip71:
Hi all,

maintenance update is out:

Version 3.3-beta3

17.10.2016

Note: This kernel is only for CM based roms which are newer or of 07.10.2016, for older rom take latest stable version !!

If you use custom roms like Resurrection Remix, Blisspop etc. you have to carefully check if you need still version 3.2 stable as custom roms are usually updated with slower pace

Update: Updated with latest official CM kernel commits as of 17.10.16, 8am CET

Fix: Add forgotten functionality to overwrite CPU frequencies when not using Boeffla-Config (not recommended)

Change: Removed compiler flag not required anymore

Enjoy

Andi
[Galaxy S 5 Original Android Development] j1gga84:
3.3 beta 3 runs great and the screen flickering issue when waking up device is gone :good:

But it seems that CM team is still working on the CM13 kernel:

https://www.cmxlog.com/13/klte/

I don't know if latest changes are already implemented in boeffla 3.3 beta 3 or to ask different: are these changes important for operation?

regards and thanks again :good:
[Galaxy S 5 Original Android Development] andip71:
Only the last 3 kernel commits have been pushed after I made the build.

They seem not essential as everything seems to be running fine.

However, I am prepared to follow the CM updates already tomorrow again with a new beta if reasonable.

Andi
[Galaxy S 5 Original Android Development] andip71:
Ok, maintenance update again.

This is including also the latest 3 patches of official CM branch

Version 3.3-beta4

18.10.2016

Note: This kernel is only for CM based roms which are newer or of 07.10.2016, for older rom take latest stable version !!

If you use custom roms like Resurrection Remix, Blisspop etc. you have to carefully check if you need still version 3.2 stable as custom roms are usually updated with slower pace

Update: Updated with latest official CM kernel commits as of 18.10.16, 8am CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] frost80:
Hi Lord Boeffla

just want to know if your kernel is compatible with resurection remix rom marshmallow

waiting your answer to flash it

big thx :)
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=5608948]frost80[/MENTION]

If you use official RR then you have to use Boeffla 3.2 stable but no guarantes from Lord Boeffla.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] f0xy:
Not to go off topic Lord, the only reason I use SuperSU is so I can use ARISE sound mod in enforcing mode, not sure why it's not able to do it with CM Superuser
[Galaxy S 5 Original Android Development] Reechings:
Anyone turning up the charging power for wireless and have any idea what is safe or what they have used it at before? Currently using Qi wireless stick on charger at 950 and wondering if I can go higher. Cheers
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Had to share the love for this fantastic kernel, this is my comment from the arkTube thread.

I installed a new kernel on my Galaxy S5, the Boeffla and tuned it with the included config app. Now all the cores are running at 2.8 GHz flawlessly without any overheating issues or freezes. The CPU actually runs cooler than before when it was at stock clock. The most interesting part is that now I am able to run VP9 videos at 60 FPS smoothly and damn it looks good! The audio was also improved greatly, crystal clarity and dope Dept! I noticed immediately that the VP9 videos are so much smoother and clearer without those low bitrate muddy boxy effect that I've seen with the H264. Though this old 32bit arm v7 hardware doesn't natively support VP9 or Opus, this kernel tweaks with the newest CM13 ROM and the MX Player does really come out better than the standard native hardware way. The phone also aces 8 simultaneous downloads without breaking a sweat at an average speed of 80 Mbits on 4G connection and 120 Mbit on my WiFi. I skip merging metadata because I don't need any fancy artwork for my music though it looks nice I'll admit. Also Opus audio downloads with metadata included doesn't seem to work, maybe the codec doesn't support metadata.
[Galaxy S 5 Original Android Development] 2phazt:
Cpu scaling is kind of weird with 3.3b4 - core1 is almost always stuck at 1500 mhz - even with zero load.

This happens with every governor - no matter if hotplugging is set to default or optimized - default just keeps core4 active but on 300 mhz.

My question is - is this an allready documented bug?

Can I do something on my end?
[Galaxy S 5 Original Android Development] j1gga84:
For me it also feels that the battery consumption is higher after build 3.2 !?

Where did you check the CPU rates?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] j1gga84:
Okay, I made a screenshot and it is exactly the same on my side..

This high consumption only appears in in usage, not when device is in deep sleep.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] zfk110:
Its!

http://xdaforums.com/showpost.php?p=69240775&postcount=4734
[Galaxy S 5 Original Android Development] The~Skater~187:
Ruining the updated Resurrection Remix With boeffla 3.3 beta 4 with no issues. Deep sleep seems to be working fine.

Resurrection-Remix-BoefflaKernel-SM-G900P
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=4326892]The~Skater~187[/MENTION]

You have only 2 hours of uptime but 30 minutes of that 2 hours your device was running at 1500 MHz, seems to be the same issue..

I was running about 16 hours..

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] The~Skater~187:
That's because I do daily reboots on my device. Ran it fully through the day yesterday with no issues. But I will keep my eyes open for the issue you speak of.

Resurrection-Remix-BoefflaKernel-SM-G900P
[Galaxy S 5 Original Android Development] j1gga84:
Maybe it will be better with one of the next updates:

http://xdaforums.com/showthread.php?p=69272975

Concerning the CPU stuck at around 1500 MHz a user in CM13 thread wrote the following:

http://xdaforums.com/showthread.php?p=69256317

I tried that but it has no effect for me :(

Regards

Sent from my SM-T805 using german Tapatalk 4
[Galaxy S 5 Original Android Development] 2phazt:
Doesn't work for me too.