I tried to download ShadowGun onto my TP running CM9, and it says that my device is incompatable.........why?.....
Also tried it with Need for Speed Shift.....
Oh, btw, both are on sale for $0.49
The touchpad is not running official android so some apps, usually games, don't recognize it as compatible even when it is. You will want to change the build.prop file to an official android device with similar hardware, if I was on my desktop id give u the exact device
Sent from my DROID3 using Tapatalk
Build.prop file??????.......lol......let me go search it up......thx for the reply.....
Downloaded fine for me. Plays pretty smooth too. Running cm9 alpha 2.
Sent from my SPH-D700 using XDA
Worked for me I'm on cm7.
Sent from my android touchpad.
Followed the instructions in this post, and all is well.......
http://www.everythingabouttablets.net/2012/01/02/get-asphalt-6-hd-running-on-your-cm7-touchpad/
Also, if you've changed your LCD density, a lot of apps will show up incompatible. You can either change it back to 160, or use an app like lcd density pro to download a modded market apk that will work with your custom screen density, while making the market think you are still running 160.
mike-y said:
Also, if you've changed your LCD density, a lot of apps will show up incompatible. You can either change it back to 160, or use an app like lcd density pro to download a modded market apk that will work with your custom screen density, while making the market think you are still running 160.
Click to expand...
Click to collapse
Thanks for recommending lcd density pro I was a little skeptical about paying ~$3 for it but it seems to work great with the app market where I change my DPI to 132 the native DPI of the Touchpad.
You may want to try the "rohan" update here in the Dev section. It changes a bunch of stuff in your build.prop file. I was able to download and start Shadowgun last night (I didn't really try playing). I still had problems with Dead Space, and haven't tested any of the Gameloft games yet.
Related
Hey everyone-
In case you didn't already know, the Hulu Plus app just came out for android but of course it's not compatible with the Vibrant. It is, however, compatible with the nexus s, which makes me think that getting it to work on the Vib shouldn't be to hard given how easy it was/is for the netflix app (assuming they use the same DRM technology). So I was wondering if anybody would be willing to tackle this mod and try something out? I don't have the apk, sorry, but it can be found here: http://bit.ly/lZqZ6m. Thanks again.
-bobofosho123
I got my APK from here instead: http://forum.xda-developers.com/showthread.php?t=1136634
My Nook Color (running CM7) is already working (it's a "Nexus S" by "samsung" in name alone) so I tried the same edits on my SGS Vibrant and caused the app to FC. Still running a 2.2 Froyo build ATM.
So, I'm inclined to believe it requires 2.3 or later to work ATM. Merely changing the model / manufacturer section of the system\build.prop (case IS important) on a SGS CM7 (or GB ROM) may allow it to finally work. No need to change the fingerprint as I didn't have to for the NC.
a straight ahead build.prop edit running CM7 nightly did not help the situation. app is listed in market and downloads, but get device compatibility error for playback.
You might try switching the resolution to match that of the nexus a, in combination with your build props edits. I think theres an app in the market that does this called screen density.
Sent from my T959 using XDA Premium App
wachalookinat said:
You might try switching the resolution to match that of the nexus a, in combination with your build props edits. I think theres an app in the market that does this called screen density.
Sent from my T959 using XDA Premium App
Click to expand...
Click to collapse
you can change density from within the build prop no application required.
I got the app from the market a few weeks ago and it of course did not work.
I however logged into my hulu account a yesterday and it showed my phone as an activated device on the account settings page.
It detected as a t959. I have a vibrant with CM7 build 41.
A friend has an hd2 with a cm7 rom on it and it does not shoot out the unsupported device message it tries to play the videos but will sit at the loading screen forever.
What's the word on this it seems like nobody cares to get hulu working!!!
Sent from my SGH-T959 using XDA Premium App
just installed the APK ya it says no support bummer anyone modified this yet to work on more devices? I have a Samsung Galaxy Tab 7.0 running Rooted Gingerbread CDMA Sprint Rom.
I used to use one modded by Racing19969 for the Galaxy S 4G when I had it, when I dusted off my old Vibrant I tried it out and all is well as I said all credit goes to Racing19969
http://dl.dropbox.com/u/51005515/HuluPlus-repackaged-signed.apk
Hi all,
I was wondering whether anyone had any theories why some apps I've paid for disappear when using different ROM's / Phones.
The Apps I can use as an example, are as follows:-
1. Exchange by Touchdown Key by NitroDesk, Inc
2. RootTools by JRummy16
3. 360 Live by Juan Xavier Larrea
For example, while using Lite'ning ROM v6.0 on my SGS2, all those apps were available. But when I changed ROM's to the SensatioN ROM by Crysis, they disappeared.
Similarly, on my X10i when I upgraded to 2.3.3 they all disappeared. And because this happened without any tweaking, i.e. it was using Sony's release without ROOT'ing, I contacted Android Market Support and this was their explanation in relation to the Touchdown Key.
"Thanks for writing back. It appears in a recent update by the developer,
they changed the screen requirements of the app, it now only supports
Normal, 160 (density) screens. The specs on your device show as Normal 240
(density). So to continue using this app you will need to contact the
developer and request the 240 be added into the app."
So with that response in mind, I'm trying to figure out why there is a difference on my SGS2 when I switch between Lite'ning ROM and the SensatioN ROM.
Any thoughts? Does anyone know why I am seeing these differences between two ROM's? Is this something to do with tweaks within these ROM's and the density that Market Support is talking about above? Or the old problem of footprinting?
There's no way to definitively answer your question, unless you know the particular applications as well as the developers.
Yes, a lot of ROMs have different LCD Density values. If it is just down to LCD Density then that's a very simple fix. Try setting it back to 240 (default value) and see if the application reappear. I've never heard of apps not showing in the Market due to LCD Density though. I think you've just been fobbed off there, but I'm not 100% sure - just about 99%.
In case you don't know, to set LCD Density you need a rooted phone. Edit /system/build.prop and find the value in there. You can do this manually with something like Root Explorer (my personal choice), or there are apps that set LCD Density available on the Market, but lots of them don't persist the change for long.
Thanks for the reply mate.
Yeah, my phone(s) is rooted. I'll do a few tests with an App I saw on the market (LCDDensity for Root) and see if that makes any difference to the market content...
Funnily enough, I stumbled across this post from searching for that app in Google...
http://forum.xda-developers.com/showthread.php?t=1183444
I'll report back whether it does fix the problem...
Grevane said:
Funnily enough, I stumbled across this post from searching for that app in Google...
http://forum.xda-developers.com/showthread.php?t=1183444
I'll report back whether it does fix the problem...
Click to expand...
Click to collapse
I'm surprised by that, but if that's what it does then that's what it does! Have you tried browsing for apps in the market on your PC? Obviously your PC doesn't know what your current LCD Density setting is on your phone, so it may not be relevant.
Maybe remote install from the website is the way to go.
Different ROMs are based from different builds, which can also include for which device as well.
So if the rom you are using announces itself as htc sensation, your samsung only apps goes missing in market, and vice versa!
Android market allows the developer to choose which brands/model phones they want the app to be used by.
LiFE1688 said:
Different ROMs are based from different builds, which can also include for which device as well.
So if the rom you are using announces itself as htc sensation, your samsung only apps goes missing in market, and vice versa!
Android market allows the developer to choose which brands/model phones they want the app to be used by.
Click to expand...
Click to collapse
Is that relevant though? I thought that all the ROMs for the S2 were based on the Samsung ROMs. There's certainly no HTC ROMs available for it.
Of course, the developer can put in the build.prop (I believe) whatever they want, but why would they do that?
Well, so far, as far as I can tell, the LCD Density hasn't helped....
I also cannot install "remotely" from the market website as the market website says "This item is not compatible with your device".
I've also tried this... without any success...
http://forum.xda-developers.com/showpost.php?p=11626645&postcount=425
ViralCipher said:
I found the solution to the market downloading problem! For anyone who has been having the Market Downloading issue with this ROM do the following and it should fix your issue. It fixed the issue for me and a co-worker.
To fix the market you go in manage applications:
1. Find Google frame work, clear all data and then force stop
2. Find Market.apk – then clear cache & data, then force stop.
3. Then, open ROM manager and fix permissions.
4. After the permissions have been fix, boot into Clockwork from ROM manager. And then format the Cache Partition.
5. Now reboot and test.
Click to expand...
Click to collapse
Hmmm... strange...
I've noticed at least 10 apps that show as 'not compatible' with my Streak, including the latest, XDA app, for example.
Question is: Why?
I have only modded the resolution to 180, but other than that, I'm running a stock and rooted ROM (351) with just a bit of bloatware stripped out. (Stage UI, etc.)
Can anyone give me an idea as to why apps that by all accounts ARE compatible show as being incompatible for me?
The main point is that I'm sure that many of these apps work for other Streak owners, just not for me.
The XDA app being a prime example of such. There must be a logical reason, but I don't know it. Anyone?
I am also on stock 351 and the XDA app shows up as compatible for me in the market. Did you change your fingerprint to get another app working, such as Netflix? I am at the stock 160 density.
The method that the market uses to determine compatibility is pretty poor when it comes to matching apps with compatible devices. You can try changing the fingerprint to another device.
Double check that you have the content filtering (maturity level) set to all, but that should not effect the XDA app.
I too found now that lots of the apps shows that they are not compatible with Dell Streak. Even some of the apps already installed won`t update because they are not compatible with Dell Streak now!
I tried to unroot Streak and now it is ok and at least apps already installed are again compatible. So try to unroot it first. Anyway, I needed root just to get rid of ooVoo etc.
I have official 351 and density set to 140
Revin said:
I too found now that lots of the apps shows that they are not compatible with Dell Streak. Even some of the apps already installed won`t update because they are not compatible with Dell Streak now!
I tried to unroot Streak and now it is ok and at least apps already installed are again compatible. So try to unroot it first. Anyway, I needed root just to get rid of ooVoo etc.
I have official 351 and density set to 140
Click to expand...
Click to collapse
I can't function without root, but I suspect it might be the same problem, because I have the identical problem. Installed apps show as 'incompatible'... what a load of crap.
Thanks for the tip. I'll try it.
Unrooting attempt forked my system. I had to restore. Thank god for Nandroid
Can't unroot.
Which items are showing as not compatible with the Streak so someone like me, with the resolution untouched but the ROM rooted, can test things.
Strephon Alkhalikoi said:
Which items are showing as not compatible with the Streak so someone like me, with the resolution untouched but the ROM rooted, can test things.
Click to expand...
Click to collapse
Many things which I already have installed show as incompatible, such as these two examples:
Drag Racing
XDA Forum app
QuickOffice Pro (which I own and purchased directly) is also listed as incompatible, but I have it installed and running perfectly.
I found an apk here for the Drag Racing app and it works. I'm now up to the latest version, but my Market app still shows that I need to update but says it's not compatible, but as I said, I already have the game installed and have already updated it to 1.1.0 via the apk manually.
There are quite few others, but I don't recall them all now.
None of those are showing as incompatible on my Streak. So the most likely culprit is the screen DPI change you made, since the DPI change is the only major difference between your Streak and mine. There are other possibilities such as a bugged Market APK or a corrupt flash of the ROM, but those aren't as likely.
I presume you have tried getting these apps through your PC?
I think it is just the root. I have DPI 140 (different from official 160 and even that is not standard for 800x480 screen) and I have device unrooted now and apps are compatible again (for example Appbrain was not compatible before and now it is ok).
When I last time had problem with this I wrote to developer of application and he wrote back that the app should be compatible with Dell Streak. So I wrote to Google support and they wrote that my device is rooted so they can't support it. So maybe Google is blocking some of the apps to the root users?
Donalgodon: sorry for your troubles with unrooting. I used Gingerbreak and the unroot function worked perfectly.
If I weren't rooted I might be inclined to agree with you. But, I'm rooted therefore something else must be causing the compatibility problem. Unlike you guys, I didn't change the dpi of the screen. The dpi change seems to be the common denominator here, and thus the dpi is more than likely the culprit.
Strephon Alkhalikoi said:
None of those are showing as incompatible on my Streak. So the most likely culprit is the screen DPI change you made, since the DPI change is the only major difference between your Streak and mine. There are other possibilities such as a bugged Market APK or a corrupt flash of the ROM, but those aren't as likely.
I presume you have tried getting these apps through your PC?
Click to expand...
Click to collapse
They show as incompatible from the PC also. I reset the Market, but no love.
Strephon Alkhalikoi said:
If I weren't rooted I might be inclined to agree with you. But, I'm rooted therefore something else must be causing the compatibility problem. Unlike you guys, I didn't change the dpi of the screen. The dpi change seems to be the common denominator here, and thus the dpi is more than likely the culprit.
Click to expand...
Click to collapse
Hmmm... but I have different DPI then official (140) and when unrooted apps are compatible again and I still have DPI 140... But maybe another idea - I updated market manually. If I think of it, that was maybe the time when appbrain shows as not compatible...
So, does anyone updated Android market manually too?
I did not manually update Market, but it did it automatically to the 3.1.3 version. I'll strip out the DPI change later today and report back.
I had the same problem so I tried changing back to 160 using blade buddy, nothing happened, until I accidentally turned it off. After boot, I checked market and it was fixed. So I tried going back to 200 using lcd density (which is temporary until you do a full reboot), the problem came back. I did a reboot, now back to 160 and it was ok again. So I tried blade buddy again and set it to 200 and saved it, full reboot, and it's still fixed. I hope this will solve your problem too.
Sent from my Dell Streak using XDA App
Just a follow up to my own OP...
I stripped out every mod I made and even replaced the original build prop from a backup I made when I first flashed the stock ROM.
No luck. Still the same apps show as incompatible with my device.
This may be one more motivation for me to dump the streak.
Anybody have any other ideas about what I can try?
I had problems with some of my apps not showing so I changed my fingerprint to 351, uninstalled the new market update, and froze the market updater. Using the old market without a problem and all my apps are available. HBO Go would not install with the new market, now it does. Running SD 191 perf 200 dpi.
rsfinsrq said:
I had problems with some of my apps not showing so I changed my fingerprint to 351, uninstalled the new market update, and froze the market updater. Using the old market without a problem and all my apps are available. HBO Go would not install with the new market, now it does. Running SD 191 perf 200 dpi.
Click to expand...
Click to collapse
How can I freeze the market from updating automatically using Titanium Backup?
donalgodon said:
How can I uninstall the Market update if it updated automatically?
Click to expand...
Click to collapse
First freeze market updater (I use Bloat freezer), then go to settings, manage apps, all apps, select market and then select uninstall updates.
You could also change market updater apk to bak
Has any CM7 users recently updated WWF? I did a couple days ago, and now its getting a FC upon opening. When I view the report crash info, it mentions "Screen size not currently supported"
Just wondering if anyone else had this problem?
Yes! I had the same problem as well. In the mean time, I've been forced to use an older version.
stinky634 said:
Has any CM7 users recently updated WWF? I did a couple days ago, and now its getting a FC upon opening. When I view the report crash info, it mentions "Screen size not currently supported"
Just wondering if anyone else had this problem?
Click to expand...
Click to collapse
My wife is pretty angry about this bug. Anyone find a solution other than using an older version? Anyone have a version that works that they can upload?
Words works for me if I change my lcd density from 160 to 180 or 200.
AndroidLonghorn said:
Words works for me if I change my lcd density from 160 to 180 or 200.
Click to expand...
Click to collapse
I thought about trying this. Last time I changed my LCD Density, a few other things got messed up.
I have just been using my Evo, until an update comes out, but may just have to resort to an older version. Seems like the easiest way for now.
Changed LCD to 180, and it works, plus I really like the overall look of the nook now. Icons arent spaced out too weirdly, and bigger fonts make me feel less blind.
I noticed an update available on my transformer today for words with friends. On the nook, it says the app is incompatible and won't update. i was hoping it was going to fix the last update. They suck.
AndroidLonghorn said:
My wife is pretty angry about this bug. Anyone find a solution other than using an older version? Anyone have a version that works that they can upload?
Click to expand...
Click to collapse
The old version that I found was from here:
http://forum.xda-developers.com/showthread.php?t=1220069
you don't need to increase it all the way into the eighties; if you change the density to 161 it will work and it won't cause the rest of your widgets to funkify
jackgibbs said:
you don't need to increase it all the way into the eighties; if you change the density to 161 it will work and it won't cause the rest of your widgets to funkify
Click to expand...
Click to collapse
This is exactly what I did with my girl's NC. Downloaded LCDDensity from the market and bumped it to 161. No strangeness with the widgets and words started perfectly. Thanks!
You could also buy it from the BN store. Their version looks a bit cleaner and works I think at 160 or 161.
~Leko
Anyone having issues with the newest update. Seems it won't connect to the server.
Yes it was acting up...
I used the dark mod now and don't update. No ads and cleaner:
http://forum.xda-developers.com/showthread.php?t=1220058
The update from just a day ago works fine now.
I bought the Sims 3 a long time ago for my daughter to play on my phone and I thought I'd load it up on the Touchpad for her, but it doesn't show up in a search in Android market, and doesn't show up in my app list as purchased. If I go to the market on my PC though, it's there and showing purchased. I try to send it to my TP as a HP GT-i9100 and it never sends it. My build.prop has been edited to a GT-i9100.
Thoughts on this issue?
There are threads on this topic already. The gist of it is you're going to need to sideload a backup from your phone. Changing your build.prop to a Nexus S will allow you to download it from the market, but once you launch it you'll still need to download the sum of the game from EA's servers, which won't be fooled.
You need to install the game on your phone, back up the apk and the downloaded data from the android system folder on the SD card, and then transfer them to your touchpad.
leftovermagic said:
There are threads on this topic already. The gist of it is you're going to need to sideload a backup from your phone. Changing your build.prop to a Nexus S will allow you to download it from the market, but once you launch it you'll still need to download the sum of the game from EA's servers, which won't be fooled.
You need to install the game on your phone, back up the apk and the downloaded data from the android system folder on the SD card, and then transfer them to your touchpad.
Click to expand...
Click to collapse
I searched and only one other thread came up, and it didn't pertain to my question. Thanks though! It's already installed on my phone so it'll be easy to do. Thanks for the reply.
Sent from my DROIDX using Tapatalk
From what I understand, EA has not updated the game for ICS and I am personally not convinced it can be made to work until (if!) they update it.
I had my build.prop set to a T989 Samsung Galaxy S II and under this setting it did show up in CM7 but it is not showing up with the same build.prop settings in CM9 which is making me think the issue is not the device setting but the actual version of the OS. Comments in the reviews seem to confirm it does not work with ICS and EA has not gotten off their ass to update the game since September, which is BEFORE ICS was even released.
I suppose it might be possible to obtain the apk from some, ahem, unofficial source (and before anyone gets their panties in a bunch I paid for the app a while back it just won't show in the market anymore) and sideload it.
Even if you do that and manage to get it to load and then load the data from another device there is still the issue that the game is made for 16:9 aspect ratio and will not work properly on 4:3. The only way I know of to fix that is to get hacked files that force a 16:9 ratio (with a portion of the bottom of your screen unusable) and I don't believe there is an ICS version of those files, just Gingerbread.
TL;DR - I'm not convinced it can be made to work under ICS and to even attempt it is a huge pain in the ass.
_Motoki_ said:
From what I understand, haEA has not updated the game for ICS and I am personally not convinced it can be made to work until (if!) they update it.
I had my build.prop set to a T989 Samsung Galaxy S II and under this setting it did show up in CM7 but it is not showing up with the same build.prop settings in CM9 which is making me think the issue is not the device setting but the actual version of the OS. Comments in the reviews seem to confirm it does not work with ICS and EA has not gotten off their ass to update the game since September, which is BEFORE ICS was even released.
I suppose it might be possible to obtain the apk from some, ahem, unofficial source (and before anyone gets their panties in a bunch I paid for the app a while back it just won't show in the market anymore) and sideload it.
Even if you do that and manage to get it to load and then load the data from another device there is still the issue that the game is made for 16:9 aspect ratio and will not work properly on 4:3. The only way I know of to fix that is to get hacked files that force a 16:9 ratio (with a portion of the bottom of your screen unusable) and I don't believe there is an ICS version of those files, just Gingerbread.
TL;DR - I'm not convinced it can be made to work under ICS and to even attempt it is a huge pain in the ass.
Click to expand...
Click to collapse
It works fine on ICS. I have it running on alpha .6. The problem is the unsupported touchpad resolution of the TP messes up all the onscreen touch buttons. Maybe EA will update it in the future.
danknee said:
It works fine on ICS. I have it running on alpha .6. The problem is the unsupported touchpad resolution of the TP messes up all the onscreen touch buttons. Maybe EA will update it in the future.
Click to expand...
Click to collapse
I wouldn't hold my breath. I don't think Android is much of a priority for EA right now.
I did a full wipe when updating to CM9 and reinstalled everything but haven't been able to reinstall Sims due to it as far as I can tell being blocked for ICS. Have you had luck getting it to show up in the market with a particular build.prop under CM9 or did you already have it installed from CM7?
I'm afraid the whole aspect ratio issue makes it not really playable though. I was using the hack posted here that forces 16:9 and it did work fine under that but those files were meant for CM7 and I have my doubts that they will work for CM9.
Anyway, it requires manually copying files, changing permissions and rebooting back and forth which is a pain in the butt. :-/