Ok first; I've re-flashed things, I've set my phone up EXACTLY the way I've had it previously and it's had NO issues. My idle drain is much higher, and I've changed nothing. I've gone from idling at 0.22-0.4% per hour to 0.8-1.5% per hour. I got these overnight to see if anyone can help me. Hopefully you can. Honestly I've ensured nothing is different (I have OCD, believe me ) - so clearly it looks like google play services, but it comes out of nowhere after it being fine for months :S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had the similar issue, usually my overnight battery drain was 2-3%. Then without any obvious reason last week it jumped to 10%, no new apps installed, except of auto updates of pretty essential apps which I do keep on my phone.
Meanwhile I got the OTA 3.2.7., updated & cleared cache in recovery but it stayed the same.
From Friday evening till Saturday evening Google Services & Google Playstore used more than 350 mAh of battery, almost the same amount as the 4h of SOT I squeezed out.
Last night I let the phone get discharged near empty, cleared cache and data & uninstalled updates for Google Playstore, went on Google Playstore to receive the update again and called it a night. Woke up this morning with only 3% drain. (Doze-OFF, Wifi-ON, Location-ON).
The issue might not be the same as yours but it sure has some common points...
SkipperZG said:
I had the similar issue, usually my overnight battery drain was 2-3%. Then without any obvious reason last week it jumped to 10%, no new apps installed, except of auto updates of pretty essential apps which I do keep on my phone.
Meanwhile I got the OTA 3.2.7., updated & cleared cache in recovery but it stayed the same.
From Friday evening till Saturday evening Google Services & Google Playstore used more than 350 mAh of battery, almost the same amount as the 4h of SOT I squeezed out.
Last night I let the phone get discharged near empty, cleared cache and data & uninstalled updates for Google Playstore, went on Google Playstore to receive the update again and called it a night. Woke up this morning with only 3% drain. (Doze-OFF, Wifi-ON, Location-ON).
The issue might not be the same as yours but it sure has some common points...
Click to expand...
Click to collapse
Cleared Cachce and data in apps > google play store and services? or just play store. and uninstalled updates for both?
How do you get the update again? Just load up the store?
Basically; I've re-flashed my phone several times so I doubt it's that but worth a try, and sounds similar.. I used to get 1-2% max over 12 hours, literally it was fantastic, but now I get much more, its annoying.
ritchiedrama said:
Cleared Cachce and data in apps > google play store and services? or just play store. and uninstalled updates for both?
How do you get the update again? Just load up the store?
Basically; I've re-flashed my phone several times so I doubt it's that but worth a try, and sounds similar.. I used to get 1-2% max over 12 hours, literally it was fantastic, but now I get much more, its annoying.
Click to expand...
Click to collapse
Yup, cleared cache & data of the Playstore app, then on the three dot menu uninstalled Playstore update (it reverts to factory version) and then just rerun the Playstore app and it updates itself on recent (6.9.21 - 3270725) version.
Today is running fine, no issues so far.
It is strange that it occurs after re-flashing, are you maybe restoring Playstore with the backup after flashing?
SkipperZG said:
Yup, cleared cache & data of the Playstore app, then on the three dot menu uninstalled Playstore update (it reverts to factory version) and then just rerun the Playstore app and it updates itself on recent (6.9.21 - 3270725) version.
Today is running fine, no issues so far.
It is strange that it occurs after re-flashing, are you maybe restoring Playstore with the backup after flashing?
Click to expand...
Click to collapse
I don't use any backups at all mate, I literally wipe everything and start fresh, don't even backup data, lol.
So you did this for JUST playstore? Not google play services.
I will try it
ritchiedrama said:
I don't use any backups at all mate, I literally wipe everything and start fresh, don't even backup data, lol.
So you did this for JUST playstore? Not google play services.
I will try it
Click to expand...
Click to collapse
OK...I think that makes your problem a bit more complicated than the one I was having.
Yup, I just did it for the Playstore app...but you can try to clean both, nothing to lose...
How long has this occurred over, it's not unusual for Google play services to be doing things in the background after flashing a rom, especially if you have Google restore / backup enabled. This should settle down after a couple of days.
ghostofcain said:
How long has this occurred over, it's not unusual for Google play services to be doing things in the background after flashing a rom, especially if you have Google restore / backup enabled. This should settle down after a couple of days.
Click to expand...
Click to collapse
Erm, 2 days, and it's never happened before when I've flashed anything, so I'm not sure why it would now, and backup is off for everything mate.
Related
Hi,
Maps appears always in the battery stats. I don't use Maps. I don't have GPS enabled (I enable it only when I use navigation software; not maps). Location services are always disabled.
When I force stop Maps, this app start itself automatically (right after stopping; sometimes afte some time).
How should I stop it permanently. It drains battery not that much.. but still would like to save some percent.
Thanks!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I believe you can disable it, if you dont like/have that option you can freeze it with Tibu.
Edit: Strange though it doesn't ever show in my bat stats. Are you using Latitude? I guess it could be showing because of Navigation.
I noticed my g-maps kept showing up in recent apps, and it turned out that it was because of an updated. Once I went into maps, and saw the "new features" page, it hasn't done it since.
Probably not related, but figured I'd throw it out there.
I agree with the Pirate; seems like latitude is signed in.
Thanks. I did following:
- started maps and 'accepted' new features.
- signed out from latitude. Yes.. seems that it was signed in all the time
Will report later if the maps will appear or not in battery stats again.
Thanks!!!
bullka said:
Thanks. I did following:
- started maps and 'accepted' new features.
- signed out from latitude. Yes.. seems that it was signed in all the time
Will report later if the maps will appear or not in battery stats again.
Thanks!!!
Click to expand...
Click to collapse
For sure signing out of latitude will save you some juice!
I have issues with google maps.
Version 6.3
Gps and location disabled not signed to latitude. But still have 3 google map service running. Quite annoying.
from what I've read around the internet, this is a problem across devices.
I don't use Latitude (never have), and have turned off location services. But Maps is still a persistently active service/process. I posted on a Google board, so hopefully they will reply.
Maybe the operative question is: who isn't experiencing this issue? Maybe we can figure out why.
Maps is always running for me too, but it is never using enough battery to even be on the battery usage statistics. I rarely see it in the recent apps list either.
I went a few days disabling Maps and noticed absolutely no difference in battery either. I'm perfectly OK with it running and taking up 9.3mb of RAM.
noma_pride said:
from what I've read around the internet, this is a problem across devices.
I don't use Latitude (never have), and have turned off location services. But Maps is still a persistently active service/process. I posted on a Google board, so hopefully they will reply.
Maybe the operative question is: who isn't experiencing this issue? Maybe we can figure out why.
Click to expand...
Click to collapse
Well i never have maps show up in my battery list, nor in system panel list. But i do see maps running in my settings app menu, 1 service and 1 process. So never seems to use any resources for me.
Google needs to fix this...can't really do anything to remedy this besides freezing or disabling the package when you are not planning to use it.
I've noticed considerably increased battery life with the apk frozen...even with latitude off and location updating disabled Maps causes some battery drain.
Clear data is a solution . . . sort of!
By clearing the data of the maps (in the application manager), you can have the Google maps drop off from your running app list.
But, all the setup/data in the Google maps will be lost by doing so !
so, this is a solution if you don't care the setup / cached data.
I have a Captivate with rooted stock Gingerbread. I have to kill Maps ever so often when it shows up. It's always low double digits percentage of battery usage for me.
No latitudes (Join Latitudes shows up in Maps->More). GPS not enabled.
I allways unninstall it as i dont need it, but i do want it but will wait till they fix it. For me the best map and gps is me ( roll down the window and ask for directions)
Sent from my Galaxy Nexus using xda premium
Sorry for the near-necropost, but I'm coming at a similar issue, from a slightly different angle, and wanted to scope out any thoughts anyone might have here instead of opening a new thread.
My issue with Maps constantly running is no as focussed on the battery life issue, but rather privacy. I run LBE (basically a selective App permission firewall) and one of the features of this program is the ability to Allow/Prompt/Deny certain application privileges. Well, I set it to prompt me to allow Maps to obtain my location, thinking that it would be only a minimal annoyance since I only use Maps once or twice a week.
Think again. Did you know that while Maps sits there, open, in the background, it checks your location constantly? (well, once every half our or so). I finally set LBE to allow maps to get my location without prompting me, but LBE still flashes a notification bar alert to let me know when an app has requested something like my location. Sure enough, every half hour or so, Maps asks for my location, regardless of how long (measuring even into the days) it has been since I have actually used the app. I don't have Latitude running.
This cannot possibly be something that everyone else is just cool with?
Please tell me this isn't just an accepted evil without a solution?
Root and delete maps from /system/app. do t hardly use it anyways. There is also an older version somewhere that doesn't run in the background and you can actually stop.
Sent From My Sprint Galaxy Nexus
Google Maps is running for the network location... barely uses any battery life (having your screen on for a minute will use more battery life) and will not slow down your phone. You guys are freaking out over nothing
derekwilkinson said:
Google Maps is running for the network location... barely uses any battery life (having your screen on for a minute will use more battery life) and will not slow down your phone. You guys are freaking out over nothing
Click to expand...
Click to collapse
No, that's not the case, or at least that's not the behavior that I am referring to.
Looking at the event log in LBE, there are actually two things that Maps is doing at regular intervals in the background:
"Track Your Position"
"Obtain Your Current Position"
That's how it is worded. I'll also add that I have experienced other apps where LBE asks me whether I'll grant permission to obtain my "Network Location". That is a distinct permission (at least as far as LBE categorizes them), and is not what I'm concerned about with Maps.
Regarding the suggestion of uninstalling Maps, I still use it, as mentioned, once or twice a week.
Google tells us that to check the "use location data" means background location data will be sent. Weird thing is practically everyone has a blind spot for it - the old not-reading-the-EULA problem perhaps...
I personally think the info could be of interest for population densities, average distance travelled per day, literally where people go and when. With the obvious proviso that none of it is personally identifiable. Just aggregates...
Google is actually sitting on a goldmine of info, but realistically it will be parlayed into advertising profitability.
To be more precise: "Allow Google's location service to collect anonymous location data... ...Collection may occur even when no apps are running."
Hi, recently I found the GPS on my Galaxy Nexus refuse to lock properly.
I used maps for years, and the locating seems good enough (it seems that these locations are from wifi or other source now).
Recently I installed an app to track my route, which really needs true GPS, and the problem began.
Every morning, when I go from my home to work, the GPS just not work at all (no lock). Sometimes it works when I leave home, but minutes later, it lost lock and never gets back during the whole route (even after I reboot the phone and clear the AGPS data with GPS Test). After I got to the workplace, and tried again, the GPS is still not working.
What's surprising me is the GPS works fine when I leave from my work pace and head to my home in the afternoon. It locks fast and works well all the way. (This is the same route in the morning)
The same problem happens for several days (bad in the morning, good in the afternoon).
With GPS Test (https://play.google.com/store/apps/details?id=com.chartcross.gpstest), I notice the phone really gets a lot of satellites(>9) with good signals, but somehow none of them are used to calculate my location (they are all grey in GPS Test's satellite view).
Does anyone have any idea what's the problem and how to fix it?
The phone is stock android 4.3 unrooted.
Thanks.
The attached file is the screenshot of GPS Test this morning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PS. the gps works great at noon, have no idea why it refuse to work every morning.
I have a similar problem, when I leave work from a particular exit my gps doesn't find anything for quite a while, where as if I leave from another it gets it straight away.
The only thing I can think of is there are lots of buildings and roofs around that first exit, where as the second one is straight into a carpark. Maybe there is too much interference when you leave home, but not work?
slatsmckracker said:
I have a similar problem, when I leave work from a particular exit my gps doesn't find anything for quite a while, where as if I leave from another it gets it straight away.
The only thing I can think of is there are lots of buildings and roofs around that first exit, where as the second one is straight into a carpark. Maybe there is too much interference when you leave home, but not work?
Click to expand...
Click to collapse
The thing is when I leave home at night, the GPS works well, but not in the morning. On the other hand, when I arrival at work, the GPS still not working, but it works at noon.
I try to figure if the timing is the problem. For example, if much more interference in the morning or the satellites decide not to communicate with me at that time?
As you can see in my attachment, it actually found a lot of satellites, but no data received from any of them. Don't know why, and never noticed before.
gancuimian said:
The thing is when I leave home at night, the GPS works well, but not in the morning. On the other hand, when I arrival at work, the GPS still not working, but it works at noon.
I try to figure if the timing is the problem. For example, if much more interference in the morning or the satellites decide not to communicate with me at that time?
As you can see in my attachment, it actually found a lot of satellites, but no data received from any of them. Don't know why, and never noticed before.
Click to expand...
Click to collapse
Have you checked/changed the server you use for gps? I had to change mine from US to oceania (depends where you are) at one point and that seemed to help
slatsmckracker said:
Have you checked/changed the server you use for gps? I had to change mine from US to oceania (depends where you are) at one point and that seemed to help
Click to expand...
Click to collapse
Great idea, I never would have thought of that on my own! I normally use FasterFix from the Play Store to set the GPS server to US. After the first day, locks were very slow and inacurate, and by the second day, I stopped getting locks altogether. I tried flashing back to stock, still didnt work. Then i came across your post, and after setting it to Oceania, I got a lock in under 10 seconds. Many thanks!
How to checked/changed the server you use for gps
A30N said:
Great idea, I never would have thought of that on my own! I normally use FasterFix from the Play Store to set the GPS server to US. After the first day, locks were very slow and inacurate, and by the second day, I stopped getting locks altogether. I tried flashing back to stock, still didnt work. Then i came across your post, and after setting it to Oceania, I got a lock in under 10 seconds. Many thanks!
Click to expand...
Click to collapse
How to checked/changed the server you use for gps
Thank you!!!
A30N said:
Great idea, I never would have thought of that on my own! I normally use FasterFix from the Play Store to set the GPS server to US. After the first day, locks were very slow and inacurate, and by the second day, I stopped getting locks altogether. I tried flashing back to stock, still didnt work. Then i came across your post, and after setting it to Oceania, I got a lock in under 10 seconds. Many thanks!
Click to expand...
Click to collapse
Hello stranger,
I signed up to this forum just to reply to your post. I recently installed Paranoid Android 4.4 (final build) on my Gnex and GPS was not working at all (would show 0/0 satellites, sometimes 1 or 2, but NEVER lock). Where as previously on PA-3.99 it was fine. After scouring the internet for the last two days and trying anything that didn't involve me wiping, reflashing, etc. your post single handedly saved me from doing any of the extreme measures. I just went to download faster fix, but then stumbled upon fasterGPS. This app, using lovely root access (yay root!), allowed me to set my NTP to North America and then Canada. Now my GPS works perfectly! Thank you again so much!
Phone:
Samsung Galaxy S7 (SM-G930T)
Rooted
Android 7.0 Nougat
Watch:
Samsung Galaxy Watch (SM-R810) 42mm
I turned on the watch for the first time and followed instructions to download the Wearable app. The wearable app also installed 3 other apps (Galaxy Plugin, and two other Samsung helpers). Everything went smoothly until I got to the swirling galaxy screen on phone that said "Pairing underway". After waiting for a long time, it said "This is taking longer than expected. Tap CANCEL to try again" while the watch continued to display "Check your phone to complete setup."
Things I've tried:
- Uninstall and reinstall Wearable (and the 3 other apps). Also tried clearing data/cache
- Using the Galaxy Watch in standalone mode, turning on bluetooth, and then trying to pair with phone
- Same as above but I updated Tizen software through wifi
- Reseting the Galaxy Watch (both through the standalone setting menu and the "hold down home button to get into recovery mode" method)
- Toggling bluetooth on both devices, resetting network connection on phone so there won't be any stored bluetooth settings (this is what one of the Samsung live agent instructed on the website)
- Installing Samsung Health on my phone, then resetting all synched data (not that there were any) according to some random forum post
- Prayer
Notes:
I made sure to give all permissions to those apps and XPrivacy wasn't interferring. I haven't factory reset my phone, there's too much customizations and data. I also don't have another phone I can try this on.
Please help me, I am so sad!
I dont know how long you waited but I used my S7 to pair and it took like over 10 mins to complete the pair but it eventually did.
hotplex said:
Phone:
Samsung Galaxy S7 (SM-G930T)
Rooted
Android 7.0 Nougat
Watch:
Samsung Galaxy Watch (SM-R810) 42mm
I turned on the watch for the first time and followed instructions to download the Wearable app. The wearable app also installed 3 other apps (Galaxy Plugin, and two other Samsung helpers). Everything went smoothly until I got to the swirling galaxy screen on phone that said "Pairing underway". After waiting for a long time, it said "This is taking longer than expected. Tap CANCEL to try again" while the watch continued to display "Check your phone to complete setup."
Things I've tried:
- Uninstall and reinstall Wearable (and the 3 other apps). Also tried clearing data/cache
- Using the Galaxy Watch in standalone mode, turning on bluetooth, and then trying to pair with phone
- Same as above but I updated Tizen software through wifi
- Reseting the Galaxy Watch (both through the standalone setting menu and the "hold down home button to get into recovery mode" method)
- Toggling bluetooth on both devices, resetting network connection on phone so there won't be any stored bluetooth settings (this is what one of the Samsung live agent instructed on the website)
- Installing Samsung Health on my phone, then resetting all synched data (not that there were any) according to some random forum post
- Prayer
Notes:
I made sure to give all permissions to those apps and XPrivacy wasn't interferring. I haven't factory reset my phone, there's too much customizations and data. I also don't have another phone I can try this on.
Please help me, I am so sad!
Click to expand...
Click to collapse
Archangel said:
I dont know how long you waited but I used my S7 to pair and it took like over 10 mins to complete the pair but it eventually did.
Click to expand...
Click to collapse
I remember waiting until it stopped trying to pair. I will wait longer this time. Fingers crossed.
Edit: It's been over 40 minutes now, I included some earlier screenshots.. This is about the same wait time when I first tried it. Still no change.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIXED
I disabled Xposed Framework, rebooted, and was able to pair. Xposed Framework was then enabled without much hiccup. YAY!
Little different scenario here, I was trying to pair Watch active 2 to new S21 Ultra and I got stuck on dead "done" button, couldn' go any further. Googling it I found Samsung suggestion to do factory reset and everyone said it works. Well I didn't want to do factory reset because I just spent hours doing a serious de-bloat so I checked my list of apps I got rid of and re-installed one that sounded pretty relevant: "com.android.companiondevicemanager" and that was my lucky guess, I was able to pair my watch right away after that. No factory reset.
^thanks for the feedback....glad you got it sorted! cheers
https://www.androidcentral.com/pixel-6-network-problems-december-update
I just ran into this driving through an area where I usually lose signal and call drops. Today the phone did not reconnect to the network until about a half mile away from where it usually reconnects. Other than that, I've been experiencing better data connections since the December update.
For me personally, the mobile network quality on P6P (1 physical sim, one esim) is bad compared to my 2 physical sims Oneplus 5T, for both carriers. I am in Aus. My area does not have 5G covered, always at 4G. I have tried both A1 and A5 updates (for AU) and usually the mobile strength (I see the triangle bar) of A5 is even worse than A1 lol. I don't know what happens in the background, but I have not expected mobile network becomes a problem with a phone in 2021. And because the network quality is poor, the battery life saw immediate consequence. Maximum 4.5 hours SOT even with "Proxy" wakelock issue addressed and no heavy-tasking time.
I have a new Sim from Verizon arriving on Monday which I hope improves my cellular connection. I had to reboot my phone today while driving through a rural area in order to reconnect. Toggling airplane mode didn't work.
I hear on a certain telegram group that users are using the modem back from November. This solves the problem because the full signal is back. You have to unlock and flash the radio from november. When thats done your great signal is back! So there must be a problem with the radio from december.
You can simply remove the radio (modem) from the .zip of factory images. Then in fastboot flash it mode: fastboot flash radio radioblablabla or whatever it's called. The only drawback is that you have the bootloader must unlock and this at the cost of a complete wipe
Here's the proof that it works. It's not the pro version, but that doesn't matter.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@DanielF50 brought to my attention the following Reddit post:
DanielF50 said:
Apparently the latest beta for Carrier Services potentially fixes this, some people in the comments are still having issues though (not that I have/had this issue).
Source:
https://www.reddit.com/r/GooglePixel/comments/rk1hfk
Click to expand...
Click to collapse
Fixes for some people but not others and I am in the others camp!
I personally don't have this issue. However, I read that updating Carrier Services to the latest BETA version fixes it.
Taking a LONG time to join the Beta program for Carrier Services. Been over 10 minutes and still waiting for approval.
After 20 minutes, I was approved to join the Beta program. I cleared memory and rebooted. Hopefully this will improve my carrier connection. I have a new SIM from Verizon too.
swieder711 said:
Taking a LONG time to join the Beta program for Carrier Services. Been over 10 minutes and still waiting for approval.
Click to expand...
Click to collapse
Yeah happened to me, you can try to close the Play store and go back in and you should've joined and can update from there!
wilpang said:
Yeah happened to me, you can try to close the Play store and go back in and you should've joined and can update from there!
Click to expand...
Click to collapse
That's happened to me for some non-Google app recently too. Closed the play store, might have even rebooted, and then the beta version was ready for me to update to.
swieder711 said:
Taking a LONG time to join the Beta program for Carrier Services. Been over 10 minutes and still waiting for approval.
After 20 minutes, I was approved to join the Beta program. I cleared memory and rebooted. Hopefully this will improve my carrier connection. I have a new SIM from Verizon too.
Click to expand...
Click to collapse
You can also find the beta app on APK mirror
Downloading the carrier services beta version totally worked for me. I'm in Germany with T-Mobile (Congstar) and got the A1 December update. Since the update I had no signal at work most time but now it's on full power again.
I just updated the P6P with the January update (OTA manually requested in System Update).
After the update, MMS is not working in the Google messages app.
I am on T-Mobile in US and phone purchased unlocked from Google Store
MMS settings haven't changed in the app.
SMS works
Unsure if this matters, but a couple MMS came in right at the time the phone was starting up after the update / when the notification of "finishing update" or something to that effect was showing.
Has anyone else experienced issues with Google Messages MMS with January or December update?
Thoughts on how to resolve this?
If a solution is posted elsewhere, let me know and I will ask the Mod to remove this post.
I'm on a stock P6P US Tmo with Jan. update. MMS is working fine for me, including airplane mode using wifi.
johninsf said:
I just updated the P6P with the January update (OTA manually requested in System Update).
After the update, MMS is not working in the Google messages app.
I am on T-Mobile in US and phone purchased unlocked from Google Store
MMS settings haven't changed in the app.
SMS works
Unsure if this matters, but a couple MMS came in right at the time the phone was starting up after the update / when the notification of "finishing update" or something to that effect was showing.
Has anyone else experienced issues with Google Messages MMS with January or December update?
Thoughts on how to resolve this?
If a solution is posted elsewhere, let me know and I will ask the Mod to remove this post.
Click to expand...
Click to collapse
New bugs? Again?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jokes aside, best try to reset your network/messaging/phone services/apps. That might help you.
MMS is working again but it required factory resetting the phone. Resetting WIFI / mobile only didn't help. Nor did clearing storage in carrier services (if that matters).
On a positive note, signal seems a bit better with this update. I cleanly move from LTE to 5G to 5G UC walking down the hall in my flat. (e.g. my Bermuda Triangle of signals). I love the Net Monster app. I never knew where the cell points are located near me. I am between 2 LTE points which explains the bouncing back and forth. Interesting to see the 5G UC point which is much farther away than I thought.
I am glad that UC is in large letters now vs. the microscopic letters before the update.
I noticed android messages somehow had notification sounds set to nothing, which was odd as I never touched it, but wondered why my phone was vibrating and only playing a sent message tone. I cleared app data and it's back to default.
Try setting up your phones carrier settings manually and see if it helps, or try resetting the value to default.
Go to settings > network > SIMs > APNs (at the bottom) > three dots in the top right > reset to default.
What carrier do you have?
@RetroTech07 thank you! I will keep this in mind in the future.
I have had disappearing notification sounds for years with Android. Not this time though because I completely reset the phone.
Try this....1. turn wifi off. 2. Force stop messages. 3. Clear cache. 4. Open messages. 5. Check the status of "chat features", if it takes longer than a couple minutes to be "connected"...repeat steps 2 &3.
pedro6669 said:
Try this....1. turn wifi off. 2. Force stop messages. 3. Clear cache. 4. Open messages. 5. Check the status of "chat features", if it takes longer than a couple minutes to be "connected"...repeat steps 2 &3.
Click to expand...
Click to collapse
That doesn't really impact MMS though, it's just setting up to use advanced features like wifi and chatting through your PC if you wanted.
No not really. If you're setup to use RCS and it's not connected you will not get any MMS's. Hope you get it figured out.
That's not true. I don't use that feature and get MMS just fine.
Thanks for the options! MMS is working after the factory reset but if it stops again, I will give these a try.
johninsf said:
MMS is working again but it required factory resetting the phone. Resetting WIFI / mobile only didn't help. Nor did clearing storage in carrier services (if that matters).
On a positive note, signal seems a bit better with this update. I cleanly move from LTE to 5G to 5G UC walking down the hall in my flat. (e.g. my Bermuda Triangle of signals). I love the Net Monster app. I never knew where the cell points are located near me. I am between 2 LTE points which explains the bouncing back and forth. Interesting to see the 5G UC point which is much farther away than I thought.
I am glad that UC is in large letters now vs. the microscopic letters before the update.
Click to expand...
Click to collapse
I hate the large letters. Looks so stupid.
If I had better vision, the size might be too much. Poor vision sucks so I will take what I can get!
Sidebar: I hate menus at restaurants where the font is a 6 + poor lighting. I just order the special or a burger or salad. LOL.
Seriously, I take a picture of the menu and zoom in.