Hi all,
running ICS on my sensation, just bought a few app today, no issues, just downloaded and installed nicely. No, i did a factory reset and installed a update for the ICS rom, and now i'm only seeing half of my paid apps under my apps in the market.
Can't search for them either. Paying for apps, and then not be able to redownload them... any advice on this ?
Presumably the missing half of your apps are flagged as incompatible with your newly flashed ROM software and are being suppressed from display.
I'm being absolutely plagued by error code 923 on my Nexus S vanilla ICS 4.0.4 rooted.
It seems to have started after the last update from 4.0.3. I've been all over the google and every forum I can find looking for solutions.
So far I've:
Deleted Google Play and reinstalled (rebooted)
Deleted all my accounts and put them back (also rebooted)
Followed this (although I don't see "Market Updater" on my phone):
getsatisfaction.com/omgpop/topics/error_923
Next step is a wipe and new ROM. Don't really feel like going to that kind of effort though, everything else works perfect.
Help!
psy-q said:
I'm being absolutely plagued by error code 923 on my Nexus S vanilla ICS 4.0.4 rooted.
It seems to have started after the last update from 4.0.3. I've been all over the google and every forum I can find looking for solutions.
So far I've:
Deleted Google Play and reinstalled (rebooted)
Deleted all my accounts and put them back (also rebooted)
Followed this (although I don't see "Market Updater" on my phone):
getsatisfaction.com/omgpop/topics/error_923
Next step is a wipe and new ROM. Don't really feel like going to that kind of effort though, everything else works perfect.
Help!
Click to expand...
Click to collapse
I realized I was a little vague. It happens when I update apps in Google Play. Doesn't matter if I'm using 3G or Wifi and turning the screen off makes it happen a lot quicker. If I sit on the update screen and watch it, then it will usually work, but only one app at a time.
psy-q said:
I realized I was a little vague. It happens when I update apps in Google Play. Doesn't matter if I'm using 3G or Wifi and turning the screen off makes it happen a lot quicker. If I sit on the update screen and watch it, then it will usually work, but only one app at a time.
Click to expand...
Click to collapse
Nobody else has this issue? I'm pretty desperate
I went ahead and did a factory reset. For anyone else who stumbles along here from Google or elsewhere: YOU'RE DOOMED! There is no hope for the accursed 923 error. DOOOOOOOOOOOOOM.
After flashing to cm10 on my ns4g i was unable to download from the market(getting error 927). I bypassed the market app, used the browser to download titanium backup from the web site, restored my backup and all is good downloading off the play store app.
To sum it up, if you're still having issues there is still the play store web site. Hope that helps.
Edit: i also tried all the fixes here on xda for that problem. None of them worked until i used the web site.
Sent from my Nexus S 4G using xda premium
Hi,
I recently migrated to Nexus devices. I have a Nexus 5. Recently, while I am working with my phone, the play store suddenly opens to a random (usually Korean) app. I say Korean because the dev's website ends with'.kr' and the language looks like one of the East Asian languages (I am sorry but I cannot differentiate them very well).
I notice this usually happens when I am back to my home screen.
I suspected Ads and I have downloaded Ad Away and made sure I am running the most recent updates. I even installed Ad Network Detector by Lookout and even uninstalled some apps I suspected. But it still pops up.
This issue happens also on my Nexus 7 2013 (running rooted stock 4.4 and stock kernel - Dalvik runtime). Now there is an overlap of apps but they are not exactly the same.
Please note that I am running rooted stock 4.4 with custom kernel on my Nexus 5 (ART runtime). I have not updated play store manually. Everything is as is from Google. And the play store version is 4.4.22.
One last thing, yesterday, I noticed the same type of "ads" on my wife's galaxy s2 running Jelly Bam v10. There is very little overlap in terms of apps.
This is a very annoying form of ads. Anyone experienced this? And if so, any workarounds? I am trying to avoid a factory reset if possible.
I appreciate your help.
ash_arani said:
Hi,
I recently migrated to Nexus devices. I have a Nexus 5. Recently, while I am working with my phone, the play store suddenly opens to a random (usually Korean) app. I say Korean because the dev's website ends with'.kr' and the language looks like one of the East Asian languages (I am sorry but I cannot differentiate them very well).
I notice this usually happens when I am back to my home screen.
I suspected Ads and I have downloaded Ad Away and made sure I am running the most recent updates. I even installed Ad Network Detector by Lookout and even uninstalled some apps I suspected. But it still pops up.
This issue happens also on my Nexus 7 2013 (running rooted stock 4.4 and stock kernel - Dalvik runtime). Now there is an overlap of apps but they are not exactly the same.
Please note that I am running rooted stock 4.4 with custom kernel on my Nexus 5 (ART runtime). I have not updated play store manually. Everything is as is from Google. And the play store version is 4.4.22.
One last thing, yesterday, I noticed the same type of "ads" on my wife's galaxy s2 running Jelly Bam v10. There is very little overlap in terms of apps.
This is a very annoying form of ads. Anyone experienced this? And if so, any workarounds? I am trying to avoid a factory reset if possible.
I appreciate your help.
Click to expand...
Click to collapse
I'm glad that I found this as the same thing has been happening on my N5.
Cataclysm, Faux and 'next' browser. Although I think it still happened in chrome. It seems to happen when I'm using a browser, the play store launches by itself to some random app.
I'd hate to think this is Google doing this to sell more crap....
it sounds like you both have a spam app installed...try Addons Detector in play store, or uninstall anything that is not absolutely reputable, and read reviews about apps
N5 TapTalk
n7of9 said:
it sounds like you both have a spam app installed...try Addons Detector in play store, or uninstall anything that is not absolutely reputable, and read reviews about apps
N5 TapTalk
Click to expand...
Click to collapse
It seems to have stopped since uninstalling the latest version of 'next' browser (beta 1.3).
I noticed that the issue would almost always arise when browsing, and since going back to my previous browser if choice (Boat) it hasn't happened since.
A real shame if it's indeed the browser, it had great promise and I was going to use it as my daily... But not if they are injecting crap like this into it.
Neither lookout adwatch nor airpush detectors picked it up, so it must be stealth.
I've emailed the devs asking if they have something like this in their browser, although I'm pretty convinced since it hasn't happened once since removing it.
Update:
It's not the browser, nor the one or two games I installed.
Tried several different ad and air push detector apps but can't find the culprit.
This is truly annoying, especially as I have very few apps installed beyond the stock Google ones.
Any help appreciated.
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
I've been running Temasek's unofficial cm12 builds for the Note 3.
Works great in general, but the amazon Kindle reading app doesn't function. This is quite a kicker as I was heavily invested in my kindle library.
The app breaks on downloads. Some books will appear to download to completion, then inform me that the download failed. Sometimes the app will break and throw a "has stopped working" as soon as the download is initialized.
Things I have tried:
Plenty of app data/cache wipes and reinstalls
Clean rom flashes
Uninstalling all other amazon products (research suggested potential conflicts)
But nothing has worked.
Amazon support refuses to help troubleshoot since it's cyanogenmod.
Any ideas?
I was also having this issue on my galaxy s4 i9500 running the latest Euphoria build. I did some searching on Google, and found a solution that worked for me. I used build.prop editor to reduce the Dalvik.vm.heapsize from the default (mine was 512 I think) to something lower (the site I found said to drop it to 402, but I set it to 470 and it works fine). This solution worked for me, but I claim no responsibility if this messes up your device in any way.