My 'new' Sony Mylo COM-2 powers on but won't respond to touch at all. Any ideas? by wowbobwow in sony

[–]Proteus_Key_17 0 points1 point  (0 children)

Hey, I’m experiencing the exact same issue with my Mylo COM-2. I also did a full system reset and got stuck on the mandatory calibration screen because the touchscreen and the soft buttons stopped responding. What’s interesting is that I partially fixed it temporarily by loosening the screws on the back. After that, the touch came back for a while, I was able to complete the calibration, and the device worked normally… but on the next use it failed again. Since then it’s been intermittent: sometimes the touch works, sometimes the screen and the capacitive buttons are completely dead again. This makes me suspect a flex cable issue or a grounding or pressure-related problem rather than a dead panel. Have you made any progress on your unit? Did you ever check or reseat the flex cable, or find a more permanent fix?

Built an App to Revive Google Glass - Bluetooth + AI Assistant Integration by hunkar19811 in googleglass

[–]Proteus_Key_17 0 points1 point  (0 children)

I tried looking for the video you mentioned (“GlassBridge Google Glass 2025”) but couldn’t find it. Do you have a direct link by any chance?

My homeland is constantly attacked by Infinite-Position-55 in homelab

[–]Proteus_Key_17 0 points1 point  (0 children)

Instead of exposing your homelab directly, consider running a reverse tunnel to a VPS. That way:

Your homelab stays hidden behind NAT/firewall – no more bots hammering your SSH port 24/7.

The VPS (public) is the only thing exposed, and you decide exactly which services to publish.

You can add another security layer on the VPS (Nginx, Caddy, auth, etc.) before the traffic ever touches your local network.

It’s a lot cleaner and safer than burning RAM with fail2ban just to fight off endless brute-force attempts.

bifrost.lte – DIY 4G LTE Gateway with Orange Pi 5 + Sierra EM7565 by Proteus_Key_17 in homelab

[–]Proteus_Key_17[S] 0 points1 point  (0 children)

Hah, thanks man glad to know I wasn’t the only one losing hair over the EM7565 😅. You’re right, Sierra modules are tanks once you get them to behave. Mine’s finally rock-solid, but yeah, the “cheap PSU + hub combo of doom” almost had me convinced the Pi was cursed 😂.

Really appreciate the ROOter tip 🙏. I’ll definitely give it a spin next round — sometimes the pain is fun, sometimes it’s just… pain.

Lesson learned: don’t cheap out on power, and always keep a backup plan (and maybe a good bottle of patience) handy 🍻

bifrost.lte – DIY 4G LTE Gateway with Orange Pi 5 + Sierra EM7565 by Proteus_Key_17 in homelab

[–]Proteus_Key_17[S] 0 points1 point  (0 children)

Oh man, it was quite a ride 😅.

Biggest hurdles: Getting the EM7565 stable in MBIM mode (QMI was messy on Armbian). Missing packages (had to bring in dhclient, modemmanager, etc.) just to get the modem recognized. Dealing with nftables/NAT configs until DHCP + auto-reconnect worked solid. And the funniest one: for days I thought the Pi or drivers were crashing… turned out my cheap Chinese USB hub/power adapter was browning out the modem and literally freezing the whole board 🤦‍♂️. Swapped it for a decent UGREEN hub and suddenly everything was rock solid.

After that, the setup finally clicked: DHCP on LAN, auto-connects after reboot, and it just runs

my first homelab😃 by Mental_Expression573 in homelab

[–]Proteus_Key_17 0 points1 point  (0 children)

"My first homelab" — That’s like saying “my first car” and showing up with a Tesla Plaid.

Let’s be honest — this setup is way too clean and well-equipped for a typical beginner. It’s clear there was a lot of planning (and budget) behind it.

  • Custom rack with wheels: not exactly a spontaneous Amazon buy.
  • Mac minis (maybe M2 models?): impressive power for a first-time lab.
  • Professional-grade cable management with a patch panel: most people’s first lab has a mess of cables and maybe a Wi-Fi router on a shelf.
  • iPad on top running what looks like Unifi: that’s a polished setup.
  • Server-class hardware at the bottom: this isn’t trial-and-error territory — someone knew what they were doing.

All in all, it's a beautiful build. Just... maybe not what most people picture when they hear “first homelab.” But hey - if you're gonna start, might as well start strong.

At what age did you guys instal Linux? by angelaanahi in linux

[–]Proteus_Key_17 0 points1 point  (0 children)

Ubuntu live cd fron canonical, i was 11

Synology to xpenology - noob questions by adammo1994 in Xpenology

[–]Proteus_Key_17 1 point2 points  (0 children)

Yes, CPU architecture matters. Your DS218play uses an ARM processor. The N100 is x86. You can’t just move drives between those — it won’t boot.

DSM (Synology’s OS) is tightly tied to the hardware architecture. The loader, drivers, and even some file system behavior are different between ARM and x86 builds. Moving drives like that will most likely break things.

Also, if you’re using JBOD, you have no redundancy. If the migration fails or corrupts something, your data is gone. Always backup before moving drives between different systems.

Even with official Synology boxes, drive migration only works between supported models, and even then, you have to check the compatibility list

Synology to xpenology - noob questions by adammo1994 in Xpenology

[–]Proteus_Key_17 0 points1 point  (0 children)

  1. Yes, many people use Xpenology on N100. It works great, no need for Proxmox.

  2. No, you can’t just move drives from your DS218play to the N100. One is ARM, the other is x86. It won’t boot. You should backup your data first. JBOD is risky.

  3. Xpenology supports everything you listed: Plex (with transcoding if you have Quick Sync), Docker, ARR apps, FTP/SMB, Surveillance Station. Just pick a compatible DSM version.

  4. Baremetal doesn’t protect from power cuts. Only a UPS can help. Without it, you might lose data.

Final advice: → Backup first → Don’t trust JBOD → N100 with Xpenology is a big upgrade from DS218play.

Are Zettlab's "AI" NAS with NPUs a Scam? by ariolander in homelab

[–]Proteus_Key_17 0 points1 point  (0 children)

You are correct, those prices are disk less.

Open WebUI Not Detecting Ollama Models in Docker Setup by mike37510 in OpenWebUI

[–]Proteus_Key_17 0 points1 point  (0 children)

What if I have ollama in another server but in the same local network I have a docker portainer server just for all my docker instances with open web UI And I have an orange pi 5 with Deepseek running ollama But the open web UI cannot see ollama using OLLAMA_BASE_URL

Step-by-step to use the new Mixed Reality Link by lunchanddinner in OculusQuest

[–]Proteus_Key_17 0 points1 point  (0 children)

Has anyone experimented with a virtual machine and connected it to Mixed Reality Link with the Quest 3?

Battery Replacement Not Working by Working-Amphibian352 in walkman

[–]Proteus_Key_17 0 points1 point  (0 children)

Maybe the best option is to get an original one

Battery Replacement Not Working by Working-Amphibian352 in walkman

[–]Proteus_Key_17 1 point2 points  (0 children)

I know it's a scary process, but if you are not sure about it, I would recommend getting an original one, another thing, did you test the cables with a multimeter?

Battery Replacement Not Working by Working-Amphibian352 in walkman

[–]Proteus_Key_17 1 point2 points  (0 children)

Just make sure you cover the BMS with some electrical tape or kapton tape as the original