Just today, out of nowhere my iMate Jam just stop having sounds....
Its strange, the volume level is always at 0, no matter what I do to raise it up, it will turn back to 0
Also I m very sure its not an hardware issue, because the speaker phone works perfect while I turn the speaker phone on...
Its just the volume always stuck at level 0
I try soft reset couple of times, it didnt work... its still at 0
I have no program open at the back that could set it back to 0
So does anyone experience this before?
To describe, its like the unit is "force" to have the volume level at 0 at all time
:?:
Hi
had a problem with sound, but it was down to the headset jack, phone is been repaired by HTC.
Do a full backup via active sync, then do a hard reset see if that solves the problem. you can the restore the backup.
still have the same problem...
I was thinking not to hard reset
But if all else fail, I think I must
I am guessing something was mess up in the registry from installing/uninstalling program that I try
Had the same prob. yesterday. Uninstalled the latest programs hacked several reg. entries nothing helped. Hard-reset solved it finally & sprite did the back-up trick so no harm done whatsoever in the end.
Only not satisfying that I couldn't pinpoint the failure.
Cheers, M
Related
Suddenly I have lost all telephone comunication. The XDA still rings, but I have now the mic and sound. The volume adjuster on the side also seems to not be working. The screen tap sounds have also disapeared. Can anyone help?
i'd try software and hardreset before writing it off as a hardware defect
the fact that screentabs also dont give a sound would prob mean that
it's not the gsm sound which have been broken
OK, I have now tried both software and hardreset but still now luck. Although the volume does seem to come back intermitantly. Do you think formating and re installing software will help? If so, how do I do it?
When I am on a call the backlight on my Touch Cruise turns off - I don't mind this. The problem is that when I try to turn it back on it is extremely dim (even if the backlight setting is "bright") and I need to use "Adjust backlight" to make it brighter. In sunlight this is almost impossible to do since I cannot read the screen. Even after I readjust the brightness, whenever the backlight turns off and I turn it back on, the backlight is dim again.
I have tried renaming the \HKCU\ControlPanel\Backlight\LockLevel folder to LockLevelx - this has not worked.
I have tried setting \HK:M\Drivers\Builtin\RIL\EnableFastDormantDisplayDuringCall to 0 - this has not worked.
Help please!
Do you have this problem all the time or you can see this misbehaviour just now?
I'm asking, because this could be caused by some other software you installed on your device,
which does some "things" with the backlight or some call manager like PhotoContacts etc.
This happens all the time. It does not happen after I soft reset the device until I use the phone. As soon as I use the phone the backlight turns off and is dim whenever I turn it back on.
- Are you running some "cooked" unofficial ROM?
- if you are using HTC Home, try to deactivate it, just choose some different homescreen schema but not HTCHome, make a soft-reset a try it.
- check HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel\LockLevel - this should have the value 0
- running standard ROM
- deactivating HTC Home doesn't help
- LockLevel is set to 0
This periodically happens on my device too. And it's really, really annoying. I found that one way to make it go back to 'normal' for a while is to change both lock levels (in locklevel and locklevelx to value 1) then back to level 0 (including the waiting and the soft resets) and then it seems to go back to normal again.
what seems to set it off for me is using the call history to dial a number, but this is sporadic.
Thank you Marissa and Hujer. Unfortunately both your suggestions have not worked.
I have had the same problem. What helped in my case is deleting locklevel and locklevelx from the registry and then soft reset. Worked for me!!
Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.
sclhtc said:
Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.
Click to expand...
Click to collapse
Exact same happens to me, using Bepe 64 rom. Real pain in the neck.
Possible workaround
This sounds very much like the same problem Trinity users have faced since that device was released. Try searching the Trinity Forums. There was a reg fix...something to do with "fast off" or similar.
The workaround there was, after the phone call, to press the power key to put the device into standby, and then when it wakes the next time the backlight is restored. Try that anyway.
No luck with this either.
I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??
Tim B said:
I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??
Click to expand...
Click to collapse
Exact same happens to me, using official rom.
I had to do a double reg edit, try this which is what I use:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableFastDormantDisplayDuringCall"=dword:00000000
[HKEY_CURRENT_USER\ControlPanel\Phone]
"Sleep"=dword:00000000
Reboot!
Thanks but that didn't work either.
Just to be clear I do not mind the backlight staying on, dimming or turning off during a call but when I press "Call End", the backlight dims (which I do not want) and if the backlight turns off after a call it is dim when I turn it back on (which I also do not want).
Did anyone find a solution to this?
Have tried all the things on here, and some work for a little while, but then the problem reoccurs
Wow, this is so strange. Mine comes back on at the same brightness level.
You all are experiencing the same thing as Marisa?
It is an odd problem because it seems that it occurrs all of a sudden out of the blue.
One time you make/receive a call and afterwards, even if the call was only a few seconds, you terminate it and the screen either is already dim or then dims and will stay dim unless you hit a backlight changer. Even then, if you lock the phone, or the phone dims after your prescribed time, it then stays dim. The only way to temporarily fix it is to set it to the normal level and then soft reset. It will then behave properly until the next phone call.
It is very inconvenient as if it locks while this is going on, you can hardly see to unlock it.
I have trawled the internet for hours looking for solutions to this. The Kaisertweak does not work for this on this device (don't know why!) Installed Schapps but the very tweaks I need do not appear when installed on my device.
All the registry edits don't work. In fact when I go to do them, the value is already at the recommended value anyway. Renaming locklevel seems to work sometimes for a while, but then reverts back.
I think it is more a problem of undimming than dimming. It dims when I expect it to dim, but does not light up again afterwards. The Kaiser solution of pressing the power button or d-pad to do this does not work on the Orbit.
I have a fairly non scientific feeling that it's something to do with either Shell, Pontui or Co-Pilot. I have uninstalled Shell & Pontui, but it has made no difference. Makes no difference either if HTC Home is/isn't installed/running.
Another strange thing is that when it is in its dimmed state, I only have to touch the page where the backlight slider is for the light to come back up. I don't need to touch the slider at all, it's already where it should be, 3/4 of the way up.
In fact I have done the registry tweak which is supposed to stop it dimming during calls altogether, and checked to see that it 'took' and it is still happening.
Somewhere, there must be a registry key or somesuch which controls what happens after this "temporary" dimming, which says, the call is over/the device is unlocked - go back to prescribed brightness. But I can't find it.
This is a really insidious problem which drives you mad, especially when you are out and working, you don't have time for this nonsense. If all else fails in a week or so I will try a hard reset, i just don't have time right now.
Any help gratefully received.
I have just emailed O2 with this problem. Let's see when/if they reply.
Hi everyone,
Im facing a very unique and highly irritating problem on my phone. I own a HTC P3350 (Love) handset with a built-in WM6.0. It was working fine till yesterday. Suddenly since this morning whenever i switch on my cell or get a msg or miss call, the dialer screen comes on. (Its as if the green dialer button is stuck, i checked if thats d problem, but that isnt the case).
I even restored my registry and stuff from an old backup i had made. Even that didnt help.
Is it a hardware or software problem? What should I do about it?
All suggestions are welcome. Please help me.
Welcome to forums
Perhaps a hard reset could help
Good luck,
@orb3000: i tried hard resetting too, twice actually. But the problem wasnt solved. Any more ideas??
another thought crossed my mind. What if i assigned some other action to the dialer button and see if it still persists?? i can then rule out if its the hard button problem.. Think it'll work??
The best way to know is testing it!
And what happen if you remove your SIM card? problem persists?
Ya it persists even if sim card is out. Im so frustrated that i'll start plucking my hairs in some time. If a msg is open when i switch it on, it starts dialing d no automatically. Its so damn problematic.
Will the company repair or do something about it? Its 8 months old..
Could it be a virus??
Sorry I dont know what else to recommend, but hopefully another more experienced member can give you better advice.
Be patient!!
oh.. thanks all the same..
can u do me a favour and try to boot the phone up wth the headphones plugged in???
no that didnt work either,,
i just hard reset my phone and i have removed the storage card from the slot. i have not restored from my backup nor have i synced yet. my phone is as good as new with no contacts or appointments. And now the problem has disappeared!! But that doesnt help coz at some point of time i'll have to restore my device which might bring back the problem.
are you using the ones that came with phone and do they double up as handsfree
my line of thought as i had a kaiser with a headphone fault were the wires that made the button to call work were faulty
this meant that everytime the headphones wires were twisted a certain way the dialer kept popping up and dialling numbers
so thgere fore if ur handsfree was connected and then the phone came up without dialer this would mean that there is a hardware fault
my only suggestions now is to flash to a different rom
if the problem persisits then its a hardware fault and youll need to contact vendor or seller
i just hard reset my phone and i have removed the storage card from the slot. i have not restored from my backup nor have i synced yet. my phone is as good as new with no contacts or appointments. And now the problem has disappeared!! But that doesnt help coz at some point of time i'll have to restore my device which might bring back the problem.
Hi everyone. Thanks for all your suggestions. But none of them seemed to work. I'll just write my problem in detail once again:
My phone - HTC P3350 (Love) with WM 6.0
ROM version: 3.17.720.3 WWE
ROM date: 21/01/08
Radio version: 02.94.90
Protocol version: 4.1.13.44
ExtROM version: 3.17.720.103
My exact problem -
1. Whenever i bring back my phone from stand-by mode by pressing power button, the green call receive button somehow gets pressed from the 'inside' and depending on what window is open the action takes place. For eg: if im on my today screen, the dialer screen opens up; if im on the dialer screen, the last dialed no starts getting dialed; AND THE WORST PART - if someone calls me when my phone is on stand-by mode, the call automatically gets received (coz the green cal receive button virtually gets pressed)!!
2. The super-added problem is that if i press the power button to put the phone into standby when im talking to someone, the speaker phone gets activated and then exactly 3 seconds later the call hangs up.
The problems are so weird and 'funny' that im getting to think its a virus doing all this.
What i tried doing -
1. i hard reset my phone and restored using sprite backup. The problem persisted.
2. So next i hard reset again and restored using PIM backup and restored only the contacts. The problem disappeared for a day but reappeared.
3. So i hard reset again and this time i didnt restore and i also removed my storage card. And now the problem has become unpredictable! It appears sometimes and sometimes the phone is completely normal.
Im trying hard to find a pattern as to when it appears for eg: whenever the battery is low; only during the evening, etc. I dont know but i've not found out any fixed pattern (which i expected if it was to be a virus)
My current status -
I disabled the 'Turn off device if not used for' option in Advanced Power settings. And i never put my phone on standby. I just use the device lock option. But the problem is that battery running out twice faster.
This has just temporarily treated the problem but the basic problem still remains....
My Touch Pro of 12 months has decided that to continuously run the vibrator. I have tried a soft reset without success.
Can anyone advise me how I might stop this without a hard reset.
Sorry - but unless you have a reason why its constantly vibrating (ie you messed about with some settings, or it started after you installed / uninstalled something) then you dont have many options:
1) Do something to make the phone vibrate, then stop it and see what happens (although i guess you have already done this).
2) Remove the vibrate motor (a little extreme!)
3) Do a hard reset - obvisously you will have backed up all your data, so whilst a hard reset will be an annoyance, it wont be the end of the world.
Finally - and this might be bad news!
When you soft boot the phone it (should) vibrate then stop.
What does yours do? Does it vibrate as soon as the phone is powered / restarted? or does it wait until its booted into windows before it goes crazy? (1st sounds like hardware / water damage, 2nd more likely software - hard reset should fix).
If you can still run it ok other than the vibrating, try installing SPB Backup (not free, but the trial should work for this). Run the full backup, saving on your computer, and do a hard reset, then reinstall spb and restore from the backup. If it continues to vibrate, it is probably a setting, somewhere, that is bugged/messed up. You can also check the various notifications to see what all has vibrate set, it is possible that something as simple as continuously detecting wifi and being set to vibrate to tell you that. Of course, check that before doing the backup/hard reset/restore, if you haven't checked it already that is...
I know a girl who'd prolly buy it...haha
Hello guys, first post here.
So I have this problem with my Z1c: When my headphones are connected, the notification volume goes all the way up and when I am listening to music, the volume of it randomly goes up and down (without me pressing any buttons). Also, the power button stops working, I can't turn the screen off.
I think my phone is recognizing my headphones as a headset (Smart Connect says so) and it thinks I am pressing some non-existent buttons.
I have tried disabling Smart Connect and even factory resetting my Z1c. Neither has solved the problem. Is the headphone jack busted?
By the way, the problem exists with both my in-ears and over-ear headphones.
I haven't found anything online about this particular problem.
Thanks,
Wouter Vork said:
Hello guys, first post here.
So I have this problem with my Z1c: When my headphones are connected, the notification volume goes all the way up and when I am listening to music, the volume of it randomly goes up and down (without me pressing any buttons). Also, the power button stops working, I can't turn the screen off.
I think my phone is recognizing my headphones as a headset (Smart Connect says so) and it thinks I am pressing some non-existent buttons.
I have tried disabling Smart Connect and even factory resetting my Z1c. Neither has solved the problem. Is the headphone jack busted?
By the way, the problem exists with both my in-ears and over-ear headphones.
I haven't found anything online about this particular problem.
Thanks,
Click to expand...
Click to collapse
Haven't ever used smart connect myself, but there's obviously bugs with it, (quick search turns up pages of complaints on Sony forums). Seems like one of those things they just didn't get right, in general. Since it's persistent after hard reset, my guess is hardware, but just to be clear - when you did a factory reset, it still did the same thing right off the bat, without you adding or tweaking anything, right? Also did you just factory reset, or did you reflash the rom? If it's a problem with the system flash, a reset won't change it.
I would try to reflash system, and see if the same. Also, are you rooted? You can try removing smart connect app, etc. (make a backup)...
Also, have you seen this - https://play.google.com/store/apps/...key&pcampaignid=APPU_1_kgNwWerXJYbf-QHv8Jy4Aw
levone1 said:
Haven't ever used smart connect myself, but there's obviously bugs with it, (quick search turns up pages of complaints on Sony forums). Seems like one of those things they just didn't get right, in general. Since it's persistent after hard reset, my guess is hardware, but just to be clear - when you did a factory reset, it still did the same thing right off the bat, without you adding or tweaking anything, right? Also did you just factory reset, or did you reflash the rom? If it's a problem with the system flash, a reset won't change it.
I would try to reflash system, and see if the same. Also, are you rooted? You can try removing smart connect app, etc. (make a backup)...
Click to expand...
Click to collapse
Thanks for your reply levone,
Smart Connect was working flawlessly for me since i got the phone which was a couple of years ago, but unfortunately these last few days I have run into this problem. My phone isn't rooted, so I can't remove it. (it's a system app)
I just did a factory reset, not a reflash, and it did the same thing right off the bat. I don't know how to reflash, so I'll have to research that if the problem persists.
I will try the Smartkey app, thanks for that.
Alright, I tried Smartkey, the problem is still there. Next I tried reflashing the ROM, the problem is still there .
Next I tried disabling Smart Connect and installing Smartkey on the reflashed phone, just to see if it did anything, it didn't.
So, this must be a hardware problem, right? Headphone jack busted in some way?
Appreciate your thoughts,
Hello,
i had also issues with the headphone jack. In mine were fluffs (lint, dust - not my native language, so sorry for using bad words).
after removing there weren´t any issues.
Greetings
I had the same problem. Replacing the headphone connector was the solution, in my case of course. But you could first try to clean connector. If problem persist you have to change definitely the connector.