Database Users

S Health - Step Counting

Has anybody else noticed that when using S Health to count your steps taken...it will randomly reduce the number of steps? I will be up to 4000 steps for example and then I can look back a while later and be at like 3400. Does it have some sort of formula to clean up steps that it thinks were not real steps after a certain point?

WeatherTech said:
Has anybody else noticed that when using S Health to count your steps taken...it will randomly reduce the number of steps? I will be up to 4000 steps for example and then I can look back a while later and be at like 3400. Does it have some sort of formula to clean up steps that it thinks were not real steps after a certain point?
Click to expand...
Click to collapse
Hmmm, I haven't had that issue, it doesn't reset for me. Did it just start happening or has been happening since you started using it?
Sent from my SPH-L710 using xda app-developers app

Happened to me. I just switched to accupedo.
Sent from my SPH-L720 using Tapatalk 2

me too!
I also noticed this. very frustrating - I went for a walk during lunch and had some few thousand steps , then later in the day it was like400 ! what? I keep it in my pocket all the time so of course never saw when/how it happened. glad to hear I'm not the only one, and will be curious to hear more about this.
thx.

WeatherTech said:
Has anybody else noticed that when using S Health to count your steps taken...it will randomly reduce the number of steps? I will be up to 4000 steps for example and then I can look back a while later and be at like 3400. Does it have some sort of formula to clean up steps that it thinks were not real steps after a certain point?
Click to expand...
Click to collapse
I have the opposite problem where it jumps up
Sent from my SPH-L720 using xda app-developers app

You aren't walking backwards perchance? Like an older car's odometer?

This has happened to me when I walked 10,000 steps it dropped down to 3500! :|

John.E.Boi said:
You aren't walking backwards perchance? Like an older car's odometer?
Click to expand...
Click to collapse
Lulz
Sent from my SPH-L720 using Tapatalk 2

Clarification
To clarify - I have noticed that it resets to zero if you reboot your phone. Sometimes though it will randomly drop by a few hundred - I had assumed it was to eliminate what it perceived as fake steps but who knows - glad to see it is not only me. No issues with the other parts of the app, though.

Did you get the newest OTA update? I was having this happen as well. The newest OTA update is supposed to include a new version of S Health. I just updated last night so I'm not really sure if it fixed it yet or not.

onehitch said:
Did you get the newest OTA update? I was having this happen as well. The newest OTA update is supposed to include a new version of S Health. I just updated last night so I'm not really sure if it fixed it yet or not.
Click to expand...
Click to collapse
I will see if that works - will wait until tonight to update, though - don't want to lose the steps that I've already walked today
Thanks!

onehitch said:
Did you get the newest OTA update? I was having this happen as well. The newest OTA update is supposed to include a new version of S Health. I just updated last night so I'm not really sure if it fixed it yet or not.
Click to expand...
Click to collapse
I haven't noticed any issues since the OTA.
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 05:04 PM ---------- Previous post was at 05:04 PM ----------
WeatherTech said:
To clarify - I have noticed that it resets to zero if you reboot your phone. Sometimes though it will randomly drop by a few hundred - I had assumed it was to eliminate what it perceived as fake steps but who knows - glad to see it is not only me. No issues with the other parts of the app, though.
Click to expand...
Click to collapse
Doesn't happen to me. I am on the newest OTA though
Sent from my SPH-L720 using xda app-developers app

I'm also having the same issue.

Facebook News Feed Issues?

Been having some strange issues lately with Facebook on my N4. Over wifi it operates like normal, refreshing my feed quickly and normally. But over Straight Talk T-Mobile it refuses to update 95% of the time despite 4 bars of HSPA+ For comparison, Instragram updates immediately and numerous Speedtests show my normal 5-15mb/s.
Tried wiping the cache and uninstalling to no avail. Anyone having issues? This just started about a week ago.
Running latest PA and latest Franco nightly.
Sent from my Nexus 4 using xda app-developers app

zeeebs said:
Been having some strange issues lately with Facebook on my N4. Over wifi it operates like normal, refreshing my feed quickly and normally. But over Straight Talk T-Mobile it refuses to update 95% of the time despite 4 bars of HSPA+ For comparison, Instragram updates immediately and numerous Speedtests show my normal 5-15mb/s.
Tried wiping the cache and uninstalling to no avail. Anyone having issues? This just started about a week ago.
Running latest PA and latest Franco nightly.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What radio? Probably unrelated but I had similar facebook issues on the .33 radio over LTE. Downgraded to .27 radio and it fixed my loading issues.

zeeebs said:
Been having some strange issues lately with Facebook on my N4. Over wifi it operates like normal, refreshing my feed quickly and normally. But over Straight Talk T-Mobile it refuses to update 95% of the time despite 4 bars of HSPA+ For comparison, Instragram updates immediately and numerous Speedtests show my normal 5-15mb/s.
Tried wiping the cache and uninstalling to no avail. Anyone having issues? This just started about a week ago.
Running latest PA and latest Franco nightly.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Im having the same issue

Yea I've been having to Facebook over chrome cause the app won't refresh my stuff most of the time it's like the app won't use my 4g or something trippy stuff
Sent from my Nexus 4 using xda app-developers app

Any chance you've exceeded your Data Cap for StraightTalk, from what I've seen straighttalk isn't exactly the most reliable for data usage.
---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------
By the way when you say update, are you talking bout with the screen off, or when you're actually in the app forcing it to update?

For me it's when I'm in the app trying to update it and I know im not outta data so I'm thinking it's the app
Sent from my Nexus 4 using xda app-developers app

icecicle said:
For me it's when I'm in the app trying to update it and I know im not outta data so I'm thinking it's the app
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Course at the same time I never considered Facebook to be all that reliable on the mobile side, so if all the other apps are working fine and it's just facebook that's crapping out it seems to re-enforce my feeling about their app. (I mean it even crashes on iOS every so often).

T-Mobile Straight Talk really doesn't have a data limit. Or I've never gotten close to it. As I said Facebook is the only app that does this. And even then 1 time out of 10 it'll update like normal.
I'm thinking this is some bug with the latest Facebook update. If anyone has any other thoughts for fixes let me know!

zeeebs said:
T-Mobile Straight Talk really doesn't have a data limit. Or I've never gotten close to it. As I said Facebook is the only app that does this. And even then 1 time out of 10 it'll update like normal.
I'm thinking this is some bug with the latest Facebook update. If anyone has any other thoughts for fixes let me know!
Click to expand...
Click to collapse
Its the latest update. See the comments on playstoere. Also wife has note 2 and hers is acting up.
Sent from my Nexus 4 using xda app-developers app

Facebook app is weird

+1 on this issue. Actually +2, since my wife has the same problem.
Sent from an N4 blessed with AOKP and sanctified by Faux123!

Same here with me and my wife. The only way I can get fb to load is to close all running apps via the multitask button then reopen and it goes.
Sent from my Nexus 4 using Tapatalk 2

Same issue here on the Facebook app, I've tried opening and closing it a few times and eventually it will refresh.

I believe it's definitely something on straight talks end because if you try to request the desktop site of facebook in chrome, it doesn't load either. I also am having this same issue.

Just a follow up, fixed using common sense. (shocking really)
Downgrading to 3.2 works like a charm. Can't post a link but look for the V3.2 APK on Android Drawer.

Lock screen and Knock On Solution

Strangely, my phone stopped responding to knock on to wake the screen. When you pressed the hardware power button to wake the screen would immediately close. It would take about 10-15 tries to unlock the screen in that split second before it closed. To troubleshoot I flashed back to factory and I still had the same issue after the phone was allowed to sleep just a few minutes. I took the OTA, same problem.
I was ready to box it up and swap out, but decided to try one other thing. I went to the screen off effect and changed it to Simple. Everything worked fine after that. I switched it back to retro tv and it would take many more tries to wake the screen. apparently its some kind of software bug. Thought I'd pass the info on to anyone else having similar issues.
Apparently root apps that play with system files trigger the bug too, like greenify. So the bug isn't tied to one screen effect, just switching to another fixes it until you play with system files via flashing or root apps. Hopefully it's something they fix in the next update.

It seems if you flash or change any system files, it reverts back to the retro tv effect and the issue repeats until change to another transition.

So the knock on feature is supposed to be more reliable if I do this?

in_dmand said:
So the knock on feature is supposed to be more reliable if I do this?
Click to expand...
Click to collapse
If you are suffering from the same software bug, it works. If you flash a mod or do anything that does a "updating android" on reboot, it reverts back to the default screen effect and the knock on becomes unreliable. After a deep sleep you can't wake it with a knock most of the time. Strange but saved me a trip verizon hell for a swap.

Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!

in_dmand said:
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
Click to expand...
Click to collapse
Glad it helped man. I restored my recovery,reflashed stock and took the ota before i found the bug. lol Works as advertised now.

Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app

dpaul01 said:
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Make sure the sensor area to the right of the FF camera is clean. If you have a screen protector over it, you might want to pull it off and clean the area really good. If that sensor is blocked or not working, it will do the same thing whether or not you change the screen off settings. Could be a bad sensor and you may need to swap it out.

Tried cleaning it, no luck. Seems like its hw related. Off to vzw I go.
Sent from my GT-N5110 using xda app-developers app

Can confirm this. Disabling retro worked originally, but after rooting and Greenify it's back.
Do I have to flash to stock to fix now? Or will Greenify uninstall do the trick?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 08:28 AM ---------- Previous post was at 08:10 AM ----------
Well, I tested it myself. Uninstalling Greenify does indeed fix the knock-on issue.
A shame, as I really liked that app. Boo Verizon/LG. Boo.....

Damn! I was wrong.
Still having this bug, but only from deep sleep.
Incredibly annoying, but I really don't want to Re flash. Any ideas.
I'm dying here....
Sent from my VS980 4G using XDA Premium 4 mobile app

Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app

Flashed back to stock myself and the problem continued. I returned the phone for a new one yesterday (14 days) and for the moment I'm going to keep this one stock until the issue fleshes itself out.
Sent from my GT-N5110 using xda app-developers app

timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing seems to fully resolve this. Super annoyed I ever installed Greenify. Ugh.
I'm within my 14 days (I got it on Monday), but I purchased from letstalk (the $26 price mistake deal that lasted a few minutes). Does anybody know if I can just walk into Verizon to switch it out, or do I have to do the mail back, wait 5 days with no phone thing?
thanks

I've only replaced the phones I directly received from Verizon in person. Call Verizon and tell them you needed to swap a phone under the 14 days. They can look at your account and tell you if you can just swap it in person or if you need to return through the reseller.
Sent from my VS980 4G using XDA Premium 4 mobile app

I've used greenify for two weeks without this issue ever happening.. maybe I'll freeze it now lol
Sent from my VS980 4G using Tapatalk 4

Maybe it was when we removed the Chinese SU. Secret payload to punish us. Lol
Sent from my VS980 4G using XDA Premium 4 mobile app

wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4

timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In theory, Greenify may break such a feature like Knock-on, but its always recoverable. Simply de-greenify the app and manually launch it to restore everything to normal.
Please avoid greenifying any app with background functionality.
PS: Greenify actually never touch any system files.

jayochs said:
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
No, that was just humor.

How to fix wake up lag

If you are annoyed at the 2+ second wake up lag with the note 3, you can fix it by removing the sd card from the device. sounds weird but it works.

Or you could just disable media scanner.
Sent from my Galaxy Note 3, using XDA Premium 4.

I don't have an SD card installed and see the lag.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

PeartFan40 said:
Or you could just disable media scanner.
Sent from my Galaxy Note 3, using XDA Premium 4.
Click to expand...
Click to collapse
how

This lag sucks! Is there anything else i can do to fix this?
Sent from my SAMSUNG-SM-N900A using Tapatalk

I've used Rescan Media on other phones to keep the phone from scanning the SD card on every boot. I don't know if it'll work on the Note 3, but the phone is fast enough that I don't mind the 2 second lag. (The shortest lag I ever ran into that cost a life was well over 10 seconds. If takes me 2 seconds more to call 911, I don't think anyone's going to die.)

So every time you wake the device it takes 2s? Did it do this out of the box? I doubt it; so I'd suspect it's an app issue, or you've installed a bunch of wonky xposed modules or something.

My phone is stock for the most part. Haven't rooted the phone (killing me btw) but i did install your normal apps.
It lags from time to time and it does bother me. It shouldn't lag like that.
Sent from my SAMSUNG-SM-N900A using Tapatalk

I unchecked Wake Up Command option in Lock screen settings and lag actually disappeared and hasn't come back.
Sent from my SAMSUNG-SM-N900A using Tapatalk

wally3614 said:
I unchecked Wake Up Command option in Lock screen settings and lag actually disappeared and hasn't come back.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Have that turned off as well. Can't be that
This same thing existed on the note 2. It was always said that it was due to the exynos going into such a deep sleep that it took a second or 2 to gather itself and wake up so to say. Someone made an app that would keep a constant wake lock so it wouldn't sleep. Obviously you can guess the side effects but it did work.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Mine is set to off and I still get lag.
I want to fix it because it drives me nuts
Sent from my SAMSUNG-SM-N900A using Tapatalk

So, is it possible that it is the button lagging?
I notice a little lag when trying to wake my phone but I also notice lag elsewhere. After the home button is pressed there is a small delay before getting to your launcher. The menu button also has a delay when opening the menu (wallpaper, manage apps etc) on launcher.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

wudien said:
So, is it possible that it is the button lagging?
I notice a little lag when trying to wake my phone but I also notice lag elsewhere. After the home button is pressed there is a small delay before getting to your launcher. The menu button also has a delay when opening the menu (wallpaper, manage apps etc) on launcher.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
On the home button lag do you have s voice activation on via double press of the home button still? If so turn it off, if not.... I got nothing.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Now it lags when trying to end a call. I tried what I can but not sure what else i can do. I would like to resolve this
I call Att and they put me in touch with samsugn support she suggested sending it to them for them to check it out but i would be without a phone for a week or so.
Not sure
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 08:32 PM ---------- Previous post was at 07:51 PM ----------
Ok, not 100÷ yet but thanks to someone else i may have found a solution.
He suggested that the problem comes from the sd card you use. He stated that he removed his old card and got a sandisk and it fixed the issue for him
I had my old pny 32gb card in but it has been giving me problems for a while. The note 3 was not reading it ( was at 1st)
So i took the card out and so far the lag is gone. Both on the lock screen and end call
Ill keep testing but so far there is a change. Weird.
I'm going to pick up a new card(have too) so lets see
Sent from my SAMSUNG-SM-N900A using Tapatalk

Mayonesa said:
Now it lags when trying to end a call. I tried what I can but not sure what else i can do. I would like to resolve this
I call Att and they put me in touch with samsugn support she suggested sending it to them for them to check it out but i would be without a phone for a week or so.
Not sure
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 08:32 PM ---------- Previous post was at 07:51 PM ----------
Ok, not 100÷ yet but thanks to someone else i may have found a solution.
He suggested that the problem comes from the sd card you use. He stated that he removed his old card and got a sandisk and it fixed the issue for him
I had my old pny 32gb card in but it has been giving me problems for a while. The note 3 was not reading it ( was at 1st)
So i took the card out and so far the lag is gone. Both on the lock screen and end call
Ill keep testing but so far there is a change. Weird.
I'm going to pick up a new card(have too) so lets see
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
No SD card here and it lags. Can't be it. That might help if using an SD card but not a full solution as there's last without one as well.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Well it has helped me. Since i took out my sd my phone hasn't lagged like before.
Even though it is the same phone each make act different. As an example, the guy got a SanDisk card and he was fine. May not work for my phone. So far removing the card helped me.
Shouldn't be like this. Our phones should all work perfectly but that is not the case. With this phone and others i have had in the past.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Still no lag and battery seems to be better as well, unlike before
Unplugged at 0900 and its now 1400 and im at 92÷ with normal use. Calls etc.
I just hope then the new sd card i get works well
Sent from my SAMSUNG-SM-N900A using Tapatalk

I get no lag with my att note 3 with the no SD card. Wakes instantly. Stock
Sent from my SAMSUNG-SM-N900A using Tapatalk

Must be an issue with the earlier release models. I got mine less than a month ago and has a 32GB PNY card and no issues whatsoever. In fact it has NONE OF THE ISSUES stated in any of the threads on this site. If I press the wake button, bam! there it is. So this must be an issue for you early buyers.

I got my note 3 about 3 weeks ago. Dont know what model it is because i haven't looked.
My previous sd was given me problems before, had to reformat it twice and when I took it out it wasn't working. So maybe that was the issue.
I have a SanDisk card coming so lets see how that goes.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Sprint S7 & S7 Edge Nougat 7.0 beta program is Open

Hurry up before they close sign ups.
If you don't know how to register, simply download the Samsung beta program from the galaxy apps store (not play store) and then follow the prompts.
I hope you guys find this helpful

Finally!

FYI-You have to wipe data or get constant reboots
Sent from my SM-G935P using XDA-Developers mobile app

aburns7487 said:
FYI-You have to wipe data or get constant reboots
Click to expand...
Click to collapse
Mine works fine without the wipe.

I was just sharing my experience as I just got the phone the day before. I had the phone all set up it was working fine on Android 6.0.1. I upgraded to the beta for nougat Android 7.0 and immediately my phone kept rebooting every 30 seconds or little bit longer. Once I realized the data I have not had any issues at all.
Sent from my SM-G935P using Tapatalk
---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------
I previously had the Note 7
Sent from my SM-G935P using Tapatalk

I had massive restart loop every 30 seconds yesterday. Have been troubleshooting. Ultimately had to rewipe again, to get it to work.
Sent from my SM-G935P using Tapatalk

I downloaded the app this afternoon, did the registration, went into my setting and checked for an update and it downloaded nougat. The one thing I have found is that Bluetooth sucks! Seriously my music breaks up with it just in my pocket and I'm wearing Bluetooth headphones. Then I took it out of my pocket and put it on the counter and I can't get 5 feet away from the phone and the music breaks up again. Prior to the update I could go to the gym, put my phone down and be a good 40 feet away and it would still work fine.
Sent from my SM-G935P using XDA-Developers mobile app

Is there a way to keep the phone's screen from coming on when a text message comes in?
Sent from my SM-G935P using XDA-Developers mobile app

Thanks to this thread I installed the beta Nougat OS.
Nothing bad so far. I did NOT wipe or remove data.
So far, I really like it. The SoTP meter says it's faster. Only thing that doesn't work so far is my Agenda Widget. Love the improved AOD. Battery seems to last a little longer, but not enough experience to say definitively. I did notice that the phone was warm when at 100% this morning. Haven't seen that since the update that stopped us charging to 100% (even though the display said it was).
The options in Settings are better- much better control of notifications.
I'll post more as I discover it.

Is anybody having the issue where the speaker volume is really quiet? Like unusable when watching YouTube.
Sent from my SM-G935P using Tapatalk

sgtmedeiros said:
Is anybody having the issue where the speaker volume is really quiet? Like unusable when watching YouTube.
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
I just pulled up a random video on YouTube. Sound is working fine.

Is the registration still open?

DubSolo said:
Is the registration still open?
Click to expand...
Click to collapse
i registered but im afraid to lose my hotspot. i here they fixed the "turn it on after reboot" thing. im still on OG firmware and get 2 and 1/2 days battery life so can someone confirm hotspot still works if turned on real quick after reboot?
being on the OG firmware I can still set my apns. Thanks

Robalboa said:
i registered but im afraid to lose my hotspot. i here they fixed the "turn it on after reboot" thing. im still on OG firmware and get 2 and 1/2 days battery life so can someone confirm hotspot still works if turned on real quick after reboot?
being on the OG firmware I can still set my apns. Thanks
Click to expand...
Click to collapse
I was trying to run the Sprint software on my g935a but that damn annoying Sprint activations wouldn't allow me to get anywhere. Want Nougat bad and Verizon stopped at beta 2...booo

DubSolo said:
I was trying to run the Sprint software on my g935a but that damn annoying Sprint activations wouldn't allow me to get anywhere. Want Nougat bad and Verizon stopped at beta 2...booo
Click to expand...
Click to collapse
Nougat is closed again
Sent from my SM-G935P using XDA Free mobile app

The Beta Program is over today.
https://www.sammobile.com/2016/12/3...ogram-ends-today-official-release-in-january/

Goat1378 said:
The Beta Program is over today.
https://www.sammobile.com/2016/12/3...ogram-ends-today-official-release-in-january/
Click to expand...
Click to collapse
So it releases in January. Just a few days awayyy
Sent from my SM-G935P using XDA Free mobile app

Son Rise said:
So it releases in January. Just a few days awayyy
Sent from my SM-G935P using XDA Free mobile app
Click to expand...
Click to collapse
Lol if only! Thats when Sammy will release it to the carriers. And then they will do their thing and probably take their time draging feet.

Goat1378 said:
Lol if only! Thats when Sammy will release it to the carriers. And then they will do their thing and probably take their time draging feet.
Click to expand...
Click to collapse
Sprint users were part of the beta too, so it shouldn't be like rollouts in the past. Although I don't understand why we've been testing 7.0 and the final is supposed to be 7.1.1, unless Sprint stays on 7.0.

Ramer said:
Sprint users were part of the beta too, so it shouldn't be like rollouts in the past. Although I don't understand why we've been testing 7.0 and the final is supposed to be 7.1.1, unless Sprint stays on 7.0.
Click to expand...
Click to collapse
If sammy sends them 7.1.1 them that's what we will get. 7.1.1 isn't that much different from 7.0 just a few features added like app menu short cuts which wouldnt take much for them to add in the final release .I really dnt get how beta is over with all bugs not fixed. I personality still have an issue with Youtube videos not working after some time. Notification tones stop working after some time. No factory reset or caches clear has fixed this in the whole beta process.