yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] Danhack000:
No there isn't, but you can always mod the media_paths.xml file to gain mic and any other volume possible for your device.
[Galaxy S 5 Original Android Development] grigaraz:
Is there any support for fixing TTL on your kernel?
[Galaxy S 5 Original Android Development] andip71:
Hi all,

maintenance update for LineageOS 14.1 kernel is out.

Version

4.0-beta28

31.05.2017

Update: Updated with latest official LineageOS kernel commits as of 31.05.17, 08.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] txordi:
Yiah
[Galaxy S 5 Original Android Development] andip71:
No. This is afaik not possible, see also FAQ on www.boeffla.de for explanation.

If someone meanwhile found a kernel-based way, nice. But too late, S5 kernel is not in active development anymore, only maintenance.

See roadmap on www.boeffla.de.

Can you elaborate a bit more please?

Andi
[Galaxy S 5 Original Android Development] grigaraz:
TTL

The fact is that in Russia (and not only) many operators are withdrawing money (~ 1$ 12 hour) for trying to distribute the Internet from the phone via wi-fi to other devices,

The operator learns about the distribution of the Internet, because of the changed TTL (by default, the Android value TTL 64) with the connected TTL device changes to a value of 63, and the operator immediately charges the payment . on some android devices there is support for fixing TTL at the kernel level, on some .. the module xt_HL.ko is compiled

After that TTL can be fixed with the help of ip tables. And no matter how many devices are connected to the distributor, the TTL value of the exciter is 64

Sorry for my english Thanks.

P.S. On one Russian site, the enthusiast added the xt_HL module to your kernel for G900F stock http://4pda.ru/forum/index.php?showtopic=622076&view=findpost&p=58647828
[Galaxy S 5 Original Android Development] andip71:
Well, this functionality (module) is controlled by CONFIG_NETFILTER_XT_MATCH_HL setting in the defconfig.

In my kernel, this setting is set to Y already. This means, the functionality this module provides is already compiled directly into the kernel.

Without doing any more investigation from my side on that topic, this information may help you already?

Andi
[Galaxy S 5 Original Android Development] grigaraz:
What do I need to do to make this team iptables -t mangle -A POSTROUTING -j TTL --ttl-set 64 work ?

Terminal says : No chain/target/match by that name.
[Galaxy S 5 Original Android Development] andip71:
Maybe someone knows in this thread.

I don't know, never even tried to use iptables on an Android environment myself. Sorry.

Andi
[Galaxy S 5 Original Android Development] grigaraz:
Whatever it is, thank you so much for the best kernel!!!
[Galaxy S 5 Original Android Development] andip71:
By the way, what when you remove the "-ttl-set 64" from the statement? Does it then work?

This appears to me like something else is not known to the command. Also not sure whether the standard iptables command on Android knows all those parameters or whether you would need a custom iptables command. Just one more idea.

But as said - never used it myself. Had no use case for it.

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

maintenance update for LineageOS 14.1 Boeffla kernel is out:

Version

4.0-beta29

07.06.2017

Update: Updated with latest official LineageOS kernel commits as of 07.06.17, 15.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] msprenger:
Hi [MENTION=220904]andi[/MENTION],

thank you very much for your great kernel..running it eher since on all my Roms..its perfectly stable and without any issues ...by the way is beta 29 stable enough to become stable Version??

LG msprenger
[Galaxy S 5 Original Android Development] andip71:
Yes, it would fully stable.

Maybe soon I make it a stable release. It's more and more time.

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

finally my LineageOS 14.1 kernel is released as a stable release.

Further patches will go into a new version.

Version 4.0 stable

15.06.2017

Exactly same version as latest beta29

Enjoy

Andi
[Galaxy S 5 Original Android Development] abdouhh:
hello help

plz can u port lolilop or C12.1 CM13. to galaxy s5 zoom i tired find but i dont have any one to port it plz help me this divece have a good proccessor 6 proc and have 2 gb RAM and memory 8 gb but it havn't a cm12 or 13 or 14 and update it stop it at 4.4.2

thxxxx alot if u help

:crying::crying::crying::crying::crying::crying:
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Hey guys, know this is a little off topic but I just got a S7 Edge G935F from a friend that is having a bloody problem flashing TWRP and Lineage because of the ****ing FRP lock...he has completely forgotten the last synced account to log in and I know the phone isn't stolen because he just included all the packages and documents to proof its his.

Anyone of you know how to get rid of that lock?
[Galaxy S 5 Original Android Development] KazuDante:
[MENTION=947981]Lord Boeffla[/MENTION]

I wanted to ask if its possible for the app to receive a edit in regards to the voltage control , instead of increments of -25 that it could be in -5 or even better ones when shifted to custom , since not all frequencies can accept the full 100 or more , that way we could really dial in the lowest voltage for each frequency on each device and avoid lock-ups due to a specific frequency not getting its needed voltage.
[Galaxy S 5 Original Android Development] andip71:
Please read FAQ on www.boeffla.de. I can only develop for devices I personally own.

And in general I dumped Samsung for any new devices as it is not a pleasure anymore to develop for Sammy.

Well, it is not in my plans. But I believe you can do already what you want:

Click on the voltage itself (it is a button), there you can enter the voltage you want manually even in +/- 1mV steps.

You just cannot use the sliders for it, as this would be too fine grained for the sliders. But you should be able to configure any specific voltage manually already.

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

already new beta out, after code updates on official LineageOS sources:

Version

4.1-beta1

21.06.2017

Update: Updated with latest official LineageOS kernel commits as of 21.06.17, 14.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
Just wanted to thank [MENTION=947981]Lord Boeffla[/MENTION] for convincing me to ditch Xposed and move forward. Your recent kernel makes all the difference in LOS14.1.
[Galaxy S 5 Original Android Development] andip71:
Hi all

next LineageOS 14.1 Boeffla kernel update is out:

Version

4.1-beta2

28.06.2017

Update: Updated with latest official LineageOS kernel commits as of 28.06.17, 08.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] j1gga84:
Can anybody tell me on which linux version the latest boeffla kernel is based?

thanks and regards
[Galaxy S 5 Original Android Development] andip71:
3.4.107

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
Is there a setting within Boeffla-Config that will automatically set my SELinux to Permissive at boot? I have The SELinux Toggler installed, but for some reason it won't set permissive at boot. Will BC do this for me with a setting?
[Galaxy S 5 Original Android Development] andip71:
Yes, there is a checkbox on the overview screen (first page basically) in Boeffla-Config.

Just uncheck the SELinux checkbox and it will be applied during every start.

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
I do that and restart, but it's checked again after reboot and SELinux is still Enforcing. I'm using MagiskSU root, would that have anything to do with it? I doubt it since I was having the same issue with SuperSU last week...
[Galaxy S 5 Original Android Development] andip71:
During start, are you getting the animated Boeffla-config icon in the notification bar, that indicates your settings are being applied?

If you have this animated icon and in the end a notification after start, your settings were correctly applied, then I need to investigate.

For this, please send me the log files from folder /boeffla-kernel-data to support@boeffla.de.

But will not look into that today anymore (but tomorrow), I call it a day now.

Andi
[Galaxy S 5 Original Android Development] andip71:
Just tried it on my S5 now on LineageOS 14.1, yesterdays nightly + LineageOS internal root.

Result: Working for me.

I have no idea whether Magisk could be blocking that, I personally think this should not be the case.

Maybe you have other apps installed that can toggle the selinux status after Boeffla-Config did it? Who knows.. maybe you should uninstall all such apps (like the toggler you said).

As said, when you send me the logs I can check whether boeffla-config would try to switch it off or not for some reason.

Thanks

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
I don't notice the bc icon at the top. I uninstalled the toggler, and went through all the steps in the troubleshooting page. Nothing worked so far. I deleted the log, rebooted, and it recreated, so I'll attach here. I don't think I have other apps that affect startup at all.http://cloud.tapatalk.com/s/59552ff891344/bc.log
[Galaxy S 5 Original Android Development] andip71:
Please also provide boeffla-kernel.log from same folder.

Thanks.
[Galaxy S 5 Original Android Development] ldeveraux:
Sorry! http://cloud.tapatalk.com/s/59553145575f5/boeffla-kernel.log
[Galaxy S 5 Original Android Development] andip71:
Looking good. After start the selinux status is permissive, see log part attached.

Hmmm. Running out of ideas now.

Especially as it works like it should on my phone.

What if you uncheck the selinux box in Boeffla-Config, close the app and start it again? Is it then still unchecked?

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
If I uncheck it and reopen, it stays unchecked and my system info says Permissive. If I check it again and reopen, it stays checked and says Enforcing. Very strange. I have UMS mode unchecked, and Doze active checked, do those matter? Would it help to reinstall the Boeffla-config?

Also, now that I uninstalled the toggler, it's strange that the bc app changes to permissive at boot, but something else changed it back.
[Galaxy S 5 Original Android Development] 10goto10:
Could it be Magisk Hide? Because passing CTS requires SELinux to be set to enforcing.
[Galaxy S 5 Original Android Development] andip71:
That is a good point... I also suspect some magic in Magisk causes it.

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
Ah! I do have Magiskhide enabled to play SMR. I didn't realize Magisk required Enforcing SELinux anyway. But I'm not even sure what a permissive kernel buys me anyway, so I'm not sweating it. Thanks for the explanation both!
[Galaxy S 5 Original Android Development] andip71:
In short: A permissive kernel removes a security feature of Android. It gives apps (root apps) much more power to change settings and configurations. This also means, this power can be misused to inject trojans, viruses etc.

So in general it is absolutely adviced to keep selinux on enforcing, to have these security feature enabled.

Why the switch is in? Well, some apps or system-related stuff sometimes requires a kernel in permissive mode (in the past there were things like Viper4Android and some other mods that required it... not sure if that is still the case as I dont use that myself).

Andi
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Guys one question, I recently bought a battery replacement for my Galaxy S5 but it is much larger, rated at 7000 mAh instead of the default 2800 mAh battery.

I'm wondering if I need to edit the system somehow so it detects the correct capacity to ensure the right battery life percent is shown and properly fully charged. Is that needed or does the hardware detect those kind of things on its own?
[Galaxy S 5 Original Android Development] andip71:
AFAIK you do not need to change something.

The battery level (during charging and discharging) is determined by the battery voltage. So it should automagically work :)

Andi
[Galaxy S 5 Original Android Development] :
What battery did you get if you don't mind me asking? I'm in need of a new battery for the S5
[Galaxy S 5 Original Android Development] Ragnar Eldur:
https://m.aliexpress.com/s/item/1892615100.html?spm=a2g0n.search-cache.0.0.3d2c41caY05NT5
[Galaxy S 5 Original Android Development] :
Thank you very much! I hope the experience is good with this extended battery. :)
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Indeed is, included was another back to for the much larger battery as 7000 mAh is quite the upgrade from the standard 2800 mAh. The back is even of higher quality, compared to the flimsy thin one that was before. The only downside for some is that this makes the phone thicker but for me it's actually better because it give better grip to reduce the risk of dropping the phone. Also now the lense doesn't stick out of the back like before so it's less to scratch.
[Galaxy S 5 Original Android Development] snikerfreak:
And can you please share some experiences about this battery? I'm think about buying one becuase the stock battery is just small for me. (plus flashing Boeffla kernel gives better battery life, so might be a good idea to get one)
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Had no problems so far, lasts longer and charges quickly with my 2.4 amp charger. Like new back also more.
[Galaxy S 5 Original Android Development] andip71:
Hi all,

new beta kernel out for you, which is particularly meant to be used with todays expected LineageOS nightly.

Version

4.1-beta3

12.07.2017

Update: Updated with latest official LineageOS kernel commits as of 11.07.17, 18.00 CET

Change: improve zzmoove stability by disabling thermal support (credits to ZaneZam)

New: Kernel configuration and compiler flags changed to switch off kernel size optimization (in favor of speed)

Update: Improved device detection in installer script

Andi
[Galaxy S 5 Original Android Development] fbs:
This is the kind of thing I've always suspected to make things slower: blindling turning on "optimizations"

Kernel code is kinda "already optimized".. if the compiler tries to do much more, it will shot its foot

Maybe that's why I always felt custom kernels slower than vanilla ones.. (just complained about it some days ago.. did you see btw? lol)
[Galaxy S 5 Original Android Development] andip71:
I always compile my kernels with exactly the same compiler (toolchain) version, the same switches and optimizations as the vendors do for their stock kernels.

However, this time I decided to do a slight change in favor of speed to remove the kernel size optimization.

Kernel is getting slightly bigger by that, but the compiler does not try to find similar code blocks anymore to jump into but it does inline a bit more. Which should lead to some less "jump-back-work" and therefore be even faster. Not measurable though, but this is a good thing to do.

Other devices have switched off the size optimization already a while ago in their stock kernels.

And yeah, I disagree on custom kernels being slower or significantly faster than stock kernels. Based on theory this cannot happen.

Andi
[Galaxy S 5 Original Android Development] fbs:
??? Then why did you remove "slim" and "intellimm" governors? They were part of your kernel and they were slowering down everything! Then, in practice, boeffla was slower than stock, on those days.

There's a lot of "under the hood" options you can tune that can affect positively or negatively the performance. Even on GCC itself, there are hundreds of compiling options that can affect speed. So, of course you can have faster and slower Kernels.

For instance, I'm seeing a "trend" of tunning "vm.swappiness" to 100 in most recent Kernels. Reading the source code of the Linux kernel, this will make swapping very aggressive, putting on a ZRAM (which needs a lot of CPU power to compress) parts of apps CODE, instead of only getting rid of file caching. This is absurd, this will slow things down and use a lot of battery! Even on our 2GB device, ZRAM is enabled by default and tunned to be highly used.
[Galaxy S 5 Original Android Development] andip71:
slim and intellimm did not make the kernel slower, they pushed frequencies a bit up for all governors - this caused slightly increased battery consumption.

In general, custom kernels are not slower than stock, it should be rather the other way round.

My comment was however more regarding compiler options.

And I am not commenting the swappiness thing, these are the kind of "magic tweaks" many tend to put in, which have lots of side effects. Would never do that in my kernels. Close to stock, my main objective still.

Andi
[Galaxy S 5 Original Android Development] 10goto10:
With the recent updates to zzmove stability I decided to try out zzmove.

It seems that zzmove native hotplugging rarely offlines cores, keeping an average of 3 cores active on idle. Switching to 'zzmove two cores min' did improve things somewhat, but still overly aggressive IMO compared to default hotplug.

I know there are latency penalties with on/offlining cores, as cache, registers, etc has to be taken care of, but performance is only marginally better (placebo?)

My question is, is it okay to use 'default' hotplug (mp_decision?) with zzmove? My goal is to improve battery life (actually, replicate the LOS efficiency performance settings.) Thanks.
[Galaxy S 5 Original Android Development] andip71:
It is okay to use mp_decision hotplugging with zzmoove, indeed.

But I guess the zzmoove "master" [MENTION=3279788]ZaneZam[/MENTION] can give much better answers to your doubts.

Thanks

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

maintenance update for the LineageOS 14.1 Boeffla kernel:

Version

4.1-beta4

19.07.2017

Update: Updated with latest official LineageOS kernel commits as of 19.07.17, 08.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] 10goto10:
Just to report, that using zzmoove battery yank profile + native zzmoove hotplugging results in nearly 0%/hr battery drain! The battery graph is ruler-flat. :)

No stabililty issues too. (I'm running with 1729MHz max CPU speed.)

So it definitely seems to work better than interactive + mp_decision!
[Galaxy S 5 Original Android Development] Balrog86:
Touch boost frequency

Hi, I made some research on finding the most battery "efficient" clock Speeds on my Galaxy S5 G500F.

I'm using the last lineageos rom and boeffla kernel&donation app.

Of cause I don't want a laggy device, but I wanna test abit with lower clock speeds.

My Problem is: It doesn't matter what cpu govenor I choose (as long as my max cpu freq is above or equal 1574MhZ) it ends up my cpufreq is jumping to 1574MhZ, each time I touch my display. I want to try a lower, more energy efficient value for "touch boost".

This was one of the reasons I went for Boeffla kernel & donation app - but I can't find the setting or switch inside the app, changing my "touch input" frequency.

Please tell me, how to access that setting.
[Galaxy S 5 Original Android Development] SuperSandro2000:
Fyi The beta4 fixes the camera reboot issue at least for me.
[Galaxy S 5 Original Android Development] der-seemann:
sound (mic) control

Is there any way to edit the mic level? As mine is way too low, the phone is not usable...

For my s4 a got stweaks, that worked really well and easy... But not for this kernel
[Galaxy S 5 Original Android Development] andip71:
It is not there anymore.

You can see it in the change log:

http://kernel.boeffla.de/sgs5/boeffla-kernel-cm/cm14.0/changelog.htm

LineageOS team removed all boost functions around 13.12.2016 already. Hence you cannot configure it anymore as it is gone.

I was not happy they removed it, but I had to follow this to not create weird side effects in the end.

I am not aware of any kernel on the S5 with working mic level control, as we do not seem to have the chance to control it.

If you find a kernel that has it implemented, I might look into although this kernel is end-of-life and not in active development anymore.

Maybe you still can tweak something on rom side, I remember (I think) there were some mixer.xml files or similar, which allowed some tweaking on rom level at least.

Andi
[Galaxy S 5 Original Android Development] Balrog86:
My cpu keeps ramping up

But there must be a reason for my frequency's ramping up to 1574MhZ, each time I touch/scroll my display.

I didn't find the change you mentioned on github, but I found two parameters, that might be helpful:

/sys/module/cpu_boost/parameters/input_boost_freq
/sys/module/cpu_boost/parameters/input_boost_ms

---------- Post added at 03:54 PM ---------- Previous post was at 03:23 PM ----------

I had the same issue. It seems also be related to input boost.

Using hotplug profile "Optimized" along with zzmoove caused two freezes within 10 minutes on my device - so I guess zzmoove governor needs it's own hotplug profile in order to run stable.

If you're pro user, you can fix the 3 core always active issue by changing the tunable default setting

inputboost_typingbooster_cores 3

to 1 or 0.

btw: Thanks alot my lord, your kernel and app is awesome: Keep going :)

I was able undervolting my G900F to -100mV! Voltages 300MhZ-883MhZ even further! (300MhZ@ -200mV)!!!

Never had such a "cool" phone ever... it's about -15°C (need further testing)
[Galaxy S 5 Original Android Development] andip71:
The commit I was referring to is: 641a06ae99046c9c99e364fb72b941cfbde182de

But I just saw, they disabled LOTS of stuff but not cpu_boost (which is input boost).

Will look into it, maybe I can re-enable it again.

EDIT: Ok, I can bring the control back in theory. But it will not make any change because the boost to 1574 MHz is something mpdecision does. So you will not be able to remove this mpdecision based "boost".

Andi
[Galaxy S 5 Original Android Development] Balrog86:
Correct me if I'm wrong, please, but isn't mpdecision the same as hotplug profile "default"?

As I'm using the default zzmoove hotplug profile (it's running stable so far), shouldn't it disable the mpdecision "boost"?

Thanks for your time & work.

EDIT: It'd be also cool having a features like 3c toolbox has:

- Auto-Trim option for startup

- "Optimize Databases" & at startup (whatever this means)

- "Optimize app startup" (whatever this means)

It'd fit very well into your config app I think.
[Galaxy S 5 Original Android Development] andip71:
You are only partially right.

mpdecision is still loaded and doing its boosting thing, even when you use zzmoove native hotplugging.

You would need to completely unload mpdecision by killing it hard. This is possible of course, but I would not recommend it as it also covers overheating protection. I am sure you do not want to lose this feature. Having mpdecision boosting up to 1574 is something they have done to improve smoothness, on the other side it also does not really consume significant battery.

So in short: You can experiment with it, but I would not recommend killing mpdecision to just get rid of something that doesnt make a lot of difference while losing safety things like overheat protection...

U decide of course :)

Andi
[Galaxy S 5 Original Android Development] Balrog86:
Thanks for your detailed reply.

Of course I do not want to loose overheating protection! :)

I was about to ask here anyways: What does your changelog entity

mean? Is my phone able to overheat if I'm using zzmoove?

I'd just like having an option defining the boost frequency, as I made some deep research on my "battery efficient" clock rates for my Galaxy S5

Setting the boost frequency to 1190400 or (if this will cause lags) 1497600 would be a much better solution for me.

ps.: Please also review the last edit on my last post.

pss: I am NOT a robot@google #hatecaptcha