Develop Bugs

Android Market Error

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

[Q] "Lost" Internal Storage and ODIN after failed encryption on ICS (AOKP Build 39)

[Q] "Lost" Internal Storage and ODIN after failed encryption on ICS (AOKP Build 39)
I have kind of an odd one. I flashed AOKP Build 39 today (using ODIN to EL29 CWM then flash). That went fine. Then I tried to encrypt the phone, which failed and kicked me back out to reboot. It mentioned something about having to do a full factory reset. I think I saw the default recovery logo show for a second before the AOKP boot animation kicked in. Phone booted fine, then I noticed that I lost the Internal storage. My SD card is at /emmc, and it works fine. I tried to ODIN back to EL29 CWM to do a full reflash (using the 1 Click Restore in the Sticky section) and now ODIN keeps failing at "Setting up Connection"
I'm hoping you guys can give me some insight

I dont have much to say on whats going on or how to fix it but.... From what I've read from your post you said something about a "factory wipe" form the "stock recovery"!!! I know you said that you didn't do the wipe, the phone did when it reset itself... I know that is a big no no with this rom. And the mention of eMMC... Sounds like the eMMC hardbrick bug.
On a side: This has got to be at least the 3rd or 4th post I've read today with the words "AOKP Build 39", "eMMC" and "factory reset" in them. And not one of them has turned out good.
Sent From My Galaxy Class StarFighter

I don't think it is the eMMC hardbrick bug. From what I have read of that, it completely hoses the phone. Also Build 39 has CWM 5.5 (which I heard is a bad build), so I didn't see it boot into Recovery.
I looked into it more and I keep seeing things in logcat about bad partitions. I would try an reformat it, 'cept I don't know how (safely at least). Maybe flashing Caulkin's Format All? I've pasted in the logcat info for anyone that wants to look
Code:
D/VoldCmdListener( 1745): volume mount /mnt/sdcard
D/DirectVolume( 1745): Checking for bad partition major number
D/DirectVolume( 1745): Found bad partition
E/DirectVolume( 1745): Fixing major number from 179 to 259 for partition 11
I/Vold ( 1745): /dev/block/vold/259:3 being considered for volume internal
D/Vold ( 1745): Volume internal state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/MountService( 1865): volume state changed for /mnt/sdcard (unmounted -> checking)
I/StorageNotification( 1955): Media {/mnt/sdcard} state changed from {unmounted} -> {checking}
D/MountService( 1865): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///mnt/sdcard (has e
xtras) }
I//system/bin/fsck_msdos( 1745): ** /dev/block/vold/259:3
I//system/bin/fsck_msdos( 1745): Invalid signature in boot block: f616
I/logwrapper( 1745): /system/bin/fsck_msdos terminated by exit(2)
E/Vold ( 1745): Filesystem check failed (not a FAT filesystem)
W/Vold ( 1745): /dev/block/vold/259:3 does not contain a FAT filesystem
E/Vold ( 1745): /dev/block/vold/259:3 failed to mount via NTFS (No such device)
E/Vold ( 1745): Volume internal found no suitable devices for mounting :(
D/Vold ( 1745): Volume internal state changing 3 (Checking) -> 1 (Idle-Unmounted)
I/PackageManager( 1865): Updating external media status from unmounted to unmounted
D/MountService( 1865): volume state changed for /mnt/sdcard (checking -> unmounted)
D/MountService( 1865): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///mnt/sdcard (has
extras) }
D/MediaScannerReceiver( 2029): action: android.intent.action.MEDIA_UNMOUNTED path: /mnt/sdcard
I/MemorySettings( 4775): Received storage state changed notification that /mnt/sdcard changed state from unmounted to ch
ecking
I/MemorySettings( 4775): Received storage state changed notification that /mnt/sdcard changed state from checking to unm
ounted
I/StorageNotification( 1955): Media {/mnt/sdcard} state changed from {checking} -> {unmounted}
D/VoldCmdListener( 1745): volume shared /mnt/sdcard ums
D/VoldCmdListener( 1745): volume shared /mnt/emmc ums

So I managed to fix the issue myself. I'll put the instructions down here in case anyone needs them
I tried "normal" Odin and that let me flash the EL29 CWM. From there I just flashed Caulkin's Format All (several times) and then reflashed my ROM.

"normal" odin as opposed to ? mobile odin ? I never mobile odin .. I personally do not trust it .. I have always and will always "normal" odin

i think people should just stop flashing those aokp
i try to time and it fail on my phone
better safe than sorry

yoo0angg said:
"normal" odin as opposed to ? mobile odin ? I never mobile odin .. I personally do not trust it .. I have always and will always "normal" odin
Click to expand...
Click to collapse
As opposed to the EL29 Restore executable, ie this http://forum.xda-developers.com/showthread.php?t=1433101

Kyral Retsam said:
So I managed to fix the issue myself. I'll put the instructions down here in case anyone needs them
I tried "normal" Odin and that let me flash the EL29 CWM. From there I just flashed Caulkin's Format All (several times) and then reflashed my ROM.
Click to expand...
Click to collapse
Awesome m8!!!
Glad it wasn't as bad...
mrej201 said:
i think people should just stop flashing those aokp
i try to time and it fail on my phone
better safe than sorry
Click to expand...
Click to collapse
That's what I'm saying...
Sent From My Galaxy10.1 Class Starship...

[Q] Galaxy nexus showing error after every boot

i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers

coolshan said:
i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers
Click to expand...
Click to collapse
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.

Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already

coolshan said:
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already
Click to expand...
Click to collapse
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt

Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
Petrovski80 said:
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt
Click to expand...
Click to collapse
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol

coolshan said:
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol
Click to expand...
Click to collapse
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.

Petrovski80 said:
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.
Click to expand...
Click to collapse
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/

coolshan said:
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/
Click to expand...
Click to collapse
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895

Petrovski80 said:
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"

coolshan said:
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"
Click to expand...
Click to collapse
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah me too.. thanks for the help though. but still i dont understand why is they phone functioning properly? what disfunction this process can cause ? it seems to make and receive calls and sms without any probelm

Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:

coolshan said:
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:
Click to expand...
Click to collapse
Great you fixed it. Thanks for posting the solution here.
Sent from my Galaxy Nexus using Tapatalk 2

Can't install Dropbox, Chromium ROM 11

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]

Error installing Facebook on CM 12.1 (ZMoD by Ziyan)

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.