Related
got a new phone from tmo today...rooted it, flashed jf1.5, flashed new spl, moved apps and dalvik cache to sd...smooth sailing...redownloaded all my apps from sd and from market, still good...went to google maps and it cant find my location using gps...cellular location still good though...and yes, I did enable gps in the settings...so I reflashed did everything as before and still no go...did I just get a defective G1 or is there something I can fix? Thanks for any help guys!
BTW, my old phone, before it got wet, worked great with all the same settings and same ROM...
GPS can be iffy. Some locations are just prone to bad GPS acquisition. I went to visit my parents last night, real hard to get a fix in their backyard, but eventually it did. Tried at a friend's apartment building, anywhere NEAR it, its impossible to get a fix. Probably something to do with signal reflection. Other times, it'll lock on within a couple of seconds.
Your radio and firmware version are also important. The newer versions seem to lock on to GPS a lot easier. You say that you have jf1.5 -- the latest is 1.51, and can you confirm that you have the latest (official, not the hacked phone killer) radio installed?
lbcoder said:
GPS can be iffy. Some locations are just prone to bad GPS acquisition. I went to visit my parents last night, real hard to get a fix in their backyard, but eventually it did. Tried at a friend's apartment building, anywhere NEAR it, its impossible to get a fix. Probably something to do with signal reflection. Other times, it'll lock on within a couple of seconds.
Your radio and firmware version are also important. The newer versions seem to lock on to GPS a lot easier. You say that you have jf1.5 -- the latest is 1.51, and can you confirm that you have the latest (official, not the hacked phone killer) radio installed?
Click to expand...
Click to collapse
I do have jf1.51...and the latest radio...and the latest SPL...my old phone didnt have this problem...I kept all my settings(thank you MYBACKUP PRO) so essentially everything is the same, except for the phone...and the same spots where I used to be able to get a fix with my gps(even indoors) I dont get anything....must be the phone...and if it is...any fixes you guys know about?
just got off the phone with a tmo rep re: my gps issue....I explained to him that I used to be able to get a gps lock on my old phone in seconds indoors and out but not with this replacement phone and he says to me well I have a g1 here with me and Im not able to get a gps lock...I told him that it's probably because he's inside a building with lots of electrical interference and other buildings blocking the reception...i also told him that I was able to use TeleNav with my old phone along with other apps that required gps...and he suggests to me to call TeleNav because it might be a problem with their app...oy...he also suggests to me to go to a tmo store where they have demo phones and we could compare gps signals....oy...I also told him that that I used google maps as a navigation tool before but not anymore since I cant get a gps lock anywhere...and he just tells me to try the tmo store...oy...i might need to unroot this phone and return it to tmo, I guess....
I'm on my third G1. The first one died to some strange graphics issue where the screen would go completely pixilated and wacky on me. I think the graphics processor was overheating. On the second one the touch screen died about the same time the speaker in started buzzing during calls.
Luckly because TMobile extends your warranty 90 days every time you get a new phone, I've only had to pay for shipping. I got the latest one, and immediately installed Cyanogen 4.2.5 on it. No problems. Then I followed Michael Mayhew's instructions for the maps update to get Navigation.
I can't get the GPS to work at all. I've since tried going back to RC29, or the base Cyanogen 4.2.5 without the maps hack. I've tried other GPS applications such as the Chartcross GPSTest. I can't get a read at all on any of them. I don't know if it was working before the updates, because I never tried to use maps before I installed the mod.
So I'm wondering somehow a radio update was applied that broke this phone, or if there is anything I can do to change the gps drivers around. Anyone with similar GPS failure issues?
I don't really want to return this one as I've only had it one day!
Yes, similar issues. No solution thus far. I also did not test GPS before flashing. OOPS?!? And now it no longer works, but I can't tell if that was the case to begin with.
I followed the same procedure (CM 4.2.5, Navigation mod), and had the same result--broken GPS. "My Location" not working, "Searching for GPS" forever, etc.
So two possibilities I can see:
1) hardware problem w/GPS
2) one or a combination of CM 4.2.5 + Nav = broken GPS
I have seen a few people on these boards say their GPS doesn't work all of a sudden. In fact, there are stock Droid owners with issues.
Can anybody chime in?
Hmmm
So for about 10 minutes on Friday it started working again. Totally random, I have no idea why. I was at a party and decided to see if it was working. All of a sudden I had signal (using GPSTest) and google maps found my location.
I've since tried it several times, rebooting, and doing a bunch of other stuff. I can't get it working again. Total fluke! So frustrating!
Well now the new version of google maps is in the market. I've successfully installed that one but still no GPS.
Im having the same issue on my G1 right now. Sorry for the Zombie thread, but did this ever get resolved?
I've had the gps fail on my phone and others I know have also. The g1 seems to have issues with the gps antenna strip breaking internally so one minute you'll have reception, the next.. nothing. Only solution is to find a new antenna strip and replace it (good luck!)
Aside from possible hardware failures, the GPS units on these phones tend to be very weak. Sometimes it *IS* impossible to get a strong enough signal to lock on, even when out in the open if there is something nearby that can reflect the GPS signals.
However note that these are AGPS devices, which means that with a cell connection and a data connection, and given that google knows the coordinates of the cell tower you are connected to, it is able to load assistance data (almanac + accurate time synchronization via NTP), and this will *GREATLY* improve your chances of getting a good lock and greatly reduce the time it takes.
Woil said:
I'm on my third G1. The first one died to some strange graphics issue where the screen would go completely pixilated and wacky on me. I think the graphics processor was overheating. On the second one the touch screen died about the same time the speaker in started buzzing during calls.
Click to expand...
Click to collapse
I doubt that it was the GPU overheating. Your phone would burn your hand if it got that hot.
The in-call buzzing could be corrected by shifting the screen a little bit while it is happening. It is related to GSM interference with the speaker. The speaker is literally playing the radio waves emitted by the phone. The touchscreen issue was probably a broken cable... also related to moving the screen.
Luckly because TMobile extends your warranty 90 days every time you get a new phone, I've only had to pay for shipping. I got the latest one, and immediately installed Cyanogen 4.2.5 on it. No problems. Then I followed Michael Mayhew's instructions for the maps update to get Navigation.
I can't get the GPS to work at all. I've since tried going back to RC29, or the base Cyanogen 4.2.5 without the maps hack. I've tried other GPS applications such as the Chartcross GPSTest. I can't get a read at all on any of them. I don't know if it was working before the updates, because I never tried to use maps before I installed the mod.
Click to expand...
Click to collapse
Note that you are getting refurbs....
So I'm wondering somehow a radio update was applied that broke this phone, or if there is anything I can do to change the gps drivers around. Anyone with similar GPS failure issues?
Click to expand...
Click to collapse
What radio version are you running?
I've also had no luck getting a GPS signal ever since I installed hacked navigation... I wonder if that's the problem? Has anyone tried removing the hacked navigation, to see if that solves the problem?
BTW, the problem started on CM 4.1 with EBI0 radio (2.22.19.26I), and still persists with CM 5.0.7... Has anyone tried upgrading their radio to 2.22.23.02? How about the folks that have gone back to the Updated Rogers EBI1 Radio (3.22.26.17)?
I have been having the "searching for gps" problem as long as I can remember (although I just got this phone a month or two ago)....I remember trying to install the hacked navigation or something so maybe that messed it up?...this phone was never opened, and I would hate to have to open it up to see if it is a hardware issue because I may not put it back as it was. IDK what to do, I even started a thread about it and tried every solution I could find and nothing worked for me....
I wish someone could chime in here with some insight...but it is also nice to hear others with this issue and their advice/ideas also...
Has anyone tried un-rooting and returning the phone back to complete stock and wiping everything ? has that worked for anyone?
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
[email protected] said:
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
Click to expand...
Click to collapse
If you are bootloader unlocked, you can fastboot flash any radio.img you want. If you are not bootloader unlocked, no you can't. The radio.img is universal btw, not specific to a carrier.
Edit: the guide below will help you unlock the bootloader and learn fastboot if you are unfamiliar.
http://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Nexus 5X using Tapatalk
Thanks. I will do that. I appreciate the help.
Is this a problem for other Verizon users too? If so, I just won't upgrade the radio firmware on mine either.
I would highly suspect that the problem is for everybody on Verizon especially since I replaced my device and did all this SIM card changes and things. It is very unnoticeable in that the only time you experience it or see it is if you are making a call on the new nougat radio 03.72, you will see the LTE icon disappear as soon as you make your call, regardless of whether you are on an 'HD call' or not. If you are on the older radio 03.61 that is on marshmallow, then you never experience that problem, ever, ever. Everything is perfect with that "radio." I've done a lot of testing on it, as I said, up to replacing my device, all to no avail. unless using 03.61 which is again, perfect. I wouldn't change if you can avoid it. If you do get the nougat radio though (03.72), it's a nuisance because after the majority of reboots overall, you will come up with everything normal-'looking' with the LTE icon there but when trying to make a call it will disappear and you'll have an exclamation point there until you hang up from the call and LTE comes right back. (unless you're on wifi off course in which case none of this apples). The solution if you find yourself with the 03.72 nougat radio with this happening, is to toggle airplane mode and then you're good to go until the next time you have to reboot. I always check afterwards by calling voicemail to make sure the LTE icon stays while on the call. It will disappear immediately.
I'm going to assume there is some sort of an "initial-boot-handshake" that's not taking place correctly, but DOES communicate correctly coming out of airplane mode when the device is already booted.
Regards
Edit: This may be a regional VZW issue and not a phone or baseband issue.
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
tech_head
Everything was working fine on mine with the marshmallow radio. I didn't have an issue until I updated to nougat.
Hearing what happened with yours makes me think that it's a regional Verizon thing. Hopefully they will fix soon. I'm not holding my breath because it's been about a month here in Central Kentucky
I'm glad yours is working now man.
Cheers!
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
heffe2001 said:
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
Click to expand...
Click to collapse
Best of luck. Let us know how it goes if you get the chance. Thanks!
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
bjoostema said:
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
Click to expand...
Click to collapse
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
**
As mentioned earlier in the thread, the radio is independent of the OS version, so why not take 1 or 2 minutes and flash an earlier radio? There is a radio / modem repository thread on XDA with all versions you can just grab and try out. Literally takes less than a minute and if you don't like the results, then just flash it right back. I use Fastboot, but TWRP, FF, NRT, etc. all work equally well. You may also post what you find under "Phone Settings" when typing " *#*#4636#*#* " into the dialer. Report back on your findings.
Here are the screenshot links for my phone settings.
Thanks
OP
http://forum.xda-developers.com/attachment.php?attachmentid=3882483&stc=1&d=1474502181
http://forum.xda-developers.com/attachment.php?attachmentid=3882482&stc=1&d=1474502181
tech_head said:
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
Click to expand...
Click to collapse
Are You running stock nougat now. If so, what is your simultaneous voice and data status with respect to my post.
Thanks
OP
[email protected] said:
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
Click to expand...
Click to collapse
No problem bud! I haven't flashed another radio yet either. I will report back after I test a few more things.
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
chaoticyeshua said:
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
Click to expand...
Click to collapse
It is still kind of up in the air. What I do know is that there is a software incompatibility somewhere within nougat here in Lexington, KY, at least. I assume it's the radio software but I'm not certain. I'm not bootloader unlocked at this point so I haven't yet tried to flash marshmallow radio on to stock nougat. I will probably try this in a few days when I have the time to deal with the factory reset it involves. Please refer back to the original post for questions about my reasoning.
It's quite interesting, the problem, as everything with stock nougat - voice and data-wise, works just like marshmallow after I toggle airplane mode after reboot. With marshmallow, it just worked. Very weird. But given I can just toggle airplane mode 1 time for every time I boot, it's just a slight nuisance. Once I toggle airplane mode, everything is good just like marshmallow, as if nothing was ever wrong. It could be something about the boot sequence. It's very interesting. I'm open to ideas at this point.
Thanks.
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
spjetrovic said:
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I appreciate your input. It doesn't sound like our issues are quite the same. I'm not sure though.
What is it that Verizon did for you. That may be the answer to my problems.
Thanks. Best Regsrds.
GPS on my bootloader unlocked A2017G cannot get a fix for some reason. I last had working GPS on the November 12 release of CM13, lost it when I flashed the November 23 release (to get cam to work) and today finally decided to flash DrakenFXs B06 on top to see whether that might fix it (some indications of it in the CM13 thread).
However also on B06, much as with CM13, GPS Status just sits there telling me it sees somewhere from 18 to 27 satellites (so more than enough for a fix) but never actually gets a fix. Does my phone have a hardware issue or is there anything I can try (I may try to flash stock recovery if I can find it somewhere to go to B08 as I can get the OTA on my phone)?
Update: Flashing the full ZTE B06 update and then going to B08 did not help, either (and I now get a BL unlocked flash screen, I really hate those).
I still think it´s weird that GPS status says it can see that many satellites but never gets a fix out of it? Other radios work, so I don´t think there is something wrong with the antenna?
I guess unless someone has a good idea, I will send it back to Amazon.
If I can get a refund I think I will go for the OP3T instead (or bite the bullet and get a Pixel XL).
Maybe I am just expecting too much by testing indoors, outdoors it did work in seconds...
Yesterday I finally went from locked rooted B03 to unlocked rooted B08 and since then I notice that indoor GPS locks take much more time. Checking the GPS settings, I noticed that the Qualcomm IZat location service now only has an 'Agree' and 'Disagree' option when selecting the service. In B03 it was possible to switch it on and off with a checkbox. When either selecting Agree or Disagree, the box disappears and there is no indicator whatsoever showing whether IZat is actually turned on or off.
On B03 switching this on massively improved the GPS lock time indoors. Now, I do not really notice any difference whether I agree or not, indoor GPS lock in general takes a lot more time.
Anyone else?
New X Compact, and out of the box has had a GPS problem. It came loaded with Nougat, and I updated ota each version one-by-one to the latest Oreo 118, then unlocked bl, and flashed Sailfish, and the problem is the same on all.
What it is, is that the GPS signal will get a fix on-and-off after every few minutes, but won't hold steady. Using SatStat app on Android, I saw that the effect was the same with GPS and with network location.
Using a GPS info app, I see that when there is a fix, I get a read on latitude and longitude and altitude, but never anything for speed or direction. Seems like the fix is so brief that there is not a chance to measure it.
It seems obviously a hardware issue, being consistent over many software states, but the hardware is obviously working, so not sure... I would wonder if it was an issue with the carrier, but I used the same sim with the same account on my previous phone and it was fine.
Any ideas?
Thanks