yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] PrinceMS:
I have everything default.

- FHD resolution (I don't see the difference at higher res).

- Most apps are sleeping but all social media is not. FB, LinkedIn, tiktok, Gmail, outlook.... (Neither banking, etc)

- wifi / 5g always on

- nearby scanning: not sure. Whatever is default? On?

- brightness: auto but regular is 30% inside. It's low compared to most iPhones

- "extra dim" on always in drop down bar

- dark mode always! Dark wall paper

- AOD , always on.

I get close to 8 hours sot.

1d+ use.

Love to get 10 hours. But I ain't fidling with settings, that will reduce connectivity or features (even if I don't use them).

PS: I charge my phone to 85% only. That sot is with adaptive charging and 85% battery stats to protect it.
[Samsung Galaxy S22 Ultra] mkyadav91:
Impressive bro. Any debloat you did?
[Samsung Galaxy S22 Ultra] PrinceMS:
I put all apps that I don't use on daily basis on sleep. I guess they went in deep sleep overtime.

There are two things that kill the battery for me. Maps + Tiktok
[Samsung Galaxy S22 Ultra] haifish9999:
View attachment 5974789

My SOT ( at 5% battery remains) with RAM Plus was disabled. All my settings was maximum with Adaptive enabled all sections (which one was included).
[Samsung Galaxy S22 Ultra] OverplayOfficial:
Daily reminder that the battery highly depends on your signal. In your screenshot you had full bars so that plays a big part in this. As for the adaptive refresh rate, I've been testing this since I got the phone because I had stutters. For me, the 48-96 works best for battery&smoothness and 60-120 for eliminating stutters completely
[Samsung Galaxy S22 Ultra] mkyadav91:
Can you share full screen shot of app battery usage also.

Thank you 👍
[Asus ROG Phone 6 / 6 Pro] AmeNahar:
for your info , asus can detect your devices on their system, if you ever root your device or unlock bootloader, my suggestion : dont try UBL/root if you dont wanna lose your warranty like me :D ...i directly ask the live agent and they detec my device on rooted state eventho i didnt root anymore and relock bootloader :')
[Asus ROG Phone 6 / 6 Pro] TechX1991:
I feel like that can't be true... But I can't contact them on it. Their custom support page doesn't have a USA option for region. I can just lie obviously, but I still feel like that just isn't a thing.
[Asus ROG Phone 6 / 6 Pro] AmeNahar:
im from malaysia and im about to claim warranty ... but suddenly the customer support(live chat) agent said my device has been rooted .. they detect via serial number . 🥲😔 my warranty ends 31/12/23
[Asus ROG Phone 6 / 6 Pro] Andrologic:
Of course they can. That's the whole purpose of the ASUS unlock app - to void your warranty. Your device identifier is registered in their database when you unlock, so you can re-lock the device as much as you like, it won't make a difference.
[Redmi Note 8 Pro Themes, Apps, and Mods] PandoraDev:
So, I have an app which makes u able to take contactless payments and I really like it. But the thing is no matter what I do, I can't get it to work on custom roms. Even modded MIUI is able to run it. I don't have any problems with any other app detecting root/custom rom or whatever. I'm on evolution x 13.

View attachment 5964269

View attachment 5964267

View attachment 5964263

As you can see, I have bypassed safetynet and play integrity checks. It is not the unlocked bootloader or root. Its the custom rom detection. Can you guys please help?
[Redmi Note 8 Pro Themes, Apps, and Mods] khusika:
Hi @PandoraDev

Have you tried hiding it using Zygisk?
[Redmi Note 8 Pro Themes, Apps, and Mods] PandoraDev:
Yes. İt is hidden using zygisk but that didn't help.
[Poco F5 Pro / Redmi K60 (China)] findwalter:
Hi, i recently bought Redmi K60 from china, and i realise system haptic feedback is so weak, i put it in max and still nothing compare to my old poco f2, f2 has more firm haptic.

any chance to increase the haptic strength? maybe magisk module or something?
[Magisk] krakout:
Oh interesting, installed! Now to find some decent music to test...
[Magisk] beeshyams:
Thanks a lot 🙏

Will flash soon. I have V4a, James DSP installed. In theory, will this mess with them?
[Magisk] JoshuaDoes:
In theory, it should improve them! This module is not an effect, and does not do anything like disabling effects. It only changes the configuration used by the speakers, in this case increasing the volume that's digitally set by Google's DSP, and lowering the volume of the hardware amplifier.
[Magisk] acwcanada:
Believe most rooted users are using one or more of these: Viper4Android, JamesDSP and Dolby etc. Any idea their coexisting with your module? Any conflicts between them? And would you recommend or discourage the using of them with yours? Thanks
[Magisk] acwcanada:
Thanks for clarification.
[Magisk] beeshyams:
👍 That's true. Played for a short while.. Good.. Keep it up. Pixel 6a, Android 13. Will revert if I notice heating
[Magisk] TimeToPickUp:
its only for phone speaker correct? not headphones or other bluetooth speakers?
[Magisk] JoshuaDoes:
Yeah, this won't affect anything except for your phone speakers!
[Magisk] Legitsu:
was litterally just thinking about something like t his today

NICE!

is it possible to furter increase the volume while in calls ? voice should not be subject to as much clipping overload and the call volume still kind of sucks
[Magisk] JoshuaDoes:
Goofed the install script for the v1.1 update twice in a row, please update to v1.1.2 using the Magisk app!
[Magisk] Legitsu:
I wonder if this could be made adaptive so we can squeese some more volume out durning calls where clipping isn't as big of an issue
[Magisk] JoshuaDoes:
The new v1.1.2 update also applies to all other mixer fields, give it a try!
[Magisk] Legitsu:
nice do the other mixer fields have seperate amp/pcm gain controls ? if so can we push it a little harder for calls ? the biggest issue I have with this device is the crap volume during calls my ears aren't what they used to be so ill take every bit I can get
[Magisk] JoshuaDoes:
The latest v1.1.2 update applies the new values to all speaker-based mixer paths instead of just standard media volume, give it a try!
[Magisk] Legitsu:
sorry got lost in the pixel6 pro sub again gdam it xda this new ui still sucks... testing
[Magisk] JoshuaDoes:
They are separate fields, but see how this update does for you first, it's already a bit of an improvement. If you're still not satisfied, you can do smth like this:

adb shell
su
cp /data/adb/modules/pixel-tensor-audio-decompressor/system/vendor/etc/mixer_paths.xml /sdcard/mixer_paths.xml

### Keep your command prompt / terminal open
### Copy that file to your computer
### Find the fields you want to edit by searching for "handset", "voice-handset", and "voice-speaker-post"
### Copy it back to your phone's internal storage

cp /sdcard/mixer_paths.xml /data/adb/modules/pixel-tensor-audio-decompressor/system/vendor/etc/mixer_paths.xml
reboot now
[Magisk] Legitsu:
whats the STOP before I launch the speakers out of the phone and into my ceiling max?

*sets everything to 999*
[Magisk] JoshuaDoes:
As noted in the original post, max value for digital PCM is 913, and max value for amp is 20. Just fair warning, although it works and sounds great, you are likely to trigger the DSP's volume normalization (speaker safety feature), so sudden loud noises will reduce the volume ever so slightly for a brief moment. If you can get used to it like I can, good luck!
[Magisk] Legitsu:
hrmm need to figure out how to murder the speaker safety then .... is it a gain safety or are we just running into the peak current limit at high amp gain ?

edit: I think this is ok for me for the moument. someday maby somebody will sit down and write a cli or gui app so we can change this stuff on the fly
[Magisk] innit:
"all other mixer fields" - does it mean you also tweaked bluetooth & wired headphones values?
[Magisk] beeshyams:
Can I make a suggestion?

Not everyone can discern these improvements.

Add a test track that has a variety of musical instruments, a broad spectrum of vocals etc so that one can play before and and after flashing the module.

Just toggling the Magisk module-does it really disable? I always thought a reboot was needed for any Magisk changes to take effect
[Magisk] gpvecchi:
Waiting for the 14 build, thank you!
[Magisk] Shayan69:
Will flash and update how it differs
[Magisk] krakout:
Installed fine on my 14b4, though I have not tested for results.
[Magisk] JoshuaDoes:
The new v1.2.0 build adds Android 14 support! I'll update the original post to mention it
[Magisk] JoshuaDoes:
As with every Magisk module, disabling or enabling a module has no effect until after you reboot.

I also don't really have any good examples for people to use as I can't guarantee people will like the same things I like, so instead I'd advise for you to just listen to the things you're normally used to listening to using your phone speakers, like your favorite songs or your favorite YouTubers. The only real way to test the difference is by listening to what you already know!
[Magisk] beeshyams:
I am convinced about the quality 👌

I was only thinking of others who need proof!
[Magisk] JoshuaDoes:
I have a terminal script using the tinymix Magisk module, I'll see about adding it to the GitHub repo with instructions for how to use it. Also, the safety protection is just handled by Google's digital sound processor software, it's not that the speakers can't handle it but rather that the DSP refuses to allow it, thus resulting in the sudden volume lowering.

No, the values I'm altering do not exist for wired headphones or Bluetooth mixer paths. By "all other mixer fields" I was referencing the mixer paths that do have these values, namely the voice call paths. You can inspect `/data/adb/modules/pixel-tensor-audio-decompressor/system/vendor/etc/mixer_paths.xml` and search for "865" and "14" to find exactly which mixer paths have been altered.
[Magisk] JoshuaDoes:
I'll see about updating the XDA post to make sure people test with what they're already used to listening to, then! I was under the impression that people would infer this themselves :P
[Magisk] hanschke:
I wil test it on my pixel fold
[Magisk] innit:
Will take a look at it, thanks.
[Magisk] bobnot:
Noticable difference 👍🥰
[Magisk] ropapermaker:
Tried on A14 B4.1 and the clarity is quite noticeable!

I also tried higher PCM values but heard clipping so I think your values are perfect
[Magisk] andybot23:
This looks really cool! Other than the phone's speakers, would this module work with Bluetooth audio (i.e. earphones)? Nevermind, see that it doesn't.
[Magisk] gpvecchi:
Wouldn't it be best to maximize the PCM volume and lower a lot the amp volume?
[Magisk] JoshuaDoes:
One would assume so, but the big problem is we don't yet know what the PCM volume matching 100% would be. I need to do a more advanced analysis using a tool to figure out the best possible frequency response curve with whatever set of values, but until then, this was the best I could figure out in my own time that's had no artifacts, clipping, distortion, etc. Feel free to experiment if you'd like! See earlier comments for instructions on how to edit the patched mixer_paths.xml
[Magisk] Legitsu:
with pcm you run into problems with over-driving the circuit so you need both a certain level of input gain from the pcm and a certain ammount of gain on the amp

if we can disable the safety in the dsp code we can play around a bit. likely will need to find in the source tho
[Magisk] zyhk:
I hear a little bit distortion to my ears. If you like, try my magisk module Hifi maximizer as your testbed. I think you could hear the best sound from Tensor devices, e.g., no re-sampling distortion, 100 media volume steps, 48kHz & 32bits configuration and very small jitter.
[Magisk] Legitsu:
100 volume steps is too much. It takes forever to volume change

distortation is not really avoidable phone speakers suck this is the way of things
[Magisk] Seosam:
The moduke doesn't work on Beta 14 4.1 with KernelSU. So I made your changes manually.

And wow, sound much better! Thank you for your work!
[Magisk] bs3pro:
Does this increase the volume when using speakerphone on calls? I wish my speaker was little louder on my Pixel fold.
[Magisk] JoshuaDoes:
I've already tested with "Audio misc. settings" which is also by you, mostly because of it disabling the audio effects framework entirely so I could hear the results with no effects on top, does this have the same effect as your linked module (haven't clicked it yet)? Because on the ROM that I run, I don't get that distortion regardless of whether effects are enabled or disabled. And the ROM that I run is helluvaOS, which already maxes out at 48KHz with packed 24-bit float32, and they've also recently readjusted the MaxxAudio waves configuration which means I might copy that into the module so people are more closely in line with the environment I have.

Are you by chance on the Pixel 7 Pro? A user on Telegram recently recommended changing the amp volume to 12 for that device, and the same may also apply for the Pixel 7. I'm currently working on importing my custom text menu engine into the install script, which will allow the user to test various suggested presets from the community with a live demo before confirming their choice and continuing with the install/update of the module. For obvious reasons they won't be able to test stuff that needs replacing such as the waves config, but they'll be able to find a comfortable volume from the presets and it will apply it until next reboot using tinymix and my custom `phonedac` script that I've been using to wrap tinymix all year. If you'd like to try amp volume 12 before I release this v2.0.0 update, look earlier into this comment thread to find instructions for editing the patched media_paths.xml file. And thank you for your feedback!
[Magisk] JoshuaDoes:
It does in theory but I've yet to place a call to actually test it, would you mind letting me know if it does?
[Magisk] JoshuaDoes:
I'm working on a v2.0.0 update right now that incorporates a custom text menu engine I wrote in Go a couple of years ago for a few separate projects to use. You'll be able to live test from a range of preset values until you find a setting that's most comfortable for you before installing the patch! It should be ready soon, within a day or two. And if you decide you want to try other values too, it's as simple as running the install process again, either through a new update or through a manual reinstall.
[Magisk] Samuel Holland:
It would be nice if we could have a cross pixel category here on XDA, so people could be aware of potential solutions that will work for their device without having to go through each forum besides their original device. Anyhow, I'm glad I found this being on pixel 7 pro, and thank you for sharing this.👍
[Magisk] JoshuaDoes:
Update v2.0.0 is now live! Let me know what you think <3
[Magisk] Fishawy:
Magisk/FoxMMM installer is broken?

Using volume buttons to navigate between options is okay, but tapping the screen to select is not working.
[Magisk] JoshuaDoes:
We're on v2.0.2 v2.0.3 now, but it's essentially the same as v2.0.0 (besides the removal of the preset keycodes and replacement with the keycode calibrator, as the touch screen keycode is different across devices). Magisk has a bug where, even though it works perfectly fine with local ZIP files, any module update downloaded through the Magisk app will fail to execute a binary file, and cannot change the binary to be executable post-extraction.

Unfortunately, this means that all module updates must be installed manually from here on out. I will investigate the Magisk source code tomorrow and submit a pull request to fix it as soon as possible. Until then, I have decided to make the decision to break in-app updates. If you tap on the "Update" button, you will see a warning about this issue instead of the changelog, as well as a link that you can tap which will take you directly to the new release where you can both read the new changelog as well as download the updated ZIP for manual installs. This cannot be helped.

For those of you who were relying on in-app updates, you may find the update linked below in case you didn't get a chance to read the warning in the changelog.

Pixel Tensor Audio Decompressor v2.0.3
[Magisk] JoshuaDoes:
Which device are you using? It's entirely possible that the keycodes on my device are different from yours. If so, I will either need to send you a test module that will tell me the correct keycodes, or I can delete the keycodes file which will allow my text menu to guide you through the keycode calibrator process (which is how I generated the keycodes file live on my device!)
[Magisk] Fishawy:
Pixel 7 Pro.

Perhaps a suggestion to replace "touch screen" with "power button" or "volume up" to select?
[Magisk] cemg92:
Pixel 7 user here. Can confirm that touching the screen does not select anything
[Magisk] JoshuaDoes:
I decided to scrap my preset keycodes entirely, v2.0.3 is now out. It instead requires you to calibrate your keys on startup for navigating the menu. In order, it will ask you to choose how to navigate down, navigate up, and how to select an item. It is recommended to respectively choose volume down, volume up, and then tap your screen. Controllers and remotes are also supported! This is required for certain devices like yours that do not have the same keycodes as my Pixel 6 Pro, I apologize for that.

Also, I would have gone with the power button, but when I used my text menu engine in a previous module from back on my Pixel 4a5G called "JD's Toolbox" for installing custom kernels and recoveries, I used the power button there and it became super annoying to deal with. Reasons being, pressing the power button can't be blocked by Magisk so the screen would turn off, and holding the power button would bring up the power menu which would overlay the screen and block potentially necessary visual output. I feel that tapping the touch screen is a much preferable method, but now you get to choose your method!
[Magisk] Fishawy:
Thanks for the quick fix. Confirming that touch screen works on v2.0.3, flashed successfully.
[Magisk] JoshuaDoes:
Tiny update that saves keycodes to a permanent location and allows recalibrating on module start!

Pixel Tensor Audio Decompressor v2.0.4
[Magisk] beeshyams:
Unfortunately for me on 6a,touching the screen works but doesn't let me choose any calibration value. Playing with volume buttons(post screen calibration) only shows the default value set by you and then says installation failed

Maybe I don't get it, but a suggestion-an app that is installed with the Magisk module that let's you change on the fly depending on what you are listening like the James DSP Manager does?
[Magisk] cemg92:
Wow, my man works fast!! Lol. Appreciate it. Pretty useful module, I can definitely hear improvements!

Pixel 7 user here. Can confirm that touching the screen doesn
[Magisk] beeshyams:
To clarify further, I simply can't choose any values after screen calibration
[Magisk] JoshuaDoes:
Would you mind sending a screen recording of your attempt to do the calibration process? It should look something like the one I attached below (edit: can't upload video attachments, use this link instead). As a side note, you CANNOT use any other Android functions while using the module's menu. The menu has no way of knowing if you are currently interacting with the Magisk terminal. Also, with the new v2.0.4 update, your calibration will be saved to `/data/local/tmp/menuKeycodes.json` and be available for use next time you use the menu. If your calibration process goes wrong, you can always close Magisk and start the menu again, then tap the screen or press one of the volume keys before the 5 second timer is up to start the recalibration process.

Also, while I'd love to have made an app for live testing different presets, I do not have the time nor the energy to make it myself, hence my inclusion of my text menu engine here. If someone is willing to make an open source app that utilizes the `phonedac.sh` script and `tinymix` binary I've included with the module, I'd be willing to consider integrating it with a future update.
[Magisk] zyhk:
Hifi maxmizer is for audiophile experts while Audio misc. settings is for casual audio lovers. The former replaces audio_policy_configuration.xml (deep_buffer is set 48kHz 32bits signed integer; not usual 32 bits float) and audio_platform_configuration.xml.

As you said so, I made a root script (needing magisk's global mount space option) to dynamically replace "mixer_paths.xml" on the fly with specified parameters (amp gain and digital volume).

To my ears, till 837/15 is OK, but 847/14 makes distortion.
[Magisk] beeshyams:
It looks from your video that you flashed twice.. Anyway this is the link for the video on flashing the second time

screen-20230730-155955.mp4 - Shared with pCloud

Store videos in pCloud. Share them with just the right people. Access them on any device. Create a free account now!

u.pcloud.link

I chose to change values and it says installation failed. The json file (probably from the first install says)

"/dev/input/event0": [

{

"keycode": 114,

"action": "nextItem",

"onRelease": true

},

{

"keycode": 115,

"action": "prevItem",

"onRelease": true

}

],

"/dev/input/event3": [

{

"keycode": 330,

"action": "selectItem",

"onRelease": true

}

]

}
[Magisk] beeshyams:
Thanks for your help

How does one flash this? Can't do with fox Manager or Magisk
[Magisk] JoshuaDoes:
I flashed twice to show what should happen the second time you use the module after calibration, it isn't supposed to force you to recalibrate anymore. Also, "installation failed" just shouldn't happen unless you accidentally tapped the screen before attempting to navigate down to one of the other two home menu choices. Now that you have a valid looking calibration file, can you try to just run the module normally now without touching anything at all?
[Magisk] JoshuaDoes:
Do you have the capacity to try helluvaOS in your free time? I worry that me being on P6P is leading to a difference here. But also, when I get the free time today I will try HiFi Maximizer and see if it does anything specifically different that I don't get when combo'd with helluvaOS + Audio misc. settings. Regardless, I'll also add 837/15 as a preset option to the menu in the next update.
[Magisk] gpvecchi:
Apply till next reboot gives an error...
[Magisk] krakout:
Just installed 2.05 over 1.2 (I think), manually as instructed. Stuck for several seconds at the attached screen, then the reboot prompt appeared, without other info (like "finished" or something). Safe to reboot?
[Magisk] JoshuaDoes:
It does so purposely, it's only a live test and the menu cannot determine if you are interacting with the Magisk terminal or some other part of Android. So it aborts on purpose to prevent accidental menu navigation while you go try the audio. After you confirm it's the volume you want, reinstall and choose "Confirm and install patch" instead.

It seems like a Magisk bug that pops up once in a while, I've ran into it myself. If you're ever stuck at that screen, just close Magisk and try again. It's failing to auto-scroll when this bug happens, and the menu works by writing a bunch of newlines to keep the auto-scroll momentum moving.
[Magisk] krakout:
Interesting. I haven't ever seen it but I'll take your word for it!

I tried again a bunch of times, always the same issue unfortunately. If I scroll down manually once the reboot message appears I see the script messages (but they have timed out). If I try to scroll manually before the reboot message appears, the Reboot prompt appears immediately and the script messages do not!
[Magisk] beeshyams:
Seems working but a very short test..
[Magisk] JoshuaDoes:
Are you using the latest official Magisk?

Also, I recorded a voiceover explaining exactly how to use the menu!

https://raw.githubusercontent.com/JoshuaDoes/pixel-tensor-audio-decompressor/dev/media/screen-20230730-191327.mp4