Hi Everyone,
I am currently using the latest CM build 13 (07/07/2016) and having some issues downloading Snapchat.
When I click on Snapchat in Playstore it just crashes.
I have wiped my phone and freshly installed the build again and same issue occured.
I thought it might have been the G Apps i installed so using the G Apps Open and G App base from CM both provided the same result no change.
I downloaded the snapchat apk and installed it that way but when i try to launch it snapchat crashes.
I am running out of ideas has anyone else ran into this problem ?
Running Correct Date/Time, Removed Cache and Data from Playstore, Snapchat, Play Services.
EDIT: I had to format everything on my phone (Backed up data of course) this has resolved the issue not sure why though.
I know with the TF101 droid tablet, running certain custom ROMs requires you to format the internal storage with a certain version of TWRP, otherwise the Play Store will error out
Related
Weirdest thing is going on in every single update I've been applying lately, let is be 7.2 official or KANG RC1, ICS nightlies or whatever (though I haven't reverted to the stable 7.1 just yet):
After a while, if not immediately, my market aka play store is unable to find me even the most trivial apps (such as YouTube). I AM able to install them after Googling and applying via Play Store, once prompted to select an action.
Is something going on that I'm not aware of lately?
My setup: internal install with data + cache + dalvik wipe
Maybe it is the telephone permission. Check Sam I am's ics nightly build thread.
Sent from my MB870 using xda premium
boyoboyo said:
Weirdest thing is going on in every single update I've been applying lately, let is be 7.2 official or KANG RC1, ICS nightlies or whatever (though I haven't reverted to the stable 7.1 just yet):
After a while, if not immediately, my market aka play store is unable to find me even the most trivial apps (such as YouTube). I AM able to install them after Googling and applying via Play Store, once prompted to select an action.
Is something going on that I'm not aware of lately?
My setup: internal install with data + cache + dalvik wipe
Click to expand...
Click to collapse
Go to applications and clear the cache on google play. Then clear the data on google services framework, and restart the nook.
That's what worked for me. Hope it helps
I have the same problem with Swiftkey Tablet X. I had it installed previously. I recently re-installed Kang's latest 7.2 after wiping. I also ran DizzDen's IMEI generator and V6 Supercharger. Swiftkey Tablet X was listed in the Play Store, but it said it was incompatible with my device. I cleared the Play Store cache, cleared the Google Services Framework data the rebooted. Now I can not find it listed at all. Any suggestions?
otaku91 said:
I have the same problem with Swiftkey Tablet X. I had it installed previously. I recently re-installed Kang's latest 7.2 after wiping. I also ran DizzDen's IMEI generator and V6 Supercharger. Swiftkey Tablet X was listed in the Play Store, but it said it was incompatible with my device. I cleared the Play Store cache, cleared the Google Services Framework data the rebooted. Now I can not find it listed at all. Any suggestions?
Click to expand...
Click to collapse
Are you doing any build.prop edits? I have used Samsung GalaxyS edits since before I included the ability in the IMEI Generator... never have market device visibility issues.
I haven't done any manual build.prop edits. I have installed a ROM fresh and used your IMEI app at least 30-40 times. (Thanks very much, BTW!) The only thing I have done differently than normal is run the V6 Supercharger script. This is the first time I have tried to install it since the Market has changed to Google Play, though.
It's another one of that question!
mine's SM-G900I, rooted, and not flashed with any kind of ROMs, so I'm using the original, TouchWiz, just rooted
I have both Freedom, and Installer Cracked Google Play
Freedom is turned off, and I'm using the Chelpus' Google Play, version 4.6.17
Google Play Services at 4.4.52 version,
and Google Services Framework at version 4.4.2 (it's in the application manager, running, but for some reason not in /system/app)
tried going to:
http://forum.xda-developers.com/showthread.php?t=2299947 - Fail, only modded GP is in my phone now, and with GSF situation like I described above
http://forum.xda-developers.com/showthread.php?t=1561960 - uninstalled with ES File, reboot then install mod / original, Fail
No SD card inside
Clear Cache + Data does not work either
anybody can help me?
So I did this once before and it ended up with a few apps force quitting on startup. Looking at a log cat it seems like they were unable to open android system webview I tried installing that form the app store with no dice.
Does anyone here know if it's possible to remove the google bloat and just install everything from the play store out of the things you need?
Stock OOS already has Google apps included. What exactly are you trying to accomplish by flashing Gapps over Google apps that are already installed?
This has worked with me GApps .
Hi everyone,
it seems the Play Store has got the same problem as years ago. After a clearing of cache and data, I have and empty installed app list and if I try to download apps bought time ago, they cost again.
I talked about the problem and it seemed to be related with detaching script on roms or apps like iytbp. No solutions found over the internet works (delete and readd the account, clearing cache partition, etc).
The only way to restore it was to restore back a previous titanium backup, data only, from a clean installation or from an uncleared play store.
It happened to me on XXX 9.1 but it's not rom related, 'cause it happened again on a clean installed stock Oreo 8.0 rom after installing iytbp with detach.plz method. But today a guy tried on a full stock Oneplus 5 and it happened the same (no root, no unlocked bootloader).
Can you please try if you have the same problem? After a Play Store backup, of course. I already sent a google feedback about that and, if you have the same problem, a google operator suggested to feedback them about that. Thanks in advance for the attention.
P.S. I tried the same on my Wiko Fever (full stock and updated) and it seems to have no problem at all. It also happended on Nougat, but I have not tested a lot.
Same issue here. I've also used the iYTBP detach script, you say it is caused by this? Have you found a solution? I'd rather not have to do a whole factory reset seeing as I don't have TB.
EDIT:
Found the solution to the problem for me. Not sure if this will fix it for good but for now Play store will update and installed apps show up. This solution requires root access. This is what I did:
1. Make full backup in TWRP.
2. Go to "system/priv-app/phonesky", cut the phonesky.apk (apk file for the Play store) file out of the directory to for example your documents folder.
3. Do a full (regular) reboot.
4. Copy the same apk you just move away form it's directory back to it's place (system/priv-app/phonesky).
5. Do another full reboot.
6. Wait about 30 seconds and the Play store should back on your device and functioning normally.
EDIT 2:
Issue where apps don't recognise that the user has purchased it still persists. After uninstalling the app and reinstalling it this issue got fixed.
After having enough with PE10, due to non working camera and stream apps I returned to original room 8.1
After reinstalling all looks like it is working fine, except the Google Play Store -> it is Completing Setup for the past 3 day's.
It says that will install 0 from 4 application, but it is not going forward. Has any one faced such issue?
ROM I have downloaded latest one from Google directly.
BTW, I have tried to installed it twice and the same issue, also I am typing from this Nexus, so in general all works but I cannot update anything....
Has anyone faced similar issue? I am not able to install any thing due to "freeze" Google Play Store....
I have inserted SIM card if that would help, but still the same issue...
It can be closed: I have clear cache and data. Force stop application. Then reopened and it started to work correctly.