yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] glitterballs:
There were some mounting issues with both cards early on. That has been solved. Did you try installing the superuser zip in CWM from the post linked in the OP? That's why it's there.

Re: Going to the other ROMs - The second method (One click) definitely works. I think flashing a Voodoo 5 kernel & rebooting to recovery might get you to the point where you can disable lagfix and reflash any ROM/kernel (or not disable lagfix and flash a just flash a ROM). I've not tested this, so...it might just be easier to one click back to stock, reboot to recovery and flash CWM from the update.zip you should probably keep on your SD card at all times.
[Captivate Android Development] theMaginator:
Thank you. The problem was that I did not install the superuser.apk before hand and then after it was too late because of the mounting issues. I'm going to try it again.

But so I understand your kernel fixes the mounting issues right?
[Captivate Android Development] glitterballs:
OP updated. Just a few changes as in the initramfs, wifi sleep. BLN are working again (!), but you have to use the app to toggle them off an on after every reboot, you also need to push the liblights.s5pc110.so to /system/lib/hw. You can find these on neldar's git. I also patched in xcaliburinhand's wired headset support. If anyone else wants to be nice an make a nice flashable zip with the liblights and kernel I'll put it in the op but I've had enough for one day.
[Captivate Android Development] chrisryn:
Ok here is whats required for rooted applications

1. Plug your phone to your computer and open adb shell

2. If your prompt looks like this # goto 13

3. Close adb shell

4. Download root.zip below

5. Type adb push rageagainstthecage-arm5.bin /data/local/tmp/

6. adb shell

7. type "/data/local/tmp/rageagainstthecage-arm5.bin" (without quotes) in adb shell

9. Wait till shell reboots.

10.Start adb shell you should now see the # prompt

11. Type ""mount -o rw,remount /dev/block/stl9 /system" with out the quotes(rw of file system)

12. Exit adb shell

13. Push su,busybox to /system/bin

14. adb shell

15. Type "cd /system/bin"

16. Chmod 4755 su

17. chmod 4755 busybox

18. reboot and enjoy

I have to switch computers to add files I will edit this once I get them( about 5 minutes)

Edit: Added files. I believe that covers it all let me know if it doesn't work. I was dozing off as I wrote this(13 hour workday).
[Captivate Android Development] GusBourg:
So... How did you get your GPS working? I've tail'd /data/gpspipe. There's content but I don't see any sats.
[Captivate Android Development] jwlsinx:
Thanks gb.
[Captivate Android Development] :
I cleared catche/dalvik and installed the nonOC/UV kernel right after the panic. Anyway, I didn't even think about pulling the log and it's gone now to my knowledge. I tried to adb pull and it founds nothing. I can try to adb bugreport but I don't know what information to send you from that or if the file is deleted by the catche/dalvik wipe.

I was at 73% battery because I had just looked at it before I locked the screen. I locked it, set it down (unplugged with nothing running) picked it up couple min later and the screen was black and in the top left corner it said kernel panic. Then I performed the steps above. The installation was maybe 30min old. The market had just finished autoinstalling all my apps.
[Captivate Android Development] jwlsinx:
So it's the first time I've built an update.zip, but I flashed the CM6.1-GalaxyS-BETA3.zip, then the kernel and everything looks good, runs good. See attached. Had to reinstall the 2.3 keyboard, but that's it.

Update has the kernel and the s5pc110.so file. Most people called it lights.s5pc110.so, so I used that file, and just did a symlink from liblights -> lights.
[Captivate Android Development] glitterballs:
Dammit, dammit, dammit.
[Captivate Android Development] tjsooley:
Is there any update on sound recording?
[Captivate Android Development] jwlsinx:
No sleep death with the non oc-uv kernel. Left in charger all night.
[Captivate Android Development] keredini:
Had sleep death when I woke up this morning, phone charged all last night. I'm using the OC/UV kernel.
[Captivate Android Development] mkoby:
Is this the OC/UV or the non-OC/UV?
[Captivate Android Development] jwlsinx:
Non-OC/UV. Also, BLN seems to work by default with it (no need to re-enable it after a reboot, etc).

Edit: I've attached the OC/UV kernel update.zip for those who want it.

Um...
[Captivate Android Development] Smallsmx3:
so does this mean no sleep death anymore?
[Captivate Android Development] glitterballs:
No, definitely not. :confused: The no oc/uv kernels never had a problem afaik.

I left my phone plugged in overnight via USB...no problem. Got to work, left it in the wall charger for about three hours after fully charged and it happened again. I haven't been able to get a good log of it happening...when it does crash, there isn't a /proc/last_kmsg. I can change a few things I think will fix it, but since this happens so intermittently, it takes at least several hours after flashing a new kernel to see if it's fixed. I know it's a bug, and I would love to fix it, but in the mean time, either charge your phone via USB and pull it when it's completely charged, or use one of the kernels w/o oc/uv. I had some code up earlier which I will put back up when I get home, hopefully someone will be able to spot a problem.
[Captivate Android Development] jwlsinx:
What happens if you have the OC kernel, but turn off the UV, especially if you turned off UV for the lower frequencies.
[Captivate Android Development] glitterballs:
Same thing. I actually just caught it happening, and the reason there's no /proc/last_kmsg or logcat errors is because it seems the battery is just, for lack of a better word, shorting out, almost as if you pulled the battery. There's no shutdown.
[Captivate Android Development] cnewsgrp:
You guys seems to be making very good progress. What is the best time for educated newbies like me to jump in and take a look at the ROM.
[Captivate Android Development] cckidquick:
I have gotten sleep death a few times...but the weird thing is I didn't get it till I stopped uv..

I'll test again tonight with a uv
[Captivate Android Development] NiXXeD:
As long as you agree not to ask questions that have already been answered, you can probably play with the ROM now. Just read the issues log first, and read the installation instructions like 3 times over. And learn how to Odin if you haven't already.
[Captivate Android Development] Athailias:
I just woke up and havent had much/enough sleep so this may not be super coherent but...

When I flash the I9000 beta three (or nightly) from jpm per the instructions I usually wind up having to flash it two times in a row before it will boot. Well one night at work I got anxious because GB hadnt put out the reorient for the latest nightly and I had flashed to stock purely to get a flash addict fix and for some crazy reason thought id try axura. Oh I know why I flashed JPU came out and I was going to mess with it, anyway I wound up flashing cm 6.1 nightly over top of axura and it booted first try. Does anyone have any thoughts at to why this might be? Basically my process (accidental process caused by not liking axura rc2.1 and being at work and unable to flash to stock) was Flash to stock and master cleared, Flashed Axura, flashed 6.1 nightly from dec 7th. and it booted! I then flashed the reorient kernel. Anyone have any thoughts of why it went so smooth? I didnt make a backup or use the "init" kernel. I will try to do it again later tonight or tomorrow if I get some sleep at some point as I still havent tried to get JPU on the phone.

For clarification, I am not asking for help as this actually seemed to work better for me, just wondering if anyone had any thoughts as to why this may have worked better for me than the actual instructions for flashing.

Update: I just repeated the results. Flashed stock (granted I didnt do a master clear), flashed axura ce 2.1 and then flashed the nightly beta 3 and the latest kernel and booted right into CM
[Captivate Android Development] glitterballs:
/system = ext4 with CM6.1, /system = ext4 with Xcaliburinhand's Reorient/Voodoo
[Captivate Android Development] fatttire:
If I could guess maybe you skipped a step in the install, we all do it ;), and axura filled in that step for you.
[Captivate Android Development] glitterballs:
lol.

Hey, just for the hell of it I flashed the Captivate JJ6 modem over JK3. Seems to work so far with no reboots. Anyone else want to have a go at it?
[Captivate Android Development] Athailias:
Thats my point. I know I skipped several steps. I was just surprised that I didnt have to do so much stuff to get from stock to CM 6.1 and in the future I will do it that way as it was pretty painless.
[Captivate Android Development] glitterballs:
I think you missed my point. The /system filesystem formats are the same, ext4 with Xcal's Voodoo 5 based kernel used in axura, ext4 with CM6.1. I've said a few times in this thread people should be able to go back and forth with a Voodoo 5 based kernel.
[Captivate Android Development] chrisryn:
whats the patch.zip in OP for and do I just flash it from recovery?
[Captivate Android Development] Athailias:
Right, I guess what I am getting at is someone should change the instructions to start with axura and save some headaches.
[Captivate Android Development] Smallsmx3:
This rom is not hard to flash....
[Captivate Android Development] Athailias:
I have never had a "problem" installing this rom. I just know that I have seen several posts where people say "re-read the aery's directions" or "you didnt do something right" and I just thought going stock, then axura, then cm6.1 was the easiest for me so far. I was just sharing my experience with it. I wasnt complaining or saying its too hard any other way *shrugs* sorry if I have come off that way.
[Captivate Android Development] fatttire:
One thing to watch out for is the emergence of a new bug. A new install route is a developers nightmare :D since if there is a bug you don't know if its bc of the funky install or legit.

One of the reasons there's a "tradition" of flashing to stock isn't for user experience but make debugging possible.

Glad it works for you! Its kinda fun to try new combinations
[Captivate Android Development] jwlsinx:
For everyone who has been missing swype with this rom, the new version of swype as packaged with the Assonance v4.3 rom works. I've attached a zip that you can use in recovery to install it.

Change settings under Menu -> Settings -> Language & keyboard -> Swype

Set as default kb by long pressing in a text box, selecting Input Method, then Swype.
[Captivate Android Development] Smallsmx3:
So hows the jj4 modem working out? Ive been using the new jk4 and its working well does jj4 drain the battery life?
[Captivate Android Development] Sebring5:
What does the codeworks patch do?

I tried flashing it in recovery as a zip file and it would not install. Is it an Odin file that needs to be unzipped?

Do you flash it after installing CM beta and before the reorient zip or at some other point? My phone works without it and I do not understand why you would flash this.
[Captivate Android Development] cappyron:
So.... I decided to embrace the use of the external sd card and bought a good one... this rom is great :)... So now I think I'll try to contribute and fix bluetooth :)

Sent from Cyanogen... or something similar
[Captivate Android Development] Haloruler64:
Guys, I'm really sorry for asking a stupid question, but internal SD doesn't work? It says fixed in changelog. Thanks for the help...
[Captivate Android Development] jwlsinx:
It's mounted at /mnt/emmc, is that what you meant?
[Captivate Android Development] Haloruler64:
Yes, thanks SO MUCH! I really apologize for the n00b move of not reading, I'm really stressed and sick right now. I really appreciate it! :)

EDIT: How do you mount to a PC? I don't see an option

EDIT2: There are no icons in my notif drawer when i plug my phone in, nothing for USB. Works on my friends Vibrant. Anyone know why that is?
[Captivate Android Development] Haloruler64:
after 2 reboots, it appeared. Didn't mount, so unplugged and replugged, now it wont show up again. What's wrong?
[Captivate Android Development] Haloruler64:
Excuse my triple post, but I gave up on CM6.1, so no help needed anymore :)
[Captivate Android Development] glitterballs:
It's really subjective I think. Gdanko knows a little bit (a lot probably) more than I do about the hardware differences between the Captivates and the i9000s, and he's pretty convinced that a Captivate modem is the way to go. I flashed partly for the hell of it, partly because I thought everyone had dismissed Captivate modems working with i9000 kernels, but, I got to thinking that it works pretty well for the Vibrant people. And, it turns out, works for us as well. edit - No soft reboots or any of the other problems I had with the JI6 modem & a i9000 kernel. Battery life honestly does seem a little bit better, but, like I said, it's subjective. After having HSUPA, I think I can live without it if my battery life is a bit better.

Ehmm....it's a kernel patch. It patches the code from codeworkx's kernel source to compile and run on the Captivate (with the right initramfs). You probably shouldn't just go around flashing things you find posted without know what they are. Just saying...

Keep us updated. You know where to find the sources right?
[Captivate Android Development] Sebring5:
You are right. My bad. Thanks for explaining what it is. I understand now.
[Captivate Android Development] glitterballs:
I'm not trying to chastise you, just saying, for your own protection/good, make sure you know what you're flashing is all. :)

And for anyone who wants to have a go at compiling, now they can. That patch has the headset support, BLN, proper screen rotation, etc. Also, anyone who wants to try to track down the sleep death/charging thing, raspdeep's sources/patches are here.
[Captivate Android Development] bongostl:
So I'm having the same problem with Titanium Backup (says that 'unknown apps' is unchecked, even though it is checked)...any help would be appreciated.

When I do this, I get the '#', so I skip to 13.

I do the instructions, but still, titanium gives me the same mes.

if I don't skip to 13, i get an insufficient permissions error after #7.

Any help would be super appreciated..Titanium is useless right now...

Thanks!
[Captivate Android Development] Smallsmx3:
So I used modem jj4 yesterday and I got about 13 hours of battery...which is what I was getting when I used jk3 but 8 hrs of that was while I was sleeping. Cell standby and phone idle consumed over 50% of the battery which I still don't get with this phone. Should I have wiped battery stats even when I flash a modem?
[Captivate Android Development] glitterballs:
Try unchecking it.

Ehh...yeah I don't know if JJ4 is a keeper. Like I said, gdanko seems to think a Captivate modem is the way to go, I just wanted to try it out. The voice chip support might be in the modem, I'm not honestly sure, but I think the voice chip support part of why he wants a Captivate modem. The ROM definitely seems to have battery issues no matter what you do, which, honestly is kind of why I still put out the oc-uv kernel. I know the charge death issue exists, it exists for all i9000 kernels using PMIC as far as I know, but it really allows you to really aggressively undervolt and significantly increase battery life.

edit - Some time this weekend, maybe tonight, I'm going to roll out a different version of the OC/UV kernel which use a different strategy to reduce power to the CPU. You won't be able to undervolt as aggresively, but it should (hopefully), be stable while charging.
[Captivate Android Development] BL4zD:
Will you continue to release the regular uv kernels? I've never been able to reproduce the charge death since I've exchanged my captivate and got a 10.10 revision
[Captivate Android Development] glitterballs:
Errr.....wow, this could be interesting. I've kinda had my suspicions that this might be due to a hardware difference or defect. Have you left it in overnight in the wall charger? Like waaaay past a full charge? Seriously, how long has this been going on? I'd appreciate as many specific as you can get me, pm me whatever you think is relevant.

To answer your question, if straight undervolting instead of PMIC works and is stable for everyone, if anything, I'll probably drop support for the no oc/uv kernel, because if it's stable and you don't want overclock or undervolt, you don't have to. We'll see though, if there's enough demand for it, it's not really an issue to maintain three kernels, but if no one's using one, then why bother right?
[Captivate Android Development] bongostl:
Hi everyone---freaking out here.

just got my captivate.

was flashing with odin, and it just stopped.

for a while

did a battery pull, and now it boots to a black screen with a phone, then an orange exclamation point, and then a computer.

anyone know anything?

thanks!
[Captivate Android Development] glitterballs:
You can still get into download mode so don't worry. There are two things you can do, one is make a field test jig. I've also been able to get into download mode by holding all three buttons while plugged in to USB, the phone would start to cycle 'off --> phone ! computer', take the USB out then put it back in and I got into download mode. Field test jig only works if you had froyo on beforehand.
[Captivate Android Development] Dieabolical:
I flash ROMs all the time and get that from time to time depending on the postion I get myself into. Don't worry, you didn't brick the phone.

Make sure Odin is opened up on the desktop before trying this

1. Pull the battery out

2. Disconnect the USB to the phone

3. Press the volume up and down buttons at the same time and hold them both down (don't let go)

4. Connect the USB cable to the phone

5. Put the battery back in

6. See if that takes you to download mode
[Captivate Android Development] CNKirby:
I have also had success with this method!
[Captivate Android Development] cappyron:
So.. I've been thinking about trying a different approach for the kernel.. I'm thinking I'm going to try starting with the source we do have (2.6.29) and patch it up to .35 or so (since supposedly that's faster)... Hopefully that way I'll keep bluetooth working :)
[Captivate Android Development] bongostl:
thanks for all of the help so far, ya'll.

Anyone have any advice for saving battery life?

I'm blowing through bout 5% every 20 min, with the screen off, the phone unused.

I'm on the UV/OC kernel, and have it set to 0/25/50/75/100/100

This kind of battery drain makes it pretty close to unusable....

I would be fine on a different rom, but I really want to be able to keep the standard google calendar (I hate that i have to remember to select my GC when using the TW cal app).

edit--

i have tried the jj4 and jk4 modems...can't tell a difference.
[Captivate Android Development] loraque:
CM is currently a battery hog. They know about it, but are fixing things that are broken before tuning battery. I don't think there is anything to be done about it... yet.

BETA.
[Captivate Android Development] bongostl:
oh well.

would be happy with another rom....but HATE tw calendar. Why can't the manufacturers just leave enough alone?
[Captivate Android Development] TheEscapist:
You tried reseting your battery stats? I'm getting 16 hours with moderate usage, only 1-2% usage while idling. I'm assuming your turning off wifi,data,gps, etc while the phones not being used?
[Captivate Android Development] glitterballs:
CM6.1 eats up more battery than most ROMs, but it shouldn't be anywhere near 15%/hr. At some point, and I know you might not have time to do it today, but, do a battery calibration. If you flashed with less than a full battery, it can throw off your battery stats, which is why I say to do a calibration. If that doesn't work...of the top of my head I can't think of what would be causing drain like that. You flashed the Beta-3 ROM right? And then one of the 12-8 kernels?

edit - Glad to see you recovered from that brick. It's a learning experience. :) You might want to look up one of the threads on the Field Test Jig and have on handly juuuuuuust in case. (I do.)
[Captivate Android Development] glitterballs:
I posted a new modem in the main thread, it's a TLJL3 modem, I've been using it most of the day. It seems to be a little friendlier on battery so far. It might not turn out to be a winner, but I thought some of you would want to check that out.
[Captivate Android Development] tjsooley:
JK4 is good too
[Captivate Android Development] bongostl:
I bought myself a jig...thanks for the advice, ya'll. It is all really appreciated.

I see a ton of different instructions for recalibrating the battery.... how do ya'll recommend?

---

edit---

you da man, glitterballs.

and I protest; you should take donations.
[Captivate Android Development] ademejia:
Do you guys have GPS working on cm beta 3 I'm using gb kernel 12/8 I'm reading some do and don't?
[Captivate Android Development] biggem001:
i do, picked up while driving in about 15-30 seconds. Will give accurate resultes (~5-~15 meters) from 0 to 90MPH, sitting on mount on window.
[Captivate Android Development] ademejia:
which beta and modem are you using? im not having any luck with mine
[Captivate Android Development] Squeak22:
I'm using JK3 and the 12/5 release, haven't updated to the 12/8 release yet. I used GPS to drive about 4 hours yesterday and it worked fine for driving.

I was in the middle of nowhere and it was snowing heavily, but I still got passable GPS.
[Captivate Android Development] tjsooley:
My gps with beta 3 and jk4 rocks locks to 10 ft in 30 sec outside
[Captivate Android Development] glitterballs:
Sometimes I have to toggle GPS to get it to work (ie, turn it off, then turn it back on). I think I read there's a rare bug where the GPS is competely borked during install. Or something. Pretty sure I read there's a bug with some people with GPS.
[Captivate Android Development] glitterballs:
Oh, well, I absolutely do take donations as long as you give it to one of the people I have listed in my signature. :)

I really mean what I say there. There are people like me who can manage to compile a kernel and maybe make a few minor tweaks or changes to get things working on our phone, but the kernel hackers, the guys (and gals probably) who figure this stuff out in the first place, and then put their code out there for others to use are the ones, in my opinion, who really deserve any kind of monetary compensation. If you say thanks to me, and you enjoy your phone a little more, that's all I really want. And if you can't afford to give any of those guys a couple bucks, maybe just send them a PM or post in one of their forums and tell them how much you appreciate their work.

edit - where did you buy a jig at? I was actually thinking of making some and working out some kind of deal where you donate to a dev (not me, I don't even consider myself a dev) and I'll send you a jig.
[Captivate Android Development] bongostl:
I just ordered the parts. i got 2 of them for about $15 all in.

[
[Captivate Android Development] ademejia:
thanks for the gps help beta 3 kernel 12/8 jk3 modem

i got gps to work by toggling gps numerous times then i notice if i use the google maps first to search then click on navigation from maps it works faster.
[Captivate Android Development] sdotbrucato:
My signal is in and out which I'd imagine is due to lack of 850 band. I might try and push another modem and see what happens...
[Captivate Android Development] WickedStyx:
Is that 502 pit supposed to be 512 pit?
[Captivate Android Development] sdotbrucato:
I used 512pit so I'd imagine so.

EDIT:Pushed JG8 Modem, no dice... dont know how to check service menu on CM....
[Captivate Android Development] WickedStyx:
In that case I'll have to hold off for now. I only get 850mhz coverage.
[Captivate Android Development] glitterballs:
Yeah, my bad. First kernel should be good on the keys. I'll get the right one out in a minute with OC/UV.