Hi guys, hopefully someone can help me out, my TP2 calls my recent contact list by itself while it is sitting on my desk and not by me touching the phone by accident. This stops happening if I lock the screen before hand, but I shouldn't have to do that.
tp1
dudded101 said:
Hi guys, hopefully someone can help me out, my TP2 calls my recent contact list by itself while it is sitting on my desk and not by me touching the phone by accident. This stops happening if I lock the screen before hand, but I shouldn't have to do that.
Click to expand...
Click to collapse
The reason I upgraded to a tp2. My tp1 called people all the time. While I was even holding it away from my face. Nothing would stop it. Sometimes I was not even aware that I was calling people three way. It was a bad situation.
If your phone is doing that, see aboiut a warranty replacement.
I had a Wizard that did that after I upgraded to a cooked 6.1 ROM. I flashed a 6.5 ROM and it never happened again. It was'nt a regular thing but it always dialed the same number which was a work colleague but he wasn't on my speed dials. Of course he was on the the recent calls list as soon the phone called him.
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 was wondering if anyone else is experiencing this, if it's normal behavior and if there is a way to correct it.
When I get a phone call, I get the standard caller ID. When I take the call, it changes to the "add a note" card with the caller id image in the background. But when I hang up (from the phone) this card never goes away. If I'm in the office with the watch on the charger in my living room and take a call, I can go in there an hour or two later and that card is being displayed in full brightness in the charger. This is a bit fo a pain, especially if I'm sitting on the couch with the watch in the charger and take a call.
It seemed to me that when I first got the watch, this didn't happen; when I hung up the call, the display would go back to my watch face. I was hoping that once the Lollipop update came through (which seemed to take forever to come) it would go back to the original behavior but it hasn't.
Is anyone else experiencing this?
Is this by design? Is there anyway to either make it go away on call end or stop it from displaying at all?
Any insight would be greatly appreciated.
So nobody? I'm the only one in the world experiencing this?
Same here
I am also facing this issue and haven't found solution till date. At first I thought one if call recorder app is causing this , still no luck even after removing that app.
aXish said:
I am also facing this issue and haven't found solution till date. At first I thought one if call recorder app is causing this , still no luck even after removing that app.
Click to expand...
Click to collapse
My ultimate solution was to buy the Huawei watch. I never could determine the cause which survived every fw upgrade. Between that and the miserable battery life, it was the right decision. The Huawei is better in every way for me and two months into it, I still haven't run the battery out once.
Sent from my Lenovo TAB 2 A10-70F using Tapatalk
I am also experiencing this and wonder has anyone come up with a solution?
A few weeks ago I bought my wife an used Asus Zenfone 2 (ZE551ML - Z00A) and I installed LineageOs on it. Since then the bottom microphone stopped working.
I make a call to other phone and only the top mic picks up the conversation, meaning that the person on the other side barely hears me, and in fact hears me better if I speak with the phone flipped up side down.
Now, I know that you're thinking that most likely its a hardware issue, and with that in mind I bought a new bottom board (which contains the charging port, mic, etc), but when I swapped it it the problem persisted. After that I assumed that the problem was in the rom itself, so I installed 3 other images with the same results... So i got on google and searched a bit, and it seems that i's a common condition on this phones.
I think the problem might be that the call manager mistakes the mic1(top) and mic2(bottom), because in the calculator tests the 1st passes but the 2nd fails.
Another option would be to try this, however I can't find this option in any of the images I've tested: https://www.youtube.com/watch?v=Ocm_WX-ilE8
Does anyone know how to solve this? Thx.
Drydenmike said:
A few weeks ago I bought my wife an used Asus Zenfone 2 (ZE551ML - Z00A) and I installed LineageOs on it. Since then the bottom microphone stopped working.
I make a call to other phone and only the top mic picks up the conversation, meaning that the person on the other side barely hears me, and in fact hears me better if I speak with the phone flipped up side down.
Now, I know that you're thinking that most likely its a hardware issue, and with that in mind I bought a new bottom board (which contains the charging port, mic, etc), but when I swapped it it the problem persisted. After that I assumed that the problem was in the rom itself, so I installed 3 other images with the same results... So i got on google and searched a bit, and it seems that i's a common condition on this phones.
I think the problem might be that the call manager mistakes the mic1(top) and mic2(bottom), because in the calculator tests the 1st passes but the 2nd fails.
Another option would be to try this, however I can't find this option in any of the images I've tested: https://www.youtube.com/watch?v=Ocm_WX-ilE8
Does anyone know how to solve this? Thx.
Click to expand...
Click to collapse
Hello, i can confirm it did my own too..
Go to Phone application > Setting > Accessibility > open TTY
Select one of the options and restart the phone,
Repeat the procedure for all options, repeat the last time with the option TTY complete and reboot tour Phone...