yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] dealpapa1:
i saw two files with same name lineage-16.0-20190524-UNOFFICIAL-flo.zip
[Nexus 7 (2013) Android Development] ripee:
I thought I had accidentally delete 0524 of both deb and flo because Google Drive didn't update itself fast enough, so I re-uploaded both. Now I removed the extra copy.
[Nexus 7 (2013) Android Development] MaSaNRW:
Hi there,

I had these rotation issues as well, independent of the installed firmware. In the beginning the reboots fixed them, but some weeks ago that did not help anymore.

Proceed at your own risk!

After asking Mr. Google, I found out that this seems to be a hardware issue. What helped me was placing the tablet upside down on a hard surface (f.e. a table) and then (carefully, do not press too hard!) pressing the area around the N and the S of the Nexus logo with my fingers several times. After a reboot, rotation works without issues.

These tablets have an issue with the gyroscope/acceleration sensors or the cable connecting them to the mainboard. Pressing the described area loosens them and make them work again.

In some videos, there is also a description on how to fix this permanently.

Hope this helps some of you out there.

Cheers,

Marius
[Nexus 7 (2013) Android Development] asquartz:
Problem switching users

Thank you for this ROM which is working excellently on my flo. But for one problem.

I created a new user and switched to it, and the navigation bar disappeared. I checked settings to make sure it was configured to display the navbar, and that expanded desktop was turned off.

However, the navigation bar stays gone evenwhen I switch back to my original user. The only way to get it back is a reboot.

This was asked by someone else way back at post #18 but didn't get an answer then. I wonder if anyone has found a solution to this?

Thanks.
[Nexus 7 (2013) Android Development] proeprnorf:
Im trying to update but the recovery installer is giving me error 7

Even though my devices is flo it says that this rom is for flo and my devices is deb. tried wiping cache and still... any ideas ?
[Nexus 7 (2013) Android Development] ripee:
Update TWRP to 3.3.1-0.
[Nexus 7 (2013) Android Development] proeprnorf:
Thanks! That fixed it.
[Nexus 7 (2013) Android Development] n3kf:
Great ROM. Thanks to the developers. Running it on a 32gb Flo.

I do find that if I get too many apps open, it gets rather sluggish. If I remove some via recents, it goes back to normal. Any way to improve this? I can live with it.

Secondly, my calendar widget seems to be stuck in night mode. The calendar is set to light theme, but the widget is always dark. Some way to change it?

Thanks. And again this is a great ROM. Really appreciate the work.
[Nexus 7 (2013) Android Development] Nexus7_2013_Flo:
Just clean flashed the 0206 version, so far so good. It appears to run really well. Will see how it works in the coming days.
[Nexus 7 (2013) Android Development] abhijitv92:
The 0206 version is really great. Thank you for all the hard work developers.
[Nexus 7 (2013) Android Development] dealpapa1:
does 0602 has June 2019 Android Security Update?
[Nexus 7 (2013) Android Development] ripee:
It hasn't been merged yet, this is just a weekly build.
[Nexus 7 (2013) Android Development] keyra74:
a huuuuuuuuuuuuuuuuuuuuuuge thx. you made my nexus live again
[Nexus 7 (2013) Android Development] ripee:
Changelog

Build 0609 for both variants

* June security patch level.

* Synced with LineageOS sources.
[Nexus 7 (2013) Android Development] nocaldawg:
So do I reflash the updates or will this update OTA in the settings? Thanks
[Nexus 7 (2013) Android Development] Pajoe:
Sorry if off-topic: I found several references to Wickenberg releases in this thread, and even installed from https://lineageos.wickenberg.nu but can not find any information on those releases on XDA. I would like to learn more about them and how they differ to ripee 's version, I am guess Ripee releases are better.

thanks
[Nexus 7 (2013) Android Development] pitrus-:
Respect the thread and use Ripees builds. I think we both use the same manifest (followmsi) for builds, so I guess only difference is the support for OTA on my server.

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] Pajoe:
thanks for the information , I will try to remain more on topic of this thread
[Nexus 7 (2013) Android Development] dealpapa1:
you have daily build?
[Nexus 7 (2013) Android Development] chielmi:
This ROM really makes me happy. Somebody willing to maintain such an old device that's abandoned from official support from Lineage and such.

ROM is working fine! Haven't found any real issues. The Nexus 7 isn't the fastest anymore, but still more than usable.

Keep up the good work! :)
[Nexus 7 (2013) Android Development] ripee:
It's ok, as long as the discussion is on topic.

He does because he hosts them on a traditional server, so the URL of each new version matches it's zip filename. I cannot do that in mine because I host them on Google Drive and the fileID is only assigned after the file is uploaded, so no way to predict it.

All credit to followmsi and flex1911 ;)
[Nexus 7 (2013) Android Development] dealpapa1:
You can host your file on his server

Lol
[Nexus 7 (2013) Android Development] logitechor:
Been using the Nexus 7 for years now. Have consistently had a Custom ROM on it. Thank you very much for the ROM. For my needs excellent.
[Nexus 7 (2013) Android Development] MartinX3:
Using the june patch 2019 on my old nexus 7 2013 wifi.

Happy happy happy. <3
[Nexus 7 (2013) Android Development] xenokc:
How do I turn on SELinux enforcing?
[Nexus 7 (2013) Android Development] pitrus-:
You don't, it's not finished/working for/on this device.

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] schnee1:
Hi! I have a problem with Netflix. It used to work but now the latest update show as device not supported in the play store. Any idea why is it like that?

Thanks
[Nexus 7 (2013) Android Development] Ranbato:
Install an old version. I use 4.5.8 but it doesn't support downloads
[Nexus 7 (2013) Android Development] ripee:
Flash Magisk and enable Hide, then select the Play Store from the list.
[Nexus 7 (2013) Android Development] schnee1:
I don't have root on my device, but i tried this solution anyway. Unfortunately it did not work (or i am doing something wrong)

---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------

The last version i used from play store (before the June 6 update) worked fine even with the downloads....
[Nexus 7 (2013) Android Development] Ranbato:
Let me know if you get it working again. I have never been able to on a recent version of Netflix
[Nexus 7 (2013) Android Development] Heinz-:
Hi [MENTION=9350973]All[/MENTION], just one question: How do I update this unofficial LineageOS 16 from one release to the next one? The built-in updater does not work, so I have to download the new rom from ripee's Google Drive manually, and then? The updater worked as long as LineageOS 14 for the old Nexus 7 was still supported officially. I think I have to put the downloaded zip to a special directory as I had to do on LineageOS 14. I can't find any information on that topic.

Thanks for your support,

Heinz
[Nexus 7 (2013) Android Development] schnee1:
So far i was unable to solve the issue. The play store (in settings) shows as uncertified device and Magisk hide does not help. In Magisk if i test it shows that the device is failing the standard tests.....
[Nexus 7 (2013) Android Development] sir_bazz:
Just to rule out an issue I've been encountering with Magisk lately, can you try toggling the Magisk hide option in settings off and then on again.
[Nexus 7 (2013) Android Development] ttamo:
reboot to a recvovery, install the zip, and restart the device.
[Nexus 7 (2013) Android Development] schnee1:
Tried it and yes it solve the issue (device passes the safety net test) and playstore gets certified status. After reboot the setting resets unfortunately. However this did not help with the netflix issue, it still not supported on the device in play store. If i install the APK from other source, it starts, but quits with an error "unsupported device".

I was able to download the APK from this february from apk mirror, and it installs and works fine (even downloading shows works perfectly)
[Nexus 7 (2013) Android Development] Ranbato:
Which Feb version? I have never been able to play a downloaded show. Also, what Magisk modules?

Thanks
[Nexus 7 (2013) Android Development] schnee1:
Installed this version:

Netflix 6.26.1 build 15 31696

February 25, 2019

Version:6.26.1 build 15 31696

https://www.apkmirror.com/apk/netflix-inc/

TBH i am not sure if Magisk is required or not for this APK as i did not hide from netflix app only the playstore app
[Nexus 7 (2013) Android Development] ripee:
This is a temporary solution that doesn't really work because you'd have to do this every time you reboot.

I may have a solution to the Netflix problem. I have forked the device trees and replaced the proper build fingerprints with those of the Pixel 3, courtesy of Samsung Galaxy S4 developer, side. This helped the S4 pass, so perhaps it will help us. Not that it has anything to do with it, but the S4 uses the same msm8960 chipset as we do.

New builds tomorrow!
[Nexus 7 (2013) Android Development] Heinz-:
Exactly this doesn't work. That's why I ask.

Of course I can do a full backup of all my apps, wipe everything and install the new zip every week. but there was a more simple way by copying the zip to a system folder and installing it by the builtin update function.
[Nexus 7 (2013) Android Development] urbient:
[MENTION=276094]heinz[/MENTION] , what happens exactly if you "dirty flash" a new version over the old version in twrp ? wich error code or behavior do you encounter ? the internal update is not possible for unofficial roms as explained in this thread earlier . greetings
[Nexus 7 (2013) Android Development] sir_bazz:
Yes that's the same as what I'm seeing too.

Haven't been able to make time to try and narrow down the cause, but it only recently became an issue a week or so ago.

Only changes I've made since then are playstore updates so who knows.
[Nexus 7 (2013) Android Development] julla0:
What about widevine L1 for some apps like mycanal?
[Nexus 7 (2013) Android Development] SteamPlay43:
In build from June 20th it still desn't pass SafetyNET.
[Nexus 7 (2013) Android Development] ripee:
I'm still thinking about it...
[Nexus 7 (2013) Android Development] test011a:
Magiskhide off and on again helped. On everytime it reboots.
[Nexus 7 (2013) Android Development] ripee:
Perhaps the build fingerprints got blacklisted by Google?
[Nexus 7 (2013) Android Development] test011a:
I actually tried changing fingerprint with Magiskhide Props Config module a week ago. About 6 different fingerprint from the module's list. Did not helped. (I hope we are talking about the same fingerprint thing)

I end up using 0602 rom with Magisk 19.3. I have to turn off and on Magiskhide every reboot, but the latest Netflix form Google Store works well.

Is there any possibility that this is a problem with Magisk 19.3?
[Nexus 7 (2013) Android Development] ripee:
Perhaps. The correct value is in device-common.mk and the build fingerprint is the latest one.
[Nexus 7 (2013) Android Development] sir_bazz:
That was my thought as well.

If it were a ROM issue, I'd expect that toggling the hide option in Magisk wouldn't make any difference.

Unless I'm not understanding the Magisk hide process correctly?

Edit: And for the record, I'm on PEX ROM from Feb so this isn't a Lineage specific issue.
[Nexus 7 (2013) Android Development] VollNoob:
Hello everyone, yesterday I installed the latest build of this rom and it just works great, thank you for that.

But unfortunately, I cannot install Gapps. It constantly tells me that I do not have sufficient space. But how can this be? Could you help me out please? Many thanks in advance
[Nexus 7 (2013) Android Development] misterchambo:
See OP, you have to repartition your device.
[Nexus 7 (2013) Android Development] VollNoob:
Thanks a lot, I must have skipped that part :)
[Nexus 7 (2013) Android Development] dafiduck:
Pay attention to the gapps variant you want to install, in my case also after repartition the full version can't be installed so I used the micro version but users used the full version

---------- Post added at 07:40 ---------- Previous post was at 07:39 ----------

I have an annoying problem, when the boots end the dialog error "google play store keeps stopping" appears and disappears in loop making the tablet unusable, some other times the dialog stops appearing so the tablet can be used

Anyone has this problem?

I use the rom version 20190619.175105 and gapps arm-9.0-micro-20190622
[Nexus 7 (2013) Android Development] Heinz-:
OK, let's have a try...

Dirty flash the new LineageOS from ripee's Google Drive from June 20th over the one from June 9th without wiping anything.

Restart into recovery (TWRP 3.3.1-0)....

Install...

Choose Image; Install Image...

Confirm install...

"Warning: No file_contexts ... Patching system image unconditionally ... Script succeeded"

Reboot...

Hm... it seemed to work! :)

Sometimes I saw only the background image for a few seconds and then the screen shut off...

I'll watch this behaviour.

Thank you

Heinz
[Nexus 7 (2013) Android Development] ripee:
Changelog

Build 0623 for both variants

* Synced with LineageOS sources.

I tried playing around with the build fingerprint from the Pixel 3 for the purpose of having Magisk pass SafetyNet without having to toggle Magisk Hide off and back on, but it seems that either recent versions of Magisk aren't compatible with older devices such as ours, or the deb and flo build fingerprints may have been blacklisted or at least not longer supported by Google.

Anyway, sideloading Netflix works, and video plays without any problem, even right after failing the SafetyNet test in Magisk Manager. Ours aren't the only legacy device suffering from this inconvenience.
[Nexus 7 (2013) Android Development] dealpapa1:
time to give up google tablet. google already gave up
[Nexus 7 (2013) Android Development] Ranbato:
I have never been able to get recent Netflix to work -- and I am starting to wonder if it is the Pixel Magisk module I have been installing to run the Pixel launcher. I'm going to switch launchers and see if that makes a difference...
[Nexus 7 (2013) Android Development] Ranbato:
No Bueno. Also tried clearing Netflix data. Maybe I'll have to do a full wipe.
[Nexus 7 (2013) Android Development] dafiduck:
The display brightness level is lost at every reboot, is this a known bug?
[Nexus 7 (2013) Android Development] sir_bazz:
FYI......

Uninstalled the current ver of Magisk and Magisk Manager and reinstalled Magisk V19.2 and Magisk Manager V7.2.0 and all is good again.

At least for now anyway....it's only about 20mins but root access has survived a couple of reboots which is encouraging.

For those that may not be aware, older versions of Magisk are available at GitHub.
[Nexus 7 (2013) Android Development] abhijitv92:
Hi I am on build 0623 and have the deb variant. I tried screen mirroring to my firestick but the tablet goes black and back to the lock screen. Is this a known issue? Or I am the only one facing it. I have done a clean install after repartitioning the storage and the problem still persists.

Thanks to all the developers for their hard work and their support for this device.
[Nexus 7 (2013) Android Development] Nomelas:
has anyone been able to get safetynet to pass with this Rom? (Using magisk)

EDIT: looks like SELinux enforcement is disabled - any reason why that is?
[Nexus 7 (2013) Android Development] drmarble:
SELinux is permissive because it hasn't been set up yet. If you make selinux enforcing wifi doesn't work (among other things). It needs more work. I have been working on the selinux policies but it isn't easy. The source code is up there if you want to work on it. https://github.com/LineageOS/android_device_asus_flo Look at the permissions for init.flo.wifi.sh. That really needs work.
[Nexus 7 (2013) Android Development] ripee:
Setting the kernel to enforcing is the last step in preparing the sources for official support, which we will never get because followmsi has no interest devoting the time necessary to bring the sources up to the level of the LineageOS charter.

SELinux is basically a finely tuned set of exeptions in kernel security policy. It has to be properly set up so that all functions work with no unnecessary security holes being left open. This is as much an art as it is a science to do properly, and much too time consuming to be worth it if official support is not the goal.

followmsi's sources are linked at the bottom of the OP, which aren't the official ones at all ;) But the init.flo.wifi.sh file should be there, or one with a similar name.
[Nexus 7 (2013) Android Development] xbs:
Running latest build 20190623. Tablet discharged 75% in 17 hours of standby. Any ideas why is this happening? Cheers
[Nexus 7 (2013) Android Development] icanfly77:
Thanks to dev for this just installed now after taking a while to get my head around the re partition process etc

Anyway, couldn't seem to find much info but what are the add ons addonsu-16.0-arm-signed.zip/addonsu-remove-16.0-arm-signed.zip and Magisk for?

I sort of figured addonsu would add the superuser app and remove would remove it? If that is the case cool, but then I read that Magisk provides root as well?? So I am just confused if I even need any of these add ons? For sure addonsu if it does what I think it does, but if magisk does root as well, does that mean I decide if I want addon su or magisk for root app? Thanks
[Nexus 7 (2013) Android Development] pitrus-:
You can see the su addon as a much simpler alternativ to Magisk with no support for root hiding and Magisk modules. It's ment for those that wants the bare minimum root functionality.

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] julla0:
NFC on?
[Nexus 7 (2013) Android Development] xbs:
Yes. Going to turn NFC off and check again.

Thanks
[Nexus 7 (2013) Android Development] ipdev:
It's not the fingerprint.

There is something else that changed that caused it.

As you mentioned, it is affecting more devices.

I'm still running AEX from March on my flo and Netflix is available to download.

It's probably not SafetyNet or Play certification, since I fail both on my Pixel 3a XL Q-Beta and can still install Netflix from PlayStore.

My Pocophone on the other hand, was able to install Netflix from PlayStore.

Since the beginning of the month, or so, Netflix is not available in PlayStore.

My Nexus 6P, unofficial lineage 16 and the same arm64 gapps package I used on my Poco, Netflix is available. So Gapps is out of the question also.

Maybe some odd line in a security update?

OT.

Note:

Miui has been working on getting full HD with Netflix. Poco was even updated to widevine L1. So it should have a green light from Netflix.

Also has Netflix related lines in the stock system/build.prop

#Netflix custom property
ro.netflix.bsp_rev=Q845-05000-1

Thought there was more? I'll have to mount a few older images to check.

I haven't had time but, been curious to see what would happen if I added the props to my Nexus 7.

Cheers. :)
[Nexus 7 (2013) Android Development] ripee:
After toggling Magisk Hide, Netflix sometimes appears in the store for me, sometimes not. Without Magisk, forget it, so I think it has to do with newer Magisk not being entirely compatible with older devices, some of which aren't powerful enough to run Netflix in HD anyway, unlike ours.

[MENTION=7280276]ipdev[/MENTION], do your other devices that have Netflix in the store have enforcing kernels? Ours is permissive and most likely always will be, but if Netflix sometimes pops up in my play store, heck knows.
[Nexus 7 (2013) Android Development] ipdev:
So Netflix's website sucks.

Unless you have help links. Then you can gat an older download and instructions on how to disable PlayStore updates.

It seems all Pixel's are on Netflix's current device list, along with Nexus 5, 5X, 6, 7 (2013), 9 and 9 LTE.

Xiaomi POCO F1 is also on the list.

Not sure how current they keep the list.

My main Nexus 7 (flo) I use daily, is Permissive.

AEX and EX kernel from March. It was clean flashed with the Magisk-Debug at the time. Magisk (debug) has only been updated since.

My Nexus 6P and Poco both Enforcing. (Magisk-Debug)

Pixel 3a, unlocked bootloader, Q-Beta with no modifications. (Enforcing)

It doesn't seem to make sense to me.

It's mixed and I haven't been able to figure it out.

There should be some kind of pattern. Maybe it is Magisk?

I did a little testing tonight on my (secondary) flo and after figuring out a few user errors, Didn't realized I downloaded the AEX + GApps build., I gave a few things a try.

Didn't have time to test everything but, even a clean flash of the AEX march build failed.

Dirty flashing the EX kernel failed. Adding the current Magisk-debug also failed.

I should have time tomorrow night to test some older Magisk builds.
[Nexus 7 (2013) Android Development] ripee:
The Nexus and Pixel devices you listed as being on Netflix's list refer to stock roms with locked bootloaders.

All in all, the most important thing is that new versions of Netflix can be sideloaded and run properly. That they don't appear in the store is inconvenient, but a small price to pay for being 3 full versions ahead of stock.
[Nexus 7 (2013) Android Development] sir_bazz:
Haven't had a chance to do any more testing but just quickly chiming in to say that haven't had any issue with losing root since rolling back to Magisk 19.2.

Not a Netflix user so can't test that but I do see the Netflix app in the store if that means anything.

Was hoping to test upgrading to the current version of Magisk, (to rule out the possibility of the reinstallation being the fix rather than the older version being the fix), but finding time is not easy at the moment.
[Nexus 7 (2013) Android Development] Ranbato:
See that is where I can't figure out what I am doing wrong. Yesterday I wiped system and data and flashed 0623 ROM, Open Gapps, and Magisk.

Signed in to Google, installed Netflix (not there so installed from apkmirror), toggled Magisk hide and hid Netflix.

Still won't stream.
[Nexus 7 (2013) Android Development] Ranbato:
Figured it out. If you ever install es file explorer Netflix will never work again, even if you uninstall it.
[Nexus 7 (2013) Android Development] schnee1:
Since i downgraded to magisk 19.2 i have no problem with having Netflix showing up in the play store. I think there is a bug in 19.3, i will test and hen try to report it to magisk.

Now that netflix latest is installed i have another problem with playback: after installation and logging into Netflix, i can start streaming a movie, but after ~30-60 secs the video stops with an error (5,7). After this error i can't play anything from Netflix (either loading video but never starts or the above error). If i clear the app data for Netflix and login again, i am able to watch the video for 30-60 secs again.....

Magisk hide is enabled for Netflix and Play Store. I also have ES filemanager installed, not sure if it has any relation to the error (as suggested in one of the posts), as it was installed long time ago and Netflix did work fine in May.
[Nexus 7 (2013) Android Development] Ranbato:
That is the exact error I was experiencing until I wiped my system. Even uninstalling es file manager didn't fix it.
[Nexus 7 (2013) Android Development] schnee1:
Wiped the device and reinstalled it without ES File explorer, but the result is the same: after 30-60 secs i receive the Error 5,7 from Netflix.....