Huawei Nexus 6P :: Unlock Phone When Laying On Desk
Nov 4, 2015
Definitely enjoying the Nexus 6P after getting it yesterday. After bringing it to work that, I have to say that it's a little frustrating having to pick it up to unlock it with the fingerprint reader on the back. Coming from a Galaxy S6 this wasn't an issue since it was on the front. Besides that I'm definitely enjoying this phone more. I was thinking about getting a dock for it, but realizing it would be the and issue. This is where double tap to wake would really come in handy if a dev ends up figuring out a way to get that to work (if it's even possible).
In the last 3 weeks I have had events where the phone becomes non-responsive. What I mean is that it will not unlock by finger sensor, and the lock screen will not slide up to enter pin. The phone shows at the bottom of the lock screen the 3 icons for locked, camera and something else but, can not get it to swipe. If i reboot sometimes it does and sometimes it does not solve the problem. If it does it, I have to power off the phone, wait a few seconds and power back on.
Other times the phone gets hung up on the volume level screen will trying to adjust up or down but, not movement and locks the screen and becomes non-responsive. Also, during this time, it tends for the phone to get warm. Other times if I leave the phone alone for a few minutes, it tends to settle down and fix itself?????? I never get an "android stop working" like message either.
The phone is stock unrooted from day one from BB but, now I am over 15 days and can not return or exchanged.
I rooted my device using CF tool and now its endlessly rebooting and when i tried going into recovery mode a red warning sign over a laying android comes up and after some time it reboots , but every time it just stucked at the start animation.
So, I was trying to flash the Marshmellow factory image into my Nexus 5 following the instructions found here: [URL] ....
Everything went fine, up until I got to flash boot "fastboot flash boot C:image-hammerhead-krt16mboot.img" after that, the phone went into a boot loop for a couple of times, then, the droid with the red exclamation symbol appeared. I went to recovery, wiped data and cache. Which should fix it (right?)?
I can't go to fastboot to start over, nor anything for that matter.
I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:adb>fastboot devices ertyugg(this edited for privacy) fastboot
commands: update <filename> reflash device from update.zip flashall flash boot + recovery + system flash <partition> [ <filename> ] write a file to a flash partition
[Code] ....
Message shown :
options: -w erase userdata and cache (and format if supported by partition type) -u do not first erase partition before formatting -s <specific device> specify device serial number
dkotoric has realised this is due to using the double tap to sleep function on some launchers. Locking your device with that prevents the fingerprint scanner from allowing access for some reason. So today was my first full day with the 6P. It's a truly great device. A whole bunch of times though when I've come to unlock the device I've had to put in my pattern because it won't accept the fingerprint scanner.
The icon at the bottom of the lock screen that should be a fingerprint is just a lock symbol. If I then lock the phone again and reunlock it works as expected. Not sure if this is a software bug or some setting I've got wrong. Can't see a pattern for when it does it though. I've switched 'require pattern on restart' off which has made no difference.
Ok, so I just got my awesome new 6P. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't.
I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: [URL] ..... (wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently ...
I wrapped my Nexus One with the SGP Shield (similar to Invisible Shield, BodyGuardz, BestSkinsEver, etc.) and apparently the contacts on the Desk Dock charger have no tolerance for variance. I can only get the charge contacts to connect if I push down on the phone against the dock at a specific angle, but as soon as I left it sit by itself, it loses it.Any other suggestions for a decent dock, perhaps a landscape one? Alternatively, any thoughts on how I could make this one work? Perhaps a tiny spot of solder on the pins?
I haven't received mine yet, but probably one of the first things to do is unlock the bootloader. Does the fingerprint verification/ unlock still works with an unlocked bootloader.
I am already unlocked and rooted, but I would like to relock the bootloader assuming that I can unlock it for future updates without losing data. The Nexus 5 had a boot locker app in the App Store which allowed this, but I do not find an option for the 6 P.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader.
Last year I bought the nexus 6 and for the first time (I've had a lot of android phones) in my phone was also disabled force encryption after the bootloader unlock, twrp and root. So I decided to decrypt it because reading on the nexus 6 forum some devs suggested this to increase the phone performances.
I read that now twrp supports encryption and that Google increased the phone performance also with force encryption enabled.
I am having an issue where the touch screen seems to be unresponsive for a short time after unlock. For instance, if I unlock the phone via fingerprint, pattern, or slide the first touch doesn't respond and I have to tap whatever app or item I am trying to use. I'm using Cataclysm ROM with the most recent ElementalX kernel. Maybe it's a ROM/Kernel thing and I should try stock but just wanted to ask here.
I am having an issue with the 950s screen responsiveness and hoping a few other ow red could confirm if they are also so I know if it's a bad screen or something else.
When the phone is laying flat on a hard surface the screen is completely unresponsive. As soon as a pick it up everything is fine.
The other issue is in regards to the keyboard which seems to be hit or miss on recognizing input near the edges of the screen.
I suspect it could be the tempered glass screen protector but I don't want to remove it if others have the issue if there is a known software issue.
So just got my 6p yesterday but it seems as though ambient display although turned on is not working ND when I answer a phone call my screen stays black during the call and won't wake up.
So apparently it's because the tempered glass screen protector is covering the proximity sensor. I still have to actually test that theory out once I get a new protector but from doing some digging that most def it. Just a heads up I used the one by super shieldz so don't buy that one until they make a cut out for the sensor.
My Nexus 6P will not do anything but charge when it's plugged up to my PC. I am using the systemless root and Franco kernel r7. Other than that, it's stock. What happens when I plug my phone into my PC is the battery icon changes to charging, and that's it. The PC does not recognize the phone is plugged in, and there are no unknown USB devices in device manager. I also do not get a USB notification on my phone.
More details:
- I have done the complete drive install VIA the nexus root toolkit (both initial setup before this problem, then again when the problem surfaced) - USB debugging is enabled - I swapped cables about 3 times, no change - Tried different USB ports on PC and laptop and even ports directly connected to the motherboard. no change. - Tried on my laptop (Windows 10) and it does the same thing as the PC (Windows 10). - USB settings are set to MTP, although if I change it, it seems to get stuck on charging. I have to tap MTP about 3-5 times in order for it to say it's in MTP mode again. - Running the command adb devices in command prompt does not show anything connected.
Other than this weird issue, I have not had any problems with my phone. I also have another USB-C cable on the way, but it seems unlikely that would be the issue.
I got my brand new 6p last week on friday and am in love with it, currently testing out the battery to see how much juice I can get out of it in a normal working day. I have however noted that when i browse using 4g on chrome the phone gets warm, not too hot to hold but get noticeably warm, the top half between the camera and the fingerprint sensor and the front screen as well. I have the phone in the 'adopted' case that i ordered with it from the Google store which might be bad for heat dissipation but still wondering if other people have had their phones get warm when being used?
How to use the new Emojis which "came out" with 6.0.1? checked Google keyboard but it contained only old emoticons.whats the procedure for enabling the latest emojis
How can I get my voicemails to show up there? Does it work with Verizon? The tab only appeared after I installed Google Voice and set it up as my voicemail in the phone app settings...
It doesn't matter to me if I have to use Google Voice or Verizon's native voicemail, just seems like a cool feature.
On a related note, Google Voice regularly alerts me of Voicemails hours or even days after I get them...is that normal?
The phone apparently does not support HDMI over USB-C and I need to find a way to mirror my screen via HDMI.
My car has an HDMI input to the head unit and it was just recently found to have a bypass in it so that the HDMI will work while driving. I do not want to watch videos while driving but I do want Google maps/waze to be shown on my head unit screen as the car's standard navi is terrible.
I have tried using Chromecast but the Chromecast does not work unless the car is connected to WiFi. Using my phone as a hotspot was a workaround up until an update to the Chromecast was said to cause it to crash. So this option is out.
What I would like to do ideally is buy an HDMI miracast dongle to mirror the screen as it uses WiFi direct. If I go into settings>WiFi>menu>advanced I see the WiFi direct menu but it looks incomplete.
I did some searching and saw that there was a way to edit the build.prop on the nexus 6 to allow for miracast.
I don't get my Nexus 6P shown as a drive on Windows 10. I've installed the Google Drivers. Also I have the adb and fastboot driver. USB Debugging is enabled. When I switch to MTP, nothing happens. When I change to PTP my Nexus gets a mark in the device list but I can't install any driver manually. Even when I navigate to the location where the google drivers are located.
