Related
I got my t-mobile TP2 at the end of August. At first I thought it was the best device ever. The screen was huge and clear. Web browsing was awesome and the keyboard is just the best...
Now a few months later I hate this thing. All the things I love are still true but so many bad things have surfaced.
The phone is slow and unresponsive. I hate that it ignores my inputs and I push the key again and again and again and then it decides to empty the buffer and gives me 15 of the letter I was trying to type. I don't like the wait after I make an entry.
I can't stand the lack of a scroll wheel and Dpad. Take GoogleMaps, I knew before that certain actions were a precise number of scroll clicks and then a click to select. Without the wheel I'm stuck pocking at the screen. I used to be able to use Gmaps driving without looking and only taking attention away from driving for a split second. I can't use it now because it's too risky...
I've tried to speed the device up and make it as close to what I want as possible. I turned off Manila and installed voldpad but it's not enough. I'm sick of hard resetting the device trying to make it faster.
The stupid iphone did this. Microsoft and HTC now think that everyone wants to tap away at screens with gimmicky interfaces and the devices are loosing real functionality.
My 8125 was a better device, buttons everywhere and didn't lag.
Thoughts?
yup, walk to the toilet and flushhhhhhhhhh it
I would have to agree with you to a point. My first device was the 8525 . I have also used the tilt and the fuze. It seemed with each generation, the device loses fuctons out of the box. If it was not for xda, i would be hating these devices and gotten an iphone. The tilt 2 is no exeption but the improvements over the fuze out weight the bad aspectes of the device. It might be awhile before the apps catch up with the hardware.
there has been a new wave of devices that use the sliding keybord layout. e features of the upcoming droid read like the wishlist for htc on the touch pro 2
Crazya said:
The phone is slow and unresponsive. I hate that it ignores my inputs and I push the key again and again and again and then it decides to empty the buffer and gives me 15 of the letter I was trying to type. I don't like the wait after I make an entry.
Click to expand...
Click to collapse
Well, this sounds like a hardware issue to me.. perhaps you have a defective phone. Mine is fine, there are a few software glitches here and there, but overall that problem is not common for this device.
I came from a Wizard, so ya know..
I hear ya, I came from a Samsung i760, quite possibly the last WinMoPro phone that will ever sport a traditional phone button grid on the front of the phone (*plus* an excellent slide-out qwerty.) I got quite used to it, and I could do everything blindfolded. It was also built like a tank, no case needed.
But like you, I was seduced by that big, luscious WVGA screen. And so far Im pretty happy, although I do miss the buttons (and Dpad) alot. "The devils' greatest trick was to make the world think they didnt need phones with buttons" was my mantra.
Well, the tradeoffs are good, good enough that I think I'll stick with the TP2 until something better comes along. The speed is much faster, the screen is, well, gorgeous, and a myriad of little other things make it more preferable than the i760 *OVERALL*.
...but man, I wish I could mate the two little bricks and get the best of both worlds.
Well it just is impossible to have both a large screen and buttons on the front of the phone. I still think this phone is the best of both world with the slide out keyboard. This phone's keyboard is very easy to use and large. My Tilt keyboard would sometimes not register a key input because I didn't push the key hard enough. This one is as fast and easy as typing on my computer.
As for sluggishness, I have had none and still use the default T-Mobile rom with TouchFlo3D. Which is actually very suprising to me in having it work so well. With the Tilt you had to ditch the AT&T rom so fast it wasn't even funny. As for your keyboard problem, it almost sound like a hardware buffer problem or that you have something messing you drivers or freezing your phone. First I would check the Memory Usage and then perhaps dig down deeper into the Task Manager and see CPU Usage of your various apps to see if any are hogging it. Perhaps selectively uninstall software. Or last try a warranty exchange.
Granted, my T-Mobile USA Touch Pro 2 doesn't have much installed or changed yet. It does have Exchange Push activated and Facebook, actuall AIM, MyPhone, Marketplace, Bing, Skyfire, PHM RegEdit, Netflix Mobile, and Garmin Mobile XT installed.
I noticed a huge reduction in issues once I switched to WinMo6.5. The keyboard buffering problem is still there, but it's nowhere near as bad, and only really occurs if you fire up an app and immediately start typing.
You just have to realize that what you typed WILL show up eventually, and that the device will quickly catch up to you. It's no different than opening Windows PowerShell on my laptop, and typing a command while waiting for it to load, it'll execute the command once it's loaded...I don't have to worry...
My problem with the TP2 is that it feels fragile and just too.. plastic.. I've had a HTC Wizard before which didn't feel like cheapass plastic.
Too bad HTC has cut on the quality of their phones.. I don't want my phone to feel like it's going to break when I bend the hinge.
i feel the same way. for me tho, i dont think its the phone... i think ita WinMo6.5. So outdated and UGLY with the 6.5.1 additions of "finger buttons." ive been searching for a phone that i can use on tmo with 3g, othrer than mytouch and g1. i hate those devices. if i could get the rhodium onto hero, life would prolly be better.
I am with you 100% when it comes to the d-pad. I currently am still on the Fuze and miss the d-pad from the Tilt. Left and right on the Fuze is unreliable, but I can still use up and down. I am very hesitant to move "up" to the Tilt 2, and you are confirming my fears.
You are right, and I've also thought that if/when Apple makes an iPhone with a qwerty keyboard, you will suddently see a huge influx of new devices with qwerty keyboards. I also bet Apple will come out with a slick voice recognition interface, then everyone else will be following suit with that too.
I still love mine, but dumped the stock ROM a long time ago. I'm on Fusion v6.0, 21869.
I moved to the Rhodium from the Vogue about a month ago and I have to say I love it as much today as I did the day it arrived, probably more. Stock ROM. I thank God every day the DPAD is gone - what a waste of space. Have experienced no hardware issues and far fewer software issues. For the first time, I have a phone that only gets reset during my weekly backup each Monday morning instead of every day or two. Although initially I hated the addition of the audio jack, I recently had occasion to use it for playing preshow music over a theatre sound system for a play, so even that came it handy, though I will always prefer Bluetooth audio.
All i can say is every one to there own, People will love it People will hate it, Me i love it, On the other hand if you Hate it GET RID and leave us to enjoy ours
Well, I'm glad so many still like it. I think my next step is to check out another unit in the store and see if mine is defective.
I'm also going to look at a new ROM, maybe that will speed it up. Any recommendations as to which one I should try?
Well I am been using it for a few months now and it still runs fine. I haven't flashed any ROM yet. Still with Telstra 6.1 ROM.
However, I do miss the D-pad too. Problem is having a large screen and a D-Pad will make the phone larger. I don't think I want anything larger so if I have to choose I will go with large screen. Otherwise I would have bought the TP instead.
I think that they could get both in there if they tried. Maybe a little joystick like the qtek 8130 or the 2125...
I miss the DPad, but then again, the screen is so much bigger than my Diamond that it's easier to finger navigate. A Blackberry trackball would have been awesome.
I'm two weeks into my Sprint TP2 with stock 6.1 ROM, and I am loving it. I listen to music and watch TV shows on the train during my commute. I just discovered voice command and I'm playing around with it. Selecting media is still a bit dodgy, but making calls works amazingly well without a need to record tags for each contact.
I know these features were available on the Diamond, but the headphone jack and storage card make all the difference in the world. I now realize that 4GB non-expandable storage is a huge liability (and ActiveSync is a slow-ass way to transfer files). The USB adapter discouraged me from using the Diamond for music -- now I listen to music and podcasts when I commute via car. No more staticky, commercial ridden radio for me.
I loaded Fusion visual voicemail, but I haven't been able to use it because I haven't missed a single call since I got the TP2 (with the Treo, Diamond, and Mogul, I would frequently get calls that went straight to voicemail).
And the battery life is a tremendous improvement over the Diamond. When I used the Diamond, I would leave the house with a full charge and then recharge it two more times at work. I don't know if I could get through an entire day on one charge with the TP2 (it would be close), but the charging itself is so much faster that I just need a 20 minute boost towards the end of the day to get me back home. The Diamond would sometimes takes 2 hours to get back to full charge. It was maddening.
I think the two features that would have made this phone perfect are a trackball and more stable screen rotation. Many apps practically crash when you rotate the screen (opera mini has to be restarted if I accidentally open the screen to type, and a couple of times I had to hard reboot because it got locked up). I'm glad the G Sensor doesn't rotate most programs -- I actually find it an annoyance. I prefer portrait mode 99% of the time unless I'm using the keyboard.
And speaking of which, what an awesome keyboard. The Mogul keyboard was awful, which is why I settled for the Diamond instead of waiting for the Touch Pro to come back into stock. I figured I barely ever used the keyboard, so it didn't make sense to spend more money and wait an indefinite amount of time for a feature I didn't even use. The TP2 keyboard is a different animal -- the spaced, offset keys make typing a breeze. I can actually pound out a few paragraphs now without having to correct every fourth letter. It more than makes up for the thickness.
And now that I have the keyboard, I can control emulated games. That was pretty much impossible on the Diamond.
Maybe in a few weeks I could change my mind, but I doubt it. If I could get the VolDpad repeat scroll mode to work properly in Opera Mini, I wouldn't even mind not having a trackball.
I have owned every HTC phone ever offered by AT&T (previously Cingular) , starting with the 2150 (wizard) , Hermes, Kaizer, Raphael, and now Rhodium. The first (2150 or wizard) was almost useless, and although you can see the potential it was practically a piece of trash. With the Hermes and Kaiser things slightly improved especially if I flashed the correct ROM, I still have my Kaiser which I use as a substitute phone. Starting with Fuze (Raphael) these phones are significantly improved, none the less lack of support for a capacitive screen have kept them one or two steps behind the Iphone or even your regular touch screen phones. My son has an LG with Symbian OS and the touch screen works beautifully, and its a lot less cost than these expensive WM phones. The notification remains an issue especially lack of repeat without third party apps.
Yet the versatility and potential for customization is far beyond any other phone. I have to say that if this site was not in existence, most likely I, like many others would have given up on these types of phones a long time ago (HTC listen and heed).
This long winded start of this post is to give you my two cents based on my experience. By virtue of being a member of this site we all make modifications to our phones, install and uninstall a huge number of app and ROMs, we remap keys and make short cuts etc. Windows OS tends to leave behind fragments of programs and registry changes and even key that were created even after uninstalls, and after many of these you have dead snippets of code left behind scattered all over, you also will have other modifications created by these programs that do not revert to original by simple uninstall, leaving your phone operating at a much less than optimal settings, where some setting is causing it to look for a program that does not exist anymore, or it is constantly hunting for things you already uninstalled, etc. My experience with my last two phones from att, is that the original ROM was really optimized specifically for that device, on both after flashing many ROMs I found that the original ROM (minus bloatware loaded by the carrier) gave me the best option for speed and functionality, which made these excellent devices much better than any phone on the market, and yes much better than an Iphone. I also found that after few month with heavy customization my phones became boggy and did not work well. I suggest that if your phone today is not working as well as it did when you first bought it, you should do a hard reset, learn how to us Sashmi which will automatically reload all the programs and settings you need. Other commercial back up programs may back up the settings that are causing the problem, and may not be useful for this purpose. Just try using your phone immediately after a hard reset with no extra software and you might be surprised at how much better it functions. If you reload your programs and it again becomes slow, then a software you are loading that may not be compatible. If so inclined you may want to reload your programs one by one and you should be able to figure out which one is causing the problem. You may have to live without a program that you like; remember many cabs you load from here are Beta modifications that are ported from other devices that may not function well on your phone . If your original OS is not fast enough then you should flash a ROM from this site that was designed for your device based on your carrier. You should remember that although it is a lot of fun to modify your phone, you may not have the best combination for optimizing your phone, and the slowness may be a result of all the fun you had doing that. I don't think it fair to say that your phone does not function well after you changed many things on it. But if you are like me, you will continue to mess with it as long as you are on this site, just remember to reset and start from scratch and things will go back to how they were!
Here's my HTC history:
Hermes (TyTN): Clunky, but a nice phone for its time
Kaiser: (TYTN II): As above, lovely tilting keyboard, faster and the most responsive satnav of them all.
Raphael (Touch Pro): What were they thinking! Screen too small and GPS a total failure, often just not working - and when it did the lag was awful. Hate this phone with a passion.
Rhodium (Touch Pro 2): Great phone. Miss the dpad a bit. No TAB key!! (OK, you can map one). Slight GPS lag. S2U2 pretty much mandatory to avoid calling people from your pocket.
If I couldn't have the Rhodium, I'd go back to my Kaiser.
I have not played enough with my TP2 yet, but I think if you like hardware buttons, you can customize the existing buttons with utilities like AE buttons and many others which allows you even double or triple click on the same buttons. I use it even on Tilt which has D pad and the scroll wheel as well. I would say give it a try.
OK, I'll admit it: I'm a huge fan of Defender 2 game. Downloaded because it was so heavily advertized that my phone suggested it in notification - and played ever since.
Initially, the game played lie a charm, no problems whatsoever. 4.0.2
However, I had some issues with the phone and took it to service a couple of times. After the second time at service, my phone upgraded to 4.0.4 and my troubles with the hame began. I should mention that I'm grateful I had a protective foil because the idiots there managed to seriously scratch it Anyway, the problem:
Every once in a while (2 - 3 games taking 2 - 3 minutes each), the screen just stops responding. My weapon no longer shoots arrows, I can't cast spells, etc, etc. This happens regardless of game time: it can happen during the second game as surely as during the twentieth. Edit: Lasts up to 5 seconds.
However, the non-responsiveness is limited: touch usually stops working on the right (bottom) part of the screen, but still works on the other side (where speaker + front camera are). I have managed to actually observe an instance where the border between working and non-working section was extremely clear at about 1/3 - 2/3 split. Moving my finger in and out of this zone would make the game start shooting arrows again or stop doing it, depending on the zone I moved my finger into.
Perhaps I should also mention that the phone heats up quite a bit during gameplay. However I'm not so sure it should be a factor since the unresponsiveness can happen even right after I start playing. But perhaps that's also a factor to consider?
Anyway - anyone else having these issues or someone that can explain what I'm experiencing?
I started having the same issue yesterday morning as well - except it seems to be ALL the time. The bottom 1/3 of the screen doesn't respond to touch about 50% of the time. Typing is virtually impossible and every touch must be made deliberately and repeatedly. I downloaded a multitouch test and it was quite obvious where the division was between responsive and un-responsive.
I'm rooted on 4.1.1 with stock everything. I restored to my previous nandroid backup from a week ago but still had the problem. Definitely seems like hardware now.
I really don't want to have to buy a third Nexus...
Funny: I just flashed minco ROM which has Francisco's kernel and this doesn't happen any more. Played some 20 rounds so far so I can't say for sure yet, but it seems this rom solves the issue where stock and some others didn't
Latest update: the minco ROM does help, but it does not solve the issue.
I will try to escalate this to Francisco, perhaps (look, I'm an optimist, OK? ) he'll be inclined to look into the issue. Seems to be something few people are aware of. I imagine there aren't many games where one has a fingen onscreen all the time...
A lot of people are experiencing this problem (including me). I'm pretty sure its a software issue. Mine started after I updated my phone from ICS 4.0.2 to 4.0.4...and with jelly bean. I would love for some one to find and correct this issue.
Sent from my Galaxy Nexus using xda app-developers app
Yes, me too - moving from 4.0.2 to .4 seems to be when they introduced the problem. Don't know about lot of people though: searching yielded almost nothing.
About 10 days ago I decided to upgrade my 2012 Nexus 7 to a 2013 model, as I felt the deal on offer was too good to refuse, and there was plenty of life in the tablet yet.
Having kept a close eye on the forums, I was all too aware of the numerous reported display issues, but naïvely hoped that these were no longer such an issue - and that subtle revisions over time would have all but eliminated them.
Initially I thought I was fine, but when setting up Nova Launcher, I did notice on several occasions that a long-press on desktop icons failed to register, and I had to try repeatedly before eventually being able to do such things as rename folders.
Everything else seemed fine, and the display looked good, but I decided to use the “Display Tester” app to double check a few things. Multi-touch seemed fine - 10 touches registered without problem, but the Gamma test screen sent the device crazy - with phantom touches all over the place.
So I read a little more and confirmed others had seen both these issues, but at the end of the day if they only happen rarely, or when displaying some very specific images on screen, should I really worry?
I thought I’d see how it goes, but now I’m finding other subtle issues too. Playing Real Racing 3 for example, where you’ll spend most of your time with the thumb on-screen accelerating, every other race or so the touch de-registers, and you have to lift your thumb off and push it down again to keep the car going... Now I know this never happened on my 2012 Nexus, and it ruins the game play as you invariably don’t notice until other cars start overtaking!
So my question is, is this normal? Were the original issues ever resolved satisfactorily, or do you just live with these issues? I love the tablet otherwise, and would take it back today if I felt confident I’d get a better one, but it concerns me that the one I have may actually be quite “normal” and I may end up with one that’s even worse. It may be fine 95% of the time, but that 5% is really spoiling the experience.
Before returning the device I was considering trying sfhub's fix... Do you think it's likely to help such issues?
Your thoughts on the matter would be greatly appreciated.
Honestly, I think that any issue with a Nexus 7 is to be somewhat expected. My nexus 7 2013 had that fault for about a month when I got it, but I think it slowly went away after about 6 months. Now the only issue with my device is one speck of duct under the screen (which I can live with). But to be honest, it is very subjective. I am pretty sure that the fixes never fix the problem for very long, so you may have to wait this one out. If you play games a lot and this affects you, then return it and replace it. I hope this somehow helps you, I know how annoying it can be to have a faulty device!
I never had any of those issues and bought 2 used off of eBay, one for me and one for my wife. I even broke the screen on one and replaced it myself. And I've never done it before. So I would not say those issues are normal. I think that people who's nexus' work fine don't post about it as much as those with issues. Just my opinion.
Thanks for the feedback... I'm in two minds. On the one hand I have a near perfect device, but on the other it can frustrating, and it shouldn't be (i.e. it's a brand new device - not a refurb. unit). The danger with procrastinating is that as these are nearing the end of their life as "current" products, if I leave it too long I'll have no choice but to send it back to the manufacture, as I won't just be able to switch it in store. I'd be even less confident about a resolution then - especially as the symptoms are relatively rare and specific.
You're quite right though, that people without issues are less likely to shout about it than people with them - so the level of responses also tend to suggest that this isn't "normal" or expected... I feel an exchange may be in order. Worst case, I get one that's not as good - but I'll always have the option to return it.
If its brand new and under warranty, definitely exchange it.
You can also try this. A customer paying good money shouldn't have to, but it can be easier than going through exchanging. TS10 worked great for mine, making touches sensitive like on my first-gen N7.
http://forum.xda-developers.com/showthread.php?t=2428133
Thanks for the feedback - I exchanged it on Friday for another. Was anticipating I might end up with a slightly newer, perhaps subtly revised unit, but ended up with one from an even older batch - July 2013 as opposed to September 2013.
Never mind the age though, this one's definitely better. No lost touches, and altogether more reliable. :good:
Hey
So I'm pretty confident this is going to be my next phone most of the reviews have been favourable and Googles support in terms of updates ect is a big deciding factor.
Just wondering what this community's thoughts are in terms of community dev for the Pixel? I understand is very early days so far so please dont jump on me. I'm just curios if we are expecting this phone to have similar support here like the Nexus devices did? I'm a flash-a-holic however when I got my Note4 here in the UK, somehow I got the C (Exynos) variant where else almost every other Note4 I've seen here in the UK has been F (SD805) so I've missed out on a lot of Non-Samsung rom's for the last couple of years, before that I was spoiled for choice with my S3, and I'd very much like to get back to flashing several times a week playing around seeing what I like and what I don't like.
Anyway again, I know it's early days and it's hard to predict the future but some opinions are best guesses would be really helpful to make my decision and hopefully get what I want from my device this time....
Happy Pixeling
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
I haven't had any issues with my Pixel XL? Maybe because I haven't upgraded to 7.1.1?
Samsung phones are slow and sluggish as all getout IMO.
I have no bugs, great battery life, and the phone flies. Best out of the box experience I ever had. With that being said, I to, hope development picks up. Think with the dual partitions, and phones lack of availability is part of culprit. Once those two things straighten out, well this is a nexus except for the name
No bugs to report here. Everything has been flawless so far.
Development WILL pick up. The Nexus 5X sold at half the price of this phone and it still took a few months for development of truly custom ROMs and kernels to get into high gear.
I have been loving the phone. I got mine at launch and have had very little issues. Everything is fast and stable.
nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
I've had zero issues with mine on 7.1 or 7.1.1, have you tried a reset? I know 5 other people with the Pixel and they all love it and have had no problems.
nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
Sounds like you have a lemon. Had a black 32gb and upgraded to a silver 128gb because I had run out of space. Both had no issues. I'm actually amazed at the speed and smoothness of the overall user experience.
I had an LG V20 right before I traded in the 32 for the 128. It was very underwhelming. Although I appreciate the larger screen real estate, it's quality just wasn't on par with the Pixels. Colour uniformity issues and general graininess. Also found 2 dead pixels. As well, LG's skin over nougat felt very dated. The hardware, while impressive and very well put together, was very clunky. The Pixels hardware takes a backseat to the fantastic software.
Sent from my Pixel XL using Tapatalk
I am sorry to hear you are having so many problems. I have 128GB XL from the google store and do not have the problems you are having. I know that does not help you, just thought I would mention it.
nabbed said:
The phone is buggy as hell - Bluetooth is buggy, Do not disturb mode is buggy, Project FI / cellular connection is buggy, sometimes Google Services just straight up crashes.
To be honest I prefer the less buggy experience with Samsung phones. This frequency of updates Google likes to advertise, it's a blessing and a curse, and for all the bad reasons - they need to update frequently to fix bugs, but with each new update, they seem to introduce new bugs.
Click to expand...
Click to collapse
No bugs at all. Dunno what phones hes using
I haven't seen any bugs either, dnd works flawless, haven't had any issue with Bluetooth, nothing has force closed at all. I do notice my Nexus 6 had a tad bit better service at my house (~3-5dBm). But the funny thing is that my n6 always had higher cell standby use on my battery.
To make it short.
no bugs, great battery ( much better as my Angler ).
Great Device
Love this device. Just got it Tuesday. No bugs that I've seen yet. Went right to 7.1.1 after unboxing so I can't speak to 7.1. I've used bluetooth for car audio, a speaker in my apt, connection to my huawei watch, and wireless headphones for running and have yet to experience an issue with that. No problems on T-Mobile here in LA either. Dont' use DND so can't speak to that. But overall very happy with my purchase!
airmaxx23 said:
I've had zero issues with mine on 7.1 or 7.1.1, have you tried a reset? I know 5 other people with the Pixel and they all love it and have had no problems.
Click to expand...
Click to collapse
Well, you see, if you don't use features then there will be no problems with them.
Bluetooth - many people have reported that the phone would automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When you manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
Do not disturb mode turn itself on occasionally during the day, even though it's set to turn on only at night hours. Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier, even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
nabbed said:
Well, you see, if you don't use features then there will be no problems with them.
Bluetooth - many people reported that the phone will automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
Do not disturb mode turn itself on occasionally during the day, even though it's set to turn only at night hours. Someone has suggested that this particular bug has to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
Click to expand...
Click to collapse
I'm not seeing any of these issues. I use Bluetooth all day and my Moto 360 lives on my wrist. My T-Mobile signal in Boston is way better than it was with my 6p. I have never had dnd turn on by itself and I've had the phone since launch.
toknitup420 said:
I'm not seeing any of these issues. I use Bluetooth all day and my Moto 360 lives on my wrist. My T-Mobile signal in Boston is way better than it was with my 6p. I have never had dnd turn on by itself and I've had the phone since launch.
Click to expand...
Click to collapse
That's why they are bugs and not design decisions. They show up for some people but not others. Maybe it's a combination of apps or a combination of settings that are different between our phones. But all of these people who reported them, they aren't imagining these things. Please at least acknowledge that.
nabbed said:
Well, you see, if you don't use features then there will be no problems with them.
1. Bluetooth - many people have reported that the phone would automatically connect to a bt car kit but it would be in the state of "Connected (no phone)." When you manually reconnect from the bt Settings menu it would work just fine. That's a bug. It may have something to do with a particular car kit, but I tried 3 - Motorola Roadster 2, Jabra Freeway, and a Jarbra Talk bt headset. All 3 started acting up this way after 7.1.1 update.
2. Do not disturb mode turn itself on occasionally during the day, even though it's set to turn on only at night hours. Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected, as this doesn't happen when the watch is disconnected. I wish they would fix that.
3. Project FI just straight up disconnects sometimes for no reason even though I have 3 partners in town US Cell, Sprint and T-Mob. So this bug is probably due to switching to a different carrier, even though US Cell has -60-80 dB signal strength everywhere, and in principle, the phone should stay connected to it all of the time.
4. And when I try to fix Bluetooth issues and play in the settings menu, Google Play Services sometimes just crashes. It's probably related to the bt bug.
None of these are major issues, but they are annoying, especially bt because I use it all of the time.
Click to expand...
Click to collapse
1. Never had any B/T issues.
2. I have had that issue but it turned out to be the phone turning on in my pocket. Other things would turn on too like Flashlight and hot spot. My phone digitizer is just too sensitive. I can almost wave my hand over it to make selections. I also have a Huawei watch and dont feel this has any impact at all. I did chang to the Microsoft lock screen to minimize this (and its nicer than stock and works with fingerprints). But I dont consider my revision of your issue a bug. More like something is just too sensitive on my phone. Which you could turn down the sensitivity.
3. Dont know anything about that.
4. Yes, I can confirm I was doing something with connectivity in the Settings menu and it crashed. This happened on all versions since release. I dont quite recall what I was doing. But yes, I confirm this bug as well.
Well I'm glad I read this thread.
The "Do Not Disturb" bug has been bugging the heck out of me.
Never bothered to check if it was happening to anyone else.
"Someone has suggested that this particular bug had to do with an Android Wear smartwatch being connected"
No Andoid Wear here.
And I always disable the screen wake motion/tap features to prevent my phone screen from turning on when in my pocket. I hate it when that happens and then you notice flashlight through your pocket or pull your phone out and all sorts of freaking apps have opened up and are pissed.
Otherwise, other than lack of development and the huge chins on this phone and the sucky speaker it's been the best phone I've ever had.
Dirty Unicorns is prepping to drop their first XL ROM so my development issues will be resolved with that and the eventual release of Xposed for Nougat.
I seem to have kinda fixed the bt bug by doing something interwebs suggested, Reset Network Settings. I can now work the Jabra headset and will have to try and test the bt car kit tomorrow. But boy, is it simply buggy just trying to troubleshoot this thing! Multiple times after the reset, the bt headset would connect to the phone and be in the normal state "Connected" but would have the "phone audio" feature disabled in a radio button inside the bt device settings. And tapping on the radio button to enable it would do nothing! That was new, never seen that before.
Then I would click the bt on/off switch from the notification pulldown menu, until the thing got stuck in the on position. After a reboot, bt was actually off. I enabled it and finally bt was working.
I got sick of troubleshooting and testing it, so that's where I stopped.
---------- Post added at 06:55 PM ---------- Previous post was at 06:51 PM ----------
CZ Eddie said:
Otherwise, other than lack of development and the huge chins on this phone and the sucky speaker it's been the best phone I've ever had.
Click to expand...
Click to collapse
You should have seen Note 7. It was unlike any new phone before. I've had like 15 flagships on their release, and Note 7 was super special.
RIP!
nabbed said:
You should have seen Note 7. It was unlike any new phone before. I've had like 15 flagships on their release, and Note 7 was super special.
RIP!
Click to expand...
Click to collapse
Fugg Samsung and their lack of developer support and locked bootloaders.
I had every Samsung Superphone since the Galaxy Skyrocket and will never buy another one.
I do support Samsung otherwise though.
They employ thousands of people here in Austin, TX and are sinking Billions of dollars into the local economy. :good:
I've had Honor 7x for about a week now and I love the phone. I experience no lags or any other issues except one. Touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
May I Ask....
pcaseiro said:
I've had Honor 7x for about a week now and I love the phone. I experience no lags or what so ever except one issue, touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
Click to expand...
Click to collapse
Short Answer For Me.. No.
Are you still within your return period ? Swap it out for a new one.. and see if it's any better.
If Not... Sell It.
Didnt have any issue as such..
Get it checked..
I am having the same issue now I believe. Phone worked great for about two weeks then started having screen issues. I have to push a little harder and slower than normal or touches don't want to register. The buttons along the bottom and the pull down menu at the top of the screen seem especially bad. A reboot clears it right up for a time. I'm past the return period so I have to send it in for a warranty repair. Were you able to get the issue resolved with your phone? I'm a little worried with it being a sort of intermittent issue they won't be able to reproduce the issue and won't fix it.
Yes it is buggy !
pcaseiro said:
I've had Honor 7x for about a week now and I love the phone. I experience no lags or any other issues except one. Touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
Click to expand...
Click to collapse
Hi,
Yes, I'm also facing the same issue and thinking that removing the tempered glass may help.
Also, there are lags and lack of responsiveness in this device time to time and I don't feel it as a Hardware issue. Its just that if you are not used to clearing out apps from recents, unlike 90 percent of the other users and if you ever felt the phone's hardware/software competent enough to handle those by itself and at the same time, maintaining the performance, then you are wrong.
Now after a good 2 months of usage, I can say that we will have to wait for a slim pure AOSP rom for this device to please us. Its not at all a balanced device and indeed its a total flop. I feel no joy( and sometimes want to throw it on the wall also) in using it now because of these 3 issues :
1. Time to time lag/hanging - due to not clearing recents frequently - Since I do not believe it is really required for a phone with 4GB ram and Kirin, equal to SD 652 processor. My OP2/ Mi Max and all others used to be much much better than this piece of sh**.
2. Touch not snappy and feels like less responsive for a fast user. May be perfectly fine for the one's using it in a relaxed way.
3. Notification quick reply screen timeout because of not recognising it as an active function.
- From a quite unhappy first time honor user !
I got in touch with customer service and they advised me to factory reset it.
After that phone actually felt better with no issues.
However, I was still within the 15 day return window and I didn't want to take the chance, I sent it back and bought another one.
With the new phone all I can say is that I love the phone. No touch screen issues, no lag what so ever, it is extremely fast and even after I cranked it up with apps it didn't get any slower. I can say that it's faster than my broken Nexus 6p.
Love it
Glad you got a new one sadly I missed my return window. I tried a factory reset and only installed a podcast app different from the one I normally use and actually Uninstaller a few factory apps like Facebook, Instagram and couple Google apps docs and sheets. Still had the issue after some use. Always seems to happen after 20-30 minutes of phone calls. I have contacted support and will most likely be sending it in. I'm getting the b140 update as I type this and the change log says "Performance optimization changes has been included in the current software" so maybe that will fix it. What are the odds. Is it hardware is it software I don't know but I would think if it were hardware a reboot wouldn't make the issue go away for a while but that's probably flawed logic. Also I'm using the US variant (L24) 32gb/3gb.
Touch Screen Issuess
pcaseiro said:
I've had Honor 7x for about a week now and I love the phone. I experience no lags or any other issues except one. Touch screen sometimes acts up and is not responsive and sometimes I have to touch the same spot like two or three times to get it to work and it's so frustrating.
The only way that I'm able to make it work well as it should again is by restarting the phone, and then it's all good until next day or so.
Have you guys noticed the same symptom?
Click to expand...
Click to collapse
I was having a touch issue, but changed in the settings-Smart assistance-touch disable mode (un toggled it)
Well it's been a couple of days since I received the b140 update and so far my screen hasn't acted up. I'm not 100% sure it's fixed but so far so good.
jmjj27551 said:
I was having a touch issue, but changed in the settings-Smart assistance-touch disable mode (un toggled it)
Click to expand...
Click to collapse
This seems to have resolved my issue also. Thanks for the tip!
Since it seems software related, and I imagine this 'feature' is to detect whether you 'meant' to touch the screen or not, it would make sense that this is potentially the problem. In my case especially, I would describe the issue as it seems like my screen falls asleep if I take too long between interactions.
Edit: this actually didn't resolve the issue
-tg
Unfortunately after further testing the issue persists. Most noticeable in clash of clans, Facebook, Snapchat, other slightly higher resource usage apps.
tjg06c said:
Unfortunately after further testing the issue persists. Most noticeable in clash of clans, Facebook, Snapchat, other slightly higher resource usage apps.
Click to expand...
Click to collapse
Still digging in on this, I enabled Show Taps from the developer options and the malfunctioning taps actually do show up when they occur. I sent an email to support 2 days ago with no response yet. Will probably have to call I guess. womp.
-tg
got my phone more than 15 days ago, issue started becoming more prevalent this past week. notably when i'm playing rhythm games (lol). thought ir was the tempered glass screen protector but its now happening with a film/wet application protector. i can't replicate it consistently either. would be interested in updates, this is really frustrating.
sgchrom said:
got my phone more than 15 days ago, issue started becoming more prevalent this past week. notably when i'm playing rhythm games (lol). thought ir was the tempered glass screen protector but its now happening with a film/wet application protector. i can't replicate it consistently either. would be interested in updates, this is really frustrating.
Click to expand...
Click to collapse
I still haven't received an email response, however if you go to the site via mobile you are presented with a live chat option during their business hours (listed on the site https://www.hihonor.com/us/support/index.html). I used that to arrange the repair return for the phone. They don't simply replace it which is kind of frustrating, so I guess it's back to my trusty nexus 5 for a week or two. ?
-tg
i've done some looking around -- i know this thread is much older than the recent UI update, but it looks like the most recent update has messed up the touch sensitivity completely. loads of people are complaining on the hihonor forum. hoping this'll be something they can fix with a patch.
really hoping that i won't have to send it in, this is a replacement for my old phone since the charge port was completely shot. so i'd have to buy a new phone anyway...
thanks for the update, hope this all gets fixed soon!
This appears to be related to the most recent update. That is when it started becoming more of an obvious issue.
Oreo will fix this surely... I had same but now its fixed ?
Touch sensitivity
I'm having the same issue, my screen touch is not sensitive I used to have moto g4 it's been a couple of yrs since I bought it even that screen touch sensitivity is better than this. But overall features camera screen everything is good except the touch sensitivity, I need to click everything a couple of times to respond and even while texting I'm missing out some letters. BTW I won't use any screen guard or tampered glass and it's been a week since I'm using honor 7x.Apart from the screen sensitivity issue I'm damn satisfied with the product.
Thanks,
Aditya
verma.arun833 said:
Oreo will fix this surely... I had same but now its fixed
Click to expand...
Click to collapse
I can also confirm that this is a software issue and is resolved by the Oreo update (currently beta, link below), at least for my case of ghost taps registering on different parts of the screen than what I am actually touching. I've been running Oreo for a week now and this is definitely the phone I was hoping for when I bought it :good: I've been emailing details regarding this issue with a member of their beta support team and it has been relayed to development. Hopefully they can/will release a hotfix for nougat in the meantime.
Oreo is currently in beta. The forum post regarding beta enrollment :
https://forum.xda-developers.com/honor-7x/how-to/how-to-beta-test-emui-8-0-oreo-based-t3757323
I used to have similar problems, particularly when I try to scroll by sliding it would actually open the link if there is one where I first touched. Also writing was difficult on SwiftKey, it would jump over and behaved as if I hit enter.
I joined oreo beta and upgraded yesterday, all these problems seem to have disappeared. Fingers crossed, will wait and see a few more days.