[ROM][10.0][OFFICIAL] LineageOS 17.1 for Wileyfox Swift

Apr 22, 2015
27
0
31
Dar es Salaam
kukutrust.org
Bug in 17.1/crackling? (2)

You can try to power off the phone, remove and insert the card again and reboot. I know that's just a work-around, but better than nothing.
.
Still resulting in: "San Disk SD card Corrupted" + "San Disk SD card Not inserted"

Besides that: Is there any special reason you need to use your sd as internal storage? Else just using it as "normal" sd card would be way easier (and faster).
.
I intend to give it to an African lady – are you aware how much they gossip on social media and how much data needs to be stored?

EDIT:
I'm going to remove the option of adoptable storage soon as it just causes problems.
This option is running fine on Lineage 16 – so why not on 17?
 

RavZ75

Member
Feb 27, 2019
38
11
0
Playing a game like Hill Climb Racing for a while makes phone freeze up until it reboots, phone gets warm so I am sure it's a thermal issue.
I don't play many games on it anyways but.. I just wonder if I am alone with this issue? I only seem to be able to play simpler games like Solitaire and such while games like Hill Climb Racing and Pokemon Go overheats and restarts phone after about 15 min or so.
This is while being on LOS17.1 on Crackling, I don't remeber this to be an issue before being on stock but that is like ages ago for me.
 
Last edited:

115ek

Senior Member
Jan 30, 2017
496
543
103
This option is running fine on Lineage 16 – so why not on 17?
Because it is obviously broken. I see two options: Either use lineage 16 or use the SD card as normal SD card.
Or third: Find out what's broken in detail, repair it and push the needed changed to the lineage gerrit. Help is welcome everytime.

Playing a game like Hill Climb Racing for a while makes phone freeze up until it reboots, phone gets warm so I am sure it's a thermal issue.
I don't play many games on it anyways but.. I just wonder if I am alone with this issue? I only seem to be able to play simpler games like Solitaire and such while games like Hill Climb Racing and Pokemon Go overheats and restarts phone after about 15 min or so.
This is while being on LOS17.1 on Crackling, I don't remeber this to be an issue before being on stock but that is like ages ago for me.
Well, crackling is a low-end device from 2015. You can't expect to run current games with fancy graphics on it. Maybe collect a log of the freezing. But I guess there isn't much we can do here.

$ adb logcat -d > logcat.txt
/system/bin/sh: logcat: inaccessible or not found
Did you follow the instructions? Is
Code:
adb devices
showing something for you? Are you able to access the device via adb?
 
Apr 22, 2015
27
0
31
Dar es Salaam
kukutrust.org
Another attempt

Besides that: Is there any special reason you need to use your sd as internal storage? Else just using it as "normal" sd card would be way easier (and faster).

EDIT:
I'm going to remove the option of adoptable storage soon as it just causes problems.
Maybe I mis-defined it: we are talking about extending the internal storage -- a meagre 16 GB in case of the Swift -- by SD card.

Just sideloaded the PixelExperience_go_crackling-9.0-20190123-0935-OFFICIAL.zip -- and the SD card works flawless.

Quod erat demonstrandum: there must be a bug in the L17 code.
 

115ek

Senior Member
Jan 30, 2017
496
543
103
Maybe I mis-defined it: we are talking about extending the internal storage -- a meagre 16 GB in case of the Swift -- by SD card.

Just sideloaded the PixelExperience_go_crackling-9.0-20190123-0935-OFFICIAL.zip -- and the SD card works flawless.

Quod erat demonstrandum: there must be a bug in the L17 code.
Well, as I already said: Use pixelexperience or whatever fits your needs. Adoptable storage is slow anyway and I guess you won't have much fun (in terms of performance) with it.
Most likely this isn't even a Lineage bug rather than a aosp one. I think google doesn't really care about the adoptable storage as sdcards are near to deprecation nowadays.

As I don't have the ressources to find and fix this bug I'm going to remove this feature.

EDIT: If a fix gets available it's no problem to reenable it. But if it's not working it shouldn't be selectable for the user.
 
Apr 22, 2015
27
0
31
Dar es Salaam
kukutrust.org
Really: no offence meant!

Because it is obviously broken. I see two options: Either use lineage 16 or use the SD card as normal SD card.
Or third: Find out what's broken in detail, repair it and push the needed changed to the lineage gerrit. Help is welcome everytime.
Where can I find the latest L16 zip? Best a 'lineage.microg.org' make.

Well, crackling is a low-end device from 2015. You can't expect to run current games with fancy graphics on it. Maybe collect a log of the freezing. But I guess there isn't much we can do here.
Its NOT freezing! Just not recognising the SD card after reboot.

:angel: in fact, I used it for downloading bittorrents

Mate, I love the Open Software idea, thus I also submit bugs e.g. to Libre Office. Otherwise I do grassroots projects in Africa, I don't code.

Did you follow the instructions? Is
Code:
adb devices
showing something for you? Are you able to access the device via adb?
Sure, I just sideloaded another system.

Cheers
 

115ek

Senior Member
Jan 30, 2017
496
543
103
Where can I find the latest L16 zip? Best a 'lineage.microg.org' make.
I don't know. Maybe some archived it.
If nothing helps: Just build it on your own. https://wiki.lineageos.org/devices/crackling/build

Its NOT freezing! Just not recognising the SD card after reboot.
I know. It wasn't related to your comment. I talked about the freezes when running games.

Sure, I just sideloaded another system.
Strange. Did you modify the system even further? For me it works on the official lineage build (clean installation).
 
Apr 22, 2015
27
0
31
Dar es Salaam
kukutrust.org
Probable cause of failure?

I decided to start from the scratch, wiped and re-formatted everything.
After flashing
Code:
lineage-17.1-20200919-recovery-crackling.img
I face the following error:
Code:
Failed to bind mount /mnt/staging/emulated/media/0 to storage/emulated: No such file or directory
Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
Please advice, thanks!
 

r25txe

Senior Member
Mar 3, 2011
481
165
0
When I format the SD card as system. When I turn the phone off and on, it says SD card is not inserted. the phone is rebooting.

After turning it off and on several times, it sees the SD card and works normally.

I tried it with 2 different SD cards. Sandisk with 100mb / s read and write value.
Ota 08.august.2020 update.

This is a longterm bug in Lineage and even on Resurrection ROMs; I had this on an 8.1 build before and the workaround is to reboot until it picks up the card. It doesn't matter the size or speed of card you use.

@115ek, I'm still running a build from around July as I just haven't had a chance to update, I see that you've mentioned removing adoptable stoprage from the ROM, has that occured in any of the released builds yet?
 

115ek

Senior Member
Jan 30, 2017
496
543
103
I decided to start from the scratch, wiped and re-formatted everything.
After flashing
Code:
lineage-17.1-20200919-recovery-crackling.img
I face the following error:
Code:
Failed to bind mount /mnt/staging/emulated/media/0 to storage/emulated: No such file or directory
Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
Please advice, thanks!
Where did the error message occur? Did you make a factory reset? Wiping isn't enough...

This is a longterm bug in Lineage and even on Resurrection ROMs; I had this on an 8.1 build before and the workaround is to reboot until it picks up the card. It doesn't matter the size or speed of card you use.
Well, even more a reason to drop this feature.
@115ek, I'm still running a build from around July as I just haven't had a chance to update, I see that you've mentioned removing adoptable stoprage from the ROM, has that occured in any of the released builds yet?
I merged on 25th and the last build is from 26th - so it should be included there.
 

r25txe

Senior Member
Mar 3, 2011
481
165
0
Where did the error message occur? Did you make a factory reset? Wiping isn't enough...


Well, even more a reason to drop this feature.

I merged on 25th and the last build is from 26th - so it should be included there.

Thanks


Do I need to switch from using adoptable storage to portable storage before I update to the latest or is it just that the latest ROM won't allow adoptable storage as an option? (I hope that makes sense)
 
Apr 22, 2015
27
0
31
Dar es Salaam
kukutrust.org
SD card works fine! :)

This is a longterm bug in Lineage and even on Resurrection ROMs; I had this on an 8.1 build before and the workaround is to reboot until it picks up the card. It doesn't matter the size or speed of card you use.
:) This workaround "fixed" it! I rebooted a few times and now I am equipped with 144 GB device :D

---------- Post added at 04:15 PM ---------- Previous post was at 03:46 PM ----------

Well, even more a reason to drop this feature.
I reckon, that you live in a 1st-world country with cheap internet or even flatrate.

In tropical Africa however, people even skip a meal to pay for their telco-bundle and stay connected!
E.g.: https://www.tigo.co.tz/combo-packs
If they can't extend their storage, their apps are going to store more data in the cloud. Ultimately they are condemned to spend even more…

I merged on 25th and the last build is from 26th - so it should be included there.
"Included" in the sense of excluded?
 

115ek

Senior Member
Jan 30, 2017
496
543
103
Do I need to switch from using adoptable storage to portable storage before I update to the latest or is it just that the latest ROM won't allow adoptable storage as an option? (I hope that makes sense)
You don't need to switch. You just won't be able to set up a new sdcard as adoptable storage starting with the latest build.
Already existing adoptable storage continues working (of course with its bugs...).

:) This workaround "fixed" it! I rebooted a few times and now I am equipped with 144 GB device :D
I already told you that several posts before. Anyway, nice that it works for you now.

I reckon, that you live in a 1st-world country with cheap internet or even flatrate.

In tropical Africa however, people even skip a meal to pay for their telco-bundle and stay connected!
E.g.: https://www.tigo.co.tz/combo-packs
If they can't extend their storage, their apps are going to store more data in the cloud. Ultimately they are condemned to spend even more…
Well, that is really far-fetched. What has a flatrate to do with adoptable storage? :confused:
You are still able to store your stuff on the external sdcard. In addition, the adoptable storage continues working if you already enabled it.
In the end adoptable storage is buggy and not working reliable, that's why it was dropped now.

"Included" in the sense of excluded?
Exactly.
 

r25txe

Senior Member
Mar 3, 2011
481
165
0
You don't need to switch. You just won't be able to set up a new sdcard as adoptable storage starting with the latest build.
Already existing adoptable storage continues working (of course with its bugs...).

That's what I suspected, but thanks for clarifying.

---------- Post added at 06:37 ---------- Previous post was at 06:25 ----------

:) This workaround "fixed" it! I rebooted a few times and now I am equipped with 144 GB device :D


It's fairly straightforward to figure out whether it will work.


After rebooting, go to 'settings ... storage' and if it says 'checking' on the card, give it time and it *might* pick it up.


If it changes after the above to 'corrupted' and there's a weird second card listed as 'not inserted', *you need to reboot*, and do it until it picks up the card again properly and there won't be a second card listed and the storage will reflect your combined card and phone storage.


The max number of times I have had to do this is three times. Once.


As a result of these 'corrupted' starts I HIGHLY recommend good backups. I've not ever lost something, but with this bug you can never know.


Finally, these dodgy starts seem to cause 'tombstone' files that you need to clear using the repair command in TWRP. (Interestingly, TWRP [3.4] never fails to load the adoptable storage partition properly). You only need to tick the data partition and it will also check the adopted storage on the card, too.
 
Apr 22, 2015
27
0
31
Dar es Salaam
kukutrust.org
Thanks for the good advice!

After rebooting, go to 'settings ... storage' and if it says 'checking' on the card, give it time and it *might* pick it up.

If it changes after the above to 'corrupted' and there's a weird second card listed as 'not inserted', *you need to reboot*, and do it until it picks up the card again properly and there won't be a second card listed and the storage will reflect your combined card and phone storage.

The max number of times I have had to do this is three times. Once.
Right! My "mistake" was, to reformat each time right away. Thanks again.

Finally, these dodgy starts seem to cause 'tombstone' files that you need to clear using the repair command in TWRP. (Interestingly, TWRP [3.4] never fails to load the adoptable storage partition properly). You only need to tick the data partition and it will also check the adopted storage on the card, too.
Using Lineage recovery that far, maybe I should give TWRP a try indeed.
 
Apr 22, 2015
27
0
31
Dar es Salaam
kukutrust.org
What is the use of Lineage OS?

Well, that is really far-fetched. What has a flatrate to do with adoptable storage? :confused:
Without doubt smartphones only work as 'always on, always connected' terminals of Big Brother's server. The former notion of PC as (personal computer) was turned upside down.

Thus the Open Source core of Android plus Lineage OS constitute the final frontier against total surveillance, since at least I can decide what to keep private and what not. This freedom must include the decision about which data I like to swap to the cloud. Extending storage facilitates free choice.

Your arbitrary act of removal will deprive Swift-users of this very free choice and thus runs against the spirit of Lineage OS.
 

115ek

Senior Member
Jan 30, 2017
496
543
103
My last comment on this discussion:

Thus the Open Source core of Android plus Lineage OS constitute the final frontier against total surveillance, since at least I can decide what to keep private and what not. This freedom must include the decision about which data I like to swap to the cloud. Extending storage facilitates free choice.
Extending storage has no influence on keeping your privacy or not. At least not directly.
However, if I take you at your word you need the extended storage to keep your privacy.

But then, some posts earlier, you told:
I intend to give it to an African lady – are you aware how much they gossip on social media and how much data needs to be stored?
That contradicts your last argument. Either social media or privacy. Your arguments are a bit confusing.
Furthermore, data can be also stored on the sdcard.

Your arbitrary act of removal will deprive Swift-users of this very free choice and thus runs against the spirit of Lineage OS.
There are many wrong statements in this sentence. I clarify once again:
  1. The removal is arbitrary by no means. The adoptable storage feature is not working correctly and thus was removed. The users should be preserved of running into trouble with it.
  2. The "very free" choice you mentioned was between using the sd card as external storage (working correctly) and adoptable storage (not working correctly).
  3. The removal of adoptable storage also took place for several other official lineage devices for exactly the same reason I just explained. LineageOS does not ship broken features. If the broken feature is essential, the device looses official support.
  4. I'd like to remember we all do this as a hobby in our free time.
  5. You are completely free what to install on your device. Noone forces you to install LineageOS.
  6. All sources are available and build instructions are available. You can build images on your own and re-enable the broken feature again.
  7. Contributions are welcome every time. If you can contribute something constructive feel free to do so. If you repair the adoptable storage I'd be happy to include it again.
 

UNLUCKY67

New member
Jan 21, 2015
3
0
0
Help stuck on bootloader screen

This is the first time I've tried to flash a phone...I've been meaning to try for ages (bought a swift cos it was Cyanogen - was gutted when it went to Android). It was running the last android update (7.1)
I've spent hours doing this, had problem after problem, done lots of web searches etc, and now at the point where I have no os on the phone and when I turn it on it goes to the fast boot screen....
This is what I've done (more or less -honestly I'm confused now!)
1. Backed up to internal SD card but I think the card has failed? It was working after the back up, unmounted it to use in my pc to back up the back up but couldn't get my PC to recognise it at all - even to say it isn't readable/needs formatting, when I put it back in the phone, before I lost the os in the phone, it was telling me it needed to be reformatted (which I didn't do) In another android device I can see there is some data still on there, but not what it is. Decided to leave it for now - if I really need to I guess I might be able to find a way to recover the data? I have another card that does work in phone and PC and have started using that .
Factory reset
Using ADB/Fastboot on windows 10 pc
2. Managed to unlock the OEM and get phone to be recognised as adb device and fast boot device
3. Fastboot lineage recovery img. Seemed to work but then I just got the android recovery. I now think this might be because it kept auto installing/reverting to android recovery. After much faffing I fastbooted twrp.img and had the same problem...got round it by taking out the battery and restarting using volume down & power . I had to change the squashfs file format to ext4. Used twrp to wipe the device. (I know I should/could have done a new backup using twrp - I stupidly didn't)
4. If I try and use twrp/ mount usb/ to allow me to fastboot the lineage recovery file I don't see the recovery mode. I just get the bootload screen. Message on windows is reading and writing both OK.
I can fastboot twrp recovery and from there try and install the lineage os. I need to turn the zip verification off but still just boots to bootloader screen. This is both from the files on the sd card and also using windows to sideload. I have downloaded the latest lineage 17 files (zip and Image) several times so file integrity should be ok - wondering if I should try an earlier version or?
Sorry huge post - this really has become a nightmare. I do have some recovery logs from latest attempt - skim read (and not really knowing what I am reading) I can see something about not being to decrypt the device?
Grateful for any advice - I love my Swift... no idea what I would replace it with...
Thanks