yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] DerTeufel1980:
Yeah! Baseband issue fixed now :)

New kernel with also added Cm11 support coming soon!

The problem is, you should not have been going back :p

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
new kernel uploaded :)

+ fixed loosing baseband on aosp roms

+ added support for cm11

+ some code cleanup
[Galaxy S III Original Android Development] rascal0pl:
Hi, I want to test it with CM11, but If my AOSP rom is first and sammy's is second - it won't boot?
[Galaxy S III Original Android Development] DerTeufel1980:
the primary rom always boots, as long it is 4.3 or 4.4 (as secondary rom, only cm10.2 is supported currently, but i try to add full support for others sonn)
[Galaxy S III Original Android Development] spoonymoon:
Yeah 4.4 support on my favorite kernel :D

Thank you soo much Devil :)

You are reliable as a rock, so many people have and always will use your roms/kernels on different devices and are so greatfull to you :o

One again thanx :P
[Galaxy S III Original Android Development] DerTeufel1980:
next version is hopefully going to have dualboot of all the supported roms ;)
[Galaxy S III Original Android Development] rascal0pl:
ok, thanks for answer, so in this case I will wait for next version, because I must have access to stock rom (MHL) :)
[Galaxy S III Original Android Development] spoonymoon:
Damm sounds good, no other kernel have this yet :laugh.

Thats amazing and wil surely get a lot off new users, which now only have option to use googy if they want dualboot!!

You rock ;)

Thx :)

------------------------

Newest kernel runs flawless on cm11 v.5

Super super fast on 1600mzh whit zram on 30% and swapp 60% on dalvik even!

Actually there is NO waiting time from tap to open and ready app :eek. And i mean NO waiting!!!!!!

Edit:and baseband all good on cm11 v.5
[Galaxy S III Original Android Development] riso123:
No, sorry, I meant I went back to googy and I DON'T have the error any more.
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks for your feedback :)

I don't really care about how many people are using my kernel. It's much more important, that I know that my kernel isn't just sammy source with linux101 and touchwake :p

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] riso123:
Am I doing something wrong? Flashed over from googy and lost root.

If I Flash back to googy root returns? Do I need to flash the cusyom cwm in your first post too?

---------- Post added at 05:23 PM ---------- Previous post was at 05:10 PM ----------

Additional info - im running the latest wanam custom ROM, if that makes a difference?

---------- Post added at 05:42 PM ---------- Previous post was at 05:23 PM ----------

Never mind, resolved now.
[Galaxy S III Original Android Development] Voxyn:
How did you resolve the issue?
[Galaxy S III Original Android Development] riso123:
Flashed cfroot latest in touch cwm recovery.
[Galaxy S III Original Android Development] serkaon:
Does the devil kernel run on omnirom 4.4?

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] DerTeufel1980:
You need to try it. I am using the cm initramfs. Maybe it does also work for omni

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] serkaon:
İt didn't run on omnirom 4.4. I ask always because i like your kernel too.

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] dollyaja:
No issue and good battery life ? I also on cm11 v5

Errr and which to download,devil or devil2 , :D
[Galaxy S III Original Android Development] Mostafa Wael:
Which kernel should i install for slimkat beta1.9?

I see 2.2.5 and 2.2.5b

Also it is mentioned that 2.2.5b is for omnirom for some testing purposes..

So which one?
[Galaxy S III Original Android Development] lovleshgarg:
I am using 2.2.5b and it works fine for me on slimkat 1.9
[Galaxy S III Original Android Development] xeizo:
No, the last two settings are not available using 2.2.5b and Deviltools 1.1.2, they may be with other combination of versions but not with this combination. On the other hand is this the first combination with long battery life on Temas rom :)

edit. Ah, you mean Devil Kernel Manager on app store, sorry forgot about that one. Yes it's a good alternative of course :)
[Galaxy S III Original Android Development] DerTeufel1980:
I'll check the adb thing. But I can't tell you about the script. After a quick look it seems to be OK and should get executed.

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] Madness.:
Devil, can you update your kernel's busybox? And please implement ABB control. Good job as always Devil :thumbup:

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Original Android Development] Suenu:
I don't know why but no matter what I do, the kernel settings I do with devil tools do not stick.. Once I reboot it's all back to default..
[Galaxy S III Original Android Development] DidyMond:
In DevilTools try to check "Option -> Ignore Kernel Version"
[Galaxy S III Original Android Development] Suenu:
Thanks I'll try that.. I always thought it was a busybox problem
[Galaxy S III Original Android Development] riso123:
Anyone else got issues with latest omni and devil? The ROM just won't boot past splash. :(
[Galaxy S III Original Android Development] DerTeufel1980:
Sorry, I missed deleting 2.2.5, please use the b version of it

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] rascal0pl:
[MENTION=4196889]DerTeufel1980[/MENTION]

Please, tell me.. it is normal that I can't write anything on my SD card - stock rom (permissions error)?

Stock 4.3 + 32GB ExFat formatted card as first rom and CM11 temasek as second rom (on cm11 there is no problem, but I need stock rom, when I want to use my phone as video camera).
[Galaxy S III Original Android Development] DualJoe:
[MENTION=4196889]DerTeufel1980[/MENTION]:

I think i've found the culprit. Any scripts after 10sd_mount are not processed. If i move the scripts to a position earlier than '10sd_mount' they get executed. The script can't be disabled though (reenabled at boot time) so this might be the only workaround for now.

CM11 official nightly on 2nd rom (cm-11-20131228-NIGHTLY-i9300.zip).

Kernel = Devil2-2.2.5b-i9300-DUAL-20131227.zip

Edit:

That doesn't work either:

localhost / # insmod /system/lib/modules/cifs.ko
insmod: can't insert '/system/lib/modules/cifs.ko': invalid module format

Works on Temasek Rom though...

Wait.. doesn't work on Temasek either :p but CIFS does work anyway so i guess you've compiled it statically into the kernel already. :victory:

In case someone wants to bindmount/mirror folders from sdcard1 to sdcard0 for 2nd rom:

#!/system/bin/sh
#/system/bin/sshd
#insmod /system/lib/modules/cifs.ko

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,errors=remount-ro
busybox mount -o bind /storage/sdcardx1/Android/obb /.secondrom/media/obb
busybox mount -o bind /storage/sdcardx1/Android/obb /.secondrom/media/0/Android/obb
busybox mount -o bind /storage/sdcardx1/Android/data /.secondrom/media/0/Android/data
busybox mount -o bind /storage/sdcardx1/Download /.secondrom/media/0/Download
busybox mount -o bind /storage/sdcardx1/DCIM /.secondrom/media/0/DCIM
busybox mount -o remount,ro /

You might want to check your kernel with an SELinux/Enforced rom like official CM11 nightlies yourself. I think your kernel is not running properly (on these roms). Even though i couldn't find anything in SELinux audit logs or /proc/kmsg it looks like the system is partially hardened/locked and thus no new init.d script gets processed.

I'm using a simple init.d test script like this but nothing shows up in logcat (logcat -d |grep initdtest).

#!/system/bin/sh
log -p i -t initdtest "initdtest"

The standard init.d files do work for sure though. I get the '00banner' welcome message in logcat successfully. They are probably part of SELinux policy already but new files seem to be a problem. I'm running 'cm-11-20131228-NIGHTLY-i9300.zip as 2nd rom.
[Galaxy S III Original Android Development] Zwulf:
Works very well on Temasek. :)

CWM is a pleasure. Just tried MultiROM on my Nexus 7 flo... gosh. TWRP is really... gosh... I'm so glad about your dualboot and kernel on my i9300! Thanks for the good work!

Tapagetalkt per Dirty Unicorns 5.0 vom Nexus 7 (flo)
[Galaxy S III Original Android Development] DerTeufel1980:
Can you try deleting all files in init.d besides yours, then execute init.rc, which should lead to execution of init.d as if the device gets booted. Does this work?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DualJoe:
How can i execute init.rc? That's not sh/bash but 'init' script language. If i start 'init' manually it throws errors.

What is the daemon for init.d? Is it installd? Maybe i can invoke that manually.

Edit: 'stop/start installd' doesn't show anything. Maybe other service...
[Galaxy S III Original Android Development] DerTeufel1980:
I am just tapping it within root Explorer. It then asks, if I want to execute it.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DualJoe:
True, but that's probably useless. It very likely just connects it blindly to shell.

What i can do later is repacking the ramdisk without that script. I already tried that but the toolchain i used didn't understand the compression format so i have to fiddle some time to get this started...
[Galaxy S III Original Android Development] Mostafa Wael:
Guys i would like to know maximum stable CPU OC for our i9300..

Is 1920 MHz stable? I tried it before in JB ROMs and it freezes in the same instant i set it...

So what about it know?? Is it stable?

And if i overvolted the 1920 MHz step from 1425mv to 1475mv??

:confused:
[Galaxy S III Original Android Development] coolhof:
Its different for every phone.

Mine is Oc to 1800 Mhz.

Some phone's can not run even on 1600mhz.

You have to test it yourself what's your phone capable is to run.

Ov the mv. doesn't help.
[Galaxy S III Original Android Development] DerTeufel1980:
You could also create a script located before the sdcard one, and then delete the sdcard Script With your one. If it gets deleted you also know initd is working

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DualJoe:
Good idea. :good:

And yes, works! I've put 5 additional custom log scripts beside the standard scripts so there are more than 10 different scripts executed. All show up in logcat.

(Counter evidence) Right before that attempt i accidentally remounted root RW instead of /system and it didn't work (because 10sd_mount wasn't deleted due to still read-only filesystem).

Maybe you just put that script right at the end (zzsd_mount)? It seems to work properly since /mnt/shell/emulated is empty now.

Edit: Tested.. renaming to zz seems to work.

Please also don't forget to update to new SELinux compliant 'ls' binary capable of 'ls -Z' in /sbin.
[Galaxy S III Original Android Development] Erik1805:
Using temasek v26 with latest Devil Kernel. Sometimes the screen gives a flickering. It is a bit hard to explain. Anyone an idea?
[Galaxy S III Original Android Development] francescozanghetta:
issue usb mounting

[MENTION=4196889]DerTeufel1980[/MENTION] Many Thanks for your great work

I have strange issue with your kernels 2-2.2.5/2-2.2.5b: my phone doesn't get mount when I connect it to PC via USB. The phone just starts to charge. Basically my pc recognizes the phone but it fails to install the driver. The phone gets mounted normaly when it is in recovery and download mode. My rom is S4 revolution 4.3 but it happened with I9300XXUGMK6_I9300ITVGMK1_ITV stock.

I tried several kernels (stock MK6, Xpure, GX) and that does not happen so the phone mounts.

I tried everything I could (install new driver, install kies, several PCs, make some search on xda) but with your kernel I get the same result. I also tried to turn off USB debugging but nada.

Could you please help?

Your kernel works very well and I want to keep it

Thanks in advance
[Galaxy S III Original Android Development] DerTeufel1980:
Just turn it on/off with easy ums or similar app. Only needed once. It's going to be fixed in next release

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] xeizo:
A special Happy New Year to DerTeufel as your kernel is pretty good but especially your recovery is awesome! To think of it, now I'm running the latest stock-Samsung XXUGML2 on my device while at the same time I'm also running Temaseks latest V26 build!

It's real easy to switch between the two, fantastic work done!

Only "bad" thing is XXUGML2 seem to have broken WiFi(authentication for WPA2 fails), at least with your or Googy-Anas kernels which are the two I've tried. All else works. At least 3G+ works and I have a liberal data plan, and of course - something has to be broken! WiFi isn't the worst thing, and since it's dual boot it's just to boot into Tema to get fully working WiFi just like that! :D

:good::good::good:
[Galaxy S III Original Android Development] DerTeufel1980:
How old or new is this latest ml2? Maybe Samsung changed something wifi related. Was it working for you on older Samsung roms? Did you try setting static IP instead of using dhcp?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] cba1986:
The problem is if you boot ML2 + devil for the first time the wifi doesn't connect. But if you boot ML2 for the first time with stock kernel, connect to WIFI and then flash Devil, the WIFI works fine.

[MENTION=4196889]DerTeufel1980[/MENTION] i have a little request if possible. Can you make smaller steps for setting the voltages of the CPU?
[Galaxy S III Original Android Development] xeizo:
Thank you very much cba1986, I will try that! I was with the family so I didn't have time to answer myself :)

I wrote a small guide for someone who pm:ed me:

Hi,

Check DerTeufel1980:s Devil2-thread under Original Android Development, all clues are in there, but basically:

(you probably need an sdcard in the sdcard-slot, to host the stock-rom zip, as the operation near fills the 16GB variety of S3. There will be storage space back when the operation is over. Also, you need a nandroid backup of your Tema on the extra sdcard. And you need to already have a dual boot-enabled kernel active on the Tema before you make your nandroid. And you need to have Deviltools installed.)

1. From normal CWM install Devils recovery to replace it.

2. Boot into Devils recovery.

3.Choose to create a second filesystem.

4. Restore your Tema nandroid from the extra sdcard TO the second filesystem(menus are self explanatory).

5. You now have two identical roms to choose to boot between. You will keep Tema on the second filesystem.

6. Choose to wipe THE FIRST filesystem,

7. Install the stock sammy.zip from the external sdcard to the FIRST filesystem.

8. DON'T install an identical dual boot enabled kernel, ie Devil2-kernel, as you use on Tema on the Sammy stock-rom JUST YET. Use the default Sammy kernel for setting things up the first time and then dirtyflash Devil2 at a later occassion otherwise WiFi will be broken!!!!

9. Choose to reboot from the first filesystem.

10. It will take very long the first time, but then you will be met by the normal Sammy-setup. Set it up.

11. Install Deviltools on Sammy as well(but not before you have setup WiFi, and after you have dirtyflashed the Devil2 kernel!), setup your favorite governor etc., from Deviltools you can choose which rom will boot the next time you reboot!

That is pretty much it! Happy dual booting! :)
[Galaxy S III Original Android Development] xeizo:
cba1986:s suggestion worked! Now WiFi is 100% ;) Also, I noticed the PC had a hard time finding the" Devil2/First Time-version", no such problems now. MTP works as usual.

I will probably keep using the Sammy stock kernel on the sammy stock rom for a while to at least see what it is good for, also, the whole point of this operation was to keep one rom as close to stock as possible! Now it IS stock.

That means I have to dual boot through Devils recovery instead, that's not such a big hassle as I'm into recovery all the time flashing new roms ;) :D

Happy New Year again, but it's lot's of fireworks here so I can't hear yah! :p

edit. Hmm, it was a little hard to boot into the second rom again using only the recovery, it defaulted to the first rom. I had to guess I had to install a dual boot kernel on the first rom anyway to get back to number two, and so it was, but this time at least WiFi stayed functional on the Sammy rom. So, Devil2-kernel on both roms, and EVERYTHING is working! :D
[Galaxy S III Original Android Development] DerTeufel1980:
Little late, but: Happy New Year everyone! :)

Could someone please upload latest stock Samsung kernel.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] JustArchi:
http://d-h.st/U6t

Happy new year Devil :).
[Galaxy S III Original Android Development] Mostafa Wael:
hey devil

when i connect the mobile to computer, it doesn't get identified or read, and it says "driver installation failed" what shall i do

i tried SGS3 easy UMS and i didn't manage to get it working....

please help
[Galaxy S III Original Android Development] DerTeufel1980:
Can you please check data/property/persist.sys.usb.config

What's in this file?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] xeizo:
Yes, the kernel has MTP-problems with stock Sammy, while WiFi was sticking after setting it up with a stock kernel so didn't MTP. It works flawless in Temasek rom though ...

And there are quite numerous freezes in stock Sammy, mostly immediately following a reboot, Temasek is stable!

After 3 to 4 of froozen reboots the device seem to work in a semi stable mode for more lengthy periods of time, MTP never shows up though, while there is a connection sound in the PC.
[Galaxy S III Original Android Development] DerTeufel1980:
...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Mostafa Wael:
mtp,adb

that's all what i found written in the file
[Galaxy S III Original Android Development] xeizo:
I don't even have that file ...
[Galaxy S III Original Android Development] DerTeufel1980:
What does (in terminal emulator)

getprop persist.sys.usb.config

return?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] xeizo:
Nothing ...

edit. can connect with Kies Air though, mabe Sammy has started trying to hide USB in latest rom ...
[Galaxy S III Original Android Development] DerTeufel1980:
Please try setprop persist.sys.usb.config mtp,adb

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Mostafa Wael:
please derteufel tell me exactly what i should type in terminal emulator to help you....:D
[Galaxy S III Original Android Development] DerTeufel1980:
That's it

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Mostafa Wael:
that's what I got
[Galaxy S III Original Android Development] xeizo:
Yes, there was nothing, but I created the file in root browser and then issued the command and it got filled with mtp,adb. Still no connection, but now at least it is the source of error messages in Windows like a mtp device that can't be stopped. And Kies(USB) at least starts searching for it, but never finds it ...

---------- Post added at 09:43 PM ---------- Previous post was at 09:36 PM ----------

At last!

I rebooted both PC and Phone, after creating the suggested file as I mentioned above, and now I can browse the device in Windows Explorer as usual and PC-sync works! :D

Thanks, DerTeufel :good::good::good:
[Galaxy S III Original Android Development] Mostafa Wael:
can you please tell me what you did exactly??
[Galaxy S III Original Android Development] DerTeufel1980:
Did you reboot already after using setprop?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] Mostafa Wael:
got it working finally, thx derteufel :)
[Galaxy S III Original Android Development] DerTeufel1980:
update :)

+ merged mk9 source drop

+ fixed usb connection

+ fixed execution of some init.d scripts

+ changed calculation of next freq in pegasusq (based off a commit by stratosk to ondemand governor, which giot merged into linux 3.11)

+ reverted Sec Oom Killer (maybe causeing some random reboots)

+ switched to latest linaro toolchain (4.8.3 of 12/2013)
[Galaxy S III Original Android Development] xeizo:
Great work! Will try! Btw, what's the 1.00GB image (boot.img) created under a /dualboot folder on the external sdcard? Is it essential? I guess so, but if it is not it would be nice to be able to remove it for more storage space ....

edit. the Samsung-camera has shockingly much better IQ than the Google-camera, that alone is worth dual boot, and it saves to the external sdcard ...
[Galaxy S III Original Android Development] DerTeufel1980:
Oh, that's strange. There shouldn't be a 1gb boot.img.... You can delete it. I'll check why it got created.

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] xeizo:
Thank you, I'll do that, booth OS:s seem to work great with your new kernel so far! :D

edit. 2D hw-accelleration and compositing in the gui work much better and are much smoother on the Sammy rom now! Big improvement indeed. No difference on Tema, as it already was smooth. Real nice little kernel what it looks so far :)

Samsung stock experience home screen, running smooth on Devil2-kernel :D
[Galaxy S III Original Android Development] cba1986:
Mk9 is a firmware leak?

---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------

Really smooth indeed.
[Galaxy S III Original Android Development] DerTeufel1980:
Mk9 is latest note2 release

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S III Original Android Development] ddaflorez:
Can anyone share oc/uv settings ? Aint know why cant use my prevous settings used with googy max.... also wondering why gpu voltages are a lot higher than stock :/

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] xeizo:
Sammy stock seems to love these settings:

Scheduler: cfq

Idle mode: idle+lpa

Governor: devilq

200-1400MHz

cpu/gpu-voltage: default

Zswap: 20%

Swappiness: 130%

After playing around with Startup Manager, ES Process Manager and Greenify it is as smooth as Kit Kat, but which much better camera and better sound! DerTeufels new kernel really did the trick! And I have installed ALL Samsung bloat there is, I really wanted the full Samsung Galaxy experience, but 99% of them are disabled/frozen just being there because I can ;)

In Kit Kat you can play around a lot more with the settings, I use zen, aftr+lpa, zzmoove, 400-1400MHz(to cure sound stutter when listening in headphones for lenghty periods of time), default voltage, Zswap 30% and swappiness 60%. Those settings are fine in Kit Kat but doesn't play well with Sammy stock.

edit. I replaced the ext sdcard with a 32GB one, now I have to have at least TWO nandroid backups stored LoL ;)
[Galaxy S III Original Android Development] ddaflorez:
I actually use these on my sammy's 4.3 :

Io sched: row

Governor: devilq 200-1600 mhz

Gpu steps: 266-440-533-640-700

Gpu steps voltages: 925-1000-1050-1075-1100 mv

Cpu voltages: -50 on all frequencys.

Zram and swappines off. But dont see any battery saving :/

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] f0xy:
Hello guys, just a quick one,

Is it right I'm experiencing slow charging after using this kernel and now I'm back to stock omnirom after full wipes etc?

I've used multiple wires/chargers