yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] oldman_58:
Trying to sync and build this morning, I am getting the following error:

Syncing work tree: 57% (278/486) error: Your local changes to the following files would be overwritten by checkout:

services/core/java/com/android/server/pm/PackageManagerService.java

Please, commit your changes or stash them before you can switch branches.

Aborting

Syncing work tree: 100% (486/486), done.

error: frameworks/base/: platform/frameworks/base checkout 04b1916d86526465851e450f5e700065bea48623

I made no local changes
[Nexus 7 Android Development] mausbock:
I installed BetterBatteryStats and now the device is charging. Tomorrow I will analyze the kernel and​ partial wake locks.
[Nexus 7 Android Development] AndDiSa:
[MENTION=2742144]oldman_58[/MENTION] you applied the patches from the manifest directory, didn't you? This is causing the problem with synchronization. You can reset those changes, sync and re-apply them. In that case eerything should work fine, e.g.

cd frameworks/base
git reset --hard
cd ../..
repo sync frameworks/base
cd frameworks/base
patch -p 1 < ../../.repo/manifests/frameworks_base.patch
...

Most likely this issue will occur for other directories where you have applied the patches, too.
[Nexus 7 Android Development] androiduser0815:
Hello AndDiSa,

thank you very much for your work. This rom works great and smooth on my Nexus 7 (grouper). Smoother than the original rom (Android 5.1.1).

I found three inconsistencies:

1. App icons after rotation

Before rotation: 6 lines and 5 columns – after rotation: 5 lines and 4 columns.

2. Gallery-App

No information in gallery app under “settings“ (dt. “Einstellungen”), just a black screen.

3. Android-Keyboard (AOSP)

I can´t swipe words.

Unfortunately no Nexus 7 camera app working with this rom.

Deutsche Version

Hallo AndDiSa,

vielen Dank für deine Arbeit mit der rom! Sie läuft sehr stabil und flüssig auf meinem Nexus 7 (grouper). Ich würde sogar sagen, dass sie viel flüssiger läuft als die ursprüngliche rom (Android 5.1.1).

Mir sind bei der rom drei Ungereimtheiten aufgefallen:

1. Anordnung der Icons nach dem Drehen des Geräts

Das Nexus auf Auto-Rotation eingestellt. Wenn ich es boote, werden die Apps in 6 Zeilen und 5 Spalten angezeigt. Nachdem das Nexus im Querformat war und es dann wieder ins Hochformat gestellt wird, werden die Apps nur noch 5 Zeilen und 4 Spalten angezeigt. Die Anzeigebereich der Apps erscheint auch kleiner.

2. Gallerie-App

Unter „Einstellungen“ in der Gallery-App wird nur eine schwarze Seite angezeigt. Ich weiß nicht, ob dies normal ist.

3. Android-Tastatur (AOSP)

Ich kann mittels Wischen keine Wörter schreiben.

Ansonsten funktioniert leider keine Kamera-App für das Nexus 7 (im Play Store werden welche angeboten, welche die Frontkamera freischalten).
[Nexus 7 Android Development] rauhut:
I doubt that it is branch related but I experience the following since this and previous build: when updating both ROM and GAPPS (use pico opengapps, rest like in first post) I get constantly crashes of Google apps like Gmail or Google+ immediately when launched. Authorizations seem to be somewhat "forgotten" and reset to none. Granting access again via settings does not help much, some issues can be fixed by uninstalling and re-installing the app. Any idea what is causing it and how it can be avoided in update process?

BTW: is device encryption working reliably on the latest build? If yes, which file system do you use?

Thanks.
[Nexus 7 Android Development] AndDiSa:
[MENTION=7655286]igor1st[/MENTION] I've just uploaded the new tilapia version (20170507), it's linked in the OP now.
[Nexus 7 Android Development] igor1st:
Thanks! Started testing...
[Nexus 7 Android Development] Ahkah:
In "APPS" screen (entered via the ":::" symbol):

I can confirm this (small) bug:

Before rotation: 7 x 4 icons

After rotation 7 x 3 icons (resp. 4 x 5 in portrait mode)

Gallery

My Gallery app is named Galerie, not Gallerie (-> wikipedia), but I can confirm the empty "settings" screen.

Camera

The recommended app "A Better Camera" seems to work. By the way: There is only one camera in this device. It's located on the same side as the display.

However the new OS version runs fine, and the update process from the March version (both OS and recommended gapps) worked flawlessly. Great work!
[Nexus 7 Android Development] igor1st:
[MENTION=2188693]AndDiSa[/MENTION]

There are already some results. Radio continues to die and can't recover itself in sleep. But after connecting tablet to USB it is restored and continues to work until next death. Only turning the screen on looks insufficient for me - I waited several minutes on second case and got it restored only after connecting cable (toggling airplane mode doesn't help). Proper fix to this problem is still needed.
[Nexus 7 Android Development] cloud79:
tried it, mario run doesn´t work with latest build (grouper)

but impressive how much more performance this rom gives comparing to stock
[Nexus 7 Android Development] Codster314:
How bought the Night Light feature? Available in the 7.1.x? This isn't any fancy glitter or anything, this is just the "Reduce Blue Light Filter" (makes screen yellow'ish). Helps reduce eye strain at night and promotes better sleep schedules. I'm not too sure on resources it takes, but I do not imagine it uses a lot, as it's just a reduction of blue light during dusk->dawn.

Most modern mobile devices include this feature now, and is included in iOS's "Night Shift" (iOS 9.3), Windows "Night Light" (W10 CU), and in Andriod "Night Light" (7.1.x). Since all 3 major mobile OS's adopted this feature, I assume it has some scientific backing.

Be nice to see it included in this custom ROM. It's included in all of the other custom ROMs I use (SAOSP-N for Nexus 4, PureNexus for RedmiNote3). And is a generic Android 7.1.x feature.

Edit: AmbientDisplay doesn't really make sense on non-AMOLED screens I think. So no reason to add that. It'll just be a battery drain on our IPS LCD. Since it's main feature is the selective lighting on only portions of the screen to save battery.

But I do see it in ur April Build (just turns screen on when notifications come in). So yea that is already included in this. Or at least there is an option "Ambient Lighting" under Display.
[Nexus 7 Android Development] ozkrkstro:
bueno amigos no se si para reportar algo es asi pero la mia es una tilapia y los datos moviles no me van bien se desconectan a cada poco y el laucher cuando la giro se ase pequeño de ai todo lo demas funcionando todo a la perfeccion gracias son lo mejor
[Nexus 7 Android Development] seatibiza:
What?

Gesendet von meinem XT1572 mit Tapatalk
[Nexus 7 Android Development] iamelton:
you need to provide a copy of your msg in english.. its a forum rule..
[Nexus 7 Android Development] AndDiSa:
Night Light currently isn't a standard feature of AOSP, when it's integrated, it will be also included into the ROM.

The AmbientDisplay option is a left over from [MENTION=6754437]millosr[/MENTION] nASOP repo which I am using to build for the Tilapia device. As I do not have such a device available I do need feedback from the users to iron out such inconvenineces / issues. Thanks for that.
[Nexus 7 Android Development] Ahkah:
In my humble opinion the warmer display colours are mostly a temporary fashion and some "want to have what others have" feature. As far as I know the effect on people's wellbeing is unproven or just a placebo. Some people in fact sleep better with the knowledge, that their device has all security corrections, than with a yellowish display.
[Nexus 7 Android Development] mausbock:
[MENTION=7655286]igor1st[/MENTION] and [MENTION=2188693]AndDiSa[/MENTION]

I also tried the latest tilapia build and have no issues with mobile data until now. I will test it next days more intensive and report if issues occur.

(I also have no more wake locks like I reported before.)
[Nexus 7 Android Development] paasoares:
[MENTION=2188693]AndDiSa[/MENTION]

on this version for 2 days now and, although a few small issues, this is by far the best version that my Tilapia ever had :

- smooth

- fast

- not a single FC

- no battery drain

Great Job !!!

Thanks
[Nexus 7 Android Development] Codster314:
I think it is a standard feature in AOSP... and it's already in there since AOSP version 7.1.1 - You just have to configure the flags to enable it in: /android/frameworks/base/core/res/res/values/config.xml

AOSP URL (with directions on enabling it): https://source.android.com/devices/tech/display/night-light
[Nexus 7 Android Development] AndDiSa:
[MENTION=7056085]Codster314[/MENTION] we would need HWC2 support for the tegra3 to enable Night Light but we only have hwcomposer.tegra.so as a binary that, for my knowledge, doesn't support setColorTransform
[Nexus 7 Android Development] shaggyskunk:
Just download an app from the store that does essentially the same thing ie: CF.Lumen and there's a number of others.
[Nexus 7 Android Development] mistermagic87:
[MENTION=4793590]beppemila[/MENTION] You may want to try the steps below it fixed the Google play services issue for me, hopefully you haven't already since I didn't look through all your posts, hope this helps. My apologies if you have tried it.

[MENTION=5128593]dark0shark[/MENTION] Thanks for the suggestion and for posting this here. I was also having the google services force close issue and this version of Open GApps resolved it for me on the latest 20170505 build. Here's to hoping this helps someone else who runs into the issue.

[MENTION=2188693]AndDiSa[/MENTION] Thank you so much for the releases this brought new life back into my old Grouper, haven't used it enough to see any bugs but I'll report back with what I find.
[Nexus 7 Android Development] Codster314:
Ah, maybe that's the reason I do not see it in many Nexus 7 ROMs. Okay. :) I do see a similar option in the Lineage Grouper ROM (Live Display). Does the same thing and does change the screen colour, but the options are a bit different than the AOSP Night Light. Maybe Lineages version of it I guess.

I can't use the Lineage one, I find this ROM more smooth than the Lineage version. And the Lineage ROM fails SafetyNet (Basic and CTS). While this rom passes both, allowing people to play FE Heros and other SafetyNet games.

Yea I like ChainFires's Lumen, it's very nice, but for it to fully work u need it rooted (it does work unrooted, but things like the keyboard and such aren't affected). I would like to not root my device, since I like to play FE Heros and other SafetyNet Games. But the unrooted version is fine for now I guess.
[Nexus 7 Android Development] namerke:
Have you ever heard about magisk root and it's root hiding ability? Google it if you didn't. I'm using the same and it let me play Mario and use my banking app, and both of those check for safetynet. Also, it enables me to use naptime and servicely to gain some extra idle juice :)
[Nexus 7 Android Development] mafarric0:
Hi [MENTION=2188693]AndDiSa[/MENTION]. I came here to give my feedback, but basically it's exactly what [MENTION=342699]paasoares[/MENTION] already wrote.

Thanks a lot a continue the great work. :good:
[Nexus 7 Android Development] AndDiSa:
[MENTION=4573282]namerke[/MENTION] I am using Magisk on my phone and it works really great. Probably I should update the OP of this thread, too, to suggest to use Magisk instead of SuperSU ... :-0
[Nexus 7 Android Development] mistermagic87:
[MENTION=2188693]AndDiSa[/MENTION] with the new PerformanceControl application added what settings do you use or suggest if any? Will this work once rooted or is this only if I use a different kernel for overclocking?
[Nexus 7 Android Development] Ahkah:
I tested the PerformanceControl app. It just crashes. It might be interesting that F-Droid constantly offers to replace it with a newer version (2.1.6 -> 2.2.5), but, if I agree, fails due to "signed with a different key".. However, F-Droid's description of this app states that it needs root access. Hence it's plausible that it does not work, but in any case it should not crash but complain about missing access rights or whatever.

---------- Post added at 15:55 ---------- Previous post was at 15:43 ----------

My n7 specimen tends to restart instead of shutdown. Often I need two or three or more attempts to shut it down. Could this have anything to do with the OS, or is it a hardware failure?
[Nexus 7 Android Development] n3kf:
Me also. Although the safety net test does not pass. Does it for you?
[Nexus 7 Android Development] paasoares:
What should be the procedure to uninstall SuperSU and replace it by Magisk ?
[Nexus 7 Android Development] sbasstik:
According to official magisk thread https://xdaforums.com/showthread.php?t=3473445 You only need to Install magisk Manager from Google PlayStore if You have official systemless supersu
[Nexus 7 Android Development] mistermagic87:
I have no issues with the PerformanceControl app crashing after granting it root. Is it not supposed to work?
[Nexus 7 Android Development] AndDiSa:
[MENTION=4974293]mistermagic87[/MENTION] people are complaining that the app i not working when you are *not* rooted ...

As you are using the app to change system / kernel settings, I supposed it's obvious that you need to be rooted to use it, but I was wrong.
[Nexus 7 Android Development] AndDiSa:
[MENTION=342699]paasoares[/MENTION] I need to test by myself, normally it should work in the following way:

- boot into recovery

- flash rom

- reboot into recovery

- flash gapps

- reboot into recovery

- flash (magisk

- boot

Because Magisks has built-in root, there should be no need to root using SuperSU, but as I said I'll need to test whether it's working in this way.
[Nexus 7 Android Development] paasoares:
I followed those steps and it seems to work.

- Device is rooted

- when i clicked magisk icon was redirect to google play to update, which i did

- safety net check failed : CTS profile mismatch

- dont have any wallpaper (strange)
[Nexus 7 Android Development] AndDiSa:
[MENTION=342699]paasoares[/MENTION] regarding the CTS: probably we need to change the fingerprint to "google/nakasi/grouper:5.1/LMY47D/1743759:user/release-keys"

Not sure whether it's sufficient or if some other changes are needed.
[Nexus 7 Android Development] HerrT:
Did you turn on the "Magisk Hide" switch in the Magisk Manager app under Settings?
[Nexus 7 Android Development] paasoares:
With "Magisk Hide" setting turned on, it stays on "checking SafetyNet Status..." forever
[Nexus 7 Android Development] AndDiSa:
[MENTION=342699]paasoares[/MENTION] yesterday I did some additional test regarding Magisk and CTS compatibility, unfortunately no success to pass the Safety Net check, always CTS failure even with the changed fingerprint. If anybody has a hint hint what to do to get it passing the check. I don't think it has to do with root, as Magisk installed on my phone let it pass the test. I suppose there is some other check which is failing ...
[Nexus 7 Android Development] n3kf:
Maybe if we get a log and put it in the Magisk forum they could help determine what change is needed?
[Nexus 7 Android Development] evlo:
Most likely not related to your ROM, but maybe you can help?

For some reason if my router is set to protected management frames capable - nexus 7 can't connect.

BTW it was kinda fun to debug as i finally learned some ADB stuff to do it, yay!
[Nexus 7 Android Development] AndDiSa:
[MENTION=1261291]evlo[/MENTION] you are not alone, seems to be an issue with Android generallye.g. Nexus 6P. Sorry, but I have no clue how to fix that.
[Nexus 7 Android Development] AndDiSa:
Regarding Magisk / SafetyNet: I did some further tests and the result so far is:

- having flashed the ROM only: SafetyNet is green for basic and CTS (even with ro.debuggable=1)

- having flashed Magisk on top: SafetyNet is red for basic and CTS

- having flashed SuperSU: SafetyNet is red for basic and CTS

I am still wondering why my phone is still SafetyNet compatible, even with Magisk installed ...
[Nexus 7 Android Development] n3kf:
Well the Magisk folks say follow this:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

If nothing works, then try post logs to the following Magisk thread (would probably be good to turn verbose logging on in Magisk):

http://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page1341

I'll play with it later today, unless mother's day here in US keeps me busy!
[Nexus 7 Android Development] AndDiSa:
[MENTION=6824216]n3kf[/MENTION] I've read on github that Magisk hide currently has some issues, probably it's related to that. I'll continue to do some test and will keep you updated. At least the ROM without SuperSU / Magisk is passing SafetyNet, that's fine to see. All other is nice to have ... ;)
[Nexus 7 Android Development] n3kf:
Thanks for all your work. If the ROM works fine unrooted, definitely a Magisk isuue. Good thinking trying that!!!
[Nexus 7 Android Development] miab:
all apps will not open

Sorry for the possibly silly question but I followed the install instructions except for the factory reset and have 7.1.2 on the tablet. I started with an unrooted 5.1.1 unit. I tried this rom because the tablet was so slow and unusable. Now all apps will start to open once chosen but will either close or it will say '--app--' has stopped. I don't know why I didn't factory reset but I goofed. I am good at following instructions usually. 'Google play services" issue message keeps coming up as well.

What do I do now. Start over ? How?

UPDATE:

I wiped all data in Twrp recovery except internal data and then reinstalled the ROM and gapps. everything looks good but again apps close or do not respond once trying to open. When I try to sign in to google it says 'couldn't sign in , problem communicationg with servers, try again later.' Also google play services always comes up with a message that it has stopped. :(

thanks in advance.
[Nexus 7 Android Development] adstraylight:
Make sure Play Services has all its permissions​

Settings - Apps - Goolgle Play Services - Permissions

In fact go through all the apps to check their permissions, including system apps which are shown via the three dot overflow menu on the apps screen.

Reboot.
[Nexus 7 Android Development] miab:
Thank you for your reply. Alot of the permissions are off. Do you suggest I allow all? Btw I did not install superuser v2.79sr3 . Is this necessary and could this be why?
[Nexus 7 Android Development] adstraylight:
Yes turn them all on.

Most apps will ask for permissions as they need them, but I find this a bit of a pain, and it's much simpler to allow them all, it comes down to how much you trust the source of the individual app. I think in this instance we can trust Google to not be evil ?....

No I don't think SuperSU has anything to do with it, I think it's just an artifact of either the gapps package you installed, or perhaps your installation procedure. Either way, once it's fixed you should be fine.

SuperSU is only needed to run 3rd party root apps for things such as kernel tweaking, and giving some file managers access to the /system partition. Anything signed by Google does not need su to run.
[Nexus 7 Android Development] BOBvD:
Same here. Rooted Tilapia with latest build (20170507). PerformanceControl App working fine, but F-Droid offers update which is not intallable.

Besides that no issues. 3G ist working fine since latest build. Best Rom ever for Nexus 7, thank you so much!
[Nexus 7 Android Development] gouchouya:
hi AndDiSa

thx for your wonderful effort

and

does we have chance to got Fuchsia OS by your hand >_^
[Nexus 7 Android Development] frov:
FYI: flashing DeltaGapps failed

I tried this ROM and I normally use DeltaGapps found here:

https://xdaforums.com/android/softw...s-lp-20150107-1-t2997368/page334#post72306262

I ran into an issue when flashing those Gapps in TWRP 3.1.0-0 on Nexus 7 as described in:

https://xdaforums.com/showpost.php?p=72294335&postcount=3330

The Dev there reported that the ROM or Kernel has the root cause:

https://xdaforums.com/showpost.php?p=72305339&postcount=3333

As I reported there, using OpenGapps did work. I did not try the indicated DynamicGapps.
[Nexus 7 Android Development] AndDiSa:
[MENTION=6291257]frov[/MENTION] so your finding says that TWRP is missing a patch / using a wrong kernel? But it's strange that all the other zip files I was flashing up to now were executing fine.

Nevertheless I found a bug in TRRP 3.1.0.0, too:

adb backup --twrp is not working, it's finishing immediately due to missing /bin/bu binary. Probably I should inform Drees Troy about these issues.
[Nexus 7 Android Development] a247:
Google Maps issue

I'm coming from stock 4.4.4. It is amazing how well this old Tilapia device performs with this ROM, great work!

My only use of the Tilapia tablet is Google Maps in my car. Same here, great performance, much smoother than before. Just one issue: While navigating, when I touch the microphone button on top, the area where the map is drawn starts to flash black and white at high speed, but Maps continues to run, I still get directions where to go. There is no way to get the map display back other than wiping away Maps from the recent apps list and then restarting it. The same thing happens sometimes when I switch to another app and then back to Maps. This was working ok with 4.4.4.

To install this ROM, I completely wiped the device including interal storage, installed the ROM, OpenGapps Pico (also tried Nano) and then Maps from the store. I have 130 MB free in the system partition and have granted all permissions to all Google apps.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8280502]a247[/MENTION] I never saw such an issue ... it would be great to have a logcat to alalyze this issue more deeply.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8280502]a247[/MENTION] I'll have a look at it later, thanks for posting the log.
[Nexus 7 Android Development] pehlm:
Thanks @AndDiSa for the new version of the ROM! It's working as expected, I think it's even more stable now than before. I've now changed from SuperSU to Magisk and it's working really good. Wish I could help you out with the Magisk - SafetyNet error though, I think as you say that it isn't a ROM issue but a Magisk bug, so we will wait and see. But thanks again! :good:
[Nexus 7 Android Development] AndDiSa:
[MENTION=7682126]pehlm[/MENTION] Currently I am not very happy with Magisk, the processor does not really use the lower frequencies and uses only 1000 MHz- 1300 MHz ... probably it's due to different sepolicy settings. You need to have a look at that.
[Nexus 7 Android Development] paasoares:
Are you sure ?

Take a look at this screenshot. I'm using magisk
[Nexus 7 Android Development] AndDiSa:
[MENTION=342699]paasoares[/MENTION] no, I am not 100% sure that it remains in that state, but if I compare having rooted with SuperSU the frequencies almost immediately after initial startup go down to 340 - 860 MHz and is switching off unused cores while with Magisk it remains on 1000 - 1300 MHz and the device is notably becoming warm ...
[Nexus 7 Android Development] indexftw:
Hi.

So far imo this is the best experience on tegra nexus 7.

There's one issue though. I can only charge it while the tablet is turned off. If I try to charge it while it's on it doesn't react to usb charger. If I turn it on while it's charging it will drain power faster than it can charge. Core speed fluctuates I think from 300 to 1300 I tuned it down to 1000 still no go. Charger I'm using is stock one output rated at 5v@2apms DC.

Any hints? With all 4 custom roms I've used since 2012 charging worked just fine. I doubt it's hardware issue.
[Nexus 7 Android Development] a247:
I can confirm the issue with USB charging. It only works the first time after booting up the device. If you unplug and then plug in again, from then on it won't charge anymore. I am not affected because the charger in my car is detected as an AC adapter and with this one it works ok.