yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mschumacker:
I thought so at first, but mine hangs alot. Also, It seems that I'm not getting 4G all the time like I did on my other phone.

Mine's been as slow that when clicking on a button, there is at least a 3 second lag before anything happens. I didn't put any Facebook on it as I know that's a hog, but mainly just running email and messages.
[Samsung Galaxy Nexus] breversa:
That's because CyanogenMod changed the names of the stable releases. Starting from then, "SNAPSHOT" means stable, while "NIGHTLY" means less-stable.
[Samsung Galaxy Nexus] hgmichna:
To my knowledge the Galaxy Nexus has only 3G hardware, not 4G/LTE.

Due to little RAM and due to RAM compression some delays are expected. That can't be helped.
[Samsung Galaxy Nexus] vortex-5:
Galaxy nexus GSM version was HSPA+ verizon had an LTE capable variant.
[Samsung Galaxy Nexus] HeaDekBatHblu:
Need overclocking to 1.5GHz in the last snapshot cm13. What is the core I can put to get it?
[Samsung Galaxy Nexus] alarien:
I guess, your best bet would be LuckyK.

Also, "ядро" in this context is not a "core", but a "kernel".
[Samsung Galaxy Nexus] HeaDekBatHblu:
I have not found a working kernel under the downloads LuckyK. They all cause or bootloop, or reboot into recovery mode. I found one yet, but it crash AOSP keyboard and settings constantly...

And, sorry for my bad english :C On 4pda i don't have any reply on my question.
[Samsung Galaxy Nexus] m3nu:
Upgraded today

Also upgraded from CM12 to the latest CM13 nightly today. All working as expected. Steps:

- flash latest recovery image

- factory reset (keep media)

- Apply CM13 and gapps pico

- Reboot

Great job the devs are doing here really.
[Samsung Galaxy Nexus] bugsey:
hi!

Ziyan writes: "all the camera issues (ie. pink lines, rare crashes) resolved", but that`s not so optimistic.

Camera app almost always crashes, when switching to video-mode with throwing exception:

java.lang.RuntimeException: getParameters failed (empty parameters)
at android.hardware.Camera.native_getParameters(Native Method)
at android.hardware.Camera.getParameters(Camera.java:1979)
at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:357)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.os.HandlerThread.run(HandlerThread.java:61)

But! If previously take a picture (in photo-mode), error in most cases will not appears!

Maybe camera just needs initialization?
[Samsung Galaxy Nexus] gh[o]st:
After installation any application (applications installed and running). google translate
[Samsung Galaxy Nexus] hot\oniel:
Done.......

Thank already have ROOT ....

OK everything is working well since installation ...

It has been an excellent job with this ROM Ziyan ...

Regards........ :laugh: :good:
[Samsung Galaxy Nexus] nikodr:
Since audio fx is not working i think this is a must for everyone running cm 13. It installs viper for Android. Just did it and i have good sound on my nexus :)

http://www.gizdev.com/guide-install-viper4android-on-cyanogenmod-13-android-m/

---------- Post added at 05:03 PM ---------- Previous post was at 04:54 PM ----------

@ziyan any news regarding the no signal and drop off signal? I really want to use it as a phone. Having this problem is impossible. Zzpianoman in his android 6.0 rom posted a fix that may fix the signal drop. Can you post something similar? Thank you!
[Samsung Galaxy Nexus] ArnoldGarry256:
Wow! This is so impressive. For the first time I see myself running 6.0.1 as daily driver on my GNex. Just booted it up with GApps. Thank you!!!
[Samsung Galaxy Nexus] nikodr:
Can we use the radio files from aosp lollipop roms? Zzpianoman mentioned something. Any news regarding radio loss?
[Samsung Galaxy Nexus] hot\oniel:
I have ROOT but not which one? ... As I put Super Su?

please let me know........

Regards
[Samsung Galaxy Nexus] momojuro:
The ROM comes with an inbuilt Superuser manager which let’s you disable root when not needed. For example, when an app asks for the root permission a pop-up will appear to choose if you want its allowing or not. So, there's no need to install SuperSU. :)

Best regards.
[Samsung Galaxy Nexus] WoolTomb:
Can i flash this ROM if i have TWRP 2.8.7.0? Or do i need to flash before TWRP 3.0.0.0?
[Samsung Galaxy Nexus] thagringo:
you can use whatever version you want.

cheers
[Samsung Galaxy Nexus] zzpianoman:
I never suggested such a thing.
[Samsung Galaxy Nexus] nikodr:
Forigve me i meant the files you posted i thought were from aosp roms. Sorry
[Samsung Galaxy Nexus] Vara83:
I returned to CM12.1 from CM13 because SuperSU not works, my phone is rooted but is impossible to install SuperSU Binaryies, so Apps like BusyBox, Trickster MOD and Leandroid not works corretcly
[Samsung Galaxy Nexus] nikodr:
I have cm 13 rooted you need latest Version 2.65 otherwise it won't work. All root apps i have and busybox work perfectly in cm13 with supersu 2.65
[Samsung Galaxy Nexus] hot\oniel:
Unfortunately the application Audio FX stopped.

I can not delete.

how I solve that? this occurs frequently ..

I had to flash every time it happens ..

please let me know......

regards
[Samsung Galaxy Nexus] Nautilus74:
Why you can't delete it? Any file manager can do it!

(then you install Viper....... ;) )
[Samsung Galaxy Nexus] nikodr:
Regarding audiiofx check some posts back i posted a link that says how to remove audio fx and install viper.
[Samsung Galaxy Nexus] hot\oniel:
Problem with file.........

file problem I'm having trouble downloading files needed ... as I get?

Please let me know with some guidance .. :)

Regards
[Samsung Galaxy Nexus] a2dx:
Download

Hello everybody,

there is no download link for this rom? Where can i download it? Or am i dumb to see it :/

Thx

Iam dumb, found it in the download section ^^
[Samsung Galaxy Nexus] nikodr:
[MENTION=2633638]Ziyan[/MENTION] can we help with logcats to fix the signal bug?
[Samsung Galaxy Nexus] ArnoldGarry256:
It's fine. Haven't faced any issues with GApps though. Installed once and works like charm.

---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------

Been using it for 3 days. I don't face any signal drops. Could be a location/radio issue?
[Samsung Galaxy Nexus] Ziyan:
It might be this Android bug: https://github.com/Unlegacy-Android/android_packages_apps_Camera2/commit/c05c3ec9aedbd9a87acac5852f0d37f600b4bde6
[Samsung Galaxy Nexus] bugsey:
I don`t know. Maybe.

I know only one thing: when i`m start using CM, i`ve always some bugs with camera app :)

Before CM13 (and before CM12, i think), there is was some sound delay in recorded videos. Now - it`s a problem with initialization.

But i like CM and i will use it (not develop it).
[Samsung Galaxy Nexus] RansuGiru:
data usage on mobile hotspot

Hi Folks,

**Update**

After testing tethering on a new phone, also running 6.0.1, my data usage is back to normal .... so definitely something going on with the base ROM for the Galaxy Nexus ...

So I've recently flashed CM 13 on my takju and have seen an incredible increase in the amount of data used while tethering my laptop to mobile hotspot. Previously while running stock jellybean (official google image), I would use 10-50mb per 7 hr tether. I ssh to a remote server and run terminal apps, hexchat irc, and sparse web browser use -- all routed though a socks proxy on localhost on the ssh tunnel. Now I am seeing 500+mb, even up to 1gb ... crazy! (and scary on a tiered plan like Ting)

My assumption is that the network stack on marshmallow has greatly increased background data during hotpot connections. Can anyone confirm or explain this behavior?

Also, I have monitored usage on the laptop using iftop on the wlan0 interface at the ssh destination port and the local loopback socks proxy. The cumulative data matches what I *used* see, but my carrier metering and android system mobile data metering report the super high usage ...
[Samsung Galaxy Nexus] Ziyan:
Just pushed a bunch of CVE fixes to the CM13 kernel; apparently, lots of folks were freaked out recently, so CM kinda made this a requirement... They should be included in the next nightly (20161029). :)
[Samsung Galaxy Nexus] runekock:
It doesn't seem like a rom problem to me.

You sure that your laptop isn't downloading windows updates or something? Or a virus in one of the devices?
[Samsung Galaxy Nexus] RansuGiru:
Positively no updates downloading, since I'm running Debian with manual updates only! Virus in the ROM, maybe .... definitely not on the laptop.
[Samsung Galaxy Nexus] biomorgoth:
CM13 feedback

Hello everyone!

I have tried to use CM13 as an alternative to MM Unlegacy-Android, but i could not stay with this ROM for a big reason, and the reason was that i could not use the mobile data on the phone. I successfully configured the APN for my mobile carrier, and immediately enabled it with no luck. The signal indicator on the status bar did never showed mobile interaction (by this i mean the typical up/down arrows never showed, nor the G/E/3G/H/H+ characters). I tried turning Airplane Mode off/on, rebooting the phone, turning it off, removing the SIM card and sliding it back again then turn on the phone, and even had reset, but the issue stood there.

I did a clean install of the following files:

cm-13.0-20161028-NIGHTLY-maguro.zip
open_gapps-arm-6.0-pico-20161029.zip

After that i tried using the latest snapshot version from get.cm site:

cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J5-maguro.zip

Using the same open_gapps zip, but the result was the same.

Finally i rolled back to CM12.1 where this issue has not happened in my case. I do not know if this is relevant, but my network operator is a MVNO.

I would be happy to be testing on next releases, as it would be awesome to have again 996MB RAM instead of the 876MB from CM12.1 :)
[Samsung Galaxy Nexus] MayuraDeSilva:
I'm on cm-13.0-20161020-NIGHTLY-maguro right now and haven't had any issues related to Cellular Data - neither in previous CM13 builds.
[Samsung Galaxy Nexus] biomorgoth:
Can i ask which phone carrier are/were you using on your GNex?
[Samsung Galaxy Nexus] MayuraDeSilva:
I've used Mobitel, Dialog, Airtel (Current) and Hutch, and cellular data was fine with all. Not sure if you've even heard of any of those :)

Today updated to cm-13.0-20161101-NIGHTLY-maguro and still fine.
[Samsung Galaxy Nexus] biomorgoth:
As far as i can see, none of those mobile operators are MVNOs. Also, none of them operates on the same band as my operator. Maybe the issue starts from there? It would be nice if any of the devs could determine if the RIL could affect data performance based on any of those features (network band, type of carrier, etc.). I will try to get borrowed a non-MVNO SIM card from a friend just to try if data finally connects.

But also, if any of you could tell me where to get the RIL log or any log that could be useful, i would appreciate.

BTW Thanks for helping me on this! :)
[Samsung Galaxy Nexus] MayuraDeSilva:
Well...That's a start then :) See if you can try non-MVNO from a friend. Hope devs can resolved it for ya.

Hope this may come in handy ~ [Reference] How to Get Useful Logs
[Samsung Galaxy Nexus] fromfree:
I had this issue too, but I only tried the snapshot. My network operator is PosteMobile (italian) that should be a MVNO.

The same APN settings are working flawlessly in every other ROM.
[Samsung Galaxy Nexus] uji_sine:
CM14.1 launch, hope to see on galaxy nexy as soon. Thank you develope workibg hard on this device.
[Samsung Galaxy Nexus] Android-Andi:
Patient is the best recipe :)

The AOSP cast feature in CM should be finally fixed on next weekly (in case someone needs it).
[Samsung Galaxy Nexus] miomaguro:
Nightly 20161107... Quite impressive!!

I wanted to say thanks for this awesome ROM: in my device, it works way more smoothly than the CM12! It takes a bit longer to boot, but then it is impressive! Do you suggest to never update Google Play and keep staying with the pico gapps?
[Samsung Galaxy Nexus] musical_chairs:
Yes, you'll need to stay with the pico gapps. There is no need to update your gapps package as Play Store and Play Services will update themselves automatically.
[Samsung Galaxy Nexus] miomaguro:
Thanks for your answer, I was a bit ambiguous with my question, actually the point was exactly if I should allow Play Store and Play Services to update themselves automatically OR if (for a matter of performances/functionalities) it's better to keep with the gapps version.
[Samsung Galaxy Nexus] bamtan2:
opengapps gapps are the same as the automatic update gapps!
[Samsung Galaxy Nexus] miomaguro:
Uh, ok thanks for making me aware of this... However, apparently I've started having some troubles I want to share. First of all, the phone stuck with a black screen and was not responsive until a battery removal. Then, I realized it had exhausted 40% of battery in one hour (I was not looking at it). Then, I found a bug and a little issue: the bug is related to the carrier icon that shows the empty signal bar even if it is perfectly connected to the network and can receive phone calls. The issue is related to the tone volume that seems to me a bit lower than that I was used to with the CM12.0.

Does anyone have the same issues?
[Samsung Galaxy Nexus] bamtan2:
This is probably common for devices that have very old, worn out batteries. When someone with an old iphone gets this problem, they throw it away! :) With Galaxy Nexus you can replace the battery.

Unfortunately old phones don't have many new batteries made for them. When I bought the battery I use now, I had to buy many different batteries, because I knew most of them would be bad. And most were. But luckily ONE battery was good. It was a fake samsung battery from ebay which I can't find online anymore. It has better battery life than my original 2011 battery. A battery manufacturer must have made a batch of them, and then sold them as fakes. I'm thankful to them, but I wish they would have simply branded them as something distinct, so I could tell you now which battery to buy.
[Samsung Galaxy Nexus] miomaguro:
Not actually, it was not an issue of battery: I think it was some process gone mad in the background that was blocking the whole system. The battery reset was only used to hardly stop everything. My battery is still pretty good and can last more than one full day with my moderate usage. However, in addition to the above mentioned issues, I've started experiencing some random reset from time to time.

Urgh: for two days it was running perfectly and now... It's like the Murphy's law: I shouldn't have said anything!!
[Samsung Galaxy Nexus] newfoundme:
CM worked perfect until crash; can't flash other roms nor other recovery

ROM worked almost flawless for months until crash last week.

Stuck in boot loop; works up to Cyanogen sign and restarts

Can't flash other rom: in TWRP 'E:zip signature verification failed', but if I uncheck this in settings, it won't work either.

Tried to flash other recovery and other rom with adb sideload. Won't work either.

Any suggestions?

Regards
[Samsung Galaxy Nexus] vortex-5:
You probably need to wipe /system /cache /dalvik-cache before trying to flash the new rom.
[Samsung Galaxy Nexus] newfoundme:
Thanks; I tried this. It looks like my rom has flashed successfully but when I reboot the nexus, it seems that the entry (new rom, copied and flashed to sdcard) has disappeared.

Could it be that the memory of my nexus is corrupt?

Maybe something else?

Regards
[Samsung Galaxy Nexus] mike.sanders:
New snapshot release?

Latest snapshot release dates back to 2016-08-20.

While I did start out with a snapshot installation because I wanted less frequent updates and more stable behavior (in comparison to nightlies) I do believe that there have been some security fixes which would be welcome.

AFAIR, there was some news coverage on a more severe Android security issue for which a fix is yet to be released. Are you waiting for that? Or can we expect a new snapshot soon-ish? Or is it recommended to just use nightlies?
[MENTION=2633638]Ziyan[/MENTION] ? Anyone?

Thx

- mike
[Samsung Galaxy Nexus] musical_chairs:
The 'nightlies' were just recently changed to weekly builds since there is very little changing in cm13 any more. They are very stable at this point, I would recommend running them.
[Samsung Galaxy Nexus] Cintra2:
Yes, I can confirm having updated to the latest 'Nightly' and after sorting out an old Gapps problem causing "Google Play Services has stopped" messages that were almost impossible to get past, my Galaxy Nexus is working pretty damn well for such an old device :) Many thanks to the developers..
[Samsung Galaxy Nexus] newfoundme:
Hi,

I can flash any rom but it looks like what I flash doesn't 'stick' to my phone's memory. Is there anything I can check or uncheck in TWRP so I can actually write something on its memory?

Thanks
[Samsung Galaxy Nexus] miomaguro:
Is the wipe needed for each nightly? Or I can simply install the new zip?
[Samsung Galaxy Nexus] :
No wipe needed, simply flash the new nighties
[Samsung Galaxy Nexus] miomaguro:
What about cache wipe?
[Samsung Galaxy Nexus] :
Not needed
[Samsung Galaxy Nexus] miomaguro:
Good to know! Thanks
[Samsung Galaxy Nexus] edu24lal:
i have the latest cm 13 nightly...is working fine until some time after boot i go to youtube app and videos dont play..says tap to retry and do nothing....instagram videos doesnt work either.....so i have to reboot phone....then all work and after a while the same problem
[Samsung Galaxy Nexus] miomaguro:
With the new nightly (14-11-2016) I have an issue with some webpages: if you try to surf the website of the Danish weather (dmi . dk), the browser does not show the picture of the forecasts. You can make the comparison with the same webpages open in the PC browser and in the smartphone...

Does anybody have the same issue? Any hint?
[Samsung Galaxy Nexus] a0a0:
Hi, when I do a VIDEO Call on Whatsapp on the other side my video is in grayscale. It happens to someone else ?
[Samsung Galaxy Nexus] ancelin:
Hello all,

I installed this CM13 rom in February but I went back to CM12.1 because it was not as smooth. -->previous post

Yesterday I tried again with cm-13.0-20161114-NIGHTLY-maguro.zip but I have the exact same issue that tactile do not respond at every touch. I really notice this while playing game when you need to be quick and where I need to touch 2 or 3 times somewhere for my command to be taken.

I do not have this problem with CM12.1

--> Does anyone have the same issue ? Do I need to flach another Kernel or ril or anything to avoid this issue?
[Samsung Galaxy Nexus] jnraj:
device gets into bootloop on activating greenify xposed module,

thanks for everything
[Samsung Galaxy Nexus] m3nu:
The hardware of this phone is fairly old. It may be too weak for recent games. Maybe keep using it for less challenging applications.
[Samsung Galaxy Nexus] hgmichna:
Do not ask too much from the Galaxy Nexus

I say the same. Ziyan has done an excellent job to stretch the limited resources of the Galaxy Nexus to their limit, for example by using data compression to stretch its RAM.

But of course you don't get something for nothing. The already slow, by today's standards, Galaxy Nexus does not become faster by installing ever bigger new Android versions on it. Android 6 on the Galaxy Nexus is not far short of a miracle.
[Samsung Galaxy Nexus] ancelin:
I think I will stay to android 5 if you say it is harware limite, the strange thing is that game like "clash royal" is working so well with CM12.1 but cannot play with cm13 (touch responses issue)

--> I went back to android CM12.1 and no more issue, phone is much much faster on this Ziyan CM 12.1 rom -->work like a charme than never!
[Samsung Galaxy Nexus] PGHammer:
There IS an official CM13 for GNex!

Actually, there is an official CM13 for GNex; the current nightlies are from the official (release) channel.

Current nightly : cm-13.0-20161122-NIGHTLY-toro.zip

Current recovery : cm-13.0-20161122-NIGHTLY-toro-recovery.img

Alternately, you can use TWRP 2.8.7.0 or later as a recovery.

---------- Post added at 07:47 PM ---------- Previous post was at 07:45 PM ----------

In my case, I have an issue with Konami slots - but not any other game - on CM13. However. of the games that have the issue, why CM13 (but not CM12)?
[Samsung Galaxy Nexus] PGHammer:
Possible root of issue; flash of GApps?

Did you have an issue with your GApps?

OpenGApps 6.0 nano is too big - replace with the pico version. (This applies to any ROM based on Marshmallow or later; I moved north to Unlegacy Android, which is based on 7.1 Nougat, and flashing 7.1 pico solved the one app issue I had with CM13 and 6.0 pico. In other words, I moved north - not south - and the issue went away.)

I've since swapped launchers and assistants (to Arrow and Cortana - replacing the stock Launcher and Google Now, respectively) because they are what I am used to on my tablet; rather amusingly, the "wrong" launcher does not call attention to itself any more than it does on Lollipop (which is what my tablet is running).
[Samsung Galaxy Nexus] Syakir Imran:
Xposed

how you flash xposed? I got bootloop with the latest cm version.

are there any xposed for cm??
[Samsung Galaxy Nexus] jnraj:
flashing xposed did work but turned out useless since no module could be activated from xposed app, reboot resulted in bootloop, had to hide root for some apps so switched to 12.1.
[Samsung Galaxy Nexus] vortex-5:
Anyone know why the current version nightly has been held up? seems to be backed up several weeks now.
[Samsung Galaxy Nexus] osm0sis:
Probably because 14.1 and 13.0 nightlies are now rolling out simultaneously for several devices, so there are server load concerns and they backburnered a few devices.
[Samsung Galaxy Nexus] vortex-5:
Ah. Well fingers crossed that unlegacy means that an eventual port of CM14 will make it to Maguro failing that a year later I might be on unlegacy to try it out :)
[Samsung Galaxy Nexus] ancelin:
No issue for me and Gapps, I used OpenGApps 6.0 pico as always

My process :

I installed latest twrp 3.0.2 recovery --> wipe system, wipe data, wipe cache, wipe dalvik + changed data and cache to f2fs

After I flached latest nightly and latest OpenGApps 6.0 pico + reboot

I did not unmount /system before flaching and don't know if it was needed. Phone is working well on cm13 exept touch response where I need to touch 3 times on same point for the phone to react.

I whent back to cm12.1 using same process and but with pico opengapps from 20160120 to avoid market 963 issue ( I didn't know if this is solved with new gapps now?) + only use one Data APN with MMSC set and ",mms" on APN type...

(those 2 issues i dont have it on CM13)
[Samsung Galaxy Nexus] el_ruwen:
Hi!

I got the latest SNAPSHOT currently and I had CM 10 (or 11?) before. I wiped everything before installing the new version. I got a few issues:

1) Compared to the previous version my mobile is pretty slow.

2) GPS does not work at all. I am trying to use OpenStreetMap

3) 90% the camera does not work. I get something like "No connection to the camera" possible.

Can I simply update from the SNAPSHOT to the latest nightly without flashing or wiping anything? I got my phone encrypted, might this be a problem?
[Samsung Galaxy Nexus] m3nu:
I'd try the latest CM13 nightly. You may have the last CM12 snapshot. CM13 seems more responsive compared to that. I also don't think CM12 snapshot has the latest security patch level.
[Samsung Galaxy Nexus] el_ruwen:
I just checked. I definitly got CM13 Snapshot. Do I have to wipe my device or since it stays in the same version I don't have to?
[Samsung Galaxy Nexus] m3nu:
I'd try the latest nightly. Snapshot just means the devs think it's more stable. But Aug ist a long time in Cyanogen land and you will have missed out on many fixes. You can check https://www.cmxlog.com/13/maguro/ for the latest changes.
[Samsung Galaxy Nexus] el_ruwen:
Thanks for the changelog link. Quite useful. I put on the nightly build. The camera works slightly more often. Probably 80%. Mostly a reboot fixes it now. But still far from being good.