yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] lpfansether:
Christopher,

This is an intended change and not a bug. It supposedly wont be a problem when 2.3 rolls out. The way it's set up now though, only one card can be read on our phones. From my understanding (and I could be wrong), this is due to aosp and samsungs awkward build. I'm assuming they chose to have the external card mount so that the phone can see it instead of the internal because external capacities are much larger. If, however, you're like me and don't have an external nor plan on buying one soon you may want to get used to abd pushing. You can simply replace the vold.fstab and vold.conf files with one from another rom (I used premonition b5). If you know what you're doing, you can edit those to files rather than injecting them from another rom and it's probably a better idea. I'm really new with android and definitely not a programmer but wanted to share what I've learned and what has worked for me.

Sent using XDA App
[Captivate Android Development] Sebring5:
This was fixed on Beta 2. Check and make sure you are flashing Beta 2 both rom and reorient kernel. Flash again.
[Captivate Android Development] Sebring5:
My understanding is this will not be fixed and you need to purchase an external SD card. They are cheap. I put one in and resolved these issues. From what I have read this is the way Samsung roms will be structured going forward. Only Samsung apps or files will be saved to the internal SD card. Everything else requires an external SD card.
[Captivate Android Development] Athailias:
The i9000 Cyanogenmod guys have left xda because of "noobs" bugging them. We should be carefull not to annoy Glitterballs or we may lose our source for kernels :P
[Captivate Android Development] seivad17:
My battery life is better than usual.
[Captivate Android Development] NiXXeD:
Captivate is not yet supported for the mod. I would wait to avoid annoying them more.
[Captivate Android Development] NiXXeD:
Clockwork is already built into the kernel. There should be no need to install it again.
[Captivate Android Development] Smallsmx3:
Is anyone's cell standby high using jk3? Everytime I turn on my phone the data arrows are searching....cell standby is always really high. 30% or more. At work cell service sucks but. I could always get through an 11 hour shift. I didn't even get ten hours. I didn't use my phone at all and cell standby was almost 60%. I was using the oc kernel and I switched so maybe that will help. Is anyone using the jj4 or ji6 modem?
[Captivate Android Development] fatttire:
Lol what's funny is there are now noob questions on their cyanogen forums.

I'm totally cool with their decision to close off support... as long as they keep working on it.
[Captivate Android Development] Squeak22:
Yeah, but I think codeworkxx (Aery) has moderator privileges over there in the i9k subforums, so he can control it better.
[Captivate Android Development] glitterballs:
Oh, come on, I don't come off like that do I? I mean...most of you guys aren't too bad. I understand why aery did what he did, I probably would've handled things differently were I him, and until I can do what he can do (probably never :)) I'm certainly not going to criticize him, especially when he's doing all of us a favor.

If you don't know how to do that already, or can't learn on your own, just try to be a good beta tester. Learn how to use adb, logcat, dmesg. Also, the kernel itself hasn't changed much, very little actually.
[Captivate Android Development] tjsooley:
has anyone tried the nightly beta 3?

will it work with the b2 kernel
[Captivate Android Development] ademejia:
i did this the other day bluetooth will not work
[Captivate Android Development] NiXXeD:
This is why people get angry over XDA forums. Both of you need to read. I'm not even going to answer.
[Captivate Android Development] DOAlaboratories:
Did you flash the initial kernel?

Sent from my Cappy using mental telepathy, *****ezz.
[Captivate Android Development] aqtrans:
I've only been running it for a few hours, but so far so good for me. I'm really ecstatic to finally have a non-Samsung ROM operational on this phone.

At first I was having a problem installing Angry Birds (and some other apps, but I needed my Birds above all), but simply running "vold" in ADB seemed to fix it :) And when I was restoring my apps with Titanium Backup, the Market would FC after almost every app, but it didn't seem to affect anything after.

As far as I know, voice works, I called my voicemail and the machine picked up my voice. Data and wifi working great.

I'll see how it holds up throughout the day tomorrow...

@mkurzum: I just commented out that line in the updater-script.
[Captivate Android Development] chipsa964:
Can anyone post some screenshots of what this baby looks like?
[Captivate Android Development] chipsa964:
Maybe it's just me, but I don't really see a big difference other than the stock look of the status bar icons. Can you tell me what you feel is so good about this rom compared to, say, Cog/Doc/Di11i ROMs?
[Captivate Android Development] Dani897:
it is built from source. it's at a minimum a stepping stone to ports and more sophisicated development because it has stock froyo as a starting point, it is not a touchwiz rom with a few stock looking componants injected into it. the idea in aosp is that mods from other phones can more easily be ported. it's not just about the look of the rom or the software it contains.

edit: on another note has the bluetooth driver been changed? i mean can this run the wii mote software? and is there potetial for a hsupa modem to work with working bluetooth audio?
[Captivate Android Development] chipsa964:
Oh, I see. Well Gingerbread is rumored to come out pretty soon so we are never gonna catch up as far as flashing new roms go :-p
[Captivate Android Development] aqtrans:
To me, most changes are just that everything works like it should :p. For example, Google's cloud settings backup actually restore, and apps you previously installed automatically reinstall when setting up your Google account. Facebook contact syncing works inside the app, not using Samsung's plugin.

There aren't two apps for phone and contacts, it's one app, with tabs for each.
[Captivate Android Development] chipsa964:
That sounds pretty tight. What bugs have you seen so far?
[Captivate Android Development] DOAlaboratories:
CM is now flashing, kernel comes next :D
[Captivate Android Development] mkurzum:
Got it to work, restarted the whole process from scratch.

Flashed jm8/pit 502/re-part

Flashed JPM/pit 803/no re-part

Booted into OS

Booted into recovery

Did a wipe/restore

Flashed cyanogen rom

Flashed reorient kernel

Flashed Rogers modem

This method worked for me, I came from the latest cog, with voodoo disabled.

I'm loving it, feels like I'm back on my good old nexus
[Captivate Android Development] bedwa:
For some reason my home key and my back key both act like back keys.... Hmm.....
[Captivate Android Development] darkamikaze:
lovin this community. I previously heard cm won't be coming until march if we get lucky :).. looks like i'm getting lucky WOO
[Captivate Android Development] DOAlaboratories:
home button functions as back.
[Captivate Android Development] mkurzum:
Home button doesn't seem to work with the overclocked kernel, flashed it 4 times, everything works fine with the regular kernel.
[Captivate Android Development] sdotbrucato:
Anyone mind posting links to JPM downloads? Search doesn't appear to be working...
[Captivate Android Development] mkurzum:
This is the place for stock odin roms

http://www.samfirmware.com/WEBPROTECT-i9000.htm
[Captivate Android Development] sdotbrucato:
Ugh, I'm on XDA too often, I forgot all about SamFirmware. Thanks!:D
[Captivate Android Development] WickedStyx:
Has anyone tested this with 850mhz? If not I will post my findings later on
[Captivate Android Development] sdotbrucato:
Flash went successful. Really liking it thus far. Will compile bugs as I use it.

I'm going to have to push Swype and hopefully Allshare, but other than that, I'm very happy!
[Captivate Android Development] Smallsmx3:
Ill answer. I'm still learning but I would say I'm passed noobanism. If u flash beta 3 over the beta 2 kernal it will boot but the changes that were made wont be applied because they are made in the kernel. So its pointless until an updated kernel is put together
[Captivate Android Development] tjsooley:
Thank you I did found this answer but other people did say that it fixed bluetooth.
[Captivate Android Development] ademejia:
i was just answer the guys question
[Captivate Android Development] glitterballs:
Not quite. Pairing works, discovery is broken. Wifi and USB tethering still crashes. So even if I were to spin out a new kernel with updates, you know what else we'd have working? Nothing. And on top of that, the last thing I want is for people who have different hardware submitting bug reports and wasting their (edit - Aery et al) time with problems that aren't theirs to fix (edit - which has actually already happened). Actually the last thing I want is for a bear to bite off one of my hands. Kind of off topic, but you get what I'm saying.

I'm still trying to figure out why our phones crash when charging with OC/UV kernels. The other day I said that i9000s have had this problem, and I think I was wrong about that, but it's clear at least setiron's kernels and Vibrants have had the same problem as well.

Backlights have been completely fixed and can by controlled by the app now thanks to neldar. Someone asked about a initramfs fix...yes it could have been done, but in my mind, rebooting your phone to turn them on and off isn't a good fix. It's functional, but I want to be able to turn them off before I go to sleep at night so they aren't on all night if I get an email in the middle of the night.

When/if raspdeep and I can get the OC/UV thing figured out, I'll push out an update with 100% BLN and hopefully a fixed OC/UV, and perhaps whatever else is functional with CM. I did ask Aery if it was ok to release a kernel for Captivates, and he gave me the greenlight after the cell radios were fixed, but's very clear he only wants people who can debug using this, even though, I think in several people's opinions, this ROM is not only very usable, but probably better than most other froyo ROMs to date for captivate. So, I'm kind of walking a fine line between giving you guys updates and giving you guys things that are still kind of broken that the dev really only wants people who can debug to be using. I hope you all understand I'm not holding anything back intentionally.
[Captivate Android Development] plasticdarlow:
Makes Sense... Thanks for the update:cool:
[Captivate Android Development] tjsooley:
Understood,

thanks for all your hard work
[Captivate Android Development] Sebring5:
Thanks for doing what you are doing. There is no question in my mind you are doing the right thing. I think this rom is the greatest thing since sliced bread and we have you and someone who is getting donations from me to thank. Thanks again.
[Captivate Android Development] glitterballs:
**** that, this **** is cooler than sliced bread. :p

And seriously, I'm glad others are supporting the real devs. I mean, so many people run around here with donate buttons, most of whom seem to do jack ****, and there are guys like Master who kang the the **** out of others people's work and pass it off as their own and ask for donation, there are guys like setiron and myself who patch together other people's work (and are honest about it), but the guys who really make our phones awesome are the guys like Aery, sztupy, supercurio, raspdeep, neldar, xcaliburinhand, etc. These are the guys who really deserve our support and thanks. And if you can't toss them a couple bucks, at least say thanks.

Ok, on to other issues. No one who has used a non OC/UV kernel had had sleep death right? I'm going to need some more guinea pigs to help figure this out, but I need some input on that last question. (Thanks to everyone who tried the workaround, now we're gonna fix the code in this *****.)

Sent from my brain using thumbs 2.0.
[Captivate Android Development] aqtrans:
Yep, I've been running the latest non-oc/uv kernel since it's released, leaving my phone on the charger all night, and not one occurrence of the sleep death.
[Captivate Android Development] mkoby:
I haven't had the sleep death while charging but I did experience it on my way to work this morning. I'm using the non-oc/uv kernel. My phone was on when I got in the car to drive to work. When I got to work it was off (was in my shirt pocket the whole time). I had 98% on the battery when I turned the phone back on.

That being said, I've had the ROM installed since Tues. and this is the first time that has happened. It was a occurring multiple times a day on the stock ROM, and at least once a day on other roms.
[Captivate Android Development] glitterballs:
There may or may not be other issues that cause sleep death when using i9000 ROM. It's clear this is happening with setiron's kernels, and some Vibrant kernels (actually eugene seems to have fixed this, and I think I know what he did, but I want to be methodical about it). Everyone seems to ignore it or just deal with it. To isolate a single variable, we need to know about sleep death while charging. (Thank you though.)
[Captivate Android Development] seivad17:
Using non OC/UV Kernel for 3 days with no sleep of death. I leave it on the charger all night every night.
[Captivate Android Development] cchant:
Same here. I've been running it since launch
[Captivate Android Development] darkamikaze:
I had one shutdown where I clicked the power button and it was as if I just turned on the phone using the Non-OC
[Captivate Android Development] sportedwood:
Just switched back from my aria running cm6.1 this afternoon, after the 3rd time i reached for my captivate today, while plugged into car charger, and it was off with a charging logo I switched back to the aria :cool:. I really want to use my captivate but there are some things about CM that I'm so used to now, anything I can do to help with this charging issue let me know but not sure what to do :confused:
[Captivate Android Development] fatttire:
Get the non oc/uv version
[Captivate Android Development] sportedwood:
Ill give it a go and report back tomorrow after my drive to work.
[Captivate Android Development] lpfansether:
Not sure if you want more people reporting on this too, ditto to the quote above. I never flashed the OC/UV as it isn't that important to me.
[Captivate Android Development] tjsooley:
Ditto Ditto
[Captivate Android Development] loraque:
I can confirm the following-

I initially flashed the OC kernel, and the first night left it plugged in to the computer, and it was off-dead in the morning. Fully charged when turned back on.

I then flashed the non-OC kernel you made available, and last night I left it plugged into the computer all night without any issue this morning. Fully charged.

I have also run SetIron's kernel in Mikeymike's ROM prior to the CM beta, and got a crash on that kernel (OCUV too), when the phone was OFF but plugged into the computer. That one actually had the kernel panic screen waiting for me in the morning.

I am unable to detect the difference in performance, which means OC fails my human test for overclocking :). The human test being, if you cannot tell the difference without running a benchmark, then you don't need it!

Does hacking on your phone bring back the early era of overclocking P60-90's? Totally hitting my old school gadget reflex with this phone. Fun times.
[Captivate Android Development] glitterballs:
@ loraque

Do you know what version of setiron you were on? re: overclocking- the only time I notice a difference w/ overclocking is when I watch flash video. @1200MHz it's flawless. @1000MHz it skips a little. Generally though, I have the clock speed limited to 1000MHz.

Sent from my brain using thumbs 2.0.
[Captivate Android Development] loraque:
The thread was here- http://xdaforums.com/showthread.php?t=818030

According to the version notes, 1.3.5 during my time there, which was the first i9000 rom I tried. I will have to look again for some stuttering during video playback. If I notice, I might run it OC since the phone seems to be able to handle it.
[Captivate Android Development] votum:
So I am unable to get my computer to recognize my phone with CM on there, trying to flash away, will it be safe to just flash something else in CWM?
[Captivate Android Development] votum:
Nevermind...CWM keeps failing on line 4, formatting system

edit: think I fixed it, flashing jf6 now
[Captivate Android Development] votum:
Nope, its bricked lol.
[Captivate Android Development] Squeak22:
You have to Odin it back. Make sure you select with partitioning when you do it. Can you get into download mode?

Its almost impossible to brick these things.
[Captivate Android Development] votum:
It goes into download mode 1 out of 20 times, rest of the time screen stays blank but pc recognizes it as an unknown device.

Already have a replacement on the way from ATT, won't turn on so they won't be able to figure it out either. I'll keep trying with odin though
[Captivate Android Development] wstahlhut:
have you tried ADB to get it into Download, it helps...
[Captivate Android Development] Athailias:
There is a new nightly on cm. It reads as beta three in the about phone menu.
[Captivate Android Development] plasticdarlow:
Where you able to flash it? Is it just me, ir is cm down right now? (Internal server error)
[Captivate Android Development] glitterballs:
What do you mean it won't turn on? Literally nothing at all? Or phone ! computer? These things are reeeeeeaaallly hard to actually brick, there are a bunch of safeguards Samsung built in. You shouldn't give up because it may happen again and you're essentially saying that a phone is smarter than you ;) ...you need to show it who the boss is.

@ everyone else- I'll try to get a new kernel out soon. I got a few things to do today, so it might not be til later today or tomorrow.

Sent from my brain using thumbs 2.0.
[Captivate Android Development] loraque:
Give this a try, as it just happened to me. This worked.

http://xdaforums.com/showthread.php?p=9330685&highlight=red#post9330685

Originally Posted by Mattwp103 View Post

So its my first post here and I have come across a fix for the screen not turning on I plugged into the computer via USB and removed the battery reinserted the battery. Then held volume up and power till red text came on the screen from there i switched to holding both volume buttons down and power then when the red text flashes to black release power and continue to hold both volume buttons. That should get you back to the downloading digger bot. If this helped you or was already posted let me know. thanks.
[Captivate Android Development] jwlsinx:
gb, is there any chance I could get the patch set you use to reorient the kernel? I'd like to do some development / debugging work on the kernel / rom, but that means I'll need to do my own compiling, and I don't really want to have to re-invent the wheel here. Also, are you compiling this in a 64 or 32 bit env? My box is 64 bit archlinux, but I'm thinking of installing 32 bit ubuntu inside of a vm to handle compiling.

Thanks!
[Captivate Android Development] tiger4j:
Since he might be busy... I'm not too incredibly experienced with this at all, but I do recall reading a while back that 32 bit was the way to go. Lucid, if I'm not mistaking, as I don't know if meerkat had everything available in repos. I might be wrong, but I don't think you would go wrong with that.

*develop away* :-)
[Captivate Android Development] tjsooley:
GB look,

http://xdaforums.com/showthread.php?t=858724

over on the vibrant forum it appears they have a beta 3 kernel that all the voltage and oc problems they were having (which looks like the ones we are having) were fixed.

also they have a reorented beta 3 kernel will that work on the captivate?
[Captivate Android Development] votum:
It does something, because the computer recognizes it as an unkown device as soon as I plug it in, battery or not. I can get the red text but that work around doesn't work to get me in download mode. The phone isn't smarter than me, I just do not want to spend hours and hours flashing it. I could get JF6 to work maybe 1 in 10 tries before this...now d/l mode takes maybe 20 tries, do the math thats 200 times pulling my battery and reconnecting and holding buttons, pain in my ass and ATT will just send me a refurb anyway
[Captivate Android Development] tiger4j:
Votum. If you have different USB cord try that. Also check your micro USB connector plate inside the slide door for corrosion. I had corrosion on mine after about a month of getting it with similar symptoms. I used a very thin piece of cardboard to clean plate and fixed it. Might also delete drivers and reinstall, I've had to do that before. Hope you get it straightened out.
[Captivate Android Development] votum:
Thanks for the advice, its all mint in there, been using 3 different USB cables in 10 different USB ports and 2 different computers, uninstalled and reinstalled drivers, everything I can think of. Its got no water/physical though so ATT will take it back for sure. Verbal contracts are binding in WA and in the disclaimer they have to tell you over the phone before sending a new one out they make no mention of tampering with the software, so if they do find out for some reason it won't matter. Plus I'm military so free lawyers if they do charge me 500 lol. Not too worried about it, will be back to it on Wednesday
[Captivate Android Development] votum:
Just wanted to throw one more thing out there after not being able to find it online at all, yesterday about an hour before the phone died I got an OTA update message. Am thinking that it might have started installing while I was away, then the OC/UV kernel died in the middle or something. Not exactly sure, and have not been able to find anything about an OTA update other than the one in September. Might not be relevant but I'd advise you guys to watch your phone if that message pops, I never said OK to the update but I have never gotten an OTA update and don't know if they are auto or what.
[Captivate Android Development] jwlsinx:
Hey, NiXXeD I finally had time to go through your guide. See my thoughts below:

the initial kernel provided by Aery is an Odin flashable i9000 kernel. The kernel provided by gb is a zip that can be installed in recovery (the zImage's are different sizes, so I'm assuming that gb has made some changes to the kernel).

before installing the zip (and after installing the new modem) you need to do a factory reset (I didn't do a backup first). otherwise, the phone will not properly boot - which did happen.

Other than that it looks good.
[Captivate Android Development] BL4zD:
Has anyone had any success building a kernel yet?

I've set up my environment and grabbed the source, etc. but I don't know which defconfig to use. Does anyone know?
[Captivate Android Development] TheEscapist:
Not sure if you're still looking for this info, but I just had a sleep death on your oc/uv kernel while on your beta 2 kernel while charging. Never had it on Setiron's under Perception B4.

Also, usb storage mount doesn't work with the modded vold.fstab. Maybe because of that, might not work at all.

So far, that's the only issues I've had, other than not finding a working Swype. Thanks for throwing this together, it's an awesome help.
[Captivate Android Development] Athailias:
I hope you were too busy to build a kernel, because there was a new nightly last night. hehe
[Captivate Android Development] Smallsmx3:
There's been a few nightlys since beta 2 dropped.....its been really quiet since they left xda. Doubt well see any updates till it gets out of beta. Its fine though. I've been running beta 2 since it dropped without any problems. If it runs this good as beta 2 I can't wait till a finished product or near finished..
[Captivate Android Development] Athailias:
Ive been running the nightlies without reorient. I just turn off autorotate and keep a modified plug in my headphone jack.