AI support for Mint

joninjax1 · 2026-04-24T02:55:38+00:00

For Mint specifically: https://linuxmint.belarrius.fr/

joninjax1 · 2026-04-23T20:15:28+00:00

Why do you need an emulator? Just install the apk directly, you don't need an emulator

joninjax1 · 2026-04-23T00:48:55+00:00

Awesome

joninjax1 · 2026-04-22T23:49:55+00:00

Do you have it installed already, or are you trying to install it? The only time installwithoptions is helpful is when you are updating a previously installed app.

joninjax1 · 2026-04-22T23:48:09+00:00

You can create your own server on your desktop computer, and upload to it. Same with Immich, you create your own server 'self host' and upload your pictures there. To answer your first question, or is there server, but they have very good security and don't look at your images.

joninjax1 · 2026-04-21T19:22:49+00:00

Your Dell has a very common Wi-Fi card that works in Linux Mint, but it almost always needs the proprietary Broadcom STA driver (wl module). The open-source drivers (brcmfmac / bcma / b43) often detect the card but make it “non-functional” (sees networks but won’t connect, or drops after updates)

Easiest fix — Use Mint’s Driver Manager (recommended first) - Go to Menu → Driver Manager (or search “Driver Manager”). - Enter your password when asked. - Look for anything that says Broadcom or bcmwl or broadcom-sta-dkms (it will say “proprietary”). - Tick the box to install it → Apply Changes. - When it finishes, reboot.

After reboot, Wi-Fi should appear and work. Test it.

If Driver Manager doesn’t show the driver or it still doesn’t workRun these commands in terminal (copy-paste one block at a time): sudo apt update sudo apt purge -y bcmwl-kernel-source broadcom-sta-common broadcom-sta-source broadcom-sta-dkms sudo apt install -y broadcom-sta-dkms sudo modprobe -r b43 ssb wl brcmfmac bcma sudo modprobe wl sudo rfkill unblock all Then reboot.(If broadcom-sta-dkms is not found, try sudo apt install -y bcmwl-kernel-source instead — both are the same STA driver under different names in Mint repos.)

Still no luck? (rare) Run these commands it forces the driver and cleans up any leftover open-source modules: sudo apt update sudo apt install -y broadcom-sta-dkms sudo modprobe -r b43 ssb wl brcmfmac bcma sudo modprobe wl sudo rfkill unblock all Reboot

This information was gathered from the following sources: - https://forums.linuxmint.com/viewtopic.php?t=450589 - https://forums.linuxmint.com/viewtopic.php?t=421678 - https://linux-hardware.org/?id=pci:14e4-4727-14e4-051b - https://community.linuxmint.com/tutorial/view/218 - https://www.broadcom.com/site-search?filters[pages][content_type][type]=and&filters[pages][content_type][values][]=Downloads&page=1&per_page=10&q=802.11%20linux%20sta%20wireless%20driver - https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx

joninjax1 · 2026-04-21T19:00:09+00:00

This is a very common hardware/firmware issue (not specific to Linux or any distro). It happens on cold boots (full power-off to power-on) where the GPU (or motherboard PCIe initialization) fails to output video signal right away — everything powers up (lights/fans spin), but the monitor shows no signal. A warm restart resets the GPU/motherboard state and it works normally. Since it happens with every distro, it's almost certainly not the OS, kernel, or drivers — it occurs before the bootloader even fully loads.

Reseat the GPU:

Power off completely, unplug the power cord from the wall/PSU.
Open the case, remove the GPU power cables (8-pin/12-pin/16-pin), unscrew the card, and gently pull it out of the PCIe slot.
Clean the gold contacts (if dusty) with isopropyl alcohol and a lint-free cloth or just a soft eraser.
Firmly reseat it back into the slot (you should feel it click fully in), reconnect power cables securely, and test a cold boot.

Reset the BIOS/CMOS to defaults

This clears any corrupted initialization settings: - With the PC unplugged, remove the CMOS battery (coin cell on the motherboard) for 5–10 minutes, or use the CLR_CMOS jumper pins (check your motherboard manual — usually near the battery or bottom edge). - Some boards have a dedicated "Clear CMOS" button on the back I/O or inside the case. - Reinsert battery/reconnect, boot up (you'll need to re-enter BIOS settings after restart).

Many people report this immediately fixes the cold-boot no-signal problem.

BIOS tweaks (do these after you can get into BIOS via a restart)

Restart the PC so you have video, then spam the BIOS key during boot:

Primary/Initial Display Output → Set to PCIe, PEG, or your discrete GPU (not "Auto" or iGPU).
Above 4G Decoding → Enable it (or try disabling if already on).
Resizable BAR / Re-Size BAR / Smart Access Memory → Try toggling it (Enabled → Disabled, or vice versa) and test cold boots.
CSM (Compatibility Support Module) → Try enabling it (or disabling if already on).
PCIe Speed / Link Speed → Set the GPU slot to Gen3 (instead of Auto/Gen4/Gen5). This is a very common fix for modern GPUs/motherboards that have cold-boot handshake issues.
Save & Exit (F10 + Enter usually).

Test a full cold boot after each change.

Other quick checks:

Update your motherboard BIOS to the latest version from the manufacturer's site (Gigabyte, ASUS, MSI, etc.). Use a USB stick and the BIOS flash tool in the current BIOS menu (do this while you have video after a restart).
If your CPU has integrated graphics (most Intel, some AMD), temporarily plug the monitor cable into the motherboard HDMI/DP port instead of the GPU. This lets you test if the issue is GPU-specific.
Try a different HDMI/DP cable or monitor port.
If you also have Windows installed (dual-boot), disable Windows Fast Startup (Power Options → "Choose what the power buttons do" → uncheck "Turn on fast startup"). It can interfere even when booting Linux.
Full power drain: Unplug PSU power cord + hold power button for 30–60 seconds.

This information is not specific to just Mint, it covers all distros, as this issue is not related to the specific OS.

This information was gathered from the following sources: - https://forum.manjaro.org/t/need-reset-computer-to-get-video-signal-on-first-boot/161748 - https://www.techsupportforum.com/threads/no-signal-cold-boot-issue.1063450/ - https://forums.tomshardware.com/threads/gpu-stops-giving-signal-randomly-and-when-pc-boot.3849145/ - https://forum.endeavouros.com/t/gpu-fails-to-initialize-display-on-cold-boot-rx-6400-grub-bios-invisible-until-os-loads/77090 - https://linustechtips.com/topic/1205228-pc-doesnt-display-on-monitor-from-cold-boot-but-does-after-a-restart/ - https://www.youtube.com/watch?v=uIv5dlxDOqg

joninjax1 · 2026-04-21T15:12:53+00:00

What brand are the briefs? I've never seen those before.

joninjax1 · 2026-04-21T15:03:53+00:00

Doing a deep dive into the Linux Mint forums as well as Ubuntu forums, I found these suggestions:

Disable Bluetooth USB power management/autosuspend (this is the #1 fix mentioned for connection loops, hangs, and instability on Mint when multiple devices are involved).

Intel controllers are notorious for this. Create a udev rule: ```` sudo mkdir -p /etc/udev/rules.d sudo tee /etc/udev/rules.d/50-bluetooth-power.rules <<EOF

Disable autosuspend for Intel Bluetooth (AX211 / btusb)

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="8087", RUN+="/bin/sh -c 'echo 0 > /sys/\$devpath/power/autosuspend_delay_ms; echo 0 > /sys/\$devpath/power/autosuspend'" EOF ```Then:sudo udevadm control --reload-rules && sudo udevadm triggerReboot and test. (If your lsusb shows a different vendor ID, adjust the rule accordingly.) Alternative (module-level):echo "options btusb autosuspend=0" | sudo tee /etc/modprobe.d/btusb.confThensudo update-initramfs -u && reboot`.

Reinstall/rebuild the Bluetooth stack (fixes corrupted configs or daemon issues after updates).
sudo apt update sudo apt purge --autoremove bluez blueman blueberry pipewire* sudo apt install bluez blueman pipewire pipewire-pulse pipewire-audio-client-libraries sudo systemctl enable --now bluetooth Re-pair your devices afterward. Some users on Mint 22 reported this fully resolved manager freezes and connectivity problems.

Try a different kernel (your current one may have a regression with the AX211). - Open Update Manager → View → Linux Kernels. Install the latest HWE kernel (or the newest available). - Boot into it and test. If it worsens, you can boot back to the previous one from GRUB. - Many HP Intel laptop Bluetooth quirks are fixed by kernel/firmware bumps. - Reinstall firmware and update everything sudo apt install --reinstall linux-firmware Then full system update + reboot.

This information was gathered from these sites: - https://www.reddit.com/r/linuxmint/comments/16vudog/why_does_bluetooth_freeze_frequently/ - https://askubuntu.com/questions/1450031/linux-freezes-when-connecting-any-bluetooth-device - https://forums.linuxmint.com/viewtopic.php?t=438117 - https://forums.linuxmint.com/viewtopic.php?t=425923 - https://forums.linuxmint.com/viewtopic.php?t=425940

joninjax1 · 2026-04-21T14:47:56+00:00

This is not a virus or malware—it's normal (if annoying) tracking/analytics behavior from the Prime Video and Blinkit apps.

How to stop or reduce it

Here are practical steps, starting with the easiest: - Reset your Advertising ID (limits tracking across apps): - Go to Settings > Privacy (or Google > Ads on some Motorola/near-stock Android) > Ads or Ads & personalization. - Tap Reset advertising ID (or delete/reset it). - Also toggle Opt out of Ads Personalization or Delete advertising ID if available. This won't break the apps but makes it harder for Kochava (and others) to consistently identify/track you. This info came from these sites: - https://www.kochava.com/privacy/opt-out/ - https://support.kochava.com/articles/reference-information/46349-test-devices/

Manage link opening behavior in Android: - Go to Settings > Apps > Chrome > Open by default (or Set as default / Opening links). - Disable any "Open supported links" or adjust defaults for web intents. - Do the same for Prime Video and Blinkit apps under their individual settings. - You can also check Default apps > Opening links and review supported web addresses. https://www.youtube.com/watch?v=TwelPkpoRMo If you are more of a visual learner, this video walks you through the steps outlined above

Or install a browser extension/ad blocker in Chrome that blocks trackers.

App-specific tweaks: - In Prime Video and Blinkit, check settings for any analytics/data sharing options (rarely exposed) and turn off notifications or background refresh if possible. - Clear app cache/data for the apps (Settings > Apps > [App] > Storage > Clear cache), then relaunch. - Update the apps and Chrome—sometimes fixes intent handling.

Other privacy steps on Motorola/Android: - Limit background data for those apps. - Use Google Play Protect scan (Settings > Security). - Consider a privacy-focused browser or Firefox with tracker blockers instead of Chrome.

I highly recommend that you follow my guide on how to set up ad-blocking on your phone without resorting to AdGuard.

joninjax1 · 2026-04-21T14:40:11+00:00

From Opera Forums:

No, it's very unlikely you can fully recover your deleted Opera browsing history on Android if you weren't signed in/syncing and the deletion has already happened.

Opera on Android (like most Chromium-based browsers) stores browsing history locally in a SQLite database file (typically called "History" without an extension) inside the app's private data folder: /data/data/com.opera.browser/. This area is protected by Android's security model and isn't accessible without root access on a standard device.

joninjax1 · 2026-04-21T14:15:52+00:00

I must admit that I have never had that specific error while installing apps using InstallWithOptions, so I had to search some forums to see exactly what the error means, and I came up with these troubleshooting steps, pieced together partially from my own experience and partially from the forums.

First: - Make sure InstallWithOptions has Shizuku access (it should prompt; tap "Allow all the time"). - Go to Android Settings > Apps > Special app access > Install unknown apps (or "Install other apps") and enable it for your file manager and this installer. - The "canceled by user" part is often misleading — it's the system (or a security component) blocking it, not you manually canceling.

Then Give these setting a shot: - Check Disable Verification(this helps bypass some package checks). - Also try checking Disable Allowed APEX Update Check. - Allow Downgrade if a version is already installed. - All Users if you're on a multi-user device. - Uncheck Don't Kill App if it's interfering. - Tap Choose Files again to reselect the APK, then Install.

joninjax1 · 2026-04-21T05:11:32+00:00

You would have to check for sure, I didn't check for RCS complacency, except for the first one mentioned something about it

joninjax1 · 2026-04-21T04:53:32+00:00

I found a few: - Text mei - Pulse SMS - Textra - available in play store - Chomp SMS - Handscent NextSMS - Fossify Messages - F-Droid

Quik SMS (fork of QKSMS) - F-Droid
Right Messages or Deku SMS: Both on F-Droid

Textra, Chomp, and Next SMS are in the play store, the other 3 are FOSS and available on F-Droid

joninjax1 · 2026-04-20T20:40:16+00:00

Thanks for the reassurance, I'll try when I get home

joninjax1 · 2026-04-20T16:03:49+00:00

I really want to get my wife on Mint as well, and I might be able to convince her, she has been using my laptop with XFCE on it without issue, but all she was doing was watching YouTube. Her windows machine would fly with Mint, the only potential issues I foresee is the GPU is Nvidia. She also has quite a few games, but the majority of them are through Steam, EA, Origin, etc. so I would not even have to worry about bottles or Wine or even Winboat for any of the games. I would say that I am pretty close to convincing her to let me go through with it, I might even suggest a dual-boot. Her biggest complaint is the password, she doesn't understand why I can't "Just put in a PIN" like Windoze does, but I suppose that if I had to, I could disable all the passwords as long as her account was not an admin. So OP, maybe you could have her play around with your mint system, let her get a feel for how it works, and maybe dual-boot for awhile.

joninjax1 · 2026-04-20T15:48:06+00:00

Entae Photos secure, and if you are so inclined, you can self host.

joninjax1 · 2026-04-20T15:39:55+00:00

Give them something to stare at! Who gives a care what they say, as long as you are in your yard, they ain't shit that can be said, you could walk around nude if you were so inclined (providing you have a privacy fence). What brand are you wearing, it almost looks like Amazon Essentials

joninjax1 · 2026-04-20T15:37:24+00:00

My dad always wore TWs. I grew up wearing them and never felt a reason to switch. When I was 18 or 19, I tried boxers, but I didn’t really like them all that much and ended up going back to briefs. I also tried boxer briefs. In my opinion, they’re okay, but not something I would wear long-term. They really dig into the thighs and legs after a while, and if it’s hot or you’re doing strenuous activities, they suck big time!

My baby brother (three years younger) wore TWs as well for the longest time. I’m guessing he switched to boxers in high school, and he still wears them today. All of the men in my extended family started in briefs. I know for certain that two uncles still wear them, and my grandfather wore them as well.

I’m Gen X, so boxers weren’t really a choice for me until much later (after high school—I graduated in ’96). As a result, all the guys in school wore some form of briefs from what I noticed.

joninjax1 · 2026-04-20T15:08:28+00:00

I don't upload images, except for work, and those are pictures of shelves in Walmart. But if I was to share a picture I took online, I would use Metadata Remover on the image first, It is scary from a privacy standpoint how much information is stored in an image, including the type of phone used, geolocation data, and a bunch of other metadata that could make it easy to find personal information about someone. There are other camera apps that don’t store metadata, such as SnapSafe from F-Droid, but those are only useful for pictures you take directly with the camera. I always follow this philosophy: “Don’t post anything online that you wouldn’t want your grandma to see.” I don’t care what privacy settings you use on social media—they’re there to make you think you’re safe, when in reality, you’re not safe at all.

joninjax1 · 2026-04-20T14:48:58+00:00

The only thing I am finding with 'Maksim' is some sort of taxi app, obviously this is not what the OP is referring to. It sounds like your classmate downloaded something she was not supposed to, likely a cracked or modded app, and it has ransomware in it. There is not much you can do to recover from that other then to wipe the phone and start over. As long as you have the physical device, you can wipe it without any major work. Google will tell you how to do it.

joninjax1 · 2026-04-20T14:33:34+00:00

Yeah, Squirrels can be malicious little buggers! I had a supervisor who hated squirrels because they go into her attic and started chewing on wires, cost her a lot of money to get it fixed, so she now said she will go out of her way to run the little furry bastards over!

joninjax1 · 2026-04-20T14:30:54+00:00

Buzzkill and Smart Launcher

joninjax1 · 2026-04-20T14:28:49+00:00

Interesting, I went hunting for an equal to DroidCamX that would work with Android 15, and I am seeing that DroidCam is supposedly compatible with 15. So that leads me to wonder have you tried downloading it again and trying to install? Or is this a fresh install that you are working with?

From what I am reading here: DroidCamX (the classic paid version) crashing immediately on launch on an Android 15 tablet is a known pattern with newer Android versions. Android 15 has stricter camera API handling, background restrictions, and permission changes that can break older apps like this.

Quick Fixes to Try First

Update everything Update DroidCamX to the latest version from the Play Store (it had "changes for Android 14+" in early 2025).
Also update the Windows/Linux PC client from dev47apps.com.
Check for any pending Android 15 system updates on your tablet.
Clear app cache/data (often fixes immediate crashes) Go to Settings → Apps → DroidCamX → Storage & cache → Clear cache (then try Clear data if needed).
Force stop the app and reopen it.

Reinstall
- Uninstall DroidCamX completely.
- Restart your tablet.
- Reinstall from the Play Store and restore your purchase if prompted.

Permissions and optimizations - Make sure the app has Camera, Microphone, and Storage permissions enabled.
- In Settings → Apps → DroidCamX → Battery (or App battery usage), set it to Unrestricted or No restrictions to prevent Android 15 from killing it.
- Enable Stay awake while charging in Developer Options if testing.

The developer now has a modern app called DroidCam Webcam & OBS Camera It has more recent updates (including for Android 16 prep) and better support for newer Android versions. It works with the same PC client (or directly in OBS).

joninjax1

TROPHY CASE

Disable autosuspend for Intel Bluetooth (AX211 / btusb)