yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
Not Android 14, but...

Android 15 might decouple NFC from system updates

At this pace, it almost feels like we won’t need proper Android updates at all in a few years

www.androidpolice.com

https://twitter.com/i/web/status/1655636463760056320
[Google Pixel 6 Pro] roirraW "edor" ehT:
Beta 2:

Android 14 | Android Developers

<!-- hide description -->

developer.android.com

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

developer.android.com

Get Android 14 | Android Developers

Get Android 14 on your eligible device.

developer.android.com

Android 14 | Android Developers

<!-- hide description -->

developer.android.com
[Google Pixel 6 Pro] Lughnasadh:
Their blog post...

Second Beta of Android 14

The Android 14 beta is now available from partners including Lenovo, Nothing, OPPO, OnePlus, Realme, Tecno, Vivo, and Xiaomi across select devices!

android-developers.googleblog.com
[Google Pixel 6 Pro] amritpal2489:
Anybody updated to Beta 2?

How is it?

Any serious issues like Beta 1?
[Google Pixel 6 Pro] acwcanada:
I flashed the factory image with platform-tools v33.0.3 (patched boot.img with Magisk 26101 canary), keep root, run a few hours already, everything seems ok

Edit: One problem occured: JamesDSP stop working no matter what I did (uninstall/reinstall the module)
[Google Pixel 6 Pro] amritpal2489:
Great
[Google Pixel 6 Pro] Doug8796:
I have really bad lte at my new house and use a cell booster. Getting bad speeds on beta 2. Is this just me or are you guys getting less speed?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Android 14 Beta 2.1:

Android 14 | 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

Edit - Interesting. Where the Release notes had initially said:

They changed it back to May:
[Google Pixel 6 Pro] acwcanada:
Updated to this A14 Beta 2.1 and run it for a few hours, everything seems to be OK as so far didn't encounter any issue.

P.S. Be careful of the Platform-tools v34.0.3! I use it to flash this A14 2.1 factory image and it still throws me error which I didn't mark down what kind of error as I was so nervous at that moment thinking that my phone will bootloop again like when it was flashing with v34.0.1. I immediate change to v33.0.3 and everything went smoothly.
[Google Pixel 6 Pro] roirraW "edor" ehT:
See below, and you might want to consider visiting the link in the quote at the very bottom and +1 it, to help get Google's attention (but staying with 33.0.3 for now is fine):
[Google Pixel 6 Pro] acwcanada:
Same as you, I also always haveing command line open in the platform-tools folder but I didn't know this trick to get rid of the "Android_Product_Out" error (I now remembered that I did see it when I was using the v34.0.3). Since I already flashed A14 Beta 2.1, just wish Google would fix the Platform-tools before they release new update. I have already done visiting the link in the quote at the very bottom and +1 it, hope we can get Google's attention.

Thanks so much to provide these useful information.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! Glad to help.

Me too. I wish Google would test more extensively, give release notes on the new version, pull known bad versions to keep them from being downloaded anymore, and I'll also add that they should always change the version number when they've changed the files - as they kept the 34.0.1 version number when they had changed some of the files in the zip around May 10th, if I remember correctly.
[Google Pixel 6 Pro] amritpal2489:
Is pixel 6 pro boot.img working fine for rooting or do we still need to use 7 pro's??

PS: Using Magisk Delta
[Google Pixel 6 Pro] MartinN6:
pixel 6 pro boot.img works pretty good for root with magisk canary
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hey! Finally on the English page:

Beta 3:

Android 14 | 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

Get Android 14 | Android Developers

Get Android 14 on your eligible device.

developer.android.com

Android 14 | Android Developers

<!-- hide description -->

developer.android.com
[Google Pixel 6 Pro] acwcanada:
Update to A14 Beta 3 by flashing the factory image with platform-tools v33.0.3, patched boot.img with Magisk canary-26102, retained root and everything seems to be OK.

Edit: If you are users of "Classic Power Menu", it is crashed when starting. AOSPMods users would also find many features are now not working such as some status bar icons, lock screen features etc.
[Google Pixel 6 Pro] acwcanada:
Just realized that the fingerprint sensor is disappeared on my Pixel 6 Pro after update to this A14 beta 3! Google the web and find out I am not the only person, please read this web page and think hard before you decide to update:

Android 14 Beta 3 breaks the fingerprint sensor entirely on some Pixel phones

Android 14's third beta release seems to cause some Pixel phones to lose their fingerprint sensor entirely, frustratingly.

9to5google.com

PS: Further searching and I am seeing a lot of people reporting this issue to Google's "Android Issue Tracker" although most of them are Pixel 6/6P/6a. So if you are using one of these, I would suggest you stay with Beta 2.1 and not update to this Beta 3 until Google fix the issue, hopefully they would release a Beta 3.1 soon to rectify the problem.
[Google Pixel 6 Pro] D_JWhite:
My fingerprint reader has also gone since updating. I will say that updating was still preferable as I was experiencing excessive battery drain on beta 2.1, and this seems to have resolved.
[Google Pixel 6 Pro] KwstPap:
on me fp working fine. come from a13 stable. aosp mods have bugs. universal face unlock module is broken now. lsposed we need to flash debug-canary version to work. battery seems good, smooth
[Google Pixel 6 Pro] liber:
You can fix fingerprint using the pixel repair tool here

It works until reboot.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Android 14 Beta 3.1:

Android 14 | 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
[Google Pixel 6 Pro] Hell-Razor:
Anybody elses magisk crashing on them when trying to select the boot file to patch? Tried reinstalling, nada.
[Google Pixel 6 Pro] roirraW "edor" ehT:
What version of Magisk are you using? And Stable, Beta, Canary, or ? As far as I remember observing, those who are on 14 Beta 3/Beta 3.1 have had no issue with Magisk v26.1 Stable (26100).

Also, is there any possibility that you previously hid Magisk, and that you've accidentally installed a new copy instead of unhide the original?

Hopefully, someone who is actually running the recent Betas will chime in, too, since I'm on 13 Stable for June.
[Google Pixel 6 Pro] Hell-Razor:
I'm on 26100 too.

No never did that hiding stuff.
[Google Pixel 6 Pro] Lughnasadh:
PSA:

I was not able to patch the boot image with the newly released Canary 26103 on A14B3.1. Cpio changes were made to this release and I got a cpio error. A Github issue has been opened.
[Google Pixel 6 Pro] acwcanada:
I am also on A14B3.1 with Canary 26102 and just got updated to 26103, confirmed that patching the P6P boot image returned with the same error as yours.
[Google Pixel 6 Pro] acwcanada:
One more question: If I remember correctly, you did mention you have a P7P, did this also occur to it? I was thinking that if it is only with the P6 series then I wouldn't expect a update to rectify it too soon and I may have to consider going back to 26102. Thanks
[Google Pixel 6 Pro] Lughnasadh:
I'm running stable Magisk on my P7P so I don't know if it affects that device, or whether it affects stable A13 builds as well. Haven't really seen any other reports except for mine and yours.
[Google Pixel 6 Pro] acwcanada:
Noted, thanks to clarify. People just may not realize it as I wouldn't know either if I don't see your message and run a test patching to get the error.
[Google Pixel 6 Pro] Lughnasadh:
Looks like there is a Pull Request in progress to fix this issue.
[Google Pixel 6 Pro] acwcanada:
The opened issue in Github is disappeared, do you have any idea? Thanks
[Google Pixel 6 Pro] Lughnasadh:
Yeah, John merged the fix. Should be in the next Canary release. Here is the commit for the fix.
[Google Pixel 6 Pro] acwcanada:
Great, thank you for the info.
[Google Pixel 6 Pro] Radon7:
New Android 14 Beta 4 just released! Here is a Twitter thread on what's new:

https://twitter.com/i/web/status/1678802671291998208
[Google Pixel 6 Pro] roirraW "edor" ehT:
Android 14 Beta 4 is up:

Android 14 | 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

Get Android 14 | Android Developers

Get Android 14 on your eligible device.

developer.android.com

Android 14 | Android Developers

<!-- hide description -->

developer.android.com
[Google Pixel 6 Pro] acwcanada:
Flash factory image with platform-tools v33.0.3 and patch boot.image with Magisk-26100 (stable) kept root and everything went smoothly.

P.S. If you are on Magisk canary, remember that canary-26103 is not able to patch the boot.image, you either have to downgrade to canary-26102 or use that stable-26100. Also, new platform-tools v34.0.4 same as v34.0.3 will give error when flashing, so stay with v33.0.3, you don't lose anything!
[Google Pixel 6 Pro] lssong99:
Thanks for the head-up. I just wondering why 26103 cannot patch the boot.img. Could you please also share the patched P6P image here? (Don't want to down grade since some other issues...)
[Google Pixel 6 Pro] acwcanada:
Mine is patched using stable-26100 (as I said I already downgrade to it), I have no idea if you can flash it to keep root if you are on canary-26103. Anyway, attached here as request:
[Google Pixel 6 Pro] lssong99:
Thank you very much! I will try it after work.... As you said, after flash it will downgrade to 26100.... Let me think about this.....

Anyway, thank you soo much!
[Google Pixel 6 Pro] lssong99:
Okay.. I just patched the boot_patch.sh based on Github modification and patch the boot.img with Canary 26103 and it works! Here I attached the patched boot_patch.sh and boot.img of P6P.

If you want to patch by your own with patched boot_patch.sh, please

1. Put the patched boot_patch.sh into /data/adb/magisk (you should backup the original file in this path.) then

2. Set-up environment as described in boot_patch.sh

3. chmod boot_patch.sh 777 (777 is bad but easier...)

4. run 'boot_patch.sh /path_to_your_boot.img/boot.img

5. Profit!

you will have a new-boot.img in /data/adb/magisk path. Just flash this file and it will work.

It's not possible to patch inside Magisk.apk. It seems using an internal script which need to be updated by developer for next release.

Patched boot_patch.sh file is located at https://github.com/topjohnwu/Magisk...e5692da64c1b3f026a62704/scripts/boot_patch.sh
[Google Pixel 6 Pro] mfinlay04:
Getting bootloop when trying to root UPB4 with 26q00 stable. Have 33.03 fastboot. Initially tried the OTA root via magisk as UPB3 I had root working great. Since had to flash the full image to escape the bootloop
[Google Pixel 6 Pro] zyonee:
Tried this method in the Pixel 6 (not Pro) boot.img without success. Can't remember the exact error message. Instead, I had to resort to installing 26100 and patch it from there.
[Google Pixel 6 Pro] mfinlay04:
still bootlooping with this. What version of fastboot are you using? Maybe I need to update?
[Google Pixel 6 Pro] lssong99:
Did you set up the environment variables like dm_verify and others? My understanding is both needs to be true (default is false)
[Google Pixel 6 Pro] zyonee:
Uhm, I don't think so, that wasn't mentioned in the instructions for patching it manually through adb shell.
[Google Pixel 6 Pro] roirraW "edor" ehT:
What environment variables are you talking about? Platform-Tools v33.0.3 doesn't need any environment variables set up. v34.0.4 does, but it also has other issues.

Are you talking about DM Verity and Verification, needed to be disabled if you plan on flashing a custom kernel?

FYI @zyonee, disabling those two things, if you didn't previous disable them, will require your phone to be wiped after in order to function correctly.

Are you using Platform-Tools v33.0.3? All 34.x versions have problems, and 33.0.3 (so far) still works with all 13 Stable and 14 Beta versions of Android.
[Google Pixel 6 Pro] mfinlay04:
Yes I'm still using 33.0.3
[Google Pixel 6 Pro] roirraW "edor" ehT:
Does the phone boot fine if you sideload the OTA and don't bother with patching the boot.img?
[Google Pixel 6 Pro] mfinlay04:
Yes, it works perfectly for everything else. Also, downloaded R34 tools and tried to flash a patched boot.img and the phone still bootlooped. I'm going to try to patch with Magisk Delta and see if I have better luck.
[Google Pixel 6 Pro] mfinlay04:
No dice with Magisk Delta, still bootlooped.
[Google Pixel 6 Pro] Lughnasadh:
When you flashed the full image, did you clean flash or dirty flash? If you dirty flashed, maybe you have a Magisk module in need of an update that is causing your bootloop?

Also, I'm assuming you are using the correct boot image for the build you are on?
[Google Pixel 6 Pro] Doug8796:
https://developer.android.com/about/versions/14/download-ota

Does any brave bootlocked soul want to flash the OTA to Dev Preview 1 to see if it works? I started testing 13 on Dev Preview 2.

Thanks,
[Google Pixel 6 Pro] Justarandomguy:
Rn configuring my Pixel 6 Pro on A14 preview, will use it as main device (I have a backup one if something goes awful everytime on me), and see how it goes
[Google Pixel 6 Pro] tim_m:
I'm going to do it as well, but i'm leaving the beta program first just to make sure it doesn't try and install a beta over the DP1. I've only ever had an issue with a DP once in the many years i've been installing them now, which was last year with the first preview. I got stuck in a factory reset bootloop. That was a bummer but i had a backup.
[Google Pixel 6 Pro] tim_m:
Installed using the OTA on my 6 pro no issue at all and it's working as expected.
[General Topics] lelepu:
I would like a black theme instead of the blue O2 one, and it's by no means a drawback if it's Star Wars or Lord of the Rings themed, but the main thing is that it's black, or at least dark charcoal.
[General Topics] orb3000:
Perhaps you´ll have more chances to get it if you search here:

http://xdaforums.com/forumdisplay.php?f=251

Good luck,
[Android Q&A, Help & Troubleshooting] blizzardblaise:
Some apps and games will not fit my screen for some reason. I have a Revvl V+ and this is getting irritating. The apps will only appear a little larger than half of my screen. Any suggestions would help.

Some apps include: Pray Always!, Bethesda Pinball, Sonic Jump

I attached a picture to show what I mean.

Thank you
[Android Q&A, Help & Troubleshooting] Arealhooman:
These apps are not meant for your devices dimensions. It would strech the screen out, or make part of the game disappear/break if it tried to fit your devices demensions.
[Xiaomi Poco X3 Pro] VladislavRake:
Hi, i have problem.

Bottom area of x3pro display heating too much at 80-100% brightness.

How can i fix it?
[Xiaomi Poco X3 Pro] Tomo123:
Let me think... gee, maybe lower brightness? And stop playing genshin at max brightness for hours on end.
[Xiaomi Poco X3 Pro] VladislavRake:
i'm not playing gayshin, and i'm not playing alot
[Xiaomi Poco X3 Pro] d_g_m_2000:
Who told you that being sarcastic is having a cool personality? if you don't help.. *stfu
[Xiaomi Poco X3 Pro] Tomo123:
Wow, some really edgy boys up in here... Enjoy each others company. May it be a wet night for you two.
[Xiaomi Poco X3 Pro] Sib64:
EDIT MODERATION​

I would like to remind you that we are here to share knowledge, but also to help in our comments.

But I would also like to remind you that it is good to research and read before posting a question (xda forum rule #1), as you may not be the first to ask that question.

Sometimes some people should reread the forum rules, especially the one concerning courtesy in answers or questions:​

Thank you for your comprehension and have a nice day ;)

Sib64 - Moderator
[Galaxy Tab S Q&A, Help & Troubleshooting] LOAZIT:
hello

i'm trying to downgrade my p615 to android 12 from android 13 for the purpose of installing lineageos.

SamFirm v0.5.0 gives me this error for some reason.

Could not fetch info for SM-P615/OJM. Please verify the input or use manual info

can you tell me what should i do from here?

thanks
[Samsung Galaxy Watch 4] luufeliipee:
Is possible use button stopwatch with waterlock? (screen blocking)

Tks.
[Upgrading, Modifying and Unlocking] lelepu:
In the Greek Rom from Qtek devises in Greece, there is an application witch converts the characters wenn you typing an sms, and you can write 160, and not 70 characters pro sms.

The foto shows witch application is that.

I am also uploading two files, witch i think is a part of this application,

but it not runs on other non Greek rom devices. It's locked.

Can anyone help me, and maybe all the Greeks to solve this problem?
[Samsung Galaxy S23 Plus] skimminstones:
Just pre-ordered the s23+ in Green, (never liked the square design of the ultras) to replace my Pixel 6 pro. This is my first Samsung since the Galaxy S3.
[Samsung Galaxy S23 Plus] pvc_:
I pre-ordered going from S20+ to S23+. Honestly, I am not that excited about this phone as I think S20+ is one of the greatest phones they've produced in recent memory. By doing this "upgrade", I am losing a lot of features and options. I am still debating with myself if I should cancel the order and keep the S20+ for another year...

Here is the list of downgrades: No SD card, RAM reduced from 12GB to 8GB, No MST, lower pixel density, fewer cameras, slower wireless charging, No FM radio, and probably a few other things...

My main reasons for buying it are: bigger battery, more storage space, faster processor, and I'm worried my S20+'s battery would degrade even more as it ages...
[Samsung Galaxy S23 Plus] goRt:
Yep, graphite expected in 3-4 weeks, 1+8 retiring as it will only get security updates this year and the 10/11 have no released bootloop tool
[Samsung Galaxy S23 Plus] rafik25:
Hello to replace my p7pro that I sold I bought this Monday the s23plus that I received yesterday ( Boulanger marketplace in France)
[Samsung Galaxy S23 Plus] pksw:
Have had mine for a few days now. Upgraded from s10+ as my battery had degraded so the phone wouldn't hold a charge.

A bit different having no buttons on the left, no headphones socket, no sdcard but I guess no modern phone has kept all these features.

Scrolling is very smooth, but otherwise I've set the phone up identically to the s10+ so I've not really noticed any difference yet.

I hope I can find a way of making the torch load by holding one of the physical buttons like I did on the s10+. (I know I can use double click on thr power button but I want that to be the camera).
[Samsung Galaxy S23 Plus] Fredzvw:
Just pre-ordered the s23+ in Green to replace my S22+!

Received today.
[Samsung Galaxy S23 Plus] pvc_:
Where are you located? Mine was shipped today, but FedEx says they won't deliver till Wednesday of next week even if it gets here sooner.
[Samsung Galaxy S23 Plus] Fredzvw:
Québec, Canada. Phone was in stock in Ontario.

Samsung said they will send my phone February 8. That's what they did and received it February 10 with Fedex!
[Samsung Galaxy S23 Plus] ermacwins:
Graphite so 3 weeks wait or so
[Samsung Galaxy S23 Plus] dachriss_13:
I did the same. Although design and exteriour changes are minimal, the way the S23+ performs compared with S22+ is way way better. Oh, and I can easily get 5-6h SOT whereas with my S22+(snapdragon) I never passed 4h-4.5h.
[Samsung Galaxy S23 Plus] skimminstones:
still waiting for mine from EE in UK.

Was going to get it from samsung direct but the website wouldnt allow me to cash out so thought id just do it through EE. Got a text recently saying "good news we will deliver earlier than expected" and heard nothing since.
[Samsung Galaxy S23 Plus] Keith W:
Just pre-ordered the S23+ in Graphite

They said they had it in stock at time of purchase but are now saying up 4 week wait :(

EDIT: The date changed to a 7 week wait!!!

Have just cancelled and re-ordered the S23+ in Phantom Black instead.... Should be in my hands Saturday morning
[Samsung Galaxy S23 Plus] skimminstones:
Finally got mine, set it up last night and just going through all the app installations. I prefer setting them up fresh rather than from backups
[Samsung Galaxy S23 Plus] Keith W:
I am the same, always set up a new phone from scratch rather than use backups
[Realme 6 Questions & Answers] Ahmed405:
After flashing custom ROM for realme 6 call senseor stopped working...any one help

I have changed many custom ROM for my phone but this still not work

I don't know what to do, I'm so tired trying to solve it but I fail

Now I'm on stock ROM ui 1 Android 10
[Magisk] mtuxz:
Hi

I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.

I followed this instructions to fix magisk stock backup does not exist

I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
[Magisk] ethical_haquer:
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!

:)

Alteratively, look here.
[Magisk] Minionguyjpro:
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???
[Magisk] ethical_haquer:
I'm installing an update right now. :) I would imagine it works with TWRP as well, but I only recently started using it.