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

[LesGirauds]

Thanks for that. I was using the balance branch and getting freezes. I'll see how it goes on 'latency'.

I'm getting freezes on the latency branch too. I've removed Ktweak whilst I do further testing.

Edit: I'm now in the process of trying to recover my Nexus from some quite worrying errors, I think it might be a gonna. I'm having to repair & reformat partitions (changing file system) in the hope I can get it back but I keep getting "failure to mount '/system' (invalid argument)"

Edit edit: Sadly, I think it's gone. I eventually managed to repair and wipe all partitions, load the latest ROM, Magisk and GAPPS but the Nexus just keeps random freezing. I can only reboot and carry on... until the next freeze.

Edit edit edit: yep, she's dead. I don't really know what they problem is but maybe the partition table is shot. I've already recreated and reformatted the data partition due to it having disappeared completely. Then I'll get system or cache mount errors. Sometimes it holds together for long enough for me to clean flash a ROM, only for it to die again; freezing or partition mount errors. I've reflashed an earlier version of TWRP but that hasn't helped. I think I'm calling time on it.

 

[nitishdk]

Unable to sign in playstore after update to latest version clicking on sign in doesn't do anything even in settings there is no option to add Google account also it asks for playservices

 

[AndDiSa]

Unable to sign in playstore after update to latest version clicking on sign in doesn't do anything even in settings there is no option to add Google account also it asks for playservices

Did you reflash gapps after updating the ROM to the latest version?

 

[nitishdk]

Did you reflash gapps after updating the ROM to the latest version?

No do I have to?

 

[AndDiSa]

No do I have to?

Please have a look at the OP. There is described what to do in case of a new install and what to do in case of an update install ... and yes, you have to reflash gapps.

 

[nitishdk]

Please have a look at the OP. There is described what to do in case of a new install and what to do in case of an update install ... and yes, you have to reflash gapps.

Ok no problem will do I just checked ur last post and did update

 

[LesGirauds]

I dug out my old Nexus (a 16gb model) which had a broken screen and used its internals (motherboard etc) and assembled a 'new' working tablet. Just now updating it to the latest ROM etc.

I hate throwing stuff away when there's a chance it could be re-used/repurposed so it feels like validation for hanging on to 'junk'! I really didn't want to buy a new tablet not least because I like the Nexus 7.

 

[Foliant]

Hello,
Im using (Build 20201217) and can say its running way smoother than Lollipop.
Installed open_gapps-arm-7.1-pico-20201223 and can install one App at a time (download queue seems to stop)

I found two annoying behaviors:

• First is the Home- (circle) and Tasks- (rectangle) Button doesnt work. Back (triangle) is working fine.
• Second: Holding the WLAN-Icon does not open the Network Settings, however a short tap does enable/disabling WLAN.

I was updating the Tablet because Android 5 was unacceptable in performance. I have another "grouper" with Kitkat and its reasonable fast. Now Im also wondering if there might be other things on(in) my hardware causing the issues.

Are there any workarounds or things i should try?

Regards, Patrick

 

[rickykemp]

I've flashed this to a grouper but cannot get the pico gapps to install - always get an error 70 in TWRP. TWRP says my system partition is only 639MB, even after using TWRP to resize it. Any ideas?

 

[Razor98566]

I used some other 7.x rom so far and had heavy problems with things as simple as watching youtube, couldn't watch anything higher than 480p. Now I can watch stuff on 720p again!
Sadly games like Cytus still don't run anymore (which they did back then, I think it was on version 5.x ?) but my Nexus is old xD

Thank you!

 

[BeeJ1109]

HI ALL,
How do you put this device into download mode, so I can flash TWRP v3.4, via PC and ODIN, or Equivalent for Nexus 7. I am a Samsung user.
No Procedure is available on this Thread. To Go from Stock to New Release ROM, via TWRP. Stock is so "bloody slow" to do anything useful. I only just charged the battery after 2 years of being stored away. Updated all apps from Google Play Store, took a whole day, still no improvement.
I Wish to add TWRP, backup, then Root with Magisk 20.4, then add Titanium Backup Pro, backup apps only. Install latest ROM, Restore apps. Save backup with TWRP, OS & apps. Done.
Any help or links to proceed would be appreciated.
Thanks & Cheers.
Merry Christmas and Happy New Year to All.
BeeJ1109

 

[rahimali]

HI ALL,
How do you put this device into download mode, so I can flash TWRP v3.4, via PC and ODIN, or Equivalent for Nexus 7. I am a Samsung user.
No Procedure is available on this Thread. To Go from Stock to New Release ROM, via TWRP. Stock is so "bloody slow" to do anything useful. I only just charged the battery after 2 years of being stored away. Updated all apps from Google Play Store, took a whole day, still no improvement.
I Wish to add TWRP, backup, then Root with Magisk 20.4, then add Titanium Backup Pro, backup apps only. Install latest ROM, Restore apps. Save backup with TWRP, OS & apps. Done.
Any help or links to proceed would be appreciated.
Thanks & Cheers.
Merry Christmas and Happy New Year to All.
BeeJ1109

Power off device. Then turn power on while holding down Vol Up + Vol Down buttons. That should bring you into bootloader/fastboot mode from where you can flash TWRP

 

[AndDiSa]

If your device is connected to a PC via USB and having ADB installed and configured, a simple

adb reboot bootloader

should do the trick, too.

 

[AndDiSa]

Power off device. Then turn power on while holding down Vol Up + Vol Down buttons. That should bring you into bootloader/fastboot mode from where you can flash TWRP

Holding Vol Up + Vol Down on (re-)starting the device will bring it into apx-mode. So be careful! Leaving that mode is possible only by pressing the power button for at least 20 seconds.
Booting into bootloader Vol Down + Power is sufficient.

 

[Foliant]

Just to let you know:

two annoying behaviors:

• First is the Home- (circle) and Tasks- (rectangle) Button doesnt work. Back (triangle) is working fine.
• Second: Holding the WLAN-Icon does not open the Network Settings, however a short tap does enable/disabling WLAN.

Meanwhile I boot the latest Unlegacy (ua_grouper-7.1.2-20200619-0145.zip) its also faster than stock Lollipop and all is working well.

I cant verify if it was a bug in initialization or the ROM itself, because I dont want to switch the ROMs again.

 

[Hagemanto]

Hello people, hello AndDiSa and thanks for this wonderful rom. I'm using since last December, always ran fine, some lag sometimes but I can use it for my daily tasks (aka play, read pdf, connect to chromecast). Partition are f2fs except system, I left original (I read it could be left like this with no big cons). I have just a question, when I start the tablet up it stucks on the Google logo screen for a long time (around 90-120 seconds), after that it works fine, and if I need to cold reboot I need to wait other 2 minutes because it stops responding, as if it's performing some sole turnoff operation. Not a big problem though, but I wrote to get some opinion and hint from expert members, to get it work even better, if possible.
Thanks in advance, people, and I wish you all a happy new year.

 

[Flounderist]

Hello people...

Long booting time is quite normal (it usually takes around 3/4 minutes and 7/8 after a clean flash). F2FS is ok for data partition only, cache and system can stay ext4 as usual. Try with a full device format for a fresh start. Don't forget that if you format data, it goes back to ext4 file system.

 

[Hagemanto]

Long booting time is quite normal (it usually takes around 3/4 minutes and 7/8 after a clean flash). F2FS is ok for data partition only, cache and system can stay ext4 as usual. Try with a full device format for a fresh start. Don't forget that if you format data, it goes back to ext4 file system.

Thanks for the answer, I didn't know about that last part.
I meant, long booting time occurs every time I turn the tablet on, not just after a rom flash. With google screen logo staying for long, long minutes

 

[AndDiSa]

Thanks for the answer, I didn't know about that last part.
I meant, long booting time occurs every time I turn the tablet on, not just after a rom flash. With google screen logo staying for long, long minutes

Staying such a long time on the Google logo may also indicate that a file system check is initiated ...
Generally I would expect boot times of less than a minute on a "warm" boot. I cannot speak about f2fs as I never used it for a longer time but if I remember well boot times without the need for application optimization rarely took more than 2 minutes until I was able to use the device.

 

[Hagemanto]

Staying such a long time on the Google logo may also indicate that a file system check is initiated ...
Generally I would expect boot times of less than a minute on a "warm" boot. I cannot speak about f2fs as I never used it for a longer time but if I remember well boot times without the need for application optimization rarely took more than 2 minutes until I was able to use the device.

Well, it's not big deal, I can wait. Just my curiosity. By the way, I have another question... Ok to use f2fs or are there other, newer, better file system to use?