• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Screen Fix Finally :)

I had to add max events because it wasn't in my build.prop.

My density was set at 160 originally before even changing anything.

I need to use all 5 fingers and try hard to break 200 touch events per second.

Thanks for the tips, it might be working a little better but it still randomly messes up, maybe just not as often.
 
For me... it helps a lot but not a complete fix. Good job finding the tweek.

I can still replicate the problem but its definently better, at least 60% improvement!

Thanks

Ps. Still need to look further into this
 
Loota said:
I'm running shevron 5.1 rooted of course.. I'm using the lite version of romtoolbox and changing the settings to exactly the numbers you prescribe and not noticing any difference.. I'm going to open buildprop on my comp and see if changes are being applied.

Edit: changes are definitely applied... since screen density is 160 by default Im going to leave it there and drop max events some more see if I can get a positive result..
Click to expand...

I would suggest changing the density to 157 and the max events to 241 and let me know how it works, I mainly use my thumb and have no problem, when I use my index or diff finger sometimes it will drop apps but never like it did before
 
scerini said:
I would suggest changing the density to 157 and the max events to 241 and let me know how it works, I mainly use my thumb and have no problem, when I use my index or diff finger sometimes it will drop apps but never like it did before
Click to expand...

Yeah that's exactly the numbers I've used. Using a large surface area I do not drop even on touchutil but with my index finger I see no noticeable change.. not knocking it of course just providing feedback. Also I should note that with settings back to stock 160 density and 300 max events. It does not register up downs with the flat of my thumb either... I cannot comment if this is different from before changing the buildprop since I did not test but that could be pertinent because if rom toolbox formats the buildprop and improves it even with default settings it could be good to know..
 
Just my 2 cents worth here. I used the same build.prop as stock GB in one of my CM7 tests on the Boost TU and CM7's touchscreen acts fine. No bug. This would seem to suggest that the problem is elsewhere. For now, this is just an educated guess.
 
Like Dmajor239 I didn't have the max events but I went a head and changed LCD density to 157 via root explorer and is working better.
 
So do I need to be stock in order to get the screen fix? I tried it with Shevron 5.1 and didn't seem to make a difference.
 
cjoeone said:
So do I need to be stock in order to get the screen fix? I tried it with Shevron 5.1 and didn't seem to make a difference.
Click to expand...

no i run stock, and while the change seemed to help some..its very obvious the problem is still there..what was strange is after i made the change to those exact numbers i could drag and drop easier then before..but a day later it seems like it always has..maybe placebo?
 
This helps, but, the problem is still there... Thanks anyways. Now I don't have to kill myself trying to drag and drop onto somewhere else
 
I tried these changes however I decided I wanted to go back to the original settings that were being used which was 160 LCD density and I'm pretty sure max events was set to 300 but I can only go up to 281 in max events is there something I'm missing here?
 
Hey scerini could you edit your post with a warning that people may need to switch back to make google playstore notice their phones as compatible again? Not that its causing unfixable problems but just so that peeps know from the git go what they need to do..
 
Ill be sure to do that, I haven't had any problems with anything like that. Didn't know about it either thanks for finding that out. I've been super busy lately work 7 days a week 8-5 and the girl I was going to marry just left me for her ex so I just got a lot of free time back going to help out on CM7 as much as possible, was actually thinking about getting rid of my Ultra but I don't want to let it go cheap anyone interested?
 
I'm just lucky it didn't get that far, sorry to hear that though man it must be terrible, just know your not the only one is it me or has anyone else noticed that like everyone is breaking up or cheating here lately?
 
Yeah bro its all good... for the best really... if you're looking for something to get your mind off things... I'm sure a lot of us would love to see a super battery saver rom based on your results in the battery thread ;-)
 
Great. My app store doesn't recognize me correctly anymore. Even when I put it back to 160 and 300. Anyone have a build.prop file that works?

Good find though. I find it works best with your thumb rather than your finger.
 
You must log in or register to reply here.
Back
Top Bottom