yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] ripee:
Out of respect for followmsi, please remove my link. Users can figure out to look for the link in my signature.

But while we're on the subject, I just used the roomservice.xml that followmsi linked in the OP.
[Nexus 7 (2013) Android Development] followmsi:
Thanks for your reply !

Posting different ROM in different threads is always a bit special .. Nevertheless.

Actually we should respect [MENTION=5120185]flex1911[/MENTION] !

Main work for lineage sources has been done by him.

As I understood his flo device has broken USB port .. Not charging.

He wanted to repair at some point.

If somebody is going to publish lineage-16.0 for flo .. its maybe done by him first.

I fully understand the users are "hot" for Pie .. and for Lineage-16.0 too.

We may ask [MENTION=5120185]flex1911[/MENTION] directly about his plans ?

Maybe he is happy that somebody else is moving on.

It's all a matter of communication !

[MENTION=6005084]ripee[/MENTION]

What about RR 7.0 .. Do you like it ? :)

Why not publishing monthly RR builds for flo/deb ?

Enjoy your weekend ..
[Nexus 7 (2013) Android Development] flex1911:
Yeah, I feel absolutely ok if someone else continues my work on lineage for flo. I didn't plan much about it recently as I don't have any opportunity to fix it or even just work on it. I passed my flo work in lineage to [MENTION=5848265]npjohnson[/MENTION] so he will continue maintaining it and (probably) will try to bring the official support. And if someone else wants to publish their unofficial builds of Lineage 16.0, I'm definitely for it.
[Nexus 7 (2013) Android Development] ranaxda200:
My wifi router has only 2.4gHz option not dual mode so can't change it!

Still no deep sleep issue persists on aex pie too. Any log to provide you?
[Nexus 7 (2013) Android Development] followmsi:
Thanks a lot for the quick update .. And thanks again for all your work you have done for the flo/deb devices !
[Nexus 7 (2013) Android Development] followmsi:
Between AEX, RR and PE are no real device related differences .. all use same config and kernel. .. etc.

Right now I did switch to hidden 2.4ghz network .. and the device is sleeping :)

Pls replace the following file with root explorer ..

/system/vendor/etc/wifi/WCNSS_qcom_cfg.ini

Replace the complete file with this version .. (same file works for RR and PE too)

https://raw.githubusercontent.com/followmsi/android_device_asus_flo/aex-pie/wifi/WCNSS_qcom_cfg.ini

The change above will be part of next releases for February ..

- There will be one more RR with the same changes .. and fixing RR tools menu crash in settings. (Workaround)

- There will be one more PE version with the same changes .. and adding Chrome into system. (1275 MB system.img)

- Until we find proper fix for "soft reboot" issue on NON-CAF sources there will be no new classic version anymore.

- All new "classic" builds would have same reboot issue - if we do not find/apply proper patch first.

- Yes, for moment AEX seems to be my favorite ROM .. especially as "classic" replacement.

- At some point I will have to rename this "classic" thread to it's new name.

When Google February security patches are arrived the build process will start .. stay tuned :)

Enjoy your weekend ..
[Nexus 7 (2013) Android Development] Booroner:
After trying PE, Classic and AEX I can say that AEX is the best for me in daily use, no restart and significant problem, it's amazing for me.

I think as you [MENTION=5480152]followmsi[/MENTION] I think AEX would now be the way to go, again thanks for your hard work and waiting for the new compilations, which by the way the only thing that fails me are the gestures, the rest perfect !!!
[Nexus 7 (2013) Android Development] ranaxda200:
Thanks for your MAGIC! ;)

Finally deep sleep is working good testing for about 15 minutes. :good:

https://photos.app.goo.gl/Ga2bczyuHufG5pWk8
[Nexus 7 (2013) Android Development] Bingley:
Also switched from PE to AEX, and it's much smoother, less janky, and battery doesn't drain so fast. I'd love to disable substratum fully though as it's messing with my MX Player background so I can't get true black just shades of grey.

Other than that, I've noticed that the screen turns on for no apparent reason occasionally, even with wifi off and no reminders etc, which is odd.

Would love to see AEX continued/built upon over PE
[Nexus 7 (2013) Android Development] MikiGry:
[MENTION=3453224]Bingley[/MENTION]

Hmm. Are You using magnetic cover ?
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Good morning, friend, test it yesterday. Only 2 kernel files have stabile results: Update.ZIP_ElementalX-N7-6.06-deb.zip and Update.ZIP_google_msm_lineageos_kernel-deb-20170330.zip.

Update.ZIP_franco.kernel-deb-r29_20170329.zip - stabile result, but default governor and CPU frequency other than vs original Franco file from developer.

Update.ZIP_Quanta-Flo-v14-flo.zip - stabile result, but default governor and CPU frequency other than vs original Quanta file from developer. So Quanta - Franco based kernel, it have a same problem as Update.ZIP_franco.kernel-deb-r29_20170329.zip.

Quanta-Flo-v14_AnyKernel2_followmsi.zip, ElementalX-N7-6.06_AnyKernel2.zip, franco.kernel-flo-deb-r29_kernel-flasher-5.1-20170329.zip, google_msm_lineageos_kernel-flasher-5.1-20170330.zip - really have a bug with MIX kernel setiings - it leave SuperSU, but and settings - may be problem in this? We have dirty kernel install and it is possible kernel config file to be left on the disk (ramdrive)?

I take many screenshots, but upload it later.

P. S. Sorry for my English, I`m Russian.
[Nexus 7 (2013) Android Development] followmsi:
Thanks for your testing !

We need to sort this out first.

For this reason we stay on EX for a while .. until we have clear understanding of the changing values.

Just testing 7.1.2 sources .. to see if and what is breaking :)
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Cool! Waiting new ROM! :)
[Nexus 7 (2013) Android Development] followmsi:
Some small issues whtin the /hardware/qcom/audio package which are (hopefully) solved ..

The build completed successfully now :)

Please enjoy Android 7.1.2 on flo / deb devices ...

AOSP_7.1.2_r2_N2G47E_flo-ota-eng.followmsi.zip

AOSP_7.1.2_r2_N2G47E_deb-ota-eng.followmsi.zip

Installation:

1. Boot into TWRP

2. Wipe system, cache and dalvik

3. Install AOSP_7.1.2_r2_N2G47E_flo-ota-eng.followmsi.zip

4. Install open_gapps-arm-7.1-xxxx-2017xxxx.zip (optional)

5. Install SuperSU-v2.79-201612051815.zip (optional)

6. Reboot into system

- Until all the kernel testings are done I have used the same ElementalX kernel like in previous build. (v4)

- The installer will backup your gapps installation - no need to install gapps after the upgrade.

- SuperSU.zip is required as we have overwritten the boot.img !

Ejnoy :)
[Nexus 7 (2013) Android Development] miki67:
Thanks [MENTION=5480152]followmsi[/MENTION], dirty flashed over last 7.1.1 and updated to 7.1.2 without issues, all works very well... [emoji6]

Inviato dal mio Nexus 7 2013 (AOSP Nougat 7.1.2_r2_N2G47E) con Tapatalk 6
[Nexus 7 (2013) Android Development] conite:
I've never had a problem with these builds, but for some reason, this time, the setup wizard crashes ("Setup Wizard keeps stopping") whether I choose "set up as new", or choosing to bring my data from "Your Google Account".

Ideas?
[Nexus 7 (2013) Android Development] followmsi:
Made a dirty flash .. do you have a backup ?

Restore your last backup and reboot ...restore Data partition only !

Will check the setup wizard .. in the next days.

Need logs and detailed info.

Did you wipe system as well ?

Pls wipe system too .. cache, dalvik.

Did you install gapps ?
[Nexus 7 (2013) Android Development] conite:
I followed the posted instructions exactly (system, cache, dalvik wipe). Usually I flash the ROM, and GAPPS right away.

I was able to get going again by flashing the ROM, then booting, and then flashing GAPPS - thus avoiding the setup wizard. Never had to do it in two steps before.

Thanks for your work, BTW.
[Nexus 7 (2013) Android Development] followmsi:
This means if you not flash gapps then all is working fine with stock setup wizard ?

Then after setting up .. you reboot and install gapps, correct ?

Does have gapps his own setupwizard ?

Need to check this ..

As more information as better ..

I am the dirty installer .. takes a lot of time to setup all the stuff again.

I do have approx. 150 apps installed .. tons of logins .. one restore of data and I am happy ;)

Cheers
[Nexus 7 (2013) Android Development] conite:
Without GAPPS, there is no setup wizard. It just boots right into the home screen. Once booted that way, if you subsequently flash GAPPS (arm 7.1 pico April 4) it will skip the setup wizard and go straight to the home screen.
[Nexus 7 (2013) Android Development] followmsi:
Will test the complete setupwizard stuff in the next days .. Thanks for your input !
[Nexus 7 (2013) Android Development] m00head:
I think you also have to wipe data if you are doing a clean flash (not dirty flash) to prevent the initial Google setup wizard from stopping.
[Nexus 7 (2013) Android Development] conite:
I did.
[Nexus 7 (2013) Android Development] m00head:
By 'data' I meant the data partition, not data in general. The instructions do not say wipe the data partition - only system, cache and dalvik.
[Nexus 7 (2013) Android Development] brewer75:
gapps-config

I am currently using a different ROM but am interested in this one due to the vigorous support from the OP. I am intrigued by the possibility of flashing stock gapps and using the gapps-config.txt file to pare down the size and allow for something other than the pico gapps. However, I have attempted, and been unsuccessful, in finding my gapps installer file in order to copy the gapps-config.txt into that folder. I looked at the github post for further clarification but even a search of my files did not show a /sdcard/Open-Gapps/ file. Obviously, I have loaded the open gapps on my internal SD card in preparation for flashing but if that is the file I need to have found, I have been unable to copy the text file to that zip. I'm sure I'm zoning out on something here and I would just appreciate it if someone could help me out. Thanks!
[Nexus 7 (2013) Android Development] dealpapa1:
android-7.1.2_r1

android-7.1.2_r2

android-7.1.2_r3

android-7.1.2_r4

android-7.1.2_r5

Android 7.1.2 Release 5 (N2G47J)

Android 7.1.2 Release 4 (N2G47H)

Android 7.1.2 Release 3 (N2G47F)

Android 7.1.2 Release 2 (N2G47E)

Android 7.1.2 Release 1 (N2G47D)

what is the difference between those? why there are so many different release?
[Nexus 7 (2013) Android Development] dt0807:
I assumed you created a "gapps-config.txt" file with a text editor based on this:

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

I think you just have to have the gapps-config.txt and Open GApps package zip in the same folder on your internal storage or SD card (doesn't necessarily have to be this Open-GApps folder). Like if you want to pare down the stock package, you just have to have "open_gapps-arm-7.1-stock-xxxxxxxx.zip" (this is the installer that the wiki refers to) and "gapps-config.txt" in the same folder. And when you flash the GApps, it should automatically detect the config file.

I think the Open-GApps folder is created automatically by the Open GApps app if you download zips through that. I hope this clears things up.
[Nexus 7 (2013) Android Development] brewer75:
Thanks. I've never used the Open Gapps app so that file had never been created in my SD file before. I downloaded the app and things are looking proper now. I didn't make a custom gapps-config.text but chose to try the one posted by the OP and I haven't flashed the new rom yet so I'm not sure if the gapps will load properly. We shall see!

Well, I attempted to flash the 7.1.2 build with the stock gapps fix and iI received the message that there was insufficient space so I guess I'll try another time.

UPDATE...I tried again but after flashing the 7.1.2 rom, I rebooted into recovery, THEN I flashed the stock gapps as stated above and they seemed to flash normally.
[Nexus 7 (2013) Android Development] rockcipher:
Any ideas on the netflix issue beyond the drm blobs posted here? https://xdaforums.com/nexus-7-2013/orig-development/official-cyanogenmod-14-1-nightlies-flo-t3502494/post70351749#post70351749

Those work for me on this rom, but unfortunately stop Google Play Movies from functioning.
[Nexus 7 (2013) Android Development] m00head:
They are for all the currently supported devices:

https://developers.google.com/android/images

N2G47J: Pixel / Pixel XL (Deutsche Telekom)
N2G47H: Nexus 6P
N2G47F: Nexus 5X
N2G47E: Pixel / Pixel XL
N2G47D: Pixel C

Android 7.1.2 Factory Images and OTAs as well as April Security Update Now Available for Supported Devices

https://www.xda-developers.com/andr...y-update-now-available-for-supported-devices/
[Nexus 7 (2013) Android Development] Bingley:
Nope, no earphones in, airplane mode, basically flashed zips & updated apps & installed a browser. It's not often but sometimes I catch it.
[Nexus 7 (2013) Android Development] taw62:
For me as well. And since I found "round corners" in the settings, I'm totally excited ?.
[Nexus 7 (2013) Android Development] DCvan:
- Yes, for moment AEX seems to be my favorite ROM .. especially as "classic" replacement.

- At some point I will have to rename this "classic" thread to it's new name.

When Google February security patches are arrived the build process will start .. stay tuned :)

Enjoy your weekend ..[/QUOTE] [MENTION=5480152]followmsi[/MENTION] Thank you for taking your precious time in making Flo/Deb device running latest software!

Clean flash AEX (was running Classic Flo jan2019 version) and it's running pretty good. ?

On the next update, possible to add at a glance option and dark mode for swipe left Google feed?

Thank you and truly appreciated your time! ?

Cheers.
[Nexus 7 (2013) Android Development] spocoeric:
[MENTION=5480152]followmsi[/MENTION] Thank you for taking your precious time in making Flo/Deb device running latest software!

Clean flash AEX (was running Classic Flo jan2019 version) and it's running pretty good. ?

On the next update, possible to add at a glance option and dark mode for swipe left Google feed?

Thank you and truly appreciated your time! ?

Cheers.[/QUOTE]

Took me forever to find a way to get google feed dark mode. CPL launcher has an add-on that does it. Using it with AEX now
[Nexus 7 (2013) Android Development] elpeh:
AEX on deb: mobile data problem

Hello,

thanks for your efforts, followmsi. I installed your latest AEX build on deb. Usable and stable, as others wrote for flo. But: mobile data is not usable.

After unlocking SIM card, provider is recognized, mobile data show connected with "LTE", or e.g. "H" (if Preferred network type is set to "3G").

But no IP address is assigned.

The "Access point names" submenu gives an empty list and info "Access Point Name settings are not available for this user".

Any idea? (Not rooted yet, but I could do that.)
[Nexus 7 (2013) Android Development] prsa01:
**update - have also been getting some wifi resets (wifi disconnecting/reconnecting). I'm going back to the orig wifi file and will report if any change. **note - I am also on a new version of dd-wrt on my router so issues may be at the router.

FYI only - Had my first hang/crash/reboot on AEX today just browsing in Chrome.

My (impression only) is slightly more choppy browsing since making the op recommended wifi file change (post #2176) to enable deep sleep. Wasn't enough use either before or after the change to be more than just an impression.
[Nexus 7 (2013) Android Development] Longerski:
What is "wifi file change"?
[Nexus 7 (2013) Android Development] prsa01:
See post # 2176

See post # 2176
[Nexus 7 (2013) Android Development] prsa01:
AEX app icon descriptions

OK, feeling like more of an idiot than usual.

How do I get app labels to display? Under home screen settings, "display app labels" is on. Sure it's simple, but can't figure it out.

Thanks
[Nexus 7 (2013) Android Development] jhford:
Minutes

Is it OK to replace the ini file on AEX? I just did it. What do I gain?

---------- Post added at 08:59 PM ---------- Previous post was at 08:51 PM ----------

Anybody know how to get minutes and seconds in the status bar clock working on AEX? I use Nova Launcher. So, i tried the Activities widget trick and long pressing the cog icon in the status bar pull down to reveal the hidden System UI menu. But there is no such selection in either.

Thanks
[Nexus 7 (2013) Android Development] elpeh:
At least after installing Magisk (but I think, it's independent - I somehow missed it):

manually adding APN settings does work, as does mobile data if they are correct.
[Nexus 7 (2013) Android Development] DCvan:
Settings/Extensions/statusbar/clock settings

There is no second that I can see and it's working fine for me.
[Nexus 7 (2013) Android Development] followmsi:
Pixel Experience .. the final ROM

PixelExperience_flo-9.0-20190206-0806-UNOFFICIAL.zip

Changes:

- Google security updates -> February 2019

- Increased system partition from 1200MB to 1275MB

- Added Chrome browser

- Reverted some Wifi changes to fix Deep Sleep.

This ROM requires 1275MB system partition ! - Pls use "sysrepart_1280_120.zip" script.

One last try .. ;)

Pls go ahead and start building regular PE builds for flo/deb.

I just don't have the time to make regular PE builds too.

It's still a nice option for our devices.

Enjoy :p

EDIT:

Want to finish PE in a good state .. and made a quick build to fix Bluetooth for Deb device only:

PixelExperience_deb-9.0-20190206-1921-UNOFFICIAL.zip
[Nexus 7 (2013) Android Development] makjim:
I have installed the AEX on my deb as well. Seems quite stable but have problem turning on the Bluetooth.
[Nexus 7 (2013) Android Development] followmsi:
Thanks for report.

Need to fix it for Deb .. next release.

Should not work on all CAF builds.
[Nexus 7 (2013) Android Development] vagelis74:
Great rom, very smooth and beautiful the PE pie, for battery i will test the next days the bahaviur
[Nexus 7 (2013) Android Development] aclegg2011:
[MENTION=5480152]followmsi[/MENTION] good job as usual. I've got bliss pie booting on my Deb!
[Nexus 7 (2013) Android Development] PhantomAndroid:
Hi everyone,

I'm still getting the Moonlight error for "This device or ROM doesn't support hardware accelerated H.264 playback." I've tried both the RR Rom and Pixel Experience Rom for Android Pie (latest ones), but both seem to get the error. Does anyone have any more ideas I might be able to try to get it to work? Thanks in advance!

-John
[Nexus 7 (2013) Android Development] abhifx:
GAh! Tempting but i am now with AEX and will have to wait.

There are three things i wish would be fixed (i wish i knew how to help in this regard),

1) Wireless display (this tablet also makes my tv smart)

2) Standby drain fix (which i hope this new update will bring)

3) The elemental kernel has some issue with my screen and i get tons of ghost touches randomly (but i still need double tap to wake)
[Nexus 7 (2013) Android Development] followmsi:
1. Maybe we could use lineage solution for wireless display at some point.

As you may know native miracast support has been dropped in Pie.

2. Yes .. just running latest PE build .. same deep sleep as in other ROM. As the same code fix works on all ROMs.

3. There is no ex kernel for pie ! My kernel does support dt2w as well.

Aex still needs to merge monthly changes .. when they are done we can start building.

Cheers
[Nexus 7 (2013) Android Development] aquatix:
I went the upgrade way of first dirty flashing the latest PE build on my flo over CLASSIC after doing the partition resize, which all ran fine. Then I wiped everything except for data and internal storage, and flashed AEX and gapps pico (and later nano). The tablet boots fine, and I even get notifications of Telegram and such on my lock screen, but on unlock (with a pattern), Android UI restarts.

I captured a lot of log, of which this seems relevant: https://pastebin.com/raw/J4Fv51v0 Of course I'm positive that my unlock pattern is correct.

Any ideas what is causing this? How to fix, apart from doing a complete wipe? :) Thanks in advance!
[Nexus 7 (2013) Android Development] lollyjay:
Has anyone upgraded to magisk 18.1.?
[Nexus 7 (2013) Android Development] aquatix:
I did, seemed to work fine on my brief time using the latest PE ROM.
[Nexus 7 (2013) Android Development] followmsi:
We will need to check this later on ..

Pls use AIDA or other tools and test for codecs .. OMX.qcom.decoder.avc missing ?

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Not sure if we have keymaster issue or it's just your fault. :)

Just boot into TWRP and flash the zip file below .. reboot into system and login without any passwords/pattern/pins.

Works on every device ..

Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip

Set new pattern/pin/password and test again .. we may have keymaster issue.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Resurrection Remix .. the final ROM

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

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

Changes:

- Google security updates -> February 2019

- Reverted some Wifi changes to fix Deep Sleep.

- Workaround to fix crashing RR Tools settings menu

Sources:

https://github.com/followmsi/manifests/tree/flo-deb-rros-lineage-16.0

Tested with Magisk 18.1 !

Enjoy :p

EDIT:

RR team introduced a new bug in February updates

Long press on power button (to get shutdown menu) will crash SystemUI.

There will come new builds once RR team has fixed this issue.
[Nexus 7 (2013) Android Development] aquatix:
Oh, that's cool, going to try right now. Just to be clear: that won't wipe my data right? :)

Edit: awesome, that seems to have worked. Thanks again, going to fly AEX for a bit!

Edit 2: there was a notification about "Tap to finish Nexus 7 setup", which opens a wizard that among other things, sets up your lockscreen. Might be related? (Or red herring of course).
[Nexus 7 (2013) Android Development] elpeh:
AEX device encryption

Hello,

latest AEX on deb: encrypting the device doesn't seem to work. After having been asked for PIN and then confirmation, a green droid is show for a couple of seconds. After that boot loop. Had to wipe data in TWRP recover as data is no decryptable in TWRP with the PIN. Tried the encryption process afterwards a second time. Same result.
[Nexus 7 (2013) Android Development] SergioA:
Hi followmsi, thanks for your hard work!!!!

I've just dirty installed RR over PE (usual wipes), all is working really fine, but the power button isn't responding when long pressed, and a message telling "system UI keeps stopping" appears...

Other than that, all is brilliant ;)

Any suggestion to fix the power button issue?

Thanks again and Ciao from Italy

Sergio
[Nexus 7 (2013) Android Development] followmsi:
Made 4 RR builds for 4 different devices today .. all have the same problem. :(

Not sure when it's fixed by RR team and when I will have time for building again ..

Sorry .. no better news.
[Nexus 7 (2013) Android Development] SergioA:
Thanks followmsi, don't say sorry, you're doing a great job in keeping our devices alive, and giving us you time and competence, for now I'm perfectly satisfied with PE which I restored from yesterday's backup ;)

Grazie mille!!!

Sergio

Inviato dal mio ONEPLUS A6013 utilizzando Tapatalk
[Nexus 7 (2013) Android Development] followmsi:
Thanks for the info .. seems to be a general keymaster issue.

AEX uses Lineage keymaster sources too.

Maybe I adjust for next release .. not sure yet.
[Nexus 7 (2013) Android Development] followmsi:
To finalize the custom ROM series !

All custom ROM using the same device/vendor and kernel sources ..

lineage-16.0-20190208-UNOFFICIAL-flo.zip

lineage-16.0-20190208-UNOFFICIAL-deb.zip

Renamed the trhead a bit .. Only until AEX is ready for February. :)

Enjoy LineageOS :p