Ok I first tried LCD density Moder pro from market, BOOT LOOP, dont try it, had to odin back to stock.
Then I used my normal method, use root explorer go to system/build prop/ hold it down and choose open with text editor and changed the line from " ro.sf.lcd_density= 320" and change the 320 to 240, save and exit, reboot and profit.
The only problem is that the camera is off center and the dialer is also.
I just read of a new method for ICS and wondering if it will work on JB, this method you change the line "ro.build.characteristics=verizon" from verizon to ??? Tablet I guess, thats my question. Any help would be appreciated.
I hope there is a fix for the LCD Density Modder app I purchased that a year ago with my Galaxy Nexus and it was cool but it may need to be updated to support the 5.5"screen.
Related
Bought this game for my Nexus S. Trying to put it on my NC. Wouldn't install. Has anyone gotten this working yet?
Don't believe so. You may want to follow the thread about gameloft games, we've been able to get some working with hacked .apks, some with IMEI patches. I believe someone got Asphalt 5 working.
I can't even buy it from the market, cause it says my device is not compatible. Anyway around this?
I have this game on the Xoom and just bought it via market.android, I'll see if I can get it to run on the NC without an IMEI patch.
However, I will say this, the Need for Speed games are much better. I played Asphalt 6 on the Xoom for about 20 min and found it boring. It doesn't capture me like the NFS series. Again, your mileage will vary. I will post if I can get the bought version to DL and run using Chainfire.
The apk for samsung galaxy s version 3.2.2 works great with phiremod 7.1 for me without the need for chainfire.
FYI, I bought it during the recent sale and I installed and played this last night. I installed Chainfire first, so I'm not sure if that is needed or not. The only problem is the camera angles were all like pointed up over the car, so I'm not sure if it's the apk or maybe I need to adjust the DPI (on the stock 160 now).
ponyboy82 said:
FYI, I bought it during the recent sale and I installed and played this last night. I installed Chainfire first, so I'm not sure if that is needed or not. The only problem is the camera angles were all like pointed up over the car, so I'm not sure if it's the apk or maybe I need to adjust the DPI (on the stock 160 now).
Click to expand...
Click to collapse
I bought for .10 in recent sale as well and was unable to install on nook color from market. I then installed it as an apk with chainfire pro v3.3 and qualcomm plugin and it force closes. Any ideas? Thanks.
On a nook color CM7 stable 1200.
Which version .apk did you get? That matters much more than the version of CF3D.
The following versions are known to work on the NC:
Asphalt 6 1.0.4 xperia arc version (works with CF3d-qualcomm), 3.2.2 Galaxy S
I believe I had Chainfire setup to use the Nvidia plugin at the time. I didn't think to try any others. I believe I was using something like 3.1.9 for the Asphalt version (I would have to double check to be sure).
You should find the 3.2.2 version. You won't need chainfire at all to get it up and running (set it to powerVR if you already have it installed).
gallahad2000 said:
Which version .apk did you get? That matters much more than the version of CF3D.
The following versions are known to work on the NC:
Asphalt 6 1.0.4 xperia arc version (works with CF3d-qualcomm), 3.2.2 Galaxy S
Click to expand...
Click to collapse
Tried Asphalt 6 1.0.4 xperia arc version with CF3d-qualcomm which force closed
and 3.1.2 Galaxy s which played the intro movie and nothing else. Is there a 3.2.2?
Edit - again, I just tried to install 1.0.4 xperia and opened the app and i got - this app is not compatible with this device.
Purchased it for .10, it installs fine on Nook and phone, but will not run on either device.
Phone is rooted Moto Triumph.
This is one that I really wanted to try out!
The market version runs perfectly on my Nook (I have since uninstalled the 3.2.2 since now I can use an officially supported version. I have build.prop set to galaxy tab, IMEI from my serial # (both using DizzyDen's patch) and my LCD density set to 160 (set LCD for root).
gallahad2000 said:
The market version runs perfectly on my Nook (I have since uninstalled the 3.2.2 since now I can use an officially supported version. I have build.prop set to galaxy tab, IMEI from my serial # (both using DizzyDen's patch) and my LCD density set to 160 (set LCD for root).
Click to expand...
Click to collapse
Could you please share your build.prop?
Or you can use the Nexus S build.prop.
GT-I9023 works for me.
i think its
ro.product.device
ro.product.model
ro.device.somethinghere. forgot.
Make these changes:
ro.build.user=cowork03
ro.build.host=Sprint5
ro.product.model=SPH-P100
ro.product.brand=sprint
ro.product.name=SPH-P100
ro.product.device=SPH-P100
ro.product.board=SPH-P100
ro.product.manufacturer=samsung
ro.build.fingerprint=google/passion/passion:2.3.6/GRK39F/189904:user/release-keys
to the build.prop file in /system/ with either root explorer's text editor or ES file explorer in order to see the apps in the market. Sorry for not mentioning the .fingerprint before, the ROM i'm on already changed it so I didn't realize that it was needed.
Or if you have CM7 you can use these DizzyDen's IMEI generator settings:
Device_Manufacturer = Samsung
; If blank then the program will not edit build.prop
; If anything other than blank the program will edit build.prop to include manufacturer
Manufacturer_Device = SPH-P100
; If blank then the program will not include device in build.prop edit
; IF anything other than blank the program will include device in build.prop edit
; NOTE: No build.prop edit will occur if Device_Manufacturer is blank
Device_Model = SPH-P100
; If blank then the program will not include model in build.prop edit
; IF anything other than blank the program will include model in build.prop edit
; NOTE: No build.prop edit will occur if Device_Manufacturer is blank
This is how it reads in my !IMEIme.ini (part of the DizzyDen patch). This only works on CM7(since it already has the ro.build.fingerprint edits).
Thank you gallahad2000! Damn this game is addictive!
[and the graphics are seamless. Amazing performance]
I have a G Tablet, and have used Cyanogenmod 7.0.3 for some time. I thought I would upgrade from 1.1 to 1.2, so I could try some Honeycomb like goodness. Right. Not a good plan.
Thanks Roebeet for NVFlash!
So, I have been trying to reinstall what I had, and I have run up against some troubles. I now have Cyanogenmod 7.0.3 and Gapps 20110307 running on the Gtablet, but I am struggling with the market. At first, I could not get the market to run; all it would do was FC. Thanks to Google-fu, a change in the language to English (United States) got that repaired.
So, the only way I can get stuff installed is to revert back to 2.3.3 market. The new market sees my tablet as Malata Tablet. I have changed build.prop fingerprint, but in the Market on the device, the message I get is "Your device is not compatible with this item". On the web Market, it identifies my tablet as Malata Gtablet. If I downgrade the Market app, I can install Maps and Flash, but when Market upgrades those apps don't show up as apps in My Apps.
So, I need to change more in the build.prop, right? So what the heck do I change? I am not able to mess around for days on end to upgrade to 1.2, I just want to use the tablet for what I was; web, kindle, google reader. I can do that, but I want to fix this weird issue too!
Can anyone help me out? TIA!
What is your ro.product.device = in build.prop?
Try changing it to
ro.product.device=olympus
--
Fixed
Actually, the way I fixed the market issue, was to change the DPI in the build.prop from 161 to 160. Boom, everything works fine.....yes!
G tablet is back baby, I am waiting for cheaper quad core tablets before I even dream about upgrading.....sweeeeeeeet!
Where do I go to change the DPI in the build.prop. Sorry for being such a noob!
I've been told two ways to edit build.prop, one by using ES File Explorer (which is free) and the other by using Root Explorer (which isn't). However, the only way I know to install either is via the Market, which tells me they aren't compatible with my tablet.
I have a chicken-and-egg problem: I can't edit build.prop until I install one of those apps, and I can't install either app without editing build.prop first.
So hopefully there's another way... anyone?
Solo Jones said:
I've been told two ways to edit build.prop, one by using ES File Explorer (which is free) and the other by using Root Explorer (which isn't). However, the only way I know to install either is via the Market, which tells me they aren't compatible with my tablet.
I have a chicken-and-egg problem: I can't edit build.prop until I install one of those apps, and I can't install either app without editing build.prop first.
So hopefully there's another way... anyone?
Click to expand...
Click to collapse
net-widgetron-propeditor - An Android app to edit build.prop files - Google Project Hosting
http://code.google.com/p/net-widgetron-propeditor/
Download
http://www.estrongs.com/en/download.html
HOKAY. I've missed something somewhere. I've set the DPI to 160 rather than 161, but I still get the "not compatible" message.
... but I never give up when technology tells me no. Off to Google!
Solo Jones said:
I've been told two ways to edit build.prop, one by using ES File Explorer (which is free) and the other by using Root Explorer (which isn't). However, the only way I know to install either is via the Market, which tells me they aren't compatible with my tablet.
I have a chicken-and-egg problem: I can't edit build.prop until I install one of those apps, and I can't install either app without editing build.prop first.
So hopefully there's another way... anyone?
Click to expand...
Click to collapse
Someone else probably will answer, but you can get root explorer by using Amazon Market app which you can download and install and while they aren't as complete as the real "market" they also work and don't cause these kinds of problems. (you will have a better experience if you already have an Amazon account.)
Solo Jones said:
HOKAY. I've missed something somewhere. I've set the DPI to 160 rather than 161, but I still get the "not compatible" message.
... but I never give up when technology tells me no. Off to Google!
Click to expand...
Click to collapse
try changing ro.product.device=olympus in build.prop.
Sorry for being so lacking in knowledge on this, but, how do I get to "ro.product.device" to make the change? Where do I find this?
Thank you!
janovak1 said:
Sorry for being so lacking in knowledge on this, but, how do I get to "ro.product.device" to make the change? Where do I find this?
Thank you!
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showpost.php?p=17567049&postcount=97
Hi Guys....
Ive The Tab "BSNL Penta IS701c"
Which Is Rooted Also & Having No Problems....
But Some Apps Like Webroot Security,Kasper key Security ,Sketchbook Pro v2.5.1(Specially)
.
.
.
Ive Got Following details Like
"BSNL Penta IS701c"
Screen Resulution......800*480
But Showing 800*455 In Benchmark(maybe cause of status bar Which Get 25 pix hight)
So I cant open These Apps.......(maybe Other Problem)
But I Want To Use These Apps Any Professional/Programer Have Idea To Solve these issue?
Please Inform Of walkthrough Me ...
Replay as Soon As Possible.....
Thanx
Yes first you need to root the tablet
Then goto system folder via es explore and find build.prop. Long press on it and open with it es text editor and find lcd density chande the value of lcd density
Sent from my GT-S5830i using xda app-developers app
Hi there... recently Flashed 5.1 on my Nexus 5, rooted my device then went ahead and tried to change the DPI like I always do after a flash and its not working...
I have tried setting the value ro.sf.lcd_density to 400 and it wont register.
The setting has definately been modified when i review the build file...
I have tried various apps that change DPI too and none of them work
Any ideas?
can you attach build.prop (from the rom's zip if available and from the phone's system partition) ?
Having the same issue on nexus 6. Changing to 520 DPI will boot loop, using 500 DPI doesn't change anything (some text in some apps is smaller, but everything else is the same).
Hello everyone
i tried to change screen resolution on my redmi note 3 qualcomm sd650 kenzo 2gb version with miui 8.0.6 global stable rom rooted xposed ( yea i did everything needed unlocking bootloader and modding boot.img and twrp 3.0.2 installed ) ... when i apply 720x1280 320DPI (via terminal or the apps like resolution changer v1.4 or screen shift v2.1 beta
the hardware capacitive keys (back, home ,menu) stop working so device turnes useless if you dont know how to turn on the quick ball setting which gives you software back , home and menu buttons which i dont like to use ... if i go back to 1080x1920 480DPI it works fine again ... any ideas how to fix this ?
Also screenshots looks messed up if you use 720p resolution ... its looks like they capture the upper left corner of the 1080p screen only
Please help me fix this ... i really want to have the extra performance out of this phone
We need a solution for this ... Please guys
sniper9911 said:
Hello everyone
i tried to change screen resolution on my redmi note 3 qualcomm sd650 kenzo 2gb version with miui 8.0.6 global stable rom rooted xposed ( yea i did everything needed unlocking bootloader and modding boot.img and twrp 3.0.2 installed ) ... when i apply 720x1280 320DPI (via terminal or the apps like resolution changer v1.4 or screen shift v2.1 beta
the hardware capacitive keys (back, home ,menu) stop working so device turnes useless if you dont know how to turn on the quick ball setting which gives you software back , home and menu buttons which i dont like to use ... if i go back to 1080x1920 480DPI it works fine again ... any ideas how to fix this ?
Also screenshots looks messed up if you use 720p resolution ... its looks like they capture the upper left corner of the 1080p screen only
Please help me fix this ... i really want to have the extra performance out of this phone
Click to expand...
Click to collapse
Do you want to change dpi only ? Or you want to change Resolution as well ?
If you want to change dpi only.
Go to /system/build.prop
Insert this line in the end
ro.sf.lcd_density = value you want.
Reboot.
I am using 340 dpi and everything works perfect
gulshanstrider said:
Do you want to change dpi only ? Or you want to change Resolution as well ?
If you want to change dpi only.
Go to /system/build.prop
Insert this line in the end
ro.sf.lcd_density = value you want.
Reboot.
I am using 340 dpi and everything works perfect
Click to expand...
Click to collapse
Dpi changes fine but when you chanfe resolution also it makes capacitive keys not working
I need resolution change man ... Please i need this fix
Bumping up my request
had the same issue but no longer persistent
ok try this
using root explorer go to directory /system/
back up your build.prop
open build.prop using text editor, remove any new tweaks caused by the app you mentioned on OP.
then add "ro.sf.lcd_density=xxx" change xxx to the value you want, i woulf suggest 480 (default), 440, 400 just dont use weird numbers or apps will fc (rare tho),
uninstall the app you mentioned on OP
next is the most important part
reboot into recovery , wipe cache and dalvik , then reboot your phone and wait until your phone is being optimised.
MIUI is a super-customised skin. You can't be sure about tweaks which are working for vanilla skin would work for MIUI. Most of the features are embedded in MIUI's framework, so weird things would happen if you edit build.prop. So, I would suggest, if you want 720p res on your phone, first install a custom ROM such as CM14.1 etc.