[ROM][UNOFFICIAL][OREO] LineageOS 15.1 for Wileyfox Swift 2/Plus/X

[beamscotty]

I have an annyoing problem with my Swift 2, which started like a week ago: Every (almost) time I wake the device up, using fingerprint or PIN - no difference - the touchscreen remains unresponsive for a random time which lasts from a few seconds to several minutes, after which the screen works normally again until the next time it wakes up from sleep.

When this started, I was in Lineage 14. I am now on crDroid 8.1 which I dirty-flashed with no apparent issues. I have tried factory reset, wiping, installing both Lineage 15 and crDroid 8.1 from fresh, but the problem still remains. I'm starting to think this is hardware related.

Has anybody had this problem? Also, are there any logs one could catch to see what is going on?

The system is not frozen, because I can see the status bar update (data traffic counters in crDroid, for example) it is only the touchscreen which is unresponsive for a while.

 

[pinckston]

I have an annyoing problem with my Swift 2, which started like a week ago: Every (almost) time I wake the device up, using fingerprint or PIN - no difference - the touchscreen remains unresponsive for a random time which lasts from a few seconds to several minutes, after which the screen works normally again until the next time it wakes up from sleep.

When this started, I was in Lineage 14. I am now on crDroid 8.1 which I dirty-flashed with no apparent issues. I have tried factory reset, wiping, installing both Lineage 15 and crDroid 8.1 from fresh, but the problem still remains. I'm starting to think this is hardware related.

Has anybody had this problem? Also, are there any logs one could catch to see what is going on?

The system is not frozen, because I can see the status bar update (data traffic counters in crDroid, for example) it is only the touchscreen which is unresponsive for a while.

Having a similar problem here, but not identical. My touch will randomly freeze up every so often, but a screen off/on sorts it out. I have posted a logcat of this a few pages back but had no advice on the issue, don't have the ability to interpret the logcat myself! ?️?️

 

[vm03]

I have an annyoing problem with my Swift 2, which started like a week ago: Every (almost) time I wake the device up, using fingerprint or PIN - no difference - the touchscreen remains unresponsive for a random time which lasts from a few seconds to several minutes, after which the screen works normally again until the next time it wakes up from sleep.

When this started, I was in Lineage 14. I am now on crDroid 8.1 which I dirty-flashed with no apparent issues. I have tried factory reset, wiping, installing both Lineage 15 and crDroid 8.1 from fresh, but the problem still remains. I'm starting to think this is hardware related.

Has anybody had this problem? Also, are there any logs one could catch to see what is going on?

The system is not frozen, because I can see the status bar update (data traffic counters in crDroid, for example) it is only the touchscreen which is unresponsive for a while.

Having a similar problem here, but not identical. My touch will randomly freeze up every so often, but a screen off/on sorts it out. I have posted a logcat of this a few pages back but had no advice on the issue, don't have the ability to interpret the logcat myself! ?️?️

Check on stock. I think it hardware problem with touchscreeen.

 

[pinckston]

Yeah, happens on stock too, but it's so random it still makes me think wileyfox have buggered up somewhere on the software front!

 

[vm03]

Yeah, happens on stock too, but it's so random it still makes me think wileyfox have buggered up somewhere on the software front!

No. It hardware problem. I got this much more on replacement screen from aliexpress (i think defective parts, rejected by factory, sold on ali) .

 

[qok7650r3u]

I just installed the latest build, and it seems alarm and notification sounds are not playing at all, staying completely silent instead. The build from the 20th of September seemed to have some similar issues with alarms, but the one from the 28th worked perfectly.

I made my own build with the latest source, but threw out the

32936bef04e0f15f326e4ebb09f7a881139b5621 
1c69a9a3354f07b4dca957a927580b903b3ca92d

commits from the 12th of October. Notification sounds work again. I checked, and my phone is the version with the AW87319, so that seems to have something to do with it if the sound in the recent build works for everyone else.

 

[vm03]

20181026:
- fix fingerprint auth in some apps
- upstream updates

 

[Abdullah S.A.]

Now that this ROM is stable and bugless, perhaps it's time to make it official? If the contributors want of course...

 

[fred0r]

2 things on latest:
- when using opengapps and selecting 'backup from another android-phone (cable less) a long time afterwards the initial setup, i just get a black screen shown. until now i have not used any google-login on that installation.
- (perhaps offtopic) just tried to remove the 'Mic and Cam'-Icons from the Lockscreen and was unable to find the options to remove them.

 

[TheDevFreak]

Now that this ROM is stable and bugless, perhaps it's time to make it official? If the contributors want of course...

IIRC the maintainers here just need to bring it up to lineage charter if it's not already then contact lineage to get it official

Yep the maintainers just need to follow this guide https://wiki.lineageos.org/submitting_device.html and then ensure they are compatible with the LineageOS Charter https://github.com/LineageOS/charter

 

[dryhte]

IIRC the maintainers here just need to bring it up to lineage charter if it's not already then contact lineage to get it official

Yep the maintainers just need to follow this guide https://wiki.lineageos.org/submitting_device.html and then ensure they are compatible with the LineageOS Charter https://github.com/LineageOS/charter

@vm03, please do... :good:

 

[vm03]

@vm03, please do... :good:

I don't have extra free time for it...

 

[nikith290]

@vm03, please do... :good:

IMHO, It's pointless.

Specifically for the device, little will change, because we already fully meet the requirements, and nothing gonna be more stable or something.

But.

This is an extra headache for vm03, me, DinD_Ykt and other people directly or indirectly involved in the development. More time will have to be devoted to the maintenance, which is not always possible in most cases.

If you want the official build, you can try to do it yourself. =)

 

[dryhte]

Ok... but from you guys' perspective, the ROM is stable/final now?

 

[waver1967]

@vm03
thanks,
you did it again.
a lifesaver build for lg l70 d320n and now a perfect build for the swift 2x .
you'r a boss.

 

[ianvt]

Call quality

Since I updated to the latest build the call quality is just horrible. People can't understand me and there is lots of static and clipping on the line.

 

[vm03]

Since I updated to the latest build the call quality is just horrible. People can't understand me and there is lots of static and clipping on the line.

Mobile call or internet call (like skype)?

 

[Mawfingerer]

Finally took the plunge and updated from 14.1. Didn't bother putting any google stuff on just vanilla lineage and gotta say working pretty sweet so far. To all guys/girls who contribute to keeping this maintained thanks for your hard work and dedication!

 

[puszekkk]

Are there any plans of releasing Lineage 16 or we are forced to use bugged GSI-s?

 

[Sad_Salo]

Mobile call or internet call (like skype)?

Таже проблема в мобильном звонке и мессенджерах. Swift2