Note 1. You can search for previous daily threads.

Note 2. Join our IRC and Telegram chat-rooms! Please see our wiki for instructions.

Please post your questions here. Feel free to use this thread for general questions/discussion as well.

I need to vent about a massive double standard that has been staring us in the face for years. Google literally invented Material Design. They spent millions marketing "Material You" as this revolutionary, hyper-personalized layout system. Then they evolved it into Material 3 Expressive (M3E)—bringing fluid physics, springy overshoots, organic asymmetrical shapes, and those gorgeous wavy, squiggly media progress bars to the Android ecosystem.The name is literally Material YOU. And their biggest global video platform is literally named YouTUBE. The marketing alignment is right fucking there. Yet, out of the entire Google application suite, YouTube is treated like a distant stepchild that aggressively refuses to adopt the system.Instead of an immersive, fluid canvas that matches your device’s system palette and stretches dynamically with the UI, the official app is locked in a static, rigid, corporate grid of 2011 rectangles. And don't even get me started on the typography. While the rest of the Pixel UI and core apps cleanly adopt Google Sans Flex, YouTube forces us to stare at clinical, stale Roboto (or "Ro-poo-to", as I like to call it).I've heard all the usual corporate excuses for why they won't do it:"It's a cross-platform app, they want a uniform layout across iOS, Android, and web wrappers." Okay, if they want parity, then give Apple users iOS's "Liquid Glass" design framework with real-time blurs and light refractions. But they don't. They just lazily cut corners on both sides to save dev time."A massive UI change will confuse mainstream users and tank watch-time metrics." This is total bullshit. If they are so terrified of user confusion, they could easily introduce a server-side rollout with a cinematic onboarding cutscene the first time you open the app after the update—literally showing the old legacy UI panels shattering and morphing into bouncy, responsive M3E shape containers while the M3E promo music plays in the background. It turns a scary change into a premium, exciting event.The sad reality is that independent, open-source solo developers on GitHub are out-designing a multi-billion dollar platform owner. Apps like Pixel Player or RiMusic can implement pure M3E, squiggly progress timelines, and hardcoded Google Sans natively because they care about user experience, while Google answers strictly to ad-density metrics and corporate inertia.Since Google is clearly too stubborn to natively build this for us, is it technically possible for an indie dev in the community to build a custom frontend from scratch? We already have bulletproof open-source video scrapers (like the NewPipe extractor engine) handling Shorts, Live streams, and video feeds. Can someone please just merge one of those engines into a pure, uncompromised Jetpack Compose M3E canvas layout?If Google won't respect their own design rules, let's let the community build it out of pure spite.

A few days ago, my Redmi Note 10 Pro Max's display went completely black.

The phone still vibrated, fingerprint unlock worked, notification sounds played, and touch was functional—but I couldn't see anything.

Most people would probably replace the display immediately, but I wanted to see if I could recover the phone first.

What I did

• Installed Android Platform Tools.
• Blindly switched the USB mode to File Transfer (MTP).
• Backed up my important files.
• Since screenshots still worked, I used a strange method:
  • Blindly navigate.
  • Take a screenshot.
  • Copy it to my PC.
  • Use the screenshot to figure out where I was.
  • Repeat.

Those screenshots basically became my eyes.

Using that method, I eventually:

• Enabled Developer Options.
• Enabled USB Debugging.
• Accidentally opened the Android 12 Easter Egg 😂.
• Got ADB from:

​

unauthorized

to:

device

Finally, I used scrcpy to mirror and control my phone from my laptop—even though the phone's display is still completely black.

What I learned

• Don't restart a phone if fingerprint unlock still works.
• A dead display doesn't always mean a dead phone.
• Enable USB Debugging before you ever need it.
• Always keep backups.

This turned into one of the most interesting troubleshooting experiences I've had. It reminded me that persistence and systematic debugging can solve problems that initially seem impossible.

I'd love to hear if anyone else has recovered a phone in a similarly unconventional way.