Related
Got it this afternoon... Noticed that the volume keeps turning full down to mute with no input from me...
Faulty phone or a software issue? Anyone else seen this?
R
Sent from my Galaxy Nexus using XDA App
rakh1 said:
Got it this afternoon... Noticed that the volume keeps turning full down to mute with no input from me...
Faulty phone or a software issue? Anyone else seen this?
R
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
You're not alone. There's a few people begin to report they have the SAV-Ghost issue (self-adjusting volume) in this thread: http://forum.xda-developers.com/showthread.php?t=1352545
You are not alone. A handful of people commented on that at in the 24hr thread. I named it the SAV -ghost. (Self adjusting volume ghost)
Thyrus said:
You are not alone. A handful of people commented on that at in the 24hr thread. I named it the SAV -ghost. (Self adjusting volume ghost)
Click to expand...
Click to collapse
Surely it should be either self-adjusting-volume or volume-adjusting-ghost? It can't be SAV-ghost because if it's a ghost adjusting the volume then it's not self adjusting!
Lol you have a point there. Lol. Damn there goes my contribution to android -naming the first galaxy Nexus bug.. ah well I still call it sav-ghost
HooloovooUK said:
Surely it should be either self-adjusting-volume or volume-adjusting-ghost? It can't be SAV-ghost because if it's a ghost adjusting the volume then it's not self adjusting!
Click to expand...
Click to collapse
It's a ghost he can convince the phone to adjust the volume by itself. Come on everybody knows that.
Sent from my HTC Desire using XDA App
Questions regarding this issue:
Does it only decrease volume?
Can you reproduce it?
how often does it occur?
Any apps you have installed that might interfere with volume in any way?
maybe this was the reason for all the delays, sounds like a software problem especially if they released the phone, can't be hardware if they knew of this issue
Well too early to say I would need some info to narrow it down.. I don't think it is sw at the moment. I twittered some other experienced users and they're have not seen such on their device. So could be user app related (market apps) or hw batch issue.
As far as I can remember this was occurring when the phone was vanilla. Only ever adjustable down. Have fought it several times with up volume but it is like the down volume key is locked on. However, down volume key appears fine so I don't think this is mechanical.
R
Sent from my Galaxy Nexus using XDA App
justabrake said:
maybe this was the reason for all the delays, sounds like a software problem especially if they released the phone, can't be hardware if they knew of this issue
Click to expand...
Click to collapse
Did they officially release the phone ?
They just put ICS on the SGS2 phone I wonder how's that working out
i have this problem. Hope its not hw issue.
randypurcz said:
Did they officially release the phone ?
Click to expand...
Click to collapse
I thought the release date officially was the 17th
They released them didn't they, they just didn't appear out of the sky,
This must be the reason why all the delays on this Recall if it's a hardware for sure software can be fixed,
I know they said they ported ICS over to the SGS2 phone I'm wondering if that has the same problems if not then it's hardware for sure
thought it was just my imagination at first....i hope it is software, i have already unlocked the bootloader so byebye warranty
happening to this many people, it seems software, not hardware related
tried experimenting, making sure that there was no way there was any pressure on the volume key
one thing which seems to confirm that it is software - hold volume down, dont let go, and then hold volume up at the same time. the volume goes up instead of having a battle....anyone concur?
that and, in bootloader mode it doesn't seem to be cycling through the options when left alone for a while
garok89 said:
I have already unlocked the bootloader so byebye warranty
Click to expand...
Click to collapse
Not true, it is relockable like Nexus S. Not like Nexus One.
Sent from my Nexus S using XDA App
Righty then, really willing to help you guys.
garok89 said:
hold volume down, dont let go, and then hold volume up at the same time. the volume goes up instead of having a battle....anyone concur?
Click to expand...
Click to collapse
Thats actually normal. This is how it is supposed to behave, no battle anticipated. Same behaviour on my 3 phones.
Again, my questions:
- Which volume is affected? Media volume, ringtone volume or all volume (master). When this happened, what did the display say which volume is being adjusted?
- Up and down, or down only (ie decrease only? or up down as it wants)
- If you have seen it adjust volume and it says "Media Volume", did it also happen during a call (which would then say call volume or similar). It is really important as both volumes are actually independant from each other. Meaning if more than one type of volume is affected, it may point more towards hardware than software. I can hardly believe that ICS or any app for this matter would trigger this behaviour in different threads/apps.
- Can you reproduce it? If so, please help us with logs to see whether HW or SW (see below)
- Can you interrupt this behaviour by either holding VOL up or VOL down? If you can interrupt it, does it keep doing it or would your interference stop the SAVing for a while?
- State of phone. Was the phone in use or did that happen with display off (if you come back after a while and the Volume is lower?
- If it did, go to the settings and volume - are all volume bars now lower or only one?
So, as far as I heard, it even happened with vanilla handset without apps right?
can you guys execute DDMS (comes with the Android SDK) and check the logs?
i.e. when it happens, you will be able to see the debugger code lines. The code as to WHEN and when it happens would be very important to see whats causing this behavior. Little pic attached for those that want to try
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you reproduced the issue, copy the relevant lines (you can verbose the log) here?!
The volume ghost happened this morning again when my alarm went off. I was already awake and I heard my alarm go off with just one beep and then silent. When I picked it up I saw the volume was down again and then had a battle with it pressing volume up but the phone was insistent on going down. So it must be all volumes getting turned down and not just ringer volume cause even if phone is on silent, the alarm should still go off as normal. At least it did on my N1.
Moral of the story, don't trust the alarm to wake you up cause it may just turn itself down leaving you sleeping in.
I am hoping its sw related cause I love this phone and don't want to return it!
Sent from my Galaxy Nexus using XDA App
@seakins please have a look at my questions. Also check when it does that are all volume settings down or just the one (alarm in that case)
I'm having the same problem. It usually happens when i unlock the phone, but has happened at other points, too.
I really hope this isn't hardware-related.
---------- Post added at 08:25 AM ---------- Previous post was at 08:23 AM ----------
Thyrus said:
@seakins please have a look at my questions. Also check when it does that are all volume settings down or just the one (alarm in that case)
Click to expand...
Click to collapse
In my case, it's just notifications and ringer. Media and alarm volume are unaffected.
For some reason the notification sound and vibrate won't work on my Galaxy Nexus for long periods of time even though they are set to. It doesnt matter what the notification is for, text message, facebook, gmail, etc I will not get a sound or a vibrate to let me know, just the LED will flash. It will be like this for hours and then work for a bit and then stop working again! What is going on? I'm running stock 4.0.2
For me sounds work but vibrate for notifications doesn't
Sent from my Galaxy Nexus using Tapatalk
karallam said:
For me sounds work but vibrate for notifications doesn't
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Go into settings that are in the sms app and select vibrate always, it will be way at the bottom
Sent from my Galaxy Nexus using XDA App
For me I have absolutely no clue what the problem is. I know its not settings because I have looked everywhere plus it goes back and forth between working for a bit and not working for a long time all on its own. I've even tried a factory reset and the problem persists. Could it be a hardware issue?
Sent from my Galaxy Nexus using xda premium
Same problem for me, vibrates for phone calls, and when shutting down, also when turning volume down, but not for any other notifications. (Yes, I set all the individual settings to "vibrate".) Must be a bug with the phone, lots of others are complaining about this problem as well. Hopefully this will be fixed with an update.
bovineyard said:
Same problem for me, vibrates for phone calls, and when shutting down, also when turning volume down, but not for any other notifications. (Yes, I set all the individual settings to "vibrate".) Must be a bug with the phone, lots of others are complaining about this problem as well. Hopefully this will be fixed with an update.
Click to expand...
Click to collapse
Have you looked here in the sms settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus using XDA App
Just tried Sound Manager V2, and set vibration to "vibrate whenever possible". Now all is well! Disappointing that this setting does not work in Android settings though.
So I know this thread is pretty old but I never did find a solution to this problem and thus got rid of my Galaxy Nexus and went to an iphone for a while. I have a galaxy Nexus again and am having the exact same problem. I have done everything everyone has suggested and trust me it has nothing to do with settings. For a while notifications will work as they are supposed to but then they will suddenly stop working properly (won't vibrate or make the sound) until i reboot the phone and then it will work for a short period before not working again. I've tried a factory reset and all that fun stuff and nothing helps.
Sound Manager V2 worked for me
Same issue here, and Sound Manager V2 fixed the vibration issue for me. Had every vibrate setting I could find set to always vibrate and yet my phone would only vibrate on the vibrate only setting.
I hate to bump an old thread... but, it perfectly explains my issue. Has anyone ever discovered the cause or a fix for this? All of my settings are properly enabled. The issue seems to occur any time I switch the phone to "vibrate" mode, using either the volume rocker or the power menu. Whenever I try and turn the volume back up (again, either via volume rocker or power menu), notifications stop completely, except for the notification light. Reboot fixes the issue each time. But, it's very frustrating, and reminiscent of the BlackBerry days of battery pulls. Ugh!
same problem
same here -_-
I rooted my Sprint Galaxy S3 last week and have had some problems with echoes since then on the normal handset and on Bluetooth. This is after finding suggestions to turn off noise reduction. I didn't have this problem prior to the rooting. I used this tutorial at this link http://forum.xda-developers.com/showthread.php?t=1743780. I have not been able to find anyone else with this problem, I do have backups using Titanium afterwards and have tried it again and even without the backups. Any suggestions appreciated.
"This video will show you the latest and easiest method to root the Sprint, ATT, T-Mobile and Rogers Samsung Galaxy S III! No data will be wiped. If you have any questions at all, please ask! THIS WILL WORK ON 4.1.1 JELLY BEAN"
Are you running a custom a Rom?
Sent from Pluto.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No just the stock ROM
Anyone? Should I try a new ROM?
Anyone? Should I try a new ROM?
Try a different ROM, if its still happening, its most likely a hardware issue
I dont think theres any "setting" that rooting it could have changed and introduced the echo
Sent from my PG06100 using xda premium
I can try one, I wasn't doing this until the root, its the stock ROM now. Any ROM suggestions?
same on tmobile
yeah i'm having a similar problem too on my tmobile s3 but it only happens when i have a custom rom(i tried a couple custom roms and they all seem so have the same effect). when i go back using my nandroid back up of the stock rom and kernel, the problems not there anymore... and turning off noise reduction seems to work for some ppl but not mine. i noticed that the closer u talk to the bottom of the phone, the less echo there is. so maybe the second mic on top is reacting too?
-------------------------------------------------------------------------------------------------------------------------------------------------------
i'm new to this, so any tips would b nice!:laugh:
I'm having the same issue -annoying echoes on my phone after rooting. I figure it's probably part of the beast - I'm finding my S3 to be a very strange bird indeed.
Sent from the house halfway up the next block
echo
sparkie6point0 said:
I'm having the same issue -annoying echoes on my phone after rooting. I figure it's probably part of the beast - I'm finding my S3 to be a very strange bird indeed.
Sent from the house halfway up the next block
Click to expand...
Click to collapse
Mine has just started doing the same thing. any fix?
I did a dirty flash and it fixed the problem
Sent from my SPH-L710 using xda app-developers app
Rooted GS3, stock Touchwiz
I was having the annoying echo when calling anyone on any set, any carrier. Noise cancellation on or off, did not make a difference. had tried to disable all sorts of voice activation....nada.
So got frustrate and did a full data wipe. After setting all accounts and apps back to normal (no nandroid and/or titanium baks), problem was solved! I was so relieved!
One day I accidentally opened S voice by clicking home twice, then called my wife after some time....hated echo in my ear was back!
I then rebooted to recovery, cleared cache and dalvik a couple of times and made another test call.
All back to normal.
I'm thinking about forcefully removing S Voice (should be called @$$ Voice)....
NOTE: as S Voice is a system app, I think to remove it I'd need to fiddle with the system/app folder and remove the apk...however, the application can actually be disabled! Will report back on results
Maybe BT is the issue?
So yesterday I kept S Voice disabled from app manager, then I would connect and disconnect from my car's bluetooth as I needed. The echo would still return and it would only go away if I rebooted. I also did the eq/sound check for right/left ear available from the dialer's menu just to rule it out: no difference. Echo still there. Rebooted phone, called from car BT, no echo.
As of now my last call after a reboot was fine, no echoes. I will keep the phone in the current state but WILL NOT turn off BT as I usually do during the day to save battery. Wil test later and report back.
One more thing, i noticed when the echo appears on BT, it also appears using the gs3 normally talking from it.
Echo is gone, day 2
Hello Everyone!
So I've been watching my phone since my original post here last week. I have to say there was nothing really I could pinpoint that would cause the echo. Noise cancellation ON or OFF, on my car's BT or not, on the phone's original wired headset...echo will go away ONLY if I rebooted a couple of times or did a factory reset from recovery. Mind you, the fix would only last for one or two calls. After that I'd have to either reboot multiple times or go to recovery and reset everything. So......
I finally broke down and called Sprint for a repair/diagnostics. Fortunately there is a center right by my house! Unfortunately it'll cost me between $50 and $100 just for the appointment...
I then proceeded to reset counters (gigantic thanks go to chainfire for his triangle-away which I bought to support the team!) un-root my GS3, remove apks than might hint at a rooted phone, rebooteed.
And what do you know? Echo is GONE....
It has been 2 full days and many calls (my wife is an angel....) made without a reboot or a factory reset.
I also have to add that since I was getting tired of TouchWiz, yesterday afternoon I replaced my launcher with Apex.
Does anyone think the launcher would affect the echo issue in any way?
BTW I always use qbking77's root/unroot instructions. Thanks go to him for always having an answer and a way!
Hope all this helps anyone in fixing his/her GS3 because it is in the end a great phone, and if a definite solution is found, I'll sure root my phone again!
Suddenly i got an issue with earpiece. It's almost impossible to hear a word from call (GSM and whatsapp). It's too low. I have to press it hard against my ear to hear it clearly. It suddenly happened. No clue about how did it happen. Tried "mixer_path.xml" edit, but it gets denied saying "read only" file. I'm on Oxygen OS 4.0 official (Rooted). Tried freedom OS too. but the issue still presence.
Does anyone know a fix for this?
Thanks
Unfortunately, I am coming with bad news. You should open an RMA and send your device to service center. I had this issue too, i sent back my phone and they replaced the earpiece in it.
tamasturcsek said:
Unfortunately, I am coming with bad news. You should open an RMA and send your device to service center. I had this issue too, i sent back my phone and they replaced the earpiece in it.
Click to expand...
Click to collapse
Oh wow. Then it's a hardware issue. Wonder is it okay if i change it myself.
GTRanushka said:
Oh wow. Then it's a hardware issue. Wonder is it okay if i change it myself.
Click to expand...
Click to collapse
You can, only issue is, no OE spares are available in the market.
For anyone with a Low In-Call voice handset volume problem. What this means is if you are on the phone with someone in a voice call with the phone up to your ear and not on speakerphone and you have a hard time hearing them, then you try to turn up the volume on the side of the phone but its already at max volume then try this.
TWRP-Low-InCall-Volume-Fix.zip >> https://www.androidfilehost.com/?fid=673368273298967516
This is a TWRP flashable file that corrects the file 'mixer_paths_tasha.xml' which is completely missing the entries to boost the volume.
I had this problem and it corrected it on most Oxygen OS based Roms.. I am using 'FreedomOS-CE-op3t-nevax-2.9-signed.zip' and its working SO GOOD!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guys for any one with low audio :i have change 3 earpiece for this 3 weeks and using this sound mod but allways i had low volume ,the last time i changed the earpiece i cleaned under the earpiece (i removed the protection under the earpiece) and there was very but veryyyy dust,i cleaned every bit of dust since i see the light from earpiece in front of the display i used the hairdryer ,and now i can hear very well.
I also have this problem. Earpiece speaker volume is very low! Is there any solution at the moment? I don't have root on my OP3T.
I had to clean the earpiece mesh with a soft brush. The holes are so small, the oils from our face and the dust close them shut. It's not a sofware issue and not a speaker hw failure.
Creeper36 said:
For anyone with a Low In-Call voice handset volume problem. What this means is if you are on the phone with someone in a voice call with the phone up to your ear and not on speakerphone and you have a hard time hearing them, then you try to turn up the volume on the side of the phone but its already at max volume then try this.
Click to expand...
Click to collapse
Thank you thank you. Call volume is now loud and adjustable with Creeper36's patch above. For other average users or folks coming from google, I followed GadgetHacks "Root Your OnePlus 3 or 3T & Install TWRP Recovery" article (minus the SuperSU zip install for root, that kept crashing my device). Root is not necessary for this patch just TWRP. Once TWRP is installed, put Creeper36's zip in an accessible directory on your phone, reboot into TWRP recovery, select "install", locate the low volume patch, and go for it.
Brace Your Selfs Long Post Coming (WITH FIX)
Guys the solution is simple ...!
Let's tell you my story. I was a very satisfied OP3 user, until one day .... my speaker volume was so low i could not even listen to a person at a room without any noise. (3 months ago) .
My first thought was that the problem is from the rom (Was using FreedomOS BETA at that time ) so i changed to FreedomOS Stable but the problem was the same , let's try again changed to Stock rom problem still there .
So let's go on and try the roms (Lineage Os , Mokee Os , Resurrection Remix , etc ) every rom had the same issue Low volume.
Next thought might be a problem from the earpiece (got some spare earpiece parts from ebay ) they arrived, i changed the earpiece .... slightly more volume but still useless.
Ok let's try mixer_paths changed the max volume to 95 but issue still there ... I was disappointed i thought it was a motherboard problem ... i gave up ... after some days my screen cracked but it was working ( I love my OP3 and i bought a new LCD ) .
Then after i got the part i changed all my parts to the new Screen .
The volume of the earpiece like magic goes back to normal .
So i took the old screen (cracked but still working) and cleaned the earpiece's grill (after you remove your earpiece there will be probably a black layer of Speaker Cloth remove that too and then you will see the grill ) , it had a thick layer of dust in it , i used some alcohol an old toothbrush a little force at the grill and after i removed all the dust i putted the old earpiece and the cloth back in (the first i thought it had a problem ) I reassembled the phone and volume was like new ....
If you are in warranty it's not a good idea if not try it the simplest solution was the correct one .
Creeper36 said:
For anyone with a Low In-Call voice handset volume problem. What this means is if you are on the phone with someone in a voice call with the phone up to your ear and not on speakerphone and you have a hard time hearing them, then you try to turn up the volume on the side of the phone but its already at max volume then try this.
TWRP-Low-InCall-Volume-Fix.zip >> https://www.androidfilehost.com/?fid=673368273298967516
This is a TWRP flashable file that corrects the file 'mixer_paths_tasha.xml' which is completely missing the entries to boost the volume.
I had this problem and it corrected it on most Oxygen OS based Roms.. I am using 'FreedomOS-CE-op3t-nevax-2.9-signed.zip' and its working SO GOOD!
Click to expand...
Click to collapse
So I flashed this through TWRP (using OP3 with stock updated Oxygen OS), and now I have no sound at all.. How to fix?
[SOLVED] - I HAVE FINALLY SOLVED THE PROBLEM
ITS NOT THE HARDWARE ISSUE ITS NOT A SOFTWARE ISSUE AND ITS NOT A EARPIECE ISSUE
SOLUTION
1) REMOVE SCREWS
2) REMOVE BACK COVER
3) REMOVE THE MOTHER BORAD
4) REMOVE THE EARPIECE
NOW IF U SEE BELOW ULL SEE A NET REMOVE THE NET AND THEN TAKE A BRUSH
1ST CLEAN THE NET
2ND CLEAN THE GRILL WHICH IS ON THE SCREEN (ONCE U CLEAR JUST CHECK IN THE LIGHT IF U CAN SEE THINGS CLEARLY FROM THE GRILL - ONLY USE LITTLE DEO SPRAY)
5) PUT EVERYTHING BACK AND BOOT PHONE
job well done!!!!!!
use the below video if you don't know how to open the phone
https://www.youtube.com/watch?v=TVHO3CVt8hs
GTRanushka said:
Oh wow. Then it's a hardware issue. Wonder is it okay if i change it myself.
Click to expand...
Click to collapse
Since I live in Mexico, trying to get an RMA from OP is almost impossible.
So, I ordered an ear speaker for my OP3 from Aliexpress, and I replaced it using this video:
https://youtu.be/TVHO3CVt8hs
And no, there is no difference, the problem still persist. In an local android repair center, they guy there told me that the earpseaker from the OP3 is similar to the ones other phones have, so I may try to use other earpseaker from other phone but I don’t expect that to fix this problem.
karan.champaneri said:
[SOLVED] - I HAVE FINALLY SOLVED THE PROBLEM
ITS NOT THE HARDWARE ISSUE ITS NOT A SOFTWARE ISSUE AND ITS NOT A EARPIECE ISSUE
SOLUTION
1) REMOVE SCREWS
2) REMOVE BACK COVER
3) REMOVE THE MOTHER BORAD
4) REMOVE THE EARPIECE
NOW IF U SEE BELOW ULL SEE A NET REMOVE THE NET AND THEN TAKE A BRUSH
1ST CLEAN THE NET
2ND CLEAN THE GRILL WHICH IS ON THE SCREEN (ONCE U CLEAR JUST CHECK IN THE LIGHT IF U CAN SEE THINGS CLEARLY FROM THE GRILL - ONLY USE LITTLE DEO SPRAY)
5) PUT EVERYTHING BACK AND BOOT PHONE
job well done!!!!!!
use the below video if you don't know how to open the phone
Click to expand...
Click to collapse
Can confirm this works, mine was really blocked. Couldn't see daylight through it. Had to scrape the muck and dust from inside front cover.
Nice and loud now.
Sometimes my phone's vibration is not working, I need to shake it first before it start working again. It clearly is a hardware problem. Just want to ask if anyone had this problem too. And if you have some advice that will be totally appreciated. Thank you.
Yeah i realized my phone not vibrating when i receive phone calls even though i set it to vibrate.
did anyone found a solution? Mine does the same, tried everything. sometimes the vibration is there and sometimes it's completely gone ...
sometimes the vibration feedback comes back after shaking the phone heavily. So I guess it is a hardware problem (loose connection)
michielbangels said:
sometimes the vibration feedback comes back after shaking the phone heavily. So I guess it is a hardware problem (loose connection)
Click to expand...
Click to collapse
if shaking the phone triggered the vibration, then i suggest you contact samsung for repair or replacement.
Hi, you aren't alone. I got the exact same problem on my A7 2017.
Have the same problem. It has occurred after the oreo update.
Hello, everyone... I'm from Brazil, and I have the same problem too. I've just shaked heavily my Samsung Galaxy A5 2017 and it came back to works...!! Definitely looks like a hardware problem. :-/
patz0110 said:
Sometimes my phone's vibration is not working, I need to shake it first before it start working again. It clearly is a hardware problem. Just want to ask if anyone had this problem too. And if you have some advice that will be totally appreciated. Thank you.
Click to expand...
Click to collapse
ogirdornavi said:
Hello, everyone... I'm from Brazil, and I have the same problem too. I've just shaked heavily my Samsung Galaxy A5 2017 and it came back to works...!! Definitely looks like a hardware problem. :-/
Click to expand...
Click to collapse
+1 for hardware problem. facing the same issue for a320
need to share it heavily or until it wont work anymore, need to open the backdoor, open using screwdiver, find the vibration module on the bottom right part of phone. i need to hit it couple times until the vibration work again.
but i have to test the vibration first, is it still work or not by using + & - cable (power source = 5v)
like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same problem here. I was using google's keyboard because.... because Samsung had to cheapen a great phone via software penalties. Whatever. All they had to do was put in a smaller battery. I'll be romming this sucker up probably past the S 12. Plenty of bloatmobiles to hose down in between. Have your vibrator, Samsung, you earned it. Save some for the carriers, too.
Dial *#0*# (If it not works, then use *#9998*842#
You can test a lot of features
If vibration didn't work give the phone good shake
If not then it HW
So, still no solution for this? Has anyone determined if the vibration module itself or the connection to it is the most likely point of failure? The vibration unit costs about 3 Bucks, I'm more worried about the waterproof seal after opening it...
I had an A5 and about 4 or 5 months in the vibration was not working properly. I just kept it off. It would work and then just quit and mess up my texts. I was using google keyboard to get the feedback. But obviously that never panned out.
Samsung A3 (2017) Vibration Unit Repair - The Incomplete guide.
Okay, because nobody asked for this, here's my update in a new thread.
I don't know if people will see my post.
But I solve it. My A5 2017 doesn"t vibrate suddenly.
In a first time I thought it was a software problem.
So I factory reset my A5 2017 but the vibrator doesn't work.
I formatted my A5 2017 using the sofware Odin on my computer in a second time.
But the vibrator doesn't work again.
I read before after shaking the phone the vibrator work for a few time.
I shook my phone and pressed Down/Up inputs to switch my phone between Vibrator/Sound mode. The vibrator ran just one time.
Finally I call the *#0*# and select Vibrator.
Nothing happened.
I shook hard the phone during the *#0*# vibrator test and suddenly it began to vibrate. And I let it vibrate during whole the test (around 10/20 sec).
My A5 2017 run perfectly after day after day.
leo31 said:
+1 for hardware problem. facing the same issue for a320
need to share it heavily or until it wont work anymore, need to open the backdoor, open using screwdiver, find the vibration module on the bottom right part of phone. i need to hit it couple times until the vibration work again.
but i have to test the vibration first, is it still work or not by using + & - cable (power source = 5v)
like this :
Click to expand...
Click to collapse
Are you on crack?
Here are the facts:
Vibration working BEFORE Oreo update.
Not working AFTER Oreo update.
Here is a misguided, foolish assumption:
This a hardware problem.
This is an intelligent response:
WHAT?
GAMPAWA said:
Finally I call the *#0*# and select Vibrator.
Nothing happened.
I shook hard the phone during the *#0*# vibrator test and suddenly it began to vibrate. And I let it vibrate during whole the test (around 10/20 sec).
My A5 2017 run perfectly after day after day.
Click to expand...
Click to collapse
Worked for me. But not for long.
The vibrator runs fast, slow, or not at all. Definitely a hardware problem, but it's long out of warranty now.