Huge problem with Defy.
Had the phone for 7 months, and for the past month, every time i make or receive a call, when i try to end the call i cannot, because the screen is black and the red led is shining. Either i dial a number and the screen goes automatically black and i have to wait 2-3 minutes for it to get back or actually remove the battery, or i recieve a call and i can't end it because the screen is black whilst talking and afterwards.
I had this while running 2.2.2 CEE and CM7 which i'm running now. Any ideas?
Thanks.
I'll take a wild guess here, but since you had it in two ROMs and judging by the effects, could it be related to the proximity sensor?
Trimis de pe Defy CM9
Yes. I managed to find a videon in which some chinese guy unscrewed the right-sided bolt a little and it fixed his issue. It partly fixed mine too. In any case, way better than before, now i could actually try and close a call every once in a while.
But is there any way to permanently solve this?
^ Here's the video you're talking about: http://www.youtube.com/watch?v=uMk1S90MjbY&feature=youtu.be
BTW, same problem with my Defy. It used to work perfectly but then a few months ago I started noticing some problems with sensor (using Nordic 177-5 and CM7). Then I reflashed Nordic and used WajkIUI but the issue was still there. Luckily, WIUI has an option to completely disable proximity sensor which I did. Now, I have moved on to CEE 179-002 and CM9 and the issue comes back because now there's no option to disable proximity during call.
I still have to try out what that Chinese guy has shown. The very dim red light in sensor region is constantly glowing (if you look closely). Definitely a hardware issue.
Anybody else has permanent solution?
I have had the same problem.
A small time after i replaced my screwed front housing (broken screwholes ) inkl. Digitizer-toutch glass .
Im on quark's cm9 defy+ build march 30 at my normal defy.
A kernel change from 4.5.2-109 DHT22 to CM9 kernel solved the problem till now.
Now im looking for 4.5.1-134 DFP-231 kernel CWM update.zip
Sent from my MB526 using XDA App
So I followed the Chinese guy's video and found the my proximity sensor starts working, when I put a little pressure on the screw with a screw driver. Video tells us to rotate it, but mine works by pressure. it again stops working when pressure released. Now I don't know how to keep it constantly under pressure.
It's probably loose, coz sometimes it works on tapping the sensor.
bone101 said:
Im on quark's cm9 defy+ build march 30 at my normal defy.
A kernel change from 4.5.2-109 DHT22 to CM9 kernel solved the problem till now.
Click to expand...
Click to collapse
How are you able to run CM9 defy+ build on normal defy? Which is you base SBF ? are there any special steps required to install defy+ cm9 on defy? Please let me know, I'll try upgrading kernel, it might work!
bikerabhinav said:
So I followed the Chinese guy's video and found the my proximity sensor starts working, when I put a little pressure on the screw with a screw driver. Video tells us to rotate it, but mine works by pressure. it again stops working when pressure released. Now I don't know how to keep it constantly under pressure.
It's probably loose, coz sometimes it works on tapping the sensor.
How are you able to run CM9 defy+ build on normal defy? Which is you base SBF ? are there any special steps required to install defy+ cm9 on defy? Please let me know, I'll try upgrading kernel, it might work!
Click to expand...
Click to collapse
It is proximity sensor issue indeed. And dirt accumulation may be the problem! First try to check the working of proximity sensor by reading its raw values(Use Elixir2 or androsensor) And since it is still under warranty(7months) go see a service center... Unscrewing the torx screws may make it less water resistant and also loose your warranty!
pranks1989 said:
It is proximity sensor issue indeed. And dirt accumulation may be the problem! First try to check the working of proximity sensor by reading its raw values(Use Elixir2 or androsensor) And since it is still under warranty(7months) go see a service center... Unscrewing the torx screws may make it less water resistant and also loose your warranty!
Click to expand...
Click to collapse
Yes I tried Elixer2 and after tapping sensor a bit I can see the graph saying near/far as I move my hands over sensor. Dmesg logs an error too:
Code:
isl29030_get_avg_noise_floor: prox data sample 4 is 0x57
The 4 & 0x57 parts keep changing now and then to 0x58, 0x59.
I looked up the isl29030's driver for Defy and ended up with this.
This pastebin is the driver for same sensor used in Moto Atrix: http://pastebin.com/ur5LkA91 line 536 shows the error I get
Can someone please explain what's happening here?
bikerabhinav said:
Yes I tried Elixer2 and after tapping sensor a bit I can see the graph saying near/far as I move my hands over sensor. Dmesg logs an error too:
Code:
isl29030_get_avg_noise_floor: prox data sample 4 is 0x57
The 4 & 0x57 parts keep changing now and then to 0x58, 0x59.
I looked up the isl29030's driver for Defy and ended up with this.
This pastebin is the driver for same sensor used in Moto Atrix: http://pastebin.com/ur5LkA91 line 536 shows the error I get
Can someone please explain what's happening here?
Click to expand...
Click to collapse
Its because the sensor is not getting or not able to get enough samples or values to calculate.. Might be hardware issue!!
Cm9 + cm9 kernel dont solve the problem !!!
For more info about cm9 defy & defy+ look for the thread in XDA defy development sektion.
Sent from my MB526 using XDA App
---------- Post added at 04:39 PM ---------- Previous post was at 03:58 PM ----------
I opened the housing and cleaned the prox. sensor.
I tryed to fasten the screws not so hard as in the past.
Let´s have a look if its better now.
Maybe its a software bug
bone101 said:
I opened the housing and cleaned the prox. sensor. I tryed to fasten the screws not so hard as in the past.
Click to expand...
Click to collapse
Did this solve your problem?
No , I think Not......
Now i reflashed my Stock rom via RSD lite ans reenstalled my Backup
Now if i made a call the Display goes out for a moment, but a Bit longer than before, and comes again correctly.
Lets have a look.....how long
Sent from my MB526 using XDA App
Even I have this irritating problem after giving my phone for service due to water damage
Sent from my MB525 using XDA
Maybe its too hard screwed like in video
Sent from my MB526 using XDA App
This did not solve my problem...I have problem both with my led and sensor...may be its a bit complicated..should try giving it for service
Sent from my MB525 using XDA
Yes
Sent from my MB526 using XDA App
Related
So i I have a Nexus Ons, and Its been working flawlessly since I bought the thing. At first I tried to keep it original and not root it, but then I just said **** it haha but thats not the problem. I rooted it cyanogen mod all the goodness and i installed torch to use my flash led blub as a flashlight. I may have over used and it over heated so when i take pictures using flash there is a area of blue in every picture i take using the flash. when i dont use flash it takes pic of very good quality just as before but now i cant use flash if my life depends on it.
Is there anyway to like lower the flash so the blue does not show up as much or all together replacing the blub it self?
PLEASE XDA MEMBERS AND COMMUNITY HELP ME WITH THIS I TRY TO MAKE THREADS AND I FOLLOW THE FORUMS EVERYDAY BUT NO 1 SEEMS TO HELP
Have you checked all your settings on the camera itself. Its possible you may have inadvertantly changed something. Check your settings and go from there. If the led is toast , prolly have to send the phone in to get fixed.
it def isnt a setting because it happens when i change roms too.. and like am i still able to send it in even tho its rooted or would i have to bring it back to stock?
It sounds like the led is ok but there might be a light-leak internally between the led and the camera.
Yep, might be the back cover not sitting well, or protector case, or your fingers.
Jack_R1 said:
Yep, might be the back cover not sitting well, or protector case, or your fingers.
Click to expand...
Click to collapse
Agreed. Never heard of this problem which leads me to believe it's not shipped physical hardware malfunctioning. If it was there would be alot of threads *****ing and complaining, since that's what 8/10s of humanity use the internet for =D I'd make sure it's none of the above then flash a different rom or version and double wipe the phone. G'luck
Sent from my Nexus One using XDA App
Not anything like this is it: http://forum.xda-developers.com/showthread.php?t=873215
Damn, it is like that in the youtube video you just posted although it isnt as blue.
Is there anyway to change the bulbs board or?
There is, of course, if you disassemble the phone and have the LED board.
You might be better off attempting to use your warranty and have the phone replaced.
Try cleaning the lense.
Sent from my Nexus One using XDA App
I read in another thread where somebody's flash led turned blue after dropping it from 1m
Other than trying to replace the led i can't think of anything.
I've recently changed the whole LCD/Touch assembly ... and now my proximity sensor is not working! I didn't re flash the ROM after the service, so I know that it was working on that build before...
When I run Phone Tester app it detects the proximity sensor is detecting Far... and when I place my finger over it it detects Near, but it takes around 30 or more seconds, to go back to Far again...
What could be the cause of this? The Light sensor works normally... I don't see any dirt there... but the "hole" does look "hollower" ... maybe that lens thingy fell out... could this be it?
Thanx
proximity lens
Hi,
your wrote is a little bit older, but maybe you can me help.
i have the same problem: i lost the lens from proximity sensor. so its function is not correct.
how are you fixed this problem?
i find nowhere to buy this mini lens :-(
regards
jozsi76 said:
Hi,
your wrote is a little bit older, but maybe you can me help.
i have the same problem: i lost the lens from proximity sensor. so its function is not correct.
how are you fixed this problem?
i find nowhere to buy this mini lens :-(
regards
Click to expand...
Click to collapse
I think those lenses are not so important, more important is to have a clean space between them and the outer space. It is possible to interfere some dirt/dust/whatever during replacing touchscreen/combo.
No I can correct you...Lenses and position of those is extremely important to light and proximity sensor.I had to find those lenses here in xda cause my hd2 had many problems without,the backlight regulation doesn t work,and even the proximity sensor was faulty
I'm also searching for that lense, does any1 know where can one be bought or found?
Axel85 said:
No I can correct you...Lenses and position of those is extremely important to light and proximity sensor.I had to find those lenses here in xda cause my hd2 had many problems without,the backlight regulation doesn t work,and even the proximity sensor was faulty
Click to expand...
Click to collapse
Maybe you'd have been right about lenses, IF your prox sensor would have been OK...isn't it?
bib*oops said:
Maybe you'd have been right about lenses, IF your prox sensor would have been OK...isn't it?
Click to expand...
Click to collapse
proximity sensor and light sensor had many problems without the lenses...Light sensor was changing my backlight only under the sun,instead now it s about 5 to 6 times more accurate,and even the proximity one gave me many accuracy problems.I had the same problem in a tmous and an european hd2,maybe there are some hardware revision more sensible,that works even without those lenses.
To anyone searching for those lenses,I can tell you it s really really hard to find,you have to search for someone who sell spare hd2 parts from a broken hd2.I couldn t find those lenses in any spare parts store,I asked to almost any ebay sellers and internet shops,I ve mailed to htc,I ve talked with an htc hardware technician in chat,and I ve tried to buy 3 new middle frame chassis that came without the lenses.I had trouble even to find a picture of those lenses,cause almost no one noticed those,i ve lost those changing my touch screen,and I think anyone with proximity sensor not turning on their screen have lost those lenses,or had gone out of position
Finally after 5 months I ve found those lenses here in xda
Axel85 said:
proximity sensor and light sensor had many problems without the lenses...Light sensor was changing my backlight only under the sun,instead now it s about 5 to 6 times more accurate,and even the proximity one gave me many accuracy problems.I had the same problem in a tmous and an european hd2,maybe there are some hardware revision more sensible,that works even without those lenses.
To anyone searching for those lenses,I can tell you it s really really hard to find,you have to search for someone who sell spare hd2 parts from a broken hd2.I couldn t find those lenses in any spare parts store,I asked to almost any ebay sellers and internet shops,I ve mailed to htc,I ve talked with an htc hardware technician in chat,and I ve tried to buy 3 new middle frame chassis that came without the lenses.I had trouble even to find a picture of those lenses,cause almost no one noticed those,i ve lost those changing my touch screen,and I think anyone with proximity sensor not turning on their screen have lost those lenses,or had gone out of position
Finally after 5 months I ve found those lenses here in xda
Click to expand...
Click to collapse
Ok, I got your point, maybe you're right about those hardware revisions...
Ok, found today guy selling broken HD2 parts, got myself lens, so happy
works great, no more in call screen on problems
krashekspres said:
Ok, found today guy selling broken HD2 parts, got myself lens, so happy
works great, no more in call screen on problems
Click to expand...
Click to collapse
You re really lucky man....
krashekspres said:
Ok, found today guy selling broken HD2 parts, got myself lens, so happy
works great, no more in call screen on problems
Click to expand...
Click to collapse
Hi,
oh man! can you tell me wher i can get this lens?
my proximity sensor without this lens make me crazy :-(
same here! where i can find it?
Hello,
I broke the screen of my Moto Defy+ (MB526) which I obviously want to replace.
However, here (NL) we only have parts (such as replacement screens etc) for the Moto Defy (MB525) available.
Does anybody know if hardware parts such as screens/digitizers etc. are interchangeable between the MB525 and the MB526?
Thanks in advance,
TY
Although not absolutely certain, but I think they're identical with respect to the touch screen and hence parts should be swappable between models
Sent from my MB526 using xda premium
All the parts are interchangeable (caution with camera and battery) between defy and defy+.
Ignore of your taking about digitizer
I may be wrong but afaik display comes with rev versions so make sure its the same revision(may be written on the display itself
Sent from my MB526 using xda premium
OK
hackergnome said:
Ignore of your taking about digitizer
I may be wrong but afaik display comes with rev versions so make sure its the same revision(may be written on the display itself
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Take care about battery and camera, all other parts are interchangeable, i think.
As far as display and digitizer goes its all the same Ive replaced mine manually with a chinese one. Works fine. Remember your speaker orientation before popping it out. Might not matter but why risk it and it looks identical rotated.
drawkcaB said:
As far as display and digitizer goes its all the same Ive replaced mine manually with a chinese one. Works fine. Remember your speaker orientation before popping it out. Might not matter but why risk it and it looks identical rotated.
Click to expand...
Click to collapse
Slight bit of an OT regarding our Defy Screen.
Since you replaced yours with a Chinese replacement LCD, how's the quality of the display? Is it par with the original Defy LCD?
Though i always use the freezer trick to fix dead pixels on my Defy. I'm planning on also replacing my LCD with a Chinese one hoping that it will be more tough on dead pixels..
Thanks.
chipset used in defy+ is little different to that of the defy. Some Parts may cause problem
drawkcaB said:
As far as display and digitizer goes its all the same Ive replaced mine manually with a chinese one. Works fine. Remember your speaker orientation before popping it out. Might not matter but why risk it and it looks identical rotated.
Click to expand...
Click to collapse
Hey,
Can you confirm the quality of chinese LCDs? I am getting MB525 LCD, which I hope is compatible with MB526. My phone, got dropped from bed & not almost half of the screen is black.
I stay in Mumbai, India.
Tnx.
mGforCe said:
Hey,
Can you confirm the quality of chinese LCDs? I am getting MB525 LCD, which I hope is compatible with MB526. My phone, got dropped from bed & not almost half of the screen is black.
I stay in Mumbai, India.
Tnx.
Click to expand...
Click to collapse
Sorry been off XDA for ages. Yeah my Digitizer works fine. I didnt change the screen just the touch was cracked and i changed it along with the entire front housing. Works without any issues. I too live in mumbai and i ordered mine from ebay.com
I hate making new threads... but I've been looking at different places and haven't found the right answers to my questions... so yeah.
I have a GREEN LENS Defy MB525. It has gone through some trouble. It has some blue marks and such on the screen.
I found this and will be trying the method soon to see if the screen gets fixed. But, the owner of the phone had disassembled it to change the ear piece that was broken. Afterwards, the phone's screen doesn't take all the touches.
On the QWERTY screen, when you try to use the "Shift key or any of the letters (zxc...) on the phone, it takes the keys on top of them or below them.
I want to try to fix the phone but I don't know if it's a problem with the LCD that needs to be replaced, the digitizer or simply something else entirely.
The phone is running CM 10 2ndboot 2012-12-31 but it does the same on stock. I already tested it.
Any tips or help will be appreciated to finally have a working Defy
I also found this but since I don't have another screen to use for testing... well yeah...
I had such problems before after changing the speakerphone . All I did was to get a new digitizer and clean the inner screen using lighter fluid
Sent from a Motorola Defy
Okay, so it appears to be a digitizer problem?? Alright.
xXLostsoul111Xx said:
Okay, so it appears to be a digitizer problem?? Alright.
Click to expand...
Click to collapse
When in doubt , change both
Sent from a Motorola Defy
xXLostsoul111Xx said:
Okay, so it appears to be a digitizer problem?? Alright.
Click to expand...
Click to collapse
Because you put the phone in the freezer you maybe destroy the digitizer but also be aware to check ALL the contacts and terminals from the motherboard for oxidization.
I was asking because I don't wanna invest into something that isn't really needed. Don't have a steady income. >.>
xXLostsoul111Xx said:
I was asking because I don't wanna invest into something that isn't really needed. Don't have a steady income. >.>
Click to expand...
Click to collapse
I didn't put my Defy in the freezer though
Sent from a Motorola Defy
I haven't put it in the freezer yet.
I am thinking of doing it since it seemed to produce results in that thread.
I specifically said "will be trying the method soon".
Since it's such a strange advice I have yet to do it. I wanted to asked about my other problems before trying that.
The circles on the screen I am aiming to fix with the freezer thing have nothing to do with my problem since I've had those circles from way before the problem appeared.
It appeared when the phone was disassembled to change the earpiece. Please don't jump to conclusions so quickly. I am only considering that method to fix the circles in the screen since Auris posted in that thread favoring it.
Auris 1.6 vvt-i said:
Wrap it up in a plastic bag. Wrap it reeeeeeeally good, then duct tape it. After taking it out of the freezer, let it stay with the bag for at least 6 to 8 hours, 'cause when you take a cold object into a warm room, it condenses. Make sure your phone is well acclimated and there is no condense whatsoever. Then you can unwrap it and put the battery back in.
Click to expand...
Click to collapse
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
All that aside... since the freezer thing is not really relevant to the state of the phone as of writing this message...
Is there a way to know if the digitizer is busted? or the LCD? It was fine until my friend opened the phone to change the earpiece then the phone started showing the weird symptom where it wouldn't let him type any letter on the third line of the keyboard (zxc...). I tried the Android keyboard (AOSP) and swiftkey 3. The problem still persist even if I go to stock rom.
Let make a little light: The color problem relied to LCD and the keyboard malfunctioning is from digitizer. Because is improbable to broke both from one shot disassemble again, reattach CAREFULLY the digitizer and LCD and power on. Good luck.
I'm running latest cm11 nightly (27Jan) on my Samsung Galaxy S4 I9505 international version (jfltexx), but noticed the proximity sensor is broken since quite a few nightlies ago.
When I take a call, the screen goes off, but then it never comes back on again until I press the power button, or after a long delay. Checking with cpu-z, the sensor initially detects 0cm when u touch the proximity sensor, but upon lifting finger, it never gives a higher value (usually limit at 8cm). I can't post to the cm11 development thread to get help on this (maybe coz I've not chalked up enough post counts). Any idea on this will be much appreciated, thks.
Sent from my GT-I9505 using Tapatalk
androimedan said:
I'm running latest cm11 nightly (27Jan) on my Samsung Galaxy S4 I9505 international version (jfltexx), but noticed the proximity sensor is broken since quite a few nightlies ago.
When I take a call, the screen goes off, but then it never comes back on again until I press the power button, or after a long delay. Checking with cpu-z, the sensor initially detects 0cm when u touch the proximity sensor, but upon lifting finger, it never gives a higher value (usually limit at 8cm). I can't post to the cm11 development thread to get help on this (maybe coz I've not chalked up enough post counts). Any idea on this will be much appreciated, thks.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
maybe it is dirty? from the inside of glass, i had this, posted how to disassemble S4 and how to clean the sensor and glass from the inside. from 43-51 (avarage sensor value) i got 12-16 and the trigger is 46 (going back from close to far).
I had the same symptoms as you, screen black untli i pressed something.
http://forum.xda-developers.com/showthread.php?t=2354585&page=3
Thks very much! Following the discussion in the link u sent me, I've managed to fix my proximity sensor problem.
Sent from my GT-I9505 using Tapatalk