[Touch-packages] [Bug 1589125] Re: WiFi does not work after about 1 in 4 suspends
*** This bug is a duplicate of bug 1576747 *** https://bugs.launchpad.net/bugs/1576747 ** This bug has been marked a duplicate of bug 1576747 Network manager unable to control wifi after suspend in 16.04 -- 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/1589125 Title: WiFi does not work after about 1 in 4 suspends Status in network-manager package in Ubuntu: Confirmed Bug description: Steps: Suspend, wait, resume, a few times. The Network Manager applet shows WiFi is enabled and shows just one or a handful of WiFi names, they don't include some that are known to be available and in use on other computers. Disabling and enabling WiFi does not fix the problem. Disabling and enabling networking does not fix the problem. Adding the following does not help: /etc/pm/config.d/unload_modules SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" Only workaround which works perfectly and instantly is to run: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 4 18:18:50 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.43.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.43.0/24 dev wlp2s0 proto kernel scope link src 192.168.43.89 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 HTC Portable Hotspot DF99 c29b59ba-b6ef-49db-b159-75ec21d3f436 /org/freedesktop/NetworkManager/ActiveConnection/0 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589125/+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 1576314] Re: Wifi fails to resume from standby
*** This bug is a duplicate of bug 1576747 *** https://bugs.launchpad.net/bugs/1576747 ** This bug has been marked a duplicate of bug 1576747 Network manager unable to control wifi after suspend in 16.04 -- 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/1576314 Title: Wifi fails to resume from standby Status in NetworkManager: Incomplete Status in network-manager package in Ubuntu: Triaged Bug description: System fails to detect any Wifi network SSID's on resume from standby sudo service network-manager restart brings the list of wireless network back in operation and you can continue as normal until next standby. Or a full system restart. Wireless card replaced with another working model. System fully patched as of 28.04.2016 description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 73 serial: 0c:8b:fd:b5:7c:0f width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-21-generic firmware=16.242414.0 ip=10.10.10.239 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:47 memory:f7a0-f7a01fff Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 28 17:17:33 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-15 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.10.10.1 dev wlp2s0 proto static metric 600 10.10.10.0/23 dev wlp2s0 proto kernel scope link src 10.10.10.239 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1576314/+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 1521337] Re: Add support for wired audio headset controls
*** This bug is a duplicate of bug 1309731 *** https://bugs.launchpad.net/bugs/1309731 ** This bug has been marked a duplicate of bug 1309731 headphone button does not play/pause music. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1521337 Title: Add support for wired audio headset controls Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: Most phones support remote controls built into wired audio headsets. There seem to be various types on the market offering between one and four function buttons, I for example have a pair of three-function Sennheiser CX2.00G earbuds. Google released a specification as part of its Android project (https://source.android.com/devices/accessories/headset/specification.html), but according to some source it is incompatible with older devices because different resistor values are being used. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521337/+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 1497828] Re: Apps appear to freeze in Unity8, although they are really still rendering (swap interval zero). Need to interact with the shell to unfreeze it.
A simple way to test it on the phone is to install my updated glmark2 click from the store, I recompiled it against the stable overlay PPA today so it now runs on OTA-7. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1497828 Title: Apps appear to freeze in Unity8, although they are really still rendering (swap interval zero). Need to interact with the shell to unfreeze it. Status in QtMir: Triaged Status in qtmir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: Apps appear to freeze in Unity8, although they are really still rendering (swap interval zero). Need to interact with the shell to unfreeze it. Test case (on Unity8 wily desktop): $ glmark2-mir -b :title=--desktop_file_hint=unity8 This freezes a couple of times during the benchmark. Test case (on a phone): $ mir_demo_client_target -n--desktop_file_hint=unity8 This freezes very quickly when you move your finger around. Test case (on a phone): $ glmark2-es2-mir -b :title=--desktop_file_hint=unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1497828/+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 1471666] Re: [MX4] 4K record
I think this might be because the video resolution is hardcoded at a maximum of 1920x1080 in http://bazaar.launchpad.net/~phablet-team /camera-app/trunk/view/head:/ViewFinderOverlay.qml#L101 . -- 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/1471666 Title: [MX4] 4K record Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: New Bug description: Hello, in camera options there is no possibility to record video in 4K. Max. is 1080p. Even on origami wallpaper (that to win invate of MX4) there was information about recording in 4K. How hard that will be to solve that? I'm not technical guy, but is that only to edit old/add new header 4K and two numbers of new resolution video output? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471666/+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 1470109] Re: gallery-app crashes after a few seconds opened
** Changed in: gallery-app Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1470109 Title: gallery-app crashes after a few seconds opened Status in Canonical System Image: New Status in gallery-app: Confirmed Status in Thumbnailer: New Status in gallery-app package in Ubuntu: New Bug description: This happens using the new thumbnailer included in SILO 10, on the BQ. To install the new thumbnailer from silo 10: sudo apt-get update sudo apt-get install thumbnailer-service To recreate just copy 2000 photo files to the Pictures folder and open the gallery-app. After a few seconds it crashes is most cases. I've attached the .crash report obtained on the phone. Backtrace (although symbols are not available it might add useful information): Thread 16 (Thread 0xad5ff370 (LWP 28281)): #0 0xb69db572 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 No symbol table info available. m-linux-gnueabihf/libQt5Core.so.5 No symbol table info available. rm-linux-gnueabihf/libQt5Core.so.5 No symbol table info available. #3 0x00053f4e in QString::QString(char const*) () No symbol table info available. #4 0x0008328a in PhotoMetadata::fromFile(char const*) () No symbol table info available. #5 0x000834e2 in PhotoMetadata::fromFile(QFileInfo const) () No symbol table info available. () No symbol table info available. #7 0x00061df6 in MediaObjectFactoryWorker::create(QString const) () No symbol table info available. #8 0x00061be0 in MediaObjectFactoryWorker::runCreate() () No symbol table info available. ject::Call, int, void**) () No symbol table info available. ibQt5Core.so.5 No symbol table info available. /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 No symbol table info available. inux-gnueabihf/libQt5Widgets.so.5 No symbol table info available. #13 0x00fa7020 in ?? () No symbol table info available. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470109/+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 1473720] Re: Capturing photo in Messaging App makes the keyboard go away and I'm unable to get it back
Confirmed on arale rc-proposed r58. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1473720 Title: Capturing photo in Messaging App makes the keyboard go away and I'm unable to get it back Status in Canonical System Image: New Status in messaging-app package in Ubuntu: Confirmed Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Phone: Arale @ rc-proposed #61 Reproduce: 1. Open Messaging App 2. Tap camera icon 3. Take picture and accept it What happens: Keyboard goes away and does not come back when focusing the text input. What should happen: The keyboard should function normally Note: only a reboot seems to fix this To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473720/+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 1471577] Re: Left launcher should show what apps are open
GTriderXC, please open a separate bug for that issue, if there isn't already one open. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1471577 Title: Left launcher should show what apps are open Status in Canonical System Image: New Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: Confirmed Bug description: Hello, I think that will be good if left launcher shows us somehow what app is in opened. For now, when we start new app, its icon 'lands' in left launcher. But we don't know if that app is pinned there and it is all the time, or only because it's opened. I think that in Desktop version that issue is solved, but for now can't check it now. Desired solution--- Launcher should indicate running apps in the launcher with a mark on the left side of the app icon. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471577/+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 1473246] [NEW] MediaTek Preloader on a mobile device triggers cdc_acm kernel module usage by ModemManager
Public bug reported: This is an interesting bug that is triggered under some circumstances if one of the official, MediaTek-SoC-based Ubuntu phones is connected to a Linux host via USB. Tested host: Ubuntu 15.04 Desktop, kernel 3.19.0-21-generic, package linux-image-generic 3.19.0.22.21 amd64, package modemmanager 1.4.0-1 Tested phones: Meizu MX4 (arale) and bq Aquaris E4.5 (krillin), image version irrelevant because the Preloader comes with all devices and cannot be changed How to reproduce, possibility 1: 1. Disconnect the USB connection, if necessary. 2. Turn off the phone. 3. Connect the phone via USB. It will take a bit and then turn on, displaying the charge animation. How to reproduce, possibility 2: 1. Reboot the phone while it is still attached to the host. The kernel ringbuffer will contain the following log messages (example for krillin): [288774.244158] usb 1-1: new high-speed USB device number 22 using xhci_hcd [288774.373589] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000 [288774.373593] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [288774.373594] usb 1-1: Product: MT65xx Preloader [288774.373596] usb 1-1: Manufacturer: MediaTek [288774.435247] cdc_acm 1-1:1.1: ttyACM26: USB ACM device [288774.874607] usb 1-1: USB disconnect, device number 22 [288774.874755] cdc_acm 1-1:1.1: failed to set dtr/rts And syslog will contain the following log messages: Jul 10 00:58:07 fire ModemManager[1103]: info (tty/ttyACM27): released by modem /sys/devices/pci:00/:00:14.0/usb1/1-1 Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Iridium) [ttyACM27] error when checking support: '(Iridium) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Cinterion) [ttyACM27] error when checking support: '(Cinterion) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Nokia) [ttyACM27] error when checking support: '(Nokia) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn (Plugin Manager) (Generic) [ttyACM27] error when checking support: '(Generic) Missing port probe for port (tty/ttyACM27)' Jul 10 00:58:10 fire ModemManager[1103]: warn Couldn't find support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin The allocated ttyACMx device is never freed, and after a couple of days developing on the phone (with lots of phone restarts) I've noticed that my machine has accumulated an usage count of 58: $ lsmod | grep cdc_acm cdc_acm36864 58 lsof show that ModemManager still holds the devices: # sudo lsof | grep ACM ModemMana 9214 root9u CHR 166,1 0t07599355 /dev/ttyACM1 (deleted) ModemMana 9214 root 10u CHR 166,0 0t07596974 /dev/ttyACM0 (deleted) ... Restarting ModemManager immediately reduces the usage count to 0 again and frees all devices. Why does this happen? Luckily I've read the MediaTek Preloader source code. The Preloader is the first-stage bootloader on MediaTek SoCs and exposes a proprietary USB interface that can be used for debugging purposes and to download firmware to the device. The implementation of this interface is rudimentary and emulates a CDC ACM serial port, which probably doesn't fully conform to the standard and also just falls from the bus after a short amount of time if the host doesn't initiate the proprietary protocol. So I think the kernel and ModemManager immediately try to use the emulated device when it becomes available, but because the implementation in the Preloader is incomplete some bug (timeout?) is triggered and ModemManager never closes the device. Sadly I don't have the expertise to decide if this is a bug in ModemManager or the kernel or both, so I file it with ModemManager. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1473246 Title: MediaTek Preloader on a mobile device triggers cdc_acm kernel module usage by ModemManager Status in modemmanager package in Ubuntu: New Bug description: This is an interesting bug that is triggered under some circumstances if one of the official, MediaTek-SoC-based Ubuntu phones is connected to a Linux host via USB. Tested host: Ubuntu 15.04 Desktop, kernel 3.19.0-21-generic, package linux-image-generic 3.19.0.22.21 amd64, package modemmanager 1.4.0-1 Tested phones: Meizu MX4 (arale) and bq Aquaris E4.5 (krillin), image version irrelevant because the Preloader comes with all devices and cannot be changed How to reproduce, possibility 1: 1. Disconnect the USB connection, if necessary. 2. Turn off the phone. 3.
[Touch-packages] [Bug 1465826] Re: The phone freez totally
I did a bit of analysis on krillin OTA-4. 1. Go to the apps scope. 2. Swipe in the launcher from the left. No error. 3. Switch to an app. After about a second, the following error is logged to unity8.log: ** (process:2492): WARNING **: Unable to get pids for 'unity8-dash' to send signal 19 ApplicationController::pauseApplication FAILED to pause appId= unity8-dash process 2492 is unity8, signal 19 is SIGSTOP on x86 Linux. 4. Swipe in the launcher from the left. The following error is immediately logged to unity8.log: ** (process:2492): WARNING **: Unable to get pids for 'unity8-dash' to send signal 18 ApplicationController::resumeApplication FAILED to resume appId= unity8-dash Signal 18 is SIGCONT on x86 Linux. 5. Tap inside the app to make the launcher disapper. The following error is immediately logged to unity8.log: ** (process:2492): WARNING **: Unable to get pids for 'unity8-dash' to send signal 19 ApplicationController::pauseApplication FAILED to pause appId= unity8-dash Every time the launcher is shown or hidden while an app is active, those errors appear. But no matter how hard I try to provoke it, the UI doesn't freeze. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1465826 Title: The phone freez totally Status in Qt integration with the Mir display server: New Status in unity8 package in Ubuntu: Incomplete Bug description: I want to change between 2 application( dekko to web browser) , but the phone complcompletely freez. After ~20 minutes I restarted the phone.(pushed the ON buttone until restart) To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1465826/+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 1429784] Re: Battery level stuck overnight
I noticed this bug when the system settings screen showed a battery level of 94% after 59 hours of idling. But I am not sure it is an userspace bug: phablet@ubuntu-phablet:~$ cat /sys/devices/platform/battery/power_supply/battery/uevent POWER_SUPPLY_NAME=battery POWER_SUPPLY_STATUS=Charging POWER_SUPPLY_HEALTH=Good POWER_SUPPLY_PRESENT=1 POWER_SUPPLY_TECHNOLOGY=Li-ion POWER_SUPPLY_CAPACITY=93 POWER_SUPPLY_BATT_VOL=4186 POWER_SUPPLY_BATT_TEMP=260 POWER_SUPPLY_TEMPERATURER=6644 POWER_SUPPLY_TEMPBATTVOLTAGE=508 POWER_SUPPLY_INSTATVOLT=4186 POWER_SUPPLY_BATTERYAVERAGECURRENT=462 POWER_SUPPLY_BATTERYSENSEVOLTAGE=4186 POWER_SUPPLY_ISENSEVOLTAGE=4275 POWER_SUPPLY_CHARGERVOLTAGE=4702 POWER_SUPPLY_STATUS_2ND=Discharging POWER_SUPPLY_CAPACITY_2ND=50 POWER_SUPPLY_PRESENT_2ND=0 POWER_SUPPLY_VOLTAGE_MAX_DESIGN=420 POWER_SUPPLY_VOLTAGE_NOW=4186000 POWER_SUPPLY_TEMP=260 It shows POWER_SUPPLY_STATUS=Charging because I had to connect the USB cable for phablet-shell. POWER_SUPPLY_CAPACITY=93 must be wrong, it is an impossible value after two and a half days of idling with radios enabled. I rebooted the device and nothing changed. So it might be a kernel and/or hardware issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1429784 Title: Battery level stuck overnight Status in upower package in Ubuntu: Confirmed Bug description: Test case. - Leave the device locked overnight. - On the next morning, go to System Settings Battery. Expected result. - Battery should report a lower level. Actual result. - A plain graph is shown. current build number: 135 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1429784/+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 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
I rebooted my krillin until the bug got triggered (about ten times) and tried to gather as much information as possible directly after the device was accessible via ADB. I've attached the following files: - dmesg - Output of logcat -b main - Output of logcat -b system - Contents of all GPU-related directories under /sys/kernel/debug - Contents of all system- and GUI-related logfiles under /var/log/ I am currently trying to find any differences to a normal environment, but no luck so far.?field.comment=I rebooted my krillin until the bug got triggered (about ten times) and tried to gather as much information as possible directly after the device was accessible via ADB. I've attached the following files: - dmesg - Output of logcat -b main - Output of logcat -b system - Contents of all GPU-related directories under /sys/kernel/debug - Contents of all system- and GUI-related logfiles under /var/log/ I am currently trying to find any differences to a normal environment, but no luck so far. ** Attachment added: dmesg.bz2 https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+attachment/4421429/+files/dmesg.bz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in unity8 package in Ubuntu: Confirmed Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+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 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
** Attachment added: logcat-system.bz2 https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+attachment/4421431/+files/logcat-system.bz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in unity8 package in Ubuntu: Confirmed Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+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 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
** Attachment added: logcat-main.bz2 https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+attachment/4421430/+files/logcat-main.bz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in unity8 package in Ubuntu: Confirmed Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+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 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
** Attachment added: sys-kernel-debug.tbz2 https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+attachment/4421432/+files/sys-kernel-debug.tbz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in unity8 package in Ubuntu: Confirmed Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+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 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
** Attachment added: var-log.tbz2 https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+attachment/4421433/+files/var-log.tbz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in unity8 package in Ubuntu: Confirmed Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+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 1447562] Re: There should be levels on the screen to see whether one holds the camera level
The code for this already exists in the Level app in the store. -- 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/1447562 Title: There should be levels on the screen to see whether one holds the camera level Status in camera-app package in Ubuntu: Confirmed Bug description: Many digital cmeras, especially Ricoh and recent Panasonic ansd Olympus, show levels on their screen to make it easier to hold the camera level, which is very important for landscape and architecture shots. Olympus and Ricoh have one horizontal level at the bottom to make horizontal lines in the picture beine level and one vertical level on the right side of the screen to make the optical axis level and so vertical lines being vertical, especially with a wide angle lens. Panasonic cameras have something like an artificial horizon in the middle of the picture. This would also be a great feature for Ubuntu's camera app, to not come home with the Leaning Tower of Paris. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1447562/+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 1377427] Re: white 1 pixel line on left edge of the screen since RTM image 81
This bug gets triggered much more often since krillin r23 (OTA-4), at one point I got it on four out of 18 reboots. It has to be an issue at the driver level, since screenshots taken with the device itself show a correct picture, just the display doesn't. ** Changed in: unity8 (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377427 Title: white 1 pixel line on left edge of the screen since RTM image 81 Status in unity8 package in Ubuntu: Confirmed Bug description: with image 81 my krillin shows a white 1px line on the left edge of the screen, specifically visible when switching apps or sliding the launcher in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377427/+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 1468002] Re: Using menu in landscape mode crashes Gallery app
The app does not just crash, in step 5 the option menu is briefly shown and then tumbles down. It really looks like some kind of intentional animation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1468002 Title: Using menu in landscape mode crashes Gallery app Status in gallery-app package in Ubuntu: Confirmed Bug description: Using Meizu MX4 with Ubuntu 15.05 r2 Steps: 1. open gallery app 2. choose photo 3. rotate phone to landscape 4. tap photo (to show menu) 5. tap icon top right (to show options) 6. gallery app exits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1468002/+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 1421455] Re: Slow wake up time on physical power button pressed
The issue became *much* better on my krillin device with OTA-4. Can anybody comment on what was changed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1421455 Title: Slow wake up time on physical power button pressed Status in powerd package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Device: bq Aquaris E4.5 running: Stable #17 When pressing on physical power button on device to wake it up sometime it even takes up to 2-3 secs before anything appears on the screen. This time wary but its hard to tell then its shorter and when is longer. This is not so bad on nexus4. Should you need more info, I'm happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1421455/+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 1448180] Re: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone
Any updates on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1448180 Title: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone Status in location-service package in Ubuntu: Invalid Status in qtubuntu-sensors package in Ubuntu: Confirmed Bug description: Device: bq Aquaris E4.5 Ubuntu Edition Operating System: Ubuntu 14.10 (r21) I am currently trying to build a clone of the GPS Status Android app, it displays various details about the built-in GPS receiver. According to the developer documentation at http://developer.ubuntu.com/api/qml/sdk-14.10/QtLocation.location- positioning-cpp/ , a call to QGeoSatelliteInfoSource::createDefaultSource() can be used to get access to the default Satellite positioning source implementation. On my device this call returns NULL. Sample code is located at https://github.com/Sturmflut/ubuntu-touch- simple-gps/tree/3da3dc5f089e698c34765fd18322b84727cb13ae , the call in question is located at backend/modules/Simplegps/gpsdataprovider.cpp . I attached the file and its header for future reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1448180/+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 1421455] Re: Slow wake up time on physical power button pressed
So this bug has to be escalated to the handset or even the chipset manufacturer, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1421455 Title: Slow wake up time on physical power button pressed Status in powerd package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Device: bq Aquaris E4.5 running: Stable #17 When pressing on physical power button on device to wake it up sometime it even takes up to 2-3 secs before anything appears on the screen. This time wary but its hard to tell then its shorter and when is longer. This is not so bad on nexus4. Should you need more info, I'm happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1421455/+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 1421455] Re: Slow wake up time on physical power button pressed
I was monitoring my syslog while pressing the button. Apr 29 14:37:35 ubuntu-phablet powerd[949]: handle_requestSysState from :1.13 - ACTIVE (1) Apr 29 14:37:35 ubuntu-phablet powerd[949]: name_watch_add: looking for :1.13 Apr 29 14:37:35 ubuntu-phablet powerd[949]: watching :1.13 to see when it disappears on dbus Apr 29 14:37:35 ubuntu-phablet powerd[949]: libsuspend: acquire_wake_lock: powerd_power_request Apr 29 14:37:35 ubuntu-phablet powerd[949]: handle_requestSysState - SUCCESS Apr 29 14:37:35 ubuntu-phablet powerd[949]: Enqueue state change to ACTIVE Apr 29 14:37:35 ubuntu-phablet powerd[949]: exiting suspend Apr 29 14:37:35 ubuntu-phablet powerd[949]: libsuspend: exit_suspend. Apr 29 14:37:35 ubuntu-phablet kernel: [21759.723201][Ker_PM][request_suspend_state]wakeup (3-0) at 21760134073325 (2015-04-29 12:37:35.882532317 UTC) exactly here there is a short delay Apr 29 14:37:36 ubuntu-phablet powerd[949]: Emitting signal for transition to state ACTIVE (1) Apr 29 14:37:36 ubuntu-phablet powerd[949]: Transition to ACTIVE complete Apr 29 14:37:36 ubuntu-phablet powerd[949]: libsuspend: release_wake_lock: powerd_power_request Apr 29 14:37:36 ubuntu-phablet kernel: [21760.273491]mtk-tpd: TPD wake up Apr 29 14:37:36 ubuntu-phablet powerd[949]: light_dev: setting brightness to 120 Apr 29 14:37:36 ubuntu-phablet kernel: [21760.310044]mtk-tpd: TPD wake up done Apr 29 14:37:36 ubuntu-phablet kernel: [21760.310066]MAGNETIC mag_context_obj ok---hwm_obj-early_suspend=0 Apr 29 14:37:36 ubuntu-phablet powerd[949]: we get signal from :1.13: DisplayPowerStateChange Apr 29 14:37:36 ubuntu-phablet powerd[949]: Received DisplayPowerStateChange: state=1 flags=2 Since some of those messages are from the kernel ringbuffer, I looked at the corresponding dmesg output: [21606.412808] [Ker_PM][request_suspend_state]wakeup (3-0) at 21606823677239 (2015-04-29 12:35:02.572136231 UTC) [21606.953480] mtk-tpd: TPD wake up [21606.980027] mtk-tpd: TPD wake up done So there seems to be at least half a second of delay between the kernel registering the button press and the display actually being requested to power on. Since display power-on is not instant, the total time from button press to visible display content is close to a second on my device in best case, sometimes up to three seconds and in rare cases the display does not turn on at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1421455 Title: Slow wake up time on physical power button pressed Status in unity8 package in Ubuntu: Incomplete Bug description: Device: bq Aquaris E4.5 running: Stable #17 When pressing on physical power button on device to wake it up sometime it even takes up to 2-3 secs before anything appears on the screen. This time wary but its hard to tell then its shorter and when is longer. This is not so bad on nexus4. Should you need more info, I'm happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1421455/+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 1421455] Re: Slow wake up time on physical power button pressed
Looking at the strace output one can see that powerd gets the power
button press notification, processes it, and then nothing happens for
half a second:
[pid 949] 1430318963.039809 send(3, 31Apr 29 16:49:23 powerd[949]: exiting
suspend, 48, MSG_NOSIGNAL) = 48
[pid 949] 1430318963.040868 gettimeofday({1430318963, 40921}, NULL) = 0
[pid 949] 1430318963.041289 send(3, 31Apr 29 16:49:23 powerd[949]:
libsuspend: exit_suspend., 58, MSG_NOSIGNAL) = 58
[pid 949] 1430318963.042623 open(/sys/power/state, O_WRONLY) = 14
[pid 949] 1430318963.043483 write(14/sys/power/state, on, 2 unfinished
...
Note: 508 milliseconds delay
[pid 8256] 1430318963.515663 ... futex resumed ) = -1 ETIMEDOUT (Connection
timed out)
[pid 8256] 1430318963.515862 clock_gettime(CLOCK_MONOTONIC, {27280,
493365943}) = 0
[pid 8256] 1430318963.517005 clock_gettime(CLOCK_MONOTONIC, {27280,
493965482}) = 0
[pid 8256] 1430318963.518207 futex(0xaa430c, FUTEX_WAIT, 30, {14, 999399518}
unfinished ...
[pid 971] 1430318963.587966 ... read resumed a, 1) = 1
[pid 971] 1430318963.588263 close(7/sys/power/wait_for_fb_wake) = 0
[pid 971] 1430318963.589699 open(/sys/power/wait_for_fb_sleep, O_RDONLY) = 7
[pid 971] 1430318963.590953 read(7/sys/power/wait_for_fb_sleep,
unfinished ...
[pid 949] 1430318963.592034 ... write resumed ) = 2
If you look close enough you can see that pid 949 does a blocking write of the
string on to /sys/power/state, and this syscall comes back half a second
later. Half a second. Exactly the missing time we are looking for.
So I pressed the power button to turn off the screen, waited a couple of
seconds to allow the system go to sleep, and did the following:
root@ubuntu-phablet:~# time echo on /sys/power/state
real0m0.545s
user0m0.000s
sys 0m0.000s
Something in the kernel seems to take roughly half a second to wake up.
I looked at the Documentation/power/states.txt file of the Linux kernel
and was am a bit confused: There should be only four valid values one
can write to /sys/power/state, namely mem, standby, freeze and
disk. On the bq phone the file contains mem disk, so only those two
states are available. I found out that on seems to be an accepted
value on Android kernels only.
So the root of the problem my lie in kernel land at the end.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1421455
Title:
Slow wake up time on physical power button pressed
Status in powerd package in Ubuntu:
New
Status in unity8 package in Ubuntu:
Incomplete
Bug description:
Device: bq Aquaris E4.5 running: Stable #17
When pressing on physical power button on device to wake it up
sometime it even takes up to 2-3 secs before anything appears on the
screen. This time wary but its hard to tell then its shorter and when
is longer.
This is not so bad on nexus4.
Should you need more info, I'm happy to help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1421455/+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 1450026] [NEW] upowerd regularly tries to open a number of non-existant sysfs files on the bq Aquaris E4.5
Public bug reported: current build number: 21 device name: krillin channel: stable alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2015-04-29 08:25:10 version version: 21 version ubuntu: 20150410.1 version device: 20150408-4f14058 version custom: 20150409-665-29-206 I was debugging an upowerd issue with strace and found that the daemon tries to open the following non-existant files every ten seconds: [pid 2020] 1430314162.277522 open(/sys/devices/platform/battery/power_supply/battery/energy_now, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.283633 open(/sys/devices/platform/battery/power_supply/battery/energy_avg, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.288603 open(/sys/devices/platform/battery/power_supply/battery/manufacturer, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.292523 open(/sys/devices/platform/battery/power_supply/battery/model_name, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.293236 open(/sys/devices/platform/battery/power_supply/battery/serial_number, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.295228 open(/sys/devices/platform/battery/power_supply/battery/energy_full, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.295953 open(/sys/devices/platform/battery/power_supply/battery/energy_full_design, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.296704 open(/sys/devices/platform/battery/power_supply/battery/charge_full, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.297415 open(/sys/devices/platform/battery/power_supply/battery/charge_full_design, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.300221 open(/sys/devices/platform/battery/power_supply/battery/power_now, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.301404 open(/sys/devices/platform/battery/power_supply/battery/charge_now, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.302508 open(/sys/devices/platform/battery/power_supply/battery/charge_avg, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.304173 open(/sys/devices/platform/battery/power_supply/battery/charge_full, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.305134 open(/sys/devices/platform/battery/power_supply/battery/charge_full_design, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.305820 open(/sys/devices/platform/battery/power_supply/battery/current_now, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Summary changed: - upowerd regularly tries to open a number of non-existant sysfs files on the bq Aquaris E.45 + upowerd regularly tries to open a number of non-existant sysfs files on the bq Aquaris E4.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1450026 Title: upowerd regularly tries to open a number of non-existant sysfs files on the bq Aquaris E4.5 Status in upower package in Ubuntu: New Bug description: current build number: 21 device name: krillin channel: stable alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2015-04-29 08:25:10 version version: 21 version ubuntu: 20150410.1 version device: 20150408-4f14058 version custom: 20150409-665-29-206 I was debugging an upowerd issue with strace and found that the daemon tries to open the following non-existant files every ten seconds: [pid 2020] 1430314162.277522 open(/sys/devices/platform/battery/power_supply/battery/energy_now, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.283633 open(/sys/devices/platform/battery/power_supply/battery/energy_avg, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.288603 open(/sys/devices/platform/battery/power_supply/battery/manufacturer, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.292523 open(/sys/devices/platform/battery/power_supply/battery/model_name, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.293236 open(/sys/devices/platform/battery/power_supply/battery/serial_number, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.295228 open(/sys/devices/platform/battery/power_supply/battery/energy_full, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 2020] 1430314162.295953
[Touch-packages] [Bug 1427359] Re: ubuntu-device-flash fails to flash image once it reboots into recovery mode
This happened to me today on Ubuntu 14.10 with a bq Aquaris E4.5. I ran ubuntu-device-flash without any parameters. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1427359 Title: ubuntu-device-flash fails to flash image once it reboots into recovery mode Status in android-tools package in Ubuntu: Confirmed Bug description: Running Ubuntu Trusty 14.04 and the latest packages from the android- tools PPA: https://launchpad.net/~phablet-team/+archive/ubuntu/tools 1. Try to flash a krillin device via: ubuntu-device-flash touch --channel=ubuntu-touch/ubuntu-rtm/14.09 2. Observe that at the time of this bug, RTM image 19 is downloaded and pushed to the phone successfully. 3. u-d-f reboots the phone into recovery mode and you see the Ubuntu logo spinning. 4. u-d-f complains that it failed to enter recovery after about 60 seconds. See the log output for more details. [1] [1] http://pastebin.ubuntu.com/10505648/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1427359/+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 1448180] Re: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone
** Attachment added: gpsdataprovider.h https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1448180/+attachment/4383067/+files/gpsdataprovider.h -- 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/1448180 Title: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone Status in location-service package in Ubuntu: New Bug description: Device: bq Aquaris E4.5 Ubuntu Edition Operating System: Ubuntu 14.10 (r21) I am currently trying to build a clone of the GPS Status Android app, it displays various details about the built-in GPS receiver. According to the developer documentation at http://developer.ubuntu.com/api/qml/sdk-14.10/QtLocation.location- positioning-cpp/ , a call to QGeoSatelliteInfoSource::createDefaultSource() can be used to get access to the default Satellite positioning source implementation. On my device this call returns NULL. Sample code is located at https://github.com/Sturmflut/ubuntu-touch- simple-gps/tree/3da3dc5f089e698c34765fd18322b84727cb13ae , the call in question is located at backend/modules/Simplegps/gpsdataprovider.cpp . I attached the file and its header for future reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1448180/+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 1448180] [NEW] QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone
Public bug reported: Device: bq Aquaris E4.5 Ubuntu Edition Operating System: Ubuntu 14.10 (r21) I am currently trying to build a clone of the GPS Status Android app, it displays various details about the built-in GPS receiver. According to the developer documentation at http://developer.ubuntu.com/api/qml/sdk-14.10/QtLocation.location- positioning-cpp/ , a call to QGeoSatelliteInfoSource::createDefaultSource() can be used to get access to the default Satellite positioning source implementation. On my device this call returns NULL. Sample code is located at https://github.com/Sturmflut/ubuntu-touch- simple-gps/tree/3da3dc5f089e698c34765fd18322b84727cb13ae , the call in question is located at backend/modules/Simplegps/gpsdataprovider.cpp . I attached the file and its header for future reference. ** Affects: location-service (Ubuntu) Importance: Undecided Status: New ** Attachment added: gpsdataprovider.cpp https://bugs.launchpad.net/bugs/1448180/+attachment/4383066/+files/gpsdataprovider.cpp -- 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/1448180 Title: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone Status in location-service package in Ubuntu: New Bug description: Device: bq Aquaris E4.5 Ubuntu Edition Operating System: Ubuntu 14.10 (r21) I am currently trying to build a clone of the GPS Status Android app, it displays various details about the built-in GPS receiver. According to the developer documentation at http://developer.ubuntu.com/api/qml/sdk-14.10/QtLocation.location- positioning-cpp/ , a call to QGeoSatelliteInfoSource::createDefaultSource() can be used to get access to the default Satellite positioning source implementation. On my device this call returns NULL. Sample code is located at https://github.com/Sturmflut/ubuntu-touch- simple-gps/tree/3da3dc5f089e698c34765fd18322b84727cb13ae , the call in question is located at backend/modules/Simplegps/gpsdataprovider.cpp . I attached the file and its header for future reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1448180/+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
