Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


claude0001 last won the day on January 15

claude0001 had the most liked content!

Community Reputation

584 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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 ...
  6. Best thing about that story is that, a few weeks after that comic hit the net, someone published an actual open-source 3D model for a tiny violin.
  7. Thanks for sharing this article. Note that the comparison is quite unfair with respect to LineageOS in that, in this study, the LOS device had GApps installed, which then -- unsurprisingly -- phone home to Google in the same way they do when installed on a commercial AndroidOS. The Lineage Project does not ship GApps in their ROMs -- users have to install them separately (and willingly) from a 3rd-party source after flashing the OS. I think it is safe to assume that a LineageOS with MicroG (as also used by /e/) or a vanilla LineageOS (with neither GApps nor MicroG installed) would co
  8. 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
  9. After reading a little, I am under the impression that /e/ is indeed more about the default software distribution than about the underlying OS. Not to turn down that effort -- sane defaults that just work out of the box are certainly a good thing. I'll keep using vanilla Lineage (without Gapps or MicroG) for now. The Aurora store also displays tracker information from Exodus btw. But most of my apps are from F-Droid anyway... Thanks for sharing.
  10. Thanks for this heads-up. Out of curiosity: What are the differences between /e/ and plain LineageOS without Gapps? LineageOS MicroG has been available for a while (and is not classified as "beta").
  11. 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
  12. 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
  13. 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
  14. Actually, I find the Pro1 is too large for comfortable thumb-typing. Travel of the thumbs is too long for some keys when holding the phone by the keyboard. From other discussions here, I know that I am not alone with this opinion. I certainly could thumb-type much faster on my good old N900 -- though I must admit that I neither miss the small screen size of the latter, nor the absence of many special keys the Pro1 has ... I can well imagine that the PlanetComputers keyboard is even much less comfortable to thumb-type on, but -- in all fairness -- I do not think that was the design goal o
  • Create New...

Important Information