anyone know were i could get all white parts for my motorola defy?
sent from Motorola Defy @1.3gz running 2.3.7!
ebay.... 10 char
10 char?
sent from Motorola Defy @1.3gz running 2.3.7!
minimum size of the post is 10 character . and i believe that thread already exists
nani?you can use the paint.
Eh? White Motorola Defy?
There's no all white housing for defy... only black for front case and battery cover.
Maybe you can get red middle housing for your identity
Sent from my MB525 using XDA App
Related
So my mom got a droid x brand new and best buy put a screen protector on, but they did it wrong so the phone made a red dotted line to show where a dirtspec/airbubble was so we went back they fixed it, but the red line wont go away, its super annoying, please help..
Sent from my SCH-I500 using XDA App
Sounds like a dead pixel, have them replace the phone because I've put 2 screen protectors on and pressed like hell with the included cardboard squeegee and haven't had any issues.
Sent from my DROIDX using XDA App
Yeah... The DX doesn't have a feature nor the hardware that will let it know that there is an issue with the screen being dirty. Take it back... and if they give you crap, raise some hell.
Sent from my Liberated Droid X using XDA Premium App
Thanx man good advise, verizon is preety damn mean when it comes to customer service y'know! Like really u can buy a brand new fone and then it breaks and its not your fault and they wont give you another new phone!
Sent from my SCH-I500 using XDA App
But how can it be a dead pixel if its like a digital red line running down the screen...?
Sent from my SCH-I500 using XDA App
They could have broken a whole line of pixels when they put on the screen protector by putting too much pressure, but it could have been other causes... your screen seems to be broken...
Sent from my Liberated Droid X using XDA Premium App
But the line comes and goes but its always in the same place??
Sent from my SCH-I500 using XDA App
I still think it's a broken screen... but one way to find out. Take a screenshot on your homescreen when the line is there, then post it here. Maybe a second opinion can be provided.
could be stuck pixels? check JscreenFix in the market.
Pulled some info from Wikipedia too,
If an LCD display is subjected to physical shock, this could cause one or more TAB connections to fail inside the display. This failure is often caused by horizontally flexing the chassis (e.g. while wall mounting or transporting a display face up/down) or simple failure of the adhesive holding the TAB against the glass. TAB faults require replacement of the LCD display module itself. If these connections were to fail, the effect would be that an entire row or column of pixels would fail to activate. This causes a horizontal or vertical black line to appear on the display while the rest of the display would appear normal. The horizontal failure runs from edge to edge; the vertical failure runs from top to bottom.
While your line is not black, maybe it is getting stuck on rather than off?
Either way, I'd probably have verizon replace it, would not be fun if you find some temporary fix that stops just after warranty is up.
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
Hello everyone, I need some help. Hopefully I am posting in the right thread.
I have a Motorola Droid X and a few months back. I used a Modified SBF to be allowed to root my Droid X. It worked perfectly but as soon as I booted up. I had the dreaded ? in the upper right hand corner and my battery wasn't being recognized. So I thought it was a bad SBF flash, so I did another SBF back to the original version that came with the phone... Still wasn't being recognized.
I had to charge it using the McGyver method by cutting an old USB cable and blah blah blah. I don't know if that killed my Droid X, but what could I do to resurrect this thing from the dead. It won't turn on.
Also, the battery on the bottom... It seems soft or smushy... Could that be the cause of a dead battery? And I tried a different battery from an old flip phone, didn't fit but it still said it wasn't recognized.
Thanks again guys.
I believe you need a new battery.
Sent from my Galaxy Nexus using Tapatalk 2
infazzdar said:
I believe you need a new battery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks man, you know where I can find a cheap one?
JustWorksTechnology said:
Thanks man, you know where I can find a cheap one?
Click to expand...
Click to collapse
They're very inexpensive from Amazon, even the extended battery is only about $15!
Sent from my Galaxy Nexus using Tapatalk 2
Did you by chance do the stripped wire charge with the battery still in the phone? Because that's a big no-no.
Sent from my Black Iced X
newmanx4 said:
Did you by chance do the stripped wire charge with the battery still in the phone? Because that's a big no-no.
Sent from my Black Iced X
Click to expand...
Click to collapse
Yes I did, I was following the instructions that were in the tutorial. =/
newmanx4 said:
Did you by chance do the stripped wire charge with the battery still in the phone? Because that's a big no-no.
Sent from my Black Iced X
Click to expand...
Click to collapse
Strange, I've never heard of the McGyver method causing an issue when done correctly.
Sent from my Galaxy Nexus using Tapatalk 2
Reason I say that is because the stripped charger method can fry the battery if done too long. If the battery swells in the phone the pressure placed on the screen can permanently damage the display. May be only a 1 in 10 chance of it happening, but I sure don't want to be the 1!
Sent from my Black Iced X
Hi XDA,
on my Defy (MB525) I had a broken digitizer. I replaced with a digitzer bought off EBay which went surprisingly fine with the help of a few YouTube-Videos showing it.
Every thing works (including proximity) anyhow a few screen areas (lower left side) where major cracks have been do not work with the new screen. As an example: I have SwiftKey installed (QWERTZ-Layout) and when I press e on it, the keyboard shows w and r (which are adjacent to e). The same goes for the entire row below it. The effect can be reproduced with other applications or keyboards as well, and is pretty annoying.
Question: Is there anything on the software-side where I can fix this or is the replacement digitizer faulty? If the latter is the case, is there any recommended source in Europe?
I appreciate all your answers and suggestions!
Cheers,
frickelbarde
The digitizer in question was faulty.
Don't buy the Chinese stuff, watch for genuine parts. For the Defy there is a polish guy on EBay who sells built-out originals for ~15€. The one I bought worked.
Cheers,
Frickelbarde
Sent from my Cosmo using XDA Premium HD app
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