Jump to content

Alter blades id / useragent .ref small mms o2


Recommended Posts

Guest cbrpaul
Posted

Anyone know where the files are in the blade to change its id ?

Reason i ask , o2 only send very small mms to blades , as they dont recognise the blade, so it needs to be "spoofed" into something else o2 does know !!

I found this beow that relates to the HTC when that had a problem on the same thing whenthat first hit the market ,

To get around the problem there are a couple of reg entries to change which 'fool' O2 into thinking your handset is one that the network recognises, e.g. a Nokia N95 (just wheres MMS is concerned).

So, fire up your fav reg editor and browse to:

1. HKLM\Software\Arcsoft\Arcsoft MMS UA\Config\MM1\WspHeader\User-Agent

Change the value of User-Agent to:

"NokiaN95/11.0.026; Series60/3.1 Profile/MIDP-2.0 Configuration/CLDC-1.1" (no quotation marks)

2. HKLM\Software\Arcsoft\Arcsoft MMS UA\Config\MM1\WspHeader\x-wap-profile:

Change the value of x-wap-profile to:

"http://nds1.nds.noki.../NN95-1r100.xml" (no quotations marks)

here is my build.prop would a change here work ?

heres the file ,

What would be the suggested area to change ? and to what ?

I have highlighted what it could be in red below !!

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=ERE27

ro.build.display.id=Swedish Snow RLS1

ro.build.version.incremental=20101208.144833

ro.build.version.sdk=7

ro.build.version.codename=REL

ro.build.version.release=2.1-update1

ro.build.date=Wed Dec 8 14:50:08 CST 2010

ro.build.date.utc=xxxx

ro.build.type=user

ro.build.user=user

ro.build.host=localhost.localdomain

ro.build.tags=release-keys

ro.product.model=ZTE-BLADE

ro.product.brand=ZTE

ro.product.name=P729B_TSE

ro.product.device=blade

ro.product.board=blade

ro.product.cpu.abi=armeabi

ro.product.manufacturer=ZTE

ro.product.locale.language=en

ro.product.locale.region=GB

#ro.wifi.channels=14

ro.wifi.channels=

wifi.interface=wlan0

wifi.supplicant_scan_interval=15

#wlan.default.dns1=xxx

ro.board.platform=msm7k

# ro.build.product is obsolete; use ro.product.device

ro.build.product=blade

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=P729B_TSE-user 2.1-update1 ERE27 20101208.144833 release-keys

ro.build.fingerprint=ZTE/P729B_TSE/blade/blade:2.1-update1/ERE27/20101208.144833:user/release-keys

usb.default.pid=0x1354# end build properties#

# system.prop for surf

#

ro.setupwizard.mode=OPTIONAL

ro.build.baseband_version=TSE_P729VB01

ro.build.sw_internal_version=TSE_P729VV1.0.0B05

ro.product.board_name=blade

rild.libpath=/system/lib/libril-qc-1.so

rild.libargs=-d /dev/smd0

persist.rild.nitz_plmn=

persist.rild.nitz_long_ons_0=

persist.rild.nitz_long_ons_1=

persist.rild.nitz_long_ons_2=

persist.rild.nitz_long_ons_3=

persist.rild.nitz_short_ons_0=

persist.rild.nitz_short_ons_1=

persist.rild.nitz_short_ons_2=

persist.rild.nitz_short_ons_3=

DEVICE_PROVISIONED=1

debug.sf.hw=1

dalvik.vm.heapsize=24m

ro.config.ringtone=Terminated.ogg

ro.config.notification_sound=F1_New_SMS.ogg

persist.sys.timezone=Europe/London

ro.camera.sound.forced=0

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.com.google.gmsversion=2.1_r12

ro.sf.lcd_density=240

qemu.sf.lcd_density=240

ro.com.google.clientidbase=android-zte

ro.com.google.clientidbase.yt=android-zte

ro.com.google.clientidbase.am=android-zte

ro.com.google.clientidbase.vs=android-zte

ro.com.google.clientidbase.gmm=android-zte

net.bt.name=Android

ro.config.sync=yes

dalvik.vm.stack-trace-file=/data/anr/traces.txt

Guest StevenHarperUK
Posted

90% of the useragent sting is generated by files you can't touch

The main part you can effect is covered in this topic (linked in the FAQ)

Lost access to some operator services

Your opertaor may provide services and filter them by the useragent in your browser

this is adjusted in the build.props

http://android.modaco.com/content/zte-blad...-rom-flb-froyo/

However I assume there are other browsers that you can fully hack around with the Useragent - download some from the market if thats what you need.

Guest Phoenix Silver
Posted

apparently the line to change is

ro.product.model=ZTE-BLADE

Guest Frankish
Posted

I just use the cyanogen mms apk. it has options to change us string, black or white backgrounds, longer vibrate and burst vibrate options. Works a treat.

Guest cbrpaul
Posted

ok we are getting somehwere , !!!

i d/l the Mms.apk afger reading from this site ,

http://softbanksucks.blogspot.com/2010/08/...upport-for.html

it will allow you alter the "Custom User agent " settings, and will allow you spoof your phone , i chose iphone3

however it will only send or reveice pictures that are below 300kb !!!! , but this is a mass improvemnt on the 25k received !!

So if you send any pictures messages , you need to reduce the picture to below 300kb ,

Im wondering if thats the industry max anyway for mms ???

Guest hecatae
Posted
is gt540 can receive mms ?

it's the reason of the topic

gt540 is an o2 uk recognised phone and can receive and send mms

Guest hecatae
Posted
Im wondering if thats the industry max anyway for mms ???

o2 uk max mms size is 300kb

Guest cbrpaul
Posted (edited)
o2 uk max mms size is 300kb

thx hecatea,

I have sorted it by using handsent to re-size sent mms to a max of 300k(default) in its settings, ( note spoof settings for useragent are only in the standard sms app settings, this caught me out for abit !! )

Im happy now ,

solved !!! :lol:

Edited by cbrpaul
Guest That-Guy
Posted

Can someone write a guide for this please?

I am wanting to do this to both mine and the gf's phone :lol:

Guest cbrpaul
Posted
Yes plz write a guide :lol:

ok i see what i can do :)

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.