Related
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
gthing said:
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
Click to expand...
Click to collapse
That is the most intense thing I have ever heard ever.
I'd root that baby. Maybe an Android "virus"?
jigglywiggly said:
That is the most intense thing I have ever heard ever.
I'd root that baby. Maybe an Android "virus"?
Click to expand...
Click to collapse
i dont believe android phone has viruses....maybe just program errors.
Its a ghost.
campchi said:
i dont believe android phone has viruses....maybe just program errors.
Click to expand...
Click to collapse
no viruses, YET!
gthing said:
The other day I took my phone out of my pocket and set it down. I watched as it unlocked itself, opened a new text message, and began typing gibberish. I could see the letters on the keyboard popping up and then moving around before settling on a letter. It got through about three gibberish words before a phone call came through and the phone began ringing.
I have had this happen before (gibberish texts sent to people) but have never caught it in the act. It seems to happen when an event is happening on the phone - either an incoming call or an alarm going off. It's like some instructions are being sent in the phone internally but are being manifested through input on the touch screen or into the Google Voice SMS app.
Anyone else see anything similar or know what might be going on?
I'm running unrooted with the latest OTA updates.
Click to expand...
Click to collapse
ok, first off...
secondly, your thread title alone is tempting enough for me to post a reaction.
thirdly, maybe there's a delay in your screen touch input? or maybe someone has remote access into your evo? (this is going to make me sound dumb and ignorant, but please bear with me).. i know there are ways to get access into iphones to control them via commands through text messages. maybe that's happening with your evo?? again, i'm almost embarrassed to even be entertaining this idea since android is quite locked down in its nature, but it's the closest thing i could think of as a possible cause besides paranormal activity.
...which, in and of itself, sounds so awesome and creepy.
I had similiar things happen when using any custom rom based off the new ota..
Its something with the screen sensitivity they changed for the ppl who were having grounding issues..its the only thing I can think of..
I think I also have a paranormal situation of my own! Well maybe, but its very curious... A certain phone number/friend of mine has told me that my phone is calling him while my phone is completely idle. This has happened twice in the last 10 days or so. The first day he missed the call, the second time he was able to answer it and it was dead air. My phone was never touched; it was home alone the first time and it was streaming bluetooth music the second time. I know this sounds absurd, but unless it starts happening more frequently I guess I'll just deal with the mysteriousness of it all.
oOflyeyesOo said:
Its a ghost.
Click to expand...
Click to collapse
the ghost would have to use a hot dog for the screen to recognize him/her LOL..
i myself dont believe in ghost but thats trippy.
lol a floating hot dog typing things by its self. WTH I just laughed out loud and nearly woke my wife up. That was funny if you picture it in your head lol.
When i got my first Vogue, it would do that. Randomly resend text, send garbled text, and call people. Without any interaction whatsoever.
Sent from my Evo using XDA App
That is hilarious. I would have freaked out seriously. Is your phone rooted?
My phone is not rooted and was running stock with the latest OTA. I am leaning towards the theory that it is something to do with the latest OTA which addressed the grounding issue.
I enabled a password on my phone. Last night I kept hearing these little noises, like a bug beating its wings in really quick, short durations. I was looking all over before I realized it was coming from my phone. Face down, on my nightstand, it was randomly pressing buttons on the password screen and I was hearing the short vibrations of the tactile feedback. It had done it enough that I was locked out and had to wait 30 seconds.
Something's not right in Evo land.
You definitely need an exorcists.
Since you live in UT, I am sure there lots of Mormon High Priest that can help you out.
Good luck.
gthing said:
My phone is not rooted and was running stock with the latest OTA. I am leaning towards the theory that it is something to do with the latest OTA which addressed the grounding issue.
I enabled a password on my phone. Last night I kept hearing these little noises, like a bug beating its wings in really quick, short durations. I was looking all over before I realized it was coming from my phone. Face down, on my nightstand, it was randomly pressing buttons on the password screen and I was hearing the short vibrations of the tactile feedback. It had done it enough that I was locked out and had to wait 30 seconds.
Something's not right in Evo land.
Click to expand...
Click to collapse
Once in awhile the phone will stop vibrating and it won't ring if I get email, text message or IM. Changed My SIM Card, even factory restored the phone and it still does it from time to time. Do you guys have a similar issue? After rebooting the phone the problem is fixed-but it's only temporary. I have stock software-no rooting...
Please help!
Thank you.
same thing
same thing here buddy. no idea. but luckily it doesn't do it often. i tend to check my phone so often anyway that it doesn't get in the way though. definitely weird. it's like the opposite of a phantom vibrate haha.
I hope they come out with some kind of a fix for it-this is really annoying. Haven't seen a lot of people to complain though-strange!
i didn't complain because i thot it was normal.
I don't get vibrate nor ring for txt's.
btw, sms = normal txts?
Yeah, it isn't normal at all. I wonder if it is software problem, because if it was hardware I would thing the notifications wouldn't work at all.
Anyone has a solution please?
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 can't be the first one to need this but I can't seem to find it...
You know how the screen remains locked when you get an SMS (at least on my model of rhodium)? I want that to happen to all notifications. And if possible, to calls too.
It is so annoying when one of those happens and the screen remains unlocked, having my phone in my bag or whatever and things start to get "clicked", notifications get dismissed and so on. It happened a lot to me that I got some notification and by the time I got the phone out, it was dismissed and I was navigating the menus. Once I managed to call someone too.
Anyway, suggestions/pointers appreciated. Thanks.
Use Android, problem solved .
Honestly tho, I never figured out how to fix this in WinMo either. Drove me batty.
ciuly said:
I can't be the first one to need this but I can't seem to find it...
You know how the screen remains locked when you get an SMS (at least on my model of rhodium)? I want that to happen to all notifications. And if possible, to calls too.
It is so annoying when one of those happens and the screen remains unlocked, having my phone in my bag or whatever and things start to get "clicked", notifications get dismissed and so on. It happened a lot to me that I got some notification and by the time I got the phone out, it was dismissed and I was navigating the menus. Once I managed to call someone too.
Anyway, suggestions/pointers appreciated. Thanks.
Click to expand...
Click to collapse
My solution was to install and use s2u2. It has a setting that will keep the screen off if the proximity sensor is blocked. It will lock for all notifications and it will lock in call as well.
thanks
Took me some time until I got the configurations working to my liking but it finally does what I wanted and a bit more. Will need to see how the battery is affected but only time will tell.
Thanks again.
This is something that has been bothering since CM7, and I thought that Nikez Lente might have fixed it but apparently it does the same thing. Occasionally I try to call someone and the carrier drops the call for whatever reason, and if I have the phone to my ear when this happens, the screen locks, so I have to unlock my phone in order to redial. When I don't have the phone to my ear and the call drops, my screen doesn't lock, so I have to either wear a headset or put it on speaker so I know if the call is connecting. It's a minor annoyance, but it seems kind of stupid, especially since if the call connects I can take the phone away from my ear to press the hang up button and my screen isn't locked. I sometimes find myself in places where my mobile carrier's reception is not the best, so I have to put up with this nonsense from time to time. Is there some setting to disable this annoying lock behaviour short of disabling lock screen entirely, or an app that fixes it?
I remember somewhere _thalamus has mentioned about this behavior and said this is how it supposed to be.
So I don't think there's fix for it.
BTW, Sense ROMs seems not to have such problems.
Or you can try some lockscreen replacements and disable the stock lockscreen.
h3110 said:
I remember somewhere _thalamus has mentioned about this behavior and said this is how it supposed to be.
So I don't think there's fix for it.
BTW, Sense ROMs seems not to have such problems.
Or you can try some lockscreen replacements and disable the stock lockscreen.
Click to expand...
Click to collapse
How it's supposed to be?! In my not so humble opinion, I think that's completely idiotic. What is the rationale behind it, because I cannot for the life of me think of how locking the screen when the call drops is useful, especially since it isn't done when the call drops when you don't have the phone to your ear. If you're in a low-signal area it adds to the frustration, to have to enter unlock codes every time the carrier drops your call.
I don't feel like changing ROMs again for the time being, as it seems there is no ICS Sense ROM available that is at least as stable as Nikez Lente and doesn't require my phone to be S-OFF (none of the techniques I've tried to get S-OFF have ever worked), and well, I don't think I really like Sense all that much. So any suggestions on what lockscreen replacements are out there which don't have this idiotic behaviour? I don't mind paying a nominal fee for something that will work and not spam my phone with garbage first opportunity it gets.