Screen alignment instability hardware caused? - MDA III, XDA III, PDA2k, 9090 General

Dear all!
My screen worked flawlessly for the first two months after purchase, but then it suddenly started to constantly lose its alignment, often several times a day.
Several posts in this forum indicates this as a hardware problem, others got their screens stable by flashing their ROMs.
Any input on this matter would be highly appreciated since I am up to flash my ROM to one of the packages baked by this forum (1.4 or WM5) to sort other problems....and such a flash would probably break my guarantee. If you indicate my screen problem is hardware related I will return my device and have the screen replaced before flashing it to something more decent!
Regards
QTEK 9090
ROM Version : 1.22.00 WWE
ROM Date : 10/22/04
Radio Version: 1.06.02
Ext Rom Vers: 1.22.741 WWE

If I were you I would get it replaced, it isnt fit for the purpose it is made for and as you say flashing wiill invalidate your warranty.

Thanks for your response “cruisin-thru” and yes unless I am convinced it’s a flash problem I will replace it before breaking my warranty. On the other hand, my company have replaced several blue angels and got the same problem back after a while on the replaced items.... perhaps the Swedish batch is faulty all over!
On PCs calibration problems is often caused by flash bios problems or faulty drivers.
I wonder if screen alignment problems are mentioned in any of the HTC fix lists (if they make such a lists public?) for later builds than mine?
The main reason for me (and probably for many of you...) to flash away my warranty is of course the unbelievable amount of software bugs in the original ROMs on such a super great device on which we have already spent well too much time and effort, and money on peripherals.
It's not always easy to differ hardware related problems from software related problems and I still believe screen alignment instability is the same kind/class of problem as uni-directional calls (no caller), Bluetooth range within decimetres, catastrophically bad sound quality for my callers and almost useless wifi due to several shortcomings.
But again if I can’t find any good references where flashing to 1.4 or WM5 solves the screen alignment instability, I will definitely send my device back.
Regards
I am definately willing to take a chance to flash my device to something more stable, the device is great I love the machine

Related

SPVM2000 no sound (response from Orange) help needed

Hi
Just got off the phone with Orange as the replacement phone they sent me also has the "no sound in call" bug (can not hear other party without soft reset)
They said, that as far as they are aware, there is no known fault with this Phone and no inherrent fault.
The Phone was supplied to me in working order and must have developed a fault after.
Their technicians are not aware of any known issues with "no sound in call" and the manufacturer is not aware of any issues with the SPVM2000.
I said itis well reported on this site, to which they said this is not an XDA it is a SPVM. so it is not relevant.
I said it is the same phone!!
I told them that I was surprised at their repsonse, but I would ask others to see if I am alone in having a Orange SPVM phone that about once a week needs a reset becuse the other party can not be heard.
Please help me. If you are another SPVM2000 user, that has suffered with this fault at any time, please reply, as I will then present them the information, that they can not deny.
Hi,
I have two SPV 2000 from Orange UK and *both* exhibit this problem with the ROM's they were shipped with (one had 1.40 the other 1.31). The one phone has been abandoned by it's user as it's just too unreliable, whilst my phone now has the Wizard WM5 port, and that does work OK (although WM5 has it's own problems).
As we all know this is the most common problem with the BA device - funny how Orange have never heard of it!
Yeah - this happens to me. It happens consistently when you turn bluetooth off. If you do a soft reset all works fine.
great, thats what I needed.
Pity no one else replied.
Ill give it another couple of days.
After this I will present them all the results and maybe a letter from Small claims, as they should not be selling phones they know will fail in service.

sometime NO GSM and sometime will detect a radio rom.

why my dopod 838pro sometime it cannot detect a radio rom and show a NO GSM, but if detect it a radio rom and it will hang about and half hours and reset will turn back to NO GSM, is hardware or software prob, anyone can give me a solution?
Provide more information - OS version and Radio version. Its probably a hardware problem but you may try to reflash to a manufacturer's shipped version and retest.
I had the same problem basically. Phone would freeze up, get repeated NO GSM messages, drop the radio even when it finds it after several minutes of use. I did buy the phone off eBay used and it did freezeup in WM5 ALOT.
I took the phone apart and cleaned all the contacts - same problems. Reflashed manufacturer's rom again and it took. Before it sometimes would hang up - looking for GSM radio. Took it apart again FULLY and put everything back together. It is now working for the past week. No freezeups or drops. Seems to always find GSM on bootup.
last time using a official rom wm6 also freeze up, then flash it to manila2d rom, it also got a same prob, try reflash a radio rom, but always get stuck at 6%, but try and try then 100% done, but also same prob.
so ur solution is try Reflashed manufacturer's rom again?
Thats what I did but the flash alone didn't fix the problem. I don't think a rom flash will bring your phone back but you may get lucky. I had to open it up and clean and reposition things. For some reason it worked. I still get screen fade to white and the directional pad on the front sometimes doesn't work - you move the scroll wheel and it will work again. Might have to replace the dPad circuit board or flex cable. The HERMES seems to have MAJOR problems with quality control and the radios. I personally think the battery presses against a backing plate which rests directly against the chipsets. The silver plate behind the battery does flex and it shouldn't. It probably should be a little thicker to prevent flexing. The heat from charging and the pressure from the battery I think causes the radios to fail. Bad soldering also may be a problem but any pressure on a motherboard and chipsets isn't a good thing. Also screws that are too tight also may contribute to the problem.
My phone has been working for about a week. Prior to that it was getting constant NO GSM errors on bootup and dropped calls. Today the phone was out of the house for the first time in weeks and it worked without any problems - no freezes (did a lot before) and no dropped radio. It has been sitting on my desk for two weeks without any problem. Will try it a few more days and see.
herm200 no GSM
Hi! I have read all thread about no GSM from here.
I have already do many many tests, tried to flash any radio rom extracted, hard reset, mtty with set 1e 1... I have already dissasemble and reassemble it
but no one fix the problem No GSM.
I have the same probleme, sometime no gsm and sometime ok.
So please, if anyone find everything which can fix this problem please post it!
Sorry for my english!
Thanks a lot for all jobs and helps.
Hello all, my hermes had this problem too!
Sometime it works, " 1.56.70.11" and sometime no! "NO GSM"
i have done about twenty flash thinking it will resolve this problem...
After reading a topic on this problem, i have understand it was an hardware problem. Something unsolde.
I have buy "double face scotch", i have disasemble the phone completely.
And on every chip and on the "battery"( little round and flat) i have put a little piece of scotch. it will do a pression on every chip to keep chip connected on the motherboard.
From this moment, the phone has never freeze, no more "no gsm" message!
ALL IS GOOD
Sorry for my poor english.
Many things can affect the radio
Try this...
Un plug your batt... insert a big piece of aluminium under the batt over the gsm chip... it wil not work properly... Magnetic issues... the batt do this things too i prove it on a Nokia... the batt without the stick = radio problem no signal...
Abd here i got the same trouble no gsm sometimes i realized that has been a lot flashes but noup, was a dialer that makes this issues 3G phone canvas,.... back to touch dialer 3G or 2G and its good now... think the CPROG and some other is not so compatible.
Desperately please help me, my Dopod 838 Pro has No GSM!
hey dude try another rom... the roms with HTC phonecanvas 2g or 3g do this issues on my hermes dunno why... thats th reason i dont cook anymore phoncanvas on my roms.
Update Radio ROM to 1.47
I had same problem just recently, and the recommendation that I got was update your Radio ROM ONLY...I upgrade to Radio 1.47 as all the time I was loosing service connection as well as No GSM...after this, my Hermes took live again.
I had 1.16 Radio...!!! and that issue came up after upgrading to one of the so many cooked ROM...I don't remember which one...
Check this link for more info, it saved my life!!!
http://forum.xda-developers.com/showthread.php?t=295751
Cheers,

pink n purple camera glitch

hey guys, my friends has just got his desire from o2. know having only got it yesterday hes never really had a chance to DO anyhing with it.
now, today we were dicking about and i knocked it out of his hand. no immediate damage except he got a glitch while in the viewfinder. now ive searched modaco and the entire internet and found a lot of people are having the same issue
my question is can we replicate these conditions ourselves. my friend seems to be getting it when rubbing the back above were sd card and sim is. and only while the data is connected.
of all the threads i saw there is no fix except a new device
any ideas or advice appreciatred
f/w 2.1-update1
baseband 32.36.00.28u_4.06.00.02_2
kernel 2.6.29-c8d11160 ([email protected] #1)
build 1.20.207.3 cl171460 release-keys
software number 1.20.207.3
browser webkit3.1
Aye, that friend would be me. PiLoT managed to knock the phone out of my hand completely by accident, but having checked a good few websites out there, I don't think that it has anything to do with what's happening.
There are several videos that demonstrate the problem, and a quick search of YouTube for "HTC Desire Camera Glitch" returns four or five relevant results. Most comments seem to say that a replacement phone is the answer, but it's a bit too specific for me to think that it's a hardware problem.
Any time I run my fingers across the back of the phone (over where the MicroSD card and SIM card are) at the same time I have "Mobile Network" enabled (i.e. GPRS), I get a weird splitting of the screen. It separates into its component colours - magenta, cyan, yellow - and scrolls to the side and/or splits into various "window panes". When GPRS is off, the problem is impossible to recreate, which is the part of the problem that makes me think twice about it being an out-and-out hardware issue.
The version details PiLoT posted below are correct for my device:
Firmware: 2.1-update1
Baseband: 32.36.00.28u_4.06.00.02_2
Kernel: 2.6.29-c8d11160 ([email protected] #1)
Build: 1.20.207.3 cl171460 release-keys
Software Number: 1.20.207.3
Browser: WebKit3.1
I'm going to email O2 about this - I've got insurance for my phone, but since this falls under the category of a manufacturer's fault, I'm pretty sure I should be able to claim it under warranty.
I'd very much like to hear if anyone else with a Desire is able to replicate this issue, or if anyone here has had the issue, what steps they took to resolve it.
Alright, so I emailed O2 about this. They seem to acknowledge that it's a manufacturer's fault. Without openly saying "Yeah, we know about this", they didn't question me at all when I described the problem. They just said that they'd arrange a brand new Desire to be sent out to me.
They're doing a door step exchange, which means that I'm giving back everything but my SIM card. The email even said that it'd be a brand new phone, meaning I get the joy of unboxing the Desire for the second time.
Only disadvantage is that the rest of the UK think that Moray is part of the Highlands, so nothing gets here on Next Day Delivery. They say it'll be here on Wednesday, but I'm waiting for the confirmation email from the courier (think they said DPD).
Also, finding out that removing all personal details and info from the Desire is a bit of a daunting task. The backup feature apparently encrypts your data, meaning it can only be used again with that specific phone. Not to mention the fun I'm going to have wiping the microSD card... hoping there's a feature on the phone for that, rather than having to whip it out and pop it into an adapter for my laptop.
Will keep this thread up to date with the various happenings over the next few days.
I have the same camera problem with my HTC Desire . Is there any solution for the problem or is it better to send it back to HTC?
I had same problem with my camera, and i gave it to HTC service and they replaced camera, and some connectors..i forgot which...
And no more problems with camera!
I had a random one where half the screen went green and showed a completly different angle. Very weird but only happened the once..so far
I have the same camera problem with my HTC Desire . Is there any solution for the problem other than sending it back to HTC?
Although this is an old topic, I wanted to state my experience...
I'm using this device for some time now, and I've experienced this issue couple of times. Rebooting, deleting the camera app info or changing roms didn't help particularly but somehow it turned back to normal with unresolved question... Why does this happen?
I began to have this issue again last week, I'm a frequent flasher so I thought another flash may solve the issue but no... nothing changed.
Than I uncovered the battery compartment, and start to clean the camera lens while watching the camera display...
I felt-hear a click sound and voila coincidentally the view was bright and clear as first day.
The it hit me I dropped my phone last week in hurry while taking a note... Camera device must be disconnected or loosened hence the the tint or pruple effect...
Any how I would like to share this as an experience...
Have try...
ham-solo said:
Although this is an old topic, I wanted to state my experience...
I'm using this device for some time now, and I've experienced this issue couple of times. Rebooting, deleting the camera app info or changing roms didn't help particularly but somehow it turned back to normal with unresolved question... Why does this happen?
I began to have this issue again last week, I'm a frequent flasher so I thought another flash may solve the issue but no... nothing changed.
Than I uncovered the battery compartment, and start to clean the camera lens while watching the camera display...
I felt-hear a click sound and voila coincidentally the view was bright and clear as first day.
The it hit me I dropped my phone last week in hurry while taking a note... Camera device must be disconnected or loosened hence the the tint or pruple effect...
Any how I would like to share this as an experience...
Have try...
Click to expand...
Click to collapse
I second this fix. I uncovered the back of my phone and press on the camera until it clicked. Voila problem solved.

Signal Sporadically Drops After Kernel Mod.

Hey,
Before I go any further, yes I have checked for other threads relating to the issue I am experiencing an could not find any that were completely relevant to my situation (I know how annoying and time consuming duplicate threads get! haha).
So I am with Telstra (Australia) currently running the 4.1.1 (JRO03C) Build. It is rooted and (Currently) running leanKernel-4.0.0dev14-jb. Prior to this I was running Franco's kernel. More or less, after waiting for Franco to push out a stable build for his mod, I decided I would try out the LeanKernel that is included through his Updater (So much quicker than the recovery way, I love it!). However, I just had to be unfortunate enough to do this during that 12 hour window in which the Franco Kernel Updater was experiencing a bug when flashing LeanKernel. After installing and rebooting, the phone would not start. It would just sit there at the splash screen, I set to work resolving it but ran into issues where the boot-loader was saying that there was no 'Boot' or 'Recovery' partitions. This was peculiar because I could still access CWM. So I eventually fixed it by pushing the Stock Kernel to it Via Fastboot and re-applying all the Bootloader and Radio images. (Another small fact, regardless of what Kernel I flash to it, it still seems to say LeanKernel.)
Now, the phone worked fine and Dandy for a few days, I did not even loose my data in the process - Was exactly the same as before. However just out of nowhere it lost signal. I immediately try powercycling it - did not fix the issue. So I then cleaned the SIM card and all the usual but it still could not acquire said reception (I also swapped SIM with a friend and my SIM worked in his without fault). I proceed over the next few hours feverishly mixing and matching all kinds of Radio's, Kernels, Settings, Supposed Patches and Fixes to no avail. The signal would come and go seemingly at will. I also fully reset the device and that did very little to improve the situation apart from render the phone slightly more responsive. And the thing is, its not as if it is saying it still has reception - the representation bars literally disappear completely.
Im at wits end with it, I had a HTC Dream when i was at school and spent weeks upon weeks figuring out how to carry out the Basics of a PowerUser Equivalent (Rooting, ROM FLASH, Radio's, Kernels, Overclocks, Diagnosing Software errors - the works) but this one has me gob smacked. Any help would be greatly appreciated, please let me know if you guys believe I may have forgotten a step or something obvious (Hiding in plain sight haha).
Thanks!
THEfog
Anyone? Any feedback appreciated.
Fixed.
Alright, So I waited for somebody to reply to my question but it seems like everybody has better things to do. Eventually I resolved the problem.
I take no responsibility if you destroy your phone by disassembling it incorrectly.
I exhausted all possible software related troubleshooting, so I decided to tear it apart. After following the iFixit Guide for disassembling the Nexus (ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1) to Step 7 and removing the Headphone Jack/Speaker Assembly, I then noticed that my Coaxial Antenna cable had been pinched by the plastic mounts that it sits in. Due to the way it had been pinched and where the mount was - I was confident in assuming that I must have dropped it one to many times (i1081.photobucket.com/albums/j345/THEfog101/WP_000002-edit.jpg) causing the plastic rails to compress the cable.
Due to the small size of the cable - it was beyond repair, however I did manage to get it partially working as a interim solution. I separated the plastic shielding from the cable and re-rolled the inner cabling to the best of my ability. I then re-applied the plastic shielding and sealed it in wax. After re-assembling the phone (i1081.photobucket.com/albums/j345/THEfog101/WP_000011.jpg) it was getting reception, however it did sporadically drop under heavy usage (Lots of Data Usage Etc).
I Hunted around for the replacement cable (Was a lot easier than I thought It would be) when I found a supplier in the US, it proudly stated it was for the global model so I was confident it would work with my Australian model (cellphone-repair-shop.com/samsung-galaxy-nexus-global-antenna-coax-cable/). It was a little bit more pricey than I thought, but it was still a heck of a lot cheaper than buying another Galaxy Nexus (~$500).
The Cable came (i1081.photobucket.com/albums/j345/THEfog101/IMG_20120828_171935.jpg) and I fitted it the next day, simply taking the old one off and replacing it with the one I received in the mail - nothing else needed to be done. Since fitting the new antenna the Nexus now receives full reception again does not suffer any drops in service. (i1081.photobucket.com/albums/j345/THEfog101/WP_000020.jpg).
I hope this helps any others that suffer an issue similar to this. Sticking it may not be a bad idea either - simply because I could not find any other DIY fix to this issue online.
P.S Sorry about the non hyperlinked URL's, it wont let me post them because I have not posted here 10 times, despite me having been a member for quite some time.
Thanks!
Nice job, you know your stuff. Glad you got it fixed.
PS: the posting limits are based on the number of posts you have, not the date you have registered at XDA.
Thanks, It was a good opportunity to learn a little more about the internals of the phone as well. But yeah, I figured that was the case when it kept em blazing that message across the top of the page in large obnoxious letters whenever I tried to post with URLs embedded haha

Had my One X for two months now.

It had no issues at all, everything was fine, after three weeks of no issues I decided to unlock the bootloader, and flash a custom ROM, after many roms and no issues at all today I noticed the screen started rippling, the screen is loose, a dead pixel on the bottom of the screen, wifi antenna issues.
It worked great without ANY issues for a few months and now all of a sudden this **** happens, what do I do?
I live in The Netherlands, should I call HTC? Go to the place where I bought the phone?
Since when Grozny is in Netherlands?
Well, as you have void your warranty, you can't expect that they will fix it for free. But, if I was you I would have taken it to HTC service and ask them for help.
There are some threads here on how to lock the bootloader back, and flash stock ROM, you can try that as well, and hope that they won't see it.
Anyhow, I really wish you good luck with your handset. This looks like hardware failure, shouldn't have anything to do with you have rooted and played with ROMs, but there is always the fine print in warranty that covers the manufacturer from everything...:silly:
[email protected]|-|oR said:
Since when Grozny is in Netherlands?
Well, as you have void your warranty, you can't expect that they will fix it for free. But, if I was you I would have taken it to HTC service and ask them for help.
There are some threads here on how to lock the bootloader back, and flash stock ROM, you can try that as well, and hope that they won't see it.
Anyhow, I really wish you good luck with your handset. This looks like hardware failure, shouldn't have anything to do with you have rooted and played with ROMs, but there is always the fine print in warranty that covers the manufacturer from everything...:silly:
Click to expand...
Click to collapse
Was born in Grozny.
Either way, I am writing HTC Support now with all the issues explained, telling them that I've read all the threads with similar issues on XDA-Dev.
Hope they don't come with the ''Flashing, rooting'' bull**** as it's obvious that this is all a hardware fault, if they do, I'm going to ask them in which way changing the software and playing with roms makes the screen come loose.
I'm seriously ashamed seeing all these threads with issues, HTC makes one of the strongest devices out there, and it has countless issues building up every day.
D3VICE said:
I'm seriously ashamed seeing all these threads with issues, HTC makes one of the strongest devices out there, and it has countless issues building up every day.
Click to expand...
Click to collapse
If HOX devices had failure rate of 0.1%, there would still be a thousand failed HOX devices if HTC sold one million phones. And failure rates are *considerably* higher than that. So, for any device that sells well, there's bound to be more problem reports out there, too.

Categories

Resources