[Touch-packages] [Bug 1453200] Re: No focusing under low light conditions

2017-03-19 Thread jose sanchez
ON the Meizu Pro5 the camera does not focus if you are trying to take a
picture with writing the picture comes out good but the text is blurry

-- 
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/1453200

Title:
  No focusing under low light conditions

Status in Canonical System Image:
  Triaged
Status in camera-app package in Ubuntu:
  Triaged

Bug description:
  Test case.
  - Under low light (but not very low) conditions
  - Open camera app.
  - Tap in settings to disable flash.
  - At a distance of 20 cm, frame a black keyboard.
  - Tap to focus in a key.

  Expected result.
  - Keys are focused.

  Actual result.
  - No focus.

  Also, if it's focused, it will unfocus.  This has been tested in Arale
  with Vivid devel-proposed 207 and krillin with Vivid and stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1453200/+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 1429887] Re: Sometimes need 3 power button presses to turn on screen

2017-01-08 Thread jose sanchez
This problem started after the ota 14 update

-- 
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/1429887

Title:
  Sometimes need 3 power button presses to turn on screen

Status in Canonical System Image:
  Incomplete
Status in Unity System Compositor:
  New
Status in powerd package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  [filing here although may be other components]

  Mako running 211 from rtm
   I experienced these symptoms which have been previously mitigated in other 
scenarios.
  Last week while traveling and roaming this happened pretty much 100% of the 
time.
  This occurred in all areas (hotel, MWC, outside, etc)

  Press power button, no response
  Press button again, screen turns on for a few seconds then turns off
  Press button again, either phone resumes or more often the power dialog is 
shown

  When I returned back home the function was normal without reboot or
  other changes.

  The differences in environment:
  Roaming on foreign GSM network
  Lots of Wifi APs not connected

  Attached are some perhaps relevant logs, unfortunately the syslog
  rolled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

2016-11-27 Thread jose sanchez
I have a pro5 and i canr hear the other person and they cant hear me.
This is my daily i sold my iphone and android as i wanted something
different. Please fix whatever you need to fix this count me in.

-- 
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/1590844

Title:
  Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2016-11-27 Thread jose sanchez
I can connect and pair perfectly on my meizu pro5 but the audio is so
bad that all you hear is static and then it hangs up he call 3 min later

-- 
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/1500242

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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