My DHD has problems with the proximity sensor. I returned the device to the vodafone store (Netherlands), and they changed the device for a new one that worked.
Today, 1 day later, my second DHD is now having the exact same problem with the proximity sensor.
When I make a call, the screen immediately goes black, and the device no longer responds to any button (not even the power button on top). The ony way to get the device back to life is by removing and reinserting the battery.
Video of the problem
When I receive a call, the screen stays unlocked, even when the device is placed against my ear, so I end up with my ear pressing the active screen....
I've read more complaints about this exact problem on the tweakers.net forum. It is still unknown whether this is a hardware of software failure.
UPDATE
The problem seems to be related to the lightsensor, when holding a locked DHD in front of a bright light source, the device wil unlock (as long as you keep it in front of the light).
It might be, that when used in bright daylight a DHD will function properly.
Also, when calling using the headset, the problem does not occur. When inserting a headset in a "locked" DHD, it will wake up.
UPDATE2
Some facts, to "bust" some myths about the problem:
- It seems the problem can happen on all DHD's, not just devices with a particular S/N, software version, carrier (telco) or color.
- It has something to do with the light sensor (which is the same sensor as the proximity sensor) since the device unlocks when held in front of a bright lightsource, some users claim their device works well, as long as they are in daylight.
- The DHD uses a CM3602 proximity/light sensor, the same as a regular Desire
- The problem might not occur immediately after purchase, sometimes it takes a few days before it starts, thus switching your DHD for a new one might only solve your problem for a few hours/days (this is what happend to my second and third... yes third device)
Seems like the same kind of problem: http://forum.xda-developers.com/showthread.php?t=811282
Exactly the same post. Nice detail that I'm also a Dutch user bought it at a Vodafone store.
So, that's at least 3 devices reported with this problem.
Is there a way to turn off the proximity sensor? This would mean I have to turn the screen off manually when I make or receive a call, but that way, I don't have to reset the device every time I make a cell
Maybe you guys have found why it failed the google test ?
1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??
I wouldnt be very worried tbh, this is surely software related else they wouldnt release any batch of cellphones and delay the release for more than just a few weeks.
Can you make a Video and load it up on Youtube?
If we have a video it´s much easier to show HTC the problem... maybe we can load this video up on facebook to the HTC page...
Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Edit: Ah I see 2x LeonM1234 and 1x WizardX. Forget this post
liorra3 said:
1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??
Click to expand...
Click to collapse
Will try contacting HTC Netherlands tomorrow, today is Sunday...
name_th said:
Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Click to expand...
Click to collapse
This is my second DHD with this problem
P.S. Can any mod please remove the 1 post per 5 minutes limit, it is quite annoying... thanks!
A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D
HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
www . techeye.net / mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?
i think to cancel my DHD order until that issue will check.
Apache14 said:
A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D
Click to expand...
Click to collapse
the solution with the desire was an software update ?
Milini said:
HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
http://www.techeye.net/mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?
Click to expand...
Click to collapse
There you go proper link and welcome!
liorra3 said:
i think to cancel my DHD order until that issue will check.
the solution with the desire was an software update ?
Click to expand...
Click to collapse
Yep was solved with a S/W update
You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.
mach03 said:
You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.
Click to expand...
Click to collapse
Keep in mind, my device worked as it should the first day...
i don't understand how it can work fine one day and the following day it messes up lol
Apache14 said:
Yep was solved with a S/W update
Click to expand...
Click to collapse
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?
liorra3 said:
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?
Click to expand...
Click to collapse
s/w is software... you practically answered your own question
Related
Hi all,
I recently received a replacement Desire for my 'faulty' one. I tested all basic functions before walking away and everything checked out.
After I rooted it and installed Modaco r17 ROM, My proximity sensor sensitivity dropped dramatically. When I make or receive a call, the screen blanks as it should, but when I move the phone away from my face, it stays blank. I can't end the call or use speakerphone or keypad. The only way to bring the screen back is to hold it under a very bright indoor light, or direct sunlight...or pull the battery, of course.
I loaded a sensor test tool (SensorList) and it confirms that the sensor is reacting only to very bright light. I've checked that my cover doesn't obscure the sensor and tested that the behavior is the same with or without the screen protector.
I tried a couple of other ROMs, Modaco r19 and Shadowfrost v13. I un-rooted my phone and dropped a stock HTC ROM back onto it...and the problem is still there!
I'm waiting on a reply from HTC service about it...but in the meantime...any advice? I've seen a few posts around the web with this problem, but no definitive solutions or answers.
Question Added to Developers
I've noticed a smattering of people in various forums, with various of the newer android phones having proximity sensor problems. Perhaps these are not quite as finely calibrated as the other sensors, or not as reliable. Have any of you developers seen a way calibrating or adjusting the sensitivity? Perhaps a value in a system file we can change?
Thanks in advance.
Added question and bumped
Apols if this is pushy. I added a question to you developers, so giving this a bump.
phantomfisho said:
Apols if this is pushy. I added a question to you developers, so giving this a bump.
Click to expand...
Click to collapse
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Daelyn said:
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Click to expand...
Click to collapse
Images:
1. Holding hand over phone screen
2. Clear view of the screen in dimly lit room (it's quite cloudy )
3. While running FroYo
This does seem like Sensor List correctly detects and measures the proximity/light sensors in FroYo on an HTC Desire, or am I mistaken?
Ditto Issue
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
nayajoeun said:
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
Click to expand...
Click to collapse
Thanks John. I tried the same thing with the same result.
I ended up taking it in to HTC. Luckily I came across a good service rep. He said they'd seen some quality problems with the first batches of Desires and mine was not the first faulty proximity sensor they'd seen. My guess is the timing with the rooting was coincidental.
They would have replaced it, but they didn't have any replacement stock at the time...more evidence of early quality issues. They gave me priority and repaired it in 24 hours. It's been running fine under a number of ROMs since.
BTW I had problems de-rooting and reloading the stock ROM. Then I realised I just had to have the original goldcard in the phone and presto! One day I'll learn to RTFM properly.
Cheers mate and good luck with yours.
I have also this problem. When I make a phone call screen goes black immediately and there's nothing you can do. After the call is over I can wake up screen by pressing power button. I'm not sure when it started because there's been so many variables. I even destroyed my invisibleshield thinking it caused the problem.
Sensor list and sensor dump says that max value for proximity sensor is 1. Screenshots above there was at least 9. Also light sensor doesn't work at all.
I tried to unroot and go back stock but the problem still exist.
Have anybody found a way to control these sensors or do I have to send my phone to HTC to get it repaired?
Thanks in advance!
Hi, I have the same problem here with my proximity sensor since I have used a custom ROM (I don't remember wich one because I have tried so many Froyo ROM before the OTA).
I can't send my desire to HTC because my phone is out of waranty since I have installed all these ROMs.
Does anybody's got an idea, some help from devs ?
OK,
Maybe I'have found a solution to the proximity sensor's problem... At least my proximity sensor is working normaly now.
What I have done (you can found all in the xda posts) :
1. Going back to Hboot 0.80 => forum.xda-developers.com/showthread.php?t=741672
2. Rooting the desire and install the new recovery using unrevoked
3. Installing the OTA 2.2 without the Radio 5.09 (not a leedroid or djdroid or any other ROM, just a 2.2 rooted)
4. Configuring my phone
5. Installing the 5.09 Radio
I don't think that I have doing anything else, but now I can call someone even in the dark and my screen doesn't stay blank anymore !
Hope this could help someone.
Hi guys
i have a strange issue on my device,since stock ROM i guess, the problem is follows:
my screen just go black sometimes i thing it happend only when a call is in progress or when call is ended by the third part, the screen just stay black and no solution but uplug battery and start up the phone
i had this problem eaven on my stock Rom froyo 2.2, then i try leedroid 2.3 and it was ok i guess, then i try oxygen rc6 everything works superb,fast,clean,smooth but the black screen occures multiple times in one day (today around 3 times) so i was forced to return to my stock froyo 2.2 and hopes will be ok,
the problem is as i search thru internet... seems like one of the sensors works baddly, i think is the proximity sensor, what can i do? should i sent my device to repair? i realy appriciate any help and suggestions and ideas how can fix this problem....
still no solution it happens on stock froyo 2.2 too but in smaller period as on oxygen rc6, i try set --- display off to value 30 minute from previously 2 minutes and problem dont occured for last 2 days
this might seem like an ovbious answer but when your making a call the desire has a light/proximity sensor to the left of the top htc logo that turns the screen black when it senses something, this is to stop you pushing buttons with your ear.
i dont mean to insult your intelligence or anything, just saying ya know if it happens when not in a call it sounds like a software issue
i already know that, searchin a lot about this problem mate trust me, i also know when the proximity sensor is located and what is his function but the issue happening only when a call is made never happend just like that so i thing no sw prob, using stock froyo 2.2 now no root just a clean official and it happens like 2 times per day when i was calling more that 2 minutes when i set in setting--display to turn off screen in 10 minutes this problem dont show up soo i dont know realy maybe i sent my device to reklamation will see
This happens me with root and without root. It's when your using anything that has with the SD card to do with. Like the gallery, it has gone black for me to under a call though... I dont know how to fix this problem, and it's very frustrating to take out the battery all the time.
My friend i am working in mobiles but i couldn't guess the problem cause i bought my cousin this HTC desire until she removed the screen guard (( the plastic sticker for protect the screen)) from the screen and i solved the problem so easily.
Best of luck
true is that i am using Zagg shield, but this cannot solve the problem cuz i try few days without any screen protector and the problem was still there,
but i guess i solve this problem few months ago, i notice that the black screen after call happend when my network is set to "GSM only" strange but since i use WCDMA only the problem is gone, dont know surely but guessing, also when i use mobile network in gsm only mod, phone freezes totaly and only unplug battery helps, as i said since i am using wcdma/hsdpa/3g only non of these strange thing happens
hope this help for someone
AssassinSvK said:
true is that i am using Zagg shield, but this cannot solve the problem cuz i try few days without any screen protector and the problem was still there,
but i guess i solve this problem few months ago, i notice that the black screen after call happend when my network is set to "GSM only" strange but since i use WCDMA only the problem is gone, dont know surely but guessing, also when i use mobile network in gsm only mod, phone freezes totaly and only unplug battery helps, as i said since i am using wcdma/hsdpa/3g only non of these strange thing happens
hope this help for someone
Click to expand...
Click to collapse
Hi, guy!!
I've the same problem several months ago. Have you solved by using WCDMA only??
Thanks
Hi all,
This was happen to me last few day and i google whole world, finally i find my answer and i hope it was help for those who facing this kind of problem.
I can confirm this problem no related to rooted or without rooted phone. this problem definitely come from the proximity sensor which people highlighted this sensor located at top left of htc logo which u can see a blue color circle there.
Try watch this video of disassemble htc desire and you will find the way to clean this proximity sensor area.
Tools to use for dis-assembly:
1. Philips screw driver.
2. Torx screw driver
Cleaning tools:
1. a wet small cotton buds.
Hope this method can help.
Area to clean:
1. The proximity sensor which you will see covered by a black rubber
2. The casing area which i show on photo.
Disassembly Video:
youtube.com/watch?v=sXZqIjtFoAU
i231.photobucket.com/albums/ee126/nkh73925/untitled.jpg
I were unable to post due to spamming protection system from XDA. Please add urlsef the http.
I recently posted a thread on here about how my HD2's accelorometor no longer worked under android after being repaired. My thread was moved however but that is not the point the point is that after searching for several hours I have found a few threads about this problem and it seems that I am not alone!
My Thread: http://forum.xda-developers.com/showthread.php?t=1094479
Other thread: http://forum.xda-developers.com/showthread.php?t=999597
There are more but the one below mine seemed to be the best. It seems that this is a development issue so hopefully this thread will not be moved as my other one was as I've now done the research which I needed to comfirm this. It seems that a lot of warrenty repaired HD2's have this problem so as this is most likely a driver issue I would like to ask any dev that can to possibly look into the WM and or WP7 accelorometor drivers and see if there is any code for a second sensor and maybe if there is someone could look into incorporating it into our current android driver for future kernels. I am not a dev my self really, not in linux or android anyway. However I can provide logcats etc if needed.
As I said before please do not move this thread as devs do not go to Q&A and this is now a dev issue I think.
Any info or progress devs can give I will do my best to update the first post to help others.
I have just done an adb logcat from clean boot, to unlock then opening the bubble app and moving the device around for about 1 min and no change in app. It is attached below.
I have also done an adb dmesg which is also attached.
I hope someone can help all with this problem and thanks in advance to any devs which help.
Update 1: It seems that there is more than just the G-sensor which is different on these HD2's it also seems the light sensor and GPS are different!
Update 2: After trying the oldest 1.48 ROM for the HD2 it seems that HTC had planned the changes as all the hardware seems to work (minus the compass) in that ROM also with old SPL and Radio. Which I guess means that these other drivers must have been overlooked in the porting process...
Update 3: On trying it for myself it just seems that a GPS lock takes a really long time compared to other HD2's but it seems the GPS works. G-sensor still seems the most important thing to fix as many apps rely on it.
not denying the existance of the problem, but i would have thought that it was a damaged sensor (i have heard stories about hd2 accelerometers breaking for no good reason [probably a hardware defect]). There are only 2 hardware models arent there? International and TMOUS. I also thought that each model set used the same hardware across each model (ie no sort of Leo rev.2 with improved or different internals.
Of course i am probably wrong though
1 more thing. I had a Sony PSP repaired (a failed update so it bricked). They repaired it and when i got it back the UMD drive didnt work. So just to say that just becasue it cam back from a repair center doesnt mean they didnt break something else (although i expect htc take more care than sony)
joshman99 said:
not denying the existance of the problem, but i would have thought that it was a damaged sensor (i have heard stories about hd2 accelerometers breaking for no good reason [probably a hardware defect]). There are only 2 hardware models arent there? International and TMOUS. I also thought that each model set used the same hardware across each model (ie no sort of Leo rev.2 with improved or different internals.
Of course i am probably wrong though
1 more thing. I had a Sony PSP repaired (a failed update so it bricked). They repaired it and when i got it back the UMD drive didnt work. So just to say that just becasue it cam back from a repair center doesnt mean they didnt break something else (although i expect htc take more care than sony)
Click to expand...
Click to collapse
Well the sccelorometor works in Windows Mobile and Windows Phone 7 so I doubt it's a hardware issue. It's all in the links above... But thanks anyway.
Hello
I don't know if is about service. I bought my HD2 from Vodafone (brand new) and I can't use G-sensor and proximity sensor in Android. And I tried more then 20 versions (SD or NAND). In windows 6.1, 6.5, and 7, everything is perfect; in Android it's not working ... If you have a solution, please tell me ... G-sensor is not so important, but proximity sensor is ... Especially when I need two hands on keyboard ...
I also risk myself to ask them about this issue. The answer was: "if you already tried that, you lost your warranty ..." Point. Yeah, sure ...
ctzctz said:
Hello
I don't know if is about service. I bought my HD2 from Vodafone (brand new) and I can't use G-sensor and proximity sensor in Android. And I tried more then 20 versions (SD or NAND). In windows 6.1, 6.5, and 7, everything is perfect; in Android it's not working ... If you have a solution, please tell me ... G-sensor is not so important, but proximity sensor is ... Especially when I need two hands on keyboard ...
I also risk myself to ask them about this issue. The answer was: "if you already tried that, you lost your warranty ..." Point. Yeah, sure ...
Click to expand...
Click to collapse
I think u mean g-sensor for rotating the keyboard... but anyway regardless of what HTC has to say... which will never be good... this really needs to be looked into by someone familier with WinCE like cotulla was, as he was the one that reverse engineered these drivers in the first place but maybe he might have not reverse engineered the drivers for the different g-sensor and prox sensors possibly disgarding them as junk, as HTC as far as I know did used to leave drivers for other devices in builds. Or maybe when the prox and g-sensor drivers were being fixed later down the line the code was streamlined by removing them. Whatever the cause though or at whatever point they were lost at, they have been lost and we therefore need, with dev help, to look at the wince drivers again so maybe this can be fixed.
Hope this helps.
P.S. If anyone still has access to cotulla's early kernels, and early builds, pre-git merge with g-sensor support please post them so we can try them on effected HD2's. Thanks.
this is definitely kernel/driver issue. i am stucked at this problem for a while now. and no dev is trying to help. please someone do something. i bought hd2 just to enjoy different roms of android.
I don't think this is limited to the accelerometer. Before I received my replacement HD2, GPS worked fine, even in gingerbread I could get a fix. Now my replacement phone doesn't pick up or takes forever to see satellites. I Haven't tried it in WM but I suspect different hardware.
mr_dilly said:
I don't think this is limited to the accelerometer. Before I received my replacement HD2, GPS worked fine, even in gingerbread I could get a fix. Now my replacement phone doesn't pick up or takes forever to see satellites. I Haven't tried it in WM but I suspect different hardware.
Click to expand...
Click to collapse
I have noticed also that the light sensor doesn't work in WP7 and I think it was also the same in android! I don't really use gps but I might try it to test. Btw what are you running on your HD2? You should try running older WM ROM's on your phone and see if things work. Because if they don't maybe would could convince HTC to replace our phones... Although they've likely included the new drivers in the 3.xx ROM's so that wouldn't really fix anything. However with dev help we really need to look into the drivers in WinMo and see what the new hardware is. After all if HTC has changed hardware due to it being more available maybe the new hardware is also present in some of their android devices... And if this is the case then it would be pretty easy to fix although this is just speculation but without some help I can't really make it more.
Also does anyone know of any app which can list what hardware is in a Windows Mobile device? If there were this would really be useful.
Thanks.
I spent the day flashing some roms and radios, and got different results. In WM, I do pick up satellites a little faster, this improved with an older radio 2.12. In android I eventually saw satellites, again this improved with radio 2.12. I tested against another HD2 both running Hyperdroid CM7 2.0.1; the signal was a lot weaker and I picked up fewer satellites total. This may be due to different/older hardware I'm not sure.
There was an app in the market which told you what hardware your phone was running but I can't remember the name of the app or if it said what version. I hope this info helps.
http://forum.xda-developers.com/showthread.php?t=1049170
looks like the devs are already in the works of fixing the g-sensor missing drivers/code
and will most likely be implemented in next builds/kernels...
btw i lost my hd2 recently.. a brand new one was sent to me thru the insurance company.. after installing an android nand rom i notice the screen auto-rotation wasnt working.. fashed WP7 and everything was fine.. so yea its for sure a driver related issue all we can do is wait for all these great devs to cook a new kernel with a fix...
With Phone Tester (by Miguel Torres) you can get good info about sensors and etc.
Also Phone Explorer (by Dave Truby)
Sorry this is not spam to advertise app. Just wanted itself know have difference on hardware on my two phones.
I have old and many many times asked and short or longer discussed light and proximity sensor problem. With last two roms, it started work little better. But lighting phone with some sharp light after call is very displeasing.
datas0ft said:
With Phone Tester (by Miguel Torres) you can get good info about sensors and etc.
Also Phone Explorer (by Dave Truby)
Sorry this is not spam to advertise app. Just wanted itself know have difference on hardware on my two phones.
I have old and many many times asked and short or longer discussed light and proximity sensor problem. With last two roms, it started work little better. But lighting phone with some sharp light after call is very displeasing.
Click to expand...
Click to collapse
Hi, all help is good I guess. Anyway are these WinMo or Android apps? Since if their Android due to the kernel problem it may give false reports but either way I'm interested in whether the results you got are different on the two HD2's?
P.S. I hope some kernel devs can help me with this soon as I haven't heard from any yet but wish to.
Me too. G sensor works only in WM, and in Android It doesn't work.
nhoc_tron36 said:
Me too. G sensor works only in WM, and in Android It doesn't work.
Click to expand...
Click to collapse
The drivers are written for and debugged using the hardware present in the device of the developer. ie. Cotulla prioritized the LEO100 a.k.a EU HD2 as he dint have the TMOUS version.
Well this is a leading problem in linux support, the drivers are available only for hardware which is used/produced/supported by good devs.
The only thing you could do here is check with kernel and android logs what happens when those specific hardware are switched on and/or accessed.
Google is your best friend. who knows you might just become jr.Cotulla trying to fix your Hardware problem.
Well, i started by fixing my Harddisk's MBR back in 1995 (god, those ol days. cant forget DOS, and 512MB HDD) and today im a Microsoft MVP
I get this issue too...
I have Euro HD2 on android... with WM everything was... hum I can't say "fine" ^^ but it was working anyway!
Yes, these two previously named apps are android. On winmo i dont had problems with proximity sensor. I didnt changed anything and moved to android. Then started these proximity sensor problems. And now i can assuredly say that it is proximity sensor side problem. Phone tester shows all time status "Near". When i give more light to phone then it shows "Far".
I ordered new flex cable ribbon which one have proximity and light sensor. It arrives at week or more. Then i can assuredly say is it broken proximity sensor or drivers (kernel) side problem. I opened my phone many times and cleaned sensor too, that some dust cant be problem.
Proximity sensor info:
Name: CM3602 Proximity sensor
Vendor: Capella Microsystems
Version: 1
Power: 0.5
Resolution: 9.0
Max Range: 9.0
Centimeters: 0
If someone needs or want some other info or test i can give or do it.
any update to this as I am experiencing the same problem on one of my HD2s. I realize its an old thread but maybe someone has results.
Devs help needed!
Still hope devs will see this
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
wave1990 said:
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
Click to expand...
Click to collapse
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Protonus said:
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Click to expand...
Click to collapse
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
wave1990 said:
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
Click to expand...
Click to collapse
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Protonus said:
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Click to expand...
Click to collapse
I do not know if you develop .... but you could create a fix that recalibrates the driver every tap on the screen!
is an idea =)
Hi,
I just received my HTC One X today as an upgrade from T-Mobile. I've been waiting to get my hands on this for ages like most of you so you would most likely know how I feel when its not how you expected i.e things going wrong/not working etc.
THE PROBLEM:
The problem seems to be that when I am on a call using the speaker mode, the mic does not seem to work, therefore the person on the other side cannot hear me. I tested it again myself and it seems as if the mic mutes itself when you press the speaker mode in a call. You are still able to hear the other person yet they cannot hear you.
However when I am not in speaker mode, everything works as normal so I am wondering is this a software fault or hardware fault.
Please get back to me as soon as, as I really do not want to return the phone and go through the dreaded process.
Thank you for reading.
P.S
My HTC One X:
Software Version: 1.26.110.5
HTC SDK: 4.11
(As i am on Tmobile, My HOX is branded therefore has not received latest update)
I have the exact same problem, I bought the phone about a month ago, and I didn't check the speaker mode function, then I flash few different custom rom, Now I found the speaker mode problem as tkr1992 has, since I unlock the bootloader (although I relock the bootloader) but HTC won't repair the phone free of charge for me, they say the phone need a new mainbroad... will cost me 2XX USD,
I don't even know is the phone has this problem when I first bought it or after I flash some custom rom.
HtC told me it should be software problem cos it is the same mic that use in speaker mode or non speaker mode, so when other side can hear you when you not on speaker mode, mean the mic is alright, BUT they told me it need to replace the mainboard cos I have unlock the bootloader so they can't not recover the phone to stock rom, BUT again I already relock the bootloader and RUU the stock rom back to the phone, still the same problem.
I need help too, Any good fellow can help??????????
I hope it is just a software fault. I did just receive an update today from T-Mobile, as my HOX is branded. The update is 1.28.110.7. It still seems that my mic problem is present.
Does anyone also know what fixes are included in this update?
Thanks
Any ideas anyone? Would really like to fix this instead of sending phone back to tmobile.
Thanks
Sent from my GT-P7510 using XDA Premium HD app
this is what got from HTC
Regarding to your inquiry about HTC One X, we would like to provide you with following advice and solution as below: First you can diagnosis the hardware issue on the speaker. Please kindly type *#*#3424#*#* on the dial screen, you will enable the function test program. And then select "Audio Test", tap Run. Please finish the test as instructions.
But it didn't work for me the phone just didn't do anything, you can try.
Thanks for that, i just tried the audio test diagnosis. The test shows that everything is working correctly however the same problem still occurs within a call like before.
Sent from my GT-P7510 using XDA Premium HD app
Try reset to factory setting, see if it does any different.
That is the HTC guy try to do to my one x.
btw have you rooted your phone or unlocked the downloader?
You have working Navigation application in background and this make call routing first to speaker part permanently, not to earphone - like phone is in Handsfree mode. Try to disable it / shut down it / and all be fine.
WBR, DebeliaMark, Bulgaria
tkr1992 said:
Hi,
I just received my HTC One X today as an upgrade from T-Mobile. I've been waiting to get my hands on this for ages like most of you so you would most likely know how I feel when its not how you expected i.e things going wrong/not working etc.
THE PROBLEM:
The problem seems to be that when I am on a call using the speaker mode, the mic does not seem to work, therefore the person on the other side cannot hear me. I tested it again myself and it seems as if the mic mutes itself when you press the speaker mode in a call. You are still able to hear the other person yet they cannot hear you.
However when I am not in speaker mode, everything works as normal so I am wondering is this a software fault or hardware fault.
Please get back to me as soon as, as I really do not want to return the phone and go through the dreaded process.
Thank you for reading.
P.S
My HTC One X:
Software Version: 1.26.110.5
HTC SDK: 4.11
(As i am on Tmobile, My HOX is branded therefore has not received latest update)
Click to expand...
Click to collapse
Mic Problem whilst in Speaker mode in a call
Hi All
I have the same problem after software upgrade two months ago
and did not have a time to try to fix it
I thought after factory reset it will work, but finally it did not help
My phone was never rooted
Uninstalled any navigation software
Tried the audio test diagnosis.(the test shows that everything is working correctly)
If someone have any solution it will be more then welcomed
Thanks
HTC One X Locked S-ON RL
Software Version: 1.29.401.11
HTC SDK 4.12
HBOOT-0.95.0000
RADIO-1.1204.105.14
yesss please someone help! mine started acting crazy today after work. i called my friend around 5.40 then about an hr later i made another call and they couldnt hear me but i thought it was just their phone. since then ive made about 5 calls to 2 diff people and they both cant hear me ... i havent tried factory reset or the navigation yet because my phone isnt backed up yet but please please please someone help
anyone get a solution to this?
romy134 said:
anyone get a solution to this?
Click to expand...
Click to collapse
I'm experiencing this exact issue as well - has anyone come up with any possible solutions?
There are 2 microphones on this phone, the upper one next to the headset jack and the other next to the lower right corner of the screen.
While on phone mode the lower one is the main microphone because its closer to your mouth, on speaker mode the upper one becomes the main mic.
It's probably a hardware fault since you flashed stock rom and it's still not working.
I seem to have this issue too - did anyone get a solution
Audio tests fine, but in Google Talk, or Google Hangout, or Phone Dialer in speaker mode - the mic input is not working, so recipient cannot hear.
Google Maps Issue
So my wife has the same phone (HTC One X) and has the most recent update to 4.0.4 (stock everything) and found out that it is indeed either the google 'navigation' app, or the google 'maps' app running in the background that will give this problem. Simply go to settings, then apps, then stop the maps or navigation process, make sure you go to the cached processes as well and stop those. Right after that her phone started working again. I also tested with the HTC test tool code that was given earlier and just like everyone else the test passed fine. So this should be the fix.
i have the same issue..
.. since updating my HOX to 3.18.401.1 and can confirm that disabling the google maps service solves the issue (at least for now)...
Anyway i have to admit that thos workaround doesn´t make me happy at all, a phone without google maps is a pain in the ......
Update: Nope .... it worked for the first 2 calls, now silence again.....Did already 3 factory resets....no idea anymore, i think i gonna sned it in to HTC...
Hello,
I have the same problem and many users "HOX" have the same worries. It seems that when you change the screen touch there is a lot of trouble of this kind.
Does anyone find a solution?
error23 said:
.. since updating my HOX to 3.18.401.1 and can confirm that disabling the google maps service solves the issue (at least for now)...
Anyway i have to admit that thos workaround doesn´t make me happy at all, a phone without google maps is a pain in the ......
Update: Nope .... it worked for the first 2 calls, now silence again.....Did already 3 factory resets....no idea anymore, i think i gonna sned it in to HTC...
Click to expand...
Click to collapse
Any update on this? Did you send it to HTC? Mine has also stopped suddenly a few days back while on viper 3.7.2. Tried factory reset, flashed the rom again, flashed other roms, but the problem is still there...
in may case it was a defective mainboard....
I had to send in my HOX 3 times to HTC repair until they (and me) figured out it was a Mainboard problem.
The first 2 repair attempts where quite strange, because they changed some parts which have absolutely nothing to do with the MIC and when i received it the problem was still here, but anyway
I came to the final diagnosis, because after turning the HOX on, it was working for some calls, then the MIC suddenly stopped...Getting more and more angry because of sending the phone in and receiving it 3 weeks later unrepaired, i once squeezed my HOX really hard during a "silent" phonecall and while squeezing it (on both lower edges) the MIC worked again.
After that experience all was clear, because this behaviour is typical for a hairline crack on the PCB. I wrote this on the RMA form and they exchanged the Mainboard....
So, finally i have my HOX again for 4 weeks now (after almost 2 1/2 months without it) and it works flawlessly....
So, good luck guys and a lot of patience
error23 said:
I had to send in my HOX 3 times to HTC repair until they (and me) figured out it was a Mainboard problem.
The first 2 repair attempts where quite strange, because they changed some parts which have absolutely nothing to do with the MIC and when i received it the problem was still here, but anyway
I came to the final diagnosis, because after turning the HOX on, it was working for some calls, then the MIC suddenly stopped...Getting more and more angry because of sending the phone in and receiving it 3 weeks later unrepaired, i once squeezed my HOX really hard during a "silent" phonecall and while squeezing it (on both lower edges) the MIC worked again.
After that experience all was clear, because this behaviour is typical for a hairline crack on the PCB. I wrote this on the RMA form and they exchanged the Mainboard....
So, finally i have my HOX again for 4 weeks now (after almost 2 1/2 months without it) and it works flawlessly....
So, good luck guys and a lot of patience
Click to expand...
Click to collapse
Thanks for your input mate. Was your bootloader unlocked? Did the warranty cover that?
Sent from my HTC One X using Tapatalk 2