CAll Quilty HAck VoCOdeR - Droid X General

Step 1. Dial ##7764726
Step 2. Enter 7 0's as the password (Zeros) Verify.
Step 3. Select 04 Vocode
Step 4. Select EVRC - B
Step 5. Apply and Phone will reboot.
The above was the old way of going in on Froyo, now the Gingerbread method is
Step 1. Dial ##7764726
Step 2. Enter 6 0's as the password (Zeros) Verify.
Step 3. Select 06 Test Mode, select next, and next again...
Step 4. top pull down menu Select EVRC - B
The problem is that on some phones the 3g is effected and/or after a reboot it doesn't hold? Some have experienced significant improvements where others don't hear any, any thoughts??
Jedi

What exactly is this supposed to do?

Jmoney47 said:
What exactly is this supposed to do?
Click to expand...
Click to collapse
Enhance call quality,
"There are many reasons why the audio quality of mobile phones isn’t great. One simple, but fixable reason is that the phone is most likely configured to use an outdated voice encoder algorithm by default.
Luckily for us, Motorola includes hidden programming menus in most of its phones where we can adjust advanced settings like voice quality."

All this did to mine was make it so I couldnt hear anyone, and they couldnt hear me. So yeah, changes call qualirt, but apparently not always for the better. Maybe you have to have support in your area.

SoundZombie said:
All this did to mine was make it so I couldnt hear anyone, and they couldnt hear me. So yeah, changes call qualirt, but apparently not always for the better. Maybe you have to have support in your area.
Click to expand...
Click to collapse
My issue was it knocked out my 3G service, crazy. So results will vary, maybe an earpiece hack of some sort would be better served.
Sent from my DROIDX using Tapatalk

JkdJedi said:
The problem is that on some phones the 3g is effected and/or after a reboot it doesn't hold?
Jedi
Click to expand...
Click to collapse
It doesn't even hold for me if I go thru the same procedure again within a boot.
BTW, the number dialed happens (or is meant) to be ##PROGRAM.

This worked great for my X. I was ready to go back to my blackberry with the reception problems. This made a huge difference. Thanks!
Sent from my Xoom using Tapatalk

It works for me, but it does not stay after a reboot.
I'm running apex rc2

Related

[q] Slot index?

On my Eris I was able to use ##PST on my Eris to change my slot cycle index, but for my new D2 it is not working. How would I go about accessing this on the D2? Thank you.
Edit: Did a through Google search, which brought up ##7764726 but then not sure where to go afterwards to adjust the slot cycle for calls.
tbaker077 said:
On my Eris I was able to use ##PST on my Eris to change my slot cycle index, but for my new D2 it is not working. How would I go about accessing this on the D2? Thank you.
Edit: Did a through Google search, which brought up ##7764726 but then not sure where to go afterwards to adjust the slot cycle for calls.
Click to expand...
Click to collapse
you can use qpst to make that change. it's the only way i've heard of on moto phones.
so i just put ##QPST in the dialer then?
tbaker077 said:
so i just put ##QPST in the dialer then?
Click to expand...
Click to collapse
no, it's a program for the computer.
this is how to set it up
http://thewindows7site.com/forum/threads/19170-Diagnostic-Mode-for-Droid-X
And it works for the D2 right?
The article doesn't explain what to do when using the QPST app.
tbaker077 said:
And it works for the D2 right?
The article doesn't explain what to do when using the QPST app.
Click to expand...
Click to collapse
this procedure works practically the same on the droid1, droid2 and droidx. there's only a slight variation with the droidx cause ther is no keyboard.
But the procedure for droid1 and droid2 is the same. see here http://www.howardforums.com/showthread.php/1593533-service-programming-on-the-moto-droid
Using qpst is the easy part. open it. connect to the port you made. then choose Service Programming in qpst, then click on "read from phone", change the slot cycle index, then click on "write to phone"
WARNING: this is very powerful software that can write to the NVRAM of your phone. which means you can bork your **** with one wrong click. i highly recommend you do some googling and reading before you do it. qpst has been around for many years and very popular for reprogramming lots of different phones so there's plenty of info out there on it.
So what is slot cycle index? Why would one need to change it. Just interested to learn more. I've got the qpst program for messing with an old phone and might try this if it's worth it on my D2.
Sent from my DROID2 using XDA App
newk8600 said:
So what is slot cycle index? Why would one need to change it. Just interested to learn more. I've got the qpst program for messing with an old phone and might try this if it's worth it on my D2.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
it's a common cure for phones that have a bad "ring delay". Or, it's a way to save some battery life.
On the CDMA Paging Channel (this is the shared channel that all phones
listen to for incoming calls and other control info), time is divided into
"slots". To conserve power, phones that are currently idle only "wake up"
and listen for messages on the Paging Channel during their assigned
slots. The slot cycle index determines how often the phone's slot comes
around. If the slot cycle index is 0, the phone wakes up every 1.28
seconds. If it's one, it wakes up every 2.56 seconds. If it's two, it's
every 5.12 seconds, and so on. The larger the setting, the more power is
conserved, but the longer it takes to page the phone for an incoming
call. You can imagine that if it were set to 10.24 seconds, few callers
would hang on the line long enough for you to answer your phone.
There are two settings that govern this. One is the "preferred slot cycle
index" in the phone, and can be set via service programming. The other is
the "maximum slot cycle index" set in the base station and broadcast in
overhead messages on the Paging Channel. The phone has to use whichever
number is smaller.
Still can't get HW Virtual serial to connect. It worked once last night, but now it isn't. Any ideas? Real shame I can't just change it like I could on my Eris or Samsung i760, with a dialer code.
Edit: I must have skimmed it, but on the Droid 2 what is the T key?
tbaker077 said:
Still can't get HW Virtual serial to connect. It worked once last night, but now it isn't. Any ideas? Real shame I can't just change it like I could on my Eris or Samsung i760, with a dialer code.
Edit: I must have skimmed it, but on the Droid 2 what is the T key?
Click to expand...
Click to collapse
the letter T on your keyboard
I know that but how do I use to it to enter diag mode, because the HW virtual serial isn't working for me.
tbaker077 said:
I know that but how do I use to it to enter diag mode, because the HW virtual serial isn't working for me.
Click to expand...
Click to collapse
it's right there in the first post of the hofo link i gave you.
I tired what was stated in that link, but I still can't get HW to connect. Still getting an error.
Edit: tired the T key but I don't think it worked? Still getting connection error.
So, I was able to get HW to connect to the phone again but QPST says no phone for the specific port and settings I chose. Could this be some how driver related, or is it something else?
call ring delay is found in the build.prop. if you're rooted, jrummy's apps can help.
Sent from my DROID2 using XDA App
Im pretty sure it is not really a software thing, but a deeper phone things. But, as far as I know if it was software thing then a simple reg edit on my old Samsung i760 would have done the trick instead of putting in a dialer code, to mess around with some slot index settings and then having the phone turn off and restart(was like 4min process total). I could be totally wrong here(kind of hope I am), but if I am not it be nice to get this method working. Thank you.
gunz.jones said:
call ring delay is found in the build.prop. if you're rooted, jrummy's apps can help.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
that only changes the ring delay when dialing out. it has nothing to do with the slot cycle index.
Can you maybe assist me on why the D2 isn't showing up in QPST despite HW is connected to the phone, please?
tbaker077 said:
Can you maybe assist me on why the D2 isn't showing up in QPST despite HW is connected to the phone, please?
Click to expand...
Click to collapse
sorry dude, i dont know what the problem is. i dont have a d2. if you look in that hofo thread, there are lots of suggestions and tips to getting that to work. do you have it shut off, then hold the T, then plug in usb cable. then wait and continue to hold the T till it's done. dont press power button.
do you have an unrecognized devices in your device manager when you're doing this?
I read a portion of that long thread, and most was for the D1 and not really related to what I have. I don't see any issues listed in device manager regarding the D2. Maybe you can post me the full 32bit Droid 2 drivers, because the ones on Moto's site didn't seem to be the right one, and I have used the wrong drives I got doing a google search. Thank you.

[Q] Echo Problem, Please help before I decide dump my Eris

I've had this horrible Echo ever since I rooted my phone (4 months or so). I don't hear it but people on the other end hear themselves. I've searched and the only thing I've seen suggested is turning the in-call volume down and that doesn't help either. I've tried several different roms and nothing.
I don't believe I had this problem until I rooted. If the only way to fix the echo is to un-root I'll just get a different phone. It's too boring without root.
Thanks for the help,
did you try *228?
Rooftop-Special said:
I've had this horrible Echo ever since I rooted my phone (4 months or so). I don't hear it but people on the other end hear themselves. I've searched and the only thing I've seen suggested is turning the in-call volume down and that doesn't help either. I've tried several different roms and nothing.
I don't believe I had this problem until I rooted. If the only way to fix the echo is to un-root I'll just get a different phone. It's too boring without root.
Thanks for the help,
Click to expand...
Click to collapse
Can you let us know what ROM/version your running? I know that this problem was much more pervasive across the 2.1 ROM's that folks first rooted too. After going to the 2.2 roms..myself and my family have had no real issues with it. I will say that if you go into an area with 1x coverage vs 3G, I have seen it pop back up but I chalk that up to a coverage issue.
Right now im running Vanilla Tazz 26 but this has been going on with multiple roms, including kaosfroyo V39.
I haven't been able to perform *228 since I've rooted. It never gives me a dial pad when I dial *228. I've always chocked this up to being rooted. Should I be able to perform *228 as I did without root?
I know these are nOOb questions, I really appreciate the help.
Rooftop-Special said:
I haven't been able to perform *228 since I've rooted. It never gives me a dial pad when I dial *228. I've always chocked this up to being rooted. Should I be able to perform *228 as I did without root?
I know these are nOOb questions, I really appreciate the help.
Click to expand...
Click to collapse
Yeah you can still *228. The dialpad is an option when you push menu inside of a call.
Sent from my KaosGingerbread using XDA App
playpolo4life said:
Yeah you can still *228. The dialpad is an option when you push menu inside of a call.
Sent from my KaosGingerbread using XDA App
Click to expand...
Click to collapse
I've always tried pressing menu when I've dialed *228 in the past and nothing. This time I held menu and up comes the keyboard. I was able to update my roaming. I'll see if that fixed the problem. I'm keeping my figures crossed.
Thanks again, I really appreciate it!
Still have the echo. Any other ideas?
Thanks,
i have had to flash a different radio in the past to get rid of an echo. i was running the july radio and had to get the older hero radio posted in the "all radio" thread. be careful when flashing radios, charge fully, etc. also, please post in q&a section next time since your post is not about developing. thanks! hope this helps.

Help with DK28 issue

Hi. I have been on DK28 for about a month now and I'm fairly happy with it. However, There are a few issues (nothing too major) that i would like to ask help for. just to kindda be quick, I used odin to go to dk28. I had removed some bloatware while on 2.1 and flashing would not work for me so i had to use odin. I was rooted on DI18 and im rooted also on DK28. I do know that this is not the official release and IT IS buggy but i thought some of these issues might have been resolved.
These are the problems:
-screen rotation lags. Whenever i go from landscape to portrait or wise versa the screen takes like 3 or 4 seconds to change orientations. I remember it was almost instant on DI18.
--I drop internet connection a lot. I always get the connection failed error message regardless of whether im on 3g 0r 4g. i'd be on youtube for like 15 min and this happens. Same when im browsing the market. The icons on the notification bar show signal bars but the phone is not connecting. I have to toggle them on and off to get back online. I did try to flash older modems but wasnt able to (system error 7 or sm like that).
---battrey is not calibrated. I used the "wipe battery stat" trick a few times and it does not seem to help. when the phone is fully charged it shows 100% and as soon as i take it off the charger it goes to 96%!
----SOmetimes when i make calls the counter on the screen starts but i dont hear anything. If i make a second attempt i get through right away!
-----I dont use Bluetooth a lot but it seems like most of the times i have to unpair and re-pair back my jawbone for it to connect. I never had this issue with DI18.
Everything else seems to be working ok.
Thanks in advance for reading this and helping me if you can.
and ohh. btw here is some info about my phone in case you need them:
Frmw versoin 2.2.1
baseband: s700.0.55.KD28
Kernel: 2.6.32.9
Build: froyo.DK28
1. for screen rotation fix do this: get android terminal from market. type"su" (without "") then type /system/bin/sensorcalibutil_yahama and hit enter. follow the onscreen instructions.
2. for better data connection do this Get your MSL#
Easy way to get your MSL # use connectbot from market
Go to phone > Dialer > ##3282# > Multimedia > Enter "MSL" > You will see RTST Proxy, HTTPPD Proxy > modify every list > set Address with "0.0.0.0", port with '0'.
this will help with speed but data connection errors are pretty common on dk28.ive seen a great speed increase after doing this.
3. battery thing is common for the phone so the battery doesnt overcharge.
4.when you cant hear anything toggle speakerphone on/off and then you can hear them without calling them back.
5. dont use bluetooth. cant help you sorry.
hope i helped you
Thank you very much for you help. I did the Calibration thing and now the phone only does horizontal orientation. lol. Im flashing back to DI18 and starting all over again. Its kindda fun anyways!
shahin26 said:
Thank you very much for you help. I did the Calibration thing and now the phone only does horizontal orientation. lol. Im flashing back to DI18 and starting all over again. Its kindda fun anyways!
Click to expand...
Click to collapse
It is alot of fun. That's why I've flashed every rom on dk28. If you need anymore help with something you can pm me.
Sent from my Evo Killer!!!
Are there any drawbacks to #2, the MSL/HTTPD proxy thing? And/or can someone explain what this actually does? I also have DK28 speed issues, but am reluctant to try something like that without a bit more understanding of what's going on.
Thanks!
Sent from my SPH-D700 using XDA App
moriarty00 said:
Are there any drawbacks to #2, the MSL/HTTPD proxy thing? And/or can someone explain what this actually does? I also have DK28 speed issues, but am reluctant to try something like that without a bit more understanding of what's going on.
Thanks!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/sprint-ep...reaming-pandora-skyfire-tunewiki-over-3g.html. read that thread.
Sent from my Evo Killer!!!

Manual Program Dinc with MIUI

Hi,
Have an Incredible. Rooted with s-of and MIUI 2.97 and Android 2.3.2. I am trying to manual program it to get in and change MDN/MIN numbers. I have tried ##778 and ##778#, but all that happens when I do this is I get the Verizon recorded message that they can't complete my call. No programing menu, etc.
Any suggestions?
BM
bartman99 said:
Hi,
Have an Incredible. Rooted with s-of and MIUI 2.97 and Android 2.3.2. I am trying to manual program it to get in and change MDN/MIN numbers. I have tried ##778 and ##778#, but all that happens when I do this is I get the Verizon recorded message that they can't complete my call. No programing menu, etc.
Any suggestions?
BM
Click to expand...
Click to collapse
You must be on a sense rom to use ##778# (epst). You will need to do a backup, flash a sense rom, change the settings, and then restore back to MIUI. As long as you dont do a factory reset in between, the settings will stick and you wont have to reactivate. What are you trying to do?
bartman99 said:
Hi,
Have an Incredible. Rooted with s-of and MIUI 2.97 and Android 2.3.2. I am trying to manual program it to get in and change MDN/MIN numbers. I have tried ##778 and ##778#, but all that happens when I do this is I get the Verizon recorded message that they can't complete my call. No programing menu, etc.
Any suggestions?
BM
Click to expand...
Click to collapse
Try *228 from miui
Sent from my ADR6300 using Xparent Red Tapatalk 2
cmlusco said:
You must be on a sense rom to use ##778# (epst). You will need to do a backup, flash a sense rom, change the settings, and then restore back to MIUI. As long as you dont do a factory reset in between, the settings will stick and you wont have to reactivate. What are you trying to do?
Click to expand...
Click to collapse
Bummer. I was hoping that wouldn't be the case.
I bought a used Incredible, modified it to use MIUI just the way I wanted and then activated it on PagePlus (and activated it using *22890, *228, *22899). The ESN is good and it activated fine. Only thing is, the phone still "thought" its phone number was the old one, not mine. I could call out fine, but incoming calls to my number didn't come though (I never tired to call the old number from the previous owner). I contacted Pageplus again and they everything is fine on their end and I would have to manually program it. Well since the Incredible is not supported by P+ (and certainly one that is rooted with a custom ROM), I figured I'd do it myself. I need to get into the manual programming menu to change the MDS and MIN (and whatever else has the old phone number and change it to my number).
I hope this was clear.
Thanks in advance... BM
You may be able to use a pc program called qpst to change the settings. Im not sure if qpst is reliant on epst being on the phone or not.
bartman99 said:
Bummer. I was hoping that wouldn't be the case.
I bought a used Incredible, modified it to use MIUI just the way I wanted and then activated it on PagePlus (and activated it using *22890, *228, *22899). The ESN is good and it activated fine. Only thing is, the phone still "thought" its phone number was the old one, not mine. I could call out fine, but incoming calls to my number didn't come though (I never tired to call the old number from the previous owner). I contacted Pageplus again and they everything is fine on their end and I would have to manually program it. Well since the Incredible is not supported by P+ (and certainly one that is rooted with a custom ROM), I figured I'd do it myself. I need to get into the manual programming menu to change the MDS and MIN (and whatever else has the old phone number and change it to my number).
I hope this was clear.
Thanks in advance... BM
Click to expand...
Click to collapse
Is this a phone number you've had for a while, or a new one? If it's a new number, make sure you're calling the MDN (aka My Phone Number) and not the MIN (Mobile Identification Number). Page Plus phones will have two different numbers here, it's easy to get confused and call the MIN instead of the MDN.
musical_chairs said:
Is this a phone number you've had for a while, or a new one? If it's a new number, make sure you're calling the MDN (aka My Phone Number) and not the MIN (Mobile Identification Number). Page Plus phones will have two different numbers here, it's easy to get confused and call the MIN instead of the MDN.
Click to expand...
Click to collapse
No, my phone number is an old one that I have used for many years with P+. The one on the phone (MDN) was never mine, was likely from the previous owner and was never on the P+ list.
Anyway, I tried flashing a couple of mostly stock Sense ROMs with no luck (Stock +, Touch of Blue). I can get into the PRL editing mode (##775, I think), but ##778 does nothing. I have yet to try to return it to unrooted stock with s-on, but that is my next step:crying:
BM
bartman99 said:
No, my phone number is an old one that I have used for many years with P+. The one on the phone (MDN) was never mine, was likely from the previous owner and was never on the P+ list.
Anyway, I tried flashing a couple of mostly stock Sense ROMs with no luck (Stock +, Touch of Blue). I can get into the PRL editing mode (##775, I think), but ##778 does nothing. I have yet to try to return it to unrooted stock with s-on, but that is my next step:crying:
BM
Click to expand...
Click to collapse
I always find it strange that some people have issues accessing epst. I have tried many stock based roms including stock+ and TOB, and have always been able to access the menu.
I would not go s-on for any reason. It makes it way harder to reroot, and i doubt it would make a bit of difference with your issue.
I would just stay s-off and do the latest ruu. Or as i sugested earlier check out qpst.

Background noise through handset earpiece

I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Sent from my XT1575 using Tapatalk
Same issue here ! immediately after MM OTA update on my XT1575 (stock vanilla) people start complaining they cannot hear me well !
After sorting most of MM issues this is a major pain in the a**
Let Moto know about this as it makes the phone crippled.
How come there aren't any more complaints about this serious issue !
This is 100% MM related - People complain they can barely hear me on the other end of the line - I sound muffled, stuttered and basically bad to the point they cannot continue the conversation and demand I call them from a land line !
Forget all MM bugs, problems, etc (need I mention the Equalizer went AWOL) now this Smartphone which I highly praised and loved became a ...smart something - with no phone feature.
Help me let Moto support be aware of this issue.
Thanks
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
alon3232 said:
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
Click to expand...
Click to collapse
Did all that on a call to Motorola after the first replacement phone failed to address my issue. No surprise, it made no difference.
That was followed by a factory reset and a test prior to connecting to my Google account and downloading any apps. Also, made no difference.
Now I'm waiting for my second replacement.
Sent from my XT1575 using Tapatalk
I have a thread on the Motorola forums for this issue.
My second replacement arrived yesterday. It solved the background noise issue! Unfortunately it came with loose buttons which actually rattled when shook or when the phone vibrated. Back to Amazon it goes.
Unfortunately, now Amazon wants to pull the plug on the purchase and take it all back. I'm not ready to give up though. Besides really liking the phone, I've also invested in a screen protector and car mount. I'll have to talk to Amazon today and see what we can do.
Sent from my XT1575 using Tapatalk
It's all boxed up and ready for UPS. I'm really unhappy that I could not get a good MXPE. As I consider other options, it's tough, especially at the $350 price point.
I'm actually giving the ZTE Axon Pro some thought, but undecided so far. And if the was a sale on the Nexus 6P that brought it down $100, it would be a contender. I'll pay a few more bucks for a Nexus. Given the right price, I may even give the MXPE anther shot, after they work through this stock of bad phones.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Don't get the axon. If you can't get the. 6p I'd go with Nexus 6 some places U can get it under 3 I think
Sent from my XT1575 using Tapatalk
Solved
Hi guys ive got the solution to this problem, my mic used to not work at all on handset calls and wud work on speakerphone. After diagnosing for 24 hrs I was able to understand the problem, all you need to do is replace top mics with bottom mics in music_path.html file If someone is not able to do it lemme know on twitter ill email u my edited file, just replace yours with mine. N nw the mic works like a charm. I am not a regular xda user, so won't be able to check back frequently, my twitter id is @smartphoniac
Have seen ppl replacing motherboards and phones in service center, also some use it on Bluetooth or handsfree, trust me its nt needed just do what i wrote above and issue is solved, if u r a noobie tweet me ill email u my file so that u will have to do jst the copy pasting and this painful issue will be gone forever.
Edit: This will also solve the problem if caller gets his own voice as echo. After this editing even that issue will be solved
Hi guys,
I've just bought a Moto X Style and I'm having the same problem as the original poster - constant background noise (kinda buzzing/hissing) during phone calls, coming through the upper speaker:
jswclw said:
I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Click to expand...
Click to collapse
So far I've tried booting into safe mode, wipe data/factory reset, different carrier/SIM card - no difference.
I'm running Android 6.0.1 and I upgraded right after I bought the phone, so cannot tell if the problem existed on Android 5.
However - and this is my question - since you claim that it's a software thing and Marshmallow-related, is there anyone who tried flashing a Nougat ROM and has it helped? I don't know if I should try and get a replacement phone (especially that some people had the same issue on 2-3 consecutive phones) or just wait for the Nougat update, assuming that it helps.
Thanks for advice!
Hi, it's me again - just wanted to tell you that I've flashed the 7.1.1. AICP ROM and the background noise is still there while calling Is it really a software issue? So many people say it appeared after MM upgrade and there were no problems on Lollipop, but maybe my speaker/mic is simply broken? Is there any ROM you can flash to get rid of this issue? All help is really appreciated! :good:

Categories

Resources