[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Photo access (gphoto2://) works in both Ubuntu 18.04 and 20.04. Documents access (afc://) works in Ubuntu 18.04 in reading mode - I can copy file from iPhone to PC. But it hangs (forever 0%) while copy one small file to iPhone device. In Ubuntu 20.04 I get errors for both case (copy file from iPhone documents to PC and with reverse direction). Can not say that Ubuntu 20.04 is better in this use case... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
No luck with Ubuntu 20.04 (trying to copy mp3 file to VLC folder on iPhone): "Error while copying test.mp3. There was error copying file into afc ://some-id/org.videolan.vlc-ios. The connection was interrupted." Something broken with iOS 13 update... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1741045] Re: Change the default resample-method to speex-float-10 in daemon.conf
http://comments.gmane.org/gmane.comp.audio.pulseaudio.general/21051 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1741045 Title: Change the default resample-method to speex-float-10 in daemon.conf Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I suggest changing the default resample-method to speex-float-10, instead of speex-float-1, which is the current default now, in /etc/pulse/daemon.conf. It would look like this in daemon.conf: resample-method = speex-float-10 I have always done that since at least 12.04 LTS. I was not satisfied with the sound quality in Ubuntu compared to Windows, so I changed the resample-method. In my day-to-day usage, it gives better sound quality without sacrificing CPU power. I have not tried other resample methods. Maybe there are better options I don't know about. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1696 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 14:37:25 2018 InstallationDate: Installed on 2017-10-02 (92 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1741045/+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 1608246] Re: Does not work button on the headphones to answer call's [Meizu PRO 5]
Same issue with OTA-13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1608246 Title: Does not work button on the headphones to answer call's [Meizu PRO 5] Status in dialer-app package in Ubuntu: New Bug description: Call answer with headset button does not work. Checked on Meizu PRO 5 with OTA-12 and with several wired headset. PS: Works fine on BQ Aquaris e4.5 Ubuntu edition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1608246/+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 1608246] [NEW] Does not work button on the headphones to answer call's [Meizu PRO 5]
Public bug reported: Call answer with headset button does not work. Checked on Meizu PRO 5 with OTA-12 and with several wired headset. PS: Works fine on BQ Aquaris e4.5 Ubuntu edition. ** Affects: dialer-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 dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1608246 Title: Does not work button on the headphones to answer call's [Meizu PRO 5] Status in dialer-app package in Ubuntu: New Bug description: Call answer with headset button does not work. Checked on Meizu PRO 5 with OTA-12 and with several wired headset. PS: Works fine on BQ Aquaris e4.5 Ubuntu edition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1608246/+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 1489784] Re: No access to the FM tuner/radio on Meizu MX4, Aquaris Bq e4.5, e5 and m10
Meizu MX4 hasn't FM radio support by hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1489784 Title: No access to the FM tuner/radio on Meizu MX4, Aquaris Bq e4.5, e5 and m10 Status in Canonical System Image: In Progress Status in media-hub package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in qtmultimedia package in Ubuntu: Confirmed Bug description: Device Aquaris BQ45 as a buitin hardware FM tuner. On "factory" mode this device works. The device does not seem known by the kernel and there is no API to develop an FM radio application. The C code for the FM chip: https://github.com/Sturmflut/mtkfmcli Still missing Audio part. Some more details from mailing list: We discussed this topic lengthily on the list some time ago :) It's not like we don't want to support FM radio, but the lack of a common Android HAL for FM radio access would force us to maintain an FM radio abstraction ourselves (more on that below). In addition, most of the device-specific radio apps require elevated privileges to run as they directly access the FM radio HW (not multiplexed by a system service). > For some reason Android doesn't have an FM radio API and leaves it up to > the manufacturers to come up with something. I've looked at several > devices, among them the bq Aquaris E4.5, and every SoC manufacturer > seems to have a different opinion on how to do it. > > Some ship no FM radio at all. > > Some seem to ship drivers for the Linux V4L subsystem. > > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel > drivers with a custom character device (/dev/fm) and custom ioctl > commands. There seem to be userspace libraries (libfm*) including a JNI > wrapper in /system/lib of the Android container on our Ubuntu phones. > > Because there is no standard API, there are no generic FM radio apps for > Android, and pretty much every manufacturer ships a custom app for his > own SoC(s) and/or device(s). > > > I'll try to come up with a piece of C code for the command line that can > at least initialize and tune the FM radio on the Aquaris E4.5 and E5. > The long-term goal could be to turn this into plugins for an extended > media-hub. > If you are interested in helping to enable the functionality, the correct chain for integrating the feature would be: [1.] Add a (potentially limited) API to lp:platform-api, that exposes a simple common C interface to the Ubuntu side. [2.] Provide an implementation of the API in platform-api/android (see http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/) [2.1] Provide a dummy fallback implementation for devices that do not support FM radio of any kind. [3.] Expose the respective hardware functionality to media-hub. Multiple ways are possible, but we would need to significantly adjust the interfaces to support fm radio semantics (switching stations, rds, automatic scans etc.) [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch specific backend implementation, that either: [4.1] Leverages the API in [1.] directly (would require any app to have special privileges in accessing the system). [4.2] Leverages the API in [3.] (which is the clean way of integration FM radio support). For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get started. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1489784/+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 1445913] Re: System hangs on restart on the Bq Aquaris 4.5
Press and hold power + volume up buttons for about 8 seconds -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1445913 Title: System hangs on restart on the Bq Aquaris 4.5 Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: It now happened the second time that I was not able to initiate a restart of the system on my Bq Aquaris 4.5. This happened after I pressed the power button for a few seconds and afterwards selected the restart option. Other symptoms are: - The white screen with the black bq logo does not appear. - Instead, a pale violet background is permanently shown. Backlight of the display is on. - The phone cannot be turned off by pressing the power button for longer. - If the phone is connected to my desktop using an USB cable, the device is recognized but cannot be mounted. Since the battery cannot be physically removed on that phone, the only option to solve the situation was for me to let it run out of battery power until it turns off by itself. Afterwards, the phone can be put to live again after connecting the power cable. It appears as if the phone is hanging in the boot loader. The problem may be more prevalent when battery power is already low (50%) the time the restart is initiated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1445913/+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
