yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] aliw32619:
Lol there you go a new list of governors http://forum.brighthand.com/android-os/286992-cpu-governors-explained-credits-xda-forum.html
[Galaxy S III Android Development] andip71:
The question is: Does it have anything which all the others do not have and cannot provide?

I try to only implement things that are different from existing things in a good way.

So, do you have any experience with that gov in the past? Any reason why you would propose it?

Andi
[Galaxy S III Android Development] Depressed T.Bear:
Andi,

I just flashed back the other kernel and created the swapfile.

It worked perfectly. The swapfile was active and was used.

Then I flashed boeffla kernel beta again, the swapfile is still there, but is no longer used. The boeffla config app says:

Total swap: 0MB

Swap used: 0MB

Swap-free: 0MB

So it seems definitely to be a kernel bug!

Do you already have new insights?
[Galaxy S III Android Development] andip71:
No insights, honestly as I wrote many times already, I do have almost no time at the moment. So, please do not expect a quick answer on this. Especially as not many people use swap ever.

The only thing I could think of - btw - is a busybox issue. Once I have time I will find out.

Andi
[Galaxy S III Android Development] aliw32619:
Well i didn't try it yet as i found Boeffla kernel offering the best for my phone but was a bit surprised it haven't offered these governors , i only read online about hotplug and the other governors still didn't try them yet , maybe others in the thread had tried it. :)
[Galaxy S III Android Development] andip71:
As a quick test, I just activated a swap file with 256 MB size manually by these commands:

dd if=/dev/zero of=/mnt/extSdCard/swapfile.swp bs=1024 count=256000

mkswap /mnt/extSdCard/swapfile.swp

swapon /mnt/extSdCard/swapfile.swp

And it is working fine for me, so swap functionality as such works.

So must be something between the apps and the interaction. I still suspect some busybox issue together with my kernel, as this is sometimes the case.

But... as long as I have no insight how the apps want to activate swap, I will have no chance to find out where it goes wrong. Not as long as I cannot see a log of the commands the apps execute.

Andi
[Galaxy S III Android Development] MIKEMON:
swapiness not at all important, but also works on beta2

Clear data from the application config / restart / change back to a functional

Edit: I used all governors, but none compares to Zzmoove

I have optimum and I use powersave aggressive without problems
[Galaxy S III Android Development] putti71:
Which governor profile do you use?

How high did you put your SD buffer and intSD buffer?

Any other tweaks, like speedmod or so?

Thanks in advance.
[Galaxy S III Android Development] klurosu:
Always zzmoove...wait I'll see nd ya the pics...

All the rest that you can't see...is stock

sent fom a far far i9300 galaxy
[Galaxy S III Android Development] Depressed T.Bear:
Ok, I'll try it manually too. Can you tell me what I have to enter to deactivate it then?

Busybox. Mh, I noticed that it's installed to "/sbin/"... usually its located in "/system/xbin/", isn't it?
[Galaxy S III Android Development] andip71:
Sbin is the one that comes with the kernel only. Xbin is the normal location, yes.

To deactivate you use the swapoff command, just like the swapon.

Andi

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy S III Android Development] Depressed T.Bear:
Hi Andi

The commands create the swapfile successfully (checked it with file manager), but it's not working. Boeffla Config & Ram Manager Pro are saying there's no active swapfile... So I think its Busybox related, but thats to high for me. I can just hope you can find the error and fix it as soon as you'll find the time.

In the meantime I have to use the other kernel. My RAM (even using greenify..) has just ~ 70 MB free and many of my apps are restarting continuously.

Edit: Terminal Emulator now says: mkswap: no such tool ,and the same for swapon / off
[Galaxy S III Android Development] tmac31:
after beta2 my free ram is 470 mb it was 350 or something on beta1 dunno what is changed.. im using archi 1.7.15 there is something wrong with your device maybe a memory leak caused by a bad app. you should easyly have 200-300 mb free ram atleast.
[Galaxy S III Android Development] viktor92:
I haven't seen any difference in memory usage between the two betas
[Galaxy S III Android Development] tmac31:
dunno seems ram usage decreased for me nothing changed instead of kernel but lets see for a while.
[Galaxy S III Android Development] JustArchi:
You have three locations for android binaries:

/sbin - Kernel's ramdisk, these binaries are provided by the kernel and are directly located in kernel's ramdisk.

/system/bin - Provided by ROM, by convention system binaries.

/system/xbin - Provided by ROM, by convention system root-related binaries.

The order of calling commands is: /sbin, /system/bin, /system/xbin. You can check it yourself through "echo $PATH" command. This means that if you're calling i.e. "mkswap" command then it will result in execution of:

- /sbin/mkswap

- /system/bin/mkswap

- /system/xbin/mkswap

- Nothing, error command not found

Whatever comes first.

If you want to check which binary exactly is responsible for your command, use "which" command. Like "which mkswap", this will tell you where mkswap points to (one of the above examples or null response, command not found).

Now here comes the fun part: By default boeffla includes only a few binaries: adbd, boeffla-init.sh, busybox, cbd, healthd, tinyplay, ueventd, watchdogd. So if you're calling mkswap command, this is executed from either bin or xbin directory, so if it doesn't work correctly it's the ROM's fault, and not the kernel.

However, as pointed before, busybox is linked to /sbin and will be executed from /sbin unless you use the full path like /system/xbin/busybox. So actually if your mkswap command doesn't work, try "busybox mkswap" command, this will force android to use busybox binary, and it will use /sbin/busybox, the kernel's busybox instead of mkswap command provided by the ROM in /system/bin or /system/xbin.

Hope you got the point. Kernel has highest priority but due to the fact that kernel can't fit every configuration, rom should be responsible for bigger part of working utilities, not the kernel. And this is exactly done in boeffla kernel, only busybox points to /sbin from "important" commands. Apart from that, if it really doesn't work, you should notify the developer about the problem, because probably his busybox is outdated or not compatible.
[Galaxy S III Android Development] Depressed T.Bear:
Well, but Archi 1.7.x hasn't all the nice Samsung features under the hood, or?. Probably that's why you have so much free memory.

---------- Post added at 10:15 PM ---------- Previous post was at 10:10 PM ----------

Thx Archi for your comprehensive explanation! I think I understand now how it works (a bit ^^)
[Galaxy S III Android Development] tmac31:
its a samsung based rom so not really. even on stock i had 300 to 400 mb free ram. 70 mb means pretty much not usable something is realy wrong with your device.at worse case you should atleast have 200 mb free ram.
[Galaxy S III Android Development] MIKEMON:
Very detailed and explained, thanks
[Galaxy S III Android Development] JustArchi:
As above, bloatware is indeed "cut" from the base, however I also provide full standalone bloatware package (250 MB), so by default you get debloated stock on steroids, but if you want you can install everything what Samsung provides, on your own wish.

But that's not a thread about AD, if you have further questions please visit AD's Q&A :).
[Galaxy S III Android Development] Depressed T.Bear:
Ok, maybe I'll switch from NeatRom to yours ;)

So again related to busybox: I have the "Busybox Pro" App from Stericson. It has an option to remove the busybox from /sbin/ on every boot. Would it be a solution to do this and then to (re-)install busybox 1.22.1 to "/system/bin/" ??
[Galaxy S III Android Development] putti71:
Hi together.

I found this app ROEHSOFT RAM-EXPANDER (SWAP) .

Do you think this could work on our S3 with TouchWiz installed or can I configure this kernel in such a way to do the same?

Sorry for being OT and this probably dumb question, but there are so many people in appstore which say that it's a great tool, that I am very interested.
[Galaxy S III Android Development] andip71:
Without looking at it...

I do not recommend to create swap unless urgently required.

Reason:

You need a swap file or partition on SD memory.

When you place it on internal SD memory, due to the nature of swap, the wear on your internal SD card will be high. When your internal SD memory gets defective, your S3 is bricked.

When you place it on external SD, it is by far too slow for a good user experience. Lags will be quite prominent.

But this is just my personal opinion.

Apart from that: I never tried this app, so if it uses the correct commands with a proper busybox etc., it should work.

Andi
[Galaxy S III Android Development] putti71:
I like to try it on extSD. I hope it will work :)

EDIT I took 500 MB swap on extSD and my Ram manager has around 30 to 40 MB more (from 730 to 690 ), but from the feeling I can't say anything yet. This all could be big placebo effect.
[Galaxy S III Android Development] JustArchi:
There's no placebo when it comes to swap files. Use "free" command, it will let you know how your swap situation looks like.
[Galaxy S III Android Development] user2k10:
Very informed answer!
[Galaxy S III Android Development] putti71:
I left the phone now for 20 minutes and now the Ram usage is down to aroundView attachment 2732536 500.
[Galaxy S III Android Development] MIKEMON:
I do not use such an application, but Android is low ram bad Ram

In Boeffla config can be well configured / Gov, cpu, LMK / or other
[Galaxy S III Android Development] lsalamun:
It is not how much free ram you have, it is how well android handles it, some say free ram is wasted ram, some say it is not, but linux always uses all of the ram and manages it smartly, it is not like windows, linux will use every single bit of it and take what it needs for cache and then with lmk, clean that cache and put something new in it, so i never watch how many 'free' ram i have, and i have never any problems with it:)
[Galaxy S III Android Development] DocMarc73:
Same here. Never understood those ram addicts..... !-)
[Galaxy S III Android Development] ymy3890:
No KIKIT for S3 international....

Very disappointing news..

http://www.sammobile.com/2014/05/08/samsun...axy-s-iii-mini/
[Galaxy S III Android Development] andip71:
We have to be bolt.

Or, you consider jumping to other options like CM11 or Omnirom...

Andi
[Galaxy S III Android Development] XeLLaR*:
The GT-I9305 will get the KitKat update. Porting from there will not be that hard i guess?

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] andip71:
Will comment when the code arrives.

But the i9305 has 2 GB memory, while the i9300 has only one. Just to bear in mind, that was apparently also the reason behind why Samsung decided against KK on i9300 (rumors said).

Andi
[Galaxy S III Android Development] boyheadkick:
I read somewhere that it wasnt about the ram, but that the kitkat team for i9300 was running into problems initializing the system apps..they even showed an error code where the system apps were not being loaded at all

-aL

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] XeLLaR*:
If we remove the bloat it should be ok, i think. Samsung puts a lot of crap in the roms unfortunetly.. its crazy

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] hwjrmrm:
waiting for I9305 system+boeffla kernel=I9300 4.4.2 :good::good::good:
[Galaxy S III Android Development] XeLLaR*:
We need to wait for the sources, aftert that we can see if it will be possible. In this moment there are 0% informations.

If you want to check the hardware differences, check the attached image. I cant find a difference, except for the 2GB of ram, and the LTE capability and of course the Modem (which we wont need i think because we have our own)
[Galaxy S III Android Development] ShonkUK:
If you port the i9305 kernel to the i9300 would be nice if you released it for the i9305 also

to save us having to go back and re port boeffla back over :p

---------- Post added at 09:06 AM ---------- Previous post was at 08:58 AM ----------

There arnt many differences it should be trivial

we have no fm tuner on the i9305
[Galaxy S III Android Development] andip71:
While I understand your point very well, I will continue to follow my golden rule: Only provide kernels I can personally test (i.e. which I have a device for).

But I am pretty sure, there are the known "suspects" that will clone my kernel and provide it for the 9305 again as well :)

Andi
[Galaxy S III Android Development] XeLLaR*:
i can try and see what i can do but i cant promise....but i must be carefull since i dont want to brick my s3 :P

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] Mosh Edd:
Thanx for sharing M8. seems to really work well. :victory:
[Galaxy S III Android Development] gieffe22:
hope for a porting of KITKAT in i9300 from i9305...i think that [MENTION=947981]Lord Boeffla[/MENTION] and other big devs like [MENTION=5161352]JustArchi[/MENTION] and other kernelcreators should make this miracle...
[Galaxy S III Android Development] ymy3890:
+1
[Galaxy S III Android Development] XeLLaR*:
it seems that the partition layout for the GT-I9305 is completely different from the layout of the GT-I9305.

The GT-I9305 has 4 extra partitions on top of the one that the GT-I9300 has. And they have different names. Also the framework seems to be different:

http://xdaforums.com/galaxy-s3/help/porting-roms-s3-i9300-to-i9305-t1971421/page2

But for us it will be easier, because we have to remove the LTE, and not add it.

We will have to edit the framework.jar for sure. Most probably in:

com\android\internal\telephony\gsm

android\telephony

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

I want to leave a review about 5.3-beta2.

With the kernel is going ****. In normal internet surfing CPU temperature around 42-43 degrees began when beta1 was consistently 38 degrees.

Just some **** with cores. When used with the beta1 PegasusQ- balansed 99% of the time worked for 2 cores, and with beta2 kernel is constantly connected is disconnected.

Returned to 5.3-beta1, it's just perfect.

P.S. RU Community (4pda.ru) users also complain about the increase in the temperature of the processor and other problems.
[Galaxy S III Android Development] andip71:
Thanks, it can very well be, this is a side effect of the cpu plugging activated for general now.

Would be interested in more feedback on it from others. As this is very experimental.

But, when you do not try things, you never will move on. Thats why I want to give it a try.

you_man: Forgot to mention - would you like to find out which of the two changes causes your issues?

From beta1 to beta2, the cpu plugging stuff has been changed, and also the initramfs.

If you want, I can compile two kernels for you, one of each having only one change in. Then you could try both and let me know :)

Cheers

Andi
[Galaxy S III Android Development] you_man:
Yes, of course
[Galaxy S III Android Development] MIKEMON:
It is true that the temperature is higher, but I have not followed this too.

I use the phone for work and everyday use

I'm more cpu temperature monitor
[Galaxy S III Android Development] JustArchi:
This may be matter of settings Andi. Actually kernel's hotplug policy depends on selected choice, and we have a few models:

We may want to try other policy before turning it off completely :).
[Galaxy S III Android Development] andip71:
Yep, first let's you_man confirm if the updated initramfs or the hotplug policy is the root cause. Then we can go on with next trials.

Andi
[Galaxy S III Android Development] lsalamun:
Hi Andi,

Is it possible that battery life is a bit worse on beta 5.3 than on stable 5.2?

I experience a bit more drain but maybe i'm wrong, i am testing beta for a few days with exactly the same settings and it is a bit different, i switched back to stable and it was fine after then..
[Galaxy S III Android Development] MIKEMON:
Very hard to say at this base testing

For me seems about the same even if the temperature of processor utilization and higher

Maybe try a different setting
[Galaxy S III Android Development] lsalamun:
I was using the exactly the same settings, but, i am like that, i like to keep it stable, the difference was 1h of screen on time less with beta version, and i tested it for about 4 days with full charging cycles.
[Galaxy S III Android Development] MIKEMON:
In that case, go back to the stable version 5.2 and enjoy

---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------

I note that the version 5.2 stable is very hilarious
[Galaxy S III Android Development] andip71:
For beta3 I will most likely revert the hot plugging changes again. Think it needs more investigation first...

I personally feel my phone was smoother without.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] XeLLaR*:
Hmm..

I cant tell you that i felt a difference in smoothness, but i can tell you that the batterydrain has increased slightly.

(comparing b1 to b2)

Gz

X

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] matt-86:
Hi boeffla. I tried to install your kernel several times and i always get this: please update to latest binary using legacy property environment for update-binary.....

Why? I have latest philz touch and it happens both on stable 4.3 and stable omni kernel....
[Galaxy S III Android Development] ZaneZam:
the "problem" is the used version of the update binary in the CWM script not the version of the recovery itself. it's a warning that an older version of that binary is present and the legacy mode was used by philz recovery (kudos for that!). the binary must be compatible with the recovery. isn't it archi? :) my knowledge about recoveries might not be up to date so shed some more light into the internals if u are around and if it is needed ;)
[Galaxy S III Android Development] JustArchi:
You're right ZZ. KitKat introduced some new environment properties, like required support for set_metadata function to set SELinux context. Due to that, old update-binary doesn't "fully" support new standard, and even if it may work, because it's binary afterall, it still relies on "old standard" and demands from recovery to support it. So we have two binaries now, pre-4.4 and 4.4+.

TL;DR: Andi needs to take update-binary from any 4.4 ROM and replace with his own :).
[Galaxy S III Android Development] matt-86:
Ookk. Is there another recovery that supports new binary?
[Galaxy S III Android Development] JustArchi:
Pretty much everyone which supports KitKat ROMs.
[Galaxy S III Android Development] matt-86:
Suggestion? :)
[Galaxy S III Android Development] Naveed Abbas:
Latest CWM
[Galaxy S III Android Development] malachow:
Mate, the easiest way to get rid of any recovery related issues is to always use the latest version of PhilZ from this list:

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300

I can ensure you it won't fail in any aspect. ;)
[Galaxy S III Android Development] viktor92:
Andi have you noticed any difference between NB6 and ND2 roms ?
[Galaxy S III Android Development] MonsterMMORPG:
installed this

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-omni/omni11_download/Series 2.x/2.2/

on this rom

http://xdaforums.com/galaxy-s3/development/gt-i9300-resurrection-remix-4-4-2-t1815285

galaxy s3

is that correct ?
[Galaxy S III Android Development] MIKEMON:
Yep, it's a good rom, but many users takes, legal Sammy rom

Me too, I tried a lot, but I am satisfied on the official firmware and best for me

Boeffla kernel, allows system adapted to a very beautiful
[Galaxy S III Android Development] D00ky:
Andi, in case there is really no official KK for our S3 would you reconsider and make Boeffla kernel for ported rom in case it is super stable? Check out this thread. Those guys might be up to something.
[Galaxy S III Android Development] viktor92:
It looks extremely interesting !! :good:
[Galaxy S III Android Development] andip71:
Nothing significant. Runs very smooth, but not better than firmware I had before.

It is good. Battery too early to judge.

Will have a quick look in the next few days. But in Wednesday I will first go on longer holidays.

So, nothing to come very short term...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] D00ky:
I/community is in no hurry. First it has to become rock solid. In this thread: http://xdaforums.com/galaxy-s3/general/video-kiktat-update-canceled-due-apps-t2746793 looks like few devs teamed up.
[Galaxy S III Android Development] MIKEMON:
So after some testing, it seems to me beta1, economical to battery

it seems to me even smoother and faster when multitasking

just my personal opinion
[Galaxy S III Android Development] andip71:
Thanks Mikemon,

for me it looks quite similar, on top I feel the general hot plugging causes some loss of smoothness.

Before I go on holidays to Abu Dhabi on Wednesday, I will put beta3 out to you all. There I will have this general CPU plugging reverted back to how it was before (it seems it needs some more investigation first, after my return from my holidays).

Also, the beta3 kernel will allow overclocking to 1700 MHz as a test (by sacrificing the currently existing 1500 MHz frequency step).

So, stay tuned :)

Andi
[Galaxy S III Android Development] MIKEMON:
Enjoy your holiday and return to the great work Boeffla kernel.

clocked at 1700Mhz seems unnecessary, although some might use for games

But many thanks
[Galaxy S III Android Development] andip71:
At least I think, having overclocking steps 1600 and 1700 instead of 1500 and 1600 makes more sense. As 1600 should be running stable for everyone.

For people not using overclocking at all, there is anyway not a single change.

Andi
[Galaxy S III Android Development] Choristav:
Is it because there's a limited amount of steps? Why not remove 300MHz in that case?

On an unrelated note, in case we get a note2 port of kitkat, there's no way to have a custom kernel on it save for the official i9300 source drop, right?
[Galaxy S III Android Development] andip71:
No, it is - of course - possible to add frequency steps. Or remove one in the lower areas...

But you know my objective - close to stock. And stock works with these steps I do not want to change at all. Also stock already has 2 additional overclocking steps that are just disabled in the code.

And staying close to stock, I just enable them and put two frequencies behind, which is now 1600 and 1700 for a test instead of 1500 /1600.

Hope you understand.

About the other question: This is something frequently asked these days. However I have no time to really check that before my holidays anymore. After I return back we know already more...

I still say: If you want KK for your S3, move on to Omnirom or CM11. It works pretty well for 95% of the functions.

Andi
[Galaxy S III Android Development] AlboGio:
Good!

First, thank you for your job:good:

Second, sorry for my english :angel:

With another old rom and kernel, my S3 was stable on 1700 MHz

(tested in daily use, and stresstested with "StabilityTest"/"Antutu benchmark"/similar apps):good:

If you need request/tips :p , i suggest/ask the possibility to have two more options in kernel/config apps

1) Manual select the entropy level (that i have increase with other free app, it fix some my S3 lags :eek:)

2) The ability to set "events" like the many CPU app tweaker.

"If cpu temp is over than X, so downclock to Y Mhz (original 1400mhz)..."

very usefull if you want OC to 1700MHz (especially in summer and warm places)

And keep the phone stable, preventing overheating that cause freezing/reboot.