yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ExecutorElassus:
Quick question: if this the thread where maguro users can get help with CM13 on maguro? I've been struggling getting the nightly to play nice with opengapps (Setup Wizard crashed endlessly, and then when I deleted that from the system, Google Play Services causes a SecurityException trying to use fine location permissions. Note: I did NOT install opengapps before the first boot of CM13, so perhaps this is the issue?

Thanks for the help
[Samsung Galaxy Nexus] n@vier:
Yes, you must flash both ROM and opengapps (I suggest nano) before the first boot.
[Samsung Galaxy Nexus] ExecutorElassus:
Thanks. Do I need to wipe (format) /system before doing so?
[Samsung Galaxy Nexus] hgmichna:
Flash CM 13.0 and Gapps

In my experience, yes. Once CyanogenMod has been booted without the proper Gapps, it seems to be tainted forever.

It does not hurt anyway to wipe system and flash both CM and Gapps again. You do not have to wipe data.
[Samsung Galaxy Nexus] ExecutorElassus:
Yup, that's what I did. Oddly, TWRP gave me a warning about not having an OS installed, but I booted anyway, and it seems to be booting up fine.

Wheeeeee, now I can install and configure ALL MY APPS AGAIN. This is my favorite thing.

Cheers

UPDATE: it finished booting, and then got stuck in a permanent "Unfortunately, Setup Wizard has crashed" loop. Google Play Services also is doing the same. Now that I have a clean install, how do I fix this?
[Samsung Galaxy Nexus] hgmichna:
Flash CM 13.0 and Gapps

I made a mistake in my previous message. You have to wipe data as well, after the update went wrong because of the wrong Google apps. You have to do a factory reset now.

It is probably best to wipe system, data, and the caches, and flash everything again.

Your message seems to indicate that you had already wiped data, i.e. done a factory reset. In that case I don't know what happened. I have never experienced what you have now. But now you have no choice but to do everything again.

Make sure you really have the correct Google apps: OpenGapps for ARM, Android 6.0, pico.
[Samsung Galaxy Nexus] n@vier:
[MENTION=7642483]ExecutorElassus[/MENTION]

Full wipe (dalvick, system,data and cache) then flash ROM + opengapps (pico or nano) for ARM 6.0 MM and enjoy :good:
[Samsung Galaxy Nexus] hgmichna:
OpenGapps nano does not fit

Last I read here is that nano no longer fits.
[Samsung Galaxy Nexus] n@vier:
I used nano on LP 5.1.1 why they should not fit with MM they add only hotword and search.... anyway surely pico work without any problem :good:
[Samsung Galaxy Nexus] ExecutorElassus:
pico fits with 6.0; nano does not (the CM13 install leaves about 170MB on /system, and the nano package is 176 or so). Anyway, I now went through a complete wipe (system, data, dalvik, cache), flashed the ROM, flashed opengapps, and am now booting. I'll update with results in a minute.

Cheers

UPDATE: whoooo boy, that finally worked. Man, that process got complicated after 12.1. Anyway, now I'm re-installing all my apps for real this time, without Play Services crashing every keypress. Huzzah! Thanks for the help.
[Samsung Galaxy Nexus] n@vier:
Well done ;)

Anyway nano opengapps are 146.92mb... and I think it should be fit too while micro opengapps not because are 181.5mb.
[Samsung Galaxy Nexus] vortex-5:
I've noticed an interesting problem ever since switching to 13 from 12.1

13 seems to have problems on Wifi when the wifi DTIM is set to anything other than 1. I was previously using 3-4 so that clients can sleep for longer when on power save mode but now the Galaxy Nexus can't seem to get an IP if the DTIM is anything other than 1. A DTIM of 1 which I expect is what most people run seems to work fine.

Edit: looks like a DTIM value of 2 also seems to work but any number higher causes issues.
[Samsung Galaxy Nexus] vortex-5:
Just out of curiosity:

the latest nightly 20160811 has some changes to the dexopt menu (Optimizing apps most likely)

https://review.cyanogenmod.org/#/c/153969

Can't really tell if it's just adding numbers to the total or if we will actually notice anything.
[Samsung Galaxy Nexus] Ziyan:
They totally overhauled it: https://drive.google.com/file/d/0Bw4WlD4fmC5xbGI1WFd1aXFvbzA/view amazing for our amoleds :) plus, they removed that resource intensive spinner (no joke! damn java animations), so upgrading should be a bit faster.
[Samsung Galaxy Nexus] vortex-5:
Oh thanks yeah that looks a lot better. I don't have to be afraid of upgrading anymore due to burn in! :)

FYI I was previously using a script in 12.1 to dim the screen during run during /etc/init.d

The contents are:

#!/system/bin/sh
#
# Dim LCD during boot sequence
#
#
#

echo 5 > /sys/class/backlight/s6e8aa0/brightness

I've attached a flashable zip in case anyone still wants to use it. In 13.0 however the screen returns to fullbright after the boot animation says ANDROID I'm assuming half-way through the boot animation the kernel starts controlling the brightness. Not sure if there's a reliable way to still dim the brightness during initial bootup to further reduce burn-in even with the new optimization screen which is slick btw.
[Samsung Galaxy Nexus] ilovebillgates:
your not kidding Zi !

your not kidding Zi, just flashed the 0812 nightly on one of my Gnex's and after 3 weeks of on and off "google services crashes / setup wizard crashes" using

every build before, she is running like a steam train.. which for a 5 year old device is pretty amazing ;)

love some of the new gui touches and icon updates and the boot optimization is down by about 12 mins with stock pico gapps flashed

when booting, all that glitter animation stuff really needed to go and it has..

handset is smooth as silk and this build has breathed fire into the old G-irl again !

some shots of the 0812 nightly build on first boot and optimization ;)
[Samsung Galaxy Nexus] Ziyan:
If all goes well, tomorrow's nightly (0813) will include the shiny new HexoLibre CM theme, available from the theme chooser :) there should be still more than enough free space left for pico gapps.
[Samsung Galaxy Nexus] ilovebillgates:
cool Zi, saw that on the manifest, so that will def add to the aesthetics of an already excellent and rock steady rom ;)
[Samsung Galaxy Nexus] ExecutorElassus:
Question: do you need to keep flashing opengapps into the recovery, or can they update from the Play store?

Also, my camera keeps crashing, and the flashlight tile won't show up on the pulldown menu (but is there when I select "edit tiles" to move them around). Also, the barcode scanner app (which is probably related to the camera) also crashes every time. Are these known bugs?

Cheers
[Samsung Galaxy Nexus] MayuraDeSilva:
Is it this same theme or a new one?

[IMG="COS13: Hexo"]https://lh4.googleusercontent.com/-CQZZ9Vvvc3k/Vw6M0zwoNnI/AAAAAAAAUh8/qoCInjrxaY0U9qEOWZOla3enfQhUHU1RgCL0B/w572-h509-no/13.04.16%2B-%2B1[/IMG]

---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------

They can be updated from the Play Store.
[Samsung Galaxy Nexus] LeoHart:
It seems some people have issue with the cam. Me too.

But I noticed the cam is working again for a while, after a device restart.

Maybe it helps you.
[Samsung Galaxy Nexus] jirkadus:
Anyone is having problems with Gmail or Inbox? Inbox just tells me something went wrong after I select the account to login and gmail says "Unknown issue with google play services". But I have no problem with play store or google calendar. Weird. I tried remove and add google account, wipe the inbox data & cache. Nothing helped.
[Samsung Galaxy Nexus] YouKnowNothingJohn:
When upgrading to 0813 from 0806 yesterday I lost the play store. This is strange since I performed a complete wipe and fresh install with 6.0.1, including REPIT and gapps nano.

Everything worked fine but after installing the latest nightly yesterday I lost the play store and get the play services error messages.

I added these items to the 50-cm.sh script in system/addon.d:

rm -rf /system/priv-app/AudioFX

rm -rf /system/priv-app/CMBugReport

rm -rf /system/priv-app/CyanogenSetupWizard

rm -rf /system/priv-app/Mms

rm -rf /system/priv-app/Tag

rm -rf /system/priv-app/ThemeChooser

rm -rf /system/priv-app/ThemesProvider

rm -rf /system/priv-app/VpnDialogs

rm -rf /system/app/BasicDreams

rm -rf /system/app/Browser

rm -rf /system/app/Calendar

rm -rf /system/app/DeskClock

rm -rf /system/app/Eleven

rm -rf /system/app/Email

rm -rf /system/app/Exchange2

rm -rf /system/app/Galaxy4

rm -rf /system/app/HTMLViewer

rm -rf /system/app/HoloSpiralWallpaper

rm -rf /system/app/LatinIME

rm -rf /system/app/LiveWallpapers

rm -rf /system/app/LiveWallpapersPicker

rm -rf /system/app/LockClock

rm -rf /system/app/NoiseField

rm -rf /system/app/PhaseBeam

rm -rf /system/app/PhotoPhase

rm -rf /system/app/PhotoTable

rm -rf /system/app/Terminal

rm -rf /system/app/VisualizationWallpapers

Might this be the cause? And can I just flash the latest open gapps again or do I need to reflash the nightly also to make sure the permissions are set correctly as it was with the upgrade from Android 5 to 6?

edit:

I think I found out what the problem is. After a reflash the file system is the stock size and you need to run the following in TWRP to fix it:

click Wipe

click Advanced Wipe

select System

click Repair or Change File System

click Resize File System

I just did this and reflashed the gapps nano and I'm going to check if it fixed my problem.

edit2:

Unfortunately this did not fix my problem. I keep getting play service errors no matter what I try. I'm now wiping everything and flashing the rom, repit and gapps again.

edit3:

A factory reset seems to have done the trick but I'm not happy having to set up all of my apps again. Is there a safe way to upgrade when using repit??
[Samsung Galaxy Nexus] MayuraDeSilva:
Haven't had such a problem with upgrades.

Since my /system exceeds 643MB with GApps installed, and as /system reverts back to 643MB again upon reflash of CM13 update, I had to flash GApps eveytime I upgrade though.

With REPIT, I've been using the Resize File System option in every upgrade to resize the /system partition to repartitioned size. Unless the ROM doesn't do it automatically upon reflash, we have to use Resize File System option everytime.

This is what I have been doing:

1. Flash CM13 update

2. Resize File System (REPIT again if it fails)

3. Flash OpenGApps (Updates from Play Store will remain after booting up)

4. Wipe Cache

PS: Still on 2016-08-06 NIGHTLY
[Samsung Galaxy Nexus] YouKnowNothingJohn:
Yes this is what I have found out as well. I got my phone working properly again, fortunately. There is an option in TWRP for the resize as well. Next time I will use that after a reflash.

Do you know if it is necessary to reflash the gapps as well or should the resize suffice after a ROM update?
[Samsung Galaxy Nexus] MayuraDeSilva:
I found that if /system partition only used less than 643MB with GApps installed, I don't have to reflash GApps again.

Now mine uses 672MB and has to reflash GApps with every update. Unless it will end up in a bootloop or errors.

It all goes smoothly and preserve all the updates to GApps too. Hence I don't mind the extra step :)
[Samsung Galaxy Nexus] bamtan2:
It looks like the opengapps flash didn't work, you didn't notice, you rebooted into android, and then android 6 is broken forever if it's booted without gapps.

I hope everyone sees your post, because you're not alone. Many others have unknowingly ruined their system due to this and similar problems. I wish this didn't have to happen to you. Sorry ;(

You have provided lots of good data as a tester of bigger partition sizes, etc. But if you're done with that testing, you can switch to a more stable system: the same ROM, using the very smallest opengapps! :) Also, CM12.1 is quite stable too, and it does not explode when something goes wrong with gapps.

Thank you again for your posts (and tests) :)
[Samsung Galaxy Nexus] YouKnowNothingJohn:
Well actually I didn't flash opengapps at all after the update. Since I'm used to just flashing the new ROM and have everything working, I did exactly that. I didn't realise that by using REPIT you need to resize /system/ and reflash opengapps with each update. And yes, this resulted in a boot without gapps because they did not fit anymore...

I'm not sure what the differences are between gapps nano and pico but nano is what I used with android 5 so that's why I figured I can use REPIT to be able to install the same gapps version. It's definitely a hassle but at least I know what the problem is now.
[Samsung Galaxy Nexus] musical_chairs:
That makes sense, actually. You increased your /system partition size with repit, and flashed a larger gapps package. When you flash a ROM upgrade, it backs up your gapps like normal, flashes the ROM, and then tries to restore your gapps. But since the system partition is now smaller due to flashing the ROM, it runs out of space when trying to restore the gapps, leaving things in a broken state. To deal with this, you need to resize the file system, then re-flash the gapps. If you forget, and reboot immediately after flashing the ROM, you get all those nasty google play services errors.

If the ROM flash could resize the partition before restoring the gapps, that would solve this problem. But unless that feature is added, you will always need to flash gapps every time after flashing a ROM update if you are using a bigger system partition and larger gapps.
[Samsung Galaxy Nexus] MayuraDeSilva:
Absolutely! Had no idea the first time, but that's one way to learn. As /system defaults to 643MB, it leaves no space. Since then I've been flashing GApps (Stock customized) everytime and it works.

This is even before Nighlies and then requested [MENTION=2633638]Ziyan[/MENTION] if he could integrate the resize script in the ROM. May be it's out of the line to include custom scripts. Or it will be in a future release :)
[Samsung Galaxy Nexus] bamtan2:
I'm not sure, but I think the only thing in nano that you can't install from the app store is the face unlock: https://github.com/opengapps/opengapps/wiki/Package-Comparison

That's why I'm happy using the smallest package. Because it doesn't make a difference for me! ;)
[Samsung Galaxy Nexus] iPlasm:
Thanks very much Ziyan! :) , I've tried before your Unofficial CyanogenMod 13 ROMs with the official ROM, the 13th august ROM was the perfect update till now, it's even faster then 12th august Rom! I wiped all partitions for each new ROMs installation.

I really liked the new theme Hexo, beside I prefer light settings :p more like to be iOS :)

Waiting for Snapshot release for Maguro!
[Samsung Galaxy Nexus] osm0sis:
It's something that should be included in the ROM zip, since that's how it's done on other devices with resized system partitions. He's got a rough version included in the OMAP-AOSP ROM zip, and of course Omni isn't afflicted because it (smartly) sticks with file-based zips instead of block image writing.

In the mean time it wouldn't be too hard to write an addon.d script that comes before the GApps one and resizes system as part of the restore. :good:
[Samsung Galaxy Nexus] MayuraDeSilva:
Awesome! Then we can hope it will come to future CM13 builds too :) Thanks, [MENTION=4544860]osm0sis[/MENTION] :good:
[Samsung Galaxy Nexus] Mimamau:
I am still on 20160510. Whenever I try to dial a number, the phone just reboots. After the reboot it says no sim card.

Though mobile data works. But when I receive a call it also just reboots.
[Samsung Galaxy Nexus] hgmichna:
Defect in 20160510

So 20160510 has a bug. But we have August now, so why is that of any interest?
[Samsung Galaxy Nexus] osm0sis:
Does this work? :cowboy:

/system/addon.d/00-resizesystem.sh:

#!/sbin/sh
#
# /system/addon.d/00-resizesystem.sh
# For devices that have a repartitioned /system.
#
# During an upgrade, this script resizes the system partition to re-accomodate
# larger GApps on system.dat ROM zips that don't include this functionality.
#
# osm0sis @ xda-developers

. /tmp/backuptool.functions

# determine the location of the emmc system partition
if [ -e /dev/block/platform/*/by-name/system ]; then
block=/dev/block/platform/*/by-name/system;
elif [ -e /dev/block/platform/*/*/by-name/system ]; then
block=/dev/block/platform/*/*/by-name/system;
fi;

# force expansion of the path so we can use it
block=`echo -n $block`;

case "$1" in
backup)
# Stub
;;
restore)
# Stub
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# force check and resize /system partition
if [ -e "$block" ]; then
umount /system;
e2fsck -yf $block;
resize2fs $block;
mount /system;
fi;
;;
post-restore)
# Stub
;;
esac;

Direct Download (Save As, then rename from .txt to .sh)

Set 755 (rwxr-xr-x) permissions.
[Samsung Galaxy Nexus] ar2klaps:
Google play and google play services not working on my nexus maguro after upgrading to the latest version.
[Samsung Galaxy Nexus] bamtan2:
There is a defect in cyanogenmod which allows CM12 users to automatically upgrade to CM13, which then destroys their system. Unfortunately this happened to many people in this thread. It's time we do something about it [MENTION=2633638]Ziyan[/MENTION]! ;( The updater must be disabled somehow.
[Samsung Galaxy Nexus] quantan:
Hi. Snapshot build ZNH5Y is rolling out and our maguro is one of the supported devices. Glad to see it. But I cannot find the build on Downloads page of maguro. Does anyone know where to download it :D
[Samsung Galaxy Nexus] axlu:
Bugs?

Hi. I have had to take my phone to serious repair (new firmware) but now I am back. I have installed cm.13.01-0815. It was impossible to reinstall SuperSU and the TWRP Manager, because I couldn't update the Binary files and the phone was suddenly unrooted . I managed to make a root with Nexus toolkit. Other toolkit couldn't work under 6.0. So now I am back to 12.1 for a while. But I will be back after rehearsal of my skills:). Anyway, thanks for all the efforts with 6.01.

axlu
[Samsung Galaxy Nexus] Gorduza:
I am not sure what type do I use. It is the stock gesture unlock that comes with CM13. I am not using another app.
[Samsung Galaxy Nexus] quantan:
Finally Snapshot build is available for maguro. Thank you so much for your work, [MENTION=2633638]Ziyan[/MENTION] :D
[Samsung Galaxy Nexus] hgmichna:
CyanogenMod contains root functionality

CyanogenMod already contains root functionality. You just have to enable it in the developer options. SuperSU is not needed (although some users install it because they prefer it).

---------- Post added at 06:00 PM ---------- Previous post was at 05:46 PM ----------

Great!

I still do not see a snapshot in the auto-updater, only nightlies. Do I have to change a setting? Or will they magically appear?
[Samsung Galaxy Nexus] quantan:
I'm not sure whether the snapshot can be installed via auto-updater or not. I come from another ROM and just decide to fresh install it.
[Samsung Galaxy Nexus] Fetznschaedl:
Concerning to new snapshot build: Everyone remember that this snapshot was branched from the nightlies on Aug 1st. That means if you currently run a nightly build of Aug 1st or newer you cannot dirty flash the snapshot and you have to make a clean install. You can only flash the snapshot on nightlies of Jul 31st or older.
[Samsung Galaxy Nexus] georgedorn:
I can' t get CM13 to work on my Maguro. I tried varius nightlies. I tried the snapshot released today.

Procedure always the same:

TWRP 3.0

Wipe everything with Advanced Wipe (data, system, cache), can' t do a cleaner install I suppose.

Install cm13 zip

Add more zips

Added Open Gapps Pico

So ROM an Gapps gets flashed together before the first boot

Installation is fine, boot is fine

Result in setup screen always the same:

Unfortunately Google Play services has stopped.

Can't add a google account as every Google service stops

Factory reset via settings

Reboot

Same thing again.

I'm running out of ideas here.
[Samsung Galaxy Nexus] GerardJ:
cm-13.0-20160816-SNAPSHOT???

I'm a bit at a loss. I have cm-12.1-20160719-SNAPSHOT.YOG7DAO8DL-maguro.zip installed on my Nexus. Working fine.

Today I received an invitation to update to cm-13.0-20160816-SNAPSHOT.ZNH5YA0FE-maguro.zip.

Earlier on, I tried to install a NIGHTLY, but encountered problems with the installation of gapps. Reading the various reactions, I do understand that a problem with memory partition needs to be resolved by running a special script. Correct? This is something beyond my capabilities. Luckily, when I encountered the problem, I could re-install a fairly recent back-up. So my question is whether the memory issue has been resolved. In other words, is it safe to update to cm-13.0-20160816 SNAPSHOT?
[Samsung Galaxy Nexus] bamtan2:
CM12 and CM13 are not really compatible. CyanogenMod updater is destroying the system of everyone uses it.

This is a big problem and I don't know how to fix it ;(
[Samsung Galaxy Nexus] Android-Andi:
Anyone tried gapps by deltadroid?

https://www.androidfilehost.com/?fid=24591000424951861

"The base gapps packages contain only the required core Google applications, framework and libraries (Google Play Services, Calendar Sync, Contacts Sync, Facelock, and Google Play Store)."

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Maybe worth trying it (small enough for tuna?), never had issue with those on tab2 while a lot of people have issues with opengapps.

~ All my work, news etc. on http://andi34.github.io ~
[Samsung Galaxy Nexus] Ziyan:
This is isn't my decision; the CM team decided that they don't care about GApps, and that people who use it should take care of them on their own. So yeah, if you update from 12.1 to 13.0, you need to be extremely careful to install a 13.0 compatible GApps package *before* booting into it the first time, and make sure that the permissions are correct.

You probably need to follow this post. What's really concerning me is the "Add more zips". Did you happen to remove the CM setup wizard? That's known to cause such issues, as it's supposed to grant permissions to GApps!
[Samsung Galaxy Nexus] MayuraDeSilva:
Placed your script in /system/addon.d via File Manager (TWRP) and dirty flashed the latest nightly - cm-13.0-20160815-NIGHTLY-maguro.zip

It worked :good: It did! :laugh:

System partition preserved the resized partition size and still Used = 671 MB ;) Rebooted to the system and existing GApps are intact too.

Only one issue though - I had Sound Recorder system app removed with GApps installation, and it was making a comeback this time. But not other removed apps such as HexoLibre (Will give it a go again)

Anyway, the mystery has been solved ;) Thank you, [MENTION=4544860]osm0sis[/MENTION]. No more flashing GApps with updates. This is a great addition for us using [MENTION=4141005]Lanchon[/MENTION]'s REPIT :good:

UPDATE:

Did it all over again.

1st Time: Wiped the /system and installed CM13 (Resize File System) and GApps / Xposed (Sorry - Can't go for a Clean flash right now)

2nd Time: Placed the script and dirty flashed CM13 update (and Xposed).

This time Sound Recorder or any other removed system apps didn't show up :)

Thanks again, [MENTION=4544860]osm0sis[/MENTION] and [MENTION=2633638]Ziyan[/MENTION] for these elegant and snappy builds. Latest NIGHTLY is pretty solid.

Hope this script will be included in upcoming builds too.

---------- Post added at 01:51 AM ---------- Previous post was at 01:49 AM ----------

This was annoying when I wanted to try CM13 first time too.

If it's possible, try flashing the last Stock firmware for Galaxy Nexus (Android 4.3) and install CM13 again using TWRP 3.0.2-0

Haven't had a single "Unfortunately, Google Play services has stopped." message ever since :)

Hope it helps.

---------- Post added at 02:07 AM ---------- Previous post was at 01:51 AM ----------

Interesting! Can you mention the steps to activate Gesture Unlock? So I can try to replicate it on mine too. I can't find such option on mine in Lock Screen > Screen Lock settings.