Leaderboard

I assume most people will do the same, those ready to use Ubuntu Touch or LineageOS probably were prepared to flashing themselves at some point anyway. I asked to change too, but made sure they knew I wouldn't keep Android. It probably doesn't make any difference, but just in case, I want F(x)tec to know that offering alternate OSes was and still is greatly appreciated and a selling point for me, despite this temporary choice in favour of Android to get the device earlier.

Here's the complete message: So now the suspicion is confirmed that LineageOS (also Ubuntu Touch) isn't ready for the shipping of this batch. Sad, but good they let us change to Android, I've just sent the mail a minute ago! EDIT: And the change has already been confirmed by Fxtec.

From the latest update: The available engraving area must have been increased in the end. I remember mine (top left, IGG contest reward) used all available space in height and width in the demonstration render they provided, but I see the lunar module in the bottom row is much higher. Not a complaint at all, it is good news for those who wanted bigger logos!

Updated too...it takes long time...play store still, magisk too...all works 🙂

@EskeRahn Hi now i have feedback. They have repair parts so my phone is repaired. reason for waiting that they did not had parts... So I wait on delivery....

I have attached the actual data sheet for Pro1's touch controller (which also has register information) to this message. Registers 0x805B and 0x805C are still there. 🙂 GT928 Datashet English.pdf

I've taken a photo of the chipset inside my first replacement screen which worked fine for a year until I broke its glass. It's not very legible on the photo but it's a GT9286.

I've also asked to switch my option to Android in order to avoid further delays. Got confirmation after a few minutes.

Yep same, got the confirmation too. Looking forward to it!

I have ordered one - better to have more than having none of a keyboard phone. 😄

Two years later....BUMP! I guess this didn't happen, but if @Hyrum is still around, there are a lot of people who now own these things, and X variants heading out soon. Show of hands....who's still interested?

It should work for Pro1. These displays usually have some smaller or bigger black spots mostly at one or two corners, otherwise I have replaced my screen to one of them... three times. First was a short-life unit because of insufficient glue (only two-side glue what was provided), second last more than original and third is the current one...

So I found this for 30 shekels...... https://m.aliexpress.com/item/32956500815.html I hope it's not fake for so few shekels. At that price I could have a bunch of spares, or order a bunch and sell pre-flashed units for less than the ones fxtec sells and still double my money. I feel like there would be a market for this considering this thread exists :) I could even let people trade in their unflashed ones for flashed ones at a reduced price. Am I an evil capitalist, a genius, or some of both? :O After reading the reviews it sounds like there are enough quality issues that I'l h

I wonder how it will go with the upcoming Pro1X devices, if they will even have LineageOS ready yet, which doesn't seem to be the case at this point. In any case I'll keep my battered Pro1 in a drawer even if only for flashing replacement screens without having to perform any such tricks on my future daily driver...

for me the touch worked perfectly after flashing OTA 2020-08-25. And the fastboot flashing worked fine as well after removing the "rem" from the line in the script that flashes the system image 🙄 So now I have upgraded all the 4 spare displays I have, hopefully I can stay on LOS for a while now. //Per

this is a gt1x driver for android, that might be interesting https://github.com/goodix/gt1x_driver_generic

The "gt1x" could well indicate x is to be replaces with some digits, According to this, at the least a gt1151 exists, so that might be a relevant guess? Have we got any good images of the print that might help? We expect a minor square chip like on this image. ADD a little more googling indicates that a gt1143 and gt1152 also exists

Okay, so Pro1's touch controller seems to be model GT911, PDF attached. ...or at least it mentions our 0x5D and 0x14 addresses which is a calming fact... ...and yes, it also has 0x805B and 0x805C registers for setting blank area. These are R/W values, so it is recommended to read before writing and also reading stock values of Pro1 would be interesting. Also touch/release levels may be set differently anyway. 🙂 GT911 Programming Guide_v0.1.pdf

Another option would be to find I2C line of touch controller (physically), attach a logical analyzer, then let stock OS boot and analyze its initial communication during boot process. 🙂

You are right and it seems the manufacturer of touch screen controller is correct but the actual model is basically seems to be different. This document states "GT928 has 2 sets of slave address 0xBA/0xBB & 0x28/29" but we have address 0x14 with an alternate address of 0x5D which is different than what is written in this document. However, it may be a very similar command what we need or (considering it is the same manufacturer) it may also happen to be the same, however, I would not try it. I have only found it described as "gt1x" but a better model name may help and a pdf whi

I'd also like the original APK/set of files used to fix the edge issue in 17.1. Let me share my experience and research here: 1. When flashing to stock to resolve the issue, having the phone actually boot up the most recent update is necessary. Otherwise the fix does not work. I know this because I tried flashing an old version of stock and installing the stock OTA updates via the normal (booted!) route. The issue did not go away at any point during this. I then flashed the non OTA 2020-08-25 stock version again and let it boot. Only then was the issue resolved. 2. Given that th

Not even a month... :)) Just wait... and wait... and wait I'm waiting for a warranty display since october/november 2021. Not even a response to my last reminder email.

Well, got it apart today... Found what appears to be a manufacturing defect... The sheet metal clip holding all the ribbon connectors on to the main board was installed in such a way it had partially cut the battery ribbon cable right at the connector... Looks like I need a new battery as well... I'm not sure if the battery is still providing power to the board or not... Reseated the ribbon cable to the USB board at both ends... No change... Will not charge or boot. Disconnected the USB board ribbon cable and tried to boot. Did not boot... While testing charging, I notic