Hi @rueding, There's a couple of Nextcloud apps, if that's any help... https://open-store.io/?sort=relevance&search=Nextcloud I can also sync between my phone and my Nextcloud calendar: Accounts has CalDAV, as well as Nextcloud and ownCloud...

it works Thank you

@fishfingers44 generally speaking, all the up to date clicks are in https://open-store.io/ Speaking about Dekko specifically, as it's under heavy development, you need to follow the releases in its repo (https://gitlab.com/dekkan/dekko/tags/) for now

Managed to find a workaround. If you restart ofono (sudo initctl restart ofono), the import suddenly starts working. The drawback is that your phone goes offline and you will have to restart to get it back online. The pattern seems to be, that if your SIM is offline, import works. My 2nd SIM is blocked, therefore it stood offline and the import worked on the first try. Unfortunately, switching to flight mode doesn't work, because it simulates a modem with no SIM card.

@stefano If I try browser next for maps.google.com, the browser doesn't access the gps... But the page doesn't crash - that is promissing.

I was trying to move a folder from PC (kde neon)to my phablet after updating to ver 170 , I got the,could not write to device message, so I turned on developer mode,and it worked. I usually move items to the downloads folder on phablet,thats when I realized there was not one. I ran the update to ver 172 and looked for the downloads folder, it was not there ( no wipe ). I then made a downloads folder, so a screen shot shows different date on that folder. So a terminal readout is correct,but I made that folder. I am using " skyneels Nvram flashable fix" and reflashing twrp periodcaly,to get away from Wifi,problems. Just trying to see if something slipped thru, I don't think its worth going to github for, seemed strange tho.

@advocatux thanks, worked. One comment for those who are doing the same thing: don't forget to enable developer mode once you have installed the legacy Ubuntu Touch. Otherwise UBports installer won't detect your device.

To support ratings/reviews, the code for the server that was used for the old store from Canonical, for this purpose, is I think Open Source, but it would require getting that set up and running somewhere under open-store.io, and then updating the client side to support it. It's a fairly simple API, and there's already code in unity-scope-click which supports the old service.

There is a beta test build for ppl with problems, please try https://github.com/ubports/telegram-app/releases/tag/v2.5.5

I made a test build here: https://github.com/ubports/telegram-app/releases/tag/v2.5.5 - Can you please try with this one?

@truscellino Yes, it's still happening for me. Tapping the network name again doesn't help the situation. Surprisingly, turning WiFi off and on again doesn't help either (I would have expected this to work). The only solution is to turn airplane mode on and off again or to reboot the phone. I recently changed the channel my router uses and it had no effect on this issue. Good luck with your investigations. I have only one router and no convenient way to test others.

please in future can you remove any text etc.you no longer want when editing posts @advocatux @Lakotaubp Ok, I'll do that next time @advocatux said in Description of new updates: In short, no, there isn't official changelogs as such. Ok, clear. Thanks

@Lakotaubp Yes, thank you. Ok, the single update that doesn't want getting installed isn't such a big Problem and I thought with 16.04. there were some issues - but yes, you're right. In this case moving to 16.04. seems to be a good option. So I will give it a try :-). Thanks.... Michael

@advocatux Thanks, it's working now.

@domubpkm yes, browser-ng is usable (sort of) in xenial rc, and almost completely broken in devel. The fix is already done and we just need to wait for all the pieces to fit in place

@lakotaubp thank you, I've updated the title to show that I am running 16.04 stable. Here are the log files in .cache/upstart as suggested. Which ones are relevant to this issue? I'll upload them to pastebin address-book-service.log.1.gz address-book-service.log.2.gz address-book-updater.log.1.gz address-book-updater.log.2.gz application-click-com.ubuntu.terminal_terminal_0.9.0.log application-click-com.ubuntu.terminal_terminal_0.9.0.log.1.gz application-click-logviewer.neothethird_logviewer_2.1.log application-failed.log.1.gz bluez-mpris-proxy.log.1.gz bluez-mpris-proxy.log.2.gz ciborium.log.1.gz ciborium.log.2.gz click-user-hooks.log.1.gz click-user-hooks.log.2.gz dbus.log dbus.log.1.gz dbus.log.2.gz dbus.log.3.gz dekkod-notify.log dekkod-notify.log.1.gz dekkod-notify.log.2.gz gnome-keyring.log.1.gz gnome-keyring.log.2.gz indicator-datetime.log.1.gz indicator-datetime.log.2.gz indicator-keyboard.log.1.gz indicator-keyboard.log.2.gz indicator-network.log indicator-network.log.1.gz indicator-network.log.2.gz indicator-network.log.3.gz indicator-network-secret-agent.log.1.gz indicator-sound.log maliit-server.log.1.gz maliit-server.log.2.gz maliit-server.log.3.gz media-hub.log media-hub.log.1.gz media-hub.log.2.gz media-hub.log.3.gz mediascanner-2.0.log.1.gz mediascanner-2.0.log.2.gz mediascanner-2.0.log.3.gz msyncd.log msyncd.log.1.gz msyncd.log.2.gz msyncd.log.3.gz mtp-server.log.1.gz mtp-server.log.2.gz nuntium.log nuntium.log.1.gz nuntium.log.2.gz nuntium.log.3.gz ofono-setup.log.1.gz ofono-setup.log.2.gz pulseaudio-trust-stored.log.1.gz pulseaudio-trust-stored.log.2.gz scope-registry.log scope-registry.log.1.gz scope-registry.log.2.gz scope-registry.log.3.gz session-migration.log.1.gz ssh-agent.log.1.gz ssh-agent.log.2.gz sync-monitor.log sync-monitor.log.1.gz sync-monitor.log.2.gz sync-monitor.log.3.gz telephony-service-indicator.log telephony-service-indicator.log.1.gz telephony-service-indicator.log.2.gz tone-generator.log tone-generator.log.1.gz tone-generator.log.2.gz ubuntu-location-service-trust-stored.log.1.gz ubuntu-location-service-trust-stored.log.2.gz ubuntu-push-client.log ubuntu-push-client.log.1.gz ubuntu-push-client.log.2.gz ubuntu-push-client.log.3.gz unity8-dash.log unity8-dash.log.1.gz unity8-dash.log.2.gz unity8-dash.log.3.gz unity8.log unity8.log.1.gz unity8.log.2.gz unity8.log.3.gz untrusted-helper-type-end-push-helper.log.1.gz url-dispatcher.log usensord.log.1.gz usensord.log.2.gz Here is /var/log/syslog https://www.dropbox.com/s/ug0632bcv34hepr/syslog.crash?dl=0 I will leave this file shared for as long as possible.

I've downloaded the file ubports-installer-0.1.21-beta.freebsd and can have a look into it with $ xz -dc ubports-installer-0.1.21-beta.freebsd | tar tf - +COMPACT_MANIFEST +MANIFEST /opt/ubports-installer/LICENSE.electron.txt /opt/ubports-installer/LICENSES.chromium.html /opt/ubports-installer/blink_image_resources_200_percent.pak /opt/ubports-installer/content_resources_200_percent.pak ... How is this to be installed and used on FreeBSD? I tried to rename the archive to the normal file name for FreeBSD packages, integrated it in my repository and tried to install it, which gives: # mv ubports-installer-0.1.21-beta.freebsd /usr/local/PKGDIR.20170304/ubports-installer-0.1.21-beta.txz # pkg repo /usr/local/PKGDIR.20170304 pkg -R /usr/local/etc/pkg/repos/ install ubports-installer Updating FreeBSD repository catalogue... meta.txz : 100% 264 B 0.3kB/s 00:01 packagesite.txz : 100% 418 KiB 428.5kB/s 00:01 Processing entries: 88% pkg: wrong architecture: linux:4:x86:64 instead of FreeBSD:12:amd64 pkg: repository FreeBSD contains packages with wrong ABI: linux:4:x86:64 Processing entries: 100% Unable to update repository FreeBSD Error updating repositories! Can the dev who created this archive please contact me? Thanks.

@vincitygialam hi & welcome You can join us in our Telegram (https://ubports.com/telegram-welcome) & Matrix groups too (#ubports:matrix.org is a good place to start). Edit: also you can introduce yourself here if you want

@thebird said in Working bluetooth on devices: If you have a positive Bluetooth story, please tell it in this thread. I bought an JBL Go bluetooth speaker. With my bq E5 sound through bluetooth did not work. The phone connected, but the play button did not work. All sounds stopped working. Could not switch off bluetooth and even restart the phone. Had to do hard reset (volume+power combo). So I used the speaker with jack-jack cable. Then I smashed my screen and was forced to buy a new phone. So I installed ubports on my new FP2 and tried to connect the speaker via bluetooth and ... wait for it ... it did not work again. The same troubles. But, and this is why this is a positive story, my brother bought himself a JBL Clip 2 and. .. yay ... it worked with both of my phones. So I traded the speakers with my brother and now everybody has a working bt speaker (brother is iPhone positive).

@rickigonzalez https://gitlab.com/dekkan/dekko/tags/0.1.6-beta1 Try this version of dekko2 it does work.Any issues read through https://forums.ubports.com/topic/1477/dekko2-developer-community-thread/76