Thank you all for your reply; I'm so impressed with Touch. Definitely a keeper.

@zubozrout said in Manpages in terminal?:

Hi,
you can always Google man pages for specific things when on the go, even narrow it down by distro and its version when searching.

I had just spent about 45min searching for a ubuntu-app-launcher man page (saw and used the command in vid) before posting this; not convenient.

@hummlbach said in Manpages in terminal?:

If you want to have man pages in the terminal (which absolutely makes sense when thinking of convergence!) you could put them and man into ~/man respectively ~/bin manually and set the environment variable MANPATH or INFOPATH accordingly. Or make a click package for it which installs it to /opt/click.ubuntu.com/man.yourname/ and set PATH=/opt/click.ubuntu.com/man.yourname/current/bin and MANPATH=/opt/click.ubuntu.com/man.yourname/current/man or whatever in ~/.profile... That would be cool, I would install it too!

@dobey said in Manpages in terminal?:

@hummlbach Or, simply install them in libertine and access them inside the container.

Yep, definitely going for the computer in a pocket; I'm absolutely going to implement 'man' with or without the continuation of the precedent :0] Thank goodness this OS makes that possible. Thanks for the tips.

Thank you all for your time! Good to meet you.

@ikoz Actually the --help readout has "init" in parenthesis, that command works too

@ikoz Actually the --help readout has "init" in parenthesis, that command works too

That's what I was initially told, @arubislander ;But I had an error after only changing the "framework" to "ubuntu-sdk-16.04.5", something along the lines of "16.04 is deprecated, no longer supported. Please use a more current framework".

I then changed the other settings to accommodate the rollback (the only thing I could think to do), but maybe there was something more I could have done with the current Clickable?

I have been using "clickable create" per Youtube and doc tutorials. Not sure if it's too much different than "clickable init"? I'll have to look into the latter. [Edit: looks like they are equivalent commands]

One of the traditional benefits of open source is making sure perfectly good hardware doesn't go to waste, (old laptops to netbooks etc.). I'm glad 16.04 still installs on my Nexus 5; Unfortunately I don't see any app for an external tethered camera; and the Word Processor (LightP) is not as good as the reviews indicate (can't intentionally save without creating new file, or overwrite a file); And there is no Emacs available in shell. I can use the whole thing as SSH with a whole lot of chrome, but I'd prefer better.

So... I need to do some dev! One of the examples in Qt Create is virtually a camera app already. But my efforts have been a bit cumbersome so far:

• I reverted to clickable 7.9 in the pipx repos (the only install method that works on my Debian)
• I arbitrarily changed the minimum version to 6.0 in clickable.yaml
• Changed "framework" to "ubuntu-sdk-16.04.5" in manifest.json.in
• Changed "policy_version" to "16.04" in {project}.apparmor

... And after three days of effort, at least something is happening on Nexus 5, unfortunately just a blip and an immediate crash of the boilerplate helloworld.

Perhaps there's a better approach. I'm going to look for an error log, but if anyone has any tips or resources, that would be great!

@ikoz Thank you much!

Or... the installer link I found is out of date?

@ikoz Ah!... So has clickable moved beyond supporting the Nexus 5 I wonder? (It doesn't work with most carriers anymore as I understand (VoLTE or something?). At least that was the case. I was also curious why Liberty containers did not seem to be working out-of-the-box on the Nexus 5.

lomiri-app-launch did not show up in an apt-cache search on my phone. (?)

I first attempted some app development on my Ubuntu tower and actually ended up with the same roadblock then; I moved over to trying every available installation method, listed for clickable-ut on my Debian laptop, running into various errors, settling on a successful run with pipx; When running "clickable" in my QML package's directory It ends with the following error (running "clickable desktop" works fine):

[...]
Cleaning up.

Running command "launch"
Trying to kill the app before starting

Launching app
/bin/bash: lomiri-app-launch: command not found

I've temporarily bricked my Ubuntu tower when I tried install various Lomiri packages, one which augemented the kernel in way my machine doesn't like. But that's my fault, not something I expected to run into though.

Now that I'm back to this error, I did find a package on Debian for "lomiri-app-launch"; and once installed and rebooted, "which" can't find it in "/usr/lib/x86_64-linux-gnu". I don't know much about that folder, it shows as executable; but I added it to the path anyway; strangely "which" still can't find it, even after logout. I'm not even sure if it's looking for a package on my primary machine or on Ubuntu Touch but... Oh what a tangled web we weave.

Any help would be appreciated.

@stanwood , Thank you much!

I did attempt the first half:

sudo rm -rf ~/anbox-data 

without success. Right now I have it in a functional precarious state after various adb resets and anbox-tool installs. So I'll leave it for now. But if I try again, I'll take a look at the local folder there.

Is there a quick way to reset Anbox after messing with it?

I installed an unsuccessful google play services and app combo, and wanted to try again. I know how to uninstall a given package, but I couldn't isolate the the play services package/packages.

I attempted deleting the anbox-data directory so I could re-run "anbox-tooll install". I didn't have the appropriate permissions even with sudo. I started fishing around online for a quick method, seeing as how these are isolated in containers.

Looks like I should have been looking into Waydroid this whole time instead? as that's the more preferred app?

My g'ness... I just, barely remembered it... phew! So that's taken care of from a functional perspective.