Phone: Nexus 5x Operating System: Android 7.0 When I try to delete a contact in contact list of phone it displays the error message: Contacts from your read-only accounts cannot be deleted, but they can be hidden. Cancel Hide When I see the details of the contact, I cannot see the number but I can see it in the Whatsapp contact details.

So I bought new Nexus 5x with android 6.0 and everything worked fine, but when I updated to 7.1.2 suddenly wifi stoped working. (It seeks for wifi networks forever). When I go to settings I can see MAC adress which is default one 02:00:00:00:00:00. I've noticed that its common problem for phone like Nexus 5, 5x 6p and Pixels but all solutions I could find just failed. **What i have tried:** first simplest solutions they gave like pulling off SIM card, turning off phone, charging battery to 100%. - Failed Then i was trying to install other versions of Nougath 7, 7.1 , 7.1.2. Switching back to Android 6 makes wifi running again. Some people said that changing MAC adress resolved issue, so firstly I have rooted my phone. Then I have tried to use some external programs for changing MAC but they didint worked. **Problem** I am trying to change MAC manualy. I did it few times on other linux/windows machines with no issue. when i check for avalible network interfaces throught *ifconfig* it outputs bullhead:/ $ ifconfig rmnet_ipa0 Link encap:UNSPEC UP RUNNING MTU:2000 Metric:1 RX packets:843 errors:0 dropped:0 overruns:0 frame:0 TX packets:1129 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:563887 TX bytes:210944 dummy0 Link encap:UNSPEC inet6 addr: fe80::78e6:16ff:fe96:3cf7/64 Scope: Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 TX bytes:210 rmnet_data0 Link encap:UNSPEC inet addr:10.156.9.217 Mask:255.255.255.252 inet6 addr: fe80::53e3:f4d7:6ca9:be5e/64 Scope: Link UP RUNNING MTU:1500 Metric:1 RX packets:843 errors:0 dropped:0 overruns:0 frame:0 TX packets:1129 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:568878 TX bytes:210944 lo Link encap:UNSPEC inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope: Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 TX bytes:0 there is no *eth0* interface nor *wlan0*. All of those interfaces does not have mac assigned. As I have tested *rmnet_ipa0* and *rmnet_data0* are probably for mobile connection (ifconfig (rm..) down makes mobile connection off. So my question is how do I find network interface for wifi so I can try digging in it. Thanks!

I have a Nexus 5X and was in a bit of a hurry when I followed the setup steps. There was a calibrate compass wizard, which I skipped because I wanted to do this later. However, I've not figured out yet how to launch the compass calibration wizard again. I found this question on Android.SE telling about the general process, as well as this Google support article , but I couldn't figure out how to launch that wizard again. Any ideas?

I'm a deaf person with a Nexus 5X. I almost never want my phone emitting any kind of sound. When I had a Samsung Galaxy S4, there was a configuration option to mute all sounds independently of the various volume settings. Since then, Android has released their do-not-disturb mode. That doesn't really fit in with my usage because that ties in with the whole notification system. I want my phone to function as if it was not in the DND mode, just without sound. I looked into key remapping solutions to prevent accidental buttonpresses (phone holder, pants, whatever), but that doesn't prevent applications from changing the volume. e.g. Google Duo assumes that all videophone calls users will want audio regardless of the audio settings prior to opening the app. That absolutely makes complete sense, so that's why I'm asking for a lower-level way to disable the speaker. I did look at several muting-related questions, but those seem to be more of one-time actions - "I want to turn off sounds right now, but I'll adjust them later" So, the question is, as the title states, how to selectively stop the speaker from functioning that cannot be overridden by any app. How would I proceed to go about doing that on a Nexus 5X?

Recently, about 4 weeks ago, the volume on my microphone became too low for listeners. I can hear them perfectly though. I found somewhere on the internet (I can't remember where) that if I clear the system cache (see below), then the volume returns to normal. Which it did. It's happened again though. So I've cleared the cache again and again the microphone volume has returned to normal. Is there a way around this? It looks like its a software fault rather than a hardware fault. These are the instructions I followed to wipe the cache: * Power off the phone * Hold down power and the volume down button * Use the volme up/down to select "Recovery mode" and press power button * When "No command" is displayed, hold down power and press volume up. * Select wipe cache * Restart Currently on 7.1.1

I am unable to click on install button. I have made back up some of my apps. But now when I'm clicking on the install button, it's not working. Cancel button is working nicely. I purchased it 3 days ago. I didn't install any app that is related to screen brightness. I googled for this problem, I found an issue with screen brightness app. I didn't install any kind of these apps. I'm using Marshmallow 6.0.
Any suggestion please.

Currently, when we try to turn on Hotspot in Nexus 5x, then WiFi just gets disabled and only mobile data is shared over WiFi instead of already connected WiFi (broadband). Using Netshare WiFi sharing on LG Nexus 5x isn't working all that great for WiFi sharing with Mac. When Samsung Galaxy S7 and above can achieve this feat, then I guess that there should be a way to achieve the same for stock Android in Nexus 5x. Is there a way to enable wifi sharing in Android 8.1 in LG Nexus 5x when we turn on the default hotspot on? Is there a way to share WiFi in Nexus 5x on Android 8.1 using methods such as the one mentioned at https://android.stackexchange.com/questions/116508/how-do-you-enable-hotspot-wifi-sharing-on-nexus-5-android-m-version-on-sprint-t ?

Whenever I try and adb pull an installed APK from my device, it says adb: error: remote object {name} does not exist. I've tried and it works with files in /sdcard, and I definitely have access to the APK. I can also ls inside the app's install directory and it will be fine. Here is an example with Snapchat: pm path com.snapchat.android gives me /data/app/com.snapchat.android-2/base.apk ls -l /data/app/com.snapchat.android-2gives me total 153872 -rw-r--r-- 1 system system 78767561 2016-09-02 13:03 base.apk drwxr-xr-x 3 system system 4096 2016-09-02 13:04 lib drwxrwx--x 3 system install 4096 2016-09-02 13:05 oat I can stat and cat the base.apk, which proves there isn't a file permissions issue. I've restarted my phone, restarted adb, rebooted my computer, tried it with other apps, tried it with everything and nope, it's like adb just can't see it. Anything I can try or do? **Update** 1. Forgot to mention I am using adb on Windows 7. When I use cmd.exe, the above happens, but when I use git bash (on MinGW) it gives a weird error: adb: error: remote object 'C:/Program Files/Git/data/app/{apkName}/base.apk' does not exist. 2. I ended up pulling the APK through one of those WiFi file transfer apps which present a UI over a HTTP server. Based on #1, it must be a weird bug on my system/with adb where it won't properly parse a path.

I have a 3 port USB-C charger from Aukey that for the past weeks worked well with my Nexus 5X when used with an old ATX power supply as power source. I found critical reviews on Amazon (link to US website, but same type of issues on DE and IT as well) where the product stops working or even fries the phones after some time. I am using exclusively the USB-C port, the other ones cannot charge the Nexux 5X as fast. I am using the original Nexus 5X USB-C cable, not the one provided by AUKEY (it is said to be low quality). I decided to take it apart and I measured the voltage on the power pins of USB-C while charging and while the charger is powered by 12.2 V from a DC-DC power supply. The source is therefore cleaner than a car electric circuit would be. I measured with this conditions on the output port 5.10-5.38 V. The tester gives me 5.01 on a LM7805 used as calibration. Nexus 5X is not Quick charge 3 compatible, therefore it does not negotiate voltages continuously variable above 5 V, in theory it should only jump to 9 V but I haven't seen it, even if the charger could provide it. Will the 5.4 V damage my Nexus 5X, as it happened to (other) smartphones from the reviews? After all, USB tolerates up to 5.25 V only.

Google Maps reports rotating direction (0.5 rotations / minute) with stationary phone. The compass is calibrated and works correctly in compass-specific apps. https://www.youtube.com/watch?v=x6uOI5g8xbc **Steps to replicate:** After booting into Safe Mode and calibrating the compass via rapid figure-8's (or slow, or rotations on table), the direction in Google Maps slowly rotates. EDIT: I did a factory reset and, before logging in, Google Maps still has this error. I think it may be a hardware bug at this point. **Apps affected:** - Google Maps (Safe Mode and normal mode) - GPS Status (only available in normal mode) **Apps not affected:** - "Compass" (orange circle logo) - Sensors Multitool (shows correct magnetometer readings for X, Y, and Z. Confirms correct calibration) https://goo.gl/photos/SavNsaY2PyNPa17G8 **Troubleshooting steps I've tried:** - Calibrating compass - Rebooting in Safe Mode - Disabling/re-enabling Google Maps (includes data/cache deletion) **Specs:** - Nexus 5X - Android 6.0.1 - Google Maps 9.34.1

A few days ago I started experiencing a strange problem with my proximity sensor. When I answer a call and put the phone to my ear, the screen goes blank. When the call ends, the screen stays black. This (as I've discovered) happens to quite a few people. I started checking with aida64 app. When the app starts, it reports proximity sensor value of 5cm. When I cover the sensor, the value goes to 0. Then I uncover the sensor - and the value stays at 0. I switch from aida64 to any other app and back to aida64 - and the value goes back to 5cm. Alternatively, I can switch the screen off, then on again - and the value will go back to 5cm. Basically, it looks like once the value is down to 0, it won't reset for the currently running activity/app - yet it does reset when the activity is deactivated and then reactivated. I tried booting in safe mode - same results. Any ideas about trying to solve this? The phone is Nexus 5X with PureNexus 7.1.2 ROM and Magisk. Come to think of it, it may have started when I updated magisk a few days ago, but maybe not. Any suggestions on rolling magisk back a couple of versions would also be useful. *EDIT:* I uninstalled magisk altogether and the problem persists, so it can't be magisk related.

Yesterday my Nexus 5x froze and started bootlooping, it did start twice since yesterday but only for a couple of minutes. I tried going into the recovery mode, but as soon as I click the power button to enter the recovery mode, it goes back to bootloop. Also tried going into safe mode once, but that didn't help. I have already tried flashing the device with the Nexus root toolkit, but the problem still exists.

There are similar questions for previous Android releases. Is it possible in Android 8 Oreo on a stock Nexus 5X to customise the lock screen to display upcoming calendar events? Google Pixel 2(XL) allows this. (the image is of a home screen, but the question is specifically for the lock screen)

I used Wugfresh' root installer before and it worked like a charm. You can't get any OTA's with it though. Since I wanted Android 7, I wanted to unroot, install the OTA and reroot using Wugfresh' client. I already did this before when I wanted to upgrade to Android 6. Then everything went well and I was done in an hour. This time however, I'm stuck. When it needed to reboot after succesfully installing Android 7.1.1, I got set to the No Command screen. After some googling I found out that you had to go to the bootloader first, and then go to Recovery. I got that far, but now I have no clue on what to do. Rebooting from there doesn't work (obviously). It seems logical to me that I have to install TWRP, but the zip file is not there anymore to install it. Is there a way to still get this zip file on my phone while in recovery mode, and is this the solution to my problem? I also found the format option in TWRP. Does that get rid of all the TWRP stuff and bring me back to complete stock, so I can go back to rooting everything again? I'd be happy to do so, since right now I'm sitting with nothing but a dead Android. Thank you so much for your help in advance!

I have a nexus 5X phone, which needs a factory reset to fix it's infinite boot loop. The problem is that the bootloader says DEVICE STATE - locked. Is it possible to fix this?

I have a Nexus 5x that has an unresponsive and broken display (screen displays colored lines and doesn't respond to any touches) that I am trying to get files off of. I can't seem to get my computer to recognize it, presumably because you need the phone to be unlocked, but i cant get through the lock screen without touching the display. Is there any way to unlock my screen through recovery mode or something without wiping it? Thanks!

I unlocked the bootloader on my Nexus 5X phone. When I tried to boot into recovery mode, I get the standard message that my device isn't being scanned for corruption. I expected it... but then nothing. It doesn't boot, it doesn't change. I tried relocking the bootloader in an attempt to fix my mistake, but then I get a message that my device is corrupt. Still doesn't let me boot. Tried unlocking and relocking again. Same thing. If I hold the power button down long enough, I can go back to the broken Android screen. The Start option has the same problem as above. Restart bootloader just shuts the phone off for a split second, then goes back to the broken android screen. Recovery mode doesn't work as described above. I'm afraid to go with "Power off", I'm afraid it might ruin my phone. I can re-re-unlock the bootloader and go back to the "can't check for corruption" message. Re-re-locking it makes the "your device is corrupt" message again. What do I do? I'm afraid I might have already ruined the phone.

Everything I've read indicates /proc/last_kmsg used to be how, however that seems to have changed with Android 6.0 (I'm on 8.1). I've also seen reference to /sys/fs/pstore/console-ramoops for Android 6.0+, but I have no file called that. I can't ls the directory either, because apparently I don't have root shell with adb. I've tried adb bugreport, but that doesn't seem to contain shutdown logs. I've tried adb root, but I get the message: adbd cannot run as root in production builds I have a Nexus 5x that is rooted, with TWRP and Magisk. The only other suggestion I've seen is to edit '/system/build.prop' to include the line ro.debuggable=1, but I can't access that file either due to a lack of root access. I've spent a week trying to sort this out. Surely it can't be this hard to find shutdown logs?

So I just flashed suhide lite onto my nexus 5x after reading around that I could use it to bypass root detection for banking apps and android pay; however even if I set it so my banking app (halifax) can't detect root I open it up and it still states an error code about it being rooted. Anyone able to help me figure out an alternative or if I'm missing something?

Almost every time I make a phone call, the time on my phone changes. Typically it goes forward about 7 hours, but sometimes it's a little different. To fix it, I open up settings and turn the automatic time off and then on again. I did try leaving the automatic time off, but the error persists. How do I fix this?