yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] martinzh:
Typing error .S3
[Galaxy S III Android Development] viktor92:
I try MM nightlies from time to time and that wasn't my experience. It's not "much smooth" and the memory consumption it's about the same, and both configured in the same way with same programs installed and boeffla u600. Not to mention CM 12.1 it's more stable.
[Galaxy S III Android Development] AliTajelsir:
[MENTION=947981]Lord Boeffla[/MENTION], the default pegasus governor settings were changed, and even if I tune it manually it won't stick after reboot.

Running beta 12 with 08/02 nightly.

Thanks in advance!.
[Galaxy S III Android Development] andip71:
Hi,

I think I already have the ramdisk with the changed pegasus settings included. So it should be in.

As for the settings not sticking - are you on CM13 or any other rom?

Unfortunately you did not give zero information about rom, kernel version, configuration etc., so I am unable to say more.

Andi
[Galaxy S III Android Development] yoahmad1995:
I'm on CM13 and settings revert to defaults whenever I reboot.
[Galaxy S III Android Development] andip71:
You still have not given the requested information.

I just did it myself on cm13, latest kernel. Rebooted and the tunables were sticky.

Maybe any other app conflicts and resets them, there are plenty apps that are able to do that. Sorry, but you have to search to find it.

Kernel and app are fine, as I just confirmed for myself.

Andi
[Galaxy S III Android Development] AliTajelsir:
[MENTION=947981]Lord Boeffla[/MENTION], I failed to clarify that I have the changed settings but my manual configurations won't stick on boot.

I'm on cm13 08/02 nightly with beta 12, as for my configuration I'll attach the profile's file.

Thanks again!.
[Galaxy S III Android Development] andip71:
No no, I did understand it.

And I just did exactly the same, and my manual settings were sticking fine.

So I can only assume something else is conflicting.

Andi
[Galaxy S III Android Development] AliTajelsir:
Ok. I'll investigate further.

Thanks!.
[Galaxy S III Android Development] Logan:
Lord boeffla config reset app option not working in 4.4.4 tw any idea?
[Galaxy S III Android Development] yoahmad1995:
Not tunables is my problem... My problem is the LMK values sir. :p
[Galaxy S III Android Development] andip71:
How did you do it precisely, what happened?

Ah, your screenshots were always showing governor tunables. Ok.

Then: what did you configure for lmk?

I think you should send me a debug info file for future analysis (action menu in Boeffla-Config).

Andi
[Galaxy S III Android Development] taco9:
CM13 12-2 nightly with boeffla 5.0 beta 11 and everything fine. Settings holding on reboot, zzmove std and nice battery performance. This will probably be my daily driver for a long time. Much thanks.
[Galaxy S III Android Development] AliTajelsir:
I didn't figure what was the problem exactly but increasing the boot up delay to 5 sec solved the issue and settings are sticking fine now.
[Galaxy S III Android Development] andip71:
It can be slow rom processes that overwrite it again, mods, other apps etc.

But good you found a way. Great news.

Andi
[Galaxy S III Android Development] mahe.:
Andi,

f2fs finally coming to cm13 nightly(i see lot of f2fs commits)? i remember that you have mentioned beoffla kernel will not support f2fs as it have stability issues. will that decision will stay same with cm13 also now? f2fs still have stability issues?
[Galaxy S III Android Development] NickName98:
It will stay the same because the kernel is no longer supported
[Galaxy S III Android Development] andip71:
I saw this stupid stuff already this morning.

As I follow the cm source base always, I will merge these changes in of course.

But I will not use f2fs myself, so I will not be able to provide support from my side for questions.

Wrong.

Cm13 kernel is still in maintenance mode, so changes cm does are implemented by me too.

Andi
[Galaxy S III Android Development] Gokulbalram:
(._.')

You seem a little conflicted
[Galaxy S III Android Development] andip71:
No. I just don't like f2fs, I find it not required.

But I always follow cm basis. I don't block things from going into my kernel when it is official.

Had the same already some weeks ago when cm put f2fs into the opo kernel.

Andi
[Galaxy S III Android Development] Gokulbalram:
Why though? I'm asking purely out of curiosity
[Galaxy S III Android Development] Pedro030993:
Hi friends, i have a Galaxy S4 (Sph-L720) i update to android 6 with the rom of cyanogenmod13, all things work perfect its very fast, buuut the one problem are the audios in whatsapp are very slow, anyone fix that? Thank you
[Galaxy S III Android Development] :
Wrong Thread. This is Galaxy s3 board
[Galaxy S III Android Development] Pedro030993:
Excuse me, i try with that thread, thanks
[Galaxy S III Android Development] w1nter456:
Hi, can I use it for unofficial cm11?
[Galaxy S III Android Development] andip71:
Don't know... test and let us know :)

I tested against this:

http://xdaforums.com/showthread.php?t=2524285

Andi
[Galaxy S III Android Development] ekie84:
Is this only for omni rom or all CM11?thanks

Send from my GT-I9300 using Tapatalk 2 (Temasek CM11 v1 / 3.0.64 CM)
[Galaxy S III Android Development] andip71:
ekie... see one post above. I, so far, only tested for Omni.

But give it a try if you have a CM11 running. Then we will see.

Make a nandroid first, then all is fine.

Andi
[Galaxy S III Android Development] cink40:
Not booting on temasek v2.…
[Galaxy S III Android Development] andip71:
Ok, good to know.

I have not yet decided which route to go with CM11 finally.

As the Omnirom team is quite busy, I was basing on their source code so far.

Andi
[Galaxy S III Android Development] Undgrand:
Look closer. 5h online and only 2% lost.

Its going into deep sleep pretty quick i guess it has a very long standby time :)
[Galaxy S III Android Development] Moster2:
The reason is that omni has the new mali libs and kernel sources, mainly mali related. Cm didnt push that yet, so it wont boot. I hope someone from cm will push the same commits soon
[Galaxy S III Android Development] andip71:
Allright, Moster. Then let's expect the issue will resolve itself soon :)

Andi
[Galaxy S III Android Development] Richard_10:
Hi. Would you like to share your config
[Galaxy S III Android Development] RohanAJoshi:
did you made any calls ?
[Galaxy S III Android Development] Entropy512:
CM11 or Omnirom? It's one or the other, you can't have both since CM is using older EGL blobs.

(Unless you're doing crazy hacks like what gokhanmoral did to have two different selectable Mali drivers...)
[Galaxy S III Android Development] JustArchi:
Andi, kernel for OmniROM is not, or will not be in very near future, compatible with CM. Even if it works now, it won't work in VERY near future.

Please consider building from CM sources :). Thanks.
[Galaxy S III Android Development] arj03:
This kernel looks very nice. Thanks for your hard work.

I was wondering if this has any of the binary blobs from the leaked 4.3 roms, or if this is vanilla. Also has the recent samsung 4.3 kernel helped with the drivers of the GPU compared to the default CM kernel.
[Galaxy S III Android Development] lukaaa47:
MDNIE doesnt stick after restart
[Galaxy S III Android Development] tisazalay:
Thanks for the kernel, I still think JustArchi is right (quoted him also), I can only wish the issue is not resolved by itself but by a caring hand :rolleyes:

(my hope is backed by the fact that this very beloved thread (for me and many others) is devoted to cm builds, but Omni is a welcomed plus)

Thanks, I think the same, maybe if Lord Boeffla so decides, he can have kernels for stock (done already), Omni (alpha already) and cm (pre cm11 done already)
[Galaxy S III Android Development] bornlivedie:
God forbid...

Go Omni!
[Galaxy S III Android Development] andip71:
No, definitely the kernel I built as an alpha yesterday was for Omni.

Based on Omni kernel sources.

And I would never do that kind of hacks. To be honest, the GPU stuff is not so much my priority as I am not doing gaming. So messing around in the mali area is something I anyway do not like :)

Thought it might be very close to 10.2 source, just changed initramfs. But might not be 100% true.

Well, I was very interested in seeing and trying out Omni, to be honest.

As far as I know, CM team has no S3 kernel devs anymore, so I am a bit concerned about CM11 on the S3.

If that has changed, and I have missed that info (which is not unlikely due to my professional work pressure in the past weeks), then I would be happy.

But do not want to strategically choose a "dead horse" :)

No, did not do that.

Yes, then you are using a rom which overwrites the settings again.

So check where you can configure that in your rom instead and do not use it in the app. I think I mentioned in the documentation this was only a hack for the CM10.2 releases where this was dropped.

I considered to drop that again as well, but it seems to be useful even in the Samsung kernels area. So I decided to keep it in, with all possible side effects.

Well, see above.

I want to support what has the better future - at least long term.

Andi
[Galaxy S III Android Development] ekie84:
Im sorry but where is the kernel for omni 4.4?i cant find it on the download site ...thanks
[Galaxy S III Android Development] andip71:
I do not put download links to Alpha versions on the download site, as I do not want to spread these versions alot.

The link is in this thread, just scroll up around 20 posts.

Andi
[Galaxy S III Android Development] andip71:
Well.

Ext4 works perfectly + I never had any data loss in the past 4 years with it.

So why adding an additional file system that is indeed a bit faster (but io is not the bottleneck in modern phones, even not on the s3), but you can read a lot about compatibility issues and people corrupting their data? And I am not interested at all in increased benchmark figures.

I just find it useless. My close to stock objective says, I should use what comes out of the box for Android, which every rom, kernel and recovery understands.

Andi
[Galaxy S III Android Development] Gokulbalram:
Data loss is a thing with ext4? Never knew that. The only FS that (afaik) is prone to data loss is NTFS.

It's never about the benchmarks, it's always about UX so if there's compatibility issues then I guess you could say it's not yet something fit for use.
[Galaxy S III Android Development] andip71:
No. Data loss is not a topic with ext4. I never had any.

But with f2fs there are many reports about it.

So why should I give my data to such a file system then.

And yes, I think it is not adequate.

But we should stop this topic now.

I don't like f2fs, I will not use it ever.

But I will include it as my kernel should never have less functionality than stock.

People must know what they do...

Andi
[Galaxy S III Android Development] andip71:
But the good thing I just saw...

They merged all that F2FS code in, but did not enable it (yet).

Andi
[Galaxy S III Android Development] 2phazt:
You still hope, he? ?
[Galaxy S III Android Development] andip71:
Naaaaaaaaaah, it is just so typical. Moving code and and not enabling it, saw that so many times already.

And I am not hoping, I just do not care of people that switch to f2fs and have only the slightest issue with it. I might even laught about them, like a little devil.

I have made my point so many times.

Andi
[Galaxy S III Android Development] Gokulbalram:
It's probably just an alternate like they have it for the Moto G
[Galaxy S III Android Development] Logan:
I was testing cm13 LMK in tw 4.4.4, 85 swap and 4 devices 600mb zram to avoid

Launcher crash that is known in touchwiz its still crashing but less delay so wanted to return to stock kernel settings to compare them in config settings 2.2.27 but it is not working phone not rebooting just warning messages return not settings.

I got bootloop in cm13 while updating to 12.2 nightlies so switched back to tw.

Sorry that is out of the topic
[Galaxy S III Android Development] andip71:
New CM13 kernel update

Hi all,

new update for the CM13 kernel.

Version 5.0-beta13

15.02.2016

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

Fix: Correct wrong pegasusq tunables when manually selecting standard profile

Change: Slightly more relaxed timing during startup to make settings stick better for some roms

Update: Ramdisk of official CM13.0 build of 14.02.16

Enjoy

Andi
[Galaxy S III Android Development] sunny1234590:
On latest build WiFi isn't turning ON. Anyone else?
[Galaxy S III Android Development] andip71:
Probably not, as wifi has not changed and works fine here.

At least as long as you are on latest CM13 nightly.

Flash kernel again.

Andi
[Galaxy S III Android Development] sunny1234590:
Yup, I am on the latest build. Will download again and check.
[Galaxy S III Android Development] Wasim625:
Can anbody tell me whats the best settings governor and LMK settings for CM12 for i9300 - I'm using temasek's 5.0.1 by the way with boeffla kernel for CM 12. I am using ZZmoove with zzmoove-battery. Everything's working fine but the phone lags when i connect it to WiFi (after a gap of 7-8 hours).
[Galaxy S III Android Development] :
5.0.1? Why are you using such an old rom?
[Galaxy S III Android Development] cokesucker:
Dear Lord,

question: does baseband/bootloader have any effect on your kernel? Reason i ask is because I'm running cm11 with BK 2.14. Today i flashed a TW ported rom which changed my bootloader /baseband. Then i restored my cm11 back. But was pleasantly surprised to find that it's running noticeably smoother than before. E.g. i had a stutter when manually locking the screen before and now it's gone. Sorry if this is OT or a silly question.
[Galaxy S III Android Development] andip71:
Well, honestly it should not have any influence as both is not directly kernel or rom related.

But you never know, I would just be happy and enjoy it if I were you :)

There are things, we cannot really explain, hehe.

Andi
[Galaxy S III Android Development] Wasim625:
Lol was using a 4.4.4 previously till yesterday

[emoji14]

May be I don't really flash alot. Any help regarding the post BTW?
[Galaxy S III Android Development] Maxoobidou:
I think he meant that even for Lollipop, 5.0.1 is pretty old, last Lollipop version is 5.1.1.

5.0.1 was pretty buggy too.

I've heard talks about these commits: http://review.cyanogenmod.org/#/c/132461/ and http://review.cyanogenmod.org/#/c/132628/ , and how they would greatly improve battery life. Does it looks like it will to you guys, or is it just normal bugfixing/stability/performance commits ?

Also, I updated from beta12 to beta13, and the nightlies from 08/02 to 14/02, and my S3 feels way snappier. It's actually working quite good now !

Finally, does this : http://review.cyanogenmod.org/#/c/132806/ means we're going to see beta14 soon ?
[Galaxy S III Android Development] andip71:
Hi,

regarding the mentioned changes - we will see. They are looking fine, but if they have significant impact is something we can only find out in real life.

And beta14 will come once there is a fundamental set of changes merged in (currently not one of them is merged.

And just because CM now finally switched (stupid) F2FS file system on last night, I will not come around with a beta14 yet.

Probably beginning of next week a maintenance release, or earlier when they manage to move significant changes in.

Andi
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], I got news: http://review.cyanogenmod.org/#/c/132976

EDIT: Never mind, you already know :P
[Galaxy S III Android Development] andip71:
Hi,

yeah, I know. Read the post above yours, there I mentioned it already.

Also that I am not releasing a new kernel version just due to this "nonsense" :)

It will be in the next update of my kernel.

Andi
[Galaxy S III Android Development] Maxoobidou:
Thank you for the answers.

I agree with you, I don't think F2FS calls for an update.

To be honest, I'm not against Cyanogen merging it in officially, they aren't pushing anyone to use it, it just opens more choice for the end user, but I just don't get what the fuss is all about. F2FS doesn't improve much, and actually introduce new risks. All of that to solve a problem that doesn't exist : the data partitions are all fine in ext4 (or even exFAT).
[Galaxy S III Android Development] andip71:
Exactly the point.

I am also not against CM merging it in officially. Thus I can enable and and do not have to support it myself.

And this is the reason why I will of course also take it over.

Andi
[Galaxy S III Android Development] hamza touati:
hello [MENTION=947981]Lord Boeffla[/MENTION]

in the boeffla config app in the governor tunables i can't find the ''' frequency step ''' where is it ????
[Galaxy S III Android Development] Gokulbalram:
Time to put a big, red-colored notice in the OP stating your kernel isn't responsible for an FS issues lol.

Or you can just not merge the changes
[Galaxy S III Android Development] andip71:
Dont know? Maybe you use a governor that does not have that tunable implemented.

Naaah, I will always merge CM changes the same way.

I will just ignore people whining when they lost data due to f2fs.

Andi
[Galaxy S III Android Development] Gokulbalram:
Big red scary notice it is then
[Galaxy S III Android Development] hamza touati:
iam using zzmoove governor :(
[Galaxy S III Android Development] andip71:
Yes, in zzmoove there is no tunable frequency step.

Hence, you cannot see and configure it.

Andi
[Galaxy S III Android Development] 2phazt:
What about using f2f2 only for system and cache? Do you see any risks there?
[Galaxy S III Android Development] andip71:
Sorry, asking the wrong one :)

I think f2fs makes no sense at all compared to ext4. So my answer would be no.

On system it makes zero sense, as system is a read-only file system.

Cache... well, at least in theory it makes sense, but ... :)

But the worst is: When something goes wrong, I will not give any support. Just want to say that clearly again :D

I wonder again and again what people expect from f2fs in real life? Zero is the answer. Just more risk for zero. But enough said now, we are all adults and we know what we do.

Andi
[Galaxy S III Android Development] Gokulbalram:
A placebo perhaps?
[Galaxy S III Android Development] andip71:
Nope, for sure not.

I do not dispute F2FS is able to handle higher IO.

Just my point is - in real life, why should I do it with all the issues and risks I already listed?

IO is not the limiting factor on our devices, even not on the S3.

But please, can we close this philosophic topic? I start to repeat myself, and this means I am wasting my time already :)

Andi
[Galaxy S III Android Development] rudolf4321:
Hi have a question about the charging options^^

If i usually charge with 1.8A (1800mA), and now max it out to 2A (2000mA) will it damage the battery ? I mean 200 mA isnt a that big difference but still noticable in charge time.
[Galaxy S III Android Development] andip71:
Likely.

The higher the charging rate, the more heat, the worse for your battery.

But s3 has battery which can be easily replaced, so....

Andi
[Galaxy S III Android Development] rudolf4321:
Do you use the higher charging rate :D and which one would you recommend using ? (I have the s5)

btw your kernel is by far the best even its in beta for CM13

Ups my fault just noticed this is the wrong theard :(
[Galaxy S III Android Development] andip71:
No, I don't when I am not in a rush...

But I am neither using my s3 nor my s5 for daily driver.

And you are in the wrong thread then [emoji1]

Andi
[Galaxy S III Android Development] andip71:
Kernel update

Hi all,

CM13 kernel maintenance update for you, to be up-to-date with CM's latest commits:

Version 5.0-beta14

18.02.2016

Update: Updated with latest official CM kernel commits as of 18.02.16, 9am CET

Update: Ramdisk of official CM13.0 build of 18.02.16

Enjoy

Andi
[Galaxy S III Android Development] yoahmad1995:
I'm on CM13 with adopted SD Card 64GB TwinMOS class 10

Running great on a 4-year-old phone so far but I'm having a problem with Asphalt 8 when I enter online match... The loading takes too long and when its done I find the race started already and I missed 36 seconds of the race.

Btw this never happened on Lollipop with FolderMount to mount its OBB and Data.

Otherwise, its great but I'm curious to know because I'm addicted to this game.

Thank you. :)
[Galaxy S III Android Development] andip71:
I think we have to accept, the S3 is quite old and not adequate for modern games anymore.

Just saying that without being a gamer nor at all interested in gaming :)

Andi
[Galaxy S III Android Development] yoahmad1995:
You're right but Asphalt 8 is not a modern game I even used to play it with my S2 back in the day on stock ICS in 2012 :)
[Galaxy S III Android Development] andip71:
I have absolutely no clue as you see... Never had a single game on any of my smartphones [emoji3]

Andi
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], is it normal seeing soft reboots with ZRAM on?
[Galaxy S III Android Development] konohanz:
Asphalt 8 is one of my daily games, running smooth in my device, never had an issue with games :D
[Galaxy S III Android Development] andip71:
I never had them.

But zram is just a dirty workaround for the too small ram of the s3 for today's roms / apps.

So I would not be surprised.

Andi
[Galaxy S III Android Development] yoahmad1995:
Did it take so much time loading a multiplayer race? And do you have your SD Card adopted? I have a lot of media so I had to adopt it.
[Galaxy S III Android Development] viktor92:
No, it's not normal. I use Zram since ages and never had that...
[Galaxy S III Android Development] sunny1234590:
I have it too sometimes.
[Galaxy S III Android Development] andip71:
I think I have stated enough times about memory shortage of the s3.

Cm13 is not perfect for the s3 anymore. This is a fact.

Andi
[Galaxy S III Android Development] konohanz:
Yes i had, nope all games running very smooth no problem at all with me..
[Galaxy S III Android Development] zjunior06:
Works in cm13?
[Galaxy S III Android Development] andip71:
No words... What does the thread title say?? [emoji35]
[Galaxy S III Android Development] Gokulbalram:
It says free chocolates :D
[Galaxy S III Android Development] froycard:
Thanks to Mr Boeffla for your development...

Any advice to use your kernel with, I mean, I am using the latest Android version - 6.0, from cyanogenmod (build: nightly - 20160206), and it works solid without lagging, boots and any other ailments you may find in other kernels. I tested Bliss, and it didn't work to me, as well other developments you can find on this forum. I installed the last nightly - 20160217 and it was buggy (phone didn't work), and had to revert to nightly - 20160206...

so what do you think? I need continue updating my nightly cyanogenmod version to the latest, or I stick around with a functional one till they have a snapshot version one? or do you use any custom-made one that you can download from other source?

Thanks again for your kernel...
[Galaxy S III Android Development] Maxoobidou:
Next nightly is gonna be a big one :p

Can't wait to try it !
[Galaxy S III Android Development] Gokulbalram:
Why is that?
[Galaxy S III Android Development] sanguinesaintly:
Next nightly what ? This is a kernel thread you know.
[Galaxy S III Android Development] andip71:
If you found a combination where everything works for you, you can stick to it for some times.

But after some time you should update again as well, as bugs get fixed.

Personally I cannot recommend anything for a daily driver phone, as I don't use my S3 anymore as daily driver for more than a year.

Andi