yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] bitstra:
Going to Install and test it now - thx!

---------- Post added at 05:33 PM ---------- Previous post was at 05:18 PM ----------

[MENTION=5480152]followmsi[/MENTION]

installed sensors.qcom AS described.

Works Like a Charm!

Screen Rotation - OK and fast.

GPS - OK.

Compass - OK

Lightsensor - OK.

Xyz- Sensors Not Tested for now...
[Nexus 7 (2013) Android Development] followmsi:
Thanks for testing ..
[Nexus 7 (2013) Android Development] logitechor:
Thank you for updating to Lineage 17. So far just testing out. For me - what I need to work it does. Seems smooth too.
[Nexus 7 (2013) Android Development] bitstra:
OK, while having my morning coffee I took the time and tested all sensors with updated sensors.qcom

Perfectly! See attached screenshot.
[Nexus 7 (2013) Android Development] cucumbersmell:
EdXposed with Gravitybox [Q] is working great on LOS17! Gives me all the additional customization options I need. Did not work on AEX.

Thanks for these builds!
[Nexus 7 (2013) Android Development] nicky-xda:
GAPPS working already?

I want to dirty update - without wiping DATA - to this v17 from AospExtended-v7.0.

Unfortunately it does not work with the BitGapps.

Anybody tried the Gapps if it's working now?
[Nexus 7 (2013) Android Development] Gorky24:
open_gapps-arm-10.0-pico-20191114-BE
[Nexus 7 (2013) Android Development] nicky-xda:
Thanks, but what do you exactly mean by your posting? ;)
[Nexus 7 (2013) Android Development] crypt0kiddie:
*UPDATE*

prsa01 post below this was my issue, his instructions fixed my issue.

-------------------------------------------------

Someone gave me a Nexus 7 2013 Wi-Fi

I've unlocked and installed TWRP.

I've tried this ROM as well as a few others and I just keep getting:

Updated process ended with ERROR: 7

A quick Google brought me to multiple Youtube videos and XDA thread on this issue. I ended the updater-script as outlined and I'm STILL getting the error.

Thoughts?
[Nexus 7 (2013) Android Development] prsa01:
Repartition

You don't mention repartitioning. Read the portion of of first post related to that. Hopefully that will solve the problem.
[Nexus 7 (2013) Android Development] KHOATUM:
Hello, I got the Asop running with gapps. I've got two problems.

1. Home button, all apps, settings from drop down menu doesnt do anything.

2. Brightness always goes back to default

What should i do?
[Nexus 7 (2013) Android Development] warp_zone:
I'm using flo and I experienced these issues when I used opengapps on the gdrive.

If I use the latest official beta or BiTGApps, these were solved on AospExtended. (but on LOS weren't)

Compared with AospEx, LOS seems to be more buggy. I found these issues on LOS.

* can't change to dark mode

* can't change battery status view style

Now I reinstalled AospExtened and almost all functions are fine. Battery consumption is about 2 or 3 percent/hour.

The small issue I have confirmed on AospExtended is QR code wifi setting;

* When I try to share wifi setting with QR code, setting app has no response.

* When I set wifi SSID and pass by reading QR code, setting app are terminated abnormally.

Anyway, I really appreciate for [MENTION=5480152]followmsi[/MENTION] 's hard work!!

---------- Post added at 08:31 AM ---------- Previous post was at 08:15 AM ----------

I forget to write about sensors...

After replacing sensors.qcom, all the sensors and compass are working as same as stork rom! (I checked on "GPS Status & Toolbox" app)

On flo custom roms, A-GPS can't be used?

XTRA data seems to be downloaded successfully, but satellite info doesn't show up unless device is in the open air and it takes about 10 minutes to cold start.
[Nexus 7 (2013) Android Development] SoulSmasher:
Using the AospExtended-v7.0-flo-20191117-1106-ALPHA on my flo. Working great so far, no issues whatsoever. Thanks for supporting this device and making this available! :)
[Nexus 7 (2013) Android Development] followmsi:
Thanks for feedback.

I had a quick look ..

For me sharing QR codes works on AEX .. i can see pasword in clear text below QR code.

But as you mentioned, setup a new connection thru QR code does crash settings app.

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

As well .. in AEX there are also tons of "WifiLinkLayerStats" log entries in logcat .. flo does not support this kind of stats.

https://review.lineageos.org/c/LineageOS/android_frameworks_opt_net_wifi/+/260124

The changes are missing in "general" AEX sources .. and will hopefully come later on .. as it's still called ALPHA.

For next release I will cherry pick the 2 changes above - but no more "general" fixes.

Just to explain (again) .. I do not care for "general" problems in the moment !

I want to fix device related issues first. (like sensors .. etc.)

And I know .. for "you" (all) it's hard to differentiate between device related and general problems.

The flo/deb device/kernel/vendor sources are more or less ready for TEN .. some minor stuff is left.

CRdroid is good example of using "same" sources for other custom ROM.

At some point all the "important" changes should be part of all the different types of custom ROM.

My plan is to handover lineage-17.0 beginning of next year and continue to build AEX only.

The December patches for Pixel 4 did arrive today .. very late this month.

All the teams have been waiting for it .. not sure when they get implemented into the various custom ROM.

New December builds should hopefully come before Christmas :)

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Did you boot into system before gapps installation ?

Pls reinstall from scratch .. sounds like something went wrong.
[Nexus 7 (2013) Android Development] DCvan:
Regarding the new sensors test, I didn't notices any different. However my NordVPN connection keep disconnecting from basic news article to Twitter to YouTube. It's a mystery, was running fine previously.

I made a copy of the default sensors and reverted back. NordVPN connection is fine again.

I also redownload the sensor from GitHub link, same problem.

Maybe if someone can test the NordVPN with the test sensor?

Thank you so much for taking your time to keep flo running!
[Nexus 7 (2013) Android Development] warp_zone:
I find that QR code sharing works when device lock is disabled.

(I usually lock my device with pattern auth.)

I'm verry sorry that I don't know whether this issue is device related or general...
[Nexus 7 (2013) Android Development] cucumbersmell:
Workarounds that are working for me:

Dark Mode = substratum + Liv Dark Theme

Battery view (status bar options and more) = EdXposed + Gravitybox [Q]
[Nexus 7 (2013) Android Development] Sobek5150:
Hey guys - I'm on the last Pie build of AEX for my two Flo devices. Charging seems to be incorrect. It's charging (based on lock screen info) at 1mA. It gives me about 4+ hour estimates on charging. it does this on both devices. Cable and Charger are high quality and no issues on other devices.

Anyone else experiencing this? Suggestions? Eventually I plan to move to A10 - but just holding off for the time being.

Thanks!
[Nexus 7 (2013) Android Development] Keltek:
I have the same issu and discover the workaround. Plug the USB-A connector not fully. Make only power contacts connected but not the data contacts. This works for me with any usb cable.
[Nexus 7 (2013) Android Development] Ally L.:
Google Contacts

I've run into a strange issue that I've not seen anyone else mention... Recently I did a clean install of LOS 17.0-20191107-flo with BiTGApps-arm-10.0.0-v0.5, and for some reason Google Contacts would not sync no matter what I try. What's interesting is that BiTGApps presumably installed one version of Google Contacts (1.7.31, which has no "uninstall" option), but when I open the app page in the Play Store, it would say "Install" instead of "Update," as though the existing version isn't recognized. I've tried installing the new version (3.14.0.282336800), disabling the old, clearing the cache/storage, but none of it made a difference -- the app (either version) would act like it's syncing for a while, then come back with a still-empty list and no error message. My other Google apps, like GMail and GVoice, are working fine, so I'm baffled. I'd appreciate suggestions on what else to try. Thanks!
[Nexus 7 (2013) Android Development] ipdev:
Google Contacts work for me on flo and deb.

Installed from PlayStore.

Sounds like it's something with the BitGapps install.

First check permissions and turn on (or off and on) for contacts.

Also what is the package name of the contacts installed by BitGapps?

(Long press icon on select App Info.)

com.google.android.contacts would be Google Contacts and should show installed in PlayStore.

com.android.contacts would be AOSP Contacts. Not Google version, will not show in PlayStore.

Besides permissions, maybe it has to do with the version of play services or webview that you have installed. (or some other conflicting app.)

I don't use BitGapps and normally just skim that thread.

The older threads have been closed and a new combined thread was started.

BitGapps xdaThread - Link

When I pulled up the thread to see if I could find instructions on using the config script. Hey look at that..

The only Known Issue on the OP of BitGapps new thread.

Didn't have time to search the thread but, it's a known issue and someone may have a workaround posted in the BitGapps thread.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] followmsi:
Confirmed .. tested on another device running lineage-17.0 .. same problem with active lock screen.

It's on my "open issues list" now .. but no idea by when it will be fixed.
[Nexus 7 (2013) Android Development] followmsi:
Sounds strange .. did you find solution?

Reinstall your vpn app ..?

Quick search for NordVPN shows a lot of "privacy issues" with this provider.

Maybe now as you send them proper sensors values they don't like you anymore. :)
[Nexus 7 (2013) Android Development] DCvan:
Reverting back to your default seem to have a stable connection, but from time to time connection still break. The alpha build so far running great except for this VPN.

I'll wait for the next build from you and try a clean install. Thanks so much for your time in keeping flo up to date!
[Nexus 7 (2013) Android Development] Ally L.:
Thank you [MENTION=7280276]ipdev[/MENTION] for your response!!

I normally used OpenGApps, but I had read that some folks were running into issues with setup using OpenGapps on this ROM, so I decided to try BitGApps. If all else fails, I may go back.

I tried turning permissions on ("People Details" under Google Account was the only place I found) but unfortunately didn't change anything.

The package name of the old Contacts app was "com.android.contacts" -- that explains why it didn't show in Play Store.

Thanks for the heads-up to the BitGApps thread! Supposedly installing Magisk along with the ROM and BitGapps sometimes causes the Contacts Sync Adapter to break, but I didn't install Magisk. Even so, I thought I'd try the suggested workaround -- turn on permissions for the Sync Adapter -- and I'm still trying to figure out how.
[Nexus 7 (2013) Android Development] ipdev:
Settings -> Apps & notifications -> See all (Number of apps) apps -> Upper right (3-Dot Menu) Show system

That should show all apps installed. Select the one you want and then select Permissions.

(Check for Contact Storage and Google Contacts Sync or Contacts Sync)

A quick look a my flo,

Contacts (AOSP) -> Disabled

Contacts (Google) -> Permission = Contacts

Contacts Storage -> Permission = Contacts and Phone

Google Contacts Sync -> Permissions = Contacts

- So I broke it on mine by disabling Contact Storage, took me a few minutes to get it working again. After I enabled Contact Storage, I tried wiping storage and cache on the apps. Still didn't work, ended up having to toggle Contacts off and on under Settings -> Accounts -> username@gmail.com -> Account sync to get it to work again.

Good luck.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Ally L.:
Success! The permissions on my flo matched yours except Google Contacts Sync, which had no permissions; once I granted permission to Contacts, sync finally worked. (If the workaround solved the issue, maybe the root cause had nothing to do with Magisk... Who knows!)

Thank you so much [MENTION=7280276]ipdev[/MENTION]!! :)
[Nexus 7 (2013) Android Development] followmsi:
Lineage-17.0 - December 2019

The December build .. but we are still on November security patch level !

No idea when Lineage team will apply security patches this month ..

lineage-17.0-20191221-UNOFFICIAL-flo.zip

lineage-17.0-20191221-UNOFFICIAL-deb.zip

Changes:

- Google security updates -> Still November 2019 (10.0.0_r11) !

- Latest LineageOS changes for Android 10 -> still a lot of lineage stuff is missing.

- Kernel: Patch for lowmemorykiller

- Disable NearbyMessagingService

- New System.img partition size for flo and deb -> 950MB

- Drop "buggy" QCOM avc decoder

- New "sensors.qcom" binary -> Thanks to Unlegacy Android Team

system-as-root (SAR)

https://xdaforums.com/showpost.php?p=80591849&postcount=2709

Pls check first page for installation instruction and known issues.

Enjoy Android 10 :)
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.0 - December 2019

The December build .. but we are still on November security patch level !

Like LineageOS too .. the December security patches are not merged yet ..

AospExtended-v7.0-flo-20191221-1752-ALPHA.zip

AospExtended-v7.0-deb-20191221-1942-ALPHA.zip

Changes:

- Google security updates -> Still November 2019 (10.0.0_r14) !

- Kernel: Patch for lowmemorykiller

- New System.img partition size for flo and deb -> 950MB

- Drop "buggy" QCOM avc decoder

- New "sensors.qcom" binary -> Thanks to Unlegacy Android Team

- Latest AospExtended changes for Android 10 -> still a lot of stuff is missing.

- Patch for WifiStats log spam (cherry picked from LineageOS)

- Patch for Wifi QR Code -> Settings app does not crash if you scan Wifi QR code (cherry picked from LineageOS)

system-as-root (SAR)

https://xdaforums.com/showpost.php?p=80591849&postcount=2709

Pls check first page for installation instruction and known issues.

Tested flo version with Magisk 20.1

This time the ROM installer did backup existing opengapps installation and did restore after ROM installation.

Also Magisk will be automatically re-installed too .. like in Pie before.

Enjoy Android 10 :p

And have a good start into 2020 .. cu you next year !
[Nexus 7 (2013) Android Development] ryaniskira:
How are you using the latest OpenGapps beta on Aospex? The installer claims that I am running 7.1.2, and when modifying the install.sh script to "lie" about what Android build it's for, it complains about lack of space (yet the Gapps zip included in the Drive folder flashes without complaints). Failing that, please link your build of BiTGapps as the thread has absolutely zero links to it.
[Nexus 7 (2013) Android Development] ipdev:
Free space error is the same as SDK check.

System is not mounted properly so, it falls back to the defaults in TWRP.

- Mount system in TWRP before installing Gapps.

- Adjust the mounting part of the installer.

Some examples using the 20191209-nano installer script.

(I included the comment out of provision also.)

Add /system back to mounts.

Example 1 GitHub - Link

Mount system or system_slot to system and remount.

Example 2 GitHub - Link

Mount system_root or system then remount if needed.

Example 3 GitHub - Link

Hope it helps explain a few things.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] DCvan:
Go to page 277, post by [MENTION=7280276]ipdev[/MENTION]. I used his OpenGapps Mod.
[Nexus 7 (2013) Android Development] nicky-xda:
Wifi issue on dirty update to AospExtended7/LOS17: could not be saved/connected

On clean instal wifi is working ok.

When i dirty update from AospExtended6.7 - without wiping "DATA" ( wiping only "system/dalvik/cache") - WiFi will not connect, it shows: could not be saved/connected.

Is there a way to reset the WiFi network?
[Nexus 7 (2013) Android Development] mido hamdy:
does video glitches on youtube fixed?

how is the battery backup compared to android 9 builds? thanks.
[Nexus 7 (2013) Android Development] ipdev:
Hi all.

If you are using my modded OpenGapps.

Notes about the 20191222 builds.

Nano and below should work fine.

Micro and above will break trebuchet.

Please look at this post for more information and possible workarounds.

[ROM][OFFICIAL][LineageOS][15.1][dragon] - [Lineage-16.0/17.0] xdaPost #1456 - Link

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] reignydeyz:
Most features aren't working

Hi. I've been wanting to install Android Q to my nexus 7. I've tried clean flashing your builds with LOS at first but I came across a lot of features that don't work. Here are some of them:

* Home button (circle)

* Task button (square)

* The slide menu also doesn't work when you click the icons in it.

* Bluetooth is crashing

P.S. I also tried tha AEX and I still got same results. I hope you find this post helpful and I look forward to flashing your future builds. Though, I still want to say kudos to the dev for making this effort. :)
[Nexus 7 (2013) Android Development] ipdev:
Sounds like a symptom of something else not installing correctly.

If you clean flash (wipe system, data and caches) just Lineage or AEX (No gapps, magisk, kernel ...) and reboot, do the issues still exist?
[Nexus 7 (2013) Android Development] crypt0kiddie:
Looks like "KHOATUM" posted a couple pages back and was having just about the same issues.

I'm also having these issues. I've tried flashing a couple times now and each time I basically can't use the ROM because the home and task buttons do nothing.

Someone speculated that GApps might be the issue elsewhere.
[Nexus 7 (2013) Android Development] crypt0kiddie:
*Update*

OK I just flashed the newest version of AospExtended, I was one version behind, I now have the one in my signature.

That one also had the same issues with the task and home button. I flashed a total of 3 times, with GApps and Magisk and got the same results all 3 times.

I'm using "open_gapps-arm-10.0-pico-20191114-BETA-test.zip" and "Magisk-V20.1.zip".

As long as I don't flash GApps, I'm fine. Magisk doesn't seem to cause issues.

Is the above GApps this the incorrect GApps to be using with these ROMs?

*Update #2*

As I said, it constantly breaks if you flash the ROM, GApps and then Magisk all in one shot BUT I found if I install just the ROM and do a full reboot, let it settle on the home screen and then boot back into recovery, I can flash the above GApps and its fine.

Maybe I missed this as being the proper way to do this, I thought you could install all of them in one shot. My bad if I misunderstood.

I tried wiping and re-flashing all 3 again after getting it to work, it broke again but as soon as I tried flashing just the ROM again, rebooting and then GApps, it was fine again. Doesn't seem to matter when you do Magisk.
[Nexus 7 (2013) Android Development] aquatix:
I've got the same problem, did anyone have a fix?
[Nexus 7 (2013) Android Development] ipdev:
That's why I asked if it happens with a clean install, rom only. ;)

In the beginning, Magisk caused Lineage to be glitchy on first boot. Since then, updates to Magisk and Lineage, I have not seen this problem since.

As for GApps, the problems you describe come from provision being removed without having a working SetupWizard. With the newer OpenGapps_BETA builds, SetupWizard starts but crashes at the WiFi, and the pixel overlay breaks the stock launcher(s).

By leaving provision installed, SetupWizard will not run and you will start at the home screen. (You will have to manually set the time, date, ... under Settings.)

I switched to AEX_alpha 7 on my main (daily use) flo about 2 months ago.

AEX_alpha 7, sGapps and Magisk canary-debug.

I use OpenGapps_nano-MOD for testing and on my arm64 devices.

The modded OpenGapps is only a workaround. Once OpenGapps 10 becomes stable, I will stop the MOD versions.

Note about the 1222 builds. xdaPost #2836 - Link

List of GApps. xdaPost #2766 - Link

(Looks like I'm going to have to edit the gapps link post a little.)

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] DaCl88:
Thank you vor this fantastic AEX ROM.

My old Nexus 7 2013 deb runs smooth and without any problems.

This ROM is better than every oreo and pie Custom-Rom.

The problems with youtube video playback are fixed in this version.

A made a dirty flash over the build from 20191013 and i have no freezes or errors.

I have installed this Rom, OpenGapps from your googledrive folder and magisk 20.1.

Then I only clear the cache and everything works fine :)
[Nexus 7 (2013) Android Development] hellochrome:
Deleted
[Nexus 7 (2013) Android Development] edison0354:
In commit history, I saw QCOM AVC codec is removed. Does it mean Android Q on Nexus 7 can not hardware decode H.264 anymore?
[Nexus 7 (2013) Android Development] DaCl88:
Your are right.

On Kodi with the last build in h264 only uses the software decoder.

On the build from oktober the hardware decoder was used.
[Nexus 7 (2013) Android Development] prsa01:
Flo, Lineage 17 dirty flash from previous build w/bitgapps & magisk reflash. Had a few more initial glitches than previous update. Recurring "android.process.media keeps stopping". Cleared cache &data, rebooted a few times. Ultimately things seemed to settle down and has been working well for the last day or so.

As always, thank you much for your time!
[Nexus 7 (2013) Android Development] Артибальт:
How to increase the volume threshold on this android assembly? Cannot find mixer_paths.xml file.

Thanks.
[Nexus 7 (2013) Android Development] warp_zone:
Sorry for late reply.

I used open_gapps-arm-10.0-pico-20191114-BETA-test.zip, and without any trouble when installing it.
[Nexus 7 (2013) Android Development] Spyr0s:
I installed latest lineageos and gapps from OP. I confirm the bugs previously mentioned also im getting an error E1001 when trying to install the ROM after resizing, you need to reboot recovery after resizing and then install rom. Did a second try, i installed rom, booted, then back to recovery to install ipdev's pico gapps (22/12/arm) from his gdrive and i had a few bugs here and there. Setup Wizard is crashing all the time, then android settings is crashing, then system is complaining that selinux is persmissive, some problems with GPS - not working until i open Maps, i need to set up everything manually. I left it for a few hours but now im back to stable 7.1.2., because Solid Explorer is crashing when i try to copy text (eg copy Wifi pass from txt) and Nova Launcher doesn't support gesture navigation yet.
[Nexus 7 (2013) Android Development] ojcu:
Does anyone else have battery life issues on the latest AospExtended?
[Nexus 7 (2013) Android Development] damian6017:
there is problem with google family link account cant add device Safety.net passed any ideas
[Nexus 7 (2013) Android Development] hapklaar:
I do, but on the latest LineageOS. Device has much less battery life compared to LOS15 I used before.
[Nexus 7 (2013) Android Development] ojcu:
I think, in my case, it's a dirty flash with few complications that caused it. I've just clean flashed, set up Greenify and we'll see.
[Nexus 7 (2013) Android Development] ritvikp:
Opengapps in the link above are arm64. I don't think they are working with this ROM. I could not locate your post with the link for arm builds. Can you help? I am using an older build.
[Nexus 7 (2013) Android Development] DCvan:
Page 277, post by [MENTION=7280276]ipdev[/MENTION] OpenGapps mod (nano & Pico arm) works.
[Nexus 7 (2013) Android Development] DCvan:
Happy New year! To you [MENTION=5480152]followmsi[/MENTION], all the best in 2020!?

Thank you so much for you to take your time to keep our devices software New! ?

Happy New year to everyone in 2020!✨??
[Nexus 7 (2013) Android Development] followmsi:
AVC codec will be re-added for next build .. seems to be the better way, even we get some glitches in YouTube app.

https://github.com/followmsi/android_device_asus_flo/commit/9ad412490254acc5a1bbfa3bd0ce829555d245c1

Happy new year !