adam.c.r.roman

Interesting. Good idea, I wish I was even slightly competent with Linux and changing those files. I'm just a lowly old-school microcontroller and DSP assembly language guy. Anyone else want to look into this? And are you AT&T people still going strong?

I believe so, unless someone changes the volume levels in the drivers. The chips that handle the audio (the Qualcomm chip and whatever CODEC is being used for the speakers, mic, and headphone jack) usually have at least 256 levels of volume, usually in several stages, so it's probably a matter of the software being tailored to adapt to the gain of what's coming out of the Qualcomm chip. It seems T-Mobile's audio is extremely compressed and then expanded to keep volume very consistent and loud to use as little data as possible. My educated guess, anyway. At any rate, these adjustments need

Sorry, haven't seen this thread in a while. (I don't get alerts for some reason.) I'm delighted that my ranting about debouncing and key-scan priority has seemingly made some significant difference. In a proper design, keyboard debounccing (see that?) wouldn't be the responsibility of the host processor, but rather be the sole responsibility of a microcontroller in charge of the keyboard. Just look into the original Intel 8048 microcontroller in Every IBM PC keyboard in the 80's. Oh, and a similar dedicated microcontroller in Every Other Computer Keyboard Since! There's a reason for this

Regarding my calls now being too loud on the lowest volume setting, that's something I will try, thank you, but it won't work past December whatever on T-Mobile, right? Maybe off-topic again - I know it's a huge redesign, but I really wish there was a 5G Pro2 coming out instead of a Pro1 X. Doesn't make much sense to me - are they going to get enough revenue from the Pro1 X to keep going and accomplish that? I mean, it's like 4-year-old tech now.

VaZso, thanks very much for that info! Very interesting. I'm a low-level hardware / software guy - microcontrollers and such - and I appreciate the education in an area I'm not too familiar with. I just know I was with Sprint (now T-Mobile, didn't even know that) for 20 years, and never had reception problems until AT&T with this phone. I wasn't sure if the Pro1's design was an issue, but I'm getting greater signal strength than ever with T-Mobile.

I'm an hour Southwest of Chicago in a very heavily-populated suburb, so there was just no good reason to have such horrible reception. I can't believe you actually heard back from tech support! This is also off topic, but I've been trying to get a new FPC cable since April 8th, paid over $40 for it, and somehow it's gotten lost in the mail Twice. The second time, they provided a tracking number, and Royal Mail says they have no idea what happened to it, and that f(x)tec should file a claim. Forwarded proof that I still didn't get my cable (which Will break eventually), and no response.

Well, my Pro1 was working all day today on AT&T... until I effortlessly switched over to T-Mobile. Using this on AT&T for 2 years has been a nightmare, signal-wise. I experienced constant dropouts and no data in certain buildings, and even in my home. At times, I had to go outside on my front porch to have an intelligible conversation with someone! For the past 4 hours on T-Mobile, data and call quality has been outstanding, especially the calls' sound quality, in general. Some calls are way too loud on the lowest volume setting. (Can this be adjusted?) But I'm worried abou

I think most major US carriers just don't care about this 0.01% of their customers to include any training on getting off-brand devices working with their networks. It just doesn't affect their net revenue. But, per KingOfTerrible's comments, I saw that T-Mobile does have a rather promising BYOD (Bring Your Own Device) program, where they seem willing to accept any phone that is unlocked and compatible with their network, regardless of brand, so I have new hope with this possibility. Please, everybody, share your experiences with getting the Pro1's working with US carriers. Thanks!

Probably don't have to say this, but please let us know if your Pro1 quits - is it beginning or end of 2/22? -- not sure. I wasn't able to get them to not deactivate my Pro1 on that day and see what happens, so the absolutely awful "Calypso" replacement phone they sent me should be automatically activated. Didn't know you could deactivate the 3G band, thanks for that info, as well as the T-mobile option. I haven't seen mention of this before. Much thanks, and I hope you keep us updated on this thread. Even though this phone has the keyboard repeating key problem I've babbled about, I'

I'm not sure what to do about this either. AT&T support has been down the last 2 days, so I can't even tell them not to deactivate the Pro1 and activate the replacement they sent me just to see what happens on 2/22. I'm willing to do whatever it takes to keep this thing working. Are we sure the Pro1 X has the same 3G/4G chipset and it won't work either? I'm not sure about all the different bands that are listed.

I have found that a reboot always fixes the severe lags, where it outputs like 1 character a secondd, but nothing helps those repeated keys like you just saw, because... I'll say it again... there's something in the Software where it's not sampling and debouncing the keyboard fast enough, regardless of moderate physical degradation to the keyboard. The lag issue is confusing, however. I have to wonder if there's a keylog being created every time the device reboots, and it gets to be so huge, that writing keystrokes to the log file takes priority to them actually being output to the app

Anyone else getting repeated keys AND keys out of order? I can type something like APPLE and it may come out APPELL. Most certainly software, and not just the debouncing issue I described that can repeat keys. And I also have experienced severe lagg (that extra "g" was a repeated key for real) where the keyboard input is several seconds behind. It seems to happen a lot faster when I Copy and Paste web text. I have to wonder if this is due to a keylog file that we don't know about. Because, unlike the repeat issue, that problem is always resolved on a reboot (so maybe a new log file i

I posted on this thread on July 13th that I'd been waiting 2 1/2 months for the FPC flex cable. The next day, on July 14th, I got this response: "Apologies for the delays in getting back to you. This has been shipped to you a while back, but given your response we're assuming it hasn't arrived yet. We will be re-posting this with a tracked service this week, and it will arrive at your door most likely by the end of next week. We're posting it to the address below, and if there's any change to it, please reply." The address was correct, yet it still has not arrived, over 5 weeks late

It is partly a hardware issue that should be flawlessly corrected with proper software, as I've described. My repeated key issues started about 9 months ago. Same thing with my Photon Q. I'm surprised the backspace key didn't break off and fall right out of the phone. That's very interesting that it's happening on LineageOS as well. But I'd have to guess that the way keyboard input is processed on LineageOS was just "borrowed" from Android. I'm an old-school microcontroller coder, and I have an example of this happening in early 80's tech. I have an old Radio Shack programmable

I wish you the best luck, but I suspect their fix will likely be either a new motherboard with nice, new, shiny, clean keys that don't produce enough noise to mess up (for a little while), or it will come back the same. The only proper fix is in the Android kernel, but since nobody cares about a phone with a physical keyboard anymore (except for us few enlightened souls), I'm really not sure it will ever happen. It's not a matter of rewriting the existing keyboard handling code, it's probably a restructuring problem, so the keyboard handling is a much higher priority, and ensuring processing

I ordered a replacement FPC cable on April 7th, paid for it on April 8th, and over 3 months later I still don't have it. On May 27th, they admitted they had no stock and it was delayed, but it was in transit and I should receive it in, at the most, a week and a half. That was 2 1/2 months ago. I contacted them again on June 27th, then again on July 9th. Still nothing. And I paid like $43 for a 5-inch flex cable. Anyone know how I can light a fire under their asses? I'm losing patience!!

This has been a maddening problem since my Photon Q, and I believe there are 2 issues happening, and although I'm a talented engineer, I'm not in a position to confirm my suspicions in the near future. I believe auvo.salmi is right, in that the keyboard is wearing out a bit over time. This causes noise or "bounces" in the keyboard input. In the best-case scenario of keyboard design and OS integration, there is a dedicated microcontroller reading the mechanical buttons which employs advanced debounce algorithms. In my microcontroller programming experience, I require about 60ms of no keypre

netman, thanks very much for explaining the Pro1 hardware and refreshing my memory on the limitations without diodes, that makes perfect sense. I remember designing the hardware and firmware for a small keyboard for an invention of mine that included 2 encoders on the matrix, and I did have to include diodes on the 4 encoder outputs so they didn't short out the keys when the knobs were in certain positions. And I think you're right about not being able to conquer that hardware limitation with a creative driver. That third key does indeed short everything out and obscure the source. I was

netman, really great work, and I do apologize for not being more well-informed. This makes complete sense in both respects... I probably didn't reboot after the 3/6 update and just got pissed off too quickly when it improved only slightly, and I just put it back in the box. (I do adore this hardware now, with several exceptions I may post elsewhere, but I was pretty thrown by the fact that the second slider since 2012 was seriously flawed, so I had little patience at the time). And yes, if the keyboard matrix and firmware isn't arranged properly for more than 2 key presses in hardwar

Thanks for the replies Peter and Slion, I wish I knew how the heck this got remedied without an update and the power off for 6+ weeks. Could I have forgotten to reboot and try again after the last update?! (I thought that was automatic.) Can't imagine that, but anything's possible. So glad I don't have to write keyboard code myself. Apologies, this Keyboard Mod backer is finally a fan after 2 1/2 years.

I admit, this is Very strange. That actually does work. When I performed that test 2 months ago, it certainly did not work at all after updating the software, so back in the box it went. Today when I took it back out, I immediately looked for a software update, and there were none, so back in the box it went again, because how could anything be different? That test actually works now, yet no software update was performed. How could that be???? But I have found a similar keyboard issue which is reminiscent of the previous issue, but with 2 keys held down, not one... Try holding A

elvissteinjr, I very much appreciate that info. But the latest update did not fix the keyboard issue as I described. Does anyone know if the source code for the keyboard microcontroller is available to be modified, and if so, where to find it, as I believe it is not reporting key events correctly to the OS, therefore no OS workarounds will make the Pro1 usable for serious typists. If it's not available, we'll have to beat it out of Liangchen so I can fix it, lol. Please, let's get this thing right!!!!

My Pro1 has been sitting in the box since I got it in January, hoping, praying that the horrible multi-key keyboard issue gets fixed. After about another 6 weeks, I took it out tonight, and there is still no software update that fixes it. I'm a virtuoso musician and lightning-fast typist that simply can't use this device as it is because it doesn't respond correctly if the last key doesn't get released before the next key is pressed, which is an absolutely unacceptable problem. Try this... Hold the letter A and then quickly press every other key and see if it got the next letter correctly. Th