|
Post by whitigir on Feb 19, 2022 9:27:25 GMT
So playing around some more, and I realized that in order to play offscreen and DSD256 with OS 8X. You donât need to tweak minimal CPU cores, just simply give it the performance setting by cpu governor
|
|
|
Post by NPAudio on Feb 19, 2022 9:43:16 GMT
The Hiby daps are set as performance governer as default. Meaning it just stays at max frequency all the time. Only they had CPUSets for Music apps set to only 2 cores and foreground apps all 8 so when you were upsampling or dsd converting in neutron and then switched to say web browser the sound would stutter, crazy!
Have you tried on demand governor with it.
|
|
|
Post by whitigir on Feb 19, 2022 15:04:56 GMT
After spending time with our lovely Dx300. I can safely say that if it isnât the Dx300 then there is nothing else out there that can do this very special and specific feature
Neutron Player with Oversampling into 8X or 384Khz and then into DSD256 on the fly
How so ?
1/ battery life !! The digital battery life is greatly effected. It goes down from 16 hours for FLAC and into 6-8 hours depending on the original files whether it was DSD64 or FLAC 16/44.1 format
Assuming it cutting the battery life in 1/2. Then taking DX300Max for example. You can easily be cutting back down from 10 hours into 4-5 hours easily
2/ Heat dissipations !! While the Amp sections doesnât heat up as much, the Quad DAC sections donât even heat up as much with Dx300 and it Cirrus chips!! This is very different for other chips like ESS or AKM. Every devices j have came through that have these chip sets, are a heat generator !!! Except the Dx300 of course
Even so, the Dx300 can easily be heating up into 45-50 Celsius !!! Which is pretty warm!!
3/ There are Steel Plate that is on the back of the battery and separating the CPU away from the Battery itself. This acts as a physical barrier to reduce EMI and shielding, together with the heat being generated by the CPU underneath
If you are enjoying this very specific features ! Or should I say that , to be enjoying the best of Neutron and what it can offer !!! Nothing is better than DX300
And not to hype anything up, but if you have Amp12EX also, that is another winner !! And amazing combinations !!
I donât know about MQA and such, but I love seeing this Blue LED indicator of DSD256 !!!
But this feature is the real deal !!
|
|
|
Post by whitigir on Feb 19, 2022 15:09:21 GMT
I love this Neutron to DSD256 Feature !
The benefits are huge, including
Sharper and more vivid Textures!! Better dynamic and controls !! Less distortions !! Less noises !! Clarity vastly improved
Soundstage is wider and deeper with more layering!!
Better cues of imagines !!!
Decays are also more defined
Tonal body also has improved in inner density, dynamic, and pitches.
Suddenly when comparing between one specific Redbook FLAC 16/44.1 Vs Mango OS playing back, the differences are huge !!
|
|
|
Post by whitigir on Feb 19, 2022 15:12:54 GMT
The Hiby daps are set as performance governer as default. Meaning it just stays at max frequency all the time. Only they had CPUSets for Music apps set to only 2 cores and foreground apps all 8 so when you were upsampling or dsd converting in neutron and then switched to say web browser the sound would stutter, crazy! Have you tried on demand governor with it. I am trying out On demand now and scaling back on Minimum CPU frequencies. It does Off screen DSD256 just fine. Less heat generated, but battery consumption is about similar still. The temperature goes down from 47 Celsius into 43 Celsius after 30 minutes of playing. . Still going into 50Celsius after 1 hour though âŚ..Still trying to tweak around more for a better optimized setting. But I am amazed at a player that can do this on the fly and still last for more than 6 hours Now*** is there a way to increase the battery capacity on the digital side !!! Lol!!! Even if it involves in modifying the back plate !! I am thinking that we can mill out a customized Metal Plate that can screw on into the chassis socket ? ButâŚ.it is sitting flushed to the chassis though, raising it would be a biatch
|
|
|
Post by whitigir on Feb 19, 2022 19:55:46 GMT
On demand didnât work too well, unless I maximize out the frequencies of the cores. I am back at performances setting. It doesnât allow for parameter changing like on demand do (which I have no clues yet). But with performances setting, I can scale back in frequencies for all cores and still doing a wonderful job
|
|
|
Post by samandhi on Feb 20, 2022 23:34:45 GMT
I love this Neutron to DSD256 Feature ! The benefits are huge, including Sharper and more vivid Textures!! Better dynamic and controls !! Less distortions !! Less noises !! Clarity vastly improved Soundstage is wider and deeper with more layering!! Better cues of imagines !!! Decays are also more defined Tonal body also has improved in inner density, dynamic, and pitches. Suddenly when comparing between one specific Redbook FLAC 16/44.1 Vs Mango OS playing back, the differences are huge !! Don't forget dither with sound shaping. It should alleviate any outstanding quantization errors.
|
|
|
Post by gentzen01 on Feb 22, 2022 17:29:25 GMT
Thanks for a comprehensive and well-written guide! While everything else is quite clear, I'm guessing the boot img files you created are specific to that firmware and won't work with DX300Max. To root DX300, did you extract the original boot img file(s) from the firmware (e.g., using something like TWRP), patched them (e.g., via Magisk) and flashed them (e.g.,with Fastboot Commands)? Or a different method? I'd be quite interested to know how to do this on my DX300Max. Not sure I'll go ahead with the PCM-->DSD256 setting on Neutron (too much heat dissipation might compromise the device long term), but I sure do want the option to be there (plus any other tweaks that may come handy)
|
|
|
Post by whitigir on Feb 22, 2022 18:43:44 GMT
Thanks for a comprehensive and well-written guide! While everything else is quite clear, I'm guessing the boot img files you created are specific to that firmware and won't work with DX300Max. To root DX300, did you extract the original boot img file(s) from the firmware (e.g., using something like TWRP), patched them (e.g., via Magisk) and flashed them (e.g.,with Fastboot Commands)? Or a different method? I'd be quite interested to know how to do this on my DX300Max. Not sure I'll go ahead with the PCM-->DSD256 setting on Neutron (too much heat dissipation might compromise the device long term), but I sure do want the option to be there (plus any other tweaks that may come handy) Yes, just as Steve stated on the very first post , patched the boot partitions on the player by magisk and then flashing back on an unlocked boot loader dx300 I donât think the Dx300Max can stand the heat generated by the PCM-DSD256. However, rooting it to make it more battery efficient will be an excellent idea
|
|
|
Post by gentzen01 on Feb 23, 2022 12:51:09 GMT
Thanks for a comprehensive and well-written guide! While everything else is quite clear, I'm guessing the boot img files you created are specific to that firmware and won't work with DX300Max. To root DX300, did you extract the original boot img file(s) from the firmware (e.g., using something like TWRP), patched them (e.g., via Magisk) and flashed them (e.g.,with Fastboot Commands)? Or a different method? I'd be quite interested to know how to do this on my DX300Max. Not sure I'll go ahead with the PCM-->DSD256 setting on Neutron (too much heat dissipation might compromise the device long term), but I sure do want the option to be there (plus any other tweaks that may come handy) Yes, just as Steve stated on the very first post , patched the boot partitions on the player by magisk and then flashing back on an unlocked boot loader dx300 I donât think the Dx300Max can stand the heat generated by the PCM-DSD256. However, rooting it to make it more battery efficient will be an excellent idea Thanks for getting back to me. Appreciate the help.
Did you change anything in the boot partition img files you got from the firmware? Or flashed them back, to root, exactly as they were? Regarding the DX300Max, what makes you think so? If the SoC is what's doing all the work (rather than the AKM chips), then on Neutron there should, in principle, be no difference between the DX300 and the 3Max in terms of overheating (i.e. the greater efficiency of the Cirrus chips should not be a factor). It would then come down to the heat conducting and heat disspation properties of the DAPs. 3Max Ti has more real estate to disperse heat before dissipation (and a dedicated heat dissipation outlet on the other side from where buttons are), plus titanium has relatively low thermal conductivity similar to SS (unless I'm wrong here). Would that not make the risk from overheating no higher than on the regular DX300? I noticed you mentioned min-max frequencies for the cores. How many cores (at the minimum) do you need to stop PCM-->DSD256 stuttering/clipping with screen off? Can it be done effectively with less than 8 (to minimize heat generation), e.g., with 4 or 6?
|
|
|
Post by whitigir on Feb 23, 2022 16:45:52 GMT
The DX300 Max and 300, neither one has a proper cooling mechanism. However, the Cirrus chips are running much cooler than the AK4499EQ on Native DSD256 as an interface. Sharing the boards, the 3Max will heat up much more than then 300. You can try and put 3Max in performances mode and see.
It has 4 lower cores and 4 upper cores. You can play around and see which one works out the best for you. It does take up a lot of processing power though.
|
|
|
Post by NPAudio on Feb 23, 2022 17:11:26 GMT
Yes, just as Steve stated on the very first post , patched the boot partitions on the player by magisk and then flashing back on an unlocked boot loader dx300 I donât think the Dx300Max can stand the heat generated by the PCM-DSD256. However, rooting it to make it more battery efficient will be an excellent idea Thanks for getting back to me. Appreciate the help.
Did you change anything in the boot partition img files you got from the firmware? Or flashed them back, to root, exactly as they were? Regarding the DX300Max, what makes you think so? If the SoC is what's doing all the work (rather than the AKM chips), then on Neutron there should, in principle, be no difference between the DX300 and the 3Max in terms of overheating (i.e. the greater efficiency of the Cirrus chips should not be a factor). It would then come down to the heat conducting and heat disspation properties of the DAPs. 3Max Ti has more real estate to disperse heat before dissipation (and a dedicated heat dissipation outlet on the other side from where buttons are), plus titanium has relatively low thermal conductivity similar to SS (unless I'm wrong here). Would that not make the risk from overheating no higher than on the regular DX300? I noticed you mentioned min-max frequencies for the cores. How many cores (at the minimum) do you need to stop PCM-->DSD256 stuttering/clipping with screen off? Can it be done effectively with less than 8 (to minimize heat generation), e.g., with 4 or 6? The stock kernel parameters on the 3MAX cripple the 660s performance to keep the temperature down. The current 3MAX hardware mod i'm doing will also receive much better graphite cooling film. 30 times more heat conductive than the stock silcone. Probably more so as that stock silicone sheet does not stick to the side of the chassis well at all. Infact the couple i've seen only had contact at the part they stuck the serial number sticker on it. The rest was flopped over đ A vented stainless steel back may cone to a future one but it's out of budget for this one.
|
|
|
Post by whitigir on Feb 24, 2022 19:31:41 GMT
Thanks for getting back to me. Appreciate the help.
Did you change anything in the boot partition img files you got from the firmware? Or flashed them back, to root, exactly as they were? Regarding the DX300Max, what makes you think so? If the SoC is what's doing all the work (rather than the AKM chips), then on Neutron there should, in principle, be no difference between the DX300 and the 3Max in terms of overheating (i.e. the greater efficiency of the Cirrus chips should not be a factor). It would then come down to the heat conducting and heat disspation properties of the DAPs. 3Max Ti has more real estate to disperse heat before dissipation (and a dedicated heat dissipation outlet on the other side from where buttons are), plus titanium has relatively low thermal conductivity similar to SS (unless I'm wrong here). Would that not make the risk from overheating no higher than on the regular DX300? I noticed you mentioned min-max frequencies for the cores. How many cores (at the minimum) do you need to stop PCM-->DSD256 stuttering/clipping with screen off? Can it be done effectively with less than 8 (to minimize heat generation), e.g., with 4 or 6? The stock kernel parameters on the 3MAX cripple the 660s performance to keep the temperature down. The current 3MAX hardware mod i'm doing will also receive much better graphite cooling film. 30 times more heat conductive than the stock silcone. Probably more so as that stock silicone sheet does not stick to the side of the chassis well at all. Infact the couple i've seen only had contact at the part they stuck the serial number sticker on it. The rest was flopped over đ A vented stainless steel back may cone to a future one but it's out of budget for this one. Yes, pretty much agreed, but when you really think about it, SS and a little frame isnt going to do much good anyways lol !! However, better dissipations will allow better clocking !!
|
|
|
Post by gentzen01 on Mar 9, 2022 15:44:25 GMT
Steve, was intending to be using TWRP Recovery to extract .img from DX300 Max firmware to patch up with Magisk and root. However, to my great disappointment I can't find the TWRP binary for the DX300 Max specifically (there probably isn't one).
I'm not experienced in Android and haven't used QFIL before. Could you kindly explain what the .elf file you provide above is for? Is it the emmc Firehose Programmer file to use with QFIL (with the DAP in EDL mode) to copy boot (and recovery) img from the Qualcomm firmware? In other words, is it the same .elf file across all these Qualcomm devices? Also, how many boot.img files does DX300 Max partition have (Whitigir said 2 for DX300 reg)? And, once I've patched the boot image file(s) with Magisk, can an ADB command pull them to the PC for fastboot-flashing them onto the DX300 Max? Or do I have to do it manually looking for files in the internal storage of the DAP? All responsibility is mine for attempting it Thanks George
|
|
|
Post by whitigir on Mar 10, 2022 7:27:08 GMT
TWRP isnât compiled for the specific DX300/Max yet!
The file provided by Steve is a firehose file that you gotta use with QFIL and from there you can extract your own Boot IMG then using magisk on your device to patch it. There will be 2 to extract (I would think, either way, you will see it in the list) and patch
If you have used TWRP before, then QFIL isnât hard to figure out. It just takes some times. I never used either one and still pulled mine.
|
|