wilhelmfitzpatrick

The person who maintains all the Lineage infrastructure is currently moving house, so that may be connected.

Here's what I wound up with that is working quite well: https://www.xmpow.com/collections/car-phone-mount/products/mpow-127-gravity-car-phone-mount-air-vent-phone-holder I like the gravity style holder for quick placement and removal. It seems to be available as vent mount or window suction cup mount as well. The spacing of the prongs at the bottom is wide enough that the USB port isn't covered, so I can easily plug it in for long drives.

Does the "register your device with Google" thing have any impact on SafetyNet, or is that something different? https://www.google.com/android/uncertified/?pli=1

I got the OTA this morning. Installed no problem, verified that the keyboard fix is good. Glad to see signs of life.

So my spontaneous reboot adventure has taken an interesting turn. From the time I first got the phone, it was rebooting at least once, and sometimes several times a day. But starting about a week ago, with no software changes to speak of, this behavior has suddenly stopped, and I've not had a reboot since. I can only assume that some dodgy trace on the motherboard "burned in" as a result of regular use. Finger crossed that the reboots don't come back.

@Slion yes, I've not been able to dig into this very far yet. I found: https://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_SEARCH ...but I'm not sure if that's the right thing either.

Would it be possible to remap a key (the FxTec key perhaps) as a SEARCH key that would work with the existing Android global shortcuts mechanism?

@david curious what speedtest app you are using?

USA, Washington, in Seattle

@tdm I was afraid that might be the answer. Thanks for confirming. @ddark-il here's hoping that it is something that can be fixed in software. I haven't engaged with support yet, because honestly right now, what can they do? Either it's software, in which case an OTA will be needed, or it is hardware, in which case a replacement device will be needed, and neither of those will be happening in the short term. I did grab some bug reports immediately after a few reboots, I haven't taken the time to look through them yet. I've not yet figured out a way to "induce" a failure. Usually

My Pro1 has habit of spontaneous reboots once or twice a day (running stock), and I'd like take a stab at figuring out what is going on, so I'm trying to figure out if I an get at any logs from prior to the crash. I've looked for stuff like /proc/last_kmsg and /sys/fs/pstore/console-ramoops running 'dmesg' just gives a permission error. Anyone know what the right method would be? Is it possible without root?

I'm an Action Launcher fan and I've continued using it. It does okay in landscape as far as icons are concerned, widgets get stretched an flattened which is not as nice (although in my case, mostly useable). I'm addicted to the left side app drawer, which works great in landscape. Oh, and I also like that typing on the physical keyboard while on the home screen invokes search.

One of the several DoxBox port, I would guess. This one seems to be the most maintained: https://play.google.com/store/apps/details?id=bruenor.magicbox.free

@sequestris http://www.skinomi.com/sk35070-note-10-phone-black-carbon-protector.html

Thank you @SirBaconIII, I'm also on T-Mobile, and the setting in the phone app was the missing piece I needed to get WiFi calling back. It was working on my two previous devices (Pixel 1 & Essential) and given that my office is practically a Faraday cage, I was sorely missing it.

I got a black carbon fiber skin from Skinomi for the Note 10, and the back piece is a pretty good fit. The camera and sensor holes are in the right place, although quite a bit larger than they need to be. I filled in some of the gap using other pieces from the kit. I also clipped the corners on the skin, much more than I needed to it turns out, but overall I'm pleased with the result. It looks nice, and it definitely makes the device much more "grippy" to hold.

I can add that holding down the function arrow while typing space does cause a space to be correctly entered into Sheets. Very odd bug.

I am using my as my daily driver, but there are definitely challenges, at least some of which I hope will get better over time: 1. curved screen leading to lots of spurious edge touches - this has turned into the biggest ongoing annoyance. I'm trying to learn different ways of holding the phone, but that also leads me to worries of dropping the phone as it is heavy and if I'm trying to avoid the edges I can't grip it as securely. 2. the fingerprint reader constantly misfiring as a handle the phone. Here's hoping for the "reader is off when the screen is off" feature request. 3.

Answering my own question. After much to-ing and fro-ing, including pairing the watch to another phone (a Pixel 3) and then resetting it, I finally convinced it to pair and set up with my Pro1. So no blame to the Pro1, just some form of WearOS voodoo.

Ah, I too had assumed that FxTec was leveraging the Android built-in global shortcut mechanism. Well, that's a bummer, but at least I can stop searching for now.

I've not been able to figure out how to type the accelerator shortcuts to launch apps via the physical keyboard. The settings panel for the physical keyboard shows the "Search" key (magnifying glass). I tried using the "FxTec" key, but that just takes me back to the launcher. Any hints?

Yes, I am a direct T-Mobile user.

Set up my Pro1 this evening on T-Mobile, in Seattle. Shortly after finishing setup, I got a text, presumably from T-Mobile that said: "We see your phone does not have correct settings to access the internet or send MMS. Settings will be sent to your handset." Subsequently, I'm getting LTE (I believe, it says 4G), mobile data works and I can send and receive MMS. So I suspect that T-Mobile has noticed the Pro1 on its network and is sending the correct network configuration to it when it joins, which is very nice.

Is anyone using their Pro1 with a WearOS watch? I'm so far unable to successfully set up my watch (previously synced to my Essential Phone). It seems to pair on the phone side, but the watch acts like the pairing request never completed. Going to try repairing the watch to another phone, but I'm curious if anyone has had success with this. I've already tripped over the aptX profile bug, hoping there aren't more BT issues with Pro1.

The Pro1 has landed in Seattle! Looks and feels great, waiting for my apps to finish reinstalling. It's been a long wait, here's hoping it'll be worth it...