Now, im very aware that this could turn out to be an absolute no-brainer question that can hopefully be resolved by some simple change within the settings, but I've looked through all the sub-menus and I cant seem to find why my HOX makes the noise.
I restarted the device, and the noise was gone... but then 8 hours later, everytime I unlock the screen, it makes the noise. Same when it comes to unlocking it.
But there are other occasions when it doesn't... does anyone have any ideas?
EDIT: it's not the 'screen unlock sound' incase you are wondering.
Related
I have a problem that more people seem to have, according to the search. I couldn’t find the “audio” tab in my Bluetooth-settings, so that didn’t help me.
The problem is as follows. After 1 day the sound on my compact III mutes, including vibration. Sometimes it's after 12 hours, sometimes after 2 days, there's no distinct pattern to be recognized. Also, it doesn't seem to matter if you use the phone or not, since it sometimes is alright at night and the sound is muted the next morning. This is for all sound-events (warnings, incoming call notifications, messages, mp3 etc), however, you can make a call without any problems and hear what the other person is saying. Once you’ve hard-reset the device everything is back to normal.
It does get annoying however, since I regularly miss calls due to this bug.
I had the same problem on my Vario in the past. So I’m guessing it’s somewhere in the software I use, but apart from Total Commander and TomTom6 I haven’t installed any third-party apps.
Yup i've been having a slight problem with the sound. I thought it was like the endless knackered M500's that orange used to send me which had speaker failure after about 10minuites! (Swear they kept sending me the same 2 faulty phones - I had 5 in 5 days once!) But a play in the bluetooth seems to get it working again.
The other annoying thing is that if you leave the power management at the default settings then occasionally the screen blanks without being able to get the backlight on again - so now I have to manually turn of the screen. Stil aint much of a problem - ive had a normal days use, 2 hours of radio play, bluetooth and wi-fi on all day and still have 35% battery - wehay!
Hopefully there'll be a patch soon to sort out he glitches.
I forgot to mention I had the exact same problem on my mda Vario also. I always thought it was a problem with that specific piece, but apparantly not.
Could it be the vibrate.cab that I'm using to produce vibrations when you use the phonepad? Or should I really do some further research in the bluetooth-department?
Same problem here.
Phone becomes completely silent after 9 hours in standby mode.
I need to reset it to get back sound
Does someone know what is going on here ?
Please advise. Thank you.
I seem to experience no problems the past couple of days (fingers crossed). I used the 'speed up your WM5' tweak where you set the Glyphcache to 32768. After I reduced it to 16something the problems seem to have disappeared.
I noticed that this problem happens when for example email is automatically checked during night. If email comes in (and is not read immediately) the phone will start notifying in background.
Notifications are kept and only a program like "check notifications" will delete them manually. But still if you delete them, the phone then needs a reset
to work properly again.
This is not a memory issue, it has to do with the notifications.
I do not know how to solve it.
I'm about to make myself look very stupid with this...
I've been using DeFroST for ages now and just come across a problem that's driving me mad. I've suddenly got a selection of incredibly annoying sounds that I just can't seem to turn off.
When I unlock or drop down the notification drawer there's a shrill 'ding'. Selecting the app drawer or select a check box there's a "thock" noise. (don't laugh at my descriptions!)
I've had the phone on silent yet these noises still occur. Volume doesn't seem to affect it either. I've performed a full wipe and re-installed the ROM yet they're still there. I also can't find any option in the menu to turn to damn things off.
Can anyone let me know if they're also having the same noise, and more importantly, how can I get rid of them, they're driving me mad!!
Should've posted in the ROM thread - would get more replies
I'll be honest, I've done it in both.
Alright, I've spent all day searching and can't find a clear answer for what I'm looking for.
Just last night my keyboard and lock sounds are very quiet, now I've seen others with this issue, but I haven't seen anyone explain why this happens or how to fix it.
So does anyone know how to fix this, or have I missed it in my searching?
lolwut. Are you talking about the audio output from the keyboarD? Like when you type it makes that noise, and now that noise is quiet? I think its tied into your general phone sound level. Check your settings under menu-settings-language & keyboard-touch input
Yea, all sound levels are at max and the other sounds ( ringer, text, emails, ect...) still play at proper level. But the keyboard clicks when typing and the screen lock/unlock sound is still there, but just barely making any noise
nobody's got anything?
also last night to took my friend's evo and his is doing the same thing, he said he noticed it soon after the 3.70 update
This just happened to me. I fixed it with a hard reset of the phone. I had to reload the few apps I had and sync my google calendar and contacts. Back in business. Have no idea why it happened in the first place, but they are working now.
i have to say, i never really liked the hard reset idea so i never did it. today i let the battery run until it shut off the phone, i then pulled the battery, put it back in and then charged it full before turning the phone back on. and now my clicks have returned
I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.
Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.
I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.
I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.
bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.
Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.
The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?