So when I just got the phone I set up the Peel remote app and had it working great. After I got all my other apps setup the way I usually do, I found my IR blaster no longer worked no matter which remote app I tired, not even the Peel app which worked at first.
By using another camera, I realized the IR led was not even firing when a remote button was pressed although the notification led would flash the usual blue. After awhile I finally figured out it was tasker causing this. With tasker disabled, the IR blaster worked just like it should but the instant I enabled tasker it would stop working.
Now my question is anyone else experiencing this and any thoughts on any workarounds? I value tasker more than the IR blaster but it would be very ideal if both worked
No one else having this issue? I'm sure I'm not the only one who uses tasker AND the IR blaster lol
I have Tasker running and the peel remote works just fine for me.
Figured out the cause
Just an update for anyone who runs into this.
I finally narrowed the problem down, it seems if I have any profile in tasker that uses the state of the proximity sensor as a context causes the IR blaster to no longer function. Thankfully the one profile I have that uses the proximity sensor as a context is fairly trivial so it's no problem to disable it. With that one profile disabled, everything works the way it should now, even with my other 21 profiles active and running
aameghoo said:
Just an update for anyone who runs into this.
I finally narrowed the problem down, it seems if I have any profile in tasker that uses the state of the proximity sensor as a context causes the IR blaster to no longer function. Thankfully the one profile I have that uses the proximity sensor as a context is fairly trivial so it's no problem to disable it. With that one profile disabled, everything works the way it should now, even with my other 21 profiles active and running
Click to expand...
Click to collapse
Thank you. So glad i found your post. I was have problem with my ir too but not because of tasker, mine was because of an app call Gravity. After seeing how proximity sensor affected ir, i switched it off and now my ir blaster is working great! [emoji1]
Sent from my SM-G925T
I'm glad I found your post, my peel remote worked fine to start with on my S6 but recently it stopped working, so today I downloaded and tried several different remotes but no luck. So I'm curious if you would be willing to help me out by telling me how to check the tasker like you did, please. Thanks in advance and God bless. - Joshua
aameghoo said:
Just an update for anyone who runs into this.
I finally narrowed the problem down, it seems if I have any profile in tasker that uses the state of the proximity sensor as a context causes the IR blaster to no longer function. Thankfully the one profile I have that uses the proximity sensor as a context is fairly trivial so it's no problem to disable it. With that one profile disabled, everything works the way it should now, even with my other 21 profiles active and running
Click to expand...
Click to collapse
Related
Hey guys,
New smartphone user here. I've had Nexus 5 for a few months now.
Lollipop is really well made and the new visuals are great. Everything seems to be working well so far, except for my compass. It does not work either in my Compass app or in Google Maps. I've seen a few threads where people lost some of their sensors, so I downloaded Sensor Box to see what it would find.
The magnetic sensor works properly, but there isn't a "compass" sensor in it. Are they different or is the compass position determined using the magnetic sensor? The GPS Essentials compass does work, but it feels very slow and it's all over the place.
Additionally, when I start my Compass app, it does not activate Location like GPS Essentials would, although, it fetches my current address properly on top of the compass itself. (see attachment)
Could it be just that the compass works in a different way in Lollipop and apps have to be updated for it? I'm completely lost. Any help would be appreciated, guys.
Cheers,
I am experiencing the same issue.
I'm also having this issue, only app I did get it to work with was Compass 360. But I really only would need it for Google Maps, so this is still very annoying.
Did anyone come up with a solution, or at least an explanation yet?
Or does anyone know where to file a bug report about such an issue?
Are you sure the APIs just didn't change with Lollipop? If one app works and not another, it may not be a Lollipop bug.
Kompass is dead on for me, no issues whatsoever. Try moving the phone in a horizontal figure 8 to calibrate the kompass and watch for electrical/magnetic interferences.
Hi
After downloading an app calles Sensor Box I saw that on my rooted device (sm-g3858) (stock rom) the orientation sensors, magnetic and gyroscope sensors are missing. Is there any way to add them? Are these sensors hardware based? GPS works fine for me so is there a way to implement these 3 mentioned sensor functions? Available in the phone are accelerometer and proximity sensor so I want to know if I can add the others by adding certain xml files
Pretorian187 said:
Hi
After downloading an app calles Sensor Box I saw that on my rooted device (sm-g3858) (stock rom) the orientation sensors, magnetic and gyroscope sensors are missing. Is there any way to add them? Are these sensors hardware based? GPS works fine for me so is there a way to implement these 3 mentioned sensor functions? Available in the phone are accelerometer and proximity sensor so I want to know if I can add the others by adding certain xml files
Click to expand...
Click to collapse
Sensors are indeed hardware. You can't simply "add" them. If my memory serves me, the only practical use of a gyroscope sensor is for Photosphere. Lots of devices are missing this. It's odd that your phone doesn't have a magnetometer. It's also odd that there's no orientation sensor. To be honest, I don't think that your phone is missing a magnetometer or orientation sensor. I mean, if you're watching a video or viewing a webpage and the display rotates, then clearly it has that sensor. And most phones have a magnetometer. Your phone (Galaxy Beam 2) is kinda a specialized device, so I guess it's possible that certain things common to other phones were omitted. If that's the case, it's unfortunate, but sadly, you can't "add" them via software.
Planterz said:
Sensors are indeed hardware. You can't simply "add" them. If my memory serves me, the only practical use of a gyroscope sensor is for Photosphere. Lots of devices are missing this. It's odd that your phone doesn't have a magnetometer. It's also odd that there's no orientation sensor. To be honest, I don't think that your phone is missing a magnetometer or orientation sensor. I mean, if you're watching a video or viewing a webpage and the display rotates, then clearly it has that sensor. And most phones have a magnetometer. Your phone (Galaxy Beam 2) is kinda a specialized device, so I guess it's possible that certain things common to other phones were omitted. If that's the case, it's unfortunate, but sadly, you can't "add" them via software.
Click to expand...
Click to collapse
thank you for your reply. Maybe that function is not activated? Samsung pretty much sucks when it comes to software support so maybe some files are just missing. Do you know where I could find the location of these files? The problem is that compass apps for example need that function (unless you know of an app that doesnt..)and I might not be suprised if Samsung just didnt add the files to /system
Pretorian187 said:
thank you for your reply. Maybe that function is not activated? Samsung pretty much sucks when it comes to software support so maybe some files are just missing. Do you know where I could find the location of these files? The problem is that compass apps for example need that function (unless you know of an app that doesnt..)and I might not be suprised if Samsung just didnt add the files to /system
Click to expand...
Click to collapse
I really couldn't help you with that. I doubt anyone could. I would suggest, however, that you try a couple other apps. Phone Tester, Sensor Kinetics Innovations, to name a couple. Also, some basic apps that use these functions. Most compass apps use the magnetometer, and there's also metal detector apps (obviously, you'll need something steel or iron, not just any random metal). And as I said before if you're viewing a webpage or video or something, and you turn your phone sideways and what you're viewing changes its orientation, then you've obviously got that sensor as well.
Planterz said:
I really couldn't help you with that. I doubt anyone could. I would suggest, however, that you try a couple other apps. Phone Tester, Sensor Kinetics Innovations, to name a couple. Also, some basic apps that use these functions. Most compass apps use the magnetometer, and there's also metal detector apps (obviously, you'll need something steel or iron, not just any random metal). And as I said before if you're viewing a webpage or video or something, and you turn your phone sideways and what you're viewing changes its orientation, then you've obviously got that sensor as well.
Click to expand...
Click to collapse
I tried Sensor Kinetics and when I change the orientation the Accelerometer is effected. So basically the orientation sensor is the accelerometer in this phone. And I can also see that in the demo option. But anyway I tried several metal detector apps and there is 0 reaction. So I guess thats it. Thanks for your time.
Wondering if anyone has any advice for my weird mic issue - it's a little different to the others I've seen but willing to try anything at the moment. Here's what I've found so far:
*People can't hear me when I talk into the phone. I've tried calling my home phone and listening and I don't hear anything either.
*This problem seems to happen when I'm holding the phone normally (i.e. against my face - ear to the ear speaker and mouth near bottom of the phone's mic)
*If I talk right into the bottom of the speaker (as in have the bottom mic and speaker right in front of my mouth), it picks up audio fine on the other end.
*Speakerphone appears to be fine so secondary mic is working fine.
*Done the usual clean the mic hole with pin (and compressed air), made sure my finger wasn't covering the mic hole, removed any cases, etc.
My suspicion is maybe the proximity sensor is doing something to cause the audio to cut out? I can't imagine the bottom mic being that directional that it picks up nothing in one particular direction while works fine in another.
Phone is bone stock S6 - SM G920W8 running 6.0.1 (Build G920W8VLU3CPC8)
I've already done a factory reset so this thing is as clean as it gets and still no luck. Help!
Apps could be the issue.
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
WSADKeysGaming said:
Do you have any apps or had any apps in the past that use the proximity sensor on your Galaxy S6? I know that I have had these problems in the past where certain apps that use the proximity sensor, such as the wave your device on and off app that I frequently use interfere with how the microphone detects how far away your face is.
Click to expand...
Click to collapse
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
syee said:
Not that I recall. I did boot the device up in Safe Mode (which should stop any third party app from loading) and the problem still occurred. I also tried it again after I did a factory reset and before I loaded any apps but that didn't help either.
I don't use the gestures at all so I don't think it's that but maybe the factory reset turns it on. I'll see if I can find it to check.
Click to expand...
Click to collapse
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Don't mention it!
There are so many settings nowadays that its hard to remember whats on and off, left and right. Glad I could help!
syee said:
Well, it looks like gestures were turned on by default. Turned them all off and then turned them on one by one and made a test call and found it's the "Smart Alert" feature that caused the mic to not work when near my face.
Thanks WSADKeysGaming for the reminder about the gestures! I completely forgot about it because I never used them.
Click to expand...
Click to collapse
Sorry for bumping an old thread, are you familiar with why the Smart Alert feature would do this? Thanks!
Guys!
Do you experience proximity sensor issues while answering calls on OP7P?
For me while I'm on calls. The display comes on and gets disturbed and get pressed by my ears all the time.
Also any idea of where the proximity sensor is located on OP7P?
Thanks ?
Yes, I'm having the same issues. While I'm on calls I often activate the notifications pulldown. It would be nice to know how to fix this.
If you pull down the notification shade, the sensor is located just above the fifth icon on the first row. IE behind the screen.
If you pull the shade all the way down it is above and between the third and fourth icons. Easiest way to describe it. Put your thumb over that area with auto brightness on to watch the slider move.
Annoying while on a call that the screen comes on.
I'm experiencing the exact same issue with the caller app.
I also tried to make a flip cover to turn screen on or off with a proximity sensor detection app and it didn't work either.
I search a little in engineer mode (*#808#) and found that there is multiple proximity sensor, the IR sensor work quite well but it doesn't seem to be the default one.
The default one seems to be the ultrasonic sensor which works really bad.
There is also a "TP" proximity sensor which seems to be a near field detection which seems to work if I move my hand near the screen.
The sad thing is that in dedicated app to use or test proximity sensor (and in antutu or else) only one proximity sensor is listed (The ultrasonic one I guess) so you cannot switch to use the one which is working well.
Isn't this in the wrong place? Shouldn't it be in the Questions and Answers section?
Mods?
Probably just here looking for a mod to improve the situation
Actually I was going to open a new thread in Q&A when I found this one with the same subject and problem.
Do you think I need to open a new thread?
Is any of you experiencing the same issue as I described in my answer?
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
I tried to with no luck but as I explain in my first message the IR sensor is only used when screen is off (that's why it could help with double tap to wake)
But when screen is on another or couple another sensors are used and you can't calibrate them.
I think ultrasonic sensor is used when screen is on.
Do someone tested proximity sensor with any app on the play store? (Like proximity sensor test)
Put it on a table and check if it's working, mine is absolutely not. If I hold it like I was about to phone it works a little but it's not impressive.
Since I got 9.5.7 (EU version) earlier this evening screen turn off when I make a call.
I'm having this issue since 9.5.8... It's very annoying and I'm really disappointed, I often turn on airplane mode during a call... I tried to calibrate but it doesn't work.
I'm very very frustrated
schmeggy929 said:
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
Click to expand...
Click to collapse
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
dallasnights said:
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
Click to expand...
Click to collapse
This...
I've been having issues with phone calls but more so with pocket issues.. When I had the 6t pocket mode kept the phone neutral but this phone doesn't seem to have an accurate prox sensor.. Is there a way to activate a pocket mode?
Sent from my [device_name] using XDA-Developers Legacy app
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
pinzarualex said:
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Click to expand...
Click to collapse
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
But I have had this issue since release.. Do you a link to this information? If that's the case maybe someone can look into the firmware and see if it's minor tweak that can fix it?
Sent from my [device_name] using XDA-Developers Legacy app
Jack_Sparrow_ said:
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Click to expand...
Click to collapse
Of course it didn't fix anything...
Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
j0hnee said:
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have reported this to Funk wizard on the OOS support thread and he said he cannot reproduce it anymore on the latest test build, so... We have to wait for next firmware release and see if that is indeed the case
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Vimes14 said:
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Click to expand...
Click to collapse
.
I just tried it myself and turning over the phone definitely muted the incoming call (with the phone open or closed) Also the palm gesture worked (cover screen only) but that was slightly more difficult as you really have to cover the whole screen for a couple of seconds.
I also used AndroSensor (and another app) and noted the proximity sensor was present but wasn't showing a reading. Obviously it is working (and works when holding phone to ear by turning screen off for example).
So I am not sure why it's not working for you.
.
apprentice said:
.
So I am not sure why it's not working for you.
.
Click to expand...
Click to collapse
Thanks for checking.
Did some more testing, the flip gesture seems to be working for incoming calls with the Google Phone app, and alarms created by the Samsung Clock app, but not the Google Clock app or Calendar notifications. Using the Google Phone app once the call is established, then the screen does turn off when held close to a head when folded. So seems like the sensor is working, in some situations, which means it is probably software related, rather a hardware defect. I really don't want have to reconfigure my setup up again.
The Google Phone app also has a setting flip to mute, which was not set. So I flipped that to true.
I had previously written a Tasker profile to mute everything (enter Do Not Disturb) on a Pixel 3XL, before Google implemented it at the OS level, so I may try that here.
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
apprentice said:
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
Click to expand...
Click to collapse
I think the problem is that the Samsung implementation is to hook into a small subset of their applications to do a local mute, where as Google implementation just invoked Do Not Disturb, which meant every application would mute, assuming they are compliant. I think DND was slightly flakey on OS9, but from OS10 onwards it was rock steady.
To bring clarity to my local behaviour, I enabled my Tasker method that engaged DND when the phone is flipped. Works in both folded and unfolded configurations. As a bonus with Join, I have a method that automatically distributes DND to my other devices.