yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] Siggyceline:
Yep, definitely R/W in Root Explorer. I can rename or delete the original file in the specified directory from Root Explorer, but cannot copy (write) the new proper file to that location. It gives "copy failed" every time. In TWRP Recovery File Manager, no files or subdirectories are showing in that /vendor/ directory at all. So it seems to me that something has changed and is wonky between Lineage 14.1 and 17.1. I had suspected it is something with how Google introduced something new for file management /permissions between those Android revisions?
[Nexus 7 (2013) Android Development] Af0x:
Hello, I can´t use the updater. It says "installation failed". Is this a known bug? Regards
[Nexus 7 (2013) Android Development] NTGDeveloper:
What's the issue with installing GApps on Lineage Recovery? Lineage signs the update packages for official LineageOS images. lineage recovery makes you accept another prompt in order to install unsigned packages such as Google apps. Try using Lineage Recovery again, and while you sideload/install ZIP, pay attention to the device and accept an "Install Anyway" prompt or something.
[Nexus 7 (2013) Android Development] ud4:
Fixed now
[Nexus 7 (2013) Android Development] :
Thanks a lot for fixing this, works like a charm!

I've just resurrected my 2013 Nexus 7 flox and I am happy again with it.

So far, I didn't find any issues.

So I just registered to XDA to simply say: Thanks a lot for the great work, I realy appreciate your effort!
[Nexus 7 (2013) Android Development] esykas:
everything ok on my Nexus

App Store ok under Magisk

Netflix supported

Pubg supported

thanks for all
[Nexus 7 (2013) Android Development] bertans:
Confirmed... fixed with build 20210208, worked with build 20210215.

Nice job ud4, no more issues so far! :cool:

With two Nexus 7 brought back to life, I owe you a beer (at least). Paypal?

A
[Nexus 7 (2013) Android Development] killeriq:
any update on DEB? thanks
[Nexus 7 (2013) Android Development] stanislav.bebej:
Hello to everyone,

first of all big thank you to all the developers keeping our beloved devices alive and up to date.

Today I installed the latest version of LineageOS (lineage-17.1-20210222-nightly-flox-signed.zip) and Google Apps (open_gapps-arm-10.0-nano-20210224.zip) using LineageOS recovery (lineage-17.1-20210222-recovery-flox.img).

I signed in using my google account. Using google play store I am unable to use any of my previously purchased applications (it wants me to pay for them again). I do not see them in my family library neither. What's funny is when I go to the play store using my computer web browser and "send" the purchased app to my Nexus 7 device it gets installed.

When using google play movies I am unable to play any of the purchased movies, nor download them. I get "Playback isn't supported on this device" error.

I tried several reboots, installing Android system webview, factory reset but nothing helped.

Do you happen to know how to fix my issue or is this expected when using this ROM?

Thank you for any advice.

Edit: just like that the purchases and family library started working today. The play movies however still cannot play any of my movies.
[Nexus 7 (2013) Android Development] C Karthik:
The camera app gives the error 'Can't connect to camera' when switching to video mode. Is anyone else facing this issue?
[Nexus 7 (2013) Android Development] r1t1l3n:
Installed + ElementalX Kernel

This build is extremely responsive and a much better expereince than the ver 14.1 build I was using before

Cheer! and thank you for your hard work!
[Nexus 7 (2013) Android Development] ipdev:
Good to see flo is back on the official build list. :)

I have been wondering about this for a while.

BOARD_KERNEL_CMDLINE += vmalloc=340M

android_device_asus_flox BoardConfigCommon.mk - GitHub Link

Is setting vmalloc to 340M still needed?

If so, is 340M still the correct value to set?

As expected, if I set it too low or too excessive, I had issues with the rom.

When testing.

Simply removing the predefined vmalloc value I did not experience a negative effect.

Might be a placebo but, removing it seemed to have a positive effect.

Cheers. :cowboy:

PS.

I know it merged in CAF for SDK21 (Lollipop)

Increase vmalloc size source.codeaurora.org - Link
[Nexus 7 (2013) Android Development] atiska007:
Dear All,

please help! I made the progress of repartition:

.
.
mke2fs 1.44.4 (18-Aug-2018)
Discarding device blocks: done
Creating filesystem with 6997491 4k blocks and 1749664 inodes
Filesystem UUID: 094fddb5-d6e9-4e7e-9cde-eb6dc22a720c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

2048+0 records in
2048+0 records out
1048576 bytes (1.0 M) copied, 0.213348 s, 4.6 M/s
20480+0 records in
20480+0 records out
10485760 bytes (10 M) copied, 2.091614 s, 4.7 M/s

Seems it finished well.

Flashed recovery: fastboot flash recovery lineage-17.1-20210301-recovery-flox.img

And now when try to reboot recovery (it is working) and start Recovery mode, I got an error on Nexus:

E:Failed to bind mount /mnt/staging/emulated/media/0 to... no such file or directory

E:emulated failed to bind mount /mnt/stagign/emulated no such file or directory

So cannot make a factory reset now and cannot flash lineage installation package..

What should I do now? Did I bricked my tablet? :S
[Nexus 7 (2013) Android Development] npjohnson:
those are both expected - just factory reset.
[Nexus 7 (2013) Android Development] Siggyceline:
Anybody know how I can get DFS channels working again like I was able to in 14.1? It seems

/vendor/firmware/wlan/prima

is not available to write to in 17.1? Is there an easy way around this for 17.1? Why can't the devs use the later WiFi driver for Nexus 7 FHD build? (Then none of us would have to worry about replacing the driver like I've been doing previously for 14.1?)

Siggy
[Nexus 7 (2013) Android Development] daltab:
Vibrate does not seem to work with Lineage 17.1 on the Nexus 7. The option does not even appear in the Sound settings. Is this a known limitation?
[Nexus 7 (2013) Android Development] LV198:
Nexus 7 has a vibrate motor? That's new to me...
[Nexus 7 (2013) Android Development] daltab:
The 2013 does. The first gen did not, from what I've heard.
[Nexus 7 (2013) Android Development] LV198:
I have a Nexus 7 (2013) and it never had a vibrate option, even on Stock ROM.
[Nexus 7 (2013) Android Development] daltab:
Now I'm questioning my sanity. I swear my tablet would vibrate before I updated to lineage. I'll test it today with a different time then report back how crazy I actually am. Haha
[Nexus 7 (2013) Android Development] daltab:
It's confirmed, I'm just making stuff up apparently. I swear I used to have haptic feedback on my Nexus 7.
[Nexus 7 (2013) Android Development] GeekyTanuj:
@ud4 is there any possibility that double tap to wake will be embedded in your kernel in future builds? Is it just me who has noticed that sensors stop working momentarily in the last official ROM from time to time?

I make use of followmsi's kernel to get this feature but somehow, that kernel always causes lags here and there sometimes. Hence, have been sticking to the default kernel for this reason.
[Nexus 7 (2013) Android Development] Lantizia:
I've also been following the install guide

to the letter

...

At the bottom of the Repartition section we're told (after repartitioning) to flash the recovery image then use it to factory reset. So I'm not sure how you were expecting @atiska007 to do the very thing they were already explaining is the thing they were already trying to do and were stuck on?

I can confirm I get the same issue (when trying to load recovery), it shows for about 5 seconds at the bottom of the screen (nothing shown elsewhere on the screen) before rebooting...

So if this is normal... (I can only assume you think that by saying "those are both expected")... is there a work around?
[Nexus 7 (2013) Android Development] npjohnson:
That's... weird!

Try fastboot -w from bootloader, then booting to recovery?
[Nexus 7 (2013) Android Development] Lantizia:
Well after doing what you said... now it shows the same two lines at the bottom (joined by a third)... but at least you get the actual recovery menu showing at the top and it doesn't reboot after 5-ish seconds any more.

Proceeding with the remainder of the installation instructions seems to have worked without a hitch and it's now running LineageOS 17.1.

Can anyone here update the install guide to reflect this required extra step?

Thanks :)
[Nexus 7 (2013) Android Development] Lantizia:
Is a slimport HDMI adaptor supposed to work with this release? It did when it was running LineageOS 14.1.

Plugging in the adaptor is fine... but the moment you plug in a HDMI cable (with a TV on the other end) the entire tablet freezes up into an unrecoverable state (other than forcing it to power off and on).
[Nexus 7 (2013) Android Development] npjohnson:
doing it right now
[Nexus 7 (2013) Android Development] npjohnson:
It's now on the wiki. Thanks for the feedback.

No, and it never will again. MHL/Slimport were dropped in AOSP as of Nougat - there's no further support for it, and no way to bring it back.
[Nexus 7 (2013) Android Development] Gorilla Daddy:
Camera stops working after a while in video conference apps. After maybe 20 minutes? Happens in Teams, Facebook Messenger; for examples.

The video from the other end runs fine, as does the audio. What freezes is the Nexus 7 2013's video camera feed.

It just freezes the previously moving picture. If I disable video & reenable (like by pressing a camera icon in the app if it's available) it will do video for about 3 seconds, then freeze again.

I suppose the way to reproduce is just to leave a video call going and check in on it until it freezes. Just wondering if anybody has a solution already. Or also has this trouble.
[Nexus 7 (2013) Android Development] Gorilla Daddy:
Another bug is Screen Casting. This works on Lineage 17 for the LG V20. When I screen cast the Nexus 7 2013, it will lockup and reboot. Sometimes it gets halfway through connecting to the TV. Never does connect completely or show any video.
[Nexus 7 (2013) Android Development] Madacam:
Hello,

Thanks for this great job.

I followed the installation guide of lineageOS 17.1 on my nexus 7 flo, now flox, and everything went well:

stock version of android; using flo-deb_clamor_repartition; installing twrp-3.5.0_9-0-flox.img; following the commands after "adb shell" and installing lineage 17.1.

However, I have a question about the manual command to update lineage 17.1:

"wget https://raw.githubusercontent.com/LineageOS/android_packages_apps_Updater/lineage-16.0/push-update.sh && chmod +x push-update.sh" .

Why does the wget command refer to "/lineage-16.0/" and not to "/lineage-17.1/" ?

Thanks again for your work.
[Nexus 7 (2013) Android Development] ddonmez:
Any. Official deb solution?
[Nexus 7 (2013) Android Development] NTGDeveloper:
Just wanted to post here that there is a LOS18.1 build available and the update did not go smoothly for me. I was on LOS 17.1 Recovery when I installed. Basically, I installed LOS 18 image, then MindTheGapps, then Magisk 22. I booted my device, and it lasted for a couple of seconds, then crashed and continued to do that. I had to factory reset my device.
[Nexus 7 (2013) Android Development] sasuke chen:
I have some questions.

Please help me.

Because of some bank app issue.

I'm trying to flash an edited boot.img.

I need to set ro.debuggable to 0, but after I unpack the boot.img with android image kitchen on windows 10.

There is no default.prop in the ramdisk folder.

So I couldn't edit the default.prop and repack the boot.img.

Is there any way to set ro.debuggable to 0 without magisk root?
[Nexus 7 (2013) Android Development] BLewis4050:
Wow -- frustrating to read, but thanks for attempting!
[Nexus 7 (2013) Android Development] pedritopl:
Worked as expected with flox TWRP.

First I wiped System, Vendor, Data & Cache and the installed Lineage + MindTheGapps. After i ital setup I flashed Magisk 22.0 and then my apps backup from Migrate-NG 4.0.

All working fine.

Maybe Your problem was that You used the 17.1 Lineage recovery.
[Nexus 7 (2013) Android Development] edison0354:
Any one using flox 18.1 with Edxposed?

I got an endless bootloop/auto-reboot once Edxposed is installed. No logcat can be recorded, seems it starts to reboot before connecting to adb.

Same thing happens to both Edxposed & Lsposed.

Tried clean flash, still the same issue.
[Nexus 7 (2013) Android Development] cedge:
Thanks for the continued support of our old device. I didn't get on with 18.1 so tried and failed to repartition my device again to 1.5Gb so ended up using the 'RESTOCK' and then 'CROSS' scripts to install Lineage Flox. Thanks for the great work.
[Nexus 7 (2013) Android Development] AlecSp:
Like quite a few others, I didn't have an easy ride getting this installed.

I'd previously been on the unofficial 18.1 build and thought that it could be as simple as flashing the official build from TWRP. No dice.

I came back this weekend to give it another go, following the Wiki instructions. Got through the partitioning bit OK, but couldn't flash the Lineage recovery - insufficient space. And I'd lost TWRP through, I think, the repartitioning process. Slight panic as I couldn't do much.

All picked up a little when I discovered that I didn't need to flash a recovery, but could simply fastboot boot into one - that was a revelation. Managed to get my old unofficial 18.1 re-installed, which re-assured me that I wasn't completely screwed.

Had another go, following the steps in the guide, but simply booting into Lineage Recovery for the flashing - and it finally worked! It was probably unfortunate that I hadn't discovered the Flox TWRP before I did all this but, ho hum, it's all good learning along the way.

As for the build - it's awesome. The 17.1 and 18.1 unofficials I'd been using were a little sludgy and, while it's early days so far, I think 18.1 is faster than quite a few recent Flo builds I've used. I still can't believe that my old 2013 Nexus is running on the latest Android 11, when it first came out with Android 4.3! Kudos to the team :)
[Nexus 7 (2013) Android Development] leetripper:
With the latest build I'm having echo for the called in Telegram video calls. It was not in the builds before. It's a pity, because it's so amazing, what this device is capable of with lineage os 18.1...
[Nexus 7 (2013) Android Development] Af0x:
Hello,

I want to give feedback to the upgrade from 17.1 to 18.1. If the device is encrypted but no password is set you can´t boot into the upgraded system as it asks for a password which cannot be empty.

Regards
[Nexus 7 (2013) Android Development] leetripper:
Due to testing purposes I installed 16.0-20210422-UNOFFICIAL. No echo in Telegram video calls. Experienced these echoes on my Moto X4 also. Over here - [OFFICIAL][ROM][PAYTON]LineageOS 18.1 - ThE_MarD did an amazing work on 'echo-references' to solve it.
[Nexus 7 (2013) Android Development] jaucar:
I have installed this Rom correctly.

However the sensors do not work.

I have done a clean installation again and they still do not work.

Is there any solution that can solve it?
[Nexus 7 (2013) Android Development] killeriq:
@ayenzel

​

hello, how did you install it on DEB? thanks
[Nexus 7 (2013) Android Development] ilyvasile:
Installed flox 18.1 on my old flo (with BitGapps&Magisk). Had repartitioned with Clamor zip before install. LOS works perfectly, including OTA updates with encryption, safetynet with magiskhide. I only faced the problem with included TWRP, it can't decrypt data, but anyway OTA/Magisk/Gapps install scripts works normal. Also, lineageos recovery not able to sideload install BitGapps, use TWRP.

Big thanks to device team for N7 2013 long life.

P.S. I had slow charging, touchscreen, and sensors issues before too, but fixed with this guide, cleared both flat cables connectors with vodka, and used thin resin sticks between them and back cover for tightening.

https://xdaforums.com/t/fix-nexus-7-2013-grounding-issue-improve-touchscreen-performance.3011140/

If somebody don't want use HW fixes, maybe ParrotMod fix sensors problem, it able to restart them when problem occurs, i used it on old firmwares, works very great

https://xdaforums.com/t/app-root-parrotmod-fix-the-2013-nexus-7-touchscreen-and-auto-rotate.3375928/
[Nexus 7 (2013) Android Development] userXCVII:
Are you able to downgrade from lineage os 10 to the stock OS? If yes, please share the steps. :(
[Nexus 7 (2013) Android Development] killeriq:
guys please could someone explain the difference ?

"flo-deb_clamor_repartition" vs "flox-deb_clamor_repartition_20201203"

the "newer" one is suggested from LineAge 17.1 - 18.1 , but havent find the difference...

Or if i have already the older one do i need to put the newer one? Thanks
[Nexus 7 (2013) Android Development] jorges4lu2:
Hi, could someone share with me the latest 17.1 build? It seems they are not supporting it anymore on the official web.

Thanks in advance
[Nexus 7 (2013) Android Development] sinkoo1979:
Use the new one
[Nexus 7 (2013) Android Development] Topster77:
I have the same issue with Official Lineage 18.1... blank installation, still something drains my battery... (see here). Any ideas?
[Nexus 7 (2013) Android Development] BLewis4050:
I've upgraded to 18.1, but cannot get past the lock screen - the PIN is valid as it errors on an incorrect PIN entry, but then only clears the screen as if to display the home screen of the launcher, but instead goes back to the Lock screen. Any insight would be appreciated.
[Nexus 7 (2013) Android Development] artigasperez:
Thanks for the hint. I recently installed flox 18.1 20210614

I'm using OpenWrt 21.02 with WPA2/WPA3 Mixed mode, and those config sets 802.11w to "optional". I have to setup another SSID with only WPA2.
[Nexus 7 (2013) Android Development] artigasperez:
I couldn't find a post for official lineageos 18.1 for flox, but the links you posted as

"Official dowload links" are now for 18.1 , and btw the install instructions worked great upgrading from an old LineageOS 15.1.

In the official 18.1 i can confirm that encryption works ok.

The only problem that i can confirm is with using wifi with mixed mode WPA2/WPA3 (the same network in that the old 15.1 worked fine for the last year). For now, the workaround was to add in the router a new network offering only WPA2.

Thanks to the developers for their hard work, that allow us to keep this device updated, 8 years after buying it.
[Nexus 7 (2013) Android Development] Martin_D:
I had the same issue with my Nexus6 when upgrading to lineageos 18.1. This seems to be a standard problem on first startup of android11 when you have a pin etc. configured.

Go back to your last backup, remove the screen lock and have a look at https://xdaforums.com/t/remove-bypass-lockscreen-with-recovery.3530008/

The exact names and amount of files you find in /data/system varies depending from device and previously installed lineage versions. Delete files named *.key and *locksettings* before flashing lineageos18.1 etc.
[Nexus 7 (2013) Android Development] cweiske:
Thank you for keeping the Nexus 7 alive! It is awesome that I could get an Update to Android 11 in 2021, 8 years after official release.
[Nexus 7 (2013) Android Development] GeekyTanuj:
Can anybody share the last zip of Los 17.1 flox?
[Nexus 7 (2013) Android Development] AlecSp:
Any reason why you wouldn't go for an Official LOS 18.1 build for Nexus 7 2013 Flox...?

I've been using it for months with no problems. A bit of a dickabout getting it repartitioned as Flox, but if you've already achieved that, then why stick with an older, unoficial build?
[Nexus 7 (2013) Android Development] olekor:
"From your Terminal/PowerShell, run adb sideload /path/to/flo-deb_clamor_repartition.zip, filling /path/to/ in with the path you downloaded the repartition zip to."

What needs to fill here /path/to/? Does it mean a place where this repartition.zip?
[Nexus 7 (2013) Android Development] GeekyTanuj:
I did achieve the Flox partition and am running an old 17.1 build but the only reason that stops me to jump to 18.1 is that Android 11 isn't too friendly about sideloading OBB based apps. For example, I can't get to sideload Respawnables (a game) if I download it from sources other than the play store.

If you happen to know a workaround for the same, please let me know!

Also, if you can drop the link to the last 17.1, I would appreciate that too!

Thanks.
[Nexus 7 (2013) Android Development] ipdev:
Yes. ;)

It would be the full path to the zip file.

This is only needed if you are not in the same directory the zip file is in.

If you are using Windows, it would be something like this adb sideload C:\Users\YourUserName\Desktop\NameOfFolder\flo-deb_clamor_repartition.zip

If you added the adb command to your Windows $PATH.

or copy the adb.exe file into the same directory as the flo-deb_clamor_repartition.zip file.

You can just call adb from the directory the zip file is in.

adb sideload flo-deb_clamor_repartition.zip

Cheers. :cowboy:

PS.

There is no problem calling a full path, I do it quite a bit. ;)

Note: I have seen issues in different threads about using \User\Desktop\

Normally it was recommended to make a directory on C:\ and move the files there.
[Nexus 7 (2013) Android Development] Dtox88:
It's been fun dusting off the OK' flo(x) for 18.1. Thanks! What kernels are folks using?
[Nexus 7 (2013) Android Development] sofakng:
I'm trying to repartition my Nexus 7 (2013) using the repartition script but I'm getting some errors:

flox:/ # modify
2048+0 records in
2048+0 records out
1048576 bytes (1.0 M) copied, 0.034057 s, 29 M/s
dd: /tmp/backup/recovery.img: write error: No space left on device
umount: /mnt/system: Invalid argument
umount: /data: Invalid argument
umount: /sdcard: Invalid argument
umount: /cache: Invalid argument
/system/bin/modify[42]: can't write temporary file /tmp/shelg6qc.tmp: No space left on device
mke2fs 1.45.4 (23-Sep-2019)
/dev/block/mmcblk0p22 contains a ext4 file system
created on Mon Jan 10 14:57:17 2022
Proceed anyway? (y,N)

Should I ignore the errors and just proceed? (I don't need any data from the device)

If I do proceed and attempt to flash the recovery image I get a different error:

E:\Tools\adb\platform-tools>fastboot flash recovery c:lineage-18.1-20220110-recovery-flox.img
target didn't report max-download-size
sending 'recovery' (10878 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 0.353s
[Nexus 7 (2013) Android Development] underflash:
Hello, please share latest 17.1 build? On the official web only 18.1 is available.