CM11 M4 snapshot.

[RottenEntrailz]

Anyone try this yet? Impressions?

Sent from my Nook HD CM11.

 

[pyrofool]

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.

 

[Goggles2114]

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.

 

[jeobenauer]

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.

 

[Goggles2114]

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

 

[RottenEntrailz]

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

 

[digixmax]

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.

 

[JanSpatschek]

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?

 

[adwait.bhandari]

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

 

[jeobenauer]

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

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.

 

[alex9yust]

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.

need to do wipe data/factory reset and not restore the old data. otherwise, "android.process.acore stopped unexpectedly" for me.

 

[buzz killington]

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.

 

[JimJ2Mz]

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