Related
I have a very low volume voice during calls. the volume of the phone is 100% but still you can't hear anything in public places.
I'm now using the speaker during calls...any help?
I've got the same problem does anone know what can I do??
I had this problem try this link: http://forum.xda-developers.com/showthread.php?t=429436
But using that method gives distortion to the sound, I am also having issues hearing who I´m talking with but it MUST be fixed by HTC either through update or getting a new device when they fix the problem.
But AudioPara3.zip has a bug
New AudioPara3.zip indeed turn the volume louder, but has a bug: the receiving call phone ring doesn't stop when turn Touch Pro face down as the original AudioPara3.zip does and the specifications annouce.
May be it's possible to contact the author of new AudioPara3.zip, I don´t know who is, and ask him to correct the bug.
Thanks very much.
cribeiro
Does it produce distortion with that program?
Although I love my TP I'm almost at the stage where I'm going to get rid of it....the volume during calls is pathetic..and despite all it's other features..it is afterall, supposed to be a phone. And if I can't use it for calls then it has just about no use to me.
I really fail to understand what these manafacturers do when they are testing a new device before its launch. Omission of such a basic problem only reflects as a disgrace to HTC. Hope this will be corrected through a ROM update. I have a diamond and I was seriously considering an upgrade to the Touch Pro. Now I will wait if and when this problem is corrected.
I can only sympthasize with those who own this device and are suffering the ignorance of HTc.
Regards
I'm not sure a ROM upgrade wil be able to do anything as from all the reading I've done, it's a hardware problem.
I've just spent an hour or so looking for alternative phones and sadly there's nothing that I would feel happy about buying...and nothing coming in the near future either...or does anyone know of anything?
The TP was for me the ultimate purchase, everything about it was perfect....until I discoverd I couldn't hear anyone on the phone!!
srmz said:
Hope this will be corrected through a ROM update.
Click to expand...
Click to collapse
You hope in vain.. I will quote:
"[..]However I can also see that these issues do not effect everyone, we have had a lot of good feedback regarding this device[..]"
So yes, HTC thinks that touch pro is close to perfection.
What should you all do? Contact and tell them about those problems, tell them that's a GENERAL ISSUE NOT A ONE DEVICE SPECIFIC ISSUE.
info AT htc DOT com
http://www.htc.com/www/about_htc_bymail.aspx
http://www.htc.com/europe/CS_Mail.aspx
http://www.htc.com/europe/CA_Hotline.aspx
Don't forget, this issue will not disappear/fix by itself. So if you care, then implicate yourself .
I am experiencing a very annoying problem with my Samsung Google Nexus S GT-i9023 (pearl white). Everything works fine except the NFC chip.
Every time, I try to turn on the NFC chip in the wireless menu, immediately the message "An error occurred" appears. So the NFC chip won`t turn on at all. No reboot, stock recovery (wipe internal storage etc.) could solve the issue.
Background information:
My Nexus S is 3 days old. It came out of the box with Android 2.3.3. I updated immediately after the first boot to 2.3.4 via OTA! I didn't check it with 2.3.3. Around the net are a lot of people experiencing the same(!) problem. No matter if it is a i9020 or a i9023. Also some people say, that it worked before with 2.3.3 and after updating to 2.3.4 NFC stopped working. I not able to verify this information.
Well meanwhile my Nexus S is at Samsung Germany service partner, called Bitronic Service Line. The guys called me some days ago, to inform me, that they don't know how to fix it. The placed an issue at Samsung Germany itself, so Bitronic is awaiting now reply from Samsung.
My question to xda-developers forum users:
Are you invovled in such a problem? Do you know a working fix? Probably sb. heard something about a defective production lot or maybe about udapting problems via OTA?
By the way, for more information, my and other Nexus S users story, can be read in the android forum. Just search via google for "Nexus S NFC error". It is issue nb. 13581. Sry but since I have only a few posts, the board rules does not allow me to post external links. Sry for that.
Attached a screenshot of the error msg.
Thx for information or any help.
Regards.
Same problem here. Sent my nexus s i9023 also to bitronic germany a week ago. Still waiting for a reply.
I tried alot ROM's (cyanogen, MIUI, nscolab etc.) and kernel's. Nothing helped. So I think this is a hardware problem.
According to a callback of Bitronic (Samsung Germany's contractual Service Partner), my problem could be identified as an hardware bug. They told me, that they replaced a specific part. Which exactly, I don't know.
I´ll get my phone back in around 2-3 days. Then I will post an final statement.
just got my nexus s back. everything is working properly again, so it was definitely a hw bug. From my side the problem is solved.
If someone is experiencing further problems with de- and activating the NFC chip, keep going on with reporting here.
Cool story bro.
Just kidding. Sending it out and getting it back in 2 days is pretty great turnaround. Sounds like quality service. Glad it got sorted.
Got my SNS back today. NFC is now working. Seems so that samsung has found the bug.
Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot
fix the a2dp on gb and i'll give you your first donation.
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..
Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.
So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium
ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?
No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?
I haven't seen anything posted anywhere is a while about the Galaxy S GPS issue and wondering if people are still having issues? I can not get any signal at all with the GPS (get maybe 2 satellites buddy on Verizon with a HTC gets his in 2 seconds) and have tried all the fixes out there. Is there one I'm overlooking or did people just give up on trying to fix it? I was also wondering if it was a phone issue with just my phone, and if I should take it back to T-Mobile to get a replacement (just got the phone 3 days ago).
I'm on 2.2.1, thanks!
No complaints here. With custom roms and even stock I haven't had any issues.
sent from the pits of hell (from an sgs4g)
mad_fitter said:
No complaints here. With custom roms and even stock I haven't had any issues.
Click to expand...
Click to collapse
hm... the woman at t-mobile yesterday when I stopped in to get a jacket said that her boss doesn't have an issue as well? Maybe I'll run it to t-mobile and see if they have an answer.
I had the same issue . it seems that it is a hardware issue. search the vibrant thread for GPS super fix. the copper contact in the phone has a poor contact with the gps antenna . simple fix . I than used GPS aids to rebuild the gps data folder and bam awesome results.
found it here.
http://forum.xda-developers.com/showthread.php?t=974702
elinca247 said:
I had the same issue . it seems that it is a hardware issue. search the vibrant thread for GPS super fix. the copper contact in the phone has a poor contact with the gps antenna . simple fix . I than used GPS aids to rebuild the gps data folder and bam awesome results.
found it here.
http://forum.xda-developers.com/showthread.php?t=974702
Click to expand...
Click to collapse
Thanks, looks like it would void the warranty? Plus I'm not that skilled at taking apart my stuff like that ha... I'll check into it though.
Not up on flashing and all that, do I have to root my phone first to use that GPS aids?
Yes to use GPS aids the phone needs to be rooted
Sent from my SGH-T959V using XDA Premium App
elinca247 said:
Yes to use GPS aids the phone needs to be rooted
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
What is rooting? Is it safe?
It most likely is the hardware issue. If I were you, it sounds like you just got the phone? I would exchange it.
It is a known issue with these phones. (sucks I know) but it only happened with my vibrant, not my sgs 4g yet......
Anyways, the hardware fix would technically void warrenty. But the good people at Samsung decided not to put any void stickers on the case of the device. So, unless you really messed something up when you did the hardware fix they would really never know....
I took it into T-Mobile and the guy factory reset it, seems to work well now? I noticed that quite a few things look very different like the Market and the Settings, think maybe I had a mix of some kinda old and new system which was screwing things up? Either way if it does it again the guy said he would replace the phone.
I guess the Sensation is not the first device to have this problem -
When using Fring, the front-facing camera shows my face as upside down to the other person , which means I have to rotate it 180 degs for them to see me right, which obviously means I get to see freaky people who's hair are defying gravity and who speak from their foreheads..
Anyways, I googled for solutions and found out that fring support apparently has an apk which has fixed this issue and they are sending it to people individually when they open a service ticket (no such luck at my end so far)...
But I thought it's worth throwing out here to see if anybody else has such an apk to share with all of us.
Thanks in advance,
mOrph
anybody with an apk? anybody at all??
I know this is a stupid question but have you tried reinstalling it?
Paging Dr B said:
I know this is a stupid question but have you tried reinstalling it?
Click to expand...
Click to collapse
Yes I did. Tried reinstalling. Having done a coupla hours of google searching, what I found out is Sensation isnt the first or only device to have this issue.
I finally heard back from Fring support. Here's what they had to say -
"Hello,
Thank you for contacting our support team.
Please note that the handset you are currently using is not officially supported by fring.
We are aware of the issue and working to solve it in the near future.
Make sure to check our blog for version updates http://www.fring.com/blog
Please feel free to contact us again should you have any further queries."
I am also having this problem, although I do have to say that is not just a problem with fring. I also have the same problem using the T-Mobile Qik video chat. I have seen fixes for the problem for other devices that would probably work, assuming I had a rooted phone...
Has anyone found a way to fix this without root??? This is the only thing wrong with my T-Mobile Sensation.
And please don't tell me to hold the phone upside down, that is not an acceptable solution.
Also it would be interesting to find out if there is anyone who doesn't have this problem. Considering this is the only thread about it, I'm beginning to think that this is a problem only on certain devices.
Tango works fine download that
I can confirm that Tango does work correctly, although the audio seems quite garbled. Hard to hear the other person, although they were on 3g at the time and not on WiFi.
Qik said they are working on an update to support the sensation.
So does the Sensation have an upside down front facing camera and just correct for it in the software? It seems weird that the video is upside down. I would understand having no video, as that could be a driver problem, or an interface problem.