Database Users

T-Mobile GPRS / EDGE GOOGLE FIX - regedit MTU setting

For those of you who cannot browse GOOGLE sites using the unlimited T-Mobile GPRS/EDGE plan do the following:
On your WM5 device, use a registry editor and do the following:
Go to HKLM\Comm\Cellular Line\Parms\tcpip
and add a DWORD registry key called MTU with value 1460 (UPDATED)
Open PocketIE/Opera/Netfront and go to any Google page you want!
Oh, and make sure your internet gateway is using:
internet2.voicestream.com

It seems as though the fix is not working for all cities.
I'm actually in New York City, so I guess the MTU values could be different in different areas. Works great on an MTU of 1460 in NYC.
You can try values from 1500 (default) all the way down to 1400.
Trial and error, if it does work for you though, please post the city and MTU value you got it working with.
Goodluck everyone. I have been struggling with this since February and am really pleased I have finally managed to resolve it.
If there are any other New York City T-Mobile users, please confirm the fix.
Thanks.

The following solution worked for me on my T-Mobile MDA. Note: the NdisWan key did not exist, I had to create it from scratch. Before adding the information below into my registry, I was unable to get past the initial google page. Now I can google anything, and use google maps too! And BTW I am in Long Island.
Change the MTU Settings for PPP Connections
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NdisWan\Parameters
Add a Protocols subkey (if it does not already exist). To do so:
a. On the Edit menu, point to New, and then click Key.
b. Type Protocols, and then press ENTER.
4. Add a 0 (zero) subkey to the Protocols subkey. To do so:
a. Click the Protocols subkey that you created step 3.
b. On the Edit menu, point to New, and then click Key.
c. Type 0 (zero), and then press ENTER.
5. Click the 0 subkey that you created in step 4.
6. On the Edit menu, point to New, and then click DWORD Value.
7. In the Value data box, type ProtocolType, and then click OK.
8. On the Edit menu, click Modify.
9. In the Value data box, type 800, make sure Hexadecimal is selected under Base, and then click OK.
10. On the Edit menu, point to New, and then click DWORD Value.
11. Type PPPProtocolType, and then press ENTER.
12. On the Edit menu, click Modify.
13. In the Value data box, type 21, make sure Hexadecimal is selected under Base, and then click OK.
14. On the Edit menu, point to New, and then click DWORD Value.
15. Type ProtocolMTU, and then press ENTER.
16. On the Edit menu, click Modify.
17. Under Base, click Decimal, type the MTU size that you want in the Value data box, and then click OK.
18. Quit Registry Editor.
19. Restart your computer.
The MTU size that worked with the customer I was talking to was 1350.

Squuiid said:
For those of you who cannot browse GOOGLE sites using the unlimited T-Mobile GPRS/EDGE plan do the following:
On your WM5 device, use a registry editor and do the following:
Go to HKLM\Comm\Cellular Line\Parms\tcpip
and add a DWORD registry key called MTU with value 1450
Open PocketIE/Opera/Netfront and go to any Google page you want!
Oh, and make sure your internet gateway is using:
internet2.voicestream.com
Click to expand...
Click to collapse
This worked PERFECTLY! I'm in NYC as well and 1450 worked. (for what's it worth, that long process also described in this thread DID NOT work for me)

Squiid you are the man I work in NYC and live in NJ works like a charm... it's especially great cause i'vee ben trying to access all my gmail and GFYD accounts and it's been so inconsistent. It works well thus far thanks!

Squiid you are the man I work in NYC and live in NJ works like a charm... it's especially great cause i'vee ben trying to access all my gmail and GFYD accounts and it's been so inconsistent. It works well thus far thanks!

The registry fix for MTU of 1450 seems to be working in Dallas, thanks for the tip.

ok... so right after I added the editi in the registry it worked right away I was sitting at the starbucks on W35th and 7th. Then I went to a building right down the street and had to google something I couldn't access any google page.
I had great service in the building just no google pages which thought I had fixed. Now I can't access them from anywhere in the city again? the MTU edit is still in my registry.
Any ideas on this? thanks?

This worked for me, PHL market.
It allowed me to get to google.com.
However I still can't access any of the other google sites. (local/maps)

MTU of 1460 best
Have done some adittional testing, an MTU value of 1460 works best!
1450 sometimes works on all google sites other times not.
1460 seem to work all the time.
Please leave your feedback, and for those that have, thanks.

Not working here
Squuiid said:
For those of you who cannot browse GOOGLE sites using the unlimited T-Mobile GPRS/EDGE plan do the following:
On your WM5 device, use a registry editor and do the following:
Go to HKLM\Comm\Cellular Line\Parms\tcpip
and add a DWORD registry key called MTU with value 1460 (UPDATED)
Open PocketIE/Opera/Netfront and go to any Google page you want!
Oh, and make sure your internet gateway is using:
internet2.voicestream.com
Click to expand...
Click to collapse
I´m not with T-Mob but I do have these problem, I tried the values you suggested but doesn´t seem to work. Is there a range of values that I should try?

I figure out myself
luiggi said:
I´m not with T-Mob but I do have these problem, I tried the values you suggested but doesn´t seem to work. Is there a range of values that I should try?
Click to expand...
Click to collapse
Here one may find a useful list of values depending of the connection type
http://www.stearns.org/p0f/mtu.h
by the way, none of these worked for me.

adamb2k6 said:
The following solution worked for me on my T-Mobile MDA. Note: the NdisWan key did not exist, I had to create it from scratch. Before adding the information below into my registry, I was unable to get past the initial google page. Now I can google anything, and use google maps too! And BTW I am in Long Island.
Change the MTU Settings for PPP Connections
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NdisWan\Parameters
Add a Protocols subkey (if it does not already exist). To do so:
a. On the Edit menu, point to New, and then click Key.
b. Type Protocols, and then press ENTER.
4. Add a 0 (zero) subkey to the Protocols subkey. To do so:
a. Click the Protocols subkey that you created step 3.
b. On the Edit menu, point to New, and then click Key.
c. Type 0 (zero), and then press ENTER.
5. Click the 0 subkey that you created in step 4.
6. On the Edit menu, point to New, and then click DWORD Value.
7. In the Value data box, type ProtocolType, and then click OK.
8. On the Edit menu, click Modify.
9. In the Value data box, type 800, make sure Hexadecimal is selected under Base, and then click OK.
10. On the Edit menu, point to New, and then click DWORD Value.
11. Type PPPProtocolType, and then press ENTER.
12. On the Edit menu, click Modify.
13. In the Value data box, type 21, make sure Hexadecimal is selected under Base, and then click OK.
14. On the Edit menu, point to New, and then click DWORD Value.
15. Type ProtocolMTU, and then press ENTER.
16. On the Edit menu, click Modify.
17. Under Base, click Decimal, type the MTU size that you want in the Value data box, and then click OK.
18. Quit Registry Editor.
19. Restart your computer.
The MTU size that worked with the customer I was talking to was 1350.
Click to expand...
Click to collapse
I'm using an 8525 with
CE5.2.1622 ( Build 18128.0.4.4 )
ROM 3.62.502.3 ( 10/11/07 )
Radio 1.16.00.00
Protocol Ver: 32.53.7018.01H
( Yes I used pof's SIM/CID Unlocker....way to go pof ! )
Anyway, I've tried adding these keys ( which, by the way, once I reboot the 8525, I lose all BUT the "ProtocolType" entries under the "0" key ), and setting my MTU from 1430 to 1460 as the original author suggested, and I can get past google.com, and it simply dies "Opening" gmail/calendar/maps.
THe funny thing is I'm running Xplode's WM6 ROM for BlueAngel on an older Siemens SX-66, and even though it DOESN'T have any of these entries mentioned, it works....I can go to gmail just fine, even without the registry settings.
Has ANYONE gotten a consistent solution to this ? Is there any particular ROM image someone can recommend to move to that includes fixes for this ?
Thanks.

Updated Radio ....still doesn't work.
I updated the Radio ROM To 1.54.30.10, and it still doesn't work. Even though now, I have 2 "cellular line" entries in the HKLM\COMM section of the registry.

HTC P6500 & HP IPaq 614c PPP Protocol MTU
Hi everyone,
I am wondering if any can look over my problem and possibly offer some advice?
I have a problem probably generic to most PDA devices where i can not change the MTU size for the PPP Protocol.
I have made the changes as advised in this thread and neither have worked for me, the MTU is still default 1500.
Changes made are as follows:
"HKLM\Comm\Cellular Line\Parms\tcpip" Set to 1450, MSS is still 1460
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NdisWan\Parameters\Protocols\0" and also changed \Parameters to \Parms as they all within Registry on WM6 and set ProtocolMTU, PPPProtocolType and ProtocolType as in XP, MTU set to 1450 but the MSS is still 1460.
I am using Windows Mobile 6.
The tool i use on the PDA is the Microsoft Power Toys Analyzer, copy the file to my XP machine and open the netlog0 file with Wireshark and investigate the capture.
The latter of the two keys is how the MTU is changed on a Windows XP machine.
I do know that data cards connected to a PC that use the WWAN protocol for GPRS connection will list a Wireless Network Interface card and for that the MTU would be changed under the network adapter itself, if they are using the PPP Protocol and listed as a Dial Up adapter the the latter key above must be used, all tested and works a treat.
I am imaging that PDA devices must work in the same way.
The devices i am currently using definatly use the PPP Protocol to connect, can anyone advice how this MTU is changed or even advice how to tweak registry to get GPRS to use WWAN, the latter may be impossible for me as i am not a software developer, tweaks i can handle.
Well thanks for looking at my post and i hope someone can point me into the correct direction.
Many Thanks
Martin.

if you pissed off with t-mob comm mngr settings

i am piised off, dont know why but when you fully install t-mob rom link to discoonect from wi-fi is not there when you click wifi icon, instead there is a connection manager link there. so i have hard reset me phone stopped t-mob ist. and checked files.
in command mngr cust. cab there was ome entries and i found my way.
to get back your disconnect-connect wifi link ( when you clicked to wifi/gprs icon )
go to
HKLM\ControlPanel\9
and change
Group value 65536 to 2
then
go to HKLM\ControlPanel\WrlsMgr
clear \Windows\CommManager.exe from Redirect
plus change Group 65536 to 2
and you are done.
hopefully some one will add this one to hermes tweaker

Thanks M8;
Also they have tried to stop you from chsing UMTS under phone settings! your choice is now limited to Auto or GSM and you can no longer use the UMTS band 2100 etc only the mix. The cab responciable for this is PP_Remove_UMTS_Only_(Network_Band).CAB in \windows it is invoked in PreConfig.txt part of preautorun.exe. Anyway to get it back just use this :-
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting]
"ShowPIN2Page"=dword:00000001
"ONSDisplayRule"=dword:00000001
"Enable3GLongNamePrefix"=dword:00000000
"LongNamePrefix"="UMTS"
"EnableUsimEF"=dword:00000001
"ShowNITZPage"=dword:00000000
"HiddenFDNFunction"=dword:00000000
"HiddenBCFunction"=dword:00000000
"FDNQueryPBTimeout"=dword:00060000
"ShowFDNPage"=dword:00000001
"ShowTtyPage"=dword:00000001
"ShowUMTSBandPage"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting\BandType]
"ItemValue4"=dword:00000003
"ItemName4"="UMTS(2100+800)"
"ItemValue3"=dword:00000002
"ItemName3"="GSM(1900+850)+UMTS(1900+850)"
"ItemValue2"=dword:00000001
"ItemName2"="GSM(900+1800)+UMTS(2100)"
"ItemValue1"=dword:00000000
"ItemName1"="Auto"
"ItemCount"=dword:00000004
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting\NetworkType]
"ItemValue3"=dword:00000002
"ItemName3"="WCDMA (3G)"
"ItemValue2"=dword:00000001

which UMTS i should choose on t-mobile?

Here in the UK keep the band type to Auto it will give you wider coverage.

[SFR TV] for Dream WITHOUT option full Internet XXX

Hello,
I want to view TV channel on my HTC Dream with my illimythics 3G (standard) contract.
SFR tell me it's impossible to do this with iPhone and Android, You must have the option "full Internet Or option iPhone".
I don't wan't to pay an option I have ALREADY have : If my SIM card is in my HTC Cruise Polaris (WM6) I have TV ...
I test if SFR take the hardware or software limitation : This is SOFTWARE limitation :
I am put my SIM card into my Dream G1, make a gateway 3G+ - Wifi, and coonect my cruise without SIM card to the adhoc of my dream and I can see my TV ....
I have also test with another User Agent, this is good results.
I search for an internet Browser with custumisable UA, and it can play the RTSP protocol with this option (for find codec !)
Code:
s=W9
i=RealSystem Broadcast Distribution
c=IN IP4 0.0.0.0
t=0 0
a=SdpplinVersion:1610641560
a=StreamCount:integer;2
a=control:*
a=LiveStream:integer;1
a=LatencyMode:integer;0
a=Title:buffer;"VzkA"
a=range:npt=0-
a=tool:sdpgen 0.1
m=audio 0 RTP/AVP 96
b=AS:12
b=TIAS:12000
b=RR:450
b=RS:150
a=maxprate:16.000000
a=control:streamid=0
a=range:npt=0-
a=length:npt=0
a=rtpmap:96 AMR/8000
a=fmtp:96 octet-align=1;
a=mimetype:string;"audio/AMR"
a=ForceRTP:integer;1
a=AvgBitRate:integer;12000
a=ASMRuleBook:string;"RTCPRule=0,TimestampDelivery=True,Marker=0,AverageBandwidth=12000;RTCPRule=1,TimestampDelivery=True,Marker=1;"
a=PayloadWirePacket:string;"rtp"
m=video 0 RTP/AVP 97
b=AS:100
b=TIAS:100000
b=RR:3750
b=RS:1250
a=maxprate:16.000000
a=control:streamid=1
a=range:npt=0-
a=length:npt=0
a=rtpmap:97 H263-2000/90000
a=fmtp:97
a=mimetype:string;"video/H263-2000"
a=ForceRTP:integer;1
a=AvgBitRate:integer;100000
a=Preroll:integer;1000
a=ASMRuleBook:string;"RTCPRule=0,TimestampDelivery=True,Marker=0,AverageBandwidth=100000;RTCPRule=1,TimestampDelivery=True,Marker=1;"
a=PayloadWirePacket:string;"rtp"
a=framesize:97 176-144
Thanks.

HELP! Slow Internet Speeds

I'm hoping someone can help me...
I've seen similar threads with no answer.
I'm currently running MattC FroyoSense v3.2, and the rest of my setup can be seen in my signature.
I'm getting really poor internet speeds, whether it be tethered, wifi hotspot, or directly on the phone's browser. I'm lucky if I get anything over 300k, despite always being in HSDPA or 3G.
I see others are getting well over 1MB, so clearly somethings not right on my end.
Can anyone help??

nova hands said:
I'm hoping someone can help me...
I've seen similar threads with no answer.
I'm currently running MattC FroyoSense v3.2, and the rest of my setup can be seen in my signature.
I'm getting really poor internet speeds, whether it be tethered, wifi hotspot, or directly on the phone's browser. I'm lucky if I get anything over 300k, despite always being in HSDPA or 3G.
I see others are getting well over 1MB, so clearly somethings not right on my end.
Can anyone help??
Click to expand...
Click to collapse
Check APN/DNS settings.

nova hands said:
I'm hoping someone can help me...
I've seen similar threads with no answer.
I'm currently running MattC FroyoSense v3.2, and the rest of my setup can be seen in my signature.
I'm getting really poor internet speeds, whether it be tethered, wifi hotspot, or directly on the phone's browser. I'm lucky if I get anything over 300k, despite always being in HSDPA or 3G.
I see others are getting well over 1MB, so clearly somethings not right on my end.
Can anyone help??
Click to expand...
Click to collapse
Did you try add this to yours build prop
ro.ril.hsxpa=3
ro.ril.gprsclass=32
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=14
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=8
ro.ril.def.agps.mode=1
ro.ril.def.agps.feature=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.disable.power.collapse=0
Also you can check this out http://forum.xda-developers.com/showthread.php?t=768998&highlight=enable+hsdpa

leon98408 said:
Did you try add this to yours build prop
ro.ril.hsxpa=3
ro.ril.gprsclass=32
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=14
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=8
ro.ril.def.agps.mode=1
ro.ril.def.agps.feature=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.disable.power.collapse=0
Also you can check this out http://forum.xda-developers.com/showthread.php?t=768998&highlight=enable+hsdpa
Click to expand...
Click to collapse
Is this okay to do on a TMOUS HD2?

Well, I tried it, and it didn't work that well.
I got intermittent internet, and the Market and PDA Net didn't work at all.
Had to revert to my original settings.
This is getting so frustrating.

nova hands said:
Well, I tried it, and it didn't work that well.
I got intermittent internet, and the Market and PDA Net didn't work at all.
Had to revert to my original settings.
This is getting so frustrating.
Click to expand...
Click to collapse
I get on average 4.2mbps or so, but I have found that this varies due to the WM ROM and RADIO that I use to put the DROID Build onto. Maybe this will help, if not then the APN name can be changed in the settings but make sure its set to 'mobile internet' of the network and not GSM, HSDPA etc (Mobile Internet will give the biggest speed your phone can handle.

nova hands said:
I'm hoping someone can help me...
I've seen similar threads with no answer.
I'm currently running MattC FroyoSense v3.2, and the rest of my setup can be seen in my signature.
I'm getting really poor internet speeds, whether it be tethered, wifi hotspot, or directly on the phone's browser. I'm lucky if I get anything over 300k, despite always being in HSDPA or 3G.
I see others are getting well over 1MB, so clearly somethings not right on my end.
Can anyone help??
Click to expand...
Click to collapse
It might just be your area. Click on my thumbnail for a closer look at settings, it may help.

deadmansink said:
It might just be your area. Click on my thumbnail for a closer look at settings, it may help.
Click to expand...
Click to collapse
I changed my settings to match yours, but I'm still only getting 0.60Mb/s...
I wonder if it's my WinMO ROM and Radio combo.
I'm in Springfield, MO. I don't think there's 4G coverage here yet, but I still have the "H" on my phone, so it's gotta be faster than 0.60Mb/s, right?
EDIT: Where exactly in the build.prop do those "#DNS" values go?? I downloaded a modified build.prop, but it didn't work well. I lost connection to the Market and any apps I had that used the web, like speedtest.net and PDANet. Maybe you could email your build.prop and I can try it on mine?

nova hands said:
I changed my settings to match yours, but I'm still only getting 0.60Mb/s...
I wonder if it's my WinMO ROM and Radio combo.
I'm in Springfield, MO. I don't think there's 4G coverage here yet, but I still have the "H" on my phone, so it's gotta be faster than 0.60Mb/s, right?
EDIT: Where exactly in the build.prop do those "#DNS" values go?? I downloaded a modified build.prop, but it didn't work well. I lost connection to the Market and any apps I had that used the web, like speedtest.net and PDANet. Maybe you could email your build.prop and I can try it on mine?
Click to expand...
Click to collapse
Do you have root explorer or equivalent? system/build.prop

deadmansink said:
Do you have root explorer or equivalent? system/build.prop
Click to expand...
Click to collapse
Yeah. I have ES File explorer.
I know how to edit the build.prop, I just don't know where in the document to add those #DNS settings...
Does it get added to the end of the document?

nova hands said:
Yeah. I have ES File explorer.
I know how to edit the build.prop, I just don't know where in the document to add those #DNS settings...
Does it get added to the end of the document?
Click to expand...
Click to collapse
You just need to replace the number on those
net.ppp0.dns1=
net.ppp0.dns2=
net.dns1=
net.dns2=
net.dns3=

nova hands said:
Yeah. I have ES File explorer.
I know how to edit the build.prop, I just don't know where in the document to add those #DNS settings...
Does it get added to the end of the document?
Click to expand...
Click to collapse
You won't be adding it fresh, scroll down and look for the same info as my signature thumbnail, click on it for a larger look.

deadmansink said:
You won't be adding it fresh, scroll down and look for the same info as my signature thumbnail, click on it for a larger look.
Click to expand...
Click to collapse
EDIT: See my next post.

nova hands said:
Right. I see the DNS settings you have in the picture in your signature.
I understand that those go into my build.prop.
My question is, do I ADD those settings to the long list of stuff that's already in my build.prop file, or am I supposed to delete something from the build.prop and put your settings in its place?
Click to expand...
Click to collapse
When you scroll down your list, towards the bottom, you'll see yours, you will be changing, and possibly add the DNS3 that I show.

deadmansink said:
When you scroll down your list, towards the bottom, you'll see yours, you will be changing, and possibly add the DNS3 that I show.
Click to expand...
Click to collapse
Hmmm...
Mine doesn't look like that.
Here are the last few lines in my build.prop:
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
I don't see any section of the build.prop that looks like what yours is.
Here's my build.prop:
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=5
ro.ril.hsxpa=2
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.enable.amr.wideband=0
ro.com.google.clientidbase=android-htc
ro.ril.vmail.23415=1571,BT
# begin build properties
# autogenerated by buildinfo.sh
ro.build.changelist=278359
ro.com.google.clientidbase=android-htc
ro.build.changelist=278359
ro.com.google.clientidbase=android-htc
ro.build.id=FRF91
ro.build.display.id=FRF91
ro.build.version.incremental=278359
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=四 10月 28 16:49:04 CST 2010
ro.build.date.utc=1288255744
ro.build.type=user
ro.build.user=root
ro.build.host=HPA008
ro.build.tags=release-keys
ro.product.model=HTC HD2
ro.product.brand=htc_wwe
ro.product.name=htc_bravo
ro.product.device=bravo
ro.product.board=bravo
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=qsd8k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bravo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=MDJ FroYo -=HD=-
ro.build.description=MDJ FroYo -=HD=-
ro.build.changelist=278359
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_bravo/bravo/bravo:2.2/FRF91/218634:user/release-keys
ro.build.project=155891
ro.product.version=4.3
keyguard.no_require_sim=1
# end build properties
#
# system.prop for ace
#
ro.sf.lcd_density=240
debug.fb.rgb565 = 0
rild.libpath=/system/lib/libhtc_ril.so
# Modify MMS APN retry timer from 5s to 2s.
ro.gsm.2nd_data_retry_config = max_retries=3, 2000, 2000, 2000
# ace RF team request
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 8
ro.ril.hsupa.category = 5
ro.ril.hsxpa = 2
# Default network type.
# 0 => WCDMA preferred.
ro.telephony.default_network=0
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.
dalvik.vm.heapsize=24m
# For the default value of agps
ro.ril.def.agps.mode = 2
# For HSDPA low throughput
ro.ril.disable.power.collapse = 0
# For emmc phone storage
ro.phone_storage = 0
# 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/
# Release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.version = Bluetooth 2.1 + EDR
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles = 4270339
# 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
# For quick boot mode
persist.sys.shutdown.mode = hibernate
# For opensense sdk
ro.htc.common.version = 2.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.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=OPTIONAL
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.google.clientidbase=android-htc
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.2_r7
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=0
htc.audio.hac.enable=0
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.setupwizard.enterprise_mode=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4

nova hands said:
Hmmm...
Mine doesn't look like that.
Here are the last few lines in my build.prop:
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
I don't see any section of the build.prop that looks like what yours is.
Here's my build.prop:
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=5
ro.ril.hsxpa=2
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.enable.amr.wideband=0
ro.com.google.clientidbase=android-htc
ro.ril.vmail.23415=1571,BT
# begin build properties
# autogenerated by buildinfo.sh
ro.build.changelist=278359
ro.com.google.clientidbase=android-htc
ro.build.changelist=278359
ro.com.google.clientidbase=android-htc
ro.build.id=FRF91
ro.build.display.id=FRF91
ro.build.version.incremental=278359
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=四 10月 28 16:49:04 CST 2010
ro.build.date.utc=1288255744
ro.build.type=user
ro.build.user=root
ro.build.host=HPA008
ro.build.tags=release-keys
ro.product.model=HTC HD2
ro.product.brand=htc_wwe
ro.product.name=htc_bravo
ro.product.device=bravo
ro.product.board=bravo
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=qsd8k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bravo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=MDJ FroYo -=HD=-
ro.build.description=MDJ FroYo -=HD=-
ro.build.changelist=278359
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_bravo/bravo/bravo:2.2/FRF91/218634:user/release-keys
ro.build.project=155891
ro.product.version=4.3
keyguard.no_require_sim=1
# end build properties
#
# system.prop for ace
#
ro.sf.lcd_density=240
debug.fb.rgb565 = 0
rild.libpath=/system/lib/libhtc_ril.so
# Modify MMS APN retry timer from 5s to 2s.
ro.gsm.2nd_data_retry_config = max_retries=3, 2000, 2000, 2000
# ace RF team request
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 8
ro.ril.hsupa.category = 5
ro.ril.hsxpa = 2
# Default network type.
# 0 => WCDMA preferred.
ro.telephony.default_network=0
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.
dalvik.vm.heapsize=24m
# For the default value of agps
ro.ril.def.agps.mode = 2
# For HSDPA low throughput
ro.ril.disable.power.collapse = 0
# For emmc phone storage
ro.phone_storage = 0
# 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/
# Release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.version = Bluetooth 2.1 + EDR
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles = 4270339
# 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
# For quick boot mode
persist.sys.shutdown.mode = hibernate
# For opensense sdk
ro.htc.common.version = 2.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.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=OPTIONAL
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.google.clientidbase=android-htc
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.2_r7
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=0
htc.audio.hac.enable=0
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.setupwizard.enterprise_mode=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
Click to expand...
Click to collapse
Change what you have and add what I have above it, just like you see it in mine and then save

deadmansink said:
Change what you have and add what I have above it, just like you see it in mine and then save
Click to expand...
Click to collapse
Okay.
I'll try that.
Should I also add the "# DNS" part?

nova hands said:
Yeah. I have ES File explorer.
I know how to edit the build.prop, I just don't know where in the document to add those #DNS settings...
Does it get added to the end of the document?
Click to expand...
Click to collapse
Exactly as it is read.

deadmansink said:
Exactly as it is read.
Click to expand...
Click to collapse
I'll try that.
On a side note, I restored the phone back to factory default WinMO.
I did a speed test, and I'm getting the same exact speeds.
Now, my first thought was that it was all just limited to network, but I called t-mobile, and they assured me that I'm in an area where I should be getting higher speeds.
Beyond that, they couldn't help me at all.
I'm going to hold off reinstalling Android until I get some decent speeds in WinMO.
Thanks for all the help!

Man... I've searched all over these forums, and I can't find an answer to this.
Why can't I get decent data speeds?!
I'm back on stock WinMO, and it's still stuck around 500Kb/s!
There's gotta be SOMETHING I'm missing...
The network here supports higher speeds, and I'm not getting them.

[INFO] WaccoPedia - Sharing is Caring

Sharing is Caring - Caring is Helping - Helping is Sharing​
{
"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"
}
Purpose of this thread is to share some useful basic information as gathered using my (rooted) HTC Desire HD, and is meant as non posting/replying reference only thread.
Thanks to all who've posted useful info, helped me with all my questions and contributed their knowledge and skills with the community.
Special thanks to Mike1986 and all ARHD team members for showing skills, respect, patience and humor.
and
BIG respect for all great people I've met on various forums and sites for making great Android ROMs, MODs Themes, Apps, Scripts etc. and for all the posts containing useful and friendly information.
Kernel: "abbreviations"
Governors:
Radio: Preferred Network types and info
RUU (ROM Upgrade Utility):
Android Partitions:
Android: Anatomy and Physiology
CID: Carrier ID (+ some codes)​
GLOSSARY
Code:
[B]2G[/B]
The second generation of mobile telephony systems uses digital encoding. 2G networks support high bit rate voice, limited data communications and different levels of encryption. 2G networks include GSM, D-AMPS (TDMA) and CDMA. 2G networks can support SMS applications.
2.5G
2.5G extends 2G systems, adding features such as packet-switched connection and enhanced data rates. 2.5G networks include EDGE and GPRS. These networks support WAP, MMS, SMS mobile games, and search and directory.
[B]3G[/B]
The third generation of mobile systems provides high-speed data transmissions of 144Kbps and higher. 3G will support multimedia applications such as full-motion video, video conferencing and Internet access.
[B]4G[/B]
As of the end of 2009 it was consensus that 4G would designate Mobile Network technologies beyond 3G and its extensions "3,5G" (HSPA) , "3,75G" (HSPA+). These would logically include WiMax and LTE. In the beginning of 2011 carriers in the US started to misuse the term, advertising their HSPA networks as 4G press coverage on thisismynext Officially, the term 4G has been defined by the ITU to include LTE-Advanced and WirelessMAN-Advanced (WiMax2), none of witch are deployed anywhere still. GSMA PR
802.1X
As the IEEE standard for access control for wireless and wired LANs, 802.1x provides a means of authenticating and authorizing devices to attach to a LAN port. This standard defines the Extensible Authentication Protocol (EAP), which uses a central authentication server to authenticate each user on the network.
802.11
The IEEE standard for wireless Local Area Networks. It uses three different physical layers, 802.11a, 802.11b and 802.11g.
802.11a
Operating in the 5 GHz band, 802.11a supports a maximum theoretical data rate of 54 Mbps, but more realistically it will achieve throughput somewhere between 20 Mbps to 25 Mbps in normal traffic conditions. In a typical office environment, its maximum range is 50 meters (150 feet) at the lowest speed, but at higher speed, the range is less than 25 meters (75 feet). 802.11a has four, eight, or more channels, depending on the country. WLAN products based on 802.11a technology are rapidly coming to market in 2003, making them more affordable and widely available.
802.11b
Most WLANs deployed today use 802.11b technology, which operates in the 2.4 GHz band and supports a maximum theoretical data rate of 11 Mbps, with average throughput falling in the 4 Mbps to 6 Mbps range. In a typical office environment, its maximum range is 75 meters (250 feet) at the lowest speed, but at higher speed its range is about 30 meters (100 feet). Bluetooth devices, 2.4 GHz cordless phones and even microwave ovens are sources of interference (and thus create poor performance) for 802.11b networks. Minimizing interference can be difficult because 802.11b uses only three non-overlapping channels. 802.11b products have been shipping in quantity for several years so you will find that products are plentiful and affordable.
802.11e
802.11e provides Quality of Service (QoS) support for LAN applications, which will be critical for delay-sensitive applications such as Voice over Wireless IP (VoWIP). The standard will provide classes of service with managed levels of QoS for data, voice, and video applications.
802.11g
The 802.11 task force is still developing 802.11g, and it is expected to be ratified as a standard by mid-2003. 802.11g offers the throughput of 802.11a with the backward compatibility of 802.11b. 802.11g will operate in the 2.4 GHz band but it will deliver data rates from 6 Mbps to 54 Mbps. Like 802.11b, it will have up to three non-overlapping channels. 802.11g uses orthogonal frequency-division multiplexing (OFDM) modulation as does 802.11a, but, for backward compatibility with 11b, it also supports complementary code keying (CCK) modulation and, as an option for faster link rates, allows packet binary convolutional coding (PBCC) modulation.
Its "backward compatibility" with 802.11b means that when a mobile 802.11b device joins an 802.11g access point, all connections on that access point slow down to 802.11b speeds.
802.11h
This standard is supplementary to the MAC layer to comply with European regulations for 5GHz WLANs. European radio regulations for the 5GHz band require products to have transmission power control (TPC) and dynamic frequency selection (DFS). TPC limits the transmitted power to the minimum needed to reach the furthest user. DFS selects the radio channel at the access point to minimize interference with other systems, particularly radar. Pan-European approval of 802.11h is not expected until the end of 2003.
802.15
This IEEE working group addresses the standard for WPANs. It has four active task groups.
802.15.1 had the job of delivering the standard for low-speed, low-cost WPANs and is based on the Bluetooth spec.
The 802.15.2 task group is developing the recommended practices on how 802.11 WLANs and 802.15 WPANs can co-exist in the 2.4 GHz band. It is mainly working on the interference problem between Bluetooth and 802.11.
The 802.15.3 task group is delivering a standard for higher speed WPANs from 10 Mbps to 55 Mbps at distances less than 10 meters.
The 802.15.4 task group is preparing a standard for simple, low-cost, low-speed WPANs. Data ranges from 2 Kbps to 200 Kbps and uses DSSS modulation in the 2.4 GHz and 915 MHz ranges.
.apk or APK's
An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened and inspected using common archive tools
.tar
Similar to a zip file, a tar file archives multiple files into one file
.tgz
TGZ files are commonly used as install packages for Slackware Linux.
ActiveSync
This program by Microsoft is what we all use to connect to our computers at work or at home. It allows contacts, tasks, emails and Calendar events to be synchronised with Outlook as well as such things as media and favorites. In Windows Vista this has been replaced by the Windows Mobile Device Center. In addition ActiveSync allows browsing of the device in Windows Explorer and programs can be installed via an 'InstallShield' type package installer. AES - Advanced Encryption Standard.
Security issues are a major concern for wireless LANs. AES is the U.S. government's next-generation cryptography algorithm, which will replace DES and 3DES.
AKU
Adaptation Kit Update - Starting with Windows Mobile 5 Microsoft began a policy of updates similar to that of the desktop windows. Rather the replacing the whole OS some functionality may be added. For example AKU 2.0 introduced push mail. These updates are distributed through the OEMs and are given to the consumer in form of ROM updates. Note that OEM may choose not to create an update with the latest AKU for their devices. Getting an AKU for your phone is like getting the SP2 (Service Pack 2) for your Windows Xp.
AP - Access Point.
Wireless devices, such as laptops or PDAs, connect to a wired LAN via an AP, which is a hardware device or a computer's software that acts as a communication hub. APs provide heightened wireless security and extend the physical range of a wireless LAN.
Application Unlock
Most Windows Mobile phones only allow you to load applications that have an acceptable digital signature. If you try to edit the registry or load an application it will give you an error. Application Unlocking removes this barrier and allows you to install any application or edit the registry to your liking.
Bluetooth
A wireless technology developed by Ericsson, Intel, Nokia and Toshiba that specifies how mobile phones, computers and PDAs interconnect with each other, with computers, and with office or home phones. The technology enables data connections between electronic devices in the 2.4 GHz range. Bluetooth would replace cable or infrared connections for such devices.
Bootloader
The bootloader is the first thing to load once you turn on the device, this does the job of booting up the device hardware and loading various items into memory before the ROM starts in the device. The bootloader is also responsible for enabling the flashing of new ROMs and other components such as the Radio and the Ext_ROM. Two modified bootloaders for the Hermes are HardSPL and SSPL.
To enter the bootloader, press and hold the OK and POWER buttons while inserting the stylus into the reset hole on the bottom of the Hermes.
BREW - Binary Runtime Environment for Wireless
Developed by Qualcomm, BREW is an open source application development platform for wireless devices. BREW developers can create portable applications that work on any CDMA handset. Applications include SMS, e-mail, location positioning, games and Internet radio.
When first introduced, BREW was solely for CDMA handsets. BREW has since been enabled for GSM handsets and expects to add TDMA handsets. BREW and J2ME are competing head-to-head for the wireless application development market.
CDMA - Code Division Multiple Access
A digital wireless technology that uses a spread spectrum technique to scatter a radio signal across a wide range of frequencies. CDMA is a 2G technology. WCDMA, a 3G technology, is based on CDMA.
CDMA has multiple variants, including CDMA 1X, cdma2000, CDMA2000 1X, CDMA2000 1xEV-DO and cdmaOne.
CID
The CID (Carrier ID) of the device is a setting which determines which carrier ROMs should be allowed to run on the device. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have SuperCID which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted.
CID Unlock
Load any carrier ROM (in any language) on the device.
CLDC - Connected Limited Device Configuration
CLDC outlines the basic set of libraries and Java virtual machine features that must be present in each implementation of a J2ME environment.
Cooked
Refers to ROMs which have been modified and optimised by users to offer better performance than a carrier ROM
CustomRUU
CustomRUU is an RUU (Rom Upgrade Utility) which has support for ALL SPL versions including HardSPL and SSPL.
Dalvik (cache)
Dalvik cache is a program cache area for the program dalvik. Dalvik is a java based virtual machine that is the bases for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program.
De-Odex
Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
EDGE - Enhanced Data GSM Environment
A 2.5G technology that enhances GSM. EDGE increases transmission speeds on GSM networks and enables the transmission of large amounts of data at 384Kbps. With EDGE, mobile operators can deliver multimedia and other broadband applications to mobile phones.
EPOC
EPOC is an operating system developed by Symbian for small, portable computer-telephones with wireless access to phone and other information services. EPOC is based on an earlier operating system from Psion, the first major manufacturer of personal digital assistants (PDAs). The term is no longer in use and is now referred to as Symbian OS.
Ext_ROM or ExtROM
The Ext_ROM (or Extended Rom) is a dedicated part of the ROM memory that is (by default) hidden to the user. This area typically includes cab files that are loaded upon Hard Reset. Also, if the author of a ROM wishes, the flashing process can preserve the Ext_Rom. This space is frequently used by carriers, or others creating ROMs, to store cabs that load settings onto the phone.
Firmware
This is a piece of software that is stored in a device to make it function. It is, unlike ordinary software, usually semi-permanent and resides in a non-volatile storage area which is unaffected by "hard resetting" a device. The term usually refers to low-level code that controls individual hardware components such as a radio rom.
Flash
Term meaning to write something (usually a ROM image) to a non-volatile chip. The term originates from original chip writers (EPROM blowers) which used to write to a chip by fusing tiny areas in the chip making individual links either short circuit or open circuit.
GPRS - General Packet Radio Service
GPRS is a radio technology for GSM networks that adds packet-switching protocols. As a 2.5G technology, GPRS enables high-speed wireless Internet and other data communications. GPRS networks can deliver SMS, MMS, email, games and WAP applications.
GPS
This stands for Global Positioning System. It is technology whereby your device communicates with satellites in orbit around the planet to determine your location within an error margin of a few meters.
GSM - Global System for Mobile communications
GSM, a 2G technology, is the de facto European standard for digital cellular telephone service, and it is also available in the Americas. GSM is the most widely used of the three digital wireless telephone technologies (TDMA, GSM and CDMA), and it supports voice, data, text messaging and cross-border roaming. The SIM (Subscriber Identification Module), a removable plastic card that contains a users data, is an essential element in a GSM network.
GSM operates in multiple frequency bands, GSM 900, GSM 1800, GSM 1900. When GSM is working on a radio frequency of 1800 MHz, it is sometimes referred to as DCS 1800, GSM1800 or PCN.
H.323
H.323 is the standard for interoperability in audio, video, and data transmissions, as well as Internet phone and Voice over IP. The standard addresses call control and management for point-to-point and multipoint conferences, as well as gateway administration of media traffic, bandwidth, and user participation.
HardSPL
This modified bootloader allows a much safer flashing process to take place since it reduces the chance of permenently bricking your HTC based device. It also removes the need to CID Unlock the device since it ALWAYS reports SuperCID when flashing.
Hard Reset
Similar to a soft reset, by performing a hard reset you completely wipe your device and restore it to the position it was in when you first turned the device on after it was purchased or after a new ROM is flashed.
HDML - Handheld Device Markup Language
Handheld Device Markup Language is used to format content for Web-enabled mobile phones. HDML allows Internet access from wireless devices and is derived from HTML. Openwave created this proprietary language, and it can only be viewed on mobile phones that use Openwave browsers.
HDML was created before a WAP standard was defined. It uses Openwave's Handheld Device Transport Protocol (HDTP) instead of WAP. HDTP - Handheld Device Transport Protocol.
This protocol is optimized for HDML. It presents the HDML to the HDML interpreter in an appropriate format.
Heimdall
is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy S device
IDEN
A specialized mobile radio network technology that combines two-way radio, telephone, text messaging and data transmission into one network.
IPL
Initial program load - usually paired with Secondary Program Load (SPL), is the boot loader of your phone, much like the BIOS is the boot loader for your PC. Note: IPL/SPL are highly hardware dependent, flashing the wrong IPL/SPL is much more serious than a flashing the wrong ROM. It may be noted that, sometimes a ROM package also contains the IPL/SPL which will be flashed into your phone. Hence be extra careful what you are flashing.
J2ME - Java 2 Micro Edition.
Java 2 Platform, Micro Edition (J2ME) is the edition of the Java platform that is targeted at small, standalone or connectable consumer and embedded devices, such as cellular phones and personal digital assistants (PDAs). The J2ME technology consists of a virtual machine and a set of APIs suitable for tailored runtime environments for these devices. The J2ME technology has two primary kinds of components--configurations and profiles.
Java
Industry standard object-oriented language and virtual machine, invented by Sun Microsystems and formally released in 1996. Some phones support downloading of Java applications over the WAP connection. Sun's Java specifications include many Java APIs and platforms, including the JavaPhone API and PersonalJava platform.
Kang
The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Kernel
The central or core software component of most operating systems. Its responsibilities include managing the system's resources (the communication between hardware and software components) and can provide the lowest-level abstraction layer for resources (especially memory, processors, and I/O devices).
Messaging
SMS (Short Message Service) is a feature available with some wireless phones that allows users to send and/or receive short alphanumeric messages.
Picture Messaging allows users to send and receive picture messages along with text. Users can choose from several preset and/or received pictures stored in their phones. Some phones also contain a picture editor.
Chat Messaging lets users "talk" using SMS messages.
MMS (Multimedia Messaging Service) is a new standard that is being defined for use in advanced wireless terminals. The service allows for non-real-time transmission of various kinds of multimedia content, such as images, audio, and video clips.
MexE - Mobile Station Application Execution Environment.
Mobile Station Application Execution Environment is a framework to ensure a predictable environment for third-party applications in GSM or UMTS handsets. MExE does this by defining different technology requirements called "classmarks." MExE classmark 1 is based on WAP, classmark 2 on PersonalJava and JavaPhone, and classmark 3 on J2ME CLDC and MIDP. Other classmarks may be defined in the future. MExE specifies additional requirements for all classmarks, for instance a security environment, capability and content negotiation, a user profile, user interface personalization, management of services and virtual home environment. A handset can support multiple classmarks.
Microbrowser
Also called a mini-browser. Software built into a wireless device that allows users to access and display specially formatted Internet content, such as stock reports, news, and sports scores using a handset device.
Mobile Information Device Profile (MIDP)
Set of Java APIs that is generally implemented on the Connected Limited Device Configuration (CLDC). It provides a basic J2ME application runtime environment targeted at mobile information devices, such as mobile phones and two-way pagers. The MIDP specification addresses issues such as user interface, persistent storage, networking, and application model.
Nandroid or Nandroid Backup:
A file typically created in the custom recovery program, such as 4EXT Recovery, that is a carbon copy of whatever state your phone is in. The file is typically stored on the SD card for later use in case something should go wrong in a ROM or Update, or a Boot Loop occurs
.NET Compact Framework
The .NET Compact framework is a smaller version of the .NET Common Language Runtime, optimized for the deployment of mobile applications running on resource-constrained devices such as PDAs. .NET CF supports only devices running Microsoft operating systems-specifically, Windows CE 3.0 (used in Pocket PC 2000 and Pocket PC 2002 platforms).
OBEX - Object Exchange
Object Exchange is a set of protocols allowing objects such as vCard contact information and vCalendar schedule entries to be exchanged using either IrDA or Bluetooth. Symbian OS implements IrDA for exchange of vCards, for example between a Nokia 9210 Communicator and an Ericsson R380 Smartphone, and vCalendar.
OS
Operating System - the platform software for your phone, much like Windows 7 for your PC. Upgrading the OS is like, in PC terms upgrading from Windows Vista to Windows 7.
OC - OverClocking
Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer
PAN - Personal Area Network
Allows devices to work together and share information and services. Using technologies such as Bluetooth, Personal Area Networks can be created in public places, in the home, in the office, in a car. This network enables everyday devices to communicate wirelessly. For example, a PAN allows users the ability to wirelessly synchronize with a desktop device to access e-mail or the Internet.
Protocol
Similar to `Radio`. Both terms refer to the radio protocol stack, which is the software which handles communications with the mobile network.
QoS - Quality of Service
Quality of Service is a measure of network performance that reflects the network's transmission quality and service availability. QoS can come in the form of traffic policy in which the transmission rates are limited, thereby guaranteeing a certain amount of bandwidth will be available to applications. Or QoS may take the form of traffic shaping, which are techniques to reserve bandwidth for applications but not guarantee its availability.
Radio
The radio stack is responsible for the phone functionality of the device. This includes GPRS, GSM, UMTS, and GPS operations. The version you use depends on who your carrier is as users have reported versions working better on one carrier than the other.
ROM - Read Only Memory
The ROM holds the Operating system and other components such as the bluetooth and wifi stacks. The ROM is accompanied by the Radio, Ext_ROM, SPL and IPL. Carriers such as T-mobile or Vodaphone taylor the ROM to their specifications and version numbers do not carry the same meaning across different carriers. IF the carrier you use supports the device well they will usually release regular ROM updates.
Root
Common word associated with giving a user "super user" access to their phones programming and other various asspects that would normaly not be possible.
RTM
Release to manufacturing or Ready to market.
RUU
The RUU (Rom Upgrade Utility) is the program which runs on the pc when a new ROM is flashed.
Sense
HTC Sense is a user interface, based on the TouchFlo 3D user interface, developed by HTC for mobile devices running Android and Windows Mobile. HTC Sense is a “design experience, an architecture that is all about how people use the device, making their content personal to how they use the device.” However, HTC has confused the issue by calling HTC Sense a user interface in press releases about the launch of the HTC Hero in India. Announced June 24, 2009, the first phone running Android to feature HTC Sense was the HTC Hero, and the first Windows Phone to feature HTC Sense (an updated TouchFlo) was the HTC HD2, announced October 6, 2009.
SIM - Subscriber Identity Module
Cellular systems using GSM technology employ SIM modules to store user provisioning information. Non-volitale storage for contact information is also available on these modules. This is also commonly used in the form `SIM unlock`. Some phones are locked to the specific telco from which you purchase your phone, eg you can't use a locked O2 phone using a Vodaphone SIM/smart card. To use SIM card from other telco, you need to SIM unlock your phone. Note: In general, the phrase 'unlock your phone' usually refers to SIM-unlock, not CID unlock.
SIM Unlock
Use any carrier's SIM in the device.
SIP - Session Initiation Protocol
SIP is the real-time communication protocol for Voice over IP (VoIP), and it has been expanded to support video and instant-messaging applications. SIP performs basic call-control tasks, such as session set up and tear down and signaling for features such as hold, caller ID and call transferring. Its functions are similar to Signaling System 7 (SS7) in standard telephony and H.323 or Media Gateway Control Protocol in IP telephony.
With SIP, most of the intelligence for call setup and features resides on the SIP device or user agent, such as an IP phone or a PC with voice or instant-messaging software. In contrast, traditional telephony or H.323-based telephony uses a model of intelligent, centralized phone switches with dumb phones.
SOAP - Simple Object Access Protocol
SOAP is a way for a program running in one kind of operating system to communicate with a program in the same or another kind of an operating system using HTTP and XML.
Soft Reset
Soft resetting the device will lose all the data currently in RAM and any unsaved information, much like pressing the reset button on your pc. A soft reset is the first thing to try if your device has stopped responding.
SPL
Secondary Program Loader. Refer to `IPL` or `Bootloader` for further information.
SU
"Super user", or root permissions
SuperCID
By CID unlocking your device the value of the CID is changed to 'SuperCID'. This allows the flashing of ANY ROM to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
UMTS - Universal Mobile Telecommunications System
The 3G mobile telephone standard in Europe, standardized by ETSI. It supports a theoretical data throughput of up to 2 Mbps. Initial trials began in 2001, and it should be rolled out in most of the world by 2005.
UV - UnderVolting
Undervolting is the process of lowering the voltage supplied to the processor in order to achieve lower temperatures and/or saving battery
VoIP - Voice Over IP
VoIP is a set of technologies that enables voice to be sent over a packet network. While few corporations use VoIP today, its usage for messaging is expected to explode in the coming two years.
Users can communicate using VoIP as easily as they do with today's PBXes and public phone network. By leveraging the existing data network, companies can save significant amounts of money by using VoIP for toll-bypass, which is particularly important for multinational corporations. VoIP will also speed the adoption of unified messaging by transmitting voice, fax and e-mail messages. VoIP is also known as IP telephony.
Over the next several years, companies will deploy VoIP in conjunction with 802.11 wireless LANs, enabling workers to have WLAN-based mobile phones when in the office.
VoWIP - Voice over Wireless IP
Combining VoIP with 802.11 wireless LANs to create a wireless telephone system for offices is an emerging market segment. VoWIP enables businesses to leverage their wireless LANs to add voice communications, enabling companies to deploy and manage voice and data over a single wireless backbone.
From a network perspective, VoWIP applications require some reservation of bandwidth to support the real-time nature of voice. Proprietary standards like Spectralink Voice Priority (SVP) are today's solution; however, the IEEE is developing the 802.11e standard for quality of service as a long-term solution.
NOTE:
Thread is under construction, so please accept my appologies regarding not finished/updated posts or typo's
No claims can be made regarding content that I share. Consider this thread as "my private reference"

Kernel: "abbreviations"
A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree in which you can access your phone's hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel on top of the existing one, effectively overwriting it.
A quick and brief overview of some kernel "abbreviations" I've found ..
OC 1.6 - Over Clock max 1,6GHz
OC+1.9 - Over Clock max 1,9GHz
2WCR - Two Way Call Recording support - now you can record incoming and outgoing calls (takes the audio direct from the chipset line in/out)
NCR - No Call Recording support
BFS - Brain **** Scheduler is a task scheduler - major performance increase over stock CFS (Completely Fair Scheduler) -> is not recommended for ROM with Sense
VIO - V(r) Input/Output scheduler - controls data input and output (memory card, disk, etc..) - stock kernel has CFQ
SLQB - a low level memory allocator/manager
MIUI - kernel for MIUI ROM
CFS - Completely Fair Scheduler
CIFS - Common Internet File System (is a virtual file system for Linux to allow access to servers and storage appliances compliant with the SNIA CIFS Specification)
TUN - VPN support
VR - I/O scheduler (better than NOOP)
NOOP - The NOOP scheduler is the simplest I/O scheduler for the Linux kernel.
VDD - Voltage Drain Drain (refers to the positive operating voltage of a field effect semiconductor device.)
NLS - National Language Support

Governors:
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies.
- ondemand -> Available in most kernels, and the default governor in most kernels.
When the CPU load reaches a certain point, ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative -> Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand.
Conservative provides a less responsive experience than ondemand, but can save battery.
- performance -> Available in most kernels. It will keep the CPU running at the "max" set value at all times.
This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
- powersave -> Available in some kernels. It will keep the CPU running at the "min" set value at all times.
- userspace -> This lets programs that runs on the OS decide the CPU frequency.
- interactive -> The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle.
When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
- smartass -> Is an improved version of interactive governor (Best explanation i've found paraphrases to: based on interactive, but better.)
(smartass is a "double" governor (near interactive - awake mode, near conservative (but not the same) - sleep mode), so when you use it in sleep mode, actually you use only a "half" of it.
- smoothass -> (improved smartass)
- brazilianwax -> Very agresive version of smartass
- interactiveX -> Tweaked Interactive governor by Imoseyon by adding more features like suspend/wake profile
- ondemandX -> Tweaked and ported from 2.6.38 base Ondemand governor by Imoseyon by adding more features like suspend/wake profile
It's got its own sleep profile built in, so it doesn't play well with the OC daemon ..!
- smartassV2 -> smartassV2 is generally based on the implementation of interactive with some major changes and the addition of a built in sleep profile (behaves a bit differently when screen is off vs. on).
The smartassV2 improves the very naive scheme which the first smartass had.
- lagfree -> lag free, but not that battery friendly as ondemand
Note: as far as I could find it, smartass2 = smoothass. Original it was called smartass2, but the name has been changed into smoothass.
* wake_min_freq = setting -> minimal frequency for device while it's awake
* wake_max_freq = setting -> maximal frequency for device while it's awake
* sleep_min_freq = setting -> minimal frequency for device while it's sleeping
* sleep_max_freq = setting -> maximal frequency for device while it's sleeping
* wake_governor = governor for device while it's awake
* sleep_governor = governor for device while it's sleeping

Radio: Preferred Network types and info
GSM => GSM(2G), GPRS(2.5G), EDGE(2.75G), UMTS(3G), WCDMA(3G), HSDPA(3.5G/3G+) HSUPA(3.75G) {Cell Carrier examples: AT&T and T-Mobile}
CDMA => CDMA(2/3G) EV-DO(3G) WiMax(3/4G) {Cell Carrier examples: Verizon and Sprint}
HSPA+ Evolved High Speed Packet Access (84 Mbit/s in the downlink and 22 Mbit/s in the uplink)
H: HSDPA High Speed Downlink Packet Access (Category 8 - 7.2 / Category 10 - 14,0 Mbit/s in the downlink)
H: HSUPA High Speed Uplink Packet Access (Category 6 - 5.76 Mbit/s in the uplink)
3G: UMTS Universal Mobile Telecommunications System (384 kbit/s -> (max 2 Mbit)
E: EDGE Enhanced Data Rates for GSM Evolution (384 kbit/s)
G: GPRS General Packet Radio Service (52 kbit/s)
GSM Global System for Mobile Communications (14.4 kbit/s)
Remark:
The ROM has a file called "build.prop" with various important settings in it.
One of these settings is "ro.ril.hsxpa=2", this means you (might) have/use a HSDPA/HSUPA network (also called "HSPA") with high speed downloads and uploads, and this setting gives you the "U" in the radio name found in "Settings - About phone - Software information - More - (Baseband version)"
Code:
ro.ril.hsxpa indicates hsxpa support of the target network:
#
# Network parameters
#
#ro.ril.hsxpa : inidcates hsxpa support of target network :
# 0 - UMTS r99
# 1 - HSDPA
# 2 - HSDPA/HSUPA
#
#ro.ril.gprsclass : inidcates GPRS class of target network :
# Class 2 : 3 slots : 8 - 12 kbps upload / 16 - 24 kbps download
# Class 4 : 4 slots : 8 - 12 kbps upload / 24 - 36 kbps download
# Class 6 : 4 slots : 24 - 36 kbps upload / 24 - 36 kbps download
# Class 8 : 5 slots : 8 - 12 kbps upload / 32 - 40 kbps download
# Class 10 : 5 slots : 16 - 24 kbps upload / 32 - 48 kbps download
# Class 12 : 5 slots : 32 - 48 kbps upload / 32 - 48 kbps download
#
#ro.ril.hsdpa.category :
# Cat 1 = 1.2 Mbit/s
# Cat 2 = 1.2 Mbit/s
# Cat 3 = 1.8 Mbit/s
# Cat 4 = 1.8 Mbit/s
# Cat 5 = 3.6 Mbit/s
# Cat 6 = 3.6 Mbit/s
# Cat 7 = 7.2 Mbit/s
# Cat 8 = 7.2 Mbit/s
# Cat 9 = 10.1 Mbit/s
# Cat 10 = 14.0 Mbit/s
# Cat 11 = 0.9 Mbit/s
# Cat 12 = 1.8 Mbit/s
# Cat 13 = 17.6 Mbit/s
# Cat 14 = 21.1 Mbit/s
# Cat 15 = 23.4 Mbit/s
# Cat 16 = 27.9 Mbit/s
# Cat 19 = 35.3 Mbit/s
# Cat 20 = 42.2 Mbit/s
# Cat 21 = 23.4 Mbit/s
# Cat 22 = 27.9 Mbit/s
# Cat 23 = 35.3 Mbit/s
# Cat 24 = 42.2 Mbit/s
# Cat 25 = 46.8 Mbit/s
# Cat 26 = 55.9 Mbit/s
# Cat 27 = 70.6 Mbit/s
# Cat 28 = 84.4 Mbit/s
#
#ro.ril.hsupa.category :
# Cat 1 = 0.73 Mbit/s
# Cat 2 = 1.46 Mbit/s
# Cat 3 = 1.46 Mbit/s
# Cat 4 = 2.93 Mbit/s
# Cat 5 = 2.00 Mbit/s
# Cat 6 = 5.76 Mbit/s
# Cat 7 = 11.5 Mbit/s
#
#Not speed related, but still nice to have :
#ro.ril.enable.3g.prefix : adds the 3G prefix to the operator name.
# ro.ril.enable.dtm : Only set this to 1 if your network allows simultaneous
# transfer of Circuit switched (CS) voice and Packet switched
# (PS) data over the same radio channel (ARFCN).
Preferred Network types:
WCDMA preferred - Automatically switches between G/E/3G/H based on the best/strongest signal available and is supported by all providers.
Has high battery usage since it constantly scans the network for the strongest signal to switch.
GSM only - Only uses G/E and never switches to 3G/H. Should have minimal battery usage.
(there is a problem with GSM only on some older networks... so if data is used, you can miss calls, thus GSM auto (PRL) is the safest setting)
WCDMA only - The GSM phone is capable of using only 3G data communication. When the 3G signal is too low you get nothing at all.
Only uses HSDPA and will not switch to G/E/3G even if the HSPDA signal is too low. Use this only if you use your phone in a area with good coverage. Should have moderate battery usage.
GSM auto (PRL) - Automatically switches between G/E/3G/H based on the PRL (Preferred Roaming List) for a provider on your phone.
Not supported by all providers and may not be supported in certain regions. Should have moderate battery usage since it uses a predefined list to switch.
CDMA auto (PRL) - The CDMA phone is capable of using both 2G and 3G data communication and when signal strength is low 2G is favored more.
CDMA only - The CDMA phone is capable of using only 2G data communication. When the 2G signal is too low you get nothing at all.
EvDo only - The CDMA phone is capable of using only 3G data communication. When the 3G signal is too low you get nothing at all.
GSM/CDMA auto (PRL) - Some phones are equipped with both GSM and CDMA capabilities. This setting appears to just have the phone attempt to stay connected to the data communication type that works the best.
Unknown - If none of the above fit or the phone is acting weird as far as connecting to the carrier, you will see your preferred network type is set to this
General NOTE:
If not known how to get a preferred network type, dial *#*#4636#*#* , this brings you in the "Testing" menu, select "Phone information" and scroll down to "Set preferred network type: "
Always be careful with switching to "PRL" as device issues might occur if "PRL" is not supported by your network provider !!

RUU (ROM Upgrade Utility):
A) RUU Update - Flashing Android RUU Update Using HBoot
- First you need the RUU.exe that you intend to install.
- Run the RUU as Administrator.
- Tick the 'I understand the caution indicated above...' box, and click next.
- At this point do not go any further!
- Navigate to C:\Users\xxxxx\AppData\Local\Temp (xxxxx is your user name , and ... AppData is a hidden folder)
- You should see one or two folders like this example: {E328FA5C-81C2-4B70-96AE-D5418A9A5B75}
- Go into the folder with "dotnetinstaller.exe".
- Open the next folder. (like this example: {50F2F878-636A-496F-A7CB-544C067E0C4B}
- Copy "rom.zip" into another folder (outside of temp).
- At this point just Cancel and quit the ROM Update Utility.
- Rename the "rom.zip" to "PD98IMG.zip" and put it on to the root directory of your MicroSD card in your phone.
- Shut down the phone.
- Press the Power button + Volume down button at the same time and hold them untill you get to HBOOT (white screen with skateboarding android).
- Wait for the HBOOT to parse the zip file.
- Follow the on-screen instructions and boot into newly flashed device.
B) RUU Update - Install through PC
Download and install the latest HTC Sync and restart your computer.
- Download and run the 1.15.405.1 Test RUU as Administrator. (This one is known to find the Android DHD)
- Get to the "1. Connect the Smartphone to the USB Cable" step. (but no further !!!!)
- Go to the C:\Users\xxxxx\AppData\Local\Temp directory, and find the folder with dotnetinstaller.exe and inside the next folder find the rom.zip
- Delete this "rom.zip" (which is the 1.15 version !!) and replace it with the "rom.zip" copied out earlier!!! -> See A) RUU Update - Flashing Android RUU Update Using HBoot !!!
Back to the RUU installer ...
- Now click through the next buttons.
- The RUU Utility should now be set to update. You will see the version number of the rom at the final step.
- Click update...

Android Partitions:
Android uses several partitions to organize files and folders on the device. Each of these partitions has a distinct role in the functionality of the device.
Standard internal memory partitions on Android phones and tablets:
/boot
/system
/recovery
/data
/cache
/misc
Hardware specific partitions:
(They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.)
/radio
/wimax
SD card partitions:
/sdcard
/sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices.
Purpose and contents of each of these partitions:
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the bootloader and the kernel. Without this partition, the device will simply not be able to boot.
Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, other than the kernel and the bootloader. This includes the Android user interface as well as all the system applications that come pre-installed on the device. (Sense, boot animation, busybox, etc)
Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/radio
The phone's radio firmware, controls cellular, data, GPS, bluetooth.
/wimax
Firmware for Sprint's flavor of 4G, WiMax.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy S and several tablets – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.

Android: Anatomy and Physiology
Google IO's "Android: Anatomy and Physiology" .pdf​

CID: Carrier ID (+ some codes)
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from Vodafone (Vodafone is the ‘carrier’), your phone will only accept Vodafone ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
Code:
SuperCID 11111111
Asia-HK-CHT HTC__622
ATT CWS__001
BM BM___001
Bouygues-Telecom BOUYG201
Brightstar-PTB BSTAR502
Brightstar-SPA BSTAR301
Chunghwa-Taiwan CHT__601
CT HTCCN702
CU HTCCN703
DCM DOCOM801
DOPOD DOPOD701
Era T-MOB009
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-DAN H3G__F05
H3G-Italy H3G__402
H3G-ROI H3G__003
H3G-SWE H3G__G04
H3G-UK H3G__001
HTC-Asia-SEA HTC__037
HTC-Asia-SEA-WWE HTC__044
HTC-Australia HTC__023
HTC-BE HTC__E41
HTC-Czech HTC__C24
HTC-Denmark HTC__F08
HTC-Dutch HTC__E11
HTC-EastEurope HTC__032
HTC-ELL HTC__N34
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-GCC HTC__J15
HTC-GER HTC__102
HTC-India HTC__038
HTC-ITA HTC__405
HTC-Nor HTC__Y13
HTC-Norway HTC__H10
HTC-Poland HTC__B25
HTC-PTG HTC__506
HTC-Russia HTC__A07
HTC-Singapore ????????
HTC-SPA HTC__304
HTC-Sweden HTC__G09
HTC-Turkey HTC__M27
HTC-WWE HTC__001
Hutch-Australia HUTCH001
O2-DE O2___102
O2-UK O2___001
Open-Channel HTCCN701
Optus-Australia OPTUS001
ORANGE-AT ORANG113
ORANGE-BE ORANG012
ORANGE-CH-FRA ORANG203
ORANGE-CH-GER ORANG104
ORANGE-ES ORANG309
ORANGE-French ORANG202
ORANGE-PL ORANGB10
ORANGE-PO ORANG008
ORANGE-SK ORANG006
ORANGE-UK ORANG001
Rogers ROGER001
SMC-Voda-HK SMCVD001
StarHub-Singapore ????????
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMA T-MOB102
TMCZ T-MOB004
TMD T-MOB101
TMH T-MOB007
TMHR T-MOB006
TMMK T-MOBL11
TMNL T-MOB003
TMSK T-MOB008
TMUK T-MOB005
TMUS T-MOB010
TWM-TW HTC__621
VIRGIN-UK VIRGI001
VODA-Africa-South HTC__016
VODA-Australia VODAP021
VODA-Germany VODAP102
VODA-Greece VODAP006
VODA-Ireland VODAP019
VODA-Italy VODAP405
VODA-Mobilkom VODAP120
VODA-Netherland VODAPE17
VODA-New-Zealand VODAP022
VODA-Portugal VODAPD18
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-SFR VODAP203
VODA-Spain VODAP304
VODA-Swisscom-DE VODAP110
VODA-Swisscom-FR VODAP212
VODA-Swisscom-IT VODAP416
VODA-Swisscom-WWE VODAP015
VODA-TR VODAPM27
VODA-UK VODAP001

reserved for future usage 8

reserved for future usage 9

reserved for future usage 10

No questions, No comments Please
This is a refference only thread.
Thanks