yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] FabianoT:
So, I'm not alone :D

This is quite strange, perhaps this feedback'll be useful to [MENTION=2188693]AndDiSa[/MENTION], in case he looks for further improvements.

My Nexus is yet 4 times (or more) faster than with stock Android... it's not a big issue.

Anyway, I'm still curious about the reason, if this is a planned AndDiSa choice about the supported features or not. Just curiosity.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8874203]FabianoT[/MENTION] it's not planned, but I have the same behaviour (and even with a 3.4-kernel), i.e. only generic A7-NEON instead of Tegra4-NEON. I will see whether I can find a reason for that, currently I dont have any clue.
[Nexus 7 Android Development] FabianoT:
Ok, :good: but pay attention that, I remind, Nexus 7 2012 has Tegra3 (not Tegra4) chip.
[Nexus 7 Android Development] AndDiSa:
Sorry, it was a typo ... I ment Tegra3
[Nexus 7 Android Development] FabianoT:
I have also tried Skype on 'tilapia' and works like a charm, frontal camera works. :good:
[Nexus 7 Android Development] chappatti:
Tablet not charging??

I installed the latest ROM version without hitch. However, I cannot charge the tablet. With the charging cable in, nothing happens. Same cable and block work for other phones. But the Nexus 7 shows no charging symbol and battery does not change %

Is this s known problem? Im on fresh ROM with Magisk only installed. Nothing else.

Thanks for any replies.
[Nexus 7 Android Development] bovirus:
[MENTION=593442]chappatti[/MENTION]

To avoid misunderstanding I believe thatit's better to report the ROM installed as date (version).
[Nexus 7 Android Development] js-xda:
Maybe a bit silly idea but try charging while running the recovery (TWRP) instead of the normal ROM. Just to understand whether it is something about the ROM or about the hardware.
[Nexus 7 Android Development] jackjsa:
Latest logcat (memory leak problem)

Hi, sorry for late logcat because I'm too busy, but now I got it!

hope dev can found reason of this problem,

Regard.
[Nexus 7 Android Development] psiphi:
Reboot without having the charging cable hooked to it. After it is booted, attach the cable.
[Nexus 7 Android Development] mikefive:
I can confirm that i -sometimes- have this behaviour too. (20180917 version) After several days i'm not able to charge the tablet anymore.

But a simple reboot solves this problem for me.
[Nexus 7 Android Development] mafarric0:
Same here, since long ago...
[Nexus 7 Android Development] mausbock:
I also had some trouble with slow or not charging when plugging in original charger. Mostly this occured when battery was lower 15% and automatically entering power saving mode.

Rebooting sometimes helped, but only when disconnecting before rebooting.

Charging while powered of always was possible but still not fast.

Then I tried the charger from my Galaxy S7 and using this I have no issues and charging is much faster than before. Rebooting or charging while powered off is not necessary now.
[Nexus 7 Android Development] jackjsa:
I use my tablet for web browsing, listen the music, watched offline video and play some game over 2-3 days(not turn off) it's not have this problem but when I streaming video (eg. YouTube, Newpipe, and in browser) my device slowdown & got stuck... and some time it reboot to google logo, I watch RAM free it's only 80-150 MB left,

1. I repair /data and /cache by TWRP but this problem still there

2. I have this problem before install fdroid, BTW I can try to re-install it and test again

PS. I don't know this problem caused by F2FS or not ? because I format /data and /cache to F2FS

What file system are you using ?
[Nexus 7 Android Development] chappatti:
Agreed ! I rebooted and all is fine.

Thanks all !!

---------- Post added at 02:37 AM ---------- Previous post was at 02:33 AM ----------

Agreed ! I rebooted and all is fine.

Thanks all !!
[Nexus 7 Android Development] rockuman_ex:
Is wifi very unstable with the latest version?

I get disconnections every few seconds
[Nexus 7 Android Development] chappatti:
No not really. I dont see such a behavior on my tablet.
[Nexus 7 Android Development] Mandrake2010:
hi, I had the 13 cm, with the twrp 3.2.3 I did a cleanup of data / system / cache / dalvik. then installed the latest firmware. the rom is ok but how a problem with the screen, when I turn it off, when I turn it on again the brightness is very low you can not see it (sometimes you can not see it), I have to press the power button several times until the unlock appears with the right brightness. maybe it's a brightness level problem? I had it set at 30%

Edit:with brightness over 40% no problem, but to boot ghost touch. ( vanished after off/on screen)

Sorry for bad english
[Nexus 7 Android Development] rockuman_ex:
does double tap to wake work?

i got it enabled in the settings, but it doesn't wake up the device when i double tapped
[Nexus 7 Android Development] AndDiSa:
It works ... as long as the device is not in deep sleep mode.
[Nexus 7 Android Development] rockuman_ex:
Not sure how to get the device to deep sleep mode, but what i did was press the power button to turn the screen off, double tap, nothing.
[Nexus 7 Android Development] bagoes.s:
how to share storage with other device by wifi or usb?
[Nexus 7 Android Development] gmikhail:
You can use MiXplorer: https://xdaforums.com/showthread.php?t=1523691

Start FTP server on one device and go to it from another (all devices must be on the same wifi network).

Opening usb drives is also supported (in MiXplorer settings: Enable user OTG driver).
[Nexus 7 Android Development] FabianoT:
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------

[/COLOR]

I have installed the ROM two weeks ago and that one works stable with WiFi. I have tilapia(3g version)
[Nexus 7 Android Development] bagoes.s:
I have use MiXplorer, but still can not connect with that using FTP server. I used FTP client on my PC. Also try connect with USB to PC still not showed. Have set to transfer file.

For USB OTG flashdisk is OK.
[Nexus 7 Android Development] Mandrake2010:
[MENTION=225651]op[/MENTION] Thank very much for this ROM, fast and good battery, but the brightness under about 40% is set at 0??? Over 40/45% no problem.

Somebody have this problem??

I have grouper 16gb
[Nexus 7 Android Development] joshiyama:
Setup wizard crashes

The setup wizard crashes every time any idea how to fix that?

never mind I went back in to TWRP wiped it reloaded the ROM and gAPPs it seems to be working great now.
[Nexus 7 Android Development] rahimali:
The solution to setupwizard crashing is provided in the OP
[Nexus 7 Android Development] AndDiSa:
Version with December 2018 security patches

I just uploaded the last version of the ROM with December 2018 security fixes. Beside that I've tried to fix some memory glitches which were reported by some users.

You can download the new version directly from the OP.

Some additional hints I would like to mention here as sometimes users are complaning about slow responsiveness / snappiness / video stuck ...

If you are updating, I suggest always to clean cache and dalvik-cache even if the initial boot will take looonger. Also after system is up and running there is still much optimization work going on in the background.

Please keep in mind that during that stage the system might be not as snappy as you are expecting, especially if you have installed a huge amount of applications. Let it settle down (those optimizations may be noticeable within the first few hours(!) of usage) but the overall performance will improve much over time.

[MENTION=5304398]jackjsa[/MENTION] I played youtube for several hours in continuation withhout having issues
[MENTION=8559165]OlliWi[/MENTION] I also played "Force of Glory" yesterday for more than half an hour checking memory consumption. The memory usage is always critically high, but I had no crash.
[MENTION=5128593]dark0shark[/MENTION] I've updated the link to Magisk, too, thank you very much for the hint
[Nexus 7 Android Development] bovirus:
[MENTION=2188693]AndDiSa[/MENTION]

I beleieve that for most iof user is bnot celar that

- Asus - Model names

Grouper = Asus Nexus 7 2012 WiFi

Tilapia = Asus Nexus 7 2012 3G

I propose you to add this important info at begin of first post to avoid a lot of misunderstanding

For the same reason and your thread visibility, I believe that could be useful to change the thread title form

[ROM][NZH54D][2018/12/05][Grouper|Tilapia][F2FS/EXT4]Android 7.x AOSP

to a different title like

[ROM][NZH54D][2018/12/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP

Please add in first post the changelog about release 08.12.2018.

Thanks for your wonderful firmware.
[Nexus 7 Android Development] Adiker:
Great ROM, my N7 is usable again. Strange thing though, I tried F2FS filesystem and it was very laggy but it supposedly should be better than ext4... I switched back to ext4 and it's much better.
[Nexus 7 Android Development] psiphi:
Try putting a FTP Server on the PC instead and just use the tablet as a client. I have had to do this my self on occation with devices, but don't recall if the Nexus 7 was one of them. I assume there is a firewall on some devices that get in the way of them being servers. There is probably an app to check and change firewall settings, but I am too lazy to look for it.
[Nexus 7 Android Development] SmaRkieS:
agree, 2 years ago I killed my nexus 7 because that dev is careless for not identifying the rom properly. I end up buying new motherboard.
[Nexus 7 Android Development] jackjsa:
Memory leak problem solved!

I do a clean flash with latest build (20181208) and I tested to watching YouTube & other streaming apps 2-3 days, this problem is gone and memory management even better, everything smooth, I've not found any problem,

but I have some question, after my device boot up(first boot) it's not enter setup wizard screen but it's enter to home screen instead, that's normal ?

(I try to re-flash this rom and factory reset but got the same)

PS. I'm very happy :victory:, this ROM make my nexus run like new, Thank you so much [MENTION=2188693]AndDiSa[/MENTION] :good:

Sincerely,
[Nexus 7 Android Development] AndDiSa:
[MENTION=5304398]jackjsa[/MENTION] you are welcome! I am glad to hear that your issues are gone.
[Nexus 7 Android Development] AndDiSa:
double post
[Nexus 7 Android Development] behere:
The 3G disconnects after being in standby for couple of hours? Need to restart for the 3G to reconnect. Anyone else with tilapia having this issue.
[Nexus 7 Android Development] Portgas D. Ace:
Not trying to step on your toes, but it is YOUR duty to do proper research before flashing software onto your device.

@AndDiSa: I am still amazed how smooth this old piece of hardware runs because of your well-balanced ROM :good:
[Nexus 7 Android Development] bovirus:
[MENTION=5901790]Portgas D. Ace[/MENTION]

I believe that it's important that anyone make some checks before to flash a firmware.

On the same time time it's important that the info can help the user (also novice) to identify the product in the right way.

For that I propose (and AndDiSa accept and apply) to change from product name (grouper/tilapia) to full product description (Nexus 7 2012 Wifi/3G).
[Nexus 7 Android Development] Portgas D. Ace:
[MENTION=637263]bovirus[/MENTION]

I also welcome the new thread name, it will for sure avoid confusion and help users. On the other hand, the information about what grouper/tilapa means is written in the OP (not sure if added recently or if it has been there for longer :confused: ). But yeah, this is also some kind of development :good:
[Nexus 7 Android Development] mafarric0:
You are the one who is careless, because if you bothered reading the thread or the first post carefully as everyone else you would not flash the wrong ROM!

However flashing the grouper in a tilapia does not kill anything. The only consequence is that you will not have 3G while using grouper version. I already did it on purpose because of the problems on the tilapia version at the time, and when I flashed the tilapia version a few months later I had 3G again.
[Nexus 7 Android Development] TureX:
Thank you [MENTION=2188693]AndDiSa[/MENTION] for this update! Now Is fantastic! Is possible add advanced reboot and battery% in status bar?
[Nexus 7 Android Development] Ahkah:
For whatever reason the device reacts much better with the December version than with the October version that was installed previously. However, I have not been using it very much so far, especially not for YouTube.
[Nexus 7 Android Development] sinthemau:
[MENTION=2188693]AndDiSa[/MENTION]

First, thanks a lot for all this: my Nexus is now again workable, indeed.

I started with October release and all gone well, but then I tried to update with December OTA release and nothing happens!!!

I explain better: I flashed again from TWRP and all scripts work out flawlessly, but when finished if I go to Android System Information on my Nexus I still see reference to the October patch and security update!!!!!???

I followed the info in 1st message and "apparently" all gone OK...where am I doing bad? Cannot understand

Thanks a lot for your efforts
[Nexus 7 Android Development] AndDiSa:
[MENTION=2957165]sinthemau[/MENTION] I checked the links in the OP and they are fine. The November-versions had the issue that they were saying serurity patch "05/10/2018", but the December-versions are fine. I have no idea why it still shows October ...
[Nexus 7 Android Development] sinthemau:
Thans for checking AndDiSa...

maybe something goes wrong updating, cannot say.

I have tried 3 times to do the update and always was the same, very strange.

Maybe I will go again starting over with a full factory reset like the first time.

Thanks indeed and see you
[Nexus 7 Android Development] AndDiSa:
[MENTION=2957165]sinthemau[/MENTION] did you check the MD5-sum of the file and does it match?
[Nexus 7 Android Development] sinthemau:
NOt done yet, I will do . Thanks for the input
[Nexus 7 Android Development] sinthemau:
[MENTION=2188693]AndDiSa[/MENTION]

Reloaded the OTA and all is fine now. Probably it was corrupted..

Thanks pal!
[Nexus 7 Android Development] wkpn:
Hi, I'm trying to install it on my Tilapia and I cannot get gapps to work. I did install ROM, rebooted, installed gapps and I just don't get them. I can't open Play Store because it closes immediately. I downloaded Gboard from apkmirror and it says that I don't have Google Play Services installed. Gapps log seems fine.

Can anyone help? Thanks.
[Nexus 7 Android Development] mikeataol:
Thanks for providing this.

Runs great, went from stock 5.1 to this and it runs great (WiFi/grouper 20181208.)

Appreciate you providing it.
[Nexus 7 Android Development] heilbron:
I also had these problems with OpenGapps on Grouper, and finally gave up on them.

However, BeanGapps (from 2017) worked fine! Don't worry about the their old version, it gets updated automatically after installing.

Pls hit thanks if this helped you!
[Nexus 7 Android Development] TureX:
Hi, i got a problem, bluetooth doesn't turn on,if you Need i Will provide a logcat
[Nexus 7 Android Development] wkpn:
that worked, but I don't have on-screen buttons (back, home etc.). Any fix for that?

upd: also when I reboot system ui constantly crashes and I need to re-flash everything again
[Nexus 7 Android Development] Nexus7_tilapia:
!!!

#REPORT

I did clean install the latest release & everything works like a charm here. [tilapia]
[Nexus 7 Android Development] AndDiSa:
[MENTION=4963494]wkpn[/MENTION] looks as your permissions for gapps are not set correctly, probably you need to do a wipe before using the BeansGapps as the 'old' gapps have already the wrong permissions set. Nevertheless the PICO gapps are working without any issues and the rest you can install from the play store.
[Nexus 7 Android Development] wkpn:
not sure how many wipes I did, I managed to get it to SetupWizard, but now I'm stuck at "Checking for updates" screen...
[Nexus 7 Android Development] schmatzler:
Thank you for the update! The device runs very smooth.

I am still running it with MicroG instead of OpenGAPPS.

The update is very simple. I just flashed the ROM, SuperSU and XPosed over my existing install and copied the MicroG apps from /data/app into /system/priv/app again (had to redo the permissions to 755).
[Nexus 7 Android Development] TureX:
Here logcat of bluetooth turning on problem
[Nexus 7 Android Development] AndDiSa:
[MENTION=3777227]TureX[/MENTION] I guess there is something wrong within your /system partition. The file /system/lib/libchrome.so is missing and due to that bluetooth cannot be switched on.
[Nexus 7 Android Development] CamoGeko:
Finally decided to try this ROM, was on SlimKat and crDroid before. With SlimKat I ran into an issue with apk's not wanting to install from internal storage, and with crDroid SystemUI kept crashing after a certain amount of time so I would have to reboot to put things right.

Hopefully this ROM doesn't have the same issues as crDroid.
[Nexus 7 Android Development] MiSSigNNo:
My bad... by the way, I can't remember but in Android 7 encryption was on by default? Could we force disable encryption?
[Nexus 7 Android Development] MiSSigNNo:
Same here: I'm stucked in the "checking for updates" screen. I think the last update is corrupted for new devices. Tomorrow I will try full wiping again and trying with another build.
[Nexus 7 Android Development] heilbron:
<deleted/>
[Nexus 7 Android Development] lotte67890:
Well, this is so far the best version of the ROM since I started using it many years ago! Even apps like Firefox, which consume a lot of memory are running smooth and flawless!

Thank you so much!

L
[Nexus 7 Android Development] Alex_Lyt:
I don't know what You've done, but finally my grouper become fast like new! No freezes on video, no freezes after deep sleep. Average free memory is about 500 instead of 100 on previous builds. Battery consumption also improved greatly! Thank You a lot!
[Nexus 7 Android Development] Sam Nakamura:
Not sure but as no one else mentioned it yet it probably a issue only on my Grouper...

No matter how but I can't update Magisk (currently 17.3) to version 18.0, I tried the recommended way by letting Magisk Manager do his job, I patched the boot image and flashed it via TWRP and repeated both with running the latest magisk uninstaller before - then I had it one time booting on Magisk v18.0 but the next boot it just hanged again on the "Google splash screen" for ages - once even over night as I forgot about it (plugged on a cable)...

Tried to get logs by PC but I didn't got any output at the stage my Grouper hangs...

First thought about a Magisk issue but 18 works on all my other devices, even on Mako... So it might be related to my setup, actually I'm asking you guys - is anyone on the Grouper December build running Magisk 18 successfully?

[MENTION=2188693]AndDiSa[/MENTION] or anybody else what logs could I provide to give a picture of what's going on here, at "the loop/hang" there's no information to pull via PC...

If I keep pressing power and vol - to boot to recovery I can simply flash Magisk 17.3 to boot up again - it only hangs on combination with v18, that's why I expected reports here but obviously I'm the only with this specific issue....

Any ideas will be appreciated - thanks for reading!
[Nexus 7 Android Development] mikeataol:
Hi. I used Magisk 18, but I was coming from stock and hadn't used a previous version. Worked fine.
[Nexus 7 Android Development] AndDiSa:
[MENTION=7125933]Sam Nakamura[/MENTION] I am using Magisk 18.0 without any issues here with my setup, but I need to say that I am normally not flashing the ota package, but the boot.img and system img directly. Nevertheless the result should be the same, i.e. flashing the ota or flashing boot.img + system.img should led to the same configuration. Rebooting to recovery and flashing magisk-v18.zip works for me flawlessly. Probably you can try to connect the device to your PC and try to get a logfile while booting

adb logcat | tee log.txt

so you can see what's going on and everything is logged to the logfile, too.
[Nexus 7 Android Development] tuserr:
Hi guys, i couldn't find anything about how to overclock GPU and CPU. It exist a kernel that let me do some overclock compatibile with this rom?

and which app should I use for overclocking?

Thanks in advance!
[Nexus 7 Android Development] Sam Nakamura:
I already connected my Grouper with the PC to log an see what happens when "it hangs" but no output at this stage... That's the thing but thanks for your suggestion, I'll try again later - just to be sure there's no user error!

So it supposed to work fine! Great news, was getting already tired from trying, all possible things failed all the time, tried so many times now... :cyclops:

Edit:

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

Ran the "full uninstall" option from within Magisk Manager, booted to recovery and flashed Magisk 1800 and it works, maybe (better probably) it was in issue with my set of Magisk Modules I usually flash after first boot, that's the best possible explanation...

Gonna do them one by one now, still wondering why "the hang" then initially, when everything was working great and only Magisk was updated (not a single Module)...

Another of these great "android riddles" which just happen, don't know... :confused:

Thanks for the support!
[Nexus 7 Android Development] Misterke:
Hi guys,

I have installed this ROM on my grouper and first impressions were great, but I'm having an issue which makes it rather unusable: after the Nexus 7 has been asleep for a while (by closing its smart-cover), there's a chance (seems to go to 100% the longer it stays asleep, but there might be some other conditions which I haven't been able to fix yet - I get the impression it occurs more when having used Youtube or because it then is in landscape mode) that waking it seems to work just fine, but the touch-screen will only see about 10% of all touches. That makes controlling the device almost impossible. Closing the smart-cover and reopening it, seems to then give me a small chance that things return to correct operation, but the chance of that are pretty low, so constantly flapping the cover closed and back open is a bit too weird to work around this.

Before I had CyanogenMod on it and had no such problem, but it was pretty slow and had much worse battery life, so I'd love to get rid of this touch screen issue, so does anyone have an idea what could be wrong here and how to fix it?

Thanks, K.
[Nexus 7 Android Development] AndDiSa:
[MENTION=2989194]Misterke[/MENTION] unfortunately I don't have a smart cover so I cannot really reproduce that behavior, but you could provide with a logfile so I'll have a look at it
[Nexus 7 Android Development] Flounderist:
In the past I built a kernel based on DanielHK works. It booted on Lineage OS. You should flash the boot.img attached using TWRP.

It has Overclock and Undervolting options enabled, use Kernel Adiutor for some tweaks.

Edit: the boot image is based on Lineage, it should boot on AOSP as well. In case of bootloop dirt flash ROM or restore a backup. Flashing a boot.img will break magisk as well.
[Nexus 7 Android Development] Misterke:
Hi AndDiSa,

I don't think the smartcover is the trigger, it just uses a magnet in the right place to trigger the same the power button would. However, just to be very sure, I've removed the cover to see wether that removes the issue.

I assume you mean an adb logcat output when you say logfile, right? I'll try hooking it up to my PC tomorrow to catch the output, but as I have the impression it might have some link with deep-sleep, I'm uncertain how adb logcat reacts to that.

To me it looks like something involving the touchscreen not getting correctly reset after waking from sleep. I have no idea what bus/protocol is used between SoC and touchscreen, but maybe after going to (deep?) sleep this isn't correctly reinitialized...
[Nexus 7 Android Development] pincher65:
trigger inside grouper, magnet just controls it. did you try to turn on the restriction of background processes in the developer settings (i use 4)?