I backed up my build.prop as I edited a copy. Now I reverted to the old one and I am having error. I am guess I might have screwed up the backup somehow.
Could someone please verify a couple things below in the original build.prop?
ro.product.model=MB860
ro.product.model.internal=MB860
ro.product.brand=MOTO
ro.product.name=BELCA
ro.product.device=olympus <------?
ro.product.board=olympus <------?
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=CA
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OLYFR_U4_1.5.7
ro.build.display.id=OLYFR_U4_1.5.7
ro.build.version.incremental=1299003836
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Tue Mar 1 09:39:40 PST 2011
ro.build.date.utc=1299001180
ro.build.type=user
ro.build.user=fpgh48
ro.build.host=ca25rhe85
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=MB860
ro.product.model.internal=MB860
ro.product.brand=MOTO
ro.product.name=olyatt
ro.product.device=olympus
ro.product.board=olympus
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=olyatt
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=olympus-user 2.2.1 OLYFR_U4_1.5.7 1299003836 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/olyatt/olympus/olympus:2.2.1/OLYFR_U4_1.5.7/1299003836:user/ota-rel-keys,release-keys
# end build properties
Thanks for this, good to know I didn't screw things up.
Hope this helps you as little this is a stock build prop from 1.5.7 from ATT
What Kinda Error Are you having ?
Certain apps a opening up in a smaller resolution and not using the full screen when they used to open up in full screen. Also some apps that worked before are now force closing, this all happened after I copied the build.prop and edited it for use of a game.
Try to clear your dalvic cache,after checking build prop if you want I will post my whole build prop maybe there was a setting changed. I know I saw some commands about Res. Text back let me know I will post whole file also like I said try to clear the dalvic cache. You can download a app off market to do it or use cwm if you have it installed
AT&T ATRIX - VERSION 2.3.4 ROOTED BL UNLOCKED
I have tried to clear the devik cache and it didn't work.
Here is the build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OLYLA_U4_0.37.23
ro.build.display.id=OLYLA_U4_0.37.23
ro.build.version.incremental=1306604023
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.2
ro.build.date=Mon May 23 10:46:32 BRT 2011
ro.build.date.utc=1306158392
ro.build.type=user
ro.build.user=wmb050
ro.build.host=zbr05lnxdroid07
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=MB860
ro.product.model.internal=MB860
ro.product.brand=MOTO
ro.product.name=BELCA
ro.product.device=olympus
ro.product.board=olympus
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=olympus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=olympus-user 2.2.2 OLYLA_U4_0.37.23 1306604023 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/BELCA/olympus/olympus:2.2.2/OLYLA_U4_0.37.23/1306604023:user/ota-rel-keys,release-keys
# end build properties
#BEGIN ikolympus-145 ndkj78 04/29/10 add properties for RIL
rild.libpath=/system/lib/libmoto_ril.so
#ikolymp-874 increment channels to support EFEM
persist.ril.mux.noofchannels=9
persist.ril.mux.ttydevice=/dev/ttyHS3
#Begin IKOLYMP-2372 jqc837 31.aug.10 Short music file set as ringtone does not play in loop when receiving incoming call
#Begin IKOLYMP-425 jqc837 31.aug.10 ro.cdma.home.operator.numeric should not be set
ro.telephony.call_ring.multiple=false
#End IKOLYMP-2372 IKOLYMP-425
#added property for modem ikolympus-203
persist.ril.modem.ttydevice=/dev/ttySPI0
#added property for default RIL mode to be UMTS ikolymp2180
persist.ril.modem.mode=2
#IKOLYMP-4257 add feature GENERIC_OEM_HOOK flag
#IKOLYMP-4894 add feature MUX_PANIC_NOTIF flag
#IKOLYMP-5747 add feature BDTSE_FOR_DTMF flag
#IKOLYMP-7714 Remove feature BDTSE_FOR_DTMF. Revert to DTSE for DTMF
#IKOLYMP-8033 Restore BDTSE_FOR_DTMF.* Remove GENERIC_OEM_HOOK (no longer used)
persist.ril.features=0x24
#IKOLYMP-9894 Increase the PPP max failure threshold to 12
#IKOLYMP-10006 Increase the PPP max failure threshold to 16
persist.ril.pppd.start.fail.max=16
#end
#IKOLYMP-9157 libgps send_rds retry number+1
persist.libgps.send.rds.retry=4
ro.hdmi.mirror.enable=false
ro.hdmi.default.app=
hw.overlay.path.config=
# temporary enable AT&T NSUI feature from system prop.
# This should be removed once Flex is enabled in Olympus.
ro.mot.FTR.NSUI=true
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=240
dalvik.vm.heapsize=32m
# Enable FP sensor
ro.mot.hw.fingerprint.enable=1
# required for UDD backup tcmd
ro.mot.hw.calibratedImager=1
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
#For enabling Wispr Feature
ro.mot.wifi.hotspot=0
# To enable Google Froyo Tethering (USB & WIFI hotspot)
ro.tether.denied=false
# To set wifi (AP) driver's firmware path
ro.wifi-ap.fw-path=/system/etc/firmware/wifi/sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin
# Enabling EONS feature IKOLYMP-1962
persist.cust.tel.eons=1
ro.opengles.version = 131072
# For docked touchpad keyboard map
android.keylayout.evfwd=/system/usr/keylayout/evfwd.kl
android.keychar.evfwd=/system/usr/keychars/evfwd.kcm.bin
# To send 70 touch events per second
windowsmgr.max_events_per_sec = 70
debug.mot.extwmlog=0
debug.mot.extamlog=0
#proximit sensor screen off delay
mot.proximity.delay=450
#proximit sensor disable touch distance
mot.proximity.distance=60
# Enable HAC support
ro.mot.hw.HAC=1
# BEGIN Motorola, a17262, 8-Dec-2010, IKXOLYMPLA-93 turn off entitlement check
ro.mot.entitlement_check=false
# END
# BEGIN Motorola, w30495 IKOLYMP-9553, add property to control maximum number of hidden apps
ro.MAX_HIDDEN_APPS=50
# END
# Enable APN authentication for a specific MCCMNC - IKOLYMP-9071
umts.apn_authentication.enable=302610
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=false
ro.default_usb_mode=0
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r10
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.ms=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.config.sync=no
ro.browser.useragent=0
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal/?model=MB860
gsm.sim.mot.simswap=1
ro.config.sync=no
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.media.enc.hprof.vid.bps=4000000
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.enc.hprof.codec.vid=h264
ro.media.enc.hprof.vid.fps=30
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB860/profile/MotoMB860.rdf
ro.build.version.full=Blur_Version.0.37.23.MB860.BellMobility.en.CA
vmiku914 said:
Certain apps a opening up in a smaller resolution and not using the full screen when they used to open up in full screen. Also some apps that worked before are now force closing, this all happened after I copied the build.prop and edited it for use of a game.
Click to expand...
Click to collapse
This is a known (but sometimes frustrating) "Atrix issue".
If you read some of the market app comments, the Atrix has that issue with some apps.
"TV Listings" is an app off the top of my head that worked when the Atrix launched, and then went to the 2/3rds of the screen showing it. "Weatherbug" isn't as noticeably bad, but used to be better at using the full screen.
It's weird because this happened before the first Bell Update came out too.
Unfortunately or fortunately, (depending on how you look at it) it's more of an "Atrix Issue" than anything you did wrong...
that's a strange Atrix issue, one minute an app resolution is fine then the next it shrinks to the resolution of other devices.
hmmm could it be the high resolution screen? anyone try installing spare parts and switching off app compatibility mode? (this fixed the issue on a droid with a dpi mod and my tablet with old apps.) (if im totally off just ignore me)
turning off compatibility mode worked! Thank you!
anytime glad to here it worked!
MMORPG Order & Chaos Online HD v1.0.2 Apk Working On Evo3D & Some Android Devices
This should work on most Android device that have root,R/W access,s-off.ect
PLEASE NOTE THAT THIS GUIDE IS SHOWING YOU HOW TO GET THE OFFICIAL GAME DIRECTLY FROM MARKET
THE BENEFIT OF GETTING THE GAME THIS WAY INSTEAD OF THE HACK OR PATCH VERSION IS LISTED BELOW
1:The official version will allow you to make in-app purchase which can get you the nice items like experience stones which increase xp by 100%
2:You will be able to get the overpower super gears at later levels.
3:The Game just runs way smoother than the hack or patch version(NO LAG AT ALL)
4:You will be able to get the awesome future updates soon as they are available because of this method here
5:No crashes because it is the Official game directly from market.The crack/patch version is known for having Force Closes and Crashes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE:Things you will need are Build.Prop Editor or Root Explorer which is what i used,ChainFire 3D and of course your phone need to be rooted with s-off and Superuser access,you should do a nand backup from custom recovery just incase u messed up somewhere.
CONFIRM:Before we begin,uninstall the patch/hack version if you have it installed,You may also delete the the old game cache folder GloftMMHM if you want a clean installation and a low chance of any problems or if you are getting unable to download message.
STEP 1:EDITING BUILD.PROP
This is where you are going to edit your build.prop to make market think your device is one of the compatible device for O&C and by doing that you will be able to see and download the game from Market directly.The changes you will be making to your build.prop are listed below.Keep in mind I didn't find the second line ro.product.model.internal= on Evo3D build.prop,but that line didn't matter it seems.
Some device have identical lines listed more than once,like for example Evo3D have two ro.product.model lines,so you must edit both lines if u see it more than once .
Make the following edit to your build.prop to make the game appear in market and u should be able download & install it.
Build.Prop #1 FOR HTC DEVICES IF THIS BUILD.PROP WORK FOR YOU,THEN YOU DONT HAVE TO FOLLOW THE OTHER EXTENDED STEPS
ro.product.brand=sprint
ro.product.model=PG06100
ro.product.name=htc_speedy
ro.product.device=speedy
ro.product.board=speedy
After you made the above change to your prop and save & reboot.Check market to see if u can download and install Order & Chaos.If you are able to see it but dont see the option to install it,then reboot your device a second time.If you are still unable to install the game then you have to refer to the addition steps below.
Make the change below to your prop if the above method didnt work for you and you will have to follow the additional steps if you have to use the build.prop below
BUILD.PROP #2 FOR NON HTC DEVICES
ro.product.model=Optimus 2X
ro.product.model.internal=
ro.product.brand=lge
ro.product.name=lge_star
ro.product.device=p990
ro.product.board=p990
Thanks to mattijuana from Atrix forum for settings
If you are using Root explorer,open it up then navigate to system then Build.prop,long press on it then select open up in text editor,make sure its mount as R/W and then make the above changes ONLY please,if u dont your device can get stuck in bootloop like mine did cause i was rushing and didnt capitalize what needed to be or maybe i didnt put space.
If you are using Build.Prop Editor app it simplify the process a little.
After you make the changes to your build.prop and save it you will need to reboot your device for the changes to take effect.
STEP 2:BUYING & INSTALLING THE GAME DIRECTLY FROM MARKET
Open up market and search for Order and Chaos and you should see it and able to download and install it because market thinks your phone is Optimus 2X(If you are able to see it but cant download it you might need old Market v2.3.6).Buy it and then install it then launch it and download the remaining data,its about 600mb plus in size so a fast connection would be nice.After that the game will launch properly but mine got stuck at the loading screen mainly because its looking for a NIVIDIA chip because your device is imitating a phone that use that NIVIDIA chip.So now we have to spoof our Qualcomm chip,thats where ChainFire comes in.Thanks Malebolgia from Whispering Island Server and guild leader of FORGOTTEN a level 60 guild for the information on ChainFire.
STEP 3:SPOOFING YOUR DEVICE QUALCOMM CHIPS WITH CHAINFIRE 3D PRO(HACK VERSION WOULD NOT WORK)
IF YOUR DEVICE ALREADY HAVE A NVIDIA CHIP,THEN YOU CAN PROBABLY SKIP THIS STEP
YOU WILL NEED CHAINFIRE 3D PRO VERSION FROM MARKET.....(CRACKED VERSION MAY NOT WORK)....
You will need the ChainFire3D Pro version app from market and get the pro version so you can install your own driver and apply pro version features,The driver you will need is NVIDIA driver that you can find here http://www.megaupload.com/?d=4P9LEW7P or if this link is down or the file is deleted you will have to search for LibGLEMU_NVIDIA file in zip format on Google.
You will need to grant superuser access for ChainFire3D and when you first launch it you will need to install the CF3D(then if you Evo3D you may need to remove your battery to boot back up after installing CF3D driver if your device froze trying to reboot) that is already provided with the app then you will need to install the NVIDIA driver you downloaded and is on your SD card.For some reason when you install those two drivers on Evo3D your phone will not reboot unless you take the battery out after each driver installment then power on your device.
NOTE:
Some device don't lockup or freeze after installing CF3D & NIVIDA drivers and would require the battery to be remove to reboot,But my Evo3D does.
After you installed the require drivers and rebooted twice after each driver installment by taking out your battery cause it wouldnt reboot normaly after the drivers installment on Evo3D,Im not sure about other devices.Launch ChainFire then navigate to Pre-app OpenGL settings and select Order and Chaos app and apply the NIVDIA plugin thats on your SD card and then check HIDE CF3D ID and DUMP Shaders options.Then launch Order and Chaos app.It should now load up properly and you can create account or if u have one already sign in and create a character and join the Whisperin Island Server of America,the best sever in my opinion
STEP 4:YOU ARE DONE,NOW GO ENJOY THE GAME IF YOU FOLLOW THE STEPS ABOVE TO THE LETTER.
Getting in-app purchase to work require Market version 3.0.27 and above
Now you should have the game running fine if you follow the steps correctly and made a nand backup just for good measure.
Please Join The Whispering Island Server if you dont want to get Ganck by higher level players or you are unable to complete a quest because over 20 people is doing the same quest as you on the other crowded servers with lag issues.My Name is Kaizer a Lv60(Max) warrior and leader of legends guild with over 200 active members,Ask for invite to Legends guild on global chat within the game if you chose Whispering Island Server,hope you did.
This is how my HTC EVO 3D Build.prop look after editing.
ro.com.google.clientidbase=android-sprint-us
ro.com.google.clientidbase.yt=android-sprint-us
ro.com.google.clientidbase.am=android-sprint-us
ro.com.google.clientidbase.vs=android-sprint-us
ro.com.google.clientidbase.gmm=android-sprint-us
ro.com.google.clientidbase.ms=android-sprint-us
ro.phone.min_match=7
ro.product.model=Optimus 2X<-----EDITED LINE
ro.cdma.home.operator.alpha=sprint
gsm.sim.operator.alpha=sprint
gsm.operator.alpha=sprint
ro.cdma.home.operator.numeric=310120
gsm.sim.operator.numeric=310120
gsm.operator.numeric=310120
gsm.sim.operator.iso-country=us
gsm.operator.iso-country=us
# begin build properties
# autogenerated by buildinfo.sh
ro.aa.taskid=193975
ro.aa.romver=1.11.651.3
ro.aa.maincid=SPCS_001
ro.aa.modelid=PG8610000
ro.aa.cidlist=SPCS_001
ro.aa.rid=146
ro.aa.customizationid=184167
ro.aa.project=Shooter
ro.aa.skulist=651
ro.product.brand=lge
ro.product.model=Optimus 2X<------EDITED LINE
ro.aa.mainsku=651
ro.com.google.clientidbase=android-sprint-us
ro.build.id=GRI40
ro.build.display.id=GRI40
ro.build.version.incremental=69941
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=一 5月 23 22:21:14 CST 2011
ro.build.date.utc=1306160474
ro.build.type=user
ro.build.user=
ro.build.host=AA108
ro.build.tags=release-keys
ro.product.model=Optimus 2X<------EDITED LINE
ro.product.brand=lge<------EDITED LINE
ro.product.name=lge_star<------EDITED LINE
ro.product.device=p990<------EDITED LINE
ro.product.board=p990<------EDITED LINE
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shooter
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.11.651.3 CL69941 release-keys
ro.build.description=1.11.651.3 CL69941 release-keys
ro.build.changelist=69941
ro.product.ua=
ro.build.fingerprint=sprint/htc_shooter/shooter:2.3.3/GRI40/69941:user/release-keys
ro.build.project=193975
ro.product.version=1.11.651.3
ro.build.languageremove=0
keyguard.no_require_sim=1
# end build properties
#
# system.prop for mahimahi
#
ro.sf.lcd_density=240
debug.fb.rgb565 = 0
#C2D
debug.composition.type = c2d
rild.libpath=/system/lib/libhtc_ril.so
# Default network type.
# 4 => CDMA mode preferred.
ro.telephony.default_network=4
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=8
persist.data_netmgrd_mtu=1472
#
wifi.interface=eth0
wifi.supplicant_scan_interval=15
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
# Change to 32m, due to 2.3.3 GB already change to 32m
dalvik.vm.heapsize=32m
# For the default value of agps
ro.ril.def.agps.mode = 2
# For emmc phone storage
ro.phone_storage = 0
# For ext4 file system
ro.ext4fs = 1
# For FOTA setting (leave empty value to use default)
ro.htc.checkin.url = http://andchin.htc.com/android/checkin
ro.htc.checkin.crashurl = http://andchin.htc.com/android/crash
ro.htc.checkin.url_CN = http://andchin.htccomm.com.cn/android/checkin
ro.htc.checkin.crashurl_CN = http://andchin.htccomm.com.cn/android/crash
ro.htc.checkin.exmsg.url = http://fotamsg.htc.com/android/extra/
ro.htc.checkin.exmsg.url_CN = http://fotamsg.htccomm.com.cn/android/extra/
ro.htc.appupdate.url = http://apu-chin.htc.com/check-in/rws/and-app/update
ro.htc.appupdate.url_CN = http://apu-chin.htccomm.com.cn/check-in/rws/and-app/update
ro.htc.appupdate.exmsg.url = http://apu-msg.htc.com/extra-msg/rws/and-app/msg
ro.htc.appupdate.exmsg.url_CN = http://apu-msg.htccomm.com.cn/extra-msg/rws/and-app/msg
# release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100101000011 represent bt profile list
ro.bt.profiles = 4270403
# Properties of BTLA stack
service.brcm.bt.activation = 0
service.brcm.bt.srv_active = 0
service.brcm.bt.hcid_active = 0
service.brcm.bt.btld = 0
service.brcm.bt.btld_pid = 0
service.brcm.bt.avrcp_pass_thru = 0
service.brcm.bt.avrcp_toggle = 1
#Welly_Fang
ro.htc.device.slot1 = NV
# Following property will be reference by Settings.
ro.product.processor = 1.2 GHz dualcore
ro.product.ram = 1GB
ro.product.display_resolution = 4.3 inch QHD resolution
ro.product.main_camera = 5M * 2
ro.product.front_camera = 1.3M
ro.product.bluetooth = 3.0
ro.product.wifi = 802.11 b/g/n
# For opensense sdk
ro.htc.common.version = 3.0.0.0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.networklocation=1
ro.setupwizard.mode=DISABLED
ro.setupwizard.mode=OPTIONAL
ro.config.ringtone=QuietlyBrilliant.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r3
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
ro.setupwizard.enterprise_mode=1
ro.media.codec_priority_thumb=so
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Sent from my Optimus 2X using XDA Premium App
Dude you're the effing bomb!! It worked it really worked. Definitely a thanks. I couldn't get it off the market so i had some searching for the apk. I think I'm really gonna love this game. My!? Is why doesn't gameloft port it over since as you can see it can run on our phones very well.
mrjaydee82 said:
Dude you're the effing bomb!! It worked it really worked. Definitely a thanks. I couldn't get it off the market so i had some searching for the apk. I think I'm really gonna love this game. My!? Is why doesn't gameloft port it over since as you can see it can run on our phones very well.
Click to expand...
Click to collapse
Glad I can help
Sent from my Optimus 2X using XDA Premium App
This game really heats up my phone big time, what is a safe temp you think for evo 3d? After a little playing it got up to 52 degrees celcius
mrjaydee82 said:
This game really heats up my phone big time, what is a safe temp you think for evo 3d? After a little playing it got up to 52 degrees celcius
Click to expand...
Click to collapse
Yeah it do hit extreme temperature mainly because data is constantly being transfer and if you are on a weak connection the harder the radio will have to work thus generating more heat and if u are playing while plug in and using the Evo3D charger which charges at a higher voltage the faster the phone temp will go up,mine goes way above 54c/110'F,but don't worry,the led should start blinking from Green/Orange repeatedly when the phone start to hit unsafe temperature,and when it do start to blink orange/green you might want to unplug the charger and/or you may need to pull the battery out for about about 2-5mins if you are concern about damaging your device by overheating it,but I just reboot and wait few minutes to start playing again cause I have a otter box case and pulling battery out is a pain.
Also try setting resolution for the game to 16bit from ChainFire3D settings it will reduce memory use and help with battery heat because the chips are drawing less power,and you wouldn't even notice the difference in 32bit and 16bit.And u can also mess around with SetCpu or whatever to lower your CPU speed under 1ghz.Or if you are home and on wifi,turn off mobile data/3G u will still be able to get txt and calls dont worry.Those settings seems to keep temps down a little bit.
Sent from my Optimus 2X using XDA Premium App
Okay thanks
Thank you ever so much... I've been waiting on this for a minute...
ourprisonplanet said:
Thank you ever so much... I've been waiting on this for a minute...
Click to expand...
Click to collapse
You are welcome sir
4g for htc evo would look like this?
ro.product.model = Optimus 2X
= ro.product.model.internal
ro.product.brand = LGE
ro.product.name = lge_star
ro.product.device = P990
ro.product.board = P990
BUILD_DISPLAY_ID=4.24.651.1
dalvik.vm.dexopt-flags=m
dalvik.vm.heapsize=48m
dalvik.vm.lockprof.threshold=500
dalvik.vm.stack-trace-file=/data/anr/traces.txt
gsm.operator.alpha=Sprint
gsm.operator.iso-country=us
gsm.operator.numeric=310120
gsm.sim.operator.alpha=Sprint
gsm.sim.operator.iso-country=us
gsm.sim.operator.numeric=310120
htc.audio.alt.enable=1
htc.audio.hac.enable=1
keydispatchtimeout=15000
keyguard.no_require_sim=1
media.a1026.nsForVoiceRec=0
media.stagefright.enable-http=true
media.stagefright.enable-meta=true
media.stagefright.enable-player=true
media.stagefright.enable-scan=true
net.bt.name=Android
persist.service.adb.enable=1
persist.service.mount.playsnd=0
persist.sys.shutdown.mode=hibernate
postprocess.denoise_level=5
postprocess.iso_midband=400
rild.libpath=/system/lib/libhtc_ril.so
ring.delay=0
ro.aa.cidlist=SPCS_001
ro.aa.customizationid=177316
ro.aa.maincid=SPCS_001
ro.aa.mainsku=651
ro.aa.modelid=PC3610000
ro.aa.project=SuperSonic_GB
ro.aa.rid=62
ro.aa.romver=4.24.651.1
ro.aa.skulist=651
ro.aa.taskid=193963
ro.board.platform=qsd8k
ro.bt.chipset=Broadcom BCM4329-B1
ro.bt.profiles=4270339
ro.bt.stack=Broadcom BTL-A
ro.bt.stack.version=2.0.50.032
ro.build.date=一 5月 23 22:29:13 CST 2011
ro.build.date.utc=1306160953
ro.build.description=Ginger-AleV5 ro.build.changelist
ro.build.display.id=GRI40
ro.build.fingerprint=sprint/htc_supersonic/supersonic:2.3.3/GRI40/61076:user/release-keys
ro.build.host=AA135
ro.build.id=GRI40
ro.build.product=supersonic
ro.build.project=198504
ro.build.tags=release-keys
ro.build.type=user
ro.build.user=root
ro.build.version.codename=REL
ro.build.version.incremental=60865
ro.build.version.release=2.3.3
ro.build.version.sdk=10
ro.cdma.home.operator.alpha=Sprint
ro.cdma.home.operator.numeric=310120
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-sprint-us
ro.com.google.clientidbase.am=android-sprint-us
ro.com.google.clientidbase.gmm=android-sprint-us
ro.com.google.clientidbase.ms=android-sprint-us
ro.com.google.clientidbase.vs=android-sprint-us
ro.com.google.clientidbase.yt=android-sprint-us
ro.com.google.gmsversion=2.3_r2
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.ringtone=RingRing.mp3
ro.htc.checkin.crashurl=http://andchin.htc.com/android/crash
ro.htc.checkin.url=http://andchin.htc.com/android/checkin
ro.htc.common.version=2.1.0.0
ro.media.cam.preview.fps=0
ro.media.codec_priority_for_thumb=so
ro.media.dec.aud.wma.enabled=1
ro.media.dec.jpeg.memcap=20000000
ro.media.dec.vid.wmv.enabled=1
ro.media.enc.aud.amrnb.bps=5525,12200
ro.media.enc.aud.amrnb.ch=1,1
ro.media.enc.aud.amrnb.hz=8000,8000
ro.media.enc.aud.codec=amrnb
ro.media.enc.file.format=3gp,mp4
ro.media.enc.hprof.aud.bps=12200
ro.media.enc.hprof.aud.ch=1
ro.media.enc.hprof.aud.hz=8000
ro.media.enc.hprof.codec.aud=amrnb
ro.media.enc.hprof.codec.vid=m4v
ro.media.enc.hprof.duration=60
ro.media.enc.hprof.file.format=mp4
ro.media.enc.hprof.vid.bps=2000000
ro.media.enc.hprof.vid.fps=24
ro.media.enc.hprof.vid.height=480
ro.media.enc.hprof.vid.width=720
ro.media.enc.jpeg.quality=95,85,70
ro.media.enc.lprof.aud.bps=12200
ro.media.enc.lprof.aud.ch=1
ro.media.enc.lprof.aud.hz=8000
ro.media.enc.lprof.codec.aud=amrnb
ro.media.enc.lprof.codec.vid=m4v
ro.media.enc.lprof.duration=30
ro.media.enc.lprof.file.format=3gp
ro.media.enc.lprof.vid.bps=256000
ro.media.enc.lprof.vid.fps=15
ro.media.enc.lprof.vid.height=144
ro.media.enc.lprof.vid.width=176
ro.media.enc.vid.codec=m4v,h263,h264
ro.media.enc.vid.h263.bps=64000,6000000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.h263.height=144,720
ro.media.enc.vid.h263.width=176,1280
ro.media.enc.vid.h264.bps=64000,6000000
ro.media.enc.vid.h264.fps=1,30
ro.media.enc.vid.h264.height=144,480
ro.media.enc.vid.h264.width=176,800
ro.media.enc.vid.m4v.bps=64000,8000000
ro.media.enc.vid.m4v.fps=1,30
ro.media.enc.vid.m4v.height=144,720
ro.media.enc.vid.m4v.width=176,1280
ro.opengles.version=131072
ro.product.bluetooth=2.1 + EDR
ro.product.board=supersonic
ro.product.brand=sprint
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.device=supersonic
ro.product.display_resolution=4.3 inch WVGA resolution
ro.product.front_camera=1.3M
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.product.main_camera=8M
ro.product.manufacturer=HTC
ro.product.model=PC36100
ro.product.name=htc_supersonic
ro.product.processor=1GHz
ro.product.ram=512MB
ro.product.ua=
ro.product.version=AvA-Modified
ro.product.wifi=802.11 b/g/n
ro.ril.def.agps.mode=2
ro.ril.def.preferred.network=4
ro.ril.set.mtu1472=1
ro.setupwizard.enterprise_mode=1
ro.setupwizard.mode=DISABLED
ro.sf.hw=1
ro.sf.lcd_density=240
ro.telephony.call_ring.delay=0
ro.telephony.default_network=4
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.wifi.channels=
service.brcm.bt.activation=0
service.brcm.bt.avrcp_pass_thru=0
service.brcm.bt.avrcp_toggle=1
service.brcm.bt.btld_pid=0
service.brcm.bt.hcid_active=0
service.brcm.bt.srv_active=0
service.brcm_bt.btld=0
settings.display.autobacklight=1
settings.display.brightness=143
watchdogtimeout=120000
wifi.interface=etho
wifi.supplicant_scan_interval=30
windowsmgr.max_events_per_sec=100
windowsmgr.support_rotation_270=true
ro.config.ringtone=Windchimer.mp3
Thanks
I would totally put chainfire on my nook color, but your instructions kind of scare me since we cannot remove the battery.. and your advice was right about putting the new market back on, I could buy runes and such afterwards. Unfortunately it can't see the game anymore, but since I could buy it legit I don't mind.
Btw, I am in your guild. Good write up btw.
Edit: No problems with chainfire(must be your phones), and a notable amount of smoothness since I did it. Good idea.
Silentbtdeadly said:
I would totally put chainfire on my nook color, but your instructions kind of scare me since we cannot remove the battery.. and your advice was right about putting the new market back on, I could buy runes and such afterwards. Unfortunately it can't see the game anymore, but since I could buy it legit I don't mind.
Btw, I am in your guild. Good write up btw.
Edit: No problems with chainfire(must be your phones), and a notable amount of smoothness since I did it. Good idea.
Click to expand...
Click to collapse
Did you try the option in ChainFire3D that says Fix Market Settings to see if u can see it again in the new Market?
I'd love to give this a go, but I can't get past step 2. I downloaded the new version from the market, with my modded build.prop, but when I go to run it, and download content, it says, "an error has occurred with the download, would you like to restart it? " or something to that effect, click yes, and the same message comes back up. Over, and over. I've posted on the gameloft forum, but no help over there. Hopefully, someone will have answers or help here. Thanks for reading.
Veedubklown said:
I'd love to give this a go, but I can't get past step 2. I downloaded the new version from the market, with my modded build.prop, but when I go to run it, and download content, it says, "an error has occurred with the download, would you like to restart it? " or something to that effect, click yes, and the same message comes back up. Over, and over. I've posted on the gameloft forum, but no help over there. Hopefully, someone will have answers or help here. Thanks for reading.
Click to expand...
Click to collapse
Try using a different connection or uninstall game reboot then reinstall,if that don't work,you may need to find and download the remaining game cache off the internet which is about 650MB+ and I'm not sure if the game Cache off another device may work on Evo3D,but if u look hard you might find the Optimus 2X or GX2,that's the device our phone is imitating ,You can then place it in the gameloft/games/GloftMMHM folder on your SD card,then reinstall the game from market,that might probably work because the game would only require about 160+MB more to complete.If that doesn't work,refer to method 2 below.
so here is what I want you to try.
step 1:
Uninstall the Order & Chaos you downloaded from Market and download & install the one from the link I PM/sent you cause I can't post it here.
Step 2:
Launch the one you downloaded from my link and see if it will download the remaining game from Gameloft severs.
Step 3:
If you were able to complete the download,leave the game and then uninstall Order & Chaos again then reinstall the one from Market it should just require about 165+MB more to complete this time around because its a newer version of the game.
Let me know how it goes.
will it work with this asus eee pad code?
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HMJ37
ro.build.display.id=HMJ37.WW_epad-8.4.4.11-20110711
ro.build.version.incremental=WW_epad-8.4.4.11-20110711
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Mon Jul 11 14:47:25 CST 2011
ro.build.date.utc=1310366845
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=WW_epad-user 3.1 HMJ37 WW_epad-8.4.4.11-20110711 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:3.1/HMJ37/WW_epad-8.4.4.11-20110711:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libmbm-ril.so
rild.libargs=-d /dev/ttyACM0 -i wwan0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V5.1.50
bt.version.driver=V6.17
gps.version.driver=V1.3.2
keyguard.no_require_sim=true
drm.service.enabled=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.1_pre-r1
gsm.bodysargsm=32,26,29,29
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
farr3ll said:
will it work with this asus eee pad code?
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HMJ37
ro.build.display.id=HMJ37.WW_epad-8.4.4.11-20110711
ro.build.version.incremental=WW_epad-8.4.4.11-20110711
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Mon Jul 11 14:47:25 CST 2011
ro.build.date.utc=1310366845
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=WW_epad-user 3.1 HMJ37 WW_epad-8.4.4.11-20110711 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:3.1/HMJ37/WW_epad-8.4.4.11-20110711:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libmbm-ril.so
rild.libargs=-d /dev/ttyACM0 -i wwan0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V5.1.50
bt.version.driver=V6.17
gps.version.driver=V1.3.2
keyguard.no_require_sim=true
drm.service.enabled=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.1_pre-r1
gsm.bodysargsm=32,26,29,29
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
If you your Tab is rooted with R/W and you are able to edit the corresponding Build.Prop settings in first post,then yes it might work,because our phone is able to imitate Tabs too & vice versa.But keep in mind you will be installing a phone version of the game and it might not look full screen on you pad,I'm not sure.
still reads as incompatible at market
Lord_Kaizer said:
If you your Tab is rooted with R/W and you are able to edit the corresponding Build.Prop settings in first post,then yes it might work,because our phone is able to imitate Tabs too & vice versa.But keep in mind you will be installing a phone version of the game and it might not look full screen on you pad,I'm not sure.
Click to expand...
Click to collapse
Unless you have found anything different, there doesn't appear to be a "phone" version and tablet version, nothing I have found suggests the way the game renders, the sd card contents, or changing the build.prop has changed those things. Since I am using a pad, I would like to be able to test this, but when I put the galaxy tab settings in my build.prop nothing was any different than before.
I am very curious though.
farr3ll said:
still reads as incompatible at market
Click to expand...
Click to collapse
Did you reboot after changing your build.prop? The changes won't take effect until you do, and this method is verified as working.
I have a totally different device, but the method that worked for me to be ABLE to see/download it in the market, I had to be using the OLD style market(the newer one is more device aware).. then to be able to buy game time in game I had to install the new market(grey/black style).
farr3ll said:
still reads as incompatible at market
Click to expand...
Click to collapse
At which point do it say incompatible,anwser the following questions
1: Are you using a custom rom?
I'm using stock
2: Did you have the patch/hack version installed before this?
if u did,u may have to delete the old cache folder GloftMMHM from the gameloft folder on your SD and start fresh
3: were u able to see the game in market
and download & install,but then got incompatible when u launch the game?
if that happen,did you install the NVIDIA driver and check hide CF3D options.
2: Did the game load up normal after installing or did the incompatible message pop up?
If so,please check the build.prop changes and comepare it line by line to mine in the second post.And check the steps again please.
yeah, it should work for any device. thank you so much kaizer. it worked for me on evo3d. now i can play.
Hello everyone,
I was using VeganTab as my ROM of choice for a long time, and recently switched to CyanogenMod7 for a change and a more traditional Android feel.
With VeganTab, I had no issues using the Market. Every app I wanted to download was available in the market. Using CyanogenMod7, when I go to download apps I get a "this application is not available for your device" message on several apps. Firefox being one of them, which the gTablet should be able to support.
Why would one ROM work and the other doesn't on the same device? Has anyone else encountered this and know how to fix it?
Hello, I have one Gtab running CM7 what version/build are you on? Which apps are not showing up other than Firefox? Have you modified anything (build.prop)? If I remember right I had to modify the build.prop to get some apps to show up.
The apps in the market are set up to show only to devices that they are designed to be run on. When you change roms, your device shows up differently to the Market, so some apps might appear that weren't there before and some may dissappear. Read through the thread where you got the rom from and you may find some tips. Also as a temp. solution you can download the .apk files for many apps either to your PC or the the tablet and "side load" it (go to file manager and tap the downloaded .apk to install). Open a root file explorer and go to /system and open build.prop. Let me know what is says for product board, region and lcd density.
Thanks for the quick response Dave.
So far, Agenda Widget and Firefox are the two I can't get through the market. I haven't tried a ton of others yet.
I've been playing with the bool.prop file a little bit, based on tutorials I've seen here and at other forums. This thread seems to offer the best advice, but didn't work for me.
Below are my build.prop values at current time:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRI40
ro.build.display.id=GRI40
ro.build.version.incremental=eng.cyanogenmod.20110505.210139
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=Thu May 5 21:02:03 CDT 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=cyanogenmod
ro.build.host=scout73
ro.build.tags=test-keys
ro.product.model=GTablet
ro.product.brand=passion
#ro.product.brand=nvidia
ro.product.name=passion
#ro.product.name=harmony
ro.product.device=olympus
#ro.product.device=harmony
ro.product.board=harmony
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=malata
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=harmony
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.3.3 GRI40 102588 release-keys
ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
# end build properties
#
# system.prop for harmony
#
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
# Density set to 161 to allow market to function properly
ro.sf.lcd_density=161
wifi.interface = wlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
# For emmc phone storage
ro.phone_storage = 1
# Add external mount points
ro.additionalmounts=/mnt/emmc;/mnt/usbdisk
# Add reference RIL
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
keyguard.no_require_sim=1
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.0.3-Harmony
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Looks from your build.prop file that you are on an older build of CM7. The apps you mentioned, Firefox and Firefox Beta, and the Agenda Widget show up and work on mine. You could try using some of the values in my .prop file here, or update to a newer version of CM7. You might be able to install over your current build without wiping your data, but back up first of course.
Thanks Dave. Can you link me to a stable, updated version of CM7?
There is a CM7 rom hosted here at XDA:
CYANOGENMOD7.2.0-RC0-BUILD98-REPACK
Or you can go to Cyanogenmod Wiki. Don't forget to download the Gapps separately from the bottom of the same page and install them too.
I apologize in advance if it is not allowed to post a link to their wiki page .
Actually I have had this problem ALOT, no matter what version of CM7 I use on it. Its even worse when the new Market gets pushed to it, I usually have to downgrade it back and remove the MarketUpdater.apk so it stays on the old one.
I am running the ICS Alpha/Beta (forget which) right now so everything works, albeit very slow.
I had the same issue it's the odd LCD density of 161 that market doesn't like. I changed mine to 200 then do the standard market fix reboot and it should be fine.
Sent from my HTC Glacier using xda premium
Hi All!
I'm running emulator with clean avd and installed Google Play Store on it (tried with ARM api-18, and ARM api-19).
When I'm accessing play store to browse around, I'm missing many apps- games, utils, etc. If I search directly for a specific app (eg, clash of clans)- I'm showing "your device isnt compatible with this version".
Why is that? Am I missing certain permissions or abilities on the emulator?
If I download the apk and use adb to install to emulator, it works fine- so what am i missing here?
I even tried taking a vanilla nexus-5 build.prop, placed it on the avd, but still- same behaviour.
isn't there a way to browse all apps on play store, and install it directly from there?
thanks!
avivz said:
Hi All!
I'm running emulator with clean avd and installed Google Play Store on it (tried with ARM api-18, and ARM api-19).
When I'm accessing play store to browse around, I'm missing many apps- games, utils, etc. If I search directly for a specific app (eg, clash of clans)- I'm showing "your device isnt compatible with this version".
Why is that? Am I missing certain permissions or abilities on the emulator?
If I download the apk and use adb to install to emulator, it works fine- so what am i missing here?
I even tried taking a vanilla nexus-5 build.prop, placed it on the avd, but still- same behaviour.
isn't there a way to browse all apps on play store, and install it directly from there?
thanks!
Click to expand...
Click to collapse
You havr extension for Google chrome on pc to download apps from playstore.
Go to playstore with google chrome, and go to app which ypu want to download, and download with that extension.
Next when you download it, just launch that .APK and that will be installed on emulator.
Give feedback.
Check the build.prop of the device you are emulating. You might change it to something more universal, like a Nexus 5 or something.
es0tericcha0s said:
Check the build.prop of the device you are emulating. You might change it to something more universal, like a Nexus 5 or something.
Click to expand...
Click to collapse
Thanks es0tericcha0s.
I changed the build.prop to a very standard nexus-5. Here it is - but I still dont get market apps...
Any help would be greatly greatly appreciated. Here's my build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JB_MR2
ro.build.display.id=JB_MR2
ro.build.version.incremental=wpef12.hot.corp.google.com
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Mon Aug 12 17:40:30 UTC 2013
ro.build.date.utc=1376329230
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs16.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus 5
ro.product.brand=google
ro.product.name=hammerhead
ro.product.device=hammerhead
ro.product.board=hammerhead
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=hammerhead
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=hammerhead-user 4.3.1 JB_MR2 937116 release-keys
ro.build.fingerprint=google/hammerhead/hammerhead:4.3.1/JB_MR2/937116:user/release-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Could it be related to parameters that are external to the build.prop file-
eg, IMEI, Android ID, SIM Card, or even- the actual google account used to sign in to play store?
This is so frustrating, I dont get how play store decides which apps you see...
avivz said:
Could it be related to parameters that are external to the build.prop file-
eg, IMEI, Android ID, SIM Card, or even- the actual google account used to sign in to play store?
This is so frustrating, I dont get how play store decides which apps you see...
Click to expand...
Click to collapse
It's possible that the emulator might just not be able to run certain kinds of apps. Which emulator are you using?
es0tericcha0s said:
It's possible that the emulator might just not be able to run certain kinds of apps. Which emulator are you using?
Click to expand...
Click to collapse
I'm using the standard sdk emulator- both arm and x86 versions behave the same.
I dont think it's that the emulator can't run the apps- when I manually install apk via adb, it works fine ..
Hi - so I am only posting as a last result and 4 days of stumbling around rooting, ROMs, and different devices I've finally reached a wall.
I have several LG Aristo 2's that I use on an ESX server for various development machines. They work terrific for what I have them for but the problem is I have particular phones for particular servers and I cannot pick one out of 8 devices because they are all named the same. For the past year or so I have kind of limped but now my environments are a bit more fluid and I need to be able to pick an offending perp out of the line up.
So I have been hacking around on a test phone for the past few days and have driven myself crazy trying to get the model number to change. I have tried several different ROMs, assuming this might be a problem but I just can't seem to change the model name that the devices connects over USB with.
I have updated the build.prop and changed model name, device name, and even added ro.mtp.label and ro.ptp.label.
About to give up thinking this is impossible I had a spare Blu Vivo sitting around and I went through the same process and have been successful in renaming the device doing the things in the line above.
Is this just not possible on the LG Aristo 2?
Android Version: 8.1.0
Model Number: LM-X210MA
Here is a section of my build.prop
Can anyone point me in the right direction? Beer money will be sent!
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OPM1.171019.026
ro.build.display.id=OPM1.171019.026
ro.build.version.incremental=1832618554af2
ro.build.version.sdk=27
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.1.0
ro.build.version.security_patch=2018-11-01
ro.build.version.base_os=
ro.build.date=Thu Nov 22 18:55:26 KST 2018
ro.build.date.utc=1542880526
ro.build.type=user
ro.build.user=jenkins
ro.build.host=LGEACI6R1
ro.build.tags=release-keys
ro.build.flavor=cv1_lao_com-user
ro.build.ab_update=false
ro.product.model=HulkHappy
ro.product.brand=lge
ro.product.name=HulkHappy
ro.product.device=cv1
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=LGE
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=cv1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=cv1_lao_com-user 8.1.0 OPM1.171019.026 1832618554af2 release-keys
ro.build.fingerprint=lge/cv1_lao_com/cv1:8.1.0/OPM1.171019.026/1832618554af2:user/release-keys
ro.build.characteristics=default
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=QC_Reference_Phone
ro.board.platform=msm8937
ro.vendor.product.manufacturer=LGE
ro.vendor.product.model=LM-X210
ro.vendor.product.brand=lge
ro.vendor.product.name=cv1_lao_com
ro.vendor.product.device=cv1
ro.ptp.label=HulkHappy
ro.mtp.label=HulkHappy
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
@jwoegerbauer
Awesome, thank you for the information. I had been using a version of the first one and it did not get me as far along as what you just shared. So using
Code:
adb shell settings put secure global device_name "device name"
I have now at least been able to differentiate on the direct server what device is connected. In my ESX host it still shows the Model LG LM-X210G. I'd share some images but I guess my n00b status, rightly so, won't allow that.
But using my eyes:
ESX shows the USB device as: LG LM-X210G
Easy Tether shows the devices as: LMX210G1db3... (stripping the rest, but guessing its part of the serial)
Windows shows the device as: HulkHappy
... since HulkSmash destroyed the first phone I was trying this on.
Is there any where else I can look? My biggest desire is to get my ESX host in line.
jwoegerbauer said:
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
Click to expand...
Click to collapse