Database Users

CM10 Nightlies for Fascinate!

Just noticed that fascinatemtd is finally being included on the CM10 nightlies! I've been following the Jelly Bro roms up to last week. Although I've been using it as my daily driver, I'm looking forward to even more stability.

Anything not working?

Hilbe said:
Anything not working?
Click to expand...
Click to collapse
I couldn't get the market to download any apps on 8/22. 7/26 gapps. Wiped all three coming from Jt's newest build. Tried twice.

rjkxb2 said:
I couldn't get the market to download any apps on 8/22. 7/26 gapps. Wiped all three coming from Jt's newest build. Tried twice.
Click to expand...
Click to collapse
JT's last build (19 August) had zero issues for me. Last night I dirty-flashed to the 8-23 nightly (after wiping caches) and all is well including app installs with market.
Sent from my SCH-I500 using xda premium

is anyone running the nightly on a alt carrier ?
if so can i get a link to the fix

The wifi reception on the 8/24 nightly with devil kernel 1.2.1 is not as strong as on ths ics build 15 with devil 1.1.3
Smoother than ics, but doesn't feel quite as fast.

What CWM are people using. I was running 7.2 and tried flashing while CWM 3 was installed, it rebooted in CWM 6 and it said it installed fine, but im stuck on the Cyanogenmod boot screen for like 10 minutes...
also is there a way to turn a ROM ZIP file into something I can use Odin to flash it with? I can get into recovery, but I dont ahve a mini USB reader to install a new ROM on.

I was running build 15 teamhacksung ICS, then went to 8/24 build CM10.. cleared all cache, etc, installed cleanly. Loved jelly bean, but it's still very half baked, not usable as an every day phone.
Just went back to CM9 nightly, into which teamhacksung ICS was rolled into today, and everything is nice and quick again. will go back to CM10 when the bugs are worked out.

audiphile said:
I was running build 15 teamhacksung ICS, then went to 8/24 build CM10.. cleared all cache, etc, installed cleanly. Loved jelly bean, but it's still very half baked, not usable as an every day phone.
Just went back to CM9 nightly, into which teamhacksung ICS was rolled into today, and everything is nice and quick again. will go back to CM10 when the bugs are worked out.
Click to expand...
Click to collapse
Really?? 8/24 nightly and all of Jt's builds before that worked great. Very snappy and I've had zero problems. I haven't been back to ICS since probably JT's second build. The nightlies or paranoid android are what I use now daily, and I haven't had a bug problem in quite some time.

I'm been on CM10 8/19 nightly since it dropped. Everything works. I use it heavily for work and personal.
I've put off updating my ROM to another nightly, because it takes me a hour or two to get everything restored back the way I want it. Seems you really do need to do both wipes and a cache flush, then flash ROM, then latest JB apps, to assure best results. I've tried cutting corners twice, and both times, it's bit me in the ass.
Kind of hoping they'll hit a "stable" point on the nightlies soon, and I'll catch up then. I ran CM9 happily for about a month, but I'm so pleased with the additional smoothness, stability and additional features of JB, I haven't looked back since I switched.

tbaddley said:
I'm been on CM10 8/19 nightly since it dropped. Everything works. I use it heavily for work and personal.
I've put off updating my ROM to another nightly, because it takes me a hour or two to get everything restored back the way I want it. Seems you really do need to do both wipes and a cache flush, then flash ROM, then latest JB apps, to assure best results. I've tried cutting corners twice, and both times, it's bit me in the ass.
Kind of hoping they'll hit a "stable" point on the nightlies soon, and I'll catch up then. I ran CM9 happily for about a month, but I'm so pleased with the additional smoothness, stability and additional features of JB, I haven't looked back since I switched.
Click to expand...
Click to collapse
Strange, I have the exact opposite experience. I install everything clean, never cut corners.. CM10 seems to have some memory leak.. it start out really beautiful and smooth.. within hours, it's not usable. CM9 remains stable for days in a row, so i'm back to that for a while.

I've been using the nightly CM-10 builds since 8/23. What's the consensus? If I want to flash to the latest build, do I need to wipe the data and cache?
Thanks!

gm2racer said:
I've been using the nightly CM-10 builds since 8/23. What's the consensus? If I want to flash to the latest build, do I need to wipe the data and cache?
Thanks!
Click to expand...
Click to collapse
That's been my experience, and the thing holding me back from upgrading right now. Definitely going to flash to the latest by this weekend, to see if there are any changes/improvements.
I'm just glad I haven't experienced any memory-leak type behavior. I will admit, though, that I've had it do the "sleep of death" thing twice in ~2 weeks. It may have come back to life on it's own, but I was impatient and pulled the battery in both instances.

is anybody else not able to send mms ?

tbaddley said:
That's been my experience, and the thing holding me back from upgrading right now. Definitely going to flash to the latest by this weekend, to see if there are any changes/improvements.
Click to expand...
Click to collapse
I've done a couple of flashes without wiping the data or cache with no ill effect.

Flashed the 9.1.12 CM10 nightly this morning. Only wiped Dalvik cache, nothing else. Kept all my apps/settings. Everything but Google Music was working great, so I flashed the GApps again, went into Play, uninstalled/reinstalled Music, and everything works now.
GPS locks in pretty quickly in GMaps and all of my GApp and 3rd party apps are working normally.
If this continues to be stable, I'll be more likely to flash more nightlies, with fewer days between upgrades.

phone call static
Has anyone experienced static when making phone calls. I was using the 8/26 build and everyone that I called complained that they couldn't understand me because there was a lot of static. I flashed the 9/1 build and I get the samething but a little worst. Other than the static everything is working great.

Bassmas5 said:
Has anyone experienced static when making phone calls. I was using the 8/26 build and everyone that I called complained that they couldn't understand me because there was a lot of static. I flashed the 9/1 build and I get the samething but a little worst. Other than the static everything is working great.
Click to expand...
Click to collapse
No static here... I've been running the cm10 nightlies (stock kernel) for about a week without any issues. I updated to the 09-04 build last night after just wiping cache and dalvik, along with a test kernel that JT posted yesterday that's designed to provide a bit more power to the radio in order to maybe fix the intermittent loss of data. So far so good.
One thing - I've had some issues after experimenting with using link2sd (a great tool) to move various apps to /system to save precious space on /data. It seems that after moving Google maps; voice; Gmail; and similar core apps to system, play store reports update after update for the apps I've moved.
Sent from my SCH-I500 using xda premium

i was running SC3 milestone 2 (gingerbread).
i odin'd to stock EH03 then rooted it.
tried flashing the CM10 ROM via CWM recovery 2.5.1.x (red), 3.0.0.5 (blue), and 3.0.0.8 (yellow). they all abort saying that there is an error on the .zip file.
any suggestions?
edit: followed this: http://forum.xda-developers.com/showthread.php?t=1238070; stock GB -> THS ICS -> JB. yay!

Anyone else notice that auto brightness isn't working, or maybe it's just me? Using the 9/10 nightly.
Edit: Seems to be working now, before I had all -1's in the light sensor levels but now I'm getting actual values.

Cyanogenmod Samsung Logo Hang

Is anyone else having the problem where if you turn off your phone and turn it back on it'll sometimes freeze at the Samsung logo. If you do a battery pull and turn the phone back on again, it'll boot like normal.
Firmware: MDL
ROM: Cyanogenmod 10.1 RC2
Recovery: TWRP

What twrp version?

xBeerdroiDx said:
What twrp version?
Click to expand...
Click to collapse
TWRP 2.5.0.2
I used your HOW-TO guide to complete everything
Loki+TWRP+Motochopper CASUAL
Wiping Device
Flashing ROM

How long has it been doing this/at what point did it start?

I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal

emckai said:
I've only had the phone for about 2-3 days and when I got it I immediately flashed CM. So ever since I flashed it?
I just noticed it last night though.
No changes. Only CM was flashed. No different kernal
Click to expand...
Click to collapse
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.

jd1639 said:
This has been seen in some builds of 4.3. If you let it boot a long time it'll usually get past that and then be ok. Technically, the 2.5 build of twrp is not for 4.3 roms so you might try 2.6.3.0. But that's been met with mixed success.
Click to expand...
Click to collapse
RC2 is a 4.2.2 build.
Last night I decided to just try and let it hang and see if it'll get past it but 2 minutes later it never did. So I just held the power button (10 seconds) to shut it down and restart.

Sorry, didn't read your whole post and missed the rc2.

jd1639 said:
Sorry, didn't read your whole post and missed the rc2.
Click to expand...
Click to collapse
No problem. Just wondering what is causing this issue, seems like some people in the Cyanogenmod thread is also having this issue.

It's happening on the cm10.2 roms too and seems to be related to the recovery used. See if twrp 2.6.3.0 works for you.

SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.

I switched custom recovery. TWRP to CWM and everything is booting just fine. (knock on wood) I'll turn off and on my phone a couple more times and see if it's actually the custom recovery.

cwm has had far fewer problems on the S4 than twrp. i've always rolled with cwm touch across my devices just out of preference. glad i havent had to deal with any of these twrp issues. glad you're sorted. cheers

Just rebooted my phone a couple of times (about 10 times) and it didn't hang at samsung logo anymore.
Thanks everyone!

emckai said:
SOLVED: According to Cyanogenmod this is a known issue. Check the #2 post in the OFFICIAL cyanogenmod thread.
Click to expand...
Click to collapse
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.

CZ Eddie said:
LMAO, that's not "solved". It's simply acknowledging there is a problem. hahah
So guys, the problem is not just in CyanogenMOD. It's also in stock 4.3 GE and 4.4 ROM's. And I get it regardless of what version of TWRP or Philz CWM I use.
It's something that started with 4.3 and is still present in 4.4 (stock GE & AOSP both). Because I never had the problem on any 4.2 ROM's.
Click to expand...
Click to collapse
x2 to all of the above. Known issue for S4s on 4.3 and 4.4 and although a couple of ROMs have claimed that they're "solving" it as of yesterday's nightlies it ain't fixed....
Just hold down power till the Samsung screen disappears then immediately let go. It'll try again. Repeat, repeat, repeat as necessary and eventually it will work.

Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.

CZ Eddie said:
Okay, it's definitely a kernel issue.
I've ruled out recovery and ROM.
For instance, I flashed an AOSP 4.4 ROM and it was freezing at Galaxy S4 splash screen on almost every single reboot.
Then I flashed a different kernel and the issue immediately and completely disappeared. I've done 20+ reboots since.
I flashed Ktoonsez 4.4 AOSP kernel btw. That's what fixed it for me.
Click to expand...
Click to collapse
I've been using the same kernel since yesterday afternoon and haven't hung once either. I've tried it with CWM and TWRP because my hangs used to occur when I rebooted system from recovery and both have worked just fine.

CM11 M4 snapshot.

Anyone try this yet? Impressions?
Sent from my Nook HD CM11.

I tried it last night. I flashed over the 3-6 nightly and had many force closes and network issues. I did not try and do a clean flash.

On an attempt to just hit update and go it got stuck in a reboot loop. Attempting a clean install results in network seen but not connecting. Rolling back to 10.1.3.
Edit now it seems no matter what version I try installing networking is hosed. I feel kinda stupid here guys.
Edit: Had to go through reflashing cwm-5 the m4 rom, gapps, and all that as if I wee going from 10.2 rather than update 'just working' Most annoyed.

I should have left well enough lone. I had installed the 3/8 nightly and it was working great.
Then I saw the 3/8 snapshot and decided to install it.
The Snapshot seems to be no good. It throws errors when logging in and I also lost WiFi.
I have re-installed the 3/8 Nightly and am a happy camper again.

In fairness leaving well enough alone would have left you with B&N's stock environment. We tinker, it's what we do.

I gave this a shot myself and got a bunch of fc's. Went back to the last nightly. From what I heard the M should be more stable so much for that.
Sent from my SCH-I545 using xda app-developers app

I updated from 01/18 to the M4 and it has been very stable.
See http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for important considerations in switching between the two branches snapshot/stable and nightlies of CM11. The blog explains why going from some of the most recent nightlies to M4 might be a downgrade and as such can cause the problems reported above.

I don't know if I just have bad luck (or a bad device), but I haven't had a single official CM11 build without random reboots and screen flashing / flickering. Anyone else here?

You should not flash the m4 if your nightly is newer than 20140308 otherwise you will get FC's.

adwait.bhandari said:
You should not flash the m4 if your nightly is newer than 20140308 otherwise you will get FC's.
Click to expand...
Click to collapse
Not true.
M4 was taken from the nightly branch on 2/28. If you have flashed a nightly to your device newer than 2/28, you will be downgrading if you flash M4 afterwards - resulting in unpredictable results.
Based on this thread, the results will be WiFi issues and possible boot issues.
If you want to switch to the monthly builds, do not take anymore nightly builds, and wait until April to take the M5. If you want to stick with the nightly s, then do not flash the monthly's.

pyrofool said:
I tried it last night. I flashed over the 3-6 nightly and had many force closes and network issues. I did not try and do a clean flash.
Click to expand...
Click to collapse
need to do wipe data/factory reset and not restore the old data. otherwise, "android.process.acore stopped unexpectedly" for me.

I guess I got lucky. I dirty flashed m4 over 10.1.3 stable and everything is running perfectly. I wasn't expecting it, but m4 is much speedier than 10.1.3, only downside is battery life seems to be not as good.

Beware!
There was a post I found a while back on the official Cyanogemod site that went into details about Nightlies, Milestones, Release Candidates, and Stable Releases. What would be most important for users of CM11 at this time which was explained in the post is that you either stick with updating from nightly to nightly OR milestone to milestone. If you're on a nightly and you update to a milestone snapshot, you risk damaging and messing up the OS. Vice-versa as well and should also apply to RCs and Stables. Nightlies are bleeding edge and have the latest code while a milestone snapshot is more stable, but has older cold. So going from nightly to milestone snapshot would be one heck of a messy downgrade.
srry for dis messy post btw qq

[Q]Update CM 10.2.1(grouper) to which CM 11 version on Nexus 7 2012

Been meaning to update to CM 10.2.1 on my Nexus 7 tablet for a while now. Was a rank noob when I rooted & flashed it (using Skipsoft Unified Kit, all props to the dev!) so bear with me if I get a bit bogged down re technicalities.
It failed to install automatically in TWRP so I flashed the zip manually, and was successful. Now because it's been a pretty long time in between updates, 3 other CM11 updates have appeared...guessing the latest is the first one listed below. Do you have to progress through them in sequence to get to the latest? Also is there anything different about updating to a new version, ie from 10 to 11? Can I just use the auto updater in settings?
The 3 available
cm-11-20141112-SNAPSHOT-M12
cm-11-20140916-SNAPSHOT-M10
cm-11-20140804-SNAPSHOT-M9
Thanks for any opinions etc

Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck

R_a_z_v_a_n said:
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck
Click to expand...
Click to collapse
Thanks to the mods for moving it to the correct forum.

This is still the wrong forum. You're looking for 2012, you're in 2013.

nhizzat said:
This is still the wrong forum. You're looking for 2012, you're in 2013.
Click to expand...
Click to collapse
Uh yes Lol
I did mention that should be sorted asap

Just bumping this from the 3rd page. I think it got lost in the initial misdirected subforum, in case anyone has some input

If you update the Android version, e.g. CM 10 to 11, you should to a factory reset first, otherwise you can simply flash the latest build (M12).
The auto updater always worked for me when upgrading one CM 11 build to a newer one.

Thanks luckyrumo. So - just getting this straight for the noob lol - a factory reset needed due to moving one Android version to the next ie from JB to Kitkat to switch from CM10 to 11 is that right?

zhukoz said:
Thanks luckyrumo. So - just getting this straight for the noob lol - a factory reset needed due to moving one Android version to the next ie from JB to Kitkat to switch from CM10 to 11 is that right?
Click to expand...
Click to collapse
Sure you can try without, but I'd do one. With a tool like TitaniumBackup you can restore almost everything afterwards.

[CM 13 122715 unoffcl] Setup Wizard Loop after upgrading to May 25 Nightly and Gapps

After upgrading to the newest 25 May nightly I've got a pop-up that play store has stopped working, so clearly a gapps fail. Checked and saw that there were new gapps (May 25) so I dirty flashed them (without cleaning cache). And then I fell into the loop. I panicked and rolled to the May 22 Nightly to see if there was any change but it was the same, so I hope I didn't mess something up with this stupid move. Anyway, is there a way I can continue using my gapps without full factory wipe and without reinstalling the ROM?

Jaegerz said:
After upgrading to the newest 25 May nightly I've got a pop-up that play store has stopped working, so clearly a gapps fail. Checked and saw that there were new gapps (May 25) so I dirty flashed them (without cleaning cache). And then I fell into the loop. I panicked and rolled to the May 22 Nightly to see if there was any change but it was the same, so I hope I didn't mess something up with this stupid move. Anyway, is there a way I can continue using my gapps without full factory wipe and without reinstalling the ROM?
Click to expand...
Click to collapse
They just tweeted there was an issue with 5/25 nightlies and gapps just reinstall gapps I guess, I don't use CM so that's all I can say.
Sent from my Galaxy S5 using XDA Labs

CyanogenMod ‏@CyanogenMod An erroneous 'n' slipped into an ifeq check and caused last night's nightlies to kill gapps. [1/2]
CyanogenMod ‏@CyanogenMod 1h1 hour ago Seattle, WA
The fix is already in place and builds will be pulled shortly, but consider staying clear of the 5/25 nightlies. [2/2]

Rakuu said:
They just tweeted there was an issue with 5/25 nightlies and gapps just reinstall gapps I guess, I don't use CM so that's all I can say.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Okay, thank you! After all the mess I had done though, will I be alright with just installing the new nightly update when it comes out?