yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] :
I am not sure about this as I actually used higher values than the default ones :( and still had the problem. Maybe extreme high empty app value would help but then there is no point in having 1GB of RAM available...
[Samsung Galaxy Nexus] bamtan2:
CM should know better than to give people destructive upgrades. :( It is a shame how so many people are coming to the forum complaining about this. CM should know better, shame shame.

I don't know what the CM community is doing about this, but I almost wish [MENTION=2633638]Ziyan[/MENTION]'s last build of CM12 had disabled the updater app, or made it so it couldn't update to CM13.

I think what you're noticing may be the normal behavior. Wait 10+ minutes for the phone to start after a ROM flash. Also, I wonder if your facebook app problem could be caused by rebooting the phone during the normal boot process?
[Samsung Galaxy Nexus] Android-Andi:
Wrong forum
[Samsung Galaxy Nexus] Gorduza:
Hey Guys, I have seen that there are new updates available, so I went to install them finaly. Download, install, reboot and S**T... did I just installed 6.0.1? :confused:

Now I am in this stage like a person named Sin Jeong-hun in CynogenMOD Development Forum:

The only diffrence is that I have the latest version installed: cm-13.0-20160803-NIGHTLY-maguro.zip

with installed OpenGApps: open_gapps-arm-6.0-pico-20160803.zip

My question, is there a way I can make my device work properly without total wipe?

Thanks in advance.
[Samsung Galaxy Nexus] l.capriotti:
I had CM13 since some months, moved to the nightlies as soon as the first one was released, updated a couple of times since then.

Yesterday I installed the latest one and now I have the system partition completely full, up to the point that adaway cannot write the host file due to no space.

Should I try a clean install formatting /system?
[Samsung Galaxy Nexus] hgmichna:
system full

A system without reserves is a bad system.

Had you installed OpenGapps nano? If so, then switching to pico would solve your problem, i.e. wipe system, flash CM and pico OpenGapps.

But I suspect you were already on pico. Doing the same procedure may buy you a little time, but if we are generally so close to full then the problem calls for a general solution. [MENTION=2633638]Ziyan[/MENTION]?
[Samsung Galaxy Nexus] MayuraDeSilva:
You can try REPIT to increase the size of /system partition without wiping anything, or wipe /system and reinstall.
[Samsung Galaxy Nexus] hgmichna:
system full

Technically highly competent Android cracks can do this, but what about the many non-technical users? I hope that the resizing can be done automatically in future updates.
[Samsung Galaxy Nexus] MayuraDeSilva:
Prerequisites: TWRP 3.0.2-0

1. Download the file for maguro (If your partitions formatted in F2FS, need to change the filename - Read: How to REPIT)

2. Disable MTP

3. Copy it to /tmp folder via TWRP File Manager

4. Flash

If he can handle those steps, he'd be fine.
[Samsung Galaxy Nexus] hgmichna:
system full

She.

You haven't dealt much with non-technical users. If you write this up step by step, finger touch by finger touch, you end up with several printed pages, and the likelihood that one step goes wrong is high. If you write down how to recover from each and every mistake, you have to write a book.

I have done this, so I know what I am talking about. Check, for example, How to update from CyanogenMod 12.1 to 13, which describes a simpler procedure, but inexperienced users still make mistakes.

Generally, if CyanogenMod should remain popular, it has to be easy to install and update for non-technical users. Otherwise it will be a small niche product for a few nerds like us here.

The most horrible mistake in recent times was to kill the user's phone when she used the built-in CyanogenMod updater and got from CM 12.1 to the first CM 13.0, a truly evil development that has damaged CyanogenMod's reputation.
[Samsung Galaxy Nexus] Gorduza:
I don't like what I am reading...

Yeah... :crying:

Edit:

So what do I have to do now? Do I need to flash CM 12.1 with 5.0 OpenGApps and than CM 13 with 6.0 OpenGApps? Will I loose data? Do I need to wipe anything?
[Samsung Galaxy Nexus] Regina Rainbow:
[MENTION=2633638]Ziyan[/MENTION]: Back in the time when you optimized the ducati carveouts for CM 12.1, there have been the same symptoms around (camera crashing, not possible to reconnect afterwards). In this post it turned out, it might have been triggered by disabling HAL debugging. After you reenabled HAL debugging, camera (ducati) was stable even with bigger carveouts.

I think I remember that disabling HAL debugging was one of your commits for CM 13 in the nearer past. So, might the camera (ducati) problem in CM 13 also be related to the debugging code?
[Samsung Galaxy Nexus] hgmichna:
How to update from CyanogenMod 12.1 to 13.0

How to update from CyanogenMod 12.1 to 13.0
[Samsung Galaxy Nexus] MayuraDeSilva:
Probably. Here what we can do is offer help and suggestions for a specific situation. We don't know if the user is non-technical user or can't presume what he or she'd gonna do with our suggestions, or what's most comfortable to proceed with. She may ask if any questions. Ultimately, it's up to the user to decide.

I've come across a similar issue (/system being full) with nightlies after 27th, and both wiping /system and REPIT helped me in those situations. Hence the response:
[Samsung Galaxy Nexus] Regina Rainbow:
Adaptive Brighness not working

Main problem for me is that adaptive brightness seems to be broken. Therefore the screens tends to be way too dark, really hard to read even in surroundings with dim light. In CM 12.1 this didn't happen, screen brightness always adapted to a sound level.

Steps to reproduce

:

1. Turn on adaptive brightness [Settings -> Display & lights -> Adaptive brightness]

2. Start some app, that prevents the screen from turning off automatically (or just keep the device busy by touching the screen)

3. Cover the light sensor of your Galaxy Nexus with your finger for 10-15 Seconds. [Sensor is right next to the front speaker of your phone]

Expected behavior

:

Screen get's darker gradually, as long as your finger is on the sensor. Screen get's brighter, when you release your finger.

Observed behavior

:

Screen brightness doesn't change at all

Anyone else having this issue?

Edit: Couldn't reproduce this bug anymore after reinstalling the affected version of CM13. So for me, this bug is closed.
[Samsung Galaxy Nexus] hgmichna:
Adaptive brightness

Not me, anyway. Automatic brightness adaptation works just fine here.

Anybody else?
[Samsung Galaxy Nexus] Gorduza:
So I followed the tutorial and made Factory reset, installed CM12.1 with OpenGApps for 5.1 and it worked perfectly fine, than I installed CM13 and OpenGApps 6.0 and after optimizing 47 apps It stuck on "Finalizing update" rotating circle. After an hour I held the power button to turn off and than turn on the phone. The system then optimized another 8 apps and carried on. It is now working fine, but it was weird and I was worried. :) I can finaly use my phone again! Thank you for your help. :good:

Automatic brightness is working fine for me.
[Samsung Galaxy Nexus] axlu:
Hi. I might have had the camera from cyanogenmod apps. While I was trying to apply a fix for USB OTG my phone has crashed, so I have to factory reset and reinstall everything. It looks like a rather lenghty proces. Can I go directly to CM13?
[Samsung Galaxy Nexus] hgmichna:
How to update from CyanogenMod 12.1 to 13.0

Factory reset cannot hurt, but was not prescribed and not needed. In fact, if you did a factory reset then you could install CM 13.0 straight away, without reinstalling CM 12.1 first. I have added this possibility to the instructions.

The crazy getting stuck after an update seems to be a defect in CM 13.0. Apparently we all have that after each update. I hope it is harmless and only requires an extra reboot. I also hope it will get fixed in a future update.

---------- Post added at 05:55 PM ---------- Previous post was at 05:49 PM ----------

Yes, after a factory reset you can go to just any version. If you use the TWRP recovery, wipe system as well and the caches. With the Cyanogen Recovery just wipe cache. Some later versions had a defect that wiping system also wiped all internal memory. Not sure about this, but anyway it works without wiping.

Then flash cm-13.0 and the OpenGapps for ARM, Android 6, pico without rebooting in between.
[Samsung Galaxy Nexus] bamtan2:
I'm sorry these bad things happened to you :( To avoid this, I personally try to use older software for longer, so I stay more "user" and less "tester". I am on CM12 so [MENTION=2893530]hgmichna[/MENTION]'s guide is helpful to me, thank you for that!!

CM13 may have more bugs than CM12. It certainly will receive more NEW bugs, because it is under more new development. I recommend not updating from CM12 to CM13 unless you have a backup of your data and are prepared to factory reset if something goes wrong.

If have a problem with the /system size, maybe due to a CM13 bug or a GAPPS bug, the only solutions are to revert to an older version and wait for a fix, or use REPIT to expand /system into the space unused by /cache. I believe REPIT is safe to use. First flash ROM, then REPIT, then GAPPS. When you flash the proper REPIT zip file in TWRP, it will copy itself to /tmp, and then you can unmount your file systems and flash it again from /tmp. If this is too complicated, I recommend staying on CM12 stable for the near future.
[Samsung Galaxy Nexus] typ1232:
So I decided to do the upgrade from latest cm12.1 to cm13 nightly from 20160803. I did a dirty flash, but followed the instructions to flash gapps right after.

So far everything is working great except for one issue.

The maximum screen brightness is way too low. During boot I see the screen going to full brightness, but after booting it goes very dim. This doesn't seem to be related to the issue with adaptive brightness that someone mentioned here today. Whether adaptive brightness is enabled or not, the maximum brightness is just very low. This sadly makes the phone unusable in the sun.

Do you have any suggestions?
[Samsung Galaxy Nexus] axlu:
Hi. I am using cyanogenmod recovery. I have tried to make a factory reset, but I can only get a screen with Google and a padlock after restart. I have tried to reload the bootloader: same screen. What can I do?
[Samsung Galaxy Nexus] NightShadow02:
I came from stock ICS and installed CWM then flashed cm13 and pico gapps 6.0 and I got a ton of messages regarding google play services have stopped or something. would you happen to know what went wrong?
[Samsung Galaxy Nexus] Android-Andi:
Have seen those happen if user use outdated recovery & OpenGapps.

~ All my work, news etc. on http://andi34.github.io ~

Edit: also happens if google apps don't have proper perms. On some gapps you have to set perms manually before login into google account.
[Samsung Galaxy Nexus] hgmichna:
Updating from stock to CyanogenMod 13

I would first install TWRP, either 2.8.7.0 or 3.0.2. The easiest way is through TWRP Manager, but that requires a running Android, so in your situation you will have to go to fastboot mode and install the recovery with the command (replace the twrp...img file name with the actual one):

fastboot flash recovery twrp...img

You have to wipe data (factory reset), system, and caches. Then flash cm-13.0 and OpenGapps ARM, Android 6, pico.

After this and after everything works fine, you can flash the Cyanogen Recovery and switch on automatic recovery updating in the developer options. Alternatively you can stick with TWRP, but you have to update TWRP manually.
[Samsung Galaxy Nexus] Regina Rainbow:
Thanks for checking! So it seems like the problem roots in some specific quirk of my phone/installation of CM 13.
[Samsung Galaxy Nexus] hgmichna:
Automatic brightness

Quite likely, but it could also be a hardware defect. The sensor or its connections may be broken.

The test would be to install an older Android, but that's a lot of work for an old phone.
[Samsung Galaxy Nexus] Regina Rainbow:
Thanks for your reply. I had this problem after upgrading (=dirty flashing, more or less!) CM 12.1 to CM 13, following your excellent how-to (kudos!). To rule out the possibility of a hardware error or bug of this specific MM-ROM I meanwhile did a clean install of Omni 6 (wiping caches and data before). Outcome: adaptive brightness is working on Omni 6. I think this could be a CM 13 bug on the Galaxy Nexus, maybe especially for people upgrading, because additionally I had the same brightness issues typ1232 describes. Right now I'm installing a TWRP-Backup of my faulty CM 13-Install to dig a little deeper into this.
[Samsung Galaxy Nexus] Zenroid:
I have such problem on cm13 as well
[Samsung Galaxy Nexus] LeoHart:
[MENTION=7643454]jango0[/MENTION]

Screen casting never worked with the Gnex.

Neither on stock nor with cm.
[Samsung Galaxy Nexus] Maguro13:
Clean Flash not working CyanogenMod 13.0

I am trying to do a clean flash of cm-13.0-20160806-NIGHTLY-maguro with open_gapps-arm-6.0-pico-20160806 using TWRP twrp-2.8.7.0-maguro.

Wiped everything.

It always says Google Play Services has stopped working.

Any Tips?

Im just trying to get CM 13 to work and would like some GAPPS with that.

Thanks.
[Samsung Galaxy Nexus] Android-Andi:
You could try gapps by deltadroid http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Never had issues on tab2 with them.

~ All my work, news etc. on http://andi34.github.io ~
[Samsung Galaxy Nexus] bamtan2:
If you flash CM13 and boot it without google apps, I think it stays broken, even if you flash both again consecutively. I think you may need to delete something to fix it. Someone else can say better how to fix a broken CM13 flash, and then maybe [MENTION=2633638]Ziyan[/MENTION] can add that to the OP.
[Samsung Galaxy Nexus] hgmichna:
I believe that a factory reset, i.e. wiping data, fixes it. Also wipe the system partition, for good measure.

And flash both cm-13 and gapps together without booting in between.
[Samsung Galaxy Nexus] Regina Rainbow:
Just wanted to update this: I wasn't able to reproduce this bug after reinstalling the affected version of CM13. Thanks for testing and trying to help [MENTION=2893530]hgmichna[/MENTION] and [MENTION=6857758]Gorduza[/MENTION].

---------- Post added at 11:56 AM ---------- Previous post was at 11:54 AM ----------

I encountered that problem as well, my screen looked very dark, lifeless and dull after boot. [MENTION=4913017]typ1232[/MENTION], please try the following:

1. Go to: Settings -> Display & lights -> LiveDisplay -> Color calibration

2. Hit the Reset Button of the Calibration Tool

On my Device all three primary colors were preset to 50% after upgrading from CM12.1 to CM13, making the screen look dark an dull. (After resetting, they jumped up to 100%, the screen looked bright and readable again.)
[Samsung Galaxy Nexus] typ1232:
That was it, thanks a lot! Exactly the same problem. Colors were at 50%.
[Samsung Galaxy Nexus] YouKnowNothingJohn:
I also accidentally upgraded to CM13 without noticing it's a new version of Android. Proceeded to install TWRP 3.0.2.0, wipe everything, flash the update again, flash REPIT, flash Open GApps nano.

The phone works fine again but after a reboot I also get the "Android is upgrading - starting apps" message indefinitely. Any news on this?
[Samsung Galaxy Nexus] l.capriotti:
can you advise a meaningful filename ie a proper new partition layout?
[Samsung Galaxy Nexus] musafercom:
hello

I on latest nightly build and every thing is fine with me thanks for you all.

is it possible to install c-apps now ? if yes please a download link and steps on how to install it.

best regards
[Samsung Galaxy Nexus] Ziyan:
I'm not fully sure what causes that yet. If it won't go any further than that, and you can't get a logcat (ie. if usb debugging isn't up yet), simply hold down the power key long enough to shut down. The phone should boot fine afterwards. For some reason, everybody forgets about that little kernel feature I added more than a year ago, and does battery pulls instead :(

EDIT: I just performed an upgrade from about a week-old nightly to 0806, and it went fine - didn't stuck on the starting apps screen. Does it happen on a clean install with the 0806 nightly?
[Samsung Galaxy Nexus] MayuraDeSilva:
Didn't know about the Power Key shut down - has been pulling battery all the time :) Next time we know better. Thanks for mentioning it, [MENTION=2633638]Ziyan[/MENTION].

---------- Post added at 08:55 PM ---------- Previous post was at 08:51 PM ----------

If your partitions are on EXT4, you can use the default filename / layout: lanchon-repit-20160723-system=1.0-cache=0.0605+wipe-data=same-maguro.zip

I just have it renamed to: -system=1.0-cache=0.0605+wipe-data=same.zip

If your /data partition is formatted in F2FS, rename it to: -system=1.0-cache=0.0605+wipe-data=same+keep+f2fs.zip

Hope it answers your question :)
[Samsung Galaxy Nexus] MayuraDeSilva:
Sounds about right. Had to try and it works ;) Nice one!
[Samsung Galaxy Nexus] Gorduza:
Lockscreen "glitch"

I have came upon a minor bug regarding lockscreen.

I have gesture lock and privacy settings to see full notification, cm-13.0-20160803.

When I pull down notification panel and swipe away some notification or perform an action with some notifications, I cannot swipe up to get to unlock gesture screen, I have to tap on empty space first or pres back key and swipe up to unlock the device. has anyone encountered this behaviour?

Will update to 2016-08-09 help? I am kind of worried to perform another update, after the last one.
[Samsung Galaxy Nexus] Heart1010:
I'm on cm13 and wondering if I also have to flash gapps again right after cm13 nightly when I update my cm13? Or was it only needed once at first install?
[Samsung Galaxy Nexus] hgmichna:
Reinstall Gapps?

The Gapps for CM 13.0 are only needed once for the first installation.
[Samsung Galaxy Nexus] bamtan2:
Unfortunately no one here is likely to know the answer because they're not exactly CM13 developers. They just make CM work on our device! :) To talk about daily CM bugs, one will need to go to the CM website and deal with CM developers who make these bugs.

FYI: CM12 is probably more stable and will not see many updates. I use it for that reason.
[Samsung Galaxy Nexus] vortex-5:
Hi I think it was mentioned that F2FS support was useless on /cache so would everyone recommend to keep it ext4?

is f2fs support available on /sdcard as well?

I'm new to F2FS but I think I'm going to migrate my /data directory.
[Samsung Galaxy Nexus] bamtan2:
/cache isn't used :)

/sdcard is virtual; it's contained on /data.

And /system is changed on ROM flash to be whatever the ROM maker wants it to be.

Galaxy Nexus NAND is old and slow and known to fail. NAND in general can be preserved by leaving more of it empty (25%+) so that the controller can unload older cells, and by using it less in general (no long stressful benchmarks, and probably no encryption :)).

F2FS in theory can be good for NAND! But users have reported software incompatibilities, in particular with WhatsApp.
[Samsung Galaxy Nexus] Nautilus74:
delete audiofx and install Viper4A ! ;)
[Samsung Galaxy Nexus] MentalBreach:
Thanks for your feedback :) What about network signal drop?

- - - - -

Thanks for your feedback :) What ROM wuold you reccomend to me? Also Lollipop based (while developers fix Marsmallow bugs).
[Samsung Galaxy Nexus] massima:
i use the ZMod , it works perfectly:good:
[Samsung Galaxy Nexus] ancelin:
For now i use the official cyanogen 5.1.1 and it work well. Just be care because it is nightly so flash a working one (watch forum about it.)
[Samsung Galaxy Nexus] bandelenth:
I have to admit, it took me a moment to decide whether to try the first public build and I am really impressed, everything as of now is working just as expected! The only thing I noticed was the different color scheme, the white seems less blueish and I like that a lot. Keep up the good work!
[Samsung Galaxy Nexus] MentalBreach:
Thanks everyone for your feedback and very useful advices! :D
[Samsung Galaxy Nexus] ardeus_ua:
Great rom. Fast. One issue noticed. Cannot switch to 2g network.
[Samsung Galaxy Nexus] hot\oniel:
Gaap Problem

I had problems with the author GAAP recommended in early article. leaving the link takes me to a GAAP pre settings but the cell Maguro when flash does not accept them.

I'm making a mistake?

Please let me know thanks ............:p:
[Samsung Galaxy Nexus] momojuro:
The nano version of GApps is the one suggested and needed for the ROM. I suggest you to make again a clean flash, and to install the GApps package before the initial boot. :)

Best regards.
[Samsung Galaxy Nexus] hot\oniel:
Gapps aborted........

see what happens

I started from scratch .... all flash from home .....

please let me know......
[Samsung Galaxy Nexus] rahimali:
That error might be due to the fact that you're using CWM. Switch to TWRP and see if the error goes away...
[Samsung Galaxy Nexus] a8a999:
No data access

Battery life is better than CM 12.1. But I can't get mobile data access.

Carrier: AT&T

Cell phone: can make and receive call

Cell data: no data connection

APN: nothing

Does anyone have same problem?
[Samsung Galaxy Nexus] uji_sine:
Please try flash with twrp, i had same problem before.
[Samsung Galaxy Nexus] hot\oniel:
thank you all, and switch to TWRP and problem solved everything right .... thank a lot.

now I'm trying to make ROOT and I could not do it .....

let me know as I do ..ej Super Su, King Root? the one that works?

Regards....
[Samsung Galaxy Nexus] barrikarizki:
Enable developer settings, then you'll find the root option there
[Samsung Galaxy Nexus] uji_sine:
If you flash with trwp, you can enable in developer mode but if you flash with CWM root not activate.
[Samsung Galaxy Nexus] 3a6ygb:
I have a similar problem

Only I have Russian operator, and I do not have access to APN
[Samsung Galaxy Nexus] thagringo:
thanks for this build and the new kernel with more memory available [MENTION=2633638]Ziyan[/MENTION] !

couple of things id like to comment/ ask :

- in meminfo i see there is actually more ram available than 811, why is that ? I dont have the device with me right now but i think it says 821 MB. Just courious BTW !

- in case you are able to get up to, lets say, 850 MB free to userspace, does it really make sense to keep using zram ?

- navbar is reeeeally slow sometimes, havent noticed this with the back button but specially the home and recents button take sometime a couple of seconds to respond. Not sure if the hole system freezes or it is just the navbar ...

- is doze supposed to be working with this device? Im asking because im not sure it actually does, BBS does only show doze interactive times but no idle times at all. Deep sleep state is there as usual.

- i know there has been some tuning in CM towards bfq cgroups, is there anything special that has to be activated or tuned further ? Have only been able to find the commit where all the interfaces are created.

Im asking because i dont see any improvements in my tests, cfq actually is faster. Granted I havent tested that much, but crappy mmc maybe ? Storage is almost empty with about 75% of it available.

eagerly waiting for your next release !!!

EDIT : forgot to add -> latest greenify does not recognize the device as a MM device, and therefore all MM goodies are disabled. Dont know if this might be related to the above or is a bug in the app.

Thanks for your time !
[Samsung Galaxy Nexus] hot\oniel:
ROOT Option.......

I enable the developer settings and I can not find the option to ROOT ..

I Use as you recommended the TWRP and was a success but can not find the option ..

Please give me more location of this option ...

Best regards
[Samsung Galaxy Nexus] momojuro:
I joined a screenshot about it for you ! "Root access" option is the one which you need to change. :)

Best regards.
[Samsung Galaxy Nexus] MayuraDeSilva:
Are you using the Gesture Unlock (Xposed) module or another app?