Stock nexus, 4.4
Starting about a week ago the amazon app just keeps crashing, over and over. I've tried clearing data and cache, uninstall/reinstall. Also get some other apps randomly crashing, but not that often. Amazon crashes every few seconds and i can not use the app.
Anyone have any suggestions on how to fix this?
Edit: on the play store I see a lot of people complaining about the same thing. Oddly, if you use the amazon store to install the amazon app, it looks like it's a slightly older version, which is working (or it's the phone version since it seems to play prime videos)
Related
All of a sudden outta nowhere, Google maps has been force closing on me. I searched it on Google and there is a thread over in the Samsung vibrant forums where a lot of people are having the same issue. It was working fine yesterday. Can anyone else check and post your results?
google maps force close
I'm getting force close on google maps using dell streak today after about 10 seconds - cant get past the whats new in google maps screen
+1 on places app
[10char]
same here ... try uninstalling and reinstalling google maps. It has been working so far for me.
This is weird, I tried uninstalling/reinstalling and changing kernels, and it still is force closing. For some reason if I use WIFI it works fine, if I switch back to 3g, it force closes again...
Same here tried everything even flashing a new rom......
Yes. Really amazing to me that Google can put out updates that force close on their own platform.
Sent from my PC36100 using XDA App
I just got mine today. Non-rooted, 2.2 and it FC'd on me before and after the maps update. Sprint reinstalled software - no dice. Since others have it that gives me hope for a software patch and not an exchange.
Me too.
I really needed Maps for traffic today. First I started getting "failed to login." Then I started getting FCs. I was on Fresh 3.0. I tried uninstalling and reinstalling Google Maps. I was still getting FCs. I flashed to Fresh 3.1.0.2. I'm getting "failed to login," again. I hope Google puts a patch out.
Looks like they fixed it. Atleast its working for me now.....
I am in Southern California and not only had the F/C with Google all day but also had my phone reboot about 10 times while trying to use either Google or Sprint Navigation. I thought it was my phone as I have had this happen before. It would happen when I would turn the GPS on. Not sure what the cause is, and I am thinking it maybe time to fully root my phone and move to a different Rom. I am just running stock with the fist version of Unrevoked that ever came out.
I got the latitude list open before one of the force closes. after that it worked again
Sent from my PC36100 using XDA App
i thought mine was F/C because i was not connected to the data network. to save battery i turn off 3g manually and thats when Gmaps would close on me, then i turned back data and it worked flawlessly.
Same
endoracing said:
same here ... try uninstalling and reinstalling google maps. It has been working so far for me.
Click to expand...
Click to collapse
Yup, I did exactly that, uninstall then reinstall Google Maps after encountering FCs out of the blue yesterday, and now no more FCs.
I recently flashed the Jellybean RC3 rom and noticed some issues.
Chrome causes my phone to do an automatic restart and I can't find a way around it.
It tends to lag in terms of responding to clicks or movements.
And the big issue for me is that the Play Music app (Google) continues telling me "Music temporarily unavailable Couldn't play the stream you requested." Before I flashed this rom, I had no issues using the app and now I continue to receive these errors.
Does anyone know what could be causing these issues and how to fix them?
Update: I just tried with the Tiny CM10 and it is the same issue.
It worked fine before flashing to these roms. Any idea why that would be?
This is a known bug launching chrome from the dock. Either launch it from your desktop, or another workaround apparently is to put it in a folder in the dock.
I had RC3 for a while, then switch over to CM10. Everything seemed to be a lot more stable, but Chrome also does weird stuff on CM10 as well. Never could get it to work normally on my DINC
romeyjdogg said:
I had RC3 for a while, then switch over to CM10. Everything seemed to be a lot more stable, but Chrome also does weird stuff on CM10 as well. Never could get it to work normally on my DINC
Click to expand...
Click to collapse
I don't like chrome even on the galaxy nexus. Slower and buggy to me. I used to but stock is better.
Sent from my Galaxy Nexus using Tapatalk 2
AntiStache said:
I recently flashed the Jellybean RC3 rom and noticed some issues.
Chrome causes my phone to do an automatic restart and I can't find a way around it.
It tends to lag in terms of responding to clicks or movements.
And the big issue for me is that the Play Music app (Google) continues telling me "Music temporarily unavailable Couldn't play the stream you requested." Before I flashed this rom, I had no issues using the app and now I continue to receive these errors.
Does anyone know what could be causing these issues and how to fix them?
Update: I just tried with the Tiny CM10 and it is the same issue.
It worked fine before flashing to these roms. Any idea why that would be?
Click to expand...
Click to collapse
Chrome wouldn't even start on my Incredible with the RC3 ROM. I would advise using the stock browser until Albinoman works out all the kinks (although the work he's done so far is awesome!). I've also had connection errors before, primarily in the Play Store, retrying a few times seems to work. I always use Wi-Fi and haven't tried cellular data so I can't help you there if you're using 3G to stream.
AntiStache said:
And the big issue for me is that the Play Music app (Google) continues telling me "Music temporarily unavailable Couldn't play the stream you requested." Before I flashed this rom, I had no issues using the app and now I continue to receive these errors.
Click to expand...
Click to collapse
Maybe something to do with your Android ID changing when flashing these newer ROMs? Though that usually shows itself in problems downloading stuff from the Play Store... but you may need to clear data on the Google Music app, also maybe clearing data on the Play Store may help too.
andrewia said:
Chrome wouldn't even start on my Incredible with the RC3 ROM.
Click to expand...
Click to collapse
The main reason I dislike Chrome is because of the space it takes up. It eats up over 30Mb of app data, which on our Dincs is stored in the 150Mb datadata partition. So if you have a reasonable number of apps installed, it's very likely that Chrome will fail to install properly due to there not being enough space to install its data, and it will fail complaining that "your phone lacks functionality critical for running Chrome." In reality, the problem is that Chrome is just too bloated to fit on the limited partitions in our dincs.
(flashing the etx4all nodatalimit mod solves this issue, as does moving all possible apps to the sdcard, but IMHO Chrome is not nearly worth going to all that bother.)
Hello,
I am having a big trouble somwhere since the new Play Store was introduced. Everything was fine earlier, but right now Play Store randomly stops applications on "Starting download...". It happens both on stock and CyanogenMod ROMs. It just looks like it downloads the apps which it wants to. On the other hand it only behaves at home (2mb Wi-Fi) but at work (download rate about 5mb/s) everything works flawless. Also, on packet data everything works fine. Is it problem with my router ? I did not changed any settings for ages, so I dont think so. Or does the Play Store started to "choke" on slower connections? Any advice would be appreciated.
To be clear: I've tried reflashing, clearing caches of play store or download manager, wiping through recovery. Nothing works. I am using NEAK Note2 kernel, but I think it does not matter.
Best Regards.
tehaerpl said:
Hello,
I am having a big trouble somwhere since the new Play Store was introduced. Everything was fine earlier, but right now Play Store randomly stops applications on "Starting download...". It happens both on stock and CyanogenMod ROMs. It just looks like it downloads the apps which it wants to. On the other hand it only behaves at home (2mb Wi-Fi) but at work (download rate about 5mb/s) everything works flawless. Also, on packet data everything works fine. Is it problem with my router ? I did not changed any settings for ages, so I dont think so. Or does the Play Store started to "choke" on slower connections? Any advice would be appreciated.
To be clear: I've tried reflashing, clearing caches of play store or download manager, wiping through recovery. Nothing works. I am using NEAK Note2 kernel, but I think it does not matter.
Best Regards.
Click to expand...
Click to collapse
Looks like you tried everything obvious.
But have you tried just using stock kernel? Just my 2 cents. Ml
tehaerpl said:
Hello,
I am having a big trouble somwhere since the new Play Store was introduced. Everything was fine earlier, but right now Play Store randomly stops applications on "Starting download...". It happens both on stock and CyanogenMod ROMs. It just looks like it downloads the apps which it wants to. On the other hand it only behaves at home (2mb Wi-Fi) but at work (download rate about 5mb/s) everything works flawless. Also, on packet data everything works fine. Is it problem with my router ? I did not changed any settings for ages, so I dont think so. Or does the Play Store started to "choke" on slower connections? Any advice would be appreciated.
To be clear: I've tried reflashing, clearing caches of play store or download manager, wiping through recovery. Nothing works. I am using NEAK Note2 kernel, but I think it does not matter.
Best Regards.
Click to expand...
Click to collapse
Which Version of Play store are you on , Try to clear DATA of playstore in App manager and give a try
When Google Play Services (GPS) version 4.0.33 was posted here, I downloaded and applied it without issue. Even though I wasn't having any trouble with it, I decided to incorporate all of my system app updates with Titanium Backup to open up a little space on my phone. I had a handful of apps ready for incorporation, so I just hit run and set my phone down for a few minutes to let it finish. I've never had any trouble with this operation before, but this time it hung when it reached GPS until I force quit TB. When I went to restart the operation, GPS was no longer listed as an app ready for incorporation, so I figured it had worked and everything was fine. TB hung up two more times after that on different apps, so I continued the operation 1 app at a time until I was finished. Geting to the point, I noticed I no longer had GPS on my phone later when I went to open an app that required and it told me I didn't have it. So I went to the Play Store and downloaded version 4.0.31 and installed it as a normal app. Then I used TB to convert it to a System App because that was the way it was before. But then it started force closing and none of my apps that require it would work. So I removed it and restored the original that I had backed up with TB, and everything was fine again. I decided not to mess with the 4.0.33 update anymore. Then a few days ago 4.0.33 was officially available on the Play Store as an update, so I updated that way. Ever since, every time I restart my phone it force closes 3 or 4 times, but then seems to work fine until the next reboot/start up. Also, I've noticed that every time GPS starts having issues, the Google Settings app icon turns grey*, but it seems like it still works fine regardless of the color of the icon.
Anyway, I was just wondering if I was the only one having these issues, or if someone has managed to fix it if you've experienced this? Thanks in advance!
* It was always green before this fiasco, now it's only green if I "Uninstall Updates" to GPS via App Manager since GPS no longer shows up on the Play Store for me until I have uninstalled the 4.0.33 update, and then it shows it's ready for an update...
I ran into the same problem after I tried to integrate GPS 4.0.33 into the stock rooted ROM of my Nexus 7 (4.4 KitKat). I had to reinstall 4.0.31 in order to get it back to work. After the first reboot GPS was automatically updated to 4.0.33, but I won't try integrating it with Titanium again for fear of running into the same issue. I used to integrate all of the Google apps that came with the stock ROMs as soon as I received an update. But with 4.3 JB I started running into problems when I tried to integrate Chrome, Earth and Google +. I recently got updates for all of these, but I did not tried to integrate them into 4.4. My Google settings icon is grey, but I don't know if that is causing any side effects. I was never able to manually update GPS via the Play Store. It has always been pushed to my Nexus 7 and SGS3. It would be nice to know what specifically makes these apps incompatible for integration with Titanium or with other program for that matter. For what I can see, there is enough storage space left to integrate them. In previous ROMs I have also used Apps2ROM to integrate apps that were not included in the stock ROMs. Btw, what version of Android are you running?
I've seen a few threads without replies about this topic, but has anyone gotten the Play Store to work on a stock 8.4.3? I've found that stock is the most useable ROM speed-wise and the only major setback for me is lack of the Play Store.
I've tried several guides:
http://www.cnet.com/how-to/how-to-get-the-google-play-store-on-the-kindle-fire-hd/
http://www.howtogeek.com/232726/how-to-install-the-google-play-store-on-your-amazon-fire-tablet/
http://www.lovemyfire.com/google-play-apps-kindle-fire.html
http://forum.xda-developers.com/showthread.php?t=2365224
I've gotten everything installed and it did work at first, but it wouldn't download any apps without updating first and then it worked for a couple apps. I then started getting the error "Google Play Services Framework has stopped." constantly. As soon as it closed it would reopen without a couple seconds and the only thing I could do was trudge along and force stop the framework service. Removing the updates kept the error and it needed a fresh install to stop the errors.
Now I reckon I'm up ****s creek without a paddle but if anyone had any ideas or has successfully gotten Play Store working I would happy if you could share any info.
Cheers.