I am experiencing a problem with the speakerphone. The buzzing noise that is known to happen on GSM devises when u r close to speakers, TV's, radios etc is happening when I turn on the speakerphone. Is this a known problem for GSM TP2 devices running android? Is there a fix or will I just have to deal with it till it gets worked out?
EDIT
I have done some testing and lots of reading. Its seems that the "GSM BUZZ" only happens on the 2G network. I will explain exactly what I am experiencing, when I am on the phone if I turn on the speakerphone the speaker starts buzzing, also if I am on the phone and recieve an alert/notification or press a button the same buzz comes through the speaker and to stop it I have to turn the speakerphone on then off. This is a real problem and it is happening on both GSM devices I have access to. I need people with GSM devices to do test so we can see if this is happening on all GSM devices. All I need is for u to make a call with 3G turned off or if u do not have 3G access simply turn the speakerphone on and report what happens. Also make a call and press a key, I belive that if keytones are enabled the buzz will happen and if not it will be buzz free. Somehow sounds are turning on the speaker while on the phone. Lets get this fixed!
You have a giant WinMo6.5 logo in your sig... Why don't you stick to WinMo?
Does it happen in WinMo? I don't have any speakerphone issues, but I'm on CDMA.
I asked for help not a smartass comment. stop being condescending towards people just cause u have a little knowledge. if all ur gonna do is talk down to others than y even post anything? u can go ahead and come back with another post trying to put me down but all it will do is make me laugh. please do not post unless u are willing to help me understand my problem. I know u think ur routine of accusing people off not reading before posting makes u feel like a man but to other u come of as a douche bag.
Now to answer ur question, CDMA devices so not genrerate the buzz through TVs and speakers that GSM devices do. My question was asking y the known buzz comes through the speakerphone. its almost like android thinks the speaketphone is part of another device.
now ur other question, I don't stick to WM for the same reason everyone else doesn't, my device allows me to do things like boot android and Ubuntu so I have the freedom to choose my OS.
porkenhimer said:
I asked for help not a smartass comment. stop being condescending towards people just cause u have a little knowledge. if all ur gonna do is talk down to others than y even post anything? u can go ahead and come back with another post trying to put me down but all it will do is make me laugh. please do not post unless u are willing to help me understand my problem. I know u think ur routine of accusing people off not reading before posting makes u feel like a man but to other u come of as a douche bag.
Now to answer ur question, CDMA devices so not genrerate the buzz through TVs and speakers that GSM devices do. My question was asking y the known buzz comes through the speakerphone. its almost like android thinks the speaketphone is part of another device.
now ur other question, I don't stick to WM for the same reason everyone else doesn't, my device allows me to do things like boot android and Ubuntu so I have the freedom to choose my OS.
Click to expand...
Click to collapse
You obviously do not what you're talking about.
Plus, I asked a simple question and you failed to answer it in your long drawn out whining post. Meh.
FYI, CDMA devices produce a similar noise in other devices, not sure why you think that's isolated to GSM. iDEN does the same thing - perhaps the frequency is different, never really looked into it.
Your sig just makes me think you prefer WinMo, and kinda makes me giggle as it is comically large.
Well, I've got a bit of the same problem. But it only occurs when I'm either ending the call or when i have to touch the touchscreen during the call. Then it just goes haywire and give the bzzzz noise..
Running Froyo Red..
arrrghhh said:
You obviously do not what you're talking about.
Plus, I asked a simple question and you failed to answer it in your long drawn out whining post. Meh.
FYI, CDMA devices produce a similar noise in other devices, not sure why you think that's isolated to GSM. iDEN does the same thing - perhaps the frequency is different, never really looked into it.
Your sig just makes me think you prefer WinMo, and kinda makes me giggle as it is comically large.
Click to expand...
Click to collapse
i do know what i am talkin about. its called "THE GSM BUZZ" cause it happens on gsm devices.
i am so sorry i did not get ur approval before postin my sig. u remind me of one of those kids that feel bad about ther self so they try to insult other to make themselves feel better. u picked the wrong one. i ain't puttin up with ur ****. u may get a pass from other cause u helped a few people but u r constantly being rude to anyone that ask a simple question. ur way is not always right.
i asked for help not for comments on my sig or to be told to stick with a certain OS. this is America and i can like two things at once. yes i love WM but if i wanna use android on my device i will and do not need u to make up my mind for me. if u wanna help me get to the bottom of this buzzing noise fix this problem then cool but i do not need ur condecending remarks.
arrrghhh said:
You obviously do not what you're talking about.
Plus, I asked a simple question and you failed to answer it in your long drawn out whining post. Meh.
FYI, CDMA devices produce a similar noise in other devices, not sure why you think that's isolated to GSM. iDEN does the same thing - perhaps the frequency is different, never really looked into it.
Your sig just makes me think you prefer WinMo, and kinda makes me giggle as it is comically large.
Click to expand...
Click to collapse
Actually, I'd be shocked if a CDMA device actually caused the "GSM buzz" in other devices - Interference maybe, but not the distinctive buzz. It's due to differences in the channel access schemes between CDMA (To be specific, ANY form of CDMA, whether it is Qualcomm CDMA2000 or UMTS) and GSM (iDEN is similar to GSM)
CDMA systems a channel access scheme that has all devices transmitting continuously when active, but using special coding so that the receiver at the cell tower is able to "pick out" the individual handset signals. Since the device is transmitting continuously, the RF power envelope is fairly constant.
2G GSM/EDGE (not UMTS), iDEN, and the long obsolete D-AMPS use a different channel access scheme, time division multiple access. Each handset is assigned a time slot (or slots for EDGE) to transmit in. On a given channel, a set of slots is contained within a frame. Each time a phone's assigned spot in a frame comes up, it transmits. The end result is that the RF envelope pulses on for a short period every frame. Many other devices will rectify and filter the RF (unintentionally) resulting in a signal that follows the RF envelope - a low duty cycle square wave with a frequency equal to the frame repetition rate.
I have no clue why a device would cause such interference to itself in only one OS. It's not an issue anyone else has encountered to my knowledge. Original poster has a pretty poor attitude and atrocious grammar that is difficult to read. (People who can't be bothered to type out the word "you" really bother me for some reason...)
Entropy512 said:
Actually, I'd be shocked if a CDMA device actually caused the "GSM buzz" in other devices - Interference maybe, but not the distinctive buzz. It's due to differences in the channel access schemes between CDMA (To be specific, ANY form of CDMA, whether it is Qualcomm CDMA2000 or UMTS) and GSM (iDEN is similar to GSM)
CDMA systems a channel access scheme that has all devices transmitting continuously when active, but using special coding so that the receiver at the cell tower is able to "pick out" the individual handset signals. Since the device is transmitting continuously, the RF power envelope is fairly constant.
2G GSM/EDGE (not UMTS), iDEN, and the long obsolete D-AMPS use a different channel access scheme, time division multiple access. Each handset is assigned a time slot (or slots for EDGE) to transmit in. On a given channel, a set of slots is contained within a frame. Each time a phone's assigned spot in a frame comes up, it transmits. The end result is that the RF envelope pulses on for a short period every frame. Many other devices will rectify and filter the RF (unintentionally) resulting in a signal that follows the RF envelope - a low duty cycle square wave with a frequency equal to the frame repetition rate.
I have no clue why a device would cause such interference to itself in only one OS. It's not an issue anyone else has encountered to my knowledge. Original poster has a pretty poor attitude and atrocious grammar that is difficult to read. (People who can't be bothered to type out the word "you" really bother me for some reason...)
Click to expand...
Click to collapse
but its not just my device. my friend also has a tilt 2 and she lives in another part of the state and her speakerphone makes the same buzing noise on android. its kinda weird cause i have not seen other people askin about this problem. its just a buzzing noise that makes u not wanna use the speakerphone. also it happens if there is alerts while using the phone and then the only way to stop it is to turn the speakerphone on then off. it has to be affecting others too. it could not just be happening on two devices.
I see exactly the same thing on my rhod100 (de).
I also have another problem which existed for a long time: On some occasions, after booting to android, audio is completely gone. I test it by placing a call and checking if there is any in-call audio. Plus, on such an occasion, media files also do not make any sound, and rebooting the phone is the only solution. Enabling speakerphone does not help, even if I hear the mentioned buzzing sound.
I remember seeing something about audmgr_enable and that the arm9 did not respond to an rpc in the logs. I can post them if that happens again.
I think there are a fair number of known issues with the speakerphone.
I haven't bothered to try it myself, the only speakerphones I have ever used with acceptable audio quality are Polycoms.
edited first post.
well... i have the same problem and i've tried all the android variants out there...
finally someone else that has this problem. it is a big problem for me cause it makes the speakerphone unusable. I wish someone with some knowledge would recognize this is a real problem and try to fix it. I think somehow android thinks the speaker is part of another device.
are ALL the users with this problem ONLY experiencing this issue on Android or WinMo as well?
ryannathans said:
are ALL the users with this problem ONLY experiencing this issue on Android or WinMo as well?
Click to expand...
Click to collapse
From his description, it seems to only happen in Android.
I talked to stine briefly, and he hasn't tested it - is there a bug open on it? If you really want dev attention to a problem, and there isn't already a bug, file a bug. If there is a bug, post to it and add some logs - there might be something funny going on that's easily spotted.
Also, you haven't done any triage from what I can tell - does this not happen on a certain combination of rootfs, kernel, or system image? If you can recreate a scenario of where it doesn't happen, that'll help narrow it down. If it's always been happening... it'll be more difficult, but also good to know.
One of our top kernel devs has a GSM device, he's never mentioned this issue. If I talk to him today, I'll mention it to him.
arrrghhh said:
From his description, it seems to only happen in Android.
I talked to stine briefly, and he hasn't tested it - is there a bug open on it? If you really want dev attention to a problem, and there isn't already a bug, file a bug. If there is a bug, post to it and add some logs - there might be something funny going on that's easily spotted.
Also, you haven't done any triage from what I can tell - does this not happen on a certain combination of rootfs, kernel, or system image? If you can recreate a scenario of where it doesn't happen, that'll help narrow it down. If it's always been happening... it'll be more difficult, but also good to know.
One of our top kernel devs has a GSM device, he's never mentioned this issue. If I talk to him today, I'll mention it to him.
Click to expand...
Click to collapse
it happens no matter what build or combination of parts. it only happens on android anytime the speaker is on and if the speaker isn't on and any kids of alert or noise such as a button press happens the speaker comes on and buzzez till u manually turn the speakerphone on then off. basically the same noise that comes through any audio device when a GSM cell is near is comin through the speaker. i am pretty sure it only happens on 2G cause the "GSM BUZZ" does not happen with a 3G signal. if ur guy test he'll for sure hear it.
I just managed to confirm the issue on a Tilt2 - needed to force 2G.
(I almost never use speakerphone and am almost always in 3G areas so never noticed this before.)
Apparently there are some audio routing patches in the pipeline already that might fix this.
Problem gone in Android 2.3.3... works like a charm
eu0741924381 said:
Problem gone in Android 2.3.3... works like a charm
Click to expand...
Click to collapse
Interesting - did you ONLY change system.ext2 build, or did you also use a different kernel?
had this problem a few times (froyo) but never occurred in my last call.
I think it may have something to do with a data connection before or during the call? There are a few problems originating from data connections. Perhaps it was latest kernel that fixed it for me? Will have to wait and find out.
Related
Hello,
well I think all of you know, that many reviews say, that the call quality of TG01 is pretty bad. They say, that the people that you call with the TG01, don't understand your voice very good etc.
Well it's not clear if it's a hardware or a software issue.
So today I made a test of the hardware. I installed the newest version of Skype mobile on the TG01 and called the Skype test Service. There I could leave a voicemessage and after that I was able to hear my voicemessage.
So I tried that and found that the quality of the microphone isn't very bad. Everything was very clear. No cracking or somethin like that.
So why is the quality in normal calls so bad? I think it could be a software problem. I would be very happy if it would be a software problem, because softwareproblems can be fixed
What do you guys think?
I would like you to try this method, too. I want to know if you make the same experiences with the microphone on skype that I have made.
Best regards,
Manuel
there is already a topic for this
there is more to it then the test you described accounts for like signal being 3g or 2g probably other variables but you test shows good results for software prob which can be proved by results of using srswow
useyourfist said:
there is already a topic for this
there is more to it then the test you described accounts for like signal being 3g or 2g probably other variables i belive there may be some incompatabilty with signals of the phone your calling
Click to expand...
Click to collapse
so many people are complaining about this.... but imho no ones actually quantified the problem...
some say it's barely able to function as a phone, others say the call qual is merely degraded...
some say no probs on 3g, others say 2g is best....
most people seem to agree its probably not hardware... the problems is retained on bluetooth... aparently...
some say it's orange... some say it's any 1800gsm network...
i think the majority of people who have unlocked thier phone & moved away from orange have experienced improved results... there's a few posts to this effect over on modaco.com & my own opinion is that my unlocked TG much prefers my work SIM to my orange one... roll on end of contract
trying to post on my tgo1 is annoying you got my post before i finished it lol stupud buttons i agree its got to be software or evil orange hopefully the rumored fix appears soon. i personaly have bad quality all the time so like you roll on end of contract 20months noooooooo
My TG01 ia unlocked and I use it on the o2 network, I had complaints from people i am calling about them not being able to hear me or dropping in and out so the problem is not specific to orange. It is better with a bluetooth headset but still not great.
I am waiting for this rumoured "audio fix" to appear from orange / toshiba or the newer 6.5.3 rom would be nice (wont hold my breath though).
i forgot to mention when i first got tg01 i had loads of problems, anyway went into store and they "tested" it and said it sounded fine i told them what i thought it sounded like trying to talk through two tin cans with a string,
manager at store said thats just what tg01s sound like htere is nothing that we can do, no refund as its classed as being in the design of the phone not an actual fault. i am going to start a down with orange group lol
if I ring someone from my orange sim, hang up swap to my tmuk sim and ring them back they tell its like i'm on a diff phone....
You sure you're not using a different phone?!
I can't honestly see why that should make a difference, phone-side, as TMob and Orange operate on the same frequency band - I suppose it could be through the voice-compression systems used at the cells and downlinks though.
The way to test this, would be to try a test-call using both your Orange and TMobile SIMs in a different handset - see how it goes.
I've found the 'listening' quality of the TG01 pretty poor, I have to admit, but having spent years listening to, and diagnosing audio systems small and (very) large, what I'm hearing is definitely a limitation of the speaker / amplifier, rather than codec / software issue.
if I ring someone from my orange sim, hang up swap to my tmuk sim and ring them back they tell its like i'm on a diff phone....
Click to expand...
Click to collapse
This could point to an issue with one of the bands that the phone uses causing the problem like the 3g band. I have read other posts saying they dont have an issue when the phone is forced to GSM mode.
I have the problem both with the orange sim that came with the phone and also my contract o2 sim. This leads me to believe that the problem doesn't lie with the operator but with the actual phone itself. It could be hardware but most likely software as most people are saying.
Lets hope they release this blinking fix soon before i get rid of it and get an android phone. Had windows mobiles for the past 6 years and have put up with things not working because basically there wasn't an alternative that could match what the windows platform could. Now there is so unless something drastic happens on the windows mobile front there will be a lot people leaving and going to alternative platforms.
orange and tmobile are the same company as of a few months ago so i will avoid them both now. its such a shame tg01 has this problem i will have to find out what network the people that complain to me about how i sound are on (as some say i sound fine) as its an interesting therory about signals ect
Some news again:
-------------------
Dear Manuel
Thank you for contacting Toshiba Mobile Communications.
Toshiba currently negotiating with the network operators in order to release new software to resolve the audio issue. Unfortunately, we cannot do anything until this approval is been given.
Please do not hesitate to contact us again for further assistance and use the reference number found in the subject field for all enquiries.
Best Regards,
Toshiba Mobile Communications,
T: 008000 505 2006 - International free phone number
T: 0044 207 111 0990 - Please use this number if your country does not support the free phone number
E: [email protected]
------------------
But I think all of you know, that a software update is planed.
useyourfist said:
orange and tmobile are the same company as of a few months ago so i will avoid them both now. its such a shame tg01 has this problem i will have to find out what network the people that complain to me about how i sound are on (as some say i sound fine) as its an interesting therory about signals ect
Click to expand...
Click to collapse
i dont think that TMUK & O-UK have combined thier resources yet...
youbrokeit said:
You sure you're not using a different phone?!
I can't honestly see why that should make a difference, phone-side, as TMob and Orange operate on the same frequency band - I suppose it could be through the voice-compression systems used at the cells and downlinks though.
The way to test this, would be to try a test-call using both your Orange and TMobile SIMs in a different handset - see how it goes.
I've found the 'listening' quality of the TG01 pretty poor, I have to admit, but having spent years listening to, and diagnosing audio systems small and (very) large, what I'm hearing is definitely a limitation of the speaker / amplifier, rather than codec / software issue.
Click to expand...
Click to collapse
as you say same frequenzy band - but completely different hardware at each end + different infatsructure....
a lot of this is probably location... Orange is terrible where i live at the best of times....
DunkDream said:
Some news again:
-------------------
Dear Manuel
Thank you for contacting Toshiba Mobile Communications.
Toshiba currently negotiating with the network operators in order to release new software to resolve the audio issue. Unfortunately, we cannot do anything until this approval is been given.
Please do not hesitate to contact us again for further assistance and use the reference number found in the subject field for all enquiries.
Best Regards,
Toshiba Mobile Communications,
T: 008000 505 2006 - International free phone number
T: 0044 207 111 0990 - Please use this number if your country does not support the free phone number
E: [email protected]
------------------
But I think all of you know, that a software update is planed.
Click to expand...
Click to collapse
this (often posted) msg from Toshiba could amount to a number of things...
it could mean
we've developed a fix & are merely waiting for the carriers to agree distribution terms before we issue it
but it might mean
we dont care - go away. if the carriers start saying there's a problem & they're prepared to pay us development costs then we'll consider lifting a finger to find a fix, but we're a bit busy developing other products at the moment so if you don't like waiting, we suggest you get a iphone
or anything in between.... !!!!!!!!!!!!!!!!!
it's worth noting that Japan doesn't use GSM, so they may not be that ofey with designing for it....
I still just want to clarify what exactly the problem is....
Like I said earlier
To many people are describing varying degrees of severity, against far to many variables
We’ve read them all... "this phone's shjt, its ok on 3g, its best on 2g, its orange, it's the 1800gsm band, its hardware, its software blah blah
To meaningfully get to the bottom of this we really need to pool resources, conduct some testing & arrive at what the precise problem is we're experiencing...
After all if everybody is correct about the problems their having... then all this serves to demonstrate is that TG01s are leaving the factory with a myriad of different problems, suggesting a woeful lack quality control....
...........which would be very unlikely from someone like Toshiba....
My own €0.02 ???
Orange is pathetic in my area.
I can only get 2g signal. On my Nokia 2600 I had to go into the garden to get any telephony at all.
My TG at least works in the house.
When I use the TG I can be heard fairly well - with the occasional ''can you repeat that mate, you broke up a bit' from the person on the other end of the line...
When I put in the T-Mobile SIM call quality is vastly improved....
....based on the above I THINK that
- The TG01 isn't a bad unit - perhaps just not as good as some of the other WM devices...
- The majority of MY call quality issues are caused by the orange signal in my area
.........................
Reading this forum RE the (apparently divine, can do no wrong) HTC HD2 didn't that arrive with dodgy call quality & the xda boffins had to make a selection of revised radios to get the quality people expected?
Cheers - sorry for the long one !!!
Adam
I still just want to clarify what exactly the problem is....
Like I said earlier
To many people are describing varying degrees of severity, against far to many variables
We’ve read them all... "this phone's shjt, its ok on 3g, its best on 2g, its orange, it's the 1800gsm band, its hardware, its software blah blah
To meaningfully get to the bottom of this we really need to pool resources, conduct some testing & arrive at what the precise problem is we're experiencing...
After all if everybody is correct about the problems their having... then all this serves to demonstrate is that TG01s are leaving the factory with a myriad of different problems, suggesting a woeful lack quality control....
...........which would be very unlikely from someone like Toshiba....
My own €0.02 ???
Orange is pathetic in my area.
I can only get 2g signal. On my Nokia 2600 I had to go into the garden to get any telephony at all.
My TG at least works in the house.
When I use the TG I can be heard fairly well - with the occasional ''can you repeat that mate, you broke up a bit' from the person on the other end of the line...
When I put in the T-Mobile SIM call quality is vastly improved....
....based on the above I THINK that
- The TG01 isn't a bad unit - perhaps just not as good as some of the other WM devices...
- The majority of MY call quality issues are caused by the orange signal in my area
.........................
Reading this forum RE the (apparently divine, can do no wrong) HTC HD2 didn't that arrive with dodgy call quality & the xda boffins had to make a selection of revised radios to get the quality people expected?
Cheers - sorry for the long one !!!
Adam
youbrokeit said:
I've found the 'listening' quality of the TG01 pretty poor, I have to admit, but having spent years listening to, and diagnosing audio systems small and (very) large, what I'm hearing is definitely a limitation of the speaker / amplifier, rather than codec / software issue.
Click to expand...
Click to collapse
sorry to be thick - but are you saying you think the problem is caused by the physical speaker (microphone) or by the amplification method the phone uses to boost sound output?
if this is what you're saying, then what do you think the fix is? (a different speaker?)
forgive my ignorance but i thought the problem was still edvident when using a BT device, so doesn't this rule out hardware altogther?
Sorry if i'm being thick... !!!
cheers
My dad is getting problems with poor audio, he often gets people asking "what did you say", when he can hear them clearly. The signal in our house is usually 4/5 bars of 2G with occasional 3G coverage in places.
He's getting fed up with it so I hope there is a fix coming because otherwise it's a decent phone bar the poor battery life.
eddybrown said:
My dad is getting problems with poor audio, he often gets people asking "what did you say", when he can hear them clearly.
Click to expand...
Click to collapse
This may sound really strange (and it's based on something somebody said on another forum) but ...
The microphone on the TG01 is at the bottom left of the screen. Can you ask your father to ensure that he is talking directly into the microphone and see if it makes any difference?
This may sound really strange (and it's based on something somebody said on another forum) but ...
The microphone on the TG01 is at the bottom left of the screen. Can you ask your father to ensure that he is talking directly into the microphone and see if it makes any difference?
Click to expand...
Click to collapse
Doubt it has anything to do with the microphone as it happens with a bluetooth ear piece as well.
Anyone else's In call volume very low? even though its on maximum volume? I cant seem to hear very well unless I put the phone on loudspeaker. any ideas on this one?
cheers
Yup. I am on .14 and it is awful. I hear the .16 update fixes it though. There are so many good things about this phone that I couldnt care less about this issue though at the moment.
Nope. I have .16 and it's just as bad.
Flamso said:
Nope. I have .16 and it's just as bad.
Click to expand...
Click to collapse
Cheers mate, I was just about to follow the debranding tutorial to update to 1.6 to improve my In- Call volume.
I have also heard that 1.6 offers an improvement in this area.
Baggyb said:
Cheers mate, I was just about to follow the debranding tutorial to update to 1.6 to improve my In- Call volume.
I have also heard that 1.6 offers an improvement in this area.
Click to expand...
Click to collapse
I'm actually thinking of unbranding my phone just because I can. But it's just to get rid of like one or two pre-installed programs.
i am on firmware 1.6 and it doesnt solve anything, its really really bad! the volume is ridiculous I can hardly hear anyone unless I go into a room where theres no noise at all! SE need to fix this
volume at max is not even iphone at half
Volume is terrible, i keep squeezing the phone into my ear.... what i don't understand is who ever listened to the phone and said ooooh this is good, how is he not FIRED
if this phone ever gets released in the US with the same problem i am complaining to the FCC. it seems someone to do something about it, (remember what happened to Toyota?)
I honestly dont think a firmware can increase/fix the volume issue, i honetly think the speaker is at its limits, i even hear distortion some times, telling me my volume way to loud for the speaker capacity, although i can BARLEY hear something.
Terrible
Yea, I cant say that the volume is loud, but I found out a solution that works for me.
Actually the screen seems to pick up the vibrations from the speaker, so if you instead of holding your ear against the speaker move your ear slightly down so that you actually have your ear on the top part of the screen instead... then the volume is much better!!
Just a tip.
And for SE: I noticed that only the higher pitched frequencies causes distort in the small speaker. Analyze the speaker and identify which frequencies that causes distortion and filter those frequencies out. Sacrifice those frequencies for a louder volume!
Regards // R
I read somewhere that they put the phone in test mode and forced the volume higher and worked.
Which would mean the hardware is capable of higher volume its just bad software.
This issue bugs me big time, and I'm quite dissapointed :-/
Any news on SonyEricsson solving this issue?
I've read that the X10 mini does have a much better loudspeaker. How can this be when it's an even smaller phone?
I strongly(!) hope that SE will fix it! A phone that is useless for phone calls? Than I can buy an iPod touch :-(
there is a 'volume hack' app but works only for rooted devices.
same problem..can hardly hear when on the street or in public place.
i enable speaker..and keep the loudspeaker near my ear.
Nocturnal310 said:
there is a 'volume hack' app but works only for rooted devices.
same problem..can hardly hear when on the street or in public place.
i enable speaker..and keep the loudspeaker near my ear.
Click to expand...
Click to collapse
Personaly I don't think that this is the way you have to make calls with a top of the line smartphone ;-)
Does anybody know if Sonyericsson is aware of this low volume issue?
Do they want to adress this issue with a soft- or hardwarefix?
Hopefully the update will come soon
http://talk.sonyericsson.com/message/1899#1899
Willey1986 said:
Hopefully the update will come soon
http://talk.sonyericsson.com/message/1899#1899
Click to expand...
Click to collapse
I hope so.
yea...its really in a sad shape
i cant believe it.
i dont know why would they make an android phone when they dont even know whats it like?
X10 = lots of problem + lack of hope and many anger users around the world
Yes there are many problems with X10, i think X10 problems will be solved soon after the update 2.1 let us hope for the best
i use the speaker all the time
i hate SE
Mehdiest said:
yea...its really in a sad shape
i cant believe it.
i dont know why would they make an android phone when they dont even know whats it like?
X10 = lots of problem + lack of hope and many anger users around the world
Click to expand...
Click to collapse
Actually, the number of problems is far, far, far, far, faaaaaaar less than you think it is. Being on a board for people needing technical support for their phones will make you think there's a lot more anger and problems than there really are. It's the nature of the internet.
Think about it, if there were really that many shopstopping problems, the phone would have gone through a recall by now. You can't let this forum (or any other tech support forum) give you any sort of indication of percentage of users with problems.
Same problem here... German o2 X10i (R2BA026). Speaker volume set to max. but still can't hear the other side It's a shame...
EDIT: oops... have to change my Avatar and Signature Hihi
iead1 said:
Actually, the number of problems is far, far, far, far, faaaaaaar less than you think it is. Being on a board for people needing technical support for their phones will make you think there's a lot more anger and problems than there really are. It's the nature of the internet.
Think about it, if there were really that many shopstopping problems, the phone would have gone through a recall by now. You can't let this forum (or any other tech support forum) give you any sort of indication of percentage of users with problems.
Click to expand...
Click to collapse
Looks like coming from se and not one of forum users. I am not worried as i know it will be taken care of now as it has been launched in us.
Sent from my X10i using XDA App
Hello everyone. This is my first post on XDA. I've been lurking for a month or two, and have decided that XDA is the place to be!
I've had my Bolt since April, and like many others I am very frustrated with it. The OTA back in May/June, the one that caused all the random resets, made me start exploring and discovering this thing called 'rooting'. Back then I felt that rooting was a risk I didn't want to take, yet. It reminded me a lot of my Dish Network days, where keeping up with ECM's was an ongoing hell, and I just didn't want to go back there. The OTA after that fixed the resets, and bought some time while I researched rooting.
For the most part, it seems like most of the problems are software related, and the hardware is just being held hostage by crappy coding. BUT, it also seems like most every TBolt owner is on their third device because of hardware issues. I don't want to trade up for a less-than-new device. I did go through an authorized reseller, and bought a year-long, no questions asked warranty, so I can play that card if needed.
My dilemma is that I am ready to root, but if I have bad hardware, I want to return an un-screwed with device. I know that I can unroot, but it would be my luck that it wouldn't go well. And believe me that I considered modding it just to see if it is the hardware or not.
ISSUES: I have various quirky things going on that are obvious software problems, like texts going to the wrong people, butt-dialing (once), CPU lock-ups, erratic scrolling (browsers mostly), software lags, etc.. I think the touch screen, though hardware, is controlled through SenseUI, which has really contributed to my wanting to go with AOSP. The biggest issue I have is with the data connection. I've read a lot of threads on this that have ended in numerous solutions. The most common culprits seem to be the SIM card and the battery cover (idiot design btw). Regardless of whether I am in a good coverage area or not, I have the classic ... 3G..1X..3G..nothing..1X..1X..1X..nothing..3G..nothing..1X..etc. This was really terrible before one of the OTA's, after which it seemed to settle down. I've also experimented with the modem settings, and also the radio settings. CDMA auto PRL works best. Still unsure about the modem settings. Currently I have CDMA only for preferred mode, Enable for Rev A., and Disabled for 1X diversity. I still experiment with these settings, but don't really see much difference. A detailed guide to those settings would be really kick-ass. One day, my phone wouldn't let me make or receive voice calls. Somehow, a setting changed that set it for EVDO only, really strange.
I use Easy-Tether, and have recently been using a Wilson dual-band repeater/amp. I have also found a most excellent app called RF Signal Tracker, which gives me separate RF meters for voice and data, and also shows the state of the SIM card when toggling Airplane mode. I live a little bit out of the city, so I know that serving towers might be causing some headache. With the Wilson, both meters are around -72dbm, which is decent. In town, without the Wilson, it's a little better, around -66dbm. I will stare at this this thing and watch the EVDO meter bottom out at -120dbm and then bounce back. Sometimes it will stay on 1X (for hours probably if I let it), requiring a reboot (or airplane toggle, it varies). Sometimes, while using ET, the signal strength will be awesome, but I get connection errors like it's not even hooked up, or I'll be typing a lengthy post and when submitting I'll get a Connection_Reset error. Sometimes the throughput will blaze (even while streaming), sometimes I'm reaching for a hammer. I have also found that "It works...if i use it," meaning that a data session might start out crappy, but will stabilize. There are times when the data connection is crappy, and rebooting the phone will fix it. And of course, there are many days with no issues at all.
With a hundred different combinations, I can find no rhyme or reason why this handset cannot maintain a data connection with consistency. I'm leaning toward software, but I still can't tell. Others with this problem had their SIM card replaced, which worked, but maybe it was just the battery cover. Is there a fool-proof test I can do that will troubleshoot this? Another possibility might be Big Red Brother compelling me to buy a Nexus.
And: 2.2.1
BB: 1.39.00.0627r
K: 2.6.32.21-g0606a3a
Build: 1.70.605.0
Pete said:
Hello everyone. This is my first post on XDA. I've been lurking for a month or two, and have decided that XDA is the place to be!
I've had my Bolt since April, and like many others I am very frustrated with it. The OTA back in May/June, the one that caused all the random resets, made me start exploring and discovering this thing called 'rooting'. Back then I felt that rooting was a risk I didn't want to take, yet. It reminded me a lot of my Dish Network days, where keeping up with ECM's was an ongoing hell, and I just didn't want to go back there. The OTA after that fixed the resets, and bought some time while I researched rooting.
For the most part, it seems like most of the problems are software related, and the hardware is just being held hostage by crappy coding. BUT, it also seems like most every TBolt owner is on their third device because of hardware issues. I don't want to trade up for a less-than-new device. I did go through an authorized reseller, and bought a year-long, no questions asked warranty, so I can play that card if needed.
My dilemma is that I am ready to root, but if I have bad hardware, I want to return an un-screwed with device. I know that I can unroot, but it would be my luck that it wouldn't go well. And believe me that I considered modding it just to see if it is the hardware or not.
ISSUES: I have various quirky things going on that are obvious software problems, like texts going to the wrong people, butt-dialing (once), CPU lock-ups, erratic scrolling (browsers mostly), software lags, etc.. I think the touch screen, though hardware, is controlled through SenseUI, which has really contributed to my wanting to go with AOSP. The biggest issue I have is with the data connection. I've read a lot of threads on this that have ended in numerous solutions. The most common culprits seem to be the SIM card and the battery cover (idiot design btw). Regardless of whether I am in a good coverage area or not, I have the classic ... 3G..1X..3G..nothing..1X..1X..1X..nothing..3G..nothing..1X..etc. This was really terrible before one of the OTA's, after which it seemed to settle down. I've also experimented with the modem settings, and also the radio settings. CDMA auto PRL works best. Still unsure about the modem settings. Currently I have CDMA only for preferred mode, Enable for Rev A., and Disabled for 1X diversity. I still experiment with these settings, but don't really see much difference. A detailed guide to those settings would be really kick-ass. One day, my phone wouldn't let me make or receive voice calls. Somehow, a setting changed that set it for EVDO only, really strange.
I use Easy-Tether, and have recently been using a Wilson dual-band repeater/amp. I have also found a most excellent app called RF Signal Tracker, which gives me separate RF meters for voice and data, and also shows the state of the SIM card when toggling Airplane mode. I live a little bit out of the city, so I know that serving towers might be causing some headache. With the Wilson, both meters are around -72dbm, which is decent. In town, without the Wilson, it's a little better, around -66dbm. I will stare at this this thing and watch the EVDO meter bottom out at -120dbm and then bounce back. Sometimes it will stay on 1X (for hours probably if I let it), requiring a reboot (or airplane toggle, it varies). Sometimes, while using ET, the signal strength will be awesome, but I get connection errors like it's not even hooked up, or I'll be typing a lengthy post and when submitting I'll get a Connection_Reset error. Sometimes the throughput will blaze (even while streaming), sometimes I'm reaching for a hammer. I have also found that "It works...if i use it," meaning that a data session might start out crappy, but will stabilize. There are times when the data connection is crappy, and rebooting the phone will fix it. And of course, there are many days with no issues at all.
With a hundred different combinations, I can find no rhyme or reason why this handset cannot maintain a data connection with consistency. I'm leaning toward software, but I still can't tell. Others with this problem had their SIM card replaced, which worked, but maybe it was just the battery cover. Is there a fool-proof test I can do that will troubleshoot this? Another possibility might be Big Red Brother compelling me to buy a Nexus.
And: 2.2.1
BB: 1.39.00.0627r
K: 2.6.32.21-g0606a3a
Build: 1.70.605.0
Click to expand...
Click to collapse
You need to research cellular technology. All the signal amps in the world aren't going to make for a stable lte signal unless they're smart enough to unpack the packets and lie about transmission data. That said, pretty much all your issues sound software related. Some of what you call hardware problems cannot be randomly duplicated by hardware failure or even accurately diagnosed without some knowledge and experience. Restoring to stock is easy and quite reliable. Some do it once or twice a week. I have guides in my thread.
Thank you for the response. I confirmed that it was software. I took it to the reseller and found out that even though I took two OTAs this year, the radio never updated, and was still on the original from the release. I'm at 2.3.4 now, with a stable radio. Feeling like I'll take that plunge, now that I know the hardware is good.
BB: 1.48.00.0906w_1, 0.01.78.0906w_2
K: 2.6.35.10
Build: 2.11.605.5
Hi folks,
I wanted to find out if the HTC One X "squeeze fix" potentially works to address some of the signal issues some of you may be having. It will help us understand if we have a hardware issue, merely a network issue, or possibly both.
Here's a thread that explains the issue and the fix for the One X:
http://forum.xda-developers.com/showthread.php?t=1688538
If you all could so kindly attempt to do the same (we have a few points of connection, so take off your battery cover to make sure you are squeezing the correct point to address the appropriate signal issue you are having) and report back.
If you DO NOT have a signal issue, this thread does not apply to you, so please kindly refrain from derailing the thread.
Thanks all!
Demo video for One X WIFI signal issues:
The two phones have completely different chassis so I'm not squeezing my phone.
We have identical prong connectors. Take off the plastic cover and have a look. Like I said, this is an inquiry poll to find out if we have a potential hardware issue since some people have been experiencing signal issues (in layman terms, this is fact-finding thread).
If we do not, great. Nobody can continue to argue that we have a build quality issue.
If we do, at least we can track it somewhere. There is no need to call this "non-sense" or to tell me that I'm holding my phone wrong. Jesus...
neoshi said:
We have identical prong connectors. Take off the plastic cover and have a look. Like I said, this is an inquiry poll to find out if we have a potential hardware issue since some people have been experiencing signal issues (in layman terms, this is fact-finding thread).
If we do not, great. Nobody can continue to argue that we have a build quality issue.
If we do, at least we can track it somewhere. There is no need to call this "non-sense" or to tell me that I'm holding my phone wrong. Jesus...
Click to expand...
Click to collapse
I am in Annapolis and for me, the signal is fantastic (whether I pinch the back, squeeze the right side, left, hold upside down with my left foot in the air, with my right eye closed..) Seriously, for me I am very happy. Today for example, regular CDMA tested with Speedtest resulted in near T1 speeds and that...was actually inside an elevator! Yes, I am very happy with almost every aspect of the EVO LTE. Fyi, I am rooted with Fresh 1st version, stock kernel etc, just so I could get the application links fixed.
If there is any hardware issues with signal, wifi or CDMA, I don't see it and have had the cell for two weeks tomorrow. My wifi connects to my wireless-N Netgear dual band around 30mb down and whatever up. Both CDMA/wifi work well, no matter how I hold it etc. Hopefully there isn't a bad batch of cells out there but maybe there is.
Thanks for your input. Really appreciate folks like you who give useful feedback!
Sent from my EVO using XDA
Service is kinda funky where I live so I tried this to see if there was a hardware issues and I can confirm there is no issue with my phone. Squeezing, pinching, pushing.....didnt change anything with the signal on the analyzer. Just confirms thats the service blows here.
1.) Has anyone with the "Bluetooth Problem" rooted their phone and found that it fixed the BT issue.
2.) Did the first OTA cause the BT problem on the Amaze.
I bought my HTC Amaze in January 2012. I didn't have my access to my Plantronic headsets at the time. Before I was able to test the Bluetooth on my Amaze, the first OTA came out. I did the update and all was good. Then my headsets came in and I tried them all (3 total -Voyager Pro HD and Explorer.) The range with the Voyager and Explorer was about 1-2 Ft. I basically had to hold the handset next to the Bluetooth headset. The Explorer had a better reception, but both headsets were distorted with the sound of static and would drop connection with a mere turn of the head. After ICS I now get about 8-10 Ft. with lots of static at anything over 3 feet.
My HD2 running CyanogenMod 7 still gets 30 ft. line of sight. And 15-20 through doors and walls.... I guess I'm spoiled.
Thanks for any answers guys.
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Maybe there's an issue with your BT antenna? It could be something as similar to the wifi fix (where you add a small piece of aluminum foil to the back of your case where the antenna is).
I have spent alot of time on the T-mo forum in the last few months. For the most part there seems to be a BT issue with at least "some" of the phones. When I updated to ICS the BT did without question get better. Not great.. but marked improvement. The fact that ICS made it better, along with a few posters stating that their phones BT worked fine prior to the first OTA but went bad after the update, led me to believe that the problem may be software related ...ergo the first OTA. The other people that are having this problem also saw a difference when they too updated to ICS.
One update "allegedly" messed up BT on the phone (some anyway) and another made the BT problem better. Strange....
hasoon2000 and kered424 are you guys running stock ROMs? I haven't rooted a custom ROM up to this point because I wasn't sure if it would actually fix the problem. That is why I was seeking a confimation or denial that rooting the phone would fix the problem. My dilemma is returning the phone. I have not unlocked the phone...but I did do the "Leaked ICS." But that is off topic...
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
kered424 said:
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
Click to expand...
Click to collapse
Thanks for you reply kered424.
I guess what I am really looking for is someone that actually recognized they had the problem and notice a change when rooting a custom ROM onto the phone. I may not find that person here...most people here root without need. I'm all about rooting...I have an HD2 that I still root (my digitizer just went out.) I just do not want to go through the hassle of rooting only to find out that it was the hardware and not the software. I would not even post about this and root the phone...if it were not for the marked impovement when I updated to "Leaked ICS."
It leaves me going: "Hardware?..software?...hardware?...software?"
From your description, it sounds like hardware. Have you tried the aluminum foil trick? That's the only thing I can think of.
Solution to Amaze 4G Bluetooth Issues. Possibly.
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
Still Still No Adequate Solution to Amaze 4G Bluetooth Issues.
badgerdave said:
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
Click to expand...
Click to collapse
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
BlackeyedBandit: I once read that the very first OTA is what messed up the Bluetooth on the Amaze. Unfortunately I am unable to comfirm this, or deny it. When I purchased my Amaze in Janaury 2012 my BT devices were being shipped to me. Before these devices got to me, my Amaze prompted me to do an update. I did it. When my BT devices arrived none of them had a range of more than 1-3 Ft. without static and/or terminated BT connection. When the ICS update came out the range increased to about 8-10 Ft.
I want to revert back the ROM that was first released to see if in fact it is better. But....I don't want to go through all those changes to find out it doesn't work any better. My phone is still completely stock...because I want to be able to return it soon. I love the phone and only want the BT to work in a manner that I have become accustomed to with HTC products. And to get the video stereo sound quality fixed too.
This is my second HTC device. The first was the HD2. It was a nightmare with WinMo 6.5 on it. I returned that thing 5 times and never got one that worked right. I eventually...with the help of xda members and others, learned the art of rooting. Once I got that down and rooted Andriod onto it, I was in love. I thought that even with all it's faults, HTC made an awesome device. I just needed to figure out how to "tune it up."
So I believed that the Amaze would be super awesome and looked forward to getting it. I feel let down because BT is a must for me. I'm not sure I will buy another HTC product either. This is the second time I have been burned.
BlackeyedBandit said:
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
Click to expand...
Click to collapse
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
notperse said:
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
Click to expand...
Click to collapse
Bro I think you have been extremely unlucky with the amaze. Although it does have some issues (capacitative light bleed, camera flash bleed, lower battery life than one would like, and slow development) most of these have been overcome to a great extent. If you are using a case you will have WiFi issues and possibly Bluetooth (I had WiFi issues with cover on, no BT issues) but that's fixible with a silver cigarette foil (or gold as well Iguess) placed in the battery back cover right beside the camera hole in the cover.
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
I too have the bluetooth connectivity issues. The only reference I could find to an "aluminum foil fix" was actually wifi antenna related. However, the thumbnail image is in this post by darll, 15th November 2011: (Wifi signal affected by phone case) in the Amaze 4g General forum.
BT MAC addresss
hasoon2000 said:
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Click to expand...
Click to collapse
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
chevycowboyusa said:
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
Click to expand...
Click to collapse
I think it is on the chip, but I'm not certain. It could also be programmed into the part of the phone firmware that is not touched when flashing.
I also want to report that I've had no issues with BT connectivity, and I have connected with about 8 headsets / handsfree over the past year.
My Amaze can get into a problem state with the BT, where the phone does not acknowledge a change in BT from off to on or vice versa. When this happens the phone starts to overheat, and I have to power completely down, and then power on again - at which point it will show the actual BT status. I've been on NRG almost from the start, so I don't know if this is a hardware issue or a ROM issue. I haven't had it happen in a while - I'm now more careful about turning on the BT (the problem seemed to happen when I was accidentally hitting the switch twice). Since I know how to avoid it, I haven't pursued any fixes.
Have you tried replacing the back cover? That seems like the most probable fix.
bluetooth
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
BT
artur-x said:
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
Click to expand...
Click to collapse
This have anything to do with it?:
http://forum.xda-developers.com/showpost.php?p=54112028&postcount=6