I am trying to convert a non-JP Google Pixel 4a into a JP Google Pixel 4a by changing the model numbers. After flashing the latest stock firmware (Android 13) sourced from [the official website](https://developers.google.com/android/images) , I installed [Magisk v29.0](https://github.com/topjohnwu/Magisk/releases/tag/v29.0) and rooted my Pixel by following [this guide](https://thedroidwin.com/root-android-magisk) . [Rooting using Magisk] 0. Enable Developer Settings 1. Enable USB Debugging 2. Enable OEM Unlocking 3. Unlock Bootloader

fastboot flashing unlock

4. Extract boot.img

unzip sunfish-tq3a.230805.001.s2.zip
cd sunfish-tq3a.230805.001.s2
unzip image-sunfish-tq3a.230805.001.s2.zip
cp boot.img /run/user/1000/gvfs/mtp:host=***/'Internal shared storage'

5. Patch boot.img 6. Boot using patched boot

adb reboot bootloader
fastboot boot patched_boot.img

7. Install patched_boot using Magisk Now that my phone is rooted, I accessed protected system files to overwrite using [this article](https://thedroidwin.com/how-to-enable-osaifu-keitai-in-non-japanese-pixel-devices) . 1. Enable root access

adb shell
su

(Tap 'ok' on Pixel screen) 2. Extract devinfo.img

dd if=/dev/block/by-name/devinfo of=/sdcard/devinfo.img

3. Copy devinfo to PC

cp /run/user/1000/gvfs/mtp:host=***/'Internal shared storage'/devinfo.img ./devinfo.img

4. Open the file using the hex editor

ghex devinfo.img

I am supposed to find my phone's model number and replace it with the Japanese version's, but all I see is 16 bytes corresponding to "ANDROID-BOOT!..." That's literally the only thing in the file. Is this method not universal for all Pixels? What went wrong?

My Pixel 8 seems to be stuck thinking that an external monitor is still connected, despite having disconnected it hours ago. My friend let me connect my Pixel 8 to his portable monitor via USB-C to try it out. That worked fine and then I disconnected it. But now, hours later, I still see the external display icon in the top bar and I see "External Display" listed as "on" under "Other devices" in Settings > Connected devices. Beyond this, there are other oddities: I get no sound from my phone when I play videos (because it's trying to play sound on the phantom display?). When I take screenshots, I get two at a time (one of the phone screen, one of the phantom display?). As far as I can tell, there is no way to tell the phone that it's disconnected. Tapping on "External Display" takes me to a screen that lets me change the rotation on the external display and shows its resolution, but there's no control to disconnect. Long pressing, swiping, etc on "External Display" do nothing. I don't see any way to make the phone realize the display is not connected. I've tried a few other things to try to fix it: - Connecting my phone to my PC with a different USB-C cable - Connecting to a monitor of my own with USB-C to DisplayPort (although, the phone doesn't recognize this monitor) - Plugging a USB-C cable in to the phone with nothing on the other end - Unplugging the USB-C cable - Turning airplane mode on and off - Locking/unlocking I haven't tried restarting yet, because it seems crazy that my phone is stuck thinking it's got a display attached when there is literally nothing connected.

I just updated my OG Pixel 1 to Android 10. I normally use light mode (not dark mode), but my phone just hit the threshold to turn on battery saver mode, and now it has forced my phone into dark mode. I can't toggle this in settings while battery saver is on, and I don't see any settings in battery saver to prevent this force theme change. I find it incomprehensible that this wouldn't be an option, given that there are plenty of phones (like the OG Pixel) that still use LCD screens, and thus whose screen colors don't affect the battery usage. Are there any settings, hidden or otherwise, that prevent dark mode from activating during battery saver on Android 10?

> Tip: To check estimated battery capacity, tap Battery and then Battery health and then Battery capacity. > Battery health assistance [reduces] the battery’s maximum voltage in stages. It starts at 200 charge cycles and continues gradually until 1000 charge cycles. \- [Understand your Pixel battery](https://support.google.com/pixelphone/answer/15738128?hl=en) Battery health assistance is a new feature, introduced with the Android 16 update. On Pixel 9a (the newest Pixel) battery health assistance is turned on by default, and cannot be turned off. On earlier models, it is possible to turn off battery health assistance.[*] This can allow the battery to hold a larger charge (higher mAh), while degrading faster. The rise in mAh would be visible through Android API's and third-party apps. In this case, would the "estimated capacity" rise accordingly? Or, does the system appear to prevent "estimated capacity" from rising, even when the maximum mAh rises? I suppose it _could_ set "estimated capacity" using the maximum mAh obtained without exceeding the voltage limit that _would_ be imposed by battery health assistance. Even if battery health assistance has been turned off. I note the "battery health status" (not available on all models) is defined as whether "remaining battery capacity" is below 80% or not. I have access to a Pixel 8a (99% estimated capacity) and a new Pixel 9. [*] The help page does _not_ comment how this feature is related to the Pixel 6a "appeasement" payments and mandatory Android 16 update . The mandatory programme for Pixel 6a reduces battery capacity after 400 cycles, not 200 (if it has the "impacted" model of battery). Also, the mandatory programme does not mention further progressive reductions.

I have a Google Pixel 6a (bluejay) phone. On this phone camera makes shutter sound when I take a photo. I have looked up the phone by IMEI by going to https://store.google.com/us/device-authenticity?id=[IMEI] URL and it shows "Intended region: IN,JP". I have previously installed LineageOS and rooted it to remove the files /product/media/audio/ui/camera_click.ogg /product/media/audio/ui/camera_focus.ogg, /product/media/audio/ui/VideoStop.ogg and /product/media/audio/ui/VideoRecord.ogg. This removed the sound, but because of the root banking applications complained, so I reinstalled the system to CalyxOS without wiping. Now I want to remove the same .ogg files without rooting the phone. I have downloaded https://release.calyxinstitute.org/bluejay-factory-25608200.zip file linked from the page https://calyxos.org/install/devices/bluejay/linux/ . It is an archive with all partition images. Inside an archive there is another archive bluejay-bp1a.250505.005/image-bluejay-bp1a.250505.005.zip which I unpacked. This archive in turn contains product.img file. I unpacked product.img by running unzip image-bluejay-bp1a.250505.005.zip product.img. I confirmed that product.img contains the files media/audio/ui/camera_click.ogg and similar. I tried to mount the image and got this error:

# mount -o loop product.img /mnt/
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
# dmesg | tail -1
[360861.911279] EXT4-fs (loop0): couldn't mount RDWR because of unsupported optional features (4000)

I ran e2fsck -E unshare_blocks product.img and then tried to mount again: Then the image mounted successfully with mount -o loop product.img /mnt/. I then modified the image:

cd /mnt/media/audio/ui
mv camera_click.ogg camera_click.bak.ogg
mv camera_focus.ogg camera_focus.bak.ogg
mv VideoStop.ogg VideoStop.bak.ogg
mv VideoRecord.ogg VideoRecord.bak.ogg
cd /
umount /mnt

Then I rebooted the phone to fastboot with adb reboot fastboot and flashed the modified product.img to both slots:

# fastboot flash --slot=all product product.img
Resizing 'product_a'                               OKAY [  0.019s]
Sending sparse 'product_a' 1/7 (262112 KB)         OKAY [  6.272s]
Writing 'product_a'                                OKAY [  1.279s]
Sending sparse 'product_a' 2/7 (262128 KB)         OKAY [  6.243s]
Writing 'product_a'                                OKAY [  1.227s]
Sending sparse 'product_a' 3/7 (262120 KB)         OKAY [  5.996s]
Writing 'product_a'                                OKAY [  1.313s]
Sending sparse 'product_a' 4/7 (262120 KB)         OKAY [  5.941s]
Writing 'product_a'                                OKAY [  1.199s]
Sending sparse 'product_a' 5/7 (262124 KB)         OKAY [  5.985s]
Writing 'product_a'                                OKAY [  1.262s]
Sending sparse 'product_a' 6/7 (262104 KB)         OKAY [  5.968s]
Writing 'product_a'                                OKAY [  1.318s]
Sending sparse 'product_a' 7/7 (161293 KB)         OKAY [  3.752s]
Writing 'product_a'                                OKAY [  0.967s]
Resizing 'product_b'                               OKAY [  0.014s]
Sending sparse 'product_b' 1/7 (262112 KB)         OKAY [  5.982s]
Writing 'product_b'                                OKAY [  1.258s]
Sending sparse 'product_b' 2/7 (262128 KB)         OKAY [  5.930s]
Writing 'product_b'                                OKAY [  1.256s]
Sending sparse 'product_b' 3/7 (262120 KB)         OKAY [  5.992s]
Writing 'product_b'                                OKAY [  1.274s]
Sending sparse 'product_b' 4/7 (262120 KB)         OKAY [  5.932s]
Writing 'product_b'                                OKAY [  1.247s]
Sending sparse 'product_b' 5/7 (262124 KB)         OKAY [  6.002s]
Writing 'product_b'                                OKAY [  1.252s]
Sending sparse 'product_b' 6/7 (262104 KB)         OKAY [  6.221s]
Writing 'product_b'                                OKAY [  1.293s]
Sending sparse 'product_b' 7/7 (161293 KB)         OKAY [  4.136s]
Writing 'product_b'                                OKAY [  0.917s]
Finished. Total time: 100.988s

However, after rebooting the phone, the camera still clicks. The files are also still there:

$ adb shell
bluejay:/ $ ls /product/media/audio/ui/camera_click.ogg
/product/media/audio/ui/camera_click.ogg

/system/product is a symlink to /product. Why the files were not modified? How can I still remove these files?

[Android 11](https://en.wikipedia.org/wiki/Android_11) came out in late 2020, when most home networks use WiFi. After searching for hours, I have been unable to find a built-in way of transferring files from my Windows PC to my Android Pixel (and ideally the reverse, too) without downloading a special app from the Play Store. This is shocking to me. Is it really the case that Android doesn't natively support WiFi file transfer? [I'd rather not need to search for (and decide whether I trust) a third-party app. And I'd certainly rather not use a physical cable for file transfers like it's 1990.]

I just switched from an older Samsung phone to a Pixel 9 running Android 15. I noticed that the timestamp on each notification shows a relative time ("43m") rather than the wall-clock time ("07:22”). Is there a setting (or 3rd party app) to change this behavior? In particular, I'd like to be able to see exact time of events more than an hour ago, which now just show up as e.g. "2h" - the loss of precision is really annoying.

I want to swap Recent Apps and Back button and keep Home in a middle. Is this possible? All other forums says: "buy Samsung" or "deal with it"

On my Pixel phone, apps will download on Play Store, but once the download completes, it doesn't install. After some time, there's a notification from the Play Store that says > Google Play isn't responding. Try again in a few minutes, and if the problem continues, get help troubleshooting. (Error code: 927) Usually, if I restart the phone, the apps can be installed, but if I wait a few hours, I have to repeat the process. Does anyone know of a way to fix the issue permanently?

Just under a year ago, I changed carriers due to carrier unlock policies. The provider I switched to I was able to get the Pixel 7 Pro on a payment plan (2 years). With it being a Pixel, I thought at the time all Pixels were OEM unlockable. Man was I wrong, not only am I stuck paying off this phone for 2 years, but without carrier unlock first that can't happen. I know in every other device that If I issued a certain adb disable command, it bypassed that. Is there not something similar I can do to get OEM unlock without carrier unlock? Any help is much appreciated.

I have forgotten my Google Pixel 7's login pattern. There is no way to "Reset Password" or change it to fingerprint login or PIN. - Any way to switch it to alternative login method? - Any way to get my photos back? The photos are all that I want. (Photos were not uploaded to cloud)

## Situation I have an old phone, it's been replaced, but it still has some photos on I want to recover. From the symptoms I presume it must be a hardware fault, and I am wondering what options are available to me. I have a friend who works as an embedded engineer who is willing to help me try get the photos off of it. The current possibilities they could think of are: - Buy a cheap new screen to connect to the phone to see if we can get the UI back - Attempt to connect via the JTAG pins and execute a script to extract the data Are there other options? Or should we go with one of these? ## More information If it's relevant, the phone is a Pixel XL. A possible silver lining is I was running LineageOS, so I unlocked the bootloader and was never able to re-lock it. The symptoms at the time of death were: - Phone would randomly restart every few weeks - This got more and more frequent - One day the phone restarted and never turned back on - If I held the power button to turn it back on, the phone vibrated yet the screen never turned on - When plugged in the red light didn't appear even though it was drawing Watts - Forced resets (holding power and volume down button for 30+ seconds) sometimes caused a vibration but nothing ever appeared - Plugging it into a laptop resulted in no devices being visible to the laptop (presumably I needed to enable file transfer via the UI which wasn't possible) It's since sat in a box for 2 years and now there is no vibration whatsoever, but it does still draw current when charging. (I contacted multiple places about data recovery in the last couple of years but never received a response.)

I am interested in understanding the charging capabilities of the Google Pixel 9a. Specifically, I would like to know the maximum wattage it supports for both wired and wireless charging.

Pixel phones (both older Qualcomm and newer Google Tensor) are known for very good camera algorithm. What I have heard the camera chipset (hardware) is similar to other phones, but the algorithm is what makes quite significant difference. Which part of the software stack is doing that algorithms? Is it only [Pixel Camera app](https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera) or is there some other firmware? I'm asking if I reinstall stock Android with [LineageOS](https://lineageos.org/) whether I loose this functionality. Also, I suppose Pixel Camera app is installable on LineageOS. I'm asking specifically about Google Pixel 5 (redfin) and 6 (oriole), but it can be considered as a general question about all Pixel phones. I also suppose this is the only functionality I could use when migrating to LineageOS (I've had good experience with LineageOS support on other phones).

I am a complete newbie to AOSP and I'm having trouble building and flashing android kernel for Pixel 8. I've been trying to follow [Building Pixel Kernels](https://source.android.com/docs/setup/build/building-pixel-kernels) instructions, but I'm experiencing some issues. I think my problem is that **I don't know which platform manifest branch to use with which kernel manifest branch.** - When I try to [flash the device using flash.android.com](https://source.android.com/docs/setup/build/building-pixel-kernels#flash_the_device_using_flashandroidcom) , there are no instructions on which platform and kernel combination is supported for Pixel 8 device (there's [a table](https://source.android.com/docs/setup/build/building-pixel-kernels#supported-kernel-branches) but it only has information regarding Pixel 6). I tried flashing git-aosp-main-with-phones, but after flashing the kernel, Pixel 8 will not boot correctly. I built the kernel by repo init & sync -ing android-gs-shusky-5.15-android14-d1 branch from android kernel manifest. I followed [the guide](https://source.android.com/docs/setup/build/building-pixel-kernels#download_and_compile_the_kernel) from the same instructions mentioned above for fetching kernel source, building it, and flashing it. But the device only displays android logo and after a few minutes, kernel panics. - I decided to try fetching and building the platform myself, and I tried following combinations: - platform manifest android-14.0.0_r27 and kernel manifest android-gs-shusky-5.15-android14-d1 - results: kernel panics after a couple of minutes - platform manifest android-14.0.0_r6 and kernel manifest android-gs-shusky-5.15-android14-qpr1 - results: kernel doesn't panic, but Pixel 8 displays Google logo and doesn't proceed If someone could point me to a working platform and kernel combination for Pixel 8, (or if I'm doing something else wrong) it would be extremely helpful!

I'm fairly new to the Android platform so hopefully this is a silly question, but since I've had my Pixel (Pixel 1, Android 8.0.0), it's been giving me notifications for alarms I set in the Clock app two hours prior to their occurrence (disregard actual time in the screenshot). Note that I _do not want to delete the alarm_, just this notification about it. . I know this isn't a *huge* issue, but it's just more annoying notification clutter that I don't want. What's weird is, I've apparently found the settings to change this behavior - but the toggle is disabled and I can't modify it. Is there another way to do this that I'm missing, or a way to enable that toggle?

How do I re-flash both partitions of a Google Pixel 6 Pro device in one go? If I follow the instructions at https://developers.google.com/android/images , I have to: 1. re-flash the first, default partition (a or b) using flash-all.bat 2. return to the bootloader (which means either (A) turning the device off after it automatically reboots and booting back into the bootloader using the hardware buttons or (B) doing a "false setup" of the device (after it automatically reboots) and returning to the bootloader via Android's Developer Options screen and the adb reboot bootloader command 3. set the inactive partition to the active partition using fastboot set_active a or fastboot set_active b 4. re-flash the second, remaining partition using flash-all.bat Is there a way to combine these re-flashing steps to make re-flashing both partitions less troublesome? (Note: My goal with re-flashing both partitions instead of one is to eliminate malware, so simply nuking and regenerating both partitions from scratch would also be a workable solution, but I don't know how to do that either.)

I am building a kernel for a google pixel 5 (first time, guides here have been a huge help!). **Getting to the issue:​** I'm trying out the following steps as they seem to be tailored to what I'm doing and using menuconfig cause lots of issues. https://groups.google.com/g/android-building/c/6HPwJloQkP8/m/oopcu67nAQAJ (response by Droid SMU with the step by step). Now, after running ./build_redbull.sh from the top directory, the following issue appears: INSTALL techpack/video/msm/msm-vidc.ko DEPMOD 4.19.135 ======================================================== Building external modules and installing them into staging directory + make -C private/msm-google-modules/wlan/qcacld-3.0 M=../msm-google-modules/wlan/qcacld-3.0 KERNEL_SRC=/local/home/bd/android/kernel/private/msm-google O=/local/home/bd/android/kernel/out/android-msm-pixel-4.19/private/msm-google CC=clang HOSTCC=clang LD=ld.lld HOSTLD=ld.lld HOSTLDFLAGS=-fuse-ld=lld NM=llvm-nm OBJCOPY=llvm-objcopy DEPMOD=depmod make: Entering directory '/local/home/bd/android/kernel/private/msm-google-modules/wlan/qcacld-3.0' make -C /local/home/bd/android/kernel/private/msm-google M=../msm-google-modules/wlan/qcacld-3.0 modules WLAN_ROOT=/local/home/bd/android/kernel/private/msm-google-modules/wlan/qcacld-3.0 MODNAME?=wlan CONFIG_QCA_WIFI_ISOC=0 CONFIG_QCA_WIFI_2_0=1 CONFIG_QCA_CLD_WLAN=m make: Entering directory '/local/home/bd/android/kernel/private/msm-google' make: Entering directory '/local/home/bd/android/kernel/out/android-msm-pixel-4.19/private/msm-google' /local/home/bd/android/kernel/private/msm-google/../msm-google-modules/wlan/qcacld-3.0/Kbuild:48: ../../../../../aosp_groups_version//local/home/bd/android/kernel/private/msm-google-modules/wlan/qcacld-3.0/configs/default_defconfig: No such file or directory make: *** No rule to make target '../../../../../aosp_groups_version//local/home/bd/android/kernel/private/msm-google-modules/wlan/qcacld-3.0/configs/default_defconfig'. Stop. make: *** [/local/home/bd/android/kernel/private/msm-google/Makefile:1661: _module_../msm-google-modules/wlan/qcacld-3.0] Error 2 make: Leaving directory '/local/home/bd/android/kernel/out/android-msm-pixel-4.19/private/msm-google' make: *** [Makefile:146: sub-make] Error 2 make: Leaving directory '/local/home/bd/android/kernel/private/msm-google' make: *** [Makefile:26: all] Error 2 make: Leaving directory '/local/home/bd/android/kernel/private/msm-google-modules/wlan/qcacld-3.0' Click to collapse I checked the Kbuild line 48 mentioned (make line) and it looks like this: 48 include $(WLAN_ROOT)/configs/$(CONFIG_QCA_CLD_WLAN_PROFILE)_defconfig The arguments are: WLAN_ROOT := drivers/staging/qcacld-3.0 CONFIG_QCA_CLD_WLAN_PROFILE ?= $(WLAN_PROFILE) What is worrying me is also the double // in the path aosp_groups_version//local (the make line). ​ **The question:​** I tried looking around in the forum but found nothing similar, has someone maybe encountered this? Or how would I go around trying to fix/debug a problem like this?

Where are the device mics on the Pixel 3a?

I've seen multiple posts on Reddit from Pixel 8 Pro users, claiming that the December Feature Drop for Pixels enabled an 80% battery charge limit feature. The setting looks like this: " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> Does the regular Pixel 8 not support this feature? My battery settings look like this: " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy">