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

[robin0800]

Unofficial Rom lineage 16.0

There's a OTA with security update 5 march almost ready for release. Could be today or possibly next day or two.

Don't think they are going to make it!

I have made an unofficial one.

http://www.mediafire.com/file/fdmv9mj5ubnmb01/lineage-16.0-20200313-UNOFFICIAL-crackling.zip

should be there in about an hour

 

[Floyd-74]

Thank you robin0800, great job! ?
Kind regards.

 

[HTCm8LinOS]

Thank you robin0800 for the quick build (which works perfect!) and thank you jrior001 for the work of maintaining the official build so long. I still cant believe that i am rocking this phone (which cost me 50 Euros). Will go on and build for myself, thanks to the wonderful people at the LOS Wiki...

 

[petexd]

Unofficial Lineageos Rom

Thanks robin0800. I've just installed your rom. Great job.

 

[didyou]

Will this device be no longer officially supported?

 

[wowi63]

Thank you, robin0800,
for building this image.

I don't know about the structures of LinageOS, but could it be possible to make a official build again?
My wife and me use LinageOS for MicroG, they build their images only from official builds.

 

[115ek]

Hi. I'm continuing the official support and just re-added crackling to the build targets.

 

[wowi63]

Thank you, 115ek,

very nice!

---------- Post added at 11:57 AM ---------- Previous post was at 11:05 AM ----------

Seems to be Christmas today, LineageOS for MicroG got an Update from today including the security-updates from march!

))

 

[Floyd-74]

@115ek

Great news, thanks for taking on this hard work!

 

[Petrolofen]

@115ek
Many thanks! I am glad that you are doing this work! I am so happy with this cell phone.
Best regards!

 

[didyou]

I am very happy to continue the project. I hope it will continue for a long time, thank you very much.

 

[BlackMam]

That's really great news, that people like robin0800 and 155ek are still contributing to this phone. Thank you so much, everybody! I also installed Robin0800's ROM and it's working nicely.

 

[petexd]

Hi. I'm continuing the official support and just re-added crackling to the build targets.

Thanks 115ek. I'd just built an up to date rom for myself but am glad to see an official version. I've installed it and it's working well.
Great job.

 

[EmreA32]

Lineage OS 17 (Android 10)

Hi. Unofficial Lineage os 17 released for "crackling" (sourceforge.net/projects/lin17/)
please support for official. Thanks

 

[quho]

Thanks for keeping this phone alive with LOS.

I have been having an issue with applications not refreshing the screen when it's turned on unlocked. It started long time ago, maybe in LOS 14.1, but I'm not sure. I'm currently on the latest LOS 16 without gapps.

Strangely, it happens only when the screen is turned off and on again for the second time while the screen shows the same application. The touchscreen still works, but the screen won't refresh until it's supposed to show a completely different content (e.g. switching to another application using the home or overview button).

Steps to reproduce:
1. disable "Power button instantly locks" in the screenlock settings
2. switch to an application where sliding does something (e.g. home screen, or stay in the settings)
3. press the power button four times (screen off, on, off and on again)
4. try sliding the screen

Anyone else getting frozen screen? I tried changing various settings. I also tried a clean profile and remapping the power button to one of the volume buttons. I don't see anything suspicious in the log. Could it be a driver or firmware bug that's normally avoided by unlocking the screen?

 

[libove]

I may also be seeing this on dumpling (OnePlus 5T)

Thanks for keeping this phone alive with LOS.

I have been having an issue with applications not refreshing the screen when it's turned on unlocked. It started long time ago, maybe in LOS 14.1, but I'm not sure. I'm currently on the latest LOS 16 without gapps.

Strangely, it happens only when the screen is turned off and on again for the second time while the screen shows the same application. The touchscreen still works, but the screen won't refresh until it's supposed to show a completely different content (e.g. switching to another application using the home or overview button).

Steps to reproduce:
1. disable "Power button instantly locks" in the screenlock settings
2. switch to an application where sliding does something (e.g. home screen, or stay in the settings)
3. press the power button four times (screen off, on, off and on again)
4. try sliding the screen

Anyone else getting frozen screen? I tried changing various settings. I also tried a clean profile and remapping the power button to one of the volume buttons. I don't see anything suspicious in the log. Could it be a driver or firmware bug that's normally avoided by unlocking the screen?

As hugely different as the two platforms are (Wileyfox Swift, and OnePlus 5T "dumpling"), I think I may be seeing the same thing on dumpling (LineageOS 16.0 April 21, 2020 and all recent prior versions since I switched from OnePlus' OxygenOS to Lineage about eight weeks ago; build number lineage_dumpling-userdebug 9 PQ3A.190801.002 a53a4eb30f).
The symptom I'm seeing is that the screen will time out naturally or will turn off due to closing the cover, and then when I either tap the power switch or open the cover to wake up the screen, the screen does wake up but it does not show any updates to any touches - even though in fact the phone is responding to everything (just, no visual updates occur). The display will update to what the phone is currently thinking/doing if I turn the screen off and back on again (tap the power button to blank the screen, and a second later tap it again to wake it up).

Not sure if it's exactly the same thing, but it's similar enough that if it really is from the same source, then it's either not hardware related, or it's related to some hardware that these two very different devices happen to share.

I'll cross-reference this Swift thread in the dumping forum. Hopefully between the two someone will have an answer.
-Jay

 

[115ek]

Thanks for keeping this phone alive with LOS.

I have been having an issue with applications not refreshing the screen when it's turned on unlocked. It started long time ago, maybe in LOS 14.1, but I'm not sure. I'm currently on the latest LOS 16 without gapps.

Strangely, it happens only when the screen is turned off and on again for the second time while the screen shows the same application. The touchscreen still works, but the screen won't refresh until it's supposed to show a completely different content (e.g. switching to another application using the home or overview button).

Steps to reproduce:
1. disable "Power button instantly locks" in the screenlock settings
2. switch to an application where sliding does something (e.g. home screen, or stay in the settings)
3. press the power button four times (screen off, on, off and on again)
4. try sliding the screen

Anyone else getting frozen screen? I tried changing various settings. I also tried a clean profile and remapping the power button to one of the volume buttons. I don't see anything suspicious in the log. Could it be a driver or firmware bug that's normally avoided by unlocking the screen?

As hugely different as the two platforms are (Wileyfox Swift, and OnePlus 5T "dumpling"), I think I may be seeing the same thing on dumpling (LineageOS 16.0 April 21, 2020 and all recent prior versions since I switched from OnePlus' OxygenOS to Lineage about eight weeks ago; build number lineage_dumpling-userdebug 9 PQ3A.190801.002 a53a4eb30f).
The symptom I'm seeing is that the screen will time out naturally or will turn off due to closing the cover, and then when I either tap the power switch or open the cover to wake up the screen, the screen does wake up but it does not show any updates to any touches - even though in fact the phone is responding to everything (just, no visual updates occur). The display will update to what the phone is currently thinking/doing if I turn the screen off and back on again (tap the power button to blank the screen, and a second later tap it again to wake it up).

Not sure if it's exactly the same thing, but it's similar enough that if it really is from the same source, then it's either not hardware related, or it's related to some hardware that these two very different devices happen to share.

I'll cross-reference this Swift thread in the dumping forum. Hopefully between the two someone will have an answer.
-Jay

If you're on an official version please open an issue.
That way some more developers may look into it.

---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------

If someone has some minutes left: Could you take some wifi speed measurements? With and without using bluetooth. Is there any difference? And how are "settings/locations/wifi and bluetooth scanning" settings affecting the situation?

Edit: It would also be interesting if gapps are installed or not.

 

[quho]

Not sure if it's exactly the same thing, but it's similar enough that if it really is from the same source, then it's either not hardware related, or it's related to some hardware that these two very different devices happen to share.

That's interesting. I think there is a small difference. At least in my case, turning the screen off and on yet again doesn't fix it. I always have to switch to a different application, or start one if I was on the home screen, to get it working again. One thing that I forgot to mention is that the quick settings menu pulled down from the status bar shows up fine. It looks like it's only the window of the application that was shown before the screen was turned off that breaks.

 

[quho]

If you're on an official version please open an issue.
That way some more developers may look into it.

Ok, it's the issue #1899 on gitlab.

If someone has some minutes left: Could you take some wifi speed measurements? With and without using bluetooth. Is there any difference? And how are "settings/locations/wifi and bluetooth scanning" settings affecting the situation?

With iperf running in termux I see about 24-30mbit/s download speed. That's on a 20MHz channel. Enabling bluetooth and location doesn't seem to have a significant effect.

 

[libove]

That's interesting. I think there is a small difference. At least in my case, turning the screen off and on yet again doesn't fix it. I always have to switch to a different application, or start one if I was on the home screen, to get it working again. One thing that I forgot to mention is that the quick settings menu pulled down from the status bar shows up fine. It looks like it's only the window of the application that was shown before the screen was turned off that breaks.

Ah, ok then, it's definitely a different issue. Thanks for pointing that out.
Oh, well; and good luck!