Homebrew [Release] Homebrew Launcher with grid layout

[SomeGamer]

It would be nice if we could download icon packs, themes and banners straight from GridLauncher! Of course I know it's a lot of work, so this isn't a request, just an idea!

 

[Gocario]

It would be nice if we could download icon packs, themes and banners straight from GridLauncher! Of course I know it's a lot of work, so this isn't a request, just an idea!

An homebrew like the updater would be nice.

 

[AmandaRose]

Yes beta 123 is crashing for me it does it any time I push up on the dpad for some reason

 

[20mark]

beta 123 hangs on my 9.0 n3ds too.
what i do: click on the "home" button bottom left and then hangs.

 

[Astoria]

Latest version is crashing every time I try to use the title launcher or it's needed by any other app (like savemanager)

 

[hobbledehoy899]

...I think it's time to re-evaluate some code...

 

[kabii-sama]

Yes beta 123 is crashing for me it does it any time I push up on the dpad for some reason

To be more specific, I think it crashes when you press up to move to the settings... or down to the title launcher. Basically I can only access whatever's in the corner icons by tapping them. For now disabling the option to access the corner icons using the d-pad seems to prevent the crashes. Wasn't this an issue in a previous version of the launcher though? If so, I imagine it shouldn't be too hard to fix.

I will say that the title launcher works perfectly fine for me. Other such apps like HANS seem to work for me as well, although they all take forever to load thanks to all the software I have on my 3DS.

Edit: I've been using this launcher for a while now and just noticed the option to excite the water on the top screen with key presses is absent. Was that removed due to issues it caused? If so, I suppose it's not too big of a deal; that feature was probably the most insignificant option available.

 

[mashers]

Important
Please download beta 122 from this link:

Raw

This will stop the crashing on opening the title launcher and using the D-Pad navigation. I don't know yet if it fixes the other issues with launching titles through SVDT etc. My next priority will be to sort out the crashing - that will be beta 124. Beta 125 will then attempt to address the issues with launching through SVDT/Brain dump etc.

 

[mashers]

Ok, I've now reverted the source to a state consistent with beta 122 and the crashing has stopped. I'm now gradually reintroducing the changes from beta 123 and testing every step of the way to try to work out what went wrong.

 

[RedHat]

Ok, I've now reverted the source to a state consistent with beta 122 and the crashing has stopped. I'm now gradually reintroducing the changes from beta 123 and testing every step of the way to try to work out what went wrong.

Oh, programming. Keep at it, mashers, we know you'll do it!

 

[mashers]

Oh, programming. Keep at it, mashers, we know you'll do it!

Thank you buddy. That is exactly the encouragement I needed this morning after a sleepless night worrying about this It doesn't help that there isn't any debugger or useful console for the 3DS. That means FTPing in to check log files after every test...

 

[daxtsu]

Thank you buddy. That is exactly the encouragement I needed this morning after a sleepless night worrying about this It doesn't help that there isn't any debugger or useful console for the 3DS. That means FTPing in to check log files after every test...

Sure would be nice if it had a crash dump screen like the Wii and Wii U, heh.

 

[TheReturningVoid]

Sure would be nice if it had a crash dump screen like the Wii and Wii U, heh.

But how does one even read that stuff? All I can understand is "Exception (DSI) occurred!"

 

[daxtsu]

But how does one even read that stuff?

On the Wii you would just use addr2line with your elf file and follow the stack trace, entering the addresses to see where it crashed. It was tedious, but it was better than what the 3DS has (i.e., nothing).

 

[VinsCool]

But how does one even read that stuff?

By logic, memory adresses are all shown in there. The one who get a crash dump will know exactly what is going on.

 

[TheReturningVoid]

On the Wii you would just use addr2line with your elf file and follow the stack trace, entering the addresses to see where it crashed. It was tedious, but it was better than what the 3DS has (i.e., nothing).

By logic, memory adresses are all shown in there. The one who get a crash dump will know exactly what is going on.

\

Ah, I see. It all makes sense now.

 

[mashers]

I found the bug! Of all the things it could have been, it was the part of the code which stops the top screen panel from drawing if the currently selected menu item has a full screen banner. The launcher was trying to retrieve the currently selected menu entry and then assessing its values relating to the banner. But if no menu item is selected (i.e. during dpad navigation or when transitioning to the title menu), it wasn't getting a valid menu entry back and that caused the crash. I've added some checking to this process now and it seems to be working perfectly.

Please update to beta 124 using the online updater and I hope you will find that this is now working

--------------------- MERGED ---------------------------

I think I've also just sorted the problem with launching titles through SVDT etc. I'm just downloading braindump to test it.

--------------------- MERGED ---------------------------

Ok, braindump seems to be working as it's showing the correct title ID when I open it. I've just tested with System Settings, and now I'm dumping my DKCR3D cart. How do I check what it has actually dumped?

 

[Deleted-236924]

I believe braindump dumps things im its 3ds folder (so sdmc:/3ds/braindump/)

At least that's what I remember, I might be wrong.

Also it takes a while to dump actual games for the most part, with braindump, so be patient

 

[mashers]

Well, the braindump screen says it's putting it in /<titleid>/. Will it be apparent what has been dumped just by looking in that folder?

 

[Deleted-236924]

You should have an exefs.bin and a romfs.bin in that folder.