yashsingh1/xdaforums huggingface dataset:
[Wileyfox Swift] NotATechnician:
Thanks! I did "fix" it in the meantime...

For the record, the version of TWRP is the latest (at current time of writing). But for anyone else stumbling on the thread for a fix..

I took the heavy-handed approach, not only wiped the /system partition, but reformatted as ext4 (it was previously splashfs)

Flashed Lineageos 16, GApps-9-arm64.nano, and the root add-in, wiped Dalvik and Cache, reboot to System.

But it only rebooted to Bootloader, no matter how I did it. So then I flashed crDroid4.7 just because it was in the folder even though I knew nothing about it. Wipe Dalvik&Cache, reboot to system and happy days, it chugged for a while before giving me a new set-up experience.

So, I flashed the Pie crDroid (5.3) and I am off to the races. crDroid is LineageOS based, so do not ask me why one boots and the other does not, but my Crackling Wileyfox has life again. So, I am somewhat using LineageOS and very grateful for all the people who put the work in.
[Wileyfox Swift] kabu83:
Might be that the latest version is not the latest 'recommended' version of TWRP? Have you tried 3.2.3.0?
[Wileyfox Swift] FtCat:
Latest, 3.3.0-0, works for me with no issues.
[Wileyfox Swift] dedaol:
Is this rom SELinux Enforcing?
[Wileyfox Swift] jrior001:
Enforcing is mandatory on lineage officials.
[Wileyfox Swift] RoterfuX:
I can't get it working, it always fails at 47%. I tried different builds and it's always the same problem. I format the data and wiped cache & system before I did the sideload. TWRP version is the one from the lineageos wiki.

Any idea what could be the problem?

Thanks!

C:\WINDOWS\system32>adb sideload lineage-16.0-20190429-nightly-crackling-signed.zip
serving: 'lineage-16.0-20190429-nightly-crackling-signed.zip' (~47%) adb: failed to read command: No error

Edit: found this link https://xdaforums.com/showpost.php?p=69648733&postcount=47 and I'll try it tomorrow again.

Edit2: didn't work. Copied the build and opengapps Pico to the SD card and flashed it via TWRP. Worked and the phone runs again.
[Wileyfox Swift] oliverjames:
Persistent mobile network issue

I upgraded from 15.1 to 16.0 at the first opportunity. Upon returning to France from a trip to neighbouring Switzerland I saw that my French mobile service had automatically switched to piggy-backing on it's Swiss roaming partner. This has cost implications and so I've now restored my previous installation of 15.1.

The problem I have with ver. 16 is that I cannot manually select the mobile network. Has this affected anyone else?
[Wileyfox Swift] kabu83:
Indeed, it seems as if the toggle button always returns to 'auto select network', after an error message that manual selection is not possible.
[Wileyfox Swift] ArmiDuctor:
Same here. This looks like a bug indeed.
[Wileyfox Swift] oliverjames:
Yes, that is precisely what happens.
[Wileyfox Swift] DaniTD:
In general this ROM works great, except for one problem

I did a full reset of the phone after update to have a clean install. But I notice that my WiFi connection is extremely slow, I can even see on Telegram it has difficulties to connect, since it keeps on "Connecting..." every now and then. I made some test and I think I found the problem. It seems it has to do with the NearbyMessagingService service of Google Play services.

-By default, If I do a Wifi speed test with my provider, I get 1Mb download speed, 1Mb upload speed, 16ms ping and 64ms jitter.

-If I go to developer options/running services and I stop NearbyMessagingService, I get 12Mb download speed, 8Mb upload speed, 1ms ping and 1ms jitter.

Has anyone experienced this?

Regards
[Wileyfox Swift] Telcoced:
Hi there, and thanks Jrior001 - and mikeioannina ;) - for this ROM,which allow us to keep our precious alive.

I've finally switched to it today - 20190515 build - from Pixel Experience ROM, not updated anymore for this device. Everything seems to work fine, I have just two workarounds :

- Led notification doesn't work for SMS app (the led is working for missing calls or charging, so it's not an hardware problem), am I the only one ?

- A more specific problem, I can't manage to log in "Notes by Firefox" app : "failed to authenticate" message after full successful procedure. Maybe it's an app problem, but I would like to know if someone encounter the same.

Regards.
[Wileyfox Swift] oliverjames:
Bump, 2 posts have confirmed this bug. Is it possible to resolve it?

Reminder, under "Settings, Mobile network, the Automatic select network" toggle button always returns to 'auto select network', after an error message that manual selection is not possible.
[Wileyfox Swift] petexd:
I don't use this but I tested it today. I'm on the latest 16.0 and auto select toggle works on mine. I've not looked at it before.
[Wileyfox Swift] fungolfer:
slow update download

I only have one real problem with my Swift: When I download the updates the connection failes 3 - 4 times and after that the download speed is at about 252 kb/s. My internet speed is 194 MBit/s. the update download takes about 30 minutes with that speed. when downloading apps I have a much better speed. The update downloads on Lineage 15 were much, much faster.
[Wileyfox Swift] jrior001:
You need the smallest gapps package you can find, nothing else will fit.
[Wileyfox Swift] almodovaris:
Yup, that is opengapps pico ARM 64 bit for Android 9.0.
[Wileyfox Swift] libove:
Hm, ok, Pico DID fit (This time). So, what's missing?

Well, don't I feel silly....

When I first went at this a couple of months ago, I thought I had tried the pico package and it too was too big. I even had half a thought that I'd see the storage space error despite there obviously having been enough space to squeeze pico onto the device. Either something has changed in the Lineage OS 16.0 image for Swift and/or in the OpenGapps pico package since then, or I'm mis-remembering. :-}

So, I've got pico installed.

The description of the difference between the pico and nano packages is that nano includes "additional functionality NOT AVAILABLE FROM THE GOOGLE STORE", such as Google App (Search). (And a bunch of other stuff).

I do happen to like having the Google App search bar on a Home screen.

Hm. Interesting. The "Google" search app does seem to be available in the Play store.

What really is the difference then between OpenGapps Pico and Nano in terms of what you CAN'T get if you install Pico? (Not what you DON'T get by default, but what installing Pico prevents you from easily getting afterwards?)
[Wileyfox Swift] kabu83:
The issue still persists, it seems to be handled here: https://review.lineageos.org/c/LineageOS/android_packages_services_Telephony/+/243706

I don't know if or how we can upvote the process.

Living in Switzerland near the Austrian/German border, I use a global SIM card (Qynamic) for data, which works fine for me, however might be a bit pricy for EU-customers.
[Wileyfox Swift] oliverjames:
Yes that's it. Very annoying. I live and work close to the Swiss border and frequently find, after a trip into Switzerland that my phone has locked onto the Swisscom network, renown for being an expensive service. There was no way to reset the network provider to my French based one.

So I'm still with LOS 15.1, which doesn't suffer from this bug. However a fix would enable a switch to LOS16 with its probable security enhancements.
[Wileyfox Swift] fungolfer:
I had the same problem and I took the open_gapps-arm64-9.0-nano2019xxxx.zip and this one worked for me. Hope you can find it as I'm not sure where I got it from...
[Wileyfox Swift] kabu83:
Using two SIMs, when I change the data SIM in the network operator menu, it seems that the system is forced to do a network scan and logging in to the home network. Maybe you can try this workaround.
[Wileyfox Swift] oliverjames:
Thank you for your idea. It may work but it would be a cumbersome solution, made worse the constantly varying network signal strengths.

Good design should make life easier, not more complex.
[Wileyfox Swift] zomgzerg:
If you use Chrome it has a widget search bar that you could put there instead.
[Wileyfox Swift] fungolfer:
Today the update download was fast and it didn't stop several times. Thank you very much :)
[Wileyfox Swift] FtCat:
Manual selection of network works with latest update 16.0-20190608
[Wileyfox Swift] oliverjames:
Thank you for that. I'll give it a try.

I confirm that the bug is now fixed. Good work. Thank you.
[Wileyfox Swift] Philotra:
For whoever is stuck in fastboot while updating from stock (Android 7) to LOS16;

Try first downgrading your phone to cyanogenOS 13, see; https://cyanogenupdatetracker.com/downloads/

and afterwards follow the guide from https://wiki.lineageos.org/devices/crackling/install

I reverted to COS by using the fastboot package and installed the standard package afterwards (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB). Hereafter the LOS install guide worked perfectly.
[Wileyfox Swift] oliverjames:
Root problem

I discover that all's well except that the compatible addonsu zip is not giving root access. Any suggestion for an alternative means of rooting?
[Wileyfox Swift] wkn000:
Did you activate Root in Developer options after installing in TWRP?
[Wileyfox Swift] oliverjames:
No, good idea, but I didn't think of that. I solved the issue by restoring the LOS 16 image that I'd saved prior to reverting to LOS 15.1, and then letting it update OTA. Much quicker in the end.

All is now working as required.
[Wileyfox Swift] fungolfer:
And again the update took forever. I had to restart the download several times and my WiFi connection only gets around 2mb/s. On Play store I get around 42 mb/s. I have no idea if it is my phone, my fritz router or the lineage site but I never had these problems with LOS 15 and the updates until may I think.

Any suggestions?

Think I found the problem: Once I deactivated Bluetooth the speed went up to 72 mb/s. So in case of a download I have to stop bluetooth
[Wileyfox Swift] oliverjames:
Audio issue

I've noticed for a while that if I try to stream an audio signal (radio broadcast or podcast for example) the sound cuts out after about 1' 30". Has anyone else experienced this, and if so, found a cure?

Thank you.
[Wileyfox Swift] oliverjames:
More problems with LOS 16.0

In addition to the audio streams cutting out, I note that my Swift phone no longer recognises the WiFi at a friend's house (my other phone running stock Oreo does).

A further problem, the camera App is saving the photo's in the folder /Android/data/org.lineageos.snap/files/ and not in /DCIM/Camera/ which makes it hard to review or find photos.

If anyone has a fix for these bugs it would be much appreciated.

Thank you.
[Wileyfox Swift] almodovaris:
Perhaps you should give storage permission to the camera app.
[Wileyfox Swift] oliverjames:
The camera app has storage permission. The app settings give the option "phone" and SD card". I'd like the photos stored in /SD card/DCIM/Camera/.

When I take a photo I can no longer review the photos (in the directory chosen by the camera app).
[Wileyfox Swift] datapanik:
Today I just update from lineage-16.0-20190812-nightly-crackling-signed.zip to lineage-16.0-20190821-nightly-crackling-signed.zip

I don't have the problems you describe before or after the update.

A radio broadcast or podcast runs as long as I want it to.

With camera, pictures save to /DCIM/Camera

I'll check WIFI while I get home
[Wileyfox Swift] oliverjames:
Thanks. I solved the streaming cut-off by doing a factory reset then allowing the big G to restore my apps and data.

I still have the same issue with the location of the camera jpg files though.
[Wileyfox Swift] :
"Playing Now" feature

Please add "Now Playing" feature in sound settings. Please, please ?

Like a pixel experience rom. Thanks man i love lineage os ?
[Wileyfox Swift] testdriver2:
I tried to do the encrytion. Phone booted and showed a black screen after LineageOS-Logo. Every now and then there was back button flashing at left bottom . After some minutes the phone went to recovery. I booted to OS and encrytion was not there.
[Wileyfox Swift] oliverjames:
Camera - picture save folder

Still having the same issue with my Swift running the latest LOS 16: photos are saved in SD card/Android/data/org.lineageos.snap/files and not in SD card/DCIM/Camera.

Is it possible to fix this please?
[Wileyfox Swift] :
Add The "Now Playing" Feature

Please add "now playing"
[Wileyfox Swift] zomgzerg:
It seems like the device is no longer officially maintained :(

anyway, thanks for the work so far.
[Wileyfox Swift] oliverjames:
I'm still getting the OTA updates on my Swift, that suggest that it is still actively supported.
[Wileyfox Swift] petexd:
There's a OTA with security update 5 march almost ready for release. Could be today or possibly next day or two.
[Wileyfox Swift] robin0800:
Unofficial Rom lineage 16.0

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
[Wileyfox Swift] Floyd-74:
Thank you robin0800, great job! ?

Kind regards.
[Wileyfox Swift] 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...
[Wileyfox Swift] petexd:
Unofficial Lineageos Rom

Thanks robin0800. I've just installed your rom. Great job.
[Wileyfox Swift] didyou:
Will this device be no longer officially supported?
[Wileyfox Swift] 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.
[Wileyfox Swift] 115ek:
Hi. I'm continuing the official support and just re-added crackling to the build targets. :)
[Wileyfox Swift] 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!

:)))
[Wileyfox Swift] Floyd-74:
[MENTION=8036586]115ek[/MENTION]

Great news, thanks for taking on this hard work!
[Wileyfox Swift] Petrolofen:
[MENTION=8036586]115ek[/MENTION]

Many thanks! I am glad that you are doing this work! I am so happy with this cell phone.

Best regards!
[Wileyfox Swift] didyou:
I am very happy to continue the project. I hope it will continue for a long time, thank you very much.
[Wileyfox Swift] 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.
[Wileyfox Swift] petexd:
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.
[Wileyfox Swift] :
Lineage OS 17 (Android 10)

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

please support for official. Thanks :)
[Wileyfox Swift] 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?
[Wileyfox Swift] libove:
I may also be seeing this on dumpling (OnePlus 5T)

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
[Wileyfox Swift] 115ek:
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.
[Wileyfox Swift] quho:
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.
[Wileyfox Swift] quho:
Ok, it's the issue #1899 on gitlab.

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.
[Wileyfox Swift] libove:
Ah, ok then, it's definitely a different issue. Thanks for pointing that out.

Oh, well; and good luck!
[Wileyfox Swift] killerbees19:
I've formatted an Android 6 device and flashed this ROM. Is encryption stable with this ROM? Anything else I should know before enabling encryption?
[Wileyfox Swift] 115ek:
Yes, it works. Else the build won't be official. See the requirements here.

Setting a PIN/password/pattern is advisable. Else your device gets encrypted with "default_password". But you can also do this afterwards.
[Wileyfox Swift] killerbees19:
Thanks, [MENTION=8036586]115ek[/MENTION]! Device successfully encrypted :D

btw: I've a strange issue. Not sure if it's related to this specific ROM…

I've connected a Bluetooth device (Marshall Minor II) and it works fine, "only" BT 4.x with SBC, but everything stable. Except when used for phone calls! It's switching to mono (left side) and the volume of built-in microphone is way too low. Nobody can hear me, I've to shout directly into the microphone as a workaround. It doesn't matter if called via default telephone app (2G/3G) or Linphone (WiFi/SIP). I'm unable to reproduce this behavior with other Android devices and this Bluetooth headphones.

There's always one line in the kernel log when starting a phone call:

qdsp_cvp_callback: cmd = 0x112c2 returned error = 0x9

# 0x000112C2 = VSS_IVOLUME_CMD_SET_STEP

When using Linphone there's an error too, but it's different:

q6asm_callback: cmd = 0x10da1 returned error = 0x2
q6asm_send_asm_cal: DSP returned error[-2] audio audstrm cal send

# 0x00010DA1 = ASM_STREAM_CMD_SET_PP_PARAMS_V2

Not sure if they're related to this issue.

Any ideas what's going wrong here? Any hints what I should check?

Edit: See next post.
[Wileyfox Swift] killerbees19:
I've cleared the BT app cache and data, now it works in stereo…

Pure luck? We'll see… :rolleyes:
[Wileyfox Swift] robin0800:
Oficial 17.1 is out

Oficial 17.1 is out for this phone

https://download.lineageos.org/crackling
[Wileyfox Swift] wkn000:
Dirty flashed it over my LOS 16.0 (after preactive uninstall of addonsu) with TWRP-3.3.1-0. Installed Magisk for root. Works all fine by now.
[Wileyfox Swift] edwaine:
[MENTION=8036586]115ek[/MENTION] where's your Lineage 17.1 crackling thread?
[Wileyfox Swift] 115ek:
I updated it to link to the new downloads. Then it disappeared. xda is a bit broken sometimes :rolleyes:

I already contacted a moderator - let's see if they can bring it back.

However, 17 is official now and gets shipped.
[Wileyfox Swift] maxic_g:
Already installed. It's ok with BitGapps R6. Thank you.

P.S. With BitGapps update to next build is broken. OpenGapps - ok.
[Wileyfox Swift] killerbees19:
But now TWRP (3.3.1-0) is unable to mount /data :confused:

It can't find the crypto-signature. Any ideas how to fix that? :eek:

Edit: TWRP 3.1.1/3.2.3 displays a password prompt, but says it's invalid. TWRP 3.3.x doesn't show a password prompt at all.
[Wileyfox Swift] 115ek:
TWRP isn't able to decrypt /data partition. The problem needs to be solved in TWRP.

Besides that, beginning with Lineage 17, all devices ship the lineage recovery which should be the preferred solution.

Why do you need a decrypted /data partition? OTA updates work fine without.
[Wileyfox Swift] killerbees19:
Primary for backup purposes, but emergency access via ADB in TWRP would be nice too, if something goes really wrong.

Edit: Nevermind, I've disabled encryption again. (TAR-backup of mounted /data to SD-card; format /data in TWRP, reboot; restore unencrypted /data-backup in TWRP)

Maybe I'll re-enable it again in the future, but for the moment the TWRP "bug" is a real problem for me.
[Wileyfox Swift] FtCat:
Where is the download for the lineage recovery? I notice for other devices it is on the download page together with the updates but not for crackling. Have updated with TWRP and all went smoothlly am happy with it so far. Installation instructions required for the recovery as well.
[Wileyfox Swift] 115ek:
Lineage recovery shows up correctly on the download page since this morning. Instructions in the wiki also have been updated.
[Wileyfox Swift] Cerealekillers:
Is it better to use Lineage recovery instead of TWRP ?
[Wileyfox Swift] 115ek:
Lineage recovery is intended to establish a common base. If users use different TWRP's it is hard to deal with occuring problems. Furthermore, the lineage team hasn't got influence on the TWRP development (Exception: the lineage device maintainer and twrp device maintainer are the same person...).

The lineage recovery only features basic functionality like installing LineageOS images, applying OTA updates, factory-resetting the device or installing gapps. It is not as complex as TWRP!

In general I'd say: If you're a standard user you should go with lineage recovery. If you're more experienced or if you need special features then TWRP is the way to go. However, then you should be able to deal with issues on your own, too.
[Wileyfox Swift] Cerealekillers:
Okay, thank you, I'll stay with TWRP then.
[Wileyfox Swift] FtCat:
Having tried both I prefer TWRP.