yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 Q&A, Help & Troubleshooting] f_ammari:
Yes same her, my CorePlayer 1.3.6 stopped playing Youtube end of July.

Is there any update out there?
[XPERIA X1 Q&A, Help & Troubleshooting] surgex0:
Yep, doesn't work...lame
[Huawei P50] Cyanide_zh:
Huawei P50

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com

Somebody managed to flash a generic system image. No idea whether the device is based on qualcomm or hisilicon. And seems that it isn't repeatable arbitrarily due to potential efuse writing.
[Huawei P50] Alpa7000:
Yes，it's a Huawei P50 prototype

And it can run Windows 11
[Redmi Note 8 Pro Questions & Answers] edu.mc:
hello,

in Fastboot-mode I flash TWRP successfull, but when I want to boot recovery, it starts Redmi-Recovery 3.0.

No start of twrp-recovery.

Commands: (same commands I have tried with Windows 10, other TWRP-versions I tried too.)

$ fastboot devices

tkx4gm5575vod69p fastboot

$ fastboot flash recovery twrp-3.7.0_9-0-begonia.img

Sending 'recovery' (31380 KB) OKAY [ 0.876s]

Writing 'recovery' OKAY [ 0.248s]

Finished. Total time: 5.123s

Shutdown phone, Press Power On/off + Volume-Up, Press Volume-Up and it starts Redmi-Recovery 3.0.

Where is my mistake?
[Redmi Note 8 Pro Questions & Answers] edu.mc:
got done, used alternative twrp
[Redmi Note 8 Pro Questions & Answers] dzli:
"twrp-3.7.0_9-0-begonia.img"

I think this is official twrp, but this is for Android 9.0
[Redmi Note 8 Pro Questions & Answers] edu.mc:
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.

I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot

so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
[Redmi Note 8 Pro Questions & Answers] mydurmaz:
which lineage did you flash?

There is no official as far as I can see. unofficial too.
[Redmi Note 8 Pro Questions & Answers] edu.mc:
lineage-20.0-20220822-UNOFFICIAL-begonia.zip

(I don't know from which address I download it. I searched unsuccessful)
[Redmi Note 8 Pro Questions & Answers] edu.mc:
https://sourceforge.net/projects/darkjoker360-developements/files/Xiaomi/Redmi%20Note%208%20Pro/ROM/20.x/lineage-20.0-20220822-UNOFFICIAL-begonia.zip/download?use_mirror=netcologne&use_mirror=netcologne&r=
[OnePlus Nord 2 5G] c1rca:
Hello

i used stock OxygenOS firmware based on Android 11 and everything was working good. But i wanted to try [ROM][13.0][DENNIZ] Project Elixir [OFFICIAL] [Thirteen][AOSP] and install it using TWRP. Elixir works fine but i have some problems with SMS so i install [ROM][UNOFFICIAL][12] PixelExperience [AOSP] OnePlus Nord 2 5G [denniz] and have same problems. Then i try

OPN2_DN2103_OxygenOS11.3_A.20_Stock using PartitionsBackupper_v1.8. Installation was ok but after turn phone on i catch bootloop on text "android".

I tryed to get back Elixir but is the same problem: bootloop.

How can i fix it?
[OnePlus Nord 2 5G] c1rca:
I back to A19 and works again

right now have problems to update. show: veryfication field.

I tryed to install stock A20 but it didn't work -> bootloop

So i stay on A19.
[OnePlus Nord 2 5G] roldev:
You can try this guide:

https://xdaforums.com/t/stock-full-rom-oxygenos_11-3_a-20-eu-dn2103-unbrick-guide.4366985/

Tried, works fine and can be updated to A12 stock through updater. Warning. Will remove fastbootd and BROM so no more control over your own cellphone.

You can update to A11_A.21 too through temporary TWRP install to have the latest OOS11, until hope that the custom ROMs became more stables.

Unfortunately phh stopped it's AOSP, as per Andy Yan words so hard time for all GSI based ROMs. The most skilled devs don't have enough spare time.

Let's see what's happening...
[OnePlus Nord 2 5G] c1rca:
I make everything from this step:

and still same problem.

Do you use mtkclient?
[OnePlus Nord 2 5G] roldev:
For some reason partition backuper didn't work for me. Maybe because unauthorized pc I used , so I made full restore with mtk client from this post.

This backup did not override your proper unique partitions. Did a full wipe after flash and get brand new A20 which still use with a pleasure. A bit worried about the android security patch a bit old, but not so critical.

In a couple of weeks when buy new phone will try update this one with well maintained custom ROM. Right now is my daily driver.

Hope helped.
[OnePlus Nord 2 5G] c1rca:
I tryed both and mtk works better. Now i have A20 with A11

Not work for me. It's A21 with A12? Or need to wait for A22?
[OnePlus Nord 2 5G] roldev:
Nope, bro. The last A11 is A21 update.

Won't be A22 update.

You can update to A12 C.10 on DN2103.

Or every A12 update > 02, for an Indian version.

Make sure you really want to f** your phone with A12 from OnePlus, loosing fastbootd and BROM mode ...
[OnePlus Nord 2 5G] c1rca:
thank you. I will stay on A11 but i can't update it to A21. I have "veryfication problem". I am on A20.
[OnePlus Nord 2 5G] roldev:
There is a way, documented here in this forum, to recover stock boot.img, update via temporary TWRP install, and get the latest update.

Because of lack of time I didn't update to A21. The unique difference between A20 and A21 is android security patch level. 2 months diferentes which is not so important for mi. A20 hasn't any bug. Disabled update notice and enjoy.

When have some time will install some of the customs roms available, currently in very advanced state and development.

Cheers.
[OnePlus Nord 2 5G] TheKloras:
wait, did they really just remove fastboot and brom on C10? because i installed it and got bootloop, and i cant even figure a way to fix it so i guess my phone is just a brick because of that
[OnePlus Nord 2 5G] roldev:
I don't know when removed fastbootd exactly. I think still there on C.01. Brom was disabled from preloader on C.04 or C.05 beta. Then applied to C.10.

I suppose they do this to have less RMA requests, which still happens with their own firmware....

I really don't know what to suggest you, apart that request support from them...
[OnePlus Nord 2 5G] TheKloras:
wouldnt disabling a feature that let you restoring the rom make more rma requests since if you softbrick there isnt really a way to restore it? thats like so stupid
[Samsung Galaxy Z Fold 4] Mark:
Hi all,

As we know MS has released and has been maintaining an ARM version of Windows for a while now, I was curious if anyone knew if it was possible to dual boot the ARM version? If dual booting isn't an option, what would be the best way to run it? I'm not worried about performance as such, as it's not something I plan to really use until KVM is supported for more than the pixel anyway, I was purely looking to test and see how it would look on such a device.

Any recommendations would be appreciated.
[Samsung Galaxy Z Fold 4] fonix232:
Dual booting is 99.999% won't work - the ARM image maintained by Microsoft is incredibly limited and lacks a lot of drivers, drivers that one would need to write from scratch, since they don't exist for Windows.

Virtualizing it would be possible on Android 13's new built in emulation stack, but you'd still need to root the phone for that, and beyond losing warranty in many places, you'd also lose access to a number of functions.
[Samsung Galaxy Z Fold 4] Free Flow:
Has anybody on the Android 13/OneUi 5 Beta managed to root their device and try if the KVM feature works on the Z Fold 4?
[Samsung Galaxy Note 20 Ultra Questions & Answers] bingblop:
So, sideActions which is/was the only reliable app that could remap the Bixby key on a Note 20 to a plethora of options is now gimped a bit with OneUI 5 Android 13 due to Google's restrictions through tightening of privacy and security.

The way sideActions works in Full Remapping mode (where Bixby Voice is disabled allowing instant actions) is by reading the logcat generated by system logs. So whenever a long press is generated on the Bixby key, the logcat outputs a command that sideActions picks up on. This is a special permission granted by android.permission.READ_LOGS and WRITE_SECURE_SETTINGS through a one time ADB command.

The problem now is that Android 13 no longer seems to allow logcat access after a reboot, nor does it allow access without explicitly granting that ADB Command and THEN ALSO going in the app and accepting the permission prompt to access logs which I'm still not exactly sure how to get that prompt to appear when I want it to. Without accepting that prompt, sideActions won't recognize a button press on the Bixby key in Full Remapping. I'm sure other apps that rely on logcat reading have the same issues.

Does anybody know the workaround for granting log access permanently? Meaning that it will persist through reboots since currently, the prompt only offers "Allow This Time Only". At the very least, how to get the prompt to re-appear following a system reboot so permission can be given until the next reboot? I can only seem to get it to appear randomly following ADB commands.

The alternative to sideActions is using Bixby Routines (now called Modes and Routines) to remap the Bixby key. However, the response time is much longer due to being unable to shorten the long press action time. If you're like me, holding down a button for 2 to 3 seconds feels like an eternity when you're used to 350 milli-seconds (practically instant and is customizable through sideActions settings menu with a range anywhere from 350ms to 1500ms), especially when you use it frequently.

Edit Solution: Figured it out. Just remove the files permissions for sideActions and accessibility permission and then force close it. When you open sideActions again and enable the Bixby key, it'll prompt you to grant 1 time log access. That'll last until your next reboot.
[Samsung Galaxy Note 20 Ultra Questions & Answers] bingblop:
Figured it out. Just remove the files permissions for sideActions and accessibility permission and then force close it. When you open sideActions again and enable the Bixby key, it'll prompt you to grant 1 time log access. That'll last until your next reboot.
[Samsung Galaxy Note 20 Ultra Questions & Answers] Mikehawk595:
I feel you. Having this exact same issue. Very odd, hopefully we'll find a workaround. I'd really dislike to go back to using Bixby Routines to remap the key. I've been spoiled by sideActions.
[Samsung Galaxy Note 20 Ultra Questions & Answers] mark:30::
even after doing this, volume buttons do not work properly, unfortunately
[Samsung Galaxy Note 20 Ultra Questions & Answers] LXative:
Found this thread while trying to fix my S22 Ultra so sideactions would work again. I ended up wiping data on side actions and bcactions, then uninstalling both apps. I reinstalled bcactions and sideactions (from APKmirror, since Play said my phone was incompatible). I went through the initial setup again like you do on a new or wipef device, and when you connect to your PC and run sideactions.exe, you get the script permission and are able to map or full remap your buttons. Literally took less than 5 minutes, working again now for me and I'm happy.
[Samsung Galaxy Note 20 Ultra Questions & Answers] bingblop:
Just so everybody is aware, there is a workaround to get sideActions working again but it must be done after every reboot.

Basically, the goal is to get the prompt asking for one time log access. That'll give SideActions the access it needs. To accomplish it on Android 13, make sure sideActions doesn't have file access and accessibility service is disabled. Next time you open the app and toggle the side button key to on, you'll get the prompt. The key things here are accessibility disabled and file access off.

Also, I highly recommend App Ops or similar ADB permission toggler to grant sideActions full remapping access without connecting to PC. All it does is run a few ADB commands.. can be ran anywhere. I like App Ops because you can manually toggle Secure Settings and Read Logs on. I uninstalled Bixby when I got the device but you can do that too.
[Samsung Galaxy Note 20 Ultra Questions & Answers] LXative:
Think my issue was that I was giving bx/side full permissions. I reinstalled and didn't give full access to either, got the prompt immediately. This will keep me working until something can be figured out, but it doesn't sound promising with UI 5. :(

Thanks!
[Samsung Galaxy Note 20 Ultra Questions & Answers] Ocraftyone:
Another arguably simpler way is to go into app info and force quit the app. When you open the app again, it prompts for log permissions.
[Samsung Galaxy Note 20 Ultra Questions & Answers] xclub_101:
After the March security update it is no longer able to intercept the Power button but is OK for Volume on S23U??? Weirdest part is that it keeps working for both buttons on S22U after same update. Both phones still need the kill + give log permission routine after each restart but on S23U the Power button no longer seems to be intercepted :(
[Samsung Galaxy Note 20 Ultra Questions & Answers] bingblop:
Because of how unreliable and flimsy the logcat prompt was, I decided it was time to move on. Now I'm using RegiStar, coupled with Tasker to achieve my goal.

The RegiStar response time is a little bit longer, but not as long as Routines+. That's really the only downside if you couple with Tasker. If you're not familiar with Tasker, it's an automation application that allows you to accomplish anything you want on phone that doesn't require root access. The latest Tasker beta also includes a flashlight action that is twice as bright as the native built in flashlight setting. So I created a task to vibrate for 25ms followed by toggling the flashlight. That's my long press.

Double pressing the power button is customizable from advanced settings. Can use Tasker action for this too if you want.

The slightly longer delay in triggering long press I've gotten used to and I've come to find that remapping the power key without sideActions isn't so bad.

If you need help with Tasker, PM me. It can be overwhelming at first but I've been using it for a few years now and I love it. Otherwise, RegiStar also includes native actions that you can use instead.

If you're someone who uses double press and hold option within sideActions often, then sideActions is you're only option. Nothing else offers that level of integration. For volume key remapping, almost any third party application supports this. Only power key remapping is limited with Galaxy devices.
[Samsung Galaxy Note 20 Ultra Questions & Answers] BigBadBoogie:
My problem is that s22 ultra keeps turning of in my pcket.

Long press power works

But press power + volume down still pops ppwr of menu and i think this ks why my phone power of every day at work (tight pocket lot of crouching).

I though samsun had poclet check and disabled buttons but doesnt seem like it and bx.and side doesnt help on this last issue
[Samsung Galaxy Note 20 Ultra Questions & Answers] sosimple:
Is there a solution don't have to give this one time permission every reboot, if we are rooted?

Isn't any root command to bypass this?

Thanks
[Samsung Galaxy Note 20 Ultra Questions & Answers] Coldblackice:
Surely there must be a way to modify the time delay? Especially when apps like Galaxy-MaxHz are able to modify settings like custom resolution and particularly custom modding the animation scales to lower/higher than possible in Settings.

Yep, using this simple LSPosed module:

禁用日志访问请求(DisableLogRequest)

Automatic approve for app to access device logs (Android 13+) 自动同意应用访问设备日志 (Android 13+)

modules.lsposed.org
[Samsung Galaxy Note 20 Ultra Questions & Answers] Coldblackice:
Is sideActions still working for anyone? I cannot get the power button to work anymore (when using full mapping), only the volume buttons work. If I revert full-mapping back to the "gimped" mode -- meaning Bixby is enabled -- the power button shortcut works, although obviously with the less responsive/longer delay.

Anyone know how this can be worked around? I know RegiStar exists, but SideActions has much more functionality and customization possible, particularly binding variations like double-presses to separate actions.

EDIT:

Got it working, and still continues to work. I just have to force-close it on each reboot. Same thing with "ClipStack", which is also able to continue working, thank goodness.
[Google Pixel Watch] Motawa88:
Is it possible and can someone do it? Please? :)
[Google Pixel Watch] Quad_Plex:
I actually included a dump of a bunch of the Pixel Watch sounds alongside the apk dump I did on reddit, although I don't believe I've managed to find all of them, there's a good variation of sounds in there to use as notification sounds

https://www.reddit.com/r/WearOS/comments/y3rosv
[Google Pixel Watch] Motawa88:
Thanks!!
[Google Pixel Watch] Motawa88:
do you know if its possible to change the charging sound on a galaxy watch 5? I want to use the pixel watch sound
[Google Pixel Watch] Quad_Plex:
The Charging sound? Oof, Probably not. I believe that is handled by its own Samsung App, which displays the charging interface, so unless you decompile that app, replace the charging sound, recompile it and somehow get it to install without root, I don't think that's possible
[Google Pixel Watch] mdianov87:
Download from here

For Phone:

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

For Watch:

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

I hope you can help and not just ask questions.
[Google Pixel 7 Pro] zuiffon:
Hello

I have random wake up for some seconds with my Pixel Pro 7.

I have disabled all options that can be disabled, it's really random, if I move the phone or touch it, it doesn't wake up.

Is not notification too.
[Google Pixel 7 Pro] zuiffon:
Noone else have this problem ?

Is my Pixel faulty ?
[Google Pixel 7 Pro] Shebee:
Have you tried to reset the phone or contact support?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I haven't noticed any particular issue like this.
[Google Pixel 6] Darkeligos:
Hello. I've updated my rooted Android 12 Pixel 6 a couple of times using These methods in the past, but this time I'm getting a very different outcome. I believe its because the OTA force-installed itself one day, and I lost root with it.

After executing 'fastboot update --disable-verity --disable-verification image.zip', my phone bootlooped. I tried factory resetting, which gave the same bootloop. Then I tried removing the disable verity and disable verification and then it said my phone was corrupt.

I've tried using the Pixel flasher tool and the Android Flash Tool, but after seemingly successful writes to partitions, I get booted into Fastbootd and then get an 'Error communicating with your device'. It always happens once it gets to Fastbootd.

Am I totally bricked?
[Google Pixel 6] ne0ns4l4m4nder:
For me it was an issue with the cable or usb port I was using
[Google Pixel 6] Darkeligos:
Sigh...you were right. I had been trying multiple ports and cables, then decided to plug it into my powered USB hub. Worked like a charm. After getting into fastbootd, it continued unpacking 'product' and other files, which never happened before this time.

It all boots now. Thank you!
[Google Pixel 6] ne0ns4l4m4nder:
You got it. I've found I can't use front IO panels most of the time. Maybe because of power constraints. 🤷‍♂️ No idea, glad I could help
[Galaxy Tab S2 Q&A, Help & Troubleshooting] edevoucoux:
Hello,

I am, currently unsuccessfully, searching the web for update files (OTA updates) of LineageOS 17.1 (updates applied via its integrated updater).

The context :

I'm using a Samsung Galaxy Tab S2 SM-T813 (gts210vewifi) tablet that I flashed (customized) with LineageOS 17.1.

It has worked perfectly since then and I regularly update the OS with OTA updates via the updater without any problem (these updates are frequent: once a week!).

The last update I did a few weeks ago also went well, but it was when I came back into the system that I made a mistake: I think I used a boot.img file incompatible with the update I had just performed in order to re-root the tablet.

After having flashed the resulting file to do so and rebooted, I went into a bootloop on the LOS logo.

The considered solution:

Here is my trouble. I'm almost certain to 'resurrect' my tablet by flashing via TWRP one of these OTA updates which, during this process will replace the incompatible boot.img with the one contained in the update, thus restoring the situation and allowing me to reboot into the system to start again on this new basis and to be able to make a report of the potential damages.

So, that's why I'm looking to find where these OTA update files for LOS 17.1 can be accessed and downloaded on the web. (which repository, ...).

If anyone of you has already faced this kind of issue (or not) and know where to find these files, this will help me greatly!

Anyway, thank you already for paying attention to my request for help in this matter.

Rgds

Eric
[Galaxy Tab S2 Q&A, Help & Troubleshooting] bluess57:
The URL to the OTA server which was baked into the ROM will be inside one of the .prop files (build.prop/default.prop/?).

The OTA URL also shows up in logcat when manually triggering an OTA update.

None of this is likely to help you since you are not booting.

Do you have a copy of a lineageos .zip that you flashed from ?

You'll need to contact who is providing your device ROM
[Galaxy Tab S2 Q&A, Help & Troubleshooting] edevoucoux:
Hello bluess57,

First of all, many thanks to answer my topic.

Regarding your two first points, you're right: I have only access to the external SDCard and the internal SDCard except its system files via my PC.

Unfortunatly not: I delete these update files as soon as they are successfully installed (which is another error of mine), but if it was the case, I couldn't access to them since they are downloaded in a system folder (/data/lineageos_updates or something like that: can't remember nor verify). The update process is automatic thanks to the updater: it lets me know that there is an update, letting me click to download it and after to install it, and then it does the job without any intervention.

This LOS is an UNOFFICIAL one, so I can't contact LineageOS team (even if it is possible ?). I've searched and not found a solution on the web, that's why I'm now looking for help on forums.

Thanks again for your answer and if you, or anyone else has any idea to help me thanks very much.

Rgds

Eric
[Moto Edge X30] hk56184172:
I used to fix ims with phh settings,and the phone call is working,also can send message.but cant receive the message.......
[Moto Edge X30] albertordzcz:
can you make an outgoing call in volte 4G?
[Moto Edge X30] hk56184172:
Yes.LTE is working and can make an outgoing call.Just cant receive message
[Moto Edge X30] psychedelicNerd:
Not related to gsi, but i had this issue on the regular Chinese Rom. The thing that fixed it for me was switching the sim back to old phone and then back into the Motorola phone. It used to be very frequent in the past so i would send a message to myself to check if things were working. Doesn't happen anymore. You said the lte calls work. What is your career and country?
[Moto Edge X30] hk56184172:
I'm in china now
[Moto Edge X30] BGF12:
Volte is working on your phone? In which country do you live?
[Moto Edge X30] BGF12:
Volte is also working for me! And I can send and receive messages!
[Moto Edge X30] OpenAL:
Well, well, well! Let me tell you about @karandpr - this person is a real VoLTE ninja! They know all the ins and outs of Voice over LTE (VoLTE) and can troubleshoot any issue faster than a speeding bullet. With their superpowers, they can ensure you have crystal-clear voice calls on your LTE network. So, if you want to make sure your VoLTE game is on point, look no further than karandpr!