Leaderboard

I will mention that Manjaro Linux on my Thinkpad X230 has no problems with either fastboot or ADB with what is installed by default with the OS. I use the yollow-tongued USB port(no SS designation), not the blue tongued one (designated SS). 😉

This is what I did (starting with a fully functional and stable LOS 18.1 + GApps + Magisk + XPosed setup): Backed up everything (Titanium Backup). Replaced display. Flashed stock according to @Waxberry's [Guide] Restore to stock firmware using Fastboot method. Used the 20200825 firmware (it was necessary to re-enable the four commented-out lines in fastboot_all.bat). Display margins returned to normal on first boot. No installation of newer OTA updates necessary. Reinstalled LOS 18.1, GApps, Magisk, XPosed like in https://wiki.lineageos.org/devices/pro1/install and

Hello! I've decided to root my FxTec Pro 1, installed Universal ADB driver (can use adb without issues), and booted into bootloader (using power + volume down). Dev mode and USB debugging is enabled. For some reason though, "fastboot devices" doesn't show my device (while "adb devices" does), and other fastboot commands don't work either and say "waiting for any device". Is there a step I may have missed? I already prepared a patched boot image that I want to flash the bootloader with but can't even run fastboot. Any help appreciated! /Theo

Yeah from Android 10 it got better. To me the main advantages of gesture navigation are: More screen real estate cause no navigation bar No need to reach for the bottom of the screen to go back There are apps that let you set it up though on Android 9 which is what I did on stock with my Pro1. Used an app called gesture control. We are somewhat off topic though.

The link above contains all gesture navigation features in Pie (link). Actually, the more I experiment with it, the more I like the new mode, might just keep it ... 😄

The traditional nav-bar then gets replaced by a single "pill" icon and occasionally appearing (probably context-sensitive) thin arrows to help transitioning to the new interface. I can well imagine that in Android 10, more features were introduced, but basic stuff like e.g. fast task switching by swiping the bottom of the screen works.

If I've observed the task switcher correctly, when "auto-rotate" is enabled, the cards' outer shape always follows the orientation in which the phone is currently held, and the cards' displayed content always follows the orientation the respective task was opened in. For me, this works the same for closed keyboard and open keyboard – with the exception that open keyboard forces landscape even when the device is held in portrait orientation.

On LineageOS 16.0 (build date: 20210815): Can't reproduce #3873 Dragging left-right always switches tasks, flinging to the top closes them. Both in landscape and portrait, irrespective whether keyboard is open or closed -- though open keyboard forces landscape for me, don't know if this can be disabled (would anyone want that?). Can't reproduce #3874 with gesture navigation enabled, opening the gitlab.com search box in the described way does not open an empty nav bar. Firefox here, not Chrome (as in the report). But as you initially wrote it happens in all browsers ... As

I'm not quite sure I understand the first one. When I open the task switcher in landscape, cards for apps able to do landscape are in landscape and apps that don't do landscape are in sideways portrait-- because they can't do landscape. In eiher case the cards slide to the right or left and the icons are at the top. <shrug> The second one, I dunno, since I use a nav bar and not gestures. 😉

https://wiki.lineageos.org/how-to/bugreport

https://wiki.lineageos.org/gapps.html (Content compared here)

Ho wait that's only an issue when the keyboard is open. It's like the task switcher still thinks you are in portrait. Not an Android bug then but really a bug of LOS for Pro¹.

Is it just me or the fact that they swap the task switcher direction between landscape and portrait is very annoying. When in portrait to scroll through your tasks you drag vertically, do that in landscape and you close your task. Who the hell comes up with ideas like that at Google's Android. Moreover the way they capture the preview screenshots for the task switcher is rather useless in landscape. I'm in a ranting mood 😁 LOS 18.1 is awesome so far but it looks like it's going to take weeks of bug fixing to get it as useable as stock... That's kind of why I postponed flashing i

Another major issue is that when the keyboard is open and you focus a text field in a browser for instance you get a useless band of empty screen at the bottom, that's possibly not an issue when not using navigation gesture. It looks like it tries to show an empty navigation bar. That one is pretty much a show stopper for me as it prevents proper use of keyboard in browsers. Chrome, Firefox Klar/Focus and Fulguris are all affected. How do we report bug for LOS? Do they track those on GitHub somewhere?

This thread may help. I haven't done any of this because I don't care about this stuff, but from comments I've seen there is stuff in this thread that works. I think @Rob. S. has messed with all this most recently and will probably be more helpful than me.

I use MindTheGapps from last April. http://downloads.codefi.re/jdcteam/javelinanddart/gapps Others hve used OpenGapps, nano or pico. I believe, but don't remember source, troubles come with the bigger packages.

(Some comment on touch issues, moved to this thread)

More precisely: "Based on the non-kernel-parts of Mobian + Android 9 and Hybris". It is true that some Pro1-specific work (obviously no Pro1X yet) is going on there, thanks for the heads-up. But for the reasons discussed above it still relies on Android 9 and is thus probably not what @shane was expecting.

Usually this ghosting problem appears relatively often and there is an unsensitive part of the screen. After touching / moving a finger near the bottom part of the display, maybe at a corner, it becomes temporarily better - it is not a fix as it is temporary but an experience. Without attaching the display to the assembly, what happens if you gently move different parts of the ribbon cables (mostly near the bottom part)? Also, is there any difference when you use a wire to connect the screen's conductive part to the assembly's conductive part (shielding / gnd) which the display is

I also have doubts they would be planning on flashing the phones in the UK. Maybe they did that with the 10 Xmas phones, but I don't believe they have the people or set-up to do anything on a mass scale. I think everything will be shipped from HK, as the Pro1s were.

I don't think so, my original Pro1 came straight from China.

Droidian is making good progress. Not ready for daily use but getting closer. Based on Mobian for pinephone.

I always find it best to install the Google USB driver. Windows doesn't always install a compatible one. https://developer.android.com/studio/run/win-usb