yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] Doktor M@buse:
Add / Modify these registry settings on your device:

REGEDIT4

[HKEY_CLASSES_ROOT\.mp3]
"PerceivedType"="audio"
@="MP3File"

REGEDIT4

[HKEY_CLASSES_ROOT\MP3File]
"EditFlags"=dword:00010000
@="MP3 Format Sound"

[HKEY_CLASSES_ROOT\MP3File\Shell]

[HKEY_CLASSES_ROOT\MP3File\Shell\Open]

[HKEY_CLASSES_ROOT\MP3File\Shell\Open\Command]
@="wmplayer.exe \"%1\""

[HKEY_CLASSES_ROOT\MP3File\DefaultIcon]
@="wmplayer.exe,-2002"

[HKEY_CLASSES_ROOT\MP3File\Shellex]

[HKEY_CLASSES_ROOT\MP3File\Shellex\ContextMenuHandlers]

[HKEY_CLASSES_ROOT\MP3File\Shellex\ContextMenuHandlers\{E88B4A18-6F77-4bb6-8E0D-DCD4B1F8F1DA}]
@="Use as ringtone"
"DelayLoad"=dword:00000001

[HKEY_CLASSES_ROOT\MP3File\Shellex\EventSoundHandlers]

[HKEY_CLASSES_ROOT\MP3File\Shellex\EventSoundHandlers\{245F94CF-DD9C-46F9-B4C8-D2B14A877893}]
@="XME EventSound Player"
[Touch Diamond, MDA Compact IV General] Zida2k:
WOW thank u homie is worked THAAAAAAAANKS
[Android Head-Units] ontherocks62:
I see a plethora of HUs with the following processors marked on their boxes and units. Googling doesn't lead to any details about the manufacturer and or its official specs.

I have put down some I could find by Googling. Can anyone help to provide the details of the missing ones

T2 - Allwinner https://www.allwinnertech.com/uploads/pdf/20190404102543df.pdf

T3 - Allwinner https://www.allwinnertech.com/uploads/pdf/2021060915285353.pdf

T5 - Allwinner https://www.allwinnertech.com/uploads/pdf/20210609152941fe.pdf

T7 - Allwinner https://www.allwinnertech.com/uploads/pdf/2019071117200830.pdf

T3L

TS7 - alps

TS8 - alps

TS9 - alps

PX2 Rockchip http://rockchip.fr/Rockchip PX2 TRM V1.0.pdf

PX3 Rockchip https://rockchip.fr/PX3 datasheet V1.3.pdf

PX4 Rockchip

PX5 - Rockchip https://rockchip.fr/PX5 datasheet V1.1.pdf

PX6 - Rockchip

PX30 - Rockchip https://rockchip.fr/PX30 datasheet V1.3.pdf

UIS7862 - UniSoc

UMS512 - UniSoc
[Android Q&A, Help & Troubleshooting] darknotfound3:
Hi, iv'e recently installed blissos on my 2 in 1 PC and after that i tried to connect a pair of heaphones with the jack but it doesn't work. Can someone help me?
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, @darknotfound3 Welcome to XDA! I hope you'll always get the support you require.

However, prior to your next posting besides the XDA Forum Rules please read all the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved your thread to Android Q&A.

Regards

Oswald Boelcke

Senior Moderator
[Sony Xperia XZ Premium Questions & Answers] bk37:
Hi, after having tried many custom rom I went back to stock using newsflasher as I did many times before. The problem is that the phone cannot find any wifi network. I tried installing a custom com non stock based and the wifi is working. So I think the problem is software related. What can I do? I need to use a stock based rom. Is there a file I need to reflash in newsflasher?

P.S. I have flashed the stock rom file using the drm backup guide
[Xposed General] @Zainullah:
Xposed
[Xposed General] ZG_DEV:
Welcome to XDA world of developers 👨‍💻🌎

Please introduce yourself in Introductions forum !
[General Questions and Answers] vanishu:
how can i create from google images a send to printer option

so basically - now i have to right click a picture-click save as- name it- then click beam- then wait for the fone to find my bluetooth printer then tap it

so ideally- id love to see a pic then simply right click/menu and see a beam option-thus skipping all those other steps

any thoughts? theres gotta be a way to send the beam.exe link from registry into the right click menu when you click on a picture in pocket ie
[Android Builders Collective] tablet_seeker:
Target/Variant: android 13 .0 / treble_arm64_bvN

Issue: Copying files to /data/data or /data/media during build so they're visible to AOSP File Manager after boot.

Documented Solution: I first copied my files folder to /system during build with:

PRODUCT_COPY_FILES += $(call find-copy-subdir-files,*,files_folder,system/files_folder)

(this works)

Then I copy a file from /system/files_folder to /data/data or /data/media by adding this to system/core/rootdir/init.rc in the post-fs-data section:

copy /system/files_folder/file.txt /data/media/file.txt

(this works too)

Inside AOSP, with a root file explorer, I can see the files are copied correctly, but don't show up in the AOSP File Manager at Android/data , Android/media or Android/obb

Issue 1.1: Installing APK (Magisk App) to /data during build

Documented Solution:

LOCAL_MODULE_PATH := $(TARGET_OUT_DATA)

Adding this local module path to the Android.mk of the app is supposedly the most common way to install apks in /data.

But after including the above code, the app is not visible in the launcher, and no install files can be found anywhere. (Without the LOCAL_MODULE_PATH line it installs fine in /system)

Any tips or hints would be awesome. Thanks.🙏
[Xiaomi 13] buralardayim:
Hello. Anybody can use card emulator pro with fuxi?

I was using xiaomi mi mix 2 before. card emulator pro was working great. I bought Xiaomi 13 and I follow all the steps correctly, but my cards cannot be copied. please help.

xiaomi 13 global version, xiaomi.eu stable rom 10.0.31.0.tmccnxm, magisk rooted.
[Xiaomi 13] Aquariuslt:
met the same issue.

(but I havent try on other xiaomi phone)
[Xiaomi 13] buralardayim:
nfc still create random numbers every time...
[Xiaomi 13] pospa38:
Mi mix 2 ends on android 9, it means it has got unlocker vendor for R/W. Devices which is Launched with android 9+ has locked vendor and magisk root cannt write ID to nfc folder. You must create magisk module in cardemulator app and flash zip file module in magisk. Magisk module you create in card emulator with 3dots in card and button "create magisk module" after reboot your device it should work correctly. You can flash only one module from cardemulator but dont worry this one module of one card works on all your card in emulator. Try it .
[Xiaomi 13] buralardayim:
Thanks for reply. İ tried but unfortunately it doesn't work... I applied all steps by app Creator. Any advice for me? Every time changing NFC serial number
[Xiaomi 13] igunisu_mac:
According to the developer of the app "card emulator pro", you should use kernel SU instead of magisk on xiaomi 13 series(I haven't tested yet).
[Xiaomi 13] buralardayim:
I'm using ksu now, trying immediately
[Xiaomi 13] buralardayim:
it's working, thanks! i tested other phone seems working but door nfc reader can't read my phone. i dont understand.
[Xiaomi 13] igunisu_mac:
Sorry, no clues here. I haven't tested yet, still on MIUI.

Maybe you can check the help docs, supposedly it was updated recently.

BTW, here is what the developer said "Xiaomi 13 series have to use kernel SU to work, magisk doesn't support odm partition mounting, please see the help document."
[Xiaomi 13] buralardayim:
where can i read that help inst.?
[Xiaomi 13] igunisu_mac:
In the app, tap the three dots, and there is a "help and feedback".
[Wear OS Q&A, Help & Troubleshooting] callumw:
Hi

I have a Galaxy Watch 5 LTE and I always use it with WiFi on, Bluetooth off, location off and no LTE SIM configured.

Basically I want it as a WiFi device only.

Since the last SW update a week or so ago (R915FXXU1BWH3) I noticed it's now auto-activating the bluetooth, usually late at night.

On my phone I use Tasker a lot. Some of what I do with Tasker is using NFC tags to enable BT to connect to specific audio devices like headphones, BT speakers, motorbike helmet etc and set volume/screen/app profiles depending on what I'm connecting to. Once disconnected it turns BT off on the phone and resets to a default "home" volume/screen profile ready for a new connection.

But with the watch auto-enabling BT, it hooks into the phone preventing it from switching BT off which would let it reset to the "home" profile (and allow it to connect to a new device) until I manually switch it off on the watch to "release" it.

After the update I had to reset a lot of setting changes... lots of stuff turned back on that I had set off, so it looks like it had updated a lot.

e.g. Developer mode was gone, so I had to tap tap tap to re-enable it again. FAIK it might do that every time it updates, but I only noticed it this time while digging about resetting everything.

I got it all reset back to the way I like it, but the BT doesn't persistently stay off.

Anyone know how I can get it to stay off?

Model: SM-R915FZSABTU

SW: R915FXXU1BWH3

One UI: 5.0 Watch

System version: 1.5

Wear OS: v4.0
[Google Pixel 8 Pro] roirraW "edor" ehT:
Pixel 8 Pro [Husky]

​

July 1, 2024

:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Android Flash Tool

flash.android.com

Google Pixel Community

Android Security Bulletins | Android Open Source Project

source.android.com

Here there be dragons. 🐉 I am not responsible for anything at all. 😹

VERY IMPORTANT - On the Pixel 8/Pro, we use Magisk to patch init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition.​

Spoiler content hidden.

INDEX

:​

Post #2 - ADB/Fastboot & Windows USB Drivers | Unlocking Bootloader

Post #3 - Full OTA Zip method

Post #4 - Factory Image / Android Flash Tool method

Post #5 - Play Integrity / SafetyNet

Post #6 - Other, most important resources

Post #7 - My personal advice for how to get your device back up and running as you had it before a factory reset

Post #8 - Blank

Thank you to the following users, who have all contributed greatly to my knowledge of Pixels since I came back to XDA a year ago after a few years of mostly inactivity. Apologies if I miss anybody. In alphabetical order:
[Google Pixel 8 Pro] roirraW "edor" ehT:
ADB/Fastboot & Windows USB Drivers | Unlocking Bootloader

​

ADB/Fastboot & Windows USB Drivers:

​

Unlocking Bootloader

:​

How to Root the first time / aka How to unlock the Bootloader

:

Unlocking the bootloader will factory reset your device. There is no way around this. I highly suggest never re-locking your bootloader once you unlock it. If you do ever re-lock the bootloader, only do so after restoring the phone to 100% stock by using the latest Pixel 8 Pro Factory Image or Official Google Android Flash Tool.

Verizon variants:

T-Mobile and AT&T variants:

The direct-from-Google (or other retailers who aren't U.S. Carriers), the factory Carrier Unlocked Pixels:

Spectrum:

The rest of the world's carriers:

Other than trying the things I mentioned above, there is nothing else that anyone on XDA can do to help get OEM unlocking to be ungrayed.

Unlocking Bootloader

(required in order to root)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Rooting or updating using the (preferred) Full OTA Zip method

​

These days I recommend this Full OTA Zip method instead of the Factory Image, for both rooting and updating each month.

NOTE that as @Lughnasadh and @badabing2003 have previously found and reported, both the factory image method using Flash-All.Bat, and the Official Google Android Flash Tool (webpage) cause only the most recently flashed slot to boot. If you want both slots to be bootable, you want the Full OTA Zip method a couple of sections down in this post.

These three instructions only apply if you're already rooted and updating from one firmware version to another:

Made sure all Magisk Modules have been updated.

Disable all Magisk Modules.

UNhide

Magisk!

Always use the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers.

Unzip the Platform Tools.

[you don't normally have to manually switch slots - this is just an FYI]

If you ever manually need to switch slots, then from running Android:

adb reboot bootloader
fastboot --set-active=other
fastboot reboot

[you can also follow all of these Full OTA Zip method instructions without a locked bootloader - just ignore anything having to do with Magisk or init_boot.img]

Full OTA Zip method

:
[Google Pixel 8 Pro] roirraW "edor" ehT:
Rooting or updating using the (not ideal) Factory Image method

​

These days I recommend the Full OTA Zip method in the post above instead of this Factory Image method, for both rooting and updating each month.

NOTE that as @Lughnasadh and @badabing2003 have previously found and reported, both the factory image method using Flash-All.Bat, and the Official Google Android Flash Tool (webpage) cause only the most recently flashed slot to boot. If you want both slots to be bootable, you want the Full OTA Zip method a couple of sections down in this post.

These three instructions only apply if you're already rooted and updating from one firmware version to another:

Made sure all Magisk Modules have been updated.

Disable all Magisk Modules.

UNhide

Magisk!

If you are going to use the Official Google Android Flash Tool, then skip the steps I indicate with FAB(Flash-All.Bat).

If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:

Deselect Wipe

Deselect Force Flash all partitions (which will also wipe)

Deselect re-lock bootloader

Always use the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers.

Unzip the Platform Tools.

[requires an unlocked bootloader for updating via this factory image method, and for the Full OTA method if you're rooting]

Factory Image / Android Flash Tool method

:
[Google Pixel 8 Pro] roirraW "edor" ehT:
My personal advice for how to get your device back up and running as you had it before a factory reset

:

I use Nova Launcher Prime, so I do backups anytime I change my home screen or app drawer/tabs setup, so widgets and app icons and other Nova-specific configurations are easier to restore.

Go to Android Settings and use Settings' search box for Backup. Make sure that your Google account is set up to backup your apps (and app data for the apps that developers have configured to use Google's Backup API). Make sure things are backed up. Note, this doesn't backup the apps themselves, only the list of apps, so only applies to apps installed from the Play Store. As I said in parentheses, developers have to choose to integrate Google's Backup API into their app, and those apps only will get their app data backed up into Google's cloud.

If you're rooted also, then you could use something like Swift Backup to backup to the cloud. I do so, although I still restore as much as possible through Google's backup, and I only restore through Swift on a case-by-case basis, as needed when I discover an app that's tough to set back up doesn't have it's data restored by Google.

If you've used Google Photos to backup your photos to Google's cloud, then hit the button in Google Photos to free up space. This will automatically and only delete your local copies of photos and videos that it's already backed up.

Once that ^ is done, look at your internal storage with your favorite File Manger and see if there's anything left that you want to back up manually, since a factory reset will wipe everything. Copy them to your computer or a flash drive.

When you're just starting the out of the box setup after the reset, when it asks you if you want to use a cable to restore things from an old phone, choose No, and that will lead you to Google's cloud backup where you can choose to restore everything, or you can select what you want to restore.

I think you can figure out the rest.

Also see Post #3 - Other, most important resources:

A list of other important apps
[Google Pixel 8 Pro] roirraW "edor" ehT:
Reserved #8
[Google Pixel 8 Pro] rester555:
@roirraW "edor" ehT You wouldn't happen to have a dev or early unit would you? :)
[Google Pixel 8 Pro] roirraW "edor" ehT:
Oh, that would be nice! No, I've never had a dev or early unit of anything, though. :)
[Google Pixel 8 Pro] rester555:
Depending on radio metrics, I will most likely be getting the 8pro.
[Google Pixel 8 Pro] wangdaning:
If you buy me one I will test it out for you :D
[Google Pixel 8 Pro] roirraW "edor" ehT:
https://store.google.com/magazine/events

"Okay audience (employees), clap now."

Introducing The Pixel 8 and 8 Pro - Google Pixel Community

7 years of software updates for the Pixel 8 series

Pixel 8 and Pixel 8 Pro will receive seven years of ongoing software support across Android OS, security and Feature Drops.

blog.google

I'm not too happy with the $420 trade-in value of my 512 GB Pixel 7 Pro. Outright selling is an option, although there's less than a $100 buffer between that trade-in price and the lowest priced one on Swappa.

It's pretty bad that Samsung's last year best model with the same storage is worth $100 more at trade-in.

Heck, the same size storage Pixel 6 Pro is worth only $20 less than the 7 Pro.
[Google Pixel 8 Pro] rester555:
Yes, the trade in deals are a joke. It's obvious they realize the real "worth" of pixel hardware is behind their competitors. More than anything, if you want this phone, you should get it 6 to 9 months later for a much better deal. But most likely your P7P will be worth much less after 6 to 9 months.
[Google Pixel 8 Pro] roirraW "edor" ehT:
I hate to say it, but if I do choose to upgrade, our Pixel 7 Pros might become our new spare just-in-case phones, which would be good since our other most recent spares are pretty ancient.

I know that benefits Google, too (keeping our phones for spares), but it makes me gag to think of parting with them for such a low price.

My wife and I do have some credit with the Google Store, at least.
[Google Pixel 8 Pro] AmyClaraRose:
im just waiting for pre order to come up on my mobile network so i cane arly upgrade
[Google Pixel 8 Pro] rester555:
I would do this every time if it didn't have a locked bootloader on the carrier phones.
[Google Pixel 8 Pro] AmyClaraRose:
im in the uk luckily enough
[Google Pixel 8 Pro] LLStarks:
Had some play time.View attachment 6017551
[Google Pixel 8 Pro] rester555:
At a store? Which store?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I think I can perceptibly notice the phone boots faster than the P8P, and my complex Nova Launcher home screen loads sooner, too.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Let's try four posts in a row.

Wah. Google changed something for the P8P and now I can't enable the accessibility service necessary for the Classic Power Menu root modification to work.

Edit: nevermind. Fixed it.

Learn about restricted settings - Android Help

When you install an app on an Android device, you control app permissions. Permissions let you choose which capabilities or info that an app can use. Learn how to change app permissions. Harmful apps

support.google.com
[Google Pixel 8 Pro] Ultimoose:
Use the Displax version safetynet-fix-v2.4.0-MOD_1.3-Zygisk.zip @Morgrain Don't use the _2.0 version. @roirraW "edor" ehT It might be worth updating the page 1 post to remove the "install the latest version" or the original one andjust say the the above one. When I saw this post I tried all three and only the 1.3 version works for the P8 to get you to pass the safety net checks.

And unrelated, thanks brother for all youre doing and have done for past phones and releases.
[Google Pixel 8 Pro] Lughnasadh:
Yes, first flash the September boot image (device may not boot but that's okay), then flash the October boot image. This method worked for the most part on Pixel 6s and 7s, but just know that I don't think it's been tested on the Pixel 8.
[Google Pixel 8 Pro] Lughnasadh:
I have no thoughts or opinions because when I get a new device I set everything up from scratch, including all apps. So my way takes a whole lot longer than yours 🤣
[Google Pixel 8 Pro] snovvman:
Folks please check my logic. This is basically what I have done over the years with P4, 5, 6, etc., modified for init_boot. I like flashing manually. I see QPR is already out but no discussion on using it on the P8P and root.

If QPR is not a good idea, I see people talking about flashing the Sept boot image first, then Oct, but are we talking about flashing the Sept boot over the Oct full image, then the Oct image?

Anyway, I would appreciate some feedback and input.

1) Download QPR1b2, extrat init_boot.img

2) Use P6P's Magisk 26301 to patch image and copy to computer.

3) Start P8P, enable dev, unlock booloader, phone will wipe and reboot.

4) Set up P8P using built-in new phone migration process from P6P to P8P (install Google backed up apps, transfer settings, etc.)

5) Copy SD card content from P6P to P8P (music, ringtones, app-specific backup such as Nova)

6) Reboot to bootloader, run flash-all (remove -w and add --skip reboot)

7) Fastboot reboot bootloader

8) Fastboot flash init_boot --slot all magisk_patched.img

I know --slot all may not be needed, also, some will boot unrooted and reboot to flash the patched, but I've always done it this way and it has worked well. This way, it keeps Play Store from becoming uncertified and does not break the root continuity.

9) Fastboot reboot, phone will prompt to install magisk apk, install magisk apk, hide magisk.

10) Install Displax safetynet fix

11) Install SwiftBackup (if not installed by migration already). Restore backup.

12) Restore Nova backup (so desktop icons will show properly after the restore.
[Google Pixel 8 Pro] Lughnasadh:
I've just been informed that Google messed up the naming of the factory images. Apparently the September builds are actually October, so this method probably won't work.
[Google Pixel 8 Pro] snovvman:
Is the October build October too? Are they, then, one in the same?
[Google Pixel 8 Pro] Lughnasadh:
From what I understand, yes. Just different variants of the October build. I cannot confirm anything personally as I don't get the phone until tomorrow, but it makes sense since there were no September builds for A14 since stable A14 was released on Oct. 4, I believe.

badabing pointed this out to me.
[Google Pixel 8 Pro] roirraW "edor" ehT:
@LLStarks, see below (what @Lughnasadh said). There are actually valid reasons to still use 33.0.3 if you want to wipe while using fastboot (34.0.4 won't actually wipe even with the -W). The whole fiasco is Google's own fault. If they would just reasonably fix 34.x, then we wouldn't have to be going through this.

Absolutely, I plan to, but thank you for the reminder. I've been quite overwhelmed in recent months (having nothing to do with technology or the forum), and I just haven't brought myself to properly updating the OPs. I definitely plan to, though, and hopefully sooner rather than later.

I apologize for any confusion.

It's a lot easier to "generate"/write new content than to proofread and correct/update existing instructions, but of course I don't want to write all the OPs from scratch, either.

And thank you so much for your kind words, it's really appreciated. You're welcome, and my pleasure for what help I can give.

If I may ask, after flashing the September boot image, does that mean you should then try booting from it (understanding that it won't likely boot), and only then, re-flash the October boot image, then hopefully boot and profit?

What!? Just the factory images or the OTAs, too? Does the naming mismatch include in running Android's About menu, because mine says October after I took the OTA before rooting, and after manually sideloading the OTA in order to update the other slot (and this would be the slot I should be in now)?

I haven't touched the factory image zips other than download what is supposed to be October's.

This is even more confusing since there are three September images and only one October one.