Having installed 6.0.1 a week ago and pulling out my hair ever since over the Vibration Off problem(glitch?) where you cannot get rid of vibrations on notifications, I finally found a possible solution.
I had tried all the forum posts which said "go through each app settings, DND mode, etc.etc.etc." and done exactly as stated and still had vibrations on notifications, which was driving me absolutely nuts!! Checked and double-checked and quadruple-checked etc.etc. each and every setting to no avail....
Until I remembered: Most of the Samsung range (and some other models) actually have push-tab type connectors on the internal boards.. So, I located the vibrator component on the board of my Tab 3 8'', undid it and put a piece of thin non conductive material between the tab and the contacts, and TADA!! Problem finally fixed with a sigh of true relief!
I would not recommend this method to people who aren't at least a little tech savvy, in case you damage the board of your unit.. But I did a quick google image search to find where the tab for the vibrator was on the board, simply clipped off the back cover of my Tab 3, unhooked that tab and put the material between the tab and the board so it could nolonger make contact..
It's the definitive way to disable the vibrator mechanism, at least until a patch is released to fix this flaw in Android OS.
Hopefully this will serve to help others, as I've seen many forum posts, especially on 'googleproduct' where others are pulling out their hair over this issue..
Related
I found this page
www[dot]wikitude[dot]org/enupdate-samsung-galaxy-3
...about problems with the Samsung Galaxy (not Galaxy S!) compass. The problems sound exactly like what I'm seeing with my Captivate (i.e. tilting the phone around any axis causes the compass reading to change erratically).
This page is a year old. Not a good sign, huh?
The test app on that page runs fine on my Captivate, but I don't know how to interpret the output.
(Apologies for the [dot]s in the URL above...apparently this forum is really zealous about keeping us newbies from posting links!)
Hey, just curious if you updated your phone to Froyo? Asking because it looks like the similar issue occurs on HTC Desire after OTA update to android 2.2 so wonder if there is some bug with new OS, not depended on the device type... Anyway take a look at the following thread in order to get more info:
forum.xda-developers.com/showthread.php?t=747398
Thanks for the reply. No, I haven't upgraded to Froyo or done any ROM flashing. I've rooted, that's all. Rooting was the first thing I did (I won't put up with no sideloading), and I didn't notice the compass trouble until later. I'm new to Android, so after I learn about backups I may do a factory reset and see if things are any different.
Try this to calibrate the compass:
Find a level table. On the phone go to Settings, Display, Horizontal Calibration. Put the phone face down on the table with the lower part of the phone hanging over the edge. Look under the phone and press the "calibrate" button keeping the phone face-down. Don't move the phone. It takes about 3 seconds to calibrate.
It fixed the compass for me the first time, but you may have to try it a couple of times.
unkarob said:
Try this to calibrate the compass:
Find a level table. On the phone go to Settings, Display, Horizontal Calibration. Put the phone face down on the table with the lower part of the phone hanging over the edge. Look under the phone and press the "calibrate" button keeping the phone face-down. Don't move the phone. It takes about 3 seconds to calibrate.
It fixed the compass for me the first time, but you may have to try it a couple of times.
Click to expand...
Click to collapse
Please look at the date before responding to a thread. This was from August 2010 and has either been answered or the poster has moved on. No need to resurrect 7 month old threads.
Hey guys,
This forum has been wonderful for me so I thought I would pass along my own personal experience with a couple of items.
First 'the Clip' case - great - I love mine. For those that have had concerns about the main home/back/menu/search buttons not being lighted, the clip is perfect for helping to find these keys. If you insert your tablet camera up (not upside down to uncover the usb port), the right hand clip is the perfect tactile way to find menu (just above) and back (just below). A good way to navigate these buttons in darker settings.
Second - the static/hissing/white noise problem people have experienced. I know several people have indicated it is a hardware problem and to replace your tablet, that was not an option for me as it did not start until after the 30 day return period. I have found, however, that if you set your screen to NEVER sleep and instead use the power buton to put the screen to sleep, it cuts down on the occurences significantly. Additionally, if it does happen (it has happened twice in the last week), it recovers for itself. You get the noise for ONLY the existing sound that is supposed to be playing and the next sound (whether it is a feedback sound, a notification, etc), it will have corrected itself. At least that's what my experience has been.
To all the developers out there (and especially roebeet) - thanks for everything, I love this tablet due to your hard work. I am running TnT lite 4.2.5 and am very happy with it.
how do you get the screen to never sleep?
Go to settings, display, screen timeout and set to never.
dwebww said:
Second - the static/hissing/white noise problem people have experienced. I know several people have indicated it is a hardware problem and to replace your tablet, that was not an option for me as it did not start until after the 30 day return period. I have found, however, that if you set your screen to NEVER sleep and instead use the power buton to put the screen to sleep, it cuts down on the occurences significantly. Additionally, if it does happen (it has happened twice in the last week), it recovers for itself. You get the noise for ONLY the existing sound that is supposed to be playing and the next sound (whether it is a feedback sound, a notification, etc), it will have corrected itself. At least that's what my experience has been.
Click to expand...
Click to collapse
I understand you in regard of this XD i've been having this sound problem, but bought mine overseas (i'm from Chile) and my brother threw the boxing into the trash, so doubt that there is a cheap way to replace mine .
Do you prefer some ROM in particular? Now i'm toying with VEGAn 7, but i can't play more than 2 or 3 mp3 songs without getting sound off, i'll try your "fix" to see if the situation improves
webman418 said:
Go to settings, display, screen timeout and set to never.
Click to expand...
Click to collapse
hmm.. I guess VeganTAB 5.1.1 doesn't have that option.. bummer..
i had to change the tablet language to english to find that option for some reason
I am a complete noob to smartphones and the Relay is my first.
I have a stock, unrooted, unmolested T-mobile $400 prepaid Galaxy S Relay 4G, did the update to Jelly Bean via wi-fi. I've already sent one in for replacement because of the following problems, and the new one behaved the same way.
1. The home screen and pulldown menu do not rotate by gyroscope regardless of the screen rotate setting. This would not be a big deal, except that when the phone comes out of the box, they do rotate (it also rotates to keyboard when keyboard is open). The current phone stopped rotating after I did the update but the old one definitely stopped rotating before then, not sure why or when. It seems subzerobob had this same problem but I can't find any resolution he might have enjoyed: http://forum.xda-developers.com/showpost.php?p=35827475&postcount=748
2. Every time the phone is turned off and on, the time and date setting reset to default which seems to be "automatic time/automatic time zone". This does not work for my purposes and I find it extremely irritating besides.
Can anyone point me in the right direction here or even just explain why these things are happening? I feel like I'm going crazy and can hardly find any similar complaints, and T-mobile has been useless, verging on hostile ever since I bought this cursed thing.
If I recall correctly, the chipset used by our phone has the persistent real time clock disabled by default. And not just in our phone, but any phone that uses it. Apparently there's some sort of bug in it. I believe the people putting together our CM rom have successfully enabled it though.
Hello everyone ... on my Nexus 5 once again happened some incredible problem with vibration ... Here's the thing: Last night my Nexus just lay on the bed and when I took it, at this point I found the lack of vibration. First, I turned on Vibrate when pressing the navigation keys, and found no vibration. At first I began to sin on the vibrating motor, but I remembered that I was already have this problem a few months ago, in the same way. When I downloaded from the Market program to test the vibration and turned her to work constantly, I found that the vibration motor that works but is very weak, as if barely barely turns .. As if he did not have enough energy. But! Motor is spinning so bad until not "turn off the screen." After blocking in a few seconds the vibration motor is working again as if nothing had happened! As well and clearly. However, once you unlock it as soon as the problem returns, vibration works very poorly. I have tried different programs for vibration control, no result. Found a video on YouTube of the problem, attach below. If the problem is simply to reiterate, I would like to know the cause .. This problem is very infuriated me yesterday, vibration at all almost no and I missed a few calls. I understand the engine is all right and I think that this is some sort of deep software problem...
I have already booked two motors, then try to replace, but not sure it will help .. Phone never fell or dropped, handle carefully. (but the body have a little small scratches ) A very long time looking for information on this issue on the internet, but found nothing ..
I dont want to go to the service center, I want to understand itself, with your help, of course ..
Factory reset or Reflashing ROM to any other doesn't help too...
Model - D281 16GB white.
ROM - CM11 Snapshot M9
Kernel - ElementalX 1.04cm
Recovery - TWRP 2.7.1.1
Can not listen to what people say on the video, the main thing to hear the vibration motor.
P.S. Sorry for my bad english, I'm from Russia and I write through Google translator... Hope on your help, guys..
So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.
Well, sadly I couldn't fix the issue with the voice notes, but I disabled the "ok Google" feature from the Google assistant and I haven't had any problem with voicenotes anymore, let's see if it stays like that.
It didnt solved the problem, I plan to go back to android 9
Does not feel any fix, but so frustrating 'couse battery capability is much much worse...
I think the fingerprint at least is faster and more reliable.
ferluna18 said:
So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.
Click to expand...
Click to collapse
I fixed the voice messages disabling the feedback tactile of 3 under screen buttons
Did the upgrade change your GPS functionality? Since the day I updated, my phone started drifting. I have 25 kilometers displacement on a day staying permanently at my home office. Compared to 0.5 kilometers before the update.
I didn't understand how you fixed the voice messages, can you be more specific?
Hey guys, it's July 9th and the last firmware released for xperia xz2 is 52.1.A.2.1, will Sony stop supporting this device or what? Btw my cellphone has now a ghost touch.
ferluna18 said:
Btw my cellphone has now a ghost touch.
Click to expand...
Click to collapse
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.
sersel2 said:
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.
Click to expand...
Click to collapse
Thanks for sharing your experience, well I still have the ghost touch but now occurs more often and I have had another issue since some months ago ad well and tje thing is that sometimes the proximity sensor "detects" it's being covered and makes the screen flash several times during a call or hearing voice notes in whatsap, sometimes the failure is as bad that I have to restart the phone, I don't know what could be causing this problem but I have to say that I have dropped some water in my cellphone in the past two or three times, and I don't know, maybe some of this water came into the phone through the earpiece and messed with the upper part of the screen and the other sensor up there, my phone os almost a year old now, Do you guys think it might mot be water resistant anymore? And btw, have you dropped water in the phone as well? Thanks for reading.