Related
Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.
Any help would be grateful on this one
I have just changed the heat sink on my 9300 wifi ITX motherboard GF9300-D-E.
It will not boot windows as it gets to the starting screen and stops. Then when i tried linux it will kernal panic and not boot that either.
I thought it was memory and removed one of the sticks. This is when things started to get strange. The bios screen did not fit my monitor as it should, has done previously, also there are strange flickering on this as well.
So i have tried it with both sticks in one stick [both tried]
Now I am a little stuck as to what it can be. I have also reset the bios to a default state to see if that was the problem and it was not.
There is also the issue that on some boots the bios will not fully load up.
If this is not an issue with the motherboard then i am sorry but i am a little stuck for the reason at the moment.
So anyone any ideas on this as I'm a little stuck. Any other info will be added if you think its necessary but i think its all covered.
Please help I miss my desktop, my ageing 5 yr laptop really does not cut it any more
have you tried safe mode? press f8 when windows is starting. if you get a blue screen post what the error message is.
Yeh the one time i got that far i had
Page_access_in_non_paged_area
That was also on a recovery boot of windows.
Next time nothing happened...
Also i get weird graphics glitches on the memory test from ubuntu. if that means anything to anyone
chris10230 said:
Yeh the one time i got that far i had
Page_access_in_non_paged_area
That was also on a recovery boot of windows.
Next time nothing happened...
Also i get weird graphics glitches on the memory test from ubuntu. if that means anything to anyone
Click to expand...
Click to collapse
i need the stop code. it goes like this 0x000000 and so on.
Yeh i would love to post that error message but i cannot get that far until it crashes
I got to the windows system recovery hit enter, then it stopped working
Now it wont even give me a video output! Really starting to think its hardware, but what hardware i do not know. Later im gonna try some RAM from my house mates pc and see if it does any better. If that doesn't work then i think i may be RMAing the motherboard as its the only other thing it can be!
If you have any more ideas joe then i would be welcome to hear them as i would rather not go down the RMA route...
Wish id noted down that bluescreen when it came up now
sounds like your video card. is your video card onboard or add in?
on board but i can disable if i have an external one, i can try this as well house mate has a spare will get back to you when i have tried that one as well.
If it is that then def an rma job. Also i would not be surprised it has been idling at 70/80 degrees C for about 8 months due to the passive cooler i had on it.
Hey,
I had this error, and a range of other ones, stuff like Memory_Error etc (can't remember codes), on my laptop earlier this year.
I tried memtextx86, and burnin, as I suspected it was an issue with ram - I also tried 3 different sets of rams, with different combinations of sticks. Nothing worked.
Unfortunatley, I took it back to the manufacturer and it was the motherboard had gone faulty.
I hope this isn't the case for you, but those 2 programs may be worth trying. Just as a note, neither reported any issues with the ram.
When in windows (vista at the time) I could not be in for more then 20mins without a system hang and crash. Although I did have video out.
Hope this helps
Stu
If the only thing you changed before it started to play up was the heat sink, its probably the cause.
If its turning on and then playing up after a period of time for no apparent reason it could be heat.
Is the heatsink on the right way? I put my amd stock heatsink on backwards when I installed it, didn't notice for 2 months, it wasn't touching the processor at all. Funny when I look back on it.
Did you put thermal paste on it? I once thought it would be a great idea to clean all of that gunk off my cpu, not so good in hindsight.
Hope it helps,
They say you learn from your mistakes, an I've broke more computers than I can count.
stu i shall try at the weekend one more exam and im free for another year!
and mercianary yeh i did clean the paste off, i did apply paste, but going back is a good point as i think there may be slight sizing issues with the heatsink i changed it for. As for temps, not real problem i think as i want from a passive heat sink to one with a fan so it must be cooler, that was the idea anyway.
It was idling at 45-55 if it did anything that needed the whole chip, its a 3ghz core2duo it hit 65 easy and it starts to underclock at 70 so i wanted it to be cooler so i could use all the power all of the time! In hindsight a bad idea.
Also on the grounds of the stock cooler that is broken as it kinda got stuck on the motherboard when i put it on one of the clips went straight through and jammed....
anyway everyone who has replied thanks i will come back when i have done some testing.
This may be a problem beyond the scope of android, but seeing as I'm running it, I thought I'd try here first.
I've noticed that the lower left hand side of my screen has a "dead spot" where touch is simply not registered. To illustrate, I went to screen calibration's test screen and drew a straight line along the edge of the screen. (See Attachment)
I've tried recalibrating the screen (manually and resetting to default calibration) as well as wiping data and reinstalling the system. Reinstalling the system worked once, but then the problem came back and subsequent reinstalls did not fix the issue.
I'm running Incubus26jc super froyo [RLS 12] on the 15-07-10 340X480 Froyo Kernel.
Anyone else seen anything like this? As far as I can tell, the problem is not getting any worse. Currently, it's only a hindrance when trying to use keys in that region, but I can work around it by switching to and from landscape. It's a bit of a hassle, so I'm hoping someone may be able to shed some light on the situation.
I was sure it was hardware until the system reinstall fixed it, but am now baffled as I can no longer replicate the fix.
I have not tried reinstalling the kernel but will at some point in the next day or so. I'd like to avoid switching back to WM to check if the problem persists, but may have to... we'll see. Doing everything I can to make this phone last until the Incredible month of February when I'm up for an upgrade.
dont know the issue resolution... but i have the same with my touch vogue.. and in the same 'area' apparently as well.
hard for me to hit the 'a' key on my keyboard. hehe
I'm glad to see I'm not the only one... anyone else?
Bottom right corner for me... I was able to calibrate around it but it took a few tries.
Sent from my Full Android on Vogue using XDA App
The sensitivity across my screen was inconsistent some time ago. I found that years of my abuse had taken a tole on the exterior of my phone. It eventually got worse and I bought a new housing (with a new digitizer) on ebay for a reasonable price. If it is hardware then it really isn't that hard to fix if you like taking things apart.
If you're sure that win mo accepts input from that part of the screen then nevermind my post. I would play with a painting app though and investigate the hardware further.
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
In any case, my investment in a hew housing was well worth it considering how modern my old phone has become thanks to the developers here.
gooph said:
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
Click to expand...
Click to collapse
In my case, no - when drawing a straight line down or across the screen, the line starts 'moving' away from the stylus (like the picture in the OP).
Gah... now it's shutting itself off randomly and the dead spot has grown. Not good at all.
Yeah, mine was better for a while then 'slid' again. I ended up swapping the digitizer with my other Vogue and things are back to normal.
Sent from my Full Android on Vogue using XDA App
I have another vogue, but am weary of doing anything like that. How hard was it to get done?
All you need to do is switch the front half of the housing rather than the digitizer itself- it's not hard. There's a teardown guide somewhere in the forum, Google Vogue teardown and it should be at the top.
Sent from my Full Android on Vogue using XDA App
The only thing that worries me is that my spare vogue exists because it was dropped in a muddy puddle. I'm hoping the water damage isn't too bad. Guess we'll just have to see.
it is really annoying
I have the exact same problem and I too thought it was a hardware issue till I saw this Thread. I was ignoring it till two days ago when it started really bugging me. Now, I don't even need to press any button and it automatically gets pressed around the curve and I have a google search box there, so it keeps on searching for eee or sss randomly and started draining my battery. Is there a proper fix for this?
I thought I'd chime in too... I could never seem to calibrate the touchscreen properly in either Android or Debian. Changing the screen resolution (i.e. msmfb scaling) seems to have no effect, whether it's 240x320 or 640x480. Any area within 5mm or so of the edges of the LCD will register as the edge, making "A" and several other keys on the virtual keyboard impossible to hit. Passing calibration values to the kernel didn't seem to fix anything, but it's possible I was using them the wrong way...
i have the same kind of problem on my Kaiser... i think its realted to hardware... either the housing or the digitizer...
I am experiencing the same problem on X10 mini pro. the same screen spot exactly, i have to try very hard to get z or x or shift to work. Sometimes when I try locking the screen and unlocking it back, it works.
update
so after a very long time with this problem i decided to change the digitizer and problem is gonne. visualy the broken digitizer had nothing wrong with it. The fix was fairly easy though, there is no glued parts involved into getting a new digitizer on the u20i.
Touch Screen
I just bought a brand new Cubot One and it looks more than perfect! It has just a little problem with the touch screen ( I think its the software, need ROM change). There is a dead line on the right side of the screen that touch doesn't work at all. Any solutions? Anyone faced that before? Can I fix it myself or do I have to send it back for replacement? Is there any video or guide that shows its done?
I uploaded a video on YouTube to show the problem but i cant post it yet.. (new member)
You can write "Cubot One touch screen problem" and it's the 1st one.
Thank You!
Long story short. My TP has CM9 installed and will not turn on at all. I've searched and tried every possible thing to try and get it to boot but I get nothing at all. I'm basically out of options and thinking of sending it to HP for repair. Has anyone sent theirs to HP while Android was still on it? And if so, what did they do or say about it? My wife had dropped it once but it worked fine for awhile and has no sign of physical damage. I was thinking of opening it myself to see if anything came loose or something. Is there a way HP can tell it has been opened in case I still need to send it in after I open it up?
I don't have personal experience, but I would imagine unless the thing is completely broken where they can't get it booted and can't read the filesystem, they'll be able to tell. Technically, you already voided the warranty. I imagine opening it up will make matters worse as far as they're concerned. I believe I've read of people getting their TP fixed even with CM installed, but usually for screen issues that are obvious hardware faults.
I too have had the issue where my TP seemed completely dead, but finally after many combinations of button holding, rebooting, and recharging, it came back.
I will say, in my limited experience with HP's support, they are stellar especially considering the TP is a dead product. I want to recommend just being honest with them, and maybe they'll cover you this one time.
I sent mine in with CM7 installed and they replaced it without any problems whatsoever. My Touchpad had the battery with a question mark issue and they seem to have replaced the logic board along with the battery, but got me my original case back (same serial number, but different MAC address).
Yep I would just send it in as is and not try to do anything further. I highly doubt that they will be able to tell CM9 is installed since I don't think they even try to fix them via software without completely redoing the filesystem.
A friend's sister bought her a touchpad some time ago - not sure it's ever been used. When we run the diagnostics on it, there's a band right across it where the touch sensors aren't working. So, before I invest any more time into getting this thing going for her, is there any possibility that putting kitkat (or even some later version) on this will fix this problem or is it just flat out a hardware issue?
By a band do you me a 'dead space' is there a visible 'smear' on the screen?
It won't take much time at all to flash KK on it (famous last words).
Should go smoothly. Use Rolands Tutorials for reference.
middle_road said:
By a band do you me a 'dead space' is there a visible 'smear' on the screen?
It won't take much time at all to flash KK on it (famous last words).
Should go smoothly. Use Rolands Tutorials for reference.
Click to expand...
Click to collapse
A dead band. If you hit the screen there it doesn't register. About 2 inches wide from side to side.
Seems too defined to be software related but I thought I'd ask. If it won't help, I'm not sure I want to invest the time so I was hoping someone could tell me one way or the other.
doncaruana said:
A dead band. If you hit the screen there it doesn't register. About 2 inches wide from side to side.
Seems too defined to be software related but I thought I'd ask. If it won't help, I'm not sure I want to invest the time so I was hoping someone could tell me one way or the other.
Click to expand...
Click to collapse
I've repaired them where the battery was 'swelled' up from over charging, but I haven't yet seen a dead area from side to side.
Is it possible to bring it up in WebOS and see if the problem is there also?
_Dan
middle_road said:
I've repaired them where the battery was 'swelled' up from over charging, but I haven't yet seen a dead area from side to side.
Is it possible to bring it up in WebOS and see if the problem is there also?
_Dan
Click to expand...
Click to collapse
I have two Touchpads, both set up the same. One touchpad the screen works perfectly, but on the other one there are "dead spots" not lines where you lose the capacitive touch. Which leads me to believe that it is not software related in my case.
Don't know if that helps.
Sometimes is only dirt in the way. Open the Touchpad and clean the touch sensor from inside with alcohol.
Search on youtube for cleaning touch sensor, you will get the idea.
I have fix one that one, and it works with no dead spot.
good luck!