yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] andip71:
Thank you so much, Horst.

Appreciated, as always. Thought you already moved on to tge s6 ?

Andi
[Galaxy S 5 Original Android Development] HorstiG:
Yes, but all with Stock at the moment, buaaaaah,

All works great, realy, but TW is sorry (zum Kotzen)
[Galaxy S 5 Original Android Development] The Peterle:
I have also no WiFi issue with beta 10 on official nightly 1905.

I read something about new kernel commits in the next mega nightly. Perhaps we need a kernel update again.

Regards Peterle
[Galaxy S 5 Original Android Development] andip71:
At least I see some new commits dropping in, so... yes. I think an update is then advicable to be done by me :)

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
If we ever get a next nightly. 3rd night without one...
[Galaxy S 5 Original Android Development] andip71:
It's even worse on the OnePlus... no nightly for the 4th night in row :)

Andi
[Galaxy S 5 Original Android Development] venereo:
Update bootloader? I'm still on KK! 100% OK.
[Galaxy S 5 Original Android Development] ScratMan38:
[MENTION=947981]Lord Boeffla[/MENTION] : the new beta kernels with anykernel concept does not work with my camera.

I tried several combinations with CM13 builds :

- July 11th

- July 14th (containing a camera wrapper cleanup)

- July 17th

and kernel :

- Boeffla 3.0 stable

- Boeffla 3.1 beta1

- Boeffla 3.1 beta2

- CM Stock

Only the stable Boeffla 3.0 kernel with SELinux set to permissive at boot makes the camera work. :crying:

Here are the logs with the kernels :

- stock CM

- Boeffla 3.1 beta2

- Boeffle 3.0 stable
[Galaxy S 5 Original Android Development] andip71:
Time to fix your underlying problem, eh?

No seriously - no idea. My camera never required selinux set to permissive at all. So there seems to be something (which I do not know) wrong.

And when the camera even does not work when the kernel is set to permissive after boot, well... what should I say.

I never came across someone else, who had to set the kernel to permissive to make the camera work. It seems you are the only one having this issue all over the world?

Please excuse me, but I have no clue how I could help here.

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

maintenance update out for you.

I decided to remove the zip signature from the flashable zip as it turns out to cause trouble for many recovery versions.

As it, at the same time, provides absolutely zero advantage (everone can unpack the zip, change content, zip and sign it again with the test keys out in the web - so there is anyway no security the zip was not touched since I released it), so why causing trouble for nothing...

CM13 -- Version 3.1-beta3

18.07.2016

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

Change: Removed zip signature to be more compatible with certain recoveries

(do not forget to configure your recovery to bypass signature checks;

when flashing the kernel out of Boeffla-Config's TWRP screen, this is done automatically temporarily for Boeffla-Kernel zips)

Enjoy

Andi
[Galaxy S 5 Original Android Development] DirkStorck:
Flashed und running fantastic with RR.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] j1gga84:
Good morning Andy,

Just for information:

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

It seems that some kernel related fixes are on it's way ;)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
And guess what... The new kernel is already compiled and ready to be shipped.

Just waiting for nightly to arrive so I can do a quick check.

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

here we go for the promised CM13 maintenance update with latest CM code changes in.

Version 3.1-beta4

20.07.2016

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

Enjoy

Andi
[Galaxy S 5 Original Android Development] Xtreme.Infinity:
Hi Andi,

I'm running latest CM13.0 nightly with its kernel.

I just wanted to ask that in your "downloads general" section on your website, there is a cleaner script for G900F. Do I have to run that script before flashing the kernel file or it isn't required?
[Galaxy S 5 Original Android Development] andip71:
Only required when you had elemental kernel before. Otherwise never.

I think I should remove it, as almost nobody (afaik) still uses elemental.

Andi
[Galaxy S 5 Original Android Development] andip71:
Good morning,

maintenance update for CM13 kernel:

Version 3.1-beta5

22.07.2016

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

Enjoy

Andi
[Galaxy S 5 Original Android Development] bluesman1306:
Thank you :)
[Galaxy S 5 Original Android Development] ScratMan38:
Hello My Lord ;)

Coming back on my issue, as my camera started working after flashing kernel 3.1 beta 4 (still in permissive).

I then tried to understand why it suddenly and unexpectedly started to work... and I remembered I flashed beta 4 over stable 3.0.

I tried the following :

- clean flash CM13, no custom kernel ==> SELinux is forced to Application ==> camera crashes ==> use init.d script to set SELinux to permissive on boot ==> camera crashes

- clean flash CM13 ==> flash 3.1 beta x ==> SELinux can be strict or not ==> camera crashes

- clean flash CM13 ==> flash 3.0 stable ==> SELinux set to strict ==> camera crashes ==> disable strict SELinux and reboot ==> camera works

- clean flash CM13 ==> flash 3.0 stable ==> flash 3.1 beta x ==> SELinux set to strict ==> camera crashes ==> disable strict SELinux and reboot ==> camera works

So it looks like there is something in the stock CM13 kernel that prevents my camera to work, that is not present in the 3.0 kernel, allowing my camera to work (but only in permissive). When flashing 3.1 beta, it grabs some parts of the original kernel, containing the thing that makes my camera crash.

But what ?

The issue for me being that the stock kernel and the ROM has been improved in the last few days (solving issues with vibrator, advanced display, BT, flashlight...) and these changes aren't in the stable 3.0 ; so by keeping the stable kernel, I can't profit from these changes, as some issues occurs more and more when the kernel becomes too old versus the ROM.
[Galaxy S 5 Original Android Development] andip71:
This is simple.

When you first flash Boeffla 3.0, it still comes with the ramdisk using permissive (it is a parameter when assembling the kernel) to start.

So when you flash latest boeffla over it, it will take this ramdisk and therefore it works.

When you use official CM kernel, it starts in strict mode.

So, it is still the same thing: SELinux.

But maybe you should start looking at the SELinux denial messages in the kernel log (dmesg command). Maybe this tells you which denial breaks the camera.

Andi
[Galaxy S 5 Original Android Development] Kenny13554:
Hey Andi,

just out of curiosity: What exactly about xposed is it you do not like? I'm using your Kernel on official CM13 with Xposed, using 10 Modules, and had no issues whatsoever. Is it just that it poses a possible risk if mis-configured or are you worried about something in particular (e.g. modifications in ART etc.)?

No criticism, just plain curiosity and the hope to gain some more insight. Who am I to criticize the lord anyway, right? ;)

Best,

Kenny
[Galaxy S 5 Original Android Development] andip71:
xposed is too powerful for most users, it allows you to completely screw up the system, also to lead to all sort of side effects.

I cannot count how many times people were using an old Boeffla-Config version because the auto updater did not work as they removed internet connectivity right via xprivacy from the app. And this is only one example of many.

In short - it causes support work for no use. So I do it the same way Cyanogenmod officially does: Xposed = I do not accept a bug report

Andi
[Galaxy S 5 Original Android Development] Kenny13554:
haha okay, that's what I thought. So I think I'm gonna continue using Xposed, as you do not seem to consider it as blasphemy ;)

thanks for the fast response, btw.
[Galaxy S 5 Original Android Development] andip71:
Sure, you can do what you like.

You just will not get my support, whatever happens.

And no, xposed is a serious thing. Too serious as countless smartphones have been rendered already a soft brick by it.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
I took some dmesg with the 3 kernels (cm stock, Boeffla 3.1 beta 5 and 3.0 stable). But I don't know what to look for in it.

I can see some lines in stock and 3.1 with "camera_check_event_status : event_data->status failed!" ; that is not in 3.0, that have more lines mentioning camera.
[Galaxy S 5 Original Android Development] andip71:
Hm, no. I cannot see anything helpful. Selinux denials are usually seen in all the lines containing the word "avc". But nothing is really logged which looks like camera.

Your S5 continues to be a mysterious diva.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
But dmesg returns the logging from end of boot, right ? it looks like the issue comes from the ramdisk, so the very beginning of the boot process.

Is it possible to see the log during boot at kernel start ?
[Galaxy S 5 Original Android Development] andip71:
dmesg returns everything since last boot, as long as the ring buffer is not overwriting old entries already. Which happens quite soon after start.

Make also sure, you have kernel logger switched on, btw.

And I do not know any way of seeing the messages during boot already. You can connect and access dmesg after adbd is up and running (this is before the rom comes up) via usb and adb interface. But these records you also get when running dmesg after the UI is loaded.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
I can confirm the buffer is saturated. I tried to read dmesg immediately after boot with Tasker, and the first line is already incomplete.
[Galaxy S 5 Original Android Development] ScratMan38:
Tried to set airplane mode to accelerate the booting process, got some dmesg with much more reference to camera.

By looking for "cam" in the logs, I can see many lines with some read errors in the stock and 3.1 logs, with some voltage regulators disabling/enabling/setting in between (tentative to reset the camera module ?).

In the logs from stable 3.0, there are many messages about camera firmware read and write, it looks totally different...
[Galaxy S 5 Original Android Development] Swizzy88:
I've been using this kernel for a few weeks now and really like it, especially the application it comes with.

Ive noticed there is some strange hotplug behaviour when max frequency of the cpu is limited to less than 2265mhz.

The other cores rarely turn on, only under extremely high load. As soon as I raise the limit to 2.2ghz and more hotplugging works as normal.

I've tried clean installs of rom+ kernel and have tried almost every combination of governors and settings. Any ideas?
[Galaxy S 5 Original Android Development] andip71:
Yes, I confirm that.

Something has changed in the April / May timeframe that causes it. I confirmed it working fine on a cm rom from early April.

Mpdecision does not switch cores properly anymore when the frequency is lowered below that frequency.

I have no solution for it, as mpdecision is closed source. A question to cm team also did not bring up something useful.

For the time being we have to list that as a known issue, and hope cm team will fix this one day.

Btw, it only applies to s5. OnePlus One and OnePlus x do not show this issue, although they use the same SoC.

Andi
[Galaxy S 5 Original Android Development] andip71:
Honestly, this would be something for an experienced rom dev to look into. Especially into the logcat logs.

As it is happening for you also on cm stock kernel, you should probably open an official bug in cn bug tracker.

I don't see I can be of more help in that topic anymore...

Sorry

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
I'm working on this with some devs of the CM kernel, they asked to provide some logs with adb during boot, and it shows some interesting things. Looks like the kernel founds the camera FW in companion chip's EEPROM, but fails to use it, breaking the camera.

Fingers crossed, hoping they will find a fix.
[Galaxy S 5 Original Android Development] andip71:
Ok. Really sorry I cannot be of more help here.

But please keep us posted how it evolves. This is very interesting.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Don't be sorry, you helped me a lot already, giving me the direction where to look, focusing the scope on the kernel boot.

And you already did so much and so great work to bring your kernel to our phone... really, don't be sorry :good:
[Galaxy S 5 Original Android Development] ScratMan38:
[MENTION=947981]Lord Boeffla[/MENTION] : just one question. You mentioned the only difference between stock CM kernel and you 3.0 stable kernel was that your kernel was booting with SELinux set as permissive, with option to switch to enforce at the end of boot thanks to the config app ; while stock CM kernel was starting in enforce mode directly, due to an option at kernel compilation.

So, I'm thinking about the possibility to compile my own CM stock kernel, from full CM sources, but with SELinux set to permissive.

Would this be possible ?

I would have a little bit more work, as I would have to rebuild the stock kernel everytime the kernel source code is updated, and then I would have to flash new nightly, then my customized CM kernel, followed by your kernel (but these three steps can be automated using CyanDelta, so not a big deal, I just need to create a flashable zip from my custom boot.img) ; but at least it would provide me with permissive SELinux, and working camera with latest CM and Boeffla updates.
[Galaxy S 5 Original Android Development] Swizzy88:
Thank you very much for the response.

I suspected mpdecision, it has caused trouble for almost every Samsung device I've owned when it comes to kernel development.

I think for some devices they managed to fully disable & replace mpdecision but I'm not a developer so I have no idea how it actually works.

I hope you will keep developing, it's a great kernel & app and its only getting better :good:
[Galaxy S 5 Original Android Development] andip71:
Well, this is certainly possible. And it is not hard when you already achieved compiling a kernel.

You can even base your work on my repo and switch to selinux permissive there, then you have your personal unofficial Boeffla-Kernel. And you can rely on me for putting the latest updates in.

With some luck (I never tried it though) you can probably make it work even without compiling the kernel. Selinux is a boot option parameter on the S5. So you could unpack even an existing kernel into zImage, dtb and ramdisk and repack it with this parameter added.

Would require some proof of concept though.

Just giving you some more ideas.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
GOT IT !!!!!

I finally managed to make my camera work with stock CM13 kernel, with SELinux set as enforce !!!

By looking at the logs I provided, and comparing with the log cal002 made on his phone, I found my phone tries to find some informations about the camera module in a missing XML file :

mm-camera-sensor: [mm]check_version:715 firmware version file system/etc/F16QL_s5k2p2xx_module_info.xml
mm-camera-sensor: parse_module_xml:103 Could not find or parse file system/etc/F16QL_s5k2p2xx_module_info.xml

This file is present in the stock Touchwiz ROM, but not in CM, so I tried to copy the xml file from the last Samsung ROM I used to flash my camera firmware, and placed it in the /system/etc/ folder on my phone.

I rebooted, and tadaaaaa !!! camera is working with stock CM kernel !!!!

I even tried to flash Boeffla 3.1 beta 5, and the camera is still working using either strict SELinux or not :victory:

Seems I need to make a script to automatically copy this XML file back in the system after nightly update.
[Galaxy S 5 Original Android Development] spaziomilano:
Wowwwww[emoji7]

Envoyé de mon SM-G900W8 en utilisant Tapatalk

---------- Post added at 10:25 AM ---------- Previous post was at 10:21 AM ----------

Is it possible to me to try this "easily"

Envoyé de mon SM-G900W8 en utilisant Tapatalk
[Galaxy S 5 Original Android Development] andip71:
First - congratulations to the successful investigation.

Did you provide this information to cm guys too?

Maybe they can improve for others too based on this information.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Yes I did. However I'm not sure they will implement something, as I found a workaround, not the root cause, so the issue is still not understood.
[Galaxy S 5 Original Android Development] RUSPO:
Hi guys, i want to flasch this kernel on my cm13 but when i do it with twrp i riceved a faillure message. Can you help me? Is there any guide to correct flasch?

Thank you
[Galaxy S 5 Original Android Development] DirkStorck:
I think [MENTION=1045701]lordbo[/MENTION]effla has written somewhere that you have to disable signature check in recovery as long as you don't flash kernel within the app what you can't do if you haven't installed the kernel before.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
If you would tell us the message, we could probably help.

Andi
[Galaxy S 5 Original Android Development] venereo:
Update to latest twrp. Twrp manager will be the easiest way.
[Galaxy S 5 Original Android Development] RUSPO:
thank you guys, i solved after i updated my twrp.
[Galaxy S 5 Original Android Development] fbs:
flashed over mokee and it worked.

later, I rebooted it, and (inexplicably to me) it entered in a bootloop. rebooted many times but bootloop.

formatted /system, reflashed mokee with gapps.. and still in bootloop

boy, did it screw up my /data again?!!

I know any non-cm13 is not supported, but I FORMATED my /system and reinstalled the same rom with its old kernel altogether... WHY will I have to "factory reset" again and again?!
[Galaxy S 5 Original Android Development] venereo:
If you dont like deleting data then you shouldnt be using cm13 in the first place. Nightlys are nightlys, you either backup often or just suck it up.
[Galaxy S 5 Original Android Development] fbs:
Nonsense, and doesn't explain anything. Why did you write at all?
[Galaxy S 5 Original Android Development] andip71:
I think he is partially right.

Cm13 and everything that bases on it is not considered officially stable.

So weird things can happen, and they do from time to time.

Andi
[Galaxy S 5 Original Android Development] fbs:
Ok, of course. I think I didn't make myself clear. The question is: installing boeffla kernel will modify anything on /data ?

If I did restore the /system to the way it were before installing boeffla, why the bootloop?

you can reply really technically if you have some time ... :fingers-crossed:
[Galaxy S 5 Original Android Development] andip71:
Boeffla-Kernel installation does not touch /data at all.

Neither during installation, nor during kernel start.

That is all I can say.

Andi
[Galaxy S 5 Original Android Development] venereo:
There a lot of variables there including using a beta kernel and a nightly ROM. But you can try sorting /data by date and delete most recent ones one by one.

Everybody understood you. You just cant complain about your data, no one really cares
[Galaxy S 5 Original Android Development] lucadalba:
Installed 3.1 beta 5 on CyanogenMod 13.0 Official.

It works fine.

I've installed SuperSU 2.76 as root and SuperSU app as root manager (NOT CM SU) and I have NO problems.

Thanks for all your work[emoji6]
[Galaxy S 5 Original Android Development] marouane80:
Hello,

These are my settings on CM13 for this kernel on SM-G900F (thanks to Boeffla) .

What inside ?

=> Just a script that run from init.d folder !

What to expect ?

- Long battery life (hyper deep sleep 1% of battery /6h) tested many time (thanks to sched_mc_power_savings)

- The smoothest UI experience (best OC config. I/O ...and many other things)

How to ?

. First uninstall any kernel tweaker (faux, k. adiutor), then flash the zip over recovery.

. Reboot

. Now test the new performance of your Galaxy S5 !

:good:
[Galaxy S 5 Original Android Development] airidosas252:
Funny thing is, that stock Touchwiz ROM is way more buggier than CM13. Random reboots, heating, browser crashes - this is like a routine happening with Touchwiz ROM. With CM13, it becomes weird that no bugs I mentioned happen. And neither of available kernels fix those issues and they are completely random.

Also, from my experience, conservative governor makes phone as fluid as you can possibly imagine, take it stock or CM13. Interactive governor is a lot more aggresive with CPU scaling and it's not recommended for those, who expect fluid animations and constant launch times.
[Galaxy S 5 Original Android Development] venereo:
The discussion is not which one has more bugs. The discussion is about complaining about your data. And that's users' responsability, either on cm13 or on touchwiz.
[Galaxy S 5 Original Android Development] dawid0089:
Butt boeffla config app i can use?
[Galaxy S 5 Original Android Development] marouane80:
i can't answer because i don't use any app for custom or original kernel. i always use my scripts. why don't try ? your life is your own experience ! :)
[Galaxy S 5 Original Android Development] andip71:
Hi all,

update to the CM13 kernel.

Version 3.1-beta6

01.08.2016

Change: Removed Boeffla Notification LED control (only fading switch is left)

Reason: CM built-in LED control is much more powerful nowadays (and Boeffla LED control conflicts with it), so use this in future to configure notification LED speed and brightness

Change: Internal download URL changed for kernel

Enjoy

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
But there is no option in CM to dim the LED brightness during the night... :(
[Galaxy S 5 Original Android Development] andip71:
That might be true.

Still you can, by chosing different (darker) colors change that for the night.

But honestly, during night I do not need any notification...

I am sorry, but it has more advantages than disadvantages to finally move on what CM has.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
It's not for the notifications, I keep my phone offline during the night, but I let it plugged on the wall charger, and it makes the charging light too bright., mainly when yellow or green.

With Boeffla kernel, I could use a dedicated profile for the night, with reduced charging current and reduced LED brightness.
[Galaxy S 5 Original Android Development] andip71:
Yep, you either can use a different (darker) color in the LED settings for charging light in the settings of the rom.

Or, if that is not flexible enough, you need to use 3rd party software like light flow to cover this very specific requirement.

I will, in any case, not bring that back anymore. It creates more conflicts than good, so my decision was taken.

Andi
[Galaxy S 5 Original Android Development] venereo:
Why dont you take some time to look at boeffla kernel app and share your settings as a profile?
[Galaxy S 5 Original Android Development] Mar-cel:
One core is always at 1036Mhz with latest kernel Version. it doesnt calmed down.

Is this a bug? Or relates to only me?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Must be something at your end (app, process etc.)

Here my overview screen with almost exactly the same configuration you have in terms of rom version, kernel etc.

Andi
[Galaxy S 5 Original Android Development] Mar-cel:
I've installed Greenify, Force Doze, Viper4Android and Xposed. I think one of those, is the problem. Now I just have to find out who...

How can i fully disable zRam as you have on the picture?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] carabinieri5675:
Disable greenify at first. It is recommended.

Resurrected OnePlus 3