Is there a fix for the ghosting issue when scrolling through webpages?
tell the ghosts to buy their own tablet and leave you alone.
The Jack of Clubs said:
tell the ghosts to buy their own tablet and leave you alone.
Click to expand...
Click to collapse
Ah, i should have called my friend in the Ghostbusters.
Seriously, anyone else having this issue? Its not the worst thing in the world, just messes with my eyes as I scroll down webpages.
What do you mean - ghosting? I have an image persistancy (or whatever it called) issue - if the screen was on for a few minutes showing a static image, this image will remain on the background for some time. This is a hardware issue (some Ipads and Asus Transformers had it too), and there is no fix for it.
Unrealwolf said:
What do you mean - ghosting? I have an image persistancy (or whatever it called) issue - if the screen was on for a few minutes showing a static image, this image will remain on the background for some time. This is a hardware issue (some Ipads and Asus Transformers had it too), and there is no fix for it.
Click to expand...
Click to collapse
No, its not a static image issue, its as if the text leaves a trail when scrolling up and down a page.
androidmonkey said:
No, its not a static image issue, its as if the text leaves a trail when scrolling up and down a page.
Click to expand...
Click to collapse
Does it happen every time? Or only for some of the websites? If it is the latter case it might be the problem of compatiblity, try using other browser to see if it remains, for example opera or firefox.
Related
Can be very wonky at times. When the two points are directly beside or above/below each other on the x or y axis it seems to lose tracking of both points most of the time. Makes the pinch to zoom somewhat more difficult as you have to do it at an angle. Just wondering if everyone elses G tablet does this also.
Thanks!
Hmmm 52 views and no replies?
Nope, no issues here. Have you tried the touch recalibration app? Or reflashing? Do you only notice this in certain apps or is it everything?
Thanks for the response! Haven't tried reflashing but did do the calibration app a while and it helped somewhat. It does seem to be with every app. Think I will reflash and see if that alleviates it.
Thanks!
I don't believe the G-Tablet multitouch is as good as people say it is. My girlfriend had purchased Glow Hockey 2 on my tablet because she wanted to play air hockey against me, only to find that when two points on the screen are touched, the accuracy and responsiveness of the touches drop nearly 75%. It's a shame too, as that game looks to be a sure-fire hit with tablet devices.
I'm pretty sure that it is a hardware limitation, not a software limitation that can be fixed with re-flashing or calibration.
Enectic said:
Can be very wonky at times. When the two points are directly beside or above/below each other on the x or y axis it seems to lose tracking of both points most of the time. Makes the pinch to zoom somewhat more difficult as you have to do it at an angle. Just wondering if everyone elses G tablet does this also.
Thanks!
Click to expand...
Click to collapse
have you calibrated your screen ?
slsmag said:
have you calibrated your screen ?
Click to expand...
Click to collapse
Yup, responsiveness is great. Multitouch leaves a bit to be desired.
I can confirm this problem on my tab, with all rom's except the TnT ones (never tried them). Using multitouchvisualizer app from the market you can see that the screen will not register 2 points immediately when they have the same x (horizontal line) or the same y (vertical line). The problem is definitely better after calibrating the screen (doesnt take as long to register the second point), but the problem persists and leaves something to be desired for this multitouch screen. When pinch to zoom is at an angle to vertical or horizontal, its perfect. If pinching on the horizontal or vertical axis, there is lag.
Normally this doesn't matter because you can just pinch-to-zoom on an angle, but when playing games like cordy or jetcarstunts, where buttons are aligned horizontally, the second tap sometimes isn't recognized immediately. Its somewhat nit-picky, but there are many other touch screens where this is not a problem.
Make sure that you have the proper permissions files available. If you are missing the "Multitouch Distinct" XML file then it doesn't work properly...
Early ROMs didn't have it, so you had to add it manually...I think newer ROMs have it though...
I've attached it here JIC -- just remove the ".txt" extension and drop it in
TeutonicWolf said:
Make sure that you have the proper permissions files available. If you are missing the "Multitouch Distinct" XML file then it doesn't work properly...
Early ROMs didn't have it, so you had to add it manually...I think newer ROMs have it though...
I've attached it here JIC -- just remove the ".txt" extension and drop it in
Click to expand...
Click to collapse
"Drop it in" where? What folder?
Thanks
AndreCole said:
"Drop it in" where? What folder?
Thanks
Click to expand...
Click to collapse
Second that request!
Put it in /system/etc/permissions/ as android.hardware.touchscreen.multitouch.distinct.xml, and make it readable for all.
But, before you do, make sure that the file doesn't already exist. It does on CyanogenMod 7.0.3.
rajeevvp said:
Put it in /system/etc/permissions/ as android.hardware.touchscreen.multitouch.distinct.xml, and make it readable for all.
But, before you do, make sure that the file doesn't already exist. It does on CyanogenMod 7.0.3.
Click to expand...
Click to collapse
Yeah - went looking and found it. There are two files.
android.hardware.touchscreen.multitouch.distinct.xml
and
android.hardware.touchscreen.multitouch.xml
And a review as text file seems to show the same contents.
This post (12/2010) is unclear on what to do.
Thanks!
My Touchwiz update went fine on my stock unrooted tab. However, the new pan and tilt functionality doesn't work even though I've turned on all the settings and calibrated my tab.
Am I missing something or has anyone else experienced this?
this feature looks kind of.... stupid
For photos in the Gallery and web pages you need to put two fingers on the tablet initiate it's ability to zoom. They show holding it by the bottom corners then touching the screen with your thumbs. It works as show on mine. It can also be turned OFF in settings. Make sure its not OFF if you want to try it.
Ultimately it is a gimmick. Can't see even holding the tablet that way in normal use.
ericyyou said:
this feature looks kind of.... stupid
Click to expand...
Click to collapse
Agreed. For me, pinch to zoom works much better.
I like the ability to move an icon/widget from screen to screen while holding it down and turning tab left/right.
Much better for moving icons.
4dthinker said:
For photos in the Gallery and web pages you need to put two fingers on the tablet initiate it's ability to zoom. They show holding it by the bottom corners then touching the screen with your thumbs. It works as show on mine. It can also be turned OFF in settings. Make sure its not OFF if you want to try it.
Ultimately it is a gimmick. Can't see even holding the tablet that way in normal use.
Click to expand...
Click to collapse
Apparently I'm as stupid as the feature...didn't realize two fingers had to be on the screen. Doh.
walkamongus said:
Apparently I'm as stupid as the feature...didn't realize two fingers had to be on the screen. Doh.
Click to expand...
Click to collapse
Pwned. Lol it shows a demo of how to use it the first time you open the browser.
My Galaxy SII has burn-in on the notification bar. When I use *#0*# to check the screen, it is obvious that red and blue is burnt-in. Anyway to get rid of it?
real burn in?
are you sure it is a burn in? Do you see it in your browser on a white page?
I thought I spotted something similar but it was just OS bleeding through at some points in the interface. I believe I experienced it with miui.us or CM7.
I found this with a Google search. The question is, why didn't you
marrek said:
are you sure it is a burn in? Do you see it in your browser on a white page?
I thought I spotted something similar but it was just OS bleeding through at some points in the interface. I believe I experienced it with miui.us or CM7.
Click to expand...
Click to collapse
It is burn-in. When I browse using full screen, it becomes pale blue on the notification bar
MistahBungle said:
I found this with a Google search. The question is, why didn't you
Click to expand...
Click to collapse
I found it as well. But changing notification bar color is too hard for me. I followed some other suggestions on post (e.g. full screen browsing, screen brightness)
The problem is, the burn-in mark is still there, it does not get fix or reduced.
I just wanna see if new solution is found since the post is already a year ago.
mozclub said:
I found it as well. But changing notification bar color is too hard for me. I followed some other suggestions on post (e.g. full screen browsing, screen brightness)
The problem is, the burn-in mark is still there, it does not get fix or reduced.
I just wanna see if new solution is found since the post is already a year ago.
Click to expand...
Click to collapse
There is no solution, the pixels on notification bar faded because they were used more then the surrounding ones (which are now brighter). You can only minimize the risk of burn-in by lowering brightness. Its a downfall of AMOLED technology, no fix for that.
question and observationsstion part:
1. Has anyone noticed a white washed effect one their prime every so often? I am having this issue where reading something in black/white, the letters seems to be washed out and the white over powers the black text line definition so it becomes a white blurish effect.
1a. I have also noticed my led display has this "oil spill" under the glass somewhere in the upper middle area. A little minor grab of the prime on certain corners moves and reshapes this "oil spill". Does this have anything to do with #1?
Observation:
Not a super tech junkie but is there some sort of a memory leak in the ROM? I have noticed the reboot happens when the Asus task manager craps out and when ics+ browser is handling some open tabs with at least one tab with a video playing. I may be completely off here but that's just my observation. It seems the prime slows to a crawl with a few apps open and it speeds up when i close them but then it reboots when I reopen the same apps (mostly ics+ and maybe maps and translator and opera). I am going to stop using ics+ and use opera and see if it does this. I am also using dolphin so I'll be switching around however I am wonder if anyone has found a rhythm or rhyme to the rebooting issues.
Thanks!
Well the reboot thing isn't new,but you know there is a limit of available memory so if you're like me, opening closing apps like crazy and complaining about when one of them eventually crash you're just rising the pole. I use system panel to track how the device is doing and if in need of something to do to it.
I've had the wash out effect happen when you hold it on certain angles. I posted a thread about it not too long ago because I noticed my TF101 didnt do this. So I had asked some people who had them both to compare. The last post in the thread the poster noticed it as well.
http://forum.xda-developers.com/showthread.php?t=1669860
I'm having some screen issues with Firefox. Sometimes the bottom of the screen goes black and the tabs at the top disappear. By using split screen mode I can repair this but it does seem to come back regularly. Strangely enough I can replicate this behavior by using the volume down button (wtf?) when a video is playing on a website. It seems some kind of screen resolution thing, in Firefox it's reported as 1195x747x24 but in Chrome I see 1205x753x24.
Is anyone else having these screen issues with Firefox, and am I right in thinking that it is Firefox that somehow gets the resolution wrong and that that's the cause? Why its also related to the volume button is beyond me.
ASW1 said:
I'm having some screen issues with Firefox. Sometimes the bottom of the screen goes black and the tabs at the top disappear. By using split screen mode I can repair this but it does seem to come back regularly. Strangely enough I can replicate this behavior by using the volume down button (wtf?) when a video is playing on a website. It seems some kind of screen resolution thing, in Firefox it's reported as 1195x747x24 but in Chrome I see 1205x753x24.
Is anyone else having these screen issues with Firefox, and am I right in thinking that it is Firefox that somehow gets the resolution wrong and that that's the cause? Why its also related to the volume button is beyond me.
Click to expand...
Click to collapse
I don't know the answer, sorry, but curious if you've tried the jelly (for lineage) browser? You can find the apk by searching xda if you didn't know.
I ask about that because jelly is using the system html rendering, so it may work and be very minimalist. Aside from that, and hope u don't mind my asking, why not use apps when available? I'd expect the app for netflix etc to be able to function no issues. If not, there should be support from them. But ff not playing a video properly? not sure there's much support available for that?
Have you automatic screen resolution adjustment checked or free form mode activated (as indicated by me in that thread) via adb?
(When free form was activated I realized similar behavior in free form apps)
I found out that Firefox beta doesn't have this issue, so I presume whatever it is it'll be fixed in the next release of Firefox.
Screen issue is fixed now with the update., Firefox working the way it should now.
I presume other screen issues with video playing like people have reported with vlc will also be fixed.