[ROM][UNOFFICIAL][10] LineageOS 17.1 [deb][flo]

[k23m]

I installed this today but could not install gapps nano as there was error 70.
I had aex installed earlier with gapps nano and system was repartitioned. I also tried using the partition fix. Gapps Pico installs and works but nano does not get installed due to lack of storage space.
I tried installing digital wellbeing from the playstore but it does not work. Is there any way to install gapps nano on this ROM?
Thanks to all the developers for keeping this device alive.

I've tested the following components for you:

• sysrepart-max.zip (attached to the first post)
• lineage-17.1-20200918-UNOFFICIAL-flo.zip
• open_gapps-arm-10.0-nano-20200918.zip

With sysrepart-max there is no problem:

GApps Size Calculations
------------------------------------------------------------------
  TYPE  |         DESCRIPTION        |      SIZE |   TOTAL
        |         Current Free Space |    470732 |  470732
 Remove |             Existing GApps | +       0 |  470732
 Remove |             Obsolete Files | +       0 |  470732
 Remove |              cmsetupwizard | +       0 |  470732
 Remove |           extservicesstock | +     124 |  470856
 Remove |             extsharedstock | +      56 |  470912
 Remove |      packageinstallerstock | +    1944 |  472856
 Remove |                  provision | +       0 |  472856
Install |                       Core | -  181484 |  291372
Install |               batteryusage | -   10492 |  280880
Install |                    calsync | -    2544 |  278336
Install |                  googletts | -   35460 |  242876
Install |                     markup | -   10488 |  232388
Install |     packageinstallergoogle | -    1876 |  230512
Install |                     search | -  115964 |  114548
Install |                soundpicker | -    4684 |  109864
Install |                     speech | -   39128 |   70736
Install |                  wellbeing | -    8436 |   62300
        |               Buffer Space | -    9216 |   53084
------------------------------------------------------------------
                        Post Install Free Space |   53084

Here are sysrepart-max partitions:

Filesystem                Size      Used Available Use% Mounted on
/dev/block/mmcblk0p30
                         26.4G      1.3G     25.1G   5% /data
/dev/block/mmcblk0p30
                         26.4G      1.3G     25.1G   5% /sdcard
/dev/block/mmcblk0p22
                          1.3G    911.4M    459.7M  66% /system
/dev/block/mmcblk0p23
                          9.9M      4.1M      5.3M  43% /cache

Cheers!
:highfive:

 

[johndaog]

How to enable livedisplay?

This custom rom is fantastic
thank you very much.
I just wonder, is it possible to enable Livedisplay?

Please help

 

[abhiver]

I've tested the following components for you:
sysrepart-max.zip (attached to the first post)
lineage-17.1-20200918-UNOFFICIAL-flo.zip
open_gapps-arm-10.0-nano-20200918.zip


With sysrepart-max there is no problem:



Here are sysrepart-max partitions:


Cheers!
:highfive:

Thank you kind sir it worked. I flashed sysrepart-max on my already installed rom with pico installed then rebooted into recovery and then I successfully installed nano gapps. Thank you.

 

[k23m]

Thank you kind sir it worked. I flashed sysrepart-max on my already installed rom with pico installed then rebooted into recovery and then I successfully installed nano gapps. Thank you.

This is good news! While sysrepart-max can accommodate pico, nano and probably micro, here is a tip for installation of ANY GApps' app from ANY package...

• have a look at the Package-Comparison
• for example if you want GooglePay from the "Stock" variant but it will not install...
• get the "aroma" GApps and select only the above component for installation
• everything else should be installed later from the Play Store

I posted gapps log and screenshot from Stock Google Pay installation here.

:victory:

 

[johndaog]

Does anyone know how to enable livedisplay or night light?

 

[osm0sis]

This custom rom is fantastic
thank you very much.
I just wonder, is it possible to enable Livedisplay?

Does anyone know how to enable livedisplay or night light?

Known issue that it's broken, but you can work around it somewhat by editing the tunable file directly or using a tweak app. Tunable paths added to my previous post on it here:
https://forum.xda-developers.com/ne...ageos-17-1-t4038425/post83397915#post83397915

 

[michelfliegt]

Deb with gapps boots into recovery

Hi! As long as I only install the os (+ maybe magisk) all is well. When I add gapps the device shows the lineageos boot animation and then reboots directly into recovery

 

[steve1308]

I keep running into these USB settings problems.
IF I am in developer mode and go to "Default USB config" I have all the options file transfer. USB tether, etc.
but when I go to the basic "USB preferences" device settings, everything is greyed out. Same under Hotspot and tethering the "USB tethering" is greyed out.
Anyone know how to fix this? Thank You!!!
(I found a workaround to do what I needed, but this issue still exists)

 

[followmsi]

Hey! I noted this over in the AEX thread and reported it to @ripee but I think he ignored/dismissed me for some reason: https://forum.xda-developers.com/nexus-7-2013/development/rom-t3569067/post83166953#post83166953

The good news is the tunables do exist so you can modify them with root. I just moved into my new house and don't have my PC set up yet, but I'll hunt them down for you and add them to this post when I do. :good:

Hopefully it can be fixed in the device tree at some point. I'm still going to look into getting them working right in FKM with @franciscofranco too.

Edit: To edit them directly the locations are /sys/devices/platform/kcal_ctrl.0 /sys/devices/virtual/graphics/fb0/rgb
and it may be one, or the other, or both but connected depending on the kernel you're using.

Actually it was a missing overlay only .. no kernel changes required.
Tested on "my" kernel only .. but EX kernel should work the same way.

The sources have been updated .. for flo and deb devices.
https://github.com/followmsi/android_device_asus_flo/commit/ddaa78d1392cf359e3fcd35f2d62a00e4b57256f
https://github.com/followmsi/android_device_asus_deb/commit/e6bad90ca6de5cb06ee3ed8a95592f89a87c69dc

As @ripee is using "my" sources the next builds should include this change too.
Not sure about the @pitrus- (wickenberg) builds.

For demonstration I have uploaded my "private" build .. just for flo device only.

lineage-17.1-20200923-UNOFFICIAL-flo.zip

Changes:
- Fixed Night Light and Linage LiveDisplay.
- Increased media volume steps from 15 to 25
- Patched framework/base to support microG
- Patched framework/av to bring back "wifi-display" in android 10. (still not working)

Enjoy

 

[pitrus-]

Actually it was a missing overlay only .. no kernel changes required.

Tested on "my" kernel only .. but EX kernel should work the same way.



The sources have been updated .. for flo and deb devices.

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

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



As @ripee is using "my" sources the next builds should include this change too.

Not sure about the @pitrus- (wickenberg) builds.



For demonstration I have uploaded my "private" build .. just for flo device only.



lineage-17.1-20200923-UNOFFICIAL-flo.zip



Changes:

- Fixed Night Light and Linage LiveDisplay.

- Increased media volume steps from 15 to 25

- Patched framework/base to support microG

- Patched framework/av to bring back "wifi-display" in android 10. (still not working)



Enjoy

Great work! And as my builds use your source trees they will include the changes. [emoji106]

https://lineageos.wickenberg.nu/-manifests-/17/flo-deb.xml

 

[steve1308]

Is there anyway to update the com.android.webview?

 

[pitrus-]

Is there anyway to update the com.android.webview?

https://play.google.com/store/apps/details?id=com.google.android.webview

 

[johndaog]

Thank you to all who collaborate and work towards perfecting these ROMs. The work you guys do here on XDA is absolutely fantastic.

 

[Curtis7990]

Does this rom have always on feature?

 

[_slam]

Tried every version of twrp (3.4 -3.3) and I am still getting the "Updater process ended with ERROR: 7" when trying install lineage-17.1-20200925-UNOFFICIAL-flo.zip. Not sure what the issue is???

My setup:
Production Name - flo
Variant - flo 32G
HW Version - rev_e
Bootloader version - FLO-04.08
Carrier Info - None (wifi)
Serial Number - xxxxxx
Signing - yes
Secure Boot - enable

any new paths to get 10 on this would be greatly welcomed
Lock State - unlocked

 

[DCvan]

Tried every version of twrp (3.4 -3.3) and I am still getting the "Updater process ended with ERROR: 7" when trying install lineage-17.1-20200925-UNOFFICIAL-flo.zip. Not sure what the issue is???

My setup:
Production Name - flo
Variant - flo 32G
HW Version - rev_e
Bootloader version - FLO-04.08
Carrier Info - None (wifi)
Serial Number - xxxxxx
Signing - yes
Secure Boot - enable

any new paths to get 10 on this would be greatly welcomed
Lock State - unlocked

Please read OP need to increase partition inorder to work.
I used @followmsi sysrepart 1280_120 https://forum.xda-developers.com/nexus-7-2013/development/rom-t3569067
Credit to @k23m

 

[_slam]

Please read OP need to increase partition inorder to work.
I used @followmsi sysrepart 1280_120 https://forum.xda-developers.com/nexus-7-2013/development/rom-t3569067
Credit to @k23m

Thanks sysrepart.zip worked, and got 10 up but now getting an GApp error "error 20"

edit: resolved, had to use the nano GApps

 

[DCvan]

Thanks sysrepart.zip worked, and got 10 up but now getting an GApp error "error 20"

Not sure about error 20. I used Gapps pico and that's working, but during setup can not use Google backup too restore. Manually download apps from Play store.

 

[_slam]

Not sure about error 20. I used Gapps pico and that's working, but during setup can not use Google backup too restore. Manually download apps from Play store.

sorted it out, had to use a smaller download package nano or pico, thanks for the help.

 

[acidboot3r]

Hey All,

I have a Nexus 7 2012 edition and to my surprise it's currently running LineageOS 16, Android 9. I don't know how that ended up happening since the Nexus 7 2012 is meant to support roms above Android 8 at most. I suspect I had flashed an Android 9 ROM for Nexus 7 2013 a long time ago. Anyways it's currently running fine with no issues. I was wondering if flashing LineageOS 17 is worth doing considering Lineage16 runs fine?