yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] uji_sine:
Thank you for comfirm my problem.
[Samsung Galaxy Nexus] bamtan2:
There should be a note in the OP about how [MENTION=2633638]Ziyan[/MENTION] maintains this ROM, but doesn't develop CM. So when there are bugs in CM, all we can do is wait for someone upstream to fix ;) If you have big problems, try a release from a week before, and maybe the bug is not there.
[Samsung Galaxy Nexus] mstyle3244:
I can't figure out how to enable root mode in the file manager of the new cm13 nightly.
[Samsung Galaxy Nexus] atiartstudio:
;) Stuck In Welcome Screen.Cm 13

I've just faced such a ridiculous bug...

https://forum.cyanogenmod.org/search/?type=all&q=+Stuck+In+Welcome+Screen.Cm+13
[Samsung Galaxy Nexus] rmedion:
same thing here..any idea guys?
[Samsung Galaxy Nexus] ciorci:
for me the only way to fix this is install busybox...
[Samsung Galaxy Nexus] mstyle3244:
"Busybox 1.24.2" the "/ su / xbin" I installed the problem was not resolved.
[Samsung Galaxy Nexus] ciorci:
strange...this work fine for me..
[Samsung Galaxy Nexus] atiartstudio:
deleted
[Samsung Galaxy Nexus] wyur:
[MENTION=2633638]Ziyan[/MENTION]

I made a build on 22th of July and I have still problems with Ducati. If I let my phone go in stand-by (or induce it manually) while a video player has a video loaded, then whichever player I used (Youtube, VLC...) crashes.

Also if everyone else is having issues playing videos in 720p at 60 FPS on YouTube, I have noticed other players like NewPipe (a YouTube front-end) load them just fine.

Attached a logcat and a screenshot I took at a different time with another app.

EDIT:

When it goes to sleep:

07-24 16:07:07.272 488 509 I PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
07-24 16:07:07.419 166 198 D PermissionCache: checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (183 us)
07-24 16:07:07.581 488 509 W linker : /system/vendor/lib/libglslcompiler_SGX540_120.so: unused DT entry: type 0xf arg 0x3db
07-24 16:07:08.464 488 509 V KeyguardServiceDelegate: onScreenTurnedOff()
07-24 16:07:08.592 488 509 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
07-24 16:07:08.595 488 507 I DisplayManagerService: Display device changed state: "Schermo incorporato", OFF
07-24 16:07:08.595 166 166 D SurfaceFlinger: Set power mode=0, type=0 flinger=0x40624000
07-24 16:07:08.639 488 509 I PowerManagerService: Sleeping (uid 1000)...
07-24 16:07:08.667 488 562 D WifiConfigStore: Retrieve network priorities after PNO.
07-24 16:07:08.667 488 562 E wifi_gbk2utf: g_pItemList is NULL
07-24 16:07:08.668 535 1172 E bt_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null
07-24 16:07:08.778 488 562 E native : do suspend false
07-24 16:07:08.799 488 562 D WifiConfigStore: No blacklist allowed without epno enabled
07-24 16:07:08.871 966 2641 D NfcService: Discovery configuration equal, not updating.
07-24 16:07:08.930 535 578 D DOMX : hardware/ti/omap4/domx/domx/omx_proxy_common/src/omx_proxy_common.c:1839	PROXY_SendCommand()
07-24 16:07:08.930 535 2503 D DOMX : hardware/ti/omap4/domx/domx/omx_rpc/src/omx_rpc.c:347	RPC_CallbackThread()
07-24 16:07:08.930 535 578 D DOMX : ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001009 - Error returned from OMX API in ducati
07-24 16:07:08.930 535 2503 D DOMX : ERROR: failed check:0 - returning error: 0x81009 - Remote processor fatal error
07-24 16:07:08.930 535 578 E OMXNodeInstance: sendCommand(32:TI.DUCATI1.DECODER, StateSet(0), Idle(2)) ERROR: Hardware(0x80001009)
[Samsung Galaxy Nexus] rmedion:
[quote name="niknok" post=67876628]yes, i had a problem with the release. can't get past the language selection. there seems to be another lock screen underneath.[/QUOTE]<br />

<br />

Thank you for comfirm my problem.

did u guys find a way how to pass the language selection? because after installing, boot up and i just cant pass it..
[Samsung Galaxy Nexus] osm0sis:
Are you guys removing CMSetupWizard as part of your GApps installation? Because there's a thing with that: https://github.com/opengapps/opengapps/wiki/Notes-for-CMSetupWizard

Alternately, if you aren't removing it, you could try removing it and apply my fix and see if that works around your issues.
[Samsung Galaxy Nexus] rmedion:
thanks for the reply man..

gonna test it rite away..[emoji106]
[Samsung Galaxy Nexus] sherincal:
Latest nightly works with your fix, osm0sis
[Samsung Galaxy Nexus] Python.:
How does this ROM compare to CM 12.1? I've been out of the loop for a while but would appreciate any help
[Samsung Galaxy Nexus] bamtan2:
http://xdaforums.com/showpost.php?p=67902373&postcount=4220

people have had more problems with CM13 recently, but those are CM13 problems, not galaxy nexus problems. newer software is always less stable
[Samsung Galaxy Nexus] vortex-5:
Which radio is recommended for CM13?

I'm running the standard I9250XXLJ1 baseband is that the supported version or is there are radio flash that needs to happen?
[Samsung Galaxy Nexus] MayuraDeSilva:
cm-13.0-20160725-NIGHTLY-maguro.zip

Hmm... Updated to latest nightly - cm-13.0-20160725-NIGHTLY-maguro.zip from 20th build, and after booting up, stuck at Preparing Contacts Storage. message.

Anyone experiencing the same issue?
[Samsung Galaxy Nexus] Mr.FREE_Bird:
I don't have the same problem, updated just 10mins ago and my gnex booted up just fine and works perfectly after optimizing apps.
[Samsung Galaxy Nexus] WoolTomb:
How much free RAM is there with the latest official CM13?
[Samsung Galaxy Nexus] Noeljunior:
For free are you asking usable RAM? "0.97GB total, 68% used (average)"
[Samsung Galaxy Nexus] MayuraDeSilva:
Glad to hear that :) Mine was stuck after optimizing the apps. Wiped /system and reflashed 20th build, but stuck in same screen. Had to reset and install from scratch to resolve it. No issues with the latest build after a clean install though. *Gotta love TitaniumBackup*

UPDATE: Buggy and occurred bootloops with Xposed installed. REPIT doesn't seem to comply afterwards either. Had to flash stock firmware and CM13. Guess I'll stick with 07/20 build for now.
[Samsung Galaxy Nexus] Vara83:
same me with old unofficial ROM 07/07/2016
[Samsung Galaxy Nexus] gabrielex:
For free I mean free, which means unused one, in your case 32%. which is 310.4MB of free memory and 659.6MB used one out of 970MB total.

Maybe this could be an issue with specific gapps? I'm using the open_gapps-arm-6.0-pico-20160704
[Samsung Galaxy Nexus] Stenean:
Hi, I encountered something very peculiar this morning. Firstly I noticed that flashlight tile was gone, and camera was throwing "Unable to connect to camera" error. After 4 days uptime that in itself wasn't that strange, but when I looked into htop to check for hogging processes, there was only one core reported! Output from /proc/cpuinfo confirmed this:

root@maguro:/ # cat /proc/cpuinfo
Processor : ARMv7 Processor rev 10 (v7l)
processor : 0
BogoMIPS : 1194.24

Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10

Hardware : Tuna
Revision : 0009
Serial : 0146b06209009010
root@maguro:/ # exit

I'm attaching logcat of the last 12 hours, because yesterday evening everything was fine.
[Samsung Galaxy Nexus] Ziyan:
Please try updating to the latest nightly (0727), which has a related issue (camera memory leak, which might cause such problems after some time) fixed :) it might fix the problem you're experiencing.
[Samsung Galaxy Nexus] molletts:
WiFi stops working

I keep finding that the WiFi drops and stops picking up any networks - toggling it off and on makes no difference; WiFi Analyzer doesn't see anything either. I just tried soft-rebooting to see if that fixed it (I shut down then started up again last time it happened, which did fix it) but the soft-reboot got stuck at the CM logo screen for over an hour; I've just power-cycled which has brought it back. I shall try a normal reboot next time it happens.

Has anyone else seen this problem?

It was fine on CM12.1 until I upgraded a couple of days ago.

I'm currently running 20160726 (I clean-installed straight to this version from 12.1, formatting /system and /cache and using TWRP's smart /data wipe); I'll update to 0727 now but I can't see anything in the changelog (at cmxlog.com/13/maguro) that appears to relate to WiFi.

Any suggestions welcome!

Stephen
[Samsung Galaxy Nexus] KarlusHTC:
Installed now the 13.0-20160726-NGHTLY-maguro, updated directly from Cyanogen 12.1, took tyme to update all apps, wen finally ended it's saying that I need to update google play services all the time popping up the message. what can I do to solve this?

Thanks in advance for the great job you all been doing keeping alive my Nexus2.
[Samsung Galaxy Nexus] MayuraDeSilva:
Did you install a compatible GApps package when you update to CM13 - right after flashing the ROM?
[Samsung Galaxy Nexus] madde-:
Hi - since the latest nightly (29-7) my APP Signal whoch I use for SMS / MMS and IM doesnt work anymore and quits with a standard error "Signal dies not work anymore"
[Samsung Galaxy Nexus] vortex-5:
So I get this too with the latest nightly. I noticed that my wifi starts working again once I set the region code to US (I'm in Canada) setting it to the Canada region code will always have the wifi show up as "saved" it seems to not be able to obtain an IP when the region code is changed to Canada for some reason.
[Samsung Galaxy Nexus] KarlusHTC:
Made a clean install, and installed open_gapps-arm-6.0-pico-20160728, all is good now. Thanks #MayuraDeSilva
[Samsung Galaxy Nexus] MayuraDeSilva:
Performance: 07 / 27 Build

Noticed the "Disable dexpreopt to make room for gapps on /system" has been reverted back in 07 / 27 build.

Did you guys notice any improvements in booting or after upgrading?
[Samsung Galaxy Nexus] MayuraDeSilva:
Cool! You're welcome :)
[Samsung Galaxy Nexus] abo we2am:
Please help me, I can't access CyanogenMod site, could any one upload the last nightly build for me?

Thanks guys.
[Samsung Galaxy Nexus] natzy85:
Do you guys have a seldom bug when power on opens the camera? I did dirty flash from CM12.1 and test several nighlies. I just wish to know if this will go away if I flash it with proper format.

Just found out this is because of double tap to camera. How do I disable this?

Found it in the buttons section.
[Samsung Galaxy Nexus] Zenroid:
Installed latest nightly of cm13 over cm12 but stuck at starting apps, format /system still failed. After formatting /data booting up successfully with better performance than cm12 it seems :)
[Samsung Galaxy Nexus] Cuissedemouche:
Hello,

I want to install this rom with the stock version of OpenGApps. So I need to change my system partition size, but I'm not sure when I need to do it, if it's before or after flashing rom.

If I understand :

1) I wipe my device

2) I flash the rom

3) I use this repit script : lanchon-repit-20160415-system=1.0-cache=0.0605+wipe-data=same-maguro.zip (link found from this post : http://xdaforums.com/showpost.php?p=67057919&postcount=307)

4) I flash the gapps

Also, I use F2FS partition, but I see it worthless to have a /cache partition in F2FS in the first post, so if I only format the /data to F2FS is it good ?

Thanks, and also sorry if my english isn't very clear.
[Samsung Galaxy Nexus] bamtan2:
I think you are correct. Because flashing the ROM wipes /system every time, you can flash the ROM, then flash REPIT to resize /system, then flash GAPPS onto the larger /system.

I'm not sure how big a GAPPS you can fit in a 1GB partition. I personally flash the smallest GAPPS because I download the other Google apps from the Google Play app store.

Formating /data to F2FS should work. But beware: some bugs have been found when using F2FS! Including with Whatsapp.

Note: please use the latest unofficial TWRP by [MENTION=2633638]Ziyan[/MENTION] found here: http://xdaforums.com/showpost.php?p=67908270&postcount=2004 -- just select "image" flash in TWRP, and select "recovery" partition to flash it to.
[Samsung Galaxy Nexus] kaynpayn:
My biggest problem is the phone heating up a lot. Battery lasts a lot while the phone is on standby. As soon as I turn the screen on, it starts mowing down the battery and heating up a lot doing something simple like browsing reddit. Anyone else has this? Using the 0727 build.

By burning the battery I mean I can go from 100 to 0 in half an hour. Phone starts throttling too due to overheating. At least I notice it getting slower. Jut by typing this it burnt 10℅ and the top around the camera is boiling.
[Samsung Galaxy Nexus] uji_sine:
Sorry, I not have problem same with you. (07-27-16 build)
[Samsung Galaxy Nexus] NightShadow02:
i accidentally flashed a tuna marshmallow rom and am now trying to flash cwm13 on it but now when it tries to boot to system, I get a blackscreen after the Google logo and after a few minutes, it looks like it rebooted and the google logo appeared again and goes again to the blackscreen of uncertainty.

im using the latest snapshot from 7-19. the installation in twrp seems oddly quick. less than 30 seconds. it says installation is successful but the installation time is suspicious.

edit: ok odd. after multiple reflashes in TWRP I see the CWM bootscreen now. weird. what happened man
[Samsung Galaxy Nexus] ogre_x:
Flash the latest official factory image from google to reset the phone.

Then boot into recovery and do a factory reset.

Then just flash the custom recovery and rom from cm.

Had a similiar issue with black screen on boot both standard and into recovery. Above method fixed it. Running 30/7 build now.
[Samsung Galaxy Nexus] NightShadow02:
i wanted to do that but with no way to transfer the factory image to the phone (using "easy" channels) I was going through instruction for adb, installing adb drivers, etc then saw how complicated the driver installation was (instructions that I found seemed like they were from 2013 and had broken screenshots and stuff) I decided that maybe I'll try another reflash. I reflashed one more time then now I can see the CM bootscreen. Weird. What happened?

Also, my directory structure looks messy af. I'm seeing multiple layers of past directories (DCIM, Whatsapp) under 0/0/0/0/0/... for example. How would one clean that?
[Samsung Galaxy Nexus] ogre_x:
Yeah, GN is a real sore thumb when it comes to those pesky USB drivers. I flashed from my Macbook - no need to hassle with USB drivers, just do flash-all.sh.. Learning to use fastboot and adb is a great investment and simplifies flashing a lot.
[Samsung Galaxy Nexus] NightShadow02:
thanks for the help buddy.

ok new problem. flashing CM12.1 works but when i try to flash the latest CM13 nightly, it says E:/Error in /tmp/sideload/package.zip (Status 7)
[Samsung Galaxy Nexus] hgmichna:
High power consumption, heating up

I see this occasionally. I have also seen it on phones that had been booted after updating from CM 12.1 to 13 before flashing Google apps matching Android 6. Apparently this does something to the data partition that cannot be rectified by wiping system and caches alone. It keeps reappearing until you do a factory reset and flash CM 13 and Gapps for Android 6 without booting in between.

But on my Galaxy Nexus the effect sometimes occurs, although it had been updated properly and never been booted with the wrong Google apps, so perhaps there is some kink still in there. Another conspicuous effect is that it does not recognize the SIM card. I have to watch this more carefully. Perhaps it only happens when powering up for the first time after a CyanogenMod update.

When I reboot, it usually starts up, recognizes the SIM card, and runs just fine. Wish I knew what is going on there. I keep updating, hoping that some future version solves this problem.
[Samsung Galaxy Nexus] kaynpayn:
This one never got anything custom. Skipped from stock 4.1, not even rooted, straight to cm13. Think it has anything to do with it?

Also no problems with the sim whatsoever. Is there any ROM more recent than 4.1 that wont have this problem? Hopefully on android 6 but anything else would do as well.
[Samsung Galaxy Nexus] bamtan2:
There are parts of the phone that the stock ROM updates but custom ROMs do not, so for this reason the general XDA advice is to start from the newest stock ROM. I cannot tell you if this has anything to do with any problems though.
[Samsung Galaxy Nexus] bamtan2:
I cannot help you, but maybe [MENTION=4141005]Lanchon[/MENTION] would like to see your REPIT log :)
[Samsung Galaxy Nexus] Cuissedemouche:
I already said that I solved my problem in original post :D

Finally I have CM13 (nightly 2016/07/30), it works pretty well.

For now, the only bugs I met were the popping sounds and I can't access to Battery in Parameters.
[Samsung Galaxy Nexus] rasshi:
Do you support ETWS ?

If the Sim is not pointing there is an item of ETWS it does not have a item for pointing to Japan of SIM.

Sorry bad for my English.
[Samsung Galaxy Nexus] lleha776:
Installed in my Galaxy nexus... work pretty well

thank you so much ...
[Samsung Galaxy Nexus] hgmichna:
Phone gets hot and runs down the battery

I have similar symptoms with CyanogenMod 13 on several Galaxy Nexus GT-I9250 phones and also on two of three Samsung Galaxy S4 LTE-Advanced GT-I9506 phones. The phones become slow, almost unworkable, heat up, and eat battery charge rapidly.

On the Galaxy Nexus, when it happens after booting, the phone usually does not recognize the SIM card. A second reboot usually resolves the problem for the time being.

What is going on? A general defect in CyanogenMod 13? Anybody else seeing this? I keep updating in the hope that a newer version has this repaired.
[Samsung Galaxy Nexus] MayuraDeSilva:
If you can, try flashing last stock firmware (4.3) for Galaxy Nexus and install CM13 again.

I had a similar issue when I try CM13 for the first time, and was very sluggish, couldn't able to detect the SIM and keep crashing Google Play services. Flashing stock firmware and reflashing CM13 resolved it for me.

Hope it helps :)
[Samsung Galaxy Nexus] hgmichna:
Phone gets hot and runs down the battery

In your case, did rebooting solve the problem for at least a day? Or did you have the problem always?
[Samsung Galaxy Nexus] MayuraDeSilva:
Not always, but sometimes rebooting and wiping cache partitions seem to resolve it temporarily. At that time, I thought the ROM was buggy.

Kept reinstalling many times and ended up with different errors, until I reflash it with stock firmware.
[Samsung Galaxy Nexus] hgmichna:
Phone gets hot and runs down the battery

Thanks! I don't have the option to reflash stock firmware, because most of the phones I deal with are far away from me and in the hands of non-technical people.

But since most users here also do not reflash to stock I still have hope that the problem will be fixed or will go away with CyanogenMod updates. Note also that we have no explanation and that the problems occur sporadically. If the phone runs fine on one day, why not on another?

Just updated to cm-13.0-20160731-NIGHTLY and don't see any errors yet. Hope, hope.
[Samsung Galaxy Nexus] MayuraDeSilva:
True - I couldn't find a solution to mine that time and it wasn't on daily updates either. Hence had to try what I could try.

Glad to hear no errors so far. Hopefully the issues will be resolved over the updates.
[Samsung Galaxy Nexus] sleepnd:
Anyone has issue on Camera, it said it cannot connect Camera.

Both 0731 and 0803 have issues, don't know is it becasue dirty flash from 0730 or not.
[Samsung Galaxy Nexus] Ziyan:
Tomorrow's nightly (20160803) will have the AOSP camera app replaced with Snap (CM's camera app), which offers a little bit more features without drawbacks on our hardware :)
[Samsung Galaxy Nexus] LeoHart:
Update to nightly 0802

unfortunately the issue is still there :(

:edit:

Ok, I will try the 0803 :)
[Samsung Galaxy Nexus] Ziyan:
Sadly, I can't help any more without a way to reproduce this... as far as I know, it can be anything from a generic CM or app bug to a camera HAL problem. The only known problem for me is flashlight - you can't turn off the screen while using it, as it will crash ducati. Of course, this flashlight problem isn't present on AOSP 6.0... Was camera fine for you on 12.1?
[Samsung Galaxy Nexus] LeoHart:
On CM12.1 all worked fine.

For me it seems that flashlight and camera depending each other. I can not use flashlight if the camera is not working.

I am not using the camera frequently, so it is not a huge problem for me.

Overall CM13 performing better on the Gnex as CM12.1, also the apps :good:

I am trying the new nigthly version and with a little luck it solves the problem ;)
[Samsung Galaxy Nexus] m00nman:
Camera works here too.

I can't seem to switch I/O scheduler to anything else. Only BFQ works. If I try to go to let's say deadline the OS just hangs and the only way to restart is to pull the battery (or press the power button for long enough for the phone to switch off)
[Samsung Galaxy Nexus] bamtan2:
This is a known issue. Unfortunately a lot of kernel variables do this ;( I think ziyan is okay with it because he found BFQ to be the best after many months of testing. The workaround for this problem would be to use a different kernel with different settings by default. [MENTION=4608636]bsmitty83[/MENTION] and others have released alternative kernels.
[Samsung Galaxy Nexus] Ziyan:
...or change sys.io.scheduler=bfq in the build.prop to something else, like cfq, and reboot :)
[Samsung Galaxy Nexus] :
Mine was a fresh installation and I had same issues with the camera. It was not possible to connect when there was not enough free RAM. It worked only after closing and restarting the app. The problem did not occur when there was plenty of RAM free but once I have launched several other apps and then tried to run the camera, it would not connect on the first try :(

I also experienced another issue related to phone calls - same as in the zzpianoman's ROM - which was that once every few calls the phone would just become completely silent while in the middle of a call (= I could not hear anything), and in order to fix it I had to end the call and make a new one :/ Unfortunately I cannot provide any logs, etc. as I have moved to another ROM (< Android 5.0) in the meantime since phone calls are the priority to me and have to always work 100%.
[Samsung Galaxy Nexus] axlu:
Other small bugs

Hi. I have just installed the latest (200160803) As a few of the other updates it was a little difficult. Very slow, needed a battery pull, but now it's up an running and with a new camera. What happened to the one which could do spheres and panoramas? Another feature I have missed during Lollipop was the support of extra storage through the USB, will that feature return? Anyway, you are doing a very good job. Keep up. Axlu
[Samsung Galaxy Nexus] Ziyan:
Hmm, I don't recall the old camera app doing spheres and panoramas - only Google Camera can do that (ie. if you install a big enough gapps package, or download and install the APK from somewhere, as Google only allows downloading it on the latest Nexus devices :(

I thought USB OTG was working, like on AOSP 6.0 - CM might need something else to enable it, need to investigate it later :(
[Samsung Galaxy Nexus] bamtan2:
Maybe different minfree values are needed to reserve more RAM for camera use? Our old nemesis, lowram...
[Samsung Galaxy Nexus] crackerjacc:
After getting bit by not paying attention and loosing everything to the nightly update being updated to CM13 from 12.1 I did a clean install of 13 but I noticed after the Aug 2nd nightly that after the update and reboot the phone gets stuck on "Android is upgrading - starting apps". It just sits there forever until I pull the battery and restart the phone. Just started doing this but appears to happen every time a new update gets installed now.

Also, FB app particularity is freezing then going to a black screen until a not responding error occurs and I have to close out the app and restart. It's the only app running at the time. It gets a lot worse if I open another app. I'm assuming this is a lack of RAM issue but the same configuration with CM12.1 didn't have this issue at all on my phone. :(