ToniCipriani

So by means... they pushed me to August, guess I'm expecting them to push it further out again.

You shouldn't need to provide it. Canadian carriers have done away with CDMA so it's not like they need to whitelist your ESN, If they do ask via an online check, just enter 1111111111119 . I've jumped between carriers (Fido, Bell, Telus) and never really needed to provide it, just stick your SIM in. Also, I use mine on Telus, which shares a network with Bell. You'll be fine.

FWIW I type Chinese on mine all the time, just install another keyboard app to drive the hardware keyboard. I'm using Swiftkey which supports a bunch of languages.

They're telling me they are getting a batch in August... ¯\_(ツ)_/¯

https://www.xda-developers.com/android-12-beta-gsi/ So we're officially approaching 3 versions of Android, and a full year of security updates behind.

From the article Qualcomm released the fixes back in December 2020, but still up to OEMs to push it. Samsung patched it as part of their May updates. 100% on FxTec here now, or should I say that company FxTec hired to (not) handle updates.

They seem to be more targeting the rugged phone crowd. And it's still missing a slider even though it is a portrait form factor. Not a fan of losing screen estate just for the keyboard. Majority of phone apps are designed to work in portrait widescreen aspect.

https://www.bleepingcomputer.com/news/security/qualcomm-vulnerability-impacts-nearly-40-percent-of-all-mobile-phones/ I wonder if the 835 is affected and might finally push us past April 2020 updates...

At this point I've given up hope we will see anything beyond P. I saw a theory around here given the 1X is switching SoC, they won't push anything for us 835ers and focus just on that.

They'll probably check if you have any physical damages via photos, then send a replacement screen. That or you send it in for repair. On that note, it's been a week since I patched up the PCB, now mine hasn't gone crazy with the touches, just still that defective strip.

This always has been since day 1 of the Pro 1, the built-in ADUPS checks for updates whenever you switch wireless networks (mobile vs Wi-Fi), plug and unplug the charger, etc. Many cases will trigger a wireless update check.

First attempt in blue, second attempt on the green parts in an effort to improve it. Turns out no difference between the two. And as of today the phone is still working minus that strip.

If you see the video I posted earlier, I would agree with that assessment, but then again it doesn't explain why taping the PCB would improve it. It does somewhat make sense though, from the calculator test where that strip started working again, I was using a bit of pressure, so it could have pressed something back into connectivity.

But this doesn't seem to explain why me taping the black PCB under it improved the issue drastically. I'm day 2 with a 80% functional display. Knock on wood it still hasn't gone nuts.

Not really. But I'll need a bit more clarification before I can answer fully and correctly: when you mean frame, do you mean the bracket where the LCD/Digitizer is glued to, or do you mean that whole LCD/frame assembly to the slider assembly (i.e. the screwed on piece)? Display seems glued on tightly, I don't see , but the display assembly seems to creak a bit when mounted to the slider assembly.

FWIW... this problem makes Spotify SUPER annoying to use. Casually scrolling through a random play list, random song you tap on plays.

This actually explains why sliding your finger on the bottom it might trigger the problem. Now I'm curious if everyone is having the problem at the same exact location, which could indicate a recurring problem caused by a particular flaw in the design.

OK, I've edited the post after reuploading the images to Imgur. Seems like the forum has some problems when you're just copying/pasting an image.

So I did some tests about that "strip" of touches, this was what the touch pattern looked like: One thing I noticed is that when you tap on that strip, it activates both top and bottom of it. Same situation when you rotate the display: BUT, if you actually press or slide over the correct place, it starts working correctly: This image with the tap location, clearly shows when you tap in that "strip" of area, it registers two touches: So I'm still leaning on the theory that some flex in the display is causing this.

No, as in if I leave it hanging it works fine. Snap it to the frame, it works for a bit and it starts going crazy. That is until now I taped down the PCB.

The part I still find very odd is that, the screen works perfectly fine if I don't mount it to the phone chassis. I couldn't tell what is being affected when it's snapped to the frame.

Another update... so my last experiment failed, problem came right back after 24 hours. However, re-reading what @vvv was saying about the PCB flex, I tried adding a little tape to the hold the PCB down rather than padding the connectors. Seems like this one did the trick, it hasn't gone crazy for more than a day. One little symptom remain though, is that "strip" of display where it dances on when it goes crazy, isn't as sensitive anymore. More specifically, sometimes it misjudges a swipe as a tap, accidentally activating the item there. This does bring a lot of validity to say the proble

Latest experiment (courtesy @vvv): Adding more padding to the LCD connector. I noticed the foam where cutout for the LCD o on the chassis has a pretty deep marking (not my phone shown, just for location): (Source: https://gelraen.github.io/fxtec-pro1-teardown/) Folded up some duct tape, and padded that cutout. So far it's working, I was able to complete 2 Mario Kart races without losing control. Calculator test also passed. Will report back in a day, my last reseat lasted that long.

I'll try some more padding experiments. This seems to align with my very first experiment with reseating everything. So far I only tried padding and insulating the main flex cable connectors, I thought the gold grounding may be causing some issues.

Thing is, every single time I reseat the screen or even run the phone with the screen detached from the phone chassis, it's not happening. I really hope that's not in indication that replacing the panel will not solve the problem.