Alright, so when i clean install a ROM, I'm able to access King.com's apps (Candy Crush, so forth) download them no problem so on. The only changes i make to my phone from that point is changing the DPI from 480, to 420, restoring only user apps via Titanium and switching runtime to ART. And while neither change immediately effects Candy Crush and its availability on the Play store, within the next couple hours, i don't know exact cause i went to bed this most recent test, something triggers the Play Store to believe Candy Crush, and affiliate games are not compatible with my Nexus 5. I can't even pull it up within Play Store, i have to google it, and click the link directly to it on the play store, where it says im not compatible with the version.
Now i can still play the games, having the apk already on my phone, but i can't update them, or download any of the new games, and i don't know if this might be happening with more apps, just having me unaware of such an issue.
I've tried two different Roms, both Cataclysm, and Purity, and the issue has effected them both. I've even gone as far as clean wiping my entire phone, and pushing a rom back via ADB to have it clean of -everything-.
Is this a issue anyone else is having? Does anyone think it could have to deal with ART? Or is it something else that is making the Play Store believe the newest phone on the market is incapable of it's most popular game.
I think the next attempt I'm going to clean install again, and run Davlik for a day, to see if it happens again.
Change your DPI back and it should work. There is a xposed mod that always sends a fake DPI to Google play to prevent this.
Typed on the Nexus
Related
I have an r800x which I cant seem to download some simple apps that shouldent have issues. very simple games like tiny tower can be installed via .apk but when searched in play store it comes up with an error. This is just one example. The "Your device isn't compatible with this version." on store is annoying when I have to go find the apk from somewhere else..
I've read about lcd density changers but I don't think its changed. I also unlocked bootloader and flashed custom kernel with custom rom a week previous to this disappearing apps in store problem. Also a friend is having same problem with his locked/rooted r800a.
In short I want to see ALL apps in the play store for every device regardless of compatibility or a way to remove the error.
Here are a couple things you can do:
-Try the app ChainFire3D. It is free but there is also a paid version which may help you more. It has an option to attempt to patch the market to show apps that may not appear for your device (again, not sure if the free version has this, but worth a shot).
-You can also try to go to Settings>Apps>All apps, then look for Google Play and wipe the cache; then try to search for apps. On another note, I once had this same exact problem. It was due me changing my screen density. I changed it back to 240, wiped Google Play data, then it worked beautifully.
- If you still have an issue, try getting an app that will allow you to change your density and try the level 240 (I think it is the same on all devices). Then wipe Play's data and try.
chainfire3d was one of the ones not compatable so I couldent download it easy from market or I would have tryed it. thx tho
I used an lcd density changer pro app to goto the 240 and that seemed to fix the problems. For some reason it was on 210. ty.
I posted this on another tech forum too, but I am looking to anyone and everyone for answers before I go crazy.
I have an HTC Wildfire S, currently with version 4.2.2 Jellybean. This error has been pestering me ever since my first ICS ROM 4.0.4. I have tried numerous versions of gapps, numerous resets. This has come to happen daily no matter what I do. It only affects the Play Store. I have endlessly searched online and tried different things to no avail, now across 3 Android versions built by different developers. It got worse as of 4.1.2 and is no better in 4.2.2. Using the standard gapps flashables and the built in one to the 4.1.2 ROM, this error will come daily out of nowhere. Usually it shows when I open the Play Store or when I try and run a paid app. In that case(running paid app), it will get so relentless that I can't do anything with my phone but clear dalvik and reboot. It will stop any work I am doing with the constant error. Clear data no help. Force stop just has it restarting on its own. Clear cache no help. Clear Google Account no help. Only clearing the dalvik like a good little girl and rebooting clears it for a little while and lets me use paid apps and the Play Store, only to have it resurface hours later. Reflashing gapps, even after totally wiping them only does about as much as just clearing the dalvik cache. In desperation, since it seemed to mostly happen when launching paid apps, I tried a Play Store with the licensing system hacked. Besides being able to launch my BOUGHT apps offline(like offline games should be able to), this offered 1 improvement. I no longer have it flash up randomly during work with other apps or when launching a paid app. But, I do still have it come up as soon as I try and launch the Play Store in about the same amount of time. The temporary cure: same thing. At least I am not forced out of other apps. My guess is the hacked version does not make the crashing library load to check the license online, hence this improvement. But it still sucks when I want to install or update an app. I would have quit the Play Store and bought from Amazon and others if I have not already paid for so many apps over time I can't use or update without it.
Given I have got it so that it only happens when I launch Play(with hacked Play Store only, otherwise the random relentless error happens(usually when launching or working with a paid app) with any normal version of Google Apps and Google Play in addition to when I launch Play), I am about to either become a pirate and install black market(can have paid apps and avoid launching Gay Store, which would avoid this with the hacked Play Store as unlike the regular builds, it only happens when I actually launch Play) or get an iphone. After over a year, I am just so sick of this error and it's driving me loony. Have never found an answer to it or a fix when searching online. Nor have I been able to trace or figure out why this is happening. Only common thread(besides the hardware) is the ROMs are all stable CM builds, but different Android versions and different developers. I hate to become a pirate to solve this, but I am at wits end and really don't want Apple. I just want something stable, which my setup otherwise is, except for the Play Store. Again, clearing the dalvik cache is the only thing that lets me use it again, but the error will rear its ugly head again anywhere from hours to a day or 2. Please help me. Piracy is not a good fix but iphones are even worse. I will not pay for all my apps again through Amazon. That is just not an option for me, with money being tight and all. The only reason I would consider splurging on an iphone is so I never lose an investment due to a faulty appstore again and to punish Google for this miserable failure by handing over no more money to them.
Selenia said:
I posted this on another tech forum too, but I am looking to anyone and everyone for answers before I go crazy.
I have an HTC Wildfire S, currently with version 4.2.2 Jellybean. This error has been pestering me ever since my first ICS ROM 4.0.4. I have tried numerous versions of gapps, numerous resets. This has come to happen daily no matter what I do. It only affects the Play Store. I have endlessly searched online and tried different things to no avail, now across 3 Android versions built by different developers. It got worse as of 4.1.2 and is no better in 4.2.2. Using the standard gapps flashables and the built in one to the 4.1.2 ROM, this error will come daily out of nowhere. Usually it shows when I open the Play Store or when I try and run a paid app. In that case(running paid app), it will get so relentless that I can't do anything with my phone but clear dalvik and reboot. It will stop any work I am doing with the constant error. Clear data no help. Force stop just has it restarting on its own. Clear cache no help. Clear Google Account no help. Only clearing the dalvik like a good little girl and rebooting clears it for a little while and lets me use paid apps and the Play Store, only to have it resurface hours later. Reflashing gapps, even after totally wiping them only does about as much as just clearing the dalvik cache. In desperation, since it seemed to mostly happen when launching paid apps, I tried a Play Store with the licensing system hacked. Besides being able to launch my BOUGHT apps offline(like offline games should be able to), this offered 1 improvement. I no longer have it flash up randomly during work with other apps or when launching a paid app. But, I do still have it come up as soon as I try and launch the Play Store in about the same amount of time. The temporary cure: same thing. At least I am not forced out of other apps. My guess is the hacked version does not make the crashing library load to check the license online, hence this improvement. But it still sucks when I want to install or update an app. I would have quit the Play Store and bought from Amazon and others if I have not already paid for so many apps over time I can't use or update without it.
Given I have got it so that it only happens when I launch Play(with hacked Play Store only, otherwise the random relentless error happens(usually when launching or working with a paid app) with any normal version of Google Apps and Google Play in addition to when I launch Play), I am about to either become a pirate and install black market(can have paid apps and avoid launching Gay Store, which would avoid this with the hacked Play Store as unlike the regular builds, it only happens when I actually launch Play) or get an iphone. After over a year, I am just so sick of this error and it's driving me loony. Have never found an answer to it or a fix when searching online. Nor have I been able to trace or figure out why this is happening. Only common thread(besides the hardware) is the ROMs are all stable CM builds, but different Android versions and different developers. I hate to become a pirate to solve this, but I am at wits end and really don't want Apple. I just want something stable, which my setup otherwise is, except for the Play Store. Again, clearing the dalvik cache is the only thing that lets me use it again, but the error will rear its ugly head again anywhere from hours to a day or 2. Please help me. Piracy is not a good fix but iphones are even worse. I will not pay for all my apps again through Amazon. That is just not an option for me, with money being tight and all. The only reason I would consider splurging on an iphone is so I never lose an investment due to a faulty appstore again and to punish Google for this miserable failure by handing over no more money to them.
Click to expand...
Click to collapse
Full wipe should have been done between different dev's roms.
Then flash your favorite rom and start from scratch with everything.
It will fix your error definitely.
Lgrootnoob said:
Full wipe should have been done between different dev's roms.
Then flash your favorite rom and start from scratch with everything.
It will fix your error definitely.
Click to expand...
Click to collapse
Thanks for trying but definitely not. I full wipe before every flash of a new ROM and even did it a few times and reinstalled the last 2 ROMS to no avail. Seems to fix it a bit longer than wiping dalvik, but inevitably, the error comes back within days. This is even without restoring my Titanium backup and reinstalling apps from scratch via Play. But again, thank you for being the first to try. But I do know to full wipe /system, /cache, and /data, and sd-ext before even restoring backups, let alone a new ROM install. I do this in TWRP 1 partition at a time then flash or restore(whichever applies) then usually wipe dalvik after for good measure
Selenia said:
Thanks for trying but definitely not. I full wipe before every flash of a new ROM and even did it a few times and reinstalled the last 2 ROMS to no avail. Seems to fix it a bit longer than wiping dalvik, but inevitably, the error comes back within days. This is even without restoring my Titanium backup and reinstalling apps from scratch via Play. But again, thank you for being the first to try. But I do know to full wipe /system, /cache, and /data, and sd-ext before even restoring backups, let alone a new ROM install. I do this in TWRP 1 partition at a time then flash or restore(whichever applies) then usually wipe dalvik after for good measure
Click to expand...
Click to collapse
Any more ideas? I never said this would be easy. In fact, the fact I posted here suggests that it will not. I am experienced with Linux systems and troubleshooting thereof and generally pretty good with Androids and modding. I love helping people but despise asking questions of others and only do so in desperation. Usually content to troubleshoot and lookup info myself and always been that way. But I feel I have reached a dead end, so now I call upon a forum I see as loving challenges to hopefully bail me out. Thanks again, guys. Note:had this issue with 1 other device that dropped dead before I could troubleshoot: a Pantech Burst, also with ICS and JB(was fine on GB as was this HTC Wildfire). It also had no other issues outside of a few minor things listed under bugs for its ROM, just like this phone.
Selenia said:
Any more ideas? I never said this would be easy. In fact, the fact I posted here suggests that it will not. I am experienced with Linux systems and troubleshooting thereof and generally pretty good with Androids and modding. I love helping people but despise asking questions of others and only do so in desperation. Usually content to troubleshoot and lookup info myself and always been that way. But I feel I have reached a dead end, so now I call upon a forum I see as loving challenges to hopefully bail me out. Thanks again, guys. Note:had this issue with 1 other device that dropped dead before I could troubleshoot: a Pantech Burst, also with ICS and JB(was fine on GB as was this HTC Wildfire). It also had no other issues outside of a few minor things listed under bugs for its ROM, just like this phone.
Click to expand...
Click to collapse
How 'bout the forum here for the wildfire s?
So this happens even if you run completely stock with no user installed apps? (Other than CM?)
Your s-off right?
Lgrootnoob said:
How 'bout the forum here for the wildfire s?
So this happens even if you run completely stock with no user installed apps? (Other than CM?)
Your s-off right?
Click to expand...
Click to collapse
Not S-Off, which was deemed impossible with Wildfire S at the time I started flashing ROMS. Bootloader is unlocked, however, which is said to be good enough for flashing from zip files. All changes I make to /system from TWRP stick permanently. As to whether I had the issue on GB, didn't as far as I left it on there, which was not long at all. Just a matter of days. I loathed the stock Sense 2.1 ROM and only bought this phone off my friend because it was very capable of being modded, otherwise, I would have passed, even at $25 I paid over a year ago. The other phone with same issue started the issue with stock ICS, which continued with custom ROMs. I mention this because that phone had no secuflag. Just a locked bootloader that was easily hacked to unlocked. All root apps do their job with no issue and all my added init scripts(mostly for internet tweaking, etc) stick.
Selenia said:
Not S-Off, which was deemed impossible with Wildfire S at the time I started flashing ROMS. Bootloader is unlocked, however, which is said to be good enough for flashing from zip files. All changes I make to /system from TWRP stick permanently. As to whether I had the issue on GB, didn't as far as I left it on there, which was not long at all. Just a matter of days. I loathed the stock Sense 2.1 ROM and only bought this phone off my friend because it was very capable of being modded, otherwise, I would have passed, even at $25 I paid over a year ago. The other phone with same issue started the issue with stock ICS, which continued with custom ROMs. I mention this because that phone had no secuflag. Just a locked bootloader that was easily hacked to unlocked. All root apps do their job with no issue and all my added init scripts(mostly for internet tweaking, etc) stick.
Click to expand...
Click to collapse
I just think that it might because of tweaking.
Partly right. I wiped the phone. Reapplied basic tweaks and was fine. So before letting it pull all my apps back in, I fired up a cheap Chinese tablet that is often used as a victim to my experiments. I installed my previous apps 1 by 1, as this tablet never had the issue. Went on a sudden hunch I had and set Cache Apps to SD Card up and let it run as it binds all app caches. Let it go overnight. In the morning, BAM! Play Store was stopping. Restored apps on my Wildfire S but used a shell script I wrote instead of that app. No Play crashes all day. Funny it probably caused it on my Burst too(RIP). I used the app on several GB phones with no issue but either a Play update, an update to the app, or ICS+ cause this app and Play not to play well. This app does not have many settings to try and fix it. Thus I would avoid that app until further notice. Funny how it's on Play but crashes Play
Sent from my Wildfire S A510e using xda app-developers app
So, I have a TF101 that I had rooted and played around with.. tried kitkat, ICS, etc... Now I have something else, and I want to give this tablet to someone else.. but I want it to be unrooted, stock rom. So, I flashed it back to factory and reset it. The needs of the next user are extremely simple, so stock should work fine...
...however, I can't get Google Play Store to work at all. I've done much research, and some say to just wait 3+ days for google play services to update itself, etc. no dice... I left it plugged in and running, checking each day to ensure it was still connected to wifi so that it could do whatever it needed to do. Nope. I found a thread on another webforum where someone described the exact problem, then at the end he said "problem solved, thank you" without actually describing what happened. Sad. sigh.
I've noticed that google play services isn't even on the stock firmware. instead, it's called google play framework. Perhaps that's part of the problem? I dunno.
I tried downloading the most recent version of google play services and manually installing the APK, but that didn't work either, google play store keeps crashing. Perhaps I need to also download a few more APK's go go along with it, but I need help identifying what is current.. or at least, I need to identify one recent enough that it can then update it self to current.
So.. I'm stuck. Can someone point me in the right direction to try to bring this fully STOCK TF101 up to at LEAST a version of google play store that works? APKs? tweaks?
Flashing to a custom rom is my LAST resort. I don't need any help doing that.. but I want to try to make Stock work again first.
BTW, that original Youtube app from stock all those years ago... it was pretty cool looking now I'm stuck with it.
Use Easyflasher:
http://forum.xda-developers.com/showthread.php?t=1688012
This will put it back to factory new condition and remove Root.
Sorry if I wasn't clear. I have successfully flashed the unit back to stock rom and completely wiped and reset to factory. then I turned it on, and google play store won't run. I want to install apps normally.
Trimbleepic said:
Sorry if I wasn't clear. I have successfully flashed the unit back to stock rom and completely wiped and reset to factory. then I turned it on, and google play store won't run. I want to install apps normally.
Click to expand...
Click to collapse
I had the same problem.
I found the newest playstore on internet and installed it.
Then I had no problems anymore.
That seems to have worked! I had assumed I would need to update google play services first, but apparely I just needed a new Google Play Store APK. I found one that works here: http://www.apkmirror.com/apk/google...google-play-store-6-0-7-android-apk-download/
I downloaded the APK and ran it, and the play store now runs and is updating all other apps on the old TF101. Sweet.
Dunno if Google Play Framework will automatically replace itself with Google Play Services or what, but I'll keep an eye out for that.
Just to followup and close this topic... The tablet is now up and running with multiple apps from the play store, and my wife is now using it to read kindle books and mess with her nursing app. I was planning to give it to her mother, but she intercepted it when it started working
So, basically - if you want to go back to stock firmware - flash to stock, factory reset, then download and install current playstore (as per link above) and don't worry about Google Play Services, it will sort itself out.
Hey guys,
I'm going mad here on a problem with a specific app.
It's the Harman Kardon Controller App.
I have to use this apps to stream music from my new two HK Omni 10 speakers and in order to configure them as a stereo pair.
As you can see from the reviews on the Play Store, HK totally screwed up the software.
It was hard enough to configure the speakers one time, but now they released an update, that makes it impossible.
There are older versions of the software which you can download from certain other apk-hosting-sites.
With these older versions configuring the speakers is possible again, but now there is a prompt, whenever opening the software, saying 'new software is available' (wanting me to update to the new version that's gonna screw everything once again).
Now, the problem is: Everything else but excepting to update that app is greyed out, so you just have to do it or find a way to trick around it.
Of course I went for the latter
Tried:
- Giving the apk an own signature with ZipSigner
- removing the app from Play Store, there disabling auto-updates, clearing Play Store's data and cache
- wiping dalvik and cache in recovery
- reinstalling the app (from an apk - not from the Play Store)
- before opening it, detaching it from Play Store via Titanium Backup Pro
But none of all these things worked.
Everytime the ****ing prompt shows up again.
The app now isn't shown under My Apps in Play Store, though.
And when pressing on "update now" it doesn't find the new version, but the same one installed at the moment instead
(So I only found a way to making updating impossible, not to prevent the app from checking for updates).
Can you guys think of any way to move around that?
I mean, I assume it still finds the update looking in the Play Store, but still I can't see how.
Maybe it has got something like an update checker on its own?
Maybe just a built-in mechanism to destroy itself for the sake of forcing to using the new update?
Any idea and help is much appreciated!
Edit: Solved.
Had to include a firewall (droidwall) to forbid internet access when opening the program, and then allowing it again, when being in another menu.
Afaik, It happens to me (on more than one smartphone, LP and Marshm.) when play store updates itself.
I have tried deleting cache for play store and play services, removing account, rebooting, even resetting play store to factory.
One thing I noticed is that while the app is at 100% it will install right upon closing the play store (meaning out of background).
So I wonder whether this may be a clue on what is causing trouble and how to fix it.
HeyRicardo said:
Afaik, It happens to me (on more than one smartphone, LP and Marshm.) when play store updates itself.
I have tried deleting cache for play store and play services, removing account, rebooting, even resetting play store to factory.
One thing I noticed is that while the app is at 100% it will install right upon closing the play store (meaning out of background).
So I wonder whether this may be a clue on what is causing trouble and how to fix it.
Click to expand...
Click to collapse
Since this is not how it should work, given the fact that you are having this issue on more than one device, this tells me that the issue isn't with the device or the apps, it is more likely an issue of user error or things that you have modified on your device.
Are you using stock ROM or custom ROM?
Are you using modified Google apps?
Have you tried factory resetting the device itself instead of resetting the Google apps?
Sent from my LGL84VL using Tapatalk
Droidriven said:
Since this is not how it should work, given the fact that you are having this issue on more than one device, this tells me that the issue isn't with the device or the apps, it is more likely an issue of user error or things that you have modified on your device.
Are you using stock ROM or custom ROM?
Are you using modified Google apps?
Have you tried factory resetting the device itself instead of resetting the Google apps?
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I pointed out the fact it happens on more than one (even tablets with 5.1) just to rule out the fact it may depends on a specific device.
But let's talk of a specific device, as right now the problem is persistent on one, running 6.0
It's stock and not rooted. No modified apps.
The only thing I feel worth bringing up to the attention is AppMgr III and that the 2GB SD is used as internal storage (not portable), though reports on available storage are inconsistent (see here).
I observe also a slight higher battery consumption than when things work smoothly, however I can not blame any specific app, I don't see anything (I assume because it's due to something wrong with android itself).
Now, fixing via factory reset is painful but I can't do it every play store update, if that's the case (I assume it will work, as everything used to work very well).
Another thing I may throw in is some problem (?) with nova launcher (prime), but again I didn't any crazy thing, so I go blind about it.
Thanks for your kind attention, ricardo
As a workaround I have been able to seamlessly update apps by entering safe mode. On two different devices.
I don't think I'll ever succeed and work out the reason why it's stuck on normal mode.
Just to tell, the tablet updated playstore on march 3rd. Then on march 10th I turned it back on and there was another playstore update (it says it will be installed), but it never does, and so does it for apps. So I could not have done anything in between, and I can assure I care so much to the (reading) tablet that I just install needed apps and verified and tested on other devices before installing on my tablet. It's definitely a problem with play services (interacting with chinese devices, could it be relevant?)
(duplicate post)