hey guys,
My friend has an annoying problem. when she gets a call a blue android pops up in the black with a speech bubble and three dots in it. She is on stock 2.1
She never noticed this before..
Is this normal? i rooted and flashed mine as soon as i got it so i have never seen this before.
Just curious as to what it is and what it means...
Anyone? anyone? bueller?
Any chance you could put up a screenshot (or picture) of the error screen? It's not one I've seen before, so seeing what you're seeing might help in the solution.
A few questions: Could it be a contact that is missing a picture? You said its stock, have they applied any themes, or apps that may change contact data? Is it an "error" message? Does it happen with every inbound call, regardless of who?
Sent from my Captivate running Continuum 5.5
I saw this on my phone before flashing a custom ROM. I don't think it was an error, but I always wondered what the heck it was. Never had a chance to get a screen shot of it...
Haven't seen it since moving away from stock!!
Sent from my GT-I9000 using XDA App
quarlow said:
A few questions: Could it be a contact that is missing a picture? You said its stock, have they applied any themes, or apps that may change contact data? Is it an "error" message? Does it happen with every inbound call, regardless of who?
Sent from my Captivate running Continuum 5.5
Click to expand...
Click to collapse
w
As far as I know, yes it happens with every incoming and outgoing call...I personally have not seen it. I do know all about her phone tho. It is non rooted, so a SS will not happen. she also has not applied any themes at all or installed anything that affects contact data. I do not believe it is an error message. I will be seeing her tomorrow and ill let you know then.
The reason why I am curious is because it is something i have not seen before or heard of before either...
Ive got that little guy on my phone as well. Im on stock 2.3.3 KF1 released last week. Called my self at work today to play around...
I think the icon is to show that you are connected and talking through the handset. Its not a button and it does not appear until the call is connected. Also if you press speaker it goes away. I dont think it does anything, its just a square head guy with two eyes and a speech bubble with three dots in it.
LOL....its the noise cancellation feature. click it
Related
Hi all.
I have discovered a problem with an X1.
When recieving a SMS, It will not display I have a new text message...or sms icon on the top title bar.
However, If I go into the messaging.. I will find.. that i have indeed had a new text.
sometimes.. i can check my phone front screen many times..and then only if i go into messaging, will i see the text has actually come ages ago..but no notifications on homescreen or titlebar...but once into messaging... it will show...in blue.. one new sms.
It the stock r3a rom..and no hardspl/anything else installed or on.
I have hard reset, and tried it with zero apps installed...however, it still does it.
Anyone else come across this issue? or more so.. a fix?
Same thing here
I also experienced the same problem. So, if i received a message, but i don't wake my phone, it wont give any sound or any notification. But if i wake it up, there will be a notification about it, although it was sent an hour ago.
Has anyone find the solution for this?
THx
I had a problem a while ago in which the the notifier in Xperia panel would say I have new messages but when I open the message-inbox there's nothing there. So I only recieved texts 10% of the time, very very annoying and I had T-Mobile send it back because it wouldn't work properly even after using SE update service.
Seems like nobody reading this post. LOL
Or nobody has the same problem...
Is everyone experiencing this problem using T-Mobile?
Maybe this is the issue?
Maybe some app you installed is causing the problem. My notifications are working fine and Voice Command even reads them. I have the new Christian WM6.5.
WhyBe said:
Maybe some app you installed is causing the problem. My notifications are working fine and Voice Command even reads them. I have the new Christian WM6.5.
Click to expand...
Click to collapse
Stock Rom
nothing installed at all. It has just been to SE for repair on Keyboard sticking issue... keys would re-repeat..and have to really depress the space bar.
This is now resolved...but the SMS notification issue still exists.
I wondered if those others suffering also... had A T-Mobile sim.?
Mine is a Generic_UK device and was purchased outright for £500 from expansys...and has not been flashed in anyway except official upgrades. (work device... my personal device is flashed more times than i would care to admit.)
For what it's worth, my boyfriend has the same problem, and he's on AT&T.
radi0chik said:
For what it's worth, my boyfriend has the same problem, and he's on AT&T.
Click to expand...
Click to collapse
Why is it we are having multiple problems with this issue... and no one really has ever addressed it?
Seems to be an issue that is fundamental to a phone nowadays..
I once had the problem that indeed the notification popped up but the message was not stored in the sms directory. Anyway, installing a new rilphone and radio solved that problem for me. Why don't you try different rilphones or radio if you did not already?
Sorry that I can't really help here...
Hello,
I've been having a problem with a few of the custom builds (Timor, AthineOS, CellPro Evo), and one problem I've noticed with each of the ones I've used is that when I get a text it doesn't notify until I wake the screen back up. Once I do that it vibrates and rings, but its up 30min after I got the text. Is this a known problem with a fix or am I better off sticking with a stock ROM?
Thank You
Funny you mention this, because I'm having the same problem. I thought it may have been a tweak I'd done and was going to do a hard reset today.
The only cab I've installed is Microsoft MyPhone. And had to edit the reg to allow the changing of the notification light timing in the Sounds & Notifications settings.
Do you know if this happens before you've made any changes to settings or installed any software on the phone? I don't recall having any problems like that myself with Timor installed, but I'm also not sure I received a text in that time. I haven't tried the other ROMs you listed.
It seemed to happen after I edited the reg settings.
Doesn't seem to be a constant occurance though. I happened to me 12 hours ago, even after a soft reset. But now I just sent a test message to myself, and all is ok... weird
Well I've regularly installed My Phone, Marketplace, Bing, Groovefish, and MP3 Trimmer, but I'd rather not delete and hard reset everything to do a test if someone knows a fix
I haven't had this issue...I am using the Valkrie Firestorm 5 and even when my phone is sleeping my phone vibrates as I get SMS messages and emails...
Well I have hard reset and held off installing using the My Phone. Everything seems well with recieving on time...but now the screen turns on everytime i get a message. It didn't used to do that and I find it quite annoying..I looked around my settings and Advanced Config and couldn't find anything.
It happens in the stock HTC rom too.
It normally doesn't happen if you come out of the text messages and go back to the home screen after you reply to someone. It's a really annoying bug
Me too...
I thought it was the result of all the hacking, tweaking and breaking I've been doing on this flash since I've been using it as a "scratch pad" but the problem you are all describing sounds identical.
I will also second the Home screen suggestion. Hit 'End' after you are done messing with the phone to go back to the Home screen. There is definitely a notification bug related to not alarming/vibrating when not on Home screen.
Though I have observed this issue, this does not completely explain my problems. Sometimes I don't actually even receive the SMS or MMS until the next day or after rebooting my phone! Most of the time it's fine though. I'm going to do a clean flash and see if that gets rid of that issue.
Same Here
I have run across the same problem with a number of the cooked ROMs. I never really noticed the problem with the stock ROM though. In my experience some of the cooked ROMs are having a problem handling the text messaging. I have over 3000 text msgs in my backup and as soon as I try to view an older text, the systems tend to lag and freeze up to the point that I need to soft-reset. Im using Athine right now and so far it has handled the text msging just fine without freeze or lag, but it also seems to have the same notification delay bug that the other ROMs have.
dwarf said:
It happens in the stock HTC rom too.
It normally doesn't happen if you come out of the text messages and go back to the home screen after you reply to someone. It's a really annoying bug
Click to expand...
Click to collapse
Yeah I'm familiar with that bug. But I go back to the home screen 99% of the time then shut the screen. I'll get a message and the LED will start blinking, but only when I turn the screen back on will it ring and vibrate.
Same problem here with the cell pro rom
ftmoe said:
Hello,
I've been having a problem with a few of the custom builds (Timor, AthineOS, CellPro Evo), and one problem I've noticed with each of the ones I've used is that when I get a text it doesn't notify until I wake the screen back up. Once I do that it vibrates and rings, but its up 30min after I got the text. Is this a known problem with a fix or am I better off sticking with a stock ROM?
Thank You
Click to expand...
Click to collapse
I have the problem with almost all of the ROM. Does anyone know if it could be a result of not using the right radio?
I could be wrong.. but I don't think it has anything to do with the radio. There doesn't seem to be any problem is receiving the message from the carrier, it's more-so the OS not notifying. This has only happened to me since trying the new WM 6.5.5 builds with Sense 2.5. Previous to these builds I have never had any issues, and only used EnergyROM with a COM2 build, and Sense 2.1
nackas said:
I could be wrong.. but I don't think it has anything to do with the radio. There doesn't seem to be any problem is receiving the message from the carrier, it's more-so the OS not notifying. This has only happened to me since trying the new WM 6.5.5 builds with Sense 2.5. Previous to these builds I have never had any issues, and only used EnergyROM with a COM2 build, and Sense 2.1
Click to expand...
Click to collapse
Im not sure about all the technical stuff your talking about...I just know that on almost every ROM I flash, when the phone goes to sleep, they seem to not do anything. Its only when I wake it up do I receive text messages, notifications and the weather doesnt update on its own in the prescribed time its supposed to according to the settings I have selected.
The radio version may affect the quality of your reception. So if you have no reception then that will obviously delay texts getting through, and stop you being able to get to the weather servers. But I can't see why it should have anything to do with delayed notification of texts that are already on your phone.
I realise this might not help you much, but on my EnergyROM (see my signature for full details), my phone gets texts fine when it's asleep.
The weather isn't designed to get automatically updated when your phone is asleep though. There was a recent thread on how to change the registry to make it do so, if you haven't done that then your weather stuff may well be acting correctly.
steviewevie said:
The radio version may affect the quality of your reception. So if you have no reception then that will obviously delay texts getting through, and stop you being able to get to the weather servers. But I can't see why it should have anything to do with delayed notification of texts that are already on your phone.
I realise this might not help you much, but on my EnergyROM (see my signature for full details), my phone gets texts fine when it's asleep.
The weather isn't designed to get automatically updated when your phone is asleep though. There was a recent thread on how to change the registry to make it do so, if you haven't done that then your weather stuff may well be acting correctly.
Click to expand...
Click to collapse
Awesome...thank you so much for the information and help
This is the thread about getting weather to update automatically - http://forum.xda-developers.com/showthread.php?t=585373
WHY DONT YOU JUST USE A ENERGYROM????? I dont have any issues with those roms and i just updated to the .88 radio. no issues as of yet.
Hello,
Ever since I have gotten this phone, I have run into problems occasionally with messages failing to send out. They simply get stuck at "sending".
Mtmichaelson informed me that on the VZW community forums this is a main complaint of the phone. I spoke with tech support and of course they said they have never heard of this before and simply wanted me to perform a factory reset (Which I had already done previously, even before I was rooted) . I even went out to get a new sim card.
Today though, I think I may have found out what causes it. It appears it's happening from sending messages consecutively too fast.
For example, say I sent you a message at 11:00:01 AM saying "SCREW", followed by "YOU" at 11:00:04 while the first message is still attempting to send. (It doesn't always happen, but when it does its usually from sending messages consecutively too fast. At least with my own testing)
The first one will send and the second one will fail to send, along with any other messages you attempt to send, until you either put your phone in airplane mode or reboot.
I have corrected the situation by using Handcent and applying a 1.5 second delay of when I press send. Now, my texting problems have been solved. (Hopefully)
I live in Houston and there have been no reports of VZW network issues here, and I've had a Tbolt and a Charge and never had this issue.
Thanks,
Samsuck
I've run into the same thing numerous times. Always seem to happen when im in a low signal area.
Do you ever have the issue where only half of 2 part messages comes through?
yup.. i have problems with low signal texts, and im not a big handcent fan... can never get the stock notifications to stop so i always get two notifications per sms/mms... oh well.
xjli said:
yup.. i have problems with low signal texts, and im not a big handcent fan... can never get the stock notifications to stop so i always get two notifications per sms/mms... oh well.
Click to expand...
Click to collapse
I actually prefer GO SMS but the lack of nice free themes suck.
All you have to do is go to your stock messaging app, hit menu, settings, and scroll down to notifications, and turn it off
Sigh..
Nevermind.
Sent from my VS910 4G using XDA App
This is the biggest, most frustrating thing I've ever experienced. I'm glad I'm not the only person, but this is my only gripe with this phone.
When all my messages get stuck in "sending" I have to put it in airplanes mode one time for every message I'm trying to send.
I also have a horrible problem with not receiving all the sections of long text message.
Sent from my VS910 4G using XDA App
Samsuck said:
Sigh..
Nevermind.
Click to expand...
Click to collapse
i guess turning notifications off didnt work? lol
xjli said:
i guess turning notifications off didnt work? lol
Click to expand...
Click to collapse
That's not it, me setting a delay in handcent to prevent the texting issue didn't work.
Unfortunately, I think I may have to get a new phone, this is happening way too often, and as much as I love the phone, and Revolt rom. I am tired of my girlfriend *****ing at me for not replying, when I have it's just that I encounter the "stuck at sending" problem, at least 3 times a day
Samsuck said:
That's not it, me setting a delay in handcent to prevent the texting issue didn't work.
Unfortunately, I think I may have to get a new phone, this is happening way too often, and as much as I love the phone, and Revolt rom. I am tired of my girlfriend *****ing at me for not replying, when I have it's just that I encounter the "stuck at sending" problem, at least 3 times a day
Click to expand...
Click to collapse
Mine has only gotten stuck twice, but both times I cleared it by calling voicemail. Worth a try, easier than a reboot.
Sent from my VS910 4G using xda premium
mine only gets stuck when i have pretty much no service.. like cant make a phone call use data only type of service. otherwise, no issues.
This still happens to me alot
Sent from my VS910 4G using XDA App
one solution i just read is to delete your texts. once they start to become full the phone has a problem sending. try erasing your threads then it should work. i just googled this problem since i ran into it and am testing it now
I will be following this as it happens to me excessively.
Same here. i thought it had something to do with the handoff between wifi and 4G, but after reading this thread, I'm not so sure. For me it always seems to happen when I've been connected to a wifi network and switched to 4G. I'm testing not running wifi at all today to see if it happens again.
Same problem here. I concur that it appears to be an issue with sending text messages "too quickly."
I also called Verizon, got bumped up to "Tier 2 Support" and spent well over an hour on the phone doing every little thing they asked. I am going to try using the Handcent delay feature and see if that helps.
For those of us on Revolt...Does anyone know if/think it may have something to do with v1.5 still using V4 and not having the latest radio update? Or is this a problem for those using the stock rom and V6 as well?
jamRwoo said:
Same problem here. I concur that it appears to be an issue with sending text messages "too quickly."
I also called Verizon, got bumped up to "Tier 2 Support" and spent well over an hour on the phone doing every little thing they asked. I am going to try using the Handcent delay feature and see if that helps.
For those of us on Revolt...Does anyone know if/think it may have something to do with v1.5 still using V4 and not having the latest radio update? Or is this a problem for those using the stock rom and V6 as well?
Click to expand...
Click to collapse
Yup, sending messages to quickly is my theory as well but the handcent delay didn't work for me. I set it to 1.5 seconds which I figured should be enough.
Do any devs have any insight on how or why this may be occuring? It'd be awesome if someone knew of a fix. I'm pretty confident that it's a software issue and not phone related
Samsuck said:
Do any devs have any insight on how or why this may be occuring? It'd be awesome if someone knew of a fix. I'm pretty confident that it's a software issue and not phone related
Click to expand...
Click to collapse
It happens when your text threads are full. If you erase your texts they send. The the revolution had trouble with dealing with the threads
Sent from my VS910 4G using Tapatalk
jackpot08 said:
It happens when your text threads are full. If you erase your texts they send. The the revolution had trouble with dealing with the threads
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
I really don't think that has anything to do with it. The threads can't get "full" unless you set a limit (which I didn't), and I was still having the issue even after deleting all of my texts (one of the many things Verizon had me do on the phone). I'm no dev, so I could be wrong about this, but I feel like a fix that easy would've been diagnosed by now.
I agree it's a software issue of some sort...it doesn't seem consistent enough to be a hardware issue. There's threads on the LG forums about it. The handcent delay seems to have helped me, or at least I don't find myself wanting to throw my phone across the room as frequently.
On a lighter note, while on the phone with Verizon, the lady had me turn off my WiFi because "When it's turned on your phone sends the text messages through the wifi."
jamRwoo said:
I really don't think that has anything to do with it. The threads can't get "full" unless you set a limit (which I didn't), and I was still having the issue even after deleting all of my texts (one of the many things Verizon had me do on the phone). I'm no dev, so I could be wrong about this, but I feel like a fix that easy would've been diagnosed by now.
I agree it's a software issue of some sort...it doesn't seem consistent enough to be a hardware issue. There's threads on the LG forums about it. The handcent delay seems to have helped me, or at least I don't find myself wanting to throw my phone across the room as frequently.
On a lighter note, while on the phone with Verizon, the lady had me turn off my WiFi because "When it's turned on your phone sends the text messages through the wifi."
Click to expand...
Click to collapse
Verizon T1 tech's don't know anything. Their solutions to everything is usually a "factory reset"
SMS is in no way sent via WI-FI lol
So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
kcraptor82 said:
So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
Click to expand...
Click to collapse
First off I'll say that ML2 had been known to be buggy. For your first problem, did you make sure Glove Mode is disabled? For your second problem I have no idea. Sorry I can't be more helpful.
If it is in fact stock, do a software update to KitKat and it should fix your stability issues. I can't because of root.
About 2 days ago I noticed when i receive a call, it rings but the screen is black. If i hit the power button it will wake the screen but it doesn't show I'm receiving a call except for the fact I lose LTE ( I'm on Verizon). I can also double tap the screen ( have the mod) and it will wake but still nothing. Once the call is over it will show a missed call in the status bar. I'm rooted but on 5.0.1 stock. Was working fine until a few days ago. Anyone else?
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
KB112 said:
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
Click to expand...
Click to collapse
No, not using Lux. Starting to piss me off. Just shows up out of the blue and haven't really installed any new programs in a while.
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
chemguru said:
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
Click to expand...
Click to collapse
That was a great idea but still didn't work. I took the screen protector off and still the same thing. I might try a custom rom but I think it's time to sell. I love big phones and I do like this phone but it may be a tad too big for me. Might put it on Craigslist but the hicks in my area don't understand what "Nexus" is or "price is firm"...."will you take $150 for that there phone?"
alnova1 said:
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Click to expand...
Click to collapse
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
SP_Kenny said:
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
Click to expand...
Click to collapse
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
alnova1 said:
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
Click to expand...
Click to collapse
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
SP_Kenny said:
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
Click to expand...
Click to collapse
I just installed it and it seems to have fixed my problem for answering calls. Have no idea what was wrong before on the original rom. Seems to be running nicely and Verizon is working fine it seems like. Thanks for the recommendation.
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
SP_Kenny said:
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
Click to expand...
Click to collapse
I definitely will as soon as I head out and do a little testing on it.
I had this exact problem with my wife's Nexus 6 but mine was functioning fine. Turns out that under SETTINGS - SOUND & NOTIFICATION - APP NOTIFICATION she had the Goggle Dialer blocked.
Have the exact problem outlined by the original thread starter, scour a few webpages with different sort of solution.... nothing works!
My solution: Simple, just uninstall the Phone app updates, voila, all back to normal.
Hope it'll help someone.