Develop Bugs

Phone call abruptly disconnects and screen becomes unresponsive, help!

I've had this issue happen a few times, so I disregarded it, but just a few minutes ago it happened 3 times in a row. Here is what happens:
I'm in the middle of a phone call, and suddenly I hear a beep, and I look at the phone and the call was disconnected (I'm back on the 'Phone' screen). I then realize that the phone becomes unresponsive (the screen doesn't respond, same thing goes for the Home/Menu/Back/Search buttons).
The only thing I can do is press the top 'Off/Lock' button to shut off the screen, then press it again, and everything goes back to normal.
This happened 3 times within 5 minutes.
Is anyone else experiencing this problem? If so, any advice/solutions?
My 30-day purchase window is up in about a week, so I'd like to get this resolved before then to avoid any headaches.
Thanks in advance.

Have you loaded any apps? Modified the phone at all?
I've never seen this type of behaviour before.

Thanks for the reply. No, I haven't rooted it, or loaded custom time or anything. The only thing I've done is just download/install some Apps from the Android Market, that's it.
What do you all think I should do?

*bump*
I think I may have fixed the issue -- I had the Google Voice installed on my phone, and when I uninstalled it, I haven't had the problem since (it's been about 3 days).
Has anyone else experienced any stability issues or glitches using the Google Voice app?

My mom has been having this issue with her stock 2.1 Inc... She says the screen suddenly stops working and all that will work is the power button and volume rocker. Says it usually happens mid call.
PS. she doesn't have google voice. And google voice doesn't cause this issue on my Inc.

Yeah, it just happened to me again, and I don't have Google Voice installed, so that's not the culprit.
Is anyone else having this problem? Please let us know in this thread - I am going to swap the phone out tonight at my local Verizon store.

It happens to me frequently. Before and after I rooted. Let me know what Verizon does about it.
Sent from my Incredible.

I got the phone replaced at the Verizon store a couple of days ago, and I have yet to see the problem. However, ill keep a close eye out and will post another update in the next several days.
Sent from my ADR6300 using XDA App

[Q] Can't answer calls sometimes! Really annoying!

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

Smartwatch 2 gets stuck?

I bought my Smartwatch 2 from amazon and apart from being totally disapointed by the fact that Sony removed the shake2wake, music widget and auto brightness I have found an other problem: it gets stuck (happens like once a day) and it usually happens when I let it turn the screen off by its own, it will just dim the screen and get stuck in a dimmed screen state, showing my apps, but I can't interact with it, is anyone else experiencing this, and did anyone manage to fix this problem, or is my devices defective and I should send it back for repairing, and if that's the case can I send it to Sony Roumania instead, cause I don't like the idea of sending it to Amazon UK?

Ranomez said:
I bought my Smartwatch 2 from amazon and apart from being totally disapointed by the fact that Sony removed the shake2wake, music widget and auto brightness I have found an other problem: it gets stuck (happens like once a day) and it usually happens when I let it turn the screen off by its own, it will just dim the screen and get stuck in a dimmed screen state, showing my apps, but I can't interact with it, is anyone else experiencing this, and did anyone manage to fix this problem, or is my devices defective and I should send it back for repairing, and if that's the case can I send it to Sony Roumania instead, cause I don't like the idea of sending it to Amazon UK?
Click to expand...
Click to collapse
Do you think you might have downloaded an app that is causing this? I haven't had my watch for long but, I downloaded a calander app which would cause my watch to freeze whenever I'd open it.

MO3iusONE said:
Do you think you might have downloaded an app that is causing this? I haven't had my watch for long but, I downloaded a calander app which would cause my watch to freeze whenever I'd open it.
Click to expand...
Click to collapse
Downloaded only Sony's apps (most of them) and WatchIT and the xbmc and tasker extensions, don't think any of one can cause that...
EDIT: Forgot to say it also happened when my phone was dead, so the watch was not connected to anything.

Just if anyone is interested and has the same problem as I did, I managed to solve it by unpairing the watch from the phone, reseting the watch and doing the whole repairing process.

Ranomez said:
Just if anyone is interested and has the same problem as I did, I managed to solve it by unpairing the watch from the phone, reseting the watch and doing the whole repairing process.
Click to expand...
Click to collapse
Yep, I'm experiencing the same problem as I'm typing. I was just viewing an email and, exactly like you said, the backlight slowly turned off and it just stopped working. I'm going to soft-reset the smartwatch.

InjecTioN said:
Yep, I'm experiencing the same problem as I'm typing. I was just viewing an email and, exactly like you said, the backlight slowly turned off and it just stopped working. I'm going to soft-reset the smartwatch.
Click to expand...
Click to collapse
Hope you fix it man, the smartwatch 2 is a beautiful device, unfortunately mine is no more (screen got burnt so I sent it back to amazon and got my money back) so I really hope you fix it and keep enjoying it cause I really miss it but oh well, waiting for a g watch and hoping to be as satisfied of it as I was of the smartwatch 2.

[Q] Screen goes randomly off

Hello,
The screen of my moto 360 goes randomly off and vibrates at that moment, just like when you dim the screen with your hand., but now I'm using it. It's very frustrating because I can't even open an app normally or the screen goed of and I need to start over again. Does anyone know how to fix this?

Having same issues with mine.
Really strange and really annoying. Its like when u cover it with palm. It vibrates and screen goes off but ur in the middle of trying to do something. Anyone else having this problem?

Glad I'm not the only one having this issue, just got my Moto 360 today. I'll be in the Settings or other parts of the watch and it will just randomly turn off. It is really frustrating to deal with.

I have the same issue. I have pretty hairy arms so I wonder if the hairs are somehow triggering the capacitive touch screen.

you guys try to do a reset on the watch yet?? not just a reboot..

Any updates on this? I'm having the same issue

Any updates? I have the same issue I think it happend after udate to 5.0.2 but I'm not sure.

I'm also having the same problem. I picked up a new Moto 360 during the BBY sale rush of the last couple of days. At first it was buggy but the screen seemed to stay on while working with it. Then it had a system update, and since then most bug issues (like the faces not updating with the companion app changes) went away, however from that point the screen constantly shuts off, usually with a little buzz, while I'm interacting with the watch.
For instance, regarding the sensor used to turn off the watch if you palm it. I thought maybe that was it, so I was looking for a way to turn that off. I went into settings, and spend about 10 times of the screen shutting off before I could get to "accessibility settings" just to see if that might be there.
This problem occurs whether I'm wearing the watch or not (trying to eliminate arm hair or similar), and has occurred after a factory reset and re-pair with my phone (Note 4). Ambient sensor settings don't help, because all that does is make the screen go dark instead of off, but it still reverts back to the clock no matter what I was doing.
Any ideas? Any way to turn off a sensor perhaps, maybe in a custom ROM? Since this seems to be associated with an update near as I can tell, I wonder if a fix is coming from Moto or if it's too rare of an issue to be on their radar.

As an update, I replaced the watch with a new one, and this new watch is perfect. It started on outdated software which I left on for a bit to make sure it didn't show the problem, then I updated. Still no issues. I think there is a chance the problem is software regardless, but either way it must be a small portion of watches and isn't necessarily tied to any particular outside software influence (phone model or android version, or installed apps as NONE of those things changed). My advice to people reading this thread is to exchange the watch or get an RMA if possible.

Same Issue
Hi All,
I have the same issue. Sent it back for repair so let's see...

Same issue here as well

[Q] random calls...anyone else have this issue ?

I am not entirely sure if it is an android bug or specifically samsung. Anyway on my s5 and my N4 if I go to make a call occasionally it will say call not sent...when I go to redial the number the phone has already chosen a different contact at random to call...to make the issue worse the screen will then blink on and off in succession preventing me from stopping the random call...this seems to happen once or twice a week...I have already disabled the gesture option that calls people so I am at a loss here...anyone else experience this?

Not an Android bug. I've had it where the phone would try to connect and give up, but the second attempt would go through. That's a reception issue though.
It sounds like your software is glitch in for some reason. Usually a factory reset will fix this (unless you rooted and did something to alter the system, in which case, your alteration could be the cause). If not, then warranty time.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk

Yes, I have this too. Really annoying, happens every few weeks, and seems to go away after a restart.

Sorry to bring an old thread back to life but, has anyone figured out this problem? This happens on my Verizon Note 4 as well, so it is not carrier specific.
Everywhere else I have searched no one has an answer.
Just usually a call is placed. Then a quick message pops up with "Call not sent". Then another contact gets called instead. For me I don't see any pattern to how the wrong contact gets chosen.
This happened in KitKat and now is happening still in Lollipop.
Also I did a factory reset when I upgraded to Lollipop. Any ideas?
Edit: Just thought about this. Do any of you who have the problem use Google Voice?