Upgrading from *official* 14.1 to 15.1 (feedback/issues)

Seems, that you were right. The card seems to be broken. Isnā€™t a LOS problem. Tried to format the Card with Windows, Linux, Mac and another android device. Tried different tools like GParted, Partition Wizard, diskpart, Sd Formatter without effort.
I found this information at the SanDisk site.

Write protection errors occur when a flash drive detects a potential fault within itself. The drive will go into write-protected mode to prevent data loss. There is no method to fix this. To verify the issue is related to the flash drive and not your computer we recommend that you try plugging the USB drive into another port on your computer. You should also try the drive on another computer if possible.

Iā€™ll buy a new one.

2 Likes

IMHO K9 has currently problems with Oreo notifications. If you set a notification sound it displays notification LEDs, thatā€™s what I observed.

1 Like

Another effect i ā€œsufferā€ since 2p181021: when on the move with energy saving location mode, the phone does not sleep anymore. So the battery drains quite a lot. Anyone else, or private specialty?

Hi,
I created a log - can I send it to you per PM? I donā€™t know how to post it online - too many chars.
Regards
Friederike

1 Like

Hey, iā€™m getting daily upgrades lately and the bugtracker shows no changes, what is going on there? is this a testing period?

As discussed on this topic, they moved from weekly updates to daily updates. :slight_smile:

3 Likes

oops thanks, i should have searched before asking :smiley:

1 Like

any news on the one. According to tot the fairphone bug tracker it seems to be solved but there isnā€™t any update on the LineageOS bug tracker.
thx
stefan

It was solved in the bootloader code for the Fairphone 2, so I think thereā€™s nothing to solve in LineageOS itself.

In the bugtracker @borjan notes:
"Solved with 18.09.2.
Please note that you will have to use the manual archive to flash the bootloader partition - the update file does not provide the fix."

I just did the following for my LineageOS 15.1 to check whether it actually works (the bug didnā€™t bother me much, so I didnā€™t check until now), which it does, so ā€¦

  • Boot the phone into Fastboot mode
  • Extract the manual archive fp2-gms-18.09.2-manual.zip from here to somewhere on your computer where you can find it
  • Open a cmd or shell
  • Go to the directory where you extracted the archive
  • Make sure fastboot works for you in this directory with fastboot devices
  • Windows cmd:
    fastboot flash aboot "images\emmc_appsboot.mbn"
    Unixoids shell:
    fastboot flash aboot "images/emmc_appsboot.mbn"
  • When done, fastboot reboot
5 Likes

I will check tonight and report back

when I click on here I end up at Fairphone OS downloads for Fairphone 2. So you want me download FP2 - Binary images of Fairphone OS 18.09.2 what has the file name fp2-gms-18.09.2-manual.zip.
I sit behind a very slow internet connection currently. Would you mind to upload the emmc_appsboot.mbn, if this not the only file in the archive, either here in the bug report?

that worked out well :slight_smile:, I updated the bug report, including a extended guide
by the way you can now get fastboot etc. as standalone tools: https://developer.android.com/studio/releases/platform-tools.

2 Likes

TWRP 3.2.3-0 canā€™t decrypt an encrypted LOS15.1.
i created an issue on github:

is anyone working on this?

a workaround exists, thanks to AnotherElk by upgrading from 14.1 first (Updating LineageOS 15.1 for microG via TWRP + feature test)
but this is not a good solution for the regular user (&not based on the current 8.1 encryption)

1 Like

who is the maintainer of TWRP FP2? As looks like that only an update from 3.2.3-0 to 3.2.3-1 is necessary.

According to Fairphone 2 itā€™s still @z3ntu ā€¦ but it seems he had to do something good for the remaining Fairphone 1s first :wink: ā€¦

Last time I checked, devices which already got TWRP 3.2.3-1 were the minority anyway, so patience seems to be asked of us ā€¦

2 Likes

So what I know:

The 3.2.3-1 version that is available for some devices is a rebuild of version 3.2.3 but with an updated device/kernel tree.

I asked what was changed in the devices that got the -1 build but I only got vague answers from the TWRP maintainers. Iā€™ve looked into the issue on the FP2 multiple hours trying different things that didnā€™t help at all unfortunately.
Basically I donā€™t know what part is broken so i canā€™t fix itā€¦

6 Likes

itā€™s a pain

thx for the effort letā€™s hope that it will be found, somehowā€¦

After a couple of months, here some experiences on various shortcomings with LOS 15.1
Roughly in order of annoyance

  1. The notorious ā€˜no shutdown bugā€™ - variously covered in other threads
    The workaround with the torch doesnā€™t work always (seems random)

  2. If phone is off, charging via USB & computer drains(!) the battery

  3. Image updates do not install properly. A manual reboot into TWRP is necessary.

  4. Occasionally the dual-sim settings & proximity sensor calibration are lost after reboot

  5. Rebooting while charging via USB seem to make problems (e.g. hangs on boot, ā€¦)

  6. Occasionally pugging in/off of headset activates the music player

  7. No possibility for groups in contacts

1 Like

Can you observe whether the workaround does not work when the phone is connected to charger/USB and/or Bluetooth is enabled?
Those circumstances had an impact on the workaround for other users.


These two problems are not normal.

If you happen to have fairphoneangels in your vicinity, they might be able to check whether your bottom module may be faulty by swapping it and seeing whether the battery drain persists.

Else ā€¦ a general troubleshooting step with modules is to disassemble them (hereā€™s a video), clean the contacts on the respective module and the core module with alcohol, and then re-assemble the module and try again.


Same workaround as for shutting down, else automatically rebooting into the recovery (without keeping Volume + pressed at reboot) will not work.


I canā€™t say anything about Dual-SIM, but I never lost proximity sensor calibration after a simple reboot.


General question: Did you upgrade an existing LineageOS 14.1 installation, or did you install LineageOS 15.1 from scratch (incl. wiping the phone)?

Thanks for taking the effort going through all the issues.

No, never during any charger/USB connect. Donā€™t use Bluetooth presently.
For my feeling it occurs purely random. Some times the workaround works works for ~10x in a row. Then I get even 2 reboots before successful shutdown.

Thanks for the detailed advice.

My understanding was that direct upgrade 14.1 ā†’ 15.1 is not possible. (Was discussed in some forum or in some installation guide, I guess). So, wipe & from scratch.

cheers