yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] red.hat:
Re: [Kernel][23/03] Perseus

What tips are shared, and results will vary depending on the device. No two individual devices respond the same way. As no two devices are manufactured the same way, a device tweaked one way may get 17 hours while another may get 21. On that note here is what you can try out.

My Battery Saving Tips.

CPU: set frequency to 200-1200 or 1100, and UV by 100( this is tricky, if your system freezes or reboots change to 75).

GPU min 108-350 or 54-266( this might respond well to you) UV GPU for the above steps as 800, 825, 875, 925 ( if too low it will get hot and certain programs won't respond well)

CPU scaling: sampling freq 5000, freq of response 200. Freq step 40

CPU hot plugging: cpu up rate 10, down rate 20. Hot plug conditional (500, 300), (500,300), 500,1000), 400. Run queue (200,200), (300,300), (400,400).

You can also try the app greenify on pay store. It hibernates apps that might drain your battery. This helps prevent some wake locks that might keep your phone up.

Please try this out if you want. This is just for my phone and may or may not work for everyone. You report your findings.
[Galaxy S III Original Android Development] Steve_max:
No. Look at the Linux sources. The IO scheduler is attached to the devices, not to the system. The modules are loaded or unloaded depending on whether they're used or not. When something requests the kernel for a read/write to device X, the kernel sends it to device X's scheduler to work its magic. If other programs request reads/writes to device Y, the kernel sends them to device Y's scheduler. Each device's scheduler will have its own separate queue, no matter if it's the same scheduler logic or a different one. There is no "changing from one scheduler to another", all enabled I/O schedulers are loaded at the same time and work completely independently.

The CPU scheduler is a completely different beast. It selects which threads will be run at each moment of time. That is a CENTRAL scheduler, attached to the system itself, not a modular scheduler attached to a single core or processor. This is why you can't use two different CPU schedulers at the same time: there is no room for two schedulers. There's usually no reason to use anything but CFS.
[Galaxy S III Original Android Development] mattiadj:
R: [Kernel][23/03] Perseus

I think I can do a simple cmw mod of all this :)

Also why u have choose that high swap and zram value? I think 1.6 total is not useful IMHO

From universe with my gs3
[Galaxy S III Original Android Development] nfsmw_gr:
Don't know how this works for you,it always says device or resource busy for me.

I am a long user of scripts and script manager so i don't think i've done anything wrong.

Also checked with zram status app and saw the size was indeed 650mb but zram was not in use.
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][23/03] Perseus

I'm happy with 33. Audio, as good but with bugs. So I'm just going to wait for a fix or whatever is needed to improve 34.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][23/03] Perseus

Type free in the terminal emulator and see zram is working

Let smanager show device or resource busy it doesn't matter Ur work is done ...

For example open a script run as root it will show device or resource busy but Ur zram status will change it will change to whatever script u choose

The error doesn't matter it i is working

I have tried every script once again it is saying that device or resource busy every time

Edit Wait let me check again

Edit 2 final: yes it is working 100 percent confirmed

Every script is going to say device or resource busy but is still going to work ignore this message

To prove it

I used NY script to provide me Zram and for me too it was saying this only device or resource busy but ibsoit of saying this zram is working

See the screenshot for increasing usage of zram while abuse the phone

Also note at this time there is no swap I an using as no sd card is there in my phone while taking thus screenshot......

Thus means the value displayed in screenshot is not aram+swap it is only zram as swap is 0

---------- Post added at 06:17 PM ---------- Previous post was at 05:46 PM ----------

Also another way how not to receive the error device or resource busy is turn off Ur phone remove Ur sd card then boot Ur phone without sd card then run the script now most probably the error will not be there

---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------

No 1.6 total is never useful I did it previously right now I am on 650 mb zram 512b swap which according to me is good

But I think device is more smooth on 500 mb zram 512 mb swap I didn't do it cause I am a multitaskaholic and want more zram cos of more multitasking even if it means lags rarely
[Galaxy S III Original Android Development] nm8:
please do, that will make it easier for ageing noobs like myself...
[Galaxy S III Original Android Development] mattiadj:
R: [Kernel][23/03] Perseus

Jkay framework makes my rom a caos so I flashed back my rom without wipe.

Now I'm on 400mb zram and 200 swap on internal sd and situation is the same previous. I think the very useful thing of Jkay framework is the 50app unlocking.

I think it is possible tweaking service.jar.

From universe with my gs3
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][23/03] Perseus

Domt swap on internal sd it is dangerous
[Galaxy S III Original Android Development] mattiadj:
R: [Kernel][23/03] Perseus

Not mate :) check my mod about multitasking. I'm swapping on internal from 6 month and until now all is ok :)

From universe with my gs3
[Galaxy S III Original Android Development] psyntific:
Re: [Kernel][23/03] Perseus

Thanks invinciblecc it works like a charm...:)
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][23/03] Perseus

By swapping on internal memory if u mean partitioning internal memory or putting swap file on internal memory then it is dangerous because each storage has a limited amount of read write cycles

So putting swap file on Ur phones memory is not advised

If u r talking about Ur mod and have actually swapped internal memory band external memory then it should be ok
[Galaxy S III Original Android Development] nfsmw_gr:
@invisiblecc

Well,it actually does work indeed.

But it seems script manager doesn't like spaces,i tested command after command sperately to figure it out

and i ended up removing a couple of spaces to make output less errors. :p

Anyway it still does say the message device or resource busy but it works fine. :)
[Galaxy S III Original Android Development] nfsmw_gr:
Quick status update,just tried listening to some music.

I must say i enjoyed overall the old "scoobydoo sound" better than boeffla,both on headphones and on phones speaker...

Any chance of reverting to the old sound engine?

(btw yes i disabled saturation prevention)

I did like however the privacy mode and the microphone gain features. :)
[Galaxy S III Original Android Development] shorty1483:
For me it's the opposite. So glad AndreiLux switched from the old one to Boeffla...
[Galaxy S III Original Android Development] AndreiLux:
I'm not going to do anything right now until the drama calms down.
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][23/03] Perseus

As promised here is a simple app so you can all play with zram easily.

Zram Control V 1.0

Download: http://db.tt/p4Bq0Y48

Features:

> Slider to chose size

> Swap on/off google

> set size changes

> set on boot via init.d

> remove init.d boot set

Planned:

> Swappiness slider

> zram detailed info

> hard swap control
[Galaxy S III Original Android Development] drknezz:
Hey guys, I really want to try out this kernel but my phone doesn't want to let me. After flashing and rebooting it keeps going into a bootloop, had to revert back to Boeffla Kernel.

Running Omega v43.1 which is 4.1.2 so no issues with JB being the problem. I honestly have no idea why it won't work for me :(

Any help?
[Galaxy S III Original Android Development] Erahgon:
Re: [Kernel][23/03] Perseus

To those who don't like the new sound engine: what do you perceive has regressed? Sound quality? Loudness? EQ settings? Bugs?

This would help Andrei better the sound engine.

Now on to some more swap/zRam discussions!

@Andrei: hope you don't mind us cluttering up your thread with this swap and zRam stuff!

@Invinciblecc: no problem mate! I was just trying out 832 MB as I was curious! Haha! Turns out that there's no "reserved space" on the RAM for zRam specifically. So that doesn't really matter. However, if I want an optimal system (and make use of swap properly), it's better to keep zRam regulated. Although, even with 832 MB my device was fairly responsive.

With regards to the swapiness, I prefer 70 when using hard swap, as it reduced the amount of lags (and the multitasking ability was the trade-off). I kept it 90 as that was the value provided by Andrei. Also, I want to bias my device to perform better at the cost of a slight bit of multitasking. I hope you get what I mean!

Lastly, in your screenshot, the "swapoff" command wasn't applied properly (I.e. there were no targets nor args). It should be "swapoff /dev/block/zram0".

My next step is to try 500 MB zRam and 512 MB hard swap. I have a class 6 SD card, 64 GB - partitioned with ext4 on P1 and swap on P2. Going to use Yank's script to do that.

Also, regarding the I/O schedulers and readahead, it was explained perfectly by the person above about it being a modular system. To my knowledge, schedulers aren't switched. The logic is applied to a block device. I'm going to try "row" first, then "cfq". I think I'll keep my readahead to 512 KB on internal and 1024 KB on external.

I prefer init.d scripts, as they act early in the boot stages.

---------- Post added at 01:01 AM ---------- Previous post was at 12:56 AM ----------

Delete Boeffla's init.d files from the init.d folder. His kernel app creates init.d files to change kernel parameters, and other kernels have problems due to conflicting pointers.
[Galaxy S III Original Android Development] AndreiLux:
Apparently this is a reoccurring issue by other kernels and ROMs infecting init.d with some zombie scripts, very awesome practice...
[Galaxy S III Original Android Development] nfsmw_gr:
That's fair enough.

Atleast can the speaker bug be fixed if boeffla is the default from now on?

A poll could be created on first page to know which audio engine people prefer.
[Galaxy S III Original Android Development] rickoslyder:
After this bump I give up.
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][23/03] Perseus

Zram control update:

Zram control V 1.1

>Hard swap ON/OFF toggle

>Swappiness slider.

Note: use yanks script to set up hardswap if you like. No hardswap related stuff will be set to init.d

Download: http://db.tt/PoYeh5WT
[Galaxy S III Original Android Development] nfsmw_gr:
Thanks for this.

Why don't you create a thread for it at themes and apps though?
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][23/03] Perseus

Will do soon ;)
[Galaxy S III Original Android Development] TigerCourage:
Re: [Kernel][23/03] Perseus

I can confirm it's smoother now with 500 zRam than with 200 and multitasking is just awesome!
[Galaxy S III Original Android Development] mattiadj:
R: [Kernel][23/03] Perseus

Which swappiness and lmk?

From universe with my gs3
[Galaxy S III Original Android Development] TigerCourage:
Re: [Kernel][23/03] Perseus

Latest Perseus defaults
[Galaxy S III Original Android Development] mattiadj:
R: [Kernel][23/03] Perseus

Ok so 90 and standard lmk.

From universe with my gs3

---------- Post added at 12:34 AM ---------- Previous post was at 12:28 AM ----------

Ok guys.

No time to make a cmw zip but I have made a new TEST version of my popular multitasking script supporting zram.

Nothing special.

500mb zram + swappiness 100 + custom lmk.

I'm using it from today without any lag and good multitasking results.

Simply download this file from

http://db.tt/toTFlKnW

Copy it in etc/init.d and set permission to 777 then reboot.

Give me your feedback to improve this

From universe with my gs3
[Galaxy S III Original Android Development] yahyoh:
what do u think Andrei ?
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][23/03] Perseus

Hardcore is a god, I'm assuming he's looked into it more then.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] javelar:
Re: [Kernel][23/03] Perseus

Was having slowdowns and lag but after disabling zram it's great again. As smooth as it's ever been. (Wanam 6.2 and jkay deluxe)

Sent from my GT-I9300
[Galaxy S III Original Android Development] AndreiLux:
Re: [Kernel][23/03] Perseus

Irrelevant and minor. I already said there's nothing interesting in the update.
[Galaxy S III Original Android Development] jun_ng_1208:
Urm...no one? Sorry for bumping...
[Galaxy S III Original Android Development] Erahgon:
Re: [Kernel][23/03] Perseus

Hmmm... that's a first. Which kernel were you on before you tried Perseus?
[Galaxy S III Original Android Development] jun_ng_1208:
I was using Yank's kernel...but once I flash it back to Yank's kernel, GPS works fine again :confused:
[Galaxy S III Original Android Development] DenethorLenwion:
Sorry to ask, but there is no init.d folder neither in /etc, nor in /system/etc. However, "free" reports that the zram is available (swap size total is 204796 -- or is that a hardswap?) Does that mean that I have no init.d support?
[Galaxy S III Original Android Development] Erahgon:
Re: [Kernel][23/03] Perseus

Clear your init.d folder of all kernel related files and flashing Perseus once again.

The Perseus kernel gives you init.d support I believe. Create an init.d folder in " /system/etc/ " and add the file into that.

Note: " /etc/ " is a symlink to " /system/etc/ " so it is basically the same folder.

In version 34.1, 200 MB zRam is enabled by default. ZRam is, simply put, another implementation of swap. So the command "free" in terminal will display that info under the heading "swap".
[Galaxy S III Original Android Development] DenethorLenwion:
Should I remove the "txt" extension, or it doesn't matter?
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][23/03] Perseus

Zram & Hard swap control V2.0

Download: http://db.tt/mSNRxaHX

BIG IMPROVEMENT GUYS!

> will now set hard swap state selected to boot init.d ( on or off )but only if you don't have yanks swap script there.

> much faster performance. Forgot a command or two before. This works a treat and I'll leave it as is for a while.

P.S. I hope you're OK with this Andrei. Since so much discussion is on swap I thought this would help everyone...

Future updates will be in a dedicated thread I'm going to make when I get the time... enjoy!!

---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------

Sorry guys missed a bug I'll reupload again soon...

Edit: reuploaded guys!
[Galaxy S III Original Android Development] Steveon:
just a question from me

I now only use zram and set the disk size to 512mb, not combo with hard swap. So does that meant that all the swap are happening only in the RAM? I dont want any swap on my internal as it gonna wear the memory down faster

thanks
[Galaxy S III Original Android Development] hypergamer1231:
do i need to do any partitions on my external memory card to enable swap or just install this kernel and swap will work please advise am waiting for a response since days please
[Galaxy S III Original Android Development] Steveon:
i did not make any partition on ext for my zram swap to work, u can use the terminal and type 'free' to make sure whether the zram works or not

but it is diff case if u want to combo zram with ext memory swap
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][23/03] Perseus

Ya all swap is happening in ram as zram means swapping in ram

No Ur internal memory is not being worn out
[Galaxy S III Original Android Development] xclub_101:
Screen calibration => flux/f.lux ? Also WLAN adhoc mode ?

How easy/hard would be to have some extra small program to do what f.lux (flux) program is doing on notebooks? Would that be something worth doing? (I find that one nice on my notebook, but I am not 100% certain that I spend enough time looking on my phone to see the difference).

And another thing - would it be possible to add the WLAN driver extensions that makes adhoc mode possible?

The details and source code (and custom kernels) are found at:

https://github.com/monk-dot/SPAN

(another extension for the WLAN driver seems to be here:

https://code.google.com/p/bcmon/

but it is not clear if that one has adhoc mode).
[Galaxy S III Original Android Development] GrayJack:
I never have such a bad feelings with Perseus kernel.

34.1 is a real disaster: numerous lags and even freezes with even default settings in STweaks.

I really suspect the reason is:

and I don't think it should be introduced in such way it cannot be easily disabled.

Reverted back to 33.3 for a good time (luckily I have all Perseus kernel backups from some time). 33.3 works like a beauty.
[Galaxy S III Original Android Development] Steveon:
same here, until i make the zram disk size to 512MB which is recommended by former here and the lag gone, the default 200mb is a disaster
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][23/03] Perseus

Um... why don't you install the app I made for free and disable zram?
[Galaxy S III Original Android Development] tsubus:
I have 500Mb zram disksize and it's as smooth as it's ever been. I never had any lag with 200Mb either, though.

ps: is the source code on github always updated with the latest changes? (I am asking because, unless I'm mistaking, the changes for 34 and 34.1 are not in)
[Galaxy S III Original Android Development] GrayJack:
Thanks for this, because looks like it is the only stuff that makes 34.1 working more or less.

One questions: when I try to disable zRam it disables it OK. After that I press "Set now" and "Set on boot". But anyway after next start or reboot zRam enables again. Why?
[Galaxy S III Original Android Development] Steveon:
I using this technique since I am lazy to create my own script

After you installed the zram control app and set on boot, close it

Then you use a root explorer to explore sys/etc/init.D

You will then notice a zramcontrol file, Edit it by delete all and left the first 4 lines. Save it, delete the app(scared it overwrite)
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][23/03] Perseus

Yeah I haven't yet implemented that yet... I had some weird bugs do with the kernel default kicking in at the wrong time etc. Etc but I should be able to add it now..
[Galaxy S III Original Android Development] GrayJack:
OK, waiting for update.
[Galaxy S III Original Android Development] trein91:
Not sure if this is kernel related but, there are a lot of instances whereby S-voice, google Now, and certain other voice/sound input dependent apps fail to get any sound at all. Only way (that works sometimes ) is to reboot the phone until it finally works. Someone else having the same issue?
[Galaxy S III Original Android Development] Highlander11:
Re: [Kernel][23/03] Perseus

(Start OT:

I guess you'd better start that dedicated thread of yours - I have a number of comments on your app and it does not belong in Andrei's thread :p - it just won't be right or polite...

End OT)
[Galaxy S III Original Android Development] davi_ssilva:
Re: [Kernel][23/03] Perseus

Hi, thanks for the app! Could you please give me a link to download yank's script? His thread is closed now and I can't get it there. Also, I'd like to know if there's any more thing I have to do, besides installing your app and yank's swap script.

Thanks in advance!
[Galaxy S III Original Android Development] drakester09:
Re: [Kernel][23/03] Perseus

"Disaster"? Damn you guys are really dramatic.

More like "experimental", as said on the OP.

If there is a reason why the zram got configured that way is because everyone started saying that it was great.

It can be easily adjusted, and even more now with an app... If there is a necessity of adjustment, Andrei will do so in the next version.

He's either busy, taking a break or just waiting for all the noise to quiet down.

Please do so, it would be easier to follow than here. :)
[Galaxy S III Original Android Development] pedro.coba:
hi all, if Perseus working on CM10 4.1.2??
[Galaxy S III Original Android Development] anapospastos:
Re: [Kernel][23/03] Perseus

Yes it works. Please, install it and write your experience here.
[Galaxy S III Original Android Development] tsubus:
I'm sure that at some point, if zram will be kept, there will be options to configure it with STweaks. For now it has been stated how to configure it and disable it, so we can get around it easily.
[Galaxy S III Original Android Development] AndreiLux:
Now it supports Samsung JB.

/update
[Galaxy S III Original Android Development] :
don't understand now :( AOKP JB as in AOKP rom w/ CM10 device tree?

and it says in first post Samsung JB.

sorry, but confused.
[Galaxy S III Original Android Development] AndreiLux:
Ahhh whoops. I misread your post. Right no AOSP support for now until they sort out JB.
[Galaxy S III Original Android Development] naveediftikhar:
ok..seems nice..but facing issues..flashed using mobile odin..got stuck on samsung logo..wiped dalvik cache and cache...phone booted up..but lost signals...phone got stuck after a min or so...now can boot up at all..stuck on sam logo!!:S using alpha 22 btw!
[Galaxy S III Original Android Development] AndreiLux:
What ROM are you on? I tested and made it on LI8.
[Galaxy S III Original Android Development] naveediftikhar:
ohh sry..m using li8..thought i mentioned but guess i forgot..!

---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------

ok tried flashing through pc odin aswell now..still no use..stuck on sammy logo...seems life the phone is functioning within but the screen is stuck as pressing the home button lights up those capacitive buttons...but then nothin again...!
[Galaxy S III Original Android Development] AndreiLux:
Home button problem eh? Well re-download the .tar. I had a last second mistake fixed and had to re-upload the file.

I have no issues so far on LI8 and everything seems working.
[Galaxy S III Original Android Development] naveediftikhar:
ok update again..flashed back siyah rc1 and all's normal again!...!

---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------

ok ill redownload it..jus in case...i downloaded a .tar like 5 mins ago to flash through pc odin..so when did u exactly reupload?
[Galaxy S III Original Android Development] nodstuff:
Sweet, this is the kernel I've been waiting for.

Thanks Andreilux.
[Galaxy S III Original Android Development] mariosraptor:
This look really promising Andrei. But for me it broke the softkey buttons. It works whenever it wants. Had to revert back to stock XXDLI8 kernel

Using wanamlite 3.6
[Galaxy S III Original Android Development] AndreiLux:
I fixed the softkeys in 22.1. Re-download.

I hope it's stable now.
[Galaxy S III Original Android Development] Flypwnz:
+1. Same here :(
[Galaxy S III Original Android Development] more2come:
Is this kernel based on the I9305 sources? Will give it a try and report back!
[Galaxy S III Original Android Development] AndreiLux:
You need to be more specific and provide the last_kmsg log. I don't fix it if I can't reproduce it, as it works fine here.

No, this is based on i9300 sources.
[Galaxy S III Original Android Development] jnr21:
+1

:(
[Galaxy S III Original Android Development] more2come:
Working fine here. No problems since installation. Feels a little snappier than LI8 standard kernel, additional RAM has a positive effect on multitasking. Will try some more demanding stuff later on this night!