Does anybody know how to change the DPI on latest ICS leaks? Tried app that worked on LP2, LP5 but its not working on these new fw.
Download root explorer (make sure you're rooted) then go to system/buildprop then look for ro.sf.lc_density. Edit that value to your choosing then save and reboot
Be careful, i'm not entirely sure but i think that changing DPI in LPB causes problems with the phone, on LPH i don't know, sorry
And yes the method to change is like said enrygie...
I was looking rather at som app that can do that for me (yep I am lazy ), but changing value in build.prop works so far. Phone booted and so far no FC or anything bad happened. So thx.
That's great! Keep testing
Enviado desde mi GT-I9100 usando Tapatalk
Related
[Q] "This applicatiln is incompatible with you're device" for compatible apps
Hi guys . I just wanna ask if all of you experiencing this. (Not only me).
This past days. Android market changed to google play. If i open google play some of the apps says, "This applicatiln is incompatible with you're device" . Not like android market, it only shows the applications compatible with you're device. Do you experiencing it guys?
are you using Stock ROM or mod?
Some of the mods need that you flash a fix for them to work properly... and also depends if you updated the OS (ICS 4.0.3 or 4.0.4) maybe, if the developers of the app have not updated it.
*also if you do use a modded ROM, some change the dpi settings. Some apps have issues when it's too low.
cyberboob said:
are you using Stock ROM or mod?
Some of the mods need that you flash a fix for them to work properly... and also depends if you updated the OS (ICS 4.0.3 or 4.0.4) maybe, if the developers of the app have not updated it.
*also if you do use a modded ROM, some change the dpi settings. Some apps have issues when it's too low.
Click to expand...
Click to collapse
Thanks for the reply cyberboob. It really makes meaning, what you said.
Below are info that you asked
Rom - ICS 4.0.3 mod (I9100XXLPQ_I9100HTSLP3_I9100NELP2_HOME.tar)
Everyone says to change the DPI settings, can you pls tell me a correct and easy way to do that. Its very bad not to have many apps that i really need in google play. Thanks again
pathslug said:
Thanks for the reply cyberboob. It really makes meaning, what you said.
Below are info that you asked
Rom - ICS 4.0.3 mod (I9100XXLPQ_I9100HTSLP3_I9100NELP2_HOME.tar)
Everyone says to change the DPI settings, can you pls tell me a correct and easy way to do that. Its very bad not to have many apps that i really need in google play. Thanks again
Click to expand...
Click to collapse
Have a look here http://forum.xda-developers.com/showpost.php?p=23438841&postcount=11877
No worries. This site has tons of people who want to help.
As 078gregory posted the link... that's the best way to do it... but sometimes you also need to delete the exact same setting - meaning:
ro.sf.lcd_density=240 ---it appears twice (one further down)
ro.sf.lcd_density=240 ---and your values might already be different (I'm guessing yours is set to a lower number than 240 already), could be 180 or something.
If your settings are 180 or whatever... try changing them to 190+ (mine's on 210 now and no problems with any apps). Good luck.
I was finally able to root and checked the DPI
As you said cyberboob, i have two entries
ro.sf.lcd_density=240
ro.sf.lcd_density=240
I f i change that it affects my screensize like anything. I still have the same problem and not sure how to fix this. I tried changing the dpi to different values but nothing works. The apps that show incompatible are still the same.
im having a similar problem
i flashed LPS the other day but didnt like ICS, i reverted back to LA4 with CWM but google play app and website thinks im still on ICS so i get updates for things like Flash, Gmail, Talkback and YT but then get errors saying a need a newer SKD version.
Also apps i have installed some say incompatible because Play thinks im still using ICS but infact on Gingerbread.
Really confused as to why this is happening.
*Updated to Sensation fingerprint*
Can't download or even play certain apps or games such as Gameloft's N.O.V.A.3?
Follow the below steps to make your HTC ETO 4G LTE disguise itself as a HTC Sensation to get the best of the Google Play Store.
Tested working on stock ROM with Root and SU.
Modern Combat 3, N.O.V.A. 3 tested to work perfectly. All other Gameloft games should work and show up in market.
Please note, if you have a custom ROM, you probably do not want to use this. It will overwrite your ROM creator's settings. It will probably work, but it will take away certain features of their build.prop tweaks.
Users are saying that this kills Google Wallet. I cannot confirm this since I don't use it. Use at your own risk. Please update us if it does or not.
You must be rooted!
BACKUP YOUR CURRENT BUILD.PROP
1. Clear Google Play Store Data (Settings, Apps, All, Google Play Store, Clear Data)
2. Download the build.prop I have attached at the end of this post.
3. Unzip it
4. Use a file explorer such as ES File Explorer and navigate up to /system
5. Copy and paste it over your current build.prop in/system
6. Reboot phone
Clear as mud
*Edit*
Removed manual way to update (Hardcore DIY'ers can Google it)
Updated build.prop to HTC Sensation (pyramid). Apps were showing up before with the Galaxy SII build.prop changes, but downloaded files weren't compatible with our phone. Sensation makes for a better fingerprint.
Thanks for this! Only one thing:
People need to understand that if they're not on the stock ROM (that this build.prop is based off of) that they are risking losing whatever modifications their ROM devs added into build.prop.
Different devs do different things in there....blindly replacing your ROM's build.prop is usually a bad idea.
smw6180 said:
Thanks for this! Only one thing:
People need to understand that if they're not on the stock ROM (that this build.prop is based off of) that they are risking losing whatever modifications their ROM devs added into build.prop.
Different devs do different things in there....blindly replacing your ROM's build.prop is usually a bad idea.
Click to expand...
Click to collapse
True... which is why it's important to manually make the change to the build.prop on your rom. Takes a little work, but worth it.
If you follow these instructions, you cant mess it up.
smw6180 said:
Thanks for this! Only one thing:
People need to understand that if they're not on the stock ROM (that this build.prop is based off of) that they are risking losing whatever modifications their ROM devs added into build.prop.
Different devs do different things in there....blindly replacing your ROM's build.prop is usually a bad idea.
Click to expand...
Click to collapse
Meaning such as CM and MIUI and such? Anything based off of 1.13 or even 1.12 is OK right? Im just curious about that, thats all. Ive been wanting to plat Tigers Woods, and for a $5.24 game, im pretty pissed they wont even remburse me for that ****. Thannks brotha. Thanks to the OP as well
reverepats said:
Meaning such as CM and MIUI and such? Anything based off of 1.13 or even 1.12 is OK right? Im just curious about that, thats all. Ive been wanting to plat Tigers Woods, and for a $5.24 game, im pretty pissed they wont even remburse me for that ****. Thannks brotha. Thanks to the OP as well
Click to expand...
Click to collapse
Meaning anything that's not stock. Viper, PokeROM, Fresh, whatever.
Each developer tends to make their own build.prop edits. If you just make the changes to the stock build.prop that the OP attached and you're running any custom ROM you're overwriting whatever they may have done. Unless your Dev puts the change into his/her ROM, or someone makes a flashable zip for you, for your ROM, just grabbing a random build.prop and using it because it has the edits you want is a bad idea.
I'm using Joelz9614 rom just manually edit. A safe rule is never paste over the prop when you can do the edits yourself if you're not sure if it's modded
Sent from my GT-P6210 using Tapatalk 2
Oh and great post op. You're a life saver!
Sent from my GT-P6210 using Tapatalk 2
Kidromulous said:
I'm using Joelz9614 rom just manually edit. A safe rule is never paste over the prop when you can do the edits yourself if you're not sure if it's modded
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
Exactly.
One more note guys this will kill google wallet mine was still stuck so not sure about those already set up but changing your device to a non wallet device means no wallet. Just thought I'd add this though we are bound to see people ask about it anyway. Perhaps that can be added to the op
Sent from my GT-P6210 using Tapatalk 2
so i screwed up! i edit manually didnt work maybe i mis spelled.. and then thought i could just flash that build prop posted...and i had just flashed FRESH 5.0 and just kinda now read that i should have changed the build prop with that rom untill the developer had that built in.. any ideas what the hell i can do now?
BAttitude7689 said:
so i screwed up! i edit manually didnt work maybe i mis spelled.. and then thought i could just flash that build prop posted...and i had just flashed FRESH 5.0 and just kinda now read that i should have changed the build prop with that rom untill the developer had that built in.. any ideas what the hell i can do now?
Click to expand...
Click to collapse
OPen the zip for the Fresh ROM, go to /system and pull out build.prop. Push that to your phone, and change the permissions.
Or, flash Fresh over your current installation without wiping.
You could push the original build.prop to your phone from the Rom you are using or reflash
Not Sent
Kidromulous said:
One more note guys this will kill google wallet mine was still stuck so not sure about those already set up but changing your device to a non wallet device means no wallet. Just thought I'd add this though we are bound to see people ask about it anyway. Perhaps that can be added to the op
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
Won't Gameloft eventually make the market change so that the One-X variants are downloading the HD versions? I would only do this if you have to have it now...
BAttitude7689 said:
so i screwed up! i edit manually didnt work maybe i mis spelled.. and then thought i could just flash that build prop posted...and i had just flashed FRESH 5.0 and just kinda now read that i should have changed the build prop with that rom untill the developer had that built in.. any ideas what the hell i can do now?
Click to expand...
Click to collapse
You could reflash your ROM or ask the dev for this build.prop file to paste over your corrupted one.
it was a damn brick and i could even get to recovery screen... i did volume down and power and the bottom buttons would flash and then finally stopped i then press volume down and power and magiclly i got to the bootloader then the recovery and reflasheed
You removed the changes that needed to be made manually? I applied the Samsung changes and now would like to apply the new sensation changes. I guess I'll dig through the build.prop and check which lines are different
To the OP, why would you remove the changes to the file that can easily be done manually??? It's a simple mod that can be done. Users NOT in the know will replace their their file with yours, only to end up with a mess because they are on a different rom that has somewhat different parameters than what's in your attachment.
gpz1100 said:
To the OP, why would you remove the changes to the file that can easily be done manually??? It's a simple mod that can be done. Users NOT in the know will replace their their file with yours, only to end up with a mess because they are on a different rom that has somewhat different parameters than what's in your attachment.
Click to expand...
Click to collapse
Well I hope these heed his warning or perhaps the thread and they should be ok.
Sent from my EVO using Tapatalk 2
Deleted
fldash said:
Won't Gameloft eventually make the market change so that the One-X variants are downloading the HD versions? I would only do this if you have to have it now...
Click to expand...
Click to collapse
I have nova 3 now so I needed to do it before this it didn't work on my phone
Sent from my EVO using Tapatalk 2
just gonna ask here cause i cant post on android development..
im on wanam v12 and im just wondering is it possible to change dpi or atleast is changing dpi can be done on any rom?
i tried dpi changing apps but nothing happened so i will have to change it in build.prop was it..
plus i wanna know if its risky
TIA
Tricks25 said:
plus i wanna know if its risky
Click to expand...
Click to collapse
1) Make a Nandroid
2) Edit build.prop to your liking
3) Works and looks fine? Enjoy! Goto 5)
4) Looks crap/doesn't work as planned/bootloop? Restore Nandroid
5) Use phone
i'm running cm7.2 ultimate and previously used swype beta. however, this has expired as of today.
i'm wondering if i can extract the built in swype from the stock rom file(s).
i have a multiple files stock rom which contains swype (with the correct language included).
in which file can i find the swype.apk?
and it i succeed in extracting swype from te stock rom, will i be able to use it in my cm7.2 rom?
i read about a check that swype performs with build.prop so how can i make swype actually work on my ace with cm7.2?
(what should i edit in build.prop to succeed in the check and does it corrupt my rom when i edit my build.prop file?)
Brother install stock rom first and then create backup of swype file using root uninstaller ( i use that) and install it with correcting permissions using root explorer
Try lucky patcher on your expired beta of swype it may work
Hit thanks cos you wont die
Next time use Q&A THREAD, keep general thread clear!
DutchArjo said:
i'm running cm7.2 ultimate and previously used swype beta. however, this has expired as of today.
i'm wondering if i can extract the built in swype from the stock rom file(s).
i have a multiple files stock rom which contains swype (with the correct language included).
in which file can i find the swype.apk?
and it i succeed in extracting swype from te stock rom, will i be able to use it in my cm7.2 rom?
i read about a check that swype performs with build.prop so how can i make swype actually work on my ace with cm7.2?
(what should i edit in build.prop to succeed in the check and does it corrupt my rom when i edit my build.prop file?)
Click to expand...
Click to collapse
You may ask someone who has the sock to upload here the file
Sent by my GT-S5830i with Tapatalk 2
Its called Swype.apk and you can extract it from systen using root explorer. I am sorry that i cannot upload the file.
Sent from my GT-S5830i using Tapatalk 2
Please, take a look at my signature links.
thanks all,
I must say my question was not clear enough. I had a stock rom available and from that rom I've extracted the Stock Swype. I tried to get it to work using the instruction from Marine for another Phone. But unfortunately, It didn't work.
I'm on the ultimatum rom and extracted the swype from a 2.3.6 stock rom.
place the apk and libswypecore.so in the right folder and fixed permissions. i synced the files and rebooted the Phone as instructed but after that, Swype is available but doesn't work.
Anyone know what else I can do to fix this? Should I edit my build.prop?
DutchArjo said:
thanks all,
I must say my question was not clear enough. I had a stock rom available and from that rom I've extracted the Stock Swype. I tried to get it to work using the instruction from Marine for another Phone. But unfortunately, It didn't work.
I'm on the ultimatum rom and extracted the swype from a 2.3.6 stock rom.
place the apk and libswypecore.so in the right folder and fixed permissions. i synced the files and rebooted the Phone as instructed but after that, Swype is available but doesn't work.
Anyone know what else I can do to fix this? Should I edit my build.prop?
Click to expand...
Click to collapse
What do you mean with "is available but doesn't work"??
When you switch in swipe keyboard it crashes? It force closes?
Inviato dal mio GT-S5830i con Tapatalk 2
GibboAce said:
What do you mean with "is available but doesn't work"??
When you switch in swipe keyboard it crashes? It force closes?
Inviato dal mio GT-S5830i con Tapatalk 2
Click to expand...
Click to collapse
no forced closes. I can swype, but it doesn't show the words I swype. My entry field stays empty.
I've checked the apk / swype files and all the dictionary files are in there.
I read another thread here at XDA which told something about swype checking the build.prop file. So i've checked my build.prop with the build.prop in the stock rom. There were some differences (cooper instead of GT-S5830). So i've editted my build.prop, saved it and rebooted. After that, my phone wouldn't boot anymore so now i'm busy downloading the latest version of The Ultimatum rom to get my ace working again..
so editting build.prop isn't really the best option to do (unless you really confident that you know what you're doing, which I'm not).
DutchArjo said:
no forced closes. I can swype, but it doesn't show the words I swype. My entry field stays empty.
I've checked the apk / swype files and all the dictionary files are in there.
I read another thread here at XDA which told something about swype checking the build.prop file. So i've checked my build.prop with the build.prop in the stock rom. There were some differences (cooper instead of GT-S5830). So i've editted my build.prop, saved it and rebooted. After that, my phone wouldn't boot anymore so now i'm busy downloading the latest version of The Ultimatum rom to get my ace working again..
so editting build.prop isn't really the best option to do (unless you really confident that you know what you're doing, which I'm not).
Click to expand...
Click to collapse
try better keyboards like swiftkey or x touchpal ( i recommend x touchpal as u can conver that app to system and working, will not take space in internal memory as our ace is low with internal). hope i helped u
I don't think so...
Both Swiftkey and Touchpal X take up a heck lot of space, unlike what you claimed.
For example
Touchpal X : ~15MB
Stock Swype : ~3MB
And the stock Swype is better, in my opinion.
Sent from my CM7 GT-S5570I
Hi,
I want to change DPI on my I9300 with latest stock 4.3 Samsung ROM (rooted) - XXUGMJ9 so I edited the /system/build.prop file using Solid Explorer and changed there ro.sf.lcd_density to 245. After reboot I didn't notice any change. I tried the Texdroider DPI changer but it's already saying that my DPI is 245. Any ideas what I'm missing? Do I have to install/flash anything else?
Thanks.
There can be 2 lines ro.sf.lcd_density in your build.prop maybe u missed one.
Sent from my GT-I9300 using Tapatalk
LOL, you were right, I changed only one line but there are two lines in the build.prop. Thanks!