So my Incredible just recently and randomly started to make a clicking noise. It happens when the screen is on at 1 second intervals and for a while after the screen is turned off as well. It's not a software sound but a sound from inside the phone. Its an amoled version running CM7 and other various customizations. I was wondering if anybody has ever had this happen and if it is something I should be worried about? Also, I'd like to know the cause and how I can stop it from happening.
Does your phone still vibrate? If it doesn't it might be the mechanism inside.
Sent from my sexy assistant. (AMOLED HTC Incredible)
It does vibrate as normal. Everything works just as before but I'm curious to know what it could be.
PitaBlackZ said:
It does vibrate as normal. Everything works just as before but I'm curious to know what it could be.
Click to expand...
Click to collapse
has it ever gotten wet? maybe something fell inside the the phone and is now shorting it. do you have insurance?
maybe take it apart and see if there is anything floating around.
No, its never gotten wet. It doesn't sound like something is rattling inside. I could be wrong but I think its got something to do with overclocking it. When I turn on the screen it instantly starts clicking sometimes fast but moslty at 1 second intervals. When I shut the screen off it usually stops instantly. Sometimes it clicks for a short while afterwards. The sound is like a clock ticking. Unfortunately I don't have insurance.
PitaBlackZ said:
No, its never gotten wet. It doesn't sound like something is rattling inside. I could be wrong but I think its got something to do with overclocking it. When I turn on the screen it instantly starts clicking sometimes fast but moslty at 1 second intervals. When I shut the screen off it usually stops instantly. Sometimes it clicks for a short while afterwards. The sound is like a clock ticking. Unfortunately I don't have insurance.
Click to expand...
Click to collapse
I had a computer that did that exact same thing. Windoze machine, actually. Some BS process was running in the background that kept doing something that used that sound effect. Is it like the sound used when you have audio feed back turn on for the keyboard? I definitely think it's a software issue, not hardware, so it's probably fixable in some way.
Is it the same clicking noise like when you open up an app that uses your camera? I know whenever I open up the camera, bar code scanner, etc I hear a clicking noise. Not sure if some app keeps trying to access the camera and maybe that is where it is coming from?
I bet its the camera being used for some background app.
Is it the same quiet click from the camera you hear when the phone boots up?
The clicking stopped yesterday just as randomly as it started. It didn't sound like the sound the camera makes when started. It actually sounded like a clock ticking. Its very odd.
I had that happen on my evo. Soneone mentioned that it was an app that was bugging and it was causing the touch panel in the lcd to think it was being touched. But android wasn't handling it properly so it caused a ticking noise to come from my speaker. I just wiped and reinstalled my rom and it went away.
Sent from my Recharged EVO.
Interesting. The sound didn't seem to come from the speaker in my Incredible but I can't be 100% sure. I haven't uninstalled any apps nor did I download any new ones before the sound started. Very strange stuff lol. Althought its since stopped, I'd still like to know what it was. I'm sure it was an app but.I don't have a clue as to which one.
as long as its not damaging the phone its fine
The phone seems to be perfectly fine thankfully. Guess I'll never know what it was. Oh well... thanks to everyone for the input.
Related
1.Anyone notice the loud hissing sound from the (CDMA) radio when using android? If you don't put it next to your ear and you can hear it. It makes no hissing sound what so ever when I'm in windows.
2.Also, the phone gets verryyy warm when running android. I did not overclock or modify anything. Everything is stock from the 6/01/10 release. When I switch back to windows the phone starts to cool down
I've been switching between this build of android and windows for the past couple of days. These two symptoms will keep me away from android until maybe the next build. Also, worry that the symptoms might damage the phone. Is anyone else experiencing this issue? btw it's a Sprint Touch Pro 2
The hissing is the speaker. The sound isn't working and is constantly in call mode for sound.
As for overheating, I have yet to have an issue with it.
Thanks for the reply. Do you or anyone know of a way to turn off the hissing sound?
edit: never mind I think I may have found the solution to my own problem regarding the hissing sound.
I deleted the command "Enable External Speaker - external.rhod_speaker=1" and the hissing sound has now stop
Does disabling that give you longer battery life?
I didn't notice any difference in battery life but I don't see why you would want to enable external speaker anyway. The feature doesn't work in this build
I also notice my TP2 being stupid hot kinda like when I talk on it for over an hour. My actual problem was that the keyboard back light was not turning off when I closed the keyboard. To fix this just don't slide open the phone before switching over to android.
gface2k said:
I also notice my TP2 being stupid hot kinda like when I talk on it for over an hour. My actual problem was that the keyboard back light was not turning off when I closed the keyboard. To fix this just don't slide open the phone before switching over to android.
Click to expand...
Click to collapse
To be more specific I think if any of the backlight is on while you are in windows, it will stay lit when you boot into android. To fix this make wait till all the backlight turn off then boot into android
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
gthing said:
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
Click to expand...
Click to collapse
That is the most intense thing I have ever heard ever.
I'd root that baby. Maybe an Android "virus"?
jigglywiggly said:
That is the most intense thing I have ever heard ever.
I'd root that baby. Maybe an Android "virus"?
Click to expand...
Click to collapse
i dont believe android phone has viruses....maybe just program errors.
Its a ghost.
campchi said:
i dont believe android phone has viruses....maybe just program errors.
Click to expand...
Click to collapse
no viruses, YET!
gthing said:
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
Click to expand...
Click to collapse
ok, first off...
secondly, your thread title alone is tempting enough for me to post a reaction.
thirdly, maybe there's a delay in your screen touch input? or maybe someone has remote access into your evo? (this is going to make me sound dumb and ignorant, but please bear with me).. i know there are ways to get access into iphones to control them via commands through text messages. maybe that's happening with your evo?? again, i'm almost embarrassed to even be entertaining this idea since android is quite locked down in its nature, but it's the closest thing i could think of as a possible cause besides paranormal activity.
...which, in and of itself, sounds so awesome and creepy.
I had similiar things happen when using any custom rom based off the new ota..
Its something with the screen sensitivity they changed for the ppl who were having grounding issues..its the only thing I can think of..
I think I also have a paranormal situation of my own! Well maybe, but its very curious... A certain phone number/friend of mine has told me that my phone is calling him while my phone is completely idle. This has happened twice in the last 10 days or so. The first day he missed the call, the second time he was able to answer it and it was dead air. My phone was never touched; it was home alone the first time and it was streaming bluetooth music the second time. I know this sounds absurd, but unless it starts happening more frequently I guess I'll just deal with the mysteriousness of it all.
oOflyeyesOo said:
Its a ghost.
Click to expand...
Click to collapse
the ghost would have to use a hot dog for the screen to recognize him/her LOL..
i myself dont believe in ghost but thats trippy.
lol a floating hot dog typing things by its self. WTH I just laughed out loud and nearly woke my wife up. That was funny if you picture it in your head lol.
When i got my first Vogue, it would do that. Randomly resend text, send garbled text, and call people. Without any interaction whatsoever.
Sent from my Evo using XDA App
That is hilarious. I would have freaked out seriously. Is your phone rooted?
My phone is not rooted and was running stock with the latest OTA. I am leaning towards the theory that it is something to do with the latest OTA which addressed the grounding issue.
I enabled a password on my phone. Last night I kept hearing these little noises, like a bug beating its wings in really quick, short durations. I was looking all over before I realized it was coming from my phone. Face down, on my nightstand, it was randomly pressing buttons on the password screen and I was hearing the short vibrations of the tactile feedback. It had done it enough that I was locked out and had to wait 30 seconds.
Something's not right in Evo land.
You definitely need an exorcists.
Since you live in UT, I am sure there lots of Mormon High Priest that can help you out.
Good luck.
gthing said:
My phone is not rooted and was running stock with the latest OTA. I am leaning towards the theory that it is something to do with the latest OTA which addressed the grounding issue.
I enabled a password on my phone. Last night I kept hearing these little noises, like a bug beating its wings in really quick, short durations. I was looking all over before I realized it was coming from my phone. Face down, on my nightstand, it was randomly pressing buttons on the password screen and I was hearing the short vibrations of the tactile feedback. It had done it enough that I was locked out and had to wait 30 seconds.
Something's not right in Evo land.
Click to expand...
Click to collapse
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.
So I am hoping someone with some real hardware/software knowledge can provide some input...
I recently received my warranty replacement unit because of unresponsive touch and phantom touches. My new unit seems to work perfectly, except now every 10 to 20 touches, the touch will register, but the touch sound "click" doesn't play (if I put my ear close to the speaker, I can hear the speaker activating though). Repeated touches (like repeatedly pressing back) won't reproduce the problem, but more random timing and touches (like in regular use or typing) will. I'm wondering if anyone thinks this is a hardware issue, or some component of the stock software that wouldn't have been overwritten between the update to JSS15Q, and then to JSS15R (it happens in all three versions).
Think I should go for another replacement? Or do you think I should root and unlock, and see if a full installation of a ROM fixes it. It's definitely a sign that something is wrong and it's annoying, I just can't figure out if it's software or hardware related. I'm definitely not going to just ignore it.
(SIDE STORY: When I called nexus help for my first unit, the guy was so helpful and took my word that I had already tried factory resets, and set me up for an RMA. My call on this unit, the woman told me to reboot and toggle touch sounds, and kind of rudely insisted that I was on 4.3 and that Build Version (e.g. JSS15R) had nothing to do with software!! :what: She then told me she'd send me an email with more troubleshooting steps, which never came. I had figured I'd wait for the email, so that I had her name for my next call. Totally unacceptable.)
You come off as just looking for a reason to complain at this point, there doesn't seem to be any real problem with your device other than you being overly picky
Sent from my HTC One using Tapatalk 4
You're completely right. I was so delighted when I managed to find something wrong with my new tablet...
Seriously? You come off as just a worthless ass of a poster at this point. The problem is there, and can be consistently reproduced. I press home and it clicks, and five seconds later I press home and it doesn't click. Your opinion on whether this is a "real problem" or me being overly "picky" is completely irrelevant. It is most certainly real and not normal, and indicates either some software or driver bug on my device, or a strange hardware malfunction. My previous unit (which had very real problems) did not have this problem.
I hope I speak for others here, when I tell you to **** off unless you have something worthwhile to contribute. Just because you don't think something is important, annoying, significant, etc. doesn't make it any less so for someone else.
Do you have this issue with SwiftKey?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yeah. It's actually everywhere throughout the OS. System settings, stock launcher, Nova launcher, Swiftkey, AOSP keyboard, etc.
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
GoneTomorrow said:
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
Click to expand...
Click to collapse
Exactly my thoughts on going through another RMA. But I do feel that it's reasonable to expect a properly functioning tablet on our parts. What you're experiencing is strange. I can tell you that on my Optimus G, when muted, I can hear a faint speaker "activation". Sounds like maybe yours is a hardware issue. Are you stock, or have you tried flashing other ROMs?
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
FYI: I've seen this on multiple tablets (TF101, GTab, Nooks, 2012N7, 2013N7) with different customed ROMs.
So, I wouldn't blame it specially on the Tab. In fact, I see this issue less often on the 2013N7. It usually happens
after I just freshly loaded a new ROM.
spackmanbr said:
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
Click to expand...
Click to collapse
So a couple of nights ago, I decided to try disabling touch sounds in settings. Since doing that I haven't heard a single pop from the speakers. Looks like it was either the touch sounds 'leaking' or the speakers popping from being activated, which they do even when muted (the mute being software)
I'm quite happy with this fix, since the tablet is muted 99.5% of the time, and I don't care for the touch sounds anyway.
Hi Folk's,
Sorry to drag up an old post, but I've noticed my N7 shows this behaviour on KitKat as well.
It misses the touch sound if you pause for about 5 secs during input. Does it every time and it's very annoying. I've tried a couple of different KK roms and it does the same on all of them.
Just tried going back to CM10.2 (JB 4.3) and it works fine!
Does anyone know the cure for this, apart from going back to JB, please? Would really like to be running KK, but this bug is bugging me!
Thanks for any info.
Cheers
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Petermira said:
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Click to expand...
Click to collapse
@Petermira @Xi2or @spackmanbr
I have this same behavior on a stock 4.4.2 S3.
After 5 seconds, if I click anything UI (keyboard, Soft buttons, shortcuts, toggles) there is no sound. If I quickly click again and keep clicking, the sounds work as normal. It's definitely ROM related but is there a fix???
UPDATE: Issue does not happen with headphones plugged in. STRANGE!!!
UPDATE: Issue does not happen if I keep a song playing in Power Amp or similar.
Affected UI items include:
- keyboard
- shortcuts
- toggles
- capacitive buttons
- dialer pad
- etc.
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.?