yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] MechaGen:
Can someone please tell me why I can't see newly downloaded zip files in CWR on my wife's Captivate? I've tried different locations, download directly to phone, download on pc & transfer to phone. Nothing seems to work.

I've flashed a number of modems on my Captivate, & finely found one that works well but every time I try it on her's, I don't see the files.

Rom Manager: current recovery, 3.x.x.x.

CaptivateMTD

CM7 Nightly's #124

Appreciate any help.

Sent from Tapatalk, NOOK Color CM7 Nightly's!
[Captivate Android Development] EnemyOfGlaDOS:
That should do the trick.. but I don't use TiBu.
[Captivate Android Development] airtower:
Rom manager is picking up nightlies again
[Captivate Android Development] techmik67:
to turn off LED notifications, either turn them off in each apps settings under LED settings, or go to cmsetting>sounds>quiet hours and choose "dim LEDs"

also, stop complaining about the LEDs not staying lit with the screen, like Keep The Lights On.... as I said, we are aware and are working on it..... if you cant be bothered to read the last few pages to see if your question is there you shouldnt be using CM .....
[Captivate Android Development] SweetwaterBurns:
Check to see if 'use internal storage is checked' under cyanogenmod settings - applications. That setting swaps internal and external storage under cm but not cwm. You can either try copying the file you want to flash to emmc or toggle that to go back to default. You might lose access to apps that aren't installed internally if you do.

Can't think of anything else that might

be the issue, hope it helps.
[Captivate Android Development] nkrick:
If you want to "redo" CM to try to improve battery life, just using ROM Manager / CWR and doing a clear data / factory reset will have the same effect as flashing to stock. I have done a reset twice now with a boost in battery life both times. Unfortunately, once I start flashing nightlies, battery life starts to degrade again. The same thing applies to flashing to stock. It seems to improve battery life, until you start flashing nightlies.
[Captivate Android Development] astrocrep:
Thanks going to do this now after I flash the latest nightly... it's just been bad since I've been rolling in them... I lose like 50% in 4-5 hours!!
[Captivate Android Development] shaolin95:
Am I the only one that gets a million reboots with each new nightly? It takes me a while until it gets stable. I mean reboots as in it reboots...tries to load all stuff...then I get the Android logo thingy again...tries to come back and same thing....it takes me way too many tries before it works.

This started for me like on nightly 72 or so.

It seems I need to install clean all the time now.
[Captivate Android Development] ou812bkewl:
Does it do it when you clean install too or just when updating?
[Captivate Android Development] shaolin95:
Updating only...not sure what changed after nightly 70 or so...or maybe some program I have running makes the problem...hard to pin point.
[Captivate Android Development] johnhazelwood:
I don't think I get reboots after updating, but usually I update..play with it some..then set it down overnight. The only weird thing I've had happen once is I woke up one morning to find the phone was in setup mode (like a clean install took place and everything was wiped out). Fortunately I had a nandroid backup so I could restore, but thought that was super odd.
[Captivate Android Development] shaolin95:
I am going to just install fresh on this one I guess. Being trying to get it stable since 6am and it is almost 11am now....of course I am at work so I am not at it all the time but it should have been done already. lol
[Captivate Android Development] XsceneXhippieX:
i would think its a hardware going out issue due to overclocking maybe, i could be wrong but ive never gotten anything even remotely similar and i even updated repeatedly, like the same data went through 5-6 nightlies with nothing like that happening, i did however experience performance degradation with said process, which is why i now try and wipe every update
[Captivate Android Development] nkrick:
There was a bug somewhere back then that causes boot issues, but it was only in a few nightlies before it was resolved. I don't remember the details. I do know that I have not experienced any boot issues since that bug was resolved.
[Captivate Android Development] EnemyOfGlaDOS:
Something is definitely up.. never experienced this.. :(
[Captivate Android Development] shaolin95:
Nah if it was hardware related it wouldnt happen only when upgrading plus a fresh install wouldnt fix it..I suspect some of my million programs creates the issue. No biggie, a clean install from time to time is not bad either. :)
[Captivate Android Development] RockRatt:
I don't have rebooted at all but for some reason when I flashed #127 over top of #126 after ONLY clearing dalvich cache my slide lock screen came up, I slid to open it and got tons of fc's that wouldnt stop (for everything it seemed) and only had a black screen with all the piled up fc's. I held all three buttons and went into recovery and flashed a second time and then it came up with no issues. I noticed after #127 that the cwm version changed to cwm 5 something. Maybe why something weirded out due to the cwm version change?

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] dannyfritz:
I used to get charger deaths every night nobody else seems to get, but the latest kernel (124?) seems to have fixed that. Sweet. I have an alarm clock again.
[Captivate Android Development] RichMD:
If wiping data/factory reset really is equivalent to flashing stock, then I assume that means we can start with a custom GB ROM (Apex, etc), and wipe data/factory reset, dalvik, cache, and then flash the CM7 nightly zip. Is that correct? I tried asking a few pages back about flashing KF1 stock before CM7. It works and I haven't seen any noticeable problem but I'm not certain if there could be any intangible effects such as battery drain, poor signal, etc compared to apps FC, etc.
[Captivate Android Development] skatcat31:
No. what he means is that it it's the same as if you flashed cm.from stock again, and nothing else. Cm7 doesn't use the same file system as samsung roms, so odin to stock is required to change the partitions back

Sent from something from somewhere
[Captivate Android Development] nkrick:
Installing CM 7 repartitions the phone and changes the partitioning type. It will probably work to start on KF1, but I have not heard if anyone has tried it and it is not the "supported" method in the instructions.

Since CM7 does not touch the bootloaders, you can always try going straight from KF1. The worst that could happen is a boot loop. As long as you have 3-button combo, you can get to download and odin to stock at that point. It would really be no worse than doing an odin to stock before you start and it could have the benefit of working and saving the step of odin to stock.

*edit: If your phone blows up, I am not responsible. The "right" way to go to CM7 is to follow the instructions in the OP.
[Captivate Android Development] MechaGen:
Thanks, that was it! Don't think I would have found that one by myself.

Sent from Tapatalk, NOOK Color CM7 Nightly's!
[Captivate Android Development] RichMD:
Thanks for the info. It reinforces what I was thinking. Odin to stock is required if I try a Samsung ROM after CM7 but not vice-versa since CM7 repartitions via a CWM flash. My phone hasn't blown up yet but I understand your disclaimer. :)
[Captivate Android Development] brandon_L:
I've been running CM7 for three days now and am very impressed. My battery life is just as good as other ROM's I have ran and performance has been great.

Here is how I installed from Apex 10 and I9000 gingerbread boot loaders. The CM7 FAQ for SGS Users states that

Note: As of Nightly 78 (Captivate), Nightly 77 (I9000), or Nightly 75 (Vibrant); the gingerbread bootloaders are now compatible with CyanogenMod 7 and external SD card is accessible. They are not required for the ROM to work properly and you do not need to flash them as the froyo bootloaders work just as well.

The first thing I did was switch to the I897 captivate gingerbread boot loaders found here. Worked quick and easy. (I9000 boot loaders may have worked, but I wanted to get on "captivate" loaders. Not sure if it made a difference or not.)

As far as flashing to stock I used [MOD] {One Click Odin} Stock I897UCKH3 with boog_kh3_kernel3, NO Bootloaders I tried to flash CM7 without this step but the flash failed. This will get you to a basically stock ROM with the correct Captivate identification and partitions, while still keeping the gingerbread boot loaders if you decide to move on to another ROM later. The kernal has CWM, so from here you can flash CM7.

Of course I did a factory/data reset before flashing.

This is what worked for me. I will probably use the I897UCKH3 above as my "flash to stock" from now on.
[Captivate Android Development] geminihc:
anyone have issues with nightly build 127 with bluetooth?

i simply just cant turn it on, i press the icon and it doesnt get "checked" and gets stuck.
[Captivate Android Development] musicalmindz:
Good to know, I wasn't looking forward to Odin/Re-Root, I haven't done that in forever haha.

Ill try it this weekend and see how it goes, thank you!
[Captivate Android Development] FireRaider:
I had this happen a while ago. A clear data/factory reset was the only way I could get it working again. But its worked since.

sent from XDA app
[Captivate Android Development] pandakh:
Ive been having camera fc's like crazyy! Anyone know how to fix it... It ruined my day...
[Captivate Android Development] CalvinL:
Is there an issue with nightly 103? It's been draining my battery like crazy.

I've barely turned it on, and it drains a few % per hour. It says 49% of my battery is just "Android system."

Shouldn't display be the highest number? I charged it to 100% at 8 AM. It's 11:26 PM, and drained to 47%. Keep in mind, I've only made about two calls and checked it for the time about 20 times. NOTHING else.
[Captivate Android Development] EnemyOfGlaDOS:
Not sure about the battery drain issue..but why not update to a newer nightly? You may find better battery life :-/
[Captivate Android Development] skeepon:
whats the upside to having gb bootloaders?
[Captivate Android Development] gilpdawg:
That happens sometimes. I find that a quick reboot after unplugging from the charger helps keep that from happening, as well as rebooting after it happens to stop whatever is going haywire.
[Captivate Android Development] \/icious:
I personally haven't. You can try wiping your caches, fixing permissions, making sure datadata is below 90% and reflashing the current nightly . If none of that works reload a backup or its time to start over again with a clean install.
[Captivate Android Development] buttstache:
I was going to put CM7 back on my phone, this time using nightly 127. I flashed back to JF6 using Odin one click and followed the instructions for installation. They're basically the same as any other rom so it isn't really tough.

Now though, it just boot loops. It never installs, mind you. ATT screen, then Cyanogen screen, then it shows some text scroll by in CWM before it reboots and does it all over.

The text, what I can read before it disappears, says it can't find a file or can't open something. Really kinda frustrating. I didn't have this issue when I installed nightly 92, but it gave me mad FCs everywhere constantly so I switched to stock KH3 for awhile. Was gonna give CM7 another shot, but it's not looking so good.

-edit-

Oh, ok, so apparently flashing CM7 now swaps the position of your SD cards? I put the nightly zip on my external sdcard and now it's installing and stuff. Hey, just FYI, this is really dumb + not mentioned ANYWHERE in the installation instructions. Step 5 of the harder way even says INTERNAL sd card. Whatever, it's installed and now I gotta go swap my cards back to where they should be. Just a warning to others.
[Captivate Android Development] quick6black:
did you try calibrating you battery. I am on 126, calibrated the battery and using some different scripts and only dropped 12% over night in 8 hours.
[Captivate Android Development] cbasse:
I could be wrong, but I think you did something wrong...
[Captivate Android Development] EnemyOfGlaDOS:
Hmm. I don't think it does. Doesn't for me anyway. I ALWAYS put the zips on my internal SD card. (External is full) And the zips are always right there! Been flashing CM zips since March and none of that has changed. ;)
[Captivate Android Development] johnhazelwood:
It should be placed and flashed on sdcard, not external SD card (which not everyone has).
[Captivate Android Development] anishz:
guys i have been using miui for a long time, have used cm7 before (nightly builds 78-104), but i flashed nightly 126 (back to stock and all), everything was fine except market, lot of FC's (would work only for 5-7 secs). :mad:

tried clearing market cache, fix permissions, data wipe reinstalled again, but nothing seems to work, i had flashed the latest aug something gapps.

Any suggestions?
[Captivate Android Development] buttstache:
Weird then that it bootlooped until I put the cm zip file on the external. It worked first try then. Luckily it doesn't do it in Android, only in CWM.

I've come into a new problem now though. Everytime I reboot my apps and settings get wiped, and the phone thinks it's the first time again. Every time. My ADW launcher settings stay, but no apps or google info does. Plus TiBu is apparently only letting me restore half my apps. The rest just fail.
[Captivate Android Development] ballz0iron:
are you undervolted? you may be undervolted in such a manner that it FC's the camera, ive had it happen myself took a few minutes to figure out the root of the problem but upping my UV settings seemed to do the trick
[Captivate Android Development] halfsoul:
check datadata
[Captivate Android Development] Nick0703:
Try changing the Local to something else. I too was having the same problem, I changed my local from English (United States) to English (Canada) and everything is working no more Market FC's.
[Captivate Android Development] kschumake83:
I have a verry odd problem. I have been running nightly 123 since the morning it came out, and all of a sudden out of no where i lost signal. So i checked in about phone and it said baseband unknown. Then i went into cwr and flashed a known working radio i had on my phone, same problem, tried again with another known working modem, no dice. Now i factory reset and cleared all caches and fixed permissions still a no go. Anyone have any ideas?
[Captivate Android Development] XsceneXhippieX:
Sounds like you tried to toggle 2g/3g its known to have said effects and thus it can't be used at all to knowledge, search the thread and you will find many that went through the same
[Captivate Android Development] kschumake83:
No it wasn't that I was in the middle of reading the news but I figured it out. Here I lost all of my eds stuff so I had to reflash a nightly. Don't know why it happened but its all fixed now. Thanks for the reply though.
[Captivate Android Development] littlewierdo:
Ok, having two particularly interesting problems, the first is easier than the second.

1. How do I get the gps to stay on when the screen on my phone turns off? I want to use Glympse this weekend for a trip I am making but the instant the screen turns off, the gps disables and glympse stops reporting my position.

2. A bit more complicated, the phone quality (sound specifically) is AWFUL on Cyanogen. (after receiving MANY complaints from people I was calling) I tried flashing several different modems (kg3 was one of the ones I tried) and even tried two different kernels (Glitch was one of them) and the audio quality was about the same. Audio was extremely quiet for the person receiving the call (so MY VOICE was extremely quiet - as in barely able to hear anything from me and very poppy and 'static-y'). I should also mention, I tried calling land lines and several different cell phones on different carriers (one on Verizon and another on T-mobile) with no luck (just an fyi, Im on ATT) AFTER EACH MODEM / KERNEL install.

So, beginning to think I might have a problem with my hardware, I flashed back to stock Eclair 2.1 (the ORIGINAL OS WITHOUT the 2.1 update that was released) and the call quality was fantastic on stock.

So, I dont know what to do. My phone needs to function primarily (shocker I know) as a phone first and foremost. Probably a dumb question (and wishful thinking), would the default modem that comes stock with the phone work with CM and if so, any idea of where I can get it (maybe someone has re-written it to make it compatible - again, wishful thinking).

Otherwise, I need some suggestions, otherwise I will have to switch to another rom.

Later today, I will try reflashing CM and maybe this will all work magically again, but I dont have high hopes (besides, it is too early in the morning atm to do any testing with the phone - no one is awake).

If it works, I will post an update - otherwise, suggestions would be great.
[Captivate Android Development] Thesandlord:
A hack to get GPS to stay on even if the screen is turned off is to start Google navigation and let it navigate to some random place.

The reason that call quality is worse is that our phones have built in hardware processing to make quality the best. Problem is all the other ones don't have this hardware and thus do processing in software. Because of this, there are currently no drivers for the chip, so the modems that expect this hardware part to be there don't work too well. The Galaxy S modems should work better though, because they do it in software. But bottom line is if you need phone first then CM7 is not the best choice.
[Captivate Android Development] simple man:
The new volume script that comes with glitch will help on your end. As far as radios go, here in Missouri BVJJW2 works best for me. One of the best for call sound quality even for people in the N.E. states is BUJS1 it's a froyo modem but works great on G.B., the only problem with BUJS1 is that it is not 850mhz by default, so if you want 850mhz to work you will need to go to an area that only has 850 to flash it. I hope you get it fixed and can stay on CM7. :-)

Sent from my SGH-I897
[Captivate Android Development] sixstringsg:
Said script only works if you're using the newest Glitch kernel. It won't work with anyone else's unless they pull in the changes.
[Captivate Android Development] CalvinL:
So I have the latest Nightly, but my phone is still draining battery a TON. I don't have too many things pushing, and it drains a few % just in standby. It was 60-something % about two hours ago. It's at 16% now.

It wasn't like this at first, but it's becoming a real problem. My 3G connections have also been pretty bad.

I just checked my battery usage, and it said 29% Google docs even though I haven't even opened it or used it... Uninstalled it for safe measure.

Kernel version:

2.6.35 12-g52fdd0a

atinm@wolverine#1

Mod:

CyanogenMod-7-9242011-NIGHTLY-Captivate

Also, using Advanced Task Killer, why does it keep saying I have 10 programs opened every few seconds when I don't? Due they pop up from pushing data?
[Captivate Android Development] sixstringsg:
And now comes the string of don't use task killer responses.....
[Captivate Android Development] WillyWonka23:
Has anyone tried Juice Defender? Does this application actually save battery on cm7?
[Captivate Android Development] CalvinL:
Where are the string of responses that will help me solve the battery drain issue?

Always assumed Juice Defender wouldn't work well, so never tried it.
[Captivate Android Development] nkrick:
Based on your description, it sounds like ATK is draining your battery. Remove ATK and see how your battery does. When your battery life is significantly better and you want to know why, use google search to find out why Android task killers are very bad for battery life and essentially "break" built in Andriod memory management.
[Captivate Android Development] sixstringsg:
Task killers are detrimental to your battery. Android has one built in, so another one is bad for your battery.
[Captivate Android Development] XsceneXhippieX:
i personally use and love juice defender. If and only if you take the 5-10 minutes to get setup correctly then it can and will double your battery life. But if you don't set up correctly you won't notice anything
[Captivate Android Development] littlewierdo:
Use Autostarts instead of Advanced Task Killer for controlling apps from starting.

And, task killers are 'ok' for one purpose - killing an app that has gone out of control. For example, I remember installing an app that began downloading data from 3g when I was out (and nowhere near any wifi networks). I needed to kill the app quickly so I used a task killer to kill the app. OR, if an app has seriously slowed down your phone, you can use a task killer.

But what you dont want to do is use a task killer on a regular basis for killing apps and you dont want to use a task killer for 'autokilling' apps. In short, many apps have conditions that an app can automatically start itself under (3g on/off, wifi on/off, location change, screen on/off, etc). So, when you autokill an app, that app will likely be restarted shortly after it was killed because of a condition that allows that app to start, the task killer will see the app started and kill it again, the app will restart because of a condition, and round and round we go with app starting, app killed over and over again. This uses a serious amount of processor power to continue to start and stop the app.

Enter Autostarts. Autostarts lets you prevent the app from ever starting in the first place by disabling the conditions that an app can automatically start itself under.

Oh, one more thing, thanks for the tips regarding call quality, got it resolved, more details (maybe, if anyone is interested) to come. Its a problem with permissions and CM in short.

And, regarding gps and the screen being off, Id like to see an option added to CM that allows the gps continue to remain active when the screen is off. The gps not being active sort of defeats the purpose of using Latitude or Glympse (or other location sharing apps)...
[Captivate Android Development] xTRUEx:
im on nightly 129, and was wondering if anyone else was capable of switching their keyboards. Ive installed swype through the swype beta installer. i enabled it in the keyboard section, but there is no place to switch it. ive done it many time before so im not sure whats going on.
[Captivate Android Development] halfsoul:
Open the swype installer again and it will ask you if you want to change keyboards. I bet there's another way, but this is how I did it.
[Captivate Android Development] Smasher816:
How to change your keyboard fast and easy:

Hold down on any text box

Choose "Input Method"

Choose desired keyboard
[Captivate Android Development] xTRUEx:
tytyty love u
[Captivate Android Development] Smasher816:
lol.

No problem man.
[Captivate Android Development] pandakh:
I posted this a few days ago but no one answered. Is there a way for me to check what is my current nightly build?
[Captivate Android Development] sixstringsg:
Settings > about phone, it's under mod version. Or at least I think, I always build my own so it says KANG instead of a date.
[Captivate Android Development] pandakh:
Mmm i figured but mine doesnt say, it says GRJ90...i seriously dont know what that is, im still a bit new to cyanogen. But ill manage it isnt really important. And ive noticed every time i update the build nothing in the about phone section changes, why is that? sorry to bother.
[Captivate Android Development] sixstringsg:
That's build number. We're looking at Mod Version. I'll update to a new version and check for you.
[Captivate Android Development] pwnerman:
Go to Settings>About Phone>Mod Version..... it should have a date in there...take that date and go to where you download the builds and match it up with the date and there you go...your build number

Sent from Captivate