Germany: Emergency screen doesn't allow to call the police - Moto G 2015 Q&A, Help & Troubleshooting

I use a Moto G (3. Gen.) in Germany, running in English. From the lock screen, I slide up to reveal the phone PIN input, and choose "Emergency" on the bottom. Now, I input "110", which is the German police emergency number, and it says, "110 is not an emergency number" (have a screenshot, but don't know how to post it here).
On the other hand, it lets me call 112 the same way, which is the German firefighters emergency number.
This is obviously a problem, and I'd like Motorola to react to this as soon as possible. What should I do?
Edit: This might also affect other phones, and needs to be addressed somehow!

Related

[Request] Emergency number override

Hi
I have a request for a software update for my HTC touch Pro (althought this problem is on ALL HTC phones). Since HTC apparently don't care about fixing this themself I was hoping some of you guys could help me out.
I'm located in Norway and here we have three emergency numbers to call:
110 - Fire brigade
112 - Police
113 - Ambulance
The problem is that apparently HTC have decided that no ones needs three emergency numbers and they have made the assumption that 911 = 112. This means that if I want to call the fire brigade and I dial 1-1-0 and hit the call button the phone overrides what I have dialed in and calls 112 instead
This means that you have to explain your emergency to a police officer first that then calls up the department you meant to call and gives them the information one more time. Valuable time is therefore lost if you have an emergency where someone is hurt.
Any help or advice on how to solve this problem would be appreciated.
EU decided that 112 is enough whenerver you are (within EU of course)...
Cheers
Chris
Well that is just brilliant. Means I can't get the help I need when I need it.
I do get that most phones will just enable me to call 112 if my key lock is activated, but when I do type the exact number to the emergency service I need I don't want to talk to some police officer.
So anything I can do to fix this mess?
that's an interesting point, I live in Australia so if I put a custom rom on will 000 work (our emergency number)?
hidden_hunter said:
that's an interesting point, I live in Australia so if I put a custom rom on will 000 work (our emergency number)?
Click to expand...
Click to collapse
That is one of the points I want help to find out. I'm not sure if this info is even stored in the ROM or if it is somehow hard decoded into the phone.
I know that you can call the american emergency number 911 in norway and it will reconnect you to our 112. So most likely it will reconnect also other emergency numbers. Maybe that is what causes the problem in my case? That the phone thinks that any random 3 digit number I call is an emergency number somewhere in the world and that it connects it to our police emergency number.
No one have any more ideas on this issue?

[Q] Droid X programming code?

I have searched and searched for how to get to the programming menu for the DROID X.
We bought this phone from a guy that flashed it to Metro PCS and it worked perfect.
We want to use it for Metro as well. But for some reason the workers say they need a programming code for it because it's not one of their own phones. We tried telling the worker the model number because I guess sometimes you can get the code from the M#, but it didn't work. I have searched online that you can do ##PROGRAM and then send, then 000000, but the only screen we had was the "Touch the Droid to activate" and it has Emergency call and Change language at the bottom. We tried typing ##PROGRAM 000000 in the E. Call but it just tells us it's not an emergency number.
Since we've called the MetroPCS customer service, the first time, we couldn't get the ESN, because the MEID HEX isn't behind the battery, so that worker did us no good. Then we rebooted the phone and it actually came up past the "Click the Droid to activate" screen and we're actually at a home screen now, but with no service and etc. We talked to another worker and we got disconnected. The third worker supposedly set up our account and gave us a phone number but couldn't program because the model number wouldn't work. IDK.
All I want is the programming menu code, so they can fully activate the phone. I'm sorry if this is confusing, it was very confusing to us too!
Sorry this is so long, I thought maybe more details is better than too little details. Thanks for whoever replies.
Sara
EDIT:: Since we have been able to get to the homescreen somehow, I guess we could try doing ##PROGRAM on the normal dial pad, but my boyfriend has the phone so I will wait for him to come over. I also have seen that on some Droid X's the ##PROGRAM doesn't work and just dials the number because of some ROM. Will I have that problem since the phone is flashed over to Metro?
Droid X
I had same issue, if the phone is waiting for network program and you can't do anything but press a green droid then you can't enter ##program.. Once the phone is one with metro you can then enter the ##program and 000000 .. I just did that here.
Phone has to be activated before you can enter.. Is what I found.
hope I helped
wholesale - florida .com
Mark
MikeB89 said:
I have searched and searched for how to get to the programming menu for the DROID X.
We bought this phone from a guy that flashed it to Metro PCS and it worked perfect.
We want to use it for Metro as well. But for some reason the workers say they need a programming code for it because it's not one of their own phones. We tried telling the worker the model number because I guess sometimes you can get the code from the M#, but it didn't work. I have searched online that you can do ##PROGRAM and then send, then 000000, but the only screen we had was the "Touch the Droid to activate" and it has Emergency call and Change language at the bottom. We tried typing ##PROGRAM 000000 in the E. Call but it just tells us it's not an emergency number.
Since we've called the MetroPCS customer service, the first time, we couldn't get the ESN, because the MEID HEX isn't behind the battery, so that worker did us no good. Then we rebooted the phone and it actually came up past the "Click the Droid to activate" screen and we're actually at a home screen now, but with no service and etc. We talked to another worker and we got disconnected. The third worker supposedly set up our account and gave us a phone number but couldn't program because the model number wouldn't work. IDK.
All I want is the programming menu code, so they can fully activate the phone. I'm sorry if this is confusing, it was very confusing to us too!
Sorry this is so long, I thought maybe more details is better than too little details. Thanks for whoever replies.
Sara
EDIT:: Since we have been able to get to the homescreen somehow, I guess we could try doing ##PROGRAM on the normal dial pad, but my boyfriend has the phone so I will wait for him to come over. I also have seen that on some Droid X's the ##PROGRAM doesn't work and just dials the number because of some ROM. Will I have that problem since the phone is flashed over to Metro?
Click to expand...
Click to collapse

[Q] Fake and undefinied call?

Hi,
yesterday I got a call, from undefinied number... that is very interesting - because at services from my provider I have blocked "calls from undefinied number", and in the billing list - there is no this call, also a man in the provider help line says that there is no this call. My phone says - call exist (1 notification, missed call). I don't have any "fake call" applications installed. Can u help my find it out? I dont know what I have to do, or is my phone secure...
Man on help line also says, that some phones have function - combination of keys, or just function from menu - that generates fake call, and then number is undefinied, because in reallity - noone calling. HTC Sensation have it? May I generate it accidentaly?
Also i can say that I've not hear any ring, or wibrations, but maybe I've been in another room, but this is quiet impossible.
Plase help - I'm little bit afraid.
And sorry for my english - I hope u understand
I had something similar to me happen the otherday, Had a call form an unkown number, picked it up and it went down straight away, seemed like some kind of software bug tbh, it happend as soon as my reception come back from no signal

[Q] How to prevent USSD message from being sent?

Hey.
I'm not really sure where this question is belong to, so I'm posting it here and in "Android Q&A" as well, hopefully to get a decent answer...
I've just bought an Android phone (JIAYU F1 - link here), and it's really great.
Thing is, I have special SIM from my carrier, that allows me to use only certain models of phones, and not others.
I moved the SIM from the old phone to the new one - and for the first 10 second - it was great.
I could dial numbers, and recive call from other phones. BUT - after like 10 sec's or so - I saw the words "USSD sent" on the screen, some blank message appears, and since I clicked OK (no other choice...) - I couldn't make and receive any calls.
My guess is that this "USSD message" is responsible for the whole mess, reporting to my carrier which phone model using the SIM right now.
This is why I want to find a way to prevent it to be sent to my carrier.
I'll be thankful if you can help find this way...
Thanks in advance.

[Completed] Unwanted texting prefixes and "Yi Dialler" prompts before making calls.

Hello all,
I'm unsure about where to post this issue I am having with my handset. Let me explain a little about what is going on, and maybe someone can redirect me to where I should post the full details and hopefully get some answers
Have a Huawei C8813 Handset from China. It was payment for a computer job I did some time ago. I suspect it was a contract phone of some description, however it was completely wiped when I received it.
I had to perform some build prop edits in order to get it working on 2 Degrees here in New Zealand. These involved (ro.cdma.home.operator.numeric=53024) and other related lines.
The issue I am having at the moment is that when I receive calls from other cellphones in New Zealand, they come through with no International prefix (this is fine, and desired). However text messages I receive from NZ cellphones come through with the International prefix. So if I were to receive a call from 022022022, it would come through as such, but a text message from the same number would appear on my handset as +6422022022. This causes me to attempt to enter both the prefixed and non prefixed numbers into every entry in my address book. Text messages will send fine to either the prefixed or non-prefixed number, but this causes message thread separation (undesired).
Further to this, if I make calls to a non-International-prefixed number (a local New Zealand cellphone) eg 022022022, I get a dialog up titled ""Yi Dialer" (China +86)" with the following options: "Call China (International Roaming Call)", "Call China (**133 call back)", "Call other country", "Call local". Obviously the call goes through fine if I select "Call local". However, if I put the international prefix in front of the number for NZ (+64,) calling a number in NZ, it bypasses "Yi Dialer" altogether and just makes the call eg: +6422022022.
I have searched the internet far and wide and can find very little related to "Yi Dialier" (or "easy dialer" if translated from Chinese). I have checked out all of the stock applications that came with the phone and none appear to be related to dialing.
I am interested in perhaps a build.prop or similar setting that may erase this issue and make the phone believe it is based in New Zealand. As far as I can work out, the handset thinks it is roaming all of the time, when in fact it is not. There is no convincing it of this through regular Android settings with regards to the carrier or cellphone network.
Any help or direction with this would be greatly appreciated. I am happy to provide screenshots and exact build.prop edits I have done to make the phone operate here in NZ.
Thanks in advance,
Mike
MikeNZd4d said:
Hello all,
I'm unsure about where to post this issue I am having with my handset. Let me explain a little about what is going on, and maybe someone can redirect me to where I should post the full details and hopefully get some answers
Have a Huawei C8813 Handset from China. It was payment for a computer job I did some time ago. I suspect it was a contract phone of some description, however it was completely wiped when I received it.
I had to perform some build prop edits in order to get it working on 2 Degrees here in New Zealand. These involved (ro.cdma.home.operator.numeric=53024) and other related lines.
The issue I am having at the moment is that when I receive calls from other cellphones in New Zealand, they come through with no International prefix (this is fine, and desired). However text messages I receive from NZ cellphones come through with the International prefix. So if I were to receive a call from 022022022, it would come through as such, but a text message from the same number would appear on my handset as +6422022022. This causes me to attempt to enter both the prefixed and non prefixed numbers into every entry in my address book. Text messages will send fine to either the prefixed or non-prefixed number, but this causes message thread separation (undesired).
Further to this, if I make calls to a non-International-prefixed number (a local New Zealand cellphone) eg 022022022, I get a dialog up titled ""Yi Dialer" (China +86)" with the following options: "Call China (International Roaming Call)", "Call China (**133 call back)", "Call other country", "Call local". Obviously the call goes through fine if I select "Call local". However, if I put the international prefix in front of the number for NZ (+64,) calling a number in NZ, it bypasses "Yi Dialer" altogether and just makes the call eg: +6422022022.
I have searched the internet far and wide and can find very little related to "Yi Dialier" (or "easy dialer" if translated from Chinese). I have checked out all of the stock applications that came with the phone and none appear to be related to dialing.
I am interested in perhaps a build.prop or similar setting that may erase this issue and make the phone believe it is based in New Zealand. As far as I can work out, the handset thinks it is roaming all of the time, when in fact it is not. There is no convincing it of this through regular Android settings with regards to the carrier or cellphone network.
Any help or direction with this would be greatly appreciated. I am happy to provide screenshots and exact build.prop edits I have done to make the phone operate here in NZ.
Thanks in advance,
Mike
Click to expand...
Click to collapse
Hi, thank you for using XDA assist.
There is a general forum for android here*http://forum.xda-developers.com/android/help*where you can get better help and support if you try to ask over there.*
Good luck.

Categories

Resources