Related
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
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.
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!
At this point all I really care about is something that will keep my data connection from frequent and random drops. If not it's time to look at other options.
Sent from my HTCONE using xda app-developers app
tommason1968 said:
At this point all I really care about is something that will keep my data connection from frequent and random drops. If not it's time to look at other options.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
NEVER happens to me so I doubt 4.2.2 will remedy for ya. Maybe look into other avenues to resolve this issue
I don't know what else it could be. Others with different devices hold their connection from the same location while mine drops. Whatever the case, it's getting old. I'm done talking to Sprint about it as the answer of "we are working on the towers right now“ doesn't work for me. If they were truly working on them the guys I work with would have the same problem.
Sent from my HTCONE using xda app-developers app
The main reason I want 4.2 is so I can play with non-daily driver ROMs without dealing with the SD card when I go back. Anyone else?
Sent from my HTCONE using Tapatalk 4 Beta
Embluss said:
The main reason I want 4.2 is so I can play with non-daily driver ROMs without dealing with the SD card when I go back. Anyone else?
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
That's probably the only practical reason.
tommason1968,
I know exactly what you are talking about! I had a thread complaining about the same thing. Took my phone into the Sprint store and it failed "once" a test and they gave me a new phone and the exact same thing happens to my current phone. Can't go down the street (or even sometimes sitting still) and I lose data connection. Listen to streaming radio on Tune-In and it cuts out constantly. Used the Scout (Telenav) GPS and always got "There is no cell phone coverage / Now there is cell phone coverage" during a trip to Wisconsin and Mississippi this month.
Heard the excuse that the towers are being upgraded and that is the reason service is so poor. Almost tempted to say well put that in writing so that I can go to another wireless company without an ETF.
Came from the HTC LTE and never had so many drop outs. Yes, there were marginal spots that I would lose service, but in the past I have made it to Wisconsin and back without dropping service once not to mention 50 - 100 times, so like you think it is directly related to the phone. When you take the phone into the Sprint store, they are like well nothing what we can do, or well that is a lot of work and doubt we will find something. It is tempted to reactive my old HTC LTE and see how it does because I know where the marginal areas are at and the areas that are not marginal that I still lose connectivity on a constant basis with my HTC One.
Just wonder if like the first I-phone made of solid shell, that the metal casing isn't affecting how well the phone does in the terms of the ability to connect and stay connected to the cell towers.
For me, it's gotta be the way ZOE clips will be captured as a single video file instead of 20+ images. Each time I take a ZOE clip all those 20 pics get backed up on my G+ cloud.
elrey75 said:
For me, it's gotta be the way ZOE clips will be captured as a single video file instead of 20+ images. Each time I take a ZOE clip all those 20 pics get backed up on my G+ cloud.
Click to expand...
Click to collapse
And the charging speed. And the quick toggles. And hopefully the focus on the camera. And the OS efficiency.
I've managed to get rid of all the lag by turning off all animations. I just need better battery life. Everything else has been promised.
I just want the added features of 4.2.2. I want quick toggles, lock screen widgets, etc. And the added battery percentage and what not.
eXplicit815 said:
I just want the added features of 4.2.2. I want quick toggles, lock screen widgets, etc. And the added battery percentage and what not.
Click to expand...
Click to collapse
What if I told you...
EQS and percentage are already available on Viper and HTC will not incorporate lock screen widgets.
4.3
Who cares about 4.2? 4.3 began rolling out to the Google Experience/Play HTC Ones a few days back which has a functional IR blaster! That, with CM's new camera and this phone is going to be pretty awesome, pretty quickly.
sauprankul said:
What if I told you...
EQS and percentage are already available on Viper and HTC will not incorporate lock screen widgets.
Click to expand...
Click to collapse
I'm with explicit. I like the aosp toggles much much more along with HTC's version of the battery percent. Also, the update will come with lockscreen widgets. They already have the implemented in the Intl version.
I for one am pretty stoked about this update. It will include everything that I like in aosp plus it will have IR.
Sent from my One using Tapatalk 4
Gumby63 said:
I'm with explicit. I like the aosp toggles much much more along with HTC's version of the battery percent. Also, the update will come with lockscreen widgets. They already have the implemented in the Intl version.
I for one am pretty stoked about this update. It will include everything that I like in aosp plus it will have IR.
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
I just want native AVRCP 1.3!!!!!
sauprankul said:
What if I told you...
EQS and percentage are already available on Viper and HTC will not incorporate lock screen widgets.
Click to expand...
Click to collapse
What if I told you...
That the EQS included with Viper looks hideous to some of us?
Just ribbing you, but seriously-- I cannot stand how it looks in the slightest. Native quick toggles are also one less app needed to replicate functionality, which is nice if you're trying to keep things slim.
Rirere said:
What if I told you...
That the EQS included with Viper looks hideous to some of us?
Just ribbing you, but seriously-- I cannot stand how it looks in the slightest. Native quick toggles are also one less app needed to replicate functionality, which is nice if you're trying to keep things slim.
Click to expand...
Click to collapse
Yeah. I think that the EQS are stupid looking too. Just wanted to make sure it was known that most of these features already exist in some form. I love the Holo style EQS, though. In the meantime, I'm using Floating toucher. Its pretty cool.
I'm more excited about the camera improvements. The number of pictures out of focus is too damn high!
I expect that it will be the only update released for this phone.
sonicice said:
I expect that it will be the only update released for this phone.
Click to expand...
Click to collapse
No way. This is a flagship device that's barely 4 months old. Support has to be for at least a year.
sauprankul said:
No way. This is a flagship device that's barely 4 months old. Support has to be for at least a year.
Click to expand...
Click to collapse
Good one
I'd be willing to guess the 4.2.2 delay is a Sprint issue more than an HTC one.
I personally am not even excited about the 4.2.2 update anymore, due to how long it's taken and now that 4.3 is out.
FlowingAway said:
I'd be willing to guess the 4.2.2 delay is a Sprint issue more than an HTC one.
I personally am not even excited about the 4.2.2 update anymore, due to how long it's taken and now that 4.3 is out.
Click to expand...
Click to collapse
I'm not excited about either one. I have a Nexus 7 with 4.3 on it and it doesn't look/feel much different from when I used CM on my LTE. There just isn't anything to really worry about other than the kernel.
http://techtainian.com/news/2014/4/1/android-443-begining-to-hit-nexus-devices
https://plus.google.com/+TheogusperGeorgePhilipPiccadilly/posts/Qh7sBgex1ei
legit?
Well it is April 1st...
looks exactly like if i edited my build.prop to say 4.4.3, rebooted to have the change take affect, started recording a video, boot up, go to about phone and see the 4.4.3. they show no other proof, nor try to.
Google are too busy pi**ing about with pokemon rather than fixing their devices.
simms22 said:
looks exactly like if i edited my build.prop to say 4.4.3, rebooted to have the change take affect, started recording a video, boot up, go to about phone and see the 4.4.3. they show no other proof, nor try to.
Click to expand...
Click to collapse
sadly i have to second this... :/ real easy to do that show us more proof before i get excited.
but i guess its better than no news
Not buying it, too soon for the next update.
jamel_tza said:
Not buying it, too soon for the next update.
Click to expand...
Click to collapse
Too soon for the next update? You do know that 4.4.3 is an incremental update and not a major one right? We have a few bugs that are long overdue.
sent from my neXus 5
OuncE718 said:
Too soon for the next update? You do know that 4.4.3 is an incremental update and not a major one right? We have a few bugs that are long overdue.
sent from my neXus 5
Click to expand...
Click to collapse
Yea, I'm aware. With so many incremental updates in such a short period, it makes more sense for Google to roll these minor fixes with the fix of something that's been inherently broken since the release of the OS like the audio latency issue. We typically get a late spring/summer update, IMO it would be easier to release everything in a bigger update. That's just my opinion, by no means does that make it right.
jamel_tza said:
Yea, I'm aware. With so many incremental updates in such a short period, it makes more sense for Google to roll these minor fixes with the fix of something that's been inherently broken since the release of the OS like the audio latency issue. We typically get a late spring/summer update, IMO it would be easier to release everything in a bigger update. That's just my opinion, by no means does that make it right.
Click to expand...
Click to collapse
I'd also rather things be released in one big update but keep in mind that certain things are just unacceptable. Like how data goes in and out. That's the biggest issue I have with my Nexus 5. Other than that I am in no rush for any other bug fixes.
A "phone" should at least be able to make phone calls and receive text without having to toggle Airplane mode on and off.
sent from my neXus 5
I think this is bull !
We know 4.4.3 will be coming soon and leaked info to date shows a build of KTUxxx and not the build shown in the screenshot.
I guess we can expect this sort of c*** today.
OuncE718 said:
I'd also rather things be released in one big update but keep in mind that certain things are just unacceptable. Like how data goes in and out. That's the biggest issue I have with my Nexus 5. Other than that I am in no rush for any other bug fixes.
A "phone" should at least be able to make phone calls and receive text without having to toggle Airplane mode on and off.
sent from my neXus 5
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda app-developers app
T is for testing
deakelem said:
sadly i have to second this... :/ real easy to do that show us more proof before i get excited.
but i guess its better than no news
Click to expand...
Click to collapse
Look at the build number... Legit.
simms22 said:
looks exactly like if i edited my build.prop to say 4.4.3, rebooted to have the change take affect, started recording a video, boot up, go to about phone and see the 4.4.3. they show no other proof, nor try to.
Click to expand...
Click to collapse
Gesendet von meinem GT-I9505 mit Tapatalk
jamel_tza said:
Not buying it, too soon for the next update.
Click to expand...
Click to collapse
I don't think its too soon for an update. Having said that, this looks pretty fake. It looks like a custom rom to me and the kernel build date is November 20th.
Please continue discussions in the existing thread HERE.
Thread Closed.