Leaderboard

Excerpt of the latest changes in the list in the FP:

Hi all, I've been watching from the sidelines for a little while, so I should probably introduce myself. Electrical Engineer from Manchester UK now settled in Tauranga NZ, currently driving a beaten up Cosmo Communicator running Ubuntu Touch (dropped it, radios stopped working, still a nice PDA) looking for a replacement with working telephony, Ubuntu Touch, and a keyboard of course. Nice to see the Pro1-X finally rolling out, despite some serious issues beyond F(x)Tec control. Really great to see pics of a Pro1-X running UT, and so shiny fresh out of the box. It's a

I cannot agree more with the neofetch show off part, nicely put @claude0001. And actually I am afraid that many users of LXC on SFOS or other systems have felt overwhelmed by the extra work needed to configure their DE, or just don't see how much of a game changer it can be, and they end up not using it much. I have a VERY configured LXC container from my Pro1 that I can use and attach on my Pro1x, but so far I haven't been able to start X on it. It is a bit oudated and there's probably something that is conflicting, I have yet to identify what the issue is because I can start X in newly

This, 100%. Imho, configuring your 'containered' (desktop) GNU/Linux distro in a way to make best use of the small (touch-)screen is a large part of the work. That is, if you want to actually use the system productively rather than just show-off your neofetch output online to your friends once ... 😉 . Trying to operate applications designed for desktop workstations via a touch interface can be frustrating even on a full-size display. On a small handheld touch-screen, the experience can quickly become infuriating, unless given some significant GUI customization. In my setup (bas

My Pro1 is running happily again with a brand new display I finally got from FxTec, but thanks anyway! 🙂

Sure, I posted a link above in the message showing LXC pics, here it is: https://talk.maemo.org/showpost.php?p=1574496&postcount=237 The setup is not exactly user-friendly at the moment because the dev of harbour-containers does not use Sailfish anymore, and some things have changed, but it can still be made to work. Then in my opinion you also need some configuration inside the container to make it really convenient for the small screen size and to use keybindings as much as possible instead of touch (see what I did with my Pro1 for instance: search on Youtube for "Pro1 Saiilfis

Same. I bet this is a radio firmware problem, not a radio hardware problem. I'm sure as more people get their devices, these kinks will get worked out.

I self-declared 741€, the amount I paid F(x)tec, ergo 177,84€ VAT.

Just paid 24% VAT upon my Pro1-X's arrival in Finland. Edit: And tracking now shows customs release.

Mine arrived today, in the US. Ordered from the website.

Thanks. I knew there was a thread somewhere.

Looks like $300 declared value (as mentioned previously) plus shipping at standard 20% VAT (no duty) - exactly what I would expect to see.

I found and am using a tempered glass screen protector that fits the Pro1X: https://www.amazon.com/gp/product/B07H9QSJK3/ The fit isn't perfect, but it's pretty good. The screen protected doesn't curve quite as much as the Pro1X so there are corners, but to me that's a positive; the tiny corners of the screen protector make it much easier to open and close. For the bottom, I am using an adhesive rubber sheet cut to shape. It works pretty well.

Extended or maybe eXclusive as it was planned to be only one manufacturing run in a special colour and yes, there were special options. Anyway, I don't know if original plan was needed software modification or not, but if so, it should had been only a slight modification which would also be running on Pro1, so practically it is close to nothing. Because of a redesign was necessary, unfortunately, it has caused also software incompatibility. I would not think higher amount of RAM and Flash were intended to be exclusive for Pro1-X but blue colour is. (Pro1 was practically prepared

The Pro1X was PLANNED to be a Pro1 eXtended with more ram, and changed key-layouts.... But after they were swindled, they had to redo the whole thing with a different chipset, and this is why the old code was supposed to have worked (almost) unchanged on the planned Pro1X, but will not work at all on the actual.

For all the issues that I reported on the other thread, wifi isn't one of them. Granted, my home wifi sucks, so I haven't tried to do anything very heavy.

After comparing Pro1x, a Pro1 and a Titan Pocket, they all report similar dBm for my WiFi network, but maybe the Titan is just not great either?

Good point, better to have backed up and not need the backups than the other way around! Some more info: I did not time it, but I think I let it sit at the boot logo for 2-3 minutes before rebooting and flashing LineageOS again. I assume that the firmware flashing actually happens pretty early in the boot process, so I wouldn't be surprised if letting it boot for a much shorter time works as well. Haven't seen any anomalies since I did this. Used my phone with my banking app, Whatsapp, Android Auto, etc. The only difference is that I am regularly surprised that UI elements at

I found an easy way to fix this from any ROM, without having to wipe userdata. tl;dr: Edit: Make backups. It shouldn't be necessary, but you never know! Flash the 2020-08-25 stock ROM, but skip flashing/wiping userdata. More info here. Let it attempt to boot (for a couple of minutes). It (very probably) won't ever get through it, because the userdata partition wasn't wiped. This doesn't matter, though. It does flash the touchscreen firmware, which fixes the unresponsive screen edges. Edit: I did not time it, but I think I let it sit at the boot logo for 2-3

I would not say it is safe considering it is more than a year since it was updated... I have used stock OS because it was set up and it is a bit harder to do a major update on a daily driver without a proper way of backup/restore in case something went wrong... However, stock OS simply had a lot of problems and LineageOS works as good as possible, the only problems remained were built into kernel, so they are basically not LineageOS-related. Device is really fast, NFC payment is working, every functions work as they should...

They have stopped pushing updates for Pro1 a very long time ago. ...or is it about update system which also stops working? Anyway, LineageOS still provides an up-to-date Android environment, however, there are still bugs in kernel which could only be improved through manufacturer as having closed-source components and what is very sad to be left alone...

Can't speak for wherever you are, but here in Finland they are very clear about that: "In the case of customs declarations for release for free circulation, the conversion rates applied are those valid on the date when Customs accepts the customs declaration for the goods." So at least here, no, you can't get around that unfortunately.