Database Develop

My Zio is making a quiet ringing sound

Ok So my phone has done this a couple of times. Basically what is happening is randomly my phone is making a standard ringing sound of 3 or 4 beeps (or so) a pause then the beeps again. This is completely different from the standard sounds i have set on my phone and when this ringing is happening i am not receiving a call nor am i receiving a text message. so far it just happens randomly and even when i put my phone into sleep mode it still rings requiring me to take the battery out to make it stop.
Has this happened to anyone before? what dose it mean exactly?

hofuldig said:
Ok So my phone has done this a couple of times. Basically what is happening is randomly my phone is making a standard ringing sound of 3 or 4 beeps (or so) a pause then the beeps again. This is completely different from the standard sounds i have set on my phone and when this ringing is happening i am not receiving a call nor am i receiving a text message. so far it just happens randomly and even when i put my phone into sleep mode it still rings requiring me to take the battery out to make it stop.
Has this happened to anyone before? what dose it mean exactly?
Click to expand...
Click to collapse
Happened to me until a factory reset. Came back though after reinstalling my apps. You can stop it by making a call. It is a little easier than removing the battery. Still annoying though. I think it could have started after an app was moved to the SD card, so I batch moved everything to the internal storage except for some games. Has not happened for a couple days, but I would not be surprised if it came back. I wish I knew what caused this.

Sprint ZIO or Cricket ZIO?
Sent from my Zio using XDA App

Happened with me, too, on the Cricket Zio. Still searching for a solution. Doesn't seem to be a Zio specific problem, though. I read somewhere that it was happening on the Motorola Droid as well.

Mattix724 said:
Sprint ZIO or Cricket ZIO?
Sent from my Zio using XDA App
Click to expand...
Click to collapse
weeel the picture under my name says sprint soooo. lol

The XDA app doesn't show it. Please don't insinuate that anyone here is stupid. I, for one, don't appreciate it, and neither does anyone else. WE are trying to help YOU, and we ask questions for a reason. A clear, simple answer is what you should give when asked a question IF you want our help.
Sent from my Zio using XDA App

Quite ringing sound
This happens on the Cricket zio as well. It normally happens when you are in a low signal area for any extended period of time. Normally rebooting or making a phone call will stop it. As to why it is happening I have no idea however I do recall this was a problem on one of the old kyocera slider phone I had in the past.

Is there any point in digging into this? It's beginning to happen to me a lot (as my coverage at home sucks despite living in downtown Charlotte).
Every problem has a solution but I'm wondering if the new OC'ed kernel will eliminate it.

One can only hope.
Sent from my Zio using XDA Premium App

mattpedigo said:
despite living in downtown Charlotte.
.
Click to expand...
Click to collapse
Charlotte NC ? I live in Kannapolis.

pomeroythomas said:
The XDA app doesn't show it. Please don't insinuate that anyone here is stupid. I, for one, don't appreciate it, and neither does anyone else. WE are trying to help YOU, and we ask questions for a reason. A clear, simple answer is what you should give when asked a question IF you want our help.
Sent from my Zio using XDA App
Click to expand...
Click to collapse
WOH calm down sir. i don't appreciate how you are treating me right here. i guess you think everyone on this site has used the XDA app. well i have never used it before. therefor i did not know that thos images showing whos carrier is being used weren't shown.
you are a very rude person.

hofuldig said:
WOH calm down sir. i don't appreciate how you are treating me right here. i guess you think everyone on this site has used the XDA app. well i have never used it before. therefor i did not know that thos images showing whos carrier is being used weren't shown.
you are a very rude person.
Click to expand...
Click to collapse
Can we stay on task here and stop with the petty squabbling. Nobody cares how anybody reads the forums but being a smart-a$$ about it will ultimately result in this sort of argument.
Fact is, that we're trying to address an issue here. And to that point, my phone is still making the ringing noise, even with the new OpenZIO ROM. How can that be?
My guess is that the ringing noise is tied up somewhere not on the typical hard-drive of the phone. Kinda like a beeping mechanism on a computer motherboard. And since somebody reported that it happened on an older Kyocera phone, that only furthers my theory in this.
Evidently, it seems to be triggered in poor reception.

mattpedigo said:
Evidently, it seems to be triggered in poor reception.
Click to expand...
Click to collapse
This much I know is 100% correct. The first time it happened to me and my wife we were traveling to the beach and this happened while we were in "Dead Zones" and now it happens to me on a daily basis on my commute to and from work. I drive through a lot of "Dead Zones".

Fate43 said:
This much I know is 100% correct. The first time it happened to me and my wife we were traveling to the beach and this happened while we were in "Dead Zones" and now it happens to me on a daily basis on my commute to and from work. I drive through a lot of "Dead Zones".
Click to expand...
Click to collapse
A lot of dead zones in the Charlotte area? Where are you commuting to and from?

I have also had this issue a couple of times while running rooted 2.2.
I too was in a poor signal zone. An interesting fact is that when I would adjust the volume while it was making the funny sound, it would say that it was adjusting call volume not ringer volume. It was a while ago since it happened last, but I'm also pretty sure the sound comes from the ear speaker and not the louder back speaker, which is why the sound is so soft.

I'm having the same issue!
I'm having a hard time isolating what application could be causing this. It probably doesn't help that I'm EXTREMELY new to this forum.

also having this issue
this happens to me also in a low signal area.. it happens at 5am and again at 9pm. i'm home way before 9pm so i don't know what the signifigance of that may be?

You have all been hax0rd!!! Mwuaaahahahaa!!!
Just kidding.
I have never had this issue before. You could try installing my ROM to see if that fixes the issue?f
**edit: just read upwards -- appears that someone has already tried installing the ROM.
This leads me to believe that it could be a hardware issue.
Perhaps you can take it in for an exchange?

ROM won't fix it. I was having the issue on stock 2.12 as well. It did not start till the update so has to be a bug in the OS.
Sent from my Zio using XDA Premium App

Take your phone back to cricket for an exchange (provided you can reproduce the sound to a rep).
Be sure to flash a stock rom to ur phone or they wont touch you.

[Q] Call Waiting

Can anyone tell me of an app whereby when I call someone and they're on the phone, my phone tells me. I know Samsung's Touchwiz does this. HTC doesn't do it with Sense though and I'm running CM which doesn't do it either.

Bump?
Sent from my Incredible S using Tapatalk 2 Beta-5

AFAIK, Android does not have that feature. Samsung and Sony add that by themselves

It actually sucks to think that something so basic is patent encumbered. I'm guessing that's why I'm also yet to find an app to provide this missing functionality.
Sent from my Incredible S using Tapatalk 2 Beta-5

Doesn't it beep faster for you when you call someone that's talking to someone else?
Sent from my Incredible S using XDA

And if someone ports a Sony Ericsson Neo Rom to IncS? Same qualcomm and adreno. Same chip
Sent from my HTC Incredible S using xda premium

Splux said:
Doesn't it beep faster for you when you call someone that's talking to someone else?
Sent from my Incredible S using XDA
Click to expand...
Click to collapse
Nope, if I call someone and they're on a call, my phone just rings normally leaving me none the wiser.

Lulz, that's really odd. For me it beeps faster and hangs up 2 sec later...
Sent from my Incredible S using XDA

In terms of non-Android I know Nokia does and I was surprised to be told that Apple doesn't. Am really quite gutted that this can't be done with a simple app.

It works on my Inc s. I've enabled call wait from my service provider, so when I'm on a call and someone else calls, I get a series of beeps with the other caller number or contact data flashed on my phone. I just have to accept, reject or ignore the second call and the first caller gets into hold... its all available on your phones too, you only need to enable it in call settings and of course, with your service provider too
Sent from my Transformer TF101 using XDA

ragapa97 said:
It works on my Inc s. I've enabled call wait from my service provider, so when I'm on a call and someone else calls, I get a series of beeps with the other caller number or contact data flashed on my phone. I just have to accept, reject or ignore the second call and the first caller gets into hold... its all available on your phones too, you only need to enable it in call settings and of course, with your service provider too
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
That's the wrong way round. I have mine enabled for people calling me. But what I'm referring to with this thread is a notification to say that when I call someone else, I'm alerted to the fact that they're already on a call.

@Sabret00the
Wouldn't that be a function that the person you're calling, needs to enable with his service provider? I usually get a recorded message saying that the person you are calling is on another call... wait for him to respond, or hang up & dial later. The phone displays number busy... isn't that so? Or then I'm confused....
Sent from my Transformer TF101 using XDA

Nope. It's a standard feature for Samsung's, Sony's and Nokia. If I ring from my IncS and someone is on the phone, it just rings normally. If I ring from a Samsung it states on screen that "the person you're dialling is on a call".

sabret00the said:
Nope. It's a standard feature for Samsung's, Sony's and Nokia. If I ring from my IncS and someone is on the phone, it just rings normally. If I ring from a Samsung it states on screen that "the person you're dialling is on a call".
Click to expand...
Click to collapse
there are tons of threads and requests for this feature,like sms delivery report.Its a manufacture dependent feature.As far as i know it is called "gsm supplimentary service" n i guess on this situation when the user is busy on a call the gsm server sends a code to the phone n the phone then shows a toast notification.All nokia ,samsung and sony ericsson phone have that feature and htc , motorola and iphone doesnt have that I dont know it can be done by an app. may be .. by somethin in the "telephony.app" ... who knows since there is no developer interest in this and
the sms status report

sohojmanush said:
there are tons of threads and requests for this feature,like sms delivery report.Its a manufacture dependent feature.As far as i know it is called "gsm supplimentary service" n i guess on this situation when the user is busy on a call the gsm server sends a code to the phone n the phone then shows a toast notification.All nokia ,samsung and sony ericsson phone have that feature and htc , motorola and iphone doesnt have that I dont know it can be done by an app. may be .. by somethin in the "telephony.app" ... who knows since there is no developer interest in this and
the sms status report
Click to expand...
Click to collapse
Are these features still available on CyanogenMod Samsung's? Or is it something you only see on stock ROMs?
Sent from my Incredible S using Tapatalk 2

sorry dont know about CM ,bt all samsung and sony phone has it ,even those dumb phone's with monocromes . dont mind weither it is stock or community rom.i jst want this enabled on my phone so that i dont became an annoying person by calling and calling people while they talking on their phone(cuz my phone is unable to notify ) check this link http://forum.xda-developers.com/showthread.php?t=787706&page=2 might help..idk

sabret00the said:
Can anyone tell me of an app whereby when I call someone and they're on the phone, my phone tells me. I know Samsung's Touchwiz does this. HTC doesn't do it with Sense though and I'm running CM which doesn't do it either.
Click to expand...
Click to collapse
What do you want? Some kind of beep?

zezoka said:
What do you want? Some kind of beep?
Click to expand...
Click to collapse
Yup, something like a beep and a toaster that says "Your call is being held".

My Nexus 4 is an embarrassment

Apologies for the rant folks but I need to get this off my chest!
<rant>
Google needs to fix the Nexus 4 bugs fast
My state-of-the-art Nexus 4 phone has some major issues that aren't just frustrating - they're embarrassing. The camera will often stop working, especially when used in low light or after taking lots of pictures. I was out for a Christmas dinner with friends last night and we asked the waitress to take a picture of the group. I handed her my phone and ended up red-faced because the bloody camera wouldn't work. I also had the camera freeze with the flash still lit up on numerous occasions last night. How the hell did this get through testing? This isn't a one-off - it happens *every* time I try to take lots of pictures. I expect the camera to work.
Can you imagine the furore if the camera on an iPhone did this? People would be foaming at the mouth.
And the camera quality is pretty poor with many shots out of focus and terrible red-eye on others (with no red-eye reduction mode available) and none of the fancy new image filters can fix it. Yet I'm pretty sure ICS had a red-eye reduction filter.
And I also have a WiFi issue which means my connection speed will drop from 40MB to around 2MB for no reason. I have to toggle WiFi off/on to clear it. Rumour is that it's a problem with the WPA2 encryption used by some routers but I have yet to prove this myself and all our other devices are fine, my Nexus 7 included.
And this morning the phone rang and I couldn't answer the call because the buttons on the incoming call screen simply didn't work. It was charging at the time which I expect is the issue but even so...
In my humble opinion Google needs to get a 4.2.2 update out that addresses issues like this quickly because right now I am seriously considering selling this device and getting something else.
I am not your beta-tester Google. This just isn't good enough.
</rant>
I feel better now. Sorry if this thread sounds a little selfish but I expected so much more from a Nexus device. My 2011 Xperia arc S might of been a bit laggy but at least it was 100% reliable.

Well then return it.. or maybe learn how to use it first.
Personally I don't have any of these issues.
Sent from my Nexus 4 using xda app-developers app

I no issues with my camera from Christmas dinner last night either, from 3 to 8:30pm EST I was snapping away.
No wifi issues here either.
Either yours is broken or some crap app is causing the issue.

Had the camera thing happen to me yesterday. Also have a screen bug that makes part of the screen disappear.
Buy I consider these android problem's which can be fixed. Not Nexus 4 problems.
Sent from my Nexus 4 using xda premium

OP should re-flash the stock ROM. If his issues continue, I'd RMA the device.

rec71 said:
My state-of-the-art Nexus 4 phone .
Click to expand...
Click to collapse
It's $350, who said it's state of the art?

E3SEL said:
It's $350, who said it's state of the art?
Click to expand...
Click to collapse
That's just the price. The actual specs could be considered state of the art.

I'm not sure why the 350 price tag seems to give people a sense of cheapness. This is what a high end phone should sell for. Instead companies **** all over the little people of the world by inflating the price by 300% and lots of times more. Google is merely just sticking it back to those companies and also marketing their ecosystem...
Sent from my Nexus 4 using xda premium

rec71 said:
Apologies for the rant folks but I need to get this off my chest!
<rant>
Google needs to fix the Nexus 4 bugs fast
My state-of-the-art Nexus 4 phone has some major issues that aren't just frustrating - they're embarrassing. The camera will often stop working, especially when used in low light or after taking lots of pictures. I was out for a Christmas dinner with friends last night and we asked the waitress to take a picture of the group. I handed her my phone and ended up red-faced because the bloody camera wouldn't work. I also had the camera freeze with the flash still lit up on numerous occasions last night. How the hell did this get through testing? This isn't a one-off - it happens *every* time I try to take lots of pictures. I expect the camera to work.
Can you imagine the furore if the camera on an iPhone did this? People would be foaming at the mouth.
And the camera quality is pretty poor with many shots out of focus and terrible red-eye on others (with no red-eye reduction mode available) and none of the fancy new image filters can fix it. Yet I'm pretty sure ICS had a red-eye reduction filter.
And I also have a WiFi issue which means my connection speed will drop from 40MB to around 2MB for no reason. I have to toggle WiFi off/on to clear it. Rumour is that it's a problem with the WPA2 encryption used by some routers but I have yet to prove this myself and all our other devices are fine, my Nexus 7 included.
And this morning the phone rang and I couldn't answer the call because the buttons on the incoming call screen simply didn't work. It was charging at the time which I expect is the issue but even so...
In my humble opinion Google needs to get a 4.2.2 update out that addresses issues like this quickly because right now I am seriously considering selling this device and getting something else.
I am not your beta-tester Google. This just isn't good enough.
</rant>
I feel better now. Sorry if this thread sounds a little selfish but I expected so much more from a Nexus device. My 2011 Xperia arc S might of been a bit laggy but at least it was 100% reliable.
Click to expand...
Click to collapse
U should reflash stock nexus 4 IMG from Google.. Definitely something wrong with software department in ur phone.. Probably because of ota updates
Sent from my GT-I9100 using xda premium

E3SEL said:
It's $350, who said it's state of the art?
Click to expand...
Click to collapse
Google says(look at the specs of the phone)... BTW I use the crap out of my N4 camera and have not had these problems. Also I leave mine plugged inost of the day at work (I'm in a vehicle) and have never had an issue with answering. Id RMA it but it up to u if u wanna wait and see if 4.2.2 fixes these issues. I would have though 4.2.2 would be out by now but oh well.
Using Tapatalk 2

did you put in a custom rom?

The camera bug is well documented as are the WiFi problems. This is not just an issue with my device. I'm on stock 4.2.1 fwiw. Maybe a reflash is worth a try but I doubt it.
Funny how when anyone dares to criticise this device people get all defensive though!
Sent from my Nexus 4 using xda premium

If they are well documeneted why didn't you mention it in op and why don't you get a replacement ?
Sent from my Nexus 4 using Tapatalk 2

Use it or lose it. To be quite honest, I don't care either way but there was no need for yet another pointless thread in this forum.
Sent from my Nexus 7 using xda premium

^ yeah because this thread takes up way too much space. /sarcasm
OP: do a factory data reset and If the problem still persists return it!
Sent from my Nexus 4

XxSilent22xX said:
^ yeah because this thread takes up way too much space. /sarcasm
OP: do a factory data reset and If the problem still persists return it!
Sent from my Nexus 4
Click to expand...
Click to collapse
Is that the point? No.
You go ahead and make pointless threads. See how long they stay unlocked for.
Sent from my Nexus 7 using xda premium

I've had some times where the call and lock screen are unresponsive. Usually there is a home and back button at the bottom for seemingly no reason and I have to hit ”back" to get back to the state where I can use the lock screen.. I'm guessing this is causing the call screen to lose interactivity sometimes as well. I'm suspecting issues related to lock screen widgets/extra functionality/Google Now as none of this used to happen on previous revisions, it seemed to start when that feature set was introduced. I also accidentally bring up the camera from the lock screen which gets annoying, but that's more my fault in the way I pick the phone up sometimes if I "pry" it up when it's sitting against something. Annoying, but whatever.
I have had no camera issues specially yet, though I haven't used it extensively only occasionally.

We are all beta testers for any phone we use. How do you think they know what to change and fix for future models.
Still it sure does not seem so awful for most others.
Plus, we have no idea what apps you may be using that may be messing things up.
Sent from my Nexus 4 using xda app-developers app

Richieboy67 said:
We are all beta testers for any phone we use. How do you think they know what to change and fix for future models.
Still it sure does not seem so awful for most others.
Plus, we have no idea what apps you may be using that may be messing things up.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
He should get a Nokia as the beta test is over for Nokia's ..lol
Sent from my Nexus 4 using Tapatalk 2

I totally agree with OP.
Was in Switzerland last week and the camera also decided to stop working, flash would stay on, screen wouldn't turn off and it was boiling.
Turned it on and off but during those 2 days happened more then once.
It was embarrassing because I was telling my family how good this phone was but they just laughed at me. Everyone one else has an iPhone even the kids (3 iPads, 4 iPhone, 2 imacs)
So difficult to get one so might sell mine. I want a phone that works and I am not spending my money to do beta tests.
Ps. This is my second one and I we are not even talking about the rattle and the buzzing
Sent from my Nexus 4 using xda premium

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.

Crash - Bug or just me?

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.