The software for linux phones is pretty much there. Gnome and KDE mobile are surprisingly capable. There’s built in apps for every basic thing you’d need on a phone like a dialer, SMS app, camera, etc. plus all the normal apps adapted to work with mobile like the calculator and maps apps.

The only real limitation is with the hardware. I have no idea why all new linux phones launch with specs from a decade ago. You can get a better experience by flashing ported Postmarket OS to an Android phone like the Nothing phone or a OnePlus 6t.

It shouldn’t be like that, no idea why it’s impossible to just have a linux phone with decent specs and a good camera on par with modern flagships.

Consumers: “We don’t want AI data centers anywhere near our homes!”

Nvidia: “Ohhhh, you want them as close to your homes as physically possible?”

How is it able to get the latitude and longitude of the devices? As far as I’m aware, the bluetooth spec doesn’t provide coordinates as part of its metadata. And you’d need some kind of triangulation method otherwise. I’m certainly not able to get the coordinates of my bluetooth devices. Wish I could, would make finding the remote a lot easier.

I’m highly suspicious that this entire project and even these responses are all AI-generated. Something about the grammar and use of em dashes that really seems fishy to me. And in their first (almost identical) post to this one, someone said that hiding the source code could make people suspicious it’s been authored by AI, and OP responded “what counts as ‘AI-authored’ to you?”. Veeeery sus

As if speaking English would make a difference in them understanding the title

Image reading this title to some 16th century farmer

Yes. Here’s the contents I currently have in /var/lib/gdm/.config/monitors.xml:

<monitors version="2">
  <configuration>
    <layoutmode>physical</layoutmode>
    <logicalmonitor>
      <x>0</x>
      <y>0</y>
      <scale>1</scale>
      <primary>yes</primary>
      <monitor>
        <monitorspec>
          <connector>DP-1</connector>
          <vendor>SAM</vendor>
          <product>Odyssey G93SC</product>
          <serial>HNTW700164</serial>
        </monitorspec>
        <mode>
          <width>5120</width>
          <height>1440</height>
          <rate>239.997</rate>
        </mode>
        <colormode>bt2100</colormode>
      </monitor>
    </logicalmonitor>
    <disabled>
      <monitorspec>
        <connector>HDMI-1</connector>
        <vendor>FUN</vendor>
        <product>Evanlak8K V2</product>
        <serial>0x00006410</serial>
      </monitorspec>
    </disabled>
  </configuration>
</monitors>

The disabled dummy plug is the “Evanlak8K V2” device while my functional monitor is my Samsung Odyssey OLED G9. This config is the same as the one currently running on my GNOME desktop config, but in GDM still defaults to the enabled dummy plug, even with the fixed ownership.

At this point, do you think I should issue a report on GDM’s repository? Maybe the devs there would have more insight

Just checked the ownership of the monitor config, it was gdm:root, so I changed the ownership to gdm:gdm and rebooted. Still facing the same issue.

Didn’t see any error messages in the logs about not being able to load wayland, but just to confirm, I ran loginctl show-session {gdm session id} -p Type which returns Type=wayland, so it’s definitely running under wayland. I have an AMD GPU though so I wouldn’t expect there to be any problems there.

Not seeing anything else weird in the logs that are jumping out as strange to me either, so a bit at a loss here. Any other suggestions?

I had a few Raspberry Pis and some Libre Computer boards a while back, but I recently decided to just build a beefy small form factor PC and put Proxmox on it, and honestly couldn’t be happier with the results. The ability to allocate resources for services and containers on the fly is a game changer. I can spin up a fresh container running whatever service I want in a matter of minutes without the hassle of flashing to a device and setting up networking, etc.