After applying the bgill55marketfix the about phone section info changed from jrummy FRF83 back to the leaked froyo "....xxxx test keys" thing, did this happen for anyone else?
Sent from my Droid using Tapatalk
I forgot what it was supposed to say actually Jrummy can you please post what the Build number is supposed to read?
It's possible that it changed the build number in order to trick the marketplace to give the phone full access, not entirely sure. But thats my best guess at the moment.
Mine currently reads voles-userdebug 2.2 FRFXX 33333 test-keys after the marketplace fix.
EDIT: I opened up Build.prop in word pad and this is what I found:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF57
ro.build.display.id=
voles-userdebug 2.2 FRFxx 33333 test-keys
ro.build.version.incremental=33333
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Tue May 25 07:55:51 MST 2010
ro.build.date.utc=1274799351
ro.build.type=userdebug
ro.build.user=android-build
ro.build.host=android-test-32.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=Droid
ro.product.brand=verizon
ro.product.name=voles
ro.product.device=sholes
ro.product.board=sholes
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=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sholes
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=voles-userdebug 2.2 FRFxx 33333 test-keys
ro.build.fingerprint=
verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys
# end build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
# Default network type.
# 4 => CDMA / EVDO.
ro.telephony.default_network=4
wifi.interface = tiwlan0
# 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 = 360
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# 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=24m
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=droid.ogg
ro.config.ringtone=DroidInvasion.ogg
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
ro.com.google.clientidbase=android-verizon
ro.com.google.locationfeatures=1
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.config.ringtone=CaribbeanIce.ogg
ro.setupwizard.mode=OPTIONAL
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.config.vc_call_vol_steps=7
ro.cdma.otaspnumschema=SELC,1,80,99
ro.telephony.call_ring.multiple=false
#ro.telephony.call_ring.delay=3000
ro.url.safetylegal=http://www.motorola.com/staticfiles/Support/legal/?model=A855
ro.setupwizard.enable_bypass=1
ro.media.dec.jpeg.memcap=20000000
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
I think those two changes is what allows Froyo to work within the marketplace. Since 2.2 isn't officially out it would make sense that Google has it locked out. It's actually pretty common to do this. I do this with my PSP games so they work with older versions of firmware.