@dobey
Ok, thanks. Then I'll have to wait 'til someone fixes this.

@Reload Hi,
You mean that the volume is lowered on its self ???
Or do you want a feature to prevent accidental modification of the volume setting ?

The volume can be set at any time (even phone locked), so accidental modification is possible.
I don't have this issue thanks to a phone case protecting the buttons.

And personally I like to be able to adjust the volume whenever I want.
But I guess this should be considered.

But I'm afraid that if accepted it won't be a priority except if someone steps in and propose a PR.

@mihael no, this probably won't change much.

@AppLee said in swipe to go back:

Maybe a poll can be done if other back your ideas

In my opinion polls can raise false expectations. Unless the community is being consulted on a concrete choice with concrete implementation plans, it might be best not to hold them.

Yes, correct, Linphone should work, but needs a SIP account. Wifi calling enables automatic handover of calls (incoming/outcoming) though any wifi network (when mobile provider offers this features, which is mostly the case now). This is particulary advantageous to call from abroad (no roaming fees), as well as in case of poor coverage signal.

The post at 13 Jan 2020, 23:29 suggests it is possibe to show different blink patterns (but ofcourse all white). It would be interesting to find out how to trigger these different modes.

As for disabling the charging- or message received indication what would be the best way? A menu in the system settings? A config file in phablets home dir?

The led notifications are guarded by a unity8. How can unity8 detect what phone/hardware it is running on?

-Edit-

I have been working on a way to disable showing charging state.
See https://github.com/ubports/unity8/pull/283

@makeixo These devices are not yet available for the regular stable/rc/devel channels, and only have edge channel builds currently.

@Flohack thank you very much for your answer

@Fla that pull request is in dev as of last night and should be in rc for next week. Well before OTA12.

@kugiigi Okay, I passed on the info.

We've received testing that confirmed the worst, this causes problems setting up the data connection on the Pro 5. Both SIMs return to 2G when it is installed. Thanks to everyone who helped!

Happy to help ! 👍

@dR0W Ok. It seems like Pulseaudio is unable to enable "voice call mode" on your BT headset for some reason. To help investigate this, please follow this:

Disconnect the headset if connected. Run echo 'exec pulseaudio --start -vv --log-target=syslog' >~/.config/upstart/pulseaudio.override to enable additional logging on Pulseaudio. Run initctl stop pulseaudio then initctl start pulseaudio. Note that restarting it won't take the settings above into effect. Now, connect your headset, then have a call. Send me the file /var/log/syslog. I'm not sure if it contains sensitive information or not, so you can PM me if you want. After testing, remove the config file by rm ~/.config/upstart/pulseaudio.override

Also, if possible, could you please retry this with the old version of Pulseaudio?

AVM is already offering comparable media phones - which can play regional and internet radio stations and also videos from a harddisk which is connected to the router. But at least the AVM phones are not a bit so powerfull than UT already is (no bluetooth e.g.).

https://en.avm.de/products/fritzfon/fritzfon-c6/technical-specifications/

https://en.avm.de/news/the-latest-news-from-fritz/2019/new-fritz-clip-the-fritzbox-as-a-media-server/

See left side of this board: https://github.com/orgs/ubports/projects/15 - All critical devel bugs must be fixed before we make a new RC

@Flohack Regarding the user-data folder, it took at least 30-35 minutes to backup 12Go (including compression) over usb2.0, and nearly the same (a little faster) to restore (arround 20 minutes).

The system-data folder was smaller then it take less than 5 minutes to backup (and 3 more to restore).

I was thinking about doing it on the SD at the beginning but as my data partition was about 54Go, I was scared that my 32Go SD card wasn't sufficient (as I already had a lot of things on my SD like all the pictures taken by the camera, they are very big on te Pro5 because of the sensor quality).
And one other thing was that my sdcard wasn't mounted on recovery, I think that the recovery-turbo.img miss a lot of features.

For the phone where the system-data and user-data are correctly mounted on the /data folder in recovery, this script can work well if you remove the line "adb shell mount /dev/block/sda44 /data"

But if you want to do that locally on the SD card, if it is mounted, you can do that on the recovery nearly the same way, don't forget to use tar as it will take care of the symlinks (not to ignore them, it will save them too).

It will be very perfect if that can be integrated to the installer !

@vandys
For record purpose :
https://docs.ubuntu.com/phone/en/platform/guides/push-notifications-server-guide
https://github.com/BigET/NotificationPost