So i've had my Nexus S for a little over a month now, and this morning when I woke up, the phone doesn't vibrate at all anymore. It shouldn't just be a setting because I've rebooted, played with the haptic feedbacks, played with the alarm, etc etc. Nothing works.
Has anyone else had this problem? Did the vibration on my phone just die? I've searched through XDA, and some people have had vibration issues, but only when receiving sms.
(I'm stock everything > locked, unrooted, stock rom)
Hoping someone knows a fix. Thanks in advance!!
ctai320 said:
So i've had my Nexus S for a little over a month now, and this morning when I woke up, the phone doesn't vibrate at all anymore. It shouldn't just be a setting because I've rebooted, played with the haptic feedbacks, played with the alarm, etc etc. Nothing works.
Has anyone else had this problem? Did the vibration on my phone just die? I've searched through XDA, and some people have had vibration issues, but only when receiving sms.
(I'm stock everything > locked, unrooted, stock rom)
Hoping someone knows a fix. Thanks in advance!!
Click to expand...
Click to collapse
Don't worry, juat wipe everything....hold power and vol.up....after you know what to do
Sigh. I was hoping it wouldn't have to come to that. I will try a full wipe and restore it this weekend and get back to you. Thanks so much for your help!!
Sent from my Nexus S using XDA App
Its gonna work trust me.
This may sound stupid, and maybe you've already checked, but under your sound settings is the vibrate set to always? I have things mysteriously uncheck themselves from time to time.. other than that, sadly, wiping would be the way to go..
So I haven't wiped yet because I was working all day but the vibrating came back on it's own for a while. Then it stopped again and now it's back again. Is this a bug? I will wipe this weekend to see it it will fix it completely.
Also, I've checked the settings and ok pretty sure it's set to always vibrate.
Sent from my Nexus S using XDA App
OFF-TOPIC
I remember long ago i had sony ericsson i500 (i think) and it had the same problem but one day it broke so i opened it and found out that the cable connecting the "motherboard" to the vibrator wasnt connected properly , you may have the same problem.
Related
Driving me insane. Doesn't matter what ROM I'm running, it does it 90% of the time for incomming and outgoing calls.
Anyone have any ideas?
Mine randomly does this as well. It's a rather unpleasant experience to have the speakerphone on @ your ear when someone responds to your answering the phone.
I've had mine turn on in the middle of a call once or twice. I thought I had somehow hit something not knowing it.
Had that problem. Believe it has something to do with the "car dock" mode. somehow it gets turned on or something. Don't really remember what I did other then try resetting it, pulling battery, or just smacking the crap out of it onto a table or something. I'm serious, not hard enough to break it but enough to fix it hehe. I'm actually pretty sure that's what I did lol.
Infuse w serendipity VII
I'm having this issue all of a sudden as well. All I know, is it didn't do it before I got the Gingerbread OTA update, and now it does.
Very annoying!
Sent from my HTC Inspire, so the typos aren't my fault.
Same issue here. Running stock non-rooted GB. Also on wife's LG Phoenix. Could be something sent down from ATT?
Try going to settings - dock - remove check from Auto-launch. I'm wondering if it thinks for some reason it's docked and therefore defaulting to Speaker
Just found out that GoSMS was the problem. Updated on both phones and the problem is gone. They actually admitted to it with the update description.
I have the same issue. Went as far as flashing back to stock unrooted. Still occurred. I believe its a hardware problem with the usb on the phone. Something about the contacts crossing.
Sent from my Inspire 4G using XDA App
GoSMS Pro was doing it for me. Uninstalled and problem went away. I'm gonna reinstall to see what happens.
Just updated my GoSMS, and was surprised to see the issue came from there. It will be nice to not have to deal with this anymore!
Sent from my HTC Inspire, so the typos aren't my fault.
Was there a solution to this issue? Because I have the same issue, but I do not have the GoSMS app.
TolaSkamp said:
Was there a solution to this issue? Because I have the same issue, but I do not have the GoSMS app.
Click to expand...
Click to collapse
If you read the thread you would have seen that the two causes of the problem were dock mode and also go sms. Not to mention this was dug up from 3months ago
Thanks for your reply.
Guess I should have mentioned dock mode does not seem to be whats causing it on mine.
I understand this was dug up from 3 months ago, but I am having the issue now was good back then.
Same happens with me... i hav removed dock mode also but still have speaker always on..
any solutions?
I recommend root and custom rom. Never had this problem since then.
harlenm said:
Driving me insane. Doesn't matter what ROM I'm running, it does it 90% of the time for incomming and outgoing calls.
Anyone have any ideas?
Click to expand...
Click to collapse
Okey I am having this problem on every rom whether its ics or gb.
The culprit is carhome app.I have be after this problem since I got my inspire. It gave me whole lot of trouble. Latest one is force auto-rotate screen.
Another thing is u need original inspire charger and usb. If u have anyone thing which is not original. Carhome app will cause problems. Unfortunately my inspire charger and USB r broken.
The only solution is to open the rom zip delete carhome.apk and carhomeluncher.
How I come to conclusion.
I charged my phone then flashed aospx rom everything was fine no auto speaker, no forced auto rotation but as soon as I connected my USB carhome app pops up and
All these problem started to happen again.
Sent from my Desire HD using xda app-developers app
same problem
Hi, I have the same problem with the New Att stock sense 3.0 (3.20.502.52) rooted ROM http://forum.xda-developers.com/showthread.php?t=1810461
The Car Panel app was launching randomly, so I first froze it using root uninstaller, no more car panel launching, but my screen started randomly turning on while in sleep, so I completely uninstalled Car Panel, my screen still goes on sometimes, and it did not solve the speaker always on problem.
Cheers.
Remix22 said:
Hi, I have the same problem with the New Att stock sense 3.0 (3.20.502.52) rooted ROM http://forum.xda-developers.com/showthread.php?t=1810461
The Car Panel app was launching randomly, so I first froze it using root uninstaller, no more car panel launching, but my screen started randomly turning on while in sleep, so I completely uninstalled Car Panel, my screen still goes on sometimes, and it did not solve the speaker always on problem.
Cheers.
Click to expand...
Click to collapse
Once carhome starts there is no way to solve the problem.even after removing it problem remains.
Best solution is delete it from the zip before installing
Sent from my Inspire 4G using xda app-developers app
I have found my screen won't stay off when I hold it up to my ear. Light sensor is very sensitive or my ear is shaped weird... Probably the later. I then think 'fat facing' because of this has attributed to random hangups and speaker phone engagements.
Sent from my Inspire 4G using xda app-developers app
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium
Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!
I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?
I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.
Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.
He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O
@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves
Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!
Hey guys! I woke up this morning in a rush, tried to make a text and phone rebooted. Now it wont stop rebooting. I've managed to get it into recovery and flashed CM10 again and nothing. I managed to get it to stop for a bit, but almost every time I hit the sleep/wake button to lock the screen it turns off!!
Any help is GREATLY appreciated!!
No eh?
Well it seems to be a hardware issue. Almost every time I lock the phone it wants to hard reboot. Sometimes when I'm in an app the power button menu shows up too. This is driving me insane.
Has anyone else had this issue!? I'm running cm10 so I guess my only option is to contact HTC?
Many questions u full wiped right? Have u tried flashing back to stock if that doesn't work have u tried ruu all of these should be done and if it persists after that than yes something janky is going on with your phone...did you mess with the CPU at all?
Why not try flashing another Rom and see if it still does it. Hope this helps in some way
Sent from my HTC One X using xda premium
Hello guys... I need some help with my infuse 4g..... The phone suddenly went deaf, it doesn't ring nor vibrate it had this problem weeks ago alongside the fact that my infuse kept getting stuck at the samsung screen logo so i decide to upgrade to gingerbread 2.3.6(stock firmware + rooted)... after i did everything became normal but now my sound and vibration is gone again(its not a hardware problem) so i dont know what to do, i can only use media with my earphones but however i can call and talk on the phone without my earphone, i'm really frustrated cause iv searched for a solution all over xda and other forums but i still havent found help so please help me out.... THANK YOU!
DopeBoi Dipsey said:
Hello guys... I need some help with my infuse 4g..... The phone suddenly went deaf, it doesn't ring nor vibrate it had this problem weeks ago alongside the fact that my infuse kept getting stuck at the samsung screen logo so i decide to upgrade to gingerbread 2.3.6(stock firmware + rooted)... after i did everything became normal but now my sound and vibration is gone again(its not a hardware problem) so i dont know what to do, i can only use media with my earphones but however i can call and talk on the phone without my earphone, i'm really frustrated cause iv searched for a solution all over xda and other forums but i still havent found help so please help me out.... THANK YOU!
Click to expand...
Click to collapse
did you go to the sound setting and tried adjusting things in there ?
if you didn't drop the phone, then, maybe you should root it again ? or recall if you install any app before it went dead ?
g-noob said:
did you go to the sound setting and tried adjusting things in there ?
if you didn't drop the phone, then, maybe you should root it again ? or recall if you install any app before it went dead ?
Click to expand...
Click to collapse
The phone wasn't dropped everything was working perfectly fine then i placed it on the table & when i took it back frm where i left it n realised i had a missed call so i was wondering y it didn't ring and then i realized the sound and vibration were all dead.... i ll try rooting it again and see plus i can't recall if i installed any app before it went dead... But thanks for ur suggestion i'll try that
Thought I noticed a few days ago that my phone wasn't vibrating while ringing but forgot about it and went about my week. (I don't get a lot of calls). Yesterday I had the phone on vibrate only and happened to look at it while I was getting a call. It definitely was not vibrating. So I downloaded vibrate tester and... nothing. It's not like you can even hear a broken motor or something trying to vibrate, just nothing at all.
I haven't found this problem searching around, my phone is totally stock no root or anything. Anyone else seen something like this? I was on 4.4 when I noticed and I updated to 4.4.2 today and still no help. Any suggestions?
What did google say?
Sent from my Nexus 5
dicecuber said:
What did google say?
Sent from my Nexus 5
Click to expand...
Click to collapse
To do a factory reset, which I'll be trying tomorrow, but I have a sneaking suspicion it won't work. Just wondering if anyone else had observed this issue.
I had this happen. But it came like that out of the box. I returned it for a new one. Only took 6 days. It was a dead vibrator motor. Sounds like that might be your issue. If so try a factory reset and if it doesn't fix it then time to rma
Sent from my Nexus 7 using XDA Premium 4 mobile app