Ask a question
Search in Wireless Forums

Wireless Forum

Posted Sep 9, 2010
1:58:49 PM
View profile
New Thread for information re: MC Firmware updates
Edited by dellsweig on Sep 9, 2010 at 2:21:52 PM

All

 

Many of you have been following the MC threads for some time. Those that know me know that I have patiently tried to explain some of the issues and have been part of a select group of MC testers which are getting to do field testing on some of the various fixes to some of the MC issues. I have no idea how big this group is but I do know the Jitter fix and range fix have NOT been pushed out yer. They will be part of a fix that includes a couple more updates and will be pushed out once the ATT QA process is complete. Anyone that has worked in a software shop will understand the importance of a QA cycle.

 

I kind of stopped posting due to the noise level in the forums and some of the simply stupid posts.

 

I think the mis-information spread in this forum needs to be corrected - and as many have said - word from ATT would go a long way but absent that I will post an occasional update.

 

I have had two test pushes in the last month that have completly fixed he Jitter issue and have given me extended range on the Microcell presumably by increasing the transmit power of the uint.

 

I have been in continuous contact with the Microcell Engineering group at ATT Network Engineering for specific tests and follow ups.

 

Next week, the test group will receive a push that addresses the dropped calls many of us have seen.

Following that (no date given yet) will be a push that addresses the upload data cap and issues with MMS.

 

I was asked if I had upgraqded my Iphone to 4.1 yet so possibly there is some give and take here between apple and cisco/Att - I did not ask.

 

 

Finally - this is is for any of you that are lucky enough to be in the test group. I mentioned to the engineer that I am seeing about 3 to 4 Mb a day of data from the MC even when the phones are idle and associated with my WiFi. I was told this is diagnostic data and will show up on my bill. Because one of my phones is on a limited data plan, Engineering contacted the billing office and had a credit issued for the data usage. I suggest if you are in this test group to monitor this data usage.

 

Everyone else - once this test and QA cycle is complete and you get these fixes the Microcell works like a charm.

 

Hang in there

 

Also filing complaints with the FCC, FTC, etc, etc just will get you aggrevated. It wont get the problem fixed.

All

 

Many of you have been following the MC threads for some time. Those that know me know that I have patiently tried to explain some of the issues and have been part of a select group of MC testers which are getting to do field testing on some of the various fixes to some of the MC issues. I have no idea how big this group is but I do know the Jitter fix and range fix have NOT been pushed out yer. They will be part of a fix that includes a couple more updates and will be pushed out once the ATT QA process is complete. Anyone that has worked in a software shop will understand the importance of a QA cycle.

 

I kind of stopped posting due to the noise level in the forums and some of the simply stupid posts.

 

I think the mis-information spread in this forum needs to be corrected - and as many have said - word from ATT would go a long way but absent that I will post an occasional update.

 

I have had two test pushes in the last month that have completly fixed he Jitter issue and have given me extended range on the Microcell presumably by increasing the transmit power of the uint.

 

I have been in continuous contact with the Microcell Engineering group at ATT Network Engineering for specific tests and follow ups.

 

Next week, the test group will receive a push that addresses the dropped calls many of us have seen.

Following that (no date given yet) will be a push that addresses the upload data cap and issues with MMS.

 

I was asked if I had upgraqded my Iphone to 4.1 yet so possibly there is some give and take here between apple and cisco/Att - I did not ask.

 

 

Finally - this is is for any of you that are lucky enough to be in the test group. I mentioned to the engineer that I am seeing about 3 to 4 Mb a day of data from the MC even when the phones are idle and associated with my WiFi. I was told this is diagnostic data and will show up on my bill. Because one of my phones is on a limited data plan, Engineering contacted the billing office and had a credit issued for the data usage. I suggest if you are in this test group to monitor this data usage.

 

Everyone else - once this test and QA cycle is complete and you get these fixes the Microcell works like a charm.

 

Hang in there

 

Also filing complaints with the FCC, FTC, etc, etc just will get you aggrevated. It wont get the problem fixed.

Nothin left to do but smile smile smile :)

New Thread for information re: MC Firmware updates

[ Edited ]
24,194 views
66 replies
(0) Me too
(0) Me too
Reply
View all replies
(66)
0
(0)
  • Rate this reply
View profile
Oct 6, 2010 11:00:12 AM
0
(0)
Tutor

All I have to say is thank you for providing the information that you have.   Clearly AT&T has lost control of this situation from a QA standpoint.  We all just want to know that someone acknowledges that the problem is "real" and a "fix" is coming soon.  You have allayed both of those concerns.  In that, you are doing a service to us normal people out here.

 

The only thing that I would like you to take to Microcell engineering is the sincere suggestion that they allow us to turn off cellular data on the microcell.  Almost all of us have wifi also, and its just another thing that can go wrong that is unnecessary.  Why make the cellular radio do more than it has to?  Most of my problems go away when I turn it off on my iphone.  My two cents.

 

Also, please update us on the date of GA, and let us know after it has happened (since we can't see FW build no.)

 

Thanks for your help!

 

john

All I have to say is thank you for providing the information that you have.   Clearly AT&T has lost control of this situation from a QA standpoint.  We all just want to know that someone acknowledges that the problem is "real" and a "fix" is coming soon.  You have allayed both of those concerns.  In that, you are doing a service to us normal people out here.

 

The only thing that I would like you to take to Microcell engineering is the sincere suggestion that they allow us to turn off cellular data on the microcell.  Almost all of us have wifi also, and its just another thing that can go wrong that is unnecessary.  Why make the cellular radio do more than it has to?  Most of my problems go away when I turn it off on my iphone.  My two cents.

 

Also, please update us on the date of GA, and let us know after it has happened (since we can't see FW build no.)

 

Thanks for your help!

 

john

Re: New Thread for information re: MC Firmware updates

31 of 67 (4,995 Views)
0
(0)
  • Rate this reply
View profile
Oct 6, 2010 11:52:52 AM
0
(0)
Guru

 


jpbrewer wrote:

 

The only thing that I would like you to take to Microcell engineering is the sincere suggestion that they allow us to turn off cellular data on the microcell.  Almost all of us have wifi also, and its just another thing that can go wrong that is unnecessary.  Why make the cellular radio do more than it has to?  Most of my problems go away when I turn it off on my iphone.  My two cents.

 

 


 

Well, the problem with that is that turning off cellular data breaks a bunch of features on the phone (visual voicemail, MMS, location services, including find-my-iphone). So I would veto that suggestion, unless changes are made to allow those features to work over WiFi.

 

I'd actually rather that data through the microcell be unmeasured. It's much better to use 3G data than WiFi (modulo the difference in latency and bandwidth) in so far as you wind up getting a publicly reachable IP address and don't have any NAT or firewall issues. Believe it or not, I have an app on my phone (EchoLink) where this is an issue. If they got rid of the upload cap and allowed the data to be unmeasured, I'd probably actually use that instead of WiFi at home.

 


jpbrewer wrote:

 

The only thing that I would like you to take to Microcell engineering is the sincere suggestion that they allow us to turn off cellular data on the microcell.  Almost all of us have wifi also, and its just another thing that can go wrong that is unnecessary.  Why make the cellular radio do more than it has to?  Most of my problems go away when I turn it off on my iphone.  My two cents.

 

 


 

Well, the problem with that is that turning off cellular data breaks a bunch of features on the phone (visual voicemail, MMS, location services, including find-my-iphone). So I would veto that suggestion, unless changes are made to allow those features to work over WiFi.

 

I'd actually rather that data through the microcell be unmeasured. It's much better to use 3G data than WiFi (modulo the difference in latency and bandwidth) in so far as you wind up getting a publicly reachable IP address and don't have any NAT or firewall issues. Believe it or not, I have an app on my phone (EchoLink) where this is an issue. If they got rid of the upload cap and allowed the data to be unmeasured, I'd probably actually use that instead of WiFi at home.

Re: New Thread for information re: MC Firmware updates

32 of 67 (4,972 Views)
0
(0)
  • Rate this reply
View profile
Oct 6, 2010 2:05:57 PM
0
(0)
Guru

 


dellsweig wrote:

ATT is a huge beast and as we discussed, those familiar with the SDLC (Software Development Life Cycle) will understand the time it takes to make major changes to software..

 

 


 

Let's talk about the software development life cycle a bit. I'm a software engineer by trade. I write software for a living. I'm not perfect. I've written code that has bugs in it or that in some way didn't meet expectations. It happens.

 

WHEN it happens, the first thing that happens is that we determine the scope of the problem and determine how best to address it. Having done that, we come up with a plan to fix it. We then communicate that plan back to product management to make sure that the plan is going to address the needs of the customer. Product management keeps the customers informed, including when a fix is expected to be delivered, any potential work-arounds that might tide them over until then, and so on. Once the coding is done, a release-note is written documenting what the changes do. The documentation team gathers all of the change release notes into a release note document that is given to the customer to show what changed, why and what it means to them since the last release.

 

THAT'S the software development life cycle too. Not just writing and testing the code. The software development life cycle also touches the interactions with the customer.

 

Or, at least it's SUPPOSED to.

 

 


dellsweig wrote:

ATT is a huge beast and as we discussed, those familiar with the SDLC (Software Development Life Cycle) will understand the time it takes to make major changes to software..

 

 


 

Let's talk about the software development life cycle a bit. I'm a software engineer by trade. I write software for a living. I'm not perfect. I've written code that has bugs in it or that in some way didn't meet expectations. It happens.

 

WHEN it happens, the first thing that happens is that we determine the scope of the problem and determine how best to address it. Having done that, we come up with a plan to fix it. We then communicate that plan back to product management to make sure that the plan is going to address the needs of the customer. Product management keeps the customers informed, including when a fix is expected to be delivered, any potential work-arounds that might tide them over until then, and so on. Once the coding is done, a release-note is written documenting what the changes do. The documentation team gathers all of the change release notes into a release note document that is given to the customer to show what changed, why and what it means to them since the last release.

 

THAT'S the software development life cycle too. Not just writing and testing the code. The software development life cycle also touches the interactions with the customer.

 

Or, at least it's SUPPOSED to.

 

Re: New Thread for information re: MC Firmware updates

33 of 67 (4,931 Views)
0
(0)
  • Rate this reply
View profile
Oct 6, 2010 8:17:43 PM
0
(0)
Teacher

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!

Re: New Thread for information re: MC Firmware updates

34 of 67 (4,861 Views)
0
(0)
  • Rate this reply
View profile
Oct 7, 2010 5:35:36 AM
0
(0)
Scholar

kenchills wrote:

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!


I never had that issue and specific pushes to address that issue were not discussed by MC engineering. That said - there may be other testers involved in that...

 

Sorry....

 

 


kenchills wrote:

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!


I never had that issue and specific pushes to address that issue were not discussed by MC engineering. That said - there may be other testers involved in that...

 

Sorry....

 

 

Nothin left to do but smile smile smile :)

Re: New Thread for information re: MC Firmware updates

35 of 67 (4,799 Views)
Highlighted
0
(0)
  • Rate this reply
View profile
Oct 7, 2010 5:46:52 AM
0
(0)
Explorer
Edited by bongoherbert on Oct 7, 2010 at 5:49:09 AM

 


kenchills wrote:

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!


 

I'm not the addressee of your original query, I'll jump in anyway.

 

An observation- after the most recent push I received I've noticed that it takes an extra couple of seconds for the macro-cell network to hand-off to the mcell (or, alternately, longer for the mcell to take control from the macro-cell). Sort of like it's being 'really sure' you're nearby... 

 

This may or may not be related to your question directly, but seems to have some implicit connection.

 


kenchills wrote:

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!


 

I'm not the addressee of your original query, I'll jump in anyway.

 

An observation- after the most recent push I received I've noticed that it takes an extra couple of seconds for the macro-cell network to hand-off to the mcell (or, alternately, longer for the mcell to take control from the macro-cell). Sort of like it's being 'really sure' you're nearby... 

 

This may or may not be related to your question directly, but seems to have some implicit connection.

Re: New Thread for information re: MC Firmware updates

[ Edited ]
36 of 67 (4,796 Views)
0
(0)
  • Rate this reply
View profile
Oct 7, 2010 5:52:48 AM
0
(0)
Guru

bongoherbert wrote:

 


kenchills wrote:

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!


 

I'm not the addressee of your original query, I'll jump in anyway.

 

An observation- after the most recent push I received I've noticed that it takes an extra couple of seconds for the macro-cell network to hand-off to the mcell (or, alternately, longer for the mcell to take control from the macro-cell). Sort of like it's being 'really sure' you're nearby... 

 

This may or may not be related to your question directly, but seems to have some implicit connection.


Wait....are you saying that a call will now hand off from a macro-cell to a MicroCell?  That would be a huge improvement and would be the first I'm hearing of it.


bongoherbert wrote:

 


kenchills wrote:

dellsweig:

 

Just in case you don't catch this in the other thread,  does the upcoming firmware fix the problem where certain phones will not automatically connect with the m-cell?

 

Thanks!


 

I'm not the addressee of your original query, I'll jump in anyway.

 

An observation- after the most recent push I received I've noticed that it takes an extra couple of seconds for the macro-cell network to hand-off to the mcell (or, alternately, longer for the mcell to take control from the macro-cell). Sort of like it's being 'really sure' you're nearby... 

 

This may or may not be related to your question directly, but seems to have some implicit connection.


Wait....are you saying that a call will now hand off from a macro-cell to a MicroCell?  That would be a huge improvement and would be the first I'm hearing of it.

Re: New Thread for information re: MC Firmware updates

37 of 67 (4,791 Views)
0
(0)
  • Rate this reply
View profile
Oct 7, 2010 9:05:06 AM
0
(0)
Explorer

Not a -call- but the service per se. Sorry to get your hopes up... it would be nice. 

Not a -call- but the service per se. Sorry to get your hopes up... it would be nice. 

Re: New Thread for information re: MC Firmware updates

38 of 67 (4,753 Views)
0
(0)
  • Rate this reply
View profile
Nov 1, 2010 8:22:45 AM
0
(0)
Scholar
Edited by MyDogHasFleas on Nov 1, 2010 at 10:23:16 AM

Re: New Thread for information re: MC Firmware updates

[ Edited ]
39 of 67 (4,106 Views)
0
(0)
  • Rate this reply
View profile
Nov 21, 2010 4:31:44 PM
0
(0)
Contributor

Since you've been doing traffic analysis, can you confirm that the FAQ is wrong and that the microcell doesn't need to have incoming traffic forwarded to it (e.g. ports 443, 4500, ...)

Since you've been doing traffic analysis, can you confirm that the FAQ is wrong and that the microcell doesn't need to have incoming traffic forwarded to it (e.g. ports 443, 4500, ...)

Re: New Thread for information re: MC Firmware updates

40 of 67 (3,458 Views)
0
(0)
  • Rate this reply
View profile
Nov 22, 2010 8:04:40 AM
0
(0)
Scholar

Jay Levitt wrote:

Since you've been doing traffic analysis, can you confirm that the FAQ is wrong and that the microcell doesn't need to have incoming traffic forwarded to it (e.g. ports 443, 4500, ...)


I do not forward ANY ports and I have uPnP disabled on my router. My MC works perfectly.

 

The MC uses a secure tunnel which it establishes (outbound). There is no need for inbound port forwarding.

 

Here is a snapshot of the OUTBOUND communication - there is NO inbound unsolicited communication.

 

192.168.1.1312.230.208.129UDP_App*UDPEF1.34 MB
192.168.1.1312.230.208.129UDP_App*UDPDefault1.01 MB
192.168.1.1312.230.208.131https443TCPDefault120.76 KB
192.168.1.1312.230.208.195https443TCPDefault30.17 KB
192.168.1.1312.230.208.133ntp123UDPDefault7.98 KB
192.168.1.1312.230.209.133ntp123UDPDefault7.9 KB
192.168.1.1312.230.209.5ntp123UDPDefault7.9 KB
192.168.1.1312.230.208.48ntp123UDPDefault7.82 KB
192.168.1.13192.168.1.1domain53UDPDefault866.00 Bytes
192.168.1.1312.230.208.129UDP_App*UDPCS6416.00 Bytes

Jay Levitt wrote:

Since you've been doing traffic analysis, can you confirm that the FAQ is wrong and that the microcell doesn't need to have incoming traffic forwarded to it (e.g. ports 443, 4500, ...)


I do not forward ANY ports and I have uPnP disabled on my router. My MC works perfectly.

 

The MC uses a secure tunnel which it establishes (outbound). There is no need for inbound port forwarding.

 

Here is a snapshot of the OUTBOUND communication - there is NO inbound unsolicited communication.

 

192.168.1.1312.230.208.129UDP_App*UDPEF1.34 MB
192.168.1.1312.230.208.129UDP_App*UDPDefault1.01 MB
192.168.1.1312.230.208.131https443TCPDefault120.76 KB
192.168.1.1312.230.208.195https443TCPDefault30.17 KB
192.168.1.1312.230.208.133ntp123UDPDefault7.98 KB
192.168.1.1312.230.209.133ntp123UDPDefault7.9 KB
192.168.1.1312.230.209.5ntp123UDPDefault7.9 KB
192.168.1.1312.230.208.48ntp123UDPDefault7.82 KB
192.168.1.13192.168.1.1domain53UDPDefault866.00 Bytes
192.168.1.1312.230.208.129UDP_App*UDPCS6416.00 Bytes
Nothin left to do but smile smile smile :)

Re: New Thread for information re: MC Firmware updates

41 of 67 (2,001 Views)
0
(0)
  • Rate this reply
View profile
Nov 22, 2010 8:08:16 AM
0
(0)
Mentor

I've found the same thing.

 

Initially mine did not work.  I tried setting up Port Forwarding as suggested in the FAQ and it didn't help.  I enabled UDP Fragment Re-assembly, and that fixed the problem.  Later on, I disabled the Port Forwarding, and it continues to work.

I've found the same thing.

 

Initially mine did not work.  I tried setting up Port Forwarding as suggested in the FAQ and it didn't help.  I enabled UDP Fragment Re-assembly, and that fixed the problem.  Later on, I disabled the Port Forwarding, and it continues to work.

Re: New Thread for information re: MC Firmware updates

42 of 67 (1,998 Views)
0
(0)
  • Rate this reply
View profile
Nov 22, 2010 5:16:51 PM
0
(0)
Contributor

Thanks for the quick responses!  I had a feeling there was no inbound communication involved.

Thanks for the quick responses!  I had a feeling there was no inbound communication involved.

Re: New Thread for information re: MC Firmware updates

43 of 67 (1,938 Views)
0
(0)
  • Rate this reply
View profile
Dec 2, 2010 1:50:29 AM
0
(0)
Tutor
Edited by mtndrew1 on Dec 2, 2010 at 1:51:16 AM

I think I just got a series of updates. The microcell has been up and down starting at exactly 1am and now I'm getting 200 kbps+ upload through it on my iPhone speedtest app. Maybe they're fixing it? Fingers crossed!

I think I just got a series of updates. The microcell has been up and down starting at exactly 1am and now I'm getting 200 kbps+ upload through it on my iPhone speedtest app. Maybe they're fixing it? Fingers crossed!

Re: New Thread for information re: MC Firmware updates

[ Edited ]
44 of 67 (1,693 Views)
0
(0)
  • Rate this reply
View profile
Dec 3, 2010 2:18:23 PM
0
(0)
Scholar
Edited by AnClar on Dec 3, 2010 at 2:18:40 PM

Nothing new in my area (central TX).  Latest iPhone speedtest still shows only 50k upload.  You're certain you tried this with wifi off?

Nothing new in my area (central TX).  Latest iPhone speedtest still shows only 50k upload.  You're certain you tried this with wifi off?

Re: New Thread for information re: MC Firmware updates

[ Edited ]
45 of 67 (1,612 Views)
0
(0)
  • Rate this reply
View profile
Dec 3, 2010 2:25:32 PM
0
(0)
Guru

AnClar wrote:

Nothing new in my area (central TX).  Latest iPhone speedtest still shows only 50k upload.  You're certain you tried this with wifi off?


Ditto here.

 

I did see a solid 2 mb/s download, which is pretty decent.  But upstream....still right on dial-up speed...56 kb/s.


AnClar wrote:

Nothing new in my area (central TX).  Latest iPhone speedtest still shows only 50k upload.  You're certain you tried this with wifi off?


Ditto here.

 

I did see a solid 2 mb/s download, which is pretty decent.  But upstream....still right on dial-up speed...56 kb/s.

Re: New Thread for information re: MC Firmware updates

46 of 67 (1,606 Views)
0
(0)
  • Rate this reply
View profile
Dec 5, 2010 1:13:30 AM
0
(0)
Tutor
Yes, wifi is definitely off. 3G data is a completely different experience now. Several hours of phone calls since the update and all were crystal clear and jitter free. MMS messages go through quickly and reliably now in stark contrast to the prior experience.

A coworker with a microcell at home is experiencing the same thing. This is in downtown Los Angeles and the Hancock Park area.
Yes, wifi is definitely off. 3G data is a completely different experience now. Several hours of phone calls since the update and all were crystal clear and jitter free. MMS messages go through quickly and reliably now in stark contrast to the prior experience.

A coworker with a microcell at home is experiencing the same thing. This is in downtown Los Angeles and the Hancock Park area.

Re: New Thread for information re: MC Firmware updates

47 of 67 (1,525 Views)
0
(0)
  • Rate this reply
View profile
Dec 5, 2010 5:38:34 AM
0
(0)
Guru

That's encouraging and should offer some hope for others who have been having problems.

 

It'll be interesting to see if others in the L.A. area report the same results, and also to see if those improvements propagate around the country.

That's encouraging and should offer some hope for others who have been having problems.

 

It'll be interesting to see if others in the L.A. area report the same results, and also to see if those improvements propagate around the country.

Re: New Thread for information re: MC Firmware updates

48 of 67 (1,500 Views)
0
(0)
  • Rate this reply
View profile
Dec 5, 2010 5:52:26 PM
0
(0)
Guru
Edited by nsayer on Dec 5, 2010 at 6:48:39 PM

I de- and re-registered, and the uplink is still capped. It did look like it did some sort of firmware download while it came back up (the flickery 3G light followed by a reboot), but it's not behaving any differently. This is in the Bay Area.

I de- and re-registered, and the uplink is still capped. It did look like it did some sort of firmware download while it came back up (the flickery 3G light followed by a reboot), but it's not behaving any differently. This is in the Bay Area.

Re: New Thread for information re: MC Firmware updates

[ Edited ]
49 of 67 (1,459 Views)
0
(0)
  • Rate this reply
View profile
Dec 5, 2010 6:50:12 PM
0
(0)
Guru

nsayer wrote:

I de- and re-registered, and the uplink is still capped. It did look like it did some sort of firmware download while it came back up (the flickery 3G light followed by a reboot), but it's not behaving any differently. This is in the Bay Area.


It's next Thanksgiving it's coming to your house.Smiley Very Happy

 


nsayer wrote:

I de- and re-registered, and the uplink is still capped. It did look like it did some sort of firmware download while it came back up (the flickery 3G light followed by a reboot), but it's not behaving any differently. This is in the Bay Area.


It's next Thanksgiving it's coming to your house.Smiley Very Happy

 

Re: New Thread for information re: MC Firmware updates

50 of 67 (1,448 Views)
0
(0)
  • Rate this reply
View profile
Dec 5, 2010 6:55:48 PM
0
(0)
Teacher
My upload is still capped at 47kbps. My dowload through the Microcell is so crappy that the speedtest.net app usually won't even run the test fully. It gets stuck halfway through the download. Half of the time it won't even get through testing the ping.
MMS's usually won't send at all.
My upload is still capped at 47kbps. My dowload through the Microcell is so crappy that the speedtest.net app usually won't even run the test fully. It gets stuck halfway through the download. Half of the time it won't even get through testing the ping.
MMS's usually won't send at all.

Re: New Thread for information re: MC Firmware updates

51 of 67 (1,962 Views)
0
(0)
  • Rate this reply
View profile
Dec 5, 2010 10:20:34 PM
0
(0)
Scholar
No changes in Reno. Still getting > 500ms ping times, ~1000K download and 56K upload. Maybe firmware updates are being rolled out by region?
No changes in Reno. Still getting > 500ms ping times, ~1000K download and 56K upload. Maybe firmware updates are being rolled out by region?

Re: New Thread for information re: MC Firmware updates

52 of 67 (1,944 Views)
0
(0)
  • Rate this reply
View profile
Dec 6, 2010 1:46:37 PM
0
(0)
Scholar
Edited by AnClar on Dec 6, 2010 at 1:49:32 PM

Wireless_Guru wrote:
No changes in Reno. Still getting > 500ms ping times, ~1000K download and 56K upload. Maybe firmware updates are being rolled out by region?

At the risk of beating a VERY dead horse, the fact that we have to sit here and speculate about whether there will be, have been, or are ever going to be, any firmware updates to address the issues we've all been experiencing with the MCell is just plain sad and inexcusable on AT&T's part.  There are reasons why AT&T has just been rated the worst wireless provider in the United States by Consumer Reports...this is just one of them.


Wireless_Guru wrote:
No changes in Reno. Still getting > 500ms ping times, ~1000K download and 56K upload. Maybe firmware updates are being rolled out by region?

At the risk of beating a VERY dead horse, the fact that we have to sit here and speculate about whether there will be, have been, or are ever going to be, any firmware updates to address the issues we've all been experiencing with the MCell is just plain sad and inexcusable on AT&T's part.  There are reasons why AT&T has just been rated the worst wireless provider in the United States by Consumer Reports...this is just one of them.

Re: New Thread for information re: MC Firmware updates

[ Edited ]
53 of 67 (1,889 Views)
0
(0)
  • Rate this reply
View profile
Dec 7, 2010 4:06:31 AM
0
(0)
Scholar

AnClar wrote:

Wireless_Guru wrote:
No changes in Reno. Still getting > 500ms ping times, ~1000K download and 56K upload. Maybe firmware updates are being rolled out by region?

At the risk of beating a VERY dead horse, the fact that we have to sit here and speculate about whether there will be, have been, or are ever going to be, any firmware updates to address the issues we've all been experiencing with the MCell is just plain sad and inexcusable on AT&T's part.  There are reasons why AT&T has just been rated the worst wireless provider in the United States by Consumer Reports...this is just one of them.


To add to that....

 

Having been in the firmware test group and having my MC work PERFECTLY since getting the firmware, it is sad that ATT cannot make this device work equally well across the supported footprint. For whatever reasons - geopgraphic, infrastructure, whatever. Aparently many have gotten the fix delivered to their MC.

 

As a note - My upload never changed from the 56k BUT MMS works very well. It also appears that when multiple devices are connected, each gets 56k and each has no issue with MMS. The only place this cap could possibly be an issue is when the control channel is used heavily -  as in txt or mms. For any other upload - like web browsing, the WiFi connection (if present) is used.


AnClar wrote:

Wireless_Guru wrote:
No changes in Reno. Still getting > 500ms ping times, ~1000K download and 56K upload. Maybe firmware updates are being rolled out by region?

At the risk of beating a VERY dead horse, the fact that we have to sit here and speculate about whether there will be, have been, or are ever going to be, any firmware updates to address the issues we've all been experiencing with the MCell is just plain sad and inexcusable on AT&T's part.  There are reasons why AT&T has just been rated the worst wireless provider in the United States by Consumer Reports...this is just one of them.


To add to that....

 

Having been in the firmware test group and having my MC work PERFECTLY since getting the firmware, it is sad that ATT cannot make this device work equally well across the supported footprint. For whatever reasons - geopgraphic, infrastructure, whatever. Aparently many have gotten the fix delivered to their MC.

 

As a note - My upload never changed from the 56k BUT MMS works very well. It also appears that when multiple devices are connected, each gets 56k and each has no issue with MMS. The only place this cap could possibly be an issue is when the control channel is used heavily -  as in txt or mms. For any other upload - like web browsing, the WiFi connection (if present) is used.

Nothin left to do but smile smile smile :)

Re: New Thread for information re: MC Firmware updates

54 of 67 (1,829 Views)
0
(0)
  • Rate this reply
View profile
Dec 7, 2010 1:13:33 PM
0
(0)
Tutor

Unless I missed this somewhere (entirely possible as it's a rather long thread), is there a date when these (or any) fixes will be pushed out to the community in general for this issue?  If not, how do I join the test group?  I would be more than happy to participate before my 30 day return window closes on this product.  I'd rather keep my MCell as signal in my area is horrible but not if it's problematic (etc).

 

thanks,

 

John

Unless I missed this somewhere (entirely possible as it's a rather long thread), is there a date when these (or any) fixes will be pushed out to the community in general for this issue?  If not, how do I join the test group?  I would be more than happy to participate before my 30 day return window closes on this product.  I'd rather keep my MCell as signal in my area is horrible but not if it's problematic (etc).

 

thanks,

 

John

Re: New Thread for information re: MC Firmware updates

55 of 67 (1,751 Views)
0
(0)
  • Rate this reply
View profile
Dec 7, 2010 3:27:58 PM
0
(0)
Explorer

I have the update and it definitely improves the voice quality.  I never have "skipping" anymore and the signal seems to be a little stronger.  I do frequently have dropped calls despite having a four or five bar signal.  Hopefully that will be fixed soon too.

I have the update and it definitely improves the voice quality.  I never have "skipping" anymore and the signal seems to be a little stronger.  I do frequently have dropped calls despite having a four or five bar signal.  Hopefully that will be fixed soon too.

Re: New Thread for information re: MC Firmware updates

56 of 67 (1,737 Views)
0
(0)
  • Rate this reply
View profile
Dec 8, 2010 5:21:17 AM
0
(0)
Teacher

I have the same problem...I have no idea what firmware I have but I usually have to attempt making a call 3-5 times when on my Mcell and it immediately says Call Failed it's extremely frustrating on top of the fact that like most others the speeds are extremely slow no matter what speed connection you have from your broadband provider along with 500+ms ping time makes for a very slow MMS send or receive. I use wifi for everything that I can but somethings just can't be done on wifi.

I have the same problem...I have no idea what firmware I have but I usually have to attempt making a call 3-5 times when on my Mcell and it immediately says Call Failed it's extremely frustrating on top of the fact that like most others the speeds are extremely slow no matter what speed connection you have from your broadband provider along with 500+ms ping time makes for a very slow MMS send or receive. I use wifi for everything that I can but somethings just can't be done on wifi.

Re: New Thread for information re: MC Firmware updates

57 of 67 (1,689 Views)
0
(0)
  • Rate this reply
View profile
Dec 8, 2010 7:05:42 AM
0
(0)
Scholar
Dellsweig,

Can you please ask your sources if there's any way to tell when the latest fix has been sent to the MicroCell. Noticeably improved ping times? Increased download speed? I get around 1Mbps on the MC, 2-3Mbps on the macro network, and 5Mbps on my Wi-fi network. Anything end users can test?
Dellsweig,

Can you please ask your sources if there's any way to tell when the latest fix has been sent to the MicroCell. Noticeably improved ping times? Increased download speed? I get around 1Mbps on the MC, 2-3Mbps on the macro network, and 5Mbps on my Wi-fi network. Anything end users can test?

Re: New Thread for information re: MC Firmware updates

58 of 67 (1,673 Views)
0
(0)
  • Rate this reply
View profile
Dec 8, 2010 8:08:23 AM
0
(0)
Scholar

Wireless_Guru wrote:
Dellsweig,

Can you please ask your sources if there's any way to tell when the latest fix has been sent to the MicroCell. Noticeably improved ping times? Increased download speed? I get around 1Mbps on the MC, 2-3Mbps on the macro network, and 5Mbps on my Wi-fi network. Anything end users can test?

The last I spoke with anyone from Microcell Engineering (in Atlanta) was back in the beginning of November - a wrap up call.

 

With the exception of the WiFi (I do way better then 5Mbps) the numbers you are seeing is the same as I am getting.

 

My range is very good - this morning sitting in my car outside the garage - I was still connected to the MC with 4 bars - 3 inside walls and insulated outside walls between me and the MC. I have no jitter and no issues sending or receiving MMS.

 

From what I see on the boards - many folks have gotten this update and are quite happy. It seems some have not - I dont know what to tell them.....

 

 


Wireless_Guru wrote:
Dellsweig,

Can you please ask your sources if there's any way to tell when the latest fix has been sent to the MicroCell. Noticeably improved ping times? Increased download speed? I get around 1Mbps on the MC, 2-3Mbps on the macro network, and 5Mbps on my Wi-fi network. Anything end users can test?

The last I spoke with anyone from Microcell Engineering (in Atlanta) was back in the beginning of November - a wrap up call.

 

With the exception of the WiFi (I do way better then 5Mbps) the numbers you are seeing is the same as I am getting.

 

My range is very good - this morning sitting in my car outside the garage - I was still connected to the MC with 4 bars - 3 inside walls and insulated outside walls between me and the MC. I have no jitter and no issues sending or receiving MMS.

 

From what I see on the boards - many folks have gotten this update and are quite happy. It seems some have not - I dont know what to tell them.....

 

 

Nothin left to do but smile smile smile :)

Re: New Thread for information re: MC Firmware updates

59 of 67 (1,664 Views)
0
(0)
  • Rate this reply
View profile
Dec 8, 2010 10:58:16 AM
0
(0)
Contributor

is there a way to fine out what firmware the MC is running? and is there an alert when there is a new firmware available?? Also I have no issues with making or receiving a call while on the MC but the data is so bad its like having no data at all. Just like other users i use my WIFI for everything on my phone bu as far as sending n receiving MMS it either takes too long or i never get them or they never send.

is there a way to fine out what firmware the MC is running? and is there an alert when there is a new firmware available?? Also I have no issues with making or receiving a call while on the MC but the data is so bad its like having no data at all. Just like other users i use my WIFI for everything on my phone bu as far as sending n receiving MMS it either takes too long or i never get them or they never send.

Re: New Thread for information re: MC Firmware updates

60 of 67 (1,615 Views)
Advanced
You must be signed in to add attachments
Share this post
Share this post