yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DerTeufel1980:
new sammy 4.2.2 test ;)
[Galaxy S III Original Android Development] alirezaafkar:
Sorry I'm asking!

But, any idea if root access from ADB could be fixed?
[Galaxy S III Original Android Development] DerTeufel1980:
Not yet

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
The exFat code you've just released is Samsung proprietary (even states it in the source code...).

I suggest deleting all binaries you compiled and uploaded and doing this on your Github:

git reset --hard 98309749bca864d54ff132ea5363940569ca193c^

git push --force

Or alternatively a git rebase and remove the picks of the appropriate commits.
[Galaxy S III Original Android Development] DerTeufel1980:
You are right

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
I'll re-upload the sammy 4.2.2 test kernel later

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] psndna88:
new cm anyway has exfat support by vold so no need for them after all
[Galaxy S III Original Android Development] danarama:
I've not noticed this but I recently updated to RootBox (AOSP Combo ROM) and after testing, I have found that when I flash this kernel, it breaks MTP etc.

Essentially what happens is the phoen doesn't detect it's detected to my computer (Tested on 3 separate machines, Win 7, 8 and Ubuntu 13.04). I get the LED but not the notification to choose MTP. The Storage menu doesn't offer this choice as it should.. If I reflash the ROM to get it's stock kernel, the function comes back.

Does anyone else have rootbox and can confirm? Used the first 2 test kernels and also 23.1 and the problem persists.

I'll change ROM before I change kernel and go back to PAC, but I'd rather not. Are there any logs I can provide?

Here is a kmsg whilst plugging in the USB to my Ubuntu machine (Full log attached)

What;s this? I didn't unplug it

<6>[ 915.797712] c0 max77693_irq_thread: interrupt source(0x01)
<6>[ 915.798510] c0 max77693_irq_thread: charger interrupt(0x40)
<6>[ 915.798600] c0 max77693_charger_irq: irq(436)
<7>[ 915.800109] c0 usb: reset
<7>[ 915.800242] c0 usb: android_disconnect con(0), sw(1)
<7>[ 915.800319] c0 usb: android_disconnect force_disconnect
<7>[ 915.800403] c0 usb: android_disconnect schedule_work con(0) sw(1)
<6>[ 915.800861] c0 adb_release
<7>[ 915.800920] c0 usb: usb_gadget_disconnect
<7>[ 915.801002] c0 usb: android_disconnect con(0), sw(1)
<7>[ 915.801077] c0 usb: android_disconnect schedule_work con(0) sw(1)
<7>[ 915.801224] c0 usb: usb_remove_config cdev->config= (null), config=c0ad2c40
<6>[ 915.801605] c0 adb_open
<7>[ 915.801669] c0 usb: android_bind_enabled_functions f:adb
<6>[ 915.801744] c0 adb_bind_config
<7>[ 915.801863] c0 usb: usb_gadget_connect
<7>[ 915.802083] c0 usb: android_work config= (null),connected=0,sw_connected=1
<7>[ 915.802451] c0 usb: reset
<7>[ 915.802543] c0 usb: android_disconnect con(0), sw(0)
<7>[ 915.802623] c0 usb: android_disconnect force_disconnect
<7>[ 915.802711] c0 usb: android_disconnect schedule_work con(0) sw(1)
<7>[ 915.804599] c0 usb: android_work sent uevent USB_STATE=DISCONNECTED
<7>[ 915.804713] c0 usb: android_work config= (null),connected=0,sw_connected=1
<7>[ 915.808789] c0 usb: android_work sent uevent USB_STATE=DISCONNECTED
[Galaxy S III Original Android Development] sherlock5545:
That's what happened to me once rootSU, it was with Paranoid and this kernel. I asked for suggestions and ended up solving by flashing the rom, gapps, rebooting, setting up everything, then back to recovery and flash kernel.

I know it's strange, even you said so at that time, but at least it worked for me.

Sent from my GT-I9300
[Galaxy S III Original Android Development] danarama:
Thanks I'll give it a go
[Galaxy S III Original Android Development] DerTeufel1980:
Try using easy ums to activate MTP. After you reboot once it should be fixed.

I still don't know why this happens...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Unfortunately this didn't make a difference.

This did work, using a similar app to easy UMS.
[Galaxy S III Original Android Development] Teura:
Now that you mention it, when I tested this kernel on Rootbox a week ago, I had the same. First I thought it was my computer as it failed the new device install because it couldn't find any drivers. I manually pointed it to being ADB and then that part worked, but not the storage. I spent an hour trying to figure it out, but then found out that it was because of the phone. Only difference was that for me, I could re-enable MTP via storage menu and it worked just fine after that. What I had was Rootbox 4.1 and version 23.1 of the kernel.
[Galaxy S III Original Android Development] danarama:
It could be a bug in the PA part of the rom as Sherlock had issues with PA. Can't remember having it on PAC though
[Galaxy S III Original Android Development] habylab:
Glad to see you're still helping us old S3 fellows out!
[Galaxy S III Original Android Development] DerTeufel1980:
please someone try again if this kernel boots on sammy 4.2.2
[Galaxy S III Original Android Development] Kemby13:
Has anyone tested 0.25.6 yet?

One question, can i flash this safely on v1.5.3, since it is a "combo" kernel? Srry if it is a dumb question :)
[Galaxy S III Original Android Development] DerTeufel1980:
I would like to know that, too. If it boots I could try looking into the slow speed issue

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
What's 1.5.3?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] brujo55:
why trickster mod app state in 2 plane,drain battery fast?
[Galaxy S III Original Android Development] MuertoKo:
That's goggy kernel version, a dual-boot kernel based on Siyah.

Wish I could help but no 4.2.2 here :(

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Anakha56:
So question where do I download the Samsung (4.1.1) version of this kernel? Going to the main website and clicking on Download --> Devil Kernel I read that this kernel is for CM only, also your first mirror has a malware warning on my end with the second mirror being dead. And if I go back and select the SGS3 it is the CM ROM only. Also first post is an outdated kernel by the look of things? Sorry for the questions.
[Galaxy S III Original Android Development] danarama:
There is no 4.1.1 version.

Touchwiz v 4.1.2

AOSP v 4.2.2
[Galaxy S III Original Android Development] Anakha56:
Sorry I meant 4.1.2. Getting the codes mixed up on my end. Same problem as before, where do I get the download link?
[Galaxy S III Original Android Development] danarama:
There is only one kernel and it works on both. The latest official release is attached to post 1.
[Galaxy S III Original Android Development] DerTeufel1980:
Sorry for confusing you. At my website there's only galaxy s1 kernel

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
What about my sammy 4.2.2 test kernel? I don't wanna loose another day...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Anakha56:
No worries. If I dont ask the question it could scare potential new users away. Thankfully you have a friendly user helping out. :)

Thanks rootSU! Appreciate the help :).

[MENTION=4196889]DerTeufel1980[/MENTION] I will be flashing 4.2.2 soon, just have to wait for the download to finish :/. Once down I will be able to test & report back sadly my country does not have the fastest of Internet speeds :p.
[Galaxy S III Original Android Development] danarama:
I am evil, do not mistake me for being friendly :p
[Galaxy S III Original Android Development] Anakha56:
Well its still booting but it was drawing the Samsung logo frame by frame. Right now "Android is upgrading..." slowly I might add...

[MENTION=2872010]rootSU[/MENTION] Trying to sucker us in are you? :p

*edit*

Yeah no go. Not going into the ROM after the install...
[Galaxy S III Original Android Development] DerTeufel1980:
It does not finish the boot? Or is it just too slow?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
Let me guess, but I think it did boot, then started the upgrading apps but in the end it bootlooped? Happened to me ones testing Siyah on 4.2.2 so might be...

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
Ah. I thought it was working with Siyah... Just very slow.

Could you please get a logcat for me?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Anakha56:
I shall get one for you shortly. Just need to do a few things at work first. If anyone else can get the logcat in the meantime go for it :p.
[Galaxy S III Original Android Development] Anakha56:
Well it booted this time around but wow... It is slower than a 286 booting DOS... :p Just to confirm the adb command it should go something like this:

adb -d logcat>mylogfile.txt
[Galaxy S III Original Android Development] Anakha56:
Okay 2 logcat files one at +-2mb another at a very small size of 984kb. They are raw, unfiltered logs and have quite a lot of errors in them from what I can tell. Hope they help :).
[Galaxy S III Original Android Development] MuertoKo:
Sure, just as yours I guess, for me it didn't boot first time, but did in second try... Or maybe was just too slow and I desperate before leting it boot lol

Anyway I see some gentle people poster logs so I guess you're good to debug!
[Galaxy S III Original Android Development] tolis626:
Sorry if it's a stupid question (I bet it is,I just couldn't find an answer),but is there any point in updating to the latest test kernel (0.25.6 at this time) for us AOSP users?
[Galaxy S III Original Android Development] DerTeufel1980:
No. I just have added sammy initramfs for 4.2.2

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] dmourao:
Hey, [MENTION=4196889]DerTeufel1980[/MENTION]. Ehmmm.. Could you include Westwood (TCP Congestion) on your kernel? It's noticeable faster than the most used ones in SIII (Don't know why Westwood is so underrated here). Thanks!
[Galaxy S III Original Android Development] Kemby13:
Srry, i forgot to mention (was writting 2 different posts in the same time and i missed it).

v1.5.3 is ArchiDroid 4.1.2 rom (XXEMF1), i was wondering if the new build will work normally on that rom as does the Devil 0.23.1?
[Galaxy S III Original Android Development] habylab:
Westwood was awesome on Franco's, would be great to see it added, along with zzmoove 0.5.1b whenever it is possible!
[Galaxy S III Original Android Development] mateusmillian:
Amazing Kernel. Thanks! :laugh:
[Galaxy S III Original Android Development] DerTeufel1980:
Yes it works

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] brujo55:
[MENTION=4196889]DerTeufel1980[/MENTION]

any kernel update for CM SELinux support?

cm merge this.

What is SELinux?

SELinux is a security enhancement to Linux which allows users and administrators more control over access control.

Access can be constrained on such variables as which users and applications can access which resources. These resources may take the form of files. Standard Linux access controls, such as file modes (-rwxr-xr-x) are modifiable by the user and the applications which the user runs. Conversely, SELinux access controls are determined by a policy loaded on the system which may not be changed by careless users or misbehaving applications.

SELinux also adds finer granularity to access controls. Instead of only being able to specify who can read, write or execute a file, for example, SELinux lets you specify who can unlink, append only, move a file and so on. SELinux allows you to specify access to many resources other than files as well, such as network resources and interprocess communication (IPC).
[Galaxy S III Original Android Development] danarama:
Would this negatively affect a remount of the sdcard that I perform via scripts, though?
[Galaxy S III Original Android Development] brujo55:
temasek implement this in your own rom/kernel.

any probrem.i think is fine.
[Galaxy S III Original Android Development] habylab:
Zzmoove 0.6 is out now, sounds good!
[Galaxy S III Original Android Development] dmourao:
Do you have any tunnables or init scripts to share? I'm not a huge fan of zzmoove, but I'm willing to give it a try. Thanks!
[Galaxy S III Original Android Development] pricey2009:
Hey guys, is there an option to dual boot on this kernel?
[Galaxy S III Original Android Development] danarama:
It's coming
[Galaxy S III Original Android Development] nkirk:
Hi OP,

Any plans on adding USB OTG support?

//nkirk
[Galaxy S III Original Android Development] DerTeufel1980:
I never thought about this. Doesn't perseus, which I use as base, already have usb otg?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] brujo55:
any update for today?

zzmoove 0.6

linux 3.0.86
[Galaxy S III Original Android Development] DerTeufel1980:
Maybe already tomorrow :)

Gesendet von meinem SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] brujo55:
nice,cant wait
[Galaxy S III Original Android Development] brujo55:
SELinux support for CM rom?
[Galaxy S III Original Android Development] romeo57:
Is it just me or what.

Whenever i swap my battery or restart my phone, it restarts back.

The phone goes to the homescreen, but restart back.

This happens after i flash this kernel. Don't get me wrong, i LOVE this kernel. The most responsive kernel I've tried so far.

I'm using Wanam v6.8 btw.
[Galaxy S III Original Android Development] danarama:
I'm sorry I don't understand
[Galaxy S III Original Android Development] MuertoKo:
Actually I DO understand what you mean, it's an issue present in Perseus kernel as well, and as this is based on Perseus it may have inherited the issue, it's just that it boots to spaslh screen... and again... and again... and finally it boots normally after 1, 2, 3, or 4 mini-bootlops right?

Reported some times in Perseus, some tried to pull logs as well with no luck though... Anywa, no solve for it for now and I couldn't pull a log myself as it happens random :S (Not every time I switch it off and on happens, most, but not every!)
[Galaxy S III Original Android Development] romeo57:
Yes you are correct.

I've ARHD with Perseus before, and yes i got bootloops too.

I went as far as 2 bootloops. I stopped it by unlocking the phone. Then keep the screen on until everything's loaded.

It only happens when i restart/swap battery though.
[Galaxy S III Original Android Development] Olioaglio:
Teufel, is zzmove 0.6 governor on your Roadmap?

Boeffla users report great over all experience. But i want to stay devilish :D

Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
At first I'll add dual-boot and try to reduce wifi wakelocks

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Olioaglio:
Thanks for response. Dual boot is great news. Never used it since siyah and this has been ages :p take your time. I'm quite happy with current kernel version. To be honest, i love it.

Cheers, Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
ok, here is my dualboot modified kernel. there should not be any issue with it, as it is basically the same as before, just with modified initramfs, to handle dualboot.

to make use of the dualboot functionallity, you also need my dualboot recovery. although i have looked through my scripts very carefully, there could be a typo, which makes something not work.

the worst case would be, that you need to flash another recovery by using odin, but i don't think this really could happen.

if you don't flash/use my dualboot recovery, you still can use this kernel, as you did before.
[Galaxy S III Original Android Development] danarama:
Thanks for this. Will there be a future option to "fake flash" recovery like with siyah? From devil tools for example, so I can use the recovery for dual boot and second rom management but not primary device management?
[Galaxy S III Original Android Development] DerTeufel1980:
First I need to know if everything is working well, before I can look at further improvements.

AFAIK gm has developed this feature within several months.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
I need some feedback :p

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Olioaglio:
Is it really essential to flash the recovery to be able to dual boot? I (and many others I'm pretty sure of) have Philz Recovery and are very happy with it. I thought this feature gets active through an app like it is with ghokanmorals siyah kernel (hijacking recovery is optional, but not necessary).

Olioaglio
[Galaxy S III Original Android Development] DerTeufel1980:
Yes it is. I would not have written it otherwise.

Gesendet von meinem SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
Now it's been almost one day and still no feedback. This is sad :confused:

If no one is interested in this project, I should stop it maybe :mad:

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] alirezaafkar:
I didn't try because of ADB root and I don't want change my recovery!
[Galaxy S III Original Android Development] danarama:
I'm sorry. I am interested but not at the expense of changing my recovery.

If you can tell me the locations/folder structure I need for second rom etc, I will look at manually positioning the rom to test if that's helpful?
[Galaxy S III Original Android Development] tintin1503:
I just flashed the kernel and recovery and when I boot to recovery, there is a message on the main recovery page -"E: unknown volume for path [/data]"

Then I just checked the dual boot menu, option - "create secondary system image" - nothing happens

When I tried another option - "enable mounting of sec. filesystem" - Get the below error messages-

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't mount /cache/recovery/last_log

So if you could explain the steps to be followed in order to dual boot, I'm looking forward to test. Currently on XXEMF6 and will be putting CM nightly from yesterday as second.
[Galaxy S III Original Android Development] DerTeufel1980:
Thank you very much. I take a look what is wrong there.

@ the others: I can't start working on options like "hijack recovery" as long as i don't know if the recovery is working properly.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Olioaglio:
[MENTION=4196889]DerTeufel1980[/MENTION], but that's exactly the point. You don't "have" to hijack recovery in siyah (this is optional) for dual booting feature, because you can start it "once" (rootSU called it fake flash) on next reboot with all options out of gk's app and keep your safe working recovery. If all is going well you can hijack and use it as your main recovery. The benefit in this case is, if there are really problems with the new recovery and/or kernel (bootloop etc.) you are always able to restore your old nandroid backup without odin/triangle problems coming along. I don't want to complain or sound rude or sth. It's just the thought that i always want to have a cute way back to a backup if tests fail. For now I'm trying your latest kernel in single boot configuration. Will keep you updated when there are problems.

Cheers, Olioaglio
[Galaxy S III Original Android Development] danarama:
"Fake flash". Boot into the recovery without flashing it. Not sure if it runs from ram disk or something? Same as ROM manager used to do.

Does ROM manager still offer the fake flash option like it did with cwm 2.x ?

If so I could boot into it that way and test
[Galaxy S III Original Android Development] DerTeufel1980:
I don't know what exactly gm did with the recovery and the fake flash option.

As he never released the sources I have to get it working on my own (instead of just using the precompiled, and outdated recovery which gm has built).

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] danarama:
Because its Sunday, I have some time ;)

Flashed kernel then recovery.

Booted to recovery. Created secondary system.img, received error about mounting data. Enabled mounting of secondary filesystem (errors as reported about /cache/recovery). Flashed my rom.zip as "rom to secondary" then "kernel, modem and recovery".

When booting there was no bootanimation, so bit odd. Eventually got to Nova launcher. It did the whole "you're new, this is how you use nova" thing - which was good. There was no setup wizard but because the rom is a nightly, its hard to pin that on anything.

Anyway rom seemed functional. Reboot from power menu rebooted back to secondary rom. Was bootanimation this time. No "how to use nova" guide so seems to save settings to /data with no issue.

---------- Post added at 01:54 PM ---------- Previous post was at 01:46 PM ----------

If you have anything specific you'd like me to test today whilst I have your recovery flashed, please let me know. As long as it doesn't involve downloading large files as my broadband is rubbish ;)
[Galaxy S III Original Android Development] zodiaxe66:
GM is a wizard and his recovery is still one of the most stable ones,it never fails.even though it's outdated
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, he is. Before he left, he wanted to give me the sources. Hopefully he'll come back one day and give it to me

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] brujo55:
for non second rom kernel,any update to linux 3.0.86 + zzmoove 0.6?
[Galaxy S III Original Android Development] danarama:
He said its exactly the same except dual boot!
[Galaxy S III Original Android Development] DerTeufel1980:
In fact it is linux 3.0.86, but it was a very small update, which should not change anything besides a number ;)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] brujo55:
ok.cant wait next update.:good:
[Galaxy S III Original Android Development] DerTeufel1980:
Please get a logcat and last_kmsg

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] hanspampel:
Ok i get two. I hope thery where right. It was my first time.;)
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks. I'll check it, when I come home

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] troyjamz:
Hey! Just trying your kernel. Everything seemsn to work fine. Is there any way to make this work with stweaks.apk ?
[Galaxy S III Original Android Development] nfsmw_gr:
DerTeufel1980 mentioned earlier that one of the next versions will bring STweaks support,so just wait a bit. :)

If you want to configure it now,use Trickster mod.It's free from google play. ;)
[Galaxy S III Original Android Development] troyjamz:
Awsome. Thanks for the tip!
[Galaxy S III Original Android Development] Eliranu:
Dertefuel I've been using your kernel since my GT I9000 and now for my GT I9300 so far I love it... Ridiculously smooth looking forward for the next builds

Thank you!
[Galaxy S III Original Android Development] Draiden:
Video playback seems to be broken, but very fast and snappy Kernel anyway.
[Galaxy S III Original Android Development] nfsmw_gr:
Confirmed,+1.

It doesn't work properly...

Should we upload a kmsg?

Also something irrelevant with this issue...

Do you plan on adding Zcache, Cleancache and Frontswap support like your i9000 kernel,or this is not possible on the i9300?

Thanks for your work. :)