@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

Great. It works.

@wgarcia you're welcome!

@dzd1 hi, there's some work in progress to make available the Korean keyboard layout. IIRC the issue is that the layout exists but it isn't showing in Settings.

Success!!! I finally solved my problem with the vcf sharing approach. Once again many thanks to all you Ubuntu Touchers for your help and patience. Now to bed!

@gt for uMastonauts, @Krille needs to move the app to QtWebEngine but it seems he's having some trouble with that, and for Duolingo the xenial version has not been tested yet as you can see in https://open-store.io/app/duolingo.aitzol76 (I'll ping him in the Spanish group).

Guys we are finally trying to fix this: https://github.com/ubports/docs.ubports.com/pull/138 BR

@doniks Will remember that trick. It had begun to stop rotation on android before I put it away. Lets see how it goes. Yes mine is a flo.

@guru : is this information of any help?: https://github.com/ubports/ubuntu-touch/issues/223

@ellypsis IIRC some users tried that road before but it didn't work, but of course YMMV so sudo mount -o remount,rw /

@advocatux I know it isn't software as OTA4 is working like a charm on my main phone which is a BQ 4.5. This one is running OTA4 as well. The one thing I can think is that I took it cycling with me and I got quite wet, although it was in my pocket. Though I have done that a few times. The phone is working, but the screen is blue tinged with graphic lines through it and eventually stops being responsive. It gets hot on the front just above the micro usb charger. It was second hand, so might have had issues anyway and I can't vouch for the battery. I have had the back off and looked at the area where it gets hot, but can't see anything obvious. It seems to be related to the screen driver, but not sure what is getting so hot. The battery connector is near that point.

Thanks for putting up this link. I have stored it safely , just in case.

https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461 unlock bootloader only windows 7

I was about to post a reply to this post, but I found this bug on GitHub : Mobile data usage monitoring #66 Just to let other know that's a work in progress