yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] cas8180:
I used the leak from sextape and also added freezas optimized kernel and other than then some of the jerky ness I can't complain my battery life has literally doubled. Something must have been jacked in my mb1 ROM.
[Sprint Samsung Galaxy S III] Whiplashh:
I did notice something new. You cannot use the brightness slider in notification tray when phone is below 5%. You could before MD4.

Not a big deal, just informing everyone.

------------------------

Sprint Galaxy S3

Whiplashh Rom

Look it up. :trooper:
[Sprint Samsung Galaxy S III] auau465121:
I'm I the only one who has the talkback app start every time I restart my phone?
[Sprint Samsung Galaxy S III] npsiwak:
Put me in the list of people who are noticing choppy-ness and jerky-ness returning to the scrolling. I notice it the most in facebook and the official twitter app, but I honestly started to notice it before. Am i alone in this?

Rooted stock MB4, stock kernel/firmware/modem/etc, with CWM recovery. Flashed in freeza's rooted stock rom for the update since OTA's wouldnt stick with any of the OTA rootkeeper tricks.
[Sprint Samsung Galaxy S III] phyba:
I'm just running the md4 kernel and modem on mc3 build and have lag at times. I don't think its the kernel as its happeeing on all kernels. Must be something in the build
[Sprint Samsung Galaxy S III] dcharleyultra:
Nope. (I have accessibility enabled for Tasker and LMT.)

Swyped from my SPH-L710
[Sprint Samsung Galaxy S III] auau465121:
O okay go figure I had a flashlight call & SMS enable. I cut that off and problem is gone :D
[Sprint Samsung Galaxy S III] toolegit:
:laugh:
[Sprint Samsung Galaxy S III] interhawk1:
I have the same problem
[Sprint Samsung Galaxy S III] cas8180:
Hope someone can come up with a fix for this.
[Sprint Samsung Galaxy S III] colonel.shepard:
Buttery smooth here
[Sprint Samsung Galaxy S III] Omar04:
Yep same here since day 1. (Full Stock BTW)

Edit:

Also... almost full storage 4.2GB left of internal Memory. No issues at all with scrolling or swiping.

Every device behave differently. (YMMV as some say)
[Sprint Samsung Galaxy S III] g_money:
Scrolling between screens has always been kinda choppy for me (both before and after md4). I was messing with my phone after 1 of my restores, and it seemed to be running so much smoother *before* I added all my widgets. Once I added my widgets seemed the jerkiness came back? I never attempted to verify because I'm keeping my widgets (because I love widgets!). I'm gonna say no increasing choppiness with md4, for me.

Your mileage may vary...

g_money
[Sprint Samsung Galaxy S III] babyschmoof:
I'm completely stock and not rooted. Since the update (from Google's) site, the battery life has been way down. Nothing else has changed. My screen is still set to auto, and times out every minute. According to battery stats, the screen is taking 80 percent of the battery.

Thoughts? Any chance something was missing from the Google direct download? The radio/modem updates were included, correct?
[Sprint Samsung Galaxy S III] poit:
The update runs checksums at the beginning of the update, so if something was corrupted or missing it would error out and not update. You get a new rom and modem. You can check by looking at settings>about device. The baseband is the modem, the build number is the rom. Both should end in MD4

Go through all your sync settings and make sure none of the settings have changed. Also, make sure it's not just you playing with the new update. I know for the first day or two my battery usage goes way up because I keep playing with the phone:D

As I think about it, 80% screen is not right. Are you sure the screen is ever turning off?
[Sprint Samsung Galaxy S III] babyschmoof:
Everything looks good, and I verified the screen turning off.

I'll let the battery drain until it turns off and do a full charge. Hopefully things level out in a few days.

One thing I noticed is that the phone seems to charge faster.
[Sprint Samsung Galaxy S III] Slomodrop:
Anyone with choppy scrolling tried an fsTRIM like LagFix or tried an entropy mod like Crossbreeder or the other one ( ant recall name).

// Galaxy SIII SPH-L710 // MOAR 3.0 + MD4 baseband // KT747 ktoonservative-BFQ 384-1809Mhz + rescaling // Crossbreeder entropy + DNS + blocking // LagFix fsTRIM // Nova Prime // sent from xda premium
[Sprint Samsung Galaxy S III] Chuck_IV:
Seeing it too on my wife's unrooted S3. I'd notice a rare stutter before MD4, but after MD4, every scroll to another screen in tha launcher now has a hitch/stutter to it.

Luckily it's not something my wife really notices. It's a bit annoying to me since I have a buttery smooth Note 2, so I see it plain as day.
[Sprint Samsung Galaxy S III] npsiwak:
Yeah, I tried to remove all my widgets on the screen (at least the ones I rarely use, like google keep or ask.do), and it hasnt helped all that much. Its pretty strange to me, since my wife's unrooted, stock, updated S3 runs smooth as silk. I think that it is probably something software related, i might have a rogue app running somewhere. What is a good app to monitor that?
[Sprint Samsung Galaxy S III] j76ms:
I've always noticed a very slight stutter on both of our non-rooted galaxy s3s. It only occurs occasionally when swiping home screens. It is like a small hiccup. My wife could care less but I notice it every time. It does not happen when I use TSF Shell so I don't really care. I always assumed it was something in Samsung's touchwiz. I notice it and am slightly annoyed every time I use my wife's phone.
[Sprint Samsung Galaxy S III] cas8180:
This started happening when I was running mc3 as well. As soon as rolled back to mb1 smoothness returned a d all choppy ness went away
[Sprint Samsung Galaxy S III] TrueRain:
That's funny because the choppiness on my phone went away after I updated from MB1 to MD4
[Sprint Samsung Galaxy S III] bxfinest:
Try unmounting the external sd if you have one. I just got a GS3 this week and the choppiness (both in gaming and ui) was annoying the hell out of me until I did that.
[Sprint Samsung Galaxy S III] sputnik767:
I've had choppy scrolling in the home screens, app drawer, and folder open/close animations in every update after LJ7. LJ7 is completely smooth, but choppiness is very noticeable in every subsequent update.
[Sprint Samsung Galaxy S III] Whiplashh:
I had no home screen choppyness on ICS, LJ7 had it, MB1 wasn't as bad, but still there, MD4 still here, but it doesn't bother me as much.

------------------------

Sprint Galaxy S3

Whiplashh Rom

Look it up. :trooper:
[Sprint Samsung Galaxy S III] metalfan78:
Has anyone else had any issues in contacts? When I try to slide left/right for message /call it hardly ever works now.
[Sprint Samsung Galaxy S III] galexandr:
I'm having the same problem. Came here to ask and saw that someone already asked. :)

Any help welcome.
[Sprint Samsung Galaxy S III] Whiplashh:
I have noticed that too. Kinda annoying. One of the few features of touchwiz I actually use.

------------------------

Sprint Galaxy S3

Whiplashh Rom

Look it up. :trooper:
[Sprint Samsung Galaxy S III] galexandr:
In reply to chopping screen. I'm on the launcher (nova) and considered going back to stock. What are your thoughts.
[Sprint Samsung Galaxy S III] metalfan78:
Yea, I like that feature. I'm glad I'm not the only one
[Sprint Samsung Galaxy S III] Whiplashh:
Never used nova. I use apex. ;)

Agreed.

------------------------

Sprint Galaxy S3

Whiplashh Rom

Look it up. :trooper:
[Sprint Samsung Galaxy S III] sputnik767:
It's very interesting how different some of these "identical" phones behave regarding updates. For me, LJ7 is perfect, for you and many others, LJ7 had issues. My GF's AT&T S3 is perfect on ICS, but the only JB update kills her battery in a half day.

---------- Post added at 03:46 AM ---------- Previous post was at 03:45 AM ----------

Yep, this too. For me, swiping left for message generally works, but swiping right doesn't work most of the time.
[Sprint Samsung Galaxy S III] Rapture Veteran:
anyone in here having an issue with the screen not turning off when its on the charger? im not sure if this is ktoonez kernel or this, but i just notice it today
[Sprint Samsung Galaxy S III] sputnik767:
I actually like the TouchWiz launcher and it is generally smoother for me than any 3rd party launcher. At least LJ7 was. But if you want to go back, just clear app defaults in Nova and select TouchWiz when you press the home button (assuming you didn't get rid of TouchWiz).
[Sprint Samsung Galaxy S III] Whiplashh:
Me too while on touchwiz. I just use it more because I like some touchwiz only widgets too.

------------------------

Sprint Galaxy S3

Whiplashh Rom

Look it up. :trooper:
[Sprint Samsung Galaxy S III] poit:
I suspect the variation has to do with apps and data on each users phones. I know that whenever my phone gets laggy, I can just kill apps and the phone gets back to normal. Some of these apps may not work well in 4.1.2, or the data may get wonky during the upgrade process.
[Sprint Samsung Galaxy S III] sputnik767:
That's what I thought at first too, but it was equally laggy whether coming from a full wipe and clean install, or a dirty install, or a clean install and app restore. At least in my case, apps don't seem to have much if anything to do with it. As it is right now, I am stock rooted, stock recovery, stock kernel, no debloating. I did the ODIN install, wiping all data.
[Sprint Samsung Galaxy S III] npsiwak:
I did this except for the data wipe, and can't seem to shake the scrolling lag, in essentially every app I use. Seems like it is something to do with a framerate issue, or maybe a rogue app. Whats the prescription for finding a rogue app? Better battery stats, searching for PWL?
[Sprint Samsung Galaxy S III] JoelB23:
Im wondering the same. My friends tried to put me in a group message and it ddint work. Also didnt work when i tried to start one. So i guess Sprint didnt fix it :crying:
[Sprint Samsung Galaxy S III] Exit_Only:
I must say MD4 is super solid. I'm running MD4 with my 4cyl Turbo Engine Scripts and its absolutely stellar. Battery life improved 10-15% over MB1 and very smooth overall vs MB1. I'm not a touchwiz fan but this update made me enjoy touchwiz finally.
[Sprint Samsung Galaxy S III] galexandr:
Fixed the slide to call by factory resetting the phone.
[Sprint Samsung Galaxy S III] Weston87:
So I mentioned this is a previous post that I was having trouble with the talk back setting. Well it happened again. It seems every time I restart my phone or take the battery out and start my phone up again the talk back setting keeps turning itself on. Does anybody know of a way to keep it turned off? I hate this setting.
[Sprint Samsung Galaxy S III] Exit_Only:
Go into settings...application manager.... And disable talk back. Problem solved
[Sprint Samsung Galaxy S III] Weston87:
Ok I did that and it worked but I still get the little hand icon in my notifications bar at the top. It still say that it is activated, but when I go to setting and go to accessibility it's not there. It's even not there in the app manager. Which is all good except for the annoying icon that I can't remove. Do u have any ideas as to how I can remove that?
[Sprint Samsung Galaxy S III] auau465121:
Do u have anything turn on in the accessibility settings? If so cut it off will fix your problem. Hit thanks button if helped
[Sprint Samsung Galaxy S III] Weston87:
Just auto rotate. Should I turn it off too?
[Sprint Samsung Galaxy S III] auau465121:
No I know it's crazy but if you have anything turned on in Accessibility / services settings then it will trigger it. Go to accessibility scroll down to services and see what is turned on in there cut it off
[Sprint Samsung Galaxy S III] Weston87:
Ok so I found what was making it do that and I even got the hand icon off for good. I went accessibility and scrolled down to services and turned off go launcher notification. And now it stays off. So if your using a launcher and you have its notifications turned on you will have to turn the it off.
[Sprint Samsung Galaxy S III] auau465121:
I wonder where u got this great idea from Lol.
[Sprint Samsung Galaxy S III] g_money:
Sorry in advance if this has already been asked, but:

Has anyone had a problem with S Voice since the update?

I was showing my phone to a n00b s3 user today, and accidentally pulled up S Voice (I never use it, other that playing with it when I first got my s3). He asked what it was, I tried to show him but kept getting the "no network connection" error? His worked fine though. He is still on mb1. I fixed it by clearing data and uninstalling updates. Works fine now. Just wondered if it had something to do with md4?
[Sprint Samsung Galaxy S III] Omar04:
Have nothing to do with MD4 it works fine. You said you unistalled an Svoice update but there's none the version on MD4 is 10.1 nothing else, I bet you installed the S4 Svoice leaked app on the S3 that one cause Network Error when launched and you don't remember. Or came with your custom TW rom if you have one installed.

Stock MD4 S Voice app. V10.1 notice there's no unistall update just a disable button.
[Sprint Samsung Galaxy S III] rocket321:
I was having a lot of stutter in fast games (e.g. subway surfers) and it would sometimes ignore swipes that occured at the time of a stutter. I've found that closing all apps (by holding home and then tapping the close all button) would return games to acceptable performance levels. I'm not sure what MD4 is doing wrong but it seems to not manage memory/multitasking effectively.

Admittedly, the ROM which gives me the best in game performance is CM10.0. All TW ROMs from LJ7 - MD4 have had some amount of stutter in games. MD4 does seem to be just a bit worse unless I remember to close all apps first.
[Sprint Samsung Galaxy S III] poit:
I'm just guessing here, but based on many reports of better battery life and stuttering, I'm beginning to think they did some retuning on this rom that's biased towards battery life. Perhaps it keeps the clock speeds lower and doesn't release memory as readily as previous roms with the intent of improving battery life. Just a guess.
[Sprint Samsung Galaxy S III] Exit_Only:
Stuttering??? On md4??? Been on it for 3 days and not one single reboot. This is the most stable this phone has ever been. No lag no nothing.

Users reporting stuttering need to do a full data wipe/reset. I did a full wipe right after the update and its unbelievably smooth and stable. Battery life is stellar.
[Sprint Samsung Galaxy S III] poit:
In my case I was on STOCK MC1 and updated OTA to STOCK MD4. There should be no need to do a full wipe and reset after an OTA update from one version of 4.1.2 to another version of 4.1.2 I've got lots of apps that I don't want to lose data on.

I stick by my original comment, something is tuned differently on this ROM. I expect the difference in people's experiences has to do with the running apps and the choice of launcher.
[Sprint Samsung Galaxy S III] Exit_Only:
Well you can stick by your opinions. I will choose to stick with the facts. I've looked at the code (I am a script developer) and there is nothing "tuned" differently. Samsung did do a lot of bug fixing but that's where it ends.
[Sprint Samsung Galaxy S III] Omar04:
This^^^
[Sprint Samsung Galaxy S III] poit:
So you are saying that now if we do do an OTA update that doesn't even change minor version numbers, we have to completely wipe our phones in order to keep them running right? That's absurd. That's never been the case before. There is a change in this rom that isn't playing nice with some apps/launchers. It may be a "bugfix" gone bad, it may be a change in cpu tuning, It may be some of the code that supports multiview. I don't know what. I'll keep looking for the next update.
[Sprint Samsung Galaxy S III] cas8180:
This is starting to remind me of the old ICS debate with the epic touch. While some claimed it was smooth and they had no issues tons of people were reporting issues and those people were getting chastised from other users. I personally can validate there is something wrong I experienced the same issues with mc3 and in both cases flashing back to mb1 resolved all stuttering .
[Sprint Samsung Galaxy S III] g_money:
Omar, thanks. Yea, I don't remember updating it, but I very well could have without thinking. I flashed freeza's md4 stock rom. Like I said, don't use S Voice, so was kinda surprised when I found it was broken...
[Sprint Samsung Galaxy S III] flastnoles11:
Prefect example of every phone behaves different... while you may have problems there are many others that don't ;)
[Sprint Samsung Galaxy S III] tinpaul:
Noobe question, how can I flash back to previous rom without losing data. MB1
[Sprint Samsung Galaxy S III] Omar04:
No, you do factory resets when something is wrong. ;):rolleyes:

BTW if you aren't full stock and you are rooted and tinker with the rom/system expect misbehavior at some point. If not nvrmd devices behave different anyways (setup/apps/setting/etc)
[Sprint Samsung Galaxy S III] cas8180:
Kind of funny that people always say wipe your phone then reflash vs trying to flash back to an older version and see if that remedies the issue. Why is it that even doing a simple dirty flash back to mb1 resolves the issue. I would challenge anyone that is having the stuttering issue grab freezas stock mb1 odex or deodex ROM and just dirty flash I bet you will see a difference
[Sprint Samsung Galaxy S III] Omar04:
Because not everyone have the same setup or mods on their devices and recommending that may cause major trouble. That's why is better to play safe and do a clean install on those cases. But people have the last word on what they want to do with their setup. (if something happen then.... Hey is your fault you told me to perform a dirty flash, I hate you) LOL :beer::D
[Sprint Samsung Galaxy S III] cas8180:
I see your point and I also see the value in a wipe and clean install. And your right people will be people. However a wipe is.a destructive trouble shooting tip. I other words you know your gonna lose your data and confog settings yes you can backup and restore and all that but ultimately that just puts the system back in the same state. In my experience just doing a dirty flash I have had high success with and I also don't lose anything. And this is about as close to a side by side comparison of ROMs as you can get without having two of the exact same devices. I think there is value in both methods but I do prefer the dirty flash method cause this allows me to run the dirty exact same setup with user data intact on a completely different ROM version and see how it behaves.
[Sprint Samsung Galaxy S III] Ragnar:
Actually you should never dirty flash when going from one rom to another. Frameworks are different and many other things can be different. All you do is make a mess of things all jumbled together. Dirty flashing an update of the same rom is ok, as long as you understand that things can go wrong and you may have to re flash clean. You may never truly experience the essence of a rom if you have dirty flashed over a different rom. All user data and set ups can be backed up and restored from one rom to another. Just don't restore system apps or data.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] cas8180:
I disagree
[Sprint Samsung Galaxy S III] flastnoles11:
You can disagree, that's your prerogative, but he is absolutely right
[Sprint Samsung Galaxy S III] Ragnar:
The beauty of Android :thumbup::D:thumbup:

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] cas8180:
That is your opinion I am a professional software architect for a living and can go into great lengths of the technical details of what could and what could not go wrong. There is a possibility of corruption but only a possibility a data wipe is a Guarantee of data loss. Period.
[Sprint Samsung Galaxy S III] rocket321:
To anyone playing swiping games (temple run, subway surf, etc) I would suggest if you run under md4 vs CM10 you will see md4 has stuttering / input lag. Maybe you just never noticed before because you hadn't run an AOSP rom.

Problem is I actually like touchwiz..

Clearing data isn't the issue, I mentioned this has been consistent in all tw roms, but noticibly worse under MD4.

I can't speak for ICS roms as my phone shipped with LJ7.
[Sprint Samsung Galaxy S III] CNexus:
This is mainly due to the fact that AOSP roms are much less resource intensive than proprietary roms (Touchwiz, Sense, etc). And its understandable that you would experience this the most on MD4 because of the Multiwindow service and other goodies running in the background, ready to be used at a moments notice.

You want to pull out professions, ok, I can go there too. I work in a company as one of the top Java developers.

When you dirty flash ROMs, the apks and files that are already there are depending on and expecting certain other files. Android is an OS, not an artificial intelligence system. It wont know that those exact files are no longer there and will continue to reference them. In turn, the files that replace the originals lack the necessary definitions and methods that the OS is still expecting. Hence FCs and freezing issues that will occur the majority of the time when you dirty flash a rom.

But as stated above, you are free to have your own opinion. But do not misguide others by stating that dirty flashing is a safe and viable practice.

I agree with poit 100%. The changes with which apps are running at what times dont necessarily need to be written into the kernel, either.
[Sprint Samsung Galaxy S III] jhill110:
Take it easy guyz.

I have yet to do more than wipe cache and dalvik cache (dirty flash) when flashing updates. I've used TB to freeze virtually all samsung bloatware since ICS. The issues many are having I just don't see with my device.

Also my phone (minus bloatware) consistently benchmarks much higher without all the Samsung junk than other GS3's do.

Luv this phone!

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] rotorrocket:
Still waiting on the OTA... Ugh!
[Sprint Samsung Galaxy S III] jhill110:
Have you tried the google.services.framework method?

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] rotorrocket:
From what I've read at the beginning of the thread, it can cause unexpected issues.... :eek:
[Sprint Samsung Galaxy S III] FLBoy1991:
U can use the mb1 stock reset zip pm me if u need it

---------- Post added at 01:47 PM ---------- Previous post was at 01:40 PM ----------

Ditto bro :banghead::thumbdown::confused::mad:

---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------

True but all u have to do is re-sign into Google
[Sprint Samsung Galaxy S III] CapsLockKey:
My son's S3 got the update today, but mine hasn't. Noticed you can now add numbers to the call reject list from the call log now by long pressing the entry.
[Sprint Samsung Galaxy S III] colonel.shepard:
now for 4.2 lol
[Sprint Samsung Galaxy S III] Exit_Only:
I updated manually via stock recovery. Got tired of waiting :P
[Sprint Samsung Galaxy S III] tinpaul:
Can anyone check the Sprint zone app and check device, after manual update, it states that there's a Google update, after clicking it, it takes me to update my rom even tho the rom is already been updated.

Can anyone verify this.
[Sprint Samsung Galaxy S III] Omar04:
Yes noticed that.

Edited

It reappeared. :what:
[Sprint Samsung Galaxy S III] tinpaul:
Just got the ota and checked again and yes it even does it after an update via OTA
[Sprint Samsung Galaxy S III] w8setter:
Fyi if you are trying to swipe contact to call on md4, you no longer start the swipe on the contact picture, you start the swipe right beside the pic and it works flawlessly, as I have become accustomed to using this feature alot!...Don't know why they changed this...
[Sprint Samsung Galaxy S III] metalfan78:
You're right, I've been trying to swipe from the picture. Thanks for the tip.
[Sprint Samsung Galaxy S III] Whiplashh:
Maybe there was another bug to where you clicked on the picture and it registered as a swipe. ?

------------------------

Sprint Galaxy S3

Whiplashh Rom

Look it up. :trooper: