yashsingh1/xdaforums huggingface dataset:
[Vivo X Fold] rocky272727:
Any Vivo X Fold + owners, how long does the battery last one charge?
[Vivo X Fold] lawtq:
Can't answer the question about differences from first one as never had it. Software wise they're all the same it seems, had the x 80 pro and x note before selling them.

This has better battery life than the x note did and that had a 5000mah battery! Really good wifi battery life and good cellular battery but not great. Like most phones I guess.

If you have the first I wouldn't bother get this one. Pointless. It's best fold phone for me though and I've had honor magic v, z fold 3 and 4, huawei fold, and xiaomi first folding phone
[Vivo X Fold] Smartphoner:
Can you please confirm if the VoLTE and Android Auto are working?
[Vivo X Fold] lawtq:
VoLTE works for my EE uk sim but I've never used android auto
[Vivo X Fold] ricky886:
Google voice match not work
[OPPO Find X3 Pro] Dax1983:
In less than 12 hours OPPO will be live streaming the #ColorOS13 global online launch event. I noticed that the preview is already available on Youtube:
[OPPO Find X3 Pro] SamS0806:
Guess I have to wait until December for the update!

View attachment 5692899
[OPPO Find X3 Pro] Dax1983:
I'd still prefer getting the official version, but was too interested in ColorOS13 to pass it off.
[OPPO Find X3 Pro] W.Logan:
It will be a game changer when they start launching the official version. Though tbf, there aren't a lot of complaints other than GPay in this beta.

Did you hear about any overheating news? It doesn't seem like it this time.

Well done, ColorOS and OPPO!
[OPPO Find X3 Pro] SamS0806:
There were probably security challenges in the syncing GPay in the beta version.

I have only seen one review where there was overheating but that was due to an Always-On setting.

Have you seen a stress test for ColorOS 13?
[OPPO Find X3 Pro] mklasse:
I got notification to try the ColorOS 13 beta, but when I clicked on it, it says no test version available.. that is such a dissapointing thing :rolleyes: I was busy with life I wasn't even aware ColorOS 13 is coming, now because of that notification I want to try them so bad.. oh Oppo.. you #$#@$! :cautious:
[OPPO Find X3 Pro] Alex4455:
Why would you want to try a buggy software right off the start ?

I would hold at least 2-3 update versions before updating to Color 13 with A13
[OPPO Find X3 Pro] mklasse:
I just like to try new stuff, and generally impatient guy hahaha

I have been disappointed by how manufacturers put their own skin over vanilla android though..

Like Android 12 has new quick setting style, but ColorOS 12 quick setting is exactly the same as Android 11.

The funky time widget of Android 12 didn't make it to ColorOS 12 either, I had to download and use 3rd party widget for the same look.

I wish they sell Pixel in my country. I don't want to buy a phone that has no local support in case something went wrong, hence I choose Oppo, was satisfied Huawei user until they are banned to use google services.
[Touch Pro, Fuze General] botzino:
Hi mates,

as already recommended, I just ask how I can deactivate UMTS/3G on my TP. Several tests mean that with this little trick may be the battery-performance much better. But how to do??

Tanks for answer

botzino
[Touch Pro, Fuze General] andy.xda:
you should just be able to hold down the end call key, a list will come up and there you are.
[Touch Pro, Fuze General] Giannis86:
i used advanced config

menu-->more settiungs->comm manager

then i enabled 3G (you have to disable another one if you want to add a new item)

anyway after that 3G appears in the comm tab in TF3D

every time i dont use the the device for massive internet stuff i turn it off..

i found that it saves a lot of battery like this

another method is to just go to your phone settings and set the network to GSM only...but this method is far more time consuming
[OPPO Find X2 Pro Guides, News, & Discussion] crazyfish1111:
one key root.

V12.1

The version number must be f.20

Connect your phone to your Windows computer.

Mobile phone settings file transfer, computer installation driver.

Unzip the package with one click root.

Friendly reminder: you need to unlock it first, go to the official application.
[OPPO Find X2 Pro Guides, News, & Discussion] cazxda:
how to run this? i jsut need to run the batch file?
[OPPO Find X2 Pro Guides, News, & Discussion] nongrata23:
Anybody tried this, does it work for European version?
[OPPO Find X2 Pro Guides, News, & Discussion] gustavomp:
I'm a bit skeptical. Anyone tried it?
[OPPO Find X2 Pro Guides, News, & Discussion] crazyfish1111:
https://pan.baidu.com/s/1qD95_rp-ShWvQAHLsUsppQ?pwd=6666#list/path=/ pwd=6666
[OPPO Find X2 Pro Guides, News, & Discussion] crazyfish1111:
View attachment 5930475
[Nokia 8 Questions & Answers] DARKNIGHT2711:
WHAT I CAN DO? IT DOESN'T LET ME INSTALL TWRP OR ORANGE FOX OR ANY ROM, I CAN ONLY ENTER FASTBOOT, THE BOOTLOADER IS UNLOCKED, IN HAVOC OS THERE IS ONLY THE PAYLOAD.BIN FILE AND I DECOMPRESSED IT, I HAVE THE BOOT.IMG, SYSTEM.IMG, VENDOR. img
[Google Pixel 6 Pro] Batyan:
Hi everyone.

I have rooted Pixel 6 Pro (no custom kernel or recovery) on Android 12. I tried to OTA update, so I:

- disable magisk

- download OTA update

- install magisk to second slot and rebooted

After that i got "Corrupted device" message on boot. But my first slot boots fine and continue showing me to reboot to apply update.

So, I have slot "_b" booted normally and slot "_a" with "Corrupted device" message. So, how can I fix that without wiping data? I hears some people get hard bricked devices trying to fix it

Thanks a lot

PS. I'm not sure what Android version came with OTA - in update process there were no information
[Google Pixel 6 Pro] Druboo666:
Flash both slots @ Android Flash tool

Search the guides how to do that
[Google Pixel 6 Pro] Batyan:
Thanks a lot.

So, flashing without "Wipe Device", without "Lock Bootloader", but with "Force Flash all Partitions", am I right? Do I need to disable any verification?
[Google Pixel 6 Pro] roirraW "edor" ehT:
"Force Flash all partitions" will wipe your phone because your internal storage is a partition. No, don't disable verification.

So yes, flash without wipe device, without lock bootloader, and WITHOUT force flash all partitions and WITHOUT disabling verification.
[Google Pixel 6 Pro] bush911:
Hi there,

Just like the title says.

Xprivacylua won't' work on Android 13 for me. what I was wondering is whether I can downgrade without flashing the bootloader.

I am going to follow the following guide but am afraid to get a bricked phone:cautious:

How to Bypass Anti Rollback Mechanism in Pixel 6A/6/6 Pro

This guide will show you how to bypass Anti Rollback Mechanism while doing a downgrade from Android 13 to Android 12 on Pixel 6A/6/6 Pro.

www.droidwin.com

Thank you all

------------------------add---

finally managed to downgrade to Android 12, just add --force before update:

fastboot --force update image-oriole-sq3a.220705.001.b2.zip (m phone is pixel6)

then reboot, then choose factory reset.

credits @Bunnehbunn
[Google Pixel 6 Pro] Deleted member 6200352:
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day

forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.

If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
[Google Pixel 6 Pro] bush911:
You've made my day😁

I am going to wait and see for several days before proceeding as I just know how to flash-all, I have never flashed step by step or flashed to the specific slots.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.

I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
[Google Pixel 6 Pro] Lughnasadh:
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me 😆
[Google Pixel 6 Pro] bush911:
Is downgrading on both slots a must? I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.

tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12

Post before crashing

.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you want to run Android 12 instead of 13, and you've already flashed 13 to both slots, or at least 13's bootloader to both slots (which you should definitely do if you haven't), then yes, you should downgrade both slots and wipe to start fresh.

You can't expect both Android 12 and Android 13 to operate with the same app data, so having a different version of Android on the other slot isn't going to do you any favors.

Try a factory reset?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Here my friend. Also in the OP.

Partial quote:
[Google Pixel 6 Pro] Lughnasadh:
Ok, you are now officially a better friend to me than search is. Sorry search... 🤪

Thank you!!!
[Google Pixel 6 Pro] roirraW "edor" ehT:
You can join the ranks of such like my boss at work (where we use Google officially for everything including company mail). They chat me to ask me for a link to a particular file that's in Google Drive, or to find a particular email for them.

Just kidding about joining the ranks! :D You're welcome!
[Google Pixel 6 Pro] Lughnasadh:
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???

It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Absolutely, I agree on both parts.
[Google Pixel 6 Pro] enderdzz:
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.

I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.

I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
[Google Pixel 6 Pro] Namelesswonder:
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April. Also I'm surprised you weren't bricked after booting Android 13 because it does increment the anti-rollback counter.

https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226

drivers/soc/google/boot_control/boot_control_sysfs.c - kernel/gs - Git at Google

I'm guessing your bootloader version is old enough to not have the bits implemented so it just doesn't care, but that's weird because the July Android 12 bootloaders do have the bits and will not load if the counter is incremented by Android 13.

I wouldn't recommend continuing to run like this and would update to the August Android 13 bootloader because there's no telling what might be happening wrong under the hood. Example is that the August Android 13 bootloader it is able to boot Android 12 but because of interface differences it is a broken experience.

https://xdaforums.com/t/psa-do-not-...ader-central-repository.4352027/post-87310375

So yeah if you're correct then it's possible you did get away with it as your firmware is too old to have implemented it. However this is not a supported firmware-software configuration.
[Google Pixel 6 Pro] enderdzz:
Thank you for your reply!

Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.

I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.

BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
[Google Pixel 6 Pro] Namelesswonder:
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal (android.hardware.boot@1.2) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.

I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.

And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.

https://xdaforums.com/t/psa-do-not-...-6-pro-bootloader-central-repository.4352027/
[Google Pixel 6 Pro] enderdzz:
Thank you very much! I'm much more clear now.
[Google Pixel 6 Pro] Namelesswonder:
That's good.

Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
[Google Pixel 6 Pro] enderdzz:
Yes, I'm also interested in this topic.

I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems :)

I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.

I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
[Google Pixel 6 Pro] Namelesswonder:
If WebView applications didn't crash within minutes of launching them then that means the DRM library should either be working or just not segfaulting like it does with Android 12 on 13 bootloader.

The fingerprint scanner HAL not working is completely understandable, part of the bootloader flash also carries the fingerprint scanner's firmware, and we know that one of the big things with Android 13 is that the fingerprint scanner is somewhat more reliable, so it definitely has changed between Android 12 to 13.

Interesting stuff, will be cool to see where it can go, but man is it sketchy to recommend people still on Android 12 to downgrade to April and then try flashing the Android 13 system images, real possibility of making bricks.
[Google Pixel 6 Pro] nutzfreelance:
i am another person very interested in android 12 on a13 bootloader and android 13 on a12 bootloader.i will be watching this thread .

i have concerns with android 13 and want them assured long before i do an update.
[Google Pixel 6 Pro] card13:
Ran a couple tests to see what was working and what was failing.

OEM A12 (raven-sq3a.220705.004-factory-112d4f32) on A13 Bootloader

Step 1. Make sure both Slots have A13 w/A13 Bootloader

Step 2. Make full backup of Apps and Data

Step 3. Install with fastboot --force update

Step 4. Sign-into Play Store

Step 5. Install Webview Canary

Step 6. DRM specific items fail with unable to access errors

LOS 19.1 on A13 Bootloader

Step 1. Make sure both Slots have A13 w/A13 Bootloader

Step 2. Wipe

Step 3. Install LOS 19.1

Step 4. Boot Slot B (Slot A fails to boot)

Step 5. Install DRM testing tools. Got same issue as OEM A12

At end of process re-wiped and re-installed A13 Update.

***EDIT***

Forgot Install of ROM step in OEM ROM trial write-up.
[Google Pixel 6 Pro] bush911:
This DRM issue is really annoying. I use Firefox as Browser, Poweramp as audio player. So far so good. Previously, Chrome and Musicolet have issues.

I even flashed April image on A13 bootloader, issues persist.

With A12 OS on A13 bootloader, there is no system update available message anymore, therfore no forced automatically update
[Google Pixel 6 Pro] nutzfreelance:
Has anyone tried the android 13 beta bootloader with A12 or A13?

I would really like a way to test andorid 13 without being forced to stay on it. information on new features and security methods is very sparse. and there are many show stopping bugs being reported.
[Touch HD General] JetMouse:
Hi - is there any way to remove this from the home page (similarly to how voicemail disappears once you've deleted it)? Thanks...
[Google Pixel 5 Questions & Answers] jonga80:
My question is about this function. I understand is a function that always runs when music plays. On my Pixel 5 it runs randomly, sometimes yes, it's recognizing music, and sometimes it's not. I would like it to always run when music is playing. I have the button activated on the lock screen, but I would like it to be always automatic, not having to do it manually.

Maybe my English is not the best, because I used the google translator. I asked in some Spanish forums and they couldn't help me.

Thanks.

View attachment 5688871
[Redmi Note 11 (spes/spesn)] anmol150704:
When MIUI 13 android 12 in India will start to rollout ??
[Redmi Note 11 (spes/spesn)] animegamer4422:
Sir , the update has been already rolled out

View attachment 5688877
[Redmi Note 11 (spes/spesn)] pulsar:
yes. I don't have the update either.
[Redmi Note 11 (spes/spesn)] anmol150704:
When was it out for u? I also have revive updates early option turned on
[Redmi Note 11 (spes/spesn)] anmol150704:
When did u receive the update
[Redmi Note 11 (spes/spesn)] pulsar:
My Redmi Note 11 model is 4GB+64GB
[Redmi Note 11 (spes/spesn)] Wilbo2016:
As far as I know the only difference is NFC. Look under Connection and Sharing in Settings and scroll down to NFC.
[Redmi Note 11 (spes/spesn)] Lister Of Smeg:
Hi Pulsar,

As mentioned in the other post, if you download MIUI Downloader and run that. It will tell you exactly what device you have, and what official firmwares are available.

The only difference is whether your have NFC or not... So will be a spes or spesN (if nfc).

Cheers, Lister
[Redmi Note 11 (spes/spesn)] zoltan.1612:
Possible to flash spesN fastboot rom for spes?

Difference NFC and carrier aggregation.

Spes support only intraband carrier aggregation, but spesN support interband.
[Redmi Note 11 (spes/spesn)] SubwayChamp:
While you're locked, probably, the stock recovery refuse to do so, but if you are unlocked, you can. It doesn't hurt to try it, if you can flash it, no harm goes on.
[G1 Apps and Games] mouseclone:
Ok, maybe I'm going a little overboard here, but I jailbroke the phone just yesterday. I thought that it was time to see what all I would be able to do with it. So i got to looking around trying to figure out what I could skin. /system/app/Launcher.apk provided what i needed to redo the app bar. Here are my results.

I didn't do any modification to the xml files yet. I would like to get where I can edit the images out of those files as well. I removed the up/down arrows, but it was more of a replace with a 1x1px png. you get errors if the files are not put back with the right names or if files are missing. So I'm sure in the xml you would be able to edit it out.

One last thing. There really isn't much space on the /system mount. even when coping the file back up after repacking, I would ofter get not enough space on disk error. Trying again resulted in a success.

How about something else. I am not the best artist or graphics person. I'm sure that my files are larger then they should be. I had to do a 255 index on the color to get the image files down small enough. I'm sure with proper programming on my part, I wouldn't need the bar image, just the tux image. /shrug. I'm tired and going to be.

Enjoy.
[G1 Apps and Games] Karolis:
Impressive. What does it look like with the apps menu expanded?

Oh, and how do you take screenshots?
[G1 Apps and Games] mouseclone:
It looks like it would noramally but with a tux on it instead of the grey bar. I will have to gt another image up.

The program to take screen shots is ddms (i think). It is in the tools directory of the sdk. Sorry, I just woke up for work.. not much sleep. But I do know if you are running linux it has to be on a 32bit os. It wouldn't run on my 64bit ubuntu.
[G1 Apps and Games] mouseclone:
a question I received

I don't know how much help I can be with the jar tool. I can tell you what I did though.

I used adb to get the /system/app/Launcher.apk file. The I extracted the file. So now I have the .apk file and a folder with all of the files in it. I then copied the .apk file to make a backup of it, just in case I needed to push it to the device.

Ok now I am set to do the editing of the files. I use Linux so I started gimp up editing an image. Then saved the image, keeping it the same size (56x295 - something like that) as the previous file. The files size (k/mb) will change. You need to keep this as small as you can.

I then started up Archive Manager, I think that you said that you use winrar or something. You might want to try 7zip, not sure though. Onward. I opened the .apk with the archive manager. The allowed me not to have repack the archive. I then dragged and dropped the edited .png file into the same folder I edited it from, into the same folder browsing though the archive manager. This did nothing more than update the .apk archive with the edited file.

then I pushed the file back to the droid. I hit the end button to turn the screen off and then menu x2 to get into the interface again. This refreshed the interface. and my edits were there.

That is about it. I'm going to copy and paste this reply in the forum so others will benefit from your question.
[MTCD  Android Head Units Q&A] quocta:
Hi team,

I am driving Outlander 2022 and using DVD Android 11, is there anyway to change GG assitant to other one? Because when I disabled GG Assistant the voice control button not working if want want to use other Voice Assistant I have to open app.
[MTCD  Android Head Units Q&A] quocta:
I found solutions - have to change GG Assistant in default app to other - but in default app I didn't see the other except GG Assistant
[MTCD  Android Head Units Q&A] quocta:
Fixed by myself
[Redmi Note 11 (spes/spesn)] pulsar:
Since Android 12 is coming out, I want to know if Xiaomi will ever release Android 13 in Redmi Note 11.

I don't intend to root or put custom rom yet. But I will do once Xiaomi stops supporting the device.

So, maybe I will flash custom rom later.

Currently with MIUI 13.0.15 android. Xiaomi Ram management is very bad.