yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] JustArchi:
Nope, you're wrong. Only if the zram values are different from already applied, the swapoff and swapon kicks in, to make proper change. With default values this won't happen, and with custom ones you'd still need to do so anyway.

The thing is that AK works "on top of" the system and the previous kernel, and it doesn't "replace" them, like Boeffla for example. I prefer to inherit all the tweaks, which are already available, instead of replacing them with my own solutions. This way, Synapse with my scripts can detect the current state, and save it as "the default" state, which you can later restore with just a few clicks from the app. If I delete configure_zram, the default state for the zram will be "off", and it shouldn't be so, because ROM is basicly unusable with out of memory otherwise. Same goes for LMK and other tweaks we applied from the init.rc.

In 99.9% situations, you don't need to, and you shouldn't, modify zram values. The 0.1% is the situation when you prefer hardswap.
[Galaxy S III Android Development] FadeFx:
But then id need to configure the zram settings in configure_zram the same way i set it in synapse to prevent that, which makes zram settings in synapse obsolete imho...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
Why? It takes a little longer, but works fine.
[Galaxy S III Android Development] FadeFx:
Because it puts strain on the system for quite some time after boot and causes unneccessary lags for that time. Why not just write the settings to the configure_zram file as well from your script, this would prevent that issue completely.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
Because it's not possible. I can either disable configure_zram completely, or leave it as it is now. Why not stick with default values instead?
[Galaxy S III Android Development] cangcan:
[MENTION=5161352]JustArchi[/MENTION], what governor does your experimental kernel use? Is it pegasusq?
[Galaxy S III Android Development] JustArchi:
It is. CPU governors weren't touched yet.
[Galaxy S III Android Development] FadeFx:
You can not parse it into a textfile? I am not sure if it is even possible to go back to default so synapse doesnt configure zram at all, i would love to use the configure_zram file only...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] Mostafa Wael:
hey [MENTION=5161352]JustArchi[/MENTION] :)

looks like i will not be able to test the latest iteration :D

http://xdaforums.com/showpost.php?p=59285446&postcount=2771

i will miss your Archikernel very much

and i will be waiting for S820 devices, whether i like it or not :D

can you tell me the ETA of the first S820 device ?

sent from the old-but-gold Nokia C3-01 :cowboy:
[Galaxy S III Android Development] JustArchi:
If you clear Synapse's data and reboot, zRAM set by configure_zram will become new defaults.

No clue.
[Galaxy S III Android Development] JustArchi:
So is experimental working fine? I couldn't find any issues myself.
[Galaxy S III Android Development] FadeFx:
For me it seems to, just let me test a bit longer.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] ste22032:
Same here. Only positive feedback about it.
[Galaxy S III Android Development] FadeFx:
That zram stuff is still giving me issues, i have cleared data for synapse, rebooted and set my uv settings and other stuff again, everything ok till then. A bit later i did a change to gpu threshold and when i applied it synapse got stuck again, checking osmonitor i found out that swapoff is running and seems to apply some random changes to zram.

Edit: it looks like it did apply 200mb disksize to zram0 device, while zram1 is still on 300 as it is configured in configure_zram

Edit2: after a reboot zram was back to normal, but i reproduced it, i wanted to change gpu-up-threshold 1-2 to 80% but instead it did above changes to zram but this time both devices. I am confused...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
On the first day, Archi said "This TouchWiz is one big crap, let's fix it", and then ArchiDroid was born.

On the second day, Archi said "AD works okay, but stock kernel is outdated crap, let's fix it", and then ArchiKernel was born.

On the third day, Archi said "AD with AK works okay, but it's too slow, let's fix it", and then ArchiDroid Optimizations were born.

On the fourth day, Archi said "It's fast now, but i9300 support in CM is bad, nobody cares anymore, let's fix it", and then unofficial CM12 was born.

Today I say "It works fine, but Linaro is not enough for me anymore, let's fix it", and so... ArchiToolchain was born :cool:.
[Galaxy S III Android Development] myshakugan:
I'm having some trouble with zram too. Set 75mb to each device. For a while the phone would function normally, but after a while it starts lagging. I use my phone for usb tethering, so when I connected it to pc and went to settings to enable it, my settings would just hang there for a while, then the device self reboots. After rebooting, the synapse settings go back to default. I wanted to make sure if this issue was being caused by zram, so I kept everything unchanged and changed the zram values again and then, boom. Same issue again. So i wiped data of synapse again, and kept zram at its stock value. Now everything seems to be fine.
[Galaxy S III Android Development] FadeFx:
Hehe, going to max it out...

Btw, zram settings are applied always when changes are made in synapse, they are just not saved so they are not applied on boot. Hope you can fix it, as this is a major annoyance and nearly drives me crazy.

Edit: they are saved and get applied after boot despite i didnt touch them in synapse after clearing its data.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
Of course they're saved and applied on boot, I just checked that. Swapoff is just slow and it takes some time. And once again I repeat that script does the change only when needed.
[Galaxy S III Android Development] HaarisTheBoss:
Working without any problem.

Thanks for your efforts in the community.
[Galaxy S III Android Development] FadeFx:
But i want to use settings i can not set in synapse, i want 600mb on two disks with swappiness of 90, this has served me best until now. Id prefere not having support for zram in synapse if it works in a different way than systems zram settings.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
... How is the method used in Synapse different from system settings?

Mate, you're talking nonsense right now. You could've asked about 600 MB option, and I'd add that.
[Galaxy S III Android Development] FadeFx:
Remember, i actually have asked for that. It has just been a while ago with previous test version of the 2.0 branch.

The difference is that system configures zram on boot with the configure_zram file, while synapse starts a service on boot to execute the command. If i dont want to have swapoff running on boot i have to configure it in the file the same way i do it in synapse. In that case i would prefere to have only the configure_zram file as it is already there and works as it should.

tapatalked from lollipopped i9300

---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------

Here...

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
I repeat, for the third time. If Synapse values equal already applied values, no swapoff/reset/swapon is done, because it's not needed. And also, I repeat for the third time, that Synapse takes default values from values applied at boot time. So if you set your values in configure_zram, then install AK, no swapoff will be running because synapse values will be default values, and default values are the values applied by configure_zram.
[Galaxy S III Android Development] FadeFx:
But this is not the case, i did clear data for synapse, then rebooted but synapse still had set 200mb for both devices, so it does actually not take the values as configured in configure_zram. If you say it should do so, there is definitely something wrong, as it does not. Just give it a try and you will see that it does not.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
It is 200 MB, because 200 MB is max value, if you didn't notice yet. When I change that value, it will work.
[Galaxy S III Android Development] robert018:
[MENTION=5161352]JustArchi[/MENTION] Okay, I can't boot with ArchiKernel whatsoever, I tried 1.7.2 AOSP LP, latest test kernel with no luck, I flashed over stock kernel cm12 nighlies by [MENTION=4898097]arter97[/MENTION] and also weekly, and no luck booting up, it always boots to recovery, I don't even see boot animation.

Thank you,

Robert.
[Galaxy S III Android Development] JustArchi:
Log or didn't happen.
[Galaxy S III Android Development] robert018:
How can I take the log without booting?
[Galaxy S III Android Development] JustArchi:
http://xdaforums.com/showpost.php?p=59223306&postcount=2108
[Galaxy S III Android Development] FadeFx:
But there is still the fact that it has to be configured the same values in two places if one wants to use non-stock values, this renders the settings in synapse useless imo.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] JustArchi:
No, it has to be configured in Synapse only, unless you have OCD and you're angry that Synapse fixes initial status set by stock system.
[Galaxy S III Android Development] duttyend:
No problem so far... so good !!!

Thank you so much !!!
[Galaxy S III Android Development] JustArchi:
Another test release for biggest ArchiKernel fans.

1. Don't flash on previous line of ArchiKernels (1.X), or any custom kernel. Flash this on stock kernel [ONLY], or previous 2.0 test version (28 Feb+).

2. If you have 2.0 test version (28 Feb+) already, you should clear Synapse's data prior to flashing to avoid conflicts. You can do so through Settings -> Applications -> All -> Synapse -> Clear data

3. Half of the features are still missing.

4. Works with LP only.

5. This is a test release, expect bugs.

6. This is based on N7100 sources.

Fast changelog:

1. In comparison with latest experimental release, which has been confirmed to work fine, this release is compiled with new shiny ArchiToolchain.

2. ArchiToolchain is based on Linaro 4.9.3 2015.02 GCC, but built from source by me with some extra patches for Cortex A9 CPU with NEON. It's very similar to these toolchains. It includes latest components, and enables additional extra features, such as CLOOG support, which will benefit AK with additional optimization flags soon.

Have fun.
[Galaxy S III Android Development] FadeFx:
Not sure what OCD means, but i disagree, stock values as they are set by moster2 are 4 disks 600mb, this is not ideal as it prevents hotpluging because the disks are balanced to the 4 cores of the cpu. To retain hotpluging i prefere 2 disks 600mb which works just good, but it can not be set in synapse cause 200mb/disk is max.

However if i do changes in synapse only that are not in the config file, this means the system boots up, sets the settings from config file during init, then after boot the synapse service kicks in finding different settings than they are currently and thus starting swapoff and rebuilding zram. This causes high load on the cpu and a lagy system for several minutes because it happens in the same time when mediascanner also loads the system.

Only way to prevent this is to set the same values in the config file as it is in synapse, because synapse forces its settings to the system, no matter if i want it to or not.

I am not sure if my english is not good enough to tell you what my point is, or if you just dont want to think about that issue as it is minor.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] habylab:
Seems to work first time, but not after that. Just will not load, blank.

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] GeekyDroid:
Hmm, thank you for your explanation! :)
[Galaxy S III Android Development] Gonnelli1355:
It would be a great thing if you implement zRAM. It's very useful for our phone! Anyway, great job :)

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] marcero:
As far as I see zRAM is already running per default.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] RibozoM:
this is 2.4.6 omni version. i have no zRAM on 2.5.0
[Galaxy S III Android Development] @non4:
Testing this kernel as of tonight on CM nightlies. All seems fine apart from weird video playback/recording which I merely tested to verify the issue, I don't particularly use it

Edit: Video seems erratic for first few seconds then plays normally, its like FF or frameskip then it "calms down" and plays normally. To reproduce playback issues simply play a recording in stock gallery, pause and then play again. Is there an app for the charging interface at all?
[Galaxy S III Android Development] gieffe22:
just hope that video bugs can go away from this beauty...i plan to use it with newest miui 4.4 from datagut...but not before that video play and record is fixed,,, until this day, i remain with archiport...
[Galaxy S III Android Development] cassote:
I can say that for me the camera rebooting is the only major issue..... Video playback is fine.... Oh running omni for the record
[Galaxy S III Android Development] d1rekt0r:
[MENTION=5161352]JustArchi[/MENTION] , you think you can fix HWC with this kernel ?
[Galaxy S III Android Development] snnrkn:
Since when hwc is kernel related? Kernels are open source and if it was there, it would have been fixed ages ago.
[Galaxy S III Android Development] d1rekt0r:
I have no idea how it works, just asking
[Galaxy S III Android Development] Abo3mood:
Is it possible to make it compatible with a kernel config app, like boeffla config ie.
[Galaxy S III Android Development] aldus320:
Just tried your kernel justarchi, and wow this is blazingly fast, the screen looks good too, can you implement the sharpness tweak like on boeffla kernel?
[Galaxy S III Android Development] microcens:
+ 1
[Galaxy S III Android Development] kaninchenkatze.tt:
The Oversharp is Changed by the Kernel but you can choose in advanced settings or in display settings an other scenario or like cyanogenmod
[Galaxy S III Android Development] habylab:
I think this is the plan, in the future. For now, it is pretty well tweaked from the start.
[Galaxy S III Android Development] GeekyDroid:
I think zRAM isn't usefull at all on a 1GB RAM phone. As zRAM dicreases your performence and battery life!
[Galaxy S III Android Development] Gonnelli1355:
I don't think so. Our phone can't take more than 2 apps running together, and if they're not too big! zRAM is a must for me, I was just asking if it could be implemented in future. Thanks
[Galaxy S III Android Development] AssassinGEO:
I just tested zram off on stock ROM,and gotta say,multitasking sucks by hard. I mean,when opening skype + odnoklassniki + vk (rus apps) and twitter,they all stay in ram and can be opened without reopening,but,as soon as I start to use one app hardly,then every other app gets turned off. But why did I mention STOCK ROM? Because on AOSP,I was always turning zRam off and phone had an AMAZING multitasking. 1gb RAM was holding apps just better than with zRam ON on STOCK ROM.

But one benefit: ROM now flies without zRam and not thinking of going to AOSP now,so,I think I will leave it disabled.

Kernel is good,though. With this one screen looks as good as on stock ROM.
[Galaxy S III Android Development] szotaa:
Android HW Composer is an abstract 2D composer library that can help to offload GPU resource for screen composition. Its a part of Hardware Abstraction Layer, so according to the graph its a rom, not kernel, issue.
[Galaxy S III Android Development] JustArchi:
Now you said that correctly ;).

And BTW, in old implementation it was 600 MB / number of zram devices, so you had 2x 300 MB. I raised maximum zRAM size to 300 MB to allow you your old setup.

I'm wondering if I can add override switch for zram, not sure if Synapse allows for such thing. As for now it must stay as it is.
[Galaxy S III Android Development] FadeFx:
While an override switch would be cool, i still think it would be better to leave zram settings out of synapse. In old implementation it was ok, because there was no zram in stock system, but now it is enough if we can configure it through the file.

tapatalked from lollipopped i9300
[Galaxy S III Android Development] ramabg:
I just installed the latest experiment version over 1.7.2 kernel on weekly 7. Stweaks was remain with full option. Is the stweaks settings legit or just mock up ?
[Galaxy S III Android Development] FadeFx:
You didnt even read the release notes, did you?

tapatalked from lollipopped i9300
[Galaxy S III Android Development] ramabg:
It did not mention that the new kernel has full option/ feature
[Galaxy S III Android Development] JustArchi:
Now read first point of your quote.
[Galaxy S III Android Development] JustArchi:
Nope. User should not edit system scripts in order to achieve customization he wants.
[Galaxy S III Android Development] JustArchi:
Next release will be boomy :p.
[Galaxy S III Android Development] vinodr5371@xdaroms.co.in:
Where is latest test kernel for lollipop give me link,can I use with crdroid?

---------- Post added at 03:25 AM ---------- Previous post was at 03:19 AM ----------

Can I Use test kernel on crdroid rom? ??
[Galaxy S III Android Development] eatsleep:
Deleted
[Galaxy S III Android Development] EyeOfMySharingan:
JustArchi, Can I flash ArchiKernel.zip on samsung stock recovery? or do i need to flash it on a custom recovery like philztouch cwm recovery?

Im running Samsung 4.3 XXUGOA2 both on stock kernel and recovery.. Thank in advance.!
[Galaxy S III Android Development] vinodr5371@xdaroms.co.in:
Only work with 5.0 not to 4.3 u have to flash lollipop ROM,u need custom recovery...
[Galaxy S III Android Development] eatsleep:
You should be running stock kernel with any custom recovery, just flash ArchiKernel_V1.7.2-SAMSUNG.zip from the download page and you should be fine.

This kernel is compatible with almost all usable android versions 4.3-5.0.2, you just need the proper version over the stock kernel
[Galaxy S III Android Development] EP21:
The test builds are lolipop only, read a few pages back, archi posted it himself.
[Galaxy S III Android Development] robert018:
[MENTION=5161352]JustArchi[/MENTION] here's the log with the latest test kernel 8/3

https://docs.google.com/file/d/0Bz03n2RgZSSEamZicGZMOTVyakU/edit?usp=docslist_api

Robert.
[Galaxy S III Android Development] JustArchi:
Looks good.

No clue then, it works for me.
[Galaxy S III Android Development] robert018:
Is the log before reboot is the same after the reboot?

Robert.
[Galaxy S III Android Development] JustArchi:
It's install log.
[Galaxy S III Android Development] robert018:
Ohh, ok. :)

Robert.
[Galaxy S III Android Development] D00ky:
[MENTION=5161352]JustArchi[/MENTION] This is definitely the next big thing for our S3. But as I am on AD 1.x I can only observe this testing phase. That is why I and probably others on AD 1.x would really like to know if you will keep this project LP exclusive right until the stable/fully functioning version or we will get some treat in the meantime? I presume that keeping it LP only it saves time and speeds up the development. So at least I support this decision. Keep up the good work.

One more question related to stock samsung JB kernel. Can you confirm that stock kernel ZRAM configuration is 300mb on 1 device with swappiness set to 60?
[Galaxy S III Android Development] JustArchi:
There is dedicated Sammy governor on i9300, so stock settings don't matter that much anyway.

Also, as for now I do not plan test releases on Sammy. Maybe later.
[Galaxy S III Android Development] RoelD92:
which recovery did you use to flash the kernel?

If it was TWRP, doesn't there also need to be a code [1.000000 i believe] in that code indicating succes?

Did you already try redownloading the kernel? it might be a bad download.
[Galaxy S III Android Development] robert018:
I'm using TWRP, I tried tried AK v 1.7.2 and all test kernels, all with the same result. I will try CWM recovery and report again, [MENTION=5161352]JustArchi[/MENTION] , which recovery do you use?

Robert.
[Galaxy S III Android Development] JustArchi:
Latest TWRP (2.8.5.0?).
[Galaxy S III Android Development] robert018:
Okay this is very weird as I'm using TWRP 2.8.5.0 (latest) !

Robert.
[Galaxy S III Android Development] RoelD92:
i've added my log of the latest experimental flash. as you can see, it gives me a succes code [1.0], which it does not for you. strange

I am using 2.8.4.0. Not the latest, but 2.8.5.0 was a small update.
[Galaxy S III Android Development] robert018:
I have no idea why is that.

Robert.
[Galaxy S III Android Development] D00ky:
Can you explain what do you mean by dedicated sammy governor? I only know about cpu governor so this connection to zram puzzles me :)

The thing is that I flashed all stock latest AD 1.x (including kernel) two weeks ago and it gives me pretty good results especially memory management and I would like to use the same settings when I flash AK. Another new observation for me is that with this stock kernel CoolTool always shows 3 online cores when screen on and doing nothing. Is this normal behaviour for PegasusQ? When I am on custom kernels PegasusQ usually won't give me good results but now it does.

One more thing. There are quite a few users that correlates number of zram devices with cpu cores. Correct me if I am wrong but using 4 zram devices won't necessarily plug-in all 4 cpu cores.
[Galaxy S III Android Development] JustArchi:
No, when you work on zram device, there is exactly one kernel thread that can run on one CPU doing the task. With 4 zram devices, you can have up to 4 threads, which can run on 4 CPUs if needed.

As for zram governor, read it in AK help
[Galaxy S III Android Development] D00ky:
:eek: I didn't know that. So after turning off AK's zram it completely shuts down zram or it switches to sammy's zram? Or it is impossible to use sammy's zram solution with AK? Sorry to bother you so much :)
[Galaxy S III Android Development] JustArchi:
Sammy's zram works on sammy's ROMs only, and it works regardless of AK - the flag I mentioned is a compile flag and it's set by me, not by you.
[Galaxy S III Android Development] D00ky:
So if I have AD 1.7.18 and AK 1.7.2-samsung there is always sammy's zram governor enabled and turning on and off zram through AK has no effect?
[Galaxy S III Android Development] JustArchi:
It has effect, but zram governor is there all the time and it decides what to swap, instead of kernel.
[Galaxy S III Android Development] D00ky:
So only changing swappiness has no effect, ok. Thank you for clarification.
[Galaxy S III Android Development] bangdes:
[MENTION=5161352]JustArchi[/MENTION] : Are new version still compatible with 4.3 aosp?
[Galaxy S III Android Development] JustArchi:
No clue, not tested. Most likely yes with some little changes to config.
[Galaxy S III Android Development] St3ve32:
If you mean the new test versions of AK 2.0 than no. At this moment Archi supports lollipop only. From what I understood the final version will be compatible with older android versions again. So you might just wait :)
[Galaxy S III Android Development] JustArchi:
I just compiled latest AD from sources (10th March today), AK still works flawlessly, as it's supposed to thanks to my own anykernel method.

Sorry mate, it works for me, can't help you.
[Galaxy S III Android Development] robert018:
Thank you anyway, I'll try some different things and report back :)

Robert.
[Galaxy S III Android Development] Mostafa Wael:
it is really hurting me that i can't test the latest test version with ArchiToolchain :crying:
[Galaxy S III Android Development] FadeFx:
Latest test version seems to run great (except of maybe the zram limitations ;)...) no freezes or sod yet and quite smooth as well.

tapatalked from lollipopped i9300