yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Tsaukpaetra:
For those interested, in the thread referenced above, the kernel supplied is indeed for the i9000. That means that if you try it, everything should work with the exception that the Accelerometer (The thing that tells your phone which side is currently "up") is rotated 90 degrees counter-clockwise (really only affects things that rotate the screen, like youtube), and the Home and Back buttons are switches, and media playback just won't work, these are know compatibility issues, but everything else works fine out of the box.

You will still need to format system and data to upgrade from 4.1.2, but this is handled easily enough as the kernel itself will need to reparition the phone for dual-boot.

For all others willing to wait, it shouldn't be too much longer after DerTeufel1980 fixes the dual-boot things that he will be able to release a normal i897 version for us. ;)
[Captivate Android Development] albokid2468:
I bought a captivate with this ROM.

It would perfectly, in every way possible.

The only issue I have is when I power down. Sometimes it powers down perfectly.

But sometimes it never shuts down, and the circle stops. It seems like the device froze. If I don't hit the power button a few times, it won't shut down at all.
[Captivate Android Development] Tsaukpaetra:
Well, this is the Thread about the generalized Kernel for JellyBean CM10-based devices, but a good idea would be to see if there are any updates to the ROM. There has been a lot of work done since development continues.

I would recommend reading up on the ROMs available, if you're already on a CM10-based rom, then moving to another shouldn't be too difficult, just make sure you follow Any and ALL instructions provided on their respective threads.

However, if you're just looking for an updated kernel (which may help in this situation), the new thread can be found Here. You'll probably just want the normal kernel (the one called the Revert version.) for starters.
[Captivate Android Development] jjziets:
Which is best for more ram Devil 3_1.7.5 or Devil 4.2?

I just want more ram with no extra bugs on my CM10

Which would you recommend. This or the reverted [KERNEL] - Devil4.2?:confused:

also I get a warning when I click on the links

"

High Risk Website Blocked

Location: rootaxbox.no-ip.org/derteufel/jellybean4.2.x

Access has been blocked as the threat Mal/HTMLGen-A has been found on this website.

Return to the page you were previously viewing":eek:
[Captivate Android Development] Tsaukpaetra:
If you want something without bugs.... well the best of luck to you, it's almost impossible to do so. However, it's really a matter of reading the first post to make an informed decision: If you want Dual Boot, use the normal version. If you don't want Dual Boot, use the Revert version (so it doesn't repartition your device). Either way, you have to read more, otherwise people will just point and laugh if you have issues that the developer mentioned in the documentation.

Best of luck!

Oh, and the "virus alert"? This is a common ploy by Sophos in particular to blacklist innocent sites that use dynamic IP (i.e. no-ip.org) hosting. If you go to http://88.190.33.222/derteufel/jellybean4.2.x you will get no such warning.
[Captivate Android Development] ecselite:
which version is compatible for 4.1.2 roms ?
[Captivate Android Development] Tsaukpaetra:
Don't dig up old threads!

The latest version working with Jelly bean is found at [KERNEL]DualBoot - Devil4.2 (06-Feb-2013)

You can find the kernels on the normal download site, http://rootaxbox.no-ip.org/derteufel/
[Captivate Android Development] Klitoni:
Im running CM 10.1 Stable.

U guys think that phone will run better with this Kernel ?
[Captivate Android Development] Tsaukpaetra:
mods please lock thread

It's hard to tell. Your milage may vary, but there's no real harm in trying out a new kernel. But really, you should not grave dig! Read my post directly above yours.
[Captivate Android Development] Fallen Spartan:
Ok folks, thread locked for time being ala post below:
[Captivate Android Development] spinedoc:
Hey guys, thanks in advance for the awesome and hard work. I am running into an odd problem, not even coming up with any hits on search of this forum or a search engine.

I installed this kernel and also installed the Cyanogenmod 10.1 v2 update floating around from wrsmega, that installed fine as well. I rebooted into recovery and then did a fix permissions, then rebooted.

Looks like I'm booting into Jelly Bean as far as I can tell, but before it goes to desktop I get a weird "Type password to decrypt storage" message. I have no idea what the password might be, I even tried my google password but no go.

Any ideas where I might start?
[Captivate Android Development] DerTeufel1980:
If there ever comes up the message, that decryption failed, do not hit the button!

Try flashing semaphore kernel, maybe just something went wrong by mounting /data.

If semaphore fixes it, please flash back and tell me, if it's still ok, or not.
[Captivate Android Development] spinedoc:
I figured it out, I was using wrsmega's files and they don't seem to work. The mod shut down the thread but didn't link to yours leaving me lost where the new versions were. I found your CM10 v10 and installed that and everything seems to be working so far, I'll play with it later tonight.
[Captivate Android Development] XeoNoX:
Oh thank you thank you thank you!!! Finally after months someone recompiled the kernel and fixed the " Phone to PC USB " slow transfer rate issue. Its back to normal and transferring at 8-10 MB/s instead of 2-4MB/s. I dunno what u did but it works normal now!! thanks again. Ill be donating and thanks again for the fix

---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------

hrm i would donate but i cant read German or dutch or whatever language that is when i click the donate button...is there a English translation.
[Captivate Android Development] melvinaury:
You can use Chrome browser (PC), it can translate to any languages.
[Captivate Android Development] DerTeufel1980:
i just have started to upload the kernels.

changes since 1.1.0:

- use 200 mhz if gpu is active, but also 100 mhz if not (if you want the cpu to always run at higher than 100, you have to disbale lock_scaling_min at /sys/devices/system/cpu/cpu0/cpufreq/lock_scaling_min)

- linux 3.0.40

- row i/o scheduler from linux 3.5

- tunings to deadline i/o scheduler

- switch do_fsync() to fget_light() (less overhead)

- optimized AES and SHA1 routines

- added Wheatley governor, thx to kasper_h

- compiled new bigmem libs for latest hw_composer changes

- Increase dpram semaphore wait timeout (cdma modem fix by Efpophis)

- disabled twrp recovery for now (not working with jellybean)

- compiled with "old" toolchain for now (at least for me, there was no performance difference, but more issues)

- new cm 10 partition layout (use onenand for /data)

kernels can be found here: http://rootaxbox.no-ip.org/derteufel/jellybean/

until i move them to the correct folder tomorrow
[Captivate Android Development] dongfangri:
The kernel works almost fine, just found 2 problems:

1. very lag with row schedule.

2. a little lag with ZRam.
[Captivate Android Development] Monfro:
New kernel for CM10 works really well.

I have waited the relese of Devil kernel to try CM10.

I simply can't live without it on my Cappy. :)

Sent from my Captivate
[Captivate Android Development] DerTeufel1980:
Row seems to be buggy.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] TomMelee:
Please forgive my dumbitude, but is there a guide somewhere for the more intricate kernel settings? Swap vs. zRam, "swappiness", etc? I'm familiar w/ the governors and such.
[Captivate Android Development] prbassplayer:
Check the FAQ of ICS thread (3rd post), most of it is the same in JB.
[Captivate Android Development] TomMelee:
Ok, got it, thanks. One last dumb question. I tried Devil Manager and Devil Config, and I feel like I prefer Config. I've also got NSTools---I'm afraid it's redundant or dangerous to have both, but I don't see a place to set voltages in Devil Config (or Devil Manager.) Am I missing something?
[Captivate Android Development] RootTheMachine:
Nope you have it right.

Sent from a jelly bean
[Captivate Android Development] TomMelee:
One last dumb question.

Enabling "deep idle" on this phone has always resulted in sleep death the first time the screen shuts off. Every time, always, every rom and every kernel I've ever tried. If I use Devil Config and set deep idle OFF and Devil Idle to Automatic, might this address the issue? Or do both need to be ON?
[Captivate Android Development] Monfro:
This is a captivate issue.

Someone seems to have solved this issue flashing i9000 bootloader.

My suggestion is to turn both off and enjoy stability.

Sent from my Captivate
[Captivate Android Development] TomMelee:
Ok, thanks. I'm currently hemmorhaging battery, but np.
[Captivate Android Development] Monfro:
I think turning off will not make a big difference on an average use.

Anker battery can give 30-40% more juice than original.

Sent from my Captivate
[Captivate Android Development] tkjeeper:
If you're battery is that bad there's other issues. I'm regularly at 18 hrs with 3 hrs screen time. Deep idle isn't the solution. I've never used it.
[Captivate Android Development] TomMelee:
Anker battery? What is this?

On my ICS rom I was regularly at 18 hours with ~40% remaining. I'm bleeding ~10%/hour right now on this JB rom, however I've got BetterBatteryStatistics running so hopefully I can nail it down soon. Ambient GPS is awful on this thing, I accidentally left it on yesterday for ~3 hours indoors and it ate 14% battery.

It's also a brand new OEM battery, and I probably still need to calibrate it. It's got less than 15 charge cycles on it.
[Captivate Android Development] Monfro:
Anker battery is a great 1800 battery that fits in original back cover.

Jelly Bean drains that much because of Google Now, which wants to determine your position using maps, that running in background drains more juice than ICS

Sent from my Captivate
[Captivate Android Development] TomMelee:
Oooh, ok. I just got rid of an oversized battery that finally died on me. I can keep the thing plugged in at work, that's no problem, and I've got it slowed now it would seem---but it drank like 40% in 30 minutes last night while I was setting it up. Eep.
[Captivate Android Development] askpcguy:
I flashed [ROM][MIUI][Multi-Lang][8/23/2012] 2.8.17 - JellyUI v1.3 and noticed it uses the Devil Kernel. A problem made me want to restore my nandroid backup. What I did was boot into recovery, format /system then flash the base rom I was on when the Nandroid backup was made. Now my captivate gets stuck on the white AT&T screen. I'm unable to three button into recovery. I even tried flashing via Odin the semaphore 1.2.6c.TAR as I thought it would fix this broken recovery thing.

Should I try flashing the CM10 Devil kernel.tar so I can use recovery to restore my nandroid backup, the backup is of Miui 8.10 ice cream sandwich.
[Captivate Android Development] tkjeeper:
You're the reason I didn't flash that rom buddy. I wish I could help. I flashed the other jb miui rom, didn't like it so I flashed back and restored my nandroid. I hope you get it worked out. I'm not sure I even remember how to use Odin anymore. Keep us posted on his you get back to normal.
[Captivate Android Development] prbassplayer:
Odin a kernel that shares the same partition layout as the rom you attempted to restore.
[Captivate Android Development] askpcguy:
I thought I did, Semaphore v1.6.2c.tar which is ICS. Miui 2.8.10 (Cloud) was ICS at least I thought so. Didn't fix it. I even tried Devil3_1.1.3_ICS_cappy_CFS_BLN_CMC_20120807.tar and nothing. I think my mistake was wiping system then flashing the ICS rom while I was still "On Jelly Bean"

---------- Post added at 05:41 PM ---------- Previous post was at 05:29 PM ----------

All clear. I flashed Devil3_1.1.3_JellyBean_cappy_CFS_BLN_CMC_20120807.tar via Odin, three button into recovery is successful. I see my mistake. I flashed the WRONG miui ICS rom. Once I get into the Phone OS, my backups are going to the micro-sd card and I'll try one more time.

I think things are OK now, past the white AT&T screen. I will try once more to nandroid restore myself back to miui ICS. *Random question, anyone up for a little midnight code session? Make a script to copy backups (Miui, Nandroid, Titanium backup and theme backup to EMMC) as an ultimate precaution?*
[Captivate Android Development] prbassplayer:
Wait you flashed a JB miui?
[Captivate Android Development] xtmp:
affirmative :)
[Captivate Android Development] askpcguy:
Yup, this to be specific http://xdaforums.com/showthread.php?t=1847668 Worked after flashing twice. Then I got weird behavior when the phone simply would not wake up. Tried to DDMS and find out whats going on but nothing worked. Going to leave the jelly bean ROMS alone at least until next release 8.31 and hope many of the Nexus S bugs resolved.
[Captivate Android Development] XeoNoX:
how do i get into download mode? everytime i try to get into DOWNLOAD mode it goes into RECOVERY mode instead. ive even tried ADB using the REBOOT DOWNLOAD command and it still takes me to recovery...any ideas?
[Captivate Android Development] pqee:
Just noticed today that Stock RAM setting is preventing video playback with videos my own camera has taken. Tried with both stock gallery video player and quickpic and both fail (built in codecs?). MX player still works though.

Rom: cm-10-20120825-NIGHTLY-captivatemtd

Kernel: DEVIL3_1.2.1_JELLYBEAN_CAPPY_CFS_BLN_CMC #375

Default RAM Setting: Stock

Flashed CM10 back over for stock kernel and videos play fine.

Flashed Devil kernel and they fail again.

Switched RAM setting to XL, reboot - videos play fine again.

Haven't tested BigMem setting or if camera can even take videos with stock RAM (was trying to play old videos I've recorded).

I'm happy with XL so just pointing out the bug/issue/problem/inconsistency etc...
[Captivate Android Development] RootTheMachine:
ADB reboot download doesn't work on non-stock roms. Please refer to the troubleshooting sticky in the general section, as download mode isn't controlled by the kernel.
[Captivate Android Development] geokilla:
Trying to run Helly Bean and it's not booting up with the latest Devil 1.2.1? It just goes straight to Recovery... Hope I got the right kernel o.O
[Captivate Android Development] Monfro:
This kernel is for CM10 and other derived roms.

Helly Bean comes with its own kernel and you don't need to flash another kernel.

When a new build of Helly Bean is released it includes a updated kernel.

Sent from my Captivate
[Captivate Android Development] geokilla:
I thought Helly Bean is based on CM10 :eek:

Time to read the OP again..
[Captivate Android Development] tkjeeper:
Cm10 got rid of data data, helly bean keeps data data, kernels differ accordingly.
[Captivate Android Development] whisky23:
Installed Slimbean 2.2 from ICS4.2. So far, everything is running smoothly. The only issue is the compass calibration seems to be off by about 90 degrees, and no amount of figure 8's will fix the problem. But GPS seems fine after installing the fix. I wonder if the compass issue is Semaphore related.
[Captivate Android Development] pqee:
Should you ask that in the Semaphore thread? This is for Devil Kernel.
[Captivate Android Development] Nick0703:
The compass worked fine for me when I was using it. And also the compass is fixed in the Semaphore kernel. But still I don't remember having any problem with the compass when I was using the Devil Kernel......
[Captivate Android Development] DerTeufel1980:
new jellybean kernel can be found at my website now.

some things need to be added to it tomorrow. op also is going to be updated tomorrow.

http://www.hellybean.com/jelly.html
[Captivate Android Development] pqee:
Videos are working again with the Stock memory configuration. (Kernel 1.4.1)

Thanks for the update!
[Captivate Android Development] thuanngotau:
What version is suggested to be used with RemICS-JB Rom? I'm so confused, sorry guys!

EDIT: I found the answer!
[Captivate Android Development] Monfro:
New.1.4.1 kernel works really well here.

Sent from my Captivate
[Captivate Android Development] Kyuta Syuko:
I'm using the AOCP CP3 and was trying to get this kernel to work with it but it will only boot into recovery and as far as I can tell there is no /datadata partition unless it's somehow hidden in a way I can't make it visible. Any other ideas on what might be the cause?
[Captivate Android Development] embedded123:
Do you guys use deep idle on Devil new kernel?
[Captivate Android Development] DerTeufel1980:
I don't know this rom. I can't tell you anything about it having /datadata or not.

This kernel does not have datadata, and is made for ROMs, similar to cm10.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] Kyuta Syuko:
Well AOCP is a ROM built from source based off CM10 and AOKP with some tweaks of their own. I don't see a /datadata partition so I was just wondering what else might cause the kernel to just boot into recovery.
[Captivate Android Development] Monfro:
If your system partition is 420mb then this kernel is compatible.

If your system partition is 1.5gb it means that rom has the old CM10 partition layout without datadata and this kernel is not compatible.

Sent from my Captivate
[Captivate Android Development] melvinaury:
In that case you have to install the older release that support that partition layout.
[Captivate Android Development] pqee:
I think you mean Data partition, not System partition. The current CM10 nightlies have a 420Mb data partition (hence all the complains of running out of room for apps) and a system partition of about 1.5Gb.

I'm running CM10 from yesterday (09/08) and this kernel, v1.4.1.
[Captivate Android Development] Kyuta Syuko:
According to df my system is 350M and my data is over 1G according to settings it's around 2G, but aren't these sizes determined by the pit file? Never used CM...
[Captivate Android Development] pqee:
You definitely don't have the CM10 layout then and I wouldn't install the kernel from this thread or you're probably going to get bootloops.
[Captivate Android Development] prbassplayer:
Actually the kernels ramdisk (I believe) makes the partition. However you will need to factory reset and possibly do a mess of a process to get it to work. :)
[Captivate Android Development] DerTeufel1980:
Sounds like you are using hellybean.

Hi. Long time no see.

In fact it's the kernel itself which makes the partitions, but simply flashing a kernel to a not matching rom is not the best idea.
[Captivate Android Development] Kyuta Syuko:
Nope using AOCP, but I'll give the HellyBean variation a try and see how it works.
[Captivate Android Development] DerTeufel1980:
Well, now I know at least why the kernel was not working. It's the old cm10 partition layout, before system and data got swapped.

You should try a rom based on the new cm10 layout, or my hellybean, with its own kernel
[Captivate Android Development] prbassplayer:
Well I didn't say it was easy :) But I figured it was possible because early JB I used your helly bean kernel on the old cm jb partition and it worked. Hope all is well for you.
[Captivate Android Development] kevin37:
forgive me if this is already posted but I am at work and do not have the time to suf through the posts. but I created the twrp file in cache and now when trying to boot into recovery it wont go past the devil kernal splashscreen? Is there a way I can fix this?
[Captivate Android Development] prbassplayer:
I haven't been using devil much anymore as i897 isn't my main device now, however last I heard twrp wants playing nice with JB. Try to remove the time you creates in recovery.
[Captivate Android Development] Kyuta Syuko:
Finally got around to flashing Devil Kernel HellyBean Edition with AOCP and it seems to be working. At the very least my phone booted up.

*edit*

Seems a shared library got misplaced after flashing the kernel. As far as I can tell it only affected two of the apps I use.
[Captivate Android Development] azunino:
Hi,

I've been using CM10 with Devil3_1.4.1_Jellybean_cappy_CFS_BLN_CMC_20120905 and the experience has been great so far: no FC, no SODs, no lags, no reboots and battery life is almost 2 days. In other words super stable! thanks!!!

I just have two minor problems. If a turn off the phone and connect the wall charger, the phone boots cm10. If I turn it off while still charging, the battery charging animation starts, but before showing the green bar, it hangs and the screen stays on showing an empty battery.
[Captivate Android Development] pqee:
I'm getting boot loops with the latest CM10 (18th) and Devil 1.4.1.

Anyone else?

----

Ok so apparently its just a black screen, not a true bootloop but still unusable.

It's due to the vsync/ioctl changes from one or both of these merges:

http://review.cyanogenmod.com/#/c/23403/

http://review.cyanogenmod.com/#/c/23466/

There's a bit more info here with a revert for i9000. Not sure if it will work on ours.

http://xdaforums.com/showthread.php?t=1892913

Sent from my Jellied SGH-i896.
[Captivate Android Development] bitnerd:
Yeah, I have the same problem on mine. Had to switch back to the stock kernel
[Captivate Android Development] RootTheMachine:
Yep, same here. I had the same guess also.

EDIT: Your posted fix works great.

Sent from a jelly bean
[Captivate Android Development] Tsaukpaetra:
Its a known issue. Basically the kernel doesn't have the necessary files (gfx etc) to show the correct charging animation, and also doesn't handle correctly the boot process for charging only. (Something in the kernel arguments I think that tells the difference). To save space this data is usually left out.

Sent from my SGH-I897
[Captivate Android Development] DerTeufel1980:
new kernel + changelog at my website: http://www.hellybean.com/jelly.html
[Captivate Android Development] prbassplayer:
Don't see anything on Vsync does it have the new Vsync set up?
[Captivate Android Development] azunino:
It seems it does:

https://github.com/DerTeufel/samsung-kernel-aries/commit/95e1d50a581912e3e435b2cc95827fca2fb469cc

https://github.com/DerTeufel/samsung-kernel-aries/commit/5885202705ccb8ce6c6d18d7417ae2e4c9115ade
[Captivate Android Development] zuN!:
Would the new Vsync be the cause of its inability to be used with AOKP Build 2?
[Captivate Android Development] tkjeeper:
Doesn't work with paranoid android either, won't boot past kernel screen
[Captivate Android Development] dongfangri:
Thanks for your rapid response, DerTeufel1980.

The new kernel works great, except a little bug: kernel version shows "Unavailable" in Settings/about.
[Captivate Android Development] Wakamatsu:
Ditto for me and Slim Bean 2.4.
[Captivate Android Development] DerTeufel1980:
Yes, your rom needs to be updated. You should force your rom dev to do so. The changes are saving more than 5% cpu power.

It's a bug of cm10

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] shuyin1102:
If you come from AOKP --> DONT FLASH V1.5.2 :(
[Captivate Android Development] mrsubway:
So I'm assuming this won't work with Slim Bean 2.5, as it is AOKP.
[Captivate Android Development] prbassplayer:
First Slim isn't AOKP. Second SlimBean 2.5 has the Vsync code implemented but disabled. So devil 1.5.2 won't work. I'm currently building 2.5 with Vsync enabled for internal testing. Sorry to hijack your thread DerTeufel :)
[Captivate Android Development] mrsubway:
And I apologize for being a dumbass. :(
[Captivate Android Development] vbenkovskyy:
My phone is booting normally but screen is black.

(ROM: MIUI JB (Base - CM10))