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.
Just did the update, Not really wanting to post, did a quick search and found nothing, But the 2.2 OTA update appears to have broken the camera...
The default app opens and cloes, and others just sit with a black screen
That's weird. I just done my update 2 hour ago. But seems like everything works fine.
Fine with mine.
I even tested the 720p.
Try to manually reboot your phone.
I got issue with app list and fixed with reboot. Probably this one too.
Also check your SD card.
Yea I havent read anyone else having this problem so its annoying, I was planning on doing a sidew by side comparrison with the 2.2 and 2.1 versions.
Same problem here...
RESTART your Desire, it's fixed most peoples cameras.
you should do it with goldcard inside... your radio hasn't been able to update properly
jpxdude said:
RESTART your Desire, it's fixed most peoples cameras.
Click to expand...
Click to collapse
Tried that didn't work
djoni1980 said:
you should do it with goldcard inside... your radio hasn't been able to update properly
Click to expand...
Click to collapse
I shouldnt have to use a gold card.
Only way I tried to make it run,was playing with the task killer and killing footprints,gallery and cam apps.
Then it runs,but that's not a solution...
I've got the same problem, just opens and then closes. Tried reboot but it didn't help.
BRAVO PVT1 SHIP S-ON
HBOOT0.92.0001
MICROP-031d
TOUCH PANEL-SYNW0101
Radio-5.09.00.20
Thats the info from the recovery section
Bouncer5 said:
I shouldnt have to use a gold card.
Click to expand...
Click to collapse
well you're on orange, aren't you?
No goldcard = no camera
My camera isn't working either, a friend of mine with the same phone and same provider (vodafone) has got his camera working with no problems at all.
Same here, camera dead. Rebooting didn't help.
EDIT: Started task killer, killed everything (including camera, it was listed). Now it works.
A note to everyone with problems - I have done some testing and the problems seems to be some unresolved compatibility issues migrating from the old android os to the new one. Things seem to be fixed for some people by restarting however in some cases a factory reset is required. Most settings will be maintained in this however user dictionary, security and data settings may be lost. Other app based settings will also be lost, but so far it seems to be the sure fire method to resolve the problem.
Also note that the problem has been filed with HTC and we are waiting for a response.
Camera is working again, out of nowhere!
+1 - stock unbranded desire. Camera now fails, reboot doesn't help.
Task killing a bunch of apps lets you start the camera - but this does not survive a reboot.
Moving apps to the SD card in App Manager also re-enables the camera for some reason but again this does not survive a reboot.
Need a fix for this pdq!
OK - have a fix that works for me. Killed all tasks one by one and tested camera to find culprit:
LED Light Widget 1.0.9
Uninstalled this and camera working normally even after reboot.
Mark One said:
OK - have a fix that works for me. Killed all tasks one by one and tested camera to find culprit:
LED Light Widget 1.0.9
Uninstalled this and camera working normally even after reboot.
Click to expand...
Click to collapse
Nice, work's!!! TY
np - glad it works for you too.
I love the DINC2 so far, but one thing that I wish I could change is the softkey brightness.
Are they supposed to be always on? Even with the clock in night mode?
I tried LED hacks and a few other brightness control apps, but no luck so far.
Does anyone know of an app that can dim/turn off the softkey backlight?
siskiou said:
I love the DINC2 so far, but one thing that I wish I could change is the softkey brightness.
Are they supposed to be always on? Even with the clock in night mode?
I tried LED hacks and a few other brightness control apps, but no luck so far.
Does anyone know of an app that can dim/turn off the softkey backlight?
Click to expand...
Click to collapse
LOL just flash virtuous 2.35 softkeys don't work, but everything else does. No softkeys lighting up is not all that bad.
Sent from my ADR6350 using XDA App
That's an idea! *g*
If I get desperate and there are no other solutions, I might try it.
Does global mode work with virtuous?
Nope
Sent from my rooted GB ADR6350
Well, so much for that!
Thanks for letting me know.
what rom are you running? stock? on cyanogen mod the softkeys go out on night mode in the clock app.
Right now I'm running the debloated stock, but am thinking of skyraider zeus.
Had it on there yesterday, but then lost mobile service after unlocking the SIM, and decided to try the stock rom. Service came back, and now I'm chicken to try flashing again.
Does global mode work with cyanogen? I will use this phone in Europe later this year and want a stable rom with working global.
siskiou said:
Right now I'm running the debloated stock, but am thinking of skyraider zeus.
Had it on there yesterday, but then lost mobile service after unlocking the SIM, and decided to try the stock rom. Service came back, and now I'm chicken to try flashing again.
Does global mode work with cyanogen? I will use this phone in Europe later this year and want a stable rom with working global.
Click to expand...
Click to collapse
According to post #18 SkyRaider Zeus does work in global mode. I haven't tested it, but I have been running SkyRaider Zeus for about a week now and I love it.
Yep, that's part of the reason I want to use it, but I'd like it even better if it had softkey backlight control, too. I guess I will have to risk flashing and seeing what happens with the softkeys.
When I ran it yesterday, it was bright daylight, and I only noticed how annoying the backlit keys were later that night, when the phone was running debloated stock.
There's no risk flashing most stable roms from the dev section. Make sure you have a working backup of your current rom and you're good to flash new ones. I had an issue trying to mess with global mode on my phone once and it required me to do a restore of a working backup I had then all was fine again.
Also in the cm7 thread this post confirmed working global mode recently. http://forum.xda-developers.com/showthread.php?p=17245922
Sent from my Incredible 2 using Tapatalk
Thanks for the info!
When I ran into the no service problem after unlocking the Sim, I restored via cwm, but nothing
worked. Got an endless 'loading, this can take several minutes. Please wait.
This was the backup of the stock ROM, though.
Sent from my ADR6350 using XDA App
if you had issues restoring a backup in clockwork then it wouldnt have been because you unlocked the sim card. sounds like you had a corrupt backup or something went wrong with the backup you were trying to restore. but out of curiosity, how long did you let it try to restore before you gave up?
The restore went through successfully, according to CWM, but when the phone restarted, I was stuck with: Loading! It can take several minutes. Please wait.
I waited for an hour, and then flashed the debloated ROM.
What happened after the SIM unlock (I was running Skyraider Zeus at the time), was that I lost my mobile service.
I am sorry to hear you are having problems. I hope you didn't lose any data. I run cm7 nightlies. I have heard that cm7 supports global mode. I also use an app called "Screen Filter". When I was unrooted/stock, the app would not turn off my softkey backlight (there is an option to enable or disable softkey backlight), but on cm7, the feature works. I have two widgets, one set at 46.8% without softkey backlight, and one set at 97.8%, also without softkey backlight. The second one barely dims the screen, and turns the softkey backlight off. And best of all, with cm7 I am able to assign one of them to long press search key, so I can turn off the softkey lights from anywhere. I have not tested it, but there is a chance this could work on a rooted sense rom (the screen filter setting). I know it works on cm7 though.
Also, with cm7 you can control the brightness of the softkeys (if you only want to dim them) if you customize the auto-brightness (the setting is built into the rom), but then you have to use auto-brightness (I do that as well).
Hope that helped!
DalekCaan said:
I have heard that cm7 supports global mode. I also use an app called "Screen Filter". When I was unrooted/stock, the app would not turn off my softkey backlight (there is an option to enable or disable softkey backlight), but on cm7, the feature works.
Click to expand...
Click to collapse
Thank you!
You don't know how happy it makes me to hear that cm7 does global and screen filter works with the softkey backlight!
I'm a big fan of Screen Filter, anyhow.
Can you tell me where I can find the latest stable version of cm7 to try out? Or do I need to grab a nightly?
Any ideas on battery use, and signal strength with cm7? I have pretty horrible signal strength with the debloated stock rom, though it was no better with the unrooted stock.
siskiou said:
Thank you!
You don't know how happy it makes me to hear that cm7 does global and screen filter works with the softkey backlight!
I'm a big fan of Screen Filter, anyhow.
Can you tell me where I can find the latest stable version of cm7 to try out? Or do I need to grab a nightly?
Any ideas on battery use, and signal strength with cm7? I have pretty horrible signal strength with the debloated stock rom, though it was no better with the unrooted stock.
Click to expand...
Click to collapse
There is no stable version yet, but here is the link for the nightlies:
http://forum.xda-developers.com/showthread.php?t=1156343
I find them stable enough for daily use. I have used WiFi, GPS, Bluetooth, 3G, Tethering, SMS and MMS with Handcent, etc. and have never had any problems (other than the compass issue with AOSP, which I really don't mind, as it's fine when I'm moving).
There is also a beta:
http://forum.xda-developers.com/showthread.php?t=1153261
if you don't want to deal with nightlies. I haven't used it, but I have heard it's good enough for daily use.
I do have pretty bad signal strength with this rom, however I have always had bad signal strength and have never dropped a call/had to resend a message. At best I can get around -80 dbm, but usually I'm around -90.
My battery use has been okay. Not 72 hours like some people report (I don't see how that's possible with any rom), but with ~2 hours of screen on time, I'm usually just below 50% at the end of the day. So I charge every night, but I never worry about making it through a day. I use the Tiamat kernel because without it the speaker on calls is too low for me, but another benefit is that Tiamat includes the smartass governor, which is supposed to help battery life.
Thanks again!
I'll check out cm7.
Yes! It works!
I have the latest nightly and screen filter controls the backlight!
Thanks a million, and also for mentioning the long press option.
Now I use that for turning off the soft keys when reading. Much nicer than having to go back to the home screen.
Get it? The title is a Star Wars reference. As in developers are Jedi? Like in the movie? Nevermind.
I have been having a strange audio bug recently. I flashed RC Mix Runny v1.0 through to v1.4 and each subsequent ROM version did exactly what it should. No issues that weren't listed on the thread.
Then I flashed Runny v1.5, followed by (after the ROM had booted twice) a theme I made on UOT Kitchen. A few days afterwards, when making a phone call, I couldn't hear the phone ringing through the phone's speaker. Nothing. That's the bug.
This only applies to phone calls (or at least the speaker normally used for phone calls). When I select 'speaker phone' the rear speaker kicks in and I can hear the phone call just fine, though a little loud when walking around in public.
The headset also works perfectly.
I flashed RCMix3d 3.5 v1.0 today - no themes this time in case it was the cause last time. The ROM boots up just fine, everything seems perfect but when I go to make a phone call the same bug presents itself. Meaning it's most likely a bug I have caused, not a bug in a ROM.
But what did I do?! Has anyone heard of this behavior before? Could it be radio/RIL related?
If anyone can shed a little light, I would appreciate it greatly.
Max-E-Moose said:
Get it? The title is a Star Wars reference. As in developers are Jedi? Like in the movie? Nevermind.
I have been having a strange audio bug recently. I flashed RC Mix Runny v1.0 through to v1.4 and each subsequent ROM version did exactly what it should. No issues that weren't listed on the thread.
Then I flashed Runny v1.5, followed by (after the ROM had booted twice) a theme I made on UOT Kitchen. A few days afterwards, when making a phone call, I couldn't hear the phone ringing through the phone's speaker. Nothing. That's the bug.
This only applies to phone calls (or at least the speaker normally used for phone calls). When I select 'speaker phone' the rear speaker kicks in and I can hear the phone call just fine, though a little loud when walking around in public.
The headset also works perfectly.
I flashed RCMix3d 3.5 v1.0 today - no themes this time in case it was the cause last time. The ROM boots up just fine, everything seems perfect but when I go to make a phone call the same bug presents itself. Meaning it's most likely a bug I have caused, not a bug in a ROM.
But what did I do?! Has anyone heard of this behavior before? Could it be radio/RIL related?
If anyone can shed a little light, I would appreciate it greatly.
Click to expand...
Click to collapse
Please search before opening a new post as I have seen this pop up alot the past few days with that rom. I would look in the roms thread
I will search more thoroughly. Apologies for any infraction.
Cheers for pointing the way.
Max-E-Moose said:
I will search more thoroughly. Apologies for any infraction.
Cheers for pointing the way.
Click to expand...
Click to collapse
While you are searching for hours for a solution, download a different ROM (other than RCMix) and find out if it is really a bug or some hardware issue. And while you wait for the download and flash, keep searching
hohinder said:
While you are searching for hours for a solution, download a different ROM (other than RCMix) and find out if it is really a bug or some hardware issue. And while you wait for the download and flash, keep searching
Click to expand...
Click to collapse
Thanks for your advice. I heeded it!
I flashed Black Ice [AOSP] to see if it was still persisting. It is.
Seems like it's a hardware problem. I was hoping it wasn't. I didn't want to have to pay to fix it!
Ta for the help!
try changing the radio or kernel see if it helps
SOLVED
NOT SOLVED
rakinisbat said:
try changing the radio or kernel see if it helps
Click to expand...
Click to collapse
I was holding back on changing the radio because I don't like higher risk of bricking. Having done it in the past though, I said it was worth a shot before I blame the hardware entirely and hand over money to fix it.
I had been using radio 26.09.04.11 and it's matching RIL with every ROM I tried.
Once changed to radio 26.13.04.19_M and it's corresponding RIL and the problem was erased. I can hear phone calls on the phone speaker again. (Like normal folk!)
Thanks for the push rakinisbat, I needed it!
Edit: NOT SOLVED. The problem has re-surfaced. I have made absolutely no changes to the system since it started working. I am now going to pay someone to take a look and will report back with results.
Definitely not solved.
This problem with the receiver not working has not gone away.
I have tried ignoring it for the last while and just using the speakerphone on a low volume - not ideal but workable.
A few days ago I changed ROM - curious to try out ICS. I load up the new ROM and a while later, accidentally forgot to put a call I was making onto speakerphone and suddenly the receiver is working again - JOY!
Now, two days later, the receiver is not working again.
I have pry tools now and would happily change the receiver, but this recurring trend of it working for a spell after a new ROM is flashed leads me to believe this is more software related than hardware.
If anyone has ANY ideas or thinks they could help (if I provide a logcat to them or something) then please PM me or respond to this thread.
Everything works fine for me...never experienced this .....check your audio settings....and why you running such an old version??
Sent from my Desire HD using xda premium
harshrocsu;20112881why you running such an old version??[/QUOTE said:
The last time I changed to that radio, my audio bug was fixed (temporarily).
I will update to the new radio (12.65.60.29_26.14.04.28) I saw mentioned a few days ago and see if it changes anything - though I doubt it.
I have done a fair bit of research on this and it is not as uncommon as I thought it was a few months ago. It seems to have happened to the HTC Desire, Desire S and Desire HD - but not en mass. In every case, the phone was working fine, then came intermittent receiver audio, then receiver audio gone altogether.
I have not heard of one working solution, though I have had some helpful people lend an ear!
Click to expand...
Click to collapse
You say the problem is solved for a while when you flash a new ROM. Is there a possibility that a certain app that you install/restore that maybe messes with the speaker?
Just a thought..
if4ct0r said:
You say the problem is solved for a while when you flash a new ROM. Is there a possibility that a certain app that you install/restore that maybe messes with the speaker?
Just a thought..
Click to expand...
Click to collapse
An avenue I had not gone down. I have been restoring mostly the same apps for ages.
Thanks for the idea. I will do a backup and then a fresh install tomorrow (I'm at work) and check. Will report back afterwards.
Ongoing audio issue
I have fully wiped the phone and re-installed a ROM twice now (ICS both times, I know this problem acts the same with GB). I didn't install any apps for a while and had audio in the receiver for phone calls.
The first time I wiped it, I had audio back so decided to install apps from the market - one at a time and test the receiver by ringing the house number after each is installed. I got distracted (it was late) and when I next picked up the phone, audio was gone.
Second attempt, this time stay vigilant. I fully wiped the phone, installed a ROM, and got to work on installing the apps again. I installed a few apps, which I will list here, and audio disappears again.
Installed apps:-
Dictionary.com
Dropbox
Earth
Es File Explorer
Facebook
Goggles (I dunno why, the camera isn't even working - habit maybe)
Google Sky Map
Google+
Messenger
Moon+ Reader Pro
MX Video Player
Streetview For Google Maps
Sugarsync
Tumblr
Twitter
XDA
To my knowledge, apart from MX Video Player, none of the rest these apps should have any effect on the audio.
Today I am going to wipe it and not install any apps for the next 24-48 hours and see if the audio still disappears.
Tune in next time to see if the problem makes my brain crack in two.
Max-E-Moose said:
I have fully wiped the phone and re-installed a ROM twice now (ICS both times, I know this problem acts the same with GB). I didn't install any apps for a while and had audio in the receiver for phone calls.
The first time I wiped it, I had audio back so decided to install apps from the market - one at a time and test the receiver by ringing the house number after each is installed. I got distracted (it was late) and when I next picked up the phone, audio was gone.
Second attempt, this time stay vigilant. I fully wiped the phone, installed a ROM, and got to work on installing the apps again. I installed a few apps, which I will list here, and audio disappears again.
Installed apps:-
Dictionary.com
Dropbox
Earth
Es File Explorer
Facebook
Goggles (I dunno why, the camera isn't even working - habit maybe)
Google Sky Map
Google+
Messenger
Moon+ Reader Pro
MX Video Player
Streetview For Google Maps
Sugarsync
Tumblr
Twitter
XDA
To my knowledge, apart from MX Video Player, none of the rest these apps should have any effect on the audio.
Today I am going to wipe it and not install any apps for the next 24-48 hours and see if the audio still disappears.
Tune in next time to see if the problem makes my brain crack in two.
Click to expand...
Click to collapse
I had exactly the same issue. After rooting my desire HD I installed ARHD 6.3.1 and it was working very fine until I installed the ICE HD theme for ARHD 6.3.1. Sorry, no disrespect to the theme author but I was not able to hear anything through Phone speakers after installing this theme. This is what I did to solve this issue,
1- Use Superwipe to clear everything using ClockworkMod recovery.
2- Install the STOCK 1.32 PD98IMG.zip from here. Put it in your SD card, Flash is using the HTC Stock Recovery (It will detect it automatically). Remember that the Kernel and Radio are inside this ZIP file so you need not to install anything else.
That's it. you are back to old stock ROM and now you must be able to hear you phone speakers. If not, switch off your phone for few hours and then turn on. (I know switching off and on sounds silly but it worked for me). You can install any custom ROM after that rooting again.
kaydee7902 said:
I had exactly the same issue. After rooting my desire HD I installed ARHD 6.3.1 and it was working very fine until I installed the ICE HD theme for ARHD 6.3.1. Sorry, no disrespect to the theme author but I was not able to hear anything through Phone speakers after installing this theme. This is what I did to solve this issue,
1- Use Superwipe to clear everything using ClockworkMod recovery.
2- Install the STOCK 1.32 PD98IMG.zip from here. Put it in your SD card, Flash is using the HTC Stock Recovery (It will detect it automatically). Remember that the Kernel and Radio are inside this ZIP file so you need not to install anything else.
That's it. you are back to old stock ROM and now you must be able to hear you phone speakers. If not, switch off your phone for few hours and then turn on. (I know switching off and on sounds silly but it worked for me). You can install any custom ROM after that rooting again.
Click to expand...
Click to collapse
Thanks so much for getting on to me, I have been hoping that someone out there solved this issue and might read this little thread!
I will be following your advice today and will report back.
Solution seems good so far!
I'm not going to jump the gun again and say that it is definitely solved but my audio came back!
I did what you said, reverted everything back to stock. When it loaded up Froyo and for the first while, the receiver wasn't working. I set about rooting, Radio S-Off, ENG S-Off, adding CWM etc.
About three hours later (I didn't actually leave the phone off, I reset it a lot though) the audio returned to the receiver!
I'm delighted but remain skeptical as it has come back to life and then died again so many times before.
I want to believe!!!... So I remain hopeful. Time will tell.
It fixed itself...(!)
See post below
Absolutely positively finally fixed.
Thanks to everyone for their help in trying to solve this issue.
I replaced the broken receiver with a new one I got from eBay (along with prytools for under €10) and this issue is completely fixed.
What had happened, if anyone is interested, was that the inside of receiver housing and the output on the receiver itself had been clogged with dust, tiny hairs and the like. That must have shorted the tiny thing.
Lesson learned. Get stuck in.
Hi guys.
Here`s my problem.
The camera LED on my hTC Desire won`t work in video camera recording mode(recording with LED ON), and also won`t work on the built in Flashlight.apk from Sense.
However, it does work on photo camera mode(if in dark places, it take photos using the LED - all ok).
I`ve tried different ROMs, with a full wipe(bot cache and Dalvik cache) in between the ROMs, and the LED acts the same in all of them(works only on photo camera mode - darkened places). However, I`ve installed the ICS ROM found here, on xda-developers, and this certain ROM has a small widget called "Torch", which uses the LED for a flashlight, and IT WORKS.
Now, if there was a hardware issue regarding the LED, it shouldn`t work on any ROM - basically it`s not a software issue.
I`m pretty much stunned here.
Has anyone encountered this before?
Thanks.
Hi,
I have a similar sounding problem. No camera, no camcorder, no flashlight, no led's. However the flash flashes when the phone is being booted. Thats it. I will try ICS to see if the flashlight etc works and let you know.
I have tried sense roms, AOSP roms to no avail.
regards
zaphodbeeb said:
Hi,
I have a similar sounding problem. No camera, no camcorder, no flashlight, no led's. However the flash flashes when the phone is being booted. Thats it. I will try ICS to see if the flashlight etc works and let you know.
I have tried sense roms, AOSP roms to no avail.
regards
Click to expand...
Click to collapse
I`ve had the exact same problem in the past, regarding the LED, which didn`t work in any applications(flashlight, camera etc.), but strangely flashed by itself when the phone booted, and sometimes flashed randomly while simply browsing through phone(internet, games,) - without a certain pattern. I had to send the phone back for warranty, and they told me that there was a problem with a certain hardware circuit band which connects the LED and Power Button to the phone`s motherboard. I think you have the same problem.
U can try with ICS, but my guess is, it won`t help you.
i_cs_u said:
I`ve had the exact same problem in the past, regarding the LED, which didn`t work in any applications(flashlight, camera etc.), but strangely flashed by itself when the phone booted, and sometimes flashed randomly while simply browsing through phone(internet, games,) - without a certain pattern. I had to send the phone back for warranty, and they told me that there was a problem with a certain hardware circuit band which connects the LED and Power Button to the phone`s motherboard. I think you have the same problem.
U can try with ICS, but my guess is, it won`t help you.
Click to expand...
Click to collapse
Hi,
you were spot on. Got the beloved desire back from HTC (excellent service by the way). Thanks for your help.