yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Jolufa:
Anyone can make one package flashable with ODIN?

My Cappy is in semi brick mode and can flash only using ODIN and I find only stock ROMs.

Thank you
[Captivate Android Development] laughingT:
have you checked the profiles section of settings? I think it has overrides that could do what you describe.

Sent from my SGH-I897
[Captivate Android Development] mik101:
This is why you're supposed to do nandroid backups. Restore to stock with Odin. Flash cwm package with Odin and then restore your backup. Then you'd be up and running again.

Unfortunately this time around you'll probably be starting over. There is no need of Odin tarballs for aftermarket ROMs if you do what I said above in the future. Good luck.
[Captivate Android Development] Primus76:
For fun I've gone back to the 10-26 nightly with the 3.0.31 kernel to see if my BT disconnects all the time with phone and media connected.

On the first short test from home to daycare with the latest and both options selected it disconnected from Ford sync in under 2 minutes. Did this to make sure it still did it with phone and media selected.

I then flashed Oct 26, and confirmed it was still both selected and it stayed connected the whole way home.

Will keep it over the next couple of days to see how it behaves. If it continues to work properly then something changed in the kernel or rom between this version and the later November releases when I first started seeing it.

If this is the case what do I need to do to report it?

Thx

Edit - how would I go about backing up and restoring the kernel only if I want to test the old kernel with the latest nightly to rule one out? Sgs kernel flasher doesn't work for this rom.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] Katze Pavilion:
I don't use profile, I turned it off in setting.
[Captivate Android Development] ReaperManHK:
That's weird, that happened to me today, except on my Sensation. Must be a CM issue.
[Captivate Android Development] tmroy:
I have, on occasion used heimdall to reflash just the kernel.

I have, on occasion, extracted the kernel from a cm*.zip package (Its called boot.img) and used heimdall to

reflash it and booted into recovery.

You can also just flash a zImage from a semaphore kernel. Once you're in recovery, you're good to go.

I wouldn't actually use the flashed kernel for anything except installing a real *zip file though.

---------- Post added at 04:55 PM ---------- Previous post was at 04:52 PM ----------

I had a recent cm-10 nightly rom detach itself from ford sync .... The only problem is is that its my wife's flex, and I don't drive nor

ride in it every day.
[Captivate Android Development] Primus76:
I think I have to go back in time more. My 10 26 test started disconnecting too. Again if you disable the media portion it works fine. It is when cm10 goes to connect to the media after connection the phone portion that the phone disconnects.

Willing to run whatever is needed to identify the problem but need guidance from dev.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] pawitp:
PSA: Starting tonight, nightlies for Galaxy S, Galaxy S B and Captivate will be switched from CM10 to CM10.1.
[Captivate Android Development] Primus76:
Amazing as always pawitp!

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] agpsalazar:
hey friends why the option "wipe battery stats" disappeared of recovery? :(
[Captivate Android Development] Gromlakh:
I don't know "officially", but if I had to guess it's probably because "wipe battery stats" doesn't really do what everyone thought it did and is really kinda pointless.
[Captivate Android Development] jamina1:
Wrong thread sorry
[Captivate Android Development] TD4:
For some reason i'm getting SU force closing everytime it ask for root access, data, cache and dalvik wipe before i flashed it

Anybody else having this problem?
[Captivate Android Development] thangphysk48:
Try to flash newest SU

http://androidsu.com/superuser/
[Captivate Android Development] Primus76:
Woohoo 421! Downloading gapps fro goo since none seem to respond. And it says there is no account. The settings button top left when notification bar is pulled is slightly off screen.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] truckmann:
For those that haven't found it there is a new thread for CM10.1

http://xdaforums.com/showthread.php?t=2046952
[Captivate Android Development] vuvantuan59:
thanks so much rom verry good !
[Captivate Android Development] pqee:
Did you remove the gallery at all? The stock gallery is both gallery and camera apps.

Sent from my Jellied SGH-i896.
[Captivate Android Development] swayjd:
thsi also happens to me, though only at the first try, if I just swipe left again it works. Also happening on calls sometimes. It doesnt pick up the call at first.
[Captivate Android Development] djxs:
I didn't remove anything. I flashed gapps after the first boot and that's about it.
[Captivate Android Development] wwcjr91:
I noticed this with all JB ROMs.
[Captivate Android Development] shane87:
I did notice that my wifi drops signal a lot faster than on ics. On ics I could pick up my wifi router almost 300 feet from my house. On jb, it was so much weaker that sitting about 50 feet from my back door, wifi was coming and going.

As far as the camera app, I reinstalled go launcher ex through tibu, and restored the data for it, so I can keep the same screen layout. My camera shortcut showed a broken link, and clicking on it gave me the message that the app could not be found, please try restarting go launcher. After deleting the link and re-adding it, the camera launches fine, though I haven't tested it from the lockscreen, since I have a pattern lock.
[Captivate Android Development] Spritely:
My phone was nightmare-ishly slow on HellyBean (various versions, my phone just didn't like it) so I was pretty excited when I saw this here. CM10 has been doing well for me so far. Restoring things has been somewhat of a pain thanks to the rom partition and internal storage being swapped (and therefore the internal storage gets full just by sneezing at it) but otherwise it seems to be solid and quick.

---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------

The link saved on your backup is just a different version of the camera app which can change things. I see it a lot on my launcher back ups. Same for the gallery. Replacing the shortcut will always fix it.
[Captivate Android Development] whiteguypl:
Anyone try any different modems?
[Captivate Android Development] shane87:
I'm running the same modem I had on cm9, the tljl3 modem. I have used this modem since I was on gb, as it provides the best all around performance for me. You should have the last modem you installed, since cm installers always check to see if a modem is installed, and skip modem installation if one is found.
[Captivate Android Development] whiteguypl:
Hmm wonder how I got on jk4 then... must have been bored one day. Thanks for the tip. Jl3 is what I thought I was on.
[Captivate Android Development] bitnerd:
Yeah, my modem didn't change at all from the BVJJW2 I was using on CM9

---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
[Captivate Android Development] CheesyNutz:
Had some unusual lag spikes a when back no idea what caused them not happened anymore
[Captivate Android Development] zuN!:
Sightly off-topic from the purpose of this thread, but is there a way to have a widget for Google Now or is the search bar the only thing. Clicking the search bar brings up Google Now / Voice button the new voice search. It would be awesome if we could see cards on the homescreen. Does anyone know if that's possible?
[Captivate Android Development] djxs:
The only "lag" I've noticed was at first boot, more specifically, during the boot animation. (It would pause every three seconds)

Other than that, I haven't noticed anything since I flashed it yesterday.

I also tried reflashing but still no camera app, I do have Gallery though.
[Captivate Android Development] Lollipop_Lawlipop:
For those having weak wifi dropping issues, have you gone into advanced wifi settings and disabled "Avoid poor connections"?

If not, why haven't you?
[Captivate Android Development] djxs:
I'm getting three bars again upstairs, so it looks like that fixed it.

Thanks! :)
[Captivate Android Development] pqee:
I think I saw a fix being merged for the "lag" on the boot animation. Guess we'll find out next nightly.

Found it: http://r.cyanogenmod.com/#/c/21636/
[Captivate Android Development] Nick D:
I installed CM10 yesterday. Phone wouldn't wake this morning. I see no difference, it's still a problem. Back to CM7.
[Captivate Android Development] Gore785:
This isn't a bug on the ROM but I wanted to know if u could find a fix for the add a n dictionaries on the keyboard. I'm trying to add emoji
[Captivate Android Development] CheesyNutz:
ROFLMAO ... i have yet to see this sleep death ... i refuse to drop back to CM7 hell ICS :P
[Captivate Android Development] johnnyrichter:
Wouldn't wake = it froze in the screen off/idle state or it turned itself off but you could turn it back on? The latter is what I refer to as sleep-death. I'll assume your reason for skipping over cm9 was due to the same issue.

Were you using the baked-in kernels or a certain other kernel?

Did you do a process of elimination to see if an app was causing it?

Have you tried increasing your idle clock from 100MHz to 200MHz?

Have you tried increasing that clock AND increasing the voltage for 200MHz from 950mv to 975mv or even 1000mv?

Sleep-deaths, if that's what you're suffering from, have been commonly caused by too low of an idle clock or too low of an idle voltage. Increasing my idle clock to 200MHz and the voltage for that clock from 950 to 975/1000mv minimized my sleep-deaths down to maybe 1-2 a day which usually occur while I'm asleep.

I did not have this problem with stock GB-KK4 or Legend5 ICS. If it were the fault of CM9/CM10 then everyone would be seeing the problem. I ruled out apps and kernels causing the problem which leads me to believe it may be the hardware. Perhaps certain cappies cause it, or certain revisions of a certain part(s) in the phone cause it. Hopefully this is something that can eventually be figured out and resolved via software if possible.

Just some friendly advice...constantly replying to people to let them know you don't have the same problem isn't really on-topic or helpful(i.e. you've told us at least 20 times in both this and the cm9 threads that you don't have sleep-deaths when people were reporting theirs).
[Captivate Android Development] ThisWasATriumph:
As far as I can tell, theres a hardware defect that causes this. I have 2 remaining cappys and one sleep-deaths all the time on any rom post-gingerbread.
[Captivate Android Development] CheesyNutz:
ill continue thanks some people need to remove the stick. :eek:

the "sleep death " that people have imho is hardware related and nothing to do with the rom .

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

thats my guess is that its hardware related my wifes has the sleep death and is running the same rom same settings etc etc that i am and i have no problems.
[Captivate Android Development] johnnyrichter:
That's what I've been leaning towards lately. Wasn't there several cappy revisions?

Like I mentioned above I didn't have the issue on Legend5 ICS and I used that ROM for several days before trying out and sticking with CM9. I'll probably wait a few more nightlies before jumping on CM10. I just hope to see the CM devs look in to this sleep-death issue if they haven't already, since this is what they do and will probably have more luck figuring it out than we would.

Perhaps only CM9/10 expose the hardware issue like they do with the partitioning? No other ROM gave me "can not install to external/internalSD" errors, CM9/10 was the only one requiring that script fix. That was the fault of the phone and CM only exposed it from what I understand.

You constantly telling people that your phone doesn't have the same problem theirs does is not constructive at all and you've done it in at least three of the same threads I've posted in. It does not offer anything to the thread topic nor does it help the users with their problems. You're just adding random irrelevant discussion with those replies and these threads are hard enough to navigate for info as-is, especially when they shoot up several pages a day.

My reply was nothing more than friendly advice and I wasn't trying to be disrespectful so there's no need for the childish comments.
[Captivate Android Development] wwcjr91:
+1 Thanks Johnny
[Captivate Android Development] rabi347:
I installed cm10 and now I noticed that my IMEI has changed to generic and the phone stopped working (can not make calls or text). Anyone got a fix for this please?
[Captivate Android Development] low99:
If you're coming from CM9, there should be a "backup" folder on your SD card which contains necessary files to restore your phone. What's left is to look for a guide to help you restore it. This is one such guide - http://xdaforums.com/showthread.php?t=881162

### EDIT ### - Here is another one - http://xdaforums.com/showthread.php?p=9567974

Please don't follow blindly and at least understand what you're doing before attempting the guides above. They may be outdated.
[Captivate Android Development] whiteguypl:
Sleep death is a (admitted by Samsung and fixed) hardware defect in the first generation of captivates. Not all had it some worse than others. Their is a post here (search) that has all the information about it and even the model #s effected.
[Captivate Android Development] n311.dunkle:
Question about the OP: there's a note that nandroid back ups are not compatible with other versions so I need some clarity? Why include it in the instructions when flashing from cm9? How do I utilize the nandroid if things don't go well? And if they do?
[Captivate Android Development] JoshJ22:
That just means that cm9 and cm10 nandroid backups aren't compatible. To restore a cm 9 nandroid backup u need to first flash cm9 and then restore
[Captivate Android Development] swayjd:
My cpu is stuck at 1000. Doesn't seem to want to scale down on ondemand.

Edit: disregard. Reboot fixed it. Can't set minimum frequency to 100mhz though, the option is there but when you leave the processor options it reverts to 200.
[Captivate Android Development] pawitp:
The truth is that there's no CM maintainer for the Captivate right now and the current builds are just a byproduct of the CM for the international Galaxy S. So unless someone submit patches for this device, there won't be any device-specific improvements.
[Captivate Android Development] swayjd:
Will it stay that way? Or will someone be joining your ranks to take care of us?
[Captivate Android Development] pawitp:
That's not for me or any other CM developer to decide. It's up to whether some developer with a Captivate decides to step up and start submitting patches or not ;)
[Captivate Android Development] shane87:
If I can get a 64bit system setup, I will gladly start working on the cappy code!
[Captivate Android Development] swayjd:
Is there any way to know if such a person has started to submit those device specific patches?

Is the bbq site accountable?
[Captivate Android Development] pawitp:
It will appear on there once merged, but don't hold your breath for one.
[Captivate Android Development] fohdeesha:
And this is why Helly Bean and the devil kernel will live on forever. He has been creating i897 builds based on cm10 for months now, and they're amazing.
[Captivate Android Development] Ajfink:
Getting some power button death from this bad boy. Otherwise, running well.
[Captivate Android Development] swayjd:
Was it like this for cm9 as well? We seem to have a considerably large community, why do you figure no one comes forth? Developers moving on from such an old phone?
[Captivate Android Development] xCAVEMANx:
Ran all night

No sleep death...Had it off the charger for over 2.5 hours with gps, wifi, and sync all on. Heavy internet usage. Battery at 86%. Min freqency set to 200 mhz. Hiccup and freezes barely, but that is most likely due to ****ty FB app and not the OS. i987.

---------- Post added at 08:08 AM ---------- Previous post was at 07:52 AM ----------

Got a random reboot in the middle of a phone call. ugk3 modem. Boot screen says cyanogen (mod) 9 but when open everything is Jellybean. Is my install screwed up? Sorry if this sounds noobish.
[Captivate Android Development] pawitp:
In CM9, some people in teamhacksung still have their Captivate, but now no one has it. Either broken, or gave it to someone else to move on to other devices, etc. They have no obligation to stick with the Captivate just to develop it, if they want to move onto other devices, it's their choice ;)

Some people may be taking CM as a base and release their own ROMs, but it has no meaning unless they pick out their fix and submit it back to CM. Granted, our commit standard are somewhat high and we don't accept "might increase performance a little bit" or "might fix, but I have no idea" patches. But if someone develop a fix for, say, the sleep death, and submit it back to CM, it's the only way for this ROM to progress on device-specific bugs. Otherwise, it will just piggy back on the work I'm doing on the Galaxy S I9000 (International), which is fine, but will not lead to fixes for device-specific bugs such as the sleep death.

Which is more or less based off the source I've worked on. CM10 for Captivate has always been compilable, just no one compiled it and released it as "CM" until the build-bot did. It's easy to build a Captivate build based on the previous work done, and the CM buildbots are doing exactly that for the time being. I may be wrong, but I don't think he has a Captivate either and that would not lead to Captivate-specific bugs getting fixed.
[Captivate Android Development] cbalt:
You are correct he doesn't have a captivate either he has an i9000 iirc.
[Captivate Android Development] RootTheMachine:
Latest nightly wiped all system settings, which seemed quite abnormal.
[Captivate Android Development] djxs:
Hold down the search hardware key and you'll get the Google Voice prompt, if that's what you're looking for.

Sent from my SGH-I897 using Xparent ICS Blue Tapatalk 2
[Captivate Android Development] CheesyNutz:
Loaded up the new nightly build have not noticed anything out of the ordinary battery seems a bit better
[Captivate Android Development] singlebeam:
Boot animation performance was fixed so it doesn't freeze anymore. I think it looks better than it ever has.

Also my bluetooth file transfer is functional where it wasn't on the first nightly build... though not sure if that issue was unique to my initial flash or not.
[Captivate Android Development] dono89:
profile setting continue to not working.

if flag the setting "not sure" for unlock the device (the 2nd option) when unlock, it continue to ask the pin or password (if before set it for vpn or any certificate)

there's a solution?

in cm9 working great.

thanks pawit :good:
[Captivate Android Development] skyxliner:
Anyway to get more governor profiles such as smartv2? Feels sluggish...
[Captivate Android Development] daskanda:
Flash a non stock kernel such as semaphore or devil
[Captivate Android Development] fohdeesha:
no devil support yet, don't know about semaphore either
[Captivate Android Development] vileladelima:
Devil Kernel?

The CM10 work with a non stock kernel?

I could flash Devil, ou Semaphore, or other with no problems?

Thanks!
[Captivate Android Development] tkjeeper:
No, not yet
[Captivate Android Development] scythekain:
Anyone running the nightly CM10 from 0818 have the EFS problem that the Hellybean users had? I flashed CM10 on Saturday night (0818), and it ran fine till Monday morning when my device got blocked. I'm not sure, if my EFS folder got hosed somehow or what.
[Captivate Android Development] ThreeofNine:
Interesting...my wallpaper returns to the CM10/JB default every time I disconnect USB debugging mode after transferring files. (on 20120820 nightly)
[Captivate Android Development] Gore785:
Yeah me it happened after in flashed this ROM.
[Captivate Android Development] rabi347:
Same thing here. My efs is hosed.
[Captivate Android Development] melvinaury:
Me too. I have to call AT&T and now I'm back on service.
[Captivate Android Development] psyfactor:
It seems to happen randomly on my phone since ICS. All I had to do is flash to stock GB and the IMEI shows up again then flash back to CM10.
[Captivate Android Development] rickneworleansla:
I've been on 10-20120818-NIGHTLY-captivatemtd and so far everything has been fine. I've been reading about the problem many have been having with the efs folder getting wiped. It's also been listed in the bug tracking below. I'm holding off flashing any new nightlys until this gets addressed or resolved. Is it only Helly Bean CM10 having the issue? Who else is having problems? Which Nightly are you on? I was hoping to reflash today to see if the new CM10 boot animation has been added.

http://code.google.com/p/sgscm10/issues/list
[Captivate Android Development] CheesyNutz:
just flashed the newest nightly build still the ciD boot-animation
[Captivate Android Development] scythekain:
I'm on the same nightly you are on, I flashed it saturday night and my phone ran fine until Sunday night after I went to bed. When I woke up monday morning my device was blocked. Unfortunately I didn't check my IMEI before restoring from my backup, an unrelated bug *06# is not working... It was only afterwards, I found you can also find the IMEI in the about phone> status.
[Captivate Android Development] rickneworleansla:
I just checked and my IMEI on the back of the phone is the same as the one listed in my system setting>-about phone>status. It looks like I'm good. It strange that you had the issue and I didn't. I came from Helly Bean and did a clean wipe before flashing. When I flash the next nightly I will be sure to pull my SIM card first and check the IMEI listed in settings. At least that way I can try to restore the correct IMEI before getting booted from the network.

:good:
[Captivate Android Development] scythekain:
:good:

ME As well. Before I flash ANYTHING, Modem, Kernel, ROM, I'm pulling the SIM and verifying that my IMEI didn't get hosed. Right now, besides the unimportant *06# not working, the CM10 nightly seems pretty stable. (as most CM nightlies always are.)

I'm gonna honestly probably wait till they either add the new boot animation, or fix the IMEI bug.

:o
[Captivate Android Development] borets.boris:
Those with IMEI issues:

See if you have an efs folder in following directory:

/sdcard/backup

If you do, then try copying the folder over to your root directory, overwriting the contents in the root directory. I did that, and my IMEI matches now. :thumbup:
[Captivate Android Development] Gore785:
Yup
[Captivate Android Development] singlebeam:
The CM10 bootanimation hasn't been merged yet.
[Captivate Android Development] JonnehXD:
So what are all the symptoms of this IMEI issue so we know what to look for before getting booted off the network? I have an /efs folder containing an IMEI folder but the IMEI folder is empty. I also can't find an IMEI on the sticker under my battery to compare it to.

If there's a significant risk I could be booted from the network I'll go back to CM9 to play it safe. I can't seem to keep a JB rom running quickly anyway.
[Captivate Android Development] Gore785:
Just take out sim card flash your rom. After boot go to settings>about phone>phone status and check of imei is the same number as the number behind battery. If not follow one of the many restore imei methods. Once your done restore sim and your set :
[Captivate Android Development] JonnehXD:
I know that, I was asking what happens when things have gone wrong for other people. /efs gets wiped and they get booted from the network provider, I gathered that much, but are there any other warning signs?