@lakotaubp Thank you for tips, I finally got it to come back on. After trying a bunch of things, what ended up working was plugging it in to my computer at work, I left it plugged in for a few hours, hit the power button and it showed the battery icon, almost fell out of my chair, held the button and it fired right up. Not sure why, but it's on and working again so I'm happy.

Ah! Okay. That makes sense then, @mic_ !

The negative tone starts at your post title ("a sad story") and then continues. What it's "a clear picture" for you, maybe other people see it just as a grumbling because you're using some adjectives that are not really necessary to describe a technical problem.

Anyway, it's way better to fill an issue, that's true.

For example, Logitech M535 works fine: https://www.logitech.com/de-de/product/bluetooth-mouse-m535?crid=7

If anything else fail, try to install with good old '' ubuntu-device-flash '' tool. It worked for me as a last stance, when everything else would just not work.

@cj_c Pleased to hear it. We have a good helpful community here.

@dobey this is also what I saw on the OpenStore !

I use Rudi timmers gmail app and it works well in Xenial.

regards....

@dobey hi ! this is what behavior I also expect ! I will try it soon. thanks!

I think it's time to debug and nail this down. I found the file /etc/init/wpasupplicant.conf which spawns the WPA daemon as:

exec /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

I will mount the /root in this test device writeable and change the line to:

exec /sbin/wpa_supplicant -dd -u -f /var/log/wpa_supplicant.log -O /run/wpa_supplicant

to gather the debugging output in a file.

Update:
It's not necessary to mount /root writable. The proc init starts and re spawns that proc when it dies. With a bit of luck you can fire up these three lines from a shell script and get your version of WPA up before init can restart its own:

#!/bin/sh pkill -9 -f '/sbin/wpa_supplicant.*' wpa_supplicant -dd -u -f /var/log/wpa_supplicant.log -B -O /run/wpa_supplicant exit

The lines in the log files look promising...

I can confirm that setting up a DavMail in server mode & using it as a caldav gateway to exchange works fine

I've tried it on an f-droid only version of Android without Exchange provider

Only tried caldav but no doubt the other gateways DavMail provides would work too

If it works on android, no reason why it wouldn't work for UBPorts

It'd be nice to have it on-device though, maybe DavMail could be repackaged in some way to provide the required Dav gateways to Exchange

I know it's java based though, so might be too heavy to run in the background on a mobile device

But it's a thought

That may be a clue. I will try to run UB ports on Ubuntu in Virtual machine.

I've done the following steps and it seems to work for me:

Charge the phone to 100% until there no charge indicator left Boot the phone to bootmenu (where you can select recovery, fastboot, etc.) Leave the phone in this bootmenu until the battery is empty (in my case this took 8-9 hours) Charge the phone until there is no charge indicator left

After these steps my E4.5 lasts almost as long as it was new and the percentage shown in the power-management shows the correct values again.
I hope this is a long-term solution.

@gucu No sorry your device is not supported this is the current list of supported devices https://devices.ubuntu-touch.io/ Due to the nature of Ubuntu Touch each device has to be ported separately and takes a lot of work and effort. There should be other device available later in the year but no clear time scale yet.

@matteo you can request support for Suru Dark in morphs issue tracker: https://github.com/ubports/morph-browser/issues
I think there is no issue for it yet.

@stefano yes it is definitely annoying. I'll keep an eye on it and this thread in case I see something similar to your bug and I will report to you. Honestly, I'm not using the Pro5 that hard to be a 100% sure my device isn't affected.

You could install such things in a libertine container instead.

However, there are no USB serial adapter drivers built into the kernels on the images, so I guess you might not get very far with pyserial yet. 🙂