yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] miomaguro:
Does anyone with the 14112016 Nightly experience with frequent wifi disconnections? It seems like my maguro struggles connecting to wifi networks and after connection, it loses it quite rapidly if no activity is done. It takes several trials before connecting and really few minutes to lose the connection. What is the experience of other users?
[Samsung Galaxy Nexus] PGHammer:
I went to UA from CM13 (but NOT due to any 13-related bugs)

The only reason I left 13 was because UA 7.1 snuck up on me and I wanted to give it an honest shot - basically comparing MM to N heads-up. I had no issues with 13 - however, I have had no issues with UA 7.1 either (which is why I'm still there). I'm not a triskidelophobe (fear of the number 13) - if anything, Friday the 13ths tend to be my luckiest - not unluckiest - days of a month. The issue with pico merely STARTED with CM13; however, it applies to all versions of GApps later than Lollipop; it may well apply to Lollipop as well. (While the GNex has larger default storage than all except the most recent phones, it doesn't support physical microSD cards.) To be honest, I DID have my issues with the comparable Omni 6 (the animation runs FAR too long with Omni 6, which is why I booted It off the GNex after less than an hour); so CM13 trails only UA 7.1.
[Samsung Galaxy Nexus] miomaguro:
Yesterday I installed the latest Nightly (20161204) and at first it seems to perform better with respect to the above wifi issue: it still struggles a bit to properly connect to the network but (for now :fingers-crossed:) it seems with less troubles. I've made a screencast of the wifi issue, if anyone wants to see what I'm talking about.

However: so far so good!! Many thanks!
[Samsung Galaxy Nexus] vortex-5:
If you're having wifi issues still you should try turning on Legacy DHCP under the developer options. It's generally accepted that that's what's causing it.
[Samsung Galaxy Nexus] miomaguro:
Thanks for the suggestion: I've turned it on. Let's see if you got the right point! :fingers-crossed:
[Samsung Galaxy Nexus] hgmichna:
Legacy DHCP to solve Wi-Fi problem

Please remember to report your results after testing. I am probably not the only one who is curious about this.
[Samsung Galaxy Nexus] Valberu:
Xposed Issue

Hi everyone,

Did you know why xposed modules put the device into bootloop with the latest builds ?

I'm running the 20160820 Snapshot with no problems about xposed, but if i upgrade it with next nightlies, enable any module will result in a bootloop. I've tried any kinds of wipe, clean install, sdk version etc...

Thanks for your help :)
[Samsung Galaxy Nexus] miomaguro:
After a couple of days of testing I must admit that the wifi is much more stable and rarely loses the connection. It also struggles only for a short time and after the establishment it stays connected. Than, thanks! It seems like that was the main issue: the new DHCP frequently goes mad with our device and lollipop DHCP greatly improves the wifi connectivity.
[Samsung Galaxy Nexus] vortex-5:
Yeah the legacy DHCP seems to be the magic fix for most people. Now the developers haven't gone through and assessed why the Marshmallow DHCP is different enough to cause an issue but most people say that it tends to get "stuck" usually if you reboot the device it will fix itself but then get stuck again after a few hours.
[Samsung Galaxy Nexus] Mariano.:
Well, i dont know if is my phone working bad or this rom. First, start working very very fast, then one or two day later, the pone start to stuck in Twitter, whatsapp, work very very slow until reset them, the battery down (70% to 18% for example). Also, camera didnt work sometimes.

Tomorrow i will install another rom and comment.

Sorry for my bad english
[Samsung Galaxy Nexus] musical_chairs:
Something with the recent kernel security updates is breaking xposed. The same thing happens on my build of Unlegacy-Android 4.4. It's possible that something is slightly awry in the kernel updates that is causing the issue; it's more likely that xposed uses a method that is now considered a security flaw and has been patched. If that's the case, hopefully xposed will be updated to work again on newer kernels. Otherwise, somebody is going to need to bisect the kernel to find the offending commit. (this would require seven or eight test kernel builds and a basic understanding of git bisect.)
[Samsung Galaxy Nexus] Valberu:
Thanks for thoses informations !

BTW, how do you guys deal with the "mobile radio active" bug ?

The only solution i've found was to use the "smart network" xposed module to turn off data when screen off.

This bug drain the battery so much that I can't use my phone without this module.
[Samsung Galaxy Nexus] osm0sis:
Is this something different than the zygote socket whitelist that rovo worked around in Xposed 87?
[Samsung Galaxy Nexus] Android-Andi:
You should be right. Here's the rom changes (pushed to CM after i updated UA): https://review.cyanogenmod.org/#/q/topic:asb-2016.10+(status:open+OR+status:merged)

But it is OT here and not sure if it is the right place to discuss Xposed or a different rom.
[Samsung Galaxy Nexus] el_ruwen:
Just in case someone struggles with the same issues. I removed encryption, now the cam seems to work more often. But still not 100%.
[Samsung Galaxy Nexus] PGHammer:
No Idea; However....

No idea; however, I haven't had ANY reason to run xposed so far; if anything, I have been finding reasons NOT to run xposed (mostly conflicts with existing apps or ROMs) - for example, if you want to use Google Assistant (or the Pixel Launcher), currently you have to be as plain as possible.
[Samsung Galaxy Nexus] Valberu:
I guess, because the v87 does not work neither

Edit : It finally work with the 20161219 nightly
[Samsung Galaxy Nexus] Daniol71:
Do I need TWRP to install CM13? I'm trying with CWM and I get a bootloop. Sorry if I'm late to the party, I've been waiting for hardware replacements for my GNex from Hong Kong since my sister broke most of it. Eager to try out Marshmallow in the GNex since the last thing I had on it was KitKat.
[Samsung Galaxy Nexus] osm0sis:
Yeah CWM is pretty ghetto compared to a currently maintained recovery like TWRP.
[Samsung Galaxy Nexus] Daniol71:
Thanks, had bootloops with TWRP as well, turns out the version of SuperSU I was flashing caused problems (v2.46). I know there is a newer version, but v2.46 is the one available as a zip download. I'll download SuperSU from the Play Store instead.
[Samsung Galaxy Nexus] rahimali:
You can download the flashable zip of the latest version (v2.79) from this page.
[Samsung Galaxy Nexus] fr_awd:
I installed : cm-13.0-20161212-NIGHTLY-maguro and I cannot seem to get my laptop via ubuntu 16.04 to detect my phone. I have developer options enabled with adb root access, android debug and usb config set to mtp. Basically my laptop no longer detects my phone. My phone displays nothing but the charging icon. Adb devices detects nothing

I started a clean install with stock android 4.3 takju and then installed cm 13. Also I had usb debugging working about an hour prior to CM 13 as I was using android tools to push the files.

I'm out of ideas on how to get my usb debug of laptop to detect my phone
[Samsung Galaxy Nexus] Daniol71:
Does your phone respond to being plugged into the laptop? Do you get the file transfer notification? The micro usb port on the GNex is not the best quality and many people (including myself) have had problems with it not properly making connections after a while. In fact, I've had to replace the port, but there are two other options you can try first.

Before you try these, make sure it's not a software problem.

1) Blow into the port to remove any dust. If you have compressed air that's even better.

2) Remove the battery. Get a small, non-conductive tool and carefully push the "tongue" inside the port upwards a bit. Alternatively, try a different cable.

---------- Post added at 01:40 PM ---------- Previous post was at 01:33 PM ----------

Thanks, seems like I used an older SuperSU download page yesterday (thanks Google search). Trying to install SuperSU, even from the Play Store and rebooting into TWRP still causes a bootloop after the installation. I'm sticking to the built-in root manager for now. Two questions:

Is it recommended to make the system Read & Write like TWRP asks when you go into recovery? Is it recommended to allow TWRP to "fix" root access after an installation? I usually select no for both options, but thought that might be why I'm having the issue with SuperSU.
[Samsung Galaxy Nexus] runekock:
You should always allow TWRP to make System writable. Otherwise, it can't flash any rom modifications. The only reason it asks is that some stock roms won't update if system has been modified (possibly they fail safetynet too).

Normally, you shouldn't need to let TWRP fix root. If your rom is prerooted, it shouldn't even ask, or if you flash supersu, that does the trick.
[Samsung Galaxy Nexus] fr_awd:
You know I tried switching cables and blowing into the port, which did nothing. I tried all of that except bending the tongue upward! Just bent the tongue up. Now usb debug prompts pop up and the laptop detects my phone. Thanks buddy:D
[Samsung Galaxy Nexus] Daniol71:
Glad I could help! Just a heads up that the bending trick might not work forever, you might have to replace the usb port in a year or so. That's a pretty easy fix and you can find replacements on Amazon and Ebay quite cheap. Here are some details: https://www.ifixit.com/Guide/Samsun...o+USB+Charge+Port+&+Main+Mic+Replacement/9641

Like I mentioned in an earlier comment, my sister completely wrecked my GNex so I've replaced almost every part of it, the only original part left is the motherboard :D It was surprisingly easy to disassemble and reassemble!
[Samsung Galaxy Nexus] Progressive82:
Is there some kernel for cm13. I would to overclock.
[Samsung Galaxy Nexus] MayuraDeSilva:
cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-maguro.zip

Does the new SNAPSHOT build (cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-maguro.zip) include all the fixes until 12 / 21?

Or the cm-13.0-20161219-NIGHTLY-maguro.zip is the latest?
[Samsung Galaxy Nexus] everslick:
no mobile data connectivity

I also lost mobile data connectivity after the switch to CM13 (from CM12) - as reported by others. my provider is spusu.at which roams on one.at. i configured the APN (mass.at) and activated data roaming. i did a factory reset before upgrading. i tried 3 different snapshots during this year - all the same - no mobile data. anything i can do to help fix this?
[Samsung Galaxy Nexus] pamudithazenanjana:
Don't know whether this is a bug or not, but when I flashed the latest SNAPSHOT build (cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-maguro.zip) the overall look was off white for some reason. Almost as if the color calibration went wrong. The whites were too warm that it looked as if there was a yellowish glow on screen.
[Samsung Galaxy Nexus] mlsoftlaberge:
[MENTION=2633638]Ziyan[/MENTION], Do you intend to continue this rom after the closing of Cyanogen?

It seems the download servers are already down.

I am worried about the future of my favorite rom.
[Samsung Galaxy Nexus] frusso3:
Hi guys, the last snapshot I installed it but I noticed that the volume of notifications is very low. How can I do to fix it?
[Samsung Galaxy Nexus] daytonahemi08:
Loving the ROM is 7.0 coming or am I asking to much ,:confused:
[Samsung Galaxy Nexus] vortex-5:
So with cyanogen mod now closing shop what's the next logical transition path for us? Project Unlegacy or Linage OS?
[Samsung Galaxy Nexus] frusso3:
Also, why the internet and youtube videos are always slow scrolling?
[Samsung Galaxy Nexus] vortex-5:
Does anyone know when the last snapshot was based on build wise is the nightly Dec 19 cm-13.0-20161219-NIGHTLY-maguro.zip newer than snapshot Dec 20 cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-maguro.zip?
[Samsung Galaxy Nexus] vortex-5:
I just went back and reflashed the nightly it seems the nightly has less bugs than the snapshot so if you're currently on that don't update.
[Samsung Galaxy Nexus] jrs007:
Has anyone managed to solve the GPS problem?
[Samsung Galaxy Nexus] hgmichna:
GPS

Which GPS problem?

I just updated to cm-13.0-20161219-NIGHTLY and tested the GPS. It worked quickly and precisely.

That said, the GPS chip in the Galaxy Nexus has always been somewhat slow and occasionally unreliable. I believe that is a hardware problem. Newer GPS chips are far better.
[Samsung Galaxy Nexus] bugsey:
Always "on charge"

hi!

i have TWO maguros in my family.

after update 13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-maguro boths phones always shows ON CHARGE indicator on top of screen.

what is it?
[Samsung Galaxy Nexus] mlsoftlaberge:
I am very sorry to inform my fellow Galaxy-Nexus users, that the LineageOS github for replacing cyanogenmod, is totally inactive in regard of the Galaxy-Nexus (maguro) since the day of the closing.

About 150 differents brand of phones are ready to compile and publish, but maguro activity is totally dead.

I fear we are stuck with the last Cyanogen-13 on our maguro and that no more development will be done on our old phone.

Can someone try to tell me how to make maguro be a part of the new LineageOS?

Can I take the job and do it myself?

Will someone be willing to help me ?

All those existential questions are keeping me up at night!
[Samsung Galaxy Nexus] bamtan2:
CM is built from AOSP, and in our case [MENTION=2633638]Ziyan[/MENTION] and friends have done a good job of keeping both working. Now that CM is gone, it is most important we support the AOSP ROM at https://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574 ... then if someone wants to make more ROMs out of it, whether Lineage or anything else, that is good too :) "Unlegacy" is the new name for this Galaxy Nexus AOSP ROM.
[Samsung Galaxy Nexus] miomaguro:
I definitely agree: I tried both CM13 and Unlegacy and, IMHO, the latter is way better than the former, thank to Ziyan & Co.... Hail Gnex!
[Samsung Galaxy Nexus] wooser:
So, seems that our maguro has been definitely abandoned: up to now it's not present in the target list of Lineage OS build: https://review.lineageos.org/#/c/155809/80/lineage-build-targets
[Samsung Galaxy Nexus] bamtan2:
​

The same people who made CM for Galaxy Nexus now make Unlegacy:

https://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574
[Samsung Galaxy Nexus] vortex-5:
I've tried both as well Unlegacy is smoother and faster than CM13 at this point seeing how the last version was a nightly the snapshot was at an earlier point.

If you're looking for your next firmware currently Unlegacy 6.0 is more stable and that's the one I'd go to until 7.1 development gets closer to stable status. Right now for some people GPS seems to be an issue and there is very little ram but these issue tends to iron themselves out.

6.0 has a lot of ram free and does not have the hiccup issues that CM13 seems to have after unloading apps.
[Samsung Galaxy Nexus] m3nu:
Also tried Unlegacy last night. 7.1 didn't boot, but 6.0 works very well. Not missing the CM modifications too much.
[Samsung Galaxy Nexus] dumas777:
> I tried both CM13 and Unlegacy and, IMHO, the latter is way better than the former

Little bit of sour grapes on that? You know I wouldn't cry a bit if Kirt McMaster got bone cancer right about now. Guess time to make the most of yet another asshat in society crapping the bed for everyone else due to greed. Its just a shame they outnumber givers like Ziyan 100 to 1. Don't get me wrong Unlegacy is damn good and am grateful for having it as a fall back plan but having to switch (Android way too much of security sieve to not keep updated at least monthly) before the 7.1 roms are ready is not ideal and just sad to see CM ruined due to greed, incompetence and pettiness.
[Samsung Galaxy Nexus] Lore1:
There are different Galaxy Nexus devices. Unlegacy project does develop for device "tuna". Does Unlegacy also work on device "maguro"?
[Samsung Galaxy Nexus] bamtan2:
Yes! But this is not the Unlegacy thread.

PS: There is Tuna Maguro (GSM) and Tuna Toro (CDMA)
[Samsung Galaxy Nexus] wooser:
I'll definitely miss those and all the platform support behind. BTW anyone tried to compile an unofficial build of LineageOS?
[Samsung Galaxy Nexus] vortex-5:
For people that are not yet familiar with the Galaxy Nexus lineup it works like this

The base code name is tuna that is all Galaxy nexus are tuna devices.

Maguro (japanese term for blue fin tuna) is the GSM radio version

Toro (japanese term for the fatty part of the tuna) is the LTE radio version
[Samsung Galaxy Nexus] hgmichna:
No, not LTE. The Galaxy Nexus never had LTE. I guess you meant CDMA, the old US cellphone system.
[Samsung Galaxy Nexus] vortex-5:
There was an odd verison LTE variant with 4G branding I think. It went by the model number i515: http://www.gsmarena.com/samsung_galaxy_nexus_i515-4301.php
[Samsung Galaxy Nexus] hgmichna:
Galaxy Nexus, Maguro and Toro versions, LTE version

Oh, I didn't know that. Thanks!

But I think Toro is still the CDMA version. Can anybody confirm this?
[Samsung Galaxy Nexus] vortex-5:
Yes it was CDMA it was produced only for the verizon network as far as I know and it also happens to be LTE on their network (early generation of course)
[Samsung Galaxy Nexus] musical_chairs:
..and Toroplus, the one everyone keeps trying to forget, a model exclusive to the U.S. carrier Sprint, an LTE version with embedded sim card.

The Tuna ROMs work on all three variants. Maguro has the most developers working on it, so it's the best supported of the three. Plus the 'fat tunas' have some weirdness with their LTE over CDMA radio layers that add to the fun.
[Samsung Galaxy Nexus] musafercom:
cm 13 latest snapshot dated 21/12/2016

Is possible to get this

https://download.cyanogenmod.org/get/jenkins/189503/cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y2-maguro.zip

anywhere possible to download as cyanogenmod download page seems to be not working anymore

thanks & best regards
[Samsung Galaxy Nexus] osm0sis:
All builds of CM (ever!?) are here: http://mirrors.reflected.net/pub/get.cm/jenkins/?C=N;O=D

You'll just have to hunt through and find the final build. :good:

Edit

: ;)

maguro: http://mirrors.reflected.net/pub/get.cm/jenkins/189503/

toro: http://mirrors.reflected.net/pub/get.cm/jenkins/189524/

toroplus: http://mirrors.reflected.net/pub/get.cm/jenkins/189525/
[Samsung Galaxy Nexus] musafercom:
thanks

thanks so much thats helps
[Samsung Galaxy Nexus] osm0sis:
Anyone know if the final snapshot is newer code than the final nightly though? That's the real question.
[Samsung Galaxy Nexus] vortex-5:
In my testing the final nightly has a few more bug fixes than the snapshot. For one landscape keyboard on AOSP keyboard works in the final nightly it does not on the final snapshot opting to only take up half of the screen and appearing broken most of the time.

I'm assuming the final nightly was rushed.
[Samsung Galaxy Nexus] ExecutorElassus:
I just checked the LineageOS site (which seems to be claiming the mantle of CM's successor) and maguro isn't on there. Do any of the maguro devs have contact with the LineageOS teams? Is maguro going to be moved there, or will development continue here, more or less independent? I ask because my phone has fallen back into that random-reboot-freeze-coldboot-no-SIM-card-reboot cycle again, and it's not in a very usable state.

Is it possible that this is just hardware failure, that the phone is plain dying? Anybody else having these kinds of issues? My phone reboots at least twice a day, usually more, almost always when idle, and very often either freezes in the reboot, or boots up but doesn't find the SIM card. Is there something I can do to mitigate this?

Cheers,
[Samsung Galaxy Nexus] osm0sis:
LineageOS is the actual successor to CyanogenMod, founded by Steve "cyanogen" Klondik and everything.

During the transition all the CM maintainers made the switch as well, so you'll see in the various threads that between CM and LOS the only thing that has changed is the branding. Now that raises the question of whether [MENTION=2633638]Ziyan[/MENTION] opted out of being maintainer when it came up, was too busy to make the switch in a timely manner, or whether Lineage intentionally dropped maguro.

The last scenario would be surprising since I believe I recall seeing other CM13 devices that have made the jump over as LOS13. Hopefully he can pop in and clarify. :)
[Samsung Galaxy Nexus] bamtan2:
I would encourage anyone who wants LineageOS on Galaxy Nexus to click the profiles of some of the developers on this forum and donate $$$ to them! I've donated to [MENTION=2633638]Ziyan[/MENTION] and others because they're why the phone works right now! I don't donate and demand work be done, I donate because of work they've done. It's worth it! These people are volunteers doing work on their free time.
[Samsung Galaxy Nexus] hgmichna:
Unlegacy

[MENTION=2633638]Ziyan[/MENTION] is active in the Galaxy Nexus Unlegacy AOSP project, which may be the most interesting alternative. Check here:

https://xdaforums.com/sitesearch.php?q=Galaxy Nexus AOSP Unlegacy

---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------

I have the same problems with the last CM13 nightly. Might check Nougat Unlegacy project. See other post.
[Samsung Galaxy Nexus] jrs007:
Try testing out of the wifi network.

In 3g only
[Samsung Galaxy Nexus] hgmichna:
GPS

Works without any problem here, but I had a GPS fix shortly before.

The GPS of the Galaxy Nexus has never been very good, not with the stock ROM either.

Without any data connection it is even worse, takes ages until first fix.

But we have to consider it normal for this phone.
[Samsung Galaxy Nexus] amine a.b.i:
is it a whole 1gb of ram??
[Samsung Galaxy Nexus] Vara83:
Hello, I know i am a little off-topic, but there is any chance to see a Lineage OS 14.1 for maguro?

I read that unlegacy project was at October 2016 version and CM13 at December 2016
[Samsung Galaxy Nexus] vortex-5:
This has change the latest build of unlegacy has security updates mid January so it's newer than CM13

(this is for unlegacy 6.0.1 I'm sure 7.1 is the latest)
[Samsung Galaxy Nexus] nailyk:
I didn't read the full history :s but looks like there is no LineageOS for maguro.

Can someone confirm this please?
[Samsung Galaxy Nexus] :
Yep, no LineageOS for our maturity :(

But there is a really good 7.1.1 unlegacy AOSP Rom: https://builds.unlegacy-android.org/aosp-7.1/tuna/

Try it.
[Samsung Galaxy Nexus] nailyk:
Thanks for the answer.

I missed all the Lineage functions on it.

That is why I start building the 13.0 but just encounter a weird error:

hardware/ti/omap4/pvrsrvinit/pvrsrvinit.c:8: error: undefined reference to 'SrvInit'
collect2: error: ld returned 1 exit status

On a two year old code :s

Will try to fix the build asap to keep updating this device.

P.S.: Maybe the 7.1 source could be helpful :)
[Samsung Galaxy Nexus] _yen_:
https://github.com/Unlegacy-Android...mmit/cf961527cc979f0363761b67c635c4afe21f4e9b
[Samsung Galaxy Nexus] nailyk:
No way, I keep getting:

/var/jenkins_home/workspace/CM-13.0/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/../lib/gcc/arm-linux-androideabi/4.9.x-google/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lsrv_um_SGX540_120
collect2: error: ld returned 1 exit status

at pvrsrvinit target

Even after adding vendor/samsung/omap4-common/Android.mk

And I don't get why cm-13.0 didn't build out of the box...
[Samsung Galaxy Nexus] Android-Andi:
You need vendor/ti now https://github.com/TheMuppets/proprietary_vendor_ti

Edit:

There's something more needed in the device tree. I'll push it to gerrit in the evening.

Edit2 to make it short:

You need https://github.com/Unlegacy-Android...mmit/cdfe0c7df7894338093cf43ba0eecaa72af0b60c

Also you need to move

TARGET_BOARD_OMAP_CPU := 4460

From BoardConfig.mk to device.mk

( https://github.com/Unlegacy-Android/android_device_samsung_tuna/blame/aosp-6.0/device.mk#L25 )

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] :
That would be fantastic!!! Keep us posted! Thanks for your support!

Yep, I'm missing the LineageOS functions too.