Everytime I try to purchase an app or song or book from the market I get "An error has occurred. Please try again." Its been happening since about October. I've tried clearing the cache on the market, I tried factory resetting, I even tried wiping everything (sd and emmc included.) The log mentions something about mismatched uids.
HTML:
12-11 10:28:01.601 I/ActivityManager( 461): Starting activity: Intent { flg=0x20010000 cmp=com.android.vending/com.google.android.finsky.activities.PurchaseDialog (has extras) } from pid 1242
12-11 10:28:01.701 D/Finsky ( 1242): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping self-update. Local Version [8009011] >= Server Version [0]
12-11 10:28:01.741 I/ActivityManager( 461): Displayed com.android.vending/com.google.android.finsky.activities.PurchaseDialog: +123ms
12-11 10:28:01.831 D/Finsky ( 1242): [1] PageFragment.rebindViews: Page [class=PurchaseFragment] loaded in [89 ms]
12-11 10:28:01.841 E/Finsky ( 1242): [1] AppPermissionAdapter.<init>: Invalid group name:null
12-11 10:28:01.871 W/Finsky ( 1242): [1] CarrierParamsAction.run: Saving carrier billing params failed.
12-11 10:28:01.881 D/Finsky ( 1242): [1] CarrierProvisioningAction.shouldFetchProvisioning: Required CarrierBillingParams missing. Shouldn't fetch provisioning.
12-11 10:28:01.881 D/Finsky ( 1242): [1] CarrierProvisioningAction.run: No need to fetch provisioning from carrier.
12-11 10:28:01.881 D/Finsky ( 1242): [1] GetBillingCountriesAction.run: Skip getting fresh list of billing countries.
12-11 10:28:01.881 W/AccountManagerService( 461): caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.881 E/Finsky ( 1242): [57] 1.run: Caught SecurityException: caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.901 D/Finsky ( 1242): [1] CheckoutPurchase.onErrorReceived: Could not retrieve Checkout auth token: caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.901 E/Finsky ( 1242): [1] CheckoutPurchase.setError: type=UNKNOWN, code=-1, message=An error occurred. Please try again.
Reposted to QandA, sorry for the mix up. Mods feel free to delete.
I was getting the authentication error and wouldn't log me in....I reflashed Gapps and I could get into Market again but when I try to download or update an app, it just sits there and says, "downloading......"
But my buddy who is on Sprint is able to download apps just fine.
Have you tried contacting Google via email. It might be on their end.
Sent from my ADR6300 Incredible
I believe this can be fix like so:
Go to: settings/applications/manage applications/running app./tap:download manager,then tap clear data,and force to stop,after that go back to home,restart your phone,also clear cache/data on market,I hope this will fix your problem...let me know.
Sent from my PC36100 using XDA App
Thanks for the suggestion, but I am still having the problem. I'll just use the web interface for now.
I just downloaded the MarketFix app from the Android Market. It moves the market cache to the SD card. Problem solved...give it a shot.
I had that same problem when the credit card information for Google Wallet had to be updated.
Try entering or updating your Wallet info online via your computer.
Sent from my NookColor
gadzooks64 said:
I had that same problem when the credit card information for Google Wallet had to be updated.
Try entering or updating your Wallet info online via your computer.
Sent from my NookColor
Click to expand...
Click to collapse
Thanks for the tip, but still a no go.
wrong thread, sorry
I'm having the same exact problem as the OP, anyone know of any other possible solution or tricks?
By the way I have a different device than OP, mine is a cheap chinese tablet called teclast p75.
android market place error
unfortunately i also have the issue with the android market place on my kindle fire. i installed the market place, google wallet is actual, but i am even not able to download free apps. after accepting and clicking on "download" i always get the message
"appname" could not be downloaded due to an error. does anybody have an idea? I am really lost.
have you been updated to the 3.4.7 version of the market yet? that's to anyonehaving this issue
I got same proplem. i'v update market, clear cache, clear everything and stil can't buy anythings from google play
so?
I am having this problem now. on og droid steel droid rom.
I had a similar problem once on my kindle and eventually what i wound up doing was going into recovery and flashing the ROM from scratch like it was brand new. Wipe System/Data/DataData/Cache/Dalvik/anything else you like to wipe and reflash the ROM (and the newest applicable gapps) and see if that helps. It did the trick for me, it is an odd error and I feel like the easiest thing is to start from the beginning when something like that happens and hope that you don't run into it again.
EDIT: of course make a nandroid first, in case it doesn't work
I had the mismatced UIDs issue when I installed a stock 2.3.4 Rom. It alerted me on the first boot up, then never alerted me again. I had to install a different Rom because many features didn't work. Hope this helps!
I did try reflashing the stock ROM (provided by the producer) without success, still having the same problem.
You mention reflashing the gapps, would that only work if you got the Cynogenmod installed or will they work with any ROM?
I did try reflashing the stock ROM (provided by the producer) without success, still having the same problem.
You mention reflashing the gapps, would that only work if you got the Cynogenmod installed or will they work with any ROM?
Click to expand...
Click to collapse
Were you able to root/flash this through recovery? With stock ROMs the GAPPS are typically included (unless the company making the tablet wishes to use a different market so they don't have to pay royalties to google).
Yes it does ship with gapps but the user mentioned re-installing them (maybe even upgrading). I wondered that if you can find different gapps it could make it work but I don't know how you would go about it. The gapps for Cynogen are in a zip that has to be installed using Cynogen recovery console, not sure how to install them manually.
kulhat said:
Yes it does ship with gapps but the user mentioned re-installing them (maybe even upgrading). I wondered that if you can find different gapps it could make it work but I don't know how you would go about it. The gapps for Cynogen are in a zip that has to be installed using Cynogen recovery console, not sure how to install them manually.
Click to expand...
Click to collapse
If you want to install a newer market you can do it as long as you're rooted. That being said, so long as you're not on an ancient device (maybe you're that lucky with the chinese tablet) it is supposed to update automatically. At any rate, if you have SU then you just need to drop the vending.apk into /system/app and give it the following permissions:
[X][X][ ]
[X][ ][ ]
[X][ ][ ]
EDIT: You might only need marketupdater.apk things have changed since they changed the market to googleplay so I am not as familiar with it as I used to be when I originally rooted/ added the market to my Kindle Fire
All I do anymore to get gapps is flash the gapps.zip through recovery but I don't know a whole lot about your chinese tablet so I can't really give input on its recovery setup haha
Related
Hi folks,
I took sometime to check that my phone was working properly for warranty reasons and now I am desperately trying to backup some of my apps (not even everything...) before unlocking the bootloader (which wipes everything, that's the whole problem!) and install a custom ROM. If have tried the following options :
Titanium backup : I am not root so it doesn't work. Other software could save my APK but not the actual data, which is what I am interested in
NANDROID backup : as I am not unlocked so I don't have a custom recovery image so no nandroid backup
adb backup : was my best hope but it really behaves weirdly on this device : it states in logcat that it can't find the specified package or that it can't bind it... really weird :
Code:
D/BackupManagerService( 272): Binding to full backup agent : com.mypackage
W/BackupManagerService( 272): Unable to bind to full agent for com.mypackage
W/ActivityManager( 272): Unbinding backup agent with no active backup
W/ActivityManager( 272): Process/uid not found attempting kill of com.mypackage / 10272
W/ActivityManager( 272): Unbinding backup agent with no active backup
W/ActivityManager( 272): Process/uid not found attempting kill of com.mypackage / 10272
I also tried this script (http://smartmobilehub.com/actionbar/36152/Ultimate-Backup-Tool-No-Root-Required) that automates the process, but as it uses adb backup it doesn't work either.
I am thinking about trying to root the device without unlocking the bootloader (with this tool for instance : Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460) but I am really not confident it will work and will not hurt my device. Did anyone try that ?
Did anyone ran into the same kind of problem ? Has someone got a solution ?
Can someone with stock JB test if adb backup works (very easy command to backup google maps for instance :
Code:
adb backup -f mybackup.ab - apk com.google.android.apps.maps
If the output file is more than 1ko then it probably worked, you can check in titanium backup with the option : "restore from .adb backup") if JB solves this problem, then it's worth waiting for the update, otherwise I could try something else right now.
Thanks in advance for your help!
adb backup should work. I've done it before, but never tried to restore it. None if the other options are viable.
Thanks for your input BenPope! I think you should check your backup with Titanium Backup, you could be surprised...
For me it seemed to work : first I launched the full backup, it did backup the shared part (SD card part) for a long long time and did output a massive several GB file, but it didn't backup all the other packages except for a random few ones (and I ran the backup several times caused it sometimes crashed my phone and overall the output size was always different). I discovered that with Titanium Backup, and therefore tried to backup a single package with logcat which outlined the problem exposed in my previous post.
Can you try backing up a single package if you are still on stock ?
Maybe I'll try tomorrow. I'm not rooted, how far can I get with Titanium to test it?
BenPope said:
Maybe I'll try tomorrow. I'm not rooted, how far can I get with Titanium to test it?
Click to expand...
Click to collapse
You have no other choice than using another device that is rooted as Titanium Backup (TB) won't offer much options on a non rooted one... I used my tab for instance. Also keep in mind that this is a Pro feature that requires you to purchase TB (but if you plan on rooting, this is the best app ever! )
Other option, without TB, you can try running the backup on a single package (use my command or ultimate backup script, see 1st post). If the output is a 1ko file with the -apk option (which determines to backup the apk too), then something went wrong...
Just do nandroid back up in recovery
johnnyk75 said:
Just do nandroid back up in recovery
Click to expand...
Click to collapse
How? I don't have a custom recovery as I am not unlocked
Good news! I just had the JB OTA update today and it solves the adb backup problem : backup is now possible (though with no password and data only it seems, but it works). So I now have back-up my data and unlocked my bootloader, at last!
Thanks for your help folks
I've had a problem ever since I've tried using 4.2 ROMs, such as CM10.1 and AOKP. I install the ROM, load my apps onto it, and when I reboot, not only does the reboot take a ridiculous amount of time (sometimes over 5 minutes) but some of the apps will have had their data wiped and some will just disappear completely!
Finding this really frustrating not being able to reboot without fear of losing apps and data, I decided to logcat the boot. The logcat is full of things like this:
Code:
W/PackageManager( 420): Package com.teslacoilsw.launcher at /system/app/com.teslacoilsw.launcher-1.apk reverting from /data/app/com.teslacoilsw.launcher-1.apk: new version 20003 better than installed 19504
W/PackageManager( 420): Package source /data/app/com.teslacoilsw.launcher-1.apk does not exist.
W/PackageManager( 420): Couldn't delete native library directory /data/app-lib/com.teslacoilsw.launcher-1
I/PackageManager( 420): Package com.teslacoilsw.launcher codePath changed from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk; Retaining data and using new
D/PackageManager( 420): No files in app dir /vendor/app
W/PackageManager( 420): Code path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Resource path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Permission com.android.launcher.permission.INSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
W/PackageManager( 420): Permission com.android.launcher.permission.UNINSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
That same error frequents throughout the boot, just with different package names for all the apps on my phone, both system and user apps. Here's a logcat of a boot.
At first I thought maybe it was because when I upgraded from 4.1 to 4.2 and restored my apps+data through TitaniumBackup that maybe the 4.1 data was screwing with something in 4.2, so I did a clean wipe of the ROM, downloaded the apps from the Play Store and didn't restore anything from TitaniumBackup, yet it was still doing it! I've tried wiping and reinstalling about 5 times now and I keep losing some apps+data on a reboot.
Can anyone who understands logcat a bit better than me or someone help me out?
dudeman1996 said:
I've had a problem ever since I've tried using 4.2 ROMs, such as CM10.1 and AOKP. I install the ROM, load my apps onto it, and when I reboot, not only does the reboot take a ridiculous amount of time (sometimes over 5 minutes) but some of the apps will have had their data wiped and some will just disappear completely!
Finding this really frustrating not being able to reboot without fear of losing apps and data, I decided to logcat the boot. The logcat is full of things like this:
Code:
W/PackageManager( 420): Package com.teslacoilsw.launcher at /system/app/com.teslacoilsw.launcher-1.apk reverting from /data/app/com.teslacoilsw.launcher-1.apk: new version 20003 better than installed 19504
W/PackageManager( 420): Package source /data/app/com.teslacoilsw.launcher-1.apk does not exist.
W/PackageManager( 420): Couldn't delete native library directory /data/app-lib/com.teslacoilsw.launcher-1
I/PackageManager( 420): Package com.teslacoilsw.launcher codePath changed from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk; Retaining data and using new
D/PackageManager( 420): No files in app dir /vendor/app
W/PackageManager( 420): Code path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Resource path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Permission com.android.launcher.permission.INSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
W/PackageManager( 420): Permission com.android.launcher.permission.UNINSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
That same error frequents throughout the boot, just with different package names for all the apps on my phone, both system and user apps. Here's a logcat of a boot.
At first I thought maybe it was because when I upgraded from 4.1 to 4.2 and restored my apps+data through TitaniumBackup that maybe the 4.1 data was screwing with something in 4.2, so I did a clean wipe of the ROM, downloaded the apps from the Play Store and didn't restore anything from TitaniumBackup, yet it was still doing it! I've tried wiping and reinstalling about 5 times now and I keep losing some apps+data on a reboot.
Can anyone who understands logcat a bit better than me or someone help me out?
Click to expand...
Click to collapse
well...
only errors i see are:
Code:
E/Gmail.LabelManager( 2334): Unable to get label ^i for account [email protected]
E/Gmail ( 2334): Couldn't find label: ^i
are you using nova launcher? stable or beta? i was a user of nova launcher (switched to apex a few days ago) on CM; never seen such warnings.
my advice would be start fresh: flash stock images through fastboot, formatting the partitions before flashing them. update your bootloader to latest version if needed.
then flash latest twrp (can't suggest cwm version, but i assume latest non-touch would be the most stable, although some will say otherwise), and reflash your rom.
install fewer apps at the same time, rebooting in between.
Re: CM10.1 apps + data loss on reboot
bk201doesntexist said:
well...
only errors i see are:
Code:
E/Gmail.LabelManager( 2334): Unable to get label ^i for account [email protected]
E/Gmail ( 2334): Couldn't find label: ^i
are you using nova launcher? stable or beta? i was a user of nova launcher (switched to apex a few days ago) on CM; never seen such warnings.
my advice would be start fresh: flash stock images through fastboot, formatting the partitions before flashing them. update your bootloader to latest version if needed.
then flash latest twrp (can't suggest cwm version, but i assume latest non-touch would be the most stable, although some will say otherwise), and reflash your rom.
install fewer apps at the same time, rebooting in between.
Click to expand...
Click to collapse
Wait so the whole "couldn't delete data-lib" thing is normal..?
Yeah using nova, beta builds.
Hmm, okay I'll give flashing stock a try. How do I go about updating the bootloader? IIIRC I think there was a bootloader img in the stock folder, is it that?
Sent from my Galaxy Nexus using xda premium
Re: CM10.1 apps + data loss on reboot
dudeman1996 said:
Wait so the whole "couldn't delete data-lib" thing is normal..?
Yeah using nova, beta builds.
Hmm, okay I'll give flashing stock a try. How do I go about updating the bootloader? IIIRC I think there was a bootloader img in the stock folder, is it that?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes. Let us know how that turns out.
Sent from my i9250
Re: CM10.1 apps + data loss on reboot
bk201doesntexist said:
Yes. Let us know how that turns out.
Sent from my i9250
Click to expand...
Click to collapse
That seems to have worked. I didn't realise it would wipe my sdcard though, so I lost everything including over 10,000 texts :/ all I have is a TB backup from a week ago and my camera pics that dropbox auto uploaded. Oh well, can't do anything now, thanks a lot for your help
Sent from my Galaxy Nexus using xda premium
Hello i got a strange problem. Few days ago I got crash when i want to open (installed before and updated before to the last version) Dropbox. It happens suddenly. After update it works fine, but with next trying to open, apps got crash and closed. I decided to do reinstall, uninstalling and installing again, but i had some bugs/errors.
When i want to download i got problem called Error -24, i found sollution for it, but don't work for me.
Sollution is like:
Qewbicle said:
Go to
/data/data/
and search for your
com.application-address.whatever-it-may-be
Some of them you can tell what they are just by the names, the others, google-em.
If you wish to keep the information that it contains for the app, I recommend making a copy of it first.
Delete it
Install the application, it'll work, trust me.
Now replace it with your copy.
Done.
Click to expand...
Click to collapse
But it didn't works for me, after this i got problem with package lost in google play store. Sometimes i got LOW STORAGE info, but it is fake, cause i could install other apps, much bigger than dropbox - so i have space to install.
I delete folder com.dropbox from:
/data/data
/data/usr/0/
/data/system
every dropbox folder
I tried to install dropbox from official homepage, i get the app on my phone, but installation is not finish. I also tried to restore backup of Dropbox via titanium backup, but it stuck on the restoring (app only and same for app + data)
I don't have no idea what is wrong. I did also FIX APK Permission from 4EXT Recovery without any result.
Here is my logcat:
Code:
I/SystemServer( 418): DropBox Service
I/BootReceiver( 418): Copying /proc/last_kmsg to DropBox (SYSTEM_LAST_KMSG)
I/ActivityManager( 418): START u0 {act=android.intent.action.VIEW dat=file:///storage/sdcard0/Download/Dropbox.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 2538
I/AppSecurityPermissions( 2763): Ignoring unknown permission:com.dropbox.android.permission.C2D_MESSAGE
I/ActivityManager( 418): START u0 {dat=file:///storage/sdcard0/Download/Dropbox.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from pid 2763
W/ActivityManager( 418): No content provider found for permission revoke: file:///storage/sdcard0/Download/Dropbox.apk
W/ActivityManager( 418): No content provider found for permission revoke: file:///storage/sdcard0/Download/Dropbox.apk
I/PackageManager( 418): Running dexopt on: com.dropbox.android
E/installd( 84): dexopt cannot open '/data/dalvik-cache/[email protected]@[email protected]' for output
W/PackageManager( 418): Package couldn't be installed in /data/app/com.dropbox.android-1.apk
I/InstallAppProgress( 2763): Finished installing com.dropbox.android
Any sollution? I am working with it about few hours... Thanks for help.
I almost forgot, after some restarts and clean dalvick-cache my Titanium Backup was gone, and i had to install it again, strange situation when app suddenly dissappear, any fix for it too?
Update:
I tried to install via terminal emulator but got message:
Code:
pkg: Dropbox.apk
Failure [INSTALL_FAILED_DEXOPT]
I installed the ZMoD ROM by Ziyan a couple of weeks ago on my Galaxy Nexus. works perfect, much faster than CM 10.2 which I used before, and stable with no problems so far.
the only issue I have is that I can't install the Facebook app. when installing via Play Store, I get error 504 (which normally means that there is a network connection error, but that's not the case because I can install other apps just fine).
I then tried to sideload the app using adb, and this is the error I get after the several packages have been compiled:
Code:
E/installd( 136): DexInv: --- END '/data/app/com.facebook.katana-1/base.apk' --- status=0x0100, process failed
W/PackageManager( 414): Package couldn't be installed in /data/app/com.facebook.katana-1
E/Finsky ( 1478): [1] 2.onReceive: Error -504 while installing com.facebook.katana: INSTALL_FAILED_DEXOPT: Package couldn't be installed in /data/app/com.facebook.katana-1: scanPackageLI
W/Finsky ( 1478): [1] 3.installFailed: Install failure of com.facebook.katana: -504 null
D/Finsky ( 1478): [1] InstallerTask.cancelCleanup: Cancel running installation of com.facebook.katana (com.facebook.katana)
E/ActivityThread(19954): Failed to find provider info for com.facebook.katana.provider.AttributionIdProvider
searching the web for this error it seems that one possible cause is that the /system partition is too small, and indeed, there is hardly any space left there. I got an error about this issue when flashing the GApps, so I selected a smaller GApps build to work around it.
any ideas what can be done about this?
solved
ok, I solved the issue. for the record, I did a new install of ZMoD, but this time, I not only did the normal factory reset (i.e. clearing cache, dalvik, data), but also formatted the /system partition. looks like this removed some leftovers from the old CM version which caused the conflict.
Firstly, the "system" partition of official LineageOS 18.1 doesn't have enough free space for OpenGapps "stock".
Previously I've been using OpenGapps "pico" instead, then today I want to try to configure "stock" to exclude most of apps, only leaving out several wanted ones. There's an official tutorial for this: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
I modified the example "Include" mode installation config, replacing "Include" with "Exclude" & commented out apps I want to install.
After several cycles of trial-and-error process, the OpenGapps installation process finally seemed to be complete without error.
However, the phone fell into bootloop after rebooting from TWRP...
Fortunately, I was still able to adb shell into the phone, and then I got these two lines from logcat:
Code:
11-06 10:21:35.139 5990 5990 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
11-06 10:21:35.139 5990 5990 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.projection.gearhead (/system/app/AndroidAutoPrebuilt): android.permission.UPDATE_APP_OPS_STATS}
I was confused. I actually excluded "AndroidAuto" and (not mentioned in example config) "AndroidAutoPrebuiltStub" but these two unwanted apps were still automatically reinstalled during boot, even after manually deleting its files under TWRP & deleting its sections in /data/system/packages.xml. I also checked /system_root in TWRP & these two apps didn't show up there.
Finally I gave in. I commented out the lines which previously excluded these two unwanted apps in my OpenGapps config. But then the phone still fell into exactly the same bootloop syndrome.
After some googling, I edited /etc/permissions/privapp-permissions-google.xml - according to official docs, "as of Android 9, implementors must explicitly grant or deny all privileged permissions or the device won’t boot". So I added (seemed to be missing) "android.permission.UPDATE_APP_OPS_STATS" inside the "com.google.android.projection.gearhead" section.
Phew. After editing privapp-permissions-google.xml the phone finally got out of bootloop...
Ah, tried again, with "GearheadStub" included, while both "AndroidAuto" and "AndroidAutoPrebuiltStub" were excluded, this time the unedited privapp-permissions-google.xml didn't trigger a bootloop.