Avatar

infeeeee

infeeeee@lemm.ee
Joined
45 posts • 73 comments
Direct message

The problem is not building a new operating system, but app support. We have and used to have a lot alternatives, but because mainstream apps are missing no one wants to use them. They don’t have enough users, so developers won’t develop for them, egg-chicken problem. Everyone tried to solve this by android compatibility layer, but android apps will always run better on android…

I use microG since years at this point, and while most things are working, I always find some quirks, and some random apps not behaving as they should. I’m fine with that, but a non-tech guy would freak out from that. And it’s not even a completely different os, only an alternative implementation of GMS aka Play Services.

See previous and current examples, all of them was/is a good or at least usable as an os, but if you can’t use your bank’s app or whatever app you need in your daily life, you won’t switch to it. Even M$ couldn’t solve this problem, why Mr. Pei could solve it.

Edit: Obviously in the article they don’t speak about an actual OS, but one more Android skin… So Mr. Pei is not planning to solve this, they are just redefining the meaning of words, Android skins are called "OS"s in entrepreneur speak nowadays.

permalink
report
reply

I’m a happy user of input-remapper (AUR). I use it to replace PageUp/PageDown with Home/End keys on my Laptop. How does your tool compared to that?

Feedback: Can you add an example systemd service? Or it would be even better if the PKGBUILD would install it, I’ve seen a lot of software which adds a disabled service, so you just have to enable and start it.

permalink
report
reply

Posting here as there doesn’t seem to be an active Arch Linux community.

archlinux@lemmy.ml seems active to m

Your text says qemu-desktop is only “optional” for qemu-base. You can safely remove qemu-desktop, pacman won’t nag about optional dependencies.

For checking dependencies, I like to use pactree, it draws nice graphs in the terminal: https://wiki.archlinux.org/title/Pacman#Pactree

permalink
report
reply

It’s incorrect. I have 2 AMD cards, I can detach it from linux before booting the guest. After I shut down the guest I have to log out in Gnome to make the card usable again, but no reboot required. It depends on how you set it up. I have a single 34" monitor with 2 inputs, connected to both cards.

I recommend to read about this topic, it would be quicker than waiting for people to answer, your questions were answered multiple times. I recommend the vfio wiki on the r*ddit a lot of good links are collected there: https://old.reddit.com/r/VFIO/wiki/index

permalink
report
parent
reply

Why do you care? People do a lot of stupid and wrong things, you don’t have to care or share these things. See my example: I read about this backround image app or whatever is this, I thought “yeah, it’s stupid and I don’t care” and moved on with my life. Never thought about this again until you posted this here. There are a lot more important things to be angry about. Ignore the unnecessary. This guy makes nicely edited reviews, that’s all, forget the extra bullshit around that. Your life will be better.

permalink
report
reply

Which games exactly? What are their ratings on protondb?

permalink
report
reply

Because they have different appid. Izzy version is app.organicmaps.web fdroid version is app.organicmaps (you can see this in the url). Google version uses the same appid as fdroid. You can’t have two apps installed with the same appid, but this way you can have both installed at the same time.

I guess organic devs wanted separate appid for their 2 versions and fdroid just went with the default, original one.

So the 3 versions:

  • Web: built by organic devs, you can download this from github releases, scraped from there by izzy
  • Google: built by organic devs, you can download from github or from play store
  • Fdroid: built by fdroid build server, signed with fdroid devs’ key.
permalink
report
reply

The source on this is one guy from X (formerly Twitter), from Vietnam.

I mean, it sound plausible and expected, but it’s not some official news.

permalink
report
reply

I guess they don’t disclose it because they change it frequently. If whatever new arm chip became discounted, they just switch to that.

I noticed this a long time ago, Asus did this with their entry level routers frequently, but they at least disclosed it. You had to be careful, the same router with the same name could be totally different inside, only the revision number changed.

permalink
report
reply

Xiaomi’s reasoning was they produce different phones for Chinese internal and for global market. A lot of scalpers bought the Chinese version, took it outside China, flashed a global rom and sold it. Chinese versions have limited frequency support and sometimes different chipsets, the problem was buyers of these phones nagged to Xiaomi’s support and left bad reviews, even though it wasn’t Xiaomi’s fault.

Yes, it sounds bullshit, I’m just illustrating, that if you ask companies for reasons, they can tell you some similar stories.

The good part, is that bootloader opening workflow was not the best, but at least acceptable for me compared to Asus’. You had to register your IMEI with a Xiaomi account, than wait a week and you could open it (This was the workflow like 5 years ago, and I still have the same phone, I don’t know if they changed it). This way they could slow down the scalpers, and they could see if someone want to mass open a lot of phones at the same time.

permalink
report
parent
reply