sms notification baloon dont work to send sms directly

Thank you for your bug report. Is the message you replied listed in the messaging application interface? Did you play with multiple SIMs? It could be the same issue than bug #1423942
In any case having the ~/.cache/upstart/telephony-service*.log would be useful

No, the message I sent from the notification baloon dont appear on the SMS conversation... I just enter "OK" and click SEND, but that's all. No tracking of my message.

About SIM, I have only 1 SIM.

That's all I can say about this bug. Also I can say I tested this again one hour later, and the same behaviour.

sorry, I maybe misunderstood the bug description. what do you call "baloon"? maybe you could take a screenshot (press volume up/down together) to show the interface you are using? On my bq/rtm if the phone is off I get a notification and the screen wakes up, if I tap on that notification it opens the messaging application ... is that what is happening to you?

I cant repeat now this behaviour I meet in the first 2 days.

When the screen was off, I received a notification, like when you receive something (SMS, email, soo on), but I was able to click it, and the notification expands with one raw so I was able to type a text "Ok" and click SEND. But the message never went somewhere and nobody received it.

I can't screenshot because I cant repeat this. Now, when I receive an SMS or another notification I dont have the option to expand the notification to reply directly from there. Just a simple notification...

I could repeat this. See the attachement.

And now the prove that the SMS never left from my phone.

ok, so you are replying from the indicator menu, not from the bubble, that makes more sense. Any chance you could add ~/.cache/upstart/telephony-service-indicator.log to the bug? You can get it through adb or install the logviewer application and screenshot that

I've tried to reproduce here but no luck, having the log would be useful, any chance you could get that?

TOnight

În data de luni, 30 martie 2015, Sebastien Bacher <email address hidden> a
scris:
> I've tried to reproduce here but no luck, having the log would be
> useful, any chance you could get that?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1437486
>
> Title:
> sms notification baloon dont work to send sms directly
>
> Status in telephony-service package in Ubuntu:
> New
>
> Bug description:
> When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
> I click the ballon, a input appears, I completed the answer to that
> SMS, and clicked SEND, but the SMS never arrived and never left from
> my phone. I repetead those steps one hour later, the same behaviour.
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1437486/+subscriptions
>

--
Trimis de pe Ubuntu Touch

http://paste.ubuntu.com/10707281/

On luni, 30 martie 2015 17:24:38 EEST, Sebastien Bacher wrote:
> I've tried to reproduce here but no luck, having the log would be
> useful, any chance you could get that?
>

--
Sent from my Ubuntu touch device

Once you are able to reproduce this bug again, can you please check if the actual message you replied to is gone from the messaging-menu?
Also, did you reboot your phone to get that working again? Or it simply started working again after some time without a reboot?

The message I receive remains in sms conversations, only my reply dont go
anywhere. Reboot doesnt resolve anything. My reply dont exist anywhere...
Even after reboot.

On marți, 31 martie 2015 15:43:03 EEST, Tiago Salem Herrmann wrote:
> Once you are able to reproduce this bug again, can you please
> check if the actual message you replied to is gone from the
> messaging-menu?
> Also, did you reboot your phone to get that working again? Or
> it simply started working again after some time without a
> reboot?
>

--
Sent from my Ubuntu touch device

Thanks for the info.
When you say it remains in sms conversations, do you mean the messaging application, or the menu that is displayed when you pull down from the message indicator to write the reply?

If you meant the messaging menu accessible from the indicators, try tapping the input field of the same message (as if you were trying to reply the same message again) and check if the text you composed before reappears.

I attach t this message some printscreen step by step. The story is: I receive 2 SMS with text "TEST". I reply to the second one with the text "Test" and the message I receive dissapear from Notifications, I reply to the first one with the text "Test2" and the first SMS I receive dissapeard too. And the last screenshoot we can see I have only the 2 SMS that I receive and nothing from me to that person.

I attach t this message some printscreen step by step. The story is: I receive 2 SMS with text "TEST". I reply to the second one with the text "Test" and the message I receive dissapear from Notifications, I reply to the first one with the text "Test2" and the first SMS I receive dissapeard too. And the last screenshoot we can see I have only the 2 SMS that I receive and nothing from me to that person.

Status changed to 'Confirmed' because the bug affects multiple users.

Hi, I also have this problem
~/.cache/upstart/telephony-service-indicator.log says:

--
tp-qt 0.9.3 WARN: Trying to overwrite contact id from "+45########" to "########" for the same handle 3 , ignoring
--

(######## is the same number in both quotations)

So perhaps related to having multiple contacts that share similar phone numbers?

It also says (I just tested that it didn't work)

--
** (process:2216): WARNING *: a source with id 'telephony-service-indicator' doesn't exist
EndOfStream signal arrived via the bus.
void AalMediaPlayerControl::playbackComplete()
--

Hope this helps, or I will be happy to share any other information

Just in case that makes a difference, what language are you using?

I am using Danish as the language on the phone

ROmanian language

În data de miercuri, 1 aprilie 2015, Sebastien Bacher <email address hidden> a
scris:
> Just in case that makes a difference, what language are you using?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1437486
>
> Title:
> sms notification baloon dont work to send sms directly
>
> Status in telephony-service package in Ubuntu:
> Confirmed
>
> Bug description:
> When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
> I click the ballon, a input appears, I completed the answer to that
> SMS, and clicked SEND, but the SMS never arrived and never left from
> my phone. I repetead those steps one hour later, the same behaviour.
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1437486/+subscriptions
>

--
Trimis de pe Ubuntu Touch

The expected behavior is for the message to disappear from the menu after it is sent. The original message and your reply should show up in the messaging app. Sounds like this is not happening for you so it's definitely a bug. If either of you can attach the telephony service log to this bug that would be extremely

In order to debug this issue it would be good to have some additional information that can be retrieved using the terminal app available in the ubuntu store.

Once you are able to reliably reproduce the bug, try the following steps:

1) open terminal application
2) type "mc-tool dump" and press return
3) dismiss the keyboard by swiping it down
4) long press anywhere on the screen to invoke the popup menu, select the text, copy the output and paste it here.

However, if you happen to have adb access from your desktop to your device (developer mode active), this is way easier:
adb shell mc-tool dump

The output might contain private data (like your phone number), so feel free to change it before posting.

Thank you.

2015-04-02 4:46 GMT+03:00 Tiago Salem Herrmann <<email address hidden>
>:

> The output might contain private data (like your phone number), so feel
> free to change it before posting.
>

bogdan@bogdan-Lenovo-B580:~$ adb shell mc-tool dump
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
     Account: ofono/ofono/account1
Display Name: SIM 2
  Normalized: <SelfHandle>
     Enabled: enabled
        Icon: im-ofono
    Connects: automatically
    Nickname: <SelfHandle>
     Service: ofono

Presences:
   Automatic: available (2) ""
     Current: registered (2) "Digi.Mobil"
   Requested: available (2) ""
    Changing: no

      (string) modem-objpath = /ril_1

------------------------------------------------------------

     Account: ofono/ofono/account0
Display Name: SIM 1
  Normalized: <SelfHandle>
     Enabled: enabled
        Icon: im-ofono
    Connects: automatically
    Nickname: <SelfHandle>
     Service: ofono

Presences:
   Automatic: available (2) ""
     Current: nosim (1) ""
   Requested: available (2) ""
    Changing: no

      (string) modem-objpath = /ril_0

--
Buzea Bogdan

Looks like you are using the second slot.
Could you try moving the sim card to the other slot (probably the top slot) and check if the bug is still reproducible?
Thank you.

This actually seems to work

I at least get the text to show up in the messaging app, but haven't heard
if it showed up in the other end.

Den torsdag den 2. april 2015 skrev Tiago Salem Herrmann <
<email address hidden>>:
> Looks like you are using the second slot.
> Could you try moving the sim card to the other slot (probably the top
slot) and check if the bug is still reproducible?
> Thank you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1437486
>
> Title:
> sms notification baloon dont work to send sms directly
>
> Status in telephony-service package in Ubuntu:
> Confirmed
>
> Bug description:
> When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
> I click the ballon, a input appears, I completed the answer to that
> SMS, and clicked SEND, but the SMS never arrived and never left from
> my phone. I repetead those steps one hour later, the same behaviour.
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1437486/+subscriptions
>

--
Folmer Fredslund

Thanks.
Folmer, did you run the command after or before changing slots?

could you also provide the output of the following command?

adb shell gsettings get com.ubuntu.phone default-sim-for-messages

Hi

Den torsdag den 2. april 2015 skrev Tiago Salem Herrmann <
<email address hidden>>:
> Thanks.
> Folmer, did you run the command after or before changing slots?
>

After moving the sim.

> could you also provide the output of the following command?
>
> adb shell gsettings get com.ubuntu.phone default-sim-for-messages

The output for that command is:
'ask'

Best
Folmer

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1437486
>
> Title:
> sms notification baloon dont work to send sms directly
>
> Status in telephony-service package in Ubuntu:
> Confirmed
>
> Bug description:
> When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
> I click the ballon, a input appears, I completed the answer to that
> SMS, and clicked SEND, but the SMS never arrived and never left from
> my phone. I repetead those steps one hour later, the same behaviour.
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1437486/+subscriptions
>

--
Folmer Fredslund

I changed to SIM1 and everything works fine, but I consider the problem
should be solved for the second SIM. Maybe someone like me insert the SIM
in slot 2.

On joi, 2 aprilie 2015 16:13:06 EEST, Tiago Salem Herrmann wrote:
> Looks like you are using the second slot.
> Could you try moving the sim card to the other slot (probably
> the top slot) and check if the bug is still reproducible?
> Thank you.
>

--
Sent from my Ubuntu touch device

Yes, you are right.
The fix is already attached to the bug report.
Thanks all for the help on debugging this issue.

The related bug was already fixed in vivid but never in RTM:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1423942

This bug was fixed in the package telephony-service - 0.1+15.04.20150402~rtm-0ubuntu1

---------------
telephony-service (0.1+15.04.20150402~rtm-0ubuntu1) 14.09; urgency=medium

  [ Tiago Salem Herrmann ]
  * Check if default sim is active before sending messages. (LP:
    #1437486, #1423942)
 -- CI Train Bot <email address hidden> Thu, 02 Apr 2015 20:51:32 +0000