yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] supertaco:
Sorry and thank you for your time. It's an old Nexus 7. The first batch of the first nexus 7. I've opened the tablet and discovered on the nand the reading Kingston.
[Nexus 7 (2013) Android Development] MarviXDA:
It's wonderful! Thanks!

Add. Tested on deb, last aosp rom. 2 devices, main and test.
[Nexus 7 (2013) Android Development] crypt0kiddie:
Where is the "bootanimation.zip" located? Its not in /Systems/Media/...
[Nexus 7 (2013) Android Development] MarviXDA:
Look at /system/product/media
[Nexus 7 (2013) Android Development] yourrealking:
The old initial screen orientation problem, that started to appear since LOS 15, still exists in LOS 17.1. That is, if I lock the screen orientation to landscape (auto-rotation disabled), and I set the screen lock to "None", and I press the power button to turn the screen off and press it again to turn the screen on, the screen rotations to portrait.

This problem does not happen in AOSP EXT. That is, AOSP EXT in the situation above, starts in landscape mode, as it should be. But unfortunately, AOSP EXT lacks some of the features LOS 17.1 has such as ADB over Wi-Fi toggle, so I would like to use LOS 17.1, if possible.

In case of LOS 17.1, if I don't disable auto-rotation and check "Rotate lock screen", which is only enabled when auto-rotation is enabled, then LOS 17.1 starts in landscape mode in the situation above. So, to me, this does not seem like a limitation (that LOS cannot start in landscape mode) of LOS, but more of a BUG. I mean, the lock screen is not even enabled (set to "None"), so why does LOS think that it needs to show the lock screen in portrait mode and start in portrait mode? That is, if the lock screen is disabled, it should start with the last known orientation, not from portrait. Or, even if auto-rotation is disabled, if the screen orientation is fixed to landscape, the lock screen should start in landscape mode. I mean, why would someone who has fixed the screen orientation to landscape want to see the lock screen in portrait mode?

Anyway, if it is not very difficult to fix, please fix this problem in LOS.
[Nexus 7 (2013) Android Development] crypt0kiddie:
Thanks!

---------- Post added at 03:18 AM ---------- Previous post was at 03:16 AM ----------

Holy CRAP this current version of "AospExtended-v7.0-flo-20200116-1010-UNOFFICIAL" runs freaking amazing! I've ran previous versions from Nov and December that didn't work this well.

It's like a whole new tablet!
[Nexus 7 (2013) Android Development] jw243:
Installed the latest LOS 17.1 build from January 15th. Everything seemed to work well. Then I tried to encrypt data partition. First boot got stuck in LOS boot animation. After forced switch off tablet booted normally, asking for decryption pathphrase on the way. In settings, it shows data partition as encrypted.

Would it be possible to have the data partition force encrypted right out of the box?

And would it be possible to include "double tap to unlock" feature in kernel?

Would it be possible to set SELinux to "enforcing"?

Thanks for the great work.
[Nexus 7 (2013) Android Development] ipdev:
Sorry, I should have stated that better.

I was referring to how/what I initially installed and setup.

How many backup scripts were going to be used.

50-lineage.sh (los)

50-base.sh (aex)

70-gapps.sh (gapps)

91-iYTv7a.sh (My backup script for vanced)

99-magisk.sh (magisk)

blacklist (What and where did/does this come from?)

Steps used:

Clean flash (Wipe and format all)

Initial install ROM (see list below.)

Boot system and make some changes.

Screen size and/or navigation bar and/or dark mode and/or setup WiFi and/or setup google account.

Reboot into recovery and dirty flash (re-flash ROM only) and reboot.

Initial install ROM only, dirty flash works.

Initial install ROM and OpenGapps, dirty flash works.

Initial install ROM and Magisk, dirty flash works.

Initial install ROM, OpenGapps and vanced, dirty flash works.

Initial install ROM, Magisk and vanced, dirty flash works.

Initial install ROM, OpenGapps and Magisk, dirty flash ends with a bootloop. WTF ?

So it appears the backup scripts are running and it does not matter how many backup scripts there are.

Something is conflicting, getting corrupted or removed/not replaced when using both magisk and opengapps.

No more skimming logs, time to scour them. :(

Not sure if it's Magisk, OpenGapps or something else yet.

Notes:

I copy vanced YouTube into system/priv-app and add a backup script in addon.d

Bootloop is due to kernel panic.

[ 2.540679] No filesystem could mount root, tried: ext3 ext2 ext4 vfat ntfs fuseblk f2fs
[ 2.541137] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
.
[ 5.650665] Rebooting in 5 seconds..
[ 10.658050] Going down for restart now
[ 10.658233] in panic

Clean flash (wipe and format everything) installing ROM, gapps, magisk, kernel, whatever else... Works fine.

Cleanish dirty flash (wipe system) then reinstalling ROM, gapps, magisk, kernel, whatever else I installed that modifies system. Works fine.

Using the backup scripts should be the same result.

Did not make a difference:

Magisk with and without modules installed/active

In some ROM/device threads it's recommended to disable modules before updating the rom. I never had a problem with the modules I use but, I tried it both ways for testing.

Installing ROM and booting into system. Then rebooting into recovery to install magisk.

Wiping cache(s) after dirty update before rebooting into system.

I gave up on wiping cache(s) awhile ago.

Made a difference:

Slightly older version of OpenGapps Pico. - Dirty flash worked with Pico and Magisk installed.

Workaround:

Pull boot.img from ROM zip and reflash boot.img and then patch with magisk after the dirty flash.

Cheers. :cowboy:

PS.

WOW!

Sorry all, that turned into a super long post. :o
[Nexus 7 (2013) Android Development] DCvan:
[MENTION=5480152]followmsi[/MENTION] the latest AEX7 0116 build is running great (very smooth), clean install with OpenGapps Beta Pico 0116 build.

Was wondering can the grayish black in settings be change to dark black as in quick setting?
[Nexus 7 (2013) Android Development] pacman00700:
Great ROM. Thanks. Anyone able to get signature spoofing to work to enable Gmicro?
[Nexus 7 (2013) Android Development] followmsi:
Would it be possible to have the data partition force encrypted right out of the box?

- NO .. will not be included into ROM - pls use manual workaround.

And would it be possible to include "double tap to unlock" feature in kernel?

Yes - It's already part of the kernel .. the ElementalX code has been used - activate thru kernel manager tools.

Would it be possible to set SELinux to "enforcing"?

- No .. maybe later on.
[Nexus 7 (2013) Android Development] followmsi:
blacklist (What and where did/does this come from?)

Approx. 8 years ago ..

https://github.com/LineageOS/android_vendor_lineage/commit/129989b172c48d8937d7b104d2146b567b4c1dcc

https://github.com/LineageOS/android_vendor_lineage/tree/lineage-17.1/prebuilt/common/bin

Initial install ROM, OpenGapps and Magisk, dirty flash ends with a bootloop. WTF ?

Made a difference:

Slightly older version of OpenGapps Pico. - Dirty flash worked with Pico and Magisk installed.

What has changed in opengapps .. again ? :)

I always tested opengapps and magisk only .. no more other addon scripts.

Maybe I have used older gapps version .. thats why it was working for me.

Tested on other A-only devices too.

But lineage (did not check AEX) is not fully ready with all the adjustments for TEN .. etc.

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/267400

https://review.lineageos.org/q/addon

As it looks like we still need to be more patient to get all the "tools" working for A-only devices on Android 10.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Pls ask Lineage or AEX team directly.

AEX did implment in Pie .. but not yet in TEN.

Linage normally does not like it :)

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Don't know .. pls ask AEX team directly or wait until TEN development has been finished.
[Nexus 7 (2013) Android Development] Guichinga:
First of all, thanks for still supporting this device, which is still working for me perfectly - despite its age!

I was coming from the Lineage OS 16 version which was becoming really laggy :eek: and therefore I was performing a clean installation of the AEX7 0116 build together with OpenGapps Beta Pico and Magisk and finally even the newly provided kernel.

The rom is running pretty good and I don't experience any lags at the moment - which is really amazing! :o

Actually I have the following topics identified which I wanted to report, as I couldn't find dedicated hints so far:

1. The lockscreen will accept either the pattern or PIN only after some time (maybe ~30 seconds) before the tablet is getting unlocked.

2. My router is set on 5 GHz wifi only with auto-channel acitivated and wifi NOT being hidden. With this setting I don't get wifi connected after every reboot of the device automatically. After disabling wifi and re-enabling it again, I can connect to my wifi manually. If I activate 2.5 GHz on my router as well, then the connection works straight forward after the reboot. The same issue I had already experienced under LOS 16 before - which got obviously introduced some months ago, as before it has been working without any issues!

Actually I am glad having my beloved Flo running Android 10!

Hopefully I didn't miss any postings on my topics ;)
[Nexus 7 (2013) Android Development] R3M768:
Seems there's something going wrong when i install for flo. I wiped system, then install the rom followed by gapps. I get the lineage boot animation and then it reboots into recovery. Is there something i am doing wrong?
[Nexus 7 (2013) Android Development] MarviXDA:
Try to install with old gapps version, gapps-arm-10.0-20191015-fix.zip
[Nexus 7 (2013) Android Development] jimmybreeze:
Hello all!

I am trying to install this on my Nexus 7 2013 but unfortunately I'm getting Error 7 on it.

I've scoured the internet and done a fair amount of troubleshooting already.

1. I am updated fully on the device with stock, so 6.0.1.

2. I for sure have a 2013 since it has 2GB of RAM and no LTE, so trying to install flo. I did try deb as well, but that didn't work either.

3. I am using the latest version of TWRP, 3.3.1.0.

4. I've tried older versions of TWRP as well, trying to match what the youtube instructors were using.

5. I've deleted the "Assert" line in the install script.

6. The way I wipe it is go to Wipe in TWRP and choose "Factory Reset." Should I be doing something else here?

No matter what I do, I'm back to "Error 7." Any other suggestions?

Thanks!
[Nexus 7 (2013) Android Development] MarviXDA:
One step is missing - repartition.

See the 1-st post.
[Nexus 7 (2013) Android Development] ThWunderlich:
Have you repartitioned the tablet?

As far as I remember Error 7 hints to the size of the partitions.

Oh, not fast enough...
[Nexus 7 (2013) Android Development] jimmybreeze:
Ah, the videos I watched did not have that, will try it soon. Thanks to you both!
[Nexus 7 (2013) Android Development] MarviXDA:
You are a brave man. To flash device without reading of instructions... ?
[Nexus 7 (2013) Android Development] jimmybreeze:
Ha, I didn't read these instructions, per se, just other instructions...

But curious, since it said I would get error 70, not error 7, from not repartitioning. But will do so anyways and see what happens.
[Nexus 7 (2013) Android Development] ipdev:
Hi.

I repeat this quite a bit across threads. ;)

At least three times in this thread.

xdaPost - 2445 - 2637 - 2789

TWRP error 70 is lack of space to install.

You will probably need to repartition your device if you haven't already.

TWRP error 7 is compatibility.

- Wrong version of a file.

- Device is detected improperly.

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

The TWRP recovery.log file should show what triggered the incompatibility error.

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

Sometimes wipe and/or format data may be required.

To grab the recovery.log file.

Easiest way to grab the recovery.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.

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] jimmybreeze:
Hi, after repartitioning with the script, I was able to install with the same install of TWRP and the same LineageOS 17.1 zip that I had been originally trying, not sure why it was giving me Error 7 since I was using the same zip file. But I have it up and running like a dream. Thanks for putting up with the repeat questions.
[Nexus 7 (2013) Android Development] ipdev:
Good to hear you got it to work.

Just noticed you are new to xda.

Welcome to the xda family :)
[Nexus 7 (2013) Android Development] followmsi:
For Wifi .. pls test new kernel .. even you do not use hidden network.

For lockscreen - Can't replicate now - need to check.
[Nexus 7 (2013) Android Development] followmsi:
Lineage-17.1

Like mentioned before .. I did plan to handover Lineage-17.1 beginning of 2020.

That's done now.

This thread will be used for AEX only.

There is a new thread for lineage-17.1 .. https://xdaforums.com/nexus-7-2013/development/rom-lineageos-17-1-t4038425

[MENTION=6005084]ripee[/MENTION] will continue to build regular lineage-17.1 builds for flo/deb.

If there are some code changes in the next time .. we test on AEX first and apply changes to Lineage sources later on.

Like always .. I have uploaded my last builds to androidfilehost.com ..

https://androidfilehost.com/?w=files&flid=289295

Thanks to [MENTION=6005084]ripee[/MENTION] for taking over !

Cheers
[Nexus 7 (2013) Android Development] Guichinga:
Thanks for your feedback. As mentioned before, not a big issue for me, I can handle it ;)

Regarding the kernel, I am using already the latest available kernel under your kernel folder flo-deb-followmsi-kernel-ten-20200117.zip. The kernel was already part of my initial fresh installation.
[Nexus 7 (2013) Android Development] AdeTheux:
Weird, I've done this update many times but this time WiFi doesn't work anymore after installing the ZIP. It's not a hidden network. When I try to connect, it just states "failed to save" or "failed to connect".

Happens with both WiFi networks at home (main and guest).

Any thoughts?
[Nexus 7 (2013) Android Development] DorianX:
Did you tried latest kernel?

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.0 - January 2020 - Part 2

The last builds for this month !

This time for deb device as well ..

NFC has been enabled now .. seems to run good.

Played YouTube video on my phone and "beamed" it to Flo .. YouTube app starts and does play the same video.

AospExtended-v7.0-flo-20200122-1535-UNOFFICIAL.zip

AospExtended-v7.0-deb-20200122-1718-UNOFFICIAL.zip

Changes:

- Enabled NFC

- Kernel: latest changes for (hidden) Wifi networks.

- Patched libstagefright_omx.so

- Latest AospExtended changes for Android 10

Tested dirty install on flo - ROM installer did backup/restore my opengapps pico and Magisk 20.3 installation without problems.

Enjoy Android 10 :p
[Nexus 7 (2013) Android Development] JT1510365:
Great work buddy as always without your awesome work and expertise i would never be able to make my awesome roms and we probably would never experience android 10 on one of the best tablets in my opinion on the nexus 7 2013. I am so so very grateful for you man:) Thanks for all the help you have given me along the way. Also if you ever want to take a break if you feel overwhelmed we will understand:)

God bless ya!
[Nexus 7 (2013) Android Development] MarviXDA:
Aggressive wifi scan in developers menu is ON or OFF?
[Nexus 7 (2013) Android Development] reignydeyz:
Menu still doesn't work

Hi.

I know I've posted this before, seems the issues keep recurring....

* Home button (circle)

* Task button (square)

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

* Bluetooth is crashing
[Nexus 7 (2013) Android Development] MarviXDA:
Last deb rom testing. Dirty flashing. 1-st device. 2 little issues:

1. The shape of icons changed to default.

2. Google search appears at the bottom of screen.

No more issues. This rom is wonderful. Thanks!
[Nexus 7 (2013) Android Development] AdeTheux:
I don't seem to have that setting. The closest is wifi throttling.
[Nexus 7 (2013) Android Development] followmsi:
I do not change button / icons shape or search bar stuff at all !

All the "desgin" part is done by AEX team .. like they want, not like "we" want :)

If there are issues/problems with menu, icons or buttons just let them finish their work .. they left alpha state some days ago.

You may contact AEX team directly in telegram or thru other channels to let them known about this stuff.

This may speed up fixing time for certain issues ..

I will not have the time to forward your findings.

I take care for the device relaed stuff .. like Bluetooth.

Can't replicate Bluetooth crashes .. pls post logs of your BT problem.

Hope you have better understanding !

Cheers
[Nexus 7 (2013) Android Development] AdeTheux:
Same problem with AospExtended-v7.0-flo-20200122-1535-UNOFFICIAL.zip, if that's what you mean.
[Nexus 7 (2013) Android Development] followmsi:
Tested fresh connection to 5 GHz network.. no hidden network - no problems.

Saved the network .. can connect without problems and can switch between other networks.

Delete all files in /data/misc/wifi and reboot .. test again.

If still not working do clean install .. factory reset in twrp !
[Nexus 7 (2013) Android Development] Guichinga:
Did a dirty flash of the latest rom for Flo - without flashing GApps and Magisk again, and it worked great.

Even my 5 GHz wifi was recognized straight forward as well and the overall performance and speed of the device is still fantastic!
[Nexus 7 (2013) Android Development] MarviXDA:
Last deb rom testing. Dirty flashing. 2-nd device. 2 little issues, same as on first device.

And one more serious. Gapps and some programs (chrome for example) don't work.

Reflashing of new piko gapps fixed this problem.
[Nexus 7 (2013) Android Development] nathankferguson:
Man this has made my tablet completely new. Thanks so much for all you guys' hard work.

Only issue I'm having is I'm unable to edit my build.prop and having issues adjusting permissions in system. Any advice?
[Nexus 7 (2013) Android Development] AlesUlrych:
Hi,

I have a question. As I understand from the discussion here, Nexus 7 2013 should also support 5G Hz wifi. I don't know why, but my tablet doesn't see any such wifi, only 2.4 GHz. Did you buy some special Wifi card into it or was it made more different pieces of Nexus 7 2013? Or is it possible that in Europe (Czech Republic) is different 5Ghz Wifi than you have?

I tried both LineageOS 17.1 (latest) and AOSPExtended v7.0 (2020-01-22)

I have a Flo version of 16GB.

Ales
[Nexus 7 (2013) Android Development] andrei15:
Check wifi channel on router. Nexus 7 2013 can not support specific channels.
[Nexus 7 (2013) Android Development] AlesUlrych:
Thanks a lot,

already see wifi 5G ...
[Nexus 7 (2013) Android Development] Guichinga:
Okay, the issue on the 5 GHz network auto-connection is - at least on my network - the channel setting.

If I have the channel set fixed onto channel 36, then the device is recognizing the wifi network and performs an auto connection successfully and the network is shown within the available network list.

If there is any higher channel set either manually - or by autochannel on my router, then I have to connect it manually, as the network is not getting recognized as available, the network isn't visible on the list at all. After disabling WIFI and re-enabling it again, the network will be shown for a while to connect, and later on it disappears again.

Maybe this could help the devs somehow in troubleshooting!?
[Nexus 7 (2013) Android Development] cucumbersmell:
I haven't tested yet with AOSPExtended, but new Open GApps are working with Setup Wizard on Havoc. I'm using Pico.

https://www.xda-developers.com/open-gapps-android-10-roms/

Edit: Tested and working with AOSPExtended!
[Nexus 7 (2013) Android Development] boki0812:
Does anybody have problem with random restart, afer last update?

Any info how to solve this problem?
[Nexus 7 (2013) Android Development] MarviXDA:
I have. And it's not a problem of the last rom. And it's not random.

It happens if amount of free memory becomes below 200 Mb, approximately.

I think, this is normal behaviour.

---------- Post added at 05:39 AM ---------- Previous post was at 05:23 AM ----------

The last deb rom is much more optimized then previous. So, reboots have become much more rare.
[Nexus 7 (2013) Android Development] AlesUlrych:
Hello,

AOSP Extended has been working perfectly for several days, Youtube, NewPipe, Video - everything works perfectly.

Netflix just doesn't work for me, but there's nothing I can do about it. Error 5.7 after several seconds of playback. PlayProtect is certified, Netflix updated. I don't have a liboemcrypto.so file that I recommend deleting somewhere. Maybe someone can tell you what to do with it.

And I have one more question.

I've seen a Youtube video showing that this tablet can be recharged via Wireles charging - link

Has anyone tried it? Isn't it Fake? Is it worth buying a Wireles Qi Charger? I therefore ask that the USB port would not be used so often if I charge the tablet wirelessly.

Thanks everyone for every help. :)

Ales
[Nexus 7 (2013) Android Development] taw62:
Sure, it can be charged wirelessly. But it's not very fast, so it takes a while.
[Nexus 7 (2013) Android Development] MarviXDA:
Wireless charging is working with any wireless charger. One of my deb devices with broken usb port was used in so way during more then one year.

About liboemcrypto.so. Did you try Netflix WITH it?
[Nexus 7 (2013) Android Development] AlesUlrych:
Unfortunately, I have not seen this file in lib at all, but it is true, before a few updates AOSP I tried to add to Magisk "Netflix Enabler", which could delete the file "liboemcrypto.so". But then I reinstalled AOSP several times, now I don't have the "Netflix Enabler" add-on in Magisk, I uninstalled and reinstalled Netflix, but the liboemcrypto.so file is still missing in / lib. Maybe the new version of Netflix is no longer used ...

Or do you have a problem with Netflix? Is it just me?
[Nexus 7 (2013) Android Development] MarviXDA:
I don't use Netfix.

And i have only libcrypto.so in rom, not liboemcrypto.so
[Nexus 7 (2013) Android Development] AlmostIdiot:
Try this version: https://androidfilehost.com/?fid=529152257862715472
[Nexus 7 (2013) Android Development] AlesUlrych:
Great,

it looks like this version works. I was offered an update right after installation, but I disabled it. The newer Netflix is up-to-date in Czech, which is not, but it does not matter at all, the main thing is that it works and plays the film series with Czech dubbing.

Thanks again for the link.

Ales

Edit:

Incredibly,

Netflix works perfectly with your version !!!

I've been staring at the witchers all night. :)

Thanks a lot again.
[Nexus 7 (2013) Android Development] bcote311:
Flashed the rom to give try it out. Great job!! Thank you! I was a little hesitant to do the repartition at first but the zip flashed fine and all is well!! Is anybody using anything special for "hold back to kill" in the meantime until it is added? Do you even need things like that on 10 anyway? Thanks again!
[Nexus 7 (2013) Android Development] MarviXDA:
Deb rom. Wallpapers sometimes change to default. It's bug?

I have live wallpapers, YoWindow.

I guess, this is the bug of default AOSP launcher.
[Nexus 7 (2013) Android Development] SGH-i200:
By "Works on every device" do you mean every Android device or only Nexus 7 2013 devices?