yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] musicalmindz:
So when I woke up this morning my phone was stuck in a boot loop on the CM screen with the spinning circle arrow thang. Popping out the battery and rebooting doesn't seem to do anything. I can get into the recovery menu but not entirely sure what my best course of action is. Any ideas?

Im on RC1 and haven't done anything to do the phone recently so not sure what it could be. Thanks!
[Captivate Android Development] ThisWasATriumph:
I struggled with this for a while. Ultimately I had to wipe /data and restore from a backup. One time I got it out of the loop by connecting the usb cable and then unplugging it. Still not sure what causes it.
[Captivate Android Development] RCDuke:
Since you can get to recovery, try clearing your cache, then reboot. Otherwise reflash the RC1.
[Captivate Android Development] musicalmindz:
So I tried clearing cache and also wiping Dalvik cache. Neither helped.

I'm not sure how to reflash RC1 from recovery since I usually do it through Rom Manager. Will RC1 be available for me to flash from recovery if I did it through RM?
[Captivate Android Development] nbell13:
This happened to me once, factory reset fixed it.
[Captivate Android Development] RockRatt:
Go to recovery, wipe dalcich cache, go back tk recovery main section, install zip from sdcard, choose zip from sdcard, volume keys down to clockworkmod folder, (click through the folders until you see where the rc1 is located) into the menus until you get to "get", then select the rc1, click on it to install.

PS. I would suggest to try out the newest nightlies as they have everything that the rc's have and then added functions and features that make CM7 run better and better battery life too. Just mho.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Captivate Android Development] RichMD:
If you get stuck, it looks like wiping data does work according to some of the responses. My "theory" is that during the night an app update(s) happened and /datadata filled up to the point that it caused a reboot and it can't boot correctly with it completely full. This may make no sense but I thought I would throw it out there...:D
[Captivate Android Development] ThisWasATriumph:
See I would have thought the same when It happened to me except I had 50 megs free...
[Captivate Android Development] Twicebak3d:
If you can't find the zip to reflash, just mount from recovery and drag/drop. Clear cache/dalvik manually and flash. Clears that issue up for me every time.

On a side note, I find 179 to be the best nightly I've come across. Got 36 hours on battery underclocked to 800 - 100mv. I get no real impact on anything except 720p playback. Runs everything else smooth

as silk. I do hope for tv out one day, but I can live without it.

Thanks devs. My Cappy would be crappy without you.

Sent from a CM7 i897 that is quite possibly more than a few nighties behind.
[Captivate Android Development] musicalmindz:
Woohoo! Got my USB working finally and downloaded 179 onto the sdcard and installed from CWM Recovery and we're back in business.

I've never reflashed to stock since my very first time rooting so I am wondering if things get kludgy after tons of CM7 flashes? I think i've done at least 30 by now (mainly through Rom Manager and not through CWM). Any chance my latest bootloop failure is from that or just chalk it up to something random?

I'm also considering trying the Glitch kernel once version 13 comes out, hopefully that will help with my dismal battery life haha. Thanks again for the help!
[Captivate Android Development] ballz0iron:
You need to clear your phone by going to stock or atleast do a factory reset on cm7 once every few nightlies or your phone will get terrible battery life
[Captivate Android Development] Gromlakh:
Not true. The nightlies are just update files, there's no reason flashing one (or fifty) of them would cause you to have battery life issues. If you have battery life issues after flashing a nightly, it may mean you need to recalibrate your battery, but it's not a sign that you have to flash back to stock (which you should almost never have to do).
[Captivate Android Development] Twicebak3d:
+1

10 char
[Captivate Android Development] Thesandlord:
So I have a strange problem. Running one of the latest nightlies. Basically maps works fine, but navigation just sits at the splash screen and then it says to force close it but after doing that the phone vibrates without stopping until I pull the battery. I've actually had a few problems with this nightly so Im probably going to flash the latest one to see if that fixes my problems, but this was so interesting I wanted to share it.
[Captivate Android Development] johnhazelwood:
Check you battery stats and see if android os is way up on the list, like #2. I find that I have to reboot frequently to make the phone run normally.
[Captivate Android Development] Aus_Azn:
Same problem here, running 181.
[Captivate Android Development] RichMD:
That has happened to a few of us at least. I reverted to Maps 5.11 and that works. The workaround for 5.12 is to go into maps, find the location and then choose directions - it works then - just not if you go into navigation first when on 5.12. It happens with different builds and different kernels (glitch and stock)
[Captivate Android Development] musicalmindz:
Ok awesome I am glad I don't have to do that, it never sounds exciting.

I am hoping Glitch + some UV will help me improve my battery life otherwise I might have to try one of those larger 1850ma batteries. I checked my battery usage and Android OS is usually 4th of 5th on the list at like ~5% so I doubt that's the issue. Thanks though.
[Captivate Android Development] tiuk:
Thanks, had this exact problem and figured it was from the update.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] littlewierdo:
kanged.net?? Bad Gateway...
[Captivate Android Development] tiuk:
http://koush.kanged.net/cm/nightly/captivatemtd/

Looks like they only go to 150 though, guess that one is dated.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] _MuLder_:
Anybody else's phone shutting off while charging?
[Captivate Android Development] rexboy:
I have the exact same problem but not using cyanogen, using 2.3.5 custom rom.
[Captivate Android Development] bentonhall:
Yep. On 181 and have this as well.
[Captivate Android Development] JiroPrinz8:
Try latest kang on sixstringsg's thread, I'm using it and don't have this issue. It's basically the latest nightly with some tweaks added.

Sent from my *Glitched CM7 Captivate
[Captivate Android Development] GRACO:
I'm using 181 + glitch and no problems so far ...
[Captivate Android Development] aHecticLife:
Any update on the choppy 720p recording ? :(
[Captivate Android Development] tommyguns818:
I finally rooted my wifes phone with odin one click and loaded current nightly and so far everything is working well. I had it twice go into deep sleep and the only way out was to 3 button into recovery. I removed Setcpu and so far so good. I'm currently reading up on the Glitch kernel and I'm having flashing withdrawls. Cant wait to flash it. So far this cappy is a lightning bolt compared to what is was out of the box. Thanks again for the great help peeps.
[Captivate Android Development] Malorkus:
Same here. Reverting maps to 5.11 fixes it; Is this a CM7-specific bug or do other ROMs have the same issue? Does anyone with CM7 not have the problem with 5.12?
[Captivate Android Development] nbell13:
Same problem with 7.1 stable and glitch kernel v13.
[Captivate Android Development] RichMD:
I'm guessing it is the same with any CM7 based ROM - MIUI as well but that is a guess. I wonder if 5.12 has a modification where it tries to determine how much space is in /datadata so it could download maps of the surrounding area, etc. Maybe the small amount makes it have a problem compared to a SamSung based ROM which would have much more space? It can't be very widespread or it would have been fixed already since it has been out for a bit now.
[Captivate Android Development] boog:
Withe the navigation problem, see if it helps to reboot, turn on gps, open maps, let it find your location (or at least start the gps), then open navigation.

Mine works with 5.12, with the latest (as of an hour ago), built from source.

It also appears to happen after each reboot. Must be something in the way navigation tries to load gps? But, opening maps first seems to let it work.
[Captivate Android Development] RichMD:
Thanks - I posted that workaround with 5.12 previously. However, with 5.11 it isn't required. V5.12 is a problem with multiple CM7 builds and multiple kernels. They obviously changed something with the app that has a problem with a CM7 based ROM. My guess would be related to storage of data.
[Captivate Android Development] boog:
oops, guess I missed your workaround post. It is an odd bug though.
[Captivate Android Development] ninjuh:
Just flashed #181, trying to install gaps via rom manager & its saying, "Please update to latest rom manager!" then FC's...NEVER had this problem:confused:
[Captivate Android Development] mikehe:
got to be flashing and really enjoyed the nighly's but have i missed something havent seen a new one in a couple of days.
[Captivate Android Development] mcala:
Me either, not since the 16th. More like weeklies!
[Captivate Android Development] mikehe:
yes i am sure they are hard at work, but i need my nightly's please
[Captivate Android Development] bigbooty:
Don't see a whole lot left to fix....This is pretty solid right now.
[Captivate Android Development] RichMD:
Agreed. I think they started focusing on CM9 (ICS) - at least I hope so.... :)
[Captivate Android Development] bigbooty:
Yes to that.
[Captivate Android Development] mikehe:
no sense in getting worked up that we know absolutely nothing about, don't need any rumors floating
[Captivate Android Development] ou812bkewl:
Looks like atinm has already created an ICS Captivate branch on github and most subsequent submissions have been ICS related.

https://github.com/atinm
[Captivate Android Development] boog:
I had issues with it building from source, had to run 'make clean' and 'make clobber' before it would build properly again. I wonder if they are having the same issue, along with messing with ics.
[Captivate Android Development] dohboy15:
If you look at the change log, under "To be included in next nightly" there are a few ICS related things! It looks like minor stuff though, why would ICS stuff be added to CM7 nightlies?
[Captivate Android Development] Gromlakh:
If they're adding it, it's because it would offer an improvement of some kind. It may look minor, but it may be something actually big. Or, it might be laying the groundwork for bigger imports of ICS stuff.
[Captivate Android Development] dohboy15:
Oh ok, so are they "merging" CM7 with CM9? Or just adding ICS improvements to CM7?

Sent from my Rogers i896 running CM7!
[Captivate Android Development] sixstringsg:
Neither really. The second certainly not, CM9 is entirely based on ICS. They are merging ICS changes into the kernel, yes. I don't personally know if the Galaxy S series will ever see a 3.0 kernel, which is what ICS is based on. There are already ICS builds that work on our 2.6.35 kernels though. Therefore, some things need to get merged into our 2.6.35 kernel to play nice with ICS.
[Captivate Android Development] SweetwaterBurns:
Isn't fugumod based on v3.0 now? Couldn't we use that as a base for reorienting the kernel for ics on captivate?
[Captivate Android Development] Kaik541:
we don't need a 3.0 kernel to run ICS, and in fact, most of the useful things have already been backported from the maguro kernel
[Captivate Android Development] littlewierdo:
So, where are the current nightly builds being stored? I assume there are Kang builds being made available and I am hoping some fixes are being made for general stability, currently Im running 181 and it has a number of problems that are just bizarre in nature, these problems were introduced when the nightly in the 170's with a bunch of changes were introduced (179 I think).
[Captivate Android Development] Time_Zone:
I have not experienced any bugs using the default kernel. What are you seeing?
[Captivate Android Development] boog:
this might tie you guys over till the nightly bot is back up.

Edit: link removed

built from the latest source as of a couple hours ago :D and not modified in any way.
[Captivate Android Development] RichMD:
If you want KANG builds (MIUI battery, etc) then you can also use the location below

http://fitsnugly.euroskank.com/gigglebread/captivatemtd/
[Captivate Android Development] atinm:
Please post kang builds to a thread other than this - we really would prefer to just deal with builds that came from us or from buildbot. The reason buildbot is out of commission is because some hard disks need to get rebuilt due to a crash or something and the person who needs to do it hasn't had the time yet but hopes to have it sometime soon.
[Captivate Android Development] mikehe:
i see that if i have a picture and i want to share it one of the option is "HTC Messenger" it doesnt work on my cappy so is there a way that this can be removed or deleted from my options.

Thanks CM7 for the hard work

P.S.

what\where can i find other kernels to see if my battery will last longer or do i just have an old battery
[Captivate Android Development] cfili:
Thanks for the update! Many of us were wondering what happened.
[Captivate Android Development] veener79:
OK after watching the video this has clicked for how to do this. I am a very visual and hands on learner. Going to give this a try. Hate when I let me phone get very low on battery it takes for every to fully charge. :(
[Captivate Android Development] loserskater:
I know atinm has mentioned that he's going to work on this but I just wanted to chime in.

Actually it worked right before the captivate based rom came out. Xcal was working on it for awhile and the 2.2 leak just happen to come out at about the same time. This means that xcal did all of the routing based on the 2.2 i9000 source. And actually the Samsung EQ was getting in the way of it working properly which is why he released his app to bypass it. I'm very optimistic that atinm can get this to work without too much effort. I'm sure if he talked with xcal he could get it done in no time.
[Captivate Android Development] tbong777:
That's great but all i see is a lot of eye candy function...My excitement regarding 2.3 is the HARDWARE support. We don't have dual cameras, NFC is a year away for practical use, Sensors...do we have all of what GB will use? I think its great that those who want ASOP have at least that. but I rarely flash for eye candy. I can usually find that somewhere within the 2.2 world.

I think the SGS II will take full advantage of GB. I am reading this thread though with interest and will wait for a version that does not clip anything I have already and try it. If it takes nothing away and adds something like most ROMs I will certainly give it a go.
[Captivate Android Development] flashman2002:
Just stop talking about this then! Either you will flash it because it is a really great ROM built from Source or you wont. All I have seen is you asking what is there that is a benefit to the Captivate and for you it seems like there is no benefit so don't put this on your phone.
[Captivate Android Development] Kaik541:
while I'm sure you're trying to make a good point, I just don't see it. what is the point of a post like this? to let us know you aren't running it? using 2.3 isn't about eye candy. it's about having an AOSP-like experience, it's about trying to merge with cyanogenmod, it's about customization and configurability... let's not ignore the fact that there are also bugfixes and security patches in 2.3 that are still exploitable in 2.2 (how do you think rageagainstthecage root method works?). if you don't want to run it, that's fine, but I don't see the point of coming in here and going "this doesn't support everything about the android OS because we lack some hardware" (I don't see you complaining about a lack of JIT in 2.2 because the hummingbird processor wasn't really supported so you only saw mild improvements)
[Captivate Android Development] singlebeam:
I would love to see this also. I use exchange for work and can't stand the security policy enforcement that requires me to put in a password. I used touchdown for a while and eventually moved to the email.apk from the Galaxy Tab as I am a minimalist and like simplicity.

I have read this entire thread and haven't seen anything about this....it will be the deciding factor for me to flash. Can anyone confirm that the email.apk from CM7 will or will not require a password for exchange accounts? Thanks.
[Captivate Android Development] yoni45:
Bluetooth seems to be working much better than any 2.2 ROM I've ever flashed -- it connects flawlessly to my PC/laptop allowing full sound transfer (streaming both music and phone calls to my computer speakers). Car connection also seems to sound much better on the other end (I'd imagine this is less to do with bluetooth than with whatever is done to process sound coming from the mic?).

Long-press for switching music tracks while phone is locked is pretty sweet.

LockScreen gestures, especially when I removed the actual 'unlock bar' (so it's only unlockable via specific gesture) works better than any lockscreen I've used before (especially with music controls on the screen).

Ability to rotate phone 180 (upside down) is something I've never had, and I can see that being functionally useful sometimes.

Recent applications menu is far better (allows upto 15 recent apps, looks better).

The controls widget/notifications settings widget is fully customizable, providing far more options (arguably doable through a 3rd party widget).

Browser seems to fly in comparison (maybe it's me?).

Off the top of my head so far...
[Captivate Android Development] mcord11758:
Eye candy? You mean like every rom out for the captivate prior which is basically the same base with the same tweaks wrapped up in different themes. I mean as mentioned I fail to see your point. Several of us have kindly tried to express what is different. If you don't care to listen move on
[Captivate Android Development] Evilspawn:
Finally no more pop Samsung system sound....I love the asop system sound. Question: is there a way to make it louder cause its really low and I wanna show it off ;)
[Captivate Android Development] drwx:
you say that as if samsung will release the galaxy s 2 phones with gingerbread on them. i would imagine that samsung will release the galaxy s 2 phones with froyo and then ****-tease about gingerbread for 9 months like they did with froyo for the captivate.
[Captivate Android Development] waghoba:
I found this in my extracted apk's folder. I really don't remember where I found this but I am attaching it. Just make sure it works and have backup of your current email.apk . ALSO AS EVERYONE ELSE SAYS..I am not responsible for anything goes wrong :p
[Captivate Android Development] waghoba:
Have you tried settings-> CM settings -> sound ?
[Captivate Android Development] alec5216:
My screen on/off animations have stopped working. I can't figure out why. Does anybody else have this problem?

Solution (thanks to mcord): If using spare parts, set Window animations and Transition animations to normal. One is for screen off, the other for screen on.
[Captivate Android Development] techmik67:
Yes, atinm and xcal have spoken..... the GOOD devs actually share info......

Look at DSP manager app already on phone with cyanogen....

As has been explained several times now, SAMSUNG stuff will MOST LIKELY NOT WORK on an AOSP rom that has had all SAMSUNG framework removed.....
[Captivate Android Development] whyareyou:
I think the browser is hardware accelerated in gb, hence the pop in browser speed, this alone is worth it, imho.
[Captivate Android Development] coderunner:
If I remove adw, I am guessing the adw settings will still be under settings since it is part of the rom. am I right?
[Captivate Android Development] mcord11758:
If using spare parts put animations back to normal
[Captivate Android Development] majinzen:
No the settings will be gone.
[Captivate Android Development] waghoba:
lol sorry for asking this stupid Q's but I was just taking a chance :o. is there any way to enable the zoom and text re-flow in AOSP email. Thats what I actually want.
[Captivate Android Development] Kaik541:
make sure "all animations" is enabled under settings

browser is only hardware accelerated in samsung's leaked ROM, this code does not exist in AOSP, so this has nothing to do with it.

just install another launcher, the settings menu is only there as long as you use ADW (there is really no benefit to uninstalling ADW).
[Captivate Android Development] boog:
Will do! Sorry about that!
[Captivate Android Development] Raul77:
does anyone know of any KANG build that mounts external SD like MiUi ? in /mnt/sdcard/external_sd ?

Thanks,
[Captivate Android Development] Mantu13:
I'm suddenly having issues with my computer not recognizing my phone. Installed nightly 181 coming from the stable 7.1 build last Saturday. I know for a fact that the drivers worked fine before the flash and I'm 80% sure I've transferred files since then to my phone. My phone doesn't even seem to notice the phone is connected (not in device manager) now but it does charge via usb. Is there a way to see if my usb connector is messed up? I've tried several cables. any other ideas?

edit: wiping davik cache seems to of worked. computer now sees phone. Thanks for the people who made suggestions!
[Captivate Android Development] nbell13:
Did you install the Nexus S windows driver?
[Captivate Android Development] tsuda:
I have 181 and the USB works fine. So it's not the build.
[Captivate Android Development] Mantu13:
Yeah I had the nexus s drivers installed. Tried reinstalling them but that didn't seem to do the trick. Tried in 2 other computers and didn't have any luck. I guess I'll try to reflash tonight but I'm not thinking it will work
[Captivate Android Development] nathanjones:
Try pulling the battery (so not JUST power cycling). Twice mine has gone kinda crazy where it would charge, but not have usb development or usb mass storage.
[Captivate Android Development] Aus_Azn:
No. That's a change that is largely unfavourable with the community, as far as I've seen. KANG builds occurring right now are due to the Nightly bot being down, or cherrypicked changes while still sticking to CM and AOSP standards.

That's just wrong, man. The accepted standard for AOSP is /mnt/emmc/
[Captivate Android Development] CptTwinkie:
Wasn't that added and reverted not too long ago in the nightlies? I heard it caused more problems than it solved. Can anyone from teamhacksung comment?

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] tiuk:
I think you're referring to the ability to mount external sd as internal and vice versa.

Sent from Captivate, CM7.1, Glitch.
[Captivate Android Development] Aus_Azn:
Well, it's finally time for me to bow out from the Galaxy S Captivate for good now.

Just got a HTC Vivid, and the way it looks, I don't think I'll be back.

Thank you very much for all of your effort, Captivate Dev Community, with a special tip-of-the-hat to the CM Team and MikeyMike01. It's been a lot better than it would have been.
[Captivate Android Development] riceje7:
i need to root and flash cm on a captivate for a friend, his captivate is already on gb so what is the preferred method for flashing cm as the op says to be on eclair/froyo. is this still the case, or can i just flash cm from cwm once i've rooted it?
[Captivate Android Development] Gromlakh:
If it's not already, flash one of the many i897 GB kernels that have CWM recovery baked in. Boog's, Samurai, Corn, etc. Just match it up to whatever GB release he's running and flash the appropriate kernel.

From there, just flash the CM7 installer package from CWM recovery. If it pops up some text, reboots back to recovery, pops up similar text, and looks like it's hanging...that's normal. Just wait.
[Captivate Android Development] riceje7:
sweet, i'll give it a try thanks