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
Does anyone know of the best way to get serious technical attention from Google or Samsung? To put how serious this is (not to start a flame war), I will be purchasing an iPhone 5S on Monday and never another Android device unless either they solve this issue or I get another job (I LOVE my job, so unlikely).
If you search Android Wifi Constantly Downloading, you will find results from people who have this issue. Some people say its sync, some its apps updating, but it is not. It is a bug with the Android kernel in how it doesn't filter multicast packets, resulting in the system staying awake and receiving packets most of the time. Some people have been able to solve it by purchasing a new router or turning off multicast on computers, but this is not an option in an enterprise location like a hospital. I have been stuck with this issue since I got my Note 2 last year.
The Note 3 exacerbates this problem even more because the processor low power states are not as efficient as the Note 2's. On the Note 3 I lose 12-15% per hour idle, on Airplane Mode with Wifi on. I did a test on my Note 2 and in 1 day and 7 hours of complete idle, radios off, and wifi on the battery drained fully.
Normally I carry my phone and a 9000mAH external battery. It takes the entire phone's battery and 80% of the external to get through a normal day. Last week, with the major ice storm, power was out for days and I was stuck at work. Generators provided only power to essential services, so my phone was dead days before the power was back. I do have UL data but Verizon's signal does not penetrate at all. I am tired of worrying about battery and if something like this happens again, I will be out of luck. No iOS devices have this issue and as a result I will be switching, keeping my Note 3 only for rare travel use.
This is a thread for reference: http://forum.xda-developers.com/showthread.php?t=1738171&page=6. Every Android 4.0+ device I have ever encountered (S3, S4, Nexus 4, Nexus 5 [drains even faster], Note 2, Razr, etc.) has this issue (why I want Google to solve it) but it can be solved with kernel mods (why I want Samsung's attention) as it was on the GNex in franco's kernel.
changt34x said:
Does anyone know of the best way to get serious technical attention from Google or Samsung? To put how serious this is (not to start a flame war), I will be purchasing an iPhone 5S on Monday and never another Android device unless either they solve this issue or I get another job (I LOVE my job, so unlikely).
If you search Android Wifi Constantly Downloading, you will find results from people who have this issue. Some people say its sync, some its apps updating, but it is not. It is a bug with the Android kernel in how it doesn't filter multicast packets, resulting in the system staying awake and receiving packets most of the time. Some people have been able to solve it by purchasing a new router or turning off multicast on computers, but this is not an option in an enterprise location like a hospital. I have been stuck with this issue since I got my Note 2 last year.
The Note 3 exacerbates this problem even more because the processor low power states are not as efficient as the Note 2's. On the Note 3 I lose 12-15% per hour idle, on Airplane Mode with Wifi on. I did a test on my Note 2 and in 1 day and 7 hours of complete idle, radios off, and wifi on the battery drained fully.
Normally I carry my phone and a 9000mAH external battery. It takes the entire phone's battery and 80% of the external to get through a normal day. Last week, with the major ice storm, power was out for days and I was stuck at work. Generators provided only power to essential services, so my phone was dead days before the power was back. I do have UL data but Verizon's signal does not penetrate at all. I am tired of worrying about battery and if something like this happens again, I will be out of luck. No iOS devices have this issue and as a result I will be switching, keeping my Note 3 only for rare travel use.
This is a thread for reference: http://forum.xda-developers.com/showthread.php?t=1738171&page=6. Every Android 4.0+ device I have ever encountered (S3, S4, Nexus 4, Nexus 5 [drains even faster], Note 2, Razr, etc.) has this issue (why I want Google to solve it) but it can be solved with kernel mods (why I want Samsung's attention) as it was on the GNex in franco's kernel.
Click to expand...
Click to collapse
Have you seen this?
http://www.amazon.com/dp/B0047E0EII/ref=cm_sw_r_udp_awd_6Fxatb0KT9CDC
Sent from my SM-N900V using Tapatalk
changt34x said:
Does anyone know of the best way to get serious technical attention from Google or Samsung? To put how serious this is (not to start a flame war), I will be purchasing an iPhone 5S on Monday and never another Android device unless either they solve this issue or I get another job (I LOVE my job, so unlikely).
If you search Android Wifi Constantly Downloading, you will find results from people who have this issue. Some people say its sync, some its apps updating, but it is not. It is a bug with the Android kernel in how it doesn't filter multicast packets, resulting in the system staying awake and receiving packets most of the time. Some people have been able to solve it by purchasing a new router or turning off multicast on computers, but this is not an option in an enterprise location like a hospital. I have been stuck with this issue since I got my Note 2 last year.
The Note 3 exacerbates this problem even more because the processor low power states are not as efficient as the Note 2's. On the Note 3 I lose 12-15% per hour idle, on Airplane Mode with Wifi on. I did a test on my Note 2 and in 1 day and 7 hours of complete idle, radios off, and wifi on the battery drained fully.
Normally I carry my phone and a 9000mAH external battery. It takes the entire phone's battery and 80% of the external to get through a normal day. Last week, with the major ice storm, power was out for days and I was stuck at work. Generators provided only power to essential services, so my phone was dead days before the power was back. I do have UL data but Verizon's signal does not penetrate at all. I am tired of worrying about battery and if something like this happens again, I will be out of luck. No iOS devices have this issue and as a result I will be switching, keeping my Note 3 only for rare travel use.
This is a thread for reference: http://forum.xda-developers.com/showthread.php?t=1738171&page=6. Every Android 4.0+ device I have ever encountered (S3, S4, Nexus 4, Nexus 5 [drains even faster], Note 2, Razr, etc.) has this issue (why I want Google to solve it) but it can be solved with kernel mods (why I want Samsung's attention) as it was on the GNex in franco's kernel.
Click to expand...
Click to collapse
If you are sleeping and your Samsung phone melts and catches your pillow on fire, and then you take pictures and post it on Reddit, you will probably get the attention of someone at Samsung.
Other than that, if you are worried about what your phone is doing with the data it is downloading, you can go to Settings > Data Usage and see what apps are using data and how much in whatever time frame you would like. If an app is using too much data, turn off its sync in account settings and disable notifications from within the app. If you are concerned that your phone is using data that it is not telling you about, set up a packet sniffer and see what's going on. Be sure to let us know what you find!
Wile i don't know how to answer your question, you may want to try giving yourself a static IP address at your work and see if the helps with the broadcast battery drain.
adoublearonn said:
If you are sleeping and your Samsung phone melts and catches your pillow on fire, and then you take pictures and post it on Reddit, you will probably get the attention of someone at Samsung.
Other than that, if you are worried about what your phone is doing with the data it is downloading, you can go to Settings > Data Usage and see what apps are using data and how much in whatever time frame you would like. If an app is using too much data, turn off its sync in account settings and disable notifications from within the app. If you are concerned that your phone is using data that it is not telling you about, set up a packet sniffer and see what's going on. Be sure to let us know what you find!
Click to expand...
Click to collapse
Exactly what I figured, but I would rather not burn the apartment down yet. I have done packet analysis and it is the Android kernel. All sources of packets are from local IP addresses on the same enterprise network. No way to stop data from that so far, too bad the obvious solution of using android firewall and blocking kernel from all networks doesn't work.
pdtp said:
Wile i don't know how to answer your question, you may want to try giving yourself a static IP address at your work and see if the helps with the broadcast battery drain.
Click to expand...
Click to collapse
Thank you for trying to provide a solution, but I have tried that before and it doesn't work.
Just like the poster on the other thread said, probably will never get fixed. Well, until Android 5 or 6 comes out. Check out my incredible battery life of 8 seconds screen on, airplane mode, sync off, and wifi on below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You know you might want to talk to your IT department at work, they may not be aware that they have so much broadcast traffic going on & they may have an Android device with the same issue. I'm the system administrator at a hospital and have completed special requests for people with phone issue, esp ones that cause me issues.
pdtp said:
You know you might want to talk to your IT department at work, they may not be aware that they have so much broadcast traffic going on & they may have an Android device with the same issue. I'm the system administrator at a hospital and have completed special requests for people with phone issue, esp ones that cause me issues.
Click to expand...
Click to collapse
I have had a case going on with them for 4 months, but unfortunately it requires changes to a large number of the systems and networking equipment, so it is unlikely to be fixed until we revamp connections to our research facility in 2015. Glad you have been able to help out others in your position though. I would still hope for Google to solve this as the user shouldn't have to change things on the network side when other client devices have no issue.
Something seems a bit odd here, which is:
(3200 mA-hr + 0.8*9000 mA-hr) * (1 A / 1000 mA) * ~3.8 V ~= 39.5 Watt-hrs
Put another way, over a "day" of 12 hours, that's well north of a continuous power dissipation of 3 W.
That is abnormal power dissipation for a phone which is merely awake (not staying in deep sleep) but doing little. That's "screen-on, active game playing on multiple cores at max clock" kind of power usage territory.
Last night I set up a IPv4 multicast sender/receiver pair (with "mint" using two different nodes) on a 802.11g wlan (80 pps @512 bytes -> ~40 kBs), put my N3 in airplane mode, and then connected it to the same WiFi network. In 3 hrs I saw the battery drop only 2%. That seems a bit higher than it should be, but nowhere near the horrid 15-20%/hr you are reporting.
The latter point doesn't prove to much, other than it can be difficult to replicate pathological behaviors that are uncommon.
I believe you are experiencing what you report; but are you sure that it is not merely a case of defective hardware?
Also - you didn't mention: does your phone have installed on it an app which registers for a particular multicast group? (And also - is this IPv4 or IPv6 multicast?)
.
bftb0 said:
Something seems a bit odd here, which is:
(3200 mA-hr + 0.8*9000 mA-hr) * (1 A / 1000 mA) * ~3.8 V ~= 39.5 Watt-hrs
Put another way, over a "day" of 12 hours, that's well north of a continuous power dissipation of 3 W.
That is abnormal power dissipation for a phone which is merely awake (not staying in deep sleep) but doing little. That's "screen-on, active game playing on multiple cores at max clock" kind of power usage territory.
Last night I set up a IPv4 multicast sender/receiver pair (with "mint" using two different nodes) on a 802.11g wlan (80 pps @512 bytes -> ~40 kBs), put my N3 in airplane mode, and then connected it to the same WiFi network. In 3 hrs I saw the battery drop only 2%. That seems a bit higher than it should be, but nowhere near the horrid 15-20%/hr you are reporting.
The latter point doesn't prove to much, other than it can be difficult to replicate pathological behaviors that are uncommon.
I believe you are experiencing what you report; but are you sure that it is not merely a case of defective hardware?
Also - you didn't mention: does your phone have installed on it an app which registers for a particular multicast group? (And also - is this IPv4 or IPv6 multicast?)
.
Click to expand...
Click to collapse
Thank you very much for your insight. I am 90%+ sure that it is not a hardware problem because I have epic standby time when connected to LTE only (1% drain every few hours) or my own wireless network (Netgear WNDR3700, obviously not available at work). This also occurs on my Nexus 5 (man that thing drained fast, but don't have it with me anymore to test), Note 2, and others' S4s and G2s. Surprisingly, it doesn't happen on my 2.3 Droid Inc. I don't have an incredible number of data points because everyone has an iPhone 5 or 5S, but its 100% for all Android devices I know here.
I have a screenshot of Network Log (sorry, accidentally made some stray marks when covering up the IP). All of the packets are generally from all those local IP addresses. There are an incredible number of them, likely over a thousand. They come from that 238 subnet, other subnets, and sometimes from different ports on the same IP. The bandwidth fluctuates, but I would say averages around 3-4Mbps.
I'm not sure if I have any app that registers for a multicast, but I am running CleanROM with all Samsung Hub/AllCast/Share stuff disabled and just productivity apps. I assume this is an IPv4 multicast judging by the IP addresses.
View attachment 2589419
I ran a different multicast experiment yesterday.
I moved both the multicast source and the receiver so that they were both on the the same WiFi segment (with the N3 connected to the same AP/SSID). I did this mostly to try to pump up the traffic rate. (The way I did it in the first trial, the sender was on one subnet, and multicasts had to traverse *two* ancient routers to get to the receiver along a wired path. I was having a significant throughput issues of unknown origin - maybe because the sender was in a VM, or maybe because "mint" sends all it's packets per second in an immediate burst instead of pacing them). In that trial, I couldn't do much better than 40 kbps.
The best I could do with both sender/receiver on the same WiFi segment was with the sender emitting about 1 Mbit/sec of traffic, and the receiver successfully getting about 0.7 Mbit/sec of multicast traffic. So anyway, this meant that the N3 would be sitting there (passively) listening to about 1.7 Mbit/sec of radio traffic most all of which was multicast.
I ran this way for about 3 hours, and the N3 lost 6% of battery (Airplane mode, but WiFi on) - 2%/hr. That is substantially more than when my home WiFi network is quiet, but still nowhere as bad as you are seeing. I also had a WiFi-only Nexus 7 tab sitting there the same way, and it lost a similar amount of battery. I didn't see any evidence that the N3 was "staying awake" at that time.
So, I don't know what to make of it. It sounds sort of reasonable, but the question is - why 3 watts of power dissipation? (For comparison, the PA - Power Amplifier - chips at the front end of cell radio transmitters are usually spec'ed to max out around 2W - and everybody knows how fast a cell phone will drain if it is left on in a zero-service area, or how much shorter "talk time" is than standby time - and your device seems to be using even more power than that!) I certainly believe you are experiencing exactly the symptoms that you describe. But it also does sort of sound like it is something a bit more subtle than just simply "is multicast in use?" - probably it is also something specific about the way your employer's network is utilized or configured or the exact nature of the traffic in use. (Some protocols are incredibly noisy when it comes to broadcasts - the old Novell netware comes to mind)
In IPv4 multicast the destination MAC address can be either individual hosts' MACs or a MAC constructed from a IANA prefix plus a slightly-ambiguous mapping of the IPv4 group multicast address. Interestingly, the Wikipedia page for "IP multicast" makes this comment:
If two hosts on the same subnet each subscribe to a different multicast group whose address differs only in the first 5 bits, Ethernet packets for both multicast groups will be delivered to both hosts, requiring the network software in the hosts to discard the unrequired packets.
Click to expand...
Click to collapse
and then goes on to describe circumstances (dumb switches or dumb routers that don't understand IGMP) how multicast can lead to traffic flooding.
I asked about an App on your phone because there was the possibility that you were using a BYOD device with an institution-supplied App (that might be a multicast receiver).
Anyway, I can't help you get Samsung/Google's attention; about the only way I know that I can help personally is the following: I recently built tcpdump for ARM (tcpdump-4.5.1 plus libpcap-1.5.2) - I can provide it for you via PM if you want a copy (let me know). You'll have to run it from a terminal emulator (as root I suppose). But by doing that, you can capture the output to a file (tcpdump -i wlan0 -s 1600 -w packet_logfile.pkts) and then move that file afterwards to a honest-to-goodness computer and look at the packet capture using Wireshark. I tried this last night with a small sample, and it seems to work correctly. (In my experience, trying to use a Android device for reviewing massive amounts of data - like packet logs - is a horrible experience; you can't see the forest for the trees.)
Note: I don't know if the WiFi radio in the N3 can be operated in "monitor" mode... meaning that you might only see traffic that the radio is collecting based on it's own MAC plus however it deals with multicast... but that latter condition might just be exactly what you need to figure out what exactly is going on.
$.02
i'm wondering if it would be possible to identify problematic batches
of the pixel c to the serial. it has been done before with the nexus
9 that also had a lot of problems at launch.
5A2300 is first 6 digits of my device and i do not not have any issues
although my internet is cap @ 50down/5up. i am curious if there are any
batch differences at this point, or even if there are different batches.
Please report first 5/6 digits of serial, 32GB/64GB, and a concise description
of any issues. thanks.
Edit: i will try to tabulate the results in this post, updating every few days.
-serial----------model-------# report------------- issues reported -------------------- thru post 142
5A190---------[n/a]---------[2]-------[1]had chipped bezel and bad wifi,
--------------[32GB]------------------[2]Distance 12 ft
--------------------------------------Pixel C - 58/64
--------------------------------------iPhone 6s - 58/54
--------------------------------------Nexus 5 - 55/66
--------------------------------------Distance 30 ft + wall
--------------------------------------Pixel C - 58/64
--------------------------------------iPhone 6s - 58/64
--------------------------------------Nexus 5 - 55/66
--------------------------------------Distance 45 ft + 2 walls
--------------------------------------Pixel C - 58/65-68 (3 tests)
--------------------------------------iPhone 6s - 58/15-38 (3 tests)
--------------------------------------Nexus 5 - 55/40-54 (3 tests)
--------------------------------------Welp, seems like my iPhone wifi chip can't push out enough signal
--------------------------------------at the longest distance. My connection is supposed to be 50/50,
-------------------------------------but 55/65 is my typical speed on my PC connected to wifi dongle
------------------------------------at 20 ft. Nexus 5 has a TPU case. iPhone has a plastic polymer + TPU
-------------------------------------case. Pixel C has a standard Smartshell type case for tablets. Router
--------------------------------------is relatively high end (Netgear X4 AC2350) so if this tablet has wifi
-------------------------------------issues, it is being masked by the massive coverage of the router
5A2000-------[32GB]--------------[1]n/a
--------------------------------------[2]No WiFi issues. Massive slowdowns when battery dips below
--------------------------------------20%.
--------------------------------------Only fix I found is to reboot. At first reboot touch screen will
------------------------------------- unresponsive, but a second reboot fixes it.
--------------------------------------I ran an iperf3 test earlier this week. Results are here
-------------------------------------- http://forum.xda-developers.com/showpost.php?p=66276497&postcount=35
--------------------------------------[3] display issue. has a band/shadow that runs the length of the screen. It is especially
---------------------------------------visible when the brightness is low.
--------------------------------------[4] Had the random reboots starting after the May security update. As of today, the
-----------------------------------------screen started acting up where half the screen would be digital "snow" and not
---------------------------------------- refresh even after a full factory reset. Currently in RMA process and new one
---------------------------------------- ordered set to arrive this week.
5A210----------------------------------No issues so far. Wifi about the same as my Nexus 7 and a little
--------------------------------------weaker than my S7.
5A2200-------[64GB]---------[2]-------[1]occasional system lag that clears after a reboot and had a
-------------------------------------------slow
------------------------------------------ WiFi connection until I assigned my Pixel C a static IP address.
------------------------------------------[2]no issues
5A2300-------[64GB]---------[4]-------[1]had occasional touchscreen and keyboard issues
--------------------------------------[2]Slow Wifi on 2.4ghz band. (4x to 10x slower download speeds
--------------------------------------compared to Nexus 6p testing at the same time on the same
--------------------------------------network)
-------------------------------------[3]critical data corruption after a month - device requested
------------------------------------password on boot, confirmed that thepassword correct but it was
------------------------------------unable to decrypt and required factory reset. Following factory
-----------------------------------reset, evice was stuck in a bootloop and could not boot into
-----------------------------------Android Recovery. RMA'd.
-----------------------------------[4]no issues for me either. So far I'm loving it, can't wait to try out N
-----------------------------------[5]5A2300 - fine for first the three months but now the dreaded half
----------------------------------screen freeze fault had started. Definitely a screen hardware issue as
----------------------------------it happens during boot too. Going to RMA
5A2600------------------------------[1]-No issues so far
---------------------------------------[2]- perfect no crashes on MM.
5A2700-------[64GB]---------[1]-------RMA- wifi is not so bad and no problem until now with screen.
------------------------------------------Just one point: it is more yellow than the first one, that was
-------------------------------------------more blue.
5A2800-------[64GB]---------[2]-------[1]Compared to my nexus 6p, wifi range/speed is not as good,
--------------------------------------------not a real problem for me as I can go around my whole
-------------------------------------------apartment without it the dropping connection.
-------------------------------------------I have had it for 24 hours, and have not seen any keyboard
-------------------------------------------problems.
------------------------------------------Will update if I see any problems.
------------------------------------------[2] no wifi or screentouch issues. Perfect quality.
5A290--------[64GB]---------[2]-------[1]No issues at all. At initial start Touch not responsive as
-------------------------------------------expected....but after update gone and no issues with wifi or lag.
------------------------------------- -----[2]Touchscreen issues after reboot/crash (fixed by booting to
-------------------------------------------safemode and leaving the table on/standby all the time) slow
------------------------------------------ wifi depending on the distance from the router
------------------------------------------auto-brightness appears to cause random crashes
5A300--------[32GB]---------[2]-------Both had wifi download issues and this second one has now
------------------------------------------developed a nice case of the touchscreen jitters. (fixed by
------------------------------------------booting into and back out of safe mode)
5B020--------[xxxx]---------[2]-------Wifi dropping [fix].http://forum.xda-developers.com/pixel-c/help/slow-wifi-speeds-t3269506/post64398251#post64398251
--------------------------------------physically perfect but same bad wifi
5B0300-------[32GB]---------[1]-------ordered from Canada (shipped from Mississauga, ON) RMA'd
-------------------------------------------last Friday because had to reboot tablet (froze) and upon
------------------------------------------ reboot, persistent screen issues as reported by
-------------------------------------------many (swipes registered as tap, impossible to use multi fingers
------------------------------------------as 2nd finger is registered on and off, screen bounces back in
------------------------------------------opposite direction of swipe,etc.). No issues connecting to WiFi,
------------------------------------------5Ghz speeds are decent, 2.4Ghz speeds are ridiculous
-----------------------------------------1-2 Mbps downloads in the same room as router, few feet away).
-----------------------------------------Range of WiFi also seems to be much less than any other I tried
-----------------------------------------(Macbook Pro, iPad 3, One m8, Xperia Z3) receiving
---------------------------------------- RMA unit tomorrow (Dec 22nd) will update post.
5B0400-------[32GB]---------[4]-------[1]good WiFi and good screen, no problems.
-------------------------------------------[2]no issues so far, will report.
-------------------------------------------[3]Last update on my 5B0400:
------------------------------------------DEAD, hard drive corrupted after 6 days of use.(see post on
------------------------------------------troubleshoot subforum) Returned it to Google Store within
------------------------------------------Buyer Remorse Period..
-----------------------------------------The pixel c is so far the most unreliable device i've had. I never
-----------------------------------------had these problems with my previous nexus 10.
-----------------------------------------[4] poor bluetooth range. clear line of sight is 10 feet.
-----------------------------------------[5] Wifi bug ==> rma !
5B0500-------[32GB]------------------[1]aside from the fact that the Pixel C seems to have the worst
-------------------------------------------WiFi antenna in the known universe, this one has been flawless
------------------------------------------so far. Not one single unexpected reboot
------------------------------------------[2] display issue. complete right side of display is defective.
5B1200-------[64GB]---------[3]-------[1]good WiFi, good screen, no KB to test
-------------------------------------------[2]Mine has the dropping wifi issue. It also has some problems
------------------------------------------to recognize touches and gestures. The gravity of this issue
------------------------------------------varies alot. The third day using the Pixel C was the worst. Later
------------------------------------------it became better, but it still isn't perfect. Aditionally sometimes
------------------------------------------I'm not able to wake the tablet after it was idle
-----------------------------------------for some time. In this case I have to force reboot it.
-----------------------------------------Happend about four times now (using the Pixel C for two
----------------------------------------- weeks). Gonna return it after the holidays.
----------------------------------------[3]did not even want to turn on past the bootanimation. RMA is
---------------------------------------under way
5B1400-------[xxxx]---------[1]-------Keyboard is a big lagging yes, but for example, more on Firefox
-----------------------------------------than on Gmail.
-----------------------------------------My router is a Sagem Livebox Play (french people will see...)
-----------------------------------------I have, at best, 17/18m for the internet.
-----------------------------------------I did few tests, with Wifi Analyzer, Speedtest and speedof.me :
-----------------------------------------on 2,4Ghz, Pixel C is bad in my bedroom, 8m from router. It has
--------------------------------------- -70db signal, same as my old
-----------------------------------------Nexus 4. The N4 keeps a 12/13m speed, the Pixel barely hits 2m.
----------------------------------------Oh, and it doesn't finish the speedof.me test. Next to the router
---------------------------------------reaches 15m speed (speedtest) but... goes down
--------------------------------------after 5s around 3m. The speedof.me test
--------------------------------------gives me between 2 and 3m.
--------------------------------------on 5Ghz... Pixel C reaches 17m speed on speedtest, on speedof.me,
--------------------------------------ANYWHERE in the flat, even with -70db
5B1600---------[32GB]-------[1]------My replacement Píxel 32GB has the serial number 5B1600.arrived
-----------------------------------------today, no issues yet.
-----------------------------------------Does not have the screen clicking noise my previous píxel had.
-----------------------------------------It seems i have the first 5B1600 here, I hope it does not have
----------------------------------------issues
5B1700-------[32GB]---------[3]------[1]They both have same problem couldn't connect to 5ghz
-----------------------------------------network unless i change router to channel 44, which I've never
-----------------------------------------had to do with any of my 5 nexus devices. The range on it is also
----------------------------------------shocking. I did a comparison to my nexus 6 and nexus 10 and the
----------------------------------------pixel couldn't get the 5ghz in my room but the other two
----------------------------------------devices could and on 2.4. the pixel would only get half
----------------------------------------strength where the other two would be full. My room is not 4
---------------------------------------meters from-the router. Asus rt-68u.
---------------------------------------[2]random reboots. Many many reboots on M, and a few on N2
---------------------------------------Wiped the device and set up as a fresh device, but still get
---------------------------------------random reboots.
---------------------------------------[3] display issue, color banding on all backgrounds.
5B190----------[64GB]---------------LEDs on the cover are different brightness and occasionally get
----------------------------------------terrible screeching feedback when making calls via VOIP.
5B2000-------[64GB]---------[1]-------wifi is not bad but touchscreen problems come after +/- 2 days
----------------------------------------of normal use. After a reboot in safe mode, problems disappear
---------------------------------------for 2 days..
5B2300-------[64GB]---------[2]-------both touchscreen and wifi issues present Slow Wifi on 2.4ghz
-------------------------------------------band. (4x to 10x slower download speeds compared to Nexus
--------------------------------------------6p testing at the same time on the same network)
5B2400-------[32GB]---------[1]-------1) Slow Wifi Problem: Through Walls (193ms, 2.59mbps down,
-------------------------------------------7.88mbps up) compared to a Nexus 6
-------------------------------------------(3ms, 29.5mbps down, 51.79mbps up)-Of course, the Pixel C
-------------------------------------------software related performance issues are here. Regarding
------------------------------------------touchscreen responsiveness, I haven't felt any missed touches
-----------------------------------------however the touch gestures don't seem to be optimized for
----------------------------------------the Pixel C at all.
5B2500-------[32GB]---------[1]-------OK with 2 walls between tablet and wifi access point i have
------------------------------------------problems
-------------------------------------------Speedtest:
-----------------------------------------------------Ping-------------Download--------------Upload
--------------------------------------Htc one m8-------5-------------------41,7-------------------11,1
--------------------------------------Nexus 10 --------5-------------------50,1-------------------11,1
--------------------------------------Pixel C----------6-------------------20,8-------------------10,8
--------------------------------------Edit: The Pixel C also needs a lot more time to connect with wifi
5B300--------[32GB]---------[2]-------[1]have touch screen issues like swipes responding as touches
------------------------------------------and when they do swipe it's chittery, but Wi-fi speed is fine.Wi
-----------------------------------------Fi Speed test: http://i.imgur.com/ODqXJoH.png I'm 2
-----------------------------------------floors away from my router btw on 5Ghzs Touch screen is my
-----------------------------------------main issues
-----------------------------------------[2]no random reboots on MM.Many Many reboots on N2
610700--------------------------------no problems. Android 6.0.1 - March Patch.
612300--------------------------------No touchscreen issue (after I updated from stock). WiFi was
---------------------------------------never an issue, even in the upstairs room on the other side of the
---------------------------------------house away from the router where my nexus 10 struggled. As for
--------------------------------------the corrupt hd issues, I have a feeling it has something to do
--------------------------------------with magnets, but I don't have the keyboard and I don't
---------------------------------------plan on testing that theory. Fwiw I'm running the n preview and
---------------------------------------everything has been great aside from the expected bugs on the os
---------------------------------------side of things.
61250--------------------------------yellow tint bottom of screen.
612600 -------(64GB) -------------Perfect device, Wifi is OK, screen is OK.
6127----------------------------------Received mine 2 hours ago. It's a 64GB I still need tot try it out
--------------------------------------and test.Speedtest was promising
--------------------------------------with 25Mbps higher then my Nexus 10
--------------------------------------I have very mixed results going from 173Mbps to 6Mbps.
--------------------------------------1st try 10m with 2 doors in between @ 37Mbps.
--------------------------------------2nd try @ 84Mbps.
--------------------------------------1st try upstairs around 10m @ 34Mbps
--------------------------------------2nd try @ 69Mbps
--------------------------------------Upload speed is capped with my ISP at 12Mbps so I always get this
--------------------------------------speed
61300 --------------------------------Perfect. No gaps or creaking and wifi is fine. Success at last.
620100--------------------------------gap between glass and metal case under the power button,
----------------------------------------except this one is longer along that top edge before it meets like
----------------------------------------it does around the rest of the tablet. Google escalated...
--------------------------------------Will see what happens. Otherwise, fine with wifi and no screen
---------------------------------------issues or clicking!
6202000xx------[32GB]--------[3]------[1]Perfect. No WiFi issues, no touchscreen issues. I have
--------------------------------------------noticed chrome fails to scroll a pasge sometimes, -but that's a
--------------------------------------------browser bug, not a touchscreen bug.
--------------------------------------------[2] No issues
--------------------------------------------[3] 64GB. wifi issue. also clicking sounds from pressing on display.
-------------------------------------------[4] - random reboots, RMA
62030---------------------------------I've just got a 32gb in UK with dev discount C1502W 62030 no
----------------------------------------issues so far with 2 days of use as tablet only no keyboard. It's a
----------------------------------------monster eats media and web pages all day long like nothing
----------------------------------------happened!
Miscellaneous Comments----------------Router in the basement, so through one floor and its in a
-----------------------------------------------separate closed room. Pixel C 22 ms, 5.1 MBS dwn, .73 mbs
-----------------------------------------------up. Nexus 6p, 19 ms, 5.9 MBS down, .68 mbs up.
-----------------------------------------------Yes my DSL sucks as I'm in the country. But my Pixel that
-----------------------------------------------arrive today does not seem to have the WiFi issue.
It certainly feels like most if not all have wifi and or touchscreen issues but I'll throw down:
1st Pixel C 32GB: 5A300
2nd Pixel C 32GB: 5A300
Both had wifi download issues and this second one has now developed a nice case of the touchscreen jitters. (fixed by booting into and back out of safe mode)
I wonder if the Pixel team is the party rerouting the RMAs once they get with UPS. They need to do something here...
atg284 said:
It certainly feels like most if not all have wifi and or touchscreen issues but I'll throw down:
1st Pixel C: 5A300
2nd Pixel C: 5A300
Both had wifi download issues and this second one has now developed a nice case of the touchscreen jitters. (fixed by booting into and back out of safe mode)
I wonder if the Pixel team is the party rerouting the RMAs once they get with UPS. They need to do something here...
Click to expand...
Click to collapse
is that a typo up there? sure it is not 5A230? just asking since it is close.
dkryder said:
is that a typo up there? sure it is not 5A230? just asking since it is close.
Click to expand...
Click to collapse
Nope! No typo and I did find it a bit odd that ours are different this early on. I saved my RMA conversation with the google rep and that is how I confirmed my past serial number. So both of mine came from the same batch.
Is yours 32GB or 64GB? Perhaps that is it.
5A2300 here as well. I've had occassional touchscreen and keyboard issues. Haven't seen any problems with Wi-Fi as of yet, although that doesn't mean they don''t exist. I just might not have noticed them.
64GB model, if that makes a difference.
5A2000 32GB here. No problems with wifi or touchscreen.
5A2200 64GB
I have the occassional system lag that clears after a reboot and had a slow WiFi connection until I assigned my Pixel C a static IP address. I can't remeber where it shipped from.
atg284 said:
Nope! No typo and I did find it a bit odd that ours are different this early on. I saved my RMA conversation with the google rep and that is how I confirmed my past serial number. So both of mine came from the same batch.
Is yours 32GB or 64GB? Perhaps that is it.
Click to expand...
Click to collapse
64GB model
atg284 said:
It certainly feels like most if not all have wifi and or touchscreen issues but I'll throw down:
1st Pixel C: 5A300
2nd Pixel C: 5A300
Both had wifi download issues and this second one has now developed a nice case of the touchscreen jitters. (fixed by booting into and back out of safe mode)
I wonder if the Pixel team is the party rerouting the RMAs once they get with UPS. They need to do something here...
Click to expand...
Click to collapse
it seems google is definitely re routing to get a closer look at the units. i want this device to succeed so it is crystal clear that google needs get hands on and try to
figure out what the problems are, what needs to be done to get it fixed and try to keep as many of those who bought the unit happy.
dkryder said:
it seems google is definitely re routing to get a closer look at the units. i want this device to succeed so it is crystal clear that google needs get hands on and try to
figure out what the problems are, what needs to be done to get it fixed and try to keep as many of those who bought the unit happy.
Click to expand...
Click to collapse
Very true! They have until the 21st of January for me.
Mine is 5B020
I only had wifi dropping issues which I've explained in the other thread how I fixed it.
Sent from my iPhone using Tapatalk
5B2500 32 gb
no problemms
5B0400
32GB good WiFi and good screen, no problems.
Sent from my Pixel C using Tapatalk
5B1200 64GB - good WiFi, good screen, no KB to test
Gesendet von meinem Pixel C mit Tapatalk
To you guys and gals with good wifi, are you testing this from around 20-30 feet away on a different floor and or rooms away? The wifi issue is only at a reasonable distance through a wall or two or a floor. Again, away from the router and not close to it. Thanks for any info.
5B2000 - 64Gb - wifi is not bad but touchscreen problems come after +/- 2 days of normal use. After a reboot in safe mode, problems disappear for 2 days...
Envoyé de mon SGP621 en utilisant Tapatalk
5A290 64GB model. No issues at all.
At initial start Touch not responsive as expected....but after update gone and no issues with wifi or lag.
5B2300 64GB both touchscreen and wifi issues present
First one 5A190 had chipped bezel and bad wifi, second one 5B020 physically perfect but same bad wifi ...
5A2800 on RMA'ed device, thus far I get slower download speeds issue (for lack of better words) but thus far no touchscreen issues, although I have kept the device in landscape since getting this as that appears to be a possible root cause.
The original was a 5A110 and has terrible touchscreen issues, out of the box really
Now that I've got the Moto X Pure Edition activated, I've been able to work out some of the kinks inherent using it as a daily driver. One noteworthy issue that remains is an odd bug where the device will completely lose connection to the Internet on both a WiFi and cellular data connection, usually after transitioning between types of connections. When this happens, an exclamation point is displayed next to the icon representing whichever connection is currently active and nothing is able to transmit data to or from the Internet or even my local network.
Rebooting the device always fixes the problem, but this issue is materializing a bit too often for my liking, which is usually once every time that I return to a WiFi network after being disconnected from one for some time (more testing may have to be done to confirm exactly what triggers it).
The device is running the stock rom (rooted) and the stock kernel along with the usual tweaks (ad-blocking, Xposed framework, audio fixes, etc.). Anybody seen this before or know what might be causing it?
UPDATE (3/1/2017)
Figured it out! The problem appears to have been caused by my failure to whitelist certain applications in PowerNap. After following the instructions found in the Moto X Pure Edition power optimization thread, the problem appears to have vanished. I don't know if it was the Google Services Framework, JavaTcmdHelper, Android System, or some combination of those that needed to be whitelisted, but the problem has vanished. At least one of those must be responsible for verifying the validity of an Internet connection in sleep mode, which would cause the device to become confused when it would wake up with a different connection that it hadn't verified (that's my theory at least).
At any rate, it is no longer an issue.
Update (Later on 3/1/2017)
Well, it looks like it might not be fixed so well after all. A couple hours after arriving home today, I went to use the device and saw the dreaded "!" next to the network indicator. Still, two days is longer than it's ever lasted before. I've cleared the cache and dalvik/ART cache to see if something in there might be gumming it up and will add another post to this thread if the problem returns.
Still an issue
Looks like it might not be fixed after all. I lost connection again the other day in a parking lot and once more today after getting home. Any ideas as to what could be causing this?
I just recently got my x pure. I've seen this issue on mine too.
Another one!
inkdaddy66 said:
I just recently got my x pure. I've seen this issue on mine too.
Click to expand...
Click to collapse
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Bill720 said:
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Click to expand...
Click to collapse
I'm unlocked and rooted. Running validus 7.1.1 ROM.
does your configuration look anything like this?
inkdaddy66 said:
I'm unlocked and rooted. Running validus 7.1.1 ROM.
Click to expand...
Click to collapse
That too is interesting. I'm running the stock Rom, (rooted) so we can probably eliminate that as a potential cause. Given how little reference there is to this on the web at large, the problem is probably caused by a common app or setting (or some kind of unfortunate combination) running on both of our phones.
All we need to do is figure out what kind of "unusual" stuff our devices have in common. I'll rattle off a list of software and settings that might be out of the ordinary or network-related; you tell me if you're running anything like it on your phone.
AdFree
A.R.I.S.E. audio
FolderSync
Ice Box (Motorola Update Service is the only frozen app)
TOTAL Wireless My Account App
Pebble, MyTracks, and Pebble MyTracks
SlingPlayer (this one sometimes wakelocks)
Titanium backup (I tried restoring some WiFi access points once, but it didn't work)
Xposed Framework with Amplify, Greenify, and Power Nap installed and configured as instructed in the Moto X Pure Edition battery life guide thread OP. I've also got MinMinGuard and YouTube AdAway.
As far as settings go, I've not got much in the way of unusual configurations. I enabled the system UI tuner to get the battery percentage and the extended developer options to try out multi-window, (and to change the animation scales to .5X) but everything in there is still pretty much stock.
Does your configuration have anything in common with mine?
Close, but no cigar
It got almost 8 days this time before it happened again. I thought that maybe switching to the legacy DHCP client had done the trick, but that was apparently not the case. Any ideas as to what could be causing the issue or how to fix it?
Or, if you're having the same problem, can you look at my list in the previous post and tell me if any of the software or settings are similar so that we can narrow down the cause?
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Anything familiar?
aybarrap1 said:
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Click to expand...
Click to collapse
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Bill720 said:
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Click to expand...
Click to collapse
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Cause and effect differential diagnosis
aybarrap1 said:
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Click to expand...
Click to collapse
Hmmm... That's also interesting, but I just don't see how system UI tuner could be harming anything. Do you have any other apps or settings at all that you think could be causing the issue?
If this were anything other than my primary, I'd hard reset and troubleshoot that way, but I don't exactly have the time to pull the rug out of an otherwise-working setup right now, so this is going to have to be done the hard way (or, in the case of hardware glitch, lived with).
At any rate, I discovered a new symptom earlier in the week. This time, Internet connection was lost, but only for WiFi, so the connection would actually fall back to Cellular and still continue to work. As before, toggling the connection had no effect, but rebooting the device "fixed" it. I thought maybe it was a fluke, since we'd had an AP hiccup over the weekend, (I refuse to reboot that thing because I'm going for an uptime record) but it happened again on Wednesday, so I'm not sure what to make of it.
Side-issue aside, I'm beginning to wonder if it's some kind of combination of network behavior and usage pattern that brings the issue about. It seems like if I stay within range of the WiFi network, no issue develops, but if I move out of its coverage and don't touch the phone for a while, that allows for ideal conditions under which to replicate the problem (sometimes). I haven't nailed down a consistent pattern yet, but the problem does emerge more often when I'm returning home than at other times. Any thoughts?
Update (3/24/2017; 12:32PM)
Scratch that last part about the issue only being triggered upon "arriving home." The problem happened again this morning, in the same general area. First, no WiFI, then, after resetting the connections, no cellular either. I captured a LogCat before rebooting this time though. Anyone want to take a crack at sifting through that to see if it offers any clues?
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Possible fix
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
pizza_pablo said:
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Click to expand...
Click to collapse
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Bill720 said:
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Click to expand...
Click to collapse
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Always on is not necessarily a good thing. Reality is that when you lose or turn off WiFi, mobile data should only be delayed only by a second or two. There is no real benefit to having it on except for maybe VOLTE.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Actually, it's a battery killer more than anything else... It keeps cellular data active even when on WiFi.
It is possible it's a tower thing though. I have noticed at this one hotel I stay at frequently people tell me they call and it rings or just goes to voicemail even though I have good signal. After investigating it a bit, I'm in a spot that has nearly identical signal strength from 3 towers and it's a metro area so there are 4+ bands accessible... I've seen times watching LTE Discovery where it keeps switching bands and towers for 30 to 120 seconds or so, like it can't make up it's mind what to talk to because it's confused, then it locks on for a while before it starts it's cycle again. During those cycles I think is when people can't call me, can't really say if it affects internet or not since I tend not to use my phone too much in the evenings when I'm on the road (usually on laptop).
Uptime record, but... it's back
acejavelin said:
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Click to expand...
Click to collapse
Interesting. I thought for sure that I had the default settings checked in there, but maybe I did change it early on and just forgot. Either way, waiting an extra five seconds to establish a data connection isn't that huge of a deal for me, so I'll leave it off anyway in exchange for battery life when the signal's poor.
At any rate, however, the problem has returned. I was just a few hours short of 9 days of uptime and really thought that I was out of the woods with this problem, but it has returned once again upon returning into range of the home access point. Looks like we're back to the drawing board on this one.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Bill720 said:
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Click to expand...
Click to collapse
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
*another* new strategy (sigh)
For this week's shot in the dark, I'm going to try manually switching WiFi off before I leave anyplace covered by an access point. Since the problem seems to occur most often when connected to WiFi or when connecting to it, maybe this will make some kind of a difference.
pizza_pablo said:
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
Click to expand...
Click to collapse
I see now; my mistake.
Sorry for the crosspost - hoped I can get more eyes here...
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
P.S. One thing I cannot do on IOS AW app is see battery usage by app. Sadly if I paired up to my old Galaxy S5 test phone, I suspect the problems may go away as it would be a first pairing of a watch to that phone plus it's not the same as the use environment.
wig said:
Sorry for the crosspost - hoped I can get more eyes here...
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
P.S. One thing I cannot do on IOS AW app is see battery usage by app. Sadly if I paired up to my old Galaxy S5 test phone, I suspect the problems may go away as it would be a first pairing of a watch to that phone plus it's not the same as the use environment.
Click to expand...
Click to collapse
Man, as I was reading this I was like.. is this guy a mind reader.. I swear to you I have the exact same issues, and the same reason for switching from Apple watch Series 3 to Android Wear (watches should be round darnit).. I almost bought the HW2 classic and for the same reason (smaller screen, giant bezel, etc.) bought the LGWS.. I sure hope someone has some advice for both of us recent converts!
Day 2... full delete of app IOS, reboot phone. Full restore of watch. Remove from bluetooth pairings. Start over from scratch.
left it mostly stock... only OK Google and Cellular turned off (no sim in there anyhow, but to be safe since technically all phones are supposed to allow 911 calls regardless of sim status)... in that stock vanilla flavor - battery held up all day. Ended the day with about 30%. WIFI was not linked to any network, so just Bluetooth to my phone. All worked great.
Day two of grand experiment.. added WIFI set to auto on. Loaded the main app I really want, Watchmaker. five hours of use 44% of battery gone - roughly 8ish percent per hour. Not terrible, but compared to vanilla. MUCH worse. Will keep playing. The mix is in there somewhere.
The shocker is that the HW2 has a slightly smaller battery (10mAh smaller) but also a MUCH smaller face. That would account for it.
I had exactly the opposite experiences with the Huawei and LGWS. I tried out a Huawei watch 2 classic for about a week, and I had TERRIBLE battery life. Like, fully charged to DEAD in 12 hours. The LG lasted me 18 - 25+ hours (the lesser on workout days). I had all connections turned off except Bluetooth, although I turned on GPS on the LG and didn't notice any battery life change. I had assistant on, fit with everything on, always on, basically most of the apps and such.
Unfortunately, it seems like the battery life you get depends on the watch, and what you have on with AW. With LTE and WiFi on, I'm sure I would have been charging the LG once at least during the day.