Hello all, I have a problem with vibrations on my I9105P. More specifically: my phone fell down from a table right on the floor (maybe 0.5 meter) and since then vibration doesn't work. Everything else works fine, tried reflashing the system and all - nothing works (first I thought it was kernel's fault). What can I do now? Will the warranty cover the repair?
PS. I use case for my phone - it's made of a silicone or something like this (don't know exactly).
If ur phone falls down, how u can say that is kernel problem?
rs tony said:
If ur phone falls down, how u can say that is kernel problem?
Click to expand...
Click to collapse
Well, maybe I said it wrong. I didn't notice that the vibration isn't working for about 5 hours after the fall and so when I reflashed the kernel I thought about the fall - my phone used to fall from time to time and it never broke, so now I'm quite confused. However today, when I was writing on the phone's keyboard, it vibrated once while pressing the letter. Since then - silence.
If you stay it vibrated once that means it's somehow not completely broken. I would disable every sort of vibration in the phone's settings. The vibration motor is probably stuck and it is probably getting damaged more if it keeps trying to spin like that. What did you think - if the phone survived one fall it will survive 10 more just as well? Try the warranty, there's a good chance they'll cover it. Or learn to live without vibration.
cLick1338 said:
If you stay it vibrated once that means it's somehow not completely broken. I would disable every sort of vibration in the phone's settings. The vibration motor is probably stuck and it is probably getting damaged more if it keeps trying to spin like that. What did you think - if the phone survived one fall it will survive 10 more just as well? Try the warranty, there's a good chance they'll cover it. Or learn to live without vibration.
Click to expand...
Click to collapse
I didn't think like that. I guess it's like every time it fell down I felt a relief, because nothing was broken (I wasn't throwing my phone around my house, as I said, it OCCASIONALLY fell). Anyway, thanks for help - I'll try the warranty, just wasn't sure if they will accept it at the service.
Related
I'm not sure if it's lag or what, but my phone screen won't come on. I think it's a ribbon that was disconnected or something though. For about a few hours if I were to press power to see the lock screen, all I saw where a bunch of rainbow static. Then I powered my phone on and off because nothing would work and now it's jut black! Does anyone know what's wrong? I can't boot into clockwork so I don't think it's a rom problem. Does anyone know the problem or have any idea to fix? Anyone I should ask specifically?
maybe water? even having my phone in the bathroom while i take a shower cause me that
It's not water, I never bring my phone close to place with water :/
can you boot into the screen where there are 3 droids with the skateboards? (i not sure whats the name)
I think I can boot and my phone still works, because it still rings when someone calls and it still vibrates when someone text it, but I just can't pick up or reply (because the screen won't come on). I should be able to boot into that thing, but I can't anything :/
well bro sorry i cant help you :/ maybe it could be the screen,the ribons or somethings loose. did it fell?
aznangel1408 said:
I think I can boot and my phone still works, because it still rings when someone calls and it still vibrates when someone text it, but I just can't pick up or reply (because the screen won't come on). I should be able to boot into that thing, but I can't anything :/
Click to expand...
Click to collapse
Seems like either broken ribbon that connects the screen to the "motherboard', or dead screen itself. That's exactly how 1 of my phones died (it was too complicated to disassemble and fix it myself)
But once I had similar problem with my TP2, the screen first become unresponsive to any touch, and then it went just black after restart (and every next restart). However all keys did work.
Hard reset somewhat helped, the screen actually came back, but it was still stuck on setting up Windows Mobile (if you know WinMo: the part where you calibrate touchscreen), apparently "touch" part of the screen didn't work.
I thought it is ribbon or screen assembly, but since all the keys worked I flashed another ROM and what do you know: all problems went away. It worked fine for as long as I had it. I never figured out what caused it/was the problem.
koete said:
well bro sorry i cant help you :/ maybe it could be the screen,the ribons or somethings loose. did it fell?
Click to expand...
Click to collapse
MT4GS said:
Seems like either broken ribbon that connects the screen to the "motherboard', or dead screen itself. That's exactly how 1 of my phones died (it was too complicated to disassemble and fix it myself)
Click to expand...
Click to collapse
Yea I think that's the problem here. I think I'm just going to borrow a friends mt4gs to use and navigate recovery and do a back up and just buy a new one and restore. Thanks for all the help guys
I noticed this morning nothing would make my phone vibrate anymore.l checked every setting and made sure everything was set to vibrate but nothing would actually make the phone shake, then I determined it must be a hardware issue after doing factory resets, OEM flashes, and several NANDROID restores - I smacked the back of the phone with my knuckles right where the speaker is, and while I was in the volume control panel I had the vibrate length menu open, i selected an option and the phone very very weakly vibrated, and having vibrated once, it then lodged itself loose again or something because it wouldn't vibrate again until I smacked it again.
I've had it for 2 months, I've never ever dropped it or, with the exception of hitting it to diagnose my issue, ever let it experience any kind of acceleration or sudden stop. I babied this thing and then this **** happens? I don't have TEP - what should i do? Should I take it apart? My warranty is already void from unlocking the bootloader, or is this different because it's a hardware issue????
Hardware issues != software issue.
I'd take it to a store and see what they say. I need to take mine in sometime too to see what they'll do about my caps lock LED since it never worked.
dpwhitty11 said:
Hardware issues != software issue.
I'd take it to a store and see what they say. I need to take mine in sometime too to see what they'll do about my caps lock LED since it never worked.
Click to expand...
Click to collapse
They're sending out a new one right now so I'm just gonna swap phones.
Exact same thing happened to me.
Did they charge you $50 to get a replacement phone like they did to me?
chas9rr said:
Exact same thing happened to me.
Did they charge you $50 to get a replacement phone like they did to me?
Click to expand...
Click to collapse
Yup, a refurb at that. I found out that the Photon 4G motor is the same as in the Q but I can't solder that precisely so I just paid the $50. ****.
Hi guys
Unfortunatly my time has come to have a possible hardware issue.
Yesterday my N5 was connected via USB (like I usually leave it resting at work / charging) and out of the blue, rebooted. Google logo shows up, and reboots right away. Trying VolDown + Power shows up the menu but I hardly have any time to select bootloader or recovery, and when I do, it eventually reboots again after a couple seconds.
I'm able to turn it on and have it on if I avoid touching the power button, when I do, sometimes it works (screens just turns off), sometimes ir shuts down after a few seconds after doing so. It's not always, but happens three out of five times.
Connecting the USB cable has the same behaviour, sometimes it's alright and I'm able to copy files and so on, sometimes it shuts off and there it goes into bootloop again.
So, I got home, opened it and I looked like a donkey looking at a castle lol. I had a disconnected brown wire on the right side of the battery which I was able to fix, but that doesn't seem to be the cause of the problem.
The power button feels ok, it's not exactly rattled or anything, it has on/off feeling. if you know what I mean.
Problem is, I bought this in second hand in london about 6 months ago, would be hard to RMA and probably they would give me the finger.
Anyway, suggestions? Anyone went through anything like this? I doubt it's a software issue (rom) cause the same behaviour happens when on recovery / bootloader. Sometimes it holds on and lets me do things, sometimes it doesn't. Most often, doesn't.
Any help or tips are greatly appreciated.
Thanks guys.
Back to my LG 4X
Send in for repair or replacement.
Lethargy said:
Send in for repair or replacement.
Click to expand...
Click to collapse
I can't, was bought in second hand in a shop, besides I opened it and the water sensor is pinkish (never touched water, probably humidity).
I can only do that around christmas time.
Any other tip ? Something I can do before considering something like that?
MidnightDevil said:
I can't, was bought in second hand in a shop, besides I opened it and the water sensor is pinkish (never touched water, probably humidity).
I can only do that around christmas time.
Any other tip ? Something I can do before considering something like that?
Click to expand...
Click to collapse
By sending in for repair or replacement, I meant to LG. Not Google for RMA.
LG will charge you for the repair or replacement.
There really isn't much you can do otherwise.
My Nexus 5 vibrate motor seems to randomly stop. Usually, it stops working for just a few seconds at a time, but sometimes it stops for more than just a few seconds. It started randomly one day, and I haven't been able to tie it to a specific app yet, and it didn't coincide with the installation of a kernel or ROM.
I'm running rooted stock Lollipop with elementalX kernel (2.03).
I've tried pushing on the back, since some people have issues with the vibration motor not making good contact with the rest of the phone, but it seems that doesn't really do anything for me. It seems to help occasionally, but not necessarily.
Sometimes turning the screen off and back on helps, but sometimes not either.
Unfortunately, the inconsistency is making it difficult for me to figure out what the problem is. Could it just be a dying motor?
You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.
bblzd said:
You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.
Click to expand...
Click to collapse
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket
And it happens with stock kernel as well, correct? If it has been less than 1 year you could RMA.
chronostorm said:
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket
Click to expand...
Click to collapse
I had this problem as well and still encountering it sometimes. Don't worry about a missed call though. My vibration completely stopped working and a reboot didn't help, however a call made the vibration work again lol and it has been working since. Fingers crossed same **** doesn't happen again.
Hello,
So maybe you already laughed a little bit by reading the title of the thread.
I had a foam party yesterday and I was stupid enough to have my oneplus one in my pocket. After about 15 minutes I finally realized that it would be a good idea to put my phone away. When I came back home in the night everything was fine but when I woke up today the touchscreen wasn't responding (only physical buttons worked). So I tried to hard reboot the phone and then everything was working again.
But after some minutes of use, I noticed that a part of the screen was reacting strangely. I went in the setting to activate the "cursor route" and I saw that there is kind of a band in the middle of the screen (about 1 cm) where the tactile is not working.
I removed the back cover and noticed that is was a little bit wet inside .. so I put my phone into some rice.
I tried to see how the screen is responding in my recovery (twrp) and the problem is also there, so I'm pretty sure it's an hardware problem.
Do you have any tips or things I can try to do ? I just want to avoid the Oneplus RMA because I don't want to be without phone for 2 months ..
Thanks in advance !
PS : I'm running CM 11S (latest OTA) and I'm rooted.
Stop using the device at all, you're potentially doing more damage every time you use it while it's wet/damp. Leave it in rice for three days without touching it. After three days is up take it out and inspect the touchscreen again.
okey, so I leave it off in the rice. 3 days without phone will be hard
If I have to replace the tactile screen (without LCD), do you know if I have to use thermal tools ?
pocj30 said:
Hello,
So maybe you already laughed a little bit by reading the title of the thread.
I had a foam party yesterday and I was stupid enough to have my oneplus one in my pocket. After about 15 minutes I finally realized that it would be a good idea to put my phone away. When I came back home in the night everything was fine but when I woke up today the touchscreen wasn't responding (only physical buttons worked). So I tried to hard reboot the phone and then everything was working again.
But after some minutes of use, I noticed that a part of the screen was reacting strangely. I went in the setting to activate the "cursor route" and I saw that there is kind of a band in the middle of the screen (about 1 cm) where the tactile is not working.
I removed the back cover and noticed that is was a little bit wet inside .. so I put my phone into some rice.
I tried to see how the screen is responding in my recovery (twrp) and the problem is also there, so I'm pretty sure it's an hardware problem.
Do you have any tips or things I can try to do ? I just want to avoid the Oneplus RMA because I don't want to be without phone for 2 months ..
Thanks in advance !
PS : I'm running CM 11S (latest OTA) and I'm rooted.
Click to expand...
Click to collapse
Lol, so it's a hardware problem that you soaked your phone ? Sounds more like a user problem.... Good luck trying to pass that on a RMA...Well good luck with trying to get a RMA period... lol
pocj30 said:
okey, so I leave it off in the rice. 3 days without phone will be hard
If I have to replace the tactile screen (without LCD), do you know if I have to use thermal tools ?
Click to expand...
Click to collapse
It'll be much longer without your phone if you don't though. And what @Cholerabob is right, what you've done to your phone isn't covered by warranty, warranty doesn't include damage caused by the owner.
Transmitted via Bacon
Cholerabob said:
Lol, so it's a hardware problem that you soaked your phone ? Sounds more like a user problem.... Good luck trying to pass that on a RMA...Well good luck with trying to get a RMA period... lol
Click to expand...
Click to collapse
If you read my post better, you will understand that I said I don't want to pass it on RMA. Of course I know that I will have to pay about 150e because it's my responsibility and it's not covered by any warranty. That's why I want to change the component myself.
And yes, it's an hardware problem because of a user mistake.
Try to make constructive answers next time at least.