yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] followmsi:
It's time for AospExtended .. February 2019

AospExtended-v6.2-flo-20190208-1407-UNOFFICIAL.zip

AospExtended-v6.2-deb-20190208-1518-UNOFFICIAL.zip

Changes:

- Google security updates -> February 2019

- Reverted some Wifi changes to fix Deep Sleep.

- Fix for Bluetooth (deb device only)

- Added Telephony stuff (deb device only)

Tested flo version with Magisk 18.1 !

Enjoy :p
[Nexus 7 (2013) Android Development] vagelis74:
I am using PE pie 2 days ago and I love the stand by, it's gorgeous.
[Nexus 7 (2013) Android Development] greenleaves:
Just wanted to report that I flashed AospExtended-v6.2-flo-20190208-1407-UNOFFICIAL.zip with succees and it booted up well. However Magisk 18.1 didn't work. I flashed it via TWRP with no success and can't get it rooted.

Appreciate your help and thanks for all the efforts. Greatly apprecited
[Nexus 7 (2013) Android Development] iaTa:
That's weird because I'm getting 5% per hour idle drain on latest PE clean flash.
[Nexus 7 (2013) Android Development] Booroner:
Testing February AEX.

Great job, thanks!
[Nexus 7 (2013) Android Development] elpeh:
Another question: with "telephony stuff" integrated, I now have APNs available automatically for mobile data. Also the SMS/MMS app. Haven't tested receiving SMS, but sending SMS is not working (error 21). Maybe SMSC is not set? Any way to do this/debug further (without root...)? Phone calls are not supposed to work, are they (there is no Dialer app)?

Thanks

---------- Post added at 09:14 PM ---------- Previous post was at 09:09 PM ----------

I can confirm that Bluetooth is working on deb now (only tested with keyboard for now).
[Nexus 7 (2013) Android Development] taw62:
Magisk 18.1 is running without problems on my flo with latest AEX. Did you install Magisk Manager v7 as well?
[Nexus 7 (2013) Android Development] greenleaves:
You nailed it. Now it's working. Many thanks ... :good:
[Nexus 7 (2013) Android Development] prsa01:
Dirty flash from previous AEX to 2/9 AEX. No issues.

Pico gapps & 18.1 Magisk remained from earlier installation. Had earlier expanded system partition to 1280.

All working well, only a few hours so far.

Thanks op!
[Nexus 7 (2013) Android Development] lollyjay:
Same here ?
[Nexus 7 (2013) Android Development] followmsi:
Some more updates ..

The last Bug fix release for RR:

RR-P-v7.0.0-20190209-flo-Unofficial.zip

RR-P-v7.0.0-20190209-deb-Unofficial.zip

Changes:

RR-P-v7.0.0-20190209

- Bug fix release: RR-Team did fix Power/Reboot menu

Tested on flo with Magisk 18.1 !

Except for AEX - all other ROM have been moved to androidfilehost.com ..

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

If you want to switch (dirty) between different ROM you may get strange errors.

Pls do no post your problems here unless you did factory reset first - Thanks !

"Project Android Pie for flo/deb" is closed for me now :)

Of course, we still can improve AEX in the next months.

I still hope there are more "devs" who are willing to start building custom ROM for flo/deb.

Cu next month .. with the next monthly AEX update !

Enjoy your weekend !
[Nexus 7 (2013) Android Development] makjim:
Have installed the AEX on deb with Magisk 18.1 without any problem. Bluetooth working OK too.

Some issue with the MX Player, have grey bars on top and bottom for all the UI Style except the "Black UI".

Thank you very much for your works.
[Nexus 7 (2013) Android Development] jhford:
Magisk

I'm running the latest AEX on my 2 debs. Magisk 17.3 and 18.1 install properly, but the devices remain unrooted. Any suggestions?

Thanks
[Nexus 7 (2013) Android Development] Stanzilla:
Are the Oreo packages officially dead now?
[Nexus 7 (2013) Android Development] prsa01:
AEX - I occasionally lose wifi on waking back from what I assume is deep sleep.

Symptom; browser hangs. Sometimes eventually starts responding and then works normally. Other times I cycle wifi off/on and all works.

Not a big deal, just putting it out there and curious if anyone else is seeing the same
[Nexus 7 (2013) Android Development] abhifx:
wew! lets test the battery life. if everything is good then this will be my daily driver.

Thanks!
[Nexus 7 (2013) Android Development] AlesUlrych:
Hi,

Where did "Lineage-16-20190208-UNOFFICIAL-flo.zip" disappear? It is no longer downloadable on the disk. Any reason for removal?

Thanks for the info.

Ales
[Nexus 7 (2013) Android Development] SGH-i200:
The non-AEX ROMs have moved:

Direct link to flo ROMs: https://androidfilehost.com/?w=files&flid=289296
[Nexus 7 (2013) Android Development] followmsi:
Yes !
[Nexus 7 (2013) Android Development] simonbult:
Hi guys. I have installed the latest Flo AEX version from stock and now I'm stuck in the configuration process at the system updates check. The WiFi connection is good so I don't know why it is stuck. I use the OpenGapps Pico version. Can you please give me a response? Thanks

Update:

Now I've switched to mindthegapps package, but the situation is always the same
[Nexus 7 (2013) Android Development] rajsris:
AEX requires gapps, correct? Which package are folks using?
[Nexus 7 (2013) Android Development] nomesrjp:
I use ARM/9/Pico
[Nexus 7 (2013) Android Development] elpeh:
Haven't tested systematically yet, but have the impression that with this version on my deb device and mobile data (LTE) enabled, I have noticeable battery drain. In contrast to previous built,. where the "telephony stuff" had not been integrated.
[Nexus 7 (2013) Android Development] Booroner:
All right here except google chrome that closes from time to time, especially when opening links telegram, twiter .....

I use opengapps pico (arm 9)
[Nexus 7 (2013) Android Development] alizain2308:
I am using the Oreo build which is giving me superb battery life(good for me since I have to charge my tab wirelessly as its usb port just died). Hopefully pie does the same too! :)
[Nexus 7 (2013) Android Development] rajsris:
So what's the latest with getting the latest versions of Netflix to work? Are we still going to have to use version 4.8.5?
[Nexus 7 (2013) Android Development] elpeh:
Ok, seems to be at least no general problem. Not reproducible. After a restart 6 hours with Wifi and LTE enabled (Wifi in use) and 5 hours with Wifi disabled (LTE in use). Most of the time in standby. 94% deep sleep, seems fine.
[Nexus 7 (2013) Android Development] andrei15:
Hi guys

Is there any overheating in this rom when viewing the youtube (720p60, 1080) as in aicp 8?
[Nexus 7 (2013) Android Development] sir_bazz:
Fark me!

Only just found these little nuggets of gold hidden in here. They really deserve their own thread for greater visibility.

Installed on flo earlier today and its brilliant. Absolutely gobsmacked at what you've done here for our old Nexus devices. Many thanks!

Also have a deb which is now crying out for some Pie lovin'.
[Nexus 7 (2013) Android Development] Booroner:
At the moment no, everything is fine except chorme when opening links, which closes, otherwise everything ok.
[Nexus 7 (2013) Android Development] JT1510365:
i dont have any issues with chrome so you must of done something wrong
[Nexus 7 (2013) Android Development] Ch3vr0n:
I'm currently using the last 8.1.0 build for my N7 3g version (razorg). Sysrepart went fine. Can I just flash this Extended build over the top? If yes, should I wipe data/cache? What Android version is it based on?

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Nexus 7 (2013) Android Development] Booroner:
You can open links on Twitter, Telegram .... without problems ??? To me it gives me failure and I have to do it 3 or 4 times.

If I sail or open chorme directly I have no problems.
[Nexus 7 (2013) Android Development] JT1510365:
Yes I can open links without chrome failing every single time:) In fact I have been using chrome all the time and not had one single crash:)

Did you do a clean flash?
[Nexus 7 (2013) Android Development] Booroner:
I think I remember that, given that with a dirty flash I had problems with the google service and I did it clean. At the moment I'll leave it like that and in the next compilation I'll go back to flashing in clean, although I think I remember that another compi was going something similar with chorme.

Thank you very much for the help.
[Nexus 7 (2013) Android Development] jhford:
AEX restarts

I'm running the latest AEX on my 2 debs. Chrome and Chrome Beta intermittently cause the ROM to restart. I need more stability. What should I do?

Thanks
[Nexus 7 (2013) Android Development] sir_bazz:
[MENTION=5480152]followmsi[/MENTION]

After all the excitement over PE on flo yesterday, I got straight into putting it on deb today.

Noticed that on deb, default swapiness is set to 0 in the kernel. Is this by design? My understanding is that a value of 0 is the equivalent of disabled.

My flo device has the expected default of 60 which I've manually set to 20.
[Nexus 7 (2013) Android Development] Booroner:
Make a clean flash and try, it's great for me, the only drawback is to open external links in Chorme but it can be my thing since more compis works well.
[Nexus 7 (2013) Android Development] followmsi:
Pls do clean install .. factory reset via TWRP (to keep internal storage)
[Nexus 7 (2013) Android Development] followmsi:
Well spotted :)

I do not own any deb device myself .. spent some time to make it ready for Android Pie.

If you find differences to flo setup - pls let me know.

Like you did now .. you are welcome !

Fixed for all branches now .. to be in sync with flo device.

Below you can see AEX branch as example .. will be part of next AEX builds.

deb: do not set swappiness

https://github.com/followmsi/android_device_asus_deb/commit/e199ce14881bbf73d8b6bded42a07da5143266ce

Pls don't expect new PE build for deb now.

Thanks
[Nexus 7 (2013) Android Development] kmygmky:
I installed AospExtended-v6.2-deb-20190208-1518-UNOFFICIAL.zip with nano on deb. I like it the most. But the compass does not work well. You can not use applications such as Star Walk 2.
[Nexus 7 (2013) Android Development] js89:
Wow, very very nice work.

One thing I noticed on the AospExtended rom is that the minimum brightness is brighter than previous Oreo roms. 5 instead of 1 according to Brightness Tweak app, which unfortunately forgets the setting every now and then.
[Nexus 7 (2013) Android Development] JT1510365:
yes compass is broken but in my opinion there is no need for it vut it will probably be fixed eventually:)
[Nexus 7 (2013) Android Development] adi.vladut:
Labels in landscape mode

Do you have labels under the icons in landscape mode?

Is there an option to enable/disable the labels?
[Nexus 7 (2013) Android Development] sir_bazz:
As one of the few people who still own both flo and deb, happy to help where I can.

And no hurry for the fix as I'm setting it manually on boot with KA anyway.

Bigger thanks for creating the rom, and breathing new life into these old devices.
[Nexus 7 (2013) Android Development] prsa01:
Yes, I get the same. Labels in portrait but not landscape. Have not found a setting that gives landscape labels.
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.3

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

Actually I did not plan to make a new builld .. I'm still curious .. :D

AospExtended-v6.3-flo-20190215-1904-UNOFFICIAL.zip

AospExtended-v6.3-deb-20190215-2014-UNOFFICIAL.zip

Changes:

- AEX Update to version 6.3

- Do not set swappiness (deb only)

Tested flo version with Magisk 18.1 !

Enjoy :p
[Nexus 7 (2013) Android Development] JT1510365:
Thank you so much for the new build:) Can you please tell me are we eventually going to get a fix for the compass and a fix for nfc because nfc has been removed from the rom and compass sensor does not work but anyways i am very happy with it right now as it is:)
[Nexus 7 (2013) Android Development] Ch3vr0n:
[MENTION=5480152]followmsi[/MENTION] it looks like my earlier question may have been missed. Curly using your last AOSP 8.1.0 based rom on my Deb. What Android version is this 'extended' based on, and can I dirty dirty flash it (with or without wiping /data and /cache) or is a clean flash required?

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Nexus 7 (2013) Android Development] JT1510365:
aosp extended is based on android 9 pie and it works better than aosp 8.1.0 plus it has more customization options and has new features that came with pie:)

Make sure to wipe everything except internal storage
[Nexus 7 (2013) Android Development] followmsi:
Based on AOSP with some extensions .. good replacement for "classic" version.

Pls check website for more details ..

https://www.aospextended.com

Take backup of data partition first!

Update to latest Magisk manager .. still in Oreo.

Boot into latest TWRP.

Wipe system, cache, dalvik and start to install ROM, gapps and Magisk.

Reboot system and check .. all ok ?

If not do factory reset in twrp and start from scratch.

Same procedure for all devices ..

Good luck !
[Nexus 7 (2013) Android Development] followmsi:
NFC has been "hidden" but not removed ..

https://github.com/followmsi/android_device_asus_flo/commit/4317307bc7ea1689f7b991dfd5c2528d476a6195

If you copy back the permission files and reboot you can see and test NFC .. still buggy.

Similar issues like in Oreo.

AEX added Compass QuickSetting in 6.3 .. if you enable .. do you get any values at all ?

Do you get values but wrong values ?

Pls more details.

Lineage did apply patch for framework/native .. we may cherry-pick for next AEX release.

Still not sure if it helps/improves compass ..it's already part of current lineage-16 build ..

Do you get better compass results in lineage 16 ?

NFC will take longer .. not sure about compass.

Enjoy your weekend ..
[Nexus 7 (2013) Android Development] Aerys:
Can you make minimum brightness similar to 8.1 rom? It's to bright now:)
[Nexus 7 (2013) Android Development] Ch3vr0n:
I'll stick with this one then for now. It's precisely why I chose it. Stock, all those extensions, do it from being stock anymore. I don't like that.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Nexus 7 (2013) Android Development] lollyjay:
https://venturebeat.com/2018/08/28/how-android-pies-adaptive-battery-and-adaptive-brightness-work/
[Nexus 7 (2013) Android Development] lowsum:
Wow last build is just great! My good old FLO sleep like a baby, only 2% drain on a 24h idle. Only using Naptime and Universal GMS doze Magisk module. Incredible... I'm speechless!
[Nexus 7 (2013) Android Development] curiousde2002:
Just upgraded to 6.3 from 6.2 with dirty flash, before that clean install from your latest Oreo classic.

Compass is showing only values between 205° and 240°, also tried calibration with google maps showing medium accuracy but no success.

Otherwise the ROM seems to be great with one issue that I had on 6.2 already:

After reboot automatic screen rotation does not work in about 80% of the cases.

Some apps however can force the rotation.

Succeeding reboot sometimes does not help.

This last reboot I did via recovery, without wiping anything, just booting.

Now automatic screen rotation is working, but this can be coincidence.

But thanks anyway for your hard work!
[Nexus 7 (2013) Android Development] followmsi:
Had a quick look on my Flo now ..

Depending on the used app I get different results .. but magnetic north orientation seems to be weird.

Should be the same behavior as on last classic Oreo version.

Using same kernel and same sensors.

Will add the sensors patch from frameworks/native into next release .. to see if its improving.

But I don't have rotation problems ..

My kernel does include parrot fix from ex kernel .. no idea if you have cable issues.

Cheers
[Nexus 7 (2013) Android Development] curiousde2002:
:(

I had the rotation issue on Oreo only when Xposed was installed.

But as here on pie it was gone after some reboots, btw on Oreo it always came together with adaptive brightness not working. Once one issue was gone the other one was as well.

Just now while writing this I played with the compass.

When moving the device from horizontal to vertical I get different values and then a reboot.

Now the rotation issue is back.:(

I'd better not touch compass any more.

First it does not work and second whenever I enable it the device reboots.
[Nexus 7 (2013) Android Development] m0crt:
John

There's checks in the Moonlight app to disable 264 for certain ROMS detected due to performance of the GPU. I've recompiled a new APK that does now work.

Give it a go if you like:

https://drive.google.com/open?id=1qJgoVI2S598WLJN5INVGvgd3pU6HCqSy

Mo
[Nexus 7 (2013) Android Development] hlxanthus:
Anyone else recently having an issue with the setup stalling on checking for updates? On the 0209 version clean installed with pick open gapps. Ran out of time but I will try a clean install again later with the latest version. Been out of the room scene for a minute and not sure of this is a common issue that I just don't know how to overcome.
[Nexus 7 (2013) Android Development] followmsi:
No idea what's wrong with your device .. in my compass tests I never got unexpected reboot.

And still no rotation issues for me.

We will not be able to fix hardware issues thru software updates.

Need to test on latest classic Oreo version .. can't remember compass situation on Oreo.

Have to get working compass on my device to exclude hardware issues.

But not rush .. Compass has lower priority.

Cheers
[Nexus 7 (2013) Android Development] curiousde2002:
The last 2 reboots were via recovery, no rotation issue.

Maybe there is some correlation between the sensors for compass and rotation

I remember in Oreo the "heading" mode, as I call it, worked with Google maps and maps.me and this also requires working compass I guess.

But I never tested compass itself.

Another issue:D

My Deb has problems with deep sleep, actually almost no deep sleep when 4G is on but otherwise in standby.

"msm_hsic_host" seems to be responsible.

4G signal looks perfect.

With my S5 logged in in the same network no problems.

Any idea?
[Nexus 7 (2013) Android Development] Booroner:
I have noticed that the last compilation is a bit more cocky drum.

Everything else great, good work.
[Nexus 7 (2013) Android Development] ddv13:
Does someone else have the problem that the Play Store doesn't recognize earlier purchases and beta apps. All apps I purchased before need to be purchased again on my Nexus (which isn't the case on my other phones) and all beta apps can't be installed, because they miss the install button. I did a clean 6.3 of the ROM with Nano GApps.
[Nexus 7 (2013) Android Development] ranaxda200:
I'm having issue with deep sleep again on latest AEX on my Flo. [MENTION=231896]dev[/MENTION] any log would I provide? Plz help me.
[Nexus 7 (2013) Android Development] jhford:
I really need some help/advice. I have 2 debs running AEX. which are still spontaneously and frequently rebooting when I'm using Chrome and Chrome Beta. It happened with previous Roms I tested from he also, but I've tried so many that I've lost track. I'm happy to keep testing, but I also need something stable. Should I start all over with a clean install? If so, which Rom should I try? The various Pie Roms seem to have pretty much the same customization capabilities.

Thanks
[Nexus 7 (2013) Android Development] Booroner:
I would use AEX works incredibly well, it would make clean flash, first ROM together with Gapps (peak) after restart system configure and flash Magisk 18.1
[Nexus 7 (2013) Android Development] DCvan:
Yes, I had the same problem in clean installed (AEX 0128 version using pico). I believed I went to Play store app and clear both cache and storage. Not sure if I rebooted and launch play store or just open play store right after. I got all my purchased app recognized again.
[Nexus 7 (2013) Android Development] jhford:
Thanks, but I'm not sure I understand "first ROM together with Gapps (peak) after restart system." What does "together with Gapps (peak)" mean? Also, does "clean flash" mean the following?

1. Wipe dalvik, system and cache.

2. Reboot from TWRP back into TWRP recovery.

3. Flash AEX Rom.

4. Flash Gapps + whatever "peak" means.

5. Restart System.

6. Configure, whatever that means.

7. Flash Magisk 18.1.

8. Reboot System.

Thanks

EDIT.

I went ahead with a clean install. But I have a Google bootloop while it does "adding finishing touches" and "checking for updates." I rebooted to stop the bootloop, but it began bootloop in the same place, "checking for updates" again.
[Nexus 7 (2013) Android Development] Uchihi:
Those of you that have used this rom for a while, is there any issues? Battery life? Lag? Thanks
[Nexus 7 (2013) Android Development] firepower9966:
Recents takes forever to scroll through apps horizontally ,can there be option to have it scroll vertically like it does for phones. (I using same ROM on redmi note 3). It compresses apps to one line on top or bottom of scrolling. Also noticed this is more laggy and has trouble launching apps. I found previous RR-P ROM to be grreat, but though I try this one.
[Nexus 7 (2013) Android Development] adi.vladut:
I also had bootloop using that method. Flash the room then boot to system. Afterwards reboot to recovery and flash the gapps.
[Nexus 7 (2013) Android Development] taw62:
I'm on the latest AEX for flo and I'm totally happy with this ROM: no reboots, no fc, 99% deep sleep in idle. It's definitely not the newest hardware anymore but does it's job very well with the newest software.
[Nexus 7 (2013) Android Development] sir_bazz:
Yup the GUI is smooth, incredibly smooth.. And gaming aside, it's still a very usable device for almost everything else.
[Nexus 7 (2013) Android Development] followmsi:
I do not own deb .. can not test myself.

Does other Deb users have same deep sleep problem ?
[Nexus 7 (2013) Android Development] followmsi:
You missed the most important step for "clean install" -> wiping data !

Do it via twrp to keep internal storage.
[Nexus 7 (2013) Android Development] sir_bazz:
On PE here, but now that you mention it, yeah I also noticed it for the first time today.

Usually I put the tablet into aeroplane mode when not in use, (where deep sleep works as expected), but just happened to forget to do it this morning.

Didn't give it much thought until reading these posts just now. Will have a better look tomorrow.
[Nexus 7 (2013) Android Development] jhford:
I followed your advice. The only change I made was to wipe dalvik and cache after I flashed gapps arm/9.0/micro. But it still bootloops, if that's the correct term, during the Google setup. That is, it seems to be finished when the "anything else?" screen appears. I tap "no thanks " but the "adding finishing touches" and "checking for updates" screens reappear, and both previously described processes repeat infinitely. Any other suggestions?

Thanks
[Nexus 7 (2013) Android Development] followmsi:
Skip restore from google completely.

Have a look here ..

https://github.com/opengapps/openga...re-open-gapps-related-what-can-i-do-to-fix-it
[Nexus 7 (2013) Android Development] djjstew:
Installed ROM on Sunday and noticed significant lag. This morning went back into recovery and cleared dalvik and cache and rebooted and things seem to be much smoother now. This is not my daily driver usually just for some reading before sleep but I have not noticed any other issues. Battery performance is much better than Oreo. Worth the upgrade to get to play/learn Pie (of course my T-Mo Note 9 still not updated) and get the security patches.
[Nexus 7 (2013) Android Development] sir_bazz:
Unable to replicate any issue with deep sleep on deb. Enabling data with aeroplane mode off for a few hours this morning, has my typical, and expected, deep sleep numbers.
[Nexus 7 (2013) Android Development] Uchihi:
Tried flashing this rom for the first time, both from AICP rom and stock rom. Got the same error both times:

E004: This package is for device: flo; this device is .
E:unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/AospExtended-v6.3-flo-20190215-1904-UNOFFICIAL.zip'

Anyone know the solution? Installed via TWRP on both occasions, on a Nexus 7 2013 Wifi Version (flo).