yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] k4bbe:
Hi all. Thanks for the kernel. Ran Boeffla on my S3 and only chose the S5 as an upgrade once you released a kernel for it.

I have been Having some random freezes on official Cm12 and now 12.1 nighties.

I have logs dmesg,logcat and event but last kmesg is not in the Proc folder.... Would it be anywhere else and should I pm the logs I have, upload or post here?

Thanks

K4bbe
[Galaxy S 5 Original Android Development] Pjerisimo:
I mean which version/build of CM 12.1 should I use with boeffla kernel? I see different versions are mentioned, temasek, albinoman's, etc.
[Galaxy S 5 Original Android Development] andip71:
I will of course switch to ramdisk of official nightlies once available.

Andi
[Galaxy S 5 Original Android Development] Ozzy2403:
http://download.cyanogenmod.org/?device=klte
[Galaxy S 5 Original Android Development] andip71:
Kernel is already updated and I will release it today as beta1.

Andi
[Galaxy S 5 Original Android Development] carabinieri5675:
Perfect.
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Can't wait ???. Thanks Andi!

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] DirkStorck:
Thanks a lot :D
[Galaxy S 5 Original Android Development] benjamen50:
Anyone using the official nightly? Any issues?
[Galaxy S 5 Original Android Development] carabinieri5675:
Please, there is an existing thread. This is the Kernelthread for Boeffla.
[Galaxy S 5 Original Android Development] andip71:
Official CM13 for S5

Hi all,

last night, the first official CM13 version for the Galaxy S5 came out.

Time to provide you a fully rounded up new beta version (not alpha anymore, as it is official now) for CM13.

At the same time, a small maintenance update to the CM12.1 kernel, which could be pretty much the last one, depending on how CM team continues with builds for the S5...

CM13.0 -- Version 3.0-beta1

28.12.2015

Note: You are

strongly adviced

to

use first official CM13 version of 28.12.2015 or newer !!! Other roms might work, or not...

Updated with latest official CM kernel commits

Ramdisk updated to official CM13.0 version of 28.12.15

SELinux default is strict now (you can change this in Boeffla-Config any time - if you need it sticky across reboots, configure in app settings menu and not the overview page!)

Changes to toolchain and compiler/linker switches

CM12.1 -- Version 2.3-beta9

28.12.2015

Ramdisk updated to official CM12.1 version of 26.12.15

Changed some compiler switches

Enjoy

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Thanks Andi! Finally nightlies :)

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] ScratMan38:
I flashed the 28/11 nightly after full wipe, directly with Boeffla alpha 10, and everything worked perfectly.

But after flashing beta 1, camera didn't work anymore. I tried to flash ROM again to restore stock kernel, but camera was still not working. Then I flashed back alpha 10, and camera is now working fine.
[Galaxy S 5 Original Android Development] andip71:
Quickly checked here camera working normally with beta1 on latest nightly.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Made a backup with alpha 10, and tried again with beta 1 : still can't connect to camera. Using stock camera app, Google camera or A Better Camera.

Edit : changed config app settings to set SELinux to permissive on boot, and rebooted. Now camera is working with beta 1.
[Galaxy S 5 Original Android Development] XZ00E:
Is it receommended to make a clean installation with CM13 ?

Such as:

1) Boot in to recovery, clean data, wipe cache and dalvik

2) Install CM13

3) Install Gapps 13

4) Reboot

Should work then right?

Is the CM13 stable as the CM12.1 or is it receommended to wait a while.

Need to clean up my phone so I've been browsing all over the internet to find the pros and cons of updating or not from 12.1..

Please advice! :)
[Galaxy S 5 Original Android Development] Frost009:
Always recommended to do a clean flash. Should be stable enough for daily use since it is now official nightly release, just do a backup in case you want to revert back to 12.1. In my opinion, CM 13 is smoother and has better battery life than 12.1, so just flash it and try for yourself to find out if you like it better than 12.1.
[Galaxy S 5 Original Android Development] andip71:
Interesting but still weird.

It is working for me with selinux strict.

Maybe everything gets sorted after the next clean install?

Don't know if you dirty flashed over a previous unofficial build...

Andi
[Galaxy S 5 Original Android Development] DirkStorck:
At my side it is working with selinux strict too.
[Galaxy S 5 Original Android Development] andip71:
Good to know.

But let's be fair, we have the second CM13 nightly now. So things probably need to settle a bit over the time.

I will release a maintenance update soon, which includes the ramdisk of the latest nightly. Just to go sure we stay in sync as closely as possible in the first days now.

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Working with strict too for me.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] Putrid Polecat:
Anybody successfully get pure CM13 running on G900T? It gets to the lock screen and crashes on com.android.phone. no sim detected. I reinserted sim but that didn't help. I guess I'll wait for a few more nightlies.
[Galaxy S 5 Original Android Development] andip71:
Of course.

Latest CM13 nightlies (from last night and the one before) working just fine already for me. None of your mentioned issues.

Andi
[Galaxy S 5 Original Android Development] Putrid Polecat:
The T-Mobile variant? Ok I'll try it again.
[Galaxy S 5 Original Android Development] andip71:
Ah sorry, missed that part. I meant the G900f of course...

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

Hi all,

as we are in the very beginning of CM13 for the S5 (at least the official one), I want to make sure the first wave of fixes is contained in my kernels in a timely manner.

Therefore, a pure maintenance update now for CM13:

Version 3.0-beta2

29.12.2015

Note: You are

strongly adviced

to

use first official CM13 version of 28.12.2015 or newer !!! Other roms might work, or not...

Ramdisk updated to official CM13.0 version of 29.12.15

Enjoy

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Thanks again Andi! :)

Great as always!

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] zrockcool:
Guys, I encounter this error when I try to open the kernel. CM 13 latest nightly installed and boeffla beta2. Thanks!

"SD memory r/w issue, Boeffla Config cannot write to your SD memory"
[Galaxy S 5 Original Android Development] andip71:
Well, I am sure the message tells you more, or?

Andi
[Galaxy S 5 Original Android Development] zrockcool:
Exact message,

Boeffla-Config cannot write to your SD memory,this impacts functionality of Boeffla-Config.

Please restart your system now,maybe you should wipe Art,Dalvik cache as well.

Done restart and wipe cache but still encounter the error.
[Galaxy S 5 Original Android Development] andip71:
Then uninstall the app, download freshly from the kernel homepage and install it again from the apk file.

Sometimes this is a bit a hassle.

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Granting storage permission fixes ALL of this issues.

Marshmallow has permissions now...

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Yep, and usually a dialog should pop up, asking for it if not granted.

But this seems to not always work for everyone.

I realized when people restore the app via e.g. TitaniumBackup, then these issues sometimes occur.

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Right there is a pop up dialog.. I always make a fresh install so that could be the reason I see it.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] zrockcool:
Reinstalling the app fixes the pop up error.

Thanks Andi!!
[Galaxy S 5 Original Android Development] XZ00E:
Thought so!

How ever! There's no instructions that say if Gapps 13 now is

required

or just preferable (as it seems to be a nightly build on top of cm 12.1?)

I've got TI Pro for instance, but does it backup the whole system - WITH the ROM setttings (incl. Gapps?)

How do I backup my phone with the ROM (CM 12.1)?
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
[MENTION=947981]Lord Boeffla[/MENTION]

Is it ok to use beta2 on cm13 nightly 30.12.?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
I am running that combo here, I do not see any reason for a kernel update atm.

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Ok.

What's this?

http://review.cyanogenmod.org/#/c/126096/

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
First: Not for us, it is for kltekdi.

Second: Disabling the driver for a regulator that does not exist in this device or is not being used.

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Thanks!

Flashing beta2 now :)

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] benjamen50:
Anyone tried dirty flashing CM 13.0 unofficial to official?
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Yes. No problems (for me at least) BUT I did a clean flash today. Feels just better ;)

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] ScratMan38:
I made clean flash. I was using the unofficial December 27th build from Albinoman, and I wiped system, data, cache and dalvik before installing the first official nightly.

I tried again with Beta 2 and 30/12 nightly, still can't connect to camera.

Maybe flashing Alpha10 on top of first official nightly broke something. Will try to backup everything and fully wipe, to see if it helps.
[Galaxy S 5 Original Android Development] corsetto:
Hi [MENTION=947981]Lord Boeffla[/MENTION] just to inform you this strange behavior of beta2 on AIPC 11 tofay release fresh install (30/12).

If I flash you kernel I lose the active cover (S-View) functions.

Not a big problem for me just to improve your fantastic kernel.

Thanks and Regards
[Galaxy S 5 Original Android Development] andip71:
This is probably due to double tap to wake, as this requires the proximity sensor.

You might try to switch it off.

If so, there is unfortunately no solution. Double tap to wake is known to break some stuff.

And... hehe, I did not even know this active cover (S-View) functions exist... never use it. Or is it AIPC specific in any way?

Andi
[Galaxy S 5 Original Android Development] Putrid Polecat:
OK, all set! CM 13 + Boeffla Kernel running fine on T-Mobile G900T.

Resolution:

1. Dirty Flashing didn't work. I had to clean flash even though installing and setting up all ups is a PITA.

2. GAPPS for Android 6.0 was essential. I flashed http://opengapps.org/

It is noticeably smoother than 5.1. Thanks Lord Boeffla. :good:
[Galaxy S 5 Original Android Development] corsetto:
[MENTION=947981]Lord Boeffla[/MENTION] I Tried to disable double tap to wake, but didn't sorted.

Who cares, I prefer to lose this function but all mine Rom must have your kernel!!!
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
It is really smoother than 5.1 :)

And Doze (with Greenify) is awesome.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] benjamen50:
Dirty flash worked pretty smooth for me. From unofficial to official. (was planning to delete this post but oh well).

Edit: Just wanted to give a tip, if your phone gets frozen use Volume down + Power button for 7 seconds or more. Then the phone will turn off and restart itself.
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
So quiet in here... ;)

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] milestone97:
Is the Kernel/CM13 ready for daily?
[Galaxy S 5 Original Android Development] kris_l:
Hi, I've made some research and i've found that s-view cover use hall sensor to switch screen on or off. If I remember in Resurrection Remix 19th DEC build s-view cover was working with your alpha6 kernel for cm13. Maybe it needs some permission on ramdisk for hall sensor? I'm currently on aicp build 3rd Jan 2016 and this and previous build works fine with s-view if I use stock kernel but with yours s-view doesn't work. Maybe you could look for fix for it? Your kernel is the best one for s5 anyway.
[Galaxy S 5 Original Android Development] andip71:
My suspicion is a bit different... when it does work for you with kernel version 9 or 6 (which I would appreciate if you could test quickly), then it is an incorrect library used in CM13 still.

Because the mentioned betas had the sensor drivers reverted back to kitkat libraries, whereas now I use of course 100% driver code which is in official CM13.

But that would mean, it should also not work for you with CM13 stock kernel. Did you test that ever?

Anyways, I will release a new maintenance release in a few hours latest, then you can test again. Then we can take it up from there (in worst case I can make you a test kernel with the drivers for the hall sensor reverted back to kitkat blobs again).

Andi
[Galaxy S 5 Original Android Development] andip71:
CM13 kernel maintenance update

Good morning,

new week, new start, with an update to the CM13 kernel.

Version 3.0-beta3

04.01.2016

Update: Updated with latest official CM kernel commits as of 04.01.16, 6am CET

Ramdisk updated to official CM13.0 version of 04.01.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Thanks Andi!

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] BrX91:
Just a quick question. Usually video preview when recording bug was caused by inconsistencies between ROM and kernel. Now I am using 4.01 CM and beta3 kernel and preview in camerafx is broken (colorful stripes when recording). It was fine on previous builds - kernel update was fixing this issue, but not this time. So what can cause this behaviour?

Wysłane z mojego SM-G900F
[Galaxy S 5 Original Android Development] andip71:
...maybe it is broken in todays CM.

Kernel is 100% up to date with todays CM.

If you can test with stock kernel, we would know more...

Andi
[Galaxy S 5 Original Android Development] gboros:
Thanks for the update!

Are you having WIFI drops in opo or s5? And just to know your opinion, do you think it can be kernel related?

Thanks!
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
It's cm related. S3 and S4 have it too.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] thejester123:
WiFi does turn off eventually when screens off due to marshmallow's native " Doze " feature.
[Galaxy S 5 Original Android Development] andip71:
Yes, these are the "wifi drops" we all sooner or later are faced with.

If this is a doze feature and not working better in future, it is a killer.

Andi
[Galaxy S 5 Original Android Development] HorstiG:
Delete this app and the problem is solved

/system/priv-app/SamsungDoze/SamsungDoze.apk
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
I don't think so...

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] BrX91:
Strange behaviour part2: flashed build on top of existing one with gapps - ROM is not booting. After flashing Your kernel it is booting fine again. Dunno why this is happening. Don't have time now to clean flash to test it tho. :(

Wysłane z mojego SM-G900F
[Galaxy S 5 Original Android Development] FlemishDroid:
You can also deactivate doze function per app. I think deleting SamsungDoze isn't the best "solution". :)

Verstuurd vanaf mijn SM-G900F met Tapatalk

---------- Post added 05-01-2016 at 12:00 AM ---------- Previous post was 04-01-2016 at 11:56 PM ----------

I thought normal Doze function kicks in after some hours when screen is off but why wifi drops already after some minutes when screen is off? With aggressive Doze function like in Greenify and Naptime it kicks in after some minutes.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] andip71:
This is also my understanding, but we all do not know if and how properly Doze is already implemented in CM13.

Andi
[Galaxy S 5 Original Android Development] FlemishDroid:
I also saw on some threads that people don't received notifications on stock Marshmallow maybe also related to Doze.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] roxdragon:
Hi i nave a galaxy s5 900f with cm12.1

1. What's the correct versione for me? COS or Cm? Whats the difference?

2. Can i flash this using twrp?

Thank you
[Galaxy S 5 Original Android Development] andip71:
1) There is no COS for the S5, that only exists for the OnePlus One.

You need version CM12.1 - Test: 2.3-beta9 for the S5.

2) yes

Andi
[Galaxy S 5 Original Android Development] roxdragon:
Thank you! Number one my friend!
[Galaxy S 5 Original Android Development] theslashy:
Dumb Question:

I love the Double Tab to Wake option, but:

When i put my phone in my trousers pocket it always get switched on.

I thought the double tab to wake option uses the proximity sensor to check if the phone is in the pocket or not ?

---------- Post added at 05:42 PM ---------- Previous post was at 05:42 PM ----------

Dumb Question:

I love the Double Tab to Wake option, but:

When i put my phone in my trousers pocket it always get switched on.

I thought the double tab to wake option uses the proximity sensor to check if the phone is in the pocket or not ?
[Galaxy S 5 Original Android Development] andip71:
Yes, on CM12.x and below. On CM13 it does not seem to work properly anymore.

For now you need to live with it or switch it off, investigating this takes too much time for the moment. Sorry.

Andi
[Galaxy S 5 Original Android Development] theslashy:
Ok, i hope for a fix anytime! Thanks for your work!!

//edit:

i just checked if the proximity sensor works at all and it works fyi
[Galaxy S 5 Original Android Development] andip71:
I hope, honestly, some other dev can fix it.

I did not write this feature at all, and I am a bit reluctant to fix it as this would take me probably many hours if it is possible at all.

So, for expectation management: Do not expect anything for the next weeks by me. Especially as it seems a lot of work on the sensors is required anyways.

It is a "shame" such a phone does not have this feature available from stock, so all we do is something a bit shaky.

Andi
[Galaxy S 5 Original Android Development] fbs:
simple_ondemand GPU governor freezes my phone. just me?
[Galaxy S 5 Original Android Development] ScratMan38:
Coming back with the "Unable to start camera" issue when using the kernel with SELinux set on Enforce.

I tried to fully wipe the phone, and install only the ROM, no custom kernel, no Xposed, no mod, no Google App.

After first boot, the stock kernel is set on Enforcing, and ... camera doesn't work.

Log is attached.
[Galaxy S 5 Original Android Development] andip71:
This governor is not stable in all cases. Known.

So you say your camera does not start even with stock kernel?

Just to confirm...

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Yes.
[Galaxy S 5 Original Android Development] andip71:
Wow, when it does not even work with stock kernel... wipe already tried? Full install via ODIN already tried?

In the end, if all that does not help, might be even a hardware issue.

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
I saw there'll be many kernel changes in the upcoming nightlies ?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Yup, wanted to provide an update yesterday already, but the build on CM side failed. So an update will come today.

But - no significant or important changes as far as I have seen. Anyways, lets put them in.

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Thanks!

Oscar Kratochvil is very active on kernel development for the S5...

Gesendet von meinem Xperia Z3 Tablet Compact Wifi mit Tapatalk
[Galaxy S 5 Original Android Development] ScratMan38:
I wiped everything, except internal storage and SDcard (didn't take time to backup everything on my PC).

I remember I returned to TW via Odin on 1st of December, because I had to rebuild NVRAM due to GPS Lock issues after flashing unofficial 29/11 build.

While on TW I updated the camera firmware, maybe this is the root cause.
[Galaxy S 5 Original Android Development] andip71:
CM13 kernel maintenance update

Hi all,

as promised, CM team was doing some work on kernel side, so here we go for the maintenance update:

Version 3.0-beta4

07.01.2016

Update: Updated with latest official CM kernel commits as of 07.01.16, 6am CET

Ramdisk updated to official CM13.0 version of 07.01.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] andip71:
[MENTION=4188231]theslashy[/MENTION]:

Dude... would you be interested in testing a kernel where I might have fixed that issue?

I think in this test kernel, proximity sensor is now correctly being used again.

Let me know pls.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
I reinstalled TouchWiz, using BOK6 base (bootloader BOK6, modem BOK5). I checked the kernel SELinux status, which was enforcing, then I tried the camera, and it worked fine. I then opened the camera diagnostic app to check its firmware version, and it's up to date (all camera, phone and loaded firmwares revisions are matching).

So then I installed the latest official CM13 build (January 7th), and when trying to open the camera, I got the "can't connect to camera" message.
[Galaxy S 5 Original Android Development] andip71:
What when you install yesterdays nightly, or one before?

Maybe something is broken in todays nightly exactly for your camera module...

Just an idea.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
I tried with January 5th, and it have the same poblem. I tried with the first official nightly, same issue, and on unofficial build from 27th december... always same problem.
[Galaxy S 5 Original Android Development] andip71:
Ok, then my last idea.. does CM12.1 also not work for you?

Just to make sure the issue is somehow CM in general and not specifically CM13 related...

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Which camera do you use? Perhaps it's that.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] ScratMan38:
Tried stock CM camera, Google Camera, Snap Camera HDR and A Better Camera Unlocked. All four can't connect to camera with SELinux set on Enforcing.
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Fresh install? Are you using xposed?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] ScratMan38:
I tried with clean install, with stock CM kernel, without any mod, no Xposed, nothing. Full stock CM. Still doesn't work.
[Galaxy S 5 Original Android Development] andip71:
I don't want to get rid of you and your issue, but I fear - as it is related to stock even - nobody here can help a lot.

Wouldn't that be a topic for a CM13 rom thread instead?

Thanks

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
I think my vibration motor is borked. Always on 50% but it is just vibrating softly. Missed a few messages and a call... I try with stock kernel.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Tried it here, vibration motor on 99% is much stronger than on 50%, and much weaker on 5%. So, on my side it works.

Hope it is not hardware, for vibration motor it can happen as it is mechanics.

Andi