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
Related
Hey folks,
I'm experiencing with my IS, as mentioned in the title, an input lag of the touchscreen. It is not really disturbing, but the fact, that my friends Wildfire recognizes the input better, with Stock 2.1 ROM installed, bothers me really
In the moment I'm S-off on Android Revolution HD 1.1.2, which has a slightly better input than stock 2.3.3, but it is still there. Please tell me, if you are experiencing similar problems.
thanks Max
Only thing I've noticed so far is that if you drag slowly In some applications (like the browser, doesn't matter which browser I'm using) it doesn't scroll at all... but in the settings menu I can swipe downwards as slow as I want to, so I guess what I'm experiencing is software related...
What I really want to know is if I'm alone, or if there has noticed the same thing
Sent from a dumb phone
with my IcS... ive noticed that certain parts of my screen at the randomest times will stop recognizing input.... for me this happens exactly at the O and N key... after leaving it for a few seconds... it starts working again so not much of an issue to me...
there is an app in market place called touchscreen booster... maybe apply that and see if that helps u change the sensitivity...
danial.aw said:
with my IcS... ive noticed that certain parts of my screen at the randomest times will stop recognizing input.... for me this happens exactly at the O and N key... after leaving it for a few seconds... it starts working again so not much of an issue to me...
there is an app in market place called touchscreen booster... maybe apply that and see if that helps u change the sensitivity...
Click to expand...
Click to collapse
thanks for the advice danial.aw. I tried your method, but the only touchscreen booster app i found in the market was for SGS, so that hadn't had any effect
Keeps annoying me buying a 500$ phone that has such a crappy touchscreen...
Sounds to me like you might have a faulty unit if it's bad with both stock and custom ROMs. Never had any issue with mine.
doctorsax said:
Sounds to me like you might have a faulty unit if it's bad with both stock and custom ROMs. Never had any issue with mine.
Click to expand...
Click to collapse
any chance I get warranty for that? the lag is really minimal
Infinite104 said:
any chance I get warranty for that? the lag is really minimal
Click to expand...
Click to collapse
Not a clue I'm afraid. Always worth asking them I suppose.
well yes it says thats its for SGS only... but the app worked on my Atrix when i had it... so im assuming it might actually help more phones than that... try it out and see...
Doesn't make any difference no matter what i set in the app. I will drive to a store today to see if it might be subjective but I don't think so.
Edit: well it's not only subjective, I'll give the warranty a try, lets see how the will react
wooh got all of my money back, I'm moving to WP7 now. Android hasnt persuaded me...maybe again when 4.0 comes out.
Infinite104 said:
wooh got all of my money back, I'm moving to WP7 now. Android hasnt persuaded me...maybe again when 4.0 comes out.
Click to expand...
Click to collapse
If you are leaving android id probably recommend waiting for the next iPhone not wp7
Sent from my HTC Incredible S using XDA App
God WP7 is woeful, the mango update had better fix/add a lot of features...
No I've tested the one from my sister for already two months and I'm very content with WP7. A Phone should be fast and I'm not really into Apple's politics.
You will be in microsofts politics though. WP7 is as closed down as ios. At least with apple you get a good warranty service.
Sent from my HTC Incredible S using XDA App
Short Story:
----------------
Yesterday I bought Google Nexus from my local MacMall (Chicago), and I was pretty stoked. The first thing I noticed upon opening it was that the box had been re-sealed. Then I tried to turn it on and the battery was dead. I thought that was kind of unusual, but not unheard of. Then I charged it and turned it on...
Below are pictures describing what I saw. I am going to exchange the device this afternoon. I was wondering if anyone has ever seen something like this and would anyone be interested in playing around with this ROM. I would imagine it is a proprietary ASUS build, but they sold it to me so it's mine now. I would be happy to post a link to the ROM, but I don't know how to extract it. (I'm sure there is a post explaining that, please direct me to it).
Here are links to the pictures:
There is a weird bar at the top:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS01.jpg
Here is the version info:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS02.jpg
Here are some of the testing apps:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS03.jpg
The serial number is all 1's:
moworldenterprises(dot)com(slash)Testing(slash)Nexus(slash)SS04.jpg
let me know if you want me to post any other information/pictures about the device.
PhatWebah said:
Short Story:
----------------
There is a weird bar at the top:
www.moworldenterprises.com/Testing/Nexus/SS01.jpg
Here is the version info:
www.moworldenterprises.com/Testing/Nexus/SS02.jpg
Here are some of the testing apps:
www.moworldenterprises.com/Testing/Nexus/SS03.jpg
The serial number is all 1's:
www.moworldenterprises.com/Testing/Nexus/SS04.jpg
let me know if you want me to post any other information/pictures about the device.
Click to expand...
Click to collapse
Fixed the links for you.
sweet, hopefully there is something useful
Do NOT return this! This is a very good find! Maybe if you could unlock the bootloader and make a Nandroid backup in CWM...
Perhaps stick it on ebay as a Buy It Now for the price it would cost you to order another one...
That way if it is truly interesting to someone, they have to opportunity of putting up (or shutting up).
No do not unlock it yet, it will erase everything. Do a system image dump. There is a toolkit in the developers section. Post it in there.
Also i noticed its running ICS
Don't send it back yet, let the devs get what they need
DroidHam said:
Don't send it back yet, let the devs get what they need
Click to expand...
Click to collapse
Lol.
The devs don't need anything from this unless you actually want to DOWNGRADE your device.
We can build AOSP from source, we don't need this build for anything at all.
Just put it on eBay :good:
Sorry I'm a Noob
nerfman100 said:
Do NOT return this! This is a very good find! Maybe if you could unlock the bootloader and make a Nandroid backup in CWM...
Click to expand...
Click to collapse
I thought someone here might want this, but I have to return it today (it is for my wife). I'm "good with puters" so I can follow instructions well, but I've never rooted or jailbroken anything in my life. I'm at work so I don't have lots of time to search forums for the proper instructions. If someone really wants this, you have about two hours to post instructions for me to backup or image or whatever it is called a copy of this ROM before I return it. I'll check back every five.
I am downloading the Root Toolkit now
KiNG OMaR said:
Lol.
We can build AOSP from source, we don't need this build for anything at all.
Just put it on eBay :good:
Click to expand...
Click to collapse
Thanks, that's all I needed to know, I'll just return it and get a stock one. Just out of curiosity, and in case someone on the forums wants it, how would I go about "copying" this ROM? and could it be done in the next hour?
DroidHam said:
Don't send it back yet, let the devs get what they need
Click to expand...
Click to collapse
This actually made me lol
You do know this is a nexus tablet right???
Sent from my Nexus 7 using xda premium
ICS on it. How strange. Makes you wonder if they were intending to launch with that on it instead of JB.
Does it have any screen raise issues or faults?
Again, I'm a Noob.
Arthur Hucksake said:
Does it have any screen raise issues or faults?
Click to expand...
Click to collapse
I'm not really sure what you mean by "raise issues or faults". It's hard to show, but when I drag my finger accross the screen, it draws a line with many dots and H and V coordinate lines. That was a horrible description. Basically, it looks like it is mapping the touchscreen feedback and then rendering a line. The line quickly disappears. The white and red boxes at the top of the screen acually have numbers written on them and those numbers change as you touch the screen. There is also like a red Frame the flashes on the screen when I select an app. I will try to post some some pictures/maybe a video. My phone sucks though so the quality wont be that good.
PhatWebah said:
I'm not really sure what you mean by "raise issues or faults". It's hard to show, but when I drag my finger accross the screen, it draws a line with many dots and H and V coordinate lines. That was a horrible description. Basically, it looks like it is mapping the touchscreen feedback and then rendering a line. The line quickly disappears. The white and red boxes at the top of the screen acually have numbers written on them and those numbers change as you touch the screen. There is also like a red Frame the flashes on the screen when I select an app. I will try to post some some pictures/maybe a video. My phone sucks though so the quality wont be that good.
Click to expand...
Click to collapse
What you're describing is the 'Show touches' and 'Pointer Location' options that can be enabled in Settings>Developer options on Jelly Bean.
Video:
moworldenterprises(dot)com (slash)Testing(slash)Nexus(slash)weirdness.3pg
KiNG OMaR said:
Lol.
The devs don't need anything from this unless you actually want to DOWNGRADE your device.
We can build AOSP from source, we don't need this build for anything at all.
Just put it on eBay :good:
Click to expand...
Click to collapse
It appears to have test apps not included in AOSP.
You should try to cold boot to recovery from the bootloader and see if it'll go without being hooked up to a computer. Maybe the bootloader is different than production.
Can't he try flashing the stock rom over this? If there are no hardware faults, why risk getting one that might be defective?
What would devs need from this ... This isn't a Samsung / HTC device
Sent from my HTC One X using Tapatalk 2
Please do a nandroid. Tests have shown ICS has better raw performance than JB. I would love to see an ICS ROM on these at least to just test it out.
Sent from my Nexus 7 using xda app-developers app
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.
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.
This right here pisses me off
Sick of this damn call timer when trying to use other apps during a call.
Although that there isnt the main reason why I'm getting rid of this phone, I'll go ahead and add it to the ever growing list of reasons why I'm dumping it and getting a Nexus 6. Screw LG and their locked down pile of garbage. Sad thing is, it's so much wasted potential.
I love it when a new device comes out, and XDA becomes riddled with whiney posts about "this" or "that" which users say they 'hate' or 'can't stand'. Okay, so there's no publicized root method yet, deemed safe for consumerism, but once that's released I'm sure that every little quarky nuance will have a method to remove, hide, or alter in some way. The call timer has an option for hiding in the LG G3 via G3 Tweaksbox. With that example, I stand confident that this phone will have some type of similarities to, as I mentioned, "deal" with the things people complain about. Fact is, this phone is not impressively different from the G3, and there are no real profoundly engineered improvements made in the G4. You may ask, "Apex, y u bye did fone den?" Good question. My answer is this, I like LG's products and I appreciate the work developers are able to do, in order to make something good, great. So, in the meamtime, until root is available, you won't hear me having a hissy fit about (insert whatever) things. Samsung isn't for me, HTC is bunk, Motorola, well... been there, done that. I think most folks would respect those complaints be made on Reddit, or somewhere besides the place that developers afford us the grace of enjoying what they do for the community, free of charge.
Sent from my LG-H811 using XDA Free mobile app
painedglass said:
Although that there isnt the main reason why I'm getting rid of this phone, I'll go ahead and add it to the ever growing list of reasons why I'm dumping it and getting a Nexus 6. Screw LG and their locked down pile of garbage. Sad thing is, it's so much wasted potential.
Click to expand...
Click to collapse
locked down how? seems pretty rooted to me
lobo4806 said:
locked down how? seems pretty rooted to me
Click to expand...
Click to collapse
TWRP now too.. ROMS will be flowing soon.
Meh, I left the steaming pile of hardware failures that is a Nexus 6 for the G4. Volume rockers stopped working on the first one, new phone had screen issues, ya, the N6 isn't the greatest phone ever.
lobo4806 said:
locked down how? seems pretty rooted to me
Click to expand...
Click to collapse
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
painedglass said:
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
Click to expand...
Click to collapse
Angry much?
painedglass said:
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
Click to expand...
Click to collapse
Because clicking a check box to unlock the bootloader is so hard. Root takes time on all modern devices.
Hahaha... Now root being available, I've installed debloated ROM and 3000mah battery serves me really well. Not to mention boost in speed as well. On stock ROM, I was missing my nexus 5 so much.
I hope you stuck around for a little longer. Feels like beasty phone just got injected with the steroid.
Sent from my LG-H811 using XDA Free mobile app
Agreed....I was fed up with this phone.....root came and glory glory amen it's a better phone. Even with just a simple debloated ROM....can't wait till they really tweak the stock ROM like crazy. I probably won't go aosp....because of the camera app...whole reason I bought the phone...it deletes the side car RAW file in the default gallery aosp can't do that...neither can manual camera app or Fv5
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
The thermal throttling and stuff needs some crazy tweaking...and a better kernel...my apps have to re draw too much...memory leak somewhere
Kingaries79 said:
This right here pisses me off
Sick of this damn call timer when trying to use other apps during a call.
Click to expand...
Click to collapse
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
mawells787 said:
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
this is gold. i dont have a tmobile version, but thanks!!! ahh boo the side effect to this is that when someone calls, you dont see the answer/decline dialog and the notification bar doesnt work
ExTREmE99 said:
this is gold. i dont have a tmobile version, but thanks!!! ahh boo the side effect to this is that when someone calls, you dont see the answer/decline dialog and the notification bar doesnt work
Click to expand...
Click to collapse
I checked and I still get the dialog box, make sure the option is checked in the call settings. I'm not sure what you mean about the notification bar, but I can drag down and click on the call, which brings me back to the call.
Sent from my LG-H811 using Tapatalk
mawells787 said:
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thanks for this
Seems like a really silly reason to get rid of an otherwise awesome phone...
What's funny is that the current root methods as dangerous as they are. Are no more dangerous then when I had my Evo4g, and that team didn't have something like "OEM Unlock" to make it easier. No risk, no reward.
Not to mention that you can drag that icon anywhere on the screen so i dont see how it can be so intrucive during other app usage. Also why dont you just talk on the phone, your on a call, pay attention and stop playing with other apps, real easy
Sent from my LG-H811 using XDA Free mobile app
Apex said:
I love it when a new device comes out, and XDA becomes riddled with whiney posts about "this" or "that" which users say they 'hate' or 'can't stand'. Okay, so there's no publicized root method yet, deemed safe for consumerism, but once that's released I'm sure that every little quarky nuance will have a method to remove, hide, or alter in some way. The call timer has an option for hiding in the LG G3 via G3 Tweaksbox. With that example, I stand confident that this phone will have some type of similarities to, as I mentioned, "deal" with the things people complain about. Fact is, this phone is not impressively different from the G3, and there are no real profoundly engineered improvements made in the G4. You may ask, "Apex, y u bye did fone den?" Good question. My answer is this, I like LG's products and I appreciate the work developers are able to do, in order to make something good, great. So, in the meamtime, until root is available, you won't hear me having a hissy fit about (insert whatever) things. Samsung isn't for me, HTC is bunk, Motorola, well... been there, done that. I think most folks would respect those complaints be made on Reddit, or somewhere besides the place that developers afford us the grace of enjoying what they do for the community, free of charge.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
your point is?
Would you be so kind as to elaborate on
XDA becomes riddled with whiney posts
Click to expand...
Click to collapse