yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kerpert:
The only way to install nano gapps is to install firstly the pico, delete with SDmaid those system apps that you can find in the PlayStore (e.g. clock, contacts, calcs, calendar) or those useless (e.g. animated background, screensaver, stock launcher after installed one alternative (Nova or so)), avoid to remove the stock keyboard.

Then flash nano gapps.

---------- Post added at 12:46 AM ---------- Previous post was at 12:42 AM ----------

Some MVNO provider requires roaming for let the Internet working.
[Samsung Galaxy Nexus] siealex:
What's new in the latest build compared to the February 22 build? Where can I find changelogs?
[Samsung Galaxy Nexus] guest4711:
See the answer [MENTION=5153662]Android-Andi[/MENTION] gave us a few days ago: https://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574/post75668311
[Samsung Galaxy Nexus] siealex:
I've found a very strange record on gerrit:

8.0 for tuna???
[Samsung Galaxy Nexus] bitbidu:
I am on 6.0.1 & thinking of moving to 7.1.2.

Is battery drain still an issue in the latest 7.1.2 build?
[Samsung Galaxy Nexus] HypnoticSilence:
I still haven't had time to mess with it since my last post, but I'll keep anyone updated here in case people are interested in the battery issue.

I am not sure if it's bug or if it the specific way I am using my device. I plan on doing full wipes each time to ensure it's not something caused from upgrading.

Hopefully I'll nail it down to one thing or another and maybe pull logs if I can manage so that the issue can be fixed if applicable.

For what it's worth, Android 7.x.x in general appears to have had battery issues for many people on all sorts of devices based on what I've read.
[Samsung Galaxy Nexus] Android-Andi:
Really? Don't say it's true?

(We pushed our 7.1 source for all devices to 8.0 in case someone starts working on it)
[Samsung Galaxy Nexus] kerpert:
I just noticed a bit more battery consumption from 6 to 7 but not a battery drain.

Depends much more from which apps are installed, which are set for notifies, which works in background.

Dunnot if someone did a comparable battery life demonstration between different os version.

Rather there are some annoying bug (camera error, wifi disconnection, freezed incall volume, background wallpaper that by randomly return to stock).

---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------

Better going directly for P.

:)
[Samsung Galaxy Nexus] Android-Andi:
First of all: P is a first Dev preview and far away from the final source which will be available.

On P there won't be less work to get things running, we see on O that there's a bunch to do to get things running.

You know O first Dev preview was released >1 year ago? How many OEMs have updated old devices to O yet?

https://www.digitaltrends.com/mobile/android-distribution-news/

As you can see, most OEMs didn't even cared about N.

Another thing:

OEMs don't care about security while they easylie could.

https://youtu.be/xv5Eb1SL96E

People here get frequently security updates, not sure why there's still questions about newer Android versions - source is open for everyone and we have created needed device branches for O on Gerrit in case someone likes to contribute.
[Samsung Galaxy Nexus] kerpert:
Right, I was sarcastic, I'm fine with even most and most stable 7.0.1 up to last security patches.

With the powerful reached by also the low level smarthphones <200€, OEMs should vouch for 10 years of security update (Android Treble should semplify this) and 5 years of major software updates.

As OEMs should guarantee spare parts for 10 years, and be pushed to take care about rubbish and recycling.
[Samsung Galaxy Nexus] kerpert:
Right now:

03-13 06:41:00.858 E/CameraHal(532): (acf00920) hardware/ti/omap4/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:4306 OMXCameraGetHandle - OMX_GetHandle() failed, error: 0x80001001
[Samsung Galaxy Nexus] siealex:
Does this ROM use ZRAM? If it does, how to disable it completely?
[Samsung Galaxy Nexus] Android-Andi:
Kernel supports it but it's not used by default. Needed fstab and init changes aren't added.
[Samsung Galaxy Nexus] musical_chairs:
Same here. Rebooting doesn't help, unlike the occasional CMA related camera failures I had been seeing on older builds. Camera works on a clean flash, also using something like Titanium Backup to wipe data for Android System makes it work after a reboot. (This erases a bunch of other apps permissions stuff). The problem seems to have showed up when the libion change was made.
[Samsung Galaxy Nexus] kerpert:
Confirm, with older builds the camera had occasional crashes, after updated to 9th March build it became almost totally unusable.

I haven't tried the complete wipe...
[Samsung Galaxy Nexus] musical_chairs:
I haven't tested a full wipe long term, just enough to know that it works initially. I figured I could get it working by wiping data in a few specific places. After a bunch of trial and error, I found I could get it working by wiping data on Android System, then rebooting. Unfortunately, this only fixes it for a day or two, then the problem comes back.
[Samsung Galaxy Nexus] Android-Andi:
You've got a full dmesg and logcat?
[Samsung Galaxy Nexus] kerpert:
[MENTION=5153662]Android-Andi[/MENTION]

enclosed
[Samsung Galaxy Nexus] Android-Andi:
Could you get a dmesg too please?
[Samsung Galaxy Nexus] kerpert:
A screenshot is fine?

It's always the same.
[Samsung Galaxy Nexus] Android-Andi:
No. Dmesg = kernel log. Need to check why the issue appears.
[Samsung Galaxy Nexus] kerpert:
How generate it?

I used the app catlog for logcat.
[Samsung Galaxy Nexus] Android-Andi:
adb shell dmesg > dmesg.txt
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=4465682]kb8no[/MENTION] and anybody else who still has a toro in service: Here's a fresh build with the open commits for toro.

https://www.androidfilehost.com/?fid=962187416754470980

The situation with the RIL is the same as with my previous builds, 4G mostly works but loses connection sometimes.

For maguro users, there is no reason to use my build instead of the official builds. The only differences are two commits and one revert. It's possible toroplus could behave a bit better with data on my build (if there are actually any toroplus's still in service...)

On another note, my camera has been working as expected ever since my previous post. Camera still locks up from time to time but it's nothing a reboot won't fix.
[Samsung Galaxy Nexus] kerpert:
I noticed the old ROMs become gradually deleted :eek:

https://builds.unlegacy-android.org/aosp-7.1/tuna/

The last one by me isn't so daily use:

1) camera never works, if not for little time after boot up, with February release it failed just sometimes

2) isn't possible to set a different wallpaper from that stock because systematically the launcher (tried Nova and the stock one) freeze for about one minute then switch to lockscreen when it's set a custom wallpaper

3) videos sometimes can't be played if not by using MX Player, Whats'app for example (but also Telegram, etc) isn't able to play a video just downloaded but have to close and reopen the app, and this not works all the time, MX Player instead works always.

4) google keyboard sometimes take so long to open while with February release it was always fast

I've tried to clean cache from twrp but nothing change.

In this moment I'm going on to use the 9th March release just because don't have the time to wipe and reinstall all for roll back to 1st Feb or 8th Feb or 15th Feb build (even don't remember which was. the best).
[Samsung Galaxy Nexus] bamtan2:
Unfortunately the guys are working on other things, so the tuna builds are a work in progress, with scaffolding and wet paint ;) That's why I must use zeelog's build for daily driver.
[Samsung Galaxy Nexus] kerpert:
Those with camera crashes can try to

- Disable wifi and bluetooth

- Reboot

- When in home please wait 2 minutes that the system become idle

- Try the camera

- Do other things but never switch on wifi or bt

- Try camera again

- Let use the phone normally for some hours

- Try camera again

Mine is working from this morning when I leaved off both wifi and bt.
[Samsung Galaxy Nexus] AceNJ:
has anyone used this ROM or zeelog's rom successfully with Android Auto? LineageOS doesn't seem to work correctly with Android Auto.
[Samsung Galaxy Nexus] Sesme:
thx for u hard work for this mytical phone!!!
[Samsung Galaxy Nexus] KShion619:
Auto might require a "certified device" aka safetynet pass, try installing magisk and getting safetynet to pass, I don't think the GNex should have a issue unless auto just uses mhl, which got disabled years ago
[Samsung Galaxy Nexus] Android-Andi:
Without root (magisk, SuperSU etc.) UA passes safetynet out of the box (build compiled as "user" build instead "usersebug" to also exclude adb root capability)
[Samsung Galaxy Nexus] KShion619:
Really? Didn't know that, I tended to just install that instinctfully. I was kinda just thinking of a reason Auto wouldn't work, because I know no one with it to test it with
[Samsung Galaxy Nexus] AceNJ:
thank you both, i can't get android auto to work but i'm not sure what else to try. i know it's unlikely many would still use such an old device for android auto but i'm going to keep trying. if not maybe ill "upgrade" to a nexus 5 or 6 and try that instead. i love the open nature of the nexus line but would only use the device for android auto rather than a daily driver.
[Samsung Galaxy Nexus] HypnoticSilence:
I'm not sure if you've tried the other versions, but I would try using 6.0 if you tried using 7.1

At least in my case, I've found certain things work better for me in one version over the other, so it may be that Android Auto also works better with 6.0 over 7.1

I personally have been using 6.0 since I can't seem to figure out the issue for battery life with 7.1, and I haven't had time to diagnose it really, but it may be worth looking at in your case.
[Samsung Galaxy Nexus] silentz0r_:
Hey everyone, I'm constantly low on ram even though I barely have any applications. I've tried several times to launch Google Maps and try to get directions to a place with no luck, every app just keeps on freezing. Is there a way to free up any additional ram? Do others experience the same issue?

Here's a list of top RAM-hungry applications:

Android OS - 375MB

Android System - 309MB

Google Play Services - 126MB

System UI - 68MB

Nova Launcher - 44MB

Gboard - 38MB

Messenger Lite - 14MB

Messages - 12MB

and the rest is below 10MB. I pretty much just can't use the phone as it constantly redraws and lags like crazy. I tried to send an email to myself earlier and it took me 20 minutes.
[Samsung Galaxy Nexus] KShion619:
Try using the 4.4 branch builds on the website or 6.0, 7.1 is pretty heavy on the limited resources of this phone, especially with gapps installed.

Also if you've used a Intel/Integrated Graphics, you know about shared memory, the OMAP devices with CMA (this one) dynamically use RAM as needed, audio and video uses these resources and RAM greatly reduces on the fly
[Samsung Galaxy Nexus] wwallace1979:
Hi, today i flashed the

ua_tuna-4.4.4-20180510-1828.zip

and

open_gapps-arm-4.4-pico-20180519.zip

via TWRP 2.8.7.0 on my Maguro (with a factory reset at first).

After reboot you say in Post 2 ->

After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.

But this information are for android 7.1.2 and not for KK because you doesn´t have this option; or are they hidden on an other place?

So that I start to add my accounts and to install aps via the Play store. But during this i get mistakes that a lot of apps which are installed are stopped. You get an information about it on the screen and you have to confirm it.

After a reboot i get the same mistakes .

What did i do wrong?

Now I´m on Version 7.1.2 whitout an mistake, but this Version is very slow.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=3689677]silentz0r_[/MENTION] Try restarting more often to see if that helps the stability. This software is not super well tested and could have memory leaks etc. Andi uploaded a kernel which disables CMA in case that causes problems. I use Zeelog's lineage 14 which also has CMA disabled. Good luck :)

[MENTION=4361601]wwallace1979[/MENTION] Always flash with the newest TWRP because old ones can cause problems! Sometimes people say they need to manually wipe /system too, but I haven't seen that problem reproduced, so it might be human error rather than a bug. You're right that you don't need to change permissions with 4.4! Just flash Gapps immediately after flashing the ROM with every version of android, just in case. You may need to wipe everything and start fresh, but you will get it working eventually! :)
[Samsung Galaxy Nexus] kerpert:
Who still daily use the 7.1?

Do you use some custom kernel configuration?
[Samsung Galaxy Nexus] musical_chairs:
I use it, and no, no custom kernel configuration. I often flash the no-CMA kernel - not because performance is better , it's not - but because I use my phone as a flashlight quite a bit these days, and that way the flashlight always works. It it sluggish sometimes, and web browsers tend to crash frequently. But otherwise it works well for my needs.
[Samsung Galaxy Nexus] kerpert:
By using a much aggressive Low Memory Killer setting I have almost no more camera errors.

Actully the most annoying thing is the background wallpaper that all the time automatically revert to the default one and can't stand on the "total black" I would...

[IMG="stock"]http://www.androidworld.it/wp-content/uploads/2016/03/Android-N-wallpaper-529x470.png[/IMG]
[Samsung Galaxy Nexus] Android-Andi:
You like to share your settings?

Tried a different launcher about the wallpaper issue?
[Samsung Galaxy Nexus] kerpert:
Both CPU 1200 MHz and governor Performance

I/O scheduler Deadline

Low Memoery Killer: 27 - 37 - 62 - 105 - 132 - 254 MB

Z-RAM 0

Other things to default.
[Samsung Galaxy Nexus] bamtan2:
In my experience the wallpaper reset happens sometimes when the system crashes, and it is independent of the launcher!
[Samsung Galaxy Nexus] kerpert:
Even the enclosed seems fine.

The empty app killer could be more, around 200/220.

I think these value must be adapted on how many apps and services are installed/enabled.
[Samsung Galaxy Nexus] kerpert:
With May 6.0.1 instead I noticed:

- I couldn't authorize the phone to adb host, inside the developer option is missing "revoke usb autorization", I fixed this by recreate adb_keys file

Anyone is still developing the MM or N ?
[Samsung Galaxy Nexus] Galaxyninja66:
Honestly I might be pursuaded to start LOS 14.1 builds. Interest in MM and N just doesn't exist for most existing Gnexus users, if anything I should roll out LOS 11 builds. I am still rocking CM9.1 (god damn I love ICS). If enough people were interested I would be happy to make some LOS 14.1 builds over the next couple of months.
[Samsung Galaxy Nexus] Android-Andi:
It's an issue with 6.0 on user builds... Didn't found the source of issue as it works on 4.4. and 7.1...
[Samsung Galaxy Nexus] sincrociclotrone:
Hello all.

This is my very first message and I would firstly like to thank all the contributors.

I have owned a Galaxy Nexus since summer 2013 and I still use it as my unique device on the go. At home I often get advantage of an iPad mini2, which performs better but runs iOS, which I hate.

I have been using custom ROMs since December 2014, and I would like to contribute with some feedback as a daily user, even though my knowledge only reaches the point to allow me wiping and flashing ROM packages.

However, I do not want to bother you guys with useless long messages, if this cannot be useful, so please let me know if you are interested.

Thanks

best

Fabbro
[Samsung Galaxy Nexus] bamtan2:
A lot of the developers have taken a break because they have done years of work here and now there are other things that they want to work on too.

But you will cause no trouble by writing long messages. They will be HAPPY with your feedback! :) Even if they can't fix these things. So please share your thoughts. <3
[Samsung Galaxy Nexus] Кирюха-:
Just amazing 7.1.2 ROM! Thank you, devs! Will the 8.x ROM get to this device?
[Samsung Galaxy Nexus] kerpert:
No
[Samsung Galaxy Nexus] WoolTomb:
Hi guys,

i want to know if the development of galaxy nexus is stopped.

Thank you
[Samsung Galaxy Nexus] guest4711:
Perhaps the guys @ replicant are still working on floss drivers for it ... (see https://www.xda-developers.com/the-...ants-to-create-a-truly-open-source-mobile-os/ )
[Samsung Galaxy Nexus] musical_chairs:
No.

I guess it depends how you define 'stopped' and 'development'. There is still a lot of work going on behind the scenes by the Unlegacy team for omap4 devices. Our devs are AWESOME, trust me. They're still committed to their supported devices. The GNex is still on the list, though it is not at the top of the priority list anymore.
[Samsung Galaxy Nexus] micha04081986:
Hey guys! Does this Rom supports microg?
[Samsung Galaxy Nexus] guest4711:
Yes, but you may need to patch the framework for signature spoofing when required. See e.g. NanoDroid:

[MODULE/SYSTEM] NanoDroid 17.6.20180805 (microG, pseudo-debloat, F-Droid + apps) - https://xdaforums.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928/post71739848
[Samsung Galaxy Nexus] kerpert:
Does also the 4.4.4 record videocalling in black and white?
[Samsung Galaxy Nexus] defailers:
Are there any chances to see a release of Android Pie (Go edition)? It will be perfect for our phones.
[Samsung Galaxy Nexus] coco1476:
Hi, i found my old nexus in a drawer running this ROM. Unfortunately is has some major lag issues, everytime I click on something I takes about 5 seconds to react. Did a factory reset and after a few hours the lag is back. Can someone help me please?
[Samsung Galaxy Nexus] siealex:
Install stock 4.3 and enjoy. Our hardware, especially the EMMC chip, is too slow for modern Android versions.
[Samsung Galaxy Nexus] bamtan2:
As with any device on XDA, some ROMs have more problems than others. :) You could update your twrp and wipe and install a different ROM with the smallest opengapps. Whether an older ROM or a newer one. I use the latest lineage from here: http://zeelogkang.blogspot.com/2017/05/lineageos-141-unofficial-712-gnex-tuna.html

Note that having just a few apps installed makes a big difference too.
[Samsung Galaxy Nexus] kerpert:
The trick is not to overdo the number of installed apps (user apps max 40/50) and avoid social network that sucks a lot of resources, keep the internal memory as much as empy and don't fill over 8 GB.

Disable every unuseful services, example those provided by Maps (traffic, daily work/home route, etc), this must be valid for all apps, disable background updates.

I'm using almost all the usefull apps without freeze or heavy slowdown: Whatsapp (I do successfully videocalling even if the others see me in black and white), Spotify, Amazon, Ebay, Chrome, Drive, Dropbox, Maps, Tomtom (only my country map), MX Player (all video works), Google News, Paypal, Google Photos, SD Maid, Teamviewer, Google Translate, Twitter, Weather app, Youtube, Bank, Calendar, Gmail, Google Camera (with panorama, and sphere), Chrome Remote, Magisk, Nova, Greenify, Xposed, Kernel Adiutor (these last three help a lot), Trimmer, fitness app, and minor others.

Under kernel adiutor set min/max CPU to 1200 MHz and performance governor, I/O scheduler to deadline and read-ahead to 128 kb, kenel samepage managing page to scan 20 and sleep between scans 250 ms, low memory killer 39/77/101/132/229/291 MB, ZRAM 240 MB, TCP congestion westwood, other things as stock.

I deleted unuseful system apps as screensaver, browser, clock (download from PlayStore), system webview (download from PlayStore), keyboard (use Gboard), stock launcher, and others.

Also stop the system animation under developer options and force GPU rendering.

Set no animation also under Nova.

The critical aspect is the battery lifetime expecially whtn GPS is on, so I arrive to use 3 battery in a day (are removable and I have external charger).
[Samsung Galaxy Nexus] danjng:
Having some issues flashing here... Perhaps I'm doing something way off, but formatting system/userdata then reflashing from zip one of the files from the ua site.

I flash the rom, then open gapps, then finally supersu. After rebooting, I am constantly getting the following:

1-01 00:00:08.524 157 157 E SurfaceFlinger: Error while compiling shader:

01-01 00:00:08.524 157 157 E SurfaceFlinger: precision mediump float;

01-01 00:00:08.524 157 157 E SurfaceFlinger: uniform vec4 color;

01-01 00:00:08.524 157 157 E SurfaceFlinger: void main(void) {

01-01 00:00:08.524 157 157 E SurfaceFlinger: gl_FragColor = color;

01-01 00:00:08.524 157 157 E SurfaceFlinger: }

01-01 00:00:08.524 157 157 E SurfaceFlinger:

01-01 00:00:08.524 157 157 E SurfaceFlinger:

01-01 00:00:08.524 157 157 E SurfaceFlinger: Error while linking shaders:

01-01 00:00:08.524 157 157 E SurfaceFlinger: Error while compiling shader:

01-01 00:00:08.524 157 157 E SurfaceFlinger: attribute vec4 position;

01-01 00:00:08.524 157 157 E SurfaceFlinger: uniform mat4 projection;

01-01 00:00:08.524 157 157 E SurfaceFlinger: uniform mat4 texture;

01-01 00:00:08.524 157 157 E SurfaceFlinger: void main(void) {

01-01 00:00:08.524 157 157 E SurfaceFlinger: gl_Position = projection * position;

01-01 00:00:08.524 157 157 E SurfaceFlinger: }

01-01 00:00:08.524 157 157 E SurfaceFlinger:

01-01 00:00:08.524 157 157 E SurfaceFlinger:

01-01 00:00:24.044 165 165 I ServiceManager: Waiting for service sensorservice...

the last message just repeating ad naseum... Any help would be greatly appreciated! thanks!!!!

Edit:

Just for some background, I grabbed all that by running adb logcat during boot. At some point it just kills that process as well, disconnecting from debug mode. It just hangs at the Android loading animation and doesn’t do anything else even after 5 hours.

Thanks!
[Samsung Galaxy Nexus] bamtan2:
Triple check that you're using the very latest TWRP, 3.2 something! People have had data problems caused by bad flashes from old twrps!
[Samsung Galaxy Nexus] danjng:
Thanks for the pointer!

Funny enough, I thought that the old posts about SuperSU may have been fixed, but apparently not (or at least not for me). That was definitely the culprit.

Formatted user and system, flashed ua's latest, and then a pico version of Google Apps.

Everything boots perfectly now! Nice and snappy! While it's not my daily, I've got a working spare that's bearable to use! Thanks to the devs!!!
[Samsung Galaxy Nexus] bamtan2:
Yep, I imagine the very latest supersu would work, but everyone uses magisk now because it's very functional, open source, and maintained within the community!
[Samsung Galaxy Nexus] sergialess:
Hello, good morning. Sorry to bother you with my question but I've found a problem trying to put in place this rom, especifically the 4.4.4 version.

I'm trying to give the gnex a second life for my daughter in order to use it a little bit (light use).

Yesterday I've been flashing 4.4.4 + latest open gapps (ARM - pico/nano). Why 4.4.4? because it is lighter and feels snappier, although latest google services are tough for this device nowadays. So long story short: after first boot, I cannot pass the google services check (it fails). After several tries, I got pass the screen but I was not able to register the google account, so no Play Store, and no apps available. Definitely, 4.4.4 is no longer working with the very latest google stuff (at least for me). My device is Maguro.

I finally decided to flash another rom (7.1.2), but I'm not happy with the result because it feels a lot of heavier, and does not run nicely.

Any idea of what should I do?. Thanks!.
[Samsung Galaxy Nexus] Android-Andi:
Updated 4.4 with September ASB patches will be available sometimes later today or tomorrow.

I'd suggest using deltadroid gapps for 4.4.4

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Direct link:

https://www.androidfilehost.com/?fid=889764386195926956