I've searched long and at any places, but nowhere was an answer. Everybody goes crazy if we talk about sensitivity, but what are the benefits of a higher sensitivity really?
I mean, here on mother earth, you can't get something better, without decreasing other features...
So if i turn the sensitivity higher (or lower), i mean if its more precise... Where are the disadvantages?
Higher battery drain?
Please help me to understand
I you slide you finger over the screen it takes a small distance before the phone reactes and moves the part of the display. Try it and you will notice this small distance on the homescreen. It is like a dead zone where you move your finger but nothing happens.
With the toch sensitivity fixes or apps or scripts you can decrease this distance to 0 or any other value. I think a value around 5 is quite common. I am not sure but I thought 15 is default, so you usually want to decrease it.
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Schindler33 said:
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Click to expand...
Click to collapse
That was the answer i wanted! Thank you!
On some older kernels, when your phone is on ac power, the screen becomes very unresponsive. That's why people came up with the need to change the touch sensitivity.
Sent from my GT-I9100 using Tapatalk
Related
Is there any way to increase the backlight further, because screen is not bright enough even when set to max. Maybe some registry hacks?..
I think this is possible, because if you guys had noticed, that when you start the 'Camera' app, the brightness increases a bit even when it was already set to max.
Even my previous Nokia 3100's screen is brighter (shame), so any suggestions would be appreciated. Thnx in advance..
Well, can't anyone help me?? (Even the experts??)
It's probably not possible to make it brighter. I think what you see with the camera is an illusion because it changes the LCD contrast/bright level, not the backlight level. It's not logical to think that the backlight is purposely limited to be less bright than it truly is.
That may be why there are no responses.
Well actually there's a response, since you're using the WM2003-SE it will decrease the brightness as I noticed from several flashing and I'm very aware of that and sensitive about this case. Further more, from couple minutes when I downgraded from 1.72.00 to version 1.66.00 WWE, it decreased as well, so if you flash back to 1.72.00 you'll notice the screen is much brighter than the WM2003 SE and the 1.66.00, I want to add something else. HTC released two type of Himalaya which is different in the Screen type and the flat cable socket. New releases are brighter than the predecessors.
a quick reply, adjusting brightness will also decreases the battery.
a big big diff.
Ok i wanted to start new thread with this issue
got a question about the screen. Some times I can sense and see that despite of auto brightness off that the screen adjusts its brightness by itself. It is a little change but my sharp eyes can see this... Do you have a similar thing?
I can easly notice this when playing my country game. When I click on the building menu the screen gets brighter. When i cancel the menu the screen makes darker
Also in sprinkle when I use water the screen gets little brighter
I think this is because the Tegra 3 (or ASUS's implementation of it) adjusts contrast to conserve power. The changes in contrast make brightness seem to change.
I think their settings are too aggressive and they should either scale them back or add an option to turn it off, if possible. I'm sure it's nice for battery life but it does (in some very specific instances) seem to impact the experience.
Note: this is not a doom-and-gloom post. The Prime's screen performance is the best I've ever experienced on a mobile device, maybe any device, overall. So this is a bit of a nuisance but nowhere near enough for me to have an inkling of regret about buying the Prime.
This only happens on mine while in power saving mode.
TF201 / XDA premium
wynand32 said:
I think this is because the Tegra 3 (or ASUS's implementation of it) adjusts contrast to conserve power. The changes in contrast make brightness seem to change.
I think their settings are too aggressive and they should either scale them back or add an option to turn it off, if possible. I'm sure it's nice for battery life but it does (in some very specific instances) seem to impact the experience.
Note: this is not a doom-and-gloom post. The Prime's screen performance is the best I've ever experienced on a mobile device, maybe any device, overall. So this is a bit of a nuisance but nowhere near enough for me to have an inkling of regret about buying the Prime.
Click to expand...
Click to collapse
Do you experince the same issue as me?
tdrussell said:
This only happens on mine while in power saving mode.
TF201 / XDA premium
Click to expand...
Click to collapse
I'm not sure, I'll have to do some more testing. I seem to remember it happening across the board.
I'll note that Battery mode really does make a HUGE difference in the screen's performance. Colors become very washed out, so much so that I'm really surprised by the impact.
Well in my case this thing occurs on every mode with the same strenght... That sucks
so anyone of you can confirm if this is normal? Do you have the same isue on your primes?
It seems the light sensor has high resolution and Asus needs to smooth up a bit the auto-brightness algorithms If your screen goes up and down then simply disable auto-brightness or change lightning conditions
ankhazam said:
It seems the light sensor has high resolution and Asus needs to smooth up a bit the auto-brightness algorithms If your screen goes up and down then simply disable auto-brightness or change lightning conditions
Click to expand...
Click to collapse
Like i said auto brightness is off. Can anyone install my country and check his out for me? Just enter build menu and chec if the screen gets a little brighter
it has nothing to do with auto-brightness... Its a feature of tegra 3, it can change the brightness of each pixel to give you the best image and use the least amount of power.. unfortunately its just annoying and not implemented well.
And you cannot turn it off.
Ya I noticed this too last night and thought that I had a defective screen. Made a thread about it earlier. http://forum.xda-developers.com/showthread.php?t=1421002
jzen said:
it has nothing to do with auto-brightness... Its a feature of tegra 3, it can change the brightness of each pixel to give you the best image and use the least amount of power.. unfortunately its just annoying and not implemented well.
And you cannot turn it off.
Click to expand...
Click to collapse
I should b off in perormnce mode. I understand this feature in saving power mode but not on others two. I hope it will be changed
Hello,
theres a bug in automatic brightness: if you turn it on and hold it against the sun the brightness will go to maximum but it won't get back (darker).
ImmanuelCunt said:
Hello,
theres a bug in automatic brightness: if you turn it on and hold it against the sun the brightness will go to maximum but it won't get back (darker).
Click to expand...
Click to collapse
I can't help myself, 3 thanks virgins in 2 days!!!! Owned!!!! last time I held something up to the sun it melted. Its kinda hot!!!!........
Ok in all seriousness I have not had this issue....did you try rebooting your prime? I have noticed some hicups from time to time, like touch tones stop working....but if I reboot it will work again. I am sure its just the newness of ICS, these things will get ironed out in time.
I leave it off anyways. Its a known automatic brightness is a battery drainer. You'll get better battery life with it off.
slayer69 said:
I can't help myself, 3 thanks virgins in 2 days!!!! Owned!!!! last time I held something up to the sun it melted. Its kinda hot!!!!........
Ok in all seriousness I have not had this issue....did you try rebooting your prime? I have noticed some hicups from time to time, like touch tones stop working....but if I reboot it will work again. I am sure its just the newness of ICS, these things will get ironed out in time.
Click to expand...
Click to collapse
I wish you took my thanks virginity LOL but yeah i've not come across this issue but who holds their tablet up at the sun... lol
ImmanuelCunt said:
Hello,
theres a bug in automatic brightness: if you turn it on and hold it against the sun the brightness will go to maximum but it won't get back (darker).
Click to expand...
Click to collapse
I think this is more of a feature than a bug, although I keep mine at one certain level anyway.
It's to give you a more seamless experience, as soon as the screen goes off and back on it adjusts. It's so when you're reading an article and move from one area to another, you don't get a surprise mid-sentence. I always hated reading things off my phone with auto brightness on, couldn't just focus on the words had to keep tripping up on a constantly changing screen.
With sun i meant that you can hold it against a bright light
Sry for my bad english...
I've actually noticed some differences in the sensitivity of the light sensor on various units. Some do seem to get "stuck," where others maintain an accurate measurement of ambient light. This seems to be correlated to newer units (e.g., C1 units).
The one I'm using right now does switch lighting both more quickly and, it would seem, more accurately. The ones I had previously would get stuck either on high or low brightness (with very little adjustment in between), and I needed to toggle the auto brightness button to get them to adjust to new conditions.
I found auto brightness on the device to be an annoying burden if anything. I just keep it pretty low all the time. Better that way anyways.
Same problem here - The brightness goes up under bright light, and won't readjust until the next screen off/on or reboot.
Does anyone have a Prime that adjusts back down without turning the screen off?
I swear it's intentional and not a bug, although they should offer you the option of controlling its parameters. Just have to wait for the unlocker and some custom ROMage.
But seriously, I think it's to keep a continuity in your current session, so that if you're gaming or working (the two things this tablet's for) you're not plagued by an ever-changing screen that distracts you...
buxtahuda said:
Does anyone have a Prime that adjusts back down without turning the screen off?
I swear it's intentional and not a bug, although they should offer you the option of controlling its parameters. Just have to wait for the unlocker and some custom ROMage.
But seriously, I think it's to keep a continuity in your current session, so that if you're gaming or working (the two things this tablet's for) you're not plagued by an ever-changing screen that distracts you...
Click to expand...
Click to collapse
I can see how the concept of continuity can be good. But in my case for example, switching the bedroom light on - followed by a certain increase of brightness on ATP - then switch the bedroom light off to go to bed - the persistent brightness (tested for >15mins) can be a little straining on the eyes. Although readjusting the brightness is as simple as 'clicking' the 'auto' icon on/off again so that the brightness comes down to appropriate level (it only takes 2seconds to do it) - I think this is defeating the purpose of having the auto-brightness setting in the first place.
maxfac1234 said:
I can see how the concept of continuity can be good. But in my case for example, switching the bedroom light on - followed by a certain increase of brightness on ATP - then switch the bedroom light off to go to bed - the persistent brightness (tested for >15mins) can be a little straining on the eyes. Although readjusting the brightness is as simple as 'clicking' the 'auto' icon on/off again so that the brightness comes down to appropriate level (it only takes 2seconds to do it) - I think this is defeating the purpose of having the auto-brightness setting in the first place.
Click to expand...
Click to collapse
Oh I whole-heartedly agree. Going from my living room anywhere else in the house causes blindness with auto brightness on. And it acts completely opposite on this device than all others I've touched that use the feature. And like you say, if it's "automatic brightness" then why would it not be totally automated?
I'm just saying there's definite reasoning and programming behind it, it's not just some bug per se.
Therefore, don't expect ASUS to do anything about it, it'll all be up to our wonderful dev's here; they'll say it's properly functioning even though it's bass ackwards from everything else in existence.
Is there something that I am missing?
I included a very common build.prop script (windowsmgr.max_events_per_sec=x) and set x to the "recommended" 150. Then I tried setting it to 1 and rebooted. I didn't notice a difference between the two.
Am I misunderstanding something here? or is this build.prop script just baloney?
It works, try setting it to 500 and then back to 150. You should notice better touch responsiveness.
ryude said:
It works, try setting it to 500 and then back to 150. You should notice better touch responsiveness.
Click to expand...
Click to collapse
Hey thanks for the response, but I still don't see anything. I set it to 50000 and it still feels the same....
I have noticed a difference, but its pretty minor. I set mine to 300 and it feels a tad smoother.
Interesting. I want to say that I'm doing something wrong with the build.prop, but at least one modification (no boot animation) definitely works.
Some work well, some are questionable, some are useless.
That windowsmanager tweak is likely not useful for many people as the original value is just fine for most people. Only the exceptionally picky will notice a difference.
In the photography world, we call such pickiness "pixel peeping".
Entropy512 said:
Some work well, some are questionable, some are useless.
That windowsmanager tweak is likely not useful for many people as the original value is just fine for most people. Only the exceptionally picky will notice a difference.
In the photography world, we call such pickiness "pixel peeping".
Click to expand...
Click to collapse
Thanks man.
But how do you then explain that setting the value to 1 feels exactly the same as when on 100 or 200?
I would assume that everything should run noticeably slower? I understand what you're saying, I'm just having a hard time believing that its even a tweak at all.
Sent from my GT-I9100 using XDA App
patsmike said:
Thanks man.
But how do you then explain that setting the value to 1 feels exactly the same as when on 100 or 200?
I would assume that everything should run noticeably slower? I understand what you're saying, I'm just having a hard time believing that its even a tweak at all.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Because at some point, you reach either a cap due to something else bottlenecking (such as the screen refresh rate), or a cap on your ability to perceive any difference.
Entropy512 said:
Because at some point, you reach either a cap due to something else bottlenecking (such as the screen refresh rate), or a cap on your ability to perceive any difference.
Click to expand...
Click to collapse
Sorry I worded my question poorly. I meant to ask why doesnt the ui feel noticeably slower at the lowest possible value of 1.
I understand why we wouldnt notice any difference increasing the value, but what about the other way around?
Sent from my GT-I9100 using XDA App
patsmike said:
Sorry I worded my question poorly. I meant to ask why doesnt the ui feel noticeably slower at the lowest possible value of 1.
I understand why we wouldnt notice any difference increasing the value, but what about the other way around?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Because you're looking for the performance to change, which it doesn't do. It only changes how many times it checks for new touch input, which improves how responsive it is to your touches. Past a certain point, it ceases to improve to a degree that the human eye can see.
Dont for get
Sent from my GT-S5570 using XDA
ryude said:
Because you're looking for the performance to change, which it doesn't do. It only changes how many times it checks for new touch input, which improves how responsive it is to your touches. Past a certain point, it ceases to improve to a degree that the human eye can see.
Click to expand...
Click to collapse
Sorry, yes I meant touch responsiveness when I wrote UI response.
And again, I understand that if you set it to a very high value, you won't notice a difference. I am asking about what happens when you set it to a very LOW value (so that I can check if the build.prop tweak really changes anything).
So hear me out: I found an easy little test for touch responsiveness - if you use the LA4 circle lock screen and press on the screen, everything turns dark when the circle pops up. So if you tap quickly, you can see exactly how fast it registers your presses because the screen starts flashing from dark to your background and so on. So I set windowsmgr.max_events_per_sec=1 and then reboot.
Then if you try and tap on the lock screen very fast, you can still see the screen flashing at much faster rate than 1 time/sec. It is actually perfectly accurate and doesn't miss any of my taps. Therefore, it is not checking for touch input every second, but still at a very fast rate where the difference is unnoticeable.
Try it - its very easy and proves that this build.prop change doesn't change anything - all placebo (unless I am implementing something wrong).
Sent from my GT-I9100 using XDA App
Hi,
Has anyone experienced an abnormal temperature in the nav keys area? It is present in any moment that the screen it is turn on, even on recovery with twrp or with different roms, increasing with time. It is safe continue using it?
A little background first: a couple of months ago I had the screen replaced, from nowhere the old screen started to blink and went black with a burned smell. Before this happening never noticed this issue before.
Appreciate your help!
There are not many chips in there. It's probably something with USB power management. Is your USB port working? I mean both client and host functionality?
Mr.Adalbert said:
There are not many chips in there. It's probably something with USB power management. Is your USB port working? I mean both client and host functionality?
Click to expand...
Click to collapse
My USB is working normal I can acess my files and charge the device too. But I don't know what you mean about the functionality part
I mean chip providing 5V for OTG. If it works as well problem could be caused by battery, but I think that heat wouldn't be concentrated in lower part of the device
Hi g4m4r1,
I have this hot area in the middle of navy keys (home button) bottom on the screen. But my device only warm when I am playing games or when I use the screen brightness over 70%.
So, in indoor usage my screen brightness is around 30% and this area is just little warm.
Other important point is the ambience temperature, in my country is summer right now, so my device get this hot area very fast when I start up some game or increase the screen brightness.
Fabio Bertelli said:
Hi g4m4r1,
I have this hot area in the middle of navy keys (home button) bottom on the screen. But my device only warm when I am playing games or when I use the screen brightness over 70%.
So, in indoor usage my screen brightness is around 30% and this area is just little warm.
Other important point is the ambience temperature, in my country is summer right now, so my device get this hot area very fast when I start up some game or increase the screen brightness.
Click to expand...
Click to collapse
Hi Fabio, thank you for your contribution, I did some testing and seems that brightness has a role in heating the nav keys area, by the way mine, it is not concentrated only at home button, but well distributed on the others buttons too.
At low brightness, just enough to see what it is on the screen, the heating rate is lower and increases, but at high brightness it is almost unbearable to the touch. About the weather part, that doesn´t seem to affect the area. But still I don't know if is prudent to me continue use the device.