Re: XWayland Victory!
 

hi,

404 not found

anybody had saved all files?

https://github.com/Preflex/easy-chroot

thank you

Re: XWayland Victory!
 

I noticed that tonight too before checking this thread. Sad news, I hope Preflex is still on it, this all looked beautiful and I was eagerly looking forward to running it on my Jolla.

Re: XWayland Victory!
 

With Elros34 Help here is Ubuntu 17.04 xfce4 desktop running on Xperia X device (sfos 3.0.0.8):

Thanks to him for his good work :)

Re: XWayland Victory!
 

Nice! Would you please post files and some instructions. Thanks!

Re: XWayland Victory!
 

I try to have audio on with pulseaudio (pavucontrol)
I have an error: connection to pulseaudio failed...
how to resolve this error?
it will be very nice to have sound out.

Re: XWayland Victory!
 

Hi @Elros34

If you get a mo, is this all still working on the Photon Q?

Thanks

Re: XWayland Victory!
 

Its been so long since I tried this but many of the commands are in the first post of this thread. I remember it worked for Manjaro distribution. Kind of a slug on my Jolla 1 but usable. Those on Xperia probably will have a better experience. Will have to try again.

EDIT: A link to the Ubuntu distribution used would be nice :)

Re: XWayland Victory!
 

Here is the link :

https://github.com/elros34/sailfish_ubu_chroot?files=1

Re: XWayland Victory!
 

Yes like on Xperia X.

Re: XWayland Victory!
 

running on my Xperia XA2 plus 6GB RAM dual SIM...
impossible to run Firefox why? any help with this error

Re: XWayland Victory!
 

Impossible to see the picture clearly especially error message

Re: XWayland Victory!
 

Yeah, too small. Try switching on scaling or use a magnifier.

Re: XWayland Victory!
 

Here is the error:

Mozilla crash reporter
We're Sorry
Firefox had a problem and crashed.

Re: XWayland Victory!
 

Very informative ;)

Re: XWayland Victory!
 

There's a button called 'Details', which I believe does what it says.

I would also suggest reporting the crash to Mozilla. You lose nothing by doing so, and who knows, someone might even (be able to) solve the problem upstream.

Re: XWayland Victory!
 

Hi,
I have ubuntu 18 installed on my XA2 plus.
about onboard
i would like to change layout because i have full keyboard activated.
with onboard settings when i change it it doesn't work.
how to change the layout with terminal? command line

Re: XWayland Victory!
 

Editing onboard layouts is actually quite complicated.

If you go to /usr/share/onboard/layouts you'll find two files for each layout. One is an svg file that defines the sizes, positions and shapes of the keys, the other one is an xml file that defines what the keys do.

An svg file will contain a bunch of key-shaped forms that have (mostly) four-letter names which I will call "key IDs".
I managed to edit these svg files with inkscape. However while I was able to create new keys and I think I also named them correctly, I was not able to link these keys to key definitions in the xml file. But that might be just due to me not being familiar with inkscape.

One xml file may be vaild for multiple svg files.
There are <panel> tags in the xml file which define which svg file to use.
Inside these <panel> tags there are <key> tags that define individual keys.
The keys of an xml and an svg file are connected via onboard's key IDs.
Which key a key ID actually produces is defined in a <keyboard> tag that links onboard's key IDs with the system's keycodes. This key definition is by default included from another file called key_defs.xml
onboard keys are by default labeled with the character that is associated with the keycode, which is linked to the key ID. However, this label can be replaced with another label by supplying a label= value in the <key> tag and/or with a graphic by supplying n image= value.

I suggest you copy an example svg/xml pair that includes a superset(!) of the keys you need to your home directory (default would be ~/.local/share/onboard/layouts ) and edit this one.
Then you can easily load this custom layout from onboard's settings dialogue.

Re: XWayland Victory!
 

How did you run it rotated? I was not able to rotate it on my nexus 5.

Re: XWayland Victory!
 

any news for 3.2.1? would be nice to have it on tama and x10 devices!

Re: XWayland Victory!
 

Official 3.2.1.20 support for Xperia !0 is there, see Jolla shop

A community port for Tama devices ist also available, thanks to rinigus et al., see: SFOS 3.2.1 for Tama devices - community port and SFOS for Sony Tama devices

Re: XWayland Victory!
 

chroot is not possible on x10, because /sys/class/graphics is empty!
latest qxcompositor is for 3.2.0.12 and official x10 images are above...

Re: XWayland Victory!
 

If your kernel has support for it, you can try systemd-nspawn. Nspawn doesn't work with my old Nexus 4, so I can offer little advice.

This might be worth looking over:
https://github.com/stken2050/wayland-desktop-container

Re: XWayland Victory!
 

I have been playing with chroot on the Pro¹ lately, extremely happy with it. Even my N900 never felt so close to an actual pocketable computer. I typed this post and uploaded images using the Pro¹.

cmus (not affected by SFOS volume, but it has its own volume settings anyway):

https://reho.st/https://0x0.st/zRJA.jpg

cmus and nnn file manager side by side, I really appreciate tiling since SFOS does not allow that:

https://reho.st/https://0x0.st/zRJT.jpg

And an additional tile for another tool:

https://reho.st/https://0x0.st/zRJN.jpg

Some random programs in different terminals in Tilix and the sidebar showing current sessions toggled on:

https://reho.st/https://0x0.st/zRJK.jpg

Neomutt:

https://reho.st/https://0x0.st/zRJ8.jpg

Tilix can be run in its own window without xfce4 and other processes in the bacground, as shown here with two tiles with micro and some nice cli-tools (the 0x0 script works in SFOS shell too by the way):

https://reho.st/https://0x0.st/zRJo.jpg

Same, seen from the home screen:

https://reho.st/https://0x0.st/zRJi.jpg

xfce4 multitasking:

https://reho.st/0x0.st/zRJs.jpg

In the end I mostly use chroot with xfce4 because the multitasking between terminal and full fledged web browser is great, and Tilix can be toggled to full screen anyway, which looks even better than when run as a standalone SFOS window:

https://reho.st/0x0.st/zR4C.jpg

Re: XWayland Victory!
 

I would like to do it on my Nexus 5 but not sure how to start.
I have tried to setup a chroot but I just messed up my Sailfish and couldn't boot into it anymore. I needed to reinstall it, so I am not so brave to start again now.

Can you recommend a bulletproof or close method to install a chroot then a distro on my Nexus 5, please?

Re: XWayland Victory!
 

I merely followed elros34's instructions on his sailfish_ubu_chroot Github repository. However, I would be interested in other distributions too (mainly Manjaro), as well as other DEs.

Re: XWayland Victory!
 

thx, it is working with the newer release on tama!

Re: XWayland Victory!
 

Can you let me know the url for that, please? Thx

Re: XWayland Victory!
 

Re: XWayland Victory!
 

Thank you. I will jump into it again on a separate rom, don't want to lose my current one again.

Re: XWayland Victory!
 

It's been so long i did not use my nexus 5. Last time i checked this chroot could not be rotated and sailfish also could not connect to monitor. Is slimport enabled and working on nexus 5 sailfish os port?

Can we rotate chroot on nexus 5?

I would like to have full desktop linux experience on phone. It's 2020 already and i still have not experienced this. There is other project too postmarket os which runs the newest linux kernel on nexus 5 with alphine linux natively without android drivers, but it also can't connect to monitor using slimport on nexus 5.

Re: XWayland Victory!
 

I don't mind if it cannot connect to a big screen as I have built a kind of laptop at home from my smartphone. What I done was I took out everything from a laptop shell but kept the screen. Purchased a controller (vga + hdmi) to the screen, a usb vga adapter for screen mirroring and a usb hub for the keyboard and mouse. Then I squeezed everything into the laptop shell including a wireless charging (only the thin coil without its house) + a keyboard from an old 10" tablet.
Then I can plug the screen into the main (or a battery pack with 12V / 3Amp output), connect the usb hub to the phone (S7) and slide the phone into the shell onto the wireless charger. And voila, my phone is my laptop and my laptop is my phone. I don't need big screen or whatsoever.
I even got the MS Visual Studio Code installed and ran on the full ubuntu 18.04. :D
I have done this about two years ago but the concept still works, but collecting dust on the shelf.
The only downside was: on my S7 I could only run Linux on top of Android in a chroot (with the Linux Deploy app) and there were a few limitation:

• no 3d acceleration as I had to connect to the chroot with VNC
• I could not make cups working with my network printer (probably this was kernel related as I got it working on my Galaxy S2 with a similar setup, but the S2 was much slower and it had other limitations)
• on newer Android roms I lost sudo (root only worked if I sshd into the chroot as root)

So finally I abandoned the project and started looking for something native. Then I found UT why I purchased my Nexus 5. Then because I didn't like UT I ended up with Sailfish and I love it. Unfortunately PM doesn't install anymore in multirom, so cannot try. (I have tried it on my Galaxy S2, but that is far from the one for the Nexus 5.)

It would be cool to use this custom laptop shell with the Nexus 5 but I think the main issue would be the slip port. (On the S7 I needed to install an Adroid app be able to mirror the screen to the usb vga adapter, but obviously this won't work on Sailfish.)

Re: XWayland Victory!
 

I don't have video out on the Pro¹ either, although the hardware should be there (through USB-C). I heard that elros34 managed to have video output on a SFOS port on the Photon Q, so there is hope and it may already work for some devices, but don't know who has the motivation and skills to work on that on the Pro¹.

sailfish_ubu_chroot with xfce4 does not rotate either; or it does, but it will just fill the top part of the screen and will be cropped on the right due to non-matching ratios. This is a non-issue on the Pro¹ though, since I only use Ubu chroot with the keyboard open (I almost never have to touch the screen with it, I mapped everything I need to custom keybindings). However I remember seeing a post by n950 here in this thread that showed chroot and a desktop environment in portrait mode. I don't remember which device he was using or how he did it, but I believe n950 is still an active user here. [Edit] Or maybe that was Jakibaki?

Performance on the Pro¹ is nice, but I don't know how it would be on older devices. I remember Easydebian was a bit too slow on the N900, and I haven't really tried chrooting with devices whose performance was somewhere between the N900 and the Pro¹. I did on my Jolla C and I think it was acceptable, but I barely used it due to the lack of hardware keyboard, so can't really say.

Re: XWayland Victory!
 

I followed the instruction on the github.
When I finally ran the: 'ubu-start.sh xfce4',
I got: 'Invoker: died: could not locate program "qxcompositor" to launch.

Re: XWayland Victory!
 

Are you sure the installation of qxcompositor was successful? You need to run ./ubu-install.sh as devel-su.

Re: XWayland Victory!
 

Yep, I know, otherwise I get an error saying something like: "run me as root" :)
I will retry.

Wow! It works!!! :D
There is no keyboard so am not sure how I can type anything. But it is cool! It started in landscape. Oh my, now I won't sleep too much tonight. :D

Re: XWayland Victory!
 

Yesterday I got this working. The missing qxcompositor package was the issue.
I have a few questions for someone who can answer :):

• How can I get an onscreen keyboard?
• Can I start in portrait mode at the top half of the screen while I am using the keyboard at the bottom?
• If I can, will the whole screen be squeezed into a portrait wide window or it will be with full width and I need to scroll if I need to access the right part of it? (I prefer the latter as the screen remains viewable.)
• How can I right click? (I do not use any hw mouse or keyboard.)
• Sometimes is it really slow, or this is only on my device for a reason? (How this opens up the programs is sometimes slower than a Debian Jessie installed into a chroot with LinuxDeploy on my Galaxy S2-i9100.)

Thanks.

Re: XWayland Victory!
 

I am using it with a device with a hardware keyboard, never played much with it with my previous non-hwkb device, precisely because it felt too limiting. However, if you are still interested, I guess you could try installing Onboard in XFCE, and placing an icon in the task bar to access it easily, or maybe it can even pop-up automatically when you place the cursor in a text field, I am not sure.

Portrait mode is possible because I saw pictures of it in this very thread (see my message above), but I don't know how to do it. I recommend you send a PM to the person who posted the screenshot, or ask directly to Elros34 or Preflex.

It should fill the whole screen if you achieve the same result as what was shown in the screenshot.

I haven't found how to right click in XFCE. I can work around this because I have a hardware keyboard and can Alt+F to open the file menu in all applications, but it is not ideal. I suppose right click emulation (with long press) is possible in other DEs, but I failed to find how to do it in XFCE. Please do share here if you find anything.

It is not slow on the Pro¹, so probably just a hardware limitation with your device. CPU or RAM, or even disk speed. Mosen has been running benchmarks on the Pro¹, maybe he can comment in more details.

Re: XWayland Victory!
 

No idea how to get the keyboard installed, without a keyboard, but i used xvkbd via apt-get to type @ since it is missing in my 3rd-level-less hwkbd layout.

On Performance, the Nexus 5 is roughly 4 times slower in storage access than the Pro¹.
Nexus 5 is 4.7Mb/sec read speed and Pro¹ whooping 18.73Mb/sec according to sysbench.
Jolla Phone was only 1.14Mb/sec.

Memory speed is only a bit faster on Pro¹:
Pro¹ 403.3 Mb/sec
Nexus 5 375.23 Mb/sec
Jolla 1 195.15 Mb/sec

Calculating prime numbers up to 2000 with two cores:
Pro¹ 3.77sec
Nexus 5 5sec
Jolla Phone 9sec

Now half that time for nexus 5 with quad core and 1/4 the time for Pro¹ with octacore should give a rough idea why xfce lags on Nexus 5.

Re: XWayland Victory!
 

Someone could actually carry back the code that I wrote for Flatpak support. In particular, support for change in orientation and Sailfish keyboard.

For Sailfish keyboard, chroot environment needs https://github.com/sailfishos-flatpa.../input-context as a plugin inside chroot. For build scripts, see https://github.com/sailfishos-flatpa...-maliit-plugin as an example. In addition, the host (qxcompositor in your case), will need to provide orientation info to the keyboard as well. This is done via DBus P2P connection as described in https://github.com/sailfishos-flatpa...ainerstate.cpp . On start of chroot, corresponding environment variable (FLATPAK_MALIIT_CONTAINER_DBUS) needs to be communicated to chroot, so the keyboard would be able to change the orientation as needed. Its all bit tricky, but doable. Current limitation - works for Qt apps only. Feel free to extend it to Gtk - I will be happy to adopt that later :)

For orientation, its way easier. Its mainly small changes in qmlcompositor and QML. don't remember exactly what, but code is small and it should be easy to find again.

I will better work on other things, but wanted to let you know about that option

Re: XWayland Victory!
 

i have a problem with option menues in apps. even when the app is rendere ok, the buttons and dropdowns in settings menu are way to large, so most of the settings are out of the screen and not reachable. i am not sure, if this is because of missing style in sfos or wrong dpi setting, may be it is only a missing environment variable?