Wileyfox Europe Limited is in Administration. Andrew Andronikou and Andrew Hosking are appointed joint administrators and act jointly and severely without personal liability.

As of now I no longer work for Wileyfox, I will still try to provide some support for you but it will no longer be official.

I'm afraid I won't be able to answer such questions as "What will happen to my phone that's off for repair"

I will try to answer what questions I can that you ask but I don't have many nor can I provide many answers.

Today is a sad day not just because I lost my job but because I believed in the Wileyfox brand :(

-Jack

Hello #TeamWileyfox

As many of you will have noticed, the official 8.1 Oreo update has started rolling out to the Swift 2 range and will aim to reach all Swift 2 devices over the coming weeks.

Below you’ll find a (hopefully) comprehensive and constantly updated list of known issues and limitations that have so far been discovered in the build released Tuesday 6th June (UOS224B) for the Swift 2 range.

A NEW BUILD OF 8.1 OREO HAS STARTED ROLLING OUT FOR THE SWIFT 2 RANGE (link)

Please note: The release has been temporarily halted whilst issues with device charging are investigated.

Current known issues (Acknowledged by Wileyfox)

1. SMS and Call logs being deleted after the update to 8.1 (Link)

2. Devices not charging quickly (Link)

3. Device is not charging once the battery has drained (Link)

4. Notification/quick toggle pull down changes colour sporadically (Link)

5. Some settings not restored correctly after hard-resetting and restoring from Google account (Link)

FAQ about 8.1 Oreo updates

Q: I've updated to 8.1 - where is TrueCaller?

A: TrueCaller was replaced with the Stock/AOSP dialler as part of the 8.1 Oreo update.

Q: Why doesn't Picture In Picture not work?

A: PIP is not supported by the processor used in the device, the Snapdragon 430. Unfortunately this looks to be an oversight on the marketing side of things as the update was advertised to have PIP upon receipt of the update.

Q: My Wileyfox Swift/Storm/Spark hasn't got the update yet, why?

A: Wileyfox are still looking at providing the 8.1 Oreo update for older devices but due to lack of support from Snapdragon, this may take a little longer to get out the door. As of now, there is uncertainty around updates on some devices. We have limited information on the status with the exception of the following: Swift 1 | Spark

Q: When will the 8.1 Oreo update start rolling out again?

A: Sources 1 | 2 have stated that an updated 8.1 Oreo build is close to release, so expect an update later this week or maybe earlier next week.

Q: How can I raise a bug?

A: The best way to raise bugs with Wileyfox is to speak to their online chat team on their website. The online chat team will triage your issue and escalate to the relevant team if they can not help you personally. Rest assured your issue will be sent to the right people and you will receive an email update once the ticket has been picked up.

Moving forward

I and the mod team will try and keep this thread updated as often as possible. If you have anything else to feel free to DM one of us. If you spot anything that needs a correction, please DM me.

Hey hey! The anticipated Android 8.1 Oreo update for the Swift 2 Range devices is here! Whoop!

Keep an eye out for a notification to upgrade. We are doing a phased rollout, so you may not receive the notification immediately, hang tight as it will get to you!

Hope you enjoy your new cookie 😊

#TeamWileyfox

https://www.techradar.com/news/wileyfox-is-back-new-handsets-arriving-this-year-and-more-good-news-for-owners

We've finally managed to get approval for replacing all our Wileyfox phones with Moto G6 series for business phones, thought I'd provide some feedback of what it was like to be a business customer of Wileyfox. We became customers of Wileyfox when the original Swift came out.

We have:

Wileyfox Swift (original)

Wileyfox Storm

Wileyfox Swift 2 series (original SKU)

One Wileyfox Pro for testing (this was free)

This is not meant to be a rant or overtly negative but to give Wileyfox an idea of what it should be doing / looking after for business users.

- MDM would not and never deploy correctly due to Truecaller interfering with Sophos, in more recent updates hard locks due to MDM

- In the most recent updates we found that our original Wileyfox Swifts kept on getting slower and slower to the point we had to factory reset the devices

- Random failures on upgrades and random restarts

- On upgrades some of our devices would randomly stop working and would only start working when we reflashed from recovery due to the misreporting of the size of the recovery and data partitions

- Our recovery partitions suddenly consuming 100% of space and then being unable to turn on, flashing got around the issue

- Batteries failing to charge leading to the Wileyfox Storm being unable to turn on, yes tried different chargers and cables

- Wileyfox Swift 2 series in the most recent upgrades crashing and getting stuck in a boot loop once they had updated because we had the crazy idea that we should encrypt our devices in a business environment, advice was to unencrypt our devices and keep then unencrypted. Sophos MDM has these modes set, getting them unset resulted in SOPHOS asking us to change supplier for our phones

- Complete lack of support on the above issues, live chat saying call the UK number, waiting 30 minutes and then giving up with lack of answers. When we did get through all the support was scripted and not really listening to what we were saying

- Don't advertise talking about how great you're new phones are, whilst the existing ones do not work or work as intended. I know this is a marketing company but still

- Advise us not to use our MDM solution, when it works perfectly fine on any other type of Android phone

- MiCollab should work out of the box as standard android, lagging shouldn't happen or interfering with truecaller / audio settings or be incompatible

- When our CEO says our current solution isn't working, forward this to our manager or someone in charge. Really don't continue to read from the script

Good example:

New Moto G6 > Deploy Sophos > Reboot > Deploy our Apps > Done

New Wileyfox Swift 2 > Add workaround in a custom package to prevent use of encryption > Disable wireless and data > Enable unsafe apps due to being an unsigned application on an SD card > Deploy Sophos from SD > Enable wireless and data > Reboot > Add workaround for truecaller > Reboot Again > Disable updates to prevent Oreo downloading > Deploy our Apps > Reboot > Hope it works > Done or start again

What we did instead was to flash with LineageOS for our earlier Swift and Storm devices which skipped all these problems, Wileyfox Swift 2 series is not yet officially supported

We have seen around a 50%~ failure rate of our phones that have encountered failures, even for the same version and product SKU. Seemingly random failures, it wasn't until after sales support wasn't provided that we started to learn the hardware and then figure out most of these were software issues disguised as hardware issues that we could reflash the devices to get them working. Again this isn't really a business type phone and I wouldn't recommend them for anyone.

Again this is not to say there hasn't been a benefit of using Wileyfox, I've learnt a lot about Android and how to work around these issues. I'd say support wise we've become quasi gods at fixing the devices internally and overcoming issues with the devices. But in a business environment we really shouldn't need to reflash phones to use them in a business setting or using custom firmware to get around these problems.

If Wileyfox is serious about the business market like the Wileyfox Pro (we did get a free one so thank you) then its probably worth looking at use cases a company would have for them or look at what your competitors are offering

Just got the download notification. 950mb+. Installing

Verified Wileyfox

Starting today you'll see a few people on the subreddit with a Verified Wileyfox tag, these are official employees of Wileyfox and are here to help out and engage in the community we have here!
These members are currently /u/Wileyfox-Beck, /u/Wileyfox-Jack, and /u/Pobi-wan.
They'll be around and helping community members with questions, product launches, and various other community events in the future!

How do I know who is verified and who isnt?

You'll be able to know by the orange Verified Wileyfox tag next to their name which looks like this.

What does this mean for the subreddit?

Well we aim to bring product launch info and news direct to here, Possible AMAs with the Wileyfox Team in the future, and other great community events for y'all to look forward to.
This also means questions can get direct responses from Wileyfox staff!

Welcome to our Community, Wileyfox!

Thats all for today but I hope to bring you even more good news in the future!

The Swift 2+ is the first phone I properly owned, not a gift nor a hand-me-down, saved up to buy myself. For what it was worth, it was a brilliant little device, and I loved it...

I never so much as scratched it, but its finally started to show its age. First the light sensor failed, plunging my front camera into eternal darkness, then it started glitching out, randomly closing my apps, crashing, and sometimes just boot looping....

Knowing about Wileyfox's situation and the fact the poor thing hadn't seen an update in more than a year, I knew it wasn't going to be fixed, so I decided it was time to finally retire my Swift while it still worked...

That brings me to now... I saved up and got myself a new phone, which I'm using now to say Goodbye. You made some great phones, and had things been different, I'd be buying from you again, but alas I won't be... Thanks for a great 3 years, Goodbye Wileyfox!

Welcome one and all to the new /r/Wileyfox!

I've recently taken ownership / top mod role here as I would like to see this subreddit strive for such a passionate community.
I've already worked on redoing the CSS and plan to get a Wiki up and running in the coming weeks!
You may recognize me from /r/Essential where I work with the community and Essential with many things and CSS work there.

Anyway, I hope to bring this subreddit some activity and promote some good discussion over here! I look forward to this quite a bit and the changes to come.

My first gen Wileyfox Swift has been retired. I got it as soon as it was released and was honoured with years of faithful yet charmingly glitchy service. I never cared that you would overheat at the mere thought of taking a picture, it made me see the world less through a lens. That restarting you meant a 5 minute wait, gave me time to make a tea. That you would randomly change which sim card was the default messenger, I got to catch up on some foreign friends.

You were tough, I dropped you countless times and yet you had barely a scratch. You did me proud little phone. Cheers.

Thanks to ZeroWhizz for pointing this out.

Build UOS273C is rolling out now to the Swift 2 range - check your phone folks!

Notable changes so far (from initial 8.1 Oreo build):

• June security patch (updated from May)

• Fix for notification shade changing colour when the background image is changed

• Assumed fix for charging issues (not confirmed yet)

• Fix for SMS/call logs being deleted between 7.1.2 > 8.1 update

I just spoke with somebody (who shall remain unnamed) at Wileyfox using the live chat on the website, I hope they don't mind me sharing the good news. From my short conversation, I have learned the following:

• Oreo will hopefully be rolling out to the Swift 2 lineup by the end of the month, but no promises were made on the time frame.

• The Oreo update will have pre-installed Amazon apps which can be uninstalled.

• A new 'Care' app will be included for easier customer support.

• The Oreo update will replace Truecaller with "the more reliable stock application" (their words, not mine). I assume this means Google Dialler or something similar.

• VoLTE support won't be included in the next update (for various technical reasons), but "if enough customers ask for it, it is definitely something they (the developers) would consider in future updates".

Stupid me forgot to ask about Oreo for the original Swift phones, sorry about that.

We're on the hunt for some feedback on our devices and would like to know what you guys would like for our next device.

What would you like to see?

Swift Gen-1 Android 7.1.2 SW44_7.1_20180110_TOS373K

• OTA Rollout to end users/customers has started

• Only customers on this SW will get this update: TOS317M

Fixes Included:

• January 2018 Security Patches

• Spectre vulnerability patch

• Minor UI improvements

Storm Android 7.1.2 SW30_7.1_20180110_TOS373M

• OTA Rollout to end users/customers has started

• Only customers on this SW will get this update: TOS318C

Fixes Included:

• January 2018 Security Patches

• Spectre vulnerability patch

• Minor UI improvements

Spark X

OTA Release Plan for End users:

• OTA Rollout to end users/customers has started

• Only customers on this SW will get this update: TNS318D

Fixes Included:

• January 2018 Security Patches

• Spectre vulnerability patch

• Zen disappearance issue

• Minor UI improvements

Add-X update

For Swift2/Swift2+/Swift2X

OTA Release Plan for End users:

• OTA Rollout to end users/customers has started

• Only customers on this SW will get this update: TOS310H

Fixes Included:

• January 2018 Security Patches

• Spectre vulnerability patch

• Newsfeed feature added to Add-X (updated SDK)

• Some general UI improvements

To answer some common questions that we get asked around update time.

• "I've not got my update yet, why not?"

The update is rolled out in batches if you've not got it yet give it time it will arrive soon, I only got mine this morning.

• "Where is Oreo?"

We are working on it, I have a version of it sitting on my desk and its being tested.

• "Where is Alexa?"

She is also on her way but I cannot comment on when she'll arrive I'm afraid.

• "I've emailed customer service and I've not had a reply yet"

They are working as hard as they can, the team was hit with a nasty flu bug and they've been running at reduced numbers"

I hope you all find this information helpful!

-Jack

*Edit - Adding updates about new rollout

In the current update, they added a feature called Wileyfox Zen. It's a news feed which is integrated into Android, and I wanted to warn you people about it:

• It collects location and WiFi data, amongst other things.

• It sells your data to advertisers.

• It cannot be uninstalled.

• Since it's integrated, it's permissions can not be turned off.

This is ironic since the device came with cyanogen and had enhanced privacy. But apparently they turned evil.

What you need:

A computer with adb on it (do a google search to find out how to get adb)

A good working SD card

Some patience

IMPORTANT: Everything will be removed from your phone!!!!!!!!!!! Make a backup if you want to keep your files.

!!!!!!!!!!!!!!!!!!!!YOU DO THIS AT YOUR OWN RISK!!!!!!!!!!!!!!!!!

Bugs/Not working: VoLTE

Download the following files to the mentioned device/folder:

- Download TWRP_Treble.img on your computer: https://yadi.sk/d/OmCp50PQBI0LLw

- Download the repartition script on your sd card: For wileyfox 2: https://yadi.sk/d/cufa3pdSQbZn7w

For Wileyfox 2+ and 2x: https://yadi.sk/d/5d7so5g1_bubCw

- Download Treble vendor on your sd card: https://yadi.sk/d/3NdLDUxQcrJ3Xg

- Download Treble boot on your sd card: https://yadi.sk/d/0gIzOEuW0aLZDg

Google drive links: https://drive.google.com/drive/folders/10RqsO1yRkyz0A5MYB5RqNcXTh64-8FQu?usp=sharing

- Download Android Pie Pixel experience gsi image on your sd card (UNZIP IT FIRST AND MOVE THE IMAGE FILE TO THE SD CARD)

https://github.com/EnesSastim/Downloads/releases/tag/PE-A-2018-12-07

(If you want something else, keep in mind that the ROM should be arm64 A-only and nothing else.)

- Download this patch (zip file) on your sd card: https://drive.google.com/file/d/1cGyvneizuIBEuy37Gyw240QgHnkDDPdc/view?usp=sharing

1- You need to unlock your phone bootloader. To do this go to settings > System > about phone > Build number and press the Build Number 7 times. The developer options are now activated.

Go to the developer options and activate ‘Allow OEM unlocking’. Turn on USB debugging on your phone via the developer options and connect your phone to your computer with a USB cable.

Open command prompt and type the following command: cd path/to/adb/folder For example: The adb folder in my laptop is located in C:\adb so I type cd C:\adb

To make sure that USB debugging is working and that your phone is connected properly, type the following command: adb devices you should see your device listed there.

Now it’s time to really unlock the bootloader:

First you need to boot your phone into the bootloader. Type this command in CMD (or boot to the bootloader manually via your phone):

adb reboot bootloader

Once your device is in bootloader mode, type the following command to unlock the bootloader:

fastboot oem unlock

You will get a confirm screen on your device press volume up or down to highlight Yes and then press the power button. The unlocking process might take a couple of seconds. This will include a factory reset.

Once your phone is unlocked, we can move on to the next step which is Installing the treble compatible TWRP.

2- Go to your phone and activate the developer options and then USB debugging.

Download this TWRP image on your computer and move it to the adb folder. Boot your phone into the bootloader and follow carefully what I say:

Type the following command to flash TWRP

Fastboot flash recovery TWRP_Treble.img

This is where things get a bit complicated, you have two different ways:

First one: If you booted to the system, TWRP will be automatically replaced with the android recovery, but if you install some ROM like Lineage OS 15.1 before rebooting, TWRP will not be removed. This is just in case you don’t to install Android Pie or Treble anymore. If you want android pie and treble, read the second way.

Second one: Boot directly to the recovery after flashing TWRP and insert the SD card where you placed all the downloaded files and let the fun begin.

3- DO CAREFULLY WHAT I SAY:

From TWRP go to 'Install'

Select storage and select your sd card

Install the repartition script, after installing it your phone will automatically reboot into recovery where you must do the following things:

Format data (Go to 'Wipe' and press ‘Format Data’)

Wipe Vendor (Go to Wipe> advanced Wipe > select 'Vendor' and swipe to wipe)

Reboot to the recovery (Go to 'Reboot' and select 'Recovery')

4- Now you must flash Treble vendor, go to 'Install' and select PT_Stable_Upstream_f.zip

5- Flash the treble boot. Go to 'Install' and select the option in the lower right corner ‘Install Image’ and select Boot_Treble_New.img and flash it as Boot image.

6- (It’s maybe a good idea to first wipe System, data and cache just in case) Now you will have to install the system. Go to 'Install' and select the option in the lower right corner ‘Install image’ and then select PixelExperienceP-arm64-aonly.img and flash it as System image.

7- We are almost done. Go to 'Install' and flash pixelexperience_071218.zip . This patch will solve a fingerprint issue.

Reboot your phone (Go to 'Reboot' and select System, ignore the No OS is installed thing.) and Congrats! You have now android pie on your Wileyfox 2/x/+

The screen size might be a bit small or big. Solving this is pretty easy. Go the settings > Display > Advanced > Display size and set the size you want. I find ‘Larger’ the perfect display size for my phone.

UPDATE :

I uploaded everything (except Pixel Experience & Magisk since I am not allowed to do so) to my google drive. Here is the link: https://drive.google.com/drive/folders/10RqsO1yRkyz0A5MYB5RqNcXTh64-8FQu?usp=sharing

3 New important things: 1- Flash nfc_gsi.zip from TWRP as a zip file (Install > select nfc_gsi.zip). NFC will work stable after flashing this

2-Device certifcation may fail. Flash certification_patch.zip from TWRP and you are good to go.

3-if you want google pay you need to have magisk on your phone and you need to flash a patch in order for SafetyNet check to pass. Here is how to do it

:- Download Magisk from here: https://github.com/topjohnwu/Magisk/releases/download/v18.0/Magisk-v18.0.zip and flash it with TWRP.

-Install Magisk manager (https://github.com/topjohnwu/Magisk/releases/download/manager-v6.1.0/MagiskManager-v6.1.0.apk)-Download this module: https://drive.google.com/open?id=1FGhHmnXszMXEbVIsYXhqBqd9ACWeYrAa-Go to magisk manager > Modules and install the module you just downloaded.

Dont forget to hide magisk from the apps that check if your phone is rooted (bank apps, google pay, etc..)

Sources: device certification zip: https://4pda.ru/forum/index.php?showtopic=892755&st=10920#entry80539089

Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Safetynet fix:

https://4pda.ru/forum/index.php?showtopic=894518&st=2820#entry77365633

Everything in this guide is thanks to the great community of XDA and 4PDA. Links to the original posts:

Project Treble: https://forum.xda-developers.com/swift-2/development/project-treble-wileyfox-swift-2-plus-x-t3848703

Pixel Experience: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/9-0-pixelexperience-p-t3833294

fingerprint issue fix: https://4pda.ru/forum/index.php?showtopic=892755&st=6880#entry77398579

After a factory reset of Android 7.1.2 my default dialler was Truecaller once more. I was fed up of it bugging me to set it up as my default messaging app, so I once again replaced it with the Google Dialler as follows:

Settings > Security Enable Unknown sources

Download the apk from https://forum.xda-developers.com/android/apps-games/app-google-dialer-t3557412 I selected the non Bubble version 11.0.164102751. The more recent version 13 seems to have a number of bugs and I want my phone to work reliably. Read all of the original post to understand the limitations of this apk.

After downloading install the app, then make the following settings changes: Settings > Apps > cog Phone app > select Phone (Truecaller shows up as Telephone)

Settings > Apps > cog > Special access > Modify systems settings > Phone > Allow modify systems settings Telephone > disable allow modify systems settings

Now open Phone and access each tab so Android asks for permissions to access phone, calls. For some reason the contacts tab doesn't work properly so head to Settings > Apps > cog > App permissions > Contacts and toggle Phone - this fixed it for me. You may want to remove Telephone's permissions to contacts, phone and other things.

Once this is done, Truecaller should be dormant, and the Google Dialler can make and receive calls, with notifications working as expected.

Now just drag the Phone icon to a convenient place on your dock.

Unlike last time I tried, the calls history lists all calls immediately.

Share any other tweaks you may have discovered.

Unofficial Lineage OS 16 (Based on Android Pie) is now stable and available for Wileyfox swift 2/x/+ . It has a better battery life, no issues with fingerprint and better compatibility.

Issues: Permissive SeLinux

This is NOT a gsi image. It is a normal ROM just like any other one. Just download it and flash it via TWRP

Link to thread: https://forum.xda-developers.com/swift-2/development/rom-lineageos-16-0-wileyfox-swift-2-t3906452

Oh look it is the 2nd of june and another self imposed oreo deadline by wileyfox has been missed. I really do not like been lied too, I would rather been kept in the dark. This company is starting to worry me, it likes your money but can not be bothered with customers after the sale. I suppose, as much as I like my phone it might be time to vote with my feet and get another brand.