Jump to content

O2 MMS problems


Guest Shuflie

Recommended Posts

Are you sure about this? I have Pauls vanilla android rom and the mms for o2 doesnt work on it.

I moved from 1.6 T Mobile ROM to 1.7 Vanilla last night.

The first thing I noticed is that I did not have to add an APN for o2 as it picked it up off my SIM card. Under the previous T Mobile firmware I had to manually add the APN. So there may be some merit in the suggestion that the T Mobile firmware somehow tries to "block" other MMS/Internet profiles.

That said, my internet works fine but MMS still doesnt work even on 1.7.....

Link to comment
Share on other sites

Guest starkos
When I was in o2 I asked manager if he would help put settings in manually for MMS he said the pulse was not yet supported by o2 and therefore will not be able to send/receive MMS.

This is along the lines of the conclusion i came to, i also remember reading somewhere that someone believed o2 has a whitelist of supported phones and that they had a similar experience with G1 until o2 enabled it? Have no idea to the validity of that what so ever, but kinda makes sense lol

Link to comment
Share on other sites

This is along the lines of the conclusion i came to, i also remember reading somewhere that someone believed o2 has a whitelist of supported phones and that they had a similar experience with G1 until o2 enabled it? Have no idea to the validity of that what so ever, but kinda makes sense lol

Is that the same case for Vodafone and Orange too ? I think people on those networks are struggling to get the pulse to work with MMS....

I just find it strange how "no brand" chinese phones off ebay will work on MMS with no problems on o2 - surely o2 dont manually add all of these handsets to some kind of whitelist ?!

Link to comment
Share on other sites

Guest chrisnic0

Yeah im running 1.7 custom and still no MMS on orange, sounds like Robot1000 is correct, I dont really use MMS that much but its just annoying that I cant :)

Chris

Link to comment
Share on other sites

Guest starkos
Is that the same case for Vodafone and Orange too ? I think people on those networks are struggling to get the pulse to work with MMS....

I just find it strange how "no brand" chinese phones off ebay will work on MMS with no problems on o2 - surely o2 dont manually add all of these handsets to some kind of whitelist ?!

Have no idea... I know what you mean about strange, I just can't see why most phones work except the pulse. If not o2 though, it's something in the firmware but I've never heard of an unlocked phone being tied to the original network only with regards to sending/receiving mms lol, its crazy :)

Link to comment
Share on other sites

Have no idea... I know what you mean about strange, I just can't see why most phones work except the pulse. If not o2 though, it's something in the firmware but I've never heard of an unlocked phone being tied to the original network only with regards to sending/receiving mms lol, its crazy :)

I think it has to be an element of the firmware on the phone. I cant believe that o2 would add the hundreds of different Chinese mobile handsets to their "whitelist" and the fact that its also affecting Orange and Vodafone subscribers suggests that its the phone that is causing the issue.

Edited by jlgmax
Link to comment
Share on other sites

Guest starkos
I think it has to be an element of the firmware on the phone. I cant believe that o2 would add the hundreds of different Chinese mobile handsets to their "whitelist" and the fact that its also affecting Orange and Vodafone subscribers suggests that its the phone that is causing the issue.

Yea I guess so, hopefully it's something Paul and the likes can look into if they get the time :)

Link to comment
Share on other sites

Guest curryhouse

Hi again, today I tried one more time to use MMS on Pulse with o2 but to no avail. I then popped in the T-mobile sim I purchased today (text & Web) and straight away I had T-mobile APN settings and I was able to send and receive MMS.

I think what other users have said is true that the phone MMS system has been made firmware redundant by T-mobile for other carriers.

Maybe it is because the Pulse is so new, branded phone etc and T-mobile want you to stay with them for a bit longer I`m just guessing.....

I will check back here often, it would be nice to continue to use my current o2 sim if somebody finds a work around.

Thank you all for posting.

curry

Link to comment
Share on other sites

Guest le_lutin
Hi again, today I tried one more time to use MMS on Pulse with o2 but to no avail. I then popped in the T-mobile sim I purchased today (text & Web) and straight away I had T-mobile APN settings and I was able to send and receive MMS.

I think what other users have said is true that the phone MMS system has been made firmware redundant by T-mobile for other carriers.

Maybe it is because the Pulse is so new, branded phone etc and T-mobile want you to stay with them for a bit longer I`m just guessing.....

I will check back here often, it would be nice to continue to use my current o2 sim if somebody finds a work around.

Thank you all for posting.

curry

I would understand that if it weren't for the fact that I am using the vanilla android ROM created by Paul. I don't believe that this ROM has anything to do with T-mobile (although I could be wrong).

I can't believe there is not some way to debug the interaction between the phone and the server as regards MMS. When I receive an MMS and click on the download button, I can see (from the arrows in the 3g/2g connection icon) that there is some exchange of data between the phone and the internet. So what is it doing? Where is this data going? I can't believe that there isn't some way to answer these questions. 

I'm on O2 by the way.

Link to comment
Share on other sites

Guest starkos

I know what you mean le_lutin, I don't even use mms much but it's just the principle of it that's drivin me nuts lol! I just find it crazy that an operator would go to those lengths to prevent mms on another network, but then why else is it not working when other android phones do...

Link to comment
Share on other sites

Guest edwardblum
I know what you mean le_lutin, I don't even use mms much but it's just the principle of it that's drivin me nuts lol! I just find it crazy that an operator would go to those lengths to prevent mms on another network, but then why else is it not working when other android phones do...

Is this affecting everyone regardless of whether they have received a code to unlock their phone or using a turbo sim type device?

Link to comment
Share on other sites

Guest zuccster

OK, this is weird. I have an unlocked Pulse with an O2 SIM / Simplicity post pay. I'm using 1.7 - MoDaCo Custom ROM - U8230 Vanilla Style. With the O2 post pay APNs from :

here

To re-iterate, I have NO T-mobile APNs, and I'm using the vanilla ROM.

When I run tcpdump while trying to send an MMS I'm seeing this:

# ./tcpdump-arm -i rmnet0

tcpdump-arm: WARNING: can't create rx ring on packet socket 3: 92-Protocol not available

tcpdump-arm: verbose output suppressed, use -v or -vv for full protocol decode

listening on rmnet0, link-type EN10MB (Ethernet), capture size 68 bytes

14:11:19.845138 ARP, Request who-has 149.254.201.135 tell 10.115.138.186, length 28

14:11:19.845721 ARP, Reply 149.254.201.135 is-at 02:50:f3:00:00:00 (oui Unknown), length 28

14:11:19.845825 IP 10.115.138.186.57611 > 149.254.201.135.8080: Flags [S], seq 1531108884, win 5840, options [sackOK,TS																													 val 6877974 ecr 0,mss[|tcp]>

...
A quick whois on 149.254.201.135 gives me:
inetnum:		149.254.201.0 - 149.254.201.255

netname:		TMUK-Byte-ACS

descr:		  T-Mobile(UK) Byte ACS LAN

country:		Gb

admin-c:		TMUK1-RIPE

tech-c:		 TMUK1-RIPE

status:		 ASSIGNED PA

mnt-by:		 TMUK1-MNT

source:		 RIPE # Filtered

This implies that there's something else in the ROM affecting the APN used for MMS - thoughts?

Edited by zuccster
Link to comment
Share on other sites

Guest le_lutin
OK, this is weird. I have an unlocked Pulse with an O2 SIM / Simplicity post pay. I'm using 1.7 - MoDaCo Custom ROM - U8230 Vanilla Style. With the O2 post pay APNs from :

here

To re-iterate, I have NO T-mobile APNs, and I'm using the vanilla ROM.

When I run tcpdump while trying to send an MMS I'm seeing this:

# ./tcpdump-arm -i rmnet0

tcpdump-arm: WARNING: can't create rx ring on packet socket 3: 92-Protocol not available

tcpdump-arm: verbose output suppressed, use -v or -vv for full protocol decode

listening on rmnet0, link-type EN10MB (Ethernet), capture size 68 bytes

14:11:19.845138 ARP, Request who-has 149.254.201.135 tell 10.115.138.186, length 28

14:11:19.845721 ARP, Reply 149.254.201.135 is-at 02:50:f3:00:00:00 (oui Unknown), length 28

14:11:19.845825 IP 10.115.138.186.57611 > 149.254.201.135.8080: Flags [S], seq 1531108884, win 5840, options [sackOK,TS 

  val 6877974 ecr 0,mss[|tcp]>

...
A quick whois on 149.254.201.135 gives me:
inetnum:        149.254.201.0 - 149.254.201.255

netname:        TMUK-Byte-ACS

descr:          T-Mobile(UK) Byte ACS LAN

country:        Gb

admin-c:        TMUK1-RIPE

tech-c:         TMUK1-RIPE

status:         ASSIGNED PA

mnt-by:         TMUK1-MNT

source:         RIPE # Filtered

This implies that there's something else in the RIM affecting the APN used for MMS - thoughts?

I have been puzzling over the MMS thing for quite a while. That means that the IP address you've highlighted is hardcoded somewhere in Paul's ROM, right? If so, I wonder if it would be possible for Paul to see which file it's in. 

[EDIT] Actually, thinking about it a bit more - I thought Paul's ROM had nothing to do with the T-Mobile ROM (ie, it was completely vanilla)?

Would verbose output get you any more detail?

By the way, does anyone know if ANY other network other than T-Mobile actually works for MMS on the Pulse??

Edited by le_lutin
Link to comment
Share on other sites

Guest zuccster

Yeah, it's trying to send via T-mob

14:53:40.702283 IP 10.113.61.79.54990 > 149.254.201.135.8080: Flags [P.], ack 1, win 2920, options [nop,nop,TS val 7132060 ecr 548983784], length 376

		0x0000:  4500 01ac 8782 4000 4006 0a84 0a71 3d4f  E.....@[email protected]=O

		0x0010:  95fe c987 d6ce 1f90 a0ea 54c6 e29d 3f27  ..........T...?'

		0x0020:  8018 0b68 8691 0000 0101 080a 006c d39c  ...h.........l..

		0x0030:  20b8 d3e8 504f 5354 2068 7474 703a 2f2f  ....POST.http://

		0x0040:  6d6d 7363 2e74 2d6d 6f62 696c 652e 636f  mmsc.t-mobile.co

		0x0050:  2e75 6b3a 3830 3032 2048 5454 502f 312e  .uk:8002.HTTP/1.

		0x0060:  310d 0a41 6363 6570 743a 202a 2f2a 2c20  1..Accept:.*/*,.

		0x0070:  6170 706c 6963 6174 696f 6e2f 766e 642e  application/vnd.

		0x0080:  7761 702e 6d6d 732d 6d65 7373 6167 652c  wap.mms-message,

		0x0090:  2061 7070 6c69 6361 7469 6f6e 2f76 6e64  .application/vnd

		0x00a0:  2e77 6170 2e73 6963 0d0a 782d 7761 702d  .wap.sic..x-wap-

		0x00b0:  7072 6f66 696c 653a 2068 7474 703a 2f2f  profile:.http://

		0x00c0:  7761 7031 2e68 7561 7765 692e 636f 6d2f  wap1.huawei.com/

		0x00d0:  7561 7072 6f66 2f48 7561 7765 6955 3832  uaprof/HuaweiU82

		0x00e0:  3330 7631 3030 4750 5253 2e78 6d6c 0d0a  30v100GPRS.xml..

		0x00f0:  4163 6365 7074 2d4c 616e 6775 6167 653a  Accept-Language:

		0x0100:  2065 6e2d 4652 2c20 656e 2d55 530d 0a43  .en-FR,.en-US..C

		0x0110:  6f6e 7465 6e74 2d4c 656e 6774 683a 2033  ontent-Length:.3

		0x0120:  3136 3132 0d0a 436f 6e74 656e 742d 5479  1612..Content-Ty

		0x0130:  7065 3a20 6170 706c 6963 6174 696f 6e2f  pe:.application/

		0x0140:  766e 642e 7761 702e 6d6d 732d 6d65 7373  vnd.wap.mms-mess

		0x0150:  6167 650d 0a48 6f73 743a 206d 6d73 632e  age..Host:.mmsc.

		0x0160:  742d 6d6f 6269 6c65 2e63 6f2e 756b 3a38  t-mobile.co.uk:8

		0x0170:  3030 320d 0a43 6f6e 6e65 6374 696f 6e3a  002..Connection:

		0x0180:  204b 6565 702d 416c 6976 650d 0a55 7365  .Keep-Alive..Use

		0x0190:  722d 4167 656e 743a 2041 6e64 726f 6964  r-Agent:.Android

		0x01a0:  2d4d 6d73 2f30 2e31 0d0a 0d0a			-Mms/0.1....

I'm a n00b to Android, does Paul build the ROMs from source or from butchered bits of other bins? Can we grep the source for the t-mobile hostnames?

Edited by zuccster
Link to comment
Share on other sites

Nice find zuccster, guess it's definitely something t-mob have done. Hopefully one of you smart people will solve the problem once and for all then :)

Great find there - I didnt think there was any credence to this "o2 MMS whitelist" suggestion !!

Well hopefully if it is simply an IP address in a config file somewhere we can replace / remove it ! :)

Link to comment
Share on other sites

Guest le_lutin
Great find there - I didnt think there was any credence to this "o2 MMS whitelist" suggestion !!

Well hopefully if it is simply an IP address in a config file somewhere we can replace / remove it ! :)

Right, might be talking out of my hat here, but is there a file called: 

data/data/com.android.providers.telephony/databases/telephony.db

on the phone?

Taken from here: 

http://forum.androidcentral.com/29942-post51.html

Useful?

http://209.85.229.132/search?q=cache:hIq00...mp;client=opera

Edited by le_lutin
Link to comment
Share on other sites

Guest zuccster

Bingo:

# grep -ri mobile ./

...

./system/etc/apns-conf.xml:  <apn carrier="T-Mobile UK" mcc="234" mnc="30" apn="general.t-mobile.uk" user="t-mobile" password="tm" server="*" mmsproxy="149.254.201.135" mmsport="8080" mmsc="http://mmsc.t-mobile.co.uk:8002"/>

...

There are a shedload of APNs in that file, that's where it's coming from. Unsure as to how the default is selected, any clues?

Link to comment
Share on other sites

Guest meinnit

zuccster you're a star! I was thinking of snooping the MMS packet but I didn't know where to start. Did you use ADB or run it directly on phone?

I think the ROM has a collection of APN's because I didn't have to enter my O2 APN settings when I installed the new ROM

Edited by meinnit
Link to comment
Share on other sites

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.