I understand this will have a low priority or none as it might raise security issues with the phone itself, but I was curious if it would be a feature on the phone. Creating a internet hotspot or sharing internet to other devices.
I would think that if this wasn’t shipped with it to begin with that it is something that could be added later. This assumes, of course, that the wifi radio can function in the mode required.
GNU/Linux desktops can already do hotspots. I don’t see any reason that the Librem 5 would be any different in the long run. The setting may not be exposed for the first several years, just like Lubuntu didn’t expose settings for WiFi networks that had more than a simple password.
Thank you for the responses! Guess we will just have to wait and see
Actually, I’m using as daily smartphone the Ubuntu powered BQ E4.5 (formerly developed by Canonical, now by a community UBports.com). Its hotspot function is what I do use around 10 hours a day. It would be a show-stopper for me, if this is missing in the Librem-5.
Oh that sounds promising, I’d love to create a hotspot for my nintendo switch if I’m on the move but it’s not a dealbreaker for me I guess
I also use hotspot capability of my phone 8h/day, so that feature is important to me too. I wonder, once I imagine it’s related to this topic, if it’ll be possible to use VNC to access the desktop mode of LIbrem5 when you’re, e.g., at your workplace, using your firm’s computer.
UBPorts will be officially supported on the Librem 5. So, I think we will definitely have hotspot capabilities on the Librem 5 even if we have to install UBPorts to get it.
Depends on the wifi radio used, but hope you are right.
As the other said there should be no technical reason withe an normal wifi module + linux + debian.
And from the UI point the librem uses pureOS with Gnome wich allready suports hotspots in an easy way via the wifi settings menu.
Will probably look like this but optimised for small screens.
Gnome user manual:
@luisfsr: In regard to a VNC server running on the phone, the problem is Wayland. AFAIK the default VNC server for the Gnome desktop called vino, only supports X (like most VNC servers). The only alternative I have found to support Wayland is still in development: gnome-remote-desktop.
What is Wayland exactly? I tried googling and just ran into more terminology I didn’t quite understand.
I’m new to the terminolgy myself, but based on my understanding of windows inner workings, and my work in graphics programming, it is the graphical backend of a linux system. Think of it like a graphics library and manager, and GNOME as the specification of that graphical system.
Sorry if that doesn’t make anything clearer, or is in fact wrong. To keep it simple, Wayland/GNOME are the graphical portion of PureOS.
I’ll try to explain it in my own words, as much as I understand it so far (with references to Wikipedia). Please, somebody correct me if I’m wrong.
- Wayland like X11 are both display server protocols.
- X.Org is the current standard implementation of the X11 protocol
- Mutter is the compositing window manager for X when using the Gnome Shell as the graphical shell.
- So basically, your Gnome applications are displayed in the Gnome Shell using Mutter to display your windows which uses X.Org in return to get input from your keyboard and mouse, draw lines and text on the screen, etc.
- One of the problems of X11 is that it’s quite old and hasn’t been designed for modern (3D-)applications. And it’s complexity is another reason, why the Wayland protocol has been developed.
- As of today, Mutter is an ongoing effort to implement the Wayland protocol. So we have Gnome on X and Gnome on Wayland in most distributions today.
- It seems like the Wayland protocol will be the standard display server protocol in the future, but the current implementations are still not mature enough for some use cases.
- Still a lot of applications don’t support Wayland so far. As a workaround, there’s XWayland, to support X applications under Wayland until they support Wayland natively.
- Another (for some problematic) design decision is, that graphical applications can’t be run as root in Wayland.
Now to our Librem 5:
- The Librem 5 only supports the Wayland protocol; XWayland isn’t used due to resource constraints (battery consumption).
- The graphical shell for the Librem 5 will be Phosh.
- Phosh uses Rootston as Wayland compositor which in return uses the Wayland compositor library named wlroots.
Why Phosh and Rootston instead of Gnome Shell and Mutter? For a phone, a lean combination of display server, compositor and graphical shell is needed to be light on the scarce resources of a mobile device.
That’s how I understand it so far - somebody please correct me, if I’m wrong.
I an no expepert on the topic but reading alot on the topic of wayland the past years and woudl say its quit a good summery.