yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Yank555:
Can you post the result of this :

fdisk -l /dev/block/mmcblk1
which swapon

JP.
[Galaxy S III Original Android Development] MuertoKo:
Don't think any luck was needed :D

Btw have you looked into intellidemand? It's something I'm missing from Sensation, even pegasusq works great... Any idea if faux did any implementation of intellidemand with quad core devices? Just curious anyway :P

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Spoke with him about intellidemandq (just invented the name ;)) when I got my S3, but unfortunately no, it's dualcore only, would need to be adapted...

But as he said, for once, the stock governor, pgasusq, is an excellent one out of the box ;)

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.3 Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
Sure not complaining about it :P was just curious about the matter :D

Glad to have pegasusq anyway, remember that nasty sucker stock ondemand on Sensation?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Yeah, not of much use ;)

I suppose device manufacturers have learned from experience (watching what devs like faux and others did as well), that much can be achieved having a good governor, so it made sense investing some energy to come up with sth. good in that area.

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.3 Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Is there a way to manually alter the io, via root explorer? I had voltage control installed and it said cfq was default but I set noop in kernel, and have cleared voltage control boot settings. Thanks!

Yay TF101 too!
[Galaxy S III Original Android Development] nass06:
"Can't open /dev/block/mmcblk1 permission denied"

I will check again the partition tonight.
[Galaxy S III Original Android Development] slim80:
Hi Yank555. The values of swappiness that i can choose in aroma is 60, 70, 80, 90 and 100. Why various memory tweaks suggest to set it at 0 (for example V6 SuperCharger), 10 or 20?

Thanks.
[Galaxy S III Original Android Development] jayden2009:
I suggest to dont use supercharger so if you can then delete it....then make a swap partion on youre ex sdcard ( i have set partition to 512MB) then flash this kernel and then set hardswap in aroma and youre phone will be a rocket :good:
[Galaxy S III Original Android Development] Yank555:
My bad, I always forget to say that you need root access to issue these commands, so :

[COLOR="Red"][B]su[/B][/COLOR]
fdisk -l /dev/block/mmcblk1
which swapon

Swappiness, as the name suggests, is something related to swap, i.e. virtual memory.

Setting it to 0 is pure nonsense if

you actually want to use virtual memory

(hardswap or zram), since in essence you're telling Linux

to try not to use virtual memory

, so what's the point in doing that ?! :eek:

Setting it to 0 if you don't use any virtual memory makes just not any sense at all... :silly:

So you'd need to ask this question in the Supercharger thread why it's done, zeppelinrox must have had an idea when he added that to his script, but I don't quite get it from where I stand, might be missing something :confused:

Anyway, read the "Virtual Memory" section in the OP and you will be enlightened on that topic !! ;)

JP.
[Galaxy S III Original Android Development] nass06:
I have this :

"

Device Boot Start End Blocks Id System

/dev/block/mmcblk1p1 * 33 104160 3332096 b Win95 FAT32

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk1p2 104161 120480 522240 82 Linux swap

Partition 2 does not end on cylinder boundary"

So i have a linux swap partition, i read in you're other thread that it's better to be the last partition

But which swapon it's not a command right?
[Galaxy S III Original Android Development] Yank555:
Oh yes, it is ;)

Since the first turns out to be ok, my guess (which swapon would have told me) is that you don't have busybox installed correctly, in /system/xbin that is.

Check that, and if it itsn't, install busybox app by Stericson from Play Store, and do a smart install to "/system/xbin".

JP.
[Galaxy S III Original Android Development] nass06:
Busybox was install in /system/bin, i change to xbin and know is working, thank you men, i will test this and tell you if my gs3 run better.
[Galaxy S III Original Android Development] Yank555:
So, I finally got that ç%*ç& thing that kept CPU freq. to scale above what you chose as max (fractions of seconds only, but not right nonetheless).

Changelog v2.4

added asynchronous PPP support in kernel (needed for asjkl)

removed PPPoE support in kernel (not needed afterall)

limited cpu freq. table to disable freq. above CPU max to avoid using higher freq. at any time (even few seconds) - This will impede setting freq any higher than chosen in Aroma, even with SetCPU/System Tuner ..., except by changing the value in /sys/power/cpufreq_max_limit !

/sys/power/cpufreq_max_limit now set by Aroma script to limit CPU frequency from using more than what user wants (usage up to 1.4 during boot is normal even if lower CPU max. chosen in Aroma)

Download link (MD5 32d1ebe063d013c00b1a692fb3d3b84e)
[Galaxy S III Original Android Development] habylab:
Nice update, well done.
[Galaxy S III Original Android Development] Ninolina:
Thanks for the update...:) I will test it tonight...:)
[Galaxy S III Original Android Development] grzesdroid:
Super kernel, everything works well. Cheers and keep up the good

SgS III / ARHD 14 / Yank555.lu 2.4 / Tapatalk / SwiftKey
[Galaxy S III Original Android Development] nfsmw_gr:
Thanks for those answers mate. :)

I've read that post after a while when it has been posted because my gf has an S2 and i'm tweaking it for her(she knows the basic though flashing a rom/a kernel etc. :p).

You're right in your conclusions,it's more aggresive than the previous settings but i find the ui the same or better/faster/smoother that way so i'll keep it like those settings.Also the scores from 8000-9000 i had in Antutu have gone back to normal at 13000 so everything's fine for me! :D

Finally the battery,i didn't nottice much of a difference myself.

Take a look yourself:

I've been gaming almost all the time and brightness was most of the time around 70%.I'm pretty pleased myself! :)

Btw,i havent checked the latest version but judging from what i've seen i think it'll be great. ;)

Cheers mate.
[Galaxy S III Original Android Development] Yank555:
Looks not too bad considering what you were doing ;)

Anyway about settings and battery life, there's not really bad or wrong ones, some may hit the battery more or less, it's up each one of us to find it acceptable ;)

I mean one can drive his car in a way to have best fuel efficiency, if that's what one wants, or rather race it and have more fun at the cost of a little worse efficiency (I'd be the latter in my car ;)).

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4 Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] androidfreak007:
Oh my ****ing god, your kernel is awesome! My s3 is blazing fast and everything is so smoothy

Keep up your fantastic work
[Galaxy S III Original Android Development] MuertoKo:
Speeder here on both car and phone :D

Great 2.4 btw ;)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] corrsea:
I hope you're not using your phone while speeding in your car:)

ROM Sotmax V5

Kernel Yank555.lu-V2.2a
[Galaxy S III Original Android Development] Yank555:
I tend to avoid that, love both way too much (plus my life's also worth quite a share to me :D).

JP.
[Galaxy S III Original Android Development] MuertoKo:
+1,love car & life lol

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] ole12:
I love my dog.
[Galaxy S III Original Android Development] Jmldsilva:
Hello,.

you are doing a great job with your kernel... i have tried many and yours is amazing.. what is your evolution plan for this kernel.

i have a default sammy rom (j5) indian update and i don´t see any problem running, is there any cons?
[Galaxy S III Original Android Development] Yank555:
No cons from my point of view, it's my daily kernel on my business phone, so it must be working.

I'm considering to add UV options, though not in Aroma, and not with the point to save battery (UV brings close to nothing in battery savings really, but adds a big risk of instability). The goal of this would be simply to reduce temperature... but we don't want the thread flooded with "my device reboots occasionnally" becuase users tend to push the limits above reason and blame the kernel when it goes wrong (experience for the past speaking here).

Other than that, whatever comes up as useful, and of course any update be kernel.org will be added (as far as it is possible).

JP.
[Galaxy S III Original Android Development] ole12:
No cons.

In my opinion, this is the closest thing you get to stock kernel (if not better?)

And it bring good amount of configuration.

And a very god, and helpful maker/chef (don't know the word of it)
[Galaxy S III Original Android Development] Jmldsilva:
Its working perfectly.. as i said before.. question? In aroma memory killer option what is the best one i am not a gamer...

---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------

Many thanks for your answer....
[Galaxy S III Original Android Development] Yank555:
I wouldn't link it to gaming or not gaming, rather to using some kind of swap or not.

If you don't use zram nor hardswap, just choose don't set.

Or best, try out different settings for yourself, keep what works best.

Set LMK high will impede multitasking but keep device fast as less apps run at the same time. Set it low and multitasking gets better, but to low and you'll be getti g lags.

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4 Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Been testing 1.4GHz in the last 1-2 hours to check if my fix works, looks good so far :

1.5 & 1.6 GHz not used at all.

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4 Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] Jmldsilva:
Yes your fix is working... i have tested to and did my self some benchs at 1.4ghz, 1.5 and 1.6 not used.
[Galaxy S III Original Android Development] nfsmw_gr:
Yes i'd like to report too that 2.4 version works great!

Thanks JP! :D
[Galaxy S III Original Android Development] Yank555:
Still, I'm not quite happy with it, it's not clean enough for my taste, it locks freq. well, so technically it's fine, but I dont like the fact that upper limit, even if set by CPU apps looks fine, will still respect Aroma setting, looks wierd (i.e. in Aroma you say 1.4, after boot you go into SetCPU, set it at 1.6, which will look as if that worked, but freq. will still not go above 1.4).

But I've already though of sth. Maybe a minor update tonight if what I made up in my mind works as expected once it's coded ;)

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4 Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] starbucks2010:
Can someone spare a minute and help me to find ut if my swap is activated?

1. I created a swap partition on my extSDcard of 1Gb, linux swap

2. I installed the kernel v2.4 with swappiness, no zram, 100 (I don't remember the option)

shell@android:/ # fdisk -l /dev/block/mmcblk1

fdisk -l /dev/block/mmcblk1

Disk /dev/block/mmcblk1: 8031 MB, 8031043584 bytes

255 heads, 63 sectors/track, 976 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk1p1 1 845 6787431 b Win95 FAT32

/dev/block/mmcblk1p2 846 976 1052257+ 82 Linux swap

shell@android:/ # which swapon

which swapon

/system/xbin/swapon

shell@android:/ #

Is it ok?

PS. My Antutu score fall from 9463 to 4679 and Quadrant from ~6000 to ~3400, so smth happened.

Uploaded also the swap.1.log renamed to .txt to be able to upload it on xda.

Thank you.
[Galaxy S III Original Android Development] Yank555:
Partition is fine, busybox is fine as well.

If you want to really know it's working :

free
cat /proc/swaps

As for benchmarks, well for me they're not worth the time you loose running them, if you feel the device is fast, that's when it really is, you're the best benchmarking "app" ;)

But if you really want to do benches, have a look 1-2 pages back, nfsmw_gr posted pegasusq settings that "solve" the benchmark problem ;)

JP.
[Galaxy S III Original Android Development] starbucks2010:
Ok, it seems that the swap is activated:

shell@android:/ # free

free

total used free shared buffers

Mem: 853360 717660 135700 0 16340

-/+ buffers: 701320 152040

Swap: 1052252 65788 986464

shell@android:/ # cat /proc/swaps

cat /proc/swaps

Filename Type Size Used Priority

/dev/block/mmcblk1p2 partition 1052252 65788 -1

shell@android:/ #

But I still don't understand why this drop in the benchmarks. And also I feel the ROM is not moving so smooth like before, with v2.4.

The drop is 50-75% for CPU Integer, CPU float-point and 2D&3D graphics. The rest of tests are similar or better than nfsmw_gr.

Maybe I'll try to reflash the kernel without swap to see if the problem is coming from it.

PS. I just checked on Turkbey ROM and I see that the ROM is supporting init.d but when I flash your kernel I choosed also init.d. Could this have an impact on performances?

Thank you.
[Galaxy S III Original Android Development] nfsmw_gr:
Hmm...I don't use any type of virtual memory here,so i can't tell if that's the problem.

My rom and kernel also has init.d support so absolutely no chance the init.d is the issue. (foxhound rom)

Take a look at those pegasusq settings and test if they work ok. :)

I get around 13000-13500 in Antutu with these settings.
[Galaxy S III Original Android Development] starbucks2010:
I reflashed the kernel without init.d and Antutu gave me 12.610 and Quadrant ~5800. So, I think that the problem was the "double init.d", one in the ROM and the other on the kernel. At least now we know what are the consequences of flashing kernel with init.d support when the ROM also have it.

Best regards.
[Galaxy S III Original Android Development] Yank555:
Yep, it's active. Just a hint, I found 256Mb to be best for my use, but some use more just fine (but more is not always better).

As for the benches, strangely I've tested this, and sometimes during the test (!!) some cores were offline ?! :silly: So what's the point in that.

I got benches in Antutu between 8000 and 13600, without changing anything, by doing multiple benchmarks

in a row

, thus without rebooting or doing anything in between.

I can only tell you that I'm done and over with benches and I'm not sure at all that any of these high-tech bench-apps are really "good" or made for multi-core devices for that matter, but that's just a hunch and I didn't feel like losing further time trying to find that out :laugh:

As for init.d, best practice is to first try without (support = no in kernel) and check if scripts are run. If it isn't then reflash kernel (just config) and choose yes and you should be good. Having it run twice is (or rather might be) a bad idea.

JP.

Believe me, that's not it, it's just the fact that by doing so you rebooted and all cores were still up when you benched ;)

Having init.d run twice is only bad in cases like UV for instance (not an issue here since there is no UV support as of now), but say you have a script that does UV by -100mV, if it's run twice that will add up and you'd be undervolting at -200mV, you're 99.9% certain to end up in a boot loop. But activate zram twice, no problem, the second activation will fail with a "device is busy" error, nothing bad will come from that. But other than that, that won't have an impact on performance once boot is complete.

By the way, most ROMs use the ramdisk that comes with them to support init.d, so flashing a custom ROM replaces the ramdisk and in this case it will break init.d support. So are you certain you still have init.d scripts running at boot ? Better check this !

JP.
[Galaxy S III Original Android Development] nass06:
I feel exactly the same since a used swap partition, specially with chrome browser is very lagy, or with sms and launcher.

You think it's because my mmc is class 4?

I'll try without init.d support.

Thank you.
[Galaxy S III Original Android Development] Yank555:
Chrome is a memory hog, so it will use a lot of memory, and start using swap. You'll end up using swap very intensly and it will reduce overall speed (hence lag).

Do take the time to actually read the "Virtual Memory" bit in the OP (and the FAQ of my hardswap mod that is linked there).

There is no better way to use something once you understand how it works, and thus you can decide if it's something you should use or not.

JP.

PS: Again, disabling init.d support

has not the slightest impact on performance

, it will or won't execute you init.d scripts. If you feel a difference, you should give a look at what is actually in your init.d, since if performance is worse with, you should consider removing the mod that's in there causing this.
[Galaxy S III Original Android Development] nfsmw_gr:
I aggree with JP,i don't think the issue is init.d support.

Anyway,i'm glad to see your phone is working well again. :)
[Galaxy S III Original Android Development] nfsmw_gr:
JP could it be possible to add the audio amplification from gokhanmoral to your kernel? :)

Not the whole "v****o sound" port,only the amplification part.

My headphones sound quiet now,hehe...

Or if you have another suggestion tell me,i'm all ears! :D

(btw i've tried that http://xdaforums.com/showthread.php?t=1722136 but no effect for me)
[Galaxy S III Original Android Development] Yank555:
I have that one working... ?!

Didin't want to overload the kernel, since that mod did it for me...

JP.
[Galaxy S III Original Android Development] nfsmw_gr:
Wow,really?! :fingers-crossed:

How you applied the mod man?

Could you upload your default_gain.conf?

What rom are you on?

EDIT:You were right.

I reinstalled the rom with the aroma option enable loud volume hack and it worked fine.

Don't know what i did wrong though...:/
[Galaxy S III Original Android Development] Yank555:
I cooked it into my custom ARHD 14.0 ;)

JP.
[Galaxy S III Original Android Development] nfsmw_gr:
Hehe...nice man! :)

Now that it works on my rom looks like i won't be needing this file after all...
[Galaxy S III Original Android Development] Yank555:
That's what I guessed, which is why I didn't post it :o

JP.

PS: 2.4a is cooking :D
[Galaxy S III Original Android Development] ole12:
Yank555.

think I need you help.

I just bought a 16gb sdcard to try use swap.

I created a 512mb Linux swap, and the rest as fat32.

After it was done, my computer didn't recognize my sdcard anymore.

Anyhow, I plugged it in my phone and it work like it should. I can explore the sdcard within the phone, and browse with my computer when I connect it trough phone. .

But the problem is the recovery don't find the sdcard, I've copied ROM and kernel to sdcard so I can completely wipe the phone. But can't do mutch since it won't find my sdcard. I am unable to mount sdcard also.

And I'm using TWRP recovery.
[Galaxy S III Original Android Development] Yank555:
My guess, the partitions are not both primary. They absolutely need to be for Windows...

JP.
[Galaxy S III Original Android Development] Yank555:
Changelog v2.4a

added dynamic cpu_max adjustment so CPU apps trying to set freq. above max. freq. will not be able to

Download link (MD5 ea59839a455e858767d883d0c4e543a0)
[Galaxy S III Original Android Development] ole12:
Yup, I set both primary.

Remembered I read a post by you that is was important.
[Galaxy S III Original Android Development] Yank555:
And Windows can't read the card ??

Can you post a :

su
fdisk -l /dev/block/mmcblk1

Thanx, JP.
[Galaxy S III Original Android Development] Yank555:
Guys, sorry, small mistake, forgot to correct sth. in Aroma script generator, OCing wouldn't work (1.5GHz, 1.6GHz).

It's corrected, please redownload and check MD5, this one's to right one (updated MD5 everywhere).

Again, sorry for this :o

JP.
[Galaxy S III Original Android Development] ole12:
Yea, right after partition was complete, I got a corrupted error.

And when I re inserted the sdcard to my pc, nothing happened.

Anyway, here is the outcome.

u0_a58@android:/ $ su

u0_a58@android:/ # fdisk -l /dev/block/mmcblk1

Disk /dev/block/mmcblk1: 15.7 GB, 15707668480 bytes

4 heads, 16 sectors/track, 479360 cylinders

Units = cylinders of 64 * 512 = 32768 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk1p1 129 16512 524288 c Win95 FAT32 (LBA)

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk1p2 16545 479168 14803968 b Win95 FAT32

Partition 2 does not end on cylinder boundary

u0_a58@android:/ #
[Galaxy S III Original Android Development] Yank555:
OK, the second partition is not of type "Linux Swap" (it is primary). Windows won't like that, and Linux will take it, but swap won't work.

JP.
[Galaxy S III Original Android Development] ole12:
I don't get it, shouldn't both partition set at primary?

How can I reformat/partition it again since windows don't recognise the sdcard any longer?

Might GParted do the trick?

Btw, I used minitool partition wizard.
[Galaxy S III Original Android Development] Yank555:
Primary yes, that's the kind of partition, that is fine as your FAT32 partition is mmcblk1p1 and the second is mmcblk1p2 (would have been mmcblk1p5 else, p1-4 are primary, p5+ are extended logical partitions).

But the partition type must be "Linux Swap" not "Win95 FAT32" for mmcblkp2.

Minitool is just fine, that's what I use all the time, Gparted should do the trick as well.

JP.
[Galaxy S III Original Android Development] jayden2009:
Taste is good :D

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] rock4hell:
i love your kenel but pls can u make it work on aosp roms plz
[Galaxy S III Original Android Development] slim80:
Hi Yank555. For the Under Volt? I must to create any script?

"SetCPU" or "Voltage Control" are not compatible :(
[Galaxy S III Original Android Development] MuertoKo:
Try using search, or at least reading OP please, Yank inveted many hours here so please, read before asking!

Anyway, gonna answer here as I don't wanna sound rude or anything, UV is not supported in this kernel as, for Yank and many in here, UV is useless in terms of battery life, it can easily cause issues if you misstouch it and finally it's not proven to have an impact into temperature, even if this needs more research to be done!

Glad if I could help and please, take it as a rule to read and search before writting here in Xda :)
[Galaxy S III Original Android Development] Yank555:
Sorry, but for now I don't have any plans to support AOSP, it's not on my roadmap :(

If at some point I dicide to use an AOSP ROM (that would be CM10 rather), then probably I would make a different kernel for it.

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4a Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] nfsmw_gr:
Hey,give a try at FoxHound or Wannam Roms!

They are smooth fast and stable. :)

The only reason i used CM9 was that touchwiz based roms sucked for me in terms of smoothness...but now with jellybean they're great!

Give them a try. :)
[Galaxy S III Original Android Development] MuertoKo:
I'm using stock deodexed JB ROM using JB Domination Theme and Nova launcher paid version, won't ever leave this combo :P

At least not until a proper CM10 comes to light, and that's not on dev's but on Samsung hands, until they release sources needed I'm sticking here :P

May like to give it a try ;)

Enviado desde mi GT-I9300 usando Tapatalk 2