yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] vortex-5:
I just swapped my partitions back to EXT4 honestly don't see a performance difference so the feeling that f2fs was faster was probably a cleared cache and a placebo.

the -30mb bug though that's legitimate I notice apps tend to crash when it's displaying this so it's probably being honest about low memory.

does nougat hold onto memory more than marsh mallow or is the base system just more of a ram hog?

---------- Post added at 10:50 AM ---------- Previous post was at 10:44 AM ----------

Actually looks like the lock screen memory leak is still present on 7.1.2 you can test this yourself.

Go to settings -> developer settings -> running processes. Observe free ram.

Now lock your phone and unlock it about 10 times (which is probably much higher during a typical day).

Notice your ram goes away and never comes back. I start with about 400MB and by locking and unlocking about once a second I can get the free ram down to 250MB and it doesn't get released if I let the phone "rest" so I think this is probably the culprit. There was an outstanding commit that was never merged into legacy that was attempting to address this leak.

for the time being I'll move back to 6.0.1
[Samsung Galaxy Nexus] runekock:
I think that f2fs got sufficiently stable around kernel version 3.16. On older kernels, a massive backport is required, and I don't think that has been done on any GN kernel.

[MENTION=5930928]vortex-5[/MENTION]
[Samsung Galaxy Nexus] n76:
Thank you for the explanation.
[Samsung Galaxy Nexus] h4xx0rr:
android Oreo is pushed to aosp..

can we expect new android on GN or should I buy new phone :)
[Samsung Galaxy Nexus] guest4711:
Yeah ;)
[Samsung Galaxy Nexus] bamtan2:
I don't think we can expect volunteers to do all the work to bring up a new operating system for free. I also don't think donating to them is enough either, because we only donate small amounts. I DO think we can donate and thank them for bringing up android 7.0, and if they feel like bringing up android 8.0, we would like that too ;)
[Samsung Galaxy Nexus] Android-Andi:
What's wrong here? Tags are pushed minutes ago...

And yeah, we'll look at it when we have time. E.g. i am limited this week, not going to work next days but birthday, appointment at the doctor etc.

Thanks [MENTION=4545566]bamtan2[/MENTION].
[Samsung Galaxy Nexus] uji_sine:
[MENTION=5153662]Android-Andi[/MENTION], happy birthday. And many thank for your work.
[Samsung Galaxy Nexus] Android-Andi:
Thanks, but you are to fast ;)
[Samsung Galaxy Nexus] Bobcus Leper:
Hi,

[MENTION=2633638]Ziyan[/MENTION], [MENTION=5153662]Android-Andi[/MENTION], First of all, thanks for all of your work on the OMAP-4 platform. Your work is incredible! I know stargo (my device maintainer) is listed as one of your contributors, so I was wondering if you could add the Droid Razr (spyder and umts_spyder), the Droid Bionic (targa), and the Droid 4 (maserati) to your devices list, considering that they all share the same OMAP-4 platform with the Tab-2 and Galaxy Nexus. I would be more than willing to use my device as a guinea pig.
[Samsung Galaxy Nexus] vortex-5:
How did you guys get Magisk to work? I'm not seeing magisk after flashing the zip. Does magisk manager come with flashable zip or do you have to install that apk via other means?

Nevermind I figured it out. Ignore this post.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=5711114]Bobcus Leper[/MENTION] stargo can join us or you setup proper device trees for it. We aren't going to do "blind" support.
[Samsung Galaxy Nexus] aro8366:
Is oc possible on marshmallow version of UA?

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] kerpert:
I'm pretty sure there isn't a working kernel with 6.x for overclocking, I never found it.
[Samsung Galaxy Nexus] Bobcus Leper:
Deleted
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=5711114]Bobcus Leper[/MENTION] that's not enough. There's lineages parts which needs to be removed and also there might be additions on our build system needed to get them booting.

You'll have to look into it or someone else who owns the device.
[Samsung Galaxy Nexus] bamtan2:
Your post is good, you don't need to delete it :)

These developers are volunteers trying to maintain many devices and they need help ;)
[Samsung Galaxy Nexus] victoralexbr:
Version 6.0 is up and running great, without any video artfacts like the slim 7.1

is the 7.1 unlegacy still stuck in the google logo boot?
[Samsung Galaxy Nexus] vortex-5:
Version 7.1 works I think it's still memory leaking at the lock screen though. Every lock seems to eat 30MB I moved back to 6.0.1 on my maguro I'll probably be leaving this phone soon though as a daily driver.
[Samsung Galaxy Nexus] diogofd8:
I tried the 4.4.4 version and flashing superSU doesn't grant root permissions.

Flashed marshmallow and obtained root through magisk, but I'd like to have the 4.4.4 on my phone as it's more fluid and customizable.
[Samsung Galaxy Nexus] dpunx:
I tried with 7.1.2 but no way to work on my maguro GNeX :/
[Samsung Galaxy Nexus] calabross:
hi guy,

have all the android 7 release the same problem you reported?

can you suggest an android 6 release that works well (gps, bluetooth, wi-fi, camera, and so on...)?

many thanks
[Samsung Galaxy Nexus] bamtan2:
this thread is for unlegacy, so try unlegacy 6! ;)
[Samsung Galaxy Nexus] calabross:
you're right but i think someone can answer without going out of topic at all... ;)

anyway, can someone explain what are the main differences between the unlegacy and other "custom" roms (eg unicorn dirty, lineageOS, etc.)? I mean, I can consider unlegacy as "basic" roms that have less functions than "customs"?

are there any major bugs in unlegacy roms that can limit phone usage (gps, bluetooth, wi-fi, camera, etc ...) or they are fully working?

Thank you
[Samsung Galaxy Nexus] bamtan2:
ziyan is the lead maintainer of this device and unlegacy is the rom he created. all the other roms are based on unlegacy. unlegacy has the fewest OS features but the newest AOSP code.
[Samsung Galaxy Nexus] kb8no:
Here's my Verizon Toro upgrade report If anyone is interested. Came from ua_tuna-7.1.2-20170620.zip which was working surprisingly OK. Used twrp-3.1.1-0-toro.img. Did clean install and wiped cache, Dalvik, system, and data. Flashed ROM, open_gapps-arm-7.1-pico-20170908.zip and SR3-SuperSU-v2.82-SR3-20170813133244.zip. Reboot system. BAM.

I have a new WiFi 5GHz router and it connected but was flaky. Had to mess a bit with Google registration but could well be because of the WiFi drops. At any rate, I managed without great difficulty. As the day progresses the 5GHz seemed to have settled in.

GPS, Google Maps, SuperSU, Play Store, camera, and Root Explorer all work properly without problems. Overall much smoother than 6/20. Have not yet appreciated alleged memory leak yet.

The 6/20 worked well on Verizon SIM with 3G and unpredictably on 4G. When I find my dongle with the SIM I will report back. VERY pleased so far. Horary for the GNex!
[Samsung Galaxy Nexus] kb8no:
I found my Verizon SIM for my Toro. I can't comment about LTE because Toro has only band 13 and Verizon is serving up band 4 here. I will try band 13 again later. However, no LTE then 3G will not start.

However, if I choose 3G CDMA preferred network then, BAM, I get 3.5G EVDO with Speedtest of 1M. If 6/20 UA experience is repeated, it is then steady and reconnects predictably after signal drop. Therefore, RIL does indeed work for 3G Verizon and this is a usable 3G phone.

LTE was a different intermittent matter on 6/20. When it did decide to unpredictably start then when band 13 dropped it would drop down to 3G as it should but never see LTE again and if 3G dropped it would not restart unless you changed default from LTE to 3G CDMA.

Then, remember, Verizon GNex cannot initiate a Verizon SIM and register on the phone on the network above KK ROM. I keep a KK backup on my phone only for that purpose.

I have zero Maguro experience so none of this may hold there.
[Samsung Galaxy Nexus] kb8no:
Phone didn't work so went to Verizon and USB modem SIM was set to no phone calls. Gave me a new full featured SIM and phone works fine. I have been unable to message LTE to work yet.
[Samsung Galaxy Nexus] Android-Andi:
Update for 6.0 for 2017-09-01 security patch level will be available later today :)
[Samsung Galaxy Nexus] kb8no:
More toro observations ...

7.1 ROM was noticeably laggy but after 9/14 upgrade I found a big improvement. I have no idea what this means.

After flashing or upgrading the Verizon SIM is not recognized but after several reboots it suddenly starts working and then sticks. I had the same experience with SLIM.

After flashing or upgrading the WiFi N 5GHx struggles with frequent disconnects but also after several reboots it suddenly settles in and sticks.
[Samsung Galaxy Nexus] Kralle_bw:
Trying to update my maguro to a newer 7.1.2 build, I only stuck at the google logo and the phone isn't starting.

Last working build is ua_tuna-7.1.2-20170808052223.

Any solutions?
[Samsung Galaxy Nexus] Android-Andi:
You've flashed magisk or something else?
[Samsung Galaxy Nexus] Kralle_bw:
Only flashed ROM and GApps (Arm 7.1 pico)

Nothing else.
[Samsung Galaxy Nexus] Kralle_bw:
The newest build ua_tuna-7.1.2-20170918073244 is now booting as it should.

Thank you!
[Samsung Galaxy Nexus] frusso3:
Hi guys, I'm still with 11 cm and I'm fine. I would like to install the 6.0 rom and I wanted to know: is it okay for every day? Any problems? Are the pictures good? Does USB otg work? I still twrp 2.8.7, do I have to update it? Thank you all
[Samsung Galaxy Nexus] bamtan2:
These ROMs have similar code base, so you do not need to ask twice ;) https://xdaforums.com/showpost.php?p=73854162&postcount=1276
[Samsung Galaxy Nexus] frusso3:
Sorry, I was trying to figure out which of the two is better :)
[Samsung Galaxy Nexus] bamtan2:
Lineage has more features. Both are built by the same volunteer developers. ;) Some people like 6 better than 7.
[Samsung Galaxy Nexus] frusso3:
I suspected him, now I have cm11 and I'm fine. I have only a few problems with the browser that occasionally hangs
[Samsung Galaxy Nexus] edu24lal:
Has anyone tried new unlegacy build? If yes, still memory problem? And what about video playback?
[Samsung Galaxy Nexus] bamtan2:
FYI [MENTION=2633638]Ziyan[/MENTION] graduated from school, was hired by a company to work on android, and has successfully brought android 8.0 to nexus 4: https://xdaforums.com/showpost.php?p=73778352&postcount=158

Congratulations for everything Ziyan :)
[Samsung Galaxy Nexus] Ziyan:
Thanks :) and don't worry, tuna isn't abandoned either, but bringing up O with our 3.0 kernel is significantly harder than bringing up devices with 3.4 kernels. So, I started with those, first. :)
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=2633638]Ziyan[/MENTION] is picking the Jelly Beans first [emoji23]
[Samsung Galaxy Nexus] secretwolf98:
Comment deleted, wrong thread.
[Samsung Galaxy Nexus] nrichard7029:
[MENTION=2633638]Ziyan[/MENTION] Isn't there a way to update the existing kernel to 3.4? I think there are patches to do that:

- https://android.googlesource.com/kernel/goldfish/+/android-goldfish-3.4

Or even 4.4?:

https://android.googlesource.com/kernel/common/+/android-4.4-o

I have heard though it would take a while to fix all errors and put the device binaries in them.
[Samsung Galaxy Nexus] bamtan2:
I think they've looked into this, and it would take a lot of work! ;)
[Samsung Galaxy Nexus] Kralle_bw:
The memory problem is still present on my maguro.
[Samsung Galaxy Nexus] PGHammer:
GNex vs. Nexus 4

What SoC does the Nexus 4 use?

It may well be that the OMAP4 SoC our beloved tuna uses is a bit TOO long in the tooth - even compared to the Nexus 4.

Ouch - that may well be it. The Nexus 4 uses a quad-core CPU (albeit a rather long-in-the-tooth one from Qualcomm of all folks - the APQ8064).

It (the Nexus 4) has less storage than the GNex (max of all of 16 GB; half the 32 GB of the GNex) - and no - it doesn't support microSD, either; however, that it's a quad-core is doubtless getting it devel props. (All specs via gsmarena.com)
[Samsung Galaxy Nexus] bamtan2:
OMAP4 can definitely run android 8, the problem is software development takes a lot of hours work from a lot of smart people, and I don't see anybody paying the bills for OMAP4 development! ;) So we must wait for people to volunteer their time.
[Samsung Galaxy Nexus] PGHammer:
No dispute here; all I am saying is that quad-core CPUs are generally more favored than dual-cores (even dual-cores like the TI OMAP where all the source is open, as opposed to quad-cores where there are still binary-blobs - which Qualcomm DOES have a history of); if things were otherwise, the Mediatek CPUs would be getting more love than they do.
[Samsung Galaxy Nexus] Max1306:
Great work!! Thank you.

Even the Blueborne-Patch is included. Only OTA update does not work. I did an "dirty flash" (only cache wipe) including the GAPPs pico. Everything works excellent.

Is it necessary to flash the GAPPS again during a "dirty flash" for update?

Max

Galaxy Nexus i9250
[Samsung Galaxy Nexus] Android-Andi:
Next 6.0 build contains the October security bulletin
[Samsung Galaxy Nexus] yossSP:
Yes, you must do it , and it's recommended to upgrade GAPPS to the actual version when reinstall.
[Samsung Galaxy Nexus] HypnoticSilence:
I can confirm the October 5th build for the 7.1.x does NOT have the October Security Patch.

Beyond that, is anyone having issues with battery life on 7.1.x?
[Samsung Galaxy Nexus] Android-Andi:
Anyone said it has?

Anyone seen a new Google tag for 7.1.2?
[Samsung Galaxy Nexus] HypnoticSilence:
I wasn't contradicting you, if that's what you were referring to.

I was stating that the 7.1.x doesn't have it.

I'm not sure what you mean by Google tag, since I'm going solely off the thread.

EDIT: Also, would you recommend 6.x over 7.x for stability / security purposes? I have no issues with downgrading or reflashing -- just curious.
[Samsung Galaxy Nexus] Android-Andi:
Sounds like complaining, writing in BIG letters never looks good.

7.1 currently don't have the updates because Google did not released new 7.x source with needed fixes (=no new tag). This means: we have to check the bulletin report and pick/Backport everything needed from 8.0.

Be patient and it'll be updated once someone of our team has time for it, if someone thinks to complains it'll never been updated.

ProTip: Don't make the same fault Tab2 community did ;) (but it's the best example of how the Android community changed in the past years: user think we owe them something, but no: we are doing this just for fun and for free and there's only a tiny part of the community donating a few bucks for the countless hours we spend.

We provide security updates frequently, on most devices you never get any because there's no rule for OEMs and there's no central place in 2017 for OS Updates on Android Phones - sounds like a bad joke but it's reality.)
[Samsung Galaxy Nexus] ramosroger:
Wow you're video inspired me to go on a weight loss journey
[Samsung Galaxy Nexus] AgentSmith:
Here's a logcat of the frequent wifi drops I'm experiencing.

I'd also like to add that wifi is drawing a lot of power. And there's that strange over-counted again.
[Samsung Galaxy Nexus] RansuGiru:
This is off topic, but does this ROM include patches to address the recent security exploits discovered in Android?
[Samsung Galaxy Nexus] grognaz:
In the about section is says :

Android security patch level

March 1, 2016

So i guess that its adressed
[Samsung Galaxy Nexus] thagringo:
I take back what i said before.

Have been using your suggested scheduler settings for a couple of days and switched back today to the stock ones. Now it feels a bit laggy, will use your settings from now on.

Thanks !

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] phaleg:
I flashed this ROM on maguro last night ... Up to now it is working great.

I followed the procedure, but I was able to set google right away, se Linux was set on permissive ...

I didn't flash superSU yet.
[Samsung Galaxy Nexus] PythonNut:
As far as I can tell, there hasn't been much new pushed to the repos, so a new build wouldn't make very much sense.
[Samsung Galaxy Nexus] massima:
What i can say....................you did a miracle with this rom:D, the use of the f2fs could make it faster with a working TWRP recovery.

I cannot mount my usbkey via OTG, stickmount tries to mount it without success. Also i cannot view in greenify the "aggressive doze" mode isn't available in the app, i think it is due to the customization of the rom.
[Samsung Galaxy Nexus] thagringo:
Aggressive doze isnt available because doze isnt working ( yet, hopefully ...)

Cant help with otg, last time i tried it worked IIRC.

Cheers
[Samsung Galaxy Nexus] PythonNut:
I've noticed a curious problem.

I'm trying to move the TWRP backup of my previous ROM to my NAS, and no matter what I try, I can't seem to get the file off the phone.

I've tried:

SMB (over the network/with various apps)

SFTP (over the network/with various apps)

MTP (over USB, I think I remember reading something about MTP problems upthread)

And all of them freeze the phone after 400-600MBs are transferred. If you wait long enough (several minutes) the device comes back alive and you can use it again, but the transaction fails. Fortunately, I can get the files off the device using TWRP and MTP, but that's obviously not optimal.

I've attached a logcat for each transport type I tried.
[Samsung Galaxy Nexus] siealex:
Try ADB pull.
[Samsung Galaxy Nexus] Nautilus74:
Same problem on my gnex...

http://xdaforums.com/showpost.php?p=65879951&postcount=91

The problem is present with ANY file >400MB

No problem on other roms....
[Samsung Galaxy Nexus] AgentSmith:
That and I'm getting other serious problems too. Battery usage data is completely corrupt now. The data either don't appear or percentages go well over 100%. A full recharge doesn't fix this.

Every reboot causes time and date to reset to the year 2000. I've found this not to be a hardware issue because after a TWRP-TWRP reboot date and time remain intact.

/System somehow got filesystem errors. I managed to repair those with TWRP's command line using the e2fsck -y command on the proper device. The built-in repair function in the TWRP GUI gave an error=4.

Wifi is still very erratic. At times it stays on for a while but most of the time it disconnects within a matter of minutes and sometimes even seconds. Now that even happens when the phone is being actively used. Very annoying. I've already posted a logcat.
[Samsung Galaxy Nexus] siealex:
It's definitely a hardware problem, most probably RAM, maybe also flash memory. Wi-Fi sometimes disconnects on screen lock, but not when it's constantly active.
[Samsung Galaxy Nexus] PythonNut:
The same things happens. Unfortunately, I don't have a logcat, since, due to some unfortunate circumstances, it takes me seven hours to produce one.

If you guys really want one, I can get it on the weekend.
[Samsung Galaxy Nexus] osm0sis:
First I'd try a different I/O scheduler and double check your I/O queue options. If that doesn't work then try Repair under Advanced Wipe options in TWRP. And if that doesn't work, maybe try after a fresh format?
[Samsung Galaxy Nexus] aosp:
The more logs the better guys if possible zip up these folders and upload them to a hosting site for the devs can take a look at them please

/data/tombstones

/data/system/dropbox

/data/data/com.android.shell/files/bugreports

You could trigger a bugreport by pressing and holding down both volume rockers and the power button simultaneously

Also if possible grab all logs after you get any crash with https://play.google.com/store/apps/details?id=com.tortel.syslog
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] Have you used any of the below tools for reading bugreports before?

https://android.googlesource.com/platform/tools/loganalysis/+/master

http://developer.sonymobile.com/kno...se-your-bugreports-with-our-open-source-tool/
[Samsung Galaxy Nexus] osm0sis:
Nah, looks cool though!
[Samsung Galaxy Nexus] aosp:
[MENTION=6906944]PythonNut[/MENTION] [MENTION=4758810]Nautilus74[/MENTION]

Besides the logs I mentioned in my prior posts can both of you guys post a screenshot of the below app please?

In the MMC drop down section please also take a screenshot of the info shown after pressing the eye ball thanks

https://play.google.com/store/apps/details?id=com.humanlogic.sdi
[Samsung Galaxy Nexus] HypnoticSilence:
I assure you, I'm not complaining. I do appreciate the effort put into this -- especially considering it's a much older device that most developers would probably overlook since it's not very new and dated.
[Samsung Galaxy Nexus] Thordgar:
Memory leakage problems are in MM or in N?
[Samsung Galaxy Nexus] _yen_:
N

bye

yen
[Samsung Galaxy Nexus] bamtan2:
I had problems with both when I tested. But I might have made a mistake, or something might have changed since then!
[Samsung Galaxy Nexus] Kralle_bw:
Memory problems on my maguro only on nougat builds.
[Samsung Galaxy Nexus] edu24lal:
Try zeelog Lineage 14.1 http://zeelogkang.blogspot.com/2017/05/lineageos-141-unofficial-712-gnex-tuna.html

Best nougat rom so far, no memory problems no video crash everything working, 880 ram ( NO CMA) CMA is the problem
[Samsung Galaxy Nexus] kerpert:
I'm on 6.0.1 and would like a kernel for regulate the screen rgb colors, does something exist?
[Samsung Galaxy Nexus] Android-Andi:
Install Magisk for root and Install kernel adiutor to change RGB ;)
[Samsung Galaxy Nexus] kerpert:
Done but can't find colour adjusting, does the 6.0.1 support it?
[Samsung Galaxy Nexus] Android-Andi:
Should be there and work... MH... I can flash my gnex later and try myself and let you know
[Samsung Galaxy Nexus] _yen_:
If color control is enabled in kernel you should have /sys/class/misc/colorcontrol/multiplier in your tuna.

Just to test open a root shell (via adb or a terminal emulator) and run this command:

echo "1530000000 1625000000 2000000000" > /sys/class/misc/colorcontrol/multiplier

you should see colors changing to a more blueish ones.

BTW actually CONFIG_COLOR_CONTROL is not set on tuna_defconfig from ti omap4 kernel branch 3.0/common in UA github.

bye

yen
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=2375847]_yen_[/MENTION] CONFIG_COLOR_CONTROL is not needed
[Samsung Galaxy Nexus] kerpert:
In meanwhile, after your suggestion to install Magisk, my phone increased a lot the battery life without wipe or restore nothing.

From 1h30min of screen I'm passed to 2h55min. Today after an entire day the battery still have 38%.

I installed also the anykernel (that of Andi) even if I didn't find any new application so I didn't understand what it did.

Then I installed the Universal Kernel Manager from Magisk but also in this case I didn't find new app, for concluding I installed also the Kernel Audiutor Mod from where I set deadline in scheduler i/o.

Will try to deepen later the question of colours.

And I don't have more that strange process called miscellaneous that show an abnormal consumption.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=4931394]kerpert[/MENTION] somehow my UA 6.0 failed to root and haven't had enough time to reflash and start clean. I'll try again next week. I thought Kernel adiutor uses the omapdss to adjust RGB color, but could be i am wrong.
[Samsung Galaxy Nexus] Android-Andi:
Next 7.1 build will have October patch level and KRACK fixes
[Samsung Galaxy Nexus] PGHammer:
Thanx - additional heads-up

Nice to know - I'm doing my first pull so I can go self-build. Speaking of which....

There is now an AOSP-8.0 branch; those of you (like me) looking to go the self-build route (or if you already have), you may want to do a re-pull from git to include the new branch.

repo init -u git://github.com/Unlegacy-Android/android.git -b aosp-8.0
[Samsung Galaxy Nexus] Android-Andi:
8.0 won't help you as it's not working on any omap4 device
[Samsung Galaxy Nexus] nrichard7029:
[MENTION=6817903]PGHammer[/MENTION] I have already tried that, and it didn't work. We need to port the kernel version, which is currently 3.0, to android o.