Hi.
My play has an annoying L trigger. When you press it, it clicks and works but you need to add a little bit of effort and it's detected a little slower. It works but it's not very good for fighting games since it doesn't feel so fluid when it is pressed. Pressing it with another button doesn't always work due to the lag (r trigger has no problems). Has anyone have a fix for this.
I'm not really thinking of returning though since I'm just going to play 2 - 4 button games.
I'm thinking of opening it after 6 months in order to adjust the trigger.
how did it go?
Related
So it appears I may have experienced my first hardware problem. Randomly I started having issues this evening with the Dragon, Fly! Game where the back menu would randomly appear while playing. At first I figured it was a terrible ad implementation added into the update that just went through for the game, but then i started experiencing the same issue in multiple applications. This has me worried. I am not running a custom kernel. Has anyone else had this issue yet?
bl4ckcontact said:
So it appears I may have experienced my first hardware problem. Randomly I started having issues this evening with the Dragon, Fly! Game where the back menu would randomly appear while playing. At first I figured it was a terrible ad implementation added into the update that just went through for the game, but then i started experiencing the same issue in multiple applications. This has me worried. I am not running a custom kernel. Has anyone else had this issue yet?
Click to expand...
Click to collapse
You know, that was happening quite often last night when my girlfriend was playing Bunny Shooter... I claimed she was accidentally hitting the back button, but it happened too many times to be her own fingers doing it.
I wonder if the buttons are just too sensitive?
I actually was playing a game, and accidentally hit the back button, and ended my game.
It's the reason I've always been a physical button fan for those four buttons.
I don't see any advantage at all to making them all capacative - too easy to hit accidentally, there's no deliberate "press" required.
geolemon said:
I actually was playing a game, and accidentally hit the back button, and ended my game.
It's the reason I've always been a physical button fan for those four buttons.
I don't see any advantage at all to making them all capacative - too easy to hit accidentally, there's no deliberate "press" required.
Click to expand...
Click to collapse
I know the reason... it saves a couple pennies in production, and, at least in theory, nonmoving parts are far less likely to break.
BUT, I also prefer physical buttons. Especially for ending a call and taking pictures.
I miss the trackpad my Moment had, too...
Dear all
I am new to this forum and new to using HTC, so therefore would like to share my experience and to see whether anyone else shares the same experience:
In terms of battery life, I can get through virtually the whole day on one charge, this includes streaming videos for around 2 hours, playing games like GTA3, Shadowgun, Riptide, for an hour~ Listen to FM radio for 30 minutes and just general texting now and again.
HOWEVER I have had the phone since April 5th and since 2 or 3 days ago I have been experiencing a bug that prevents me from unlocking my phone. Once the screen is blacked out in standby mode and I click the power button to turn on the screen and try to pull the ring up to unlock, I am unable to do so. The ring stays locked at the bottom with a few minor bounces and at the top of the screen a text reads pull the ring up to unlock. The only way for me to unlock the screen is to activate the settings menu from the locked screen and then click the home button. Additionally once I am back from the unlock screen the lower portion of my screen where I had difficulty unlocking the phone operates as normal. I have tried searching this forum but maybe I am a uber noob but can't find any mention of this or any fixes. Does anyone have this issue? Do I need to return my phone? The phone is with Three UK and I purchased the handset through Affordable Mobiles.
Additionally is it me or does the phone not enable multitasking? I have loaded a youtube video for example half way through but if I use the recent app button or home button to access another program say "Fruit Ninja" and then reload into the Internet app, the handset is forced to reload the webpage thus losing all my previous loaded stream. This is the same when I play GTA3 if I hit the home button by mistake and then quickly try to re-enter the game it loads the game from the start rather than resuming the gameplay.
I have recently also seen "noise" and other artifacts and screen anomalies. Additionally the screen flex is becoming more and more noticeable.
Hope someone can help! But atm I am thinking how the hell can they have released this product after alpha and beta testing should have uncovered these issues right?
Best wishes
kingyip said:
Dear all
I am new to this forum and new to using HTC, so therefore would like to share my experience and to see whether anyone else shares the same experience:
In terms of battery life, I can get through virtually the whole day on one charge, this includes streaming videos for around 2 hours, playing games like GTA3, Shadowgun, Riptide, for an hour~ Listen to FM radio for 30 minutes and just general texting now and again.
HOWEVER I have had the phone since April 5th and since 2 or 3 days ago I have been experiencing a bug that prevents me from unlocking my phone. Once the screen is blacked out in standby mode and I click the power button to turn on the screen and try to pull the ring up to unlock, I am unable to do so. The ring stays locked at the bottom with a few minor bounces and at the top of the screen a text reads pull the ring up to unlock. The only way for me to unlock the screen is to activate the settings menu from the locked screen and then click the home button. Additionally once I am back from the unlock screen the lower portion of my screen where I had difficulty unlocking the phone operates as normal. I have tried searching this forum but maybe I am a uber noob but can't find any mention of this or any fixes. Does anyone have this issue? Do I need to return my phone? The phone is with Three UK and I purchased the handset through Affordable Mobiles.
Additionally is it me or does the phone not enable multitasking? I have loaded a youtube video for example half way through but if I use the recent app button or home button to access another program say "Fruit Ninja" and then reload into the Internet app, the handset is forced to reload the webpage thus losing all my previous loaded stream. This is the same when I play GTA3 if I hit the home button by mistake and then quickly try to re-enter the game it loads the game from the start rather than resuming the gameplay.
I have recently also seen "noise" and other artifacts and screen anomalies. Additionally the screen flex is becoming more and more noticeable.
Hope someone can help! But atm I am thinking how the hell can they have released this product after alpha and beta testing should have uncovered these issues right?
Best wishes
Click to expand...
Click to collapse
For the unlocking, do you use a silicone cover for your phone? I heard this stops the screen from working due to static no ground (which would usually be your hand) as the silicone cover isn't a conductor the screen has no ground!!!
I don't have a silicon cover but I do have a screen protecter. Does no one else have a issue with the unlocking ofthe phone
Hi everyone.
Does anyone faced a problem with Real Racing 3 ? Brakes (tap on the left part of display) sometimes doesn't respond. I have to tap twice or even triple to brake. Acceleration seems to be working good. From another side I don't need to tap it so frequently as brakes.
At this moment I didn;t notice anything like that in any other app.
My ROM is JSS15R + ROOT
LOCKDOC_UA said:
Hi everyone.
Does anyone faced a problem with Real Racing 3 ? Brakes (tap on the left part of display) sometimes doesn't respond. I have to tap twice or even triple to brake. Acceleration seems to be working good. From another side I don't need to tap it so frequently as brakes.
At this moment I didn;t notice anything like that in any other app.
My ROM is JSS15R + ROOT
Click to expand...
Click to collapse
Yes mate, I've experienced this with RR3 and CSR Racing but only a handful of times.
I cant quite narrow it down, but i believe that when you are tapping very quickly, maybe a couple of times a second in the same area, this seems to then stop the touch from working for a second or two in that area, perhaps the whole screen but I've not really played around with it.
Again i get the same issues with CSR as you need to feather the throttle just before launch for the best RPM range.
That's the only niggle I've had since buying the Nexus 7.
ddelamareuk said:
Yes mate, I've experienced this with RR3 and CSR Racing but only a handful of times.
I cant quite narrow it down, but i believe that when you are tapping very quickly, maybe a couple of times a second in the same area, this seems to then stop the touch from working for a second or two in that area, perhaps the whole screen but I've not really played around with it.
Again i get the same issues with CSR as you need to feather the throttle just before launch for the best RPM range.
That's the only niggle I've had since buying the Nexus 7.
Click to expand...
Click to collapse
Do you think it is game optimization issue or touch screen issue? I'm crossing my fingers it's optimization... and will be fixed soon. Otherwise I;ll be quite disappointed ((
Presently I've stopped playing RR3 as it's nearly impossible ((
LOCKDOC_UA said:
Do you think it is game optimization issue or touch screen issue? I'm crossing my fingers it's optimization... and will be fixed soon. Otherwise I;ll be quite disappointed ((
Presently I've stopped playing RR3 as it's nearly impossible ((
Click to expand...
Click to collapse
I wouldnt surprised be surprised if there are still a few screen issues considering the update they pushed out to fix the initial issues but for me, I'm not really being affected. At least in games I just need to hit the corners a little faster so I'm not hitting the brake like ABS
For the most part, gaming wise, I think there are issues with certain games picking up the new nexus as a different device from the original. Hence why RR3 has a terrib resolution. Apart from that, everything looks and works great.
As a side note, if you haven't yet, install Ultimate Rotation Control (free) from the Play Store. Open it and set the mode to Auto Forced. Go back to your desktop, hold your nexus in portrait mode like a book and open RR3. When you see the EA blue logo, turn it into landscape and that should improve how RR3 looks. Should help in the short term
How can we solve it
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Clear Data,Cache and retry maybe it's just a lag?did you face any heating problem?
I recommend you to 'tick' show touches option in Developers Options!
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I play clash of clans. This is happening because you are lagging. Just close all other apps before playing. Its all smooth for me
DUHAsianSKILLZ said:
I play clash of clans. This is happening because you are lagging. Just close all other apps before playing. Its all smooth for me
Click to expand...
Click to collapse
Hmm, still happening tonight. I did a fresh reboot and made sure only CoC was running in the task manager. Still had the issue with missed clicks, maybe about 1 in every 8.
enable the deiveloper options (google if you don't know how, it is easy and required to be able to playdeus ex the fall for reasons)
Under developer options there are 2 options under input enable both of them. That will give you a graphical representation of your touches and swipes.
While we are in settings check device/display for touch sensitivity and try checking or unchecking the box to see if that helps you out.
one last thing if you are comming from a smaller screen device you may not have have noticed but touch screens are not pixel perfect in the best of worlds. And on a smaller screen with less pixels it tends to be easier to hit the area you want. Check to see if you are not hitting somethine else by a building by placing walls surrounding a building like a mine or a pump then touch to collect.
This is happening for me also, and it is really annoying. Clash of Clans is the main thing I use the tablet for.
I tried enabling the developer options like was suggested, and it is still happening. Even with the graphical touch and swipe showing where I tapped on something, Clash of Clans is apparently ignoring the action.
Use stylus
It works better if you use a stylus. I have the same problem but I have not yet found the ideal solution. Therefor most of the time, I keep on using my Motorola Xoom to play with CoC.
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I bet you guys using marshmallow os wright ? I have this problem too.. i suspect thr os isnt compatible to coc, or the coc isnt compatible to marshmallow. We need some fixes from both.
echoboomer said:
Just got this tablet yesterday. A big part of my usage will be playing clash of clans (just too addicting). So, when I got home with the Tab last night I played a couple hours of CoC, running stock.
First thing I noticed, the screen is in fact beautiful. Even on the lower brightness settings the colors pop which is amazing.
But... I started to notice touch sensitivity issues in CoC almost immediately. In the game you have to click little buildings to select them / collect resources and such. I noticed that the screen seemed to not be registering some of my clicks. In the most extreme case I'd have to touch a building 2-3 times before it would actually register. Has anyone else had this issue? I've got a couple theories:
1) The screen may be registering my clicks as little tiny swipes instead of presses. Is there any way to adjust the sensitivity on this?
2) Screen may be defective (seems worse on the left side, but could be my imagination)
3) This is just a CoC issue / compatability with the Tab S
Click to expand...
Click to collapse
I have a Samsung Tab 3 and recently the touch screen has gone haywire. I drop a troop at 12oc and heal spell drops randomly at 6oc or wherever. I click on the screen and the screen zooms in and out irradictly . Trying to do a raid must less a war attack is impossible. Anyone have the same issues? Can't play at all atm. Really frustrating
Hi, I’m not sure if this is the right spot but this started occurring on my Nexus 5x. When playing racing games and holding the throttle, it seems to cut out ie deactivate the throttle. It’s almost like its detecting a ‘sticky key’. I think this started occurring when I updated my phone, currently on MHC19J. Admittedly I’m a slacker on updating and was running a decemberish version prior to this, as I find the upgrade process cumbersome when rooted.
Is there any way around to make sure this doesn’t occur and I don’t have to let off the throttle? For reference, the game is Mad Skills Motocross 2. I haven’t found a keyboard (using stock google) setting for this so far.