yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] ggrey:
Hi all,

I had 5.0-beta7 and Boeffla Config V2 App for my s3 running CM 13, and Z-Ram was not enabled in the kernel and in the app in beta7. Then I flashed beta8 kernel, but no update for the Boeffla Config V2 App was released. I learned that Z-Ram was enabled again in the beta8 version by default, but when I opened the config app, Z-Ram was not enabled by default. So, I want to ask, if I do not enable the Z-Ram in the config app, would it be enabled by default, because in the changelog of the kernel it states that Z-Ram is enabled again by default?

Or if hadn't installed the config app at all, would it be enabled again because Z-Ram is enabled in beta8 as default. So, which one is dominant, the config app or flashing the kernel? Because I expected that the default values of the config app would change according to the new default values of the beta8 kernel (like enabling the Z-Ram).

Thanks [MENTION=947981]Lord Boeffla[/MENTION] for the hard work
[Galaxy S III Android Development] Flummi.FFM:
It is not enabled by itself because the App loads the [default] profile at Boot.

And in the default profile it is turned off......

In this case you have to enable it manually. Or it will be enabled automatically if you make clean flash or clean the APP data of the boeffla config app
[Galaxy S III Android Development] andip71:
It was already explained, but just to confirm:

When you start with a fresh installation, or reset all your kernel settings to default by flashing the reset script in recovery or resetting everything in the app (app menu, maintenance), then you will get the default zram applied after next start.

In your case, it was assumed you want to keep zram off, hence nothing was changed (would be bad if a new kernel would change your settings without asking or letting you know) [emoji1]

So enable it yourself, 260 mb with one device. Done.

Or... Reset all settings like described above.

Andi
[Galaxy S III Android Development] Logan:
Cm13 today's nightlies is here :D ill test it
[Galaxy S III Android Development] arminbih:
Is the new camera included sorry for off topic
[Galaxy S III Android Development] Logan:
The new camera made my day :)
[Galaxy S III Android Development] Vix_Sk:
how the zram work? i have it disabled since beta7 and i don't have any problem of ram or lag.. if i active zram like said in this topic by andi..will be a major battery drain..o the battery will be the same?
[Galaxy S III Android Development] lukaaa477:
Why more than 800mb zram not recommended?
[Galaxy S III Android Development] Maxoobidou:
Guys, the last 10 pages are about zram. Just go back a bit and most of your questions will be answered.

Andi already keeps on repeating himself, please at least search a bit.

To answer the questions:

The purpose of zRam is to use a part of the phone that is reserved for compression as RAM. This way the phone has more RAM. As new android versions (5+) don't work well with 1Go RAM, this is very useful. The big issue being that because this space is compressed, putting stuff in that (z)RAM uses lots of CPU power (to compress and decompress).

Basically, if everything is working well without zRam, you're better without.

If your phone is slow, or you're experiencing app crashes, use zRam.

Having too much zRam isn't really useful, as it won't be filled. You can monitor your zRam usage in the Boeffla app.

If you set a higher value of swappiness (default is 80), the phone will have a tendancy to use zRam more. Which means you should increase the size of zRam you're using (default is 256Mb). And that CPU load will increase. Only do that if you're still experiencing app crashes under heavy load with the default zRam config.

As the zRam is compressed and CPU heavy, the more you use it, the more battery it drains. We're not talking huge battery drain though, just a small amount. It's the usual Performance vs Battery tradeoff.

Hope that helped, and people stop asking the same questions over and over.

PS: about number of zram devices, no one really knows if it helps, or if it changes anything from what I gathered. Experiment yourself.

PS2: If you want to change the zRam config, you need to disable it first.
[Galaxy S III Android Development] viktor92:
Sorry but what are "snapshot releases" and why they are so different to nightlies ?

I've downloaded it for curiosity and in the blink of an eye was deleted from the site...
[Galaxy S III Android Development] andip71:
It is always a bit different, don't ask me why. CM could probably tell you. At least it was in the past whenever I tried it.

I decided to officially only support nightlies. Still it would work 99,9%.

Because the s3 has only 1gb ram, so you cannot have more than physical ram.

And some ram should be reserved to system too.

Andi
[Galaxy S III Android Development] Logan:
Andi i got a question you only update the kernel when there is new functions or fixes by cm?

So from 10 nightlies until today's nightlies almost same kernel built?
[Galaxy S III Android Development] andip71:
Yes, my S3 kernels are development-wise end of life. So I stopped adding features around 6-9 months ago. What I provide now are maintenance updates (without new features) and ports of the existing functionality to newer CM versions when they are officially supported.

Well, the 10.x kernels had less functionalities still, but since CM11 the functionality was not extended alot anymore. So the CM13 kernel does not have more in than the CM11 one, this is true.

Andi
[Galaxy S III Android Development] The_Voice_70:
beta8 works great. Thanks for your great work, Andi ;)
[Galaxy S III Android Development] andip71:
Thanks a bunch.

You can expect beta9 still today. There was a small revert in the kernel repo last night, which I will reflect too.

Andi
[Galaxy S III Android Development] The_Voice_70:
Hey yo. Great;) Better than "Dschungelcamp" ..... mööp;)))

By the way:

CM11 last snapshot with 2.13 is very fast;)
[Galaxy S III Android Development] 200:
Beta8 works fine on my i9300 with cm nightly (cm-13.0-20160115-NIGHTLY-i9300) and supersu 2.66.
[Galaxy S III Android Development] andip71:
Beta9 will come out in a few hours, and even updated stable releases again for cm11. Hopefully this comes finally to an end now.

Andi
[Galaxy S III Android Development] Llun:
[MENTION=947981]Lord Boeffla[/MENTION]: Just to let you know that i used your kernel in my i9300 with Android 4.3 and i am using your beta 8 in CM 13. Great work. Thank you and keep up the good work.

EDIT: Waiting for beta 9...
[Galaxy S III Android Development] andip71:
Kernel updates...

Ladies and Gentlemen,

late evening in Germany, and due to the crappy TV programme, kernel updates for

CM11 (NG and normal version) - hopefully the really really final version after the snapshot release which is hopefully the last CM11 release ever :)

CM13

Here we go:

CM11 (NG and normal) -- Version 2.14 stable - Final

16.01.2016

Fix: Fixed improper file permissions in ramdisk (improve stability)

Updated ramdisk to version of cm-11-20160115-SNAPSHOT-XNH0E0O00N

CM13 -- Version 5.0-beta9

16.01.2016

Update: Updated with latest official CM kernel commits as of 16.01.16, 4pm CET

Update: Ramdisk of official CM13.0 build of 16.01.16

Enjoy

Andi
[Galaxy S III Android Development] tokict:
Can't believe. You provide update to cm 11 kernel. (You just say, you wont, yesterday)

Very surprising !!!?

Thanks Andi,
[Galaxy S III Android Development] viktor92:
Ha ha ha, your are tired of CM11, you don't want to see it again !!! :laugh: :laugh:
[Galaxy S III Android Development] 200:
Just updated to Beta9 and latest nightly (cm-13.0-20160116-NIGHTLY-i9300) = works smooth. Super stuff, Andi! :good:
[Galaxy S III Android Development] myhrazayn:
TRIM support?

Hello, I'm on the beta8 of the Boeffla kernel for CM13 and I noticed that the kernel does not have the fstrim command supported. Forgive me if I get this wrong, and I was wondering if you could add in fstrim support sometime soon. :D
[Galaxy S III Android Development] andip71:
Well, sometimes even an old chap like me changes his minds :)

Andi
[Galaxy S III Android Development] andip71:
In Boeffla-config:

Action button -> Storage... -> Filesystem trim

What are you missing? Mmmmmh...

Andi
[Galaxy S III Android Development] myhrazayn:
Wow I..did not notice that..thanks...God I'm an idiot,

One more question though; is this automatic on the charger or do I have to manually do this when it's needed?
[Galaxy S III Android Development] andip71:
Has nothing to do with the charger.

All roms starting with KitKat have auto trim functionality included, so in theory you do not need to execute it ever manually.

I still do it manually from time to time, it does not hurt.

Andi
[Galaxy S III Android Development] myhrazayn:
Thank you man, great work as always :)
[Galaxy S III Android Development] azazello22:
I'm noticing CPU stuck at 1400 on Cm 12.1 build 31.

It is a bit strange, since it seems it started only today, and I didn't do anything different than the past few days.
[Galaxy S III Android Development] andip71:
You should use cm11 or cm13.

Cm12.x can have all sort of issues, it never was official.

But something keeps your cpu up. Either a process needing it (check with tools like system monitor), or one of the bugs floating around.

I guess you already checked all settings and also rebooted your device. Also resetting the settings to default would be an option for you.

Although I am sure it must be an app, maybe one where you received an update lately. This would at least explain why it just started.

Good luck

Andi
[Galaxy S III Android Development] azazello22:
Well, just like it always happen, the thing is gone after a reboot.

I checked everything and nothing seemed to be the culprit, but I surely missed something.

I know, the only (silly) reason I don't move to cm13 is broken Netflix, and well..cm11..in Italy we say "I want more pepper in my life" :D
[Galaxy S III Android Development] zerocoolriddler:
Netflix works fine for me on CM13. What's broken?
[Galaxy S III Android Development] azazello22:
Don't you have green/pink lines across the screen and wrong colours during the streaming?
[Galaxy S III Android Development] DodgerTheRunner:
Hi,

any idea why I got a reboot this night?

Phone was not in use, just charging.

This happened now the 4th or 5th time.

I'm on cm13 and beta9.

Low memory doesn't seem to be the reason this time :)

Dodger
[Galaxy S III Android Development] Flummi.FFM:
That seems to be an interesting New issue....

I had the same one time yesterday night.....
[Galaxy S III Android Development] andip71:
Looking at your log, I would say low memory (in fact out of memory) is indeed the issue. Even mentioned at the very beginning of the log.

What is your zRam configuration? Just out of curiosity...

And when more people have that now, maybe a memory leak has been introduced in latest nightly.

Andi
[Galaxy S III Android Development] DodgerTheRunner:
4 devices, 100MB. Swappiness 85

Actually 7 MB compressed, 23 MB uncompressed per device.

Is there a chance to find out which app causes the low memory?

As I said, it was just charging...

Dodger
[Galaxy S III Android Development] andip71:
Change zRam to 260 MB on one device, leave default swappiness of 80. Just for a test.

In retrospective there is no way anymore to find out why you ran out of memory.

I want to say it again: S3 small memory of only one GB will cause more and more issues. I know nobody wants to hear that, and I understand it, but this is the pure truth. So expect issues on memory in future as well.

Andi
[Galaxy S III Android Development] goldbeard:
I have to say that after using these LMK values, i never had a reboot or hard freeze

http://xdaforums.com/showpost.php?p=64774624&postcount=8706
[Galaxy S III Android Development] 2phazt:
Adjust your profile on the netflix site to medium quality instead of auto.
[Galaxy S III Android Development] Logan:
Everything works well no reboots bugs etc and using zram 4 devices 600mb

4 hours ost everything perfect andi you are the best :D
[Galaxy S III Android Development] Borkse:
I can recommend Greenify + Amplify + Power Nap. Yes, it sounds like too much work, but my S3 is really smooth with this combination and one has about 400-500 MB free ram available.
[Galaxy S III Android Development] Francesco0301:
Can u explain me your boeffla settings? (CPU/GPU/ nd misc.. etc..) Thanks!!
[Galaxy S III Android Development] Logan:
Normal kernel settings just 4 devices 600mb ram and for better battery using dark theme and wallpaper (s3 AMOLED screen) and greenify(donation package+xposed features)+cm13 nfc normal settings is on turn it off, and location scanning using wifi turn it off.

Privacy guard google play services turn off keep awake and start at boot

Turn off keep awake for heavy apps like facebook etc.

I got backlight at 1sec and in boeffla settings turn off the backlight in screen touch.
[Galaxy S III Android Development] FadeFx:
Id suggest using only two devices, the idea to use several devices is to spread the paging load to several cpu cores, having 4 devices may keep cores from going offline, causing more battery use. Also i think there is not so much difference in performance from 2 to 4 devices.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] Kord:
Hi [MENTION=947981]Lord Boeffla[/MENTION]

Any chance to implement Adaptive LMK in your kernel for S3? I know that you are no longer supporting our device, but can you consider this? The last hope for S3 :D

Regards, qrashers.
[Galaxy S III Android Development] AliTajelsir:
See this post

http://xdaforums.com/showpost.php?p=64760540&postcount=8698
[Galaxy S III Android Development] Kord:
Oh, I must missed this, sorry for spam then.

Also thanks for quick respond :)
[Galaxy S III Android Development] andip71:
I see, you know the answer already.

But really guys: S3 is end of development from my side. There will not be new functions coming in anymore. Ever.

Thanks for respecting that

Andi
[Galaxy S III Android Development] Flummi.FFM:
Just try this:

Lmk 16/32/64/128/192/256

It could improve your device experience a lot ;)
[Galaxy S III Android Development] andip71:
Anyone else already tried these LMK settings? Feedback?

I also use it now for some verification and so far I do like it.

Because, I could make it default in the kernel then...

Andi
[Galaxy S III Android Development] Flummi.FFM:
Sorry (As always) i forgot to mention a little bit more background (because i am writing in several Forums)

In the official cm13 forum for s3 someone told us these lmk values that he got from the moto e forum.

Moto e has also 1gb of RAM and works fine.

So i am testing these values 16/32/64/128/192/256 for 2 weeks now with a zram of 400 and a swappiness of 85.....

I have to say that i had before massive problems with big apps like need for speed no limits......

Now the reboots and lags because of out of memory are totally gone for me.

Of course it is not fast as modern phones but i will not give up my s3 until it breaks :D
[Galaxy S III Android Development] tokict:
Didn't yet.

But, after i know you already tried it. I will definitely do it.

Hope it works well too (with me)
[Galaxy S III Android Development] marcero:
Slightly adapted them, works flawlessly for me.

EDIT: Picture was not attached due some reason... see next post.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] marcero:
Steps of 32MB

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] mahe.:
This is [MENTION=2446031]FadeFx[/MENTION] lmk taken from cm13 thread,

http://xdaforums.com/showpost.php?p=64899119&postcount=2398
[Galaxy S III Android Development] FadeFx:
Probably a bit too agressive on foreground apps, you wouldnt want your browser to close for low memory while browsing, when there is 64mb of free ram. Check out tge settings linked below, they work perfect for me after experimenting for more than a month. Also i suggest to use 380mb zram with 2 devices swappiness 80 or even 85

Gesendet von meinem GT-I9300 mit Tapatalk

---------- Post added at 08:36 AM ---------- Previous post was at 08:31 AM ----------

Andi, its not necessary to go that high on high values, but probably a bit higher on second. I think the oom reboots happen when a process is pulled from zram into normal ram and it has not enough space to expand.

With your settings i still had problems with resource hungry apps like maps navigation and such, now they do work as intended...

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] marcero:
not really the same values...

The foreground app is so aggressive to prevent any oom soft reboot. In case the foreground app kills itself, which had never happened for me up to now, I know I have to reboot the phone to prevent oom soft reboots.

At least this is the idea behind.

I prefer to know, when I have to reboot rather than wait until it happens accidentially with potential data corruption.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] 2phazt:
I use 32,48,80,128,192,288 since a week or so and never had a lag or soft reboot till then.

I know that this are high numbers but I prefer to have as much space as possible to have always enough space to start a big app. Since I use a lot of different apps it's better then to have a full cache with some of them.
[Galaxy S III Android Development] arminbih:
Using it 10 days lord not a single problem, and phone is blazingly fast, always min 230 mb free mem. And on normal use 300 free [emoji4]
[Galaxy S III Android Development] viktor92:
I used it for some days and seems to work fine. Even I tried the first 3 values a little bigger.

Now testing FadeFx values and also seems to work fine...

ps.: on LP, still waiting a more stable MM version.

ps.2: I never had soft reboots with any configuration, running LP or MM
[Galaxy S III Android Development] Andreas21:
I have tried this now for over a week and it works very well :)

Phone feels more snappy with these values.

Sent fra min GT-I9300 via Tapatalk
[Galaxy S III Android Development] nkirk:
Actually the trick is in the empty apps. I leave it at 300 mbs. Others at relatively low values. By doing that zram will not try to compress empty apps unnecessarily and waste CPU resources and introduce lagginess. Downside is that virtually no apps will be in cache for faster loading. But it doesn't really make much of a difference as important system apps are anyway white listed.

Also for users who like to see lot of free ram available can raise it to 400mbs for satisfaction :D
[Galaxy S III Android Development] FadeFx:
I dont think its neccessary to have it that high, test my suggested values to compare and you will see that there are no lags at all. The actual trick is the jump from foreground apps to visible apps, foreground obviously needs to be as low as possible, while visible apps need to be killed if the free ram falls below a value where it is hard to open a new app or decompress one from zram. Currently i am testing how low i can go with empty apps and content provider without causing lag.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] andip71:
CM13 kernel update

Heho folks,

CM13 kernel update for you.

Version 5.0-beta10

21.01.2016

Change: Default zRam size increased to 400 MB

Change: Default LMK settings are now 16/32/64/128/192/256

Update: Updated with latest official CM kernel commits as of 21.01.16, 4pm CET

Update: Ramdisk of official CM13.0 build of 21.01.16

Enjoy

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

Above lmk settings are only for cm13? i am on cm12.1 , So It is ok to change above values in cm12.1,?
[Galaxy S III Android Development] andip71:
They are for the CM13 kernel.

You can change them on the CM12.1 kernel too, yes. And give it a try (and report... :D )

Andi
[Galaxy S III Android Development] dantemetaphor:
I have been using these values for a while now, and I have no more memory related lags and freezes, also have set zram to 400mb 1 device and swappiness at 80, I can confirm that these values works surprisingly well I can now use facebook and chrome among other apps, unlike with stock which kept freezing my device.

[Edit] didn't notice you already put those values in the latest build, [emoji4] I'm happier now.
[Galaxy S III Android Development] FadeFx:
I guess (actually i did never play with lmk on lollipop) the reason for spontanous reboots has been the same back then, so most likely these settings may help there as well. Nosy to hear how it works out for him...

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] rlon23:
Kernel Panic

Hi, I just had a hard reboot with the beta9 kernel, I am using the same LMK values posted before.

Here is the kernel message.
[Galaxy S III Android Development] arifnasirshaikh:
Deleted
[Galaxy S III Android Development] andip71:
Memory error, not much more to see.

Andi
[Galaxy S III Android Development] FadeFx:
But tgats not the typical oom error, right?

Kernel panic - not syncing: Fatal exception

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] andip71:
No, it is a fault during memory access what I saw quickly.

But honestly I don't analyse cm13 issues very deeply as it is known to not be 100% stable yet...

Andi
[Galaxy S III Android Development] mahe.:
Tested for some hours. With the new lmk few lags gone away that is good sign. But the issue with new values i think it is too aggressive with background process compare to old default values in my option (cm12.1). i have started google play app update and started reading news stand. But i could see google play app is killed few times between the complete app upgrade.
[Galaxy S III Android Development] FadeFx:
What exact values do you test?

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] The_Voice_70:
5.0 beta10:

Great Work. Nothings seems to kill this old machine. Run and run and run ;) Thanks, Andi ;)
[Galaxy S III Android Development] mahe.:
Andi recommended values: 16/32/64/128/192/256
[Galaxy S III Android Development] Flummi.FFM:
May i ask what did you exactly at the Moment when the reboot occured

I am not an expert in analyzing lastkmsg

But for me it looks like you did play a game or something else which was GPU intensive like playing a Video?

I have to say that i have sometimes reboots due to overheating.......

Next time when i play NFS no limits long enough to get a reboot i will look for you if my lastkmsg is similar
[Galaxy S III Android Development] FadeFx:
Give also a test to 16/64/96/128/176/192

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] mahe.:
will give a try now and report may be after 2 days
[Galaxy S III Android Development] rlon23:
Actually I was playing Pocket Mortys, but the phone wasn't very hot, or probably I got used to it.

If overheating was the case then this is the first time.
[Galaxy S III Android Development] viktor92:
Despite I'm on CM 12.1 (again, after a short CM 13 21/1 test) I'm trying LMK values suggested for CM 13 and they run pretty well

ps.: I never had sudden reboots...
[Galaxy S III Android Development] Flummi.FFM:
If you get a reboot next time while playing please check your boeffla app directly after reboot.

If the shown temp is 60 degree or more then it is for sure because of overheating.....

After all these intensive LMK discussions we shouldnt forget that reboots are not automatically because of low memory .....
[Galaxy S III Android Development] Dejvid50:
Will try,Fade what governor,gov.profile and zRam do you recommend ?.
[Galaxy S III Android Development] FadeFx:
I use the stock governor as is and 400mb zram with 85 swappiness.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] abol_fa:
What's the cause of io?

I have disabled zram completely but when i switch apps or visit webpages that have many ads i get my io stuck at maximum.

The device hangs or becomes really slow.

Doesn't IO indicate that something is being written or read from the disk?
[Galaxy S III Android Development] FadeFx:
How do you monitor io? With cooltool? If yes, how does your ram?

Gesendet von meinem GT-I9300 mit Tapatalk