yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] ipdev:
True but, all mine are unlocked bootloaders and some fail PlayStore certification and/or SafetyNet (including my flo) and still Netflix is available.

Granted my Pixel 3a is probably completely white listed for the time being.

6P's last stock rom was 8.1.0 (OPM7.181205.001, Dec 2018). I'm running unofficial lineage 16.

It was opened/started by hazzer originally. The latest builds, based on StatiX, are from AnyYan. I run unencrypted on testing devices.

Netflix is available to install in PlayStore even with a clean flash of rom, gapps and the current Magisk canary-debug.

Netflix offers a v4.16 Download -Link

It's an older build before some DRM changes and offline (Download) option.

Interesting note on Netflix's help site.

NOTE: Rooted or uncertified Android mobile devices are unable to download the Netflix app from the Play Store. Rooted or uncertified mobile devices are not blocked from accessing Netflix, but, depending on configuration, may not function properly.

By the way, my flo has been Not Certified in PlayStore, Passing SafetyNet and Netflix was still available to install.

Would be interested to know what you find. ;)

My results have been mixed and I can not quite narrow it down yet.

What seems to work on one device doesn't seem to work on another. As for my testing (16Gig) flo with the 0630 lineage build, using and older version of Magisk, even using the newest Manager, seems to allow Netflix to be installed from PlayStore along as SafetyNet passes even if it fails PlayStore certification.

My main flo, is on March AEX build. Apps, Magisk and Manager have only been updated since. Magisk/Manager have been updated though Manager and are both current canary-debug. Netflix is still available to install via PlayStore.

Personally, I'm not too concerned about installing Netflix on this device, if I was, I'd just sideload it.

I am just trying to figure out what changed and caused the incompatibility error around the beginning of June.

Note:

This is mostly OT and probably has nothing to do with this device, since it seems affect some devices, not all, and platform (arm/arm64, AOSP/LOS Based).

[MENTION=6005084]ripee[/MENTION]

I apologize for carrying on about this in your thread and will leave the OT with this post.

I appreciate all you contribute and offer us, especially you time and knowledge.

Thank you.

Cheers.
[Nexus 7 (2013) Android Development] ripee:
[MENTION=7280276]ipdev[/MENTION], no worries about carrying on. I have no knowledge compared with followmsi and flex1911 :D
[Nexus 7 (2013) Android Development] ripee:
Changelog

Build 0707 for both variants

* July Android security patch level.

* Synced with LineageOS sources.
[Nexus 7 (2013) Android Development] schnee1:
Made one more test after installin build 7/7. This time i cleared the data from the Netflix app, so i had 30 seconds of playback after starting a movie. Here is the logcat output:

07-07 21:54:22.783 180 180 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8960.so from current namespace instead of sphal namespace.
07-07 21:54:22.790 7146 7157 I lix.mediaclien: Background concurrent copying GC freed 154519(7MB) AllocSpace objects, 62(4MB) LOS objects, 49% free, 14MB/29MB, paused 823us total 408.020ms
07-07 21:54:25.486 7146 7157 I lix.mediaclien: Background concurrent copying GC freed 156735(6MB) AllocSpace objects, 25(1364KB) LOS objects, 49% free, 22MB/45MB, paused 183us total 180.511ms
07-07 21:54:30.352 7146 7157 I lix.mediaclien: Background concurrent copying GC freed 218539(10MB) AllocSpace objects, 26(3MB) LOS objects, 43% free, 31MB/55MB, paused 213us total 207.153ms
07-07 21:54:38.070 7146 7157 I lix.mediaclien: Background concurrent copying GC freed 248882(10MB) AllocSpace objects, 33(1788KB) LOS objects, 35% free, 44MB/68MB, paused 152us total 193.634ms
07-07 21:54:51.269 311 7805 E OMX-VDEC-1080P: (10310) -
07-07 21:54:51.269 311 7805 E OMX-VDEC-1080P: No color conversion required
07-07 21:54:51.271 311 311 E OMX-VDEC-1080P: (10310) -
07-07 21:54:51.271 311 311 E OMX-VDEC-1080P: No color conversion required
07-07 21:54:51.885 180 180 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8960.so from current namespace instead of sphal namespace.
07-07 21:54:52.723 180 180 I chatty : uid=1000(system) /system/bin/surfaceflinger identical 20 lines
07-07 21:54:52.808 180 180 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8960.so from current namespace instead of sphal namespace.
07-07 21:55:09.504 261 261 E WVCdm : Decrypt error result in session sid16 during encrypted block: 178
07-07 21:55:09.565 261 6666 E WVCdm : Decrypt error result in session sid16 during encrypted block: 178
07-07 21:55:09.607 7146 7801 D SurfaceUtils: disconnecting from surface 0x79196808, reason disconnectFromSurface
07-07 21:55:09.632 311 7805 E OMX-VDEC-1080P: (195) -
07-07 21:55:09.632 311 7805 E OMX-VDEC-1080P: Error in ioctl read next msg, error_code = -1, errno = 5
07-07 21:55:09.657 311 842 E OMX_C2D : (111) -
07-07 21:55:09.657 311 842 E OMX_C2D : Destroy C2D instance
07-07 21:55:09.657 311 842 E OMX_C2D : (111) -
07-07 21:55:09.657 311 842 E OMX_C2D : Destroy C2D instance

The video playback stops with an error when this line shows up in the output: 07-07 21:55:09.504 261 261 E WVCdm : Decrypt error result in session sid16 during encrypted block: 178

Note: it is always 'Decrypt error result in session sidXX during encrypted block: 178', only the number after the sid is changing. As i see WVCdm is the Widevine module and this error is relared to google/exoplayer?
[Nexus 7 (2013) Android Development] slapshot2286:
First off, thanks for all the work you're doing with these ROMs - you really are cranking them out and breathing new life into the N7 community.

However, I've tried your crDroid, Lineage, and Viper on my Deb, and all seem to have the same issue, which probably isn't a common one. I cannot connect to hidden networks. Unsecured and visible secured networks (5ghz and 2.4ghz) work just fine, but my home network has a hidden SSID, and will not connect no matter what. I've reset network settings, fresh flashed each one with no luck. Any ideas?
[Nexus 7 (2013) Android Development] ripee:
[MENTION=5480152]followmsi[/MENTION]
[Nexus 7 (2013) Android Development] jb-:
I had the same issue with all the custom ROMs I tried but since hidden networks aren't hidden from much of anything these days I just went ahead and changed my old 2nd router to be visible and a new ssid while I was at it. Basically any decent network analyzer will show all hidden networks. It's likely that anyone that doesn't know about these wouldn't know how to mess with your network, so...
[Nexus 7 (2013) Android Development] slapshot2286:
Oh I totally agree. But the time it took me to set up all my devices for a hidden network with MAC filtering shouldn't have to be undone by a tablet lol.

I'll probably unhide it...but I at least thought he should know it's happening. Thanks for letting me know I'm not the only one though!
[Nexus 7 (2013) Android Development] ipdev:
For those having issues with Hidden WiFi networks.

Setup-> Network-> WiFi-> Add network.

Type in SSID Name

Select encryption type

Type in password

Advanced options, last option is Hidden network change it to Yes and save.

Not the post I was looking for but, followmsi answered it in a different thread. - xdaLink

For me, normally just turning off the screen for a few seconds works.

Occasionally I will have to reboot.

Cheers.
[Nexus 7 (2013) Android Development] jb-:
I found this advanced option on only one of the ROMs I tried and it didn't work. Appeared to save and never connected and didn't show as saved. I didn't try again, just changed that router to a new ssid and not hidden, then moved on with life.
[Nexus 7 (2013) Android Development] :
Ignore
[Nexus 7 (2013) Android Development] lolcopter:
Really great work here, thank you OP! Followed instructions, copied files back over, flashed and restored all very quickly this morning. I don't use gapps at all, so didn't even bother with repartitioning at all. Very cool to see such great support for arguably the best Android tablet ever, thanks again!
[Nexus 7 (2013) Android Development] JPaps1:
Thanks to all developers who created this ROM.

For those who may have this ROM installed, how is battery life and performance?

Is this ROM daily driver worthy?

Does it have the same bug as previous lineage OS versions for this device where Netflix videos cannot play?
[Nexus 7 (2013) Android Development] ripee:
#16
[Nexus 7 (2013) Android Development] ripee:
And I refer you back to post #16. Please take note of the difference between the data and internal storage partitions.
[Nexus 7 (2013) Android Development] Deeco7:
I feel so dumb, for some reason I miss interpreted internal as main storage, forgive me for my late night antics lol.
[Nexus 7 (2013) Android Development] pi0:
Thanks for this great effort on L16! Regarding GApps, I did repartition. Here is the /system partition status after wipe and flash: (device: flo/32G)

Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p22 1.4G 752.6M 724.7M 51% /system

open_gapps-arm-9.0-stock-20190301.zip (628M) failed to flash due to insufficient space. But open_gapps-arm-9.0-full-20190301.zip (472M) installed successfully. I think it may worth mentioning in instructions to don't use something higher than full :)
[Nexus 7 (2013) Android Development] ripee:
If you wish to flash stock gapps you can always repartition to a bigger system image, but I didn't want to send less experienced users down a more dangerous path of potentially bricking their tablets by exploring options that are not as easy to implement as Clamor's tool.
[Nexus 7 (2013) Android Development] dealpapa1:
LineageOS 16 Pie now rolling out
[Nexus 7 (2013) Android Development] ripee:
Changelog

Build 0301 for both variants

* Synced with LineageOS sources.

Since today is the day that Pie has become official, it's a good day to build even though our tablets are not among the lucky few devices. You can be sure that the builds are stable enough as daily drivers, with the exception of NFC.
[Nexus 7 (2013) Android Development] :
Is it quite laggy for anyone else?
[Nexus 7 (2013) Android Development] SaySimon:
Hi everyone,

I am so glad that i am not the only one still using this awesome tablet!

I am totally new in all this process but it looks so easy so I decided to give it a go.

I have copied the 3 files in the tablet.

I have installed the twrp

I turned off my tablet

Pressed and hold power button + volume up

At this moment things are no good ahah

Instead of shows up the twrp spash screen I have android robot with the belly open and 'no command' under it. I read somewhere to press power and volume up so I have and now I have the menu like in picture.

I have wiped data/factory reset

I have wiped cache partition

Couldn't find install so I have tried apply and mount but both with no success.

Anyone can help me please?
[Nexus 7 (2013) Android Development] ipdev:
Your right, it is not too difficult. ;)

The recovery you see is still the stock android recovery. Either it was replaced by stock for some reason or it was not installed correctly. (Flashing error, bad file, user error?)

Traditionally it's done using fastboot. fastboot flash recovery NameOfRecoveryFile.img

LineageOS has good instructions for first time.

Install LineageOS on flo - Link

With the Pie builds, you will have to (re)partition your device.

Partitioning should only have to be done once.

Clamor's (re)partitioning is linked in the OP.

Uses up some free space, expands system, adds a partition for vendor, lose a little in userdata. Requires an updated TWRP to handle the new partition layout. Clamor is extremely helpful with (re)partitioning.

- Note:

Make sure you copy anything you want to save to a computer or cloud storage first. Forgot, you factory wiped already.:o

Perfect time for One Last Clean Factory Flash (Before you start modifying everything) just to make sure everything is updated and correct.

Nexus Factory Image - Link

Ignore the part in the Google instructions about re-locking the bootloader.

Cheers.
[Nexus 7 (2013) Android Development] SaySimon:
Thank you.

I have unlocked the fast boot.

I am trying to flash the recovery using fastboot,

PC sees the device, checked with fastboot devices

So I downloaded the twrp-3.2.3-flo.img on my PC and on the tablet (not sure where it goes) and at the command fastboot flash recovery twrp-3.2.3-flo.img says

Fastboot: error: cannot load 'twrp-3.2.3-flo.img': no such file or directory

And on the twrp app somewhere says device not rooted.

Obviously I am doing something wrong putting the recovery... I had a quick look for the repartition and it says 'flash repartition pack zip'. How?
[Nexus 7 (2013) Android Development] sir_bazz:
Try putting the twrp image file in the same directory, (on the PC), as your fastboot.exe

It will find it there.
[Nexus 7 (2013) Android Development] JoliOS:
Thanks again but i'm still having this problem #18 Any ideas?
[Nexus 7 (2013) Android Development] anykill:
I can install with no modified partition, after apply the script I cannot, it says invalid partition, ivalid argument, not found, something like that, but with not modified I cannot install GAPPS, says not enough space!

What should I do?

Nexus 7 flo 32gb
[Nexus 7 (2013) Android Development] anykill:
This is what happens
[Nexus 7 (2013) Android Development] ripee:
This is why you need to re-partition. There is not enough space in the stock system partition size to fit both lineage and gapps.

Please update your TWRP to the latest version. The official TWRP works fine.
[Nexus 7 (2013) Android Development] anykill:
I will try

thanks

--- Does not work... tried everything... stock, modify... format, reformat...
[Nexus 7 (2013) Android Development] slapshot2286:
Yeah I've tried this and it doesn't seem to work....though I will definitely try the screen thing. Hopefully that produces some results.
[Nexus 7 (2013) Android Development] kiraryu:
This is a kernel wifi driver bug.

It can't scan the hidden SSID when the first SSID is empty.
[Nexus 7 (2013) Android Development] ipdev:
That works too. Sometimes the simplest path is the best. ;)

The hidden network No/Yes was added in android 9. So most Pie roms will need this set to Yes.

Most of the time, you need to do it when you initially add the network.

It's been working for me and others.

Note:

Odd that I never noticed it before but, I never looked either.

Hidden networks do not show in the list even when connected.

WiFI is connected and works fine.

Attached screen shots from Poco F1 and Nexus7 flo for example.
[Nexus 7 (2013) Android Development] jb-:
I guess I don't know what you mean by first SSID is empty. I had it connected to my other router from when I did the start config and there were lots of others in the list, but not saved, just the one. Then I tried to add the hidden ssid, it saved, kinda seemed like it was doing something for a few seconds, then reconnected to the original one. I even tried having it forget the other router and doing the hidden. In no case did it show the hidden ssid as saved or connect to it (that I could tell). I'm not arguing, just this was my experience under my circumstances. I didn't document or otherwise keep track so it's all unsupported, but best as I recall from last week. Wait... what month is this? ;)
[Nexus 7 (2013) Android Development] slapshot2286:
Yeah if you could explain what you meant by that I'd appreciate it so I can fix this. Thanks!
[Nexus 7 (2013) Android Development] Nexus7_2013_Flo:
Just upgraded from 0206 to 0707. Mainly to get the security updates from the last 2 months. I do not upgrade that often, as I take the time to wipe everything, and setup the tablet from scratch again. In my case it isn't that hard, as I don' t have too much at my tablet. And I know that any issues are not related to dirty flashing, or from backup data. Once again everything went smooth, and tablet appears to run fine. Haven´t had any issues so far. Really love this ROM. Thanks Devs.
[Nexus 7 (2013) Android Development] chamo87:
last 1-2 months =

SYS UI crashes by anyone?

wake up is slow, laggy, or just imagine...?
[Nexus 7 (2013) Android Development] schnee1:
Wake up is slow for me in the last 2 builds, I takes a minute to get the tablet running at normal speed. Also some applications does not refresh in the background (eg Gmail does not notify about new mails)
[Nexus 7 (2013) Android Development] oldman_58:
Quick Question,

If I encrypted my Tablet and want to Decrypt the only thing I need to is:

fastboot format userdata

then reload the ROM..

Seems TWRP 3.3.1 will not recognize the password nor will it see Data, System etc (in userdata) as long as the tablet is encrypted.
[Nexus 7 (2013) Android Development] JT1510365:
For the love of GOD Please Don't encrypt your tablet if you want to stay on pie!!!!!

[MENTION=5480152]followmsi[/MENTION] stated in a post in one of his threads that encryption isn't working yet for pie I think its because of us repartitioning the system but I wouldn't encrypt your device if your running pie unless you know how to unbrick your nexus 7 2013 from your computer. It seems like you did if you need help with unbricking pm me:)
[Nexus 7 (2013) Android Development] oldman_58:
Thanks for your response, I was able to format and reload pie without issue.. It worked fine but could not unlock in TWRP for a backup.

Everything is back to normal.
[Nexus 7 (2013) Android Development] schnee1:
Latest 7/13 build looks much more responsive. Nice work!
[Nexus 7 (2013) Android Development] jordiiB:
Is it just me or screen autorotation is not working??

Thanks for the ROM btw!
[Nexus 7 (2013) Android Development] chamo87:
yes, autorotate sometimes stop working by me too. last version = need 3 restart bcs of this
[Nexus 7 (2013) Android Development] pitrus-:
Usually this is cause by glitchy ribbon cable between mainboard and daughterboard on the Nexus 7 2013. Can be fixed by adding some scotch tape over the connector to increase the pressure on the ribbon connector. There's youtube clips showing how to do this.

This is a known hardware fault of this device.

Skickat från min SM-T819 via Tapatalk
[Nexus 7 (2013) Android Development] Bronceado:
Updater error 4, there isn't any error like this in all the thread.

Anyway can explain me what does it mean? :fingers-crossed:
[Nexus 7 (2013) Android Development] DerGuteWolf:
Slimport problems

I am experiencing this, too. Are there any solutions so far?

---------- Post added at 07:55 PM ---------- Previous post was at 07:39 PM ----------

Unfortunatly this version also crashes for me sometimes, any other ideas what to do against this? Dos anybody know a (better) working version?
[Nexus 7 (2013) Android Development] schnee1:
Just as a note: Latest build still has this issue

Everything else works fine though
[Nexus 7 (2013) Android Development] Af0x:
I read that it is frowned to ask for ETA but does anyone know if the flo will come back to lineage-official?

If it will return will it most likely be save to upgrade this unofficial version by flashing the official build without wiping everything again?

Ty for your work & regards
[Nexus 7 (2013) Android Development] Ally L.:
First of all, thank you to the developers for your hard work! I just did a clean install of the July 27th build (flo) after repartitioning. The only issue I've had so far is not being able to connect to hidden WiFi networks -- I've tried previously posted solutions (setting the "hidden network" option to "yes," waiting with the screen off for a little while, or rebooting the tablet), but none has worked, so I had to unhide the SSID as a workaround. I'd appreciate suggestions on what else to try.
[Nexus 7 (2013) Android Development] r0ma6ka:
thanks for you

Not being able to connect to hidden WiFi networks too. Its very important to me - pls see what can do with it! Be waiting..
[Nexus 7 (2013) Android Development] MikiGry:
I've noticed that tablet struggles to play 720p 60fps videos from youtube (after a few minutes it starts playing normally with ocasional small hiccups). Is it some kind of bug or our old CPU + GPU isn"t strong enough ?
[Nexus 7 (2013) Android Development] Goon818:
[MENTION=6005084]ripee[/MENTION]

I want use the message to say thank you.

Without your work I would not use my Nexus. Perhaps I have to buy a new one.

Thanks
[Nexus 7 (2013) Android Development] Keltek:
Hello all,

I search the thread but didn't found any notice about problem I have with my N7 2013 LTE.

It is almost impossible to charge the tablet.

If I put the tablet on charger and keep it powered on, it is slowly discharge. Only method how to charge it is power the tablet off and connect it to charger.

Any workaround or fix around?
[Nexus 7 (2013) Android Development] pitrus-:
Sounds like you have NFC enabled, this can cause drain because of bug in driver, try disabling it.

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] lordnils:
Why isn't this mentioned in the starting post? :confused:

I followed all the steps, read the Q/A and known problems and started the usual setup. Encryption seemed to work fine but after reboot a message indicated the system was unable to boot, password was correct but decryption failed. Factory-reset seemed to work fine, the system is now not encrypted though.:(
[Nexus 7 (2013) Android Development] ripee:
Added 2 minutes ago.

If the instructions don't mention encryption, then it's unnecessary to get the rom to boot, since there's no point in encrypting a fresh installation without any user files on it that would need to be encrypted in the first place. ;)
[Nexus 7 (2013) Android Development] rho-bot:
Hi ripee,

I have installed your latest lineage-16.0-20190806-UNOFFICIAL-flo. Unfortunately, I get no battery stats. battery usage data for apps is n/a, only Display data is available (if selected "all data").

Does anyone else have this issue? Are there any tips how to fix?
[Nexus 7 (2013) Android Development] dealpapa1:
is pitrus build weekly now?
[Nexus 7 (2013) Android Development] ripee:
This thread is supposed to be about my builds, not pitrus's. But since he started using followmsi's sources, which is what I use, it doesn't matter.

I cannot speak for how often he will release his builds, but I release mine about once a week, as I wrote in the OP. I have reached out to him to divide the work of running builds and maintaining this thread.
[Nexus 7 (2013) Android Development] Jamin_1:
Just wanted to say thank you for this amazing work! I can't believe I am typing this on my Nexus 7 on Android P with complete functionality. Remarkable.
[Nexus 7 (2013) Android Development] ripee:
Q?
[Nexus 7 (2013) Android Development] Jamin_1:
You can tell that I am enjoying the weekend. Sorry for that. I edited my first post.
[Nexus 7 (2013) Android Development] ripee:
;) I thought you were one step ahead :D
[Nexus 7 (2013) Android Development] ripee:
Switching to pitrus-'s builds!

I have updated the links in the OP to point to his folders. He builds with the same sources as I do, which are followmsi's repos linked at the bottom of the OP. It will be up to him how often he build for deb and flo, but I will continue to maintain this thread and answer questions. I am working on other devices right now and my build environment doesn't have the space to keep building for deb and flo, but rest assured I still have my flo tablet and will enthusiastically and regularly flash pitrus-'s builds.
[Nexus 7 (2013) Android Development] Donlagos:
Thank for everything you did to keep our beloved Nexus 7 actual, can we do a dirty flash over your rom to update to pitrus-'s builds?
[Nexus 7 (2013) Android Development] pitrus-:
Yes you can, they're the same, only some build info esthetically differences (name of builder, email address and that sort).

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] 3dfxvoodoo:
Good work my friend. Cheers from Argentina
[Nexus 7 (2013) Android Development] dealpapa1:
oh yeah