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

Root Debugging the Touch Screen on the Ultra

bads3ctor

bads3ctor

Well-Known Member
Change /system/build.prop:
ro.build.version.sdk=10

to:
ro.build.version.sdk=15

Copy this Development - Minus
to: /system/app

Go to Pointer Location and touch for a while and you will see the Ultra touchscreen bug.

I have seen this bug someplace before.....it's the right side unresponsive bug.

Edit: It's a whole digitizer sensitivity problem....not just the right side.

Might be a bad digitizer....I can't believe all the Ultra phones have the same problem.....

Edit: I went to Radio Shack for a replacement....manager essentially told me to go F myself.

Thanks to penguinrepair for help with the build.prop change.
 
bro this is my one and only problem with this phone...at times it becomes a real pain...i noticed that using a screen cover makes it worse..and not cleaning the junk off of the screen..thanks for the info
 
DMajor239 said:
So does this help fix the screen issue?
Click to expand...

I think it's a sensitivity issue but the melfas touchscreen config file is in firmware in the kernel so fixing will be difficult to impossible.

In ICS Intercept I fixed TS by hacking /system/usr/idc/melfas_ts_input.idc

# Pressure
# Driver reports signal strength as pressure.
#
# A normal thumb touch typically registers about 100 signal strength
# units although we don't expect these values to be accurate.
touch.pressure.calibration = amplitude
touch.pressure.source = pressure
touch.pressure.scale = 0.025

We can't do that in CM7 so I will look for another fix.
 
The Gtab 10.1 had similar but no where near as noticeable or drastic as the TU..Touch Screen Tune fixed the issue for the Gtab..so i gmailed the developer and let him know of our ts problem..hoping he would look into it..he basically told me that in order to fix it you needed to have access to something in the phone..that was pretty much impossible to change/access...i cant remember exactly what he said it was because it was like two months ago
 
i couldnt give you an honest answer Loota..ill shoot the dude Vital another email...ill post back when i get his reply
 
http://vegantab.gojimi.com/download/TouchRecalibrate.apk

Do a recalibrate and see if it fixes TS

I did and it seems better but it might be my imagination :rolleyes:

Edit: well, I think I was hallucinating....doesn't seem better :(

Here is the logcat when the TS starts to fail:

20:07:15.133 Info Pointer 1174 Pointer 1: (177.0, 357.0) Pressure=0.133 Size=0.0 TouchMajor=0.0 TouchMinor=0.0 ToolMajor=0.0 ToolMinor=0.0 Orientation=0.0deg
20:07:15.154 Info Pointer 1174 Pointer 1: (177.0, 354.0) Pressure=0.141 Size=0.0 TouchMajor=0.0 TouchMinor=0.0 ToolMajor=0.0 ToolMinor=0.0 Orientation=0.0deg
20:07:15.154 Info Pointer 1174 Pointer 1: (177.0, 351.0) Pressure=0.149 Size=0.0 TouchMajor=0.0 TouchMinor=0.0 ToolMajor=0.0 ToolMinor=0.0 Orientation=0.0deg

Failure starts here:

20:07:15.176 Info InputReader 167 dispatchTouch::touch event's action is 1
20:07:15.176 Info InputDispatcher 167 Delivering touch to current input target: action: 1, channel '4079a630 com.android.development/com.android.development.PointerLocation (server)'
20:07:15.176 Info Pointer 1174 Pointer 1: (177.0, 351.0) Pressure=0.149 Size=0.0 TouchMajor=0.0 TouchMinor=0.0 ToolMajor=0.0 ToolMinor=0.0 Orientation=0.0deg
20:07:15.176 Info Pointer 1174 Pointer 1: UP
20:07:15.212 Info InputReader 167 dispatchTouch::touch event's action is 0
20:07:15.212 Info InputDispatcher 167 Delivering touch to current input target: action: 0, channel '4079a630 com.android.development/com.android.development.PointerLocation (server)'
20:07:15.212 Info Pointer 1174 Pointer 1: DOWN
20:07:15.212 Info Pointer 1174 Pointer 1: (181.0, 308.0) Pressure=0.118 Size=0.0 TouchMajor=0.0 TouchMinor=0.0 ToolMajor=0.0 ToolMinor=0.0 Orientation=0.0deg
20:07:15.255 Info InputReader 167 dispatchTouch::touch event's action is 1
20:07:15.255 Info InputDispatcher 167 Delivering touch to current input target: action: 1, channel '4079a630 com.android.development/com.android.development.PointerLocation (server)'
20:07:15.255 Info Pointer 1174 Pointer 1: (181.0, 308.0) Pressure=0.118 Size=0.0 TouchMajor=0.0 TouchMinor=0.0 ToolMajor=0.0 ToolMinor=0.0 Orientation=0.0deg

Edit: Tried adding /system/usr/idc/melfas_ts_input.idc from my ICS build.....it is ignored on bootup.
 
i defenantly dont want to say your are wrong about it being a sensitivity issue (you are well knolledged :D ), but i do not think it has anything to do with sensitivity at all... firmware would be my best guess... there is a script a-miss... IMO

IMFM did a great job explaining/showing what the exact problem is... it is duplicatable for every one... http://www.youtube.com/watch?v=Jz8dvPB3ZEo&feature=player_embedded

the app utility he used is "TouchUtil" found here... https://play.google.com/store/apps/details?id=Pixelated.TouchUtil&feature=search_result#?t=W251bGwsMSwyLDEsIlBpeGVsYXRlZC5Ub3VjaFV0aWwiXQ


now when you use two touch-points (two fingers) there is no problem... so the hardware works like it should (i would think)

and in every sence and situation the "sensitivity" seems/feels great with no prob... i dont have to press hard on the screen or light at that matter.

this is only my opinion :rolleyes:
 
well...i would much rather it be a firmware deal then hardware...more likely to get a fix/update to take care of the situation....never knew about the two finger thing..have to give that a try..thanks
 
johnny424 said:
more likely to get a fix/update to take care of the situation....
Click to expand...
the fix will have to come from us users... samsung is not taking any responsibilty for it and claim you are the first to ever report any problem close to what you're discribing... i highly dought they will give a fix or update... but we all can hope, right?!?
 
smith058 said:
the fix will have to come from us users... samsung is not taking any responsibilty for it and claim you are the first to ever report any problem close to what you're discribing... i highly dought they will give a fix or update... but we all can hope, right?!?
Click to expand...

lol agreed.

i deffinetly think it will be a user first..
 
Johnny

Hi,

I downloaded kernel sources for this device - and bad news are that it is using Melfas touchscreen controller which is worse than the one used on top Samsung devices, and cannot be configured. So no, support for this phone is not possible unfortunately.

BR, Vitalijus ▶ Show quoted text

Hi,

forwarding the email regarding transform ultra.

BR, Vitalijus ▶ Show quoted text
 
The Galaxy Nexus uses the same brand controller (note: it may not be the same series as the only reference is Melfas MMSxxx).

anyway, there is a page that has all the kernel stuff for the gal nex, check this out

specifically the file names mms_ts.c

repo1.pst.beuth-hochschule.de/repo/android/nexus/Galaxy-Nexus-Project-android_omap_tuna-38720e1/drivers/input/touchscreen/

would it be possible to download the stock 2.3 source from Google, and then copy over all the proprietary stuff and kernel drivers from here?
 
AndyDroidBot said:
The Galaxy Nexus uses the same brand controller (note: it may not be the same series as the only reference is Melfas MMSxxx).

anyway, there is a page that has all the kernel stuff for the gal nex, check this out

specifically the file names mms_ts.c

repo1.pst.beuth-hochschule.de/repo/android/nexus/Galaxy-Nexus-Project-android_omap_tuna-38720e1/drivers/input/touchscreen/

would it be possible to download the stock 2.3 source from Google, and then copy over all the proprietary stuff and kernel drivers from here?
Click to expand...

This is just a guess but I don't think that would work because the firmware would be pointing to the drivers that are installed on it currently and not the new drivers you copy over. Prolly would have to edit the firmware
 
What I meant was compiling a new rom in this fashion:
[Android 2.3xx source from google's developer website] + [drivers found on the site I provided] = [stock 2.3 rom with no CIQ and fixed touch screen]
 
I think this bug is only fixable by Samsung and if they refuse to acknowledge it then I am thinking of returning it to radio shack and saying ....fk Samsung :eek:

I have not decided if I want to fix a bug that a corporation refuses to fix or tell Samsung to kiss my a$$ :rolleyes:
 
bads3ctor said:
I think this bug is only fixable by Samsung and if they refuse to acknowledge it then I am thinking of returning it to radio shack and saying ....fk Samsung :eek:

I have not decided if I want to fix a bug that a corporation refuses to fix or tell Samsung to kiss my a$$ :rolleyes:
Click to expand...
do both:);)... BUT PLEASE fix this problem for all of us that got suckered into buying a broken product at high retail price.... we love uor phones and just need it fixed (and odin too) and we all would be soooo happy with a spectacular phone... PLEASE DONT GIVE UP ON US... Jew Ken Do It!!!!

Loota said:
I'll call tomorrow and see if I can get someone from engineering on the line. I'm a medical field engineer in the real world so I know if I can get the ear of someone that actually works on the damn things then I can get the ball rolling.
Click to expand...
PLEASE DO :):):):):)

DMajor239 said:
We should start some petition as well.
Click to expand...
we already do... in a way.... would be nice if we can go forward with it
http://androidforums.com/samsung-transform-ultra/495990-class-action-lawsuit.html

.

.
 
smith058 said:
now when you use two touch-points (two fingers) there is no problem... so the hardware works like it should (i would think)

and in every sence and situation the "sensitivity" seems/feels great with no prob... i dont have to press hard on the screen or light at that matter.

this is only my opinion :rolleyes:
Click to expand...

Two fingers seemed to fix it until I tried this:
Using Multi-Touch Benchmark, lightly touch with 2 or even 3 finger tips and the problem is still there. I can only get it to work normally when I past some pressure/surface area threshold regardless if I do it with 1, 2, or more fingers.

Well hell I just tried it again and 2 & 3 finger method with normal pressure and it isn't even being reliable. Seems very flakey, maybe I need to charge my fingers.
 
Samsung Galaxy S2 touchscreen problem (move threshold) - YouTube



SGS screen problems


Screen issue solve for sgs2


Has anyone looked at this app yet? it doesnt work for the ultra because i already tried but the samsung galaxy s 2 have the same problem with the screen just like the ultra. Now this app was create to fix it by setting the dial to 0 pressing apply and then press enable server. If you hit the menu button while your in the app it brings up to me whats like an entire list of stuff thats has to do with the screen and you can change any of them. It says it requires root of course but still doesnt nothing. Anyway the list of stuff that has to do with the screen, it could be one of them malfunctioning or not. On the samsung galaxy s 2 the file that was change to correct the screen problem was the HYST file. It could be possible that its the same file thats messing up the screen on the ultra.

Lol lets face it, we now know for a fact that samsung isnt pushing out an update to fix our "prepaid" "boost mobile" phone if their not even gonna fix a high end smart phone on a good carrier. Its ashame that developers had to fix it themselves smh.





Edit

theres another way to fix it too by editing the kernel
shot_000001.jpg

Kernels that were used to fix the issue
 
You must log in or register to reply here.
Back
Top Bottom