yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] xtmp:
Slim 4.2. Flash from clear slim with it kernel.

flash 1st time without clean, 2nd time with clean, but the result is the same.

btw, looks like devil kernel wipe cache & dalvik by itself when installing. just because it wrote: "Cleaning cache... dalvik" (if I'm not confused) when installing.
[Captivate Android Development] shuyin1102:
Weird. Im on the latest 0.98.3 (with aokp and now on latest cm9 nightly) sometimes reboot into recovery takes 30 - 50 seconds, and when i reboot the phone, bootloader and kernel logo boot up twice. Dont know kernel or rom issue. Did anyone experience that?
[Captivate Android Development] dave71670:
It is random for me when it boots twice but usually more likely the first and second reboot after install. That has carried thru on all most all builds for me. Not rom specific.
[Captivate Android Development] acras:
This option for those who want to prevent EU bug and move /data to external SD
[Captivate Android Development] DerTeufel1980:
please take a look here: https://github.com/DerTeufel/samsung-kernel-aries/commits/devil3

for detailed changes.

due to making test kernels for all 4 devices, and not every test build, for every device, it is hard for me, to list the changes between different test builds.

i think 98.3 is working well so far, and i am going to release it as the next stable version soon. then there will be a detailed changelog, which shows the changes bnetween the both stable ones.
[Captivate Android Development] q659503934:
@DerTeufel1980

i found two path from here ,i guess it's for bigmen cm7 kernel ,can i use it on other kernel?

https://github.com/DerTeufel/cm7/commit/cc02fadf45cfdaecc67c7e728c29f120a341719a

https://github.com/DerTeufel/cm7/commit/c75434f3665d4a741aa6c9d6465e55a171ba6839
[Captivate Android Development] DerTeufel1980:
This is the bigmem patch from cm9, just used for cm7.

What other kernels? The rom also has to support it.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] ninjah:
Awesome!! Good battery life on latest build
[Captivate Android Development] ninjah:
And deep sleep not working when deep idle enabled
[Captivate Android Development] q659503934:
i just build a kernel for cappy from Glitch's source with two patch,now there is 380mb available, 720p recording and playback work well:D

but i have a question

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC1 (5000 * SZ_1K)

this is from devil2 source but in devil3 i saw it was disable

do you kown S5PV210_VIDEO_SAMSUNG_MEMSIZE_FIMC1 work for witch part?
[Captivate Android Development] Monfro:
I confirm that 98.3 is working great!!

Less ram used than 98.2 and maybe smoother.

Working better also than the other last test kernels.

Sent from my Captivate
[Captivate Android Development] DerTeufel1980:
If it wouldn't, many people would complain.

Glitch source really is awful. The kernel is running well, but if you ever want to understand or revert a commit from him, you're lost, because he never commented his changes well.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] BitteredBro:
+1

Coming from Semaphore got bootloop after installing Devil's .98.3. Tried flashing from devil's 0.79 and same thing. I think it has something to do with Slim 4.2, because I'm using that ROM too.
[Captivate Android Development] prbassplayer:
I'm on slim 4.2 no problems. Dirty flash slim again then flash devil.
[Captivate Android Development] lordxentris:
Running Slim 4.2 on my cappy with Devil3_0.98.3, So fair, Performance is better and no boot-loops, thank God. Checking whether settings stick.... will update this post.
[Captivate Android Development] lavero.burgos:
0.98.3 running great here as well, infinitum LBR ROM.

~ V
[Captivate Android Development] Nick0703:
Are you using Devil Kernel Manager app?
[Captivate Android Development] xtmp:
yes, but last time I installed clear Slim, with formating system & data, then flashed .98.3 & got bootloop.
[Captivate Android Development] DerTeufel1980:
Did you want to boot recovery?

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] xtmp:
I don't know how to get boot.txt when phone is bootlooping, so I had to boot cwm, then launched avrora, copied boot.txt to sdcard and download it to PC.
[Captivate Android Development] tallsilver:
98.3

Just flashed AOKP 40 with 98.3 and all seems to be well for now. Only issue I have so far is all the ringtones are doubled. I remember seeing how to correct it but I'll have to find it again.:crying:
[Captivate Android Development] fractaline:
Clear data on media storage and reboot. That should do it.

0.98.3 has been smooth and fast so far.

Thanks for continuously feeding us goodies! :D

Sent from phone with app
[Captivate Android Development] DerTeufel1980:
the "problem" is, that boot.txt gets written on every boot, also boot to recovery. i have to work around this next time
[Captivate Android Development] geokilla:
Running 0.98.3 right now and it's pretty bad for me. First boot, it just froze on my launcher screen. 2nd boot, I was in Whatsapp and it froze. Then the phone vibrated for over a minute. 3rd boot now and so far so good. Hopefully it holds.... Note this is with a 114% LiveOC, which I have always used.
[Captivate Android Development] prbassplayer:
Had to drop to 110%from my normal 114%. I might be able to mess with voltage and stable it out but on vacation. Lol
[Captivate Android Development] baconatorXVI:
Interesting... I haven't seen any problems with 116% and frequencies added.(1.392ghz)

I have noticed though that certain live OC values give LOTS of unnecessary trouble, like i can't run 115% at all. (at least since the last time i tried...)

Perhaps try different values?

.98.3 has been stable for me so far
[Captivate Android Development] :
Yep, very stable here too. No live OC, but running at 1200. Battery drain is a little worse, but probably because I haven't cycled yet, and I am still getting >3 hours screen on.
[Captivate Android Development] geokilla:
That's weird.... It can do 116% but can't do 115%?

Anyways, I just got a sleep death...
[Captivate Android Development] cnu4u:
I am unable to mount my internal sd card... when I plugin usb cable to PC, I get pop-up 'USB Connected' and I get a option to 'Turn ON USB Storage'. When I click on it, I see hard-drive symbols on PC.

After latest update (0.98.3), I unable to mount it. Any ideas?
[Captivate Android Development] blacklist:
Turn off 'Fast charge', you'll be able to mount it again.
[Captivate Android Development] carlosgardel:
GPS performance in Devil

After lots of time with bad GPS in the Captivate like most of us I have very good GPS performance now with CM9 and modem UGKG3 in Puerto Rico. I was trying Devil Kernel 79 and 86 and everything was very good but not the GPS. I like the Devil and tweak settings but GPS is important to me. I gone back to stock kernel and is good again. I really like Devil Kernel, can I do something to fix it?

And yes Im using the H3llstorm_GPS_Fix in the forum.

Thanks!!
[Captivate Android Development] baconatorXVI:
Well that's been my experience at least. Each phone is different though
[Captivate Android Development] azunino:
I compiled your kernel with CONFIG_HAS_BROKEN_SD=y and flashed over CM9. As expected /data gets mounted on the second partition of the external SD. However, the first partition of the external SD gets mounted as /emmc (easily fixable by reversing the mount points in vold.fstab).

There is, however, something I do not fully understand. When CONFIG_HAS_BROKEN_SD=y the internal SD (on a fully working phone) cannot be mounted from CM9, but it works fine from recovery (as /emmc). Perhaps the default CM9 vold.fstab now is incorrect because it expects /devices/platform/s3c-sdhci.2/mmc_host/mmc2, but (pure theories from now on...) this device is no longer .../mmc2? maybe mmc3?? considering the order in which s3c_device_hsmmc0 is now on

platform_device *aries_devices[] __initdata (https://github.com/DerTeufel/samsun...a19c2d25a3/arch/arm/mach-s5pv210/mach-aries.c)

BTW, I'm really interested on this because it will enable us to use any ICS ROM on fully working phones (or not) with /data on the external and /sdcard also on the external, but still capable of accessing the internal SD whitout requiring my ugly ROM patcher (which works fine, but your solution seems much more elegant)

thanks!
[Captivate Android Development] They Drew First Blood:
Mount SD

Check this setting: boot into Recovery, go into the DEVIL menu, go into the USB Mode Settings menu, and set your USB to Mass Storage Mode. If it is set to MTP mode you will only be able to access the SD through the Recovery/mounts and storage/"mount internal + external storage" feature, and not while the phone is fully booted.
[Captivate Android Development] lavero.burgos:
.

~ V
[Captivate Android Development] bobapunk:
I wonder if this is what caused my issue a few days ago...

I ended up factory resetting my phone to get it to see apps on the internal SD.
[Captivate Android Development] melvinaury:
Hi I'm from PR too and I had excellent GPS and also I'm using UGKG3 modem. The difference that I has is that I use the latest test version .98.3 and yes I use the H3llstorm_GPS_Fix. What file do you have, I always reading the thread and they already post different releases. I always have 5 to 10 meters accuracy.
[Captivate Android Development] Thunder22:
Was wondering if .98.3 kernel is still jellybean compatible after the changes were reverted?
[Captivate Android Development] prbassplayer:
I would assume unless stated otherwise it is.
[Captivate Android Development] DerTeufel1980:
i think you are right about mmc2 and mmc3. could you try what happens, if you place the internal sd to the second position, instead of the third?
[Captivate Android Development] DerTeufel1980:
yep, that's right. it is still supported.
[Captivate Android Development] carlosgardel:
Devil GPS

Hello!! Im using GPS-mod(8NTP) now but I used H3llstorm_GPS_Fix before with the same results, very good in CM9 with his original kernel but when I changed to Devil 79 and then 86 not good. Changed to CM9 plain and is very good again.

Thanks!!
[Captivate Android Development] CheesyNutz:
i too have notice my gps a bit more flaky on the killer rom
[Captivate Android Development] shuyin1102:
i dont stare at gps but confirm that rarely see the gps works on Devil kernel
[Captivate Android Development] CheesyNutz:
mine works but its drops lots when i need it lol
[Captivate Android Development] Ir0nLy0n:
My GPS has never worked well. Not since the day I bought the phone. (Actually the reason I rooted and flashed in the first place) :rolleyes:
[Captivate Android Development] gratian556:
FWIW, My GPS works reliably on Devil 0.79. It actually works great on Semaphore and Glitch also. I found that once I started using a properly modified gps.conf my troubles ended. I insert the modded gps.conf in the ROM, flash, use GPS status app to clear and download agps data. I then wait about 60 secs for it to find and lock satellites (usually 6-7). Then I open up Sygic and am good to go.

I only use GPS status app once after a flash. YMMV
[Captivate Android Development] Ir0nLy0n:
Tried a modded GPS.conf. Best I got was 3 satellites. Maybe my area maybe my phone. Did you mod the GPS.conf yourself or where did your get it from?
[Captivate Android Development] gratian556:
I pieced it together based on work of H3llstorm, mikel.canovas and Xenova.

Critical pieces were adding correct ntp servers and agps server data based on region.
[Captivate Android Development] Nick0703:
I think we're getting a little bit of topic here with the GPS thingy.
[Captivate Android Development] melvinaury:
I second that, please just kernel topic. There is a thread with the gps config file and info regarding the configuration of the file by location.

Oh men I'm also of topic. LOL:eek:
[Captivate Android Development] cursedwave:
Has anybody been able to get the refresh rate option to stick at 60hz on the latest test version? Mine keeps going back to 56hz no matter what I try. (Devil app, init.d file, editing the file at sys/kernel)
[Captivate Android Development] DerTeufel1980:
Sorry, have disabled it, cause it wasn't working.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] cursedwave:
Oh, that would explain it. :)
[Captivate Android Development] acras:
DerTeufel1980

In nightly changelog

implement noise suppression for phone calls (1/2)

2012-07-06 at 13:39:02 (android_frameworks_base)

Phone: implement noise suppression for phone calls (2/2)

2012-07-06 at 13:38:48 (android_packages_apps_Phone)

What do you think? Will you implement this in your great kernel after pawitp patches cm9 stock kernel?
[Captivate Android Development] jerkysh:
I think this option is for phones that support this feature :)
[Captivate Android Development] acras:
Cappy does support this feature. Pawitp is working on the kernel patch.
[Captivate Android Development] cnu4u:
Sure... if its going to work
[Captivate Android Development] carlosgardel:
THiNGY

Dont worry. I end the THINGY now, the only different thing that make my GPS dont work is the Devil Kernel so thats why I ask here.

Thanks for nothing.
[Captivate Android Development] geokilla:
There is a software noise cancellation and hardware noise cancellation. Apparently our Captivate has the hardware option. But software noise cancellation is better than no noise cancellation!
[Captivate Android Development] DerTeufel1980:
Gps is working for everyone on every 4 devices. Also, I am using the same gps as pawitp and stratosk.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] aduka:
DerTeufel1980, expect a new version of the kernel with the VC?
[Captivate Android Development] baconatorXVI:
Hmm... well, I've recently done a factory reset and re install of slim 4.2 I can't seem to be able to flash directly to .98.3 at all. I get bootloops, but recovery still works.

I had had devil kernel manager installed on my first try, i froze it with titanium backup, but that made no difference during the following tests.

flashed from .79 to .86 which worked. .86 to .98.3 did not work (bootloop), back to .86.

.86 to .91 worked. .91 to .98.3 did not work.

I can't seem to get back to .98.3. do i need to fully uninstall devil kernel manager? i remember someone posting about that awhile back.

recovery works for .98.3.

I'm kinda stuck at what to do to contribute other than point out that there's an issue. .98.3 worked fine before I did the factory reset and re install. I don't suppose re downloading the kernel would make a difference?

Currently back on .79 :/

edit:

so re reading again, i suppose it's being worked on then i guess? that's weird why flashing a fresh version of slim makes bootloops.

Thanks so much for all your hard work DerTeufel1980
[Captivate Android Development] DerTeufel1980:
Sorry for this. I have found and fixed the bug yesterday.

The problem is, after factory reset, there is no devil config folder at data. In this case (because I am using slim myself), the kernel tries to apply bigmem, if the rom is slim ics. Good so far, but I have made a typo, and applying fails, so it tries over and over again.

Workaround is, flash an older kernel, boot up, and create the file /data/local/devil/bigmem

After this the bootloop should be fixed.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] baconatorXVI:
Fantastic! I'll try it now ! :)

EDIT: flash an older kernel, Use Devil Config, set either bigmem or XL on, flash .98.3!!!

it worked!
[Captivate Android Development] xtmp:
yes, it works! Thank you!
[Captivate Android Development] DerTeufel1980:
new test build:

it is just namend 0.99 because the "older" 99ers were meant to be jellybean wifi test kernels.

compared to the 0.88 test kernel, i have done/added this:

- wifi driver from galaxy nexus

- fixed a kernel wakelock bug

- automatically set xl mode for slim ics (if no /data/local/devil/bigmem file is there)*

- added io scheduler (sio, vr, cfq, noop, deadline, fiops) to initramfs, they now/soon can be added to the corresponding file at /data/local/devil/ or with the devil apps

- added touchwake and touchwake timeout to initramfs (see above ;) )

- fixed some typos in the initramfs

attention: because of the uploading of many kernels is taking a long period of time, i have decided to upload them to the ftp server. to save more time, all kernels for all devices are placed in the same folder. please pay attetion downloading the right one.

because of the time savings, i have also uploaded the *.tar files and both color versions (uploading takes longer than compiling....)

http://rootaxbox.no-ip.org/divers/test/

* if there are more roms, which are "bigmem" patched by default, please tell me their ro.build.description or something else unique, which i can grep from build.prop
[Captivate Android Development] DerTeufel1980:
@ tkjeeper: please try the kernel above for your jb port. I have forgotten to mention it this time, but all kernels are supporting jb (as far as it is possible at the moment)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] tkjeeper:
Awesome! I'll giver a go! Thanks man!

Edit: No luck Der Teufel, same results as before, no boot past rom boot screen. Tried everything again. Thanks a tonne, you rock.
[Captivate Android Development] Nick0703:
So if I understand this correctly, the latest test kernel should reduce the bootloop problem?
[Captivate Android Development] tkjeeper:
? What bootloop?
[Captivate Android Development] Nick0703:
There was some typos error in the previous test kernel where when you reboot your phone, your phone can't boot into the system. You just go into an infinite bootanimation loop.
[Captivate Android Development] dave71670:
@tkjeeper I was able to get jb to the starting apps screen with this kernel. Was this the same experience for you? Jus curious.
[Captivate Android Development] tkjeeper:
No, I'm using a ported version of jb, it didn't work for me. It boots with the kernel that came with the rom, that's it for me anyways.
[Captivate Android Development] dave71670:
I am using a ported version as well. I ported version 1 also and am going to try that with this kernel as well. Just out of curiosity to see if it will boot.
[Captivate Android Development] tkjeeper:
I thought you got it booting? Did you mean you got the non-ported version booting with 99? If so was wifi working? That's the reason for the new kernel?
[Captivate Android Development] dave71670:
Ok, v2 would only go to starting apps with this kernel. V1 with this kernel on the other hand boots AND wifi works. Woo Hoo! Working on gsm now.
[Captivate Android Development] tkjeeper:
Are you freakin serious? There's no sound tho right? You have working wifi AND gsm?
[Captivate Android Development] dave71670:
No sound. Have only wifi for now and am trying to get an apn saved for network.
[Captivate Android Development] tkjeeper:
Incredible!
[Captivate Android Development] fractaline:
is that v1/v2 as is? Or have you modified it at all?

Sent from phone with app
[Captivate Android Development] dave71670:
Ported v1 and flashed with cappy .99 devil kernel before booting. Ported v2 but it would not boot with cappy kernel. No other changes yet.
[Captivate Android Development] tkjeeper:
but v1 has no wifi toggle at all for me?
[Captivate Android Development] dave71670:
Has it for me. I am making a backup of what I am using and then flashing back to ics. I forgot to edit the build prop for the red screen problem and can't do it from rom side as I have no root with jb at the moment. Would it do any good for me to send you my backup file?
[Captivate Android Development] tkjeeper:
No thanks, good work tho.
[Captivate Android Development] cnu4u:
Very initial feel of new build .99 seems very smooth... thanks
[Captivate Android Development] mirrored:
0.99 is great for me so far with slim 4.2
[Captivate Android Development] zuN!:
0.99 not working great for me so far. I'm stuck on the I896 boot screen (in most of your cases the AT&T boot screen) and it doesn't go any further than that. Wiped Dalvik Cache + Cache prior to flashing the kernel (VC zip version).

Edit: Flashed the .tar of the 0.99VC version, it works now. Maybe I had a corrupt download.
[Captivate Android Development] DerTeufel1980:
Have you changed the build id in build.prop? The kernel is looking for it to decide whether to boot jb or not.

Ah, i also could flash v1 without factory reset, but i had to do factory reset with v2.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] dave71670:
Does .99 change modules folder in rom when it is flashed?
[Captivate Android Development] BitteredBro:
Hi. I´m trying .99 with CM9 nightly 0703. I couldn't install it at first, but as someone sugested, flashed an older version before .99 and then it worked.

Out of the box the kernel works great but I'm having troubles with the OC. Using Devil Kernel Config app I can set it past 110% but then I get an instant reboot and somethimes bootloop. That didn't happened with the older versions nor with other kernels. Probably it has to do with the app itself and not with the kernel.

I'll try using NSTools or the other Devil app to try isolate the issue.

Thanks for your great kernel, DerTeufel1980.
[Captivate Android Development] Monfro:
Kernel 99 VC works really great on aokp milestone 6. It is smooth and ram management is really good (i use 260mb swap).

Sent from my Captivate
[Captivate Android Development] They Drew First Blood:
Modules folder

I flashed my copies of .91, .98.2, .98.3 and .99 in succession. Same four files in Modules folder in each version: ansi_cprng.ko, gspca_main.ko, nls_utf8.ko, scsi_wait_scan.ko. .91 had larger file sizes in it than the other three subsequent versions; starting at .98.2 the files had shrunk, and then grew slightly larger each consecutive flash. It looks to me that the files are just updated each flash, with no files removed and no additional files added. I use the CMC versions. Hope that helps...and that I interpreted your question correctly. :)
[Captivate Android Development] baconatorXVI:
I haven't gotten to flashing .99 yet, but lie oc is subjective to the quality variances in each phone. Some people can get 130% live oc, others not nearly as much. Also sometimes live oc doesn't work well on some frequencies. For example 115% is much more unstable than 116%. Wait, you said previous versions worked, nvm. It's probably an app problem.

I'd agree try ns tools

Perhaps restore the app with no data?
[Captivate Android Development] mirrored:
are there any known disadvantages to using fast charge? been using it for a few days and its amazing, almost too good to be true
[Captivate Android Development] baconatorXVI:
Perhaps i got a bad download when i installed the .99 zip. I got incredible instability l. Home screen kept crashing as well as live wall paper.

I'll try the .tar later

Anybody else have issues with the .zip?
[Captivate Android Development] blively2:
No issues whatsoever...I'm on simply aokp

Sent from sunny Florida...
[Captivate Android Development] brianray14:
Flashed 99 also having no issues. I did notice that some launchers work better than others. Go launcher was laggy and annoying while nova is extremely zippy and responsive. Just my two cents
[Captivate Android Development] blively2:
I have to agree with you on the speed of Nova; however, that may be more of a rom and launcher issue as opposed to a kernel issue...I dunno...

Sent from sunny Florida...