[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]

[Alyonas_boy]

I have been running this for over a month now and the slowness is getting to me. Very frustrating. Even from a fresh boot it is extremely slow. If I run fstrim it will speed up for awhile and then go to a crawl again. Strating to think I need to go to Android 10 instead. My kids have Nexus 10's. Dual cores with 2gb ram and Android 10. Runs beautifully. Way way faster than my nexus 7 2013

 

[underflash]

WIth https://xdaforums.com/t/app-4-1-hebf-optimizer-battery-saver-and-root-toolbox-2021-05-31.3401341 you can set custom fstrim interval, e.g. every 8 hours.

 

[klugec]

Hi,

What kernel do I need for otg + charging at the same time?

Thank you

 

[isenbart]

Hi all, I have just found my old nexus 7 (2013) and managed to install twrp and android 9 custom rom. My nexus 7 charging port is no longer working but able to charge via wireless. To install android 10 and above custom roms i see the device needs to be repartitioned. I presume this would completely wipe the device and i would be worried that I would not be able to transfer any custom rom zip onto the device due to usb port not workinag. Is this correct? If so i will stick with android 9.

I have the same issue with the USB port but repartitioned my Nexus 7 before it broke. So I'm very happy followmsi provides this rom and I can keep my tablet up to date. I also would not know how to transfer a rom zip on the device after wiping.

 

[poo706]

In my humble opinion, 17.1 runs much smoother on flo than 18.1 or 19.1. And since 17.1 still receives monthly security updates, I went ahead and built from source to get the latest August 2022 updates. Here's the zip if anyone else is interested.

<removed>

 

[underflash]

I went ahead and built from source to get the latest August 2022 updates

Would be great you could guide how to build 17.1 from source. Thanks. Definitely time to downgrade at my end.

 

[poo706]

Would be great you could guide how to build 17.1 from source. Thanks. Definitely time to downgrade at my end.

I just followed the link in the OP: https://github.com/followmsi/manifests/tree/flo-deb-lineage-17.1

The only hiccup I encounter is this command: git checkout origin/flo-deb-lineage-17.1

So instead, I manually create the local_manifests folder under the .repo folder. Then in local_manifests, I manually create roomservice.xml and paste in the contents from this link: https://github.com/followmsi/manifests/blob/flo-deb-lineage-17.1/local_manifests/roomservice.xml

 

[underflash]

I just followed the link in the OP: https://github.com/followmsi/manifests/tree/flo-deb-lineage-17.1

For testing will garb this https://androidfilehost.com/?fid=17248734326145688960

 

[ipdev]

Would be great you could guide how to build 17.1 from source. Thanks. Definitely time to downgrade at my end.

I just followed the link in the OP: https://github.com/followmsi/manifests/tree/flo-deb-lineage-17.1

The only hiccup I encounter is this command: git checkout origin/flo-deb-lineage-17.1

So instead, I manually create the local_manifests folder under the .repo folder. Then in local_manifests, I manually create roomservice.xml and paste in the contents from this link: https://github.com/followmsi/manifests/blob/flo-deb-lineage-17.1/local_manifests/roomservice.xml

Hi.

I have not run personal builds recently but, I am using followmsi's sources.
I was testing a few build time changes..

Long story short..
Use curl to pull roomservice.
ipdev99/local_manifests - [GitHub] - [lineage-17.1] - Link

You will have to adjust the curl command back to followmsi's branch.

https://raw.githubusercontent.com/followmsi/manifests/flo-deb-lineage-17.1/local_manifests/roomservice.xml

Cheers.

 

[poo706]

Hi.

I have not run personal builds recently but, I am using followmsi's sources.
I was testing a few build time changes..

Long story short..
Use curl to pull roomservice.
ipdev99/local_manifests - [GitHub] - [lineage-17.1] - Link

You will have to adjust the curl command back to followmsi's branch.

https://raw.githubusercontent.com/followmsi/manifests/flo-deb-lineage-17.1/local_manifests/roomservice.xml

Cheers.

Awesome, thanks for the info! Why do you maintain your own local manifest? It looks like it all points to follow's branches. Also, do you regularly build 17.1 when the source updates and post the zips?

 

[ipdev]

Awesome, thanks for the info! Why do you maintain your own local manifest? It looks like it all points to follow's branches. Also, do you regularly build 17.1 when the source updates and post the zips?

I do not remember what build change(s) I was testing on flo/deb 17.1

I gave up on the change(s) or followmsi included it.
So I pointed my local manifest back to followmsi's repo.
Might have been a local build change that was never pushed to github?​

I have a Pixel C (dragon) so I also include followmsi's repo(s) for Dragon in my local manifest.
--
I run personal builds but..
It has been awhile.
SourceForge - Link

Cheers.

 

[underflash]

A bit confused about flo-flox. Now running lineage-18.1-nightly-flox and used sysrepart-ultimate.zip - 4GB system, data is wiped, 'vendor' partition is added, 'recovery' is enlarged to 64MB in-place, flox compatible.

I would like to roll back and test lineage-17.1-20201216-UNOFFICIAL-flo.zip by followmsi. Do I need to do re-partition back to stock and then enlarge system partition with e.g. flo-deb_clamor_repartition_20201203.zip?

 

[bgolfer66]

Would be great you could guide how to build 17.1 from source. Thanks. Definitely time to downgrade at my end.

I would appreciate that as well!

 

[poo706]

I would appreciate that as well!

See post #3,889, or click this link.

https://xdaforums.com/t/rom-flo-deb-unofficial-lineageos-19-1-2022-06-16.3569067/post-87283363

 

[dg85]

hello,

I installed the following items:

-lineage-19.1-20220616-UNOFFICIAL-flo
-open_gapps-arm-12L-pico-20220705-UNOFFICIAL_MOD
-Magisk-v25.1
-ElementalX-N7-7.02-Twelve-20220215-AK3

with twrp-3.6.2_9-0-flo_followmsi

My nexus7 was already repartitioned

everything works fine (sometimes a problem with bluetooth)
The installation of elementalx is done without the AROMA installer. So I don't know how to modify the kernel parameters.
(I am trying to use the usb-otg+charge function)

if I manually modify the /sys/module/msm_otg/parameters/usbhost_charge_mode file by putting Y instead of N, it works as long as the nexus stays on.
At each restart, this file returns to its original value.

there was with version elementalx-n7-7.00 a configuration file etc/elementalx.conf which could be modified, but with version n7-7.02-twelve, I can't find this configuration file.

Thanks for reading and I hope someone finds a solution for me.

 

[followmsi]

LineageOS 19.1 - August 2022

lineage-19.1-20220818-UNOFFICIAL-flo.zip

lineage-19.1-20220818-UNOFFICIAL-deb.zip

Changes:
- Google security updates -> August 2022
- Patched system/netd to bring back Network traffic monitoring on older kernels
- Patched frameworks/base & Permissions to support microG
- Latest LineageOS changes for Android 12

Pls check first page for known issues and more information.

Tested flo build with opengapps pico and Magisk 25.2 !

As SDK level increased to version 32 we have to use new gapps for Android 12L.
Pls check latest gapps builds here .. https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics
Thanks to @ipdev for the opengapps packages !

Enjoy Android 12L

 

[MikiGry]

Has anyone been able to install rom (LOS 19.1)+gapps (nano or pico) with system_repart1380_20 ?
I was able to install ROM, but gapps gave error 70 :/
With system repart ultimate TWRP wasn"t able to mount anything and I had to go back to stock 6.0.1

 

[wstevew]

Looking for help.

I have a Nexus 7 flo Wi-FI 16GB

I have unlocked the bootloader, installed TWRP 3.6.2_9-0

Wiped everything in TWRP
Transfered the linage-19.1 zip file and gapps nano to the Internal storage

Rebooted to recovery

Install
Select linage-19.1 zip and swipe


Results in error below, How do I get it to Install?

I assume this is because the system partition is 827MB (812MB free).

So I attempt this guide

https://xdaforums.com/t/guide-repar...system-partition-extra-space-for-rom.3599907/

And got to the point where I rename system to unnamed1 and i got disconnected from adb. so i go back into parted and now I get "No device found"

So now I am not sure how to recover this.




------
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/linage-19.1-20220818-UNOFFICIAL-flo.zip'
Unmounting System...
Target: google/razor/flo/6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system Image
Updater progress ended with ERROR 1
Error Installing zip file '/sdcard/linage-19.1-20220818-UNOFFICIAL-flo.zip'
Updating partition details...
..done

 

[ipdev]

Has anyone been able to install rom (LOS 19.1)+gapps (nano or pico) with system_repart1380_20 ?
I was able to install ROM, but gapps gave error 70 :/
With system repart ultimate TWRP wasn"t able to mount anything and I had to go back to stock 6.0.1

Currently you will need just under a 1.3G system partition to install Lineage 19 on flo or deb.
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1336934400 # 1275M

History of updating the required system size.
followmsi - [GitHub] - flo/deb BoardConfigCommon - Line 89​

I use REPIT to (re)partition a few devices.
I might be a little bias though.

[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 7 (2013) [deb][flo]
xdaThread - Link​

As for installing Lineage and OpenGApps..
- Post # 3,856
- Post # 3,867

Cheers.

 

[ipdev]

Looking for help.

I have a Nexus 7 flo Wi-FI 16GB

I have unlocked the bootloader, installed TWRP 3.6.2_9-0

Wiped everything in TWRP
Transfered the linage-19.1 zip file and gapps nano to the Internal storage

Rebooted to recovery

Install
Select linage-19.1 zip and swipe


Results in error below, How do I get it to Install?

I assume this is because the system partition is 827MB (812MB free).

So I attempt this guide

https://xdaforums.com/t/guide-repar...system-partition-extra-space-for-rom.3599907/

And got to the point where I rename system to unnamed1 and i got disconnected from adb. so i go back into parted and now I get "No device found"

So now I am not sure how to recover this.

The install error was becuase the system partition was too small, Lineage would not fit.

I am not sure what kicked out your adb connection.

If you reboot into recovery does adb connect?
You will not have a system partition to mount so I would suggest (if you can) rename 22 back to system.
Then reboot into recovery again.

--

If that does not work..

Use k23m's RESTOCK or CROSS scripts.
They are Windows based so, you need to run it from a computer.

xdaThread - RESTOCK - Link

xdaThread - CROSS - Link

Cheers.

PS.
See my post above.
- Post # 3,901