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

[UNLUCKY67]

I guess that could be the problem.
Can you try flashing the lastest firmware from here: https://cyanogenupdatetracker.com/downloads/
SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip
It should be Cyanogen 13 (Android 6). You can use TWRP for that.
Afterwards flash the lineage zip.

Thanks - it worked! I now have a working OS, I am so pleased.
I do still have a problem not sure if you could help as not entirely sure what has caused it.
Although I can receive and make calls and send texts I am not receiving texts (SMS) on my SIM 1 (giffgaff). Other sim seems to be working (And I could send a text from one sim to the other on the phone)
I've tried every thing I can find online (manual roaming etc) Put the Sim in a different phone and after a while I got 4 texts from one sender, but no others (have family sending me test sms).
I restored texts an old backup on google drive, there were thousands. I have tried to delete some in messenger but they don't seem to be being deleted. Currently backing them up to email. I'll then try and clear the data in messenger. Is it possible to reinstall just the messenger?
Also my google email (even after installing gmail) is showing as I have an empty inbox - (says 'you've finished - nothing in inbox' with a cartoon of someone relaxing, reading a book....) if only that was really the case .
Thanks again ...at least I now have hope of getting back a fully working phone and it is a lot faster than it was....

 

[UNLUCKY67]

Update - I have now got it all working properly. in the end I did a complete wipe and reinstalled Lineage OS (which had been updated today).
My recovery is now the lineage one.
Thanks again for your help...

 

[RunnersHai]

No SIM-Cards anymore despite serveral restarts

I got the latest version of crackling from the 17.10.2020. But even on the day before somehow the SIM-Cards can't be recognized anymore. I have no idea why. I changed nothing, in fact my Swift was just laying on the table – and when I picked it up the next time the cards were gone. It's really weird.

I swapped them, tried to clean the slots – without a change. Sometimes when I do a reboot a message pops up, saying the Android Services Library has tried to start several times without succeeding. I don't know, if it has to do anything with it.

Is it software or a hardware problem. Is it an option to push the /e/ OS on the device? But it would be an downgrade. I have read that it could brick the phone.

So thankful for any help.

 

[115ek]

I got the latest version of crackling from the 17.10.2020. But even on the day before somehow the SIM-Cards can't be recognized anymore. I have no idea why. I changed nothing, in fact my Swift was just laying on the table – and when I picked it up the next time the cards were gone. It's really weird.

I swapped them, tried to clean the slots – without a change. Sometimes when I do a reboot a message pops up, saying the Android Services Library has tried to start several times without succeeding. I don't know, if it has to do anything with it.

Is it software or a hardware problem. Is it an option to push the /e/ OS on the device? But it would be an downgrade. I have read that it could brick the phone.

So thankful for any help.

It sounds like a hardware issue for me.
Of course you can install /e/. However, the latest version for the swift is based on nougat as far as I remember. Really bricking the device is actually hard. As long as you don't relock the bootloader and lock yourself out that way.

You could also try the last official marshmallow version from here and check if the problem persists. If yes it's definitely a hw related problem.

 

[RunnersHai]

I guess you are right ...

... but in a total different way as I had assumed.

It sounds like a hardware issue for me.
Of course you can install /e/. However, the latest version for the swift is based on nougat as far as I remember. Really bricking the device is actually hard. As long as you don't relock the bootloader and lock yourself out that way.

You could also try the last official marshmallow version from.

As newbie I'm not allowed to post links, so I had to delete it. If you need the link look into the original post.

Yes, it seems that you are right. I tested everything: Marshmallow, /e/ and LineageOS without root. Nothing worked. Then I put the SIM-Cards into another phone to use it as substitute until I have bought a new one. Surprise, they doesn't work there either. Now I'm waiting for the new SIM-Cards – hopefully this was the reason. Would be a lot of work, but cheap

Thanks a lot for your support. It was very helpful to get to the ground of the problem.

 

[RunnersHai]

Two broken SIM-Cards

Yes, it seems that you are right. I tested everything: Marshmallow, /e/ and LineageOS without root. Nothing worked. Then I put the SIM-Cards into another phone to use it as substitute until I have bought a new one. .

Yeah, in the end it was so easy. The reason for not recognizing the SIM-cards was, they were broken – both at the same time. I don't know how this happened, but it has. And now, after a long journey, everything works fine again.:good:
Thanks again for the support.

 

[TitanFoxX]

Hi all,

I did a clean install of LOS 17.1 on my Wileyfox Swift. Everything works, except receiving text messages via SMS. I can send alright, but I receive none.

I tried both SIM card slots with two different SIM cards (two different ISP's). Unfortunately without success. These cards work fine in another smartphone and worked fine with the original Wileyfox firmware.

In this thread there was somebody else with the same issue.

I am using the last build version at the moment (31-10-2020), but the issue was also in the older 17-10-2020 version.

Sincerely,
Ruud.

 

[115ek]

Hi all,

I did a clean install of LOS 17.1 on my Wileyfox Swift. Everything works, except receiving text messages via SMS. I can send alright, but I receive none.

I tried both SIM card slots with two different SIM cards (two different ISP's). Unfortunately without success. These cards work fine in another smartphone and worked fine with the original Wileyfox firmware.

In this thread there was somebody else with the same issue.

I am using the last build version at the moment (31-10-2020), but the issue was also in the older 17-10-2020 version.

Sincerely,
Ruud.

Can you please open a bug report according to https://wiki.lineageos.org/bugreport-howto.html ?

 

[TitanFoxX]

Hey, thank you for the suggestion. I just filed a bug report. Dang, that template of theirs is picky how you fill in the information

 

[Floyd-74]

Hello 115ek,
thank you for your good work with this ROM.
Will there be a Lineage 18 for Wileyfox Swift?
Would be nice if it stayed with us.

Greetz, Floyd

 

[115ek]

Hello 115ek,
thank you for your good work with this ROM.
Will there be a Lineage 18 for Wileyfox Swift?
Would be nice if it stayed with us.

Greetz, Floyd

I fear official builds will be impossible due to space limitations (gapps won't fit)
However, unofficially it may work.
I already compiled an image - just for checking how 18 looks like. Bluetooth is broken, though. You can find it here.
I was really busy the last months, but I hope there will be some free time in december.

 

[Floyd-74]

hello 115ek,
Thanks for your answer, I installed the lineage-18.0-20201029-UNOFFICIAL-crackling.zip with flamegapps-basic 11 and magisk 21.1. Everything worked, the system memory partition is 99% full, but everything works including Google.
That was a little annoying without warning my recovery TWRP was overwritten with the Lineage Recovery, I flashed TWRP Recovery afterwards with adb.
But it would have been avoidable if I had flashed it again in the TWRP. Besides the well-known Bluetooth problem,
SE-Linux and the boot recovery setting are all good so far.
Thanks for your information, Floyd :good:

 

[didyou]

Hello to everyone. The phone freezes and becomes unresponsive when I enter lineage recovery mode and try to Apply Update? Right now my computer is problematic and I cannot install TWRP. I want to use it to root. Thank you.