[ROM][10.0][OFFICIAL] LineageOS 17.1 for Wileyfox Swift

[115ek]

[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */[/COLOR]

Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.

More detailed instructions at:
Install LineageOS on crackling

Official Download link:
LineageOS Downloads

115ek's test builds (for testers only)
Downloads

Recommended Google Apps package:
Open GApps (pico only)

Changelog:
Changes for crackling

Bug reports:
How to submit a bug report

Donate to support development:
Donate via PayPal to LineageOS

 

[115ek]

reserved

 

[115ek]

reserved2

 

[115ek]

The "old" Lineage 17.1 thread got lost during some xda server maintenance. It's not really clear to me what happened.
It couldn't be brought back for several weeks now, so I decided to create a new thread.

I'd also like to inform you that I'll provide some test builds here. Before merging bigger changes I'd like to ensure the builds are okay (not just for me).
It would be nice if some of you could test a bit. Only caveat: You won't be able to switch between test builds/official builds easily as different signature keys are used and a factory reset is needed (alternatively flashing a migration file could save you from resetting the device (more info)). However, these test builds are thought for interested persons only
You'll find the first test build here.
Changes:

• switch to userspace lmkd (more info here)

It would be interesting if you experience any differences in memory management (how many apps can be opened in background, how fast is app switching, when are apps closed...).
And of course if the system is usable at all.

 

[petexd]

Recovery

Can the lineage-recovery.img do nandroid backups now that twrp can't?

 

[115ek]

Can the lineage-recovery.img do nandroid backups now that twrp can't?

Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.

 

[petexd]

Lineage recovery can't do backups. TWRP can.
But standard users installing gapps could also do a backup via google servers. I guess that's the most "easiest" thing.

I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).

 

[115ek]

I've just tried to restore a recent backup for the first time with android 10 (lineage 17.1) and although it appears to backup the restore did not work. I tried it twice. Then I remember reading that twrp were having problems being totally compatible with the new partitioning of android 10 so there have been no updates since may 2019. I'm assuming that's the issue with the latest backups (and I don't use gapps).

What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.

Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.

Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.

 

[petexd]

What's happening when you're restoring? Are you running into a bootloop?
Then probably this could help.
Please keep in mind TWRP isn't able to decrypt an encrypted /data partition. As long as we don't fix it, you won't have any chance to backup an encrypted device.
If you're not encrypted it shouldn't be a problem, though.

Edit:
You can find the build with the according changes here.
Please report back if it works for you. Keep in mind you can't dirty flash this over an official build.

Edit 2:
I checked the issue on my own and it worked. The change got already merged so it'll be included in the next official build as well. As builds are weekly temporary you could download it next saturday.

Thanks for the info. That's exactly what's happening but I have no idea how to apply that patch. I don't really want to install an unoffical rom: that's how I discovered twrp wasn't working properly, testing one of my builds then hoping to go back to your offical from restore.
Any way I'm happy to wait for your next issue.
Thanks for doing a great job.

 

[libove]

I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.

 

[115ek]

I've just installed the Lineage OS 17.1 official on my Swift. Although this 17.1 thread mentions OpenGapps pico only (which was the case under LOS 16), even the pico package produces an insufficient space error on my Swift. (This is after a completely clean - wipe system and data and all caches - installation).
Have Gapps just gotten too big for these small devices? Or is there some trick to get it to work?
thanks.

Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.


Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.

 

[zappbrannigan62]

Certification Status on 17.1

Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.

Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?

Thanks!

 

[libove]

Must sideload, not enough space to push and install from local, I feel silly...

Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.

Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).

Anyway, many thanks!
-Jay

Last time I tried it worked. But you're right - the available space on /system is very rare. I already made some "hacks" to free up some space. You could try to overcome this by installing an older pico gapps package from here which is smaller. It'll update itself if you connect to a wifi network anyway.
Another thing you could try is using FlameGapps. The final thing would be resizing the /system partition.


Is anyone else experiencing this issue? I can't reproduce it on my device.
And can someone give feedback for the latest testbuilds featuring userspace lmkd? I'd really appreciate it.

 

[115ek]

Hi,
I am currently on LineageOS 16 and Play Store reports my device as "certified", which allows me to run Netflix, banking apps, etc.

Will this also be the case when updating to 17.1 with Pico Gapps wihtout tweaking / installing anything else?

Thanks!

I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.

 

[didyou]

Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;

https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr

 

[Cerealekillers]

Hello there. I am currently using the latest version of LOS 17.1. There is no problem throughout the system, but when I try to use one application, the phone resets itself. While opening the application, it stays on the white screen and the phone is reset. Application;

https://play.google.com/store/apps/details?id=com.garanti.cepsubesi&hl=tr

Have you installed Gapps or MicroG on your system ?

 

[didyou]

Have you installed Gapps or MicroG on your system ?

Yes, installed pico GAPPS.

 

[zappbrannigan62]

Works

I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.

I flashed the latest nightly + pico gapps using TWRP and

• everything is working beautifully
• Playstore reports the device to be certified

So thanks a lot!

 

[r25txe]

Aargh. Grrr. (Angry at myself. I was being stupid).
The reason why even the pico package "didn't fit" is that I'd pushed it to the device and was trying to install it locally, which (of course, in retrospect, despite there being plenty of other space on other partitions) used up some of the precious free space on /system .. for a thing that needed space to install on /system.
I deleted the local copy of the .ZIP file and sideloaded it, and it fit.
Aargh. Grrr.

Aside from my own self-stupidity, I did notice one thing that might be of interest to someone: The FlameGapps package installer refused to continue, stating that the package was built for Android 10 but this device is running (blank).

Anyway, many thanks!
-Jay

I don't use gapps on my own. But play certification is a mystery sometimes. However, as nobody complained until now (and I guess most users install gapps...) it should be okay. Maybe someone can verify this.

Can verify that my Play Store, on 17.1, reports my ridiculously modded Swift as certified without having to do anything to achieve that.

 

[mkstevo]

Sorry, I know I am a real dunderhead when it comes to these things and I apologise for such a basic question. But...

I have a Swift 2 X which is working on Oreo. If I replace this with LineageOS 17 do I have to do anything "fancy" to get Google Pay to work after I've installed LineageOS?

I've installed LineageOS on my Oppo R5 which doesn't have NFC so this can't use "Tap 'n' Pay" anyway. I've installed LineageOS on mine and my Wife's Nextbit Robin and Google Pay - "Tap 'n' Pay" - worked without doing anything more than install and go.

It's just that I do really like the facility of Google Pay and wouldn't want to lose that just for the sake of system wide dark mode.

Sorry again for being so dense as to not understand.