Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,740,412 Members 45,063 Now Online
XDA Developers Android and Mobile Development Forum

Phone calls on it's own

Tip us?
 
Wooaarr
Old
#1  
Senior Member - OP
Thanks Meter 92
Posts: 108
Join Date: May 2012
Question Phone calls on it's own

Hello there,

I have a very weird issue, my girlfriends phone makes calls on it's own. To make it worse (Or maybe better to track down...), it is making these calls in a very predictive pattern, see screenshot. Precisely at xx:25 ; xx:55 ; xx:05 and sometimes at xx:35 it dials the number 22.

The phone is a Samsung Galaxy Y (GT-S5360-T), Stock rooted ROM in Thailand with AIS as the provider. The phone has been been running on that setup for a good 2 years, without any changes of apps in the last few months.

I took a logcat from one of these calls. Here is when it starts:

Code:
Select Code
I/dun_mgr (14358):  AT command: AT
I/at      (14359):  ATcmd:0 at 3
I/dun_mgr (14358):  atx response: ...
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/dun_mgr (14358):  AT command: ATE0V1&D2&C1S0=0
I/at      (14359):  ATcmd:0 atE0V1&D2&C1S0=0 17
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/at      (14359):  ProcessATCmd: bypass to the CP: at&D2, len=5, cmdParmBuf=2, curCmdStr=&D2&C1S0=0, pConcatCmd=&C1S0=0
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/at      (14359):  ProcessATCmd: bypass to the CP: at&C1, len=5, cmdParmBuf=1, curCmdStr=&C1S0=0, pConcatCmd=S0=0
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/dun_mgr (14358):  atx response: ...
I/dun_mgr (14358):  AT command: AT
I/at      (14359):  ATcmd:0 at 3
I/dun_mgr (14358):  atx response: ...
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/dun_mgr (14358):  AT command: AT
I/at      (14359):  ATcmd:0 at 3
I/dun_mgr (14358):  atx response: ...
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/dun_mgr (14358):  AT command: ATE0V1&D2&C1S0=0
I/at      (14359):  ATcmd:0 atE0V1&D2&C1S0=0 17
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/at      (14359):  ProcessATCmd: bypass to the CP: at&D2, len=5, cmdParmBuf=2, curCmdStr=&D2&C1S0=0, pConcatCmd=&C1S0=0
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/at      (14359):  ProcessATCmd: bypass to the CP: at&C1, len=5, cmdParmBuf=1, curCmdStr=&C1S0=0, pConcatCmd=S0=0
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/dun_mgr (14358):  atx response: ...
I/dun_mgr (14358):  AT command: AT
I/at      (14359):  ATcmd:0 at 3
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/dun_mgr (14358):  atx response: ...
I/dun_mgr (14358):  AT command: AT
I/at      (14359):  ATcmd:0 at 3
I/dun_mgr (14358):  atx response: ...
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/dun_mgr (14358):  AT command: ATE0V1&D2&C1S0=0
I/at      (14359):  ATcmd:0 atE0V1&D2&C1S0=0 17
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/at      (14359):  ProcessATCmd: bypass to the CP: at&D2, len=5, cmdParmBuf=2, curCmdStr=&D2&C1S0=0, pConcatCmd=&C1S0=0
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/at      (14359):  ProcessATCmd: bypass to the CP: at&C1, len=5, cmdParmBuf=1, curCmdStr=&C1S0=0, pConcatCmd=S0=0
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
I/dun_mgr (14358):  atx response: ...
I/dun_mgr (14358):  AT command: AT
I/at      (14359):  ATcmd:0 at 3
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/dun_mgr (14358):  atx response: ...
I/dun_mgr (14358):  GPRS dial string: M0DT22
I/dun_mgr (14358):  Invalid GPRS dial string
I/at      (14359):  ATcmd:0 atM0DT22 9
I/at      (14359):  AT_ProcessCharParserDataInd at cmd sent state=4 
I/at      (14359):  ProcessATCmd: bypass to the CP: atM0, len=4, cmdParmBuf=0, curCmdStr=M0DT22, pConcatCmd=DT22
I/at      (14359):  ATC_KERNEL_Get_AT_RESP - 
I/at      (14359):  OK
E/at_call (14359):  ATC_ProcessGprsDialStr = 0
I/dun_mgr (14358):  atx response: ...
After that, the CallManager takes over.

The number 22 does not exist, so it doesn't cost me anything, nor is there any sensible data on that phone. Anyway, before i restore factoy settings via Odin, I would like to know if anyone knows something about this. Is this maybe even a new virus?

Attached is the complete logcat, from beginning of the call, to the end.

Any help would be much appreciated =)
Attached Thumbnails
Click image for larger version

Name:	2014-05-08_23_19_06.jpg
Views:	6
Size:	55.9 KB
ID:	2732645  
Attached Files
File Type: txt CallOwn.txt - [Click for QR Code] (41.0 KB, 2 views)
 
es0tericcha0s
Old
#2  
Senior Member
Thanks Meter 461
Posts: 2,368
Join Date: May 2010

 
DONATE TO ME
I would double check my apps to see which ones have permissions to call without your input.
Need some help, advice, something fixed? Hit me up on Hangouts @ es0tericcha0s and check out my site: http://mobilemojo5280.com for more info!


HTC Droid Eris / Motorola Droid / Samsung Galaxy S Fascinate / Motorola Droid X / LG G2x / HTC Evo 3D (x2) / Samsung Epic 4G Touch (Sprint S2) / HTC Amaze / Samsung Galaxy S3 (International) / Samsung Galaxy Note 2 / Nexus 4 / HTC One / Samsung Galaxy S4 / Sony Xperia ZL / Nexus 5 / ? (One+1 maybe...)
 
Wooaarr
Old
#3  
Senior Member - OP
Thanks Meter 92
Posts: 108
Join Date: May 2012
Quote:
Originally Posted by es0tericcha0s View Post
I would double check my apps to see which ones have permissions to call without your input.
Thank you, but I already did this, without any improvement. (Even after deleting every single app with permission to make calls, not including dialer & settings of course).
In LBE (I know it is outdated...), there is no event in the permission log for the calls.


I reseted the phone via Odin now anyway, but it seems just so strange to me.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes