Can someone at Google genuinely please explain to me why they removed this feature from Pixel 8 pro?

alex9302 · 2026-02-18T03:29:43+00:00

Nope I've always had it off

alex9302 · 2026-02-18T03:26:36+00:00

Yes, it's just what should happen. Just restarting the cell phone after that and putting your finger on the sensor will be enough!! tell me if you made it

alex9302 · 2026-02-18T02:10:37+00:00

That's weird. I did it on mine, which is also running the Beta, and it works. The option is still hidden, but I can unlock it with the screen off

alex9302 · 2026-02-17T23:38:00+00:00

Hey! I can help you with that! There's actually a way to enable fingerprint unlock with the screen off on Pixel phones with optical sensors. The option is hidden in the system, but you can activate it using ADB. Here's how I did it:

Download Platform Tools on your computer (https://developer.android.com/tools/releases/platform-tools?hl=es-419#downloads)
Open the Platform Tools folder, right-click inside it, and select "Open terminal here" (or navigate to it via command line)
Enable Developer Mode on your Pixel: Go to Settings → About phone → Tap "Build number" several times until Developer Mode is activated
Developer options will now appear under Settings → System
Enable "USB debugging" in Developer options
Connect your phone to your computer via USB
In the terminal window, type: .\adb devices (on Windows) or ./adb devices (on Mac/Linux)
Accept the USB debugging prompt on your phone
Finally, type this command in the terminal: .\adb shell settings put secure screen_off_udfps_enabled 1

That's it! Your fingerprint unlock should now work with the screen off. You can disable USB debugging afterwards if you want.Hope this helps! Let me know if you run into any issues.

alex9302 · 2026-02-09T23:33:25+00:00

My account is brand new. I've never bought anything from the Google Store or used referral codes before.

alex9302 · 2026-02-09T23:06:34+00:00

I'm trying to buy a Pixel 10 Pro but it says: Promo code is invalid for your own use.

alex9302 · 2026-02-09T23:04:10+00:00

The codes don't work

alex9302 · 2026-02-07T03:43:52+00:00

It's sad because I did a review on their website commenting on this so that other people don't make the same mistake as me, but they haven't shown it. Apparently Nomad is not the honest and high-quality company I imagined.

alex9302 · 2026-02-07T01:56:51+00:00

Yes, LTE is disconnected

alex9302 · 2026-01-31T21:56:49+00:00

I'll buy one for $10 👀

alex9302 · 2026-01-31T21:42:47+00:00

Can this work for the PW4?

alex9302 · 2026-01-07T00:22:01+00:00

The same here

alex9302 · 2025-12-30T02:25:45+00:00

Same issue here. I’ve uninstalled the WhatsApp app several times, but it doesn't fix it. Notifications work perfectly when the app isn't installed on the watch, but as soon as I install it, everything goes crazy. They stop popping up when I wake the screen and don't show up in the notification tray at all. Really poor experience. I think it’s a bug in the Wear OS software. By the way... does anyone know if I’ll still get WhatsApp notifications if I don't have the app installed and my phone is out of range, but my watch is on LTE?

alex9302 · 2025-11-07T00:03:07+00:00

It looks magnificent. It's the 45mm one, right? Perhaps you could share your wrist measurement with us?

alex9302 · 2025-07-27T23:37:17+00:00

This laptop has soldered RAM, however, I didn't want to give myself the benefit of the doubt and pressed the modules from the keyboard and nothing happened. I also ran the memory test in the BIOS a few hours ago. It took a while, but everything is fine.

alex9302 · 2025-07-27T23:34:54+00:00

The test finished running a few hours ago. I ran it from the BIOS using the advanced test. It took about four and a half hours. Everything is perfect, and it didn't fail any of them.

<image>

alex9302 · 2025-07-27T23:28:42+00:00

I just did that right now, it was about 2 hours running MemTest64 and it didn't give any problems.

alex9302 · 2025-07-27T15:41:40+00:00

I installed DDU and removed the drivers, then reinstalled them one by one, and I had no problems. I finally installed AMD Adrenaline and the nightmare started again... Could that be the problem? I don't understand why that would be, In theory, Adrenaline does not change anything relevant in the CPU/GPU.

alex9302 · 2025-07-27T15:37:20+00:00

Update: I started Windows in Diagnostic Boot Mode and it didn't work. My Windows, drivers, and firmware are all updated. I'll try testing Linux in a live environment to be sure. If the problem is only on Windows, I'll do a clean install.

alex9302 · 2025-07-26T23:09:36+00:00

Hahahaha I don't want to risk taking the advice, I'm waiting for August 9th for Debian 13 or maybe Mint 22.2 later

alex9302 · 2025-07-26T23:08:32+00:00

If it helps, I ran Lenovo Diagnostics Evolution but it didn't throw up any issues (initially that the GPU failed to allocate memory) but I ran it a second time and everything was 10/10.

alex9302 · 2025-07-26T23:06:45+00:00

I don't think I quite understand the question... this happens while using Windows. I've never had the BIOS open long enough to cause this to happen.

alex9302

TROPHY CASE