yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] ScratMan38:
Still LED notification issue when brightness is set to 0.

I tried by receiving a message, the LED is still on.
[Galaxy S 5 Original Android Development] andip71:
You are sure you set the brightness to 0, not the speed?

Because speed=0 means: continuous light.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Sure
[Galaxy S 5 Original Android Development] andip71:
Ok, I am off for rest of today.

We have "Fathers-Day" in Germany, and I was already for too long at my PC doing kernel stuff today. Rest of the day is reserved for my family.

CU again tomorrow

Andi
[Galaxy S 5 Original Android Development] HorstiG:
OT Sauf nicht zu viel :)
[Galaxy S 5 Original Android Development] Webtag:
[MENTION=947981]Lord Boeffla[/MENTION] it isn't possible to enable high touch sensitivity or touchscreen hovering on your kernel. Can you fix that?
[Galaxy S 5 Original Android Development] andip71:
I dont think I can "fix" that as I have not changed anything in that area at all. So I would be more than surprised if something is broken compared to CM stock kernel.

But I never tried it myself, is it available in CMxx roms at all?

Andi
[Galaxy S 5 Original Android Development] Webtag:
The settings is available under language & input. I found out that high touch sensitivity works if I use an app called Galaxy s4 glove mode. I have to fix permissions in the app, and then it works till the next reboot. I still haven't found a way to enable hovering

---------- Post added at 08:07 AM ---------- Previous post was at 07:59 AM ----------

Found an an app which enables hovering. It is called [Root] Hovering finger. You find both apps in the play store. When turning hovering and high sensitivity on in the apps, you see the slider go to ON in settings

---------- Post added at 08:24 AM ---------- Previous post was at 08:07 AM ----------

Haven't found any app that hovering works in though. I can see the capasitive buttons light up when I hover above the screen, but that's about it.

EDIT: it also works in the app
[Galaxy S 5 Original Android Development] andip71:
Boeffla Boot Animation !!!

Hi all,

quite late, but better late than never (was too busy in the past 2-3 weeks).

Hardcore fans that like to have a Boeffla-Kernel boot animation can now be happy.

User "mateepunkt" created two boot animations which you can flash in recovery. One for 720p and one for 1080p devices.

Please find everything in a new download section on the homepage called "Downloads General".

http://www.boeffla-kernel.de/index.php/downloads-general

Sneak peak how it looks like:

https://www.dropbox.com/s/utu72jdozs1kjtn/VID_20150515_123512_rotated.mp4?dl=0

Thanks to mateepunkt for these boot animations, as well as for your recent Galaxy S5 Boeffla-Kernel fan trailer :good::good:

Cheers

Andi
[Galaxy S 5 Original Android Development] HorstiG:
Very nice boat animation. My phone starts now 5 times faster. But where is the sound?

HGT - S5 G900F - Oneplus One - Tesla TTL7
[Galaxy S 5 Original Android Development] venereo:
On this version after flashing supersu 2.65 boeffla config claims it can't detect kernel although it is installed (see attached screenshot)
[Galaxy S 5 Original Android Development] andip71:
No idea why Supersu is causing trouble again.

I always use CM internal superuser...

Andi
[Galaxy S 5 Original Android Development] venereo:
Didn't had any problems on previous boeffla versions.... But supersu flashes correctly and root is OK, it's just when launching boeffla config.
[Galaxy S 5 Original Android Development] andip71:
For sure some of the new security stuff... I will look into it, but not very quickly as I am tied up with video conference meetings today.

Andi
[Galaxy S 5 Original Android Development] venereo:
No problem, will revert to beta14 meanwhile :)
[Galaxy S 5 Original Android Development] andip71:
Identified it already, it so such a pity. But well...

Andi
[Galaxy S 5 Original Android Development] venereo:
Didn't catch that.... It's not fixable?
[Galaxy S 5 Original Android Development] andip71:
Yes, it is fixable.

But I am angry on that stupid SuperSu, it behaves so much different to internal CM superuser sometimes.

Andi
[Galaxy S 5 Original Android Development] venereo:
Can I ask why su binary is in kernel? Cause before installing supersu and with internal cm root disabled when I enter boeffla config I'm offered to install su Binary on next reboot but that does not work...
[Galaxy S 5 Original Android Development] :
What's the best profile, governor, etc. for battery life (no uv or anything risky like that) ? I'm struggling to get 5 hours of screen on time on CM13 with every possible wakelock disabled and I used to get 5 and a half to 6 hours of screen on time on CM12.1 easily.
[Galaxy S 5 Original Android Development] yurividal:
Hello, I am Running Resurrection Remix ROM (CM13 based) and latest Boefla Kernel.

I have noticed that after installing the Kernel, my Clock App (Stock CM clock) force close, if my SeLinux is Enforcing. It only works with Permissive. I went back to stock CM kernel, and clock works again with both SeLinux modes
[Galaxy S 5 Original Android Development] andip71:
[MENTION=4300580]venereo[/MENTION]: Can you please re-download beta15 now and try again?

It is in for autoroot, which is historically made for stock roms.

On CM this does not always work (as you noticed), but as CM comes with an own superuser it is not critical.

Look at OP.

My kernel is for CM, other roms can cause all sort of issues.

Andi
[Galaxy S 5 Original Android Development] venereo:
Working fine now, thanks for fast fix!

But since now supersu patches boot instead of writing to /system and since you already pack binary inside kernel aren't you in a good position to patch boot image yourself, maybe as an option in boeffla config?
[Galaxy S 5 Original Android Development] andip71:
Thanks for confirming.

No, honestly, rooting is meanwhile a science of its own. So I will rather remove this autoroot functionality on CM kernels.

It is just not controllable anymore.

Thanks

Andi
[Galaxy S 5 Original Android Development] venereo:
It's fair. Can I then automatically flash supersu after kernel update? Maybe through scripting setting? Haven't found any documentation about it
[Galaxy S 5 Original Android Development] andip71:
Only when you download the kernel and then use the TWRP screen in Boeffla-Config to execute the sequence:

- flash kernel

- flash supersu

... or you use internal superuser and do not have that hassle at all anymore :)

Andi
[Galaxy S 5 Original Android Development] venereo:
It's not a hassle, it's a pleasure ehehe.

Internal superuser app lacks re-authentification and more importantly, LOGGING. I like to know what root apps do.

?
[Galaxy S 5 Original Android Development] dmcleod:
After flashing boeffla 15, the boeffla app doesn't recognize the new kernel. "kein kompatibler Kernel erkannt"

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
If you would read up a bit... pretty sure you are on SuperSu, which is causing some incompatibilities.

Solution: Download the kernel again freshly (!) and flash it.

Andi
[Galaxy S 5 Original Android Development] The_Voice_70:
beta15 works fine on CM Nightly 09.03.16. No Reboots. Smooth and stable on Crazy S5. Excellent Deepsleep..;) Great Work, Andi.

[MENTION=535343]all[/MENTION]:

Please guys ... use the Kernel ONLY on ORIGINAL CM13. Don`t use this crappy SuperSU or xposed or something else. So you`ll have less problems;) Listen to Lord Boeffla wise words;)
[Galaxy S 5 Original Android Development] j1gga84:
I don't agree, never had any problems since switching to a CM13 based ROM.

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] venereo:
Of course, let's blame supersu and xposed for all the problems in the world. Seriously, get real, nothing is perfect, boeffla kernel included.

Obscuring things don't make things more perfect than they are
[Galaxy S 5 Original Android Development] n01z:
Uhh.. but SuperSU and Xposed ARE responsible for all of the problems in the world!!

The USER (not super) could NEVER be at fault....
[Galaxy S 5 Original Android Development] andip71:
The thing is - SuperSu on CM is not the reference.

There is a built in superuser concept, which works very well and in the end (I found) causes less issues than SuperSu.

All the latest SuperSu development (especially systemless root) is looking very obscure to me.

E.g. I definitely do not like I have to flash SuperSu again after every kernel update just to ensure I still have root.

There might be roms like Sammy stock where this is required, but on CM I personally do not see SuperSu required at all. I know you have a different opinion and I respect this, we have a free world and you have a free choice.

Anyways, it is fixed but for sure it will cause trouble again in future.

About xposed - here my opinion is clear and strict. This should become forbidden officially, at least for 98% of the users.

There are reasons why I do not support users using it, and I will never change this attitude :)

Andi
[Galaxy S 5 Original Android Development] benjamen50:
I flash superSU and xposed framework everytime after updating cm :p with boeffla kernel too.
[Galaxy S 5 Original Android Development] andip71:
Well, that is your "fault" :D :D :D

Andi
[Galaxy S 5 Original Android Development] fbs:
See? I'm using a "galaxy core prime" charger, which is rated as 750ma and it is really showing it. It works dude... Lol
[Galaxy S 5 Original Android Development] andip71:
Good.

I do not trust it a lot, but if you guys are happy with it - fine. I brought it back for you after the vote.

Andi
[Galaxy S 5 Original Android Development] venereo:
You just have to reinstall supersu when updating kernel, supersu now doest write itself to system anymore, it patches boot image
[Galaxy S 5 Original Android Development] venereo:
Supersu 2.65 worked well on Boeffla beta 9, beta 10, beta 11, beta 12, beta 13 and beta 14. The same supersu 2.65 stopped working on beta 15, and correct me if I'm wrong, that's not a problem with supersu 2.65.

Regarding xposed and with all due respect to the folks that created xda who had the vision to do something different on their devices even when 98% was tolding not to, xposed deserves the same respect. I understand devs hate it (don't really know why can just check stack trace, spot it, and ignore the report) the same way CM will ignore my bug report with boeffla kernel installed
[Galaxy S 5 Original Android Development] andip71:
It was breaking due to a change I made.

But the change worked fine with internal superuser which comes with cm.

For me this is the reference.

So in my opinion, supersu is not behaving correctly and fully compatible on cm.

And xposed is... It will get censored, so I rather stop here. Lol.

Andi
[Galaxy S 5 Original Android Development] j1gga84:
Maybe [MENTION=631273]Chainfire[/MENTION] could say something concerning that supersu issue - but I have no issues at all.. Very strange.

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] andip71:
There is no issue anymore with latest beta.

Still the superuser implementations behave differently. And this was my whole point.

Andi
[Galaxy S 5 Original Android Development] venereo:
You just HATE xposed ehehe you have the perspective of those who just download 30 modules all activated at the same time doing the same thing and then you have the perspective of who can hook to any function. That is a really true power, even if you don't understand it.

Regarding supersu sorry but putting su binary update on changenotes and then saying supersu is not a reference doesn't seem compatible statements

:)
[Galaxy S 5 Original Android Development] andip71:
Yes, I hate xposed, and it is my good right to do so.

I don't have to justify that.

The other stuff you got wrong.

The Supersu Update in the change log has zero to do with the situation.

In fact it was never used unless you autorooted with the kernel (which I removed actually today in the app).

So one has nothing to do with the other here.

But we can stop discussing here, it leads to nothing and just eats my time.

I made my point and stick to it.

Andi
[Galaxy S 5 Original Android Development] venereo:
This is not a discussion!

Thanks for fixing it :)
[Galaxy S 5 Original Android Development] andip71:
Thanks, you are welcome mate.

All good [emoji2]

Andi
[Galaxy S 5 Original Android Development] DirkStorck:
I am using beta 2.68 and it's working without a problem
[Galaxy S 5 Original Android Development] Blooperto:
What happened to 2200ma ac charge limit? I remember my s5 charger was a bit hotter than now[emoji14]

Enviado desde mi SM-G900M mediante Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Yes, I hot fixed the issue 1 hour afterwards.

This was contained and explained in the change log when I changed the max charge current.

Just read...

(you can always see the change log history on the homepage or in the menu of Boeffla Config app)

Andi
[Galaxy S 5 Original Android Development] Blooperto:
Didnt know about in app changelog. ty

Enviado desde mi SM-G900M mediante Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Yep, no problem.

Guess it is time again for me to push a "did you know" message out to make this more known to people :)

Andi
[Galaxy S 5 Original Android Development] The_Voice_70:
If things not work with Super SU or xposed:

In German I say: Ich verteile dann Zewa wenn ihr alle herumheult wenn es nicht läuft. Aber dann erwartet keinen Support von Andi. Ist ja schlimm;)))
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
The S7 feels empty without boeffla kernel... :/

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
;)

That will not change (un)fortunately...

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
Sad sad sad but it was known before ;)

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] The_Voice_70:
Oh Guys ... Andi has only two arms and two legs .... and one brilliant head. ;) And a wife and a hard job. Remember that. If you want somerhing : spend a S6 and S7. If I would have the money I would do it. Really. It is no joke. I like to work with Andi and check all the things he make. Boeffla ist the "mainest part" of my phones. Ok ... I`m crazy. But I like it. I learned something in my life: If you want something ... at first GIVE something. As a gift.
[Galaxy S 5 Original Android Development] andip71:
But just to get it right and make it clear:

Even if people would donate enough for a Galaxy S7 or whatever - I will not work on a kernel for it.

I dumped Samsung finally for good, not interested in their devices anymore as long as they have knox, efuses, flash counters and other hurdles.

If people want open phones without any restrictions, there are other options available.

Andi
[Galaxy S 5 Original Android Development] Christiancs1969:
Agree. S5 is my last Sammy. I gave back s6 edge..
[Galaxy S 5 Original Android Development] DirkStorck:
What other phone do you have in mind? If any ?
[Galaxy S 5 Original Android Development] venereo:
Phones that are supposed to be used as payment in future will all have efuses

Sorry!
[Galaxy S 5 Original Android Development] andip71:
I am going with the complete oneplus suite.

Everything is allowed there. Opening bootloader is allowed, even rooting is.

Good prices for good hardware.

Andi
[Galaxy S 5 Original Android Development] andip71:
Reference?

Andi
[Galaxy S 5 Original Android Development] venereo:
No references! Makes no sense making payments with a tampered phone, just check nexus 6p. Not that efuses will make your phone stop working, but it's the only way to guarantee a non-tampered phone for money transactions
[Galaxy S 5 Original Android Development] andip71:
I would not bet on that, time will tell :)

At least when I am not able to get a phone without that kind of nonsense, I will definitely retire from developing finally. I want to control my phone, not the other way round. And I do not need this online payment stuff, not as long as I still live :)

Andi
[Galaxy S 5 Original Android Development] venereo:
By payment I mean NFC. Neither Knox or 6p efuses forbids personalization, it just marks permanently the phone as tempered (makes sense)
[Galaxy S 5 Original Android Development] andip71:
Still, I do not like some fuses to be blown in my personal smartphone.

I will go for models without all that disturbances as long as I can go. And this means automatically = no Samsung anymore. Which I do not at all regret looking at my current main phones.

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

quick maintenance update to the CM13 kernel:

Version 3.0-beta16

13.03.2016

Update: Ramdisk updated to official CM13.0 version of 13.03.16

Change: Cleanup of ramdisk after removing legacy files

Enjoy

Andi
[Galaxy S 5 Original Android Development] iamnotkurtcobain:
I think my S5 with cm13 and your kernel is smoother than my S7 lol. Touchwiz is evil...

Gesendet von meinem SM-G930F mit Tapatalk
[Galaxy S 5 Original Android Development] The_Voice_70:
Use Nova Launcher.... it´s much faster ..:D:

---------- Post added at 09:54 PM ---------- Previous post was at 09:53 PM ----------

3.0 beta16 with today`s nightly is really fast. Thanks fpr Update, Andi ;)
[Galaxy S 5 Original Android Development] venereo:
By touchwiz he meant the whole sammy rom, not just the launcher.
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=947981]Lord Boeffla[/MENTION]

SAMSUNG released the Source codes for Marshmallow

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-g900f

Hope this is also relevant for kernel development? :)

Anything regarding microphone?

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] !crazy:
So, non-tampered state here means free of all modifications producer (and still owner) doesn't like? All other issues like buffer overflows, insecure design (like running three operating systems simultaneously.), backdoors, tons of totally useless crap software which occupies one's RAM and CPU only serving as an attack surface, Samsung who probably still sends our data to NSA servers (ok, only proved fact is that Samsung was sending Voice over IP packets over ip addresses which were, and maybe still are, in possession of NSA.), uninformed, clueless user blah, blah.

Samsung needed months, like over year, if not years, depending on the area, to release security updates, and you see efuse as a feature of critical significance?

I would rather strip a system down, remove useless stuff, lock down the privileges, encrypt whole system (all partitions instead of running a kind of an encrypted VM which leaves the rest of the system unprotected.), while still being able to flash latest patched builds from CM, AOSP, etc..
[Galaxy S 5 Original Android Development] andip71:
Yes I do.

I don't like something can change / destroy hardware irreversibly on a phone I bought from my hard earned money.

Efuse is a complete no-go for ne, as flash counters and knox.

As long as I have alternatives to that I will take them and show Samsung my naked a...

Andi
[Galaxy S 5 Original Android Development] venereo:
Efuses have nothing to do with preventing modifications, locked bootloaders do that very well already. You keep talking about Samsung but nexus 6p is a Google phone and ships with efuse. For me makes no sense making payments with a tampered phone the same way you can't use a tampered credit card to pay. Efuses became affordable and now you are going to see them more in hardware, I can only imagine how they are going to be used. Today the only use I see its some apps refusing to run cause of a efuse (my Knox don't run with knox 0x1) but that already happen when for example banking apps refuse to run on rooted devices) but I really don't see why that should bother who like to modify devices, it did not prevented me from modifying my device

---------- Post added at 04:30 PM ---------- Previous post was at 04:00 PM ----------

@Lord Boeffla, maybe you know of a way of hiding root status from one app without using the infamous Xposed? :)
[Galaxy S 5 Original Android Development] andip71:
It is just: I do not like something blows (which is a physical damage to my phone) for something I buy and want to modify.

So far it does not prevent one from modifying, but what in future?

I am strict here - no phone with efuse.

And on your second question: You could replace the hash bitmap in the framework file by a transparent png. Some people did that in the past, then it was gone.

But requires you to decompile the framework apk, change the pic, compile it again.

Or at least replace it and zipalign it again.

However, needs to be done after every update again, so not a nice solution.

Andi
[Galaxy S 5 Original Android Development] venereo:
Bootloader already makes impossible to install costum rom, efuses will have other uses.

Regarding second answer most apps bank will have some kind of tamper protection. This is the kind of things xposed is good at: just find function responsible for checking root status, subvert return value with xposed and you are done. But I understand people hook to framework / system-wide functions without thinking about side effects and I guess that gave xposed a bad reputation
[Galaxy S 5 Original Android Development] !crazy:
I criticized efuse, and asked the guy how can he consider efuse as a serious security feature, and you answered, instead of him, that you do consider it an important security feature, but you don't like it?
[Galaxy S 5 Original Android Development] andip71:
When did I ever say I consider it an important security feature? I must have been drunk if I did.

E-fuse for me is an annoyance, something nobody needs, complete bull**** and nonsense. It makes me not buying a phone when it has an e-fuse.

I think that is clear enough, or? :)

Andi
[Galaxy S 5 Original Android Development] !crazy:
I have no idea how your quote ended in my post, but it was not my intention to discuss the issue with you.

The whole post of mine was written as a response to venereo or whoever.
[Galaxy S 5 Original Android Development] andip71:
No worries. XDA forum fooling us, hehe.

Andi
[Galaxy S 5 Original Android Development] !crazy:
Sorry I see know that my question (you answered with 'Yes I do' can be a bit ambiguous, if one leaves another part of my post ☺, what is one really encouraged because of my urge to type at least 2k characters in a forum post/reply.

Basically I asked him how can he consider it as a so important feature, in a situation like this, where Samsung needs years to release security fixes, force us to run bunch of apps (even the whole VM!) we don't need/want, what it self is a security issue, etc.
[Galaxy S 5 Original Android Development] venereo:
Just to make it worse, I don't really belive there is any efuse. It's very weird that bootloader version that start enforcing Knox flag was released latter than the device itself. I think it's just a maneuver to discourage hackers
[Galaxy S 5 Original Android Development] f0xy:
I'm with Andi

Keep phones and payments/cards separate.

A smartphone will not replace a card it will only ever serve as an alternative, personally I think the hype will die down soon, it's as simple to whip out a card to pay than change what you're doing or get out your phone to pay...

Just my 2cents, now back to topic :)
[Galaxy S 5 Original Android Development] n01z:
Lord Boeffla,

I have a question about using the kernel with newer CM nightlies. So far, I have only been updating my CM when you release a new kernel version (your changelogs usually say the date of the nightly used with your kernel update, so that's what I use)..

My question is:

Should there be any issues running the kernel with newer CM nightlies? Like, is there anything in particular that I should look for in the CM changelogs on http://www.cmxlog.com/13/klte to indicate potential incompatibility with the latest kernel version??

I just find downgrading Android to always be a pain..