yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nikodr:
2g not working cannot select it at all. Is this bug of cm13? Only 3g is available for my maguro.
[Samsung Galaxy Nexus] eternal70:
Use pico gapps, then
[Samsung Galaxy Nexus] Ullebe1:
Thanks for this rom, upgraded yesterday from CM12.1 with at dirty flash, and everything seems to be working great!

It even seems that the bug I've had across every single rom with colour emoji I've tried is gone. The bug consisted of certain emoji's always rendering with their legacy black versions, instead of the graphical version, even though the graphical version was present in NotoColorEmoji.ttf.

But thanks again for the great work, it is a pleasure to see this device still kicking!
[Samsung Galaxy Nexus] :
You must install nano gapps from before 02/15 because it's small enough to install. The ones after that give you that error
[Samsung Galaxy Nexus] bigflea:
Where can I download the nano gapps before 02/15?? On every download page (OpenGapps) I can only download the current version! :((
[Samsung Galaxy Nexus] Mimamau:
There's a link to older releases:

https://github.com/opengapps/arm/releases/

But I haven't tried to go back so far.
[Samsung Galaxy Nexus] bigflea:
It works!! Thanks a lot!! :)
[Samsung Galaxy Nexus] BlessOd:
Your 5.1.1 is the best, lets try 6.0.1. Thanks!
[Samsung Galaxy Nexus] Oehr:
Thanks for this!

I sure hope CM includes setting the default USB mode soon. That new "feature" of M is annoying!

P.S. the usb settings in the dev menu dont seem to do anything?
[Samsung Galaxy Nexus] amine a.b.i:
im using cm 13 right now should i flash this lineageos rom or i continue using the cyanogenmod ?? any suggestions ??
[Samsung Galaxy Nexus] Android-Andi:
Switching from CM to Lineage requires a clean flash. CM is continued as LineageOS. You don't get any updates for CM, but you'll get on LineageOS.

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] nailyk:
May be interesting.
[Samsung Galaxy Nexus] amine a.b.i:
no i mean is the lineageos 13.0 more stable smoother and faster than the cm 13 or not ? if the los better than cm so i will flash it

so which better cm 13.0 or los 13.0?
[Samsung Galaxy Nexus] guest4711:
I would flash LOS, because you will never get updates for CM anymore... Flashing CM is a "dead end".
[Samsung Galaxy Nexus] nailyk:
It is the same rom, only name change.
[Samsung Galaxy Nexus] Guichuan:
woooooow, so great, can download now, thx ! thx Ziyan !
[Samsung Galaxy Nexus] MrFlashGame:
Hey there,

i've found another bug in the newest nightly: The shell (which you can activate in the dev settings) doesn't appear if you activate the setting for it. It seems like the data for the shell is in the build but there is no way to activate it. Could somebody confirm this please?

Greetings, Nils :)
[Samsung Galaxy Nexus] amine a.b.i:
how much ram ?? please reply
[Samsung Galaxy Nexus] MrFlashGame:
Thanks to CMA, the system has access to 0,97 GB of the 1GB Ram. I hope i could answer your question. I use my maguro still as my daily driver and i have aprox. 800mb used.

Greetings, Nils :)
[Samsung Galaxy Nexus] tenchi-man:
I installed lineage-13.0-20170312-nightly-maguro-signed.zip, as the updater doesn't work, how can I upgrade to the latest nightly? Do I need to install Open Gapp again after every upgrade? Thx
[Samsung Galaxy Nexus] nu pogadi:
I downloaded the latest nightly to my PC, then copied it to the internal SD card, then rebooted into recovery and installed the zip.

I did not perform a wipe ( as in a normal update) and rebooted the system. Everything OK.

CAUTION: I do not have G-Apps installed on my device as I want it Google-free. Thus, I can not tell whether you have to re-install your G-apps.

But I would say no, because you don't switch between different ROMs or Android versions.
[Samsung Galaxy Nexus] MrFlashGame:
It's the best if you use a custom recovery like TWRP (Google is your friend). In TWRP you can wipe the System partition and simply flash the newest nightly (make sure to turn off zip signature verification, it's seems to be uncompatible with the latest nightly) and all other flashable zips you need (e.g. the addon su, open gapps pico). After succesfully flashing your zips i would recommend to wipe dalvik and cache partitions. If everything is done you just reboot. You shouldn't loose any data but make sure to always have (external) backups!

Greetings, Nils :)
[Samsung Galaxy Nexus] superottik:
Does anyone have problem with notifications on Lineage OS 13 20170318 nightly maguro ? Text messages and calendar notifications do not appear on bar. Another problem is with updates when I check updates I have message: "The update check failed. Please try later or check your internet connection.
[Samsung Galaxy Nexus] MrFlashGame:
[DELETED]
[Samsung Galaxy Nexus] Lore1:
Which overclocking kernel do you suggest for this?
[Samsung Galaxy Nexus] MrFlashGame:
Hey there,

After a little bit of using the latest los build (which is already really stable btw) i've found an issue on my device. I don't know whether it is a hardware defect or a software depended bug, but sometimes i loose almost all sensors (like the gyroscope) of the device and they aren't working anymore (CPU-Z shows also no more sensor activity). A reboot does fix this problem. Does anybody else have this issue? I can send logs if needed.

Greetings, Nils
[Samsung Galaxy Nexus] bamtan2:
that's a good bug report! exactly the kind of intermittent issue that user testing needs to find. I suggest that it's probably a software bug and the guys here would like to look at the logs. I think you can capture them well with the app syslog https://play.google.com/store/apps/details?id=com.tortel.syslog
[Samsung Galaxy Nexus] MrFlashGame:
Here are my logs. I captured them while I had this bug, it should be every log inside the zip. If something is missing please let me know. I hope this is useful for you devs out there ;)

Extra note: I use LSpeed, this App could maybe part of my problem but i had never problems with this app before and i used exactly this version of the app already with the 2 previous weeklys. Just for you to know

Greetings, Nils :)
[Samsung Galaxy Nexus] kimon_:
bug in flashlight

Hi!

When build-in flashlight is on and phone goes to standby - phone hungs up and can't boot after restart.

Phone can boot only after disconnect battery.
[Samsung Galaxy Nexus] droiduzr2:
[MENTION=2633638]Ziyan[/MENTION]

If you are looking for more RAM, what about removing all the audio files.

There is alot of audio files e.g. ring tones.

I suggest leaving 2 or 3 small files and offer a zip file for ppl to flash if they want more ring tones.

Just a suggestion
[Samsung Galaxy Nexus] Calvido:
I think you are wrong, RAM <> Storage your confusing term's

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] pepelillo:
Hello.

Does this rom support otg data while charging (even fast charging)?
[Samsung Galaxy Nexus] andifor:
Additional Permissions in LineageOS 13

Hi

I'm still with CM12.1 but gave lineagos 13 (nightly 20170401) a try. But I still have the same issue mentioned 6 month ago (see quote above).

Does anybody has a clue why this is happening, where I can try to help debug, know a fix for this? With this issue, I can't use lineagos on my maguro and I finally would have to switch to some other mobile phone. Shame, as it runs perfectly well otherwise... :-/

So any help would greatly appreciated.
[Samsung Galaxy Nexus] ExecutorElassus:
question: is it possible to sideload this ROM onto a phone with the previous cm-13 installed? I use encrypted storage, and my version of TWRP (the custom version ziyan had here last fall) can't mount it most of the time.

Cheers
[Samsung Galaxy Nexus] MrFlashGame:
Nope, unfortunately not. :crying:
[Samsung Galaxy Nexus] guest4711:
I did not recognize this behavior until now, cause emailing either with either without attachments works well.

When reading your post I checked my settings. I cannot enable the extended rigths for neither email nor k9mail. But everything is working as expected. So I think these rigths are neither used nor needed.

[Some more testing: Same behaviour on Slim-6.0.1. On RR 5.8.2 (Android 7.1.1) same behavior for k9mail, settings possible for standard-email. But no difference wether it's enabled or not. So only a cosmetic problem for me.]

---------- Post added at 06:42 AM ---------- Previous post was at 06:17 AM ----------

none. oc neither needed nor supported.
[Samsung Galaxy Nexus] andifor:
Thanks for checking. The mail app serves only as an example, because it's available for everybody. I have other apps not working without additional permissions.

I'm surprised, that no other user reported this, but I guess, there are only a few Galaxy Nexus users left :o)
[Samsung Galaxy Nexus] bamtan2:
I found one reference to this problem with google, not sure what you'll make of it though: https://xdaforums.com/showpost.php?p=65252927&postcount=2812
[Samsung Galaxy Nexus] guest4711:
I tested on other devices, too (with the same results: I cannot grant these special permissions). And I did not see any difference whether these special permissions are granted or not.

So if this should be a problem, it should be discussed elsewhere because it does not belong to this particularly ROM....

On the thread mentioned above by [MENTION=553655]Bantam[/MENTION]2 you will find:
[Samsung Galaxy Nexus] xsycox:
Yes, yes, yes, just write an e-mail to the app author about adding the rights management

or change to another app. There is really not much to do otherwise, because the new

management is strict (and useful in being so).

---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------

At one point, I was so pissed, that I changed two apps in use.

One was Kaiten Mail, which I exchanged with K9 Mail. The other one I cannot remember.
[Samsung Galaxy Nexus] andifor:
Now I'm confused. Either it's an Android feature to support additional permissions or not. Android even has a user interface for this. Why should an app developer care, if a certain flavour of Android supports these permission or not?

Anyway, thanks for looking into this issue. I dropped the topic and am looking for a different mobile with LOS support.
[Samsung Galaxy Nexus] guest4711:
As I understand it depends on API-level and the manifest. You may either use on global permissions (e-mail) or detailed permissions (read emails, read attachments, write emails,...)
[Samsung Galaxy Nexus] xsycox:
Wtf?! What certain flavour of Android are you talking now?

It is just a new rights management beginning in Lollipop. Of course, Marshmallow, Nougat and upcoming versions of Android have this new rights management, too.

And app developers also have to update their programming, if they want to have their apps working properly.

What is there not to understand?
[Samsung Galaxy Nexus] MrFlashGame:
Hey there, I just wanted to report some bugs I've found while using LineageOS (Nightly 042917):

[The SIM Manager is disappeared. The app is on the device but there is no way to open it as a normal user. I don't know why but once I the app appeared and I tried it out but it didn't work (Infinite loading circle after anything was clicked.)]

The translations are sometimes changing back to English and after a restart back to german. (After a reboot)

The wifi loses sometimes the connection but I have the feeling that it's getting better since a couple of weeks.

After manually flashing the newest nightly the updater says there is an update available and offers me to flash the newest nightly again.

I have sometimes awkward screen flashes and blackscreen after the boot and the "Android is upgrading" screen.

And one time I had the bug that the camera has lost the connection (fixed by reboot)

Greetings, Nils :)

If you need logs, more details or something just let me know.

EDIT: The camera crashes if I change between front and back camera (evertime reproducable, if I reopen the camera app the camera has changed)

[ ] = not everybody is affected by this bug
[Samsung Galaxy Nexus] hgmichna:
SIM Toolkit

Do you mean the SIM Toolkit? I just installed Lineage OS 2017-04-29 and have the SIM Toolkit app. I tested it with a Kenyan Safaricom SIM card, which has an extensive menu system, mostly for the Kenyan mobile payment system M-PESA. It appears to work just fine.
[Samsung Galaxy Nexus] MrFlashGame:
Yes I mean the SIM-Toolkit. It should work (it worked in CM 11) but for me it doesn't (E-Plus Network, Fonic is my provider)
[Samsung Galaxy Nexus] hgmichna:
SIM Toolkit

One quick check I would do first is to put the SIM card into another Android smartphone and see if the SIM Toolkit works there, just to be sure it is not some problem of the SIM card itself.
[Samsung Galaxy Nexus] nailyk:
AFAIK it is a global issue fixed on N.

IIRC only not 4G sim get the toolkit. Something odd like this.

On 12.1 didn't work too.
[Samsung Galaxy Nexus] hgmichna:
SIM Toolkit

Why then does it work just fine in my LineageOS 13.0 for the Galaxy Nexus? Just tested in the 2017-04-29 nightly. And this is a new 4G SIM card (though my Galaxy Nexus cannot use 4G).
[Samsung Galaxy Nexus] Calvido:
Hi people, I test this rom about 3 months and en every nightly update I found the same problem. Sometimes when turn on the phone, in the screen when you put your sim card pin in middle the action this reboot and when this come again to first screen now not question you​ sim pin and can't make phone calls or send SMS but you can receive calls and SMS. Only way to solve this is reboot again. This happen to me also when the phone random reboot. I don't know if they understand me. Sorry for my English

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] hgmichna:
SIM Recognition

I have a similar problem. When I power up the phone, the SIM card is never recognised. I always have to reboot a second time.
[Samsung Galaxy Nexus] nailyk:
Am not sure about the 4G thing. But I noticed this problem on my maguro (don't remember if it was with 12.1 or 13.0). One sim card the toolkit appear (orange) the other it doesn't (sfr). I will make some further tests.

Are you encrypted?
[Samsung Galaxy Nexus] hgmichna:
SIM Toolkit

No, never. Encryption could introduce new risks. I am too weary for that.

There seems to be a bug somewhere that rears its ugly head only under certain circumstances. Some people are lucky, like myself, others see the bug.
[Samsung Galaxy Nexus] GerardJ:
LineageOS updates

I'm very happy with this ROM. My present version: 13.0-20170429-NIGHTLY-maguro.

One question:

I'm using the LineageOS Downloader (Premium) to install the nightly's, primarily because this app allows me to (re-)install SuperSU at the same time, thus re-rooting my phone. Subsequently, I re-install TWRP-Recovery using the "Official TWRP app".

Sofar, so good. However, for some reason, the update function (Settings - About Phone - LineageOS updates) doesn't notice the update and continues to show that a "new" update is ready for downloading and installation: the update that has already been installed... Similarly, icons in the task bar frequently give me the message that an update is ready. Initially, I had set the checks for updates on a monthly basis (new nightly's so far appear every week), now I've set the update-check as "manually". Hope that this helps. Is this ROM-related or app-related? Any suggestion?
[Samsung Galaxy Nexus] hgmichna:
Updating LineageOS with root

Perhaps you are doing it in a more complicated way than what is required, but I don't know everything. I have TWRP installed and use the built-in updater of LineageOS.

I hope you are aware that LineageOS has its own root functionality, provided as a small ZIP file, and a similar ZIP file to unroot whenever you like.

When you use the built-in updater, you don't have to reinstall root; it just stays. So altogether I don't have to do anything besides using the updater.

The update check relates to the LineageOS ROM and has nothing to do with apps. You can set it to manually without any problems.
[Samsung Galaxy Nexus] GerardJ:
Thanks, I'll try to do it "the easy way" next time.

Earlier on, I had read that - other than the CyanogenMod ROMs - the LineageROMs didn't have a built-in root functionality. This corresponded with my experiences that root was lost after installation of a LineageOS ROM. Initially, I re-rooted with adb and fastboot commands. However, re-rooting in this manner stopped working around the beginning of April (after the reboot following the command 'adb reboot bootloader', the connection with the phone was lost, subsequent commands only resulted in ' < Waiting for device > '...). Then I used Oding 12.3 to root the phone again. Eventually, the use of the LineageOS Downloader much simplified the process...
[Samsung Galaxy Nexus] hgmichna:
Updating LineageOS with root

On https://download.lineageos.org/ the last choice on the left sidebar is, "Extras", leading to https://download.lineageos.org/extras/ . That is where you find the addonsu- und addonsu-…-remove- ZIP files for download.

Flashing these enables or disables the root function built into Lineage OS.

I think this is an elegant solution. If you have apps, like payment systems, that do not work with root, you can remove the root function entirely. If you have installed root, you can still disable it in the developer settings menu.
[Samsung Galaxy Nexus] GerardJ:
Thanks a lot. I tried to flash this file earlier on, but received an error-message (in red)

"Update process ended with signal: 4

Error installing zip file '/sdcard/addonsu-arm-signed.zip' "

My basic problem is/was that - after having lost root when updating - TWRP recovery is no longer accessible, because it requires root...

Therefore I was happy to find an option to install root access in one stroke immediately after the update.

I expect a new nightly tomorrow, and try again then.

From May 7th till 16th, however, I will be on a short holiday, being unable to respond on further replies...
[Samsung Galaxy Nexus] hgmichna:
How to flash TWRP

The TWRP Manager app requires root, but you can easily and quickly install the TWRP recovery, after connecting the phone to a computer via USB, with the command:

fastboot flash recovery twrp.img

Change twrp.img to the actual file name.

You have to have a current fastboot.exe or similar on the computer, of course.
[Samsung Galaxy Nexus] GerardJ:
That used to work with me all right . . . until earlyApril this year. (Maybe - maybe caused by the so called "Creators's update" of Windows 10 which I installed around that time.) Now I get " < waiting for device > ", and then nothing happens. Renewed installation of fastboot and adb (with adb-setup-1.4.3.exe) didn't change that behaviour.
[Samsung Galaxy Nexus] hgmichna:
Wrong Windows driver

This is most likely caused by Windows installing the wrong driver, which it loves to do. Don't ask me how many hours or days I have lost to that Windows defect, until I finally found the solution.

You can change the driver manually. Google for instructions. The correct driver is probably already on your computer, so you just have to change it in the device manager.
[Samsung Galaxy Nexus] nailyk:
FWUL advertisement

FWUL by [MENTION=5545101]steadfasterX[/MENTION] , if you have any driver problems. Perfect for the maguro.
[Samsung Galaxy Nexus] osm0sis:
You should get a refund and do the same thing for free using my FlashAfterUpdate addon.d script...
[Samsung Galaxy Nexus] GerardJ:
Sorry, but can you give a little bit more guidance? Arguments to google for? Which driver to change?
[Samsung Galaxy Nexus] guest4711:
It's usually the driver for android debug bridge. Search for "universal adb".

Cheers. K.
[Samsung Galaxy Nexus] GerardJ:
Just now, installed the 13.0-20170506-NIGHTLY-maguro, using the 'normal' LineageOS updater.

(Earlier on, I had re-installed adb, fastboot and drivers.)

Result after installation again: root lost - TWRP no longer available - Tried 'adb reboot bootloader' --> Okay (phone restarted in boot menu) - Command 'fastboot boot twrp.img' --> again '< waiting for device >' (nothing further happens).

In other words, in the normal uodate process, nothing works 'normally'.

I have re-rooted the phone again, using Odin 12.3. Then flashed again TWRP recovery, using the 'Official TWRP app'.

Next time, I will again update with the LineageOS Downloader, allowing me to flash SuperSU also, prior to reboot, thus keeping my phone rooted. For me, this is the easiest way by far...

I don't know what to do with 'addonsu-arm-signed.zip'. Flashing that file results in an error report, indicating that the process has been stopped.

But, anyway, thanks a lot for all your efforts to help me!
[Samsung Galaxy Nexus] nailyk:
Go back into recovery, flash the zip, then grab the recovery log:

adb pull /tmp/recovery.log .

or with the 'copy to sdcard' function.
[Samsung Galaxy Nexus] hgmichna:
Updating LineageOS with root

What did you have on the phone before the update? The Lineage OS updater works only when Lineage OS is already installed. When you update from something else, you have to do a clean update, i.e. wiping everything, using the recovery manually.
[Samsung Galaxy Nexus] GerardJ:
I had the earlier LineageOS NIGHTLY (20170429) installed. The update requires a compatible recovery (I had TWRP-3.1.0-0 installed).

The update script does not give me the opportunity to flash an additional zip, i.e. immediately after flashing the update, the phone re-boots. And is then no longer rooted...
[Samsung Galaxy Nexus] hgmichna:
Updating LineageOS with root

To root the phone you need to use TWRP manually. You can wipe system and cache, then flash lineage, gapps, and the Lineage root file all at once.

If this fails, you have to do a clean flash, i.e. wipe everything including data, except the internal and external (USB) storage, then do the same again.

After that you can use the built-in updater as often as you like. You will not lose root or gapps.

I don't know why or how you got into the situation you have now. One guess is that the built-in updater cannot handle SuperSU.
[Samsung Galaxy Nexus] MrFlashGame:
Hey guys,

i have tried to test out the lineage addonsu but it seems like it's incompatible to the latest nightly. If i try to install it i'm getting an error. Could somebody confirm this?
[Samsung Galaxy Nexus] GerardJ:
Thank you very much. This is all very clear to me. Will do it this way next time.

I thought of manually flashing as well, note down where the downloaded file should be (I noted something like

"/data/data/org.lineageos.updater/appupdates"), but could not find the downloaded file. Therefore, I decided to update right-away.

What you mentioned earlier on: that somehow Windows corrupted the (adb-fastboot-)drivers. I did some investigation and found "Minimal_adb_fastboot_v1.4.2.exe". Did run that file, but it subsequently reported that the drivers were already installed correctly. So. no solution there.
[Samsung Galaxy Nexus] MrFlashGame:
Another bug: The screen never turns off after the boot. The screen becomes darker but after 4 hours it was still on (Newest nightly, i have my own screen off time set in the setting; I can give logs if necessary). Would be nice if this bug would be fixed soon :)
[Samsung Galaxy Nexus] guest4711:
See

https://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574/post72108443 :

Universal adb https://github.com/koush/UniversalAdbDriver

should do the job ..
[Samsung Galaxy Nexus] bamtan2:
I think this means something went wrong and you need to start from the beginning. Format the /system partition (advanced wipe in TWRP) and factory reset in TWRP. Flash ROM and gapps, then reboot. Good luck!
[Samsung Galaxy Nexus] barbatrukko:
I m using "ClockworkMod Recovery 6.0.3.4", is ok? or i nedd to replace?
[Samsung Galaxy Nexus] bamtan2:
Everyone should be using the newest TWRP. :) I can't link directly, but you can type "galaxy nexus" here: https://twrp.me/Devices/ and choose the newest build (3.1 I think?) and find a way to install that.