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
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
Hey everyone, just wondering if anyone out there has a previous version of Yatse remote available I can install on my N5.
Briefly, I installed a bunch of updates (about 5) the other day, Yatse being one of them. Since that time I have experienced numerous reboots and boot loops where the only way that to get back into my device has been to clear cache and Dalvik. Yesterday I was unable to get into recovery or fastboot mode at all with the device and it just kept rebooting at Google logo. Since that time I have removed all of the updates and reinstalled one at a time to attempt to figure out what would break it. Yatse is the first app that it began to reboot with so I suspect that the problem lies there however as I can't reproduce the issue reliably or get a log for it yet there's no point in me filing a bug report.
I use Yatse regularly and want to see if downgrading helps. Unfortunately the developer does not have or can't provide a previous version. The version in the play store is 4.1.5 arm v7. I hope this doesn't violate rules. To be clear, I'm just looking for the APK of the last free version, same is available on play store. I purchased the "unlocker" and love the application. Just want to be able to use it/see if it might be the culprit here.
Sent from my Nexus 7 using Tapatalk
Hey Guys,
Noticed several people complaining on various forums and on Play Store as well that the recently released version of Crossy Road for Android is crashing repeatedly on rooted Nexus devices as well as rooted devices running Cyanogenmod. The fix is actually quite easy.
1. Boot to TWRP (Team Win Recovery Project) recovery.
2. Go to Wipe > Advanced Wipe.
3. Select ONLY "Wipe Dalvik Cache" and slide slider to begin.
4. Back out to main menu and select Reboot > System.
After this you should get a screen that says "Android is upgrading" or something similar with an App count. After this "upgrade" process your beautiful Crossy Road should work exactly as expected!
Horray. Now go get all those precious unlocks ^_^
did not work for me
whipping said:
did not work for me
Click to expand...
Click to collapse
Sad times I was testing on LG G2 VS980 running CM12 ... sorry it didn't work for you. Back to the drawing board I suppose
Not working :\
Do you have adblockers installed? I noticed Crossy Road would crash for me when my adblock was enabled. I reverted my host file and it started working fine.
.
It works without a Adblocker, I had the same issue.
Edit: If you delete the ads and make the app offline with luckypatcher, it will fully work with adblock.
.
rooted nexus 5 with custom rom, no ad blocker installed. still crashes everytime either directly after the developer logo or after a couple seconds in the game.
/edit:
ok i just ran an app to check if there are any adblocks on my device, thinking the rom itself might have it. it seems to be the case, disabled it, but not crossy road doesnt force close, but crashed with "unfortuntely, crossy road has stopped"
/edit 2: ok, a restart seems to have fixed the issue.
Nexus 5, CM12, Adfree Adblocker and CR from Amazon App-Shop = never had any problems!!!
Play Store version still fc...
How do i make the app offline with luckypatcher?
I could get the Yodo logo then it would crash before the hipster whale would show. I emailed the developer to find out what addresses to whitelist but haven't heard back yet.
Checking the syslog I noticed something going to service.sponsorpay.com.
Removed service.sponsorpay.com from my hosts file and no more crash.
install from Amazon Apps. but that version is not support "google play games"
Ended up using xprivacy and disabled internet permission and no crashes so far. On moto x 2013.
Thanks for that
As many of you know, bliss os 14.3 and it's variants usually have mixed results regarding wifi/BT connectivity, depending on your device(s), which in turn makes it nearly impossible to get the most out of the OS in most cases. I can't say for certain that this is a % fix/workaround, but, I wanted to share with you all in case this helps you get your OS up and going to your liking.
By default, Google play services loops or FC's out of the box. So I went out of my way on a working pc to DL from "apkpure" a current/up to date version of said apk, as well as the Play store, FX viewer and chrome. Then, I put them on a trusty usb, xferred them onto the laptop I use with 14.3 currently and just installed them all without running any of them afterwards. Next, I rebooted and then opened the play store and I was able to log into my account and start updating/installing apps as normal. Hopefully, this helps you all out too because I'm loving my laptop now and I'd be glad to help ya'll out too if I can. If someone can recompile bliss os images properly to include out the box current versions of Google service I'd love to hear from ya.
I also updated all apps but the problem still exists.