claude0001

In sharp contrast to when the original Pro1 was still in pre-production, whe have (to my knowledge at least) seen no enthusiastic demo videos of Pro1X's running an alternative OS so far. All there was, was a screenshot from the UbuntuTouch settings panel in the November update, along with the comment that porting of alternative OSes to the 662-Pro1 has "started". I thus expect LineageOS and UbuntuTouch development to be lagging behind at this point, which would explain why you were not offered the choice of the OS. I wouldn't be surprised if they eventually shipped all devices with A

The ribbon cable that is exposed by the Pro1's mechanism connects just the screen unit to the mainboard. The mainboard is inside the bottom half of the phone which also holds the keyboard. So the connection you are interested in is not visible from outside.

For LOS 16.0, the usual string shown there was "Builtin Keyboard". I'd say, either the keyboard is indeed physically disconnected, or the system has been re-configured to default to some other hw keyboard. Did you ever use an external USB or Bluetooth keyboard in the past? If yes, what happens if you re-connect that? However, as your problem appeared kind of gradually, I rather fear that the keyboard is indeed not properly connected to the system board anymore. Maybe the ribbon cable connecting it to the board has loosened with time. There is a quite complete official disassembling g

If you haven't updated your LineageOS 16 in two years, chances are you using one of @tdm's unofficial builds. Not sure if there are supported upgrade paths from there. I'm still on (a modded) LOS 16 myself, others might know better if upgrading to 18.1 can be done tranparently in your case. However, if you never updated, regressions in LOS cannot be the reason for your troubles anyway, so what would be the point of upgrading now?

Before wiping everything, I would first try to just uninstall MS Swiftkey, and see if that helps. I do not know that software from personal experience, but from what I read, it does have functions related to hardware keyboards. Maybe there is some conflict with native keyboard handling in Lineage. Also, there has been quite some development around the keyboard driver in LineageOS (18.1) during the last few months. While all these changes were of course meant to improve things, regressions for heavily customised set-ups are always possible, I guess. Which release and version of Lineag

Considering how people here and on IGG analyse (and maybe over-interpret?) these monthly reports, I think they spend quite some time writing those up. I can imagine they plan very carefully what to publish and how to present it in a way such as to cause least damage to the project. It is easy for us to ask for more honest reports and estimates, but unfortunately it is also a fact that many customers need the harsh reality to be "embellished" for them, or else they jump ship. Some people understand that by supporting Fxtec, they support an interesting enthusiast project: a concept of a sma

I like most the ones that tell me F(x)tec is a fake company and that my Pro1 does not exist. 🙃 Thinking that through, it follows that we in this forum as well as all other people publishing Pro1 videos on the web, discussing bugs and hardware issues, making custom ROMs, etc., are just actors hired to distract from the fact that Fxtec have long moved to the Caribbean where they spend their backer's money on expensive cigars. One wonders if setting up such an elaborate smoke screen would really be easier (or cheaper) than just producing the phone after all ...

I finally made a new image (20220129-UNOFFICIAL) with the January 2022 security patch level. Full list of local mods with respect to upstream Lineage-16.0 tree (practically unchanged since December): Modified gps.conf which (for me) enables the Pro1 to get its initial fix much faster. Corrected QoS powerhint signals. Backport from Lineage 18.1. Keyboard driver: Enable high keycodes Backport from Lineage 18.1. Keyboard driver: Fn-Tab acts as Alt-Tab. Cherry-picked from an experimental patch proposed by @Slion against LOS 18.1. Was never merged into any official dist

I've had one such dot since day one. It has not worsened one bit in 1.5 years. It seems to be a quite common QA problem with this kind of screen, not limited to the Pro1. I wouldn't worry too much about it.

... dazed and confused ... Do you own a qwertz or qwerty device, now? Qwertz provides square and curly brackets only via modifiers (Fn key).

When I place a script named e.g. "99hwoverlays" with the following code #!/system/bin/sh # # Set "Disable WH Overlays" developer option at startup # bash -c "service call SurfaceFlinger 1008 i32 1" & into /data/local/userinit.d/, the "Disable HW Overlay" option gets set automatically after boot. Remember to make the script executable (chmod +x). Also note that user startup scripts in /data/local/userinit.d/ are no longer executed by default in modern LineageOS, you have to install some helper app like RunUserinit from F-Droid.

It's always difficult to discuss topics that are somewhat subjective ... It would probably be good if you could provide a specific and (hopefully) reproducible example of an app that does not scroll smoothly for you. I can scroll smoothly (as far as my expectations go) when browsing through a thread in QKSMS, when scrolling down a web page in Firefox, when displaying a thumbnail gallery in the default Lineage picture app, when displaying folder contents in MaterialFiles, and when browsing through a lengthy program in Acode.

I have never played with those options and am certainly no expert in tuning the Android graphics stack to its max. However, there seems to be consensus that those options are not enabled by default for a reason. That's especially true for the "Disable HW Overlays" flag, which seems to worsen battery life (as more CPU load is generated). I'd rather not mess with those defaults in my ROM. I can confirm that also for me "Disable HW Overlays" is not persistent across reboots (while "Force GPU" is), which is kind of strange -- although it could also be an indication that this is really a

That's a good point. You are right that the Pro1 could -- technically at least -- have had the upgrade to the Pro1X's Android 10 for "free" if the SoC thing had not happened. However, it is also true that updates of stock Android 9 stopped long before the mainboard change. As far as I know, they ran into trouble with their contractor making the OS, independent of the other issues with the SoC manufacturer. Let's hope they (and we) will have more luck with the Pro1X ...

I do not know from personal experience, but people close to the Lineage porting effort have hinted F(x)tec at least suspected they would not be able keep an official Android OS afloat -- long before the 835 thing happened. Seems like keeping a certified Android OS up-to-date is not so cheap after all, let alone porting newer Android major releases to the device ...

I cannot really comment on the state of the stock Android OS as I have been on Lineage since day one. However, especially those who jumped-off stock only recently seem to not look back at all. Considering how unhappy you seem to be with your stock Android 9, I'd suggest you just give Lineage (or some derivative) a chance. I think it is by now clear that F(x)tec more or less intended the Pro1 to be used with alternative ROMs. Yes, I fully agree that they should have either stated this more clearly from the beginning, or properly supported the original OS their phone was delivered with. But

I know you are joking, but I meant that quite seriously. My wife brings home half of the family income, but, for some reason, I thought I need a phone that is 10x more expensive than hers (while having worse audio quality 😉 ). Of course I explained to her why I wanted that Pro1 so badly before throwing all that money at a company that, even then, I was not sure would be able to deliver at all. If you manage your entire household from a common financial pool, it is imho a question of mutual respect to discuss major expenses prior to engagement -- especially if they are about what most peop

You are right, but let's not further misuse this thread for discussing known issues of the original Pro1 (again). Lineage may be able to fix a few more things on the Pro1, but I think we have to accept the fact that, from F(x)tec's perspective, that one is done. Any software issues related to the binary blobs will not be fixed. Imho, we will be lucky to even get spare parts for components unique to the Pro1. Let's see how the Pro1-X comes out and how long F(x)tec plan to keep it available for purchase. If it improves on some of the issues already in the first production batch, and if

I very much enjoy the discussions here, and hope that also F(x)tec uses them for inspiration on future projects. But considering the features of a hypothetical Pro2, I think we should also be realistic: The Pro1/Pro1-X are very expensive phones even without including exotic technologies like e-ink-keyboards. I think 1000 €/$ are a magical landmark, where even enthusiastic keyboard-phone lovers will have a hard time convincing their spouses that they really need that device. A Pro2 should probably focus on getting an up-to-date flagship SoC and improve on the known shortcomings of i

Some time ago, I recommended Devuan as my GNU/Linux distribution of choice for installation in a chroot of LineageOS. Today, I wanted to upgrade my xrdp-pulseaudio modules (providing seamless sound forwarding to Android when using my X11 desktop) and found out that installing them on Devuan is not possible in a straightforward way using the tools provided on neutrinolabs' GitHub repo. The reason is that the drivers need to be compiled against the pulseaudio sources matching the version of each respective distribution. On Devuan, the command: # sudo apt build-dep pulseaudio fai

Yes, just tested that: USB mouse works for pattern-based unlocking, even if one connects the mouse only while the phone is already locked. Bluetooth mouse could work, if it is already paired with the device and BT is switched on. Otherwise probably not ...

That could not be more true. Canonical (at the time they still backed the project) would have liked us to think about Ubuntu Touch and the Ubuntu distribution for PCs as two flavours of the same OS -- as in iOS vs. MacOS. Many users unaware of technical details may believe that to this date. The truth is, for all but a few exotic devices (like the PinePhone), Ubuntu Touch does not even use an Ubuntu Linux kernel! It bundles a minimal version of the device-vendor supplied Android system, including its kernel and driver blobs. It then uses compatibility layers (libhybris) to interface

I believe you have fundamentally wrong expectations regarding Ubuntu Touch. It is not designed as a traditional Unix, but as a smartphone OS, sharing quite a few concepts with Android. This includes app confinement (sandboxing), which actively breaks core Unix philosophy, as data "belonging" to one program purposedly cannot be easily picked up by another. Installing a true Unix environment on UbuntuTouch is possible, but involves quite similar techniques than doing the same on Android, the difference being that with UbuntuTouch you use an LXC container while on Android we rely on traditio

For those with GNU/Linux-chroots: UPower provides a friendly interface to display the information from that sysfs tree. E.g. rostkatze:~ # upower -e /org/freedesktop/UPower/devices/battery_battery /org/freedesktop/UPower/devices/line_power_dc /org/freedesktop/UPower/devices/battery_main /org/freedesktop/UPower/devices/line_power_pc_port /org/freedesktop/UPower/devices/line_power_usb /org/freedesktop/UPower/devices/battery_bm

The point is that the major components that make the SoC useful as a phone are closed-source, like on any typical Android device using similar SoCs. As a consequence, all projects of using a fully open-source Linux OS on the Pro1 are just proofs-of-principle that, while academically interesting, are so far from prime-time that the last Pro1 will likely have gone the way of all silicon before they mature to the point of becoming practically useful. Do not get me wrong: this is not an unusual situation. Practically all Android devices depend on these proprietary blobs, as we both know. As o