yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] karandevilocs:
thanks for this build, i jumped straight from AOSP EXTENDED on android 9 to this ,

currently on latest version + pico gapp test versions and your custom kernel, but i have two questions

1. is there an app for the custom kernel to OC or change the governors?

2. is there a way to use my N7 as WIFI SHARING device ? im currently using my note 8 as wifi sharing device as it has that option built in in the settings and it works as extender but i would like to use N7 as a wifi share device rather than the Note8 but i can't find any solutions to that since all the articles and guides are dated back to android 4 or something so any help in that regard would be appreciated
[Nexus 7 (2013) Android Development] pilotv:
After a while with all apps installed it becomes again very slow with lags. Try in develloper options to not allow more than one activitie at same type, and it runs better and a litle fast.
[Nexus 7 (2013) Android Development] Jrieann:
Hi thank you for the ROM

I have installed microG, then Self-Check and successfully logged in, but Playstore did not log on, and the settings page will crash.

How should I install and use?
[Nexus 7 (2013) Android Development] ipdev:
Hi all. :)

Just a quick note.

---

For those of who did not use Clamor's repartitioning.

I updated my REPIT port and created a thread for it.

[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 7 (2013) [deb][flo] xdaThread - Link

This will give you a 1.4G (1477M) system.

A little more system space for GApps and custom configuration. ;)

---

For those who enable Double tap to wake.

Since DT2W is included in followmsi's kernel(s), you just need to enable it.

You can do this using a kernel manager or a simple boot script.

I combined the boot scripts I use to enable double tap to wake into a Magisk module.

mModule_dt2w GitHub - Link

I use the kernel that is built with the rom(s).

I do not modify any other kernel settings so, using a kernel manager just to enable double tap to wake seemed a bit over-the-top. ;)

---

Cheers all. :cowboy:
[Nexus 7 (2013) Android Development] karandevilocs:
Hey guys, is there a way to use this tablet as WIFI SHARE / WIFI REPEATER ?

there is an option in Note 8 wifi hotspot option to share your already connected wifi to other devices and it works like a charm, but i want to use this tablet as wifi share device rather than that , but i can't find a solution to that.

is there an App or magisk module to add this to system for a seamless connection or is it hardware limited ?

any help would be appreciated, im desperate to find a solution
[Nexus 7 (2013) Android Development] Codex0:
Hmmm am I doing something wrong? I did the following:

1. Wipe everything

2. sysrepart

3. Wipe everything

4. Install LineageOS

5. Reboot to system

But just sits on the lineage booting logo, has been on it for an hour now.

I also tried repeating this with @ipdev 's version of the repart, same thing.

I'm using the LTE version, so trying to flash the deb package

I also tried to do this with and without the pico version of the gapps. Same thing sadly. Not sure what else I can do.
[Nexus 7 (2013) Android Development] ipdev:
TWRP for deb unfortunately was not updated to 3.5.0_9-0 :(

TWRP 3.4.0-0 defaults to install the TWRP app.

Make sure NOT to install the TWRP app.

You can toggle the TWRP app install in TWRP settings so it will not ask each time you reboot from TWRP.

Note:

Installing the TWRP app on quite a few devices caused issues.

Infinite boot.

Bootloop.

Bootloop and then recovery.

Rescue Party

Try a clean install again.

Since you (re)partitioned you can skip that step.

Boot into TWRP and do the format and wipe steps then reboot into recovery (TWRP).

Install the rom and reboot to system.

Do not install the TWRP app..

Hopefully it is just the TWRP app getting installed.

If not, logs are needed to see what is going on..

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Codex0:
Awesome, that was exactly it and got it all running now. Thank you!

I get a lot of connection issues on wifi but it's not the worst, I use this as a test device these days mainly.
[Nexus 7 (2013) Android Development] String0011:
The rom works great! The developers are awesome!

Problems I encountered with my 16GB flo:

1. /system could not be mounted after flashing the partition resize zip. I tried to format it to ext3 and back to ext4. Then the partition seemed to be back with correct space.

2. After installing LineageOS, only ~280MB free space is remaining in system partition. I had to download the pico gapps. Others could not be installed due to insufficient storage space.
[Nexus 7 (2013) Android Development] names:
@ipdev

Thank you again for your help with this, unfortunately no luck yet in getting the system out of a boot loop and back to stock.

@k23m

Would you happen to have any thoughts or suggestions?
[Nexus 7 (2013) Android Development] ipdev:
I updated my REPIT port and posted a link a few posts back.

Post 3339 - Link

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] k23m:
Yes, please go to RESTOCK and get

k23m-persist-fix2.zip

Install it manually in TWRP. I will add it to the next version of Restock's scripts.

(y)
[Nexus 7 (2013) Android Development] pixel2404:
Hi@all,

I have installed 18.1 on my Nexus 7 2013 LTE. First rooted, repartitioned and installed TWRP.

Can anyone tell me which MicroG package I need to install to have Exchange Services on the device?

with best
[Nexus 7 (2013) Android Development] names:
Incredible! Worked on the first try and happy to report I am back to stock with no bootloop. Thank you for this, I don't even know how many hours I spent in this thing.
[Nexus 7 (2013) Android Development] jorgepedrero:
I couldn't make it work. I spent the whole day trying to make this repartition do its thing and every attempt fail. I followed your steps, I try different combinations, I even went back to stock android 4.3 in case the problem was that I have a previous partition but anything work. I had to use the partition script on page 1 and go for pico gapps as it doesn't accept anything else.

Any thoughts on why it didn't work?
[Nexus 7 (2013) Android Development] k23m:
It seems that currently all partitioning methods, UA, REPIT and my sysrepart, offer max 1.5GB system, which is sufficient only for pico gapps, as you have observed.

Actually you should install pico anyway and later add other Google apps from the Play Store as non-system in the userdata partition space - plenty of room there. There are exceptions. If you can not use Play Store to add some special Google apps, here is a solution if your chosen GApps package produces Error 70:

have a look at the Package-Comparison

for example if you want GooglePay from the "Stock" variant but it will not install...

get the "aroma" GApps and select only the above component for installation

everything else should be installed later from the Play Store

Works for me.
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 18.1 - March 2021

lineage-18.1-20210306-UNOFFICIAL-flo.zip

lineage-18.1-20210306-UNOFFICIAL-deb.zip

Changes:

- Google Security updates -> March 2021

- Patched frameworks/base to support microG

- Latest LineageOS changes for Android 11

Pls check first page for installation instruction and known issues !

Tested flo build with opengapps test packages (pico) and Magisk 22.0.

Installed with latest TWRP 3.5.0.

Enjoy Android 11 :p
[Nexus 7 (2013) Android Development] matt.weatherford:
Hey this is great - thanks for keeping the Nexus7 current!

Does the system update feature work ? Will this rom get notifications of new builds and offer to download/install?

I understand if this is too early in the dev cycle to have this, but would like to know either way

thanks,

Matt
[Nexus 7 (2013) Android Development] Mr.Conkel:
I'm sure once its official those feature will be implemented however for something like that as in OTA updates it would need to be official .
[Nexus 7 (2013) Android Development] Mr.Conkel:
Does this mean that Android 11 now supports signature spoofing without the need for Xposed and other helpful tools?
[Nexus 7 (2013) Android Development] Mr.Conkel:
Download quota has been reached for latest build I cannot download it from drive :(

Edit: I made a copy of the file and downloaded from my drive, sorry for any confusion.
[Nexus 7 (2013) Android Development] osm0sis:
FYI: TWRP 3.5.1_9 for flo failed to build due to size constraints (and deb tree is missing), so will likely need an official maintainer to step up and update the device tree.

Builds have been disabled until that happens:

flo-prod [Jenkins]

jenkins.twrp.me

Anybody wanting to become maintainer can join the TWRP Testing Slack and express their interest: https://join.slack.com/t/twrptesting/shared_invite/zt-6n0prc0w-Jy~lE7zMH5CYnsFrSleIPA

🤞
[Nexus 7 (2013) Android Development] followmsi:
Just saw this message ..

And the new successful flo-prod build :)

flo-prod [Jenkins]

jenkins.twrp.me

The change to exclude bash did work.

https://gerrit.twrp.me/c/android_device_asus_flo/+/3638

The DEB device tree is still on 5.0 but builds on omni 6 too ..

GitHub - TeamWin/android_device_asus_deb

Contribute to TeamWin/android_device_asus_deb development by creating an account on GitHub.

github.com

Just started my test VM and made FLO and DEB TWRP builds on latest sources.

twrp-3.5.1_9-0-flo_followmsi.img

twrp-3.5.1_9-0-deb_followmsi.img

Sorry .. but my Android time is very limited and I will not be able to help in testing.

Thanks for driving this issue !
[Nexus 7 (2013) Android Development] dahawthorne:
@followmsi

I've just flashed your new Flo version and tried a backup. On my first and second attempts I got an "error 255" failure, and the recovery log didn't seem (to me) to be helpful; posts elsewhere suggest Error 255 may be something related to multiple profiles, which I don't have.

However, on my third attempt, with all partitions mounted, and system set as read-only, the backup has gone through ok. I haven't tried a restore, but if I ever need to I'll certainly let you have the results one way or the other.

Thanks, as always, for working on my stone-age Nexus 7... :)
[Nexus 7 (2013) Android Development] DCvan:
Thank you @followmsi @ipdev The LineageOS Team! Is an incredible work keeping Flo alive. Just switched from 17.1 nightlies to 18.1 0306, no hiccup and run smoothly. Magisk 22 is not working for me but 21.4 is working fine. 👍🙏
[Nexus 7 (2013) Android Development] argamidon:
Hi all, I've just downloaded lineage 18.1 and tried to install on my nexus 7 wifi (flo).

I use fresh TWRP 3.5.1 and it works well because I successfullt installed lineage 14.1 before this.

What do I do wrong ? how to install 18.1 ? Also what version of GApps should I use ? I found version for only android 10

There is log that says there is no "file_context" in root:

Installing zip file '/sdcard/TWRP/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
Unmounting System...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
No path given to file labeling backend
selinux_android_file_context: Error getting file context handle (No such file or directory)
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keysExtracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 5 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally...
Patching system image unconditionally...performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/5a79362318d00cf4c316e86435b3ed38dd35082d
568262656 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 25919 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,254656,261632,262657,281600]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 1
I:Install took 0 second(s).
Error installing zip file '/sdcard/TWRP/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
[Nexus 7 (2013) Android Development] ipdev:
E1001: Failed to update system image.error: 1001

Is normally out of space in the system partition when installing the rom (system image).

You need to (re)partition the device for Lineage 17.x and 18.x. roms.

You need a 1.1G system partition to install Lineage 17 and 18.

1.5G system partition if you use the official lineage flox builds.

If you want to use OpenGapps.

- At least 1.28G system for rom and pico gapps.

- At least 1.37G for nano gapps.

There are a few partition options for flo/deb.

followmsi's script for a 1.2G (1280M) system. (Modified version of k23m's original script.)

Post 1,971 - Link

This will give you a 1.4G (1477M) system.

[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 7 (2013) [deb][flo]

xda thread - Link

Note:

k23m's flox script and Clamor's script will do a little more.

You will have a 1.5G system partition.

Userdata is reduced a little and a vendor partition is created.​

[IIIII] CROSS - Custom ROM Scripted Setup

xda thread - Link

Clamor's

[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]

xda thread - Link

If you already used one of the partition methods.

You may just need to format data and wipe all the partitions.

TWRP-> Wipe-> Format Data (Type yes and press enter)

TWRP-> Reboot-> Recovery (Ignore warning about no system installed.)

TWRP-> Wipe-> Advanced Wipe-> (Select all partitions)-> Swipe to Wipe

TWRP-> Reboot-> Recovery (Ignore warning about no system installed.)

If something went wrong with any of the partition methods, you can recover with k23m's RESTOCK or CROSS script.

[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix

xda thread - Link

[IIIII] CROSS - Custom ROM Scripted Setup

xda thread - Link

Remember to backup what you want to save and store it off device before you begin.

Copy it to your computer, cloud storage, USB, ...

As for GApps.

Post 3,267 - Link

There has been no change since 20210130 for Android 11.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] kdi600:
Do any body met the screen rotating problem. It seems like not working.
[Nexus 7 (2013) Android Development] kdi600:
Can you share the way to solve the screen rotation. Thank you so much.
[Nexus 7 (2013) Android Development] kdi600:
Nexus 7 2013 LTE , successful install , but can not rotate screen
[Nexus 7 (2013) Android Development] argamidon:
Yeah now it works, thank you ! :)
[Nexus 7 (2013) Android Development] Sobek5150:
I'm on FLO and have issues with rotation as well. System completely froze when I used the Home gesture from Amazon Music App in landscape. It acted like it wanted to flip back to portrait, then corrected it self, then completely froze. Had to hard boot to get back into system.

EDIT: Upon reboot, before i could disable auto-rotation, it froze again when trying to rotate. I recommend in the mean-time to disable auto-rotate to avoid issues.
[Nexus 7 (2013) Android Development] dendk:
Setup latest build flo, new gapps pico breaks the tablet goes into a boot loop the screen flickers on and off. unusable..re flashed went back to old version. Still testing...
[Nexus 7 (2013) Android Development] gigi20:
Screen rotation issue is most likely hardware related, you can find videos on YouTube on how to fix that.

While downloading the latest official LineageOS 17.1 for flox I saw that there is now also a first nightly build of 18.1. Is that an accident, or will there really be official 18.1 builds for flox now?
[Nexus 7 (2013) Android Development] osm0sis:
Oh it's real. It's in the Lineage 18.1 announcement blog post. Butttt that's flox, not flo. So this unofficial remains useful for those that don't want to heavily repartition to add vendor.
[Nexus 7 (2013) Android Development] alucard_xs:
Hello everyone,

thanks for this thread !

It worked great on my LTE Nexus 7 2013.

Just one question : I've got the "selinux disable", is there a way to enable it ?

Thanks !
[Nexus 7 (2013) Android Development] ipdev:
Welcome to Android 11. :D

SELinux is time consuming to fix and test, normally one of the last changes made.

To be enforcing, you have to make sure (define) all security permissions for the process(s) are set.

This is the selinux history of flo.

followmsi's android_device_asus_flo - GitHub - Link

The LTE (deb) builds use flo to build with.

Basically you build flo and add the deb parts.

If you want to give it a try, you can set SELinux to enforcing and see if it works.

getenforce will show you the status.

setenforce 1 will set enforcing mode.

0 = Permissive

1 = Enforcing​

In a terminal app or adb shell.

Root permission is required to change enforcement.

deb:/ $ getenforce
Permissive
deb:/ $

deb:/ # setenforce 1
deb:/ # getenforce
Enforcing
deb:/ #

You will be enforcing until you change it back or reboot.

Cheers. :cowboy:

PS.

Old but still a great explanation of SELinux.

Chainfire's How-To SU - WebSite - SELinux - Link
[Nexus 7 (2013) Android Development] alucard_xs:
Thanks for the explanation.

Btw, is it mandatory to enable it ?
[Nexus 7 (2013) Android Development] ipdev:
Enforcing is not mandatory.

It is a big part of security though.

With that being said, I do not remember the last time my flo or deb was enforcing.

CM14 maybe?

For the last few years, followmsi has been maintaining flo/deb on his own.

Along with some other devices.

Now that flo(x) is back on the official lineage list (with three maintainers), and lineage 18.1 is official.

The se pollicies are being updated and corrected for flo(x).

Followmsi's builds include the flo(x) se pollicies.

There might be something still missing due to slight differences in the builds.

I have not had time to test SELinux so I am not sure what (if anything) does not work.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] fattox:
Hi everyone, unfortunately I'm stuck at the repartition, what I'm doing wrong? Thanks from your help
[Nexus 7 (2013) Android Development] ipdev:
Not sure what error you are running into.

I never used the sysrepart script.

looking at the script, it should be a safe not to intrusive script.​

The TWRP recovery log would help.

/tmp/recovery.log

Also sysrepart should save a log file in your internal storage.

/sdcard/log.txt

You might just need to format and wipe the partition(s) in TWRP.

Post 3,362 - Link

The log files will help explain. ;)

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Sobek5150:
It's unlikely that the rotation issue is just a hardware problem. At least not for everyone. I've tested sensors. They work fine. Rotation works perfectly fine in A10 as well. To me this points to something in the build.
[Nexus 7 (2013) Android Development] Mr.Conkel:
In my experience it depends on the boot, sometimes it will work others it won't. And my sensors are proven to work fine but I just use rotation in qs (on playstore) to work around any issues so while it is a hassle its not a bad issue for me.
[Nexus 7 (2013) Android Development] Mr.Conkel:
Also something must be wrong with the MicroG implementation as the Services Core is constanly stopping when trying to use any method of signature spoofing thorugh the rom itself or Xposed. It is very constant and everytime an app asks for MicroG it will stop but the operation of the app to verify its checks are fine as far as I can tell..
[Nexus 7 (2013) Android Development] Sobek5150:
Is this the app you're using?

Rotation Quick Setting - Apps on Google Play

Quick settings tile to select portrait or landscape screen orientation.

play.google.com

And you're saying that using the app helps get you into landscape without the freezing?
[Nexus 7 (2013) Android Development] Mr.Conkel:
In my experience yes sir, It doesn't freeze hardly at all, sure there's a little lag but the tablet is old can't expect much.
[Nexus 7 (2013) Android Development] RePli2:
same here. Seems to be the same culprit for all ROMs (I tested Lineage, Havoc, PE, ...). Stock firmware works on same phone, even in WPA2+WPA3 mode (LG V30)
[Nexus 7 (2013) Android Development] followmsi:
Did you test v4 ?

EDIT:

On LOS it's still freezing .. Maybe it's the different kernel ?
[Nexus 7 (2013) Android Development] rusik2293:
better, but not fixed

Mb not working because of this

04-15 12:04:37.769 E/WVMExtractor(724): Failed to open libwvm.so: dlopen failed: library "libwvm.so" not found

Or this

04-15 12:35:02.381 W/unknown (2732): type=1400 audit(0.0:39): avc: denied { read write } for comm=504F5349582074696D65722035 name="qseecom" dev="tmpfs" ino=4044 scontext=u:r:mediaserver:s0 tcontext=u:object_r:tee_device:s0 tclass=chr_file permissive=0
[Nexus 7 (2013) Android Development] followmsi:
No .. it's not the problem .. or maybe a part of it.

/system/vendor/lib/libwvm.so exists.

Coming from here ..

https://github.com/followmsi/androi...gat/asus/flo/proprietary/vendor/lib/libwvm.so

If you find the correct lib(s) not breaking widevine and still making miracast working I am happy to make a change on GitHub ;)
[Nexus 7 (2013) Android Development] rusik2293:
Miracast log in permissive selinux modeView attachment 2017-04-15-13-31-26.txt