[tsells]

Ok, I'll blow your "regional thing" theory out of the water.

I'm on AT&T, Tacoma, Washington. Tried .4xx and had mic problems. Went back to .391 and everything is fine now.

The theory is still alive as the .3xx builds have no mic issues at all, but the .4xx builds have the mic problems for some ATT users.
We are still looking for anyone to disprove the theory by posting different results than someone else that has already posted using .402 or .428 in that particular region.

[go1ndr]

Tsells, I agree the .3xx have no apparent issues. I was in the desert (almost to the AZ state line/live in So CA) and zero issues with .378 over there. I'm very happy with .378but don't see as many happy posters with .378 as .391 though no negatives on either. Can one of you tell me what the main differences are between them, and if it's worth moving from .378 to .391? Many thanks!

[tsells]

Tsells, I agree the .3xx have no apparent issues. I was in the desert (almost to the AZ state line/live in So CA) and zero issues with .378 over there. I'm very happy with .378but don't see as many happy posters with .378 as .391 though no negatives on either. Can one of you tell me what the main differences are between them, and if it's worth moving from .378 to .391? Many thanks!

There's not much difference with most of the .3XX builds. If I remember correctly, the radio might be the only difference that I saw. If you have no issues on .378 then there probably is no reason to go to .391. But if you are having dropped calls or any other glitch then .391 works real well.

[go1ndr]

Cool! Thanks Tsells! I actually have no issues with dropped calls that I would blame on the OS. Occasional drops when going through another carrier's cell site area (Verizon in particular) would be the only issue. I actually live in/near a Verizon site and ATT coverage is not great at our house. I got my hands on an AT&T MicroCell and hooked it up in the house, which improved the coverage 1000%--but once out of that area, the AT&T reception is good. Is the .391 a leak or an official OS? Just curious--I know there is no difference. Not sure if .391 has the "open" hotspot either--though I've never used it yet. Thanks again! "Go"

[Don_Henry]

Ok, I'll blow your "regional thing" theory out of the water.

I'm on AT&T, Tacoma, Washington. Tried .4xx and had mic problems. Went back to .391 and everything is fine now.

Thanks for posting - but with all due respect, I believe you did not understand the point of the "regional thing" . . it appears that there are NO MIC PROBLEMS with .4XX in some regions, but there ARE MIC PROBLEMS with .4XX in other regions. Seems like you are in a region that DOES HAVE MIC PROBLEMS with .4XX.

Some users have NO MIC PROBLEMS with .4XX - others, such as yourself, DO HAVE MIC PROBLEMS.

In my case - NO MIC PROBLEMS with .4XX in my home region (So California) but when I traveled to Phoenix, SEVERE MIC PROBLEMS. When I returned home, NO MIC PROBLEMS.

So - this would seem to validate that .4XX has no issues in certain regions, but not other regions.

[peteygrizz]

Ok so after taking a small trip yesterday I am going to confirm that this in fact a regional or tower to tower issue with AT$T. I originally suspected this might be the case when .402 initially hit and my mic did not work at my home, but worked when driving just a few miles down the road, then went out when returning home.

Yesterday I went from My home in South Jersey to Central Jersey and made several calls during which I could be heard everywhere except at my house, with full H+ service, then traveled down to Baltimore, MD making calls along the way and hit a dead spot around Wilmington, DE where my mic dropped out during a call, despite retaining full coverage.

The issue did not surface in any other areas for me. Annoying, but at least I know. This issue has remained constant through .402, .428 in both straight and hybrid versions as well as the unreleased hybrid of .428/.523 I am currently testing.

[tsells]

I've been following the 9900 thread with the. 5xx build and they continue to have some AT&T mic issues. The regional theory seems to have some credibility.
Here's what I've been able to find by combining results in both threads:

There were no mic problems reported from anyone in Texas, So. California, Louisville, and Chicago.
But Baltimore, Boise, Denver, Detroit, So. New Jersey, NY, Central PA, Philly, Phoenix, Portland, Seattle, Wilmington (DE), Washington DC, and Wisconsin all noted mic problems.

[nsane1]

I think I can help this week. Running .5XX, no mic problems in TX, am traveling to DC and NY this week, will make test calls in each location and report in.

[Mecca EL]

Great info in here. I've pulled up AT&T's regional coverage map - it's interactive, so I've provided a link: http://www.wireless.att.com/coverage...88671875&sci=4
If you feel like it, can those participating zoom into your home city and provide info on whether you're in a Best, Good, Moderate, etc region?

This currently speaks volumes about carrier testing of OS's. In all appearances, the foreign market must be working wonders for RIM, because the majority of the "official" OS releases have been from overseas. The local market, in comparison, has all but abandoned device support. It would stand to reason that the 3xx series of OS may have been the last of the local markets test platform.

Tsells "guinea pig" statement spoke volumes to me, because if AT&T is saying "we're only going to support BB10 devices..." and leave the rest of us hanging, with our findings holding some strong validity...I'd be pissed. If it's a lack of tower support, on the other hand, then waiting for "4G" to spread will alleviate the matter - but why do we have to wait that long?

I've experienced the muting mic issue even on 2xx and 3xx series OS, but since I'm a tinkerer, I just wrote it off. I still do. But I don't mind reporting these findings to some higher ups at AT&T. Will they care...no. But if we jump ship to another carrier, with stronger coverage - even the thought of doing that - may move them to make adjustments. Hitting their pockets brings attention.

[tsells]

Great info in here. I've pulled up AT&T's regional coverage map - it's interactive, so I've provided a link: AT&T Coverage Viewer
If you feel like it, can those participating zoom into your home city and provide info on whether you're in a Best, Good, Moderate, etc region?

This currently speaks volumes about carrier testing of OS's. In all appearances, the foreign market must be working wonders for RIM, because the majority of the "official" OS releases have been from overseas. The local market, in comparison, has all but abandoned device support. It would stand to reason that the 3xx series of OS may have been the last of the local markets test platform.

Tsells "guinea pig" statement spoke volumes to me, because if AT&T is saying "we're only going to support BB10 devices..." and leave the rest of us hanging, with our findings holding some strong validity...I'd be pissed. If it's a lack of tower support, on the other hand, then waiting for "4G" to spread will alleviate the matter - but why do we have to wait that long?

I've experienced the muting mic issue even on 2xx and 3xx series OS, but since I'm a tinkerer, I just wrote it off. I still do. But I don't mind reporting these findings to some higher ups at AT&T. Will they care...no. But if we jump ship to another carrier, with stronger coverage - even the thought of doing that - may move them to make adjustments. Hitting their pockets brings attention.

Mecca,
Sounds like it's time to make a new hybrid with the radio files from .391 and everything else from the .4xx and .5xx builds!
(If that's even possible. )

PS: I reside in a "best" region and have had no mic problems at home on any OS. But I often travel to other regions that have reported problems.

[BBNewB5]

I've checked the ATT coverage map whose link Mecca provided (and checked a few others today as a result of an unrelated issue). I'm in "best" for voice and 4G/LTE (dark blue) for data. I also know of a tower 2.5 miles or so away from my house. This info doesn't surprise me as I've had no issues-although prior to installing Gamma, my radio coverage fluctuated a LOT-however, with Gamma I get steady bars of coverage and no mic issues.
However, I like tsells' suggestion, as well.

[Mecca EL]

Mecca,
Sounds like it's time to make a new hybrid with the radio files from .391 and everything else from the .4xx and .5xx builds!
(If that's even possible. )

PS: I reside in a "best" region and have had no mic problems at home on any OS. But I often travel to other regions that have reported problems.

I've checked the ATT coverage map whose link Mecca provided (and checked a few others today as a result of an unrelated issue). I'm in "best" for voice and 4G/LTE (dark blue) for data. I also know of a tower 2.5 miles or so away from my house. This info doesn't surprise me as I've had no issues-although prior to installing Gamma, my radio coverage fluctuated a LOT-however, with Gamma I get steady bars of coverage and no mic issues.
However, I like tsells' suggestion, as well.

I'll make an attempt. .391 may be too far out of series to work efficiently with the 4xx and 5xx java. I actually started Gamma with .391's sfi.

Thanks for the area info. I'm betting those in the "Good" and lesser zones will confirm whats suspected. My area went full "4G" about 3 months ago, which alleviated the muted mic issues for me. BUT, because the local carriers haven't adopted 4xx and 5xx, these OS might be too advanced, program-wise, to communicate effectively. AND, with "H+" rearing it's head again, it's safe to assume it isn't just a matter of a theme tweak, why we're seeing that symbol again.

[sedalia066]

According to the ATT coverage map my family resides in a very high level coverage area. We get several bars of H+ at home. Yet every .4xx OS so far had mic issues on my 9810. .391 is holding steady and working well so far.

[Don_Henry]

Great info in here. I've pulled up AT&T's regional coverage map - it's interactive, so I've provided a link: AT&T Coverage Viewer
If you feel like it, can those participating zoom into your home city and provide info on whether you're in a Best, Good, Moderate, etc region?

This currently speaks volumes about carrier testing of OS's. In all appearances, the foreign market must be working wonders for RIM, because the majority of the "official" OS releases have been from overseas. The local market, in comparison, has all but abandoned device support. It would stand to reason that the 3xx series of OS may have been the last of the local markets test platform.

Tsells "guinea pig" statement spoke volumes to me, because if AT&T is saying "we're only going to support BB10 devices..." and leave the rest of us hanging, with our findings holding some strong validity...I'd be pissed. If it's a lack of tower support, on the other hand, then waiting for "4G" to spread will alleviate the matter - but why do we have to wait that long?

I've experienced the muting mic issue even on 2xx and 3xx series OS, but since I'm a tinkerer, I just wrote it off. I still do. But I don't mind reporting these findings to some higher ups at AT&T. Will they care...no. But if we jump ship to another carrier, with stronger coverage - even the thought of doing that - may move them to make adjustments. Hitting their pockets brings attention.

OK - so after reviewing the AT&T coverage map - here's some more mystery thrown into my own thread and suspicions:

Running Mecca's Gamma prime - LOCAL MARKET = BEST for voice; 4G coverage in some areas; LTE in other areas - NO MIC PROBLEMS

Traveled to PHOENIX = BEST for voice; LTE every place I went - TOTAL UNRECOVERABLE MIC PROBLEMS

And as previously posted, NO MIC PROBLEMS upon return to home market

[BDKira]

Dunno if I should exist in this thread xD But here anyways..

1) What carrier are you on: Grameenphone
2) What OS you are running/tried: Tried everything from leaked to hybrids up till .402 and Barracuda Series 4.5, Myth of Love .402, and Nitroberry NX-2
3) Whether you are/are not having problems: Worked flawlessly till I tried .523 hybrids, now everytime I call it gets disconnected IMMEDIATELY, same with TEXTING, I can't text and data doesn't work, phone is basically useless!
4) What city/region you are in?: Sylhet, Bangladesh (Originally from NY, have a house in the Poconos for all you Pennsylvanians out there, holla!

[newcollector]

According to the ATT coverage map my family resides in a very high level coverage area. We get several bars of H+ at home. Yet every .4xx OS so far had mic issues on my 9810. .391 is holding steady and working well so far.

In Louisville we are in a very high level of coverage. I have had no problems with any of the .4xx OS builds. Right now I am on .428 and have had no issues. It seems really strange who does and who doesn't have problems on some of the 7.1 builds.

[go1ndr]

Great info in here. I've pulled up AT&T's regional coverage map - it's interactive, so I've provided a link: AT&T Coverage Viewer
If you feel like it, can those participating zoom into your home city and provide info on whether you're in a Best, Good, Moderate, etc region?

This currently speaks volumes about carrier testing of OS's. In all appearances, the foreign market must be working wonders for RIM, because the majority of the "official" OS releases have been from overseas. The local market, in comparison, has all but abandoned device support. It would stand to reason that the 3xx series of OS may have been the last of the local markets test platform.

Tsells "guinea pig" statement spoke volumes to me, because if AT&T is saying "we're only going to support BB10 devices..." and leave the rest of us hanging, with our findings holding some strong validity...I'd be pissed. If it's a lack of tower support, on the other hand, then waiting for "4G" to spread will alleviate the matter - but why do we have to wait that long?

I've experienced the muting mic issue even on 2xx and 3xx series OS, but since I'm a tinkerer, I just wrote it off. I still do. But I don't mind reporting these findings to some higher ups at AT&T. Will they care...no. But if we jump ship to another carrier, with stronger coverage - even the thought of doing that - may move them to make adjustments. Hitting their pockets brings attention.

Thanks for the map Mecca! By looking at the map, you would think that I am located in the best possible area for 4G/H+ coverage but ironically, I actually had to get a 3GMicroCell for my house as the reception was so bad. I live on a golf course in a very open area of Ventura County, CA (beach) and the coverage should be great but I have to actually go a mile or two for it to be perfect. That said, I have had zero issues with the .378 build you told me was a good build in May, and it has been great!

My wife's 9810-.378 however, does have some"breaking up" issuess and mic issues from time to time but only in certain areas around our house and within a few miles of it. I assumed it was due to her dropping it a few times, or wondering in and out of another carrier's cell area but now I'm beginning to wonder. I want to beleve it's due to coverage and perhaps dropping it but not completely sure. Thanks as always for all that you do for the forums and us BB lovers!

[nsane1]

Ok confirmed. Working phone in Dallas TX (635/Tollway), does not work in DC (Froggy Bottom).

My first 2 calls were fails in DC, my third worked. 4 bars 4G both locations.

[tsells]

Ok confirmed. Working phone in Dallas TX (635/Tollway), does not work in DC (Froggy Bottom).

My first 2 calls were fails in DC, my third worked. 4 bars 4G both locations.

This further confirms the "location theory", as there is yet to be a report of a mic problem by anyone in Texas!
I've updated my post above and added Washington DC to the "bad" cities.

[sbmd]

1) What carrier are you on? AT&T
2) What OS you are running/tried? ALL Leaked, Official, and Hybrids
3) Whether you are/are not having problems Yes, muted mic with 402 and 428.
4) What city/region you are in? My home region is Southern WI. I did not have issues with 428 until I got to Phoenix, I am hoping that it will work again once I return home. 402 did not work in Northern WI or in Southern WI. It did not matter whether or not it was a hybrid or not, if I used the 402 radio file, it never worked for me. I have not yet tried a hybrid for 428. 391 and lower have always worked for me stock or hybrid.


I travel a lot for work, so I get to many different regions. Let me know if there is anything you would like me to try, I will do my best to test it out. I am very busy some days so it can be difficult to test something on the spot, but I will get around to testing it. Thanks.



Also the 9860 on 402 had mic problems in Northern WI, this was the only place I tested it.

[tsells]

1) What carrier are you on? AT&T
2) What OS you are running/tried? ALL Leaked, Official, and Hybrids
3) Whether you are/are not having problems Yes, muted mic with 402 and 428.
4) What city/region you are in? My home region is Southern WI. I did not have issues with 428 until I got to Phoenix, I am hoping that it will work again once I return home. 402 did not work in Northern WI or in Southern WI. It did not matter whether or not it was a hybrid or not, if I used the 402 radio file, it never worked for me. I have not yet tried a hybrid for 428. 391 and lower have always worked for me stock or hybrid.


I travel a lot for work, so I get to many different regions. Let me know if there is anything you would like me to try, I will do my best to test it out. I am very busy some days so it can be difficult to test something on the spot, but I will get around to testing it. Thanks.



Also the 9860 on 402 had mic problems in Northern WI, this was the only place I tested it.

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.

[Mecca EL]

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 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

[jmb12177]

Maybe the reason that we don't see any updates from att is they are focusing on the bb10 devices that are to come.

Sent from my 9810 using Tapatalk

[Don_Henry]

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.

OK - so while I am glad that my theory of "regionality" proved out (and thusly I am not imagining things) - I am also totally bummed that all of us AT&T users are facing this issue.

I concur with Mecca - I hope your prediction does not prove to be true - I do not want to go back to to .391 and be stuck there simply because AT&T would rather sell iToys and HemmaROID devices to people . . .

And there is no way to complain to AT&T - they will simply say "you are using a non-authorized OS" - and if reported to RIM, there is nothing they can do about it since the problem lies in specific AT&T tower equipment/configurations and how certain towers don't play well with the uplink side of the .4XX and later sfi files . . .

Maybe time to consider a 9930 and moving to Verizon . . . . except then I would be giving up my 9810 and Mecca's killer hybrids . . . . so I guess I will not make the switch . . .

[jefo13]

I can confirm 523 works on my 9900 in So. Cal, but had mic issues in Denver and Philadelphia. I have found that if the person on the other end waitsblng enought, themic works. Anyone else noticed this?