Highlighted
philverb
1 Copper

Two issues -screen calibration. Can't click Fastboot for 2nd fastboot screen; cannot get persistent settings for 'InterruptMethod' as named by Engineering tools application.

 

"How do I make a permanent change to my Streak's touchscreen's 'Interrupt Method' setting?" 

US Beta device: Can't get into proper fastboot mode -second fastboot screen, and screen calibration is messed up unless I use the EMlist utility to temporarily change the "Interrup Method".

I wrote the following in another thread, where I was also emphasizing a touchscreen calibration problem that plagues me during normal use of the OS.

Question #1: Does anyone know a workaround for this "un-clickable" Fastboot screen area that must be clicked on to get into fastboot mode and flash a new ROM?

Question #2: Does Anyone know what settings will allow me to keep the screen configuration set to "SensePeriodical"?




##########
*Issue #1*
##########
The main point for posting this as a new topic is summed up by the sentence: "The area of the screen with an unbounded word "FastBoot" has not been clickable at all."



After booting while holding down the UP/DOWN volume buttons, I get the following.


I see only:
1. (Top Left) "Touch Calibration"
2. (Top Right) "FastBoot"
3. (Bottom Left) "Press:"
4. (Bottom Right) --Phone keypad with numeric buttons and the two labels "CLS" and "Enter" on their own buttons.

The area of the screen with an unbounded word "FastBoot" has not been clickable at all.

The first time I tried to boot into fastboot this way, these things appeared and then I attempted to use the numeric keypad --and each attempt failed, printing the wrong character. When I pressed "1", then for example, the number "6" would appear.

I then pressed the top volume button and the screen went dark. After ~3 seconds, the screen was repopulated identically, *except* for the word "FAIL" beneath the "Touch Calibration" on the top left.

I then retried without rebooting. This time, all my keypresses were accurate. I pressed the top volume button again, and the screen went dark again. The same display reappeared, along with the word "FAIL" in red beneath "Touch Calibration".

I then rebooted into fastboot again --but this time, all of my key-presses were accurate the first time. I filled up the 10 characters of space after the "Press" item on the bottom left by pressing the number pad buttons in sequence. I then pressed the top volume button, but then got the red "FAIL" when the screen came back on.

This phone was rooted (at least) once, then updated to 2.1, then (I believe) flashed with a 1.6 image. After the first aforementioned update, wiped with a factory reset.


##########
*Issue #2
##########
Touch screen mis-calibration problems were reported/observed after the first manual ROM flash. That has still been a problem for me since acquiring the Streak, and the only workaround I have yet found is a temporary adjustment using one of the engineering tools beneath the Eng. menu item "EMlist". This workaround is only functional until the screen goes to sleep, and then I get the same behavior from the touchscreen that forces me to trickily press items quickly or in a swiping motion, which is maddeningly inefficient.

Here is that little "procedure", as I typed it up:
################################
1. Enable Engineering apps by dialing *#*#307#*#* into the Phone Keypad.
2. In Application drawer, Go to "EMlist"
3. In "EMlist", go to "Touch Panel".
4. In "TouchPanel", go to "Configuration"
5. In "Configuration", under "Interrupt Mode", I changed the selected radio button from "CoordinateCompare" to "SensePeriodical" --and the keyboard began to behave as I'd hope, with no trace of the difficulties before. However, upon opening that applet up to this point, I observed that the value had reset itself to "CoordinateCompare". There is apparently an "OK" button below there that needs to be pressed in order to save the Configuration change. However, upon reboot, the same old problems reappeared, and the setting had reverted to "CoordinateCompare". There must be a way to hard code this setting, but I'm not sure just where.
################################

Does Anyone know what settings will allow me to keep the screen configuration set to "SensePeriodical"? 


The speculation from the last owner is that this may be hardware failure in the digitizer, which would kind of stink because I can't get Dell to fix or trade out this device from the Texas beta program.

I'm really hoping that this is a software issue, especially seeing how changing from the "CoordinateCompare" Touchpanel Configuration setting solves the main problem 100%, if only temporarily.

I'd love to get more input or feedback about this problem, and I also hope that this post of mine helps someone else make shareable progress.

__________________
Rogers Magic (running on AT&T)
====
Current: Alan090's CyanogenMod 5.0.8-t4 build
#####
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010(SAPP50000)
CPLD-12
RADIO-3.22.28.17
Jun 2 2009, 17:27:03
RA-sapphire-v1.6.2H
****
Dell Streak (Acquired after Texas Beta Program; Running on AT&T)
====
Model number - Dell Mini 5
Firmware Version - 1.6
Baseband Version - AUSTINBUILD_100210_01_BOSS_EVT
Kernel version - 2.6.29-perf
OEM Version - Unknown
Build Number - 79558

 

0 Kudos
1 Reply
philverb
1 Copper

Re: Two issues -screen calibration. Can't click Fastboot for 2nd fastboot screen; cannot get persistent settings for 'InterruptMethod' as named by Engineering tools application.

When using the utility for changing the InterruptMode, I see in logcat the following output, isolated as best I could:

######################################################################

D/PrintK  ( 1425): <6>AUO_TOUCH: ts_misc_ioctl()+, cmd number=5

D/PrintK  ( 1425): <6>AUO_TOUCH: ts_misc_ioctl: touch indicate mode? NO

D/PrintK  ( 1425): <6>AUO_TOUCH: ts_misc_ioctl()-, rc=0

D/PrintK  ( 1425): <6>AUO_TOUCH: ts_misc_ioctl()+, cmd number=6

D/PrintK  ( 1425): <6>AUO_TOUCH: ts_misc_ioctl()-, rc=0

D/PrintK  ( 1425): <6>AUO_TOUCH: ts_misc_ioctl()+, cmd number=8

D/PrintK  ( 1425): <6>AUO_TOUCH: ts_misc_ioctl()-, rc=0

I/reqall  ( 1778): [rq_default]>>>>>>>>>>>>>>> Scheduled freq check <<<<<<<<<<<<<<<<<

I/reqall  ( 1778): [rq_ReQallUserDbAdaptor][3ms][0 rows]SELECT login_id,login_password,time_diff,user_email1,user_phonenumber1,user_session_id,user_id,features,user_name,account_subscription,event_reminder_time,access_key,last_sync_time,last_sync_fav_order_time,has_more_posts_to_sync,has_more_places_to_sync,has_more_contacts_to_sync,has_more_collections_to_sync,has_more_tags_to_sync,has_more_favorites_to_sync,ts_posts,ts_places,ts_collections,ts_contacts,ts_tags,ts_favorites FROM user_properties

V/reqall  ( 1778): [rq_default]Cursor not null

########################################################################

0 Kudos