yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] n3kf:
Decided to try this ROM. Have been using Lineage for a while. I get a new/old device and decided to try it here. Had some trouble repartitioning, but finally got it. Installed the latest, gapps, and Magisk 19.3. Magisk was failing safteynet and was not hiding root from apps. Saw that there was a problem with some devices and dropped back to 19.2. All worked at that point. ROM runs smooth and seems to give good battery life. Lots to test.

Thanks to the Devs. Seems to be an excellent ROM!
[Nexus 7 (2013) Android Development] followmsi:
No idea.. Stuff like this should get fixed by AEX team within the next releases.

Can't confirm and can't replicate.. On the weekend I was listening music from wlan thru Bluetooth speakers for hours without problems.

More details please...
[Nexus 7 (2013) Android Development] pss34:
Need to say, I like this ROM. I had tested official RR, but the battery life was terrible even with turned off all radios and screen. No more than 2 days without any usage. Now i can use it freely for reading e-books and watching video. And BT keyboard is working well for me, I need my talet to ssh to remote hosts.

Thanks a lot, [MENTION=5480152]followmsi[/MENTION]!
[Nexus 7 (2013) Android Development] yourrealking:
I wish there is swipe-up navigation. I mainly use tablets in landscape mode, and Android tablets waste a lot of space on the navigation bar in that orientation. I could hide the navigation bar, but then I cannot navigate. Samsung's latest Galaxy tablets have swipe-up gestures. Swiping up from left is back, middle is home, right is task overview. If that is available on Nexus 7, it will be much easier to navigate without the navigation bar.
[Nexus 7 (2013) Android Development] lollyjay:
I am using Vivid Navigon Gestures from the Play Store. It works very well and can hide the regular navigation bar
[Nexus 7 (2013) Android Development] followmsi:
The final classic builds for flo/deb ..

flo-Classic_08-2019_AOSP_9.0.0_r46_followmsi.zip

deb-Classic_08-2019_AOSP_9.0.0_r46_followmsi.zip

Changes:

- Google security updates -> August 2019

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

Enjoy classic AOSP :p
[Nexus 7 (2013) Android Development] L.F.B.:
Sorry my ignorance, Master [MENTION=5480152]followmsi[/MENTION]

The classic rom is just pure AOSP?
[Nexus 7 (2013) Android Development] ipdev:
[MENTION=4522247]L.F.B.[/MENTION]

The Classic builds are as basic as it can be.

No bells or whistles. (Unless it's part of Android Open Source.)

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] followmsi:
"Classic" builds are based on "pure" AOSP sources with some minor changes.

AospExtended is "real" custom rom with a lot of more "features" ..

https://aospextended.com/

https://blog.aospextended.com/AospExtended-v6.6-Changelog/

The current 08-2019 builds are the final classic builds for flo/deb .. at least for Android Pie.

Today it's not sure if I will have the time to work on Android Q for flo/deb .. maybe later this year.

For the next time I will continue to make monthly AEX Pie builds .. August builds will come in the next days.

Same here .. it's not sure if and when we can switch to upcoming Android Q.

Cheers
[Nexus 7 (2013) Android Development] L.F.B.:
Thank you Master [MENTION=5480152]followmsi[/MENTION]

I cant live without this great AEX rom for our N7! ?

Android Q wen come out we hope u continue your development ???
[Nexus 7 (2013) Android Development] yourrealking:
I think I found a bug. Not critical, but still.

Create a widget to the settings->battery. After rebooting, click the widget to open the Battery settings. Clicking the percentage to see the usage graph crashes the screen.

A workaround is first to open the settings normally (not from a widget) and then visit Battery. Now close the settings. From now on, clicking the widget and then clicking the percentage does not crash the screen.
[Nexus 7 (2013) Android Development] dealpapa1:
Android Q Android Q Android Q
[Nexus 7 (2013) Android Development] n3kf:
I am on the AospExtended. If I have magisk and gapps, if I dirty flash to a newer version, do I only have to reflash magisk or do I need to do both magisk and gapps? Thanks
[Nexus 7 (2013) Android Development] brewer75:
Unless the dirty flashing process has changed recently, all you have to flash is the ROM update, everything else continues on without re-flashing.
[Nexus 7 (2013) Android Development] followmsi:
Pls report to AEX team directly .. I will have not the time to forward your bug report.

Thanks for understanding.
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.6 - August 2019

AEX team has still not merged the August patches .. http://gerrit.aospextended.com/q/topic:"P_aug_asb"+(status:open OR status:merged)

For this reason I did cherry-pick them now ..

AospExtended-v6.6-flo-20190820-1134-UNOFFICIAL.zip

AospExtended-v6.6-deb-20190820-1322-UNOFFICIAL.zip

Changes:

- Google security updates -> August 2019

Tested flo version with Magisk 19.2 !

Magisk 19.3 seems to have some Magisk Hide issues on certain devices.

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

Enjoy :p
[Nexus 7 (2013) Android Development] L.F.B.:
Where I can find magisk 19.2? The Magisk thread only have the 19.3...?

Edit.

Found it!

https://github.com/topjohnwu/Magisk/releases

Why this problems with latest 19.3 magisk? My N6 whith AICP rom have the same problem..
[Nexus 7 (2013) Android Development] tiis:
Thanks for the August security update, [MENTION=5480152]followmsi[/MENTION]

Unfortunately, when trying to flash the August build I get Error 7 (seven) in TWRP on flo (TWRP 3.3.1-0, Magisk 19.3, no gapps, no repartition in place).

I did a system/caches wipe and later successfully went back to your July build.

Any ideas?
[Nexus 7 (2013) Android Development] Ch3vr0n:
'no repartition in place' that's probably your problem right there. System partition to small.
[Nexus 7 (2013) Android Development] dealpapa1:
Android 10 Android 10 Android 10
[Nexus 7 (2013) Android Development] ipdev:
TWRP Error 7 is incompatibility.

Wrong version of a file.

Device is detected improperly.

(Quite a few other things depending on what is being checked.)

- The twrp recovery.log should show what triggered the error. -

Sometimes just wiping caches and or system and rebooting into twrp will work.

(Sometimes wipe or format data may be required.)

Easiest way to grab the log file, connect to your computer and run

adb pull /tmp/recovery.log

or

In the Advanced menu in TWRP select Copy log. This will save the log file to your internal (sdcard) storage.

Then connect to your computer and grab the recovery.log file from there.

It should be in the TWRP folder.
[Nexus 7 (2013) Android Development] followmsi:
It's because of this change ..

https://github.com/followmsi/android_device_asus_flo/commit/a04857c5e53c68c03b9be54edda51334afac9830

flo/deb: Extend SYSTEMIMAGE_PARTITION_SIZE

- Extend from 840MB to 870MB

- AEX uses more space in system image.

- Especially DEB device build fails due to missing space left on system partition.

Sorry, I did not mention this change in last build infos ..

Deb will not work anymore with stock size anyway .. to keep "standard" config I did change system size for both devices Flo/Deb.

For next build I can split Deb and Flo config for system image size.

We keep stock size for Flo until it breaks build process like for Deb device today.

Are you able to install gapps without system/cache repartitioning at all ?

At some point you may have to do the repartition process anyway ...

Cheers

EDIT:

Here you are ...

https://github.com/followmsi/android_device_asus_flo/commit/aabeff256c482beec75fd895cdcc090dcb32ee5e

https://github.com/followmsi/android_device_asus_deb/commit/690bba6d64374b5284617b4aee6d59d32debc93b
[Nexus 7 (2013) Android Development] tiis:
Thank you for the heads up!

I really hate the new "be evil" Google, hence, I only use microG and never tried to flash gapps.

Btw, thanks for allowing Signature Spoofing in your rom! :cool:
[Nexus 7 (2013) Android Development] Debanka:
Installing the latest build along with pico gapps has caused a bootloop. Any solution?
[Nexus 7 (2013) Android Development] biontx:
When dirty flashing:

Something is wrong with the boot.img file in AospExtended-v6.6-flo-20190820-1134-UNOFFICIAL.

Replace it with the one in AospExtended-v6.6-flo-20190723-0811-UNOFFICIAL and all should be well.
[Nexus 7 (2013) Android Development] curiousde2002:
Wireless charging

Hello everybody,

the USB connector of my Deb is worn out and charging is no longer possible.

So I'm considering wireless charging but I've never used this before.

I understand that earlier AEX ROMs support wireless charging but what about the more recent ones?

I also don't know what charger to buy?

Anybody could recommend one that is currently available?

Thank you very much in advance!
[Nexus 7 (2013) Android Development] n3kf:
I charge wireless and it works fine on this ROM. I use the following chargers and they work quite well. I'm sure many others would also.

CHOETECH Wireless Charger, 3 Coils Qi Certified Fast Wireless Charging Pad 7.5W Compatible iPhone Xs Max/XR/X/XS/8/8 Plus, 10W Fast Charge Galaxy Note 10/S10/S10+/S10E/S9/S8, 5W All Qi-Enabled Phones https://www.amazon.com/dp/B07D2CWBS1/ref=cm_sw_r_cp_taa_va1yDbDJFAJAM
[Nexus 7 (2013) Android Development] dealpapa1:
Android 10 source code is being uploaded to AOSP - XDA Developers
[Nexus 7 (2013) Android Development] jerethi:
I bet the N7 could run Android 10. This tablet has held up shockingly well over the years.
[Nexus 7 (2013) Android Development] ojcu:
Is there anything I need to do to charge wirelessly? I've just got the charger. The led on it lights up like it's charging but nothing on my Nexus...
[Nexus 7 (2013) Android Development] Ch3vr0n:
The led doesn't stay on during charging, if you want to make sure, just press the power button and look at the battery icon
[Nexus 7 (2013) Android Development] n3kf:
The lock screen will tell you if it's charging. Just hit power button after it's locked. It will say charging or charging slowly depending on your setup. Plus the battery icon will show the lightening bolt
[Nexus 7 (2013) Android Development] ojcu:
Yeah, got it. Just had to find the g spot ?
[Nexus 7 (2013) Android Development] jacopastorius:
I installed this rom and this is really great. Anyway, I have a problem with Play store that let me install just one app and then i got the message "waiting for download" if i try to download other apps. I need to reflash gapps (i use pico) to get play store to let me install just one app again. I tried clearing cache and play store data but the waiting message persist
[Nexus 7 (2013) Android Development] tsiftsism:
If i dirty flash the latest version of this rom, do i need to also flash opengapps and Magisk zip files?
[Nexus 7 (2013) Android Development] jerethi:
No. They should persist.
[Nexus 7 (2013) Android Development] v12xke:
Just reflash the ROM and OpenGapps immediately afterwards. I've been using Nano for the past couple of AEX builds and since they (OG) renew every day, get the newest version before flashing it. No issues with PS here. GL :good:
[Nexus 7 (2013) Android Development] schidddy:
hey folks, unfurtunately i cant make this rom to install properly, i keep on getting the error 7 trying to install the newest rom un twrp. Also wiped and factory reset everything on twrp. I also changed to a lower twrp Version with no sucess.

i also changed the updater script to skip the model checking according to this thread: https://xdaforums.com/showthread.php?t=2522762

the installer starts this time but after the "patching the system unconditionally" it says E1001: failed to update the system image

updater process ended with ERROR 7

EDIT

Problem solved, i accidentally choose the wrong file (deb) on the download page. Now i got it working, unleast up to the AEX Logo after installing the ROM, Gapps and Magisk. I had to repartition the System because Gapps didnt install due to lack of storage. Now i get stuck on the AEX Logo for a long while now...i used the file from Clamor to repartition, is that a problem i used that one?

i have a normal nexus 7 2013 with 32gb

any help out there?

cheers
[Nexus 7 (2013) Android Development] schidddy:
update:

my nexus gets stuck on booting the first time a new rom, also tried different roms, always the same.

Do i miss anything?

i Did the follwing

unlocked the bootloader, installed TWRP

installed Clamors Repartition tool

installed the special TWRP for it (3.3.1-1 UA)

Wiped Everything more then on time.

pushed ROMS and GAPPs

Wiped Cache and Dalvik.

no Matter what i do, ROMs dont boot

any help is gretaly apprecitated

cheers
[Nexus 7 (2013) Android Development] jerethi:
There's a special TWRP for the repartition tool?
[Nexus 7 (2013) Android Development] schidddy:
according to clamors how to, yes:

https://xdaforums.com/nexus-7-2013/orig-development/repartition-nexus-7-2013-repartition-t3844386
[Nexus 7 (2013) Android Development] jerethi:
As I interpret OP in this thread, you don't need a special version of TWRP. I'd use the repart zip in OP. That's what I did and haven't had any problem.
[Nexus 7 (2013) Android Development] nicky-xda:
Starting not possible without usb-cable connected since last update 2019-08-20

Since the last update 2019-08-20 i cannot power on my n7, when the usb cable is not connected (and n7 charging).

The battery is ok, long-pressing the power-button (and combinations of vol-up/down) does not solve the issue.

Any ideas?
[Nexus 7 (2013) Android Development] adstraylight:
I have a weird issue with this ROM, there is a weather app that I use regularly, that crashes when trying to load the weather map specifically, all it's other functions work fine.

The same app runs fine on my n4 running PIE via carbon ROM, so my guess is that it is a device specific problem. Here is the crash log generated by the app:

time: 1569063121424 msg: androidx.renderscript.RSRuntimeException: Loading of ScriptC script failed. stacktrace: androidx.renderscript.RSRuntimeException: Loading of ScriptC script failed.	at androidx.renderscript.ScriptC.<init>(ScriptC.java:83)	at uk.gov.metoffice.weather.android.j.a.<init>(ScriptC_image_splitter.java:34)	at uk.gov.metoffice.imaging.sdk.android.library.ImagingLayerManager.onImageLoaded(ImagingLayerManager.java:108)	at uk.gov.metoffice.imaging.sdk.android.library.network.LayerMetaDataNetworkManagerImpl$2.onResponse(LayerMetaDataNetworkManagerImpl.java:75)	at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:177)	at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)	at java.lang.Thread.run(Thread.java:764)

I was wondering if this was something to do with the app or the ROM...?

The same app ran fine on my flo using 8.1 from UA BTW...
[Nexus 7 (2013) Android Development] adstraylight:
To add to my last, here's a logcat..
[Nexus 7 (2013) Android Development] followmsi:
If you go back to previuos ROM .. from month before - all is Ok again ?
[Nexus 7 (2013) Android Development] followmsi:
Sorry .. no time left to look into this issue now ..

Are you able to test another PIe ROM for flo ?

Maybe it's just a device issue (flo) or general AEX ROM (for all AEX devices) ?

We need to check this first ..

Meanwhile they have already released version 6.7.

And they are working on plenty of changes/fixes .. still for Pie.

Maybe this fixes your issue too.

Coming with next build .. hopefully - it's up to AEX team.

Still waiting for security updates .. not much progress here.

http://gerrit.aospextended.com/q/topic:"P_sept_asb"+(status:open OR status:merged)

Cheers
[Nexus 7 (2013) Android Development] adstraylight:
Tbh it's not such a big deal, and it's the only thing that doesn't work for me, I just wondered if something in the log jumped out as a probable cause. I'll wait for the next build. Everything else suits me very well ?
[Nexus 7 (2013) Android Development] nicky-xda:
Starting not possible without usb-cable connected since last update 2019-08-20

Since the last update 2019-08-20 i cannot power on my n7, when the usb cable is not connected (and n7 charging).

The battery is ok, long-pressing the power-button (and combinations of vol-up/down) does not solve the issue.

Any ideas?

It was OK on the previous ROM until i updated to the newest 2019-08-20.

But when i now go back to the previous ROM it does NOT solve the issue.
[Nexus 7 (2013) Android Development] yourrealking:
Are the LOS 17.0 ROMs in the same Google Drive supposed to be usable? I could not find any post for it, but I have tried install it. It stuck at the LOS boot animation. I have tried formatting all the partitions (such as Data), but the results were the same.
[Nexus 7 (2013) Android Development] followmsi:
Android 10 development for flo has started .. :)

There are still a lot of issues .. and it will take longer to solve them !

The builds in gdrive folder are for testing - the latest build should boot up, still not tested myself.

If the builds are ready for "public" testing I will let you (all) know.

Cheers
[Nexus 7 (2013) Android Development] jerethi:
So glad to hear this!
[Nexus 7 (2013) Android Development] dealpapa1:
oh my god:highfive:
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.7 - September 2019

Very late this month ..

AospExtended-v6.7-flo-20190930-1357-UNOFFICIAL.zip

AospExtended-v6.7-deb-20190930-1537-UNOFFICIAL.zip

Changes:

- Google security updates -> September 2019

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

- Update to AEX 6.7 -> https://blog.aospextended.com/AospExtended-v6.7-Changelog/

Tested flo version with Magisk 19.2 !

Magisk 19.3 seems to have some Magisk Hide issues on certain devices.

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

Enjoy :p
[Nexus 7 (2013) Android Development] prsa01:
Flo previously repartitioned 1280/120, dirty flash from previous version with twrp 3.0.0.0.

No issues, all working great.

Thanks again for maintaining this!
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=5480152]followmsi[/MENTION] any chance of getting a kernel that allows overclock? Have I missed something?
[Nexus 7 (2013) Android Development] adstraylight:
If you look in the Kernel folder that is under the same gdrive link as the ROMs, there is an alterative kernel there called elementalx. This is overclockable. It was built in March, but is still compatible.

Edit: it looks like just the GPU is overclockable, sorry as this is all I use.
[Nexus 7 (2013) Android Development] nicky-xda:
Unfortunately, after update to the newest ROM 2019-09-30, still the same issue. Any idea how to solve it?
[Nexus 7 (2013) Android Development] MarviXDA:
Power button is OK? Disassemble n7 and check it.
[Nexus 7 (2013) Android Development] nicky-xda:
Yes, it is. I can use it without issues when the system is started.
[Nexus 7 (2013) Android Development] Baselineskip:
Running AEX flo now, excellent rom.

Thank you [MENTION=5480152]followmsi[/MENTION]
[Nexus 7 (2013) Android Development] dealpapa1:
October 2019 Android Security Update Now Available for Pixel Devices (Updated)
[Nexus 7 (2013) Android Development] AdeTheux:
That one doesn't work for GPU overcloking either. Only a few minor changes are possible (limit battery charge to x%, disable magnetic cover, etc).
[Nexus 7 (2013) Android Development] followmsi:
No need to open a new thread :)

Android 10

Let's start Android 10 testing on flo/deb devices !

It's a Lineage-17.0 (CAF version) - as "base" for all other custom ROM !

There will be no pure "classic" AOSP version this time !

Once AEX is ready for TEN we can make test builds too.

The sources are still a bit chaotic - device tree and kernel sources are online.

A lot of stuff I had to implement before it will be implemented thru regular lineage change management.

The additional patches will be uploaded to GitHub too.

It's an early version .. some problems are to be expected.

Especially opengapps (beta) installation is quite tricky. And dirty upgrade from Pie could make trouble.

All the lineage customizations are also missing - too early !

The Android 10 development for flo/deb device was a bit "special" this time.

All the testing has been done by [MENTION=7280276]ipdev[/MENTION] - big thanks to him !

Working:

- Video

- Audio

- Wifi

- Bluetooth

- GPS

- Camera (needs more testing)

- Sensors

- etc.

Known issues:

- NFC has been taken out - maybe next build.

- RILD (telephony) still not fully working (DEB only)

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

- maybe more ..

Latest Magisk 19.5 is working for root access - Safety.net check does not work without workaround.

As workaround you can enable/disable "Magisk hide" in Magisk settings menu.

Seems to be the same problem starting with version 19.3 on Pie - hope this will be fixed at some point.

And here we are ..

lineage-17.0-20191010-UNOFFICIAL-flo.zip

lineage-17.0-20191010-UNOFFICIAL-deb.zip

Enjoy Android 10 :)
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=5480152]followmsi[/MENTION] how to flash?
[Nexus 7 (2013) Android Development] followmsi:
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 (optional)

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

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.

Hope this helps you (all) ..

Cheers
[Nexus 7 (2013) Android Development] lollyjay:
Thanks working well so far. Super fast. Few small things broken such as battery icon display. I'm happy :laugh:
[Nexus 7 (2013) Android Development] followmsi:
Lineage-17.0 - October 2019

One more build .. to fix DRM.

lineage-17.0-20191011-UNOFFICIAL-flo.zip

lineage-17.0-20191011-UNOFFICIAL-deb.zip

Changes:

- Google security patch level -> October 2019

- Fix for DRM

- Latest Lineage changes (all the changes of the last 3 weeks are merged now)

Enjoy Android 10 :)
[Nexus 7 (2013) Android Development] lollyjay:
Thank you. How do I upgrade from previous build?
[Nexus 7 (2013) Android Development] followmsi:
I made dirty upgrade from previous ROM .. no problems.

But don't forget to install gapps and/or magisk afterwards again !

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

Cheers
[Nexus 7 (2013) Android Development] lollyjay:
Did not work for me. Settings is fubar
[Nexus 7 (2013) Android Development] sir_bazz:
Dammit!

Back on 14.1 at the moment but this so tempting.

Outstanding work!
[Nexus 7 (2013) Android Development] anivegmin:
Haha same here. With 14.1 everything works and you can just use the device. So tempting to waste some time and try 17.0 though (needs testing).
[Nexus 7 (2013) Android Development] razvangabriel82:
I feel like the today's build is much smoother than the one from yesterday. However, I had to do clean installation in order to have the settings app back again. Anyways, terrific job!