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]
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.
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.
Is there any way to calibrate screen sensitivity? My OnePlus 6 has too much sensitive screen. Device isn't rooted yet so I tried to change sensitivity on Nexus 4. I added touch.pressure.scale=0.3 to build.prop (I checked a few different values from 0.01 to 10) and nothing changed. Also, I found touch_dev.idc file in /system/usr directory. The comment in this file says: "Input Device Calibration File for the Mako touch screen.". There are a few number parameters (like touch.pressure.scale or touch.size.scale). I tried to change them but it didn't make any effect. Of course, I rebooted device after every change.
Should I do something more to apply my changes? Or should I change values in any other places? Maybe some kernel modifications?
Hello Everyone. (Assalamualaikum)
This is my first thread on XDA.
Here is the problem - i just flash https://forum.xda-developers.com/galaxy-star/development/port-resurrection-remix-t3429810 this rom yesterday. And now, i can't save my BUILD.PROP (in stock rom, file saved without any problems). ALSO i can't install most of my favorite apps as - Gboard, kiwi, xposed etc.
This is what shown, when i try to save modified build.prop --> java.io.IOException: error after write by shell
So, is this problem to the rom only or there is any other way to solve this two problems???
1. build.prop showing - java.io.IOException: error after write by shell
2. can not install some apps which i could in stock rom
Walikum-usalam
This can happen if your phone does not enough permissions to change it and of the apps they are not installing because the apps are not supported by the ROM
If you want to change the build.prop and install apps you can install Teamviewer in your computer and tell me the partner ID and password
I will connect to your computer and fix it
Assalamualaikum everyone and resurrecting this thread again lol. But im kinda having a issue which is kinda similar, where if i change my build prop to pixel 5 my gboard creates a gap in the bottom area which mimics the 16:9 ratio display but my phone doesn't have a 16:9 display. So any possible fix to this as i want to get rid of this odd blank space while typing? thank you