Related
Hi,
I've just gotten my Vibrant over the weekend and now I'm noticing after I allow google.com to use the "location service" (first time it works fine), when I browses to some other sites then comes back to it, or just simply re-open the browser in a later time and goes back to google.com (mobile version btw), the browser just closes itself.
I've also tried a factory reset and still was able to reproduce this issue.
Now if I do NOT allow the location service, everything would be working fine.
Is anybody else having the same issue?
my phone is not rooted.
Thanks.
Happening to me to, very very frustrating
Its probably due to the GPS. Try turning it off or applying the temp. fix.
the flash plugin has been giving me a bunch of browser crashes, not sure if that is you issue but seems to work for me with it turned off
It started happening to me today. It was working all this week with locations turned on and google as my home page, however this morning I opened the browser and it closed by itself, repeatedly. I realized that it had something to do with location as it closed imediately after "updating location". I set the browser not to use the location and now it works fine.
However, now I get "location unavailable" and a link to update. If I click update, then the browser closes, so it seems to be related to lbs.
What I don;t understand is why it started happening yesterday, after a week of normal operations.
I really hope the GPS and compass are fixed in the next release/OTA update, otherwise, back to my nexus one.
Did anyone ever find a fix for this? It happens intermittently on my phone. I turn off location sensing and use it for a while that way and it works fine. Usually, I can re-enable location the next day and everything is okay for a few days before it starts automatically closing again.
Time to use m.bing.com
Google.com force closing
Happened to me too. Here's the fix:
Go into browser. Before it finishes loading Google.com, go into Settings and disable Location and Plugins.
Now use a task killer to fully kill the browser.
The final step is to go into the browser again and re-enable everything.
Did it work for you?
On an unrelated note, this seems like a Galaxy-S bug:
"Originally Posted by Samsung_Engineer
As Mentioned above, you can either disable Java or the plug-in options in the browser settings for the time being. We have fixed this issue and the soon-to-be-released Maintenance release includes this fix.
Thanks for choosing Samsung!
JP"
leglevy said:
Happened to me too. Here's the fix:
Go into browser. Before it finishes loading Google.com, go into Settings and disable Location and Plugins.
Now use a task killer to fully kill the browser.
The final step is to go into the browser again and re-enable everything.
Did it work for you?
On an unrelated note, this seems like a Galaxy-S bug:
"Originally Posted by Samsung_Engineer
As Mentioned above, you can either disable Java or the plug-in options in the browser settings for the time being. We have fixed this issue and the soon-to-be-released Maintenance release includes this fix.
Thanks for choosing Samsung!
JP"
Click to expand...
Click to collapse
I figured the reason why we're waiting so long for the GPS fix is because it's being bundled in with other fixes.
leglevy said:
Happened to me too. Here's the fix:
Go into browser. Before it finishes loading Google.com, go into Settings and disable Location and Plugins.
Now use a task killer to fully kill the browser.
The final step is to go into the browser again and re-enable everything.
Did it work for you?
On an unrelated note, this seems like a Galaxy-S bug:
"Originally Posted by Samsung_Engineer
As Mentioned above, you can either disable Java or the plug-in options in the browser settings for the time being. We have fixed this issue and the soon-to-be-released Maintenance release includes this fix.
Thanks for choosing Samsung!
JP"
Click to expand...
Click to collapse
Well this quote squashes any hope of getting Froyo in sept along with the GPS fix since they are calling it a Maintenance release. I was hoping they were going to give us a surprise with the GPS and bug fixes for all of our troubles...
I asked about this issue a long time ago when the Vibrant was first released. No proposed solution consistently works. Therefore I just leave location off for Google.com. Try using the application "Places" as an alternative to the Google.com location-enabled local search.
Hopefully this bug is fixed in the future.
Sent from my SGH-T959 using XDA App
I don't know why, but mine seems to have mysteriously fixed itself. I even have the gps on to find out if it WILL close by itself and..nothing. It works fine now after two and a half weeks of not working. Finds my location and doesn't close.
Ankheperure said:
I don't know why, but mine seems to have mysteriously fixed itself. I even have the gps on to find out if it WILL close by itself and..nothing. It works fine now after two and a half weeks of not working. Finds my location and doesn't close.
Click to expand...
Click to collapse
Just give it a bit and it will start crashing again ;-p
Just kidding, hopefully it stays working for you. For those of us for whom it doesn't work, check out places directory in the market.
Sent from my SGH-T959 using XDA App
For some reason while I'm using the N7, just browsing various websites or looking at videos, the error notification "unfortunately maps has stopped" pops up.
I searched around for a fix or even other threads about this on the N7 but have not seen any.
I've tried re-installing the Maps application on my N7 but it seems like it can't be uninstalled. I disabled the app and the error message stopped, but when I wanted to use the Map app, I had to enable it, and after use did not disable and noticed the error notification pop up at around the same frequency.. (every other day or so.)
I have not rooted the device, and have only downloaded/installed a handful of apps; am using Apex launcher as an alternative for the lack of landscape view on the home screen. Thanks in advance for any help.
Same problem I'm having. Not rooted, completely stock.
Sent from my Nexus 7 using xda premium
I'm also having this problem with the Nexus 7 and CM10, but good to know it also happens in stock, saves me some trouble.
ESTEEeFFY0U said:
For some reason while I'm using the N7, just browsing various websites or looking at videos, the error notification "unfortunately maps has stopped" pops up.
I searched around for a fix or even other threads about this on the N7 but have not seen any.
I've tried re-installing the Maps application on my N7 but it seems like it can't be uninstalled. I disabled the app and the error message stopped, but when I wanted to use the Map app, I had to enable it, and after use did not disable and noticed the error notification pop up at around the same frequency.. (every other day or so.)
I have not rooted the device, and have only downloaded/installed a handful of apps; am using Apex launcher as an alternative for the lack of landscape view on the home screen. Thanks in advance for any help.
Click to expand...
Click to collapse
Have you tried this: Goto Settings > Apps > Maps > Force stop, clear cache, clear data. Then try rebooting your N7.
---------- Post added at 07:46 PM ---------- Previous post was at 07:42 PM ----------
andy o said:
I'm also having this problem with the Nexus 7 and CM10, but good to know it also happens in stock, saves me some trouble.
Click to expand...
Click to collapse
Have you tried fixing permissions in recovery or through ROM Manager?
I've tried both, and I've tried uninstalling and reinstalling maps, it still happens. Yesterday it interrupted me twice while I was playing a game. It's starting to get annoying.
Yes this is also an annoying issue for me.
Sent from my Nexus 7 using Tapatalk 2
If you don't *use* maps, and all the attendant programs (like local, navigation, etc) you can always go into your appdrawer, longhold the app and drag it up to App Info. (or go settings>apps>maps) and choose to "disable" the program.
(This *should* be possible stock, not rooted. I may be wrong, I didn't leave my N7 stock very long ;P)
I might have figured it out. Go to maps, settings, location settings, location reporting, select "do not update your location". So far no message this past day or so (crossing fingers).
[edit] Spoke too soon, just got one.
Call Google Apps support.
I had this issue happen to me for the Gmail app, and unfortunately, this was happening on two devices, occured after Factory Resetting two devices, and removing and re-adding the account.
Google might have changed/switched a setting, and it may have affected your ability to access any saved data you have on your account.
Same problem here, maps has stopped. Happend when my N7 was stock, andre now when it is rooted.
FWIW, this has never happened to me again since I installed AOKP some days ago.
andy o said:
FWIW, this has never happened to me again since I installed AOKP some days ago.
Click to expand...
Click to collapse
what's aokp? i still have this problem on my n7 and it bothered me again today to the point of googling for a solution, and what do you know, my own thread pops up.
AOKP is a custom ROM. Build 2 just came out a couple of days ago and build 3 is on the way. Cyanogenmod 10 may also have fixed this problem but I haven't tried any recent builds. Also, maps was updated very recently, are you on the last version?
Same Here
i have same problem with google maps on my xperia neo after i flashed my last rom.
after a fresh installation. it s runnning but when i restart i have that message "unfortunatly.. app stoped"
this stuff happened to me all the time on my N7, part of the reason i returned it.
note 2 l900 Unfortunately maps has stopped using favorites
No solutions recommended thus far have worked (fix permissions, clear cache, disable download reenable).
Every time I select a favorite or home or work in maps, it crashes andi get that error message. If I select from the history or manually enter, there's no issue.
Rooted stock Android 4.1.1. Version 6.10 maps.
But not the updated version. I hate the maps updated version. It worked fine until about a month ago (give or take).
Why are so many having this issue?
It may be the same prob fr evry1....or diff prob with similiar manifestation...post your logcats if you can....
Sent from my Nexus 7 using xda app-developers app
..oops
neo45215 said:
It may be the same prob fr evry1....or diff prob with similiar manifestation...post your logcats if you can....
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Sorry for not responding with them ... I stopped following the thread when I found out the glory of Waze (and installed Whompasaurus)
i've read somewhere that could be a font size problem, go to settings and configure the smallest font size and try again, to me i didnt worked, but somehow the crash is delayed 1 or 2 seconds more
edit: i fixed it, my solution was to change the language
on android 4.4.2 (paranoid) you go to settings>>language & input>> english (United states)
don't know why i've set it to [ Developer] Accented English (zz_ZZ), that was the problem
another solutions i've read:
clean cache app
turn off phone, remove battery, wait 5 secs, turn on
flash gapps downloaded from your custom rom web
reset gps and agps, you can do this with "gps status" (search on play store)
try with another wifi, or mobile data plan (some people had problems with wep encrypted wifi's)
guritaburongo said:
i've read somewhere that could be a font size problem, go to settings and configure the smallest font size and try again, to me i didnt worked, but somehow the crash is delayed 1 or 2 seconds more
edit: i fixed it, my solution was to change the language
on android 4.4.2 (paranoid) you go to settings>>language & input>> english (United states)
don't know why i've set it to [ Developer] Accented English (zz_ZZ), that was the problem
another solutions i've read:
clean cache app
turn off phone, remove battery, wait 5 secs, turn on
flash gapps downloaded from your custom rom web
reset gps and agps, you can do this with "gps status" (search on play store)
try with another wifi, or mobile data plan (some people had problems with wep encrypted wifi's)
Click to expand...
Click to collapse
Changing the language from (zz_ZZ) to english (United states) worked for me thanks man
I was gonna buy a new tab cuz i use map regularly
Running stock 4.2.1, stock kernel.
Cleared cache and dalvik, rebooted back into rom.
Now Google Now force closes. If I clear data on "Google Search" app, and select not to enable Google Now, all is well.
As soon as I try to enable it, it crashes.
Tried fix permissions, didn't work.
Also disabled location settings, and allowed me to open google now.
Next I enabled settings, but only GPS. This worked as well.
Once I had GPS AND wifi, it crashed again.
Tried removing updates, restarting, clearing google framework data, etc.
What am I missing?
can't launch google now
I just started getting the same problem today. I can't launch the Google Search app without it immediately crashing (Unfortunately Google Search has stopped. Report / OK). If I reset data on the app I can launch it again until I turn on Google Now after which it crashes immediately again.
I'm on a stock Nexus 4, boot loader never been unlocked, not rooted, etc. I can't seem to find any other mentions of this problem anywhere.
ricecakes said:
I just started getting the same problem today. I can't launch the Google Search app without it immediately crashing (Unfortunately Google Search has stopped. Report / OK). If I reset data on the app I can launch it again until I turn on Google Now after which it crashes immediately again.
I'm on a stock Nexus 4, boot loader never been unlocked, not rooted, etc. I can't seem to find any other mentions of this problem anywhere.
Click to expand...
Click to collapse
Anyone else? I've been driving myself nuts trying to fix it!
Thinking of just dirty flashing stock again...
I'm pretty sure it's a server side problem with Google Now data that is causing the app to crash.
ricecakes said:
I'm pretty sure it's a server side problem with Google Now data that is causing the app to crash.
Click to expand...
Click to collapse
What I figured. Now I'm missing my Nexus 7 from the My Devices tab. Somethings going on. Just can't find any news/reports of it.
Yeah, I don't understand why nobody else is encountering this problem.
This thread is the only relevant result in web search.
There are 3 other people encountering the same issue on Google+ but I cannot post links because I just created this account.
Search for "google now crashes" on Google+ and you should see a few others with the same problem but no solutions.
My gs3 started doing fc'ing after I installed a new room. Hope it is something server side because I can't fix it.
Problem seems to have fixed itself.
ricecakes said:
Problem seems to have fixed itself.
Click to expand...
Click to collapse
Ditto. Weird.
ricecakes said:
Problem seems to have fixed itself.
Click to expand...
Click to collapse
Same here. Cool I was nervous for a bit there.
I'm the same boat guys after installing jellybam for my sgs2 4.1.2 was working in another ROM same base going to try flashing gapps again or push a new Google search apk
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I'm on 5.0 with Xposed and the ColorFade Memory Leak fix. However, it seems that Lollipop is still force closing background apps too quickly. I play Hearthstone a lot, and I used to background it to go on chrome or respond to a text message or something in Kitkat 4.4 with no issues. Now on 5.0, it will close very quickly. I even hit home sometimes and went right back into the app without doing anything else, and saw that it had closed instantly. Is there any fix for this, or do I just have to wait?
I also noticed that when I was using Google maps and Spotify, then opened Waze, the first two would force close as well. This wasn't an issue on KK 4.0 either.
have the same issues on the stock firmware
I'm on tmo and I have the same problem. it's with stock and AOSP. I can't run pocket cast and anything else for fear of pocketcast (or google music for that matter) closing. I wonder if there is a way to increase it's priority so lollipop won't close it.
xcom923 said:
I'm on tmo and I have the same problem. it's with stock and AOSP. I can't run pocket cast and anything else for fear of pocketcast (or google music for that matter) closing. I wonder if there is a way to increase it's priority so lollipop won't close it.
Click to expand...
Click to collapse
I heard that TouchWiz by Samsung wasn't supposed to have this issue even though all other flavors did, but considering I'm having it, it's not the case.
There's a thing in the Xposed module, App settings, called resident which allows an application to be forced/higher priority in memory, but I find it either doesn't work because lollipop's force close background apps is too strong, or it only makes the background apps stay a tiny bit longer.
Update: I found out today that my issue was disabling Touchwiz's DVFS in the Wanam Xposed module. Re-enabling it fixed all my issues it seems.
Spartan117H3 said:
Update: I found out today that my issue was disabling Touchwiz's DVFS in the Wanam Xposed module. Re-enabling it fixed all my issues it seems.
Click to expand...
Click to collapse
Wow, is that what's been happening? I've been having this same problem on my T-mo Note 4 N910T (Lollipop 5.0.1) with apps aggressively being killed. I've been pulling my hair out because I had no idea why. After seeing your post and disabling the DVFS killer I no longer have this issue. Overlooked it because it just wasn't in my list of things that would be causing it. Thank you!
Recently I am having notification delays with my S7 Edge G935F. I have read through some posts on this forum and other sources and can't figure it out.
Here are some of the problems:
1. notifications are often delayed for more than thirty minutes
2. if I want to manually check notification when it does not pop up, unlocking the screen does not make the notification show, I have to actually launch the specific app to see the notification
3. It is more than just not showing the notification, when I am using some instant messaging apps (like WeChat), I can't see new messages coming in while the app is running in the front. I have to press the home button and get back to home screen, then re-enter the app, then the messages show up. This happens to many other apps as well.
4. Other things go wrong as well. For example, my Android Auto was set to launch whenever I get into my car and car bluetooth is connected. It is also delayed, by more than hours. It often launches long after I finish my driving and get back home sitting on my couch.
5. Downloading new apps from Play Store has problems as well. It downloads to 100% and just stops there, it does not start installation. I have to use Settings->App to kill Play Store and re-open it to "refresh" it, then it starts to install.
6. After installation of new app, it does not show up on my screen or app draw inside my launcher. I can see the app installed in Play Store. I have to kill launcher and re-open the launcher to make it "refresh" the app list then I can see new app inside the app draw.
I have also tried a lot of ways to fix it:
1. change app to not battery optimized -> didn't fix it
2. update firmware -> didn't fix it
3. factory reset -> works for the first day then it goes wrong again
4. flash to a different firmware (official ROM in different regions) -> works for the first day then it goes wrong again
5. use third-party ROM (Lineage OS) -> completely fix the problem, but too buggy to use
I can see the general idea of what's going wrong, some events happened (connected to car Bluetooth, new messages coming, app finished downloading, new app installed, etc.) and the system is not responding correctly. I am not very familiar with Android development but I feel like something is wrong with the "event handling" or "event raising" inside Samsung's Android system.
Please post reply if you have any idea or are facing the similar problems.
EDIT:
The phone is on Android 7.0, Build Number NRD90M.G935FXXU1DQER
You've stated that flashing the custom ROM solved the problem, so maybe you should try flashing a different rom that's a bit more stable.
From personal experience i can recommend the SuperStock rom. It's stock (obviously) and it's debloated and very stable with pretty good battery life as far as i remember.
there is some info about it here: https://forum.xda-developers.com/s7-edge/help/want-to-root-custom-one-stay-stock-t3631098?styleid=18 (ignore the root part).
Hi,
did you find any solution to this problem ? cause i got the same problem, and i'm going crazy... few months already and can't figure out what is the problem...
the temporary fix i've found is disabling the "google app" in application manager... it fix the problem but i can't use any Google app features (and i like using them...).
I've found few ppl experiencing the same problem searching on internet but no one with a real fix...
if someone more experienced can help debut this it would really mean a lot...
I think it is the battery optimization setting. You may check the settings>battery>advanced settings>optimize apps. You need to keep the apps un-optimized if you want the notifications and sync.
Also, you may check if Sync is on or off.
If these two does not solve, factory reset if you are on stock ROM. If on a custom ROM, you may check a different ROM
Hi,
Thanks for your reply. Actually none of this works... The only thing that "fixes" the issue is disabling the Google app in the application manager... That's why its so weird...
The problem started around July/August 2017 for me...
As i discovered that disabling Google was fixing the problem, i assumed that they'll correct it by updating the app... But only one update of the app was ok, all others would make the problems reappear...
Messing with battery optimization settings doesn't change anything for me... Factory reset as well... The problem comes back as soon as the google app gets updated...
Try clearing cache and deleting data from the Google app the time the problem occurs
already tried... doesn't help at all...