Latest Thread Images
Featured Sponsor Listings
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Sony Walkman custom firmware (non-Android)
- Thread starter MrWalkman
- Start date
unknown321123
100+ Head-Fier
From standard interface, actually when disabling the direct mode.
Yeap, latest stock firmware version (v3.02)
Thanks for checking on it!
Code:
05-26 01:22:32.429 248 248 I hagodaemon: [E| 282|b28ff460|ANLS|StreamMonitorThread.cc:55|pst::services::audioanalyzerservice::status_t pst::services::audioanalyzerservice::(anonymous namespace)::CheckPcmParam(const ipcmw::ipcsocket::PcmDataParam *)] invalid pcm codec type: 1
I am having a hard time reproducing the issue. According to logs, Walkman (not Wampy) is having issues with your files. By turning Direct Source off audio filters are enabled, but there is no data for them because... pcm codec type is wrong? Then AudioAnalyzer service responsible for spectrum analyzer crashes because there is no data from filters; Walkman service system notices dead service and reboots.
I replicated your actions as close as I could on Walkman One, but there was no crash.
Here is what we can do.
1. Try disabling Direct Source on completely different song (from other artist/album).
2. Disable EQ/Song just in case. Log doesn't show default EQ/Song settings (my bad), so I could not figure out if there was something unusual.
3. Disable visualizer in Wampy and restart the device.
4. Uninstall Wampy, set playback screen to Spectrum Analyzer and play that album we are having issues with (Άτοπος/Όπως πετάγονται οι γάτες απ'τους κάδους, θα βρεθούμε).
5. Send me a couple of tracks so I can try to reproduce it.
Last edited:
EQ/song was always disabledCode:05-26 01:22:32.429 248 248 I hagodaemon: [E| 282|b28ff460|ANLS|StreamMonitorThread.cc:55|pst::services::audioanalyzerservice::status_t pst::services::audioanalyzerservice::(anonymous namespace)::CheckPcmParam(const ipcmw::ipcsocket::PcmDataParam *)] invalid pcm codec type: 1
I am having a hard time reproducing the issue. According to logs, Walkman (not Wampy) is having issues with your files. By turning Direct Source off audio filters are enabled, but there is no data for them because... pcm codec type is wrong? Then AudioAnalyzer service responsible for spectrum analyzer crashes because there is no data from filters; Walkman service system notices dead service and reboots.
I replicated your actions as close as I could on Walkman One, but there was no crash.
Here is what we can do.
1. Try disabling Direct Source on completely different song (from other artist/album).
2. Disable EQ/Song just in case. Log doesn't show default EQ/Song settings (my bad), so I could not figure out if there was something unusual.
3. Disable visualizer in Wampy and restart the device.
4. Uninstall Wampy, set playback screen to Spectrum Analyzer and play that album we are having issues with (Άτοπος/Όπως πετάγονται οι γάτες απ'τους κάδους, θα βρεθούμε).
5. Send me a couple of tracks so I can try to reproduce it.
I tried multiple tracks from different artists and I am having mixed results, sometimes it crashes and sometimes not (in the same track). It even crashes right after a boot without me toggling to wampy. I really can’t provide valid steps to reproduce..
The only consistent pattern I noticed testing in the same track after a crash or restart without toggling wampy:
- If the current playback screen is “Standard” and you toggle Direct source to off, most of the times the track stops immediately and crashes.
- If the current playback screen is any of the rest (spectrum analyzer, analog level meter, digital peak meter) and you toggle direct off, there is no crash. At this point you can select “Standard” screen and toggle direct source and it won’t crash.
I also noticed that the tone control doesn’t affect the sound at all.
This is a newly acquired wm1a (purchased it recently from a headfier) which I had a few days before installing wampy so I can’t say if I experienced this kind of crashes before on this specific unit. Also, regarding tone control, I use it heavily in other nw devices so I am pretty sure, with wampy I couldn’t tell any difference when playing with it.
I will uninstall wampy and see if all modes work as expected.
Last week I installed another version (prior to the latest) on ZX300 (mrwalkman fw) and it worked flawlessly. I could try installing the latest on zx300 later in the day and play the same songs from the same SD card.
Last edited:
unknown321123
100+ Head-Fier
EQ/song was always disabled
I tried multiple tracks from different artists and I am having mixed results, sometimes it crashes and sometimes not (in the same track). It even crashes right after a boot without me toggling to wampy. I really can’t provide valid steps to reproduce..
The only consistent pattern I noticed testing in the same track after a crash or restart without toggling wampy:
- If the current playback screen is “Standard” and you toggle Direct source to off, most of the times the track stops immediately and crashes.
- If the current playback screen is any of the rest (spectrum analyzer, analog level meter, digital peak meter) and you toggle direct off, there is no crash. At this point you can select “Standard” screen and toggle direct source and it won’t crash.
I also noticed that the tone control doesn’t affect the sound at all.
This is a newly acquired wm1a (purchased it recently from a headfier) which I had a few days before installing wampy so I can’t say if I experienced this kind of crashes before on this specific unit. Also, regarding tone control, I use it heavily in other nw devices so I am pretty sure, with wampy I couldn’t tell any difference when playing with it.
I will uninstall wampy and see if all modes work as expected.
Last week I installed another version (prior to the latest) on ZX300 (mrwalkman fw) and it worked flawlessly. I could try installing the latest on zx300 later in the day and play the same songs from the same SD card.
v1.9.1.1 might fix the problem, please try it out
https://github.com/unknown321/wampy/releases
Same as before so I had to uninstall wampy and installed mrwalkman firmware (as I got it with the stock fw)
Thanks for looking on it, when I have more free time I will check if I can reproduce it on zx300 (hopefully not)
Report same issue like Kalex with WM1Z , 3.02 , wampy interface crash and rebootSame as before so I had to uninstall wampy and installed mrwalkman firmware (as I got it with the stock fw)
Thanks for looking on it, when I have more free time I will check if I can reproduce it on zx300 (hopefully not)
go back to 1.8.1 function in walkman One, Wampy crash ans auto switch back to walkman one mode, at leat it's work and sound good in Walkman One , hope you can verified 1.8.1 VS 1.9.1 for WM1Z
regards
unknown321123
100+ Head-Fier
Same as before so I had to uninstall wampy and installed mrwalkman firmware (as I got it with the stock fw)
Thanks for looking on it, when I have more free time I will check if I can reproduce it on zx300 (hopefully not)
This is a bug introduced by Wampy v1.9.0; reproducible by toggling on DSEE HX on any version of firmware.Report same issue like Kalex with WM1Z , 3.02 , wampy interface crash and reboot
go back to 1.8.1 function in walkman One, Wampy crash ans auto switch back to walkman one mode, at leat it's work and sound good in Walkman One , hope you can verified 1.8.1 VS 1.9.1 for WM1Z
regards
I'll post details later after I get a better grasp on what's going on; for now you can either disable DSEE HX or roll back to v1.8.x.
Oops! We ran into some problems.
Double posting replies goes against the posting guidelines. Please use the Edit feature to amend your previous post.
============================
The issue was introduced in v1.7.0, application was trying to configure filters and sometimes got invalid return codes because overridden methods returned nothing. With DSEE and spectrum analyzer on this situation produced a guaranteed crash; not anymore.
Fix - https://github.com/unknown321/wampy/commit/7dece0ea50edbd269b76d838e6f8910c6f9aea04
============================
Wampy v1.9.1.3
- fix crash on enabling DSEE
- run audio analyzer only when it's on screen
Last edited:
thanks
comfirmed working well , only thing i observed is battery drain extrem fast with wampy , anyone observed same thing or my device battery is problem
regards
comfirmed working well , only thing i observed is battery drain extrem fast with wampy , anyone observed same thing or my device battery is problem
regards
Oops! We ran into some problems.
Double posting replies goes against the posting guidelines. Please use the Edit feature to amend your previous post.
This is so annoying, I missed this last update because of this amazingly annoying "feature"...
The issue was introduced in v1.7.0, application was trying to configure filters and sometimes got invalid return codes because overridden methods returned nothing. With DSEE and spectrum analyzer on this situation produced a guaranteed crash; not anymore.
Fix - https://github.com/unknown321/wampy/commit/7dece0ea50edbd269b76d838e6f8910c6f9aea04
============================
Wampy v1.9.1.3
https://github.com/unknown321/wampy/releases
- fix crash on enabling DSEE
- run audio analyzer only when it's on screen
One thing I noticed on the previous version is:
I play music normally, with Walkman OS spectrum analyzer on - the "high" band is inactive for FLAC 16/44.1
I switch to Wampy with the Hold button
I get back to Walkman OS by switching the Hold button again - the "high" band is suddenly active
All this is happening while DSEE is off.
Is it some kind of bug, or where does the activity comes from? Is the "high" band maybe intentionally inactive by default when not playing Hi-Res audio, and somehow Wampy gets rid of the intentional behavior? (I have no idea, I'm just thinking)
I will check if this still happens with the last Wampy version.
Last edited:
unknown321123
100+ Head-Fier
Screen drains a lot of power. Wampy works along with standard application, so power consumption is increased while it's on the screen. You can try to limit the framerate, there is an option in Misc tab. Toggle it on and restart the device.battery drain extrem fast
I think double posting is locked behind either amount of likes or amount of posts made; I've seen double posting in other threads. Or could it be age since previous post?This is so annoying
the "high" band
Docs: Winamp mode changes bands from 50, 100, 160, 250, 500, 750, 1000, 2000, 4000, 8000, 16000, 28000to 1166, 2332, 3498, 4664, 5830, 6996, 8162, 9328, 10494, 11660, 12826, 13992 attempting to replicate Winamp's behaviour and filling last two bars with data.
You can disable winamp mode in settings or swipe standard interface to another screen and back, which will reset default band range.
Forgot to post link to dev notes, so here they are: https://github.com/unknown321/wampy/blob/master/MAKING_OF_VIS.md
Docs: Winamp mode changes bands from 50, 100, 160, 250, 500, 750, 1000, 2000, 4000, 8000, 16000, 28000to 1166, 2332, 3498, 4664, 5830, 6996, 8162, 9328, 10494, 11660, 12826, 13992 attempting to replicate Winamp's behaviour and filling last two bars with data.
You can disable winamp mode in settings or swipe standard interface to another screen and back, which will reset default band range.
Forgot to post link to dev notes, so here they are: https://github.com/unknown321/wampy/blob/master/MAKING_OF_VIS.md
Got it, makes sense now, thanks a lot!
bryaudioreviews
100+ Head-Fier
Hey, I notice you have both the ZX300 and WM1A m2.I like my ZX300, because the extra space on the bottom when turned sideways with wampy UI give me a palm rest where I can grip much better and doesn't obstruct the screen.
![]()
Do you mind comparing the zx300 MrWalkman modded with the WM1a m2 please? Im really looking to upgrade, however im unsure to go for a used WM1z or the wm1am2
unknown321123
100+ Head-Fier
Wampy v1.9.1.4
- fix crash on loading new reel which had only atlas files
https://github.com/unknown321/wampy/releases
Not a big deal, crashes occured only if you made a custom cassette reel skin which was not mentioned in config file; selecting that reel would produce a crash.
Also made a custom cassette skin - https://github.com/unknown321/tpp-wampy
- fix crash on loading new reel which had only atlas files
https://github.com/unknown321/wampy/releases
Not a big deal, crashes occured only if you made a custom cassette reel skin which was not mentioned in config file; selecting that reel would produce a crash.
Also made a custom cassette skin - https://github.com/unknown321/tpp-wampy

Hey, I notice you have both the ZX300 and WM1A m2.
Do you mind comparing the zx300 MrWalkman modded with the WM1a m2 please? Im really looking to upgrade, however im unsure to go for a used WM1z or the wm1am2
I'm not a fan of WM1AM2 due to three things
1/ it has a REALLY slow processor and it really shows when you need to scroll down or using a slightly modern app (comparing to other DAPs with a slightly newer processor say, SD650).
2/ the weird screen ring. it's really irritating if you use anything in dark mode and you can't unsee it.
3/ maybe it's just me, but the audio really gone stuttering if you enable high-res streaming option, so it's back to local files listening.
imo, if you really insist on using Android but with Sony sound signature, the ZX700 might be a more viable choice, otherwise for offline listening go for the WM1z?
When I go to the Wampy download page there are several files like (nw-a50.tar.gz, nw-a50.uninstaller.tar.gz) for different devices. What are these for?
Users who are viewing this thread
Total: 16 (members: 0, guests: 16)