yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Dark_Eyes_:
Just installed the latest v0.95 and it actually said 10% as default. Setted to 100% and it sticked after a reboot. Will try tomorrow to reflash kernel and see what happens.

Btw, great job on the last deviltools!

Edit: it doesn't stick after reflashing kernel on v0.95. But it says correctly that it is set at 10%... Looks like the default settings is set to 10% and the custom setting doesn't stick. Gonna try v0.5 later.
[Nexus S Android Development] TsarFlow:
Hi ! 4.3 kernel is working very well, also DevilTool does. I'm using LagFix app to keep a smooth phone, but it says me that /cache can't be trimmed because of a hardware or kernel problem. Do you have any ideas to fix this ? I'm using Carbon rom, if it is also rom related.

Thank you for this hard work bro ! :D
[Nexus S Android Development] DerTeufel1980:
The kernel does not include initramfs, because of that, it doesn't affect /cache partition. Maybe it's just not supported on this device

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] treesurf:
I just noticed that voodoo colors is back, thank you!

Does anyone know what the default color settings from marmite were? Sorry for asking here, but the marmite thread is locked.
[Nexus S Android Development] Dark_Eyes_:
Where did you get voodoo colours? There have been no new build... Maybe in the latest hellybean?

Voodoo settings from Marmite

2018580870

1699283160

2578531560

---------- Post added at 11:21 AM ---------- Previous post was at 10:58 AM ----------

It seems like the setting for vibration sticks with v0.5. It's still there after reflashing the kernel so I assume it's a bug in the latest version of deviltools. I'll keep v0.5 for now as there is nothing I really need in v0.95.
[Nexus S Android Development] DerTeufel1980:
Hellybean kernel does have voodoo color again

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] Dark_Eyes_:
Great! I'll extract it from hellybean then. Any plans to add it here too?
[Nexus S Android Development] DerTeufel1980:
Yes, maybe tomorrow

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] Dark_Eyes_:
Good, cause I don't have my Linux partition up on my new computer and it seems completely impossible to extract zImage from boot.img on Windows...

Thanks a lot for the great work !

---------- Post added at 02:04 PM ---------- Previous post was at 01:27 PM ----------

Well, something weird just happened. Vibration setting reverted back to 10% with v0.5. I can't remember if I rebooted the phone but I didn't flash anything for sure. Maybe it's a problem with the kernel then?
[Nexus S Android Development] Dark_Eyes_:
There, I took the liberty of getting the latest build from hellybean made a flashable zip with it. It works really great. Thanks DerTeufel!
[Nexus S Android Development] explorer-10:
[MENTION=4196889]DerTeufel1980[/MENTION] your kernel that's built into the latest weekly build of slimbean, is that build from 10/20?
[Nexus S Android Development] DerTeufel1980:
No, it's compiled from sources, and identical to the one in hellybean, but built for aosp

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] Dark_Eyes_:
Well, there is definitely something wrong with the vibration setting that keep resetting to 10% without notice... Worth investigating what's causing that but I feel like the default is set to 10% instead of 100% and the custom setting in deviltools does not stick...
[Nexus S Android Development] TsarFlow:
Any news for update ? :)
[Nexus S Android Development] DerTeufel1980:
There's nothing newer than the one above

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] andrei1015:
I've recently became a user of this kernel because on CM10.2 my apps got killed really easy with the default kernel. But was wondering something. I heard a rumour saying that a kernel can be overclocked and still be stable if overclocked to around 10% of the frequence. Would you be willing to add a 1096 or 1100 MHZ setting?
[Nexus S Android Development] Setting.Out:
Use devil tools, you can live oc and get what you want... on my phone I need +25 on the voltage for stability
[Nexus S Android Development] andrei1015:
Ah, so this was all the hype about the app. Thanks!
[Nexus S Android Development] DerTeufel1980:
please try, if this kernel/deviltools combination fixes the low vibration intensity.

i have added an additional sysfs to the kernel, by default, the old one is used (which is also used by crespo parts).

if you want to use deviltools instead, you can activate the other sysfs in there (crespo parts then can't control vibration anymore)
[Nexus S Android Development] Dark_Eyes_:
Thanks bro! So far so good.

The switch in newest devil tools is to disable crespo parts? I thought crespo parts were removed in cm10.2... Well anyway, I suppose it disables the vibration control by the rom?
[Nexus S Android Development] DerTeufel1980:
Yes, it's to disable the control by rom, but let deviltools control it.

Both ways working?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Nexus S Android Development] Dark_Eyes_:
It's hard to tell, as it changes really unexpectedly... I've been testing with devil tools disabled, and so far it's ok. I will wait again and if it's still good after flashing the next nightly I will test with devil tools.

Just wondering, is it also possible to had that switch for the color settings and let voodoo control it. I found that if using voodoo app, deviltools overwrite it with it's own settings...
[Nexus S Android Development] Dark_Eyes_:
Update:

While deviltools was disabled, the setting changed to 10% again. It said 10$ in deviltools even if I couldn't change the setting, but it still said 100% in the rom settings. Weird...

I will try the other way around...
[Nexus S Android Development] andrei1015:
Are those for 4.3 or 4.2?
[Nexus S Android Development] DerTeufel1980:
Both

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] DerTeufel1980:
Did it show 10$ from the beginning?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] Dark_Eyes_:
Nope, it changed somehow along the way, but I did nothing in particular...

Now using the devil tools to control vibration and it seems ok so far!
[Nexus S Android Development] DerTeufel1980:
Hope it keeps working

Edit: could you please try changing vibration in rom settings, while set to deviltools. Thanks

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] Rushabh22:
hey Dev , Just installed your mentioned kernal but within a 2 minutes my phone are getting hotter like it is burning my skin..:confused:

Don't know what's the problem..

By the way your kernal is always super fast..:good:
[Nexus S Android Development] Dark_Eyes_:
What rom are you using? I don't have that here. It's more likely to be a rom problem...

By the way, vibration setting still sticking with deviltools... Fingers crossed!
[Nexus S Android Development] adm1jtg:
voodoo color settings specifically rgb screen multipliers dont seem to save properly if you set them through the actual voodoo apk. They do appear to keep when set in latest deviltools.

Also have been getting some very odd screen off and screen on issues. Not consistent but at times the screen will turn completely green for up to 3 seconds before turning off on an auto timeout. I have seen similar behavior on wake up This behavior was also present to a lesser degree in bedalus kernel 9.1 as well. I have tested with different io and gov combinations to no avail.It is present with every combination i have tested. I suspect this to be caused EITHER by some kind of weird voodoo interaction or to be caused by the additional selinux overhead.

I should say I am using an aosp model of the kernel for testing as I am a slim user

If you would like me to test and further evaluate this I would ask for 2 test builds....

1) Simply the latest build with voodoo disabled

2) The latest with selinux disabled at the kernel level

I would like to test aosp vs cm as well...

Am working with tchaari as well on this but he has been very busy so figured I would see if you had time to run the above mentioned builds for me to test
[Nexus S Android Development] Dark_Eyes_:
It's probably a problem on the rom level then if it also happened Marmite... I never had those issues with cm. If you want a build without voodoo go to page 38... Without selinux doesn't seem to be such a good idea but you can always try. DerTeufel will need to build a new one for that...
[Nexus S Android Development] adm1jtg:
I am "attempting" to follow bedalus's thread for building just kernel and see if i can adapt that to build devil so I can mode these changes myself. Wish me luck as i am a true newbie on the dev side,.
[Nexus S Android Development] Dark_Eyes_:
I've been down that road and gave up... It really is not that straightforward. But I encourage you to try as I'm far from knowledgeable when it comes to that kind of stuff. Also, maybe I or DerTeufel can help if you get stuck. Good luck my friend!
[Nexus S Android Development] Dark_Eyes_:
Changing settings is possible in the rom, but the test vibration is always the same, meaning that it has no effect. Even if setting it to 0% does nothing, which is the desired behavior, right?
[Nexus S Android Development] adm1jtg:
Thanks,

Just for the record I cannot use the previous build for my non-voodoo test as I am on slim rom which uses the aosp version of devil and the ones posted here are all cm based.

Well lets see how my "attempts" go.

In the meantime could you test the following voodoo color scenerio...

Under color tuning in devil tool please use the following settings:

red .226

green .250

blue .333

red gamma -26

green gamma -30

blue gamma -33

it is not every time but if you let the phone sit till the screen timeout kicks in the screen will turn all green for between 1-3 seconds before it turns off

Also if you could please test those settings in the voodoo sound apk that also sets voodoo color I have found that the screen rgb multipliers when set in the voodoo apk do not survive a reboot.the gamma hack values survive the reboot fine.

Any help in further isolating these issues would be much appreciated.
[Nexus S Android Development] Dark_Eyes_:
It's normal that the settings in voodoo app do not stick. Well, not the desired effect but I have that too. DerTeufel is aware of that and will most likely try to modify deviltools when he get time. Just adjust your settings in deviltools for now.

Setting the gamma values too "negative" can cause a green flash. I've had that with almost every kernel and every rom I've tried. Try adding +2 to each value until it's gone. Right now I'm using punchy settings +4 with Marmite rgb hack and it's ok.

You can flash cm kernels on aosp roms. Just go to this thread and download the correct file in 3rd post

http://xdaforums.com/showthread.php?t=2292111
[Nexus S Android Development] adm1jtg:
What are the actual values for the marmite rgb hack as I will try those

As far as the changing kernel type you listed I am aware but don't like messing with swapping the hwcomposer files in this instance since I an testing on slim.

Thanks for all your help it is appreciated
[Nexus S Android Development] DerTeufel1980:
You also can flash this kernel to aosp. The sysfs to switch between aosp and cm mode is working, as tchari told me.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] Dark_Eyes_:
The Marmite rgb hack are approximately

Red .470

Green .395

Blue .599

That's not exact but close, as I can't adjust perfectly with devil tools.
[Nexus S Android Development] Dark_Eyes_:
[MENTION=3279686]DerTeufel[/MENTION] vibration setting still sticking with deviltools controlling it, so I think that's solved!

Thanks for the great work!
[Nexus S Android Development] treesurf:
Voodoo color settings are sticking for me between reboots and even after flashing a ROM update.
[Nexus S Android Development] Dark_Eyes_:
Voodoo colors stick if you set them with deviltools, not if you set them with the voodoo app... At least that's what happens to me and some other guys here!
[Nexus S Android Development] treesurf:
Sorry, I should have been more clear. I am using the voodoo app and the color settings are sticking for me. I'm on latest hellybean and devil kernel. I don't know why it's working for me but not others.
[Nexus S Android Development] adm1jtg:
Tried that combination with default, alt and punchy and I still have issues with all white or all green screen off. I cannot seem to make it go away no matter what settings I try. You has suggested it might be rom related and I agree it could be but what rom parts actually related to something that seems to be strictly a voodoo color issue?

Will try running an aosp version with voodoo disabled and see if the issues go away.
[Nexus S Android Development] DerTeufel1980:
Please also try "playing" with framebuffer draw delay in deviltools

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] xbs:
What is the "framebuffer draw delay" function?

TIA
[Nexus S Android Development] DerTeufel1980:
After pressing power, framebuffer stops drawing. This adds a delay, and it keeps drawing frames for the delayed time. Was meant to fix crt off animation on galaxy s3, but it can't hurt to try it

Btw: crespo with lcd panel had a delay of 250ms by default, where the others didn't have a delay

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] notbrodie:
[MENTION=4196889]DerTeufel1980[/MENTION]

Do you have any recommended settings for your kernel? Or does it come default with what you'd recommend? As my device is purely for media, I'm more focused on smooth UI than battery longevity.
[Nexus S Android Development] Dark_Eyes_:
I would suggest live oc to 110% and oc to 1320 mhz or more if your device can take it. For performance you should go with interactive and row scheduler. Look on the forum for threads that explain how to set interactive for better performance but basically you set the up threshold low like 70% and the timer short like 20000 us...

That's gonna be fast but not good on battery life...
[Nexus S Android Development] mattia.b89:
Where is the 4.3 compatible kernel? I'm on CyanogenMod 10.2

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
http://xdaforums.com/showpost.php?p=46810981&postcount=452
[Nexus S Android Development] mattia.b89:
Thank you!

Could you explain me what the apk is ???

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
Search for nstools ..is do the same
[Nexus S Android Development] mattia.b89:
Perfect !

I think NSTOOLS it's a generic tool so with this kernel I'll use its tool...

Sent from my Nexus S
[Nexus S Android Development] treesurf:
TricksterMOD is another kernel tool that works well. You can find it on the Play store.
[Nexus S Android Development] mattia.b89:
[MENTION=4196889]DerTeufel1980[/MENTION]

I think should be useful add the uptime timer in the info tab

Sent from my Nexus S
[Nexus S Android Development] DerTeufel1980:
You mean in deviltools?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] mattia.b89:
Yeah!

Sent from my Nexus S
[Nexus S Android Development] mattia.b89:
Again, on DevilTools:

the tool overwrites CM settings?

Sent from my Nexus S
[Nexus S Android Development] DerTeufel1980:
I didn't notice it on my device.

Did it for you? Which settings?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] mattia.b89:
at the moment BLN
[Nexus S Android Development] DerTeufel1980:
What do you mean with bln? That's not a rom feature.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] mattia.b89:
b

ack

l

ight

n

otification
[Nexus S Android Development] DerTeufel1980:
Bln still isn't a rom feature. There's nothing to overwrite

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] mattia.b89:
I'm on CM ...

Sent from my Nexus S
[Nexus S Android Development] mattia.b89:
How can I come back to CM kernel?

Sent from my Nexus S
[Nexus S Android Development] khalid_ham33d:
Yup, just flash the CM ROM you are using over it. It'll flash the CM kernel along with the ROM... :)
[Nexus S Android Development] mattia.b89:
And without flashing the entire ROM , for example extracting from that .zip only the kernel ?

Sent from my Nexus S
[Nexus S Android Development] Setting.Out:
You can flash the boot image (kernel), just unzip the rom, get the boot image and check out the KitKat thread for more details on how...
[Nexus S Android Development] khalid_ham33d:
Yes you can do that by extracting the boot.img from the zip file and then flash it via terminal emulator or via your PC using ADB but I think the easier way is to flash the same ROM over it. Doesn't need anything, just boot into recovery and then flash that ROM zip, clear Cache and Dalvik and you are done... :)
[Nexus S Android Development] ethan_hines:
I'm confused it says:4.3 test build on page 36 and 38

but there are only 11 pages to this thread. Where do I dl the 4.3 (does this work for 4.4 too) test build?
[Nexus S Android Development] DerTeufel1980:
You are currently writing on page 51...

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] ethan_hines:
Maybe there is something wrong with the forum cuz atm it says page 11 of 11
[Nexus S Android Development] ethan_hines:
Sorry you're right! Apparently my settings were to display 50 post/page =11pages
[Nexus S Android Development] Setting.Out:
Any chances of testing your 4.4 kernel?... ;)
[Nexus S Android Development] DerTeufel1980:
I don't have one yet

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Nexus S Android Development] Setting.Out:
Your latest one is working flawlessly on CM11 (unofficial)
[Nexus S Android Development] DarkShadow69:
+1

It's working perfectly fine on unofficial CM11 :)
[Nexus S Android Development] alienwolf426:
Hi,

I'm using the crespo_devil_20131025_VC.zip kernel file on a PA 3.97 rom and I can't seem to make the touchwake to work.

I have it enabled in devil tools and whenever I get a message/email, the BLN turns on but whenever i touch the screen, it doesn't wake. Am i doing something wrong? or it doesn't work?

Cheers,
[Nexus S Android Development] Setting.Out:
Touch wake is limited in time for screen turning off.. If you touch your screen within x amount of time (seconds usually) it'll work, but not just because you ever touch it..
[Nexus S Android Development] alienwolf426:
ohh. well, i did not know that. Thanks.
[Nexus S Android Development] miHah:
What about ART on CM11? working okay? :D anyone tested it out?
[Nexus S Android Development] doma8108:
As i could seen, art works only with stock kernel.. with devil and art put on, my phone didnt boot..
[Nexus S Android Development] Setting.Out:
Art works for me on CM11 (unofficial and euoskank) using Devil..
[Nexus S Android Development] doma8108:
Then :crying: I will try again..
[Nexus S Android Development] kkkhattak:
Which one is working with Android 4.4 ?
[Nexus S Android Development] xbs:
http://xdaforums.com/showpost.php?p=46810981&postcount=452
[Nexus S Android Development] kkkhattak:
Bro [MENTION=4196889]DerTeufel1980[/MENTION] please update your kernel :) its an awesome kernel please keep updating it with more performance update :D
[Nexus S Android Development] BradleyR2010:
Devil Kernel Manager v3.0

My app is now compatible with this kernel its an alternative to DevilTools. it should show up on google play in a few hours. Check my new DEVDB thread for more info and discussion.

DEVDB thread
[Nexus S Android Development] Dark_Eyes_:
[MENTION=3279686]DerTeufel[/MENTION] any plans to update devil kernel with the latest 4.4 code? I think there are some improvements in kitkat...

http://source.android.com/devices/low-ram.html

Thanks in advance!
[Nexus S Android Development] adm1jtg:
I dont believe there are any kernel specific changes for 4.4 beneficial or not as slimkat and cm11 and even the aosp on xda for 4.4 all run devil unchanged from its current form

The low memory device stuff is a build.prop change if i recall and the rest are rom side changes.

I could be wrong on this someone please correct me if I am wrong
[Nexus S Android Development] Dark_Eyes_:
Well I'm no expert, so I will let DerTeufel look into that if he wants, but there have been changes in the kernel on kitkat, like enabling KSM and swap, which were already on devil, but there seem to have other under the hood changes as well. As I said I don't know much when it comes to kernel so I will let DerTeufel look into that.

It's not because it works like that on 4.4 that it can't be improved...
[Nexus S Android Development] DerTeufel1980:
There's almost nothing changed at cm Crespo kernel. Do you know if other roms added more changes?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Nexus S Android Development] Setting.Out:
There's been the obvious version change (I don't know if it is a help for KitKat or an improvement for us), the aosp ROM's kernel got some patches, (but I don't know if is of any benefit either or anything you don't already include).. your kernel works flawlessly on CM, EuroSkank and Slim.. It has play store issues repoted on the Aosp ROM.. But I don't know what version they flashed or if it was flashed correctly?? Slim has some battery drain that ?may? be kernel related... But I'd still love to test an updated kernel.. ;)
[Nexus S Android Development] Dark_Eyes_:
Well the aosp ROM seems to have tinkered with the kernel a bit, and there are some merges from 3.4 version. It's highly possible that not much changed as devil works flawlessly with kitkat.
[Nexus S Android Development] k-kuchen:
I am running the latest Devil Kernel and DevilTools 0.9.6 on CM11 KitKang Nightlies. It works better than I could have hoped. But kernel settings are reset every time I reboot. Does anybody know what I can do about this?
[Nexus S Android Development] Setting.Out:
My settings stick??
[Nexus S Android Development] k-kuchen:
I have to reload it every time... Don't know what else I could try. I came from a clean install
[Nexus S Android Development] notbrodie:
what superuser tool are you using? SuperSU is generally considered to be better than CM's Superuser
[Nexus S Android Development] k-kuchen:
I'm using the built in superuser. Will try superSU if you think that might help
[Nexus S Android Development] Setting.Out:
In the settings unchecked the follow CM settings.. (SuperSU)
[Nexus S Android Development] k-kuchen:
OK, I somehow managed to get it to work tinkering with SuperSU und Superuser. Now I am just running Superuser and it works.

But I tried reproducing it on a second Nexus S and it didn't work. So I'm still kind of lost how it works

I'm sorry. I don't really know what you mean
[Nexus S Android Development] Setting.Out:
The SuperSu superuser has a settings menu in the app.. if you click the app, then select settings.. in the settings menu you'll find an option towards the bottom that is check marked for following CM (only shows on CM roms).. Uncheck this and you gain complete su control..
[Nexus S Android Development] k-kuchen:
Thanks, that worked. But sadly settings still won't be restored after reboot. It worked only once. Tried it several times after that and had no luck.

Do you have CM Superuser disabled in Developers settings?
[Nexus S Android Development] DerTeufel1980:
Sorry for this question, but you have set:

Set on boot in settings tab? Do you get a message about a changed kernel version? And which version of the app you are using? 1.0.8 should be the latest / working one. It can be found in the app thread, but it's not in the op (because it was a quick bug fixed version), but one or two pages before the end of the thread

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Nexus S Android Development] k-kuchen:
Yes it is set to change at boot. I am using 0.9.6. The latest version FC.

I don't get a message about a changed kernel
[Nexus S Android Development] Setting.Out:
I installed the latest 1.0.8 and my previous settings did not stick on reboot.. I was/am happy with 0.96, it worked... I will revert back.. :)

I do use the enable at start on superSu..