Mainly all Viper4Android issues from what I can tell.
These are probably linked to one solution, but being able to fix these problems will be greatly appreciated.
1. As I turn on my phone and continue to plug in my headphones, the phone acts as if there are no headphones plugged, which in then returns me restarting the phone and SOMETIMES it will come up with the headset icon in the statusbar which normally means it is going to work.
2. As in the previous problem I said 'normally means it is going to work' SOMETIMES no sound plays at all from anything, not from speakers not from headphones.
3. Bluetooth. When I turn on and use a Bluetooth speaker, I hear a slight pop from the speaker as it connects and nothing happens then when proceeding to turn off Bluetooth knowing it's not going to work, no audio happens at all leading to me rebooting the phone.
4. And most of all the most annoying thing in somewhat having a working daily driver, whenever in my pocket or FACE UP in a DARK ROOM, the phone will just switch off. Nothing else happens I can't bring it back at all, I just have to hard reset (hold the power button for 20 seconds until it turns back on)
5. (Edit) Also half the time my microphone doesn't work. Leading to me needing to restart my phone.
My Phone:
OnePlus 3t
OOS Beta 10 (7.1.1)
Magisk (13.3)
Viper4Android
"Allow Mediaserver/Audioserver
Emoji One
OOS call recording enabler
ATM I have the Xposed framework because it is pretty stable, but these problems we're here before Xposed framework, so that isn't the issue
Anyone being able to help with these problems will be greatly appreciated
If you need any logcats or whatever just let me know how to do them, and I'll do it for you.
Thank you so much! ~Ryan
Related
Okay guys so I have a Moto X and an HTC Stereoclip.
Upon first pairing everything is fine and dandy. Volume levels are as expected. Once I disconnect when I get to the parking lot at work and reconnect when I get inside work the volume is SUUUUUUPER LOW!!! The only way to fix this is to go to my bluetooth settings on my phone and "forget" the HTC Stereoclip. On the initial pairing everything is okay again. There is no way I'm going to keep re-pairing it the long way each time I want to use the stereoclip.
The problem is with the phone though. As I have a Galaxy Note 3 that I use with the stereoclip as well but it has no volume issues pairing and re-pairing.
Do I have a bad unit?
I've noticed on mine, occasionally, the volume will be super low when I get back in my car. As soon as the song changes, or any other notification sound happens, the volume immediately jumps back to where it was (full). I haven't figured out exactly how to reproduce the issue, but since it only happens very rarely, I haven't spent much time on it.
Had the same thing sometimes on my Note 2. I'm guessing it's a bug, but I'm not sure what causes it, nor have I ever been in a position to really troubleshoot it when it happens. By the time I could troubleshoot, I forget about it.
Hi,
My Safestrap rooted phone started having call audio problems soon or immediately after upgrading from 4.4.2 to 4.4.4 (I337UCUFNJ4 ATT stock rooted ROM). I also installed Wanam Xposed and DroidWall and a few other utilities at the time. I since disabled Wanam Xposed in the framework. I finally figured out how to duplicate the problem reliably:
1. Reboot phone to start from known state. NOTE: failure even happens in Safe Mode!
2. Connect to bluetooth car stereo or Motorola earpiece (Media and Phone)
3. Make a call and everything works normally. Hang up.
4. Make or receive a second call. There is no audio in either direction. However, if I press a number key, I can hear a beep over the bluetooth and the other end hears a tone.
• I have not been able to find any way to get the Phone audio to start working again without rebooting. (ex: I turn bluetooth off and there is still no Phone audio.)
• Turning cellular radio off/on doesn't bring audio back.
• Media audio apps like Music player continue to work.
• It appears I can make calls all day long without bluetooth.
• "OK Google" detection often quits working, but in my short test above it seems to keep working even though Phone audio is not. I'm not 100% sure this is related.
Anybody know what's going on or have debugging suggestions?
Nevermind for now
I bricked my phone trying to restore a Safestrap backup, so for now I've reverted back to 4.4.2. My battery life was horrible in 4.4.4 anyway.
I had the same problem. Go to Google app , menu, settings, voice, ok google detection, turn off from any screen.
I have rooted my phone an year back and was using it without any issues. Now recently i wanted to cast the screen and installed some mirroring app. But then as it didn't work, i removed it. But then i observed that since then my phone is always going on speaker mode. In fact "Speaker On/Off" button has no effect at all while on the call.
Also bluetooth though detects the device, does not send out the audio signal to that device and remains on the speaker mode. Even headset after connecting shows the headset icon in the notification bar but music is played on speaker phone only.
Initially i thought it could be internal speaker issue but then even BT and headset are not working, which hints me that it could be software issue.
Has anyone faced something similar? Any suggestions?
Thanks in advance!
manojrpatil said:
I have rooted my phone an year back and was using it without any issues. Now recently i wanted to cast the screen and installed some mirroring app. But then as it didn't work, i removed it. But then i observed that since then my phone is always going on speaker mode. In fact "Speaker On/Off" button has no effect at all while on the call.
Also bluetooth though detects the device, does not send out the audio signal to that device and remains on the speaker mode. Even headset after connecting shows the headset icon in the notification bar but music is played on speaker phone only.
Initially i thought it could be internal speaker issue but then even BT and headset are not working, which hints me that it could be software issue.
Has anyone faced something similar? Any suggestions?
Thanks in advance!
Click to expand...
Click to collapse
You could try just rebooting your phone and or wiping your cache and dalvik cache in recovery but that probably won't do much but you could try. Last resort I would back up all my apps using Titanium Backup/ Super Backup and Google's own backup options in your settings then try a factory reset. Will wipe your phone except for internal data storage and ext SD card but might also correct what the issue is but it might not if this app somehow had root privileges and changed something in your system but didn't remove it when you uninstalled it. Wish I had a better option but that app did something to your phone I'm pretty sure of it. Make sure Google had your phone numbers and contacts backed up automatically or you will need to back those up separately with TB.
manojrpatil said:
I have rooted my phone an year back and was using it without any issues. Now recently i wanted to cast the screen and installed some mirroring app. But then as it didn't work, i removed it. But then i observed that since then my phone is always going on speaker mode. In fact "Speaker On/Off" button has no effect at all while on the call.
Also bluetooth though detects the device, does not send out the audio signal to that device and remains on the speaker mode. Even headset after connecting shows the headset icon in the notification bar but music is played on speaker phone only.
Initially i thought it could be internal speaker issue but then even BT and headset are not working, which hints me that it could be software issue.
Has anyone faced something similar? Any suggestions?
Thanks in advance!
Click to expand...
Click to collapse
If those mirroring/casting apps used root access and modified some files in your ROM, Then you can try one thing, just navigate to /etc You should see mixer_paths.xml file, This file handles all sound routing, and i guess those apps modified this only. If this is the case, those apps definitely kept a backup of original file in same directory.
Thoctor and Sahil.bhardwaj, thank you very much for your help. Actually i tried factory reset but it didn't help. So i unrooted the phone and guess what? It started working perfect. Any ways i wanted to give it to my Dad who does not need unlocked phone so i can live with it now and can experiment with my newly bought Qiku 360!
Sahil bro, actually your comment come little late so didn't get the chance to check that out, but logically it makes sense as long as the developer of the app is well matured to take the backup of mixer_paths.xml or any system files for that matter.
I have a problem with the headset icon wich is become permanantly enabled in the status bar. Now i cant hear music with the speaker and when people call me they cant hear me unless if i use the speaker.
Its really annoying. I cant make calls now.
Any help please?!
What ROM are you using? What if any, changes have you made?
If you long press on the notification that says "Headset is plugged in" you should see app info pop up, click on it and it will bring you to the phone app info, try clearing data there and rebooting. If not software it could possibly be the hardware is damaged some way.
i have an g7-L01 on android lollipo 5.1.1
it's working great since the update and everything was normal.
suddenly the icon of the headset doesnt want to be disabled even if i plug and unplug the earphones several times.
I tried the reboot and used others earphone but no luck.
no i'm stuck with the headset mode and cant talk or listen to anything without puting earphones.
kanass said:
i have an g7-L01 on android lollipo 5.1.1
it's working great since the update and everything was normal.
suddenly the icon of the headset doesnt want to be disabled even if i plug and unplug the earphones several times.
I tried the reboot and used others earphone but no luck.
no i'm stuck with the headset mode and cant talk or listen to anything without puting earphones.
Click to expand...
Click to collapse
Maybe try flashing lollipop again?
I have a converted T-Mobile OP6T running the latest 9.0.12 OOS.
Whenever I receive a call and have a Bluetooth device connected, either my Jaybird headphones or my car stereo, It's very hit or miss on whether or not I'll be able to answer it with the Bluetooth device.
If I receive a call, it will ring and I'll try to answer it with the button on my earbuds, and I'll get nothing. Sometimes I can pick up my phone and they'll be on the earpiece, other times I can't hear them at all. I have to hang up and call them back. This is the same with my car stereo.
I did not have this problem BEFORE I did a factory wipe last week, which seems odd.
Hopefully, someone has a solution to this, as it pisses me off daily.
Does anyone have any thoughts on this?
I've forgotten and re-added both Bluetooth devices multiple times with the same outcome.
Well, I was hoping someone had some input on this, as it's aggravating me daily. Maybe I'll try another wipe without restoring anything.
Same issue
Krunk_Kracker said:
Well, I was hoping someone had some input on this, as it's aggravating me daily. Maybe I'll try another wipe without restoring anything.
Click to expand...
Click to collapse
I have the same issue. When I have the phone connected to my car stereo bluetooth, I can make outgoing calls via bluetooth just fine, but when I answer the call, it goes to my earpiece. I have to manually switch it back to bluetooth.
I haven't found a solution yet and the issue has plagued me across multiple versions of OxygenOS. When I had the 6T on ASOP, the behavior stopped, so I know this is an OxygenOS issue and not a general Android issue. OnePlus must have the stack messed up.
Since my phone is rooted, I'll take a look at the bluez settings and see if I find something there.
Mine is 100% stock, does the same thing. Plantronics 5200 headset. If the headset is off, phone rings, turn it on, put it on, auto answers fine.
If the headset is turned on, on my ear, hit or miss it will answer, or default to my phone or watch, forcing me to hit the button to switch it to
the headset.