Hi everyone,
as lots of guys did i have done the hardware mod to my nexus 5 speaker module. I'm not satisfied by the results at all!
I know google has solved this issue with the new version of the device (I think now is rev 12) making speaker holes bigger and using a speaker module different.
i also know that lots of people had his terminal changed by google just simply calling then and telling them the problem.
Now I have to ways to follows.
1. buying online the new module... but i don't know where
2. the other is trying to call the support and trying to make me change the device (but i have modified it)
Any experience by you?
thanks
Related
Hi Guys,
well, the mic issue is not really an unknown to OPO users - I have never experienced such issue, but some time ago my mom let me know she has problems with mic for long time now (she has inherited my OPO), so there I went - looking for an intel regarding this issue.
I have come across some standard fixes for Cyanogen (the last official one by OPO themselves):
- blow out dust/debris from the microphones (done with a vacuum cleaner),
- remove TrueCaller, voice recorder, turn off "Ok google" recogniton (basically not a problem for us, we have Slovak language, thus no support anyway),
- tried other services - like Viber and it worked perfectly!
- tried speaker mode - worked!
So after this I came into the conclusion maybe a drop or something has damaged or something the rear mic for ambient noise suppression (maybe?).
But then I found some info the CnM is the problem itself, so I have just switched to the LineageOS (it is not really a change when I am thinking about it now, well is it?), but this has not helped, still the same problem.
I have found this too and applied too, but, again, no success.
Do you happen to have any other suggestion? How is it possible Viber works? Can be some app such as Viber used as the phone app too?
Thank you, in an advance...and I hope we will come to some conclusions here, I am wasted from all of this...
dropadred said:
Hi Guys,
well, the mic issue is not really an unknown to OPO users - I have never experienced such issue, but some time ago my mom let me know she has problems with mic for long time now (she has inherited my OPO), so there I went - looking for an intel regarding this issue.
I have come across some standard fixes for Cyanogen (the last official one by OPO themselves):
- blow out dust/debris from the microphones (done with a vacuum cleaner),
- remove TrueCaller, voice recorder, turn off "Ok google" recogniton (basically not a problem for us, we have Slovak language, thus no support anyway),
- tried other services - like Viber and it worked perfectly!
- tried speaker mode - worked!
So after this I came into the conclusion maybe a drop or something has damaged or something the rear mic for ambient noise suppression (maybe?).
But then I found some info the CnM is the problem itself, so I have just switched to the LineageOS (it is not really a change when I am thinking about it now, well is it?), but this has not helped, still the same problem.
I have found this too and applied too, but, again, no success.
Do you happen to have any other suggestion? How is it possible Viber works? Can be some app such as Viber used as the phone app too?
Thank you, in an advance...and I hope we will come to some conclusions here, I am wasted from all of this...
Click to expand...
Click to collapse
Just a little search,and look what I found!
https://forum.xda-developers.com/showpost.php?p=74316182&postcount=2267
Oh, I thought I will get around it without a root, thus why I did not try any of the "must be rooted" approaches. But yes, it is fixed now, however...
This is a very unwanted outcome - the phone has been used for recording band's sessions as well where the mic array was used fully, but now calls, yes, are ok, but the recording quality is horrid - basically it was recording like when you switch a call to the speaker mode, where other microphones were recording too and giving that full-bodied sound, now it is like through a gaming headset with a noise cancellation.
What is this issue caused by, anyway? Is it because of a damage of one of the microphones?
Anyone? The rear mic was really handy for the music recording (full sounding). Is it possible to make it somehow toggleable?
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
Hello there
I've recently buyed a Redmi 9 and the single bottom-firing speaker was not the greatest, so ive searched for earpiece sound mods and only found some apps that SWITCH the sound source to the earpiece, but disable the bottom speaker (i also find some mods that require rooting the phone, but the app one from Play Store did the trick just fine). And that make me wonder if the kernel is able to redirect the source to the earpiece why there isnt any app that "duplicate" it to both speakers.
Later ive found the various Xiaomi phones mods that people made on YouTube, but none to my specific phone, Im not afraid of rooting it but the redirecting app made me question if all the trouble was really need.
The final question im here to make is, is there any app that behave as i described on the begining of the thread, if not, the other devices mods can work on my phone (since there is no one specific yet) or it will most prbly have driver erros due to different devices?
Hello first things first I'm totally new to this forum and I'm posting my question cause I searched the internet for weeks now and I simply can't find a solution.
The long story befor is.... I got a blackview bv9600pro for free and wanted to put lineage os (GSI) onto it (cause the blackview software is packed full of bloatware) this worked quite well except for the sound so I thought.... maybe just try the never version los 18.1... but this completly destroyed the phone into a softbrick (I think it destroyed the boot.img). So to get it back running I needed to format&flash it with the sp-flashtool. But there might come in my problem... I Have no Backup !!! So I got the original IMG from the blackview Forum and used it.
So now I'm on the original blackview software.... needet to flash the imei back... working fine.... but now to the real Problem... The mic simply does not work anymore. Or at least thats what I thought. After a while of testing around I tested a mic test app and my mic seems to work fine in direct mode but not to work at all in comunication mode and basically all apps except for memo apps use comunication mode. So I dug in a little deeper and found that Blackview has its on "diagnostics" built in (I think in its recovery.img)..... so I did run that and everything has run well except it shows me my mic error "mic-spk loopback failed". So I dug in even deeper and if I'm not mistaken its used to loopback the mic cause many android devices have multiple mics but blackview cheaped out and only built in one. So my real and Final question is - does anyone have any idea how to fix my mic?
Thanks in Advance BIzZmarCk
Sorry you didn't get any reply. If you contact blackview's support, you may get a free phone out of that, just saying.
Hi there,
I'm not sure where to turn to at all and I'm sure if this firmware can be created and used successfully, there will be a lot of other users who will benefit from it. My issue is a little specific, but bear with me, I got myself a corsair virtuoso se headset for Christmas. I've set them up using the icue software on my PC, but when I used them on the PS5, the settings did not transfer. Google has revealed that the headset itself does not have any on-board memory for saving settings. It seems like Corsair doesn't really care about console gamers and I can't get help from them.
If there is anything that can be done to get my headset how I want it, I would appreciate it if you could point me in the right direction.
Is it possible to create a custom firmware with my settings and flash it directly to the headset?
Honestly, I don't even know where to begin. I've only ever rooted and flashed ROMs on my old S10.
Please let me know if this thread is in the wrong place or if it should be deleted.
Like I said, I am not the only one who has this issue with the headset, so if it can be fixed successfully, others may benefit as well.
My recommendation:
Add
VIRTUOSO RGB WIRELESS High-Fidelity Gaming Headset​
to front of this thread's title, thus mainly users having such a headset are addressed