elvissteinjr

I've had 200+ days until just now. Didn't do nothing, but noticed it spontaneously rebooting, just sitting on the desk as usual. Rip.

For stock Magisk would be your only option I think. Otherwise you can just enable superuser access on Lineage and other ROMs, I think. There's a Pro1 Magisk guide here: Is it still 100% up to date? I don't know. Should still mostly work the same. I recommend checking the last posts in there too for more recent info. No idea if WhatsApp still works as I don't use it. Hiding root supposedly still works in Magisk, but Google has been moving forward towards making it impossible, so that may break at any point in time. Again, this is all just from memory, so things may not be 100% corr

I did have Substratum running when I was still running rooted with my first Pro1. Sure enough, it worked (it's mostly stock Android after all). The non-rooted variant? I don't think so. iirc that one only works up to Android 8 anyways. Other flavors of Android for the Pro1 probably give you the option for darker themes too, but you'll have to ask someone else about those.

Google Pay might be an option. Indiegogo seems to support it and Google Pay supports PayPal in some countries. Though that's just an idea of mine, haven't tried so no idea if that really works.

It's blue!

I can't speak for the solutions others have been using, but accidental presses have not been an issue for me using my Tasker profile for edge blocking. Not sure about the scroll bar issue. I never really use them, but after checking they're fine in my setup (small font, default element size), but problematic when element size is set to small. No case.

I wasn't able to fix it by unplugging the HDMI cable back in February either, but it's something I encountered yesterday. I'd assume fixing it like that is pretty unlikely, but it did happen at least once for me. I'm not sure what plays into this, so I'll call it random for now. I'm glad I didn't have to reboot since setting up ADB Wifi each time is a pain and I've been racking up some uptime too, even if it doesn't really matter.

Digging this up again with an old new discovery. Well, something I noticed back in February on my old unit but only now bugged me again which made me remember. If you've used HDMI before, it might've triggered some bug that causes periodical stutter every few seconds. It feels a bit like there are vsync misses, so depending on how apps are coded, they may slow down or skip frames or even run faster for a brief moment. Though it can also be just observed when scrolling menus if you pay attention. At first I thought only rebooting fixes it, but as the bug appears to be random, just plugging

I've had to enter some APN settings manually to get mobile data on my carrier to begin with. Saved fine on stock, so I'm not sure what you're doing wrong. Perhaps some cache issue?

v10.6.2b is listed to be compatible with poco x2 phones only. You need an APK for the f1. PocoSv10.4.apk works. I admit I actually had installed the F1v9.6_6.2.030 linked directly in the XDA post, but I went ahead and checked the newer builds. The one you downloaded doesn't install indeed, but the other one does. Can't say if that newer build is better or worse on the Pro1 yet, though.

Check if the download was complete, remove any other variant of GCam you may have on your device before installing. I just installed it yesterday without a hitch, so it should be working fine.

Having Tasker set the display timeout based on keyboard out state seems viable if nothing else comes along.

I've done nothing at all, but VoLTE, video and wifi calling are all enabled for me on stock. Mobilcom-Debitel, Germany. ...that's not helpful, is it?

Yeah, seems more in line with the date of the installed update, which is still a rough estimate to be fair. Did come with the October 28th 2019 update installed. It was a reserved unit for replacement cases as that's what support had told me. The mystery is as to why this seemingly old new stock was only available now and not 2 months ago when I paid the replacement order from the parcel insurance money. Something we'll probably never know.

It certainly is an older unit (260 days since last full charge). What it's been doing all the time is the real question (combined with the fact they could only now send it). Condition-wise it looked like it had never been touched before. Same goes for the accessories. Not that it bothers me. Just found it interesting.

Digging this out again, ignoring the last part of the thread title as you do. Today I've received the unit replacing my old #344 which had been lost in transit back in February: #89. Yeah that's not a digit missing or anything. Odd, if nothing else.

Received tracking number for #54XXX, QWERTZ, paid May 7th 2020. Yay!* *Feeling confused? Just poking fun. This was a replacement order for my phone that got lost in transit to Fx for a repair back in February. They've been nice enough to let me skip the queue on it, but it still took a while as you can see.

Now the issue is that a lot of the vendor stuff would probably be taken 1:1 from the current OS where possible, so the dodgy sound config for example would likely persist on a fancy new Android version. Can't even tell what I'd want a newer Android version for... maybe for the dark mode, but that's it.

I thought they got rid of the vignetting in an update very early on?

Ignoring the part how this shouldn't be happening in the first place, I suppose it should be possible to adb uninstall adups ("uninstalls" for the user account, easily reversible), keep an eye open in the community for update releases and only then get it back running to do the update. That's the best I can come up with if everything else fails and you still want stock.

On the bright side, as far as my understanding goes, the crackling can be patched without having Google to certify the new version (only needs to happen for security patch levels). So let's hope they can get to that now. Long overdue anyways, considering how often they put gaming into the spotlight on the Twitter account.

No. This a userdebug build (which shouldn't really be on shipped devices, but eh), so it's not certified by Google. But it seems like an official update just came out (finally!) that should fix this issue. I don't have a Pro1 myself right now, so I don't know if you can just update from this build to the new certified or have to reflash completely, but either way you should be able to get Safetynet working on this device with the right OS version.

I'm honestly not sure how you read his post and came to this conclusion. He pretty much said that secure boot is nothing to worry about since its status cannot be read from Android so it can't be a factor of locking you out. With that being said, can't you get in contact with the person who is responsible for corporate environment? Surely they'd know a bit better than just "yeah, because not locked". As far as states that could be read out from an app go, it's almost definitely Safetynet anyways. Recent devices were shipped with test OS builds for some reason as Eske mentioned, but I'd ac

Is that just disabling the maximum attempts or something different? Because that limit is part of Google's security requirements for fingerprint readers. Might not be able to make it to stock depending on how he did it.

Are you on stock? Keyboard Out certainly worked when I had my Pro1, but I've last seen it in February. Netman's keyboard driver on stock shouldn't have affected this at all, but I suppose the Lineage keyboard changes went pretty far and could possibly have broken that state, no idea.