yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Liv33viL:
After finding incompatibilities with DK 1.4.1 and PA 2.12 / 2.13, I notched backed down to PA build 2.10 which appeared to work pretty decently with DK 1.4.1. Just when I finished loading m nandroid backup of PA 2.10, DK v1.5.2 was released so I figured I'd give 1.5.2 a shot on 2.13, being as the stock PA/CM kernel lacked some features that I typically use.

Long story short... I got DK 1.5.2 working well with PA 2.13, for the most part, but can't get the I/O scheduler to or other kernel / memory management features to stick / work. I'm stuck with the cfq scheduler while rather preferring to utilize the noop scheduler. Also can't get the minimum CPU frequency to bind with 100mhz, its stuck @ a minimum of 200mhz The Devil Kernel config app crashes and power boots the device by just having it installed, without even attempting to open the app. I typically use System Tuner Pro to make my kernel and memory tweaks, as well as edit my prop files. STP now works initially, but after a reboot, it's rendered unstable and severely bogs down and crashes the device. I'm not sure if this is a DK issue, a PA issue or a CM 10x issue. I've been spending the last 2+ days trying to figure it out. In the meantime, I have uninstalled STP and the Devil kernel config apps from my system and have reverted to manually editing each tweak where I was able.

I haven't tried using Set CPU or Voltage Control Extreme for the scheduling or CPU bindings either.

Anyway, just figured I'd post my findings in this thread being as I see some cross chatter with the DK and the PA ROM here.

Peace-
[Captivate Android Development] :
Good luck forcing MIUI to switch...
[Captivate Android Development] swayjd:
Not sure about battery cause mine is acting up on me but performance wise, I feel like 0920 nightly works better on its own.
[Captivate Android Development] DerTeufel1980:
Have you verified, that it isn't an issue with superuser? It was/is broken on cm10 nighties, and pa is using most of its source. Please install super su, and try again

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] Liv33viL:
Superuser is one of the first things I verify. I began replacing Superuser with SuperSU Pro back on PA build 1.99i anfter the binaries have been updated. All verification for root access verified.

I finally got the I/O scheduler to the one I prefer and the min CPU frequency I prefer, by way of changing the permissions on select files and folders in the root and /system directories, then manually editing the appropriate files. Kernel Config 1.9.1 still locks up, so I don't use it, as well as STP still hoses the device on this build with this combination.

Anyway after some memory tweaks, and some build prop altering, the device is running nicely, very fast and stable on PA 2.13 with DK 1.5.2. Every so often I get some slight lag coming out of Deep Sleep Mode, but I'm currently tweaking the governor parameters, CPU thresholds in different states and fine tuning the memory management.

Other than that.... everything appears to be working as it should.

Peace-
[Captivate Android Development] n311.dunkle:
No such thing as a stupid question

Sorry if this has been answered before, but I'm tired and don't feel like reading. What are the principal differences between CM Color and Voodoo Color Kernels? Are there slightly different functions or do they just look different? And for that matter, what are the differences in Devil Config and Devil Manager?
[Captivate Android Development] tkjeeper:
Good Lord, you are the epitome of what's wrong with people. Do my work for me, because I'm lazy, you are sad.
[Captivate Android Development] vileladelima:
cHANGEs!

Hi!

I was reading the CM10 topic (http://xdaforums.com/showthread.php?t=1839977&page=36) and Monfro sad that with same two patches the CM10 will have the same partition table as helly bean.

So, the DK changes a few days ago becouse a change on the CM10, here is my quenstion, will the DK change again to run with the new cm10 partition table, or we will use the dk 1.5.2, to cm10 even with this changes?

Thanks!

p.s.: sorry, about my english.
[Captivate Android Development] Ir0nLy0n:
There should be a new kernel released with the changes. 1.5.2 still has no datadata partition so it won't be compatible.
[Captivate Android Development] melvinaury:
I think that maybe the kernel included with hellybean rom work.
[Captivate Android Development] n311.dunkle:
Come on guys, I'm not lazy. Just an idiot apparently. I should have said I tried everything I know how, read exhaustively into the night, and gave up. Y'all have always been helpful before.

I tried both versions of the installation and didn't see any noticeable differences. Is there something I'm missing? Kernel Config looks to me like it has more functionality while Kernel Manager has a better UI. Again, there might be something important I missed. Any insight?

It may be good to mention that I'm using the Aroma installer pack from the Helly Bean website. Maybe I should post on the Helly Bean thread, but this is a kernel question and figured DerTeufel1980 might answer me. The very first time I ran it I choose Voodoo color and have tried running it again with selecting CMC, but nothing seems to change. I'm thinking the kernel got flashed on first installation and doesn't matter which I select after that. I think I may know how to erase the kernel and start over, but I wanted to know the better choice before I spend any more time on this. Is it just the way they look? Or does one have different features than the other? Thanks again and sorry for being "lazy".
[Captivate Android Development] Ir0nLy0n:
The only difference between cmc and vc is the color controls. cmc is cyanogenmod color and is controlled through the advanced option in your settings menu. vc is voodoo color and is controlled with voodoo color app from the play store. The differences really comes down to personal preference.
[Captivate Android Development] n311.dunkle:
Thanks man, saved me a lot of trouble. I'm sticking with Voodoo.
[Captivate Android Development] DerTeufel1980:
Yes. Hellybean kernel is working. Got it confirmed in I9000 thread. Did not have enough time to compile a new one, or test it myself

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] acras:
Can confirm this for Cappy. If DerTeufel1980 doesn't mind I can attach it.
[Captivate Android Development] DerTeufel1980:
new kernel is at my website now. changelog also can be found there.

it is compatible with latest cm10 nightlies, hellybean, and all other roms, which are already using the "new/hellybean" partition layout of cm10.
[Captivate Android Development] Wakamatsu:
1.6.0 would reboot me back into recovery. Tried reflashing but the same thing happened.
[Captivate Android Development] tkjeeper:
Same here, I don't think that new kernel is for our setup. I'm on the new paranoid android, no data data. The new partition must be different
[Captivate Android Development] prbassplayer:
What rom? New kernel has the logical partition setup. Running awesome on my test build of Slim ;)
[Captivate Android Development] vileladelima:
What version of Devil Kernel is working on the new partition table of cm10?
[Captivate Android Development] swayjd:
Read up!
[Captivate Android Development] shuyin1102:
Confirmed that ver 1.6 not work with AOKP Build 3, flash back 1.5.2 and it running fine
[Captivate Android Development] tallsilver:
Same here. :cool:
[Captivate Android Development] Monfro:
Because AOKP 3 has not new CM partitions layout.

The situation of today is that only Helly Bean and CM10 have the new partitions layout.

Other roms will use it in next versions.

Sent from my Captivate
[Captivate Android Development] Ir0nLy0n:
ParanoidAndroid is still currently on the old partition layout. I hope to have it updated by the end of this weekend. For now 1.5.2 is the latest compatible kernel
[Captivate Android Development] tkjeeper:
Did my nandroid from 2.15 P.A. rom to that 2.5 V slim, just to try the newest devil from his site, 1.6.0, but still boots right back to recovery. You must have a SUPER new version of the rom prb?
[Captivate Android Development] prbassplayer:
I said it's my test build, haven't released it yet. Should be out the day or tomorrow, want to take a second look at cm source before releasing.
[Captivate Android Development] tkjeeper:
Well...if you really want I could test it with you...;P, hehe
[Captivate Android Development] dave71670:
Devil kernel with aokp cm10 partition is running great here. Great job Der. Cappy version of aokp with new partition in my sig.;)
[Captivate Android Development] shangxiaole:
what is meaning of AOKP cm10 partition? Did you modify it thru some configure file?:D
[Captivate Android Development] johnnyrichter:
Devil Kernel 1.6.1 VC + CM10 + Devil Kernel Config seems to be working fine so far.
[Captivate Android Development] vbenkovskyy:
Dear DEV thank you very much for your work. You've made great kernel!

I've noticed USB mounting bug. After connecting phone to PC and turning usb storage mode phone always unmounts usb storage (PC USB connection) by itself after some time... Fix this please.
[Captivate Android Development] dave71670:
1.6.1 working well with 4.1.2 aokp. Thank you sir.
[Captivate Android Development] DerTeufel1980:
1.7.4

new kernels are online now:

changelog is here:

http://xdaforums.com/showpost.php?p=32937649&postcount=7495
[Captivate Android Development] pqee:
Just to make sure, these kernels are for Hellybean, NOT CM10 layouts, right? I only found them under the Hellybean folder so unless you're still uploading version for us CM10 type users, this won't work for us.
[Captivate Android Development] Gromlakh:
I already flashed it on CM10, it works just fine.

I'm pretty sure Helly Bean and CM10 are on the same partition layout now. Someone please correct me if I'm wrong.
[Captivate Android Development] dave71670:
Yes. This is why they are called jelly helly kernels.
[Captivate Android Development] pqee:
Just realized my previous kernels were called the same, Jelly Helly. The 1.7.4 ones are in a different folder on the site which is what threw me off.

Flashed on Slimbean 2.7 and all is good.
[Captivate Android Development] DerTeufel1980:
My fault. Going to move them later.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] AceofSpades90:
lol I totally lost the *sound* when i updated from 1.6.1VC to 1.7.4VC. It's cool though. I'll try to get logcat.

EDIT: Once again, amazing job!! :D

EDIT EDIT: Probably its my rom causing problems lol i remember it did in past so yeah.

EDIT EDIT EDIT: I tried flashing with different combo's with tweaks, w/out tweaks, flashing 1.6.1 but the only way to fix it is flashing rom back...
[Captivate Android Development] pmd5700:
Same thing happened to me on LANIGHT 6.5DD.
[Captivate Android Development] dave71670:
1.7.4 just kernel flash is breaking sound on aokp as well. After full wipe and flash rom with kernel baked in all is good. Could this be the linux base change? Nice job on kernel. Thank you

Edit: Also noticed that when wiping dalvik cache from recovery it says E:unknown value for path [/sd-ext].
[Captivate Android Development] Gromlakh:
Same on CM10. I didn't notice it last night...but I did this morning when I slept through my alarm. ;)

Luckily for me I'm a robot and I woke up anyway.
[Captivate Android Development] bitnerd:
Do you get any sound at all? I'm able to play movies fine on mine with this latest kernel and CM10
[Captivate Android Development] dave71670:
1.7.5 is here. Sound working now on aokp. http://rootaxbox.no-ip.org/derteufel/jellybean/175/
[Captivate Android Development] Gromlakh:
I was getting like a half second of low volume, low quality sound, and then it just seemed like something froze/stalled/crashed/whatever. No further sound from any app, and a lot of apps that would require sound were taking forever to load.

I'll give 1.7.5 a whirl later. Sounds like this has already been fixed. ;)
[Captivate Android Development] blively2:
Delete
[Captivate Android Development] ap1618:
Hi,

can anyone confirm if this kernel 1.7.5 would work with Monfro's AOSP ROM for captivate?

It comes with devil 1.4 or something...

thanks!
[Captivate Android Development] kong00:
I have had ext sdcard issues with both semaphore 2.3+ and devil 1.7.5. My ext sdcard will not read and i have to downgrade to either sema 2.2 or devil 1.6.1 for it read correctly. anyone else having this issue? Weird thing is that when I pop in my alternative 2gb ext sdcard it reads fine, but my 16gb won't.
[Captivate Android Development] Tsaukpaetra:
Might want to fsck that card then, or pop it into a computer and check it there. I had issues like that, where it wouldn't mount because it had errors (fstab was apparently broken, it normally remounts as RO) and a quick fsck did the trick ;)

Slimbean 2.7, kernel 1.7.5 allows sound to work now.

For me, I noticed that the media provider would seg-fault through libc and others and loads of things would go awry because of it, now everything's back to normal ;)

See this and this
[Captivate Android Development] Gromlakh:
Agreed, 1.7.5 fixed the sound issues.
[Captivate Android Development] AtoZ0to9:
Is everyone using the older tweak app in the market for 1.7.5?
[Captivate Android Development] blively2:
You'll have to elaborate - What's the app name you're referring to?

There are only two that I'm aware of and they're not considered 'old' IMHO. :confused:
[Captivate Android Development] AtoZ0to9:
Sorry... those are the ones... the 2 available from the market....
[Captivate Android Development] blively2:
OK...then the answer is yes. :D
[Captivate Android Development] AtoZ0to9:
and u get a thanks press... and a post LMAO
[Captivate Android Development] Majestyk:
Semi-Bricked Captivate after Kernel install

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

Ran into some trouble installing this Kernel...

Still had rooted, stock 2.3.5 on my Captivate (i897) and wanted to try one of the CM10 roms so after following all the instructions, I could not get any of them to install with CWM. I tried every CM10 rom for i897 I could find and would always get an error/abort message. No files were copied and the old OS rebooted fine, minus all the data I wiped prior to installing the ROM.

I found a thread on another forum that said you had to install a CM10 compatible kernel before pushing out any CM10 roms so I downloaded this one and used CWM to push to my device.

Device booted to the Devil CWM app and I attempted to install the ROM. Rom gets about 10% then the screen goes black and nothing happens.

I am now unable to get an image back on the phone, getting the screen showing the android and phone with the yellow ! triangle in betweern. I can get into the Download screen and the device is seen in Odin but it just stops at <ID:0/014> DO NOT TURN OFF TARGET!! and never completes. Status bar does not move.

I can use Odin to re-flash the Devil3 Kernel and get back to the CWM screen if offers but so far I'm unable to get a rom on the device.

Can anyone tell me how to at least get back to stock from here? I'll go either direction if we can make this thing work again... either stock or a CM9/10 rom will work. I'm just stuck atm and not sure how to recover. Unit does still go to Download screen.

Suggestions anyone?

-maj
[Captivate Android Development] xtremists:
I am using slim bean with stock seamphre something kernel Guys

there are too many kernels for jb which one is Accurate I dont need oc i just need good battery life can someone tells me which to download
[Captivate Android Development] Ir0nLy0n:
Different kernels act differently on different devices. You should just try the kernels and see which is best for your phone. Also read up on governors and schedulers the right combination can really improve battery life.
[Captivate Android Development] xtremists:
i Installed Devel3_1.4.1Jelllybean_cappy_cfs_bln_vc After installing my Phone stuck in to recovery unable to mount system :/ and no way to revert then i installed semaphrne Something kernel Back And Got my Phone running what i did wrong :/ Am on slimbean
[Captivate Android Development] DerTeufel1980:
Please install the one mentioned in the thread title

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] xtremists:
Can You Please Tell me Which is the best Governer For battery ? (apart from power saver ) installed new version and its running and also name the market app for Kernel Modification
[Captivate Android Development] Ir0nLy0n:
Good info on governors here http://xdaforums.com/showthread.php?p=19846276
[Captivate Android Development] rpicaso:
RemICS 3 ?

Will this kernel work with RemICS 3? if so, which version do i download?

Thanks
[Captivate Android Development] DerTeufel1980:
please use this link, until the website is up again...working on it...

http://hellybean.site11.com/
[Captivate Android Development] DerTeufel1980:
i think so. you can take one or the other. difference is only color mode
[Captivate Android Development] OwenW71:
I've been told that the persistent bluetooth call quality issues with ICS and JB kernels for Captivate are the result of the BT stack in the kernels. Is this true, and if so, can it be fixed?
[Captivate Android Development] Tsaukpaetra:
If there is a problem with the bluetooth stack, then unless you recompile it with a fix, there's not much to do... Bluetooth seems fine form me, it's getting the phone to ring before it goes to voicemail that's usually my problem ;)
[Captivate Android Development] DerTeufel1980:
Sorry, I don't know about this problem and a fix.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] jonathan413:
Don't know if I'm seeing things but when I flashed devil kernel the first time I could only over clock to 1.4ghz..then I flashed newest semaphore kernel and over clocked to 1080ghz and it kept boot looping on me( overclocking on semaphore isn't possible on my phone but I can overclock wit devil kernel) so I then proceeded to flashing devil kernel again and now I can over clock to 1.5ghz...that frequency seemed to be unlocked somehow because the first time I flashed I was only getting max 1.4ghz...just an observation.
[Captivate Android Development] DerTeufel1980:
You can overclock to 1.4 GHz using the "old" method. With liveoc you can get even higher

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] jonathan413:
awesome thanks for the info...but fortunately liveOC is unstable no matter what value i set..im on the latest cm10 nightly and now my phone wont boot up :(
[Captivate Android Development] Kyuta Syuko:
Something I've noticed with this kernel that puzzles me is that my phone will reboot while on the kernel screen once before loading while on SlimBean. This typically happens after flashing the kernel or clearing the caches. Don't remember it happening with AOCP. Not really an issue since after the reboot it works fine. Just something I find strange.
[Captivate Android Development] Tsaukpaetra:
If you mean the brief flash that occurs after the devil splash shows, that's completely normal. It's just the screen reinitializing. Actually, ever since I changed my bootloaders to GB it has done this, kernel exclusive.
[Captivate Android Development] Gromlakh:
I don't think that's the issue, because I've noticed it on my phone as well. You get to the kernel splash screen, then it briefly goes black, and then the white AT&T logo hits again followed by the kernel splash screen. It's like there's a little mini-reboot that happens from time to time. I haven't said anything about it because it doesn't bootloop (it only happens once) and I've not noticed any negative effects.
[Captivate Android Development] Tsaukpaetra:
Yeah, that's kinda odd. Perhaps it's running a fsck? Or perhaps resetting a boot flag. You mentioned it happens after a flash, but not after that. Try a full powercycle (remove the battery) and see if it does the same when you turn it back on (obviously without having reflashed in between). :good:
[Captivate Android Development] Wakamatsu:
Happens with Semaphore also. I don't think it's something to worry about.
[Captivate Android Development] DerTeufel1980:
It's meant to be this way, to apply your bigmem settings right after power on. Without this, you would need to boot up first and then reboot

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Captivate Android Development] Kyuta Syuko:
Well that makes sense and is good to know. Love the kernel btw.
[Captivate Android Development] Tsaukpaetra:
BLN Custom blinking

Out of curiosity, I noticed a user asking how to get custom notification blinks working on the SlimBean thread (i897). I know you can use a kernel setting (I set it successfully using Devil Kernel Config), but there seems to be some options in the "Notification Light" section that indicate that the OS can somehow specify the pattern of blinking.

Now, I do know that we don't have a proper notification light on the Captivate, so this might be a mute point anyways, but at least the custom blinking thing might be accomplished I think.
[Captivate Android Development] nedthehead:
The one issue I get with this kernel consistently (since ICS) is after a while, when unlocking the phone, the screen will turn on, but the colours will be extremely distorted in a frozen position for a second or a second and a half, and then the lockscreen will load as usual. Anyone else experience this?
[Captivate Android Development] Tsaukpaetra:
That's normal. What you're seeing is the screen as it was when it turned off, and the backlight at "dim" level (the minimum allowable brightness).

I believe it happens because Android hasn't fully woken up yet (if you notice, there should be a little "brightening up" animation that plays"). You should also notice a similar effect when turning it off.
[Captivate Android Development] melvinaury:
Yesterday I download a new version 1.8.1, what's new in the new release...
[General Accessories] 2dy:
good day everyone.

I'm looking for a time now but can't find a remote control device that controls the music player of android smartphone, while the phone is conected to my car audio line in.

Does someone know if there exist such a device? (except the watches)
[General Accessories] cherrypick:
I have never heart about such knid of device.
[General Accessories] jRi0T68:
How do you connect your phone to your stereo? Usb, Bluetooth, or aux cable?

If aux cable, there are some inline extension cables with buttons, which can be programmed to skip tracks, etc.
[Nexus S Q&A, Help & Troubleshooting] torchie:
It seems to take around nine seconds total for the screen to turn white, the search box to come up, and the keyboard to pop in. I seem to have plenty of memory. What most affects the speed of the search box?
[Nexus S Q&A, Help & Troubleshooting] jayjay3333:
Mmmm..fresh bread. This thread makes me hungry. :p
[Nexus S Q&A, Help & Troubleshooting] d_phekt:
Lol I'll take a loaf of wheat please.

Mine loads just fine. Just a second or two. I see you are on a 4G so maybe its because your ROM is missing the binaries that were recently just released.
[Nexus S Q&A, Help & Troubleshooting] albundy2010:
Running the stock rom on a 9020t and I noticed straight away that loading up voice search does lag. Not as long as the op stated but there is a lag.
[Nexus S Q&A, Help & Troubleshooting] phositadc:
Ditto. Not 9 seconds but definitely noticeable lag.
[Motorola Photon 4G] jstnp_ke:
I was all prepared to root and unlock my bootloader with pudding and CWmod and then I read that no one is having success with the bootloader unlock on the new update 45.4.13.MB855.Sprint.en.US aka 2.3.5. I also saw somewhere (be it wrong or right) that the new update let you use USA sim's in the phone. IDK what to belive. I need this phone to work on tmobile today If anyone has any insight on how to do this please let me know!
[Motorola Photon 4G] rbeavers:
Have not heard that about US sims working.
[Motorola Photon 4G] maxon_yalta:
First is imposibble, as you mentioned, second is bull****.