nexusone pvt ship s-on
hboot-0.35.0017
microp-0b15
touch panel -fail
radio-5.08.00.04
Oct 12 2010, 14:33:16
PURCHASED:
Purchased in USA officially 2 years back, have also used in India with GSM sim, have never unlocked and never rooted.
May have ignored some app updates as nexus one has low memory.
CONDITION:
2 months back touch screen started being unresponsive at times. Slight water had happened, at which time phone was kept off and dried. Screen looks great, glass not broken, just non responsive now to touch. When it happened initially, it was resolved by draining battery and recharging to 100. Dunno if apps and battery were messing around, or if moisture was drying from the phone, or different charging ways. But now it's a non responsive to touch. Power, Volume and trackball are fine.
Attempted all combinations of following things:
-Clear Storage, Clear cache, Factory Reset.
-They lead to Touch screen to begin like in fresh android install. But can't touch. Trackball can go over Emergency Call and Language 2 buttons.
-Recovery Options:
update.zip from 2 sd cards 4GB original and 16GB being used on the phone. It fails at /tmp/sideload/package.zip (Status 7)
-Phone connects to 3G and Phone network(with reset as well as 16gb sdcard software being used), and can see incoming calls but can't answer them as screen does not respond to touch.
FROM HTC:
HTC India said since this phone was not sold officially in India, they are not authorized to say anything, not even what touch panel fail means. Although HTC says Global Service. But I'll stick to the tech part.
Looking into:
-Touch Panel purchase and install
-somehow open up till the touch panel and clean those points and see if anything got loose.
:good:
Regards.
So folks, what da ya expect? Is this a tinye99 or not?
race55 said:
So folks, what da ya expect? Is this a tinye99 or not?
Click to expand...
Click to collapse
nooo. surely not. he seems to be from INDIA n his problem seems to be genuine.
Sent from my Nexus One using Tapatalk
Genuinity
n1newbie said:
nooo. surely not. he seems to be from INDIA n his problem seems to be genuine.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
A simple search indicated that some user had been banned in July on this website by tinye99 name. I don't know that person. Regarding honesty of problem: I think my uniqueness shines out in the question. The sequence of events and options tried are such that one can feel the troubleshooting and learning interest of this semi-tech lover.
This is my first post on this website, as usually all troubleshooting experienced earlier was resolved via active googling. As indicated, I had not installed the custom ROMS on this nexus one as wanted one straight working simple device in which I won't have to spend much time and efforts for ongoing maintenance. I helped out some friends tweaking their gadgets.
What was another part of heartbreak was that all the great things I loved doing with the smartphone was reduced when I moved to India. Got a harsh realization that Text to Speech navigation, Pandora, Google Voice, etc won't work in India. With my half-value of the phone and a silent pissed off feeling, I've been sailing on. Global usage, global service, all myths sometimes.
And many layman technicians around me may not know if there's some easy fix. I don't want to end up spending a huge amount on replacing the LCD/touch panel for this 2 year old (but great) phone. In tech, it's best to use engineering, problem solving and trials to reach accurate solutions.
I hope this convinces all to further believe that this is a genuine case, and also that I have done troubleshooting to my best abilities.
Thank you for your time.
Regards.
race55 said:
So folks, what da ya expect? Is this a tinye99 or not?
Click to expand...
Click to collapse
Please don't go too hard on any member Let's focus on enjoying the desserts (i.e., ICS and JB)
neo.123 said:
A simple search indicated that some user had been banned in July on this website by tinye99 name. I don't know that person. Regarding honesty of problem: I think my uniqueness shines out in the question. The sequence of events and options tried are such that one can feel the troubleshooting and learning interest of this semi-tech lover.
This is my first post on this website, as usually all troubleshooting experienced earlier was resolved via active googling. As indicated, I had not installed the custom ROMS on this nexus one as wanted one straight working simple device in which I won't have to spend much time and efforts for ongoing maintenance. I helped out some friends tweaking their gadgets.
What was another part of heartbreak was that all the great things I loved doing with the smartphone was reduced when I moved to India. Got a harsh realization that Text to Speech navigation, Pandora, Google Voice, etc won't work in India. With my half-value of the phone and a silent pissed off feeling, I've been sailing on. Global usage, global service, all myths sometimes.
And many layman technicians around me may not know if there's some easy fix. I don't want to end up spending a huge amount on replacing the LCD/touch panel for this 2 year old (but great) phone. In tech, it's best to use engineering, problem solving and trials to reach accurate solutions.
I hope this convinces all to further believe that this is a genuine case, and also that I have done troubleshooting to my best abilities.
Thank you for your time.
Regards.
Click to expand...
Click to collapse
Well, tinye99 is a banned member that keeps on creating accounts every time to send more wierd questions, and this was your first post, so i was just wondering.
neo.123 said:
nexusone pvt ship s-on
hboot-0.35.0017
microp-0b15
touch panel -fail
radio-5.08.00.04
Oct 12 2010, 14:33:16
PURCHASED:
Purchased in USA officially 2 years back, have also used in India with GSM sim, have never unlocked and never rooted.
May have ignored some app updates as nexus one has low memory.
CONDITION:
2 months back touch screen started being unresponsive at times. Slight water had happened, at which time phone was kept off and dried. Screen looks great, glass not broken, just non responsive now to touch. When it happened initially, it was resolved by draining battery and recharging to 100. Dunno if apps and battery were messing around, or if moisture was drying from the phone, or different charging ways. But now it's a non responsive to touch. Power, Volume and trackball are fine.
Attempted all combinations of following things:
-Clear Storage, Clear cache, Factory Reset.
-They lead to Touch screen to begin like in fresh android install. But can't touch. Trackball can go over Emergency Call and Language 2 buttons.
-Recovery Options:
update.zip from 2 sd cards 4GB original and 16GB being used on the phone. It fails at /tmp/sideload/package.zip (Status 7)
-Phone connects to 3G and Phone network(with reset as well as 16gb sdcard software being used), and can see incoming calls but can't answer them as screen does not respond to touch.
FROM HTC:
HTC India said since this phone was not sold officially in India, they are not authorized to say anything, not even what touch panel fail means. Although HTC says Global Service. But I'll stick to the tech part.
Looking into:
-Touch Panel purchase and install
-somehow open up till the touch panel and clean those points and see if anything got loose.
:good:
Regards.
Click to expand...
Click to collapse
The touch panel on this phone was an epic fail in the first place, you might want to try and reflash the Bootloader its risky, but you should try it unlock the bootloader flash a recovery using fastboot then flash Cyanogen Mod 7.2, assuming it has USB debugging enabled by default, and flash black rose, its probably the most fail safe method I've come across to flash a boot loader
Sent from my Nexus One using xda app-developers app
touch panel -fail
Facing the Same Problem after my phone fell into the water.
After it fell into the water, it was working fine for a couple of minutes until i removed the battery to dry it up.
then when I switched back on, the screen is getting stuck at the Bootloader screen, with no option selectable as the volume rocker does not seem to be working.
Opened up the phone, saw water had seeped in...to the part which is behind the battery compartment and could be the back of the touch screen panel..(thing with 8-10 large contact points)..
neo123 : what did you do? were you able to solve your problem?
neo.123 said:
nexusone pvt ship s-on
hboot-0.35.0017
microp-0b15
touch panel -fail
radio-5.08.00.04
Oct 12 2010, 14:33:16
PURCHASED:
Purchased in USA officially 2 years back, have also used in India with GSM sim, have never unlocked and never rooted.
May have ignored some app updates as nexus one has low memory.
CONDITION:
2 months back touch screen started being unresponsive at times. Slight water had happened, at which time phone was kept off and dried. Screen looks great, glass not broken, just non responsive now to touch. When it happened initially, it was resolved by draining battery and recharging to 100. Dunno if apps and battery were messing around, or if moisture was drying from the phone, or different charging ways. But now it's a non responsive to touch. Power, Volume and trackball are fine.
Attempted all combinations of following things:
-Clear Storage, Clear cache, Factory Reset.
-They lead to Touch screen to begin like in fresh android install. But can't touch. Trackball can go over Emergency Call and Language 2 buttons.
-Recovery Options:
update.zip from 2 sd cards 4GB original and 16GB being used on the phone. It fails at /tmp/sideload/package.zip (Status 7)
-Phone connects to 3G and Phone network(with reset as well as 16gb sdcard software being used), and can see incoming calls but can't answer them as screen does not respond to touch.
FROM HTC:
HTC India said since this phone was not sold officially in India, they are not authorized to say anything, not even what touch panel fail means. Although HTC says Global Service. But I'll stick to the tech part.
Looking into:
-Touch Panel purchase and install
-somehow open up till the touch panel and clean those points and see if anything got loose.
:good:
Regards.
Click to expand...
Click to collapse
If the problem occurred as a result of water damage - then open the phone and clean the water residue. If you can't - then send it to a lab for repairs.
Related
I have a UK supplied Touch HD from Orange and it`s going crazy!
Problem 1:
Backlight switches off without warning, touchscreen still responds but obviously you can`t see anything! Multiple hard resets will eventually coax the backlight to wake up, but the delay between power button pressed and the "first buzz" of life is around 20-30 seconds. Started happening when it was about 2 months old. Initially it was infrequent and I put it down to an installed software problem, but now every few hours. Other symptoms include the charging light failing when the backlight fails and there is usually an increase in heat around the case. Strangely however when I use it as a sat-nav and it is permanently charging the backlight never fails. I have tried a new battery, desktop charger, turned off fast-sleep, autolock, light sensor, full reset and removal of all my software and it still does it. Sometimes its OK for 5 days, other times it goes "dark" after 10 minutes.
All ROMs updated to latest versions. NB This started happening with the original Orange installed ROMS
My original solution to the problem was to run bootloader which forced the backlight on, but the long delay between on/off and start means this doesn`t work anymore.
Problem 2:
Screen display appears inverted and mirrored after pressing power button during operation. This is an infrequent problem but may be connected.
I live in Thailand now. HTC Thailand will no doubt take it and charge me $250 for a new motherboard whether it needs one or not. I can`t easily return it to the UK and I just hope somebody somewhere has some ideas?!?
I was just talking to another user with completely bizarre issues. What you are experiencing is totally abnormal. Just to make sure it's not a software issue- what SPL version shows up in your bootloader? Also, what rom are you currently running?
Please read next post
Please read next post
** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.
jamesmclean said:
** OOPS my typing brain isn`t working today **
Thanks for replying. I had upgraded to:
2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship
with soft uspl but last night I reinstalled the original Orange ROM, effectively factory fresh. (The HTC April update won`t install natively on the Orange variant of the phone) and the thing stayed on all night and didn`t go dark. However, this morning when I got the reply, I turned off the phone to get to bootloader and it took 3 battery removals to activate the backlight.
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
Any suggestions would be gratefully received.
Click to expand...
Click to collapse
So is the phone working properly again with the factory Orange rom? All I can tell you is that if you want to run the 2009_RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship rom you must have a base SPL of 1.54.0000. Even if you use USPL to flash the rom to bypass CID-locking you still need to upgrade your SPL because the new 1.56+ roms are not compatible with an SPL version less than 1.54.0000. Read the guide in my signature for more information.
I see cRaCKwHoRe is on your case, so your in safe hands. I'll leave it to him.
One suggestion though. Instead of creating new posts and saying 'Read Next Post', why not just edit your first post and state 'EDIT' or 'Update' with new information below. This way thread remains short and easy to follow
Just an idea mate!!
Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.
jamesmclean said:
Hello again. As I said in the previous post, reset to check the ROM version caused it to happen again. 3 Attempts to wake it up this morning. This afternoon another spontaneous backlight failure. I started to wonder if it could be connected to something on the flash card. So I took that out and it has behaved since then. But this doesn`t mean problem solved as it had worked ok for the 5 previous days with the WWE 1.56 ROMS.
Also, HARDSPL is being identified as a Trojan "heur" with Bitdefender.
Click to expand...
Click to collapse
Most virus scanners show a false positive that USPL and HSPL are trojans or viruses. This is based on heuristics and how these utilities work. They are tried and tested and are most definitely safe.
And again I stress that you cannot run a 1.56+ rom on an SPL version below 1.54.0000. Since you are running SPL 1.14.0000 this is why you are having such issues. You need to flash a newer SPL version!
After the hardspl back to original Orange ROMS:
Anyways SPL is 1.14.0000
R 1.09.25.14
G 52.49a.24.26u
D 1.14.22273
I had 2 dark events. I wondered if there could be a problem with the memory card, so I took it out. My reasoning being, after it goes dark and is reset, something was causing it to wait 30 seconds before "smart mobility" and/or buzz (if the screens still alive). When my PC does that its usually because there`s a memory card or external hard drive confusing it. Took out the card and it was OK all night. Formatted the card this morning and had no problems all day.This is a guess, I am an idiot! But the memory card is the only ongoing part of my phone; internal storage and ROMs has been cleared or upgraded every month.I dont doubt my feeble attempts to upgrade to 1.56 and bypass HTC`s no upgrades for Orange handsets policy may have been a significant contributory factor. Interestingly, Orange are actively discouraging purchase of the HD, they have had too many problems with their handsets.
Going to keep the phone empty for a few days, no software, no sat-nav and see if I have any more events. Then I think will read your HARDSPL instructions far more carefully and retry the ROM upgrade. Excellent work by the way!
The odd thing about this telephone (apart from the inversion and mirrored display problem, which still occurs) is that following the nuclear option of total clearance and ROM upgrade/downgrade it will behave for an number of days and then the backlight dies again. It could still be hardware!
Going to keep my eye on things for a few days.
But if anyone else has had these problems with their HD or Orange handset, please tell! Maybe you aren`t crazy! To help this is a list of symptoms:
Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Thanks!
Looks like a SPL problem only. It is responsible for the boot events and mismatched display drivers between SPL and the ROM most likely did it. Anyway interested in knowing updates once U flash a new SPL 1.54. and ROM..
Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!
jamesmclean said:
Problems not resolved. Backlight dead again today. Multiple failures 10 minute interval. Totally fed up with HTC products. My previous HTC phone MDA Vario 2/Tytn/Hermes had to be replaced 4 times under warranty and until 2 weeks ago I used it when Touch HD died, now it has completely died as well.
Even in its "as-supplied" by Orange configuration the Touch HD won`t work now. May be I will try one more attempt at ROM upgrade. In the meantime I`ve just bought a cheapo Samsung sgh i200 for basic pocket PC functionality and just because it doesn`t say HTC on it!
Windows mobile is great. Massive software library and great to customize. But in my experience HTC make lousy unreliable products!
Click to expand...
Click to collapse
That's really unfortunate. Seems you have bad luck, consistently
Most people really like HTC devices. They do actually make some pretty decent stuff. Seems you've just gotten rotten luck.
Taken it back up to 1.56 with Hardspl as suggested. Installed Dutty 3.4. And it worked... For one night! Dead again today. I think now it is a hardware fault. So I suppose she`s off back to HTC and I will have to pay some money.
I have been very unlucky with HTC products. I said before I had to have 4 HTC Hermes, thought it would be interesting to tell what was wrong with them:
1. Orange SPV3100 WM5. First generation Hermes 100, hopeless wifi, buggy, returned to store and refund.
2. MDA Vario 2. WM5 Upgraded radio version, better wifi. Decided it didn`t like being a telephone anymore and the radio died after 3 months. Returned to store.
3. MDA Vario 2. WM5 Factory replacement. Dead memory card reader, didn`t make it out of the store when I went to collect.
4. MDA Vario 2 WM6 (Hermes 300). Working wifi, a much better operating system. A real telephone. Lasted 18 months! 2 weeks ago, complete power failure for no specific reason. Won`t charge or do anything now.
But before Nokia and iPhone customers get too smug. I also had an iphone when they were first released in 2007 (1.02) and that was a bug infested piece of junk as well. Got stolen in Bangkok. I really do miss having to reinstall the OS every 2 weeks! And my brother`s Nokia N95 has spent more time with Nokia than with him. 8 visits to Nokia care.
And now I have a broken Touch HD, probably with a power supply issue!
All these phones have one thing in common. They were (with the exception of the Hermes 300) first generation examples. And just before you rush out and pay big bucks for the latest telephone from HTC or whoever... Think, was this phone ready for release? Or was it just rushed out to keep the shareholders happy?
Think about it...
Hell! finally I found someone with the same problems. But I have bought it just some days ago!! The only thing I have done since then: installing tomtom on my sd-card and setting this gps-signal thing to the value 3000.
when I bought it i tried to run it in the store: after turning on, black screen but still vibration when i pressed some button, so it must have been on. Then it suddenly worked, installed the system, everything perfect. yesterday i installed tomtom, today it probably "died" around 20 times. everything the same like already described, screen messed up, after turning on vibration after 30 seconds, god!
is there anything i can do? i just bought that thing
Spontaneous backlight failure but screen and phone responding
Simultaneous charging light failure
Delayed reboot 20-30 seconds before first buzz
Continued backlight failure requiring multiple hard resets to resolve
Weak vibration during failed backlight reboot
Inverted and mirrored screen at boot or after wake-up
Click to expand...
Click to collapse
Sounds like you have the exact same problem as my HD: inverted screen, screen blank but still functioning etc...
http://forum.xda-developers.com/showthread.php?t=520781
I am waiting for mine to happen more frequently before sending it away for service. Otherwise they will just return it if they can't reproduce the problem.
Pretty sure it is a hardware problem. I am in Australia and have the original stock ROM.
We may be onto a new fault here. Just noticed 2 more threads with the same screen issues. My phone has been OK for a few days, but today screen won`t wake up at all. Hooked it up to Pocket Controller Pro and it`s reporting a "microp version mismatch 0" in its dark state. Been checking on other websites and this seems to have been a problem with Touch Diamond previously. There doesn`t seem to be an update for microp firmware. One user tracked it down to a loose connection between screen and motherboard. I don`t know! I just wish it would work!
Any suggestions for MICROP issue?
Currently running Dutty 3.4 with 1.56 Olinex. But this has been a problem long before this ROM version.
Fallen Spartan told me this:
"Have you tried going to Start > Settings > All Settings > System > Power > Advanced and making sure device isn't set to turn off after a period of time?"
Until now my phone works without problems, I will report again after some days
Yup, tried that one. Doesn`t work. You will notice after you end a call, the screen will be dim. This is the warning of imminent backlight failure. It is not power management dependent. My problems with the phone started in Feb. Initially intermittent. Now constantly.
Sometimes the thing will work for a few days for no reason. Only way to guarantee no failure is permanent USB power. Pull out the USB and watch it die, instantly! That`s with the original or the new battery.
New motherboard may be the only solution. But it is worth noting that when I had problems with my Hermes and it had to go back to HTC 3 times, each time a new phone was sent. On the service report "New motherboard" was reported. The guy in the T-mobile shop told me they`re too expensive to repair so it`s easier giving you a new one. They still hold onto the old one for 3 weeks though!
Might try to repair the Touch HD, I still have my Samsung SGH. (It`s very slow!) but I think I will wait for ASUS or Toshiba phones with snapdragon processors. Had enough of HTC and don`t want another iphone.
This is a hardware issue. No if's, and's or but's. It is caused by a disconnection between the screen and the motherboard. A faulty motherboard or a loose / broken connector is the usual culprit. I would say 7 out of 10 times it is due to a loose connector. It is a poor design to begin with and after being dropped or roughed up enough it tends to break or get loose. HTC typically just replaces the motherboard in a warranty repair situation.
If you are lucky and just have a loose connector and are comfortable with opening up the device yourself, you can disassemble the device and re-connect or re-solder the 2 port connector that connects the motherboard with the screen. Of course this will "void" your warranty so I wouldn't recommend doing this unless you are comfortable working on micro-electronics. If your case is the type where it is intermittent and it works sometimes and then sometimes not, then you have a loose connection and it just needs to be reconnected or re-soldered.
I have seen and fixed a couple of these now.
Hi,
I have recently purchased my HD2 and its been a couple of months now since I'm utilizing it. Barely exploring my phone features, it hangs 20 times in view of the following encountered predicaments :-
1) Receiving 2 simultaneous SMS
2) Receiving an MMS
3) Pressing on any of the keys on the phone whenever receiving an SMS
Well, the list goes on and on. So, in resolving this issue, SIS (Malaysia) had agreed to change a new phone for me. And so they did. Tested it on the spot and everything was working fine, but just after a few days later, the problem reoccur itself again. This time, the entire phone hangs up. No keys can be activated, neither the phone can be turned on.
Firstly, its a brand new phone, so this kinda problem should not arise. Secondly, its no doubt troublesome to flip the back cover and press the tiny red button to perform a soft reset. Why in the darn first place the soft reset button isn't placed outside ? (just liky my old TYTN II)
So I have read a couple of forums with regards to this matter and came upon two conclusions in the end. One, the Manila.exe is the main culprit towards the hanging of the device and two, the HTC Sense application program has a flaw in between. Well, there's a temporary workaround though (that is if you do not want to flip the back cover over and over again), which is to leave the phone idle for 48 hours, let the battery drain itself off and then recharge back the phone again.
48 hours is a long time to wait though, and as a professional worker in my line of work, I really do not have that much of an ample time to linger around waiting for it to run out of juice. I'm totally very much dissapointed with the purchasement of the HTC HD2 as not only the technicians at the SIS (Malaysia) could not get to reproduce my predicaments, they cant even get to solve the hanging issue which I'd reckon, that's what I've been spending most of my time on my new phone (rather than to explore what is has to offer)
Is there a work around to the HTC Sense / Manila.exe problem ? Other suggestions would be to turn off the HTC Sense, but you know what ? Turning off the HTC Sense will be something like buying an Aston and driving it at 40kpmh all the way till the south of France !!! The phone's interface will be dull, and not to mentioned, it will be more a less pictured like my old TYTN II
I do not really have such problems for the HTC TYTN II though, not even one hang moment. Please XDA developers / experts, I'm indeed begging for a solution in resolving this reoccuring problem that somehow not only it will tarnish the brand HTC, it will also loose faith of the end consumers in the market.
why don't you ask SIS to change the phone again?
Just want to say one thing ... "Stock ROM's Suck" , hate to be that blunt but the stock ROMs they put on this beautiful hardware just seem to be time bombs, waiting to explode when you get them home ...
Should flash that sucker!!
To dan138zig
Well, that was my last resort to them, in order to solve it once and for all. I've been travelling to SIS to and fro for 4 times and yet the problem is still left unresolved. They've even tested it in their environment and it works fine (for the 1st two visits). But somehow, they manage to simulate the issue and they replaced the chipboard.
Now, replacing the chipboard was to the previous original phone, though even after the replacement, it still didnt solve the problem. So ding dong here and there, and after several "consultations" with their higher level managment, they agreed to change a new phone for me, off the hook (not undergoing formal procedures, whereby I'll have to wait for another two weeks)
So, getting a brand new phone I'd reckon my miseries will be resolved, but then the hanging problem reoccur itself today again. It seems that the HTC Sense is the main culprit though, after reading a few forums off the Net. And for a "premanent" solution (that is if HTC does not come out with any ROM / fixes / enchancements), I've gotta turn off the HTC Sense feature.
Well, buying a phone that cost 2K plus had already put a large damage in my wallet, now having to face this consequences after the purchasement is a real icing on the cake. What do you think ? If you're in my shoes, what would you do ?
To watcher64
I totally couldnt agree with you more. In my view, they should just have throw the Win OS away and put in the Andriod version of it. Its always windows version mobile phones that are giving the most headache to me when it comes to utilizing it.
http://www.htc.com/sea/supportdownloadlist.aspx?p_id=297&act=sd&cat=all
Have you tried getting a new SIM? Sounds like the problem only happens when its talking to the network, and as you've had 2 handsets, i'd give a SIM change a go.
On the plus side........... at least you get 48hrs battery life.......
Not much use though if your phone doesnt work I suppose.....
rp-x1 said:
Have you tried getting a new SIM? Sounds like the problem only happens when its talking to the network, and as you've had 2 handsets, i'd give a SIM change a go.
Click to expand...
Click to collapse
Well, my SIM's working perfectly fine though, it does not give me any form of problem with my old TYTN II neither with other HTC devices I've checked with a few friends of mine. I do really suspect its the Sense that's the real culprit in the hanging of the device. Just really hope that they clear up this predicament with a new release of the ROM
conantroutman said:
On the plus side........... at least you get 48hrs battery life.......
Not much use though if your phone doesnt work I suppose.....
Click to expand...
Click to collapse
haha, forty eight hours of baterry life ? well, I wouldn't bet on it. Have tried using it extensively and even before it reaches sunset, the battery is out. And guess what ? It's a brand new battery.
The phone's terrific, but sadly, the battery isnt. Its just like you are viewing a beautiful girl from bottom up till the next and the next thing you know it, viewing her face just makes you wanna vomit over and over again
So that's how I could sum up the HD2 as a whole. Most comparison commentators out there did place the HD2 side by side with the IPhone 3Gs. Both eventually also will end up running out of juice in 48 hours when you're performing your day to day call basis
webjunky said:
http://www.htc.com/sea/supportdownloadlist.aspx?p_id=297&act=sd&cat=all
Click to expand...
Click to collapse
The HTC Support and Releases still does not solve the problem, mate. Its something that HTC R&D as well as the QA team needs to sit down and extensively test the entire device from bottoms up till all forms of problem is resolved thereafter.
steven.hum said:
To watcher64
I totally couldnt agree with you more. In my view, they should just have throw the Win OS away and put in the Andriod version of it. Its always windows version mobile phones that are giving the most headache to me when it comes to utilizing it.
Click to expand...
Click to collapse
hmm, well you did not get what I meant, but that is ok .. I meant the version of the roms suck .. I like WinMo, personally I think Android with is BigBrother Back door is just as bad as the Iphone ...
Hope any of you guys can help me on this. Last night my Leo's screen went totally unresponsive.
Could not get past the screen lock. Removed the battery, rebboted ... could not get the PIN code in.
I had seen this already two nights ago, but it got away once I moved in an area where I could get a reasonable signal (ultra-crappy where I am now on vacation).
Now Im'm beginning to think the signal thing was just a coincidence and that the problem is way more serious.
In total despair, I even tried a hard reset. To no avail.
Phone boots up fine. I can even sync to it (so yes, I can get to the registry). But since the only control is the screen ... not really a lot I can do with it.
I need to be in touch for work and I badly need the voice and internet connectivity (right now I'm using the wife's phone ...).
Any ideas besides getting an RMA from HTC?
Thanks a lot in advance.
Update: spoke with HTC support.
It looks like the issue is somehow triggered by the lock screen.
As suggested by HTC, I flashed again the 1.66 ROM upgrade and everything ran smoothly until the phone went in standby the first time.
Then, I was (and still am) unable to unlock the screen. And if I soft reset screen is unresposnsive again.
Right now I can just receive calls (I removed the PIN code from the SIM temporarily).
HTC told me to send it in for repair, but everything in Italy is closed until Aug 23rd and the only option I have is to ship it at my own expense to the UK and back (HTC will collect and deliver free of charge only within the same country).
Total bill some 100+ Euro plus driving 100 KM or so to the nearest courier collection point. A nightmare.
What really troubles me is that the problem surfaces only once the screen locks.
On one hand I follow HTC's support that if flashing 1.66 did not cure the issue, it cannot be software.
On the other hand, if it is indeed hardware, how come it freezes only after the first lock screen? Lock/unlock is a software thing. Screen should behave exactly the same way before or after the lock - shouldn't it?
Anyone here seen/heard of anything like this?
wow, gotta love those "closed for the summer" euro vacations.
If you reinstall the ROM, then why not disable the lockscreen until you can get it fixed?
You can install BSB tweaks and that has an option to disable autolock.
i had the same exact problem; it started freezing only on the lock screen then got worse and started freezing at random times while in use. I finally broke down and sent it in to HTC to check it out. I'm waiting to hear back with there diagnosis and I will pass along whatever they tell me.
Good to know the problem has come up somewhere else (if you're the only one you are most likely to hear it's your fault before they replace the most expensive component in the phone). Where are you located slimster?
How long have you been waiting for? HTC policy should be 7-10 working days from when they receive the phone at the lab (so they told me and I remember reading it somewehere here in xda too).
Hi everyone! Unfortunately, my run with my T-Mobile G2 appears to be nearing it's end.. I've had this phone since November of last year, so fortunately for me, I'm still within the 1-yr warranty. I couldn't find a legit answer on the forum so far so hopefully someone will have the information I need to know now.
Lately, my phone has been getting crazy. Sometimes it would start pressing random things by itself. Apps would start by itself, things would type by itself, etc, etc. Then, at times certain areas of my screen wouldn't work at all, most noticeably the "y," "b," and "h" on my keyboards. And this doesn't matter whether I'm using the stock Gingerbread keyboard or Swype.
To answer any questions, yes I am rooted and I have been running CM 7.0.2. I tried to flash 7.0.3 to see if that would correct my issue but it didn't. I also tried to reset the phone via Privacy within the Android UI and via Recovery, both with no avail.
My question to y'all is how can I fix this if at all? If this problem is not fixable, can someone provide me with the MOST SIMPLE guide as to how to unroot and restore my original T-Mobile stock ROM if necessary for me to send it to claim warranty.. Finally, if I resorted to claiming warranty, does anyone know if T-Mobile will be sending me a refurb G2 or a new one or a completely different one?? Thanks ... This is EXTREMELY UNFORTUNATE.
it happens to me plenty. keep the scroll pad on the side from changing angles in direct light or it goes nuts. if theres any water on the screen at all touch commands work funny. its errors in the optical touchpad and cpacitive screen technology, not the;phone itself.
edit: im stock if youre wondering
It happens even in the dark though. I think its problem with the screen.
Any word on this? the same thing is happening to my phone.
Hui,
I was also having this problem for some time and was reallythinking of replacing the phone until I finally got rid of this last week. To start with I think this is a software issue but I'm still not sure what sw is causing this. n order to fix it I had to install the rom again from scratch and did not restore anything from google. Because independent from whatever ROM I installed the issue appeared soon after I set up the phone. So if you wnt to give it try, do a clean ROM install or factory reset to your phone and then while setting up your device uncheck the option to backup and restore settings to your google account. I know that setting up everything manually does not sound great but it's better than the crazy touch screen.
Digitizer issues
Sent from my HTC Vision using XDA App
Digitizer issues, T-Mobile just replaced my original release date G2 because of it.
They will send you a refurbished model and you have to send yours back in within 7 days or they bill you $400 I believe.
Sent from my HTC Vision using XDA App
I had serious digitizer issues last month and thought for sure that my G2 was finished. Come to find out I had gotten some oil on my phone, probably from answering a text or phone call while eating at work. I took it out of its case and completely cleaned it with a cloth dampened with peroxide...not soaked just damp, and now my phone is back to normal. Give that a try and rule that out first before you replace the digitizer or phone. Make sure you clean the inside and outside of the case/skin if you have one too.
I finally figured mine out. I guess the digitizer is really really sensitive to moisture. I usually take my phone into the bathroom with me when I shower in the morning, once I stopped doing that and gave the phone some time to dry out (in a dessicant container, but rice would work just as well) my screen is back to normal. I guess the steam from the shower was enough to bring up some bugs.
UPDATE:
It seems the problem I have is ghost typing. Based on FourPointedFreak suggestion, I activated the Show Touches option in the Developer Options menu, and now I see ghost presses on the touchscreen, always in the same place, about 1.5 inches from the bottom and 0.5 inches from the left. If I try pressing with my finger in the same spot when the mark shows up, it slides down before I can even get to the screen. If googled it, and it's been reported on some Android phones and ipads, but not on the S4, and there is no agreement if it is hardware or software.
If you've dealt with something like this before, even with a different device, your input would be most welcome. I'm planning to change ROM tomorrow or early next week, and see if the problem continues. And clean my screen with a soapy moist towel, so far I've only used a cloth for glasses to clean it.
I'm really hoping it's a software issue as I don't want to do a warranty replacement, I'd be most probably get a device on MF3. But if it is hardware I'd rather have that than a faulty device. I got it refurbished as a replacement for an Xperia Ion, and I only have one more month left of warranty.
Again, any input especially from past experiences would be greatly appreciated.
-----------------------------------------------------------------------------------------------
LAST UPDATE:
It seems the problem is hardware, as the false inputs in the screen happen also in TWRP while trying to flash the new ROM. I guess any mod can close this thread now.
josemald said:
Hi everybody, in the last week I've had issues with the display. First it started like going up and down in scroll menus, like if I was scrolling up and down around a certain position very fast. In the last two days, after that happens, the touchscreen gets unresponsive (it didn't use to happen before), including the menu and back buttons, only the hardware buttons work. Home screen button works fine, but I can't do anything in the screen. The only solution is to turn the screen off, enter PIN, and then it starts working. A couple of times the screen keyboard started acting weird when I was typing, for example if I wanted to move the cursor in an email the keyboard interpreted as if I was pressing a key, which was way below. Again turning the screen off and on solved it.
I'm using Mint Jelly ROM, which has been stable for almost two months. I recently updated the modem to MF3, but only the modem and not the firmware. The screen issues were happening before that, it just got worse today. I also tried freezing Samsung WatchOn, which started acting out by showing itself on the notification panel even though I had selected the option for it to not appear, and I uninstalled the Software Update app (used for OTA updates) using Titanium Pro, since I saw it in the list of running processes. The problem still continues.
Is it possible that this is a hardware issue? I have 1 more month of the warranty (I got it as a warranty replacement for a Sony Xperia, so it wasn't new). If I don't need to send it back I would prefer not to, since the one I'd get would probably come locked with MF3 firmware. If you have any ideas on how to debug this, I would appreciate the input. I haven't installed any new app recently.
Click to expand...
Click to collapse
Well, you're definitely smart for doing your research before just pulling the warranty card.
I would do some testing and research with the phone to figure out what the cause is. It doesn't sound like something that can be just 'debugged'.
Go into your developer options on the phone and enable a few things.
To get developer options, go to System Settings > More > About Device and tap on "Build Number" until it says you've enabled it.
Then go into Developer Options (Above About Device) and under input, select both options "Show Touches" and "Show Pointer Location". Then under Monitoring, enable "Enable Traces" for anything applicable to what you're having problems with.
Some of these settings may be annoying, but continue to use the phone as you would. See if it's adding and doing things you're not, this would show clear signs of a malfunction with the firmware. Check for dead pixels too. Sometimes a dead pixel can cause things like you're dealing with. Where something is selected on the screen much lower than where you pressed and variations of that.
Also, have you tried reflashing your ROM to see if that makes a difference?
FourPointedFreak said:
Well, you're definitely smart for doing your research before just pulling the warranty card.
I would do some testing and research with the phone to figure out what the cause is. It doesn't sound like something that can be just 'debugged'.
Go into your developer options on the phone and enable a few things.
To get developer options, go to System Settings > More > About Device and tap on "Build Number" until it says you've enabled it.
Then go into Developer Options (Above About Device) and under input, select both options "Show Touches" and "Show Pointer Location". Then under Monitoring, enable "Enable Traces" for anything applicable to what you're having problems with.
Some of these settings may be annoying, but continue to use the phone as you would. See if it's adding and doing things you're not, this would show clear signs of a malfunction with the firmware. Check for dead pixels too. Sometimes a dead pixel can cause things like you're dealing with. Where something is selected on the screen much lower than where you pressed and variations of that.
Also, have you tried reflashing your ROM to see if that makes a difference?
Click to expand...
Click to collapse
Thanks for the suggestions!
Do you think it´s possible that the problem was caused by a dirty screen? I know it sounds a bit insane, but yesterday I wiped off my screen to clear dust and smudges, and since that I haven´t had any issues with the phone. This is the third touch screen device I had, I've never seen something like this, but also the S4 screen is a lot more sensitive than my previous devices. Could it be that too much dust and grease made the phone interpret that there was some input?
josemald said:
Thanks for the suggestions!
Do you think it´s possible that the problem was caused by a dirty screen? I know it sounds a bit insane, but yesterday I wiped off my screen to clear dust and smudges, and since that I haven´t had any issues with the phone. This is the third touch screen device I had, I've never seen something like this, but also the S4 screen is a lot more sensitive than my previous devices. Could it be that too much dust and grease made the phone interpret that there was some input?
Click to expand...
Click to collapse
I would think it's 'possible' but it would have to be thick and really caked on there to make a difference. That may have just been a coincidence of timing with your issue. But perhaps it is.
Maybe go buy a cheap screen protector to help with finger prints and dirt and see if it gets better?
If it persists, I would factory wipe and install the stock ROM through Odin. Use it a bit completely stock and see if the screen works. If the issue continues then its an hardware problem and i would take a video and e-mail Samsung about it with the video. I've actually had this problem before and that's because my phone was cold as hell. Doing a lot of benchmarks so i put it in the freezer (I would NOT recommend that) and my screen started acting up and it pressed random things like yours.
crzykiller said:
If it persists, I would factory wipe and install the stock ROM through Odin. Use it a bit completely stock and see if the screen works. If the issue continues then its an hardware problem and i would take a video and e-mail Samsung about it with the video. I've actually had this problem before and that's because my phone was cold as hell. Doing a lot of benchmarks so i put it in the freezer (I would NOT recommend that) and my screen started acting up and it pressed random things like yours.
Click to expand...
Click to collapse
That's a good idea. Just make sure you flash the custom ROM appropriately as not to brick your device.
Sent from my AT&T SAMSUNG-SGH-I337 via XDA Premium Mobile App
FourPointedFreak said:
That's a good idea. Just make sure you flash the custom ROM appropriately as not to brick your device.
Sent from my AT&T SAMSUNG-SGH-I337 via XDA Premium Mobile App
Click to expand...
Click to collapse
It seems the problem I have is ghost typing. Based on FourPointedFreak suggestion, I activated the Show Touches option in the Developer Options menu, and now I see ghost presses on the touchscreen, always in the same place, about 1.5 inches from the bottom and 0.5 inches from the left. If I try pressing with my finger in the same spot when the mark shows up, it slides down before I can even get to the screen. If googled it, and it's been reported on some Android phones and ipads, but not on the S4, and there is no agreement if it is hardware or software.
If you've dealt with something like this before, even with a different device, your input would be most welcome. I'm planning to change ROM tomorrow or early next week, and see if the problem continues. And clean my screen with a soapy moist towel, so far I've only used a cloth for glasses to clean it.
I'm really hoping it's a software issue as I don't want to do a warranty replacement, I'd be most probably get a device on MF3. But if it is hardware I'd rather have that than a faulty device. I got it refurbished as a replacement for an Xperia Ion, and I only have one more month left of warranty.
Again, any input especially from past experiences would be greatly appreciated.
josemald said:
It seems the problem I have is ghost typing. Based on FourPointedFreak suggestion, I activated the Show Touches option in the Developer Options menu, and now I see ghost presses on the touchscreen, always in the same place, about 1.5 inches from the bottom and 0.5 inches from the left. If I try pressing with my finger in the same spot when the mark shows up, it slides down before I can even get to the screen. If googled it, and it's been reported on some Android phones and ipads, but not on the S4, and there is no agreement if it is hardware or software.
If you've dealt with something like this before, even with a different device, your input would be most welcome. I'm planning to change ROM tomorrow or early next week, and see if the problem continues. And clean my screen with a soapy moist towel, so far I've only used a cloth for glasses to clean it.
I'm really hoping it's a software issue as I don't want to do a warranty replacement, I'd be most probably get a device on MF3. But if it is hardware I'd rather have that than a faulty device. I got it refurbished as a replacement for an Xperia Ion, and I only have one more month left of warranty.
Again, any input especially from past experiences would be greatly appreciated.
Click to expand...
Click to collapse
Yeah, I have heard the term "ghost typing" before. I couldn't seem to find much information or help on the subject as I'm sure you noticed as well. To me, and many others on the internet - this doesn't seem software related to me. This would seemingly be an issue with the hardware. Maybe the screen itself, the data connectors for the screen's signals - could be all kinds of things.
If I were in your shoes and you really like the S4, i'd just take advantage of the month you have left on your warranty and get a new device. If, and they probably will, they supply you with a new(er) device with MF3 on it, it's not the end of the world. Mine got stuck with it - there are methods to root it even still.
To me, cleaning it just doesn't sound like it's a solution. I've worked for T-Mobile, AT&T and Verizon. Only twice had I seen an issue like this where you can attempt to press "E" and another key was hit in place of "E". We never found a fix - this occurred on demo phones so we related the issue to it having demo software.
The only other 'solution' or fix would be to replace to screen to see if it fixes. But since you have a warranty, for the trouble - i'd just get a new device.
FourPointedFreak said:
Yeah, I have heard the term "ghost typing" before. I couldn't seem to find much information or help on the subject as I'm sure you noticed as well. To me, and many others on the internet - this doesn't seem software related to me. This would seemingly be an issue with the hardware. Maybe the screen itself, the data connectors for the screen's signals - could be all kinds of things.
If I were in your shoes and you really like the S4, i'd just take advantage of the month you have left on your warranty and get a new device. If, and they probably will, they supply you with a new(er) device with MF3 on it, it's not the end of the world. Mine got stuck with it - there are methods to root it even still.
To me, cleaning it just doesn't sound like it's a solution. I've worked for T-Mobile, AT&T and Verizon. Only twice had I seen an issue like this where you can attempt to press "E" and another key was hit in place of "E". We never found a fix - this occurred on demo phones so we related the issue to it having demo software.
The only other 'solution' or fix would be to replace to screen to see if it fixes. But since you have a warranty, for the trouble - i'd just get a new device.
Click to expand...
Click to collapse
Thanks, that's what I'm going to do. It must be hardware related, since the problem also came while I was in TWRP after formatting the phone. I like the S4 but a locked down Android, not so much. If rooting is enough to be able to tether, I might ask for another S4, if not, might as well try to migrate to Windows Phone. It's ridiculous that we have to pay extra just to be able to use our limited data plans to navigate through a different device.
Again, thanks for your help!
josemald said:
Thanks, that's what I'm going to do. It must be hardware related, since the problem also came while I was in TWRP after formatting the phone. I like the S4 but a locked down Android, not so much. If rooting is enough to be able to tether, I might ask for another S4, if not, might as well try to migrate to Windows Phone. It's ridiculous that we have to pay extra just to be able to use our limited data plans to navigate through a different device.
Again, thanks for your help!
Click to expand...
Click to collapse
No problem - yeah there is definitely a way to root the MF3 build of the S4.
Since you mentioned it, my only note ***If apps are important to you, Windows Phone is a dangerous field. Many apps available for Android and iOS are not available on Windows Phone. I'd make sure the content you want is available before switching.
I can see why the carriers would charge additionally for tethering. If you can make an extra buck, do it. But it does suck. Especially when you have unlimited data and want to tether.
-Do some research on Windows Phone in case you're seriously considering switching. I wouldn't though