-
Notifications
You must be signed in to change notification settings - Fork 46
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
Logo causing console to crash when launching from the home menu #146
Comments
Hi there, thanks for the report - have you tried reinstalling Anemone? |
@Helloman892 yes, i have tried installing it. |
Well that shows me. |
I've seen this problem a few times, it seems to be that the new logo causes a dabort in the home menu on occasion for unknown reasons. When I've experienced this problem, it only happens once and a reboot solves it - however, given that I have been unable to reliably reproduce it, I have had a hard time trying to solve it (and would not be surprised if there was some condition which causes it to be permanent rather than temporary!) Could you provide some additional information about your console? What region it is, if you've region changed, and what locale you use would all be very much appreciated. In the meantime, I'll try to get a build to you that uses the old logo and we can see if that solves it. However, I'm out for the rest of the evening and most of tomorrow, so it may be a bit (if any of the other developers want to step up and do this that would be very much appreciated 💜) Thank you for reporting this bug and sorry that I can't be of more help right now. |
@astronautlevel2 well,my old 3ds region is TWN and use traditional Chinese language. I have not change my region . But I don't know if the process of cracking has changed my locale. |
@LiquidFenrir yep, |
So the first QR code didnt work, and the second QR code didn't work either? that's weird. Can you describe FBI's error message? Or take a photo |
data abort |
@imbicile Please answer these questions:
|
I'll upload all the information later. At the moment, the console at home |
@LiquidFenrir |
Thank you, good to know! Is that dump from 1.3.0 or 2.0.0a ? |
@LiquidFenrir 2.0.0a
|
How many themes are in the Themes folder? * Try a litmus test of one theme. |
Hmm, very strange. I installed .cia Anemone3DS v2.0.0a to check what this ARM11 crash dealio is. If you launch Anemone, exit out of it with HOME Menu button, launch Activity Log, exit out of that, launch Anemone again, you get that crash. Edit 1 - What the heck did you guys do? I don't see Anemone3DS logo recorded in the Activity Log? Did you guys try to hide the icon.bin or something? Edit 2 - Here it is again for Friend List play status. I'm guessing someone had the idea of avoiding Nintendo detection by obscuring icon. My best bet is this is the root cause of the instability. |
Hi @TurdPooCharger, a couple answers: First of all, yes, you're right - that does indeed cause a crash. As far as I can tell, however, the LR and PC of your new crash isn't the same as OP's - to that end, could you a) confirm that they are the same on your end or b) create a new issue describing this? Secondly, we didn't 'hide the icon.bin' to 'avoid detection' or any such shenanigans - the reason it doesn't show up in Activity Log or on the Friends List is because of a flag not being set by us in the Makefile. It's an oversight, certainly, but nothing severe (unless, of course, this does cause the crash, in which case - thanks!). |
Hello there @Helloman892. I'll try to do my best in bug hunting the bug @Jesse-Fan reported, and if mine I found is different than his, report that one too in a separate issue. Your instant delete of @ev1l0rd's post was scary quick. Makes me considerate in not posting things nonchalantly. shivers I'll try to cross compare v1.3.0 and v2.0.0a .cia and .3dsx on my 4 GB SD build card (formatted with 32 KB cluster size, of course lol). Mess around with themes, title launches, etc. Try to find a behavior pattern. If required, I know a bit of hex edit viewing decrypted CIA files if need be. I'll gather all that I can find before posting. :) |
The recordusage flag is entirely unrelated to the crash - we never used the recordusage flag, yet this crash has only been occuring since we used the new logo. I'm not sure if your activity log crash is the same crash - could you post a picture of the exception screen? |
@astronautlevel2, I am utterly confused as I can no longer reproduce the Activity Log crash. Sorry if this seems too detailed or redundant. I want you guys to be sure what steps I took. N3DSXL (USA region), Luma3DS v9.0, original 4 GB Lexar micro SD card (FAT32 and 32 KB cluster)
I'm going to start from scratch removing v1.3.0, use Cthulhu to wipe everything, and then try installing v2.0.0a if that crash happens again. Camera on the ready for log dump picture. Actually, would you guys like the log dump file itself? Might have been easier. Edit 1 - I just did a v2.0.0a fresh install (with no prior v1.3.0) as noted in the reworked procedure and got the ARM11 crash again. Here's the log dump file of that crash from luma folder: Edit 2 - I reordered putting the log dump file before picture in case you guys might miss seeing it. Should I still open a separate issue? Maybe edit my posts over to the new issue if that's still required? |
@FrozenChen, can you provide details for each of the three cia files? What was changed from the v2.0.0a stable release? Other than commits not related to logo, are all three different varieties of reworked logo? Edit - I was looking into recreating your logo. Having a really hard time reconverting a .bclim back to the logo file. Every File Explorer got the extraction part down, but reimporting it requires SDK or ctr-logobuilder. |
oh sorry, all those are latest commit Anemone with different logos, so more and less 2.0.0a with a few neww commits, than shouldnt cause any issue |
Sure thing. I'm going to be on a dinner break. You'll probably hear back later in a few hours. Do you guys get bombarded with too many e-mail notifications? I don't mean to spam post if it's annoying. |
Test this one, same as last commit. Btw the card removed error was caused by a logo that was not 8kb (bigger in this case, just to test if the error was similar in any way), anything smaller or bigger causes a crash so logos are padded to 8kb. |
Test Case # 4 - 125SMg (FAILED) 👎 Can you build one with hblogo_bottom.bclim out of an 320x240 black/blank png? |
We have been going in circles, so instead of changing the logo we are changing the app. (to see if this goes over with the logo) |
You did read the part where the crash happens with new Anemone logo on hacky v.1.2.2, right? It's definitely the logo, but if you need more confirmation that it'll cause crashes on other homebrew titles, alright then. |
Test Case # 5 - 4g4JR (FAILED) 👎 @FrozenChen, do you handle developing the logo? I don't know if you caught my last edit in the post with Test Case # 4, but I mentioned if you can try matching hblogo_bottom.bclim to NintendoLogo_D_00.bclyt where all 320x240 black png is viewable. If you can see the bottom .bclim within the D_00.bclyt on Every File Explorer, I think that'll fix the bug. |
I already tested it, still causes the crash, cant reproduce the crash with checkpoint tho, have been going checkpoint->activity log->checkpoint at least 10 times. |
Any time you transition from title to another, never use the (Start) or (Power) button. This is reset whatever that causes the crash. Edit - If you do not follow procedures as described, you make the title stable for that current 3DS run session and will not be able to reproduce it until the next or 2nd next time you turn the 3DS on. |
Well anyway, here is what you asked https://transfer.sh/uv3W0/Anemone3DS.cia bottom is 320x240 |
Test Case # 6 - uv3W0 (FAILED) 👎 I don't get how this is suppose to cause crashes unless information about the logo's 8 KB compressed limit is flat out wrong. If that's the reason why, that means Anemone's logo file was marginally stable when it's total uncompressed size sits a teensy bit too big. Adding the fully blacked out bottom picture pushed it over the edge. This is my last idea. I can't tell you if it'll work or not. This is a cropped and trimmed version of the top image to be as bare minimum as possible. Having transparency enabled cause the file size to grow bigger. Perhaps you try recreating this very same image to see if you can get it to be smaller. Try centering it while maintaining the resolution. For the bottom image, have one black pixel place at one of the corners. Crossing my fingers on this one. Edit - You might be able to get away with transparency after all for the two black corners. This might reduce memory resources for the 3DS as that's one less color or fewer pixels to draw. It'll depend what the final .bclim total comes out to be. |
It crashed because while the compressed logo was smaller than 8kb, its uncompressed form was too big, the full black bottom screen uses 128kb while the top screen is 512kb(? On mobile rn). The uncompressed limt is around ~600kb. |
Edit - I'm at my limits of staying awaken. The latest crash readout seem like the same as others, but that might be due to lack of sleep kicking in. If you make another Anemone with cropped and compacted logo, i'll test it out when after I finish crashing myself. uv3W0 crash dump: |
Reviewing the code, Anemone should exit pretty much the exact same way through either the start or the home button. The fact that this seems to cause variance which leads to the crash makes me think that the home menu isn't properly deallocating something which leads to the logo causing some edge case crash. I'll try finding a (clean) way to lock down the home button as a solution in the meantime. |
@astronautlevel2 and @FrozenChen , I would like to test one with the top image having the black space cropped out and the bottom image with a single pixel placed where its most convenient (corner or center 0,0,0). Other homebrew logo's has theirs with smaller images. The blue wavy homebrew launcher-inspired one does image stretching to maximize size efficiency. I can't help recreate the logo from my end due to desktop linux being uncooperative and unsure how to go about calculating and adding the missing .darc footer CMAC SHA-256 found at the way end of a decompressed logo. DarcTool3DS doesn't add this back into a rebuilt logo when recompiling it. Edit - Some more info. Gotta save this beautiful logo.
|
The wave homebrew logo works because it was made with sdk tools that let you optimize better. My guess is that the umcompressed size of the logo is the problem, something not being freed correctly by home menu(?). 1st (256kb uncompressed size) 2nd (132kb uncompressed size) |
Test Case # 7 - 11GDE2 (PASSED - stability-wise) 👍 (FAILED - image quality suffered) 👎 Test Case # 8 - NVxMo (PASSED - stability) 👍 , (FAILED - quality) 👎 Are you using the ctr-logobuilder making the logo? Actually, don't answer that question. IF you're using ctr-logobuilder, see if you can input bash build with one or both of these cropped out top logo.
If you intend to use the new method of bclim conversion, let me know so I can skip grading for image quality. The intention is to see if the top logo screen estate can be reduced and not fill the entire 400x240. If this is possible without stretching the blue Anemone name section, you should in theory be able to use your original bclim converter to maintain quality while reducing the logo's total uncompressed size. |
@FrozenChen, i'm posting again in case you miss my last edit. The cropped out top logo images are 242 x 116. Double check to verify this is correct before building. |
@TurdPooCharger so my guess is was right, the uncompressed filesize of the logo is causing the crashes, those build were made just to find out in a fast way if it was the uncompressed file size so dont worry about the quality. I made this one for both quality and reduced size. |
Test Case # 9 - 3uYGM (PASSED WITH FLYING COLORS!!! WE HAVE A WINNAR!!!) 🥇
Well, time to pack it up, boys and girls. Again, sorry if there has been any trouble on my part, especially for the multiple back-to-back posts and my several presented theories that ended up being wrong. I specialize in basic GM9 scripting and not actual homebrew title development, so you'll have to forgive me for my gaps in this 3DS aspect. Hope this leads to providing a happier Anemone user experience and glad to be of service for this issue. :) |
Awesome, as soon as I merge in the new logo I'll close this issue. |
Hey, I'm having this same exact issue, anyone has any active links to the fixed version available? |
My deivece is Old 3DS with B9S (ver1.3) Luma (ver 9.0) FBI(ver 2.5.0)
i downloaded your latest Anemone3DS but its not working
The text was updated successfully, but these errors were encountered: