from:"Salem"

** Branch linked: lp:~tiagosh/messaging-app/forward-support

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

Title:
  [messaging] Ability to forward SMS without copy 'n past approach

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if the SMS app swipe left context had the ability to forward 
the SMS to other receivers.
  The existing approah where one can swipe left and copy the content and then 
paste into a new SMS seems less intuitive.

  **

  This feature is in the new designs but has yet to be implemented.
  https://docs.google.com/presentation/d/1hkrF2g-
  ad7fhJ0UVLKmu_5ZXSFK1EkcWS129JxmAAI4/edit#slide=id.p97

  **

  This is a certification requirement

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461873/+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 1588127] Re: Phone abandons incoming call

I am seeing timeout from the approver while trying to create an instance
of media-hub in the dbus.log file.

Media-hub is a telepathy observer (it watches telepathy to stop music
when there is an incoming call), and telepathy by design won't forward
the incoming call to the approver (to display the snap decision) until
all observers confirm receiving the incoming channel first.

If media-hub is really stuck for some reason, that would explain the
issue, since after a dbus timeout trying to deliver the channel to
media-hub, telepathy would still try to deliver the channel to the
approver, which would make the snap decision appear, and quickly
disappear (since the incoming call is already gone).

This is a guess, but seems to match what Matthew described, and what I
see in the logs:

-

virtual QMediaService* AalServicePlugin::create(const QString&)
"org.qt-project.qt.mediaplayer"
Failed to start a new media-hub player session:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
Failed to create a new media player backend. Video playback will not function.

Could not finish contructing new AalMediaPlayerService instance since
m_hubPlayerSession is NULL



-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+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 1588127] Re: Phone abandons incoming call

Thanks for the logs,
could you also grab the dbus logs using the steps I provided on comment #6 
using adb?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+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 1588127] Re: Phone abandons incoming call

you just need to ssh the device and run the same commands:

$  dbus-monitor > call_dbus-session.log
$  dbus-monitor --system > call_dbus-system.log

then attach the files to the bug report.
Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+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 1588127] Re: Phone abandons incoming call

sorry, I just read your comment where you say you're not able to use adb.
Can you access the phone over ssh somehow?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+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 1588127] Re: Phone abandons incoming call

2016-06-08 Thread Tiago Salem Herrmann

Could you also attach .cache/upstart/dbus.log? And if you are able to
reproduce it easily, it would be good to also grab two additional logs
using the following steps:

connect the device in development mode via usb in your desktop and run:

1) adb shell dbus-monitor > call_dbus-session.log
2) in another terminal run: adb shell dbus-monitor --system > 
call_dbus-system.log
3) receive a call and reproduce the bug
4) attach both call_dbus-session.log and call_dbus-system.log to the bug report.

thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+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 1585791] Re: Clicking on links doesn't work

2016-05-25 Thread Tiago Salem Herrmann

This is the commit that broke clicking the links:

http://bazaar.launchpad.net/~phablet-team/address-book-
app/trunk/revision/586

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1585791

Title:
  Clicking on links doesn't work

Status in address-book-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Links in text messages don't work any more since krillin image 342.

  the diff:

  http://pastebin.ubuntu.com/16693187/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1585791/+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 1568750] Re: With dual SIM, SIM choice is not retained for a SMS conversation

2016-04-29 Thread Tiago Salem Herrmann

The feature to restore a previous sim selection in a given conversation was 
never part of the design spec, thus it was never implemented.
The current behavior is that messaging-app must always use the sim card 
selected as default in system-settings.

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

Title:
  With dual SIM, SIM choice is not retained for a SMS conversation

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  For an existing SMS conversation with one contact (when using dual
  SIM):

  Expected behaviour: tap on conversation in messaging-app, the
  messaging screen opens showing the SMS conversation, with the
  previously used SIM selected.

  Actual behaviour: SIM #1 is always selected, even if all previous SMS
  messages to that contact have used SIM #2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1568750/+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 1571686] Re: "Ask me each time" for SMS does not work

2016-04-28 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/messaging-app/fix-sections-dualsim

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

Title:
  "Ask me each time" for SMS does not work

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  New

Bug description:
  BQ Aquaris E4.5 with OTA 10.1
  Settings "Ask me each time" in "For messages, use" in "Cellular" in "Settings"

  I am using 2 SIM cards and since the beginning of my usage (started
  with release21 this settings was working as expected -> when I wanted
  to send SMS and did not select SIM card by myself (so no SIM card was
  highlighted in the Messages app), I was asked to select one.

  Since some time (OTA-9?) there is always (first one) SIM card selected
  despite the above mentioned settings. And, by whatever reason
  sometimes the SMS is send from other then selected SIM card. Because
  it is now happening much more often and I see that "nice" info: "You
  switched to XXX XX" (PS: no I did not!), it becomes really annoying (I
  have one SIM card in roaming mode) and people are receiving my
  messages from different number and therefore I decided to open this
  bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1571686/+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 1571094] Re: /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone-gsettings-migration.py@27:call:call_blocking

2016-04-15 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/telephony-service/fix-migration-script

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1571094

Title:
  /usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone-
  gsettings-migration.py@27:__call__:call_blocking

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+15.04.20160411-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/e33f885bbc5d071b30c62ddbad840cf30b893ef4
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1571094/+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 1565103] [NEW] bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app

2016-04-01 Thread Tiago Salem Herrmann

Public bug reported:

A new bottom edge wizard is being displayed in the recent images, but
there are cases where it is being displayed when it shouldn't.

Steps to reproduce:

1) Flash the phone with --wipe.
2) Before opening dialer-app, lock the phone and receive a call.
3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

Another case is when launching messaging-app or dialer-app. we have a
first time dialog that appears behind the wizard. Not sure if that's
expected, but seems to cause a bad user experience to me.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  bottom edge first time wizard is being incorrectly displayed on
  dialer-app and messaging-app

Status in unity8 package in Ubuntu:
  New

Bug description:
  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.

  Steps to reproduce:

  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

  Another case is when launching messaging-app or dialer-app. we have a
  first time dialog that appears behind the wizard. Not sure if that's
  expected, but seems to cause a bad user experience to me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1565103/+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 1563711] Re: Can't enable loudspeaker during a call on krillin

2016-03-30 Thread Tiago Salem Herrmann

Thanks for the report.

If you manage to reproduce that again, please grab the dbus-monitor logs, 
also try to switch to another app, then back to dialer and try enabling the 
speaker mode again.

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

Title:
  Can't enable loudspeaker during a call on krillin

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  New

Bug description:
  I noticed yesterday that the loudspeaker button doesn't do anything on
  my krillin during a call.

  Couldn't find anything in the logs, I'm afraid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dialer-app 0.1+15.04.20160317-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Wed Mar 30 09:54:55 2016
  InstallationDate: Installed on 2016-03-30 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160330-020304)
  SourcePackage: dialer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563711/+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 1550582] Re: Cant delete messages

2016-03-30 Thread Tiago Salem Herrmann

Hi Arnaud,

looks like the issue you describe is a different bug. I believe we have
the similar bug for dialer already reported here:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1407977

It's a different app, but the root cause of both bugs is the same.

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

Title:
  Cant delete messages

Status in Canonical System Image:
  Incomplete
Status in messaging-app package in Ubuntu:
  Incomplete

Bug description:
  I swipe to the right to reveal the red delete icon. I tap, and the app
  freezes for around 30 seconds. Then the message is still there. E4.5,
  OTA9.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550582/+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 1475102] Re: The "call waiting "function is incomplete (Just for operator)

2016-03-25 Thread Tiago Salem Herrmann

Hi, thanks for the log,

but it seems you did not use adb shell to run dbus-monitor.
This log is from your desktop, not the phone.
Can you make sure the following command is executed?

adb shell dbus-monitor --system interface=org.ofono.VoiceCallManager >
call_waiting.log

thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1475102

Title:
  The "call waiting "function is incomplete (Just for operator)

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  Incomplete

Bug description:
  $ system-image-cli -i
  current build number: 57
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-10 02:04:41
  version version: 57
  version ubuntu: 20150709
  version device: 20150709-8965e37
  version custom: 20150709-814-6-40

  Reproduce Steps:
  1,System settings-->Phone-->Turn the Call waiting ON
  2,Call to operator(Unicom 10010 China mobile 10086)
  3,Keep the DUT is on the phone
  4,Make the another phone to DUT

  Expect Result:
  The user can answer the another call

  Actual Result:
  The DUT can't answer the another phone (call waiting is not work for operator 
)
  But for Android OS ,it's work fine for operator,And IOS can support 
"End#accept"Please  check it !

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475102/+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 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

2016-03-22 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/messaging-app/remove-gsettings

** Branch linked: lp:~tiagosh/telephony-service/default-sim-for-calls

** Branch linked: lp:~tiagosh/telepathy-ofono/use-accounts-service

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

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+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 1558778] [NEW] long press on attachments closes the osk

2016-03-19 Thread Tiago Salem Herrmann

Public bug reported:

1)  open messaging-app and add an attachment
2) tap the input field as if you were going to type a message
3) once the osk opens, long press the attachment to get the "remove" popup 
button.

Expected behavior:
The osk should remain open

Current behavior:
notice that the osk is closed and the popup remains on screen.

** Affects: messaging-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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1558778

Title:
  long press on attachments closes the osk

Status in messaging-app package in Ubuntu:
  New

Bug description:
  1)  open messaging-app and add an attachment
  2) tap the input field as if you were going to type a message
  3) once the osk opens, long press the attachment to get the "remove" popup 
button.

  Expected behavior:
  The osk should remain open

  Current behavior:
  notice that the osk is closed and the popup remains on screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1558778/+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 1558780] [NEW] contact profile empty when opened from a recents entry

2016-03-19 Thread Tiago Salem Herrmann

Public bug reported:

1) Open dialer-app
2) open the recents page (bottom edge)
3) swipe left any entry from a known contact and click the profile button

Expected behavior:
Contact profile displayed

Current behavior:
Contact profile page is displayed empty

** 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/1558780

Title:
  contact profile empty when opened from a recents entry

Status in dialer-app package in Ubuntu:
  New

Bug description:
  1) Open dialer-app
  2) open the recents page (bottom edge)
  3) swipe left any entry from a known contact and click the profile button

  Expected behavior:
  Contact profile displayed

  Current behavior:
  Contact profile page is displayed empty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1558780/+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 1546079] Re: [France]SMS aren't sent to their destinations or are received in the same device

2016-03-10 Thread Tiago Salem Herrmann

Hi,

can you confirm if you tried to send a message to your own number before
sending a message to other contact?

There was a bug that got recently fixed that if you first send a message
to your own number, all subsequent messages sent to other contacts could
end up being sent to your own number.

Does this behavior persist after a reboot? If not, try sending a message
to yourself and check if the behavior is reproduced.

thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1546079

Title:
  [France]SMS aren't sent to their destinations or are received in the
  same device

Status in Canonical System Image:
  Incomplete
Status in address-book-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  2 French customers have reproduced this behaviour after OTA-9 we're
  still collecting information from them.

  Product: bq Aquaris E4.5 & E5
  FW version: OTA-9

  Preconditions:

  STEPS TO REPRO:
  1. Compose an SMS.
  2. Check on the other side if the SMS was received.
  3. Check your own SMS box

  Actual Result:
  SMS are received back in the device or sent to another unwanted contacts
  Expected Result:
  SMS messages should be sent to the contact selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546079/+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 1471680] Re: there is no copy and paste options when long pressing the number in dialer

2016-03-02 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/dialer-app/add-copy-and-paste

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

Title:
  there is no copy and paste options when long pressing the number in
  dialer

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  current build number: 47
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-06 05:43:41
  version version: 47
  version ubuntu: 20150706
  version device: 20150701-cdd791c
  version custom: 20150602-731-5-32

  Steps:
1.open the dialer app
2.input some numbers 
3.long press the numbers 

  Expectations:
After step3#,the numbers should be chosen and there will be two options: 
copy,select

  Actual result: after step3#, there is nothing appears

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471680/+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 1547462] Re: [notification] all received messages are not always played back

2016-03-02 Thread Tiago Salem Herrmann

The real cause is that we skip notifications when the sender phone number 
matches the sim card number that received that message.
The fix is on the way.

Thanks for all the information and for taking time to help us fix this
bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1547462

Title:
  [notification] all received messages are not always played back

Status in Canonical System Image:
  Triaged
Status in telephony-service package in Ubuntu:
  New

Bug description:
  Here is another case where received messages are not notified:
  SMS messages sent directly from my operator to my number.
  To do so I need to send the SMS into a formatted url (Percent-encoding) from
  my operator web site: example: to send the message "Hello World !"
  on the mobile connect to :
  
https://smsapi.free-mobile.fr/sendmsg?user=login=password=Hello%20World%20!

  As well the login/password is the one supplied by my operator.

  This kind of SMS message will not be notified when it arrives in my BQ 
Aquaris Phone.
  Other notifications work well. This problem did not exist before OTA-9

  Expected Result: This SMS also should give sound notification.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 29
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2016-01-28 09:44:29
  version version: 29
  version ubuntu: 20160123.1
  version tag: OTA-9
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid
  phablet@ubuntu-phablet:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547462/+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 1547462] Re: [notification] all received messages are not always played back

2016-03-01 Thread Tiago Salem Herrmann

Thank you.

Could you also run the following commands as soon as the bug is
reproduced and then attach the output files here (indicator_observer.log
and indicator_backtrace.log) ?

1) dbus-send --print-reply
--dest=com.canonical.TelephonyServiceIndicator
/org/freedesktop/Telepathy/Client/TelephonyServiceIndicator
org.freedesktop.DBus.Properties.Get
string:org.freedesktop.Telepathy.Client.Observer
string:ObserverChannelFilter &> indicator_observer.log

2) sudo gdb --batch -ex "thread apply all bt full" -p $(pidof telephony-
service-indicator) > indicator_backtrace.log


Some more questions:

1)  what happens if you receive an sms from any other number after the
bug is reproduced? Does it behave correctly? or once the bug is
reproduced it always happens until you reboot?

2) Can you check if the count of received sms's in the welcome screen
increase when you get these messages?

3) When you get the message from your operator, is the recipient number
in messaging-app the same as your own sim card phone number? Or is this
a carrier service phone number?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1547462

Title:
  [notification] all received messages are not always played back

Status in Canonical System Image:
  Triaged
Status in telephony-service package in Ubuntu:
  New

Bug description:
  Here is another case where received messages are not notified:
  SMS messages sent directly from my operator to my number.
  To do so I need to send the SMS into a formatted url (Percent-encoding) from
  my operator web site: example: to send the message "Hello World !"
  on the mobile connect to :
  
https://smsapi.free-mobile.fr/sendmsg?user=login=password=Hello%20World%20!

  As well the login/password is the one supplied by my operator.

  This kind of SMS message will not be notified when it arrives in my BQ 
Aquaris Phone.
  Other notifications work well. This problem did not exist before OTA-9

  Expected Result: This SMS also should give sound notification.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 29
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2016-01-28 09:44:29
  version version: 29
  version ubuntu: 20160123.1
  version tag: OTA-9
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid
  phablet@ubuntu-phablet:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547462/+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 1547462] Re: [notification] all received messages are not always played back

2016-03-01 Thread Tiago Salem Herrmann

Thank you.

I have some more questions:

1) Does the phone vibrate even you get the message?
2) Is messaging-app open? Can you reproduce it also with messaging-app closed?
3) Once you reproduce the bug, can you check if telephony-service-indicator is 
running with "ps -aux | grep telephony-service-indicator"

Thank you

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1547462

Title:
  [notification] all received messages are not always played back

Status in Canonical System Image:
  Triaged
Status in telephony-service package in Ubuntu:
  New

Bug description:
  Here is another case where received messages are not notified:
  SMS messages sent directly from my operator to my number.
  To do so I need to send the SMS into a formatted url (Percent-encoding) from
  my operator web site: example: to send the message "Hello World !"
  on the mobile connect to :
  
https://smsapi.free-mobile.fr/sendmsg?user=login=password=Hello%20World%20!

  As well the login/password is the one supplied by my operator.

  This kind of SMS message will not be notified when it arrives in my BQ 
Aquaris Phone.
  Other notifications work well. This problem did not exist before OTA-9

  Expected Result: This SMS also should give sound notification.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 29
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2016-01-28 09:44:29
  version version: 29
  version ubuntu: 20160123.1
  version tag: OTA-9
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid
  phablet@ubuntu-phablet:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547462/+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 1475102] Re: The "call waiting "function is incomplete (Just for operator)

2016-03-01 Thread Tiago Salem Herrmann

looks like you ran dbus-monitor while making the call to the operator.

Could you run again before your receive the second call (waiting call)?

thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1475102

Title:
  The "call waiting "function is incomplete (Just for operator)

Status in Canonical System Image:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged

Bug description:
  $ system-image-cli -i
  current build number: 57
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-10 02:04:41
  version version: 57
  version ubuntu: 20150709
  version device: 20150709-8965e37
  version custom: 20150709-814-6-40

  Reproduce Steps:
  1,System settings-->Phone-->Turn the Call waiting ON
  2,Call to operator(Unicom 10010 China mobile 10086)
  3,Keep the DUT is on the phone
  4,Make the another phone to DUT

  Expect Result:
  The user can answer the another call

  Actual Result:
  The DUT can't answer the another phone (call waiting is not work for operator 
)
  But for Android OS ,it's work fine for operator,And IOS can support 
"End#accept"Please  check it !

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475102/+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 1550582] Re: Cant delete messages

2016-02-29 Thread Tiago Salem Herrmann

Hi,

do you have access to the device over adb? if so, could you run "adb shell 
dbus-monitor > history.log"
and try removing the message again?

Then attach history.log here.

Thanks

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

Title:
  Cant delete messages

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

Bug description:
  I swipe to the right to reveal the red delete icon. I tap, and the app
  freezes for around 30 seconds. Then the message is still there. E4.5,
  OTA9.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550582/+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 1549352] Re: New message to contact only opens messaging app

2016-02-25 Thread Tiago Salem Herrmann

** Branch unlinked: lp:~tiagosh/messaging-
app/set_width_based_on_screen_size

** Branch linked: lp:~tiagosh/messaging-app/fix_leaks_and_empty_view

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

Title:
  New message to contact only opens messaging app

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Open Contacts app.
  - Add a new contact with a phone number.
  - Save the contact.
  - On the contact list, tap on the contact.
  - Tap on the messaging button to send a message to the contact.

  Expected result.
  - Messaging app is opened but the message list is displayed, instead of the 
screen to write the message to the contact.

  Through Dialer app, the message creation screen is opened correctly.

  current build number: 266
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549352/+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 1547462] Re: [notification] all received messages are not always played back

2016-02-25 Thread Tiago Salem Herrmann

Thank you!

from the logs I can't tell much yet where the problem is,

could you run "dbus-monitor > dbus.log" as phablet user and after you
reproduce the issue just press ctrl+c and attach dbus.log file here?

You can remove the phone number from the logs before attaching it if you
wish.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1547462

Title:
  [notification] all received messages are not always played back

Status in Canonical System Image:
  Triaged
Status in telephony-service package in Ubuntu:
  New

Bug description:
  Here is another case where received messages are not notified:
  SMS messages sent directly from my operator to my number.
  To do so I need to send the SMS into a formatted url (Percent-encoding) from
  my operator web site: example: to send the message "Hello World !"
  on the mobile connect to :
  
https://smsapi.free-mobile.fr/sendmsg?user=login=password=Hello%20World%20!

  As well the login/password is the one supplied by my operator.

  This kind of SMS message will not be notified when it arrives in my BQ 
Aquaris Phone.
  Other notifications work well. This problem did not exist before OTA-9

  Expected Result: This SMS also should give sound notification.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 29
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2016-01-28 09:44:29
  version version: 29
  version ubuntu: 20160123.1
  version tag: OTA-9
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid
  phablet@ubuntu-phablet:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547462/+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 1547462] Re: [notification] all received messages are not always played back

2016-02-25 Thread Tiago Salem Herrmann

Hi, can you check if you have any telephony-service-indicator crash file
in /var/crash ?

Also, check if you get any suspicious message in $HOME/.cache/upstart
/telephony-service-indicator.log by the time you receive those sms's.

Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1547462

Title:
  [notification] all received messages are not always played back

Status in Canonical System Image:
  Triaged
Status in telephony-service package in Ubuntu:
  New

Bug description:
  Here is another case where received messages are not notified:
  SMS messages sent directly from my operator to my number.
  To do so I need to send the SMS into a formatted url (Percent-encoding) from
  my operator web site: example: to send the message "Hello World !"
  on the mobile connect to :
  
https://smsapi.free-mobile.fr/sendmsg?user=login=password=Hello%20World%20!

  As well the login/password is the one supplied by my operator.

  This kind of SMS message will not be notified when it arrives in my BQ 
Aquaris Phone.
  Other notifications work well. This problem did not exist before OTA-9

  Expected Result: This SMS also should give sound notification.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 29
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2016-01-28 09:44:29
  version version: 29
  version ubuntu: 20160123.1
  version tag: OTA-9
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid
  phablet@ubuntu-phablet:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547462/+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 1518344] Re: "Swipe to reveal actions" label needs more space.

2016-02-23 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/messaging-app/fix_swipe-demo_text_position

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

Title:
  "Swipe to reveal actions" label needs more space.

Status in Canonical System Image:
  Triaged
Status in messaging-app package in Ubuntu:
  In Progress

Bug description:
  Hi!

  I translated the following string to Hungarian:

  "Swipe to reveal actions"

  But it needs more space (see attached screenshot). Additional info: In
  the Phone app the same translation looks okay.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518344/+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 1546094] [NEW] messaging-app apparmor profile deny reading dconf files

2016-02-16 Thread Tiago Salem Herrmann

Public bug reported:

Messaging-app is now running confined, but it can't recover some
settings as read access to /home/phablet/.config/dconf/user  is getting
denied by the apparmor profile by default.

This is currently causing problems to read the default sim card for
messages and the mms group chat option under the settings panel.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

** Branch linked: lp:~tiagosh/messaging-app/allow-reading-dconf-files

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

Title:
  messaging-app apparmor profile deny reading dconf files

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Messaging-app is now running confined, but it can't recover some
  settings as read access to /home/phablet/.config/dconf/user  is
  getting denied by the apparmor profile by default.

  This is currently causing problems to read the default sim card for
  messages and the mms group chat option under the settings panel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1546094/+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 1513082] Re: Ringtone in silent mode not playing on wired headsets

2016-02-05 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/telephony-service/headset-silent-mode

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1513082

Title:
  Ringtone in silent mode not playing on wired headsets

Status in Canonical System Image:
  Confirmed
Status in telepathy-ofono package in Ubuntu:
  Confirmed

Bug description:
  Currently telepathy-ofono changes the audio route according to its internal 
state.
  Considering that the audio route affects other components like 
telephony-service-approver/indicator, the audio routing should be done in 
telephony-service instead.

  Cases like playing ringtones in the headset while in silent mode, and
  handling incoming calls from other connection managers (sip for
  example) will require the audio routing being done in telephony-
  service as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513082/+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 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)

2016-02-04 Thread Tiago Salem Herrmann

The SIM information on the incoming call screen is about the sim card
that's receiving the call from that contact, and not the sim card where
that contact was originally stored.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1460301

Title:
  [Dialer] Incoming call - no info which SIM card was called (dual SIM)

Status in Canonical System Image:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in telephony-service package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 14.10 (r22)

  (Don't know how to find a package version :/, but I checked for
  updates on 29-05-2015 and all apps are up to date)

  I have two SIM cards inserted into BQ Aquaris 4.5

  On incoming call I expect to see information if SIM1 or SIM2 was dialled by 
caller alongside caller ID.
  I see only caller ID.

  It may be useful if one of the SIM cards is in roaming, or when one of
  the SIMs is a company number while other is a private number.

   UX comment ---

  The SIM card indication should replace the "Incoming call" text. This
  applies only for dual SIM devices. On a single SIM device the
  "Incoming call" labe remains. Please see attached wireframe for the
  exact solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1460301/+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 1518344] Re: "Swipe to reveal actions" label needs more space.

2016-02-02 Thread Tiago Salem Herrmann

** Branch linked: lp:~radonapps/messaging-app/fix_swipe-
demo_text_position

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

Title:
  "Swipe to reveal actions" label needs more space.

Status in Canonical System Image:
  Triaged
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  I translated the following string to Hungarian:

  "Swipe to reveal actions"

  But it needs more space (see attached screenshot). Additional info: In
  the Phone app the same translation looks okay.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518344/+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 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

2016-02-02 Thread Tiago Salem Herrmann

Yes, this is still an issue. We agreed with Alfonso that ofono will use 
AccountsService to get the default sim card for calls.
It needs some work on telephony-service and system-settings.

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

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+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 1535297] Re: Unity8 crashes on session logout on desktop

2016-01-27 Thread Tiago Salem Herrmann

It is possible to link libphonenumber against protobuf-lite with this
patch: http://pastebin.ubuntu.com/14680746/ .

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1535297

Title:
  Unity8 crashes on session logout on desktop

Status in Mir:
  Invalid
Status in libphonenumber package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is happening on a fresh setup, which is basically:
  Xenial 17Jan iso + unity8-desktop-session-mir package

  When I logout, I get a black screen. Turns out unity8 is crashing with
  a "double free or linked list corruption"

  Please find unity8.log attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1535297/+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 1512132] Re: sometimes no ring for incoming calls.

2016-01-25 Thread Tiago Salem Herrmann

It seems to me that media-hub is crashing at the time approver tries to
play the ringtone. The workaround we landed makes sure the next incoming
calls will work without rebooting the device, but not the one that
actually crashed media-hub.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1512132

Title:
  sometimes no ring for incoming calls.

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  In Progress

Bug description:
  This is similar, but not equal to this:

  https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338

  After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls.
  It vibrates, the led blinks, but no sound at all. The phone isn't
  muted and toggle the related function doesn't affect the problem - the
  phone remains muted and only a reboot let the ringer work again for a
  while. after that the problem returns.

  when the problem presents, telephone-service-indicator.log reports:

  void CallManager::onCallEnded()
  void CallManager::onCallEnded()
  TelephonyService/MessagingMenu: Calling back "+"
  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  void CallManager::onCallEnded()
  void CallManager::onCallEnded()
  void CallManager::onCallEnded()

  ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' 
doesn't exist
  void CallManager::onCallEnded()
  void CallManager::onCallEnded()

  system-image-cli -i

  current build number: 28
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-12-17 18:07:06
  version version: 28
  version ubuntu: 20151210
  version tag: OTA-8.5
  version device: 20150821-736d127
  version custom: 2015--36-46-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1533659] Re: Sending rotated picture by MMS will send the original one

2016-01-13 Thread Tiago Salem Herrmann

The picture received from content-hub is correctly rotated. I believe
some component in messaging app is not respecting the Orientation exif
property.

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

Title:
  Sending rotated picture by MMS will send the original one

Status in Canonical System Image:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  How to reproduce it : take a picture, modify it by rotating it once, go back 
to the picture and share it by MMS.
  Expected result: rotated picture sent
  Actual result: original (before modification) picture sent

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533659/+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 1532899] Re: Group chat sometimes misses messages with Unknown Number Message not found

2016-01-11 Thread Tiago Salem Herrmann

Nuntium is signaling MessageAdded without "Sender", and the attachment file 
contains "message not found".
In the nuntium log we can find the following message:

2016/01/11 14:16:18 Cannot upload m-notifyresp.ind encoded file
/home/phablet/.cache/nuntium/store/a53fcb01bc22bbfaa2812221d3596d0f.m-notifyresp.ind
to message center: NETWORK ERROR

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

Title:
  Group chat sometimes misses messages with Unknown Number Message not
  found

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  New

Bug description:
  This happened the last two times I received group chat messages.
  Several messages were not listed in the chat but rather under an
  Unknown Number contact with content Message no found.

  I see 4 such entries for the time covered in the log files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532899/+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 1528625] Re: messaging-app should run confined

2016-01-08 Thread Tiago Salem Herrmann

** Branch linked: lp:~phablet-team/messaging-app/add-apparmor-profile

** Branch linked: lp:~tiagosh/apparmor-easyprof-ubuntu/messaging-app-
confinement

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

Title:
  messaging-app should run confined

Status in Canonical System Image:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  We're introducing the ability to record audio clips from the
  messaging-app which will record voice using the microphone.  This
  requires trust-store integration for the prompts and we've been told
  making the app confined will allow us to get this for free.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528625/+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 1529903] Re: Blank message in a group sms

2016-01-05 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/telephony-service/update-mms-flag

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1529903

Title:
  Blank message in a group sms

Status in Canonical System Image:
  Confirmed
Status in telepathy-ofono package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  MX4 running 201

  Received an incoming text to an existing group
  A notification was shown and added to the indicator
  The message content was empty as was the contact info
  Other members in the group received the SMS properly and subsequent messages 
were displayed correctly.
  There is no entry shown in the messaging app
  There is no crash file

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1529903/+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 1523722] Re: /usr/bin/telephony-service-approver:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:cxxabiv1::cxa_throw:core::dbus::Bus::send_wit

2016-01-05 Thread Tiago Salem Herrmann

** Also affects: qtubuntu-media (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- 
/usr/bin/telephony-service-approver:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most
+ Crash when deleting QMediaPlayer instance

** Changed in: qtubuntu-media (Ubuntu)
 Assignee: (unassigned) => Jim Hodapp (jhodapp)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1523722

Title:
  Crash when deleting QMediaPlayer instance

Status in Canonical System Image:
  Confirmed
Status in qtubuntu-media package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+16.04.20151119-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8f663af0b140859566ab5cf21a4ad6e5eb7b6fc0
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523722/+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 1523722] Re: Crash when deleting QMediaPlayer instance

2016-01-05 Thread Tiago Salem Herrmann

I am guessing this crash started to happen when we introduced the following 
change:
http://bazaar.launchpad.net/~phablet-team/telephony-service/trunk/revision/1144

It essentially pauses the stream and delete the old instance before creating a 
new one.
The backtrace shows an exception is raised in 
core::dbus::Bus::send_with_reply_and_block_for_at_most, and another thread 
shows a __pthread_cond_wait(), can it be some sort of deadlock on deletion?

** Changed in: telephony-service (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1523722

Title:
  Crash when deleting QMediaPlayer instance

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  New
Status in qtubuntu-media package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+16.04.20151119-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8f663af0b140859566ab5cf21a4ad6e5eb7b6fc0
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523722/+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 1527187] Re: Unable to hang up outgoing call

2015-12-22 Thread Tiago Salem Herrmann

dialer-app only update existing calls in the live call screen when it is in 
foreground. (we unregister the telepathy observer when it's in background to 
avoid other problems).
If you lock the device with dialer-app open, then unlock it, it is still 
reported as inactive by Qt.application.active.
If we try to make a call in this state, the app won't be able to control it. 
(including the hangup button not working)
Once we swipe the app to background and then foreground again it works again, 
and Qt.application.active reports the right state.

Did we land any change to the dialer-app focus logic on unity recently?

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

Title:
  Unable to hang up outgoing call

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  When I make an outgoing call, I am unable to hang up. I can do so only
  by changing to another app and then return to the dialer-ap.

  Step to reproduce:

  1.) Open the dialer-app
  2.) Start an outgoing call
  3.) Try to hang up by pushing the hang-up button

  Then the hang-up button is unresponsive.

  Further steps to workaround

  4.) Swipe from the right and switch to another application
  5.) A green panel appears on the top of the screen.
  6.) Click the green panel to return to the call
  7.) Now the hang up button works and you an hang up the call

  My System is the following: (I will translate some descriptions from german):
  - Hardware: BQ Aquaris 4.5 Ubuntu Version

  From Settings->Device Information-> Operating System :
  - OS-Build Number:  OTA-8.5
  - Ubuntu-Image-Part: 20151210
  - Ubuntu-Build-Description: Ubuntu 15.04 -armhf (20151210-005527)
  - Device-Image-Part: 20150821-736d127
  - Device-Builde-Description: KRILIN01A-S15A_BQ_L100EN_2028_151210
  - Adaption-Image-Part: 2015--36-46-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527187/+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 1528668] [NEW] dialer-app not getting focused after screen unlock

2015-12-22 Thread Tiago Salem Herrmann

Public bug reported:


Steps to reproduce:

1) open dialer-app
2) lock the screen
3) unlock the screen

Expected behavior:
Qt.application.active == true

Current behavior
Qt.application.active == false until we manually switch the app to 
background/foreground again.

Additional info:
This is causing a bigger issue in the dialer-app functionality. It currently 
only refreshes the live call view when in foreground, so
when dialer is in this state, calls are placed but the call controls don't work 
(like hangup or speaker mode).

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  dialer-app not getting focused after screen unlock

Status in unity8 package in Ubuntu:
  New

Bug description:
  
  Steps to reproduce:

  1) open dialer-app
  2) lock the screen
  3) unlock the screen

  Expected behavior:
  Qt.application.active == true

  Current behavior
  Qt.application.active == false until we manually switch the app to 
background/foreground again.

  Additional info:
  This is causing a bigger issue in the dialer-app functionality. It currently 
only refreshes the live call view when in foreground, so
  when dialer is in this state, calls are placed but the call controls don't 
work (like hangup or speaker mode).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1528668/+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 1522150] Re: Cut off messages

2015-12-08 Thread Tiago Salem Herrmann

In this case I believe the bug is in ofono/ril, since the
IncomingMessage signal we get from ofono already contains the message
cut off.

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

Title:
  Cut off messages

Status in Canonical System Image:
  Incomplete
Status in messaging-app package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

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

2015-12-07 Thread Tiago Salem Herrmann

The two possibilities here are that ofono is truncating the message after it's 
received, or the carrier is already sending it truncated to the phone.
The fact that characters like "ą ę" are being replaced by "a e" already 
indicates that something in the middle (carrier) is trying to replace/remove 
utf-8 characters from the message.
My opinion is that the carrier is editing the message and the swiftkey emoticon 
is making their parser break. 

If possible, insert the same sim card on another phone with another OS
and try sending the very same message. If it arrives truncated, than
it's a bug in the carrier side, otherwise if might be something in
ofono.

Thanks

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

Title:
  Cut off messages

Status in Canonical System Image:
  Incomplete
Status in messaging-app package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

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

2015-12-03 Thread Tiago Salem Herrmann

If you are getting characters replaced, I would say the operator is
incorrectly parsing/editing the message before sending.

Could you run "dbus-monitor > session.log", and in another shell "dbus-
monitor --system > system.log", and then receive the message and attach
the logs here?

Also note that the files might contain phone numbers, feel free to
remove them before attaching the logs.

Thanks.

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

Title:
  Cut off messages

Status in Canonical System Image:
  Incomplete
Status in messaging-app package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  My girlfriend send me some SMS with text: 'Umiem. Skoro się pytam to chcę 
(emoticon) bo miałeś wczoraj rację, że dawno nie wychodziliśmy', but I've 
received 'nie wychodzilismy'.
  We tested that exact text few times - all the time I'm receiving 'nie 
wychodzilismy'. Could anyone test that text? Please look at 'ś' that 
disappeared in my phone.
  We test that without emoticon and - magic, I've received all text, but 
without polish special signs (like ł ś ę, etc.). Inserted other emoticon - 
received 'ie wychodzilismy'.
  I must also admin that I'm getting 's', 'e', etc. instead of 'ś', 'ę', etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522150/+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 1517654] Re: Notifications contain no body message when only attachment received via MMS

2015-12-02 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/telephony-service/fix-1517654

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1517654

Title:
  Notifications contain no body message when only attachment received
  via MMS

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  latest rc-proposed, post ota8

  Send an MMS to the phone, with a single image, or vcard
  In the notification and mesasging-menu, it only shows the Contact name (or 
phone number) of the sender without any message.

  However in the messaging-app conversation view, it correctly shows:
  
  Attachment: 1 image (or 1 contact, etc).

  We should do the same thing for the notification and for the item in
  the messaging-menu. If the message only has an attachment and no text
  it should show the Attachment information.  If possible if the message
  has text and attachment we should show both if room in the
  notification and messaging menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517654/+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 1519809] Re: No sound is routed to bluetooth headset after a call

2015-11-30 Thread Tiago Salem Herrmann

With latest pulseaudio from silo 9 the call is routed correctly, but I
still can't control the incoming call with the headset, and I hear the
device ringtone, and not the headset one. My guess here is that HFP is
only working during an active call, since I can hangup an active call
with the headset button but I can't accept a call while it's ringing.

I am attaching the syslog.

** Attachment added: "syslog"

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4527689/+files/syslog

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

Title:
No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
In Progress

Bug description:
After the latest update to bluez5 no sound is routed to the connected
bluetooth headset after a call is ended.

Steps to reproduce:

1) connect a bluetooth headset
2) Receive a call
3) End the call
4) Try to play music

Expected behavior:
Music is routed to the connected headset

Current behavior:
No sound is routed, although music player behaves as it was playing normally.

Additional info.
If you receive a second call, the audio is again routed normally to the
headset after it's finished.
Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] Re: No sound is routed to bluetooth headset after a call

Looks like the bug is easily reproducible when the device gets connected before 
it's registered to the network, but I was able to reproduce the problem after 
connecting it manually after it's registered as well, but in this case, not 
always reproducible.
One thing I noticed (not sure if related) is that sometimes I get the ringtone 
as a2dp, sometimes I don't get nothing, and the device supports hfp, but it 
doesn't work on bluez5 as it seems. It does work on bluez4.

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

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] Re: No sound is routed to bluetooth headset after a call

** Attachment added: "cards.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525338/+files/cards.txt

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

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] Re: No sound is routed to bluetooth headset after a call

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

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] Re: No sound is routed to bluetooth headset after a call

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525333/+files/syslog

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

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] Re: No sound is routed to bluetooth headset after a call

** Attachment added: "dbus.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525332/+files/dbus.log

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

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] [NEW] No sound is routed to bluetooth headset after a call

Public bug reported:

After the latest update to bluez5 no sound is routed to the connected
bluetooth headset after a call is ended.

Steps to reproduce:

1) connect a bluetooth headset
2) Receive a call
3) End the call
4) Try to play music

Expected behavior:
Music is routed to the connected headset

Current behavior:
No sound is routed, although music player behaves as it was playing normally.

Additional info.
If you receive a second call, the audio is again routed normally to the headset 
after it's finished.
Just tried with old images with bluez4 and it works as expected.

** 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/1519809

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] Re: No sound is routed to bluetooth headset after a call

** Attachment added: "bluetoothctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525230/+files/bluetoothctl.txt

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

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1519809] Re: No sound is routed to bluetooth headset after a call

** Attachment added: "hciconfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+attachment/4525231/+files/hciconfig.txt

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

Title:
  No sound is routed to bluetooth headset after a call

Status in bluez package in Ubuntu:
  New

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519809/+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 1373059] Re: Messages sent as reply from the notification panel are counted as unseen

2015-11-24 Thread Tiago Salem Herrmann

Just to clarify, in this bug, the message marked as unread is the
message that was received, and not the message sent as a reply.

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

Title:
  Messages sent as reply from the notification panel are counted as
  unseen

Status in Canonical System Image:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress

Bug description:
  Step to reproduce:
  - Receive a message
  - Reply to the messagge from the shortcut in the notification panel
  - Open the messagges app
  - There is a number '2' (or 1, don't remember atm, I'll update asap) near the 
conversation, as you have unseen messages.

  I expect there are no unread messages, because if I reply to a
  message, I read it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373059/+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 1517531] Re: ringtone changes not applied until after reboot

2015-11-24 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/telephony-
service/delete_player_instance_on_incoming_call

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1517531

Title:
  ringtone changes not applied until after reboot

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When changing the ringtone in system settings, the newly selected
  ringtone isn't used for incoming calls until telephone-service-
  approver is restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517531/+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 1487528] Re: [notifications] + [messaging] SMS notifications should should show which SIM received message

2015-11-23 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/telephony-service/multi_sim_notifications

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1487528

Title:
  [notifications] + [messaging] SMS notifications should should show
  which SIM received message

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  User does not see onto which SIM card the SMS was received on the lock screen 
(if this option is enabled by device privacy settings).
  It is great that used has option to reply immediately, without unlocking the 
device, but it is not possible to know, which SIM card to use to reply back.

   UX comment ---

  Please find attached to this bug a design solution which shows two solutions 
for the here described issue. 
  A. Places the [SIM name] in the place of a time stamp (recommended).
  B. Adds [SIM name] after the header of the notification.

  Solution B may be applied if solution A can not be implemented for the
  time being.

  The label of the SIM card should always represent the label users set,
  even if they renamed the sim cards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487528/+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 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)

2015-11-23 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/telephony-service/multi_sim_notifications

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1460301

Title:
  [Dialer] Incoming call - no info which SIM card was called (dual SIM)

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 (r22)

  (Don't know how to find a package version :/, but I checked for
  updates on 29-05-2015 and all apps are up to date)

  I have two SIM cards inserted into BQ Aquaris 4.5

  On incoming call I expect to see information if SIM1 or SIM2 was dialled by 
caller alongside caller ID.
  I see only caller ID.

  It may be useful if one of the SIM cards is in roaming, or when one of
  the SIMs is a company number while other is a private number.

   UX comment ---

  The SIM card indication should replace the "Incoming call" text. This
  applies only for dual SIM devices. On a single SIM device the
  "Incoming call" labe remains. Please see attached wireframe for the
  exact solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1460301/+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 1373059] Re: Messages sent as reply from the notification panel are counted as unseen

** Branch linked: lp:~tiagosh/history-service/fix-1373059

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

Title:
  Messages sent as reply from the notification panel are counted as
  unseen

Status in Canonical System Image:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Step to reproduce:
  - Receive a message
  - Reply to the messagge from the shortcut in the notification panel
  - Open the messagges app
  - There is a number '2' (or 1, don't remember atm, I'll update asap) near the 
conversation, as you have unseen messages.

  I expect there are no unread messages, because if I reply to a
  message, I read it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373059/+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 1518291] Re: visual bug in messaging app in landscape mode

** Branch linked: lp:~tiagosh/messaging-app/fix-1518291

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

Title:
  visual bug in messaging app in landscape mode

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  see the screenshot

  when writing a message in landscape mode and entering multiple lines,
  the contact's name remains visible and gets mixed up with the
  message's text

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518291/+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 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)

Thanks Olga,

Just wanted to remind that "SIM 1" can be any text defined by the user in 
system-settings. Should we still go ahead and keep this solution?
We also need wireframes for missed call entries displayed in the indicator.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1460301

Title:
  [Dialer] Incoming call - no info which SIM card was called (dual SIM)

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 (r22)

  (Don't know how to find a package version :/, but I checked for
  updates on 29-05-2015 and all apps are up to date)

  I have two SIM cards inserted into BQ Aquaris 4.5

  On incoming call I expect to see information if SIM1 or SIM2 was dialled by 
caller alongside caller ID.
  I see only caller ID.

  It may be useful if one of the SIM cards is in roaming, or when one of
  the SIMs is a company number while other is a private number.

   UX comment ---

  The SIM card indication should be next to the text stating "Incoming
  call". Please see attached wireframe for the exact solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1460301/+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 1487528] Re: [notifications] + [messaging] SMS notifications should should show which SIM received message