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?
Hi guys, i have a weird issue with this rom, i've been using it for like 4 days now, but lately i've been getting random reboots, this happens when the phone freezes up out random, it shows the battery icons with a ? mark and the phone responds to volumen up and down commands but thats it, also the screen and the capacitive softkeys stop working when this happens to, and when i press the power button it restarts its self, i've alrdy wipe data+dalvik+cache and nothing the device keeps on behaving the same, im about to just re-flash the rom, from my acer s200 experience, acer phones tend to have random isolated issues to specific devices/hardware, and mostly these issues are hard to reproduce, anyways i might re-flash the oem rom today, il see if this fixes it or if its just another issue that the rom it self has, as its a beta release, any suggestions will be great appreciated.
edit: i have reflashed 10000 times it still does it, my last option would be to flash 1.6 but meh i like 2.1 better =]
hic, can u help me up rom acer liquid from 1.6 to 2.1 thanks .
It's most likely the ROM, but, still could be the kernel. I have been using the rooted kernel only, nothing else. Actually some lowmemkiller settings. I was not able to test if removing the threshold settings (I forget what the other thing was too) before I sold Liquid.
I can report bad use of the digital compass, when in navigation with google maps or (f.e.) copilot 8.
Gps receiver says that i'm going forward, but digital compass says that i'm going backward.
Stupid compass
Yes, I have the same issue in Navigation. The compass is fine in Google maps app though
So, i was having some issues with the earphone i had bought recently, but having a few problems with the same brand sometimes earlier (microsoft really put up a really interesting choice with the low price and really good bass and sound quality for its pricing, but damn, those things had caused me two replacements in earlier models) i was considering taking it to the warranty and getting a new one, fine.
Then i got the moto earphone (had never used it, was in that plastic thingy yet) to get me through the day and i put the ms one in the bag, but when i started walking, the same problems appeared. The volume would get lower, sound getting distorted, and the song started to cut to the point it would recognize as if the headphone has been unplugged and i have to start the music again. i'm no expert but i think we've got some issues here son
I went to master google in search for answers and i've found that people have been having these kinds of issues since the first generation moto g, some even got a replacement and the jack would still come faulty, there were a major "consent" that the fault was the pocket lint inside, and cleaning it would solve the problem, but my phone doesn't have even two goddamn weeks, it didn't even had time to get dirty. (and i tried it cleaning, only a lil hair came out) I am currently listening to music, and it's perfect, when the phone stays still. If i start moving it around or mess with the connector, the issues come back again.
Does someone had this problem here too? found some solution besides the pocket lint thing? i didn't found any post here on xda related to that, and i really don't wanna send it ro warranty 'cause i need it really bad for my work, and i know it's gonna take some time in there, the problem can even come back...
Please, show me a light.
I have a problem where moving the headphone jack a small amount would stop music playback its so annoying. I mostly use Bluetooth headphones though.
george241312 said:
I have a problem where moving the headphone jack a small amount would stop music playback its so annoying. I mostly use Bluetooth headphones though.
Click to expand...
Click to collapse
Moving it also distorts the sound to the point it stops. Normally this happens with detective earphones, but the jack is new to me.
I'm sure it's the jack, I just got new headphones too. What you can do is expand that contact strip in the jack inward, hence better contact? I haven't done this yet though
bestofrhcp said:
I'm sure it's the jack, I just got new headphones too. What you can do is expand that contact strip in the jack inward, hence better contact? I haven't done this yet though
Click to expand...
Click to collapse
yea, it is the jack indeed... are you facing this problem too?
i tried pulling it out a bit, but no results. Some random "solutions in the internet tell to put something behing that first metal contact strip... it that so?
So I kinda solved the problem these days... I bought a tpu case, and it has stopped. I guess that the phone is too slim, and it keeps banging in the pocket, making the jack loose and stopping the song. Now the phone is kinda bulky, fits right in the pocket, I can even run with it and the sound is still perfect. Sad that I gotta use this case, makes the phone Hella ugly, but yeah, I solved the problem
If anyone is facing it, try this, might work for you too.
Fixed my problem
I'd just like to add that I also suffered from this same issue (to the letter, volume decrease, distortion and all). It happened once a few weeks in but now, a few months later, it was happening so often that I had to give up using headphones.
Well, here's the thing: I contact Motorola and they give me the old crap about rebooting in safe mode and testing, or doing a factory reset.
As I KNOW this is a hardware issue, I just go ahead and reinstall the factory image (I was previously rooted) planning to send it in for repair/replacement: low and behold: it's fixed. So installing the original firmware and going through the setup (but choosing not to reinstall all my apps -new device option) fixed the problem. I have no idea how this can be. Maybe an app made the phone react too much to slight disturbances in the connection? When I have time, I'll be restoring my backup to see if the problem comes back, and uninstall apps one by one (starting with the xposed modules and other root apps).
I've been using the headphones a lot in the past 5 days with absolutely no issues.
tl:dr OP's exact problem, what seemed like a hardware fault, was fixed by a factory reset.
bv90andy said:
I'd just like to add that I also suffered from this same issue (to the letter, volume decrease, distortion and all). It happened once a few weeks in but now, a few months later, it was happening so often that I had to give up using headphones.
Well, here's the thing: I contact Motorola and they give me the old crap about rebooting in safe mode and testing, or doing a factory reset.
As I KNOW this is a hardware issue, I just go ahead and reinstall the factory image (I was previously rooted) planning to send it in for repair/replacement: low and behold: it's fixed. So installing the original firmware and going through the setup (but choosing not to reinstall all my apps -new device option) fixed the problem. I have no idea how this can be. Maybe an app made the phone react too much to slight disturbances in the connection? When I have time, I'll be restoring my backup to see if the problem comes back, and uninstall apps one by one (starting with the xposed modules and other root apps).
I've been using the headphones a lot in the past 5 days with absolutely no issues.
tl:dr OP's exact problem, what seemed like a hardware fault, was fixed by a factory reset.
Click to expand...
Click to collapse
Now that was unexpected lol. Anyways, thanks for the reply, i've seen much of this kinds of problems on the internet, but none of it came to a conclusion, the posts die after sometime. I hope someone finds the answer in your reply.
So, i bricked my phone sometime ago and installed the factory image. i've been using the tpu case since it came, as i stated before, it has solved my problems (i think mainly because the phone get bulkier, fits into the jeans pocket and stop moving, so the jack isn't affected by any kind of movement and it works perfectly), but after you said that i recalled, there was one day when i forgot the case at home, and unaware of that i went working with the headphone and it worked perfectly, i just noticed i had forgot the case in my way home. I'll do some further testing without the case, but your solution might just have hit the right spot.
guile50 said:
Now that was unexpected lol. Anyways, thanks for the reply, i've seen much of this kinds of problems on the internet, but none of it came to a conclusion, the posts die after sometime. I hope someone finds the answer in your reply.
So, i bricked my phone sometime ago and installed the factory image. i've been using the tpu case since it came, as i stated before, it has solved my problems (i think mainly because the phone get bulkier, fits into the jeans pocket and stop moving, so the jack isn't affected by any kind of movement and it works perfectly), but after you said that i recalled, there was one day when i forgot the case at home, and unaware of that i went working with the headphone and it worked perfectly, i just noticed i had forgot the case in my way home. I'll do some further testing without the case, but your solution might just have hit the right spot.
Click to expand...
Click to collapse
Did you, by any chance, have GravityBox installed on your phone when it was playing up? Also/or, where you using an unmodified ROM, as that's what I'm using usually (deodexed but stock) I've just restored my backup (that's rooted and has a few xposed modules on) and sure enough first time I touch the jack with music playing, it plays up (this time it triggered the voice command, which it did do some times). So I think to start by disabling GravityBox as that modifies a lot of stuff... Reboot, and the damn thing seems to work perfectly, I'm tugging and pulling at the jack right now and it's working perfectly.
I find it a bit too much to believe, and I don't want to lose GravityBox as that's a big reason I root.
One explanation I can come up with is that Motorola saw there was a problem and they fixed it in software, and installing AOSP or GravityBox that changes system files, gets rid of that software "fix".
bv90andy said:
Did you, by any chance, have GravityBox installed on your phone when it was playing up? Also/or, where you using an unmodified ROM, as that's what I'm using usually (deodexed but stock) I've just restored my backup (that's rooted and has a few xposed modules on) and sure enough first time I touch the jack with music playing, it plays up (this time it triggered the voice command, which it did do some times). So I think to start by disabling GravityBox as that modifies a lot of stuff... Reboot, and the damn thing seems to work perfectly, I'm tugging and pulling at the jack right now and it's working perfectly.
I find it a bit too much to believe, and I don't want to lose GravityBox as that's a big reason I root.
One explanation I can come up with is that Motorola saw there was a problem and they fixed it in software, and installing AOSP or GravityBox that changes system files, gets rid of that software "fix".
Click to expand...
Click to collapse
Well, try to trigger the problem a couple of times with gravity box installed. I don't have it, installed xposed once and had major lag, stuttering and FC problems, then i took the ting off. Didn't test the jack thing, but i've never been a hard xposed user.
I really think my problem is hardware-related, but tonight i'll head home without the case and report back here.
If I am on a stock Moto ROM, I have the problem. When I moved to AOSP/CM based ROM's, I can manipulate my headphones without causing it to stop.. I think maybe the stock kernel is a bit too sensitive and stops it with just a little bit of disconnection vs a more lax implementation in AOSP/CM...
So I've ran my tests: climbed stairs, climbed down stairs, run a Lil bit, shake my hips (they don't lie) and messed around my pocket: no sign of Jack problems. I guess that flashing stock firmware again did the job, as you have stated earlier. I'm going to stop using the case and go jogging, or going more often to work listening to music without it, but after today field tests, I'm sure the issue is gone.
guile50 said:
Well, try to trigger the problem a couple of times with gravity box installed. I don't have it, installed xposed once and had major lag, stuttering and FC problems, then i took the ting off. Didn't test the jack thing, but i've never been a hard xposed user.
I really think my problem is hardware-related, but tonight i'll head home without the case and report back here.
Click to expand...
Click to collapse
Just an update: I give up. I've tried multiple things, including almost bricking my device. I cannot find something definite at all. Installing a clean factory image (or a rom that has not been changed much) will get rid of the problem, even with root. However after restoring my TitaniumBackup of about 140 apps, the problem came back for a while. I noticed it after enabling MotoVoice, so I disabled moto voice and it disappeared, but then re-enabling moto voice didn't make the problem come back... And that is why I give up. I've ordered a pair of Bluetooth headphones.
I think that flashing the stock firmware again is the ultimate solution to solve the problem. After some tests I really couldn't trigger it again, so I guess that's the end of it
The problem is that the issue is so random I can't seem to find a proper way to trigger or to say it is 100% solved. I've read about it happening since the first generation moto g, seems like a hardware issue, but...
My headphone jack wont work properly when i insert the headphones into the jack completely but it works fine when i pull out a lil of the pin of headphones out of the headphone jack whats the deal its too annoying
Moto x 2013 verizon