So today, my sister was driving to Santa Barbara while using the Waze app on my phone and about halfway thru the trip, the entire system started lagging really badly. Screen glitches would often occur and it would take a long time for me to swipe down the notification bar. However, when we arrived at our destination, everything appeared and worked as normal again. The phone was on a dock placed on the windshield. Help?
Related
I just bought a used G2 today for a ridiculously good price. The phone is in absolute mint condition, however I have one small issue.
I am unable to swipe. Not swype, as in the texting app. I can't smoothly switch home screens because as soon as my finger leaves the screen during a swiping motion, any movement on the display immediately halts in it's current position. I constantly get stuck in between home screens, and when trying to navigate vertical lists it's near impossible because there's no fluidity and the list stops literally as soon as the screen has no contact. Also, while trying to navigate vertical lists, every once in a while the screen position will 'jump' back to where it just was as you attempt to scroll down further, thus causing a piece of screen that just won't go away for a moment. One more related issue is the fact that when I try to tap things it will act as if I'm doing a long-press. For example: sometimes hitting the app drawer button will bring up the long-press options, clicking an app from the open drawer will move icon like you're about to place on home screen, etc. This is all very annoying.
If this could be fixed then the phone would be perfect. It was like this when I first got it with the stock 2.2 rom on it. I proceeded to wipe and root the phone, install clockwork, and get the latest stable CM7 on it. Please, somebody help
Not to offend, but there's probably a reason it was so cheap and you may have found it.
This may not be the answer you're looking for but I had an issue just like this not long ago.
I dropped my phone in a parking garage, it landed face down. The EXACT issue you're describing, started at this moment. I found that some "persuasive" force, IE slamming the phone on a counter, or, a "twisting" action on phone helped...
I know, being so abusive to a $500 phone that I haven't even paid off yet doesn't seem like the smartest idea, but I do have insurance.
Sorry to bump an old thread, but I'm having the same problem. I dont want to go through the warranty process b/c I need to have my phone for the next few weeks. If any dev can help me solve this problem I would be very appreciative. Thank you.
Check the connection of the ribbon cable.
Could have been dropped and knocked loose.
Sent from my HTC Vision using XDA Premium App
I have my phone rooted stock but this problem has been around since before I did that. It seems an update to Google Maps changed something a while back and it is really starting to drive me crazy.
Scenario: I am driving, using navigation, and listening to podcasts in BeyondPod. I switch from Navigation to BeyondPod to change something and when I switch back to navigation it's as if it forgot everything and has to find the route all over again. It goes through the "Getting Driving Directions" thing and this is very annoying if I'm in an area where there is weak cell signal and it can sit there for over a minute or two.
This did not used to happen. It just ran in the background and I could switch to and from without it having to reload every single time.
Has anyone else experienced this?
If I try to navigate from the Zenwatch, the phone brings up google navigate even if the phone is sleeping. I would think that might be an issue in a pocket, but that's not the biggest issue.
The destination seems to get set correctly but neither the phone or the watch continues to navigate. They both seem to lock up.
Subsequently any other Nav app (I hope Waze gets Wear support soon) is unable to navigate as they are unable to get GPS lock. Looking at other GPS helper apps shows zero sats in range. Stopping/Restarting location services doesn't solve the problem. Only resetting the phone does.
Maybe it's just me. Sprint HTC One Max, stock. Anybody else?
I noticed this the other day when I was testing out navigation for fun. Once I took my phone out of my pocket, it seemed like it was able to get a lock again and things went more smoothly. I know gps can be a bit sensitive sometimes and maybe having it right next to your leg like that blocks the signal?
When the problem (GPS lockup) manifests there is nothing that will get it going other than a phone reset. I normally have my phone in a holder high on my dash where gets good reception, but when it gets in that state, not even one satellite shows a hint of a signal. Today I even made sure to stand outside holding my phone up in clear sky just to be sure.
Even if I don't access nav Google maps or Micro Maps from the watch it still locks up at some unknown point. I normally keep GPS on all of the time and have a number of apps that store locations from time-to-time. When I get in my car, Waze automatically starts but I can't get any sat signals until I reset my phone.
I'm experimenting with a theory that another member brought up in a different thread that there may be a connection with using a watch face that also includes weather and the number of GPS requests it makes. I've changed to the basic face that is in all of the marketing photos and continuing to test. I guess my next step will be to leave the watch at home :crying: to make sure that something wonky hasn't happened with the phone itself.
Are there any other frequent GPS users out there that can confirm or haven't experienced the problem? It doesn't seem to matter if you use the nav functionality on the watch.
The updates this morning seem to have fixed the problem.
Having issues with waze app and GPS. I've always had GPS issues with all of the Note series, so this doesn't surprise me. But this time around it seems like waze is the only one acting oddly. Specifically when I'm on a guided route waze intermittently sees me in a different area, most commonly when I'm on the highway it will see me on a side street running parallel to the highway. So then it thinks I'm off course and routes me back onto the highway or another direction, but I'm still on the highway. Sometimes I think it even sees me traveling a different direction, many times I'll be on the highway and it will want me to do 2 u-turns, changing directions twice but ending up going the same way as before. I also see the arrow icon representing my car on the map will constantly turn as if waze can't tell which direction I'm traveling.
My first thought is faulty GPS. I've ran Google Maps and it seems pretty solid, with none of those errors, but I'll have to test some more. Just wanted to see if anyone else got this? I may switch back to an older APK and try that as well.
No problems here. I noticed the 7's gps is way faster than my note 4 too. It finds my location on a second. My note 4 would take 5 to 10 seconds to lock in
I am having the same issue with Waze on my Note 7. It thinks i have turned onto a side road so it trys to redirect me to the the road im acually on. Its seems to think im about 30 to 50 feet to the right on the screen no matter what direction on the compass i am going.
Sent from my SM-N930P using Tapatalk
I've been having an issue when I'm stopped at the light, and the screen will start to spin around. It's like Waze forgot which way I was going so turns me around & recalculates the route...repeat.
Improvement over my Note 3 which regularly couldn't find a GPS signal or lost it in the middle of driving somewhere.
Were issue
I have been having issues also bit but only with the voice guidance. I get hazard alerts but that's it. Any thoughts on this?
waze always seemed to place me about 50 feet to the right of the road. It spent a lot of time recalculating on/off ramps when it didn't think I was driving through corn fields. I figured it was just a calibration issue with my device and didn't do anything about it before swapping it for a non-exploding phone.
I had no problem with my recalled Note 7. The replacement is messing up with waze. All the symptoms listed above are happening. Ugh
Hmm..that's not good..I still need to get mine replaced...
No GPS issues with Waze on my note 7. I use it daily and mine is a replacement. The only issue im having with Waze is the voice commands. The three finger option and waving just don't do anything! Anyone have an issue with that? I want my one eyed purple monster back!
IDK, I haven't checked on my Note 7 yet, I find this a bit funny though, Most GPS's should be accurate to within something like 5 feet, They are really accurate to within fractions of an inch but the Government and Military makes sure that the firmware on the GPS's for use by the general public are locked out of that level of accuracy. It really is a joke these days.
Do a search and in the search box enter in 2##2 to enable debugging and then enter in ##@rawgps and it will show you what your phone is reporting as the actual raw GPS via a yellow arrow. Send in a debug log on the very bottom of the settings every day. Could be possible that Waze can make adjustments to the note 7. I personally haven't noticed any issues with either phone yet, I do also keep my phone in a case and in a windshield car holder with a good view of the sky. When I ran the app for the first time though I did have to toggle location off and on to get Waze to get a GPS lock.
I returned my replacement unit and got another Note 7. No change. Waze is still showing me taking exits and being on the side road before correcting. Very annoying and the constant recalculate and accompanying chime make it onerous to use. Google maps seem to be fine. I submitted a ticket to waze as well as sending log files. I hope a fix comes soon. I need my alerts when commuting.
I fixed my Wave problems. Apparently when you do the smart switch transfer, it transfers some settings or calibrations maybe. I went into phone settings, application, waze, long press storage, clear cache, clear data. Then Uninstaller and re-download and install waze. Mine has been rock solid since doing this. Hope it works for you too.
Hey all so far I've been loving the Oreo update for our Moto z Play. It looks nice, is functional and pretty comparable battery life to nougat. Yesterday however something changed, my phone went absolutely crazy and started rebooting itself. It rebooted maybe 25 times in an hour. Sometimes I could use it for a minute or two between reboots sometimes 10 minutes and it stopped almost as suddenly as it started. I've also twice had network signal drop on me completely and only rebooting the phone restored it. My signal bars completely disappeared and even in the notification area you couldn't see the data toggle anymore. Again reboot fixed this, but what's going on? This is completely stock from Motorola and i relocked my bootloader, so no mods whatsoever have been done.
Thoughts, comments idea's?
None for me, except for the annoying navbar repositioning that I can live with.
I have a small issue. Apps won't update is Google Play Store, apps will sit on 'Download pending...' and take upwards on an hour to download a single update.
I notice a static sound coming out from my speaker when I play a any sound, like if the speaker is saturated, but I'm almost sure that is software and not a hardware issue
when I call the assistant from home button, it appears sometimes behind the home screen icons!
Screen turns black for half a second. It happens rarely but it is something that happened with G4 Play. It's a kernel issue.