Moar Pebbles, moar problems!
My Steel works really well with UT and Rockwork these days. Now a new friend came to my door today: a Pebble Time Steel. I would love to use both Pebbles alternatingly, depending on my plans for the day.
But Rockwork sees only the Steel, connected or not, and does not offer a way to connect a second Pebble. I can connect the Pebble to the bluetooth of the phone just fine, but I can't use Rockwork to interact with it.

Ideally I want Rock work to show two Pebbles, and connect to the one that I'm wearing that day. As a workaround, a separate instance of Rockwork with its own settings might also be an option.
Does anyone have any ideas about whether this is possible, and if so, how?

@kugiigi I have 4 webapps open at the same time on the BQ E5 HD, and nothing is killed ! 😉
I put the link of the thread on the Volla open issue but your interesting ideas and leads might be useful to submit directly even if you don't own a Volla.

I can confirm the same issue.

Given the nexus 7 allows similar experience than the nexus 5 (full convergence performance with hdmi support) I think it will be beneficial for the core team to give it a go solving this one so this tablet can be listed as recommended device.

Its cheap to buy and performs really well.

My 2 cents.

@prog-amateur All I can rember when I had the issue was that it was the second part of the url that I had wrong for my Generic CalDAV which is lakotaubp@-----------mail.com@------.thegood.cloud/caldev/ same for my Nextcloud but without /caldav/ at the end.
I also kept putting a capital letter at the start of a password or email address which also got the error you are.

@marc123454321 Ah if anyone try to do the same. After connecting i got a subnet mask of 255.255.255.255 on tun0 for unknown reasons and therefore cant reach any other ips. Just changed it.

Marc

@keneda You don't give the impression of a dumb user. On the contrary, an cool hacker, who is correcting runtime code in the RAM directly with hexeditor... at least, that is my impression. 😉

@markatrafik

If I get your point of view, as long as AOSP is open sourced there is no risk.
The interface with the drivers and any binding with the hardware can be integrated within UT.

A port has to know which android version was previously installed in order to assess correctly how to access the drivers.
If a driver is not in the right version than there is a risk the API changed and induced bugs...

Thanks, I am reassured. I had not realised there were applications I could not uninstall using Open Store.

@matteo my sincerest appologies for the delay in responding. I am slammed with work at the moment but plan to respon asap. I also saw your new version of the app you want tested in the QA telegram chat. I will install and send feed back soon. Appreciate your patience and all your work on this great app!

@applee
At least I can export the dictionary as text file..

@arubislander thank you for information

Thnx I was looking for manual

Hi and welcom @paul_h
What are the websites you're trying to reach from Morph ?

Is it possible that uAdBlock is blocking those sites ?
You can try and ping the destination to see if the DNS find the destination and if you can ping it from your device.

Hi All,
I follow Pine64 forum and i found quite interesting topic regarding mobian and MMS issues. One of the users developed script to retrieve not delivered MMS. If i remember correctly Mobian use ofono as well so maybe that's something that could be useful for us too.

https://forum.pine64.org/showthread.php?tid=11994

@jcmarvillet
My advice, don't rely on a company to maintain something for us (Ubuntu Touch users).
What I would do:

manually export my calendar from google import it into a nexcloud account then sync nextcloud with UT

Nextcloud will remain and if you're using service by some company and not your own instance then don't forget to backup your data 😉

Nextcloud will be maintained as Google may decide to block any third party... They are already pushing in this direction.

Hi.
Thanks a bunch. I pushed power+vol up but then the tablet started rebooting over and over. Finally I got it stopped and kicked it into fastboot mode. Third time the installer found the device and now the problem seems solved... Thanks again all of you 😉

This has been discussed on the telegram group and someone suggested a workaround while the issue still exists.

vlladdrakk on telegram:
So I took a look at that code, though I don't know c++ well, but it looks like it is a case sensitivity issue. The detected name is "pine64 pinephone (1.2)" but the name in pinephone.yaml is "Pine64 PinePhone (1.2)" I edited /etc/deviceinfo/devices/pinephone.yaml to match the case of the detected name and device info is now showing the correct device information. It is odd since the detected name is purposely lowercased here: https://gitlab.com/ubports/core/deviceinfo/-/blob/main/src/config.cpp#L65 and that change was from a long time ago, so I'm not sure why it is causing a problem now and not before. Someone else may already be fixing the problem