Mic problems with OS 7.1 - straight versions or hybrids

**newcollector** · 06-27-2012, 06:21 AM

1) What carrier are you on...AT&T
2) What OS you are running/tried...402, .428
3) Whether you are/are not having problems...No problem
4) What city/region you are in...Louisville and Bowling Green, KY...Denver, CO

**kraski** · 06-27-2012, 06:34 AM

Originally Posted by tsells

My post # 35 in this thread has been updated with Wisconsin as an area with the mic problem. Phoenix was already listed, so your report gives more credibility to the "location theory"!
Something tells me that with less and less support by AT&T for the Blackberry platform, AT&T users are going to be stuck with .391 for a while (or forever), as there are reports in the 9900 thread about regional mic issues for AT&T users on .523.

I'm in one of those ultra-hectic periods of the year. So, having just noticed this thread, I'm not going to read all the way through to find out if my area has been already mentioned. Baltimore, MD is a definite locale for .402 and .428 mic issues. 7.1.0.378 seems to be a good build, including decent battery life.

**Kimberly Boals** · 06-28-2012, 11:47 PM

AT&T in Boise, Idaho. Have tried all OS versions except .523. Had mic issues on .402 and .428 but not .437. Currently running .318.

**go1ndr** · 06-29-2012, 02:20 PM

Originally Posted by Mecca EL

I pray that your prediction doesn't come to pass. What is even more mindboggling is the fact that AT&T are the sole service providers of the Dev Alpha devices

Hey Mecca! Hope you are doing well. I have a question for you. This may not be the best forum for this but just curious. Assuming there are no mic problems, what is the advantages of your newest hybrids over say the .378 I'm currently running? I was just asked this by another blackberry owner and when I started to tell him, I realized I didn't really know. I said maybe a little faster browsing, but other than that I wasn't sure. Thanks! Go1ndr (Jack)

**tsells** · 06-29-2012, 07:46 PM

Thought I'd move this list to the end of this thread:

There were no mic problems reported from anyone in Texas, So. California, Chicago, Louisville, Miami, and Raleigh (NC).

Baltimore, Boise, Denver, Detroit, Eugene (OR), So. New Jersey, NY, Central PA, Philly, Phoenix, Portland, Seattle, St. Louis, Wilmington (DE), Washington DC, and Wisconsin all noted mic problems.

We'd all appreciate any posts from user locations of .4XX builds using AT&T with or without a mic problem, so I can add to this list.

**jackie879** · 07-04-2012, 01:31 PM

1) What carrier are you on? AT&T
2) What OS you are running/tried? .428, .391
3) Whether you are/are not having problems Yes, muted mic with .428. .Mic works fine on .391
4) What city/region you are in? St. Louis, MO

**tsells** · 07-04-2012, 01:54 PM

Originally Posted by jackie879

1) What carrier are you on? AT&T
2) What OS you are running/tried? .428, .391
3) Whether you are/are not having problems Yes, muted mic with .428. .Mic works fine on .391
4) What city/region you are in? St. Louis, MO

Thanks. It's been added to the list above.

**Mecca EL** · 07-04-2012, 03:39 PM

1) What carrier are you on? AT&T
2) What OS you are running/tried? Delta Prime - uses .428's sfi
3) Whether you are/are not having problems? No, mic works fine
4) What city/region you are in? Raleigh NC and surrounding areas. Have not experienced muted mic error within a 90 mile radius.

**Don_Henry** · 07-04-2012, 03:48 PM

Originally Posted by tsells

Thanks. It's been added to the list above.

And a BBM buddy of mine has a 9900 - lives in St. Louis - severe mic problems - went back to a .3XX OS

**iHacker132** · 07-04-2012, 10:20 PM

Normally I don't post but seeing everybody saying that its AT&T I would like to say that I'm using another provider and still having the mic problems I'm not even in the states but I do have an AT&T branded phone

1) What carrier are you on? Digicel Curacao
2) What OS you are running/tried? Leaked, Official
3) Whether you are/are not having problems Yes, muted mic with 402
4) What city/region you are in?Curacao-Netherlands Atilles

**bassoprofundo** · 07-04-2012, 11:12 PM

1) What carrier are you on? AT&T
2) What OS you are running/tried? Had .391 and have used several .4xx builds. Currently on .467
3) Whether you are/are not having problems? No, mic works fine
4) What city/region you are in? St. Louis. I work downtown and live about 25 miles north in IL.

The .4xx builds I've used have all come from AT&T and have been shrunk with BBHTool. I wonder if there's something in the radio for these builds causing me not to have issues where others do on leaked or non-ATT builds? My radio version shows:
"Cellular Radio Version: 5.0.2.1.1, SV 3-7"

**tsells** · 07-05-2012, 05:49 AM

Originally Posted by bassoprofundo

1) What carrier are you on? AT&T
2) What OS you are running/tried? Had .391 and have used several .4xx builds. Currently on .467
3) Whether you are/are not having problems? No, mic works fine
4) What city/region you are in? St. Louis. I work downtown and live about 25 miles north in IL.

The .4xx builds I've used have all come from AT&T and have been shrunk with BBHTool. I wonder if there's something in the radio for these builds causing me not to have issues where others do on leaked or non-ATT builds? My radio version shows:
"Cellular Radio Version: 5.0.2.1.1, SV 3-7"

Never seen .467. Are you sure that is the OS #? When you go to "about" what does the 3rd line say? It has the OS # in (v7.1.0.XXX).

**cerealberry** · 07-05-2012, 07:35 PM

HELP!!
) What carrier are you on; att
2) What OS you are running/tried .536
3) Whether you are/are not having problems upgraded yesterday and now I can't hear anyone when they call and they can't hear me!!!
4) What city/region you are in? chicago

**Don_Henry** · 07-05-2012, 08:06 PM

Originally Posted by bassoprofundo

1) What carrier are you on? AT&T
2) What OS you are running/tried? Had .391 and have used several .4xx builds. Currently on .467
3) Whether you are/are not having problems? No, mic works fine
4) What city/region you are in? St. Louis. I work downtown and live about 25 miles north in IL.

The .4xx builds I've used have all come from AT&T and have been shrunk with BBHTool. I wonder if there's something in the radio for these builds causing me not to have issues where others do on leaked or non-ATT builds? My radio version shows:
"Cellular Radio Version: 5.0.2.1.1, SV 3-7"

Appreciate you posting - but you have said all the .4XX builds you've used came from AT&T - AT&T has never released a 7.1 OS - so if all your OSs came from AT&T, they can not be 7.1 - would have to be 7.0 - yet you have listed .391 and several .4XX builds.

Can you clarify if you are indeed running 7.0 or 7.1 series - because St.Louis IS identified as a "mic problem" area - so if you are truly running 7.1 in St. Louis with no mic problems, this is significant news.

Please clarify - and thanks again for posting.

**Don_Henry** · 07-05-2012, 09:48 PM

Time to move the list of good and bad cities to the bottom of the thread again:

There were no mic problems reported from anyone in Texas, So. California, Chicago, Louisville, Miami, and Raleigh (NC). NOTE: There has now been a report of mic problems in Chicago with .536

Baltimore, Boise, Denver, Detroit, Eugene (OR), So. New Jersey, NY, Central PA, Philly, Phoenix, Portland, Seattle, St. Louis, Wilmington (DE), Washington DC, and Wisconsin all noted mic problems.

**Don_Henry** · 07-05-2012, 09:52 PM

Originally Posted by cerealberry

HELP!!
) What carrier are you on; att
2) What OS you are running/tried .536
3) Whether you are/are not having problems upgraded yesterday and now I can't hear anyone when they call and they can't hear me!!!
4) What city/region you are in? chicago

Cerealberry,

Thanks for posting - you are the first report of a problem in Chicago (previously believed to be a "good' city). Also noted that your problem was bi-directional - the mic problems so far have been that the BB user can not be heard, but the BB user could hear the other party.

Have you used any other .4XX OSs prior to installing .536? Did you have any mic problems with those?

Thanks again for posting!

**bassoprofundo** · 07-06-2012, 07:46 PM

Originally Posted by tsells

Never seen .467. Are you sure that is the OS #? When you go to "about" what does the 3rd line say? It has the OS # in (v7.1.0.XXX).

It's definitely .467, which hasn't been released by AT&T but is in testing. I have access to unreleased builds submitted by RIM for carrier testing.

. Good news is that it might fix issues should they ever actually release it!

Sent from my Lumia 900 using Board Express

**bassoprofundo** · 07-06-2012, 07:49 PM

Originally Posted by Don_Henry

Appreciate you posting - but you have said all the .4XX builds you've used came from AT&T - AT&T has never released a 7.1 OS - so if all your OSs came from AT&T, they can not be 7.1 - would have to be 7.0 - yet you have listed .391 and several .4XX builds.

Can you clarify if you are indeed running 7.0 or 7.1 series - because St.Louis IS identified as a "mic problem" area - so if you are truly running 7.1 in St. Louis with no mic problems, this is significant news.

Please clarify - and thanks again for posting.

It's definitely 7.1.0.467 as noted above. They just haven't actually released any of the 7.1.x builds yet via official channels.

Sent from my Lumia 900 using Board Express

**tsells** · 07-06-2012, 08:08 PM

Originally Posted by bassoprofundo

It's definitely .467, which hasn't been released by AT&T but is in testing. I have access to unreleased builds submitted by RIM for carrier testing.

. Good news is that it might fix issues should they ever actually release it!

Sent from my Lumia 900 using Board Express

I'm not trying to be rude, but you say you have access to unreleased OS's and you're also using a Lumia 900 .

I've installed plenty of the leaked OS's that were not official ATT releases, but .467 has never been posted by anyone.
How about posting a screenshot of your "about" screen showing .467? Many AT&T users have mic issues (based on their location) on any of the .4XX and now the .5XX builds, so you have "breaking news" if AT&T is testing .467.

FYI, here's my current "about" page (and it's not an AT&T release):

**bassoprofundo** · 07-06-2012, 08:13 PM

I have a Lumia 900 for a personal phone and a 9810 for a corporate phone. As I'm not on the clock and wearing shorts that don't comfortably accommodate 2 phones, I just have my personal one. That makes a screenshot a bit tough

I understand the skepticism, but builds come through all the time with version #s I never see on CB.

**tsells** · 07-06-2012, 08:23 PM

Originally Posted by bassoprofundo

I have a Lumia 900 for a personal phone and a 9810 for a corporate phone. As I'm not on the clock and wearing shorts that don't comfortably accommodate 2 phones, I just have my personal one. That makes a screenshot a bit tough

I understand the skepticism, but builds come through all the time with version #s I never see on CB.

You have access to internal RIM builds, but you can't take a screenshot because you're wearing shorts.

But keep us posted if you can find this mysterious 9810 with this mysterious 7.1.0.467 that no one in the entire CB community has but you!!!

**tsells** · 07-06-2012, 09:21 PM

Sorry for the rants above, but felt we had to clean up the thread from misinformation.

So as Don Henry said above:

Time to move the list of good and bad cities to the bottom of the thread again:

There were no mic problems reported from anyone in Texas, So. California, Chicago, Louisville, Miami, and Raleigh (NC).

Baltimore, Boise, Denver, Detroit, Eugene (OR), New Jersey, NY, Central PA, Philly, Phoenix, Portland, Seattle, St. Louis, Wilmington (DE), Washington DC, and Wisconsin all noted mic problems.

**cerealberry** · 07-06-2012, 09:23 PM

Originally Posted by Don_Henry

Cerealberry,

Thanks for posting - you are the first report of a problem in Chicago (previously believed to be a "good' city). Also noted that your problem was bi-directional - the mic problems so far have been that the BB user can not be heard, but the BB user could hear the other party.

Have you used any other .4XX OSs prior to installing .536? Did you have any mic problems with those?

Thanks again for posting!

I did have the .4xx (I forgot which one) and had no problems... After several battery pulls I got the phone to work. It was the oddest thing... I've never experienced that issue before.