First off, I know that I installed CyanogenMod 10.2 unofficial but why do all apps FC on my device! I cleared all data and cache but apps like NFS most wanted and twitter FC on 4.3. What gives?
Sent from my SPH-L710 using xda app-developers app
Maybe those apps are not updated to function on 4.3 yet. Or maybe there's something wrong with your Google frameworks on your device. Maybe try going into recovery wiping cache and dalvik and fixing permissions.
Sent from the future via Tapatalk 4
Related
Hi everyone,
So I just recently updated my CM10 to CM10.1 on my S3 (d2att; SGH-I747M), and came across a weird bug.
I don't know if this is a really bizarre feature, or just a bug, but in the Play store, I can ONLY see apps/games! Not books, not music, not magazines, not movies, nor TV. Before this update, I had all of the above.
Also, CM10.1 came with Superuser, and after doing several factory(data)/cache/dalvik cache resets, the Superuser app seems to still crash when I try to allow an app permissions by clicking "Allow" in the "Allow/Deny" screen/popup when an app needs Superuser perms. A temp. workaround is to use CF-AutoRoot by Chainfire to put SuperSU and just disable superuser.
Any way to fix this and does anyone else have one of these, or both of these 'bugs'?
Thanks!
Michael
EDIT: Fixed Superuser bug by updating to latest nightly!
I have not yet seen anyone else report this bug. I am running the 12/23 cm10.1 as we speak and have no issue with the play store or super user. I would recommend to wipe cache, dalvik, and factory reset, then reflash 10.1 and the latest 4.2.1 gapps.
Unfortunately you will lose your data doing this. I flashed a clean update. If you flashed a dirty update, it can cause problems.
Good luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RPelham said:
I have not yet seen anyone else report this bug. I am running the 12/23 cm10.1 as we speak and have no issue with the play store or super user. I would recommend to wipe cache, dalvik, and factory reset, then reflash 10.1 and the latest 4.2.1 gapps.
Unfortunately you will lose your data doing this. I flashed a clean update. If you flashed a dirty update, it can cause problems.
Good luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply!
Forgot to mention in OP post, I did do all that a couple times. I do have latest Gapps.
As stated above , my note 2 recently stopped me from downloading anything from the app store. So i cleared the data ,cache and uninstall the updates and made it worst. Now it just force closes. Hence, is there any simpler way to get play store to work again without factory reset?
Your help is much appreciated
Sent from my GT-N7105 using xda app-developers app
There are plenty of PlayStore Zip-files for flashing floating around here in the forums. Did you try that as well? You could also just try to flash your ROM again, without fullwipe, just cache and dalvik.
Martux76 said:
There are plenty of PlayStore Zip-files for flashing floating around here in the forums. Did you try that as well? You could also just try to flash your ROM again, without fullwipe, just cache and dalvik.
Click to expand...
Click to collapse
Sorry for not informing that my device is not rooted and is still in its stock rom.Prefer not rooting my phone.
Sent from my GT-N7105 using xda app-developers app
I got the rom AOKP and when I try to open Google voice it force closes please help I have tried everything and read online and can't figure it out
Sent from my GT-N7105 using xda app-developers app
I would. Go into twrp.
Wipe system.
Flash ROM
Flash gapps
Flash any addons you may have (optional)
This should fix your issue.
If not you may be using the wrong gapps.
Just wiping system and then reflashing the same ROM with gapps will not wipe anything. It will act like you never wiped or flash. The second you wipe data or factory reset. Etc. It will lose installed apps. Or data. Or if you wipe data media you will wipe everything. But just invade always back up photos before reflashing.
Another option is to force uninstall via titanium back up Google now. And then installing it from scratch.
Sent from my GN2 using XDA app.
I got it u have to go to the play store and serch google voice and update it
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I'm not sure how or why but recently, my apps have been forced closing. I'll be on my phone when suddenly every app in the background is closed. It is really annoying and I can't figure out how to stop it.
Die anyone have any experience worth this problem?
Sent from my SPH-L710 using Tapatalk 2
What rom?
Did you flash the correct version of gapps for your rom (if AOSP)?
Did you restore and data?
A full wipe and clean flash from your previous rom?
Removed apps on stock rooted that you shouldnt have?
All of that is if you're rooted, if not, since when has this been happening? Installed any new apps recently? Changed any important settings recently?
Rooted pacman rom, Android 4.1.1
I wiped data and cash in recovery.
Restored apps via titanium backup like usual.
This only started recently (that I noticed).
All I can recall would be deleting the Gemini virus and updating android tuner.
Cheers.
Sent from my SPH-L710 using Tapatalk 2
2Beastmode4u said:
Rooted pacman rom, Android 4.1.1
I wiped data and cash in recovery.
Restored apps via titanium backup like usual.
This only started recently (that I noticed).
Cheers.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Did you restore any Data? Did you restore any system apps? Did you restore any System App Data? Any or all of these can cause issues.
TEAM MiK
MikROMs Since 3/13/11
I restored user app and data with one system app (paranoid preferences).
I took a look at my logs and found this image *attached*
What ever activity 628 is, it likes to kill all background apps. Anyone know how to backtrack the app?
Sent from my SPH-L710 using Tapatalk 2
You have several options. Option one which is what I would do. Is to do Full Wipe. Then Flash the Rom again. Without restoring any apps, or data. Let it settle, and see if all the FC issues are resolved. Option two is Boot into Recovery, Wipe Dalvik, Wipe Cache, Fix Permissions, and reboot. Option three is Wipe Data, and Cache for all the apps you restored. Then reboot.
TEAM MiK
MikROMs Since 3/13/11
I've always wondered, what is fixed permissions?
Sent from my SPH-L710 using Tapatalk 2
2Beastmode4u said:
I've always wondered, what is fixed permissions?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
RW-R-R. The app has to have those permissions set or it will not work correctly. I use Root Explorer to set and fix my permissions. It all makes a lot more sense when you see it yourself.
Here is an example:
Sent from my SPH-L710 using Tapatalk 2
2Beastmode4u said:
I've always wondered, what is fixed permissions?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
System apps need to have certain permission set on them...so do things in /system/xbin and /system/bin and in other places
Fixing permissions set the correct permissions on everything so that there are no issues
It can be done in Recovery. It is in the advanced menu.
TEAM MiK
MikROMs Since 3/13/11
Fixing permissions can fix many force close issues. I'd recommend you do what prboy1969 said and wipe cache and dalvik-cache, fix permissions, and tell us the results. If that doesn't work, there's something else going on, like voltage problems with an overclock.
I'll give it a go and report back. Wish me luck.
Thank you to all of you for your help. This is why I love this community.
Cheers.
Sent from my SPH-L710 using Tapatalk 2
I decided to flash on an update to the rom so we'll see how this is goes. If it force closes I will wipe cache and fix permissions.
Though I want to ask about a separate problem all together, battery life. Before et rooting, I had 9 hours plus of battery life, now I barely get 7. I lose 30% of my battery in two hours. How does that work?
Cheers.
Sent from my SPH-L710 using Tapatalk 2
2Beastmode4u said:
I decided to flash on an update to the rom so we'll see how this is goes. If it force closes I will wipe cache and fix permissions.
Though I want to ask about a separate problem all together, battery life. Before et rooting, I had 9 hours plus of battery life, now I barely get 7. I lose 30% of my battery in two hours. How does that work?
Cheers.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
How much screen on time? If you have very little screen on time, try using Better Battery Stats to find out if there is a wakelock that could contribute to screen off battery usage.
Just recently flashed an emailfix.zip for AOSP and all of a sudden my exchange email on TW based ROMS don't work but they do on AOSP for Liquid Rom 2.8 does. I have tried wiping and factory reset in recovery and exchange account keeps re-loading. I've tried Wicked Sensation 4.1, Goodness Reborn, even the MD4 stock debloated by Freeza. Wondering if anyone knows how to fix this or has ran into this issue?
Where did you get this email fix file? I'm assuming it's messed something up in your /system partition.
You can try wiping /system in recovery prior to flashing a new Rom.
Sent from my SPH-L710 using xda app-developers app
I'm using latest TWRP recovery and tried wiping system under advanced wipe as well as cache, dalvik cache, data and system still no luck. It's weird.
Sent from my SPH-L710 using xda premium
Buddy the zip I provided just replaced the exchange email apk under /system/app if you mounted and wiped correctly it should of been erased when you wiped but if you want to test if it's my apk what you could do is push a other exchange apk from any 4.2.2 ROM and and copy it to that location using e's file explorer or any root explorer but it honestly should of been deleted when you wiped or even dirty flashing should of replaced it so maybe it's your Microsoft account that's not connecting but no way my zip fix which is old by the way should of messed with you across multiple roms
Sent from my SPH-L710 using Tapatalk 4 Beta
Thanks hope you don't think I was placing any blame its working now might be Microsoft issue as you suggested I'll check tomorrow at work.
Sent from my SPH-L710 using xda premium