yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] abeyruma:
Install Magisk and all the apps on your Playstore will work fine... You just click Google Playstore in Magic Hide settings
[Nexus 7 (2013) Android Development] esykas:
Thank you!!!!

my nexus it still smooth again, and lag free
[Nexus 7 (2013) Android Development] dirkdigles:
Got this installed yesterday per ipdev's steps above - wonderful job guys! Long live flo & deb
[Nexus 7 (2013) Android Development] underflash:
Get error after new install with complete system/data wipe:

Camera Error. Can't connect to the camera.

Any solution?
[Nexus 7 (2013) Android Development] abeyruma:
Look for a camera app in Playstore... ?
[Nexus 7 (2013) Android Development] underflash:
Stock camera app does not work? :confused:
[Nexus 7 (2013) Android Development] abeyruma:
Unfortunately not... But you can find a third party camera apps on Google PlayStore
[Nexus 7 (2013) Android Development] stunned:
Is it possible to charge the device with qi stand and have screensaver on? Like does it get enough power to actually charge the device while screen is on?
[Nexus 7 (2013) Android Development] nigelhealy:
I think it may be a unit specific problem, way back on another entirely code set (stock TWRP, Pure Nexus), I had to use the multiboot version of TWRP.

I wish whatever was specific to my unit could be fixed by something.

Of course a full wipe just loses all logs. Best I can do is next time it goes awry is to try to capture logs.
[Nexus 7 (2013) Android Development] slaman:
I just tried again using updated gapps and still have issues. I'll do a clean install now.
[Nexus 7 (2013) Android Development] followmsi:
When you open gapps only ?

Other apps don't have problems ?

No problems with cache ?

Pls wipe cache / dalvik inside TWRP ..

Do you get error/warning message while installing gapps ?

Did you restore last backup successfully ?

Just as reminder .. when you restore data you may need to install supersu as the last step again.

The su.img is located on data.
[Nexus 7 (2013) Android Development] slaman:
That worked! Saved me from a clean install.
[Nexus 7 (2013) Android Development] drewski_1:
I had no major issue with Dirty Flash of v4 over v3.

I did lose root flashing EX-6.06. I thought I flashed the version that was to maintain root, but maybe user error and used the older one :confused:
[Nexus 7 (2013) Android Development] followmsi:
Nice ..:)

If you play with ROMs you should always have a backup on USB-OTG.

Just /data only .. the other parts are coming from the ROM you install.
[Nexus 7 (2013) Android Development] followmsi:
I will try to explain .. :)

It's all about systemless rooting.

In old times the rooting process was done in system partition.

Since we have systemless rooting it's done in the boot.img (modified ramdisk) AND on /data partition (su.img)

In old times we could change boot.img without re-rooting the device, as all rooting stuff was in system anyway.

In new times we need to install supersu.zip after every new (full) boot.img installation.

If you install a ROM (any ROM on any device) there is always a "full" boot.img included.

ROM A needs ramdisk config A and ROM B wants to have ramdisk config B.

For this reason each ROM has to have it' "full" boot.img included.

If we install a new ROM we completely overwrite the boot.img

android boot.img -> kernel binary AND compressed ramdisk

SuperSu.zip is splitting the boot.img into kernel binary and ramdisk first.

Aferwards the script will decompress the ramdisk.

Will modify the ramdisk for rooting and other stuff .. vertiy /encryptable .. etc.

Repack and compress the ramdisk again and merge it together with the kernel binary to a new "rooted" boot.img !

The first "double boot" after supersu installation is actually part of this process .. to setup the changes triggered in the ramdisk before.

All the Anykernel or Lazyflasher kernels I have made for flo .. are doing the same like SuperSu.

But they don't modify the ramdisk at all - you could modify them if you want - but it's not done here.

This way we can use just one kernel binary with different ramdisk configs.

For example there is no need to make one boot.img for deb and one boot.img for flo.

Just talking about AOSP .. think you want to make kernel for lineageos . etc. too.

One ramdisk ..e.g. one tailor-made boot.img for each flavour :)

This is the reason why kernel developer using custom install scripts like anykernel ..etc.

You can't make a tailor-made boot.img for all ROMs if you want to release a kernel.

You just replace the kernel binary .. like explained above.

Hope this helps a bit ...

Cheers :)
[Nexus 7 (2013) Android Development] followmsi:
Chapter GAPPS :)

Have made some more tests: check gapps persistence after ROM installation

1. Boot into TWRP

2. Install v4 over v4

3. supersu install

4. wipe cache / dalvik

5. reboot into system

As you can see I did not install gapps - to test if the previous installation will survive !

Gapps were installed before and were working fine.

After boot into system .. without (fresh) gapps installation - the same problem like other users have.

Crashing google apps .. no play store ... etc.

Made a reboot into TWRP and installed v4 and gapps and supersu again .. like I do normally.

Did wipe cache an dalvik as well.

Booted back into system .. still strange errors.

I had to register my device again .. and now google has detected it as Nexus 7 2012 device as well :)

Used the gapps pico version all the time .. but my other google apps, installed via playstore (gmail) are still going crazy.

Need to manually uninstall and reinstall via playstore - this has fixed it.

Did not search for other ways to fix it either ..

Now I did make a restore of my last backup ... all is back to normal.

But we can summarize:

- Gapps installation is NOT persistent on this ROM !

If you had gapps installed before you MUST install it after ROM installation again !

- If you boot just once into system wihtout gapps installation you will get problems with google apps and play-store registration.

Even you install gapps afterwards - it seems not to fix the "broken" settings on /data partition.

Maybe we can fix this .. adding "addon.d" support to the ROM .. right now I need to get more information first.

[MENTION=1938578]slaman[/MENTION] [MENTION=4775959]nigelhealy[/MENTION]

Now I can understand some of your problems much better :)

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Chapter "/system/addon.d/" & "backuptool.sh"

The backuptool functionality known from lineageos and other ROMs is NOT part of AOSP!

Here are the sources for lineageos ..

https://github.com/LineageOS/android_build/blob/cm-14.1/tools/releasetools/ota_from_target_files.py

They add several lines of code to add the "backuptool" feature.

The same sources in AOSP ...

https://github.com/android/platform...8/tools/releasetools/ota_from_target_files.py

Nothing about the backuptool .. not existing in AOSP.

The actual backuptool.sh will be integrated into the OTA installer package .. inside the "install" folder.

This tool will be copied into /tmp folder and will run a "backup" and a "restore" job.

All triggered via the edify script inside the custom installer of lineageos.

Not sure if I will have the time to implement this feature into pure AOSP sources ..

To summarize :

- addon.d scripts are not supported by the AOSP OTA package installer !

- And again .. if you have installed gapps before you need to install them again - after ROM installtion/upgrade.

- Gapps are not persistent like in lineageos .. etc.

Will add this onto the first page as well ...

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Chapter "/system/addon.d/" & "backuptool.sh" - Part 2

There are some more changes required to implement this feature into AOSP.

As I want to keep the ROM as close as possible to AOSP standards I will not integrate this feature into the sources.

But as I like to play :)

Update.ZIP_TWRP_flo_deb_addon.d-backup.zip

Update.ZIP_TWRP_flo_deb_addon.d-restore.zip

ROM Upgrade Installation -> persistent gapps:

1. Boot into TWRP (3.1.0-4)

2. Install Update.ZIP_TWRP_flo_deb_addon.d-backup.zip

3. Install current AOSP ROM -> AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v4.zip

4. Install Update.ZIP_TWRP_flo_deb_addon.d-restore.zip

5. Install SuperSU.zip - due to systemless rooting

6. Reboot back into system

Enjoy :)

EDIT:

Have made a new "custom" installer for the ROM ... integrated the backuptool - only into the installer not into the sources.

Not sure if this will be integrated for all the next ROMs.

But why not .. makes life easier :)

AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v4-addon.d.zip

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

ROM Upgrade Installation -> persistent gapps:

1. Boot into TWRP (3.1.0-4)

2. Install AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v4-addon.d.zip

3. Install SuperSU.zip - due to systemless rooting

4. Reboot back into system

The "addon.d" topic will be closed now :)

Cheers
[Nexus 7 (2013) Android Development] rajsris:
Does this mean no need for gapps reinstallation with each rom update?
[Nexus 7 (2013) Android Development] followmsi:
Yes.

If you have installed gapps before you don't need to install them again.

Of course, if you wipe system you need to install them again. :)
[Nexus 7 (2013) Android Development] drewski_1:
this is cool stuff! thanks [MENTION=5480152]followmsi[/MENTION] :highfive:
[Nexus 7 (2013) Android Development] rajsris:
New add-on ROM works to keep gapps. I flashed along with SuperSU and everything remained ok after reboot.
[Nexus 7 (2013) Android Development] followmsi:
To finalize the flo/deb kernel series .. the franco.Kernel - r29

franco.kernel-flo-deb-r29_kernel-flasher-5.1-20170329.zip

Installation:

1. Boot into TWRP 3.1.0-4

2. Install franco.kernel-flo-deb-r29_kernel-flasher-5.1-20170329.zip

3. Reboot into system

Enjoy :)
[Nexus 7 (2013) Android Development] rajsris:
Also SuperSU flash again correct?
[Nexus 7 (2013) Android Development] followmsi:
No ;)

Not needed with this version.

It keeps supersu.

Only OTA packages will need new SuperSU installation.
[Nexus 7 (2013) Android Development] schufti:
very wise reasoning ... debate over this topic drove the initial developer away!
[Nexus 7 (2013) Android Development] drewski_1:
yep. been doing a variation of this for years since the Stock package is the only one that removes the AOSP redundant apps. :good:
[Nexus 7 (2013) Android Development] abeyruma:
It will definitely charge but slower... You can use a screen saver while charging

---------- Post added at 05:19 AM ---------- Previous post was at 05:17 AM ----------

https://xdaforums.com/showpost.php?p=62713192&postcount=255

Try using this to improve your charging speed... It works for me
[Nexus 7 (2013) Android Development] Bingley:
I'm getting huge system drain atm, 30-15% in maybe 5 minutes, and a third of battery usage is system. How can I find out what is causing this more accurately?
[Nexus 7 (2013) Android Development] abeyruma:
Show app usage

Settings Battery Then 3 dots on top left
[Nexus 7 (2013) Android Development] jhford:
Official Lineage OS

I have a deb and I've been using the Official Lineage OS for over a year, but the deb will no longer be updated. How does this ROM, compare and is it going to continue to be updated as Android is updated?

Thanks
[Nexus 7 (2013) Android Development] abeyruma:
It's still has Oreo October update... We're still waiting for Android Pie... ?
[Nexus 7 (2013) Android Development] jhford:
What are the ROM'S pluses and minuses?
[Nexus 7 (2013) Android Development] abeyruma:
Non that I've seen so far... It's fast and fluid..... installing Magisk Modules made it even better...
[Nexus 7 (2013) Android Development] Newstyler88:
I have tried bug de battery backup is not good for now. In my opinion the lineage oficial is better in that field. I hope the next updates chances my point of view. Thanks
[Nexus 7 (2013) Android Development] followmsi:
December 2018 ..

flo-Classic_12-2018_AOSP_8.1.0_r53_OPM8.181205.001_followmsi.zip

deb-Classic_12-2018_AOSP_8.1.0_r53_OPM8.181205.001_followmsi.zip

Changes:

- Google security updates -> December 2018 (android-8.1.0_r53)

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

Enjoy :p
[Nexus 7 (2013) Android Development] tombraga:
Thanks, installation without problem
[Nexus 7 (2013) Android Development] gege622:
It's been so long since I have thanked You.

So thank you followmsi.

It always works like a charm
[Nexus 7 (2013) Android Development] abeyruma:
There is no Picture In Picture Option on the last Service Patch
[Nexus 7 (2013) Android Development] followmsi:
Tested pip with chrome and vlc .. still works fine.

Pls confirm.
[Nexus 7 (2013) Android Development] abeyruma:
It's not in the options anymore sir... My YouTube vanced doesn't work

No options sir followmsi
[Nexus 7 (2013) Android Development] abeyruma:
The Picture in Picture is not in the options sir...
[Nexus 7 (2013) Android Development] lallolu:
Delete
[Nexus 7 (2013) Android Development] abeyruma:
Got my Problem Fixed... Lels

I think I Messed Up with Some Modules on Magisk.... Got ng Picture in Picture Fixed... Thx
[Nexus 7 (2013) Android Development] Ch3vr0n:
How about you ask in the magisk section then?

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Nexus 7 (2013) Android Development] jhford:
I recently switched from Lineage to this ROM because Lineage stopped issuing nightly updates. I use Android Auto to listen to podcasts but I get the error message that Google Play Services isn't working and AA crashes. How can I fix it? This never happened with Lineage.

Thanks
[Nexus 7 (2013) Android Development] TechnicsKuzya:
[MENTION=5480152]followmsi[/MENTION], are the wi-fi time auto sync work at the latest build!? Now using your latest 7.1.2, all ok, some month ago tried 8.1 and have a problem with connection to the hidden wi-fi network and wi-fi time auto sync (using network time). Are this problems now solved!?

P.S. When I install SIM-card, time auto sync, but without SIM - no. With 7.1.2 no such problem.
[Nexus 7 (2013) Android Development] shadow25:
Confirm, same error
[Nexus 7 (2013) Android Development] jhford:
Maybe I should re-flash Lineage.
[Nexus 7 (2013) Android Development] followmsi:
Time sync works for me ... Get correct time via automatic settings.

Hidden network needs workaround for initial connection - switch off display for a few seconds.

I am actually connected to hidden network.

There were no device and kernel changes since June .. just security updates for Oreo.
[Nexus 7 (2013) Android Development] followmsi:
Do not use Android Auto at all .. not sure if was working before.

Pls post logs. (Logcat)
[Nexus 7 (2013) Android Development] jhford:
Sorry. I've never used Logcat. Instructions?

Thanks
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Via Wi-Fi only (with fully disabled SIM-card, enable Airplane mode and then enable Wi-Fi, then disable time auto sync, set manually incorrect time and timezone and enable time auto sync - and nothing... then disable airplane mode and time succesfully sync via SIM-card GSM network)!?
[Nexus 7 (2013) Android Development] followmsi:
As I don't own deb device I did test on flo now.

For me it works if I change minutes, hours and days.

Will always be corrected via automatic time setting (wifi).

But not the time zone itself.

Like you describe it looks like GSM will correct time zone too.

No idea if this is configurable for wifi connection .. will need to check.
[Nexus 7 (2013) Android Development] inkaine:
This has never been the case for Nexus 7 (flo) firmware. Time was adjusted from wifi automatically but you had to switch to the correct timezone manually. I've carried my Nexus 7 around the world several times. Has been like that since at least KitKat.
[Nexus 7 (2013) Android Development] jhford:
AutoMate seems to work.
[Nexus 7 (2013) Android Development] Ch3vr0n:
Anyone know if this works with the N7c 2013? Seems to be identical except having a larger battery. Just curious. That said, a few days ago I stepped on mine and I'll be getting a ''new'' one, except I'd like to go from my current WiFi only to the LTE capable version. I know I most likely can't flash the rom backup from my wifi to the LTE can I? And then dirty flash the LTE rom on top? If not, can I flash /data and /userdata between devices?

Sent from my Nexus 7 with Tapatalk
[Nexus 7 (2013) Android Development] emmett.tsai:
Hi,

Here is an android pie image for flo:

AOSP_android-9.0.0_r21_full_flo-ota-eng.emmett_20190103-011704.zip

Screenshot 1

Screenshot 2

Thanks to [MENTION=5480152]followmsi[/MENTION]

This image is base on android-9.0.0_r21 aosp and fork device / vendor / kernel from [MENTION=5480152]followmsi[/MENTION]

and merge LineageOS 16.0 20181208 to kernel

and pick hardware qcom patch from [MENTION=5480152]followmsi[/MENTION]

and then patch a workaround to fix no display issue.

I am not test more. Just check boot into android and check version in Settings.

source manifest:

https://github.com/EmmettTsai/manifest/tree/flo-aosp-pie
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=8199534]emmett.tsai[/MENTION] Thank you for your work. Did you flash this with GApps; if so which one? Also did you format data? Factory reset?
[Nexus 7 (2013) Android Development] emmett.tsai:
I use recovery: twrp-3.2.3-0-flo.img, and install step:

1. wipe Dalvik / ART Cache, system, Data, and cache

2. Format Data

3. install ota package

4. re-mount system from twrp UI (I not modify ota script, so need remount by self, else install gapps will fail: Incompatible Android ROM detected)

5. install gapps package

6. wipe cache/dalvik

7. reboot system

I did not tune the system image size. after install AOSP_android-9.0.0_r21_full_flo-ota-eng.emmett_20190103-011704.zip, the system partition space will be:

Size: 837.8M

Used: 677.8M

Available: 160.0M

I try to install open_gapps-arm-9.0-pico-20181229.zip (93M), but it still say not enough space to install gapps.

However, I already re-partiton my nexus 7 via "parted" command in CWM recovery 6.0.4.9 (re-partition_note.txt)

So, for my device, I build a 2G system partiton image:

BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2147483648 # 2G
BOARD_USERDATAIMAGE_PARTITION_SIZE := 11081351168 # 10568M = 10.32G

AOSP_android-9.0.0_r21_full_flo-ota-eng.emmett_20190103-075945.zip

and install with open_gapps-arm-9.0-stock-20181229.zip success

Unfortunately, Wi-Fi not work yet, can't login google play store.

Pixel Launcher crash.

Quickstep ok.

Screenshot 3

Screenshot 4
[Nexus 7 (2013) Android Development] lollyjay:
Thanks [MENTION=8199534]emmett.tsai[/MENTION] for the reply. It is a good start
[Nexus 7 (2013) Android Development] abhifx:
Fantastic! Let the testing begin. Thanks [MENTION=8199534]emmett.tsai[/MENTION] and [MENTION=5480152]followmsi[/MENTION]
[Nexus 7 (2013) Android Development] followmsi:
Very good stuff !

[MENTION=8199534]emmett.tsai[/MENTION] .. Thanks for your work !

My time for Android will be shorter and shorter ..

In 2019 I will start a new job which requires more travelling .. for this reason I will not have much time left for Android anymore.

Nevertheless I still plan to make monthly "classic" builds for flo/deb.

Today I have added a few more changes for flo .. Added USB.basic service, Pie gestures .. etc.

https://github.com/followmsi/android_device_asus_flo/commits/aosp-p

As well I have changed wpa_supplicant_overlay.

https://github.com/followmsi/android_device_asus_flo/commit/35a0ba50fe6078c1cfd7704e9816adebffb8d132

You may test this change to get wifi running - just change the files in /sytem/vendor/etc/wifi accordingly and reboot.

Maybe there are more changes required to get wifi running.

I would love to have the time to "play" with Android like before.

Thanks again !

Cheers
[Nexus 7 (2013) Android Development] clarkgable:
I'm having difficulty running this ROM/Gapps together so I will wait for further development before trying again. Thanks for your efforts though.
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Have a new info about this bug. With my local internet provider time sync don't work, if I connect with wifi that use VPN, time sync work, but time zone still not. Then I'm reconnect to the local provider (without VPN) and time sync work too. But If I restart device time sync don't work again and time auto change to the GMT+11. Then I'm again connect to the wi-fi VPN and time immediately sync with manually setup time zone (GMT+3). So, IMHO, first of all this is a problem with NTP servers (may be link with GPS setting)!? Try latest Unlegacy build - same problem. And same that with 7.1.2 no such problem.
[Nexus 7 (2013) Android Development] Ch3vr0n:
[MENTION=5480152]followmsi[/MENTION] can you comment on my question please (the most important one is the part of going from wifi (Flo) to LTE model (Deb).

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Nexus 7 (2013) Android Development] followmsi:
Pie testing ..

Updated all the Pie branches today .. cherry-picked the relevant changes from [MENTION=8199534]emmett.tsai[/MENTION] !

Merged latest kernel changes from lineage and made a new build ..

flo-Classic_12-2018_AOSP_9.0.0_r21_followmsi.zip

As well I did prepare deb device for pie .. added ril-caf for pie ..etc.

When January patches are arriving I will make new Pie build for deb too.

Sorry, I did not test the flo build myself yet .. but still wanted to share the build today.

Again .. big thanks to [MENTION=8199534]emmett.tsai[/MENTION] for the code fixes.

And big thanks to [MENTION=5120185]flex1911[/MENTION] for all his work !

Enjoy :p
[Nexus 7 (2013) Android Development] tombraga:
I have your last classic 8.1.0 installed. Can I make dirty flash to this new Pie 9.0.0?
[Nexus 7 (2013) Android Development] lollyjay:
Seems to be corrupted :confused:

EDIT: third try worked

EDIT: No wifi
[Nexus 7 (2013) Android Development] clarkgable:
Have you successfully loaded a 9.0 Gapps with this Pie ROM? That's where I'm falling short at present. I'm getting Error 70 on twrp.
[Nexus 7 (2013) Android Development] lollyjay:
Yes nano gapps installed.

But wifi will not work

---------- Post added at 06:13 PM ---------- Previous post was at 06:03 PM ----------

@followmsi any chance you can find out what is wrong with wifi?

---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------

@followmsi any chance of getting wifi to work?
[Nexus 7 (2013) Android Development] clarkgable:
I've been trying with pico gapps but I keep getting Error 70
[Nexus 7 (2013) Android Development] followmsi:
Userdata and data is the same .. if you move to new tablet you need to backup internal storage too.

Running Flo /data backup on Deb device should work .. maybe some hickups at first boot.

Take backup first and test ;)
[Nexus 7 (2013) Android Development] followmsi:
Error 70 means no disk space left to install gapps on system.

The ROM size is getting bigger and bigger ... Time to repartition soon.
[Nexus 7 (2013) Android Development] followmsi:
Should work .. but in case of problems you need to start with clean install.

Take backup first.
[Nexus 7 (2013) Android Development] followmsi:
Yes, will look into wifi .. when time is left.

Thanks
[Nexus 7 (2013) Android Development] emmett.tsai:
Thank you, wifi work now,

but I need change TARGET_COPY_OUT_VENDOR to TARGET_OUT_VENDOR in Android.mk, TARGET_COPY_OUT_VENDOR is empty for me.

I am not sure is it because I use aosp original platform/build project

I install flo-Classic_12-2018_AOSP_9.0.0_r21_followmsi.zip + open_gapps-arm-9.0-pico-20181229 success

and can login playstore, after install package, my system space:

Size: 1.9G (2066256)

Used: 833M (852800)

Available: 1.1G (1213456)

Graphic is not stable, view broken when sliding, not sure it is framework issue or kernel issue.

I first test to rollback the kernel back to followmsi-oreo_2018-06-26 and only pick some patch. flo kernel pie-test

View broken seem fixed, but the view update become slow.