"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
johnh123 said:
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.
Click to expand...
Click to collapse
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.
johnh123 said:
I had the calibration issue.
philverb, try a screen calibration, that might help.
Click to expand...
Click to collapse
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?
Maybe. I don't get the fastboot screen when I power up with both volume buttons pressed. I get a different screen, which has a couple options including screen calibration, but not fastboot. After calibrating there, you may have some luck.
Sent from my Dell Streak using XDA App
johnh123 said:
Maybe. I don't get the fastboot screen when I power up with both volume buttons pressed. I get a different screen, which has a couple options including screen calibration, but not fastboot. After calibrating there, you may have some luck.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
There are two things here: the Recovery Console and the Fastboot Console/Screens.
Recovery Screen: hold down both volume buttons while powering up. You then get a menu of Four items:
1. Factory Reset
2. Software upgrade via Update.zip on SD Card
3. Screen calibration
4. Power off
--The Screen calibration has its own contextual instruction screen that indicates to "Press volume down key to calibration screen, Press camera key to exit." [grammatical errors not mine]
**This screen calibration for me fails with "FAIL" in red letters, no matter how many times I try.**
FastBoot Screen: hold down Camera button while powering up. This is where, as I have said a couple of times, the word "FastBoot" appears in the top right, but it is not surrounded by dashes as it is in the video I mentioned ( http://www.youtube.com/watch?v=vDXH17USk-g) at 01:58 of the video. It is the missing dashes that appear to define that "FastBoot" area as a button. In my version of the bootloader/fastboot thing, that area appears just to be a "dummy" area and intended not to be a clickable button.
--There is also a non-clickable area labeled "Touch calibration" in the top left screen, and I can activate it by using the left-hand volume button.
**When activated, this function makes the screen go dark, then returns to the original screen (also described in great detail in the original post), but then has the word "FAIL" in letters highlighted in red.
I really do appreciate your interest, and I hope that it doesn't seem tedious that I repeat myself in order to try to clarify, since you seemed to have gotten the wrong idea from the laborious detail I threw into the original post.
I think that what you have just mentioned is included in what I've been saying I have seen, no?
Thanks!
Did you tried opening the streak and reseating the touch panel cable? When I opened my streak just to check it out I saw a finger print in the camera connector, that made me think that MAYBE some wires weren't fitting 100%. Just a tought.
Good thinking....
BrokenPixel said:
Did you tried opening the streak and reseating the touch panel cable? When I opened my streak just to check it out I saw a finger print in the camera connector, that made me think that MAYBE some wires weren't fitting 100%. Just a tought.
Click to expand...
Click to collapse
That's a strong thought, and I thank you for it. My phone is (semi) bricked at the moment I am wondering now about the question of whether or not the screen problem may itself be preventing the FastBoot GUI from creating the border and therefore a clickable button.
I never get the the button border that is visible at 01:58 of the video at http://www.youtube.com/watch?v=vDXH17USk-g .
What do you think?
I've been given a troll-bricked Point of View Mobii tablet (Tegra 2 based) to fix.
I call it that, because just when you think it's about to enter APX and can be repaired, it just turns off again.
To be more precise, if I use the key combination to enter APX mode, the screen backlight comes on, but there's nothing on the screen. It stays like that for maybe 1 second, and then goes off again - all smug like.
What can I possibly do?!
Sadly I don't know what was done to put it in this state either... Just that it previously had some version of VegaComb installed (and working).
Cheers!
Update: Removed the four screws on the back, and removed the back panel itself. There was no concealed reset button, but after disconnecting the battery and reconnecting it, it was possible to get into APX.
My tablet is HKC P077A with 8GB ROM, 512 RAM and a 7'' Touch screen (Android 4.0.3). I am having 2 problems
When I switch on the tab, first "HKC" logo comes to screen and then disappears to show "android". This is standard. But after that the thing wont move forward. Just keeps on showing "andriod" with a flashing like thing implying the loading process. But after long wait there is no start screen and nothing changes. It just hangs there....
But if somehow got it to get into normal working(I donno how, but It sometimes boots ok and gets into normal working mode, with home screen and apps and everything). So once I get it right the other problem I am having is that the touch is giving VERY bad response. I have to click at spots multiple times to select that thing. Also the response is very slow. Its like the tablet is hanged. But when I tried connecting a mouse (through OTG) and everything works fine again. Is my touchscreen gone bad..??
I am already done with, reset (from "settings> backup and reset") [I cant find how to do factory reset on this model from "off" state(read below)]
I have tried to get into reset screen by pushing "Power Button+Vol up" button. Then I know the tab gets turned on (I can hear a small white noise from the loudspeaker) but nothing comes to screen. So the "Robot with heart open" is never shown. I also tried using "power button + Volume down", this takes me to a screen written in chinese. Now, I don't know Chinese but from the look and feel, its a troubleshooting window, where I can check weather components of my tablet are working (eg. I click one menu(with difficulty), then the front cam turns on, another menu makes loud sounds from speaker and another flashes many colors in screen etc). I found that most are ok except something called "T" (On the screen, its the last item to the right, is it "touchscreen"??)
So, what can I do to get my tab to work smooth again..? Is the touchpad having trouble..? Need I do any specific troubleshooting..?? Any Ideas on which key combinations to get on to the "factory reset" menu from off state..??
Also can u please specify the key combinations to the tablet factory-reset menu from "off" state.
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
robjg63 said:
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
Click to expand...
Click to collapse
Hello!
Please write your problem to an official bugreport https://wiki.lineageos.org/bugreport-howto.html to let the LOS developers team about the encountered issue.
Thanks. Signed up to add the fault and found someone witha different device reporting the same bug around a week ago.
Added my confirmation of the problem with different hardware.
Fingers crossed someone may have a look at it when time allows.