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.
Related
So far I've found
Features:
Lock Screen / home screen rotation
One finger expandable notifications
Bugs still present:
Nvidia prism / washed out colors after video bug
Bugs squashed:
boot loader freezing on reboot to recovery
Post yours. Will confirm and update op
Sent from my Nexus 7 using xda premium
Expanding/Collapsing Notifications With One Finger
http://www.androidpolice.com/2012/1...llapsing-notifications-with-one-finger-video/
Added
I believe the multi touch cross axis issue has been fixed along with the stuttering scroll you'd get (Inside chrome) if you laid your thumb out flatly on the screen.
I can no longer replicate either.
Sent from my Nexus 7
the multitouch issue is still present on mine.
to avoid possible confusions:
issue occours when the tablet is not held in hand or connected to the charger. i.e. grounded.
edit:
the 'bubbles' live wallpaper seems to have a more blue/greenesh color now.
(but could be my imagination)
New location access menu
Just wandering if the random flashing black line has been fixed with this update?
Am still waiting for ota
Sent from my Nexus 7 using Tapatalk 2
simacca said:
Just wandering if the random flashing black line has been fixed with this update?
Click to expand...
Click to collapse
It does not appear to have fixed it.
Frank
Cross axis still present ;( No decent multi-touch yet.
Any idea if the slowdown once you are <3GB space left issue has gone?
/R
rakh1 said:
Any idea if the slowdown once you are <3GB space left issue has gone?
/R
Click to expand...
Click to collapse
You what? I've never had this issue, currently sitting on ~200mbs.
yes did the IO speed improve and the colors of LCD?
rakh1 said:
Any idea if the slowdown once you are <3GB space left issue has gone?
/R
Click to expand...
Click to collapse
Yes it is completely fixed on mine.
Sent from my Galaxy Nexus using xda premium
frankusb said:
It does not appear to have fixed it.
Frank
Click to expand...
Click to collapse
Am now wondering if its some sort of hardware/electrical fault.
Sent from my Nexus 7 using Tapatalk 2
I'm still waiting on my update
Camera app is included with this update.
droidnext said:
Camera app is included with this update.
Click to expand...
Click to collapse
it is? where?
I (and two other people in the touchscreen dead spot thread) can confirm that this issue is fixed. Those of us whose screens started dropping touches and behaving erratically after a few minutes of use no longer have it occurring after 4.1.2, something I am overjoyed about :laugh:
I have noticed that the issue of crossing axes while ungrounded still occurs, but that's entirely forgiveable imho since it's so rare that I don't hold the tablet in my hands, especially for multitouch.
The prism issue persists (washed out colours in general and especially after video), but the Prism Toggle app in the market can disable it with root, so it's not a bother for me.
Meh.
Update doesn't seem amazing to me. Think ill just stick on 4.1.1 for now!
superleeds27 said:
Meh.
Update doesn't seem amazing to me. Think ill just stick on 4.1.1 for now!
Click to expand...
Click to collapse
Sorry for ot.
Up the Tigers! :laugh:
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
Please tell me you can get rid of that ugly black bar menu button in apps. Is there a way to route the menu button to holding down the back button or something? This will decide if I buy the phone or not.
Yes it is possible but at the moment only of you root. The option was available in pre release software so it's always possible HTC will include the option in a future update.
Sent from my HTC One using xda app-developers app
tdingene said:
Yes it is possible but at the moment only of you root. The option was available in pre release software so it's always possible HTC will include the option in a future update.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks, guess I won't be purchasing the phone.
brian85 said:
Thanks, guess I won't be purchasing the phone.
Click to expand...
Click to collapse
That's awesome. Glad u made such a wise decision.
Sent from my HTC One X using xda app-developers app
Wow, not purchasing the phone due to that? Come on dude, please tell me you are not that anal retentive over something so small.
Then again what is small to me, might be huge to someone else.
Losing out on what looks to be an awesome phone and may even be fixed with a future OTA update..
Sent from a galaxy far away!
brian85 said:
Thanks, guess I won't be purchasing the phone.
Click to expand...
Click to collapse
How can you not purchase the phone over a silly problem as that?? anyways rooting is an option also wait for htc to update it
It's not a dealbreaker to me but I understand that it can be for someone as it takes away some screen real estate. For the same reason software buttons are a dealbreaker to so many people.
Because its annoying and takes up real estate on a screen that is only 4.7". I'm confident it will be fixed via software update. But if would sure piss me off until then. Assuming this thing ever gets released I the US... I'll still buy
Sent from my HTC One X using xda premium
CreepyDroid said:
It's not a dealbreaker to me but I understand that it can be for someone as it takes away some screen real estate. For the same reason software buttons are a dealbreaker to so many people.
Click to expand...
Click to collapse
CraigP17 said:
Because its annoying and takes up real estate on a screen that is only 4.7". I'm confident it will be fixed via software update. But if would sure piss me off until then. Assuming this thing ever gets released I the US... I'll still buy
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Both of these. It's annoying as hell and I don't want to "hack" my phone to get rid of it.
I'll wait and see if the US models have the option to get rid of it at launch. If not, different phone for me (I'm not going to wait for a software update that could "possibly" happen).
: Menu button
flyaway9000 said:
How can you not purchase the phone over a silly problem as that?? anyways rooting is an option also wait for htc to update it
Click to expand...
Click to collapse
Honestly... If this was the only new phone coming to the market this year your argument might make sense. I dunno his opinion but for me. I like having a consistent menu button and not having onscreen buttons... Now when you have this and the galaxy s IV among other phones coming out or currently out... And like some of the stuff with each, and one has something that you know aggravates you, it could be enough to send you to a different phone.
Sent from my SGH-T999 using xda premium
I am the one who made the mod to remove that menu button on the screen and reverted back the option to map it on the back button. Apparently it's just a bug and they did not remove it. So expect it to be fixed/back on the next standard update when the phone is already released globally.
brian85 said:
Both of these. It's annoying as hell and I don't want to "hack" my phone to get rid of it.
I'll wait and see if the US models have the option to get rid of it at launch. If not, different phone for me (I'm not going to wait for a software update that could "possibly" happen).
Click to expand...
Click to collapse
brian85 said:
Thanks, guess I won't be purchasing the phone.
Click to expand...
Click to collapse
I thought exactly the same way and even cancelled my pre-order because of that but after playing around with a mates HTC One I was like.... woah this ain't as bad as I thought it would be and ordered one again a couple of days later.
Trust me with the screen as big as it is you end up with the same usable space with the menu bar as the Nexus 4 and I am sure a firmware fix will be coming in the future and/or apps will be updated to match the google guidelines (facebook are you seeing this!!!)
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
Riyal said:
I am the one who made the mod to remove that menu button on the screen and reverted back the option to map it on the back button. Apparently it's just a bug and they did not remove it. So expect it to be fixed/back on the next standard update when the phone is already released globally.
Click to expand...
Click to collapse
Where did you hear it's just a bug and you expect it will be fixed in the next update?
Like I said I was the one who made that mod in the development section. Obviously I already know how it functions/why it's not showing up in the menu/why it's not working in the stock ROM. And the whole code was in there and intact. It was just not updated so it's not showing itself in the menu options.
If I translate the code in english language it goes like this.
Back menu option: Hey are you "HTC One-debug"?
HTC One: No I am "HTC One"
Back menu option: Sorry then you can't use me I'm only available on a device named "HTC One-debug" not "HTC One"
Click to expand...
Click to collapse
So what I did was
HTC One: Hi!
Back menu option: Enough talk! Just use me.
Click to expand...
Click to collapse
Sounds stupid if you're not a programmer but really! That's whats happening there! lol
daleski75 said:
I thought exactly the same way and even cancelled my pre-order because of that but after playing around with a mates HTC One I was like.... woah this ain't as bad as I thought it would be and ordered one again a couple of days later.
Trust me with the screen as big as it is you end up with the same usable space with the menu bar as the Nexus 4 and I am sure a firmware fix will be coming in the future and/or apps will be updated to match the google guidelines (facebook are you seeing this!!!)
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
Where did you hear it's just a bug and you expect it will be fixed in the next update?
Click to expand...
Click to collapse
Riyal said:
Like I said I was the one who made that mod in the development section. Obviously I already know how it functions/why it's not showing up in the menu/why it's not working in the stock ROM. And the whole code was in there and intact. It was just not updated so it's not showing itself in the menu options.
If I translate the code in english language it goes like this.
So what I did was
Sounds stupid if you're not a programmer but really! That's whats happening there! lol
Click to expand...
Click to collapse
I asked about where did you hear the information about the fix in the next update not kiddie speak for explaining how you fixed the issue.
1. Properly designed apps that use Google's design framework will have an in-app menu button. So no black menu bar. Vast majority of apps now won't require the black bar.
2. HTC got rid of it on the One X when user feedback said they wanted it gone. I see no reason to assume they won't do it again if enough people say they don't want it.
Like I said it's just a minor bug. HTC just skipped updating this one piece of code for it to work on the production units.
Meh! I give up! lol
daleski75 said:
I asked about where did you hear the information about the fix in the next update not kiddie speak for explaining how you fixed the issue.
Click to expand...
Click to collapse
daleski75 said:
I asked about where did you hear the information about the fix in the next update not kiddie speak for explaining how you fixed the issue.
Click to expand...
Click to collapse
He was merely explaining how the bug worked to point out that mapping Menu to Long-Back option is, actually, meant to still be there. HTC simply forgot to make sure that scripts in all places were talking about the same device.
Sent from my Tricked out HTC One via xda-developers application
I know it's a bug and how he fixed it but let me quote what he said...
Apparently it's just a bug and they did not remove it. So expect it to be fixed/back on the next standard update when the phone is already released globally.
Was this bit just guessing or is it from a well known source??
JesseMT4G said:
Wow, not purchasing the phone due to that? Come on dude, please tell me you are not that anal retentive over something so small.
Then again what is small to me, might be huge to someone else.
Losing out on what looks to be an awesome phone and may even be fixed with a future OTA update..
Sent from a galaxy far away!
Click to expand...
Click to collapse
Flaming isnt necessary really
People use their phone differently, its the same reason why theres never a "best rom" or a rom with the "best battery life"
And to the other comments, its likely not to be patched so that they have more reasons to sell a "developer" version
I may have a bad news related on HTC to bring back button remapping options.
Just saw engadget chinese mention in their HTC One review about that Google MIGHT be the force behind that lead to HTC sudden removal the remapping option from HTC One's newer ROM because Google insisting the menu button must somehow be 'observable' on sight.
Click to expand...
Click to collapse
Just stumbled on this by accident:
http://forum.xda-developers.com/showthread.php?t=2245907
Basically, One owners are getting OTA update 1.29 that addresses the difficult to press capacitive buttons, improving slow motion low light video recording, better balance the Beats Audio experience (left/right audio), reduce background noise when using headphones, and improve bluetooth device matching.
Lets hope Sprint doesn't drag their feet on this one or ships with it.
My phone came with 1.29. I thought we already had this ota?
Sent from my HTCONE using Tapatalk 2
Gumby63 said:
My phone came with 1.29. I thought we already had this ota?
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Well, now I feel like an idiot. I didn't know. If this is the case, feel free to delete so we don't cause too much confusion. Oops!
gk1984 said:
Well, now I feel like an idiot. I didn't know. If this is the case, feel free to delete so we don't cause too much confusion. Oops!
Click to expand...
Click to collapse
Haha it's all good man
Sent from my HTCONE using Tapatalk 2
Remember though that the last digit in htc's file names are important also.
We may have 1.29.651.7, but that's still pre 1.29.709.12. The 651 and 709 is some carrier/region code.
The .7 means that it is older. I would suspect that if we get an update soon, and it's not a huge update, it will probably be 1.29.651.12+.
AssassinsLament said:
Remember though that the last digit in htc's file names are important also.
We may have 1.29.651.7, but that's still pre 1.29.709.12. The 651 and 709 is some carrier/region code.
The .7 means that it is older. I would suspect that if we get an update soon, and it's not a huge update, it will probably be 1.29.651.12+.
Click to expand...
Click to collapse
I WANT MY HOME BUTTON FIXED!!!!!! I'm gonna swap it today for a new phone to see if that helps. My fear is that the OTA (.12) is to try to compensate for a hardware fault with the home/back buttons. Many people have reported trouble with the buttons, many other have reported no trouble....yet HTC released that .12 update in Taiwan where they specifically say one of the bugs fixedis the unresponsive home/back buttons:
1.29.709.12(214.04MB)
1. virtual key sensitivity adjusted
Click to expand...
Click to collapse
Could just be bull****ting. I see tons of people on 3DS forums say their version of X game isn't running under 30 FPS like everyone else, even though it clearly is. Some people just don't notice these things. With that said, there may be better versions, but I'm guessing there's a ton of people that just don't know any better.
According to Slashgear.com there is an update that will fix some of the quality settings in the camera. Read on :http://www.slashgear.com/htc-one-updated-with-camera-enhancement-suite-and-more-in-europe-23278984/
Yeah, a little disappointing to see that this update isn't moving out to all HTC One handsets, just in the UK. Looks like we'll see the same pattern for updates coming to phones as we've seen in the past. 3 months at a time.
It also depends on the carrier. Hopefully they'll send it out soon.
It has only been pushed out to UNBRANDED handsets in Europe and Asia. This is software 1.29.XXX.12 (where XXX is the region code) and contains many fixes. Personally, the fix I'm most eager to see is the fix for the home/back button sensitivity, but who knows how long it's gonna take for Sprint to push this.
m03sizlak said:
It has only been pushed out to UNBRANDED handsets in Europe and Asia. This is software 1.29.XXX.12 (where XXX is the region code) and contains many fixes. Personally, the fix I'm most eager to see is the fix for the home/back button sensitivity, but who knows how long it's gonna take for Sprint to push this.
Click to expand...
Click to collapse
I'm going to root this mofo and let a ROM set the sensibility for me.
There are little quirks here are there that I would address if I could..
I wish they would have implemented a dedicated camera button.
They are making this phone a camera first, phone second item.
They should have kept it the dedicated camera button like the 4G LTE.
Update before and after
This site has a before and after shot with the camera. One can def. see an improvement.
http://www.androidpit.com/htc-one-u...&utm_medium=News-Stream&utm_content=Variant_1
Meh, with the power of root and our devs, I'm sure someone will port over the enhancements to our device.
robfactory said:
This site has a before and after shot with the camera. One can def. see an improvement.
http://www.androidpit.com/htc-one-u...&utm_medium=News-Stream&utm_content=Variant_1
Click to expand...
Click to collapse
Nice. Hope we get this soon
Sent from my Nexus 7 using Tapatalk HD
I spoke to HTC in the US and the rep told me very soon for an update. He called it a maintenance update. He also told he didn't know about the button issue he spoke with his Cain of command and they had no idea. So he's submitting a ticket about it. I hope more people call in about this and report it that way things can get done quicker.
Sent from my HTCONE using xda premium
aFoodStampBaby said:
I spoke to HTC in the US and the rep told me very soon for an update. He called it a maintenance update. He also told he didn't know about the button issue he spoke with his Cain of command and they had no idea. So he's submitting a ticket about it. I hope more people call in about this and report it that way things can get done quicker.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Awesome!