Leaderboard

Definitively not. It should be a multi-layer board and a discontinuity simply can happen at an inner layer. However, connector may be accessible (not easily but may be soldered) and an appropriate power wire could be picked but without documentation it is not easy, also BGA packages do not help at all. Maybe one usable 3rd-party info would be a pinout of display's wiring itself - it may happen it may be reachable somehow and may be checked if appropriate power wires are present, also it may happen power wire of display part may be used to powering touch, but these are only tips from f

When has your keyboard stopped working anyway? Did it work before replacing the screen? If I²C was not working, other devices on the bus were also missing. Any devices can stop the whole I²C bus easily by pulling down data or clock wires but that would also stop other devices on the bus to work. So the bus itself (that part of the SoC) is working. Anyway, have you used a metal tool to disconnect connectors? Naturally, replacing the motherboard would help but even F(x)tec does not have replacement motherboards for Pro1 as far as I know. My suspect is somehow you mad

It worked out of the box for me. Boot to Lineage or AICP recovery, choos apply update via ADB, then on the host PC: 'adb sideload Magisk-v24.3.apk' Good to know it worked for you. One important comment is that if you are coming from a fresh ROM install, you should flash your ROM via sideload, then flash MindtheGapps or OpenGapps, then reboot to system. After you get to the Android screen, reboot to recovery again and then sideload Magisk. I'm not sure if the reboot to full Android screen is needed, or just a reboot back to recovery is enough. So I always reboot to system first.

Out of subject, but I install the kraken apk who ask every time fingerprint confirmation at start, and (strangely for me) it works perfect every time. Fingerprint when phone is locked works one in ten. It could mean there's also a low level software possibility for this problem. We definitely need a retro-engineering work on this phone 😄

Interesting... it sounds really strange you have more parts which are not working... do you also have other devices on I2C-6 what I wrote earlier? Naturally I don't know Pro1's schematics but another idea may be a missing power line somewhere - so at least for touch panel, I²C line seems to be working. It uses two wires, an SDA (data) and SCL (clock) signal... device may have other pins like interrupt but basically two other pins are needed which are VCC and GND. So if these parts are otherwise working and SCL/SDA lines are connected, then either power does not reach these ICs or GND

Then I would think of a discontinuity somewhere which may be a not properly plugged cable (between main board and display) or really a touch controller (practically display) fault. You may also check visually if there are any problems with display cable or its connectors (like a deformed pin). So connections, connectors, display cables and also display can be the potential cause of your problem.

Do you see other devices on the bus? So in my case, also 0x08 and 0x09 exist, how about you? Right, it may happen a simple disconnection or an unfortunate event your display has a faulty touch controller, but I²C may also stall and that is why it is interesting if you see other devices on the bus.

It may happen - @agent008, maybe it worth a try to check if i2c-7 has a device address 0x14 using i2cdetect, so if touch controller replies to its address or it is simply inaccessible. However, it needs root privileges. It should look something like this (if querying all addresses): ~ $ sudo i2cdetect 7 Probe chips 0x03-0x77 on bus 7? (Y/n):y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- UU 09 -- -- -- -- -- -- 10: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- --

The fingerprint sensor works. I have been using the phone with a USB -C hub with a mouse connected to it, that is how I can navigate the system and how I was able to install Termux and run i2cdetect. Every time after flashing I use the mouse to pair a bluetooth keyboard+touchpad, it's fun to use an Android device without touch, haha. 😪 Apart from the fingerprint, I have devices 0x08 (microphone?) and 0x09 (unknown device?) on bus 7, and on bus 6 I have 0x28 (NFC). I spent 2½ days troubleshooting this and now don't have much time to look further into it until the weekend. If I ha

Is the pcb a plain old two sided or multi layer print? In the later case it can be hard to spot/fix, without a diagram, It might only leave a slight miscolurisation around an area where the fault is internally. But tiny lane, tiny burn, tiny spot...

Smoothly installed aicp_pro1_r-16.1-WEEKLY-20220504.zip on March 5 security patch and open_gapps-arm64-11.0-pico-20220503.zip using adb sideload Known keyboard bug still there (see lineage thread) Note that the security update date is still stuck on March?

@VaZso : bingo! I don't have any drivers using address 0x14 (just "--" instead of "UU" on row 0x10, column 4). So I'm now suspecting a hardware issue, either flat cable misconnected or something else. Did I understand this right? Any other testes I could carry out to confirm there is nothing at address 0x14? Thanks

Okay, before opening the phone again to check the screen connector etc I'll flash Lineage or AICP and Magisk for root then I'll run i2cdetect and report back here. Tks

...i have now forced samsung adb driver on w11...without problem 🙂

LineageOS 16.0 is basically Android Pie with the proprietary Google stuff removed. The Linux kernel is identical to the one shipping with the Pro1's Android OS. As it is the kernel that is doing all the hardware support, I would thus assume that a device that works in LOS 16 should work in Stock Android, too. But, no, I haven't tested it. Sorry.

I see. I might try an older stock then, if OTA is still up i might be lucky. If I understand this correctly, if the freshly flashed 20200825 ROM doesn't do the touch margin adjustment, neither would an OTA update from an earlier version – and you might be having a completely different problem. "Screen completely unresponsive, 100% not working" would also make it seem so. But just to be sure, did you actually boot the 2020825 stock ROM after flashing it? It needs to start up once to do the touch margin adjustment trick.

@claude0001so you have not tested it on andriod? because i have andriod installed and want something to work on andriod basically im not looking at speed, but sometimes i would need to connect to a network thats only has wired ethernet

I have got this combined card-reader, USB-hub, HDMI-adapter, and ethernet card: https://www.amazon.de/-/en/gp/product/B093FKT9BF/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 All features of that hub work out-of-the-box in LineageOS (16.0 over here, still). That said, performance-wise, the Ethernet adapter does not even remotely reach the advertised 1 Gbit/s: iperf3 measures ~150 Mbit/s up and ~230 MBit/s down. On the same network, with the same peer, I easily get 300-400 MBit/s via the Pro1's WiFi ...

I just removed the usb c connector and put some small wires from GND/VBAT to the outside through the USB connector hole. Luckily at work we have all the necessary tools. At some point i guess ill solder a new usb c port. For now i'm absolutely statisfied charging it on my bench PSU. Constant current until 4.2 volts and then constant voltage, right? Again im very happy that this phone is so serviceable.

Hello, i have writen small tutorial here ....or you can order whole bottom board directly from fxtec...but it will be long waiting for it. Directly charging battery is not good idea...you can littlebit charge it with laboratory power supply , but is needed to watch whole charging process. Fx dont have qi charging. Water inside connector is problem, but it is not whole problem - you must open phone and clean all an resolder all visually coroded parts.

Really sorry that this is happening for you, and appreciate you posting a timeline for others to see. My Pro1 also experienced a similar fate (went black one day, wouldn't turn on, wouldn't charge, etc). I opted not to send it in because I worried I'd never see it again. I gotta hand it to Fxtec, though. Before this phone, I was a die-hard hardware keyboard user, and the merely okay experience of the Pro1 followed by its early demise cured my need for that. Turns out a basic keyboardless smart phone is juuuuuuuuust fine.

Hi, i got a drop of water in my usb c port, so now it wont charge anymore. Can someone please tell me 1. Which wireless charger will work with the pro 1? 2. What is the process to replace the USB C port? Which parts do i need to order where? 3. How else could i emergency charge my pro 1? Manually directly at the battery? Any other hacks?

Complete radio silence since my last email. They've had my device for more than six months now. I would actually completely agree, if they had not set the expectation themselves in our communication that I was eligible for warranty service.

I checked the connectors and flat cables. They all seem fine. Both display connectors & flat cable, and the keyboard connector & flat cable. I checked i2c bus 6, and I also do not have the keyboard present ("--" on row 0x50, column 8). So that is why my keyboard is not working either...