yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] arter97:
Just got a free track, and reverted SLUB stuffs I had committed.

Now the SLUB memory allocater is identical to mainline Linux 3.0.101.

Hopefully this can help users who are experiencing random reboots.

Git log :

commit 7be127d67f02f33e94aa93ba76dba4f1c199b8ca

Author: arter97 <qkrwngud825@gmail.com>

Date: Sun Jun 15 18:14:04 2014 +0900

slub: remove slub_debug added by Samsung

Mainline Linux 3.0.101 does not has these

commit 974a49ad21673a52161f92c71ae407059ee31452

Author: arter97 <qkrwngud825@gmail.com>

Date: Sun Jun 15 18:12:08 2014 +0900

Revert "mm: Do not stall in synchronous compaction for THP allocations"

This reverts commit 5efd0383e7114b4c357e205b47f23123a7ad3d57.

commit 74975327a1d801df244539dcf2a4622cdcd72549

Author: arter97 <qkrwngud825@gmail.com>

Date: Sun Jun 15 18:11:58 2014 +0900

Revert "hotplug, writeback: don't call writeback_set_ratelimit() too often during hotplug"

This reverts commit 79bcb72f2be88e07fce43628f9b5d1da9415f430.

commit 990923339fb9669bb4d87ce300298240e57fd060

Author: arter97 <qkrwngud825@gmail.com>

Date: Sun Jun 15 18:04:45 2014 +0900

Revert "backport SLUB from Linux 3.3 (by faux123)"
[Galaxy S III Android Development] Darkened_Sky:
hey guys,

I know some of you wanted to install a stock (4.3) rom a second rom, but unfortunately the multi-boot.zip cannot handle it for now.

as a quite simple workaround I modified the update-script of justarchi's complete stock sammy 4.3 rom (as it was the only sammy 4.3 rom I have found that does not use aroma), so that it does get directly installed in /data/arter97_secondrom/system without the need to flash the multiboot.zip before. And I thought I share it with you. In addition I deleted the boot.img in the update.zip so that it does not flash the stock kernel.

as always make a nandroid backup before, you are responsible yourself what your doing with your phone ;)

If I have enough time somewhen I'll also try it with an aroma rom.

Hope it is ok to post it here :angel:

p.s.: delete the .txt ending before you insert the updater-script into the update.zip :laugh:
[Galaxy S III Android Development] rascal0pl:
could you do the same thing for archiport 4.4? Or it is just dir name matter?
[Galaxy S III Android Development] Darkened_Sky:
its easy to do, simply look at the update_script I've made.

just make sure that instead of /system /data is mounted and replace all mentions of "/system" with "/data/arter97_secondrom/system" and delete the line in which the kernel is flashed, and delete the boot.img ithe update.zip

in theory the update script I've modified should also work with archiport. but make a nandroid before you try it.
[Galaxy S III Android Development] rascal0pl:
ok thanks I wil make it, but why in your script there is:

delete_recursive("/system");

instead of

delete_recursive("/data/arter97_secondrom/system");

?

delete_recursive("/system"); will rather wipe my first rom /system partition, I think?
[Galaxy S III Android Development] Darkened_Sky:
oh yes you are right thanks, have overseen it... but strange i flashed it and my system of primary is still there, maybe because it wasn't mounted puuuuuh :D

but i will correct it and reupload it
[Galaxy S III Android Development] rascal0pl:
Anyway, it was pointless in my case, because archiport doesn't support f2fs :( But 4.3 is working fine, All I need is samsung camera, so it doesn't matter if it is 4.3 or 4.4. For daily use - temasek's rom FTW.
[Galaxy S III Android Development] habylab:
Great work, really appreciate this.

I must say, having huge camera issues compared to the work around googy had on his kernel. Camera is not showing for a bit, freezing etc.
[Galaxy S III Android Development] szotaa:
Well then Im going to use your kernel as my daily driver on cm10.2. F2FS + CM10.2 Official stable + your kernel will make a perfect combo. Big thanks mate.
[Galaxy S III Android Development] arter97:
Haven't personally tested with CyanogenMod 10.2 for a long time...

If you experience any sort of issues, please let me know :)

We can go figure and sort things out :D
[Galaxy S III Android Development] cba1986:
Very nice and informative reading. But it contradict himself with the last sentence:

Heat is one of the majors problem of the S3 while playing. At least for me.
[Galaxy S III Android Development] arter97:
That saying is not from the same person.

As the first sentence says "This a copy of a post from a chip designer"
[Galaxy S III Android Development] mrjoy:
Very annoying problem, whenever i'm flashing this kernel on my GT-I9300 with SOKP kitkat rom, after successful flashing,it doesn't shows the kernel in device's configuration.... Whats wrong with me. Even aTweaks says kernel not found
[Galaxy S III Android Development] arter97:
If you don't see "arter97" from the Kernel version, the kernel is not installed properly.

Try again with a different recovery.
[Galaxy S III Android Development] mrjoy:
Yes according to dev it is untested but its close to other Korean configuration & should work on this device too even i think other using too on same device. And i'm using latest philz recovery though.
[Galaxy S III Android Development] szotaa:
[MENTION=4898097]arter97[/MENTION] just to notice you, after I download arter97-kernel-2.0.zip Google Chrome on desktop marks it as a spyware and instantly removes it from my computer. I bet it's a google chrome mistake but please make sure there was no attacks on your website.

https://support.google.com/webmasters/answer/3258249?hl=en
[Galaxy S III Android Development] arter97:
Have you saw "flashing GT-I9300 boot.img" message while installing?
[Galaxy S III Android Development] glockaki:
With latest philz on a samy based rom didnt instaled.it still showing boeflla my previus kernel.wich i uninstalled before installation process...

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Android Development] arter97:
My Chrome 35 downloads well without any issues.. :(
[Galaxy S III Android Development] gieffe22:
i tried it on 4.3 stock rom... it works good but strangly with pegasusq the animations cause big lags...on zzmove less but still are present some strange lags...
[Galaxy S III Android Development] arter97:
Have you tweaked anything besides governor from aTweaks?
[Galaxy S III Android Development] davidwar:
Sorry for Offtopic.

Is there a walkthrough for dual boot whit this kernel? (I wan´t to try new 4.4 Sammy port with my 4.3 stock)

Thanks
[Galaxy S III Android Development] gieffe22:
no...i left all stock...i try before all stock...next only changed governor to zzmove...but still there re these strange lags on animations...the phone is fast but lags...
[Galaxy S III Android Development] glockaki:
Doesnt install on my phone.and i dont want to change recovery.maybe some other time.

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Android Development] arter97:
I think what the OP says is quite enough. Try reading it again thoroughly.
[Galaxy S III Android Development] arter97:
That's unfortunate... Try setting the minimum clock to 400MHz and see if it helps
[Galaxy S III Android Development] arter97:
Sorry for the inconvenience.. I'll test it again with PhilZ
[Galaxy S III Android Development] spoonymoon:
New kernel great work :)

Will it boot on aosp roms? Nothing in op about it so i quess not!

Thanks a lot dev:)
[Galaxy S III Android Development] arter97:
Hopefully, again, that slub reverting can help it...
[Galaxy S III Android Development] arter97:
Version 2.1.2 is up.

Please try refreshing the page before you report there isn't 2.1.2 uploaded.
[Galaxy S III Android Development] psndna88:
hey im trying to get knockon touchwake to work on note 2 using mms152_ts.c but the double tap isnt working only single tap works...

Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v98 (4.4.3) + AGNi pureCM v2.8.0 kernel
[Galaxy S III Android Development] arter97:
My code is only specific to mms_ts used by i9300. Have no idea how N7100 goes..

Go try porting dt2w. It'll be easier.
[Galaxy S III Android Development] psndna88:
i found ur modifications to mms152_ts.c regarding knockon similar mms_ts but they didnt work..

Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v98 (4.4.3) + AGNi pureCM v2.8.0 kernel
[Galaxy S III Android Development] arter97:
My Knock-On code is very short. Go try to understand it, and re-write your own on the N7100.

I cannot give you much help on this..
[Galaxy S III Android Development] psndna88:
yes im done that already,

finding why it doesnt work..

for cm where sec_switch_max77693 muic in mach-exynos is not present , ive removed part of code for charging detection ;)

plus without device its difficult..

Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v98 (4.4.3) + AGNi pureCM v2.8.0 kernel
[Galaxy S III Android Development] arter97:
Yes, charging stuffs are unnecessary.

Just go with dt2w. It has several advantages such as lower power consumption(it doesn't hold any wakelocks).
[Galaxy S III Android Development] psndna88:
any commit for it u can quickly link to me ?

Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v98 (4.4.3) + AGNi pureCM v2.8.0 kernel
[Galaxy S III Android Development] arter97:
https://github.com/showp1984/bricked-hammerhead/commits/master/drivers/input
[Galaxy S III Android Development] arter97:
Oh my.. I now got a log from a Korean user [MENTION=842274]chk[/MENTION]469

Seems like UKSM is causing random reboots(which is turned on during charge by default)

(Added in version 2.1)

Even though it's nice, I'm gonna kill it in the next release.
[Galaxy S III Android Development] habylab:
Oh okay! I'll turn it off! Maybe just a quick release to prevent hysteria?

I guess memory optimisations you have in place will make up for it.
[Galaxy S III Android Development] trein91:
[MENTION=4898097]arter97[/MENTION] SetCPU stops working on each boot. Probably because atweaks is kicking in after a small delay on boot completion. (hence the conflict) Is there any way to fix this? Other than manually starting SetCPU all the time when you reboot.

Hope you don't mind: Possible to add in Wolfson controls? I need it solely to adjust mic sensitivity.

Sent from my GT-I9300
[Galaxy S III Android Development] arhant:
kernel is good..

but after using this kernel i feel certain lags and phone hangs a lot..

and ram usage is also very high as compared to other kernels..

can you please include LMK settings in next version..

and look into lags..

UKSM is disabled..!
[Galaxy S III Android Development] habylab:
My device seems to either forget the governor, or set hotplug setting to 1 and default profile for zzmoove. Odd!

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] pricey2009:
Check your init.d scripts..
[Galaxy S III Android Development] DualJoe:
Just do it manually via init.d.

#!/system/bin/sh
(
for i in `seq 1 60`; do
if [ "$(busybox ls -A /storage/sdcard1)" ]; then
busybox mount -o remount,rw /
mkdir /storage/sdcardx1
busybox mount -t vfat /dev/block/mmcblk1p1 /storage/sdcardx1 -o rw,relatime,fmask=0111,dmask=0000,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
busybox mount -o bind /storage/sdcardx1/Android/obb /data/media/obb
busybox mount -o bind /storage/sdcardx1/Android/data /data/media/0/Android/data
busybox mount -o bind /storage/sdcardx1/Download /data/media/0/Download
busybox mount -o bind /storage/sdcardx1/DCIM /data/media/0/DCIM
busybox mount -o remount,ro /
break
else
sleep 2
fi
done
) &
[Galaxy S III Android Development] Mostafa Wael:
check this :)

http://xdaforums.com/showpost.php?p=53405865&postcount=7424
[Galaxy S III Android Development] rascal0pl:
I tried it before. It does nothing like foldermount ;)
[Galaxy S III Android Development] DualJoe:
Because you're very likely not on vfat. Fix it yourself or just ignore it. I don't have any other formats so i cannot help any further.
[Galaxy S III Android Development] rascal0pl:
You are wrong. My ext sd is formatted as fat32, so mountig with vfat should work, but it doesn't.
[Galaxy S III Android Development] DualJoe:
Then put an exec &> /data/initd.txt before it and check the errors after bootup.
[Galaxy S III Android Development] arter97:
Sorry but I want to leave aTweaks as the only kernel controller for this.

I'll have another look at alternative sound engine when I'm free.
[Galaxy S III Android Development] arter97:
If storages are not mounted by vold, apps will not be able to read it.

Also, sdcardfs cannot handle bind mounted directory.
[Galaxy S III Android Development] arter97:
A reason to release 2.1.3 soon, even if you disable UKSM, it'll still cause panics.
[Galaxy S III Android Development] rascal0pl:
It works exactly like foldermount - mounted directory becomes 0byte file. Are you sure that you are on this kernel? In your signature I see, that you are using devil kernel, so, when I used devil, mouting was working well.
[Galaxy S III Android Development] DualJoe:
True, fixed.

Its just a heads up. Maybe you need to change mount options or sth, idk. I would verify the commands manually in local shell during runtime first.
[Galaxy S III Android Development] arter97:
towelroot is very scary... ( http://towelroot.com/ )

Long-term Linux kernel has that vulnerability fixed but not our Linux 3.0.

I got you covered, next version 2.1.3 also fixes CVE-2014-3153.

This means some random apps you'd install will not be able to gain unauthorized root access using towelroot exploit.

commit a083fd5d717818597e41615b7691f58ba6a63ac9

Author: Thomas Gleixner <tglx@linutronix.de>

Date: Tue Jun 3 12:27:06 2014 +0000

futex: forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)

If uaddr == uaddr2, then we have broken the rule of only requeueing from

a non-pi futex to a pi futex with this call. If we attempt this, then

dangling pointers may be left for rt_waiter resulting in an exploitable

condition.

This change brings futex_requeue() in line with futex_wait_requeue_pi()

which performs the same check as per commit 6f7b0a2a5c0f ("futex: Forbid

uaddr == uaddr2 in futex_wait_requeue_pi()")

[ tglx: Compare the resulting keys as well, as uaddrs might be

different depending on the mapping ]

Fixes CVE-2014-3153.

Reported-by: Pinkie Pie

Signed-off-by: Will Drewry <wad@chromium.org>

Signed-off-by: Kees Cook <keescook@chromium.org>

Cc: stable@vger.kernel.org

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Reviewed-by: Darren Hart <dvhart@linux.intel.com>

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[Galaxy S III Android Development] arter97:
Version 2.1.3 is now up.

Should fix majority of kernel panics(random reboots).
[Galaxy S III Android Development] trein91:
Btw. If I want to save the kernel settings file. Is it only the "default.profile" one in data/.arter97?

Sent from my Galaxy S3
[Galaxy S III Android Development] arter97:
Yes, but it's highly not recommended.
[Galaxy S III Android Development] trein91:
I was wondering. How does one mount system as rw? I tried numerous apps on the play store but they failed. Apparently it was due to some write protection introduced by KitKat? I'm on temasek tom. Wanting to install an app via "system app installer" ie to install it as a system app.

Sent from my Galaxy S3
[Galaxy S III Android Development] arter97:
I'm not sure if that issue is related to my kernel..

I use

adb root && adb remount
[Galaxy S III Android Development] trein91:
Yeah thought I'd ask you since some people say custom kernels might restore write permissions somehow. Trying to refrain dabbling with adb since I've no experience in it really. Just refraining from that

Sent from my Galaxy S3
[Galaxy S III Android Development] habylab:
Scary stuff... Thank you!

No need to wipe cache + dalvik? Also, do the settings can reset?
[Galaxy S III Android Development] seroesh:
how necessary is conversion from ext4 to f2fs for dual boot? as I just know the flashing and if something goes wrong, I would have no clue how to fix.. ?
[Galaxy S III Android Development] DualJoe:
Apps are in their own (local) mountspace. Changes/remounts by them will not affect global mountspace (eg. other apps). Exceptions are 'adb remount' or SuperSU (su --mount-master -c mount -o remount,rw /system).

So, either remount globally or use one and the same app to do both jobs (remount, working in /system) like 'Root Explorer' or 'ES File Explorer' (should auto remount). To install a system app move the apk from /data/app to /system/app with one of the 'explorers' mentioned. No need for dedicated 3rd party apps.
[Galaxy S III Android Development] trein91:
Issue is I can't install the app as a user app. If I could I would have done that already. Apparently the only way to install this particular app is to install it as a system app directly. Copying the installation file to system app folder won't do anything.

Sent from my Galaxy S3
[Galaxy S III Android Development] psndna88:
terminal commands:

su
mount -o rw,remount /system

Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v98 (4.4.3) + AGNi pureCM v2.8.0 kernel
[Galaxy S III Android Development] arter97:
Dalvik caches are never related to kernel, so there's no need.

aTweaks settings get reset every time when you flash the kernel. This is to make sure aTweaks configuration does not get screwed all over.
[Galaxy S III Android Development] arter97:
2nd ROM always follows up 1st ROM's file system.
[Galaxy S III Android Development] seroesh:
and is it safe for a newbie like me to make the conversion? I mean - I read this thread and I have no clue how to use terminal or adb etc. but I do want to speed up my phone's flashing..

and one more question, when the conversion is made .. does it format the whole sdcard or just the device part? Like, when I format /system when I flash a new rom, the folder outside device (where the rom is installed) stay the same.. where the apps data is stored.. so basically what I'm asking is when I'm converting from ext4 to f2fs, will it format the entire phone memory or just the part where the rom is flashed and other root data is stored.

P.S.: Sorry for a dumb question and the dumb way I asked as I don't know much about what to call the part where the rom is installed.
[Galaxy S III Android Development] arter97:
If you're not gonna stick with my kernel(and go travel around the XDA and flashing another kernels), I recommend you not to switch to f2fs.

Your phone's entire data except system stuffs are going to format and switch to f2fs.
[Galaxy S III Android Development] seroesh:
I have a habit of sticking with things :D like it has been 6-8 months, I have been using Beoffla kernel with Tema's rom, but now I'm going to go to ArchiDroid Sammy and your kernel, but what I'm trying to ask is I'm not tech savy, just know how to flash a kernel and ROM, the basic stuff. I like the fact that you've optimized your kernel to a default setting so that a person like me who doesn't know much wouldn't have to do the hard work, although I can go by following tutorial and doing things right.

How much of a difference is between ext4 and f2fs? and if once I convert to f2fs, is it impossible to revert to any other kernel which isn't f2fs supported? and does all roms support f2fs or only a few?
[Galaxy S III Android Development] trein91:
Not that much of a difference imo. Other kernels that don't explicitly support f2fs won't work imo. Tried it

Sent from my Galaxy S3
[Galaxy S III Android Development] trein91:
[MENTION=4898097]arter97[/MENTION]

Am I doing it right? I checked with solid Explorer but it still shows /system as having only read permissions.

Sent from my Galaxy S3
[Galaxy S III Android Development] DualJoe:
What app do you try to install? Proprietary framework related files do not work by design (like Samsung/Touchwiz apps to AOSP/CM).

And yes, remounting doesn't work that way (like i mentioned before). Use 'adb remount' or remount in solid explorer itself.
[Galaxy S III Android Development] trein91:
Holotimus. App fails to install. Dev has no clue. His other themes work for me. Someone in that thread said he had the same issue installing, and managed to install it using "system app installer". Problem is my /system folder is read only. Which is why I can't use "system app installer" to install it directly as a system app.

Sent from my Galaxy S3
[Galaxy S III Android Development] DualJoe:
Try 'logcat -d > /sdcard/logcat.txt' right after (unsuccessful) installation. A more detailed error should be there.

Edit: Holotimus installation works here.

If you install it as system app (copy to /system/app) you have to reboot. Also wipe dalvik cache in recovery once from recovery.

Logcat should tell more...
[Galaxy S III Android Development] trein91:
https://mega.co.nz/#!9QsVVIzS!-D7UDSeg1ufDEHzW5bM-5n-Fps8BHpxoPt7exHClRm4

Thought I'd send you it too.

Sent from my Galaxy S3
[Galaxy S III Android Development] DualJoe:
MEGA is crap. Doesn't work with Chromium or Firefox. Just zip/rar and attach it to the post or use reliable one click hoster like zippyshare, mediafire or similar.
[Galaxy S III Android Development] trein91:
https://www.mediafire.com/?y505h0asjb1puv1
[Galaxy S III Android Development] DualJoe:
[MENTION=4690065]trein91[/MENTION]:

1) That xposed/masterkeydualfix shouldn't be necessary on Temasek rom. Its just for older roms and throws errors on your system anyway. This could be the culprit for your installation problem in the first place. Deactivate/uninstall it first.

2) It looks like the app is partially installed already. The system tries to update it but cannot succeed successfully.

I/PackageManager( 2516): Package com.tung91.holotimus codePath changed from /data/app/com.tung91.holotimus-2.apk to /data/app/com.tung91.holotimus-1.apk; Retaining data and using new
I/PackageManager( 2516): Running dexopt on: com.tung91.holotimus
D/dalvikvm(12335): DexOpt: load 40ms, verify+opt 131ms, 1031460 bytes
I/ActivityManager( 2516): Force stopping com.tung91.holotimus appid=10203 user=-1: update pkg

It doesn't look like a kernel issue but rather like an unsuccessful previous installation that left dead files blocking a new installation. Uninstall all parts by removing these files/folders, reboot and try installation again:

/data/app/com.tung91.holotimus-*.apk
/data/data/com.tung91.holotimus-*
/data/dalvik-cache/data@app@com.tung91.holotimus-*@classes.dex
/data/dalvik-cache/system@app@com.tung91.holotimus-*@classes.dex
[Galaxy S III Android Development] trein91:
Removed master key. Deleted all those files. Rebooted. Still doesn't install. Fml. I'll repost another logcat soon. Here it is

http://www.mediafire.com/view/?9u6wt0k4xjv0x0w

Sent from my Galaxy S3
[Galaxy S III Android Development] DualJoe:
Then i don't know. It still shows double apks (1,2) in your logs. Maybe that's completely fine but i don't have that on my side during installation and can't tell anything about it.

Last attempt might be uninstalling Google Camera and its gallery (com.google.android.gallery3d). Its AAPT's last processing attempt before it crashes and breaks installation.
[Galaxy S III Android Development] xmendp:
some one can help me. how can i seting with ver 2.1.3.? i 'm using sensation v3.3..:) thanks in advance
[Galaxy S III Android Development] trein91:
Didn't work too. ;( does my storage being F2fs change anything? At first I thought it might be a rom issue but other temasek users managed to install it.

Sent from my Galaxy S3
[Galaxy S III Android Development] arter97:
Guys, please post something related to this thread, this kernel.

This is not a troubleshooting thread for other ROMs or kernels.

[MENTION=4690065]trein91[/MENTION]
[Galaxy S III Android Development] justforreply:
Boot loop 2nd rom

If I have a boot loop in 2nd rom in boot loop have any way to wipe it data, flash another rom or reboot in 1st rom ?
[Galaxy S III Android Development] Darkened_Sky:
reflash kernel then the next restart will be to 1st rom. there you can wipe 2nd roms data in aswitch app