yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] chipsa964:
I am having horrible sleep of death issues with any nightly past 0919. I have wiped everything, tried both Devil and Semaphore kernels, tried underclocking and not underclocking, UV/no UV, and every governor I can, but I still get it. Anyone else have this issue or have a way to fix it?
[Captivate Android Development] RootTheMachine:
As long as you are on the new partition layout, nothing will be wiped. I forget which nightly changed the partitions though.
[Captivate Android Development] nok6100:
It was 9-26 the new partition was brought back, anything from that release forward will wipe.

http://changelog.bbqdroid.org/#captivatemtd/cm10/1348646446
[Captivate Android Development] Ajfink:
Been messing with the 10/1 build and it is working VERY well. Major kudos to the CM team and everyone / anyone working to iron out device-specific issues.
[Captivate Android Development] bsaelim:
Cm updater in this build too. Perhaps a replacement for CM downloader?
[Captivate Android Development] ScottyNuttz:
Me too. I was on the monthly until today, but it feels very polished with everything stock.
[Captivate Android Development] MrOpportunity:
Glad so many of you have posted that this is working well for you. I loaded it up last night and my power button stopped working reliably, now I know its hardware. Glad cm10 has such a great built-in work around for that. Thanks all!
[Captivate Android Development] kevinseto:
I too checking in to say that todays nightly is working wonderfully.
[Captivate Android Development] dbaler:
Does anyone know how to remove the "messaging is sending a large number of sms messages." notification or completely remove it from the rom?
[Captivate Android Development] RootTheMachine:
There was actually a post about this on the xda portal. It was for the Gnex but it may still apply here.
[Captivate Android Development] Ajfink:
That's what prompted me to update to yesterday's nightly. I might test it today just to see how it works.
[Captivate Android Development] Bdev3:
Interesting article on it: http://www.androidpolice.com/2012/0...ng-rom-manager-for-its-own-ota-update-system/

CM10 working great here as well.
[Captivate Android Development] mik101:
Has anyone else found media volume not working on 10-2? I'm running the semaphore kernel. Reverted to 10-1 and all is well again. Everything else seemed to work fine on the 10-2 nightly though.
[Captivate Android Development] nok6100:
Working OK here. 10-2 using stock kernel.
[Captivate Android Development] account4me2:
I'm one of those people that gets sleep deaths.

First try raising your minimum clock speed from 100mHz to 200mHz. If that doesn't fix it, flash Devil or some custom kernel and raise your 200mHz voltage a little bit (e.g. by 50mV).

This could all just be coincidence, but:

- way back in the cm9 alphas and early nightlies, I never got sleep deaths

- for many of the late cm9 nightlies I did get sleep deaths, despite multiple full wipes. it was at this stage that the above 2 steps made a *serious* difference to the rate of sleep deaths I got.

- at some point, e.g. I think the 08/15 nightly, I started noticing that I would only get a sleep death within maybe half an hour after I unplugged my phone from the charger in the morning, after having it on there all night. I may or may not have had the above 2 modifications at this point (I probably did).

- I'm pretty sure that on the 09/09 nightly (or maybe shortly after) I wasn't getting any at all.

- they're back with CM10, though I made the 200mHz modification a couple days ago and haven't had any since...

Btw, for me, changing the bootloaders had no effect.

Good luck!

P.S. unrelated, but CM9 and CM10 have had the best battery life by far of any ROM I've ever tried, so thanks guys. :)
[Captivate Android Development] johnnyrichter:
Took a break from latest CM9 stable and checked out the LANIGHT nodatadata which I stuck with for a while. Sweet ROM but I missed having stuff that doesn't come with an AOSP ROM. CM10 seems like it has become stable enough for me to use so I jumped in to the 10-3 nightly.

Initial flash led to a status 7 error. Reflashed which forced a reboot, installed, and put me back in to recovery. Flashed gapps. Rebooted and I'm now at my initial phone setup so it seems everything went OK.

About to restore my user apps and some user data via titanium(first time doing this part) which will hopefully go without a hitch and save me the trouble of redownloading stuff and re-adding all my contacts. :p
[Captivate Android Development] bsaelim:
Work fine in 10-03 with stock kernel.
[Captivate Android Development] dominuce00:
Found the post and here is the link:

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

CWM Flashable zip for us :D
[Captivate Android Development] johnnyrichter:
Running Devil Kernel 1.6.1 VC + CM10 10-3 + Devil Kernel Config. So far everything seems to be working fine.

I have noticed that CM10 runs a bit smoother with Devil Kernel over the baked-in kernel but that'sprobably because I was able to overclock and increase available memory to 403mb. All my games and apps seem to be working fine as well.

Just out of curiosity...why isn't a more customizable kernel included with CM9/CM10? Since everyone seems to go with semaphore or devil it would make sense to bake one of those kernels in to the ROM.
[Captivate Android Development] iosmonster:
probably because not all phones have the customization options that our phones have
[Captivate Android Development] Limitz Cash:
I am downloading now. I been away from the Flashing/Building Custom Roms Scene for awhile. But , I'm getting back into it. Got allot of time on my hands. I hope this CM10 is good. ;)

Thanks Dev...

---------- Post added at 06:52 PM ---------- Previous post was at 05:53 PM ----------

I just got done flashing CM10, and it's real laggy. I don't know why.
[Captivate Android Development] Tonyng:
phone freeze at date wipe

using cwm 5.1.0.7 try to wipe data/factory reset but phone stuck after I hit wipe.. plz help
[Captivate Android Development] johnnyrichter:
Mine was a bit laggy compared to LANIGHT nodatadata(AOSP and quite fast) so I flashed Devil Kernel 1.6.1 VC, installed Devil Config to max out the free RAM at the cost of 720p which doesn't really matter to me, set my clocks to 200/1200mhz using Voltage Control, increased my 200mhz voltage from 950 to 975mv using Voltage Control, and now it's running a bit faster.

You could also try semaphore which some people have been using with CM10. I've never tried it before so I can't offer up any info/tips on this kernel.

---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------

If the phone is definitely frozen then do a battery pull and then boot up with the 3-button combo to get back in to recovery and try to wipe again.

If that doesn't work then maybe try the one-click back to KK4 in my sig, re-root, and try again. The one-click method allows you to go back to KK4 with or without GB bootloaders.
[Captivate Android Development] Limitz Cash:
Now when I go into my Text Messages, and click on a conversation, Messaging Force Closes everytime. I am actually getting allot of force closes. the Rom I came from was Serendipity VII.
[Captivate Android Development] nok6100:
CM updater cannot seem to download the latest nightly, is anyone else having this type of issue? I am on 10-2 right now, trying to download 10-3. Thanks for any info :)
[Captivate Android Development] johnnyrichter:
Did you follow ALL the steps in the OP including wiping the cache partition?

Did you go to settings > apps > all and clear data and cache for Messaging?
[Captivate Android Development] Limitz Cash:
I did the Wipe Cache Partition. However, I think I overlooked the last part. I just flashed Semaphore kernel for CM10. I am waiting for it to bootup, then ill try to Clear data and cache for messaging. Thank you.
[Captivate Android Development] johnnyrichter:
Wiping data and cache for a module/app that is acting up can usually fix it, but it's no guarantee. It's the first step before resorting to flashing the module from another ROM which I can't really comment on as I don't know how to pull files from one ROM to put on another.
[Captivate Android Development] Limitz Cash:
I just did that, and it's still force closes. I am thinking about just flashing a stable version of CM.
[Captivate Android Development] johnnyrichter:
I don't know if there's been a "Stable" cm10 yet, but you could go back a day or two on the nightlies to see if that helps.
[Captivate Android Development] Limitz Cash:
I have just reflashed CM10 , restored my backup via Titanium Backup , and everything seems to be working fine so far. Cm10 looks awesome! I am really loving it! Extremely fast. My web browser and the youtube app is even extremely faster then before. Thank you so much for this amazing ROM! I will be donating to the CM10 dev team really soon. Thank you again. And thank you, everyone who tried to help me, much appreciated.
[Captivate Android Development] Primus76:
Anyone have horrible lag issues with 10 04? I could barely use the phone and had to re flash 10 03 which is humming along happily.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] bsaelim:
i noticed several cm updater entries in the change log, e.g.,

review.cyanogenmod.com/#/c/24249/
[Captivate Android Development] Katze Pavilion:
Battery life is not good. Decrease 1% per minute on using and about 1% per hour on stanby.
[Captivate Android Development] johnnyrichter:
Battery life on 10-3 has been amazing for me, but I have noticed one issue. Heywire doesn't notify me of a new text until I open it which was never a problem on CM9 or LANIGHT.
[Captivate Android Development] bsaelim:
I turned off some background sync (e.g., Twitter) and stand by battery life lasts somewhat longer. On 1003 as well.
[Captivate Android Development] Katze Pavilion:
This may made battery longer lasting on standby, but it still decreses so fast in use.

I'm on 10-04 build. Wiped all before flash.
[Captivate Android Development] bsaelim:
Similar drop during use here . Turn out the screen ranked highest in battery use in my case.
[Captivate Android Development] Edwardayy:
Anyone else having a problem where your phone freezes up when you make/accept a call?

I just updated to the newest nightly 10-4 and the problem still persists.
[Captivate Android Development] killerxtreme:
I can't seem to get CM10 to install, I keep getting

asser failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-10-20121003-NIGHTLY-captivatemtd.zip
(Status 7)
Installation aborted.

Any idea whats up? Would it help if I flashed back to a stock BL, as I'm not really sure which I'm on currently for GB..
[Captivate Android Development] johnnyrichter:
I also got a status 7 error when I first tried to flash CM10 10-3. I rebooted in to recovery and tried again and that time it worked.

Perhaps the one-click back to stock in my sig might help? It gives you the option of going with or without GB bootloaders.
[Captivate Android Development] Gromlakh:
Don't flash bootloaders unless you absolutely have to. Just flash the installer package twice, it makes you do that because of the change in partition structure. There is a fairly significant amount of wrong that will happen.

If that does not work, then you are probably using a kernel/ROM that identifies your phone as an i9000. A flash back to any stock version will fix that; no need to flash bootloaders.
[Captivate Android Development] Edwardayy:
Can someone reply to my previous question? Thank you.
[Captivate Android Development] Bozolini:
I'm on 10-04 and I am not experiencing that problem. I don't notice much difference in speed between this and some popular AOSP Rom's. Most noticeably Ace's. Considering the level of customization on CM it is surprisingly fast. I haven't had any FC's so far. Been running for 36 hours and the battery life is decent. :thumbup:
[Captivate Android Development] Klitoni:
When will Cm10 be realeased as a stable mod?I know its good enough but i wanna try it as a stable.

Thanks
[Captivate Android Development] johnnyrichter:
Devs generally don't like giving out ETAs or being asked for ETAs.
[Captivate Android Development] swayjd:
No one knows, not soon though, thats for sure.
[Captivate Android Development] AriaOfSorrow:
I had the same problem, but for me it couldn't have turned out much worse. When I flashed it a second time, it worked fine. However for some reason it did not install g-apps even though I selected it. So now I don't have any Google apps, including the market, and there's no ROM manager or anything. When I try to reboot into recovery, it acts like I just selected a normal reboot :confused: So I'm trying to get ROM Manager on another way so that it can install g-apps. I went all the way back to the Sideload Wonder Machine, and all of a sudden it can't detect my phone, even though the last time I used it, it had no problem doing so (which admittedly was quite awhile ago). I tried uninstalling the device drivers and reinstalling them, but it magically still cannot detect my phone. Now I'm completely out of ideas. Any other way I could get g-apps installed on my phone?

Edit: All right, never mind about most of the problem. I was able to get into recovery with the three button combo (forgot about that for a little while :P ) and the g-pps were indeed on my sdcard so I installed it no problem. My phone still won't boot into recovery from the power button though, and I definitely have no idea why that is the case or what I can do to fix that.
[Captivate Android Development] shane87:
Ok, so I just upgraded to cm10 (again) from cm9. I had a very odd issue after installation. Here is what happened, and how I fixed it, in case anyone else has this problem.

I downloaded the latest cm10 (10/04) from get.cm, copied it to my sdcard, made a full backup through tibu, and installed cm10. Of course I had to flash twice due to the different partition layout, but I was prepared for that. I also flashed gapps for jb. I booted up and restored my tibu backups, and rebooted again. I had to go in and manually reset all of my settings (ringtone, wifi, lock screen, etc.) I'm guessing that it has something to do with the differing partition layouts. Whatever the case was, that is when I started noticing oddness. My "symptoms" were:

1. No lock screen (I had set a pattern lock, but the phone acted like I had set "None" for lock screen)

2. No "USB Connected" notification when I plugged in usb.

3. No "USB Debugging" notification when I plugged in usb. (I even went and made sure usb debugging was enabled, root for aps + adb, and "notify for usb debugging" was enabled. Adb DID work. I just received no notification saying it was connected.)

4. My capacitive buttons would randomly light up while the screen was off, even though I had no notifications.

My fix:

Reflash cm10.

As soon as I rebooted, I had a lock screen, my usb connected and usb debugging notifications came back, and the capacitive buttons only light when they should. It was very odd, but at least it is fixed.

For anyone who is interested, while I was having the lock screen issue I used adb to pull logcats, and noticed that upon waking my phone I would get a logcat entry saying "no lock screen found."
[Captivate Android Development] Katze Pavilion:
My experiences, follow the CM9 from first the nightly, so I think you have to wait for a long time before dev guys release stable build. But I think there will not many changes when comparing to nightly builds released this time. Why don't you try nightly, it's good enough for daily use. :)
[Captivate Android Development] johnnyrichter:
After installing 10-3 I went 4-5 days without a sleep-death, the longest I've ever gone on non-stock kernel/rom.

Today I've had a sleep-death almost every time I set my phone down.

I haven't changed any settings or installed/deleted anything. Seems 100% random.
[Captivate Android Development] Sledutah:
Installed this yesterday on my wifes (was mine) captivate. Only problem was Status 7 error. I ended up downloading slimbean, let it install a newer version of CWM (I was on v3x). Flashed CM10 (10/4), this thing flies. Only gone through one battery cycle so far, 1d 13hrs with 3hrs display.

Thanks.
[Captivate Android Development] Erick Silver:
Love it!

Wanted to say thanks for the awesome nightly guys! :good: I have been using it for the last month or so and the only issue that I am having is an IMEI issue. I had apparently forgottent to back up that particular folder. However, it has not affected the everyday use of my phone so I have been reluctant to try and fix it. Just updated to the newest nightly and will see how everything works. Thanks again guys!
[Captivate Android Development] nok6100:
Look on your SD card for a folder named "backup", in there should be a backup of your /efs folder.
[Captivate Android Development] gado45:
Just installed m1.. I think its not as speedy as latests nightlys or its just me?

Enviado desde mi SGH-I897 usando Tapatalk 2
[Captivate Android Development] bsaelim:
M1 as released in September? I don't think it includes hw composer changes even.
[Captivate Android Development] mik101:
That was my experience when I used to use CM7 nightlies on my Nexus One. It seems luck of the draw. My best friend also had a N1 and we would install things identically step by step and his would always be fine, but mine would have sleep of death issues and other freezing/data corruption issues. Eventually the solution for me was to modify the running voltages of the cpu to give it an extra 25 or 50mV (Wildmonks kernel was the ONLY one that I could ever get stable on that device).

You'll also want to try not using 100mhz as the lowest frequency value if you haven't already. Try 200mhz instead. I'm not sure about changing the voltages in the CM10 kernel, but I suspect third parties (Devil or Semaphore for example) you should be able to give it a little more voltage to make it stable. I have zero issues with SODs on my I896, even when using Deep Idle on Semaphore.

My current setup is: The Oct 1 CM10 Nightly (Captivatemtd) with Semaphore 2.2.0c kernel. (Well I'm actually running the sc version with modified libraries, but that really isn't needed unless you want 720p video camera and 391mb of system ram together.)

Everything works as it should, performance is good (3711 in Antutu without any extra tweaking), battery life is good, and I've had zero crashes or sleep of deaths since installing. I couldn't be much happier with it.

PS. the modem is KG3.
[Captivate Android Development] johnnyrichter:
I run my minimum clock at 200mhz and I bump its minimum clock voltage up from 950 to 975-1000 depending on which results in the least amount of sleep-deaths. I even tried a a 400mhz minimum clock but it still had the issue. I think the only time I never had the problem was on stock GB KK4.

Usually my phone won't sleep death after a new kernel and ROM install. It'll be fine for a few days and then the day it comes back it'll happen like 10 times. Then for the rest of the time I have that kernel/rom it will have anywhere from 1 to 3 a day. It's really weird that there seems to be a formula to it.
[Captivate Android Development] Primus76:
I set my min cpu to 400. That's the only change I make and it is smooth with no sod.

Odd that there hasn't been a nightly for a bit though.
[Captivate Android Development] gado45:
M series was released yesterday, not setember, check cyanogenmod official page

Enviado desde mi SGH-I897 usando Tapatalk 2
[Captivate Android Development] RootTheMachine:
False, September. Maybe for some devices, but captivate had a m release several weeks ago.
[Captivate Android Development] swayjd:
there might be a problem with the bot, or we might have been dropped =/
[Captivate Android Development] bsaelim:
I got at least 5 sod as well since yesterday on 10-04. Will give 400 as min cpu a try (not sure how that would impact the battery though)
[Captivate Android Development] cnu4u:
Android 4.1.2 is getting released to AOSP today.... http://www.androidpolice.com/2012/1...id-4-1-2-update-being-released-to-aosp-today/

Hope we are going to see upcoming nightlies with 4.1.2 :)
[Captivate Android Development] Lollipop_Lawlipop:
Changes are minimal for other devices. Even for the N7, there aren't a lot of changes. The biggest (imo) were driver updates, but that's not applicable to the Captivate.

In other words, nothing to see here for now.
[Captivate Android Development] killerxtreme:
Everytime my phone starts up I get the flash that says I-9000, doesn't that mean that its using the i-9000 bootloaders?
[Captivate Android Development] simple man:
Yes it does.
[Captivate Android Development] Primus76:
Over 1 day so far. 31 % remaining. I did go back to 10-3 though.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] shuyin1102:
Yeah, the screen often froze when i brought it out from my pocket to accept a phone call in all the 4.x ROMs. A long press will fix, i have no idea
[Captivate Android Development] bsaelim:
Stable again after removing some apps and widgets.

On 10-4 with min cpu 100.
[Captivate Android Development] vileladelima:
Please delete!
[Captivate Android Development] melvinaury:
Well you better erase you're post the devs don't like asking for a time of a release.:eek:
[Captivate Android Development] gado45:
How do I know wich kernels are compatible with 10-4 ? Flashed devil, didnt boot so I reflashed 10-4

Enviado desde mi SGH-I897 usando Tapatalk 2
[Captivate Android Development] nkrick:
You check the thread for the 3rd party kernel and ask there.
[Captivate Android Development] shuyin1102:
:silly::silly: NEW BUILDS GUYS http://get.cm/?device=captivatemtd :cyclops:
[Captivate Android Development] bsaelim:
M2 is out too.
[Captivate Android Development] vileladelima:
Wha is the difference between these two CM10 versions:

1.cm-10-20121011-NIGHTLY-captivatemtd.zip

2.cm-10-20121011-EXPERIMENTAL-captivatemtd-M2.zip

I did not found nothing yet that answer me.

Thanks!
[Captivate Android Development] Primus76:
Someone will correct me if I am wrong but the M2 is the monthly 'stable' release which can be considered as a daily driver. The other is the regular nightly and if released the same day they are most likely the same.

Going forward you have 2 options, if you want to flash once a month then just ignore the nightlies and wait for m3 in November or whenever it comes out OR ignore the m2 and keep on flashing nightlies but be warned that they may be slightly less stable.

The short - 'm' releases are classified as the most stable and will be updated less frequently. To stay bleeding edge just keep on with the nightlies.

Sent from my Motorola DynaTAC 8000X
[Captivate Android Development] bsaelim:
Running m2 now, it is Android 4.1.2. I believe 4.1.2 merged into nightly as well.
[Captivate Android Development] Lollipop_Lawlipop:
They are identical save for branding.
[Captivate Android Development] Primus76:
Up until 10 02 i was running smooth and fine with min cpu 200 but after I am getting horrible lag even with 400 on the latest 10 11.

Anyone else?
[Captivate Android Development] nkrick:
The builds themselves may be the same because of when they were built, however, you can make official bug reports on "M" builds, similar to RC and official builds. If you find a non-device specific bug in CM, see if it is in the latest "M" build. If it is, check the CM bug tracker and see if anyone else reported it. The "M" builds should decrease the RC testing cycles because hopefully many CM bugs can be fixed through bug reports on the "M" builds before RC's are released.
[Captivate Android Development] jonathan413:
How do you change DPI? Can't edit build.prop because changes don't stick and apps from the market make my phone hang at boot screen.
[Captivate Android Development] bsaelim:
No performance issue with M2 at min 100. Not sure about the latest nightly though.
[Captivate Android Development] suerspud9:
with the new cm updater, is there a way to get the full names of the roms to display? right now the names get cutoff
[Captivate Android Development] cnu4u:
See if you can see more information in landscape mode.