Develop Bugs

phone stops ringing after a split second

i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help

Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300

Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.

[Q] Clicking Droid Incredible

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.

Inconsistent Playing of Touch Sounds

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.

Does Oreo update fix all these issues ?

I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?

The screen dimming while gaming issue happened to me once, but I was just covering the light sensor with my finger, so I just fliped the phone and never happened again

Well, sincerely I have been with this device for 1 day, I will see if it brings problems, although for now I have not found an anomaly.

alexaraz14 said:
I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?
Click to expand...
Click to collapse
I haven't had those problems, but clicking the down arrow on the mobile data quick settings crashes, every so often my phone freezes and reboots (though less than Nougat), and there's the multitouch bug which gets fixed in the May security patch (which as far as i know is not out yet).

alexaraz14 said:
I got the phone on launch day from Three store. I've already had 3 replacements in store and got a 4th one RMA'd from Razer.
Dont know if its worth waiting for this update. Some people say its fixed most issues some say it hasn't.
Currently i get that auto screen dimming when gaming or on a app for like 5 minutes or so. Very frustrating since the screen is not so bright anyway and it goes down so much, I literally cannot see the screen content when I am outside.
On top of that I have this Bluetooth issue when I connect to a device, either car stereo or any device literally.. It connects and says its connected/paired successfully but when I play something, it plays from the phone speakers.
The only fix to this is I need to go back and delete the paired connection. go to app settings and delete Bluetooth share and Bluetooth midi service app data, restart phone, pair again.
If these two things are not fixed. I've got no more patience left, I'm just going to sell the phone.
Great idea of a phone it is with the loud speakers and 120Hz screen but software has been the worst I've used on a phone by far.
Any info from you guys regarding all this ?
Click to expand...
Click to collapse
The Bluetooth problem may be a problem with your cars radio and not the phone. I have a 2012 Scion TC and and tried connecting my Razer Phone, HTC 10 and an iPhone 8 and they all had similar connectivity issues where audio was just being routed through the phone.

waiflih said:
The screen dimming while gaming issue happened to me once, but I was just covering the light sensor with my finger, so I just fliped the phone and never happened again
Click to expand...
Click to collapse
The issue itself is nothing to do with covering the light sensor. I've read on here and on Razer Insider forum that it is heat/power related and that lowers the screen brightness because it consumes too much power. A lot of people get this problem and a lot dont know about it too.
ThatGuy94 said:
The Bluetooth problem may be a problem with your cars radio and not the phone. I have a 2012 Scion TC and and tried connecting my Razer Phone, HTC 10 and an iPhone 8 and they all had similar connectivity issues where audio was just being routed through the phone.
Click to expand...
Click to collapse
Its not my car radio. I've tried on 3 different car radio's and a Bluetooth portable speaker, I get this problem with literally every device i connect to. I still have not had a fix or a solution. Only thing Razer suggests every time is a factory reset which did not change anything.

This thing on max settings according to Ampere is pulling nearly 1.5amps from the battery with brightness at full and all settings maxed
Sent from my Phone using Tapatalk

Proximity sensor ignored partially?

I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?

I experience the same thing sometimes with stock rom

keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...