DieBruine

Yeah sorry. I read it and forgot about it 🙃. Well at least we know it can't be MtG. By the way, I have often killed all apps. A second or two later the ghosting began again. So I'm not quite sure it's a cpu hog.

I received one display yesterday and sent back my phone immediately. So unfortunately I myself cannot test LoS anymore. But as soon as there's a version available with the different driver, I will flash the two other phones and ask their owners to type a little bit more often 🙂 . For now I'm stuck with a Priv/cracked screen/65% battery capacity 😖. I have to say, I am curious now if there is a OpenGapps user with keyboard ghosting issues... 🙄

I went back to stock and have zero ghosting/hiccups. Tdm will compile a LoS with stock keyboard driver to troubleshoot. I type a lot, don't like calling people 😌. Anyway, two Pro1 users on stock without keyboard issues. Two LoS users who experience nuisances... So yeah, it's definetily something in LoS. By the way, users with ghosting and other nuisances, do you flash MtG or OG? I have only tried MtG.

Funny, the small width of the Priv is wat forced me to ditch that phone. That and the unlockable bootloader/lack of OS-upgrade. If I recall correctly I have owned all Qtek/HTC/Motorola landscape keyboard phones. Priv was my first portrait. Apart from the width I was very happy with it. My daughter used one until last Saturday. She seems very happy with her Pro1, as am I. Do not understimate the difference between landscape en portrait width. You say you don't need the upgrade. But if my reason to buy a new phone was based on improved performance, and I could get decent money for my curren

Yeah, this is also my own suggestion in the Bluetooth topic, but thanks anyway😅. For the record, my headset is also capable of HD Audio over AAC, not just aptX HD. But during the pairing process, aptX HD is always selected. LoS does not contain the aptX HD licenses and therefore does not try to pair using aptX HD. The result is HD audio over AAC. Which produces noticeably higher quality audio than the standard SBC AD2P.

Then all I can think of is Hangouts in the background. We all use Hangouts. This issue however is not limited to Hangouts. First time I noticed it was during my short lived euphotic moment shortly after installing LoS.

I have typed so much my thumbs hurt. Not one single hick up, lag nor pop-up. A shame really, LoS is beautiful, just not working for me. Guess I'll be flashing three others back to stock. I am curious though, isn't anyone else experiencing these mayor-pain-in-the-butt keyboard issues under LoS!? We are a family of four with totally different lifestyles and apps. Yet all four experience so many errors that typing under LoS is unbearable.

I tried every possible combination on and off, trust me 🙄. This has no effect on the pairing process.

No, that was related to not selecting APT-X HD as codec in use. My headphone can use both APT-X HD and AAC. But the Pro1 does not have the license for APT-X HD. Yet when pairing, APT-X HD is chosen as the codec during the handshake. No matter what I try, I cannot force the Pro1 to disable APT-X HD and use the AAC codec instead. LoS also does not contain the APT-X HD license, but at least LoS selects AAC for HD-audio. AAC is not power friendly, but a clear improvement over standard SBC in terms of audio quality and compression.

Smaller screen and spacing in combination with small font. First I change it to 540. Then the system changes it to somethin else, after that I set it to 581 and keep it there. I would like to use 620, but then the navigation buttons move from the right side to the bottom in landscape. If I type 581 the navigation buttons stay at the bottom. When I use 540 and then go to 581 I still notice the difference. I use 581 because that is what the system once chose and I like. so, if someone knows how I can use a higher value while retaining the navigation buttons on the right, please let me know.

That That doesn't affect the handshake process unfortunately. Tried all possible combinations already. Under LoS it does connect over AAC. So I'm guessing there should be a way to disable APT-X.

Has anyone found a way to disable APT-X HD? since it doesn't work, I would prefer it to be disabled. I own a BT headphone that can connect with either APT-X HD or AAC. It defaults to APT-X HD and therefore doesn't work. So disabling that which does not work anyway would seem logical and in my case at least enable AAC over AD2P.

Thanks, changed the settings. Strange they haven't fixed the rotation bug. And I wish they would implement the Bluetooth implementation from LoS.

I went back to stock yesterday. I haven't typed a lot, but so far no keyboard issues. It took over an hour to install al the system updates. My phone rebooted (crash) during the fourth update if I recall correctly. I didn't pay much attention, just kept on updating. I see that the rotation bug is still in effect. But what annoys me the most are the DPI-settings. I can't recall where you can adjust that. Was it in build.prop? I remember vaguely I had to edit that back when on Cyanogenmod. And if so, does anyone have the correct location and setting similar to the smallest screen settings

This will probably have to wait until Thursday. I have had this phone since January. This issue started right after flasing LoS. I checked the topic. Nonetheless I will flash back to stock. I assume FxTec also prefers it in that state when I send it back. Edit1: I couldn't wait, just went back to stock, now booting... Edit2: Wow, took mo over an hour to install all the updates 😕 Edit3: @tdm 24 hours later, not one issue with the keyboard! I can type all I want as fast as I can, no issues with input or the annoying character-pop-up. Flashed to stock, restored 109 apps and made sure a

I can assure you two others have the same issue. And I'm betting a third, but she hasn't received nor used her phone yet. And I am talking about brand new phones. I will flash stock sometime this week. Pretty sure I never had this issue on stock.

That log was a bad example, first thing after reboot. Afterwards the keyboard went haywire again, but I didn't have my laptop with me. I can already tell you it didn't help to switch to fast polling, just by this edit. While I'm typing this response, I have had three special characters, a couple of missed letters and one enter... keylog Edit: Could you change the boot.img to log a 1000 or even 100000 characters? This is another bad example. The first three sentences produced the errors. The last two had no errors. But those are the ones with the last 256 characters. I don't mind l

Sorry, still busy renovating my garage 🥴. Flashed the boot just this morning. Everything I type shows up double in de keylog. Some keys how up as question marks. This is what I typed: die overgang De moet ik nu dus gaan herstellen voordat ik de berging kan afmaken Ai, ben echt veel tegengekomen Log included.... In the second line, "De moet" it should state "Die moet". keylog

@Slion So still no word on your repairs huh? I am still waiting for a replacement screen. After I have received that one, I need to send my own phone back for investigation/repairs. Out of four phones delivered, mine has a non-working video-out. The fact that you still haven't heard from FxTec makes me shiverrrrrrrrr. Also, I'm not used to this waiting in vain game. My screen would be sent two weeks ago, should be here by now. Request for tracking info also not honored yet. So, long story short; 'glad' to see you're in the same boat. But very unhappy with my future. At least a month witho

I just wanted to point out that it doesn't matter what I try. It's always like this. My son for instance doens't even use the keyboard because of this bug. All phones in our household show this bug. Just tell me how I can heelp and I will.

I can reboot my phone, start Hangouts or Drive (sheets) or FireFox and 90% chance it's fucked up. I haven't tested it, but I'm pretty sure it is impossible to type for more than 5 minutes straight without this bug manifesting. EDIT: As soon as I open HNagouts and start typing. Shit hits the fan. Last 10 minutes I was editing a couple of sheets. A friend of mine sent me a Hangouts message. I switched apps and started typing, You coun't meout whIh d ty = You couldn't make out what I had typed,,,, AArgh. Edit2: Seriously I am going back to stock. This is absolutely ridiculo

My screen had issues. The sent me a new one. My son's Pro1 has some glue residue visible, they are sending me a new one and ask I send the glued screen back for investigation. My USB C video out does not work. So I'm sending my phone back as soon as the replacement screen for my son is in. My phone was delivered in January. I just assume this was a fluke model, which is why my screen broke down and USB out isn't working. Shit happens, warranty claims are being handled. That's all I can say about it. Stock software wasn't bad. Rotation issue annoyed the Hell out of me. LOS is grea

It's like live playback. First you record a message. Then you point the camera to the droid and it plays the video while pointing the camera. Only thing is, it flips the screen in live view.

Another one here with 180° issue. But, only in combination with Sphero BB8 in hologram mode 😅. Any word on the typing bug that eats characters or just inserts new ones? I'd rather have a working keyboard phone than a stuck landscape mode. When I send my phone back for warranty I personally won't be running lOS until the keyboard has been dealt with. Unfortunately I am not the onlye one in this house who feels that way. Edit: I have to say that does seem to have been reduced with the latest LOS nightly. Still shit.

I bought three Snakehive cases and completely forgot to order a pouch for myself 😩. Really annoying, because six months later I actually still want to try it. It's not even that expensive. I just hate the shipping costs 😅.