If you want your phone to be permabricked by the manufacturer at some random point in the future, it’s hard to beat a Google Pixel.
He/Him. Formerly sgibson5150@kbin.social.
If you want your phone to be permabricked by the manufacturer at some random point in the future, it’s hard to beat a Google Pixel.
For me, I think it will. Love my moto.
Had mixed results on Samsung Z Flip 4. One had the inner screen die right after the warranty was up. Other is still going strong, though the permanent screen protector has separated at the hinge.
Did you read the article? Biden made many of Trump’s tarrifs permanent and Harris, while critical of Trump’s tarrifs, hasn’t put forth her own plan or disowned the Biden strategy.
Edit: Fucksake, Lemmy. It says this in the article. I said nothing positive or negative about either candidate or their positions on tarrifs. 😆
I ran into this today using ssh-copy-id on a new Debian box. Seems like that tool is biased toward copying a second key instead of a first. Either that or they assume most users use one key pair everywhere (and thus only have one loaded in their agent). I use one key pair per user per box. Excessive? 🤔
I’ve slept since the last time I set up sshd on a new install. Do you need to be able to authenticate with a password when you ssh-copy-id on a user without a public key?
Edit: Silly me. Yes, password is required.
Try harder Samsung. Google permabricked my Pixel 6. Twats.
When I installed Bazzite on my Asus laptop I got an Armory Crate application. There seems to be something similar for MSI laptops called MControlCenter, but don’t know anything about it. Hope this gets you going in the right direction.
I think it’s fine if Microsoft has their own nuclear power plant as long as every Microsoft corporate officer is required to live downwind of it. ✌🏻
The Blu Ray player is literally the only reason I use my PS5.
I mainly started using exFAT on flash drives (even on new ones) since it is interoperable between Windows, Linux, and Intel Mac. To be clear, I never don’t unmount the drive properly under normal conditions, but I remember reading around the time it was introduced that the Windows implementation guaranteed the buffers were flushed after every write (meaning no unwritten data remains when the activity indicator on the drive stops blinking) but now I can’t find any evidence that was ever the case. Wouldn’t be the first time I got bad info from the Internet. 🤷♂️
Random thoughts, no particular order
I think btrfs was the default the last time I installed Bazzite, but I don’t really know anything about it so I switched it to ext4. I understand the snapshot ability is nice with rolling release distros, though.
It’d been ages since I’d used FAT32 for anything until I made a Debian live USB when I was setting up my pi-hole on an old Core2Duo recently. It would only boot on FAT32 for reasons I probably once knew. 😆
NTFS was an improvement over the FATs what with the journaling, security, file streams, etc. I use it wherever I still use Windows (work).
Most of my general purpose USB flash drives use exFAT. I like not having to worry about eject/unmount.
I have already said “goodbye google” and “hello moto”, but long story short I had to factory reset my old Pixel 6 last night and ran smack dab into this:
https://9to5google.com/2024/07/01/pixel-6-reset-bricking-reports/
Right now I don’t even know how to turn the damn thing off. 😆
I just learned this myself. Motorola Mobility is owned by Lenovo.
Forgive the stupid question, but what does this mean, exactly? Does it mean Nvidia support on par with that for AMD? Will this enable a release of Bazzite that supports Steam Gaming Mode for Nvidia cards?
Did they find a way to cram even more stuff into the title bar?
Aye, looks like that’s where we be heading, maytee.
The trap closes.
Finally got updated 😄👍
Logout still hangs on both X and Wayland sessions (KDE) 😫👎
Thanks for asking instead of down voting me!
This is what bit me. Hadn’t used the handset for a while. Ran updates and did a factory reset. The only fix is mainboard replacement, which our pal Google won’t do for out of warranty devices despite it being their fuck up.
https://www.forbes.com/sites/jaymcgregor/2024/07/05/google-pixel-6-bug-brick-android-14-update--factory-reset/
Another, apparently unrelated issue:
https://www.tomsguide.com/phones/google-pixel-phones/android-15-feature-is-reportedly-bricking-pixel-6-phones-what-you-need-to-know