Good afternoon,
I have a T-Mobile Oneplus 7 Pro (had it for 2 weeks now), it is SIM unlocked at this time and I am waiting on the token from Oneplus which I should have this evening if the 7 day rule still applies.
Issues mostly started today and I have done everything except for a factory reset.
1) When I receive a phone call and answer it the phone is automatically on speaker instead of phone although the icon shows as phone. To fix during the call I switched to speaker then back to phone and it was fine. Next call in, same thing again. This just started today, prior to that it operated normally
2) Related to #1, when connected to the Bluetooth in my truck and a call comes in instead of being on Bluetooth like it had been it will be on phone (ear piece) setting. Again to correct during call I switched to phone then back to Bluetooth and works correctly, again until the next call comes in. This issue started today, prior to that it operated normally
3) No matter what I have my ring volume set at the phone will always ring very quietly, most of the time I will not hear it and miss calls due to this. I know the speaker is fine as I can set it to as loud as it'll go and you can definitely hear it as well as videos, but no matter what it keeps doing the low volume ring. This started last night, prior to that it operated normally
4) Certain apps when opening freeze and end up having to force close the app. I will attempt a second time opening and almost always the same thing happens again. I have uninstalled/re-installed these apps and that changes nothing. I also have a Oneplus 6t and a Note 9, both have exact same apps and they work flawlessly on them. This started yesterday, prior to that it operated normally
5) My wife also has the 7 pro and has the issue with #4 above as well. Thankfully thus far that is all she is experiencing with it. Her issue began about 3-5 days ago.
I am not certain what the issue is, but if someone has any ideas let me know as I am not changing this to international version until I know if the phone itself has an issue.
Thanks!
I had the Bluetooth speaker issue both ways as you explained. I had my Galaxy watch paired and allowed to receive calls I shut that off and seems to have fixed it for me.
GrimReaper316 said:
Good afternoon,
I have a T-Mobile Oneplus 7 Pro (had it for 2 weeks now), it is SIM unlocked at this time and I am waiting on the token from Oneplus which I should have this evening if the 7 day rule still applies.
Issues mostly started today and I have done everything except for a factory reset.
1) When I receive a phone call and answer it the phone is automatically on speaker instead of phone although the icon shows as phone. To fix during the call I switched to speaker then back to phone and it was fine. Next call in, same thing again. This just started today, prior to that it operated normally
2) Related to #1, when connected to the Bluetooth in my truck and a call comes in instead of being on Bluetooth like it had been it will be on phone (ear piece) setting. Again to correct during call I switched to phone then back to Bluetooth and works correctly, again until the next call comes in. This issue started today, prior to that it operated normally
3) No matter what I have my ring volume set at the phone will always ring very quietly, most of the time I will not hear it and miss calls due to this. I know the speaker is fine as I can set it to as loud as it'll go and you can definitely hear it as well as videos, but no matter what it keeps doing the low volume ring. This started last night, prior to that it operated normally
4) Certain apps when opening freeze and end up having to force close the app. I will attempt a second time opening and almost always the same thing happens again. I have uninstalled/re-installed these apps and that changes nothing. I also have a Oneplus 6t and a Note 9, both have exact same apps and they work flawlessly on them. This started yesterday, prior to that it operated normally
5) My wife also has the 7 pro and has the issue with #4 above as well. Thankfully thus far that is all she is experiencing with it. Her issue began about 3-5 days ago.
I am not certain what the issue is, but if someone has any ideas let me know as I am not changing this to international version until I know if the phone itself has an issue.
Thanks!
Click to expand...
Click to collapse
I have had the issue with #1 on the T-Mobile version few times. I switched to the international version and didn't have it at all. Switched back to the T-Mobile version last night and the first incoming call that I answered was that way. I think this is an issue with the T-Mobile version and it seems sporadic, at least on mine. Most likely gonna be switching back to the international version until I decide to to a JOD upgrade sometime down the road, plus the camera is so much better on the international version.
I have issue #2, like mikeb85, I also have a galaxy watch paired. I'll see if his solution fixes mine as well. Issue #4 for me seems to be related to restoring certain apps via OnePlus switch in my case. A fresh install of those apps (usually ones requiring permissions allowed by a pop-up) fixed that for me
Might be a good idea to just do a full factory reset just for safe measure. If it's still not working right, I would warranty a replacement.
I know it sounds like a cop out, but the only issue I'm experiencing is just the Ghost touching in the top right of the device.
Other than that, I just reboot and it's all good.
Related
Came across an interesting issue with my RAPH whilst away.
The phone would reboot when ringing, or making outbound calls, sometimes the call could be established and a conversation could be had for a random amount of time (never more than a minute) and the phone would suddenly reboot.
I fixed the issue by turning off bluetooth (might have been looking for my headset) and just changing every setting in "Phone" to something and then changing it back.
Havent had an issue since.
figured id post incase anyone else had this frustrating issue.
I guess this might be solved with a different Radio version.
what version are you in?
atreidae said:
Came across an interesting issue with my RAPH whilst away.
The phone would reboot when ringing, or making outbound calls, sometimes the call could be established and a conversation could be had for a random amount of time (never more than a minute) and the phone would suddenly reboot.
I fixed the issue by turning off bluetooth (might have been looking for my headset) and just changing every setting in "Phone" to something and then changing it back.
Havent had an issue since.
figured id post incase anyone else had this frustrating issue.
Click to expand...
Click to collapse
Are you using S2U2 by any chance?
Mine started doing it since i put S2U2 on but am not sure if its entirely to blame.
Hi all,
I have been doing further testing and can report that S2U2 is not the problem. Its a device issue that occurs when i roam to a GSM network. When on 3G its usually fine. I have just upgraded radio to the .28 to see if this helps.
Both myself and my brother who have the same devices are seeing the same issue. I have seen it on the 3 rom and also the HTC asia rom hence why im looking at radio now.
I tried Radio .32 with no luck. Tried a few different ROMS as well, ROMEoS, the HTC ASIA update as well as the updated 3 ROM with no joy. Shame cause the phone is great apart form this "showstopper", back to my ever trusty Blackjack until a new handset arrives.
I'm on NextG btw, and problem occurs when swictching between GSM, Edge and HSDPA. Unfortunatey both home and office are in spots that switch between signals depending on where I am in the house/office, very frustrating. I'm also 90% sure it only happens when a call and data are happening at the same time, as my phone syncs wth Exchange, this is regularly.
I rang HTC support, they suggested a hard reset, which of course I've done many times, otherwise return for repair/replacement.
Not sure if it's a phone issue or Android Auto issue but I'm not getting a pop-up in Android Auto when a call comes in so the only way to answer the call is to swipe my phone. I did a reset on the phone today for other reasons but I swear it was working before. Can anyone think of a setting that's blocking this? I've checked the Android Auto permissions and they're all checked.
Sent from my MHA-L29 using Tapatalk
Little more info. I deleted and repaired my car to my phone, rebooted the phone, deleted and reinstalled Android Auto and still the same thing, no call control. Messages work as they should with an on screen pop-up.
Sent from my MHA-L29 using Tapatalk
No such problems here. All works as it should. Not sure what to recommend.
Got it finally. I unplugged the phone and stayed connected to Bluetooth. Called my phone from another phone and the call came through on the Ford sync 3 system giving me the options to accept or reject. I accepted it and while in the call plugged the phone back in which brought me to the call screen in Android Auto. Hung the call up and while still in Android Auto I called it again and the notification showed up and gave me the call screen when I clicked it. Unplugged and retried again about 5 times and the notification pop-up and phone screen work as they should.
Sent from my MHA-L29 using Tapatalk
same issue
Having the same issue, will try your solution. Thanks!
Sorry to resurrect the thread but I wanted to thank you for the solution. While my Pixel in 7.1.2 was working no problem, having to switch out of the M9 just for this issue wasn't ideal. Followed the outlined steps and sure enough, I can take calls as expected whether I'm connected to Auto or not. Turns out the 100th Google search is the charm. Thanks!
Same issue with huawei honor 8
I am having the same issue with the huawei honor 8, and the fix does work for a time. The darn issue keeps coming back, which is obnoxious. Any one have an idea of what is causing to bug?
i heard its an EMUI issue and not an issue the phone particularly, and its up to Huawei to fix this. Im having the same issue which is tough considering i just came from a galaxy s7e that gave me tons of issues, but worked perfectly in AA
Hello! I'm going to need some help on someone that might know more than I do.
Here's the challenge:
Phone: Samsung Galaxy S7 AT&T Unlocked (G930A)
Build: G930AUCS4BRA1 (latest)
This phone has two really hard to pin down issues that will surely make a challenge.
First one, is the microphone. Calling or receiving a call makes the person on the other end to hear themselves. It is not explained by the other person using speakers, since it happens 100% of the time, even testing it with the express instruction to not use a speaker.
What the hard-to-pin-down issue is? It doesn't happen with any other calling program. I can voice call from WhatsApp or from an app from my provider using Wi-Fi or 4G and the issue disappears. Only happens if I receive or make a call from the phone without using Internet.
Second one, is a new one that happens randomly. The phone freezes, shuts down and restarts in a loop, about 3 or 4 times, and then works normally. Happens about 2-3 times a day and started two days ago, without any physical damage as a cause.
What has been done to try to fix this issue?
Cleared cache
Phone reset
Installed updates (twice, one from 6.0 to 7.0, and then updated the build number), once by using Odin, and the other one to update from SD Card.
Nothing has fixed any of these issues.
Any ideas?
Hey guys,
since amazon is out of stock - and therefore, getting a replacement device is kind of difficult - and I'm still waiting for oneplus to respond, I'd like to hear from you if you encountered similar issues with your OP6:
During calls, I can hear the other side just fine, but the person on the other side can not hear me most of the time. Sometimes, it seems some shreds of voice are being transmitted. It happened on about 90% of calls. There are calls that are perfectly fine, but most of the time, the phone is unusable.
What I could test so far:
- it happens in handset mode, speakerphone and with a bluetooth headset
- it happens on both SIMs, swapping them does not change anything
- it happens on 2G as well as 3G (no VoLTE available yet)
- the microphone works fine if I use the audio recorder (outside of calls)
- calls made via VoIP-software seem not to be affected, though audio quality on the other side isn't that great either (but that might be unrelated)
- sometimes, it seems to happen mid-call
Both SIMs did obviously work fine in my previous device (OP3), signal strength in calls is about -70dBm, both SIMs are on T-Mobile (Germany).
I'm on an A6003 with OOS 5.1.5, Baseband is MPSS.AT.4.0.c2.10-00012-SDM845_GEN_PACK-1.147963.5, bootloader is unlocked and rooted with Magisk.
I did find a thread describing similiar issues on the oneplus-forums (https://forums.oneplus.com/threads/dual-sim-issues.838595/#post-18474985), but I'm currently unable to login to their forums, for whatever reason.
Can any of you guys give me a hint on what to test to narrow down if it's a hardware or a software issue or maybe even suggest a workaround?
I'm happy to provide more details where necessary.
I'll probably have to switch back to my OP3 anyway, so I could give the Android P beta a shot and see if it happens there as well.
Best Regards.
So, it turns out (*after* factory resetting and flashing Android P of course ><) that the echo test number I've been using is equally broken on otherwise working phones, so most of my test results are null and void. I'll give it some more testing...
Just a heads-up for users who may stumble upon this thread in the future: call quality problems are mostly gone after updating to 5.1.6 (and replacing SIM-cards).
I've bought a OP6 just three days ago and I've updated it immediately to OS 5.1.8 (I've also rooted it) and the phone calls problems (call drops and other person can't hear my voice sometimes) are present.
I hope OnePlus will fix the issues not so later...
Unfortunately, I can't rule out that replacing the SIM-cards actually fixed the issue - it might be worth a shot. I haven't had any issues since my last post.
Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.
This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.