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:
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 =)
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:
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 =)