yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Moster2:
We were already talking about that yesterday. The kernel somehow interfers with the rom and/or supersu, so that you cant properly access the /system/ partition(temasek said its busybox related). Only happens with kernels thats modify ramfs.

http://xdaforums.com/showpost.php?p=47890977&postcount=250

You even liked my post :D
[Galaxy S III Original Android Development] Scarface1991:
Works flawless with Temasek's V10 ROM. Everything is fast and fluid :good:

Thank you for this great Kernel :)
[Galaxy S III Original Android Development] temasek:
Not exactly

Read this commit and it's comments from rovo

http://review.cyanogenmod.org/#/c/54659/

If i were to revert the mentioned commit in rom source system/core, there may leak a hole for root exploits.
[Galaxy S III Original Android Development] DerTeufel1980:
And with stock kernel /initramfs this commit doesn't hurt?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] BradleyR2010:
Devil Kernel Manager

I need a few testers for the new version of my app, its almost complete only thing missing is GPU and CPU Voltages Control, but i wanna make sure everything is working fine before the public release, just PM me and ill send you the link.
[Galaxy S III Original Android Development] mhb92:
i could be a tester for u.. :P

what settings is best for zram on devil kernel app... can u give me a hint :)
[Galaxy S III Original Android Development] bett3rthan:
I want too the settings for zram, but can someone explain to me what help is that zram? I read a whole forum about that, but in a few words, what`s the benefit?
[Galaxy S III Original Android Development] -MaD-:
Nice to read... I used your app on my S1! Hope to see it soon on the S3!
[Galaxy S III Original Android Development] spoonymoon:
Rofl :eek:
[Galaxy S III Original Android Development] DerTeufel1980:
New gpu control working well? Resetting of custom voltages is fixed as well, isn't it?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DirkStorck:
Hi. Just have flashed 1.7.0 because I have noticed that my CPU was running wild with the previous version...now I have connected my phone to my PC and it showed that a new hardware was found "SAMSUNG_device". The search for new drivers didn't find anything although I already used adb with this PC....

Any advice please! :)

Thank you!
[Galaxy S III Original Android Development] coolhof:
Yes its working for me.:thumbup:

Kernel 1.7.0

Deviltools 1.0.1
[Galaxy S III Original Android Development] DerTeufel1980:
I didn't change anything. Is there any issue, besides windows complaining?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DirkStorck:
No....everything else is working fine...my CPU usage is normal again gladly :)

---------- Post added at 11:00 AM ---------- Previous post was at 10:13 AM ----------

I have uninstalled the Samsung drivers, rebooted my PC, installed most recent drivers and flashed googy's last kernel.

After I have conntected my phone to my PC it was recogniced and I could use adb. The only driver that could not be found was "SAMSUNG Mobile MTP Device Driver"

Now I gonna flash your latest kernel again and see if it works :)

EDIT: After I have flashed your kernel I have the same problem again...phone does not get recogniced. :( :(
[Galaxy S III Original Android Development] noobandroid:
I still havent got a solid answer on whether the kernel dual boot as

slim bean 4.3 build 2 as main

a samsung rom as second

must use the recovery too? it seems there are a large amount of steps to do it correctly
[Galaxy S III Original Android Development] duttyend:
Hello friend,

Thank you for the new version, but unfortunately GPU voltage resets again for me (CM10.2) after a while...
[Galaxy S III Original Android Development] DerTeufel1980:
On Samsung Rom? Isn't there a dial code to get into storage mode settings?

you need to use the recovery, yes.

There aren't too many steps compared to just single boot.

You just need to create secondary system partition at first.

Oh, that's strange. I'll check the code again. You didn't change the gpu freq when this happened?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DirkStorck:
I am using the latest temasek CM11 ROM....even after I have switched to massstorage mode I could not see the drive :confused:

For testing I have flashed the nandroid as 1st ROM and flashed "boeffla-kernel-CM-2.1-beta1a-cm11.0-r3p2"....everything about detecting my device and MTP is working fine :confused:

I can't use googy's current kernel because my CPU is going crazy like with the version before your current 1.7.0 version

Will stay with this combination a bit....:(

sad this is I wanted to have Sammy and CM because the Sammy camera is much better :crying:
[Galaxy S III Original Android Development] noobandroid:
thanks for the answer, but can i use just about any rom as 2nd rom?
[Galaxy S III Original Android Development] duttyend:
No, I didn't change any frequency...

Thanks for your help :)
[Galaxy S III Original Android Development] DerTeufel1980:
Every 4.3 or 4.4 rom should be working. Obviously not every combination has been tested yet, but I can't remember anyone mentioned a non working combination

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] spoonymoon:
Everything sticks after boot - but not gpu voltages , there back at default after reboot!

on cm11 v.10

gonna flash a second rom and tjek there now :rolleyes:

edit: yes think you´re right because after setting another value in gpu, and just exiting deviltools and re-enter it resets values again !

edit: Great, then i suppose everything is working as supposed to (another request added) :victory:
[Galaxy S III Original Android Development] DerTeufel1980:
No need to re-check. Sounds like a bug of deviltools

Edit: I think the voltages never really get changed by deviltools. It just displays the new setting, but the according file always stays untouched...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rascal0pl:
Hi, is dualboot working like in googy's kernel? Is your recovery different (dual boot methods or something) from googy's one (can I flash rom update in googy's recovery [exfat support] using your kernel) ? Can I flash this kernel if I already have 2 roms (without data loss)?
[Galaxy S III Original Android Development] DerTeufel1980:
Yes, I am using the same way gokhanmoral was using. My recovery is different, because I had to code it myself (please read the faq on page 1).

Why should you want to flash the update by using another recovery? And what do you mean with exfat support? Mine has support for it, don't know about gm recovery.

Yes, you just can flash the kernel, if you already have dualboot

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DerTeufel1980:
again update :)
[Galaxy S III Original Android Development] andrewwright:
Running nice with v12 cm11 unofficial build.
[Galaxy S III Original Android Development] rascal0pl:
From "DerTeufel1980 Dual-Boot FAQ"

;)

But thanks for answer, I will flash it tommorow :)
[Galaxy S III Original Android Development] DerTeufel1980:
Ah, that's not my own faq. It meanwhile supports exfat

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] spoonymoon:
ah thats why latest version(s) seemed slower in overall >

Changelog:

29.11.2013 part 2:

+ fixed apllying of custom gpu voltage

+ removed intellyplug driver (wasn't working properly, consumed much battery, made boot up take longer and it was unstable)

once again you did an excellent job Devil, settings in gpu voltage stick now, among all others :cool:

and it has always been an extremely fast kernel but i swear this new baby is a *runner* hot d... nearly getting my fingers burnt on screen, apps FLY :victory: even whit zram disabled on dalvik 1600mzh on sio and pegasus :D

6626 in quadrant :angel:

thx a mill*******
[Galaxy S III Original Android Development] dollyaja:
whats the default read ahead size here, i cant find the setting on devils tools
[Galaxy S III Original Android Development] DirkStorck:
How can I use my 2nd ROM as my 1st ROM ?

I have made a backup of my 2n and restored it as 1st ROM but now is going crazy...average CPU usage of 60 -100% and "native processes" most of it?

Thank you!
[Galaxy S III Original Android Development] DerTeufel1980:
That's the way to go. Gokhanmoral uses the same method, just automated.

You could try installing it as primary rom the normal way, and then restore data from your backup

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Lear95:
Dual boot works perfectly.. But I have no root access on secondary rom.. Plus the external sd card ia blocked.. Is it supposed to be like this? If not.. How can I restore root on secondary rom and how can I access ext sd?
[Galaxy S III Original Android Development] DirkStorck:
You mean wipe 1st ROM, flash the ROM and only restore data partition ?!? And than I have all my apps and settings back ? :confused:
[Galaxy S III Original Android Development] DerTeufel1980:
You may also need to reflash gapps.

All your settings are at /data

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] DirkStorck:
THANK YOU! That worked :laugh: :highfive:
[Galaxy S III Original Android Development] andrewwright:
My benchmark score. They are a waste of time though. :thumbup:
[Galaxy S III Original Android Development] DirkStorck:
What is that "intellyplug driver" ?!?

Thank you! :)
[Galaxy S III Original Android Development] Jaskaran498:
Installing this kernel on omni makes my statusbar disappear (latest version rom).
[Galaxy S III Original Android Development] DerTeufel1980:
It was meant to enable hotplug for cpu governors without this function (ie interactive)

I'd say this is impossible

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rezapatel:
Seems to be working great except for zram showing as available memory, but it never gets used. Used memory off it always shows 0.

I am on CM11 Temasek v12.

Thanks

---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------

---------- Post added at 10:44 PM ---------- Previous post was at 10:21 PM ----------

Update:

Seems to be working but doesn't go beyond the numbers on the new screenshot.

---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------

Btw, zram set to 50 percent and swappiness to 80. Thanks for the help in advance.
[Galaxy S III Original Android Development] DerTeufel1980:
What's your uptime? It's not full in the beginning.... And best is it never gets full 100%

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rezapatel:
Interesting, I was never aware of that :) uptime on last screenshots was hardly a few mins on your kernel. It's been around an hour now and it has increased to almost 1 / 4th.
[Galaxy S III Original Android Development] DerTeufel1980:
Seems to be working fine then. Interesting to see how your device/zram behaves after an uptime of 1 day and more

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] duttyend:
Thank you very much !!! I confirm gpu voltage is sticking with 1.8.0 on CM10.2 ! :)
[Galaxy S III Original Android Development] ArtoD2:
What I'm doing wrong? I have Devil 1.8 and latest recovery. I have stock 4.3 (mj9) + xposed modules.

1. I boot to recovery

2. Create dualboot from menu

2.1 wipe 2nd Rom, just to make sure

3. Flash temasek CM11 v12 as a second ROM

4. Try to boot to 1st ROM (tw), I get the CM boot animation and stuck there.. there seems to be no MJ9 anywhere...

At first I thought that I had just made wrong choice, but I restored the nandroid for mj9 and tried these steps again, with same results...

Am I missing something? Would it be possible that googys dualboot (long ago removed) could cause problems?

Appreciate the help!
[Galaxy S III Original Android Development] RichMD:
I don't use exfat but I assume that DerTeufel has modified the recovery to support it so what I had in the FAQ is no longer correct - correct? I haven't updated the FAQ thread in a long time because I have been very busy with work, etc. the last couple of months.

[MENTION=1431324]rascal0pl[/MENTION] I posted this above since I saw a "post quote" but didn't realize it was for the Galaxy SIII which I never created an FAQ for...
[Galaxy S III Original Android Development] Mostafa Wael:
any luck to get devil kernel manager working?

also will inteliplug get included in next versions if it is stable enough?

thank you
[Galaxy S III Original Android Development] psyntific:
Thanks for this mate... works perfectly
[Galaxy S III Original Android Development] Jaskaran498:
ok, just figured it out today.

Its not the kernel. Actually this problem started right after i installed the kernel so i thought....

But anyways... i tested other kernels and result is same and it seems only i am facing this prob. Thats very strange...

but the room is ok. Thanks:) and well... sorry for that...:silly:
[Galaxy S III Original Android Development] psyntific:
Gpu voltages do not stick on reboot
[Galaxy S III Original Android Development] maxq1:
^ ditto. It does stick though after closing devil tools
[Galaxy S III Original Android Development] DerTeufel1980:
Did you re-flash the kernel after installing cm?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] ArtoD2:
Yes, just forgot to list it... I'm baffled with this... I will try next to restore nandroid as second, so I have two TW RIMs at first and then do wipes and CM install to test...
[Galaxy S III Original Android Development] Lear95:
Had a problem, trying to fix it. Will update you
[Galaxy S III Original Android Development] DerTeufel1980:
Most probably a problem of the order deviltools is using. If it restores voltages before speed, voltages get overwritten again, after speed is applied. I'll check this. Thanks for information

That's really strange. I am very sure many users already installed cm secondary and tw rom primary...

Did you manage to fix it?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rascal0pl:
Thanks for this kernel, finally - everything is working fine (hardware keys backlight, MTP and dual boot).

But I found one problem with dual boot (it is present on every dual boot 4.4 kernel).

I'll try to describe it clear...

The problem is only one (but very important for me) app - solid explorer. Everything is working until I boot first rom. After that, when I boot CM11 rom again (second), Solid Explorer can't refresh (yes, refresh - look at screens) external SD. I am convinced, that it is has something in common with dual boot, because it occurs only when I boot other rom (stock 4.3 in my case), but I do not know what it causes. The only thing that helps is insertion my sd card to external reader and deleting all system folders (which was created by stock rom) and change the sd-card name.
[Galaxy S III Original Android Development] DerTeufel1980:
Did you try another Explorer? I currently have no idea what is causing this. I had paid for root explorer long time ago and never had issues like this.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] Lear95:
Is there a way to switch between rom's that isn't trough recovery?
[Galaxy S III Original Android Development] spoonymoon:
That is not a problem worth mentioning even..

Use another explorer like devil says - x-plore f.eks works perfect on both sd cards

:)

---------- Post added at 02:21 PM ---------- Previous post was at 02:19 PM ----------

In devil tools..you can boot primary or second
[Galaxy S III Original Android Development] Lear95:
You mean "witch rom to boot next"? Ya that option is blocked.
[Galaxy S III Original Android Development] spoonymoon:
Then you dont have a working 2nd rom partition...

Reflash..
[Galaxy S III Original Android Development] Lear95:
Actually it's working perfectly.. I used it a minute ago
[Galaxy S III Original Android Development] spoonymoon:
Well works perfect here :rolleyes:
[Galaxy S III Original Android Development] Lear95:
Well.. How come? what rom's are you using?
[Galaxy S III Original Android Development] spoonymoon:
Cm11 v.12 and omnirom

But all i've tried have worked liquidsmooth pacrom etc.

Just remember to rename framework jar file if mentioned in op on rom thread
[Galaxy S III Original Android Development] Lear95:
What di you mean rename framework file? What for?
[Galaxy S III Original Android Development] DerTeufel1980:
It's in fact an issue of deviltools. It seems to fail by detecting secondary rom sometimes... I just don't know why :mad:

I'll remove the check in coming version... But then the option also gets displayed if one isn't using a second rom (I think users are intelligent enough to deal with it)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] rascal0pl:
other explorers (and apps) works fine...

I know that, but other explorers does't offer even half of that, what solid explorer - like all cloud drives, fast SMB and FTP, very comfortable operations on files (moving by 'drag and drop' for example). In short : this is the best combo-file manager and It is worth mentioning on that fact. I prefer one-in-all app, than installing an app for each cloud drive, or other functions (and I paid for it by the way). X-Plore, ES or other FMs are worthless for me.

So if it not a kernel or rom problem, I will notify the of SE about this.
[Galaxy S III Original Android Development] BradleyR2010:
Ive posted a couple of days ago asking for testers for the new version of DKM, just pm me and send you the link almost everything works
[Galaxy S III Original Android Development] duttyend:
I can confirm that, gpu voltages don't survive a reboot, even with "Ignore kernel version" setting :(
[Galaxy S III Original Android Development] DerTeufel1980:
I've fixed the app now. I'll try to upload it later

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] PIRATA!:
Ho to everyone!

I have a custom rom, precisely DeltaROM v3.1 based on Samsung TouchWiz rom Android v4.3 GMJ9.

I'm using chinese stock kernel for now, but I'd like to try yours as it's well considered by users of this rom.

Can you say something about setting its settings? Something that I must change in default settings??

Thank you very much.
[Galaxy S III Original Android Development] ArtoD2:
Do you have any idea, how utterly stupid can person be? Third time around, I realized that I had selected the zip -option, instead the ROM... twice...

Dualboot with TW MJ9 as first and Temasek CM11 V12 as second is working.

Thank you for the amazing work!
[Galaxy S III Original Android Development] DerTeufel1980:
please try if gpu settings all are sticking now.
[Galaxy S III Original Android Development] PIRATA!:
Is this official? Which version is this?
[Galaxy S III Original Android Development] psyntific:
gpu voltages do stick but the clock speed and up/down thresholds now get reset
[Galaxy S III Original Android Development] PIRATA!:
Is boot sound removed/disabled with this kernel?

I just installed this kernel and I've noticed that my bout sound is gone.

Are they related??

Tnx!
[Galaxy S III Original Android Development] maxq1:
^ perhaps one of your mods? i flashed the latest version of devil and i still have the boot sound.

confirming as well that new devil tools do keep set gpu voltages after reboot. dunno about thresholds and freqs though as i'm fine by stock values.

btw, whenever i set io scheduler to deadline and disable fsync, i'm either getting bootloops or the system is unstable (but more on the former). anyone else getting this? cfq w/ fsync disabled works fine though...
[Galaxy S III Original Android Development] spoonymoon:
Wrong thread :p

This is 9300 you're making a 9000 app

:)

Edit: Hey Devil in new version 1.04 gpu voltages settings are applied after reboot as supposed to :D

works perfect !

Edit 2: And yes the i9000 dkm app detects most values ok and a lot off them stick even after a reboot, but you aren't able to see which? (he he i miss tcp top on/off )
[Galaxy S III Original Android Development] -MaD-:
I tested the app for a minute and everything seems to work. It displays all values correct, but I didn't change anything...

Gesendet von meinem GT-I9300 mit Tapatalk

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] DerTeufel1980:
He has a i9300 meanwhile and making his app again now. He just needs some testers and feedback

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] BradleyR2010:
My app now works with every DerTeufel1980's Kernel out there I9000, I9300, etc
[Galaxy S III Original Android Development] riso123:
With latest release doors anyone else see battery drain relating to gmail?

In running omni and no one else is having the issue...
[Galaxy S III Original Android Development] PIRATA!:
I'm sorry...how do you consider this with last Devil v1.8.0??
[Galaxy S III Original Android Development] DerTeufel1980:
Nothing special in your screen shot.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] PIRATA!:
Quite common/good?
[Galaxy S III Original Android Development] dreadian:
regarding dual boot option

stll cannot perform dual boot even after following the instructions.

plan to use sammy 4.3 + cm11 by tema

sammy (prim) = ok

cm11 (sec) = notgood

also, in dual boot menu, i cannot seem to create the 2nd partition option

are there anyone also experiencing these problems?
[Galaxy S III Original Android Development] DerTeufel1980:
What happened after choosing to create secondary fs?

Anyway, I am going to look at the recovery tomorrow, maybe I find a way to improve it

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] bett3rthan:
Sorry for bothering you, is there any chance that you will implement boeffla in your kernel which can set the mic volume?
[Galaxy S III Original Android Development] DerTeufel1980:
uploaded a new version :)

yes, i am going to make a new build with boeffla soon. the source is already in kernel, i just need to compile it.
[Galaxy S III Original Android Development] bett3rthan:
I feel like being a pain in the arse, but can I ask you what's new in this new version?

Edited: Sorry I just saw the changelog

ALSO biiiig biig bug, lost my baseband after flashing latest version of devil kernel, flashed another baseband but still "baseband unknown"
[Galaxy S III Original Android Development] -MaD-:
I think CM11 is Android 4.4 and in devil only gave compability with 4.3?!

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] DerTeufel1980:
Can you take a look into /efs folder please. It's not empty, I guess. Please verify

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] bett3rthan:
Can't verify anymore cuz I flashed the Devil kernel 0.41. Dual Boot 24/10, and all problems are gone
[Galaxy S III Original Android Development] DerTeufel1980:
Thanks. If you find some time later, please try reflashing this one and report about it.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S III Original Android Development] bett3rthan:
I will do it right now, just tell me all the posibilities, also I must say after reflashing your 0.41 phone won't boot, so I needed to reflash CM rom, and than your kernel

Edited: efs has all data in it, tryed to mount efs partition in recovery mode, but still nothing
[Galaxy S III Original Android Development] DerTeufel1980:
I am not at home this evening anymore, but I come back to you tomorrow

Gesendet von meinem GT-N7105 mit Tapatalk 2