Recently updated my T-Mobile LG G2 to the the 4.4.2 update. Before then update, anytime I got a text message, my screen would light up. However, after the updated it doesn't do that anymore. Anyone know why or having the same problem?
At work I use wifi-calling since I don't get service and if I need to send a MMS, I use the stock app. I know I can get a 3rd party app, but those apps don't send MMS since there isn't data available.
Thanks for your help. Would love to get the screen to light up again!
I just updated today and am having the same issue. Tech support thinks it may be a glitch but not 100% sure.
Same issue here. I haven't found a fix.
It's a little off topic, kind of, but have you tried acdisplay? It's like how the moto x reacts when you get a message.
Sent from my LG-D801 using Tapatalk
I think they removed that feature in KitKat. Kinda sucks because I liked it.
Sent from my LG-D801 using Tapatalk
Related
Anyone else notice that they're not getting notifications for some received texts on the Inspire? It seems to be random, and I don't notice the new text until I open up the messaging app and see it there, I don't get sound/vibrate or anything in the notification bar. I'm using the Inspired ROM and rooted but I don't think that's the cause of the problem.
I noticed the same thing this morning. I'm completely stock for the moment.
Sent from my HTC Inspire 4G using XDA App.
Well, I guess I'm glad it's not just me. I hope somebody has a fix for it.
I only sent a test message last night after I got the Inspire and it was received and I was notified without issue. Then I installed Handcent and turned off stock messaging app Notifications and Handcent has been working fine.
Rooted with a dhd rom here. I didn't think I was having this problem but checked my messages and sure enough I had one from a hour ago I never got a notification about..... the gf soooo isn't going to believe me its my phone again.
Sent from my Desire HD using Tapatalk
yg17 said:
Anyone else notice that they're not getting notifications for some received texts on the Inspire? It seems to be random, and I don't notice the new text until I open up the messaging app and see it there, I don't get sound/vibrate or anything in the notification bar. I'm using the Inspired ROM and rooted but I don't think that's the cause of the problem.
Click to expand...
Click to collapse
I had a similar issue where my 2 Gmail accounts weren't giving notifications when I received new email. Also my Sense clock/weather wasn't always updating the weather when I unlocked the phone.
I ended up doing a factory reset and reinstalled all my apps manually and everything appears to be fine at the moment.
Yep, same problem. Seems to only happen later in the day?
ditto
**********
Anything guys?? This is really frustrating
Really need help with this. Bump.
Sent from outside your window with my Inspire 4G
I've had the same thing happen. I was in the middle of a conversation and it seemed like the other person just disappeared. Was going to send them another text when I noticed they had actually responded.
The issue clearly hasn't been resolved... It's happening to me as well. No notification. Or I get it, hear it and feel it, and then unlock my phone and no notification in the top bar or on the msg icon on my homescreen. But its def there when I open msgs....this is very frustrating as I've been patiently waiting by my phone for an answer about a new job. Has anyone had a fix for this? I'm completely stock no root. I'm about to go on to ATT and have words with them if it can't be resolved I'm geting a new phone...this is stupid we can't get basic functionality to work....out of the box.
You could try using a different SMS app like Handscent that does notifications itself. I think Go SMS does notifications too.
Or they could admit there is an issue and fix it. I shouldn't have to get a third party app to do basic phone functions like sms and phone. Wtf!
Or you could root your phone instead of expecting AT&T to fix something when it takes them months just to release updates for things that should have been included in the first place.
Well its not really on ATT its on HTC. And besides rooting would void my warranty. And if I get this job ill be leaving the country, in which case id like to return the phone as I doubt it will do me much good in the Netherlands. Either way. Shoulda worked correctly out of the box. It's an HTC sense/Rom issue not an ATT service issue.
So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
I switched to this Motorola RAZR HD from my GS3 about 2 months ago. I love the phone. Battery life is awesome, and the phone is lightning fast.
However, in the past week or two, I found that I cannot send MMS messages when connected to WiFi. When I turn off WiFi manually, I can then send MMS no problem.
I do recall doing an OTA update about 10 days ago, which is right around the time my problem started, but I'm not 100% sure that this started exactly after the OTA update. I've also been noticing since the OTA update my phone has been a bit laggy. My phone used to be lightning fast, but now its acting like my GS3 that I had. Again, not sure if this is at all related to any of the other things.
So whats the wifi fix? Is there a known problem with the latest OTA update?
I'm on 4.1.2.
Build #9.8.1Q-62_VQW_MR-2.
System version 9.16.6.XT926.Verizon.en.US
Thanks guys?
MMS needs the carrier's internet to work..not WIFI...at least that's how it is on my network (Bell).
Sent from my XT925 using xda premium
slickfing said:
MMS needs the carrier's internet to work..not WIFI...at least that's how it is on my network (Bell).
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
I am aware of that. It is my understanding that the phone disables WiFi to send an MMS and then enables it after the message is sent. It used to work just fine. I don't know what could be causing my problem. I have not changed any settings.
Just wanted to update that I'm still having these problems. 50% of the time the phone will send MMS. The other 50% of the time it will just hang there and keep trying to send and I manually have to turn off wifi to get the MMS to send. Phone still lags, probably worse than ever.
This is also not the same phone as when I first posted. I had a replacement from Verizon a few months ago. The problems carried over with the new phone.
I have been using an app called Clean Master to clean my cache and unwanted files. Seemed to work well at first, but now it doesn't feel like it does anything.
So I think they weren't working at all because my IMEI wasn't updated with AT&T when I got my replacement phone. Got that addressed.
Since then, I was able to receive old MMS, but even new ones sometimes get hung up on trying to retrieve them. exiting app and going back in doesn't fix it.
Starting the phone up again does though..
Made sure APN settings are good to go, unchecked 'mobile data' in sms settings and re-enabled within Hangouts.
I'm on stock rooted 4.4 (and franco kernel)
any idea whats going on? It seems like other people are having this problem too but I don't understand it. Thanks.
I am seeing the same issues here.. Stock play store purchased and rooted on Sprint, sometimes it works sometimes it doesn't, sometimes even SMS sits forever and wont send or receive until I restart the phone, trying to find someone with a Sprint purchased N5 to compare APNs with
Its almost 2014, you would think someone would be able to straighten out the massive amount of MMS issues with android phones :/ It should "just work" to the customer
I have a feeling it has something to do with Hangouts app itself..
I have issues with hangouts indefinitely, also with textra and handcent. Like OP said,sometimes it works sometimes it doesn't.
Sent from my Nexus 5 using xda app-developers app
Teczeus said:
I have issues with hangouts indefinitely, also with textra and handcent. Like OP said,sometimes it works sometimes it doesn't.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
That's interesting you're also experiencing it with other apps.
I haven't tried anything but Hangouts.
Maybe it's a Kit Kat issue? no clue.
Considering you have At&t and I have sprint, im guessing ruling out the carrier is OK.
Sent from my Nexus 5 using xda app-developers app
Teczeus said:
Considering you have At&t and I have sprint, im guessing ruling out the carrier is OK.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
This is true.
Running on metro pcs and my mms is perfect with hang out and sliding messaging pro. Metro runs gsm off T-Mobile towers.
Sent from my Nexus 5 using Tapatalk
Interesting, i wonder what the root of the issue is since it's selectively working.
Can't be hardware, because it selectively works whereas my data and nothing else has been on the fritz, and it seems like whenever I receive errors rebooting and going back into the app it loads the ones it was hung up on. Seems like it downloads it, but just shows an error instead of displaying the MMS.
Hmmm
And I had AT&T double check the IMEI I provided them was accurate..
Hopefully it just resolves itself eventually, either the network, or a software hiccup, or whatever it is.
Because this Nexus 5 I have right now is a perfect "copy" or whatever you want to call it, a perfect build.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
It makes sense that that would be the culprit too because it requires root access, and permissions don't seem to kick in until slightly after the phone boots up initially which would coincide with mms received and sent just for those first few moments.
Good luck all, found this advice somewhere else, and so glad it's not a hardware defect as I had suspected it wasn't.
tyrellcorpnexus said:
Interesting, i wonder what the root of the issue is since it's selectively working.
Can't be hardware, because it selectively works whereas my data and nothing else has been on the fritz, and it seems like whenever I receive errors rebooting and going back into the app it loads the ones it was hung up on. Seems like it downloads it, but just shows an error instead of displaying the MMS.
Hmmm
And I had AT&T double check the IMEI I provided them was accurate..
Hopefully it just resolves itself eventually, either the network, or a software hiccup, or whatever it is.
Because this Nexus 5 I have right now is a perfect "copy" or whatever you want to call it, a perfect build.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
It makes sense that that would be the culprit too because it requires root access, and permissions don't seem to kick in until slightly after the phone boots up initially which would coincide with mms received and sent just for those first few moments.
Good luck all, found this advice somewhere else, and so glad it's not a hardware defect as I had suspected it wasn't.
Click to expand...
Click to collapse
Thanks for the update! More knowledge into my brain housing group to share now lol.
FuMMoD said:
Thanks for the update! More knowledge into my brain housing group to share now lol.
Click to expand...
Click to collapse
No problem I hope it helps some of you guys out!
tyrellcorpnexus said:
Interesting, i wonder what the root of the issue is since it's selectively working.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
Click to expand...
Click to collapse
In my case MMS started working after disabling Adblock in the app itself. Then I went ahead an uninstalled. Thanks for the head up!
jonzr said:
In my case MMS started working after disabling Adblock in the app itself. Then I went ahead an uninstalled. Thanks for the head up!
Click to expand...
Click to collapse
For sure! adaway had been working well for me.
Same issue here on Tmobile
tyrellcorpnexus said:
For sure! adaway had been working well for me.
Click to expand...
Click to collapse
I am having same issue on Tmobile with stock Nexus 5. Only restarting the phone helps.
jamjr74 said:
I am having same issue on Tmobile with stock Nexus 5. Only restarting the phone helps.
Click to expand...
Click to collapse
Same here but with hancent and hangouts
I just want to know if anyone else is having the issue of being unable to answer the phone using the ring or reject calls doing the same thing. the phone rings and I see the call is coming but when I move the ring to accept the call the phone locks up. same when I want to reject it. I have to reboot the phone. is there a fix for this? I had NO problems before I went to the 4.4.2 update which is the only update I applied. I changed back to the .15 and .17 radios in hopes of a fix [yes I know the phone app probably could be the culprit but I am desperate] to no avail.
Not had this. If you've changed radios then you have an unlocked loader. Full wipe and reinstall your ROM is my suggestion.
Sent from my Nexus 5 using xda app-developers app
I'm having the same issues.
The incoming screen with answer reject don't show up.
I thinks it's something to do with the ROM
Sent from my Nexus 5 using xda app-developers app
Google told me to clear the system cache and if that didn't work to reset the phone to stock firmware. apparently there are plenty of people having this issue which a Google search confirmed. I emailed them and told them that this is a known issue by both Google and sprint and they sent me a link to request an rma and a new phone. one of the posts I read during my search implied that the user who did the same thing as I am doing got a new phone without the issue. Google did not in any way resist anything I said and simply said they were 'disappointed' that their fixes didn't work and are sending me a new phone. I will note that although my phone is unlocked and rooted I did receive an ota update to 4.4.2 and had the radio issues people are talking about. I reflashed to a couple of the older radios and that issue in and of itself was corrected. currently on .15 . very annoying that the lte and phone voice functionality on sprint are mutually exclusive. doesnt seem to be an issue on tmobile or at+t. they remain options once my etf gets to its minimum price in march.
kboya said:
Not had this. If you've changed radios then you have an unlocked loader. Full wipe and reinstall your ROM is my suggestion.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
the rom is stock from the ota received 2 weeks ago.