yashsingh1/xdaforums huggingface dataset:
[Wileyfox Swift] nullstuff:
it worked here, too! thank you very much! :good:

btw, to apply all the OTAs, one needs to flash stock recovery too (found it inside fastboot packages).
[Wileyfox Swift] zappbrannigan62:
Regarding encryption

First of all, a big thank you to [MENTION=2836769]jrior001[/MENTION] for this ROM.

I recently upgraded from 14.1 (unencrypted) and am now happily running 15.1 without any issues.

But I wonder:

IIRC, all 15.1 devices must support encryption - is this true for crackling as well? I never got it to work (neither on CM nor LOS), so is it working now with 15.1? Also, does the version or TWRP linked on page 1 of this thread support encryption as well?

Thanks,

Zapp
[Wileyfox Swift] jrior001:
Encryption support has always been mandatory, though I can't really speak to any pre-15.1 issues on this device since I just took over support recently.

Encryption works fine, keep in mind though this device is slow already and it will take a performance hit being encrypted.

As for TWRP, OTA's should work without issue(may need a newer build for this?) but currently we cannot decrypt in Twrp for data backups and things like that. This is something we had working in 14.1 based world but have not yet been able to figure out in 15.1.
[Wileyfox Swift] zappbrannigan62:
Thanks for the quick reply.

As I am applying the updates manually, but always do a backup before (I know that's boring, but has proven to be useful now and then), I guess I'll keep it running unencrypted. I suppose making this work is not a prio, is it?

Thanks,

Zapp
[Wileyfox Swift] jrior001:
Not really. The only bugs I'm excited about are the video issues in WhatsApp/Instagram. I have a fix but it breaks other things...

Other than that my time is better spent working on Pie instead.
[Wileyfox Swift] Anahermun:
[MENTION=2836769]jrior001[/MENTION]: Thanks for your work!

Regarding TWRP: There have been issues with encryption/decryption with other devices as well. Most of them seem to be fixed with 3.2.3-1/3.2.3-2. Just out of curiosity: What seems to be the problem/challenge with TWRP and *cryption for swift? Just asking because as of now once a device is encrypted it's not possible to update - which is kind of bad....
[Wileyfox Swift] jrior001:
I may need to run a Twrp update again for these devices, they definitely fixed the not being able to update without decrypting issue.

If you've got an example of a similar device that's fixed decrypt I'll gladly take a look at what they may have done.
[Wileyfox Swift] Anahermun:
That would be great.

So from what I could find out it was the same or very similar error with potter (moto g5 plus):

The thread about a solution is here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1153

It was also fixed for the oneplus 5: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1193

And for Pixel: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1169

So I guess you would just need to take a look there.

Does this help? Or would you need it more specific?
[Wileyfox Swift] Shotg1:
Dunno whats the problem i install the latest nigtly build 1029 but fc for all apps, cant even pass on setup
[Wileyfox Swift] Mac23:
Confirmed!

Yesterday I tried to upgrade my Swift using this build and got also fc. First I thought it was my fault but it seems to be something wrong with 1029. The build before finally worked.

But I have some questions:

- does it matter if I do the upgrade using gapps nano, although LOS 14.1 was installed using gapps micro before?

- 15.1 reports my SD card as corrupted - with 14.1 it´s working fine - what´s wrong with that? Could it be the second ext2 partition (in former times used for link2sd) on the SD? The first partition is exFAT. I don´t use encryption.

- despite the upgrade I lost the layout of my customized folders/app on all home screens

- is it possible in Trebuchet to get back the app drawer icon (these dots) in the lower middle of the screen?
[Wileyfox Swift] petexd:
Both our phones upgrade with 1029 without a hitch. I did a full install on mine and ota on my wife's. No problems.

What on earth is fc?
[Wileyfox Swift] Mac23:
fc = forced closure (of an app).
[Wileyfox Swift] petexd:
Thanks.
[Wileyfox Swift] Mac23:
I think I was wrong. Yesterday I did a clean install and no fc anymore with build 1029. It took me severel times to install as I always got stuck with the LOS boot animation. It seems that this was solved by changing from MindTheGapps to OpenGApps, although MindTheGapps are the recommended Gapps :confused:.

Experiences so far:

- SD card still corrupted - but working fine somewhere else (I will try to reformat it, as already mentioned)

- could someone confirm this? => changing the "Preferred network type" in "System profiles" closes the Settings-App (fc) - EDIT: it´s a confirmed bug

EDIT:

figured out the reason for the corrupt SD:

- formated SD in LOS 15.1: SD was formated as FAT32 and worked

- formated SD in Win7 as exFAT: SD did not work => corrupted

Conclusion: As of now LOS 15.1 does not support exFAT (but LOS 14.1 did!) :(

Found also this thread and this one.
[Wileyfox Swift] petexd:
Why a daily update?

Does anyone know why we're getting an update every day for the last week and a half. There doesn't seem to be much changing so I would have thought the normal weekly would do it. I assume it's not vital to pick everyone up (although it's not that difficult or time-consuming).
[Wileyfox Swift] robin0800:
LineageOS said they were moving all 15.1 to a daily schedule as it will make it easier to port "pie" when they are ready to do so. Though I've seen nothing as to why this should be so.
[Wileyfox Swift] petexd:
Thanks Robin0800. It seems an odd decision. I can't see the connection with changing to pie but then I'm no expert.
[Wileyfox Swift] oliverjames:
My experience with Pie is that it's far better than Oreo in terms of battery life and smooth operation.
[Wileyfox Swift] petexd:
I'm not saying pie isn't better than oreo. It just seems odd that daily updates of oreo will make changing to pie later, any easier to do.
[Wileyfox Swift] r25txe:
I know this is old, but not receiving MMS until you activate mobile data on the SIM the MMS was sent to is perfectly normal. The mobile network is sending you the message, and only to the number it is sent to, via the SIM card on the network.

Even if both your SIMs are the same network it still needs to be delivered via the mobile data tied to the same SIM.
[Wileyfox Swift] Telcoced:
Thx [MENTION=3748537]r25txe[/MENTION] for your answer and your interest. I agree with the point that data must be enabled on the SIM receiving the MMS, but I've been owning 3 different dual sim phones, and each stock ROM was able to automatically switch data between SIMS for a few seconds just to receive the MMS, without manual switching needed. My message was more or less a feature request, I should have explained it more clearly.
[Wileyfox Swift] r25txe:
Is this ROM f2fs compatible with the included kernel?

I seem to have lost access to my f2fs /data partition and my internal storage

It's strange, I did an initial setup earlier and things were fine, but neither the built in file manager or FX File Explorer can see my /data partition.

In TWRP (Flaming Skull version) there are no issues and I can browse the partition and internal storage without issues.
[Wileyfox Swift] andreas82g:
hi guys,

i need you help updating to LOS 15.1.

after the upgrade from LOS 14.1 to 15.1 i stucked into the boot animation without any success to bring 15.1 to boot completly.

i updated according to the lineageos wiki:

- flashed the new twrp-3.2.3-0-crackling.img from the twrp homepage

- than i ve done an advanced wipe of (system/cache partition/dalvik cache)

- installed the:

- lineage-15.1-20181205-nightly-crackling-signed.zip

- open_gapps-arm64-8.1-nano-20181207.zip

- addonsu-15.1-arm64-signed.zip

after i found out that the system wont boot i tried the same procedure with the twrp recovery (Flaming Skull version) of this thread without any success.

i still stucked on the boot animation.

after a google research i tried to fix the boot problem with flashing the (aboot, rpm, tz, hyp, modem, sbl1, splash) partitions like explained in this thread ( https://xdaforums.com/wileyfox-swift/help/how-to-fix-swift-able-to-boot-t3727294 ) but without any success.

i reinstalled the whole LOS 15.1 with wiping all partitions like explained above and after i stucked into the boot animation again i tried to fix it with deleting the "fota" and "misc" files explained in this link ( https://www.lineage-os-forum.de/Thread-Gelöst-Bootloop-Problem-mit-LineageOS14-auf-Wileyfox-Swift ) but still without success.

after a few more tries with wiping data again, make factory and thinks like this i decided to go back to 14.1 to get a working phone again and than happens another strange thing. ;)

i tried to reinstall lineageos 14.1 to get the phone working again in the same way like i explained above ( wiping system, cache..., flashing the LOS 14.1 zip that i used before) without getting a booting LOS 14.1.

The only way to get LOS 14.1 working again have been to flash the "stock rom" (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip) and after i checked if it is booting, i´ve done only a factory reset in twrp and flashed the LOS 14.1 zip.

than i got my LOS 14.1 working again.

than i tried to reinstall LOS 14.1 with wiping system, cache, dalvik cache i stucked into the boot animation of los 14.1 too.

what is wrong with my phone or did i´ve done something.

i really need some help because i running out of ideas how to get LOS 15.1 working on my phone.

thanks for the help and sorry for my bad english and the really large post :>
[Wileyfox Swift] almodovaris:
Tried to format the whole of /data? Hint: you'll lose everything.
[Wileyfox Swift] andreas82g:
yes, i tried nearly any constellation...

i have formated "dalvik/art cache" "cache" "System" "data" and "internal storage" and installed LOS15.1 afterwoods with same result - boot animation
[Wileyfox Swift] petexd:
When you flashed the files from the radio...zip file did you re-flash twrp?
[Wileyfox Swift] andreas82g:
yes, flashed afterwoods the skullversion and the version from the twrp homepage to test. both without any change
[Wileyfox Swift] almodovaris:
I meant using mkfs.ext4 for the unmounted /data partition. You could do that from Advanced wipe, Change filesystem.
[Wileyfox Swift] oliverjames:
Would be good if not for the random reboots

Daily OTA updates but stability appears to be getting worse.

However the last couple of OTAs appear to have solved the unexpected reboot problem.
[Wileyfox Swift] aacprime:
Bootloop happens everytime I get battery to 0% (so that phone turns off by itself). After that phone won't boot no matter what, even after clearing dalvik cache.

That's the only reason why I'm still using latest LOS 14.1 nightly instead of 15.1, which is as good as 15.1, but still I wanted to use oreo :(

Other than that it's perfect in every way and probably the best solution for our device in terms of stability and battery work, along with official CM13.1.5 which is outdated.
[Wileyfox Swift] petexd:
When it appears to have switched off at 0% battery, have you tried removing then replacing the battery before switching back on?
[Wileyfox Swift] jrior001:
My test device does this now and then, put it on a real charger( usb charging from a PC takes too long). It does not like to boot from a dead battery. It will likely boot to offline charger mode and reboot a few times but after 10 mins or so it will charge enough to be happy and boot. Not sure what that's about and it's nearly impossible to get logs from that but I will try to look into it.
[Wileyfox Swift] iYappi:
Hey guys!

Videos still don't work on Instagram with the stock kernel... Is there any ticket on the bugtracker?
[Wileyfox Swift] SartEX:
on the beta version of Instagram video works great
[Wileyfox Swift] jrior001:
We merged something a few days ago that should have resolved this on Instagram and Whatsapp video playback. Are you sure you are still experiencing this on the most recent build ?
[Wileyfox Swift] iYappi:
Thanks, I'm still using build from 23.12.2018 since there were New Year and Christmas holidays - didn't have the time to check out new builds, will install the latest one later today.

UPD: Yes, it works now! Thank you!
[Wileyfox Swift] alt-tabtab:
Several attempts to upgrade from 7.1.1 and stock rom to 15.1 with twrp-3.2.3-0-crackling following the steps on the wiki page 'Installing LineageOS from recovery', adb sideload to the letter. OK message after the install but the rom was was still booting after 35 minutes.

I installed the zip directly from Twrp, left the boot process on overnight connected to the charger but boot animation was still running next day.

The stock rom cm-13.0-ZNH0EAS2NH-crackling-signed-9c92ed2cde_recovery installs and runs normally, so the hardware doesn't seem to be the problem. Any troubleshooting tips appreciated.[IMG="adb sideload successful"]https://i.imgur.com/QSNwOz3.jpg[/IMG]
[Wileyfox Swift] oliverjames:
ETA for becoming Official?

Will this ROM be superceded by version 16 any time soon?
[Wileyfox Swift] jrior001:
There is no shipping date for 16.0 yet, and as of today these devices are not ready to migrate yet even if there was.
[Wileyfox Swift] oliverjames:
But then why are there daily OTA updates? I read some time ago that this was in preparation for a move to Android Vers. 9 (Lineage 16).
[Wileyfox Swift] jrior001:
Can't believe everything you read on the internet (yes I realize the irony as I type this on the internet).

The ability to do nightly OTA updates came as a benefit to a few new build slaves that were donated to us, and not much else.
[Wileyfox Swift] oliverjames:
Thank you for your reply, believable, which is more than can be said for much of what is published on the Internet.

I'll stay with my procedure of checking the "recent changes" list periodically and update according to that information.
[Wileyfox Swift] ArmiDuctor:
I am using opentasks in combination with davx5 and sinds the last changes my phone keeps vibrating every time it updates with the server. Could it be due to the changes in lineages? Trying to figure out what the problem is :)
[Wileyfox Swift] Thomue:
This problem is from davx5 (davdroid).

please see forums. bitfire.at /topic/1899/vibration-on-sync/24

In OpenTasks under Notifications --> Pinned Tasks. Disabling it and then reenabling it caused the option for vibrate to disappear and resolved my issue. Simply disabling the vibrate option did not work.
[Wileyfox Swift] Thomue:
Thanks for this stable and good ROM.

But GPS fix will not work correctly.

GPS fix takes 3 to more than 10 minutes outdoors. Something is completely wrong here.

GPS fix should be quick: With the recent stock ROM it took about 15 seconds. This was working fine with LOS 14.1.

Can anybody confirm this? How did you solve it?
[Wileyfox Swift] Telcoced:
I had exactly the same problem. I had to switch to a 9.0 Rom to find a fast GPS fix - I'm on Pixel Experience and quite happy with it - you can try it, CrDroid, or PixysOS, both have thread on this subforum.

I even tried before switching to 9.0, to install official Rom, in order to have an up-to-date firmware - which some believed to be the reason of the problem - and then come back to lineage 15.1, but it was unsuccessful.
[Wileyfox Swift] ArmiDuctor:
Tested it today again and although i could find 23 satellites there was never a fix. After restarting gps it also sometimes occurred that no satellites were found. Tried several apps like tomtom and osmand. Hope somebody can put some energy in it to find the problem (I would if i had the knowledge ;) ).
[Wileyfox Swift] ArmiDuctor:
Is everybody silently waiting a LOS16 build? Well I can tell you I am haha ;) Love this rom but the gps keeps annoying me. I saw some crackling changes the last days in the LOS16 change notes which spark my enthusiasm :) Lets see what will happen.
[Wileyfox Swift] aacprime:
We got oreo for our device only 6 months ago, so I wouldn't set expectations too high. Also, check this reply.
[Wileyfox Swift] Moonie_82:
I am a complete noob when it comes to custom ROMs, I have never even installed one before but I have been wanting to install LineageOS on my Wileyfox Swift for quite some time. I have been put off by posts stating that people have had difficulties installing LineageOS on Wileyfox Swifts running Wileyfox's stock 7.1.2 ROM which my phone is currently on. If I recall correctly they seem to have problems with TWRP on the device and to add to my confusion there seems to be three different versions of TWRP that I could possibly use:

1) The Flaming Skull version found on this thread.

2) A version found on the LineageOS wiki that links to a TWRP file available from Android File Host.

3) The version available on the official TWRP website (the latest version currently being 3.2.3-0).

I am hoping that one of these will work on devices running the stock 7.1.2 ROM but I have no idea which, if any, is capable of doing so, I guess you could say I am currently quite confused! Any help from the knowledgeable folks on this forum would be so greatly appreciated, thank you all so much.
[Wileyfox Swift] ArmiDuctor:
I am using the one from the official TWRP website and I never had problems flashing btw. Be aware that the GPS is not going to work well on this rom. Other then that it is pretty stable (I had a reboot last week after doing something with whatsapp video call).
[Wileyfox Swift] Moonie_82:
Thank you for your reply it is very helpful, may I ask, were you on the Wileyfox's stock 7.1.2 ROM before flashing LineageOS?
[Wileyfox Swift] FtCat:
I flashed LOS 15.1 with the official TWRP 3.2.3 0 from stock 7.1.2 but that was some time back. I also flashed a Swift with 8.1 first flashing radio-20161215-crackling from beroid's Foxy Kernel download site. TWRP would not work on the Swift stock 8.1 ROM so first flashed the image from beroid with the existing recovery before flashing TWRP. GPS does work on LOS 15.1 but it is very slow to acquire a fix and keep the fix.
[Wileyfox Swift] Moonie_82:
Good to know, thank you so much. Am I right in thinking that when you mention an 8.1 Swift stock ROM it is a typo and you actually mean a stock 7.1 ROM?

The GPS issue that has been brought to my attention is giving me second thoughts about flashing LineageOS on to my device. Is the issue really bad and detrimental to the operation of the device? Is it worth moving away from a fairly stable functioning stock ROM or would it be worth waiting to see if the issue is fixed in future LineageOS releases and installing then maybe?
[Wileyfox Swift] Thomue:
At LOS 15.1 and crdroid 5.1, GPS does not work well. Not suitable for navigation in a city between buildings or under trees.

Currently this only works until LOS 14.1 or a newer AOSP based ROM eg. PyxisOS.
[Wileyfox Swift] FtCat:
The Swift was upgraded to 8.1 at one point but I don't think went any further. If you don't use GPS daily the ROM works well. I don't use GPS regularly but I have used it for navigation successfully but have not done so in a built up area.
[Wileyfox Swift] ArmiDuctor:
Sometimes it can take an hour before it finds a fix. Well when you drive an hour you most likely are at a point where you dont know the road anymore. Problem is that you just dont know when it will get a fix. It is very random. And under trees etc is always causing problems. So if you want to use the gps on a daily basis then I would advice to use another rom. When you use it now and then and even in that case you also have another means of navigation then i would say yes install this rom. I use it as a daily driver and i am very happy. Also i have an old bluetooth gps receiver laying around that i can use for navigation. That is a good backup for when gps is essential. Hope this helps you make a discission :)
[Wileyfox Swift] Moonie_82:
I just wanted to thank everyone for all their assistance, it has been really helpful and informative. The GPS issue kind of sucks, although I do not use it often, the instances when I do tend to use it is when I am lost and need directions so reliability of this function is important to me despite me not using it all that often.

Looks like I may have to wait for a fix on this issue before I go ahead and flash it, I am subscribed to this thread so if this issue is fixed please post it on here so myself and others know.

Once again thank you all.
[Wileyfox Swift] FtCat:
Just an update on GPS. I have just flashed the latest LOS 15.1 20190314 to a new Swift, out the box, and have no problems with acquiring and keeping a GPS fix even with an overcast sky and using device only location settings. So either the problem is fixed in latest LOS or along the update chain it got broken and as I have come from a stock ROM it is still intact. Had to jump through hoops to flash TWRP recovery as it kept getting replaced on boot but followed beroid's instructions here https://xdaforums.com/wileyfox-swif...unofficial-twrp-3-0-1-0-t3350351/post70642021 and all was good. The Swift had the old fastboot.
[Wileyfox Swift] Moonie_82:
Thanks for sharing your thoughts on the matter FtCat. It is really interesting to read other peoples experiences with the ROM and the flashing process. Have other LineageOS users found that the latest build has rectified their issues with GPS?
[Wileyfox Swift] mikeioannina:
Nothing related to GPS has changed since April 30, 2018
[Wileyfox Swift] Moonie_82:
Thanks for the information mikeioannina, out of curiosity what has your experience with GPS been like on the Swift with LineageOS?
[Wileyfox Swift] FtCat:
For what it is worth I have 3 Swifts. 1 which I installed LOS 14 on when Cyanogen collapsed and then LOS 15.1 and used this until it stopped charging the battery after using it daily for approximately 3 years, updating LOS regularly. The second is my wife's which is also approximately 3 years old, this I did not install LOS 14 on but updated to the stock Swift ROM when they came out with their own after the collapse of Cyanogen and recently bought a new Swift to replace my first, this I flashed with the latest LOS 15.1.

On none of the Swifts do we keep location on at all times, in fact rarely use it. I have just taken all 3 outside and using GPS Status compared their performance. I didn't measure the time it took but all 3 took quite awhile to locate and get a GPS fix, the new one was quickest, but the fixes were stable and the time to fix was in minutes not hours. After that I brought them inside, lost the fix and took them out again, this time the fix was faster on all 3. I turned off the location settings and waited a while then turned it on again, again fixes were acquired fairly quickly on all three. It was a clear sky with no buildings nearby but there were some tall trees that would restrict a clear view of the horizon to one side but some distance away. Another point, I am in the middle of Africa, if that has any bearing, excuse the pun, on the matter. I did not have the phones beside each other in case they had an effect on each other but did notice they did not seem to fix on the same satellites and would show a different number of available satellites by 1 or 2 but did indicate the same location on all 3 phones.

My personal feeling is if location setting has been off for sometime the original fix may take a long time to acquire after that it is quicker. I don't know if there is some form of cache used to store fix information which speeds up subsequent fixes after first fix but is obviously of no use if location has not been used for a period. I only used the device GPS no WiFi or Google location assistance.