yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Galbotorix:
So I flashed the partitioner and the twrp but my internal storage shows 0mb and It doesn't show up on my computer and the data partition doesn't exist and I have a vendor partition pls help

Edit: so I repartitioned vendor to data and pushed the partitioning zip using nrt and ran it again, That worked.
[Nexus 7 (2013) Android Development] entombor2:
Security>Lock screen prefs>change shortcuts

do the toggles here do nothing? or are they bugged? I would like to be able to open the camera app without having to unlock.
[Nexus 7 (2013) Android Development] melas zepheos:
Magisk not quiet right

I am a bit stuck. I have managed to update my flo from lineage 14 to 16 (thank you for the awesome update developers :highfive: ) using TWRP. And that is working really well (only issue I have found is the buttons at the bottom have lines through them sometimes but they work).

I have not installed any form of GApps (experimenting with a google free device).

The area I am stuck is with Magisk. I have installed Magisk 20.1 with manager 7.4.0 and it seems to have worked and be running but I have no ctsProfile or basicIntegrity visible. I have tried making sure that the app has access to all the data it could want as suggested on the didgeridoohan Magisk help pages and I have uninstalled it and reinstalled it and no difference.

Can someone confirm that Magisk 20.1 works with Lineage 16.0 on flo and I should be seeing these things? Does anyone have any ideas how to get the SafetyNet check items visible? The next place I will trying to ask advice is the Magisk threads but wanted to make sure it works with the device...

Thank you for any help.

EDIT: So kinda solved my problem redid everything and but this time installed opengapps and magisk. All successful with the install and stuff and looking in Magisk Manager and SafetyNet Check functionality is there.
[Nexus 7 (2013) Android Development] pbrown77:
So no one else experienced this or have suggestions? I only needed to run the partitioner image yes? Then update twrp then lineage image and gapps. With the suggested wipes as per the description for lineage install.

No need for the magisk install is there?
[Nexus 7 (2013) Android Development] Jean_C:
If i delete webview there is just enough space to install nano gaps. If that succeeds, there are apk's for webview. Would that work? :)
[Nexus 7 (2013) Android Development] zentara:
slight problem with re-partitioning and solution

Hi, I just successfully installed your LineageOS 16 on my Nexus 7 LTE. I had a few glitches, first was after TWRP install, I needed to use TWRP's sideload to get everything in, and it worked fine.

A second glitch which applies to this thread, was that after running the Repartition script, my system dir was unusable and throwing errors on the Lineage install. In TWRP, I went to modify partitions, and had to reformat /system as EXT4 in order for it to work. It had to be formatted.
[Nexus 7 (2013) Android Development] M4DNESSS:
Hello. Is still have an issue regarding posting a photo straight from camera in all (literally all) apps with such function (Viber, Telegram, Aliexpress, etc.) and I cannot find a solution. Reflashing, factory settings do not help. Please give an idea what problem can cause such a thing.

Once again, when I I try to send a photo message (straight from camera), tablet freezes an after 10-20 seconds reboots. Every time.
[Nexus 7 (2013) Android Development] ripee:
Yes, this is necessary after re-partitioning, as the new partitions have to be prepared for use by being formatted.
[Nexus 7 (2013) Android Development] slapshot2286:
I think there may be a potential bug here. I did a clean install on my Deb, verified the correct build for Deb (latest), but it does not detect a SIM and has zero cell connectivity. I've verified that the SIM works fine with LOS 14 and the new 17 just fine, but no luck with this build (which I really, really like and want to use). This is a Verizon LTE SIM by the way.

The reason I think this is a bug of some type is because when I look at the data usage, it says 2.14GB used, though obviously this is a fresh install.

I've verified that the radio is on, and is picking up LTE towers (and only the correct Verizon ones) as well.

Anyone else having issues like this? OP have any ideas?

Thanks for the hard work as usual.
[Nexus 7 (2013) Android Development] schnee1:
The ota server seems to be down. I see ota downloads in the list till 11th of December. But non of them are downloadable
[Nexus 7 (2013) Android Development] MartinX3:
I can confirm that in my country.
[Nexus 7 (2013) Android Development] cyklop82:
Netflix is not playing any videos Error 57
[Nexus 7 (2013) Android Development] anykill:
I just cant´s install after apply the script to resize partitions...

only stock
[Nexus 7 (2013) Android Development] autobulb:
Strange, I ran the Clamor script successfully but cannot fit even Pico Gapps. Any advice would be appreciated.

Edit: nevermind, can flash the full package after retrying. I guess it failed last time and I didn't notice the error.
[Nexus 7 (2013) Android Development] sir_bazz:
Try this one.

https://xdaforums.com/showpost.php?p=78703434&postcount=1971

That's the one I used when reluctantly repartioning for the first time, and it worked without issue.
[Nexus 7 (2013) Android Development] itclub852:
Support Roms
[Nexus 7 (2013) Android Development] Zarphus:
slimport

attempting to use slimport HDMI hard locks the device. (worked fine on stock rom) if you need logs, let me know, but the way it locks up, i dont know if i can get them.
[Nexus 7 (2013) Android Development] anykill:
That works so far!

Thank you!!!!
[Nexus 7 (2013) Android Development] JamesTanner:
Random Reboots

Has anyone else got problem with this ROM randomly rebooting? I flashed this a day ago, and it's rebooted itself 7 times now (So inside of 24 hours) for no apparent reason. Not even using it - it's simply plugged in to the charger sat on my desk doing nothing, and it just suddenly reboots. I only notice because the Google logo appears followed by the LineageOS boot animation - which of course turns on the display
[Nexus 7 (2013) Android Development] Goon818:
Sorry. I have no problem with rebooting. This ROM is stable on my device.
[Nexus 7 (2013) Android Development] JT1510365:
hey ripee consider putting your builds on androidfilehost
[Nexus 7 (2013) Android Development] Deeco7:
I've noticed some slow downs from screen off, not sure if that's down to doze being aggressive when woken up, but it takes quite a long time to wake up the screen, around 10 seconds.

Also, in some instances the tablet becomes really sluggish and is slow to respond. I can provide logcats If needed, thanks.

Appreciate your work!
[Nexus 7 (2013) Android Development] Jay Rock:
This works pretty good all things considered. All I need now is a custom kernel to enable faster charging and a performance profile. Thanks!
[Nexus 7 (2013) Android Development] Jens HB:
Hi,

I tried yesterday to install it and everything looks fine in regards to installation. But after I wasn't able to connect to a hidden wifi! I know that in Android 9 there is a new option at wifi configuration to say hidden Wifi = yes/no.

Is this problem related to Pie or maybe related to this ROM. Did someone else have the same issue?

Kind regards,

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

Build 0308 for both variants

* March android security patch level,

* Synced with LineageOS sources.
[Nexus 7 (2013) Android Development] xenokc:
March 8 update looking good. I was having somewhat fast battery drain with 3/1 and doesn't seem so with 3/8.
[Nexus 7 (2013) Android Development] sacto7:
I think it is android. android 6 has slight problem with hidden wifi. android 7, 8, 9 have bigger problem with hidden wifi from my experiences. kobo even has more difficulty connecting.

The 1st solution was just to broadcast the ssid & after the tablet connected, disable the ssid broadcast again.

But I have now surrendered & enable broadcast, changed the ssid & password. Was not able to find why android won't just use the entered ssid & connect; seems to me that using the entered ssid means android is going thru many gyrations to arrive at the entered ssid to try to connect like checking all hidden ssids within range.
[Nexus 7 (2013) Android Development] Bingley:
I've tried AEX aosp rom for this device and noticed lots of battery drain and it feeling a little laggy (well, it's an old device so...) but then flashed the last official Google image, Android 6, and it's super smooth and fast in comparison. I get that new versions are nice to have but they are so laggy or slow compared to 6. I'll try this again but not holding much hope compared to stock, sadly.
[Nexus 7 (2013) Android Development] autobulb:
Can someone advise the most efficient way to update? My guess is flash, gapps, clear cache?
[Nexus 7 (2013) Android Development] me98278:
Please try PixelExperience_flo created by followmsi. You can download PixelExperience_flo-9.0-20190206-0806-UNOFFICIAL.zip from the link:

Edit : Realized I cannot post the link ... But you can find the link to the androidfilehost in first post of the AEX thread
[Nexus 7 (2013) Android Development] :
Post in the correct thread. This is not pixel experience.
[Nexus 7 (2013) Android Development] rho-bot:
Same for me, OTA shows available updates, but download fails (network connection error).

Manual download via PC & update via cable worked.
[Nexus 7 (2013) Android Development] cliffyb:
I typed out a long story of dumb steps I took but I think the correct solution for why I was stuck at the bootloader was because I skipped the "install twrp as a system app" option.
[Nexus 7 (2013) Android Development] schnee1:
Yes manual download works. However the newest image is from Dec 11, so the automated builds are down too
[Nexus 7 (2013) Android Development] jordiiB:
It can't be that because this is just an application. Make sure your partitions have been formated so they can be flashed
[Nexus 7 (2013) Android Development] knodderdachs:
Hi,

I installed lineage-16.0-20191211-UNOFFICIAL-flo a few days ago and tried to add my wifi network. Unfortunately there seems to be a bug with passwords longer than 59 chars. If I enter anything longer than 59 chars the Submit button gets deactivated. If the password is 59 chars I can submit the password, but of course, I cannot connect to the wifi network.

Could you please fix that?
[Nexus 7 (2013) Android Development] Pea123:
Hi, I have a problem with wifi - channel 13 does not work correctly. But this channel 13 is fine to use in Europe.

I can connect to my wifi at channel 13 but tablet never reconnects automatically, it ignores that wifi later. I believe this is linked to location restriction for channel 13.

This Nexus 7 Flo does not have SIM card slot, so how to change location configuration to allow wifi channel 13 working correctly? Thank you
[Nexus 7 (2013) Android Development] Cessnuks:
Good morning,

could someone tell me how to manually update?

I allready downloaded the latest build ... but i don't know how to apply it as an "update".

Kind regards
[Nexus 7 (2013) Android Development] Jump1ng:
If you have already downloaded it (http://lineageos.wickenberg.nu/builds) then boot into recovery and flash the latest full zip in TWRP recovery.
[Nexus 7 (2013) Android Development] kozmo2k4:
On the last two nightlies ( flo, 12.27 and 12/28), I have lost screen rotation.

In CPUz, it shows missing the orientation sensor.

Has anyone else experienced the same?
[Nexus 7 (2013) Android Development] edison0354:
Are you sure it's not a hardware issue? Nexus 7 sensor connection is not sable... You can try to press on the back around logo 'N', at least I remember that's the location. Try to Google for this issue. I fixed mine with this way.
[Nexus 7 (2013) Android Development] kozmo2k4:
"Press around the back N logo"? Not sure I'm following you there....
[Nexus 7 (2013) Android Development] darkvicious:
Thank you for continuing to support my nexus 7
[Nexus 7 (2013) Android Development] kozmo2k4:
Just flashed 12/29 (flo), and the rotation is back, along with other sensors.

Peculiar...
[Nexus 7 (2013) Android Development] the-weatherman:
I'm impressed how well Android 9 runs on that old device. Thank you OP for maintaining this build and giving my tablet a second life! Donated
[Nexus 7 (2013) Android Development] kozmo2k4:
100% agreed.
[Nexus 7 (2013) Android Development] mcsmart:
Does anybody here have working 5 GHz wifi with DFS channels? It seems like no channels beyond 52+ are working on my device, although the wifi region is set correctly.
[Nexus 7 (2013) Android Development] pitrus-:
I have multiple devices not working with the higher DFS channels. So I just configured UniFi AI in the controller not to use these channels when auto optimizing the wifi. In other words, I fixed it on the wifi side instead as there's not much to do about buggy drivers.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] rho-bot:
WIFI primacom driver was staging status, and several things were borked since LOS14.1

https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/183317

Unfortunately, BUGBASH-904 is non-existing anymore. But there were issues with DFS channels, and when region-setting, it could even break 5GHz at all, as the regions were not properly defined. So better to leave it unset.

There were some suggestions to update the primacom driver with newer one of a different device, but unfortunately never merged. by Sean..

Maybe some cherrypicking? https://review.lineageos.org/q/prima
[Nexus 7 (2013) Android Development] Spielmops:
I did also a clean install on my deb-device, tested it some hours with wifi and the OS runs fine. I inserted a SIM. could unlock the SIM and a while later surfed on LTE-network. At the next restart the Nexus crashed a second after the SIM-unlock-screen - I had to press the power-key for 15 seconds. Tried again, same result.

Removed the SIM-Pin on another phone and tried again. The Nexus started fine, but did not connect to any mobile network. I then tried to search for networks manuell, so I switched of the "automatic connect", but got no "search networks", after some seconds the switch "automatic connect" switched to "on" y itself.

After about a quarter of an hour I had network, but no connection (network level is more than OK here).

Some time later I had to reboot (backup via TWRP) and the tablet crashed hard the moment when the SIM-card was detected (same time, when the SIM-pin is asked).

I then ended my experience with a SIM, I have the feeling, that it is a bug.

Additional information: the stock-ROM before LineageOS was 6.01, so I think, the firmware is as new as possible.

Spielmops
[Nexus 7 (2013) Android Development] moleculezz:
Hi,

I went through the process of unlocking bootloader. I flashed TWRP. Then did repartition and flashed the TWRP UA. All with success.

I flashed the ROM w/ Gapps and addonsu, but the device won't boot. It shows a turquoise arch with a circle going back and forth for a while. Then reboots into TRWP.

Anyone know what the problem might be and what I need test?
[Nexus 7 (2013) Android Development] pitrus-:
I suppose it should work with addonsu even though Lineage dropped support for it since everyones using Magisk nowadays.

Skickat från min GM1913 via Tapatalk
[Nexus 7 (2013) Android Development] moleculezz:
Is it required to use addonsu or magisk?

Also, does it matter in what order I flashed the zip files?

I did: ROM, Gapps then addonsu. Then did reboot.
[Nexus 7 (2013) Android Development] pitrus-:
I would skip the retired addonsu and go for Magisk instead, that's what I'm using on mine and it works great.

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

I realized that I installed the Deb IMG on a Flo device!?

Now I'm wondering if this could cause any problems or if it reduces performance?

I think I installed Deb IMG because I had problems installing the Flo IMG... But I'm not sure if that was the reason or if I just mixed things up.

Kind regards

Edit:

I checked it again.

In fastboot screen it says -

PRODUCT NAME - Flo

VARIANT - Flo 16G

So I guess it's a Flo. But how can I get rid of the fact that I can only install Deb image (alltough it's a Flo device)?

EDIT2:

After having an epiphany that night i could solve the Problem.

I flashed factory image and then i did everything step by step a described in the first post.

Now I am happy and everything works perfectly.

Thanks to everyone for the great work (and the great FAQ)
[Nexus 7 (2013) Android Development] jw243:
Is it still true, that data partition on LOS16 cannot be encrypted? On LOS17.1, encryption was no problem at all.

Could SELinux be set to "enforcing" in future updates?

Would it be possible to include a "double tap to wake up" feature into the kernel?

Thanks for the great work.
[Nexus 7 (2013) Android Development] drinkypoo:
Can't log in a second user. When touching the icon in the upper left to switch users from the lock screen, I'm prompted to enter my pin to unlock...
[Nexus 7 (2013) Android Development] leetripper:
pitrus server seems to be down :(
[Nexus 7 (2013) Android Development] moleculezz:
How did you install Magisk? Which method did you use?

I am trying to figure out, but I find the documentation a bit confusing.

Also, can I just flash on top of what I have? Just have to wipe everything?
[Nexus 7 (2013) Android Development] pitrus-:
It was, only temporary. [emoji4] Now there's a buildbot up and flo/deb builds for both lineage 16 and 17. Builds untested as of yet as I haven't gotten around to do it myself, so try them at your own risk (make backup).

Haven't figured how to bake in the OTA url, and builds are signed with a new key so you have to untick the control in TWRP.

Update: OTA is via working again.

My daily builds available at https://lineageos.wickenberg.nu
[Nexus 7 (2013) Android Development] c_i_r_r_r_u_s:
THX!

Running this ROM on the Nexus7 since 1 year know. Works almost great, thanks for all the work and support!
[Nexus 7 (2013) Android Development] pitrus-:
All these questions aren't ROM specific, you should ask questions in the Magisk thread.

I can't tell if the old legacy root will cause problems with Magisk, but if it does, you should just format system partition and reflash LineageOS, Opengapps Nano and Magisk 20.3 zip and you should be good.

Check out my LOS daily builds at https://lineageos.wickenberg.nu
[Nexus 7 (2013) Android Development] schnee1:
I am trying to install the latest 17.1 build but it does not succeed. I even went back to the stock image and started from there again, but still no success. The installation goes fine, no errors. But when i try to boot the OS i only get the lineage OS boot screen (the arch with the moving circle) and after several minutes the tablet reboots into recovery.

I tried to move back to 16.0 build, but now have the same results with that too.

I tried both with and without Gapps.

Any idea what is going wrong, how could i debug the boot process? The device shows up while in am in recovery and i can connect with ADB, but it does not show up during the boot attempt..

Thanks
[Nexus 7 (2013) Android Development] ipdev:
Make sure to backup what you want to save to somewhere other than the device.

Do a clean install.

If it reboots back into recovery, connect to your computer and use adb to pull the kernel log.

adb pull /proc/last_kmsg

You can also modify the default.prop to make the device insecure.

I'd have to double check on this device where and what file name.

If it boots far enough for adb to start you can also grab a logcat on boot.

# Add or change to.

ro.adb.secure=0

ro.secure=0

ro.debuggable=1

Best of luck. :)

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] schnee1:
Thanks for the help. I grabbed some logs if somebody interested i can share it. After grabbing the logs i was able to resolve the issue as on other forums i read that installing TWRP on the boot could cause such issues. I disabled TWRP installation and the tablet booted normally. I will play with the settings if it happens always or only if i install the app as system app.
[Nexus 7 (2013) Android Development] moleculezz:
Thanks, it's booting now.
[Nexus 7 (2013) Android Development] DeviceGuru:
Hey, I just installed this on my beloved old Nexus 7 2013, and everything appears to be working flawlessly! Hats off to the dev!! I was particularly impressed by the easy-to-follow installation process and, especially, the automated repartitioning script.

One question: in Settings > System > Updater, there's an available Feb 24, 2020 (363MB) LineageOS 16.0 image download link, tempting me to install it. Should I now be doing that?

Well, I'm going ahead and doing the available updates. Feb 24 and also Feb 25. Lookin' good :)
[Nexus 7 (2013) Android Development] maruchandd:
I'm having trouble updating TWRP. I have 2.8.xx TWRP on my flo (which is lingering with android 5.1.1).

Fails flashing within twrp and gives this from adp on pc

Anyone here experience this or know the solution? I don't want to brick this guy
[Nexus 7 (2013) Android Development] rho-bot:
Have you repartitioned the device before flashing revovery?

If not, then try with official TWRP from here first https://dl.twrp.me/flo/

Then repartition, then update TWRP to the one above (it is bigger than the original one).
[Nexus 7 (2013) Android Development] pitrus-:
You should follow Clamors repartition guide here

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

Check out my LOS daily builds at https://lineageos.wickenberg.nu
[Nexus 7 (2013) Android Development] maruchandd:
I have not tried repartitioning yet because the guides recommend you have at least 3.3.1.0 installed before you try to run the partition script. are you sure repartitioning in my current 2.8.x.x version will be ok?

thanks for the reply, I did go there and some suggested it's important to use the latest version of twrp before partitioning. Would it be ok to try to repartition it with my older version of twrp as above quoted user recommends? if not i need to get twrp updated first somehow

any suggestions on what I should wipe or clean in order to potentially fix this error and allow upgrading recovery flash version of twrp without bricking it?

EDIT: I managed to get it working, description is here https://xdaforums.com/showpost.php?p=81818907&postcount=272

IT turned out repartitioning the device was not necessary, the newest twrp installed and works without having done any repartition
[Nexus 7 (2013) Android Development] pitrus-:
As long as your version of TWRP isn't from the time the dinosaurs roamed this planet, you should just do as in the clamor guide, that's what I did and it worked fine and therefore I've never had to do it again as my device is future proof.

After repartitioning your have to at a bare minimum use the old special made TWRP as in the guide, but even better is to user the latest official as it handles repartitioned devices.

From there skies the limits what you do with your Nexus 7 2013. [emoji451]

Check out my LOS daily builds at https://lineageos.wickenberg.nu
[Nexus 7 (2013) Android Development] SergioTeddy:
I'm receiving Bad Gateway when trying to download
[Nexus 7 (2013) Android Development] rho-bot:
Please read my post again
[Nexus 7 (2013) Android Development] anivegmin:
Just installed this ROM and everything seems to be working fine but just checking in security settings I noticed that SELinux is disabled. Is this normal for this ROM or an error on my device? Can it be enabled? Thanks.
[Nexus 7 (2013) Android Development] pitrus-:
Accomplishing SELinux on older devices with outdated blobs and shims for making things work is if not impossible, more like painting Mona Lisa. If we would enable it, it would most probably break lots of functions.

Check out my LOS daily builds at https://lineageos.wickenberg.nu