Leaderboard

Aaaand done! Here is the replacement display: https://www.dragonbox.de/en/spare-parts-tools/lcds/fx-tec-pro1-replacement-lcd And here the service, in case we should do that for you (display included in the price): https://www.dragonbox.de/en/repair-mod-services/after-warranty-repairs/fx-tec-pro1-display-replacement-service

Hey all, I've been using Ubuntu touch for about a week now and Ive started working on patching some of the issues with them. I thought some of these fixes would be appreciated by you and I also wanted a public forum to discuss problems and potential solutions for them. The main issues I have noticed with fresh install of Ubuntu touch my new pro 1 are as follows: GPS ❌ - Straight up not working. I may be able to patch driver support across from the lineage git but im too busy rn. Flashlight ❌ - I believe this one shouldn't be to hard to patch, just a matter of finding the right g

I think it basically has a fair price.

Asked one of those mall kiosks for phone cases to hook me up with some kind of pouch. This one isn't real leather but it fits nice and snug, looks better and is quicker and easier to put inside and take out of compared to the stock felt pouch.

Are you a collector? 😄

Finally i got my third Pro1

@Raksura wrote this list a while back and from my testing and with my patched the following are now working: Backlight, Cellular Internet, MMS and Telephony. So it is getting much more usable as a daily driver IMO.

Thanks for the hint! But that rises again the question for a wiki or something alike to keep this kind of info easy accessable. Cheers, order#10148

With my understanding the "recovery image" for Pro1 comes together with "boot image". The "boot" is only missing in the naming of the recovery-file offered for LineageOS. The fastboot command flashes the "recovery" into "boot(_a)". That means, as long the LineageOS-recovery.img is flashed into slot A, the boot-img-part is not the right one for Ubuntu Touch (that also resides in slot A) and Ubutnu Touch wont boot up fully. It needs to have its boot.img (re)flashed into slot A. So instead of "keeping" I suggest temporarely flashing the LineageOS-recovery-image to slot A, boot into that slo

My Pro1 also started to do this yesterday. Perhaps not the worst condition yet as I can still make this post on the Pro1, but sometimes it doesn't allow me to input unlock code but fills the field with random digits instead. And now the cursor started to warp to address field, which makes typing quite annoying 😄 Just going to start a three week trip today, what a great moment for the device to go mad.