As the title says, I have two questions:
Can the mic gain be altered on stock v1.26? Almost everyone I call since getting the One X says they have trouble hearing me - switched to my old HD2 and everything is loud again, so not my connection at fault.
My One X always vibrates on incoming calls, despite that option being turned off in settings. Have I missed something? How do I stop this?
EDIT: actually there is a 3rd question - on the info screen that shows phone number, IMEI etc the phone number is "unknown". On my first One X that was a DOA for screen flicker, it was the correct number. Any ideas why this might be?
Related
I'm using a custom made homescreen. I'm using the missed calls plug in and I have it set up to be visible all the time to display:
"0 Missed Call(s)"
Yesterday I started experiencing some problems with it. But I don't think it has to do with the homescreen. Since I have tried others and I experience the same issue. Here is my problem:
Every time I turn off my phone and turned back on. The number that indicates how many missing calls I have, just goes away. Instead of reading: "0 Missed Call(s)" it reads " Missed Call(s)"
Now, when somebody calls me and I don't pick up the phone. That number comes back and my phone indicates how many missed calls I have, for example: "2 Missed Call(s)." Also, If I access the "Call History" the indicator comes back. At least I know when I get a missed call. It's just very annoying to be doing that all the time I turn on my phone.
I've tried to soft reset my phone a couple of times but that didn't help. I haven't made any changes to my phone recently. A while ago I was having this problem. But I ended up removing MyFavs from the startup folder and that fixed the problem. Now I don't now what the problem is.
I would like to know if any of you knows how to fix this problem without hard reseting my phone. And if there's no way. Would any body please tell me if there is a way to backup all the text-messages (without using dashwire.com).
Thank you!
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
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.
Just wondering this seems to be a huge bug in the software (HTC One M9) i'm not sure if anyone can help out here, When my phone rings i see the number come up as i have call display, i answer have a conversation, then we hangup, Call history shows unknown and no number in history, so i can not call that person back, i was running a custom rom when i noticed this, and tried a few things as in factory reset, clear cache????? i even flashed back to stock DEV ROM for the M9, can anyone let me know things to try or am i dupped???
A great thanks if anyone can help me here
Shane
Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls
*Copy/pasted from the Pixel 2 forum. Whoops!*
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
I have noticed a similar problem that has cropped up recently - I cant make consecutive calls. If I hang up from a call and then try to make another the phone sits there. The phone button animates but doesn't do anything. If I try 20 seconds later it will sit there for about 10 seconds and then make the call. If I wait about two or so minutes it will work. Incoming calls are different.. if I am in that "period" of time, the phone will ring and if I am not in the phone app - meaning the incoming call screen pops up - I can answer it. If its a heads up incoming call I cant answer it. I must turn the screen off and then back on to get to the full screen to answer it. I am on 17.0.186697879 which I believe is the latest.
I've had the delayed calling problem for almost 2 months. The problem also includes sometimes not being able to answer a call from the notification shade when the screen was already on. Toggling airplane mode alleviates the problem temporarily.
There's a lengthy thread in the OG pixel threads with the many users with the problem. Also a lengthy thread on one of the Google support threads. Someone there suggested it had something to do with the mlb at bat app. I think that has since been debunked. I haven't found a solution yet and Google hasn't made an official acknowledgement yet.
This issue suddenly appeared on my Pixel 2 couple of days ago. Tried all the hacks and solution, but even turning off all the knobs in the phone permissions screen didn't help.
I have android 8.1.0
Build OPM1.171019.021