For a Pixel 2 with Android 11, are the default alarms stored locally as audio files? If yes, can the files be accessed through a file browser?

Album X is supposed to be a "best of" album. However, I keep on noticing very good photos that I previously missed, and am adding them to Album X in an ad-hoc manor. It would be better to add all photos not already in Album X to Album Y so that I can go through them again as a group and promote more to Album X as necessary. Is there a way to automate the process of adding the thousands of photos in Camera which are not already in Album X to Album Y? NB, as an alternative to automatically adding all photos to Album Y which are not already in Album X: Is there a way to view all the photos in Camera alongside some kind of identifier of whether they are also in Album X? Even that would make the sorting process much easier.

A couple weeks ago my Pixel XL 2 (or Pixel XL, not sure) started to have black blotches all over the screen. They grow, enlarge and eventually engulf the entire screen. Now except for a sliver on the upper right corner, the screen is pitch black regardless if it is on or off. What kind of damage is this? There had been no physical damage to the phone. As far as I can remember, the phone has never been dropped or otherwise subjected to excessive physical forces. I am trying to find the phone's IMEI, but I am not sure how to go about doing it without being able to see anything on the screen. Also when it is plugged in to my laptop via a USB-C cord, my Windows 10 recognizes the phone, but I don't see an additional drive. How should I access the files on there? Is there a way to reset the phone and clear the data?

I want to move the firmware to the phone’s memory in order to install it on the device via TWRP, since the computer does not have enough power to install the firmware in time, there is a problem with the waiting time. How I can install android 13 to pixel 2

I dont have any practical experience with rooting my phone. There is one thing that's been bugging me for a very long time: I need to be able to set a charging limit on my Pixel 2 since I dont feel like replacing the battery soon and destroying the water resistance. My question is: if I root and set a charging limit and unroot again, will this setting be erased? As I said, I am not too familiar with the risks of having my OS more vulnerable towards viruses, thus the only thing I want to do is to set the battery charging limit and then just go back to unroot. Thanks, Alex

Several times a week, the call suddenly ends and says "called ended." That's it. That's *all* the information my Pixel 2 gives me. "Call ended." Is it a cell network issue? Did the other side hang up? Did my phone think I pressed the hang up button? I cannot tell. How do I get to the bottom of why my Pixel 2 sporadically hangs up? The same thing happens to my wife's Pixel 2.

I have a Pixel 2 phone running Android which appears to have a hardware failure. The screen only shows a multi-color static and is non-responsive. Occasionally I briefly see my normal lock screen, but the screen is non-responsive and goes back to static soon. I need to get data from the device. Connecting via USB, running adb devices shows that no devices are detected. How can I copy the storage from my phone to my computer, so that I can extract the desired data?

**Background** Apparently, I have bought yet another brand new phone that is absolutely useless and has a value of zero. It is a Google Pixel 2. I would like to OEM unlock it. This option is greyed out in settings -> system -> dev.options. Therefore neither bootloader nor recovery (nor anything else that would be in any way useful) are available. I can also not flash LineageOS and am stuck with what the ****** have provided for me in their boundless wisdom and unending benevolence. It appears this is the case for many Google Pixel phones, see here , here , and here . It appears that some companies like Verizon routinely sell phones that are crippled in this way. I understand that I have most likely wasted another bunch of money on this and will not be able to use this phone with Lineage. (And therefore I am not going to use it at all.) **Question** However, before I throw it away, I'd like to make sure that there is absolutely no way to get around the OEM lock and that I understand why. How can I do this? * Is there a way to verify positively that this phone cannot be OEM unlocked? * Is there a way to verify that it's perhaps one of the infamous Verizon ones that I didn't know about before I got this? * Is there another way to try to unlock this besides in the settings (see above) or via fastboot oem unlock? **Software** ... is Android 10 from 2019, apparently. I know that this is old, but I do not care what software it has when I run it over with a steamroller. Build number is something like QP**.******.004 **Additional Information** * Some people reported that factory resets work to enable the OEM unlock option. Factory reset (System -> Reser options -> Erase all data (factory reset)) changes nothing for me. This is unsurprising, since it was new. * Some people report that some Google Pixel Phones somehow come from Verizon (see here , here , and here ); Verizon locks them and refuses to help unlocking them. Therefore, Google Pixel phones from Verizon seem to be unlockable (and as far as I am concerned unusable). I have not bought the phone from Verizon (at least not directly), I have never interacted with Verizon in any way (at least not directly), and I do not live in the US. I am therefore unsure this is actually a Verizon phone. Google's trademark obscurity, however, makes this very hard to know. * The greyed out OEM unlock option says "Connect to the internet or contact your carrier". This is a wrong and highly misleading error mesage. I assume this is a practical joke on the part of the ******* from Google. I am connected to the internet via Wifi and I do not have a carrier because I have not even a SIM in this device. * The first time the device is connected to the internet after each factory reset, I can actually switch the "OEM unlock" option. However, it doesn't actually unlock anything, it just pretends it does. After switching to fastboot mode, the device is still locked.

$ fastboot getvar unlocked
    unlocked: no
    $ fastboot getvar all
    ...
    (bootloader) unlocked:no
    ...
    $ fastboot oem device-info
    (bootloader) Verity mode: true
    (bootloader) Device unlocked: false
    (bootloader) Device critical unlocked: true
    ...

There is also no integrity warning when the device reboots, and while the "OEM unlocking" switch can be switched (leading to the apparently usual confirmation dialogues), it always says "Allow the Bootloader to be Unlocked", while it should apparently say "bootloader is already unlocked". Once I have actually tried to go into fastboot mode and do anything and then boot back into the "normal" Android ("normal" in quotation marks, cause this is about as normal as Kim Jong Un's Red Star OS), the option is greyed out again, not available any more, and says I should connect to the internet even though I am connected. * Of course:

$ fastboot oem unlock
    FAILED (remote: 'Flashing Unlock is not allowed
    ')
    fastboot: error: Command failed

(Yh, some programmer at Google or Verizon or whereever was too lazy to fix the newline in this stupid error message.) **Why would anyone end up in such a stupid situation, buying phones they cannot possibly use?** Well, I'd like LineageOS. Lineageos.org has a list of devices Lineage should work with, including Google Pixel 2. Unfortunately, for most of those, there are multiple versions. On many of these, in turn, you can, in fact, not install or run Lineage for various reasons. And as far as I can tell, it will be 100% impossible for you to know which one you get before you actually have it an try it directly. So we're stuck with wasting money.

I bought a Pixel 2 a few weeks ago and upgraded it to Android Pie, but about every three days it comes up with a notification asking me to restart (I forget the exact wording of the message). Have done this about five times now. Any idea why this is happening and if there is a fix?

I'm using my Pixel 2 (non-XL) rather sporadically throughout the day, most of the time I just keep it in airplane mode with WiFi (and WiFi Call) enabled, except 1-2 hours outside, plus 30-60 minutes of active use per day. Bought it shortly after release and so far I typically always had around 2 days of battery life per charge (varying +-6 hours or so). Now and then the average battery estimate dropped, went back up, etc. as you'd expect from a "guesstimate". However, over the last two or three weeks the estimate dropped lower and lower and this weekend I arrived at 24 hours while still dropping (even while fully idle and with full plane mode, mind you). At first, I suspected maybe my router and/or repeater (providing both 2.4GHz and 5Ghz) are acting up or confusing the phone (like constantly swapping channels). However, this seems to not be the case as neither keeping full plane mode without WiFi nor turning off 5Ghz or the repeater changed anything. In fact, I couldn't notice any significant difference between power consumption whether airplane mode is on or off (including WiFi, Bluetooth, and WiFi Call being on/off). No matter what I do, batterystats/Battery Historian (3.1 Docker Image) show an average drop of around 3-6% per hour while idle (face down). The drop is higher while used, obviously. Apps wise I don't see any massive outlier either. Only CPU tasks running repeatedly throughout the day is qcom.glink-smem-native-xprt-rpm, typically running for about 5 seconds over 5 minutes. While the phone doesn't doze all the time, it's shown to regularly be in light or full doze. I don't see any regular long wake locks except com.google.android.gms once or twice over time. However, one very odd thing that got my attention is the estimated/calculated Coulomb Charge shown in batterystats/Battery Historian (which also matches AccuBattery's estimate; assuming it does its standalone calculation). Using one example bugreport I'm having at hand right now: |Time since charging|Estimated Charge Left|Estimated Battery Percentage| |:-|:-|:-| |\+0|2615mAh|100%| |\+1h|2573mAh|97%| |\+6h|2386mAh|77%| |\+10h|2284mAh|64%| |\+10h20m|2178mAh|59% (active use)| |\+12h|2136mAh|54%| |\+18h|1987mAh|35%| |\+22h|1861mAh|19%| The last 20% would feel significantly longer than the previous percentages (as it should with the estimate being off), but it definitely doesn't last as long as 1800mAh should last in comparison (i.e. phone turning off, then only showing the static white battery screen). Two weeks ago the lower end of the scale sat at around 500mAh at 12%. Tried deep discharging twice so far, without the situation changing significantly; although that wasn't back to back). Looking for "Coulomb Charge" unfortunately didn't really reveal any useful hints so far. Anyone experienced this before? What would be the next interesting thing to look at or try? Also noteworthy I'm not eager on just wiping the phone, having to once again setup authenticator apps etc.

When I'm connected to a Bluetooth headset, it seems Do Not Disturb is meaningless. I turn it on (sometimes allowing Starred Contacts to interrupt, sometimes none) and put on my earbuds to work, alternating between listening to media and joining Teams meetings. Unknown callers, suspected spam and even my ex-wife ring right thru and interrupt the audio of my meetings. Even if I decline the call, it takes several seconds more meeting audio to return to my headset. Please help. If I'm giving a presentation and it's interrupted one more time by the phone ringing from someone I wouldn't answer even without DnD active I might do something drastic, like buying an iPhone. By the way, I still love my Pixel 2, but I'll upgrade if that will fix this travesty.

I have a Pixel 2 XL and am looking for an external monitor. If I buy a monitor that has a USB-C input and I connect the phone using a USB-C to USB-C cable, will the screen be displayed to the external monitor?

Bit of a weird setup but I have a Pixel 2 phone with offline charging disabled. Today I wanted to restore the factory image so I booted the phone into TWRP, wiped all the partitions. I then got distracted and the battery drained. Because I have disabled offline charging the battery won't charge now that the phone is off and the phone won't boot because it doesn't have enough power to switch on. I have tried starting the phone into recovery but it seems like there is not enough juice even for this. The red LED on top flashes a couple of times but the screen stays black. Any ideas how I can recover? One idea I had was to open the phone and put a charged battery from another pixel in it but this involves taking apart two phones which is a bit drastic.

My Google Pixel 2's touch screen suddenly stopped working. **The screen itself works fine and shows everything perfectly, but the _touch_ sensor is not working _anywhere_ on the phone screen!** It cannot detect my touch gestures. I was actively using my phone and noticed the battery was at 1%, so I quickly plugged it in. I was too late, however. As I plugged it in, it started to turning off due to low battery, and it did an automatic soft (proper) shutdown. With it now plugged in and charging, I turned it right back on and attempted to type my unlock password. No luck. The touch screen wouldn't respond! I held down the power button for like 10 seconds or so until it automatically did a reboot and I saw the "Google" name in color on the screen again, indicating it was turning back on. The touch screen was still totally unresponsive. I did this about 9 or 10 more times over the next 45 minutes--each time unresponsive. **How can I make the touchscreen work again?**

I failed to connect to my Pixel 2 with a broken screen with adb from MacOS in the following way: $ cd Downloads/platform-tools/ $ ./adb kill-server $ ./adb start-server * daemon not running; starting now at tcp:5037 * daemon started successfully $ ./adb shell input text 5233 adb: no devices/emulators found I use a PIN to unlock my screen and USB debugging is not enabled. As soon as, I connect Pixel 2 to my Macbook the Android File Transfer icon only shows up but I can't connect. Is there a way to copy files and settings from my phone to my laptop? Thank you in advance.

Since updating to Android 11, I've noticed some games I used to play no longer hide the navigation bar as expected. Some apps, however, work as expected. One game in question I have is Carmageddon, with the navigation bar visible on the right. I have tried: * Checking for updates (no update since 2017) * Swiping from top, left, right, bottom * Restarting phone Is there a way to restore the original behavior where this game would be able to hide the navigation bar?

i am using **google-pixel 2** phone since 2017. phone not able to start camera app and app getting crashed when i tried to open rear camera . **front camera is working fine** .i contacted google support team they said that try to clear app cache and data. i cleared camera app cache,data but no luck. how do i get my phone rear camera to working condition ? pleas help me out to get it working. thanks

I need to unlock my Google Pixel 2 XL without losing my data. I figured out the simple solution of doing a hard reset, but I can't lose all the important things on my phone because I need them for court and all of my clients of 20 years for work. I can't afford to buy any software, so I downloaded an app called Dr.Fone, but unfortunately it does not support Pixel at this time. I am not the most computer or tech-informed when it comes to these things, so I went to a local phone store and ask if they have software to do this and still no luck. I also tried to follow some YouTube tutorials and did not have luck there, either due to my lack of ability to obtain some of the resources or actions that they needed me to perform from the phone because I cannot get into the system. Is it possible to unlock Google Pixel 2 XL without losing data?

[ So when I clicked the microphone button on my Gboard, Pixel 2, it used to come up as pictures 1&2. Now, this changed today, when I click the microphone, the keyboard goes away, and screenshot #3 is what comes up. I know that this is extremely similar to https://android.stackexchange.com/questions/224089/is-it-possible-to-trigger-gboards-voice-typing-without-switching-keyboards . But I added screenshots to illustrate, and frankly, this issue is irritating me way more than it should, I don't even know why. Probably because it changed *poof* with no warning, rhyme or reason.

I have a Pixel 2 and I just installed a Android head unit in my car. I am looking for an app or script that when I get into my car and my Pixel connects by bluetooth to my head unit it turns my Hotspot on so my head unit can get internet connection. I tried IFTTT but that doesn't have an option for it. I am new to Android a bit but pretty computer savvy. Has anyone seen an IFTTT like this or know of how this can be done?