yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] fonfox:
Andi this is amazing

You are so quick

Thanks a lot

---------- Post added at 04:07 PM ---------- Previous post was at 03:32 PM ----------

Can anyboby tell me the new original LMK settings. I've override it with old default profile.

Confirm todays temasek V5.0 runs fine with beta 21.
[Galaxy S III Android Development] andip71:
Press reset button at LMK settings, will give you the default values back.

(it restores the values that are set during boot before Boeffla applies the new settings)

Andi
[Galaxy S III Android Development] fonfox:
I'm not shure if i press default in LMK 16,32,.. appears.

At first time i have install temasek Rom , stock kernel and look with kernel audiutor

LMK 42,...

(dirty flashed , boeffla-kernel-data is from earlyer Vers.)

thougt LMK was changed.

At twice i install beta 20

and see the same LMK i use'd with older boeffla Versions.
[Galaxy S III Android Development] andip71:
LMK is in the ramdisk.

Of course my kernel comes with other settings than Temasek.

So, you need to install Temasek stock kernel again to find out his LMK values, no other way.

Andi
[Galaxy S III Android Development] The_Voice_70:
beta 21 works really fine on today`s nightly. Thanks for Update on holy Sunday, Andi ;)
[Galaxy S III Android Development] Logan:
Andi do you think back to n00t + boeffla kernel

Or any 4.4.4 touchwiz based on it worths using today? Cm11 and cm13 always have problems with videos even when i flashed camera patch for cm11
[Galaxy S III Android Development] andip71:
I am not fully clear about your question.

If you want me to recommend something stable, I have said CM11.

If this is also not working for you for some reasons, I would say latest Samsung 4.3 stock.

And if that all does not work, I can just repeat what I keep on saying for a year now:

Go for a more up-to-date phone. The S3 is quite outdated already now.

Andi
[Galaxy S III Android Development] arifnasirshaikh:
[MENTION=947981]Lord Boeffla[/MENTION] what do you think about android N..? Cm13 is not even close to stable and Google released developer preview of Android N. I don't think s3 is no way capable of running it
[Galaxy S III Android Development] 2phazt:
Maybe I'm the only one but with beta21 and aicp 0313 and 0314 I get a heavy drain by CyanogenMod-System.

CPU use is very high - almost 1400+ the whole time the display is on and the device gets hot (what is expectable).

Maybe I should test the new rom versions first with beta20 to find out if it's kernel or rom related but maybe someone else can confirm the problems...
[Galaxy S III Android Development] andip71:
I think Android M does not run very good on the s3 anymore.

That is why I believe N would run even worse.

And it is not worth the efforts to even port it - my opinion.

Andi
[Galaxy S III Android Development] 2phazt:
I think that M is very good - maybe the best rom on the s3 I used so far.

There are still a few bugs - it has nightly status - but over all it has improved a lot.

The version of 0311 has brought a really big performance increase.
[Galaxy S III Android Development] dkionline:
Its good to use, but everytime the battery looses fast. Thats really bad.
[Galaxy S III Android Development] sunny1234590:
Every time my phone boots it optimizes one app!

This is seen after flashing Boeffla Kernel.

Is this normal?
[Galaxy S III Android Development] andip71:
Must be somehow specific to your phone.

I don't have that. Are you on official nightly or a custom rom?

Do you have init.d scripts running?

Andi
[Galaxy S III Android Development] sunny1234590:
Nope, nothing. Official CM13 nightly. However, how should I check about the init.d scripts? Though I am sure there won't be anything because all I have done is flashed CM13.0 and your kernel.
[Galaxy S III Android Development] andip71:
If you are on official cm13 nightly, then you should not have init.d scripts.

However you can look if you have something in /system/etc/init.d to be sure.

So then - no idea.

Andi
[Galaxy S III Android Development] sunny1234590:
Yeah, there is a folder. It has four files also!

So, this optimization on every boot is because of this?
[Galaxy S III Android Development] andip71:
Ok, when you have exactly 4 files, then these are the standard ones which come with CM. So they are safe.

Then it must be something else. Permission problem maybe, or an app that modifies itself all the time.

I really do not know.

If wiping dalvik cache also does not help, I think we will not solve that easily anymore.

Then all you can do is: trial and error to find the culprit app.

(or you backup all user apps with Titanium backup, deinstall them, install them via titanium again - dunno if that helps).

Andi
[Galaxy S III Android Development] arifnasirshaikh:
Same problem but 4 apps optimizes at boot.
[Galaxy S III Android Development] andip71:
At least not kernel related.

We have to accept CM13 is still a young rom where things can happen.

BTW - this happened from time to time also years ago on Sammy roms, so it is not something new or something serious.

Edit: Search for "android optimizing apps after every reboot" in Google and you will find numerous links for all sort of devices, all having this same thing.

Andi
[Galaxy S III Android Development] sunny1234590:
I basically reported this thing here because I was not facing these errors in previous versions.

I am not sure whether it's actually CM or Boeffla Kernel issue.

Anyways, thanks for the tip.
[Galaxy S III Android Development] andip71:
I see it from the other angle:

If it were a general kernel issue, we all would have it.

But this is not the case.

Especially as the android is optimizing thing is a function of the VM (ART vs. Dalvik) which is not part of the kernel at all.

Andi
[Galaxy S III Android Development] sunny1234590:
I totally agree with what you are saying. But then same settings, same apps but no issues with stock Kernel.
[Galaxy S III Android Development] andip71:
Who says you would not have that with stock kernel as well?

Install stock kernel now from latest nightly and check if it is really gone.

I bet it is exactly the same.

As you can see when you Google, it is a completely kernel unrelated topic coming up everywhere.

This has for sure more to do with leftovers in the file system, permissions etc.

At the same time I am sure, when you do a clean install it will be gone again as well.

Andi
[Galaxy S III Android Development] sunny1234590:
I have done a clean install and then only I am reporting here. Anyways, will check again with a clean flash and report back. :)
[Galaxy S III Android Development] ttocs99:
Hi ive just flashed the cm11 based kernal with cm11 rom and please may i ask if anyone is still using tat setup what stable voltages do use people use on boeffla im not overclocking just want to lower my voltage to save abit of juice
[Galaxy S III Android Development] Hawaiihemd:
Check the Boeffla Kernel Profile Sharing thread. Surely you will find something in there. But in the end you have to try what works for you. Every phone is different...
[Galaxy S III Android Development] ttocs99:
Hi thanks for your input is there any battery saving guides with boeffla kernal just want to get max battery savings as i think i need a new battery
[Galaxy S III Android Development] 2phazt:
Nobody using boeffla beta21 on aicp 0314?
[Galaxy S III Android Development] andip71:
Hi all,

quick maintenance update as CM pushed a big number of kernel patches in past 3 days.

Version 5.0-beta22

17.03.2016

Update: Updated with latest official CM kernel commits as of 17.03.16, 10am CET

Update: Ramdisk of official CM13.0 build of 17.03.16

Change: Improved compatibility to latest SuperSu versions

Enjoy

Andi
[Galaxy S III Android Development] Drollach Gûntar:
Thank you my Lord, you're so faster.

Cm13 is going to be better day by day.
[Galaxy S III Android Development] Bart11666:
Please tell me if i'm wrong, i already installed version 17.03 and to installed boeffla kernel wipe dalvik cache-flash kernel-wipe dalvic cache? Or flash everything fresh?

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] illustrious.hr:
just flash boeffla kernel, wipe the caches and reboot
[Galaxy S III Android Development] froycard:
I would like to ask something about the new release of Boeffla kernel... I have stuck with CM nightly version: 20160226 (since I have tested some new nightly on my cell and to my taste, there are still flawed and buggy, so I have kept this old nightly version from Feb 26),,,

Is it recommended in spite of having an old nightly version, to stick with the old Boeffla Kernel release or can I continue updating this kernel as being released?
[Galaxy S III Android Development] rhyzan:
Heya. Just want to say great work on the kernel. That's it.

And this will be our last tribute to the great S3. So... Yeah.

Device: GT-I9300 on CM13

This post is posted on mobile so don't expect too much. Have a nice day!
[Galaxy S III Android Development] 2phazt:
The kernel should correspond to the rom version of which it has been build.

Means old rom version should use old kernel.

And vice versa.
[Galaxy S III Android Development] xarmx:
Hey there. I'm new to this thread but I've been sticking to boeffla kernel since 4.2.2 slimrom. Last time I used the kernel beta5r17 for cm13 on resurrection remix rom r13. It worked flawlessly. The best combination so far. But after the latest update from the rom development, which is resurrection remix r22, whenever I flashed the kernel, be it beta5r17 or beta5r22, it turned out okay on the first boot. But when I go back to recovery mode and cleared the dalvik cache, the rom ended up in a bootloop. I really really love the boeffla sound engine, it makes the most out of my old faithful galaxy S3. Not having it on my phone kinda seems to be wrong on so many ways.
[Galaxy S III Android Development] andip71:
Ask RR team what they did to make their rom incompatible with official CM13. And whether they want to revert it back.

But you will not get an answer anyways.

Andi
[Galaxy S III Android Development] bykumza:
[MENTION=6537024]xarmx[/MENTION] Beta21 works good on RR v5.6.5, no bootloop and any problem, when i clear dalvik cachce.

by Tapatalk
[Galaxy S III Android Development] andip71:
Absolutely.

CM13 kernel is my last tribute to the S3.

When something new still comes up, it will be definitely without me.

There are point in life where you have to cut old things (also when they are good) and say good bye.

Andi
[Galaxy S III Android Development] arifnasirshaikh:
It means i gotta buy new phone soon....

In future whichever device i use.

I'll always install your kernel. ☺

Will see you on the other side, whichever thread that may be.
[Galaxy S III Android Development] xarmx:
Seriously? I'm gonna try and flash it now. Thanks again. Btw you flashed the kernel after flashing supersu? or before supersu?

Edit : Nope, still bootloops. Gonna stick to the old RR r13 rom with the latest boeflla kernel
[Galaxy S III Android Development] bykumza:
[MENTION=6537024]xarmx[/MENTION] look:

First I install Boeffla Kernel, next Flash SuperSu, because after flash Kernel, SU binnary is gone.

Edit: Maybe check RR r_22, but you'll have to do Full Wipe.

by Tapatalk
[Galaxy S III Android Development] xarmx:
Yep, I did that before, flashed the rom after full wipe and then flashed the kernel. It booted up just fine, every single time. But have you tried clearing the dalvik cache and cache partition AFTER the kernel has been flashed? I tried it more than ten times and it will always ended up with bootloop
[Galaxy S III Android Development] sunny1234590:
Phew! Optimizing app problem solved. It was 'Xmod' which was causing the issues. [MENTION=947981]Lord Boeffla[/MENTION]

Thanks for the tip! ;)
[Galaxy S III Android Development] andip71:
What the hell is xmod?

If you now say it is a xposed module,... I'll shoot you... [emoji23]

Andi
[Galaxy S III Android Development] nicesoni_ash:
Shoot him, shoot him.. [emoji14] [emoji14] [emoji14]
[Galaxy S III Android Development] arifnasirshaikh:
No it is not xposed module... It is use for modding games like for instance unlimited ammo on dead trigger 2.
[Galaxy S III Android Development] sunny1234590:
No! No, it's not Xposed. I ain't that stupid. It's an app used for having some advantages (basically cheating :P) in some games like Clash Of Clans, Dead Trigger, 8 Ball Pool etc.
[Galaxy S III Android Development] rhyzan:
Guys chill. Xmod is a cheat app. Almost as bad as xposed but... Meh. Not xposed.

You're safe from Andi's gun... For now LOL
[Galaxy S III Android Development] whatsgood:
"some advantages" nice way of saying CHEAT ;)
[Galaxy S III Android Development] sunny1234590:
Yeah agreed. Corrected my post already.
[Galaxy S III Android Development] andip71:
Lol. Ok. Lucky guy ☺️
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION] Hi
[Galaxy S III Android Development] Logan:
Andi everytime i g the charger the boeffla config app (latest) opens but screen hangs on white and 1 minute later it works
[Galaxy S III Android Development] andip71:
The app never opens by itself. I have not implemented anything like that.

If the app opens when you connect a charger, you need to check if you configured some automatism in another app to do this.

It would also help if you would provide the required minimum information about what rom/kernel etc you use.

Andi
[Galaxy S III Android Development] fonfox:
Andi what is your opinion about ksm

will ksm also be included in future kernel versions

or is it a placebo
[Galaxy S III Android Development] andip71:
The feature itself is quite old, already has beein introduced with 2.6.x kernels.

In all theory, it makes sense.

In Android world it is not used a lot from what I saw, and I believe there are reasons for it. Maybe the tradeoff of saved battery vs additional battery consumption is not worth it. Maybe due to the way Android is constructed with having a VM in betweek kernel and rom (Art/Dalvik) makes the feature less efficient.

To be frank: I never thought a lot about it. On the S3, with it's alway too small memory, it might make some small sense.

But still, it seems to be not something popular here.

Andi
[Galaxy S III Android Development] 2phazt:
Well since only memory and not battery and cpu power is the limiting factor of the S3 it does make sense to do almost anything that gives a bit more memory - even only in theory.
[Galaxy S III Android Development] andip71:
Then the question is, why has it not been implemented?

I still believe there is a reason.

And I even remember some devs were experimenting with it in the past. Would be interesting to find out whether they reverted it again or kept it in.

Andi
[Galaxy S III Android Development] fonfox:
In 19.03 nightlie it is included
[Galaxy S III Android Development] andip71:
You are correct. Saw it as well now.

Maintenance update will arrive soon, then it is of course in also, following CM as always.

Andi
[Galaxy S III Android Development] andip71:
CM13 maintenance update

Good morning,

here the promised maintenance update:

Version 5.0-beta23

21.03.2016

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

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

Enjoy

Andi
[Galaxy S III Android Development] 4rch0:
Thanks Lord

(Du bist und bleibst der Lord :D )
[Galaxy S III Android Development] Bart11666:
Hell-ooo! If I flash beta 23 with 19.03 version it will be ok?

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] 4rch0:
Yes!
[Galaxy S III Android Development] andip71:
I think so, no guarantees however. I never test against older roms.

Andi
[Galaxy S III Android Development] 2phazt:
Is ksm active in this build?
[Galaxy S III Android Development] Trafalgar Square:
yes
[Galaxy S III Android Development] andip71:
Sure, I follow CM in that things:

https://github.com/andip71/boeffla-kernel-cm-s3/commit/8dbb933d3bd9d6fb223290e8a9e4b612e6e91801

Andi
[Galaxy S III Android Development] 2phazt:
There a rumors that it breaks camera so it would be nice to be able to toggle it in the config.
[Galaxy S III Android Development] andip71:
Well - camera working fine here. So either I am lucky or it is not true. Or I did not catch it with my test so far.

But making that switchable is not possible. It is either compiled or not.

Maybe it could be compiled as a module, but not sure at all.

And also I will not investigate anymore, you know... the EOL tag.

Andi
[Galaxy S III Android Development] g104:
literally, camera is dead on temasek rom v5.2 & v5.3 with beta 23 but after i resetted the app on boeffla setting it work after reboot but now still not working. roll back beta 22.
[Galaxy S III Android Development] 2phazt:
Camera was dead for me too but after a reboot it magically works again^^ Hope it stays this way ?

Edit: Sometimes the camera needs to be started a few times to work again.
[Galaxy S III Android Development] g104:
yeah after restart few min it work but after certain period it stop working. rolled back 22 beta working again or install kernel adiutor >> kernel samepage merging >> disable KSM >> apply on boot >> reboot
[Galaxy S III Android Development] astankov:
Dear Lord,

Thank you for your perfect kernel that made my S3 the best device I've ever used so long. For the past two years your kernel was driving my phone no matter what software I used on it - stock , ported from Note 2 or AOSP but everything has to come to an end. Our S3 is old device these days and has started to really struggle with all those new memory hungry apps and new OS versions.

This situation started bugging me big time and I decided that I need new device. For the time spend flashing custom AOSP roms I understand that they will never be able to be a full featured alternative to the stock software. Maybe they are better in some cases but just in some in all other cases stock roms are much better for my type of use of the phone. That's why I decided not to use custom roms on my devices anymore and this fact was driving force of my decision to buy my new device - Black Galaxy S7 32 GB. This said I know that probably won't be able to use your kernel anymore which is making me sad a bit but hey S7 is a great (and expensive :) ) device that I will enjoy I hope for several years.

The time spend with my S3 and your kernel is something that I will newer forget and I hope to see you in S7 section of the forum.

Best regards!

Andrey
[Galaxy S III Android Development] andip71:
Thanks a lot for the nice words, Audrey.

Just I have some last bad news: No, we will certainly not see each other in the S7 forums.

I decided a year ago to not go for any Samsung device anymore as long as they continue to put efuses, knox, flash counters and other annoyances in their devices.

But have a great time anyways

Andi
[Galaxy S III Android Development] 2phazt:
Camera kept working for me but videoplayback in mx stopped working - so I rewerted to beta22 as well.

Now everything is fine again.

Seams that ksm at this stage is not really beneficial.
[Galaxy S III Android Development] g104:
weird my side mx player working on 22 & 23 with SW but now i flashed back 23 & disabled KSM, mx player running HW but once u switch to SW it will not supported.
[Galaxy S III Android Development] 2phazt:
Well, I didn't test with sw - hw is my default.

With beta22 hw works - with beta23 not.
[Galaxy S III Android Development] andip71:
So looks we need to revert the ksm changes, or?

Seems we learned why it is not used widely ☺

Will do an update today with ksm switch off again. Although I would expect cm officially will do that soon too.

Andi
[Galaxy S III Android Development] andip71:
Hi all.

would you agree switching off KSM again is a good idea, although in the official CM stock kernel it is still switched on?

It seems responsible for breaking camera (I could now also see that this morning), any maybe more.

So I am about to deactivate this stuff again. Any objections, comments?

Andi
[Galaxy S III Android Development] sanguinesaintly:
Temasek has already released a build with ksm disabled so it looks like the way to go.
[Galaxy S III Android Development] Darkened_Sky:
I disabled it on my temasek builds and since then people who previously had camera problems told me that now everything is working again.

So IMO it would be best to deactivate it.
[Galaxy S III Android Development] g104:
does KSM got any benefit? if got just leave it on :p, we can temp use kernel adiutor to enable/disable since u stated millions of times 'EOL'

i'm not sure KSM will be mature in future by official CM. :o

boss, just do whatever that convenient to u. ;)
[Galaxy S III Android Development] sanguinesaintly:
Will Kernel Adiutor override it if it is hardcoded into Boeffla kernel ?
[Galaxy S III Android Development] andip71:
Ok guys, this confirms what I think.

KSM is currently not a good idea, I will disable it completely again, like it was before.

I always had my doubts on it before, but breaking things is not acceptable.

So, beta24 will be out once todays nightly is out.

Andi
[Galaxy S III Android Development] g104:
nope, correct me if i'm wrong lord boeffla.
[Galaxy S III Android Development] andip71:
I don't know kernel auditor and how it exactoly tries to configure it.

I assume it disables the ksm functionality via sysfs.

But fact is: When I disable KSM in the next kernel version (as it breaks things), there is no way for any app to enable it again.

And it does not make any sense to bring something back which breaks things anyways.

Andi
[Galaxy S III Android Development] 2phazt:
Well, as long as it breaks things it should be deactivated of course.

But I think it could improve the s3 memory management if it works.

I read it could have something to do with video memory allocation that should use physical pages and not mapped ones. So if ksm could only be disabled for this cases it would be a win ?
[Galaxy S III Android Development] andip71:
I am happy to follow CM team when they achieve to implement something smarter.

But for the time being, I will remove stuff that breaks.

Andi
[Galaxy S III Android Development] sanguinesaintly:
So Adiutor is not a solution for turning it off as long as it's hardcoded on in the kernel. The view seems to be - disable it and live with the consequences, as long as the camera works - that would seem to override any unknown performance benefits.
[Galaxy S III Android Development] ste22032:
KSM will be disabled also in official CM starting from next Nightly, this is the commit: http://review.cyanogenmod.org/#/c/137568/ :)
[Galaxy S III Android Development] andip71:
Oh, this is good news.

Because it will change my plans now to:

- I will not do a kernel update today

- I will do an update tommorrow

- Users can still fall back to beta22 for the time being

This saves me some work :)

And users that want to ultimately have it (for whatever weird reasons) can still activate it again in next beta...

Thanks

Andi
[Galaxy S III Android Development] The_Voice_70:
Checked 5.0 beta23 with Nightlys 21.03 and 22.03.: Excellent Deepsleep 99%. No Drain. No Problems. Rock solid;) Thanks for Update, Andi ;)
[Galaxy S III Android Development] Maxoobidou:
FYI, KSM doesn't really break the camera, but the ability to play videos, including the camera stream. Any video, Youtube, local videos, etc.

It does also help memory management, so hopefully it will get fixed.
[Galaxy S III Android Development] Logan:
Andi i was getting logcats for some apps that crashes but while surfing i found this weird error but i dont have any type of lags or something

Beta22 21.03.2016 nightly

Maybe this can explain what happens to config app when i plug the charger?(hanging in white screen)
[Galaxy S III Android Development] andip71:
Does not mean a lot to me. Logcat is a rom log, and it is huge, so from that picture I cannot pinpoint anything.

But maybe an experienced rom dev can say more.

Andi