Related
"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?
Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service
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.
Dear friends, see this, see in the youtube:
watch?v=ixWozCI8sek
I activated the phone in their own settings of android to show screen touches and strokes that you can see in the video above, and installed YAMTT app to better show the problem.
The Problem on mobile touch in the middle of the screen there is a track that is not recognized touch, but if I press the screen sinking, she returns to work temporarily, and now recognizes the touch - but after a few minutes the problem back and touch is not recognized again.
The screen is perhaps dished up, and when I press down her back to be in contact with the part of the cell that recognizes the touch, but with time the screen should be getting back dished up (this is my guess, not i'm sure).
Detail, not always when I press is running, sometimes I press the screen to the center of the touch again be recognized, but it seems that the phone is registering touches alone.
What would be a solution, and change the screen (it does not mean that changing the screen the problem solved), want to try other alternatives before changing the screen.
Perhaps heating up the screen with hot air, in theory it will expand and become more pliable, and then if I press down the center panel of the phone with something for a while until it cools, in theory the screen would remain indefinitely, and if that is the problem could solve -
Anyone have any thoughts, has been there?
Thanks in advanced!
Hi all,
I got this Xperia M5 that's been giving out warnings about memory being full and I suppose it finally gave in. It only partially boots after like a full minute of showing you those blue waves. When it 'boots' the screen is black and nothing works, except you can see the status bar with just the battery icon, no-SIM icon and the clock.
Weird thing is when the device is powered off, you can press the power button once and it'll display a large battery indicator which shows the percentage normally-- I've seen this go up from 0 to over 90 something incrementally.
But when it's 'on' the way I just described, the battery is always at 0% with a red ! next to it.
Anyway, when it's in this weird half-life mode, you can actually pull down the notification bar normally, and tap stuff as well. Flashlight works, you can see an actual WiFi list (nothing happens when you connect) etc. When you launch stuff through here though, like settings, it won't open anything. It'll make the sound as if it's launched something but the remainder of the screen will still be black.
Using the dedicated camera button, I can access the camera. It works (sort of), meaning you can see the camera display where the screen used to be black. And it immediately says "system process is not responding," so I'm guessing this is a system issue where it can't load basic stuff like the homescreen?
Whatever you do or don't do, it stops responding after a couple minutes and shuts itself off.
Stuff I've already tried:
- Safe mode (volume down + power), just 'boots normally'
- Recovery mode (volume up + power) done that for over two minutes, does nothing or just 'boots normally'
- Hold down the tiny yellow 'off' button under the SIM/SD cover, did nothing.
- Xperia Companion: PC won't recognize the phone either in that zombie state, or when it's off, so I tried 'device cannot be detected', shut phone down, held down volume down button, connected USB still holding down, waited for a while and viola, nothing happened.
It's factory OS, never messed around with it and I don't know the version (could be 5?).
Any ideas?
Guys at this point all I'm wondering is if anyone ever managed to brick a phone that's as semi-responsive as this one, in the history of bricked android phones anywhere.. I mean how could it be bricked when you can (sort of) boot and even open the camera?
you said it boots in download mode?
paranoic(d) said:
you said it boots in download mode?
Click to expand...
Click to collapse
No I wouldn't say download, it's weird-- there's the status bar at the top and soft navigation keys at the bottom, but the homescreen in between these is black. I tried tapping this black area to see if stuff is there logically but you just can't see them, but there was no interaction, no sound or anything.
I am able to pull down the status bar to reveal the usual buttons and such, like I mentioned before you can turn on the flashlight, click to see a list of available wifis etc. But you can't access settings through here, I mean you tap settings and the main part of the screen is still black.
The only way to get the screen to work is to open the camera through its dedicated button, where the camera display works normally, you can switch cameras etc. Tried accessing the gallery through here but it didn't work.
I just don't wanna buy a new phone when this one doesn't seem bricked at all. If it like didn't respond at all and nothing appeared on the screen I wouldn't think twice before buying the first phone I see on Google.
im afraid that you have to flash stock rom again if you will boot into download/fastboot mode.but your problem seems strange.what was the last thing you have done before phone stuck like this?
paranoic(d) said:
im afraid that you have to flash stock rom again if you will boot into download/fastboot mode.but your problem seems strange.what was the last thing you have done before phone stuck like this?
Click to expand...
Click to collapse
Not my phone but it'd been going on about low memory for a while now. I got the PC to recognize it once in that zombie state, so I'll try that with Companion if I can get it to half-boot again. I'll post updates if anything happens.
antiglue said:
Not my phone but it'd been going on about low memory for a while now. I got the PC to recognize it once in that zombie state, so I'll try that with Companion if I can get it to half-boot again. I'll post updates if anything happens.
Click to expand...
Click to collapse
okay keep us updated