I flashed cm 7.2.0 about a year ago and am very happy with it overall, but it seems that it causes problems to the device speaker....It was damaged about 2 months after i flashed cm7 (i changed it) and now i have the same problem....Any ideas??? is it the ROM or a hardware problem (defect)??
Rom : cm7.2.0
Kernel : sympfinity v4.5
Radio : 3.35.20.10
Hboot : 6.01.1002
S-OFF
Anyone???
Angryhad said:
I flashed cm 7.2.0 about a year ago and am very happy with it overall, but it seems that it causes problems to the device speaker....It was damaged about 2 moths after i flashed cm7 (i changed it) and now i have the same problem....Any ideas??? is it the ROM or a hardware problem (defect)??
Rom : cm7.2.0
Kernel : sympfinity v4.5
Radio : 3.35.20.10
Hboot : 6.01.1002
S-OFF
Click to expand...
Click to collapse
Hardware issue. Same with me. Did you drop it? On watery surface? The sound has a lot of screeches,correct?
Sent from my Nexus 4
gobz said:
Hardware issue. Same with me. Did you drop it? On watery surface? The sound has a lot of screeches,correct?
Sent from my Nexus 4
Click to expand...
Click to collapse
I dropped it A LOT of times man and....Yeap....lots of screeches....but i don't think dropping it would cause that type of damage...i assume it's some kind of damage on the voice coil of the speaker. I also recall messing with the Dsp Manager before the 1st damage.
How about yours? was it caused by dropping it??
Angryhad said:
I dropped it A LOT of times man and....Yeap....lots of screeches....but i don't think dropping it would cause that type of damage...i assume it's some kind of damage on the voice coil of the speaker. I also recall messing with the Dsp Manager before the 1st damage.
How about yours? was it caused by dropping it??
Click to expand...
Click to collapse
Mine was def not coz of cyanogen. I had dropped it b4 the sound went mad. Yes the coil must be damaged. To confirm, check if headphones work normal.
Related
From reading various forums it seems the defy is a little flaky in build quality. I thought it may be an idea to collect on a thread who has had what repaired/replaced and by whom.
I had a bayer model 9 months, stopped powering up. Sent to carrier for repair, camera module changed to soc, repair failed in seven days, returned they replaced motherboard, on collection phone would not power on, sent back new battery added. Phone had constant reboot issues, so carrier replaced handset soc model.
This one reboots too:/
Sent from my MB525 using Tapatalk
My speaker has just gone not the loudspeaker the other one gutted :-( has anyone else had this problem.
sent from my cyanogen mod 2.3.7 defy running at 1ghz and I absolutely love it
I have had my device replaced once with a bad rom flash and now once with a bad speaker buzz. Call T-Mobil up and after a lengthy process they will send you a new phone.
The earpiece is a common problem on this phone and seems to come from the milestone that had the same defect but is repairable on garanty and is not something that seems to happen alot. I also exploded the cpu but i am running at 1.3Ghz so this is possible.
Overal i dont get alot of repairs for this model and the earpiece is easy to change if you lost your garanty.
I dont find the phone cheep and in fact i have dropped it alot, put it in water, overclocked ,overheated it etc, etc and it has very well endured the abuse... so i find this phone much more of quality than alot of models out there.
Sent from my MB525 using XDA App
A friend of mine also had a dead speaker. We just reflashed 2.1 and when it came back the speaker was repaired and they even updated to 2.2, which made reinstalling 2nd-init and CM7 even easier
I guess if you reflash your normal SBF with RSD-Lite, there should be no problem with warranty.
Hey Guys,
I've got Problems with my headphone jack.
It does not work with every headphones and even with a good working one (yes, it's ugly iPod headphones..) it may not work, if the plug is turned or other "unusual" things happen..
Is this a general problem (cause it's from the beginning - but not as bad as it's right now) or is this only my device?
Will the warranty help or should I just accept that?
Any experiences?
Thanks and greetings form Germany
Flo
You checked if you have rubbish in the jack ? Headphone's goes completely in the jack ?
FloMi said:
Hey Guys,
I've got Problems with my headphone jack.
It does not work with every headphones and even with a good working one (yes, it's ugly iPod headphones..) it may not work, if the plug is turned or other "unusual" things happen..
Is this a general problem (cause it's from the beginning - but not as bad as it's right now) or is this only my device?
Will the warranty help or should I just accept that?
Any experiences?
Thanks and greetings form Germany
Flo
Click to expand...
Click to collapse
Which ROM you are using? MIUIv4 SnapSeries has headphones problem. Use toggleheadet2 app from market to resolve it.
I'm using dudemans CM10 build (I'm the guy who wrote the brightness tipp to you )
Mhh the dirt thing could be the reason - I did not think about that
But how will I get it out?
Any ideas?
edu_stoicescu said:
You checked if you have rubbish in the jack ? Headphone's goes completely in the jack ?
Click to expand...
Click to collapse
Oh man, I feel kind of silly I didn't think of this
I tried with a needle and a bunch of dust came out
Nawesome..
Never mind - the Problem is solved
But now the plug slips out with the lightest pull, but thats better than bevore.
Thanks :good:
Edit: Can i mark this thread as solved any way?
FloMi said:
Oh man, I feel kind of silly I didn't think of this
I tried with a needle and a bunch of dust came out
Nawesome..
Never mind - the Problem is solved
But now the plug slips out with the lightest pull, but thats better than bevore.
Thanks :good:
Edit: Can i mark this thread as solved any way?
Click to expand...
Click to collapse
Thanks for the brightness thing. And yes you can mark this thread SOLVED as you got headphones working
Maybe I askes the question wrong
HOW can I mark this as solved?
FloMi said:
Maybe I askes the question wrong
HOW can I mark this as solved?
Click to expand...
Click to collapse
Edit your first post's title ^^
Bazinga
omnomnomkimiiee said:
Edit your first post's title ^^
Bazinga
Click to expand...
Click to collapse
I'll do that.
In some forum you can mark a thread as solved
solu
you could also use a Q tip to remove the dirt.
Problem is:
Sometimes my Arc S is rebooting when I put it down.
If i'm gently release it from a max of 1cm height to a soft surface, its immediatley reboots.
Was checking the battery if it's not fitting good enough, but the problem is something else.
Looks like a hardware failure for me, maybe a micro crack on the motherboard?
Or what else can it be?
(Stock GB ROM)
I think you are right. It sounds like a hardware problem some-where.
If your are under warranty, then take it in.
Otherwise here is a tutorial for taking apart your phone - http://forum.xda-developers.com/showthread.php?t=1800226
Maybe you will find something if you are lucky.
Did you overclock your phone?
xyyxpp said:
Have you overclock your phone?
Click to expand...
Click to collapse
Nope.
Not even dropped it.
Kiskoko said:
Nope.
Not even dropped it.
Click to expand...
Click to collapse
How about the rom..
stock or not?
xyyxpp said:
How about the rom..
stock or not?
Click to expand...
Click to collapse
Stock ROM, stock kernel.
Repair firmware via Update Service.
If problem occurs, you know what to do - take it to repair.
Someguyfromhell said:
Repair firmware via Update Service.
If problem occurs, you know what to do - take it to repair.
Click to expand...
Click to collapse
That was my last hope too. Will try to do so ...
Kiskoko said:
Problem is:
Sometimes my Arc S is rebooting when I put it down.
If i'm gently release it from a max of 1cm height to a soft surface, its immediatley reboots.
Was checking the battery if it's not fitting good enough, but the problem is something else.
Looks like a hardware failure for me, maybe a micro crack on the motherboard?
Or what else can it be?
(Stock GB ROM)
Click to expand...
Click to collapse
It doesn't looks like a software failure,but a hardware one.
I have an Arc S LT18i (build 4.1.B.0.587) and since a few days I have an annoying problem.
After having had a phone-conversation my screen turns black and won't come back alive!
I have to open it up, take out the battery and wait for approx. 5 minutes before I can reboot...
Any ideas???
Wich ROM and kernel did you use actually ?
Kapov said:
Wich ROM and kernel did you use actually ?
Click to expand...
Click to collapse
Euhmmm, In 'about the phone it says' : Kernel is 2.6.32.9-perf, [email protected]#1 . Where do I find which ROM I have?
Forget flashing roms etc. This is a hardware fault. The sensor left to earspeaker upper your screen is probably dead.
Sent from my LT15i using xda premium
TheHaso said:
Forget flashing roms etc. This is a hardware fault. The sensor left to earspeaker upper your screen is probably dead.
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
Oh oh, that doesn't sound too good. Is it replacable or do I have to send it to repairservice??
Patje936 said:
Oh oh, that doesn't sound too good. Is it replacable or do I have to send it to repairservice??
Click to expand...
Click to collapse
If the problem really is from the proximity sensor, I wouldn't see why it can't be replaceable although it might be quite difficult to find it on the internet, so sending the phone to Sony service (or even just people who fix phones) to check what is the real problem and how to fix it
Sent from Xperia Arc S
Problem solved
Tnx for the input guys but the problem is (more then) solved.
I sent the phone to repair service and due to problems with delivery of spare parts the sent me a brand new Xperia S !!!
Well, that's not too bad, congratulations!
Via Mobile
Hi guys
This is my first thread, in this forum. Personally, i've never moded my cell phone, but recently attempted to root and mod my wildfire s.
I succeeded, this forum was really helpfull!
Even before the mod, my screen was driving me crazy. In the begining it took my attempts to unlock the phone. Some other time, in the messages section, keypad would act on his own, literally Even if i typed "A" it would typed "enter" or anything else but "A". So I enabled touch trace to see what happens.Here is the thing, like i suspected, touchscreen's reactions are spoted away of the point i touch. Sometimes, two touch traces appear on the screen.. Some other times, its extremely difficult to unlock the screen, hang up the phone, or use the menu.. So that's the story. With the mod nothing changed..
Is it a hardware problem? Is it a software problem?
Thanks in advance.. :good::good:
PS: I use cyanogenmod 10
Only a couple of apps installed
PS: english is not my mother language so, maybe some unusual expressions and dictation could by used :angel:
Which rom?
Sent from my Wildfire S A510e using xda premium
edited main
mahesh48 said:
Which rom?
Sent from my Wildfire S A510e using xda premium
Click to expand...
Click to collapse
cyanogen 10
i had this problem too:
It's not a big problem..
your hand is wet, and the screen also, but if you dry it with a polyester (of your t-shirt) it will work..
only dry the display and your hand
so..
iPlopp4D said:
i had this problem too:
It's not a big problem..
your hand is wet, and the screen also, but if you dry it with a polyester (of your t-shirt) it will work..
only dry the display and your hand
Click to expand...
Click to collapse
you mean to take out the touch screen and dry it? Because right now im pretty sure its absolutely dry
Hi, ghost inputs is a known issue caused by the charger delivering incorrect voltage/amperes. Are you using the stock one ?
omnomnomkimiiee said:
Hi, ghost inputs is a known issue caused by the charger delivering incorrect voltage/amperes. Are you using the stock one ?
Click to expand...
Click to collapse
Yes im using the stock one. I ve never measured the output though.. I maybe check it tomorrow.. But the problem is constant and happening, not only when the device is plugged... The other thing is, there isnt only ghost inputs, there are freezings too. Or a thing, where ex: im trying to unlock the phone, so i slide to the side, and visually im almost unlocking it, but in real, nothing happens. Its still on lock screen.
any other?? im kinda desperate with this phone.. :crying:
Perhaps a recalibration might work.
Sent from my HTC Wildfire S using xda app-developers app
rishr4 said:
Perhaps a recalibration might work.
Sent from my HTC Wildfire S using xda app-developers app
Click to expand...
Click to collapse
So as i think of it ill firstly calibrate the screen and then is problem still appears i will replace the digitizer
Underdogg27 said:
So as i think of it ill firstly calibrate the screen and then is problem still appears i will replace the digitizer
Click to expand...
Click to collapse
yes, If re-calibration is not helping then you need to replace the digitizer. Am also suffering the same issue now. Just got my digitizer replaced two days before. But am still suffering from some issues regarding touch. Gonna have to recheck with the retailer
rishr4 said:
yes, If re-calibration is not helping then you need to replace the digitizer. Am also suffering the same issue now. Just got my digitizer replaced two days before. But am still suffering from some issues regarding touch. Gonna have to recheck with the retailer
Click to expand...
Click to collapse
Recalibration was succesfull it didn't come up with any change though...
So can you update this thread with your progress?? If your issue is fixed with the replacement of the digitizer then ill order one.
Underdogg27 said:
Recalibration was successful it didn't come up with any change though...
So can you update this thread with your progress?? If your issue is fixed with the replacement of the digitizer then ill order one.
Click to expand...
Click to collapse
Sure thing. I am gonna clarify this with the retailer EOD.
ITS a hardware problem
i'm pretty sure its an hardware problem,did your wfs ever fall down or get submerged in water ??
Have you tried another charger?
omnomnomkimiiee said:
Have you tried another charger?
Click to expand...
Click to collapse
That issue applies while we try accessing the phone while it is charging , right ? I mean, the touch response will be strange while the phone is been charged. But, here the OP is having issues with the touch screen all the time (charging / not-charging) . And re-calibration didn't work too.
hellfire7777 said:
i'm pretty sure its an hardware problem,did your wfs ever fall down or get submerged in water ??
Click to expand...
Click to collapse
not as far as i remember..
omnomnomkimiiee said:
Have you tried another charger?
Click to expand...
Click to collapse
Ghost input isn;t my problem.. Touch issue happens all the time charging/discharging
rishr4 said:
That issue applies while we try accessing the phone while it is charging , right ? I mean, the touch response will be strange while the phone is been charged. But, here the OP is having issues with the touch screen all the time (charging / not-charging) . And re-calibration didn't work too.
Click to expand...
Click to collapse
Right.. Recalibration wasn;t helpfull.. Im waiting your report about Digitiser replacement so ill get one and fix that matter.
Hope its screen's issue, and not some further hardware damaga
It will take another two days for him to find out and clarify the issue. If it is a digitizer issue or some other hardware issue, I will update the same here ASAP.
rishr4 said:
That issue applies while we try accessing the phone while it is charging , right ? I mean, the touch response will be strange while the phone is been charged. But, here the OP is having issues with the touch screen all the time (charging / not-charging) . And re-calibration didn't work too.
Click to expand...
Click to collapse
Nope, issue happens at all times due to residual current.
rishr4 said:
It will take another two days for him to find out and clarify the issue. If it is a digitizer issue or some other hardware issue, I will update the same here ASAP.
Click to expand...
Click to collapse
Oh thanks a lot mate.. Im kinda desperate with this device.. 2 years counting, warranty void and this ****ty thing came up from nowhere..
omnomnomkimiiee said:
Nope, issue happens at all times due to residual current.
Click to expand...
Click to collapse
I thought this was the error in the first place i measured current and voltage on the output of the charger and it seems legit..
I did change the charger thoug. So i didnt know how to proceed on this one. The way im thinking of it right now, i might let the battery completely deplete and charge from the new one?