yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] MegaDriveII:
Hello there.

Our Nexus 7, like many other old devices running unofficial ROMs using 3.4.x kernels, suffers from a really annoying bug that causes non-legacy versions of Firefox (i.e. Firefox Focus, Firefox Preview) to trigger a kernel panic and forced reboot when you open them while there's an active internet connection. It's extremely easy to reproduce. Just install Firefox Focus or Firefox Preview, try to open them, and there you have it!

There's already a fix for this, which has been already merged into affected kernels of several officially supported devices by LineageOS. This is my first comment here, so I'm not allowed to post links. However, the name of the commit is "ipv4: Pass struct flowi4 directly to rt_fill_info", and it's easy to find with a search engine.

This is a serious bug that's been known since almost a year (see Bug 5663 in mozilla-mobile/fenix on GitHub). Syncthing was another affected app, but its developers solved it by implementing a workaround (see Bug 1425 in syncthing/syncthing-android on GitHub). However, the Mozilla people doesn't seem to want to do the same with Firefox, because they argue that it's not a Firefox bug, but a kernel bug. So, at the moment, it's impossible to run a modern GeckoView-based version of Firefox on the Nexus 7, unless the fix mentioned above is merged into its kernel.

Would it be possible for the "ipv4: Pass struct flowi4 directly to rt_fill_info" commit to be merged into the kernel that this ROM uses?

Thank you!
[Nexus 7 (2013) Android Development] followmsi:
Pls test "my" kernel for OTG charging .. a lot of EX stuff has been used.

You can download from same folder on gdrive.

But no more time left for new deveoper options or other stuff.

If it's just a small patch like below .. but no more other stuff.

I like your first post ... not allowed to post links but all the related infos are included. :good:

Here you are .. will be part of next builds.

https://github.com/followmsi/androi...mmit/4bfbd25a7035e23beef97c64870083c9667c524e

Cheers
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.2 - June 2020

AEX Team did updae to version 7.2 .. https://blog.aospextended.com/AospExtended-v7.2-Changelog/

They did merge June security patches and many more changes too .. http://gerrit.aospextended.com/q/branch:10.x+is:merged

AospExtended-v7.2-flo-20200605-1318-UNOFFICIAL.zip

AospExtended-v7.2-deb-20200605-1606-UNOFFICIAL.zip

Changes:

- Google security updates -> June 2020 (android-10.0.0_r39)

- Kernel changes (ipv4: Pass struct flowi4 directly to rt_fill_info)

- Latest AospExtended changes for Android 10

Pls check first page for installation instruction !

The ROM installer will backup existing opengapps and magisk installation.

Enjoy Android 10 :p
[Nexus 7 (2013) Android Development] curiousde2002:
My Deb is presently on the latest build, AospExtended-v7.2-deb-20200605.

I found two bugs which were already there on v7.1:

screen recording and screen mirroring both are crashing and then the device reboots.

Anybody else having these issues?

Otherwise it's working very well!

Thanks to followmsi!
[Nexus 7 (2013) Android Development] DorianX:
[MENTION=5480152]followmsi[/MENTION] Is posible to update your ElementalX TEN version with latest kernel changes?

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Android Development] followmsi:
No idea about screen recording .. will need to check - not sure when time is left.

For next build I will include some frameworks/av patches to bring back "wifi display" support.

http://gerrit.aospextended.com/q/topic:"ten-aosp-wfd"
[Nexus 7 (2013) Android Development] followmsi:
It's actually just one single new change .. (ipv4: Pass struct flowi4 directly to rt_fill_info)

https://github.com/followmsi/flo_elementalx/commit/85f99f5a0f502fe059a0b4f14517d3524137be01

But yes - here is the same change for the EX kernel too ..

ElementalX-N7-7.02-TEN-20200609.zip (inside KERNEL subfolder)

Sources:

https://github.com/followmsi/flo_elementalx/tree/ElementalX-7.02-TEN

It seems newer Magisk versions do not like the kernel installer and you may loose root access.

To keep root access - just re-install Magisk.zip in TWRP - right after kernel installation.

Enjoy :p
[Nexus 7 (2013) Android Development] DorianX:
Excellent thank you so much!

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Nexus 7 (2013) Android Development] tsiftsism:
I would like your help.

My Nexus 7 is running an old AospExtended version (the one with October 2019's security patch) and I would like to know if by dirty flashing the latest rom.zip file, the ElementalX-N7-7.02-TEN-20200609.zip file, and no other file I'll be ok.

Ps1. I can't remember what gapps version I flashed back then, I guess it will be fine if I don't flash another one. When the tablet reboots it can run the already installed apps, is that right?

Ps2. If I have the .zip files in Nexus' internal memory and not inside a usb stick can they be flashed via TWRP?

Thanks in advanced for your answers.
[Nexus 7 (2013) Android Development] LisardoSc:
Gestures

Does this ROM have android 10 gestures?
[Nexus 7 (2013) Android Development] clarkgable:
Yes
[Nexus 7 (2013) Android Development] Purplezigar:
SafetyNet

Has anyone gotten SafetyNet to pass on the 20200605 build?
[Nexus 7 (2013) Android Development] ipdev:
I pass SafetyNet and have Play certification on both deb(LTE) and flo(WiFi).

Using Magisk (canary) and the aex 20200605 build(s).

Make sure MagiskHide is on and working.

Starting in Magisk 20.4, MagiskHide is off by default.

You may also have to toggle MagiskHide on (or off and on) after boot to make sure it is enabled.

A known bug that seems to affect some devices and setup. No true pattern found and what works on one device/setup may not work on a different one.

If you need to reset PlayStore Play Protect certification.

Once Magisk is settled and you pass SafetyNet, clear the cache and storage of the PlayStore app.

Once PlayStore updates if needed and re-scans the device and apps, it should show Device is certified

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] Purplezigar:
Yup, that did the trick! Weird behavior, but totally do-able. Thanks!
[Nexus 7 (2013) Android Development] rajsris:
Thanks for keeping this tablet alive 7 years later!

How do you enable scheduled sunset to sunrise darkui in this rom? Earlier, the feature used to be called night mode, but I can't find it in settings anymore. Night light is still present.
[Nexus 7 (2013) Android Development] clarkgable:
Thanks to the OP once again for a wonderful ROM, One question though- is it possible to amend the bootloader charging animation to show the percentage of the battery charged? It just shows a filling/filled up battery icon at present.
[Nexus 7 (2013) Android Development] followmsi:
Sorry .. no more time for this stuff.

No device related changes done by me .. maybe Team AEX made some changes here.
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.3 - July 2020

AEX Team did update to version 7.3 .. https://blog.aospextended.com/AospExtended-v7.3-Changelog/

I have patched frameworks/av to bring back Wifi-Display in Android 10 .. needs testing.

http://gerrit.aospextended.com/q/topic:"ten-aosp-wfd"

AospExtended-v7.3-flo-20200709-1729-UNOFFICIAL.zip

AospExtended-v7.3-deb-20200709-1955-UNOFFICIAL.zip

Changes:

- Google security updates -> July 2020 (android-10.0.0_r40)

- Increased media volume steps from 15 to 25

- Patched framework/av to bring back "wifi-display" in android 10.

- Patched framework/base to fix freeform window moving/resizing

- Latest AospExtended changes for Android 10

Pls check first page for installation instruction !

The ROM installer will backup existing opengapps and magisk installation.

Installed with new TWRP 3.4.0-0 .. https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html

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

Enjoy the summer :p
[Nexus 7 (2013) Android Development] followmsi:
EX-Kernel - fixed kernel installer due to TWRP 3.4.0-0 changes !

TWRP 3.4.0-0 was released some time ago .. https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html

A lot of nice changes .. also changes for SAR (system-as-root)

The new changes are breaking current lazyflasher kernel installer tool.

It's still the same kernel .. just using a modified installer to work on new TWRP 3.4.0-0.

ElementalX-N7-7.02-TEN-20200609-twrp340.zip (inside KERNEL subfolder)

Sources:

https://github.com/followmsi/flo_elementalx/tree/ElementalX-7.02-TEN

It seems newer Magisk versions do not like the kernel installer and you may loose root access.

To keep root access - just re-install Magisk.zip in TWRP - right after kernel installation.

Enjoy :p
[Nexus 7 (2013) Android Development] m00nlighter:
Guys,

If anyone uses headphones or other Bluetooth audio devices that support Sony's LDAC Bluetooth codec, please share your impressions (stability, sound quality, absence of issues when using LDAC, etc) on LDAC support in AEX 7.3 for flo/deb.

I'm currently using Unlegacy Android where LDAC is just working as it should—but I'd really like to switch to AEX because UA hasn't seen any updates for over a year.

Many thanks in advance!
[Nexus 7 (2013) Android Development] chrneu:
I just found my old 2013 flo device again which I flashed in the past. I wanted to flash this rom, thx to the ops for that! :)

Therefore I updated to trwp 3.4, flashed the sysrepart and then the android version. But I just get the error 7 "Updater process ended with ERROR: 7"; Error creating fstab.

Does anyone has a quick workaround for this?

Thanks for your help.

//Edit: After multiple recovery boots and wipes and reinstall of sysrepart it worked finally.
[Nexus 7 (2013) Android Development] Norghul:
Thanks a lot for this ROM, my nexus was buggy, laggy, and i m on the 20200511-0908 build, it s working perfectly, i ll have to update the new version soon :)
[Nexus 7 (2013) Android Development] andy_rose:
Yeah agree. This rom is very good. I dont use it all that much, but with my use, I have not encountered any bugs yet. Thank you!
[Nexus 7 (2013) Android Development] Ogawa:
Cleaning things out and found my nexus again. Shocked that you're keeping this alive, but am totally psyched. Installed easily and everything works great.

Many thanks!!!
[Nexus 7 (2013) Android Development] _ck_:
a curious question re: TWRP and your TEN kernel, would you have any idea why TWRP, even 3.4, can read the OTG USB stick storage but cannot write to it?

I try to backup directly to the OTG from TWRP but it fails the permission and I cannot find any special option to give write ability. Instead I have to boot to system and use MIX to move the local storage backup to the OTG stick manually where MIX knows to ask permissions. But it's slow and doubles work.

Thank you so much for keeping this tablet so amazing. Every day I use it I am in awe it's 7 years old and saved me money at a time right now where I have none to spare.

ps. have you ever listed somewhere the differences between TEN and ElementalX kernel?
[Nexus 7 (2013) Android Development] vkk178:
Can I dirty flash this over the previous version without updating TWRP ?

The usb port is completely dead and I'm making best use of this ancient device using wireless charging with No way to recover if it goes flash goes bad .

On the other hand is great that this device can wirelessly charge .
[Nexus 7 (2013) Android Development] ripee:
I have no idea what you're talking about lol.
[Nexus 7 (2013) Android Development] osm0sis:
Simple... LiveDisplay doesn't work in your Lineage 17.1 flo builds, but I could see in the sysfs that the fb0 rgb interface does exist (and the EX-N7 kernel also has a kcal interface) so the good news is it shouldn't be too hard to fix. :good:

Anyway, great work you guys have done getting these ROMs solid. :)
[Nexus 7 (2013) Android Development] followmsi:
Hi [MENTION=4544860]osm0sis[/MENTION]

Thanks for your post !

As well thanks for your repacked AK3 EX kernel !

I do not have the time for Android anymore. :(

For the moment I do make my monthly builds using current sources.

Some minor changes .. if at all.

Hope to find more time for all this Android stuff.

The SafetyNet issue seems also to be related to kernel version and not to selinux status only.

I have 2 devices in permissive mode (3.18 kernel) which are running fine with Magisk 20.4.

No need to restart Magisk hide .. SafetyNet pass just works fine.

But Nexus 7 (flo) and Nexus 10 (manta) both 3.4 kernels do have this problem .. started with Magisk 19.x version.

All 4 devices are in permissive mode .. 3.18 devices work and 3.4 devices do not work anymore.

For Google Pixel C I do use AnyKernel since years .. I will check out AK3 soon.

Thanks again for repacking !

I did upload to my kernel folder too .. https://drive.google.com/drive/folders/0By6p5AdQfavBN0pDMk92ZUdnTTg

DRM Info app is the next miracle :)

It stopped working on 4 of my devices .. since version 1.13 or 1.14 .. at the point they switched the app to kotlin code !

On my Xiaomi phone it's still working .. also latest version.

Did not find the root casue yet .. but i believe it's related to DRM HIDL service.

The 4 devices which do not work anymore are not using the DRM service .. just DRM HIDL impl (android.hardware.drm@1.0-impl) .. not sure if related. But It looks like.

Maybe DRM info app requires running DRM service.

I will test to switch to binderized DRM service .. instead of passthru DRM impl only.

But DRM works on all 4 devices .. on older DRM info app all looks good. .. L1 and L3 devices.

Netflix is running good too .. except on Nexus 7 (flo/deb) :)

Next miracle .. Netflix !

We all know the Netflix issues on flo/deb.

No idea about the root cause.

For last build I did merged some changes to bring back wifi display in Android 10. http://gerrit.aospextended.com/q/topic:"ten-aosp-wfd"

The changes are not working correctly on flo/deb ... device can "see" TV but not connect properly.

Anyway .. But after testing Wifi-Display I did disable "Wireless display" in Cast settings again and started Netflix app.

This time latest Netflix app from Playstore was able to stream all media.

No error messages after a few seconds/minutes .. streaming just did work fine .. for at least 10 minutes.

Today I quickly checked Netflix again .. did not start to stream any video .. again.

Now I did enable "wireless display" .. waited a few seconds and disabled again .. started Netflix app again and voila.

I was able to stream all content again.

No idea if this is working just for me .. or just on current Netflix app .. maybe next Playstore update will behave differently.

Too make long story short .. it seems wifi display changes do influence Netflix streaming behaviour.
[MENTION=7280276]ipdev[/MENTION] you may test the wireless display trick as well.

I hope to find some more time for Android again ..

Cheers
[Nexus 7 (2013) Android Development] casabel:
Great Rom! , my flo is resurrected, thank you devs
[Nexus 7 (2013) Android Development] ipdev:
I forgot to mention the this.

I primarily use DevCheck for device information, and it shows Clearkey and Widevine info.

xda thread - Link xdalabs - Link PlayStore - Link

Used it a lot awhile back looking for active sensor input. ;)

A secondary app (Recommended in Poco F1 threads to find screen manufacture.)

Device Info HW app shows DRM info under codecs.

PlayStore - Link

Netflix has been an adventure on Nexus 7(s). :eek:

This find could put us around the final turn and into the home stretch. :highfive:

Quick test with wireless display enabled, Netflix (7.62.0) streaming works correctly.

flo aex 20200412 Build

flo L17 20200710 (June security) vmalloc not preset. (vmalloc shows 245760 kb)

- The last time I synced and built flo.

No issues jumping around (scrub forward, scrub backwards, Quick jump 10 second (back or forward), restart an episode (correct time position in show) Picture-in-Picture, ...

If PiP is active (even paused) when screen is turned off, Netflix will not continue playing. If <See Edit>, and PiP is off (or PiP window is closed) then Netflix will resume playing. Not sure if that is intended but, I do not use PiP very often.

Quick test, so mainly observation and use.

I did not try casting to a device but, just enabling it and running Netflix, even after a reboot I was able to continue using Netflix without adjusting the wireless display. (Still enabled from before reboot.)

What setting(s) would enabling wireless display affect?

Would wireless display affect the screen draw, WiFi connection and/or the memory (buffer) ?

I will have some time this weekend to test more. Just curious if I should focus on looking for something besides general errors.

Cheers all. :cowboy:

Edit:

Had some lag issues with xda site.

To clarify, if Netflix is running or you switch to Home or a different app, then turn off the screen. Netflix will continue playing when you switch back to Netflix, unless the screen was turned off when PiP was active.
[Nexus 7 (2013) Android Development] osm0sis:
I can confirm the Kotlin rewrite seems responsible for the missing boxes on Android 10 Nexus 7, and have reported it to the app dev. :good:

Here's the last working version: https://www.apkmirror.com/apk/android-fung/drm-info-2/drm-info-2-1-1-3-200319-release/ :highfive:
[Nexus 7 (2013) Android Development] Alekos:
[Weird Bluetooth Issue only on Custom ROMs, including AospExtended]

Hope someone will see this, and can help...

So, if I flash a stock build, Bluetooth works perfectly. If I flash anything custom, it crashes. It's such a weird issue because it works Perfectly on a Stock Setup.

WiFi, GPS, everything else is working on custom ROMs. I've tried 6 different ROMs inclusing LineageOS v14-17, Havoc, Pixel, Resurrection and AospExtended. It doesn't matter which one is installed, if BT is enabled I get the constant error msg that BT has crashed. It doesn't matter if I clear cache/storage on BT, error message keeps appearing until it's disabled.

Does anyone have any insight into this issue or can point me to some sort of fix I can try?
[Nexus 7 (2013) Android Development] followmsi:
Thanks for contacting the app dev !

Cheers
[Nexus 7 (2013) Android Development] followmsi:
My assumption seems to be wrong !

If you can stream Netflix on older AEX builds it must be someting else.

At least it's not related to the "patched" framework/av sources.

AOSP Android 10 did remove WifiDisplay code from sources.

This changes will re-add sources to make it working like before Android 10.

For AEX:

http://gerrit.aospextended.com/q/topic:"ten-aosp-wfd"

For Lineage:

https://review.lineageos.org/q/topic:%22ten-aosp-wfd%22

You need to manually merge the changes/topic into framworks/av sources to include this code !

I did this for all my last Lineage-17.1 (dragon, gtaxlwifi ..etc.) and AEX builds (flo/deb).

On Samsung Tab A and on Pixel C it's working as it should .. I can mirror the Android screen to my Samsung TV.

For me it's not working on flo/deb.

Actually by mistake I did test Netflix app on flo too .. and it was working much better as all the time before.

Like you, I did not test to stream Netflix onto another device just streaming a movie and jumping around between different media.

This did not work properly all the time before .. the reason for using old 4.8.5 Netflix versions on flo/deb.

Maybe Netflix app has been "fixed" to run "normally" on Nexus 7 devices now. :)

In the last days I did receivce another Netflix app update thru palystore .. Netflix seems still to stream good on Nexus 7 2013.

As I prefer to watch Netflix on 10 inch devices I do not run/test Netflix very often on my flo.

I am not sure what happens if you enable WifiDisplay without the code modifications described above.

Are you able to stream Netfllix with disabled WifiDisplay settings too ? .. on older builds too ?

Sorry, no more time for deeper analysis.

Cheers
[Nexus 7 (2013) Android Development] ipdev:
Actually I'm a bit more confused now and still trying to figure it out. ;)

Casting..

Amazon fire tv stick set in casting mode.

With wireless display enabled, the older builds on flo (both), would show my fire stick under casting.

If I tried to connect, the fire stick would show connecting.. The tablet would reboot and cause the fire stick to drop out of casting mode.

I updated my deb to the aex 20200709 build.

It would not reboot, instead the connection would try and fail.

This did not always cause the fire tv stick to drop out of casting mode.

Netflix, it seems offers an internal casting of sorts. ?

With or without wireless display enabled

On the older builds (flo) using the cast button inside of Netflix, it picked up my older fire TV (in stand-by mode) but not my fire stick?

I switched over to my fire TV and tried the native Android casting again.

Similar story but, not as consistent.

Sometimes the fire TV stayed in cast mode, the tablets did not always reboot..

If I selected fire TV using the cast option in Netflix, it opened the Netflix app on fire TV (I'm not logged in to Netflix on my fire TV at the moment).

I was wrong earlier when I thought casting was working (at least partially) on flo/deb. :(

Seems Netflix uses it's own version, not sure how much relies on the native casting?

Now that I think of it, the tablet was basically just a remote.

As for Netflix streaming on flo/deb...

As you noted, enabling/disabling the wireless display under casting seems to affect it for some reason.

My main flo (older aex with wireless display enabled) would not load Netflix after it sat idle for awhile. (12-15 hours??) By just turning off the wireless display option, Netflix seems to be just fine. Even tonight after 24 hours and a few reboots, it still works??

Logged into PlayStore Netflix 7.67.2

My testing flo (older Lineage with wireless display enabled), Netflix was working fine after 12-15 hours. Tonight (24 hours later) Netflix gave me a connection error and I simply turned off wireless display under casting settings, and Netflix is working fine.

Not logged into PlayStore, Netflix 7.62.0 from a backup, installed with SAI

Split APKs Installer [github] - Link

I actually haven't tried Netflix on my Deb yet.

Will have to take a look at what I have in my backups..

I re-synced and build l17 (flo) the other day but, did not flash it.

I'll take a look to see if the commit was included if not, I'll try to add it and see what happens..

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] pjmarkert:
Here's how to get the battery percentage to display on stock Android:

Enable System UI Tuner. To do this, swipe down the Quick Settings panel and you'll see the settings gear icon at the top of the display. Press and hold this for a few seconds.

After a few seconds, the System UI Tuner will be enabled and will appear at the bottom of the settings menu. Once it's enabled, a spanner icon appears next to your settings shortcut icon and you'll get an onscreen notification.

Open the System UI Tuner menu and tap "status bar". Towards the bottom you'll see the option called "battery" with a number of choice. Select "always show percentage".
[Nexus 7 (2013) Android Development] M4Master96:
Deleted
[Nexus 7 (2013) Android Development] tnowakow:
Hey guys, found my old Nexus tablet and I was able to install this and I did the syspart zip, but gapps is still giving error 70? Any ideas? Trying to install arm 10.0 nano, thank you
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v7.x - Android 10

The AEX Team did not merge August security patches until now.

Some days ago they have "abandoned" several other changes too.

As it looks like they do not implement any changes for Android 10 anymore.

For this reason the July builds are my last AospExtended-v7.x ROM for flo/deb devices.

My time for Android is very limited .. not sure if I will find the time to work on upcoming Android 11.

Thanks for understanding !

Cheers :p