yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Ranbato:
Thanks for all of the great builds!

Anyone know if there is a way to get SlimPort HDMI working? It looks to me like most PIE ROMs are broken but I see this from AOSP (and [MENTION=5480152]followmsi[/MENTION])

https://xdaforums.com/nexus-7-2013/development/rom-t3569067/post75843020#post75843020
[Nexus 7 (2013) Android Development] Ally L.:
Quick follow-up... My connection to hidden WiFi networks is working now. I just happened to notice yesterday that the tablet was connecting to the hidden network on its own, and not the guest/open SSID I had set up as the workaround. Since then, the hidden network re-connects automatically as long as I turn the tablet screen off for a few seconds. I'm still running the same OS build as before, so maybe initially I didn't leave the screen off long enough to establish connection properly? Who knows, but I wanted to report back that it's no longer an issue for me.
[Nexus 7 (2013) Android Development] MikiGry:
I"ve noticed some kind of navigation bar glitch. When device is in landscape more and keyboard is opened, navigation bar glitches is such a way, that presing on back and mulltitask button results in pressing home button and does nothing. To fix that i need to rotate my screen a few times. I"ve noticed that in AOSP 8.1 as well but here it seems to be happening more frequently
[Nexus 7 (2013) Android Development] dealpapa1:
quarterly update now
[Nexus 7 (2013) Android Development] .:B:.:
Hey guys. I see there's a deb build from August 21st but the last flo build is from August 9th. The August ASB has been merged in the meantime. From what I understand the first post has been linking to more frequent builds, but that seems to have stopped at least for flo. I had the Google Drive link still cached in my browser but that folder seems to have gone altogether.

Thanks for any pointers.
[Nexus 7 (2013) Android Development] ex3meex:
BENCHMARK TEST

Hello boys, my curiosity led me to do a benchmark with this rom vs the stock official Marshmallow 6.0.1 rom with my Nexus 7 2013 FLO version (wi-fi).

I restored my Nexus to the stock official version 6.0.1 and i lunched Antutu and Geekbench apps (all clean, no root and no other **** :angel:):

After did the benchmarks on the stock rom, i rooted and flashed the LineageOS rom and i did again the benchmarks (always all clean and fresh, no extra app or something like that)

These are the results: LET'S ****ING GO LINEAGEEEEEEE :good::good::good::good::good::good: :cool::cool: :highfive: WOOOOAH
[Nexus 7 (2013) Android Development] ex3meex:
Anyone got a working PS4 Remote Control app or method for LineageOS rom? i'm having some problems dealing with that, black screen when i lunch the app (just won't start, nothing loading and all stucked).

When i close the app from the task, everything returns to normal.

I installed sony frameworks modules and other things with Magisk Hide but nothing works
[Nexus 7 (2013) Android Development] MorpheusUK:
Change keyboard navigation bar glitch

Hi,

I did a clean install of the 09/08/19 build IIRC over the weekend (which I did an OTA update to the 02/09/19 build yesterday when prompted about the available updates). Previously it had been running LOS14.1 on my N7 Flo. On both of the 16.0 builds as I have multiple keyboards the keyboard button appears between the home and menu buttons when in portrait mode (haven't checked landscape and not near the device at present). If you press on the far right where it should be the keyboard change menu pops up its just the icon positioning.

Is anyone else seeing this? Is it a known bug on the current builds?

Thanks

Morpheus
[Nexus 7 (2013) Android Development] dealpapa1:
lineage-16.0-20190902-UNOFFICIAL-flo.zip	2019-09-02 15:49	345M

do not understand why they release this build now. They can wait for the sep security. I am too lazy to make too many changes.
[Nexus 7 (2013) Android Development] Tmzdroid:
I just benchmarked my nexus 7 on stock marshmallow and got similar results on geekbench
[Nexus 7 (2013) Android Development] AndrzejSt:
Will there be a version for deb?
[Nexus 7 (2013) Android Development] pitrus-:
For some unknown reason builds for deb has been failing for a long time (fails at 99%). I will clear the source tree and clean sync it to see if it helps.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] akipapa:
hi guys,

I am trying to flash the 20190902 from [MENTION=4244522]pitrus-[/MENTION], but got "zip signature verification failed" error, which I never encountered with [MENTION=6005084]ripee[/MENTION] 's releases.

If I uncheck "zip signature verification" in TWRP, the installation can continue and my Flo can boot into android.

I asked google and found many people recommend unchecking the signature verification, but I don't understand why I need to do this? Is there some difference between pitrus-'s and repee's releases?

Is there some security risk to leave the verification unchecked?

Thanks!
[Nexus 7 (2013) Android Development] pitrus-:
You should only get this if you're switching between ripees and my builds as they're signed with different self-signed certificates (unofficial builds). If you clean flash you shouldn't see this at all. Another reasons for getting zip signature error would be a failed download.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] akipapa:
thank you pitrus- for your reply and your hard work!

Yes I only wiped System and Cache partitions.

So the certificate is stored in Data partition?

Is there a way to avoid the warning without clean flash or unchecking the box?

Thanks!
[Nexus 7 (2013) Android Development] pitrus-:
Unfortunate no, that's the point of this security feature, too make sure you don't flash an incompatible build over current build. But as the builds are the same except for certificates just uncheck the security feature when switching.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] SaZoN:
Hmm....deb folder is empty lineageos.wickenberg.nu/builds/full/deb/?C=M;O=D
[Nexus 7 (2013) Android Development] BryanF:
Yes, can someone provide an alternate link please.
[Nexus 7 (2013) Android Development] pitrus-:
Build compiled successfully again, sorry for accidentally deleting the archive though. :angel:
[Nexus 7 (2013) Android Development] dendk:
both of the last updates 904 and 906 flo boot loop on my Nexus 7 2013 flo...clean installs.
[Nexus 7 (2013) Android Development] pitrus-:
Okey, good to know. I just dirty flashed 905 yesterday and it booted successfully. I did have one app hanging the OS, however after force reboot it worked fine. It's quite apparent that this tablet is lacking enough RAM for running Android 9 and modern apps.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] jacopastorius:
Hi guys how is the performance with this rom?
[Nexus 7 (2013) Android Development] Donlagos:
The settings option "Block connection without VPN" is not working, stopping the VPN doesn't block connections.

I'm using the ProtonVPN, they don't have a kill switch in the app but they and most VPN providers use only the android kill switch.

PIA VPN use also a kill switch in there app and works fine on this Rom when enabled.

When I install the Orbot (Tor) app and try to enable orbot VPN (Tor-VPN) then the app can't make connection when I have settings option "Block connection without VPN" enabled.

Checkt all this on a other PIE Rom (Nexus 5X) and there everything works like it has to be.
[Nexus 7 (2013) Android Development] dendk:
Yea my last update was a dirty flash worked fine...Always testing I still love this tablet even though it is dated but the display is great. dated yes...but it still runs under Pie, thank you for working on the OS, It is appreciated. Back on an earlier build it is all good, boot to TWRP, WIPE ALL, copy over new build + gapps, clean davliik and boot\restore from cloud, getting very good at it.
[Nexus 7 (2013) Android Development] anivegmin:
Hi, running 14.1 on my Nexus 7 flo as this was the last release where everything works. Have tried this rom before but was a bit laggy and the compass didn't work. I'd like to upgrade but don't want to go through all the rigmarole if the compass still doesn't work and I have to then downgrade back to 14.1 (I use my Nexus 7 daily). Thanks.
[Nexus 7 (2013) Android Development] jacopastorius:
I am going to upgrade from 14.1 as well. Come back to report soon
[Nexus 7 (2013) Android Development] dendk:
Updater successful to latest build...
[Nexus 7 (2013) Android Development] shoaibsaikat:
Font issue

Some fonts are broken!
[Nexus 7 (2013) Android Development] jacopastorius:
I didn't find time to flash this pie version. Has anyone tried how is the gaming performance ?
[Nexus 7 (2013) Android Development] dendk:
Just updated to Mid Sept build, captive sign on WiFi is broken in the last few builds (dirty flash) have not tried with a clean build yet, still testing.
[Nexus 7 (2013) Android Development] cypryan1217:
Hi. I wanted to install this rom on my old device. So I rooted it with Nexus Root Toolkit and I installed the custom recovery with it too. I installed the last TWRP. After that I repartitioned the storage, and I tried to install TWRP UA, like in the guide, but I had an error that I don't have enough space on recovery. After that I installed the rom and pico GAPPS. All worked fine but I get a boot loop, and after a while I boots into recovery. I tried different builds and none of them worked. What can I do?
[Nexus 7 (2013) Android Development] rho-bot:
Suggest you first go back to factory image.

Toolkits are not needed, you can simply unlock BL via ADB, and flash the official TWRP.

Reboot to TWRP & flash LOS (+ LOS SU, in case you need root)
[Nexus 7 (2013) Android Development] ferdossi:
Location-Battery saving mode won't switch on

Hi,

Have you noticed this issue? I just installed this ROM for which I am globally satisfied.

The only problem is that I cannot enable the Battery Saving Mode in the location settings.

Each time I enable it, it automatically gets disabled by itself right away, and also disables the Location toggle (very strange btw).

My phone is rooted, I even tried a Tasker option to force this option but no luck.

Any idea? is there any other location setting elsewhere that has to be enabled prior to this one?

Thx
[Nexus 7 (2013) Android Development] jordiiB:
Can it still be a hardware issue if it worked fine on LineageOS 14.1 ?
[Nexus 7 (2013) Android Development] pitrus-:
It works fine with rotation on one of my Nexus 7, the other one has the fault I mentioned and I haven't gotten to open it up and fix it.

However you could try a clean flash of LOS 16 just to make sure it's not some crap from earlier LOS 14.1.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] cHrish1980:
First of all thanks for this ROM!

I've just switched back to LineageOS on my Nexus after trying AOSP for a while and I love the speed that my device boots up again!

So far everything works like a charm.

Except Netflix...

I've been trawling through the posts here and trying a lot of the things suggested, but I seem to be missing something.

I have Magisk 19.2 with Magisk Manager 7.2 running now and my Nexus 7 passes the SafetyNet checks successfully and Netflix is showing up in the Playstore.

I have hidden magisk for all of the playstore, playstore services and Netflix in Magisk.

I have both tried installing Netflix from the Playstore (latest version) as well as the old 4.16 release from their website.

With the old version my device comes up as unsupported, with the Playstore version everything looks good and I can start playback of a video which stops after a few seconds with error 4.7.

Has anyone gotten Netflix to work on this build?

If so, I'd be grateful for any pointers on what I am missing.

Many thanks,

Christian
[Nexus 7 (2013) Android Development] user602:
I downloaded version 4.8.5 from APK Mirror months ago and it works without errors.
[Nexus 7 (2013) Android Development] cHrish1980:
Thanks, that one works for me!

Too bad that one doesn't support offline viewing, that would have been the cherry on top - but it's great to at least be able to watch Netflix while connected to wifi again.

One interesting thing I noticed was that with the latest Playstore version, while I couldn't play anything on the tablet, I was able to cast the stream to my chromecast.

But I have no clue as to why this is possible while "local" viewing isn't. :confused:
[Nexus 7 (2013) Android Development] jhford:
TWRP error message

I have 3 debs and 2 receive this error message when I flash updates of this ROM. I posted this message on the Clamor forum, but no one has responded. Here's the message:

"Failed to mount '/vendor' (invalid argument)."

Any help will be appreciated.
[Nexus 7 (2013) Android Development] pitrus-:
Sounds like you haven't repartitioned your devices as you don't have a vendor partition on them. Follow this guide to make your tablets compatible with larger roms like this one, this will format the internal storage so make sure to backup first.

Also, don't use the TWRP in that thread, the one from twrp.me is newer and supports repartitioned devices.

https://xdaforums.com/nexus-7-2013/orig-development/repartition-nexus-7-2013-repartition-t3844386

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] dendk:
Verified power saving | location works in September 25 build, lag in September 23 build is gone.... More testing in the works.
[Nexus 7 (2013) Android Development] jhford:
Oh. [MENTION=603202]pitrus[/MENTION]. Thanks for responding. I screwed up my partitions by following some bad advice in the last few threads on Clamor's forum. I followed your advice and it's all fixed. You saved my butt. One thing puzzles me though. Clamor says to use the UA TWRP and you suggest twrp.me. What's the difference? I've always just used the ones from the official twrp site.

Tanks u again
[Nexus 7 (2013) Android Development] pitrus-:
Way back when Clamour released the repartition script, twrp couldn't cope with the new partition layout and therefore you would need to use the special build referred to in that thread. And that's not the case anymore.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] jhford:
Do you have any idea why my deb randomly reboots so frequently? Also, my Clamor log is attached. Does it look OK?

Thanks
[Nexus 7 (2013) Android Development] pitrus-:
1.5GB system partition and a vendor partition, so yes it looks good. [emoji106]

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] jhford:
Dark mode

It seems to have infected all my widgets. I hate it. How can I disable it or turn it off?

Thanks
[Nexus 7 (2013) Android Development] kazulk:
I have a video streaming app that isn't loading videos when I go to play them. Is there a certain time frame or some other criteria I should be looking for in older versions to determine if they will work? Do I just keep trying different ones until I find one that works? Just trying to figure out the process of how it was discovered what version of Netflix worked and hope a similar process will work with the app I am trying to use.
[Nexus 7 (2013) Android Development] Miho.Nightwalker:
Interesting. I don't know about the other guy but I definitely repartitioned mine as per the instructions and I'm also getting that error message, tablet however works just fine anyhow so it wasn't bothering me much ?
[Nexus 7 (2013) Android Development] Razor1973:
I have the latest TWRP, flashed the repartition script successfully, was able to install the 20190926 successfully, followed by the micro Open GApps, all successfully, but my Nexus shows the moving splash screen for about 3 minutes and then, goes back to TWRP. I have tried all of the following:

Repeating this procedure.

Installing the 20190927 build.

Booting right after installing the ROM and before flashing Open GApps.

None of that worked. Just to make sure my partitions were right and I could flash a Pie ROM, I tried the experimental Pie build of the Unlegacy Android Project. No issues, perfect boot the first time. But I want LineageOS. What am I doing wrong?

The only difference between the way I flashed LinageOS and UAP is that, for the latter, I also flashed the latest Magisk right after the ROM and Open GApps I didn't flash Magisk after installing LineageOS.
[Nexus 7 (2013) Android Development] GotoDengo:
I'm new to this ROM as well and installed the 20190925 build with no problems so perhaps give that one a try first?

And just checking that you're trying the right version of the ROM, ie deb vs flo?
[Nexus 7 (2013) Android Development] xenokc:
I have LOS 16 Pie 9 running on a couple other devices and encryption works fine but doesn't work with TRWP on N7. Seems to be more of a TWRP issue because N7 encrypted boots fine. I have LOS 16 on my dad's encrypted Galaxy S5 and TRWP has no issue with it.

Is there a 'special' version of N7 TWRP that can work with encryption?
[Nexus 7 (2013) Android Development] skare:
Getting a "404 page not found" when trying to download the FLO rom. Anyone have a working link?
[Nexus 7 (2013) Android Development] cosmo21:
Same exact problem...Flashed other roms no problem at all. When flashing this on the device just bootloops. Any solutions or anyone else having the same problem?
[Nexus 7 (2013) Android Development] pitrus-:
My bad, should be up now (upgraded to Traefik 2.0 reverse proxy) [emoji28]

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] skare:
Thanks, got it :)
[Nexus 7 (2013) Android Development] marsaltito:
Is it because of new partitions i get error "not enougs space" when tryung to install ubuntu touch ?
[Nexus 7 (2013) Android Development] EpicPotatohead:
Probably. I re-installed the repartition zip to revert the partition scheme to stock. Just got done installing Ubuntu Touch and it worked fine.
[Nexus 7 (2013) Android Development] Miho.Nightwalker:
Anyone having issues with updates saying cannot verify? Only started sometimes in last 5 days or so.
[Nexus 7 (2013) Android Development] dendk:
Getting the same From the updater, verification error on all roms running the sept 27 build.
[Nexus 7 (2013) Android Development] dealpapa1:
Getting the same From the updater, verification error on all roms running the sept 22 build.
[Nexus 7 (2013) Android Development] marsaltito:
Hi, hiw i get back to default partituon ?
[Nexus 7 (2013) Android Development] rho-bot:
Same situation, running 20190927 flo, updater shows & downloads, but denies update with "verification error"

Manual DL & Update via TWRP of 20191005 flo worked.

Update:

Having 20191005 flo running, OTA update to 20191006 is working again flawless :good:

Seems sth broke the chain between 20190927 and 20191005.
[Nexus 7 (2013) Android Development] delachurch:
Same thing here. Any ideas?

---------- Post added at 03:59 AM ---------- Previous post was at 03:16 AM ----------

Just tried,

lineage-16.0-20190925-UNOFFICIAL-flo.zip

open_gapps-arm-9.0-nano-20190925.zip

Seemed it did the trick and it is working for me. Try that out. Seems the 20191005 onwards it is not working on flo.
[Nexus 7 (2013) Android Development] jhford:
Widget data

I love the ROM, but when I reboot the following widgets have no data: Gmail, Google News and Google Voice. When I launch them from the app drawer the data usually appears in its widget, which isn't a solution.

Thanks
[Nexus 7 (2013) Android Development] rho-bot:
Cannot second that. 20191005 flo is working well for me. (see my post above)

But I do not have any gapps, so maybe there is some incompatibility ?
[Nexus 7 (2013) Android Development] real_klaerbaer:
At first i have to say: Thank you for this Build.

But i have a problem, with it:

My way for installation is:

All from the first article

twrp-3.3.1-0-flo.img

flo-deb_clamor_repartition.zip

lineage-16.0-20191006-UNOFFICIAL-flo.zip

open_gapps-arm-9.0-tvstock-20191006.zip

This works all well, but after the reboot ( lineage want to start roundabout 5min. ) i got a reboot in the recocery.

Can anybody help me?

Greetings
[Nexus 7 (2013) Android Development] tobox:
I just wiped my Lineage OS 14.1 and did a fresh install of this ROM. I have exactly the same problem, after a few minutes of spash screen the device reboots into recovery.

Will try an older version to see if that helps.
[Nexus 7 (2013) Android Development] pitrus-:
Have your tried using the lineageos recommended opengapps nano package instead?

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] real_klaerbaer:
Hello,

yes i testet the opengapps nano also. The same result.

If i flash only the lineage Os from the first Post, i get a normal boot, but without the gapps ist not realy good...

After installing the gapps, i found 2 new files in the directory. Maybe it helps a litte:

open_gapps_log.txt

open_gapps_debug_logs.tar.gz
[Nexus 7 (2013) Android Development] pitrus-:
Are you sure the repartition succeded? You can tell by looking at the size of system partition in TWRP if you choose advanced under format and select the system partition. If I remember correctly, it should say 1.5GB after repartition, and also you should have a vendor partition in the list of partitions.

If for some reason it failed, I would recommend you to use the TWRP mentioned in the Clamor repartition thread first and then upgrade to latest official after repartitioning.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] real_klaerbaer:
Sorry, under advanced i didnt find format.

---------- Post added at 02:09 PM ---------- Previous post was at 01:50 PM ----------

OK, now it seems i have a paperweight ... :crying:

i go in Advanced Wipe and select Data -> Repair or Change File System -> Repair File System = process ended with ERROR: 4 Unable to repair Data.

:(:crying::(:crying:
[Nexus 7 (2013) Android Development] real_klaerbaer:
It works. After a long day and night i got it.

I resetet my Nexus 7 with "Nexus Root Toolkit" to Original, and made all new.

And now i got it.

Thanks everybody for the help.
[Nexus 7 (2013) Android Development] demail2006:
if you can go to recovery you can recover it.
[Nexus 7 (2013) Android Development] MorpheusUK:
Hi folks,

Just a quick question, I usually try and update monthly for the Android security updates, when I was on the last official 14.1 release I could check the Flo page and see what was included in each build by date so I could tell when the security updates were merged in and at what build which I would then install. Is there anything similar I can check for these builds or is there some sort of rule of thumb e.g third Wednesday in a month?

Sorry if I've missed something obvious.
[Nexus 7 (2013) Android Development] jsschmid:
Hi,

I installed everything following the guide (I used open_gapps-arm-9.0-pico-20191011), unfortunately, when it boots up the first time, it takes around 3 to 5 minutes until it reboots to recovery.

Installing it without gapps works fine.

I used this to enlarge my system partition: https://xdaforums.com/showpost.php?p=76278047&postcount=19

I also tried this hint for a boot loop after installing gapps: https://xdaforums.com/showpost.php?p=75919404&postcount=5

...it didn't help either. Any helpful thoughts will be greatly appreciated!

Thanks

Josh
[Nexus 7 (2013) Android Development] real_klaerbaer:
Hello Josh,

this worked for me:

first:all with "Nexus Root Toolkit"

1: Factory Reset to Android 6.0.4

2: Install "twrp-3.0.2-0-flo.img"

Boot to TWRP -> Install "twrp-3.3.1-0-flo.img"

second: Reboot to recovery

install -> flo-deb_clamor_repartition.zip

Wipe -> Advanced Wipe -> System -> Repair or Change File System: If size is 1497MB -> Back

Wipe -> Advanced Wipe: selcet all -> Swipe to Wipe

install -> lineage-16.0-20190921-UNOFFICIAL-flo.zip

install -> open_gapps-arm-9.0-nano-20190513.zip

install -> Magisk-v19.3.zip

Wipe -> Advanced Wipe: Dalvik / ART Cache ; Cache -> Swipe to Wipe

Reboot

Hope you get it to work

real_klaerbaer
[Nexus 7 (2013) Android Development] Droidoidz:
Same problem here. Don't see the purpose of installing Android 6 with and older TWRP build as well to be honest...