yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] KMino:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

Yank555 just wanted to say this is running beautifully. Either EMA2 stock odex with no Samsung bloat is extending battery or this kernel is :) best ever I have experienced.

No problems at all with voice calls over the weekend either, all seems good :D

Thanks dudes!
[Galaxy S III Original Android Development] :
Had the same problem. Problem disappeared after i reflashed the kernel.
[Galaxy S III Original Android Development] drew071:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

I'll give it a go

Cheers
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

@yank if I use hard swap row scheduler would increase performance but if I am using soft swap via swap file I shouldn't choose row because this limits write to swap right and would slow system down

Right/????/??

sotmax yank zram 650 swap 1gb jkay acid mod
[Galaxy S III Original Android Development] irawanjohan:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

I have the same problem too, and go back to e version.
[Galaxy S III Original Android Development] d8389:
Hi,

I've got a freeze with 3.1g after receiving e-mail & SMS at a time.

Rebooted by long "Power".

The led was fading, but in Aroma selected stock blinking.

Previously I've read similar report on one Russian forum.

Has newer got it before 3.1.
[Galaxy S III Original Android Development] Yank555:
Yep, started playing with other things, I'll always have a version precedence, that's the time I test it before releasing, will not push that fast anymore, makes no sense and people not happy (e.g. mic problem).

I've been running that kernel version for 4 full days on my daily, never happened ... so hard call to tell you what it could be from where I stand. You should provide dmesg, last_kmsg (and maybe logcat), that may help.
[Galaxy S III Original Android Development] :
Btw, Yank, can you add "check package integrity automatically before flashing" feature into Aroma? Would've saved a lot of nerves and time...
[Galaxy S III Original Android Development] Yank555:
Nope, Aroma is Aroma, I don't develop it, I just use it.

But you should really make it a habit to

never

flash anything without prior checking MD5, if you really love your device ;)

JP.
[Galaxy S III Original Android Development] mirskym:
I also had a freeze once on 3.1g. The screen had turned off so I pushed the power button to turn it on and it wouldn't. Tried a few times and finally had to reboot through extra long press.

No problems since.
[Galaxy S III Original Android Development] dedalos1:
R: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v3

I am returning to e version. The newest have many lags in scrolling. The previous was perfect for me

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
In such a case, please post the /proc/last_kmsg here, so I can have a look.

Make no sense, the only thing that has changed in the kernel is the sound engine, and that just cannot make any lags.

And I don't have any lag at all myself...

JP.
[Galaxy S III Original Android Development] :
I make a Nandroid backup each day, so i believe i'm safe :) (I consider the probability for some wrongly received bits to break hardware to be very low)

I meant, "Add some hash-checking code into one of the scripts". At most, you will need md5sum binary, am i right?
[Galaxy S III Original Android Development] Yank555:
Sure can do, but that will make more work for me to have to generate the hash every time, and maintaining 3 kernels is work enough already ;)

Plus that will just check the boot.img, but what about the scripts (update-script & script generator) ?

It's not asking too much to check MD5s, I believe, it's a good habit anyway.

And if sth's not working, there's still time to check it then and redownload if needed before posting there's something wrong with the kernel ;)

BTW, you can very well end up with a mess, if the wrong stuff gets flashed to the wrong partition, but it's very unlikely indeed.

JP.
[Galaxy S III Original Android Development] d8389:
Now it impossible.

Rebooted more, than once.

May be next time.
[Galaxy S III Original Android Development] drew071:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

Thanks for your reply. I reflashed the kernel and all is well now. Nor sure what the problem before hand was. I was on siyah kernel, then your kernel cleaning script and then flashed yank version e. That was fine and then flashed g on top and then had freezes. Then flashed again and the freezing had stopped.

Thanks again

Drew071
[Galaxy S III Original Android Development] :
My phone just hanged, had to reboot. Last_kmesg attached, though it seems to have no useful information.
[Galaxy S III Original Android Development] Yank555:
In fact my cleaning script is meant to be used before you leave my kernel, it will not remove anything from others, it will just remove what I have added ;)

JP.
[Galaxy S III Original Android Development] Yank555:
Agreed, all there is to see is that it just stopped logging and rebooted :(

But thanx for providing the log. In case this happens again, do post the log each time, maybe at some point there will be sth. helpful to see.

You were charging your phone, weren't you ?

I never paid any attention on my dmesg when charging since I don't have any issues there, but I wonder if that many "max77686" entries are normal.

What charger do you use ? I use my old htc Sensation charger.

JP.
[Galaxy S III Original Android Development] :
No, I unplugged charger several minutes before hang. Screenshot showing that attached. I use original Samsung charger and battery.
[Galaxy S III Original Android Development] corrsea:
Don't think it's kernel related, I've had the same issue using chamonix better WiFi and stock kernel. It appeared with one of the later JB releases.
[Galaxy S III Original Android Development] eric-filth:
Yank i can do undervolt with scripts? Sorry but i read last 5 pages and saw nothing related

Enviado do meu GT-I9300
[Galaxy S III Original Android Development] Yank555:
I haven't added any sysfs interface to the voltages, so no, not yet at least.

JP.

Sent from my custom ARHD 13.0 / Yank555.lu JB kernel v1.7 Aroma (Linux 3.0.48) powered Samsung Galaxy S3 using xda premium
[Galaxy S III Original Android Development] F3nr1s:
V1,7 its again very stable and very smooth !!! time to test in hard situtation now and to see battery .

Thansk again Yank555
[Galaxy S III Original Android Development] iBuzman:
yep, same for me. thx Yank :thumbup:

Sent from another Galaxy...
[Galaxy S III Original Android Development] Honchay:
1.7 - Everything is fine, smooth and had no issues so far. A keeper one!
[Galaxy S III Original Android Development] Chris_84:
Great work mate!

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] DannySchaukens:
The new one is smooooth... but i hope there will be no lagg after a day without restart?! With 1.6. I have the problem.
[Galaxy S III Original Android Development] Yank555:
Could you post your settings file (/system/etc/init.kernel.sh) so I can have a look ?

Thanx, JP.
[Galaxy S III Original Android Development] uberto.costanzo:
kernel work good stable and fast but i have not init.d folder when setting is "yes" when install in aroma, why thanks for help
[Galaxy S III Original Android Development] Yank555:
The folder is not created, only support is added if selecting "yes". If the folder is missing, you just need to create it...

But you're right, I might just add a test in the script, if there is no such folder, the script could just create on, no biggie in fact ;)

JP.
[Galaxy S III Original Android Development] uberto.costanzo:
thanks I understand now
[Galaxy S III Original Android Development] Yank555:
Changelog v1.7a

added /system/etc/init.d folder creation if it does not exist (only when selecting init.d support = yes)

Download link (MD5 262560842b3da3a1a9f46be968a5d15b)
[Galaxy S III Original Android Development] Crimsonthunder:
Your kernel is also working with foxhound essentials 1.2. No problems everything is working fast and smooth. Thanks for your work!
[Galaxy S III Original Android Development] jayden2009:
Thanks yank for you're kernel.... Going to try this when my phone is charged :)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] störte:
One question. Do you see a chance to implement the exfat support ? Most 64 Gb Sd cards are formatted in ex-fat. I format mine in Fat32 via Mac but there is still the 4 Gb Limit.
[Galaxy S III Original Android Development] Rikul:
+1 :)
[Galaxy S III Original Android Development] F3nr1s:
Yank555 reply to this question several time in this thread . And the answer is no .

In the OP , in the FAQ

So far, no, there's no exFAT support.

exFAT is a Microsoft proprietary format for which we don't have sources. There is a way to force the kernel to load the module, but since 64Gb sdcards can be formated in FAT32 as well (not in Windows, though), I so far didn't see the need to include that hack.
[Galaxy S III Original Android Development] iBuzman:
^

I use Minitool Partition wizard or Paragon Partition Magic to format my 64gb card as fat32 in Windows.. for support of files larger than 4gb I'm pretty sure Yank has recommended ntfs format - so either way you should be able to avoid exFat and still enjoy this wonderful kernel :)

Sent from another Galaxy...
[Galaxy S III Original Android Development] störte:
Just found it. Thank you. I must have overread that one. So question is answered.

@iBuzman

I do enjoy the kernel. I will follow now the ntfs support . Never heard sd cards in ntfs ,anyway better than fat32.
[Galaxy S III Original Android Development] Yank555:
If you do have a different charger and cable, try stop using the stock Sammy charger, it's really of bad quality.

Not saying it's the cause of the issue here, though.

But it's a general advice as a sidenote, as max77686 is the regulator.

JP.
[Galaxy S III Original Android Development] :
Thanks for the advice.

I compared voltage drop of Samsung charger with an Apple one and with Chinese noname. Samsung and noname - 600 mV, Apple - 300 mV. Samsung charger equals noname one?.. Great.
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

I have set the battery charge current to 1200 and am using the stock charger would it somewhat increase the charge rate

Asking this bcos I heard somewhere in the forum that stock charger supports only 1000 so no matter what uvset current value to it is going to cut off currents above 1000 so non increase in charge rate will be there

PS even I had freeezes on the last version of kernel

sotmax yank zram 650 swap 1gb jkay acid mod
[Galaxy S III Original Android Development] Yank555:
I've only read bad things about it.

The fact that I've been using my htc's charger from day one is pure chance, it was already installed and I was too lazy to swap it, plus it had a longer cable :D

I suppose Apple, at the prices they apply, should bring along a good charger (but who knows :angel:).

JP.
[Galaxy S III Original Android Development] :
Stock charger can only supply 1A, so it won`t work.
[Galaxy S III Original Android Development] :
Got another hang. Log attached.
[Galaxy S III Original Android Development] Yank555:
Same pattern, but all those max77686 entries cannot be normal, but I just checked, I do have them as well. Either an issue, or someone just wanted to flood the log a little too much with debugging info...

Will look into that.

What ROM are you on ? Any Mods ?

JP.

EDIT : No change to those sources since Sammy's sourcedrop, so they are 100% stock...

EDIT 2 : Just flashed a stock ROM/kernel on my dev S3, let's see what the log looks like there...

EDIT 3 : OK, stock kernel has the same amount of spam in there, so that's nothing to worry about, but I will try to shut that down to stop the flooding.
[Galaxy S III Original Android Development] :
Omega 40 (XXEMA2), with Jkay's Deluxe 14.9, Xposed framework 2.1.1 on 240 dpi. I do not use tweaking apps like PMR. This configuration never hanged on 3.1f (I never had any mic issues with it , so i didn't downgrade to 3.1e)

Edit 1: guess samsung had some problems with this regulator... Why else would they log every state change? If you want, i can flash some ExtendedLogging version of your kernel, to help pinpoint the issue.

Edit 2: Re-read my log. It crashed when i was using Opera last time, so i looked for it. I found that:

<4>[ 5577.658240] c3 m.opera.browser invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0

<4>[ 5577.658379] c3 Backtrace:

<4>[ 5577.658489] c3 [<c0048e28>] (dump_backtrace+0x0/0x110) from [<c05769f4>] (dump_stack+0x18/0x1c)

<4>[ 5577.658616] c3 r7:00000315 r6:000201da r5:00000000 r4:ea17a000

<4>[ 5577.658756] c3 [<c05769dc>] (dump_stack+0x0/0x1c) from [<c00cc3ac>] (dump_header.clone.1+0x74/0x198)

<4>[ 5577.658903] c3 [<c00cc338>] (dump_header.clone.1+0x0/0x198) from [<c00cc514>] (oom_kill_process.clone.0+0x44/0x224)

<4>[ 5577.659062] c3 [<c00cc4d0>] (oom_kill_process.clone.0+0x0/0x224) from [<c00cc968>] (out_of_memory+0x274/0x348)

<4>[ 5577.659224] c3 [<c00cc6f4>] (out_of_memory+0x0/0x348) from [<c00f0d2c>] (__alloc_pages_nodemask+0x534/0x69c)

<4>[ 5577.659371] c3 [<c00f07f8>] (__alloc_pages_nodemask+0x0/0x69c) from [<c00ca168>] (filemap_fault+0x324/0x428)

<4>[ 5577.659574] c3 [<c00c9e44>] (filemap_fault+0x0/0x428) from [<c00de390>] (__do_fault+0x54/0x490)

<4>[ 5577.659712] c3 [<c00de33c>] (__do_fault+0x0/0x490) from [<c00df4dc>] (handle_pte_fault+0x2e8/0x7ec)

<4>[ 5577.659861] c3 [<c00df1f4>] (handle_pte_fault+0x0/0x7ec) from [<c00dff88>] (handle_mm_fault+0x198/0x1b0)

<4>[ 5577.659998] c3 [<c00dfdf0>] (handle_mm_fault+0x0/0x1b0) from [<c004b51c>] (do_page_fault+0xfc/0X1fc)

<4>[ 5577.660138] c3 [<c004b420>] (do_page_fault+0x0/0x1fc) from [<c003f620>] (do_PrefetchAbort+0x3c/0xa0)

<4>[ 5577.660281] c3 [<c003f5e4>] (do_PrefetchAbort+0x0/0xa0) from [<c00454a4>] (ret_from_exception+0x0/0x10)

<4>[ 5577.660481] c3 Exception stack(0xea17bfb0 to 0xea17bff8)

Seems like LMK failed. Going to invoke it several times to see if it's guilty.
[Galaxy S III Original Android Development] ezechiele2517:
Yank555, I had a problem: I recieved an SMS during sleep and after that I tryed to unlock the device but the screen was black pressing home button or power button nothing happened and I rebboted the device pressing power+home button.

I'm using latest 3.1g (with boeffla sound off) and Omega rom V40
[Galaxy S III Original Android Development] Yank555:
I've just made a slight change, as it was already done by the CM team on the CM10.x kernel to stop it from flooding dmesg ;)

It's compiling, will send you a PM with a link, so in case it happens again, maybe last_kmsg isn't just flooding with those unhelpful state changes...

JP.

PS: Instead of flooding dmesg, they should add better chargers with the flagship phones :cowboy:
[Galaxy S III Original Android Development] Yank555:
Post "/proc/last_kmsg", I can't see anything from where I stand. There's still time if you haven't rebooted again yet.

But strange, two users with a problem, both on Omega V40 :confused:

JP.
[Galaxy S III Original Android Development] ezechiele2517:
in attach
[Galaxy S III Original Android Development] :
Seems like my theory from the last post confirmed. Phone behaves REALLY strange when LMK is invoked. It's not hanging, it just stops responding to any input, be it buttons or touchscreen (Music was still playing through headset, though it was buggy for the first few seconds)

Got it hanged again by overloading the memory. Phone unhanged itself after some time, though it still behaved strange: very high response time, etc. Now i'm on medium lmk.

Going to try:

Stock LMK settings, 3.1g - good enough. Does lag while switching, did slow down, but still worked (Screenshot attached - PreHome was configured not to show recent apps, only executing ones - i double-checked that)

Medium LMK, 3.1e - perfect. Almost no lag while switching apps, even while memory is close to oom. When i did load too many apps, phone just unloaded Opera. (Oldest and biggest. Just like it should.)

Stock LMK, 3.1e - No lag, normal multitasking. Does unload apps too fast... But that's to be expected from stock.

and report back. Will also try your no-flood kernel with medium and stock LMK.
[Galaxy S III Original Android Development] Yank555:
Either there was a "proper" reboot inbetween, or userspace requested a reboot, but this looks like a shutdown.

The beginning of the log is "interesting" though, filled with :

<6>[ 7330.964718] c0 +++lpa
<6>[ 7331.001906] c0 ---lpa

And that run stopped abruptly, maybe that was when you had the wakeup issue ?

JP.
[Galaxy S III Original Android Development] Yank555:
There were LMK changes, so you indeed need to review your previous settings as I indicated (in red) when I posted the new kernel ;)

Lag can very well be induced if too little free RAM is available at some point ;)

JP.
[Galaxy S III Original Android Development] :
Just re-read first post and changelog, found nothing red about LMK. Did i miss it?

I did found

staging: android: lowmemorykiller: Add config option to support oom_adj values (Arve Hjonnevag)
staging: android: lowmemorykiller: Don't count reserved free memory (Arve Hjonnevag)

in changelog, but ability to change oom priority shouldn't change things this much (From no problems on 3.1e to hanging on 3.1f), neither should not counting reserved free memory.
[Galaxy S III Original Android Development] ezechiele2517:
I don't know Yank, what do you suggest to do ?
[Galaxy S III Original Android Development] Yank555:
I meant here : http://xdaforums.com/showpost.php?p=37504001&postcount=2351 ;)

The one to have an impact is "Don't count reserved free memory", here's the full commit comment :

JP.
[Galaxy S III Original Android Development] :
Well, i thought about that, and assumed that important notes like that one would also make their way into the changelog. My mistake, sorry.
[Galaxy S III Original Android Development] Yank555:
Not much, this is the case each time you entre core0 to lpa this will be logged...

Looks strange that it would go through there that often though.

Will keep an eye on that on my device when it's sleeping.

JP.
[Galaxy S III Original Android Development] Yank555:
You're absolutely correct there, will update it !

JP.

EDIT : Changelog updated.
[Galaxy S III Original Android Development] saad2687:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

Brother please try to fix mhl adapter sound in next release if you have time ... its a request
[Galaxy S III Original Android Development] Yank555:
I have actually bought such a thing, even though I have no need for one, so I will look into this, but I still have not had the chance to go get it at the post office, so patience is a virtue ;)

JP.
[Galaxy S III Original Android Development] enr88:
R: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v3

Ehi Yank any chance to see added feature like control GPU in this spectacular kernel ?? :D

Ciaoo

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] Yank555:
Nothing on the todo in that direction so far, not a priority for me tbh.

At best GPU OC, but I'm no fan of UV, so don't expect any kind of that in here ;)

JP.
[Galaxy S III Original Android Development] enigma1981:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

I'd rather oc than uv... faster is better imo :)

I loved the oc ability in stweaks for siyah, but it was a little too complicated with a million and one options... we know you're a fan of set-and-forget so I'd like to oc with aroma and just leave it at that :)

Swyped from my Galaxy SIII using Tapatalk II
[Galaxy S III Original Android Development] Yank555:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

Maybe some time, but for now I'm digging into the governor and mhl is next on the todo list ;)

JP.

Sent from my custom Sotmax V13 / Yank555.lu SGS3 U7 kernel v3.1g Aroma (Linux 3.0.61) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] PearLRoX:
I goin back to 3.1e..

On 3.1g i got lags and sometimes stuck on the black screen.. And reboots by his self :(
[Galaxy S III Original Android Development] Yank555:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

Logs, please ! ;) I cannot help on just a statement, and next realease will be based on 3.1g, so better we find what's causing issues for you, just going back won't help ;)

Also post /system/etc/init.kernel.sh so at least I know how you setup the kernel.

What ROM ? What Mods ? What LMK settings ? ...

I'm puzzled, as if I was using a different kernel than you ... !? I have no lag, never had a reboot, ever, nor a freeze ...

JP.

Sent from my custom Sotmax V13 / Yank555.lu SGS3 U7 kernel v3.1g Aroma (Linux 3.0.61) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] enigma1981:
PearLRoX, are you on wanamlite? I'm using that with this kernel and I've had a couple of black screen freezes where I've had to hold the power button to reboot, and one spontaneous random reboot... However, when I was on sotmax v14 (as I will be returning to once v15 lands soon...) I had no problems whatsoever, it was slicker than a jellyfish in a bucket of snot! :D
[Galaxy S III Original Android Development] PearLRoX:
Im sorry.. that i post it with no logs. But where can i find that 'logs' ? Also i can't find 'init.kernel.sh' in the map system/etc

If i have a computer i upload the logs. But i have no pc by hand for a week at the moment..

The rom and mods are in my sig. Sotmax v14 and jkay framework.

Its true what you say so my bad.. :) sorry for bothering with my wrong post and questions.

Sotmax since the start.. And with yanks kernel its just perfect. I think its jkay's framework that something to do with it.. (i think)
[Galaxy S III Original Android Development] corrsea:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

Might be, though I have the same setup as you. No issues on this side

ROM Sotmax Ultimate V14

Kernel Yank555.lu-V3.1g
[Galaxy S III Original Android Development] Yank555:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

If you use a root explorer you should be able to find the file : /system/etc/init.kernel.sh ;)

Also, dmesg is a command you type in terminal, like this :

dmesg >/mnt/extSdCard/dmesg.txt

Then you can find the log on your external sd card and it will be called dmesg.txt.

And you can also attach the /proc/last_kmsg, that is a file.

JP.

Sent from my custom Sotmax V13 / Yank555.lu SGS3 U7 kernel v3.1g Aroma (Linux 3.0.61) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] Kung-Fu-Tse:
no reboots here, Im on Omega V40 + JKay v14.9
[Galaxy S III Original Android Development] seinic:
Re: [Kernel][2013/FEB/02][GT-I9300][Samsung JB U7][3.0.61][Aroma] Yank555.lu kernel v

Same for me on settings in my signature...

SGS III with xda premium HD app

ROM: sotmax v14 HD Voice 240dpi

Kernel: Yank555.lu-V3.1g

Swap: 512MB

zRAM: 250MB

Clockwork Mod touch Recovery 6.0.2.7
[Galaxy S III Original Android Development] PearLRoX:
Sotmax V14 240dpi

Jkay deluxe Framework

Yank555 Kernel 3.1g

Upload the files on my dropbox..

http://db.tt/XYJuFo4I
[Galaxy S III Original Android Development] Yank555:
OK, look at the files.

You use "medium" LMK in your settings, please consider using "Stock" LMK, since there have been changes to LMK.

Did you do a normal reboot before you extracted last_kmsg ?

JP.