Related
I am not experiencing any issues with wifi or touchscreen input on my Pixel C, so doing this wouldn't really be relevant, but I am curious if somebody with the aforementioned problems has tried flashing the MXB48K factory image from here https://developers.google.com/android/nexus/images?hl=en
I know that there hasn't been any word from Google on what the MXB48K image is, but I figure you can't irreversibly harm your Pixel C by doing it and it may have updated Wifi and/or touchscreen drivers that help with the problems people are having. I'd be happy to help write up some instructions, if necessary, should somebody decide to try it.
Most peoples tablets updated to this build when switched on anyway
Roxas598 said:
Most peoples tablets updated to this build when switched on anyway
Click to expand...
Click to collapse
Are you 100% sure about that? Mine is fully up to date, according to the built in update, but it is still on MXB48J
oRAirwolf said:
Are you 100% sure about that? Mine is fully up to date, according to the built in update, but it is still on MXB48J
Click to expand...
Click to collapse
Same I'm still on J also. Mine updated when I turned it on but its still the J build.
Yeah I'm wondering if this build fixed the wifi and touchscreen problems. If it did I would reorder
Edit: Actually, this build was uploaded at the same time the J build was uploaded wasn't it? That would just mean it has the same problems
oRAirwolf said:
Are you 100% sure about that? Mine is fully up to date, according to the built in update, but it is still on MXB48J
Click to expand...
Click to collapse
I'll double check when I get home but when I switched the tablet on there was an update and I just assumed it was OK 38J already since there was only 2 images available
Not to mention there is no change log for either build. Worth a shot if someone has time over Christmas but I won't consider reordering it until Google officially issues a fix for these issues.
Turns out you were correct and it's on build 48J
I'm gonna flash the other one now I guess see what the deal is.
Wonder what version the tablet is on when first open though :S
Roxas598 said:
Turns out you were correct and it's on build 48J
I'm gonna flash the other one now I guess see what the deal is.
Wonder what version the tablet is on when first open though :S
Click to expand...
Click to collapse
I am interested to find out if it helps. I may flash mine to K just for ****s and giggles.
See i;m looking at the other build and it's the same date
I doubt it's actually worth flashing, if it was something important it would have been OTA'd by now
I just got done setting up my Pixel C on MXB48K. Seems to work fine. Again, I wasn't noticing the wifi problems or touchscreen problems, but I ran some control tests for the wifi before i flashed it. I will run the same tests before I go to bed and see if it makes a difference.
oRAirwolf said:
I just got done setting up my Pixel C on MXB48K. Seems to work fine. Again, I wasn't noticing the wifi problems or touchscreen problems, but I ran some control tests for the wifi before i flashed it. I will run the same tests before I go to bed and see if it makes a difference.
Click to expand...
Click to collapse
Now that Google's Pixel C is available for purchase on the Google Store, the company has posted the first set of factory images for the device. There are two Android 6.0.1 images available, carrying the build numbers MXB48J and MXB48K, respectively.
Editor's note: We were informed that MXB48J is the official released build. MXB48K is for development purposes.
Source: http://www.androidcentral.com/pixel-c-android-601-factory-images-now-available
rveupen said:
Now that Google's Pixel C is available for purchase on the Google Store, the company has posted the first set of factory images for the device. There are two Android 6.0.1 images available, carrying the build numbers MXB48J and MXB48K, respectively.
Editor's note: We were informed that MXB48J is the official released build. MXB48K is for development purposes.
Source: http://www.androidcentral.com/pixel-c-android-601-factory-images-now-available
Click to expand...
Click to collapse
oRAirwolf said:
I just got done setting up my Pixel C on MXB48K. Seems to work fine. Again, I wasn't noticing the wifi problems or touchscreen problems, but I ran some control tests for the wifi before i flashed it. I will run the same tests before I go to bed and see if it makes a difference.
Click to expand...
Click to collapse
oRAirwolf - is the Multi-window option available in the K build Developer Options by any chance?
ckevinwelch said:
oRAirwolf - is the Multi-window option available in the K build Developer Options by any chance?
Click to expand...
Click to collapse
I don't see it in there, no. I wish Google would be a little more transparent with the factory image differences.
does the k build have the same 2 stage bootloader?
dkryder said:
does the k build have the same 2 stage bootloader?
Click to expand...
Click to collapse
I'm not really sure what that is. If you can describe what to look for, I am happy to check.
I've been on this build for awhile and I don't have issues, BUT! I didn't notice any issues while on J either. So I may just have a better unit.
Sent from my Pixel C using Tapatalk
It is my hope that somebody who is experiencing issues give this build a try. This build definitely works fine for me.
oRAirwolf said:
It is my hope that somebody who is experiencing issues give this build a try. This build definitely works fine for me.
Click to expand...
Click to collapse
Thank you for testing this.
Are you a bit of a distance away from your router. Like the other side of the house or up/down a floor? The wifi works fine when you are in close proximity but rapidly degrades the further away you get. Ll of my other devices are fine anywhere in the house except for the Pixel C.
You can use speed test apps for mbps speed tests and the Wifi Analyzer app to test the dBm level.
Using these really shows the difference between the Pixel C and all my other devices. It is not just a numbers thing either. I really see slower internet speeds in use.
atg284 said:
Thank you for testing this.
Are you a bit of a distance away from your router. Like the other side of the house or up/down a floor? The wifi works fine when you are in close proximity but rapidly degrades the further away you get. Ll of my other devices are fine anywhere in the house except for the Pixel C.
You can use speed test apps for mbps speed tests and the Wifi Analyzer app to test the dBm level.
Using these really shows the difference between the Pixel C and all my other devices. It is not just a numbers thing either. I really see slower internet speeds in use.
Click to expand...
Click to collapse
What if you install the K version, atg? Does it solve your wifi issue?
Here is another update to M6E69B
https://android.googleapis.com/pack.../ea3f22cafa01264ded185bdec71b42821cec2c59.zip
I have no idea what it fixes / enhances / solves. I just got the update notice on my watch and grabbed it.
edit - I cannot see anything new other than the version. Sounds, watchfaces, installed apps, all the same. Let's hope the bugs are fixed, especially bluetooth drops.
Updated to it too. Can't spot any diffrences.
Someone on Reddit says it is a security update. Nothing else shows on Google Search.
https://www.reddit.com/r/hwatch/comments/4w9sxa/system_update_85/
Pkt_Lnt said:
Someone on Reddit says it is a security update. Nothing else shows on Google Search.
https://www.reddit.com/r/hwatch/comments/4w9sxa/system_update_85/
Click to expand...
Click to collapse
Quick glancing the patch tells me that bluetooth, wifi and clockwork were updated. More stuff and security, but mostly those.
justasalekna said:
Updated to it too. Can't spot any diffrences.
Click to expand...
Click to collapse
How to flash the zip, or unpack ?
Sent from my A168-L09 using XDA-Developers mobile app
Fauert said:
How to flash the zip, or unpack ?
Sent from my A168-L09 using XDA-Developers mobile app
Click to expand...
Click to collapse
You need to adb sideload it in recovery.
negamann303 said:
Quick glancing the patch tells me that bluetooth, wifi and clockwork were updated. More stuff and security, but mostly those.
Click to expand...
Click to collapse
Was hoping this update fixed the pairing issue on Nexus 4 phones, so I installed your latest ROM update, but it still fails to pair.
Received the update and installed automatically instantly. Haven't noticed anything different and I still can't seem to answer whatsapp calls anymore over bluetooth.
This was working before the last 1.5 update.
I have not gotten any update. Does it really take this long?
Sent from my ASUS_Z00AD using Tapatalk
Langgam84 said:
I have not gotten any update. Does it really take this long?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Tell me about it!!!! I'm still on "June" update, since I got the watch in July. I've been waiting for the OTA and it never comes. Is there a trick? I go to about>check for updates and its always "up to date". I have my "wifi" going to sleep after 3hrs. The thing always on the puck/charger overnight at 100% battery. But these OTA never happen. Looks like I've already missed the "July" update, and will probably have to get that before the "august" update....
What are you guys doing ??? Other than sideloading via adb....
mk69 said:
Tell me about it!!!! I'm still on "June" update, since I got the watch in July. I've been waiting for the OTA and it never comes. Is there a trick? I go to about>check for updates and its always "up to date". I have my "wifi" going to sleep after 3hrs. The thing always on the puck/charger overnight at 100% battery. But these OTA never happen. Looks like I've already missed the "July" update, and will probably have to get that before the "august" update....
What are you guys doing ??? Other than sideloading via adb....
Click to expand...
Click to collapse
i'm am also still at june update but got the notification of the update so when I am at home, I will charge my watch above 40% and hopefully it will be the august update.
Done the update: it now mentions july but no august yet
1.5 update can no longer make calls, battery life terrible!
I just updated last night and now I can no longer make calls, and the battery life is terrible!
"Voice Calling Info. Service not available, please try again later."
If the call does go through I can't hear the other person and they can't hear me?
Langgam84 said:
I have not gotten any update. Does it really take this long?
Click to expand...
Click to collapse
yes, it takes a while. I received mine just a view minutes ago.
That is why I posted this in the spirit of "share on XDA", so you don't have to wait. :highfive:
zdubin1 said:
I just updated last night and now I can no longer make calls, and the battery life is terrible!
"Voice Calling Info. Service not available, please try again later."
If the call does go through I can't hear the other person and they can't hear me?
Click to expand...
Click to collapse
I applied the update last night. The battery life seems about the same to me and the making/receiving calls on the watch still works.
Liquid Li0n said:
i'm am also still at june update but got the notification of the update so when I am at home, I will charge my watch above 40% and hopefully it will be the august update.
Done the update: it now mentions july but no august yet
Click to expand...
Click to collapse
No where has I seen that Huawei does monthly updates on any device. This was a patch for bluetooth, wifi, and security from comments I have found and searching. Older versions never even mentioned the security patch data. I do see better BT range and few BT dropouts, battery is the same. I don't do calls on the watch but use my BT headset for that.
Got the update today. Yep, it looks like it doesn't come at the same time for everyone. Thanks guys.
Sent from my ASUS_Z00AD using Tapatalk
Pkt_Lnt said:
No where has I seen that Huawei does monthly updates on any device. This was a patch for bluetooth, wifi, and security from comments I have found and searching. Older versions never even mentioned the security patch data. I do see better BT range and few BT dropouts, battery is the same. I don't do calls on the watch but use my BT headset for that.
Click to expand...
Click to collapse
I got my update earlier today and hope this helps my BT dropouts too! I have suspected that my BT headset dropouts might be related to my watch, so we shall see.
bbygfy said:
I applied the update last night. The battery life seems about the same to me and the making/receiving calls on the watch still works.
Click to expand...
Click to collapse
I think I may have found the issue. My Google play services looks to be way out of date. I've updated it on my phone, but it doesn't transfer to my watch? I tried updating it from the watch directly
about > version> google play services it says "checking for updates" but doesn't update it? Help!
zdubin1 said:
I think I may have found the issue. My Google play services looks to be way out of date. I've updated it on my phone, but it doesn't transfer to my watch? I tried updating it from the watch directly
about > version> google play services it says "checking for updates" but doesn't update it? Help!
Click to expand...
Click to collapse
Definitely old version. Other than the recync apps in the AW phone app or just an complete install, I have no idea, sorry
Got an update this morning, did anybody else get this one pushed down? Didn't see any change log for it.
scadilla said:
Got an update this morning, did anybody else get this one pushed down? Didn't see any change log for it.
Click to expand...
Click to collapse
I believe it is just security patches
Sent from my SM-G935V using Tapatalk
I got it this morning, too.
No reason to be sad that you got security patches. With everything that's been going on, I want my phone as secure as possible. I'm glad Samsung and Verizon are basically doing a monthly patch of the S7 line. Shows they want to keep the phones secure.
I'm getting wierd page redraw issues with Nova launcher since this update
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
beezar said:
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
Click to expand...
Click to collapse
Yes it does. Feels good to have it back
Feels back to normal...
beezar said:
Still on May update, never upgraded to June because of this issue. Does the July update fix it?
Click to expand...
Click to collapse
BTW this wasn't an issue, it was intentional from Google.
Sent from my Pixel 2 XL using XDA Labs
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
jrg67 said:
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
Click to expand...
Click to collapse
As soon as I clicked it, then I received the 54.7 MB OTA.
galaxys said:
As soon as I clicked it, then I received the 54.7 MB OTA.
Click to expand...
Click to collapse
I just looked around some more online and found others complaining of the same thing. Perhaps it's working for some but definitely not all. Just hit it again, still nothing.
Hate to hijack the thread, but this is as good a place as any to ask this really simple question of mine:
How do I update to the latest July patch if I'm still on stock May, but rooted with Magisk & Xposed enabled? I'm assuming I can just flash the full factory image zip with fastboot (disabling -w to avoid wipe) and just making sure to remove Magisk/Xposed before hand.
Latiken said:
Hate to hijack the thread, but this is as good a place as any to ask this really simple question of mine:
How do I update to the latest July patch if I'm still on stock May, but rooted with Magisk & Xposed enabled? I'm assuming I can just flash the full factory image zip with fastboot (disabling -w to avoid wipe) and just making sure to remove Magisk/Xposed before hand.
Click to expand...
Click to collapse
Yeah you can for sure do that when you flash the factory image it will remove magisk and xposed for u.
mac796 said:
Yeah you can for sure do that when you flash the factory image it will remove magisk and xposed for u.
Click to expand...
Click to collapse
Thank you for the confirmation. I assumed it would do that, but I'll probably do it myself to make sure nothing goes wrong in the flashing process.
Still slow after July update.
Sent from my [device_name] using XDA-Developers Legacy app
jrg67 said:
Has anyone pulled the update by manually clicking "Check for Updates"? I have hit it multiple times throughout the day as recently as 15 minutes ago and still saying I'm up to date on June. Is this busted again?
Click to expand...
Click to collapse
My work pixel 2 got the OTA yesterday. My pixel 2 xl still not seeing it.
Travisdroidx2 said:
My work pixel 2 got the OTA yesterday. My pixel 2 xl still not seeing it.
Click to expand...
Click to collapse
I tried to report the issue to google chat support but those people are useless outside of processing RMAs. 2 different reps told me the update isn't out yet bc it's dated the 5th and had no idea hitting the check for updates button overrides the staged rollout. Ugh.. I reported the issue on the pixel community board so let's see if that gets any traction.
jrg67 said:
I just looked around some more online and found others complaining of the same thing. Perhaps it's working for some but definitely not all. Just hit it again, still nothing.
Click to expand...
Click to collapse
I side loaded it using ADB. For some reason, it takes several days for the update to get to me in June (when prior updates worked after running "check for update").
I think delay is still present in july build as confimred by some users, so i will stay with May Build till now(waiting for fix).
I am still waiting for the July updates....
still haven't recieved July security update OTA for my Pixel 2 XL.
FPSRocketeer said:
still haven't recieved July security update OTA for my Pixel 2 XL.
Click to expand...
Click to collapse
Same.
For me June's OTA showed up instantly, but also still waiting for July security update.....
Sent from my Pixel 2 XL using XDA-Developers Legacy app
grgana said:
For me June's OTA showed up instantly, but also still waiting for July security update.....
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly the same here, thats so odd.. I wonder what is the cause of this, cuz some people got it pretty much instantly when Google released the update.
I took the update last week. Ever since, my device will connect/disconnect loop with my car. I do not have this issue with other bluetooth devices. That said, it's not the car, as my pixel 3xl is able to connect and stay connected without issue.
Some searching yesterday showed that this is a known issue with no official fix. I'm wondering if anyone has found a fix beyond the usual bluetooth troubleshooting? I'm assuming flashing old bluetooth packages isn't going to do anything...
https://www.reddit.com/r/GooglePixel/comments/1045k5g
Try some of the solutions from the comments here, or wait until Feb update.
I'm on the same boat lol
DarkShadowMX said:
https://www.reddit.com/r/GooglePixel/comments/1045k5g
Try some of the solutions from the comments here, or wait until Feb update.
I'm on the same boat lol
Click to expand...
Click to collapse
Yeah, saw that before I posted. Thanks though!
Horror_Business said:
Yeah, saw that before I posted. Thanks though!
Click to expand...
Click to collapse
We are 138.
February update appears to have resolved the issue for me.