Related
Tried connecting my kaiser to 2 different pc's and it won't get detected. The device will charge but activesync won't pick it up. Also its not listed in device manager! I tried disabling/renabling advanced network functionality as well has soft reset the device several times. I'm on the verge of hard reseting BUT when i put my device in bootloader mode it only says serial.. will not say USB as its supposed to
any help would be appreciated.. i'm on death v4 rom btw.
thanks in advance!
fone_fanatic said:
The device will charge but activesync won't pick it up.
Click to expand...
Click to collapse
Can you get an activesync connection via Bluetooth? When you inspect the extUSB connection can you see anything which looks wrong (such as a wire sticking out/in more than the others? What happened preceding this problem?
If you hard reset the device I don't see the relevance of the bootloader. It'll just restore the original image from where it's tucked away in the devices ROM. If it was working fine straight after you installed the ROM thats on it now and doesn't work after a hard restore then that points towards a hardware failure. If you have to go down the path of restoring to a different (original) ROM for returning purposes, there are ways of doing this with a microSD card - although I've not tried. I think the wiki would help there.
bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....
This might be a stupid reply but I had the same problem. My cable was busted so you could try another cable.
I am in the same situation here
Tried it with 3 different PCs with 3 different cables.
It's charging, Active sync pickes it up and trying to connect but fails to connect.
The only think I can come up with, I used new charger in the car. May be it killed the port
Is there any way to find out for sure?
i tried 2 cables with 2 different pcs... its only charging it and the computer won't detect the device at all. Nothing under usb in device manager.. even in bootloader, it only says serial not usb. I've downgraded to a shipped AT&T rom and Radio through the storage card but i still need to downgrade the SPL before i attempt to get a warranty exchange. IS that possible to do with through microsd yet?
I'm having the same issue. The usb port charges the phone fine with the USB cable, but teh computer does not detect the device. I also tried the headphones and they work fine as well. Help!
Update: I just tried a different usb cable, and now the computer recognizes the device, but as an unknown device.!!!!!
fone_fanatic said:
bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....
Click to expand...
Click to collapse
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx
ajay6780 said:
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx
Click to expand...
Click to collapse
Thanks for that suggestion but still no dice
The computer isn't detecting the device at all! Usually when a usb device is plugged in you can go to device manager and look under USB and see it there, but its not showing up. I've scanned for hardware changes several times and nothing.
I've now tried on 3 different computers (2 pc's and 1 mac) with 2 different USB-MiniUSB cables and nothing!!
i guess i'll just go to the at&t device support center tomorrow and hope they'll replace it on the spot and notice that i've changed the SPL...
can i ask for the people that are having this problem to do the following.
With your device unplugged from the PC open device manager. (Right click My Computer -> Properties -> Hardware (3rd tab) -> Device manager) Then expand the last tab (Universal Serial Bus Controller) and plug in your device.. if it doesn't show up then click actions -> scan for hardware changes..
I just want to make sure if your computer is detecting your device or not..
just an update with my situation. i went into the att device service center today and told them my problem... the guy behind the counter had no clue what he was doing. he just looked at it like a monkey for minutes then swapped it out for a new one. no questions asked even though it was hard spl'd, cid unlocked, and sim unlocked.
but now this device's vibration is really weak and i lost my invsishield protection on the front (kept the battery cover and my ppctechs scren protector)
Busted? or just won't work
Hi all,
I have been coming to these forums for a little while and only posted a couple of times. I felt this was important. I was having the same problem. Tried the cables, resets, ROM changes the works. I have had my at&t tilt htc 8925 for 36 days when I reported the problem to them. But it actually started about 10 days before. At&t tech support was very rude and accusatory when it came to them "helping" me. I, like probably all owners of a phone like this treat it like gold. It is very important to me. So when I contacted tech support and was told it was probably abuse or I had "buyers remorse" (I don't want to return the phone I just want it fixed!?)
The best they can do and they do not budge on this is for me to return the phone for an exchange. BUT, and this is a BIG AT&T but, the phone they exchange it with is refurbished. Something someone has returned. I do not want a phone that has been returned. I want mine fixed. "This is my phone, there are many like it but this one is mine" Know what I mean? When I bought the phone the guarantee was "we'll just replace it with a new phone" and I like 1000's of others did not ask if that "new phone" was refurbished. It is. Now advocates will tell you as they did me, refurbished is actually BETTER than new. Huh? Then why aren't all phones sold refurbished ones? And if they are so great, take mine back, give me one of those "crappy" new phones and give mine to someone who wants a sweet refurb. I am outraged by the whole mess.
I have searched forums and complaint sites. The bad usb port problem is NOT an isolated incident. There are a lot of people with the same "it charges but won't sync" problem. This is a known problem they refuse to address. Their stand, send in for refurb.
Personally I would like to see a recall fix class action against at&t. It can be fixed but they just don't want too. I thought I would be relatively safe buying for a huge company. They spend millions on advertising to simply leave their customers twisting in the wind after 30 days. Very bad business.
That's the rant. So I decided that if the warranty was useless anyway I'd take a shot at it myself before sending out for repair myself. There is a place in California PPC Tech http://www.pocketpctechs.com/main.asp?area=home that will fix the usb for $79 and ship it back to you in a few days. They seem to be reputable and a lot of people are opting to fix this problem themselves.
How did I fix mine? by altering the mini usb end of the sync cable. I tried other cables and connectors but I think it has something to do with the contact points. The only way mine would work was if I plugged it in, wiggled it slowly and with a little bit of pressure at times, around until the screen brightens. That means it has made a connection, then don't move. Hold very still. It took both my hands. Wait for what seems like 2 mins and it would start to sync. Based on this. my repair (before I send it to California for repair, which I may end up doing anyway) is make sure the plug on the phone is straight and not damaged. If you can get the phone to sync this way you may be able to crimp the mini end of the usb very very slightly to make the connection you are manually doing by wiggling it around. It took a lot of small tweaking but it now syncs about 29 out of 30 times. That's about as good as it gets.
So good luck to us all. If you can't get it to work yourself send it out west to PPC Tech. In this economy the phone companies like at&t better start getting their customer service back on track before they have no customers to service, It has happened to the biggest before. Wake up AT&T! The days of the business model of massive turnover and new signups is coming to an end as people tighten their belts. Treating current and future users poorly is a sure fire way to put yourself out of business.
here is my gift to you all..
http://forum.xda-developers.com/showthread.php?t=362679
read this post and check EVERY SINGLE LINK in the first post...i had this issue and i ended bending my usb plug every which way until finally i broke the plastic seperator off and in turn smashing the second pin from the left on the top off (the one in charge of activesync) over and over until it broke...i didnt really care i could still flash by sd but then i smashed the + power pin and so i was on the phone with att for many many hours explaining to them that its a known issue to users but not to the company and they finally sent me a replacement..i should have just searched my butt off before trying to deal with a problem/fox it myself (yes i dissasembled it and soldered the pin back on and it broke off multiple times causing me to dissasemble it many many times and smashing it again and i ended up getting alcohol on the water damage void pad which i replaced) learn from me...if you ever have ANY problems that are significant..dont try fixing JUST GET A REPLACEMENT...who cares if its a refurb..if the refurb sucks then send it back until they send you a new kit...after 5 returns you get a new kit soo just keep sendin back them refurbs until your happy
oh and to make it easy on yourself because if you tell att you have a usb problem its NOT covered under warranty and will take you many many hours like me to convince them otherwise (which someone eventually will understand because certain people ARE familiar with this problem at ATT it just depends who you get and how many times youve been elevated in support)..what you need to do is IF YOU CAN return your spl back to stock (if you manage to get a long enough connection with activesync) but if not dont worry too much att doesnt really check spl just that you have the shipped rom on there so load the shipped rom (found on here) on your sd and flash back and just make up some excuse that it isnt working right and youl get a replacement or if you can get the spl revrted jus throw your device in bootloader by a failed flash (pull the usb out during flash) and say its stuck in the funny colored screen lol
jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (nokias, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!
fone_fanatic said:
jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (Niki's, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!
Click to expand...
Click to collapse
Hi fone
Thanks for the reply.
Yes, I agree with you. If the phone has something else that is messed up like you were saying a scratched screen or buttons. It's just that I am as careful as I can be to keep the phone in nice condition just to send it back for maybe one that someone didn't take the same care of.
Mine works good now. I think it has something to do with when I crimped the cable end. It make a tighter fit. I think that may be the key to mine and others problems. For sure it is becoming more and more clear that there is a design flaw whether att wants to acknowledge it or not.
Thanks for your input about PPC too. If I do end up having to fix it that's probably the way I'll go if that is still the only thing wrong. Otherwise it's in for the warranty as you suggested. I KNOW I'm not that smart.
Im having this same issue and it is definately not a cable problem.
tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
if u think its a hardware problem then take it to a service center. The guys there just follow step by step guides on how to diagnose phone issues. For me he saw a crack in the usb jack on my device and just replaced it. If you send it in to HTC i think theres a higher risk of them figuring outu the device is hard spl'd and wont honor your warranty.
tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
taylor, I'm not saying it is a cable problem. I am saying it is a hardware port problem. I "fixed" mine, probably temporarily, by crimping my usb cord so that it holds more firmly in the port. I did say if you have the same problem and you use the same test I did ie: move it slightly, Gently, not like others I have heard stories of where they ram it from side to side until it snaps off, that you might be able to do what I did. I thought others with the same problem might be able to use this workaround until at&t figures out it is not an isolated incident with thousands of people having the same problem thats all. Hope this helps.
jj
I had a similar problem. Phone would charge fine, but windows didnt even recognise anything was plugged in. Interestingly the bootloader changed to USB when the cable was connected, and Serial when unplugged.
As it turns out (thanks Flying Kiwi for suggesting the obvious I had overlooked) the middle top pin was recessed too much into the plastic guide, so I stabbed it a bit with a scapel and all is well.
So it seems that the Serial/USB section of the bootloader cant even be trusted.
I don't know what caused this.
I got my G1 today. It worked for probably 2-3 hours perfectly fine.
I had an app freeze (either Barcode Scanner or Lock 2.0) and had to do a full hard reset.
Now, whenever the phones screen darkens or I put it to sleep manually, it WILL NOT come back up.
I have factory reset three times now to try and get this to work.
When the screen is black, all buttons on the phone still light up and so does the LED indicator up top. I had my phone set to use a locking pattern screen at one point during one reset to test out and when the screen went black, I was still able to try and log in by doing my pattern. It unlocked, but still showed nothing on the screen.
Please help!
I've tried:
Turning Wi-Fi off
Turning 3g Off
Disclaimer: Yes, I've searched. I can find other users with the same problem but none of them seem to have a solution.
Phone is NOT ROOTED and has the factory ROM.
Update 1: Update: It only freezes/blacks out when I try to wake the phone from one of the front key buttons.
If I'm sliding to unlock, it seems to be fine.... (but if I've already tried to open from the front it doesnt)
Update 2: If I mash all the buttons in random orders for about a minute or two it seems to come back. Anyone have any idea?
Update 3: I'm thinking this has to be an issue with none of the buttons waking the phone up when closed. If I lock the phone with the "END" key, and then click the front "END" Key again, nothing happens. If I slide the phone open, and click it twice - the phone wakes up.
Update 4: Confirmed update 3. Phone will not unlock via front keys unless it's slid open (or open enough to trigger).
I would really, really appreciate help with this.
Hate to bump this, but I've added some detail on the top and bottom. Have to leave for work, hopefully someone might have an idea by the time I get back.
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Karolis said:
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Click to expand...
Click to collapse
Removed the SD card and rebooted the phone.
No change ( still acts the same way ).
Did you factory reset after or was it an instant change?
I don't mind losing data to fix this.
supremeteam256 said:
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
Click to expand...
Click to collapse
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
zeabrid said:
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
Click to expand...
Click to collapse
If you use the official update you don't have to have root. There are some links on here. I'll see if I can find it for you.
https://android.clients.google.com/updates/signed-gfh-CRB43-from-CRB21.c88b03d2.zip
That should be it, but can't confirm since I'm on my work computer.
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
The link didn't work, btw.
derfolo said:
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
Click to expand...
Click to collapse
Zero water damage.
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
derfolo said:
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
Click to expand...
Click to collapse
Do you have a link to a guide that teaches how to do this (with the stock rom)? I can only see a few that're spread out.
I'm not entirely sure my phone can boot into safe mode/disk mode, so we'll see about that.
Another update: When I boot into safe mode, the same problem exists.
Edit: Just emailed HTC.
This can officially no longer be considered a software issue.
I just rooted and installed a standard ROM. Same issue.
It happens all the way at boot now, just realized this.
HTC emailed me back and told me to call them directly. Will do that tomorrow.
if I find a solution I'll post it immediately.
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
zeabrid said:
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
Click to expand...
Click to collapse
Yea it defitenly sounds like a hardware issue and needs to be fixed. Glad your getting it fixed and you'll be covered no problem.
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
zeabrid said:
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
Click to expand...
Click to collapse
To be honest I don't know the answer but would like to say they would pay for it. But they would have to let you know of the charge before they apply a charge to a credit card.
wow its weird cause im just having a similiar issue now.. in landscape mode.. phone and back light work perfectly. but one i close the screen everything goes virtually blank, everything is running perfectly just the screen light wont turn on..
will try some of your previous methods.. hopefully it works on mine..=/
thanks, for the info zeabrid
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.
I guess I'm one of the unlucky ones who has to send this phone in for repair.
Going there this morning..
My question is to those that have received their phones back. Any indication that the repair done has anything done different to the phone?
I mean, if they are just replacing the defective guts with essentially the exact same guts but working, does that not mean it will just happen again (SD Failure)?
Or did they actually change something within the phone to make it more durable and essentially eliminate what brought it to them in the first place?
Hopefully someone in the know could answer this... pointless to repair something with another soon to fail board or sd card.
that is a very good question, of all the phones i sent in for repair and got back
they kept their original IMEI numbers
they all came back with replaced PCB (motherboard) and cause of failure is "No Power"
by that i figure out they mean, it does not charge when you plug in the USB cable to the phone after it dies.
it seems like whatever controls the internalSD also controls the USB charging of the phone
so the problem might not really be with the internal SD but rather the power relay that supplies power to the internal SD and battery charge.
greeced said:
I guess I'm one of the unlucky ones who has to send this phone in for repair.
Going there this morning..
My question is to those that have received their phones back. Any indication that the repair done has anything done different to the phone?
I mean, if they are just replacing the defective guts with essentially the exact same guts but working, does that not mean it will just happen again (SD Failure)?
Or did they actually change something within the phone to make it more durable and essentially eliminate what brought it to them in the first place?
Click to expand...
Click to collapse
This is a great point allgamer.
However fact still remains... if they are swapping out the guts for identical, but working internals, that defeats the purpose of actually correcting the problem as the problem will surely pop up again.
Lets hope it doesnt.. but this phone doesn't seem like a good candidate for constant flashing the way my old HTC Touch Diamond was. Especially if you're doing it with ODIN, you may not have a leg to stand on come out of warranty claims.
At least if you flash something with KIES, because it was an "official" update provided by samsung. So if the phone goes corrupt, you can yell to the heavens and they'd have to fix it, because essentially they corrupted your phone.
It would be great to get some feedback from other members who received their phone back from repair. I wonder if one of those members had the SD go corrupt again with the new Motherboard in place.
Help! No touches are working, I even used webOS doctor and went back to webOS to no prevail. I know that these forums are mainly for software and this is probably a hardware issue, but I hope someone will be able to help me.
Backstory: this issue happened last year I think (don't remember exactly when) and I got frustrated a lot by the tablet so I just packed it up in the original box and now it's downstairs in my basement LOL
PlebMaster said:
Help! No touches are working, I even used webOS doctor and went back to webOS to no prevail. I know that these forums are mainly for software and this is probably a hardware issue, but I hope someone will be able to help me.
Backstory: this issue happened last year I think (don't remember exactly when) and I got frustrated a lot by the tablet so I just packed it up in the original box and now it's downstairs in my basement LOL
Click to expand...
Click to collapse
There are different reasons for the touch screen not to work, example:
The battery got overheated and trapped air, causing to bloat and apply pressure on the screen.
It can be dirty inside (dust) some cleaning could help.
The connector came loose.
For a hardware issue the only way to trouble shoot it is to open it and do a detail inspection. If the module for the touch screen is not working, find another Tablet 16g or 32g will work and swap the screen.