yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] ghoster76:
1. No chance with a custom kernel

2. Zzmove could save battery but causing some lag. I'm always using stock interactive - governor profile: interactive - battery because I need a smooth TW. Or I'm using 7500mAh battery...

3. Using touch to wake that don't face off your phone with your skin. No battery friendly because you'd think about it, your phone always has to wait for your tap, steering instead it's going to deep sleep.
[Galaxy S 5 Original Android Development] festr:
1) even if the kernel is flashed through the running ROM (is that even possible?) I thought that the knox is tripped when flashing unsigned images through the download mode.

2) did you tried various profiles like optimized?

3) I do not understand. Is the double touch wake using CPU using wakelocks or not?
[Galaxy S 5 Original Android Development] andip71:
Correction on point 3) The touch wake implementation in this kernel does not use wake locks. So it is battery friendly. Of course unless you use it without a case in your trousers, so the touchscreen gets triggers all the time).

(you can see, it sleeps like a baby when screen is not touched)

Andi
[Galaxy S 5 Original Android Development] festr:
good point on trousers. I'm not using case and wear it in trousers so that would be problem and it will probably trigger / wake the phone all the time. Will have to test this. Maybe - one feature request - do not wake the phone based on proximity sensor ?
[Galaxy S 5 Original Android Development] andip71:
Already in.

Just give it a try yourself.

Andi
[Galaxy S 5 Original Android Development] festr:
I did a flash tonight so I had no chance to wear it yet and I just tried to cover the proximity and it works... amazing.

the last outstanding doubt needs to clear for me :) I know that the kernel can be flashed in running rom (rooted) back in SGS1 times. Is that stil possible on sgs5? It is just file (kernel) and modules right? Then if those are replaced when running the ROM - does the knox trips to 0x1 when rebooted? Anyone tested this?
[Galaxy S 5 Original Android Development] andip71:
The kernel can be flashed in running rom, yes. In fact this is how it works when the kernel gets updated by Boeffla Config.

Whether it triggers the knox counter, likely I guess. I cannot say, my knox counter was triggered already after 2 hours :)

Andi
[Galaxy S 5 Original Android Development] festr:
The knox is triggered when you flash anything through odin which is not signed by samsung. Did you flash it this way anything? I'm not sure how you mean that it was triggered after 2 hours :) Sorry just needs exact informations. I have one more device home where I would love to run your kernel but I do not want to trigger knox because of warranty void on this device (its wifes phone and you know **** happens :)
[Galaxy S 5 Original Android Development] andip71:
Of course I flashed with Odin.

What I wanted to say is: I could not care less about Knox counter. If it is triggered, it is triggered. Unless Samsung does not change this approach, I would anyways not go for another Samsung anymore.

Andi
[Galaxy S 5 Original Android Development] festr:
well so I guess I'm on my own to try to swap kernel to see if it will trigger the knox.
[Galaxy S 5 Original Android Development] andip71:
But be aware... I am pretty sure it will.

Andi
[Galaxy S 5 Original Android Development] Crussader:
it will, kernel or recovery flashing triggers it
[Galaxy S 5 Original Android Development] festr:
Even if the kernel is replaced during running ROM so it is not flashed in download mode? I will believe only if someone tried it.
[Galaxy S 5 Original Android Development] Crussader:
I meant Odin flashing or flashing a whole ROM through recovery.

<OT> Why dare to trip knox on a Wife's phone? you know what your getting into... right? ;) </OT>
[Galaxy S 5 Original Android Development] festr:
And I mean replacing kernel in rooted ROM (which is possible to do without tripping knox) - the applicatino can do that but I did not know it and flashed it via odin which obviously triggered the knox so I cannot test it again on my device. If I will replace kernel on another rooted device with knox 0x0 via the app (so no through odin) thats what I'm interested if the knox will be also triggered. If yes it means that there must be some mechanism which detects non-samsung kernel (ROM itslef or some hardware watchdog / bootloader? ) or in this case the knox will be NOT triggered.
[Galaxy S 5 Original Android Development] andip71:
I guess nobody knows 100% how knox and all the flash counters exactly work.

However, it would be a piece of cake for Samsung to check if the installed kernel is original or not - a simple signature on the kernel would do the trick, signed with a key only known to Samsung. Maybe they have that, who knows.

But this is not a speculation thread, just wanted to say, it is really simple if they want that.

Cheers

Andi
[Galaxy S 5 Original Android Development] festr:
I doubt that the samsung do any signature directly for the kernel itself or do any sophisticated ways to detect this. I believe that it is in the download mode but its pure speculation. If someone are willing to try this - here is steps I followed to get rooted lollipop without triggering knox https://www.reddit.com/r/galaxys5/comments/2ubsbs/guide_rooted_android_50_for_the_international/

if I change mind I will try to flash the kernel through the Boeffla application on my wifes rooted ROM. But the phone is 2 weeks old and I will probably need to wait some more time to wait if any HW issues reveals
[Galaxy S 5 Original Android Development] andip71:
Sorry, that does not work. Boeffla-Config App can only flash if there is already a Boeffla-Kernel installed.

So you would need to use Flashify or mobile Odin for that purpose.

Andi
[Galaxy S 5 Original Android Development] festr:
good to know, thank you. I already have the mobile Odin which I used to install the pre-rooted lollipop over the exploitable 4.x older ROM. Actually there is some kernel bug which allows to gain root on older s5 rom (4.x) then through the odin you can flash unsigned image without triggering knox - through the mobile odin so the download mode is not involved. But it has stock kernel. So I guess someone has to try this. Any volunteers? :)
[Galaxy S 5 Original Android Development] Looki75:
Can the kernel be flashed with FlashFire from chainfire? (http://xdaforums.com/general/paid-software/flashfire-t3075433)
[Galaxy S 5 Original Android Development] andip71:
Well, I never tried that tool (was not even aware a new tool is coming up).

But as flashing the kernel is nothing else than flashing an image file into a partition, I would guess this should be a piece of cake for any tool.

Andi
[Galaxy S 5 Original Android Development] ZaneZam:
yes my friend as u might remember that's exactly what they did on the S3 back then in newer versions of bootloader, signature check on kernel and recovery -> if any of these are not valid you got an exclamation mark

= warranty nuked. but on S3 it was easy to fix that as there were older bootloaders available which didn't had that check. still have that info in my signature for nostalgic reasons :)
[Galaxy S 5 Original Android Development] festr:
but is this signature check for the image flashed through the odin? Or is that signature check of the kernel file itself which I doubt
[Galaxy S 5 Original Android Development] andip71:
Bootloader. So it is checked during every start again and again.

Andi
[Galaxy S 5 Original Android Development] festr:
after a bit of googling seems like the secure boot is really checking signatures of bootloader, kernel and rootfs so without proper signing of the kernel with samsung private key the knox will be triggered no matter how it is flashed.
[Galaxy S 5 Original Android Development] andip71:
You could have believed us already a few hours ago ;)

Andi
[Galaxy S 5 Original Android Development] festr:
it would save me a lot of time ;) I'm just a guy who needs exact information / facts. Telling just "it will trigger knox" is not sufficient to me. This article (http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html) though it is for s4 convinced me.
[Galaxy S 5 Original Android Development] andip71:
New beta

Hi all,

I am back from holidays now, and want to release a small maintenance update for the Samsung Stock Lollipop kernel to you guys.

Version 1.1-beta1

11.05.2015

Ramdisk updated to version of firmware G900FXXU1BOD3

Enjoy

Andi
[Galaxy S 5 Original Android Development] ghoster76:
Lord? Just update the ramdisk? :rolleyes:
[Galaxy S 5 Original Android Development] DirkStorck:
Do you plan to add LED fading to the (TW) kernel ?

Thanks!
[Galaxy S 5 Original Android Development] andip71:
Yes and no.

Yes - I plan to add it.

No - I plan to not add it to TW kernel only, but when I add it then for all S5 kernels :)

Andi
[Galaxy S 5 Original Android Development] DirkStorck:
Thanks for the info ☺ TW was only a hint that TW is relevant for me [emoji3]
[Galaxy S 5 Original Android Development] PIRATA!:
...and it's practically impossible to sign custom kernels with the Samsung key....right?

Stupid question, right? [emoji16]
[Galaxy S 5 Original Android Development] andip71:
Already ported the S3 LED control over to S5 now. So it will be in next kernels.

No, as nobody has the signing key, only Samsung (that is the whole point about it).

Andi
[Galaxy S 5 Original Android Development] MewCore:
This sure explains the lack of sound mods for S5 :( The only sound implementation in other kernel I have seen is faux, don't know if this means anything positive?
[Galaxy S 5 Original Android Development] ca229872:
Hi...... My S5 has installed nova launcher. Will it work well?........Does it increase performance?.

thanks....
[Galaxy S 5 Original Android Development] ghoster76:
Wait for him, he has already owned this device. You'd expect him for the future than ask him a difficult question.
[Galaxy S 5 Original Android Development] f0xy:
I tried this kernel on KitKat, it doesn't work.
[Galaxy S 5 Original Android Development] andip71:
Of course not???

The thread says clearly Samsung Stock LP (LP = Lollipop).

Andi
[Galaxy S 5 Original Android Development] aceqott:
Thank you very much for sharing your work.

I set it up with stock ROM BOC7.

Be of good hand that is a good kernel.

Greetings, continues.
[Galaxy S 5 Original Android Development] f0xy:
Sorry pal, I just tested, I'm tired, been in a hospital waiting room all day :)
[Galaxy S 5 Original Android Development] MIKEMON:
To begin a series of perfect work, my friend
[Galaxy S 5 Original Android Development] sarvam:
Welcome Dev, we used to love your kernel on s3 a lot, especially for sound settings...:good:
[Galaxy S 5 Original Android Development] ghoster76:
A day with Preset Battery Friendly - Governor Profile: interactive - battery: Perfect
[Galaxy S 5 Original Android Development] Mrr K:
Not a kernel, but would the viper4android app provide any useful steer on the chip's capabilities? I use this app currently on my G900F (BOB7 base) and it has a very wide range of sound options, although I appreciate that the app uses a custom audio driver.
[Galaxy S 5 Original Android Development] andip71:
Thats the point.

It comes with it's own driver.

And there is no use re-implementing viper somehow in the kernel. This is just like reinventing the wheel.

I still plan, when I have some free days, to look into the original driver code of the WDC9230 a bit more, maybe I can get some additional pointers out of that.

Andi
[Galaxy S 5 Original Android Development] farid993:
Guys does permissive mode work? After i unchecked SELinux strict (Is it for change to permissive yes?) i get system process FC and phone does not boot in to system.
[Galaxy S 5 Original Android Development] andip71:
Yes, on the first (overview) tab you can force the system to go into permissive mode straight away. But this is NOT sticky.

If you want it sticky, you need to change it in the kernel startup actions in the app settings and reboot.

Andi
[Galaxy S 5 Original Android Development] joejoecindy:
Alliance 7.1 and this kernel. Everything good and I really like this kernel. 900T. Thanks and good work on kernel. If you need any testers please let me know
[Galaxy S 5 Original Android Development] farid993:
Thanks Andi. After i set it to permissive i got system FC and it did not boot. So i wiped cache and dalvik now after reboot i get too many FCs on gapps :( . And now as you said because of reboot it is not in permissive mode yes? :D So i have FCs and nothing :D
[Galaxy S 5 Original Android Development] andip71:
Not much I can say... never tried to use the kernel in permissive mode.

All runs fine with SELinux set to enforced.

I will look into that once I have Samsung stock installed again.

Andi
[Galaxy S 5 Original Android Development] farid993:
I wish i could give you log but all things is wired! I loosed all of my data also. Now i understand why gapps giving FCs because all system apps came back to default version so as Play services. I am going to wipe phone :D
[Galaxy S 5 Original Android Development] andip71:
Just restore your nandroid backup back?

I am sure you have done one :)

If not... well... what should I say then.

Andi
[Galaxy S 5 Original Android Development] ghoster76:
I knew about changing permissive mode on start-up but I think you should set default mode is permissive ;). Some people like to install Viper4Android to improve sound quality, but they might have difficulties if kernel revert to enforcing after reboot unless they checked changing permissive mode on start-up :good:
[Galaxy S 5 Original Android Development] ghoster76:
Or he could be the Sung's guy, he might have the key. Just joking :p
[Galaxy S 5 Original Android Development] andip71:
Hi all,

if all goes well (and testing does not uncover anything bigger), expect a new beta for tomorrow:

- 3 new governors (pegasusq, lionheart, nightmare)

- Notification LED control

Cheers

Andi
[Galaxy S 5 Original Android Development] Many40:
Great. I'm looking forward for pegasusq implementation. I used it as my "daily-use" governor on my previous phone (s2).

Btw I don't want to be annoying but it would be super if you have a look at my issue as well (then the kernel would be really perfect ;))

Best regards
[Galaxy S 5 Original Android Development] andip71:
Of course. This is one of the next points to look at.

Andi
[Galaxy S 5 Original Android Development] festr:
about the notification LED control how does it work? Any reading for this subject? I thought that the LED can be already controlled by some API
[Galaxy S 5 Original Android Development] andip71:
Exactly as on the s3. Fading effect + speed + intensity can be configured.

Info on Boeffla homepage in the documentation.

Andi
[Galaxy S 5 Original Android Development] ghoster76:
I guess it'll be just like S3, my girl friend still owns an i9300 running your kernel. :laugh:
[Galaxy S 5 Original Android Development] festr:
About the led fading etc - does it use wakelock when changing color fade etc?
[Galaxy S 5 Original Android Development] andip71:
No. It programs the LED driver accordingly with a slope operation. No wakelook, no battery drain at all.

Andi
[Galaxy S 5 Original Android Development] festr:
I used led notification app which was changing colors based on criteria but it had to do wakelock and change led every time it need3d to change. With this kernel support ia there any app which can benefit from this kernel implementation?
[Galaxy S 5 Original Android Development] andip71:
Don't overestimate it.

The LED control is not intended to compete with specialised apps at all. It just adds some basic tweaking which applies to every app using the LED, but it just cares about fading/blinking, speed and intensity. Not more, no colours etc.

It is a 100% blueprint of the S3 LED control which is there for years already.

Andi
[Galaxy S 5 Original Android Development] festr:
Yes that how I understand to it. But for example, every app on s5 when you want to create blink or even fade the app (besides listening on notifications and actually programs the LED) has to program every single blink / color change which has to use wakelocks. And my question is if there is already some recommended application which can benefit from this kernel implementation which means that if I want fading the application will send some command only once to program the LED and the fading will do kernel driver (so no wakelocks). I expect wakelock only when there is new notification which would change color for example but not service the LED for blinkink / fading.
[Galaxy S 5 Original Android Development] vd69:
Nice kernel. But after every boot phone doesn't react for a minute or so . After this minute everything works like it should. Also you can't see the boot animation. I am on Alliance 8.

ΝΟΥΣ
[Galaxy S 5 Original Android Development] andip71:
The kernel driver will program the the LED driver in hardware, so there will be no wakelocks used for fading. The LED driver circuit supports fading in hardware.

Every app will leverage from that, once fading is activated it is available automatically for every app.

No wakelocks.

Andi
[Galaxy S 5 Original Android Development] ghoster76:
This is causing by your rom not the kernel, try another roms with Boeffla-Kernel before realizing that is the last reason you can find.
[Galaxy S 5 Original Android Development] andip71:
Not having this here...

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

I'm on Alliance 8 as well - no stability issues at all (even with some battery saving tweaks already implemented).

A few hints:

- did you flash ktoonsez kernel (available from Alliance aroma installer) before Boeffla? If yes, flash Boeffla cleaner script and then boeffla kernel again and see if it helps;

- try Boeffla kernel on a clean Alliance 8 rom installation (on stock kernel).

It works perfect for me so I don't see any significant reason to not work well on your phone. :)

Edit1: Btw, you didn't mention on what s5 version you are on - you are on g900f, aren't you?
[Galaxy S 5 Original Android Development] vd69:
Yes I have g900f

ΝΟΥΣ
[Galaxy S 5 Original Android Development] Many40:
So please try what I suggested. If you decide to reinstall your rom, don't forget to backup everything.

Good luck.

Edit1: Another question - I assume you are on default Boeffla settings or you changed something in boeffla config app?
[Galaxy S 5 Original Android Development] andip71:
FYI - I am currently trying to replicate your report on the tunables...

Will keep you posted.

Update1: On Cm12.1 kernel, I cannot replicate it. I chose Battery Extreme (as you did), made a reboot and checked without doing anything else in between. hispeed_freq on 3000000 - as it should.

But think I have to restore Sammy rom now and check again...

Andi
[Galaxy S 5 Original Android Development] vd69:
No I didn't thanks.

ΝΟΥΣ
[Galaxy S 5 Original Android Development] andip71:
Ok, on Samsung I can confirm this.

It is like follows:

- the kernel loads and applies the correct value to the tunable

- then some other process (I suspect rom) overwrites it again with the default

This is really odd, and I need to find a way to prevent that. Humm, not nice. And again something Sammy-specific, as it does not happen on CM.

So, I will release the kernels still today, but this glitch will be still in as I require some good thinking work on how to prevent that best.

Thanks

Andi
[Galaxy S 5 Original Android Development] andip71:
[MENTION=2174044]Many40[/MENTION]: Ok, I have a solution very soon. So I will hold back the release of a new Samsung kernel now in order to sneak that in.

Question is: Would you be happy to pre-test a test version before I release it? To confirm the issue is fixed?

Thanks

Andi
[Galaxy S 5 Original Android Development] Many40:
Awesome!!! Yes, of course - I'm ready ...
[Galaxy S 5 Original Android Development] andip71:
Ok, I am not yet 100%. But will get in touch with you once I have the version for you.

It will require also a new app, which I still have to do. The kernel is already done.

Cheers

Andi
[Galaxy S 5 Original Android Development] andip71:
[MENTION=2174044]Many40[/MENTION]: You have PM :D

Andi
[Galaxy S 5 Original Android Development] Many40:
[MENTION=947981]Lord Boeffla[/MENTION], You have a PM :D
[Galaxy S 5 Original Android Development] andip71:
New beta

Hi all,

new beta version available for you.

Version 1.1-beta2

13.05.2015

Added 3 new governors: pegasusq, lionheart and nightmare

Added notification LED control (read up on homepage how it works)

Fixed interactive governor profiles not correctly applied on boot (overwritten by Samsung Rom again) - please update to Boeffla-Config 2.1.79 to have that working correctly as well

Enjoy

Andi
[Galaxy S 5 Original Android Development] enebro77:
Installed and tested. So far, so good, so smooth, ... :)

Just one point. I dont care that much in Antutu and similar benchmarkings, but I have notice a 'low' rating in 2D and 3D ... any clue ?

Cheers
[Galaxy S 5 Original Android Development] festr:
I have tested the LED and I barely see the LED. Even though I set brightness to 130 (maximum in the app) the LED is too low. On value 20 I even do not see it.
[Galaxy S 5 Original Android Development] andip71:
Most probably because my GPU min Frequency is lowered from 200 MHz Stock to 27 MHz. You can however configure it back to 200 MHz.

This should make Antutu better. But yes, as you already said... Antutu say everything and nothing :)

Andi
[Galaxy S 5 Original Android Development] andip71:
Set it to zero then. This triggers the stock intensity.

And yes, the more you increase the LED speed, the lower in intensity gets the LED. That was already that way on the S3.

Andi
[Galaxy S 5 Original Android Development] festr:
Setting it to 0 fixed the issue I can now see it well. Fading or blinking has the same intensity even if I set it to very quick
[Galaxy S 5 Original Android Development] andip71:
Yeah, you need to play a bit to find your optimal settings. That is quite normal.

Andi
[Galaxy S 5 Original Android Development] enebro77:
Su número de confirmación es el: 36Y785861T226511A.

Thanks for your work, Sir.

Cheers
[Galaxy S 5 Original Android Development] festr:
are other colors then blue supposed to work? I used to use lightflow app to allow showing other then blue for notifications and I'm not able to get it to work anymore. Only blue blinks/fades.
[Galaxy S 5 Original Android Development] DirkStorck:
Thanks LED control is working fine ??
[Galaxy S 5 Original Android Development] andip71:
I am not using light flow. But for me, colour of the LED determined by app triggering it, does work fine.

Not sure if lightflow is compatible. I remember that topic was already around on the S3, but cannot remember if lightflow was found to be compatible or not.

If you have a very specific configuration, you might want to switch to standard settings and try again:

Fading = off

Speed = 1

Brightness = 40

If it does not help, then you need to decide to go back on previous kernel version (but then you will be stuck on it).

Andi
[Galaxy S 5 Original Android Development] festr:
omg it started to work. I just rebooted the phone and it magically started to work.

edit: all colors with fading is working with lightflow
[Galaxy S 5 Original Android Development] andip71:
Yeah, sometimes a restart works wonders ;)

Andi
[Galaxy S 5 Original Android Development] festr:
well ok a little bit out of topic, but does anyone know about application (the lightflow cannot do this) which if there is notification for lets say gmail + missed call the application allows to set color for this combination? I have green gmail and red missed call and if both are notified I would like to see orange :D
[Galaxy S 5 Original Android Development] andip71:
Maybe tasker, but for sure that would be quite a complex task to setup.

But maybe it could be done there.

Andi
[Galaxy S 5 Original Android Development] ICECOLDKILLAH:
why cant lightflow do this? you could also try light manager
[Galaxy S 5 Original Android Development] DirkStorck:
Or look at LED Blinker in playstore. No problems at all with it.