yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] musical_chairs:
Well, here you go: https://www.androidfilehost.com/?fid=962021903579493536

I have 4G working reliably, and coming up with no hassle after a reboot. I did mess around with it for quite a bit before I got things to be stable, so it might not be working out of the box just yet. Npte that this test build is not recommended for maguro. Some of the overlays I added may break things there. I need to figure out how to get this to 'play well with others' before I can push it to gerrit.

After flashing this test build, you should see the APN settings menu under Settings/Wireless & networks/More/Cellular networks/Access Point Names. If it's not there, try clearing data for Phone Services.

(Settings/Apps, tap 3-dot menu and select 'Show System', scroll down to Phone Services and tap on it, tap on 'storage', then hit ' Clear Data'. That should make the APN Settings menu available.

Check which APN is being used; you may need to choose one that lists LTE under 'Bearer'. If you still can't get LTE going, we may need to switch back to APNs that have only one bearer for each APN entry, rather than the newer APNs that use bearer_bitmask. If you can get the APN settings menu to show but can't get 4G going, I will put together a flashable zip with other APNs to test.

Have fun!
[Samsung Galaxy Nexus] kb8no:
Dang. I'm working long hours at the hospital but I'll find a way tomorrow.
[Samsung Galaxy Nexus] kb8no:
SIM not found on first boot as usual.

Reboot found SIM after obligate 1 minute wait as usual.

No APN setting found.

Phone Service clear data worked after reboot and APN setting found.

No LTE.

Default APN "internet".

Changes to "VZWINTERNET" which is my usual APN here.

Reboot.

No LTE

Multiple bearers in APN. All APN settings greyed out and no ability to make a custom APN.
[Samsung Galaxy Nexus] musical_chairs:
Try flashing this zip in recovery. You may need to reset APNs to default, the zip tries to do that for you but it may not be updated for N.
[Samsung Galaxy Nexus] kb8no:
BAM

No need to refresh.

Streaming jazz to my BT speakers in my office using LTE.
[Samsung Galaxy Nexus] musical_chairs:
Sweet!! Do you mind testing MMS yet, just to make sure I didn't break that with those APNs?
[Samsung Galaxy Nexus] bamtan2:
Wow, congrats [MENTION=4531957]musical_chairs[/MENTION]! Last I heard [MENTION=3390093]MWisBest[/MENTION] was carrying this stuff and it was voodoo. You are our new witchdoctor! ;) :good:
[Samsung Galaxy Nexus] kb8no:
MMS works!
[Samsung Galaxy Nexus] _yen_:
I got my maguro back minutes ago, no bootloop at all adding the ro.egl.destroy_after_detach property on UA 4.4 build from 10/24, so sorry for the false alarm.

bye

yen
[Samsung Galaxy Nexus] aboaboit:
When I did my testing recently, I installed your variant of TWRP, just to be as close as possible to your situation.

Right now, I've tried to perform an ADB backup from Flashfire and it's been stuck at "android" for a while already.

What's your take on this? Random lockup, known incompatibility of the rom with Flashfire or what else?

I've tried it twice, already.... funny thing is, adb reboot works.
[Samsung Galaxy Nexus] Android-Andi:
The issue should be gone for you on latest build.
[Samsung Galaxy Nexus] aboaboit:
Your TWRP or UA?
[Samsung Galaxy Nexus] Android-Andi:
UA
[Samsung Galaxy Nexus] Nonno Cicala:
I'm now using this build of UA 7.1.2 : https://www.androidfilehost.com/?fid=673791459329062290

It has the EGL_destroy patch applied and ro.egl.destroy_after_detach=true.

After more than 34 hours my system takes 433MB of RAM, and the number has been stable around that for 10 hours or more, so I'd say the EGL_destroy patch avoids the memory leak.
[Samsung Galaxy Nexus] aboaboit:
Does this include the GCC fix ?

I'd say it does, since my Maguro has now finished booting.

EDIT: saw just now your recommendation NOT to use with Maguro... I'll let you know if I spot some breakage.

What should I see? Right after boot it shows roughly 30megs free, not terribly unusual, but it is slowly climbing, which is odd :)

(flashed the latest pico GA and SuperSU)

Also, is the fix for Flashfire ADB backup already included in this unofficial build?

If it is, then it doesn't work. If it isn't, well, I tried :P
[Samsung Galaxy Nexus] musical_chairs:
1. Yes, the GCC fix was merged a few days ago, that is included.

2. I am trying to fix 4G for toro and made some changes to the CarrierConfig overlays. In this build, they are applied globally instead of being applied selectively dependent on the MCC/MNC as they should be. So it might mess up the cellular network settings menu for maguro, not sure.

3. Memory usage shouldn't be unusual, this does have the egl_destroy_after_detach patch - which has been merged and will be in all future builds.

4. Not sure about the Flashfire fix, I wasn't paying attention to that issue.
[Samsung Galaxy Nexus] kb8no:
So Toro 4G is band 13 only. A lot of band 4 out there. If I start up in "native" 4G and get out of range of band 13 it nicely "down shifts" to 3G. However it will never "up shift" back to 4G. If you remember "long time ago" when 4G was working there was still problems with "up shifting" to 4G. Seems like different old problem. Do you notice this? You can get it to "up shift" to 4G with the "airplane mode trick" but it will not do it automatically.

So if I start up in "native" 4G and it "down shifts" to 3G, when I make a phone call you naturally loose data but when call is ended and 3G tries to re-establish there is a tiny x in the 3G icon and data will not come back.

Curiously this does not happen with "native" 3G or with "native" 4G and data pops right up after a phone call. Have you noticed this?

Is there a way to force 4G only with no downshift?

When I have 4G it is robust and works great.
[Samsung Galaxy Nexus] Ziyan:
I spent some time recently with reproducing the memory leak. And yeah, the patch avoids it. It's now merged, so it'll be present in all future builds :)
[Samsung Galaxy Nexus] aboaboit:
1. ok

2. 3G connection seems to be working fine, using Wind (222/88)

3. I'm very pleased with this latest version of yours, the phone is quite responsive even after a few hours.

4. I think it was [MENTION=5153662]Android-Andi[/MENTION] (I can't mention him, the selection stops at the hypen)
[Samsung Galaxy Nexus] Android-Andi:
Nope, wasn't me telling about flashfire, never used it.
[Samsung Galaxy Nexus] aboaboit:
You did post this in reply to my question

I understood that in relation to Flashfire, what were you referring to?
[Samsung Galaxy Nexus] Android-Andi:
It was a general issue because by accident GCC4.9 was used which sometimes can make trouble on some tunas :-p
[Samsung Galaxy Nexus] aboaboit:
Ah, yes, I found out :D

Anyhow, this means my problem with Flashfire is still very much open. Considering the way it works (for ADB backups, it writes an openrecovery script and reboots), do you think I can follow the guidelines for submitting logs or would I be wasting everyone's time? Of course, assuming I am correct in reporting this in relation to this ROM, instead of, say, directly to Flashfire.
[Samsung Galaxy Nexus] bamtan2:
Try flashify or rashr. I googled flashfire and there are other people complaining about compatibility problems. The truth is that these apps are just a way to make using TWRP a few seconds more convenient. If you need to take more than a minute to deal with one of them (the way you have with flashfire), then it's not a useful app, and it should be skipped.

To manually flash from TWRP, hold the power button and hit reset to recovery (or hold all power and volume buttons from power-off), go to install, browse to downloads, sort by date, and pick the file to flash. Reset caches or factory reset after, depending on what you're doing.
[Samsung Galaxy Nexus] Android-Andi:
If my twrp fixes it it is https://gerrit.omnirom.org/25015
[Samsung Galaxy Nexus] Android-Andi:
Yes and yes
[Samsung Galaxy Nexus] Bludwurst:
For what it's worth one can also use an app to go more easily to TWRP, such as Simple Reboot — which is basically an advanced reboot menu and lets you reboot straight to recovery.

(This needs root obviously).
[Samsung Galaxy Nexus] aboaboit:
camera?

Anyone else using [MENTION=4531957]musical_chairs[/MENTION] recent build ?

Regardless of the app (tried stock, Google and OpenCamera), after a while the camera stops working until reboot. I haven't been able to pinpoint a cause, the symptoms are the same: apps hang with a black screen, even if the system otherwise behaves normally.

---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------

I'll have a look, thanks.

Nah, I wouldn't bother using Flashfire just for that: I liked the way it could create fastboot-flashable backups and stream them through USB. Very useful if your backup-phone doesn't have enough space to store the backup.

---------- Post added at 10:56 PM ---------- Previous post was at 10:44 PM ----------

Is this a new one or the same as #1862? I'm using that one currently.

I'll have a look as soon as I can, thanks.
[Samsung Galaxy Nexus] musical_chairs:
The data connection is still flaky at times. I've seen the '3G with x' icon after calls, but it typically connects for me after a few minutes. Not much time to test thoroughly ATM, very busy week at my day job.

Not that I'm aware of. There's an 'LTE Only' option in the 'secret' phone menu, but it seems to just completely kill the radio - I end up having to reboot to get any cell signal at all.

I still think the phone isn't happy about something with the APNs, maybe I'll have a chance to dig deeper in a few days. For now, I'm using the phone and haven't had any real issues other than what you mentioned above.

---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------

I'm using my latest build. :) But I'm using Android-Andi's no-CMA kernel, so the camera works fine for me.
[Samsung Galaxy Nexus] aboaboit:
I'll dig around and see if I can find the download link and how to install it (it's been a long time since I installed a kernel independently of a complete ROM, wetware memory isn't that good)

The real question is: how do I go back to the kernel in your build if, for whatever reason, I don't like the performance?

(after all, this is a backup phone and I care far more about the smoothness and responsiveness than I do about the camera)
[Samsung Galaxy Nexus] bamtan2:
The functionality to backup and restore the kernel is built into TWRP, but it is hidden a bit, and is a bit unintuitive. The downloadable kernel may be an img or a zip. If it's a zip, it's because the builder wanted to include a script to automatically put the img hidden within the zip in the right place. If it's just an img, then you need to enter the part of TWRP which flashes img files, and select the right place to flash it to. An error while doing this could be dangerous to the phone.
[Samsung Galaxy Nexus] Android-Andi:
You can simply flash anykernel with CMA enabled, it's the same source as we use on our official builds, sometimes it has some extra security updates before we merge then
[Samsung Galaxy Nexus] aboaboit:
I was curious to try the "no CMA" kernel, as suggested by [MENTION=4531957]musical_chairs[/MENTION] for the camera. But, again, I need more free time than I have and my main phone back, first :)
[Samsung Galaxy Nexus] musical_chairs:
Latest AnyKernel's are here, one with CMA and one without.

https://xdaforums.com/showpost.php?p=74480911&postcount=114

CMA kernel gives more free RAM and is better for almost everything. No-CMA kernel is better if you use your camera a lot.

You can always just flash the whole ROM again without wiping anything to put the stock kernel back in. But there's nothing special about the kernel in the ROM I posted - indeed there's nothing special about the ROM at all, except for a few small changes intended to get 4G working on toro.
[Samsung Galaxy Nexus] aboaboit:
I'll stick with CMA, then, until I can give it a spin just for fun.

Well, in my experience, the difference between the "official" one (meaning from build.u-a) from 9.11 and the build you posted is night and day: whereas in the first case it was usable but quite sluggish and needed a daily reboot (it would crash otherwise) your build has been generally smooth and manages to keep some ram free.

So, thanks for your work :)
[Samsung Galaxy Nexus] Ziyan:
This is because we merged a fix for the memory leaks - see #1933 :)
[Samsung Galaxy Nexus] aboaboit:
Yep, and his build is the only one that incorporates it in a ready-made zip if one doesn't want to setup a build environment :)

Saying thanks for a build I didn't have to do sounds like a good idea :)

EDIT: I actually thanked you on that post, too :)
[Samsung Galaxy Nexus] rahimali:
I'm gonna ask a very n00bish question and hope I don't get fried for it :D

The two patches that were merged into N, EGL_destroy patch and ro.egl.destroy_after_detach=true, would they result in any sort of improvement if they were merged into MM or LP builds or are they N specific only? Have you guys tried? :cowboy:
[Samsung Galaxy Nexus] musical_chairs:
Not a noobish question at all. And those patches were merged into MM, but not LP. From what I've read, the same issue theoretically exists in MM, though it doesn't seem to cause the dramatic memory leak there that it does in NG.
[Samsung Galaxy Nexus] musical_chairs:
toro users: I've been experimenting with apn settings some more. The phone persistently has trouble figuring out which apn to use for 4G, and it gets particularly grumpy about using the newer combined apns (the ones that use bearer_bitmask instead of bearer). But that doesn't seem to be what's breaking things. While I can't get 4G going with a 'flashed' apn using bearer_bitmask, it seems to work quite well if I program the apn manually through the apn settings menu. (see two posts down for a test build that unlocks the apn settings menu on toro)

Best-odds setup seems to be to delete all the apns (must be done one-by-one), leaving only our manually entered apn.

EDIT: Note that I still need to flash the 'APN fix' I posted earlier to get 4G working.

Here is what I am using currently. This is for Page Plus:

Name: Page Plus
APN: TRACFONE.VZWENTP
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
Server: Not set
MMSC: http://mms.vzwreseller.com/servlets/mms
MMS proxy: not set
MMS port: not set
MCC: 311
MNC: 480
Authentication type: Not set
APN type: mms,default,dun,hipri,supl
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
APN enable/disable: APN enabled
Bearer: EVDO_A, eHRPD, 1xRTT, EVDO_B, IS95B, IS95A, EVDO_0, LTE
MVNO type: None
MVNO Value: Not set

This is what it should be for Verizon:

Name: Verizon
APN: VZWINTERNET
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
Server: Not set
MMSC: http://mms.vtext.com/servlets/mms
MMS proxy: not set
MMS port: not set
MCC: 311
MNC: 480
Authentication type: Not set
APN type: mms,default,dun,hipri,supl
APN protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
APN enable/disable: APN enabled
Bearer: EVDO_A, eHRPD, 1xRTT, EVDO_B, IS95B, IS95A, EVDO_0, LTE
MVNO type: None
MVNO Value: Not set

Note that it is only the name, the APN, and the mmsc url that are different between these two. The contents of the APN field do not matter for 3G, but they are critical for 4G/LTE.
[Samsung Galaxy Nexus] kb8no:
I flashed your APN zip on your posted ROM. I can see no way to create a manual APN in the APN menu. What am I missing? Do I have to reflash and not use zip?
[Samsung Galaxy Nexus] musical_chairs:
No - I forgot I had added the change that allows adding APNs after I posted the previous build. Here, try this one:

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

Again, this is primarily for toro. I did test this one on maguro, and verified that it doesn't break anything there.

(I even tested it on toroplus, even though my two toroplus's probably make up half of the surviving toroplus's in the world) :silly:
[Samsung Galaxy Nexus] kb8no:
LTE not working on Verizon with new ROM and new APN. It's a pain to type in the APN took several tries. Triple checked it. Works like before on 3G but not 4G. MMS works.
[Samsung Galaxy Nexus] musical_chairs:
It's probably the wrong thing in the APN field. You could try flashing my previous APN zip, and once you have 4G again, check which APN is being used. I know it's a pain typing them, especially since after your APN is saved you can't change most of the fields. I'd like to get a flashable zip working with my settings, but I haven't managed to accomplish that yet.
[Samsung Galaxy Nexus] kb8no:
APN was VZWINTERNET, just the same. I know that by heart. So what fixed it on your Page Plus and what broke it on Verizon? They shouldn't be that different. Any way you can find an APN applet that let's you edit your APN you just made? BTW,. I'm very impressed we can make a custom APN at all!
[Samsung Galaxy Nexus] musical_chairs:
I'm not sure what broke it, I just took a stab at it based on what worked for me. And for editing the apns, there's no need for an applet; it can be done in the rom. (Just figured this out tonight.) Flash this little zip from recovery, and it will unlock the apn settings so you can edit to your heart's content.
[Samsung Galaxy Nexus] kb8no:
Doesn't seems to do anything or else I'm blind.
[Samsung Galaxy Nexus] musical_chairs:
It should make all the fields in each apn editable except the mcc, mnc, and enabled switch. You may need to clear data on the Phone Services app to make it take effect - I didn't have to, but I had cleared it earlier during a few failed attempts to get the overlays right.

Note that I still need to flash the 'APN Fix' I had posted earlier to get 4G working. I'm not sure exactly why. On first boot of the ROM ,or on APNs 'reset to default, the APNs in apns-conf.xml are written to telephony.db. When you delete them using the APN settings menu, they are still in the database. It seems we need to have the APNs from the APN fix zip in the database before our custom APN will work. It won't work if I just program the APN manually on top of the stock APNs, and it won't work if my custom APN is the only one in the database - even though all the others have been deleted from the menu. More research is needed here.

Anyway, here is an updated ROM with the overlay changes incorporated: https://www.androidfilehost.com/?fid=673791459329063815

All changes are now mcc/mnc specific, so they are safe for maguro.

Also included in this build are Android-Andi's test changes to the interactive governor.
[Samsung Galaxy Nexus] kb8no:
I wiped cache, Dalvik, and system. Not sure it is needed but that's what I do with UA.

I flashed all the zips together at once: your new 11/26 ROM, gapps pico, SuperSU, APN fix, and carrier config in that order with twrp. I rebooted. SIM came up in 4G. Able to edit all the APN's and make new one that is editable.

Observations:

I edited a default APN playing around and saved it . When I rebooted all APN's were gone and it would not reset the APN's. I have not tried to repeat this yet.

You can only make one custom APN. If you make a second one it erases the first one. :(

If you make a new APN and pick that new one it will stick now with a reboot and no need to delete all the other default APN's.

I am using your new ROM with the default APN that flashed with the APN fix zip. "LTE - Verizon Internet". It seems to be less flakey and more stable. Before I mess around more with custom APN's I will observe and report back.
[Samsung Galaxy Nexus] kb8no:
One of the research problems is that the notification tray icon can say LTE with bars yet you are not connected so it is hard to know when it is working. I found a useful app "internet connection checker" that I can watch and know for sure what's happening while I " research " what's happening.

The default from the zip quickly got flaky and my first impression was incorrect. I'm now experimenting with different permutations of my custom APN. If I make an APN change and save it, does it take effect immediately or do I have to reboot?

I still think the problem is the up shift from 3G to 4G and it fails to actually connect though it appears to be by the indicator. Would a log be helpful?
[Samsung Galaxy Nexus] musical_chairs:
Changes to your APN take effect immediately, no need to reboot. A log might be helpful if I knew what I was looking for... But I will be away for a bit and will not have any time for doing phone stuff for the next week or so. Thanks for all your testing and feedback!
[Samsung Galaxy Nexus] kb8no:
I figured it out trial and error. Having immediate effect sure helps. So I am away which gives me MORE time. Hahaha. If you are slow to respond I'll know.
[Samsung Galaxy Nexus] aboaboit:
Was that included in #1862?

If so, then that is the one I am using at the moment and it doesn't solve my problem with FlashFire "fastboot-style" backups.

Also, I don't think my phone is already encrypted: the "security->crypt" menu entry is still active.

(note: yeah, took me ages to answer this, sorry... I get around to answering the questions I see, eventually)
[Samsung Galaxy Nexus] aboaboit:
Installed it now on maguro, booted, seems fine.

And november update, too, wow :)
[Samsung Galaxy Nexus] OttawaNoLuck:
clang error?

Did unlegacy android switch to clang? When I try to build with a fresh checkout I get the error shown below. Installing clang doesn't help as it appears to be a hard coded path that it's looking for. Any ideas on what I can do to fix this? Thanks

prebuilts/clang/host/linux-x86/clang-2690385/bin/clang++ -fno-exceptions -Wno-multichar -m64 -Wa,--noexecstack -fPIC -no-canonical-prefixes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector -D__STDC_FORMAT_MACROS -D__STDC_CONSTANT_MACROS -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -O2 -g -fno-strict-aliasing -DNDEBUG -UDEBUG -D__compiler_offsetof=__builtin_offsetof -Werror=int-conversion -Wno-reserved-id-macro -Wno-format-pedantic -Wno-unused-command-line-argument --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 -fstack-protector-strong --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -Bprebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/bin -target x86_64-linux-gnu -Wsign-promo -Wno-inconsistent-missing-override --gcc-toolchain=prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 --sysroot prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8 -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/x86_64-linux -isystem prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/backward -target x86_64-linux-gnu -c -std=c++11 -g -W -Wall -MMD -MP -O -DNOLOG -march=native -o /android/out/host/linux-x86/obj/EXECUTABLES/ckati_intermediates/affinity.o build/kati/affinity.cc
/bin/bash: prebuilts/clang/host/linux-x86/clang-2690385/bin/clang++: No such file or directory

clang --version
clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
[Samsung Galaxy Nexus] Android-Andi:
Nothing changed. You can. Follow https://www.unlegacy-android.org/projects/unlegacy-android/wiki/Sync_ua