yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aboaboit:
I do not particularly need it, I am simply used to having root on custom roms, so I'm more than willing to give it a spin again.

Right now it came up but all attemps at adding a google account gave me "checking info" and then failure, both during initial setup and later.

I'll try this next:

ua_tuna-7.1.2-20171030050427.zip (instead of 20170918)

open_gapps-arm-7.1-nano-20171105.zip (same as now)
[Samsung Galaxy Nexus] Android-Andi:
You maybe like to check Magisk for root or try to find a newer SuperSU.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Don't forget: Latest October builds have KRACK fixed.
[Samsung Galaxy Nexus] aboaboit:
It might be so that the rom by itself boots but I kind of need GA to load and work properly, since this combo hangs at "google" too:

ua_tuna-7.1.2-20171030050427.zip

open_gapps-arm-7.1-nano-20171105.zip

I've seen another version of GA mentioned in the earlier posts, I'll give that a spin too and report here.

(EDIT: nope, gapps-base-arm-7.1.2-20170917-1-signed.zip hangs just like opengapps)

Another minor thing I noticed, possibly related to the repartitioning, but I am not sure: I can't flash the rom and GA nano back to back. I have to flash the rom first, go to the wipe submenu to perform a resize and then flash GA. Is this to be expected when using nonstandard partition sizes?

Also, reality check: am I trying to do something that's not yet known to work, i.e. 7.1+GA ?

I'd have no problem using 6.0 if 7.1 isn't ready for prime time. I have a loan phone with 2.3.6 that I am eager to replace with my gnex :P
[Samsung Galaxy Nexus] Android-Andi:
Just tested myself latest tuna 7.1 build:

Nano gapps also didn't worked to flash here, used Pico gapps which worked fine (haven't repit my device). Also I was able to setup and use my Google account without issues.
[Samsung Galaxy Nexus] bamtan2:
To everyone new: Always use the very smallest OpenGapps when you're starting out! There have been many times when larger gapps didn't fit, so save yourself the trouble and use the smallest gapps!

Testing file systems, partition space, and gapps compatibility is a separate job than getting your phone working for the first time!
[Samsung Galaxy Nexus] aboaboit:
I've already tried nano (with larger system size) and pico (with standard size): they flash ok (meaning TWRP doesn't bomb out when processing the script) but either the phone doesn't boot (if using a more recent 7.1) or gets stuck at "checking info" (if using ua7.1 from 20170918) when adding an account. I never try anything above nano anyway, learnt that with my previous already (zzrom).

[MENTION=5153662]Android-Andi[/MENTION] thanks for confirming it works with pico and default partitions. The weird crash that I experienced at my first go didn't help, but I'll try to go back to that partitioning and retest., tomorrow.
[Samsung Galaxy Nexus] Android-Andi:
I am using my own TWRP, not sure if it makes a difference.

http://andi34.github.io/recoveries_tuna.html
[Samsung Galaxy Nexus] PGHammer:
Pico, Pico, Pico (unless going older than L, then nano)

I have NEVER used nano GApps since Lineage 13 (Marshmallow) flagged it for being too big (and that was back when I was first looking at Marshmallow ROMs) - hence I haven't used it with any ROM newer than that. (In fact, I use nothing larger than nano even with KK.)
[Samsung Galaxy Nexus] aboaboit:
I'm willing to try it, if you believe it is relevant.

By the way, maguro_TWRP_3.1.1-1.img or twrp-3.1.1-0-maguro-decrypt-lzma.img?
[Samsung Galaxy Nexus] Android-Andi:
Doesn't matter, -1 might work with lineageos updates but I haven't tested if it works
[Samsung Galaxy Nexus] aboaboit:
More testing: (all files pushed to /tmp via adb and cache wiped, except where noted, and no supersu/magisk or anything else)

partitioning: reverted to original layout with lanchon-repit-20170115-system=654M-cache=432M+wipe-data=same-maguro.zip

recovery: https://eu.dl.twrp.me/maguro/twrp-3.1.1-0-maguro.img.html

rom: ua_tuna-7.1.2-20171030050427.zip (EDIT: fixed filename/version)

ga: open_gapps-arm-7.1-pico-20171105.zip

result: flashed ok, stuck at "Google"

rewriting bootloader ( as suggested earlier by [MENTION=6827887]nrichard7029[/MENTION] ) and radio from yakju-jwr66y-factory-4cadea65.zip ( just because it was there :P ) and repeating test above,

result: flashed ok, stuck at "Google"

changing recovery to twrp-3.1.1-0-maguro-decrypt-lzma.img and repeating the first test,

result: flashed ok, stuck at "Google"

going back to stock firmware, standard flash-all,

result: flashed ok, account configured, app update in progress.

So, I'd say the device is fine, hardware-wise, but there is something not quite ok with the rom, no idea what could still be different between my situation and yours, though.

Unless you have another suggestion, my next round of testing (possibly on wednesday night) will involve ua_tuna-6.0.1-20171027162949.zip
[Samsung Galaxy Nexus] Android-Andi:
Just for your information: on upcoming roms we remove the AOSP Browser for security reasons (it's outdated and has a bunch of security holes). You can install any Browser of your choice over f-droid or over PlayStore.

If you love OpenSource you might like to look at Lightning Browser (you can also download the apk from f-droid and install manually https://f-droid.org/en/packages/acr.browser.lightning/).

---------- Post added at 10:33 AM ---------- Previous post was at 10:06 AM ----------

[MENTION=7262819]aboaboit[/MENTION] idk what you are doing... But you should be able to get a dmesg at least, maybe a logcat too. Else go and get a last_kmsg

If you are usre how to get them: http://andi34.github.io/faq.html

Also note: before setting up a Google account on N you need to check play service and play store have proper permissions (mentioned in 2nd post of this thread).

Edit:

Also not sure why you use an older ROM, use latest one instead the old September build.
[Samsung Galaxy Nexus] aboaboit:
I remember using the one from 30.10, same as you did, but somehow forgot to edit the post :(

(reason is that 0918 at least booted, then got stuck much later...)

I am aware of the permission step but that applies after the initial bootup is finished and that doesn't happen here, yet-

Ok, as soon as I get the chance I'll go through the links and provide the logs you ask. Thanks again.

EDIT: yep, I tried ua_tuna-7.1.2-20171030050427.zip (bash history for the win!)
[Samsung Galaxy Nexus] ____Mdd:
Temporary solution for non-booting UA-7.1 build is to flash AnyKernel by Android-Andi...

I saw last few pages, everyone says repit/gapps/this/that... But it's nothing.. it's all about kernel.. i have flashed two times (30/10 build) and concluded it's kernel that we have to fix !!

I tried to take logs but it faild, i don't have PC, so i am doing everything with TWRP.

Log generated by TWRP terminal is of 0kb (so useless file)

But managed to take dmesg and kmesg (but both look like mostly similar)

See attachments.

I have another device, so can live with non-booting maguro, i mean if you need any thing tell me to do experiments with it.:)

Till than, can you provide AnyKernel updates for others ?
[Samsung Galaxy Nexus] Android-Andi:
That's crazy, there's one or 2 commits merged in kernel which shouldn't break boot and don't break it for me. sure, I can add 2 more anykernel to test and see if one of it is causing the issue for you. (Can't test because mine does boot without trouble)
[Samsung Galaxy Nexus] Android-Andi:
You've got a last_kmsg from the not booting kernel?

Only thing I could think off is a selinux denial which, why ever, isn't visible on my maguro.

Either, dmesg or last_kmsg is needed.

Edit:

Attached logs are useless because those are logs from recovery kernel... :(

---------- Post added at 06:41 PM ---------- Previous post was at 06:32 PM ----------

Maybe somone having trouble can test the following:

Backup important data first!

Format data -> confirm by typing yes

Advanced wipe: cache, dalvic/art, system

Reboot recovery once.

Transfer files via mtp or flash the rom from "adb sideload"

Don't flash gapps or SuperSU or whatever.

See if it boots.
[Samsung Galaxy Nexus] ____Mdd:
So i can't use use recovery to get those logs ?

I will try to get logs by adb as soon as possible..

I will also try to clean everything and flash rom via OTG, may be it can do same as sideloading..
[Samsung Galaxy Nexus] Android-Andi:
Thanks :) if it doesn't work I could provide the kernel with selinux to permissive
[Samsung Galaxy Nexus] gialakias:
I use unofficial du 7.1.2 with October security patch and it is just fine. And as far as I know it is based on this rom with the du goodies. Correct me if I am wrong. Using beans mini gapps from July and installing fine.
[Samsung Galaxy Nexus] ____Mdd:
cleared everything (system, data, cache, delvik, internal storage) then flashed from OTG, but same result.

Getenforce command in TWRP terminal says it's already permissive, i tried to set it enforce (by setenforce 1 ) but after reboot it changes to permissive again.

Is that TWRP kernel what i changed?

Can you give UA kernel with enforce and permissive and AnyKernel too for test?

EDIT: i can provide adb logs within an hour or two.:)

---------- Post added at 01:05 PM ---------- Previous post was at 12:50 PM ----------

It uses device and kernel trees only. if I'm too not wrong, using kernel tree and using source (UA) kernel, both makes difference. so it has nothing to do with UA.
[Samsung Galaxy Nexus] Android-Andi:
TWRP has an own kernel which is independent of the ROM kernel. I'll send you a permissive kernel later. If the issue is related to selinux it will boot and a dmesg from that kernel after boot is ok as it should show the denials if any.
[Samsung Galaxy Nexus] ____Mdd:
I have done adb sideloading after wiping everything, but no success for boot.

Adb logcat/kmsg/dmsg shows,

Error: exec '/system/bin/sh' failed: no such file or directory.

If i go through TWRP file manager, "sh" is there.

What next step should i do ?
[Samsung Galaxy Nexus] Android-Andi:
Attached kernel is permissive. If it boots: take a dmesg right after boot for me :)
[Samsung Galaxy Nexus] ____Mdd:
It doesn't boot.:(

Sorrry.. it booted...:)

Wait... Updating dmsg...
[Samsung Galaxy Nexus] Android-Andi:
Last_kmsg too please :)

---------- Post added at 10:43 AM ---------- Previous post was at 10:43 AM ----------

Lol, ok, give me 5 min and I attach another one
[Samsung Galaxy Nexus] ____Mdd:
Sorry for last one, it booted.

Here is dmesg taken just after bootanimation appeared,

phone booted to home screen, i will update kmsg after wiping again and at bootanimation..:)
[Samsung Galaxy Nexus] Android-Andi:
mh... there's no denials.... crazy.... can you get a last_kmsg?
[Samsung Galaxy Nexus] ____Mdd:
Here are both (dmesg again)..

(this combination boots, no matter how i flash /OTG/internal SD/sideloading all works.)
[Samsung Galaxy Nexus] Android-Andi:
I need a last_kmsg right after boot after a clean flash.

adb root
adb pull /proc/last_kmsg

Tuna reboots once after detecting & setup for your tuna variant - if there's something wrong we'll see it in last_kmsg.

Edit:

Attached another kernel, back to enforced, let me know if that one boots too once you have taken a proper last_kmsg from permissive kernel right after clean flash.
[Samsung Galaxy Nexus] ____Mdd:
I used "adb shell cat /proc/last_kmsg > file.txt

And pull too.. both gave same file except pulled file text is mixed up (no "enters" there after one line) again attached both.

Last_kmsg : pulled one.

3kmsg : generated by command (told above)
[Samsung Galaxy Nexus] ____Mdd:
Yes, it booted.

Clean flash and over permissive (dirty), both time it booted. Attached it's logs too, kmsg by both method.

Now i can't use adb stuff, it was someone else's PC, i will see tomorrow at college, or may be at evening somewhere. Till you can tell me what is next to test.
[Samsung Galaxy Nexus] Android-Andi:
Ok, turned out: 7.1 was compiled using GCC4.9 [emoji23] [MENTION=2633638]Ziyan[/MENTION] found out by accident that we changed custom toolchains usage on N (I've changed it on Omni and Slim and never thought crosschecking here because everything worked).

Should be fixed now :) and I am sure [MENTION=2633638]Ziyan[/MENTION] has more to tell for you.
[Samsung Galaxy Nexus] ____Mdd:
9-11 build is booting..:laugh:

I must say, we have the best development team.. Thanks for all your work...:good:

PS: it boots with any mod, i tried with superSU, gapps, repit and busybox.. everything is fine..
[Samsung Galaxy Nexus] aboaboit:
I can confirm I did try ua_tuna-7.1.2-20171030050427.zip ( #1866 and #1868 have been edited )

Could that be my problem as well? I am going to try the newer version.

EDIT: it works :)

Wifi seems to be unstable, possibly because this unit is already known to have poor performance on the 5GHz band.

How do I restrict wifi to 2.4GHz?
[Samsung Galaxy Nexus] uji_sine:
I can not find 11-09-2017 build, could you please give me link. Thank you.
[Samsung Galaxy Nexus] ____Mdd:
You will see last build is "experimental" and of date "8-11" in 7.1 as they are shorted name wise, just above experimental, that is 9-11 build.. https://builds.unlegacy-android.org/aosp-7.1/tuna/
[Samsung Galaxy Nexus] uji_sine:
Thank you so much.
[Samsung Galaxy Nexus] musical_chairs:
@ toro users: If anybody has a toro and a Verizon SIM and would be willing to test a few things, try this build:

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

I need to know if MMS still works on a Verizon SIM with my changes. I have a Page Plus SIM and everything is working great now (except LTE, but that's another issue). If your phone is not currently activated, you'll need to flash a KitKat or JellyBean ROM, then insert the SIM and let it load that, then flash this ROM to test. If your phone is already activated and running ua7.1, you'll need to either do a clean flash of this, or reset apn's after flashing to make sure the changes are applied.

If the phone continues to say 'No SIM Card' for more than four minutes after completing the first boot, reboot and it will find the SIM. This problem shows up on the first boot only (occurs on all android 7 builds I have tested.)

You'll also likely need to change the Preferred Network type to 3G/CDMA:

/Settings/Wireless & Networks/More/Cellular Networks/Preferred network type

Here are the changes on gerrit:

https://gerrit.unlegacy-android.org/#/c/3874/

https://gerrit.unlegacy-android.org/#/c/3875/

I removed a few more of the leftover Verizon proprietary libs. I also removed the toro-specific apns we had been using, apparently there have been some network-side changes and we no longer need these.

Thanks for testing!
[Samsung Galaxy Nexus] kb8no:
I will test for you later today. I can say that MMS works on 11/9 build already. Can I dirty flash over 11/9 build?
[Samsung Galaxy Nexus] kb8no:
Dirty flash. SIM comes up on reboot as advertised with 3G. MMS and SMS work just as 11/09. Don't find place to set APN yet, can you? LTE of course doesn't work. Want me to check something else?
[Samsung Galaxy Nexus] musical_chairs:
To reset the apns on 7.1, I use the app Activity Launcher. From the drop-down menu in the app, select 'all activities', scroll down to 'Settings' and tap on it. APNs will be about the fourth one down inside 'Settings'. Click on it and it will open the APNs menu, which will be blank. Tap the three-dot menu in the upper right-hand corner and select the only option, 'Reset to default.' This will erase your current APNs from the dirty flash and replace them with the APNs that shipped with your currently installed ROM. Test MMS again, and post your results.

(You can also reset the APNs by deleting a file in recovery or using adb shell, but it moved in 7.1 and I don't remember the new location.)
[Samsung Galaxy Nexus] kb8no:
SMS MMS Works! Is there a real app that can set APN?

See again proof of 4G data I showed you some time before so I still maintain the RIL must be close.
[Samsung Galaxy Nexus] kb8no:
This
[Samsung Galaxy Nexus] kb8no:
Umm. This
[Samsung Galaxy Nexus] musical_chairs:
Thanks for testing. Yeah I remember you had 4G working. Back then I couldn't even get 3G going. Now that 3G and MMS work for me on 7.1, I can dig into things again and maybe figure out what is up with 4G. The only thing I can figure out is that Verizon made some changes on their end that fixed things for me. I don't need the special TRACFONE apns to get a data connection anymore on Page Plus, the regular Verizon ones work again after over a year of not working. Go figure.

As far as setting the APNs, on 6.0 we needed something like this to make the APNs show up in the APN settings menu: https://review.lineageos.org/#/c/71172/

I tried implementing that patch in UA but haven't gotten it to work as of yet. I believe that that one, along with this one, will be needed to fix 4G: https://github.com/CyanogenMod/andr...mmit/7a2fa6272bdfcf8b4bc665848a56689271e1b573

Another dev also suggested I try this one: https://review.lineageos.org/#/c/168326/

...but I don't think that one makes a difference on our devices.

So anyway, there are a few ideas, I'll keep poking at it. I'm not the sharpest tool in the shed so don't hold your breath, but I actually use this as my main phone, so who knows? Thanks again for testing.
[Samsung Galaxy Nexus] kb8no:
[MENTION=4531957]musical_chairs[/MENTION] so initial impressions are that I notice the data 3g icon at the top is more stable than in the previous build and doesn't oscillate between 3 bars and zero bars as before. More steady. Take this as improvement at least in appearance. The ping here is ~ 100 ms and the upload / download ~ 1Mbps as expected for 3G. What APN did you program into the ROM? Once again it would be great to be able to easily identify and change APN.

Sorry. Ignore attachment.

Addendum: I put it on LTE and rebooted. Icon at top blank with no LTE letters but bars as expected. Able to make phone call and able to send SMS. Not able to send MMS. So as you would expect with cell connection but no data.
[Samsung Galaxy Nexus] Android-Andi:
if you guys have some time you could test if

ro.config.low_ram=true

in build.prop makes a difference (especially on 7.x)
[Samsung Galaxy Nexus] kb8no:
Makes a difference in what? What should we be looking for?
[Samsung Galaxy Nexus] bamtan2:
If it works well, you should not notice anything ;)

If it works less-well, you should notice some apps reducing their features. Because I think this setting provides an optional warning to apps, saying "this device manufacturer requests that you use as little ram as possible."

We tested this in the past and I only remember the effect being minor. I will happily turn it on now and see what happens!

I think the "kernel adiutor" app will make this easy to change...
[Samsung Galaxy Nexus] Android-Andi:
Someone told it makes the device more fluid
[Samsung Galaxy Nexus] bamtan2:
I tried on UA 6 and all I notice is the recents menu slows down and the system GUI colors shift/invert randomly. 0_o

Setting it to false caused the system to bug out, but restarting and deleting it altogether with buildprop editor worked.
[Samsung Galaxy Nexus] musical_chairs:
It definitely makes a difference, it trims the ram footprint of system by about 300 MB. It also makes things look uglier than 4.4. The status bar and soft keys bar are always black and it disables the lock screen wallpaper. I think I'd rather reboot my phone every day. :silly:
[Samsung Galaxy Nexus] bamtan2:
Testing this with one of zeelog's builds that has zram enabled, to kill two birds with one stone. ( https://zeelogkang.blogspot.com/2017/07/resurrectionremix-nougat-rr-n-v583.html )

The rom itself is buggy, but the memory performance seems really good, and I haven't yet run into a problem that looks like it's caused by the lowmem switch. The color inversions from UA 6 aren't happening in 7.1.
[Samsung Galaxy Nexus] aboaboit:
Has anyone tried the Google Dialer with 7.1 from 2017-11-09?

(I also have GA pico installed).

It worked, but in a funny way: I made a call by clicking a number in the contactbook, the app did not show up, the notification icons did not change but the call was estabilished. I had to wait for the other party to hang up because even restarting the app did not give me the red button to hang up.

PlayServices has all the permissions and the dialer has what it asked for, phone and contacts.

I can always go back to stock AOSP dialer, I'm not too fussy about this, just curious :)

EDIT: went back to stock dialer, works fine, case closed :)
[Samsung Galaxy Nexus] Nonno Cicala:
7.1.2 memory leak

I gathered some data about memory use of Unlegacy 7.1.2, 6.0.1, and other ROMs with a minimal installation, without GApps, without root and with 5-7 fixed apks. It shows that 7.1.2 system components suck RAM, so that in less than 48 hours the phone soft reboot, while 6.0.1 is working fine.

Data here:

https://docs.google.com/spreadsheet...kiGyy6iwhYoYQPjLHdn/pubhtml?gid=0&single=true

I took the data from Developer Options -> Running services , from the System line as shown in the screenshot attached, without apps in Recents and with the phone not connected to power or PC. The number I recorded (in MB) is the highest number shown for at least 3s, in an interval of at least 30s, to avoid random spikes.

After a first set taken from a full system with Slim7 1.7 I tested different versions of Unlegacy and ZZ Tuna ( https://xdaforums.com/galaxy-nexus/development/rom-t3297218 ). Every installation was done with TWRP 3.1.1-1 ( https://androidfilehost.com/?fid=961840155545590690 ), the procedure was to do a factory reset, then wipe System partiton, install the ROM and reboot. Then I installed the apks (listed in the above data sheet) with adb.
[Samsung Galaxy Nexus] bamtan2:
Really superb work! So you've basically shown that android 7 becomes unusable after a day. That explains why my test device seemed to be resetting or crashing randomly when I wasn't around... it was just a time bomb! And this also explains why so many users have said that they prefer android 6, and why I found android 5.1 to be so great.
[Samsung Galaxy Nexus] aboaboit:
Good thing I decided to read all the past messages, just in case :)

I had this happen a couple of times, I thought I had a black cat moment :D

EDIT: when it happens, like just a short while ago, the 3G network is lost and the SIM icon is greyed out.

A reboot fixes that.
[Samsung Galaxy Nexus] musical_chairs:
Agreed. But until I can get Android to properly read the SIM, the APN settings menu will stay blank. In 6.0, we used this patch, however I haven't been able to get that working on 7.1. I'm pretty sure that fixing that will be needed to get LTE going properly. The motorola omap4 guys are using this on LOS 14.1, but I don't know how to adapt that to our RIL, or if that is even possible. So I am stuck at the moment - albeit with a very stable 3G connection. :)

I didn't exactly 'program' an APN into the ROM, I removed the modified APN we had been using for MMS and reverted to the APNs that come with stock AOSP. i discovered by accident that it not only works, it works better than what we had been using.
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=4465682]kb8no[/MENTION] : Guess I'm not quite as stuck as I thought. I can reliably connect to 4G, though not automatically yet. More details to follow when I can figure out what exactly I did that got it going.
[Samsung Galaxy Nexus] kb8no:
Whoaaaaaa....! I wanna be the second to use it.