ToniCipriani

It's still kinda readable actually, if you shine a light at the right angle you see the number. Still useless and not really thought out.

It's definitely way weaker than my Priv. That's actually one thing that it does very well, together with the dedicated mute button, it's designed to work with teleconferences. In my corner home office I practically get no reception, initially phone calls didn't even go through, whereas my Priv has no issues in the same location.

This one seems to work well so far, albeit the physical button doesn't work, and the front camera is very grainy which is non-issue for me. I guess the FX needs its own port if the physical button were to be made functional.

Would be nice if they can formally open up a semi-public beta program for end-users to test updates, maybe provide OTA packages there. Just don't do it like BlackBerry who pretty much allows anyone who can fill a form in, at least vet the participants for technical background who can actually help with bugs and quality feedback. I'd gladly help, with my former full-time background as Software QA.

If only the Pro 1 had a proper desktop mode. I just plugged my phone into my work MacBook's dock and it looks ridiculously large...

Anyone working in SRE or DevOps? Full Linux terminal (Termux) with Azure CLI, K9s connected to an Azure Kubernetes Services cluster.

I'm going to assume the sticker in the back is not needed for warranty? The whole thing practically rubbed off from one week of use, it's just a blank silver sticker at this point. Not sure why this isn't in the About screen (it's allowed by the authorities, quite a few manufacturers allow that, and some info is already in the screen) or put the sticker under the slider. However I do notice the serial number on the sticker doesn't match the one in software.

Same issue here, with an Astell-Kern XB10. Not my adapter issue, it works fine with a laptop.

It doesn't if you open it using the camera button, locked or unlocked. Clearly stated on the spreadsheet the only workaround is to open it from the launcher.

Want to add on about the "launching camera with camera button" bug, not only the Snapdragon Camera doesn't show the preview, it just flat out doesn't work. If you tap any of the menus (e.g. 3 dot for selecting camera mode), it just quits to the home screen.

Any updates on which GCam port works best so far? The SnapDragon camera is horrendous to use.

Using mine on Koodo (Telus subsidiary), but so far my reception has been horrid. I can't make calls at all in my room where I can with my Priv. I don't have concrete proof, but it seems like my phone is locked out of its band 4 and 7 LTE and using only 2, 13, 17 based on my observations inside LTE Discovery. Without the primary bands it'll be poor. Which network mode are you using on yours?

Which defeats the purpose...

Actually I was referring to the fact that the lock screen alarm and the pulldown alarm has discrepancies.

I find one annoying thing is that by the time I pick up the phone, the fingerprint reader would've already got to "Too many attempts".

So regarding the known bug where audio playback is crackling, should I actually report this to the app developer (in this case Nintendo)? So far this seems to be the only app that I have the issue with. Or this is still on FXtec to fix?

OK thanks, I'll just keep an eye on it for now. Reliability is kinda important and if the phone reboots and locks itself like this I may have to go with another phone, since my job requires me to be on-call.

OK after a little digging in ADB, think I found the "culprit": Batch{22232bc num=1 start=111828095 end=111828095 flgs=0x3}: RTC_WAKEUP #0: Alarm{5f09730 type 0 when 1591875900000 net.dinglisch.android.taskerm} tag=*walarm*:net.dinglisch.android.tasker.ALARUM type=0 expectedWhenElapsed=+12h33m31s60ms expectedMaxWhenElapsed=+12h33m31s60ms whenElapsed=+12h33m31s205ms maxWhenElapsed=+12h33m31s205ms when=2020-06-11 07:45:00.000 window=0 repeatInterval=0 count=0 flags=0x3 Alarm clock: triggerTime=2020-06-11 07:45:00.000 showIntent=PendingIntent{4a12fa9

Yeah that seems accurate. The time on the "alarm" now changed to 7:45PM tomorrow, so I tried setting an alarm at 5:30AM tomorrow, and indeed it updated.

Got my phone yesterday and it updated all the way to March 2020. Still says Widevine L3 in DevCheck.

I can't figure out what this is. The time shown is also random. It's not my alarm, since I don't have one set right now, and that appears on the top left of the status bar with no time displayed if it is set. When it collapses, the stopwatch appears next to the Wi-Fi and Battery Status.

Any further background to this bug? I wasn't using the phone at all, a.k.a. I was sleeping.

Looking at how your update is named "userdebug 9", I think you got a unit with a pre-production flag enabled of some sort, so yours came shipped with an unreleased firmware. Maybe you can help test to see if the extensive list of bugs are fixed...

I just end up reverting to completely stock on the settings. Didn't know you were supposed to ignore that persistent "set up your physical keyboard" notification. Unrelated note, looks like I'm off to a bad start with this phone. This morning it was sitting at the boot screen to enter my PIN for decryption, i.e. it self rebooted. I'll see if it happens again if I can catch a debug report. It's a hard reboot as well, not like my Priv which only does a launcher reboot.

OK that fixed it. That "set up your physical keyboard" is really misleading. Looks like the shortcuts also started working as well.