• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][enchilada][11] LineageOS 18.1

Search This thread

lamahgra

Senior Member
Jan 27, 2008
106
54
since the last 10 updates "WLAN" function is broken....

had gone back to OxyOS11 - WLAN works out of the box

oem unlock
twrp 3.5.2_9-0
full wipe
install latest los 18.1
reboot
in wizard ... WLAN tries to activate ... but broken
(also uses unbricktool - OOS10.3.8 + Updates)


after wizard ... tried to enable WLAN

Code:
QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
09-13 15:11:00.015  2335  2335 D KeyguardClockSwitch: Updating clock: 15:11
09-13 15:11:03.676   841   841 E [email protected]: Failed to write driver state control param: Invalid argument
09-13 15:11:03.677   841   841 E [email protected]: Failed to load WiFi driver
09-13 15:11:03.677   841   841 E [email protected]: Failed to initialize firmware mode controller
09-13 15:11:03.678   841   841 E [email protected]: Wifi HAL start failed
09-13 15:11:03.680  1580  2176 E HalDevMgr: Cannot start IWifi: 9 ()
09-13 15:11:03.680  1580  2176 E WifiVendorHal: Failed to start vendor HAL
09-13 15:11:03.680  1580  2176 E WifiNative: Failed to start vendor HAL
09-13 15:11:03.680  1580  2176 E WifiNative: Failed to start Hal
09-13 15:11:03.680  1580  2176 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
09-13 15:11:03.682  1580  2176 D WifiScanRequestProxy: Sending scan available broadcast: false
09-13 15:11:03.682  1580  2179 I WifiScanningService: Received a request to disable scanning, UID = 1000
09-13 15:11:03.683  1580  2179 I WifiScanningService: wifi driver unloaded
09-13 15:11:03.684  1580  2176 I WifiScanRequestProxy: Scanning is disabled
09-13 15:11:03.685  1580  2176 D WifiClientModeManager: received an invalid message: { when=-20s345ms what=2 arg1=2 target=com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler }
09-13 15:11:03.685  1580  2176 E HalDevMgr: IWifiEventCallback.onFailure: 9 ()
09-13 15:11:03.686  1580  2176 D WifiController: STA disabled, return to DisabledState.
09-13 15:11:03.686  1580  2176 D WifiController: EnabledState.exit()
09-13 15:11:03.686  1580  2176 D WifiController: DisabledState.enter()

GPS also doesn't works for me....
after flashing custom Kerne "mcd_op6x_r5_custom-los" WLAN is ok...

anybody an idea whats wrong?
 

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
thank you, i installed custom kernal and i need to restore stock kernal pls u know how?
don't use custom kernel because it's not equal to stock kernel.
want to restore stock kennel there are 2 ways
1 is you flash dirty rom on twrp then format factory
2 you flash the rom via lineageos adb sideload These ways I remember correctly, all have to format factory
 
Last edited:

CrysisLTU

Senior Member
Feb 1, 2012
284
356
since the last 10 updates "WLAN" function is broken....

had gone back to OxyOS11 - WLAN works out of the box

oem unlock
twrp 3.5.2_9-0
full wipe
install latest los 18.1
reboot
in wizard ... WLAN tries to activate ... but broken
(also uses unbricktool - OOS10.3.8 + Updates)


after wizard ... tried to enable WLAN

Code:
QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
09-13 15:11:00.015  2335  2335 D KeyguardClockSwitch: Updating clock: 15:11
09-13 15:11:03.676   841   841 E [email protected]: Failed to write driver state control param: Invalid argument
09-13 15:11:03.677   841   841 E [email protected]: Failed to load WiFi driver
09-13 15:11:03.677   841   841 E [email protected]: Failed to initialize firmware mode controller
09-13 15:11:03.678   841   841 E [email protected]: Wifi HAL start failed
09-13 15:11:03.680  1580  2176 E HalDevMgr: Cannot start IWifi: 9 ()
09-13 15:11:03.680  1580  2176 E WifiVendorHal: Failed to start vendor HAL
09-13 15:11:03.680  1580  2176 E WifiNative: Failed to start vendor HAL
09-13 15:11:03.680  1580  2176 E WifiNative: Failed to start Hal
09-13 15:11:03.680  1580  2176 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
09-13 15:11:03.682  1580  2176 D WifiScanRequestProxy: Sending scan available broadcast: false
09-13 15:11:03.682  1580  2179 I WifiScanningService: Received a request to disable scanning, UID = 1000
09-13 15:11:03.683  1580  2179 I WifiScanningService: wifi driver unloaded
09-13 15:11:03.684  1580  2176 I WifiScanRequestProxy: Scanning is disabled
09-13 15:11:03.685  1580  2176 D WifiClientModeManager: received an invalid message: { when=-20s345ms what=2 arg1=2 target=com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler }
09-13 15:11:03.685  1580  2176 E HalDevMgr: IWifiEventCallback.onFailure: 9 ()
09-13 15:11:03.686  1580  2176 D WifiController: STA disabled, return to DisabledState.
09-13 15:11:03.686  1580  2176 D WifiController: EnabledState.exit()
09-13 15:11:03.686  1580  2176 D WifiController: DisabledState.enter()

GPS also doesn't works for me....
after flashing custom Kerne "mcd_op6x_r5_custom-los" WLAN is ok...

anybody an idea whats wrong?
OOS11 vendor firmware is pretty much a requirement now. OOS10 firmware works just enough to boot, but it breaks WiFi, GPS, dash charging, probably more: https://review.lineageos.org/c/LineageOS/android_device_oneplus_sdm845-common/+/315213/

Stay on OOS11 vendor firmware. Also, use LOS recovery.
Also, if you would have followed the official install instructions on the wiki, you would have known that already. :)
 
  • Like
Reactions: Spaceoid

lamahgra

Senior Member
Jan 27, 2008
106
54
OOS11 vendor firmware is pretty much a requirement now. OOS10 firmware works just enough to boot, but it breaks WiFi, GPS, dash charging, probably more: https://review.lineageos.org/c/LineageOS/android_device_oneplus_sdm845-common/+/315213/

Stay on OOS11 vendor firmware. Also, use LOS recovery.
Also, if you would have followed the official install instructions on the wiki, you would have known that already. :)
followed:


fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed


ex.
fastboot flash --slot=all abl abl.img
fastboot: error: Could not check if partition abl has slot all

Sending 'abl' (204 KB) OKAY [ 0.012s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions')

Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x0
(bootloader) cal_rebootcount: 0x31

:cry:
 

CrysisLTU

Senior Member
Feb 1, 2012
284
356
followed:


fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed


ex.
fastboot flash --slot=all abl abl.img
fastboot: error: Could not check if partition abl has slot all

Sending 'abl' (204 KB) OKAY [ 0.012s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions')

Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x0
(bootloader) cal_rebootcount: 0x31

:cry:
Your bootloader is unlocked, so you can skip that step.

Make sure your platform-tools are up to date. That should fix the fastboot flash error.
 

AshraafAzhar

Member
May 17, 2014
29
13
Selangor, Malaysia
followed:


fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed


ex.
fastboot flash --slot=all abl abl.img
fastboot: error: Could not check if partition abl has slot all

Sending 'abl' (204 KB) OKAY [ 0.012s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions')

Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x0
(bootloader) cal_rebootcount: 0x31

:cry:
Back then, I also noticed that fastboot flash --slot=all not working for me when using latest SDK Platform-Tools for Windows (v31.0.3), need to manually specify both slot such as 'fastboot flash vendor_a vendor.img' and 'fastboot flash vendor_b vendor.img'.

The guide from official wiki also didn't work for me. Have a look at MANUAL FLASH: Windows - OSX - Linux for the needed command to flash critical partition(need to use twrp for adb push and flash those critical partitions).

To make it a lot easier, I simply just use Unofficial Android 11 TWRP from Nebrassy and flash both slot with a full fat OOS 11 ROM before flashing Lineageos 18.1
 

CrysisLTU

Senior Member
Feb 1, 2012
284
356
Back then, I also noticed that fastboot flash --slot=all not working for me when using latest SDK Platform-Tools for Windows (v31.0.3), need to manually specify both slot such as 'fastboot flash vendor_a vendor.img' and 'fastboot flash vendor_b vendor.img'.

The guide from official wiki also didn't work for me. Have a look at MANUAL FLASH: Windows - OSX - Linux for the needed command to flash critical partition(need to use twrp for adb push and flash those critical partitions).

To make it a lot easier, I simply just use Unofficial Android 11 TWRP from Nebrassy and flash both slot with a full fat OOS 11 ROM before flashing Lineageos 18.1
fastboot flash --slot=all worked fine for me, using latest platform-tools and LOS recovery. You should flash from LOS recovery fastboot, not via regular fastboot.
 

AshraafAzhar

Member
May 17, 2014
29
13
Selangor, Malaysia
Ouhh, I thought both are the same, that LOS Recovery will reboot into regular fastboot and back then I also can't boot into LOS recovery on OOS 10 vendor using command 'fastboot boot recovery.img' (September 14 version), so I simply ignored 'fastboot flash boot recovery.img' thinking It will led to the same result.
 

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
since the last 10 updates "WLAN" function is broken....

had gone back to OxyOS11 - WLAN works out of the box

oem unlock
twrp 3.5.2_9-0
full wipe
install latest los 18.1
reboot
in wizard ... WLAN tries to activate ... but broken
(also uses unbricktool - OOS10.3.8 + Updates)


after wizard ... tried to enable WLAN

Code:
QtiCarrierConfigHelper: WARNING, no carrier configs on phone Id: 0
09-13 15:11:00.015  2335  2335 D KeyguardClockSwitch: Updating clock: 15:11
09-13 15:11:03.676   841   841 E [email protected]: Failed to write driver state control param: Invalid argument
09-13 15:11:03.677   841   841 E [email protected]: Failed to load WiFi driver
09-13 15:11:03.677   841   841 E [email protected]: Failed to initialize firmware mode controller
09-13 15:11:03.678   841   841 E [email protected]: Wifi HAL start failed
09-13 15:11:03.680  1580  2176 E HalDevMgr: Cannot start IWifi: 9 ()
09-13 15:11:03.680  1580  2176 E WifiVendorHal: Failed to start vendor HAL
09-13 15:11:03.680  1580  2176 E WifiNative: Failed to start vendor HAL
09-13 15:11:03.680  1580  2176 E WifiNative: Failed to start Hal
09-13 15:11:03.680  1580  2176 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
09-13 15:11:03.682  1580  2176 D WifiScanRequestProxy: Sending scan available broadcast: false
09-13 15:11:03.682  1580  2179 I WifiScanningService: Received a request to disable scanning, UID = 1000
09-13 15:11:03.683  1580  2179 I WifiScanningService: wifi driver unloaded
09-13 15:11:03.684  1580  2176 I WifiScanRequestProxy: Scanning is disabled
09-13 15:11:03.685  1580  2176 D WifiClientModeManager: received an invalid message: { when=-20s345ms what=2 arg1=2 target=com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler }
09-13 15:11:03.685  1580  2176 E HalDevMgr: IWifiEventCallback.onFailure: 9 ()
09-13 15:11:03.686  1580  2176 D WifiController: STA disabled, return to DisabledState.
09-13 15:11:03.686  1580  2176 D WifiController: EnabledState.exit()
09-13 15:11:03.686  1580  2176 D WifiController: DisabledState.enter()

GPS also doesn't works for me....
after flashing custom Kerne "mcd_op6x_r5_custom-los" WLAN is ok...

anybody an idea whats wrong?
I use the stock kernel gps work mcd kernel r8 no support for new build of lineageos
 

lamahgra

Senior Member
Jan 27, 2008
106
54
I use the stock kernel gps work mcd kernel r8 no support for new build of lineageos
msm tool 3.1.8 - patcheed to 3.1.12 via online update
local upgrade to OOS beta3 (Android11)
oem unlock
fastboot flash boot lineage-18.1-20210921-recovery-enchilada.img.
adb sideload copy-partitions-20210323_1922.zip
full wipe
flashed lineage-18.1-20210921-nightly-enchilada-signed.zip
still no wlan after first boot

extract via payload-dumper-go (OOS Beta3)
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot


no wlan :-(

went back to mcd Kernel r5 ..no gps..but wlan :)
 

CrysisLTU

Senior Member
Feb 1, 2012
284
356
msm tool 3.1.8 - patcheed to 3.1.12 via online update
local upgrade to OOS beta3 (Android11)
oem unlock
fastboot flash boot lineage-18.1-20210921-recovery-enchilada.img.
adb sideload copy-partitions-20210323_1922.zip
full wipe
flashed lineage-18.1-20210921-nightly-enchilada-signed.zip
still no wlan after first boot

extract via payload-dumper-go (OOS Beta3)
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot


no wlan :-(

went back to mcd Kernel r5 ..no gps..but wlan :)
Try OOS11 stable, not beta 3 imgs?
 
  • Like
Reactions: kecodoc

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
msm tool 3.1.8 - patcheed to 3.1.12 via online update
local upgrade to OOS beta3 (Android11)
oem unlock
fastboot flash boot lineage-18.1-20210921-recovery-enchilada.img.
adb sideload copy-partitions-20210323_1922.zip
full wipe
flashed lineage-18.1-20210921-nightly-enchilada-signed.zip
still no wlan after first boot

extract via payload-dumper-go (OOS Beta3)
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot


no wlan :-(

went back to mcd Kernel r5 ..no gps..but wlan :)
I follow the wiki sequentially and am on lineageos 18.1 it's amazing because it works so well and perfect you should try again with official oos 11
 

daleloco

Member
Mar 24, 2014
8
1
Apps & Games
Does anybody know if there is the posibility to change haptic vibration intensity? I use nav buttons, but the vibration is too high compared to stock rom. I dont want to disable it, I just want to decrease it a bit
 

lamahgra

Senior Member
Jan 27, 2008
106
54
msm OnePlus_6_OxygenOS_10.3.8\enchilada_22_J.50_210121
local upgrade: nePlus6Oxygen_22.J.60_OTA_0600_all_2108052235_37de6.zip
oem unlock en debug
fastboot flash boot lineage-18.1-20210921-recovery-enchilada.img
adb sideload copy-partitions-20210323_1922.zip

adb reboot bootlader

fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot

without any error
..
reboot recovery
Factory Reset, then Format data / factory reset
adb sideload
lineage-18.1-20210921-nightly-enchilada-signed.zip

no wlan..... @ wizard

where's my fault?
 

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
I am using lineageos without root and wondering if there is any good mod for lineageos 18.1 or leave it as it is and add nothing Thank you very much, I'm glad if you guys share these cool mods for this great rom.
 

CrysisLTU

Senior Member
Feb 1, 2012
284
356
msm OnePlus_6_OxygenOS_10.3.8\enchilada_22_J.50_210121
local upgrade: nePlus6Oxygen_22.J.60_OTA_0600_all_2108052235_37de6.zip
oem unlock en debug
fastboot flash boot lineage-18.1-20210921-recovery-enchilada.img
adb sideload copy-partitions-20210323_1922.zip

adb reboot bootlader

fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all fw_4j1ed fw_4j1ed.img
fastboot flash --slot=all fw_4u1ea fw_4u1ea.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all vendor vendor.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot reboot

without any error
..
reboot recovery
Factory Reset, then Format data / factory reset
adb sideload
lineage-18.1-20210921-nightly-enchilada-signed.zip

no wlan..... @ wizard

where's my fault?
Go to settings, about phone, click on Android version. What's your baseband version?

Also, there's no need to do such a clean install (MSM, local upgrade, etc.) If you properly flashed and can boot the latest LOS18.1 - then just upgrade the OOS vendor firmware via LOS recovery fastboot. You don't have to do anything else.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Clean installed LOS18.1 yesterday from Android 11 firmware base. Spent 1 hour figuring out why I was not able to setup my WhatsApp, turned out it had nothing to do with Lineage but because Facebook was down.

    Anyway everything is runnin smooth. Thanks 👍
    2
    So... LOS is not working for me.

    by any chance do you have a link that explains how to go back to stock?

    My phone is not briked but sms is not working and gapps neither.

    Thanks in any case,
    I bet you didn't follow the official install instructions from the LOS wiki.

    Install: https://wiki.lineageos.org/devices/enchilada/install
    Update the firmware if you never had used OOS11 on your device: https://wiki.lineageos.org/devices/enchilada/fw_update

    Also, use MindTheGapps.

    To go back to stock, you could use MSMDownloadTool.
    2
    Just a tiny review, story, thank you and probably my first post since a few years now:

    Was pretty happy with OOS, no doubt. Then the hassle began a few days ago. Some are apps were acting weird and resisted getting a connection, despite my connection was OK and permissions too. Whether reinstalling, nor clearing really everything at the base of data/data/ from those apps helped. Thought: Maybe do the step to OOS11 now. Made that. Suddenly, now also Android Auto stopped working. Paired, but no connection. Displays "Unknown Device". So back to the scratchboard and bringing back something I really didn't do a long time ago: Get TWRP, clear everything, setup LOS, GApps, SuperSU... ahm... Magisk.

    TWRP? Seems to be gone for our devices. Even custom once seems to be vanished. Don't know what happened, but maintenance got dropped? Read through the threads, the latest version should word fine - except encryption. Since this wouldn't be something I need to have: Fine.
    Connection my laptop to the device, get the latest SDK platform tools and USB driver. "adb devices" works. Fine. "adb reboot bootloader" working too - I'm happy. Moving all together: "fastboot boot twrp.img"... hmmm... Nothing? Ah, here we go. Qualcomm error. Dang. So, what to do now? MSM? Nope. LOS/CM like I had on all my devices for now.

    Recovery from LOS. That might work for me. Again to the bootloader and flashed the recovery. Reboot to OOS now? What happened? "adb reboot recovery". There we go. Fine. Now what? Mhm. Got it. Simpy sideload it in LOS recovery. Fine with that. a/b partition was kinda new for me now. Never had to deal with it, because "fastboot boot twrp.img" was a thing. Never had to install a custom recovery, because: No reason to. So straight forward: Flash LOS, flash MindTheGApps, flash Magisk 23. Switch to fastboot: "fastboot –set-active=_a" & reboot to recovery, flash the other partition the same way > Reboot to system.

    Setup straight forward like in the past and was curious, if everything works.

    So here the points:
    • Android Auto works better than on OOS10 (and obviously 11, because never worked).
    • No problems encountered so far over all.
    • AOD works like a charm.
    • AMOLED dark theme is something OOS should adopt, but probably never will.
    • Recovery is a bit underwhelming/simple, but does the job.
    • Google Camera Mod (Urnyx) works like it did on OOS.
    • DAC seems to be better than on OOS? Maybe? Because my car stereo sounds better, I think. Maybe placebo.
    • Kernel seems to be decent, because not pulling a crazy amount of energy for same tasks whilst keeping the device snappy. Tweaked governor possibly. Have to look this up. Maybe placebo too.
    • OOS navigation gestures and face unlock will be missed, for sure.

    Final verdict: I'm for sure not switching back to OOS. LOS18.1 seems to be stable enough for my daily usage. Thanks for all the efforts and time, you are putting into it!
    2
    I always update via OTA. I always have to patch a new boot.img with Magisk and install via fastboot, but Gapps are kept.
    No need for fastboot. Go into the Magisk app before installing the OTA, click on Uninstall Magisk, then Restore Images. Now install the OTA via the built in updater. Once the OTA update is installed, do not reboot. Go back into the Magisk app. Click on Install Magisk, select Install to Inactive Slot (After OTA), and only then reboot.

    Full instructions can be found here: https://topjohnwu.github.io/Magisk/ota.html
    1
    Has anybody tried to upgrade fw to 11.1.1?
  • 27
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    3
    If anybody is curious, Ive been crawling through the code commits. Unfortunately, it looks like both Enchilada and Fajita will have to wait for some time due to issues that were encountered when booting. At least for Fajita. It will be some time until we get our first official build.

    UPDATE 1: Both Enchilada and Fajita have been reverted from the hudson branch, which indicates official commit status has been reversed. Our savior Luk has got hands full with work on these issues I imagine, so wait times will extend. Hang tight lads! We will land on Hudson soon, I hope.

    UPDATE 2: That was quick! Seems like Luk figured out the issue for Fajita and has opened a commit to merge fajita to 18.1 official again. Fajita and enchilada are merged to the Hudson branch once again. This is good news, and I am hoping that the enchilada build will be posted and merged on schedule.
    3
    Anyone else having touchscreen issues with the latest build? Like not responding to some touches and not being able to pull down the notification shade?

    Edit: reverted to last week's build and the issue is gone. So some commit messes with the touchscreen.