yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Sam Nakamura:
This is a straight AOSP Nougat build, so the integration of OMS is not expected, furthermore it's not the intention of this project to offer feature sets not natively provided by AOSP (nativ OMS support was only added from Oreo, however got already limited by the release of Pie) - that's at least my understanding of it, anyone's invited to correct me if I'm wrong of course!
[Nexus 7 Android Development] AndDiSa:
Version with March security fixes (2019/13/05)

New versions for Grouper and Tilapia are linked in the OP. The following changes are applied to that version:

security patches from March 2019

missed security patches from July 2018 and October 2018

wifi enabled on initial setup, so initial setup should run through smoothly now

the occasionally reboot/shutdown issue which was e.g. reported by [MENTION=3777227]TureX[/MENTION] is (hopefully) resolved.

further improvements on device charging

additional patches on the kernel regarding power management, timer, ...
[Nexus 7 Android Development] Flounderist:
I downloaded latest build and I noticed that on 20190209 build Play Store is unable to update apps and so on.

I had to revert on January build restoring a backup to get PS working again.

Once updated, I dirt flashed latest build and magisk but still no PS working :(

Does someone had a similar issue?
[Nexus 7 Android Development] Sam Nakamura:
Did you follow the instructions, like flashing update, reboot to recovery and only then re-flash GApps (and Magisk if needed)?
[Nexus 7 Android Development] estradz21:
im having this weird issue on my nexus whenever my device display turned off i cant wake it up anymore like unlocking i have to reboot the device again to use it normally it just annoying
[Nexus 7 Android Development] Nexus7_tilapia:
Hi guys, I need help:(

I want to delete a folder in /System/App directory and i mount that Read/Write via terminal but still operation [deleting] is failed! It [FX file manager] said deleting is not permited on mounted filesystems!

BEST WISHES

-----------------

Edit:

BUT It's available via TWRP!!!
[Nexus 7 Android Development] AndDiSa:
[MENTION=8618734]Nexus7_tilapia[/MENTION] you need to mount it in R/W mode, even in TWRP. Normally it is mounted in read-only mode.
[Nexus 7 Android Development] AndDiSa:
[MENTION=2617582]estradz21[/MENTION] I cannot reproduce this, can post your device / hardware version
[Nexus 7 Android Development] Flounderist:
When moving from Jan to Feb build I only flashed ROM and magisk zip. Same when moving from Feb to latest one.

I sorted wiping data and clean flashing ROM+Gapps+magisk.

If I understood the ROM is always requiring gapps package when updating.
[Nexus 7 Android Development] Sam Nakamura:
At least I do flash GApps when updating on the N7, with a reboot to recovery in between ROM & GApps and never had such issues, I'd suspect that due to not flashing GApps on update some critical Google Services broke, hence the symptoms of not being able to update/download Apps on Playstore on your end - should be easy fixable by re-flashing the latest build with the corresponding GApps package...
[Nexus 7 Android Development] Flounderist:
Yep. PS was hanging at searching for updates.
[Nexus 7 Android Development] estradz21:
nexus 7 2012 wifi only device for me
[Nexus 7 Android Development] AndDiSa:
[MENTION=2617582]estradz21[/MENTION] sorry, I was looking for your hardware revision number (which is shown in the bootloader) to find out if there might be several versions not working well with deep sleep ... mine e.g. is ER3
[Nexus 7 Android Development] DragonTome:
For me, the March (20190309) image, does not appear to be any better about unprompted restarts. I am attaching a last_kmsg in case it may shed any light.
[Nexus 7 Android Development] AndDiSa:
Thank you very much for the log ... seems that I need to continue with the hunt :(

Can you explain me when the issue occured? While laying around? Connected to a charger? ... would be very helpful.

Edit: looks as it was not used, but charging with a power supply, am I right?
[Nexus 7 Android Development] DragonTome:
You are correct. Of the 3 times, that I have noticed since applying the March update, 2 have been while charging and 1 was shortly after it was disconnected from charging. I haven't found any specific pattern yet though.
[Nexus 7 Android Development] AndDiSa:
I had this message once some time ago, since then I was not able to reproduce. I will search a bit wether this (or a similar) issue was already reported ... probably also for a different kernel.
[Nexus 7 Android Development] DragonTome:
Thanks for investigating further. I'm quite happy to help, in anyway I can, with testing or info gathering.
[Nexus 7 Android Development] Nexus7_tilapia:
Hi guys

Today accidentally i encountered with this scene!!!

Device: Nexus 7 tilapia

Build: 20190110

Battery: Original one since 2012

[MENTION=2188693]AndDiSa[/MENTION] , I can't thank you enough!

Cheers
[Nexus 7 Android Development] NikoNik7:
Yes, that build was awesome! Next builds for Tilapia could not support this tradition so far. The accumulator is spent very quickly.

---------- Post added at 05:37 AM ---------- Previous post was at 05:14 AM ----------

Hi there,

Practically every time lag and subsequent reset is observed at installation or updating of applications for my Tilapia.

This problems were strongly shown at 20190110 Build. So I suspect that the reason (one of reasons) can be in work with 3G the module. Probably the system too often addresses communication modules even if 3G the module does not contain a sim card, judging by the strong expense of the battery which began with that version. Or reboots without having found it.

And yes, whith 20190110 Build some new corrections of a kernel began. There can be mistakes leading to permanent reset of the Tilapia during updates/installation of applications. Еconomy of the battery was replaced by strong power consumption from that Build too.

So i already thought of kickback on the version 20181208))
[Nexus 7 Android Development] nubbins01:
Hi all. Hoping I might be able to get some assistance with an issue.

I'm not 100% sure if it's from this ROM or something else more fundamental to Android, but I'm having an issue where the screen repeatedly is locking itself despite being in use, and regardless of whether or not wakelock applications are currently active. It will also light the screen up when already locked, even if there are no incoming applications. This is a tablet that hasn't been used for years, that I recently found amongst a bunch of stuff and decided to resuscitate.

This random locking and screen waking suggested an errant input somewhere, however I have not experienced the same issue just sitting in TWRP, where the screen will stay on until it hits the screen off time reliably. The issue occurs in Android Safe Mode, with on body detection disabled, double tap to wake disabled, Daydream disabled, No Smart Lock and only a swipe pin to unlock.

I thought perhaps maybe there might be an application causing the issue, but the issue occurs even when only default and pico GApps are installed. The issue appears to occur randomly - I might go hours without an issue, then at other times the issue will occur constantly for several minutes. Doesn't seem to change depending on what application I'm using - I'll have the same thing happening when I tested video (Youtube app and in a browser full screen, in non wakelock apps like sensor testors, all have been overriden)

I also suspected perhaps an accelerometer issue, but using a simple Sensor Multitool app in the Play Store, I didn't see any unexpected inputs from the accelerometer or the magnetic sensor (having said that, I'm not sure exactly what I'm looking for. Output correlated to input, however).. I am not using any kind of case, and running a magnet around the tablet affects nothing but the touchscreen.

Running:

Nexus 7 (2012 original)

AndDiSa's 7.1.2 Grouper OTA-Package (Build 20190309)

GApps ARM 7.1 Pico 20190312

Any input or thoughts would be most welcome. I have Magisk ready and raring to go, so more than happy to root if people want better diagnostic data. I have already tried rooting, but I recently flashed back to stock AOSP with GApps for testing - made no discernible difference.

Ta!
[Nexus 7 Android Development] step5:
I am using a grouper device with the latest build (20190309).

The Headphone jack is not working. There is no audio output. The headphones are working on other devices (phone/notebook) though.

Is anyone experiencing the same problem?
[Nexus 7 Android Development] DragonTome:
I am running with that build installed and have listened to music via headphones with no issues.
[Nexus 7 Android Development] bovirtual:
My tablet running the headphone jack perfectly, with some apps: you tube, netflix, etc...

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 Android Development] AndDiSa:
[MENTION=1753057]step5[/MENTION] the quality of the Nexus' headphone connection is quite bad and it's easy to get a flickering connection. I do have several headphones and not all of them are working well with my Nexus7
[Nexus 7 Android Development] step5:
[MENTION=4222375]DragonTome[/MENTION] [MENTION=2350593]bovirtual[/MENTION] [MENTION=2188693]AndDiSa[/MENTION]

Thanks for the answers!

I will try to get some other headphones for testing and post the results at the weekend.

If the headphone jack is damaged (which seems quite obvious) there will be some soldering time :D

If that doesn't help i will buy a spare part. I saw one for €5,39 on e*bay (incl. shipping from GB). That's quite cheaper than i expected.

EDIT: It works now! I had to put the vol to max, made a reboot and there was some very low volume sound. Then i pulled the plug and re-inserted it and then there was sound at a good level.
[Nexus 7 Android Development] metterschling:
I had a similar issue once with the previous release of this ROM, the tablet was not not responding to touch screen input so that it locked as there were no input. Also gesture unlock did not work as the touch screen only occasionally reacted on input. Long story short, after a reboot the issue never occurred again, so probably not the same you are seeing.
[Nexus 7 Android Development] estradz21:
ER5 for me so im ****ed?
[Nexus 7 Android Development] nubbins01:
Thanks for the reply! Yeah, doesn't sound like my issue. I'm not 100% if there's an actual physical input triggering the lock or not, but I don't think it's the touch screen itself. I've tested the screen, no errant touch zones or missing areas as far as I can tell. Reboots, Safe Mode, clearing caches etc haven't made the slightest difference sadly :(
[Nexus 7 Android Development] AndDiSa:
... at least we found out that different hardware revisions may behave differently with this ROM and it's probably an explanation for other issues reported occasionally which were not always reproduceable. Finding a solution will be the next step ...
[Nexus 7 Android Development] OlliWi:
Yes;)

ER5 doesn´t (officially) exist as far as i can see.

Board revisions mentioned in the kernel source code are
[Nexus 7 Android Development] :
Curious happenings, not sure if it's the ROM or my ageing grouper...

- WiFi has become weak; it will often drop and reconnect. My other devices are fine on same WiFi.

- web pages not displaying, maybe related to larger page content. This happens on different browsers, on different sites. If I click to another tab on the browser then click back, the page sometimes displays. Sometimes page display simply halts and I have to refresh (again; different sites, different browsers) My gut feel is this is memory/cache related but it's random and difficult to pin down.

These things started happening with the Jan release but, as I say, I've no idea if it's ROM related. My Nexus could equally be on its way out, it is getting battered.
[Nexus 7 Android Development] :
I'm going to do a complete clean reinstall as I'm getting a number of weird errors. I think my Nexus is reaching the end of its life :(
[Nexus 7 Android Development] AndDiSa:
Did you check for filesystem / emm errors? Often weired behavior is caused by a corrupt filesystem ... or even broken flash memory.
[Nexus 7 Android Development] :
It might be nothing but after I restored back to a December backup (for testing purposes), Magisk automatically updated to 18.1 and gave a 'failed' message. It said something along the lines of 'recovery image corrupt, restore stock'

So I wiped and clean installed the latest version of the ROM, rooted (with 18.1 and it was ok) and installed a fresh gapps. It's not perfect (WiFi still frail and web browsing issues as before) BUT it doesn't seem anywhere near as bad.

WiFi seems very sensitive to distance from router. That is, up to 6 feet away I get a full strength signal, 8 feet away it drops significantly and will drop out if further away than that. This is not a problem on other devices and I have tried changing channels, to no avail.

The web browsing issue, I'm still testing BUT it does seem related (in some way) to a particular forum I visit. That forum displays fine on my laptop and smartphone but my Nexus seems sometimes to struggle with it. I've no idea why. That forum does not have a 'posts per page' option (I was going to try reducing that to see if it reduced data load, its default is 50) so I've asked the forum administrator if there's any way I can reduce that count. If I don't have that forum open on a browser tab, general performance does seem better... BUT, as I say, I'm still testing and so it's all sketchy and uncertain.
[Nexus 7 Android Development] :
Well, I think I found the culprit.

I use the password manager Bitwarden and I think its 'auto fill' capability was causing the web page display problems I was having. I've uninstalled the app for now but I shall re-install to test further later, but I'm pretty confident that's it.
[Nexus 7 Android Development] topoldo:
Just to say thank you again to AndDiSa for its continuous improvement of this ROM which allows to maintain alive a device which is 7 yrs old!

Beside, I just wanto to say that when I updated the January2019 version to March2019 version (I did not install February one), I had a couple of problems, ie when I tried to launch GMail and Xodo apps they had continuous FC.

I solved my problems simply by removing and reinstalling these apps. So, if someone has similar problems, could try the same operations I performed.

Regards,

Topoldo
[Nexus 7 Android Development] :
Yes, I have experienced the same thing. Some apps just don't play nice, I don't know why that is.

As an aside, that's one of the reasons I usually do clean installs. It removes the uncertainty. Though if an app 'upgrades' its features (as happened to me with Bitwarden, as I mentioned above, and a feature becomes 'Oreo or above' only) then even clean installed apps might not work as they once used to.
[Nexus 7 Android Development] Nexus7_tilapia:
Hi guys

Who knows what are the the pre-installed 'Media storage' and 'Download manager' apps?

While capturing my traffic, i found out that these two apps send too many packets to unknown ip addresses! i disabled them with a shell command but who knows what are these apps for?

Cheers

Download manager:

com.android.providers.downloads

Media storage:

com.android.providers.media
[Nexus 7 Android Development] Portgas D. Ace:
From what I know, those two are responsible for the download of any kind of data. Disabling them will render your device unable to download files from the internet.
[Nexus 7 Android Development] Ahkah:
This is a basic component of any Android system. The media scanner service or daemon maintains an sqlite database describing all media files on the device: audio files (so called "songs" which is bullsh*t ...), pictures (mainly .jpg and .png) and movies.

The mechanism is full of bugs that have officially been blessed with "works as expected".

Consult stackoverflow for more information and about how to rebuild a corrupt database.
[Nexus 7 Android Development] outofusernames:
Known hardware problem: the WiFi antenna is on the back, connected by two springs. These can lose contact or break. If the signal improves if you press the top left of the chassis together, try carefully opening it, carefully bend the springs a tiny bit (you don't want to break them) and close again.

https://xdaforums.com/nexus-7/help/fixing-wi-fi-issues-nexus-7-t3528161
[Nexus 7 Android Development] :
Wow, much to my surprise, it does!

The back is coming off my Nexus (it's getting old and battered) and there's a gap between back and chassis of around 2 or 3mm in the top left corner. Just by pressing the gap closed, the WiFi signal improves noticeably. Weird.

Time for some glue and tape!
[Nexus 7 Android Development] Nole2019:
thanks

---------- Post added at 09:03 AM ---------- Previous post was at 08:55 AM ----------

tanks :p
[Nexus 7 Android Development] outofusernames:
What's "Weird" here? Of course the signal suffers when the antenna gets disconnected.

The wifi antenna is where the left thumb is. It connects by two springs on the main board on the right, next to the battery cable. If the gap is too large, the antenna is literally disconnected.

https://d3nevzfk7ii3be.cloudfront.net/igi/1S3nvadn4UKYoEVx.huge

Glueing the back on worked for me.
[Nexus 7 Android Development] :
It would seem weird for someone like me not aware of such things! Why should anyone anticipate that a bit of kit (wifi or otherwise) effectively be split like this; one bit on one side of the casing, one bit on the other - only functioning correctly when the casing is closed together? I didn't know and so it obviously surprised me! From the picture, there looks to be 2 (possibly 3) others things similarly split, at the top of the casing.

As it happens, I didn't need to glue the case back together. I just gently eased the back off completely and refitted it, it snapped back together nicely. I don't know why it didn't snap back before but it has now so I'm happy.
[Nexus 7 Android Development] menphis:
Please hotspot wifi not work... Not connect any device....!!!

Fix?

Thanks
[Nexus 7 Android Development] AndDiSa:
Version with April 2019/04/05 security fixes

I've just uploded the ROM for Grouper and Tilapia having the April security fixes applied.

Beside security fixed I (temporarily) reverted the kernel to the version from December 2018 as it was the most stable one and as I was not able to figure out the reason for the occasional reboots until yet.
[Nexus 7 Android Development] ismellburnttoast:
Weird. I'm on March and haven't had it; February I did though.
[Nexus 7 Android Development] CamoGeko:
This makes me want to test the March build now haha ?
[Nexus 7 Android Development] wiichoo:
Yeah me neather
[Nexus 7 Android Development] DragonTome:
The December kernel in the April build doesn't seem to make much difference. I still get restarts and odd behavior, mostly when charging. So could possibly be related to something I have installed or how I have things configured.
[Nexus 7 Android Development] Nole2019:
"CTS profile match --Fail"

In addition to this problem, everything else is perfect.

:good:
[Nexus 7 Android Development] AndDiSa:
strange ...
[Nexus 7 Android Development] OlliWi:
That test always fails on my tilapia. Anything to configure to have it pass that check?
[Nexus 7 Android Development] Nole2019:
tilapia+ROM[2019/04/05]+Open GApps (arm/7.1/pico)

no Magisk

no Root

"CTS profile match --Fail" :(

Anything else should I do?
[Nexus 7 Android Development] AndDiSa:
[MENTION=8559165]OlliWi[/MENTION] [MENTION=9831162]Nole2019[/MENTION] probably it's the version string for Tilapia which is not correctly set. I'll have a look at it.
[Nexus 7 Android Development] Nole2019:
waiting for your good news
[Nexus 7 Android Development] simonchpl:
The same here.
[Nexus 7 Android Development] laugeek57:
Grouper dirty flash over march build

no magisk v18.1

no root

flash magisk v19.0 all works fine :)
[Nexus 7 Android Development] DragonTome:
I may have been a bit hasty in my assertion. Aside from one unprompted restart shortly after installing the April build, I do not believe I have had another. My current uptime is ~80.5 hrs, which far exceeds what I was experiencing before.
[Nexus 7 Android Development] NightTrovador:
Hello, the ROM is great, it is just what I was looking for to give more life to my tablet, the problem is that it does not detect the Gapps installed by the Recovery, it is the Pico 7.1 ARM version. It installs well but when starting the tablet nothing of the Gapp.

What can be the solution, thank you very much!
[Nexus 7 Android Development] laugeek57:
Hello,

Flash the rom let do a first start then reboot recovery and flash gapps :)
[Nexus 7 Android Development] step5:
[MENTION=2188693]AndDiSa[/MENTION]

Just wanted to let you know i am using your rom some time now (at least a year) with one tilapia device and one grouper device and i have updated the rom on every release.

All this time i have never experienced reboot issues on any of the devices.

Before the first flash i did a factory reset including user data. I never installed gapps. Maybe the problem is connected to this...
[Nexus 7 Android Development] tombunyon:
I get this issue on both the tablet and my phone, and the solution I've found is simply finding the Play Store in the settings and force stopping it, although I don't believe this would apply to you as you need to reboot the device to clear the cache so the Play Store would have stopped and restarted already. On my Grouper device formatted in EXT4, Chrome will download properly (although the web browsing experience on Chrome on this device is quite poor, I recommend installing Android System WebView and using the Lightning browser), and using F2FS with this device and ROM in the past have given me download issues as well, so I suspect that there may or may not be some sort of incompatibility with F2FS. Can you try formatting Cache and Data as EXT4 and seeing if this solves the issue?
[Nexus 7 Android Development] AndDiSa:
[MENTION=9858035]magicb[/MENTION] did you check whether GApps / downloader / ... have been granted file storage permission?

Regading partitions and infos you probably would like to have a look at nexus-7-partition-sizes-16gb-model
[Nexus 7 Android Development] DragonTome:
(deleted)
[Nexus 7 Android Development] :
I seem to have the charging issue back (that is, often having to reboot before my Nexus recognises that the charge cable is plugged in) I had it once upon a time, some months back but I don't recall exactly when. Is it possibly kernel related?
[Nexus 7 Android Development] brewer75:
I have had no problems charging my Grouper and the ROM continues to function well on this old tablet!
[Nexus 7 Android Development] berthur:
Hi,

I just installed this rom on my Tilapia.

It looks really great.

I really miss one thing though.

Is there a way to enable native otg usb support in it?

Charging seems to be very is slow as well. Could it be accelerated somehow?

Thanks for the help in advance!
[Nexus 7 Android Development] OlliWi:
What do you mean with "native" otg usb support?

USB OTG is supported in this ROM.

Issue is under investigation. But it doesn´t seem be easy to fix as it might be software

and

hardware related.
[Nexus 7 Android Development] OlliWi:
No need for any extra app here too. Otg works out of the box. Did you do a clean install of the ROM?
[Nexus 7 Android Development] berthur:
Yes I did a clean install.

When I plug in the USB the ROM says it is not supported and wants me to format it.

Are there restrictions in supported file systems maybe?
[Nexus 7 Android Development] OlliWi:
Can you provide logfiles from the kernel (dmesg) and android (logcat) after you plugged the stick in?
[Nexus 7 Android Development] berthur:
Sorry but I'm not this advanced. :P
[Nexus 7 Android Development] Sam Nakamura:
No need to be sorry at all...:)

______________

There are nice apps on playstore helping you getting the requested files, not even a PC is required, check "syslog" for example and upload the logs to Google Drive and share the link here with us!