My Verizon GNex had this issue since day 1 of Jelly Bean when I'm on wifi. I assumed it was a bug in all of the Roms/ports. I just got my nexus 7 three days ago and I have the problem here also. After some exhaustive searching I have found others with this "Vegas" issue, but no solution.
Anyone got any ideas?
Have you considered that your devices are trying to tell you something? Go to Las Vegas...
Ops... you said where you were in the title....
So what are your generic coordinates being given to you or are you just going by what Google Maps is telling you.
Try getting one of the GPS apps and look at the coordinates it is saying you are at and then look them up and see if they point to Las Vegas.
I like your philosophical approach to an answer. "Where is here".
Seriously though, it always puts me in the zumanity theater at the New York New York casino in Vegas. Other people from New Jersey to Los Angeles also have this Vegas problem. Maybe Google has some subtle advertising thing going on with Vegas?
Do you have this problem when connected to other access points? I'm not an expert in how Android determines your coarse location, but I believe that either your access point/router was in Las Vegas at some point and Google cached it as such or your ISP is routing your traffic through Las Vegas.
Haven't tested with my 7. I have on my GNex. The problem only occurs at home. I assume it is not an access point issue because I have a router behind router (one at&t 2wire and one belkin) and have connected to both and they both exhibit the bug.
This problem is isolated to jelly bean. 3 other android tablets and 3 other android phones and they all work flawlessly, not including various laptops and desktops where Google assumes a very close location based solely off IP.
Is there any way to not have network assist the GPS?
Maybe your Nexus 7 passed through Vegas at one point and as everyone knows, whatever happens in Vegas stays in Vegas.
On a more serious note, have you disconnected from WiFi and see where it locates you after you download offline map of your area? If it locates you right without wifi it means that there is this site that I am forgetting the name that manages the location of routers and lets you reset them to the correct location. It has the word sky in the url is all I remember.
EDIT: I'm an idiot, I missed your last post. That's really weird...
normanb20 said:
Haven't tested with my 7. I have on my GNex. The problem only occurs at home. I assume it is not an access point issue because I have a router behind router (one at&t 2wire and one belkin) and have connected to both and they both exhibit the bug.
This problem is isolated to jelly bean. 3 other android tablets and 3 other android phones and they all work flawlessly, not including various laptops and desktops where Google assumes a very close location based solely off IP.
Is there any way to not have network assist the GPS?
Click to expand...
Click to collapse
You can disable it under Location Services but then you'll be relying solely on GPS to provide your location. You might also try remaining connected to your wifi while you get a GPS lock so that the correct GPS location of your access point gets sent back to Google. I don't know how long it might take for Google to update its own database with the correct info though.
Yes, I suspect it's the wifi or network location, NOT anything related to GPS. Wifi is somewhat easy to look up..
If you're on Linux.... prepare for long command.. All one line. Note the YOUR:WIFI:MAC:ADDRESS in there, replace it with your AP's mac address.
Code:
/bin/echo '{"version": "1.1.0","host": "maps.google.com","request_address": true,"address_language": "en_GB", "wifi_towers": [{"mac_address": "YOUR:WIFI:MAC:ADDRESS","signal_strength": 8,"age": 0}]}' | sed -e 's/" /"/' -e 's/ "/"/g' > /tmp/post.$$ && curl -X POST -d @/tmp/post.$$ http://www.google.com/loc/json | sed -e 's/{/\n/g' -e 's/,/\n/g'
normanb20 said:
My Verizon GNex had this issue since day 1 of Jelly Bean when I'm on wifi. I assumed it was a bug in all of the Roms/ports. I just got my nexus 7 three days ago and I have the problem here also. After some exhaustive searching I have found others with this "Vegas" issue, but no solution.
Anyone got any ideas?
Click to expand...
Click to collapse
What the heck does that have to do with GPS?
Your title says gps locates you in Vegas.
Sent from my Nexus 7
Hemidroids said:
What the heck does that have to do with GPS?
Your title says gps locates you in Vegas.
Sent from my Nexus 7
Click to expand...
Click to collapse
Well the Location set by GPS icon appears in the status bar. I figured it was a problem with network assisted GPS.
Houston, we have a problem......
khaytsus said:
Yes, I suspect it's the wifi or network location, NOT anything related to GPS. Wifi is somewhat easy to look up..
If you're on Linux.... prepare for long command.. All one line. Note the YOUR:WIFI:MAC:ADDRESS in there, replace it with your AP's mac address.
Code:
/bin/echo '{"version": "1.1.0","host": "maps.google.com","request_address": true,"address_language": "en_GB", "wifi_towers": [{"mac_address": "YOUR:WIFI:MAC:ADDRESS","signal_strength": 8,"age": 0}]}' | sed -e 's/" /"/' -e 's/ "/"/g' > /tmp/post.$$ && curl -X POST -d @/tmp/post.$$ http://www.google.com/loc/json | sed -e 's/{/\n/g' -e 's/,/\n/g'
Click to expand...
Click to collapse
I ran that command on my desktop and it returned my location correctly. I assume that is why the non jelly bean devices get the location correct. Its only Jelly Bean combined with my home internet that puts me in vegas.
Another quick test is just a goto speedtest.net, and see where they show you when you run their default test. It is possible, someone else mentioned, that your device came from your isp having been in vegas previously.
Altho really if you using the gps location, and not wifi/network location, it should be reading from the gps transmitter in your device ... Fkin satellites, how do they work?
Sent from my rooted Nexus 7 via xda-developers app.
Related
Here's that donate button you guys were looking for. >_>
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7ELH2CPLUZLQY
ANECDOTAL EVIDENCE IS NOT REAL EVIDENCE!!!
Get My Tracks from Google Market and post your GPS trip.
My first Froyo 2.2 test:
http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=108472444080796738089.000491a2c10ac25693114
Jupiter.XML
Jupiter.XML is not a Samsung specific file.
Jupiter mods
I've been modifying some information from the Jupiter XML to get different results. After installing a new jupiter.XML, got to LBSTestMode and select Delete GPS Data.
They can be installed by:
Code:
adb push jupiter.xml /system/etc/jupiter.xml
or (if permission denied)
adb push jupiter.xml /sdcard/jupiter.xml
adb shell
su
busybox cp /sdcard/jupiter.xml /system/etc/jupiter.xml
rm /sdcard/jupiter.xml
I made some changes to Jupiter (hopefully) enabled low noise amplification and remove a lag while trying to regain a hot fix.
View attachment Jupiter-v001.zip
Here's a v002 without ANY AGPS data. Because of a theory that AGPS is causing inaccuracy problems, I've disabled it completely. The fix will take longer, but maybe it'll be more accurate. With AGPS off, you won't get signal indoors. Remember that please and this is for the sake of testing.
AGPS doesn't have anything to do with accuracy. Stick with v001
Removed
You should also disable AGPS within Android
You can disable AGPS this way
Code:
adb shell
su
cd /dbdata/databases/com.android.providers.settings
sqlite3 settings.db
update secure set value="0" where name = "assisted_gps_enabled";
.quit
reboot
v003 has AGPS again. Make sure you enable AGPS in android provider settings (see above). I also switched the SUPL to supl.google.com:7576 instead of spirent. I changed the FrqPlan to match the Blackberry devices FrqPlan.
View attachment Jupiter-v003.zip
v004 is based on XWJP4 from a i9000 build.
I changed a lot. I made my changes to jupiter.xml (disabled the LNA for testing) and I'm using unstable 300ppb (even though I think ppb are meaningless since ppm are more important). It has LBS data enabled from this firmware. Also, I put the new drivers and forced SUPL to supl.google.com in both jupiter and gps.conf
pulled for more testing
v005 are tweaks from XWJP4. I couldn't get the new libgps.so to work on our Captivates (crashes on boot). gps.conf goes in (/system)/etc
View attachment Jupiter-v005.zip
v006 is JI6 compatible. JI6 (the Froyo build) uses the same GPS driver structure as i9000 XWJP4, so we might be able to swap files. This also means it's compatible with i9000 devices. This is mostly playing with SUPL to point to Google and remove a possible fix lag.
/system/etc/jupiter.xml
/system/etc/gps.conf
/data/gps/secgps.conf
View attachment Jupiter-v006.zip
Jupiter Research
It's a interface configuration file for GLGPS from Broadcom. If Samsung messed up, IT'S HERE
These are Samsung's settings (with OH7 OTA)
LogPriMask="LOG_DEBUG"
LogFacMask="LOG_GLLAPI | LOG_DEVIA | LOG_NMEA | LOG_RAWDATA | LOG_DEVMS | LOG_ASIC_IO | LOG_BBTEST | LOG_DEVET | LOG_MESM | LOG_DEVKF | LOG_DEVJG | LOG_DEVMR"
FrqPlan="FRQ_PLAN_26MHZ_2PPM_26MHZ_300PPB_UNSTABLE"
RfType="GL_RF_4751_DANUBE"
BrcmRFwildBase="0x1E2D6409"
BrcmRFclkDiv="21"
BrcmRFclkRefHz="26000000"
pps-enable="false"
pps-offset-ms="0"
pps-width-ns="100"
THIS IS WHAT WE SHOULD PLAY WITH!
I'm done some research and these are values for FrqPlan:
The TCXO has to be accurate +/- 2.0 ppm.
The number after FRQ_PLAN_ describes the type of TCXO used, for example,
FRQ_PLAN_13MHZ_2PPM is a 13MHz reference clock.
FRQ_PLAN_13MHZ_2PPM
FRQ_PLAN_16_8MHZ_2PPM
FRQ_PLAN_26MHZ_2PPM
FRQ_PLAN_10MHZ_2PPM_10MHZ_50PPB
FRQ_PLAN_20000_2PPM_13MHZ_50PPB
FRQ_PLAN_27456_2PPM_26MHZ_50PPB
FRQ_PLAN_33600_2PPM_26MHZ_50PPB
FRQ_PLAN_19200_2PPM_26MHZ_100PPB
RfType values:
GL_RF_PALS7
GL_RF_BARRACUDA
GL_RF_2075_LN22
GL_RF_2075_BRCM
GL_RF_PALS7_BRCM
GL_RF_BARRACUDA_BRCM
GL_RF_BARRACUDA_EXT_LNA
I found this info here:
http://openembed.com/files/pdk15_imx35__Linux_RM.pdf
Captivate Settings from OTA OH7:
Code:
I stripped everything else because we don't need it. We're not debugging. In fact, that might be a reason for the lag (all that unnecessary debugging).
This is the HTC Legend's XML file
Code:
See a difference? NO debugging and different FRQPlan (different chip anyway)
I FOUND SOMETHING WORTHWHILE!!!
Blackberry device that uses the same chip. Here are the settings for gl1
Code:
Blah blah blah! Re-education part
I think a lot of you are playing with options, not knowing what you're doing. I've written some GPS applications for WinMo (check my post history) and have taken a look at this issue. I'm currently working on a project that uses the GPS and Android phones. I negotiated a deal with AT&T to get 50 Samsung Captivates (@ $150 each) with 2GB/mo ($25/mo) for a client and I think I'm going to cancel that.
I don't think many of you understand what's going on with the phone or what AGPS does. AGPS is basically GPS support with cell towers. There are different levels of cell tower support.
MS-Based usually just uses the cell tower's location (not yours) to figure out where you are. This will allow you to go online, and get the cell tower number and find out it's GPS location. From there, the GPS using satellite charting data to find and keep a fix. GPS almanac data (says where the satellites are in the sky) can be supplied by the cell tower (the point of MS-Based), downloaded over the internet or downloaded from GPS signals (the last of the 3 being the slowest). Getting a fix without having any satellite data or positioning is known as a cold fix.
MS-Assisted does what you guys would already figure is happening. It uses the cell tower positioning and cell tower signal central to triangulate your position. In WinMo this would disable your data connection but it seems that's not the case in Android. Regardless it might slow down your internet. Obviously the accuracy here is poor.
SUPL just tells you the lat/long position of the cell towers so changing servers does nearly nothing. Google may have faster SUPL servers than spirent but the data should be the same. Once you have that data, it should be cached locally (but who knows, this is Samsung we're talking about.)
The problem is, technically speaking, the GPS should work even without AGPS. I have a couple of GPS devices with SIRFIII and it works beautifully, no AGPS needed. It should be able to download the almanac, ephemeris and time from the GPS satellites without any cell towers. That's how you know the issue isn't your settings.
Disable AGPS and you'll realize you have no options to play with. You're all playing with AGPS settings which aren't really hardware based GPS (and thus inaccurate). AGPS is not accurate. It was never meant to replace hardware GPS (which is why they put hardware GPS in phones). Hardware GPS has much more accuracy but the fact is, hardware GPS is NOT working on the Samsung Captivate. That's the baseline problem. Forget your AGPS settings. AGPS should only help you with almanac data and getting faster fixes but after that it should be running on standalone hardware and only fall back to the inaccurate AGPS when you lose a clear view of the sky (like when you're in a tunnel).
I notice little issue when I'm standing still. It's when I'm moving that the accuracy dies. With further investigation, it seems the GPS literally stops updating the location after a couple of seconds. You don't notice if you're standing still since you're in the same spot, but when you're driving you'll see it. The GPS freezes for about 20 to 30 seconds.
The question is: Why is it not working?
Here are my hypotheses.
1) There's a function running that borks the GPS and makes the GPS driver crash or lag. The GPS driver quietly reboots and then it gets a fix. This could be the reason why, after disabling and enabling GPS, it grabs a hot-started fix of a location it was struggling to get before. You manually reset the GPS driver. I've tested it with Google Maps/Navigation. The GPS doesn't move for 30 seconds. It freezes, but when I close (disable GPS) and open the app (enable GPS) it gets a hot started fix in 5 seconds. Had I not disabled and enabled the GPS, it would have lagged there. This could be a software issue.
2) The GPS isn't using the almanac data. The almanac data says where the GPS satellites are now and where they will be. The GPS uses this to track. If this isn't used, it needs to get a fix again every so often.
3) Cell towers are actually messing you up because their times are desynchronized or almanac data is outdated. (and we all would love to blame AT&T)
As for my project, I'm ready to change my order from 50 Captivates to 50 Xperia X10 phone. The X10 actually has a WORKING GPS (meaning my app works fine and isn't the cause). I have both phones that AT&T gave me to develop my application. I wis
Thank you for the info. I am eagerly awaiting a true fix
makes sense, let us know of your future findings
I just want to say this is an excellent post and very informative. Thanks for writing it. Unfortunately, I'm seriously debating returning my Captivate over this whole fiasco. The OTA hotfix that's pushing out today does nothing to fix this issue and I some how doubt this will be resolved any time soon.
There are two test ROMS that were leaked, JH2 and JH3, that already have GPS logging enabled by default. We've been turning it off since the data isn't useful to us and it fills up the phone's storage quickly. Would those logs be useful to you?
I have a Captivate, so I don't need the logs really. What are your experiences with Dynamic Accuracy off? I feel like that could be the issue. I know the GPS disables after 120 seconds with Dynamic Accuracy off, but when it does work, how well does it work for you guys?
Also, is the GPS issue for ALL Galaxy S devices? (Vibrant/Captivate/i9000)
I just got my captivate so i havent been around long, but i know for sure it affects all the US versions of the Galaxy S series (Fascinate, epic 4g, captivate, vibrant), im not sure about the European i9000
It affects all Galaxy S phones regardless where you bought them. And the issue is with BroadCom (the GPS chip maker). There is a faulty driver and/or faulty chip firmware. From what I gather, BroadCOM gave Samsung the updated driver at the end of the August which our latest JH7 probably doesn't have.
faspalma said:
I just want to say this is an excellent post and very informative. Thanks for writing it. Unfortunately, I'm seriously debating returning my Captivate over this whole fiasco. The OTA hotfix that's pushing out today does nothing to fix this issue and I some how doubt this will be resolved any time soon.
Click to expand...
Click to collapse
According to Engadget, the latest update being pushed by AT&T "fixes" the gps issues: http://www.engadget.com/2010/09/22/samsung-captivate-gets-gps-fix-other-galaxy-s-versions-wait-pat/
compuguy1088 said:
According to Engadget, the latest update being pushed by AT&T "fixes" the gps issues: http://www.engadget.com/2010/09/22/samsung-captivate-gets-gps-fix-other-galaxy-s-versions-wait-pat/
Click to expand...
Click to collapse
Engadget is full of it.
foxbat121 said:
Engadget is full of it.
Click to expand...
Click to collapse
I think it is more that samsung "is full of it", because they are stating the gps is fixed. Engadget is just relaying what Samsung is saying....
Wasn't the source released for the captivate kernel? I would love to see the GPS source code
Sent from my SAMSUNG-SGH-I897 using XDA App
CLShortFuse said:
Wasn't the source released for the captivate kernel? I would love to see the GPS source code
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
GPS and most all of the drivers are not part of the source release.
Can we recompile the driver, does anybody know?
This is the source code for Nokia's driver for the same chip.
http://www.mail-archive.com/[email protected]/msg03733.html
But I don't think they use NMEA
Ok I hear what you are saying, I never messed with the settings and claimed that it was fixed. I am under the impression that my gps is working and always was but with the new jh7 firmware (ota version) it definitely works better, I had the samsung-firmwares.com release and it made no difference but designgears rooted decided version of thee ota release made a difference. What settings need to be changed to disable all network assisted location to test if I'm actually getting a gps fix without agps?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Dani897 said:
Ok I hear what you are saying, I never messed with the settings and claimed that it was fixed. I am under the impression that my gps is working and always was but with the new jh7 firmware (ota version) it definitely works better, I had the samsung-firmwares.com release and it made no difference but designgears rooted decided version of thee ota release made a difference. What settings need to be changed to disable all network assisted location to test if I'm actually getting a gps fix without agps?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Network assist is not a problem. There is no need to disable it.
Just take a test drive using Google Navigation. Ignore the fact that it always seems to be dead on your position (because all navigation software snap you to the nearst road). Instead, pay close attention to:
1. Whether or not you see a blue circle surrounding your position. If you do see that, your GPS has failed at that time and the size of the circle is the estimated inaccuracy of the GPS. You need to be patient because blue circle comes and goes randomly.
2. Pay attetion to certain landmarks like bridges, overpasses and intersections. And compare that to your position on the map to see if you experience lags.
3. The navigation software snaps you to the wrong road nearby even though you didn't see the blue circle.
In my personally experience, all three showed up randomly. I have no problem getting a quick lock at all.
foxbat121 said:
Network assist is not a problem. There is no need to disable it.
Just take a test drive using Google Navigation. Ignore the fact that it always seems to be dead on your position (because all navigation software snap you to the nearst road). Instead, pay close attention to:
1. Whether or not you see a blue circle surrounding your position. If you do see that, your GPS has failed at that time and the size of the circle is the estimated inaccuracy of the GPS. You need to be patient because blue circle comes and goes randomly.
2. Pay attetion to certain landmarks like bridges, overpasses and intersections. And compare that to your position on the map to see if you experience lags.
3. The navigation software snaps you to the wrong road nearby even though you didn't see the blue circle.
In my personally experience, all three showed up randomly. I have no problem getting a quick lock at all.
Click to expand...
Click to collapse
This has been my experience too...and while Cog 2.1 has made it better, I still experience these same problems.
I changed the first post and hope to make this a community effort.
The problem seems to be position estimation. When you take a sharp turn, the GPS position will keep going "expecting" you to follow the same path. After a few seconds, the GPS position will slowly return back to your real position.
If we could just remove position estimation / interpolation, we might see improvement.
You can see what I am talking about in my post here:
http://forum.xda-developers.com/showpost.php?p=8295858&postcount=2
Thank you ShortFuse.
This is the most truly helpful GPS thread in a while. I hope we can get to the bottom of this soon.
Everyone needs to contribute to this thread!
Hi there.
Well, first of all, I am (hopefully) not insane. Second, I'm a network engineer for 20+ years, so my technical skills are not subject to any doubt. Third, I'm absolutely new to android, thus I don't exactly know the API and especially hardware interfaces.
OK.
I bought a Fire, axed the native shell, installed TWRP2 and CM7. Downloaded a nice ereader, a video player, and a local maps application, called Yandex Maps, I like it for instant and quite precise traffic info. Tapped the location button and found the crossfire within 30 meters around the actual location.
Then I drove to work and, while checking with traffic info, pressed "locate me" again. And the Maps has found me right in place.
"GPS is working" I said to myself.... and some days after, browsing this forum, found out that Fire HAS NO GPS SENSOR.
Need to say that I have the same IP network at home and at work (I'm the ISP in both places). And even if its location can be found via RIPE, it is declared to reside in my office. Not my home, which is 12km away.
Digging further, I installed Google Maps. This app refused to find my location. Tried Navitel - same result. But Yandex does its best - in an anonymous internet cafe (third place!) with free wifi it pinned me RIGHT on the building.
I googled for the radio chip of the kindle. According to ifixit, it's a hybrid with TI WL1271 inside. According to TI, WL1283, the chip that does have GPS in addition to wifi and BT, is pin-compatible with older WL1271 - so there *is* a small chance that WL1271 is replaced with 1283/81 in most recent devices.
That's the ONLY explanation I can believe in. Otherwise I'm totally lost. I even have posted the same issue to BT/GPS thread. Heard no answer there.
Your ideas?!
cu6apum said:
Hi there.
Well, first of all, I am (hopefully) not insane. Second, I'm a network engineer for 20+ years, so my technical skills are not subject to any doubt. Third, I'm absolutely new to android, thus I don't exactly know the API and especially hardware interfaces.
OK.
I bought a Fire, axed the native shell, installed TWRP2 and CM7. Downloaded a nice ereader, a video player, and a local maps application, called Yandex Maps, I like it for instant and quite precise traffic info. Tapped the location button and found the crossfire within 30 meters around the actual location.
Then I drove to work and, while checking with traffic info, pressed "locate me" again. And the Maps has found me right in place.
"GPS is working" I said to myself.... and some days after, browsing this forum, found out that Fire HAS NO GPS SENSOR.
Need to say that I have the same IP network at home and at work (I'm the ISP in both places). And even if its location can be found via RIPE, it is declared to reside in my office. Not my home, which is 12km away.
Digging further, I installed Google Maps. This app refused to find my location. Tried Navitel - same result. But Yandex does its best - in an anonymous internet cafe (third place!) with free wifi it pinned me RIGHT on the building.
I googled for the radio chip of the kindle. According to ifixit, it's a hybrid with TI WL1271 inside. According to TI, WL1283, the chip that does have GPS in addition to wifi and BT, is pin-compatible with older WL1271 - so there *is* a small chance that WL1271 is replaced with 1283/81 in most recent devices.
That's the ONLY explanation I can believe in. Otherwise I'm totally lost. I even have posted the same issue to BT/GPS thread. Heard no answer there.
Your ideas?!
Click to expand...
Click to collapse
Have you tried doing this with wifi turned off? Do you get the same results?
Just to clarify, you say your map app is showing you your current location without any wifi connection? i.e it updates as you drive?
From my own experience, apps like google maps can approximate your location based off your wifi. (I assume this is done because google collects wifi locations.)
Your assumptions that the kindle fire may have GPS could infact be correct. We know that the chipset does infact have BT even though there may never be working drivers for it.
Also, since amazon doesn't spec the KF for either BT or GPS the chips they get could be of lower quality. Since the only thing they need working is the wifi. This could mean the even if there is GPS or BT, there is no guarantee that they would even work. and if they did, they wouldn't work on everyone's KF.
airmaxx23 said:
Have you tried doing this with wifi turned off? Do you get the same results?
Click to expand...
Click to collapse
airmaxx23, unfortunately this is the only app that shows my location correctly, AND does not have offline map cache; even if I fill the cache manually, it requires internet connection to start. As of now, I cannot find a hacked version to try. Still looking for an alternative.
Sambena , no. Still no offline experience, see the post. Google can't locate, for the wifi at home does NOT have my location info.
Is there any way in CM7 to display exact hardware config without desoldering the device? As I suggest from above, the standard GPS API is unavailable (Google, Navitel) but Yandex is able to find some low-level interface (famous Russian coders!)
You could get into a shell and look at lspci > lspci.txt
You could also run dmesg > dmesg.txt& and then try to find your location via your maps app. Between that and a location, you should be able to see what's going on.
Sent from my PG86100 using XDA App
cu6apum said:
Hi there.
Well, first of all, I am (hopefully) not insane. Second, I'm a network engineer for 20+ years, so my technical skills are not subject to any doubt. Third, I'm absolutely new to android, thus I don't exactly know the API and especially hardware interfaces.
OK.
I bought a Fire, axed the native shell, installed TWRP2 and CM7. Downloaded a nice ereader, a video player, and a local maps application, called Yandex Maps, I like it for instant and quite precise traffic info. Tapped the location button and found the crossfire within 30 meters around the actual location.
Then I drove to work and, while checking with traffic info, pressed "locate me" again. And the Maps has found me right in place.
"GPS is working" I said to myself.... and some days after, browsing this forum, found out that Fire HAS NO GPS SENSOR.
Need to say that I have the same IP network at home and at work (I'm the ISP in both places). And even if its location can be found via RIPE, it is declared to reside in my office. Not my home, which is 12km away.
Digging further, I installed Google Maps. This app refused to find my location. Tried Navitel - same result. But Yandex does its best - in an anonymous internet cafe (third place!) with free wifi it pinned me RIGHT on the building.
I googled for the radio chip of the kindle. According to ifixit, it's a hybrid with TI WL1271 inside. According to TI, WL1283, the chip that does have GPS in addition to wifi and BT, is pin-compatible with older WL1271 - so there *is* a small chance that WL1271 is replaced with 1283/81 in most recent devices.
That's the ONLY explanation I can believe in. Otherwise I'm totally lost. I even have posted the same issue to BT/GPS thread. Heard no answer there.
Your ideas?!
Click to expand...
Click to collapse
I'm sorry to burst your beautiful little bubble here but the kfire doesn't have any GPS. What you are seeing is Google being a clever bigger. You see, when they rolled down nearly all the steers in North America, they took snapstops of the wifi, and coordinated with the GPS location. The reason you can transfer between your home network and your work with the same IP is because they used they use the Mac addresses of the networks in range, and cross reference it with their database to give you an approximation of where you are
tldr; android uses the Mac address of in range also to approximate where you are
I will have no disappointment even if my fire has no gps. I was buying the cheapest 7" tablet and I'm fine with it.
Please keep in mind that I'm almost an antipode to North America: Moscow Russia here. So neither Google, nor Amazon are aware of my IP, MAC, or even street address. I can imagine (although it's hardly probable) that Yandex is polling public wifi places for their locations, but none of mine are public!
The VERY only lifelike hypothesis that goes in groove with your idea is that Yandex cached the location of my iphone at home (the phone does have GPS and Yandex maps installed) and locates me based on the IP subnet. But: a) I never used the phone to locate the cafe I mentioned before. b) I cannot even imagine the cache size that Yandex has to have in this case.
I think this time you missed the goal. Any other thoughts?
It doesn't matter if Google knows your MAC or not when you have WiFi on it polls for acess points and bases your location off the signal strength of all of them.
You cracked the case!!!
Maybe you can teach me also, why it does NOT work here?!
afazel said:
You could get into a shell and look at lspci > lspci.txt
You could also run dmesg...
Click to expand...
Click to collapse
Indeed, thank you.
dmesg says it's a TI WL-1273, sadly... ven=0x104c, dev=0x9066. Well, at least it's proven to support BT and FM radio.
Kindle has no GPS, and Yandex is smart enough to cache locations even in NATted networks. Thanks for attention.
Starfire70 said:
It doesn't matter if Google knows your MAC or not when you have WiFi on it polls for acess points and bases your location off the signal strength of all of them.
Click to expand...
Click to collapse
It's not the Mac address of your device, it's the Mac address of the APs, they broadcast it with the probe signals. Its also more reliable to go on than the name of their AP. People change the name all the time, but who would change the Mac?
The GPS on my Nexus 7 is acting funky. I'm in Florida, and all of my apps are saying I'm in Vegas. Sometimes it'll show my correct location, but then it'll change back to saying I'm in Vegas. This is happening with Google maps, HD widgets, flixster, etc.. It's quite annoying. I haven't done anything to my N7 except unlock the bootloader, but it was doing it out of the box before that. What the French toast!? Anyone else having this happen? My GNex is fine with the same apps.
I tested mine to see if it would tell me where radio shack was. It worked and navigated good. It even told me the driving time to 3 of the nearest stores and traffic reports lol pretty crazy. I'd send it back for a replacement.
Sent from my Nexus 7 using xda app-developers app
Clienterror said:
I tested mine to see if it would tell me where radio shack was. It worked and navigated good. It even told me the driving time to 3 of the nearest stores and traffic reports lol pretty crazy. I'd send it back for a replacement.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Man, I just went to Sam's Club to exchange it. Got home, set it up, and my apps (google maps, HD widgets, google now) are showing Vegas still instead of my city in Florida. Ugh!!!
Goat1202 said:
Man, I just went to Sam's Club to exchange it. Got home, set it up, and my apps (google maps, HD widgets, google now) are showing Vegas still instead of my city in Florida. Ugh!!!
Click to expand...
Click to collapse
Are you sure you're not in Vegas?
skynoir said:
Are you sure you're not in Vegas?
Click to expand...
Click to collapse
Haha. Would be nice, but I'm not Could it be WiFi related? It seems that when I turn WiFi off, I shows my correct location in Florida and not Vegas. I don't know how/why the WiFi would interfere but not it's correct.
Goat1202 said:
Haha. Would be nice, but I'm not Could it be WiFi related? It seems that when I turn WiFi off, I shows my correct location in Florida and not Vegas. I don't know how/why the WiFi would interfere but not it's correct.
Click to expand...
Click to collapse
Did you check at the store or at home? Can you drive a few miles away and see if anything changes? Just a shot in a dark, but I work with address mapping online and sometimes for some reason the address for a certain location is totally wrong.
skynoir said:
Did you check at the store or at home? Can you drive a few miles away and see if anything changes? Just a shot in a dark, but I work with address mapping online and sometimes for some reason the address for a certain location is totally wrong.
Click to expand...
Click to collapse
With my original N7 and the new one that I exchanged for, I checked at home, and I haven't tried it anywhere besides at home. If I drive somewhere, I guess I would have to find a place with Wifi. I have a GNex, and it doesn't have the issue. It always shows the correct location. Not too long ago, I disconnected from WiFi on the N7 and it shows the correct location. So I don't know if WiFi is the culprit for some bizarre reason.
Download the map of your city and take a little drive. See if your GPS acts up away from. You can make sections of a map available offline in the Google maps menu.
Does this issue happen if you turn off wifi and enable GPS? Reason I ask is I remember Google Latitude acting super strange when I was using the wifi for it to determine my location when I was at my girlfriend's house. For a while it said I was in New York City, other times it said I was within PA but I was about 30 miles away. At one point it said I was in Africa somewhere.
All of the wireless towers (3G, 4G, etc) have ID's to them, so based on the ID that gets reported to the carrier is what dictates where on the map you are. That said, wireless access points aren't typically in the database to determine your location, so it uses some other sort of wacky way to determine your location, but like I said, Google Latitude was acting up. I remember hitting "improve my location" within the app and letting it run overnight to see if it could better determine my location. Oddly, I never had a chance to see if it fixed it, because the next morning our bid was accepted on a house so we ended up worrying about packing rather than did my phone work better. I just wanted to throw the above on the table just in case... turn off wifi... try GPS... see what happens.
JaSauders said:
Does this issue happen if you turn off wifi and enable GPS? Reason I ask is I remember Google Latitude acting super strange when I was using the wifi for it to determine my location when I was at my girlfriend's house. For a while it said I was in New York City, other times it said I was within PA but I was about 30 miles away. At one point it said I was in Africa somewhere.
All of the wireless towers (3G, 4G, etc) have ID's to them, so based on the ID that gets reported to the carrier is what dictates where on the map you are. That said, wireless access points aren't typically in the database to determine your location, so it uses some other sort of wacky way to determine your location, but like I said, Google Latitude was acting up. I remember hitting "improve my location" within the app and letting it run overnight to see if it could better determine my location. Oddly, I never had a chance to see if it fixed it, because the next morning our bid was accepted on a house so we ended up worrying about packing rather than did my phone work better. I just wanted to throw the above on the table just in case... turn off wifi... try GPS... see what happens.
Click to expand...
Click to collapse
Yeah, I mentioned somewhere in the thread that if I turn off WiFi, it seems to work fine. GPS is always on with it anyway. Either way, it should be able to pinpoint me. What's the point of the N7 if you can't keep WiFi on? Having both WiFi and GPS on should be able to find my location. I haven't really seen anyone else with this issue in trying to google it. It's just weird though because my GNex works perfect at home. And I can't get the N7 tablet to get the right location? Just odd.
Location on Google Voice Search
I'm in Lethbridge Alberta. ( Canada) Mine works fine in location and latitude... also Google Now works (when its giving me weather changes in the morning)
However, as soon as I ask Google Search "what's the weather like today", it tells me the weather for Washington and its driving me up the wall. Anybody else in Canada having the Same issues?
I believe there is a setting somewhere that has a check box "use Wi-Fi to determine my position". You need to find it and un-check the box. I would venture a guess that your internet service provider has a hub in Vegas and your outside IP address is registered through that facility.
Edit: turn Google Location Services OFF... Settings>>Location Services
Mine is showing Vegas also, oh I am in Vegas.
Sent from my Nexus 7 using xda app-developers app
It's probably due to the MAC address of the wireless router(s) your Nexus 7 is seeing. My parents live in Oregon and my step-mom works for a company based in San Diego. They sent her a remote access point to telecommute with and while I was visiting last year my Atrix would see me as being in Oregon when I was in view of a GPS satellite but otherwise, when it could only rely on WiFi for determining my location, it would see me in San Diego due to the remote access point having been in San Diego previously. So... don't worry about it! Your router/modem/whatever or your neighbor's may have been in Vegas previously at some other person's house.
Android Location Services periodically checks on your location using GPS, Cell-ID, and Wi-Fi to locate your device. When it does this, your Android device will send back publicly broadcast Wi-Fi access points' Service set identifier (SSID) and Media Access Control (MAC) data. The Google street car does this sort of thing too; collects Wi-Fi access points' data and MAC addresses, then associates them with their GPS location data.
What this means simply is that Google knows where you are when you are connected to an SSID they have previously collected location data on. For whatever reason, Google's data regarding your SSID is that it's location is somewhere in Vegas. I imagine this to be something that would remedy itself in time, though I'm not sure what the quick fix is. Maybe if you go in and out of range of your router with GPS on, the association will reset with the new location data? Are you set up to send anonymous location data back to Google?
There's nothing wrong with your GPS though.
Thanks everyone for the feedback. These last couple replies seem logical. When I turn off Google location services, my GPS works fine. What stinks is that, Google location services is required for Google Now. Has to be something with my Wifi router.
Hawkish.KMZ said:
I'm in Lethbridge Alberta. ( Canada) Mine works fine in location and latitude... also Google Now works (when its giving me weather changes in the morning)
However, as soon as I ask Google Search "what's the weather like today", it tells me the weather for Washington and its driving me up the wall. Anybody else in Canada having the Same issues?
Click to expand...
Click to collapse
Land Master said:
I believe there is a setting somewhere that has a check box "use Wi-Fi to determine my position". You need to find it and un-check the box. I would venture a guess that your internet service provider has a hub in Vegas and your outside IP address is registered through that facility.
Edit: turn Google Location Services OFF... Settings>>Location Services
Click to expand...
Click to collapse
I don't think this is the problem because I've tried, my phone (Rogers, originally registered in Calgary) as a hot spot, my house, my friends house, my work's wifi. All of these respond to any Non-location-specified operation to Washington. i.e. If i asked what time it was, it will give me washington's time. Same with weather, Washington weather. Im living in Canada. Is this a Canada specific problem maybe?
Hawkish.KMZ said:
I don't think this is the problem because I've tried, my phone (Rogers, originally registered in Calgary) as a hot spot, my house, my friends house, my work's wifi. All of these respond to any Non-location-specified operation to Washington. i.e. If i asked what time it was, it will give me washington's time. Same with weather, Washington weather. Im living in Canada. Is this a Canada specific problem maybe?
Click to expand...
Click to collapse
Nope, I'm having the same issue and I'm in the US. With "Google location services" and enabled, mine jumps back and forth between my actual location and the main floor of the "ny, ny" casino in Vegas. I have 3 other Android devices sitting near me that have never had an issue.
Caffinatedone said:
Nope, I'm having the same issue and I'm in the US. With "Google location services" and enabled, mine jumps back and forth between my actual location and the main floor of the "ny, ny" casino in Vegas. I have 3 other Android devices sitting near me that have never had an issue.
Click to expand...
Click to collapse
Yep, that's why I started this thread. Mine says I'm in the "NY,NY" casino in Vegas as well, and I'm in Florida.
Switchbitch said:
Android Location Services periodically checks on your location using GPS, Cell-ID, and Wi-Fi to locate your device. When it does this, your Android device will send back publicly broadcast Wi-Fi access points' Service set identifier (SSID) and Media Access Control (MAC) data. The Google street car does this sort of thing too; collects Wi-Fi access points' data and MAC addresses, then associates them with their GPS location data.
What this means simply is that Google knows where you are when you are connected to an SSID they have previously collected location data on. For whatever reason, Google's data regarding your SSID is that it's location is somewhere in Vegas. I imagine this to be something that would remedy itself in time, though I'm not sure what the quick fix is. Maybe if you go in and out of range of your router with GPS on, the association will reset with the new location data? Are you set up to send anonymous location data back to Google?
There's nothing wrong with your GPS though.
Click to expand...
Click to collapse
I guess I'm confused about this because I have both my N7 and GNex connected to my wireless router at home. I've had my GNex since it came out and have not had this issue with it. My router only has one SSID, right? And both of my devices are connected to it with only the N7 having the issue. And again it's only when "Google Location Services" is checked. It stinks to have to turn it off because "Google Now" requires it to be checked.
So when connected to WIFI my location gets messed up. The GPS works fine but the WIFI keeps putting my in Tokyo; thousands of miles away. It does this for all apps so maps will hop over to Tokyo and all weather apps and Google now all display tokyo stuff. No idea what is happening. I am running Paranoid Android. Could just be a glitch with the ROM.
Link200 said:
So when connected to WIFI my location gets messed up. The GPS works fine but the WIFI keeps putting my in Tokyo; thousands of miles away. It does this for all apps so maps will hop over to Tokyo and all weather apps and Google now all display tokyo stuff. No idea what is happening. I am running Paranoid Android. Could just be a glitch with the ROM.
Click to expand...
Click to collapse
Maybe they just have really strong wifi routers in Japan?
Now my location keeps jumping from my actual location and japan randomly. Kind of annoying.
Sent from my Nexus 7 using Tapatalk 2
slack04 said:
Maybe they just have really strong wifi routers in Japan?
Click to expand...
Click to collapse
heh
Hmm, I might try wiping caches, and restarting the router. Also maybe the router itself has some sort of location setting that may be set to Tokyo, not sure though
u need to open back case and bend the metal to get contact with case..
Has it always shown Tokyo?
Sent from my Nexus 7 using Tapatalk 2
jamerican413 said:
Has it always shown Tokyo?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Not till after I flashed paranoid android onto it. I'm in a different country now an we will see if it keep doing a it. Could just be a weird router glitch.
Sent from my Nexus 7 using Tapatalk 2
What is paranoid android? The song?
Sent from my Nexus 7 using Tapatalk 2
http://whatismyipaddress.com/ip-lookup, is also wrong for me
http://whatismyipaddress.com/update-location ,this adress might update it for you if google use the same databases
I have this issue as well with my Nexus 7 on CM10 and my HTC One XL on CM10. It doesn't happen on any other phone in the house only my two devices running CM10. I just can't figure out what is wrong with this. It keeps showing Lynwood, WA and I read another post that it has shown same location for two other users on a Galaxy Nexus.
I'm not so sure it's the router or ISP anymore. I have checked my ISP location online and it is correct, in fact even when I go to a website to check it on the Nexus it's correcty while my apps show Lynwood. Also, it only occurs on my CM10 devices and not my wifes ICS HTC Vivid or the Windows 7.5 phone in the house.
If I go to location settings on my devices and uncheck then recheck Google Location services then it finds correct location for awhile before going back to Lynwood, WA
Have a Gnex takju/makju with non-working wifi hotspot since 4.1.2 and still does not work on 4.2
Devices can connect to phone but wifi icon is greyed out and there is no data throughput
Rolled back to 4.1.1 and it works again, re-installed 4.2 and it does not work. Have opened issue with code.google.com
This is vital to me for work usage, but the failings of 4.1.1 on Gnex means that now I am downgrading firmware just to get hotspot working.
I was not going to commit to buy Nexus 4 immediately but if you guys can confirm that hotspot works for data throughput on the 4.2 that is installed on Nexus 4 I will order one tomorrow... I use android wifi only tabs (x2) for work on road so if anyone can test with laptop or android tabs I would be most grateful.
Thanks :fingers-crossed:
stinky73 said:
Have a Gnex takju/makju with non-working wifi hotspot since 4.1.2 and still does not work on 4.2
Devices can connect to phone but wifi icon is greyed out and there is no data throughput
Rolled back to 4.1.1 and it works again, re-installed 4.2 and it does not work. Have opened issue with code.google.com
This is vital to me for work usage, but the failings of 4.1.1 on Gnex means that now I am downgrading firmware just to get hotspot working.
I was not going to commit to buy Nexus 4 immediately but if you guys can confirm that hotspot works for data throughput on the 4.2 that is installed on Nexus 4 I will order one tomorrow... I use android wifi only tabs (x2) for work on road so if anyone can test with laptop or android tabs I would be most grateful.
Thanks :fingers-crossed:
Click to expand...
Click to collapse
I tethered my laptop to it almost right after getting the phone. Worked fine.
chinly43 said:
I tethered my laptop to it almost right after getting the phone. Worked fine.
Click to expand...
Click to collapse
Wifi or hardwired? Thanks
I have had no issues with the wifi hotspot functionality on my Galaxy Nexus in 4.1.2 or 4.2.
stinky73 said:
Wifi or hardwired? Thanks
Click to expand...
Click to collapse
Wifi - sorry, should've mentioned that right off the bat.
stinky73 said:
Great, thanks, and do you like the phone in general? (If you have a Gnex how does it compare?)
Click to expand...
Click to collapse
I don't have the Gnex - I'm coming from a T-mob G2 (Desire Z). Given the minimal RAM (512MB, 376 accessible to apps) and the fact that I was trying to run a 4.0.3-based rom, this has been a HUGE step up for me. I've unlocked the bootloader and rooted already, no issues there at all (well, not on the phone side - my laptop has ADB problems). Call quality is great, on-screen keyboard is nice though punctuation is difficult. I've been getting d/l speeds here in Seattle of 20ish Mbps consistently.
I'll mention this: I haven't wifi-tethered anything *but* my laptop yet. So, it worked (great) for that, but I can't speak to how well, say, a tablet would work.
chinly43 said:
I don't have the Gnex - I'm coming from a T-mob G2 (Desire Z). Given the minimal RAM (512MB, 376 accessible to apps) and the fact that I was trying to run a 4.0.3-based rom, this has been a HUGE step up for me. I've unlocked the bootloader and rooted already, no issues there at all (well, not on the phone side - my laptop has ADB problems). Call quality is great, on-screen keyboard is nice though punctuation is difficult. I've been getting d/l speeds here in Seattle of 20ish Mbps consistently.
I'll mention this: I haven't wifi-tethered anything *but* my laptop yet. So, it worked (great) for that, but I can't speak to how well, say, a tablet would work.
Click to expand...
Click to collapse
I think it a fair assumption to say that if it works for one it should work for all. My, and others' problems, appear to be everything under 4.1.2 and 4.2 - nothing works - for me = laptop, desktop, and tabs. Everything works with wifi tethering under 4.1.1.
Fantastic feedback on the phone, many thanks, shall order in the morning.
20Mps downloads??? Holy moly!! Here in France we eat a lot of snails....I think the ones that manage to escape the garlic and butter sauce take sanctuary in the mobile cell repeaters, where they brainwash the mobile phone network into emulating their speed.... 4-5 Mbps if we're lucky and the wind is in the right direction
Any other user experiences with WiFi hotspot on nexus 4 please?
Sent from my GT-P7510 using xda premium
stinky73 said:
Any other user experiences with WiFi hotspot on nexus 4 please?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
I've been having no issues tethering on WiFi either. I used it all day yesterday during Thanksgiving (grandparents don't have internet), with no issues. I was getting 19 Mbps here on HSPA+ on my 2012 MacBook Pro.
Wi-Fi hotspot works amazing. I use it on a daily basis to tether to my nexus 7 and sometimes laptop
Sent from my Nexus 4 using xda app-developers app
agtitan said:
Wi-Fi hotspot works amazing. I use it on a daily basis to tether to my nexus 7 and sometimes laptop
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Acuity said:
I've been having no issues tethering on WiFi either. I used it all day yesterday during Thanksgiving (grandparents don't have internet), with no issues. I was getting 19 Mbps here on HSPA+ on my 2012 MacBook Pro.
Click to expand...
Click to collapse
Many thanks, just what I wanted to hear :good:
chinly43 said:
I tethered my laptop to it almost right after getting the phone. Worked fine.
Click to expand...
Click to collapse
Acuity said:
I've been having no issues tethering on WiFi either. I used it all day yesterday during Thanksgiving (grandparents don't have internet), with no issues. I was getting 19 Mbps here on HSPA+ on my 2012 MacBook Pro.
Click to expand...
Click to collapse
agtitan said:
Wi-Fi hotspot works amazing. I use it on a daily basis to tether to my nexus 7 and sometimes laptop
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What app are you guys using to tether? I tried FoxFi (not rooted, yet) and it fails instantly every time I open the app.
I am also having Wifi tethering issues with N4. I can set it up and connect clients but I cannot get data through... I am going to a new network soon so will try again with that, if it still fails I will try a factory reset.
ThEGr33k said:
I am also having Wifi tethering issues with N4. I can set it up and connect clients but I cannot get data through... I am going to a new network soon so will try again with that, if it still fails I will try a factory reset.
Click to expand...
Click to collapse
It is network related as 4.2 "flags" the fact that you are using tethering to your supplier.... some subscriptions/networks allow you to use the phone and it's services as a hotspot included in your subscription, some not... mine (Orange France) does not and they want an extra 39 euros per month, yes 39 euros!!, to allow me to use the tethering functionality.
You can try this script that you run thro terminal (Android Terminal Emulator, for example) from the market
su -c "iptables -tnat -A natctrl_nat_POSTROUTING -s 192.168.0.0/16 -o rmnet0 -j MASQUERADE"
Copy and paste it all into terminal and hit enter... then start hotspot and see what happens. It often works like this...You might find that the string "rmnet0" is not good for you, it depends on the carrier, so you will have to try to change it....
You can find the string that you need to use to replace "rmnet0" by doing this
Stop the Wifi, go on internet using your data connection and look at your IP. To do this in adb, enter "netcfg". It will show you something like : vsnet0 UP 10.95.95.175/32 0x000010d1 00:00:00:
So, in this case you replace rmnet0 with vsnet0 - ok?
Give it a go and let us know how you get on..
A factory reset will do absolutely nothing!!
Thanks a Tonne Stinky!!! I probably wont need to do this fortunately, I'm going with a new network where tethering is completely legit in 1-2 days. I am glad you posted this as I was starting to wonder if it was something faulty with my phone, never realised it would just be greedy carriers (though given their track record this should have been the first place to check!!!).
:victory:
If for whatever reason I don't move over I will check back with this!
stinky73 said:
It is network related as 4.2 "flags" the fact that you are using tethering to your supplier.... some subscriptions/networks allow you to use the phone and it's services as a hotspot included in your subscription, some not... mine (Orange France) does not and they want an extra 39 euros per month, yes 39 euros!!, to allow me to use the tethering functionality.
You can try this script that you run thro terminal (Android Terminal Emulator, for example) from the market
su -c "iptables -tnat -A natctrl_nat_POSTROUTING -s 192.168.0.0/16 -o rmnet0 -j MASQUERADE"
Copy and paste it all into terminal and hit enter... then start hotspot and see what happens. It often works like this...You might find that the string "rmnet0" is not good for you, it depends on the carrier, so you will have to try to change it....
You can find the string that you need to use to replace "rmnet0" by doing this
Stop the Wifi, go on internet using your data connection and look at your IP. To do this in adb, enter "netcfg". It will show you something like : vsnet0 UP 10.95.95.175/32 0x000010d1 00:00:00:
So, in this case you replace rmnet0 with vsnet0 - ok?
Give it a go and let us know how you get on..
A factory reset will do absolutely nothing!!
Click to expand...
Click to collapse
Yep new carrier and tethering working a treat... Carrier blocking.
stinky73 said:
It is network related as 4.2 "flags" the fact that you are using tethering to your supplier.... some subscriptions/networks allow you to use the phone and it's services as a hotspot included in your subscription, some not... mine (Orange France) does not and they want an extra 39 euros per month, yes 39 euros!!, to allow me to use the tethering functionality.
You can try this script that you run thro terminal (Android Terminal Emulator, for example) from the market
su -c "iptables -tnat -A natctrl_nat_POSTROUTING -s 192.168.0.0/16 -o rmnet0 -j MASQUERADE"
Copy and paste it all into terminal and hit enter... then start hotspot and see what happens. It often works like this...You might find that the string "rmnet0" is not good for you, it depends on the carrier, so you will have to try to change it....
You can find the string that you need to use to replace "rmnet0" by doing this
Stop the Wifi, go on internet using your data connection and look at your IP. To do this in adb, enter "netcfg". It will show you something like : vsnet0 UP 10.95.95.175/32 0x000010d1 00:00:00:
So, in this case you replace rmnet0 with vsnet0 - ok?
Give it a go and let us know how you get on..
A factory reset will do absolutely nothing!!
Click to expand...
Click to collapse
Hi Stinky - I am in France too - using ZeroForfait (based on SFR network)
My SIM card in my wife's old Desire allows me to tether (so not an issue with the provider), but in my N4 this won't work.
I have been fighting with this all day, but no luck. I have tried a few different apps still nothing.
I tried your suggestion (although for me it was rmnet_usb0) - but still no luck.
For some reason it did work earlier (when I was trying a few different things and rebooting) using wifi or BT tether ... but now it is not working anymore.
When in tethered mode - I can ping each device from eachother - but no data flows....
I have seen some suggestions that Franco kernel might work .....
Looloup said:
Hi Stinky - I am in France too - using ZeroForfait (based on SFR network)
My SIM card in my wife's old Desire allows me to tether (so not an issue with the provider), but in my N4 this won't work.
I have been fighting with this all day, but no luck. I have tried a few different apps still nothing.
I tried your suggestion (although for me it was rmnet_usb0) - but still no luck.
For some reason it did work earlier (when I was trying a few different things and rebooting) using wifi or BT tether ... but now it is not working anymore.
When in tethered mode - I can ping each device from eachother - but no data flows....
I have seen some suggestions that Franco kernel might work .....
Click to expand...
Click to collapse
It's not in function of the sim card but the version of android.... I imagine the "wife's old Desire which allows you to tether" (aaah matrimony, you can't beat it :laugh is running an older version of android which does not flag tethering to SFR.
Try this one attached instead - remember it will not stick so if you reboot you must run terminal again and enter the commands again (maybe this was what happened to you earlier?)
stinky73 said:
It's not in function of the sim card but the version of android.... I imagine the "wife's old Desire which allows you to tether" (aaah matrimony, you can't beat it :laugh is running an older version of android which does not flag tethering to SFR.
Try this one attached instead - remember it will not stick so if you reboot you must run terminal again and enter the commands again (maybe this was what happened to you earlier?)
Click to expand...
Click to collapse
Hi again - realised that my last comment sounded slightly pervy ... oh well.
In any case, I tried your alternative - and I get the following error returned from the terminal
sh: sysctl: not found
... and tethering still not working
Looloup said:
Hi again - realised that my last comment sounded slightly pervy ... oh well.
In any case, I tried your alternative - and I get the following error returned from the terminal
sh: sysctl: not found
... and tethering still not working
Click to expand...
Click to collapse
Now tried a couple of different variations on your script, still no luck - and Franco Kernel no different
Exchanged mails with my carrier - they confirm that I should be able to share data