Posts made by negations

@advocatux That did the trick. Should have realised. Thanks for the help.

@advocatux Thanks, I tried that but it is still there. I think it needs removing from something like the apt folder?

@advocatux The UT Tweak I have (0.4.17) doesn't seem to have that facility.

I set my BQ 4.5 channel back to stable to get OTA-10, which I now have. However, it had already downloaded a weekly RC release which is now at the top of the install window. Is there a way I can delete it? I have re-booted a few times, but it is still there. Not a massive deal, but it would be nice to make it disappear.

I am not a developer, though would help if I could, and this is a bit of a newbie question. At my workplace we use all Ubuntu devices for everyone, give or take, and a few use UT phones. Our main system runs on egroupware and the latest version uses rocket chat. Anyone know if there are plans to make an app for this or what it would take? Would this be an Anbox job?

@advocatux I hadn't, but it has just been triggered. Seems fine now

Re: Unable to read SIM contacts

The topic was old so it recommended a new topic. Since the last update, running rc on my N5, all of my contacts have disappeared and I get the message in this old post "Fail to read SIM card". I tried the recommendation in the other post to open a terminal and run initctl restart ofono and get the message that it has restarted, but contacts were still not showing. I then rebooted and it seems to be back to normal.

Posting here for reference really. If it happens again I will put in more details.

@uri I can load the site on my Nexus 5 and I run my own Nextcloud instance that works fine. Do you have a test login to try?

@advocatux Have to echo all of this. I have used my E4.5 for over 4 years now and the last year (I think) with UT. I have had little glitches here and there, but nothing to stop me doing my job. Everything I need on it works. End of.

@the_cougar_kid It has been a while now as I am on 16:04, but I used the linux installer to change my Ubuntu 4.5 to UBPorts 15:04 and it worked well. When I then moved to 16 it tried to keep all the apps and other settings and for the most part was fine.

@fishfingers44 I agree and with all other comments here. I am more than happy now with 3 devices running UT 16:04 and working very well. Each update is a bonus. Thanks to all the hard work from all involved.

@lakotaubp Just to close this, that did fix it.

@lakotaubp I'll give that a go. Should have thought of route one.

I have a BQ 4.5 running 16.04 OTA-5 (my main work phone) and a N5 running 16.04 OTA-5. If I plug the BQ in via USB to charge or get photos, it pops up a window on my Linux machine which I can close. The N5 pops up endless random windows continuously for several minutes.

Any idea how I can stop this or where to look?

@fishfingers44 I installed it by downloading the click package via the browser to downloads folder then selecting OpenStore to install it.

@rueding Hi Arne: I have the E4.5 and Dekko2 works for me (the beta 0.1.6 version I think). I had to carry out some of the suggestions from the forums here: clear cache, re-install, but it now works really well.

@tlf Maybe another boot to reset the new connection?

@tlf I was thinking of this: https://support.google.com/accounts/answer/6010255?hl=en

Enabling the "less secure apps" seemed to allow my N5 to connect to google with Dekko and it seems to work with the account as well. The phone might connect and be shown, but google is set not to allow less secure apps.

@tlf Ah, actually I was thinking about signing in with Dekko for email. Seems like an authentication issue? However, I just tried on my Nexus 5 phone and it worked straight away. Not sure why it is spinning for you. I have some google accounts on my BQ phone, but they were on it when it was 15:04 and upgraded when I moved it to 16:04. If I get a chance I will try on there and see.
It works on my E4.5, though as I said, that was upgraded from a 15:04 version, so not sure if that is significant.

@tlf I think the Google issue requires you to login to your Google account and allow unsafe devices as the p-hone is seen as unsafe. If I remember, that is what worked for me.