5,603,981 Members 44,444 Now Online
XDA Developers Android and Mobile Development Forum

[Q] KitKat Short Codes in SMS/Messaging crash com.android.phone

Tip us?
 
SuperSport
Old
(Last edited by SuperSport; 8th December 2013 at 10:42 PM.)
#1  
SuperSport's Avatar
Recognized Contributor - OP
Thanks Meter 407
Posts: 2,921
Join Date: Jun 2007
Location: Northern California

 
DONATE TO ME
Question [Q] KitKat Short Codes in SMS/Messaging crash com.android.phone

When I use a Short Code as my Recipient for messaging, the com.android.phone crashes. Does anyone know why this happens, and what I can do to fix it? It happens on all the KitKat ROMs I've tried for LG G2.

Scenario:

I open messaging. It also happens with Hangouts, or any other SMS app.
I use my credit card Short Code as the Recipient: 96411
I send a message asking for Balance Info: Bal 1234 (Any message sent to the short code does the same)
com.android.phone crashes and message does not get sent.

It also happens when sending to any other short code. ie: ATT Balance info, etc... *46# or similar...

It seems to me that it's the phone that is crashing, and not messaging. Messaging stays running, but does not send message.


Thanks in advance!

SuperSport
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2013-12-08-14-34-56.jpg
Views:	693
Size:	122.2 KB
ID:	2442408  
Tablet: Lenovo IdeaPad Lynx w Win Blue
Current: Black LG G2 D800 - Stock KitKat 4.4.2
MediaFire Share - Mostly Windows Mobile
MEGA Share - Mostly Android
Disclaimer: By using any Files, Packages, Cabs, ROMs, Knowledge, etc, that I share, you are doing so at your own risk. Go Ahead, Live on the Edge!

53 75 70 65 72 53 70 6f 72 74 HEX
 
MustWarnothers
Old
#2  
MustWarnothers's Avatar
Senior Member
Thanks Meter 22
Posts: 121
Join Date: Apr 2011
I am having this same issue on a completely different phone. I just installed CM11 on my SGS2 on Sprint, and outbound shortcode replies, using either Hangouts or the Messaging app crashes com.android.phone. I've been searching around the web and still haven't found a fix. I believe there is another post someone put up on the Cyanogenmod forum/support area about this happening, but it doesn't have any replies.

Perhaps the issue is too new to have an answer. Hopefully someone else can shed some light on why this is occurring and if we can do anything to fix it.
 
SuperSport
Old
#3  
SuperSport's Avatar
Recognized Contributor - OP
Thanks Meter 407
Posts: 2,921
Join Date: Jun 2007
Location: Northern California

 
DONATE TO ME
Quote:
Originally Posted by MustWarnothers View Post
I am having this same issue on a completely different phone. I just installed CM11 on my SGS2 on Sprint, and outbound shortcode replies, using either Hangouts or the Messaging app crashes com.android.phone. I've been searching around the web and still haven't found a fix. I believe there is another post someone put up on the Cyanogenmod forum/support area about this happening, but it doesn't have any replies.

Perhaps the issue is too new to have an answer. Hopefully someone else can shed some light on why this is occurring and if we can do anything to fix it.
Thanks for your reply. It confirms it is likely KitKat related. I wonder if it happens on Stock KitKat ROMs too. If not, maybe there will be a fix soon. A file missing or something.
Tablet: Lenovo IdeaPad Lynx w Win Blue
Current: Black LG G2 D800 - Stock KitKat 4.4.2
MediaFire Share - Mostly Windows Mobile
MEGA Share - Mostly Android
Disclaimer: By using any Files, Packages, Cabs, ROMs, Knowledge, etc, that I share, you are doing so at your own risk. Go Ahead, Live on the Edge!

53 75 70 65 72 53 70 6f 72 74 HEX
 
herath
Old
(Last edited by herath; 11th December 2013 at 02:01 PM.) Reason: Adding more details related to the issue.
#4  
Member
Thanks Meter 29
Posts: 34
Join Date: Apr 2011
Having the same problem on kitkat 4.4.1 on my samsung galaxy s plus. Appears to be a kitkat related problem.

Edit--

This could be a problem only in cyanogenmod.(and cyanogenmod based rom. Do not know for sure)

E/AndroidRuntime( 2127): FATAL EXCEPTION: main
E/AndroidRuntime( 2127): Process: com.android.phone, PID: 2127
E/AndroidRuntime( 2127): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.NEW_OUTGOING_SMS flg=0x10 (has extras)
E/AndroidRuntime( 2127): Caused by: java.lang.SecurityException: Calling uid 1001 gave packagefamily.mobitel.mymobitel which is owned by uid 10106
E/AndroidRuntime( 2127): at com.android.internal.telephony.SmsUsageMonitor.che ckCallerIsSystemOrSameApp(SmsUsageMonitor.java:596 )
E/AndroidRuntime( 2127): at com.android.internal.telephony.SmsUsageMonitor.get PremiumSmsPermission(SmsUsageMonitor.java:549)
E/AndroidRuntime( 2127): at com.android.internal.telephony.SMSDispatcher.check Destination(SMSDispatcher.java:824)
E/AndroidRuntime( 2127): at com.android.internal.telephony.SMSDispatcher.sendR awPdu(SMSDispatcher.java:765)
E/AndroidRuntime( 2127): at com.android.internal.telephony.gsm.GsmSMSDispatche r.sendText(GsmSMSDispatcher.java:177)
 
Black-wolf
Old
(Last edited by Black-wolf; 16th January 2014 at 12:48 AM.)
#5  
Black-wolf's Avatar
Senior Member
Thanks Meter 33
Posts: 130
Join Date: Mar 2006
Location: Fayetteville, NC

 
DONATE TO ME
Default The Voicemail Notification, SMS, and com.android.phone

I have run into an issue involving com.android.phone on my Samsung Exhilarate. Based on what I've been able to determine, it looks like there is an issue with Cyanogen 11. I don't know if this affects all phones, but it DOES affect mine.

Here's the background:
1) Replaced CWM with TWRP Recovery
2) Installed Cyanogen 11 on my phone (because the one I'd been using forever (cm7) was starting to act up - figured it was time to reflash
3) Installed gApps for Cyanogen 11
4) Installed SuperUser

Started using the phone, and noticed my Voicemail Icon in the notification bar was up. Checked VM, nothing. WTF? Also, got a blank text from, well, myself, as I was checking my VM.

Noted the following: Every time I check VM, I get a blank text from my self, and the VM Icon refuses to go away unless I kill com.android.phone. Doesn't appear to really affect anything else.

So - who can help? I'm up for anything, including hacking open any of the com. files if need be (so long as I don't brick).

V/R

Black-Wolf
Provider: AT & T
Phone: Samsung Galaxy Exhilarate (Rooted)
ROM: Stock
OS: Android 4.0.0
Tags
com.android.phone, messaging, short code, sms
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes