yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.0 - October 2019

It's time for AEX 7.0 - based on Android 10 !

The hardware "should" work the same way like in lineage-17.0 builds .. in my quick testing I did not see any problems.

The AEX team still calls it "ALPHA" .. no customizations yet

AospExtended-v7.0-flo-20191012-2213-ALPHA.zip

AospExtended-v7.0-deb-20191013-0953-ALPHA.zip

Working:

- Video

- Audio

- Wifi

- Bluetooth

- GPS

- Camera (needs more testing)

- Sensors

- DRM

- RIL (DEB device)

- etc.

Known issues:

- NFC has been taken out - maybe next build.

- Video: Some graphics glitches when you start to watch movies. (Skip/Stop video and play again a few seconds later)

- Sensors: Compass not working correctly (same problem on Pie CAF version)

- Maybe more ..

Installation:

1.) Do factory reset in TWRP - keep internal storage this way.

2.) Format /system partition in TWRP

3.) Install ROM

4.) Install BitGapps -> https://xdaforums.com/android/software/arm-bitgapps-q-10-0-0-t3968827 (optional)

5.) Install Magisk canary 19.5/20.0 (optional)

6.) Reboot into system and start to setup your device.

If you upgrade from previous Android 10 ROM - don't forget to install gapps and/or magisk afterwards again !

The backuptool is not ready for Android 10 - it's not part of the ROM installer yet.

Opengapps BETA packages for ARM (32Bit) seems to make problems on flo device.

Used the same ARM64 (64Bit) packages on 2 other devices without problems.

As it looks like the BiTGApps package does not include SetupWizard .. just playstore will be installed.

Tested with latest Magisk 19.5/20.0 (Canary builds).

If Safety.net check does not work just enable/disable "Magisk Hide" in Magisk settings menu.

Later this month the AEX Pie October version will come as well .. maybe for the last time !

AEX Partition sizes: Flo (stock) - Deb (stock +30MB) -> Deb needs reparition !

For the System repartitioning / Opengapps: Error 70 topic pls have a look on the first page.

Enjoy Android 10 :)
[Nexus 7 (2013) Android Development] clarkgable:
Thank you! Working smoothly for me so far.
[Nexus 7 (2013) Android Development] scrubsja:
[MENTION=5480152]followmsi[/MENTION] I need to add my thanks for the amazing work! Is there any way to get the device security pin for the lock screen working? When I set the pin code and try to change the unlock method from swipe the device returns an error "invalid pin code" message even though I am using the correct pin code set earlier. Each try to set a pin code is unsuccessful. How can we secure the device?
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=5480152]followmsi[/MENTION] I have tried both AEX and Lineage. I must say that Lineage is faster and smoother. I restored my TWRP backup of Lineage 17.0 for now.
[Nexus 7 (2013) Android Development] .MoHaMaD:
gapps

gapps arm 71 mg

test lineage-17.0-20191011

https://drive.google.com/drive/folders/17uBF8at0bGw-zstO6qgPuwF2Antmcd4T?usp=sharing

Credits=open_gapps and BeansGapps

## app ##

GoogleCalendarSyncAdapter

googlecontactssync

extsharedgoogle

soundpicker

## etc ##

# default-permissions #

default-permissions

opengapps-permissions

# permissions #

com.google.android.maps

com.google.android.media.effects

privapp-permissions-google

split-permissions-google

# preferred #

google

# sysconfig $

google

google_build

google_exclusives_enable

google-hiddenapi-package-whitelist

g.prop

## Framework ##

com.google.android.maps

com.google.android.media.effects

## Lib ##

libjni_latinimegoogle.so

## priv-app ##

GmsCoreSetupPrebuilt

googlebackuptransport

GoogleExtServices

googleonetimeinitializer

googlepartnersetup

GoogleRestore

GoogleServicesFramework

vending

PrebuiltGmsCore

## app densities ##

app/googlecontactssync-all/nodpi/
app/calsync-all/nodpi/
app/GoogleExtShared-all/nodpi/
app/soundpicker-all/nodpi/
priv-app/GmsCoreSetupPrebuilt/nodpi/
priv-app/backuprestore-all/nodpi/
priv-app/GoogleExtServices/nodpi/
priv-app/googleonetimeinitializer-all/nodpi/
priv-app/googlepartnersetup-all/nodpi/
priv-app/GoogleRestore/nodpi/
priv-app/GoogleServicesFramework/nodpi/
priv-app/Phonesky/nodpi/
priv-app/PrebuiltGmsCore/320/

## app sizes ##

backuprestore-all	nodpi	5096
defaultetc-common	common	136
defaultframework-common	common	232
extservicesgoogle-all	nodpi	116
extsharedgoogle-all	nodpi	20
gmscore-arm	320	84268
gmssetup-all	nodpi	6628
googlebackuptransport-all	nodpi	40
googlecontactssync-all	nodpi	2684
googleonetimeinitializer-all	nodpi	164
googlepartnersetup-all	nodpi	1168
gsfcore-all	nodpi	4208
soundpicker-all	nodpi	2696
vending-arm	nodpi	22296
calsync-all	nodpi	1808
swypelibs-lib-arm	common	932

## gapps remove ##

/system/app/ExtShared
/system/priv-app/ExtServices
[Nexus 7 (2013) Android Development] rubnduardo:
I succesfully flashed LOS 17 in my FLO but haven't had any luck with Gapps. Tried this and just did nothing with no error reported and BiTGapps ends in bootloop. Already searched the thread.

Suggestions?

UPDATE: Flashing BiTGApps 10.0 on LOS 20191011 realease shows ""Unsupported Android SDK version."" OpenGApps releases gives same error and identifies firmware's SDK as 6 but no bootloop, just apparently does nothing.
[Nexus 7 (2013) Android Development] .MoHaMaD:
flash rom

magisk 20

gapps
[Nexus 7 (2013) Android Development] dealpapa1:
when will god stop working on android 9?
[Nexus 7 (2013) Android Development] lollyjay:
Still rocking LOS 17. My friends are amazed that my six years old flo is performing this well well. ?
[Nexus 7 (2013) Android Development] lollyjay:
Battery.
[Nexus 7 (2013) Android Development] Ch3vr0n:
What about your battery? You getting good life, bad life? ...
[Nexus 7 (2013) Android Development] lollyjay:
I am getting 7 to 9 hours on-screen time with LOS

It sleeps muuuuch longer:D
[Nexus 7 (2013) Android Development] followmsi:
Thanks.

Have seen this too .. on. AEX.

Not sure about lineage now .. also not sure if this device or general system issue with qcom in the moment.

Both teams (aex and lineage) are working heavily on ten.

Need to check root cause .. will take a bit longer.

Cheers
[Nexus 7 (2013) Android Development] ipdev:
Works for me on a clean flash.

I see a SetupWizard is not included yet.

Is there a project source (GitHub, GitLab, BitBucket..) or is it a stand-alone project?

Just curious where this build came from. ;)

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.7 - October 2019 - DISCONTINUED

This is the end .. :)

I will continue on Android 10 only.

If you want to make your own Pie builds .. pls have a look here:

https://github.com/followmsi/manifests/tree/flo-deb-aex-pie

All my "final" ROM will be uploaded to androidfilehost.com ..

AospExtended-v6.7-flo-20191018-0652-UNOFFICIAL.zip

AospExtended-v6.7-deb-20191018-0837-UNOFFICIAL.zip

Changes:

- Google security updates -> October 2019

AEX partition sizes: Flo (stock) - Deb (stock +30MB) -> Deb needs reparition !

For the System repartitioning / Opengapps: Error 70 topic pls have a look on the first page.

Enjoy Pie :p
[Nexus 7 (2013) Android Development] xiwei26:
Look what i found！I will try it tomorrow！！！
[Nexus 7 (2013) Android Development] DorianX:
Thanks for your hard work! I'm on Lineage 17 running pretty well I just have a little problem trying to use Migrate https://xdaforums.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763/amp/ was working on Lineage 16 and AospExtended v6.7 without problems but on 17 got this: "No ROM is detected"

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Nexus 7 (2013) Android Development] hanssu:
Thanks so much for doing 10 to keep our Nexus 7 going strong :D

I used it for about a week without any issues. Now however it's suddenly stuck in a bootloop: It'll start all the way to the login screen (I can even quickly touch the screen to enter or trigger the volume widget), but after a second it'll always crash and reboot (watched it like 20 times now).

No idea what caused it, all I can think off is that before I had shut it down normally hours before at ~2-3% battery. When I tried to restart it had been on the charger for 10min already, though.

edit: alright, reinstalled now. Let's see how long it lasts.

BTW, it seems that a selected display lock method doesn't apply? At least after selecting the PIN pattern, it still directly unlocks by simple swipe.
[Nexus 7 (2013) Android Development] followmsi:
system-as-root (SAR)

Some (newer) devices were using it before .. but beginning with Android 10 it's mandatory for all devices.

Also for "legacy" devices like flo/deb.

We use "2SI" - 2 stage init - thru fstab in ramdisk !

Magisk team explains the different ways on how SAR got implemented into android devices.

Pls check magisk xda thread and twitter account for more details on SAR.

Various apps and tools do have problems with "system-as-root (SAR)" and all it's implementations.

It will take some time until all the tools have been updated.

Magisk 20 is ready for "most" of the SAR implementations.

If you install Magisk 20 on flo/deb Android 10 ROM you will see "Detecting .. system-as-root" on your screen.

Until all the apps and tools have been modified for SAR there are some workarounds in place ..

Dont' make installation queue in TWRP !

Install each zip file manually.

For gapps installation it helps if you mount system partition manually in TWRP mount menu - before gapps installation.

if mounted already in mount menu - unmount and remount again.

For other tools it helps to just copy "/system/system/build.prop" (SAR location) to "/system/build.prop" (OLD location before Android 10)

build.prop is just an example .. maybe your tools requires other files to be copied.

The logic to detect if "/system" is now located in "/system/system" is missing in most of the tools/apps today.

Actually some TWRP version for some devices use the flag "system_root" in config today - to let TWRP know about SAR.

Maybe next TWRP version will include also some additional "checks" for Androdid 10 SAR devices - and it's various implementations.

To summarize .. :)

Pls be patient until all the tools/apps have been updated for SAR on Android 10 !

Or use some workarounds to make it working today.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Pls have a look above .. system-as-root (SAR)
[Nexus 7 (2013) Android Development] followmsi:
keymaster problem is known .. finally have updated first page now ..

Known issues:

- NFC has been taken out - maybe next build.

- Keymaster: Encryption seems to have an issue .. Pls do not encrypt your data partition yet.

- Keymaster: Setting PIN/Pattern/Password does not work.

No idea about your other problems .. for this kind of stuff we need logs.
[Nexus 7 (2013) Android Development] tsiftsism:
I just flashed the Android 10 alpha version (I was using the Android Pie version till now) by following the steps in OP.

Can someone please explain what exactly i should do with the Safety.net check failure in Magisk?

I have read this

but I couldn't figure out what to do.

And another thing is that when AdAway is trying to download the hosts files, it gives me a "Copying of host file failed" error message.

Anyone else having the same issue?

Or should I ask in the AdAway thread here in XDA?

Thanks in advance for your answers.
[Nexus 7 (2013) Android Development] ipdev:
For SafetyNet, you need to restart MagiskHide.

Open MagiskManager

Go to Settings

Toggle Hide Off then On

You will need to do this after every reboot and/or when MagiskHide fails.

- At least until the issue with MagiskHide on some device(s) is found and fix.

So far for me, it's only after a reboot.

For AdAway

AdAway works on deb/flo AEX 7.0 and LineageOS 17 using Magisk v20 (and canary).

Open MagiskManager

Go to Settings

Tap on Systemless hosts and reboot.

-Systemless host is a module so, it is not active until a reboot after enabling it.

After the reboot, open MagiskManager and make sure Systemless Hosts is active under the Modules section. (Don't forget to toggle MagiskHide off and on again.)

Open AdAway, it should detect systemless mode, and configure/setup.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] tsiftsism:
Thank you so much.

I couldn't figure out where the on/of toggle was.

Now everything is ok.

Thanks again.
[Nexus 7 (2013) Android Development] DaCl88:
Thank you for the rom support of our old device.

The AospExtended-v7.0-deb-20191013-0953-ALPHA works fine.

The system runs smoother then AOSPExtended 6.6, which was installed before.

The battarydrain in standby is awesome. I only lost 4% battery over 12 hours.

I have some glitches in video playback only on youtube, but after some seconds the video is fine.
[Nexus 7 (2013) Android Development] Holgott:
Hi,i am on los17 without magisk.unfortunately Videos on Browser or YouTube APP are broken.they are greyed out, parts are cut out and the rest ist shown in a non watchable way. Is this a known Problem? If so,is there a workaround?
[Nexus 7 (2013) Android Development] hanssu:
It's happening again. Still not the foggiest why, only now I known it's unrelated to any battery issue (device was at 100%/charger all the time).

Can you point me to how I get those logs? I know Android keeps record of the last boot, but seeing it instantly reboots after the crash, that one probably constantly gets overwritten.

edit: sent you a PM with a logcat
[Nexus 7 (2013) Android Development] ttamo:
deb wifi connection stops working after a minute

Hi all,

Thank you all for keeping flo/deb fresh.

I'm using your LOS17 on a deb and it's working well.

But it sometimes starts to drop its connections.

5GHz connections are rather stable, but 2.4GHz are always dropped after about a minute or so of fine connection.

(I'm sure their signals are strong enough, but my deb doesn't think they are.)

dmesg seems to be suggesting there be something wrong with HDD, SME, or HeartBeat:

wlan: [5934:E :HDD] wlan_hdd_get_station_stats: SME timeout while retrieving statistics

wlan: [23730:E :SME] csrMoveTempScanResultsToMainList: 2908: 11d AP Bssid xx:xx:xx:xx:xx:xx chan= 11, rssi = -88, countryCode JP

wlan: [23730:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer

wlan: [23730:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 0

wlan: [23730:E :PE ] limHandleHeartBeatFailureTimeout: 7206: Probe_hb_failure: for session:0

Any updates are needed for deb wifi to keep connecting?

Quick googling shows something apparently related to the errors.

But I have no idea which of them applies also to deb.

For example,

https //review.lineageos .org/c/LineageOS/android_kernel_samsung_apq8084/+/233798

https //gitlab .com/Codeaurora/platform_vendor_qcom-opensource_wlan_qcacld-2.0/commit/753c1fa82b500ee838a6a0bc7fdc136b0acae926

https //gitlab .com/Codeaurora/platform_vendor_qcom-opensource_wlan_prima/commit/4bf03df2bfd6d606b3e3e5304013bf7e44ad45a6

If you are interested in my logs, I'm happy to send it to you.

Thank you.

edit:

Maybe the symptoms above was caused by GApps.

I rebooted it and found it went into a boot-loop.

So I re-installed it with MoHaMaD's gapps instead of BitGApps.

And it works well with my WiFi so far.
[Nexus 7 (2013) Android Development] ritvikp:
Do you wipe cache in between or at the end or dont do it at all? This sequence is different from the OP. There is states gapps before magisk. Do we flash magisk before or after gapps? On flashing gapps, I am stuck at AEX bootanimation.
[Nexus 7 (2013) Android Development] Baselineskip:
I flashed Magisk last:

rom -> gapps -> magisk

MoHaMaD's alternate gapps package worked fine for me. Wipe dalvik & cache after everything is flashed.

I am finding that this Android v.10 rom is superior to its predecessor for smoothness, etc.
[Nexus 7 (2013) Android Development] hanssu:
I've just booted into recovery to try the PIN removal zip.

Except TWRP (which greeted me with 1st boot questions) now shows that all my files are gone. Something either wiped or corrupted the f2fs data partition, I only know that it wasn't me.
[Nexus 7 (2013) Android Development] JT1510365:
Can you link the gapps your using I can't find it and is play store working?
[Nexus 7 (2013) Android Development] Baselineskip:
[MENTION=1120384]jt151[/MENTION]0365

Yes, Play store works fine. I used [MENTION=4551527].MoHaMaD[/MENTION]'s gapps package bc I did not want to go thru the somewhat complicated process of installing BitGapps.

BTW, dirty install of aex rom did not work bc of settings issues, had to clean install. This is a known issue.
[Nexus 7 (2013) Android Development] brewer75:
Deleted
[Nexus 7 (2013) Android Development] kjohnson04:
Glad I didn't try that.
[Nexus 7 (2013) Android Development] followmsi:
I had a very quick look into your logs and see "digital wellbeing" crashing ..

Did you install opengapps package ?

Pls read first page first !

There are a lot of strange problems with opengapps .. pls search for alternatives in this thread too.

Hope at some point all gapps packages work the "same" way on TEN !

Otherwise you have to start from scratch .. pls check first page for known issues too.

Cheers
[Nexus 7 (2013) Android Development] hanssu:
No, I hadn't, I used the one you linked. Digital Wellbeing was only installed later from the Playstore.

I tried manually deleting that app via TWRP before the partition was lost, the crashing persisted.

I think the log may have only captured the second variety of crash (with the permanent blackscreen+backlight) that was only an aftereffect of the actual initial crash (with the rebooting).

I'll probably leave my flo unused for a month or so hoping things can get ironed out… not much motivation to spend the hours of putting everything together atm when I'm risking just losing it all over again.

Anyway, obvious example to others to backup their important stuff before trying 10 out at this point. And thanks again for providing this rom.
[Nexus 7 (2013) Android Development] cucumbersmell:
Thank you for these builds! So much fun tinkering with my old N7 (2013) and it still runs great!

For other tinkerers:

I was not able to get xposed for Android 10 to work in order to use Gravitybox. Was giving it a try just for fun and possibly additional features. (Both LOS17 and AEX.)

DoubleTap2Wake is working when enabled in EX Kernel Manager -> Gestures. (Only tried in LOS17.)
[Nexus 7 (2013) Android Development] tsiftsism:
Have you flashed a kernel .zip file, or you just use EX Kernel Manager with the build in rom kernel?
[Nexus 7 (2013) Android Development] cucumbersmell:
Using the built-in kernel that came with LOS17.
[Nexus 7 (2013) Android Development] ritvikp:
While I am able to flash MoHaMaD's gapps successfully and dont get a bootloop, but it has no impact. Cant still see play store in drawer. Can't add goggle account as well. What could I be doing wrong?
[Nexus 7 (2013) Android Development] cucumbersmell:
Try flashing the sysrepart_1280_120.zip in the first post. That's what worked for me coming from Oreo.
[Nexus 7 (2013) Android Development] ritvikp:
That was the exact problem. I realised that the /system partition just has 12MB left after flashing ROM and gapps couldn't have got installed, although it does install without error. I, however, used [MENTION=7182780]k23m[/MENTION]'s script rather that sysrepart_1280_120.zip as [MENTION=7182780]k23m[/MENTION] has also posted an undo script and I was not sure if that script should undo 1280_120 repart as well :confused:. Or will it?
[Nexus 7 (2013) Android Development] ipdev:
followmsi's version (1280_120) is a modified version of k23m's.

The modified version gives more space to system by reducing cache even more.

The resizing happens by removing the stock system and cache partitions. What is left is a combined empty space. This empty space is then used to create two new partitions. You can make these partitions what ever size you want along as they both fit inside the empty space.

The undo script works the same way, removes system and cache partitions to crate the empty space. Then it creates the system and cache partitions to be the same as stock was.

Hope this helps explain a little about (re)partitioning a device.

So yes, the undo script will work with followmsi's modified version.

The GApps package that you are installing only checks for API (SDK/NDK) version.

It is deceptive what TWRP displays on the screen versus what is in the TWRP recovery.log file.

The install script actually runs correctly that's why you see no error on the screen.

The unzip command executes properly so the script continues even though the files being extracted, run out of space in system.

The installer script (of the Gapps package you are using) basically has six steps.

[mount system; check SDK version; remove conflicting files; unzip system files to system; change(correct) permissions; unmount system]

Note:

Truncated post.

PM me if you want the long answers.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] ritvikp:
Thanks. Then I will rather use [MENTION=5480152]followmsi[/MENTION]'s zip as it gives marginally larger /system. Although, I felt that the system+cache after running the script is more than stock system+cache. Could that be possible?

Not being fussy but swipe on AOSP keyboard is leading to app crashing. Also chromecast is leading to force boot. Anybody else noticing these? Just reporting.
[Nexus 7 (2013) Android Development] nicky-xda:
Thanks a lot for android 10! :)

Does this mean that i could try to instal the BETA opengapps ARM64, even if our nexus 7 is an arm 32bit device?
[Nexus 7 (2013) Android Development] mido hamdy:
How to enable double tap to wake in AosapExtended Pie?

I used Kernel auditor and FK kernel manager but failed.
[Nexus 7 (2013) Android Development] DCvan:
It worked fine for me with KA wake setting to half.
[Nexus 7 (2013) Android Development] mido hamdy:
I will try to set it to half because when set it to full failed for me, thanks bro.
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.0

One more build ..

It's the first time the flo build is crashing (at 99%) due missing space on system partition. :(

I am used to it from DEB device.

Both devices .. FLO and DEB do have 900 MB system partition now !

Both devices will need to be repartitioned to be able to install the ROM at all.

Pls check fist page about this topic !

AEX team has upgraded to android-10.0.0_r9 .. Pixel 4 sources.

It's also October secuity level.

Lockscreen (Password/Pin/Pattern) is working now.

Full Disk Encrytion (FDE) should work too .. needs more testing.

The AEX team still calls it "ALPHA" .. a few more customizations - but still a lot is missing ..

AospExtended-v7.0-flo-20191027-1121-ALPHA.zip

AospExtended-v7.0-deb-20191027-1258-ALPHA.zip

Changes:

- Fix for Keymaster (Lockscreen Password/Pin/Pattern)

- system partition size to 900 MB ( FLO and DEB )

- Kernel: memfd backport

- Latest AEX changes

Pls check first page for installation instruction and known issues.

Tested flo version with Magisk 20.0.

Enjoy Android 10 :)
[Nexus 7 (2013) Android Development] followmsi:
Lineage-17.0

One more build .. and one more build crash.

The DEB device build has crashed due to missing space on system partition.

For FLO device it's the last build with STOCK partition size. (840 MB)

In the future .. same like for AEX - both lineage-17.0 builds (FLO and DEB) will have 900 MB system partition !

Both devices will need to be repartitioned to be able to install the ROM at all.

Pls check fist page about this topic !

Lockscreen (Password/Pin/Pattern) should work like on AEX now.

Full Disk Encrytion (FDE) should work too.

Lineage has shipped "Trebuchet" launcher .. and some other minor changes ..

lineage-17.0-20191027-UNOFFICIAL-flo.zip

lineage-17.0-20191027-UNOFFICIAL-deb.zip

Changes:

- Fix for Keymaster (Lockscreen Password/Pin/Pattern)

- system partition size to 900 MB (this time for DEB only)

- Kernel: memfd backport

- Latest LineageOS changes

Pls check first page for installation instruction and known issues.

Enjoy Android 10 :)
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=5480152]followmsi[/MENTION] I'm up and running with 1027 los for deb. Thank you!

Also activated RCS messaging so im flat-out up to date ?