y0din

If you want a second attempt, this might help.

To get USB devices working inside a container, you need to map the device into the container, which can be tricky—especially if you’re running rootless containers.

If you’re on Linux and want to avoid complicated setups with user namespaces, groups, or messing with udev rules, the easiest way to start is by manually recreating the device node inside a folder you control (like where your config is stored) using mknod.

For example, if your USB device is /dev/ttyUSB0:

1. Run ls -l /dev/ttyUSB0 You should see output like: crw-rw---- 1 root dialout 188, 0 Jan 1 1970 /dev/ttyUSB0

2. Note the major (188) and minor (0) numbers.

3. Change directory to the folder where you want to create the “clone” device node, then run: sudo mknod -m 666 ttyUSB0 c 188 0 (Use the major/minor numbers from your device — they differ by device.) This will create a device readable and writeable by anyone on the system so perhaps consider changing the mode from 666 to 660 and/or chown the file afterwards to your user and group. As I said, this is HACKY and not a secure solution.

You will now have a device file you can then pass into your container with the Docker/PODMAN option: –device /path/to/your/folder/ttyUSB0:/dev/ttyUSB0

I realize this is a pretty hacky and insecure workaround—feel free to downvote or ignore if you want something cleaner. But it’s a quick way to get your USB device accessible inside the container to get started. Later on, you can look into proper handling with udev or other methods if security is important.

If you use Windows, you are on your own unfortunately, I do not have experience with podman/docker in Windows environments.

or got a very good deal on TEMU?

It’s always been there in the add-on, why they removed it as a base feature beats me, but I feel they are going down the “Google route”, remove all that works and replace it with what you never asked for.

Google used to hold a lot of nice services and features, including Chromecast. Why kill something that worked so well for so many people?

Take a look at https://killedbygoogle.com/ if you have some spare time.

What the user wants does not matter anymore, seems to be a default all over these days… 🙄

If you download Good Lock (https://apps.samsung.com/appquery/appDetail.as?appId=com.samsung.android.goodlock), you can still modify this through the Home Up add-on, along with many other tweaks and settings. I’ve almost managed to restore it to how it was before One UI 7 using these tools.

While what Samsung did isn’t ideal, at least there’s a solution for some of the changes at least.

It’s a great tool by Samsung, but not promoted as much as it should 🙂

(edit: screenshot for reference)

It could definitely be stress-related, especially if you had a particularly bad night of sleep before this started.

When you don’t sleep well, your body can reset its cortisol production cycle. Cortisol—the hormone tied to stress and alertness—typically starts rising in the early hours of the morning, around 3–4 a.m., as part of a normal circadian rhythm.

But if you’re under even mild or subconscious stress, that spike can happen earlier or be stronger than usual, causing you to wake up prematurely and feel too alert to fall back asleep.

It’s like your body’s stuck in a “high alert” mode even if nothing obvious is triggering it.

Could be the birds that have already been mentioned as well, I am no expert, nor medical trained, but this reason is more common than you might think when waking up early. It’s the same reason you might find yourself waking before the alarm when you really need to be on time, like before going on vacation and you cannot miss your flight.

Here is a link to one of many in regards to sleep and cortisol

https://sleepdoctor.com/pages/health/cortisol

(edit: added part of the sentence that got lost before posting and figured I might add a link if someone wants to read more)

I know this doesn’t directly solve your issue, and it might not help much now, but I wanted to share my experience just in case it’s useful.

When I had a similar problem after switching phones, what ended up helping was that I had 2FA enabled beforehand. In that case, after selecting the option to recover my account suddenly allowed me to receive a verification code via SMS—something that didn’t appear on the usual login screen, it was greyed out before selecting this option.

It probably won’t work if 2FA is disabled, but maybe it’s still worth checking if any recovery options that shows up helps. There might be a choice there that helps you resolve your problem as well.

In any case, good luck—I hope you’re able to get it sorted soon!

you probably broke this part of the terms of service…

https://windscribe.com/knowledge-base/articles/why-did-my-account-get-disabled/