Yes, this is the layout I get in landscape, but it's not picked up in portrait, so that it's just a bit too narrow would make sense for it not to be picked up as a large screen as the resolution is kind of weird when tilted into portrait instead of landscape.
Do you need anything more from my part? If so, or if you want me to test/change anything, let me know, I am happy to supply with whatever I can to help 🙂
Here is a screenshot of the setting, and if I read this correctly it's off, which makes sense for me as I mostly use the app in "small screen mode" where I prefer it to be on the bottom.
The problem surfaces when used in unfolded (big screen) portrait mode, as for landscape view of the same unfolded screen, it's split and works as usual.
As far as I can tell, rail mode is off and large screen is on?
For reference the resolution for the folded out display is 1856 × 2160 pixels and it happens in "portrait" mode, where the resolution will be weird I guess.
If I switch to landscape the issue is not present, I didn't think to test for that until you mentioned "weird screen size".
Thanks for looking into it, and it's probably a corner case since the foldable screens are not all that common, at least not yet.
There is a new bug in the current version if you use a Galaxy fold big screen, kind of hard to describe so here is a screenshot:
As always, thanks for your great work!
The article explains how the method works—it's not so much traditional virtualization as it is a series of small, deceptive programs. The "host" app downloads a collection of fake apps and analyzes legitimate apps to closely mimic their behavior. When a user tries to open a real app, the host app intervenes: it closes the real app and launches a lookalike dummy app instead, using accessibility permissions.
To the user, it appears to be the legitimate app, but in reality, all input and data are being captured by the fake one. With accessibility access, the malicious app can monitor every tap, gesture, and keystroke. It can even track which apps are opened or detect when the lock screen appears—enabling it to build even more convincing fake versions of other apps and extract more personal information.
This is a prime example of why you should never install unofficial apps or grant permissions unless you're absolutely certain the app is trustworthy—sometimes, not even then.
Hope that helps clarify things. It's not totally accurate to all the details, but a general description to perhaps understand the process better.
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:
Run ls -l /dev/ttyUSB0 You should see output like: crw-rw---- 1 root dialout 188, 0 Jan 1 1970 /dev/ttyUSB0
Note the major (188) and minor (0) numbers.
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?
Thank you so much for all your hard work on Summit! I know you're probably already juggling a ton of feature requests, but I was wondering if it would be possible to add an option to organize downloads into folders based on their source—something like //.
Sync used to have this, and it made my (admittedly excessive) image and meme collections so much more organized, even if I rarely look at them again. Definitely not a big deal, just a nice-to-have. Thanks again for everything you do!
Subtitles are not always simple text files in the source. They can come in various formats like SRT, WebVTT, Teletext, and VobSub—if they are present at all.
To integrate them into WebM, you must first determine if they exist, ensure they have the correct language tags (and tag them properly if they don’t), then extract them, convert them into a format compatible with the player, and finally remux them alongside the video and audio. This process can easily fail in an automated workflow if any of these conditions are unmet or if the subtitle format is incompatible.
Given this complexity, it’s understandable why many choose to avoid the effort rather than addressing whether WebM supports subtitles.
I am not defending anyone, but the process of it all makes it understandable, at least for me.
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)
Just happy to help 🙂