Leaderboard

You really think someone wont post on IGG within 2 mins of the first batch of e-mails being sent? I'm pretty sure they will. Four whole days left in this week...

Thanks for mentioning my LOS 16 builds. For completeness: @daniel.schaaaf maintains an unofficial ROM of LOS 17.1 (Android 10) for the Pro1. In principle, the sources of all four LOS branches (16.0, 17.1, 18.1, and 19.1) are still maintained at lineageos.org and are getting patched based on the Android security bulletins. It is only that - by LineageOS policy - only one branch per device (in our case 19.1, now) is allowed for the automatic weekly builds, probably in order to save CPU time on the official compiler farm. It is however totally possible to build any of the supported

Or for us silly Yanks who don't have the sense to use metric system: 6.05" x 2.90" x .55" 😉

On Android. The "subkey" which allows gathering the decryption keys is stored in the boot menu. Supposedly to ensure if the bootloader is unlocked, it's impossible to reach the keys. I'll help you with that. The answer is: Yes. This is knowledge of Android 7 (AOSP), btw. But given how lazy they are. It might very well still be relevant: Android stores keys to reach enough for booting in the bootloader. Usually just enough to reach the lock screen. However, if you have fingerprint unlock or face unlock (whatever those techs are called), there's no effective additional decryption

So it looks like with all the screen refitting, the flex cable on mine gave in and no longer connects the display. Anyone tried ordering the flex cable between the two halves?

Search it on phonedb...here you can compare it with another devices https://phonedb.net/index.php?m=device&s=list

Same as those of the Pro1X: 154 x 73.6 x 13.98 mm, 243 g

Though I doubt that it is software, you could try to install and run KeyEvent. Showing the make and break codes for each key. If you press one key, and keep it down, and then another you will see that it you wil get independent codes, and two different up's If you do the same with the two shift keys, you will see that they act as parallel. Press and hold 1, the press and hold the other, and relase the first then the second, and it acts exactly as if it was one key. The yellow arrows does not (and if they work, the ctrls act in the same way as the shifts(

(on the wiring, the two shifts and the two ctrls are physically wired pairwise. so though we see 66 keys, there are only 64 distinct keys)

Right, usually keyboard builds up as a matrix and also Pro1's keyboard was built this way. However, there are a few keys which have its dedicated IO for allowing truly independent keypresses and these keys basically are the function keys... ...so yes, although Pro1's keyboard has a keyboard matrix, ctrl keys wired together and go to a dedicated IO.

Basically Pro1 only has one ctrl key reachable from two places, so a problem at one side may affect also the other side easily.

Just for the record, I've been in contact again lately with Fxtec asking whether there was anything to be done with regard to my USB connector and my screen, for which I'd prefer an original replacement because of the margins problem. Of course I'd want the screen only if I can get the USB fixed, too. They came back quickly informing me that displays were currently available; then they wanted me to confirm whether I meant the device's USB socket, which I did. It's been a few days since then, but let's see what comes out of it.

Citing from the disassembly guide (https://github.com/imax9000/fxtec-pro1-teardown): When inserting phone body into back casing, insert the edge with buttons first, then push the rest in. Starting from any other edge is a sure way to shear those buttons off. (Guess how I know this... I assume, that's what happened here.

20% VAT + 2.5% Duty + £8 handling fee if you're unlucky, and you probably will be as it's well over the limit. Fxtec spent the money that would have covered our customs fees on the redesign - I'd rather pay on arrival than not getting a phone so while it's not great it's hard to complain.

Lineage recovery works just fine for AICP. Never tried recovery for 19 but I don't think that AICP being still Android 11 while 19 is 12 matters for using the recovery. I don't truly know the risks of not patching. Anyone still using stock Android on the Pro1 hasn't been patched in 2 years, IIRC. There is someone here who is unofficially maintaining Lineage OS 16, keeping it patched every couple of months (He runs it Google-free, but no reason you can't add Gapps). Scroll back for previous discussion. You can follow his link here for the latest update: http://findus.zwe

Yup. Though I prefer the qwertZ, i would much rather have a Pro1 with qwertY than no Pro1. 🙂

The biggest problem (for me) would be the shifted key locations instead of missing umlauts. Personally, I don't need German-specific umlauts but I am very happy with Pro1's QWERTZ variant because at least it has standard QWERTY key placements. Anyway, it may worth a question for F(x)tec if they may have QWERTZ or current non-shifted QWERTY keyboards as spare part, but it may have low chance before Pro1-X availability. However, replacing the keyboard itself of a shifted QWERTY variant to another one is possible. ...but you are right, most of the Pro1s were sold together with sh

I get no response from the keys when using the built-in test software (the one you get when you click the build number multiple times).

Hi people, I am a Pro1 user for over a two years right now and I broke my USB socket. So if I am reading this and other topics correctly, the biggest advantage of this phone became its biggest mistake and fxtec does not only even have replacement part to be bought to fix own Pro1 but also does not responding to the emails, am I right? How screwed I am? There is any chance to buy the USB socket assembly? I sent an email to fxtec but if they are not even responding then I have no Idea what to do.