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.
Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
All I can do is slide to unlock the screen and then I'm looking at my home screen with the phone still ringing but no chance to get the call. There is nothing in the notification area or anywhere else where I could answer the call. All I can do is to wait until the ringing stops!! Really really bad behavior.
Furthermore, once the ringing has stopped, there is no information about the missed call in the call log. So I can't even call back the person who called me!
First time this happened I had "Plants vs Zombies" running so I figured the phone wasn't fast enough to switch to the incoming call. But it also happens when the phone is idling.
There seems to be no scheme behind all of this. Sometimes it happens twice in a row, sometimes only once a week.
I got my unbranded simlock free Arc in mid April with 2.3.2 and .181 firmware and applied Gingerbreak for root access. Later I upgraded via PC Companion to 2.3.3. and .145 firmware. But I lost root which I didn't like. So I downloaded the Generic World Firmware .181 and flashed it on the phone. Then used Gingerbreak again and made an OTA update to 2.3.3. and .145 firmware. Now I have root and the latest firmware.
All the while I used Titanium Backup to restore all my data, settings and apps as I don't want to reinstall all from scratch because it would take forever.
With this latest firmware, everything is fine, except for the call problem!
Please help me, what can I do?? I don't want to reflash and upgrade or whatever or lose all my data. I just want my phone to be able to handle calls as it should be!!
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup which speed up my startup time and free ram quite a bit. But I didn't frooze any crucial apps, at least I hope. Only stuff like Chinese keyboard and Let's Golf etc.
Also, if I would have frozen the call handling app or something, I wouldn't be able to accept calls in most cases, wouldn't I?
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup
Click to expand...
Click to collapse
Think you may have answered your own question here...
could be, but on the other hand I only frooze really stupid apps which should not affect any important functions of the phone. Also, if I frooze something important related to calls, why is it working most of the time? This is what I don't get.
Here is what I frooze (most of them just took up space in the app drawer and I don't use them), maybe it helps:
- stock browser (I use Opera)
- chinese keyboard (I'm german and don't need it)
- "Downloads"
- retaildemo
- live ware manager
- fb mediadiscovery
- dlna server
- news and weather
- postcard
- SE setup wizard
- sim toolkit
- sony ericsson sync service
- playnow
- sony ericsson support
- track id
- twitter
- let's golf
- google talk
- sony ericsson sync client wizard
so is your problem solved?
Anything related to google should be left alone news and weather should be fine to freeze or delete but would leave Talk alone, and depending what data from which FW was backed up, might also be an issue.
so I defrosted Google Talk. Anything else I should defrost?
Under "Settings" and then "Running services" I sometimes stop "Timescape Legacy Plugin" or whatever it's called because it takes up RAM. Could this also be a cause but I believe it's only for the Timescape app which I seldom use.
drsoran2 said:
Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
Click to expand...
Click to collapse
I have the exact same problem.
It doesn't happen often but it's really annoying either way.
I barely installed anything off the market and I don't use any sort of app killers/managers.
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Today, I re-enabled all the froozen apps and then frooze some of them again, according to the thread here on xda. But only apps about which I was really sure.
Don't know how I could test if the error is gone. I mean, have people calling me 100 times and hope it occurs or not doesn't really sound great.
may be there is some problem in your firmware,try some other firmware of other region.................
drsoran2 said:
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Click to expand...
Click to collapse
That's the weirdest part, the only thing I used that day was Whatsapp.
The incident happened about 5 hours later, I was in a car when my phone started ringing.
I tried picking it up but.. I guess you know the rest..
I was about to buy this phone but now I'm having second thoughts.
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
briggs007 said:
I was about to buy this phone but now I'm having second thoughts.
Click to expand...
Click to collapse
Well, I can tell you that this a great phone and it seems me and drsoran2 are the only ones with this problem..
Guess we just had some bad luck..
drsoran2 said:
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
Click to expand...
Click to collapse
No, I don't think that's it..
It's happened only twice to me over a 2-3 month period and my friends have always called me back asking why I never pick up the phone.
It really just happens about once a month to me, and I can answer the second time they call me right away without any problem.
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
im_iceman said:
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
Click to expand...
Click to collapse
No, as I said before, I'm not using any sort of task killers/app managers.
Today first time i encountered same problem. I have WhatsApp running in background. No task killer, nothing else.
Though i donno how to solve this problem. But i can surely tell how to pick up call in this case.
Just press the power key, this will take phone in locked state, but the call wont be rejected.
now click the home key and you will see the answer key, now slide it, it will slide without problem
it's good news that you found a workaround! I'll try to remember it the next time it happens.
Today, I had the problem again but this time it was different. The slider or the contact picture of the person calling didn't appear, but I could see the number of the person who is calling in the notification bar (not the name, just the number although this number and contact is stored in my contacts).
This happened the first time, all the other times the phone just rang without any hint of who is calling.
It would be nice if we were able to pinpoint a certain event which causes this odd behavior but so far I had no luck. What I'm doing differently since the last time it happened is, that I don't use task killers anymore. But still, it happened again today.
It's difficult to find out what it is when you don't know what causes it and when it will happen. For example, it happened to me today once for the first time in about a week.
in recent days, "it" happened very often to me!
Sometimes, the phone manages to at least show the number of the person calling so that I can call back. But usually it doesn't! The call just disappears into nirvana.
Do you guys remember if the error is associated with a certain amount of RAM left available? In other words, if the available RAM at the time of the incoming call is below a certain limit (which I don't know) the phone can't display the call. When it happened to me today, I had only 90MB RAM left. Maybe the phone can't free up enough RAM fast enough?!
Also the trick, which somebody mentioned a few posts above me, that when it happens you press the power button and then home and then you can slide and accept the call very rarely works!
I'm desperate and don't know what to do about it. I have just finished adjusting my phone to my needs. I linked apps with Link2SD and now have over 100 apps installed and still 215MB left on the internal memory, I have root and the .145 firmware. Everything is fine, except for this error!! It would take ages to restore it to the point where it is now, if it is complety possible at all.
I mean, if a phone can't handle calls, what good is it for?
I had a NEC e616 years ago which frooze while sending SMS or crashed after connecting a call or during a call and other "funny" things, but this was well known for this model.
But we don't have 2004 anymore and I except the Arc to work.
I could send it in on warranty, possibly. But then everything would be erased and it would take forever to get it repaired.
And I'm afraid they are going to tell me that they couldn't reproduce the error (because it happens so randomly)!
Such a nice and beautiful phone if not for this stupid error!
I'm already tempted to get rid of the phone and look for something else. But who's going to buy a phone with a bug which can't display phone calls?!!
I mean, I could reset it and flash the fimware and stuff and then hope. Maybe the error is gone. Maybe it persists and then all my data is gone and I have to start from scratch.
Or it is gone and then I have to start from scratch also!
If I should be forced to do it all over again and have all the work, then I could do it on another phone as well.
The Samsung Galaxy SII is quite ugly, to wide and big but I hope it can at least handle a call?!
Thank you for any help!!
Hmm..
If it happens rarely.. Why don't you sell it off on ebay
If asked about other mobile. I prefer sensation to sgs2. Much better phone function. In fact IMO htc is better than all other androids when it comes to phone functions.
Sent from my LT15i using XDA Premium App
I've tried my best with the search tool and google. But I cant find anything regarding my problem, thus I'm asking here (I keep finding questions from people who want random ringtone apps etc)
My phone has begun to randomly change my sounds for incoming calls, notifications etc. I usually note that it happen when someone calls and all of a sudden a random sound is played instead of the one I selected.
I've investigated a bit and found out that if I change the incoming call sound then just wait a hour or so. Then when I go back into settings again another sound is shown. And no, I haven't had the phone connected to my PC or anything like that (which I understand blocks the SD card and prevent sounds from the SD to play while connected). The sound change happens no matter how I set the sounds (via settings or via Sense/Personalize).
This just started to happen out of the blue. I've tried a full wipe of the phone while on ARHD 6.1.2. The problem was still there, did another full wipe and upgraded to ARHD 6.3.1, and its still there.
Did you try another ROM then ARHD (Such as MIUI for example) to see if it's still happening?
I havent had the time yet. But I will try. Though the problem began after a few month on ARHD 6.1.2, so my first thought was that it might not be the ROMs fault. But then again I could be wrong, will try another ROM and come back with my findings.
And I just found someone else with a similar problem; http://forum.xda-developers.com/showpost.php?p=21541054&postcount=62550
I've started getting this problem on a stock ROM after the latest OTA. Very annoying...
When I turn my desire on everything is fine however if I leave it a few hours and come back it will simply not wake up I can do what I like but I can not wake the phone up unless I take the battery out and turn it on again and the weird thing is that in that time where it is "sleeping" I can call it and it rings or send texts to it however when I turn it back on I have no missed calls and do not receive any of the texts I sent. At first I simply thought it must just be the sense 3.5 roms I was using which did often freeze when loading an app however I ten reverted back to a sense 3.0 rom which never froze and was extremely stable apart from the black screen freezes. Its very frustrating has anyone got any ideas ?
Also Iam currently using the AceSMod007-3D rom.
It looks that it is a problem with the ROM.
It think you have a better possibility for a solution, if you post the bug to the (thread) developer of the ROM.
maxmw said:
When I turn my desire on everything is fine however if I leave it a few hours and come back it will simply not wake up I can do what I like but I can not wake the phone up unless I take the battery out and turn it on again and the weird thing is that in that time where it is "sleeping" I can call it and it rings or send texts to it however when I turn it back on I have no missed calls and do not receive any of the texts I sent. At first I simply thought it must just be the sense 3.5 roms I was using which did often freeze when loading an app however I ten reverted back to a sense 3.0 rom which never froze and was extremely stable apart from the black screen freezes. Its very frustrating has anyone got any ideas ?
Also Iam currently using the AceSMod007-3D rom.
Click to expand...
Click to collapse
before reverting back, did you wipe everything, incl. dalvik cache? and have you tried a different sd?
May I suggest to use the search function ?
It could bring you there
http://forum.xda-developers.com/showthread.php?t=1327242&highlight=freeze
After month of freeze, wipe, many rom and new sd I tried to bend the slot card as mentionned at the end of this post.
One week without freeze...
I think it has nothing to do with Rom or SD...
Another vote for the SD card causing it. I had a blank screen a few times when testing out custom ROMs with a new SD card... Aftermarket cards do seem a bit loose in the slot compared to the stock card.
It seems like most custom ROMs can't really function without the SD card being mounted
I am starting to think that I probably also having this because of some problem with the sdcard.
As for taking out the battery, you can do instead the three-finger thing: press Power+VolDown+Joystick - this works in most cases as a warm reboot.
maxmw said:
When I turn my desire on everything is fine however if I leave it a few hours and come back it will simply not wake up I can do what I like but I can not wake the phone up unless I take the battery out and turn it on again and the weird thing is that in that time where it is "sleeping" I can call it and it rings or send texts to it however when I turn it back on I have no missed calls and do not receive any of the texts I sent. At first I simply thought it must just be the sense 3.5 roms I was using which did often freeze when loading an app however I ten reverted back to a sense 3.0 rom which never froze and was extremely stable apart from the black screen freezes. Its very frustrating has anyone got any ideas ?
Also Iam currently using the AceSMod007-3D rom.
Click to expand...
Click to collapse
maxmw said:
When I turn my desire on everything is fine however if I leave it a few hours and come back it will simply not wake up I can do what I like but I can not wake the phone up unless I take the battery out and turn it on again and the weird thing is that in that time where it is "sleeping" I can call it and it rings or send texts to it however when I turn it back on I have no missed calls and do not receive any of the texts I sent. At first I simply thought it must just be the sense 3.5 roms I was using which did often freeze when loading an app however I ten reverted back to a sense 3.0 rom which never froze and was extremely stable apart from the black screen freezes. Its very frustrating has anyone got any ideas ?
Also Iam currently using the AceSMod007-3D rom.
Click to expand...
Click to collapse
Take a look at your OC frequences controller, when you have low min values for sleep it sometimes doesn't want to wake up.
Sent from my HTC Desire using flashes and thunders
Hello,
First I apologize for opening a new thread instead of posting in the CM11 thread, but till now I don't have write privileges there.
I recently unlocked and permrooted my Desire HD then installed Mustaavalkosta's CM11, but as a newbie, I have some issues I require assistance with. To note that I did an extensive reading before I did any rooting and installing a new rom.
1- I find myself not hearing anything during calls. It's sort of like my internal speaker got muted somehow after installing CM11. I tried multiple apps to no avail. I read somewhere that if u fail to flash the boot.img in the rom u might get this issue, but thing is I did flash the boot.img after I installed the rom and the recovery and wiped the cache. I can hear the calls with the external speaker turned on and with the headphone, so I think it's not a hardware issue but a software one. Any fix to this?
2- After each restart, the UI somehow resets itself. I mean many of the settings and widgets I use either get reset or vanish like the sleep option in seetings for example (I put the screen to turn off after a 1 min and it resets to 15 sec after each reboot which is annoying as hell). Also, many apps like Dolphin and GoSMSPro shortcuts vanish from the home screen after each reboot, while whatsapp for example doesn't. I'm not able to figure why some app shortcuts vanish while others don't.
3- I tried to use ART instead of dalvik, but yet again after each reboot, dalvik is back. So effectively, I can't benefit from ART.
4- other minor bugs which I will not mention for now till I solve the 3 main ones.
If someone can provide some assistance (mainly for the first issue which is the major one), I will be very grateful. It's becoming increasingly annoying and embarrassing to turn the speaker on every time I receive a call, bc most of the times I am in a room with other individuals or in a meeting, and I am forced to have them hear the conversations bc not always I can excuse myself.
No one has any input on this?
After wiping data, dalvik cache, android secure, etc... and reinstalling the stock rooted 2.3.5 Rom, I still had the same internal speaker issue on calls. The heaphone icon was on even though there were no headphones plugged. I installed 2 widgets (togggleheadset 2 and headphone fix) and the issue was fixed. To note I had this problem back on my unrooted stock Desire HD before I rooted it and upgraded to CM11 BR3 thinking the new rom will fix this problem.
So after I made the calls work on Gingerbread stock rooted rom, I did a clean wipe once more and installed CM11 BR4. The problem reemerged. And the 2 widgets couldn't be redownloaded bc they are not compatible with kitkat. The other issues mentioned in the OP disappeared, only the incall volume issue remained.
I need to mention that many Desire HD owners have had this problem on their Froyo and Gingerbread stock builds, and usually the 2 widgets I mentioned above helped fix the issue. On 4.4.2, it seems some android users have complained of in-speaker audio volume being very low, so maybe this worsens the issue I had instead of fixing it.
I'm leaning to think that it's mostly a software/code issue, otherwise why would the widgets fix the problem on an earlier version if it's hardware related? hence, there could be a workaround for it on Kitkat if someone knowledgeable cares to look at it. Maybe the code turns off the internal speaker or lowers the volume so much it becomes unhearable. The headphone and external speaker are just fine, I can hear the other person in the call without any problem. It's when I rely on the internal speaker that I hear nothing.
Hope someone can offer some assistance here.