Hi everyone, I'm hoping someone can help identify exactly what is wrong with my phone.
I got stuck in the rain with my phone in my pocket last week, and i noticed the screen acting up, so I turned it off and left it in rice for a few days. The phone continued to work afterwards with no real issues (except for slight color distortion that isn't very noticeable). A week later I decided to try to fix the color by cleaning the motherboard with alcohol to get rid of any corrosion, after this my mic stopped working (both while in speaker mode and not) when in calls, or trying to record using an app. However, it works when using whatsapp's voice feature.
Any help would be appreciated!
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.
Just got my N7 a few days ago, loving it so far with the exception of having annoying audio feedback when either waking the screen, locking it, or receiving a notification. It doesnt happen all the time, but it has occured at various audio levels (Googling around on the issue a possible fix was to not have the volume on one of the bottom two settings).
By feedback, i mean the static sound you get normally when a mic is placed too close to a speaker.....Is this a faulty unit? Bad flash (It was updated OTA when I got it, have not done anything since getting it). Is it worth taking time to reflash it, or should I put it to stock and go swap it from where I got it (Purchased from BB, so return of it being faulty wont be an issue).
Thanks for the input, didnt see anything on search for "audio feedback".
Thoughts anyone?
I'd return it, that does not sound normal.
Thats what I was thinking, going to wait for the black friday / cyber monday rush to be gone, wanted to make sure it wasnt just a bit of over reacting on my part.
Thanks
For anyone who sees this with the same issue, I seem to have found it only occurs when the nexus 7 is in the Play Books app (I use it as an e-reader mostly atm, so its always being woken up when in that app).
Hello
I am hoping that someone wise and experienced could assist with this problem that I think is off my own making.
Phone: LG G3
Rooted: No
Android: 5.0
Today I replaced a broken screen and digitizer and the earpiece now appears to be broken. The screen is working fine and has full functionality prior to the break.
The sound however was not working at all - calls or video playback. After opening up the phone again and re-setting the earpiece video playback was working although calls were still faulty. I then checked to see if it was working with speakerphone and it was. Tried resetting again thinking maybe one of the two prongs still was not connected - no improvement.
As it took me 3 weeks to get round to repairing it there were 40 apps to update so not sure if something in this has conflicted and stopped it working but that feels like clutching at straws rather than the likely answer that I have broken it.
Anyone know a possible fix please?
Thanks
Boo-Urns said:
Hello
I am hoping that someone wise and experienced could assist with this problem that I think is off my own making.
Phone: LG G3
Rooted: No
Android: 5.0
Today I replaced a broken screen and digitizer and the earpiece now appears to be broken. The screen is working fine and has full functionality prior to the break.
The sound however was not working at all - calls or video playback. After opening up the phone again and re-setting the earpiece video playback was working although calls were still faulty. I then checked to see if it was working with speakerphone and it was. Tried resetting again thinking maybe one of the two prongs still was not connected - no improvement.
As it took me 3 weeks to get round to repairing it there were 40 apps to update so not sure if something in this has conflicted and stopped it working but that feels like clutching at straws rather than the likely answer that I have broken it.
Anyone know a possible fix please?
Thanks
Click to expand...
Click to collapse
perform a full reset and you will know if it is an app or you who proke it
A few weeks ago I bought my wife an used Asus Zenfone 2 (ZE551ML - Z00A) and I installed LineageOs on it. Since then the bottom microphone stopped working.
I make a call to other phone and only the top mic picks up the conversation, meaning that the person on the other side barely hears me, and in fact hears me better if I speak with the phone flipped up side down.
Now, I know that you're thinking that most likely its a hardware issue, and with that in mind I bought a new bottom board (which contains the charging port, mic, etc), but when I swapped it it the problem persisted. After that I assumed that the problem was in the rom itself, so I installed 3 other images with the same results... So i got on google and searched a bit, and it seems that i's a common condition on this phones.
I think the problem might be that the call manager mistakes the mic1(top) and mic2(bottom), because in the calculator tests the 1st passes but the 2nd fails.
Another option would be to try this, however I can't find this option in any of the images I've tested: https://www.youtube.com/watch?v=Ocm_WX-ilE8
Does anyone know how to solve this? Thx.
Drydenmike said:
A few weeks ago I bought my wife an used Asus Zenfone 2 (ZE551ML - Z00A) and I installed LineageOs on it. Since then the bottom microphone stopped working.
I make a call to other phone and only the top mic picks up the conversation, meaning that the person on the other side barely hears me, and in fact hears me better if I speak with the phone flipped up side down.
Now, I know that you're thinking that most likely its a hardware issue, and with that in mind I bought a new bottom board (which contains the charging port, mic, etc), but when I swapped it it the problem persisted. After that I assumed that the problem was in the rom itself, so I installed 3 other images with the same results... So i got on google and searched a bit, and it seems that i's a common condition on this phones.
I think the problem might be that the call manager mistakes the mic1(top) and mic2(bottom), because in the calculator tests the 1st passes but the 2nd fails.
Another option would be to try this, however I can't find this option in any of the images I've tested: https://www.youtube.com/watch?v=Ocm_WX-ilE8
Does anyone know how to solve this? Thx.
Click to expand...
Click to collapse
Hello, i can confirm it did my own too..
Go to Phone application > Setting > Accessibility > open TTY
Select one of the options and restart the phone,
Repeat the procedure for all options, repeat the last time with the option TTY complete and reboot tour Phone...