Related
Hi there, I'm currently running Darky's Rom 8 on my Samsung Captivate and for some odd reason shortly after installing my accelerometer went dead. I can hear it role around and move when I move my phone but theres no activity with the accelerometer.
I'm not sure If its the ROM or if its my phone.
Any suggestions?
(Sorry if this thread is in the wrong place.)
KyleTroy said:
Hi there, I'm currently running Darky's Rom 8 on my Samsung Captivate and for some odd reason shortly after installing my accelerometer went dead. I can hear it role around and move when I move my phone but theres no activity with the accelerometer.
Click to expand...
Click to collapse
What? You can hear it roll around?
Ya you Should not hear it rolling around
Sent from my SGH-I897 using XDA App
That makes it sound bad. I can hear it (I think its it) with the battery and the back cover off and my ear against the phone.
KyleTroy said:
That makes it sound bad. I can hear it (I think its it) with the battery and the back cover off and my ear against the phone.
Click to expand...
Click to collapse
Flash back to stock and see if that fixes it. If it doesn't, then you have a broken sensor. If it does, then it's a rom issue.
My accelerometer sometimes doesn't respond, when switching screen modes in web browser or similar. Good thing I got insurance for my phone in case I need to get it replaced for any reason.
att8525user said:
My accelerometer sometimes doesn't respond, when switching screen modes in web browser or similar. Good thing I got insurance for my phone in case I need to get it replaced for any reason.
Click to expand...
Click to collapse
If the hardware fails in your phone it is a warranty issue not insurance.
So have tried this feature on both mine and my girlfriend inspire 4g and it doesn't work. But I have read of it working with the inspire. Whats up? We both bought our phones on the launch day, so maybe they fixed the feature down the line.
BTW I'm running coredroid 5.1 and my girlfriend is on the stock Rom. Its not a big deal breaker for me but I wonder why it doesn't work.
I have the same issue!! Flip-for-speaker hasn't worked on stock, nor does it work on any other ROMs i've tried. WTF?!? What's wrong with this phone??
Just tried the feature on mine and it worked!
Maybe there's an update for older phones that fixes it. Make sure to have the box checked in Sound settings, also.
Works here on TPC 2.0
i'm still completely stock, and i had it work one time, and it hasn't since. Everytime my phone rings i'm flipping it around and moving it and everything but it hasn't worked since.
I believe you need to answer it first then flip it over, you cant just flip it over when its ringing.
Oohhhhhh... you have to answer it first. Now I understand. Doh!
It also uses the proximity sensor and not the G-Sensor.. So the phone either needs to be upside down on a table or use your finger to cover the sensor... You cant just turn it over.
earhog said:
It also uses the proximity sensor and not the G-Sensor.. So the phone either needs to be upside down on a table or use your finger to cover the sensor... You cant just turn it over.
Click to expand...
Click to collapse
This may be why I could never get the feature to work..
Where exactly is the sensor located? In the mesh up top?
Guys, there's a better app at the Market that will launch the speakerphone in 3 different methods, "flip", "shake" or "move away from face". It's called "UpSoundDown" and I've tried it on my HD2. I use the more convenient "move away from face" to launch the speakerphone.
Oh I see now, you have to put it on a table for it to work. Wouldn't have thought of that. I just tested it on my phone and IT WORKS. Thanks a lot for the speakerphone tips everybody.
paganfx4 said:
Oh I see now, you have to put it on a table for it to work. Wouldn't have thought of that. I just tested it on my phone and IT WORKS. Thanks a lot for the speakerphone tips everybody.
Click to expand...
Click to collapse
Yup. That's a big 'DUH!' for me too. It's the table-top thing!
Works like a charm now.
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
strapabiro said:
Since I got the phone, while in pocket, I reject/answer 80% of the calls. I was under the effect of "yay nexus is back, google finally gave us a cheapster" so didn't really got bothered. But days are passing by and it's getting quite annoying, so to the point, could anybody tell me why this phone wakes up the screen on incoming calls when the proximity sensor is covered (ie. in pocket?) (if it's "normal" to do so, then why?). Proxi switch is fine, it triggers during calls and shows activity on sensor testing apps and whatnot. Default calls screen and whatsapp incoming calls, (heck I can unlock the phone with the fingerprint reader in my pocket without taking it out, now explain that.) ... Cherry on top the "slide to answer" thingy is vertical, so yeah there is the problem (while sliding it out from the pocket, it answers or rejects the call). I'm considering throwing it out lol it's so annoying lately. Android 9 was the same? (I had 3 android one phones to fill the superexpensive 3 generation pixel gap) Was I living under a rock? Can anyone try it? Thanks for the helpful inputs in advance.
Click to expand...
Click to collapse
There is no pocket mode on stock firmware. If you'd like to add one you can use Edxposed and the dark tricks module.
Sent from my Google Pixel 3a XL using XDA Labs
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
strapabiro said:
As hard as I'm trying, I start to see it's nearly impossible to be completely satisfied with the stock android experience. I gave up rooting, flashing, modding long time ago. Ain't got time for that. This leaves one choice, a sad but with time will get used to it.
Click to expand...
Click to collapse
Do all 3a do this? I am looking into buying one but don't want to deal with something like that. This is exactly the reason I decided not to buy Galaxy S10e - just try to Google "S10 proximity sensor". It was never officially acknowledged/fixed by Samsung and over the time people just seem to "get used to it" and stop talking about it.
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
strapabiro said:
I don't know mate, that's why I asked others to try it please, it's really getting on my nerves and funny thing is, these kind of problems are a hit or miss on warranty claims ... doesn't even worth to try ... and I don't want to take this to reddit either because it'll only get downvoted to a lower than hell level by biased fanboys not to mention the google product forums with the "platinum product experts" and their generic "try this and try that" answers.
So yeah I'm angry.
Click to expand...
Click to collapse
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
AndDiSa said:
I never had issues, but probably I don't understand the issue yet, so I have a question: how do you know screen is waking up in pocket? For sure it's waking up if you move the device, i.e. take is off the table or turn it around. Are you sure screen switches on in the pocket and not while you are taking it out?
Click to expand...
Click to collapse
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
You can test by trying to unlock the device while covering the proximity sensor.
Without any mods it'll unlock.
But like that's the main benefit to a Google phone running stock firmware. It's a perfect base for mods.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
This ... Or cover like 80% of the screen, leave only a small bar uncovered on the lower part of the phone (usbc port side) and ask someone to call you. You'll see on the remaining uncovered part that the screen woke up which is hilarious. Honestly at this point I don't understand how a feature like this can be overlooked by r&d.
Sadly modding is no option for me, for safety and other reasons.
There is another thread about this in the 3a xl section, hope it doesn't count as duplicate.
strapabiro said:
Sadly modding is no option for me, for safety and other reasons.
Click to expand...
Click to collapse
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
@strapabiro,
Have you tried this app?
Skittles9823 said:
What reasons? This is a Google phone. You're allowed to unlock the bootloader and flash modified software without breaking warrantee.
If you have issues, it's easy to just flash the factory image back to completely stock and relock the bootloader.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
strapabiro said:
You're shifting the subject, but the short answer is, imagine I never had an apple product in my life but I rather buy an iphone than start doing that But that's me and that's another topic like I said, thanks though.
Click to expand...
Click to collapse
Fair argument.
Sent from my Google Pixel 3a XL using XDA Labs
Today I had my phone in my coat pocket at an appointment for about an hour hanging on a coat rack not even being touched. When I came back to, the screen was on, on the lock screen, and if was pretty warm with battery down a good 25 percent. I'm wondering if what you're talking about here has something to do with this? I was confused why or what was going on with it. No unusual apps were in memory in developer settings.
kc6wke said:
@strapabiro,
Have you tried this app?
Click to expand...
Click to collapse
I have found this "feature" annoying as well on my 3a XL. However I tired the app that you suggested and it seems to work fine. Thanks for providing a decent solution to the OPs question.
Hello XDA,
I wonder if someone can help me with my issue in my S22 ULTRA. Each time I wear something tight or I get into a vehicle under some pumpy roads. I notice my phone power get clicked 3 times and calls the emergency service. It is weird and embarrassing and I noticed I cannot toggle this future off.
Is there any solution to my problem ?
Xila123 said:
Hello XDA,
I wonder if someone can help me with my issue in my S22 ULTRA. Each time I wear something tight or I get into a vehicle under some pumpy roads. I notice my phone power get clicked 3 times and calls the emergency service. It is weird and embarrassing and I noticed I cannot toggle this future off.
Is there any solution to my problem ?
Click to expand...
Click to collapse
Have you installed the Indian ROM? In India, this is mandatory for all smartphones.
Oh yeah, I remember I did that once for the calls recording feature. Is there a way around this or I'll need to reinstall the ROM back to its original one?
Xila123 said:
Oh yeah, I remember I did that once for the calls recording feature. Is there a way around this or I'll need to reinstall the ROM back to its original one?
Click to expand...
Click to collapse
Reinstalling the ROM for another region is the only way.
Thank you TheMystic, I will do that.