I normally use a Macro in Macrodroid to activate Speakerphone when I am on call and phone is away from my ear. This help me do multitasking, easy way. I can manually activate and deactivate Speakerphone, but it slows down my regular working while on phone.
However, this is not working in Oneplus 6. I also tried Tasker profile, but it is not working as well. Does anyone have any idea how this will work on Oxygen OS? I looked in to Oneplus Forums and can see many users facing this issue with earlier OP devices as well.
P.S. I tried Auto Speaker app from play store and it did not work as well.
I do believe this may be achieved by Gravity Box, but I am not inclined to install Xposed as of now.
Update: some people on OP forum said that problem could be dialer. So I installed Google Dialer as default but It did not work as well.
samrat_castle said:
I normally use a Macro in Macrodroid to activate Speakerphone when I am on call and phone is away from my ear. This help me do multitasking, easy way. I can manually activate and deactivate Speakerphone, but it slows down my regular working while on phone.
However, this is not working in Oneplus 6. I also tried Tasker profile, but it is not working as well. Does anyone have any idea how this will work on Oxygen OS? I looked in to Oneplus Forums and can see many users facing this issue with earlier OP devices as well.
P.S. I tried Auto Speaker app from play store and it did not work as well.
I do believe this may be achieved by Gravity Box, but I am not inclined to install Xposed as of now.
Update: some people on OP forum said that problem could be dialer. So I installed Google Dialer as default but It did not work as well.
Click to expand...
Click to collapse
Why not have speakerphone on always, but deactivate it when the phone is near your ear?
nabbed said:
Why not have speakerphone on always, but deactivate it when the phone is near your ear?
Click to expand...
Click to collapse
Same principal is used in the macro, profile and app. It's not working.
That's Automation.
Any help?
Still haven't found a solution for this either.
samrat_castle said:
Any help?
Click to expand...
Click to collapse
I'm looking for this feature too... In resurrection remix 7.1.2 on nexus 6 the dialer has the option to activate the loudspeaker with proximity sensor, you could even set the reacting time. This feature is present even on pure nexus 6.0.1 but it's no more present since Oreo. Don't know why . Every option o app or trick I tried to emulate this feature is not working as good as the integrated one . We should try to dump the phone app , it's almost a replica of the Google one . I really miss this feature, because when I work on smartphone repair over a microscope, I could answer with my android wear and my smartphone over the desktop answer the call in loudspeaker mode
Related
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!
We should use this thread to discuss about the official Android 9 update for the Mi A2 Lite!
Cool, but many didn't get the update yet...
It has dark mode?
I am on Havoc OS 2.0, but it hasnt update... Maybe I will return to stock...
iniro said:
It has dark mode?
I am on Havoc OS 2.0, but it hasnt update... Maybe I will return to stock...
Click to expand...
Click to collapse
I thought it has the dark mode, but it hasn't. You can find it in the settings but if you activate it nothing happen..
I noticed that the performance is slightly better than Oreo. The phone runs faster and there are much fewer lags!
First I thought the battery drain got heavier, but after the second day it reached the normal drain, which we know from Oreo
Also I love the new stock launcher. It's like the Pixel-Launcher with the "at a glance" feature, just as the new navigation-gestures which we also know from the Pixel-devices.
00norman00 said:
I thought it has the dark mode, but it hasn't. You can find it in the settings but if you activate it nothing happen..
Click to expand...
Click to collapse
It has a dark mode but it's very limited. When you activate it the quick settings in the notification area and some colour accents on the home screen and app list will become dark. It will not, however, change any other colours in the OS.
I'm experiencing some serious lag at moments.
On oreo I barely experienced lag at all.
Any advice?
I'm having lag/stutter in recent tasks... It was way faster in Oreo and I preferred the vertical layout.
Sent from my Mi A2 Lite using Tapatalk
agamotto said:
I'm having lag/stutter in recent tasks... It was way faster in Oreo and I preferred the vertical layout.
Click to expand...
Click to collapse
If you have root, you can disable the StockLauncher and download another launcher from the PlayStore. Then you will have the vertical layout.
Updated mine in Austria by following the VPN method.
On first boot I face WiFi connection issues and also Bluetooth is not working fine. - resolved by the first reboot
I face a poor call audio distortion.
Videos, Music, etc. that uses the other loudspeaker is working fine but in phone calls using the other speaker I face massive saturation effects even with small volume.
I also tried to manufacturing reset my phone, without success.
best regards,
Mario
Correct. I updated mine yesterday and can confirm, poor call audio distortion. That thing drives me nuts.
The arrows on the network and wifi icons on notification is also a thing to remove, or at least give us the chance to remove it.
Besides that, i didn't see to much cases.
sandman01 said:
Updated mine in Austria by following the VPN method.
On first boot I face WiFi connection issues and also Bluetooth is not working fine. - resolved by the first reboot
I face a poor call audio distortion.
Videos, Music, etc. that uses the other loudspeaker is working fine but in phone calls using the other speaker I face massive saturation effects even with small volume.
I also tried to manufacturing reset my phone, without success.
best regards,
Mario
Click to expand...
Click to collapse
This is a widely seen bug for Pie which I personally find not acceptable in 'stable' release. Couldn't do a calls due to sound quality and reverted back to Oreo.
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you clear the Data of the Google Apps?
itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you clear the Data of the Google Apps?
streetspy said:
This is a widely seen bug for Pie which I personally find not acceptable in 'stable' release. Couldn't do a calls due to sound quality and reverted back to Oreo.
Click to expand...
Click to collapse
Can you detail how to revert to Oreo?
Sent from my Mi A2 Lite using Tapatalk
itwasmistake said:
I wasn't able to upgrade to 9.0. I tried VPN method and it didn't work. Can anyone help me?
Click to expand...
Click to collapse
Did you remove sim card and wipe all the things?
00norman00 said:
Did you clear the Data of the Google Apps?
Click to expand...
Click to collapse
I did.
itwasmistake said:
I did.
Click to expand...
Click to collapse
Mhmm, it only work for me when I used the CyberGhost-VPN-App (free trial). ExpressVPN or something else didn't work for me
Okay. So doing factory reset fixed the lag in recent apps.
But I did an antutu benchmark and the performance has dropped significantly from 78232 to 67477.
Anyone else can confirm this?
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
I have a rooted Indian version of OnePlus 8T.
Everytime I try to change my device props to Pixel props via directly flashing the pixel props file or using "Magisk Hide Props" module - the display brightness breaks.
While the lock screen is still okay and the brightness behaves normally but as soon as you unlock the phone it goes too dim. Sliding the brightness panel doesn't do anything and neither does disabling adaptive brightness. I've stumbled across months old posts about someone having the same issue with Oneplus 8 Pro but didn't find any solution there either.
Please, anyone let me know if you can somehow get around those problems?
Thank you!
Hi,
Did you find any solution. It seems that it breaks the highest available brightness on the device . I am not sure how to enable that
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
Removing the "system.props" from the module breaks the feature of the module
Inervo said:
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
Removing the "system.props" from the module breaks the feature of the module
Click to expand...
Click to collapse
Hi, Did you find any solution? I have same problem.
sjgoel said:
Hi, Did you find any solution? I have same problem.
Click to expand...
Click to collapse
I actually do have a *partial* solution to this. If you were changing the fingerprint to enable call screening or call recording in Google Phone, then the solution is to use Google Dialer Mod instead. It's a root app that has toggles which literally allow you to turn on Call Screening, Call Recording, and pretty much any other Google Phone feature you'd want to enable. No fingerprinting necessary. If you were trying to get other pixel mods, unfortunatley I have no answer to that.
Hey Everyone,
I was able to get all Pixel features like photos unlimited, call screen, hold for me in OOS using this Magisk Module.
But upon installing, the brightness of the device is set to low and completely broken so it doesn't change. Did anyone able to run it and fix this?
I was able to use it by going in to fingerprint and click add fingerprint which brings the brightness back to normal and quit the fingerprint by swiping in notifications and the brightness presists but that's not usable in long term
Edit1: Seems like I was wrong. All the features are getting turned off one by one.
Writing here for anyone who wants to get pixel features in oxygen os rather than AOSP.
I was able to solve the issue. All I had to do is delete the system.prop file from the module and install it. Now the photos shows unlimited uploads and I don't have the brightness issue.
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
As stated, removing the "system.props" from the module breaks the feature of the module
5ud0 said:
Edit1: Seems like I was wrong. All the features are getting turned off one by one.
Writing here for anyone who wants to get pixel features in oxygen os rather than AOSP.
I was able to solve the issue. All I had to do is delete the system.prop file from the module and install it. Now the photos shows unlimited uploads and I don't have the brightness issue.
Click to expand...
Click to collapse
I have same issue... I got call screening Pixel feature in Oxygen by changing device fingerprint but have same screen brightness problem.
Can you please some detail of how to delete the system.prop file in the module and then install it.
5ud0 said:
Hey Everyone,
I was able to get all Pixel features like photos unlimited, call screen, hold for me in OOS using this Magisk Module.
But upon installing, the brightness of the device is set to low and completely broken so it doesn't change. Did anyone able to run it and fix this?
I was able to use it by going in to fingerprint and click add fingerprint which brings the brightness back to normal and quit the fingerprint by swiping in notifications and the brightness presists but that's not usable in long term
Click to expand...
Click to collapse
Inervo said:
Hey,
Does anyone got a chance to have a fix for this? I have the same issue with a oneplus 8, and i can't find any solution yet..
As stated, removing the "system.props" from the module breaks the feature of the module
Click to expand...
Click to collapse
sjgoel said:
I have same issue... I got call screening Pixel feature in Oxygen by changing device fingerprint but have same screen brightness problem.
Can you please some detail of how to delete the system.prop file in the module and then install it.
Click to expand...
Click to collapse
I actually have a *partial* solution to this. If you are changing the fingerprint to enable call screening or call recording in Google Phone, then the solution is to use Google Dialer Mod instead. It's a root app that has toggles which literally allow you to turn on Call Screening, Call Recording, and pretty much any other Google Phone feature you'd want to enable. No fingerprinting necessary. If you were trying to get other pixel mods, unfortunately I have no answer to that.