My SGS2 stopped vibrating. Tried flashing, un-rooting, restoring stock and factory settings. None of these worked.
I am inclined to think that it is a hardware problem.
Has anyone else been dealing with issue? I read some posts on XDA regarding this matter but they were software related as opposed to hardware. Can anyone post instructions on how to fix it or provide any solutions for this issue?
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
UpInTheAir said:
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
Click to expand...
Click to collapse
Cannot get jig in Palestine. Bought the phone from the UK. Sending it back will be problematic. I will look for a repair shop.
Thanks for the quick reply
That's a "bummer" (bad luck). You could make a jig, but as you said that it would be problematic to return. Hope you can sort it easily. Sorry, can't think of anything of use right now.
Sent from my GT-I9100 using xda premium
hey there,
i got the same problem. no more vibrating at all. not with calls or notifications and not as haptic feedback. it started today (was still working in the morning), though i did not drop the phone or anything.
i am still hoping too find that it's a sw-problem. but all potential solutions i find do not help. so i guess i have to contact samsung.
but before i do that i have to get rid of all "hacking".
could you plz tell me what i have to do?
i have now cm9 20120402 nightly.
but i still have a cwm-recovery-backup of the original touchwiz (gingerbread).
-so first i make a backup of my current rom via cwm and of all my apps via titanium and store everything on my pc.
-i flash my touchwiz-backup
-i get one of those: http://www.amazon.de/s/ref=nb_sb_no...ld-keywords=Samsung+Galaxy+S2+USB+Jig&x=0&y=0 , plug it in, wait til its done and remove it again.
after that, samsung will never know i "messed" with the phone??
or do i have to consider/do something else?
tyvm!!
kws
I have the same issue.
When I was on my stock 2.3.5, I found a workaround:
- go into test mode (dial *#0*#)
- find the vibrate button, when you press it, it shouldn't work like you expect
- go back
- plug in your headphones and push the cable a bit to the left
- test vibrate again - this time it should work
- pull the cable out while vibrating, still pushed to the left, vibrations should stay on
I know it sounds crazy but it seems the hardware part that controls the vibrations is near to the jack port - excessive use of headphones, like it was case, must have damaged it somehow.
However, now I'm on CM9, so no test mode for me, I'm achieving the same effect by bashing the back button, so I get semi-constant vibration. I know, It's ridiculous.
Have the same problem here, I think it's software related because the shut down vibration stopped working when I flashed CM9 ICS, I can't remember if it was working anywhere else though. But now I'm back to 2.3.5 and it's not working at all. Did a Factory Reset, Cleaned Cache before and after the flash. Also used the Jig to reset my counter. Any clues?
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
dajomas said:
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
Click to expand...
Click to collapse
I saw something similar on CM9 thread, they said it could be a "bad flash", not a corrupted rom but the lack of proper cleanup before and after the flash. But I cleaned up everything before and after and I don't like reconfiguring the whole phone again for nothing.
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
kweso said:
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
Click to expand...
Click to collapse
I assume since your posting in xda developers that you are rooted?
If so, just back up data with titanium backup app and factory reset, setup system and then restore USER apps and data only.
Sent from my GT-I9300 using xda premium
kweso said:
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
Click to expand...
Click to collapse
Did you install another rom?
My vibration for example didn't work with some cm10.1 nightlies
it started in cm10.1 20130203. then i tried wipe cache and dalvik. nothing. then i updated to 0206 (wiped cache and dalvik again) > still nothing. went to bed. got up. everything ok! its vibration again! i am 100% sure, it did not work, when i left it on my desk last night. this morning, i checked for missed calls and it took a moment until i realized: i got haptik feedback back on patternunlock and keystrokes! checked ringtone-vibration: fine as well!
dont ask me how! would still like to know for myself.
thx,
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
call me stupid!
suddenly this evening my phone stopped vibrating again. then i realized: quiet hours! i turned off haptik feedback at night.
could slap myself. at least ill find this thread again, next time i screw it again....
nite,
kws...
...tapatalking
Girls can use it again then. Good news for them!
Sent from the little guy
Related
ive searched for things such as "sleep crash", "sleep bug", "screen wont turn on" etc. but can seem to find anything that tells me anything other than turn off wifi (which i tried to no avail). My issue is that when i press the power button for 1 second to turn off my archos 70 screen it will not turn back on. Same thing happens when i let it fall asleep. If i leave it plugged in and not allow it to turn off screen i have no issues. My apologies if i just don't know what words to search for ... i tried. In on the .4 firmware (latest) with no mods. This has happened through the last 3 firmwares from archos. Any ideas?
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Techngro said:
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Click to expand...
Click to collapse
I will try this and report back. I have been installing firmware over the issue
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
I am try before formatting and report back
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
this worked!!
mallman said:
this worked!!
Click to expand...
Click to collapse
spoke too soon. did not work. it stopped after a few tries
it works again if i recalibrate but wont hold.
Zoidpilot said:
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
Click to expand...
Click to collapse
by the way, the deep sleep option also kills mine.
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
ramso said:
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
just tried it . i hit the icon to disable sleeping. i pressed the screen button and when i went to turn screen back on it would not wake. Did i use the app wrong?
No, you use the app rigth. The app only disable deepsleep.
Sent from my A101IT using Tapatalk
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
bbop said:
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
Click to expand...
Click to collapse
err I'm afraid that I spoke too soo. My device keeps getting stuck and won't awake from sleep. This seems to happen most after switching wifi on or off, specifically whilst the device is playing music.
Zoidpilot said:
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
Click to expand...
Click to collapse
how are you installing the firmware? maybe im doing it wrong. I let the device update to latest 2.1.4 and then i wiped it via the settings and repair menu in android.
Edit**
like this??:
Step 1: Download the android 2.2 firmware for your archos tablet from here,you might a get a false positive notification from your browser as they are unaware of .AOS format, so ignore that and download it.
Step 2:Go to Menu > Settings > Device Storage & USB connection > USB connection mode of your tablet and set the connection mode to Mobile Media Device (MTP) and now connect your Tablet to pc.
Step 3:Now when the tablet is detected you will see a hard drive icon,double tap and open it and copy and paste the firmware (.AOS) file into the hard drive(make sure you dont copy it in any folder inside it like Music,Videos etc).
Unplug the USB connection and the Archos device will automatically locate the update file and will prompt you for the update,just follow the screen options and you are done,if it does not prompt you for an update then you might have accidentally misplaced the file in one of the folders,just locate the .AOS file from the file manager and and open it to start the update.
No no it wasn't that complicated... It was actually the simplest fix for a difficult problem. My device when I got it was running 2.1.2 out the box... Even then It had the screen problem. When I got the chance I installed 2.1.3 OVER THE AIR. Straight from Archos. Still had the issue though, I figured it would have been fixed but was greatly disappointed... Then I sort of just lived with the problem for awhile... I saw that the 2.1.4 update was released but was wary about downloading it because sooo many people are having issues. Just the other day though, the device cut off on me again and I figured to hell with it... So I downloaded the 2.1.4 OTA as well... no website, no manual install, I just let the device run its course on its own. After the update, it rebooted normally and it's been working great since... Sorry to hear not everyone is so fortunate... I really hope this helps somewhat
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
Hello,
I bought recently the new SGS3 and after a week or two of using I noticed the phone loses all the sounds despite all of them are turned on and not being on minimum. After a while the sounds get back and everything works fine. At first I thought it might be from the settings because I set up silent mode for all notifications and I thought it may turn all the sounds off, despite it normally shouldn't. After playing for a while with the phone I realized the issue appears randomly without any reasons while I was playing game or simply navigating through the phone. If anyone had experienced the same issue or have an idea what could be the problem (software, hardware, settings, OS, etc) or how it can be solved, please respond. Any answer is appreciated as the problem is quite annoying as I'm missing calls because of it.
Thank you.
Phone details:
Samsung Galaxy S III
Android version - 4.0.4
Baseband version - I9300BOLF1
Kernel version - 3.0.15-782020
Build number - IMM76D.I9300XXBLFB
P.S. Restart of the phone doesn't help as I already tried it. The issues is related to all the sounds not to the vibration, the last works fine.
Backup data and factory reset.
Sent from my GT-I9300 using xda premium
JJEgan said:
Backup data and factory reset.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank you for your advise JJEgan, unfortunately it didn't help neither. Yesterday I did the factory reset and left it as it is, didn't restore any of my previous settings or apps, didn't install anything additional, just wanted to see if the problem will appear again, and unfortunately it did.
Anything else I can try or I should take it to a service?
Thank you
I have the same problem with notification sounds. The problem appears when i turn off notifications on apk like im+ or Yahoo messenger. Is there any other solution rather than factory rest?
Sent from my GT-I9300
mausxda said:
I have the same problem with notification sounds. The problem appears when i turn off notifications on apk like im+ or Yahoo messenger. Is there any other solution rather than factory rest?
Sent from my GT-I9300
Click to expand...
Click to collapse
maybe there is some loose..should send back to samsung
It happened to last night. I restored the phone using CWM and now is back to normal.
I have been rooting and installing custom roms for a while. I'm no expert, but now newb either. I recently rooted my S4. It's running on the stock verizon ME7 build.
The problem I have been having is that a few minutes after I reboot it all the sounds stop working. No music, notification or in call sounds. If I restart it goes away for a little while, but soon comes back. I tried factory defaulting it, which worked for a little while, but it recently started doing it again. The only thing I can think of is I installed avast Anti-theft with root access recently. Has anyone else had this problem & do you know of a solution? I can always try factory defaulting it again to see if that helps, but I would like to know if anyone else has any ideas.
Odined back
I tried everything I could thing of, then decided to Odin back to stock. Same problem started almost immediately . There are no system sounds and I can not hear anything when I call. Also it does not pick up sounds from my voice via voice commands & the person on the other end of my calls can not hear me. At this point I wonder if blocking is some how activated. Since Verizon was nice enough to prevent me from making changes to it I can't check.... Upwards on onward. I will keep this updated in-case someone else has this problem.
I have noticed that when I am in recovery, if I try to wipe the cache partition. I get a android on his back with a triangle exclamation point & then it reboots itself... Is this normal. I have never experienced this behavior before.
I installed the blocking mode MOD. It does not seem to be the problem. No sounds after using the phone for a few minutes. I guess its time to send it back. I really enjoyed the phone. But I seems like a received a bad one. Unless anyone has anythoughts.
When your sound stops have you tried to see if it is working with headphones or Bluetooth? If there is no sound using headphones or a Bluetooth device there's probably an issue with the phone itself. If you've done a stock Odin flash and its still doing it, I would have to guess the phone is bad. Send it back. The only problem you might have is if they check the flash count, you may end up paying for a new phone. I've never had to use Triangle Away to reset my flash counter, but I believe it needs to be flashed in a custom recovery (which you don't have).
Sent from my SCH-I545 using Tapatalk 4
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.