@keneda I do not have a complete solution for everyone, just what I did:

0. export LD_PRELOAD= (libtls-padding.so causes unexpected things)
1. boostrap chroot filesystem as per https://wiki.debian.org/Debootstrap
2. mount /proc and /sys, bind mount /run/dbus (optional for smbnetfs) and /dev (fuse there)
3. chroot in with 3003 (and optionally 3004) supplementary groups
4. add apt_ user to 3003 (and probably 3004) groups
5. edit /etc/resolv.conf with nameserver of preference
6. install smbnetfs with apt-get, configure as per https://wiki.gentoo.org/wiki/Smbnetfs (I only needed auth line)
7. mount smbfs in chrooted environment with allow_others option
8. on a host filesystem as a phablet user create a symlink under Downloads (any folder accessible by filemanager without unlocking is fine) to the required share(s)

@harrisonpatm said in Accessing SMB shares, issues:

@ygrex No luck for me unfortunately. I dug around in the ~/.config folder for other places to modify, but still no joy.

you dug around looking for what? it is literally .config/com.ubuntu.filemanager/places.conf

finally got it resolved, deleted ~/Pictures (it was a symlink to other place on sdcard) and rebooted

@kugiigi said in How to take screenshot?:

@ygrex Did you by any chance do something with sharing UT folders with Waydroid?

nope, I do not have waydroid

@stanwood said in How to take screenshot?:

Did you try the other way?
Long press the power button and click on "screenshot".

Not sure it will change anything, but it's worth a try.

just checked this way, all the same result: screen flashes, clicking sound, but no files appeared

@harrisonpatm
mounting did not work well for me either, but shares are accessible with filemanager as described in https://forums.ubports.com/topic/4084/file-explorer-pc-files-samba-acces/4?_=1750938606398

Hi,

Pressing Up+Down volume buttons gives a screen flash, but nothing appears under Screenshots/ directory

not sure if it is relevant to the issue, but it also logs this lines:

Jun 26 13:36:03 ubuntu-phablet lomiri[2703]: [2025-06-26:13:36:03.404] qml: ItemGrabber: No fileName to save image to

tried fbcat, but it gives me distorted picture

and failed to get anything useful from raw /dev/fb0

tried it today at the same spot it worked last time

gave it up after 15 minutes, as per my understanding I did exactly the same thing but it just did not work today

@Keneda
yes, tried it a few times with unav with the same outcome

but today it found me in 3 (three) minutes, that makes me thinking that all ephemerides were quite uo-to-date and it did not work for some other obscure reason

the whole point of this thread is to say that geolocation is that obscure process with certain failure rate (quite high for me) and there is little one can observe about it

will check it next day to see what happens

For sure, this is what I get without Waydroid. In fact I stopped using Waydroid primarily because it breaks GPS.

Tried GPS location two times today under apparently clear sky in wide open area. Both times it did not succeed in locating me in somewhat 30 minutes.

I know it will occasionally work, but would help if there is any trick to know in advance if it is going to work or not without the need of waiting that long.

This is the usual scenario of geolocating on my phone. I open maps in Morph, geolocation sign highlights in notification bar, and I wait for 15 minutes. in a while it either starts showing my position, or I give up.

Suppose it all went well and it found the geoposition. But in couple days when I need it again, I would expect it to have more or less up-to-date ephemerides, but what I see is the same waiting for 15 minutes with some success chances.

On the other hand it happens often that it does not show my position in 15 minutes. I understand it may take longer, but since the whole process is quite obscure, there are high chances it will never show anything for me (I tried waiting for >1 hour with no success).

Any tricks to have GPS less painful?