yashsingh1/xdaforums huggingface dataset:
[Asus Zenfone 9] Veiranx:
I use AccuBattery and routinely get ~8%/hr screen on rate and 0.8%/hr screen off rate. It looks like something is running in the background (as einfachgaer guesses with Instagram and Messenger). If doing as he suggests doesn't seem to help, you might want to consider going into app info and modifying the data and battery settings for each app. To do that, press and hold on the icons until the menu pops up, then select App Info. From there, you should see Data Settings and Battery Settings; open Data Settings and select the option to prevent it from using background data, then open Battery Settings and select Restricted. Finally, select the Force Stop button for both.

Hopefully it gets resolved soon!
[Asus Zenfone 9] Thecurse21:
I had a call in messenger using the camera so the battery drain is probably from that, also Instagram I've been using it a lot with watching reels. I restricted both apps and further dialed the clocks View attachment 5743233Let's see how it goes
[Asus Zenfone 9] Thecurse21:
I use AccuBattery and routinely get ~8%/hr screen on rate and 0.8%/hr screen off rate. It looks like something is running in the background (as einfachgaer guesses with Instagram and Messenger). If doing as he suggests doesn't seem to help, you might want to consider going into app info and modifying the data and battery settings for each app. To do that, press and hold on the icons until the menu pops up, then select App Info. From there, you should see Data Settings and Battery Settings; open Data Settings and select the option to prevent it from using background data, then open Battery Settings and select Restricted. Finally, select the Force Stop button for both.

For some reason Accu battery couldn't measure my health after 5 charges in fact I after 10-12 of charging it from 5-10% to 90 it couldn't asses the health it kept saying it didn't detect any charges below the 15% threshold, I've put the clocks even further as I replied to @einfachgaer now my screen on is 13% discharge and 1.20% during screen off. Tomorrow I'll post the results going to use it today see how it fares
[Asus Zenfone 9] Thecurse21:
Update the is is my current SoT after whole day of heavy use of Instagram scrolling through reels mainly and a video call. View attachment 5745065View attachment 5745067

I feel like it could be at least 6 hours due me under clocking the CPU quite a bit and running in durable mode, but with 120hz. Anyone want to share their SoT?
[Asus Zenfone 9] vexebaj:
Something's wrong with your setup, my phone is completely stock , and from 80% charge i have it on 30 after 12+ hours of use and 4+ hours of SoT . I will try to get more precise data
[Asus Zenfone 9] sakun-ice:
View attachment 5746255

Light use with WhatsApp and browser mainly. Wifi (90%), 4G (10%) and brightness to 70-80%
[Asus Zenfone 9] Thecurse21:
Here's my yesterday stats View attachment 5746381View attachment 5746383

I'm on 32.2040.2040.23 with clean slate installed plus dialed down clocks it's feels like I'm having twice as less battery than it should be, screen on drain is 15%
[Asus Zenfone 9] einfachgaer:
Something is definitely wrong with your device not going into proper deep sleep.

Yesterday I installed Accubattery, so not much data, but it should be enough to show that the battery consumption is very different.
[Asus Zenfone 9] Thecurse21:
I use Sleep Cycle during my sleep, but I use the phone charger not to lose any battery so this couldn't be the reason, another app is YourHour which tracks my usage, going to remove it and redo the tests, also went to 90hz instead of 120hz. If this continues I will do a clean install on the whole phone. Kind of sad because I love the size of this phone and the feel it had, I am waiting for the gcam update so the photo quality comes even more.
[Asus Zenfone 9] craznazn:
Yeah, I got a good 9hr SOT on a medium use day while bone stock. Something's definitely wrong with your device.

Just took the plunge and bl unlocked so I'll let you know how much the kernels do.
[Asus Zenfone 9] Thecurse21:
Quick update: I fully cleaned the device and found out that wallpaper engine was running in the background without stopping and not reporting for some reason on the battery stats, also for some reason the wallpaper I was using wasn't running as pre-rendered but high quality preset, maybe something happened when I transferred my data from my Zenfone 6, battery seems to be way better now will post a report probably tomorrow.
[Asus Zenfone 9] craznazn:
Hope you got better results. This is my phone after a typical workday, so you definitely have a hardware issue if resetting didn't fix it.
[Asus Zenfone 9] Thecurse21:
Well this are my stats since yesterday I decided to use a lot of Instagram to check how much would it drain, plus having two video call for a total of 40mins. And the second screenshot is from couple of days ago honestly I feel like I should ask for a replacement or my expectations are way higher than they should beView attachment 5755399View attachment 5755401
[Asus Zenfone 9] Thecurse21:
Update on this once again I find it weird that I lose 30% of my battery with screen off, could someone post their display off stats?View attachment 5770257
[Asus Zenfone 9] craznazn:
This guy on reddit definitely has a different experience than you

https://www.reddit.com/r/zenfone/comments/z36rjh
[Asus Zenfone 9] FlipFlopHoudini:
View attachment 5773119

im also getting highish usage compared to others, wonder what the cause might be. Were you able to fix it?
[Asus Zenfone 9] Thecurse21:
E

Even with ultra durable mode and turned off location I get the same stats, I installed Naptime to force doze and noticed something the phone refuses to sleep

View attachment 5775397

Try and install it and report to see if your phone manages to sleep
[Wear OS Q&A, Help & Troubleshooting] nighttheduck:
Hey! This is my first time here, sorry if I'm doing smth wrong, I just really need help. My fossil gen 6 is kinda useless at this point after updating to Wear OS 3 and I would like to flash it back to Wear OS 2, since I don't get any notifications & I can't even sync my notes at this point without connecting to wifi (not even through mobile data, which is pretty annoying -> my phone & watch doesn't connect to each other through bluetooth)

thanks, for any guides in advance!

night
[Wear OS Q&A, Help & Troubleshooting] edwin270:
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
[Wear OS Q&A, Help & Troubleshooting] nighttheduck:
Did that 3 times already, nothing changed. Thanks for your answer though!
[Wear OS Q&A, Help & Troubleshooting] Rogthedodge24:
Did you get anywhere with this? I also want to go back to wear os 2. I hate the fossil app
[Wear OS Q&A, Help & Troubleshooting] mickeyvalentine:
I'd like to know too. I just came back to Android with the S23 Ultra and wanted to pair my Razer x Fossil watch to it. But I decided to update since I was doing a factory reset/disconnect anyways. Big big BIG mistake.

There has to be a way to flash wear OS 2.3 back to the watch and re partition it as stock. I'm able to see my watch as a USB perhp on my machine without BT or wifi connection.

Anyone have the old firmware for these watches? Short of buying another Razer watch for $600
[Wear OS Q&A, Help & Troubleshooting] Malvik:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.

For OTA add the hash in the placeholder.

Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>

v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)

Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.

V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
[Wear OS Q&A, Help & Troubleshooting] MiamKebab:
Hey ! Thanks for the file. I'll take the risk to brick my watch.

Do you know how I can flash the archive ?
[Wear OS Q&A, Help & Troubleshooting] Arkbird1000:
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.

Or would you be able to provide some guidance on how to proceed?
[Wear OS Q&A, Help & Troubleshooting] MiamKebab:
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.

So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.

So I'm stuck and that sucks, my duck.

Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
[Wear OS Q&A, Help & Troubleshooting] Arkbird1000:
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.

All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
[Wear OS Q&A, Help & Troubleshooting] Neil_Armstrong_:
You guys seems way ahead on me in the downgrade process...

I made Wear OS 3 update but the Fossil app used to pair the watch won't work with Oneplus 8 Pro (Android 13), gotta go back but i have no idea how...

Yet i flashed a lot of custom roms and stuff in the past, but now.. kinda lost

Im looking forward to see news here

Good luck guys, i'll keep updated if i somehow manage to flash the OTA posted ahead

Edit : well i was on Apkmirror to try an older apk of the app, and found out their app targets android 12 but not android 13..........
[Wear OS Q&A, Help & Troubleshooting] Malvik:
I do have the TWRP but need to find it, took some tweaks from Ticwatch 3 pro. I didnt pushed it on the repo tho. I didnt what made me do it, but I wiped my system partitions and had to rebuilt from the OTA only. But after getting the watch working again, I had few functionalities broke, including the OTA updates. If you can social enginner your way thru fossil to get files such as stock rom and other files for qualcomm software like rawprogrammer and firehose files it can be great help.
[Microsoft Surface Duo 2] Flavio:
Android 12L for Surface Duo is now available with new UI and more

Microsoft's biggest Android update yet is finally here.

www.windowscentral.com

My SD2 just got the OTA update.

I am not sure if I like the new Windows 11 inspired look though.
[Microsoft Surface Duo 2] Unklar:
I got the update too. It´s fine for me, but I couldn´t find out yet how to use two shown icons in overlay mode at the side in any screen /app???View attachment 5743055
[Google Pixel 7 Pro] lyndenz:
Some of the best apps are still 32-bit only. Google disabled the installation of 32-bit apks in the latest Pixel 7 series. Anyone found a hack to enable this YET?
[Google Pixel 7 Pro] wilberfan:
There have been several threads about the 32bit vs 64bit thing (which I'm avidly following) but they're not specifically about hacks to get them to run on the P7. I'll stay tuned here as well...
[Android TV General] themisofgreek:
Hello all,

I have a K10 4GB 64 GB android 9 pie system. And I would like to create an image of it so that when there happens something I can get it back. For example if the the menu boot options are not working then I can get it back by using AMlogic burning tool.

Please help. Thanks in advance....
[Google Pixel 7 Pro] tbalden:
Changelogs and such for later use..
[Google Pixel 7 Pro] Freak07:
nice to see you here :) It´s been a pleasure as always
[Google Pixel 7 Pro] i5lee8bit:
I <3 u 🥴

hehehehehe
[Google Pixel 7 Pro] bs3pro:
Kcal would be nice. A lot of piss yellow screens out there.
[Google Pixel 7 Pro] jgrimberg1979:
It won't flash and now it's obvious, this is based of August update. Do you have a kernel for the October Google update?

Definitely excited to flash this!

And thank you for you helping the community and making these phones the way we like them to run…!
[Google Pixel 7 Pro] roirraW "edor" ehT:
All the firmware for the Pixel 7 so far are dated August - that has no correlation with what security update is on the phone:

Version	Flash	Download	SHA-256 Checksum
13.0.0 (TD1A.220804.009.A2, Oct 2022)	Flash	Link	8e7393e1bd7f86d76d75cdea988d5e4ebfded3a50fac26d774b9eb07152c1ed5
13.0.0 (TD1A.220804.009.A5, Oct 2022, JP carriers)	Flash	Link	c68659bdd1d2b0b9a1740daa1502acbbf1b535be5b7e5bada157c82ef5fbf5c5
13.0.0 (TD1A.220804.031, Oct 2022)	Flash	Link	6152f6f3d8437be0ef840ed7056f15d0f52ba181a1d029ff84bd9d83c860d49f
[Google Pixel 7 Pro] jgrimberg1979:
OK not completely understanding but I appreciate the response. I see October and every kernel except despair won't flash. See the error. Is there a way for fixing this?

Thanks
[Google Pixel 7 Pro] Freak07:
Update your phone to the latest firmware.

If you already did your either running a module or something else changed the security patch state.

There's a check in the kernel.zip that checks for security patch state to be October 2022, which is the state of the latest firmware.

Despair kernel.zip simply lacks that check.

To circumvent the issue otherwise unzip the kernel.zip, locate anykernel.sh, locate the line that starts with "supported.patchlevels", delete the date after the "=" or adjust to your actual security patch state and rezip the kernel.zip.

But I'd rather update to latest firmware or troubleshoot why the security patch on your phone is off. :)
[Google Pixel 7 Pro] EtherealRemnant:
Nice to see this kernel here. I used to run this kernel on all of my HTCs... I wasn't planning to unlock the bootloader but maybe I have a reason now...

That disabling verity after every OTA thing sounds like a real pain though. Google just has to make everything so complicated, don't they? :/
[Google Pixel 7 Pro] Freak07:
hey :)

It´s actually not really complicated to keep verity/verification disabled once you get the hang of it. It´s just one more step/command during the monthly update routine. Or ticking a checkbox in the web kernel flasher.

If you haven´t unlocked bootloader yet, unlocking bootloader requires a wipe and you can combine that with the wipe required for disabling verity/verification flags.
[Google Pixel 7 Pro] EtherealRemnant:
Yeah it's not the worst thing imaginable but it's just another thing I didn't have to deal with on my OnePlus 9 along with the init_boot change is all. I have kind of been enjoying the whole having all my apps and features work without having to mess around with SafetyNet stuff so I'll have to think about it. I'm honestly quite happy with this phone stock, something I can't say for any other recent phone I have had.
[Google Pixel 7 Pro] Freak07:
yes I agree. google put out some great phones with the p6pro and the p7pro.
[Google Pixel 7 Pro] lassetth:
Thanks for the kernel.

I´m on 13 Beta (QPR) Pixel 7 Pro and hopefully you are planning to realease CleanSlate kernel also for this version!?
[Google Pixel 7 Pro] krkhaha:
DISABLE VERITY. That will be clean data? And we must to do that after any stock update?
[Google Pixel 7 Pro] Lughnasadh:
Disabling verity and verification will cause you to wipe your phone if you are doing it for the first time. For updating, you must do it during the update process. The key is to not let your phone boot up with the stock, unmodified vbmeta.img or verity and verification will be enabled again. So disable these flags while you are updating. There are many ways to go about this, The easiest may be to update via Android Flash Tool, which has checkboxes to disable verity and verification. Pixel Flasher is another easy way.
[Google Pixel 7 Pro] quorn23:
Does the P7 already have all Wireguard kernel modules? Coming from a Pixel 4XL, pickup up my 7 this week and very hyped my favorite Kernel is back, awesome!

If Wireguard is still needed, any plans to integrate it in this version of the Kernel as well? (Using Cleanslate as daily driver because of WG support and the stuff like notification blinks etc.)
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth,

Wireguard does get built-in by default with the Pixel 7. However, users are reporting that when using the Wireguard app it's reporting "userspace backend" rather than "kernel backend" as it should. Some adjustments may need to be made in the kernel if the app is reporting correctly.
[Google Pixel 7 Pro] jgrimberg1979:
Great feedback! I am with you on doing it the right way but I don't do a full update not Ota and had Google flasher flash all partitions and disabled both verifications. What am I doing wrong?
[Google Pixel 7 Pro] capntrips:
Can you share the output of the following commands?

adb shell getprop ro.build.id
adb shell getprop ro.build.version.security_patch
[Google Pixel 7 Pro] Freak07:
AOSP Build Environment and Standalone Kernel builds (monolithic builds)

I´m sure some of you followed the movement towards the Generic Kernel Image (GKI) and Qcoms adaption to it called QGKI.

You can find more information about GKI following this link.

What does that mean for custom kernels and this custom kernel?

The last few years the kernel on android devices was more or less compiled as a monolith. That means the kernel is in the zImage with all (most) drivers compiled inline.

However with GKI this changed. There´s the base kernel image while vendor/device specific drivers are compiled as dynamically loadable kernel modules.

On last years devices like the Pixel 5 (using a 4.19 kernel) and this years devices with SD888 on a 5.4 kernel base, there was the possibility to change the QGKI kernel back into a monolithic kernel image. (building the drivers that are on stock kernel external modules back into the zImage to end with a monolithic kernel)

On the Pixel 6 I wasn´t able to achieve this yet. Same goes for the Pixel 7. But during my tries I also wondered if maybe finally the time has come to follow suit, instead of trying to enforce old ways, when there´s a new way going forward.

What does that mean. This means that at this point the kernel is shipped as images that are to be flashed via fastboot. At a later stage I´m sure we can modify anykernel3 to allow flashing zips again, but at this early stage fastboot flashable images will be provided.

Those images can be flashed the same way the device is rooted, therefore I think everybody should be able to flash it easily since the device can´t be rooted any other way.

The kernel was compiled using the aosp kernel build environment. Information about it can be found on the documentation page from google.

This kernel needs to be compiled in the aosp kernel build environment just like the stock kernel. All necessary and modified repos are available on my github. Otherwise please refer to the aosp build environment and the instructions there.
[Google Pixel 7 Pro] Freak07:
Fastboot commands:

This serves just as a reference to restore the images via fastboot. This is not to install the kernel.

Flash the images in this order:

Boot to bootloader:

Either select Reboot to bootloader option via magisk manager, use the button combinations or run the following command while in the OS:

or type:

adb reboot bootloader

Now in fastboot flash boot.img, dtbo.img and vendor_kernel_boot.img

Commands:

fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_kernel_boot vendor_kernel_boot.img

Now boot to fastbootd

fastboot reboot fastboot

Once in fastbootd:

fastboot flash vendor_dlkm vendor_dlkm.img

4. Reboot either via buttons

or by typing

fastboot reboot

5. Profit!
[Google Pixel 7 Pro] Freak07:
Prebuilts for custom roms.
[Google Pixel 7 Pro] Freak07:
last one I promise
[Google Pixel 7 Pro] sam2c:
So glad to see you here 🙏💯
[Google Pixel 7 Pro] i5lee8bit:
Woowoo, let's GOOOO
[Google Pixel 7 Pro] wrongway213:
Kiri is here! Thanks for this awesome kernel!
[Google Pixel 7 Pro] Freak07:
So unfortunately we´re at the moment out of ideas and options for the vbmeta verity/verification disable requirement. @tbalden and me tried a few things and failed with our final idea this morning, which worked on a similar device.

Maybe somebody finds a way so we can actually flash custom images with the avb/vbmeta flags enabled, but at the moment not. I didn´t want to delay the release any further so here we go.

I understand this is a pain for many, but unfortunately that´s how it is now. It was a pain for me too, because on the final test, we really hoped it would work, but we we´re trapped in the wipe ourselves.

Anyway, have fun everyone with the release. It basically includes everything from the Pixel 6 kernel, as they branches are similar. :)
[Google Pixel 7 Pro] PhantomZwei:
Well this is awesome. Haven't modified my phones since Pixel 4 but this is very enticing :sneaky:
[Google Pixel 7 Pro] swieder711:
This made me smile. Loved your kernel on the P6P. So glad to see it available for my P7P.

QQ: Is High Brightness Mode (HBM) supported in this kernel?
[Google Pixel 7 Pro] Nekromantik:
nice to see you on here

I do hope its a firmware issue and next month update fixes issue and then workaround you guys been testing for flashing without disabling verity and verification works
[Google Pixel 7 Pro] Ky0sHiR0:
@Freak07

Thank You very much for this kernel!

May I ask if this one from CleanSlate is included? How is this works?

VoLTE call properties patched in - no root/magisk needed for non supported carriers/countries and VoLTE calls.
[Google Pixel 7 Pro] Ghisy:
Duuuuude! This kernel sounds amazing. And the Powerhint module? WHAT?!

Probably moving to the 7 Pro this weekend so this is very welcome!

Thanks :)

Edit: I'm a little confused: should we flash the zip as usual through EXKM/Kernel flasher or use the fastboot commands from post #4??

Because the OP also mentions the usual way of flashing...
[Google Pixel 7 Pro] rczrider:
Very excited for the kernel, thanks for your hard work!
[Google Pixel 7 Pro] i5lee8bit:
I think that was just a copy and paste from the older P6 thread (also now deprecated for that device, from what I understand). Just use EXKM or Kernel Flasher and you'll be good to go!

Edit: and the companion zip in Magisk Manager. Whoops. In other words, you don't need to manually flash each image to install the kernel.
[Google Pixel 7 Pro] rav101:
Nope,

The powerhint module was never actually depreciated, on P6 he was able to have it included in the kernel zip and it auto-installed into magisk at the same time.

That isn't working here at the moment so you have to manually flash it yourself again
[Google Pixel 7 Pro] Ghisy:
Sorry, maybe I wasn't being clear: should I use quote #1 or #2 down there?
[Google Pixel 7 Pro] Lughnasadh:
The fastboot commands are for if or when you want to return to stock.
[Samsung Galaxy S22 Ultra] shafique ali:
Hey guys i have an problem on my s22 ultra from today morning. I don't hard use or haven't dropped my phone till now from the day i bought. So the pixels on display are malfunctioning itself like only two pixel. I have attached the picture of it. Please help me with it guys thank you in advance.
[Samsung Galaxy S22 Ultra] blackhawk:
Use Screen Test to see what you got.

Send it in for warranty repair. It will likely get worse. A lot of failures and issues with the Samsung variable refresh rate displays. Completely unacceptable for flagship devices.

This is an older version, may or may not work with Android 12.