-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
need to re-compile for atmosphere 0.19 #6
Comments
On Atmosphere 0.18.1 with the last version of BootSoundNX this bug was NOT present. I know there's an old issue for it but it wasn't occuring on 0.18.1. |
I created a Pull Request (PR #8) that SHOULD fix this... Hopefully it will be merged and will fix it for you all. :) |
Well unfortunately that's not a fix, it's simply delaying the boot sound to the extent that it's not really a boot sound anymore which is why the old PR was never merged. |
Well, if that's the case, then I'll delete my PR. However, I would like it to be known that I setup that code as an attempt to fix the issue for users of older HOS versions. In the end, good to know. I was wondering why that PR was removed. |
I have the issue on Atmosphere 0.19.5 and firmware 12.1.0 |
Which issue, to be specific?
If it's the delayed boot sound, I have removed the delay code on my repo. If you want, go to my fork and try out releases v1.2.0 (updating it to the latest version) and 1.2.5 (my attempt to fix the delayed boot sound). Let me know if either of those fix your issues. Kudos, |
As I originally stated in this issue, longer bootsounds now have a pause in the playback in your 1.2.0 version. This was not an issue with the original BootSoundNX on atmosphere 0.18.1 therefore it appears that something has changed since then in either atmosphere or newer firmware versions to cause this problem. Delaying the bootsound as in your 1.2.5 version works as a workaround but as mentioned it's so late that it's barely a bootsound anymore. |
Also @TheModdersDen since there may be some misunderstanding here, to be clear the bug is a pause is IN THE MIDDLE OF the sound playback, if the sound is long enough. |
@pixeltester Exactly how long is your boot sound? Could you send me a link to it so I can test it on my side? |
You can use any mp3 longer than around 5 seconds and it will exhibit the issue... hence the sleepthread workaround of delaying until after whatever causes this. It seems that the issue is old and used to occur a few years ago when this sysmodule was first released, then at some point the issue disappeared which I can confirm since it wasn't present on atmosphere 0.18.1 and the latest firmware at that time. Now it's occurring again. |
@pixeltester https://github.com/TheModdersDen/BootSoundNX/releases/tag/1.2.5 Kudos, EDIT: I will be uploading a video soon showing the 30 second audio clip and demonstrating the project itself. |
Thanks for trying but it didn't fix it sadly, as usual a pause in the bootsound. To be sure I tried with a fresh download of atmosphere 0.19.5 and only the BootSoundNX sysmodule added, on firmware 12.1.0. As clean as it gets. That being the case I'm not sure what other information I could give you. |
Could you try installing DeepSea, through the AIO Switch Updater? I wonder if there is something about DeepSea that fixes the issue... Kudos, EDIT: Also, what switch model are you running? Is it one that can use the fusee-primary exploit? Or do you have a Mariko switch? EDIT2: I would also recommend installing the CommonProblemResolver payload that is an option to be added with DeepSea. That way you should be able to clear all your sys-module flags, if needed. EDIT3: Here's a link to install the aforementioned app: here. |
It's an original Erista model vulnerable to the fusee-gelee exploit yes. DeepSea is just a simple all in one package that boots with hekate, something I already do normally. Also clearing sysmodule flags would not be needed because as I said attempted this with a clean atmosphere download and only the BootSoundNX sysmodule. |
@TheModdersDen what brand is your SD card and did you format it with hekate? I'm starting to suspect some weird hardware variance. |
My brand of SD Card is a Samsung EVO 256 GB Micro SD card. I formatted my SD card using the Switch OS. I was having issues with my card being exFAT, but after formatting it using the Switch's internal formatting tool and putting everything back on there (with the microSD card being formatted fat32), it has worked much better since. Hopefully this helps. :) |
@pixeltester https://www.flickr.com/gp/themoddersden/R526Z4 If anyone has any questions, feel free to let me know. Kudos, |
@TheModdersDen |
@AntiFly I am aware of incompatibility with the latest HOS and Atmosphere FW & CFW versions, respectively. This was mainly just a project to see if I could get it working, and I have not had the time or energy to fix it again. People are welcome to fork the repo, and fix the code themselves. However, I don't think I'll be updating it anytime soon. |
Quick update: I have gotten some more time on my hands and have begun testing this sysmodule on Yuzu, as to not break my current, physical switch. It seems to work, so there's a possibility of a release in the near future. Keep watching this repo for more updates. |
@TheModdersDen These are good quality SD cards formatted to FAT32 with hekate. I have no idea how to resolve it but it seems it was indeed down to some kind of hardware variance and possibly format method also. |
Thank you for this information. I will see what I can do to optimize this, but for now, I will add a statement on my repo to notify everyone about this find... |
It does not work on ams 0.19
The text was updated successfully, but these errors were encountered: