Related
hi guys,
has anyone experienced a problem where their Trinity will not "wake up" with the short press of the on/off button?
I'm sure I read about this some time ago and am trying to work out if it's hardware or OS related.
I'm running mUn's TE WM6 which I have been for many months now.
The problem has only started in the last 2 weeks or so.
I haven't installed anything new, but have enabled Push Mail for OTA mail.
It's doing it 1 or 2 times a day now and is very frustrating. The only way to wake the phone is soft reset.
When calling the phone from a landline, it does not ring and goes to voicemail.
Any advice or solutions gratefully received.
no one seen this then I guess.
Bummer (for me!)
Try hard reset
sickboy555 said:
hi guys,
has anyone experienced a problem where their Trinity will not "wake up" with the short press of the on/off button?
I'm sure I read about this some time ago and am trying to work out if it's hardware or OS related.
I'm running mUn's TE WM6 which I have been for many months now.
The problem has only started in the last 2 weeks or so.
I haven't installed anything new, but have enabled Push Mail for OTA mail.
It's doing it 1 or 2 times a day now and is very frustrating. The only way to wake the phone is soft reset.
When calling the phone from a landline, it does not ring and goes to voicemail.
Any advice or solutions gratefully received.
Click to expand...
Click to collapse
Try hard reset
softreset helps, sometimes i have the problem with windows mobile 5 too
jmermel said:
Try hard reset
Click to expand...
Click to collapse
thanks John.
But do you have any fact based reason for this suggestion?
I'm happy to give it a go if there's more than 50% chance it will work.
Hard reset
sickboy555 said:
thanks John.
But do you have any fact based reason for this suggestion?
I'm happy to give it a go if there's more than 50% chance it will work.
Click to expand...
Click to collapse
You might have loaded a program that is not liked. Use a backup program. If this does not work then load your backup after the hard reset and you will be back to where you started
P3600 with D810 WM6 ROM; also happens occasionally, recovered with soft reset. Seems to happen most often when I press the On/Off button twice too quickly.
thanks guys.
I'm going to try the hard reset route-I'll report back.
Some time ago this happened to me so often, but said it was due to some application, in my case was Slide2Unlock.
Since I removed by their consumption of memory it didn't happened to me.
(Sorry for my english)
Bugger, this has started to happen to me as well. Only 3 times in the last 3 days but if it keeps is up that will be enough for me to do a hard reset (overdue). Strange cause the only new thing I put on in the last week has been PCM 16 which is only a copy/paste exercise.
The fix in the Hermes forum is to force your device to sleep and not let it go into standby.
I have had some problems recently with DeviceLock 1.2 just ceasing to work and have to uninstall/reinstall to make it work again. I set it to turn the screen off when locked, as this does not put the device on standby, maybe there is the same issue with it going into standby by itself.
I have the same problem..i think that it has to do with the phone hanging..most probably due to some background programs eating too much power and memory and the phone just lacks till it hangs..happens when you have other programs that have hanged as well..my problem is with PocketAlarm..it takes so long to load my phone went to standby and the phone couldnt be called back..in brief the phone just hangs because of a program..i don think it has any problem do to with the hardware or strictly the OS..cant really explain..but the role the OS play in this problem is that it allows the program to make full use of the phone till the phone cant cope with it..its the core of the OS so it cant be avoided with any other versions or anything..sorry it seems rather unclear..hope you guys understand..
same problem for me ... from times to times, when a call hang up, i push a lot of times the red button for going back to the today screen and as it shows up, i click immediately on the Power button for turning off the screen. right after when i forgot to do something (approx 1sec) i push the power button and there it doesn't turn on the screen ... strange ...
what i've installed on it :
TomTom 6
BatteryStatus with today plugin ver 1.04.203 beta4 i put tray icons too.
i've bluezard for sniffing and/or hacking bluetooth devices.
OBDgauge too it's a software that works with a bluetooth dongle i plug into the diag port of my car.
and that's all. ah yes one more thing -> i disable the "HTC Home" because i don't like it.
Same problem here...
Still no solution?
I got this problem from some version of rom by Karmba. But V7.2 is OK so far. It seems happened when I close Egress reader by click X button then turn off screen by power switch. It then would not wakeup again. But if I close Egress and check the running programs from Task Manager to make sure the Egress is not running at the background, then I can turn on or off the screen freely.
So I think this wakeup problem is caused by some running program that was not closed properly by X button then crash the WM.
That was just my personal finding. Hope it help you guys a bit.
Hello,
I have a strange problem with my HTC Artemis (O2 XDA branded, bought in Germany, no lock)
It behaves unstable and indeterministic.
Unstable means that it crashes/stucks or turns off.
Indeterministic means that it happens when i plugg it to charger, when i'm syncing, when a phone rings, when using applications/tomtom or just i arrive to work and i find the device off.
When it crashes or i find it off, the biggest problem is to boot the device. It takes me typically 10mins, when i'm always trying to press the power button, push the reset button or unplugg the battery for a while in random order until i bring it to work.
After first crach, the device also often crashes or stucks again during the boot process.
Once, the device was so dead, that it took me two days to bring it into bootloader mode and then i could at least flash the ROM.
All these was happening with ARTEMIS TOUCH 4.01 WWE - LITE NO CUBE.
Yesterday, i switched to ARTEMIS TOUCH 4.02 WWE - LITE NO CUBE (burned FW twice) without installing any other applications and the problems are still here
My personal feeling is that it is getting every week worser.
When i bought the device (eBay), there was original FW with Win Mobile 5 on it, i immediately flashed to ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device. So i flashed to 4.01 and this issue was away, but approx 2months ago, the above described behaviour has started and nowdays i'm fighting with it 2-3x a day.
so, can anybody help?
GiZMo
Similar here
I have a similar problem, what's really strange to me is, that as far as i can recall it started happening 2 months ago or so also!! weird huh...
my device simply reboots from time to time! even while i'm making a call.
the weird thing about these reboots is that when it comes back to live i do not have to enter my pin to enable the phone! everytime i perform a manual reboot (by software, using the pin or remove battery) i have to insert my pin to able to make a call...
i have upgraded from 3.01 full touch to 4.02 full touch about the time it started, i have now 4.02 vanilla touch but problem still occurs from time to time.
any ideas?
Im another one to join this boat!
Bought an MDA C 3, two days ago, bought of someone from gumtree.com.
Worked fine for the first hour, and then locked up - nothing on the screen, no LED. Only way to get it going was to remove battery and then press power button.
I upgraded the ROM from the original t-mob UK WM5 to mechles fine release: http://forum.xda-developers.com/showthread.php?t=371182
The lock-ups / crashes have now become rarer, on average every 4 hours (before was every 1 hour).
There is no pattern to them either, although I have saw the screen trun all corrupted just before it happens. The last one was caused when I pressed the 'start' button.
I'm on a T-Mob contract, and lost my Kaiser, got ripped of when I tryed to replace it by a tosser on here for $375 Thief on the loose thread, and was hoping my luck had changed when I bought this one!!
It is T-mob branded and I wonder if there isn't a fix on here, would T-Mob repair it under warranty??
same "issue" with no entering of PIN after reboot. But not always
GiZMoSK said:
ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device.
Click to expand...
Click to collapse
here i found a good description of that issue:
"
Originally Posted by lasertony
I've got the same problem as !Novy, but nobody seems to have noticed his question. Are there any other guys out there with this strange problem ? I have been using this rom for a while and sometimes, without any visual warning the phone freezes up. This is particularly ennoying because there is no way to check wether it is working or not. Every other function or software keeps working ! The phone is just not receiving any calls or sms. So you can miss an entire day of calls and sms without knowing... Only when trying to call somebody the dialer says 'Dialing...' and nothing happens. No connection.
A soft reset is needed to get the phone working again.
"
btw, now i'm again trying to turn the device on, it's again stuck. grrr
Hello,
i had a few weeks ago a similar strange behaviour.
After changing the sd-card I had problems to turn the device on. After a hard reset it began to boot but hang.
The I flashed back to original O2 ROM. Then I had a unpredictable behaviour. Somtimes no sound. Sometimes I cound not be called. Sometimes Error message "no sim card". After every reset i had an other error.
Hard reset and flashing was no solution. Removing battery for less than 4 hours has no effect.
Then I wanted to send it back for repair. I took of the battery. The next day I wanted to try a last time and surprise: The device works fine without an error. Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
regards
Andre
It is Happening to my device too!!
It stucks every 2-3 hours!Tried many of the cooked ROMs but nothing.Also tried all the radio roms for 1-2 days.still the same!
It stucks with no particular reason.SOmetimes in s2u2 sometimes when am receiving a call.... etc.
Had the pin problem too for 3-4 times!
I will try your sugestion ANDRE and we will see!
Also i will try flashing the original rom,cid unlock and then flash the cood rom twice!
Fingers crosed....
Andre1210 said:
Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
Click to expand...
Click to collapse
didn't help
happy u
now, i will try to flash back original german o2 rom
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
bricked or not?
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Vinnie1 said:
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
Click to expand...
Click to collapse
I thought it was a battery problem too, but I've 2 batteries and both are died in the same time? I think it's too strange...
My P3300 have this problem from when it is returned from assistence and with original firmware (without other applications).
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
GiZMoSK said:
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Click to expand...
Click to collapse
jahrami said:
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Click to expand...
Click to collapse
but i cannot get into bootloader mode so no flashing from SD card or PC
bricked device
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
GiZMoSK said:
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
Click to expand...
Click to collapse
the good sign are the leds that means you have a very good chance...the guy made the piont...check the wiki
random crashes are often caused by hardware malfunction...sometimes the connection on the motherboard stuck,get broken or make a short-circuit...so check the hardware
Hi everybody...
yesterday i was sitting at my desk with my Desire in standby...
suddenly i heard a vibration and i noticed that the phone was rebooting....
i thought that was "normal instability"...and i continued working...
some minutes later i received a phone call, i answered and i spoke normally....when it was time to end the call, like always, i touch the red button on screen to close the call and BUM !!!
my phone rebooted himself.....
from that moment every call ending , done by me or received, cause a reboot of my Desire....
i' ve already called HTC tech support for assistance, but,prior to send the phone to the repair center, i would like to know from you "experts" if this problem can be a "software related" problem or it is for sure an "hardware problem"...
obviously i've already performed an HARD reset of the phone (either by the provacy menu and by the HBOOT menu) and nothing has changed...
last thing....my phone has 7 days of life....SIGH
thank's in advance for your help
Francesco
francesco131177 said:
Hi everybody...
yesterday i was sitting at my desk with my Desire in standby...
suddenly i heard a vibration and i noticed that the phone was rebooting....
i thought that was "normal instability"...and i continued working...
some minutes later i received a phone call, i answered and i spoke normally....when it was time to end the call, like always, i touch the red button on screen to close the call and BUM !!!
my phone rebooted himself.....
from that moment every call ending , done by me or received, cause a reboot of my Desire....
i' ve already called HTC tech support for assistance, but,prior to send the phone to the repair center, i would like to know from you "experts" if this problem can be a "software related" problem or it is for sure an "hardware problem"...
obviously i've already performed an HARD reset of the phone (either by the provacy menu and by the HBOOT menu) and nothing has changed...
last thing....my phone has 7 days of life....SIGH
thank's in advance for your help
Francesco
Click to expand...
Click to collapse
Mines done that a few times, as well as when ive disconected from a bluetooth headset. It happened on 1 device and i sent it back to orange and got a replacment, the 2nd device now does it with the generic rom on it, im hoping the custom rom ive put on it will fix it if not im screwed and so need a orange rom to revert back 2
im starting to think its something ive installed on the phone that it doesnt like
Hi, my Desire HD just automaticly turn on speaker everytime i call someone or recieved a all.
I did some searching and people say turn it off may help. I tried to turn it off (no fast boot) remove the battery, and it still turn on auto speaker
I also realized that sometimes when i turn it on, carpanel automaticly launch. So this might be some problem with carpanel. I turned off the auto option in "dock" section of the setting. Still doesnt change anything
I think the proximity sensor have problems. So i tried some test with it. It's still fine
Can someone help me with this? i even tried hard reseting my phone, it doesnt help
What rom are you using? I had the same problem once, reflashing fixed it.
Sent from my Leedroid powered pocketsized supercomputer using XDA App
I'm using stock ROM , when turn on it says the branding is SFR something. I havent rooted my phone or install any other ROM ever
Well then you could try recalibrating the g-sensor from settings -> display.
Sent from my Leedroid powered pocketsized supercomputer using XDA App
You may have flip for speaker switched on. Go to Settings>Sound and then under Incoming Calls uncheck the option for Flip for Speaker.
abhishekagrawal said:
You may have flip for speaker switched on. Go to Settings>Sound and then under Incoming Calls uncheck the option for Flip for Speaker.
Click to expand...
Click to collapse
That was what I was aiming for. The g-sensor thinks the phone is upside down when in fact it isn't, recalibrating should fix this.
mrhahn98 said:
I'm using stock ROM , when turn on it says the branding is SFR something. I havent rooted my phone or install any other ROM ever
Click to expand...
Click to collapse
ok try this my friend, take battery out, sim out and sd card out, wait a few minutes thn put everything back together and power on the phone, should solve the problem, all the best.
Sent from my Desire HD using XDA App
Hi all. thanks you so much for the support.
I've tried all the above, like turn off carmode, turn off flip for speaker...etc. take out the battery, sim card, sd card. It's still the same. After some digging, i found a topic about this on the DHD forum. They said it was an USB problem. i tried to plug it in to the USB and wiggle it a little bit and carmode/speaker auto turn on and off time to time. I was about to give up and when i'm on my way to return it. It suddenly come back to normal, no problem, tested with the USB cord. This is so weird !!!!! but i'm glad that it's gone away
mrhahn98 said:
Hi all. thanks you so much for the support.
I've tried all the above, like turn off carmode, turn off flip for speaker...etc. take out the battery, sim card, sd card. It's still the same. After some digging, i found a topic about this on the DHD forum. They said it was an USB problem. i tried to plug it in to the USB and wiggle it a little bit and carmode/speaker auto turn on and off time to time. I was about to give up and when i'm on my way to return it. It suddenly come back to normal, no problem, tested with the USB cord. This is so weird !!!!! but i'm glad that it's gone away
Click to expand...
Click to collapse
My other half had exactly the same thing on her Desire, turns out it was dirt/ fluff in the USB socket!
I have the same problem with my DHD, since I don't have the warranty for my set, is there a way around it. Like some sort of app which turns the speakers off when u make or recieve the call. That can make my life easier.
This problem started with my phone too..I tried all above such as changing rom,usb trick,sim+battery+sd remove,calibrating g-sensor ...Only thing i did not try is changing radio..If it wouldnt help me ,i dont know what to do since i dont have a warranty too..Its really annoying..
DHD speaker selfactivating
Those problems /carmode and speaker selfactivating/ started shortly after OTA 2.3 update.I honestly don't remember how I've managed the carmode issue,but initially I was able to solve the speaker selfactivating by pulling out the headphones' plug during a phone call.That did it for a once or twice,as the result lasted for a day or two.After reading the tricks suggested above I tried them with no success until pulling out the phone end of the usb during a phone call while connected to the pc in debug mode.So far I've made a few calls and it looks OK.
I don't want to scary you, but when I had the same problem I found only one solution which works- restore to factory settings... Its a pity...
Hi ,
I have the same problem on my Desire Z. I have had the phone for more then 6 months.
I was running stock: - no problem !
I was running Virtuous Sense 1.0.1 for about 3 months: - no problem !
Yesterday I got this: it auto turns on the loud speaker when I answer or dial.
Flip for speaker is turned off, G-Sensor is calibrated !
I have updated to Virtuous Sense 1.0.2 : same problem !
I have wiped off everything and flashed Virtuous Unity 1.24.0 : TWICE !
Same problem
Sorry for posting under DHD, I did not want to open a new topic on DZ forum , but I will if I must, this is driving me crazy !
I have solved this after wiping all data and flashing the rom again (3rd try !
I told it, there is only one solution- restoring factory settings...
same problem without OTA
Got the same problem since 2 weeks without having done any changes at all to my DHD (still on 1.72.405.3)
+ Car panel starts randomly when connected to USB for charging
+ Phone speaker always on regardless what I tried before
So, I really do not think this is a rom related issue but more a "aging" problem like the GPS connectivity.
Anybody any idea, why the USB plug should be respobsible for this strange behaviour?
I'm not sure this is a USB related issue. It may be the audio jack. My problems started after unplugging the headphones while listening music, to answer the phone.
same problem here ...
My phone also started having the same problem since today morning!
EDIT: So I tried to remove battery, then cleaned the micro-usb port and the headphone port and the issue seems to have disappeared atleast for now. Don't want to do a factory reset as have too much data and apps on phone.
EDIT 2: So as it turns out it was Go SMS Pro problem that was causing the issue since its update 2 days back. The developer has released a new version in Market now claiming to solve the issue.
Anyways whatever issue it is hope it does not return.
Hello. My problem is with the phone's vibrator. 2 or more weeks ago I got the same problem, when I dropped my phone from the bed tot the floor (aprox. 40 cm height), it stopped vibrating for feedback, messages and calls. At that time, I thing I either turned it off and removed battery or just do a reboot, but it started working again until 3 day ago. Since then it stopped working completely. I tried turning it off, reboot, removing the battery for 15 min., nothing worked. I have no vibration feedback (for example when I type a phone number or message), no message receiving vibration, no incoming calls vibration and not even when I turn on/reboot the device does my phone vibrate(it was a small vibration when you turned on the phone). Today I thought I should first try to change my ROM prior to trying to replace the faulty vibrator, but when I selected to reboot to recovery, my phone rebooted and vibrated at the beginning, so I thought the bug is gone. I went back in to the phone and I had: vibrate feedback (typing a phone number), message vibrate, didn't have time to test the call vibration because after I received 2 messages the vibration stopped once again. So now I'm baffled: is it because of the ROM, is it a glitch/bug from the motherboard or is the vibrator almost "dead"? If anyone had this issue and can help me fix the bug I would be really thankful. If I have to replace the vibrator, it wouldn't be a hard thing to do and I would do it if I know this will fix the problem forever.
My phone is S-OFF, rooted, with AcesMod007 ROM. Thank you.
I have installed CM10 | Jelly Bean 4.1.2 - v2.8 by vijendrahs and still no vibration, so it must be from the motherboard or the vibrator itself. I might try to replace it and see if this solves the problem.
No one has encountered this problem until now? No thoughts on this? I've searched for this bug and found some applications that should remove this bug, but they didn't work for me, so I am still open to any suggestion. I still have to wait up to 3 weeks until the vibrator arrives.
L.E.: I've just noticed another anomaly: my phone jumps from 82%-85% battery to full when I'm charging it. Might this have something to do with the vibrator? How can I fix this problem? Thanks.
Tried all kinds of applications that would force the vibrator, but with no success. I am still looking for a solution.
I have no guarantee so I have to fix it myself. I saw that other peoples with the same problem had sent the phone back to HTC for a replace. One of them actually stated that HTC had replaced first the motherboard (with no success) and then the vibrator module. I hope that replacing the vibrator would solve the problem.
I've solved the problem. I decided to open it up, thinking it is a hardware problem, and take a look at it. I've blended the two legs a bit more to make sure they get a perfect connection to the the motherboard and voila. It is working fully.