yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] jmye620:
Sorry if this has already been asked, but where are gapps that actually work? ROM installs fine, but bitGAPPS and other ARM packages I have tried don't install successfully. Let me know, thank you.
[Nexus 7 (2013) Android Development] ipdev:
OpenGApps 12L pico.

I might be a little bias though. 🙃

Test builds are avalable on gDrive.

[gDrive] - [testGapps] - Link

You can find out about the test builds in the OpenGApps xda thread.

[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices

- Post # 7,259

- Post # 7,319

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Tatsh:
Hi dev, im hoping that adding 1.6Ghz and 1.7Ghz Overclock to elementalX kernel

1.5Ghz is great but 1.7Ghz seems like a good balance between battery and performance

*Tested 1.7Ghz on android 7, it works pretty amazing btw
[Nexus 7 (2013) Android Development] Vacant9767:
I'm having a bluetooth pairing issues and I'm not quire sure where to go. When I pair it brings up the device pin screen but when I go to input the pin it is like the keyboard is missing. If I use an external keyboard to type the pin the pairing fails. Thanks for any guidance.
[Nexus 7 (2013) Android Development] Anatolij:
Gapps (pico) do not work on two planets, according to the recommendations, many have tried, not one has not been installed, Error: 20. I re-partitioned the system 1380_20.zip, what will be the proposals
[Nexus 7 (2013) Android Development] Hikikomorikruge:
The 1380mb system partition is too small for the Lineage 19.1 ROM + GApps. REPIT: for Nexus 7 (2013) can give a 1480mb system partition which is large enough for both while maintaining the partition structure. However REPIT requires starting with stock partition sizes.

Restoring the original partitions with sysrepartundo.zip might work, or using RESTOCK to set your tablet mostly back to stock.

It didn't work for me and left the vendor partition for some reason. I had to delete the vendor and userdata partitions with parted, then combine the spans into a larger userdata partion before REPIT would do the rest of the work for me. This repartition guide using parted has a link to parted.

Then I was able to flash 19.1, ipdev's OpenGApps pico build, and Magisk 25.1.
[Nexus 7 (2013) Android Development] Anatolij:
<Moderator Edit>: Original English posts of quote, and English translation of this post added.

I got out of the situation, after an unsuccessful repartition of the system partition, I got (cannot mount-DATA) applied the sysrepart-flox.zip script, which restored the system partition and repartitioned it to 1467 MB, this is enough for Gaaps pico . Everything for the firmware is here.

Original:

Вышел из ситуации, после неудачной переразбивки системного раздела получил (cannot mount-DATA) применил скрипт sysrepart-flox.zip, который восстановил системный раздел и переразбил его на 1467 МБ, этого достаточно для Gaaps pico . Все для прошивки здесь.

735.69 MB folder on MEGA

6 files

mega.nz
[Nexus 7 (2013) Android Development] dickxabre:
i am using lineageos 19-20220515 and want to update to 19.1

However, below erorr code show when install gapp

BitGapp R45---error 1

openGapps Nano 12-20220311 - error 20

what can i do ?

thank
[Nexus 7 (2013) Android Development] theistus:
nice work man. Only issues i seem to be having are that bluetooth isn;t working and "hey google" can;t seem to be enabled. Might try a wipe and start fresh see if that fixes it.
[Nexus 7 (2013) Android Development] Anatolij:
735.69 MB folder on MEGA

6 files

mega.nz

<Moderator Edit>: Original English posts of quotes, and English translation of this post added.

everything you need is there and works, use the script to partition the 1476mb system partition, firmware, gapps, success.

Original:

все что нужно есть и работает, используйте скрипт для разбивки системного раздела 1476мб, прошивка, гаппсы, успехов.
[Nexus 7 (2013) Android Development] matt.weatherford:
Dear @followmsi -

This is great to hear - I hope you have a great vacation and relaxing / fun time on your holiday break. We, the community, greatly appreciate your contributions to the Nexus 7, Pixel C, and Nexus 10 LineageOS builds and whatever you can do to recharge your (personal, human) battery will benefit us all

Take good care
[Nexus 7 (2013) Android Development] shaunoleary:
Hi all, just thought I'd chime in on this ROM.

I've been running this LOS 19.1 on my trusty old N7 - and overall, it runs very well. However, I find the device can get very, very slow if I don't reboot it every half a day or so. I'm talking, apps can take a minute or more to open, the whole OS slows to a crawl, almost comatose. Rebooting (often having to do this by holding down the power button) was the only way to resolve it.

One thing I found helped was setting the Background Process Limit (under Apps in Developer Options) to about 3 or 4 made the device much more responsive. Has anyone else had this problem, any ideas/suggestions?
[Nexus 7 (2013) Android Development] DaCl88:
Yes with the last build I have the same problem.
[Nexus 7 (2013) Android Development] doxts:
No, but maybe factory reset will help.
[Nexus 7 (2013) Android Development] techack:
Great work @followmsi

Can you pls put up instructions on how to upgrade from March build of this ROM?​

Thanks!!
[Nexus 7 (2013) Android Development] kozmo2k4:
Use Mull (on F-Droid), it is a Firefox fork, stripped off all telemetry. It runs smoother, too.
[Nexus 7 (2013) Android Development] Mr.Conkel:
Bromite is also good, can be a bit slower on this Tab though as its just as heavy as chrome
[Nexus 7 (2013) Android Development] Alyonas_boy:
I have been running this for over a month now and the slowness is getting to me. Very frustrating. Even from a fresh boot it is extremely slow. If I run fstrim it will speed up for awhile and then go to a crawl again. Strating to think I need to go to Android 10 instead. My kids have Nexus 10's. Dual cores with 2gb ram and Android 10. Runs beautifully. Way way faster than my nexus 7 2013
[Nexus 7 (2013) Android Development] underflash:
WIth https://xdaforums.com/t/app-4-1-hebf-optimizer-battery-saver-and-root-toolbox-2021-05-31.3401341 you can set custom fstrim interval, e.g. every 8 hours.
[Nexus 7 (2013) Android Development] klugec:
Hi,

What kernel do I need for otg + charging at the same time?

Thank you
[Nexus 7 (2013) Android Development] isenbart:
I have the same issue with the USB port but repartitioned my Nexus 7 before it broke. So I'm very happy followmsi provides this rom and I can keep my tablet up to date. I also would not know how to transfer a rom zip on the device after wiping.
[Nexus 7 (2013) Android Development] poo706:
In my humble opinion, 17.1 runs much smoother on flo than 18.1 or 19.1. And since 17.1 still receives monthly security updates, I went ahead and built from source to get the latest August 2022 updates. Here's the zip if anyone else is interested.

<removed>
[Nexus 7 (2013) Android Development] underflash:
Would be great you could guide how to build 17.1 from source. Thanks. Definitely time to downgrade at my end.
[Nexus 7 (2013) Android Development] poo706:
I just followed the link in the OP: https://github.com/followmsi/manifests/tree/flo-deb-lineage-17.1

The only hiccup I encounter is this command: git checkout origin/flo-deb-lineage-17.1

So instead, I manually create the local_manifests folder under the .repo folder. Then in local_manifests, I manually create roomservice.xml and paste in the contents from this link: https://github.com/followmsi/manifests/blob/flo-deb-lineage-17.1/local_manifests/roomservice.xml
[Nexus 7 (2013) Android Development] underflash:
For testing will garb this https://androidfilehost.com/?fid=17248734326145688960
[Nexus 7 (2013) Android Development] ipdev:
Hi. 🙂

I have not run personal builds recently but, I am using followmsi's sources.

I was testing a few build time changes..

Long story short..

Use curl to pull roomservice.

ipdev99/local_manifests - [GitHub] - [lineage-17.1] - Link

You will have to adjust the curl command back to followmsi's branch.

https://raw.githubusercontent.com/followmsi/manifests/flo-deb-lineage-17.1/local_manifests/roomservice.xml

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] poo706:
Awesome, thanks for the info! Why do you maintain your own local manifest? It looks like it all points to follow's branches. Also, do you regularly build 17.1 when the source updates and post the zips?
[Nexus 7 (2013) Android Development] ipdev:
I do not remember what build change(s) I was testing on flo/deb 17.1

I gave up on the change(s) or followmsi included it. :unsure:

So I pointed my local manifest back to followmsi's repo.

Might have been a local build change that was never pushed to github?​

I have a Pixel C (dragon) so I also include followmsi's repo(s) for Dragon in my local manifest. 🙃

--

I run personal builds but..

It has been awhile. 🙃

SourceForge - Link

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] underflash:
A bit confused about flo-flox. Now running lineage-18.1-nightly-flox and used sysrepart-ultimate.zip - 4GB system, data is wiped, 'vendor' partition is added, 'recovery' is enlarged to 64MB in-place, flox compatible.

I would like to roll back and test lineage-17.1-20201216-UNOFFICIAL-flo.zip by followmsi. Do I need to do re-partition back to stock and then enlarge system partition with e.g. flo-deb_clamor_repartition_20201203.zip?
[Nexus 7 (2013) Android Development] bgolfer66:
I would appreciate that as well!
[Nexus 7 (2013) Android Development] poo706:
See post #3,889, or click this link.

https://xdaforums.com/t/rom-flo-deb-unofficial-lineageos-19-1-2022-06-16.3569067/post-87283363
[Nexus 7 (2013) Android Development] dg85:
hello,

I installed the following items:

-lineage-19.1-20220616-UNOFFICIAL-flo

-open_gapps-arm-12L-pico-20220705-UNOFFICIAL_MOD

-Magisk-v25.1

-ElementalX-N7-7.02-Twelve-20220215-AK3

with twrp-3.6.2_9-0-flo_followmsi

My nexus7 was already repartitioned

everything works fine (sometimes a problem with bluetooth)

The installation of elementalx is done without the AROMA installer. So I don't know how to modify the kernel parameters.

(I am trying to use the usb-otg+charge function)

if I manually modify the /sys/module/msm_otg/parameters/usbhost_charge_mode file by putting Y instead of N, it works as long as the nexus stays on.

At each restart, this file returns to its original value.

there was with version elementalx-n7-7.00 a configuration file etc/elementalx.conf which could be modified, but with version n7-7.02-twelve, I can't find this configuration file.

Thanks for reading and I hope someone finds a solution for me.
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 19.1 - August 2022

lineage-19.1-20220818-UNOFFICIAL-flo.zip

lineage-19.1-20220818-UNOFFICIAL-deb.zip

Changes:

- Google security updates -> August 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:
Has anyone been able to install rom (LOS 19.1)+gapps (nano or pico) with system_repart1380_20 ?

I was able to install ROM, but gapps gave error 70 :/

With system repart ultimate TWRP wasn"t able to mount anything and I had to go back to stock 6.0.1
[Nexus 7 (2013) Android Development] wstevew:
Looking for help.

I have a Nexus 7 flo Wi-FI 16GB

I have unlocked the bootloader, installed TWRP 3.6.2_9-0

Wiped everything in TWRP

Transfered the linage-19.1 zip file and gapps nano to the Internal storage

Rebooted to recovery

Install

Select linage-19.1 zip and swipe

Results in error below, How do I get it to Install?

I assume this is because the system partition is 827MB (812MB free).

So I attempt this guide

[Guide] Repartition Nexus7(2013) to increase system partition - Extra Space for Rom

Hi, this is my first time posting here. I noticed there is no guide to increase the system partition size in Nexus 7 (2013). The system partition is only around 880MB making it impossible to flash new ROMs and large package of GApps. This guide...

xdaforums.com

And got to the point where I rename system to unnamed1 and i got disconnected from adb. so i go back into parted and now I get "No device found"

So now I am not sure how to recover this.

------

Updating partition details...

...done

Full SELinux support is present.

MTP Enabled

Installing zip file '/sdcard/linage-19.1-20220818-UNOFFICIAL-flo.zip'

Unmounting System...

Target: google/razor/flo/6.0.1/MOB30X/3036618:user/release-keys

Patching system image unconditionally...

E1001: Failed to update system Image

Updater progress ended with ERROR 1

Error Installing zip file '/sdcard/linage-19.1-20220818-UNOFFICIAL-flo.zip'

Updating partition details...

..done
[Nexus 7 (2013) Android Development] ipdev:
Currently you will need just under a 1.3G system partition to install Lineage 19 on flo or deb.

BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1336934400 # 1275M

History of updating the required system size.

followmsi - [GitHub] - flo/deb BoardConfigCommon - Line 89​

I use REPIT to (re)partition a few devices.

I might be a little bias though. 🙃

[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 7 (2013) [deb][flo]

xdaThread - Link​

As for installing Lineage and OpenGApps..

- Post # 3,856

- Post # 3,867

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] ipdev:
The install error was becuase the system partition was too small, Lineage would not fit.

I am not sure what kicked out your adb connection. :unsure:

If you reboot into recovery does adb connect?

You will not have a system partition to mount so I would suggest (if you can) rename 22 back to system.

Then reboot into recovery again.

--

If that does not work..

Use k23m's RESTOCK or CROSS scripts.

They are Windows based so, you need to run it from a computer.

xdaThread - RESTOCK - Link

xdaThread - CROSS - Link

Cheers. :cowboy:

PS.

See my post above.

- Post # 3,901
[Nexus 7 (2013) Android Development] wstevew:
Update

I have managed to resolve things back to stock partition table, I got into parted and renamed it back to system

I then used CROSS and had the same Error when trying to install the system.

I re-run CROSS and this time I used the TWRP supplied with CROSS and all went ok, and now have Lineage 18.1 flox
[Nexus 7 (2013) Android Development] jhford:
I have 2 debs and I have the following issues. I intermittently receive the following popup messages: "System UI isn't responding" and 'Process UI" isn't responding." And I just installed this deb update and received 2 new popup messages on reboot. "Google Play Store keeps stopping," and "Google Keep keeps stopping." Also, I usually use my debs online, and I have a strong internet connection, but my debs are quite slow. I recently bought an Amazon HD 8 Plus tablet which I have modded into almost an Android device. It's running the Google Play Store (GPS), Nova Launcher, and has 131 GPS apps installed, and it runs circles around my debs. I love my debs; I just wish they could be speeded up. Anyone have any brilliant ideas?

Thanks
[Nexus 7 (2013) Android Development] underflash:
Maybe you try it on 16bg? Then use sysrepart-ultimate-2.zip
[Nexus 7 (2013) Android Development] underflash:
Same here... Will test crDroidAndroid-11.0-20220715-flox-v7.20.zip or RROS-Q-8.7.3-20220220-flo-480dpi-Unofficial.zip or lineage-17.1-20201216-UNOFFICIAL-flo.zip
[Nexus 7 (2013) Android Development] MikiGry:
Repartition solutions suggested by ipdev worked, so problem solved. I"m sure i have 32GB model :)

@followmsi

Thank you for the rom. Here are some things i spotted while using it so far:

Nexus 7 flo

LOS 19.1 20220818 + gapps 12L pico 20220705 by ipdev + magisk 25.1

Graphical glitches during initial setup

1. LOS part setup is mostly unreadable. There is black text on black backgroud (first and third picture)

2. Animations which were suposed to show how smart bar work don"t load up (second one)

AOSP keyboard

AOSP keyboard worked well during initial setup. However when i tried to login to Telegram (which requires phone numer and forces numerical kerboard layout) AOSP keybord would instantly crash. The only action it was able to perform was display for like 0,1s a window about suggesting contact name. There was no "app not responding"). Logact revealed some java exception (AOSP keyboard related).

Solution: use different keyboard

XDA app login problem

For some reason XDA appwould,t let me log in. There was no reaction when i pressed log in button (apart from high network traffic for a few seconds). First thought - android system webview is missing. Installed from Play Store - nothing changed. Then I came across this thread https://xdaforums.com/t/xda-app-and-login-problem-with-the-lineageos-browser.4400475/

I used chrome browser, set it as default one and problem solved. I was able to log in. It has to be a full prowser though. Via browser for example won't work

Build in screen recorder doesn't work

It starts the countdown and then toast appeares saying that there was a problem and it couldn"t record the screen. Logs attached. Full one - full logcat with everyting that my tablet was doing during testing (battery level reports, temperature reportt, some errors unrelated to screen recording - for me at least). Important part - just things related to screen recording.

Tried with external app - AZ screen recording. It was able to record the screen. However tablet became unusable during process (lagged soo much) and produced a strange moving black glitch at the right corner of the screen. This glitch wasn't present at the screen recording though. I could't screenshot it either (Couldn't save the screenshot error came up)

Super laggy statusbar and toggles

This is by far the most laggy part of the rom. Messing aroud toggles is a slideshow. Tablet lags horribly. I think the reason for this is scrolling toggle names. Before they start scrolling through current WI-FI network name (for example) everything is fine.

Solution for this problem would be to disable scrolling names for toggles (and just leave the first part of whatever it is currently displaying)
[Nexus 7 (2013) Android Development] G0rg0ne:
Hi. I'm back. I soft brick my flo with a repartition without pass through restock. I don't have time till now to try solve the problem but now with Cross scripts I restock and repartition. All go smooth with no problem. So I'm on Lineage 19.1 with @ipdev nano gapps. No root. Install disney+ from aurora store (in playstore the app is not available) and hbo max. Both work fine. Thx @followmsi and @ipdev .
[Nexus 7 (2013) Android Development] jhford:
How can I change the 5 icons and their apps in the taskbar at the bottom of each page?
[Nexus 7 (2013) Android Development] MikiGry:
@jhford

For what I undestand about taskbar feature is it shows the same apps that you would normally have at the botom of your homecreen (you swipe up near this area to get into app drawer). So if you want to change the apps in smart bar, you have to change those 5 homecreen apps as well (just drag and drop). This is a native android 12L feature

@followmsi

Is seems that flo has a lot more trouble playing 720p 60fps videos (from youtube) than on android 10. On android 10 i was able to watch 720p 60fps generally without any problem with minor stuttering. On LOS 19.1 however it got worse. It appeares to be stuttering much more and after some time can get so bad that voice begins to stutter as well. Logcat revealed that every time it stared to do it (just video) lines like that would appear:

08-23 21:26:17.120 10937 10937 W Choreographer: Frame time is 0.056277 ms in the future! Check that graphics HAL is generating vsync timestamps using the correct timebase.

08-23 21:26:18.160 10937 10937 W Choreographer: Frame time is 0.055402 ms in the future! Check that graphics HAL is generating vsync timestamps using the correct timebase.

Some videos appear to stutter more then others
[Nexus 7 (2013) Android Development] agemore:
Hi, sorry about my noob question.. But for update to the next build i have simply to flash the new image from twrp?
[Nexus 7 (2013) Android Development] filjusz:
And gapps&magisk if you need them
[Nexus 7 (2013) Android Development] ipdev:
If you are using OpenGApps, it includes a survival (addon.d) script.

OpenGApps will be re-installed after updating the system.

Magisk on the other hand.

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

If you are using the deprecated (I am not sure if it works on flo) install method.

Rename the Magisk file from apk to zip and install with TWRP.

It will also add a survival (addon.d) script.

The new boot image will be patched after system update.​

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] kevinkoh:
Did anyone managed to get Widevine L1 to play Netflix in FHD on LOS 19.1?
[Nexus 7 (2013) Android Development] Jacobh1245:
Not sure if anyone else has this problem. I have on other roms before too I have the 2013 WIFI model(deb) but 99% of roms don't work. I get an error saying its for the wrong device. flo and flox as expected, don't work. any help would be appreciated.
[Nexus 7 (2013) Android Development] daedric:
flo = Nexus 7 2013 Wifi

deb = Nexus 7 2013 LTE

You tried flo version, and deb version, and neither work ?
[Nexus 7 (2013) Android Development] Jacobh1245:
That is correct
[Nexus 7 (2013) Android Development] Jacobh1245:
not 100% sure, its been a long time since ive touched this tablet. Im starting to second guess myself as to the recovery i flashed. In other words i think i might have flashed deb recovery on a flo device ;(
[Nexus 7 (2013) Android Development] ipdev:
Easy mistake to make. 🙃

There are two ways to determine what version it is.

If there is a SIM card slot it is a deb. If there is no SIM card slot it is a flo.

(Bottom right side of device.)

The second way would be to boot to bootloader.

(The manual way is to power it on hold both the power and volume down keys.)

It will show what your device is.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Jacobh1245:
Yeah, so I flashed the flo recovery and gave myself a large palm to the forehead. I've never done that before but it has seemingly fixed all my problems
[Nexus 7 (2013) Android Development] ipdev:
@Jacobh1245

We have all done it. 😜

To quote myself from a diferent from a different thread.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Jacobh1245:
So true
[Nexus 7 (2013) Android Development] MikiGry:
Little update on this one. To temporarily fix the problem I have to reboot the tablet. By doing so i was able to watch a 25min 60fps 720p without any lagging or stuttering. However after some uknown amount of time this issue seems to return :/
[Nexus 7 (2013) Android Development] MikiGry:
@followmsi

New day ,new issue. I'm staring to feel bad for reporting more and more of them :p

Today i've discovered that BT died. I started to suspect something is going on after seeing "Bluetooth stopped working" message a few times after unlocking the screen (BT wasn't enabled). So i tried to turn it on, but it doesn't turn on. Reboot doesn't fix the issue

Logcat

Logcat indeed cofirmed something is wrong. System is trying to turn on BT 8 times. After that it it times out and statusbar toogle turns to off state again

dmesg

Dmesg reports that something is wrong as well. This section caught my eye:

Spoiler content hidden.