I’m now relatively sure that it is much better for you to change your sources.list in accordance with: ⚡ Mirrors. It should be worth of trying this anyway.
I was looking at that page and wondering if I should try it. But while http://repo.pureos.net/pureos/pool/main/p/phosh-mobile-settings/ does have phosh-mobile-settings_0.20.0-1
The mirrors I’m looking up don’t:
https://mirrors.jevincanders.net/pureos/repo/pureos/pool/main/p/ - No phosh-moble-settings
https://mirrors.sonic.net/pureos/repo/pureos/pool/main/p/phosh-mobile-settings/ just the beta
https://mirror.fsf.org/pureos/pool/main/p/phosh-mobile-settings/ just the beta.
Unless I’m navigating them wrong.
2 Likes
No, I’ve just checked/compared (after writing my post to be honest, although wanted to go to sleep) the same /main/p/phosh-mobile-settings/, actually confirming what you nicely put together in your post. It is or must be some synchronization related, so let us look forward to when everything on track again, tomorrow perhaps (nothing to be worried about). Same here (just the beta): https://mirror.linux.pizza/pureos/pool/main/p/phosh-mobile-settings/.
Yet it does not have: phosh-mobile-settings_0.0.1-0pureos1_arm64.deb.
2 Likes
@Sarcasmo220 I updated today and it came through no problem :). Added benefit of getting the slidey update 
2 Likes
I went ahead and downloaded the package manually to install it. Glad to hear it updated fine for you!
1 Like
The command gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/1a86:e2e4/ output "['Unknown', 'Linux FHD', 'Linux #0']" + reboot made my NexDock Touchscreen work like a charm ! Thanks.
2 Likes
Great that works @Lionel ! For other nexdock 360 users: Nowadays you can just use phosh-mobile-settings and enable the dock in the Convergence Tab which sets up that setting.
1 Like
hi Lionel,
I tried to do the same with a M14t screen from lenovo without success (see Gsetting command to activate touch screen on external monitor). So sorry to hijack this thread, but could you explain how you find 1a86:e2e4/ output "['Unknown', 'Linux FHD', 'Linux #0']" ? If it’s not the right place, I will complete my original post.
I tried with gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/2d1f:524c/ output "['LEN', '25251', '1194738522']" but it didn’t work.
Hereafter my edid information with 2 product name (i tried both without success).
Vendor & Product Identification:
Manufacturer: LEN
Model: 25251
Serial Number: 1194738522
[…]
Detailed Timing Descriptors:
DTD 1: 1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz (309 mm x 174 mm)
Hfront 88 Hsync 44 Hback 148 Hpol P
Vfront 4 Vsync 5 Vback 36 Vpol P
Display Product Serial Number: 'V307G6CZ'
Display Range Limits:
Monitor ranges (GTF): 50-75 Hz V, 30-90 kHz H, max dotclock 210 MHz
Display Product Name: 'M14t'
And my lusb output
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 2d1f:524c Wacom Taiwan Information Co. Ltd.
|__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M
ID 2d1f:524c Wacom Taiwan Information Co. Ltd.
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
ID 0424:2640 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
|__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
ID 0424:4041 Microchip Technology, Inc. (formerly SMSC) Hub and media card controller
|__ Port 2: Dev 5, If 3, Class=Vendor Specific Class, Driver=option, 480M
ID 2020:2060
|__ Port 2: Dev 5, If 1, Class=Vendor Specific Class, Driver=option, 480M
ID 2020:2060
|__ Port 2: Dev 5, If 4, Class=Vendor Specific Class, Driver=qmi_wwan, 480M
ID 2020:2060
|__ Port 2: Dev 5, If 2, Class=Vendor Specific Class, Driver=option, 480M
ID 2020:2060
|__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=option, 480M
ID 2020:2060Do someone have an idea why the old NexDock 2 isn’t recognized correctly anymore? i just wanted to check some stuff and with some of the updates in the last year the Librem 5 doesn’t detect the screen resolution (1024x768 is the highest setting) and it’s not shown up in phosh-mobile-settings / convergence. in the pull down menu the option is active.
Since receiving my Librem 5 (October 2022), I’ve occasionally used it with my NexDock2.
To do this, I would connect it via USB-C, and beforehand, to take advantage of the maximum resolution, I would run the following command in a terminal (source: NexDock 2 touch EDID doesn't detect the correct modes (#338) · Issues · Librem5 / linux · GitLab , post by Guido Gunther from November 12, 2021)
sudo -s
echo edid/1920x1080.bin > /sys/module/drm_kms_helper/parameters/edid_firmware
This worked perfectly.
Then, several months ago (under Byzantium), the connection to my NexDock2 stopped working. Dock detection was too slow (the cursor appeared just as my NexDock2 was automatically shutting down), and it didn’t seem to detect the Librem 5.
I’ve since migrated to Crimson and updated the firmware of the TPS65982 USB PD controller as described on the dedicated page: Files · master · Librem5 / fw / firmware-tps6598x-nonfree · GitLab
But when I connect my Librem 5 to the NexDock2, nothing happens. The NexDock2 doesn’t seem to detect the Librem 5. Conversely, the Librem 5 doesn’t detect the NexDock2, and after less than 30 seconds, the NexDock2 goes into sleep mode.
I also tried to reproduce the command mentioned above (suggested by Guido Gunther), but it failed. The error message indicates that the /sys/module/drm_kms_helper/parameters directory is not writable.
Even after changing the permissions of each directory (from the parent to /sys) to write permissions, it didn’t work.
Has anyone else experienced this and found a solution?
Thank you for your feedback.
Have you tried contacting Nexdock Support to troubleshoot any potential hardware issues? Maybe even try another device to see if works?
I would then ask Nexdock for the firnware requirements needed for it to work.
No, I haven’t tried contacting NexDock support. I don’t have any other equipment with a USB-C output (with DisplayPort) for connecting to the NexDock. However, the NexDock 2 works perfectly with a Raspberry Pi (using a USB + HDMI connection). The same is true for a PC (also using a USB + HDMI connection). I have no problems with my Librem 5 and another dock (Selore&S-Global SEUC0305 9-in-1 USB-C Hub). On the other hand, I confirm CaC’s observation.
Thanks Sarcasmo220 for the suggestion. I was finally able to test my NexDock 2 with another device, and the behavior is identical to that with my Librem 5. In fact, the devices don’t detect the screen, and conversely, the NexDock doesn’t seem to detect the device. And during the NexDock’s automatic sleep mode, the mouse cursor appears, and I can move it by running my fingers over the NexDock’s touchpad. Sarcasmo220 must be right: it must be related to a hardware issue with the NexDock. I haven’t contacted NexDock support yet for advice.
1 Like
I contacted NexDock support regarding my issue, and here is their response:
The problem could be related to:
The NexDock’s USB-C port
The USB-C cable
To check if the USB-C cable is faulty, please try another USB-C cable compatible with the video output and let us know the result.
The NexDock comes with a USB-C 3.1 Gen2 cable that is USB-IF (e-Marker) certified and supports a data transfer rate of 10 Gbps, 4K video, and 100W power delivery. You can use any other USB-C cable with similar specifications, such as this one: Amazon.com: Rixmie Short USB-C Cable [5 inch], 100W PD Fast Charging, 20Gbps Data Transfer, USB C to USB C Short Cable, Thunderbolt 3 for iPhone 17, MacBook, Android Auto, External SSD and More Type-C Devices : Electronics
Sincerely,
The NexDock Team
Actually, I was aware of the importance of the cable type (it was frequently mentioned in forum discussions), and I remember misplacing the USB-C 3.1 Gen2 cable that NexDock included in the box. So I tried other cables, mistakenly thinking they were compatible and wouldn’t cause any problems. Last week-end, I tested the USB-C cable provided by Purism with the Librem 5. After some initial display issues during connection, the system finally worked. Therefore, the NexDock is not the problem. The issues I encountered stemmed from losing the original USB-C cable that came with the NexDock.
However, some problems persist:
The NexDock does not appear in the “Convergence” view of the “Mobile Settings” app.
Furthermore, in the “Displays” view of the “GNOME settings”, the maximum supported resolution is 1024 x 768, not 1920 x 1080 which is the resolution supported by the NexDock 2.
Under Bizantium, it was possible to bypass this limitation using the method described in my previous message, by executing n the following commands in a terminal:
sudo -s
echo edid/1920x1080.bin > /sys/module/drm_kms_helper/parameters/edid_firmware
However, under Crimson, it is impossible to execute this command.
The second line returns a “Permission denied” error message.
Could we get some help from the Purism development team to restore the original (Bizantium) behavior that allowed for a 1920x1080 display?
Since it’s not possible to send 3 consecutive posts (
), I’m updating the last one published !
As the French proverb says, “on n’est jamais mieux servi que par soi-même” (in english “If you want something done right, do it yourself”).
So, here’s the solution to my problem.
Step 1:
sudo mkdir -p /lib/firmware/edid
Step 2:
Copy the file at this link 1920x1080.bin (will be available 30 days only) into the dedicated directory on your Librem 5.
sudo cp /home/purism/Downloads/1920x1080.bin /lib/firmware/edid/
Step 3:
Set a variable for the NexDock 2 connection.
echo “edid/1920x1080.bin” | sudo tee /sys/module/drm/parameters/edid_firmware
The first two steps went smoothly; the changes remain permanent after restarting the phone. However, the content of the /sys/module/drm/parameters/edid_firmware file is reset at each boot.
To avoid having to re-enter the command line in a terminal after each boot, I suggest creating a systemd service that will run every time the phone starts.
To do this, we create a script called init_edid.sh in the /home/purism/Public directory
The file’s contents are as follows:
#!/bin/bash
# Set a variable for the NexDock 2 connection
echo edid/1920x1080.bin > /sys/module/drm_kms_helper/parameters/edid_firmware
This file must have executable permissions:
chmod +x /home/purism/Public/init_edid.sh
The file defining the service can be called usefull_init_cmd.service
It is a text file that contains:
[Unit]
Description=Execution of useful commands during the startup
After=network.target
[Service]
Type=simple
User=root
Group=root
ExecStart=/home/purism/Public/init_edid.sh
[Install]
WantedBy=multi-user.target
The usefull_init_cmd.service file is then copied as root (“sudo -s” in a terminal) to the /etc/systemd/system directory.
Still as root, the permissions are changed:
chmod 644 /etc/systemd/system/usefull_init_cmd.service
Then, still as root, the service is enabled to start at boot:
systemctl enable usefull_init_cmd.service
3 Likes