Has anyone else tried using the Jot stylus on their Acer? Mine has a really hard time picking up this stylus. The Jot worked great on my previous Toshiba Thrive and other tablets I have tried it on. But for some reason it just will not work on the A510. Is this a software problem or a hardware defect? I have tried toggling the touchscreen sensitivity but it appears to have no affect on the screen sensitivity.
Any ideas?
xamindar said:
Has anyone else tried using the Jot stylus on their Acer? Mine has a really hard time picking up this stylus. The Jot worked great on my previous Toshiba Thrive and other tablets I have tried it on. But for some reason it just will not work on the A510. Is this a software problem or a hardware defect? I have tried toggling the touchscreen sensitivity but it appears to have no affect on the screen sensitivity.
Any ideas?
Click to expand...
Click to collapse
hi I assume you have a screen protector? I have the exact same issue, in fact the screen is so insensitive that I can't even type properly ..
but if I'm holding it I my hands it seems much better.
anyone else with this problem?
same here, pretty much useless. want to buy mine???
JJackJi said:
hi I assume you have a screen protector? I have the exact same issue, in fact the screen is so insensitive that I can't even type properly ..
but if I'm holding it I my hands it seems much better.
anyone else with this problem?
Click to expand...
Click to collapse
Nope, no screen protector yet. But it still doesn't work.
Related
Hello,
I am convinced that something is wrong with the Triumph. I searched for "keyboard" and "response" in the thread titles but got nothing.
Basically, the screen doesn't register my touches consistently. Is this something that is fixable by a software update, or is it faulty hardware? It's almost like I type too fast for the Triumph. But when touching a link, it often doesn't register, either, and it's not localized to any particular area of the screen. Slowing down my typing seems to help, but this is making the phone in my opinion, unusable. I have no reason to believe that I got a faulty unit.
What is the fix for this problem, and sorry if I missed the answers somewhere in the forums.
Have you removed the secondary screen protector?
Sent from my Triumph using XDA App
Attictron said:
Have you removed the secondary screen protector?
Sent from my Triumph using XDA App
Click to expand...
Click to collapse
No, I have not, but I have thought about it. I've heard conflicting reports about whether that helps or not. In the past, I have not noted these screen protectors to be causing the problem. Can anyone speak with authority about whether removing the screen protector solves the response issues? It's a one-way procedure, because there's no way that I'll be able to get that screen protector applied as perfectly as it was at the factory.
Thanks
lamenramen said:
Can anyone speak with authority about whether removing the screen protector solves the response issues?
Click to expand...
Click to collapse
I can't speak with authority, but I can speak based on personal experience. It made a HUGE difference for me. And no, I haven't had any scratches on the screen nor have I had any problems since I removed it.
I can't say but I have notices that when my available RAM falls below 50 mb that the touch becomes less responsive, that and cold fingers.
Screen Lag
JWhipple said:
I can't speak with authority, but I can speak based on personal experience. It made a HUGE difference for me. And no, I haven't had any scratches on the screen nor have I had any problems since I removed it.
Click to expand...
Click to collapse
The touch screen does lag, regardless of the screen protector. Its most apparent to me when opening the app drawer; it's hard to get the screen to roll. I think it's a combination of literally cold fingers as well as a sort of metaphorical coldness of the device itself; it seems that the lag effect diminishes as the device settles into its groove after prolonged use. I notice the lag when the ROM is 'fresh.'
I am on my 2nd T and they both exhibit the quirk. LPP and the new ADW seem to help her work it out. Perplexing little devices on an intentionally-attenuated redheaded step-network, fer sure, but virtually unbrickable, and oh my black jesus do i ever love me my $25/month, contract-free ultimateness.
I've spent a lot of time trying to resolve this issue in the TG-Reloaded CM7 ROM. Updating & rewriting the bi041p touchscreen driver in the kernel. I'm finally ready to just say it's a hardware problem, maybe a grounding issue. The interrupt sometimes just doesn't trigger reliably.
Well they're are two things you can do it increase the touch screen sensitivity,the first way would be to flash ROM or a kernel that has reworked drivers that are supposed to help touchscreen sensitivity a little.The next thing you could do that I think would greatly improve touchscreen sensitivity would be to take of the factory installed screen protector as it is very thick and low quality.
Hi guys.
Before buying my A510, I used to have a SGT 10.1. I sold off my SGT 10.1 2 weeks before getting my A510, so I was never able to do side-by-side comparison between the two.
However, judging by the response in the forums at that time and by my personal usage, it was clear that the Acer tablet had some serious sensitivity issues. I couldn't confirm how bad, but it was bad enough to be noticeable by me based against my SGT 10.1.
To me, the worst thing is when putting the tablet on a hard flat surface, like a table. This is where the sensitivity, for some weird r!eason, takes a very BAD hit. I just got a Note 10.1 yesteray, and used both side by side. The Note could flawlessly take input when laid flat on a table. But not the A510.
Any idea why? Do try if your tab takes a hit when placed on a flat surface and let me know.
Thanks
I had an A510 that I returned for just that reason; sensitivity not only took a hit, it became almost useless when laid on a table. Problem was compounded by a screen protector. A700 seems much better. However the most recent update (1.029 -> 1.057) actually made things worse as far as the touch screen. For a while I flashed back to 1.029. Then I decided to update to 1.057 and root, and now I am using Acer Liquid Settings program which requires root & seems to help sensitivity. I am typing this flat on a table with only 1 or 2 missed touches for this reply, all in the 1st sentence.
Edit: There is a YouTube video that illustrates this problem in the A510 Search A510 problem on YouTube.
eman01 said:
I had an A510 that I returned for just that reason; sensitivity not only took a hit, it became almost useless when laid on a table. Problem was compounded by a screen protector. A700 seems much better. However the most recent update (1.029 -> 1.057) actually made things worse as far as the touch screen. For a while I flashed back to 1.029. Then I decided to update to 1.057 and root, and now I am using Acer Liquid Settings program which requires root & seems to help sensitivity. I am typing this flat on a table with only 1 or 2 missed touches for this reply, all in the 1st sentence.
Edit: There is a YouTube video that illustrates this problem in the A510 Search A510 problem on YouTube.
Click to expand...
Click to collapse
Indeed, I have EXACTLY the same problem as that in the video. The actionbar is TOTALLY unusable on a table. When I lift and use it in my hands, things are much better but still very much worse compared to other tablets.
Now, the thing is, from what I read, an update from Acer caused this issue. Can anybody vouch for that?
I got my tablet in mid-June, and by then it was running on the latest version. I've not gotten any new updates to fix this issue. Assuming it is a software problem, why hasn't Acer issued a hotfix? Also, this must mean ALL A510s are affected right?
screen protector?
ok, may sound a bit weird, but i experienced exactly the same "issue" on my a700. if i use the tab in bed or in the stand i got no touchscreen response. but this inresponsiveness has startet sometimes after mounting a screen protector at the tab. it just takes a while, until i recognised this behavior. travelling around the last weeks and was trying to navigate through the music library at the hotel brought the problem up first time.
since i removed the protector foil, the touchscreen response is back in all situations.
regards
There have been past threads on different devices that point to a grounding issue when this occurs. Your body is a conductor when holding the tablet so it works better. If the device is grounded properly then there isn't an issue either way. If your saying this was the result of an update then that's better then a hardware issue since it can be fixed much easier, once the company is made aware of the issue of course.
Don't hold your breath...
Itchiee said:
There have been past threads on different devices that point to a grounding issue when this occurs. Your body is a conductor when holding the tablet so it works better. If the device is grounded properly then there isn't an issue either way. If your saying this was the result of an update then that's better then a hardware issue since it can be fixed much easier, once the company is made aware of the issue of course.
Click to expand...
Click to collapse
Yes a software issue can be fixed more easily...
IF the company decides to acknowledge the problem, act on the information and then go to the (likely considerable) expense of creating and releasing an update to address the problem. There have been many reports of this touch screen issue in the A51x & A7xx Iconias throughout the Internet especially, but not exclusively, if one is using a screen protector. Amazingly Acer claimed to address this in most recent OTA update for A700 (1.057), which was stated to address touch screen issues; it only made them worse on my A700. Go figure.
So I have the A700 and do not find any difference in touch sensitivity between the tablet laying down on a table and it being in my hands. Are you guys finding a big difference between the two?
Unfortunately it doesn't mean its perfect as I do struggle with touch sensitivity with the edges of the screen sometimes, which can be annoying as a lot off apps/browsers tend to put buttons in the corners.
Quick fix is to toggle the screen sensitivity everytime you boot up. (Change to medium then back high again, you do this every boot.)
A more permanent solution (applicable to the A510 only), is to flash NoThrills' optimized A510 rom along with the included NoThrills Kernel. This has solved my screen sensitivity issues.
salisbury_steak said:
Quick fix is to toggle the screen sensitivity everytime you boot up. (Change to medium then back high again, you do this every boot.)
A more permanent solution (applicable to the A510 only), is to flash NoThrills' optimized A510 rom along with the included NoThrills Kernel. This has solved my screen sensitivity issues.
Click to expand...
Click to collapse
Oh my God, you're so damn right! One of the first things I did when I got my tablet was putting the sensitivity to high, and I have never changed it since. Now that you mention, I put it to medium, then immediately high. Using the tablet on a flat surface is possible...my taps get registered flawlessly.
So, this means it is not something wrong with the display panel itself, but a software issue. Here's to hoping that Acer will fix it. Really weird man.
PS: Is there a code that I could tweak in the buil_prop maybe? I don't want to be flashing ROMs at the moment.
I was also wondering whether screen sensitivity could be addressed in build.prop. Anyone know?
himmatsj said:
Oh my God, you're so damn right! One of the first things I did when I got my tablet was putting the sensitivity to high, and I have never changed it since. Now that you mention, I put it to medium, then immediately high. Using the tablet on a flat surface is possible...my taps get registered flawlessly.
So, this means it is not something wrong with the display panel itself, but a software issue. Here's to hoping that Acer will fix it. Really weird man.
PS: Is there a code that I could tweak in the buil_prop maybe? I don't want to be flashing ROMs at the moment.
Click to expand...
Click to collapse
I currently do not know of any build.prop or init.d solution. (So I guess it's more complex than I thought it would be.)
As mentioned though, I don't have the sensitivity issues anymore since using NoThrill's Optimized A510 WW ROM (The kernel was the one that fixed it I think, since I flashed Acer's stock kernel and I got my sensitivity issues back.)
So you might wanna consider flashing a new rom, or, flashing a new kernel at least.
Hi guys,
I'm recently experiencing some random issues with the touch input. Sometimes, when I'm inking in sketchbook or SNote the tablet won't recognize my fingers anymore, only the pen, It's almost like the whole touch digitizer crashes. A reboot solves the problem...
Is anyone else having the same problem?
NIGos said:
Hi guys,
I'm recently experiencing some random issues with the touch input. Sometimes, when I'm inking in sketchbook or SNote the tablet won't recognize my fingers anymore, only the pen, It's almost like the whole touch digitizer crashes. A reboot solves the problem...
Is anyone else having the same problem?
Click to expand...
Click to collapse
I wish this were a feature and not a bug. Sketchbook doesnt like disabling the capacitive layer while youre using the pen. I'm actually having the opposite problem, it wont pick up palm rejection at all, so unless i enable the pen cursor, so i can see when the wacom digitizer is engaged and put my hand on the screen after, i get artifacts from palm to pen.... ugh....
Sent from my GT-N8013 using XDA Premium HD app
aletheus said:
I wish this were a feature and not a bug. Sketchbook doesnt like disabling the capacitive layer while youre using the pen. I'm actually having the opposite problem, it wont pick up palm rejection at all, so unless i enable the pen cursor, so i can see when the wacom digitizer is engaged and put my hand on the screen after, i get artifacts from palm to pen.... ugh....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
SBP doesn't have palm rejection. It's Autodesk's issue, not Samsung's.
Same problem, but opposite
I am getting the same problem in S-note but only a small patch tends to stop being detected by the s-pen. I am going to try a hard reset and see if it helps.I really hope it's not a hardware issue.
Turns out it was the magent on my case interfering the wacom digitizer. See if that my be the problem.
Hanzel9210 said:
I am getting the same problem in S-note but only a small patch tends to stop being detected by the s-pen. I am going to try a hard reset and see if it helps.I really hope it's not a hardware issue.
Turns out it was the magent on my case interfering the wacom digitizer. See if that my be the problem.
Click to expand...
Click to collapse
Funny, I had this issue too on my phone and it was due to the magnet on my case. Can this cause permanent damage? I kinda wanna keep using the case until a better one comes around and it only affects the wacom digitizer.
Hey all,
i have an Asus transformer, but i actually need help with my other tablet. I just bought an Insignia Flex 10.1 android tablet from Best buy. It seems to work great with my finger. However, when i use my stylus it doesnt detect it very well. When drawing or writing, it "skips" on the screen. Can someone help me with this? Maybe theres a certain stylus i need.
Thanks!
My GT2 does the same thing. It's because the screen sensitivity is significantly lower than on the Transformer. Changing stylus will probably not make any difference.
Oh that would suck. I was thinking of trying one of these:
http://www.amazon.com/Musemee-Notie...=1376404811&sr=8-4&keywords=fine+point+stylus
I noticed that when typing, (doesn't matter which keyboard) when I press the keyboard side keys, E.G. "P" or "L" they lag a tiny bit and when long-pressing, they take longer to recognize the keys.
Am I the only one noticing the glitch on the sides of the screen?
I've gotten two devices, and tested a demo model at Best buy and I found the same issue on all three.
It isn't that bad but I'd love to figure it out
Mine doesn't seem to have this problem even with a tg screen protector, i'll check at my local best buy to see if their demo model has the same problem whenever i have the chance.
hayame said:
Mine doesn't seem to have this problem even with a tg screen protector, i'll check at my local best buy to see if their demo model has the same problem whenever i have the chance.
Click to expand...
Click to collapse
Any luck?
capeorigins said:
Any luck?
Click to expand...
Click to collapse
didn't look like the display model had any problems either
hayame said:
didn't look like the display model had any problems either
Click to expand...
Click to collapse
I need to go check the displays near me then lol see if it's been fixed
I know this thread is old and dead but I noticed this too and personally I think it could be a bug/feature of Gboard, thinking like palm rejection on a laptop, it has that slight delay to reduce false inputs from your fingers touching the screen just holding the phone.
It might be worth it to try a different keyboard.
Using Hacker's Keyboards here. I noticed it with the A key. I have a theory that Moto Gestures is catching the signal first and then releasing after ms.