Related
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
At work I have access to a Nexus 7 which is shared between 7 members of our team.
I would like to be able to issue each potential user a uniquely-coded NFC keyfob that they can use to unlock the Nexus' screen and maybe set it up in particular ways.
Is this even possible? I know I can run apps once the device is unlocked, but I need to use NFC to get into it in the first place.
Yea I would say it is possible. The N7 supports various user profiles. You should be able to use Tasker to read the UID from each Tag and log into a specific profile.
You will need a custom rom/kernel because by default, NFC is off when the screen is off. A custom kernel allows NFC on all the time which can start taking commands and wake up.
I haven't messed with Tasker or Profiles. I would say it would just be a matter of logic "Read NFC and IF UID=1818181818181 then Load Profile 1" stuff.
I used NFC's coded with a URL with a unique ID to load a web page and pass the ID variable in to the server, which recorded your login and submissions. Pretty cool stuff. Just make sure you get good NFC's because the cheap ones aren't as powerful and becomes a chore trying to scan it.
The sweet spot seems to be the "N" of Nexus on the back.
Double post
I am not an Apple Fanboy. I do not own an iPhone, ever.
But seeing Apple Pay in video, I think Apple really understand what it takes to use NFC. Having to unlock your phone and/or enter a pin before tapping the phone to the NFC reader is more hassle then swiping a credit card and sign.
Yes thanks for the troll!
Oh and you really want anyone that gets their hands on your phone to also be able to spend your cash?
Sent from my SM-G900F using XDA Free mobile app
curioct said:
Yes thanks for the troll!
Oh and you really want anyone that gets their hands on your phone to also be able to spend your cash?
Click to expand...
Click to collapse
No trolling. I don't own and not planning to buy any iPhone, iPod, iPad, AppleTV nor Apple Watch.
There has to be a better way to authorize an NFC transaction then entering a PIN. Face unlock, voice signature comes to mind.
I like the security of entering a pin before authorizing the transaction. If someone steals my phone, they can go tapping all over town spending my money.
pcdebb said:
I like the security of entering a pin before authorizing the transaction. If someone steals my phone, they can go tapping all over town spending my money.
Click to expand...
Click to collapse
How about having the security yet not have to enter a PIN on a bright 5-inch screen in front of strangers?
IMO,
1. NFC on Android should work without having to unlock, like checking-in.
2. Wallet service should allow easier yet secure authentication. Like face unlock, voice recognition, even tap code!
nookin said:
How about having the security yet not have to enter a PIN on a bright 5-inch screen in front of strangers?
IMO,
1. NFC on Android should work without having to unlock, like checking-in.
2. Wallet service should allow easier yet secure authentication. Like face unlock, voice recognition, even tap code!
Click to expand...
Click to collapse
Strangers should not be that close to me in line to see me enter my code, whether it's the PIN pad at the register or my phone. Period. Shouldn't be that close anyway if I'm doing something on my phone, it's none of anybody's business to be snooping. That's considered my personal space, and you will get some F-bombs for being too close.
The idea of not having to authenticate without having to enter something is just not secure to me. And I sure as heck don't want to use voice recognition to tell everyone within earshot what my authentication code or whatever is.
pcdebb said:
Strangers should not be that close to me in line to see me enter my code, whether it's the PIN pad at the register or my phone. Period. Shouldn't be that close anyway if I'm doing something on my phone, it's none of anybody's business to be snooping. That's considered my personal space, and you will get some F-bombs for being too close.
The idea of not having to authenticate without having to enter something is just not secure to me. And I sure as heck don't want to use voice recognition to tell everyone within earshot what my authentication code or whatever is.
Click to expand...
Click to collapse
Then we get a newer version of google glass with sensors on the earpieces that press against your head and takes brainwaves. You "Think" of the code or passphrase, it gets then taken in by the sensor, encrypted, sent wirelessly to your device, decrypted, authenticated and you pay. As fast as a "thought", well some might have problems but that's another story.
Who will know your code then?... Well atleast until you find some or other method to read peoples minds.
pcdebb said:
Strangers should not be that close to me in line to see me enter my code, whether it's the PIN pad at the register or my phone. Period. Shouldn't be that close anyway if I'm doing something on my phone, it's none of anybody's business to be snooping. That's considered my personal space, and you will get some F-bombs for being too close.
Click to expand...
Click to collapse
There is a reason the pin pad on check out line has a small barrier. People can see what you type from the side. I can easily see the pattern or the PIN other people use to unlock their phone from a distance because their screen is so large and bright. Well outside of their "personal space". This is because PIN entry has a dilemma, it must display the pin pad that the user can see and large enough for the user's fat finger to touch.
The idea of not having to authenticate without having to enter something is just not secure to me. And I sure as heck don't want to use voice recognition to tell everyone within earshot what my authentication code or whatever is.
Click to expand...
Click to collapse
No one suggested authentication is not needed. Voice recognition is not the same as voice signature. Say, the phone can display a random word and you read it to the phone. The phone knows your voice. This is better than entering the same PIN over and over again.
We should be able to configure our own restrictions.
I'd make $20 and below work without unlocking or entering a PIN. and only twice in an hour. Anything over $20 would need my PIN.
PIN Settings
You can set your pin to have a timeout of 15 minutes, 1 day, or never in Google Wallet. This seems like a good compromise. If you have it at one day, you can enter it before you leave your house, or your car, etc...
Biometrics
Biometrics really need hardware integration to be both convenient and secure. The reason Apple added the fingerprint reader in the iPhone 5s is that Apple makes you authenticate for EVERYTHING. In order to store keychain passwords on the iPhone requires that you use a pin on the unlock screen, and from there it's a combo of pin and password for every single thing. Download an app? Password. Change security settings? pin. Download a song? password. Without both a pin and a password for a secured iPhone you never have access to the whole thing but it's a huge pain in the ass.
Enter touch ID- you can register up to 5 finger prints to unlock it and purchase apps and songs- the most common tasks- and now to use NFC pay. It turns the previously annoying security into a simple tap-to-unlock affair. It's silent, it's instantaneous and it is completely private, and it still doesn't give you access to the whole phone. You still have to put in the PIN every time it restarts, and password for certain things. And even if someone gets a hold of the phone, the PIN, the password and the fingerprints, the owner can brick the device remotely with find my iPhone and have it beam its location to Apple until the battery runs out and blacklist its ESN. - I think that's what the OP is talking about when he says that only Apple "gets" NFC Payment- a ****pot worth of security made totally effortless.
I hate to say it but NFC- especially payments- on Android makes me nervous as hell. I like Android for its openness and the ability to customize it and get root access if I want to and make full use of my phone- but I and a lot of other people don't have time to take the security precautions that are necessary for NFC. Apple kind of bubble wraps its users and when it comes to paying for stuff with my phone and that huge unknown, as of now, I'd prefer to be bubble wrapped and pay for stuff with a couple of highly secure taps. Even with voice or face recognition locks- things that can be accomplished in software, without standardizing hardware, it requires a certain locking down of the OS and negates a lot of the appeal of Android.
Yes
nookin said:
How about having the security yet not have to enter a PIN on a bright 5-inch screen in front of strangers?
Click to expand...
Click to collapse
You don't have to. Wallet allows setting the Wallet relock timeout to be as long as 24 hours.
IMHO Apple's implementation of Biometrics is the best so far. That, coupled with the ease of Apple pay makes it the most safe and elegant implementation so far. If nfc payments have to take off, this is the way to do it!
Sent from my Nexus 5 using Tapatalk
nookin said:
There is a reason the pin pad on check out line has a small barrier. People can see what you type from the side. I can easily see the pattern or the PIN other people use to unlock their phone from a distance because their screen is so large and bright. Well outside of their "personal space". This is because PIN entry has a dilemma, it must display the pin pad that the user can see and large enough for the user's fat finger to touch.
No one suggested authentication is not needed. Voice recognition is not the same as voice signature. Say, the phone can display a random word and you read it to the phone. The phone knows your voice. This is better than entering the same PIN over and over again.
Click to expand...
Click to collapse
What if the place you're using it in is very noisy or has a lot of background chatter? How will it be able to recognize your voice under those conditions? Also voice signature sounds a lot like something that would have an annoyingly high failure rate.
AppleCultApostate said:
What if the place you're using it in is very noisy or has a lot of background chatter? How will it be able to recognize your voice under those conditions? Also voice signature sounds a lot like something that would have an annoyingly high failure rate.
Click to expand...
Click to collapse
It is similar to what you do when voice dialing does not work. You can always fall back to PIN entry.
Entropy512 said:
You don't have to. Wallet allows setting the Wallet relock timeout to be as long as 24 hours.
Click to expand...
Click to collapse
That is a very bad workaround. You are essentially giving up security. It is like you are tired of using key to unlock a door that you decided to leave the door unlocked, for 24 hours.
I think you're all taking this security thing a little too seriously. I've been using paypass contactless credit card for years now, and I love that it doesn't need any authentication up to $20. Above that it needs the PIN. I think this is the way to go, fingerprint is not bad either.
Well that may be the case but you have to remember that nfc is still new technology. Android has been using if for years (android phones). In all of that time it took apple like 5 years to make a iphone that has specs even worth mentioning. Also android has google wallet a nfc payment system like apple pay. So really it comes down to who can have more features in the long run. On samsung phones theres samsung wallet and im pretty sure on the s5 it uses fingerprint as well.
I really love this feature but if I lost my phone, could it easily be exploited?
if you unlocked bootloader and not encrypted, yes. very easy to exploiting your phone. if not, i do not know.
That really depends on a lot of factors like for example if your phone has an unlocked bootloader and not encrypted.
The 1+ face unlock feature is not that easy to fool but it is not impossible to fool. That being said, if someone tries to unlock your phone using a photo of you and it fails five times, it will then deactivate the feature and fallback to asking you for the passcode/pin that you registered. Five attempts won't give someone a easy chance of unlocking your phone using a photo of you, that is they have to know who you are and how you look like in order to get a photo to try and fool the system in the first place.
All in all, in most likelihood, the person who finds the phone will just wipe it and keep it for themselves, unless you programmed a very easy pin/password to unlock the phone, the average person will not go through all the hassle of trying to get into your info.
HueleSnaiL said:
That really depends on a lot of factors like for example if your phone has an unlocked bootloader and not encrypted.
The 1+ face unlock feature is not that easy to fool but it is not impossible to fool. That being said, if someone tries to unlock your phone using a photo of you and it fails five times, it will then deactivate the feature and fallback to asking you for the passcode/pin that you registered. Five attempts won't give someone a easy chance of unlocking your phone using a photo of you, that is they have to know who you are and how you look like in order to get a photo to try and fool the system in the first place.
All in all, in most likelihood, the person who finds the phone will just wipe it and keep it for themselves, unless you programmed a very easy pin/password to unlock the phone, the average person will not go through all the hassle of trying to get into your info.
Click to expand...
Click to collapse
Thanks, Are there known cases of face unlock being exploited?
Basically I bought a V20 a little while ago which turned out to be a Chinese variant and I stupidly delayed on getting an unlock code.
It now seems that I have literally no way in which to switch/change the ROM to the global variant or even a custom one. Basically I am stuck with a phone that wont even allow me to use google assistant and is in a lot of ways pretty useless.
Suffice to say I am pretty pissed off but also just disappointed. Its a great phone. Amazing battery life, one of the best cameras I have even used on a phone, lightning fast etc. But it cant do half the things I want it to.
Does anyone have any advice or ways in which I might be able switch the ROM or unlock the bootloader. I am getting kind of desperate and am almost at the point of giving away the phone and buying a Xiaomi/another brand of Android.
I also have an honor view 20 Chinese version and it does everything that a American phone can do including use Google Assistant, is there something that you would like me to tell you how to make work on your phone?
xanderr89 said:
I stupidly delayed on getting an unlock code.
It now seems that I have literally no way in which to switch/change the ROM to the global variant or even a custom one. Basically I am stuck with a phone that wont even allow me to use google assistant and is in a lot of ways pretty useless.
Click to expand...
Click to collapse
It's not your fault - from what I understand, Huawei stopped issuing bootloader codes months before the V20 was even released, so there wasn't anything you could have done.
As for unlocking, in the past I've used DC Unlocker before but the caveat is that it charges you money for every bootloader code. Also, I've never been able to successfully flash a different region's ROM without soft-bricking, so YMMV.
DJW35 said:
I also have an honor view 20 Chinese version and it does everything that a American phone can do including use Google Assistant, is there something that you would like me to tell you how to make work on your phone?
Click to expand...
Click to collapse
Thanks for the reply, basically at the moment when i open google assistant, every time it tells me to go and set google as the default assistant app. I do that and set it. It then, kinda works (ie it goes back to assistant and it will listen to me while the app is open). As soon as I close assistant or restart my phone and I open the google assistant app again it tells me to do the same thing ( it loses the default setting and I am back at square one, it will never stick.)
Also if i go into the google settings and go to "Voice" and then "Voice match" it is simply grayed out. Which means I cannot train it to recognize my voice/ or say ok google to open the voice assistant.
Also when I hold down the middle navigation button it comes up with HiVoice app that is pre installed on the device.
This link seems to be what I have been having issues with. I need to remove hivoice and actually get hey google to work
NekoMichi said:
It's not your fault - from what I understand, Huawei stopped issuing bootloader codes months before the V20 was even released, so there wasn't anything you could have done.
As for unlocking, in the past I've used DC Unlocker before but the caveat is that it charges you money for every bootloader code. Also, I've never been able to successfully flash a different region's ROM without soft-bricking, so YMMV.
Click to expand...
Click to collapse
Thanks for the reply. This seems a little crazy, seems like one of the only phones that wont let you unlock the bootloader and install a different ROM. :S