[ROM][flo|deb][UNOFFICIAL][LineageOS 19.1] -> 2022-10-12

Search This thread

fattox

Senior Member
Jul 5, 2011
158
13
I tried so many times and always end up with an issue installing the gapps. After so many hours lost, now I think I'm going to live without Google until a new solution comes up
 

dogansan

Member
Sep 2, 2022
16
2
I had the same problem. Google play store updates were stuck at "pending" status, as if it was waiting for a connection even though the wifi was active. I reinstalled and it seems to be working now...unfortunately I can't remember exactly what I did to fix it but it involve reflashing the ROM (did I boot to the ROM before installing Gapps??; did I do a dirty reflash without wiping??)
I overcame this issue by updating the apps in Google Play's page , then disabling Android Auto and enable it again. Now, the blue notification dissapeared
 

followmsi

Senior Member
Oct 10, 2013
4,226
13,146
LineageOS 19.1 - October 2022

lineage-19.1-20221012-UNOFFICIAL-flo.zip

lineage-19.1-20221012-UNOFFICIAL-deb.zip


Changes:

- Google security updates -> October 2022
- Increased ZRAM size and swappiness
- 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 :p
 

AlesUlrych

Senior Member
Jan 20, 2019
62
24
Hi all, I have flashed repit from lanchon and it went well - partition seems to be resized but when I try to flash los19.1 I get this error (image) could anyone please help?

Thanks!View attachment 5719987
I have the same problem. Even Factory Reset didn't help me. Today I tried to install build lineage-19.1-20221012-UNOFFICIAL-flo.zip and with the same error.

The last working version for me is lineage-19.1-20220818-UNOFFICIAL-flo.zip

Anyone have any idea what might be causing this?
 

AlesUlrych

Senior Member
Jan 20, 2019
62
24
Hi all, I have flashed repit from lanchon and it went well - partition seems to be resized but when I try to flash los19.1 I get this error (image) could anyone please help?

Thanks!View attachment 5719987
I have the same problem. Even Factory Reset didn't help me. Today I tried to install build lineage-19.1-20221012-UNOFFICIAL-flo.zip and with the same error.

The last working version for me is lineage-19.1-20220818-UNOFFICIAL-flo.zip

Anyone have any idea what might be causing this?

Thanks a lot for any advice or idea.
 

Attachments

  • IMG_20221013_092229.jpg
    IMG_20221013_092229.jpg
    847.4 KB · Views: 93
  • IMG_20221013_092239.jpg
    IMG_20221013_092239.jpg
    889.1 KB · Views: 94
  • IMG_20221013_092652.jpg
    IMG_20221013_092652.jpg
    859.2 KB · Views: 95
Last edited:
  • Like
Reactions: galaxys

ipdev

Recognized Contributor
Feb 14, 2016
2,045
1
3,906
Google Nexus 10
Nexus 7 (2013)
Hi,
IS thaere a way to get dt2w please?
Thanks you
It is supported in the kernel, you just have to activate it.

Using a kernel manager to enable DT2W.
Post 2,159 - Link
I have not check these settings in a while so, I am not sure if this is still accurate.

I use a Magisk module to enable it.
Post 3,339 - Link
Second half of the post.

Cheers. :cowboy:
 
  • Like
Reactions: G0rg0ne and galaxys

ipdev

Recognized Contributor
Feb 14, 2016
2,045
1
3,906
Google Nexus 10
Nexus 7 (2013)
Hi all, I have flashed repit from lanchon and it went well - partition seems to be resized but when I try to flash los19.1 I get this error (image) could anyone please help?

Thanks!View attachment 5719987

I have the same problem. Even Factory Reset didn't help me. Today I tried to install build lineage-19.1-20221012-UNOFFICIAL-flo.zip and with the same error.

The last working version for me is lineage-19.1-20220818-UNOFFICIAL-flo.zip

Anyone have any idea what might be causing this?
Save the TWRP log file and see what is causing the issue.

It could be a bad file transfer (corrupt file) so, double check it against the sha256sum.

Make sure the (re)partitioning worked.
Double check the partition sizes using the df command.
You will need to mount the system partition first using TWRP.
TWRP Home Screen -> Mount (select system) return to home.

Use adb shell or open a Terminal window to run the df command.
TWRP Home Screen -> Advanced -> Terminal
df -h
To close the terminal use the exit command.

Example(s) showing system size as 1.4G.

Formatted, no rom (system) installed.
Code:
Filesystem                Size      Used Available Use% Mounted on
tmpfs                   903.7M    164.0K    903.5M   0% /dev
tmpfs                   903.7M     24.0K    903.7M   0% /tmp
/dev/block/mmcblk0p30
                         12.2G    159.2M     12.1G   1% /data
/dev/block/mmcblk0p30
                         12.2G    159.2M     12.1G   1% /sdcard
/dev/block/mmcblk0p23
                         15.7M      4.1M     11.7M  26% /cache
/dev/block/mmcblk0p22
                          1.4G     25.7M      1.4G   2% /system
With rom (system) and GApps installed.
Code:
Filesystem                Size      Used Available Use% Mounted on
tmpfs                   903.7M    164.0K    903.5M   0% /dev
tmpfs                   903.7M     28.0K    903.7M   0% /tmp
/dev/block/platform/msm_sdcc.1/by-name/userdata
                         12.2G    713.4M     11.3G   6% /data
/dev/block/platform/msm_sdcc.1/by-name/userdata
                         12.2G    713.4M     11.3G   6% /sdcard
/dev/block/platform/msm_sdcc.1/by-name/cache
                         15.7M      4.2M     11.6M  27% /cache
/dev/block/platform/msm_sdcc.1/by-name/system
                          1.4G      1.3G    105.0M  93% /system_root
/dev/block/platform/msm_sdcc.1/by-name/system
                          1.4G      1.3G    105.0M  93% /system
Cheers. :cowboy:
 
  • Like
Reactions: G0rg0ne and galaxys

Alyonas_boy

Member
Nov 10, 2016
45
13
Russia
just updated to lineage-19.1-20221012-UNOFFICIAL-deb.zip and the performance is the same. Is there anyone running this Android 12 ROM and having good performance? Perhaps something is wrong with my Device? I have Android 10 Lineagos running on my kids Nexus 10's that are only Dual Core CPU's and they run super quick. And yet here is this 2013 Nexus 7 with a Quad core that grinds to a halt on Android 12.
 

AlesUlrych

Senior Member
Jan 20, 2019
62
24
Save the TWRP log file and see what is causing the issue.

It could be a bad file transfer (corrupt file) so, double check it against the sha256sum.

Make sure the (re)partitioning worked.
Double check the partition sizes using the df command.
You will need to mount the system partition first using TWRP.
TWRP Home Screen -> Mount (select system) return to home.

Use adb shell or open a Terminal window to run the df command.
TWRP Home Screen -> Advanced -> Terminal
df -h
To close the terminal use the exit command.

Example(s) showing system size as 1.4G.

Formatted, no rom (system) installed.
Code:
Filesystem                Size      Used Available Use% Mounted on
tmpfs                   903.7M    164.0K    903.5M   0% /dev
tmpfs                   903.7M     24.0K    903.7M   0% /tmp
/dev/block/mmcblk0p30
                         12.2G    159.2M     12.1G   1% /data
/dev/block/mmcblk0p30
                         12.2G    159.2M     12.1G   1% /sdcard
/dev/block/mmcblk0p23
                         15.7M      4.1M     11.7M  26% /cache
/dev/block/mmcblk0p22
                          1.4G     25.7M      1.4G   2% /system
With rom (system) and GApps installed.
Code:
Filesystem                Size      Used Available Use% Mounted on
tmpfs                   903.7M    164.0K    903.5M   0% /dev
tmpfs                   903.7M     28.0K    903.7M   0% /tmp
/dev/block/platform/msm_sdcc.1/by-name/userdata
                         12.2G    713.4M     11.3G   6% /data
/dev/block/platform/msm_sdcc.1/by-name/userdata
                         12.2G    713.4M     11.3G   6% /sdcard
/dev/block/platform/msm_sdcc.1/by-name/cache
                         15.7M      4.2M     11.6M  27% /cache
/dev/block/platform/msm_sdcc.1/by-name/system
                          1.4G      1.3G    105.0M  93% /system_root
/dev/block/platform/msm_sdcc.1/by-name/system
                          1.4G      1.3G    105.0M  93% /system
Cheers. :cowboy:

Cheksum LineageOS on the computer is fine, I uploaded it to the tablet as usual via bluetooth, but I don't know how to verify that it is also fine on the tablet. However, I've never had a problem with it. As I said, the penultimate version works for me without any problems.

I am sending the log and a photo of the partitioned disk.
 

Attachments

  • IMG_20221014_063846.jpg
    IMG_20221014_063846.jpg
    1.4 MB · Views: 52
  • recovery.zip
    6.5 KB · Views: 11

ipdev

Recognized Contributor
Feb 14, 2016
2,045
1
3,906
Google Nexus 10
Nexus 7 (2013)
<SNIP>
I am sending the log and a photo of the partitioned disk.
Your picture of the df command, does not show system.
From the userdata and cache sizes it looks like your system should be 1.4G but...
If you mounted the system partition before running the df command, then your system partition is messed up.

Cheksum LineageOS on the computer is fine, I uploaded it to the tablet as usual via bluetooth, but I don't know how to verify that it is also fine on the tablet. However, I've never had a problem with it. As I said, the penultimate version works for me without any problems.
<SNIP>
Copy both the rom and checksum file to the device.
Use adb shell or the TWRP terminal and run the sha256sum command.
sha256sum -c NameOfFile.FileExtention.sha256sum

Example:
Code:
~ # cd /sdcard/
/sdcard # ls -la
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
drwxrwx---    3 root         root              4096 Oct 15 23:56 .
drwxr-xr-x   24 root         root                 0 Oct 16 00:01 ..
drwxrwxrwx    2 root         root              4096 Oct 14 00:51 TWRP
-rw-rw-r--    1 root         root         527290810 Oct 15 23:56 lineage-19.1-20221012-UNOFFICIAL-flo.zip
-rw-rw-r--    1 root         root               107 Oct 15 23:56 lineage-19.1-20221012-UNOFFICIAL-flo.zip.sha256sum
/sdcard # sha256sum -c lineage-19.1-20221012-UNOFFICIAL-flo.zip.sha256sum
lineage-19.1-20221012-UNOFFICIAL-flo.zip: OK
/sdcard #
Tab completion is available so you do not have to type it all in. 🙃
In the TWRP terminal..
The top line of the keyboard will have
Ctrl Esc Tab (and the left, down, up and right arrows).
sha256sum -c li[ICODE] press Tab and you will be at [ICODE]sha256sum -c lineage-19.1-20221012-UNOFFICIAL-flo.zip
so you just have to add the .sha256sum and press enter.
or just .s and press Tab again. ;)

---

From your log file.
Code:
 writing 1024 blocks of new data
 writing 1024 blocks of new data
Decompression failed with BLOCK_LENGTH_2
missing 33144 bytes of new data
failed to execute command [new 2,92396,93420]
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 1

Should look more like this.
Code:
 writing 1024 blocks of new data
 writing 157 blocks of new data
  zeroing 1024 blocks
  zeroing 1024 blocks
  zeroing 1024 blocks
  zeroing 1024 blocks
  zeroing 1024 blocks
  zeroing 742 blocks
wrote 294787 blocks; expected 294787

Looks like you wiped (formatted) partitions just before installing.
This has given errors in the past for me on some devices.

If I format and/or wipe partitions, I reboot back into recovery before installing a rom.
It was years ago and it has just become natural for me to reboot recovery after formatting or wiping partitions.​

Cheers. :cowboy:
 

fattox

Senior Member
Jul 5, 2011
158
13
Hello @ipdev I've finally managed to install the latest pico Gapps, thanks to the great and patient work of @k23m.
BUT after booting for the first time to the Play Store and signing in, I keep getting "no connection" and "connection expired".
I even tried to install the WebView... thinking it was missing but it didn't help.

Do you have any idea on how to help?!
After so much work I would really succeed with it! Thank you for your help
 

MikiGry

Senior Member
Oct 2, 2013
1,590
381
Nexus 7 (2013)
Samsung Gear S3
I still havent updated the tablet from first relase of 19.1 because my usb port is acting up again :/

As propably everybody noticed, as days go tablet is getting slower and slower which requires to perform fstrim to make it usable again. Followmsi also mentioned that Swap make is slow down after some time for some reason.
Our EMMC chips aren"t the best. Using ZRAM in theory should give more RAM and better operation, but given the state of our memory chips - it creates more problems, as RAM becames (partially) slow as well.
So my theory is we should discorage the system for using swap and leave it as emergency or even disable it.

So to test this theory, right now im testing the second option - swappines set to 0. Lets see how it goes
 
  • Like
Reactions: ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,045
1
3,906
Google Nexus 10
Nexus 7 (2013)
I still havent updated the tablet from first relase of 19.1 because my usb port is acting up again :/

As propably everybody noticed, as days go tablet is getting slower and slower which requires to perform fstrim to make it usable again. Followmsi also mentioned that Swap make is slow down after some time for some reason.
Our EMMC chips aren"t the best. Using ZRAM in theory should give more RAM and better operation, but given the state of our memory chips - it creates more problems, as RAM becames (partially) slow as well.
So my theory is we should discorage the system for using swap and leave it as emergency or even disable it.

So to test this theory, right now im testing the second option - swappines set to 0. Lets see how it goes
For the record.
ZRAM was removed from the flo builds.
LineageOS - [github] - [android_device_asus_flo] - commit

ZRAM was added back into the flox builds.
LineageOS - [github] - [android_device_asus_flox] - commit

Flox builds are a bit different so, might work better using ZRAM? :unsure:

Cheers. :cowboy:
 

ipdev

Recognized Contributor
Feb 14, 2016
2,045
1
3,906
Google Nexus 10
Nexus 7 (2013)
Hello @ipdev I've finally managed to install the latest pico Gapps, thanks to the great and patient work of @k23m.
BUT after booting for the first time to the Play Store and signing in, I keep getting "no connection" and "connection expired".
I even tried to install the WebView... thinking it was missing but it didn't help.

Do you have any idea on how to help?!
After so much work I would really succeed with it! Thank you for your help
Some GApps might be needed to be updated before you can configure you Google account.

I just did a clean flash on my deb.

I go a little overboard when clean flashing. 🙃
I wipe and format using fastboot then install and boot into TWRP.
If needed (some devices) I format data again in TWRP.
Reboot into recovery (TWRP) wipe all and reboot into recovery (TWRP) again.​

I use adb sideload to install.
Code:
[[email protected] flo_deb]$ adb sideload lineage-19.1-20221012-UNOFFICIAL-deb.zip
Total xfer: 0.98x
[[email protected] flo_deb]$ adb sideload /ip/opengapps/20220705/open_gapps-arm-12L-pico-20220705-UNOFFICIAL_MOD.zip 
Total xfer: 1.33x
Then boot into system.

Skip though the initial setup (offline).
  • Correct Time Zone.
  • Turn off all but but basic location.

I prefer to do as much as I can before going online.

Using adb, I install Magisk and push the stock boot image to the device.
Code:
[[email protected] flo_deb]$ adb install ~/github/Magisk-build/magisk-snapshot/app-debug.apk
Performing Streamed Install
Success
[[email protected] flo_deb]$ adb push boot-lineage-19.1-20221012-deb.img /sdcard/Download/
boot-lineage-19.1-20221012-deb.img: 1 file pushed, 0 skipped. 21.7 MB/s (7208960 bytes in 0.317s)
Patch the stock boot image and pull the patched boot image.
Then rename it (so I know what it is) and test boot it.
Code:
[[email protected] flo_deb]$ adb pull /sdcard/Download/magisk_patched-25205_ZpvJZ.img
/sdcard/Download/magisk_patched-25205_ZpvJZ.img: 1 file pulled, 0 skipped. 14.0 MB/s (7462912 bytes in 0.510s)
[[email protected] flo_deb]$ mv magisk_patched-25205_ZpvJZ.img magisk_25205_boot-lineage-19.1-20221012-deb.img
[[email protected] flo_deb]$ adb reboot bootloader
[[email protected] flo_deb]$ fastboot boot magisk_25205_boot-lineage-19.1-20221012-deb.img
Sending 'boot.img' (7288 KB)                       OKAY [  0.280s]
Booting                                            OKAY [  0.024s]
Finished. Total time: 0.324s
If it worked, I then use the Direct install option in Magisk and reboot.
Configure Magisk (enable Zygisk) and reboot.
Then push the main modules I use to the device.
Code:
[[email protected] modules]$ adb push ZipBin-v3.zip /sdcard/Download/
ZipBin-v3.zip: 1 file pushed, 0 skipped. 1.4 MB/s (94435 bytes in 0.063s)
[[email protected] modules]$ adb push dt2w-v2.zip /sdcard/Download/
dt2w-v2.zip: 1 file pushed, 0 skipped. 0.0 MB/s (1906 bytes in 0.060s)
[[email protected] modules]$ adb push osm0sis/*.zip /sdcard/Download/
Busybox_for_Android_NDK-1.34.1(13412).zip: 1 file pushed, 0 skipped. 17.3 MB/s (9908054 bytes in 0.547s)
Nano_for_Android_NDK-6.2(6200).zip: 1 file pushed, 0 skipped. 78.1 MB/s (379579 bytes in 0.005s)
2 files pushed, 0 skipped. 12.3 MB/s (10287633 bytes in 0.798s)
[[email protected] modules]$ adb push ~/github/usnf/mk_zip/usnf-231c.zip /sdcard/Download/
/home/ip/github/usnf/mk_zip/usnf-231c.zip: 1 file pushed, 0 skipped. 2.3 MB/s (96631 bytes in 0.040s)
Install them and reboot.
Connect to WiFi and let Google update.
You might have to start "Finish Setting up your Device" for PlayStore to update.
When you get to adding you account (You might not be able to skip adding an account), close out.
Then long press PlayStore and select "My Apps" it will check for updates, select all.

Once updated (PlayServices, AA and Speech), you should be able to sign into your account.
Normally I sign in before restarting "Finish Setting up your Device" since the skip option is not always available.

I skipped loging in and instead continued "Finishing Setting up you Device" and see the skip option is available.
So I spiked it and continued though, then added my account under Setting -> Google.
Normally I just add it under Passwords & accounts (so I can kill the sync right away).​

Not sure what else to say. :unsure:

---

This was the over complicated way I do clean flash a rom.
Actually not the complicated, it takes more to explain it than it does to do it.

Maybe you can see something that helps.

Cheers. :cowboy:

PS.
I need to check the installed (update) versions from Google before signing in.
Maybe we need to include them in OpenGApps instead of the default version(s) used.
 
  • Like
Reactions: G0rg0ne and MikiGry

MikiGry

Senior Member
Oct 2, 2013
1,590
381
Nexus 7 (2013)
Samsung Gear S3
For the record.
ZRAM was removed from the flo builds.​
LineageOS - [github] - [android_device_asus_flo] - commit
ZRAM was added back into the flox builds.​
LineageOS - [github] - [android_device_asus_flox] - commit

Flox builds are a bit different so, might work better using ZRAM? :unsure:

Cheers. :cowboy:
Flox is just a repartitioned flo with special recovery which accepts flox build only aa far as I know.

II still testing how flo work with 0 ZRAM (and I/O read ahead buffer increased to 512kb -- don"t do that unless you want up warm your hands :p) with first build of LOS 19.1. So far:

- RAM is now usually filled almost to the brim - 30-60mb free (according to disk info) (up to 0,5GB with empty recent apps menu) incorrect ram usage calculation methode was used. 1gb free with recent apps menu empty, ~300mb before it starts to slow down and LMK kick in - this makes much more sense
- Multitasking is still possible
- PDF files are easier for the tablet to process (it takes less time to sharpen the image after zooming in or out)
- Youtube Vanced loads up video tubnails faster
- Brave browser lauches faster
- Low memory killer values may need some tuning (in starts to kick in when it"s less then ~300mb free, i thing we can fill the ram a little more)
- It takes longer for Google keyboard to show up (or maybe it was its latest update which made it even heaver ?)

@ipdev
Unfortunately I had to end the test. It seems that 2gb of ram is not enough for stable operations. It looks like apps became much more RAM hungry lately or there are some RAM leaks. Google keyboard + official xda app (it can eat up to 0,5GB of RAM !!!) or a youtube notification were enough to make tablet unusable :/
New approach - back to 512mb swap (default value for the first build) but with decreased swappiness value (to make sure system uses swap as a emergency option, rather then just free extra ram)
 
Last edited:
  • Like
Reactions: ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,045
1
3,906
Google Nexus 10
Nexus 7 (2013)
Flox is just a repartitioned flo with special recovery which accepts flox build only aa far as I know.

II still testing how flo work with 0 ZRAM (and I/O read ahead buffer increased to 512kb) with first build of LOs 19.1. So far:

- RAM is now usually filled almost to the brim - 30-60mb free (according to disk info) (up to 0,5GB with empty recent apps menu)
- Despite that multitasking is still possible (not sure how :p)
- PDF files are easier for the tablet to process (it takes less time to sharpen the image after zooming in or out)
- Youtube Vanced load up video tubnails faster
- Brave browser lauches faster
- Low memory killer values may need some very fine tuning (as border between RAm overfill and lack of multitasking is very thin)
- It takes longer for Google keyboard to show up (or maybe it was its latest update which made it even heaver ?)
Might be a little more different. ;)
The (re)partitioning includes creating and using a separate vendor partition.
Following UA's approach. Not sure if flox vendor is stock or includes modifications.
Official flox builds are enforcing.

---

When flox and followmsi's flo branch where mostly inline, I "borrowed" some SELinux permissions from flox.
Still had issues when I tested enforcing flo builds. 🙃
Oddities with camera come to mind along with a few other things that I never figured out.

Followmsi's kernel also includes some extras that are not in flox/debx kernel.
Debx was never released for some reason, never looked into why.

Followmsi reverted vmalloc back to stock value.
- [github] - [android_device_asus_flo] - commit
I questioned vmalloc for a while and was running test builds with it reverted.
I did not see an improvement by keeping it or a regression by removing it on Android 6 (API 23) and above.
Removing it seemed to have a positive effect ??

I asked a few times (in different threads) if there was any reason to keep it and no one answered. 🙃
The last time I asked ??
[ROM][OFFICIAL] LineageOS 17.1 weeklies for Nexus 7 2013 (flox) - [xdaThread] - Post # 221

---

Looking forward to your experience and findings. 🙂 👍

Cheers. :cowboy:
 
  • Like
Reactions: G0rg0ne and MikiGry

Top Liked Posts