yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] dooderooni:
cliff, download and install the Nexus Root Toolkit and you can do everything you need to do with one tool.

If you hover over Nexus Root Toolkit v2.1.9 in the grey menu bar of the site linked above there are multiple video tutorials linked to show you exactly what you need to do.

Have fun.
[Nexus 7 Android Development] cliffgamerz:
Thanks a lot you helped me a lot.
[Nexus 7 Android Development] pilsener69:
Man, you are awesome.

Regards,
[Nexus 7 Android Development] elijahblake:
Does this ROM have OTA updates or do you have to flash manually? Looking to install this for my Dad and trying to see if he can update it himself.

Thanks Dev for keeping this old device alive! :good:
[Nexus 7 Android Development] cliffgamerz:
Never been happy with my nexus 7 ever like i am after installing this today, was worth the trouble. thanks to the dev and team.
[Nexus 7 Android Development] jorgesedavi:
Thanks to AndDiSa for this awesome ROM. Using it as a daily Rom.

Only one thing, could you update the instructions for updating the rom? After installing the main zip you have to power off the device, enter the recovery again, and then install the gapps and supersu zips. If you install the gapps just after flashing the rom, they just won't be installed. There are few people reporting this and installing them by weird methods instead of simply reboot to recovery after flashing rom!

Thanks another time to the dev, would you look after the battery drain? It's not a major problem but there is.
[Nexus 7 Android Development] robgriff:
When I did it, Gapps failed when I loaded all zips at once in twrp (it said Gapps was the wrong version) but when I quit to the main twrp screen and loaded Gapps on its own it was fine
[Nexus 7 Android Development] AndDiSa:
[MENTION=5252990]jorgesedavi[/MENTION] I am not having any battery drain on my device, in contrary my device never used so view energy as it it doing currently especially when laying around. The only thing I can imagine: when you update to a new version of the ROM all applications are being optimized in background which may lead to a higher energy consumption.

If you notice a battery drain please have a look to the energy screen to identify which app / component is using much energy. Also a logcat could help me to see any anomaly.
[Nexus 7 Android Development] robgriff:
I've got no battery drain
[Nexus 7 Android Development] Codster314:
Ah yes. It works because u are running Magisk. It is hiding something which FEH sees as non-official in the rom (plus ur root). FEH works for me too if I install Magisk.

It's when Magisk is not installed is what we are trying to figure out why FEH will crash on this AOSP ROM, but not the UA ROM.

Since the Vanilla ROM passes safetynet, device certified, etc. It's not that. But yea I wonder what else Magisk dose to "hide root". One of those other small things it does is something this vanilla ROM has. Like userdebug build or something like that. I wonder how many things Magisk hide does...
[Nexus 7 Android Development] ManoBros:
just flashed,

lol ,

i install Magisk 18.1 at install,

reflash all again...
[Nexus 7 Android Development] tilapia_user:
Hello community,

first of all thanks for this great rom. I'm really happy that such an old device can run so smoothly and fast due to your constant work and improvements!

I just have a very tiny problem. Just like the user TureX described, the booting process takes also very long for me (stays with the "Google" screen for a very long period). Afterwards there are no performance issues. I'm running the bootloader in version 4.23 and no magisk. Does anyone of have an idea what the reason could be? I would be very happy, if anyone could give me a hint.

Many thanks in advance!
[Nexus 7 Android Development] Ahkah:
You could connect your device to a computer and run "adb logcat" during restart. This will tell you tons of information part of which might be helpful to find the reason for the delay.

On the other hand the Google screen is not drawn by the starting Android, but by the boot loader, so probably the log will unfortunately start after the delay, i.e. when the Linux kernel and the first services have been started.

Note that the Google screen lasts much longer with the newer boot loader than with the old one; this is normal and there is no need to worry.
[Nexus 7 Android Development] tilapia_user:
Hello Ahkah,

the reason why I was worried, that the probleme came suddenly with one of the updates from last year. I had the problem also with an older bootloader, I upgraded it yesterday to figure out, if that could solve the problem. I tried to do the adb logcat, but I'm only able to connect when it's fully booted, does it still help? Or is there any other way to generate a loog of the boot loader?
[Nexus 7 Android Development] AndDiSa:
[MENTION=9731851]tilapia_user[/MENTION] when I am looking at the dmesg (kernel messages) I can see that normally it takes up to 30 sec until the kernel is initialized fully. After that the Android system is starting up, i.e. the boot logo changes from Google to Android. In addition you need to consider the time it takes to read the kernel from the file system, decompress it and finally start it. The increased startup time may be related to the compression algorithm which is used. I changed it to xz compression algorithm which provides a better compression but most likely takes a bit longer to decompress.
[Nexus 7 Android Development] tilapia_user:
I just measured the time, my Nexus 7 takes about 170 sec to change from the Google to the Android logo. Is this comparable to the booting time of your devices?
[Nexus 7 Android Development] AndDiSa:
I do have exactly 55 sec on my Grouper until the Android logo, but this might also depend on whether file system check is needed or not ...
[Nexus 7 Android Development] Nexus7_tilapia:
Hi all

I've heard Google replaced Dalvik with ART Virtual Machine since Lollipop; then why we do NOT have 'ART-cache' directory instead of 'Dalvik-cache' in /data directory in our device?

Best wishes
[Nexus 7 Android Development] tilapia_user:
Hmm I would also estimate that it took around this in former times for me. Is there any log etc. I can provide to determine, if there is any problem? Many thanks in advance!!
[Nexus 7 Android Development] AndDiSa:
[MENTION=8618734]Nexus7_tilapia[/MENTION] most likely only Google can answer that question
[Nexus 7 Android Development] AndDiSa:
[MENTION=9731851]tilapia_user[/MENTION] you might have a look at dmesg output directly after booting ... but here you can see only if there are issues after starting the kernel. If there are issues in loading / decompressing / ... you will not be able to see them.
[Nexus 7 Android Development] OlliWi:
Seems to me quite long. I have 35 sec to the android logo on my tilapia.
[Nexus 7 Android Development] BLewis4050:
pixz in place of xz?

Is it possible to replace xz with pixz, as the latter is multi-threaded for decompression as well as compression?
[Nexus 7 Android Development] AndDiSa:
2019/02/05 - release for Grouper and Tilapia uploaded

I've just uploded the latest version of the ROM for Grouper and Tilapia. As always the Android security issues listed in the latest Android Security Bulletin are patched in this ROM.

Beside that once again I've worked much on the kernel side. Some features are added (multiple binder devices, alarm timer device, ...) and some bugs have been fixed.

I am still working together with [MENTION=8559165]OlliWi[/MENTION] on the slow charging issue which occurs from time to time. Even if I was able to get charging currents up to 1500mA while the device was connected to a charger, we still have the impression that the cable / charger detection needs to be improved. We are on it ...

Those of you who are familiar with the installation process of the ROM can download directly from here, otherwise please first read the instructions in the OP

7.1.2 Grouper OTA-Package (Build 20190209) (md5: 885e601a06a2104628a1e450b73f3a18)

7.1.2 Tilapia OTA-Package (Build 20190209) (md5: 8e4c0e1955ecc0bb65a51582bb01f779)

And finally as always: flash on your own risk ... ;)
[Nexus 7 Android Development] akashkyh:
Unable to download Gapps from https://opengapps.org/

Can any1 help??

---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------

Unable to download Gapps from https://opengapps.org/

Can any1 help??
[Nexus 7 Android Development] Portgas D. Ace:
Seems that opengapps.org has some issues today. Wait until they have sorted it out.
[Nexus 7 Android Development] AndDiSa:
If you have an older package available this will work, too, as it will be updated immediately by Google.
[Nexus 7 Android Development] mikeataol:
Just noting for those who may not know.

If you get "Setup wizard has stopped..." while starting up the first time, a fix that works on this and I have seen on other roms is to tap "open program again" and then quickly swipe down from the quick settings area , and then turn on wifi.

thank you AndDiSa for your work.
[Nexus 7 Android Development] rahimali:
I flashed my phone last week so this (open_gapps-arm-7.1-pico-20190203.zip) is the latest one I've got :)
[Nexus 7 Android Development] laugeek57:
Good job !!! :)
[Nexus 7 Android Development] OlliWi:
It maybe helpful if some of you can provide the configuration settings of the smb347 charger.

Its register settings are stored in /sys/class/i2c-dev/i2c-4/device/4-006a/reg_status

This is from my smb347, loading with 9-10 W, measured at the wall socket. (~1200 mA charging current for the battery):

SMB34x Configuration Registers Detail

==================

Reg00h:	0x9c

Reg01h:	0x16

Reg02h:	0x93

Reg03h:	0xe3

Reg04h:	0x0e

Reg05h:	0x3e

Reg06h:	0x75

Reg07h:	0xe6

Reg08h:	0x08

Reg09h:	0x25

Reg0ah:	0xbe

Reg0bh:	0xa5

Reg0ch:	0x04

Reg0dh:	0x14

Reg0eh:	0xd5

Reg30h:	0x00

Reg31h:	0x00

Reg35h:	0x00

Reg36h:	0x01

Reg37h:	0x00

Reg38h:	0x50

Reg39h:	0x10

Reg3ah:	0x03

Reg3bh:	0xa3

Reg3ch:	0x3c

Reg3dh:	0x05

Reg3eh:	0x0a

Reg3fh:	0x96
[Nexus 7 Android Development] mikefive:
SMB34x Configuration Registers Detail

==================

Reg00h: 0xfc

Reg01h: 0x76

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x71

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x02

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x0a

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x03

Reg3bh: 0xa3

Reg3ch: 0x3f

Reg3dh: 0x05

Reg3eh: 0x0a

Reg3fh: 0x92

..charging with 0.45-0.9mA
[Nexus 7 Android Development] pincher65:
SMB34x Configuration Registers Detail

==================

Reg00h:	0xfc

Reg01h:	0x73

Reg02h:	0x93

Reg03h:	0xe3

Reg04h:	0x0e

Reg05h:	0x1e

Reg06h:	0x71

Reg07h:	0xe6

Reg08h:	0x08

Reg09h:	0x25

Reg0ah:	0xbe

Reg0bh:	0xa5

Reg0ch:	0x00

Reg0dh:	0x14

Reg0eh:	0xd5

Reg30h:	0x02

Reg31h:	0x00

Reg35h:	0x00

Reg36h:	0x00

Reg37h:	0x2a

Reg38h:	0x00

Reg39h:	0x11

Reg3ah:	0x02

Reg3bh:	0x23

Reg3ch:	0x1f

Reg3dh:	0x00

Reg3eh:	0x00

Reg3fh:	0x00
[Nexus 7 Android Development] lotte67890:
SMB34x Configuration Registers Detail

==================

Reg00h: 0xfc

Reg01h: 0x76

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x71

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x02

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x00

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x01

Reg3bh: 0xa3

Reg3ch: 0x3f

Reg3dh: 0x05

Reg3eh: 0x0a

Reg3fh: 0x93
[Nexus 7 Android Development] OlliWi:
Thanks to all for your contribution.

[MENTION=2188693]AndDiSa[/MENTION]

The register setting above is the first issue.

"0xfc" commands the smb347 to charge (fast charge current) with its maximum capability of 2500 mA and that cannot be handled by our Nexus.

We´re limited to 1800 mA on the input side. I currently don´t know how the smb347 will behave under such circumstances.

A value of "0x9c" corresponds to a (fast) charge current of 1800 mA which works quite well for me.

/update:

Reg01h value of 0x76 is fine. This register contains the input current limit, which is 2000 mA (1st value: 7) if connected to the dock and 1800 mA (2nd value: 6) if connected to a USB cable.
[Nexus 7 Android Development] OlliWi:
USE THE FOLLOING PROCEDURE ON YOUR OWN RISK!

You need:

1) a rooted device

2) busybox

3) some terminal emulator

To change the register values of the smb347 charger we can write directly to these registers using i2cset (which is included in busybox)

https://linux.die.net/man/8/i2cset

a) disconnect your Nexus from USB/DOCK (battery should not be empty of course)

b) open a terminal and execute the following commands:

i2cset -f -y 4 0x6A 0x30 0x80

i2cset -f -y 4 0x6A 0x00 0x9C

explanation of parameters:

-f: forces access to i2c bus because it is used by the driver and you will get a "device or resource busy" error

-y: don´t use interactive mode

4: number of the i2c bus (the one with the smb347 connected, tegra3 has four i2c busses)

0x6A: address of the smb347 chip on the i2c bus

0x30: command register "A" of the smb347, this needs to be written with 0x80 to get write access to other registers

0x00: charge current register of the smb347, containing values for fastcharge current, precharge current and termination current. Value 9C means: 1800 mA fastcharge, 250 mA precharge, 200 mA termination.

Afterwards, connect Nexus to charger and and post register content as you did above.

You can check charging current with:

cat /proc/kmsg | grep current

Good luck.

Attachment: decoding of register 0x00 (charge current) values
[Nexus 7 Android Development] DJStatikVX:
Expecting some random reboots since updated to latest build. Also, power button seems less sensitive, sometimes it takes 3 or even 4 attempts for turning on the device screen.
[Nexus 7 Android Development] OlliWi:
Your automatic input current limit (AICL) was adjusted to 700 mA

Your automatic input current limit (AICL) was adjusted to 900 mA.

Reg3fh is a status register, it is read-only.

Connected to an AC-USB-Adapter, you should get either

0x95: 1500 mA

0x96: 1800 mA

As fast charging will speed up the degradation of a battery I used a charger from an Amazon Fire tablet (rated, 5 W - 1 A) yesterday to have my Nexus charging slower overnight.;)

This resulted in Reg3Fh

0x94: 1200 mA
[Nexus 7 Android Development] AndDiSa:
I noticed this behaviour when there is much load / many apps swapped out into ZRAM. When you then activate the system tries to clean up memory which takes time and is blocking the device. Most of the time you will also notice that the resource-provider was killed to free up some memory. Generally I had this behaviour only once after a new installation. Later on the system woke up always almost immediately but I'll keep it in mind. Thank you for reporting.
[Nexus 7 Android Development] DragonTome:
I haven't had as much of a delay on waking via power buttion, but I have experienced a number of reboots while the tablet sits, unused on my desk. It gets my attention because I see the blank display change to the Google boot screen.
[Nexus 7 Android Development] OlliWi:
As always: please provide logfiles

the kernel logfile containing the reason for the crash is /proc/last_kmsg
[Nexus 7 Android Development] guilou123:
Thank you.

I made a totally clean install* and had this setup wizard crash and reboot too.

[MENTION=2188693]AndDiSa[/MENTION] Is there a possibility to activate wifi by default at first start in the next ROM to avoid this setup wizard problem ?

*had this ROM in a one year old version. I boot in recovery, format data + cache + dalvik + system + internal memory, install last ROM with adb sideload, wipe cache and dalvik, reboot into recovery, install picogapps with adb sideload, wipe cache and dalvik and reboot sytem

Just to be sure. It can't be cleaner right ? ^^
[Nexus 7 Android Development] TureX:
Hi, i notice the same problem, i need to press many time the power button. Some time i get random reboot. Sorry for My bad English
[Nexus 7 Android Development] AndDiSa:
[MENTION=3777227]TureX[/MENTION] pressing several times the power button when the device is in that stage sometimes leads to a reboot (you can check afterwards by looking as /proc/last_kmsg). You will see that there is no kernel crash, but a normal shutdown / reboot ...
[Nexus 7 Android Development] TureX:
This is not The case, i didn't get reboot after press
[Nexus 7 Android Development] lotte67890:
Thanks a lot!!! First let me tell you that my last "SMB34x Configuration Registers Detail" was taken while the Nexus was in charge mode. When in Battery mode Reg3Fh = 0x00.

Anyway I did as you suggested and noticed that Reg3Fh switched to 0x84 after approximately 30 minutes, then stepped up to 0x91 and now after nearly 3 hours of charging is set to 0x96 as you predicted.

Anyway, I never saw more than 830mA in /proc/kmsg, mostly between 500-700mA... :confused:

Maybe it needs another cycle... If anything behaves different then, I will let you know.

Lotte
[Nexus 7 Android Development] OlliWi:
I know;) The automatic input current limit (AICL) is always set to 300 mA (0x00) when not connected to a charger.

The second number is the AICL that the smb347 charger has chosen depending on the capabilities of your power source.

The bitmap representation of this numbers:

0	0	0	0	300 mA

0	0	0	1	500 mA

0	0	1	0	700 mA

0	0	1	1	900 mA

0	1	0	0	1200 mA

0	1	0	1	1500 mA

0	1	1	0	1800 mA

0	1	1	1	2000 mA

1	0	0	0	2200 mA

1	0	0	1	2500 mA

I still have to find out what´s the meaning of the first number.....

It is 0 (0000) when not connected, it is 8 (1000) if you you connect to a charger then it will switch later -> it is 9 (1001) if connected to a AC charger, it is C (1100) if connected to a USB2 port. I´ve never seen any other values.

Would be nice if someone could provide values when connected to a USB3 port and when charging in a docking station (i don´t have one).

Please post the register_status file when connected to a charger.
[Nexus 7 Android Development] AndDiSa:
In that case a logcat and/or /proc/last_kmsg would be useful to be able to analyze the issue.
[Nexus 7 Android Development] CamoGeko:
For me personally the new build has been running fine so far, I'm having none of the issues other people are mentioning. It's super amazing to see that this tablet can still do things after 7 years existence!

Thank you for building and maintaining this ROM for us! ☺️
[Nexus 7 Android Development] TureX:
Thank you i will do if it will happen again, i think was a magisk module :confused:
[Nexus 7 Android Development] DragonTome:
While my Nexus was charging, an unprompted restart occurred. The display was off and the device was not doing anything specific, that I am aware of. I was able to capture out a last_kmsg, after the restart. It is attached here.
[Nexus 7 Android Development] AndDiSa:
[27442.259712] Freezing user space processes ...
[27442.271016] bq27541_get_psp charge_design = 4400000 uAh
[27442.272030] bq27541_get_psp energy_now = 12408000 uWh
[27442.274456] bq27541_get_psp temperature= 270 (0.1¢XC)
[27442.379247] smb347_charger: [smb347_config_thermal_charging] temp=27
[27442.381670] smb347_charger: [smb347_config_thermal_charging] Bypass charger enable
[27442.408800] (elapsed 0.148 seconds) done.
[27442.409142] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
[27442.412373] PM: Entering mem sleep
[27442.413363] [mmc]:mmc_queue_suspend:354 mmc0: blk_stop_queue start
[27442.413488] [mmc]:mmc_queue_suspend:354 mmc0: blk_stop_queue start
[27442.413699] [mmc]:mmc_queue_suspend:354 mmc0: blk_stop_queue start
[27442.429244] vi vi: suspend status: 0
[27442.429378] isp isp: suspend status: 0
[27442.429508] gr2d gr2d: suspend status: 0
[27442.429740] gr3d gr3d02: suspend status: 0
[27442.429870] mpe mpe02: suspend status: 0
[27442.430036] alarmtimer alarmtimer: Nearest alarm wakeup time < 2sec, avoiding suspend
[27442.430272] pm_op(): platform_pm_suspend+0x0/0x54 returns -16
[27442.430392] PM: Device alarmtimer failed to suspend: error -16
[27451.185430] wake lock wlan_rx_wake, expired

No errors detected

Hmm ... doesn't look like a kernel issue as there was no exeption / error. Probably a soft reboot (e.g. Android reboot only). In those cases logcat would be more helpful than the kernel messages.
[Nexus 7 Android Development] DragonTome:
Hmm...OK. I'm not sure the difference between boot types. This boot returns all the way back to the Google screen, not the Android 'splash' (which appears later). I haven't been keeping the tablet connected to a machine up to this point. What is the best method for dumping a logcat in this situation? Right after the reboot? or attempt during the reboot?
[Nexus 7 Android Development] shaggyskunk:
[MENTION=2188693]AndDiSa[/MENTION] I've got a question - How can you sideload the Rom if you Flashed the update & it failed to install - I wasn't paying attention & the device booted without any os installed? I think that my download was corrupt & unfortunately there's no TWRP backup - It's entirely my fault..

Thanks
[Nexus 7 Android Development] Sam Nakamura:
Can't you "fastboot boot (or flash) twrp.img" and re-flash the ROM? Not sure why you would want to sideload it...
[Nexus 7 Android Development] AndDiSa:
[MENTION=4222375]DragonTome[/MENTION] This sounds strange to me as a "Google-Logo" re-boot is normally caused by a kernel issue, e.g. segmentation fault in a driver / paging fault / etc. and thus you should see a stacktrace in the /proc/last_kmsg, too. An "Android-Logo" re-boot is causes by Android-System issues, e.g. watchdogs detecting some issue and killing the system process, ... In those cases you most likely will not see anything in the kernel log (/proc/last_kmsg) as the kernel is not affected and continues to run while Andoid is booting again. While it cannot be seen directly in the kernel log you can still see processes beeing killed / restarted / ... in the system log (logcat).
[Nexus 7 Android Development] AndDiSa:
I second that, it's the easiest way in my opinion. If you are lucky you will still have all your data ... ;)
[Nexus 7 Android Development] shaggyskunk:
The issue is that I don't have a valid zip installed on the device - The one that I downloaded was corrupt & I had Factory Reset & Wiped Data before I had attempted to Flash the zip (corrupt).

I'm not sure if I'm explaining it clearly or if I'm understanding your suggestion properly.

At this point I downloaded the zip for the Rom to my computer - But there isn't a Flashable zip on the device.

While I'm extremely familiar with Samsung devices I'm not that familiar with Nexus & it's been a number of years since I Rooted my N7...
[Nexus 7 Android Development] AndDiSa:
[MENTION=4351374]shaggyskunk[/MENTION] I see, i.e. you do not have the zip installed on /sdcard but also that is no problem, you can do the following steps having your device connected via USB cable to your PC:

- fastboot boot twrp-3.2.3-0-grouper.img

- adb push aosp_grouper-7.1.2-ota-eng-20190209.ds.zip /sdcard

and then you can select the zip wthin TWRP and you can flash it as you are used to do.