@uwahl This was the place. By writing a new file named places.conf in /home/phablet/.config/filemanager.ubports/, I was able to get the File Manager app to access the server. Thanks all.
Technically solved issue. And yet, performance is incredibly poor. Very slow to load, and read-only.
@ygrex the directory 'com.ubuntu.filemanager' doesn't exist in my ~/.config
@ygrex No luck for me unfortunately. I dug around in the ~/.config folder for other places to modify, but still no joy.
@arubislander Nope, I have added a few apt packages already. And honestly I'm probably about to reinstall from scratch, so I'm sure I'll give this another try.
Unfortunately, didn't work for me. Snapz0r ran and rebooted the device, but afterwords snap still wasn't enabled. Mounting root to rw and attempting to install snapd via apt also didn't work, I'm assuming because of dependency issues and/or not enough space on the small root partition. Thanks though.
@arubislander said in Can I boot to tty/console only?:
While it may not be exactly what you asked, you might be interested in a post I wrote on installing LXD and running LXD containers on your UT device.
I'll be trying this now, thanks for the advice
From my searches on this forum, and other places, it seems like other people have been successful mounting or at least accessing their SMB shares via either the GUI or command line. I'm having trouble.
GUI: in the File Manager app, there's a section titled 'Network'. But tapping on it takes me to an empty folder, nothing found. There doesn't seem to be a menu or setting option to select, find, or discover the location of the SMB share.
CLI: when mounting via command line, I get "mount error: cifs filesystem not supported by the system
mount error(19): No such device"
I have already made sure that cifs.utils is installed and active, and I can ping the server address from UT
Device is Pixel 3A XL
@arubislander Considered it, as well as Droidian/Mobian, but UT is really quite good, I like it a lot. I'm only exploring what else I can squeeze out of it, I don't think there's anything wrong with that.
In any case, it seems like it doesn't work "out of the box," so to speak. Running sudo systemctl set-default multi-user.target and rebooting, the phone boots to the Google splash screen (I'm using a Pixel 3A XL), and just stays on the splash screen, screen staying on. With the phone on, I am still able to ssh into it, run sudo systemctl set-default graphical.target, reboot, and Ubuntu Touch boots normally after that.
Any ideas?
@Moem said in Can I boot to tty/console only?:
And how would you pick up a phone call?
I wouldn't. I should clarify, my interest in UT is the possibility of a fully functional Linux distro in the form factor of a pocketable phone (plus a small keyboard). I don't intend to use the phone/SIM function. It's pretty amazing what we can do with computers today, and I'm appreciative of the great work that has been done with this project.
So, any ideas as to whether this might work?
@ikoz Reduced power usage. Preference for command line. Processor is freed up from serving a GUI, thus can get more done with less resources. Aesthetics, fun, learning. Want to see what UT is capable of, compared to a standard Linux distro
I know this is probably a long shot. But I was wondering if it was possible to boot UT to console mode only. I think it would be pretty cool to have a standalone handheld terminal device in the form factor of a smartphone. I also realize that if it did work, there would be no on-screen keyboard and I would need to use a wired keyboard. Still want to try it.
Ctrl+Alt+F2-F6 doesn't do anything like it does on other Linux distros. On most Debian builds, I would run sudo systemctl set-default multi-user.target, would that work here?
@ikoz welp, you got me there. Turns out the default keyboard was English (Dvorak); not for the on-screen keyboard, but only when a USB keyboard was plugged in. Thanks!
New install of Ubuntu Touch on a Pixel 3A XL, I'm having a lot of fun exploring its use as a supplementary terminal/tablet
I thought I'd trying connecting a USB keyboard via a USB-C to USB-A adapter. It's recognized without issue, but typing output is incorrect with about 75% of the keys. For example, keys 'a, s, z, and x' all type correctly. But the 'i' key registers a 'u' on the screen, the 'p' registers a ';'... it goes on. Furthermore, I used two different USB keyboards, and the errors were the same on both keyboards, so it seems like the issue is with UT, not hardware ('i' is 'u' on both keyboards).
Anybody have any suggestions for how to debug?