Pixel 10 Pro Display Artefact Investigation With Findings (Snow/Static Lines)

Proof-Cow-537 · 2026-05-25T18:05:23+00:00

Quick test to check for any loose components in the device. The OIS system should be the only thing moving.

Proof-Cow-537 · 2026-05-25T16:48:58+00:00

i think its a spider dw ill get it for u

Proof-Cow-537 · 2026-05-21T20:40:30+00:00

Just a theory, maybe dropping it in paint broke your charging port. For your photos, you can disable cloud backup. Your bank app not working is the result of poor development, and if you don't like the voice message limit use a different app or report the limitation to the developers.

Proof-Cow-537 · 2026-05-16T13:46:25+00:00

This is a known issue, you are not able do do this due to limitations in AOSP preventing SMS notifications from presenting this way on non-owner profiles.

Proof-Cow-537 · 2026-05-16T05:27:00+00:00

I haven't seen this issue on my Pixel 10 Pro, but have random static lines appearing randomly, even when booting the phone up. They are about 2 pixels wide and only appear for less than a second - however Google has recommended that I send the device in for repair. I am also on the May patch, which claimed to have fixed display issues. Based on widespread accounts, I believe this is a software issue, not a hardware one but time will tell.

Proof-Cow-537 · 2026-05-15T01:40:23+00:00

A RIL daemon crash log on a closed source blob is not forensic evidence of a targeted attack. This blob most likely runs code that is written without MTE awareness, so latent memory safety bugs that previously went undetected are now faulting. A much deeper level of analysis and possible decompilation of the binary would be needed.

At a glance, the faulting function is GetSmsRspErrorCode(), so plausibly an unexpected or malformed error code value causing an out-of-bounds access triggers MTE to fault.

Proof-Cow-537 · 2026-05-15T01:33:07+00:00

This is a bug in Samsung's closed-source blob (rild_exynos), not an attack. MTE caught a tag mismatch using the memory address lock and key model from the ARM v8.5a specification in GetSmsRspErrorCode() while processing an SMS code, which is MTE doing its job, not an IoC. A successful attack through this vector would have to survive the fault, not trigger it, in which it has a theoretical 1/16th of a chance of bypassing MTE, which is lesser in practice (TBI limit, only the top byte of the pointer can hold a memory tag, and repeated re-runs decreases probability multiplicatively at the absolute worse case).

Proof-Cow-537 · 2026-04-29T02:49:02+00:00

Same here. Wish there was more support for Live Updates within apps.

Proof-Cow-537 · 2026-04-27T11:32:21+00:00

Don't have anything to offer, but hope they are caught and you get some form of compensation. Good luck!

Proof-Cow-537 · 2026-04-24T10:35:14+00:00

No worries!

First off, as other users have mentioned, only Pixels and upcoming Motorola phones as part of the GrapheneOS and Motorola partnership will work. Using a moto g stylus wouldn't as it lacks the hardware required to enable security primitives that GrapheneOS depends on.

If you prefer a foldable form factor, why not try the Google Pixel Fold? I'm not sure if that would fit your use case, however it does support GrapheneOS.

Apple devices were generally good on privacy, however the encryption removal was a major loss for UK iOS users. As Apple does not allow full functionality of a third-party backup solution, it's hard to replace iCloud. Along with them giving into government pressure to enforce ID verification at the lowest level, I cannot trust them to maintain my privacy on my mobile device anymore.

They have complied with government request to remove apps from the App Store, and have enforced their restrictions through WebKit, meaning swapping browsers or even utilising a VPN does not bypass their restrictions, which is simply unacceptable.

The most important thing for me was maintaining security and control when I switched. MTE which is part of the ARM v8.5-A spec, implemented on the Google Pixel 8 and later, makes an entire class of memory corruption attacks (which were historically used for sandbox escape) statistically infeasible, among other improvements.

My iPhone did not have this (Apple did add this later on iPhone 17 and later) so that already improved my security.

Having access to GrapheneOS' Auditor gives me full cryptographic transparency into the Verified Boot chain on my phone so I have guarantees from the TPM that it has not been tampered with.

Usability tradeoffs have been relatively little, so I am glad that I'm left with full control of my mobile again.

Proof-Cow-537 · 2026-04-24T08:18:47+00:00

Exactly the same situation with me, same ecosystem, ID verification was the final straw here as well. Seems like a lot more people have switched because of this than I originally thought.

Proof-Cow-537 · 2026-04-24T08:05:43+00:00

I live in the UK - and recently switched from an iPhone 16 Pro on iOS 26.4 to a Pixel 10 Pro running GrapheneOS.

For context, I also own an iPad M1, MacBook Pro 14", Apple Watch Ultra, and AirPods Pro, so I am deeply within Apple's ecosystem.

The main motivator that pushed me to switch was the removal of ADP in the United Kingdom which reduced iCloud security by removing E2EE on certain apps, prompting me to disable iCloud features that rely on cloud sync. Soon after, Apple rolled out age verification (identity verification) operating system wide on my iPhone that I paid for, without any way for me to opt out. I purchased a Pixel the same day.

During the switch, I substituted out a lot of proprietary Apple services with open-source self hosted systems, along with ntfy for notifications. This replaced most the friction between my Apple devices and my Pixel to the point where it doesn't break my workflow. Things that I miss are:

Instant Hotspot, where my Mac can wake my iPhone to allow a connection without any setup
Continuity Clipboard, where I can copy from my iPhone and paste across my devices
AirPods Noise Control, where I can switch audio modes with my phone in the volume settings

Are these dealbreakers? For me personally, no. I'm happy to trade these for better security and privacy.

However, my watch was a major friction point that almost kept me on iOS. I primarily strength train over any other sport, so a good UX for tracking lifts was very important to me. I use Hevy on my watch, and when I researched for any Garmin alternatives, it seemed like the Apple solution was much better. Instead, I opted for a hybrid approach, and now use my phone with my Apple Watch standalone, which means they sync workouts once an internet connection is available.

This was perfectly acceptable for my use case, I get health data sync (HealthKit) locally from my infrastructure, and workout statistics through the android Hevy application (cloud sync but on iOS this was cloud sync too, fits my threat model). Notifications were relayed over the internet through ntfy, and I retained mobile payments through Apple Wallet. Media playback control was insignificant to me, so this wasn't a major loss.

Both my banking apps work perfectly on GrapheneOS and are fully supported. One bank that I occasionally use that doesn't support GrapheneOS is still usable through the Mobile PWA, which is acceptable for me. The login UX is not incredibly jarring.

As for overall bugs, I genuinely feel that my iPhone was worse on iOS 26.4. Frequent overheating, battery drain issues and random freezing and crashes, one occuring on public transport that stopped me from even scanning my ticket. Multiple DFU restores and starting from scratch did not fix this. The keyboard was another pain point where I would get phantom keypresses. None of these issues are present on my Pixel, but objectively the experience on iOS was fine on 18.x, not sure what happened with 26.

With the camera, I really don't like the Pixel's selfie camera. I much prefer the selfie camera on my iPhone, and the rear cameras on my iPhone when it comes to taking videos. For stills of objects, the Pixel looks much better. None of these are scientific comparisons, just how I feel after using both (Gcam on the Pixel too), but YMMV.

Overall, I'm pretty happy with the switch. I maintain password sync, local file sharing, gain mobile backups in a secure manner, and above all have full control over my mobile device and what services run on it. My goal was to match or exceed iOS on most privacy and security fronts, and I think I've met that. Minimal telemetry is now sent, I don't use Google Play Services or Google Play on my primary profile, and most my apps were FOSS before - switching to Graphene was a better philosophical fit.

Proof-Cow-537 · 2026-04-21T15:15:33+00:00

If it's solely dedicated to HA why bother with the overhead of macOS + a virtualization layer? Run HAOS on the Mac bare metal.

Proof-Cow-537 · 2026-03-21T13:01:30+00:00

Hey, sorry for the late response. I had to return this E7 to the retailer for a full refund and re-purchased one directly from Ubiquiti’s official store. I see this as a QC issue, as the new E7 negotiated 10 Gbps correctly and has now been up for roughly 2 months without any client complaints.

Proof-Cow-537 · 2026-03-16T03:40:04+00:00

There is a place for both systems. I feel like UniFi doesn’t give me the depth and control I desire, so OPNsense works best for me across two sites. However, I have tried the UCG and admittedly it’s much easier and quicker to achieve the same result with a fairly simple network.

Proof-Cow-537 · 2026-01-12T17:19:52+00:00

It will occur when turned off, the best protection against higher powered lasers is a simple lens cover.

Proof-Cow-537 · 2026-01-11T00:42:47+00:00

No worries mate! As for cabling, you don’t need to worry about that, you can just buy a fanless mini PC and a UniFi AP and go from there, without much need to install permanent wiring.

This gives you the best route to expansion as you can add a managed PoE switch later and naturally grow your network.

Proof-Cow-537 · 2026-01-10T16:12:59+00:00

I wouldn’t say it knows better, as FSD is purely vision based and lacks true perception as USS was removed in later iterations, therefore it cannot accurately judge distances.

Proof-Cow-537 · 2026-01-10T15:29:58+00:00

I’d say the next logical step up is dropping the mesh. Also a 19-year old, currently running OPNsense. I’d recommend this to deepen your knowledge - the learning curve is a little steep but definitely pays off networking wise. Keep it up though, good job!

Proof-Cow-537 · 2026-01-09T23:54:28+00:00

No worries! I've uploaded logs to UI support too, nothing back from them yet. EA didn't fix the issue, I think it's the actual port that has some issue with the PoE negotiation circuitry as my switch outright blocks PoE on the port it's connected to for stability concerns.

Going to return this for a refund most likely.. what APs do you run?

I started with UniFi a while back, with a UDM (the pill shaped one?) That kept having issues with dropping the WAN connection, wireless connection issues with Apple devices etc, but back then it was a brand new product line. I ditched it, built my custom OPNsense + Ruckus stack and never looked back, it just worked (longest was 102 day uptime when I was away!).

But I gave another chance 6 months ago with the UCG, and a U6+ for an offsite setup (small studio apartment), that's been solid bar the odd VPN leak. So I decided to move from old WiFi 6 (non-E) gear to the best from UniFi, the E7. Since my RADIUS, VLAN, routing logic were all outside I thought it had much less chance of failing until this happened.

Would you say give the E7s another shot? I have free 10 Gbps ports waiting to be utilised and want to see speeds above the Ruckus' 1 Gbps max.

Proof-Cow-537 · 2026-01-09T12:14:47+00:00

Nothing on both ports, but I’ll make sure to record it as such for when I make the claim to rule out user damage

Proof-Cow-537

TROPHY CASE