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.
Related
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Can't say I ever have any problem like that. Might be an app on your phone that is turning the volume down? I agree it's definitely not the button bug since you can't change the volume with those buttons without unlocking the screen.
Sent from my Galaxy Nexus using XDA App
appelflap said:
I noticed this from the beginning, but didn't pay much attention to it because I thought it was my fault. But it happens again and again and I'm sure I don't do anything to cause this.
The problem: often when I haven't used the phone for a while the ringer volume is mysteriously turned down to a miminum level.
I now lock the ringer volume with an app, so this kinda solved the problem for me. Nevertheless I'm wondering if there are others who have this weird volume behavior.
BTW this is not the "classical" volume bug that was solved a few days ago with the OTA patch.
Click to expand...
Click to collapse
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
coleburns said:
yep. since day 1. no idea what causes and it's definitely no app causing it as i returned to factory settings to test it out and i still had the same issue
i honestly think it's the placement of the volume buttons but really difficult to be certain, as sometimes i will find the phone on vibrate and i am 100% i haven't touched the volume button.
At least now i am know i am not going crazy as this has been my one and only gripe about the phone
what app are you using to keep the volume locked?
Click to expand...
Click to collapse
Ahhh thx, this was driving me bananas .. at least I now know that it can be mysteriously reproduced on other devices. I've tried to monitor my own actions but I'm also pretty sure I don't accidentally touch the volume keys. I didn't do extensive research because I just thought it wasn't worthwhile. But because I missed some calls lately because of this it is now pretty high on my annoyance list.
The app I'm using is Volume + (free version will do). Until now it seems to work well. It runs a background service and intercepts volume key presses events and pushes the volume back to a saved level. (Could have used that for the other volume bug)
mobilehavoc said:
This might be an app. For example the 1Password reader app changes your volume based on some setting in the app.
Click to expand...
Click to collapse
Always difficult to say, but I wiped my device a few days ago to root it and didn't install many apps yet (only twitter and thumb keyboard)
Luxferro said:
Does you phone have the update? If not, then I'd assume it is the bug.
Why would I assume that. Cause the bug picks up noise on the volume keys, which control volume of everything, ringers, media, notifications, ect. The buttons control different things depending on what screen you might happen to be on. So it's possible that the bug could change your ringer volume as well.
Click to expand...
Click to collapse
I've installed the latest update (build ITL41F). Maybe the fix doesn't cover all scenarios yet?
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
kam187 said:
Sounds like interference to me. The fix added a 2ms de-bounce time which is ALOT. What frequency is your network on? You should try fixing it to 3g just to check if that fixes it. If it does its most likely interference.
I wonder if you have a bad ground connection in it somewhere (hardware fault).
If you can tell me the frequency your network uses (or your operator and i'll look it up) I can calculate the GSM burst time and see how it fits in 2ms. Ironically the burst arrives when you're about to receive a call so its turning the ringer down just before it rings lol
Click to expand...
Click to collapse
My operator uses 900 MHz (for 2G) /1800 MHz (3g) . Operator is T-Mobile Netherlands
Btw I just accidentaly catched the bug doing it's nasty thing on 3g.
Anyone know where to report this?
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Highland3r said:
Can't replicate this myself, however before submitting this as a bug maybe worth checking out the logcat trace around the time the volume is changing.
With the "SAV" issue, I seem to recall someone saw overrun errors in the log around the time of interference.
You may find something similar in the log or likewise there maybe some entries in there detailing a rogue process doing something a bit wacky which causes your issues.
Click to expand...
Click to collapse
SAV issue, overruns start on line 4
I'm also having this issue using: ICL35F.I9250XWKL2.
I can't find a way to reproduce it. If/when I find more info, I'll try to keep up to date.
From preliminary tests I've conducted, I now find Talk 4.0.2-235179 to be the culprit.
I have notification on and its tone is Silent. If I'm chatting with someone and that someone replies, the volume changes to 0???
I've written an app that polls the volume and notifies when it changes. Later today I might post the code.
Talk in Silent
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
DoomFragger said:
Finally have a found the real reason. When Talk is set to:
Notification: System Bar;
Sound: Silent.
When a message comes and the chat is in foreground, the volume is changed to level 3.
The program I've made, once started, poles the sound level each 5 seconds and when it's different a notification appears.
To this post I've attached the .apk, its source and a silent ringtone to overcome this bug.
Click to expand...
Click to collapse
Thanks for your detective work. This is exactly what was causing my volume to seemingly change at random. It was especially annoying because some days I use gtalk quite a bit and other days not at all.
I linked to your post and this thread on the relevant Google Code Android bug report that someone had created back in December for the same issue. It can be found here if anyone cares to star the issue in hopes of giving this bug more exposure: http://code.google.com/p/android/issues/detail?id=22579
I can confirm the problem. It only happens with Talk in the foreground running and with the silent notification on.
Thank you very much, I got the new One X and was wondering if it was a software bug in HTC software....guess not
First off, if this has already been done then sorry im obviously blind, if not then i think its a good place to post any jellybean related problems and fixes that people have discovered.
so here goes, i updated from the ota on thursday the 12th of july i had a totally stock yakju device with the build number imm761 (JRO03c after update)
problems i have found so far are
1.after every reboot the, screen stay awake during charging option is ticked in developer settings
2.the google now command of navigate me home will take you to a random address near your home even after setting home address in navigation app and in latitude (as far as i can tell this is only happening outside the us)
3.lock screen will only ever say 99% charged even when in battery settings it reports fully charged
i have not found a fix for any of these issues nor do i know if they are just problems on my device (barring the google now navigate me home command)
so if anyone could report if they have the same issues or have found fixes please post here.
thanks
Now has stopped listening for the keyword "Google". After a couple days with out reboot it seems that Now no longer responds when I say Google. I have to hit the mic button. A reboot would fix it... but a weird bug to say the least.
GldRush98 said:
Now has stopped listening for the keyword "Google". After a couple days with out reboot it seems that Now no longer responds when I say Google. I have to hit the mic button. A reboot would fix it... but a weird bug to say the least.
Click to expand...
Click to collapse
yes i knew i forgot something thanks also the option to enable this feature randomly disappears
I have a big problem since I did update to Jellybean
My phone charge itself, without it connected to AC power or PC.
And when I want to charge the power source does not load.
Last night I put in charge and not loaded than when we closed and I pressed power button + down button.
and camera, how do I set resolution? I make pictures. PNG 720x1280 on ICS I could change the resolution,
Jealybean sucks
{
"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"
}
Shot at 2012-07-19
tuice said:
My phone charge itself, without it connected to AC power or PC.
Click to expand...
Click to collapse
You have reached the Holy Grail of getting power to a mobile device—this is not a problem/consider yourself very lucky.
I do not think this is too good for battery life, and actually not charge only indicate that charge
Probably hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
omrij said:
Probably hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I didn't have this before upgrading to Jealybean
tuice said:
I didn't have this before upgrading to Jealybean
Click to expand...
Click to collapse
That's a pretty common Samsung issue, usb port dirty, faulty.
Either clean it or go to repair.
leeskywalker said:
2.the google now command of navigate me home will take you to a random address near your home even after setting home address in navigation app and in latitude (as far as i can tell this is only happening outside the us)
3.lock screen will only ever say 99% charged even when in battery settings it reports fully charged
i have not found a fix for any of these issues nor do i know if they are just problems on my device (barring the google now navigate me home command)
so if anyone could report if they have the same issues or have found fixes please post here.
thanks
Click to expand...
Click to collapse
2) I'm in the UK and don't have this bug, ensure your home address is set correctly on maps.google.com and that when you click it the pointer is showing your house only and not a generic area.
3) Again, not experienced this. My lockscreen shows 'Charged' when at 100%
Sorry fella
I can't speak to the first two problems but I can confirm that it only charges to 99%. It's been that way on every ROM I've used since stock 4.0 so now I just say 'close enough'.
Taboobat said:
I can't speak to the first two problems but I can confirm that it only charges to 99%. It's been that way on every ROM I've used since stock 4.0 so now I just say 'close enough'.
Click to expand...
Click to collapse
i found after a reboot while plugged in it will go to 100%
cymru said:
2) I'm in the UK and don't have this bug, ensure your home address is set correctly on maps.google.com and that when you click it the pointer is showing your house only and not a generic area.
3) Again, not experienced this. My lockscreen shows 'Charged' when at 100%
Sorry fella
Click to expand...
Click to collapse
i have my address set in every possible place of my google account still no luck
I've never been able to get Google Now to start voice recognition by saying Google. I was beginning to think it was just a myth. Any ideas how to force it?
Sent from my Galaxy Nexus using Tapatalk 2
tuice said:
I do not think this is too good for battery life, and actually not charge only indicate that charge
Click to expand...
Click to collapse
Battery stats is what's responsible for indicating charge to my knowledge. Try wiping battery stats in CWM
tuice said:
I have a big problem since I did update to Jellybean
My phone charge itself, without it connected to AC power or PC.
Click to expand...
Click to collapse
I've seen this happen before on a brand new HTC X One, happened after about 4 days of being used. We let the phone fully run down and then just changed it, didn't come back again.
I've had the G4 since it was launched and until now been very pleased. A couple of days ago it started to turn the screen on by itself every time it timed out or I pressed the lock button... Unless it's plugged into a charger.
I've tried pulling the battery and uninstalling any recent apps I'd installed but to no avail.
Annoyingly, by the time I got myself to carphone warehouse to get it sorted I was just outside my 28 days.
Seen a lot of people having issues with the screen but can't find anyone having this exact problem. Anybody experiencing similar? Any thoughts? Cheers.
Sent from my LG-H815 using XDA Free mobile app
Guess there's not a lot of people suffering the same issue... Noticed something odd today with the battery. Never seen it drain this fast before, is there any way the screen issue could be related to the battery? It would kinda corroborate that the phone acts totally normal when it's charging... Trying to find someone else with this phone to try swapping batteries is... Difficult.
{
"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 LG-H815 using XDA Free mobile app
Factory reset.
Done it, twice.
Sent from my LG-H815 using XDA Free mobile app
Do you have a screen protector on? If you do, is it possibly covering the light/prox sensor?
Nope, no protector, and I often manually cover the proximity sensor to demonstrate more easily what the phone's doing. Screen times out straight away and them comes back on just as quickly.
Same issue here
Sorry to drag up a thread but ive been having this issue from day 1 and its driving me MAAAAD! Press the lock screen button, the second the screen turns off it comes back on and its on the lock screen (like it would if i used the power button to unlock it)
I turned on "show touch screen touches " in developer options to see if the screen protector was touching anything but its not As far as i can tell it looks like the lock screen sensor might be dicky/weak from the factory? Major sads considering its the button I use on a hourly basis!
Any help or ideas greatly appreciated, i dont really fancy taking it back after 4 weeks to have it sent of for months to be looked at/repaired
H815P suffering the same but mine is randomly. I hardly ever notice but sometimes I just look at the phone and the screen is on.
Also same issue it s wake up randomly, screen is on suddenly and turn off, any solution?
volkie1912 said:
Also same issue it s wake up randomly, screen is on suddenly and turn off, any solution?
Click to expand...
Click to collapse
do you use greenify on unrooted phone?
vati said:
do you use greenify on unrooted phone?
Click to expand...
Click to collapse
yea, i am using greenify on unroot phone
volkie1912 said:
yea, i am using greenify on unroot phone
Click to expand...
Click to collapse
That is the problem.
if yo use the auto hibernate in greenify, it wakes up the phone, turns on the screen than after hibernation turns off the screen. That is why I use only the manual hibernation. On unrooted phone it cause more battery drain than running the pr in the background
vati said:
That is the problem.
if yo use the auto hibernate in greenify, it wakes up the phone, turns on the screen than after hibernation turns off the screen. That is why I use only the manual hibernation.
Click to expand...
Click to collapse
himm thanks for your help, also if i rooted the phone, no anymore wakeups on lock screen?
volkie1912 said:
himm thanks for your help, also if i rooted the phone, no anymore wakeups on lock screen?
Click to expand...
Click to collapse
yes, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.
vati said:
es, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.
Click to expand...
Click to collapse
Thanks for info dude[emoji106]
Sent from my LG-H815 using Tapatalk
vati said:
yes, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.
Click to expand...
Click to collapse
Hi there! thank you for the post thread! I recently got changed of my LG G4 motherboard by LG as I had another problem, and since I got back my phone it keeps turning the screen on-off randomly. I tried to change the auto-screen-off setting you described (hibernation) but the screen keeps turn on and off itself every 15secs! I even changed the phone settings to no background processing at all but same thing on and off again.. I did several factory resets, even tried not to install any app or even update the basics ones and keeps doing it randomly. I dont know what to do here please any help would be appreciated :S:crying:
turn off daydream clock in display settings
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
choroz_niki said:
Hi there! thank you for the post thread! I recently got changed of my LG G4 motherboard by LG as I had another problem, and since I got back my phone it keeps turning the screen on-off randomly. I tried to change the auto-screen-off setting you described (hibernation) but the screen keeps turn on and off itself every 15secs! I even changed the phone settings to no background processing at all but same thing on and off again.. I did several factory resets, even tried not to install any app or even update the basics ones and keeps doing it randomly. I dont know what to do here please any help would be appreciated :S:crying:
Click to expand...
Click to collapse
turn daydream clock display settings
Hey its the sensors next the the front camera that is causing this i had this look reply typed and it just disappeared but long story short i noticed it didnt down it when the phone was facedown so i tried covering the sensors next to the front camera and it didnt do it at this point it could just be a program error or hardware problem idk how it turn off the sensors and it may look tacky but use something to cover the sensors and you should be fine im not 100% sure this is the problem im still testing but so far it works
Try disabling knock to wake feature. I recently noticed that I could tap anywhere and then again somewhere else, minutes later, and the screen would turn on. It was so sensitive that sometimes it would wake by just blowing on the screen.
To get to this setting, I created an activity widget using Nova launcher. (It's under the Settings -> Knock settings).
You can also use Better Battery Stats or Amplify to see what's keeping your screen on
fixed mine
Here you go...
Settings > Display > Motion Sensor Calibration
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.
Loudspeaker is useless on my Note 10+ and even on my sisters note 10 if you switch on loudspeaker during the call. Call qualiti is getting bad. Away like one or 2 meters cant hear me the other person. On my other samsung phone like a71 you can even hear me like 10meters far. And if you use viber no problems. Any idea somebody who have a same problem?
30 feet away? wtf? 2-3 feet max.
To increase volume you could try altering hidden user settings to increase it.
Or use bt Buds+ which work very good.
blackhawk said:
30 feet away? wtf? 2-3 feet max.
To increase volume you could try altering hidden user settings to increase it.
Or use bt Buds+ which work very good.
Click to expand...
Click to collapse
Sorry i used maybe a wrong english word. Speaker phone i mean not loud speaker sorry. When the phone is on speaker phone and am moving away like go to the other side of the living room my mum cant hear me but when we talk on viber no problem at all even from the kitchen my mum can hear mee clearly. My sister has a same note 10 she have a same problem her husband have a 10+ no problem at all...
banuszzs said:
Sorry i used maybe a wrong english word. Speaker phone i mean not loud speaker sorry. When the phone is on speaker phone and am moving away like go to the other side of the living room my mum cant hear me but when we talk on viber no problem at all even from the kitchen my mum can hear mee clearly. My sister has a same note 10 she have a same problem her husband have a 10+ no problem at all...
Click to expand...
Click to collapse
Maybe noise cancelling. Or firmware version.
Compare firmware and phone app versions of the phones.
Make sure the volume limiter is not active.
I'm running Pie, more options may be available on other versions. Try running the phone speaker volume control from 0 to 100% 3 times.
Clear system cache on boot menu.
Try in safe mode to rule out 3rd party app interference.
Don't go too nuts as this is a minor problem. Upgrading could cause more issues that are more troublesome than this! A factory reset likely won't solve this. Double check all associated settings. Samsung is notorious for "hidden" settings. Some can only be called up by a search in settings if you know its name
Some only if you double tap an unmarked setting box. Quit the box of surprises... even after 3 years I continue to find new things on the Samsung Pie/One UI firmware. One of the reasons I don't upgrade especially if the OS is fast, stable and fulfilling its mission. Security is not an issue in actual use unless you do something stupid.
blackhawk said:
Maybe noise cancelling. Or firmware version.
Compare firmware and phone app versions of the phones.
Make sure the volume limiter is not active.
I'm running Pie, more options may be available on other versions. Try running the phone speaker volume control from 0 to 100% 3 times.
Clear system cache on boot menu.
Try in safe mode to rule out 3rd party app interference.
Don't go too nuts as this is a minor problem. Upgrading could cause more issues that are more troublesome than this! A factory reset likely won't solve this. Double check all associated settings. Samsung is notorious for "hidden" settings. Some can only be called up by a search in settings if you know its name
Some only if you double tap an unmarked setting box. Quit the box of surprises... even after 3 years I continue to find new things on the Samsung Pie/One UI firmware. One of the reasons I don't upgrade especially if the OS is fast, stable and fulfilling its mission. Security is not an issue in actual use unless you do something stupid.
Click to expand...
Click to collapse
Thx for your time!!!
1. Yes i think also that can be a nois cancelling bec when we talk on phone we cant hear the background music not at all that means for mee here is some noise cancel active. But i cant found a setting to switch off at all no options for that to turn off. Maybe this is the problem maybe the phone thinks that my voice is a backround noice than cancel it. Any idea how to switch off?
2. Cant do nothing with the firmware its already updated the newest from everything.
3. "the phone speaker volume control from 0 to 100% 3 times."? Who can i do that? and why?
4. What is volume limiter?
5. This problem is a major problem for use like this a phone is useless and i will sell it bec in many situations we cant use the phone.
thx for you time
banuszzs said:
3. "the phone speaker volume control from 0 to 100% 3 times."? Who can i do that? and why?
Click to expand...
Click to collapse
Not sure why but sometimes it works.
banuszzs said:
4. What is volume limiter?
Click to expand...
Click to collapse
{
"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"
}