yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] fattox:
Just updated from Lineage 18 to this 19.1 but I can't install the Gapps anymore, I get Error 20 with the Pico Open Gapps and Error 1 with the BiTGApps.

I've already flashed la last sysrepart_1380_20 but I get an error here too...

I've followed then this guide: https://xdaforums.com/t/guide-tutorial-howto-google-nexus-7-2013-stock-to-android-12.4275457/ and repartitioned correctly..but I keep getting the same errors for the Gapps.

Probably I'm misunderstanding this part:

### If you get Error 70, don't be scared. Tablet doesn't know the System partition was increased.

### Go to Wipe > Advanced Wipe > Resize File System > Swipe to Resize and flash GApps.

How to fix this? Thanks
[Nexus 7 (2013) Android Development] matt.weatherford:
I upgraded both my kids' Nexus 7 2013 FLO to this new rom (I have about 10 of these tablets drifting around the house with various LineageOS ROM on them - Thank you @followmsi !

After several weeks of use, one of the N7's on this rom seems to lose the Wifi occasionally.... a reboot usually gets it working again but it is frustrating. The other N7 on the same ROM and version (20220818) does not seem to have this wifi issue. I am wondering if a LOGCAT or other debug info would be helpful and when to do it. LMK if I can provide something here

The sheer amazingness of this rom working on a tablet of this age ..... just wow

M@
[Nexus 7 (2013) Android Development] matt.weatherford:
I should add that I did a clean install from a completely wiped N7, not an upgrade from Lineage 18.1. N7 is the 16G version. I am also using GAPPS and g00gle parental controls which all seem to work fine as well.
[Nexus 7 (2013) Android Development] catish:
screen auto rotation not working in the lastest build, while it's working in offical LOS 18.1(sometimes not). and bt always come down with 'forced stop'.

i was wrong. now i go back offical los 18.1, but the rotation funtion still dead.
[Nexus 7 (2013) Android Development] shaunoleary:
I'm really happy - just tonight I repartitioned my ageing old N7 with a 4gb system partition and reinstalled LOS 19.1 - oh wow, what a difference!! Much, much more responsive. Before it was so darn slow, almost unusable.

Why didn't I think of doing this before?

If you're having slowness problems, do the sysrepart thang - it's easy with the script, and makes a humungous difference!
[Nexus 7 (2013) Android Development] PiKa5623:
When can I update 13
[Nexus 7 (2013) Android Development] PiKa5623:
我偶尔会使用屏幕旋转功能，但我没有发现这个问题

Mod translation via GT: I use screen rotation occasionally, but I don't see this problem
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 19.1 - September 2022

Hope to find some time to look into reported issues .. We may disable ZRAM again.

ZRAM seems to slow down system after certain time. Needs to be tested first ..

For Android 13 it's just too early to start - at least for me.

flo/deb devices require quite a lot of "legacy" patches.

Not sure if 13 will ever run on Nexus 7 2013 .. we will see.

lineage-19.1-20220920-UNOFFICIAL-flo.zip

lineage-19.1-20220920-UNOFFICIAL-deb.zip

Changes:

- Google security updates -> September 2022

- Patched system/netd to bring back Network traffic monitoring on older kernels

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes for Android 12

Pls check first page for known issues and more information.

Tested flo build with opengapps pico and Magisk 25.2 !

As SDK level increased to version 32 we have to use new gapps for Android 12L.

Pls check latest gapps builds here .. https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics

Thanks to @ipdev for the opengapps packages !

Enjoy Android 12L :p
[Nexus 7 (2013) Android Development] MikiGry:
Thank you for new build :)

Is clean flash obligatory or dirty flash over previous build will do ?

If dirty flash is ok, then which partintions will have to wiped ? (apart from cache, dalvik, system).
[Nexus 7 (2013) Android Development] ipdev:
If you are just looking to update from the August build to the September build..

You should be able to just flash the new build without wiping anything.

If you are using OpenGApps, the retention (addon.d) script will keep your OpenGApps install.

- It will backup your configuration before the system update, then restore it once the update is done.

- - Unless you wipe system before the install. 🙃

If you are using another GApps package..

- You will have to double check to see what procedure is required when updating the system (rom).

If you are using Magisk.

- You will have to patch the new boot image and flash it back to the device.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] PiKa5623:
I am looking forward to experiencing Android 13 on NEXUS7 2013
[Nexus 7 (2013) Android Development] AlesUlrych:
E1001: Failed to update system image.

Updater process ended with ERROR: 1

Error installing zip file /sdcard/Download/lineage-19.1-20220920-UNOFFICIAL-flo_064915.zip
[Nexus 7 (2013) Android Development] AlesUlrych:
but after this bug the previous build 19-20220818-UNOFFICIAL-flo installed without any problem, so I'm sticking with it.
[Nexus 7 (2013) Android Development] brewer75:
I performed a dirty update and had no problems with this new build.
[Nexus 7 (2013) Android Development] bednim:
Hi all, I have flashed repit from lanchon and it went well - partition seems to be resized but when I try to flash los19.1 I get this error (image) could anyone please help?

Thanks!
[Nexus 7 (2013) Android Development] itsAlphaFox:
Sub board/sub board cable might be acting up, very common on these tablets
[Nexus 7 (2013) Android Development] hanschke:
Please so a grouper release
[Nexus 7 (2013) Android Development] fattox:
I tried so many times and always end up with an issue installing the gapps. After so many hours lost, now I think I'm going to live without Google until a new solution comes up
[Nexus 7 (2013) Android Development] dogansan:
I overcame this issue by updating the apps in Google Play's page , then disabling Android Auto and enable it again. Now, the blue notification dissapeared
[Nexus 7 (2013) Android Development] Alyonas_boy:
Hopefully, there will be some speed improvements. I have to do a fstrim every time I want to use this tablet otherwise it's painfully slow on Android 12
[Nexus 7 (2013) Android Development] jojo33680:
Hi,

IS thaere a way to get dt2w please?

Thanks you
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 19.1 - October 2022

lineage-19.1-20221012-UNOFFICIAL-flo.zip

lineage-19.1-20221012-UNOFFICIAL-deb.zip

Changes:

- Google security updates -> October 2022

- Increased ZRAM size and swappiness

- Patched system/netd to bring back Network traffic monitoring on older kernels

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes for Android 12

Pls check first page for known issues and more information.

Tested flo build with opengapps pico and Magisk 25.2 !

As SDK level increased to version 32 we have to use new gapps for Android 12L.

Pls check latest gapps builds here .. https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics

Thanks to @ipdev for the opengapps packages !

Enjoy Android 12L :p
[Nexus 7 (2013) Android Development] AlesUlrych:
I have the same problem. Even Factory Reset didn't help me. Today I tried to install build lineage-19.1-20221012-UNOFFICIAL-flo.zip and with the same error.

The last working version for me is lineage-19.1-20220818-UNOFFICIAL-flo.zip

Anyone have any idea what might be causing this?
[Nexus 7 (2013) Android Development] AlesUlrych:
I have the same problem. Even Factory Reset didn't help me. Today I tried to install build lineage-19.1-20221012-UNOFFICIAL-flo.zip and with the same error.

The last working version for me is lineage-19.1-20220818-UNOFFICIAL-flo.zip

Anyone have any idea what might be causing this?

Thanks a lot for any advice or idea.
[Nexus 7 (2013) Android Development] ipdev:
It is supported in the kernel, you just have to activate it.

Using a kernel manager to enable DT2W.

Post 2,159 - Link

I have not check these settings in a while so, I am not sure if this is still accurate.

I use a Magisk module to enable it.

Post 3,339 - Link

Second half of the post.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] ipdev:
Save the TWRP log file and see what is causing the issue.

It could be a bad file transfer (corrupt file) so, double check it against the sha256sum.

Make sure the (re)partitioning worked.

Double check the partition sizes using the df command.

You will need to mount the system partition first using TWRP.

TWRP Home Screen -> Mount (select system) return to home.

Use adb shell or open a Terminal window to run the df command.

TWRP Home Screen -> Advanced -> Terminal

df -h

To close the terminal use the exit command.

Example(s) showing system size as 1.4G.

Formatted, no rom (system) installed.

Filesystem Size Used Available Use% Mounted on
tmpfs 903.7M 164.0K 903.5M 0% /dev
tmpfs 903.7M 24.0K 903.7M 0% /tmp
/dev/block/mmcblk0p30
12.2G 159.2M 12.1G 1% /data
/dev/block/mmcblk0p30
12.2G 159.2M 12.1G 1% /sdcard
/dev/block/mmcblk0p23
15.7M 4.1M 11.7M 26% /cache
/dev/block/mmcblk0p22
1.4G 25.7M 1.4G 2% /system

With rom (system) and GApps installed.

Filesystem Size Used Available Use% Mounted on
tmpfs 903.7M 164.0K 903.5M 0% /dev
tmpfs 903.7M 28.0K 903.7M 0% /tmp
/dev/block/platform/msm_sdcc.1/by-name/userdata
12.2G 713.4M 11.3G 6% /data
/dev/block/platform/msm_sdcc.1/by-name/userdata
12.2G 713.4M 11.3G 6% /sdcard
/dev/block/platform/msm_sdcc.1/by-name/cache
15.7M 4.2M 11.6M 27% /cache
/dev/block/platform/msm_sdcc.1/by-name/system
1.4G 1.3G 105.0M 93% /system_root
/dev/block/platform/msm_sdcc.1/by-name/system
1.4G 1.3G 105.0M 93% /system

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Alyonas_boy:
just updated to lineage-19.1-20221012-UNOFFICIAL-deb.zip and the performance is the same. Is there anyone running this Android 12 ROM and having good performance? Perhaps something is wrong with my Device? I have Android 10 Lineagos running on my kids Nexus 10's that are only Dual Core CPU's and they run super quick. And yet here is this 2013 Nexus 7 with a Quad core that grinds to a halt on Android 12.
[Nexus 7 (2013) Android Development] AlesUlrych:
Cheksum LineageOS on the computer is fine, I uploaded it to the tablet as usual via bluetooth, but I don't know how to verify that it is also fine on the tablet. However, I've never had a problem with it. As I said, the penultimate version works for me without any problems.

I am sending the log and a photo of the partitioned disk.
[Nexus 7 (2013) Android Development] ipdev:
Your picture of the df command, does not show system.

From the userdata and cache sizes it looks like your system should be 1.4G but...

If you mounted the system partition before running the df command, then your system partition is messed up.

Copy both the rom and checksum file to the device.

Use adb shell or the TWRP terminal and run the sha256sum command.

sha256sum -c NameOfFile.FileExtention.sha256sum

Example:

~ # cd /sdcard/
/sdcard # ls -la
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxrwx--- 3 root root 4096 Oct 15 23:56 .
drwxr-xr-x 24 root root 0 Oct 16 00:01 ..
drwxrwxrwx 2 root root 4096 Oct 14 00:51 TWRP
-rw-rw-r-- 1 root root 527290810 Oct 15 23:56 lineage-19.1-20221012-UNOFFICIAL-flo.zip
-rw-rw-r-- 1 root root 107 Oct 15 23:56 lineage-19.1-20221012-UNOFFICIAL-flo.zip.sha256sum
/sdcard # sha256sum -c lineage-19.1-20221012-UNOFFICIAL-flo.zip.sha256sum
lineage-19.1-20221012-UNOFFICIAL-flo.zip: OK
/sdcard #

Tab completion is available so you do not have to type it all in. 🙃

In the TWRP terminal..

The top line of the keyboard will have

Ctrl Esc Tab (and the left, down, up and right arrows).

sha256sum -c li[ICODE] press Tab and you will be at [ICODE]sha256sum -c lineage-19.1-20221012-UNOFFICIAL-flo.zip

so you just have to add the .sha256sum and press enter.

or just .s and press Tab again. ;)​

---

From your log file.

writing 1024 blocks of new data
writing 1024 blocks of new data
Decompression failed with BLOCK_LENGTH_2
missing 33144 bytes of new data
failed to execute command [new 2,92396,93420]
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 1

Should look more like this.

writing 1024 blocks of new data
writing 157 blocks of new data
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 1024 blocks
zeroing 742 blocks
wrote 294787 blocks; expected 294787

Looks like you wiped (formatted) partitions just before installing.

This has given errors in the past for me on some devices.

If I format and/or wipe partitions, I reboot back into recovery before installing a rom.

It was years ago and it has just become natural for me to reboot recovery after formatting or wiping partitions.​

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] fattox:
Hello @ipdev I've finally managed to install the latest pico Gapps, thanks to the great and patient work of @k23m.

BUT after booting for the first time to the Play Store and signing in, I keep getting "no connection" and "connection expired".

I even tried to install the WebView... thinking it was missing but it didn't help.

Do you have any idea on how to help?!

After so much work I would really succeed with it! Thank you for your help
[Nexus 7 (2013) Android Development] MikiGry:
I still havent updated the tablet from first relase of 19.1 because my usb port is acting up again :/

As propably everybody noticed, as days go tablet is getting slower and slower which requires to perform fstrim to make it usable again. Followmsi also mentioned that Swap make is slow down after some time for some reason.

Our EMMC chips aren"t the best. Using ZRAM in theory should give more RAM and better operation, but given the state of our memory chips - it creates more problems, as RAM becames (partially) slow as well.

So my theory is we should discorage the system for using swap and leave it as emergency or even disable it.

So to test this theory, right now im testing the second option - swappines set to 0. Lets see how it goes
[Nexus 7 (2013) Android Development] ipdev:
For the record.

ZRAM was removed from the flo builds.

LineageOS - [github] - [android_device_asus_flo] - commit

ZRAM was added back into the flox builds.

LineageOS - [github] - [android_device_asus_flox] - commit​

Flox builds are a bit different so, might work better using ZRAM? :unsure:

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] MikiGry:
Flox is just a repartitioned flo with special recovery which accepts flox build only aa far as I know.

II still testing how flo work with 0 ZRAM (and I/O read ahead buffer increased to 512kb -- don"t do that unless you want up warm your hands :p) with first build of LOS 19.1. So far:

- RAM is now usually filled almost to the brim - 30-60mb free (according to disk info) (up to 0,5GB with empty recent apps menu) incorrect ram usage calculation methode was used. 1gb free with recent apps menu empty, ~300mb before it starts to slow down and LMK kick in - this makes much more sense

- Multitasking is still possible

- PDF files are easier for the tablet to process (it takes less time to sharpen the image after zooming in or out)

- Youtube Vanced loads up video tubnails faster

- Brave browser lauches faster

- Low memory killer values may need some tuning (in starts to kick in when it"s less then ~300mb free, i thing we can fill the ram a little more)

- It takes longer for Google keyboard to show up (or maybe it was its latest update which made it even heaver ?)

@ipdev

Unfortunately I had to end the test. It seems that 2gb of ram is not enough for stable operations. It looks like apps became much more RAM hungry lately or there are some RAM leaks. Google keyboard + official xda app (it can eat up to 0,5GB of RAM !!!) or a youtube notification were enough to make tablet unusable :/

New approach - back to 512mb swap (default value for the first build) but with decreased swappiness value (to make sure system uses swap as a emergency option, rather then just free extra ram)
[Nexus 7 (2013) Android Development] ipdev:
Might be a little more different. ;)

The (re)partitioning includes creating and using a separate vendor partition.

Following UA's approach. Not sure if flox vendor is stock or includes modifications.​

Official flox builds are enforcing.

---

When flox and followmsi's flo branch where mostly inline, I "borrowed" some SELinux permissions from flox.

Still had issues when I tested enforcing flo builds. 🙃

Oddities with camera come to mind along with a few other things that I never figured out.​

Followmsi's kernel also includes some extras that are not in flox/debx kernel.

Debx was never released for some reason, never looked into why.

Followmsi reverted vmalloc back to stock value.

- [github] - [android_device_asus_flo] - commit

I questioned vmalloc for a while and was running test builds with it reverted.

I did not see an improvement by keeping it or a regression by removing it on Android 6 (API 23) and above.

Removing it seemed to have a positive effect ??

I asked a few times (in different threads) if there was any reason to keep it and no one answered. 🙃

The last time I asked ??

[ROM][OFFICIAL] LineageOS 17.1 weeklies for Nexus 7 2013 (flox) - [xdaThread] - Post # 221​

---

Looking forward to your experience and findings. 🙂 👍

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] MikiGry:
So to go from flox to flo you would need to go back to stock partition layout and repartition again ?

Interesting. Maybe in the long run bigger value started causing issues ? Not sure. Best solution would be to compile just the kernel with different vmalloc setting (increased, stock, disabled) and ask community to test all 3 kernels. Bigger test group may notice some differences or confirm a placebo effect
[Nexus 7 (2013) Android Development] ipdev:
It has been a while since I looked into the partitioning.

I remember the free space above system is used for vendor but, I do not remember how they rearrange partitions.

So it would be the safest to revert to stock partition lay out before using the UA/flox script.

You would then have to use the flox lineage recovery or UA's TWRP recovery.

Since followmsi's l18 and newer builds are running with the stock vmalloc value..

Seems to be a large test group and no one has mentioned a regression. 🙃

I would have to find my notes from testing but, if you drop it too low or increase it too high the device becomes unusable.

Memory errors across the board.

Found one of my replies from a conversation about it.

Spoiler content hidden.

Note: To explain my comment at the end, the 100M is now free ram instead of being reserved by vmalloc.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] MikiGry:
@followmsi

Little followup on this one. Today I discovered that I had Bluetooth gebeldorch enabled in developer setting. After disabling it it kinda started to work. Now it does something like that:

BT turns on for a split second (according to statusbar toggle and setting) amd turns off again. It does that a few times (sometimes giving "Bluetooth has stopped error dialog" mid way) and finally turns on and stays on. I haven"t tried connecting with any device or sending files yet.

Logcat revealed a cycle:

1.Errors

2. BT has died

3. Scheduling a bluetooth restart

4. Back to the first point
[Nexus 7 (2013) Android Development] fattox:
It worked! The very last part was the solution I didn't know!

Thank you sooooo much
[Nexus 7 (2013) Android Development] fattox:
Do you have any workaround also for making work the Google Assistant? It doesn't work when calling for it and the setting says "it's not available for this device"
[Nexus 7 (2013) Android Development] itsAlphaFox:
Does anyone know if it is possible to get an overclock working on this ROM?
[Nexus 7 (2013) Android Development] bernascoginger:
I tried installing the new OS on my NEXUS 7 2013(dep). I had the message " UPDATER PROCESS ENDED WITH ERROR: 1". i have attached a copy of screenshot to see details. Please help me to complete installation
[Nexus 7 (2013) Android Development] bernascoginger:
I downloaded and tried installing the new Lineage OS 19 on my NEXUS 7 2013(dep). I had the message "UPDATE PROCESS ENDED WITH ERROR:1". i have attached screen shot below. Please help me to complete install
[Nexus 7 (2013) Android Development] AlesUlrych:
I have the same problem with Flo, and so far I have not been able to solve it. I wrote about it on the previous page. The only thing that works for me is reverting to version lineage-19.1-20220818-UNOFFICIAL-flo.zip

All the advice ipdev gave me hasn't helped so far.
[Nexus 7 (2013) Android Development] AlesUlrych:
Unfortunately, I tried your tips, but I didn't make any progress. So I went back to lineage-19.1-20220818-UNOFFICIAL-flo.zi
[Nexus 7 (2013) Android Development] bernascoginger:
i am on android 4.4.4. pop up message to download and install android 5.0.2 keeps on appearing on my screen. after downloading, the installation goes on all day and never gets to completion. is there a higher an available version i can download and install on my device?
[Nexus 7 (2013) Android Development] CityKev:
Might be a sledgehammer to crack a nut but this tool has been very useful for me. Install the persist fix using TWRP before then using the Restock tool to get you to 6.0.1.

Edit: it would help if I included the link 😄

[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix

RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...

xdaforums.com
[Nexus 7 (2013) Android Development] DVDK94:
I had the same problem (error 1 when installing `lineage-19.1-20221012-UNOFFICIAL-flo.zip`), but I have finally solved it. After downgrading from the official TWRP 3.7 build to the TWRP build 3.6.2 from @followmsi the installation was successful.

@bednim @AlesUlrych @bernascoginger
[Nexus 7 (2013) Android Development] bernascoginger:
i used TWRP build 3.6.0_9-1 and it failed. can you send me link to download TWRP 3.7 and a more lower version to try
[Nexus 7 (2013) Android Development] DVDK94:
Official TWRP builds for flo: https://dl.twrp.me/flo/

Official TWRP builds for deb: https://dl.twrp.me/deb/

TWRP build by @followmsi for flo and deb: https://drive.google.com/drive/folders/18JCSbs0IglAWR2YnV5lI2Eni_ZQ6AyPl
[Nexus 7 (2013) Android Development] AlesUlrych:
But I use TWRP 3.6.2 from followmsi.

I've gone back to the last working build and will stick with that for now. Why the new ones aren't working I don't know, I'll stick with the last working one for now and possibly try the new ones to see if any of them work again.
[Nexus 7 (2013) Android Development] MikiGry:
Possible solution for people who can"t clean install 20221012 build but have zero problems with older ones.

Install older one and dirty flash over it to the newest one
[Nexus 7 (2013) Android Development] comatoseEnigma:
this wont work for mako nexus 4 would it?
[Nexus 7 (2013) Android Development] curiousde2002:
Hi guys anybody having performance problems?

My Deb is lagging most of the time, so that it's hardly usable.

What I did:

Coming from LOS 17.1

I had run ipdev's repit script with system wipe,

Rebooted back into recovery

Wiped data, system, dalvik and cache

Rebooted back into recovery

Flashed `lineage-19.1-20221012-UNOFFICIAL-deb.zip` and open gapps arm pico

Boot into system and did initial setup

Rebooted back into recovery and flashed magisk 25.2

All these actions worked fine, no errors.

I tried another install but only with system, dalvik and cache wipe, but no improvement.

I'll do another clean install if I don't get any other suggestion from you:cool:

Thank you very much in advance !