[Touch-packages] [Bug 1665926] Re: photos.google.com is not usable
Dear Olivier, thanks for the quick response. The though question however will be, how to educate companies to be more open-minded when it comes to user agent sniffing. Maybe you can suggest to officially contact some Google guys so that they have a look into it. The user agent from Ubuntu Touch seems not to be Ubuntu-specific, so it must also hit other users on the planet. Otherwise we will be always on the hunt to update the overrides, and with some time passing the list gets bloated and unmaintainable IMHO. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1665926 Title: photos.google.com is not usable Status in webbrowser-app package in Ubuntu: Fix Committed Bug description: https://photos.google.com/ is not usable with the browser on UT. It´s the old user agent disaster. Removing MobileSafari helps. Is this one really necessary by the way, the other UA parts seem to be specific enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1665926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665926] [NEW] photos.google.com is not usable
Public bug reported: https://photos.google.com/ is not usable with the browser on UT. It´s the old user agent disaster. Removing MobileSafari helps. Is this one really necessary by the way, the other UA parts seem to be specific enough. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1665926 Title: photos.google.com is not usable Status in webbrowser-app package in Ubuntu: New Bug description: https://photos.google.com/ is not usable with the browser on UT. It´s the old user agent disaster. Removing MobileSafari helps. Is this one really necessary by the way, the other UA parts seem to be specific enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1665926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328183] Re: User-Agent string results in poor UX on web
Alas, how can it be that not even photos.google.com works with the default UA string from Ubuntu Touch? If I remove MobileSafari part it´s ok. What kind of weird detection are they doing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1328183 Title: User-Agent string results in poor UX on web Status in webbrowser-app package in Ubuntu: Triaged Bug description: The User-Agent string for the browser is similar enough to the Android browser User-Agent, that it creates a poor experience when browsing the web on an Ubuntu phone. An inordinately large number of web sites persistently advertise to "install our app" instead of providing the best web experience; an app which cannot be installed. This is exacerbated by the pervasiveness of webapps on Ubuntu phone, which simply embed the mobile web site with webapp-container, and still result in seeing such advertisements, despite the fact that the "app" on Ubuntu is already installed, and the Android apps being advertised are simply not installable. Having all the big web sites telling users of Ubuntu that they should be using Android instead, is not very good for the user experience at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1328183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444688] Re: WLAN to 3G connection does not connect automatically
Bug still open. Please guys, you will get overwhelmed like the people from Firefox (just look into Bugzilla´s millions of unmaintained bug reports) if you do not try to update bug statuses... ** Changed in: indicator-network (Ubuntu) Status: Confirmed => Invalid ** Changed in: indicator-network (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1444688 Title: WLAN to 3G connection does not connect automatically Status in indicator-network package in Ubuntu: Fix Released Bug description: when a WLAN connection interrupts, the 3G connection has not the ability to connect automatically. on the other hand as soon as the smartphone recognize a WLAN the smartphone will connect to it. Ubuntu 14.10 (r20) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1444688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1632715] Re: Can't receive MMS messages
** Tags removed: ota-13 ** Tags added: ota-14 t-mobile -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1632715 Title: Can't receive MMS messages Status in Canonical System Image: New Status in messaging-app package in Ubuntu: New Bug description: Hello! I'm using the Meizu MX4 on OTA 13 and my provider is Tele2 in Sweden. I have checked with Tele2 that everything works on there part, which they say it does. The bug is that when someone sends a MMS message to me nothing happenes. I can send MMS messages to others without problems. But not receive, no notification, nothing. Edit: I was able to receive MMS messages before OTA-10, during OTA-10 and OTA-11 I got SMS messages with a link to a web page and a code. Best Regards / Rasmus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5
GPS works for me now if WiFi is turned on with 9/10 success. Can be
closed IMHO
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783
Title:
GPS does not work on my Bq E5
Status in location-service package in Ubuntu:
Confirmed
Bug description:
I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
SensorsStatus app shows GPS as returning no results for location
(every reading ("Latitude", "Longitude", etc) is shown as a dash,
except "Method" which is "Satellite" and "Speed" which is "nan") . I
have attached various logfiles in the hope that they will help. I have
tried turning off location detection and GPS and turning them back on
again, to no avail. I have also tried turning off wifi, to no avail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1608234] Re: [Nexus 5] Camera pictures rotated by 90° clockwise
Hello, can be closed, this one is filed in a wrong package. Moved it to ubports issues :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1608234 Title: [Nexus 5] Camera pictures rotated by 90° clockwise Status in camera-app package in Ubuntu: New Bug description: Hello, using either the front or the back camera I get pictures which are rotated by 90° clockwise. No idea what this could come from acutally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1608234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444688] Re: WLAN to 3G connection does not connect automatically
Can someone close this bug? BTW it seems Launchpad could use a little more maintenance so that we get rid of solved but open bugs, this can be observed on many other packages also... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1444688 Title: WLAN to 3G connection does not connect automatically Status in indicator-network package in Ubuntu: Confirmed Bug description: when a WLAN connection interrupts, the 3G connection has not the ability to connect automatically. on the other hand as soon as the smartphone recognize a WLAN the smartphone will connect to it. Ubuntu 14.10 (r20) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1444688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455594] Re: downsize pictures before sharing
I just learned that Android apps like WhatsApp or Telegram can resize the pictures during upload. This would also be a valid approach for this issue. However, I still think there should be a way to switch to a different resolution also in the camera app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1455594 Title: downsize pictures before sharing Status in camera-app: Confirmed Status in camera-app package in Ubuntu: Confirmed Status in gallery-app package in Ubuntu: Confirmed Bug description: Well i was wondering if you guys can add a resize option to your gallery/camera app, so after taking a picture we can share it easily on social media or some forums that have a limit to the size of pictures that are allowed to be posted. Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1455594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620054] Re: Google reCaptcha does not work in browser
** Summary changed: - Recaptcha does not work on xda dev forums + Google reCaptcha does not work in browser ** Description changed: I was not able to post a reply on xda developers forum. Recaptcha told - me that the browser does not support the widget. It seems strange since + me that the browser does not support the widget. It seemed strange since this is a commonly used captcha framework. + + However, testing with the following test page + https://patrickhlauke.github.io/recaptcha/ revealed that reCaptcha is + not working at ll in the Ubuntu Browser. + + Since this is an important verification method these days I would assume + someone needs to talk to Google to either allow our User-Agent, or we + must fake once again the UA string in some way. This is really a bad + thing I know. But what does it help? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1620054 Title: Google reCaptcha does not work in browser Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I was not able to post a reply on xda developers forum. Recaptcha told me that the browser does not support the widget. It seemed strange since this is a commonly used captcha framework. However, testing with the following test page https://patrickhlauke.github.io/recaptcha/ revealed that reCaptcha is not working at ll in the Ubuntu Browser. Since this is an important verification method these days I would assume someone needs to talk to Google to either allow our User-Agent, or we must fake once again the UA string in some way. This is really a bad thing I know. But what does it help? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620054] [NEW] Recaptcha does not work on xda dev forums
Public bug reported: I was not able to post a reply on xda developers forum. Recaptcha told me that the browser does not support the widget. It seems strange since this is a commonly used captcha framework. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1620054 Title: Recaptcha does not work on xda dev forums Status in webbrowser-app package in Ubuntu: New Bug description: I was not able to post a reply on xda developers forum. Recaptcha told me that the browser does not support the widget. It seems strange since this is a commonly used captcha framework. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609529] Re: Need possibility to change device name on Ubuntu Touch
*** This bug is a duplicate of bug 1574370 *** https://bugs.launchpad.net/bugs/1574370 I disagree that this is a duplicate. The hostname which is referred to in the other ticket is not even used by the Bluetooth stack. So even if the other ticket would be resolved, this ticket here would still be valid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1609529 Title: Need possibility to change device name on Ubuntu Touch Status in bluez package in Ubuntu: New Bug description: Hello, got now 3 UT devices in my household, and it is really confusing to not being able to use a different name in the Bluetooth setup to distinguish devices from each other. I remember during device setup that I have entered a name for the device, why can´t this be used? Better of course to enable an input box where currently the static text lives. This is really an important feature I would say. BR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1609529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609529] [NEW] Need possibility to change device name on Ubuntu Touch
Public bug reported: Hello, got now 3 UT devices in my household, and it is really confusing to not being able to use a different name in the Bluetooth setup to distinguish devices from each other. I remember during device setup that I have entered a name for the device, why can´t this be used? Better of course to enable an input box where currently the static text lives. This is really an important feature I would say. BR ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1609529 Title: Need possibility to change device name on Ubuntu Touch Status in bluez package in Ubuntu: New Bug description: Hello, got now 3 UT devices in my household, and it is really confusing to not being able to use a different name in the Bluetooth setup to distinguish devices from each other. I remember during device setup that I have entered a name for the device, why can´t this be used? Better of course to enable an input box where currently the static text lives. This is really an important feature I would say. BR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1609529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596028] Re: Dangling entries in list of available devices
In another bug someone rote that to delete entries Bluetooth must be on. Maybe it must also be connected to smth, unfortunately I cant try this right now as I had to hard reset my phone... BR -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1596028 Title: Dangling entries in list of available devices Status in bluez package in Ubuntu: Confirmed Bug description: Accidently I seem to have paired with foreign devices, which I do not own, nor do I know exactly where it happened. Maybe I was just curious if the BQ phone would pair with them. However, now it is not possible to remove the entries again. Those entries are Roku Player and some TV device... See attached screenshots. The delete button is gray and klicking does nothing. Please help, the entries are really annyoing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444688] Re: WLAN to 3G connection does not connect automatically
Is this still an issue? For me this works I would say... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1444688 Title: WLAN to 3G connection does not connect automatically Status in indicator-network package in Ubuntu: Confirmed Bug description: when a WLAN connection interrupts, the 3G connection has not the ability to connect automatically. on the other hand as soon as the smartphone recognize a WLAN the smartphone will connect to it. Ubuntu 14.10 (r20) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1444688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
I just can tell you that I try now on bq E5, E4.5 and Nexus 5... sometimes it still happens but I figured out that normally after 2-3 minutes the WiFi internet settings are being recognized and things start working... So for me it went from not working to working after a long timeout :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: New Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) scheduled... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) starting... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) successful. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 3 of 5 (IP Configure
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
GTriderXC, I reported this behaviour here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028 - it´s also happening with other devices than carkits... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1500039] Re: Ubuntu Phone is not getting a mobile network cell triangulation position
I found a new symptom: Got an error message telling me: Geolocation error: only secure origins are allowed (see: https://goo.gl/Y0ZkNV).. Is that the reason why no geolocation works anymore in the browser? BR -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1500039 Title: Ubuntu Phone is not getting a mobile network cell triangulation position Status in Canonical System Image: In Progress Status in location-service package in Ubuntu: In Progress Bug description: Hi! I think that the mobile network cell triangulation position is not working in Ubuntu Phone OS. The position should be really fast (~1 - 5") and I'm thinking that Ubuntu Phone is waiting for a real GPS position every time. A good test could be this: - Go to a room, way out of a sky to avoid a real GPS signal. - Set WiFi service OFF. - Set GPS service ON. - Set data connection ON. - Go to this website via webbrowser-app: http://leafletjs.com/examples/mobile-example.html The website will ask you to allow access to the current location. - Make sure to not have a GPS position cached. In a PC or *any* Android you'll see your position immediately. Bug: In Ubuntu Phone an error will appears. This error is because the geoposition (https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation) is not working with the cell triangulation network data. You can try a lot of apps like Google Maps, OSMTouch, HERE map, uNAV... and a fast position from data connection is not happening, unless you be with a WIFI connection. If you try Google Maps in Android, the position will be really fast just with data connection. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1608234] [NEW] [Nexus 5] Camera pictures rotated by 90° clockwise
Public bug reported: Hello, using either the front or the back camera I get pictures which are rotated by 90° clockwise. No idea what this could come from acutally. ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1608234 Title: [Nexus 5] Camera pictures rotated by 90° clockwise Status in camera-app package in Ubuntu: New Bug description: Hello, using either the front or the back camera I get pictures which are rotated by 90° clockwise. No idea what this could come from acutally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1608234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423045] Re: camera-app not working on Nexus 5
I can take pictures with the front and the back camera without crashing. But the pictures are rotated by 90° clockwise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1423045 Title: camera-app not working on Nexus 5 Status in camera-app package in Ubuntu: Confirmed Bug description: On my neuxs 5, camera-app not working. some information: $ uname -a Linux ubuntu-phablet 3.4.0-1-hammerhead #9-Ubuntu SMP PREEMPT Sun Jul 20 08:27:48 UTC 2014 armv7l armv7l armv7l GNU/Linux crash information: ApportVersion: 2.14.7-0ubuntu10 ClickPackage: True Disassembly: => 0x0: Cannot access memory at address 0x0 InstallationDate: Installed on 2014-12-01 (79 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141201-020204) Package: com.ubuntu.camera 3.0.0.484 PackageArchitecture: armhf Registers: r0 0x19d9320 27104032 r1 0xaf2596992938476185 r2 0x1991530 26809648 r3 0x0 0 r4 0xaf23403c2938323004 r5 0xaf2341082938323208 r6 0xaf2596992938476185 r7 0x19d9320 27104032 r8 0xbeb99f103199835920 r9 0x1959308 26579720 r100x18c3520 25965856 r110x0 0 r120xb461800c3026288652 sp 0xbeb99df80xbeb99df8 lr 0xaf222d2d-1356714707 pc 0x0 0x0 cpsr 0x60101610612752 SegvAnalysis: Skipped: missing required field "Disassembly" SourcePackage: com.ubuntu.camera Stacktrace: #0 0x in ?? () No symbol table info available. #1 0xaf222d2c in android_camera_enumerate_supported_thumbnail_sizes () from /usr/lib/arm-linux-gnueabihf/libcamera.so.1 No symbol table info available. #2 0xaf256ad2 in AalCameraService::initControls(CameraControl*, CameraControlListener*) () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so No symbol table info available. #3 0xaf256b8c in AalCameraService::connectCamera() () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so No symbol table info available. #4 0xaf25597c in AalCameraControl::setState(QCamera::State) () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so No symbol table info available. #5 0xb10a1be2 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Multimedia.so.5 No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) StacktraceAddressSignature: /opt/click.ubuntu.com/com.ubuntu.camera/3.0.0.484/camera-app:11:/usr/lib/arm-linux-gnueabihf/libcamera.so.1.0.0+1d2c:/usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so+11ad2:/usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so+11b8c:/usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so+1097c:/usr/lib/arm-linux-gnueabihf/libQt5Multimedia.so.5.3.2+4dbe2 StacktraceTop: ?? () android_camera_enumerate_supported_thumbnail_sizes () from /usr/lib/arm-linux-gnueabihf/libcamera.so.1 AalCameraService::initControls(CameraControl*, CameraControlListener*) () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so AalCameraService::connectCamera() () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so AalCameraControl::setState(QCamera::State) () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so SystemImageInfo: current build number: 1 device name: hammerhead channel: ubuntu-touch/devel alias: ubuntu-touch/vivid last update: 1970-06-05 21:25:04 version version: 1 version keyring: archive-master version device: 20141018 version custom: 3 Tags: vivid ThreadStacktrace: . Thread 10 (Thread 0xac6ad450 (LWP 5862)): #0 0xb631f306 in clone () from /lib/arm-linux-gnueabihf/libc.so.6 No symbol table info available. #1 0xb626e530 in do_clone.constprop () from /lib/arm-linux-gnueabihf/libpthread.so.0 No symbol table info available. #2 0x in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) . Thread 9 (Thread 0xb231f450 (LWP 5841)): #0 0xb6318bb2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6 No symbol table info available. #1 0xb5f31350 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) . Thread 8 (Thread 0xaf0ff450 (LWP 5844)): #0 0xb6318bb2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6 No symbol table info available. #1 0xb5f31350 in ?? () from
[Touch-packages] [Bug 1455594] Re: downsize pictures before sharing
I wonder why there is no option to really set the resolution for pictures taken. On my BQ 5 I get pictures with that resolution: 5888 x 3312 Pixels (19.50 MPixels) (16:9) - this is much too large for daily use. Could you easily introduce an option to set sizes 100% / 50% /25% /12.5%, so in order to stay independent form the physical resolution, do not mention pixels but use a percentage level? BR FLorian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1455594 Title: downsize pictures before sharing Status in camera-app: Confirmed Status in camera-app package in Ubuntu: Confirmed Status in gallery-app package in Ubuntu: Confirmed Bug description: Well i was wondering if you guys can add a resize option to your gallery/camera app, so after taking a picture we can share it easily on social media or some forums that have a limit to the size of pictures that are allowed to be posted. Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1455594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5
is there any regression with that, GPS worked for me on the BQ 5 for some time
now, but stopped after the last OTA. I am not good with debugging, I strongly
suggest to give a possibility to see status of GPS: number of satellites, if it
cold starts or can look up constellation etc...
BR
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783
Title:
GPS does not work on my Bq E5
Status in location-service package in Ubuntu:
Confirmed
Bug description:
I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
SensorsStatus app shows GPS as returning no results for location
(every reading ("Latitude", "Longitude", etc) is shown as a dash,
except "Method" which is "Satellite" and "Speed" which is "nan") . I
have attached various logfiles in the hope that they will help. I have
tried turning off location detection and GPS and turning them back on
again, to no avail. I have also tried turning off wifi, to no avail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1500039] Re: Ubuntu Phone is not getting a mobile network cell triangulation position
Plus is there any chance that this bug also affects GPS liason? I am not able anymore to use any GPS app on my BQ5, this started some time after the last OTA. BR -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1500039 Title: Ubuntu Phone is not getting a mobile network cell triangulation position Status in Canonical System Image: In Progress Status in location-service package in Ubuntu: In Progress Bug description: Hi! I think that the mobile network cell triangulation position is not working in Ubuntu Phone OS. The position should be really fast (~1 - 5") and I'm thinking that Ubuntu Phone is waiting for a real GPS position every time. A good test could be this: - Go to a room, way out of a sky to avoid a real GPS signal. - Set WiFi service OFF. - Set GPS service ON. - Set data connection ON. - Go to this website via webbrowser-app: http://leafletjs.com/examples/mobile-example.html The website will ask you to allow access to the current location. - Make sure to not have a GPS position cached. In a PC or *any* Android you'll see your position immediately. Bug: In Ubuntu Phone an error will appears. This error is because the geoposition (https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation) is not working with the cell triangulation network data. You can try a lot of apps like Google Maps, OSMTouch, HERE map, uNAV... and a fast position from data connection is not happening, unless you be with a WIFI connection. If you try Google Maps in Android, the position will be really fast just with data connection. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595673] Re: Cannot access teamweek.com (site reports browser too old)
They updated their site in one day. Seem to care for their customers ;) => Can be closed. BR -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595673 Title: Cannot access teamweek.com (site reports browser too old) Status in webbrowser-app package in Ubuntu: New Bug description: When trying to open the site https://app.teamweek.com the screen is overlaid with a warning that the browser is too old. The warning cannot be confirmed, since the button seems to be off screen. Also there is no other way to get rid of the message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595673] Re: Cannot access teamweek.com (site reports browser too old)
Yes I´ve done that right now, let´s wait for the result. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595673 Title: Cannot access teamweek.com (site reports browser too old) Status in webbrowser-app package in Ubuntu: New Bug description: When trying to open the site https://app.teamweek.com the screen is overlaid with a warning that the browser is too old. The warning cannot be confirmed, since the button seems to be off screen. Also there is no other way to get rid of the message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596028] Re: Dangling entries in list of available devices
** Attachment added: "Details of dangling device #2" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+attachment/4689862/+files/screenshot20160624_183209829%5B1%5D.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1596028 Title: Dangling entries in list of available devices Status in bluez package in Ubuntu: New Bug description: Accidently I seem to have paired with foreign devices, which I do not own, nor do I know exactly where it happened. Maybe I was just curious if the BQ phone would pair with them. However, now it is not possible to remove the entries again. Those entries are Roku Player and some TV device... See attached screenshots. The delete button is gray and klicking does nothing. Please help, the entries are really annyoing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596028] Re: Dangling entries in list of available devices
** Attachment added: "Details of dangling device #1" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+attachment/4689861/+files/screenshot20160624_183214382%5B1%5D.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1596028 Title: Dangling entries in list of available devices Status in bluez package in Ubuntu: New Bug description: Accidently I seem to have paired with foreign devices, which I do not own, nor do I know exactly where it happened. Maybe I was just curious if the BQ phone would pair with them. However, now it is not possible to remove the entries again. Those entries are Roku Player and some TV device... See attached screenshots. The delete button is gray and klicking does nothing. Please help, the entries are really annyoing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596028] [NEW] Dangling entries in list of available devices
Public bug reported: Accidently I seem to have paired with foreign devices, which I do not own, nor do I know exactly where it happened. Maybe I was just curious if the BQ phone would pair with them. However, now it is not possible to remove the entries again. Those entries are Roku Player and some TV device... See attached screenshots. The delete button is gray and klicking does nothing. Please help, the entries are really annyoing! ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Overview of dangling devices" https://bugs.launchpad.net/bugs/1596028/+attachment/4689860/+files/screenshot20160624_183849140%5B1%5D.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1596028 Title: Dangling entries in list of available devices Status in bluez package in Ubuntu: New Bug description: Accidently I seem to have paired with foreign devices, which I do not own, nor do I know exactly where it happened. Maybe I was just curious if the BQ phone would pair with them. However, now it is not possible to remove the entries again. Those entries are Roku Player and some TV device... See attached screenshots. The delete button is gray and klicking does nothing. Please help, the entries are really annyoing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595673] [NEW] Cannot access teamweek.com (site reports browser too old)
Public bug reported: When trying to open the site https://app.teamweek.com the screen is overlaid with a warning that the browser is too old. The warning cannot be confirmed, since the button seems to be off screen. Also there is no other way to get rid of the message. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1595673/+attachment/4689262/+files/screenshot20160623_204734967%5B1%5D.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595673 Title: Cannot access teamweek.com (site reports browser too old) Status in webbrowser-app package in Ubuntu: New Bug description: When trying to open the site https://app.teamweek.com the screen is overlaid with a warning that the browser is too old. The warning cannot be confirmed, since the button seems to be off screen. Also there is no other way to get rid of the message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
For me its better now since last update. Transitions to/from WiFi seem to be nearly always successful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: New Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) scheduled... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) starting... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) successful. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 3 of 5 (IP Configure Start) scheduled. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) complete. Jan 17 07:36:41 ubuntu-phablet
[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
** Attachment added: "After leaving flight mode. Note the H on top. After that Internet works again." https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270189/+attachment/4565946/+files/screenshot20160130_215020638.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: New Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) scheduled... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) starting... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) successful. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 3 of 5 (IP Configure Start) scheduled. Jan 17 07:36:41 ubuntu-phablet
[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
I am adding some screenshots for this... ** Attachment added: "After leaving WiFi area. No WiFi detected, but no switch to HSDPA" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270189/+attachment/4565944/+files/screenshot20160130_214928991.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: New Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) scheduled... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) starting... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) successful. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 3 of 5 (IP Configure Start) scheduled.
[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
** Attachment added: "Only solution to fix: Enter flightmode and leave it again..." https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270189/+attachment/4565945/+files/screenshot20160130_214941450.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: New Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) scheduled... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) starting... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) successful. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 3 of 5 (IP Configure Start) scheduled. Jan 17 07:36:41 ubuntu-phablet
[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
I am not sure if this is the right place but I see similar behaviour here with my BQ 5... I am online at my home with WiFi, however if I leave my home the phone does sometimes not switch to network correctly. I can e.g. still see the WiFi indicator shown but in the list of APs there is no green entry. Also, network does show only 3G or E, but not H if I try top open smth. All internet access ends with immediate connection errors, so it could also be DNS issue. But I am not sure. How can I debug the switch between network & wifi? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu RTM: New Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) scheduled... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: Activation (/ril_0) Stage 2 of 5 (Device Configure) starting... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: (/ril_0): device state change: prepare -> config
[Touch-packages] [Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized
Any progress on this? Specifically I would need this function in my Ubuntu Touch phone ;) BR Florian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized Status in NetworkManager: Fix Released Status in Plasma-widget-networkmanagement: Won't Fix Status in network-manager package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Status in networkmanagement package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I've got few wifi network profiles. NM connects to 1st available network in alphabetical order. But at my home NM connects to slow and unstable free network and I want to connect to my own wifi router. I suggest to add some priorities to different networks to set the order which network to connect to. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/366780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Confirmed also to be an issue with: - BQ E5 - Ubuntu Touch 15.04 (OTA-8.5) - BMW 2 Series 1. Select Bluetooth device manager in car console 2. Car console states name of carkit, switches to discoverable mode 3. Turn on BT in phone and wait 4. Carkit appears in phone, press connect 5. Phone shows "Connected", "Excellent" reception, you can check "Connect automatically" But no pairing appears on neither devices. The carkit has no option to discover devices at all, just passive waiting. Also, phone shows carkit as headphone, which is basically OK, but the carkit can also act als multimedia player. SO both profiles should be announced, maybe that's the problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475379] Re: mobile data down after leaving airplane mode
To me I have the opposite problem: Release: Ubuntu 15.04 - armhf Phone Model: BQ E5 HD (sim cards in Sim slot 1 and 2, mobile data is only enabled for card 2) 1. Mobile data works, airplane mode off 2. For some reason, mobile data (Edge, UMTS) looses connectivity and never gets it again (maybe associated with entering and leaving a WiFi) - Telephone & SMS still work - Network icon shows full strength for both SIMs, WiFi icon shows "empty shape" 3. Switch airplane mode on 4. Switch airplane mode off --> mobile data works immediatly It is very annyoing to constantly loose mobile data connectivity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1475379 Title: mobile data down after leaving airplane mode Status in indicator-network package in Ubuntu: New Bug description: Release: Ubuntu 15.04 - armhf Phone Model: BQ E5 HD (sim card in Sim slot 2) 1. Mobile data works, airplane mode off 2. Switch airplane mode on 3. Switch airplane mode off --> mobile data stays down (wifi works) 4. Restart phone, Mobile data works again I need to restart the phone in order to get mobile data working again after switching off flight mode. Sorry, no idea which package this error is related to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1475379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1247216] Re: Support for XMPP
Plus add OTR to the conversation and you got a rock solid IM solution that I would like much more to use on my mobile than WhatsApp or Telegram. Different XEP coverage by some clients can be a pain, but that should be not a reason not to try to get this done for Ubuntu Touch. People started hating Skype, so some of them might get interested in Jabber again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1247216 Title: Support for XMPP Status in messaging-app package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: Triaged Bug description: Hi All, basically there are three things that block me to move to Ubuntu Touch. A missing spotify app (already in developement :) ), a missing mail app (planned for 14.04 :) ) and finally a missing IM app -- especially for XMPP. Thusly, I propose adding support for XMPP to the messaging-app. It already uses telepathy so we should be able to add this functionality. I would also be willing to work on this if somebody points me out where to start. I guess we would have to break this down into several work packages: setting up accounts, online/offline handling of friends, choosing protocols when composing a message etc. But first I would like to get some feedback if you would be okay with such a feature. Maybe it is already planned? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1247216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
