yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] _yen_:
Well thank you again, I hope that I don't give you too much trouble... if you think that my patch may be useful please push it on gerrit.

I really don't care about having credits for it or not, it may be strange but what it cares me is to have tunas running nougat in its full glory for everyone... sometimes I feel myself so sorry for not being able to help more...

yen
[Samsung Galaxy Nexus] fromfree:
I noticed this bug with some games, but I'm not shure about what causes it :confused:

This would be very useful. Zzpianomano created a rom in which you can turn off the screen during boot time, maybe the devs would consider to port this feature into UA
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=2375847]_yen_[/MENTION] Did you intend to remove gps.omap4.so for maguro? Your patch has this:

- symlink("../../maguro/lib/hw/gps.omap4.so", "/system/vendor/lib/hw/gps.omap4.so");
+ rename("/system/vendor/maguro/lib/hw/gps.tuna.so", "/system/vendor/lib/hw/gps.tuna.so");

I'm not sure how the GPS-shims work for maguro, but the original patch does not remove gps.omap4.so, it only adds gps.tuna.so.

The current GPS-shims patch does indeed break GPS for toro, thanks for catching this.

Edit: Okay, looking at the code, the shim points to /vendor/maguro/lib/hw/gps.omap4.so. So your patch is correct.

Edit2: The current GPS-shims setup uses gps.omap4.so in the /vendor/maguro folder, while all other vendor files are moved to the location they would have been in before unified builds were implemented. This is odd and feels wrong to me. Plus, if the initial variant setup fails and the fallback tunasetup script is run, that moves the maguro files rather than symlinking them, so it will break things yet again. Let me see if I can straighten this out...

Edit #3: The GPS-Shims work fine on toro it the path is corrected. I pushed a patch doing that.
[Samsung Galaxy Nexus] _yen_:
thank you, I see it... let's me test on maguro, last time I play with the shim it doesn't play so nicely for me when pointing to a symlink

EDIT: OK works fine, thanks...

bye

yen
[Samsung Galaxy Nexus] phaleg:
MM runs smooth on maguro and I don't see a real advantage to switch to N at the moment...

Did anybody have the chance to compare both of them recently?
[Samsung Galaxy Nexus] entux:
anyone else having trouble with the 27.03. 7.1.1 build not being able to find the sim card?
[Samsung Galaxy Nexus] _yen_:
It's a know bug due to some SElinux denials, it will be fixed in next build.

If you don't want to wait use the tunasefix workaround that is explained in this post:

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

bye

yen
[Samsung Galaxy Nexus] ar3s3ru:
Hello guys, my OPO broke so I have to use my maguro again.

I saw that the 7.1.1 build on maguro gets stuck on boot because of non-permissive SELinux option in the kernel.

Since I don't want to deal with preparing a ROM build environment, can I ask if the MM build suffers from this issue, as well?

Thanks!
[Samsung Galaxy Nexus] miomaguro:
MM works perfectly. Go for it.
[Samsung Galaxy Nexus] bwalter:
I tried MM a few days ago, and it seemed to get stuck on the boot logo as well.
[Samsung Galaxy Nexus] miomaguro:
I'm with the build 20170320 and no problems whatsoever. I would reinstall it after a complete wipe. My procedure is: build, opengapps pico, xposed-module, supersu. Until today, everything is working properly (average RAM is 750MB).
[Samsung Galaxy Nexus] bwalter:
I tried a complete wipe followed by ua_tuna-6.0.1-20170327.zip, and opengapps (nano I think). No xposed or supersu. I used TWRP 3.1.0.0.

I'm really more interested in 7.1 anyhow. Just waiting for a new build with the SELinux & GPS fixes (which have already been merged.)
[Samsung Galaxy Nexus] miomaguro:
I would give it another try with opengapps pico (nano is known to have problems with the system partition and MM on GNex). However, about 7, there are several comments (some pages above) about successful patches and fixes... Good luck!
[Samsung Galaxy Nexus] bwalter:
I had resized my system partition to 1GB so I was hoping micro vs nano wouldn't be an issue.

I realize there are patches/fixes to boot 7, but I think the GPS fix needs to be in the build. Everything is merged/committed, I just don't know when it will be built. Anyhow, I'm not using the phone these days (got it back from my mom after handing down my Nexus 5) but thought I'd play with it so I'll just wait until there's a build.
[Samsung Galaxy Nexus] entux:
thanks. i've followed that guide and got the rom to boot up but it seems the problem lies even deeper than that. my provider do not really show up in the list any more... well of i go studying alogcat logs. :)
[Samsung Galaxy Nexus] _yen_:
I

A little more updated tunasefix can be found here:

https://xdaforums.com/showthread.php?p=71398043#post71398043

may be it can solve you problem. I've never had that kind of problem with this ROM but I've one of the main providers in my country.

As usual logcat is welcome.

Edit: have you broken voice and data or data only? If it's only data try to insert manually APN for your provider, google has a long story not being able to keep these things up to date.

bye

yen
[Samsung Galaxy Nexus] _yen_:
Hello [MENTION=2633638]Ziyan[/MENTION],

7.1.2 changes have broken NFC build in tuna too, but this commit fix it: https://gerrit.unlegacy-android.org/#/c/1856/

can you cherry-pick it in device/tuna please?

Thanks

yen
[Samsung Galaxy Nexus] entux:
Thanks!

Is it possible that F-Droid needs an selinux fix as well? It can't download anything on 7.1.1 and I can't seem to get anything useful from LogCat.
[Samsung Galaxy Nexus] _yen_:
No, I'm using F-Droid (currently 0.102.2) myself on UA 7.1 and it needs only the storage permission granted.

bye

yen
[Samsung Galaxy Nexus] entux:
Ok... I had to wipe f-droid from my installation (had it reinstalled via TitaniumBackup) and download it via PHONE (because using desktop+MTP produced a corrupt package?) and now it seems to work.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=2633638]Ziyan[/MENTION] I see you guys have a big new 7.1 build up. The forum goers are ready to start public testing when you give the thumbs-up! :)
[Samsung Galaxy Nexus] Ziyan:
Well, it has the GPS and SELinux fixes, as well as it's 7.1.2, it should be fine, but I couldn't test it yet :)
[Samsung Galaxy Nexus] _yen_:
as a totally unofficial tester I can just say that UA 7.1.2 build works :good:

bye

yen
[Samsung Galaxy Nexus] bamtan2:
This is a known problem but I will repeat it: twrp-3.0.2-0-maguro.img results in this failure:

So I used twrp-3.1.0-0-maguro.img instead and it succeeded.

To summarize, I flashed:

Recovery image: twrp-3.1.0-0-maguro.img

System resize script: lanchon-repit-20170115-system=1G-cache=62M+wipe-data=same-maguro.zip

ROM: ua_tuna-7.1.2-20170406045232.zip

Gapps: open_gapps-arm-7.1-pico-20170405.zip

Superuser: SR3-SuperSU-v2.79-SR3-20170114223742.zip

Rebooting took 5-10 minutes, I wish I measured.

Bug: During startup setup wizard, clicking options like "VISION SETTINGS" or "Bring your data from your google account" causes "Settings has stopped" error. Workaround: I went into TWRP and deleted '/system/priv-app/Setup-Wizard' !

Bug: Dragging down from the top and disabling cellular data caused the shade to be stuck on "Cellular data" every time it's dragged down.

Feature: It seems that Android 7 has lost the ability to choose wifi bands. This could be a slight problem for a device with broken 5ghz, but for now it seems to be working. It may have detected that no data could be transferred at 5ghz and switched to 2.4ghz on its own.

Bug: Downloading a file with Browser makes it crash. Could there still be permission problems? When I try the same thing with Chrome, it says "Chrome needs storage access to download files. UPDATE PERMISSIONS" and then clicking that brings up the normal system prompt to allow access to storage, so the download works.

Bug: Home button and multitask buttons vibrate but don't function.

Feature: If you tell me how to enable zRAM I will test it!

Feature: I don't see any color control. Yellow screen life!

Feature: Printing with HP plugin works!

Feature: Camera and video both work well and operate quickly after the initial startup delay!

Bug: Maybe I'm missing something, but I don't see Google syncing anything but Chrome for me right now. No Contacts sync. Maybe that's normal with AOSP contacts, and Google Contacts must be installed from the store?

Bug: In the default apps section, there is no default home app or browser app selected, but there is a default phone app, etc.

I didn't know we still needed to do this. For me, Google Play services already has access to everything by default. Do we still need to give the keyboard access to contacts and storage, the browser access to camera, etc etc? Is there a script to do it all automatically?

That's all I've got for now. The performance is super snappy and the RAM levels look right, so no complaints there! Great work team!!! :cool:
[Samsung Galaxy Nexus] fadiesis:
thank you for your notes. what about the call in volume adjustment? Does it work?
[Samsung Galaxy Nexus] _yen_:
hello [MENTION=4545566]bamtan2[/MENTION] I just do a (really speedy) test installing 7.1.2 from scratch:

- I can flash 7.1.2 build without any error with twrp 3.0.2 but months ago twrp 3.0.2 has given me problems restoring nandroid so I advice all to update to 3.1.0

- bug 1: confirming that gapps wizard crash (may be not updated to 7.1.2 yet?) additional workaround: flash rom, reboot and setup, boot on recovery and flash gapps, reboot and set google account manually

- bug 2: haven't it, shade doesn't remain stuck

- bug 3: EDIT: stock browser need storage permission manually granted to be able to download files

- bug 4: buttons works fine here

- bug 5: untested, I don't use any google services

this kernel was maintained as stock as possible so color control was not enabled (even if it can work flawlessly), Voronk has it enabled but nougat branch has been never released...

EDIT: ZRam not enabled too..

I'll test more later...

bye

yen
[Samsung Galaxy Nexus] Android-Andi:
Hey together!

7.1.2 needs proper Gapps, 7.1.1 Gapps don't work fine here.

I compiled 2 kernel to test for you guys, we like to jump back to our stable kernel branch on 7.1 as soon as possible (atm we have a seperate 7.1 kernel branch).

Attached kernel should work on any rom for tuna, only KitKat has a own defconfig and is seperated.

Compiled with GCC 4.7.

Source: https://github.com/Unlegacy-Android/android_kernel_samsung_tuna/commits/staging

Please test and let us know if you face any issues on M or below while using this kernel.
[Samsung Galaxy Nexus] guest4711:
Thank you for this fine kernel. I'll test it on Slim 6.0. 1. Bootet fine, GPS and Wifi are working. :good:

Dmesg-log attached.
[Samsung Galaxy Nexus] entux:
I can try it out. What should I expect?
[Samsung Galaxy Nexus] Android-Andi:
I hope it works fine without issues :)

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] bamtan2:
Thank you for this advice! I searched to find 7.1.2 gapps and could only find this, but it worked: https://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

[MENTION=2375847]_yen_[/MENTION] [MENTION=2633638]Ziyan[/MENTION] I have reinstalled everything using this gapps-712-base-20170403-1-signed.zip package. To work around the broken setup wizard, I used a feature of this Gapps package to remove it automatically, by placing an empty file named ".removesetupwizard" in /sdcard/ to give their script a hint. Now the navbar, notification shade, and Contacts/Google app syncing all work fine. I have NOT done any of the "grant every permission to every Google application" mentioned on the front page, except for the Browser bug workaround previously mentioned by yen.

I guess it's possible that the incompatible 7.1 gapps could break the whole system the way I originally experienced?

Bug: In-call volume adjustment is broken.. Can confirm!

Bug: I can crash the video/camera system. Once when I played a video in chrome and turned the screen sideways, it skipped and stopped. Later, after rebooting, I crashed it when I paused a youtube video and switched to other apps for a while, I came back to youtube and it was frozen. Both times all video and camera usage stopped working.

I have noticed that sometimes, when the system is thinking very hard (maybe when a new screen is trying to load), the screen will go black. Not sure if this is a bug or a symptom of something.

Feature: Wake screen with volume buttons. This feature was critical in the past when the power button would bug in software and not wake the screen until after a reboot. I don't know if the power button bug has been fixed. I do still believe that the volume button should wake regardless, to reduce the mechanical load on our old device's power button, extending its life.

I tested the GPS and it did not get a satellite fix, but it was cloudy outside, so unfortunately I cannot confirm what the cause of the problem is. Might just be weather! :)
[Samsung Galaxy Nexus] Android-Andi:
I always use gapps by deltadroid, never had issues with them on tab2.

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] bamtan2:
OH by the way, I flashed the kernel you linked. I think you implied that it's the same as what is in the 7.1.2 build already, but I switched anyway because you asked for testing =)
[Samsung Galaxy Nexus] _yen_:
I usually use satstat from f-droid to test gps, actually (7.1.2) first sat appears in few seconds but it may take up to five minutes to get position fixed (gps only), maguro has never been good with gps...

Flashed yesterday, nothing to complain on 7.1.2 until now, thanks.

bye

yen
[Samsung Galaxy Nexus] entux:
[MENTION=5153662]Android-Andi[/MENTION]: Could you confirm this? I am already on 7.1.2.

All but GPS working well so far. Can't seem to get a sat at all.
[Samsung Galaxy Nexus] Android-Andi:
The kernel is almost the same, there's a small difference I'll look at once we know it works fine from 4.4 up to 7.1.2.

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] _yen_:
GPS works here on a stock UA 7.1.2 build (and [MENTION=5153662]Android-Andi[/MENTION] test kernel), tested using both satstat and Osmand

bye

yen
[Samsung Galaxy Nexus] musical_chairs:
Working fine on KitKat.
[Samsung Galaxy Nexus] bamtan2:
After using it full time for another day, I can say that while there are small/minor/cosmetic bugs (temporary black screens, chrome "grid" while loading, holes on recents screen), I believe the only show-stopper bugs I've had are the setup wizard (for which there is a workaround) and the video/camera crashing frequently. [MENTION=2633638]Ziyan[/MENTION] the video crashing feels the same as it did years ago, where even with much "free" RAM (all cached now actually), simply rotating the screen or switching apps can kill the video. Maybe we need more true "free" RAM, or maybe there is an old fix you already know about.
[Samsung Galaxy Nexus] PGHammer:
Oddly enough, I had the issues with the setup wizard; but a deeper wipe fixed them on a clean install (instead of a straight factory reset, I wiped everything except the data partition) - this is with both Unlegacy 7.1.2 and DU 7.1.2 based on Unlegacy - I'm expecting this to carry over to PureNexus 7.1.2 as well; apparently, there was some crud that the factory reset does NOT get that causes the setup wizard to act cuckoo.

Also, for the first time in ANY unpatched build, Location History works properly OOTB. (I never had the camera bug.)
[Samsung Galaxy Nexus] bamtan2:
Bug: Both VLC and MX Player setting "Play videos in background" doesn't show any video. It worked on CM 12.1. Note VLC also doesn't show any video in "multiwindow" mode (holding the task switch navbar button), but MX Player does work with this.

Bug: Developer Settings -> "Force activities to be resizable" doesn't seem to do anything. I think it's supposed to let you resize the "multiwindow" mode arbitrarily.
[Samsung Galaxy Nexus] _yen_:
may be a missing lib? uhm, may be not on n... idk

I got some of this at boot when I activate this option:

04-08 08:55:42.288 461 461 W PackageManager: Package com.moez.QKSMS desires unavailable shared library com.sec.android.app.multiwindow; ignoring!

bye

yen
[Samsung Galaxy Nexus] bamtan2:
Bug: I've had "Browser crash" error popups periodically while signing into some apps. I haven't isolated this yet, but it happened with multiple different apps. I haven't noticed any problems, just the popup. Maybe Chrome webview would change this. I could experiment...
[Samsung Galaxy Nexus] Younex:
Big things happening here, unfortunately the only hint is the thread title, #1 and #2 posts are not updated... ?
[Samsung Galaxy Nexus] _yen_:
Just found this thread that may be related to this kind of bug: https://xdaforums.com/android/software-hacking/fix-fix-crashing-setup-wizard-t3586177

As you have tested some options into the developer menu, have you perhaps enabled multiprocess webview? I have tested this option some times ago and it crashes aosp webview in a bunch of apps.

bye

yen
[Samsung Galaxy Nexus] bamtan2:
I did not change that setting. But I did change "webview implementation" to "chrome webview"...
[Samsung Galaxy Nexus] PGHammer:
Hola, Yen!

I've been using TWRP 3.1.0.0 since it went live; therefore I kinda doubt it was the recovery; the issue is only with the standard wipe/reset - dirty flashes from a previous (7.1.1) version are fine (either DU_7.1.1->7.1.2 or UA 7.1.1->7.1.2); despite the common code base, I would never crossgrade-flash - that's just asking for trouble. No ZRAM? Wasn't it enabled in 7.1.1? (I know it was in 7.1.0 - and it really woke things up compared to MM.)

Curiousity Q: Are you the same Yen that frequents MyDigitalLife and Neowin.net?
[Samsung Galaxy Nexus] _yen_:
Well I've flashed (mainly dirty to be honest) dozens and dozens of UA nougat builds and others flashable zip on top of it and I don't remember a twrp error that doesn't come from a bad zip or a failed assert condition, it should he useful someone post recovery logs when having this to see the origin of the problem. Official TWRP 3.0.2 build has given me a tons of troubles saving and restoring nougat nandroids towards December/January (it is pretending to backup/restore some thousands of files more that i have) for which I have to format my maguro from scratch several times. Last 3.0.2 test build from Ziyan and twrp 3.0.3 onwards doesn't give me this kind of problem.

It seems to remember that after CMA memory management was merged, ZRAM was removed, surely it was from cm13 as i find the commits. Actually kernel config has CONFIG_ZRAM and CONFIG_SWAP not set and i'm not able to enable zram using some of my (old) init script... but I'm not a dev and I can be wrong.

Last one, no I'm not that guy...

bye

yen
[Samsung Galaxy Nexus] bamtan2:
I think [MENTION=2633638]Ziyan[/MENTION] removed ZRAM because it crashed ducati.

But now that ducati is crashing again, I would like to test ZRAM again too =) =)
[Samsung Galaxy Nexus] bamtan2:
Bug: YouTube app doesn't keep the display on. It will time out as if nothing is playing.

Bug: YouTube app closes (crashes?) when the display turns off. This includes just pressing the power button, so it should be easy to verify by playing a video and pressing the power button once.

Edit: This is harder to reproduce after a reset than I thought. I can reasonably quickly crash YouTube by turning the screen off or sending it to the background and multitasking, but it works normally after closing and opening it again. Breaking things so badly that it crashes every screen-off, no matter what, is harder.
[Samsung Galaxy Nexus] gabrielex:
So I've finally found out why so many games and apps (especially Nintendo ones) were resulting incompatible on not working with my Maguro,

apparently it's all about Safety Net and more specifically basic integrity and CTS profile match fail.

I've found out this using Root Checker Pro.

Is there a way to solve this?

I'm using ua_tuna-6.0.1-20170327.
[Samsung Galaxy Nexus] bamtan2:
I don't know if this will help you, but some people use "magisk" to hide root: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Samsung Galaxy Nexus] gabrielex:
Thing is this time I haven't rooted the phone.

Used to root with CM, but didn't with this ROM.
[Samsung Galaxy Nexus] _yen_:
may be safetynet is checking bootloader?

https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
[Samsung Galaxy Nexus] osm0sis:
Doesn't happen on older devices.
[Samsung Galaxy Nexus] gabrielex:
It could be, has any of you tried if with this ROM you could pass safety net?

In the case we can't it means we need a modified kernel with that flag disabled.
[Samsung Galaxy Nexus] osm0sis:
No. You're barking up the wrong tree. SafetyNet doesn't do it based on bootloader state on hammerhead, so it definitely doesn't do it on tuna.
[Samsung Galaxy Nexus] gabrielex:
So what do you think makes it fail, specifically the CTS profile match and basic integrity tests and not the whole Safety net test?

Did you try on your Galaxy Nexus to see if it passes?
[Samsung Galaxy Nexus] osm0sis:
Bootloader check is only on devices that launched with dmverity. Same goes for untouched system image check based on write count.

Are you rooted? Have you tried MagiskHide? It apparently works for now.

CM/LOS hammerhead kernel failed out of the box on an unrooted ROM until recently when they added a commit Google was apparently checking on: https://xdaforums.com/showpost.php?p=71319479&postcount=1375
[Samsung Galaxy Nexus] gabrielex:
Not rooted as I previously said, that's why I didn't use Magisk.

Which ROM version and device are you using? When you say it apparently works for now are you talking about your GNEX?

My system image write count don't know what is, but for sure is quite high since I've been flashing so many ROMs ;)
[Samsung Galaxy Nexus] amine a.b.i:
how can i enable the google assistant on the maguro running 7.1 nougat rom ???
[Samsung Galaxy Nexus] osm0sis:
I haven't tried with maguro in a while. Unrooted should pass, ROM devs will have to look into​ it.
[Samsung Galaxy Nexus] Android-Andi:
"Userdebug" builds have adb root, maybe that's the reason?

I am not sure if all our supported devices run well on "user" builds.

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] osm0sis:
hammerhead LineageOS is userdebug and passes out-of-the-box, so it's not that. adb root might be it.
[Samsung Galaxy Nexus] fromfree:
The nougat version (10 april build) seems to have serious RAM issues, after 10-15 hours of use the memory gets saturated and the phone must be restarted. The cache usage indicator even goes overflow. The catlog reports a lot of memtrack issues and battery API or other energy errors. If it could be useful I will attach a full catlog here, let me know.
[Samsung Galaxy Nexus] entux:
I can confirm this (with an even earlier build. It's going up to 99% (7.5MB free) usage. Even directly after restart memory used is at 92% (82MB free).
[Samsung Galaxy Nexus] smart-t78:
if you are rooted, add this line to your build.prop:

ro.opa.eligible_device=true
[Samsung Galaxy Nexus] entux:
Strangely enough memory consumption went down to 66% after a while. System is using much less now than it did 3h ago???
[Samsung Galaxy Nexus] osm0sis:
Probably background optimization.
[Samsung Galaxy Nexus] guest4711:
A good kernel will use almost all ram (at least for caching) but assign it to processes when needed. Unused ram means wasting ressources...