Related
So I am hoping someone with some real hardware/software knowledge can provide some input...
I recently received my warranty replacement unit because of unresponsive touch and phantom touches. My new unit seems to work perfectly, except now every 10 to 20 touches, the touch will register, but the touch sound "click" doesn't play (if I put my ear close to the speaker, I can hear the speaker activating though). Repeated touches (like repeatedly pressing back) won't reproduce the problem, but more random timing and touches (like in regular use or typing) will. I'm wondering if anyone thinks this is a hardware issue, or some component of the stock software that wouldn't have been overwritten between the update to JSS15Q, and then to JSS15R (it happens in all three versions).
Think I should go for another replacement? Or do you think I should root and unlock, and see if a full installation of a ROM fixes it. It's definitely a sign that something is wrong and it's annoying, I just can't figure out if it's software or hardware related. I'm definitely not going to just ignore it.
(SIDE STORY: When I called nexus help for my first unit, the guy was so helpful and took my word that I had already tried factory resets, and set me up for an RMA. My call on this unit, the woman told me to reboot and toggle touch sounds, and kind of rudely insisted that I was on 4.3 and that Build Version (e.g. JSS15R) had nothing to do with software!! :what: She then told me she'd send me an email with more troubleshooting steps, which never came. I had figured I'd wait for the email, so that I had her name for my next call. Totally unacceptable.)
You come off as just looking for a reason to complain at this point, there doesn't seem to be any real problem with your device other than you being overly picky
Sent from my HTC One using Tapatalk 4
You're completely right. I was so delighted when I managed to find something wrong with my new tablet...
Seriously? You come off as just a worthless ass of a poster at this point. The problem is there, and can be consistently reproduced. I press home and it clicks, and five seconds later I press home and it doesn't click. Your opinion on whether this is a "real problem" or me being overly "picky" is completely irrelevant. It is most certainly real and not normal, and indicates either some software or driver bug on my device, or a strange hardware malfunction. My previous unit (which had very real problems) did not have this problem.
I hope I speak for others here, when I tell you to **** off unless you have something worthwhile to contribute. Just because you don't think something is important, annoying, significant, etc. doesn't make it any less so for someone else.
Do you have this issue with SwiftKey?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yeah. It's actually everywhere throughout the OS. System settings, stock launcher, Nova launcher, Swiftkey, AOSP keyboard, etc.
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
GoneTomorrow said:
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
Click to expand...
Click to collapse
Exactly my thoughts on going through another RMA. But I do feel that it's reasonable to expect a properly functioning tablet on our parts. What you're experiencing is strange. I can tell you that on my Optimus G, when muted, I can hear a faint speaker "activation". Sounds like maybe yours is a hardware issue. Are you stock, or have you tried flashing other ROMs?
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
FYI: I've seen this on multiple tablets (TF101, GTab, Nooks, 2012N7, 2013N7) with different customed ROMs.
So, I wouldn't blame it specially on the Tab. In fact, I see this issue less often on the 2013N7. It usually happens
after I just freshly loaded a new ROM.
spackmanbr said:
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
Click to expand...
Click to collapse
So a couple of nights ago, I decided to try disabling touch sounds in settings. Since doing that I haven't heard a single pop from the speakers. Looks like it was either the touch sounds 'leaking' or the speakers popping from being activated, which they do even when muted (the mute being software)
I'm quite happy with this fix, since the tablet is muted 99.5% of the time, and I don't care for the touch sounds anyway.
Hi Folk's,
Sorry to drag up an old post, but I've noticed my N7 shows this behaviour on KitKat as well.
It misses the touch sound if you pause for about 5 secs during input. Does it every time and it's very annoying. I've tried a couple of different KK roms and it does the same on all of them.
Just tried going back to CM10.2 (JB 4.3) and it works fine!
Does anyone know the cure for this, apart from going back to JB, please? Would really like to be running KK, but this bug is bugging me!
Thanks for any info.
Cheers
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Petermira said:
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Click to expand...
Click to collapse
@Petermira @Xi2or @spackmanbr
I have this same behavior on a stock 4.4.2 S3.
After 5 seconds, if I click anything UI (keyboard, Soft buttons, shortcuts, toggles) there is no sound. If I quickly click again and keep clicking, the sounds work as normal. It's definitely ROM related but is there a fix???
UPDATE: Issue does not happen with headphones plugged in. STRANGE!!!
UPDATE: Issue does not happen if I keep a song playing in Power Amp or similar.
Affected UI items include:
- keyboard
- shortcuts
- toggles
- capacitive buttons
- dialer pad
- etc.
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Ettepetje said:
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Click to expand...
Click to collapse
have you tried beta 4.3
tonytownsend said:
have you tried beta 4.3
Click to expand...
Click to collapse
Am doing so as we speak type. Nope, still buggy (same bugs).
I must be using the iPad too often because I find I'm unable to select words and then, afterwards, apply strike.
Edit: It also inserts spaces after it erroneously inserted "[ strike][ /strike]" (without the spaces) at the start of the post, in stead of around "speak", making me have to edit "[ QUOTE=tonytownsend" afterwards... Hopefully most of this is solvable in future.
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying touchscreen issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds without moving them
- If the touch indicators suddenly disappear, you have the same touchscreen issues
Kizune said:
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying multi-touch issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control. Single-finger operations and the S Pen kept working fine, though.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds
- If the touch indicators suddenly disappear, your touchscreen has multi-touch issues
Click to expand...
Click to collapse
I sure hope not. I started a whole topic on the Note 3 forum because I discovered it had a multitouch problem. Haven't been able to produce that type of multitouch issue on any of my other gear besides a Nexus 7. Will check with your method to see what it gives.
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
I discovered that my fingers got remembered (stayed) on the screen if I left 5 of them on the screen. Happened only ones though. Then I tried puting my whole hand on it for a few seconds and then the multitouch algorithm went bananas. Tried with different Multi-touch app too. I think this is a software issue, from the looks of it.
SwiftKey has been giving me problems on my 2014 Note 10.1 from day 1, but they had become 10 times worse today. I just rebooted my Note and it now behaves as normal (still somewhat buggy SwiftKey, like before). I think there are some issues in the Multitouch driver which can be triggered by the "whole hand" method described above, and possibly by other means. My MT driver had already become unstable, hence I could reproduce a defect (finger touches remaining on the screen) without the "whole hand" thing.
Kizune said:
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
Click to expand...
Click to collapse
Kizune, I included your video in a topic about this Multi-touch issue, I hope you don't mind.
Of course it's okay. Let's just hope that Samsung will fix the problem ASAP, it annoys the hell out of me.
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Itchiee said:
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Click to expand...
Click to collapse
I will very probably be doing the same. Thanks for getting back on topic.
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Sent from my HTC One using XDA Premium HD app
SlimJ87D said:
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Click to expand...
Click to collapse
I use the same (Tablet) version. Possibly it is caused by a combination of settings. I have most (aiding) options switched off. If I find the time I will experiment.
Try "Touchpal"..it's similar to Swiftkey.. it's free and has plenty of thenes. I actually like it better
Sent from my SAMSUNG-SM-N900A using xda premium
Newest SwiftKey is running perfectly for me on the Note 2014. It's so nice to be able to have a compact keyboard you can undock and move from any part of the screen to another. So convenient for applications. Highly recommended, please try it if you haven't
Hi guys I have a problem with the touch response on my G4 (H815)
Basically when I use multi touch (and sometimes just normal scrolling) in certain apps the phone will recognize screen taps at the bottom of the screen at the home and back buttons and sometimes other areas, I have used the 'multi touch app' from the play store to confirm that this is indeed the case. This is extremely annoying as apps exit by themselves because of this. It doesn't happen every single time either, just sometimes but often enough for it to be annoying and so may be hard to prove to my carrier or LG if i send it back cause they may say there's nothing wrong with it.
It seems like a hardware issue and in that case the phone should still be under warranty right? I got it in August and haven't rooted or done anything invasive.
There are many people having issues with the G4 touchscreen. Check with your carrier and see if you can exchange it or what your options are.
Hi,
Same problem for me, the back and home button seems possessed. Se this video dropbox.com/s/540ozmvdnhemv8f/MOV_0005.mp4?dl=0 for an example. I bought the phone Thursday last week and it have been this pretty much since unboxing. After a factory reset the phone acts normal for a couple of minutes or hours, but goes back to that stage were I can't use the phone at all. I've managed to update to the latest software but the problem didn't go away. I'll try to contact the supplier I bought the phone from and exchange it tomorrow.
Since I do not have enough posts to post external links you have to figure out for youself what to type infront of the "link" I included.
My Nexus 7 2013 model has some touchscreen issues. It's like the touchscreen craps out for a split second. when dragging icons from one home screen to another when i try to go to the edge of the screen to switch to the next screen it drops it on the side of that screen or the next one pushing another icon out of the way. then i have to move it again and move the other icon back only to have it happen again to the next home screen. always had this problem. also when typing it registers each letter multiple times so it looks like this: hhhhii hhhoooww aarree youuu. or something to that effect. it's really annoying. i finally gave up and went my computer to Facebook message someone. and then swipe is all messed up and it gives off the wall words and stuff because it doesn't register which words i'm trying to spell out. Often when using a news app i try to click to play a news video and it doesn't register my clicks. also on the web browser it has trouble registering my key-presses or touch for links or numbers or arrows when advancing to the next page in forums or web-pages. If that makes any since. and when trying to zoom in or out on the T mobile map is screws up almost every time and zooms completely out. anyways i hope you get the picture. has anyone else have this problem? it's quite annoying. I've been wanting to post about it for the last year but thought it was just my fingers.
My touchscreen is borked too. I can't type any sh*t, overall the UX has been f***ed up due to these non-sense touchscreen issues. Tried all possible hardware fixes available on net. Teared down tablet piece-by-piece, still no luck :/ . Bought this beauty in 2014, worked fine till mid-2016. Now it's a crap. I still can't find any worthy tablet to replace this beast. Will never buy any Mobile device from ASUS.
I know. I've reset mine a few times but that didn't help. It's working fine at the moment as I'm typing with it right now. Seems intermittent.
Sent from my Nexus 7 using Tapatalk
I've had the note10+ for about a month now. And as of recently I keep getting random vibrations. I downloaded nice catch. All it shows is system notification.
Galaxy note 10+ random vibrations
I've noticed this since the last update.
It doesn't happen after a restart for a couple of hours but after that, it happens after interaction with the touch screen. Nice catch doesn't catch it because it logs only from apps. Even the edge panel doesn't get registered. Initially I thought it was my case causing a touch on the part of the screen that vibrated but even after a case change the issue is still there. Its concerning but not too serious.
And it seems I'm not alone.
Several users of other galaxy phones have also faced a similar issue.
The vibration is very short, like a single tap, like when you type on the keyboard.
And I've even managed to recreate it by putting my hand very close to the screen (once it starts acting up)
It mostly happens when the device is warm.
My NFC is left disabled. And Bluetooth is off.
Only WiFi is on all the time.
This has been puzzling me for quiet sometime.
Could be NFC icw cover with cards in it?
With NiceCatch module of GoodLock (or NiceLock) it is logged and shows you what caused the system (or other-) sound and vibrations...
Sorry folks the day I posted this I was involved in a head on motorcycle accident with a gmc Sierra. I am alive and well. And now I have the fold3 obviously I never figured out what caused the unusual vibrations.... but oh well