yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Windsor1959:
I installed this latest Android 12 ROM for flo. I did a dirty flash over the previous Lineage 19.0. The only glitch I found was that I had to reinstall Magisk after installing this ROM and GApps. All else is running fine.
[Nexus 7 (2013) Android Development] Kick-Ass Joe:
Are you able to install Netflix with lineage-19.0-20211212-UNOFFICIAL-flo.zip? It doesn't seem to work for me even with the app renamed, MagiskHide, liboemcrypto disabler, and MagiskHide Props Config.
[Nexus 7 (2013) Android Development] LCDR:
Hello to all of you, could someone help me. Is there no "quick reboot" to recovery in Lineage 19-early.

My device is FLO.

Thanks for all your help
[Nexus 7 (2013) Android Development] jhford:
I repartitioned my 16GB FLO with @k23m's "sysrepart.zip" and got the following errors

"failed to mount '/system' (No such file or directory"

"failed to mount '/cache' (No such file or directory"

Then I tried to flash followmsi's latest version of LOS 18.1 anyway, and got the following error: "Updater process ended with ERROR: 1"

Thanks
[Nexus 7 (2013) Android Development] RazGame:
[MENTION=5480152]followmsi[/MENTION] thanks for nice ROM!

May you add Pixel buttons on navbar?
[Nexus 7 (2013) Android Development] rusik2293:
ok, last try for miracast ;)

https://github.com/kensuke/How-to-M...frameworks/av/media/libstagefright/ACodec.cpp
[Nexus 7 (2013) Android Development] RazGame:
Can't find this string at v4
[Nexus 7 (2013) Android Development] followmsi:
No .. only AOSP !

If this will be included into AOSP, we may activate it.
[Nexus 7 (2013) Android Development] followmsi:
You need to add it .. manually

We may include it into build.prop .. later on

https://xdaforums.com/showpost.php?p=71801256&postcount=274
[Nexus 7 (2013) Android Development] followmsi:
Sorry, we need to stop here testing patches into the wild ;)

You may take the manifest and setup your own lab ?

https://github.com/followmsi/manifests/tree/flo-deb-aosp-nougat

As said before .. if you have a good solution we will implement.
[Nexus 7 (2013) Android Development] rusik2293:
You thik this patch not good ?

If you just dont want to wait dont do make clean from last build:)
[Nexus 7 (2013) Android Development] followmsi:
I have no devices to test.

As well I don't want to rely on other people testing.

Miracast has not the same priority as YouTube for me ..

Not sure about this patch either .. you really think it fixes Miracast entirely ?

You are still in testing mode !

For this purpose I suggest you use an own build-tree.

Hopefully you will find a solution .. still happy to implement.

But I will stay out of the engineering part.

Cheers
[Nexus 7 (2013) Android Development] logitechor:
Clean install and v3 orks. Thank you.I too receive the same message. I have not yet reverted back to a previous install. Wondered if you fixed it.
[Nexus 7 (2013) Android Development] -BlitzkrieG-:
Installed v.4.1 with this gapps https://xdaforums.com/android/software/gapps-dynamic-gapps-t3487192

no FCs in setup wizard. Successfully recovered apps and settings from backup.

followmsi, thanks for developing.:good:
[Nexus 7 (2013) Android Development] quickstang:
I came from another ROM & tested with 4/16 gapps and got the setup issue.

However, I realized that when I rebooted to recovery, & reflashed the ROM & SU, then booted that my gapps from the previous ROM were still there. Totally forgot I was only wiping system & cache/dalvik.

Everything is working great & I just run open gapps & flash the latest pico version.
[Nexus 7 (2013) Android Development] dmitrygr:
camera does not seem to work at all (google cam pap latest ver) - just get a black screen
[Nexus 7 (2013) Android Development] miki67:
Google cam works well for me (v.2.5.042)...[emoji6]

Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.1.2_r2_N2G47E) con Tapatalk 6
[Nexus 7 (2013) Android Development] m00head:
The latest version of Google Camera which will successfully install on this device (using an APK file) is version 2.7.008, available to download from APK Mirror here:

http://www.apkmirror.com/apk/google-inc/camera/camera-2-7-008-release/
[Nexus 7 (2013) Android Development] STMSHD37:
Yeah other apps are OK. Well, I rolled back to 7.0 now but I will update to 7.1.2 soon.

And, now I know how to skip the buggy setup wizard. ;) It will be fine. Thanks.
[Nexus 7 (2013) Android Development] drewski_1:
What message :cyclops:
[Nexus 7 (2013) Android Development] m00head:
[Guide] How to Port Pixel Navigation Bar Animation to Your Phone (Updated to 7.1.1 Final)

https://chromloop.com/2016/11/guide-how-to-port-pixel-navigation-bar-animation-to-your-phone/
[Nexus 7 (2013) Android Development] :
Any chance to get substratum support?
[Nexus 7 (2013) Android Development] followmsi:
No - just AOSP :)

Why not using PureNexus ?
[Nexus 7 (2013) Android Development] patrol95:
Everything seems fine up to welcome screen, which keeps crashing when I press either "set up as new device" or "copy data"
[Nexus 7 (2013) Android Development] patria o muerte:
I artitioned my 16GB FLO with @k23m's "sysrepart.zip" and got the following errors

I got the same errors, i solved rebooting recovery,then i succesfully flashed everything.

@followmsi : amazing rom.
[Nexus 7 (2013) Android Development] jhford:
I rebooted TWRP but it didn't fix it.
[Nexus 7 (2013) Android Development] kingwangeve@gmail.com:
Why can't YouTube watch 1080P?
[Nexus 7 (2013) Android Development] G0rg0ne:
C'mon, it's just a beta. Let @followmsi work to it. Let's thank him for keeping such an old tablet alive. Also thanks @ipdev because he is always close and ready to lend a helping hand
[Nexus 7 (2013) Android Development] gnelkos:
I had similar problem until I used ADB sideload from twrp and successfully ran clamor sysrepart. I followed the lineage wiki for Flox. Oddly enough I was trying to install Flox 18.1 but got an error. Seems to be an issue with twrp and lineage recovery maybe more reliable. So I just sideloaded this ROM and it's working fine, I just need an e reader.
[Nexus 7 (2013) Android Development] DCvan:
Thank you @followmsi for bringing us a very nice Christmas 🎁!

Dirty flash Android 12 over Android 11 November build, used the bit Gapps. Had to uninstall Magish 23, flash 23 in recovery rebooted and install 23 APK. Magish is working properly with root.

Wishes everyone a Safe Healthy Happy Holidays!
[Nexus 7 (2013) Android Development] Bernd K:
Thank you @followmsi for the Android12 version. I installed today and everything run smooth. I have the impression better than 18.1. Thank you for keeping flo and deb alive.
[Nexus 7 (2013) Android Development] NorTrek:
So is the 19 very new and unstable compare to 18.1 ?
[Nexus 7 (2013) Android Development] patria o muerte:
For me,It seems to be pretty stable.
[Nexus 7 (2013) Android Development] NorTrek:
Ok, i just wonder if it will work for a daily driver for my N7. And A12 is very new and we can expect some incompatibility with certain aps ?
[Nexus 7 (2013) Android Development] vladlex:
At 19 strong charge consumption, an uncomfortable curtain, rolled back to 18.1, everything became normal, while 19 was damp.
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 19.0 - Early builds

One more "early" build of lineage-19.0 ..

Still quite a lot of lineage customizations / settings / bugfixes are missing.

lineage-19.0-20220107-UNOFFICIAL-flo.zip

lineage-19.1-20220107-UNOFFICIAL-deb.zip

Changes:

- AOSP January 2022 updates

- Latest LineageOS changes

- Some minor device changes

- Patched frameworks/base & Permissions to support microG

Known issues:

- Plenty of lineage customizations / settings / bugfixes are still missing !

- SELinux is permissive

- Maybe more issues ..

Tested flo build with BiTGApps-arm-12.0.0-R44 and Magisk 23.0.

Thanks to @ipdev for helping and testing !

Enjoy Android 12 :p
[Nexus 7 (2013) Android Development] redwoodie:
I have a DEB LTE connectivity issue after installing LOS 18.1 with CROSS2 lineage-install3.bat. Initially it took a while for mobile data to connect after installing SIM from another stock DEB, not unheard of but usually devices connect in seconds here. Then it worked fine for a day or so. After a reboot I didn't have connectivity, but after removing and reinserting SIM it was restored. Today it mostly sat unused with wifi on, but when I turned off wifi then I couldn't get mobile data again. Oddly, the network status showed connected and the data icon showed signal, but the LTE letters next to it were missing as in image below. SIM status showed connected and signal strength also. Reinsertion of the SIM didn't fix it at first, but after a reboot and a reinsertion it finally came back. I didn't observe this issue on stock MOB30X prior to running the repartition/install script.

Other details:

Repartition script was sysrepart_1380_20.zip

LOS version is 18.1-20211210-UNOFFICIAL-deb

Installed on stock/never modded/BL-unlocked DEB on MOB30X

Wiped

Ran CROSS2 (with update) lineage-install3.bat

Pico GAAPS open_gaaps-arm-11.0-pico-20211221.zip

TWRP 3.6.0_9-1-deb_followmsi.img

Magisk-v23.0.zip

Network settings are correct for carrier (Global, VZWINTERNET)

I tried using the Mobile Data Always On setting in Developer Options, it doesn't seem to affect the issue.

Any suggestions or ideas on how to resolve?

Thanks!
[Nexus 7 (2013) Android Development] prsa01:
**update - not sure what fixed it but between reflashing, clearing cache multiple times, going in/out of twrp it eventually started working normally. So disregard.

____________________________________

Anyone know possible solutions - The last 2 times I've updated 12 I've lost Google voice. I couldn't remember what I did to get it back last time so I Uninstalled and attempted to reinstall.

Play store sticks in Pending status.

I have tried clearing data and cache in play store

FYI - each of the 2 times dirty updating 12 I get a log entry appearing that gapps was retained but have needed to reflash gapps to get rid of Google services errors.

Thanks much for any ideas!
[Nexus 7 (2013) Android Development] AlesUlrych:
Hello followmsi,

I've just dared to upgrade to the new LineageOS 19, everything has gone off without a hitch. Install without error and the system started normally after reboot. Installed applications (Netflix, Voyo, Skylink, O2TV, iPrima, Kodi,...) from version 18 remained functional.

I'll probably run more tests (endurance, setting, options) tonight.

Huge thumbs up for existing work.

Thanks a lot.

Aleš
[Nexus 7 (2013) Android Development] fattox:
How's going with a dirty flash? I'm very tempted
[Nexus 7 (2013) Android Development] figgycity50:
Hi followmsi,

Simple technical request: can you enable CONFIG_NLS_UTF8=y in your elementalx Kconfig?

I'm trying to use exfat OTG in the elementalx kernel, and looking at the sources https://github.com/followmsi/flo_el...e/arch/arm/configs/elementalx_defconfig#L3666 it tries to use the utf8 charset module but when I try to plug it in I get an [EXFAT] IO charset utf8 not found error. I've done a little bit of source code reading and I'm pretty sure enabling that setting would fix it, Thanks. Great rom by the way!
[Nexus 7 (2013) Android Development] Spielmops:
I installed this LineageOS 19 over LineageOS 18 on Nexus 7-deb (dirty). Had to reinstall Magisk via TWRP and the device startet fine.

I'm missing the "reboot to recovery"-option and "change brightness by wiping the statusbar" is not working. "Terminate app in foreground" by "Long Press" a key is not working too. Is that normal?

Spielmops
[Nexus 7 (2013) Android Development] ayenzel:
I think LineageOS 19 is the best version ever for my deb. Everything feels smooth and responsive ,I feel so amazed. I love it! Thank you developer for making this ROM for my deb. Feels like a new tablet now.
[Nexus 7 (2013) Android Development] jhford:
I agree.
[Nexus 7 (2013) Android Development] dendk:
Flashed new version, 12.0, flo, new build, Bit-gapps 12.0...installed as per recommendation . Google play not showing network connection...but there is one, went in to advanced settings in the wi-fi client and tweaked it...remember this happening with older builds if the wifi was not tweaked right...must be missing something
[Nexus 7 (2013) Android Development] ayenzel:
I've encountered a problem in the camera , it will freeze and I can't use it , I'm using LineageOS19 , so far this is the only bug I found. I hope it can be fixed then it would be perfect! 😃😃
[Nexus 7 (2013) Android Development] taadow1030:
Hello all. I installed LOS 19.0 with the Bit Gapps. However, I keep getting Play Store force closes and Play Services errors. Has anyone had the same issue but got it working?

Edit: tried again and it installed this time. Then the force closes started yet again. Next, I went into the app settings for Play Store & Play Services, cleared cache and re-enabled all the permissions that somehow were not turned on. Thanks for this ROM! This is the fastest my Nexus has run in years!
[Nexus 7 (2013) Android Development] stoned-mamba-666:
@followmsi

I had trouble flashing official lineage OS build on my Nexus 7 and I ended up flashing your unofficial build. It works great and I am very happy. Thank you for your work.

I have a single question regarding your build:

LineageOS has a cool privacy feature named MAC address randomization. However I am unable to find this option in your build (last unofficial 18.1 to be precise). Device seems to be using a burned-in MAC address all the time. Do you by any chance know if this is a feature of this specific tablet model (maybe WiFi chip or driver doesn't support this) or it is a feature of your build? Can this be resolved by some clever configuration of your build?

If anyone who has been able to flash an official LineageOS build for this device can take a look at WiFi settings section and report if they have a MAC randomization feature available there I would be happy.

Thanks in advance!
[Nexus 7 (2013) Android Development] makjim:
Upgraded my DEB from 18.1 to 19.0. So far everything working OK.

Only the Trebuchet launcher is not working properly and replaced it with Nova7.

Missed the Power Menu feature for reboot to Recovery.

Thank you very much for followmsi's effort to keep the Nexus 7 alive!
[Nexus 7 (2013) Android Development] djibe89:
Hi, does anyone has twrp-3.5.2_9-0-flo_followmsi.img ?

Some people report no touch support with twrp-3.6.0_9-1-flo_followmsi

Thanks
[Nexus 7 (2013) Android Development] djibe89:
Finally I found these in my old backup
[Nexus 7 (2013) Android Development] curiousde2002:
Hi everybody,

my Deb is presently on Lineage-17.1-20220211-Unofficial-deb with TWRP-3.4.0-0-deb.

For partitioning I had used @followmsi's sysrepart_1280_120.zip.

Now I'm interested in the new lineage 19.1.

I need to proceed very carefully as the USB port is inoperative, so no way to connect to a PC!

Would the following steps work?

First put the following files on my Deb:

twrp-3.6.0_9-1-deb_followmsi.img

@followmsi's sysrepart_1380_20.zip

Lineage-19.1-20220107-unofficial-deb

BiTGApps-arm-12.0.0-R45_signed.zip

Magisk 23.0

Then:

Flash twrp-3.6.0_9-1-deb_followmsi.img

Reboot into recovery

Flash @followmsi's sysrepart_1380_20.zip (understand this will only wipe system and cache, not data or media?)

Reboot into recovery again

Wipe system, dalvik, and cache

For dirty install flash Lineage-19.1-20220107-unofficial-deb

Flash BiTGApps-arm-12.0.0-R45_signed.zip

Flash Magisk 23.0

Reboot

Maybe someone could have a look at this and tell me if I missed something.

Thank you very much in advance!
[Nexus 7 (2013) Android Development] Mr.Conkel:
Well first things first, you shouldn't have to repartition your device again if you've already been on Lineage 17.1 with gapps or have run any repartitioning tool (like clamor or followmsi methods) in the past this is normally a onetime thing unless you totally revert to stock and start from scratch.

The rest though looks fine just unfortunate that your unable to use the port .
[Nexus 7 (2013) Android Development] followmsi:
Sounds good ..

defconfig: Enable CONFIG_NLS_UTF8 · followmsi/flo_elementalx@01db365

ElementalX for Nexus 7 (2013). Contribute to followmsi/flo_elementalx development by creating an account on GitHub.

github.com

KERNEL - Google Drive

drive.google.com

Made the same change to "my" kernel .. which will be part of next Lineage build.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
I remember we have tested MAC address randomization on older Android version .. There were some issues on certain "legacy" devices .. not sure about the results on flo/deb anymore.

Will keep it on my list .. maybe we enable and test in next month builds.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 19.0 - Early builds

As Lineage has still not merged all UI changes and other customizations I have merged "advanced restart menu" and some "buttons" changes myself ..

lineage-19.0-20220215-UNOFFICIAL-flo.zip

lineage-19.1-20220215-UNOFFICIAL-deb.zip

Changes:

- Google security updates -> February 2022

- Patched frameworks/base & Permissions to support microG

- Latest LineageOS changes for Android 12

Pls check first page for known issues.

Tested flo build with BiTGApps-arm-12.0.0-R44 and fresh Magisk 24.1.

Thanks to @ipdev for helping and testing !

Enjoy Android 12 :p
[Nexus 7 (2013) Android Development] brewer75:
Thank you so much for your continued devotion to keeping this device as current as possible. Your rom is stellar and I am very happy with it. You mentioned that you have merged the "advanced restart menu" but I am unable to find this in settings, am I missing something here?
[Nexus 7 (2013) Android Development] taw62:
Go to: Settings/System/Gestures/press and hold power button/Advanced restart.
[Nexus 7 (2013) Android Development] brewer75:
Fantastic, thanks!!
[Nexus 7 (2013) Android Development] Windsor1959:
I just installed the 2/15 version of Lineage 19.0 on my flo by dirty flash, and Bit GApps, as I have done time and time again. This time, I got the force closes for Play Store and Play Services. Permissions were all enabled properly. I reinstalled. Same result. I did a factory reset and installed again. Same result.

Any ideas as to what might be going on? Thanks!
[Nexus 7 (2013) Android Development] taadow1030:
I actually had to check permissions more than once (twice I think). For some reason, some of the permissions disabled themselves again. I then went and re-enabled every permission for Play Store and Play Services and then it worked. Play Store Services updated itself afterwards and all was well. To all whom are curious, I have the Deb version.
[Nexus 7 (2013) Android Development] Windsor1959:
Permissions seem to be correct, and to remain that way, but I still get the force closes for Play Services and Play Store. I haven't found any causes yet!
[Nexus 7 (2013) Android Development] taadow1030:
I just cleaned flashed today's update on my Deb. Here's the steps I used:

I qued TWRP to flashed ROM, Bitgapps and then Magisk 23. I wiped dalvic cache then rebooted to system. I let the device sit for 10 minutes or so after the welcome screen appeared. No issues at all. I wish I was of more assistance.

@followmsi, outstanding job! Thanks again for your efforts along with those who assisted!
[Nexus 7 (2013) Android Development] haruitk:
Flashed the 19.0 build on flo, Magisk 24.1 and BiTGApps-arm-12.0.0-R45_signed.zip - seeing the same 'Google Play services keeps stopping' error...
[Nexus 7 (2013) Android Development] AlesUlrych:
For me, the upgrade went smoothly and everything works fine. The device is certified. I did a System + Dalvid Cache format in twrp-3.6.0_9-1 and then installed rom + BiTGApps-arm-12.0.0-R44 + Magisk 24.1.

After rebooting everything works for me. :)

Just a note. Isn't the problem in BiTGApps-arm-12.0.0-R45? That's the only difference I can see at first glance.
[Nexus 7 (2013) Android Development] taw62:
I am on R45 and everything works fine. Did everybody reboot into recovery before installing BITGapps? I had issues in the past when I installed Gapps right after the ROM.
[Nexus 7 (2013) Android Development] yahoé:
See below
[Nexus 7 (2013) Android Development] yahoé:
On Flo, did system and Dalvik format, then flashed the 2022-02-15 ROM + BiTGApps-arm-12.0.0-R45 + Magisk 24.1, then upon rebooting I get the “Google Play services keep stopping” error. I have the same issue with BitGapps R44 on the February ROM.

Since 2022-02-15 ROM + BiTGApps-arm-12.0.0-R45 + Magisk 24.1 works like a charm for me, the problem is only happening with the February ROM. @followmsi
[Nexus 7 (2013) Android Development] Windsor1959:
I was on BitGApps R44. I restored a TWRP backup on my flo. I tried again to install this 2/15 ROM with BitGApps R45. Same issue with crashing of Play Services and Play Store. I'll try again later, but it looks like the 2/15 ROM is more hit-or-miss than previous ROMs.
[Nexus 7 (2013) Android Development] haruitk:
thanks! flashing Magisk after BitGApps fixed it for me :)
[Nexus 7 (2013) Android Development] followmsi:
It seems R45 requires clean install ..

GitHub - BiTGApps/BiTGApps: The main repository of The BiTGApps Project

The main repository of The BiTGApps Project. Contribute to BiTGApps/BiTGApps development by creating an account on GitHub.

github.com

Here you can find instructions for 1.4G (1477M) system partition ..

https://xdaforums.com/t/rom-flo-deb...9-0-2022-02-15.3569067/page-167#post-84535925

https://xdaforums.com/t/tool-unofficial-port-repit-for-nexus-7-2013-deb-flo.4237183/

This way you can install opengapps - which require no clean install at certain revision.

Sorry, I do not have the time for further troubleshooting.

Cheers
[Nexus 7 (2013) Android Development] Windsor1959:
I tried microG and that started force closing, too.

Still no clue as to what's going on. It's not worth putting a lot of effort into my old flo, as I don't use it for anything significant. If there was an updated Nexus 7 (a tablet, not a phone), I'd have one! For now, I have Aurora Store and the Amazon Appstore installed if/when I need to install something. If I come across a potential solution, I'll try it out.

The funny thing is that my Nexus seems a bit quicker without all the extra Google stuff. My imagination? I'll find out.
[Nexus 7 (2013) Android Development] taadow1030:
It's not just your imagination. I ended up reflashing clean without gapps and using Micro g. True, my number of apps is greatly reduced without the Play Store, but my tablet is much more responsive and lasts much longer on battery. I pretty much use it only for YouTube Vanced and other streaming video anyway, so it's not a big deal .
[Nexus 7 (2013) Android Development] martin58:
what device is it?
[Nexus 7 (2013) Android Development] Windsor1959:
I now have microG set up with Play Store. That seems to be working fine, though in this setup, Play Store doesn't seem to be able to tell which paid apps I have paid for. It's not a big deal as I'm not planning to use many apps on the Nexus anyway. I can download free apps through Play Store this way. Nothing is crashing now, and my tablet seems a lot more responsive. I'll know later if battery life is better, but I suspect it will be. All is good here now!
[Nexus 7 (2013) Android Development] tekhtime:
Having a similar issue. The gapps pico fails to install despite flashing the latest system repartition zip. Any ideas?
[Nexus 7 (2013) Android Development] brewer75:
How were you able to get Play Store to work? I haven't tried MicroG on this device but my attempts to use it with the older Nexus 7 were not successful in getting Play Store to function properly.
[Nexus 7 (2013) Android Development] Windsor1959:
I followed the instructions here. You need a ROM that is signature spoofing compatible for microG to work, and this Lineage ROM is fully compatible. The trick with Play Store is to get the patched apk referenced in the link I gave you.