[Q] Do build.prop tweaks really work? - AT&T Samsung Galaxy S II SGH-I777

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