Related
Hi,
I purchased the s4 through radio shack 4 days ago. I was having issues with the wifi staying connected for more than a minute. After doing research and reading forums I came to the conclusion it was my router. I've reset it and done firmware updates and changed security to WEP and wifi issue was resolved. However now it is constantly scanning for a wifi network even though it's already connected to one. Have called samsung and radio shack sbout this and am getting various responses such as it is normal, or no it is not normal let's try a a hard reset to see if it fixes the issue. So this forum is my last resort before completely resetting the phone. Should wifi be continuously scanning even if connected to a network or not? Thanks
Valerieg8282 said:
Hi,
I purchased the s4 through radio shack 4 days ago. I was having issues with the wifi staying connected for more than a minute. After doing research and reading forums I came to the conclusion it was my router. I've reset it and done firmware updates and changed security to WEP and wifi issue was resolved. However now it is constantly scanning for a wifi network even though it's already connected to one. Have called samsung and radio shack sbout this and am getting various responses such as it is normal, or no it is not normal let's try a a hard reset to see if it fixes the issue. So this forum is my last resort before completely resetting the phone. Should wifi be continuously scanning even if connected to a network or not? Thanks
Click to expand...
Click to collapse
Mine still scans for Wifi about every 4-5 seconds even when connected to Wifi. It seems to be normal and believe it did this on my S3 as well. Unless it is draining your battery I wouldn't worry about it. Also, it may only do it when you are in the Wifi settings and not when you exit but who knows. I get great battery life so it is something I'm not going to worry about.
CCallahan said:
Mine still scans for Wifi about every 4-5 seconds even when connected to Wifi. It seems to be normal and believe it did this on my S3 as well. Unless it is draining your battery I wouldn't worry about it. Also, it may only do it when you are in the Wifi settings and not when you exit but who knows. I get great battery life so it is something I'm not going to worry about.
Click to expand...
Click to collapse
h
have you asked if it Is normal? Im pretty sure the scanning is affecting my battery life but but not
sure how to check whether it is or isn't. Just dont want to find out months down the road that I have a defective device. Will resetting it fix the?
Valerieg8282 said:
h
have you asked if it Is normal? Im pretty sure the scanning is affecting my battery life but but not
sure how to check whether it is or isn't. Just dont want to find out months down the road that I have a defective device. Will resetting it fix the?
Click to expand...
Click to collapse
I have not asked because my battery life doesn't seem to be affected by it. Also, I think my S3 did it also. From what I find when doing an internet search everyone else is seeing the same thing so almost positive it is made this way. When I look at the breakdown of battery usage (Settings->More->Battery) Wifi is only using 6% of my battery. Look and see what is using battery on yours. If you need more detailed information on what is using the battery than get BetterBatteryStats from Play store to help pinpoint it. There is a forum just for it where you can post and get help figuring it out if need be.
Also, as for resetting, I just did a factory reset yesterday and it still scans when in the Wifi settings.
The scan interval is probably cooked into the build.prop somewhere by Samsung. Usually apps like Blade Buddy and Rom Toolbox Pro can change it but BB is not compatible yet with the S4 and Rom Toolbox doesn't show the scan option in the build.prop list. I looked at a few of the custom TW roms and not finding any changes to that listed in any build.prop tweaks.
If I had to guess would say there is something else on your device using the battery but using BetterBatteryStats can pin point it for you.
**Edit....From what I am reading it seems there is nothing in the build.prop to edit. A line needs to be added in to change the default scan interval. I'm not 100% positive on this but seems to be the case.
CCallahan said:
I have not asked because my battery life doesn't seem to be affected by it. Also, I think my S3 did it also. From what I find when doing an internet search everyone else is seeing the same thing so almost positive it is made this way. When I look at the breakdown of battery usage (Settings->More->Battery) Wifi is only using 6% of my battery. Look and see what is using battery on yours. If you need more detailed information on what is using the battery than get BetterBatteryStats from Play store to help pinpoint it. There is a forum just for it where you can post and get help figuring it out if need be.
Also, as for resetting, I just did a factory reset yesterday and it still scans when in the Wifi settings.
The scan interval is probably cooked into the build.prop somewhere by Samsung. Usually apps like Blade Buddy and Rom Toolbox Pro can change it but BB is not compatible yet with the S4 and Rom Toolbox doesn't show the scan option in the build.prop list. I looked at a few of the custom TW roms and not finding any changes to that listed in any build.prop tweaks.
If I had to guess would say there is something else on your device using the battery but using BetterBatteryStats can pin point it for you.
**Edit....From what I am reading it seems there is nothing in the build.prop to edit. A line needs to be added in to change the default scan interval. I'm not 100% positive on this but seems to be the case.
Click to expand...
Click to collapse
OK I've looked at battery usage and and wifi is at b 4% and screen has the highest percentage eventhough I have it at a lower resolution. However when I click on wifi from the battery setting it says it has only been connected to Wifi for 4hrs. 32 minutes . I've had wifi turned on since I got home last night. Could that be the issue? I did charge the phone overnight unless it shuts off while charging but still my emails would have to sync every hour. Do you know why it would say it's only been connected for 4 hrs if I've been home much longer than tgst? Thanks for the help. And also did you reset your phone due to the wifi scanning?
THANK YOU
Valerieg8282 said:
OK I've looked at battery usage and and wifi is at b 4% and screen has the highest percentage eventhough I have it at a lower resolution. However when I click on wifi from the battery setting it says it has only been connected to Wifi for 4hrs. 32 minutes . I've had wifi turned on since I got home last night. Could that be the issue? I did charge the phone overnight unless it shuts off while charging but still my emails would have to sync every hour. Do you know why it would say it's only been connected for 4 hrs if I've been home much longer than tgst? Thanks for the help. And also did you reset your phone due to the wifi scanning?
THANK YOU
Click to expand...
Click to collapse
I don't know about the reported length of time for WiFi. Mine seems to be accurately reporting when I connected to WiFi this morning at work till now. Maybe it disconnected and then reconnected for something? Do you have multiple bands in your home (2.4ghz & 5ghz) to where it could have jumped between them? Did you walk outside and out of range for a sec? Maybe for some reason it had a hiccup and got disconnected and reconnected. Not sure.
Also, I did a factory reset for a Play Store issue and not because of the WiFi.
Wifi scanning every 5 seconds on my Galaxy s4
Jellybean 4.3 has been responsible for one of the highest complaints to hit android since androids launch.
Wifi overscanning
Battery management
HDMI Completely not working
The list goes on, this is all because some idiots wanted to rush jellybean out to accommodate for the introduction of the Samsung Gear. As a result of rushing it's release many elements were not tested or even included in the update of our much loved now screwed galaxy s4 's
Someone better get there act together and roll out a TESTED release to address all of these screw ups!
puniksem said:
Jellybean 4.3 has been responsible for one of the highest complaints to hit android since androids launch.
Wifi overscanning
Battery management
HDMI Completely not working
The list goes on, this is all because some idiots wanted to rush jellybean out to accommodate for the introduction of the Samsung Gear. As a result of rushing it's release many elements were not tested or even included in the update of our much loved now screwed galaxy s4 's
Someone better get there act together and roll out a TESTED release to address all of these screw ups!
Click to expand...
Click to collapse
When this post was made 7 months ago, the S4 was on 4.2.2 not 4.3. Way to revive an old invalid thread. Also, all the things you mentioned work great on my phone so calm down a little.
cruise350 said:
When this post was made 7 months ago, the S4 was on 4.2.2 not 4.3. Way to revive an old invalid thread. Also, all the things you mentioned work great on my phone so calm down a little.
Click to expand...
Click to collapse
That's funny because as a senior member, your reply seemed neither helpful nor relevant to what I said about the Galaxy S4 being affected by the latest Jellybean 4.3 update (whether I posted on an outdated thread or not) The subject matter remains relevant because the Wi-fi over-scanning while connected is still very much a current issue.
Many users have complained about the numerous errors currently being recently experienced in the latest 4.3 update, many of which have now been announced on the Samsung support forums. I'm in the UK and I see you're in the US. that in itself could make a hell of allot of difference in the errors that UK users may be experiencing. I'm also on T-Mobile and that could also have implications to the version of Jellybean subversion that has been installed.
Telling me I should 'calm down' (just because you're not experiencing any issues with your phone) is not the sort of condescending remark expected from any senior member.
puniksem said:
That's funny because as a senior member, your reply seemed neither helpful nor relevant to what I said about the Galaxy S4 being affected by the latest Jellybean 4.3 update (whether I posted on an outdated thread or not) The subject matter remains relevant because the Wi-fi over-scanning while connected is still very much a current issue.
Many users have complained about the numerous errors currently being recently experienced in the latest 4.3 update, many of which have now been announced on the Samsung support forums. I'm in the UK and I see you're in the US. that in itself could make a hell of allot of difference in the errors that UK users may be experiencing. I'm also on T-Mobile and that could also have implications to the version of Jellybean subversion that has been installed.
Telling me I should 'calm down' (just because you're not experiencing any issues with your phone) is not the sort of condescending remark expected from any senior member.
Click to expand...
Click to collapse
Well, seems you don't have the l720 so why are you paying in these forums.
Sent from my SPH-L720 using Tapatalk
I am running a Note 3 bought in Sweden around the 11th of December, fully stock. Never rooted or anything. I was actually too stupid to update myself to MJ7 right when i bought it before finding out about the KNOX-debacle, but nevermind about that. What is done is done!
Batterylife has so far been alright since I bought the phone. I've managed to get around 7 hours of screen-on time in the exact same environment as these pictures have been taken in without enabling any power saving modes or going to extremes with turning off location services etc. I was very happy.
Yet lately I've been seeing that my battery life has started to get worse. I've noticed it mostly when the phone has been idle. This led me to experiment today. I've experienced the Android OS bug earlier, which caused me to factory reset the phone and start again. It disappeared for a while, but it has come back now.
The reason I am making this thread is that I cannot for the life of me figure out what inside Android OS is wakelocking my phone. I have a lot of pictures detailing my battery stats screen, with screen on times, signal strengths, location settings, google now settings, better battery stats kernel/partial wakelocks/other tabs etc. Even "Wakelock Detector" with all of its tabs are screencapped.
The wakelock times within better battery stats just do not add up to the "Android OS" wakelock time. Is there something I am not seeing, or is it maybe because I am not rooted that I cannot see more detailed info about what is wakelocking my phone? The only thing i've done today which I know wakelocks my phone, is listen to music for about 2 hours. Surely music does not count into Android OS? It is listed as another process in the battery stats..
Anyhow, if anyone has time to take a look at my screencaps to try and pinpoint what it is exactly that adds up to the "Android OS" time, I would be very greatful. This is very frustrating, as I was very sure to disable almost everything that has to do with location services etc. to see how the battery would fare during the day.
Please help me!
Thanks.
i have exactly same problem like yours. my main wakelock is resume_wakelock and sec battery monitor. i dont know what cause those 2 wakelock. i had disabled all location services and turn off gps and auto sync. do u managed to overcome this problem ?
EddieN said:
I am running a Note 3 bought in Sweden around the 11th of December, fully stock. Never rooted or anything. I was actually too stupid to update myself to MJ7 right when i bought it before finding out about the KNOX-debacle, but nevermind about that. What is done is done!
Batterylife has so far been alright since I bought the phone. I've managed to get around 7 hours of screen-on time in the exact same environment as these pictures have been taken in without enabling any power saving modes or going to extremes with turning off location services etc. I was very happy.
Yet lately I've been seeing that my battery life has started to get worse. I've noticed it mostly when the phone has been idle. This led me to experiment today. I've experienced the Android OS bug earlier, which caused me to factory reset the phone and start again. It disappeared for a while, but it has come back now.
The reason I am making this thread is that I cannot for the life of me figure out what inside Android OS is wakelocking my phone. I have a lot of pictures detailing my battery stats screen, with screen on times, signal strengths, location settings, google now settings, better battery stats kernel/partial wakelocks/other tabs etc. Even "Wakelock Detector" with all of its tabs are screencapped.
The wakelock times within better battery stats just do not add up to the "Android OS" wakelock time. Is there something I am not seeing, or is it maybe because I am not rooted that I cannot see more detailed info about what is wakelocking my phone? The only thing i've done today which I know wakelocks my phone, is listen to music for about 2 hours. Surely music does not count into Android OS? It is listed as another process in the battery stats..
Anyhow, if anyone has time to take a look at my screencaps to try and pinpoint what it is exactly that adds up to the "Android OS" time, I would be very greatful. This is very frustrating, as I was very sure to disable almost everything that has to do with location services etc. to see how the battery would fare during the day.
Please help me!
Thanks.
Click to expand...
Click to collapse
try and turn of (auto network switch) it might have something to do with wifi
i may be wrong ,but no harm in trying
Here the same problem, it drains my battery in half a day
installed wakelock detector, and found out, that my note 3
never goes into deep sleep, it stays awake the whole time
For me it has nothing to do with screen -on time, Wifi or any apps
the problem is is in the android kernel system, and I do not know, how to solve this problem
last statistics : CPU time 3 u 11m 24s , Awake 10 u 28m 48 s
Tried lots of "solutions" found here on this forum, but so far no good
correct me if i am wrong, but as I understood, HTC and LG are having the same kernel / rom,
but without the google "apps", and are not having these problems
Asking Samsung is no use, a concreet wall will answer you sooner, than Samsung in the Netherlands
I wished I had a solution for this android kernel problem
I will wait for the Kitkat update, and if it will solve this problem, if not I will get myself another device
wiebew said:
Here the same problem, it drains my battery in half a day
installed wakelock detector, and found out, that my note 3
never goes into deep sleep, it stays awake the whole time
For me it has nothing to do with screen -on time, Wifi or any apps
the problem is is in the android kernel system, and I do not know, how to solve this problem
last statistics : CPU time 3 u 11m 24s , Awake 10 u 28m 48 s
Tried lots of "solutions" found here on this forum, but so far no good
correct me if i am wrong, but as I understood, HTC and LG are having the same kernel / rom,
but without the google "apps", and are not having these problems
Asking Samsung is no use, a concreet wall will answer you sooner, than Samsung in the Netherlands
I wished I had a solution for this android kernel problem
I will wait for the Kitkat update, and if it will solve this problem, if not I will get myself another device
Click to expand...
Click to collapse
have u try factory reset via recovery mode ? i had read somewhere that factory reset can solve that problem but i didnt try yet
peped94 said:
have u try factory reset via recovery mode ? i had read somewhere that factory reset can solve that problem but i didnt try yet
Click to expand...
Click to collapse
Hell Pepe, Tried this already several times, wiped cache and installed stock firmware twice (MJ7)
so far ,nothing, I am very glad to get good information from this forum, and hopefully I will get/ find the solution soon
maybe the problem will be solved by rooting my device and install a custom rom, but i am a bit afraid to trip knox
wiebew said:
Hell Pepe, Tried this already several times, wiped cache and installed stock firmware twice (MJ7)
so far ,nothing, I am very glad to get good information from this forum, and hopefully I will get/ find the solution soon
maybe the problem will be solved by rooting my device and install a custom rom, but i am a bit afraid to trip knox
Click to expand...
Click to collapse
how do u flash stock firmware without tripping the knox ? i want to try. and how do u do factory reset ? in recovery mode or in setting ? because i also had try reset in setting but problem still exist. later ill try factory reset in recovery mode
peped94 said:
how do u flash stock firmware without tripping the knox ? i want to try. and how do u do factory reset ? in recovery mode or in setting ? because i also had try reset in setting but problem still exist. later ill try factory reset in recovery mode
Click to expand...
Click to collapse
you tube has a lot of videos how to perform a factory reset or how to install stock firmware
T-mobile has a nice manual also http://support.t-mobile.com/docs/DOC-9049
when re-installing the (original samsung ) stock firmware , knox will not be tripped.
I even switched from T-mobile MJ6 to provider free firmware MJ7, without any problems,
hopefully MJ7 will get Kitkat sooner, than MJ6
peped94 said:
how do u flash stock firmware without tripping the knox ? i want to try. and how do u do factory reset ? in recovery mode or in setting ? because i also had try reset in setting but problem still exist. later ill try factory reset in recovery mode
Click to expand...
Click to collapse
download stock from here www.sammobile.com flash with odin
it wont trip knox
jaythenut said:
download stock from here www.sammobile.com flash with odin
it wont trip knox
Click to expand...
Click to collapse
now im on mj7, if i want to downgrade to mj1 , it will trip my knox or not ?
peped94 said:
now im on mj7, if i want to downgrade to mj1 , it will trip my knox or not ?
Click to expand...
Click to collapse
You can't downgrade Sammy won't allow it anymore
jaythenut said:
You can't downgrade Sammy won't allow it anymore
Click to expand...
Click to collapse
damn u samsung. haha. but if i want to flash mk1 or mk2 when im on mj7, is it trip my knox ? i mean if i want to flash newer firmware than my current firmware
Upgrading won't trip KNOX no.
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
Upgrading won't trip KNOX no.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
are u sure ? because i have read that whenever we upgrade or downgrade our firmware, knox will be changed to 0x1. but im not sure if we just reflash the same stock firmware
peped94 said:
damn u samsung. haha. but if i want to flash mk1 or mk2 when im on mj7, is it trip my knox ? i mean if i want to flash newer firmware than my current firmware
Click to expand...
Click to collapse
no flashing stock will not trip knox
EddieN said:
I am running a Note 3 bought in Sweden around the 11th of December, fully stock. Never rooted or anything. I was actually too stupid to update myself to MJ7 right when i bought it before finding out about the KNOX-debacle, but nevermind about that. What is done is done!
Batterylife has so far been alright since I bought the phone. I've managed to get around 7 hours of screen-on time in the exact same environment as these pictures have been taken in without enabling any power saving modes or going to extremes with turning off location services etc. I was very happy.
Yet lately I've been seeing that my battery life has started to get worse. I've noticed it mostly when the phone has been idle. This led me to experiment today. I've experienced the Android OS bug earlier, which caused me to factory reset the phone and start again. It disappeared for a while, but it has come back now.
The reason I am making this thread is that I cannot for the life of me figure out what inside Android OS is wakelocking my phone. I have a lot of pictures detailing my battery stats screen, with screen on times, signal strengths, location settings, google now settings, better battery stats kernel/partial wakelocks/other tabs etc. Even "Wakelock Detector" with all of its tabs are screencapped.
The wakelock times within better battery stats just do not add up to the "Android OS" wakelock time. Is there something I am not seeing, or is it maybe because I am not rooted that I cannot see more detailed info about what is wakelocking my phone? The only thing i've done today which I know wakelocks my phone, is listen to music for about 2 hours. Surely music does not count into Android OS? It is listed as another process in the battery stats..
Anyhow, if anyone has time to take a look at my screencaps to try and pinpoint what it is exactly that adds up to the "Android OS" time, I would be very greatful. This is very frustrating, as I was very sure to disable almost everything that has to do with location services etc. to see how the battery would fare during the day.
Please help me!
Thanks.
Click to expand...
Click to collapse
Hello EddieN,
Found this on the forum, Under Apps > Settings > Wi-Fi > Menu > Advanced there are two options that should help this: "Keep Wi-Fi on during sleep" and "Always allow scanning" I set the "Keep Wi-Fi on during sleep" to Never and unchecked Always allow scanning and rebooted the phone. This stopped my battery from draining fast, however this is not the solution where was hoping for, maybe Kitkat will solve the problem
kind regards
wiebew said:
Hello EddieN,
Found this on the forum, Under Apps > Settings > Wi-Fi > Menu > Advanced there are two options that should help this: "Keep Wi-Fi on during sleep" and "Always allow scanning" I set the "Keep Wi-Fi on during sleep" to Never and unchecked Always allow scanning and rebooted the phone. This stopped my battery from draining fast, however this is not the solution where was hoping for, maybe Kitkat will solve the problem
kind regards
Click to expand...
Click to collapse
Hello, thank you for the tip and happy new year!
I tried it, but it didn't work. Wifi is on all the time since the phone never sleeps. I just checked my phone again, and it's been on for about 4 hours. It hasn't entered deep sleep not even 1 minute out of that time. This is getting ridiculous. Screenshots from BBS are attached. As you can see, Kernel and Partial Wakelocks just don't add up to the "Awake" time.. Why is this? What is keeping my phone awake?
I'm seriously getting desperate. I'm considering just tripping knox and dealing with it properly with a custom rom/kernel combination that rids the phone of these problems. Is KitKat due this month? Or is it february? I may wait for it but something tells me it wont solve the issues we are having.
Cheers
peped94 said:
i have exactly same problem like yours. my main wakelock is resume_wakelock and sec battery monitor. i dont know what cause those 2 wakelock. i had disabled all location services and turn off gps and auto sync. do u managed to overcome this problem ?
Click to expand...
Click to collapse
me too, have you settle this problem yet?
Did you try: Settings - wifi - advanced - turn off scanning always available & auto network switch and network notification
Sent from my Nexus 7 using XDA Premium 4 mobile app
billythegod said:
me too, have you settle this problem yet?
Click to expand...
Click to collapse
yes. finally my battery life back to normal. just updated to the latest firmware in my country and do a factory reset in recovery mode. now no more drain like hell but still android os consume about 10-15% but sec battery monitor and resume wakelock no more on top in wakelock detector. i also can get about 7hours 300min screen on time with 1day standby time
Hi !
These are the problems I am facing on my Nexus 4 device and I would really appreciate if someone kindly let me know as to how I can solve these serious issues plaguing me since almost a month now. ( Nexus 4 running KitKat 4.4.4 )
1. When the phone is in the pocket and I get any notification it naturally wakes up but then supposed to go back to the Sleep Mode like in any phone normally but unfortunately, my phone stays awake and I notice this when I actually feel the phone growing uncomfortably warm in my pocket !
The screen shows multiple pages open and battery draining like anything ! ( after reading some online problems related to this I have deleted WebChat and closed the Daydream function but the problem still persists and it seems I am not the only one facing this problem . )
This has happened many times.
Further, I have no idea if this happened only after the update or not since I have never used Nexus before and besides , my phone is second hand and was already updated to this version when I had purchased.
2. At times when I am rotating my camera from lets say, Landscape to Potrait mode and visa versa to take pictures the image freezes for a heartbeat and becomes normal once again.
Acting as if memory is not enough !
Storage shows 5.75G left. Two movies and music and no games.
No anti virus app but DU Booster. ( also happened before installing the booster app. )
So far, after using this phone for almost a month I am very happy and I love the smoothness of the phone .
To me this is an Andriod version of an iPhone in terms of smoothness and reliability.
In fact, I think it is better in many ways but if these above issues are solved it would encourage me to buy a new Nexus 5 soon which I am sure is much nicer then a 4.
Thank you for your kind assistance and best regards to all.
Sammy
I assume you've performed a factory reset after having bought it used, is that right?
1. Have you set it up to turn the screen on when a notification is received? It can affect your battery life, especially if it happens to unlock on its own, which I think may be the case if you're reporting "multiple pages open and battery draining like anything"
2. It's quite normal, obviously if the switching time is not THAT annoyingly long. Mine has approximately 40% storage left and sports almost no lag within the camera app, but that fraction of a second is noticeable.
Thanks for your kind reply.
Yes, I did a factory reset.
Let me check the notification status.
With regards to camera when I twist and turn the phone - the image , instead of changing with the position actually ' thinks ', before doing it which means a blurry lag .
I clearly see this from one position to the next.
Further, what I forgot to write and ask was when the phone is in my pocket and I receive an incoming call the screen freezes and I cannot swipe it to unlock and so I have to switch off the power and turn it on and only then swipe and receive the call ! ( I used to get this on a custom ROM on Galaxy S and the Dev gave me this idea and which I apply here too ! )
Thanks again !
Sammy
Sent from my Nexus 4 using XDA Free mobile app
It took my a while, but thanks to Wugfresh I was finally able to instal 5.1 on my N6. Curious to know what the general consensus is. I've only had it up and running for 6 hours, but has anyone noticed improvement in battery life or memory management?
Thanks.
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
AstroDigital said:
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
Click to expand...
Click to collapse
Franco's kernel has given my battery some extra life, I hope this update does the same.
I have yet to get the two bugs that were really getting on my nerves previously in 5.0 and 5.0.1
1- Random restarts. They could happen at any time, but it seemed like they would happen when I was trying to text. I'd try to keep closing my text messenger application (happened with both Google Messenger and Hangouts), but it didn't always help. I'd send a text message, put my phone down and then a few seconds later, notice the Google logo because it was restarting.
2- Sometimes when the screen powers up, all I see on my lock screen is a blank black background, the on-screen back button and the usual clock and what not at the top of the phone. Otherwise, the screen itself is black and I'm basically locked out of my phone until I restarted it. If I was lucky and I was using my Bluetooth headset, if I received a phone call, that would sometimes get the phone to snap out of it and allow me to answer the phone call and then when the call was done I'd get the normal lock screen again.
So far so good with 5.1 *knocks on wood*
I just flash it this morning and I feel like im still on 5.0.1. I only use 1 wifi connection and 1 bluetooth connection, so a drop down menu doesn't really effect my daily usage since I don't switch them. Whatever they did behind the hood to improve performance/battery will be nice, but haven't had it installed long enough yet to notice anything different really.
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
5.1 is what Lollipop should have been from launch. It's equivalent to Windows 7 replacing Vista. It's that much better.
Sideloaded with adb on my stock att N6. Seems real quick so far. Don't notice any additional drain on battery.
So far it seems about the same as before to me. However, I am on Sprint and the new radio that prevents duplicate texts is awesome so that part of it makes it seem like a new device.
I play Hearthstone, Kingdom Rush and Clash of Clans on My nexus 6 and they all run fine so far.
I did un-encrypt like before. I cannot comment on battery life yet since it hasn't even been 24 hours for me since I updated.
So far so good. Battery life has certainly improved, it was pretty abysmal for me before. I only experienced one bug that I know of on 5.0.1 where occasionally my status bar and nav bar would disappear and the phone was in a partially locked state. Trying to slide down the notification drawer would show the lockscreen. Hopefully that's fixed.
is double tap to wake.. enable in 5.1??
I'm not on a N6 yet, but my GNex is on 5.1, and to compare (because I've only got 1Gb of RAM here, it's a good test because the margins are so small compared to having 3Gb) the 5.1 update is by far the most stable yet for my device. 5.0 was baaad, but consider how many commits corrected memory leaks and you can tell this is the one. I'm looking forward to getting my N6 with 5.1 on it.
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
I am noticing a huge performance improvement from 5.0.1 already. Battery life is also better. I am not having the dialer issue like some, but have seen 3 instances of people saying the same thing.
Was on stock, now on Vanillipop 1.6 with Franco Kernel r20.
Much smoother and the battery seems improved. Still testing out.
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
got a tempered glass protector on it?
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do you use a screen protector that covers the sensor? I know there is a thread somewhere around here with a lot of people that have that issue and it's because of their screen protector in 5.1 for some reason.
jakebites said:
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
Click to expand...
Click to collapse
Greatly, its butter all the time.
I haven't noticed a whole lot yet, some games seem to be playing a lot better, the graphical glitch I was seeing on xcom seems to have disappeared so its actually playable now
I've been experiencing an increase in fluidness (is that a word) throughout the UI as a whole, the phone moves from task to task without any stutter and the animations seem to have a bit more polish to them. Checking on the battery now, but I was never a power user to begin with. Overall it may not look like much but you can tell there are some big time enhancements coming from 5.0.1
I bought the s8 today from a parallel imported store. I know oreo is a major update, but for my phone it's going to take over 5 hours. My internet speeds are fine and browsing/videos are all perfectly fast on my phone - it's just this update which is slow as a snail. The pic of this is below.
https://imgur.com/a/vye3o
With my other question, I wanted to ask about a feature from the "Phone INFO samsung" app. The s8 is my first Samsung parallel imported phone, so I used the app to check if it's refurbished or not, and the app confirms it's a brand new phone thankfully. The IMEI and serial numbers all match with the box too.
I noticed however that under usage history, the battery discharge cycle number was already 2. Possibly a stupid question, but is that normal for a brand new phone? Before I installed the app, the only charging I'd done was from 44% (the % the phone came out of the box as) up to around 75%.
https://imgur.com/a/Pick8
Appreciate any answers you guys have, thanks!
**EDIT: The update might not actually be Oreo since my phone was only 7.0 before the download, the size is only 500mb - I've had someone tell me that their oreo update was 1.5gb. The issue still stands that the download is incredibly slow!
**EDIT 2:
I believe my phone was originally a Telstra carrier phone that has been unlocked, since I see the Telstra logo whenever I boot up my phone. I'm not sure if this has any relevance to the fact that when I go into Settings > Software Update, I only see the following two options:
"Download updates manually" "Scheduled software updates"
On all my friends galaxy s8's, in addition to the above settings, there is also a "Download updates automatically" and a "Last update information" section. I wonder if this has anything to do with my issue?
It is normal because every device is being charged and stressed out battery test when in production.
Also, based on your screenshot it is not OREO yet. Oreo update is 1.5GB, 500mb would just be security patches and stability update.
5 hours definitely seems odd, especially if that update is only a third of the size of the Oreo update. Oreo took about 5-10 mins to download, and then maybe 20 minutes to install on my Verizon phone.