DX340 iBasso developed Discret DAC, Easily replaceable batteries, Amp Modules! ***New firmware on 1st page. v1.04 local update. ***

[kaeswiss]

 

[Sonywalkmanuser]

Those that feel adventurous and are Rooted you can take care of the cnss_diag issue by editing a file: /data/vendor/wifi/cnss_diag.conf Download MiXplorer app and allow it Root access. find file and edit it and save and reboot. Change to below and changes remain after reboot and no more excessive CPU and logging/Storage IO:


LOG_PATH_FLAG = 0
MAX_LOG_FILE_SIZE = 1
MAX_ARCHIVES = 1
MAX_PKTLOG_ARCHIVES = 1
LOG_STORAGE_PATH =
AVAILABLE_MEMORY_THRESHOLD = 100
MAX_LOG_BUFFER = 2
MAX_PKTLOG_BUFFER = 10
HOST_LOG_FILE =
FIRMWARE_LOG_FILE =
ENABLE_FLUSH_LOG = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0
REAL_TIME_WRITE = 0

I looked at one of the log files and this appears to be verbose logging everything with wifi. So you have high CPU usage and tons writes to internal storage going on. Ibasso needs to address this in a FW update. I will try to automate the change to this file to make it easy for people. I am sure Stouthart will do this. Its a one time edit so makes no sense to put in module. There are other ways of getting this file to DAP without editing on DAP itself. For me it is easy to just edit on DAP. The log files are using 30MB of storage!!! That is a LOT of text as these are just text files. This only happens if you have wifi enabled so any streamers will have this issue. Now I will have to check out all top processes looking for stuff like this.

Here is a very, very small sample that is in the log files:
[INFO]:File Wrapped for 2 times
22:42:07.224337 [wifico][0x26496ddcc5][22:42:07.221043]wlan: [1009:WMA] wma_get_mcs_idx: 457: Rates from FW: raw_rate:4333 rate_flgs: 0xe8, nss: 1
22:42:07.226495 [wifico][0x26496dde4d][22:42:07.221063]wlan: [1009:WMA] wma_get_mcs_idx Matched rate in table: 4333 index: 9 mcs_rate_flag: 0xe8 nss 1 guard interval 1
22:42:07.226537 [wifico][0x26496de078][22:42:07.221092]wlan: [1009:HDD] wlan_hdd_get_sta_stats: 4803: snr: 52, rssi: -44
22:42:07.226564 [wifico][0x26496de37c][22:42:07.221132]wlan: [1009:HDD] wlan_hdd_get_sta_stats: 4873: [RSSI -44, RLMS 2, rssi high -55, rssi mid -65, rssi low -80]-[Rate info: TX: 4333, RX: 4333]-[Rate flags: TX: 0xe8, RX: 0xe8]-[MCS Index: TX: 9, RX: 9]-[NSS: TX: 1, RX: 1]-[dcm: TX: 0, RX: 0]-[guard interval: TX: 1, RX: 1
22:42:07.226587 [wifico][0x26496dee5a][22:42:07.221278]wlan: [1009:HDD] hdd_report_max_rate: 4603: RLMS 2, rate_flags 0xe8, max_rate 4333 mcs 9 nss 1
22:42:07.226608 [wifico][0x26496df053][22:42:07.221304]wlan: [1009:HDD] hdd_report_max_rate: 4603: RLMS 2, rate_flags 0xe8, max_rate 4333 mcs 9 nss 1
22:42:07.226630 [wifico][0x26496df1c2][22:42:07.221323]wlan: [1009:HDD] hdd_fill_fcs_and_mpdu_count: 4689: RX mpdu count 0 fcs_err_count 0
22:42:10.248056 [wifico][0x26496dff73][22:42:07.221505]wlan: [1009:HDD] wlan_hdd_get_sta_stats: 4955: [TX: Reporting MCS rate 9, flags 0x6 pkt cnt 445, nss 1, bw 4]-[RX: Reporting MCS rate 9, flags 0x6 pkt cnt 576, nss 1, bw 4]
22:42:10.248147 [wifico][0x26496e02cc][22:42:07.221550]wlan: [1009:HDD] hdd_wlan_fill_per_chain_rssi_stats: 4660: RSSI for chain 0, vdev_id 0 is -45
22:42:10.248176 [wifico][0x26496e042e][22:42:07.221568]wlan: [1009:HDD] hdd_wlan_fill_per_chain_rssi_stats: 4660: RSSI for chain 1, vdev_id 0 is -96
22:42:10.248199 [wifico][0x26496e055c][22:42:07.221584]wlan: [1009:HDD] wlan_hdd_get_sta_stats: 4960: exit
22:42:10.248220 [kworke][0x2649dd54af][22:42:07.601523]wlan: [4197:IPA] ipa_is_fw_wdi_activated: 574: ipa is disabled
22:42:10.248241 [kworke][0x264a761239][22:42:08.122877]wlan: [4154:IPA] ipa_is_fw_wdi_activated: 574: ipa is disabled
22:42:10.248262 [kworke][0x264b0b4c69][22:42:08.632240]wlan: [4161:IPA] ipa_is_fw_wdi_activated: 574: ipa is disabled
22:42:10.248283 [kworke][0x264ba38c5d][22:42:09.151919]wlan: [4154:IPA] ipa_is_fw_wdi_activated: 574: ipa is disabled
22:42:10.248305 [kworke][0x264c3b3ace][22:42:09.669658]wlan: [4197:IPA] ipa_is_fw_wdi_activated: 574: ipa is disabled
22:42:10.248325 [kworke][0x264cd18052][22:42:10.182585]wlan: [4154:IPA] ipa_is_fw_wdi_activated: 574: ipa is disabled
22:42:10.248347 [wifi@1][0x264ce1b53b][22:42:10.237904]wlan: [727:HDD] wlan_hdd_send_ll_stats_req: 1570: enter
22:42:10.248367 [schedu][0x264ce1e18c][22:42:10.238494]wlan: [1455:WMA] msg->type = 10f1 WMA_LINK_LAYER_STATS_GET_REQ
22:42:10.248389 [schedu][0x264ce1e533][22:42:10.238542]wlan: [1455:WMI] LINK_LAYER_STATS - Get Request Params Request ID: 0 Stats Type: 7 Vdev ID: 0 Peer MAC Addr: 7e:1e:603b:69
22:42:10.248412 [schedu][0x264ce1e8ac][22:42:10.238588]wlan: [1455:WMI] Send WMI command:WMI_REQUEST_LINK_STATS_CMDID command_id:90116 htc_tag:0
22:42:10.248433 [schedu][0x264ce4415b][22:42:10.246598]wlan: [1455:WMA] Radio stats Fixed Param: req_id: 0 num_radio: 1 more_radio_events: 1
22:42:10.248454 [schedu][0x264ce443d2][22:42:10.246630]wlan: [1455:WMA] Channel Stats Info
22:42:10.248597 [schedu][0x264ce4459a][22:42:10.246654]wlan: [1455:WMA] freq 2412 width 0 freq0 2412 freq1 0 awake time 80 cca busy time 36
22:42:10.248624 [schedu][0x264ce44d61][22:42:10.246758]wlan: [1455:WMA] freq 2417 width 0 freq0 2417 freq1 0 awake time 81 cca busy time 36
22:42:10.248647 [schedu][0x264ce44eda][22:42:10.246777]wlan: [1455:WMA] freq 2422 width 0 freq0 2422 freq1 0 awake time 80 cca busy time 6
22:42:10.248669 [schedu][0x264ce4502e][22:42:10.246795]wlan: [1455:WMA] freq 2427 width 0 freq0 2427 freq1 0 awake time 80 cca busy time 3
22:42:10.248692 [schedu][0x264ce45175][22:42:10.246812]wlan: [1455:WMA] freq 2432 width 0 freq0 2432 freq1 0 awake time 80 cca busy time 3
22:42:10.248713 [schedu][0x264ce452be][22:42:10.246829]wlan: [1455:WMA] freq 2437 width 0 freq0 2437 freq1 0 awake time 80 cca busy time 25
22:42:10.248735 [schedu][0x264ce45404][22:42:10.246846]wlan: [1455:WMA] freq 2442 width 0 freq0 2442 freq1 0 awake time 80 cca busy time 13
22:42:10.248757 [schedu][0x264ce45539][22:42:10.246862]wlan: [1455:WMA] freq 2447 width 0 freq0 2447 freq1 0 awake time 80 cca busy time 51
22:42:10.248778 [schedu][0x264ce45672][22:42:10.246879]wlan: [1455:WMA] freq 2452 width 0 freq0 2452 freq1 0 awake time 80 cca busy time 23
22:42:10.248799 [schedu][0x264ce457a5][22:42:10.246895]wlan: [1455:WMA] freq 2457 width 0 freq0 2457 freq1 0 awake time 80 cca busy time 38
22:42:10.248821 [schedu][0x264ce458d8][22:42:10.246911]wlan: [1455:WMA] freq 2462 width 0 freq0 2462 freq1 0 awake time 80 cca busy time 35
22:42:10.248842 [schedu][0x264ce45a1b][22:42:10.246927]wlan: [1455:WMA] freq 5180 width 0 freq0 5180 freq1 0 awake time 42 cca busy time 4
22:42:10.248864 [schedu][0x264ce45b4e][22:42:10.246943]wlan: [1455:WMA] freq 5200 width 0 freq0 5200 freq1 0 awake time 41 cca busy time 4
22:42:10.248885 [schedu][0x264ce45c83][22:42:10.246959]wlan: [1455:WMA] freq 5220 width 0 freq0 5220 freq1 0 awake time 41 cca busy time 9
22:42:10.248907 [schedu][0x264ce45db5][22:42:10.246975]wlan: [1455:WMA] freq 5240 width 0 freq0 5240 freq1 0 awake time 41 cca busy time 6
22:42:10.248929 [schedu][0x264ce45ef0][22:42:10.246992]wlan: [1455:WMA] freq 5765 width 0 freq0 5765 freq1 0 awake time 41 cca busy time 1
22:42:10.249051 [schedu][0x264ce46022][22:42:10.247008]wlan: [1455:WMA] freq 5785 width 0 freq0 5785 freq1 0 awake time 41 cca busy time 10
22:42:10.249076 [schedu][0x264ce46189][22:42:10.247026]wlan: [1455:WMA] freq 5805 width 0 freq0 5805 freq1 0 awake time 41 cca busy time 9
22:42:10.249105 [schedu][0x264ce462cc][22:42:10.247043]wlan: [1455:WMA] freq 5825 width 0 freq0 5825 freq1 0 awake time 41 cca busy time 5
22:42:10.249128 [schedu][0x264ce46414][22:42:10.247060]wlan: [1455:WMA] freq 5260 width 0 freq0 5260 freq1 0 awake time 109 cca busy time 6
22:42:10.249149 [schedu][0x264ce46553][22:42:10.247077]wlan: [1455:WMA] freq 5280 width 0 freq0 5280 freq1 0 awake time 109 cca busy time 1
22:42:10.249169 [schedu][0x264ce4668d][22:42:10.247093]wlan: [1455:WMA] freq 5300 width 0 freq0 5300 freq1 0 awake time 109 cca busy time 4
22:42:10.249190 [schedu][0x264ce467c5][22:42:10.247110]wlan: [1455:WMA] freq 5320 width 0 freq0 5320 freq1 0 awake time 109 cca busy time 1
22:42:10.249211 [schedu][0x264ce46909][22:42:10.247126]wlan: [1455:WMA] freq 5500 width 0 freq0 5500 freq1 0 awake time 109 cca busy time 1
22:42:10.249232 [schedu][0x264ce46a44][22:42:10.247143]wlan: [1455:WMA] freq 5520 width 0 freq0 5520 freq1 0 awake time 109 cca busy time 3
22:42:10.249253 [schedu][0x264ce46b7c][22:42:10.247159]wlan: [1455:WMA] freq 5540 width 0 freq0 5540 freq1 0 awake time 109 cca busy time 1
22:42:10.249274 [schedu][0x264ce46cb7][22:42:10.247175]wlan: [1455:WMA] freq 5560 width 0 freq0 5560 freq1 0 awake time 109 cca busy time 7
22:42:10.249295 [schedu][0x264ce46dee][22:42:10.247192]wlan: [1455:WMA] freq 5580 width 0 freq0 5580 freq1 0 awake time 109 cca busy time 1
22:42:10.249316 [schedu][0x264ce46f2a][22:42:10.247208]wlan: [1455:WMA] freq 5600 width 0 freq0 5600 freq1 0 awake time 109 cca busy time 13
22:42:10.249337 [schedu][0x264ce4705d][22:42:10.247224]wlan: [1455:WMA] freq 5620 width 0 freq0 5620 freq1 0 awake time 109 cca busy time 1
22:42:10.249357 [schedu][0x264ce4718e][22:42:10.247240]wlan: [1455:WMA] freq 5640 width 0 freq0 5640 freq1 0 awake time 109 cca busy time 8
22:42:10.249377 [schedu][0x264ce472bf][22:42:10.247256]wlan: [1455:WMA] freq 5660 width 0 freq0 5660 freq1 0 awake time 109 cca busy time 2
22:42:10.249496 [schedu][0x264ce473f0][22:42:10.247272]wlan: [1455:WMA] freq 5680 width 0 freq0 5680 freq1 0 awake time 109 cca busy time 1
22:42:10.249521 [schedu][0x264ce47543][22:42:10.247289]wlan: [1455:WMA] freq 5700 width 0 freq0 5700 freq1 0 awake time 109 cca busy time 27
22:42:10.249543 [schedu][0x264ce4767b][22:42:10.247306]wlan: [1455:WMA] freq 5720 width 0 freq0 5720 freq1 0 awake time 111 cca busy time 1
22:42:10.249564 [schedu][0x264ce477cd][22:42:10.247323]wlan: [1455:WMA] freq 5745 width 2 freq0 5775 freq1 0 awake time 45541 cca busy time 3922
22:42:10.249585 [schedu][0x264ce47d96][22:42:10.247401]wlan: [1455:WMA] db2dbm: 0, rssi_mgmt: -48, rssi_data: -54, rssi_ack: -48
22:42:10.249607 [schedu][0x264ce480dd][22:42:10.247444]wlan: [1455:HDD] LL_STATS RESP paramID = 0x2, ifaceId = 0,

After file edit:

Are you sure about not licensing your findings/guide? Maybe it might get “stolen” by others and copyrighted as their work.

 

[jamato8]

Using the Focal Utopia with the 340 and the AMP16 and 12 volt in. Wow, so much fun. First real serious listening with the Utopia and the AMP16 that has around 170 hours on it, or there about, and this drives them with wonderful ease, naturalness, dynamics with aplomb. Listening to Jackie Leven "Night Lilies".

Solid bass that sounds like real bass with excellent control and depth. Voice is magnificent and such imaging with depth and placement. Damn.

 

[mattclarke18]

Are you sure about not licensing your findings/guide? Maybe it might get “stolen” by others and copyrighted as their work.

I am doing this for the community as a whole to make the DX340/iBasso's the best it/they can possibly be. There are lots of smart people here. If someone can take something I have done and make it even better its actually the biggest compliment someone can give me. I do not profit from any of this nor wish to. This has become the hobby for me and enjoy the challenge. Done buying IEMs and DAPs. I would be happy to take a WMA2 and see what I could do with it. I sold mine months ago. I am FOR community driven innovation and that works best when several people pool resources and work towards a common goal. Stouthart, for example, is very smart and has his own version of tweaking and very happy to have him in the community. I do not see him as my competition but someone who has the same goal as me. I am trying to provide a root solution while his does not require root. That gives people CHOICE and that is a great thing. He noticed the resource usage. I did not because I never ran "top" with wifi enabled as I local play only. I only test my tweaks with streaming before publishing them to make sure it works etc. For me alone WIFI is just a waste of resources. He is the person that caught this issue so he deserves the credit here. My posted solution is more for an advanced user. His will be for anyone. Bottom line is iBasso can fix this issue with a FW update and probably not even aware of it. Now I wonder what else is logging in verbose mode wasting resources. Next task.

 

[Sonywalkmanuser]

I am doing this for the community as a whole to make the DX340/iBasso's the best it/they can possibly be. There are lots of smart people here. If someone can take something I have done and make it even better its actually the biggest compliment someone can give me. I do not profit from any of this nor wish to. This has become the hobby for me and enjoy the challenge. Done buying IEMs and DAPs. I would be happy to take a WMA2 and see what I could do with it. I sold mine months ago. I am FOR community driven innovation and that works best when several people pool resources and work towards a common goal. Stouthart, for example, is very smart and has his own version of tweaking and very happy to have him in the community. I do not see him as my competition but someone who has the same goal as me. I am trying to provide a root solution while his does not require root. That gives people CHOICE and that is a great thing. He noticed the resource usage. I did not because I never ran "top" with wifi enabled as I local play only. I only test my tweaks with streaming before publishing them to make sure it works etc. For me alone WIFI is just a waste of resources. He is the person that caught this issue so he deserves the credit here. My posted solution is more for an advanced user. His will be for anyone. Bottom line is iBasso can fix this issue with a FW update and probably not even aware of it. Now I wonder what else is logging in verbose mode wasting resources. Next task.

I don’t think it’s possible to do anything much for Sony without root and without the .img files.

Also it’s not just community. It’s also about the various “open” AI taking your work and using them to generate profits.

 

[mattclarke18]

I don’t think it’s possible to do anything much for Sony without root and without the .img files.

Also it’s not just community. It’s also about the various “open” AI taking your work and using them to generate profits.

My guides are now all on Google Drive and not published like I was doing before. Got to be a pain when I made a change to edit a post and remove and upload a new one. I guess if AI can download and read my guides so be it. They are free to all here without any copyrights. If someone/AI charges for them they are not very smart as Google search will lead them right to this site.

I do think I could do some things with the Sony. I would not say no to the challenge even though the DX340 is my End-Game. Root will allow you to adjust kernel stuff which will help of course. Sony has a low powered SOC with way too much bloat for it to deal with just to get the Google certification. Many of the tweaks I have done with Ibasso do not require root. You just don't have the safety net of being able to flash if things go really bad. I have been able to get into Recovery Mode and do a wipe 99% of the time on iBasso when I have gone too far.

 

[Sonywalkmanuser]

My guides are now all on Google Drive and not published like I was doing before. Got to be a pain when I made a change to edit a post and remove and upload a new one. I guess if AI can download and read my guides so be it. They are free to all here without any copyrights. If someone/AI charges for them they are not very smart as Google search will lead them right to this site.

I do think I could do some things with the Sony. I would not say no to the challenge even though the DX340 is my End-Game. Root will allow you to adjust kernel stuff which will help of course. Sony has a low powered SOC with way too much bloat for it to deal with just to get the Google certification. Many of the tweaks I have done with Ibasso do not require root. You just don't have the safety net of being able to flash if things go really bad. I have been able to get into Recovery Mode and do a wipe 99% of the time on iBasso when I have gone too far.

It’s just disappointing that other than just Google doing background data collection*, these hardware companies are also involved in so much wasteful background processing activity as revealed by you. This goes to show that highest precision audio playback on android platform needs a lot of deeper debloating to get the device to become dedicated to only audio processing functions without any hidden background activity.

* https://firebase.google.com/

 

[Stouthart]

It’s just disappointing that other than just Google doing background data collection*, these hardware companies are also involved in so much wasteful background processing activity as revealed by you. This goes to show that highest precision audio playback on android platform needs a lot of deeper debloating to get the device to become dedicated to only audio processing functions without any hidden background activity.

* https://firebase.google.com/

There is actually not that much logging going on in the background (has nothing to do with debloating). Kernel ring buffer (dmesg) is always enabled, as is the logging daemon (logd/logcat) for system messages (similar to journalctl on Linux). Both run in the background and only write to non-persistent storage (memory). Then there is the trace daemon (traced), which is used for scheduler debugging. This service is not required on a production device and can/should be disabled (already done via Advanced Tweaking).

And finally, cnss_diag: this diagnostic tool is known to drain the battery of many Android phones (especially Xiaomi). Not only does it consume a lot of CPU time, but it also writes to persistent log files on disk. I have disabled this service myself for a week now, without any issues. By the way, this service does not come from iBasso; it is part of the Qualcomm Wi-Fi drivers.

The challenge for me was not so much to figure out how to stop cnss_diag, but to provide a fix via Advanced Tweaking that is reversible and doesn't require permanent changes to config and/or vendor init files. Also, debugging the Android boot/init process isn't easy. And - unlike many other services - cnss_diag doesn't provide a setting/property to disable it. But I just found a safe solution, which stops cnss_diag immediately after it starts. The log files are still created, but they stay 0 bytes in size. This (test) version has already been published on GitHub (v5.5b). As a positive side effect: there seems to be less Wi-Fi related noise now when using the AMP14 card

For those willing to re-run the Advanced Tweaking script, please let me know if you experience any issues. Thanks!

 

[mattclarke18]

Another way to look at it is to write a script which I can do just to remove the existing conf file and create a new one with the new values I found to stop the writes to log/cpu use etc. This would need to be run 1 time. Service can stay running so less risk of anything not working. Once the file has been modified/re-created it does not change on reboot. Flash would change it back to whatever is in FW. I can create this script if anyone wishes and it would work on the non-root only devices. I have reported this to Paul. To reverse the change another script can be created to make a new conf file with "old" values.

 

[VishnuKare]

The ddHifi stand with this DAP is fully functional and looks good as well.

 

[mattclarke18]

Very nice! Now all you need to do is polish that SS so it shines

 

[jamato8]

The ddHifi stand with this DAP is fully functional and looks good as well.

Does anything hold the dap in place?

 

[frudogg]

Need help with EQ in Mango.
I have a DX 340 I am enjoying with a few different headphones and IEMs. I am having difficulty using EQ with Mango. I generally find EQ files here: https://github.com/jaakkopasanen/AutoEq/tree/master/results
In UAPP I use parametric EQ (10 band) and entire the data manually and store it as a preset for each headphone which appears to work fine.
In Mango the parametric EQ is limited to 6 bands and if I enter manually and use EQ it sounds terrible and I don't see a way to store a preset for each headphone.
Can anyone give me some help?
Thanks

 

[mattclarke18]

Need help with EQ in Mango.
I have a DX 340 I am enjoying with a few different headphones and IEMs. I am having difficulty using EQ with Mango. I generally find EQ files here: https://github.com/jaakkopasanen/AutoEq/tree/master/results
In UAPP I use parametric EQ (10 band) and entire the data manually and store it as a preset for each headphone which appears to work fine.
In Mango the parametric EQ is limited to 6 bands and if I enter manually and use EQ it sounds terrible and I don't see a way to store a preset for each headphone.
Can anyone give me some help?
Thanks

Use Neutron which you can set how many bands you want to use up to 60 I believe for PEQ.

 

[VishnuKare]

Does anything hold the dap in place?

Yes, the 2 bottom feet. These are adjustable in position and needs to be positioned correctly to fit the headphone jack and 12v dc plug.