Dear UBports team!

As you may know there is a messenger app in the Store called LoquiIM. It's an HTML5 app and was created by FirefoxOS app developers years ago to provide a all around messenger app including WhatsApp. This app is the only full GUI app to make the use of WhatsApp possible on FirefoxOS and Ubuntu Touch. To keep this up, the Loqui team needs your help. It would be a pitty, if this long project died out. We're looking forward to switch over to an Android based client. That is in the far future. Currently we emulate an S40, whose support of WhatsApp has been extended until end of 2018 some weeks ago. But this is not a surviving solution. So if someone has some experience with the WhatsApp technologies and wants to help refreshing this app, also into GUI functionallity direction, feel free to contribute on the project's Github page. Join our Telegram group.

Thanks in advice and keep up your great work here!
nfsprodriver

Hi!
My name is Bjarne alias nfsprodriver. Before UT came onto the market with the bq e4.5 I was fascinated in this OS. Since the e4.5 I use and love UbuntuTouch. Because of the knowledge of FirefoxOS running WhatsApp via the webapp LoquiIm, I started the work to port it to UbuntuTouch and got some great help and supporters - partly from here ;-). Anyway, now I'm on Nexus 5 with UT and test it and some different cool projects. I hope I can give a part of work into this great community!

@Bastos Generally external media should be mounted in /media/phablet/YOUR_MEDIA

Cordova works worse with files from my point of experience. It's also a pitty, if you'd need such a rewrite of the html5 app. So there's a need to procreed oxide-qt or an implentation of a routine which makes a barrierfree handle with files possible.

On N5 I recognized: Installing System updates seem to cause the reinstallation of the native kernel. This causes a disfunctionallity of anbox and heating of your device (100% CPU). I recommend to disable automatic System updates.

The vibrator actor has a weird behaviour. In the most apps it vibrates once after startup without respect of the sound settings. It also seems WayDroid to make the startup stuck.

@flohack Oh, there is a difference for the fp readers? Didn't know that. It's working on my OP 5 non T

Worked like a charm, thanks so much!

@lakotaubp Oooh, didn't know it's available via apt. Thanks for the link, marked it as bookmark. So let's see...

@lakotaubp May I ask, how you installed it?

Yepp OP5, I installed python3-gbinder, fixed a json issue in the images.py file and I could init it, but now some services are missing.

How can I install waydroid ATM? Currently failing with the OpenStore app and the python script on the ubports/xenial branch.

@flohack I see your point. I'll try on with manual flashing and reporting the current state of functionallity here.
Anyway, did you have a look on the merge request in the kernel repo? This is also for the old anbox, which is basically running with this.

Is it possible to merge the anbox-halium patches soon? It would be easier to test the latest Waydroid status without the need to flash the self built kernel after a daily devel update. Or are there negative side effects with these patches like power consumption?
Every time I tried to use Waydroid it didn't boot up because of vibrator issues. Is this something to be fixed before the merge?

@flohack Oh, there is a difference for the fp readers? Didn't know that. It's working on my OP 5 non T

Fingerprint reader seems to work now with the latest sensorfw changes in the devel channel (auto brightness also fixed).

Well, it's difficult to describe. I have disabled additional vibrations in the sound settings. But about in every app, there's one vibration per session after I tap on a UI element. My thinking is that this behaviour is related to the missdetection in WayDroid.
I'll try to collect some helpful logs these days to find out, where the issue has its origin.
But yes, the vibration actor itself works and is basically interacting with UT.
Anyone else can confirm my described behaviour?