[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)
I'm on a Nexus 7 (LTE) r.23 from ubuntu-touc/ ubuntu-rtm/proposed from system-image.tasemnice.eu/ Bluetooth does not even become discoverable - it just times out - even when I have my bluetooth keyboard scanning -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1421249 Title: bluetooth can not be enabled sometimes (when booting with flight mode on being one case) Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: Triaged Status in urfkill package in Ubuntu: Triaged Bug description: The bluetooth indicator and the bluetooth page in system settings sometimes won't turn on bluetooth until after a reboot. What I expect to happen is that if bluetooth is off in the indicator/system settings and I tap the switch, the switch will go green and in a moment the bluetooth indicator will show up and bluetooth is enabled. When bluetooth is on, I expect to go into the indicator/system settings and turn the switch off, the switch will go gray and the bluetooth indicator will hide and bluetooth is disabled. I expect this to work whenever I want while the phone is on. Sometimes, this does not work. For example, yesterday I disabled bluetooth at some point in the evening and later I went to sleep. When I woke up, I tried to turn it on via the indicator and also system settings and it wouldn't turn on. In the indicator, the switch moves to the green position briefly, then moves back to gray (the bluetooth indicator remains hidden and bluetooth is disabled). In system settings, the switch will stay green, but the bluetooth indicator remains hidden and bluetooth is disabled. If I leave system settings and come back, the the switch is now in the off position. /var/lib/urfkill/saved-states has: [BLUETOOTH] soft=false prev-soft=false bluetoothd is confirmed to be running before and after using the indicator and system settings when bluetooth cannot be enabled. Workaround: reboot the phone and bluetooth will be enabled. Note: this is not new behavior-- I'm only reporting it now (partly because I thought it was fixed for a while, but that might have been because I was rebooting a lot at the time) $ system-image-cli -i current build number: 194 device name: mako channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-11 15:34:27 version version: 194 version ubuntu: 20150211.1 version device: 20150116 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421249/+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 1502524] [NEW] Bluetooth - Ubuntu Touch
Public bug reported: Hi I am using a Nexus 7 - LTE (ie I get the images from http://system- image.tasemnice.eu/ubuntu-touch) While the bluetooth icon is there, it doesn't stay on. I can check the box, but the device does not become discoverable. I have just seen Michael Hall's video using a bluetooth mouse (I assume a keyboard will have the same effect), and am keen to utilise this. Thanks Steven PS Kari on ask ubuntu has had the same problem ** Affects: bluetooth-touch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluetooth-touch in Ubuntu. https://bugs.launchpad.net/bugs/1502524 Title: Bluetooth - Ubuntu Touch Status in bluetooth-touch package in Ubuntu: New Bug description: Hi I am using a Nexus 7 - LTE (ie I get the images from http://system- image.tasemnice.eu/ubuntu-touch) While the bluetooth icon is there, it doesn't stay on. I can check the box, but the device does not become discoverable. I have just seen Michael Hall's video using a bluetooth mouse (I assume a keyboard will have the same effect), and am keen to utilise this. Thanks Steven PS Kari on ask ubuntu has had the same problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1502524/+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 1483765] Re: The browser user-agent string should be dynamic, reacting to form factor changes
When I go to portal.office.com it lets me load my username and then proceeds to try and take me to anotherl ogin page. the string in the URL is generated by a federation server however, after putting in my details in comes up with credentials not found. this process works OK in either Firefox or chromium on the desktop but in in this package in either the desktop or on the touch device. -- 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/1483765 Title: The browser user-agent string should be dynamic, reacting to form factor changes Status in webbrowser-app package in Ubuntu: Confirmed Bug description: To support a converged desktop scenario, the browser user agent string needs to be recalculated as the form factor changes. Currently it is set, according to a set of heuristics, at startup time, and not re- evaluated during the lifetime of the browser app. There are some more aspects to that bug. 1. What are the heuristics for determining the form-factor, and which form factors to support? Ideally, this is an SDK API we can just re- use. 2. When should the UA be updated? Again, ideally this would be on form factor changes, based on a signal. So which service will deliver that signal? 3. The overrides need also to be dynamic as well, so how many sets are supported, ie depending on the set of form factors supported, we need as many overrides 4. This extends to not only webbrowser-app but more importantly webapp-container, where overrides are a lot more widespread, and not centrally maintained 5. When the UA and / or the form factor changes, parts of webbrowser- app or webapp-container may want to further react, for example to reload the page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1483765/+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
