After the Jelly Bean update from T-mobile (running this custom ROM) whenever I try using google Navigation, I am seeing this message after a minute or less: "Unfortunately Maps has stopped working." Then the graphical display stops working, although it appears that Navigation itself still works in the background (I still get audio updates). Turning navigation into 2D mode (by pressing the compass icon) seems to resolve the issue.
Has anyone else had received this error since updating and if there's anything else that can be done to fix Navigation (3D mode)?
I've had that same issue for a while now not just on that ROM. I had it when I was running CM10.1 as well.
Sent from my HTC One S
I'm having the exact same problem and my phone is stock. Never had an issue until the JB update, and my wife's stock One S does not have the issue even post-update.
I tried uninstalling/reinstalling Maps and Search wondering if it had something to do with Google Now, but that hasn't helped. Not sure what else to try short of a factory reset, but I use the nav somewhat frequently and it's pretty annoying to rely on the audio only.
Big Smooth said:
I'm having the exact same problem and my phone is stock. Never had an issue until the JB update, and my wife's stock One S does not have the issue even post-update.
I tried uninstalling/reinstalling Maps and Search wondering if it had something to do with Google Now, but that hasn't helped. Not sure what else to try short of a factory reset, but I use the nav somewhat frequently and it's pretty annoying to rely on the audio only.
Click to expand...
Click to collapse
Mr. Smooth, You can still use Navigation, just in 2D mode by hitting the compass icon in the upper left.
mongoosesRawesome said:
Mr. Smooth, You can still use Navigation, just in 2D mode by hitting the compass icon in the upper left.
Click to expand...
Click to collapse
Appreciate the tip. I will try that next time out. :good: Would still like to see a fix soon though.
This is so weird.
My friend has the problem on their device and I have tried navigation for over a hour of driving a day for a week and can't replicate the problem.
Is it with any specific settings maybe or something? I do have 3d on too not 2d.
I am using a stock rooted rom on the phone from the recent T-Mobile update.
Hi all.
Is there a known issue with the latest "standard application updates" that may cause the system crashing and rebooting?
I dont know if there is such a thing like "event log" in android to help tracing the error im getting since today.
First time was while I was playing Mortal Kombat X Mobile, game went unresponsive, screen black, charge led was flashing strangely and very short, almost unrecognizable. Now this could perfectly happen just on the homescreen.
Occurs once in a while, Id say almost every 1-2 hours.
Have the latest stock rom , patched, rooted and some minor debloating. Havent touched the system for weeks, everything was perfectly fine, this is the first day it is not.
So if anyone can give me a hint on how to find whats wrong , that would be great.
Guess I'm not the only one! I've been having the same exact problem since yesterday too!
onkelfeix said:
Hi all.
I dont know if there is such a thing like "event log" in android to help tracing the error im getting since today.
Click to expand...
Click to collapse
There is logcat. You're rooted, so it's fine. You can also pull logcat logs via adb. However these logs are cleared once the phone reboots.
I've been having heating issues,very fast battery drain and my camera went back to taking green pictures . It was beacause of updating magisk. I uninstalled it and reflashed the 14v and it is back to normal. I'd recommend seeing if that is the problem
pikeylfc said:
I've been having heating issues,very fast battery drain and my camera went back to taking green pictures . It was beacause of updating magisk. I uninstalled it and reflashed the 14v and it is back to normal. I'd recommend seeing if that is the problem
Click to expand...
Click to collapse
I still have 14.5 installed while it tells me 15.3 is the latest.
No overheating (at least nothing that could be felt on the outside) , camera works as it should.
Did a shutdown and restart, device didnt crash over night, now after its been used for 30minutes, it crashed while reading the news within chrome....
Maybe some kind of Spectre/Meltdown countermeasure patch which affects stability?
Really cant need that as I use my phone for 24/7 support
Just found out that I didn't have the latest build. Was on 47.1.A.5.51 probably.....
Now on 47.1.A.8.49 , still rooted , restored almost everything what has been installed before, so far it has been crash-free since 1-2 hours. If it doesn't crash within the next 24hours , i'll put the simcard back.
Hi,
Hope you are well.
I had bought my Google Pixel about 2 months ago. It was completely new and working fine. I then upgraded it to Android P beta which ofcourse is buggy. After some time, I had random crashes and freezes on my phone so citing that I decided to move back to the stable update. Once I did that, the phone started behaving abnormally. I was unable to use it completely without anything installed or with the usual softwares. It would work fine in Safe Mode. It used to restart and then get stuck at Google Icon with a bar showing at the bottom of it. I then went back to beta where I had the exact issue but it then started working fine. However, yesterday on the beta version as well its speaker did not work. I restarted it and every app got stuck then it restarted on its own and got stuck like the stable version. But I rebooted forcefully and it worked fine. As I have it in warranty from a local vendor (now google in Pakistan), so I decided to reinstall the stable version as we now had June patch. As soon I installed the stable version, without anything installed the phone started restarting just like it used to. It gets stuck on google icon with a progress at the bottom and doesn't work until I use the power button to forcefully shut it down.
I want to unlock the bootloader and flash a previous build but I don't know whether I should do that or just send it back as I am not able to judge up until now whether that's the hardware or the software.
I will really appreciate some help as I have got multiple responses on google searches but these explain motherboard as culprit. :crying:
Update: The phone again is working absolutely fine in safe mode. I just tried that. However, I am unable to even touch it in the normal mode on stable version. I have already tried the rescue OTA.
I've used tge app for over 7 yrars worked perfectly till last update now it works when it wants to. I've sent emails giving info. I've uninstalled rebooted phone ran a ram ckeaner. Rebooted. Reinstalled rebooted and set up. Spent many hours trying different settings doesn't work like it did before last update. Even the simple battery chafing blinking doesn't work everytime. Please help.in a previews email I listed everything I did even attached screen print of my OS screen version numbers of operation system etc.help please email me [email protected]
Lmllm3lpmmmpllp3kk I. Kaj e
I'm using a Pixel, still on Android 9, and my orientation sensor (and accelerometer) have suddenly stopped working. However, it appears that it's a software issue as the auto-rotation still works when in Safe Mode. I've uninstalled every app that's been updated in the past two days (roughly when I think this problem began) but it's still a no-go. I've also installed a sensor test app and I find the sensors do work initially on boot, but freeze after 5 seconds or so.
Any ideas of how I might fix this?
Clear system cache.
You update, install or uninstall any apps recently?
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
ppuzzlerr said:
I tried clearing the cache but it didn't change anything. I also uninstalled all the apps that had recently updated, restarting the phone each time, but the sensor is still frozen unfortunately.
Click to expand...
Click to collapse
Factory reset time...
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
R
BHZero said:
I have the same problem also with Pixel 1 and it happened on the same day (Oct 20)! The difference is I'm on Android 10.
After factory reset and backup restore it works.
After updating all apps, it still works.
After restart once all apps are updated... No work.
Click to expand...
Click to collapse
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
blackhawk said:
R
Roll back to factory settings, one by one and find the culprit(s). Sounds like a rogue 3rd party app.
Once I have a device running well I almost never update anything. I'll run on the factory loaded versions for years many times. Result, no issues.
Click to expand...
Click to collapse
Thanks for the help! How do I do this?
The return to factory settings is in the app under settings.
You can try uninstalling it otherwise.
I don't see that option all the time and you may have to hit uninstall for it to appear.
A forced stop might be enough for troubleshooting.
Typically I use my package disabler for things like this.
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
BHZero said:
So I've done a factory reset with no restore (to keep it clean). Updated every app individually and restarted the device each time.
Updated GOOGLE MAPS. Rebooted.
Presto! All sensors are now locking up and battery starts burning away.
Disabled Google Maps, cleared cache + data, and rebooted. Problem did NOT go away. Now I'm doing one more (hopefully last) restore and will disable Google Maps right away.
Wow... did not expect it to be Maps...
Click to expand...
Click to collapse
I'm not, Gmaps updates are a back street abortion.
So it was the update that trashed it?
I always keep gmail and maps on the factory load version. Invariably updates make them less user friendly on a Samsung
I set Playstore settings for auto updates by wifi only.
I always keep wifi disabled, effectively preventing any auto updating. I also firewall block and disable Playstore unless I need it. It's a background pocket hog.
Updates generally cause more harm than good if the app is already running well...
I have the same issue, and after guessing which app was causing the problem I found out it's the Google app. I disabled it and all the sensors started working back and also automatic brightness. Also I tried leaving the beta updates of the Google app and whenever the Google app is active the sensors stops working. Probably Google trying to kill the pixel 1 or a new function conflicting with the sensors
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Same problem here, since a couple of days ago, some sensors (gyro, light, accelerometer, compas) stop working after a couple of seconds after reboot. I factory reset my pixel, I tried uninstalling GMaps, I tried deactivating Wifi and Bluetooth,... but nothing is working.
Proximity sensor still work though.
gmsalomao2 said:
Oh my god! I have the same issue! Stock Android 10.
Sensors work fine on Safe Mode, but on normal mode they sometimes don't work.
Click to expand...
Click to collapse
Have you tried disabling Google app as mentioned by cristejeda33 above?
I have the same issues, it happens when one or more apps get updated, don't now which one is causing it exactly, but the issue goes away after the next update, and comes back at the next update and so on ..., features like, adaptive brightness, tap to wake, lift to wake, display rotation os and in camera, youtube video rotation....... stopped working and the battery is draining a lot faster. thinking of getting rid of the good old pixel ..
blackhawk said:
Have you tried disabling Google app as mentioned by cristejeda33 above?
Click to expand...
Click to collapse
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
gmsalomao2 said:
I stopped the services from the Google app and the sensors started working. And kept on working for some time after that. They keep stopping and coming back.
Click to expand...
Click to collapse
Try disabling Google play Services... just a wild guess.
It's a dependency or a parent app of Google App that's maybe causing the trouble. These can be hard to ferret out... play with it.
You could just go shotgun and revert all Google apps to factory load version -if- it wasn't a system wide firmware update that triggered it.
I've experienced this too many times, updates break things.
On my N10+ I lock down all updates, especially firmware. I'm rarely updated anything because it causes trouble. Result is a very fast and stable operating platform with minimum maintenance required. When there is an issue it's much easier to track down as the system is a known and familiar quantity. My current load is over a year and a half old... still running strong.
Wife and I are using OG Pixels and a couple of weeks ago we both noticed massive battery degradation. Then we both realized that auto rotate is extremely slow as are a bunch of sensors. Skymap doesn't track anymore. Both our phones also get extremely hot.
Google brought us here and we see that stopping the Google app makes the sensors work normally again. Lots of issues being reported in the playstore for this app also. Would love to hear if anyone has made any headway working around this or are we screwed until an update comes out?
What's the best way we can report this to Google publicly? And put the link here
All accelerometer, compass, gyroscope and proximity sensors turned off a few days ago on my og pixel and after disabling the google app all the sensors are working again.
I had a look on the play store and the last update for the google app was on the 21st October, which is exactly when it broke.
I disabled google maps first, then the google app, then sensors worked, so i re-enabled the maps app, I then cleared the cache on the google app and re-enabled that too, and all is still working.
Thank you very, very much for finding the cause of this, I was about to factory reset the phone and then have to reload everything which may or may not have worked anyway. Your efforts are much appreciated, long may your technology function correctly.