Related
I know this topic has be address many many times and there are still no soluation to the problem.
So.. I want to make a poll to see how many user is experiencing this problem.
I hope to grather enough data to see if it is a hardware problem or Firmware problem so that i can address to O2 regarding this issue.
I love my PDA/phone.. but... this issuse really bugs me cos i used the phone for business and it always happens when a important call arrived... :evil:
Pls, Lets Vote with your honest answer...
Derek
No problems here....
What i've experienced is that sometimes the ringing sound is very quite even though the volume is at maximum. I make a soft reset and everything's back to normal.
NO SOUND
I have also experienced the same. I normally have to do a soft reset to fix the problem. Seems its a firmware issue to me.
One more issue is that we need to disable the power off system setting after 3minutes.
If not, a phone call will be automatically ended after 3 minutes talking.
i have also experienced this problem. i had a important caller call me twice and i didnt hear my phone ring. it was also next to me. luckily, i had my backup phone with me when he tried that line.
agreed that we shouldnt have to soft reset to get back the ring tone functionality. i personally think its a caller id version problem, but thats my opinion cause its easier to fix. i just hope it isnt a firmware problem since i wont hold my breathe on O2 releasing a rom upgrade in my phone version.
im going to try some reg tweaks to see if it will help, once my main pc is up and running (currently moving). i just dont want to go back to an older rom because of a ringing problem. but it IS a big problem for most of us.
ps. sorry about the spelling mistakes and punctuations. im on my pda at a coffee shop.
Yup I have see the no sould on outgoing, no sound on incoming, reset does the trick for me. Also feel that the sound is low in general (even if set to max)
Ha.. i call XDA today in their headoffice in Singapore. The CS guy told me.. they know this issue and say there will be a new (Rom) or patch release very soon.
After seeing the vote result. I believe that the issue is do to software, not hardware.
I have a firend that design such product. he told me that it could be that DSP script is not written well. He said, the Echo Cancelling must be overflow causing the unit to manufunction. and after reset, the overflow will be clear out, so the unit function again.
I hope O2 is really releasing a new patch to fix this issue. If not, i think i am force to go back to my Sony Ericsson P910i or one PDA and one phone option.
i'm glad that O2 recognises the problem and not passing it on to other people. thanks for the information rcbear. glad you took the extra steps get them looking this way.
i hope "soon" means in a waek or two.
same problem
My ringer always works but sometimes, at least every other day. When someone calls me i can not hear them, they can sort of hear me, but the earpiece is dead. A soft reset fix's this problem. Is my issue related to the current issue dicussed in this thread? Thanks
Jeff
I have the problem
But I get it seldom and sporadically.
pda2k (out of the box)
ROM: 1.22.00 WWE
Radio: 1.06.00
Protocol: 1337.38
ExtROM: 1.22.162 WWE
AT&T/Cingular
Re: same problem
jeffro01 said:
My ringer always works but sometimes, at least every other day. When someone calls me i can not hear them, they can sort of hear me, but the earpiece is dead. A soft reset fix's this problem. Is my issue related to the current issue dicussed in this thread? Thanks
Jeff
Click to expand...
Click to collapse
Hi Jeffro01..
Welcome to the club.. :lol:
Derek
I don't seem to have the ring volume problem, but my phone will get into a state where it rings, I answer the phone, but there is no audio. In the six or so times it's happened, I haven't really determined if the caller can hear me. A reboot fixes it.
I can't pin down any one thing I do to cause it to get into this state, but it seems like a software/firmware issue.
I have this problem too.
I had to send my BT headset for repair for two weeks and noticed it did not happen during that time while it started again since I got my BT back.
When it happens (once to twice a week) I soft reset my SPVM2000 and it then is ok.
Also the BT Orange Switzerland patch makes the problem appear less often.
Phone ring problem got me twice today...
Both times, never heard three calls, but the phone still reports them as being missed.
Gotta be a solution for this or I'll be soft resetting every time I finish a call/use.
I had to send my BT headset for repair for two weeks and noticed it did not happen during that time while it started again since I got my BT back.
Click to expand...
Click to collapse
If so I have 2 questions for everyone who has this issue:
1, Do you use a bluetooth headset or any other bluetooth device (gps...)?
2, What is your current bluetooth version and build?
I have Bluetooth build 3900, and I'm using 1.33.
No probleme here
not using BT or WiFi.
Where can I find my BT version?
I don't also have the 3 minutes switch off pb, the PDA function switch off after 3 minutes but the phone remains operational. I often switch the PDA off myself whilst on the phone to save on batteries.
...Hi everyone! (1st post!)...
I get the dead-speaker in calls too...
I took delivery of my first SPV M2000 a couple of weeks ago; it had a few problems, one of which was that the speaker would be dead occassionally when making or answering calls requiring a soft-reset to resolve. I initially thought this might be caused by the device not correctly recognising external hardware had become disconnected - handsfree/BT/car-cradle etc. - but it did seem to be at random.
Orange replaced the device last week; and by day 3 without using any handsfree/cradles etc. and BT and WiFi not even enabled (much less paired/connected); the dead-speaker problem reappeared.
I'm not going to bother chasing Orange about this issue on its own (this device doesn't exhibit any of the other problems I had with my first); as it seems to be a pretty common problem that's going to require a software update to fix. Needless to say when I read that HTC have written a fix I will be on Orange's back to make a fix for their ROMs public. (dreaming?).
Just FYI, both the initial device I was supplied and the replacement have the same software versions (in my sig).
Regards,
Rob.
I circumvented (temporally fixed) the ringtone problem by setting the default ringtone to "None", and also set the phone to vibrate. Then Re-enabled MS Voice Command to announce all incoming calls. The only problem is, the voice isn't loud enough in noisy places, but it does the job in the office or semi noisy environment. I guess this will have to do until a verified fix comes along our way.
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
As for #4: Not all programs have a landscape mode natively.
jlczl said:
As for #4: Not all programs have a landscape mode natively.
Click to expand...
Click to collapse
Thanks. I figured that she might be using an app that doesn't work in landscape since I haven't come across it yet.
Also, regarding #2, I should have mentioned that I have 4.48.25.20 as my current radio.
1) I use Jabra 2nd gen and mine is working great. A little crackling sound but nothing major.
2) Depend on the area you live and coverage, you might want to try different radio. I have stock radio and mine is working great. Better than my fuze was actually. I can get 1 or more bar than Fuze and call quality is super clear. No drop calls yet while I had like 2-3 drop calls with my fuze.
3) I am still running on stock rom and yes indeed it's slow and sluggish. I have to reset the phone physically sometimes. I am not too happy about moving the battery cover just to reset as well. With custom rom, the phone will be snappy since some people are running custom rom with their Tilt2 already. I am in the same boat as you. Waiting for the complete stock rom dump. Until then.
4) Not all the landscape work as you have already found out.
I use a BlueAnt and my BT reception is good.
I thought mine was slow at first but as I tweaked it a bit, turning off alerts and pop ups, it SEEMS to be more of what I expected.
Haven't had a dropped call issue.
But, I am thinking that I will flash the ROM when something comes along.
Thanks for the replies.
FWIW, my wife uses a Jawbone 2 and the crackling is noticable on both ends of the call. I use a first-gen Jawbone and have nocticed the crackling as well. It seems that it works better when the phone is on the same side of my body as the headset. I did not notice this crackling on my Dash and Blackjack 2 nor her Dash.
I think the dropped calls problem is definitely area related. My wife is currently out of town and it hasn't dropped her calls at all that I know of. And when I'm at home, it's no problem. It's just that on my regular commute, it drops 5-6 times where my previous Dash and Blackjack 2 only dropped once or twice occasionally. I've only made my commute once since I got the Tilt2, so maybe there were some coincidental network issues. That said, call quality has been very good.
I just turned off the new SMS notifications. I've also removed a couple of tabs that I know I'm never going to use (stocks, AT&T, and music) at that seems to have made things a little snappier too.
HAH! Not more than 1-2 minutes after I posted my last message (from my laptop), I went to use the internet connection on my Tilt2 and it locked up. A message appeared asking if I wanted to send error details to MS and then my phone turned off.
Another thing I've noticed is that Opera takes a *really* long time to switch from landscape to portrait. And it seems to be significantly slower than Opera Mini was on my Dash and Blackjack 2. Maybe because Opera Mini is Java-based on those platforms?
My wife is now reporting that her Tilt2 won't unlock unless she slides open the keyboard. Her Exchange connection requires the phone to automatically lock and require a PIN entry. I suggested tapping the power button but that doesn't wake it up, either.
Any suggestions? I'm thinking she might have a bum unit since mine isn't having nearly the trouble hers is.
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
SoapDoctor said:
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
e_dogg said:
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
Click to expand...
Click to collapse
Don't run to fast with my advice, I'm a complete noob but hard reset would be the first thing I would try. It is a microsoft product after all and I'm pretty dman lazy to run to the store first.
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
I can't really help you out too much, but I haven't been experiencing many of these problems at all, and I'm still on the stock rom, just cleaned it up a bit. Spend some time on the forums and you'll find some good quick hacks to try before you try a new rom.
superrrguy said:
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
Click to expand...
Click to collapse
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Linear2202 said:
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
Click to expand...
Click to collapse
Good info about your Jawbone issues. I have an old Plantronics headset that I'm not really using anymore. Maybe I'll give that one a try to see if it's just that Jawbones don't like these new versions of HTC phones (it worked great on her Dash).
As for the photos tab, it seems to work ok. Though the first "flip" through the pictures seems to be slower than subsequent flips.
I found that hiding tabs I won't be using like the "AT&T" tab seems to help speed things up. I think I have 3 or 4 hidden.
amurch said:
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
Click to expand...
Click to collapse
Thanks - good to hear of your sucess with the NRG ROM. That's the one I'm planning on trying since I really like the 6.5.1 changes.
redpoint73 said:
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Click to expand...
Click to collapse
Yeah, Touch FLO 3D sure is purty. And, now that I have the tabs sorted and hidden the way I like, it's very easy to use.
Just an update...the Energy ROM seems to have cured the dropped calls. With the stock AT&T ROM, calls dropped about 5-6 times on my regular commute. With the Energy ROM, not a single one!
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Linear2202 said:
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Click to expand...
Click to collapse
Yep - happened quite often with the stock AT&T ROM. I don't recall seeing it after switching to the Energy ROM.
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.
Have AT&T Note 4 since launch. Stock, not rooted or anything like that. Not sure when this problem started because I don't regularly make calls, but I think within the last week or two, possibly after I got the update to COC6 (the update seemed to complete normally, though).
Every time I place or receive a phone call and attempt to use the phone normally (hold it to your head), the person on the other end cannot hear me at all. If I switch to speakerphone, they can hear me and it behaves normally, and if I connect to a Bluetooth device like my car, it also works fine, but if I try to use the phone normally, they cannot hear me. I can always hear them perfectly.
For what it's worth, Google won't pick up my "Ok Google" from the home screen anymore either. Also, I had previously had the option to wake the phone with "Ok Google" disabled, but when I try to enable it now, it hangs on listening to me say "OK Google" 3 times... as if it never hears me say it.
The microphone appears to be working completely normal for everything else I've tried, it's just acting like it's on mute when I'm in a call and not on speakerphone or Bluetooth, and the OK Google stuff isn't working either.
Any ideas? I'm trying not to factory reset... I've searched a lot and not found anything where anyone has solved the issue.
FWIW I had the same issue randomly with my rooted Note 2, and I believe I either fixed permissions or reinstalled the ROM to get it working (can't remember). I wish I could just reinstall the ROM or latest update (COC6) again so I don't have to factory reset. Is this an option at all?
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
pj_rage said:
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
Click to expand...
Click to collapse
Not gonna lie, I checked my mic hole as soon as I read this. XD
I tend to always put my pinky finger over that mic subconsciously. I don't mean to, but it's just how my hands want to hold the phone during a call. I constantly get people saying that they can't hear me though. Then I always notice that my stupid pinky is on the darn mic. Grrrrrr.
Sent from my SAMSUNG-SM-N910A using Tapatalk