yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] hgmichna:
Upgrade and keep data

In theory, yes, but you will have to try. Nobody will be able to give a guarantee.

But why don't you try it? If it fails, you will have to wipe data, i.e. do a factory reset, anyway. It cannot hurt to do a backup, for example with Titanium Backup.

Don't forget to also install matching Google apps before you boot into CyanogenMod 13!
[Samsung Galaxy Nexus] bamtan2:
Nope! :)
[Samsung Galaxy Nexus] MayuraDeSilva:
Didn't work for me. Proceed with caution.

As [MENTION=2893530]hgmichna[/MENTION] mentioned, have a backup before you try.

I had my apps and important system data backed up with TitaniumBackup. Hence I could restore them after a clean CM13 install :)

Good Luck!
[Samsung Galaxy Nexus] resquedaz:
Hi guys,,,, I really need your help, my mobile data is not working, i set the apn and got nothing,, love this rom hopefully you can helpme thanks a lot in advance!!!!!!!!!!!!!
[Samsung Galaxy Nexus] vortex-5:
A few things to check

1. remove all apn's and input them manually (sometimes these are not exactly correct).

2. If your on the canadian rogers network they apparently have an issue with auto detect ipv4 ipv6 so set it to ipv4 and it works.

3. sometimes there's a strange issue it's rare but it that requires you to remove /data/data/com.android.providers.telephony/databases/telephony.db and telephony.db-journal and disable /system/etc/apns-conf.xml. Then you can create the apn's manually after doing a reset. This should be very rare also you should backup before doing this modification. If you are seeing com.android.phone crash all the time this is a good bet that you need to apply this.
[Samsung Galaxy Nexus] Gorduza:
First thoughts on recent update.

After installing update CM13 20160829 through Cyanogen Update, it optimized "all" apps and carried on, but the system was very laggy. I have performed another restart and another 9 apps wehe optimized. The UI still feels a little bit laggy, but not as much.
[Samsung Galaxy Nexus] vortex-5:
I have noticed the system seems to be taking up more ram than before that maybe a cause?

Before I was hovering around 432MB after boot processes have started after 20160829 I noticed the available ram in developer options running processes was 360MB
[Samsung Galaxy Nexus] vortex-5:
I just tried 20160830 and I'm getting a bootloop (system stuck at boot animation)

The system did successfully boot once and do the "optimizing apps" process but after which it failed to startup and got stuck at the boot animation.

Can anyone confirm?

I restored from backup to 20160829 and everything is fine now.
[Samsung Galaxy Nexus] alex_ee:
I normally download and install the 20160830. All is ok, but camera again crashed and keyboard (AOSP) in Hangouts slow, freezes, although in other messengers all is ok
[Samsung Galaxy Nexus] vortex-5:
Cool thanks must be something I'm doing on my end then.
[Samsung Galaxy Nexus] alex_ee:
every time before flashing new CM, I'm doing "Wipe Dalvic cache' and then install .zip in CWM 6.0.4.7.

I hope to help you.
[Samsung Galaxy Nexus] vortex-5:
Oh I got it working it wasn't a dalvik cache issue it was more a context issue. I don't have a logcat from the bootloop I should've taken one. And I'm on TWRP-3.0.2-0 like Zyrian
[Samsung Galaxy Nexus] resquedaz:
I did the firts option and it work, thanks a lot guys and thankyou for your hard work
[Samsung Galaxy Nexus] alex_ee:
the next music track by double-click the headphones

many thanks! Now it works! :D
[Samsung Galaxy Nexus] axlu:
I have updated to 0830 using the update function (TWRP) on the phone, very smooth and nice, camera works again. Battery charging has become rather slow and works best when phone is closed. I have stopped battery apps, because the phone overheated.

I have not found a solution to read memory from the SD slot. Any suggestions? And thanks again for the excellent work on our old Nexus phone.
[Samsung Galaxy Nexus] hgmichna:
SD slot?

How many SD slots does your Galaxy Nexus have?

---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------

Does everybody here see only nightlies in the CM updater (Settings, About phone, CyanogenMod updates)? What is wrong?
[Samsung Galaxy Nexus] MayuraDeSilva:
Two Camera Apps

Just updated (dirty flash) to latest 09 / 01 build from 08 / 20 and ended up with two Camera apps - Google Camera and Snap.

Probably, now Stock camera uses a different package name I think.

PS: Removed Snap with OpenGApps Universal App Removal - (Snap)
[Samsung Galaxy Nexus] vortex-5:
Just an FYI for everyone that was having DHCP problem it's now patched in 20160901 you no longer have to use legacy DHCP when connecting.
[Samsung Galaxy Nexus] Regina Rainbow:
camera connection bug reproduced on Galaxy S III and Nexus 4 - CM Problem?

The traces have always been empty unluckily.

I've got the suspicion, that this bug might not be tuna/ducati specific, but a more general CM problem. Today I got my hands on my colleague's Galaxy S III (GT-i9300) with CM 13 installed. I tried to trigger the "Connection Bug" as described by [MENTION=7643454]jango0[/MENTION] in Post 655. And: Bingo! Snap froze, couldn't connect to camera. Afterwards camera was gone as it is on my Maguro when the connection has failed once. I was able to secure traces and the corresponding tombstone of the crash/connection error. They look quite similar to the errors in my maguros logs, except in this case ducati (and CMA) is not involved due to hardware differences of course...

Update 1: Meanwhile I was able to reproduce this on a Nexus 4 with CM 13 (Snapshot) as well [see appended tombstone]. Going to file a bug on cm jira tomorrow.

Update 2: Bug has been filed on jira. Anyone affected by the bug and registered on jira might vote for the issue to give it some gravity.

Update 3: Bug has been closed on formal grounds, I'm out of ideas. Maybe someone else with CM 13 snapshot installed can jump in producing the necessary logs for the CYAN-Tracker?

Update 4: Installed CM 13 Snapshot, reproduced the bug and refiled it on CYAN-Tracker.

[MENTION=2633638]Ziyan[/MENTION]: Do you see a better chance to find the root of this problem by comparing the logs of Galaxy Nexus [as send via PM] and Galaxy SIII/Nexus 4 [as appended]? Since they are based on different hardware and ducati or CMA can be ruled out on the S III/Nexus 4, maybe the root problem could be found in what the error logs of these devices have in common?
[Samsung Galaxy Nexus] Ishn90:
tx for the tip. same encountered here.
[Samsung Galaxy Nexus] uji_sine:
I'm tested rom on omap4 aosp thread, rom work nicely but only gps not worked. I'm hope to see cm14 on our maguro in soon. Thank ziyan, mwisbest and team.
[Samsung Galaxy Nexus] roachie54:
Root access not working

Flashed the most recent snapshot (20/08) & it's great but root access isn't working (have enabled it in developer options). Flashed from CWM 6.0.4.3 with Pico Gapps after wiping /data, /cache, /system. Previously no problems with root in CM 12 or stock 4.x, any ideas where I'm going wrong? Have to say it's great to see Android 6 running so well on a 5 year old phone that I still use every day!
[Samsung Galaxy Nexus] YouKnowNothingJohn:
Thank you so much! Just used this and didn't have to reflash opengapps!
[Samsung Galaxy Nexus] mukesh:
Do we need to change the permissions?
[Samsung Galaxy Nexus] YouKnowNothingJohn:
Yes to 755 I believe!
[Samsung Galaxy Nexus] mukesh:
Do we need to change the permissions of the file?
[Samsung Galaxy Nexus] :
Please read the thread directly above yours, lol
[Samsung Galaxy Nexus] agungbudip:
hi guys, i need help

I just installed cyanogenmod 13 yesterday

if i use my mobile data, I could only browse a page that has SSL (https)

if I browse a page that does not have ssl (http), always return ERR_CONNECTION_RESET

i use default browser and google chrome, all return the same thing

but if i use my phone as portable hotspot and my laptop connect to it all running normally, i can browse http/https page
[Samsung Galaxy Nexus] darkcompanion:
LWP

I installed the snapshot of Aug 20th onto my maguro. Works smooth and stable, great work !

I know from the FAQ that live wallpapers have been removed from the image, but downloading any LWP (Muzei, Tapet,...) gives me a 'your device isn't compatible' error message. However, LiveWallpaperPicker app seems installed. I manage to download 500 Firepaper, but that gives an error when trying to activate. Anyone else encountered the same problem ?

There's no entry for maguro on cmxlog, so I don't know if any of the subsequent nightlies have this fixed ?
[Samsung Galaxy Nexus] nikodr:
Ι had installed the cm 13 and managed to install live wallpaper. You need to root and mount system.

You install needed apk and live wall paper will work. Though you need to make sure you have some space on system. And if not maybe delete some not needed apks.
[Samsung Galaxy Nexus] Regina Rainbow:
May I ask you some questions?

1. Did you perform a clean install or an upgrade from 12.1?

2. In case of a clean install: which partitions did you wipe?

3. What Is the outcome of the following test for you?:

Go to home screen

Open the app-drawer

Start camera app (snap)

After snap has started, change from photo mode to video mode frequently and rapidly (about 5-10 times)

Does snap crash, leaving the camera in a broken state ("Can't connect to camera") or can you just restart snap (or any other app that relies on camera)?

In fact, I would be interested in feedback to the above questions by anyone, who is still affected by the camera bug.
[Samsung Galaxy Nexus] alex_ee:
1. Clean install

2. Wipe Dalvik cache, wipe data, wipe cache

The camera rarely works ("Can't connect to camera"), reboot phone often helps.

the same thing with a flashlight

*Using last CM13 (04/09/2016)
[Samsung Galaxy Nexus] MayuraDeSilva:
Using Mobile Data here too, but had no such a problem. What CM13 build did you install?
[Samsung Galaxy Nexus] LeoHart:
At first I tried to flash CM13 over CM12.1 but it caused problems with gapps.

Second time I flashed with a fullwipe. But unfortunately I had a huge bug with GPS and the whole system was not more usable so I had to flash and wipe again.

Full wipe with TWRP

I never tried to trigger because the issue with the camera occurs very quickly. I always know if I need the cam I must restart the device. Same with the YouTube App, I use the app only for search proposes and send the video-link to Firefox to play it.

This is a little bit strange. The playback function in firefox is always working independently from the system.

Camera and YouTube App stays broken until a device restart

edit

Nope, I can't trigger the issue. After the fifth switch Snap crashes but I can start the App again and the camera is still working.
[Samsung Galaxy Nexus] alex_ee:
camera works!

strange, but almost as a day on my GN camera and flashlight are working without interruptions!

I will check on...

*Using last CM13 (05/09/2016)
[Samsung Galaxy Nexus] garrymar:
Updated to 05092016. Still there are problems with flashlight in locked state.
[Samsung Galaxy Nexus] LeoHart:
[MENTION=6495692]garrymar[/MENTION]

What do you mean with locked state?

Because this is a different issue:
[Samsung Galaxy Nexus] alex_ee:
after successive launch of a large number of applications, followed by the release of them - the camera refused to run again, as well as a flashlight.

updated to 06/09/2016 - the same bug.
[Samsung Galaxy Nexus] alex_ee:
CM news?

where can I find the differences nightly builds? there almost every day, and that there is under the hood of the new unknown.

where he is the actual repository from which gather nightly builds? Because the one that is specified at the beginning of this branch and on device wiki page on the date of the last modification - is outdated.
[Samsung Galaxy Nexus] Ziyan:
Just added a link to the OP as well :) https://www.cmxlog.com/13/maguro/
[Samsung Galaxy Nexus] GerardJ:
Updated to cm 13.0 just now

Updated today from cm 12.1 to cm 13.0

(Flashed cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J5-maguro.zip together with open_gapps-arm-6.0-pico)

Sofar, everything is working fine.

The reason why I preferred the SNAPSHOT version rather than a more recent NIGHTLY is, that - to my knowledge - I always have to flash the update together with the open-gapps. It took a while to re-install the 'missing' apps. Therefore I want to avoid the need to do that everytime when I update to a more recent NIGHTLY. Or am I wrong? And is it possible to update without the need to re-install the other installed apps once cm-13.0 is installed? (SNAPSHOT or NIGHTLY).
[Samsung Galaxy Nexus] garrymar:
I mean the same problem described by Ziyan.
[Samsung Galaxy Nexus] Regina Rainbow:
Thanks for answering. [MENTION=7143784]LeoHart[/MENTION]: OK, that's just what happens on my phone. [MENTION=7673061]alex_ee[/MENTION]: After a fresh reboot, can you trigger the "can't connect bug" with the described test case or is just snap crashing? Would be interesting to know ...
[Samsung Galaxy Nexus] case-sensitive:
how to skip initial sign in

I just flashed the Sept-10 built on my gnex, coming from the August built of AOSP. I flashed manually through TWRP, with pico open gapps + superSU 2.78 + xposed + adaway systemless zip. After the flashed was completed and gnex rebooted itself, it asked for wifi connect, which I skiped, and then complained that the sim card was missing, which is true; I used gnex strictly as a wifi device with no sim card. When I hit `skip' it brought me back to the missing sim screen.

Q: How can I setup my gnex + cm13 without any network/sim? I would like to setup adblock/xposed etc before I connect to the web. I have never had this problem setting up CM on any other devices.

THANKS!
[Samsung Galaxy Nexus] alex_ee:
immediately after the reboot, the camera and flashlight run without problems, but after some time (in different ways, sometimes 5 minutes, sometimes 12 hours) once again fails to unavailability of the camera - and the camera and flashlight not work.
[Samsung Galaxy Nexus] sup123:
A humble request to help me out with my issue

Hey there. I have a galaxy nexus i19250 maguro device.

was running on 4.3 jellybean and recently updated to lollipop using the snapshot cm 12.1 ROM... Everything went fine during the process but..... once the device restarted,, there's this text of "No SIM detected, Emergency Calls only" and there's no cellular network detected.

similar thing happens when I try to install cm 13 too... I wonder if my device does that for every custom ROM.... it seems so to me...

I did try rebooting the device, taking out the sim and reinserting it... nothing worked. So I tried restoring the earlier backup and the cellular network was back........

I look forward to use the lollipop version.. if only someone could help me with the issue mentioned above......................
[Samsung Galaxy Nexus] axlu:
I have installed TWRP Recovery which updates through the update function under Settings. My most used apps are updated (if necessary) every time I am activating the update process. I am using the NIGHTLY.
[Samsung Galaxy Nexus] GerardJ:
Thanks for your reply. From reading it, it appears that you download and update when a new NIGHTLY is shown available. The update process then also updates the installed apps. Correct?

I was worried that I have to follow the more elaborate procedure with each new NIGHTLY:

- I have TWRP 3.0.2-0 installed plus the TWRP Manager app

- activate developers options with Advanced restart, Root access for Apps and ADB, ADB debug interface selected

- connect to pc and place the new NIGHTLY and the Open gapps on the \SDCARD

- start the TWRP app and select Reboot, then Reboot to Recovery

- Wipe, then Install

- (and then re-install apps that were not installed with the Open gapps pico.zip)
[Samsung Galaxy Nexus] hgmichna:
Installed apps are not updated during the Android update. They are only "optimized", which probably means recompiled.
[Samsung Galaxy Nexus] GerardJ:
OK; meanwhile I've updated my Nexus to the latest NIGHTLY without problems. Thanks for your advice!
[Samsung Galaxy Nexus] Nowhite:
Galaxy Nexus will be update to CyanogenMod 14?
[Samsung Galaxy Nexus] netreign:
someone will tell me how much RAM is available .... no more than 50 MB to me
[Samsung Galaxy Nexus] mukesh:
Yes, follow the thread at

http://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574/page70
[Samsung Galaxy Nexus] Ivo Stehlík:
AOSP is not CM 14
[Samsung Galaxy Nexus] bamtan2:
Also note that with Cyanogen Inc having business trouble, CM14 may not be as substantial as previous versions were. Volunteers may move to other projects, etc. http://www.androidpolice.com/2016/0...olvement-from-cyanogen-inc-on-cyanogenmod-14/

The most important part is having a working AOSP! :) And we have our local maintainers to thank for that :)
[Samsung Galaxy Nexus] mukesh:
AOSP is an indicator that we are likely to get CM 14 too.
[Samsung Galaxy Nexus] breversa:
Galaxy Nexus getting sluggish and choppy

Hi,

Anyone else experiencing their phone getting sluggish and choppy as hell progressively after one-two weeks of initially awesome fluidity ? The main giveaway that something is really going wrong is that even "please wait" animations (those spinny circles when loading Gmail, for instance) are VERY choppy : it's not that a task is going slowly, it's the phone that can't even show it's going slowly !

I'm having a very hard time pinpointing whether it's caused by a process hogging the CPU (by the time I can start a CPU monitor, it's too late ; I'd need a full-time logging app), an I/O problem (could my storage chip be damaged/used ? fstrim helps a bit but really not enough), or… I don't know what.

Any idea ?

(Of course, I tried clean wipe/repair partitions/reinstall, to no avail)
[Samsung Galaxy Nexus] gabrielex:
I am experiencing the same lagginess breversa is reporting (in case you were asking, no I don't have the facebook app installed).

In addition I often get green artifacts around videos.

Trying using Google cardboard camera crashes the app as soon as I start moving the phone to capture a picture.

Sometimes I also get reboots or the system totally hangs so I'm forced to remove the battery and turn it back on.
[Samsung Galaxy Nexus] WoolTomb:
I have a similiar problem. It started since i had zMod 5.1.1 and after i flashed (clean flash) CM 13 but the problem was still there. my GNexus has a lot of lags and sometimes it reboots itself and it blocks on Google logo so i need to remove the battery and then restart the smatphone. My CPU usage is normal and the Ram usage too.

I think that the only way is to perform a factory reset and then reflesh the Rom, but i have no time to try it :(

My last chance is to wait CM 14 and hope it will run better......
[Samsung Galaxy Nexus] nameless--:
Sorry to hear that guys, but my gnex is running fine since I flashed the CM13, it was about 4 weeks ago but I dont have the GApps installed. Maybe its just my impression but I think that google play services is a RAM and battery hog. Every past rom that I flashed with GApps would not run as smooth as without it after a couple of days...

btw, the inversed colors on acessibility menu isnt working, I need it to "heal" some burns on my screen after almost 5 years of joy with this little one

Anyone have a clue how to solve it or it is a problem with the build? Can anyone confirm that for me? Thanks!
[Samsung Galaxy Nexus] WoolTomb:
There are kernels for CM 13???
[Samsung Galaxy Nexus] morfances:
edit...sorry
[Samsung Galaxy Nexus] WoolTomb:
Why?
[Samsung Galaxy Nexus] morfances:
I do not know kernel to 13 cm ... I was confused with another device
[Samsung Galaxy Nexus] uji_sine:
GPS not work on 9/28/16

Any one have problem same with me, please help to confirm.
[Samsung Galaxy Nexus] wilkinator87:
since i flashed this(tried both the snapshot and the nightly version), i have no usb connectivity and my phone wont charge while turned on. phone will charge when powered down. any ideas?
[Samsung Galaxy Nexus] runekock:
It might be dirt or a bad cable or connector that prevent some of the signals from getting through. It is possible that just the power lines will work when the phone is off, but that it needs the data lines when on. Just a theory.
[Samsung Galaxy Nexus] stephendt0:
Is the lag an ongoing issue? I'd like to pass on my Gnex to my Aunty... But not if it's unusably slow since she lives 6 hours away :/
[Samsung Galaxy Nexus] robrtpit:
Bluetooth Issues

Thanks in advance for your continued support of this device!

Does anybody else have Bluetooth Playback Issues since moving to this Rom from CM 12.1 like I do? I have already created a Bug Report(jira.cyanogenmod.org/browse/NIGHTLIES-3387) for this Issue because I haven´t found any other Mentions of this Bug.

Is there an easy option to enable dexpreopt or do I have to recompile the whole ROM to get it working since I have already enlarged my system partition and switch my data to F2FS using repit?
[Samsung Galaxy Nexus] uji_sine:
Last update 10/1/16 gps work fine, thank you developer team.
[Samsung Galaxy Nexus] breversa:
As someone mentioned earlier, not everyone has lag issues, and apparently, devices without Google Apps (I use OpenGApps pico with extra removed components and full Privacy Guard) seem to suffer less.

You might want to try a GApps-less installation, and maybe give microG/Blank Store a try if you think your aunt needs access to the Play Store.

Otherwise, F-Droid.org is the place to go. :)
[Samsung Galaxy Nexus] stephendt0:
Yeah I don't think my 65 year old aunty will be able to handle not having Gapps... I'm using Open Gapps Pico, haven't noticed any major issues just yet. Just didn't really want her using stock due to security issues and what-not (not to mention jelly bean is pretty old hat now).
[Samsung Galaxy Nexus] kieudung:
I can not get past the first boot screen. I had to wait 20-30 minutes or so

situation that took place both on the rom 5.1 cm12 and other

help me
[Samsung Galaxy Nexus] runekock:
Did you wipe data and cache?

If no, do that.

If yes, you may need to format data, not just wipe it, however that will also delete everything in internal storage, so copy what you need to your computer first.
[Samsung Galaxy Nexus] kieudung:
i did wipe data and cache. :(:(:(:(
[Samsung Galaxy Nexus] mschumacker:
My LG G3 just died and not sure what I'm doing for a new phone, so went back to my trusty Galaxy Nexus and finally flashed CM13. Looks great, but it is REALLY slow. Any ideas on the slowness? Would updating to a more recent CM13 be better? I'm currently running the 20160822 nightly with Open Gapps Pico.

Thanks.
[Samsung Galaxy Nexus] hgmichna:
Galaxy Nexus speed

The Galaxy Nexus will never be very fast. It is too old, its processor is slow, and the wonderful tricks to widen its available RAM unfortunately make it slower too.

I think it is a miracle that the Galaxy Nexus performs as well as it does with CM 13. A year ago I would have lost bets on this.
[Samsung Galaxy Nexus] breversa:
Then go tabula rasa :

- re-download TWRP, CyanogenMod (+ Gapps if need) and check the control sums

- backup up everything on your phone

- check all the partitions

- reflash TWRP

- wipe everything : /system, /data, /cache + Dalvik cache and format the internal storage

- install CyanogenMod (+ GApps if needed)

- reboot

If that does not work, well... maybe nothing will.
[Samsung Galaxy Nexus] mschumacker:
What version would you expect for this phone to perform adequately? CM 10? 11? 12? I see that 10.2.1 is that last STABLE release.

Any thoughts?
[Samsung Galaxy Nexus] hgmichna:
Galaxy Nexus speed

I personally think that CM 13 performs sufficiently well for most purposes. Sure, it is slow, but when you go back to older versions, you incur all kinds of other disadvantages that can slow you down in different ways.

I hope that others report their impressions, because "adequately" is rather subjective.

I hope you have noticed that the Galaxy Nexus is very slow after booting, but becomes faster after a couple of minutes, depending on installed apps.