Seems to be down again since days... this half-assed Matrix stuff is really not production ready.
I hope you will switch to Matterbridge soon. It's rock solid and hardly needs any server resources.
Seems to work well on my Nexus5. Thanks a lot for making this!
I am actually now considering if Ubuntu Touch wouldn't make for a nice in car entertainment and navigation system. I guess that should be very doable once the RasberryPi support (and GPS) matures a bit. Otherwise it seems to already tick all the boxes and should be easy to use in a car as well. Edit: maybe with KDEconnect you could even tether an Android phone to it to take hands-free calls?
@mito77 this isn't really a support thread, and in any case that sounds more like a upstream ConverseJS issue. But what is the actual limit you set? I think in XMPP each connected device is counted as a user, even if representing only three actual people. Maybe there is an issue that devices are recognized as new while the old ones need some time to time out? No idea, just guessing
@mito77 the wss and bosh address is saved in the app, just not displayed again in the form field.
However you need to put in again your JID and password each time. I have some ideas how to add an option to stay logged in, but doing so (with the option to also log out again) is a bit complicated.
Xep-0156 is supported in the new upstream version of ConverseJS. I need to get around updating my app to it.
By the way, if anyone wants to work on an offline and multi account client for Mastodon, Pinaforce would be a really good base: https://pinafore.social/
Hi everyone, I'm New on ubports, on android I use Conversation , but on Ubports I want to use xmpp client for Muc chatroom support like gajim on Debian . I try with converseJS but don't work because I can’t connect .
Hi @mito77 can you explain better what you mean with "can't connect"? What XMPP server are you using? If it is self-hosted, make sure it is up to date and configured to expose BOSH or websockets as alternative connection methodes. Due to the webapp nature of ConverseJS you can not connect with the regular 5222 port as Conversations/Gajim etc. does.
There are two ways to run UT. With Halium, which is a Android driver compatibility layer and is thus tied to the Kernel used in the Android release for that phone, usually 3.x but can be newer.
Or you can run it without Halium like the PinePhone or on a RasberryPI in which case you can use what ever Kernel is supported by that device.
Maybe try clearing the app settings and cache with uttweaktool?
@poVoq I cannot imagine Android would make any sense to boot since it probably cannot interface with any of the hardware onboard the Pinephone.
Why would that be the case? Android does run on the A64 development board and the early batches of the PinePhone even seem to have included a bootable but otherwise hardly functional Android version. In addition AFAIK most of the hardware is internally connected via the USB bus, thus standard Android drivers might work and already exist.
I am not saying that it will be super easy, but I looks like a far from impossible task especially if you are for example willing to run without the cellular modem in order to just use you Android banking app over WiFi or something like that.
P.s. no I am not planning to port Android to the Pinephone
I agree that the dual boot to Android option should be probably advertised to hedge with people unsure if they want to make the leap.
I am guessing, but it seems likely that you can already dual boot by swapping in a SD card with another system image and images for the Pine A64 should be reasonably close to get at least WiFi connectivity (cellular modem might be another story). For the A64 there are Android7 images: https://wiki.pine64.org/index.php/SOPINE_Software_Release