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

[MikiGry]

@followmsi

New day ,new issue. I'm staring to feel bad for reporting more and more of them

Today i've discovered that BT died. I started to suspect something is going on after seeing "Bluetooth stopped working" message a few times after unlocking the screen (BT wasn't enabled). So i tried to turn it on, but it doesn't turn on. Reboot doesn't fix the issue


Logcat
Logcat indeed cofirmed something is wrong. System is trying to turn on BT 8 times. After that it it times out and statusbar toogle turns to off state again

dmesg
Dmesg reports that something is wrong as well. This section caught my eye:

Spoiler

[32m[ 792.280853] ←[33mtype=1400 audit(1661970775.916:924)←[0m: avc: denied { open } for comm="bt_stack_manage" name="ubject_r:vendor_default_prop:s0" dev="tmpfs" ino=6668 scontext=u:r:bluetooth:s0 tcontext=ubject_r:vendor_default_prop:s0 tclass=file permissive=1
←[32m[ 792.281372] ←[33mtype=1400 audit(1661970775.916:925)←[0m: avc: denied { getattr } for comm="bt_stack_manage" path="/dev/__properties__/ubject_r:vendor_default_prop:s0" dev="tmpfs" ino=6668 scontext=u:r:bluetooth:s0 tcontext=ubject_r:vendor_default_prop:s0 tcl
ass=file permissive=1
←[32m[ 792.619567] ←[33mtype=1400 audit(1661970776.256:926)←[0m: avc: denied { open } for comm="crash_dump32" name="ubject_r:vendor_default_prop:s0" dev="tmpfs" ino=6668 scontext=u:r:crash_dump:s0 tcontext=ubject_r:vendor_default_prop:s0 tclass=file permissive=1
←[32m[ 792.619567] ←[33maudit←[0m: audit_lost=728 audit_rate_limit=5 audit_backlog_limit=64
←[32m[ 792.619598] ←[33maudit←[31m: rate limit exceeded
←[32m[ 792.620330] ←[33mtype=1400 audit(1661970776.256:927)←[0m: avc: denied { getattr } for comm="crash_dump32" path="/dev/__properties__/ubject_r:vendor_default_prop:s0" dev="tmpfs" ino=6668 scontext=u:r:crash_dump:s0 tcontext=ubject_r:vendor_default_prop:s0 tclas
s=file permissive=1
←[32m[ 792.620635] ←[33mtype=1400 audit(1661970776.256:928)←[0m: avc: denied { open } for comm="crash_dump32" name="ubject_r:exported_bluetooth_prop:s0" dev="tmpfs" ino=6506 scontext=u:r:crash_dump:s0 tcontext=ubject_r:exported_bluetooth_prop:s0 tclass=file permissi
ve=1


Even emonticons see that something is wrong

[/SPOILER]

Looks like system isn't able to get acces to something


However i'm no expert in reading and interpreting logcats and dmesg so I attach full versions of both of them

@followmsi
Little followup on this one. Today I discovered that I had Bluetooth gebeldorch enabled in developer setting. After disabling it it kinda started to work. Now it does something like that:
BT turns on for a split second (according to statusbar toggle and setting) amd turns off again. It does that a few times (sometimes giving "Bluetooth has stopped error dialog" mid way) and finally turns on and stays on. I haven"t tried connecting with any device or sending files yet.

Logcat revealed a cycle:
1.Errors
2. BT has died
3. Scheduling a bluetooth restart
4. Back to the first point

 

[fattox]

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.

[ip@lost flo_deb]$ adb sideload lineage-19.1-20221012-UNOFFICIAL-deb.zip
Total xfer: 0.98x
[ip@lost 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.

[ip@lost flo_deb]$ adb install ~/github/Magisk-build/magisk-snapshot/app-debug.apk
Performing Streamed Install
Success
[ip@lost 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.

[ip@lost 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)
[ip@lost flo_deb]$ mv magisk_patched-25205_ZpvJZ.img magisk_25205_boot-lineage-19.1-20221012-deb.img
[ip@lost flo_deb]$ adb reboot bootloader
[ip@lost 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.

[ip@lost 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)
[ip@lost 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)
[ip@lost 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)
[ip@lost 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.

---

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.

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.

It worked! The very last part was the solution I didn't know!
Thank you sooooo much

 

[fattox]

It worked! The very last part was the solution I didn't know!
Thank you sooooo much

Do you have any workaround also for making work the Google Assistant? It doesn't work when calling for it and the setting says "it's not available for this device"

 

[itsAlphaFox]

Does anyone know if it is possible to get an overclock working on this ROM?

 

[bernascoginger]

I tried installing the new OS on my NEXUS 7 2013(dep). I had the message " UPDATER PROCESS ENDED WITH ERROR: 1". i have attached a copy of screenshot to see details. Please help me to complete installation

 

[bernascoginger]

I downloaded and tried installing the new Lineage OS 19 on my NEXUS 7 2013(dep). I had the message "UPDATE PROCESS ENDED WITH ERROR:1". i have attached screen shot below. Please help me to complete install

 

[AlesUlrych]

I downloaded and tried installing the new Lineage OS 19 on my NEXUS 7 2013(dep). I had the message "UPDATE PROCESS ENDED WITH ERROR:1". i have attached screen shot below. Please help me to complete install

I have the same problem with Flo, and so far I have not been able to solve it. I wrote about it on the previous page. The only thing that works for me is reverting to version lineage-19.1-20220818-UNOFFICIAL-flo.zip

All the advice ipdev gave me hasn't helped so far.

 

[AlesUlrych]

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.

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.

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.

Unfortunately, I tried your tips, but I didn't make any progress. So I went back to lineage-19.1-20220818-UNOFFICIAL-flo.zi

 

[bernascoginger]

i am on android 4.4.4. pop up message to download and install android 5.0.2 keeps on appearing on my screen. after downloading, the installation goes on all day and never gets to completion. is there a higher an available version i can download and install on my device?

 

[CityKev]

i am on android 4.4.4. pop up message to download and install android 5.0.2 keeps on appearing on my screen. after downloading, the installation goes on all day and never gets to completion. is there a higher an available version i can download and install on my device?

Might be a sledgehammer to crack a nut but this tool has been very useful for me. Install the persist fix using TWRP before then using the Restock tool to get you to 6.0.1.

Edit: it would help if I included the link

https://xdaforums.com/t/restock-sto...r-and-reset-including-usb-driver-fix.3995981/

 

[DVDK94]

I have the same problem with Flo, and so far I have not been able to solve it. I wrote about it on the previous page. The only thing that works for me is reverting to version lineage-19.1-20220818-UNOFFICIAL-flo.zip

All the advice ipdev gave me hasn't helped so far.

I had the same problem (error 1 when installing `lineage-19.1-20221012-UNOFFICIAL-flo.zip`), but I have finally solved it. After downgrading from the official TWRP 3.7 build to the TWRP build 3.6.2 from @followmsi the installation was successful.

@bednim @AlesUlrych @bernascoginger

 

[bernascoginger]

I had the same problem (error 1 when installing `lineage-19.1-20221012-UNOFFICIAL-flo.zip`), but I have finally solved it. After downgrading from the official TWRP 3.7 build to the TWRP build 3.6.2 from @followmsi the installation was successful.

@bednim @AlesUlrych @bernascoginger

i used TWRP build 3.6.0_9-1 and it failed. can you send me link to download TWRP 3.7 and a more lower version to try

 

[DVDK94]

i used TWRP build 3.6.0_9-1 and it failed. can you send me link to download TWRP 3.7 and a more lower version to try

Official TWRP builds for flo: https://dl.twrp.me/flo/
Official TWRP builds for deb: https://dl.twrp.me/deb/
TWRP build by @followmsi for flo and deb: https://drive.google.com/drive/folders/18JCSbs0IglAWR2YnV5lI2Eni_ZQ6AyPl

 

[AlesUlrych]

I had the same problem (error 1 when installing `lineage-19.1-20221012-UNOFFICIAL-flo.zip`), but I have finally solved it. After downgrading from the official TWRP 3.7 build to the TWRP build 3.6.2 from @followmsi the installation was successful.

@bednim @AlesUlrych @bernascoginger

But I use TWRP 3.6.2 from followmsi.
I've gone back to the last working build and will stick with that for now. Why the new ones aren't working I don't know, I'll stick with the last working one for now and possibly try the new ones to see if any of them work again.

 

[MikiGry]

Possible solution for people who can"t clean install 20221012 build but have zero problems with older ones.

Install older one and dirty flash over it to the newest one

 

[comatoseEnigma]

this wont work for mako nexus 4 would it?

 

[curiousde2002]

Hi guys anybody having performance problems?
My Deb is lagging most of the time, so that it's hardly usable.

What I did:

Coming from LOS 17.1
I had run ipdev's repit script with system wipe,
Rebooted back into recovery
Wiped data, system, dalvik and cache
Rebooted back into recovery
Flashed `lineage-19.1-20221012-UNOFFICIAL-deb.zip` and open gapps arm pico
Boot into system and did initial setup
Rebooted back into recovery and flashed magisk 25.2

All these actions worked fine, no errors.

I tried another install but only with system, dalvik and cache wipe, but no improvement.

I'll do another clean install if I don't get any other suggestion from you

Thank you very much in advance !

 

[MikiGry]

@followmsi

I"ve noticed that there is a repetetive error sequence which appeares in logcat during normal use. It seems like it can be triggered by:
- pulling down notification bar (and touching/rearranging toggles as well i guess)
- minimising apps
- exiting apps using navigation bar (swipe gestures in my case)

All these things are conneted to one app - system.ui

Is it possible that system.ui is causing the whole system to lag after some time (due to these constant errors) ?
Attaching a logcat of said error block from attemts to pull down statusbar (E libproces group one is the one im"m taking about)

 

[ipdev]

I installed LineageOS 19-20220904-UNOFFICIAL-a3y17lte on SM-A320FL (a3y17lte) Samsung phone. Everyting is working like charm but when calling the receiver hears echo while he or she is speaking. Is there any known solution to fix this problem? Phone is not rooted and Developer options are disabled.

Sorry but flo/deb are tablets not phones so, no help will come from this thread.

I see the thread for rom was closed and a new one was not yet created.
[CLOSED][ROM][12][BETA] LineageOS 19.1 for Samsung Galaxy A3 2017 (a3y17lte) (SM-A320F)
[xdaThread] - Link

Better to ask in your device Q&A forum.
Samsung Galaxy A3, A5, A7 (2017) Questions & Answer
[xdaForum] - Link

I have asked that our posts be moved and/or deleted from this thread.

Cheers.

 

[Chapmans35]

@

followmsi​

Really appreciate all the efforts with this rom and the new life it brings to my nexus 7. Is there a new monthly update due?