Well I don’t think it’s a good idea to maintain two posts/wikis that both list the same stuff, so I edited the post to make it more clear where to look for an updated list of issues.
Weather provider or settings problem:
When I installed the older build from here I had it quickly configured so that the lock screen displayed the current weather of my user-defined location. I thought that was quite neat.
Now that I’m on the newer OTA build from here, I somehow fail to recreate that.
I once again installed the OpenWeatherMap weather provider for LineageOS, I once again added that to the clock’s Widget settings, I once again added my API key for OpenWeatherMap, waited for it to be verified, and now I’m stuck with a problem:
I can’t enter a user-defined location anymore in the Widget settings.
Everything I enter there almost immediately throws a generic “location could not be determined” (if that is the English localization) message, the same that you get in map Apps still having to fixate your location.
With the older build, when I entered a city, I would be given a choice of locations if there were more than one places matching my input.
Has anybody got anything like this working with the OTA build?
Edit: Never mind, I uninstalled the weather provider, installed it again, and now it works
Just a quick message: yesterday I did a travel by car with OsmAnd~ navigation and it was a pleasure! The experience was awful in FP Open, with reboots, overheats and incorrect compass. Thank you all for the awesome work,
three hours ago I started encrypting my phone. It said it would take more or less 1 hour. Now it seems to start up again and again. Is this part of the normal process and should I wait some time more or should I break up the process of encrypting?
No, this is not normal. Which LineageOS build did you install?
I first tried encryption with the build linked to at the beginning of the Porting thread and ran into a bootloop.
Next time I installed the newer build from the OTA thread and encryption went fine.
@AnotherElk ok, tnx! I think I have the same build as you started with. What should I do now? Can I just pull the plug and shut down the phone and install the newer build later on?
Here’s what I did then:
Force-shutdown the phone (very long press Power).
Boot into TWRP, wipe everything, format data.
Install the other LineageOS build.
Immediately encrypt the phone, it will not take long since data is almost empty at this point .
Edit: Check whether encryption works by rebooting into TWRP, it should prompt for the encryption password and decrypt data with it.
Edit: Boot into LineageOS, restore my data from backup.
@AnotherElk. Tnx a lot again! I got the threadfile. Now adroidfilehost advises me to check the md5. Where should I find that number? I can’t find it… Also, the file is actually 15MB bigger then it should be according to androidfilehost. Is this something to worry about?
Not because of MD5, but because I think you should follow the instructions of the “When coming from any other OS” section of this post :
The one thing I find hosted on androidfilehost is the older build that gave me (and probably you) trouble with encryption, so that doesn’t sound helpful.
Why should I actually follow the “When coming form any other OS” section? I thought in my case I have to follow the version “when coming from @chrmhoffman’s build”.
If you completely wiped your phone and formatted data (like you should do just to be safe after an incomplete or otherwise broken encryption attempt), you’re not coming from any build .
Hey folks, I tried to do the “LineageOS 14.1 with OTA updates for FP2” and then followed the instructions from “When coming from any other OS”. I got stuck at the fastboot method. When I type
“adb reboot bootloader” in terminal and then press enter I get the following text: “-bash: adb: command not found”. What to do?
Did you follow the the fastboot method link in the post? And did you on the linked page then follow the You will need the platform-tools from the Android SDK on your computer. link in the “Fastboot Install Method (No Root Required)” section?
Try fastboot instead of adb.
Or hold down volume down when turning on. The FP screen with the logo remains then.
adb (and probably fastboot) are not installed or are not on your path. Check whether your package manager has them for the easiest installation method (as this should add them to path). Look for android-tools, though some distros split them into e.g. android-tools-adb and android-tools-fastboot.
Hey! I also couldn’t get fastboot going, because I’d never used it before. Coming from Fairphone Open 5, I installed the TWRP app, and used it to flash TWRP_3.1.1-0-ota-fix.img to the recovery partition. Then I booted into TWRP to flash the modem zip, lineage, and opengapps, following the instructions from the forum. And it had been great since!
Has anyone else had success in doing this instead of fastboot? I think this helps open lineage to a wider audience
@AnotherElk Hi :-). Yes, I think I did. I did download the platform tools on my computer, so I’ve got adb and fastboot. I did enable USB debugging on my phone. When I doubleclick on adb I get two terminal screens. One of those (named: --adb --80x24) had a lot of text and closes of with the wordt “Proces finished”. In the second screen (named: --bash --80x24) I can write command lines. That’s where I got stuck, like I wrote in my previous post.
I’m not sure if the connection with my phone is correct. Maybe that’s the problem?
@mase I tried fastboot, but I end up with the same problem as with adb.
Or should I just try the method from @anthony first?
With latest build 0724 the auto brightness is removed, is someone else experiencing this?
@dupdup: my mistake - somehow I had in my mind that you we’re doing this on a Linux system - I’m not sure whether there is such a thing in a Mac. If anthony’s method doesn’t work, here’s a couple of ways that should work around bash (=terminal) not finding the adb you installed:
- Open a terminal in the location where you installed/unpacked the android-tools (i.e. where you double clicked), or navigate there using
cd, as in
cd /home/user/path/to/tools/. You should then be able to run adb and fastboot from bash without messing with the path if you put
./immediately in front of it, like:
./adb reboot bootloader.
- In a similar vein as above, you can tell bash where to look each time you run a command. The advantage is that this can be done from any location, but you have to type the full path each time, e.g.
/home/user/path/to/tools/adb reboot bootloader
- Bash has a list of places (=folders) to look for commands, you can add custom entries that only affect the current terminal session like so:
PATH=$PATH:/home/user/path/to/tools/. After this just running
adb reboot bootloadershould work within that session.
- As an addendum to the above, if you want this to set up to run at every terminal you open, then there’s usually a hidden file in your home folder where bash keeps its settings - I’m not sure which one mac uses: popular options that I know of are
.bash_profile. Verify that whatever you put in actually works first, as changing it in the wrong way can potentially have messy side effects.