[Q] Two issues -screen calibration. Can't click Fastboot for 2nd fastboot screen.

---

"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.

Sounds like a hardware issue to me. Can it be sent back for repair?

Sent from my Dell Streak using XDA App

It cannot be sent back for repair since it is a Beta hardware model.

If it be a hardware problem, then it's really kind of odd that the change in sensory detection or interpretation makes a 100% improvement. The "Interrupt Methd" should not be able to correct a hardware problem that would otherwise be really pervasive, don't you think?

I reallyy appreciate the feedback!

I think that the most important question for me and my little orphan is: "How do I make a permanent change to my Streak's 'interrupt Method'?" If it can be done satisfactorily with the utility in question, then where is the configuration file (in /etc, I'd imagine) where I can manipulate it?

Everything in the running GUI environment for the touchscreen is made better by this adjustment, but I don't know how to make it a persistent configuration change rather than a temporary one (and it is temporary when I change it with 'Emlist', reverting when the screen goes to sleep),

On top of that, I'm getting USB errors --oh, nevermind.

---

I have observed in my gnu-linux syslog that I'm getting:
###########################################
Sep 21 21:00:50 $HOST kernel: usb 2-2: new high speed USB device using ehci_hcd and address 4
Sep 21 21:00:55 $HOST kernel: usb 2-2: device descriptor read/64, error -71
###########################################

...from the Streak when on the first FastBoot screen.

EDIT: Nevermind --My USB connection has been fine for ADB operations, so this is of no consequence.

I had this problem, such that the device was essentially unusable. Dell replaced my phone. I've seen on various forums that a number of people have this- hopefully Dell gets a fix for it.

Sounds like you took a spin on the Beta roulette wheel and lost. Sucks to be you, but youre not the only one, if it makes you feel better.

Sent from my Dell Streak using XDA App

Originally Posted by johnh123

I had this problem, such that the device was essentially unusable. Dell replaced my phone. I've seen on various forums that a number of people have this- hopefully Dell gets a fix for it.

Do you mean that you had a USB problem or the Calibrate Screen problem?

My USB connection has been fine for ADB operations.

I have just noted that my first FastBoot screen lacks the border of dashes that can be seen at 01:58 of this HOWTO video: http://www.youtube.com/watch?v=vDXH17USk-g . I have never gotten a glimpse of the screen that appears at 01:31 of the video.

The FastBoot item on the first fastboot screen is not clickable, no matter how hard I press or how widely I go for a click/press.

This makes me think that the FastBoot "problem" may not be intrinsically related to the touchscreen's problem.

Any ideas? I am starving for ideas, especially since I just tried to use 'flash_image boot.img' from a Modaco recipe, which has left me unable to access the OS.

Also, there is no ADB access from the Dell recovery console. Is that true of all these Streaks? All I've ever gotten while in that recovery mode is "Device not found".

I had the calibration issue.

philverb, try a screen calibration, that might help.

Originally Posted by johnh123

I had the calibration issue.

philverb, try a screen calibration, that might help.

I tried to take note in the OP that screen calibration actions in the Recovery Console and in the first screen of FastBoot do not work, failing with a big, red-lettered "FAIL".

Did you have something else in mind?