Related
I wonder if I have found a reason why GPS was not offered in the past year..
Since playing with the new radio and OS ROMs, the internal GPS on my phone has been consistently flawless. Indoor (wood frame house) and outdoor 5~30s lock ons to 3-8 satellites out of a visible 10.
A few weeks ago I got my dad the same Telus phone and this evening moved it also to the latest radio and DCD's 2.2.1. BUT, it can only perceive a maximum of 7 satellites and retain a much weaker and extremely intermittent lock to 1-3 satellites. When first activated with visualGPS, the signal strength and satellite recognition seems to be stronger for the first 5-10 seconds but then quickly drops off to rather poor levels. If the app is shut-down, I wait ~15 seconds and restart it then it returns with the same weakening performance model. This is all the while with my phone (identical ROMs) is close by but providing exceptional reception.
In the other thread concerning GPS performance there are some people complaining about the apparent "worthlessness" of the internal GPS. Possibly they aren't doing anything wrong but lost out on a crapshoot for a GPS viable Titan.
Checking in the EPST (reliable and significant? I'm still learning..), the hardware version of my phone is 0003 and the PRI Version (?) 1.15_010. In the next few days I'll head back to my Dad's to see if his phone states anything different.
GPS is working great on my Telus P4000 with the 2.2.3 ROM. Little jumpy in steel-and-concrete buildings and among the downtown buildings, but it's got a lock everywhere I've tried it.
Soundy106 said:
GPS is working great on my Telus P4000 with the 2.2.3 ROM. Little jumpy in steel-and-concrete buildings and among the downtown buildings, but it's got a lock everywhere I've tried it.
Click to expand...
Click to collapse
Yes, most seem to work well. But I think this is the first opportunity to test one of the phones with apparent weak GPS issues side-by-side with another that's working fine and has an identical (sprite backup image) software configuration.
After the ROM update, as mine, my dad's phone was updated on the Telus network via *228032. It was also left outside for 30 minutes to see if it could better survey and lock on to the satellites. I can't think of any software or settings discrepancies between the two that could cause such a difference in performance.
Tomorrow or Wednesday I'll again try out quickGPS and check if his EPST states any different hardware revision.
It's appears to be definite that my dad's Titan is subpar compared to mine with the internal GPS. It's EPST hardware revisons are identical to mine, so there is no visible difference between the phone.
I just again tried quickGPS with no difference in reception.
Keystone said:
It's appears to be definite that my dad's Titan is subpar compared to mine with the internal GPS. It's EPST hardware revisons are identical to mine, so there is no visible difference between the phone.
I just again tried quickGPS with no difference in reception.
Click to expand...
Click to collapse
please remember that this is still a "BETA" rom. it is not publicly released, or supported by ANYONE. with that in mind, it could get better with time, and when they finally release the public rom, test it again.
I was wondering the same thing if something was changed internally along the line.
I have hardware rev. 03, and my GPS blows.
fallingup said:
please remember that this is still a "BETA" rom. it is not publicly released, or supported by ANYONE. with that in mind, it could get better with time, and when they finally release the public rom, test it again.
Click to expand...
Click to collapse
Yes, and it is unlikely to be the cause of these discrepancies. With identical software setups between the Titans, I have left the hardware to be the lone differentiation. Could later software revisions resolve this hardware dilemma? Possibly, but with that mostly out of our hands and into the OEMs (I'm an old & jaded Toshiba e740 user....), I wouldn't put much hope in getting much more than what we are.
I started this thread because in the GPS FAQ thread some were expressing frustration at being unable to achieve the same GPS performance that was widely expected. With this side by-side comparison it may be comforting (though sad.... )to see that people may not be at fault for setting up the software on their phones. Myself and others were treating the GPS failures as though user error was at fault. After playing with my dad's Titan it is now clear to me that not all Titans are equal, and as such that may explain why the GPS abilities of the phone did not make it active to market. None of us bought these phones with a GPS guarantee.
jsmz, both mine and my dad's phones are hardware revision 0003. Without practical testing I don't think there is an obvious way to distinguish which phone will perform so radically different with its internal GPS. I have no inclination to tear them open..
i have hardware version 0003 and mine works fine...it gets me within ~10ft
My guess is if there are any deficiencies from one unit to the other it would most likely be in the Antenna not the actual hardware. Just about all of these units are chipset based and the features each unit has depends on how much of that chipset is used.
The fact that it is possible at all to turn on the GPS would seem to suggest it's not a hardware issue at all as far as chipset capability...
More likely just a individual manufacturing defect of that particular unit...
Could even be a bad soldering job...common with SMT boards.
Asphyx said:
My guess is if there are any deficiencies from one unit to the other it would most likely be in the Antenna not the actual hardware. Just about all of these units are chipset based and the features each unit has depends on how much of that chipset is used.
The fact that it is possible at all to turn on the GPS would seem to suggest it's not a hardware issue at all as far as chipset capability...
More likely just a individual manufacturing defect of that particular unit...
Could even be a bad soldering job...common with SMT boards.
Click to expand...
Click to collapse
I was thinking the same thing - the difference from one mass-produced unit to the next shouldn't be that substantial, and a bad/loose/iffy antenna or antenna connection is the most likely culprit.
Give it a good whack on the table and see if that smartens it up
Soundy106 said:
Give it a good whack on the table and see if that smartens it up
Click to expand...
Click to collapse
Just did that, didn't really help My gps really sucks takes at least 10 minutes to get a lock for the first time even outside with cleas sky. And even when I do get a lock using gmaps, it can be off by a whole New York City block, sometimes more. Too bad i can't just go to the sprint repair center and demand a replacement phone Maybe after the official release i will, who knows? But thank to this thread I don't feel so stupid anymore. I always thought i was doing something wrong, and after reading pretty much everything on gps here and installing quickGPS, i am quite sure it's not because of me.. But if anyone knows anything else i should try please feel free to tell me. Thanks
Asphyx said:
My guess is if there are any deficiencies from one unit to the other it would most likely be in the Antenna not the actual hardware.
Click to expand...
Click to collapse
Well as per forum posts the apparent hardware (chip revision, manufacturing flaw, etc...) discrepancy between units does not seem to be very isolated and it is best for all of us to be aware of this before banging our heads against the wall to get an afflicted unit operating.
My GPS works so well I was able to get a sustained lock at 35000 FT on a recent plane ride. That was cool, to see speed at 627KM/hour.
I have a friend that is also having GPS issues, so it appears to be fairly widespread.
having gone through 9 (yes, nine) telus P4000 units, i'm certain they are plagued with inconsistencies... getting on telus' case won't do much either except get you refurb after refurb if you're past the initial 14 days.
Lutzik - You mention off by a NYC Block...
Are you trying to use this in NYC?
I will point out that the height of buildings do block your unit from seeing enough satellites to get a fast and quick lock and whats more is you will also get reflections off the buildings that can hurt your accuracy if the conditions are right.
Remember GPS operates and locates you by noting the delay time it takes a signal to get from one of the satellite to you. It calculates the time it took the signal to get to you to determine how far away from that sat you are. By doing that for three sats minimum it triangulates your position...
Not a big problem with AGPS enabled navigators since the cell towers help ensure you have enough signal sources to throw out the errant data.
Sorry that did go a bit off topic...
I think the real issue is the beta radio driver. when a stable release is finally made I bet most everyone's sat lock and transmission issues will go away.
Asphyx said:
I think the real issue is the beta radio driver. when a stable release is finally made I bet most everyone's sat lock and transmission issues will go away.
Click to expand...
Click to collapse
It is possible to think that but beyond guessing we lack information to assume so while we have recorded cases of the erratic performance between devices with the identical software.
If a future software release resolves the problem then that further reaffirms a hardware discrepency between units. Yet we haven't seen a diffinitive answer that the units do have different gpsOne or other chipset revisions that require a software resolution while others units do not. As a few people are having GPS issues it may come down to the afformentioned quality control, manufacturing/design changes, etc..
It's cheaper to release a unit to retail without a potentially flawed feature than to advertise what may be broke and swallow a recall. I do think that we may be seeing why these phones were not sold as GPS enabled PPCs.
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.
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
I travel a lot, and I'm a minimalist. In other words, I'll travel for a week and take a paper lunch bag as my carry-on with hopes that I can get by with wearing the same outfit the entire week. I don't like carrying a full Navigation system and use my phone. This isn't an 'iPhone lovefest' because honestly, I hate everything about Apple, but I never had problems like this on my iPhone.
My problem though is the GPS. I'm on my third phone because of the GPS. The first phone would never get a lock on GPS. I could be sitting outside with a GPS satellite dedicated to me directly above me, and it would still say "Searching for Satellite". That phone went back and I took on another one.
Second phone had a problem where every now and then it would work, then stop working and never start working again until I rebooted the phone and even then it was questionable if it would start working again.
I just got my third phone a couple days ago. I did a stock root w/ no bootloaders, used Entropy's 11/13 Kernel, then threw on UnNamed ROM. This morning, I started up my car to drive somewhere and decided to test the GPS/Navigation. It took it a couple minutes to find the Satellite, then all seemed to be working ok. Then 20 minutes later it dropped the Satellite and it spent the next 40 minutes of my drive into the office saying "Searching for Satellite" no matter what I did.
This is really important to me as is the ability to tether when I want to (hence the reason I want a phone I can Root). So what can I do. At the moment, I've (In my head, so I could be wrong) narrowed it down to a couple things that could be wrong.
1. It's the ROM that's the problem. Though unlikely, it is a factor and it's me messing with the way the phone was designed and distributed.
2. It's the GPS in general. Seems like 95% of the people on here aren't having problems at all. There does seem to be 5% that seem to be having the same problems I am.
3. My region has crappy Satellite Coverage. Doubtful since my iPhone worked fine, and unless Apple did something amazing like put in an entire dedicated Satellite network to work with Jailbroke iPhones then this kinds of negates this though.
4. My cars are interferring. While this is entirely a possibility (I never do think to test this out in the open not in a car, so i can't say for sure) if it is the problem, then the device goes back as it's much cheaper to get a new device than to replace 2 cars. Again, though, my iPhone never had a problem doing this in these cars.
I love the phone, the speed, the Android OS etc... I don't want to go back to an iPhone because I"ll shoot myself. I just want to be able to have GPS work on this as it's the only hold up on the device. Any help anyone can do?
Take it back then. Honestly you say you have tried 3 different phones and all 3 are broken. I call bull****.
Never had a problem with it.
Sent from my SAMSUNG-SGH-I777 using XDA App
You didn't mention if you've tried in ANY of the three (3) phones if the GPS worked before rooting?? I'm not saying it's the rooting that's causing the problem, but I'm still running stock on my SGSII and have had no issues with GPS? Not saying it's not possible but three phones is kinda stretching it a bit to all have the same issue.
Yes, I know you took it back to STOCK rom with #3 but who knows if the STOCK ROM is really *STOCK*, you should try a new phone #4 stock without ROOT for at least a day or two to determine if it is a DESIGN/HARDWARE issue rule that out first and then try from there... If this still happens with STOCK phone, you may have to switch to another phone (iphone or otherwise)...
Good Luck!
I just took it back to stock and was going to go outside to see if it had problems finding service. Though as mentioned in many other threads on here, it's not so much it finding you when you're standing still. It's when you're driving the streets of Atlanta that things get crazy.
stalked_r/t said:
I just took it back to stock and was going to go outside to see if it had problems finding service. Though as mentioned in many other threads on here, it's not so much it finding you when you're standing still. It's when you're driving the streets of Atlanta that things get crazy.
Click to expand...
Click to collapse
Hi Stalk,
Keep in STOCK mode and drive around with it and see if this is still an issue then... Also if you have an aluminum case, this has been a known issue where the TARGUS (SP?) korean made BEAUTIFUL/GORGEOUS case affected the GPS antennae. Try it stock no case on the dash away from DIRECT sunslight and begin troubleshooting there...
UNFORTUNATELY it may boil down to Stock and working GPS or ROOT with Tethering... You ***MIGHT*** not be able to do both...
Good Luck...
If you JUST root, it shouldn't affect GPS - but test without rooting first.
And I agree - if you've got a metal case, DITCH IT.
So far, my experience is that the GPS chipset is almost as good as any standalone GPS chipset I've used - Sirf StarIII, MTKv2, STM Cartesio (the latter being the chipset in my Garmin Oregon, the former being chipsets in various Bluetooth dataloggers I've used for hiking). Actually, the GPS in this phone beats the StarIII and is around on par with the Cartesio. So far nothing I've ever used can touch an MTKv2 though.
I'm used to phones having crappy awful GPS chipsets - this is the first device I would ever consider using for geocaching on its own.
Thanks for the replies. I did test just now on the way to and from lunch with stock everything. I do have a case that's part aluminum (Case-Mate). I didn't try it without the case. didn't even think it could affect this.
Running a stock setup, I attempted to get navigation to my lunch location The drive was about 6 miles each way. When I left the office, I started Navigation. It never found a satellite enroute to the restaurant. I never stopped it during lunch from looking, though I was in a building, so i didn't expect it to find anything. On the way home, same status. Searching for satellites. I'm torn. I want this phone bad, love the Dev support, and there's nothing coming from AT&T that makes me want to use an old Blackberry to wait for. I also don't know what I can do to test this further.
On the way home, I'm going to do something very simple. I'm going to wipe the phone. I'm going to skip all steps of the initial setup, just have service and that's it. I'll start navigation and have it direct me home. If it doesn't work, I'll look at my options. If it works, then I know it's an app that's causing the problem.
Unless someone else can think of something for me to try. I wish this just worked like I know it can.
Ok. So an update. Wiped phone, not even associated with Google, Removed my 32 gig SD card for the heck of it, removed the case. Started nav and INSANTLY inside a building it had me pinpointed and was directing me to the next turn point to get home.
Here's the case I have: http://www.case-mate.com/Samsung-Ga...rsion-Barely-There-Brushed-Aluminum-Cases.asp
In one of the reviews, this is said:
As much as I wanted to love this case, I couldn't. I've used many Case Mate products before and I am just disappointed in them for the lack of quality of this case. There is a noticeable issue with the case fitting the bezel on the top right corner of the phone. The lip of the case fails to properly wrap around the front bezel. There is also the connectivity problems that come with this case. GPS has especially weakened with this case on. Other than that, I like the quality material that this case is built out of and feels very sturdy. Unfortunately though as of this writing, this is really the only choice for a decent case for this phone on the market. Time will tell if better choices come about.
Click to expand...
Click to collapse
I'm going to keep this setup through tomorrow, then root the phone if there's no difference in performance and all is well. If that works fine for 2 days, I'll throw the Kernel on and throw UnNamed on. If that works, I'll throw the case on and see what happens. I now feel like this could be the problem. Thanks for the thoughts guys. I'll continue my abuse of the "THANKS" button and thank you all.
ride home was flawless. If ride to work tomorrow is flawless, I'll root and flash.
Entropy512 said:
If you JUST root, it shouldn't affect GPS - but test without rooting first.
And I agree - if you've got a metal case, DITCH IT.
So far, my experience is that the GPS chipset is almost as good as any standalone GPS chipset I've used - Sirf StarIII, MTKv2, STM Cartesio (the latter being the chipset in my Garmin Oregon, the former being chipsets in various Bluetooth dataloggers I've used for hiking). Actually, the GPS in this phone beats the StarIII and is around on par with the Cartesio. So far nothing I've ever used can touch an MTKv2 though.
I'm used to phones having crappy awful GPS chipsets - this is the first device I would ever consider using for geocaching on its own.
Click to expand...
Click to collapse
I haven't gotten enough free time to log the NMEA output, but I don't think our "SirfSTAR IV" chipset is actually even using DGPS/WAAS. Which makes the accuracy it get's even more impressive. The chip definitely supports WAAS, but who knows exactly how the implementation is done between Android & Samsung...
I've also owned a SirfStar III based Bluetooth GPS, a MTK-based GPS (also the best I've found), and several phones with dedicated and integrated GPS chipsets. Have to agree our GS2 is one of the best. I can't exactly wander around the house and have it track my every movement like my Bluetooth pucks can (also having a large ceramic patch antenna helps a bit no doubt), but my GS2 locks fast, and stays locked. What else can you want from a GPS?
Might be worth it to look into WAAS either way though. On any standalone GPS unit, WAAS is the difference between 15-30 meter accuracy, and 3-5 meter (or better) accuracy. That is unless you have a military GPS unit, and the appropriate keys to receive the high accuracy P(Y)/M signals...
If you want to get a good idea of how the GPS is doing, this app will show you the strength of your GPS lock:
https://market.android.com/details?id=com.eclipsim.gpsstatus2
Also, upon further research, the NMEA output is reporting that WAAS/DGPS is not in use.
Example: "$GPGGA,222520.000,4218.460926,N,07111.901869,W,1,06,1.2,77.1,M,-33.8,M,,*53"
Where the bold "1" should be 2, and the null field right before the checksum "*53" should be the age of the DGPS/WAAS info if it were in use.
The chipset in our phones (http://www.csr.com/products/35/sirfstariv-gsd4e) clearly states that it supports WAAS. And since the choice of DGPS or not is solely in the hands of the chip and software (wiring/antenna connection/configuration is irrelevant) perhaps there is a way to enable the DGPS mode? If so, I'm sure we would all see MUCH better position and accuracy information.
WAAS probably requires modifications to the host processing binary (SIRFHost)
BTW, our chip is a GSD4t, not 4e.
I was having problems with my gps losing its lock for the longest time, i got a replacement phone and it started doing it again AFTER root. Im thinking some app might be causing the issue. I read somewhere that ROM Manager can cause issues. I deleted it and so far my gps has been working. I am really baffled on to what can be causing it.
stalked_r/t said:
ride home was flawless. If ride to work tomorrow is flawless, I'll root and flash.
Click to expand...
Click to collapse
Its the case man. Great looking case, but kills the cell signal and terrible GPS. Mine went back after 3 days.
Sent from my SAMSUNG-SGH-I777 using XDA App
Yep. Ride into work today lost signal once. After letting it sit for a couple minutes, I rebooted. After reboot it worked flawlessly. Definitely the case at this point. Putting Root/Kernel/ROM on it today and seeing how the drive home is. If it's good, then the case can be tossed and I'll find a different one.
Entropy512 said:
WAAS probably requires modifications to the host processing binary (SIRFHost)
BTW, our chip is a GSD4t, not 4e.
Click to expand...
Click to collapse
Good catch. Interesting. Haven't checked out the sources, but I'm assuming all the GPS binaries are blobs? And source is not available?
Always wondered why mobile phones never have WAAS support... course then again, if the hardware was developed in Korea, that would make a little bit of sense. Seeing as there isn't WAAS coverage there, although I do believe there is an alternate DGPS solution for Asia.
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