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

[emregezgin]

Hey guys.

Does anybody have speed issues? It feels like im running a wrong setting of some sort because i just tried to instll the new update from scratch with TWRP 3.4.0.0 and everything, but my grouper unit still uses like 15-20min to even open an app. I dont get why it is so slow.. I tried to use F2FS on cache and data partition but no difference at all.
It uses like 2-3 min to unlock screen and so on. Does anyone know what could be wrong? Partition sizes or is it because of the Gapp pico package?

 

[andynroid]

Hey guys.

Does anybody have speed issues? It feels like im running a wrong setting of some sort because i just tried to instll the new update from scratch with TWRP 3.4.0.0 and everything, but my grouper unit still uses like 15-20min to even open an app. I dont get why it is so slow.. I tried to use F2FS on cache and data partition but no difference at all.
It uses like 2-3 min to unlock screen and so on. Does anyone know what could be wrong? Partition sizes or is it because of the Gapp pico package?

Did you format ur data by typing yes in TWRP

 

[emregezgin]

Did you format ur data by typing yes in TWRP

Yes I did.

I have for some times played around with custom rom on older devices like oneplus one, different Samsung's and so on. That's why I'm pretty confused about how this tablet is acting like this.
It seems like the device is like pretty useless when I put on gapp, but from what I can read in peoples comments it's not the case.

I'm mainly planing to use the device as an alarm clock with google assistant and few things like calender and so on, but it can barely do this.

Do I need to increase a partition size? Or is this just a side affect of gapp?

Can someone maybe upload a video where they kind of show how fast the device is in general?

 

[E66666666]

Yes I did.

I have for some times played around with custom rom on older devices like oneplus one, different Samsung's and so on. That's why I'm pretty confused about how this tablet is acting like this.
It seems like the device is like pretty useless when I put on gapp, but from what I can read in peoples comments it's not the case.

I'm mainly planing to use the device as an alarm clock with google assistant and few things like calender and so on, but it can barely do this.

Do I need to increase a partition size? Or is this just a side affect of gapp?

Can someone maybe upload a video where they kind of show how fast the device is in general?

afaik it's just bad luck, the storage on these devices just deteriorates and then it's practically unusable.

https://www.phonearena.com/news/Is-...oogle-Nexus-7-units-before-their-time_id44240

Have 2 Nexus 7 2012's here, both are basically useless by now.

 

[emregezgin]

afaik it's just bad luck, the storage on these devices just deteriorates and then it's practically unusable.

https://www.phonearena.com/news/Is-...oogle-Nexus-7-units-before-their-time_id44240

Have 2 Nexus 7 2012's here, both are basically useless by now.

Could explain why it's acting the way it is. But why should it make a difference if it has the gapp or not? The gapp uses memory more active maybe? If yes, then it is probably the explanation......


Isn't there a way to test memory module? I guess it is a random read/write test or just some kind of bad sector(don't know if you can have that on a ssd) test?

I still think of installing a lower maybe oem android rom, like KitKat or something similar that is all about minimal size and max speed, but I feel more and more it is a waist of time. Mostly because this rom seems great in the comments and the work behind it, but it still making the tablet this slow.....

 

[DragonTome]

I'm wondering if anyone else has tried to build the rom from latest sources. I'm getting a compile error in bt that is preventing the build from proceeding. The error is:

system/bt/service/hal/bluetooth_interface.cpp:278:44: error: too few arguments to function call, expected 2, have 1
    status = hal_iface_->init(&bt_callbacks);
             ~~~~~~~~~~~~~~~~              ^
1 error generated.

Looking at the source of that file, it has not been updated in many years so I assume a dependency has changed. Any hints on how to correct this would be appreciated.

 

[AndDiSa]

I'm wondering if anyone else has tried to build the rom from latest sources. I'm getting a compile error in bt that is preventing the build from proceeding. The error is:

system/bt/service/hal/bluetooth_interface.cpp:278:44: error: too few arguments to function call, expected 2, have 1
    status = hal_iface_->init(&bt_callbacks);
             ~~~~~~~~~~~~~~~~              ^
1 error generated.

Looking at the source of that file, it has not been updated in many years so I assume a dependency has changed. Any hints on how to correct this would be appreciated.

I just checked and it seems that I forgot to push the branch upstream. Can you check again, please?

 

[DragonTome]

I just checked and it seems that I forgot to push the branch upstream. Can you check again, please?

Thanks. I sync'd the repo again and kicked off a make. It has gotten further (and still running), so I assume that was the issue.
Edit: build completed and I have installed successfully.

 

[j8a]

I succesfully installed twrp-3.4.0, OTA-Package (Build 2021107) (AOSP 7.1.2) with security patches from November 2020.
Great job!

 

[brackenhill_mob]

Many thanks @AndDiSa - keeps my wonderful Grouper useful!

 

[bb709394]

Many thanks @AndDiSa - keeps my wonderful Grouper useful!

This rom is amazing, brought my N7 back from the brink of death and is useable again (slow but useable). I was using a custom 6.0 rom and is was slow AF.

Twrp 3.2.2 works fine, used to to clean flash this rom and installed GApps pico. Rooted with Magisk 21.1 and installed Adaway and Vanced YouTube.

Thank you for the great work with this rom!

 

[fsw_informatrix]

This rom is amazing, brought my N7 back from the brink of death and is useable again (slow but useable). I was using a custom 6.0 rom and is was slow AF.

Twrp 3.2.2 works fine, used to to clean flash this rom and installed GApps pico. Rooted with Magisk 21.1 and installed Adaway and Vanced YouTube.

Thank you for the great work with this rom!

As you are rooted, if you find it too slow, you should give the app Trimmer (fstrim) a try. I'm using it after each ROM flash, each reboot and every time I install or delete something. It really make a difference on my Nexus 7.

Sent from my Redmi Note 6 Pro using XDA Labs

 

[changsterdj]

How do you put TWRP on this?

 

[fsw_informatrix]

How do you put TWRP on this?

Really?
5 seconds search on the Web:
https://twrp.me/asus/asusnexus72012wifi.html

Sent from my Redmi Note 6 Pro using XDA Labs

 

[laugeek57]

Hello,
@AndDiSa
I get my new tablet tomorrow, so I wanted to thank my German "cousin" for letting me keep my Nexus 7 (2012) for all these years ... Thanks Dude

 

[Velmont]

Hi! I am on stock Android 5, I think this ROM looks like the best one to get a modern enough device for such oldie. Particularly interested in an updated browser.

Did anyone go stock 5 to asop 7? How is that experience? As snappy or you lose some?

 

[brackenhill_mob]

Hi! I am on stock Android 5, I think this ROM looks like the best one to get a modern enough device for such oldie. Particularly interested in an updated browser.

Did anyone go stock 5 to asop 7? How is that experience? As snappy or you lose some?

I suspect most people here swapped ROM a long time ago and kept going so can't remember - I upgraded in 2013!

It's all relative. My device seems really slow but I rarely use it - my default is a Pixel C which blows it away. But for browsing, email, YouTube etc it's fine.

 

[Ahkah]

Hi! I am on stock Android 5, I think this ROM looks like the best one to get a modern enough device for such oldie. Particularly interested in an updated browser.

Did anyone go stock 5 to asop 7? How is that experience? As snappy or you lose some?

Stock 5 was a pain the brain. This AOSP made the device usable again. But, however, Android 7 is also kind of outdated now.

 

[astrod]

This ROM works really smoothly, (thank you AndDiSa!) as long as one doesn't install gapps. I'm finding that gapps seems to slow it down almost making it too slow to use, even using Pico version.

Along those lines, has anyone gotten signature spoofing working w this ROM? I tried the nanodroid patcher to use microg, but spoofing never seemed to get enabled.

 

[Portgas D. Ace]

This ROM works really smoothly, (thank you AndDiSa!) as long as one doesn't install gapps. I'm finding that gapps seems to slow it down almost making it too slow to use, even using Pico version.

Along those lines, has anyone gotten signature spoofing working w this ROM? I tried the nanodroid patcher to use microg, but spoofing never seemed to get enabled.

I am running this ROM alongside with microG, installed via Nanodroid. Flashing the Nanodroid patcher via TWRP worked like a charm for me.

How-to (at least that is what I remembered):

Clean flashed the ROM, then rebooted to recovery again, then flashed the patcher. Took some time, but finished fine. Then rebooted into the system. Rebooted to recovery again, flashed Magisk and the corresponding Nanodroid Magisk modules for microG. That's it.