yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] They Drew First Blood:
Battery life was definitely better (although I have no screenshots or statistics) with deep idle working. I do use music pretty frequently at work. I can't really compare/contrast the two, however, mostly due to the frequency that DerTeufel posts kernel updates. I barely have time to run the battery down before it is time to flash again :). I have not used the devil idle singularly. I currently have both deep idle and devil idle activated, and I have not noticed whether having both activated has altered battery life noticeably over simply having deep idle activated. I should add that I have been using the SmartassV2 governor for some time now, but have been switching through the Active Schedulers since recent issues with the fiops one. I also have the Screen Off Max Frequency enabled and set to 400MHz, and am gratified that your final link in post #888 seems to confirm that 400MHz saves the most power with the SOMF enabled. Screen Off Min set to 100MHz. Thank you for providing those links by the way, great reading. I don't want to clog this thread up too much further, as I seem to be rambling, but I need to get around to testing the devil idle's effects.

Oops, forgot to answer your other question: i9000 or i897 bootloaders? I guess it depends on whether you listen to music. If so, I would say go for the i9000 BLs and Deep Idle, but if not there may be no need for you swapping BLs from i897 to i9000.

One last thing... this is interesting too http://xdaforums.com/showthread.php?t=1478418&page=1. (Info about governors and schedulers, I found it to be more to the point than the link in OP#3)
[Captivate Android Development] jerkysh:
yay guys, new smilies!:cyclops:

and btw, the latest test kernel 0.81 is a beast, fast and my battery went better!

12 hours+ and my battery hasn't even reached 50% :victory:
[Captivate Android Development] jecsah:
I see that V.82 is up also. What changes are needed to flash on the cappy? I know I should know this but I'm too tired.
[Captivate Android Development] BL4zD:
Thanks for the kernel I'm going to try it out now.
[Captivate Android Development] mbc663:
Don't try to be hip and call it a cappy if you don't even know how to flash a kernel...just saying
[Captivate Android Development] pizz0wn3d:
Lol. And where is this v.82 he is speaking of?

Edit: Ah. In the i9000 thread. Dont think I want to flash that.

Herp derp Captivate Tapatalk 2
[Captivate Android Development] Nick0703:
Lol, same here! I think I'm better off waiting for V.83 or some new V.8x.
[Captivate Android Development] pizz0wn3d:
If its for the cappy and its newer than what's installed on my cappy, Ill be flashing it. ;P

Herp derp Captivate Tapatalk 2
[Captivate Android Development] D4almond:
maybe i miss something

i use .79

sometimes, my data switch off automaticly

i try to switch on with togle in notification bar, or mobile network setting, thats still not works

except, i reboot my phone after enabled that

i got it 3 times this day
[Captivate Android Development] baconatorXVI:
Well what I've noticed about the data toggle I'd that it takes a long time to activate and turn the data on., if you touch it and it doesn't respond right away that doesn't mean it's not working, it's just taking it's sweet time. Also multi taping it makes it unhappy.

If the toggle keeps giving you trouble remove it, once never had trouble with it in my notification bay
[Captivate Android Development] D4almond:
i know about that, ahahaha
[Captivate Android Development] CheesyNutz:
.79 is beast went 24 hours with moderate use no screenshot needed power LoL im on miuiV4 from miui. us
[Captivate Android Development] DerTeufel1980:
Most probably you get linaro compiled test kernel today :)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] xtmp:
Me pressing F5 :) And by the way the last test kernel .81 is amazing battery life! :victory:
[Captivate Android Development] Monfro:
I confirm: seems like. 81 gives more battery life.

About performance it is similar to. 79 ..i feel. 81 a little bit smoother, but can be a placebo
[Captivate Android Development] DerTeufel1980:
It still lasts some hours.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] bruzski:
just did a donation :fingers-crossed:

1VH86778LB607813P
[Captivate Android Development] DerTeufel1980:
Thank you very much my friend. :)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] Wdustin1:
A donation much deserved! wish it could be more. 6mw73589cx163593W
[Captivate Android Development] DerTeufel1980:
also many thanks to you :)

and here comes the linaro powered test kernel now.

besides of compiling it with linaro and O3 compiler flags, i have updateted the /stanging/android drivers to linux 3.4
[Captivate Android Development] pizz0wn3d:
Flashing now!

Herp derp Captivate Tapatalk 2
[Captivate Android Development] Nick0703:
My phone can't get pass the kernel splash screen. Getting bootloop.:(
[Captivate Android Development] pizz0wn3d:
I've rebooted twice since flashing it with no problems (once after flash and another after flashing bitblaster zip for swap). Try reflashing.

Herp derp Captivate Tapatalk 2
[Captivate Android Development] Nick0703:
And now I can't get into Recovery......:crying:
[Captivate Android Development] tkjeeper:
no problems here
[Captivate Android Development] geokilla:
Corrupted download maybe? Or maybe your phone just doesn't support Devil kernel, though that would be a first.
[Captivate Android Development] prbassplayer:
I also just loop. Killed my recovery. Slim 4.1 (yes not released yet) Will ODIN a kernel and reattempt
[Captivate Android Development] Nick0703:
I'm going to re-download it and my phone does support the devil kernel. The last kernel on my phone was the v.81

---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------

Yeah, I had to flash semaphore through ODIN to get recovery back.
[Captivate Android Development] sfernandez:
+1 I even re downloaded and same .81 not problem. .84 bootlooped at kernel splash and no recovery.
[Captivate Android Development] Nick0703:
Yeah, it's not working for me. I flashed it 5 times and still going into a loop. I'm going back to v.81
[Captivate Android Development] tkjeeper:
Yikes! I'm on the road! Won't be near a computer until bedtime, I guess I'm lucky that didn't happen to me! Weird.
[Captivate Android Development] zuN!:
I'm getting the boot loop as well.
[Captivate Android Development] Holmes108:
Bootloop here as well, and I couldn't access recovery. Had to install another kernel with Odin. Tried twice.

Edit: On CM9 nightly 23 fyi.
[Captivate Android Development] prbassplayer:
I'm curious what rom are you using when you loop or don't loop.
[Captivate Android Development] tkjeeper:
No loop here, simply latest
[Captivate Android Development] DerTeufel1980:
just to be safe there was no compiling error, i comiled it again, and also flashed this one right now.
[Captivate Android Development] zuN!:
This is kind of offtopic but I'm a bit agitated right now :/

Flashed 0.84 --> Bootloop.

Normally, I would enter recovery and flash the older version or restore a backup etc. ---> can't access the recovery because of the damn boot loop (it's the first time I've seen that I can't enter recovery).

Try Heimdall --> Device isn't recognized

ODIN --> same thing

Searching XDA and Google how to use adb / if possible to put the phone into recovery mode via adb while the phone is "off" or in download mode ---> no success

I have a big sadface right now. Any help from the Devil kernel readers is much appreciated
[Captivate Android Development] shaker2k:
Getting into recovery is sometimes just a matter of timing in letting go of the power and volume button. Took me 10 minutes once. Keep trying. Pull your battery and use the 3 button combo.
[Captivate Android Development] zuN!:
I've been trying for the past hour after giving up on the Heimdall/ODIN methods. Still no luck on the recovery for some odd reason. I go into recovery easily most of the time as I've been using this phone ever since it came out so the timing shouldn't be an issue. It's odd that it gets stuck at the Devil kernel splashscreen when I get the timing "successful"
[Captivate Android Development] nrcptr:
tried .85 with no luck

was running .81

cleared init.d, nstools used ultimate kernel cleaning script then flashed .85

used odin to flash semaphore 1.2.5sc.tar phone is working again

phone is running slim 4.0
[Captivate Android Development] martinomac:
Running really well, installation was fine - but I always wipe cache before flashing kernels so I haven't yet received any boot loops.
[Captivate Android Development] gocats7:
Running 85 with no issues. Thanks!
[Captivate Android Development] prbassplayer:
Ugh Nop Still loops on .85. Will ODIN and attempt with wiping caches.

Edit: nop just loops and loops :( I wanted to try this. Lol Unfortunately since I can't get in to recovery I can't procure a log. Der Teufel anything I can do to provide more info (lack ADB at the moment but will get it running if need be)
[Captivate Android Development] DerTeufel1980:
try different usb ports, or reboot into download mode. sometimes i also get the phone not recognized, but thsi always helped.
[Captivate Android Development] Nick0703:
Yeah, I'm still getting bootloop with v.85.:(
[Captivate Android Development] xtmp:
Bug ?

Running on SlimICS 4.0, flash 0.81, and went to ASS - StartUp tweaks, screen was black ~ 5 sec. Then slimICS got root permitions, than screen was black again but ~ 15-20 sec. Then I seen only first checkbutton activated (Enable start-up tweaks).

After this operation, and rebooting, phone starting showing devil screen, then slim logo infinitely(waited more than 20 minitus), not booting to desktop.

init.d has only

S30datafix**

S90volume**

Tried 3 times with stock flashing.

Without devil kernel booting fine.

Tried 0.85 - the same.
[Captivate Android Development] prbassplayer:
If I had to guess. Slim uses Init.d scrips for the start up tweaks. If you had not set that up beforehand and flashed Devil might have cause a error without the scrips.
[Captivate Android Development] xtmp:
looks like devil moves init.d slims scripts to backup folder, Slim try to find it at boot, but can't do it... and that is why it stops booting ?

PS. Testing .85 :)
[Captivate Android Development] D4almond:
Try to reset ur pc, sometimes my pc need to do that for recognize my capy

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

Btw, download from tapatalk app not problem?

I little scare to flash .85, lol
[Captivate Android Development] prbassplayer:
If memory servers the startup tweak reads init.d only once to write in another file the settings. If there is no init.d scrip the first time it might cause some issue. I don't remember the name of that file, best I can say is reflash without wiping. Should fix it.
[Captivate Android Development] mindphaser2k9:
Had bootloops on 0.84 and 0.85. Made .tar from 0.81 and flashed with Odin, this works. Can't wait for 0.86 :p
[Captivate Android Development] xtmp:
.85 works well for me. may be because I using the i9000 bootloader.
[Captivate Android Development] prbassplayer:
Anyone have it working with i897 BLs?
[Captivate Android Development] RootTheMachine:
I don't think it matters. I have i9000's and it's a no go. Just bootloops from kernel splash.
[Captivate Android Development] Nick0703:
It's not working with i896 BLs also. And I don't want to flash to i9000 BLs just to get a kernel working. Because flashing BLs is risky. I'll wait for v.86
[Captivate Android Development] blively2:
Question is...has ANYONE flashed the latest, successfully???:confused:

Sent from Orlando, Florida...
[Captivate Android Development] mindphaser2k9:
No, this is not the case. I'm using the i9000 bootloader too but this doesn't help.
[Captivate Android Development] pizz0wn3d:
I've been on 0.84 all day with zero problems. I'm even running my standard 1404mhz 117% LiveOC settings with swap enabled. From what I've been reading, it looks like its a problem for slim users. I'm on aokp b39.

Herp derp Captivate Tapatalk 2
[Captivate Android Development] prbassplayer:
Need to get my phone reset to thank you (out atm).

So it isn't BL dependent.
[Captivate Android Development] mindphaser2k9:
No, I'm on CM9.
[Captivate Android Development] pizz0wn3d:
Doesn't slim use some features from AOSP? Perhaps its a problem with an AOSP feature and Slim cherry picked it, giving its users the issue as well.

Edit: Slim OP states that it's "fully based on AOSP" with cherry picks from the CM & AOKP teams.

Just trying to come up with possible explanations. I really have no idea lol.

Herp derp Captivate Tapatalk 2
[Captivate Android Development] prbassplayer:
I don't know . Eventually today I will try the kernel with F4k mod (has the Linaro tweaks).
[Captivate Android Development] blively2:
I have no idea how to create a .tar from .81...I'm also stuck in the bootloop HELL! Would you be able to upload your .tar for download (for me)? I would be most appreciative!!

EDIT - NEVERMIND: I flashed the Semaphore 1.2.c .tar and reflashed .81 - worked well!
[Captivate Android Development] martinomac:
Yup, flashed .85 with no issues on NYX RC5. I also wiped cache before flashing kernel. RC5 has no extra scripts in init.d, just pure solidness. Paired with Devil= most reliable configuration...and I've tried just about all of the Roms.
[Captivate Android Development] baconatorXVI:
Off the topic of boot loops...

3986 score on antutu...

Vr, performance, 1.392ghz 391 ram. Devil.79.

That was only my second test!
[Captivate Android Development] cursedwave:
.85 bootlooping for me on AOKP39. :( But .81 is still solid!
[Captivate Android Development] prbassplayer:
Thats not how Benchmarks work. You should calculate the avg of a few runs. Hitting a one time high means nothing =P

Well that kills the idea its rom based. Must be a tweak or hardware difference?
[Captivate Android Development] inku:
Coming from .81 on simplyAOKP flashed .85 with no problems, thanks ;-)
[Captivate Android Development] Nick0703:
Ok, so I've tried it with Slim ICS and SimpleAOKP, and still getting bootloop. Has to be something else that's causing the problem.
[Captivate Android Development] prbassplayer:
I tried Slim 4.1 and FakMod r4 and loops. I've attempted to wipe Init.d from semaphore to flash Devil still loops. I'm out of ideas xD
[Captivate Android Development] nrcptr:
i am a noop but .81 and slim 4.0 work good on my cappy

tried .85 twice, boot loops both times

odin back to semaphore 1.2.5 sc.tar

then flash back to devil .81 and working good
[Captivate Android Development] askpcguy:
Sleep death? What were you doing on the phone before the sleep death?

I used to see that following a recharge and with wifi on.
[Captivate Android Development] askpcguy:
Going to flash 0.85 cmc and see how it looks.
[Captivate Android Development] Nick0703:
Nothing much really, I was using the XDA app. Then I went to get some food to eat and when I came back, my phone wouldn't turn on, had to pull the battery.
[Captivate Android Development] askpcguy:
No need to battery pull, hold volume up plus power until the device resets.

I just flashed Devil3_0.85_cappy_CFS_BLN_CMC_20120623.zip from 0.79 CMC and managed to get stuck in a bootloop. Three button combo does not boot into recovery. Even ADB REBOOT RECOVERY fails to work.

Uh oh, seems the captivate is down for the count. If I have to make a jig to get download mode, it'll be returned to stock and sold.. Luckily I made a backup and copied ALL files to my PC.

I seem to think I can make an Odin 3 flashable TAR file with the previous kernel and flash that from download mode. Any thoughts?
[Captivate Android Development] prbassplayer:
Rename the boot.img (i believe) to zimage and you need to stick it in .tar (or make the .tar). You can just flash Semaphore.tar to get recovery back and then flash w/e you want.
[Captivate Android Development] askpcguy:
I'll need a bit more than "I think" before attempting anything because I really don't want to fully brick it lol!

And based on this thread, it seems I'm pretty well stuck with a bootloop or make a jig to get download mode and return to stock. http://xdaforums.com/showthread.php?t=1650799
[Captivate Android Development] prbassplayer:
Thread is wrong. Well they where I was right. AND very last post is stating Semaphore released a Odin flashable.... I just got stuck in loop with out recovery and flashed Semaphore with odin. I think it might have killed my modem in the process but ROM survives and got back recovery. I'm not sure about the modem because I've swapped kernels over 15 times today and been bouncing between 2 roms like another 10 times. So as I said just Odin semaphore....

Also I say I think because at this current moment don't remember specifics, but the resources are around xda (mostly i897 and i9000 forums). Also "fully bricking" can't happen unless you flash bootloaders.:cool:
[Captivate Android Development] Nick0703:
If you get into a bootloop, just put your phone into download mode and only flash the semaphore kernel with Odin to get back the recovery and after that flash any kernel you want. There are no need to flash back to complete stock.

That's what I did when I got into a bootloop. I flashed semaphore kernel with Odin, boot up into recovery and flashed Devil V.81.
[Captivate Android Development] DerTeufel1980:
Many thanks for your donation. It's highly appreciated :-)

I hope the next releases are even going to be better. Still many things are missing.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] CheesyNutz:
My only complaint is this the AndroidOS is crazy high and I cant find out why
[Captivate Android Development] tkjeeper:
Same here, but it's an beta kernel yet so...
[Captivate Android Development] CheesyNutz:
indeed ! everything is is flipping great just wanted to point out that tiny thing
[Captivate Android Development] deBricker:
I flashed this and my phone heated up... flashed back Glitch. Idk if I'm the only one having problems.
[Captivate Android Development] apg5031:
one of the best kernel so far......thank u
[Captivate Android Development] blively2:
yes, you're the only one...

sent from an outhouse...
[Captivate Android Development] deBricker:
Maybe it was a bad flash. Ima reflash again
[Captivate Android Development] deBricker:
Reflashed and its working pretty good. Haven't tried any OCs or UVs yet. Activated power save mode... its pretty fast! Definitely a contender to IcyGlitch's throne in my book.
[Captivate Android Development] kevinnol:
Updated to 0.55 and switched to powersave mode and still .. ultra smooth

first choice if it comes to kernels thank you

Edit: Commandcenter needs some time to change the values..

What is meant by Smooth UI ?

and another thing.. the Governor Presets are Smooth, Performance and Normal

Smooth is Smooth

Normal is Normal

and Performance is .. powersave ? :o
[Captivate Android Development] DerTeufel1980:
Smooth_ui was introduced by stratosk for ondemand governor. I have implemented it to most of them. When you touch the screen, cpu goes to 1000 Mhz, to make the device react fast to your command.

Performance has to be a typo. Thanks.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] kevinnol:
-Jetzt mal auf Deutsch, weil ich mich auf Englisch so schlecht ausdrücken kann-

Die CommandCenter app reagiert (?) ab und an nicht, manchmal ändert sie den Wert manchmal wiederrum auch nicht..

Fsync und WifiMode lassen sich gar nicht durch die app ändern, jedenfalls nicht für mich

English:

The CommandCenter app wont react(?) from time to time, sometimes the value gets changed and sometimes not...

Fsync and WifeMode cannot be changed through the app. At least not for me.
[Captivate Android Development] DerTeufel1980:
well, fsync and wifi mode are just not implemented to cappy version yet. maybe i get it into the next build.

which values get only sometimes changend? all of them?
[Captivate Android Development] kevinnol:
Kind of.. for example sceen off - max freq from 800 to 400

it changes instantly, after that i cant change smooth ui off

so I restart Commandcenter and sometimes smooth got changed and sometimes not..

its difficult to explain..

'edit': got it, the app works flawless unless i change the Screen off max/mix freq ..
[Captivate Android Development] cassv:
Hi, the kernel is just great... one thing is that i was trying to install the nightly cm build and im getting the fallowing error:

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

E:Error in /sdcard/update-cm-9-2...zip

(Status 7)

Installation aborted.

I could flash a new kernel with odin or heindall, but this is kind of annoying :).

Keep the good workd.
[Captivate Android Development] shaker2k:
try flashing glitch then cm nightly.
[Captivate Android Development] cassv:
Thanks man, can you point me where to download the glitch kernel, i havent been able to find it for the captivate or ics 4.0.4.
[Captivate Android Development] Wdustin1:
http://xdaforums.com/showthread.php?t=1459576 ;)
[Captivate Android Development] blively2:
Glitch kernel for Captivate and ics:

http://xdaforums.com/showthread.php?p=21706011

sent from an outhouse...
[Captivate Android Development] mindphaser2k9:
The same issue was on Semaphore btw.
[Captivate Android Development] askpcguy:
All better now! And here I was thinking I would be pre-ordering a Galaxy SIII haha!

Here is the break down.

From 0.79, I flashed 0.85 and got stuck in a boot loop on the white AT&T screen. Three button to get into Recovery failed.

I downloaded the Semaphore 1.2.1c tar and used Odin3. Steps are, open Odin 3 on PC. Remove the battery from the phone. Plug in the USB cable. Hold volume UP and DOWN then insert the battery. Poof, download mode. Use the settings shown in the screen shot to flash the kernel. I had to use this thread http://xdaforums.com/showthread.php?t=1350266 to point out the kernel TAR goes in the Odin 3 PDA section.
[Captivate Android Development] zuN!:
Looks like I'll be pre-ordering a Galaxy SIII lol.

I've tried all my USB ports and nothing works. My device can't be detected. I'm beginning to think it's because I'm using a i9000 ported ROM.

Edit: Speak of the devil, it finally worked after so many tries.
[Captivate Android Development] askpcguy:
Seems to me MyUI 5.13 is the latest most stable ROM along with 0.79 Devil kernel.
[Captivate Android Development] DerTeufel1980:
Sorry guys for all the trouble. I really don't know, why it is working for some, but not for all of you.

I'll try to find the solution today.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] baconatorXVI:
aw you ruined my adrenaline rush of going to post "I SCORED A 4185 ON ANTUTU!"

I had found out gpu overclocking switched itself off... I switched it back on. During the test i got like 102 fps on the knights hacking their swords screen.

lol

it's nice having a flipping high score though :laugh:
[Captivate Android Development] Holmes108:
Re: bootloops,

No idea if it's relevant, but the only"extra" thing I had done to my phone (on CM9) was flash a low space, datadata fix in cwm.

No other fancy tweaks, OC, etc
[Captivate Android Development] askpcguy:
Would there be any leftover files that could be useful for troubleshooting this problem?
[Captivate Android Development] rophiroth:
What config did you try to reach that? I only get 3800 :c huehue
[Captivate Android Development] jerkysh:
i dunno why guys, but with the 17/06 CM9 the latest test kernel (0.85) doesn't boot, it takes me through a bootloop (AT&T screen then the kernel splash screen, and over and over again)...
[Captivate Android Development] lordxentris:
You should implement this as done in Semaphore if possible.

- Bootloop detection (if no normal boot is detected the phone will be forced to recovery in next boot) *

Source - http://xdaforums.com/showthread.php?t=1567464

If it is, then please ignore this. :P
[Captivate Android Development] askpcguy:
That only helps for bootloops caused by incorrect Overclocking/Underclocking or voltage changes.