Leaderboard

They stepped up their game again. Since a few weeks support is answering and sending out parts again. I got a new USB-Board a few days ago, which has brought me one step closer to revive my precious pro1.

I haven't noticed this issue on my phone either. I also have GSM battery manager and 3C all-in-one Toolbox installed and this is an early Pro1 if that matters.

I currently have two Pro1s on Lineage, and am unable to reproduce the issue, no matter how much I let it charge or discharge, and no matter if it is a slow or quick charger. One of them recently factory reset (had AICP on it before). So unless there are unknown hardware sub-variants, it must be something different we got installed that somehow triggers (or remedies) the issue.The only explicitly battery-related I got installed is GSAM battery manager, and 3C all-in-one Toolbox. Both just monitoring the usage.

FYI, the DeviceSettings UI fixes will be in tonight's official build. If there is any problem applying the custom keymap, the user will see a 'toast' error notification and the custom keymap will be toggled back off again. This resolves the problem that there was no feedback when things go wrong. To test, you can use any keymap with a syntax error. I have been using this one for testing: 70:0000:0000 Since there's no key 70, this generates EINVAL which triggers the failure notification and modified UI behavior. I'm sorry this problem wasn't noticed before causing VaZso so much f

Hey guys, at least I found a kind of flip case fitting for my needs. I don't carry my Pro1 with me a lot, so the bulky design doesn't matter and it's well protected at home 😄 I've bought it at this Etsy Store, not sure about international shipping but she's located in Munich. I like the idea of wrapping this elastic plastic stripes round the edge of the keyboard, so the display can close properly. If you order you can tell an individual phones size, choose from the Pro1's data sheet h: 154mm; w: 73,6mm; d: 8mm (depth only keyboard). I also asked her to make the whole bag 5mm wider

Sad to hear. But just to be sure, are you on stock Android or LineageOS? (Some are having charging-issues on Lineage)

Having switched to Lineage OS as my daily driver I quickly noticed a couple of apps still don't support landscape namely: Reddit and Microsoft Teams. Thankfully the "Force landscape when keyboard is open" feature from Fx Service still works great, to my surprise. Congrats to self 😁

As I read what @3zet writes, the point is if you have some software that stops charging when full (to prolong battery life when constantly connected). Charging ought to be accepted again once below a certain threshold.

Yes, looks like your USB-C connection has a hardware problem. Hope you can reach F(x)tec support. Be warned though, it seems they have been rather useless lately. They may also have run out of spare parts. Alternatively maybe you can use someone like @EvilDragon to resolder the USB board.

I decided to make the jump and use Lineage OS 18.1 as my daily driver. Moved both my SIMs from my stock Pro1 to my Lineage Pro1. Though I'm not using the official release. Instead I have a custom build with a modified keyboard driver, which is work in progresss. It seems I can still develop that driver without compromising my daily regular use. Took a bit of time and a few reboots to get my Orange FR SIM data to work but I had the exact same experience on stock as I recall. 1&1 DE SIM data worked straight away. Just wanted to congratulate everyone involved in making Lineage OS on