yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] baconatorXVI:
lets see, I had it on SIO(or Vr), conservative(I think, either that or performance) I had the cpu stepped up to 1200 with 116% live OC which yields 1392ghz. I'm on 391mb ram. I also used the devil kernel config app and set the GPU to 250 mhz OC. lol I hit 102 fps

I can't remember much else that i did special... I was on like 15% battery I think lol

I didn't do any special task killing or ram clearing.

but like prbassplayer said, it's not relevant cause it's not an average lol.
[Captivate Android Development] fractaline:
Just chiming in to report a successful flash from .81 to .85 on aokp b39...

Phew.....

Phoned in.....
[Captivate Android Development] pizz0wn3d:
Still a great feature that I'd love to have :D

I do have a (hopefully small) request though. Could we get the hardware buttons in recovery remapped to the same configuration as Glitch? They are mapped in the same order as the virtual keys that are already implemented. It's really the only thing that bugs me and I would love to see them mapped that way if it's not too much trouble (obviously the bootloop issues are a much higher priority).

Herp derp Captivate Tapatalk 2
[Captivate Android Development] askpcguy:
Interesting, 0.81 to 0.85 is successful but I tried updating from 0.79. That might be helpful.
[Captivate Android Development] zuN!:
I updated from 0.81 to 0.85 and, as you already know, ended in a bootloop. It probably depends on the ROM or another variable.
[Captivate Android Development] mindphaser2k9:
Yeah, that's correct. Here it is, tar version for Odin.
[Captivate Android Development] DerTeufel1980:
ok, hopefully this one solves the bootlooping issues. i have reverted the update to the /stanging/android drivers from linux 3.4 back to the ols ones.
[Captivate Android Development] prbassplayer:
Read before posting.

I believe its the other way around. Id have to look for the post to confirm. Never mind lol.

Awesome dl now
[Captivate Android Development] CheesyNutz:
Must resist temptation of new beta kernel..... . 79 purrs for me phone lasting all day... Must resist new goodness....
[Captivate Android Development] prbassplayer:
Well 0.86 booted. Awesome work Der Teufel. Now we need a Rom Dev to make a rom with the linaro tweaks. lol
[Captivate Android Development] DerTeufel1980:
Are there differences at the rom side between captivate and I9000? If not, the rom compiled by F4K is linaro compiled

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] blively2:
Confirmed working, as well! Ditto on the rom request! :thumbup:

Sent from Orlando, Florida...
[Captivate Android Development] prbassplayer:
Ya I've used it. And rom wise to "port" (its a sad excuse of porting ) you need to swap keylayout folder in system/usr/ and modify the build.prop. The last one isn't really necessary but just to get the ID's right.

Edit: and if it wasn't clear kernel needs to be swapped.
[Captivate Android Development] mindphaser2k9:
Booting fine, thak you sir! :good:
[Captivate Android Development] bobapunk:
Ok, should I even try .85 or should I just flash .86?

If .85 works for me, would there be an advantage to the 3.4 drivers?
[Captivate Android Development] shimbob:
.86 works fine here where .84 bootlooped.

How about creating .862 which has the 3.4 drivers but is not linaro-compiled to narrow down the issue?
[Captivate Android Development] TheSoaresan:
Guys, maybe its the way you install the zip. Some people don't wipe dalvic, some do. I've found that some kernels seem to boot loop after wiping dalvic..
[Captivate Android Development] blively2:
Tried both ways...both ended in boot loops. The latest devil kernel flashed flawlessly as all previous did (.81 and older).

Sent from Orlando, Florida...
[Captivate Android Development] prbassplayer:
The new driver where making ppl loop. Something was up with it.

I tried wiping caches (dalvik included) wiping initd and not wiping anything. Had nothing to do with that. .86 worked just fine. If I had to guess something Der Teufel might have overlooked. Not trying to sound like a ars. What Der Teufel does is amazing and have nothing but great respect. ;)
[Captivate Android Development] geokilla:
What? Really? I remember back when I was playing with I9000 ROMs, all I did was swap kernels.
[Captivate Android Development] prbassplayer:
Keylayout has to be modified because of the softkey difference. I've had issues with softkeys not working if I don't, but not always.
[Captivate Android Development] xtracrispy69:
hey guys,

I used devil with the MyUI package. Now I'm on the miui.us version. It runs standard icy glitch. Now I know there are a few versions of devil on the front page. I don't mess with any settings as many folks do. I've run a few kernels before but this one has a million options to customize. If I wanted to run this again, what version would I download and not need to mess with anything? Basically want to flash and let it do it's stuff.
[Captivate Android Development] oriveradel:
Devi3_0.79_cappy_CFS_BLN_VC_20120618.zip
[Captivate Android Development] zuN!:
0.86 works perfectly well.
[Captivate Android Development] melvinaury:
I have same question, I'm using AOKP 39 and the .85 install and work perfect. Then wish one is better on this case.
[Captivate Android Development] steelcity:
does it matter which zip is use the (cmc or vc) if i'm running slim ics?

also i've never flashed a kernel by itself before do i need to clear anything first or just flash it?
[Captivate Android Development] Nick0703:
It doesn't REALLY matter which zip you use. If you want Voodoo Color, use the VC version, if you want Cyanogenmod Color then use the CMC version. And also you don't need to clear anything before flashing a kernel, just flash it and you should be good.
[Captivate Android Development] bobapunk:
Setting do not seem to sticking after reboots with .86. Has anyone else noticed this?
[Captivate Android Development] lordxentris:
Yeah same here, after reboot, some settings don't stick.
[Captivate Android Development] prbassplayer:
Specifics?
[Captivate Android Development] lordxentris:
Screen off - min frequency

fast charge

vibration intensity
[Captivate Android Development] prbassplayer:
I'm pretty sure fast charge is meant to do that. Other 2 testing.

Edit:

Screen off min freq worked

Fast charge, as I said meant to not stick. I could be wrong.

Vibration intensity worked

Using 0.86 on F4K mod R4 with Version 3 of Devil app
[Captivate Android Development] bobapunk:
I/O scheduler, Live OC, GPU Overclock, Touchwake. Probably some others as well. I set NSTools to use a script to get some settings to stick, but I never had to do that on previous versions.
[Captivate Android Development] prbassplayer:
Never had this issue. Everything is working except known, Like GPU OC not sticking after reboot, etc.
[Captivate Android Development] bobapunk:
I have everything sticking now but GPU and "swappiness" (by using int.d in NSTools). I think my problem is something else thought because my default keyboard is also resetting on reboot. I did use TiBU to move some apps to SD... I wonder if that is causing my issue...?
[Captivate Android Development] oriveradel:
Yes it does, however; battery life for me has been a lot better with version 079
[Captivate Android Development] dongfangri:
I have the same feeling, Battery life with 0.79 is better.
[Captivate Android Development] takeoutttt:
TiBu can sometimes a major pain. Restore with user apps only not eith system apps to avoid such issues :)

Sent using Legend 4 ICS with Corn Kernrel - Samsung Captivate
[Captivate Android Development] xtmp:
flash problem

Recently on one of my cappy started having problems described here:

http://xdaforums.com/showpost.php?p=27819533&postcount=2374

Running on SlimICS 4.0, flash devil Kernel 0.81, and went to ASS - StartUp tweaks, screen was black ~ 5 sec. Then slimICS got root permissions, 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 devil 0.85, semaphore 1.2.5 - result the same.

Then I decided not to go into this evil menu. But by setting the wrong overclocking settings in Nstools the phone hung up, and I decided to reset to default nstools settings through the menus in the cwm. The result of the phone hanging on the Slim logo, again.
Flashing Slim with a wipe and without, running the kernel cleaning script from lippol not solving the problem.

Only flashing CM9 with formatting, and then slim is resolving 4 me.

I thought it was a firmware bug, or kernel, but opening the boot.txt file, I saw the following:

look attachment from "Bad block... 43..."

It seems that the memory is beginning to break down? :crying:

my eMMC chip

Type: MAG8DE

Revision:0x15

DerTeufel1980, could you please to look this post:

http://xdaforums.com/showpost.php?p=27074278&postcount=69

They say that the problem is familiar, it is necessary to correct some libraries, for the "right" works with the memory...

View attachment 1154308
[Captivate Android Development] DerTeufel1980:
afaik having bad blocks is almost normal. having them, too.

this happens to flash devices, and this is why there is the "reservoir" partition.

the link you provided is not related to our device i think. at least, i don't have the driver file they are talking about.
[Captivate Android Development] dchawk81:
Can we get a "back to defaults" script for CWM? I fudged with my settings and battery life is now atrocious, but I don't know what settings take it back to zero to start over.
[Captivate Android Development] DerTeufel1980:
most settings get applied through the files located at /data/local/devil

if you just delete them, they get recreated at the next boot with the default settings (expect the ram/swap settings file (hope i don't forget one right now)).

everything else should get cleared by cleaning init.d, or resetting nstools
[Captivate Android Development] dchawk81:
Awesome, thanks. How do I clean init.d? Do you mean delete it?
[Captivate Android Development] jerkysh:
From recovery>DEVIL, there's a option to clear init.d directory
[Captivate Android Development] Nick0703:
I had the same problem twice last week except I got it when I disable the Bluetooth kill option. I had to reflash AOKP B39 with formatting to be able to boot into system.
[Captivate Android Development] bobapunk:
Weird, my phone just did that yesterday. I was testing the new kernel and was having problems having some of the settings stick through a reboot. I set NS Tools to use init.d to get settings to stick and it worked. After a while I wanted to try without init.d so I un-checked the box in NSTools, booted into recovery and cleared the init.d through the menu. Then my phone would not reboot. I tried re-flashing the ROM (SimplyAOKP6) with no luck; I would just get stuck on the boot animation. I had to do a wipe/reset to get it back up and running...
[Captivate Android Development] DerTeufel1980:
Weird... You all are using slim ics?

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] bobapunk:
No, I am on SimplyAOKP6.
[Captivate Android Development] xtmp:
DerTeufel1980, I would venture to suggest that the problem in the datafix script, because after wiping /data, phone boots normally. Also don't understood why the slims init.d scripts are moves in the backup folder after installing the devil kernel, and I has been noticed that datafix and S90volume "some times" moves to backup folder too... So I think phone not boot when something wrong with /data or /datadata...
[Captivate Android Development] prbassplayer:
The datafix initd scrip does nothing unless enabled. It moved all the init.d scrips when you flash because that may cause loops if you don't
[Captivate Android Development] xtmp:
So, after installing devil kernel I must to move slims scripts back by myself ?
[Captivate Android Development] prbassplayer:
Yup you can try. Keep in mind it might loop so do it carefully. My 2 cents
[Captivate Android Development] Nick0703:
No, I got it both on AOKP B39 and AOKP B40.
[Captivate Android Development] bobapunk:
Worst Part is that even though I just did a TiBU yesterday, I did not move the backup off the SD so the factory wipe erased my backup...

I need to get in the habit of making a backup in recovery every time I flash something...
[Captivate Android Development] xtmp:
Ups, I did it again...

Now I flashed clear Slim 4.1. Then installed all my apps, did my setting, and time to time rebooted cappy about 20 times. Everything was fine.

Then I flashed devil .86, setup nstools, and other devil kernel config and time to time rebooted cappy about 20 times. Everything was fine.

Then I copied Slim init.d scripts from /system/etc/init.d/backup to /system/etc/init.d/. First reboot was fine, but second one....phone "just get stuck on the boot animation."

I have working cwm now, launch AROMA filemanager, how can I look what happened?

PS. Now init.d has following scripts:

00banner

00check

01zipalign

02sysctl

05freemem

05zram

06removecache

07fixperms

09cron

10sdboost

S30datafix

S90call_vol

PSS

is it ok that there is no /datadata folder in root and

data file in /data folder is "Symlink error"
[Captivate Android Development] mindphaser2k9:
One of those scripts conflicts with this kernel. My suggestion that it is 06removecache. Try to remove it and boot. If this doesn't help, try to remove other scripts one-by-one and you will see which one is wrong.
[Captivate Android Development] xtmp:
nope... deleted it all, and still nothing...

ps//

fracking android, where is the /var/log/messages ? or other dmesg :)
[Captivate Android Development] baconatorXVI:
Here's a response from a PM i recieved about my Antutu benchmark scores. This is meant to be a reference to others who are working to squeeze optimal performance out of their captivates.

The highest score i was able to achieve was 4044 when i was on 1.508 ghz.

I've had lots of experience over clocking desktops computers, i started when i was 14 years old or something.

I've been testing mostly stock settings between devil .86 and semaphore 1.2.5sc and devil keeps coming out on top with it's scores. not trying to start a war, but devil is just faster. don't get me wrong i love semaphore.

Overclocking and having the least apps active is the key.

Overclock at your own risk!

My settings, SIO, Conservative governor, Frequency at the 1300mhz step, live OC at 116%(this yielded 1.508ghz). I had UKSM on(whether on or off didn't seem to make a difference during my tests), i had the GPU overclocked to 250mhz. I was using the XL mem version.

I had intended on running more tests on the big mem version but the constant reboots got tiresome.

BE VERY CAREFUL WHEN YOU ADJUST YOUR VOLTAGES! too much is bad! Heat and overvolting is harmful!

Voltages:

Arm voltages for 1400mhz it's 1.475, for 1300 its 1.450. For the Int Voltages at 1400mhz it's 1.25, for 1300 it's 1.225.

Something strange i noticed was that whenever i would do a odd numbered live OC i would get major instability... 116% was much more stable than 115%. weird huh? also i am pretty much unable to get a stable live OC of more than 116 regardless of the frequency step.

the key is to keep finessing it and carefully and incrementally change things till you find a nice sweet stable spot, other phones can achieve more live OC.

for example my phone is almost always on this setting for everyday use: SIO, Conservative, Freq OC at 1200 and Live OC at 116% yielding 1.392ghz. with a bit of voltage increase this has become my favorite setting, i always use this setup.

Warnings about heat. voltage increases mean more latent heat. your phone is a closed system so the heat gets locked in easily... one simple way to manage it when you feel the sd card slot warm is to press the SIM/Sd slot to your lips and blow air through the phone, this will help cool it down. another way to manage the heat is to do this

I borrowed a cooling fan from my gaming computer and set the phone up on it with the battery cover off. this really helped...

higher scores are achievable... just keep tweaking things.. I deleted all my user apps so nothing would run in the background and that did helps my scores a bit. I bet wiping the SD card would improve read/write speeds incrementally...

have fun tweaking!

Hope this helps!
[Captivate Android Development] white00gt:
So you might be able to answer my question - I have not adjusted the voltage but I have it overclocked to 1200 , now when I'm talking on the phone it gets very hot and my battery will drain significantly , so is this actually the kernel causing the heat? if so how do I correct the problem , burning the hell out of my ears

---------- Post added at 07:05 PM ---------- Previous post was at 06:52 PM ----------

I'm using Team Nyx RC 5 and had no issues with .084- flash went like normal, .86 went fine as well
[Captivate Android Development] DerTeufel1980:
You could try to grep /data/user.log

Maybe there is something in it what helps.

You also could run logcat while booting.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] baconatorXVI:
well even though you haven't adjusted the voltages you still are using more than stock the voltage otherwise you wouldn't be stable at 1200mhz. in NStools under voltages "default" should be checked since you said you never changed the voltages. well if you look at the list the 1200 mhz step still has more voltage added.

it's not necessarily your kernel... if you have say the performance governor enabled (the one that behaves like a light switch, either 100% or not) it will always run the fastest frequency, which entails the highest voltage, which attributes to the highest heat. that's why i run the conservative governor, because most actions only require like 400mhz to be smooth. why make your phone work harder/hotter/faster if it doesn't need to?

try switching governors, that may help.

as i said it's probably not your kernel, all kernels use a similar voltage stepping chart in NS tools.

another shot in the dark would be to go adjust the max screen off frequency. if you set your max screen off frequency to something like 800mhz you'll use much less voltage and generate less heat.

Being far away from a cell tower will also affect how hard your phone has to work to send radio signals back and forth. the stronger the cell signal the less power gets sent to the radio chip. this probably doesn't really affect the heat, but more your battery drain.

These reasons are why battery life is such a subjective experience... why so many people don't like hearing about how one guy got like 24+ hours on a single charge. if your tweaks affect your individual battery life then that is a victory for you.

I remember before i changed anything, when i was completely stock my phone would get warm on my face when talking on the phone for extended periods of time... it's just a habit of electronics to run warm...
[Captivate Android Development] pizz0wn3d:
alogcat from the play store works great for logcats.

Herp derp Captivate Tapatalk 2
[Captivate Android Development] xtmp:
but it works only when phone is loaded ? :)

I'm trying to to find out why the phone not booting...
[Captivate Android Development] pizz0wn3d:
Oops. Pardon me, I got mixed up in which thread I was in >.>

Yeah, alogcat might not be so useful for you.

Have you tried the nexus drivers? I want to say we had to switch over to those when we upgraded to ICS, but my memory is terrible and im not completely sure ;P

Dont forget to reboot after installing drivers as well ;P

Herp derp Captivate Tapatalk 2
[Captivate Android Development] DerTeufel1980:
today, you are getting the new test build at first ;)

- recoveries should work fine now again (mounting to pc, backup/restore of nandroid)

- making a backup with cwm should use less battery now (upstream fix)

- usb transfer speed should be ~ 9 mb/s

- compiled with BFS as cpu scheduler for testing

- kernel compressed with xz (maybe a little bit faster boot time)

-lowered voltages of RAM and display
[Captivate Android Development] tkjeeper:
Are you backing off the linaro builds DerTeufel? Just curious, awesome work, thanks so much. I'm running my own ported version of FK4 which is Linaro compiled and your latest kernel and blazing fast, thanks so much for your hard work.
[Captivate Android Development] mindphaser2k9:
Incredible! :good:
[Captivate Android Development] DerTeufel1980:
no, i am not backing of linaro. i just did not mention it, because it is not changend (still linaro). the file size is as small as it was before linaro, because of the xz compression (if you were reffering to this). :)

anyone already tested usb transfer speed?

Edit: forgot to mention this:

I have switched to the latest datafix script, to activate it, there now is a file at: data/local/devil/datafix

If one writes the value 1 into it, datafix is activated at next boot. For me, it seems to be not working as good as the old one. Only 22 mb free at /datadata. Not sure, if I did something wrong. How are your experiences with the latest datafix in general, and with my kernel?
[Captivate Android Development] jerkysh:
just did, awesome! got 11,9 MB/s
[Captivate Android Development] xtmp:
Ok, I\m back :) Now I found correct adb usb drivers and installed it! So now I have logcat.

So I installed last Slim 4.1, did my settings & installed my soft. Then I installed .86 devil kernel, and after reboot many apps started forclosed. I\m run logcat and found this:

14:59:35.732 Warning SharedPreferencesImpl 2116 Attempt to read preferences file /data/data/com.jrummy.root.browserfree/shared_prefs/com.jrummy.root.browserfree_preferences.xml without permission
14:59:35.732 Debug OpenGLRenderer 1909 Flushing caches (mode 1)
14:59:35.837 Debug dalvikvm 2116 GC_CONCURRENT freed 212K, 20% free 2465K/3075K, paused 2ms+1ms
14:59:35.837 Debug dalvikvm 2116 GC_FOR_ALLOC freed 64K, 23% free 2433K/3139K, paused 12ms
14:59:35.837 Info dalvikvm-heap 2116 Grow heap (frag case) to 3.347MB for 635812-byte allocation
14:59:35.838 Debug dalvikvm 2116 GC_FOR_ALLOC freed <1K, 20% free 3054K/3779K, paused 12ms
14:59:35.838 Debug dalvikvm 2116 GC_FOR_ALLOC freed 0K, 20% free 3054K/3779K, paused 12ms
14:59:35.838 Info dalvikvm-heap 2116 Grow heap (frag case) to 3.697MB for 365920-byte allocation
14:59:35.838 Debug dalvikvm 2116 GC_FOR_ALLOC freed 0K, 19% free 3412K/4163K, paused 11ms
14:59:35.965 Debug dalvikvm 2116 GC_CONCURRENT freed 852K, 30% free 3036K/4291K, paused 1ms+2ms
14:59:35.965 Info SqliteDatabaseCpp 2116 sqlite returned: error code = 14, msg = cannot open file at line 27701 of [8609a15dfa], db=/data/data/com.jrummy.root.browserfree/databases/bookmarks.db
14:59:35.965 Info SqliteDatabaseCpp 2116 sqlite returned: error code = 14, msg = os_unix.c: open() at line 27701 - "" errno=13 path=/data/data/com.jrummy.root.browserfree/databases/bookmarks.db, db=/data/data/com.jrummy.root.browserfree/databases/bookmarks.db
14:59:35.965 Error SqliteDatabaseCpp 2116 sqlite3_open_v2("/data/data/com.jrummy.root.browserfree/databases/bookmarks.db", &handle, 6, NULL) failed

So, as I think it's blame datafix.

But I thought it was wrong permission of /datadata, so I rebooted in CWM and run "fix permission". Next boot cappy hangs on the logo, but I took logcat while downloading now.

View attachment 1157013
[Captivate Android Development] DerTeufel1980:
Yep seems to be datafix script... Weird, i never had this, and am also using slim ics.

Fix permission did most probably not work with this version of kernel. Does it only take a second to finish?

Gesendet von meinem GT-I9000 mit Tapatalk 2