yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MongolPup:
This is bonkers. Bought a Nexus 6P but pulled my GNex back out to try this...and it works. Like, really well. Even the little game in the settings menu. I was using my GNex very sparingly to surf the web while my 6P was on charger but now I feel like I have a true back up phone.

Amazing work guys.
[Samsung Galaxy Nexus] werty100:
I am going to make a litle review of this rom.... with no voice just for perfomance and to show how it good really works

[YOUTUBE]t-TEtJsIPx8[/YOUTUBE]
[Samsung Galaxy Nexus] zingzangripper:
same thing here, any fix?
[Samsung Galaxy Nexus] osm0sis:
Doubtful. I seem to recall the device they were basing the ZRAM stuff off of was a 1gb RAM device that actually has 1gb available but the OEM still added and enabled ZRAM once they upgraded it to Lollipop. We now have 996 very shared megabytes of memory, so ZRAM could still be a huge help to take the pressure off of it.
[Samsung Galaxy Nexus] PythonNut:
Are there any current plans to make a ROM based on this that goes beyond stock? I won't say exactly what features I want, to avoid looking like a whiny good-for-nothing, but I know you guys have been doing a lot of great stuff with the kernels and userspace on other ROMs, but they aren't derived from this one, so they don't get the CMA magic, among other things.

I'm toying with the idea of building a kernel for myself, but I'd honestly be out of my depth.
[Samsung Galaxy Nexus] :
I think the problem is that this CPU is too slow to handle ZRAM efficiently. Just running the OS (especially 5.x/6.0) makes it stutter, and if you add ZRAM compression to that, it stutters even more. I am saying this from my own experience. Without ZRAM everything runs just smoother, even though multitasking obviously suffers. Still, the tradeoff seems to be just too high.
[Samsung Galaxy Nexus] AgentSmith:
I'm hoping/waiting for the day Ziyan makes a Zmod version with CMA and all the other optimizations. I have yet to discover the advantage of running Marshmallow and since doze doesn't seem to have an effect (battery time is better with Lollipop) I'd prefer to revert to Lollipop also because it contains no real bugs and no special beta versions of apps like Clocksync are necessary. CM is too much customization for me but Zmod with a few handy mods is just perfect.
[Samsung Galaxy Nexus] E66666666:
Anybody had troubles with alarms not going off, or am I just an extremely solid sleeper?
[Samsung Galaxy Nexus] khromium:
NFC doesn't work on my Gnex(maguro)...
[Samsung Galaxy Nexus] thagringo:
im happy with MM on my gnex but i would really appreciate some more kernel options like color control, cpu OC and gpu OC ( and maybe even zram for those who wish to have it ?).

for more UI options im just using gravitybox.

cheers
[Samsung Galaxy Nexus] bamtan2:
Intel recommends MORE ZRAM than we use, NOT less. With ZRAM, multitasking is slow. Without ZRAM, there is almost no multitasking! The trade is clear: We accept slower multitasking so we can support modern applications which require great quantities of RAM.

I do not necessarily advocate for using as much ZRAM as Intel recommends, because their test devices do have faster CPUs. I think you should use as much ZRAM as is required to keep YOUR apps from being forced closed because of lack of RAM. Right now, I think 250MB ZRAM is a very safe number.

Of course people are making ROMs! For ETAs I think you must ask in their threads, not this one ;) But you will need to wait some time. This code has only very recently become mature enough to drop. The RAM optimization has barely 1 week of testing! And I suspect Ziyan and MWIsbest have not yet received one donation for it.

We must all appreciate that it takes years to create a high quality software package, not days or weeks.
[Samsung Galaxy Nexus] siealex:
26%, as in old Paranoid CM-based ROMs?
[Samsung Galaxy Nexus] osm0sis:
Agreed. What Ziyan has set up for ZRAM in CM 13 runs beautifully, so I can't wait to run a ROM that has both that and CMA. :)
[Samsung Galaxy Nexus] PythonNut:
Of course, and I'm deeply thankful to the GNex/Omap4 team for their herculean efforts. As for donations, I'm still a student; every dollar I donate would be a dollar added to my college debt, unfortunately, :/ but I really am indebted to you guys for your work. The GNex devs haven't just exceeded expectation, they've exceeded imagination.
[Samsung Galaxy Nexus] siealex:
Stock Nexus 5X ROM has 500 M ZRAM...
[Samsung Galaxy Nexus] aosp:
Turn on zram for bullhead

ZRAM is a clear win for app switching (15% shorter ave start time

when cycling through various sets of apps). Currently using the

same size as N9 (~500M) -- may want to shrink later.

https://android.googlesource.com/device/lge/bullhead/+/3d57239

bullhead ZRAM: use LZ4 and max_comp_streams=4

https://android.googlesource.com/device/lge/bullhead/+/7e9ea50cfd7a26cc83b6f56138208c722a86a44e
[Samsung Galaxy Nexus] zzpianoman:
Just to add my two cents to the whole RAM issue, the vast majority of apps have alternatives that use a much lower RAM footprint. Whether it's Tinfoil for Facebook, multi-protocol messenger clients for FB messenger, skype, etc, or stock browser vs Chrome, there is almost always an alternative. And while I am usually reluctant to say that the solution to a problem is to "not use a particular app" there's absolutely no reason for certain apps to consume as much RAM as they do - especially something like FB messenger, which at times consumes 150MB of RAM while running in the background. There's simply no excuse for that whatsoever. If the app developers are so careless in how they design an app, who knows what ELSE is wrong it?

Simply throwing more and more RAM at a device seems to be how Google/Android/device manufacturers opt to fix what are obvious underlying problems in the OS itself. If more people went for the alternatives, it would encourage the maintainers of the "official" and more bloated apps, to better streamline their apps so they don't eat away at system resources.
[Samsung Galaxy Nexus] almostdeadly:
Network Error

Installed this last night and noticed an issue. I haven't seen anyone else mention this but my phone won't connect to verizon's network. It recognizes the network and shows the strength but it says disconnected. I even changed to find only cdma instead of LTE thinking there may be an issue there with no change. Looking for any help or suggestions please before I just break down and buy a new phone.
[Samsung Galaxy Nexus] bamtan2:
Only CM12 is "stable", so I suggest you run that on mission-critical devices instead!
[Samsung Galaxy Nexus] almostdeadly:
So I'm obviously new here. Not the first rom I've installed so I know the basic generic steps to do so but you suggest CM12 because it's stable. I go to the CM thread and it seems those builds aren't for toro. I may be oblivious about where to actually look though.

Additionally it's actually on CDMA - 1xRTT network type and says Cellular network state : Disconnected
[Samsung Galaxy Nexus] PGHammer:
Clean install or dirty install?

DU and Unlegacy both prefer clean installs; also, if installing using OpenGapps, don't use anything larger than pico (for others, go with the smallest you can get away with); that latter recommendation applies to ANY ROM (including Lineage; it's actually part of the docs for Lineage 13 and later).
[Samsung Galaxy Nexus] entux:
Hmm... this might have been the problem. I didn't wipe system when i installed Unlegacy 7.1.1 over my former Unlegacy 7.1. I thought it's merely and update. Could have been the culprit. I wiped system for my install of Lineage 14.1 though, since I always start fresh with different roms. OpenGapps pico is a no brainer for me because TWRP actually refuses to install anything bigger than that.
[Samsung Galaxy Nexus] phaleg:
Over 2 days and no new comment here, WT* :D

XD
[Samsung Galaxy Nexus] _yen_:
people is busy...

said this I would thanks [MENTION=4695183]zeelog[/MENTION] for his commits on unlegacy gerrit, which I'm now using for quite a week. No problem using UA 7.1.1 enforcing even if there are still some additional denials (mainly system_server trying to unlink unlabeled files and shell trying to write on dalvikcache_data_file) which seems not hurt overall ROM functionality.

Also GPS-shim works good.

Good job and thanks again.

yen
[Samsung Galaxy Nexus] ASHURiCAN:
MD5 stills corrupt for last release.

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Samsung Galaxy Nexus] fromfree:
Hi yen, I also saw the commits about GPS-shim but I couldn't tell what they were about. Is GPS now working?

For who haven't noticed there are new 6.0 and 7.1 builds available: 2017/03/20 :good:
[Samsung Galaxy Nexus] _yen_:
When using the GPS-shims commit (not officially merged yet) GPS works on maguro in UA 7.1.1.

bye

yen
[Samsung Galaxy Nexus] ASHURiCAN:
7.1 20/03 build is corrupt. It'll fail at flash (never ending) and MD5 doesn't match.

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Samsung Galaxy Nexus] bryantjopplin:
I didn't see this linked anywhere so here it is. https://builds.unlegacy-android.org/aosp-7.1/tuna/

Sent from my Nexus 6 with Pixel XL build.prop
[Samsung Galaxy Nexus] ASHURiCAN:
It has been linked many times but not bad to link it again :)
[Samsung Galaxy Nexus] fromfree:
Hi, try to download from PC, use a download manager with CRC control function if you want (JDownloader for example). I noticed that downloading from phone frequently gives corrupted UA builds
[Samsung Galaxy Nexus] ASHURiCAN:
Same result, the problem is not from a bad download. The original auto generated zip file is already corrupt. I think that's the problem, it has been talked about it before, here. But it's sad it has not been resolved. We just need to wait a next release and hope that the file will not be corrupt. :(

Here is a nice quote:

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Samsung Galaxy Nexus] _yen_:
Yesterday there has been some changes in the way we access builds.unlegacy-android.org server and today 7.1.1 build is not corrupted.

Thanks to dev...

bye

yen
[Samsung Galaxy Nexus] miomaguro:
Does anyone know which security patch is included in ua_tuna-6.0.1-20170320.zip?
[Samsung Galaxy Nexus] _yen_:
Seeing commits on android manifest, it should be March (android 6.0.1 release 79)

bye

yen
[Samsung Galaxy Nexus] miomaguro:
Uh: I still don't get how you were able to check it, but thanks for sharing!
[Samsung Galaxy Nexus] _yen_:
https://github.com/Unlegacy-Android/android/commits/aosp-6.0

I simply look sources on github, eight days ago they merged android 6.0.1_r79 which is part of the march security releases so build from 20/03 should has it...

bye

yen
[Samsung Galaxy Nexus] miomaguro:
Thanks for the clear explanation: it makes a lot of sense!
[Samsung Galaxy Nexus] uji_sine:
February patch.
[Samsung Galaxy Nexus] miomaguro:
So: now I have to install it to get the REALLY TRUE answer :D:D:D
[Samsung Galaxy Nexus] aro8366:
GSM and GPS

I'm deciding beetwen https://xdaforums.com/galaxy-nexus/development/rom-t3297218 and this lovely nougat but i need a stable gsm and gps, but I heard this rom is having problems with it.
[Samsung Galaxy Nexus] bamtan2:
All the roms are based on the same code base as unlegacy, so I'd suggest just trying the next unofficial unlegacy 6.0 whenever it is built. The current newest one is corrupt, apparently because they've been having build server problems. Check https://builds.unlegacy-android.org/aosp-6.0/tuna/ next week and maybe there will be a new one. The current corrupt one is ua_tuna-6.0.1-20170320.
[Samsung Galaxy Nexus] _yen_:
I take a look at the commit, security patch is labelled February 1st, but r79 was released on March 6th... so Google is gonna slow patching marshmallow...

Thanks [MENTION=4670405]uji_sine[/MENTION] for pointing it to me.

bye

yen
[Samsung Galaxy Nexus] runekock:
ZeeLog has written a GPS fix for nougat which I don't think has been merged elsewhere yet. You might want to try his unofficial lineage 14.1:

http://zeelogkang.blogspot.com
[Samsung Galaxy Nexus] uji_sine:
​

Could you please confirm about battery comsumption.
[Samsung Galaxy Nexus] miomaguro:
I'll test it. BTW I confirm it is February security patch.
[Samsung Galaxy Nexus] knopper84:
so which one is t5he latest uncorrpted one? ua_tuna-6.0.1-20170313.zip or better ua_tuna-6.0.1-20170306.zip ?
[Samsung Galaxy Nexus] bamtan2:
I just checked the last 3 and they don't match their md5 hash. Apparently the server was broken for a while!
[Samsung Galaxy Nexus] caiu:
I Meet the same problem
[Samsung Galaxy Nexus] Ziyan:
The odd thing is that every time I download it, the md5 matches :rolleyes: but we'll keep investigating the issue.
[Samsung Galaxy Nexus] kamwaikin:
Yes

Every time i open the camera app and it prompt that:mad:
[Samsung Galaxy Nexus] _yen_:
Hello Ziyan,

in my experience all these troubles with corrupted rom stored on builds server begins few after you start using a CDN on it, which seems no more the case starting from the 22th. I may be wrong but at least all three 7.1.1 tuna builds uploaded on server after march 22th are uncorrupted.

I've also verified few times that zip corruption occurs only on builds server, not on your build bot.

bye

yen
[Samsung Galaxy Nexus] fromfree:
I'm using right now the MM 20170320, downloaded from PC using JDownloader with CRC check; md5 matched even in recovery and then the zip was flashed flawlessly!
[Samsung Galaxy Nexus] knopper84:
i dont tried the latest one...but damn.... all other ROM's before were anyhow corrupted. I tried different KK-ROM's and all MM ROMS's from https://builds.unlegacy-android.org/aosp-6.0/tuna

on every one it stucks on "Patching system image unconditionally"....recovery stay at this state forever.

The build from 16-07-25 finally worked! took me 2 hours…

SO what is wrong with the server? please hosts the right (uncorrupted) files sir!
[Samsung Galaxy Nexus] bamtan2:
I think I made a mistake verifying mine, so don't take my word for it! yen says the last few builds work, so I trust him. I don't know a good tool to automatically compare a checksum file to the file with its same name. you should be able to double click on ua_tuna-6.0.1-20170227.zip.md5sum and have it automatically compare to ua_tuna-6.0.1-20170227.zip. should be built into windows!
[Samsung Galaxy Nexus] grh35:
Hi, I would like to ask a question about 4.4 version of this rom. I'm using the latest kitkat rom and when I try to export some file from dropbox, screen freezes for a second and phone reboots. Is it rom based problem? any suggestion? I hope I get the log properly, I am noob about doing logcat :D
[Samsung Galaxy Nexus] cabalio83:
ua tuna-6 0 1-20170320 MD5

Downloaded latest build right now from https://builds.unlegacy-android.org/aosp-6.0/tuna/

MD5 is fine, make sure to download with a PC and use a download manager to avoid file corruption (in this case I used Jdownloader)

Thank you so much for keeping this little monster alive!!!
[Samsung Galaxy Nexus] aro8366:
7.1.1 doesn't boot

I have installed latest 7.1.1 rom 03/25 and pico gapps package and my phone does not boot at all. It's stuck on android logo. What could go wrong.
[Samsung Galaxy Nexus] runekock:
Maybe osm0sis' fix for seLinux has not yet been merged. If that is the case, flash it in twrp:

https://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574/post71215509
[Samsung Galaxy Nexus] osm0sis:
Yeh, [MENTION=4695183]zeelog[/MENTION] submitted a commit with most of them to the Gerrit but it's still awaiting +2 last time I looked.
[Samsung Galaxy Nexus] eddynaka:
Help flashing...

Hi guys,

just tried to flash the rom in my galaxy nexus. It keeps going forever in Android screen.

Just made a clean flash, before this i was using cm.

Can anyone help me?
[Samsung Galaxy Nexus] guest4711:
Did you update your recovery? You should use a current twrp.
[Samsung Galaxy Nexus] _yen_:
Please specify which branch of this ROM you are flashing (4.4, 6.0, 7.1.1) and possibly which build date has ROM you're trying l.

If it is 7.1.1 it's a know bug and you need to do what is explained in this post:

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

bye

yen
[Samsung Galaxy Nexus] _yen_:
a new 6.0.1 build it's out minutes ago:

https://builds.unlegacy-android.org/aosp-6.0/tuna/ua_tuna-6.0.1-20170327.zip

I'm currently out for work and I can't test md5, sorry.

Edit: confirming md5 match and zip is uncorrupted.

bye

yen
[Samsung Galaxy Nexus] gabrielex:
Is anyone using Stellarium with this ROM? I have problems with it since touch inside the app seems to not work properly (it works everywhere else).
[Samsung Galaxy Nexus] vortex-5:
Is there a way to dim the screen during the optimizing apps so you don't get a superbright square that probably causes more burn in since our phones are slow and optimizing apps can take 20-30 min?

flashable zip maybe?

There used to be one for lollipop but the same screen dim script doesn't work on 6.0.1. I'm not sure if 7.1.1 is stable enough yet since the GPS issue was only just resolved.
[Samsung Galaxy Nexus] kerpert:
I would like to have on screen the real time ram usage. Isn't this available on developer menu?
[Samsung Galaxy Nexus] miomaguro:
I would rather search through the xposed modules
[Samsung Galaxy Nexus] miomaguro:
For example, I've found this highly customizable module "Cool tool" that can enable several tweaks. See attachment.
[Samsung Galaxy Nexus] PGHammer:
Current TWRP (and other news)

Current TWRP for our GNex is 3.1.0.0 (official) - however, 2.8.7.0 and 3.0.2.0 should work (the only reason I updated was simply keeping current).

In other news, a unified version of Lineage 14.1 (UNOFFICIAL) from zeelog is now available for shakedown testing.

As is the usual, you should flash clean if coming from any other ROM (including stock) - also, as per standard, either mini_Dynamic or OpenGApps_pico (no larger) is recommended.

Lastly, despite this being Lineage, it DOES support alternative launchers (including Pixel Launcher - which can now be added via the Google Play Store for a cost of nit).

Details can be found here: http://zeelogkang.blogspot.com/2017/03/lineageos-141-tunanew-build-up.html
[Samsung Galaxy Nexus] vortex-5:
Just tried out 7.1.1 (2017-03-28) from 6.0.1 I noticed I'm getting a no sim card issue. Anyone else have this?

I did a clean flash of /system left /data intact.

Is there a work around to get the SIM card to detect?

Looks like the baseband is not up and running I can't access the *#*#TEST#*#* menu.

Anyways rolling back to 6.0.1 if anyone has a work around I'm willing to help test it in 7.1.1 otherwise I'm going to sit in 6.0.1 so I can have basic phone functionality for now.
[Samsung Galaxy Nexus] _yen_:
This is due to some SElinux denials, until proper commit is merged use the tunasefix workaround that is explained in this post:

https://xdaforums.com/showpost.php?p=71215509&postcount=1326

bye

yen
[Samsung Galaxy Nexus] vortex-5:
Are you tracking that commit on github? do you have the has I'll watch for it to appear on mainline.
[Samsung Galaxy Nexus] _yen_:
I just see that it has been merged now, as the GPS shim commit, next build will boot fine and with a working GPS for maguro users.

BTW I am primarily tracking commits on UA gerrit: https://gerrit.unlegacy-android.org/#/q/status:merged (the two commits merged today are those I'm speaking)

bye

yen
[Samsung Galaxy Nexus] vortex-5:
Oh that's great I'll try out next build then over the weekend.
[Samsung Galaxy Nexus] phaleg:
At the moment, MM rocks, seriously, a lot! :D
[Samsung Galaxy Nexus] Ziyan:
Yup, we wanted to do some minor cleanups on the commits, but in the end, we had some time issues, so we merged them as-is, as they work fine :)
[Samsung Galaxy Nexus] _yen_:
Thank you [MENTION=2633638]Ziyan[/MENTION] just a little question related to the GPS shim commit, do you know if GPS was working on toro/toro plus before this commit?

I would try to know if GPS need to be shimed also for toros as this change the way how this commit can be better integrated in the unified build (maguro only or maguro/toros).

Actually I've tested a little improvement for the maguro only option. It should be surely done better as i'm only a user but, just in case, I put here the patch file as I'm not accostumed to such modern things like gerrit... sorry.

Thanks for the hard work you and all other unlegacy devs put on keeping alive tunas

yen
[Samsung Galaxy Nexus] knopper84:
so anyone tried the latest MM, ua_tuna-6.0.1-20170327.zip ?

is it still corrupted?

As mentioned before the only MM-ROM that worked for me, is the one from this thread here dated 2016-07-25! All others from https://builds.unlegacy-android.org/aosp-6.0/tuna/ stuck at "patching system image unconditionally", even the KK-roms. ...

Tried several TWRP's 2.8.4.0, 2.8.7.0, 3.0.2.0 and latest....

so what could be wrong?
[Samsung Galaxy Nexus] phaleg:
Probably system is still mounted...

Try to un-mount it or wipe it during a clean flash...

It should work
[Samsung Galaxy Nexus] musical_chairs:
GPS has been working on toro on 7.1 for a long time, I just tested it again this morning to make sure. I haven't tested toroplus on 7.1 recently but if I recall correctly, GPS has been working fine there as well.

On a different note:

toro's RIL has always been troublesome. The recent SELinux fixes help a lot, but I still can't get mobile data working on toro on 7.1. I've been (mostly happily) using Unlegacy 4.4 for several months as it's the only place I can get MMS working anymore. Now, my setup is slightly more complicated than normal as my toro is on Page Plus. They recently changed their APNs from VZWINTERNET to TRACFONE.VZWENTP. On a stock ROM (and maybe on 4.4), the APN updates itself automatically, but on newer ROMs, it doesn't. Probably related to how activating a new sim card doesn't work on anything newer than 4.4. Anyway, I can manually change the APN on 6.0 and get mobile data, but MMS remains broken because the hack we used to get MMS working on 6.0 does not work with Page Plus's new APNs. We have been stacking hacks upon hacks to keep toro's RIL working, and unless somebody far more skilled than me digs in and figures out what is going on, I'm afraid we are stuck.
[Samsung Galaxy Nexus] _yen_:
Thank you for your answer, so GPS shim is a maguro only thing... the original commit has a reference to maguro gps driver in gps.c file (REAL_GPS_PATH) and i fear that it can break gps on toros, i've so slightly modified the commit in the way I've posted earlier to make it exclusive for maguro, can you or [MENTION=2633638]Ziyan[/MENTION] take a look at it please?

Thanks again.

yen
[Samsung Galaxy Nexus] musical_chairs:
I can test it. Ziyan doesn't have a toro. I will have to sync 7.1 again (I have 4.4 synced currently) so it will be a few days before I can get it all done.
[Samsung Galaxy Nexus] _yen_:
No, md5 is correct and it flashes without any problem

All builds past march 23th i've tested are uncorrupted, so zip corruption problems on server seems now solved.

bye

yen
[Samsung Galaxy Nexus] guest4711:
Perhaps your system partition is to small? Did you increase its size using the script from thia forum?

https://xdaforums.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
[Samsung Galaxy Nexus] _yen_:
Thanks for your willingness on testing this, if you prefer, to avoid to sync 7.1 again, I can send you some of my test builds.

Thanks

yen
[Samsung Galaxy Nexus] vortex-5:
I know I'm on MM I'm debating staying on it I'm about to take a 2 week vacation it's not the kind of situation I can tinker so most likely I'll be on MM until I get back.
[Samsung Galaxy Nexus] musical_chairs:
You could, but I don't mind; I already have it syncing. I've switched back and forth between 4.4 and 7.1 several times, it's no big deal. Besides, if you are right and your patch works, I can push it to gerrit for you. I can even try to put your name on the patch so you get the credit instead of me.