Database Users

My X01HT led is red

I got this problem last night. It started when I got my hermes dead, but after trying to charge the battery, the led turns to red. I've read on wiki (hermes problem) and try all possible solutions suggested there. Unfortunately, those don't solve my problem. Today, I am going to ask softbank shop (where I bought it from) to fix it.
The problem is, mine is flashed several times using English ROM from this forum. I also unlock it using code method, which base on imei calculation (at least that what Kevbodian, whom I got the code from, said)
My question is, is my phone still protected by Softbank warranty? I need this in order to make me feel confident when I try to communicate my problem to softbank officers. Thank you

Sounds like an overdischarged battery, pretty common. What I learned with HTC phones is that you should just never let their battery run down completely until it turns off by itself, but rather turn it off yourself at 10% unless you have the charger at hand. The shutdown threshold is always set a bit too low.
The last method in the list (the 3xAAA batteries) should work. I've always revived them by doing the same in a more "serious" way with decent equipment.
The problem is that by the time the phone turns off, and especially if you don't plug the charger right after, the battery voltage will drop enough for the phone to judge it as faulty and refuse to charge it. Charging the battery a bit outside of the phone to bring the voltage up a bit is enough.

Get you a cheap battery on eBay!
At least you can flash in case you will have to mail it in afterwards ...

Thanks for your reply. I'll try once more. Just to make sure, there are six pins on the battery. The + and - mark do not point to specific pins, but at the middle of 5th and 6th pin for - and between 1st and 2nd pin for +. Do I have to connect those two pins for each + and - or only the 1st and the last pin? Thank you.

mjbudhiyahoo said:
Thanks for your reply. I'll try once more. Just to make sure, there are six pins on the battery. The + and - mark do not point to specific pins, but at the middle of 5th and 6th pin for - and between 1st and 2nd pin for +. Do I have to connect those two pins for each + and - or only the 1st and the last pin? Thank you.
Click to expand...
Click to collapse
Were you able to figure it out? I'm in the same boat as you and I already tried the first and the last pin without any luck.

petes69 said:
Were you able to figure it out? I'm in the same boat as you and I already tried the first and the last pin without any luck.
Click to expand...
Click to collapse
Well, finally I sent the phone to Softbank. I think my problem is not at the battery. After trying to use another battery from working phone, I came to the conclusion that I got problem with my handset. Hopefully, I'll get it back alive within 15 days, otherwise I have to pay rental fee for the phone that they lent me.

I got message from softbank today. It said my phone has been fixed. I'll see what they did to it, especially the ROM. I hope they didn't lock my phone.

Big problems with Touch HD

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.

Constant Reboot-Loop (Faulty Battery?)

I'm aware that some users had this problem in the past due to changing the HSDPA/HSUPA settings or by installing the colored taskbar. In my case that's not the problem.
First of all a little recap of my well... troubled history with the Touch HD.
1. After 5 month of usage I got the infamous black screen error. The display turned black but the mobile responded to my actions. - back to the store - sent in and got it back repaired (changed main platine).
2. About 2 month later were the phone worked well - I got the same error again. Back to the store - sent in and got it back after three weeks with the comment that HTC couldn't find any error.
3. The same day I returned the phone because naturally the error was still there and furthermore the USB didn't work anymore. Got it back yesterday and it seemed to work fine. It was kinda weird that on my first startup the phone was already ready to use - no installation required and I even had the phone numbers htc used to test whether the device works or not in my call list (way to go using the european emergency call for that HTC ).
Did a hard-reset and everything installed without problems. Then when I tried to connect my phone to facebook it rebooted and was stuck in a reebot-loop. Only way to fix it is taking the battery out, wait for a couple of minutes and reinsert it. Tried nearly everything from here on:
- Hard-Reset
- Flashing another Rom
- Using Android
- Flashing back to the orginal HTC Rom
- Updating the orginal HTC Rom
- Cleaning every contact and the battery
- Completely draining the battery and recharging it to 100% before starting up again
- Cursing, swearing, considering throwing it out the window
- Taking out the battery overnight
Well, nothing helped. The only thing I can think of is that the battery is broken. Unfortunately I have no second battery at my disposal and do not know anyone who could lend me one to test it. My provider does not sell the Touch HD anymore because they now sell the HD2 so I can't test it there.
Well, maybe someone can shed some light onto this problem because I'm sick and tired of all the issues I had with my HD. Any trick, any thought about what could cause the problem would help. I'm returning the phone to the store on monday and they promised to give me a new mobile if I had issues after my mobile was sent to repair three times. Still, it will take a couple of weeks before their customer support is able to send me the offer and living a couple of weeks with that faulty phone is going to be tough since I never know when the error occurs.
Any help would be appreciated.
sincerely
Eisfeld

[Q] DZ suddenly wont turn on !

Hi I rooted my DZ about a week ago and installed CyanogenMod 7.0.3. It has worked perfect and I've been very pleased with it.
Last night I set the alarmclock for the morning, set the phone to charge and went to bed.
I then woke up 3 hrs late and discovered that my phone was turned off ?! I can't turn it on and nothing happens when I set it to charge.
My hopes are that its just the battery that's collapsed but what do you guys say ?

hoping the best for you but here's what happened to me:
Out of the blue my Desire Z stopped working: one moment everything is fine and then all of a sudden when i tried to turn the screen on nothing happened. well i didn't expect anything worse than having to take out the battery and reboot, but when i did just that only the home, menu, back and search button went on but not the screen...end of the story, i had to send it to the customer service wait for about 3 weeks (customer service in germany is rather poor because it is outsourced to another company) and get a mainboard replacement.
Maybe in your case it's just a dead battery, take it to the next electronics store and have them check if another battery fixes your problem...Good Luck!

Silly question but you have done a battery pull?

s0undless said:
hoping the best for you but here's what happened to me:
Out of the blue my Desire Z stopped working: one moment everything is fine and then all of a sudden when i tried to turn the screen on nothing happened. well i didn't expect anything worse than having to take out the battery and reboot, but when i did just that only the home, menu, back and search button went on but not the screen...end of the story, i had to send it to the customer service wait for about 3 weeks (customer service in germany is rather poor because it is outsourced to another company) and get a mainboard replacement.
Maybe in your case it's just a dead battery, take it to the next electronics store and have them check if another battery fixes your problem...Good Luck!
Click to expand...
Click to collapse
I'll go to my nearest 3 store next week to see if a battery swap will do it. I'm just afraid that it's the whole rooting thing that has caused it and that the warranty wont cover it :/
bombadier said:
Silly question but you have done a battery pull?
Click to expand...
Click to collapse
Yeah, several times

[HELP] my Omnia7 will not stay in standby! it switchs on alone

Hello guys,
I have a very strange but really bad problem: my omnia7 can't stay in standby.
When I press the power button, to turn off the screen and go in standby (so not the full turn off), my Omni7 wakes up alone, going on the unlock screen. In the same time, the phone rings with the ring that is played when you connect the phone for charging.
I've tried reboot, reset, hardreset, removing the sim-card, turning on/off "battery saver options" ... still that issue :crying:
Anyone has an idea?
I've flashed with a cooked rom (xda-devs Omnia7 Tango V4.0)
my current config :
OS version : 7.10.8779.8
hard version : 3.1.0.4
soft radio version : 2424.11.7.2
hard radio version : 0.0.0.800
loader version : 4.10.1.9
SOC version : 0.36.2.0
Thanks to any ideas, because that problem is killing me

my phone started doing this late last night too! i thorght it was because rain had gone into the power socket but if others are having same problem at the same time maybe not?
has your phone been exposed to water at all recently? is your phone jailbroken? cant realy think of other reasons
the problem stops when the phone is plugged in. is there anything that can trick the phone to thinking it is on charge? I have wphtweaks installed but the options there are not able to stop it

Hi,
I can't remember if my phone has been wet :/ I take care, so my phone never received water. But when I'm outside, under the rain, it's possible.
Today it was better, just a few times my phone wakes up alone.
I'll give you feedback in the next days. Let me know about yours

I managed to trick my phone into silence a few times earlier but it was difficult and then only lasted 5-10 minutes.
if yours didnt get wet it seems unlikely to do with water but I left mine ontop of the aga after removing the battery and over a relativly cool part. A few hours later and it seems to be working fine now.
I will report back if the issue arises again.
EDIT: Ahhhh!! STOP THE RINGING!!! started again this morning

Mine too !
This morning ... the ringing awakening problem !!!!!
But it was better this afternoon.
Really I don't know what happens.
Are we only two persons in the xda world with this problem????

this is realy weird now! mine was doing it in the morning but since about 12pm - 1pm it has been fine! I feel like its something to do with an installed homebrew app maybe.
I also have a custom rom but mine was flashed a long time ago and much older than yours. not sure which version
EDIT (1:10pm GMT): no problems since yesterday
EDIT2 (1:30pm GMT): again i spoke too soon!

Did you guys get this problem sorted out? Had the same problem recently and tried all the suggestions in other threads (bend USB pin, Reset/Restore Device etc) but nothing fixed it, so after being woken at 3am by constant charging tone, took to T-Mobile shop. They said it was a software problem. I said I'd tried all that and the most likely cause I'd seen on the internet was a duff USB port.
Anyway, T-Mobile sent it off for repair and 7 days later - returned and fixed. The repair sheet said software upgrade, but the phone had been reset to bog standard Phone 7, so unlikely. The T-Mobile repair tracking site (excellent) which shows blow-by-blow trace of what and where, showed initial software upgrade/no fix but I used their "contact us" facility to suggest a USB problem and by magic the repair tracking log showed a replacement USB port.
BTW - had to resort to an iphone and HTC android while Omnia was off for repair. Now I know why I like Phone 7 and can't wait for 8. The iphone GUI is so last decade and Android GUI is really just a copy of Windows 6.5 with XDA developers' tweaks isn't it.

Hi Wuzzok,
what do you mean by "bend USB pin" ?
Anyway, it seems like it's finished for me. I didn't get tht strange bug (soft/hard bug???) for a very long time. I just hope it's really over !

Same problem
Hi Folks,
I have the same problem, too. Yesterday afternoon on my way home the phone started ringing with the USB plug sound and always started up itself from standby mode.
As I have a custom ROM (mi7ROM) I first thought it could be a problem with the ROM - although I could not really believe it since it was running stable for months now. I flashed it again and nothing changed - still ringing and starting up itself
I managed to get rid of the sound by deleting the entry in the registry key "Local Machine\Current User\ControlPanel\Sounds\BatteryCharging\Sound" but that does not solve the real problem.
After reading here and in some other WP7 blogs I am sure that this is a hardware problem with the USB plug unit. As my phone is just 11 months old I opened an online ticket at "SAMSUNG online repair service" who promise to answer in the next 24 hours. So I just have to wait and see...

actual state
neutom said:
Hi Folks,
I have the same problem, too. Yesterday afternoon on my way home the phone started ringing with the USB plug sound and always started up itself from standby mode.
As I have a custom ROM (mi7ROM) I first thought it could be a problem with the ROM - although I could not really believe it since it was running stable for months now. I flashed it again and nothing changed - still ringing and starting up itself
I managed to get rid of the sound by deleting the entry in the registry key "Local Machine\Current User\ControlPanel\Sounds\BatteryCharging\Sound" but that does not solve the real problem.
After reading here and in some other WP7 blogs I am sure that this is a hardware problem with the USB plug unit. As my phone is just 11 months old I opened an online ticket at "SAMSUNG online repair service" who promise to answer in the next 24 hours. So I just have to wait and see...
Click to expand...
Click to collapse
Samsung sent me an offer to send the phone in for repair - but what should I say, the problem solved itself. For two days now the phone works normal again. So I had to cancel the service call .

mine hasnt done it in a long time either. looks like its just a temporary thing. I wonder what caused it! For me it started after I was using my phone in the rain and the usb slide was open so thats my suspect.

You may be right. Mine is "quiet" now, since a long time. Water may be the cause.

Update
Hi folks,
mine is mostly quiet again, too. Only few incidents "happen" but they do not last very long - only a few minutes. It's somehow spooky but I do not want to send it in to Samsung now when the error it not constantly reproducible.
I agree with you that there might be a correlation with humidity although I am sure that it did never get wet and I almost always keep the USB-shutter closed. Who knows ...

Sent it in
Finally I sent it in for repair today. It started ringing permananently two days ago...
Now I have to wait and see.

Final state
Okay, I received it back... and it works.
First they did nod find and could not reproduce the failure and wanted to send it back - only with a new flashed image - but fortunately the technician called me and I could describe the problem again. After waiting a few hours, the fault appeared again and they decided to change the mainboard.
I hope, that's all :laugh:

Hello,
Me too it makes me after my omnia 7 is dropped in water, but problem solved.

Me too
WuzzoUK said:
Did you guys get this problem sorted out? Had the same problem recently and tried all the suggestions in other threads (bend USB pin, Reset/Restore Device etc) but nothing fixed it, so after being woken at 3am by constant charging tone, took to T-Mobile shop. They said it was a software problem. I said I'd tried all that and the most likely cause I'd seen on the internet was a duff USB port.
Anyway, T-Mobile sent it off for repair and 7 days later - returned and fixed. The repair sheet said software upgrade, but the phone had been reset to bog standard Phone 7, so unlikely. The T-Mobile repair tracking site (excellent) which shows blow-by-blow trace of what and where, showed initial software upgrade/no fix but I used their "contact us" facility to suggest a USB problem and by magic the repair tracking log showed a replacement USB port.
BTW - had to resort to an iphone and HTC android while Omnia was off for repair. Now I know why I like Phone 7 and can't wait for 8. The iphone GUI is so last decade and Android GUI is really just a copy of Windows 6.5 with XDA developers' tweaks isn't it.
Click to expand...
Click to collapse
Are you really sure that the problem is USB port.. Mine too behave like this. I've tried to remove battery, factory reseting, reflashing ROM. But nothing works. Mine is Samsung focus

post to remove