Related
Why is it that I always get FC message every time I start up my Nexus S or opening Android Market which makes Market inaccessible. The start up message would show something like android.media has stopped unexpectedly. Only on Oxygen ROM, 2.3.2 and 2.3.3 (newest).
I've done wiping data, cache and even dalvik cache.
I've tried on different ROM and it works flawlessly. Oxygen is my only problem so is there any solution?
Did you try fixing permissions in recovery?
Source-X said:
Why is it that I always get FC message every time I start up my Nexus S or opening Android Market which makes Market inaccessible. The start up message would show something like android.media has stopped unexpectedly. Only on Oxygen ROM, 2.3.2 and 2.3.3 (newest).
I've done wiping data, cache and even dalvik cache.
I've tried on different ROM and it works flawlessly. Oxygen is my only problem so is there any solution?
Click to expand...
Click to collapse
Welcome to XDA!
I have never had this problem. Do you only get this FC when opening market, or other apps? You should try to repair permissions.
Thanks .
Yes, I forgot to mention I did the permission fix through CWM and it did not fix. Am I supposed to fix it before flashing?
Source-X said:
Thanks .
Yes, I forgot to mention I did the permission fix through CWM and it did not fix. Am I supposed to fix it before flashing?
Click to expand...
Click to collapse
Not really....
I did not fix permission after flashing oxygen, but the rom working fine for me...
maybe you can try fresh install oxygen again maybe??
you forgot wipe /boot....that is how i fixed my problem before and it worked perfect
I'm having this problem where sometimes after I reboot my G2x (running HellFire Phoenix V2.1 with the kernel already included) it would start back up with the "Touch Android to begin" screen as if I just did a fresh install and then nearly all my applications would start Force Closing on me.
I'm not sure what is causing this. My applications that we're previously installed all force close when I try to open it, and the Play Store is back to Market. My saved Google account is erased as well. Any ideas? It's beginning to get very annoying to have to wipe my phone and reinstall everything all over again.
hiefx said:
I'm having this problem where sometimes after I reboot my G2x (running HellFire Phoenix V2.1 with the kernel already included) it would start back up with the "Touch Android to begin" screen as if I just did a fresh install and then nearly all my applications would start Force Closing on me.
I'm not sure what is causing this. My applications that we're previously installed all force close when I try to open it, and the Play Store is back to Market. My saved Google account is erased as well. Any ideas? It's beginning to get very annoying to have to wipe my phone and reinstall everything all over again.
Click to expand...
Click to collapse
have you tried actually going in and wiping /data and /cache before re-flashing the rom to see if it helps? if not, try that.
if its only happening to you on that rom, try flashing another.
if none of this works for you, then use This tool.
Klathmon said:
have you tried actually going in and wiping /data and /cache before re-flashing the rom to see if it helps? if not, try that.
if its only happening to you on that rom, try flashing another.
if none of this works for you, then use This tool.
Click to expand...
Click to collapse
I always use the Nullifier application before installing the rom, yet I'm still having this weird problem. I'm going try that other wiping method and see how it goes. Thank you !
Downloads of gapps/ROM might be at fault also. If wiping doesn't solve it for you then you should re-download them.
Sent from my LG-P999 using xda premium
Hi, I have a Nexus 5, completely stock 4.4.2, never tampered
Whenever there are multiple updates in the Play Store and I press "Update", the first app updates, then the second one starts downloading,
but the download hangs at some point, then after a few seconds the entire Play Store app closes without any message.
After that I can open the Play Store again and try to update the apps, but they only update one at a time, because on the second update it always crashes.
All the Google apps are at the latest versions, Play Store has version 4.6.17. This is happening for a while now, but I can't pinpoint it to a certain version of the Play Store app, but in the past I did not have this problem.
I've tried restarting the device, clearing data and cache for the Play Store app, clearing the cached data for the entire system, even switching the runtime (btw the problem is happening on both Dalvik and ART), but nothing helped. I also have enough Available space: 4 GB as reported in Settings/Storage.
On my wife's Nexus 4, also completely stock and with updated Google apps, the problem it's not happening, so it's not something in my environment.
Did anyone else have this problem? I searched the forums but found nothing relevant.
Any advice?
Thank you.
Hello,
Clear Playstore's app data and cache and reconnect your google account as see whether the problem persists?
Already did that, I said in my post, did not help.
Can anyone provide any advice? Thanks.
andreipaval said:
Already did that, I said in my post, did not help.
Can anyone provide any advice? Thanks.
Click to expand...
Click to collapse
Please Help
andreipaval said:
Hi, I have a Nexus 5, completely stock 4.4.2, never tampered
Whenever there are multiple updates in the Play Store and I press "Update", the first app updates, then the second one starts downloading,
but the download hangs at some point, then after a few seconds the entire Play Store app closes without any message.
After that I can open the Play Store again and try to update the apps, but they only update one at a time, because on the second update it always crashes.
All the Google apps are at the latest versions, Play Store has version 4.6.17. This is happening for a while now, but I can't pinpoint it to a certain version of the Play Store app, but in the past I did not have this problem.
I've tried restarting the device, clearing data and cache for the Play Store app, clearing the cached data for the entire system, even switching the runtime (btw the problem is happening on both Dalvik and ART), but nothing helped. I also have enough Available space: 4 GB as reported in Settings/Storage.
On my wife's Nexus 4, also completely stock and with updated Google apps, the problem it's not happening, so it's not something in my environment.
Did anyone else have this problem? I searched the forums but found nothing relevant.
Any advice?
Thank you.
Click to expand...
Click to collapse
Hi
I have the exact same problem on my galaxy note 3 so nothing to add except that I tried a little trick that allows it to finish the updates without having to restart the store. I close it immediately after the batch download starts and then it continues updating in the background. it works most of the times but not always. I really wish someone had a solution to this problem.
http://forum.xda-developers.com/showthread.php?t=2760607
Did you by any chance ever went into the recovery and tried clearing the cache from there?
andreipaval said:
Did you by any chance ever went into the recovery and tried clearing the cache from there?
Click to expand...
Click to collapse
Yes, I cleared cache and Dalvik from custom recovery. I did a lot of searching on google and XDA and I followed all the guides, including uninstalling play store updates, clear data and cache from apps manager for play store and also Google services framework and download manager but no improvement
Im in the same boat as you on this one.
paolo200 said:
Hi
I have the exact same problem on my galaxy note 3 so nothing to add except that I tried a little trick that allows it to finish the updates without having to restart the store. I close it immediately after the batch download starts and then it continues updating in the background. it works most of the times but not always. I really wish someone had a solution to this problem.
http://forum.xda-developers.com/showthread.php?t=2760607
Click to expand...
Click to collapse
paolo200 said:
Yes, I cleared cache and Dalvik from custom recovery. I did a lot of searching on google and XDA and I followed all the guides, including uninstalling play store updates, clear data and cache from apps manager for play store and also Google services framework and download manager but no improvement
Click to expand...
Click to collapse
Are you rooted? What custom recovery are you using? I myself am all stock, never rooted or anything.
And how long does it take to clear the cache from recovery? On my Nexus 5 with stock recovery it takes very long, around 5 or 10 minutes the first time I do it in succession, but it finishes succesfully. If I repeat the clearing of cache without rebooting then it takes a few seconds, like normal.
I read somewhere that it might be an issue with errors on the cache partition and that reformatting this partition might solve it, but I cannot do it from the stock recovery. Maybe if you have the option of reformatting the /cache partition in your custom recovery you should try it.
Another thing that you can do is try to catch the errors with logcat, if you have root you can use an app, I used adb to save a logcat and found some error messages related to the installing of apps but could not find how to solve them. I will post the logcat later.
If you can get a logcat maybe you can post it and we will compare the errors.
y2whisper said:
Im in the same boat as you on this one.
Click to expand...
Click to collapse
Rooted? Custom recovery?
Did you try to clear cache from recovery? How long does it take?
andreipaval said:
Are you rooted? What custom recovery are you using? I myself am all stock, never rooted or anything.
And how long does it take to clear the cache from recovery? On my Nexus 5 with stock recovery it takes very long, around 5 or 10 minutes the first time I do it in succession, but it finishes succesfully. If I repeat the clearing of cache without rebooting then it takes a few seconds, like normal.
I read somewhere that it might be an issue with errors on the cache partition and that reformatting this partition might solve it, but I cannot do it from the stock recovery. Maybe if you have the option of reformatting the /cache partition in your custom recovery you should try it.
Another thing that you can do is try to catch the errors with logcat, if you have root you can use an app, I used adb to save a logcat and found some error messages related to the installing of apps but could not find how to solve them. I will post the logcat later.
If you can get a logcat maybe you can post it and we will compare the errors.
Click to expand...
Click to collapse
Yes I am rooted using CWM Based Recovery 6.0.4.7 with SuperSU 1.94 and BusyBox 1.22.1-Stericson on stock Samsung firmware Android 4.4.2 NB4 unbranded
clearing the cache from CWM recovery only takes a few seconds in my case. I did not try reformatting or anything else because I don't want to risk bricking it.
I will post a logcat as soon as I know how to do it.
Yup to both. Wipe was very fast... Almost too fast in my opinion
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Might try TWRP to see if it helps
Sent from my Nexus 5 using Tapatalk
Has anyone found the solution yet? no way to update all apps at once. this is driving me crazy especially when there are many apps to update
I'm also experiencing this behavior as well.
Sent from my Nexus 5 using Tapatalk
I have the same issue. Stock rooted...
I don't have a nexus but I was using a google edition ported ROM for my HTC One and was having the same issue drive me nuts. I flashed the stock sense ROM back and the store works fine now. It seems like this problem is google edition devices/OS. I never found a fix though, except to enable automatic updating so it happens in the background. That worked for me
indeed the updates work fine in the background but I would really like to know what causes this issue
Those having this problem can you guys make sure you have the latest Google Play build? Latest is 4.8.20. Go to your play store, go to play store settings and at the bottom it should say 4.8.20. If your version is earlier than that, tap the build version and it should say there's a newer version and that it's installing. At that point, exit from the play store app, and give it a minute or two. Enter back into the play store app, and you repeat the steps to see that you have upgraded your play store build.
Sent using Etch-a-Sketch
Yes, the Play Store app is updated to the latest version. Now I already got the 4.4.3 update, but the issue is still appearing, but not everytime. I think it depends on the sizes of the updating apps, it might be something related to the cache partition. Can you guys try and clear the cache from the recovery and see how much it lasts? For me it lasts more than 5 minutes and it doesn't seem normal.
Sent from my Nexus 5 using XDA Free mobile app
I had the same issue on my S4. After the play store closed about 5 times today when updating apps I decided to Google it. I found someone with a similar issue, and their fix was to enable the Download Manager app, that had somehow been disabled. Mine was already enabled, but I cleared the cache from that app, and then I was able to update my remaining 5 or so apps with no crashes.
I'm not sure how permanent of a fix it is, but it's working so far. Don't know if I'll have to clear it again later or not.
I'm getting the error in several GAPS...however, they all still work. Mostly in Google Plus and Hangouts.
"Unknown issue with Google Play Services".
I've uninstalled Google Play Services using Titanium, but it comes right back.
Using 5.1.1.
Any other tips?
Thanks,
seanvree said:
I'm getting the error in several GAPS...however, they all still work. Mostly in Google Plus and Hangouts.
"Unknown issue with Google Play Services".
I've uninstalled Google Play Services using Titanium, but it comes right back.
Using 5.1.1.
Any other tips?
Thanks,
Click to expand...
Click to collapse
Are you on stock or ROM?
drock212 said:
Are you on stock or ROM?
Click to expand...
Click to collapse
Yeah, using XtreStoLite Deo-Mod Edition 2.2 ...However, I got this error before when I was on another custom ROM. So, I don't think it's the framework.
Do you think I can just download the same APK and reinstall it using Titanium?
I've seen horror stories with doing that.
seanvree said:
Yeah, using XtreStoLite Deo-Mod Edition 2.2 ...However, I got this error before when I was on another custom ROM. So, I don't think it's the framework.
Do you think I can just download the same APK and reinstall it using Titanium?
I've seen horror stories with doing that.
Click to expand...
Click to collapse
I had the same issues on the same ROM you're on. So I did a 100% clean install. Wiping cache, dalvik, system, and data. This fixed it for me
drock212 said:
I had the same issues on the same ROM you're on. So I did a 100% clean install. Wiping cache, dalvik, system, and data. This fixed it for me
Click to expand...
Click to collapse
damn, seems a bit extreme.
seanvree said:
damn, seems a bit extreme.
Click to expand...
Click to collapse
It was my last resort. I had cleared app data. Uninstalled and reinstalled apps being affected, cleared cache through twrp. Nothing worked except a full clean install
drock212 said:
It was my last resort. I had cleared app data. Uninstalled and reinstalled apps being affected, cleared cache through twrp. Nothing worked except a full clean install
Click to expand...
Click to collapse
Ahh, okay. I'm going to try and rip out Play Services. If I do that does all my Google data go away?
seanvree said:
Ahh, okay. I'm going to try and rip out Play Services. If I do that does all my Google data go away?
Click to expand...
Click to collapse
If you do that you'll get endless force closes of Google play services. Idk if your Google data would go with it (everything Google is pretty much stored on their servers so I really don't know what you would lose) but I wouldn't suggest doing this. Trying to navigate through your phone while constantly tapping OK to the message that something has force closed is extremely frustrating and difficult if not impossible.
I had the same issue 2 days ago. I'm stock rooted, btw. The problem appeared when I dirty flashed my stock rom on top of a stock rom. I didn't want to update manually cause I've already downloaded the newest firmware version. So I flashed the newest at hand or what's already in my PC. Then, I had a "google play services error" when logging in my gmail app, had a trouble signing in google now and endless loading on youtube. Did the same, cleared cache play services, guess, I got impatient and I uninstalled it, installed the 448 and 440 newest app but the same thing "google play services error" persisted. I also did the extreme, I did the full wipe and odin'd the new firmware, the problem was gone. Bump into a problem when I installed something and had to dirty flash again. Then, it happened again "google play services error" all over again.
TL;DR, lol, Long story short.
I solved it by just clearing google play services cache and uninstalled updates and let itself update again. I didn't have to flash or odin'd again..
I don't know if it will work for you, but it did for me.
marsen2567 said:
I had the same issue 2 days ago. I'm stock rooted, btw. The problem appeared when I dirty flashed my stock rom on top of a stock rom. I didn't want to update manually cause I've already downloaded the newest firmware version. So I flashed the newest at hand or what's already in my PC. Then, I had a "google play services error" when logging in my gmail app, had a trouble signing in google now and endless loading on youtube. Did the same, cleared cache play services, guess, I got impatient and I uninstalled it, installed the 448 and 440 newest app but the same thing "google play services error" persisted. I also did the extreme, I did the full wipe and odin'd the new firmware, the problem was gone. Bump into a problem when I installed something and had to dirty flash again. Then, it happened again "google play services error" all over again.
TL;DR, lol, Long story short.
I solved it by just clearing google play services cache and uninstalled updates and let itself update again. I didn't have to flash or odin'd again..
I don't know if it will work for you, but it did for me.
Click to expand...
Click to collapse
HOLY ****!!! That worked! at least for now! Thanks sir!
Hi everyone,
my Mate 7 has a tendency to do unexpected, spontaneous forced reboots every now and then. I have no idea what causes it. Recently, it happened multiple times while trying to scan my phone for viruses using the Avira app. Today, I tried to launch 3C Toolbox when it happened.
Any ideas? For info, I run firmware B137SP3 and am rooted with SuperUser.
Have U already tried a device reset and a clean install of thr firmware? Monitorize it after clean install without any other app (no 3rd party apps, just stock apps). If stable, ok it' s not a matter of firmware. Then proceede by installing your apps one by one and monitorize which one of those let the phone reboot.
tuddu said:
Have U already tried a device reset and a clean install of thr firmware? Monitorize it after clean install without any other app (no 3rd party apps, just stock apps). If stable, ok it' s not a matter of firmware. Then proceede by installing your apps one by one and monitorize which one of those let the phone reboot.
Click to expand...
Click to collapse
No, haven't tried that yet. I was afraid this might be the only way to find out what's happening. Since the reboots occur only sporadically (less than once a day), I'll postpone this for when I upgrade to Lollipop - which will require a clean system install anyway.
Thanks for the suggestion though!
How about wiping the cache?
PoisonNinja said:
How about wiping the cache?
Click to expand...
Click to collapse
App cache or cache partition? I have 3C Toolbox installed which automatically wipes all app caches upon reboot.