yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] colt45x:
So I downloaded the latest nightly. All the previous ones have been working great... I did something wrong when flashing though. So I was on the 8/25 nightly, went into recovery, flashed the new nightly of 8/26, and it did reboot the recovery once half way through to update the recovery version I'm guessing? So after it rebooted back into recovery, I just flashed the nightly again. Then I flashed gapps, then the devil kernel, then rebooted, now when I boot the only screen I get is the CWM symbol in the middle with "devil recovery v6.0.1.0" at the bottom. Is there a specific order to follow when flashing kernels, I know I've been able to flash a rom, then kernel, and reboot sucessfully before.

Also, any ideas how to get out of this situation? Looks like I might have to odin back maybe?
[Captivate Android Development] djxs:
It shouldn't of rebooted half way through, something must of went wrong. I always flash the new nightlies in recovery without clearing anything and I haven't had a problem. Plus you only need to flash gapps once, everything will update automatically on first boot.

I haven't used the Devil kernel with CM10 yet so I can't speak for it's functionality, but there is no order to follow when flashing kernels, unless you flash a kernel then a ROM with it's own kernel, obviously it'll get overwritten.

Hopefully you had a backup in recovery. That'd be the easiest way to get back up and running.

On another note, while Bluetooth works perfect with my car, music/calls/phonebook/etc., I always seem to get a "Phonebook download incomplete" message from my car even though everything is fine. (my phone contacts were actually downloaded) I never had a problem like that with CM7.2. I still prefer CM10 though, so I guess I can live with that annoying message for now because it connects soo fast! :)
[Captivate Android Development] shane87:
You're problem is, there was no 08/26 nightly for cm10. The 08/26 nightly is cm9. Then you flashed the cm10 devil kernel on top of cm9. You will probably have to download the latest cm10 nightly (0827), wipe data/factory reset from cwm, then flash the 0827 nightly, then flash gapps, then flash devil.
[Captivate Android Development] andrewdroid:
Too many imeis are being hosed. Everyone make sure you've got a backup of your EFS folder and always flash without your sim card.

Put the sim card back after you've checked that your imei is ok.
[Captivate Android Development] XeoNoX:
flashed the cm-10-20120827-NIGHTLY-captivatemtd.zip and the 20120726 of gapps and i noticed that my CAMERA app works but when it takes pictures and u go to the gallery to check it the pictures are not really taken, its just a BLACK dark picture file and if u try to go on the computer and open it, the PC will say "corrupt or non valid file"
[Captivate Android Development] colt45x:
You're right, I can't believe I did that I'm usually really careful about those things lol. O well, at least I can get into download mode easily, because when I boot the phone the recovery literally has no options whatsoever.
[Captivate Android Development] ThreeofNine:
Had to go back to CM9 Stable. Just too many issues with CM10 on my Captivate:

1, Camera would close when I tried to go back to the camera to take another picture after looking at picture in the Gallery that I just took.

2. Touching anywhere on the side of the Home or Back button that is near the center invisible button opens the Google search/Google Now screen, or it tries to. After a minute or two of a white screen it eith auto- reboots or an error message pops to ask if you want to wait or close the Google search process

3. Using the Phone app to find a contact to call lags for a very, very long time. screen advances lag, then when the contact phone number is selected there's a log delay before the phone call is started.

4. When the phone is awakened, the notification drawer stays blank for 20-40 secs before it's populated with message, or missed call notifications.

5. There was a long delay when going from one app to another or switching homescreens

6. The wallpaper would return to the default jb wallpaper after every reboot.

I even tried the Semaphone kernel and it was even worse.

JB is looks great from what little I could use, but my phone doesn't like it I only have a few more weeks to wait before I get the GS3 and then a month or 2 before the AT&T JB version arrives. Then maybe I'll turn my Captivate into a "Samsung Galaxy Player"..........
[Captivate Android Development] mrsubway:
Stuck on Gingerbread

I wonder if someone here can help. I was originally on Slim Bean, but had a problem. Needless to say, I Odin one clicked back to a Gingerbread Rom. It seems I can no longer get past Gingerbread. I followed the instructions here to try and install CM10. I even formatted system. No matter what, the phone installs CM10, but then just boots into recovery. I've tried installing Slim ICS, Slim Bean, etc, and always have to Odin back to GB. Are there any Odins out there that are ICS or JB? Please help.

Samsung Captivate
[Captivate Android Development] swayjd:
So my lock screen is uncentered, to the right. Anyone else?
[Captivate Android Development] RootTheMachine:
Do the flash from stock again, and make sure you flash twice.

Sent from a jelly bean
[Captivate Android Development] mrsubway:
Done. No luck. :'( This is driving me crazy. Stuck on GB.
[Captivate Android Development] RootTheMachine:
Ditto, same here. I'll probably report it.
[Captivate Android Development] colt45x:
I think your skipping the step of flashing a kernel with clockworkmod injected.

I had to Odin today as well but after I got back to stock I flashes a kernel with cwm through Odin first then everything went fine. Does it take about a minute then say install from SD card complete?

If I remember right the default GB recovery won't let you install unsigned zips such as a ROM.

Also when you flash the ROM it will reboot quick after it installs the recovery packaged with the ROM then you have to flash again.
[Captivate Android Development] djxs:
If it flashes the first time then ends up constantly booting recovery, pull the battery, enter recovery again and reflash.

Any CM10 nightly ROM you download has the kernel already inside.
[Captivate Android Development] Primus76:
Thirded. Came in here to see if someone already mentioned it first. I'll let you run with it.

Thx
[Captivate Android Development] colt45x:
I'm talking about after using Odin to get back to stock gb
[Captivate Android Development] RockRatt:
The center unlock button is across all devices (or a few at least) it is known and I believe it is already fixed for the next nightly from what I read.

Sent from My SGH-I777 Running Red Reaper Rom
[Captivate Android Development] Monfro:
Here the fix:
[Captivate Android Development] jpcdeux:
That fixed lock screen but not notification pull down
[Captivate Android Development] Monfro:
Build from 28.08.2012 has the lockscreen graphical glitch fixed.

Sent from my Captivate
[Captivate Android Development] sleither:
Thanks a ton, borets.boris! That fixed up my IMEI. Oddly enough despite having a borked IMEI for a few days I thankfully wasn't booted from my network (Rogers).
[Captivate Android Development] Keland44:
build 0828 seems pretty good so far just running into issue with having no data connection when having full bars think it's more so my locate rather then the rom

but to throw it out there anybody not getting data connection even with full bars?
[Captivate Android Development] swayjd:
Honestly, at this point, I feel this is just as stable as cm9. It's a bit slower at times but that's it.
[Captivate Android Development] jpcdeux:
Go into settings and enable data. Happened to me and realized data was off.

---------- Post added at 04:58 PM ---------- Previous post was at 04:39 PM ----------

Reboot when mounting USB to comp. Anyone else?
[Captivate Android Development] mrsubway:
I still have no luck. I flashed stock GB, by stock I mean I9000 GB with a reoriented kernal. Been using this as a base from day one. The GB recovery says that the CM10 file is invalid. Flash Devil JB kernal. Wipe cache/factory reset. Flash CM10. Phone reboots into the new recovery. Flash again. Phone just keeps booting into recovery. Is there a way a phone could be damaged and not take newer ROMS? I have literally tried half a dozen ROMs with not luck. I cannot get past Gingerbread. Another weird fact. I used the file manager in recovery, and there are two files that say symlink error, and the system folder is empty!
[Captivate Android Development] cnu4u:
Anyone have issues with exchange? Exchange works well on Wi-Fi but not on 3g... Anyone any idea?
[Captivate Android Development] Keland44:
build 828 is pretty solid fast i do have to say compared to build 818, build 828 is a battery monster on battery number 2 after about 5 hours of medium usage how is battery been for everyone else?
[Captivate Android Development] whiteguypl:
Usage is entirely to subjective to lable low medium and high. Could stream music all day long with the screen off but streaming music with the screen on will kill it in 3-4 hours.
[Captivate Android Development] spotdog14:
Is anyone else not able to sync their Picasa web albums to the phone now?
[Captivate Android Development] Keland44:
agreed running groupme and syncing 3 gmail accounts

Screen on time 2 hours 13 minutes

on battery time 3 hours 16 minutes
[Captivate Android Development] whiteguypl:
yeah thats no good
[Captivate Android Development] colt45x:
I think I know what your doing wrong. If your on GB, and you flash the jelly bean kernel, the phone won't boot. You are trying to flash a JELLY BEAN kernel over a GB rom. I did the same thing with flashing a JB kernel over an ICS rom and it did the same thing, won't get past recovery. Try flashing a GB kernel with CWM injected. Then wipe data/factory reset and flash the CM10 rom THEN the kernel.

You are flashing the cm10 from the recovery though, so during the flash it would technically overwrite the GB rom and install the cm10 kernel along with the ROM. But I don't know give it a try. There are also a ton of good threads about how to flash any rom from stock, try giving them a read as well.
[Captivate Android Development] richsale:
I'm om 8-27 and not having any problems with Picasa. Syncs just fine to my phone.
[Captivate Android Development] thuanngotau:
Project Butter works?

My phone seems to stick with some "lags" as seen in CM9!
[Captivate Android Development] holeindalip:
Same thing happened to me coming from hellybean solution: use Odin and flash your i-9000 base as you said but use a 512.pit file and repartition it all and continue as you normally would by flashing cwm yada yada yada... should be good to go after that.
[Captivate Android Development] whiteguypl:
Anyone know of a quick fix for the stock browser force close when moving the cursor in a Google site search box? I find it... bothersome.
[Captivate Android Development] Primus76:
Haven't found one myself but just grabbed dolphin instead of trying to work around it.
[Captivate Android Development] W. Holybee:
I flash back stock. Then flash ICS. Then flash CM10. Most the time I flash 2x.
[Captivate Android Development] swayjd:
holy crap 3108 battery drain is through the roof. 30% in 3 hours. 51% of which is Android OS. Screen 9%.
[Captivate Android Development] whiteguypl:
hmm

My battery is fine
[Captivate Android Development] pqee:
I've seen Android OS suck up a boatload of battery on multiple nightlies, but I've also had great battery life on the same ones. It's random when it happens and a reboot usually fixes it so I'm blaming something I have installed and not the whole CM10 install.
[Captivate Android Development] thuanngotau:
After some "clear" actions I can fix it myself.
[Captivate Android Development] gluvox:
Does anyone know where my phone app might be? It's listed in titanium backup (I tried using that to bring it back), and it's listed under settings > apps, but it won't come up under apps or the phone short cuts.
[Captivate Android Development] vileladelima:
Hi, guys, good night!

My cappy is on 0830 and since I've installed CM10, my phone only has 422mb for applications, every one has this size?

Another thing, sometimes my lungs goes crazy! It becomes very slow, and sometimes it reboot by itself!

What's going!
[Captivate Android Development] speedy_11:
CM9 only had 170MB for datadata (apps) on the OneNAND. The 1.5GB you see in settings was on the MoviNAND and was't used to store apps. Pawitp moved the system over to the MoviNAND and gave most of the OneNAND space (422MB) to apps.

If you have a lot of games move them to the SD to save space
[Captivate Android Development] sinizter:
Can't wait for this to be implemented!
[Captivate Android Development] swayjd:
It's already merged, look in messaging settings.
[Captivate Android Development] sinizter:
Oh didn't notice that. Thanks!
[Captivate Android Development] cvcduty:
Well, I just spent the last three hours or so trying to use this rom... I came from TeamNyx ICS rom (RC5) and I liked what I was seeing... until I tried to actually start using the phone... I could not get it to do anything... freezing everywhere... real buggy. I guess I will load CM9.1 Stable until this becomes a bit more mature.

I jumped from TeamNyx due to the datadata low space warnings. I have learned to live with it but I figure I will try a rom without datadata... for now, I will go back and try later.

:crying:
[Captivate Android Development] RootTheMachine:
It's a great feature, I no longer need a 3rd party pop up app. Still needs some cleanup though.
[Captivate Android Development] cmilldrummin:
Been using this as a daily driver for over a month with almost no issues....try a clean reflash

Sent from a devilish jelly bean
[Captivate Android Development] azunino:
Idea: More space in /data

I've been following CM10 development and despite I think the new partition scheme is a very good solution, I've seen people complaining about the low space in /data. Some time ago I modded CM9 to store /data on the external SD card (see the link in my signature), and I've been using it with no problems. I might be able to modify CM10 to store /data on the external SD so that the size of /data is only limited by the size of the external SD.

Are you interested in such a hack?
[Captivate Android Development] whiteguypl:
The purpose of the change was so such a hack would not be needed. Afaik. And the people complaining about putting apps on SD are silly. Imo.
[Captivate Android Development] azunino:
AFAIK the purpose of the new partition scheme was to avoid the slow access to /data that some people reported. Anyway, the fact is that there is less space and the solution is moving apps to the SD card... a hack. So... the options are the CM10 built-in hack (app2sd) or... another hack. Nice :laugh:
[Captivate Android Development] RootTheMachine:
Does anybody else wish that the lockscreen could have a timer? i.e. the pattern lockscreen will only come up after an hour of screen off, while the slide lock will still be on during that. IIRC that was in CM7 but it didn't work right.
[Captivate Android Development] Monfro:
Abou low storage data, other than moving apps to SD, i suggest also:

1. Add to your gapps zip some programs that will work also as system apps, saving space on data partition: flash player, YouTube, gmail, google music, maps & streetview, nova, apex...

2. Formatting SD with cwm (make a backup of your SD first!! ).

Then use link2sd to move apps to the new ext3 partition.
[Captivate Android Development] cjd430:
This is a very particular bug, but I thought I would share anyway.

I use Swiftkey 3 as my keyboard and when you set it up it will bring up the 'Language & Input' part of 'Settings' so you can mark Swiftkey as your default input method. Well ever since I moved from 9/1 to 9/4 (and also just tried 9/6 and Helly Bean based on 9/4), 'Settings' goes full ANR when Swiftkey tries to open 'Settings.' I have found a workaround to manually setup the keyboard and get the installer to recognize the manual method, but I just thought it was interesting that it used to work and now I get some ANR's with this nightly.

Also, thank you pawtip for keeping the captivate alive.
[Captivate Android Development] mik101:
Has anyone had any problems receiving calls on the Sept 6 build? I came from the Aug30th one. I am using semaphore kernel but it hasn't given me trouble like this before. I'll have to take a look through the commits in a minute and flash todays nightly to see if anything changed. (Or maybe a bad flash?)

Thanks guys.
[Captivate Android Development] colt45x:
I'm at 1d 10h 37m on battery with 10% left.
[Captivate Android Development] azunino:
CyanogenMod 10 - M1 available for testing:

http://www.cyanogenmod.com/blog/cyanogenmod-10-m1

Thanks pawitp and all the CM10 developers and contributors!
[Captivate Android Development] dongfangri:
In both Nightly 0911 and M1, the file Term.apk is broken.The file size is too small.

By the way, terminal V1.0.45 is out.
[Captivate Android Development] rickneworleansla:
"We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward."

So does this mean that cm-10-20120911-EXPERIMENTAL-captivatemtd-M1.zip is essentially a nightly build from the beginning of the month or is this something different? If I am on September 9th would this be going backwards? Can someone clarify?

Thanks
[Captivate Android Development] cvcduty:
I am finishing setting up the M1 build. It seems that the build date is from Sept. 10... So for you, it would be a slight forward step...:D

First thing I noticed is that the Gallery App would not do anything. It will show my pictures on board but options would lead to a blank page. I had to strip a GoogleGallery.apk from ICS Gapps and that one seems to be working fine.

Question though. in /system/apps I see 2 gallery apks. Gallery2.apk & Galaxy4.apk. I noticed that the Gallery2.apk was little over 3MB where as the Galaxy4.apk was only 344KB... I renamed the Gallery2.apk and placed the GoogleGallery.apk from ICS and so far seems to work find. Why the two Gallery apks?

Now, with the ICS Gallery apk... I have 2 Picasa sync settings. One called Google Photo and the other Google-Photo... hmm...
[Captivate Android Development] ninja_rancher:
I don't see any place in the Google Search settings to download offline languages for voice search like I do on my Atrix CM10. Am I missing something, or is this perhaps not in the Captivate CM10 (yet)?
[Captivate Android Development] comdei:
How are you guys overclocking?

I can't find support for CM10
[Captivate Android Development] ninja_rancher:
You need a different kernel. Devil and Semaphore are two that I know of that support CM10 and overclocking.
[Captivate Android Development] azunino:
I'd love that! I remember using the delay options in CM7.1 some time ago.

BTW, CM10 seems as stable as CM9 so far. One difference I've noticed is that CM10 uses less battery while the phone is idle (using the same applications). 1% during the night versus %5 for CM9 (both using stock kernel).
[Captivate Android Development] singlebeam:
I would say that they built one initially as an example with following experimental builds coming at the beginning of each month.
[Captivate Android Development] typ44q:
could you share what you did to get it working? I am having the same problem when it tries to load settings and I am really missing swiftkey!
[Captivate Android Development] bsaelim:
not sure if the setcpu app would work also.
[Captivate Android Development] wilson735:
I've been running CM10-20120905-NIGHTLY-captivatemtd and I sometimes get the sleep/charge death.

Scenarios:

1) After leaving it to charge at night, in the morning I'll hit the power button to wake up the phone, and the screen will not turn on.

2) Unplugged, I'll be listening to Pandora, the screen timeouts to sleep, and then when I go to wake it up, the screen won't turn on. The music will still be playing like normal, but I can't turn on the screen.

3) The other day, it was just sitting on the table, and the screen wouldn't turn on. I wonder if incoming calls work, so I place a call to the phone, and the screen stutters on, at the lowest brightness setting, and I'm able to answer the phone. The brightness won't come back to normal after the call, though, and it won't receive any input.

In all 3 cases, I reset it by holding the VOLUP + PWR for a few seconds.

Any suggestions?

I'm going to flash M1 now to see if it helps.

Also, the phone lists this kernel version:

3.0.31-ge839092

blinky-ghost@cyanogenmod1

Tue Sep 4 22:26:11 PDT 2012

And this Baseband version:

I9000UGKG3
[Captivate Android Development] cjd430:
Swiftkey3

Step 1: Download Language (Do this as you normally would)

Step 2: Enable Swiftkey3 (Back key out of the setup and go manually enable it in 'Language & Input')

**Step2A: Re-open Swiftkey3 setup

Step 3: Set as default keyboard (Do this as you normally would)

Step 4: Integration (Do this as you normally would)
[Captivate Android Development] typ44q:
Thanks, worked perfect!
[Captivate Android Development] bsaelim:
I'm running 9-11 nightly and noticed something similar. if the screen went off while I was running Kindle, phone would not turn on or if it turned on the lock screen would be very dim and sluggish. this will last for a minute or so until a dialog showed up asking whether I want to stop Kindle or just wait.

similar experience with Pocket and Facebook.
[Captivate Android Development] kevinseto:
I've had the same occurrence in the M1 build.
[Captivate Android Development] RootTheMachine:
I have had this exact issue since ICS, and it's also present while running devil kernel. It seems to happen when I'm running out of ram.
[Captivate Android Development] Monfro:
Seems that all the commits merged in the last 24h made 13.09.2012 nightly smoother than previous versions

Sent from my Captivate
[Captivate Android Development] mik101:
How are you guys finding the OneNand implementation? I've been sticking on the last build before that (9th I think?) until I hear some more feedback. I don't want to go through a forced wipe if I'm not going to get much out of it. My phone is *perfect* on that build. I haven't had a single fc, sleep of death, slow to wake (when the screen gets stuck half on) or anything of the sort.

I suppose if it "ain't broke, don't fix it". :laugh:
[Captivate Android Development] vileladelima:
Ring Tone!

Hi, Good Morning for you all! ( Here in Brasil is 10:47 am, and yes! the real Brasil is written with 's' instead of 'z')

One question: when enter the phone opitions to chose a ringtone, appears only the standard tones. To select one music as tone i need to open Apollo, and select the music as ringtone. And the same occurs to define a tone to any contact, only appears the standard tones.

There is a trick or any app to select musics as ringtones, in / configuration / sound ?

Thanks!
[Captivate Android Development] swayjd:
It just hasn't been looked at yet. Stability before utility I guess.
[Captivate Android Development] vileladelima:
But with the CM9 is happens the same thing!
[Captivate Android Development] bsaelim:
The nightly is quite smooth on mine as well.

Although Kindle is still a bit laggy, could be memory issue.
[Captivate Android Development] n311.dunkle:
Does anybody have any insight as to why this happens when I try to wipe my dalvik cache? It says its wiped but when I check my dalvik folder it is full of crap. It also takes a long time for this process in my recovery.

Could this be why my phone is so laggy and does anyone think this thread will help? http://xdaforums.com/showthread.php?t=1716124
[Captivate Android Development] Legacystar:
could anyone tell me if the AUTO BRIGHTNESS has been fixed. i'm running CM9 on my brothers captivate because CM10 auto brightness didn't work
[Captivate Android Development] whiteguypl:
If auto bright is working its not doing much of anything. I have to change manually throughout the day.
[Captivate Android Development] azunino:
works fine here using m1 (clean install)