@lakota Thanks.

@matridium At least your up and running so who cares how ; ) I've seen acouple of times where it seems to stop then you suddenly find all is OK second time around. Have a look at https://ubports.com/page/telegram-welcome for some usfull info to get you started and welcome to and enjoy UBports.

@advocatux, Many thanks for the link. It looks like we still have to wait some time before we can take pictures with the selfie stick. In other words - be patient

@635834 said in Notes app on OnePlusOne mobile phone (OS ubuntu): Surely when I get a reminder I should get a buzz and a permanent visual reminder (which I would have to delete)? Hi, that's how reminders should work for sure. Unfortunately I don't know if it's an easy fix because AFAIK there's no Notes app maintainer currently. I'll forward your suggestion to those I think (maybe) can help to solve the problem.

@guru Agreed. I did save the original hosts file so it would be easy to restore the file and set the filesystem to read-only before doing an OTA. But that too isn't a guarantee, I realise it's a bit of a gamble.

@frapie can you run adb? is adb set in your PATH?

I'm pretty sure that the installer does not touch the partition layout. Remember Android is weird. I wouldn't be surprised if some devices/bootloaders have specific expectations about the partition layout these are embedded devices. If the bootprocess is severly messed up, you can't exactly put the hard disk into that other device and fix the partitions So, while I guess it is possible to make cache smaller, I am not gonna try on my device and I'd caution you to do so! Now to the aspect of "I'm running out of space" due to tinkering with libertine, ... well you still have some 6GB to through around, not huge, but not nothing either. If you run out of space, rather than doing acrobatics with partition sizes you want to look into acrobatics with bind mounting

You could try and if it works document it here https://docs.ubports.com/en/latest/userguide/dailyuse/libertine.html I'd also try first with a symlink, but if that gives any problems, I would assume a bind mount should work. but then you have the additional challenge of having to reestablish the mount after every reboot. maybe it can be automated with upstart.

@absurd great hope you get sorted quickly

Hey, I had the same problem (Nexus 5) and I think I know what is the cause for this problem. It is the same as @Bash-Horatio specified. The device has two identifiers: Google Android [0100] LGE Nexus 5[0232] Now, whenever the device is on fastboot it is identified as Google Android [0100] but when it moves to Recovery mode it is identified as LGE Nexus 5[0232]. Seems like the script is loosing the connection to Google Android [0100] right when the device is going to recovery mode. So, under VirtualBox you should go to Machine -> settings -> Ports -> USB. Check to "ON" the "Enable USB Controller" and "USB 1.1 (OHCI) Controller". On the right, there are small blue usb icons to add/remove usb filters. You should add two filters for each device identifier (i.e. Google Android [0100] and LGE Nexus 5[0232]). How? Connect the device when it is NOT in fasboot and add a usb filter (should be LGE Nexus 5[0232]). After having this filter switch your device to fastboot and then add a new filter (should be Google Android [0100]). Once you have two usb filters you can run the ubports. For non-VirtualBox I would say that you should disconnect / connect the device when ever your phone switched to Recovery Mode so the script will recognize the device with its new identifier (LGE Nexus 5[0232]). for me it worked fine after few hours of frustration... Hope it will help. A'aron

@costales I don't know the answer but I've linked your question in the OpenStore group (https://open-store.io/telegram).

Thanks. Now all working....

@lakota cool Nostromo btw

Itś strange, I have a OPO 64 and dont't have had any problem working on 15.04 or 16.04....Anyway I think could be much better to continue this converstation on it respective bug...Now a days I'm working on 16.04, if you want tell me steps to reproduce the bug...regards.

Just thought I would mention that I was eventually able to test out Hangouts video calling though the browser, and everything works, so a big thanks to all. I suspect a reboot did the trick.