Leaderboard

Unfortunately, firmware has to be polished, so my advice is to wait for a firmware update which may improve some of the problems...

From what I could mesure, the camera 'island' is a 0.8mm 'bump'. So would have to be a really tight fit covering the camera, to make any difference

On my side, it's really strange. The keyboard works really (quite) perfect....since I completly disabled the auto-rotate screen in LOS18.1 as I never use it, as 'clacky keyboard on' automatic set the pro1 in landscape mode. I think it's the first time I write here without a keyboard bug. Too good to be true, so I will test a few days and report here. (...I write still a few words because of murphy's law and fatality of life to be sure....incredible...)

Basically sensors and buttons are at the same positions, only camera has a small difference (camera of Pro1X is out a bit by design).

Updated the first post with warnings regarding the restore of backups. Sadly, i could not identify a pattern in which case restoring a backup works reliably. Even after days of trying and countless reflashes/lock/unlock BL... I managed to put a device in the perilous state where a restored backup with contained keys does not make those usable in Android. And was not able to recover from that state by any means. I documented the way i reached that. But the unsettling thing is, i did nothing different than during the successful restores. Until someone else with deeper knowledge solves t

I think my Pro1X just did this a few minutes ago. Suddenly appeared powered-off and unresponsive, had to try holding the power button a couple times before it woke back up. I checked dmesg and saw a huge number of these lines: [ 2836.383934] mas_ioctl: cmd=0x80044d22 [ 2836.383941] mas_ioctl: end. [ 2836.394128] mas_ioctl: cmd=0x80044d22 [ 2836.394137] mas_ioctl: end. [ 2836.404314] mas_ioctl: cmd=0x80044d22 [ 2836.404323] mas_ioctl: end. [ 2836.414717] mas_ioctl: cmd=0x80044d22 [ 2836.414726] mas_ioctl: end. I have no idea what this is referring to.

After seeing all the quick replies I decided I would open it up and just check it out (after finding a thingiverse possible case solution). Everything works perfectly (well I haven't tried to charge it yet, or traveled away from my home): wifi seems as good or better than my 2XL, Verizon works when swapping SIM from my old 2XL (calls in/out, text in/out), speakers sound good, screen rotates as expected... Really I am starting to feel good about this device...I still want LinageOS so I don't need to have all the Google default cruft, but still being ASOP basically the phone is quick and

If you really aren't interested in the phone, leave it closed box. As @EskeRahnsaid, FxTec will honor the warranty for the new owner. If you don't know if you want the device or not, but are worried that open box and tested will lower the value, I wouldn't worry. Take it out, try it out, see if it might be something you want after all. I don't think there is any reason to charge less for open box and tested (again, the warranty will still be good for the new owner), and, who knows, maybe you'll change your mind. 😉

Edited the first post with working repair instructions using restorecon. Ii just now successfully found that way to be working on my side. 🥳🎉

@Hook Wow! You are a 1-in-1000 good hearted person! Your trust in this company is over and beyond. (I mean that absolutely positive!) I absolutely believe that Chen's top target was to deliver a top product. And it shows on what they delivered (Q/A is another issue, but you can definitively see the intentions were right). That's not the problem. But due to all those hiccups, it obviously turned into a "saving face" game instead of truthful communication - and no - it wouldn't have taken a single more minute, to write what's going on than to write "we're about to ship next week" for t