I am pretty sure that many people who are reading this topic have met the situation when the message:
"A wireless radio must be attached to use this phone" pop-up on PDA screen.
My question is: This situation could be battery related? We do not speak here about chip damaged, ROM update, SIM broken and so on...
Does anyone solved this problem by replacing battery?
If so, please post the phone name and if this happened even if it is charging or not!
Believe me that I tried all the solutions found on Internet (ROM update, tweak WM....). The only thing I didn't do was to reflash radio part because I did not find the appropiate file.
When the GSM died, also the vibrator stops to work. That's why I'm thinking to battery problem...
Also this kind of problem appears on many type of devices and on some forums was mentioned that may be a battery problem but no one confirmed it!
On the other hand my wife's LG has a very strange behaviour (were blocking, sudden reset). I send it to service LG and it cames back with diagnosis: It can't be repaired.
Lucky me that I found a very smart guy who did some tests on it and he replace the battery and nothing else and the phone works perfect from then...
That is why I'm telling you that battery could be a source of very unexpected problems and strange behaviours of phones.
MoshPuiu said:
Believe me that I tried all the solutions found on Internet (ROM update, tweak WM....). The only thing I didn't do was to reflash radio part because I did not find the appropiate file.
When the GSM died, also the vibrator stops to work. That's why I'm thinking to battery problem...
Also this kind of problem appears on many type of devices and on some forums was mentioned that may be a battery problem but no one confirmed it!
On the other hand my wife's LG has a very strange behaviour (were blocking, sudden reset). I send it to service LG and it cames back with diagnosis: It can't be repaired.
Lucky me that I found a very smart guy who did some tests on it and he replace the battery and nothing else and the phone works perfect from then...
That is why I'm telling you that battery could be a source of very unexpected problems and strange behaviours of phones.
Click to expand...
Click to collapse
I have heard of people with radio issues replacing the battery & fixing the device. Why not pick up a replacement battery and try? It won't be expensive
I already ordered online an original one but I have to wait because there is no stock available yet (on ebay I'm afraid to buy a new one because of fake batteries).
MoshPuiu said:
I already ordered online an original one but I have to wait because there is no stock available yet (on ebay I'm afraid to buy a new one because of fake batteries).
Click to expand...
Click to collapse
it fixed it?
Am I the only one here that is underwhelmed by this phone?
I received my 64GB version today, did the rooting/recovery stuff, installed some apps (mostly news) and find the phone slow, with shocking battery drain, poor network signal and a purplish hew on display ( gets better if brightness turned up)
It's on stock with 44s Cyanomod software version.
My comparison is with the my previous phones S3,S4,N4,N5 and HTC One M8.
I'm going to initiate a return.Very disappointed.
Well, I came from, have a G3, which I really like. We've gotten 3 OPO's. Battery lasts for several days with moderate use, heavy use for my daughters phone, very nice. We've made no special 'battery setup' to have this several days battery life.
In general, I find the quickness on par with the G3. The phone works well, overall we are pretty happy with them, and two of the three of us mess about with the rooted side of 44s to experimental L ROMS. A few of the L ROMS, though notably more snappy, still are rough, so unless I don't have anything to do, I try and stay away from them... until the oem version comes out.
Display is great and uniform. Networks work just like my G3, consistency and strength, the data/phone side providing I have the correct APN.
I was just checking the OP against my G3 yesterday, after the G3 having sat for a month, being un-touched. My sense of the two remains the same. The G3 is a bit more polished, but the OPO allows for getting into the dirt and playing with it.
Sounds like your initial experience has been unsatisfactory, and the initial 'presentation' of a thing can sure put a cloud over it. Just like meeting a person for the first time, first impressions can make or break it.
Good luck.
bluegrass55 said:
Am I the only one here that is underwhelmed by this phone?
I received my 64GB version today, did the rooting/recovery stuff, installed some apps (mostly news) and find the phone slow, with shocking battery drain, poor network signal and a purplish hew on display ( gets better if brightness turned up)
It's on stock with 44s Cyanomod software version.
My comparison is with the my previous phones S3,S4,N4,N5 and HTC One M8.
I'm going to initiate a return.Very disappointed.
Click to expand...
Click to collapse
I hope this is a hardware problem with your phone, and a fluke. I've just ordered today and hope it is better than my Moto X(2).
cam30era said:
I hope this is a hardware problem with your phone, and a fluke. I've just ordered today and hope it is better than my Moto X(2).
Click to expand...
Click to collapse
Hopefully for you this is a hardware issue.
I've initiated a return and since this will take some time I've decided to install other ROM's in case it was a ROM issue.
Just installed the Mahdi ROM but Titianium backup restore doesn't want to work.
Time for another ROM.
Will update if another ROM solves the issues I've had.
No luck with this phone.
Installed mahdi, Stock 4.4.4, Pan Android and cDroid.
Another strange issue that I've had with all ROMs is Textsecure and Viber apps not working. I have never had issues with these apps.
Started the RMA.
I'll go back to the N5 and live it's poor battery & only 32GB storage.
bluegrass55 said:
Hopefully for you this is a hardware issue.
I've initiated a return and since this will take some time I've decided to install other ROM's in case it was a ROM issue.
Just installed the Mahdi ROM but Titianium backup restore doesn't want to work.
Time for another ROM.
Will update if another ROM solves the issues I've had.
Click to expand...
Click to collapse
I had a problem with TB on Mahdi as well. It would crash spontaneously. I wiped out TB and installed fresh. IIRC it was something like that that cleared up the issues. If I remember I'll let you know.
Agree 100% op. Got mine a few weeks ago from craigslist. Very laggy phone on all ROMs I've tried. Battery life isn't anything to brag about either. Only reason I'm keeping it is because the lollipop ROMs seem good soo far. Definitly not a flagship killer phone though.
You guys probably got bad hardware. I am on the 2nd OPO (broke first by accident), both have been really good. Exactly the same setup on OPO and N5, OPO battery lasts twice as long and there are no lags of any kinds. I actually sold the N5 on Ebay today and bought a 16gb OPO, so I am going to have two
Alright,
Phone: Nexus 5 2013
Android: 5.1.1
Country: Canada
So I've started to get a lot of issues on my Nexus 5 that I ordered back in November 2013 (when it was released) and they are too big to be left alone. If I cannot fix them, I'll have to buy a new cellphone and there's none that interest me right now, nor that I want to change my current Nexus 5.
Issues:
My Nexus 5 doesn't connect to my cellular network anymore. I'll stay on "No service" and refuse to connect to any Operator Network stating that the network is unavailable at the moment, even thought it is. Sometimes, it'll connect to the network for 15 to 30 minutes, before losing it for the next 8 hours.
It becomes hot really, really quick randomly. The upper back part of it becomes hot, and according to the Nexus 5 architecture, the battery isn't even located there so I don't know what could make it heat up like that. This happens even without it being charged, and without me using it a lot (games, apps, etc.)
The phone will randomly restart for no reason, and sometimes stay stuck on a "boot loop" (Starting apps X of Y... before restarting).
The vibrate mode is messed up. It'll vibrate every 30 seconds for a notification (email, Facebook, SMS, etc.) despite the fact that there's nothing, absolutely nothing. Right now I disabled the vibration/sound mode to avoid that issue.
The battery gets drained really, really fast. Like overnight, while not being used it'll fall from 100% to 5%. It never used to do that. When I don't use it overnight, it would lose maybe 20%, even less than that. It started recently as well.
All these issues were present in past versions of Android, starting at 4.4 so I doubt the version is in cause here, but it's still a possibility I guess.
I got my SIM card changed for a brand a new one, troubleshooted the phone with everything I could find online before giving up and restoring it to it's default settings, but the issues are still present. I don't know what I should check anymore. If you have any comments, experiences or solutions I could try to solve my issues, please let me know since at this point I'll most likely try all of them. Also, if you need more information on my phone, system, etc. let me know as well.
Thank you.
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
firemaned said:
Is your phone stock/rooted etc?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It used to be rooted, but it's not anymore. Any way I can make sure that it's rooted or not? When I used the SuperSU app back then I realized at some point that it wasn't rooted anymore (it was telling me that this app can only be used on rooted devices). I think the bootloader is unlocked because when I open my device, it shows me the little lock icon, but it's open (unlocked). Also, it's freshly reset to factory default (from yesterday).
dahawthorne said:
There is a recognised problem with the Nexus 5 that a dead battery can kill something in the radio functionality. Since you have so many problems your best bet is to start with the software - a full refresh of the ROM. It might be worth waiting a few days for the release of Android 6.0 which is supposed to be coming in the next week (anything from 29th September to 5th October, but who knows...?). If you can't wait, save whatever you want from the device and install preview 3 MPA44I - it works very well on my N5, and since I'm not using it as my daily phone (I have a Nexus 6) the standby battery life is amazing. At the moment it shows 76% with 13 days 12 hours left.
Click to expand...
Click to collapse
I already did a Factory Reset on my phone yesterday, so I guess I don't have to do another one? Right now, if I follow what you just told me, I should wait until the release of Android 6.0 (M) and upgrade to it then see if it solves my issues. I just hope that it won't take a long time to be pushed to my phone like it was with Android 5.0. Or your other solution is to flash the latest preview for Android 6.0 (M) on my phone and see how it goes, right?
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
dahawthorne said:
If you've restored a ROM and lost root, and are back to 100% stock Android, then as far as I know the Android 6 upgrade will be provided over the air (OTA) and will work fine. Whether it resolves your problems is a different question. I myself tried everything to make my radio work again after the battery died, and eventually contacted Google, who were honorable enough to send me a replacement (refurbished, but effectively as good as new) which works perfectly.
Click to expand...
Click to collapse
That was my original plan. I called the Play Store support this week and they told me that my phone was elligible for a replacement till April of 2016. I found that weird because it would make it a 2 years and a half guarantee but at least I had my backup plan in mind. Then I called today to order a replacement and the guy told me that my guarantee expired back in November 2014 (1 year after I bought my Nexus 5, which made sense) so now I'm stuck with this one. I don't know why, but since this morning (after creating this thread), the cellular network cameback. It still drops sometimes but only for a few seconds and if not, I enable/disable the Plane mode to make it connect again. However, the battery drain, phone heat, random restart and messed up vibration issues are still present. I can deal with them however until Android 6.0 (M) gets released. The most important thing was the cellular network. We'll see tomorrow how it goes. Still awaiting tips and tricks for my other issues if anyone have some.
For the battery draining issue, I think I have the paid version of Greenify somewhere and was thinking of using it to see if it helps, even though I didn't have that issue at the beginning.
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
CalculatedRisk said:
Instead of a factory reset you should try using fastboot to flash the factory image for a fresh start.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
And I imagine that the factory image is still present on the device? This is what I find weird, because when I "reset" my factory to defaults, it restores it to Android 5.1.1 even though the device came with 4.x. I come from the computer field, and a Factory Reset on a computer uses the manufacturer's image present on the CD, DVD, USB or partition given with the computer to reinstall the original OS that was present on it and the OEM software as well. If the computer was eventually upgraded to Windows 8.1 and came with Windows 7, Windows 7 will be restored, not Windows 8.1. So I can understand now that a "Factory Reset" doesn't really return the device to its factory state, right?
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
dahawthorne said:
I would guess that you've had an OTA update to 5.1.1? You would have had to actively accept it - it doesn't install itself automatically. The factory image isn't (as far as I'm aware...) on the device, it just resets components back to default values - I may be wrong about this. There's obviously no way that a Kitkat device could mysteriously upgrade itself to Lollipop in any other way than a deliberate flash or an OTA update.
I use Greenify myself and it appears to do what it claims, but I wonder if it will become unnecessary when the new Doze function comes in with Android 6. Maybe the two will complement each other for optimum battery life. Any experts out there that can comment?
You mention that it's the upper back that becomes hot - I'm guessing that this is where the processor is. Mine does the same if it's running under load - for example when taking a TWRP backup. And anything that's creating heat has to get its energy from somewhere, hence the battery drain. If there is a rogue app that's running even when you're not using the phone Greenify might kill it - worth a try.
And final comment (for the moment... ) - the padlock with the gap means that your bootloader is unlocked, but doesn't mean that the phone is rooted. It does however mean that the phone can accept new ROMs and can be rooted.
Click to expand...
Click to collapse
I did have an OTA update to 5.1.1, yes.
And I talked to one of my friend who's really into phones (used to work for Bell and he's usually the person I go to whenever I have issues with my cellphone), and he suggested me to wait until Android 6.0 comes out, and then to fastboot it on my Nexus 5 since OTA updates can be buggy sometimes. I could actually fastboot the phone right now (well tonight) with Android 5.1.1, but if Android 6.0 is to come out next week (or the one after), it might worth the wait, depending on whether or not I can keep the cellular network working. Otherwise I would have to go through 2 flashboots in 2 weeks and I can't really be bothered to do that
And I don't know where the CPU is in the Nexus 5 (I could look it up) but the zone where the heat is isn't where the battery is so there's that. However, my friend told me that the fact that my cellular network isn't working could explain why the battery is being drained so fast, but can't explain the vibrate mode and random restarts issues.
I was having battery issues on Stock ROM, but now I am using CM12.1 so battery is not draining very fast.
When I am inside my home or in some other house or building, the network disconnects very often. However, if I am outside, the network works pretty well.
The notification LED, when being configured using CM12.1 settings, shows blue color on green color selection and green color on blue color selection.
I had some of the same problems with my phone, it would reboot randomly throughout the day. With mine if I charged it overnight with it off when I turned it on in the morning it would only be at 85%. I ended up contacting LG and I paid $170 to get it fixed, they have replaced the mainboard twice so far. After the second time it had no issues, and that lasted a couple months but I have sent it back again to be fixed. If you bought the phone on a credit card they usually extend the warranty by a year, that's what I did, filed a claim and they sent a cheque for the repair cost, very simple actually. But I suspect it might be the same problem as mine, some hardware issue, especially if you've reset the phone.
Just for info, the CPU is indeed at the top rear of the phone, so this is undoubtedly where the heat is coming from.
https://www.ifixit.com/Teardown/Nexus+5+Teardown/19016 - see step 11 saying "The Quad-core, 2.26 GHz Snapdragon 800 SoC is layered beneath the RAM".
I reckon it's a rogue app, which I hope isn't a system app, running wild - a system app will be hard to cure.
A ROM refresh is probably a good place to start, and if you can wait for Android 6.0 then why settle for less...
Wiped my os on nexus 5 trying to install nethunter only comes on in twrp. very new to this be easy on me ive previously installed a vm lab with kali linux.
I have downloaded adb and fastboot
Using winace . Before this my pc would not recognize my device, "no drivers". But now it shows up on the pc control panel as active and found
However snap pea still cant find drivers although now it says are you fornatting your phone with only one option "yes" then it just dissappear. ... but before I downloaded adb, fast boot ... snap pea was simply saying no drivers found.... Please help. ..thank you.
Sent from my GT-I8190 using XDA Free mobile app
Here's an update on my situation: the cellular network is back at both my house and my workplace. The way it works, it seems that it takes it a day to "adapt" itself to the location and then gives me network. So at first after the Factory Reset, I didn't have network at my house, the day after I did. Now, when I went to work on Monday I didn't have network, but when I did on Tuesday, I did. My job is an hour of road away too, and at some places on the road I don't get any network, but it happens less and less as I travel back and forth.
The random restart and overheating issue are still present however. I didn't test the notifications (on vibrate) but I will soon. As long as I have my cellular network, I don't care about the other issues, until Android 6.0 (M) gets released and I fastboot it on my phone.
Now, since I bought my Nexus 5 using a MasterCard, I remembered that they have a promotion which double the guarantee on electronics (up to a 1 year), which means that I have a 2 years guarantee on my phone. So I called LG, and they have a promotion right now, $150 to get my phone repaired by their tech center IF it can be repaired. If they can't, they send it back and gives me a 50% refund (around that number).
My current plan of action is to wait for Android 6.0 (M) to get released, flashboot it on my phone and see how it goes from there.
Thank you for all the replies so far, they really helped me and still help me today
Good luck man. Keep us updated.
Sent from my Nexus 4 using XDA Free mobile app
Alright so, I fastbooted Android 6.0 on my Nexus 5, and it seems to have done the trick. I have network everywhere now, even on the road. I still lose it from times to times (a few seconds only), but this is a "normal" behavior considering the carrier I have. The notification issue is also gone, and so does the restart issue since I didn't have it once so far. But I only fastbooted it yesterday evening so it might be too soon to say that.
Now, I still have the "overheating" issue, but it could be from me playing Fallout Shelter, I really don't know. I used to play Clash of Clans alot, and graphically speaking, I think it's more demanding than FS, but I never had that overheating effect before. One thing I noticed however is that after fastbooting Android 6.0, my battery drops real fast, even when idle. I thought that Android 6.0 was supposed to improve the battery life. I'll try to see what process, app or activity is taking the most juice out of it, but I'm sure this isn't normal.
Alright so it took me an hour to go from my house to my workplace, and my battery went from 34% to 12%, while being on standby. This isn't normal I guess. I'll need to charge it to 100% once, and then use the Battery setting to see what's taking all the juice.
Might have spoke too soon. When going to work today, I went in a room where there's usually no signal (or the signal is very weak), and lost the network. It's normal in that room so I didn't pay much attention to it, but now I'm not able to get back on the network. Even searching for the Network Operator fails. Sigh, it really looks like I'll have to send it to LG for repair. I guess I need to fastboot it first to erase all my data, because they need to use my phone to test the repairs they make?
Hello,
My wife's S6 just received Marshmallow last week. We're on Straight Talk service on AT&T's network and everything was working fine up until Wednesday night. First, her phone went from 45% to dead in the span of an hour. Then the next day she had issues with her mobile data where she had no connection. We deleted/reloaded APN settings but that didn't fix it. I have the same service on my Nexus 6p and the same settings and mine works like a champ.
I did notice that her Android OS was consuming 45% of her battery and without any idea how to fix it I went ahead and performed a factory reset, twice. She still has excessive battery drain (70%-40% in 5 minutes), she no longer has mobile data, and her cellular/texts work sporadically; however Android OS is now under control. She now has cellular standby eating up 30% of her battery and app optimization was at 28% (This could have been due to reinstalling all her apps). I would like to say it's a hardware issue but seeing as how multiple people are having some of the same issues I think it's an actual problem with her update.
Is there any way to fix this without going back to Lollipop? If that is my only option where is the best place to find a legit version?
Here are her phone's specs:
Model: SM-G920T
Android Version: 6.0.1
Android Security Patch Level: May 1, 2016
Baseband version: G920TUEU3DPD6
Kernel Version: 3.10.61-7610624
[email protected] #1
Thu Apr 28 19:59:51 KST 2016
Build Number: MMB29K.G920TUEU3DPD6
Look, I'm going to tell you this straight.
Marshmallow has had a lot of problems.
Just scrolling through a few threads reveal most of peoples problems come from after updating to M. My S6 is completely untouched, in fact, the battery life is better.
Google released M way too early without testing it with their lab devices enough. Too many bugs, too many things missing. My best guess is uninstall any apps your wife got recently and if that doesn't work, carry a cheap power bank until Google releases an update.
I was able to downgrade to 5.1.1 and it solved her battery issue, but not her mobile data. I called Samsung and we're going to get it serviced to see if they can fix whatever is wrong. What I find funny/frustrating is that any time a new version of Android is released (and lately apple too) there are always tons of problems with battery life and other issues. You figure they'd get it right one of these days.
I upgraded to M just over 2 weeks ago & my battery life/phone experience is excellent. I was also reluctant to update, but no regrets at all in hindsight. My advise: Watch out for OTA updates - rather download new firmware & use Odin to flash.
Head on over to good ol' Sammobile and download the latest firmware for your carrier and then follow the instructions to flash. Perhaps that might help.
Just wanted to provide an update. We just got the phone back from Samsung. They ended up replacing the motherboard and that fixed the issue with no mobile data. Also, the new motherboard may have fixed the battery drain issue. It's a little too early to tell but battery drain appears normal for now.
So I've had a T-Mo S7 for about a year and a half now. It's incredibly slow/unresponsive and I've spent a really long time troubleshooting.
I've done full factory resets, and direct ODIN OS installs with data wipes. Whenever I do this, the phone starts out, with all current apps installed, extremely fast/responsive. I have a somewhat limited app library, and I haven't added anything since the phone slowed down noticeably.
About two months ago, the Samsung Device Maintenance app, which until then only reported battery draining, said "Some apps or processes are overloading the system (CPU)" and the app it reported was something like com.android/google.searchbar" which I assume is the google search bar widget. I thought, "awesome, the device app is actually doing something." I told it to kill the app and my phone sprung to life. My phone was super fast for a long time, but is now back to being super slow again. I searched "Apps" in device settings and can't find any apps/processes that sound anything like search bar. Also, how is there not a system resource monitor in system settings!? Clearly, an app is hogging resources, because I've experienced periods of responsiveness. Is there no direct way to figure this out without doing the safe mode process of elimination?
Can someone help shed some light or suggest further troubleshooting steps? Thanks in advance.
I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!
tony yayo said:
I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!
Click to expand...
Click to collapse
So I promise it's not the battery because I had it factory replaced by Samsung. To answer your question, yeah you have to send it in. With the waterproofing they have to do it at a repair center. However, for me it was 100% worth it. I think I was without the phone for about 10 days. But having a brand new battery life was incredible.
Also, as I was working with the phone slow for a while, it immediately and dramatically became quick after device maintenance killed that process. But a few months later, I'm back to suuuuper slow.
The S7 is getting old. Old things slow down. It's planned obsolescence. I've gotten to the point of turning notifications off for all apps and only using badge numbers to tell me when to check something. I also use do not disturb a lot when gaming instead of game tools because game tools is another app but do not disturb is more of an internal process. As soon as my taxes come back I'm probably going to get a S8+