I have just updated my p6210 to using aorth's cm10 build (0906). I applied a few updates of existing applications from the play store, but most other applications are shown as not compatible, even ones that I haven't ever seen have issues, like Google Maps.
Anyone else have the issue and is there a resolution for it, build.prop changes or something else?
Sent from my GT-P6210 using xda app-developers app
Additionally, is there a way to determine the actual property(ies) required that the device doesn't support which makes an app incompatible? I just went to install k9 mail and it is listed as incompatible as well. Being able to see the reason for being rejected would allow to know what needs to be changed or advertised as available.
Sent from my GT-P6210 using xda app-developers app
For full information, I did change the build.prop file to 133 dpi to test the tablet mode, but changed it back to 160 since then. Is there something in the market processing that would have grabbed that and made it permanent that isn't changed when the setting is changed? Should I have done it in the opposite order, get the market configured and synced at 160 dpi, have it take the initial setting if it's permanent, and then change the dpi?
Joel
mrjoel said:
For full information, I did change the build.prop file to 133 dpi to test the tablet mode, but changed it back to 160 since then. Is there something in the market processing that would have grabbed that and made it permanent that isn't changed when the setting is changed? Should I have done it in the opposite order, get the market configured and synced at 160 dpi, have it take the initial setting if it's permanent, and then change the dpi?
Joel
Click to expand...
Click to collapse
I've experienced the same problem. I haven't really looked into it yet. If I figure it out, I'll be sure to post what I find.
I just used this: http://forum.xda-developers.com/showthread.php?t=1839871 today to fix incompatibilities caused by setting dpi to 133.
Thanks, looks promising. To follow up for others as well, resetting the DPI to 160 didn't work immediately, I even tried killing and clearing the play store data. However, a while later (the next day) when I checked, the apps I expected were all available again. I assume it must be a periodic sync with Google's servers that is required but I haven't actually sniffed the traffic to confirm that.
Sent from my GT-P6210 using xda app-developers app
Related
Hi folks,
I'm just wondering of there's a reason why I can't access some apps I was able to find before in the market?
Quick Settings, Launcherpro beta, Adw launcher, Zeam, etc, are nowhere to be find now...
I've got some of them on my download page on the market app and I also wonder if I can still access the updates.
------------------------------
Sent from my Milestone using Tapatalk
think its a problem your end as I can findthen no problems..... Am uk..
regards
lohtse
Thanks for the reply. Ill try to find out.
Maybe your market access keys are incorrect because you have installed a custom rom? For example, test versions from Huawei have test keys installed that will not list all applications. You need to use proper release keys provided by carrier.
Thanks speckles, you point a different possible problem. Even if I don't have a custom rom: just a Milestone 2.1 rooted.
You need to use proper release keys provided by carrier.
Click to expand...
Click to collapse
Well, I think that I have the proper one for I didn't changed it. Can you tell me how can I check this? (I've got still a lot to learn.)
I have been reading a little on old and similar problems, often related issues with protected app, like paid/protected app on rooted phones - and regardless to the models, countries, carriers, and maybe even to the versions.
I am not sure to be concerned, I mean it's a bit different in my case. For instance, I have Tapatalk pro installed and which is protected but I can still find it on the market (I mean outside of the download tab).
So far, my problem only concerns some free apps.
There were from long time app that I wasn't able to find on the market (like TV.com), by example when using appbrain. But now, that's the first time I can't find apps I had already downloaded and that I've got installed. (I spotted the problem while recommending apps to a friend who's got a Desire since a few days. He was himself unable to find them, like Quick settings.)
Edit --
Scanning a barcode pointing on the apps in the market do not work as well.
Some solutions points to the build.prop:
Root your phone and modify your /system/build.prop with the fingerprint of a build that actually works. Then clear all data and cache from the market and google apps, reboot, set your clock to 23:59 and wait 5 minutes to force a refresh of the data before starting the Market app. You'll have to supply your Google account details again but this should work around the problem.
Click to expand...
Click to collapse
Useful as well:
From MasDroid, on XDA -14th April 2010, 08:59 PM
I've read about this issue which was recently explained by a developer of XDA (nprussell).
Apparently everyone is in the same boat so to speak. He states that many "protected" apps are missing from the market. There are generally two reasons why apps will be missing from the market:
When a new ROM or handset is released, the manufacturer (i.e. HTC), sends the build to Google for verification, which includes a 'Fingerprint' (a unique line of text which governs its market access) in one of the build files. Generally, it states the name of the phone and Android version in the fingerprint. With Root & System write access, this fingerprint can be changed, but although it's been claimed that the Desire has recently been Rooted, we still don't have confirmation from any developer of it being able to gain System write access.
Only until Google approve the build, then fingerprint will be added to their allowed database to view these protected apps on the market.
The other cause for apps missing from the market in builds is because of permissions of certain apps. For example, the barcode scanner app requires permissions to use the camera/auto focus. They are NOT protected apps. If the XML permission files are missing from system/etc/permissions, then Google Market will simply block these apps from showing.
HTC need to chase Google up on this and Google need to activate the Fingerprint.
Click to expand...
Click to collapse
Edit 2 --
I have tried to replace my build.prop (using one from a Telus Milestone) but nothing has changed. Maybe I need to erase the market's data as told in the second quote but I'm not sure to know how to do it.
I have the same problem. (Htc desire Vodafone/the Netherlands/original ROM) There was an OTA update few days a go. After that most of the installed apps couldn't be found. It seems that this affected a lot of people...check the comments on launcherpro an adw launcher websites
-------------------------------------
Sent via the XDA Tapatalk App
If you have edited your build.props, then it can take upto 24 hours for them to be published to the market. So wait a few days.
If it still doesn't work, try Eris Market Fix after doing a nandroid backup. Again, you may have to wait about 24 hours before noticing any changes.
I think i have same problem here. Finland/HTC Desire/Stock ROM.
There should be LauncherPro in market right? Had to dl new one from LP's site.
I have got everything back and I'm still using the same build.prop. So I believe that the market had been fixed.
Hope it's the same for you!
I was wondering if anyone knew what the cause of the apps that don't appear in the market even w/ improved market fix.
I have been trying to see if I can find the common denominator with these apps and I am coming up empty. Trying to create a running thread and identify some apps that don't so I can email the dev to see if there are restrictions present that we can't see. A couple I have noticed that I use daily are.
ADW EX
Dolphin HD (dolphin mini shows up)
Sent from my DROID2 using XDA App
Google has not officially certified the gtab for its use on the Android Market.
romanrish,
I know the feeling. I used to be able to see Launcherpro and even purchased it for my GTablet. Now with the new market (and all the fixes) I can't see it and have no way to tell when it gets an update other than going to the developers web site. BAH!
@Butch I am fully aware that Google has not certified the Gtablet for the market. This is more of a technical discussion. There are checks that are performed to identify what you should see in the market.
One of which is obviously looking at your build fingerprint. Since this action doesn't appear to have any consequences like changing you device ID probably would. I am trying to figure if there is a way to intercept these checks to display a different device w/out editing the build.prop which may cause instability or worse.
Any ideas?
Sent from my DROID2 using XDA App
mmracing said:
romanrish,
I know the feeling. I used to be able to see Launcherpro and even purchased it for my GTablet. Now with the new market (and all the fixes) I can't see it and have no way to tell when it gets an update other than going to the developers web site. BAH!
Click to expand...
Click to collapse
FYI: I have the new market and had to do the "Market Fix" (stop Market service, stop Google Framework, clear data on Framework) several times before I could "see" Launcher Pro and ADW...
It eventually worked and I was able to install both via the Market -- and now they show up fine inc. updates...
What I can't see (yet) is the EA Games that were on sale for 99cents...I am only able to see two -- FIFA (bought) and Tetris -- but I'm guessing it is something to do with the rest of the games not being supported on tablets. (I think NFS Shift even states not supported on Samsung Galaxy Tab)
I just tried the build prop from my droid2 for shiggles. It is kinda ballsy, but root explorer backs up your old build prop so I figured what the heck and gave it a shot. It seems that everything is here I haven't found any side effects. This is working great. Any app I was looking for is there now. This is the build fingerprint I used
ro.build.fingerprint=verizon/droid2_vzw/ cdma_droid2/droid2:2.2/VZW/23.20:user/ota-rel-keys,release-keys
Sent from my DROID2 using XDA App
romanrish: Did you have to do anything special post-mod of the build.prop when you changed it to your Droid2 string?
Market fix?
Hi
Firstly, i have flashed my uk wifi only xoom with Tiamat 2.2.1(moray)
now, when i go to market, i can not find certain apps. On market website it says my device is US verizon.
I followed another thread which suggested using market enabler, so I did, i used a custom value of 23415, set it to this value, and then save current settings. works fine, but when i reboot the xoom it restores back the the oringinal setting which is 310260. now i'm stuck.
another thread suggested editting build.prop although i can find the file i am at a lost as what i need to be changing and what i should be changing it to.
please help
TIA
I have the same problem with my UK xoom too, dont think there is a solution to it yet. Ive done a fair bit of searching! Would be nice to get it sortex though.
Sent from my Xoom using xda premium
nckgarvey said:
Hi
Firstly, i have flashed my uk wifi only xoom with Tiamat 2.2.1(moray)
now, when i go to market, i can not find certain apps. On market website it says my device is US verizon.
I followed another thread which suggested using market enabler, so I did, i used a custom value of 23415, set it to this value, and then save current settings. works fine, but when i reboot the xoom it restores back the the oringinal setting which is 310260. now i'm stuck.
another thread suggested editting build.prop although i can find the file i am at a lost as what i need to be changing and what i should be changing it to.
please help
TIA
Click to expand...
Click to collapse
there is an option to set that value on boot with market enabler but you need the donate or paid version of market enabler
i managed to set the value in market enabled donation version but the market still detected I was us verizon and although it changed the currency to £££'s I still couldn't search for uk app and I couldn't access certain websites bcos they said they where not available in my country
I bought the donation version too, i now get the market in ₤ and can access some UK apps like sky+ but not iplayer.
Sent from my Xoom using xda premium
I've seen this exact problem no where else on the internet. I'm flabbergasted.
Google drive refuses to open any document at all on my sidekick, and no one else on the internet has gotten this error message.
"Google Documents Error
Google documents has encountered an error. Please try reloading the document."
I'm using Ricandroid's NexusJB. I would post in his thread but I can't post in development yet. Its a great build otherwise and I'd like to avoid having to reinstall from scratch. Anyone else have this issue?
I do not have this problem. Do you have your Google account set up to sync in Settings>Accounts and Sync?
Yep, it is. Gmail and talk and contacts all work. I'm thinking its some kind of incapability with memory resources maybe? Its a blank denial on all doc types. I wish I were better at coding and linux to figure this out, but I'm too much of a newbie atm.
Sent from my SGH-T839 using xda app-developers app
Might be a server problem; have you tried again? Also see this page for some possible fixes: https://productforums.google.com/forum/#!msg/drive/ifONR5aCqSc/Sg0hZrbVQXcJ
Yeah I have, multiple times. I thought it may be droidwall but like the poster in your link says, it does load a docs list and allows me to make a doc offline. I didn't find this after many searches.. thanks for that.
Sent from my SGH-T839 using xda app-developers app
Yeeeah so it was droidwall. I found out after uninstalling it. I guess it was lying when it said it was allowing google drive. I think google drive relies upon other internet processes to function besides itself.
Thanks for your input!
Edit: Nope!
I thought it was droidwall, but I had uninstalled google drive at the same time. It seems its the new update that breaks drive functionality.
It seems the solution is to block updates. Google drive conveniently offers that functionality in its settings.
Sent from my SGH-T839 using xda app-developers app
Google Drive partially works right now when updated but the reason you can't open your documents may be that one of libs is missing in your /system/lib directory. They could have added more in the update that are otherwise seperated from the old version on your system memory.
Just a though I have had the problem once before, but I can't remember exactly how I fixed it.
Sent from my SGH-T839 using xda app-developers app
The latest version of Drive works fine for me. I did not have it installed at all, so I had a fresh install (not an update). Maybe try removing it completely (not just the updates) and reinstall. Is your Drive installed as a system app or user app? If it's a system app, you'll need to use something like Titanium Backup to remove it.
This would make sense. It is an uninstall able system app, so maybe the updates libraries are broken by that.
I'm reluctant to try uninstallong with titanium as its working now. Ehh I'll probably do it in a bit and let you guys know.
Would you know how to find out which libraries Drive uses, zydrate?
Edit: Aaand its broke again and I forgot to make a backup... whoops.
Sent from my SGH-T839 using xda app-developers app
I think google drive app that comes with ricandroid's nexus JB is the only one that will really work. Does anyone know if he packagaes google apps with it? If I could find the right package for the sidekick I could avoid a rom reinstall maybe.
I'm surprised there are barely any other sidekick users with this problem!! I'll post later to let you guys know if that holds true, and if a titanium backup would restore an uninstalled google drive's functionality.
It doesn't make sense to me that only the Drive app that ricandroid bundled with his nexusJB ROM would work. If that were the case, then anytime the app updated from the Play Store, it would break, and as you said, no one else seems to have a problem with it. I think the problem is on your device--maybe a dependency has gotten corrupted or gone missing. But you could always send ricandroid a private message and ask him what version he used, if he modified it, etc. You said it's working right now, so why not make a backup of it in case it starts acting up again?
I though it was working.... but it wassnt.
I finally reinstalled the JB build, which for some reason kind of made it faster?? Maybe a second wipe freshened it up.
Google drive was working initially, I tried updating it, it broke it again, and a titanium backup restored functionality successfully. So I still don't know what's wrong. Maybe a slightly corrupted ROM?
Ill try messaging ricandroid one of these days.
Sent from my SGH-T839 using xda app-developers app
I don't know why the update keeps breaking Drive. I posted a query on the nexusJB thread at http://forum.xda-developers.com/showthread.php?t=2162745 for you. We'll see what responses we get.
Wow, thanks man!!! Almost up to 10 posts though! Haha.
Sent from my SGH-T839 using xda app-developers app
The only response so far is that someone saw on g+ that several people still running 2.x are having an issue with google drive. Of course, everyone using the SK4G is still on 2.2. May just be a random issue.
I got another response that someone is using ES File Explorer File Manager to access Google Drive. I didn't know you could do that, but apparently you can access a lot of cloud services using that app (which is a good one, and free). Just search for it in the Play Store.
marathonjon said:
I got another response that someone is using ES File Explorer File Manager to access Google Drive. I didn't know you could do that, but apparently you can access a lot of cloud services using that app (which is a good one, and free). Just search for it in the Play Store.
Click to expand...
Click to collapse
I was watching the thread. Just posted in there as well now that I'm up to 10 posts. Thanks for your help with this, but I think I'll just stick to having updates disabled. Whatever google drive is being updated with, its nothing I can see as it has perfect functionality.
I can't install apps using the website for Play Store. It lists two devices for my phone, one with an unknown last used date and the other from months ago. I know I have multiple listings due to ROMs, had cleaned a lot out.
Google Services seems to be fine, the 'locate device' and ring works.
SCH-i535
LiquidSmooth v2.7
Any ideas on how to fix, or how to reset the relationship between the store and device?
Is the app compatible with the device?
Is the device connected to your Google account?
Sorry for the dumb questions
Sent from my SCH-1535 using Tapatalk 4
Hmong_Xiong said:
Is the app compatible with the device?
Is the device connected to your Google account?
Sorry for the dumb questions
Sent from my SCH-1535 using Tapatalk 4
Click to expand...
Click to collapse
Yes, and occurs for any app.
I don't get an error or any sign that there is something wrong other than I don't get the status bar icon show up and start downloading.
Yes. However there is a relationship issue. Bringing up "my apps" on the website gives a much different listing (old apps that were uninstalled) that what is installed and what is listed through the play app.
Also rooted and boot unlocked if not obvious by the ROM.
fussgeist said:
Yes. However there is a relationship issue. Bringing up "my apps" on the website gives a much different listing (old apps that were uninstalled) that what is installed and what is listed through the play app.
Click to expand...
Click to collapse
My best suggestion is to clear data and cache for the play store app in settings
Sent from my SCH-1535 using Tapatalk 4
Got it working.
Clearing the cache and data didn't do it, and thankfully didn't seem to even affect it (accounts and settings were all the same when I opened it back up).
I went back into the website's devices section and to settings. For some reason the actual device wasn't checked to show in the app lists; what I thought was a current was from an old flash.
Checked it show be visible, and got rid of the others. All is fine now, and explains why device locate worked as well. Although I don't know why an old phone that does work does't show in the list for locate but does for apps; hasn't been on in just over a year so google might have a timeout for something like that.
marked your first post with a thanks for the promptness and trying.
fussgeist said:
Got it working.
Clearing the cache and data didn't do it, and thankfully didn't seem to even affect it (accounts and settings were all the same when I opened it back up).
I went back into the website's devices section and to settings. For some reason the actual device wasn't checked to show in the app lists; what I thought was a current was from an old flash.
Checked it show be visible, and got rid of the others. All is fine now, and explains why device locate worked as well. Although I don't know why an old phone that does work does't show in the list for locate but does for apps; hasn't been on in just over a year so google might have a timeout for something like that.
marked your first post with a thanks for the promptness and trying.
Click to expand...
Click to collapse
Congrats man on figuring it out
Sent from my SCH-1535 using Tapatalk 4