passepartout

Wenn es eine gute Synchro gibt auf Deutsch, wenn es keine (gute) deutsche synchro gibt wie bspw. bei Rockstar games dann mit deutschen Untertiteln. Manchmal auch Englisch mit englischen Untertiteln aber eher selten.

Menü / UI Sprache ist soweit möglich immer Deutsch, außer die Übersetzung ist schlecht. Ausnahmen sind Spiele für die man öfter mal was googlen / in der community erfragen / yt tutorials anschauen muss, wie bspw. Minecraft. Das spielt aber glaube ich auch wirklich niemand auf Deutsch.

Liegt bei mir auch nicht an den Englischkenntnissen (CEFR C2).

I hope so as well, as Valve is one of the few companies left these days not consisting of shareholder imbeciles.

You forgot

• MS buys all the competition
• MS kills said companies they bought before so everyone has to use their half assed shit product

Bin kein großer fan davon dem Springerdreck hier eine Plattform zu geben.

Und trotzdem frage ich mich grade ob die Frontpage der Bild wirklich so aussieht oder ob das bearbeitet ist? Da kriegt man ja nen epileptischen Anfall.

As far as resources go, books are more complete resources but youtube videos and getting started pages / documentation / blog posts about projects / topics will get you up and running faster. This will be the resources you will frequent the most (+ stackoverflow) in the future over books. At some point a profound knowledge will help though. If you're really into books you can check out O'Reilly or No Starch Press (they're on sale via Humblebundle regularly). If you have the spare time do a Harvard edx CS50 Course (stay away from udemy or similar services if you want a general knowledge and are not looking for some very specific thing). Read forums like the self hosting / home lab / programming communities on lemmy, try to understand the discussions / their problems, they may arise on your journey as well.

For selfhosting I'd recommend getting comfortable with the linux command line at first (this may help: https://www.linuxcommand.org/). Set up a VM in VirtualBox / VMWare / whatever hypervisor you want, install a Linux image (I'd recommend plain Debian without desktop environment). Now you have a sandbox where you can toy around. If you're on windows you can use WSL2. If you're already on a linux desktop, toy around there. If you already got some hardware like a raspberry pi, get that up and running, plug it into your network and SSH into it, then you have got your playground there. Get the basic commands in like ls, pwd, cat, tail, touch, mkdir, rm, ... And some things you can do with them. Check out their respective man-pages. After that, install some packages, change configs (I'd recommend nano over vim for starters). From now on, there are no boundaries of what to do. Set up your first basic webserver with apache / nginx / caddy, install docker / podman and containerize / get some images, set up pihole, nextcloud, jellyfin, do whatever you like... Congratulations, you are now "self hosting". If you got all that, which may take a while, you can consider networking and firewalls (you could get a cheap router that supports openwrt to learn about these things). Don't open ports to the internet as long as you're not 100% sure what you are doing. You can set up a VPN with DynDNS on most modems / routers connected to your ISP though, opening up your self hosted services only to you / anyone with access.

For Programming, set a goal. This does not have to be reinventing the wheel, try something small and doable first, like a notetaking app, snake game, etc., as these might still take you several weeks / months to complete, depending on the technology you implement them with. That said, reconsider Android as an entry into programming. Toy around with some stuff with a lower gateway hurdle, like html, js, css, then maybe Python or Java. Get to know the syntax, data structures, keywords, paradigms, conventions with small little programms, and/or have a look on pages like leetcode, codewars, khanacademy, etc. Paste code with errors in chatgpt for help if you get stuck. Only then (or parallel timewise if you have a high tolerance to frustration) research the programming language and paradigms used for android (likely java / kotlin), get android studio up and running, start with a simple screen showing e.g. a label and a button. You can always extend (or more likely start from scratch) later on. If you want more than what the plain android framework is capable of, look for something else (I don't know a lot about modern android programming though lol.)

I am on Fedora as well and have used the microsoft wireless dongle with the medisalix/xone kernel module in the past, but i stopped using it since it had me pull and plug the dongle once every while to make it work again.

Nowadays i just use bluetooth (with my xbox one and xbox series x controller). You actually don't need any additional packages for that. Three things to consider about this:

• You possibly have to upgrade the controller firmware with an atrocious app on a windows machine
• pairing is a nightmare (needed an hour for one controller always trying until the pairing completed)
• You need to set some bluetooth settings in a config file for Bluetooth LE timings since the microsoft team thought it would be funny to not let the controller advertise the right configurations.

All that said, once paired and configured it just works (TM). Feel free to reach out if you need further information.

Thats what I noticed as well. I think it was about three cancels at every menu point.

Google makes small steps towards repairability with their phone design, e.g. dual entry design (so you don't have to lift off the screen to replace the battery, which could break), seperate daughter board for the usb port (so you don't have to replace the whole motherboard when the usb port breaks, which is a part that is in heavy use), etc. These are baby steps but maybe they will have a user service friendly device ready by 2027 when the EU requires it.

Sadly the glue they used for the pixel 9 seems to be really sticky so the pull tabs break, you can look for teardown videos on youtube.

They do: https://de.ifixit.com/Device/Google_Phone

• You can remove the search bar (which was the only thing bugging me about the "original")
• changing icon and font sizes, shapes, font families, ...
• actions for screen double tapping ("lock screen" is what i use)
• is open source

To me this is a feels like a full blown release as I've been using the beta, alpha, the builds on a fork of one of the maintainers github fork, ... All of them with very few issues.

That was honestly the only thing i needed from a launcher when i got my pixel 6a two years ago, but there is so much more to it as i later discovered. All the tweaking that is possible on top of the (very good) pixel launcher, which it was built upon but had this one flaw.