D1ggs

Thanks Erik.

Welp, after reflashing with the factory reset tool several times, the device is still soft bricked. I am sadly unable to boot the phone. Makes it to the bootloader and won't make it past it. For future reference people, DO NOT RELOCK YOUR BOOTLOADER IF YOU'RE RUNNING LINEAGEOS! If there's anyone smarter than me out there with tips I would appreciate it. Looks like i'm going to have to roll back to an older phone. @tdm do you have any suggestions for this sad soul?

Yeah I just flashed my device using the latest full image (October 2019) from the factory reset tool. Still no dice. Bootloader won't let me boot. I'm going to try once more with the original October flash image. But if it doesn't work, it seems I have ruined my phone for good.

Bumping this thread. I am not able to get the factory reset tool to see my device. Do I need a special cable in order for it to see it? I am in bootloader mode. Edit: I don't know why this isn't obvious, but to enter EDL mode from the bootloader you need to hold both the volume up, down, AND power button. The device will reset to the logo and then a black screen. The factory reset tool will be able to work then.

Hello everyone, I was playing around with fastboot commands and like an idiot I locked the bootloader on my phone. Previously it was unlocked. I tried running the unlock command and I'm getting an error that says I'm not allowed. Worse yet, I'm stuck in bootloader mode with no way to boot in the system. I can at least operate the boot loader, but I'm unable to flash stock back using the fastboot commands. What are my options?

Yeah I tried that and kept getting error 22 so I gave up and went back to Lineage.

Bumping this thread. Can TWRP be used to flash magisk on the latest version of stock? We're missing the latest boot.img to patch via magisk and unfortunately the lineage OS recovery doesn't play nicely with stock.

Ahhh! This is what I wasn't doing correctly. Have we figured out how to root the latest version of stock yet?

Waiting patiently for when stock has passed validation.... It's ridiculous that a phone like this hasn't been validated yet. Edit: Dumby me forgot to lock the bootloader /facepalm

Try BSG's gcam port. https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/ Night sight works very well. Panorama is jenky, but works if you just follow Google's markings. The shutter button sometimes works, but I haven't found a gcam port that does correctly use it.

Press the U key once and then hold the U key. A window will pop up. For some reason on fresh flashes it doesn't happen. After a while you'll notice it.

Well, I spoke too soon. You need to use SwiftKey in combination with the physical keyboard setting. And for some reason, it will forget and the long press accented character window will pop up again. Very annoying, not sure what's causing that.

So a gent on the github tracker pinged me and gave a suggestion to try a differenet keyboard layout. Sure enough, I switched it to the FinQwerty FxTec Pro1 US for physical US qwerty layout, the behavior has been fixed. Now, instead of long presses, I can hold down the "sym" key and get accented characters similar to how the option key works accenting characters on OSX. I expect this to break in an update since it the layouts don't operate as expected. I also don't get the repeating key issue anymore. YMMV, but worth a shot to see if it works.

So for @Zamasu and @Craig, I recently wiped my phone back to stock, learned I that the latest release isn't play certified/rootable, and went back to Lineage. The accented character long press isn't as prevelant at this time, however I wonder if extended use of Android causes the system to get a bit choppy. Anywho, I have disabled "fast polling" in the keyboard settings. Going to open a request on github to change the long press to using the right pointed arrow for accented characters.

Just updated my device to the latest stock firmware version 20200306. Yet my device is listed as not certified. Is the issue still present?

Glad to know i'm not the only one who is experiencing this. It drives me NUTS! At the very least, pressing the special yellow arrow or fxtec logo with the key in question should pop that up. I believe autocaps is set by the software keyboard. Can you try gboard and see if it stops autocorrecting?

This feature drives me nuts. For some reason, this menu pops up all of the time when I'm typing. I thought I've killed it in the keyboard settings menu but it still pops up. How do I turn this off?

Has anyone had a problem with Swift Type and the latest build where occasionally when you press two keys at once, the accented character window pops up? I'm having trouble recreating it, but it seems that switching to another software keyboard system and back seems to fix it. Driving me nuts and it's tempting me to switch to another keyboard. edit: Here's how to recreate it. This happens regardless of keyboard in use. To recreate the bug, in any text entry field (ex text message body). Type any character, and then press two keys simultaneously. The accented character window wi

Give it a few years gents. It seems the keyboardless dark ages we lived in has caused us to forget what makes a good keyboard. We'll have to crunch through a few before we get that perfection again. Pro 1 is close, but not quite there yet.

Kiwi browser, the only one outside of Firefox that supports extensions.

Try swift type. Typing this right now with correct grammatical add-ons and spelling to boot. I just wish it did emoticons like Gboard. Edit: SwiftKey, thanks for the correction Dave.

Is anyone having an issue with the speakerphone not working during calls? Pressing the speakerphone button during a call doesn't switch the speakerphone on. Edit: Disregard, wiping the phone fixed it.

Silly question, can I flash this update onto my phone without deleting my user data? I legit just installed v8 two days ago and don't want to go through the mess of reinstalling everything.

Make sure your APN is set correctly. Mine wasn't and that was the cause of my woes.

Tip, if you have Magisk installed and you keep getting errors on launch make sure Android didn't install it to your external SD card. It needs to be installed on internal storage or else it will crash!