My phone is an Epic 4G running a very mildly modified CM10. Basically the modifications are just a flashed script removing a bunch of unneeded stuff after every nightly flash. (wallpapers, ringtones, a few default apps, etc) Nothing that touches the actual system/settings.
A couple weeks ago I noticed that if I dialed a local number without the area code it was adding (617) as the area code. Same thing happens if I pick a contact from my phone that happens to not have an area code. My area code is 317, so it adding 617 has me calling totally wrong numbers. Before, IIRC it added (317) correctly instead. I've had this phone since launch and this is a recent issue.
As I said, this has been happening for a few weeks now. Multiple reboots and nightly flashes later and the problem persists.
After searching for a solution, I've seen a few mentions of somewhat similar issues as possibly being 'network issues.' My girlfriend's phone does not have this problem. Same network, different phone and stock 2.3.6. I would suspect true network issues would also affect her phone.
I searched through the phone settings and did not notice a place to change the default area code. I think I remember having that option in the stock rom though.
What do I need to do to fix this?
Honestly, when I add a new contact, I put in the area code anyway. Try adding the correct area codes to the contacts that don't have one in your phone.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Honestly, when I add a new contact, I put in the area code anyway. Try adding the correct area codes to the contacts that don't have one in your phone.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
That isn't a fix, its a work around.
Most of my contacts do have area codes already. I dont have a crap ton of contacts, but it would still be inconvenient to check/fix them all.
What made me notice was needing to manually dial a number not in my contacts that I will likely only ever call once. I had several in a couple day period and I called Massachusetts a few times on accident forgetting about this new problem.
Would also be a pain to remind people that they need to dial the local area code for times when I lend someone my phone to make a quick call. (very rare for me, but does happen)
Okay, I only said what I said because I lived in a state that no matter what number you were calling, whether it was local or long distance you needed to dial the area code.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Okay, I only said what I said because I lived in a state that no matter what number you were calling, whether it was local or long distance you needed to dial the area code.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Understandable. I know some cities and states are so saturated that people in the same city could have different area codes.
My area code covers 1/3 of the state. You have to go ~50miles north or south to get to a different area code. Typically, you only run into someone in the city with a different area code if they are from out of town. Occasionally people do move and never get their cell number changed. But they are the exceptions, not the rule.
thedumbass said:
My phone is an Epic 4G running a very mildly modified CM10. Basically the modifications are just a flashed script removing a bunch of unneeded stuff after every nightly flash. (wallpapers, ringtones, a few default apps, etc) Nothing that touches the actual system/settings.
A couple weeks ago I noticed that if I dialed a local number without the area code it was adding (617) as the area code. Same thing happens if I pick a contact from my phone that happens to not have an area code. My area code is 317, so it adding 617 has me calling totally wrong numbers. Before, IIRC it added (317) correctly instead. I've had this phone since launch and this is a recent issue.
As I said, this has been happening for a few weeks now. Multiple reboots and nightly flashes later and the problem persists.
After searching for a solution, I've seen a few mentions of somewhat similar issues as possibly being 'network issues.' My girlfriend's phone does not have this problem. Same network, different phone and stock 2.3.6. I would suspect true network issues would also affect her phone.
I searched through the phone settings and did not notice a place to change the default area code. I think I remember having that option in the stock rom though.
What do I need to do to fix this?
Click to expand...
Click to collapse
Network issues should affect her phone too so my guess would be its a bug in the recent nightly's. Try flashing back to the most recent nightly that you recall it working correctly on and see if the problem persists.
This thread seems to have a possible cause/solution...
http://forum.xda-developers.com/showthread.php?t=1227736
steeler350 said:
found the fix for it if anyone else is having the same problem
Is your phone suddenly defaulting to area code 617 when you only dial 7 digits? This is the fix. (self.Android)
submitted 3 months ago by reddit_account_42
For at least a few weeks now, my phone has been defaulting to area code 617. I assumed I probably broke it trying out some Cyanogenod nighties with the race up to 6.1, and didn't think too much of it. Now that i'm dealing with some new phone numbers, defaulting to 617 instead of my correct area code has been somewhat of a pain. Google didn't help, but it revealed a number of users with the same problems:
I then was lucky enough to find this code snippet with the constant private static final String AREACODE = "617". Looking at the name seems to indicate that it's for testing an intent, and has a bit of additional functionality I hadn't noticed:
* Make default area code 617
* Replace 411 with 1-800-GOOG-411
* Disable calling 555-5555 (Try it, dialer just closes. As the code says, "Note that no UI is displayed to the user -- the call simply does not happen.")
Realizing now that the issue is with the Dialer app, I'd figured I'd just have to find an apk of that somewhere. Instead, I realized I had downloaded Autostarts which lets you review intent handlers. Indeed, if you run Autostarts, you can see that under 'New Outgoing Call' there is an entry by Dialer. Clicking on that and you can see that the intent is handled by com.android.phone.ProcessOutgoingCallTest, which is exactly the code I found above. From here, you can just choose 'Disable' and autostarts will remove the intent, and you'll have your 7 digit phone numbers back without the 617 area code.
Note that I had to restart the Dialer for this change to work (or, rather, it crashed out from under me when I changed it). Though, there are no ill effects.
I can only assume a build of Cyanogenmod had this test facility enabled, and when I didnt' wipe during a ROM upgrade this persisted.
tl;dr: Use Autostarts and remove the Dialer entry from 'New Outgoing Call'
Click to expand...
Click to collapse
Found a thread on Droidforums that suggest hex editing the phone.odex to remove the default 617 area code. That thread says it actually breaks the phone to fix it though. So you do a complete CWM backup, mod the odex, break the phone's calling ability, replace the modded odex with the original, reboot, still broken, then restore the CWM backup and suddenly the 617 default is gone.
Figured I should check back to verify the above quoted fix worked. Still don't consider it a true fix myself since it requires a 3rd party app.
Still don't have a clue why this issue suddenly started up either. Had my phone since launch and have been running custom roms for a year or so and this issue didn't pop up until a few weeks before my first post.
Sent from my GT-P3113 using Tapatalk 2
Related
Let me start this question with a big thanks to all the developers/etc. out there. The work being done is AMAZING!
I am a new "rooter", but learning fast. I am running Cyanoginger 1.1 on my MT3GS. I have noticed a few things that aren't quite right, and I am unsure if they are related to each other, or to Cm 6.1.1, or ~ginger 1.1, or...
1. Incoming phone calls seem to sporadically go to voicemail instead of the phone. My phone can be sitting on my desk with full bars, I'll call my phone from my desk, it'll ring once or twice and jump to voicemail (nothing shows up on the MyTouch). I'll call again 10 seconds later, and it goes to my phone. Very sporadic (maybe 1 in 20 calls?)
2. My phone number shows Unknown in Settings > About phone > Status. I read in a few forums that this may be the case untill you place/receive a call, but mine is still showing unknown.
3. My market purchases are no longer integrated with carrier billing. It's asking for a credit card instead of automatically billing me at T-Mobile.
Like I said, I'm a noob at rooting/modding, but I learn quick Any help with these issues would be greatly appreciated!
qjudge said:
Let me start this question with a big thanks to all the developers/etc. out there. The work being done is AMAZING!
I am a new "rooter", but learning fast. I am running Cyanoginger 1.1 on my MT3GS. I have noticed a few things that aren't quite right, and I am unsure if they are related to each other, or to Cm 6.1.1, or ~ginger 1.1, or...
1. Incoming phone calls seem to sporadically go to voicemail instead of the phone. My phone can be sitting on my desk with full bars, I'll call my phone from my desk, it'll ring once or twice and jump to voicemail (nothing shows up on the MyTouch). I'll call again 10 seconds later, and it goes to my phone. Very sporadic (maybe 1 in 20 calls?)
2. My phone number shows Unknown in Settings > About phone > Status. I read in a few forums that this may be the case untill you place/receive a call, but mine is still showing unknown.
3. My market purchases are no longer integrated with carrier billing. It's asking for a credit card instead of automatically billing me at T-Mobile.
Like I said, I'm a noob at rooting/modding, but I learn quick Any help with these issues would be greatly appreciated!
Click to expand...
Click to collapse
The unknown number thing has to do with cm6.1.1. It shouldn't affect you anyway. For the first issue, probably t-mobile issue, neither your phone nor your ROM. Happens to me on all my phones, even my dumbphones.
The market thing is something that you give up when you flash a custom ROM. I think there might be something that can tie market to your tmobile account, but I can't find it again, it was mentioned in a thread recently.
Thanks for the quick response!
On points 2 and 3, I guess that's just the way it is. Little things, I can definitely deal.
On the first point, I just want to make sure this isn't happening because of how I flashed new roms, or how I upgraded the radio, etc.
FWIW, here's the process I used:
- rooted phone with adb/file copy, etc., etc.
- booted to ESPRIMG.zip (oops, rebooted, no backup of system!)
- booted to Clockwork
- cleared data, cleared cache, flashed CM 6.1.1, flashed gapps, rebooted
- went back to clockwork flashed radio from 7.07.(????) directly to 7.09.35.10, rebooted
- "stumbled" across Cyanoginger 1.1...
- booted to Clockwork, cleared data, cleared cache, flashed to Cyanoginger 1.1
The phone prior to rooting never had any issues receiving calls, but who knows, maybe it's because I'm staring at it, maybe it's solar flares, maybe I've angered the cell phone gods...ok, humor's "off" a bit today
If you have any further thoughts, let me know; otherwise thanks for your help! I really appreciate it!
Yeah that all sounds right. I haven't ever had issues with my phone number showing up, it seems to only happen to some people, and like you said, normally it goes away after placing or receiving a call. Who knows. I don't think it affects any apps though. I could be wrong about that, not sure. It might be your sim card, which would explain some calls not going through as well.
I know there is a way to tie the market to your t-mobile account, I just can't remember at the moment. I googled around, couldn't find anything. I think it's called market fix or something rather. I could be thinking of something else though. Frankly I like paying with my debit card better, it was never a huge deal for me, so I never thought too much into it.
MusicMan374 said:
I know there is a way to tie the market to your t-mobile account, I just can't remember at the moment. I googled around, couldn't find anything. I think it's called market fix or something rather. I could be thinking of something else though. Frankly I like paying with my debit card better, it was never a huge deal for me, so I never thought too much into it.
Click to expand...
Click to collapse
I know exactly what you're talking about... I just can't seem to find it either. It was in a thread recently, like you said.
Maybe it's just vanished
I'm gonna keep searching though.
EDIT: So I was starting to flip out, cause I could not for the life of me find the thread...
But I decided to go to my phone and see if maybe I could just find the app in the market. Then I saw that I had already searched for it before, because I actually have the same issue. I just never downloaded it and tested it out.
It's called "Market Enabler"
I'm going to download it now and test it myself.
EDIT 2: Or maybe that's not it. I don't know, I can't seem to figure it out. Maybe MusicMan can take a look? I could have sworn this was an app suggested for that, but it just looks like it makes it so you can see apps that aren't on certain carriers.
SefEXE said:
I know exactly what you're talking about... I just can't seem to find it either. It was in a thread recently, like you said.
Maybe it's just vanished
I'm gonna keep searching though.
EDIT: So I was starting to flip out, cause I could not for the life of me find the thread...
But I decided to go to my phone and see if maybe I could just find the app in the market. Then I saw that I had already searched for it before, because I actually have the same issue. I just never downloaded it and tested it out.
It's called "Market Enabler"
I'm going to download it now and test it myself.
EDIT 2: Or maybe that's not it. I don't know, I can't seem to figure it out. Maybe MusicMan can take a look? I could have sworn this was an app suggested for that, but it just looks like it makes it so you can see apps that aren't on certain carriers.
Click to expand...
Click to collapse
It could just be that we were thinking of something else and such an app doesn't exist. I'll look some more when I get home
Sent from my T-Mobile myTouch 3G Slide
Well, I "stumbled" across the solution to #2. As far as I've heard from others so far, it's purely cosmetic, but...
Go to Settings > Call Settings > Additional Settings > My phone number and enter the number. Now when you go to Settings > About phone > Status it will show the number you entered.
Again, this may be purely cosmetic, and I've noticed if you reboot, the setting gets wiped. Strange...but there you go...
Sorry to bring up this issue back up but I just recently Rooted my phone as well and am having the same problem with sporadic calls not coming to my phone.
For example, last night my father told me that he tried to call me at least 3 times in a row and it would go straight to voicemail, however today he called me (like 2 mins ago) and the phone rang as normal. Heres what I've noticed on the phone:
-the phone will drop all bars sporadically for no apparent reason, as I have never had any service issues in my house.
-it does this when its been idle for a couple of minutes and as soon as I wake it up it will show 0 bars then jump to the normal 2-3 I usually get at my place.
-whenever the bars drop to 0 my 3g/HSPA service will still show as normal
I'm not completely new to Rooting (Rooted my original G1), however my last experience with it was back on CM4.1 on my G1, so there may be a o couple of things I missed
Thanks in advance for any help!
Hi, I've a similar problem: on outgoing calls anyone on any phone is able to see my number, they always get calls from "unknown" from my phone. I use wolfbreak's rom with cyanogen and I've allready set in the settings the option to show my number on outgoing calls, but doesn't work. how can I do?
Tony84 said:
Hi, I've a similar problem: on outgoing calls anyone on any phone is able to see my number, they always get calls from "unknown" from my phone. I use wolfbreak's rom with cyanogen and I've allready set in the settings the option to show my number on outgoing calls, but doesn't work. how can I do?
Click to expand...
Click to collapse
had this prob too even if u set it in cm you still have to call your carrier to get them to make you number show
I have been having a lot of trouble with my Epic's radio behavior since the EC05 radio update. It seems that the normal Samsung "radio stupidity" that I have seen in several of their devices is worse than ever now. The best radio for call performance I have used so far was DG27's (though not data). Essentially, what it is as far as I can determine by using utilities to monitor radio operation, is poor CDMA handoff configuration.
What it does is, for no good reason, switch from a cell site providing a good signal level, to one providing a bad signal level for no reason. Either this, or it holds onto a weakening set of towers while moving, until it goes out of their range and the call drops. The phone will then display the no service message for a few seconds, and then will pick up perfect signal from a different set of towers. I can even watch this happen by driving down a given road while on a call, with another phone in my cup holder. The Epic will start to break up and show very low signal levels, while the other is doing perfectly. Additionally, the direction you drive down this (2 lane) road also has an effect.
I have fixed this before on non smartphones by altering some of the CDMA radio values. T_Add, T_Drop, T_Comp, T_Tdrop. My solution is to increase the threshold on T_Comp a little bit, and drop the T_Tdrop also a little bit. The problem is that I cannot figure how to do this on this phone. Very little radio information seems to be available, and the utilities I have do not work completely on this model.
This issue with how they program their radios seems to be a common Samsung problem, to a much greater degree than with other manufacturers. Sanyo, Palm, and Motorola seem to do a much better job with this, even in cases where they use the same radio chipsets.
I am feeling like a lot of people will find this matter interesting and/or of benefit to resolve.
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
Sent from my SPH-D700 using Tapatalk
Maybe try ##3282# or *#147852#
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
musclehead84 said:
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
It isn't the data driving me nuts. Data sessions pick up again quickly. It's the dropped calls. Either way, it is partially a symptom of the same problem. The phone is promoting weak towers, sometimes in favor of strong ones, to the active set - which it should not be.
MysteryEmotionz said:
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
...
Click to expand...
Click to collapse
No and yes. CDMA support was a hack in versions prior to 2.0. Android 2.0 (and later) has inbuilt features intended to support CDMA networks. Some of the companies are still using some legacy code, and some of nomenclature used within the system parameters still reflects GSM however.
This, however, is irrelevant in my belief. I do not think that these parameters are a function of RIL, as RIL is simply the intermediary between the "computer" and "telephone" components in a smartphone. I believe that these issues exist purely, or nearly so, within the "telephone" section of the device.
running_the_dream said:
Maybe try ##3282# or *#147852#
Click to expand...
Click to collapse
What is this ##147852#? I cannot find it in any information I have, and it has no effect on the phone itself.
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
running_the_dream said:
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
Click to expand...
Click to collapse
Yes, totally misread that. Nothing seems to apply however, as I do not think it is a software parameter on the phone end. The WiMAX radio is software controlled, through a driver in the operating system. The combination of CDMA radio and baseband processor are more or less an independent device which essentially lives on its own, with its own configuration. It is told what to do through the RIL, which is a piece of software that allows the computer aspect of the phone to talk to the radio, passing it instructions which it then acts upon according to its own programming and configuration. The RIL also allows the radio to communicate its status to the rest of the system.
I am really thinking that this will not be a setting that can be modified from within the phone itself, but will require some external involvement, similar to QPST. On this chipset, however, QPST does not appear to be able to manage these parameters.
If you find out any more info please pass it along. Thank you.
Sent From My Evo Killer!!!
Ah that's really interesting. Wish I could help.
Update with fix [Thanks jayclapp!]
For anyone with this issue, go into your APN settings and remove anything in the "Proxy" field, right below "APN". Fixed the problem immediately for me + jayclapp!
Original Post Below
----------------------------------------------------------------------------------------------------------------
Hi all,
Having an issue downloading anything from the android market on 3G. 3G works for everything else besides downloading from the market (browsing, email, sync, etc).
When I switch to wifi, I can download from the market perfectly fine.
I've tried a friends SIM with a different carrier, and it DOES work over 3G.
Logcat of the issue happening From what I can tell the error starts around line 50, but I included the full log in case it helps.
I'm not much of a developer so I'm just trying to determine why exactly it's happening, as Android simply spits out a pop-up with the useless message:
[App name here] could not be downloaded due to an error.
I have a friend on the same carrier with a Nexus S and she can download apps from the market fine. Haven't been able to test her SIM in my phone yet though.
I've found some others with a similar issue (although not restricted to only happening over 3G): http://www.google.com/support/forum/p/Android+Market/thread?tid=5a31588b6f655e89&hl=en
None of the solutions there helped though. I've cleared market data, wiped, factory reset, tried different roms, etc.
I'd really appreciate any help.
i'm having the same problem - using a galaxy nexus on tmobile. haven't had the change to try on wifi yet.
vivanshah said:
i'm having the same problem - using a galaxy nexus on tmobile. haven't had the change to try on wifi yet.
Click to expand...
Click to collapse
Glad I'm not the only one...
By searching pastebin, I've found a few others that pasted their logcats with the same issue, but I can't find wherever they posted it to see if a solution ever happened.
One solution I found was to delete / rename the .android_secure folder on the "SD" card, but I see that folder on my phone. I know dotfiles are hidden by default but I'm showing hidden files and I don't even see .android_secure from adb shell.
I'm on Mobilicity in Canada, which also uses AWS bands, not sure if that has anything to do with it.
I don't like bumping, but I still have this issue and was hoping someone could help out.
Sucks only being able to download apps over wifi.
I saw Josh Topolsky from The Verge has been complaining about this issue on twitter the last couple days.
www.twitter.com/joshuatopolsky
I've tried everything to fix it, tried different roms, kernels, wiping, factory reset, different SIM cards, nothing will fix it.
The 403 error indicates that it's Google's servers that are forbidding the connection...but I see no reason why they would, and it's not like I can change the IP address of what my phone is being assigned by the 3G towers.
Everthing was fine on stock untill i flashed revolution hd 1.3.1... I had the same problem with market but for some reason i enabled wifi and started downloading stuff from the market...then i turned it off and magic it worked thru att 3g...
I hope this temp solution might help you guys out or maybe it just worked for me
Ditto
I'm facing the same issue with a Galaxy Nexus (bought from Virgin) on Mobilicity in Toronto: market works on wifi, but not on 3g.
I'm having this problem too. With Orange in Spain.
But is not a constant problem. Sometimes works fine, and another ones not. When the error comes out I try again several times untill it works. If doesn't I whait to have Wifi.
But as I said it isn't always. But some type of bug is.
I got the Galaxy Nexus yesterday from Virgin Mobile and using it with my Telus SIM and Android Market downloads dont work using the mobile network but switch to wifi I can download from Market. I've tried everything you mentioned as well and still no luck.
I have noticed some delays in downloading but I am pretty sure it is becasue of the "little" 10 Billion Apps promotion thats causing the issues.. the market must be seeing a lot more traffic than it can cope with.. servers must be over loaded!
Try market at off peak times (worked for me)!
This theory syncs quite well with the 10 Billion Apps promotion.. just a thought!
kkh786 said:
I have noticed some delays in downloading but I am pretty sure it is becasue of the "little" 10 Billion Apps promotion thats causing the issues.. the market must be seeing a lot more traffic than it can cope with.. servers must be over loaded!
Try market at off peak times (worked for me)!
This theory syncs quite well with the 10 Billion Apps promotion.. just a thought!
Click to expand...
Click to collapse
Unfortunately that isn't the reason. It's definitely something more serious / buggy than simply too much traffic. It's been going on for almost 2 weeks now, well before that promotion even started.
Anyone feel like pulling a logcat and seeing if it matches up with mine? I'd suspect it does (403 Forbidden errors).
It basically boils down to Google's servers rejecting the connection for one reason or another. 403 error = The server is connectable, but knowingly refused the connection. It's something on Google's end, but I don't understand why certain devices are being rejected while others aren't.
Went to apn settings and removed the proxy and now i can download from market over celluar
Just wanted to confirm your fix worked for me jayclapp!
Updating the OP with the fix, in case anyone stumbles across the same issue.
Bumping up the thread but i believe it's for a good reason.
I had the same problem with I9100 after upgrading to ICS from GB. Talked to Google play support, their solutions weren't helpful (erasing cache and stuff) and they said it's a carrier problem. I used another SIM from the same carrier and it still wasn't working....
So.... Stumbled on this thread, erased the proxy and now it's working!!!
So, i'm bumping this thread so it will perhaps show up in google in a higher search position and to say thanks to the OP (besides the thanks button)
Hello everybody, I'm not sure where exactly to post this nor what thread I could search for, as I think my situation is slightly unique and I'm very much confused and concerned.
Just a bit of background, I recently purchased a Galaxy Nexus from Verizon, which has been performing beautifully. I unlocked/rooted immediately, flashed the latest MIUI and franco kernel, and have been enjoying my phone since! Yesterday, however, after failing to successfully update my ROM (forgot to wipe data before the flash and was too lazy to make backups), I reloaded my nandroid and just figured I would rest on my previous version, as it was running fine before.
Today, I found out three of my contacts received calls from me which I did not make, and do not show up on my phone records. I might have dismissed this as some sort of phantom calling, or honestly maybe even butt-dialing, except for the fact that these individuals claimed I spoke to them and said unusual things along the lines of a prank call. During this time, I was at work and my phone was safely in my pocket the entire period in question.
Now, I have absolutely no idea what happened and no idea where to start looking; as such, I'm turning to what I think is an experienced XDA community to perhaps shed some light onto this? I don't want to jump to an extreme conclusion and say that my phone was somehow "hacked," as I don't even know if it's possible that you can hack a phone to call? Or is there any way for someone to make a call that shows up as my phone number on a contact's phone in another fashion? Again, any sort of information would be helpful, and any sort of solution or preventative measure would be even more appreciated.
Thanks in advance!
It could be a rouge app you installed that have permission to place call without your permission. What app did you installed recently?
Pressed from my Maguro
Mach3.2 said:
It could be a rouge app you installed that have permission to place call without your permission. What app did you installed recently?
Pressed from my Maguro
Click to expand...
Click to collapse
I've installed Serve, Documents to Go, and Google Now for ICS from XDA! I actually did google some more, I see that it's possible someone spoofed my number? I don't really know. If it doesn't continue, it won't be a problem, but I'm concerned more malevolent calls may occur.
It's completely possible that someone spoofed your number, there are numerous websites that allow you to do so.
Sent from my Galaxy Nexus using xda app-developers app
It's certainly possible that apps can dial numbers or send text messages. I've yet to come across one that actually tries to have a conversation with the person it's calling however.
Sound more probable the number was spoofed, like someone already stated.
If you want to feel safe about your phone, wipe everything and reflash factory images. No rogue app will survive that.
Sent from my Galaxy Nexus using Tapatalk 2
I'd say go a bit further, re-lock & unlock the bootloader and then flash a factory image. Everything inside the phone has been nuked then.
Thanks for all the replies everyone,
I think I shall do as suggested and reflash a stock ROM at the very least, as a precautionary measure even though I actually am fairly certain my number was just spoofed, due to a certain pattern in the people who were called.
Thank you all for at least quelling my worries that something more serious had occurred.
I have a RAZR M that refuses to keep service on PagePlus after activating with their new sim card. I'm not sure it ever fully activated. I have no bars, no service, just a red circle. At times (usually within first 5 minutes of boot) it might show a couple bars or 4g, but I cannot make any calls. I get hopeful when I see the 4g symbol and might even receive a text but it suddenly drops to no service, red circle, as if the radio shut off.
A few months back I purchased a new Razr M XT907 on ebay. Wanted to flash it for Page Plus. I followed a guide several times, then tried following a similar guide but the settings would never "stick" long enough to be truly flashed. I got as far as activating with page plus (*228) and getting text and voice but this would last 2 minutes at a time max, and this is after my most successful of dozens of flash attempts. I then payed someone to remote flash it through my computer but it didn't fix the problem either. The hack involved flashing to stock 4.1.2, flashing to the previous radio that was 4.1.1, rooting, editing subscription value in SQLite, editing 4g value in BuildProp, and setting the phone to NV Only through DFS.
When I heard PagePlus was adopting 4G I flashed to stock 4.1.2 and waited until I could get a sim card. Went to a local dealer, got the sim card, they tried to activate it for me and my phone went through the same process it would in the past and tried to automatically dial *228. I assume when I flashed back to stock it didn't fully reset everything I had changed and was still in non-4G mode and trying to activate OTA. I've heard dialing *228 with a sim card in can damage it but I'm surprised the industry would allow that without safeguards or warnings. This is when I saw for the first time some actual GUI glitches on the phone which is lightly used and no hardware issues known. I have since reversed all the steps I remember taking to flash and manually unflash each individual setting, I have reflashed to stock multiple times. I have tried updating the PRL, I have tried flashing the 4.1.1 radio, 4.1.2 radio, and the newest radio (SM_BP_101032.021.32.80P) with no luck and minor differences. Now the only GUI glitches I get is when I turn the phone on and it tries to activate (through 4g/sim method) and says "this could take a few minutes" with an option to click "ok." This box flashes constantly and sometime makes the ok box impossible to click. One of the settings I messed with before was under ##PROGRAM under test, the service mode (CDMA/EVDO/LTE/WCDMA), (CDMA/EVDO), (CDMA/EVDO/LTE). But recently when viewing or changing this value I'll look back and it won't change, or it will arbitrarily change to just (CDMA/EVDO) and I'll set it to (CDMA/EVDO/LTE) then I come back it's set to (CDMA/EVDO/LTE/WCDMA) (default I believe). At times I cannot access the ##PROGRAM settings at all and I believe this has to do with a GSM mode or SPC issue.
Currently I'll get blue or gray 4g indicator for 30 seconds then it quickly switches to no bars with red circle. A couple times it has shown just a couple bars with no data indicator. Twice it has worked long enough to retrieve a couple texts. This seems similar to my earlier issue with trying to flash without 4g/sim. Even when the phone shows service I cannot get any phonecalls to dial out. At least once it failed and said "radio off." Indeed it's acting like the radio isn't on at all, randomly cuts in and out, and the majority of the time is no service no bars with the red circle.
I'm not sure if I corrupted a setting, never completely unflashed, or have an actual hardware issue. Interestingly my IMEI listed on the OS as well as dialing *#06# are the same, but the last digit is different (0) when reading the IMEI value in DFS. If anyone knows how to truly reset all the settings to default including those in SQLite, BuildProp, ##PROGRAM, and DFS then that would be incredible. Otherwise I may have a more difficult issue and don't know if my device is even sellable.