yashsingh1/xdaforums huggingface dataset:
[Google Pixel Watch] adfree:
I see something with "Phone"...

I made this mistake with Samsung GW4.

You can not use other Hardware.

You need to run Magisk on Pixel Watch...

As Magisk need some info from device...

For my device I was successfull with Magisk Version 24.3 and now using 25.2...

Only as info.

Thanx for your Uploads.

Best Regards

Edit 1.

Not all files downloaded... started with vendor.img

Tested under Ubuntu with imjtool but no success...

Short looked with WinHex inside... no idea what it is...

But system.img is easy. Under Windows I can use 7Zip Tool to extract files.

Edit 2.

recovery.img I can extract with imjtool...

asus@asusEEE:~/imj$ ./imjtool vendor.img extract
vendor.img is not a recognized image. Sorry

asus@asusEEE:~/imj$ ./imjtool recovery.img extract
Boot image version 2 for OS version 0x16000167 (11.128 Patch Level 2022-7) detected (1660 byte header)
Part Size Pages Addr
Kernel (@0x0000800): 17465360 8529 0x80008000
Ramdisk (@0x10a9000): 7556181 3690 0x81000000
Device Tree(@0x17de000): 143653 71 0x81f00000
Recovery DTBO/ACPIO: 28472
MAGIC: 0x1eabb7d7
Extracting dtbo
AVB0 (@0x1809000): 2240
AVBf (@0x1ffffc0):
Tags: 0x80000100
Flash Page Size: 2048 bytes
ID: 81d8d1a935948a17696e088f49b7239d8c5dcc1c000
Name:
CmdLine: buildvariant=user
Found GZ Magic at offset 11460360
extracted/kernelimage.gz:
gzip: extracted/kernelimage.gz: decompression OK, trailing garbage ignored
-100.5% -- replaced with extracted/kernelimage
Extracting kernel
Extracting ramdisk
Searching for DT at 0x17de000
MAGIC: 0x1eabb7d7
Extracting dtbo - exists so renaming to _dtbo

Edit 3.

No idea if vbmeta.img is mandatory... for Patching with Magisk.

I have ever patched both files inside 1 tar:

boot.img
vbmeta.img
[Google Pixel Watch] Tiebe:
I tried to reverse engineer the update API on my pixel 7 yesterday (just the part where it checks for a new update) but everything is encrypted (of course) and Google Play services refuses to accept any custom TLS certificates I put on my phone. There's probably a better way to do this, but I'm no expert. All I know now is that it uses the android.googleapis.com site.
[Google Pixel Watch] Shebee:
Hey,

I've successfully added an unsupported eSIM to my Pixel Watch.

My issue is that my carrier requires custom APN settings, so currently I can only make phone calls, but have no data..

When I go to the mobile data settings on my PW, I can see an entry for APN, but it's just an empty menu.

Any way of customizing those settings?
[Google Pixel Watch] ReDeViL:
Could you

Could you elaborate on how you added an unsupported eSim?
[Google Pixel Watch] Shebee:
Ordered an eSIM from Vodafone Germany online. After adding the eSIM I was able to add a plan to my watch via the app.
[Google Pixel Watch] Mannni:
Same 🙄 eSim now in the watch but no APN and I can't edit or add one.
[Google Pixel Watch] overclocked181:
A long time ago I had problems with APNs for my prepaid carriers not being in android's APN database and would have similar problems (calls only, no data).

At that time, Android stored a list of "all" know APNs in an XML files like this: /system/etc/apns-conf.xml

I was able to download an app on the phone itself, open this file and add whatever APNs I wanted. Then later in the phone settings, my newly added APNs would be available to choose from.

Of course, the main issues being the probable differences between android back then and today...plus differences with Wear.

Back in those days, I found that if I put in an AT&T sim card, android would automatically force the settings from the XML or .db file. If you could find out what APN is being used in that file, you could modify it's details. Does anyone know if Wear uses a similar APN file format as android in the past?
[Google Pixel Watch] overclocked181:
Actually, I just found another post where someone was able to access/modify the telephony database in Wear OS 2.0, but requires root.

https://xdaforums.com/t/how-to-modify-your-apn-to-support-an-mvno-freedompop-etc.3824881/
[Google Pixel Watch] lxrable:
Have you tried turning of WiFi and bluetooth for awhile on the clock to make it get the apn? I have an unsupported carrier on my watch and everything loaded just fine when you disconnected the watch from the phone
[Google Pixel Watch] Shebee:
Does your carrier require custom APN settings?

On my phone i also have to manually enter them.
[Google Pixel Watch] ystokar:
Did this require using eSIM on phone as well? how did you switch to local eSIM?
[Google Pixel Watch] styno89:
Hi @Shebee

I've exactly your same issue, I've add my no supported eSim to my Pixel watch using a VodafoneDE esim.

That was tricky but has worked!

The issue is that I found the apn setting page that is blank... have you find any solution in this weeks?

Regards
[Google Pixel Watch] Shebee:
Nope, seems they just haven't implemented that feature in wear os...
[Google Pixel Watch] styno89:
Have you abandoned this task? Or maybe you have choice a carrier that may work without any apn settings?
[Google Pixel Watch] Shebee:
Yes i have abandoned this for now. I don't want to bother switching just for the smartwatch.
[Google Pixel Watch] Chizhovka:
Hello. I activated LTE on the watch. But the APN is incorrect. LTE works partially. Notifications come, YouTube music works (without connecting to the phone and wifi of course). But google assistant does not work, writes: "No internet connection". Why can this be so?
[Google Pixel Watch] Chizhovka:
I think I understand why the Internet is so bad. In the APN settings, a proxy server is specified, which is no longer used by the provider. Is there any way to edit the APN?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Pixel 7 Pro [Cheetah] QPR Betas

​

QPR stands for "Quarterly Platform Release". Android 13 QPR3 went final in June 2023. See main thread here for final/non-beta releases.

You can officially opt into the Android Beta Program there, or use the factory image or OTA below. You can no longer manually opt into the QPR3 Beta program - only the Android 14 Beta is offered to opt into:

Spoiler content hidden.

Android 13 | Android Developers

<!-- hide description -->

developer.android.com

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

developer.android.com

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

developer.android.com

I don't plan on testing Betas of any sort, but feel free to use this thread for everything about the QPR Betas or major Android version betas for the Pixel 7 Pro. I'll update the information in the OP when necessary. See Post #2 in my main thread for general information (Unlocking Bootloader / Rooting / Updating | SafetyNet working again | ADB/Fastboot & Windows USB Drivers) but ask questions or make observations about all betas in this thread, please.

Once a QPR or major Android version goes final, I'll take those discussions to my main thread.
[Google Pixel 7 Pro] roirraW "edor" ehT:
This post is too big to update, so I no longer have the most recent old information in here.

Spoiler content hidden.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Reserved #3
[Google Pixel 7 Pro] roirraW "edor" ehT:
Reserved #4
[Google Pixel 7 Pro] roirraW "edor" ehT:
Reserved #5
[Google Pixel 7 Pro] roirraW "edor" ehT:
Reserved #6
[Google Pixel 7 Pro] roirraW "edor" ehT:
Reserved #7
[Google Pixel 7 Pro] bscabl:
yesssssss. it was great on my p6pro.. downloading now.
[Google Pixel 7 Pro] Sib64:
Thanks for sharing 😉

Well done 👍
[Google Pixel 7 Pro] EtherealRemnant:
Are these generally safe? I know that there is no EDL recovery type of thing for Tensor Pixels so is it common that they get permanently bricked by these updates or going back to the non-beta?
[Google Pixel 7 Pro] Lughnasadh:
Up, rooted & running 👍
[Google Pixel 7 Pro] bscabl:
ive been on beta for my last 3 phones.. no issues.. [3xl 6pro now 7pro]
[Google Pixel 7 Pro] Lughnasadh:
They're safe. I ran them throughout Android 12. There is a window where you can go back to stable without having to wipe. That occurs when they release the stable build of each QPR, in this case the stable build of QPR1, which should be in December. Once that stable build is released you can unenroll in the beta program without having to wipe, as long as you do it before they release QPR2 Beta 1.

Android Beta Program

Android Beta Program allows you to enroll your Android device for beta releases.

www.google.com
[Google Pixel 7 Pro] EtherealRemnant:
Thanks for the info. I will have to think about it. I normally like being bleeding edge but I also usually have a lot of bugs to complain about (so used to that with my OnePlus 9) and I don't have much to complain about here at all. Not sure I'm ready to tinker too much yet lol
[Google Pixel 7 Pro] Jiggs82:
What process u did to keep root etc ? Do u use custom kernel?
[Google Pixel 7 Pro] Lughnasadh:
I flashed the factory image and re-rooted afterwards. Not using a custom kernel.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I don't specifically recall anyone in my Pixel 6 Pro QPR Beta thread having any non-user caused (or any at all, really) hard bricks. I think these are at least as safe as the Betas for major Android versions, but I just don't have time to set my phone up from scratch if there's a major Beta bug.

I should add the link for opting into the Beta officially, too.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Android 13 QPR1 Beta 3 is here for the Google Pixel series

If you have a Google Pixel device, you can now install the latest QPR1 Beta based on Android 13.

www.xda-developers.com
[Google Pixel 7 Pro] Lughnasadh:
It's nice they released 2 betas this month. In their documentation it does say "up to 2 a month", but wasn't really expecting it. Hope they keep doing 2 a month.
[Google Pixel 7 Pro] scloutkst:
Root installed fine.

Clear calling is now a toggle under the sound and vibration menu on the 7 pro. It is OFF by default.

Vo5G is enabled on T-Mobile for the 7 pro as well.
[Google Pixel 7 Pro] roirraW "edor" ehT:
GSIs

​

I won't be using these, either, but feel free to use this thread for everything GSI related for the Pixel 7 Pro. I'll update the information in the OP when necessary. See Post #2 in my main thread for general information (Unlocking Bootloader / Rooting / Updating | SafetyNet working again | ADB/Fastboot & Windows USB Drivers) but ask questions or make observations about all GSI-related items in this thread, please.

April 12, 2023

:

Generic System Image releases | Platform | Android Developers

developer.android.com

Android 14 GSIs (Preview)​

Date: April 12, 2023

Build: UPB1.230309.014

Build type: experimental

Security patch level: April 2023

Google Play Services: 23.09.12

Type	Download Link	SHA-256 Checksum
ARM64+GMS	gsi_gms_arm64-exp-UPB1.230309.014-9890577-febd421e.zip	febd421e2fa182fa7a3e30ff64417f0da342b825535fc0eef90028679f72380f
ARM64	aosp_arm64-exp-UPB1.230309.014-9890577-2c116021.zip	2c11602154a507b8bd50d0e8a0e3b631ef24e1af70e1bc5e6932700f649cf95a
x86_64+GMS	gsi_gms_x86_64-exp-UPB1.230309.014-9890577-0aef912d.zip	0aef912d0bbab412fe4bc6d7fc9408579197af936ee84d17be10eb1117edae76
x86_64	aosp_x86_64-exp-UPB1.230309.014-9890577-d25c18bc.zip	d25c18bc77d5ff6eea176c399fc6411c66d20a5a796cb691929c1012298e82e8

Known issues with Android 14 GSIs​

Android 14 GSI binaries have the following GSI-specific known issues:

Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.

Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.

System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
[Google Pixel 7 Pro] Sib64:
Great stuff as always 👍

Thanks
[Google Pixel 7 Pro] victortitan:
this google gsi is android 13 qpr1 or stable?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I have no idea if it's either, or if it would be considered its own thing:

Generic System Image releases | Platform | Android Developers

developer.android.com

I would expect that it's an "Experimental" GSI build of Stable, since the page makes no mention of QPR.
[Google Pixel 7 Pro] victortitan:
View attachment 5742581

thank you, i will try
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good eye. My mistake. I would've expected it to say down in the Build information.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Generic System Image releases | Platform | Android Developers

developer.android.com

Android 14 GSIs (Preview)​

Date: April 12, 2023

Build: UPB1.230309.014

Build type: experimental

Security patch level: April 2023

Google Play Services: 23.09.12

Type	Download Link	SHA-256 Checksum
ARM64+GMS	gsi_gms_arm64-exp-UPB1.230309.014-9890577-febd421e.zip	febd421e2fa182fa7a3e30ff64417f0da342b825535fc0eef90028679f72380f
ARM64	aosp_arm64-exp-UPB1.230309.014-9890577-2c116021.zip	2c11602154a507b8bd50d0e8a0e3b631ef24e1af70e1bc5e6932700f649cf95a
x86_64+GMS	gsi_gms_x86_64-exp-UPB1.230309.014-9890577-0aef912d.zip	0aef912d0bbab412fe4bc6d7fc9408579197af936ee84d17be10eb1117edae76
x86_64	aosp_x86_64-exp-UPB1.230309.014-9890577-d25c18bc.zip	d25c18bc77d5ff6eea176c399fc6411c66d20a5a796cb691929c1012298e82e8

Known issues with Android 14 GSIs​

Android 14 GSI binaries have the following GSI-specific known issues:

Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.

Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.

System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
[8525, TyTN, MDA Vario II, JasJam General] sungod916:
Here is my stats:

Cingular 8525

Windows Mobile 5 (out of the box, no upgrades)

I was using Pocket MSN to get my hotmail and use it pretty frequently.

But every so often I would send someone a SMS and they would tell me that it had a bunch of extra text. I ask what text and they would read it and it would be text from hotmail emails!

I would check my "sent" SMS folder and didn't see it.

I looked at the phone of the person who got the message and it had my SMS on top but the continued with text from a hotmail email.

I search the forums and saw where someone else had the problem but no solution was offered.

Please help!
[8525, TyTN, MDA Vario II, JasJam General] sungod916:
Can anyone corroborate that this is accurate?

All my contacts are in Outlook, I should be safe when I hard reset.

Thanks!

it happened to me on my wizard with wm5. i think it is a corrupted cemail.vol file. i tried every which way to delete it, but it would not go away. even tried loading backups of the whole phone and it seemed to help for a couple of weeks but it would do it again. only thing that finally worked was a hard reset unfortunately.

...and if you look at the sent texts it won't show what hotmail was attached to it but if you use jeyo mobile companion to look at the texts it will show it. go figure
[Xiaomi Mi 9 Questions & Answers] iHimbo:
Hello everyone.

I have some trouble rooting my Redmi 9 and I hope you can help me and that I posted in the right forum.

So far I unlocked the bootloader, installed TWRP and tried to install Magisk with help of TWRP. But if I push the Magisk App button in Android, I get the messages below. It wants to install the full Magisk Manager. If I click okay it displays "Downloading", and that forever. I left it over night. Nothing happened. Only "Downloading" until I reboot the system.

I even tried uninstalling Magisk again. So I renamed a copy of the Magisk .apk to uninstaller.zip. But somehow it didn't work. I don't know how to uninstall it otherwise because I can't open the app.

Does anyone have an idea how to fix it? Or maybe there is another way to get root access without Magisk?

I'm happy for each answer.

Thank you
[Xiaomi Mi 9 Questions & Answers] Naet:
first: this is mi 9 forum haha

second: u can rename the zip to apk and install the apk, and maybe works
[Xiaomi Mi 9 Questions & Answers] iHimbo:
It seems I mixed that up. Sorry for that.

I guess I will just try to flash a complete image that is already rooted.
[Xiaomi Mi 9 Questions & Answers] Naet:
i mean, flash the zip in the recovery and after that reboot to system and rename the file to .apk and install it in the system (no recovery)
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] AndroidHQ254:
Source Changelog

Merged August Security Patch

Introduced Quick unlock

Added an option to scramble pin layout when unlocking

Added an option to hide power menu on secure lockscreen

Allow user configurable fingerprint wake and unlock

Fixed an issue where vibration intensity would reset on some devices

Fixed volume panel background color in light mode

Restored default Pixel font behavior

Enable strict standby policy

Rework screen off FOD

AppLock improvements

Updated translations
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] cerme:
hello dear,

can double tap to wake and double tap to sleep be implemented like in the MIUI?
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Sigge2099:
Hi, cant make a phonecall with any dailer. no crash reports, its just shuts down. Had the same problem after a updated the Elixir rom. Then flashed the stock 13.0.2 rom and tried this rom, same problem.

​
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] DarkEmotions:
Same for me. Is there Any Solution? Incoming Calls are also not possible. I have followed the Update Instructions on the First Page.
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
I turned off VOLTE and now the calls are working
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] DarkEmotions:
Could solve the Problem. Switch Off Volte for the SIM. After that it worked in my Case.
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] sgulen:
merhaba

öncelikle romlar için teşekkür ederim oğlu yayınlamış romu yüklüyorum ama çift hatta internet aktif oluyorken yapılıyor ve arayanada meşgül uyarısı veriyor

teşekkürler
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
Perfect ROM, stable and fast ! Thx, AndroidHQ254

Of the rom problems:

- automatic adjustment of the screen backlight: in low light it will change several times in 10 seconds
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] devnoname120:
Awesome thanks a lot!!!
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] devnoname120:
See the solution from this thread:

> Adaptive brightness fix (Updated on 09/07/2020) @AndroidHQ254 - copy to /system/overlay/ folder and set rw-r-r permisions
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
I didn't find such path (/system/overlay/) in android 13, twrp filemanager
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] devnoname120:
Maybe /system/product/overlay or /system/vendor/overlay?

Not that I haven't tried this and I have no idea what's the difference in the paths
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] 0951615114:
Can I install with miui 13 eu
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] devnoname120:
How is the battery life like compared to AOSP?
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] AndroidHQ254:
A fix will come in the next update without the need to turn off volte
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] AndroidHQ254:
Fixed in the next build release. Just be patient
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
If the solution to the problem with VoLTE is fixed in git repo, I will be glad if you add a link to the commit to this topic - it's interesting to know what the changes will be. Thx
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] AndroidHQ254:
The fix involves using the latest codeaurora telephony stuff since our vendor blobs are updated to be at per with lineageos one. The one from PixelOS has not merged the latest QSSI tag
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
Thanks for the clarification
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
Found a very similar described situation about ExoPlayer:

[Bug] MediaCodec: Codec reported err 0xfffffff4/NO_MEMORY on Android 13 devices · Issue #10661 · google/ExoPlayer

ExoPlayer Version 2.17.1 2.18.1 Devices that reproduce the issue Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G) Pixel 5 Pixel 5a Devices that do not reproduce the issue Pixel 6 Pixel 6 Pro Reproducible i...

github.com
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
@AndroidHQ254, will there be a build update this month ) ?

We are looking forward!
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
New release - https://androidhq254.blogspot.com/2022/11/pixelos-13-nov-for-xiaomi-mi-note-10-lite.html
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] Partizanos:
About expected fixes:

- VoLTE - works in this revision

- MiuiCamera with working portrait mode

Bug with freezing of the video in Telegram when rewinding - present

Thx, @AndroidHQ254 for you work !
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] gnome_mo:
I can't seem to turn down volume on ringtone and other system sounds.. All sounds are very very loud, even on lowest settings. Volume in media apps like YouTube works fine.

Just installed ROM, will report any new bugs if present.

Thanks to developer.

*Opening links from Viber doesn't work either.
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] gnome_mo:
Can anyone confirm these bugs or am I doing something wrong?
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] namstoB:
yes, that's true about call volume. I set mine to the lowest level and it's almost too loud.
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] genti.b:
Yes. Every ROM I used with november security update had very high ringtone and notification volume, even if you set it very low.
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] gnome_mo:
Ringtone I could live with, but alarm is a no go for me.

Other thing is face unlock - much better implemented in stock ROM. There is a redundant action, in my opinion - you have to press power button or tap twice to wake, and only then face unlock starts. I couldn't find "raise to wake" option like in MIUI, which is much more logical, IMHO.
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] nikkeh:
The issue I am having with this ROM is that the notification volume setting is completely ignored and notification or call sounds always play at full volume
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] andrut04:
I have Pixel OS installed for 2 days and almost everything works great. One really annoying thing for me is automatic brightness. It's smooth after restart but then starts to change rapidly, it looks awful. I can confirm that ringtones and alarm is very loud, changing it does nothing. Battery life is a little bit worse than on MIUI. Otherwise it's the best ROM that I've ever used and I'm looking forward for the next update. Thanks to the developers for their hard work!
[Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries, ] andrut04:
One more thing is that fast charging isn't working on xiaomi charger. It's working on Apple 30W charger and Realme 33W charger but not stock Xiaomi charger.