yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Liv33viL:
Decisions... Decisions...

I'm deciding whether or not to flash up / over to ExistZ's Beta series Kernel #5.

I've been on OverStock v1.1 for the past few days. I figure making a major mod such as a kernel replacement would need a few charging cycles for the internals to adjust to the change to see consistent results.

I've had no issues with OverStock v1.1, very stable, very good battery life over 3 charging cycles and no glitches. Which is awesome...

There really doesn't appear to be too much in the way of new developments or upgrades or mods to this kernel (OS1.1) unless is has already been completed, as compared to what eXistZ has been doing with the Beta Series kernel <--- for lack of a proper name. I like how he tirelessly making improvements and is quick on the response if there is a question to be answered. This is one of my deciding factors in coming on board...

Just curious eXistZ ... any idea when this bad boy will be out of beta stage?

Also... anyone care to post benchmarks, day to day performance, battery life (thus far), UV/OC tips for the Beta #5 Kernel...

Just want to have a clear comparison on paper before going live...and yes I do realize results will vary from case to case.

Thanx,

Peace-
[Captivate Android Development] ffbadkill:
I cannot connect to wifi after I flash this kernel

Also, the usb connect notify will not disappear after i unplug the usb

I am using kb1 modem.....

Anyone else has this problem?
[Captivate Android Development] existz:
Try reflashing, making sure to flash only with CWM.. then clear cache/dalvik cache, as well as reboot your router...worked for me a few builds back.. Im not sure what it is with Wifi and KB1, but seems its happening with both my kernel and OverStock kernel, so theres something going on..it doesnt happen every flash, nor does it happen to everyone.. but clearing out the cache and rebooting the router seems to help..plus a fresh flash doesnt hurt either
[Captivate Android Development] oxlong27:
Please exscuse my stupidity but can i use a different cappy modem or just kb1 i get the best signal ever with j16 and there is no 3g in my area so 3g downliad speeds dont matter for me i use wifi only. Thanks for the info
[Captivate Android Development] rajendra82:
The USB connect icon not disappearing is a KB1 bug. I've had it since stock KB1 was leaked. Turn off USB debugging unless you really need it. This only happens when debugging is on and you disconnect after hooking it up under that mode. This kernel has nothing to do with it. I have never had huge WiFi issues under KB1 with any kernel. There are times when the phone won't auto connect to the remembered SSID in range, but toggling the WiFi icon off and on in the status bar fixes it for me. I connect to Open, WPA2, and WEP networks every day, depending on where I am.
[Captivate Android Development] ffbadkill:
Thanks a lot!

Another question

I was using SuckerPunch #56 and I could wipe dalvik cache in CWM

However, now it shows

E:Can't mount /dev/block/mmcblk1p2
(File exists)

with either SuckerPunch-Voodoo or eXistZ Captivate Kernel.

Any other way to wipe the cache?
[Captivate Android Development] Liv33viL:
Another Way To Wipe Dalvik Cache

Yes,

If you have Titanium Backup Pro

Backup/Retore Tab--->Settings Button (lower Left Touch Sense Button)-->More (on the menu)--->Second Option in the flyout Menu "Cleanup the Dalvik cache"

Not positive if it's "exactly" the same as a CWM Dalvik Wipe or a manual deletion (which I usually do), but none the less it's a Dalvik wipe and it works.

HtH

PS: No takers on my prior post...?

Peace-
[Captivate Android Development] Liv33viL:
Re: Can't Mount...

RE:

E:Can't mount /dev/block/mmcblk1p2
(File exists)

Yes, I've noticed this as well with CWM 2.5.1.2 and 2.5.1.3 on a Dalvik wipe - but the cache folder is actually located @ /data/dalvik-cache

Just an FYI

Peace-
[Captivate Android Development] rajendra82:
The TiBu menu is to clean up dalvik cache errors. It does not wipe the entire dalvik cache out. I just tried it, and it only took a second, and said "no unneeded files found in the dalvik cache".

I got the error too, but the line right after that error code in the red built in CWM recovery said "cache wiped", and the next boot took quite a bit longer. So I am sure the dalvik cache was wiped despite that error message. I had some force close vibrations after boot going on in the background without any messages about them before I tried to wipe. The wiping of the dalvik cache through CWM fixed that issue, so I am pretty sure you can just ignore that line. If you feel like it not seeing the irrelevant error code, try launching the real ClockworkMod recovery (green text), by applying update.zip from sd card put there by ROM manager, or by telling ROM Manager to boot into ClockworkMod Recovery. After that, you can try wiping the dalvik cache by going into the advanced menu of the green version.
[Captivate Android Development] ffbadkill:
Thanks rajendra82 and Liv33viL

But after I wipe cache and dalvik cache, I still cannot to my router:(

I think I should stick to SP#7 at the moment:(
[Captivate Android Development] ewingr:
FYI...I am having wifi issues too. If I leave my house and it disconnects, when I return, Wifi will not come on. If I open the Settings and WiFi, it says Error to the left of the WiFi toggle.

I am missing the performance that we get when using an 19000 ROM, and am considering ditching KB1, especially given the WiFi issues.

I"m not sure if there are any other viable modems for the Captivate 2.2 ROM, but I am pretty sure the higher speeds won't be there if there are any. I can possibly live with that, but not with having to reboot to get WiFi working.

Regarding this kernel, I am still on Beta4, and I think it is working fine.
[Captivate Android Development] existz:
Have you guys with wifi issues tried rebooting your router? Worked for me...

Also, update coming today with Voodoo Sound v5
[Captivate Android Development] rajendra82:
Your only other viable choice of modems would be the i897 JI6 or JJ4 modems contained in the leaks from last year. Both should work with the KB1 kernel, and may function better with your router, if the latest Samsung code added some WiFi bug in the modem.bin that did not exist back then. You can find the CWM flashable versions of these modems in the stickied modem thread. If the bug is kernel side, there may be a fix found, once someone looks through the new source code carefully.

Edit: Do you by any chance have Y5 battery saver app? I had that at one time, and it seems to clash with the code in KB1 turning the WiFi on and off, giving me that "Error" next to WiFi toggle checkbox. Uninstall it if you have it, and then use the status bar icon to manually toggle WiFI on and off on demand.
[Captivate Android Development] existz:
*UPDATE*

BETA #6

-update Voodoo Sound v5

NOTE

Make sure to update to the latest version of Voodoo Control App
[Captivate Android Development] rajendra82:
The new update-script still has the line to delete the voltage control settings file. I am going to take that out before I flash, since I am already on beta 5. You might want to let users know about this still being done.
[Captivate Android Development] lactardjosh:
Downloaded and flashed.

Current Voodoo Control App in the market is v0.10, which was just updated today.
[Captivate Android Development] ewingr:
I may try one of those other modems.

I haven't rebooted for a while. I may give that a try. My router is an N router, and I find that no matter what modem i use, I do have short disconnects happening all the time.

I don't yave Y5 battery saver. I do have Quick Settings. Not sure if that would affect it or not. I do no I have not had this problem on any of the other many modems I have tried (on other RomS). Up to now, I have not tried a different modem on this KB1 ROM.
[Captivate Android Development] existz:
Ill fix it..thanks.. I forgot about it..kinda slipped my mind after updating these 3 kernels..lol
[Captivate Android Development] existz:
Definitely try rebooting your router..it fixed it for me when I couldn't connect to wifi
[Captivate Android Development] rajendra82:
Flashed my own modified version and on beta 6 already with Voltage Control settings intact. Holy crap this phone boots fast now.
[Captivate Android Development] rajendra82:
You will need to redo voltage control settings again. The version you downloaded deleted the settings file.
[Captivate Android Development] existz:
fixed update-script..uploading now

....uploaded ...
[Captivate Android Development] lactardjosh:
No worries, I hadn't had a chance to redo my settings for #5 since you're getting these up so fast. ;)
[Captivate Android Development] imb951:
This is working beautifully for me on Beta 6, thanks. Keep us updated.

Do we have to flash FuguTweaks again every time we flash an updated eXistZ kernel? I'm not sure how to tell that it's working...
[Captivate Android Development] rajendra82:
I hope you did your own testing.
[Captivate Android Development] existz:
Nope..its apart of the rom, not the kernel
[Captivate Android Development] imb951:
Yep, tested the original and newly posted voltage settings overnight. Original settings I had clock freeze and alarm reminder malfunctions the next morning. These new settings caused no issues at all charging overnight.

Thanks!
[Captivate Android Development] rajendra82:
Glad that it's working out for you. The testing at 200 MHz was an extremely painful process for me, because it goes so slow. I didn't even bother to do it at 100 MHz for 10 hours straight. Form this point forward my approach is going to be:

1. If I see sleep death or charging death, up the voltage at one or both of the low end 200 and 100 MHz frequencies.

2. If I see random reboots while doing moderate work like web browsing, adjust the undervolting in one or more of the 400, 600, and 800 MHz frequencies to make sure there are no frequencies getting too little or too much voltage, and there are no huge jumps between adjacent voltages.

3. If I see freezes under heavy load, take a look at the 1000 to 1400 MHz range, and rethink voltages, enabled stages, and maximum speed. This is probably the least problematic area, because stability testing so far has been fast and easy to do here.

I don't see the need to so any huge changes on my phone from the table above. At most it'll be a 25 mV swing either way, and maybe cap down to 1300 MHz instead of going all the way to 1400 MHz.
[Captivate Android Development] ffbadkill:
I tried but no luck.

It doesn't work:(
[Captivate Android Development] Liv33viL:
WiFi Issues

ffbadkill,

Can you post exactly what issues you are experiencing and what you are seeing or not seeing.

There are many ways to incur a failed WiFi connection.

I'm confident you'll be up on WiFi in no time at all...

List Modem and Kernel combination as well.

Please be as specific as possible.

Peace-
[Captivate Android Development] ewingr:
:eek:

Just tried that. I don't get 'error', but when it scans, it saw nothing at all and turned off WiFi.

Now, I turned it on again, and then it found the network. And it is playing music. Mixzing is not running. I went into processes and looke, and see no music apps running:eek:

I have Gremlins!!!

Oh, also I added that file you referenced earlier to turn off BLN (I think I remember that was from here...), but BLN still on. Can't get BLN app to turn it off; Don't have access to BLN settings from recovery.

MORE Gremlins!!!
[Captivate Android Development] boog:
So far, this kernel seems to be running great on Cognition! Eventually I hope to learn how to build my own.

Loving the Voltage app, much better than setcpu.

And I just can't manage to get 3-5 charge cycles with these daily updates! :D

Awesome work!
[Captivate Android Development] rajendra82:
Put it in the microwave right now.
[Captivate Android Development] ffbadkill:
I am using darky 9.3 and kb1 modem

When I turn on the wifi, it always show "connecting.." and disconnected soon.

After it tried several times, it set disabled at the remembered access point.

I also tested with kp1 modem and the result is the same.
[Captivate Android Development] DunDunDario:
Does this kernel have really low brightness like speedmod? Also can you use your headphones to listen to the people that your calling?
[Captivate Android Development] antonyvijai:
I see eXistz has voodoo color. Is there an app to make some color settings? Or is it just an enhancement
[Captivate Android Development] rajendra82:
Low brightness is a yes. Haven't tried the headphones while calling, but if you are talking about the HPCall supprt (Calls routed via headphones when available), it's not listed in the OP as a feature. Could be a part of more to come...
[Captivate Android Development] existz:
As of right now it seems to happen with both this kernel and overstock kernel, it doesn't happen with everyone..so kinda hard to pin down..but try toggling wifi on/off a couple times, letting it scan for a few in between..also try rebooting your router.. worked for me awhile back

Yes it has the darker min brightness..as of right now it does not include hpcall (using phone mic while headphones connected) but ill add it soon ..
[Captivate Android Development] rajendra82:
Someone said to go into video player while playing a movie, and change the color preset to warm or cool. Not sure if that is just an app specific change or system wide. The voodoo color setting sliders in the app is a Nexus S/Gingerbread thing.
[Captivate Android Development] antonyvijai:
Thanks! The kernel lists color and sharpness enhanvement as an additional feature of this kernel. Hence the curiosity! I am thinking of using blinky add on to use with BLN app. Do you know of any 3rd party app which I can use to make use of all kernel features (like, color, sharpness etc)
[Captivate Android Development] rajendra82:
Voodoo Control for sound, Blinky or BLN control for BLN, there isn't anything for sharpness/color, brightness is supposed to be pretty good with Curvefish (no personal experience). I don't use CIFS/TUN, so no input there. Just play with different apps, and post here to help others if you find a gem.
[Captivate Android Development] antonyvijai:
I think for color we have galaxy tuner! I think it is a good app with all controls for voodoo enhancement and much more. But, I decided not to install anymore 3rd party app. Thanl you for all the help!
[Captivate Android Development] ewingr:
I'm tellin' ya.

That crazy thing is playing music right now. Happens when I connect to WiFi. Turn WiFi off, it may stop, it may not. I have killed all processes, and it doesn't stop. Doesn't show any music apps running. :confused:

I guess I'll put a new ROM on. May try Cognition. Although I think I've had my ongoing problem with it in the past too. (I find that after 2-3 weeks on a 'custom ROM', my auto rotation / sensor will stop. A reflash is the only thing that fixes it. So that is why I trying the 'stock' KB1, to see if that happens on it.).

I first need to find correct way to go back to stock from KB1. I read somewhere that you should not use 1Click back to stock from KB1. I have a post in general questions on that topic.
[Captivate Android Development] rajendra82:
You don't need to use the dangerous one click to flash stock JF6 first. You can use Odin 3 v 1.7 and the KB1 tar file. When it reboots the second time, hold the three button combo and in the 3e recovery, delete user data, clear cache, and wipe dalvik cache. The last step is needed because the KB1 tar file does not include params.lfs and dbdata.rfs.
[Captivate Android Development] ewingr:
Thanks. Flashing the stock KB1 tar file will take me back to stock 2.2. From that then I presume its OK to flash Cognition, as it is based on KB1. Not sure if that would be the case if I were to want to flash to an i9000 based ROM.

I need to go search for the KB1 TAR file. I installed KB1 by using Samsung's PC app (I forget what its called...old brain having troubles with memory.) Also need to search v1.7 Odin. I have 1.0. Been a while since I've used Odin (other than 1click to JF6).
[Captivate Android Development] rajendra82:
Odin 3 v 1.0 will be fine, it's not the latest, but works for this. The KB1 tar file and associated instructions are in the general or development forum here. Can't remember which one. When you do this you will have 3e recovery, which requires signature verification. You'll need to patch it to allow you to flash a custom ROM.
[Captivate Android Development] ewingr:
Thanks, rajendra. I did in fact have to patch what I have now. Don't remember for sure how. but I know I'll find it easily.

I did just read that someone had use the AIO program and accomplish all this too. I may give that a try.

I'm going to get Cognition on here, and will likely be back to this kernel pretty quick.
[Captivate Android Development] Rrryan2:
Backing up battery stats?

Potentially stupid question: we all know that flashing a new kernel can temporarily throw the battery calibration into a tailspin. But is there a way that a kernel install script might simply back up batterystats.bin to /sdcard/ or such before installing and then re-write after the new kernel is active? Or is there more stuff going on under the hood that would make this unhelpful or impractical?
[Captivate Android Development] lactardjosh:
For the easiest brightness control, I set the minimum brightness in settings, then just use the notification by sliding my finger left to right to make the screen brighter or right to left to make it dimmer. No widget necessary. :)
[Captivate Android Development] rajendra82:
The kernel flashing process does not overwrite or replace the battery stats file. You can do these as manual steps. I never do. I am sure the backup and deleting of the stats file could be added to the initial flashing script, but you would still have restore it yourself later.

I have never bought into the theory that kernel flashing makes a huge difference to the battery stats, especially if the kernels are built from the same main source.
[Captivate Android Development] existz:
Flashing kernels/roms can mess up the battery calibration, there's been times I would flash 4-5 test versions in a row and it would not effect it, then there's been times I flashed just 1 kernel and it would drain bad..a full battery in about 6hrs..even being the same exact kernel I was using before I flashed the test versions that I was getting 30+ hrs with ...a few charge cycles fixes it ..so it can happen, its random..but its always a good idea to give it 4-5 charge cycles to recalibrate
[Captivate Android Development] rajendra82:
Then backing up the old stats file and restoring it later would just set you back further in time again, right?

What about deleting the file on each kernel flash like Rrryan2 was thinking about? Would that help rebuild the stats file faster, or is it going to be about 5 charge cycles no matter what?
[Captivate Android Development] existz:
It will still be 4-5 cycles either way, if the calibration gets screwed on a flash it will take a few, if you delete it..it will still take a few for it to calibrate.. The best thing to do is just run it to 0% then fully charge it a few times after a flash..usually it starts to get back to normal.
[Captivate Android Development] boog:
I say you name it PuckerSunch!
[Captivate Android Development] shane87:
I like ColdClocked, personaly, although Snookie Punch is good too! Keep up the good work, existz!!

ROM: Cognition v4.1.1

Kernel: eXistZ's KB1 #5 Voodoo Sound v4, Voodoo Color, Voodoo lagfix

Modem: I897 UCJJ4 w/ HSUPA/HSDPA enabled
[Captivate Android Development] rajendra82:
My vote is for *****Slap
[Captivate Android Development] shane87:
I think existz should put up a poll to choose the name. That would make it a lot easier to count votes, lol.

ROM: Cognition v4.1.1

Kernel: eXistZ's KB1 #5 Voodoo Sound v4, Voodoo Color, Voodoo lagfix

Modem: I897 UCJJ4 w/ HSUPA/HSDPA enabled
[Captivate Android Development] jcr81:
Tried both this kernel and overstock but couldn't get wifi to work. Just kept alternating between disconnected and scanning so back to sp voodoo. Wanted the ability to overclock and use the kb1 modem. I was on Dragon KP5 Rom btw. Oh and I vote that the name be "Mach" as in the term used to designate a speed. So this one would be Mach 6.
[Captivate Android Development] momulah:
Is there any way possible we can get a 500hz version that's fugu capable. This kernel plus jl2 modem produced the fastest speeds I have ever had with any combination of rom's,kernels, and modems..Ill update with a screen shot to prove it. New Orleans La area. Thanks kernel is great and I appreciate the work on it. Looking good. KB1 base is solid. I got up to 4800 download inside my xray rig..
[Captivate Android Development] Liv33viL:
Broken Modem...

Try this...

http://xdaforums.com/showpost.php?p=12217618&postcount=149

Peace-
[Captivate Android Development] xThe Enforcer:
Going to test this out soon with FF 2.6 and JL2.
[Captivate Android Development] existz:
You will need to use KB1 modem...i9000 modems wont work since its captivate source..
[Captivate Android Development] lactardjosh:
Are voice calls working with JL2?
[Captivate Android Development] momulah:
Jl2 modem does indeed work look a few post above at my download speeds...it works great!

Works for me didn't notice a difference in call quality....
[Captivate Android Development] TheGrub:
Hi guys,

I have a i896 Rogers captivate and first tried SpeedMod's kernel and since it's a i9000 based kernel, had to flash i9000 modems and still had noisy bluetooth...

I am now using supercurio's stock+Voodoo-Froyo-I896-UXJL1 and this gives me lagfix and it's running great.

Since eXistZ Captivate Kernel is based on a Captivate kernel and not a i9000, can i flash over stock+voodoo i am using now ? and can i keep JL1 modem or will i have to flash KB1 ? And KB1 is a captivate modem right ? not a i9000 modem ?

Thanks for all your responses....
[Captivate Android Development] rajendra82:
Are you absolutely certain you have paired the UGJL2 modem with the eXistZ KB1 kernel? Every Captivate kernel and a non Captivate modem pair (including UGJL2) has resulted in a total loss of audio on voice calls for me. Downloads and uploads work great, but I can't ever use the phone as a phone. The only modems that should work with this kernel are the Captivate Froyo modems JI6, JJ4, and KB1.
[Captivate Android Development] rajendra82:
Although the i896 and i897 Captivates look identical on the outside, the i896 does not have the audience chip, so pairing a JL1 with this KB1 kernel will likely result in a loss of audio in voice calls. I have not personally tried that combination, but in that aspect, the i896 probably behaves more like the other i9000 variants and Armani Captivate. The only Galaxy S variants with this chip are the i897 and the Nexus S.

I am not sure if Rogers allows HSUPA for you, but when you use KB1 modem, you won't be able to have HSUPA. If you are on WiFi most of the time like me, you might not care.
[Captivate Android Development] TheGrub:
Thank,

I don't really care for HSUPA.... Wifi 90% of the time...

And KB1 should work fine on my i896 without audio loss ?
[Captivate Android Development] max_82:
Right now I'm using speedmod kernel k13c and jq1 modem. I enable several tweaks from k13c. If I want to flash this kernel should I disable tweaks first or I can directly flash it? Thank you for the response.