Crash - Bug or just me? - Google Pixel 4 XL Questions & Answers

Could someone test something for me? Make a call and press mute multiple times quickly. Does your phone reboot?
I'm on the December image, rooted with magisk, systemless.
Logcat shows "Telecom: Session: getFullMethodPath: Hit recursion limit!: [email protected]"
Thanks!

cryppie said:
Could someone test something for me? Make a call and press mute multiple times quickly. Does your phone reboot?
I'm on the December image, rooted with magisk, systemless.
Logcat shows "Telecom: Session: getFullMethodPath: Hit recursion limit!: [email protected]"
Thanks!
Click to expand...
Click to collapse
Mine reboots as well, it's a hot reboot.

Indian SimCards
airmaxx23 said:
Mine reboots as well, it's a hot reboot.
Click to expand...
Click to collapse
do indian sim cards work on global rom in 4 xl

cryppie said:
Could someone test something for me? Make a call and press mute multiple times quickly. Does your phone reboot?
I'm on the December image, rooted with magisk, systemless.
Logcat shows "Telecom: Session: getFullMethodPath: Hit recursion limit!: [email protected]"
Thanks!
Click to expand...
Click to collapse
Maybe I'm missing something but why would you want to mute and unmute multiple times in succession? I doubt most people would ever encounter this as a real use case scenario.
Sent from my Pixel 4 XL using Tapatalk

bigdave79 said:
Maybe I'm missing something but why would you want to mute and unmute multiple times in succession? I doubt most people would ever encounter this as a real use case scenario.
Click to expand...
Click to collapse
Picture this scenario: your boss calls asking why you are not at work. You can't - off the top of your head - quickly think of a reason, other than you didn't fancy going in. As you fumble for your words you mute and un-mute the phone. Your boss thinks it is a bad line. But but before he can say he'll call back, the phone crashes. You can now leave the phone off long enough for you to be able to come up with a good excuse for being off work.
Good old Google they think of everything!

croques said:
Picture this scenario: your boss calls asking why you are not at work. You can't - off the top of your head - quickly think of a reason, other than you didn't fancy going in. As you fumble for your words you mute and un-mute the phone. Your boss thinks it is a bad line. But but before he can say he'll call back, the phone crashes. You can now leave the phone off long enough for you to be able to come up with a good excuse for being off work.
Good old Google they think of everything!
Click to expand...
Click to collapse
So it's not a bug it's a feature ?

virtyx said:
So it's not a bug it's a feature ?
Click to expand...
Click to collapse
Right! I also might add that if I were to have done that to my bosses at any time....to the unemployment line I would go! And rightfully so! ?

bigdave79 said:
Maybe I'm missing something but why would you want to mute and unmute multiple times in succession? I doubt most people would ever encounter this as a real use case scenario.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Meetings. For me, 25 times causes the crash no matter how fast or slow mute is hit.
Sent from my Pixel 4 XL using Tapatalk

bigdave79 said:
Maybe I'm missing something but why would you want to mute and unmute multiple times in succession? I doubt most people would ever encounter this as a real use case scenario.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
I don't think anyone has a reason to hit the mute button multiple times but it still shouldn't cause the phone to reboot.

airmaxx23 said:
I don't think anyone has a reason to hit the mute button multiple times but it still shouldn't cause the phone to reboot.
Click to expand...
Click to collapse
Guess you haven't been in meetings in a car [emoji3]
Sent from my Pixel 4 XL using Tapatalk

bigdave79 said:
Maybe I'm missing something but why would you want to mute and unmute multiple times in succession? I doubt most people would ever encounter this as a real use case scenario.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
It's this attitude that gives us "sloppy software" - instead of designing it for what a person can do, don't test or consider things you think someone is "unlikely" to do.

Legit does it to mine too...
Has anybody raised it to google?

fkofilee said:
Legit does it to mine too...
Has anybody raised it to google?
Click to expand...
Click to collapse
They told me it would be fixed in a future update. I would hope January's!
Sent from my Pixel 4 XL using Tapatalk

I tried it and my phone reboots as well.
BUT warning to others... don't try it because now my phone is acting weird after the reboot. Even when I enter my unlock pattern, it'll go back to a blank screen and then back to a lockscreen again. After a few attempts, it'll remain on "starting pixel..." Only fix was a shutdown and then a power up.... hopefully no lasting effects.

bigdave79 said:
Maybe I'm missing something but why would you want to mute and unmute multiple times in succession? I doubt most people would ever encounter this as a real use case scenario.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Mine reboots as well. When I am on a conference call, I use the mute button like a push to talk feature to keep background noise at a minimum.

FIXED! Feb 2020 image.

Related

2 Nexus 4 Issues That Need to Be Addressed

After using the Nexus 4 for 24 hours, I have found I have two gripes with this phone. The first is there is no audible alert if you receive a text message while on a call. In other words, if someone sends you a text message while you are on a call, you will not be made aware of it until you turn on the screen and look at it. The other gripe I have is the call waiting beep is almost completely inaudible, and the second beep sometimes doesn't even occur. In other words, if you are on a phone call, and a second call comes in, you most likely will not know about it and thus will not be know to answer the call. Today I have missed several phone calls because I was on the phone and a call waiting beep could not be heard. As an experiment, I got on a call and then called my phone from a third phone just to hear the volume of the call waiting beep...it is so low it may as well not be there. To make matters worse, after the first beep, the second beep takes so long to occur, your voicemail may likely pick it up either right before or right after the second beep occurs.
Software, not nexus 4 issue. I'm sure there's an app or will be implemented into ROM to solve your problem.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
lnfound said:
Software, not nexus 4 issue. I'm sure there's an app or will be implemented into ROM to solve your problem.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
The software comes stock on the Nexus 4 thus it is a Nexus 4 issue. Not being alerted to a second call isn't something that can be easily excused with, "there's an app or will be implemented into a ROM". A person shouldn't need to install apps or hack their phone just so they can know when a second call is coming in...after all it's a smartPHONE..
Sms issue can be solved with a 3rd party Sms app the call beep not so big of an issue to me so that's all I can say.
Sent from my Galaxy Nexus using xda app-developers app
What's a phone call?
Hey I'd love to agree with you but I just need clarification on one thing. What is this phone call you speak of?
Nocturnal86 said:
Sms issue can be solved with a 3rd party Sms app the call beep not so big of an issue to me so that's all I can say.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Maybe not being alerted of calls isn't a big deal to you, but there are some of us that get important calls throughout the day, and not being alerted to them is not acceptable. Call me old-fashioned but I expect a phone to actually be able to handle phone duties, and alerting me to a second call is one of those duties. That's a pretty basic expectation, and a glaring flaw that needs to be corrected.
chlehqls said:
What's a phone call?
Click to expand...
Click to collapse
Forever alone
Sent from my GT-I9100 using Tapatalk 2
Clearly you like the phone so how is complaining here gonna help, I wonder. I'm assuming there are no options available in call settings or sound that can remedy this issue. If not you have to get a third-party option whether you like it or not
I'm guessing you've set the phone to vibrate for incoming messages?
Sent from my Nexus 4 using Tapatalk 2
Shouldn't it be the same pretty much like the gnex 4.2 update? Why wouldn't those things work?? What happened from the recent release to now?
Sent from my Galaxy Nexus using Tapatalk 2
asasione said:
Clearly you like the phone so how is complaining here gonna help, I wonder. I'm assuming there are no options available in call settings or sound that can remedy this issue. If not you have to get a third-party option whether you like it or not
Click to expand...
Click to collapse
It's clear I like the phone? I haven't stated how I feel about the phone besides the two issues I have with it. Also, for your information, complaining is how issues get resolved because it brings it more attention. Some of us aren't content with resting on our laurels and accepting the subpar. Furthermore, 3rd party software should not be required just to get simple basic functionality. Instead of excusing shortcomings, you should be demanding a complete device. Also, to be clear, I want to like the phone and want to see it succeed. I have a vested interest in it (which I won't get into publicly), so it actually benefits me for it to be a good phone and do well. That said, if it's falling short somewhere then it needs to be corrected and not just covered up.
kurigowa said:
I'm guessing you've set the phone to vibrate for incoming messages?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
It's set to have both an audible alert and vibrate on incoming messages. The problem is, during a phone call, neither of these things happens. There literally is no alert during a phone call other than the icon on the screen. In other words, if you don't happen to be looking at your screen, you will never know you have a text message if you are on a phone call.
At least u got the phone
Sent from my GT-I9100 using Tapatalk 2
Have you looked through phone app - menu - settings?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Wow. First world problems.
Sent from my GT-I9100 using Tapatalk 2
mysterioustko said:
It's clear I like the phone? I haven't stated how I feel about the phone besides the two issues I have with it. Also, for your information, complaining is how issues get resolved because it brings it more attention. Some of us aren't content with resting on our laurels and accepting the subpar. Furthermore, 3rd party software should not be required just to get simple basic functionality. Instead of excusing shortcomings, you should be demanding a complete device. Also, to be clear, I want to like the phone and want to see it succeed. I have a vested interest in it (which I won't get into publicly), so it actually benefits me for it to be a good phone and do well. That said, if it's falling short somewhere then it needs to be corrected and not just covered up.
It's set to have both an audible alert and vibrate on incoming messages. The problem is, during a phone call, neither of these things happens. There literally is no alert during a phone call other than the icon on the screen. In other words, if you don't happen to be looking at your screen, you will never know you have a text message if you are on a phone call.
Click to expand...
Click to collapse
If getting the issue fixed is why you whine, whine on the Google forums. I am sure every single other xda members here won't boycott Google tomorrow because of this post
lnfound said:
Have you looked through phone app - menu - settings?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yep, but it matter not. In the end, the result is the same. It appears to be a glaring oversight (the call waiting beep).
Uhm, I can has phone?
I'm sure if this is a common problem on devices, Google will probably update it and fix the problem. You can always contact Google and let them know as well.
mysterioustko said:
It's clear I like the phone? I haven't stated how I feel about the phone besides the two issues I have with it. Also, for your information, complaining is how issues get resolved because it brings it more attention. Some of us aren't content with resting on our laurels and accepting the subpar. Furthermore, 3rd party software should not be required just to get simple basic functionality. Instead of excusing shortcomings, you should be demanding a complete device. Also, to be clear, I want to like the phone and want to see it succeed. I have a vested interest in it (which I won't get into publicly), so it actually benefits me for it to be a good phone and do well. That said, if it's falling short somewhere then it needs to be corrected and not just covered up.
Click to expand...
Click to collapse
It's still new. There will always be early issues. Perfection will come later
Sent from my DROID2 using xda premium
mrhaddan said:
Uhm, I can has phone?
I'm sure if this is a common problem on devices, Google will probably update it and fix the problem. You can always contact Google and let them know as well.
Click to expand...
Click to collapse
First of all, it's not a Nexus 4 issue, it's a 4.2 issue.
Second of all, I doubt Google would remove a feature they have had since...idk 2.2(the first version of Android I had). Try a restore, or mess with the settings...or maybe you're holding it wrong.

Does anyone else get this volume warning after 4.2 update?

Googled this and cant find anyone else with this issue. It's starting to get really annoying. I'm hoping that there is a place somewhere in settings to turn this off.
Posting from a UK rooted stock nexus 7.
Weird, I've never seen that before. I wish I did, mine is still pretty quiet.
lol, haven't seen this before!
but i think its kinda nice that you get warned, especially when you are using headphones...
toby512 said:
lol, haven't seen this before!
but i think its kinda nice that you get warned, especially when you are using headphones...
Click to expand...
Click to collapse
The problem is that this warning happens at something like 40% volume which is way too quiet to listen to anything with my headphones in. Would be nice if there was a way to turn off the warning.
By the way this only happens when headphones are plugged in, it lets you raise the volume normally when they are disconnected.
I'm guessing is just an EU thing.
I have that warning too... I'm in the US. The warning itself doesn't bother me, what bothers me is that my headphone volume is noticeably quieter since the update. And it does occur around 40%, I thought everyone was getting this.
Sent from my Nexus 7 using XDA Premium HD app
Ryano89 said:
I have that warning too... I'm in the US. The warning itself doesn't bother me, what bothers me is that my headphone volume is noticeably quieter since the update. And it does occur around 40%, I thought everyone was getting this.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
If everyone is getting this I'm surprised that not many have complained really. The popup is really, really annoying to me.
Sort of reminds me of the epilepsy warning they added to ps3 in an update that you cannot turn off and adds about 5 secs to boot time.
Can't say I've noticed headphones being quieter.
I have the message too
I have the message too. Not very anoying sicine it will protect your audition in the future.
If you want to be deaf just ignore the message.
jsmasterx said:
I have the message too. Not very anoying sicine it will protect your audition in the future.
If you want to be deaf just ignore the message.
Click to expand...
Click to collapse
Some people don't have to be spammed with the same information over and over again to get the message.
It would be okay if the message came in at a volume that was dangerous but at the 40% mark its just too quiet to be usable.
I just threw some albums on to check. Yep I get it, then got it again after a reboot, and again after removing and putting the headphones back in a bit later. God dammit.. I do not need Google holding my hand doing every day mundane tasks.. Why do we live in such a pansy nanny state?
styckx said:
I just threw some albums on to check. Yep I get it, then got it again after a reboot, and again after removing and putting the headphones back in a bit later. God dammit.. I do not need Google holding my hand doing every day mundane tasks.. Why do we live in such a pansy nanny state?
Click to expand...
Click to collapse
It is also to avoid people suing google. If people are to stupid to use a normal volume, they will sue if they have ear damages. look at mcdo and the hot coffee.. ridiculous.
Because of that , they needs to go this way
jsmasterx said:
It is also to avoid people suing google. If people are to stupid to use a normal volume, they will sue if they have ear damages. look at mcdo and the hot coffee.. ridiculous.
Because of that , they needs to go this way
Click to expand...
Click to collapse
I know but it just enrages me the sissy sue happy `I'm a victim of lacking common sense so pay me' world we live in.. I know it will be removed in custom ROMs..
it was added as config option in 4.2
<!-- reference volume index for music stream to limit headphone volume and display warning -->
<integer name="config_safe_media_volume_index">6</integer>
also this should be in q/a
I've never seen this pop up. I do notice that volume on you tube video is better, was very quiet, now I only need 50% to sound good. I tried a song from my card at 90% got no warming.
Hmm...
jsmasterx said:
It is also to avoid people suing google. If people are to stupid to use a normal volume, they will sue if they have ear damages. look at mcdo and the hot coffee.. ridiculous.
Because of that , they needs to go this way
Click to expand...
Click to collapse
texasice said:
it was added as config option in 4.2
<!-- reference volume index for music stream to limit headphone volume and display warning -->
<integer name="config_safe_media_volume_index">6</integer>
also this should be in q/a
Click to expand...
Click to collapse
Is this in an editable file, and if so, which one?
Sent from my Nexus 7
BillGoss said:
Is this in an editable file, and if so, which one?
Click to expand...
Click to collapse
overlay/frameworks/base/core/res/res/values/config.xml. But it's just a source file. Grepping through /etc for "safe_media_volume" returns nothing.
Yes I get that warning but only when the headphones are plugged in.
system overload said:
Yes I get that warning but only when the headphones are plugged in.
Click to expand...
Click to collapse
Same here
I join in but with a N4.
And it's already an official issue.
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=40365
I'm seeing this on my Note2 and it drives me crazy, I plug it into my car and run the phones volume at 100% and use my amp to control the volume.. I don't need it pretending it is smarter than me. If anyone finds a fix let us know..

HTC One Home / Back capacitive buttons problem

As many people have noticed, the home/back capacitive/virtual buttons often do not work.
http://www.pocketables.com/2013/04/...-issues-with-capacitive-hardware-buttons.html
http://www.androidauthority.com/htc-one-capacitive-button-problems-198220/
http://forum.xda-developers.com/showthread.php?p=40538985
http://forum.xda-developers.com/showthread.php?t=2231832
http://forum.xda-developers.com/showthread.php?t=2243961
http://forum.xda-developers.com/showthread.php?p=40574171#post40574171
http://forum.xda-developers.com/showthread.php?t=2248951
http://www.youtube.com/watch?v=uvxi6KUR-WA
http://www.youtube.com/watch?v=V7zKpBSluKU
http://www.youtube.com/watch?v=7v5Oc5-7rbA
http://www.youtube.com/watch?v=wxkwyyvOkZ8
http://forums.androidcentral.com/htc-one/270508-home-button-shorting-out.html
http://forums.overclockers.co.uk/showthread.php?p=24147320
http://forums.androidcentral.com/htc-one/270811-back-button.html
http://forums.androidcentral.com/htc-one/271243-button-issue-htc-one.html
http://community.sprint.com/baw/message/569148
Personally, I find it to be *incredibly* annoying and pretty much ruins the experience of using this otherwise good phone. I have already been to the Sprint store to possibly exchange it, but their demo unit had the exact same problem (and the employee I was talking to had also noticed the problem). I have also ran "getevent -lt /dev/input/event6" from adb shell (/dev/input/event6 seems to be the raw output of the touchscreen, some people said it is event5 on theirs rather than event6). This shows you raw data every time you touch the screen. However I noticed that when my touches of the home button go undetected, nothing is read from /dev/input/event6...so I am afraid it may be a hardware problem. I have 11 more days before my 14 day Sprint satisfaction period ends, so I'm on the fence on whether or not I should return it and wait for a better phone, or exchange it and probably get another with the same problem, or...wait for HTC to try to fix it with software.
Some have said a recent update to the Taiwan version of the One solved the problem...:
patato2 said:
doing a bit translation from Taiwan version if you guys can't wait. not sure if I used the correct words though, hope you don't mind.
1.29.709.12(214.04MB)
1. virtual button sensitivity adjusted
2. slow motion video quality improved under low lit
3. better Beats Audio experience
4. better background noise when using headphone
5. better bluetooth device matching
some said back button issue fixed after upgrading.
Click to expand...
Click to collapse
Further evidence that a software patch fixed the home button:
http://translate.google.com/transla...a=X&ei=fy91Ua_5HYaQqgHi_ICwCA&ved=0CGgQ7gEwAw
Poor Google Translate translation:
Did not receive update notifications
Through Settings> About> Software Update> Check Now
We can immediately receive an update notification
After the update the virtual keys become normal
There is a need to go faster
PS: Please note that this is the official update, Brush, may not be updated automatically through the official update to brush back the official
Click to expand...
Click to collapse
Here is the response I got from HTC:
Thank you for retrieving the information for me, [xxxxxx]. I did some research and there will be an MR update to fix this issue with the virtual keys. We do not have any information as to the date the update will be released since it will be released via Sprint your network provider, and it is currently being worked on.
I realize that not having the specific details such as the date is annoying, but we do appreciate your patience. I want to thank you again for sending me that information because that really helps us out a lot. Let me know if you have any other questions I may be able to address with you at this time.
Sincerely,
Casey
HTC
Click to expand...
Click to collapse
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Most likely what you are actually noticing is that not all presses are registered and you are rationalizing it by assuming that you just missed the target. In reality, there is a problem with the home/back buttons that HTC needs to fix, soon.
chogardjr said:
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
I have this issue as well. Seems like you have to hit the button in almost the perfect spot to get it to register.
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
treIII said:
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
~Sent in beast mode using my HTC One~
chogardjr said:
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Hey chogard. Waaazz up? Where's your Rom if you have the one. Wheres that odexed beauty?
Sent from my HTCONE using Xparent Blue Tapatalk 2
Lots more confirmations that OTA 1.29.709.12 solved the problem for the Taiwan variant HTC One. WHEN WILL SPRINT/HTC GIVE US AMERICANS THIS FIX?
patato2 said:
Here's some information about 1.29.709.12 upgrade (Taiwan version), and some responses I read from other forum.
And... sorry guys, I really don't know when will your updates come. and i don't have the phone yet . I envy you!
.
1.29.709.12(214.04MB)
1. virtual key sensitivity adjusted
Lots confirmed the home/back key issue fixed, looks solid.
2. slow motion video quality recording improved under low lit
Didn't see anyone post about it
3. better Beats Audio experience
Some said the left / right sound are better balanced.
4. reduce background noise when using headphone
a few guys said noise is "significantly" reduced.
5. better bluetooth device matching
a few guys confirmed bluetooth device matched faster.
Click to expand...
Click to collapse
For anyone interested, the Taiwan OTA firmware is available here:
http://www.androidrevolution.nl/downloader/download.php?file=1.29.709.12.zip
http://forum.xda-developers.com/showthread.php?t=2182823
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
jaybombz said:
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
Click to expand...
Click to collapse
I prefer to tap with my fingertip and this is rarely detected by the home/back buttons, which is SOOOO annoying. I'm debating trying to swap it out for a new one. From what I can tell the problem seems to affect EVRYONE, although many people might not notice or be annoyed by it. So the question is, is it truly a pure software fault, or is it a hardware fault that software (ie, an OTA) can mask or at least partially correct.
That's my preference as well - it has been an adjustment and one that I'm not terribly pleased with. I'm surprised the issue didn't show up in pre-release testing but I have to imagine it's something that software can fix with a remap of the area the system recognizes as buttons.
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Where's the Rom Fernando?
Sent from my HTCONE using Xparent Blue Tapatalk 2
It's really not an issue with the "area", as I can touch the dead center of the home button and it still won't work. Seems to me that it is either not sensitive enough, or some other problem.
Regardless, word is that an OTA fixed this problem on the Taiwan HTC One 2 days ago, so now I guess we just need to complain loud enough that HTC/Sprint pump out the fix to us ASAP before we all return our phones.
Mines like this as well, you can hit the back button dead on and no response. Hopefully they issue a fix somewhat quickly.
Sent from my HTCONE using Tapatalk 2
Having this problem as well. My device was built April 9th 2013. I can sit there and tap on the home button for 30 seconds or more in every way possible and have no registration of the contact.
This might just be wishful thinking but for some reason clicking the app drawer icon seems to fix the issue right away making me think this is software.
Other than this the build quality and everything else seems perfect.
Sent from my HTCONE using xda app-developers app
HTC needs to admit they have a problem here and advise us whether we should be returning these or waiting for an OTA patch which will be coming VERY soon.
I saw some people talking about this and didn't know what they were referring to.. I got my phone on launch day and have no issues with it, that looks super annoying
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
mang0 said:
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Calibration does not resolve the issue.

People complaining of echo/feedback during calls?

Pretty much every time I make a phone call I have people complaining about feedback they're hearing or an echo of what they're saying to me. Is anyone else experiencing this problem? Is my phone defective?
I to am experiencing this.... Not every time but at least 3 out of 10 calls I'd say......
Galaxy note 3
Galaxy s 3
Galaxy s
Galaxy tab
mazdamiata210 said:
Pretty much every time I make a phone call I have people complaining about feedback they're hearing or an echo of what they're saying to me. Is anyone else experiencing this problem? Is my phone defective?
Click to expand...
Click to collapse
On stock rom? What case are you using?
Sent from my ME302C using Tapatalk 4
tdamocles said:
On stock rom?
Sent from my ME302C using Tapatalk 4
Click to expand...
Click to collapse
100% stock non-rooted
Sent from my SAMSUNG-SM-N900A using xda app-developers app
mazdamiata210 said:
Pretty much every time I make a phone call I have people complaining about feedback they're hearing or an echo of what they're saying to me. Is anyone else experiencing this problem? Is my phone defective?
Click to expand...
Click to collapse
Is your phone in a case? Is the issue location specific?
Solarenemy68 said:
Is your phone in a case? Is the issue location specific?
Click to expand...
Click to collapse
Nope completely naked
Sent from my SAMSUNG-SM-N900A using xda app-developers app
mazdamiata210 said:
Nope completely naked
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
if guessing you should do a factory reset, then try to see if it works. if not, get a replacement.
My echo went away using the bri xnote rom ..volume levels are higher now as well..hope this helps
pham818 said:
if guessing you should do a factory reset, then try to see if it works. if not, get a replacement.
Click to expand...
Click to collapse
That would be the 5th time I reset and/or reflashed stock. Never fixed it.
wish777 said:
My echo went away using the bri xnote rom ..volume levels are higher now as well..hope this helps
Click to expand...
Click to collapse
I'm running stock because I always had battery issues when rooted. Plus we can't flash roms yet I don't think.
mazdamiata210 said:
That would be the 5th time I reset and/or reflashed stock. Never fixed it.
I'm running stock because I always had battery issues when rooted. Plus we can't flash roms yet I don't think.
Click to expand...
Click to collapse
You can flash roms now...hashcode made a recovery bypass called "Safestrap" its in android development section under sticky....
And theres a few good roms out already im using "Bri" xnote rom...and it's awesome. Haven't had any issues and the battery is the same if not better, believe me...
Its very simple to root now I successfully done it with "kingo"..
And after you flash "Strapstrap" just make a backup and literally flash a rom that easy...most of questions have already been asked if your having questions around here...
wish777 said:
You can flash roms now...hashcode made a recovery bypass called "Safestrap" its in android development section under sticky....
And theres a few good roms out already im using "Bri" xnote rom...and it's awesome. Haven't had any issues and the battery is the same if not better, believe me...
Its very simple to root now I successfully done it with "kingo"..
And after you flash "Strapstrap" just make a backup and literally flash a rom that easy...most of questions have already been asked if your having questions around here...
Click to expand...
Click to collapse
I haven't been very active on here but I did see the safestrap beta... Not sure if I trust kingo root because I saw all the problems with it before. The biggest problem I had was Android OS was always using more battery than my screen time which is a problem and unusual. Happened every time I rooted, coming from a rooted note 2 I know this isn't normal at all. On stock it stays around 8-10% during the day.
I know exactly what your going through. .To be honest this note 3 has superior battery life from any device I owned I had all the note models as well...But rooting your note 3 and debloating it..is only gonna help battery dont go crazy and install a dozen useless apps and you'll be just fine...Also inverted apps and theme's and dark wallpapers help with battery as well in theory less pixels to be energized so less battery. Am getting great battery life. I'm on this all day and connected to wifi and only have to charge it once before bed which is great..lol
wish777 said:
I know exactly what your going through. .To be honest this note 3 has superior battery life from any device I owned I had all the note models as well...But rooting your note 3 and debloating it..is only gonna help battery dont go crazy and install a dozen useless apps and you'll be just fine...Also inverted apps and theme's and dark wallpapers help with battery as well in theory less pixels to be energized so less battery. Am getting great battery life. I'm on this all day and connected to wifi and only have to charge it once before bed which is great..lol
Click to expand...
Click to collapse
Well that's what I mean just rooted messed with something because I had problems every other time I rooted
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Same here. Used Kingo to root my at&t note 3 and installed the newest safestrap. About to debloat my phone with a script that's on here. Wish me luck!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
wish777 said:
My echo went away using the bri xnote rom ..volume levels are higher now as well..hope this helps
Click to expand...
Click to collapse
So I rooted, went to x-note and the rom works great... One day callers complain about echo and the next they don't, so it's still a problem it seems.
I think I might know the reason
mazdamiata210 said:
Pretty much every time I make a phone call I have people complaining about feedback they're hearing or an echo of what they're saying to me. Is anyone else experiencing this problem? Is my phone defective?
Click to expand...
Click to collapse
The note 3 has multiple microphones so it can cancel out back ground noise. It expects that your voice will be mainly be picked up by the lower microphone next to the USB port. If you sometimes block that microphone with something like your hand, you will mess up the noise canceling algorithms which could result in the echo. Try blocking and then unblocking that lower microphone with your hand and see if you can make the echo appear and then disappear for the caller. My guess is you will find the source of your echo.
Good luck.
pjminn said:
The note 3 has multiple microphones so it can cancel out back ground noise. It expects that your voice will be mainly be picked up by the lower microphone next to the USB port. If you sometimes block that microphone with something like your hand, you will mess up the noise canceling algorithms which could result in the echo. Try blocking and then unblocking that lower microphone with your hand and see if you can make the echo appear and then disappear for the caller. My guess is you will find the source of your echo.
Good luck.
Click to expand...
Click to collapse
Doesn't matter I try holding my phone with 2 fingers on the sides not covering anything or even just putting it down on my desk and it still echoes.... Noticed now it's not doing it on speaker phone only with the ear piece which doesn't make much sense.
pjminn said:
The note 3 has multiple microphones so it can cancel out back ground noise. It expects that your voice will be mainly be picked up by the lower microphone next to the USB port. If you sometimes block that microphone with something like your hand, you will mess up the noise canceling algorithms which could result in the echo. Try blocking and then unblocking that lower microphone with your hand and see if you can make the echo appear and then disappear for the caller. My guess is you will find the source of your echo.
Good luck.
Click to expand...
Click to collapse
Funny you say that.....For the longest time I heard alot of people say I sound muffled. And about a month ago I realized I kept holding my phone and my pinkie finger was over the mic..lol....But you are right about the mic and the back ground noise..I usually get the echo effect every now and then,mostly when I'm using WiFi...I'm wondering if it's in the phone "settings" disabling background noise will help solve this echo effect? .
What exactly do you think this option will do unchecked..in phone settings?

Headset mic way too sensitive

Hi All,
Got the Z1 last week about 9 dates ago as a replacement for a Samsung Galaxy S3. Generally liking it, though struggling to get used to the size of the handset. One major issue, though that I can't easily sort or find an answer to anywhere.
Basically, when I use a wired headset with inline mic for phone calls, the microphone is way too sensitive. It picks up every movement of the headphone cord, every rustle on my clothes, etc. Tried about 5 different headsets, including a dedicated Android one button Sennheiser headset. All the same. None of these proved a problem with
Anyone any ideas on what's causing it or how to fix it? Is there something simple I'm missing? It's making calls a painful experience.
Thanks in anticipation.
Sent from my iPad using Tapatalk
Did these problems with those mics occur on your galaxy s3?
LaosPerson said:
Did these problems with those mics occur on your galaxy s3?
Click to expand...
Click to collapse
Nope. In one case, the headphones/headset goes back as far as an IPhone 4, so about three years ago. This is the first time I've had the issue with any of them.
Sent from my iPad using Tapatalk
smajor said:
Check with your mic settings, after making settings then switch your phone and then switch it on. Perhaps this helps. Also check this issue by using hand free. :fingers-crossed: well, samsung 3 is better than this
Click to expand...
Click to collapse
Tried that. No change. S3 better than this? In this respect only. V pleased to see the back of the S3, as it constantly had firmware issues, caused, no doubt. Random battery life issues (sometimes lasting a day, sometimes a few hours), crashes, screen redraw issues, glitchy music playback. I could go on.
Sent from my iPad using Tapatalk
smajor said:
Check with your mic settings, after making settings then switch your phone and then switch it on. Perhaps this helps. Also check this issue by using hand free. :fingers-crossed: well, samsung 3 is better than this
Click to expand...
Click to collapse
Woah galaxy s3 better then this? no way, i had one it was laggy in ui, because of it being ruined by touchwiz and also the fact it was an at&t variant so it had bloatware ontop of samsung bloatware lol
smajor said:
Cool! :victory: well, I don't know about the bloat ware but in my home, most of us are crazy for samsung
Click to expand...
Click to collapse
oh okay, sounds like the where in the US just because it's an iPhone it's automatically better, I used to be like that defending iPhone until i tried the beauty of a GOOD android phone not a cheap one
Oh dear. Wish I hadn't bothered posting here. Another fanboy fight. Look, whatever phone you own, hope you like it. My thanks to those posters who tried to answer my original query. Still searching for an answer.
Sent from my C6903 using Tapatalk
academicbarzo said:
Oh dear. Wish I hadn't bothered posting here. Another fanboy fight. Look, whatever phone you own, hope you like it. My thanks to those posters who tried to answer my original query. Still searching for an answer.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Yeah sorry about that, we didn't answer your question
As for that mic issue it sounds very suspicious
academicbarzo said:
Oh dear. Wish I hadn't bothered posting here. Another fanboy fight. Look, whatever phone you own, hope you like it. My thanks to those posters who tried to answer my original query. Still searching for an answer.
Click to expand...
Click to collapse
I think with Root you can get work anything even the sensitivity of your microphone. It can be easy like edit build.prop that something more but I am sure the sensitivity can be managed. If I find something I will post.

Categories

Resources