Leaderboard

EDIT: this build may not be good, flash at your own risk! Alright the new build is up. Same link. md5=4981e2547d288954d588d8ac4301e3f3 Build date: Dec 6, 2020 I've added exfat support, updated to the latest code, and I'm investigating why the file-based incremental updater (still!) won't work properly. This time it is selinux issues. Sigh.

I have a bit of a unique perspective as a developer that was given a device and also privileged to some extra chats with FxTec. FxTec is a good company with good people and good intentions. They have worked very hard to deliver even though covid killed their ODM and almost killed them. They will do their best to get all orders filled, I'm sure of that. That said, FxTec has awful communication practices. I truly feel for folks that pay good money and don't get any updates for weeks or months. And for folks that send their device in for repair then don't get any ETA or u

Just wanted to add that there are also some native us-intl xkb variants (with or without dead keys) coming pre-configured on SailfishOS.

@Kikka Things my Priv does better in order of personal annoyance: Physical keyboard alt and shift had a lock (meaning I pressed shift, took my finger off it and then the next letter I would press would be a capital letter, same for numbers), on the Pro1 I have to use one of the 2 shifts or fn keys and keep them pressed while pressing another button, and also alternate between them, depending where the letter or symbol I want on the keyboard is, as it's wide Pro1 sometimes gets stuck on silent but reboot fixes that and it didn't happen that often Much better loudspeaker/c

Yes. The Pro1X is simply a Pro1 with (if chosen) more memory and a different colored case. They have done no redesign of any sort here. Of course, I am just basing this on converging evidence (I'm not from FxTec), but I have very high confidence that what I say is true.

Hi all only for inspiration. I had problem with my cover. Fxtec was very big problem eject from cover so I did fix:

I've updated my report following a full firmware restore + clean install that was intended to let met clearly define how to reproduce the telephony issue but ended up removing it altogether. Haven't gotten GPS to work yet (and cellular internet doesn't appear to be working either). I don't know where to get details about UT development specific to the Pro1. There's UBports's repository collection, but it's not Pro1 specific. Installation is very easy: https://ubuntu-touch.io/get-ubuntu-touch

Correct.

I really believe that everyone will get their phone and things will speed up over time, even though fxtec has struggled to get things done in a timely manner so far. Bringing a phone to market as a startup is no easy feat. Your concerns are legit though, I'd only advice taking the dive if you are willing to wait.

I've been using Ubuntu Touch for about a week: Here's a report of what works and what doesn't: - OS Install process: almost perfect, a slight documentation issue for first time ADB users on Windows 10. ✔️ - OS Welcome thingy: Impeccable. ✔️ - Wi-Fi connection: Impeccable. ✔️ - Lorimi (the window manager): impeccable. ✔️ - The default terminal app: works well. ✔️ - GPS: does not work. That's an immediate deal breaker for me, but since I don't need to travel during our current quarantine, I'll test things out more. ❌ - Media player (for music): impeccable. ✔️ - Default web

I just now saw @Kikka posted this on the 20'th of February. Wish I noticed this before writing that novel above, but since I ordered mine on the 19'th of February to replace my Priv, I'll just enjoy the coincidence. :)))

Another quick update... My day job has been keeping me pretty busy, but I've made some progress. The archiver now builds and runs on Android, both in stand-alone and client/server mode. I have some more work to do before it is ready, but it's definitely progressing. Also, I still have to write a basic app for creating and managing backups and restores. I'd like to say this will be done in the next couple weeks, but I can't make any promises. Additionally, I was reminded that neither stock nor Lineage support exfat. So I will add that into the kernel for my AICP bui

I noticed that we can select the color of the frame on the indiegogo page, so there is an option "black" as well. Before I proceed with the order, I wanted to get confirmation that this frame fits the pro1 as well. Does it?

@claude0001 I can believe you about the USB. I always had issues connecting phones to Windows based PCs

This. That USB connectivity on the loader level is so picky about the partner device is a huge pita - it is however no problem that seems to be limited to the Pro1. For the records: I found that the only device I can use to reliably flash my Pro1 is my Raspberry Pi3. Both of my oh-so-sophisticated Thinkpads (one with USB2, one with USB3) either do not detect the Pro1 at all or run into random errors during data transfer. Considering how cheap the Pi3's are, I am thinking about getting a spare one just for the purpose of interfacing with the Pro1. 😄 Edit: @MickH : Good luck with

Most remote desktop solutions (on Android) can emulate right click by two-finger tapping the screen. Some can even do middle click, though my MS RD8 can´t. Security should not be an issue as you can limit access to localhost only in TigerVNC or XRDP. If needed, one can then still access the device remotely via SSH tunneling. Performance is worse than in your solution as the remoting layer adds extra overhead. Mounting my "home" in Android (i.e. /storage/emulated/0) is precisely what is working only sort-of in my chroot. Effectively, I can only read data from there, but not write there, ev