I was watching the idiot box the other day and it indicated that due to the 911 phone issue and requirement, all mobile phones were required to be able to be located to an address when calling 911, and thus all phones were required to have GPS unit installed, is this correct?
If that is so, are these phones illegal in the US as they dont have one, or do they have one and we dont know about it?
In the UK it is possible to track a mobile phone, and is done with 999 call in certain circumstances a number of ways. But I don't believe they use GPS in any of them yet. the main way is to tri-anglated (spelt sommit like that!) where the signal came from, which pin-points it to a faily small, but not perfect, radius.
The US are normally slightly more advanced with that sort of thing, but probably use a similar system.
Sorry, I just read your post again, the located to an address might be what we in UK do as a Subscriber Check, which is how we locate the owners of mobile phones in the police in UK. It can only be done in certain circumstances again, due to human rights, data protections, etc etc. But does not locate where the phone is when the signal was made, instead informs us who owns and registered the phone, and to what address.
Great if the phone is a contract phone.... But with PAYG it's not always that simple... you can pick these up anywhere now, and some people don't bother registering them...
When you use your mobile phone it can usually communicate with more than 1 base station & pick the nearest, it will also identify which transmitter on the base station has the strongest signal. You may also move between base stations as signal strength varies.
This information along with the amount of time to send & receive a signal can be used to identify the location of the mobile.
If the mobile can only see 1 base station it can be used to identify the location of the mobile in relation to the base station along with the distance.
If it can see 2 or more base stations it can be used to triangulate location.
Hope this helps.
Mike
Operators are required to upgrade their networks to support E911 service and have (I seem to remember) until November 2006 to complete said upgrade. There is presently no provision requiring individual handsets to provide GPS coordinates - or any other location-indicating function. There are several initiatives being explored that, if they come to fruition, would require location-reporting functions to be an integral part of new handsets.
Many of the dumb phones (Motorola etc) do already have some kind of GPS receiver, mostly AGPS (Assisted GPS) where the mobile network provides time, ephemeris and almanach, and the receiver only needs to listen to the sat time.
But only the HP iPAQ 6515 and 6915 have a similar chip at the moment, other smartphones or Pocket PC phones (like the Universal) don't have it. With all the hype around LBS it won't take long, maybe two or three generations of devices, until this is standard anyhow.
The E911 compliance has been delayed over and over again, and will be delayed through november. To cite the late Douglas Adams "I like deadlines, especially the swooshing sound they make when they pass by."
I am particularly interested in the wizard, however on a fundamental level WM will most likely operate the same across most models in respect to this issue (or at least that is the theory).
I realize that most GSM boards have processors on them which do things like channel syncing (which is fairly time sensitive since its tdma&fdma), a5, gsm framing, and all that. You more or less connect a sim, speaker and mic, and treat the gsm rf board as a black box.
I am hoping that somewhere someone has unearthed something that allows more direct control over the gsm board on these phones. I am aware of engineering mode, however that is not quite what I wanted.
I would like to be able to at the very least set the call parameters before a call goes out. For example, lets say that I want to disable A5, sinec there are 3 standard levels one being no encryption, and the tower and the phone negotiate and agree upon the highest common, something in the phone somewhere has to say that it supports encryption.
I am just uncertain if all that is burried away in a 'black box' somewhere and its not a software problem from within WM.
If anyone has any ideas I would greatly appreciate it, even if they are pointers to research material that may help me out a bit.
On WinMobile GSM part is isolated from the windows part, like in normal PCs modem hardware is isolated from mainboard. GSM part has its own CPU, RAM, ROM, operating system, and communicates with Windows via COM-port (or USB port in Universal). For example Universal has Qualcomm MSM6250 chip with some proprietary OS. HTC Himalaya had a different chip (I don't remember it now), and OS was based on nucleus RTOS. Anextek SP200 communicator had Siemens MC45 modem inside.
GSM hardware is a black box for WinMobile OS. MS specifies only some recomendations for OEMs, and controlling encryption is not among them. You can control it if GSM vendor supports some AT command, or some other proprietary method (maybe via dev_specific RIL command).
In the case of Universal, its GSM can be controlled from a PC with the usual Qualcomm diagnostic software (QXDM, QPST, etc), when you setup the device as a pass-through bridge between PC and GSM module. But I don't know any methods of doing the same from inside WinMobile.
mamaich said:
GSM hardware is a black box for WinMobile OS.
...
You can control it if GSM vendor supports some AT command, or some other proprietary method (maybe via dev_specific RIL command).
In the case of Universal, its GSM can be controlled from a PC with the usual Qualcomm diagnostic software (QXDM, QPST, etc), when you setup the device as a pass-through bridge between PC and GSM module. But I don't know any methods of doing the same from inside WinMobile.
Click to expand...
Click to collapse
That is what I was afraid of. Most of the GSM radio boards (or individual chips) are set up to act that way, and since its faster and cheaper I really dont know of anyone that hasnt done that in any phone that was made in the last few years.
At any rate, is there any documentation that discusses how to locate which com port or other method is used to access the GSM device within a wizard (or any other htc model, odds are many of them are similar, if not identical with this subcomponent).
Are there any known AT commands? my first project is to write something similar to the gsm engineer mode program, obtaining BTS information. I am unsure if this is obtained only via AT commands or if its something more involved, but welcome any information on this.
Found what appears the be half the answer at http://wiki.xda-developers.com/index.php?pagename=RIL While that gives me access to the radio for some stuff (location data app that can work with gsmloc.org for example) it does not appear to enable me to set any parameters for a new call.
So if anyone knows of any tricks that would help say for example disable a5 crypto (on a per call basis idealy) or something similar to the setup of a call I would still appreciate hearing about that.
I know that Typhoon ( spv c500 / i-mate sp3 /Dopod 565) memory block with gsm info data. I am trying to find it in Magican - but no results. I dont know how Typhoon place this info in mem.
Greetings,
Had someone ask me a good question the other day, and this was the first place I though that might actually have an answer.
We've got at least several hundred remote sites spread all across the country and world. Almost all of them have analog modems on them to access remote data (mostly weather data, but also troubleshooting codes). Can you think of a way that a cellphone user, for any given network, could access that analog modem remotely?
It's a pickle of a problem, and frankly I can't think of anything. I've never heard of a 'bridge' type device/service that allows that kind of access, but I suspect it exists. That suspicion comes from the knowledge that lots of industries (oil and gas spring to mind) have similar types of devices.
Appreciate any ideas you may have, and thanks.
Dave
if the analog modem is connected to a wifi router or somehow support bluetooth access
otherwise no
Anyone having issues connecting to wi-fi networks on channels 12/13? On my device I'm unable to see SSIDs in these channels most of the time. Sometimes I can see networks in channel 13.
Am engaging with Google tech support, so will keep you posted.
What country are you in?
UK
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
TheReverend210 said:
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
Click to expand...
Click to collapse
Good good.
I'm wondering whether it's down to me not activating the SIM in the phone as yet? Like a double check that the phone should be allowed to use 12&13 (rather than just selecting English UK as the language).
TheReverend210 said:
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
Click to expand...
Click to collapse
There's really no difference in using that over channel 11 in your case with the co-channel interference.
YES!
It's not just me then. Home router (2.4Ghz) is on ch.13 and when i return home the device will not auto-connect until i toggle wifi off and back on again. Wifi works fine until i leave again. connects fine to my wifi network at work but that is different channel and on 5Ghz too.
RMA'd my device and the new one was bad. Wouldn't see my network at all, but wouldn't register my Sim card either so I have just returned this replacement device. Replacement number 2 is on the way.
I switched to ch.12 and the same thing happens at home. Didn't try any other channels as they are too noisy. So I wonder if this is a software issue? I'm in the UK and the router is made by technicolor for Plusnet.
j3di said:
YES!
It's not just me then. Home router (2.4Ghz) is on ch.13 and when i return home the device will not auto-connect until i toggle wifi off and back on again. Wifi works fine until i leave again. connects fine to my wifi network at work but that is different channel and on 5Ghz too.
RMA'd my device and the new one was bad. Wouldn't see my network at all, but wouldn't register my Sim card either so I have just returned this replacement device. Replacement number 2 is on the way.
I switched to ch.12 and the same thing happens at home. Didn't try any other channels as they are too noisy. So I wonder if this is a software issue? I'm in the UK and the router is made by technicolor for Plusnet.
Click to expand...
Click to collapse
If channel 11 is noisy, then so is 12 and 13.
Sent from my Nexus 6P using Tapatalk
TheReverend210 said:
I seem to be the only person on my street that knows channel 13 exists. No issues for me connecting. Although I run my phone to my 5Ghz connection normally, I can connect to my 2.4Ghz if needs be.
Click to expand...
Click to collapse
You might want to change to channel 11. With the current setup you are not only killing your own data rates, but also the rates of everyone on channel 11. These channels are not supposed to overlap, because that creates interference. Switch to channel 11.
This is my WiFi situation. I'm normally on CH.13, but switched to 12 as a test.
My 2nd unit arrived last week, and unfortunately it's the same issue as before - no channels 12 or 13, not even visible. I'll be back in touch with Google today.
Hopefully this is a software issue rather than Google/Huawei spec'ing a duff wifi chipset.
Google spoken to and basically it's a case of tough-titty - some devices aren't going to work with channels 12 & 13.
For anyone else reading this, I had this problem and 'solved' it.
If you find that you can't see channels 12 and 13 then it's almost definitely caused by the Wifi country code restrictions.
I got my Nexus 6P here in Korea and initially tried it out with no sim card. Even though the location is set in settings, without a sim card it doesn't get the wifi country code set, and I couldn't see those channels. As soon as I inserted a Korean sim card, I was able to see them.
If you are in the UK or elsewhere, using a local sim card and you can't see those channels then chances are either your country doesn't allow it or the code is already set. Either way, your options are just accept it or try one of the 'not officially supported' ways to getting around it. That's likely why Google said you were out of luck. It's possible but involves rooting etc. I think. Just search for 'change wifi country code android'. Good luck.
throwawaynexus said:
For anyone else reading this, I had this problem and 'solved' it.
If you find that you can't see channels 12 and 13 then it's almost definitely caused by the Wifi country code restrictions.
I got my Nexus 6P here in Korea and initially tried it out with no sim card. Even though the location is set in settings, without a sim card it doesn't get the wifi country code set, and I couldn't see those channels. As soon as I inserted a Korean sim card, I was able to see them.
If you are in the UK or elsewhere, using a local sim card and you can't see those channels then chances are either your country doesn't allow it or the code is already set. Either way, your options are just accept it or try one of the 'not officially supported' ways to getting around it. That's likely why Google said you were out of luck. It's possible but involves rooting etc. I think. Just search for 'change wifi country code android'. Good luck.
Click to expand...
Click to collapse
I am afraid that the issue is not as simple. I also have problems with channels 12 and 13, however my phone can connect to those channels, but only for a while. I quote the report I filed in the AOSP bug tracker (not yet assigned, though):
Before I continue, I am based in Switzerland, use a Swiss mobile provider (Swisscom), and I bought my phone through Google in Switzerland. This is relevant because in Europe 802.11b/g/n channels 12 & 13 are allowed, while in the North America they are allowed only under "low power conditions" with the effect that, AFAIK, many devices simply do not support them. My Nexus 6P however should (and shall) support those two channels.
Now, the problem.
I have two access points at home, both in the 2.4 GHz band: one on channels 4+6 and the other (normally) on channels 12+13. What I noticed is that my Nexus 6P would initially connect to the strongest signal independently from the channel, as expected, but then after a while (a couple of hours, maybe) would just stop seeing the signal on channels 12 & 13. Not just my own WLAN, but also neighborhood WLANs on the same channels. This means that the phone can be sitting a couple of meters from the AP in my office (channels 12+13) and be connected to the AP at the opposite corner of the building (the one on channels 4+6). I checked with "WiFi Analyzer" and the phone really does not see any signal above channel 11.
Disabling and re-enabling WiFi will make the phone see channels 12 & 13 once again. However after a while the problem appears again.
At home this is just an inconvenience: I moved the frequency of the second AP to a different channel and that "solved" the problem. On the other hand this might be a much more serious problem when I am in an environment where I can't change the WiFi settings. Maybe I want to connect to a public hotspot broadcasting on the "wrong" channels or I am at the office in an area covered by APs on channels 12 & 13. Tough luck.
Incidentally, I saw at least one report of someone who had exactly the same issue: he had to disable WiFi and enable it again to get the phone to connect to his WLAN (on channel 12 or 13, I can't remember). I also have to say that in our household we have a few other Android devices (2 x Nexus 7, 1 x Nexus 9, 2 x Nexus 4, 1 x Moto X Play) running either 6.0.1 or 5.1.1 and a few other devices (iPhone 5S, iPhone 6, laptop, 2 x Kindle) and none exhibits this behavior. It seems to be specific to the 6P.
I suspect that after a while the WiFi driver simply reverts to its default regulatory domain ("US", I assume) and stops listening to channels 12 and 13. Why it might do so is anyone's guess. Maybe doze interferes with the driver.
Same problem here. The only way to reconnect to WiFi channel 12 or 13 is to manually switch WiFi off and on again on the 6p.
I'm in Hungary.
Guys, there is a thread in the Nexus Help Forum and I reported the issue in the AOSP Bug Tracker. Add your contributions to those threads and star them. Let's try to bring this to Google's attention, otherwise we will never get any action on this topic.
Edit: For some reason I can't add links to the post. Please search issue 197106 ("WiFi 2.4 GHz channels 12 & 13 not working properly on Nexus 6P running 6.0.1") in the AOSP Bug Tracker and the post "My Nexus 6P can't connect to Channel 12 or 13 WIFI's" in the Google Product Forums.
Roberto
I have been trying for a week to extract some information from Google and Huawei, but I must say that their support just doesn't know anything about this issue. It's even difficult to get someone to understand what the problem is: one Google support guy thought I was talkng about LTE channel 12, for example. Huawei support started talking about options in the WiFi settings that are not there, then they wanted to guide me through adding a new WLAN, and finally started clutching at straws, giving more and more fantastic explanations of why it might be so.
Bottom line is: nobody I talked to ever heard about this issue.
I would really like to understand if it could be a hardware issue (which I honestly doubt) because my RMA window is closing soon and I don't honestly know what to do: apart from this WiFi issue my 6P is absolutely flawless and I do not want to risk getting a new telephone only to find out that WiFi still does not work as expected and it's also got other issues. (And, yes, something like this already happened to me.)
robertototaro said:
I have been trying for a week to extract some information from Google and Huawei, but I must say that their support just doesn't know anything about this issue. It's even difficult to get someone to understand what the problem is: one Google support guy thought I was talkng about LTE channel 12, for example. Huawei support started talking about options in the WiFi settings that are not there, then they wanted to guide me through adding a new WLAN, and finally started clutching at straws, giving more and more fantastic explanations of why it might be so.
Bottom line is: nobody I talked to ever heard about this issue.
I would really like to understand if it could be a hardware issue (which I honestly doubt) because my RMA window is closing soon and I don't honestly know what to do: apart from this WiFi issue my 6P is absolutely flawless and I do not want to risk getting a new telephone only to find out that WiFi still does not work as expected and it's also got other issues. (And, yes, something like this already happened to me.)
Click to expand...
Click to collapse
Hello, I also have the same problem. As I can report it to Google? I have not found a way.
gmarti said:
Hello, I also have the same problem. As I can report it to Google? I have not found a way.
Click to expand...
Click to collapse
Did you call the Google Store Support? I hope that if they hear the same reports repeatedly they will take notice.
If your telephone is unlocked (and if you are on XDA chances are it is), flash Franco's kernel. I did it today and now my problems with WiFi are gone. Plus Franco's is known to be very battery efficient. It's a win-win situation.