Issues with MD4

Anyone noticing battery drain issues after the MD4 update? I used to get 16-20 hours with 3 hours of screen on prior to the update, and now it seems to be draining at a faster rate (getting 12-14 with 2 hours screen on). I am not rooted running stock Touch Wiz and on wifi most of the time. All my other settings are equal to before with only my google email and calendar being synched.
 
Many people seem to be reporting somewhat better battery life. Have you looked at the battery page to see what, specifically, are you highest battery users?
 
I have an issue after i installed MD4, when i plug in my headphones i am getting the audio options and constant notification in the bar. I had fixed this on the previous build by uninstalling the contextawareservice file through TB. I assumed that i would need to do that again when i started seeing the popup however the file is not showing as installed. Does anyone have any other idea how to turn this off in MD4 or any other idea?
 
Last edited:
Many people seem to be reporting somewhat better battery life. Have you looked at the battery page to see what, specifically, are you highest battery users?

Thanks for your response....My second day with the update seems to be much better. It looks like it took a day for things to level off. Really liking the update, appears to be smoother and the the Android OS and system seem to be using less resources. My usage for multi window is still limited..but it's great to see Samsung roll it out on all their Galaxy devices. On a tablet I could really see this feature come in handy.
 
I have an issue after i installed MD4, when i plug in my headphones i am getting the audio options and constant notification in the bar. I had fixed this on the previous build by uninstalling the contextawareservice file through TB. I assumed that i would need to do that again when i started seeing the popup however the file is not showing as installed. Does anyone have any other idea how to turn this off in MD4 or any other idea?

You've discovered Page Buddy! I didn't find it useful, either. I'm on a custom ROM, but I think this is the same on stock MD4. Go to Settings / Display. There should be an item for PageBuddy there. Tap on the left side of that row (not on the on-off toggle). This will bring up a page with three options that can be individually checked or unchecked. Or you can just to back to the Display screen and turn them all off from there.
 
I'm having the issue where I cannot swipe to call a contact. Anyone know how to correct this issue? Please advise and thanks in advance.
 
I would try clearing cache for both the contacts app and the phone app. Go to Settings / Account Manager, scroll all the way to the right, and then scroll down to Contacts. Tap that row, then tap the clear cache button, and the force stop button. Repeat for the Phone app. Then exit out of settings and try again.
 
To swipe to call, to have to start your finger to the right of the contact picture as opposed to starting your finger on the contact picture. It takes some getting used to.

Sent from my SPH-L710 using Android Central Forums
 
I did clear the cache for both contacts and phone. And I also followed the instructions to swipe at the right of the contact picture which works. Big thanks to both team members for the quick response and precise nfo. Thanks!
 
I just got the ota this morning and can no longer swipe to call a contact... swiping from right to left brings up messaging just fine just not to call
not rooted all stock

I too have this problem! PRETTY SILLY you now have to swipe after the contact pic... oh well. Plus my battery took a beating... It's been 5 days since I updated and it doesn't hold like it used to. WHACK!
 
I too have this problem! PRETTY SILLY you now have to swipe after the contact pic... oh well. Plus my battery took a beating... It's been 5 days since I updated and it doesn't hold like it used to. WHACK!

Everything works on my phone. I do have root.
Try doing a factory reset.
 
My swipe to call works fine. It is just a little tougher and it not as responsive. You have to so a quick swipe.

Sent from my SPH-L710 using Tapatalk 2
 
Plus my battery took a beating... It's been 5 days since I updated and it doesn't hold like it used to. WHACK!

Everything works on my phone. I do have root.
Try doing a factory reset.

Unfortunately, stas may be right. Sometimes an OTA (which is what post 1 really is) or a dirty flash just cause issues like this. If you're rooted, use TiBU to back up all your apps and settings, and do a reset. That will most likely resolve your battery woes.
 
Ok today I notice something really strange in my battery stats. My phone was at 100 percent charge last night, I put it in airplane mode. 6 hours later this morning I turn it on and its at 87 percent. I checked the battery stats and I see media server being active for 6 hours and 57 mins and my battery had drained 13 percent over night in airplane mode. I have never seen this before. The only two things I'm syncing are gmail and calendar. Nothing else is being synced. Could someone tell me why media server would be consuming so much battery. I did not see this issue before the update.uploadfromtaptalk1367681854287.jpguploadfromtaptalk1367681872285.jpg

Sent from my SPH-L710 using Android Central Forums
 
I too have this problem! PRETTY SILLY you now have to swipe after the contact pic... oh well. Plus my battery took a beating... It's been 5 days since I updated and it doesn't hold like it used to. WHACK!

Media server will show activity whenever you're downloading anything (whether it's a media file, and application, or anything else), but if you were in airplane mode that probably isn't it. Unless you were streaming movies via WiFi. ;)

A corrupted SD card, or a corrupted file on the SD card, could cause this. If you have an SD card, try removing it and see if that resolves the problem. There's also a potential problem with DRM (copy protected) files and a process called DRM Protected Content. If you have any of these files on the internal card, try backing them up to the SD card, or a PC, and deleting them.

If you haven't done it already, reboot the phone. Just like ctrl-alt-delete on a PC, a reboot can resolve all sorts of glitches.
 
My swipe to call works fine. It is just a little tougher and it not as responsive. You have to so a quick swipe.

Sent from my SPH-L710 using Tapatalk 2

If start your swipe just to the right of the contact picture as opposed to starting on the picture, it will work 99.9% of the time. No need to quick swipe it.
 
Guys,

Just updated my phone to MD4 using the OTA update from sprint.

I had previously been running LJ7 and had it rooted with CWM as the recovery and left the stock rom.

Because i couldn't install the OTA without putting the stock recovery back, i did so and then installed the OTA, which took me to MD4.

i am now having TONS of bluetooth issues with my car and in general, where the phone wont play into my car stereo at all, music or phone calls and the bluetooth reboots the phone completely if i disconnect or at random.

should i factory reset the phone? anyone seeing this as well?
 
There was no need to mess with the recovery. This thread tells you how to update without losing root and with CWM recovery: http://forums.androidcentral.com/sprint-galaxy-s-iii/272331-your-way-update-md4.html . And it's safer than using the OTA on a rooted phone, too.

It's hard to know what the issue with your phone is now. A factory reset is often recommended after an OTA, and if it won't cause you too much grief in terms of lost data and such, it's probably a good idea. Alternately, you could reinstall CWM, and follow the steps in post #2 of the linked thread, and hope that solves your issues. I suspect you'll need a factory reset at this point either way.
 

Trending Posts

Forum statistics

Threads
956,628
Messages
6,969,233
Members
3,163,591
Latest member
cass_wbb