I get moving from reddit but just leave your comments up, this just made me have to do guesswork based on OP's reply.

Warning! This may be collecting data for advertising. From the Privacy Policy:

We may use personal information to tailor and provide you with content and advertisements. We may provide you with these materials as permitted by applicable law.

Some of the ways we may market to you include email campaigns, custom audiences advertising, and “personalized advertising” or “targeted advertising,” including through cross-device tracking.

If you have any questions about our marketing practices or if you would like to opt out of the use of your personal information for marketing purposes, you may contact us at any time as set forth in "Contact Us" below.

Using latest fedora 41 with Plasma Mobile, I can't get Bluetooth to work. Nothing shows up running bluetoothctl list. It's an intel wireless 7265, which shows up as a network controller under lspci, but the bluetooth part doesnt. hciconfig returns nothing.

Steps I've taken:

sudo modprobe bluetooth

sudo dnf install bluez bluez-utils

sudo systemctl start bluetooth

I'm having deja vu where I followed all these steps before, but somehow I'm stuck here. Thank you for any help.

I've got an x86 tablet, and I don't want to run Windows or Android, so I have always been left with the option of Linux with GNOME. GNOME is a solid DE, but despite the design language, it is nowhere near ready for touchscreens. Depending on the distro, it was either severely outdated or just generally buggy, particularly with the onscreen keyboard. This lead my to completely abandon my tablet for a while, but today I had an arbitrary though that I should try out KDE Plasma Mobile. Low and behold, it was exactly what I needed for my tablet.

I expected it to be a bit buggy, because I had tried out KDE Bigscreen and this seemed like the mobile equivalent of bigscreen, a fork that is half-baked and still has lots of work to do before it's worth daily driving. Imagine my shock when I booted the Fedora liveUSB and everything felt incredibly fluent and polished. I knew about 15 seconds in that I was switching. The navigation feels like an Android tablet, which I see as a positive, and the keyboard is just so much larger and more responsive. The GNOME default OSK is hardly usable because it's letters are so small, so this was a relief being able to type with no need for checking that I'm writing correctly every few characters. The next thing I noted is how polished it feels even for large screens(I have a 12 inch tablet). The gestures work on the whole screen, and this makes it feel effortless to navigate around. The final thing I want to touch on before I stop glazing is the really good performance. I have a very old tablet, about 10 years old, and the performance felt like it was brand new.

Thanks for reading my glazing exhortation, and if you have a tablet, I couldn't recommend Plasma Mobile more.

P.S. does anyone know where KDE connect is?

I've been dealing with this bizarre issue on my Garmin Oregon 450 GPS, and I need help diagnosing and fixing them. For some reason, I can't catch a break with these undocumented unsolved mysteries. Here's the situation:

(Original)Stuck in USB Mode:

When I turned on the GPS, it shows the USB icon as if it's plugged into a computer for file transfer, even though it isn't. If I plug in a USB, it works for file transfer. The issue disappears when I cover the pins from the back case (with the USB port) to the main board with electrical tape. When I do this, the device works perfectly fine, but I need a more permanent solution without relying on tape(outside, if I want to load maps I will need to disassemble my gps). This issue was sort of fixed by resoldering the CMOS battery(which garmin says is not needed - )

Power Button Problem:

After I desoldered and potentially re-soldered the CMOS battery, the GPS starts when I press the power button, but it doesn't boot fully. It powers on but does not complete the boot process. The thing with the CMOS battery is, I don't know if CMOS is the right term. The battery's voltage is lower than a standard cmos bat, at a shocking 0.24V. This causes me to think it's either completely cooked or it's a specialized battery. Either way, garmin's user manual(link) says it is not needed. See page 36, saying "Data Storage Life: Indefinite; no memory battery required"

Steps I've Taken:

I've desoldered and attempted to re-solder the CMOS battery (model 10N4). I've tried electrical tape on the USB pins, which temporarily solves the ghost USB issue completely even if I press the power button. I've put a little bit of isopropyl alcohol down the USB port(device was off, port was disconnected), it's still drying as I type. I have NOT disassembled any further than the secondary back plate with the battery slots. If someone thinks that will help, I will try to.

Can anyone contribute to this discussion? I have found radio silence online. Thank you very much.

Photos:

The main board of the GPS, with the pins covered up. Back view

The back plate - note the corrosion

The USB pins uncovered.

An overexposed mess showing my shoddy soldering job of the button cell.

Thank you for reading this, and for any ideas you may have.

I run very hardened firefox to prevent fingerprinting, and this often causes issues with websites(e.g. images not loading due to cross site request policies, sites not working due to webgl/webrtc disabled). Is there any way to only allow features on websites in my lan, or ones I select?

Thank you for the answers!

This is wild because I had never heard of this news anywhere. R.I.P. DivestOS, my favorite mobile OS. Anyone know of a project with a similiar goal of deblobbing android?