yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] followmsi:
Yes .. since last release (classic_06_v3).

https://github.com/followmsi/android_device_asus_flo/commit/79fcc0d85ebf2b2d2ab8b9461964096729e22b2b

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

If you want to test new Xtra server and other gps stuff you may test on classic_06_v2.

In case the overlay is "disturbing" your tests.

Cheers
[Nexus 7 (2013) Android Development] abhifx:
wew... first lock took 20 min. but after that its locking in 3 second. will test again in evening while driving. if everything goes well then this is the go to rom.

Edit: as i have already pointed in lineage thread, the overlay seems to also have ntp server address which defaults to north america. i doubt that this is causing delay in locking GPS locking for Asian continents. can you please check?
[Nexus 7 (2013) Android Development] followmsi:
I did test different NTP server (Europe) with no better results.

You may do your own tests in Asia.

Hope you find the best config for your setup.
[Nexus 7 (2013) Android Development] abhifx:
I have dug more and tested latest Unlegacy Build and GPS is certainly locking in seconds.

in their overlay config, this is what is related to GPS configs

<!-- Values for GPS configuration -->
<string-array translatable="false" name="config_gpsParameters">
<item>XTRA_SERVER_1=https://xtrapath1.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_2=https://xtrapath2.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_3=https://xtrapath3.izatcloud.net/xtra3grc.bin</item>
</string-array>

this is what is reflecting in Lineage and Classic

<!-- Values for GPS configuration -->
<string-array translatable="false" name="config_gpsParameters">
<item>SUPL_HOST=supl.google.com</item>
<item>SUPL_PORT=7275</item>
<item>XTRA_SERVER_1=https://xtrapath1.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_2=https://xtrapath2.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_3=https://xtrapath3.izatcloud.net/xtra3grc.bin</item>
<item>NTP_SERVER=north-america.pool.ntp.org</item>
<item>SUPL_MODE=1</item>
<item>SUPL_VER=0x20000</item>
<item>LPP_PROFILE=0</item>
<item>NMEA_PROVIDER=0</item>
<item>A_GLONASS_POS_PROTOCOL_SELECT=0</item>
<item>ERR_ESTIMATE=0</item>
<item>INTERMEDIATE_POS=0</item>
<item>SUPL_ES=0</item>
</string-array>

So my point was if these extra GPS parameters are casing long time in locking GPS as north america NTP pool is used? good thing is, once locked i get tons of satellites and stable connection. in Unlegacy i get instant lock but it fails frequently.

I am out of ideas. I do suggest at least the server in overlay config should be pool.ntp.org to make it country agnostic i really like classic as it has all the right functionality (elemental, addon.d etc). But GPS in India is killing me.

is there a short cut? i cant edit overlay without compiling.

Edit: here is what was merged in mako

https://review.lineageos.org/#/c/Li...rameworks/base/core/res/res/values/config.xml
[Nexus 7 (2013) Android Development] followmsi:
Yes , you will need to compile to change the overlay.

For this reason I have made 2 new packages .. you will need to replace the files manually in /system and reboot afterwards.

framework-res.apk_XTRA-only.zip

diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index 90ab501..0d41f58 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -270,20 +270,9 @@

<!-- Values for GPS configuration -->
<string-array translatable="false" name="config_gpsParameters">
- <item>SUPL_HOST=supl.google.com</item>
- <item>SUPL_PORT=7275</item>
<item>XTRA_SERVER_1=https://xtrapath1.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_2=https://xtrapath2.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_3=https://xtrapath3.izatcloud.net/xtra3grc.bin</item>
- <item>NTP_SERVER=north-america.pool.ntp.org</item>
- <item>SUPL_MODE=1</item>
- <item>SUPL_VER=0x20000</item>
- <item>LPP_PROFILE=0</item>
- <item>NMEA_PROVIDER=0</item>
- <item>A_GLONASS_POS_PROTOCOL_SELECT=0</item>
- <item>ERR_ESTIMATE=0</item>
- <item>INTERMEDIATE_POS=0</item>
- <item>SUPL_ES=0</item>
</string-array>

</resources>

framework-res.apk_ntp.pool.org.zip

diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index 90ab501..2a85d31 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -275,7 +275,7 @@
<item>XTRA_SERVER_1=https://xtrapath1.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_2=https://xtrapath2.izatcloud.net/xtra3grc.bin</item>
<item>XTRA_SERVER_3=https://xtrapath3.izatcloud.net/xtra3grc.bin</item>
- <item>NTP_SERVER=north-america.pool.ntp.org</item>
+ <item>NTP_SERVER=pool.ntp.org</item>
<item>SUPL_MODE=1</item>
<item>SUPL_VER=0x20000</item>
<item>LPP_PROFILE=0</item>

The NTP server topic has been discussed already in this thread.

Not sure if the change will improve gps lock time .. I doubt.

I will not have time for more testing !

Maybe we can switch to general "pool.ntp.org" in August release.

Happy testing ! :p
[Nexus 7 (2013) Android Development] abhifx:
Holy Crap! You are a life saver. will definitely test and revert. I just have 2 days to test before i go for my holiday.

Thanks a lot!
[Nexus 7 (2013) Android Development] abhifx:
copying files manually or through TWRP turned out to be difficult, so i have made the flashable zip. so far i have tried NTP server change only and that seems to work. but will check more when i drive to my office.

Next stop would be checking xtra server only when i return.

Please people check and revert as i will be away for next week.
[Nexus 7 (2013) Android Development] abhifx:
and here is XTRA only flashable zip.

also note that i have no idea if this is working or not :D
[Nexus 7 (2013) Android Development] jumperalex:
Just wanted to pop in to say thanks and confirm that Netflix 4.8.5 still works ... well for ME it works "now" but I'm updating from a few versions ago when it was much more hit/miss and for me it had been a miss. Now all is good just in time for the beach.
[Nexus 7 (2013) Android Development] Ch3vr0n:
I'd love to know how I can get Netflix working (latest version if possible naturally)

Sent from my Nexus 7 with Tapatalk
[Nexus 7 (2013) Android Development] ranaxda200:
Anyone here confirm that if USB OTG working fine or not. For me only upon restarting the device, it detects otherwise not.
[Nexus 7 (2013) Android Development] followmsi:
Me too ;)
[Nexus 7 (2013) Android Development] ReichMann:
Does anyone face lagging in YouTube? I am using June Version with YouTube vanced.
[Nexus 7 (2013) Android Development] Ch3vr0n:
You probably refer to the newest version. I don't even know how to get an old version working. So if you or anyone can inform me, I'd love to know. Or even better a TWRP flashable zip that does that.

Sent from my Nexus 6P with Tapatalk
[Nexus 7 (2013) Android Development] followmsi:
Delete your current Netflix installation.

Install this apk ..

https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-4-8-5-build-9781-release/

Logon again and start streaming .. no download function in this "old" version.

Good luck !
[Nexus 7 (2013) Android Development] Ch3vr0n:
Can't delete what isn't installed in the first place :P I'll give it a try. Don't need the download function. For that I have my phone and my 'nebula capsule' :)

Sent from my Nexus 6P with Tapatalk
[Nexus 7 (2013) Android Development] nicky-xda:
Dirty update from LOS 14.1?

I have now installed: lineage-14.1-20171226-nightly-flo-signed.zip

Is there a way to dirty update to this AOSP ROM without wiping "DATA"?

When i try that it gets stuck at booting and the user interface never appears.
[Nexus 7 (2013) Android Development] abhifx:
Nope. This is a complete version upgrade from Nougat to Oreo. Clean install is recommended.
[Nexus 7 (2013) Android Development] followmsi:
If you still try to dirty upgrade you need to remove lineage signing first.

Upgrade from unofficial version instead as from official.

But like mentioned above. .. Clean install is recommended.
[Nexus 7 (2013) Android Development] nicky-xda:
Thanks for your valuable hint! :)

Yes, i know, that clean instal" always recommended, but i still prefer to at least try the dirty way. Unfortunately i cannot find a download of the "unofficial LOS 14.1".

Any idea where to find a working link?
[Nexus 7 (2013) Android Development] followmsi:
Not really required to install unofficial but preparing the data partition for it.

https://wiki.lineageos.org/signing_builds.html

Boot into twrp and do all steps via adb.

Once data is ready for unofficial start to install aosp oreo version.

Wipe system and do fresh install of gapps.

Wipe cache and dalvik before reboot into system.

Still no guaranty that it will work as it should ..

Good luck !
[Nexus 7 (2013) Android Development] dealpapa1:
oh yeah. we want android 9.0 lol
[Nexus 7 (2013) Android Development] b4ckfir3:
I doubt that a nexus 7 would even be to run it ?
[Nexus 7 (2013) Android Development] dealpapa1:
it will do not worried.

:D
[Nexus 7 (2013) Android Development] Aerys:
Very curious how Android Pie will run on our beloved Nexus 7! :victory:
[Nexus 7 (2013) Android Development] Semtronix:
Just install Magisk, no? That's all I do and it works fine. Comes up as certified device in the Play Store settings.
[Nexus 7 (2013) Android Development] slaman:
Thanks for this ROM.

I am not seeing the Blue Light Filter in this ROM - am I missing something?
[Nexus 7 (2013) Android Development] rajsris:
It unfortunately isn't included in AOSP. I've been using an app called f.lux to achieve the same effect. Requires root.

https://play.google.com/store/apps/details?id=com.justgetflux.flux
[Nexus 7 (2013) Android Development] followmsi:
Have activated this in latest version .. pls test in version V4
[Nexus 7 (2013) Android Development] followmsi:
It seems to be possible ...

https://github.com/followmsi/platfo...mmit/2e6a43841dd2bbecaaca6476ee159a770a4ab358

Enjoy V4 with activated Night Mode in Display settings :)
[Nexus 7 (2013) Android Development] followmsi:
AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v4.zip

AOSP_7.1.1_r28_N6F26U_deb-ota-eng.followmsi-v4.zip

Changes:

Enabled Night Mode in Display settings

For reference:

https://github.com/followmsi/platfo...mmit/2e6a43841dd2bbecaaca6476ee159a770a4ab358

Enjoy :)
[Nexus 7 (2013) Android Development] slaman:
You rock!!! Thanks!
[Nexus 7 (2013) Android Development] slaman:
Just did a dirty Flash and an having problems with most Google apps (music, YouTube, photos)

They just won't open - get a message that the app stopped working when I try to launch. I reflashed and then flashed open gapps again, but that didn't fix.

Do i have to clean Flash?

I'm really trying to avoid that...
[Nexus 7 (2013) Android Development] drewski_1:
hate to say, but probably should clean flash.

what was your starting point? prior build of this ROM? different custom ROM? 6.0.* ROM?
[Nexus 7 (2013) Android Development] nigelhealy:
Ditto.

I was this ROM, then saw v4.

I just dirty flashed the ROM, rebooted and lost Play Store, also lost root. That mean I lost the ability to boot into recovery via root apps. So that implied I needed to flash gapps again and flash supersu again after dirty flashing the ROM. So I downloaded and booted back into TWRP using the power off on volume buttons and then TWRP could not see /sdcard to see my gapps supersu zips, it could not mount /data and when I booted it asked for a password, that implies TWRP corrupted data.

Most other ROMs protect gapps during reboot can this be included?

I was on the last most recent TWRP, I'm going to to fastboot flash latest TWRP and hope to not need to do a clean install.
[Nexus 7 (2013) Android Development] followmsi:
I did dirty install too .. no problems.

But I do always install new gapps and as we replace the boot.img completely you need to root again.
[Nexus 7 (2013) Android Development] followmsi:
Did you install supersu afterwards ?

If you install a full ROM the boot.Img will be overwritten, completely.

Unlike if you install custom kernels via anykernel or lazyflasher, where it just replace the binary and does not change the ramdisk.

After each ROM installation you need to run supersu.zip again.

Will have a look the add-on stuff .. to keep gapps persistent.

To prevent issues, I always install new gapps if I flash a new ROM.
[Nexus 7 (2013) Android Development] followmsi:
In general .. If something goes wrong with dirty installation I always try to restore my last backup and most of the times it works .. on all devices.

Which kernel did you use before you flashed the new ROM ?

ElementalX kernel or another kernel ?
[Nexus 7 (2013) Android Development] nigelhealy:
Confirmed, your TWRP or ROM corrupted /data , cannot mount /data, how did you manage to do that? In "wipe" advanced, I see /data has become 0 zero size.

Also if I attempt to do a clean install it cannot mount /data, cannot wipe /data when f2fs, I tried a few things and I had to change filesystem back to ext4 then back to f2fs to allow it to wipe. So your TWRP is not recognizing f2fs properly, only after I change the filesystem. Might explain why it cannot mount /data on reboot into TWRP?

In my case I was on your last prior versoin of ROM and no flashing of kernel, so only your stuff in your sequence.

---------- Post added at 08:01 AM ---------- Previous post was at 07:52 AM ----------

(sigh, forced to do a clean install after full wipe)

Do I flash the supersu before or after the anykernel version of ElementalX?

Is your anykernel ElementalX contained in the most current ROM? (so I need only flash supersu) ?
[Nexus 7 (2013) Android Development] followmsi:
Had problems with the glitch kernel these days .. also problems with /cache & /data partitions.

The new version from yesterday is working fine now, at least for me.

Don't know why your data got corrupted now ..TWRP is able to format and to mount F2FS.

Will do a fresh install of the latest ROM again .. try to replicate the issues.
[Nexus 7 (2013) Android Development] nigelhealy:
The advice in OP manually unmount /system after /system wipe, does not work. Install of the ROM fails. Have to reboot back into recovery after wipe of /system to then install ROM.

Your TWRP cannot reboot into recovery, I have to poweroff then use buttons to get into recovery.
[Nexus 7 (2013) Android Development] followmsi:
It's the same kernel just different install method.

The ROM is installing a full boot.img where you always need to re-run supersu.

The anykernel or lazyflasher packages are supposed for kernel changing after rooting has been done.
[Nexus 7 (2013) Android Development] followmsi:
Which version of TWRP are you using 3.1.0-4 ?

Sorry .. not able to reproduce your issues with TWRP.

Reboot to recovery works for me.

System mount / unmount works.

Will check the latest ROM again ..
[Nexus 7 (2013) Android Development] followmsi:
Do you have a current backup of data ?

Restore it and you should be fine ..

Need to replicate your issue.
[Nexus 7 (2013) Android Development] nigelhealy:
I got all mucked up overnight so I went to your crrent ROM 3.1.0-4 and did a full wipe of all partitions. Unmounting of /system does not successfully cause ROM to install. With all partitions empty and TWRP reboot into recovery, it sticks at Google logo.
[Nexus 7 (2013) Android Development] followmsi:
Just did boot into TWRP 3.1.0-4

1. Wipe/Format system partition (ext4)

2. Did mount / unomount in TWRP mount menu -- a few times - no issues at all - Kept it unmounted !

3. Installed latest v4 ROM .. no issues at all - no warning - no errors.

4. Installed gapps from today - they are back to old size approx. 130 MB for pico and not 70MB like for the last 2 weeks.

(Tested small and big versions - seems not to be realted - both are working fine for me.)

Anyway - no issues here .. no warning ... all ok.

5. Did install SuperSu 2.79.zip - no warning .. no issues .. ramdisk has been modified .. all ok.

6. Did wipe cache (f2fs) and dalvik after SuperSU installation.

7. Reboot into system

8. All is back to normal .. like before.

It's important to use 3.1.0-4 .. as several custom installer problems have had issues with "lineageos" version of busybox.

Busybox is the "shell" for TWRP .. if busybox is not working correct you get strange issues.

In latest version I have changed to omnirom busybox - all the "custom" scripts I have tested are working fine now.

I wish I could replicate your issues :)
[Nexus 7 (2013) Android Development] Ch3vr0n:
Not until SuperSu stops working on the ROM entirely. But I'll keep that in mind.

Sent from my Nexus 6P with Tapatalk
[Nexus 7 (2013) Android Development] jerethi:
Our Nexus 7 is the little engine that could. I have confidence she'll run Pie like a champ!
[Nexus 7 (2013) Android Development] followmsi:
August 2018 ..

flo-Classic_08-2018_AOSP_8.1.0_r42_OPM4.171019.021.Y1_followmsi.zip

deb-Classic_08-2018_AOSP_8.1.0_r42_OPM4.171019.021.Y1_followmsi.zip

Changes:

- Google security updates -> August 2018 (android-8.1.0_r42)

- Adjust DRM blobs

- Added some Bluetooth codecs

Sources:

https://github.com/followmsi/manifests/tree/flo-deb-aosp-o

https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2018-06-26

Android O and P

Of course, I will have a look into Android P for the flo/deb devices !

Pls don't expect any P ROMs in the next time .. it will take a bit longer.

As I understood Google they will "tag" the monthly Oreo updates until October/November.

At this point the Classic Oreo releases will stop.

Hopefully we are able to continue on Android P .. even before October/November.

Enjoy :p
[Nexus 7 (2013) Android Development] Ch3vr0n:
Not seeing August build, only July

Sent from my Nexus 7 with Tapatalk
[Nexus 7 (2013) Android Development] lollyjay:
It's there
[Nexus 7 (2013) Android Development] Ch3vr0n:
I know. Grabbed it via another way. For some reason it (tablet Google drive app) would only show previous build

Sent from my Nexus 7 with Tapatalk
[Nexus 7 (2013) Android Development] tombraga:
Already installed the August build, all top, New TWRP included. Thanks a lot, you do a great job.
[Nexus 7 (2013) Android Development] abhifx:
Great Changes, will try the bluetooth codecs.

good to know someone is working on Android P for such old device. Nexus will remain updated for at least more year then :D
[Nexus 7 (2013) Android Development] abhifx:
[MENTION=5480152]followmsi[/MENTION]

cant select any codecs other than SBC nor can i change the bitrate. any editing i need to do to get extra codecs?
[Nexus 7 (2013) Android Development] followmsi:
To change via developer settings is not working .. like on other devices too.

But if you connect to BT device which supports aptX system will recognize and show in paired devices settings.

You can de/select the aptx codec as well.

For me it just works fine ..
[Nexus 7 (2013) Android Development] beachfl:
Installed just fine on my flo, latest TWRP, and rooted with Magisk. :)

(An attempt to dirty flash from parallel Lineage resulted in a bootloop with 'com.android.phone' repeated errors On Load... so Factory Reset and all fine.)

Sensor Test and GPS Test report everything working, and I haven't noticed any issues at all so far.

Thank you!
[Nexus 7 (2013) Android Development] crossxn:
Can you please guide me to latest twrp?
[Nexus 7 (2013) Android Development] beachfl:
I found it from Google. I don't have the link to hand.

Edit: here.. I looked it up for you:

flo or deb
[Nexus 7 (2013) Android Development] gege622:
I Thank you beachfl, i'll keep these URL in mind.

And Thanks again Followmsi, it always works like a charm.

For the GPS: I desactivated my wifi, activated the location functunality (!), launch Google Maps and it was OK. :good:
[Nexus 7 (2013) Android Development] dagnygren:
No camera

Have no camera on this device. Is it working for others?

I am referring to r42 and this is a flo.
[Nexus 7 (2013) Android Development] DCvan:
You can install cameringo or silent camera on playstore.
[Nexus 7 (2013) Android Development] gege622:
Personally, i use the Silent camera app:

https://play.google.com/store/apps/details?id=com.peace.SilentCamera

There're Ads but it works great
[Nexus 7 (2013) Android Development] dagnygren:
Thanks but....

Thanks! Installed that and that verifies that the hardware works. But can somebody explain to me why the builtin AOSP camera app says: "Cannot connect to camera" ? Did I install the wrong gapps? Using Silent Camera and switching a couple of times between back and front camera + setting autofocus to macro and back also froze the tablet and rebooted it?
[Nexus 7 (2013) Android Development] beachfl:
It's a known issue with the Oreo builds for this device. It's nothing you did.
[Nexus 7 (2013) Android Development] lollyjay:
Cameringo from Play Store is working for me
[Nexus 7 (2013) Android Development] vannrith:
Thank you, working fine so far, and I use adb to remove unwanted app like keyboard and default camera app.

I install Open Camera, it's working fine. For the performance, it's much better than stock Android M factory image
[Nexus 7 (2013) Android Development] phaze3131:
Cool rom thank you for the work!

Any idea why I am not getting a sound notification when I first plug in my device?

I have checked the sound settings (charger is ticked) and made sure all my sound levels are set to normal.

Thanks for the help :)
[Nexus 7 (2013) Android Development] followmsi:
Will have a look in the next time ..

Next flo sessions are planed for P.
[Nexus 7 (2013) Android Development] abhifx:
Cool!

i guess nexus 7 is one of the rare device where partition can be modified. is there a remote possibility of trebalising the system with old blobs?
[Nexus 7 (2013) Android Development] followmsi:
P does not require full treble devices .. we can continue without extra vendor partition.

We use /system/vendor. it's mounted as /vendor .. already today in Oreo and before.

Yes, we need to move a few more libs from system to vendor.

Lineage did big part of the work for Oreo already.

(Free) space situation on system partition is another issue ..

Cheers
[Nexus 7 (2013) Android Development] MikiGry:
I know, that we probably can get P to boot without treble support. But I think (I don't know how much he work needs to be done) enabling full treble support and booting p as a GSI should make a lot of staff easier in the future
[Nexus 7 (2013) Android Development] followmsi:
Good point .. there are several devices using cache or other partitions as vendor replacement.

Let's check the possibilities ..
[Nexus 7 (2013) Android Development] MikiGry:
[MENTION=5480152]followmsi[/MENTION]

Redmi Note 4 received unofficial treble support via using some unused partition

While Asus Zenfone 4 received "treble" support via puting everything needed in /system

https://www.xda-developers.com/asus-zenfone-4-android-oreo-project-treble/
[Nexus 7 (2013) Android Development] abhifx:
yes repartition would also solve shortage of system partition. i guess pie is even bigger.

or we could just install gapps through magisk :p
[Nexus 7 (2013) Android Development] dealpapa1:
twrp-3.2.3-1 is out?
[Nexus 7 (2013) Android Development] Ch3vr0n:
Why don't u ask that in the TWRP thread?

Sent from my Nexus 6P with Tapatalk
[Nexus 7 (2013) Android Development] gege622:
You could also check those Urls:

https://dl.twrp.me/flo/ and

https://dl.twrp.me/deb/
[Nexus 7 (2013) Android Development] Ch3vr0n:
Why you quoting me? I'm not the one posting/asking about a new TWRP version

Sent from my Nexus 6P with Tapatalk