Related
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.
Little background - been running cm7 for a long time. Flashed the alpha/beta builds when cm10 work started. The alpha worked well, but as the betas progressed and then the nightlies came, the constant freezing and random rebooting basically made the nook unusable. A sd card install experienced the same issues. Since no one else seemed to be experiencing these issues, I just went back to çm7 and have used that since.
Flash forward to today, thought I'd give a stable 10.1.2 a try. Same issues, if it doesn't reboot or freeze on the cm boot screen then it will do it in the setup screen. Wiped data/cache of course. Anyone experienced these issues or have any ideas on a solution? It'd be nice to experience some jellybean goodness. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
gardndj said:
Little background - been running cm7 for a long time. Flashed the alpha/beta builds when cm10 work started. The alpha worked well, but as the betas progressed and then the nightlies came, the constant freezing and random rebooting basically made the nook unusable. A sd card install experienced the same issues. Since no one else seemed to be experiencing these issues, I just went back to çm7 and have used that since.
Flash forward to today, thought I'd give a stable 10.1.2 a try. Same issues, if it doesn't reboot or freeze on the cm boot screen then it will do it in the setup screen. Wiped data/cache of course. Anyone experienced these issues or have any ideas on a solution? It'd be nice to experience some jellybean goodness. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Do you flash new gapps as well?
03/01/13, latest unless I'm missing something?
Sent from my Galaxy Nexus using xda app-developers app
gardndj said:
03/01/13, latest unless I'm missing something?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Only thing I could add is that when I flash a new rom, I boot up into that rom before I go back into TWRP and flash gapps. I have never had the issues you describe. I see you are coming from CM7. That takes a Factory Reset along with a wipe of Cache and Dalvik Cache.
gardndj said:
03/01/13, latest unless I'm missing something?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Did the last suggestion help? I added it later so you might have missed it but I'm sure you not performing a Factory Reset when flashing is the root of your problem.
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
Hello, recently i install lollipop for my nexus 7 2012 And i use the factory image in Google website, before of that i was using cm11, since i install lollipop i having problems with Facebook app, the app Just Crash And close when i open it. I do the factory reset And wipe cache with cwm, And still the same
Sorry for my english
mauri800 said:
Hello, recently i install lollipop for my nexus 7 2012 And i use the factory image in Google website, before of that i was using cm11, since i install lollipop i having problems with Facebook app, the app Just Crash And close when i open it. I do the factory reset And wipe cache with cwm, And still the same
Sorry for my english
Click to expand...
Click to collapse
Yes, I have noticed the same. The Facebook app has been pretty unstable in Lollipop.
I have had a similar experience, I think with usage it improves, Android adapts and optimises RAM and processes, mine seemed to run better after using my tablet for longer, it might still have issue but I'm sure future updates will help
Sent from my D5503 using XDA Free mobile app
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?