david

I ran termux and ran the command termux-wake-lock. It asked permission to do its thing and I gave it permission. Didn't solve the problem. I'm guessing that if the screen goes off by itself, some of these things might work, but by me pressing the power button, it might be overriding these things. Alternately, it is just about the screen going off, or something related to that other than wakelocks.

I tried this app, telling it to hold the wakelock for an unlimited time, with display off, and then activated it. It still didn't work. https://play.google.com/store/apps/details?id=com.dambara.wakelocker&hl=en_US So maybe it is just the act of the screen going off, not anything to do with wakelocks or power saving modes.

I tried this app: https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en_US The app was made for an older version of android, so that might be why, but I couldn't get it to stop the behavior when I hit the power button to turn off the screen and turn it back on again. I found a newer version if this app and it behaved the same way.

They already are. They are hitting Y/H repeatedly until they remember that they have to hit another key first. Worst than that, in my case, I'm typing too fast and the multiple-simultaneous-keypresses bug is getting me and I'm having to go back and hit keys repeatedly, which is causing my brain to think that I need to hit the keys harder in the first place.

If you point me in the direction of a player and how to configure it to play when the screen is locked, I can test that. Are you suggesting that there is a way to hold a wakelock through some automation? Will that keep the phone from going to sleep?

Darn... Okay, so we just need a little robotic spider that sits under the screen and every time the screen is turned on, he runs out and taps the Sym key. 🙂 Or.....we can hypnotize every Pro1 owner so that they tap the Sym key every time when they first start using the keyboard.

UPDATE: The phone doesn't even have to enter any sort of deep sleep. If I turn off the display and turn it back on, that's enough to do it. So whereas others were reporting it happening when opening the keyboard, in my case, if the screen is on and I open the keyboard, I'm fine. *IF* the keys were fine the last time I closed the keyboard and *if* the screen hasn't gone off in the meantime. In other words, after the keys have been "woken up", everything is fine as long as the screen stays on, whether the phone is opened or closed multiple times. But if the phone is in the open state *

Ding ding ding!!! You just won the fake prize of the night! 🙂 My phone had been sitting a while, so I tested out your idea, and sure enough, the 7, Y, H were dead. N was not, but maybe I bumped something else before trying it. Oh, I just looked above, and maybe on the QWERTY, it is the B key on the bottom row that would be dead. I'll test that in in the morning, after my phone has been sleeping. But I think the mystery is solved. Things must need to be re-initialized after sleeping, so the register issue happens again, just like when the phone is powered on again. Maybe it

Adding to this, no matter how large a person's hands are, relative to the keyboard, the Pro1 *will* take longer to type the same content, when compared to a smaller keyboard, with all other things being equal. Has anyone ever played the game Whac-A-Mole in an arcade? The key to getting a better score on that is to minimize how far your hand/arm must travel. Keeping the hammer close to the machine and in the middle of the holes reduces the delay each time you need to pound one of the teasing critters. If you make that machine twice as wide, it will take longer to reach the mo

What I'm suggesting is that because the bug happens differently for some people, maybe there is more than one bug. It is possible that it is the same root bug and that other, external factors make it behave differently on different devices, however. In that case, fixing the root problem will fix both manifestations of it. In the meantime, there may be a way to get around it for those who have the issue every time they close and open the screen. But I get the point that maybe fxtec doesn't need any other info *if* the root cause is the same. Stupid question... Can this register be mod

Serial number 838 here. Although, we can't be certain all parts of later phones are truly later parts, but it certainly could be something to later phones somehow having a difference. It definitely is not a problem for me, since it only happens after reboots, and I didn't notice it before. I may have had one or two times where I thought the keyboard was dead, and it may have been this situation. Just looking for possible causes, since it might be something fxtec can't fix (if it is caused by something external). And if they can fix it, it would help if we can narrow down the variabl

For the people who have this happen every time the screen comes back on, are you on QWERTY or QWERTZ? I am on QWERTY, and as mentioned before, I only have the issue after powering on. There could me multiple variables involved. - QWERTY vs QWERTZ - Some system setting - Some 3rd party app (keyboard related or button mappers would seem to rank high on the suspicion list) - Some bad config hiding in the /data partition that a system reset could clear up Mine is QWERTY, with it set at Default, with no language picked. Been reset since the last OTA, at least twice,

Thanks for sharing those, @elvissteinjr. I could see myself using most of those. I'll have to put these on my to-do list of things to try.

Time to get out the ouija board app!

I prefer the size I have it at, but I am aware that would help. I am hoping fxtec or Google fix it in an update. I always try to leave computers at 100%, because some apps don't adjust to smaller or larger properly. In this case, the system isn't set right for the standard size. It shows just how much portrait mode has overtaken people's minds, since if the programmers and testers would have tested it in landscape, it would have been apparent immediately. I am pretty surprised that they don't have more automated tool to spot off-the-screen issues like that. Part of me fears that the

I also found out that out of X-Plore (long press, Open With), Solid Explorer, Total Commander and Explorer (the one @Hook uses), only Explorer opens Gallery Go in the way it would be opened if you opened Gallery Go and opened an image. The other 3 open it in some sort of restricted mode, where you can share, but the other editing functions aren't available. Some sort of read-only mode. That may be due to an android change that the others haven't caught up with yet, or they did it on purpose.

I haven't tried it yet, but I doubt it would work for me, because when in landscape, I have to touch the very edge to get to the android settings from the top screen pulldown. I could put a shortcut on a home page and go home first and hunt around for it, but that wouldn't be as convenient. I could map buttons to get to the settings, but I am trying to avoid too many artificial helpers while waiting to see what fxtec changes/fixes. I definitely have unintentional touches on the edges. Another reason a non-rounded, bezel screen would be preferable to me.

One other thing I just found out between the BSG port and the san1ty port. The BSG port somehow writes the EXIF data in a way that older EXIF viewer apps cannot read. They could read the EXIF data from the san1ty port. I had to install a newer EXIF app to be sure there was EXIF data in the BSG photos. Related to that, BSG records the Camera maker as Google. san1ty records it as Fxtec. They both record the Camera model as QX1000. Also, I forgot to mention in my other post, for anyone wanting to test out multiple GCam ports, you can't install more than one at a time, since they al

At least with the help of Titanium, it allowed me to do batch freezing and unfreezing with filters I set up, and I did half at a time, so it only took several attempts to find it. I refuse to call Windows applications "apps". They are programs or applications. 🙂 I have been meaning to organize my apps for a while now. I'll probably end up uninstalling some that I feel I will never use, but if there is a chance I might use it, I'll keep it around... "just in case", and then never remember that I have the app. 🙂

I have no idea why this app would cause this to fail, but this is the guilty app: https://llamalab.com/timesheet/ It used to be on the Play Store, but is no longer there. I uninstalled the version I had and reinstalled from their website and it caused the same issue. I don't think I ever actively used the app, so no big loss. But out of hundreds of apps, that is the last one I would expect to mess up the default image viewer. 🙂 UPDATE: I should mention, this app did not show up as having any running background services when I looked in developer options in Android. It also

I have determined that some other app is making this fail on my phone. I ran the Explorer app that you are using and told it to always use Gallery Pro, but it would still ask every time. I then used Titanium Backup to batch freeze all my apps (hundreds) except for Gallery Pro, Titantium and system apps. When I opened an image in Explorer, it went right into a viewer. I thought it was using an internal viewer at first, but then I went into Gallery Pro's system settings and cleared the defaults. It then asked which app to use when opening an image. So it is being set, but not using it due

My popup in Chrome lists "Add to Dictionary" and "Delete", but no guesses provided to pick from.

Weird. It worked properly in the Pixel 1 that I tested too. I will test some more tomorrow to see if I can get it working on the Pro1. Thanks for testing it.

The only thing I flashed a few times was the boot image (both a stock one and Magisk patched). I didn't flash any other partitions.

I somehow missed your details, @FlyingAntero, in that last post, and discovered them, the hard way, myself. LOL I decided to try out the Pocophone GCam ports, and the first one I found was the BSG port, with the night sight mode working correctly (not upside down in the viewfinder, and saved correctly too). It does show upside down for the panorama mode, but the saved panoramic photo is correctly oriented. For the san1ty port (F1), as noted, the night site mode is upside down in the viewfinder, but saves the results properly. It is just very difficult to use with it showing upside dow