yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ap1618:
Im confused... this IS the "CAD" thread, and if I follow the link in the OP which says "Devil ICS Kernel" it takes me to the i9000 thread.

The latest I see with "cappy" in the zip file name is 0.79.
[Captivate Android Development] dave71670:
No this is the devil thread within CAD . Go back to threads list on PC.
[Captivate Android Development] tkjeeper:
It's not rocket science brah!
[Captivate Android Development] ap1618:
That's what I meant... Devil thread in CAD... i dont see the Devil > 0.79 exclusively for cappy. I see it for i9000 and i9000B.

AND it specifically says dont flash those versions on anything else.
[Captivate Android Development] prbassplayer:
You know you could just try to delete the getprop out of the scrip. In most cases the scrip has no need to know what device its flashing on.

Edit: Disregard. Nightly's scrip is one scrip for a whole list of devices so ya no getprop is a bad idea lol
[Captivate Android Development] DerTeufel1980:
thanks for pointing this out. ia am just using my i9000 initramfs...i did not think about getting errors like this because of the "wrong" files.

I'll change it in the next version...for now it is too late ;)

the following kernel is a test kernel, as i have changend many, many, many important things, and i can't test the kernel, as i would do it for the i9000. if it really is less stable than the previous ones, please tell me.

changed:

updatet kernel base from 3.0.8 to 3.0.30

integrated backports from linux 3.1 and 3.2:

dynamic writeback feature from 3.1

I/O-less dirty throttling from 3.2

ext4 optimations from 3.2
[Captivate Android Development] shaker2k:
Noob question sorry.

What do I do with the file i downloaded and put in command center? Do i rename it?
[Captivate Android Development] prbassplayer:
Nop just stick it where it says in the post /sdcard/android/something/something (to lazy to go check right now xD)
[Captivate Android Development] CheesyNutz:
This kernel is a beast!!!!
[Captivate Android Development] proper69:
This kernel is amazing. First day 8 hours use and 40 minutes screen time. 70% battery left. Sorry no screen shot. Super good work!

The only thing we are missing now is the script to use our stock modems made for captivate and rom switching would be over for me. Well as it stand slim and this is my rock solid not switching unless something has more features. But what more could we want?

Sent from my SGH-I897
[Captivate Android Development] Austin Ag06:
I've. Been thinking about flashing this kernel since I saw it posted here. What modem do I need to install for this to work properly? I'm currently running znkp1.
[Captivate Android Development] sinichi21:
Just want to let you know I think my didle is working now :D I flashed the latest .60 build hopefully It will stay like this thanks for the great work, the only thing I notice is whenever it first boot up it seems to load slower than glitch and semaphore other than that everything is good thanks again
[Captivate Android Development] CheesyNutz:
i know this kernel is still beta ... but any chance of adding twrp :D
[Captivate Android Development] proper69:
Any modem works. I'm currently using znkp1
[Captivate Android Development] shaolin95:
If you do, please keep a version without it. I prefer the old fashion one.
[Captivate Android Development] prbassplayer:
I know a few port builds I tested for him had twrp. Don't know if he will eventually replace it. I personally dislike how it look but as a touch screen stand point twrp's layout is much better. My 2 cents
[Captivate Android Development] cyberbandit1998:
Where can I get command center or can somebody post dl link
[Captivate Android Development] CheesyNutz:
follow the link in the OP
[Captivate Android Development] cyberbandit1998:
Nothing there not on market and no dl link
[Captivate Android Development] CheesyNutz:
http://xdaforums.com/showpost.php?p=25823224&postcount=3
[Captivate Android Development] prbassplayer:
... Its not OP but common why did you even try reading the WHOLE Original post as in all 3 post

http://xdaforums.com/showpost.php?p=25823224&postcount=3

Edit: ninja'd lol
[Captivate Android Development] cyberbandit1998:
Thanks for nothing I read whole post I figured it out thanks. PS was market compatibility issue
[Captivate Android Development] Wakamatsu:
Take a deep breath.
[Captivate Android Development] herofmm:
Actually, flashing back to icyglitch kernel didn't help. Instead, I download build prop editor from "market and replaced "ro.build.device" and "ro.build.product" with "captivate". Then, I was able to flash AOKP build 35.

Following is the checking script from AOKP for your information.

assert(getprop("ro.product.device") == "captivate" || getprop("ro.build.product") == "captivate" ||

getprop("ro.product.device") == "captivatemtd" || getprop("ro.build.product") == "captivatemtd" ||

getprop("ro.product.device") == "SGH-I896" || getprop("ro.build.product") == "SGH-I896" ||

getprop("ro.product.device") == "SGH-I897" || getprop("ro.build.product") == "SGH-I897");
[Captivate Android Development] baconatorXVI:
Hey man, if you scroll back a few pages you'll find .91, and even further back you'll find .86. but don't use .81?(i think it was .81 that gave trouble right?)?

it was posted by DerTeufel1980 as a test kernel. not a stable/official release. .79 works great. .86 works pretty good too. i'm content on .79.
[Captivate Android Development] dave71670:
Here. http://xdaforums.com/attachment.php?attachmentid=1152451&d=1340540375 This is .86
[Captivate Android Development] baconatorXVI:
.86 Page 100

.91 Page 106

There ya go.
[Captivate Android Development] dave71670:
.81 Works pretty good here. It was .84 and .85 that were start of Linaro that caused issues for some. ;)
[Captivate Android Development] baconatorXVI:
right, it was awhile ago, I didn't even try them.. lol

I think i get it now, you got confused when you clicked Derteufel's signature link... which probably took you to the 19000 thread yeah, stay in this thread. it's back a few pages. i already told you where. .79 works great. .86 and .91 work. it's your choice. Hope ya figure it out!
[Captivate Android Development] blively2:
Then don't flash them...just stay on .79 then....:what:
[Captivate Android Development] SkyboneNoya:
Hey would there be any works of getting audience chip support added in for captivites or is this to much work? I feel like I read something on this 30 pages ago or something but. Ya just wondering :D

Also, I can't get the devil idle to work. I just freeze and need to pull the battery when i set it to automatic. I assume that the I897 bootloaders are at fault. Is it worth getting i9000 loaders and using devil idle?
[Captivate Android Development] prbassplayer:
Idle works fine on me with I897 loaders. 0.79 and fiops causes SoD but other than that works fine. Doubt he will invest the time for audience chip support (though I'd love to see it on asop kernels as well) since no one has ever done it and requires a lot of ground work.
[Captivate Android Development] dchawk81:
How many posts per page are you set to view? It affects what page a post shows up on.
[Captivate Android Development] SkyboneNoya:
Ah yes I just realized that devil idle does work! The deep idle was the problem I believe. To bad about audience.
[Captivate Android Development] Wakamatsu:
All versions of Devil posted in this thread:

http://xdaforums.com/misc.php?do=showattachments&t=1642460
[Captivate Android Development] Holmes108:
The default view, I'd assume, as the info is accurate for me.
[Captivate Android Development] geokilla:
I'm getting sleep deaths on 0.94. Anyone with the same problem? I believe I'm not undervolting...
[Captivate Android Development] They Drew First Blood:
Governors

Baconator, check out this post if you haven't already: http://xdaforums.com/showthread.php?p=22127033#post22127033 (Scroll up to first post)

Info on governors and schedulers. Apparently there are better governors than Conservative to use for your battery.

Thread about battery drain, by same user (Bedalus): http://xdaforums.com/showthread.php?p=22126792#post22126792

(Thanks again to Bnevets27 for providing the original link to these posts by Bedalus.)
[Captivate Android Development] prbassplayer:
404 on first link
[Captivate Android Development] killer23d:
I9000 or Captivate boot loader?
[Captivate Android Development] geokilla:
I9000 bootloaders. Captivate bootloaders are a pain when trying to get into Recovery and Download mode.

It happened to me when I was recharging, and when I wasn't recharging. It doesn't occur frequently either. Rare, but happens.
[Captivate Android Development] ap1618:
I feel that Devil has more battery drain than Glitch.
[Captivate Android Development] lavero.burgos:
You right with glitch I could get 2 days but lagging and slow. I prefer devil which is faster and smooth but more battery drain. Anyways I always have a charger close.

~ V
[Captivate Android Development] mindphaser2k9:
Not for me.
[Captivate Android Development] Nick0703:
Hey Teufel, I got the same problem again with the infinite bootloop on v.94. Here's the boot.txt http://pastebin.com/pjskk7UL

Like last time eveything was good till I rebooted my phone. I think the problem is caused when I use the "Devil Kernel Manager" app, because before I used the other one "Devil Kernel Config" app and I didn't get the infinite bootloop problem with that.
[Captivate Android Development] dave71670:
+1 Had same problem with manager. Running config and not a single bootloop so far. Should post in manager thread as well.
[Captivate Android Development] xchrisknightx:
sent from my cappy running latest cm9 nightly a

nd devil kernel
[Captivate Android Development] Nick0703:
We both should post it. Because if only one of us post it, he'll think it's a ROM problem. I've posted something like that before and he told me it can't be the app, has to be a ROM or a Kernel problem. When I tried other ROMs with his app I got the same problem. I staying away from his version now.
[Captivate Android Development] xchrisknightx:
Sorry for my meaningless post lol must have pocket posted :-P

sent from my cappy running latest cm9 nightly and devil kernel
[Captivate Android Development] dave71670:
No problem. I will post there even tho it may not do any good. Developer needs to know.
[Captivate Android Development] Nick0703:
I posted my comment already.
[Captivate Android Development] dave71670:
I have as well. I hope problem gets resolved. I like the ui of the app with this progressing kernel.
[Captivate Android Development] Nick0703:
Same here, I really love the UI. I just hope it gets fixed.
[Captivate Android Development] baconatorXVI:
Thanks, I have read quite a bit about the different governors and your post has inspired me to do even more tests!

I found this wonderful app here https://play.google.com/store/apps/...ult#?t=W251bGwsMSwyLDEsImRzLmNwdW92ZXJsYXkiXQ..

It's called cool tools. it's great for monitoring which governor is using the highest frequency in real time.

I based my little remedial tests with airplane mode on. I run a very system tasking live wallpaper and lightning launcher. i would test idling frequencies and left/right, up/down, and diagonal scrolling.

from my testing I have decided on smartassV2 for running low frequencies on simple tasks. Lazy was good cause it would run the home screen on 200mhz when idle, but it would usually jump up to the 1000mhz step(1.392ghz for my settings) which was unnecessary for that action. Smartassv2 showed itself to run around 400mhz on an idle homescreen without any unnecessary frequency spikes when scrolling, on my settings while scrolling it stayed usually below 982mhz(or something like that).

if you're curious i am using https://play.google.com/store/apps/details?id=com.maxelus.galaxypacklivewallpaper for my live wall paper. the red dragon wall paper is stunning. it's not free though, worth the purchase though.

This is an excellent tool, it provides lots of great heads up info when you are curious.

you've inspired me to search for other governors, They Drew First Blood thanks for the links!
[Captivate Android Development] bobapunk:
I always have used smartassV2 (since I found it anyway). Glad to hear it appears to be one of the best for battery life!
[Captivate Android Development] tkjeeper:
Seems like a newb question, but for some time, I don't exactly remember when, I haven't been

able to restore a nandroid. Fails immediately. I have done this before, any one else have issues doing this with any rom on devil 86? Thanks.
[Captivate Android Development] acras:
DerTeufel1980

Will there be a test kernel for cappy with features like in 0.98 i9000 test kernel?
[Captivate Android Development] They Drew First Blood:
Nandroid

I remember having that issue on Glitch kernel when using the Fiops governor... I would switch from Fiops if you are using it, other than that I couldn't tell you. I guess also try mounting /data before starting the Nandroid? That used to work for me too, when I had that issue, but your issue seems slightly different. My Nandroids would fail with a mounting error, rather than immediately, now that I think of it. Currently I'm on Devil .91 so I can't comment on .86. No issues at all with .91 though.
[Captivate Android Development] brianray14:
Just flashed 94 and everything seems just fine so far.. noob question.. how do i go about adjusting colors without voodoo color baked into kernel? I'm on slim 4.2 so can't take advantage of the cmc i don't think
[Captivate Android Development] prbassplayer:
Galaxy S app its there. Slim doesn't use Voodoo either and have cmc with that app
[Captivate Android Development] :
You can use the Galaxy S Settings app for CMC, but for Voodoo (I prefer this) use the Voodoo Control app on the market, which is good for voodoo sound settings too.
[Captivate Android Development] brianray14:
I prefer voodoo app as well but doesn't work with 94. I'll give galaxy S a go
[Captivate Android Development] fryboy3k:
Random mini-reboots

I am running AOKP b39 on my captivate with Devil 0.91 and I am getting these min-reboots where it will go to my boot animation for a few seconds then back to the home screen. This usually happens when the screen goes to sleep, never during use. I am overclock but to 1200 and never saw this on Glitch. I will attempt to get a logcat if wanted but it is intermittent so difficult to know when it will do it. Thank you in advance.

Others than this I am enjoying this kernel, the speed and options are great. Thank you.
[Captivate Android Development] DerTeufel1980:
here is a new test version.

i now almolst completely updated rcu, memory management, slub, block, page writeback and filesystem writeback to linux 3.3

schedulers now can be specified at /data/local/devil/governor

valid values are all the alvailable governors ;) you have to write them like this:

ondemand (not: Ondemand)

this kernel also can be used for jellybean (for knowing if jellybean is running, the build.prop is scanned for this: JRN83C. as long as no one changes it, it is working. both ports i know (mkalter and nasif are having this value in their build.prop))
[Captivate Android Development] askpcguy:
In the status, does it say why it failed? One reason comes to mind is Missing md5sum. There is a thread to fix that. Generate a new md5sum for all IMG files.
[Captivate Android Development] tkjeeper:
I believe the message was mismatched md5 sum. I make sure I'm on the same kernel from the backup, and that the rom from the b/u is on the sd, don't know what else to do. Thanks I'll check that link.
[Captivate Android Development] bitnerd:
it's also possible to rebuild the md5 sums manually. I had to do that once in the past. not sure why, though
[Captivate Android Development] Tritan88:
The kernel version will matter for trying to restore. I know in one of the versions there was a change made to fix nandroid backup issues. If your backup was made with the buggy version that could be your issue.
[Captivate Android Development] DerTeufel1980:
The old version just did not backup, because md5 could not get generated.

In this cause right now, you have to recreate the md5 yourself.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] bobapunk:
Is this flashed via CWM or Odin? I am guessing CWM but assign double checking.

Thanks!
[Captivate Android Development] Ir0nLy0n:
CWM
[Captivate Android Development] bobapunk:
Ok, .98 flashed and is running fine. I reset all of my settings via "Devil Kernel Manager", but almost none of them stick through a reboot.

Here are the settings that reset on reboot:

Swappiness Value

Governor

Touchwake Toggle

Touchwack Delay

GPU OC (I know this one has never stuck)

I/O Scheduler

I am comfortable enough editing the config files manually. Can you let me know where the files are that need to be edited?

Thanks.
[Captivate Android Development] prbassplayer:
What version of the manager you are using?
[Captivate Android Development] bobapunk:
I do not see a version number anywhere... (According to the Play Store is is v 1.3)

I just went through "devil kernel manager", "devil kernel config", and "ns tools". After setting/confirming all the settings in each app, I think everything is sticking except GPU OC.

EDIT,

This is really weird. After a few reboots my phone is not seeing the internal SD Card at all...

ETA II

Flashed back to .79

I can browse the internal SD from the file manager in recovery

Phone is not seeing internal SD at all (no apps from SD are showing in app draw, apps I have home screen icons for state "app not installed")

Root Explorer force closes when launched...

I could use some help/ideas here!

Thanks....

ETA III

Reflashed ROM... Simply AOKP 6... Still unable to see internal SD from ROM
[Captivate Android Development] pizz0wn3d:
Try flashing back to stock.

.98 was very unstable for me, lots of apps closing without the FC prompt, Mucho reboots, etc. I'm back on .86 for now.

Initially I thought it was because of zram, but then I disabled it and the problems continued.

Herp derp Captivate Tapatalk 2
[Captivate Android Development] DerTeufel1980:
This is weird. Try to make a backup of your data while you are in recovery, then format it.

I have had it once, after flashing a cm7 nightly, the device did not want to boot anymore, cause internal SD card got partially corrupted.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] bobapunk:
I was going to try a wipe/reset next...

The really strange thing is that I can browse the internal SD via USB, AND the Gallary App opens images that are on the Interal SD Card just fine...
[Captivate Android Development] dave71670:
.98.2 working fast and stable so far on F4k rom. Giving little time to test more. Thanks again. Great work.
[Captivate Android Development] baconatorXVI:
The link says 266 views, 1 says it's unstable, another says it stable and fast.

Anybody else have anything to say?
[Captivate Android Development] Monfro:
For me too on aokp 40

Sent from my Captivate
[Captivate Android Development] bobapunk:
Running nandroid "back up to external SD".

I have a concern that restoring _may_ cause the problem again...

While I am doing all of this, I think I am going to jump to AOKP b40 since Simply AOKP is no longer being developed...

Thoughts?
[Captivate Android Development] baconatorXVI:
Slim ICS. Never had any major problems. Smoothest my phone has ever been.
[Captivate Android Development] bobapunk:
Ok, I did a factory reset, then resotred just /data and i am right back to where I was...

Odining kk4 stock right now... :(
[Captivate Android Development] martinomac:
Working really well and smooth, no FC. Using SlimICS 4.2, Devil Config 0.6, 106%OC, SmoothUI, 403MB, ZRAM - 100MB, 60% Swappiness, Touchwake, Ultra KSM, SmartassV2, Noop

Best battery life ever, approx 0.9%/hr on Devil Idle and highest Antutu score....well done DerTeufel, thank you!
[Captivate Android Development] DerTeufel1980:
Have you tried to format the card? Nothing else had solved this issue for me.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] geokilla:
Aw no ODIN version this time. Ok thanks anyways!
[Captivate Android Development] askpcguy:
Nandroid mismatch md5 sum fix thread link:

http://xdaforums.com/showthread.php?t=714114
[Captivate Android Development] prbassplayer:
I can't speak for your sd card issues but I'm using 0.6 from xda thread with no issues
[Captivate Android Development] askpcguy:
Flashed 0.98 then hit some sleep. No problems overnight, phone still worked haha! Using NSTOOLS, liveOC 104% and set Conservative govenor. Saved no problem. Media storage now loves going crazy and saying I have duplicate of each MP3. I fix that by unmounting EMMC, force stopping Media Storage, then clearing data and rebooting. NSTools settings saved without issue.
[Captivate Android Development] bobapunk:
No, I did not try that...

TiBU is restoring apps right now (Running on AOKP 40) Everything appears to be fine, but I still have to re-set all my settings. Reflash Devil Kernel, and move apps to SD. Then I will know for sure. I guess if it doesn't work, I will be re-formatting... :(
[Captivate Android Development] Ir0nLy0n:
Having the same problems with apps closing without prompt. Even closing background apps.
[Captivate Android Development] xtmp:
Installed it without wipe cache & dalvik.

Got memory leaks after half an hour of usage.

Than I wiped cache & dalvik from CWM & flashed it again and got boot infinite.

nandroid...
[Captivate Android Development] :
Yeah, I am having memory leak problems with .98 too, other than that no FC's or anything. Back to .79 I guess. Thanks for the frequent updates and support, keep up with this great kernel!
[Captivate Android Development] geokilla:
All kernels seem to have memory leak after like 2 days of use.... Just suddenly comes. At least that's my experience anyways.
[Captivate Android Development] DerTeufel1980:
I already heard about the ram issue. It seems to be caused by the 3.3 updates. I am trying to upload a version without the 3.3 updates later (hope I have enough time)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] prbassplayer:
Psh if not you'll get it some other time. Take it easy.
[Captivate Android Development] DerTeufel1980:
here it is. same as before, but without the 3.3 updates.... i think more work has to be done to it :(
[Captivate Android Development] :
Testing now. Will report in an hour or so on ram usage.
[Captivate Android Development] dave71670:
Running 98.2 for a while on 391 ram, switched to 403 and lost root browser in rom toolbox. Just went back to 391 and sd came back for browser again. Hope this helps those losing sd in browsers.
[Captivate Android Development] jerkysh:
oh, this one is definitely better, i tested each test kernel, but always came back to 0.86.

this one didn't give me any issues, i'll test it one more day, but for now, everything's awesome !:)
[Captivate Android Development] azunino:
Hi DerTeufel1980,

reading the changes in your git I saw this:

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

From the little I understand, this change reverses both SD cards, even in fully working phones, when the kernel is compiled with CONFIG_HAS_BROKEN_SD=y. Is that right?

thanks for your work!
[Captivate Android Development] xtmp:
Got bootloop on this version. :(
[Captivate Android Development] :
What rom? Were you coming from another version of Devil? Did you wipe cache and dalvik cache?
[Captivate Android Development] DerTeufel1980:
To be honest, I am not sure, but i think so. A user asked me to make a kernel for him, with this changed. I just have made a config out of it, and compiled the kernel for him. Too bad, he never wrote again

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] acras:
So if you revert 3.3 updates what are the changes left in changelog for 0.98 kernel?