The tutorial which you mentioned above is written for Minimal ADB and Fastboot and not for plattform tools. Since this tool is only available for Windows, you have to use the original Android SDK Platform-Tools. The procedure should be more or less the same, although the place where you can put the plattform-tools folder might differ. And the command line tool on macOS is - of course - also a different one
I’m still planning to expand the tutorial for plattform-tools and thus for other operating systems like Linux and macOS…
regarding my problems with video conference, looks like the mediaserver is crashing. Added more info in the lineage os tracker issue I opened.
Paging @dk1978 , but be assured it’s only for letting you know, I’m not expecting a reaction as long as you’re still busy with your personal needs!
Yep if you look at the line below the line your quoting you will see I did both… as I was cross referencing two different guides to see if either worked in this particular instance. Neither did…thank you for following up though
Actually, no. First, you flashed recovery, then you flashed boot…
But, according to the LOS wiki, you’re supposed to flash boot.
So, this should work, if your image is correct.
I’m not sure whether you’re supposed to flash to boot_a or boot_b, though, as I always use a different approach: I temporarily boot twrp: fastboot boot twrp.img (from twrp.me)
Since using the update from Jan 27 (microG), I see an increased battery drain by the cellular network standby process (> 33%), despite being connected to WiFi. I disabled the parallel connection option in the developer menu, but no avail. Does anybody run into the same issue or know how to solve that?
Hi community. First of all I want to thank all the Devs here for contributing all the good stuff what makes my FP3+ such a great device.
I hope I’m addressing my “issue” in the proper channel (I don’t really know if it’s a feature request or a bug):
I’m running my FP3+ with LineageOS 17.1 and OpenGapps Nano. When connection the FP3+ via Bluetooth with my car the car does not show the signal quality of the connected device. It also tells me, that there is no service available. Nevertheless I can make an receive calls through the car system what is really strange. I tried to switch to the different Bluetooth AVRCP versions to fix this behavior (1.4 - 1.6) with no success.
BUT: When adding a second SIM into Slot 2 everything looks as expected. My car shows the signal quality and the provider information of SIM in Slot 1 when connected via Bluetooth. I tried this in two other vehicles from colleagues and it is exactly the same behavior.
My conclusion is that the LineageOS 17.1 Bluetooth stack is sending the connection status of SIM 2 if only one SIM is inserted into the phone (SIM 1 slot) which gives a misleading information to car systems. Luckily telephony works. It would be great if this could be fixed.
when I set the notification color for Signal to green and I am charging my phone (between 15 and 90% -> yellow color), then the notification color for Signal is red (green + yellow?). Has anybody the same issue?
Yes, color is “a bit off while charging”, but also non charging it looks like it’s not completely honoring the settings, which might also be caused by hardware limitation, as i always observe some " cycling " while composing a color
I’m running LOS 17.1 (version 1st Feb 2020) on my FP3+. Last week and this week I’m having a problem with the Updater. I download the new LOS update in the Updater, but when I click “Install”, the Updater crashes and I get a notification that the app has been repeatedly terminated (“Updater wird wiederholt beendet”). I have no clue what caused this, because I didn’t change any settings or similar stuff.