[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Swift

[killerbees19]

I've formatted an Android 6 device and flashed this ROM. Is encryption stable with this ROM? Anything else I should know before enabling encryption?

 

[115ek]

I've formatted an Android 6 device and flashed this ROM. Is encryption stable with this ROM? Anything else I should know before enabling encryption?

Yes, it works. Else the build won't be official. See the requirements here.
Setting a PIN/password/pattern is advisable. Else your device gets encrypted with "default_password". But you can also do this afterwards.

 

[killerbees19]

Thanks, @115ek! Device successfully encrypted

btw: I've a strange issue. Not sure if it's related to this specific ROM…

I've connected a Bluetooth device (Marshall Minor II) and it works fine, "only" BT 4.x with SBC, but everything stable. Except when used for phone calls! It's switching to mono (left side) and the volume of built-in microphone is way too low. Nobody can hear me, I've to shout directly into the microphone as a workaround. It doesn't matter if called via default telephone app (2G/3G) or Linphone (WiFi/SIP). I'm unable to reproduce this behavior with other Android devices and this Bluetooth headphones.

There's always one line in the kernel log when starting a phone call:

qdsp_cvp_callback: cmd = 0x112c2 returned error = 0x9

# 0x000112C2 = VSS_IVOLUME_CMD_SET_STEP

When using Linphone there's an error too, but it's different:

q6asm_callback: cmd = 0x10da1 returned error = 0x2
q6asm_send_asm_cal: DSP returned error[-2] audio audstrm cal send

# 0x00010DA1 = ASM_STREAM_CMD_SET_PP_PARAMS_V2

Not sure if they're related to this issue.

Any ideas what's going wrong here? Any hints what I should check?

Edit: See next post.

 

[killerbees19]

I've cleared the BT app cache and data, now it works in stereo…

Pure luck? We'll see…

 

[robin0800]

Oficial 17.1 is out

Oficial 17.1 is out for this phone

https://download.lineageos.org/crackling

 

[wkn000]

Oficial 17.1 is out for this phone

https://download.lineageos.org/crackling

Dirty flashed it over my LOS 16.0 (after preactive uninstall of addonsu) with TWRP-3.3.1-0. Installed Magisk for root. Works all fine by now.

 

[edwaine]

@115ek where's your Lineage 17.1 crackling thread?

 

[115ek]

@115ek where's your Lineage 17.1 crackling thread?

I updated it to link to the new downloads. Then it disappeared. xda is a bit broken sometimes
I already contacted a moderator - let's see if they can bring it back.

However, 17 is official now and gets shipped.

 

[maxic_g]

However, 17 is official now and gets shipped.

Already installed. It's ok with BitGapps R6. Thank you.

P.S. With BitGapps update to next build is broken. OpenGapps - ok.

 

[killerbees19]

Thanks, @115ek! Device successfully encrypted

But now TWRP (3.3.1-0) is unable to mount /data

It can't find the crypto-signature. Any ideas how to fix that?

Edit: TWRP 3.1.1/3.2.3 displays a password prompt, but says it's invalid. TWRP 3.3.x doesn't show a password prompt at all.

 

[115ek]

But now TWRP (3.3.1-0) is unable to mount /data

It can't find the crypto-signature. Any ideas how to fix that?

Edit: TWRP 3.1.1/3.2.3 displays a password prompt, but says it's invalid. TWRP 3.3.x doesn't show a password prompt at all.

TWRP isn't able to decrypt /data partition. The problem needs to be solved in TWRP.
Besides that, beginning with Lineage 17, all devices ship the lineage recovery which should be the preferred solution.
Why do you need a decrypted /data partition? OTA updates work fine without.

 

[killerbees19]

Why do you need a decrypted /data partition?

Primary for backup purposes, but emergency access via ADB in TWRP would be nice too, if something goes really wrong.

Edit: Nevermind, I've disabled encryption again. (TAR-backup of mounted /data to SD-card; format /data in TWRP, reboot; restore unencrypted /data-backup in TWRP)

Maybe I'll re-enable it again in the future, but for the moment the TWRP "bug" is a real problem for me.

 

[FtCat]

TWRP isn't able to decrypt /data partition. The problem needs to be solved in TWRP.
Besides that, beginning with Lineage 17, all devices ship the lineage recovery which should be the preferred solution.
Why do you need a decrypted /data partition? OTA updates work fine without.

Where is the download for the lineage recovery? I notice for other devices it is on the download page together with the updates but not for crackling. Have updated with TWRP and all went smoothlly am happy with it so far. Installation instructions required for the recovery as well.

 

[115ek]

Where is the download for the lineage recovery? I notice for other devices it is on the download page together with the updates but not for crackling. Have updated with TWRP and all went smoothlly am happy with it so far. Installation instructions required for the recovery as well.

Lineage recovery shows up correctly on the download page since this morning. Instructions in the wiki also have been updated.

 

[Cerealekillers]

Lineage recovery shows up correctly on the download page since this morning. Instructions in the wiki also have been updated.

Is it better to use Lineage recovery instead of TWRP ?

 

[115ek]

Is it better to use Lineage recovery instead of TWRP ?

Lineage recovery is intended to establish a common base. If users use different TWRP's it is hard to deal with occuring problems. Furthermore, the lineage team hasn't got influence on the TWRP development (Exception: the lineage device maintainer and twrp device maintainer are the same person...).
The lineage recovery only features basic functionality like installing LineageOS images, applying OTA updates, factory-resetting the device or installing gapps. It is not as complex as TWRP!
In general I'd say: If you're a standard user you should go with lineage recovery. If you're more experienced or if you need special features then TWRP is the way to go. However, then you should be able to deal with issues on your own, too.

 

[Cerealekillers]

Lineage recovery is intended to establish a common base. If users use different TWRP's it is hard to deal with occuring problems. Furthermore, the lineage team hasn't got influence on the TWRP development (Exception: the lineage device maintainer and twrp device maintainer are the same person...).
The lineage recovery only features basic functionality like installing LineageOS images, applying OTA updates, factory-resetting the device or installing gapps. It is not as complex as TWRP!
In general I'd say: If you're a standard user you should go with lineage recovery. If you're more experienced or if you need special features then TWRP is the way to go. However, then you should be able to deal with issues on your own, too.

Okay, thank you, I'll stay with TWRP then.

 

[FtCat]

Okay, thank you, I'll stay with TWRP then.

Having tried both I prefer TWRP.

 

[oliverjames]

Lineage recovery is intended to establish a common base. If users use different TWRP's it is hard to deal with occuring problems. Furthermore, the lineage team hasn't got influence on the TWRP development (Exception: the lineage device maintainer and twrp device maintainer are the same person...).
The lineage recovery only features basic functionality like installing LineageOS images, applying OTA updates, factory-resetting the device or installing gapps. It is not as complex as TWRP!
In general I'd say: If you're a standard user you should go with lineage recovery. If you're more experienced or if you need special features then TWRP is the way to go. However, then you should be able to deal with issues on your own, too.

Could you please tell me how to revert to TWRP?

Thank you.

For info I updated my Swift to 17.1 without problems. After selecting the recommended Wipe in TWRP, I flashed the latest ROM and OpenGapps Pico (all other versions too large to fit the available space) and rebooted. The phone booted up with my previous desktop settings intack, marvellous, and time saving. To get root I copied the latest Magisk (v20.4) zip and the MagiskManager-v7.5.1.apk to the phones sdcard. I then flashed Magisk.zip, rebooted and installed Magisk manager. This all worked well giving root and enabling me to use the hide option.

 

[115ek]

Could you please tell me how to revert to TWRP?

Installing TWRP is quite easy: enter fastboot mode and

fastboot flash recovery YOUR_TWRP.img

You can enter fastboot via different ways:

• from Lineage via advanced restart (developer options): choose bootloader
• from recovery: choose advanced -> reboot to bootloader
• from powered off device -> connect USB while holding volume UP
• from powered off device -> power on while holding volume UP

EDIT: And yes, gapps pico is the only fitting package. Actually this was all explained in the LOS 17 thread. But it disappeared and until now xda wasn't able to bring it back.
Perhaps I should start a new one to not spam this one...