Ever since I've started working the CM10 builds from codeworkx (which, by the way, are amazing), I've had a persistent problem with the Google Maps API not being available. Google Maps itself continues to work fine, but apps which depend on it don't work anymore. In the case of Instagram it just means I can't use the photomap which isn't a huge problem, but for apps like Uber and AirBNB it means that I can't install them at all (they show up as incompatible). Trying to install the apps via adb also fails with INSTALL_FAILED_MISSING_SHARED_LIBRARY.
I've tried installing a few different versions of gapps (currently using 20120726 since it's the most recent) and it hasn't helped. I also found some instructions for fixing this issue a while ago by updating the relevant files directly (can't post the link, but it's on slatedroid and the article is "fixing the INSTALL_FAILED_MISSING_SHARED_LIBRARY error") but it hasn't helped either.
I've tried all of this both with an updated CM10 build as well as after doing a full wipe and install of the updated ROM with no change.
Any ideas on what could be going on? Is there anything else I can try?
Related
While testing CM7.1 I found that my google cloud backup was not working.
Restore worked fine, but backup was enabled, but not provisioned.
So I started reproducing that error, created logs and finally found that there is an incompatible version mismatch between several components of the gapps package.
In this special case, the GoogleBackupTransport.apk shows version 2.3 whereas other components show version 2.3.3 and 2.3.4 - a colorful mixture...
Some code from the newer packages is calling a service intent of GoogleBackupTransport which does not exist in version 2.3.
Read the full "story" in CM bug tracker, issue 4353 (I'm not allowed yet to post URLs here)
CM Team told me that they are not responsible for gapps - which I understand and respect.
So where could I report such an issue? Who created those packages?
In my special case, I used a newer GoogleBackupTransport.apk from an older Oxygen ROM, based on 2.3.5 - backup is working fine now, I'm happy.
I also considered creating a gapps package based on the 2.3.7 Versions that can be found in the oxygen-rom repositories, but those are not universal packages with all DPI versions, so I won't do that work if that's not a full replacement for the universal package...
Now, how to proceed getting this fixed? Or who could (and likes to) build a universal gapps package based on 2.3.7. A consistent package might solve other maybe yet undiscovered issues as well.
Edit: I'm talking about gapps-gb-20110828-signed.zip, but older versions are affected, too.
Any luck addressing this? I'm having the same problem.
No, nothing happened. This will be fixed in ICS Gapps, as this is a complete new package.
To workaround this issue, do the following:
Get the GoogleBackupTransport apk in Version 2.3.7. You could extract it from the latest Oxygen ROM, for example (www.oxygen.im), or go to the oxygen github repository if you do not want to download the whole ROM, get it here:
https://github.com/oxygen-rom/android_vendor_google/tree/gingerbread/system/app
Replace the old Version in your ROM, then delete data partition.
You have to run the Setup wizard again to activate the backup system, the only way to do this is a factory reset or a clear data from recovery.
Sent from my HTC Desire using XDA App
So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?
lordcheeto03 said:
So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?
Click to expand...
Click to collapse
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
bizcuite said:
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your input. I don't know how much of a change there will be using the /etc/permissions files from CM, though I will try it. As for the build.prop, I use the exact same build.prop in CM and the play store works 100%.
EDIT:
I looked at /etc/permissions and the only difference between CM and the one I'm working on right now is that CM has a file called com.cyanogenmod.android.xml. I don't believe that file is needed because I'm not building CM.
Did I break my Tablet...?
I am a big PACman fan and have been using the rom on every one of my devices. I am also not new to rooting and flashing procedures and have done them on different devices many times including updating hundreds of times. PACman was quiet for a while but has started up again since August, so I was really looking forward to that until I had following problem:
1. Installed the newest rom with a factory reset beforehand.
2. Setup the device as usual.
3. Opened gmail --> Stuck on "Getting your messages"
4. Tried calendar, contacts and google music without success, as they display neither my music, contacts nor my calendars.
5. Drive and Maps are working though...
I have now done the following:
- Reverted all the way back to stock 4.1, rooted and upgraded to 4.4.2 stock.
- Flashed boot.img from PAC rom and installed it with gapps. Everything went perfectly.
- Added my google account during the setup process, opened gmail --> stuck on "getting your messages"
- Added a second google account, which is also not syncing.
Before this I already tried using different gapps (PA, CM, Banks), doing a playstore and play services reset. I am really not new to this and this is the 5th device I own that I rooted and installed custom roms on. My phone has PAC and is working flawlessly. I'm really lost here and would appreciate any ideas or help.
Rom versions I tried: nightly from 12th, 18th and 323rd with clearing cache and dalvik after install.
Gapps: Banks, CM and PA gapps 11th, 18th
When installing AOSB project, everything works flawlessly!
Something I am missing here? Please help!! This is getting so frustrating...
PS: Here are three screenshots of how it looks like (weird is that there are no timestamps in the sync tab)
http://imgur.com/sAEqmCE,UxNjuNa,zJ83DiT
moesus said:
Gapps: Banks, CM and PA gapps 11th, 18th
When installing AOSB project, everything works flawlessly!
Click to expand...
Click to collapse
the problem is in P.A.C ROM builds or in Gapps.
Rootk1t said:
the problem is in P.A.C ROM builds or in Gapps.
Click to expand...
Click to collapse
PAC rom can't be the problem, as all other users report no errors. I have tried different Gapps (always checked MD5 sums...) and this issue doesn't resolve. I am looking for any new ideas on the issue.
Personally I cannot explain the issue myself
So if anyone has an idea, please help!
Search for another boot.IMG, there have been issues with the cm boot and wifi modules, maybe the same with the PAC boot.IMG low/ connectivity would explain the lack of sync time stamps
Sent from my omni_pollux using XDA Free mobile app
Hi. I'm using CM12.1 with my quark (xt1254). Using a clean install method if I flash cm with a current gapps build (tried 1/29/16 & 1/30/16) the play store will not download apps over approx 25 MB. Play store downloads the app to 99%, restarts the download, then fails with error 963. Small apps are unaffected. Using the exact same method, but with an open gapps from 12/08/15
https://www.dropbox.com/s/e7a48os7ucj014p/open_gapps-arm-5.1-stock-20151208.zip?dl=0
, works perfectly fine. Just thought I'd see if anyone had any thoughts as to what's up. Ideas, contents, suggestions appreciated.
sd card
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
kikkie said:
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
Click to expand...
Click to collapse
I think the issue is related to the way CM12 chooses the default install location for you. The newer gapps builds may have triggered something, but I believe the root of it to be the default installation location. Please see this post for a possible permanent solution.
http://forum.xda-developers.com/showpost.php?p=65139180&postcount=6
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
elderlypunk said:
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
Click to expand...
Click to collapse
No joy after changing the default location? Which way did you use to change the location? Did it give you any messages? it shouldn't have, if it worked, it should just have returned a prompt.
Just to be on the safe side, I would load the gapps file that you mentioned was working in the past, and change the default location before trying any of the apps. If you already have it all loaded up, then yes, I'd also recommend you clear the cache and data from the playstore and playservices apps.
Don't know if you're using opengapps, but I took a look at their most recent builds and noticed that the file size changed slightly after 01/20/2016, so your reasoning has merit.
If you happen to be using TWRP, you could also try changing the location from recovery. Advanced -> Terminal Command -> Select and then enter the command. I really hope this helps.
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
elderlypunk said:
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
Click to expand...
Click to collapse
Ugh. I was able to recreate the behavior you're experiencing on a 2012 Nexus 7 - the only device I have access to with no SD card slot. I used the last two nightlies of CM12 and opengapps from two days ago, and also the one I mentioned from 1/20. Always had the behavior when downloading large apps, and as you say, apps not from the playstore. And yes, same behavior whether I used nano, pico, et. al.
The behavior disappears once I flash the latest nightly with the gapps from 1/20 AND change the default location. I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Gster09 said:
I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Click to expand...
Click to collapse
No worries! Since I found a working older gapps I'm inclined to let this go for now.
Which older version did you install? I'm running into this issue.
See link in op.
Hello,
I have same 963 error issue on my both cm 12.1 devices : Galaxy Nexus and Nexus 7 (2012).
I tried on my Galaxy to "pm set-install-location 1" but it don't solved the issue.
(delete the play store app cache and data don't work)
Can you provide me the link to this Gapps, it is not working anymore
ancelin said:
Hello,
Can you provide me the link to this Gapps, it is not working anymore
Click to expand...
Click to collapse
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue.
Click to expand...
Click to collapse
Did s/he mention when it will be fixed?
If you're looking for a version of Open GApps that doesn't have the double download fail with error 963. Then you should install Open GApps 2016.01.05. Don't install the 2015.12.08 version if you're using CyanogenMod! You'll end up breaking WebView on your rom if you do. You can find an Older Version option on the Open GApps Web Site and get the version I mention from there.
As others may have mentioned you can temporarily dismount your SD Card as a work around to this issue, but I preferred to downgrade rather than having to do that every time I used the Google Play Store.
As I understand the issue it's not a bug with Open GApps itself but a bug with the Google Play Store, apparently but I haven't confirmed any version of Google Play above 6.0.5 can have this issue.
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
Click to expand...
Click to collapse
This fixed the issue for me, and I was able to install the 2 problematic apps. Strangely, I had no trouble installing some other apps, namely made by my operator (MEO music and MEO drive), which leads me to think it might be related to locale.
However, now I can't search the play store, as it force closes when tapping the search box :/
Best thread ever.
Finally it works.
Thanks everyone
Hi,
I have had a search of XDA and cant find the following issue mentioned anywhere.
So sorry if missed something but i need help with the following.
I have in the last 2 days installed the following several times each
[ROM] [8.1] Resurrection Remix O v.6.1.0 [POLLUX/POLLUX_WINDY][UNOFFICIAL]
and
[ROM] [8.1] LineageOS 15.1 [POLLUX/POLLUX_WINDY][UNOFFICIAL]
and did the usual wipes, factory resets etc and although both roms work fine my issue is when i install apps from unknown sources.
I can install them fine, and they work without issue.. but if i reboot any of my apps from unknown sources are removed..
There is no trace of them, i have turned off the newer security stuff in the settings, tried with and without root,
with and without developer options..
Just need to know what im missing to get these apps to stick ..
The apps I have tried are the uber app, the sricam app, and apkpure .. none of which will install on the Tablet from google play
so im trying via sideload and they have all previously worked on all previous roms (mainly 7.1 roms)
cheers
shaun