Related
I haven't seen this posted here, but it seems to be pretty prevalent on the Amazon.com forum(s) for the KFHD.
Every now and then, when I wake the KFHD, presumably from a deep sleep, the speaker makes a pop sound, like when you restart a stereo or computer hooked up to a powered sub. Seems like a lot of people have this happen. I wanna say it started after i removed the ads from the lockscreen but can't be certain. I'm pretty sure it's a software issue that could be fixed with a patch as everything seems fine otherwise.
Hasn't caused an issue, but I see it leading to a problem down the road. What's the warranty on this? 1 year? Are warranty claims handled through Amazon regardless of where the device was purchased (Best Buy?)
I have it. Haven't removed the ads, but am rooted. I thought it was because I dropped it, but now I guess not...
Sent from my KFTT using xda app-developers app
This has been posted in the questions section. Multiple people including myself have noticed this issue. People reported this happening if the volume is set middle to high. No reason as to why but possibly software related bug.
Moved To Q&A
Please post questions in the Q&A section
alkemist80 said:
This has been posted in the questions section. Multiple people including myself have noticed this issue. People reported this happening if the volume is set middle to high. No reason as to why but possibly software related bug.
Click to expand...
Click to collapse
It [has] happened to me randomly very rarely seems like a software bug
Sent from my KFTT using Tapatalk 2
dank101 said:
It [has] happened to me randomly very rarely seems like a software bug
Sent from my KFTT using Tapatalk 2
Click to expand...
Click to collapse
It's a common occurrence for me, on power off and reboot. I suspect that it is a driver issue. It's almost as though the power to the speaker amplifier is being powered down abruptly. Amazon support knows of the problem, and as usual, they thanked me for reporting it and said that their technicians were working diligently to find a resolution.
Happens all the time to me too
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
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=39892
it's pretty sad that there's only 45 votes on this issue. Here's a hint: bugs won't get fixed if people don't speak up about them. And don't think your voice exactly resonates here on XDA.
Just star it, and leave a comment. Doesn't have to be anything long winded either.
Sent from my Nexus 10 using xda premium
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Troute said:
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Click to expand...
Click to collapse
While agree it's not the end of the world, it's a complaint I see often here in kernel and ROM threads. While a lot of it is due to wonky behavior due to OC (either CPU or GPU), it's really just exacerbating an issue that is already present.
Besides, UI bugs are some of the most prevalent and immediately noticeable to more "common" end users. While functionally it's not debilitating, it's an aesthetic scar that doesn't need to be there.
Sent from my Nexus 10 using xda premium
Hmmm.. So I assume it doesn't matter that I need exactly 15 seconds everytime I get a notification to pull down the status bar, caused by flipbacks. Okay I'm like 1000% sure Google noticed it anyway, cause its on most devices, also 100% stock ones (like me) so...
Sent from my Galaxy Nexus using xda premium
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
jbdan said:
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If it would bounce back after a reboot one time, I wouldn't care, but its always there, it doesn't matter what I do, it bounces every time... So its a bit annoying.. This is the only thing which sometimes makes me want to throw the 7 at a wall...
Sent from my Galaxy Nexus using xda premium
Thanks OP, have added my star.
I had not noticed this problem but I was intrigued.
I could not duplicate the problem, but I am using Apex launcher, not the stock launcher. Does the problem occur in all launchers? Also I am not using the stock ROM.
I wonder if this problem happens with only some units, or perhaps it relates to those user's expectations. Maybe they expect their device to react more quickly than it is able to.
Far be it for me to be dismissive of people's satisfaction with their devices, but that bug-report thread has a lot of problems. It contains over-reaching claims and supposed knowledge of the problem's causes and solutions.
Again, I don't write off these people's unhappiness but I personally would not star that issue.
i too have this problem when on stock rom..now on PA beta 9 with m-kernel, the problem still exist...and it's very annoying...i even thought there was a problem with my touch screen panel and sent it to asus for repair but when i got it back, the same problem still remains..
Not starring because it does not bother me.
Life has too many other issues to worry about having to occasionally re-swipe.
Now pop-up ads in the Yahoo app could get me started...
squshy 7 said:
Come on guys, with all the members here and all the people who like to complain, it's pretty sad that there's only 45 votes on this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
I noticed this issue minutes after pulling this thing out of the box, this might not bother you people who casually use their tablets, but top those of us who have been using android since the G1 notice this. It bothers me so much that I am considering taking this junk back and using the money to get a real tablet from Samsung.
This issue is so annoying to me, I not only notice it on the stock launcher, but also Nova and Apex. Now, the launcher I can deal with, but where I becomes a deal breaker for me is the browser, whether it's chrome or the stock browser in CM10. Trying to scroll around the OS that requires some flicking reminds me of trying to flick scroll on a resistive touch screen, I think that best describes the issue.
I just wanna know if it's fixable through a software update or a hardware problem, cause if it's the latter, this thing is going back, and that's too bad because it was a Santa gift, so I'll have some explaining to do.......
compact_bijou said:
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
Click to expand...
Click to collapse
As I stated (not in precise terms sorry) in the OP, it would be a mistake to think that xda threads are the first place companies like Google and Asus check to see what issues people are having. They have issue and bug trackers for a reason. The universe does not revolve around our little community.
Also, this issue pertains to the general consensus that touch screen issues (like bounce back) have become exacerbated on 4.2 and above. Not anything regarding physical QC issues (though, to be fair, may very well be the root cause, but that is an entirely different issue; the fact of the matter remains that anecdotally it appears the touchscreen responded better on 4.1.2)
And besides, I'm just looking out for the well being of this device's future. Reporting bugs on bug trackers is important to these developers.
Sent from my Nexus 10 using xda premium
to be honest, this annoys me a lot.
starred and commented.
This really annoys me as well. I voted and commented. Hopefully they can get this fixed soon. Otherwise I might switch to CM10.
Sent from my Nexus 7 using xda app-developers app
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
leonclement said:
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
Click to expand...
Click to collapse
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
farmerbb said:
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
Click to expand...
Click to collapse
Yea the notification bar is better on 4.2.2, but the launcher still does it, nova prime does it too, and even when on dolphin or boat browser sometimes when you flick it will scroll nicely & sometimes a flick wont move the page much at all, weird and annoying, would be a much better experience if it was fixed!
This is a huge issue for me. Is there a way to increase or decrease sensitivity? Maybe that would help.
Sent from my Nexus 7 using xda app-developers app
Interesting, I thought I was the only one who had noticed this. Don't know why I haven't seen this thread earlier.
For me I solved this by using apex launcher, somehow you never get those annoying jumpbacks. I tried nova launcher as well but it worked as bad as the original launcher. Going to star tomorrow.
Sent from my GT-I9300
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.
Since mods for our phone is spread out over 5 different device threads, here is a composed list of all the available mods I have found for our phones. Unless otherwise posted I have personally tested these mods, on my G925A (AT&T S6 Edge)
PingPong Root
Viper4Android
Head Phone boost
DolbyDigitalPlus Port (untested by myself, Anyone use that can vouche?)
Edge Battey Feeds
Quick launch edge feed
Music Edge Feeds
Disable DVFS
Remove brightness slider from drop down menu
Remove wifi notification from drop menu
using FlashFire for ZIPS (non XDA link)
Remove camera restrictions and compression (non XDA link) (Untested by myself, Anyone use that can vouche?)
UPDATE 6/4/15
Black Amoled theme
Smart Manager
Verizon Themes on AT&T
*************************************************************************************************
If you have any other Mods, post them here and I will edit the OP. I want to make finding MODS as easy as possible for folks
And if I helped you find a mod, hit the thanks button!
this is great, thanks for the list.
How did you manage to make the volume boost to work? I have exactly the same problem that I totally lose calls in and out audio.
http://forum.xda-developers.com/att-galaxy-s6/general/boost-headphone-volume-root-required-t3114480
I will edit the OP with this link. I linked the wrong one originally
Sent from my SAMSUNG-SM-G925A using XDA Premium HD app
Don't know too much about the AT&T variants, but just wanted to post this incase it works for you guys. If it works, seems like an awesome way to add a bunch of modifications.
http://forum.xda-developers.com/galaxy-s6/development/framework-alliance-framework-v1-one-t3126627
Shortly after posting my question I followed the instructions in that same post and it worked fine for me. I had to put the value in 40 because in 50 it sounds very distorted. Played around with the vaules until I found that 40 is the best one for me.
justda said:
http://forum.xda-developers.com/att-galaxy-s6/general/boost-headphone-volume-root-required-t3114480
I will edit the OP with this link. I linked the wrong one originally
Sent from my SAMSUNG-SM-G925A using XDA Premium HD app
Click to expand...
Click to collapse
Well glad you found a way to make it work.
Sent from my SAMSUNG-SM-G925A using XDA Premium HD app
Hey all! I just wanted to report my discoveries today. I have had a T-Mobile flat S6 for a little over a month now. My father has a S4 that I gave him awhile back, but wanted to get something new. I decided to give him my S6, and get an AT&T S6 Edge for myself. I'm' pretty used to being able to fully modify every aspect of my phones, because I normally only buy phones with unlocked bootloaders. I've done quite a bit of research, and experimentation, and found that even though we are pretty limited in our choices, we can indeed get something like the Alliance Framework to work, which adds a lot of functionality. What I did was install the XtreStoLite ROM from the main S6 Edge section using FlashFire. When it flashes, it will take you to an aroma installer. Could just be my phone, but the phone went totally crazy. Started flashing like crazy, but you could make out the aroma options. I was able to check the options I wanted, and flash. The install worked! After going through and setting things up, I then flashed the secondary package that you can install with the XtreStoLite ROM. Same thing happened where the phone would flash like an old tv that couldn't find signal. I was able to check all the modifications, including the built in Alliance Framework. It flashed fine, but got stuck trying to reboot. I manually rebooted, and after a few minutes, the phone came back on like normal. I checked everything, and the Alliance modifications are fully functioning. I just thought I'd share with you all, in case anyone is mod happy like I am. The link to the ROM is below:
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Thanks for this find! Now I wonder if any other aroma roms work,lol
No signal issues or FC's? Or any major issues at all
Sent from my SAMSUNG-SM-G925A using XDA Premium HD app
No issues! I've been using it all day. Talked on the phone through bluetooth and the built in speaker. Was able to call out and receive calls. Made plenty of texts. Played quite a bit of youtube and netflix. I was also able to install the cocktail mod. Phone feels super snappy also. No lag whatsoever.
If anyone has any questions, I'd be glad to help! :good:
Moostafa29 said:
No issues! I've been using it all day. Talked on the phone through bluetooth and the built in speaker. Was able to call out and receive calls. Made plenty of texts. Played quite a bit of youtube and netflix. I was also able to install the cocktail mod. Phone feels super snappy also. No lag whatsoever.
If anyone has any questions, I'd be glad to help! :good:
Click to expand...
Click to collapse
I installed and am running also.
Lots of custom colors to play with
Sent from my SM-G925A using XDA Premium HD app
Be careful. Many 925A users, like myself are having GPS issues. Dev is supposed to be fixing I would hold off on XtreStoLite for now
dirtyballoonot said:
Be careful. Many 925A users, like myself are having GPS issues. Dev is supposed to be fixing I would hold off on XtreStoLite for now
Click to expand...
Click to collapse
I can confirm the GPS issues. Had it all setup and I liked how good the rom was but without the GPS it's useless. So back to stock.
Sent from my SAMSUNG-SM-G925A using Tapatalk
http://forum.xda-developers.com/showthread.php?p=61606751
At&t GPS fix
Sent from my SM-G925A using XDA Premium HD app