Hello all,
Well, some days ago, I decided to buy a Rhodium and sell my old Raphael, but first I had to fix the keyboard space bar who was causing trouble (had to push quiet strong to (as this thread : http://forum.xda-developers.com/showthread.php?t=777284). So, I had an old TP who was bricked, I thought I could switch the keyboard to fix this problem.
I disassembled the TP very very slowly and carefully (2 hours to open the first housing [...]) after all was done, I reconnected the speaker (once more, 2 hours to reconnect it...). I started the phone... all was fine, keyboard ok, but radio signal no detected (may be a bad location). Well, after somes hours I thought the rom was causing trouble -> flash into shipped rom, radio included, not improvement. Updating radio to latest one... no change. Hardware problem could only cause this.
But, when I'm very very very (yes, very !) near a great signal radio, my TP can connect to the operator ! (but low signal). Otherwise, the TP is like in Flight mode.
What have I done ? have I destroyed the radio ? I followed the dissassembling file step by step.
Ps : I switched again to my old keyboard, no change.
Thanks to help a poor noob.
Related
Folks,
I have noticed a problem with the screen sensitivity since upgrading my imate with the qtec 1.11 rom:
The screen sensitivity appears to drop very considerably at times. More often in areas of poor reception. It renders the device virtually unusable at times.
I am minded to think that the new rom allocates more time to keeping the signal strong rather than having the screen retain its sensitivity. The reason for me thinking this is that I never have any problems when I go into flight mode.
Hardware keys do not suffer from any sensitivity problems and I know the unit is fine in that regard - ie, I have started using the up/down hardkey instead of the stylus when the unit is playing up.
Has anybody seen similar & more importantly does anybody know how this could be tweaked?
This is the only problem I have encountered with 1.11! Other than that, everything is great - especially the battery life!
Cheers
Marc
The problem seems to occur irrespective of the signal strength. I am about to downgrade but am wondering which element to downgrade: Radio or System?
Anybody else have this problem or can anybody give some advice.
Is there any way to change the priorities on the JAM so that it commits more time to the screen touches and less to other elements?
I cant be the only person with this problem.... surely!
did you install any software after the upgrade?
do you have the same problem even after a hard reset w/o insstalling any other software?
I don't have any problems with screen sensitivity.
Do you use any different software before and after upgrade?
I have managed to prove that the screen problem I am suffering has nothing to do with the ROM version - I have had the problem occur with 1.03, 1.06, 1.11.
It looks like a hardware problem. Good news in one way but bad news for me.
There are others that have mentioned slow screen response.... my problems started off like this about 2 months ago. Now the unit can go days without getting any response from the touch screen. Hard and Soft resets make no difference at all.
I think we need to get more people to comment on this...... anybody?
I have managed to prove that the screen problem I am suffering has nothing to do with the ROM version - I have had the problem occur with 1.03, 1.06, 1.11.
It looks like a hardware problem. Good news in one way but bad news for me.
There are others that have mentioned slow screen response.... my problems started off like this about 2 months ago. Now the unit can go days without getting any response from the touch screen. Hard and Soft resets make no difference at all.
I think we need to get more people to comment on this...... anybody?
My immediate reaction after installing 1.11 rom/radio and then the 27 MB storage rom was that my magician felt sluggish compared to before.
I haven't had too much time to play with it, but yes, it definitely feels slower with 1.11.
@LeSkip: I use QTEK 1.11 ROM and my mini runs faster (compared to the original O2 mini ROM). I don't have any experience with BigStorage ROM so I can't compare.
@marcyspark: I hope you're still under warranty. Downgrade the ROM so you can have it repaired under warranty (Upgrading the ROM can void your warranty).
Cheers for the warning - I already took care of that side - thanks for the thoughts though. Much appreciated.
I now have to deal with the Imate UK service centre which, so far, has not been good:
1. After explaining that I had upgraded to the latest Official Imate ROM I was told to go to the website and install the latest ROM !!!
2. I was told to list all third party applications that are installed!!! There arent any cos the damn thing has had a new ROM installed and I cant get it to do anything!!!
3. The most recent advice was to hard reset and everything would be fine!!! Aaagggh!
4. Finally, I was told that a firmware update will be available to fix my problem which, as I told them previously, occurred with Firmware 1.03 and 1.06.
Bizarrely, the imate has come back to life after a few days without use AND I have noticed that if you press onto the battery from the back you can get it to respond for a while.... but only a while. Could this be a design issue rather than a hardware fault???
I have never pressed hard on the unit (for fear of damaging or marking the beautiful screen) but could it be that the chassis flexes over time?
Any thoughts folks - surely this stuff is for beta testers not paying consumers..... dont start me off on this one.
(I sound like a Lawyer cos I am one)
I have a MDA Compact running 1.0.1 rom, so I just upgraded to 1.11. All went fine, everythings seems to be speedy and nice.
The next thing I did was use my sprite backup to restore teh apps to the MDA. Once I had done this, the screen became very unusable and needed a big press to get anything to happen.
I have just hard reset again, and all is fine. Im now going to try reinstalling everything from scratch and see how it goes.
Its a software thing guys, must be.
Hello Everyone,
I'm in need of some assistance to see whether my hardware is bad or not. I have a G3 cid/sim unlocked 8125 that I've been flashing for 2+ years. I recently switched to Tmobile from Cingular/Att. I'm running WM6.1 from It's Right.
As of yesterday I noticed my phone would freeze and then turn to the dreaded WSOD. I was unable to reset using the power button but could through the soft reset button on the side. The phone will either not load all the way or will eventually load up but freeze after a few minutes of use.
Resolutions I have already taken are:
1. Taking out the Tmobile sim. This has made no difference.
2. Reflashing the phone completely. I took it to the base Tmobile 2.26, flashed the 3.08 ipl/spl, flashed the newest WM6.1 From It's Right (TNT.19209+Professional+Wizard+TouchFlo+FREE).
What I have found is still instability. I noticed part of the problem was coming from TimeSync 2.33 so I removed it. The only other programs I have installed that did not come with the rom are:
QuickMenu 2.7
Netfront Browser 3.5 (demo)
Heck the phone just white screened and reset itself while I'm typing this.
BTW none of this has ever happened to me before using the TNT rom's, Mfrazz's roms, Summiter roms, etc... This is a completely new problem that just started yesterday.
Any advise/solutions would be greatly appreciated. If the problem cannot be resolved easily or cheaply I'll be upgrading to a Tilt/Tytn II but I have to justify the cost.
Edit: I'm getting a lot of looks but no replies so I will be posting this in the general forums also.
I have the same issue with tht TNT ROM. I'm downloading the AMP one right now to check if it is of any relevance.
The same happened with the love rom, so it's probably not a rom issue. Are you overclocked by any chance?
When it first started, yes I was over clocking with the newest version of BS.
I figured out what the problem is (fingers crossed). My phone has went through hell and back with the amount of times it has been dropped by my children and myself. The battery cover (extended battery of course) broke and I recently ordered a new one along with some new stylus's.
Well it seems as if the phone's dimensions have changed slightly from all the banging around and I had to change how the ribbon that allows you to remove the battery is positioned.
Instead of either folding it under the battery or having it come over the battery I had to lay the ribbon flat along the phone then place the battery in. Also had to make sure both sides of the sim card are inserted properly. Otherwise it seems as if the battery connection is compromised, therefore the WSOD and soft resets. It still happens occasionally, usually when I place the phone in my holster.
I hope this helps others with similar problems.
The rom is fine. In fact I am yet to have a complaint about it except for the notifications (standard TNT) at reset. I haven't even installed BS yet, but I have put in TimeSync 2.33 with no problems.
I've also went back to SPB shell and ditched S2U2 for now. Not that S2U2 gave me problems. It's just without the new BS skin I missed having the time in big bold #'s and for some reason I can't stand HTC Home. SPB Shell gives me the home buttons and the standby screen.
Oh yeah - I'm very glad I don't have to get a new phone yet since I found out yesterday that TMobile's 3G network will be using the 1700 band and the tytn / tynn II wouldn't give me 3G once the network launches.
I love my Touch Pro - really I do, its got all the features I want currently (except a digital compass would be good with some AR software, but that's not important roght now).
However, having got my first TP back in February I am about to send my handset back yet again as it has died again.
The first handset had a serious problem with battery drain and switching itself on (ie screen on) when not in use - I posted here about this at the time (clicky).
The o2 UK repair centre (Anovo) first of all said they'd fixed the fault, but after two weeks the phone was doing the same again - I did confirm this was not a software issue by running it ofr two weeks without any of my usuall applications on it.
So it went back again and was returned 'No Fault Found'.
At this point I demended a replacement handset. The replacement I received (a refurbished unit) had a speaker fault - crackling whenever the speaker activated, ie before a call connected and during.
That one went back as well and I ended up with an SE X1 for a while. OK but not a Touch Pro (and wouldn't run my legitimately purchased Tom Tom Nav 5 s/w). This was because o2 UK said they had no more stock of the Touch Pro and wouldn't be getting any more (why? too many problems with it?)
Eventually I got a call from o2 after numerous letters of complaint saying that they were going to exchange the SE X1 for a brand new boxed Touch Pro.
I have had this brand new replacement since August now.
About a month ago it died on me again. It just wouldn't switch on. Disconnecting and reconnecting the battery resulted in the flash on the back flashing, the handset vibrating (as though it was starting up) but nothing else.
Connecting the charger resulted in the flash on the back flashing bright about every second.
A hard reset would not work at this stage.
After a couple of days I heard the 'battery low' sound from the drawer that it was stashed in. SO tried a hard reset again - nothing. Tried a hard reset again with the charger plugged in and it reset and cam back to life.
... for two weeks...
then it died again.
This time is very similar to last with theflash falshing thing, except that if I try a hard reset it seems to go through the motions but without the screen coming on (ie the vibration. The beeping sound. Click the volume down and it pings again as though its starting the reset, then about a minute later the vibration again as though its restarting after the reset). But the screen doesn't come on at all. And the lights don't light up on the front buttons or the keypad.
Unfortunately I didn't have myMobiler installed on the handset so I couldn't try connecting to it from my PC (myMobiler did try installing but as I couldn't click the 'OK' button it didn't complete).
So. Are my four deaths of the TP unique or has anyone else had similar problems with this handset?
-FM
Not I.
I have had my Touch Pro (AT&T's HTC Fuze) since December 2008 and I have not had a single real problem with it. I say "real" because I have had times when I couldn't get a GPS lock and of course the phone is slow sometimes, but that's what I've come to expect from HTC.
Anonymitee said:
I have had my Touch Pro (AT&T's HTC Fuze) since December 2008 and I have not had a single real problem with it. I say "real" because I have had times when I couldn't get a GPS lock and of course the phone is slow sometimes, but that's what I've come to expect from HTC.
Click to expand...
Click to collapse
you need the 1.14.25.35 radio. and a different rom. maybe atts 5.11 rom if you want to still keep it stock. 1.14.25.35 is atts radio too so that stock and wont void your warranty as well.
Fuze Died Today, I Think
I've used this fuze since December of 2008 and have been quite pleased with the performance. (considering that it IS Windows) My signature radio works quite well in the mid west North America and travels well through different data protocols. Like H to Edge to GPRS and back to 3G again.
Today I flashed a new rom via usb and now it won't pass the splash screen. That flash appeared normal in all respects. Tried several hard resets (to the bootloader screen) and have tried to re-flash a different rom via micro sd card.
I've begun to think that this may be a hardware failure and would appreciate any advise for troubleshooting. Keep in mind that device will NOT connect via usb.
my screen went white a couple days ago. it would end up showing the windows logo for a while then a white screen. i hard reset a few times but nothing worked so i reloaded atts 5.11 rom and now it just stays at the "initial setup of the touchflo interface may take serveral minutes please wait" screen and wont get passed. i saw another thread about the white screen months back but i cant find it again. im just gonna wait till they have tilt2s and claim it under warranty. im gonna miss having flash, i use it to light up everything, but im sure a larger screen will make up for it.
Well I now have a bit more info on this since the phone cam eback from 'repair'on Saturday.
All they had done at the repair centre was to 'reload software' (their words, not mine). ie I guess they flashed the ROM again.
It worked for a day, though I guessed that was more coincidence than anything - after all, when this handset first did this a few weeks before it suddenly started working again a few days later.
Luckily in that time I'd remembere to install MyMobiler this time, and so when the screen died I connected to my laptop and fired up a remote view of the phone.
The screen itself was dead, but everything else seemed to be working on the phone - except that while the screen was dead I had an error displayed on screen. The error was "MicropERROR" as attached here.
So I Googled the error message, and what a shock a nice long thread on XDA-dev about it. Seems it s a fairly common problem with the Diamond, Touch Pro and Touch HD. Joy!
So the phone is now back with 'o2' again for another 'repair' this time with the attcahed screenshot enclosed. I have been warned again, though, that the Serra is out of stock and if they can't repir it I may have to select a substitute. As far as I am concerned there is no substitute - there is no other phone at the mo with the Touch Pro's features (hardware keyboard, VGA/WVGA screen, A-GPS, g-sensor, WinMo, runs TomTom Nav5).
I fear the worst again, and fear I'm back where I was in July with an impossible choice to make thanks to o2 UK discontinuing the Serra / Touch Pro after a few months of supplying it.
-FM
well i got my TP back in March.09 and last month i have to replace the mother board and the back speaker other than that all is good so far
but i was so frustrated with HTC support centre (which is the main one in Taiwan ) real unpleasant experience as you all may know
Cheers!
Time to send mine back
Just had an issue with my last one, it was only 5 months old and the screen started looking like it had a vertical hold issue. Just got my refurbished one in Wednesday and now it is doing the same thing after playing games on it for 5 minutes. The speaker phone is crackling too for some reason and when charging it at night it's like the screen will not fully black out. I am wondering if I even want to try another one of HTCs products or not. Nice phones but to many headaches it seems.
Sorry, Double Post . . .
Never mind, please delete....
you´re wrong
This problem is from hardware or software. All you said is a lie, No GSM is an attempted issue from an expose the UNI to a HIGH frecuency electromagnetic radiation, like an electric motor, high tension wires, electomagnets etc. The high frecuency fries the GSM transeivers of UNI. in same way the uni has 2 CPU´s one of them works for pocket pc device and another one for GSM tunner and transmiter, as all CPU´s this have a NVRAM memory that requires a boot program if this memory gone damage or the NVprogram corrupted result in "No GSM".
The UNI had a several electronic design problems one of them is the low duration to expose to a hard usage, at the end reflash again and again and again the UNI gone damage the CPU´s, if your UNI gone to "No GSM" due to a hard punish to your UNI, you install or reflash some that corrupted the NVRAM from the CPU phone or you get a defective UNI.
antonny said:
Hi guys, at last my uni get no gsm (when I pull out the battery.. (duh!)... If U're succedd with my step, please don't pull out the batterry)...
Any way, I bring it to repair centre.
After My uni fixed, the repair centre said that every pda must turn off radio every day, cause as far we know, our device can't be turn off (unless we pull out&put it back without press power button). So our radio can get rest... (hmmm now I know why my uni get no gsm.. cause it never turn off and always on for years! Can U imagine that... Always searching for signal 24 hour 7 days for years...No wonder my uni radio get broke...)
Anyway, from now, everynite I turn off my uni radio and turn it back on in the morning... Also, now I use ROM Tomal/Ranju 7.7 (cause this ROM can still boot quick&correctly with no gsm...(just prepare if the problem occure again..)
Thanks.. Hope this can help...
Click to expand...
Click to collapse
This has to be the strangest thing I ever heard.
Speaking of ROMs you can use - Tomal's 8.2 (and quite a few others) boots fine without GSM and I find it much more functional than 7.7. Just a tip.
Thx
Thx, Orb 3000, AIN1, Enigma1nz.
No prob mate
Happy new year!
Hello all,
Well, some days ago, I decided to buy a Rhodium and sell my old Raphael, but first I had to fix the keyboard space bar who was causing trouble (had to push quiet strong to (as this thread : http://forum.xda-developers.com/showthread.php?t=777284). So, I had an old TP who was bricked, I thought I could switch the keyboard to fix this problem.
I disassembled the TP very very slowly and carefully (2 hours to open the first housing [...]) after all was done, I reconnected the speaker (once more, 2 hours to reconnect it...). I started the phone... all was fine, keyboard ok, but radio signal no detected (may be a bad location). Well, after somes hours I thought the rom was causing trouble -> flash into shipped rom, radio included, not improvement. Updating radio to latest one... no change. Hardware problem could only cause this.
But, when I'm very very very (yes, very !) near a great signal radio, my TP can connect to the operator ! (but low signal : EDGE). Otherwise, the TP is like in Flight mode.
What have I done ? have I destroyed the radio ? I followed the dissassembling process step by step.
Ps : I switched again to my old keyboard, no changing. :/
Ps 2 : Already posted in TP hardware problems, no answer.
Ps 3 :A beer will be offer to the one who could help me.
Up.
Please, has anyone an idea ?
I finally managed to repair it myself.
Opened device several times fixed battery & phone with tape and moved the hardware. After some test I found that if I link a little piece of metal next to USB to the plastic component, phone recovered radio signal, GPS, etc.