Related
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...
Some applications look misaligned due to the higher resolution on our phones. Two of the applications I use that have this issue that I have noticed so far:
Heytell is an app that does this on our phones.
Application Protection seems to only use half of the screen where on my other phones it would take up the entire screen when asking for passcode.
This is a known issue. The only thing you can do is contact the dev of your apps and let them know.
The Spare Parts Plus! app has a feature "Enable/Disable compatibility mode to allow Apps to work at full screen size on Galaxy Tab and other large screen devices" but I don't have my Rezound yet to test it.
I thought Honeycomb had the ability to do that on it's own in every app without 3rd party support. My Xoom did it without 3rd party.
AtLemacks said:
I thought Honeycomb had the ability to do that on it's own in every app without 3rd party support. My Xoom did it without 3rd party.
Click to expand...
Click to collapse
I believe he is referring to the original Galaxy Tab that ran Froyo (Or gingerbread, I can't remember xD).
I'll try this out though, I believe it should work fine this way. It's just a scaling issue with background elements.
Ahh, ok. Report back! I don't have any issues with my apps, and don't intend to download any that require it just because, lol.
I notice sometimes when I'm playing videos in Dice Player, they start playing in this tiny view(thumbnail like) in the of the screen. I'll have to use my fingers to pull it out to fill the screen.
I am writing to get some details or clarification on the LCD Density of the Droid X2.
I have noticed on several sites that the lcd density is ~256 ppi pixel density. PhoneArena and GsmArena both list this. Wikipedia has useful information, but not in this aspect, or it is nested under a subject somewhere. I noticed in the standard stock Verizon rom in the build.prop that it is set to 240, I also noticed this is the same setting for the CM7 build also.
My conclusion is that it is set this way for app compatibility? I understand that it can make the resolution smaller or larger depending on the setting. I have with other phones, changed the density and some looked and performed better (Possibly my imagination?), but it broke some apps and thoroughly pissed off Android Market. By The Market statement I mean that many apps were reported as "not compatible with your device".
*The easiest thing would be a explanation of the pros and cons of this setting/adjustment.
*Also a tip on how to fix the market, along with apps that get cranky when adjusting this setting. (It may be possible that the market and app issues are gone now, but making sure of this) I have skimmed some resources but none that were detailed enough or were just too excessive. The threads here, what few that are related get turned into an app fest discussion.
(Point is not what app to use or not to use to adjust density).
Please be simple and to the point, unless you truly know what you are talking about. I thank everyone who contributes to this discussion.
It's interesting you point this out. I have long suspected app issues are with the odd PPI of the X2.
In calculating the true density, I come up with 256.7 PPI. That means it falls into the hdpi catagory. However, you are right about the build.prop saying it is 240 PPI. I think this is just set as the minimum for the app to appropriate the correct layouts.
I doubt this actually has to do with the issue you are having. A lot of developers do not allow certain apps to work on devices for which they have not tested- although they shouldn't be appearing in our market in the first place.
To fix the market freeze the market auto updater with your favorite bloat freezer. Boot into 240 dpi. Go into settings then manage apps then the market and clear data. Go into market and click accept and back out. Then boot into preferred dpi. This should fix any issues. If they arise, repeat. This worked for me.
Sent from my MB870 using xda premium
Hey there. I'm very curious as to what the proper steps to change this setting are. I don't want to just go into my build.prop and screw some things up. I found the line. Should I just backup my phone, backup the build.prop and then edit the line and reboot my phone? Thanks for anty help.
Sent from my MB870 using XDA App
Reservation 1
.......Reserved for possible future usage on this thread
Hey guys,
I am running jasmine ROM 4.0,the latest version and im having trouble lowering the dpi. I want to lower the dpi to 420 but when i do the phone/contacts app stops working and so does quick remote (i havent tested every so, those are the two I've noticed). I have tried 560 which works but is still a bit big for me. I tired 480 but I have the same issue. Does any one know how to fix this? It worked fine on the aosp/cm based roms but I like the stock roms better so far and don't want to switch
Edit: the same issue happens on all the stock roms I've tried.
Bump. This is still a really annoying issue for me. Can anyone help?
r3xx3r said:
Bump. This is still a really annoying issue for me. Can anyone help?
Click to expand...
Click to collapse
Have you confirmed others are able to go that low?
I don't know what the limits are, but I would think at some point apps physically wouldn't be able to adapt. This may be the issue, just guessing though.
bweN diorD said:
Have you confirmed others are able to go that low?
I don't know what the limits are, but I would think at some point apps physically wouldn't be able to adapt. This may be the issue, just guessing though.
Click to expand...
Click to collapse
I think by others you mean either apps or roms. And it would be yes both. Only the apps I mentioned in the OP didn't work. I didnt test every app, but a lot of them worked fine. Also, aosp roms don't seem to have this issue, obviously quick remote isn't on aosp roms, but none of the apps I use on aosp/cm based roms had an issue. I also tried changing the dpi to 420 for the whole system, than using an xposed module to change just the dpi of the apps I knew didn't work to stock. But I had issues with network connectivity. I'm going to try just changing the dpi of the apps I want and know work to 420.
Sorry about this post. I wiped my phone and started from scratch and just changed the dpi of a few spots, including Nova launcher with app settings from xposed and it seems to work now.
r3xx3r said:
Sorry about this post. I wiped my phone and started from scratch and just changed the dpi of a few spots, including Nova launcher with app settings from xposed and it seems to work now.
Click to expand...
Click to collapse
When I said others, I actually meant, other people.
Glad you got it worked out.
Hello all! I have searched XDA for a similar issue but can't seem to find anything. I find it hard to believe this hasn't been asked before, so I must be using the wrong verbiage.
For some reason, certain apps are getting killed off when they aren't the foreground app. I could be playing a game, hit the recents button and switch to hangouts to type out a text, switch back to the game, and the phone reloads the entire game. This is extremely frustrating as you can imagine, but games aren't the only apps this happens to as pretty much any app does this, with the exception of Hangouts and a few others. There doesn't seem to be any rhyme or reason to it either, because it's not limited to only apps that take up large amounts of ram like games. I've checked my free ram available while running Hearthstone, and it never drops below 500 it seems. I am running SKyDragon's version 9.0, Sense 7, LP 5.02. I know LP had a memory hole issue when it first came out, but I thought the version of SkyDragon I have fixed it long ago. Thanks for any help!
Well Ok then. Does anyone know if this inherent to LP with the known ram issues or is this something else?
Euphoria64 said:
Well Ok then. Does anyone know if this inherent to LP with the known ram issues or is this something else?
Click to expand...
Click to collapse
Don't know if its a problem with LP in general. But Sense ROMs have always been notorious for high RAM usage, as well as aggressive killing of apps. You might try a GPE or AOSP ROM, to see if it helps.
Thanks for the reply. Is there any way to modify the phone's inherent management of apps and memory? The only thing I could find was changing the minfree values. I'm not super familiar with how exactly it works though. I've read a brief overview of it, but when I changed Empty App to a lower number (200), it doesn't seem to make a difference. I have a feeling I'm not understanding it correctly though. Like I said in my first post, the free RAM amount never dips below 500, so it's not killing apps because it's running low on RAM. smh
Can try a different kernel,memory is usually controlled there.