Develop Bugs

Vibration...not so stable

I've seen a couple of people post on this issue but not many is facing it so i'm wondering if it's cause by a certain software? Or is this just another bug in the 2.1 and hopefully it gets fixed in 2.2
I've got the sound manager app installed to activate the vibration again once it stops. Usually it's for my SMS but over the last 2 days, even when i draw the unlock pattern, it does not vibrate anymore until i re-activate it using sound manager.
I've read that it could be the battery being weak but my batt was at some 65% so i'm guessing that is not the reason.
Anyone knows what maybe causing this vibration to stop issue? Maybe it's an application causing it....my only guess is "Handcent".

I've had this issue for the last month.
I've tried a few different things and usually it comes back, one way or another.
A few days ago I discovered something that leads me to start thinking I have a hardware fault. My vibration disappears almost daily now but the last 3/4 times it's gone I've done nothing except give the phone a light tap (light as in two fingers on the back of the unit) and the vibrate function has immediately returned.
I'm just guessing but it kinda looks to my untrained eye that it's a hardware issue on my handset - it may just be mine though.

Ha....if that is the case then you probably have a faulty hardware. No tapping is going to make mine vibrate until i launch Sound Manager to reset the vibration setting

I'm gonna contact HTC and get it sent back in the next few days for sure. I think I'd prefer it to be a hardware problem (fixable) than a non-descript software issue that may or may not be fixed at some point in the future.
Well I hope there's a permanent fix soon for you

mine always has some problem with the vibrate too...

Anyone any news? The vibration of my Desire is not stable, you clearly hear changes in the speed/power. I contacted HTC and wait for their answer.
For your information, it does always work and I am using Android 2.2.

My vibration works without sound manager on 2.2. I have even had the phone turn off due to low battery and the vibration works once the phone is back on charge
Sent from my HTC Desire using XDA App

HTC told me to hard reset the device. I can not believe that a hardware issue is solved by software reset ?

[email protected] said:
HTC told me to hard reset the device. I can not believe that a hardware issue is solved by software reset ?
Click to expand...
Click to collapse
Generally it's the first thing they think of to try, regardless of the fact it means you lose all your data.

Mine hasn't changed/failed since getting the phone in April (on its day of release)

teffers said:
Generally it's the first thing they think of to try, regardless of the fact it means you lose all your data.
Click to expand...
Click to collapse
That's what I think too. I will hard reset the device after my holiday and will take care of a backup myself. If this doesn't fix the issue I'll send it to HTC...

Bad Vibrations
I've noticed a problem recently, that I get vibration when the phone rings with an incoming call, or when I switch to vibration profile, and the handset also gives 'haptic feedback' when typing etc, but no longer vibrates when I receive text messages or emails, despite soft resetting, de- and re-selecting all the relevant options.
Running 2.1 on T-Mobile, can't tell you what software I've got on it as I stood on it and cracked/trashed the screen earlier today - phone still running, receives calls, seems to be receiving emails, but can't read anything at all on the screen.
On a side note, does anyone know how to get data off a running Desire with an unreadable screen?! I can't get it to sync with the PC Sync software because I can't get it into sync mode from the touchscreen menu
Phone is set up to backup to memory card, so I am now wondering if I can use that card in a replacement handset to restore my data to new phone?
Sorry for hijacking the thread a little! Ed

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.

Rhodium400 in-call problems with hearing either side (proximity sensor?)

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.

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.

Proximity sensor not working since june 2019 security patch

Hi
I'm searching for anyone else having the same problem as me and other people that i've seen in Lenovo Forums
I'm having different problems, but the most important for me is the proximity sensor, because once I answered a phone call, it makes impossible to hang up because the display turns black and it doesn´t "wakes" until the phone call has ended. The same problem with audios in whatsapp.
Another problem is that Moto Actions like turn on the flashlight with a shake, and open the camera with a twist doesn´t work anymore. Plus, the vibrator started to fail, having an unusual behavior until it just stopped.
And the device is not recognized correctly in any computer I've tried, it just appears as "unknown device", and the device doesn't show the options that use to appear when connected to a computer, it just says "charging".
I want to think that all of them are software problems, and not hardware problems, because they all started after the june 2019 update, and, as I said, there are other people having the same problems, and I think it would be a big coincidence if all of us have the same problems with our hardware.
If any of you have had the same problems, could you tell me if you could find a way to fix it? Or, anyone has any idea how could I solve, at least the proximity sensor problem, it would be better if the device don't turn off the screen anymore during phone calls.
I've tried reinstalling the drivers in 3 different pc's, and any of them worked, but when I tried with another device (Moto z2 force) they all worked. I've done factory reset three times, and one hard reset, with no changes. Could someone help me?
Thanks for reading.

Well, sound like... simply failing phone ? RMA ?

emcom said:
Well, sound like... simply failing phone ? RMA ?
Click to expand...
Click to collapse
Do you think that? I've had this phone for a year and a half, and I've never had any issue, until the last update on june 2019.
Maybe is a coincidence and my phone started to fail just after the update, but to be sure, I want to know if there's someone else having the same issue, and maybe someone could fix it.

I've had these problems a few months ago too, but back then I was thinking it was related to a hardware problem cause I had to send my phone to fix the screen (broken glass) and after that I noticed that the moto actions wasn't working properly, as the flash light from the frontal camera and the most annoying of the problems, the proximity sensor that would stop working when I got a call or audios in whatsapp. All of these was solved a couple weeks ago tho, after I had to fix my screen again (yes, 2 times in 3 months, congrats), just days before the android pie was released, so I can't say exactly what fixed it