yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] jhford:
Deb. Am I the only one experiencing "screen tearing"? Great descriptive phrase. Wish I had thought of it yesterday.
[Nexus 7 (2013) Android Development] followmsi:
I don't use Nova launcher but for example Spotify app does also hook on accelerator sensors .. and does drain battery.

If I kill Spotify app to release accelerator sensors the flo device starts to sleep very well.

Back in Oreo the "earlysuspend" code got removed from kernel .. lineage, EX and "my" kernel too.

Unlegacy is still using it .. and I remember discussions about this topic at this time .. also about sensors and sleep.

For this reason we did test the Unlegacy kernels now.

Needs to be tested if Unlegacy does not have the same sensors issues.

For Deb we have the USB modem and it's wakelock issue too.
[Nexus 7 (2013) Android Development] tiaka1:
Won't turn off

Hi

I have just installed lineage 16 on my nexus 7 2013 wifi.

Followed all the instructions.

Every thing works fine except it won't turn off.

It keeps rebooting.

The only way to turn it off is to boot into boot mode and turn it off there.

I going to put up with it but I thought I would let you know.

Cheers :)
[Nexus 7 (2013) Android Development] sidamos77:
I wrote about that a few posts above. Disable HW Overlays in developer settings. This removes 99% of the tearing. Although this setting does not survive reboots.

---------- Post added at 11:05 PM ---------- Previous post was at 10:54 PM ----------

With WiFi off during standby (enable Airplane mode with Tasker on screen off), Unlegacy only uses 0.3%/hour, same as LOS 14.1 with WiFi off during standby. So, it is possible with Pie.

I checked sensors on Unlegacy in BBS. Google Play Services and Nova use Accelerometer all the time also. I have made screenshots and will compare with LOS 0501 tomorrow.
[Nexus 7 (2013) Android Development] MaxPowerOne:
I have a bug, clean install the bottom bar glitches out graphically on the central dot (the one to go back to launcher), could you fix that? Clean install, is yours giving the same glitch?
[Nexus 7 (2013) Android Development] JT1510365:
Yes this is an issue with all pie ROMs for this device for some reason I don't know what causes this or how to fix it
[Nexus 7 (2013) Android Development] MaxPowerOne:
Ok thanks, the newest update is broken, all animations are desyncronized, I tried 2 installations.
[Nexus 7 (2013) Android Development] ranaxda200:
Anyone facing recognisable frame drops while screen transitions?
[Nexus 7 (2013) Android Development] followmsi:
Yesterday I had some time to look .. Unlegacy is using different sensors wrapper.

I have cherry picked this change for testing .. looks good.

https://github.com/followmsi/android_device_asus_flo/commit/02f62fb2cc0d13afe0ba4e74ae90282d0b57c238

Sensors seems to be more "sleepy" now.

For testing you can replace the lib your self .. maybe not on 05/01 test build.

sensors.msm8960.so.zip

@ripee you may make a new build .. using "normal" kernel again.

Added wakelock group for deb as well ..

https://github.com/followmsi/android_device_asus_deb/commit/57b81be3a8c497ae7a04a324b5cd47e6a9d6e2ae

Cheers

---------- Post added at 10:47 ---------- Previous post was at 10:41 ----------

Pls think about your communication style.

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

2nd build 0505 for both variants

* If you flashed 0505 already, flash the one that is currently up, as it is the updated one.

* Wakelock and sensors fixes added, as per followmsi's post #233.

* NFC is tentatively fixed, as per followmsi's commits from May 5, 2019.

* Synced with LineageOS sources.
[Nexus 7 (2013) Android Development] sidamos77:
[MENTION=6005084]ripee[/MENTION]

[MENTION=5480152]followmsi[/MENTION]

Here is the result of my 12 hours standby comparison between Unlegacy and LOS 0501 (with kernel 0501) on my deb.

Both standby in airplane mode. Both do deep sleep. 99% (Unlegacy) and 100% (LOS 0501).

Drain:

Unlegacy: 0.3%/hour (0.6%/hour with WiFi on)

LOS 0501: 1.3%/hour (2%/hour with WiFi on)

Screenshots from BBS attached. You can see that the Amazon Kindle app does quite a lot of partial wakelocks. I do not have this installed on Unlegacy. This may be responsible for a tiny bit of difference. I will uninstall this after the next test.

Next I am testing with LOS 0505 the new sensors code.

Thanks for your work and help!
[Nexus 7 (2013) Android Development] shugal:
Thanks & couple of questions

First of all: many thanks for keeping my beloved Nexus 7 alive! :good:

Secondly, a couple of questions (sorry if I've managed to miss earlier answers):

1. After doing the repartition, flashing ROM and Gapps and everything works fine is it ok to update TWRP?

2. Just updating the ROM, all I have to do is a dirty flash, also having to flash Gapps again?

Thanks in advance!
[Nexus 7 (2013) Android Development] nmichalo:
installed latest 0505 build on my FLO and I think it is very good. The shoutdown function works properly and my imprssion is that it is a little faster than the 0427 that I use to have. Great job ripee & followmsi

---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------

I have done both things with dirty flash without a problem. But I update twrp version from recovery within twrp.
[Nexus 7 (2013) Android Development] sidamos77:
LOS 0505 now only drains 0.4%/hour with WiFi off (and NFC off).

This is pretty good, only slightly more than Unlegacy. I will check over the next days how it continues.

Thanks a lot to [MENTION=6005084]ripee[/MENTION] and [MENTION=5480152]followmsi[/MENTION]!
[Nexus 7 (2013) Android Development] Neur0Nerd:
I flashed the su remover and I get vendor mounting errors, anybody has the same issue when flashing zips ?
[Nexus 7 (2013) Android Development] ripee:
My last few builds have not included lineage su root, so perhaps it has something to do with that, but I have never heard of the su addon remover causing those kinds of errors.

Wipe System, Cache, and Dalvik. Then flash the rom zip, gapps, and Magisk if you wish.
[Nexus 7 (2013) Android Development] ttamo:
Thanks ripee, but there is still something wrong with NFC.

With your 0505 build, I can activate NFC on my DEB, but then the process named com.android.nfc uses around 100% of CPU, which causes high temperature and short lifetime of battery.

After killing the process, the device comes back to its normal temperature.

Everything else is fine with me. Screen rotation, wifi, GPS and compass are working. Really good ROM, actually!
[Nexus 7 (2013) Android Development] AlesUlrych:
Hello, I have a problem with the latest builds (0501 and 0505). I use the tablet as a navigation and with these builds gps is delayed by about 5-10s. So it shows me the place I've already passed. This is not how navigation can be used. I tried the Wickenberg buil (0504) and it works fine there.
[Nexus 7 (2013) Android Development] ripee:
Changelog

Build 0507 for both variants pulled due to TWRP error 70.
[Nexus 7 (2013) Android Development] AlesUlrych:
I in TWRP 3.3.0-0 mode clean Dalvik / ART Cache, system and cache.

Should I do something else?

This new build throws me an error 70 when installing opengaaps nano, all previous builds went through without error. Download Pico version with try again.

Edit: With build 0507 Error 70 when installing opengaaps pico ! - yet return to Wickenberg
[Nexus 7 (2013) Android Development] jvdxda:
FYI I also get error 70 with build 0507 + opengapps pico

build 0505 + opengapps pico installed fine just now. rebooting...

---------- Post added at 12:46 PM ---------- Previous post was at 12:09 PM ----------

I am very impressed by this android 9 port so far! Donated!

Thanks for breathing new life into my Nexus 7 yet again. Feels pretty smooth, zero issues so far.
[Nexus 7 (2013) Android Development] Quantuss:
SELinux Disabled

Hi [MENTION=6005084]ripee[/MENTION] - I'm not seeing SELinux Enabled. Is that correct and if so is that coming soon?

Thanks and great work on this! Latest version is working well!
[Nexus 7 (2013) Android Development] sidamos77:
Got again 0% deep sleep, this time with 0505 2nd build.

At least, this time I see the cause in BBS: sns_async_ev_wakelock
[Nexus 7 (2013) Android Development] Nexus7_2013_Flo:
Thank you

Came here to say thank you to the developers. This is my new favorite thread. My Nexus 7 (Flo) has been with me for many years now. As news reader, notebook at meetings, navigation unit. First running stock Android, I remember it got Lollipop and Marshmallow. Then I was saddened about it getting abandoned by Google. But then I heard about Lineage. So started anxiously to learn about twrp and flashing of custom ROMs. For quite a long time I have been running Lineage 14.1. Loved lineage, because of the privacy manager, and how I could control which gapps I wanted. Then shortly also Lineage abandoned my beloved device, but luckily I found this thread. After trying some different versions of this ROM I am now at 0505, and it seems to run great. Yes, it got harder for me to get a GPS lock. With Lineage 14.1 I could get a lock in my office, or in my home. Tried with GPS reset app yesterday. No satellites indoor, as there used to be. So it appears the sensitivity has gone down? If that is possible, I am not an expert in this. But I am not going to cry about that. Now I just need to start the GPS outdoor. My older car has a regular USB port, earlier it could marginally keep up with power consumption, while using the Nexus 7 as Navigation unit. Now I have to use a car charger, because power consumption from GPS is much higher than earlier. But also that I can live with. In general also when using the device as notepad, checking emails etc. it appears that power consumption is higher than at Lineage 14.1. But OK, the device is ancient, and this is the latest Android release, so perhaps it was never thought to run at so old devices? No big deal. I am just so happy that I can play with the newest Android release, and my trusted Nexus 7 is still alive and kicking. I don´t install just any ROM, I like to have some feeling that there are some developers behind that will take it further. This I am seeing here.I will be checking in every day, curios to see how the developers can bring this forward. Again thank you.

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

SELinux is not enabled.

Out of respect to the developer I would not ask about when it becomes available. It has been stated that SELinux is not yet stable, and the developer will release it when he feels it is stable.

So just be patient, and enjoy what you have already.
[Nexus 7 (2013) Android Development] dansblackcat:
Always used the same Pico gapps but now I also get the error 70 with 0507, insufficient space.
[Nexus 7 (2013) Android Development] sidamos77:
[MENTION=5480152]followmsi[/MENTION]
[MENTION=6005084]ripee[/MENTION]

Reboot fixed it. Anyone knows this wakelock? I could not find anything useful about it.
[Nexus 7 (2013) Android Development] nunclud:
Hello friends, i know this could still be in beta phase, but how stable is it as daily driver for car MOD.
[Nexus 7 (2013) Android Development] AlesUlrych:
At the moment I use a stable and fully usable version from Winkenberg (build 0506) for navigation in the car.

Ripee's build is applicable for car navigation to version 0427, while the latest 0505 is also stable, but the position in the navigation is a long delay.
[Nexus 7 (2013) Android Development] mattrophy:
For the fix for Pixel Launcher crashing, for anyone else who wasnt sure how to sideload, you have to turn on developer options, then turn on adb debug mode.

Then you can, via USB cable from your PC, when the N7 lineageOS system is booted up, run on the PC:

$ adb install -d com.google.android.apps.nexuslauncher_P-4623511-502_minAPI21\(nodpi\)_apkmirror.com.apk

This seems to fix the pixel launcher crashing issue.

Note: APKmirror said there was a newer version of the APK, but the newer one did not work.

Get this Version:

https://www.apkmirror.com/apk/googl...cher-p-4623511-android-apk-download/download/

This might also help you while crashing is going on:

https://www.reddit.com/r/LineageOS/comments/9e1j45/where_is_trebuchet_launcher/

thank you for a great N7 Android 9 / LineageOS 16 ROM !
[Nexus 7 (2013) Android Development] ripee:
Changelog

2nd build 0511 for both variants

* May Android security patch level.

* Synced with LineageOS sources.
[Nexus 7 (2013) Android Development] Donlagos:
This delay to get a GPS fix is something I had also in Lineageos 14.1, the same like in this Pie rom it takes some time but it get a fix and than it works ok, I think it is a Lineageos Nexus 7 problem.

I tried in 0427 with Magisk the Global optimized GPS replacer modul to fix this, but it didn't make any improvement.
[Nexus 7 (2013) Android Development] JambaFee:
Thank you for this version, it's the first one since build 0421 that's working on my deb device.
[Nexus 7 (2013) Android Development] christnt:
I tried the new build, 0511, yesterday.

Upgrade from 0427 to 0511 by using the install option in TWRP 3.3.

Clean cache and dalvik.

After the boot screen, you can see the login screen (or greeter) for less that one second before the screen turns blank, backlit, though.

Forced reboot by holding pressed the power button did not solved the issue. Every reboot acts this way: backlit blank screen right after the boot screen ends. Only one second of the greeter is visible, so no further action is possible if not forcing reboot by holding the power button for 3 seconds.

Cleaning again the cache and dalvik or reinstalling this build, 0511, have no effect.

Last version up and running is 0427. Opengapps pico installed and OK. No su or magick installed. No options in developer mode changed. It is actually disabled.

Is there something I missed? Do I need to change something after activating the developer mode and before upgrading? Do I need to clear something else than cache and dalvik from twrp? Any command to run from twrp?

Thanks in advance.
[Nexus 7 (2013) Android Development] JambaFee:
Too soon happy: Unfortunately, after a few hours of perfect operation the "gray screen" occurs again after rebooting.
[Nexus 7 (2013) Android Development] dendk:
Another successful install on a semi crippled Nexus 7 2013, Build 511 with a partially working USB port, use of ADB wireless, partitioning tool for more space, flashed full Gapps 9.0, TWRP 3.3.0, Magisk 19.0, restored apps....now to complete installs and test.
[Nexus 7 (2013) Android Development] lorkyn:
Hello everyone,

yesterday I did a fresh install on my deb with 0511. Everything went well, no problems across multiple reboots.

Unfortunately, after charging up, I encountered the gray screen after boot problem later that day.

Some people here mentioned 0421 being the latest version without that problem. However, I am unable to find that particular version for download. Can someone please link it? Thanks.

[MENTION=507649]devs[/MENTION]: are there any logs that we may be able to provide to tackle this problem on the deb?
[Nexus 7 (2013) Android Development] pitrus-:
I'm running 0512 from my compile bot successfully on my two flo's, no gray screen so far.

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] ripee:
If you're using the repos in your github account in your builds, then comparing your builds and mines are like apples and oranges. Your official forks are a bit outdated by now, if I may say so.
[Nexus 7 (2013) Android Development] AlesUlrych:
I can confirm the problem with 0511 from Ripee, but both the 0512 and the new 0513 (with the security patch 5.Mai) from you Pitrus work without error, including navigation (no delay).

What's new in Ripee's build on Flo doesn't work I don't know before solve it, I'm satisfied with your compilation.

In addition to navigation, I use the tablet to watch TV, Youtube and Voyo, the videos from NAS Synology and everything works for me for the time being. Newly, I found out that NFC is already visible, but I didn't show it.

Big thanks. Pitrus.
[Nexus 7 (2013) Android Development] pitrus-:
Sorry no, I'm not using those anymore. This is my build manifest, using followmsi repos.

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] ripee:
Ok then, just to be sure I'm not overlooking anything, I will run a build for flo with that roomservice, and a corresponding one for deb.
[Nexus 7 (2013) Android Development] lorkyn:
Thank you, I can confirm 0513 for the deb now no longer has the gray screen issue (no gapps, magisk for root by the way).
[Nexus 7 (2013) Android Development] AlesUlrych:
Hi Pitrus,

for the first time, an automatic update on my Nexus 7 from version 1205 to 1305 took place.

So far it seems that everything is going well. Great, I don't have to watch new versions anymore. :)

However, if it is not a Ripee build because it has a 1305 version. :)
[Nexus 7 (2013) Android Development] JambaFee:
I installed build 0513 on deb. It is running fine at the moment and already has survived a few reboots. Let's see...
[Nexus 7 (2013) Android Development] dendk:
A couple of things with 511 flo, saw the grey screen had to reboot it has not come up since... As others have described the pixel launcher is not working and I can not add icon group names as the keyboard function flashes but does not come up (fixed with icon change). There are also a few app issues but I am happy the builds are moving forward with good results, thanks to the devs.
[Nexus 7 (2013) Android Development] marsaltito:
Is USB OTG working with this rom?
[Nexus 7 (2013) Android Development] nmichalo:
Yes it is, I have been working all versions since 22/04/2019 and all of them hadn't had any issues with OTG USB sticks
[Nexus 7 (2013) Android Development] marsaltito:
I tried with couple different cables and usb sticks. None of them worked !!

:(
[Nexus 7 (2013) Android Development] nmichalo:
At my previous nexus 7 I had the same issue and it was due to bad handling, the usb port was damaged as my wife used to pulle the charging cable with a lot of strength. Then my elder son broke the tablet and I bought a second nexus 7!. Everything is working with the second tablet thought. I have tested it with a KINGSTON DTDUO3/16GB DATATRAVELER MICRODUO 16GB USB3.0 FLASH DRIVE it works perfectly, where as my previous tablet stopped recognizing it about a year before its destruction.
[Nexus 7 (2013) Android Development] chamo87:
no problem with OTG. I use a Transcend 128GB USB 3.1 (for video playback) long ago with a random OTG-cable from Ali.

Tip: Dont use NTFS
[Nexus 7 (2013) Android Development] ripee:
Changelog

Build 0519 for both variants

* Switched back to los-16.0 device tree branches, and the corresponding kernel followmsi-pie branch, to avoid the grey screen bug experienced by some users.

* Synced with LineageOS sources.
[Nexus 7 (2013) Android Development] .:B:.:
Just bumped my Nexus 2013 to LineageOS 16 as well. Thanks a lot for your work [MENTION=6005084]ripee[/MENTION].

For reference, I was on a personal LineageOS 15.1 build and had used k23m's sysrepart script to resize my partitions already. Prior to switching to this 16.0 build, I had already upgraded my TWRP to vanilla 3.3.0. I decided to try with upstream TWRP before switching to the UA build. Flashed the repartitioning zip linked in the OP here as per the instructions, and had no usable partitions upon rebooting into TWRP (reading the first pages suggests this is because I had already a non-standard /system partition due to the previous repartitioning zip I used for 15.1).

I was able to get things going by manually formatting /system and /vendor to ext4 and /data to F2FS. Then I sideloaded the LineageOS zip, OpenGapps and addonsu. Hope this helps people in a similar predicament - do note though I'm not responsible for you breaking your device :silly:.
[Nexus 7 (2013) Android Development] JambaFee:
Build 0519 works great on both deb and flo!
[Nexus 7 (2013) Android Development] AlesUlrych:
Hi,

with this build, the car navigation works without delay. :)
[Nexus 7 (2013) Android Development] sobokuone:
Vender image for nexus7

Is there a vendor image for Nexus 7 on The unofficial lineageos 16? Also SElinux is disabled. Is it supost to be and if not how would I fix that?

Thanks,

Joseph
[Nexus 7 (2013) Android Development] sushiboba:
Thanks! LOS16 installed perfectly on Nexus 7 2013... loving it... if only it would be more stable for Nexus 10. I still think this is a great tablet even though it's 6 years old... now the 1st gen is horrible no matter what/super outdated.
[Nexus 7 (2013) Android Development] sushiboba:
I noticed sometimes the Rotation stops working and it ends up locking into portrait mode instead of landscape. Anyone else encounter this bug?
[Nexus 7 (2013) Android Development] AlesUlrych:
Yes, I have encountered this error. Mostly, restarting, or shutting down and turning on your tablet and rebooting helped.
[Nexus 7 (2013) Android Development] lolcopter:
SETTINGS>DISPLAY>ADVANCED>Rotation Settings

Make sure auto-rotation is enabled. Mine got turned off somehow awhile back

This latest build has been amazing for me, excellent work all around
[Nexus 7 (2013) Android Development] .:B:.:
I've wondered about SELinux too. [MENTION=6005084]ripee[/MENTION] what breaks when SELinux gets enforced?
[Nexus 7 (2013) Android Development] ubcjack:
Hi, very sorry if the question had been answered before but it's not clear to me after reading faq.

Does the Room pass SafetyNet check (with/without Magisk) at the moment?

For Pokemon go purpose.
[Nexus 7 (2013) Android Development] ripee:
SELinux would only be activated by making the kernel enforcing if sepolicy were properly written to allow only the bare minimum of system access by only those processes that need it and keeping it disabled for everything else. Writing a proper sepolicy is an art and a science and is a lot trickier than it seems. This is the very last step in development, right before a rom is to be submitted for official support, as official support requires the kernel to be enforcing.

However, at this moment, followmsi has NO PLANS TO SUBMIT DEB OR FLO FOR OFFICIAL LINEAGE SUPPORT! Does it really matter if we have official support or not? There are plenty of devices whose unofficial builds are much more stable than their official builds, deb and flo among them. If you are concerned about security, install a reputable antivirus app (yes, they exist, and yes, for cheap or next to nothing).
[Nexus 7 (2013) Android Development] yourrealking:
What's the best workaround to keep it locked to Landscape?

I want the tablet to stay always in Landscape, and no auto-rotation. The reason is that I just use the tablet to watch YouTube, and you wouldn't want to watch YouTube in portrait mode. I watch YouTube while lying down, so if I don't disable auto-rotation, it often gets rotated to portrait accidentally. I also have disabled the lock-screen (that is, when I press the power button, it just shows the app).

The problem with this ROM is that if I have switched the tablet to landscape and the disabled auto-rotation, and if I turn off the screen and then turn it on, it gets locked to portrait.
[Nexus 7 (2013) Android Development] yourrealking:
The rotation confirmation button is displayed between the Home and the Recent buttons. Shouldn't it be displayed right to the Recent button?

[IMG="screenshot"]https://i.imgur.com/Xmh8Kum.png[/IMG]
[Nexus 7 (2013) Android Development] sushiboba:
Yeah, I think it's a bug... I can't even press it.... it should replace the "recent" button area... because trying to press that tiny area ends up just triggering the home button

I did toggle the auto-rotation button from the pulldown, as well as the rotation settings check/uncheck and it still doesn't fix it. Rebooting SOMETIMES work, but having to reboot all the time is annoying.

Yes, I noticed restarting does fix it most of the time, but not 100% and even rebooting, it ends up being locked again... it's pretty irritating... might have to install some third party app that will force the orientation... some apps that is only available in portrait mode ends up taking over the rotation even if you disable auto-rotation.