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?
Related
Can anybody get this to work? I'm constantly dropped wifi direct signal with my tv. I successfully got it to mirror for 5 seconds before it froze. And most of the time I can't even get the N7 to detect my tv in the wifi direct settings. While I have my Note2 right next to it, it can detect it no problem.
Anybody have this working flawlessly? I'm also getting random reboots.. so I'll return this tomorrow I guess (16gb)
lazynok said:
Can anybody get this to work? I'm constantly dropped wifi direct signal with my tv. I successfully got it to mirror for 5 seconds before it froze. And most of the time I can't even get the N7 to detect my tv in the wifi direct settings. While I have my Note2 right next to it, it can detect it no problem.
Anybody have this working flawlessly? I'm also getting random reboots.. so I'll return this tomorrow I guess (16gb)
Click to expand...
Click to collapse
I was testing this last night. It is finicky but I got it to work pretty well.
Two things to note based on my observation:
1. Rotating the screen during mirroring drops the connection. This has to be a software bug because my S4 does not do this.
2. The wifi antenna seem to be at the top half of the tablet...so if you're in landscape mode, hold the tablet such that you don't have your hand over that portion. I find that the connection quality is extremely dependent on how you hold the tablet.
Lolento said:
I was testing this last night. It is finicky but I got it to work pretty well.
Two things to note based on my observation:
1. Rotating the screen during mirroring drops the connection. This has to be a software bug because my S4 does not do this.
2. The wifi antenna seem to be at the top half of the tablet...so if you're in landscape mode, hold the tablet such that you don't have your hand over that portion. I find that the connection quality is extremely dependent on how you hold the tablet.
Click to expand...
Click to collapse
I don't have the ability to test it, as i don't have a miracast enabled device, but that sounds a lot like the old 'you're holding it wrong,'Apple quip.
I got the same issues as Lolento.
My Netgear Pvt3000 works perfectly fine with my HTC One (ARHD 12.3 rooted). When i connect it to my Nexus7 2013 (Stock rooted) it starts lagging horribly as soon as i swap it into landscape.
Got no solution for that so far. Kinda disappointing.
marc99ch said:
My Netgear Pvt3000 works perfectly fine with my HTC One (ARHD 12.3 rooted). When i connect it to my Nexus7 2013 (Stock rooted) it starts lagging horribly as soon as i swap it into landscape.
Click to expand...
Click to collapse
I have no problems with my PTV3000. Did you update to the latest firmware? Except for an one second occasional slip in video, it works flawlessly. My only problem is that the TV shows it in a 1280x720 resolution.
unni_kmr said:
I have no problems with my PTV3000. Did you update to the latest firmware? Except for an one second occasional slip in video, it works flawlessly. My only problem is that the TV shows it in a 1280x720 resolution.
Click to expand...
Click to collapse
Weird. I'm on 4.3 (Build JSS15J). Is there somewhere the latest firmware for download available? Thanks.
I would really prefer to cast it from my Nexus instead of my One.
marc99ch said:
Weird. I'm on 4.3 (Build JSS15J). Is there somewhere the latest firmware for download available? Thanks.
Click to expand...
Click to collapse
Sorry, I meant the PTV3000 firmware (download link). My tablet is on the same build as yours.
unni_kmr said:
Sorry, I meant the PTV3000 firmware (download link). My tablet is on the same build as yours.
Click to expand...
Click to collapse
Yes thanks, I updated the Netgear Box even before i started trying to connect something.
Thats so sad. Such a cool feature but not usable with my prefered device.
Anyone try and the rocketfish from best buy? On sale for 30
Sent from my Nexus 7 using Tapatalk 4
marc99ch said:
Yes thanks, I updated the Netgear Box even before i started trying to connect something.
Thats so sad. Such a cool feature but not usable with my prefered device.
Click to expand...
Click to collapse
That sucks. I think we can call it typical Asus :silly:.
unni_kmr said:
That sucks. I think we can call it typical Asus :silly:.
Click to expand...
Click to collapse
Exactly...I'll probably flash a Custom Rom...and see if there's any difference.
Used it with the last unofficial cm10.w nightly and then with the official nightly from a few days ago with a rocketfish miracast reciever from best buy. I thought it was strange that it worked because people have been reporting that it doesnt work on CM at all. With the compression decreasing the quality ive just decided to use my chromecast with the new aircast app that koush is testing now. Dont really game on my android devices so didnt really see a point to get frustrated over full mirroring.
Sent from my Nexus 7 using Tapatalk 4
marc99ch said:
Exactly...I'll probably flash a Custom Rom...and see if there's any difference.
Click to expand...
Click to collapse
psychedelicNerd said:
In response to your private message asking whether I tried playing games with Miracast.
Click to expand...
Click to collapse
I shot a video of the video/audio dropping issue that occurs with my Nexus 7 2013 & PTV3000 and uploaded it in YouTube.
Sorry for the bad quality. I thought of doing this since I got a private message from a member asking me how well the gaming works with Miracast. In the video, I am playing a YouTube video first, then GTA 3 and finally camera app.
CM 12 FOR NEXUS 9 LTE
Hello fellow XDAers. This is the first time I have compiled any android build. I really only compiled it for myself because I did not see any CM12 for the Nexus 9 LTE. But I thought I would share it with you people. This thread is not going to be one of those fancy, decked out looking posts. To be straight to the point, I just compiled the Nexus 9 LTE code from github. I do not take ANY credit for any of the source, all though I will take credit for compiling it for you and bringing to you a fully functioning cm12 build for the nexus 9 LTE. Remember, as always, I am not responsible for any damage done to your device from using any of these files(Blah Blah). And now to the good part!
WARNING
If you flash this zip file and directly boot afterwards, it WILL encrypt your device if its not already encrypted. To prevent this, I have attached a non-encrypting boot.img that you need to fastboot flash directly after installing this zip file.
**ROM**
Get the latest build here. - 3-18-2015
**GAPPS** Check the lollipopalooza thread for aarch64 Gapps courtesy of craigacgomez here.
**NON-ENCRYPTING/PERMISSIVE BOOT.IMG** Download here.
Credit to the CM team as always for providing a great OS for our awesome tablets and phones.
Credit to @simonsickle for github repos
EDIT: As of atleast the 3-08 nightly for flounder, the OFFICIAL CM nightlies have LTE support built in. I do not know if this is an accident or what, but you no longer need to download LTE or WIFI specific ROMS. The roms contained at http://download.cyanogenmod.org/?device=flounder do in fact work with LTE/WIFI Nexus 9.
Sounds good! Have you thoroughly tested on your N9 LTE?
Is GPS working? This was always the problem with other ROMs I tried for the LTE
And what about charging and battery charge display? Other ROMs would charge slow, show 60% although fully charged and this kind of stuff.
A 100% working CM would be nice
Thanks
taronas said:
Sounds good! Have you thoroughly tested on your N9 LTE?
Is GPS working? This was always the problem with other ROMs I tried for the LTE
And what about charging and battery charge display? Other ROMs would charge slow, show 60% although fully charged and this kind of stuff.
A 100% working CM would be nice
Thanks
Click to expand...
Click to collapse
Hi, thanks for the reply. Right now it appears that everything is working ok. But, like you said, it seems LTE goes in and out at random times. I am working on testing out everything and hoping other people may find out whats still buggy too. All though, I am not a dev so I probably would not be able to fix it =[. But i will post more information as it is discovered.
I'm all in for testing; very surprised cm 12 wasn't ready for this already when mine arrived last week. ?
Nice, thanks and ready for testing.
0309 flashed and booted just fine. Within a few minutes the 0310 update was available, same result. Except this time mobile data was available in the OS.
Will keep at it testing, great job ty!!!
3's&7's said:
0309 flashed and booted just fine. Within a few minutes the 0310 update was available, same result. Except this time mobile data was available in the OS.
Will keep at it testing, great job ty!!!
Click to expand...
Click to collapse
Actually, if you updated to the 3-10 nightly, thats an official CM build. Which I have discovered LTE does in fact work in the nexus 9 build. And the build I posted on here (3-09) LTE worked for me, but it took a couple of reboots. Anyway, thank you for trying out my build!
bynarie said:
Actually, if you updated to the 3-10 nightly, thats an official CM build. Which I have discovered LTE does in fact work in the nexus 9 build. And the build I posted on here (3-09) LTE worked for me, but it took a couple of reboots. Anyway, thank you for trying out my build!
Click to expand...
Click to collapse
I did not find any APN (etc) related settings in the 0309 build. So a few reboots later you were able to connect to your carrier?
3's&7's said:
I did not find any APN (etc) related settings in the 0309 build. So a few reboots later you were able to connect to your carrier?
Click to expand...
Click to collapse
To be quite honest Im not sure whats going on with my nexus 9. It seems no matter what rom Im running, sometimes LTE works and sometimes it doesnt. But with mine, yes, I am able to connect to data services. It works upon boot, I dont have to do anything extra. Except the first time it booted, it took about 2 reboots for LTE to kick in. So far so good for me. Im on T-Mobile US, im not sure if that matters though. Anyway, good luck
Is there a setting somewhere that enables LTE?
Sent from my Nexus 6 using Tapatalk
trebills said:
Is there a setting somewhere that enables LTE?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I dont know what the heck is going on, but it seems you need to reboot a couple of times and when your tab boots up, dont touch it for about 20 seconds and then see if its working.
bynarie said:
I dont know what the heck is going on, but it seems you need to reboot a couple of times and when your tab boots up, dont touch it for about 20 seconds and then see if its working.
Click to expand...
Click to collapse
When I boot up my tablet, if I let it sit there until the screen turns off, it works. If i dont wait, it does not work. Its got something to do with airplane mode being enabled and I have no idea why this is happening.
trebills said:
Is there a setting somewhere that enables LTE?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Goto the settings and search for "Data" and goto the Data Connection and toggle off/on data connection a couple of times. It should work.
Has anyone installed it? How's it working out, what quirks bug problems, if any?
clockcycle said:
Has anyone installed it? How's it working out, what quirks bug problems, if any?
Click to expand...
Click to collapse
Haven't noticed anything new (good or bad)
Sent from my Pixel C using Tapatalk
Joediver53 said:
Haven't noticed anything new (good or bad)
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Did you install the OTA without wiping?
According to the notes, it mentions having wifi issues. I already have a slight random issue on N4F26O, had to go back to N4F26I. Didn't want to install the beta if it was gonna have more issues..
I have had it for about 2 weeks and haven't had any problems. WIFI seems to be OK for me.
Sent from my Pixel C using XDA-Developers Legacy app
wifi seems to be ok and also battery is really better
On my Google Pixel C tablet I see a gain of 15-25 -dBm while testing with Wifi Analyzer app meter. Tablet sitting in the same location/placement, while testing going from N4F26I, N4F26O to NPG05D.
Are you taking dBm readings at the same WiFi frequency? If your router is set to 'Auto Channel' it may 'optimize' on its own and then the readings taken at different frequencies may be misleading.
revengers said:
Are you taking dBm readings at the same WiFi frequency? If your router is set to 'Auto Channel' it may 'optimize' on its own and then the readings taken at different frequencies may be misleading.
Click to expand...
Click to collapse
Same channel same frequency. Manually set. Tested before updating, then after without changing or moving and thing. Wifi router is next to the tablet on the same desk without any obstructions. Ran it several times, same results for a couple days now.
Has anyone rooted NPG05D? I wonder if I flashfire from N4F26O if root will survive. I don't have a insecure kernel for it.. to bypass forced encryption. so that twrp can have access to write.
clockcycle said:
I don't have a insecure kernel for it..
Click to expand...
Click to collapse
Have you seen this? https://forum.xda-developers.com/pi...yflasher-make-install-custom-kernels-t3537487
Hello, I need some advise please as I am unable to get Call Screen to work on my Pixel 6 Pro. Ironically it is working on my old 3 XL lol.
When I go into the settings for Call Screen it says to download a language update then says update isn't ready. Screenshot attached.
Any Ideas please?
Can't advise but having same problem so curious to see if anyone comes up with a fix!
Sorry I don't have anything helpful to add other than that it is working for me.
What version of the phone app do you have?
pahardie said:
What version of the phone app do you have?
Click to expand...
Click to collapse
Mine is using Version 71.0.404685116-publicbeta-pixel2021 on the Pixel 6 Pro and 71.0.404685116-publicbeta on the 3 XL
Prototypeuk said:
Mine is using Version 71.0.404685116-publicbeta-pixel2021 on the Pixel 6 Pro and 71.0.404685116-publicbeta on the 3 XL
Click to expand...
Click to collapse
Thanks I have the same! My pixel 5 has the same version and same warning so least I know it's not a pixel 6 thing
pahardie said:
Thanks I have the same! My pixel 5 has the same version and same warning so least I know it's not a pixel 6 thing
Click to expand...
Click to collapse
Ah ok so I wonder what it is then?
pahardie said:
Thanks I have the same! My pixel 5 has the same version and same warning so least I know it's not a pixel 6 thing
Click to expand...
Click to collapse
Are you outside of the US? Perhaps something like that?
TonikJDK said:
Are you outside of the US? Perhaps something like that?
Click to expand...
Click to collapse
Yes I am outside the US. I'm in the UK however it does work on my Pixel 3 XL and I know they have announced it was coming to the UK so I don't believe location is the issue. Where abouts are you located?
Australia here. Same issue. No fix to report though.
Having the same issues with mine and my wipes P6P and P6 ... It's a bummer because I know other people in Australia have it working fine.
It's working on my Pixel 6 Pro in the UK. It did say it needed to download a language pack but calling my number shows call screen and it works.
The error on mine disappeared this morning randomly - I didn't do anything. Can now see the voice options as well as the demo. Could only see demo yesterday with the error popping up wrt the download.
I can see the voice options today which were not there yesterday and when someone calls it shows call screen but it still doesn't work.
Does the transcript work ok on yours?
Called myself !
No it doesn't work. Press call screen it answers but then no transcript. Can't even hang up as buttons greyed out.
Actually tried it again and it worked ok.
First time defo didn't but each subsequent time working ok.
Bit weird.
It's working for me on Pixel 6 Pro. May be there's a setting somewhere that's messed up.
With this feature only just rolling out in the UK I think they're probably still enabling it etc at the server end. It'll likely just start working soon. Fingers crossed for everyone!
pahardie said:
With this feature only just rolling out in the UK I think they're probably still enabling it etc at the server end. It'll likely just start working soon. Fingers crossed for everyone!
Click to expand...
Click to collapse
Really bizarre it is still showing the same error but it is working at the moment lol.
Haha mine is showing the download message again now. But is working .
Oh well! Glad to hear yours is working now!
I know there were a bunch of topics on this earlier in the year but I have yet to find a solution and here's the weird thing...
I have a P6 Pro (Android 12.1) coworker has a P6 (Android 13) and both of us when at home (different homes lol) will have the Wi-Fi turn off, and a few seconds later turn back on again.
The problem for both of us started about a month ago. This is way too coincidental. Neither of us had this problem before and since we are on two separate but similar phones running two different versions of Android could this be a Google connectivity related app that is causing this problem? Maybe a bad update to something?
Btw I've tried all the fixes mentioned in previous posts. Everything but a factory reset and nothing has worked. It only happens once or two a day but it's annoying
I noticed that as well during the last couple of weeks. This wasn't happening before for sure. Still no idea what's causing it.
arvylas said:
I noticed that as well during the last couple of weeks. This wasn't happening before for sure. Still no idea what's causing it.
Click to expand...
Click to collapse
Thank you. The Google Connectivity Service app that helps manage Wi-Fi was updated about a month ago.
Since we all have different versions I'm thinking this has to be app related. Nothing else makes sense
I had the same issue back on 12.1 on my P4a...and oh man did it annoy the sht outta me! I too assumed it was prolly app related. I spent ages trying to chase it down. Then google offered me $300 trade-in plus a pair of Pixel Buds for a P6a...suddenly I just stopped looking.
Hand76 said:
Thank you. The Google Connectivity Service app that helps manage Wi-Fi was updated about a month ago.
Since we all have different versions I'm thinking this has to be app related. Nothing else makes sense
Click to expand...
Click to collapse
Did you try disabling the Google connectivity from app info?
arvylas said:
Did you try disabling the Google connectivity from app info?
Click to expand...
Click to collapse
Not yet but may that later tonight
For now I tried rolling back to v53 of Google connectivity service to check if that's the culprit.
arvylas said:
For now I tried rolling back to v53 of Google connectivity service to check if that's the culprit.
Click to expand...
Click to collapse
Since it also happens with GrapheneOS which doesn't have that, its not the culprit.
I'm using the modem from qpr beta. Is anyone else with the problem using this one?
arvylas said:
I'm using the modem from qpr beta. Is anyone else with the problem using this one?
Click to expand...
Click to collapse
Modem firmware isn't relevant to wifi.
I don't want to jinx it but after happening to me every day for a few weeks it stopped. Been a week now with no changes made on my end.
This had to be a Google app. They are always getting updated and not always for the better