yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] habylab:
Silly question, has this got the Black Crush fix? Thanks.
[Galaxy S III Original Android Development] Yank555:
This is indeed not supported, as that module is not open-source (Microsoft proprietary code).

There is a way, or a hack, to load it anyway ... so far I didn't feel the need to add it, since it's possible to reformat 64Gb cards in FAT32 (not in Windows, though !).

JP.
[Galaxy S III Original Android Development] Yank555:
OK, I'm testing this right now (as I run at 1.6 by default...), mine's not going above 1.4GHz ?!

I've also erase init.hardswap.sh and reflashed the kernel (1.5a), the file is back after reflashing.

JP.
[Galaxy S III Original Android Development] MuertoKo:
I'm using it caped at 1.4GHz since install and all is working like a charm O.o Dn why tweaks are not applied to him... :S Maybe a log of his kernel flashing could give some light... even if tweaks are installed properly must be something else... right?

All tweaks working, hardswap appears there (even if I just deleted it, for now...) :S

Actually CPU is running at 1.6GHz for 26 seconds, guess it's time until it sets to 1.4GHz... no more so all good on my end!
[Galaxy S III Original Android Development] jayden2009:
I have tried a lot of kernels...had only one favorite...that was perseus....now I have added one to my favorites....I can only say one thing...you have done a very good job...I can't judge it on the complicated things like values etc etc because I don't have the skills...but it's so smooth...thanks for sharing you're kernel with xda :beer:

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] corrsea:
Hits 1.6Ghz fine for me JP
[Galaxy S III Original Android Development] jayden2009:
Same here it hits the 1.6 :thumbup:

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] Yank555:
The config is applied late at boot. But it should be running at 1.4 if no settings are applied ?!

Need to dig into that to make sure everything is right on that end.

JP.
[Galaxy S III Original Android Development] Yank555:
Oh, I almost forgot, if you don't have a swap partition, the script will not get installed and it should say this in the flashing log :

Problem, no swap partiton found !
--> Hardswap installation aborted.

I've checked with all scripts removed (no Aroma settings, pure vanilla kernel), and the kernel is locked at 1.4GHz max, as I intended it to be, stock values by default...

Do you happen to have any kind of CPU controlling app, lile SetCPU or System Tuner that sets this at boot time ? Or some init.d script ?

JP.
[Galaxy S III Original Android Development] Yank555:
I've made a full clean-up flashable zip, so you can remove all the files that at worst might have been added to your system :

/system/etc/init.kernel.sh

/system/etc/init.hardswap.sh (only if you chose hardswap = yes)

/data/kernel-script.log

/data/hardswap.log (only if you chose hardswap = yes)

/data/swap.0.log (only if you chose hardswap = yes)

/data/swap.1.log (only if you chose hardswap = yes)

/data/swap.2.log (only if you chose hardswap = yes)

/data/swap.3.log (only if you chose hardswap = yes)

/data/swap.4.log (only if you chose hardswap = yes)

Kernel configuration & log files removal (MD5 a9181a4f0f4e5b6bc39c8da2fbae212b)

Flashing this will remove everything in preparation to flash a different kernel, so your system becomes perfectly clean again, as if my kernel never had been there.

JP.
[Galaxy S III Original Android Development] Yank555:
Changelog v1.6

mdnie: custom settings - Includes hardcore sharpnes fixes, and black gamma curve adjustment for black crush (AndreiLux)

used more "conventional" default Aroma settings

Download link (MD5 59c64375e3f92e83e14b3ddacc2b65c4, reuploaded a304370b2d9b4f771b6884ac1847a8ee)
[Galaxy S III Original Android Development] DannySchaukens:
Thx men. Its smooth and the battery after 14h with data, bluetooth for calls, calls, 2 times mailsyn, whats up is very good. 64₩ 1h15 screen on.

Thx !!!
[Galaxy S III Original Android Development] Yank555:
Glad it's working fine for you ;)
[Galaxy S III Original Android Development] jayden2009:
Lol kernel is not getting the time to settle down... Going to flash 1.6 thank you :)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] uberto.costanzo:
work very well thanks Yank:good:
[Galaxy S III Original Android Development] Yank555:
I've reuploaded v1.6, nothing changed, except I decided it was time to add a splash-screen to the Aroma installer ;)

JP.
[Galaxy S III Original Android Development] MuertoKo:
By mdnie custom settings you mean you have customized them (using those 2 tweaks) or that they are customizable via script? (remember reading about this somewhere on SG2 I guess... My sister has one LOL)

Flashing :D

EDIT: Btw, forgot to thank you for implementing this as I suggested :D :D So so glad for it m8! I'm using all black theme from Vertumus (JB Domination) with black icons and all that jazz, and trust me, that "black" improvement is just awesome there, I can feel a big new amount of different blacks now :D Andrei did a good work with that :P
[Galaxy S III Original Android Development] Yank555:
No I just used Andrei's commit, he did customize them, but they are not "customizable", this should cure black crush.

Let me know if it's working as expected ;)

JP.
[Galaxy S III Original Android Development] MuertoKo:
Working great as usual :D Tweaked applied properly, I swear! (Easy for me to check with all that black there :D)

Btw big LOL on Aroma logo :P

Thanks for all the effort Yank, never tested a better kernel :D
[Galaxy S III Original Android Development] Ninolina:
I just want to give you my feedback but for v 1.5 as I used it from last night. I must say it's GREAT so far. It's smooth and my battery life was never better in stand by. Last night I only loose 1% in 3 hours which is better that I had even on ICS. :) I am on newest Omega ROM v30...:)

So, GREAT job...:) I will now try newest v1.6 and see could it be even better then v1.5.

Thanks...;)
[Galaxy S III Original Android Development] keizero:
Nice, dude! :good: Just dl-ed and will flash this over your v1.5
[Galaxy S III Original Android Development] MuertoKo:
Yes ;)

http://xdaforums.com/showpost.php?p=33345154&postcount=217 <--- changelog v1.6 ;)
[Galaxy S III Original Android Development] Yank555:
Hi,

Little OT by me, just in case there are TF101(G) users in here, I've been working on my TF kernel today, if you want to give it a go and test it a little.

Here's the changelog for v1.1 :

based on ASUS v9.2.2.6 TF101G sources

added /proc/config.gz support

added swap support

added zram support

ntfs (rw) support (kernel support only)

cifs support (kernel support only)

added cfq & deadline I/O schedulers

set cfg as default I/O scheduler

new dynamic sync control (faux123)

TCP westwood congest ctrl (faux123)

Proport. Rate Reduction TCP (faux123)

ARM AES/SHA1 (faux123)

JIT compiler for packet filters(faux123)

fix ipv6 protocol lookup (faux123)

ipv4 check ret.val. dst_alloc (faux123)

ipv6 check ret.val. dst_alloc (faux123)

updated LZO compression (faux123)

do_fsync() to fget_light() (faux123)

Download link

JP.

PS: Please don't report anything in here, but PM me about it, I don't want the S3 thread cluttered with TF stuff ;) Maybe I'll open a thread in the TF forum, don't know yet...
[Galaxy S III Original Android Development] ole12:
It seems the problem was that I created Linux swap FIRST, and fat32 second. After I crated fat32 as first partition, and Linux second, it worked.

Thanks.
[Galaxy S III Original Android Development] Yank555:
The first must be the FAT32 partition, but from what you posted, you actually created 2 FAT32 partitions, that couldn't have worked either.

For Windows to read your SD card you need to comply to the following :

only primary partitions allowed (no extended/logical partitons of any kind)

only one FAT32 partition allowed

the FAT32 partition must be the first

Anyhow, glad it works now ;)

JP.
[Galaxy S III Original Android Development] nfsmw_gr:
Each person has its own choices i suppose. :P
[Galaxy S III Original Android Development] diddsen:
@yank

any plans to implement hardcores sharpness settings?

this would be great :)
[Galaxy S III Original Android Development] MuertoKo:
Changelog v1.6

mdnie: custom settings - Includes hardcore sharpnes fixes, and black gamma curve adjustment for black crush (AndreiLux)

used more "conventional" default Aroma settings

Download link (MD5 a304370b2d9b4f771b6884ac1847a8ee)

Already implemented: http://xdaforums.com/showpost.php?p=33345154&postcount=217

As said in my last post, please, use search before posting and read OP carefully :D
[Galaxy S III Original Android Development] habylab:
Nice one! The kernel development for TF101 is quite dead. Last comment, work on audio, the bug of speaker in balance.
[Galaxy S III Original Android Development] Phuongld:
Hi OP,

Love your kernel but got serious lag when play game. Don't get lag on stock kernel. Is this relative with hard swap? I'm on viking v10
[Galaxy S III Original Android Development] MuertoKo:
Please more info? You using swap? What you selected in Aroma? What init scripts do you have?

Thank :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Phuongld:
I'm using hard swap, swap 100 (default),

I have 2 init scripts: 11extsd2internalsd and sqlite.

Don't set LMK, cpu frequency is 1.4Ghz, dynamic fsync choose no, init script support choose yes
[Galaxy S III Original Android Development] Yank555:
I just PMed someone on hardswap seconds ago ;)

If you use memory hogs (like games), hardswap may be counterproductive. Also how big is your swap partition ?

Have a look at the lmk & virtual memory section in the OP, should help you understand the pros and cons of hardswap.

JP.

PS: Set Fsync to on if you want more speed, should help in games as well.

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] Chris_84:
I also got hard swap with the same scripts as you on omega 32 and had no lags for example when playing need for speed.

Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member :P
[Galaxy S III Original Android Development] Phuongld:
My swap partiton is 512Mb. Now try omega 32 maybe this time I don't get any lag.

By the way your work is brilliant! I got over 6000p with stock clock.

Edit: after change some setting now my phone become a beast. Don't see any lag even open 7 apps
[Galaxy S III Original Android Development] Yank555:
A really minor update, nothing really, just added one sysfs interface file to help being compatible "properly" with most CPU controlling tools, that's the "/sys/device/system/cpu/cpuX/cpufreq/scaling_available_frequencies" file.

Performance, battery life etc are totally untouched, not a single line of code changed in that perspective.

Changelog v2.4b

added scaling_available_frequencies sysfs interface

Download link (MD5 40939ff66d1338b736df49f5343a14ee)

JP.
[Galaxy S III Original Android Development] Ferdimage:
Wow what an awsome Kernel, havent used this one before and im very impressed with the performance.

Thank you
[Galaxy S III Original Android Development] georgesadam:
Hello yank

Thanks for the kernel but i i had a big problem yesterday after flashing ur kernel .. it was great and smooth till the battery reached 15% i couldnt recharge my phone as its showing in the battery setting USB CHARGING while im using ac charger .. i took 1hr to charge 1% . Im using arhd 12 and i used all stock settings in ur aroma installer . I took another battery and restored my backup, am i fine now? Everything look okey now shoud i use ur remove script ?

Thanks again
[Galaxy S III Original Android Development] Yank555:
Hi,

Very strange ... though I once had this on stock kernel at the time, where my wall charger was wrongfully detected as USB once, was quite surprised. Without fastcharge, obviously, that will take an eternity to charge as USB charging current is applied (500ma/h max.).

BTW, this can also happen if you use a USB extension cable, or plainly a different longer USB cable.

To solve it, I just unplugged and replugged for detection to take place again, and it was detected correctly as AC, and charged as expected.

The kernel, I speak in general terms now and not about this kernel specifically, will try to detect what kind of "thing" is attached to the other end you the cable you plug in. If it fails to find any answer within a certain time, it will

always

default to USB since that is the safest guess (because it also is the slowest).

Now you have two options :

you give it another go with my kernel, knowing that charge code, if you choose to disable fastcharge is 100% stock, so will be the behaviour as well (!), or you use fastcharge, and you wouldn't even have noticed this detection glitch is you set USB to 1000mA

you rather don't want to try the kernel again, then you can run the "remove" zip, it will remove the few leftovers (which even if you don't won't be a problem, they will just be there and do nothing as stated in the OP)

JP.
[Galaxy S III Original Android Development] starbucks2010:
Yank,

I have a strange problem and I don't know from where is coming. It may sound silly but for me is important. Since a while I don't have anymore the icons of accounts (Facebook, LinkedIn) in the right side of contracts. The only modifications that I have done is to update your kernel. Is there any chance to have the kernel something to do with this? I just want to cover all the possibilities.

Thank you.
[Galaxy S III Original Android Development] Yank555:
No, I don't see how the kernel could interact with that ... flashing the kernel will do 2 things :

replace the boot image (different partition from ROM which lies on the system partition)

system is mounted to update/replace /system/etc/init.kernel.sh (your Aroma settings) and /system/etc/init.hardswap.sh (if you use hardswap)

data is mounted to remove the old log files and add the kernel flash log (/data/kernel.log)

And that is all that is done.

Messing with these icons should happen somewhere either in /data/app/* or /data/dalvik-cache/* or maybe /system/app/* or ... ? Places I don't go...

Have you tried wiping dalvik cache so it is rebuild at reboot ?

Or uninstalling / reinstalling those apps ?

JP.
[Galaxy S III Original Android Development] scedric57:
hello yank and georgesadam

i've got the same problem since the 2.3 no charge in usb ( 1% / hour, same problem with 700ma in aroma option) , and even discharging in use on usb , i have put the 2.2 and it's good

(it's the original usb cable, insertcoin rom 2.3.1)

cordialy

Cédric

sorry for my english
[Galaxy S III Original Android Development] Yank555:
There has been 0 code change to the charging bit of sources since v1.1 !? All that was added is the possibility to unlock fastcharge and use

any

charge current up to 2100mA (but only if you have a charger that can give that much), but that is a change only in the sysfs interface, which is nowhere near the code of setting the charge current.

I charge mine just fine on my PC's USB hub with around 700-800mA/h net while the phone is powered on...

This kind of behaviour has been reported on other kernel threads, dunno what causes this :(

To validate what is configured, type this in a terminal :

>cat /sys/kernel/fast_charge/force_fast_charge
2 - Use custom mA on AC (1000mA) and USB (1000mA)

The answer is given in clear text as you can see...

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] cr0wnest:
Had random instability issues with this kernel. Phone suddenly lags and turns VERY sluggish after using it for awhile. I can press buttons but it takes forever to load, almost resorted to pulling out battery to hard reset but it managed to load anyway. Also tried different settings in Aroma but the result is the same. :/
[Galaxy S III Original Android Development] starbucks2010:
Thank you for your answer. I was 99% that the problem cannot come from the kernel but I had to ask. I did a clean cache and dalvik but no results. I'll try to reflash the ROM with full wipe and make more tests.

Best regards.
[Galaxy S III Original Android Development] androidfreak007:
Same problem here.

After clearing cache and dalvik it solves the problem but after two days of usage the problem starts again.

So i went back to stock kernel. No problems here since 4days.
[Galaxy S III Original Android Development] MuertoKo:
Only time I had this issue was my fault on plugging the cable correctly so.. can't help there... still please, try what Yank suggested, reflash kernel without setting anything on charging menú, this way Yank may have an idea! (I mean, having the issue with 700mA and not testing without it can't help him understand if can be, somehow weird, related to changing charge currents or w/e).

Just to make it easier to find a cause :P You could check your kernel wakelocks during the "slow charging process" please? The only time I had something similar, discharging while plugged in, was my fault as somehow a rogue process was keeping my device awake only during chare with USB due to a "bad" usb plug, I guess it was due to a driver problem related to using windows XP that kept my device awake...

Can you share any logs? I never experienced this and I'm quite a hardcore phone user... 15 tabs open and loaded as soon as I leave work to read them on the u-ground while I go home while I listen to music, and by using no swap and 256 readahead I've never had a single stuttering...

Anyway, what was your config on Aroma exactly? or configurations in case you tried some? A big buffer or a weird LMK configuration can lead to this behaviour if you don't have a usage according to configuration.

Each configuration has a kind of "use" for it, for Yank 3Mb readahead is great, I can't use 3Mb or my phone lags badly, but on 256Kb instead of stock my device avoids all posible lags ever... So let's guess we use our devices in a way different way (Lol what a sentence).

Hope it's configuratión related and not a weird bug! Let's help us debug this by sharing :D All you can say about the problem, logs, configuration and testnig can lead to a better kernel or at least, will let you use this kernel at 100% and enjoy this insane smoothness I got with it :D
[Galaxy S III Original Android Development] Yank555:
Never exprienced this ... can you elaborate a bit more :

- what was/is your exact kernel setup (post /system/etc/init.kernel.sh)

- what ROM / other mods do you use

- what were you doing

I won't be able to help without more input...

JP.
[Galaxy S III Original Android Development] Yank555:
One general comment I just made on a fellow kernel thread that might, should have educational impact :

http://xdaforums.com/showpost.php?p=34045966&postcount=226

JP.

PS: Not related to anything discussed in here but I think it's good for general knowledge ;)
[Galaxy S III Original Android Development] more2come:
After a few days of abscence, I returned to your kernel and the most recent kernel baffles me. I'm not using any Swap or zRAM option, but multitasking is a breeze!

I set read ahead to 256kb to avoid lagging, I experienced heavy lags with 1 MB and 2 MB read ahead before.
[Galaxy S III Original Android Development] Yank555:
That's good to know. Might be worth defaulting to 256 or 512 then in Aroma ?

JP.
[Galaxy S III Original Android Development] nfsmw_gr:
Yes i totally agree here.

Whenever(in every phone i used) i set the value at 1mb and up i ended up with micro lags in the ui and quite heavy one in games.

So yes,512 is the perfect value for me too. :)
[Galaxy S III Original Android Development] more2come:
I'll give you feedback later today, I'm going to perform some memory intense testing as well as some extreme multitasking, results will be postet ASAP!
[Galaxy S III Original Android Development] MuertoKo:
Good to read :)

As I said some time ago I set it to 256-512 and all works just way better than stock :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
OK guys, next version will have 256kB default, we can change it anyway as we like.

Funny I never have issues and it's been at 2048kB since forever, even on my Sensation at the time. Even worked fine at 3072kB (but as I didn't see any benefit, I reverted back to 2048kB).

JP.
[Galaxy S III Original Android Development] nfsmw_gr:
Any plans for the next version except that JP? :)

(not that i'm not pleased with this kernel,it's the best i've used!i'm just a litle curious. :p )
[Galaxy S III Original Android Development] more2come:
I am very pleased with this kernel, exceptional work! Had a download running in background, started a 1080p video in windowed mode and set up some routes with Google Maps, everything worked great without a hitch! This is how a quadcore powerhouse should do multitasking! I regained faith in the Exynos hardware and will stick with my S3 instead of getting a Nexus 4, thanks Yank! :)
[Galaxy S III Original Android Development] Yank555:
Great to hear ;)

So far not really, been working on my TF kernel lately ;)

Will change the cpu max freq. limitation, since I'm still not pleased with the way it is now... and I have a user request I'll be looking at, but nothing that would have any impact on performance or battery life or so...

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] cr0wnest:
I was using all the "default" settings given by the kernel except CPU speed (I chose 1.4 GHz), and I tried with and without dynamic fsync. As for the Low Memory Killer Presets, I have tried both 2048 and 3072. I am running on WanamLite v4.3 ROM with 15 toggles mod. Other than that everything is just the way it is. Unfortunately I do not know what was my exact kernel setup, i assume whatever settings I get the moment I flash the kernel with the desired options.

Then again there is a possibility I need to perform a full wipe prior to fully testing out this kernel as I have been dirty flashing updates for this ROM. I would really love to give this kernel another go once I do that. ;)
[Galaxy S III Original Android Development] starbucks2010:
How can I change the read ahead to 256kB?

Thank you.
[Galaxy S III Original Android Development] cb_jimmy:
Hi, I'm giving this kernel a try. What's the recommend LMK value for better multitasking?
[Galaxy S III Original Android Development] mabmed:
Thanks Yank555..

Works good in Wanamlite 4.3/4.1.1

No problem..
[Galaxy S III Original Android Development] cink40:
aroma
[Galaxy S III Original Android Development] Yank555:
When you do, I'd suggest to use 512kB readahead and "don't set here" for LMK.

Let us know how it goes ;)

JP.
[Galaxy S III Original Android Development] Yank555:
If you don't use any kind of virtual memory (zram or hardswap), best it to leave it stock, choosing either "Stock" to force it (in case a script fiddles with it) or "don't set here" to just leave it be.

Personnally I use 256Mb hardswap with "Medium" LMK settings.

JP.
[Galaxy S III Original Android Development] starbucks2010:
Thanx. I found out that is possible also with ROM Toolbox.
[Galaxy S III Original Android Development] ali4796:
after using this kernel (2.1) with ARHD 14

and these settings:

CPU 1.4GHz (I/O is CPU load = yes)

MMC readahead 2048kB, scheduler cfq

LMK = Medium

Hardswap = yes, zram = no, swappiness = 100

Fastcharge = custom, USB = 900mA, AC = 1000mA

init.d support = no

i had lags while playing (more than one or two times every time i played)

if i received a sms, phone seems to go on freeze then it became well

when the game was on the back and i was texting, keyboard was too slow (even in phone, contacts)

Summary, it seems that my phone has been slowed down