yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] 96carboard:
Losing features? Aside from hardware, the ONLY feature that matters is being able to clear out all the google-spyware and run a pure AOSP.

Hardware-wise, some reasonable level of performance and a screen that is *nearly* as wide as a Nexus 6 is what I'm after in it. Would be nice if the screen was equal or even better, bigger than N6, but it seems that all the dainty fingered fairies that work for Google can't picture what is needed for comfortable use by man-hands.
[Google Pixel 6 Pro] znel52:
Twenty twenty twenty-four hours to goooo.
[Google Pixel 6 Pro] 94b20gsr:
I wanna be sedated!
[Google Pixel 6 Pro] znel52:
Just hope the google store doesn't melt down tomorrow. Seems to be a lot more interest in this pixel over any of the others they have released. Just hope they are prepared 😂
[Google Pixel 6 Pro] dmb219:
I was looking at that case too along with a Caseology but I think I like the Spigen better, I'm glad I saw your post. Happy Pixel day!
[Google Pixel 6 Pro] znel52:
I liked the caseology parallex with the black and gold but couldn't find it in stock. Didn't like the other colors they currently have. Went with the spigen for now probably get the caseology later.
[Google Pixel 6 Pro] dj24:
First time potential Pixel owner. Can prior owners share with me what a Pixel's battery looks like generally? Mostly during stand by times and during usage without having to go through extreme decluttering?

What kind of SOT should one potentially expect with the Pro's 5005mAh battery ?

Thanks!
[Google Pixel 6 Pro] bobby janow:
Sounds like you are a typical user and not someone streaming 24/7. In that case you will never need to charge it during the day. You actually should get a full 24 hours but we shall see with the new chip.
[Google Pixel 6 Pro] znel52:
Sadly they were not prepared and the store did in fact melt down.
[Google Pixel 6 Pro] gettinwicked:
So, I went to Best Buy today and looked at one in person. I gotta say, I'm even more excited now! I only had a couple minutes, so, I didn't get to try everything, take pictures, etc.. I'm exited for the bigger phone than my 4xl. I have big hands/thumbs, so typing can be a pain in the a$$. This phone looks like it will be good for me there. The camera bump is NOT as pronounced as it looks like in some pictures. It was not bothersome at all while holding the phone. But, the back of the phone is glossy, and a fingerprint magnet. It felt a little gross to be honest. You'll definitely want a case on it. The screen is gorgeous. It had a wallpaper with a lot of white on it, and dark mode was set to off, so I was able to see if it had any blue tint, or major fading as I tilted it (looking at you 2xl). I *think* the screen won't be a problem, but again, I didn't get much time with it. There was zero lag as far as I could see, for the phone and the screen. Very fluid. You can definitely tell the difference between its 120Hz and my 4xl 90. I did get a moment to check out the camera. The zoom looks pretty good. Went in to 4x and the picture was about as clear as at 1x. That's about all I got though. I ran out of time for my lunch for work. I'm counting down the days until it comes!
[Google Pixel 6 Pro] Aridon:
I have a pro on order but I'm concerned and will be reading reviews carefully. I'm sure to get it the 28 to the 3rd.

Google has a bad record hardware wise and s new chip is a big deal. There are likely to be some compromises and the videos we've been have been on the ****ty side. Lots to be concerned about.
[Google Pixel 6 Pro] freebee269:
I just went into my local Best Buy and played with one. I took some pictures snapped a video or to the test out the stabilization and just looked over the device. I have to say I am impressed with it. You can tell it is much lighter than my current phone which is the iPhone 13 Pro Max. those pictures were very vibrant. And I was pleased with the stabilization and the videos although I couldn’t really get much of a test because I couldn’t walk around with the phone. But it was very snappy in the UI and I turn the brightness all the way up on the screen and in my opinion that’s plenty bright for me. Playing around with this phone makes me want it even faster now lol.
[Google Pixel 6 Pro] lawtq:
This makes you want to discard your pro max?
[Google Pixel 6 Pro] freebee269:
I’ve been looking for something on Android with vanilla Android the way Google intended that would make me go back. This phone does it for me. On iPhone I use most Google services anyways. The only thing that kept me on the iPhone was video quality. At my job I record a lot of video with my phone. Samsung and Google were lacking in this category. From what video I took at Best Buy I can tell Google has done some work on their quality. Going to sell my 13 pro max when my pixel 6 pro arrives. I’m looking forward to it.
[Google Pixel 6 Pro] dj24:
You are the exact person I'm looking to get feedback from. In short, Iam waiting to find out if the Pixel 6 pro will match the 13 pro max in regards to SOT/ battery life before I decide which one of these two to purchase. Could you come back and provide your thoughts regarding this on a thread I created here once you get your 6 pro?

Thanks!
[Google Pixel 6 Pro] freebee269:
Sure. But my delivery date is nov 12 😒
[Google Pixel 6 Pro] dj24:
No problem. I'll try my best to hold out with my aging Note 20 Ultra till then :)
[OnePlus 8 Pro Questions & Answers] nayhtoo:
I have tried flashing it twice, both time it didn't work. Is there any solution?
[OnePlus 8 Pro Questions & Answers] dlads:
There's a massive thread about this in the q+a or guides section..

May be your persist.img

There's a guide to fix it
[Moto G 5G Plus Questions & Answers] fcuevas40:
i bought it in November 2020 in Spain, but the phone is from Italy. I am waiting for android 11 OTA for months, but no notice...
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] itspdp:
Hello Guys,

We know, Some App in Our Devices doesn't allow us to Take ScreenShot.

and We See an error saying "Couldn't Take Screenshot" OR Similar.

I'm Creating This Post Because I haven't Found Any. (I'll try to make it Up to date, Specially for whichever ROM I'll be Using in the Future).

So I Made a Magisk Module using The Smali Patcher 👈

It will allow the User to Take ScreenShot in Protected Apps.

Just Flash it From MAgisk and Enjoy ;)

Currently Only Available for Xiaomi EU Beta 21.5.12 ROM

Download Link:- Click Here

If you Want to Make For Your Device/Rom, You Can Use Smali Patcher,

Follow The Instructions from The Post. Click Here.

Please Comment Down for Issues OR Suggestions.

You can Contact Me on Telegram @itspdp

Click on That Thank Button, If It was Helpful.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] zgfg:
Thanks, interesting

I remember I encountered an app or two not allowing screenshots - but I forgot now, can you please tell which apps to test with

Btw, I have Mi 9T (not Pro) and Xiaomi.eu 21.5.20 (davinci was 'delayed' a week later than your raphael), but I think the module should work as well

Btw, as I can see, changes should be systemless, hence if anything goes wrong just disabling the module (and reatarting the phone) should be enough to go back to 'normal'
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] itspdp:
Y

Yes Everything will be Systemless, we can try, if anything goes wrong we can remove that module (Even from Recovery)

Use The Smali Patcher to Make Modulw for Your Device.

(Link and Tutorial already inside the post),

It's easy and will take about 5-10 minutes only.

P.s. :- This Module is Device and Rom (Including Version) Specific, You Have Make For Your Own Rom/Device amd Update it with Each OTA Update of Your Rom.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] zgfg:
After some troubles with the PC, I was able to run Smali Patcher to create a module for my Mi 9T, Xiaomi eu 21.5.20 - do you know please a (system) apk in Xiaomi.eu that does not allow screenshots, that I can test with and without the module, to check does it work
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] ca_guri01:
Try Chrome incognito mode
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] zgfg:
Thanks, I tried Chrome Incognito window with the my Smali patch module disabled and it complained that screenshots are not allowed

I enabled the module, rebooted and tried again, and it successfully made the screenshot

Thanks, it works (Mi 9T, Xiaomi.eu 21.5.20, Magisk v23)
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] zgfg:
I don't know what's wrong now - I tried to repeat everything with Xiaoni eu 21.6.9:

- Connected again my phone to (the same PC), ran SnaliPatcher (as admin) again, successfully created a module for Secure Screenshot

- Module installls from Magisk app with no errors (everyrthing the same as when did first time for 21.5.20)

But when I reboot, it fails and after a long time staying on MIUI splash screen, it eventually reboots to TWRP.

I have to remove the module to be able to boot

Tried two times (rebuilding the module by SmaliPatcher, installing the new module), no success
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] zgfg:
Managed to make the module again with Xiaomi.eu 21.6.16:

- I used SmaliPatcher to create the module before (!!!) I installed Magisk.

That is, I installed Xiaomi.eu 21.6.16 and used SmaliPatcher to create the module for Secure Screenshot, only then I installed Magisk and finally installed my SmaliPatcher module - it boots properly to Magisk and Secure Printing works

I think this is the same way I also successfully used SmaliPatcher with Xiaomi.eu 21.5.20

However, when I was on Xiaomi.eu 21.6.9 and when I reported a bootloop, I did it by slightly different order:

- I upgraded to 21.6.9 and immediately installed Magisk, then I used SmaliPatcher to create the module, installed the module and rebooted, but instead of to system it eventually booted to Recovery (TWRP)
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] verydp1:
This is actually what I was looking for. Btw some apps don't allow us to copy / paste, could you help me with this problem?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] zgfg:
Settings, Apps, find your app, Permissions and enable Access items in the clipboard
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] remorze:
this give me a bootloop, anyone know other apps that can do Secured ScreenShot
[Redmi K20 Pro / Xiaomi Mi 9T Pro Themes, Apps, and] zgfg:
Magisk module as attached to OP post will work for you only if you have Mi 9T Pro/Redmi K20 Pro with Xiaomi.eu 21.5.20 (exactly that build)

Otherwise you have to install SmaliPatcher to PC, connect to your phone and follow instructions for the patcher to make yourself the Magisk module for your phone

I don't have Pro but 'plain' Mi 9T, and I'm on newer Xiaomi.eu builds, hence I had to do myself Magisk modules three times (Xiaomi.eu weekly releases).

First time it worked fine for me, next time I also had the bootloop when I made and installed the module (AFAIK, I was following the same patching procedure, with the same phone and PC, hence I don't understand why that time I had a problem). Third time again everything was ok (I got the module for Magisk that does not produce bootloop and it 'unlocks' screenshoting from the apps otherwise not allowing)
[MX Player] gururoop:
I've noticed that pause/play using Bluetooth earphones' buttons is not working in any version of Android 12 (tested on every version, from DP1 till PB1). The sound is muted for a few seconds, but the video continues playing. I've tried both free and pro versions and tried toggling the settings. The same problem also exists in Facebook app but not VLC player nor XPlayer.
[MX Player] MXPlayer:
Please collect a bug report from the help menu on the playback screen quickly after reproducing the problem and share it with us at support@mxplayer.in along with a reference to this thread link. Once received, we will investigate this further and get a workaround for your issues.

Thank You.
[MX Player] gururoop:
Just an update, the bug is not resolved in Android 12 Beta 2, which was released yesterday.
[MX Player] Thirumalai.K:
We apologize for the delayed response.

Based on the information provided, there seems to be a bug in Android 12's MediaPlayer implementation. Please select HW+ Decoder from the menu options on the playback screen and let us know if it fixes your problems.
[MX Player] gururoop:
The problem is not solved by choosing HW+ decoder. I understand that this problem is in Android 12 (because the same problem exists in videos on Facebook app), but some other media players like X Player and VLC seem to have apparently found a workaround the issue. Good luck with that. I am really missing my favourite media since Android 12 DPs started coming out.
[MX Player] gururoop:
Just an update. The problem is not resolved in Android 12 Beta 2.1 which was released today.
[MX Player] gururoop:
Any update on this problem? Its not fixed by Google in betas 3 and 3.1. Have you guys raised a bug report with Google?
[MX Player] gururoop:
Just an update, this problem is not yet been solved. I have tried every monthly patch of Android 12, 12L Beta 3 and now Android 13 DP1. The reason I keep on checking MX Player Pro if they fixed it after every update is that it is awesome and still much better than VLC Player and X Video Player, both of which have found workaround to this issue. I hope and request the developers fix this issue so that I can get back to using my favorite player since more than 10 years again.
[MX Player] gangpe:
Same here. I've pinged the devs via tickets a few times with the logs attached. Heartbreaking considering other players are able to use the Bluetooth controls. Hope they fix this soon; I'll buy the pro version once they do.
[MX Player] Batman1302:
Friends, the same has happened to me. It's a horrible mistake, I thought it was a problem with my cell phone. MX Player is very important to me because it's the only one I use to watch classes, due to the perfect compatibility with MixPlorer. Could you please let me know when the bug is resolved? I'm considering staying with the BS Player while they don't solve it.
[MX Player] slamming_sammy1:
I have a Samsung Note 10+ and bluetooth control is still not fixed. Please fix soon.
[MX Player] Renate:
You need to break this problem down.

Get UsbMode.apk out of my sig. Figure out what keys your headphones send.

Then, try to send the keycodes manually with ADB.

$ input keyevent 126
$ input keyevent 127
$ input keyevent 85
$ input keyevent 85

That's Play, Pause, Play/Pause

Your headphones may be "Apple compatible" and send out multiple keypresses just to be stupid.
[MX Player] slamming_sammy1:
ok but why does it work with other apps like the built-in samsung music player; also downloaded a podcast app called podkicker and that works like a charm
[MX Player] Renate:
Just a stab in the dark, I would guess that your headphones are sending multiple keys.

That can be hard to see in my UsbMode.apk but if you press the key enough times you'll see wonkiness.

In any case, if the manual key insertion works responsibly you can guess what's happening.

Reverse engineering and flashing the headphones can probably be done, but it is a bit of a project.

I do that to all my BLE keyboards because I hate stupid identifier like "Anker 1234".

I prefer "English" and "Russian".

(Although, since the start of the year I don't use the latter keyboard.)
[MX Player] slamming_sammy1:
it's not the headphones. I've tried 5 to 6 different bluetooth devices and they all don't work; but they all work with other apps; it's the app
[MX Player] Renate:
That all may well be, but until you narrow the point down your bug report will go nowhere.

Did you even try keyevents? How do you know that all your headphones don't generate multiple keyevents?
[MX Player] slamming_sammy1:
ok I can give it a try. but I don't know how to do this:

Then, try to send the keycodes manually with ADB
[MX Player] Renate:
Do you have ADB enabled? No? Google it.

C:\>adb shell
$ input keyevent 85
[MX Player] leo46:
I noticed the same problem and am willing to help debug it.

I am using Pixel Buds Pro with a Pixel 6a with Android 13.

I downloaded & installed USB Mode but unfortunately I don't see any key printed when triggering the pause control on the earbuds. Using ADB shell to send key events show them as expected. Could it be that these earphones use another mehcanism to send play/pause events?

I created an issue here describing which apps work and which won't, maybe this can help:

Play pause not working in all apps - Google Pixel Buds Community
[MX Player] Renate:
Oh, I was thinking that headphones were just using HID (7 keyboard or 0xc consumer) over Bluetooth.

I've verified that they are using AVRCP instead.

I dug out my old Bluetooth headphones to give this a whack.

It's got some wacky multifunction knob/switch that I was never sure exactly how it worked.

My /system/usr/keylayout/AVRCP.kl is conspicuously missing:

key 164 MEDIA_PLAY_PAUSE

So I put it in. (You must be rooted or Magisk or something.)

But... I commented it out and it still worked!

So it must be using Generic.kl

Also, I never see headphone buttons in UsbMode.apk even when they are working.

I have a footpedal that generates MEDIA_PLAY and MEDIA_STOP and I see them.

But that uses HID 0xc consumer controls.

Still, maybe your system is doing something different.

It might be worth trying to edit AVRCP.kl

I looked at this some more. "Media buttons" get dispatched a little bit differently, that's why UsbMode.apk didn't see them.

android.intent.action.MEDIA_BUTTON

https://developer.android.com/guide/topics/media-apps/mediabuttons

I'll look at this some more.
[MX Player] leo46:
Let me know if you need help: I can do more tests if needed.
[MX Player] Renate:
Well, try this:

$ cd /system/usr/keylayout
$ grep MEDIA_PLAY_PAUSE *
[MX Player] Renate:
So, here's another wrinkle, at least on my Android 10.

The AVRCP over Bluetooth gets sent to the MediaSessionService.

That service figures out who is the most "media like" and send it KeyEvents (i.e. key strokes).

It never sends a MEDIA_PLAY_PAUSE. Instead it attempts to keep track itself and injects KEYCODE_MEDIA_PAUSE and KEYCODE_MEDIA_PLAY alternately.

MediaSessionService: Sending KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_MEDIA_PAUSE, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=0, downTime=0, deviceId=-1, source=0x0, displayId=0 } to the last known PendingIntent PendingIntent{8401405: PendingIntentRecord{a403c5a com.simplemobiletools.musicplayer broadcastIntent}}
...
MediaSessionService: Sending KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_MEDIA_PLAY, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=0, downTime=0, deviceId=-1, source=0x0, displayId=0 } to the last known PendingIntent PendingIntent{8401405: PendingIntentRecord{a403c5a com.simplemobiletools.musicplayer broadcastIntent}}

So try this and push some buttons.

$logcat *:s MediaSessionService
[MX Player] leo46:
Here are the grep results in case you still need them. I'll send the logcat later.

Generic.kl:key 164 MEDIA_PLAY_PAUSE
Vendor_046d_Product_b501.kl:key 164 MEDIA_PLAY_PAUSE
Vendor_05ac_Product_0239.kl:key 164 MEDIA_PLAY_PAUSE
Vendor_0957_Product_0001.kl:key usage 0x000c00CD MEDIA_PLAY_PAUSE
Vendor_1949_Product_0401.kl:key 164 MEDIA_PLAY_PAUSE
Vendor_22b8_Product_093d.kl:key 164 MEDIA_PLAY_PAUSE
Vendor_2378_Product_1008.kl:key 164 MEDIA_PLAY_PAUSE
Vendor_2378_Product_100a.kl:key 164 MEDIA_PLAY_PAUSE
qwerty.kl:key 164 MEDIA_PLAY_PAUSE
[MX Player] Renate:
Thanks, you don't need to copy the logcats, just say if they are basically the same as mine.

Edit: Well, this gets weirder and weirder.

Some big wired USB keyboards have those Stop, Play, Play/Pause buttons at the top.

I didn't have one, so I made one. :p Just a little micro that can do the consumer controls.

Like you posted, 0x0c00cd, 0x0c00b0, 0x0c00b7

These buttons show up fine in UsbMode.apk, but the funny thing is, my cheesy player app ignores them.

*Also Firefox playing an MP3 ignores it all too.

It's only paying attention to the stuff dished out by the MediaSessionService, which is stupid.
[MX Player] Renate:
Ok, just clarify for me @leo46 what the problem is now.

You've got all those PLAYs and PAUSEs using your normal headphone controls, but com.mxtech.videoplayer.pro is not responding?

Does it not work even when the player is in the foreground? (There are complications with background.)

What a tangled mess.

Ok, do you know (and love) apktool?

Take apart your app and look in AndroidManifest.xml

Look for receivers with android.intent.action.MEDIA_BUTTON

Is it there?

For the adventurous, rebuild the app (with apktool) with the only change

android:compileSdkVersion="25"

See also: https://developer.android.com/about/versions/oreo/background#broadcasts
[MX Player] Renate:
So, here's a little app to experiment with.

Put some music in your player and pause it.

First try with nothing typed in the top edit control. Do the controls do anything?

Next, type the package name of your player in the edit control. Do the controls do anything?

If nothing yet, app switch to your player then app switch back to my app. Do the controls do anything?

For extra credit, try using the version 25 remade player.
[MX Player] vitmac:
On my experience mx player have never responded to any of my 3 Bluetooth headphones play/resume button on android 12 when seeing videos on foreground. Other apps do respond to it. I'm using a Galaxy Z Fold 3.

When I pair these same headphones to my older galaxy devices (android 11 or lower) mx player responds fine to the button.
[MX Player] Renate:
The plot thickens:

I have now a USB device with 3 buttons, stop, play, play/pause

I have a Bluetooth device with 3 buttons, stop, play, play/pause (this is not using the AVRCP protocol).

The USB version works properly, they're just buttons, appear in UsbMode just fine.

The Bluetooth version on stop and play works the same but play/pause get screwed up and the ACTION_UP gets supressed.

Neither version works with a stock media player because they're both just listening to Intents, not KeyEvents.

Also, note that 0x0c00b1 (Consumer control media pause) does not work at all because there is no media pause in Linux, although there is MEDIA_PAUSE in Android.

<slaps forehead>

TLDR: Your player app probably needs to be updated to use registerReceiver instead of relying on AndroidManifest.xml
[MX Player] leo46:
That's it: I am trying to play/pause using my bluetooth headphones controls. Foreground or background does not change: MX Player doesn't react to play/pause.
[MX Player] leo46:
Just downloaded the app and started playing a sound in MXPlayer pro:

- with the empty edit control, the buttons do not work

- with the edit control filled with the package's name of mxplayer the buttons work

Note that installing/starting the app shows a warning saying the app was created for an older version of Android.
[MX Player] Renate:
That may be part of the reason why it works...

Somebody needs to do a deep dive into the app that doesn't work.

At the very least take a peek at AndroidManifest.xml as I mentioned above.
[MX Player] MikeOShay:
I haven't had time (or perhaps capability) to go in and do any of these deeper troubleshooting steps, but I can confirm that with MX Player Pro v1.46.10 (ARMv8 NEON), the media buttons do nothing with every Bluetooth device I've tried (2 types of headphones and my car). Media controls work as expected with all other players.

Here was my original report: https://xdaforums.com/t/bug-bluetooth-media-buttons-not-working.4454321/

I have the app running in a Google Pixel 6, Android 13. It worked fine on my previous phone, a Samsung Galaxy S7, not sure what version of Android.

I've found a single condition where a Bluetooth button works. If the app is playing in the background, the Pause/Play button will Pause, but cannot resume.
[MX Player] Renate:
Aw, it's easy. Go to my sig and under "Android Tools for Android" is binxml

C:\>adb push binxml /data/local/tmp
C:\>adb shell
# cd /data/local/tmp
# chmod 755 binxml
# cd /data/app
# ls -l
# cd com.mxplayer.whatever-12345678
# /data/local/tmp/binxml base.apk

Then just copy the tree and attach it or post it.