Hacking Unofficial Luma build discussion

[Sono]

Hi @Sono ! Did you happen to find the patch for forcing the headphones out?

Ah, I'm sorry, I forgot.

I can't do it until I can get a SATA to USB adapter, because the files I need are on my HDD.

 

[Nutez]

New update (yay someone else posted so I didn't have to double )

Another update is that there probably won't be an update for a while... Mostly due to busyness, but also because I've run out of viable new feature ideas. Thanks for all the previous suggestions and sorry that some of them didn't make it (too difficult, too niche, out of scope etc.). Regardless, I'll still do obligatory updates to keep up with Official Luma and the .3gx plugin fork.

Oh and feel free to make me eat my words by pointing out any bugs or suggesting a new, must-have feature . All feedback is still very much welcome!

 

[jeffyTheHomebrewer]

Only feature I'd like is something that can take notifications from an Android device (via an app on the android) and send it to the 3DS's notifs, or a similar app but with RSS feeds like RSS-Mii on the Wii. You might not even need a custom Luma build for that!

 

[Ryu_Okami]

One last feature request: would it be possible to make a option for it to toggle wifi to off when the lids closed, and restore it when its open?
This would save a LOT of battery power in sleepmode, and since other than spotpass/streetpass nothing would use wireless, it wouldn’t do much harm.

Thank you for all the work you’ve put into this! It’s amazing!

(also closing rosalina needs like .5 seconds delay, I still always press b on stuff coming out of it)

 

[Nutez]

I’m also interested in whether there is a “true sleep” opportunity. Right now if I put it to sleep while WiFi is enabled my battery is dead within a day. If I disable WiFi before putting it to sleep my battery is alive for another two or three days.

One last feature request: would it be possible to make a option for it to toggle wifi to off when the lids closed, and restore it when its open?
This would save a LOT of battery power in sleepmode, and since other than spotpass/streetpass nothing would use wireless, it wouldn’t do much harm.

The START button WiFi quick toggle was supposed to satisfy you guys! Fine try the 'double-custom' firm attached and that should kill/resort WiFi before/after sleep if you already had Wifi on. Otherwise, it has the same features as the last release.

Thank you for all the work you’ve put into this! It’s amazing!

(also closing rosalina needs like .5 seconds delay, I still always press b on stuff coming out of it)

Cheers, it's been fun implementing the features and being able to share them. Loads of attribution and appreciation should go to all the various other people that I assimilated code from though .

(and on that note I am also waiting for the real devs at Official Luma to solve b button problem for me too )

 

[Sono]

@Nutez

Easy.

In the code where the B button is handled to close the menu, before calling the function, spinloop with the B button check until it's released.

Try this:

while(!(*((vu16*)0x90146000) & 2));

(note the ; at the end)


Edit: nvmd, I forgot that hid process registers the entire keycombo before Rosalina opens... you'd need a hid process patch to return no keys pressed if the Rosalina keycombo is pressed...

Edit2: if hid process does opposite DPAD filtering then that code could be replaced by the patch.
I would do it if I had a SATA to USB adapter, but all my 3DS patch files are on my HDD...

 

[MarioKartFan]

The START button WiFi quick toggle was supposed to satisfy you guys! Fine try the 'double-custom' firm attached and that should kill/resort WiFi before/after sleep if you already had Wifi on. Otherwise, it has the same features as the last release.


Cheers, it's been fun implementing the features and being able to share them. Loads of attribution and appreciation should go to all the various other people that I assimilated code from though .

(and on that note I am also waiting for the real devs at Official Luma to solve b button problem for me too )

You mad scientist! You’ve done it! This solves one of the biggest design flaws with the 3DS!

 

[MarioKartFan]

@Nutez I was a little worried about whether your updates to disable WiFi while sleeping would result in stability issues based on what @Sono said previously. I'm happy to report that on my N3DS, N2DSXL and N3DSXL, your latest version has been rock solid after 4 days of testing. And the battery drain is gone! I honestly cannot believe that Nintendo didn't make this a system option as it's a total game changer.

One suggestion: I think this is such a significant edit that it should be added to baseline Luma (perhaps with a corresponding Rosalina menu item to enable it). Are you interested in merging this?

 

[Nutez]

@Nutez I was a little worried about whether your updates to disable WiFi while sleeping would result in stability issues based on what @Sono said previously. I'm happy to report that on my N3DS, N2DSXL and N3DSXL, your latest version has been rock solid after 4 days of testing. And the battery drain is gone! I honestly cannot believe that Nintendo didn't make this a system option as it's a total game changer.

One suggestion: I think this is such a significant edit that it should be added to baseline Luma (perhaps with a corresponding Rosalina menu item to enable it). Are you interested in merging this?

I was considering including it in the main build, but the option would need to persist in config between reboots for it to be worthwhile... Fortunately, this brainstorming has met the "rule of three" condition for optional features that need persistent config, so I should finally deal with that issue! And I could probably even make it easier on myself by just creating an additional config file, rather than trying to merge into the Official Luma one.
These are the optional features to apply on boot that I am considering so far:

• Cut WiFi in sleep mode
• Cut power to DS flashcarts
• Automatic LED suppression
• Future: may reinvestigate the feasibility of automatically applying screen filters

Do we have any other suggestions? You can think a bit more "outside the box" for these ones as they would be optional to all users.

 

[ExiledRose6084]

I am new to this site but I just wanted to say I love your version of luma it has so many features that should of been included in the default luma 3ds I mean if you ask me this should be the new official version of luma. Looking forward to seeing more updates to this in the future.

Edit: NVM deleted my suggestion wasn't feasible lol

 

[BETA215]

Hi @Nutez! I'm having some bugs with that manual volume adjustment option.

In my N3DSXL, I once tried it and volume was adjusted fine. But now, every time I turn on the 3DS, the volume (bar?) acts strange. Like, I move it 50% and it sounds way quieter. Only in the highest 25% you see an abrupt change of volume, and sometimes it even glitches and jumps randomly from 80% to 14% or from 20% to 90%. It doesn't seems like a hardware fault, since it works as intented in TWL_FIRM and AGB_FIRM.

In my o2DS, trying to set a desired volume, it stops registering volume changes and gets stuck at 0% until resetting. Then it gets back to normal.

Do you have any other social media or Discord account, to mention some other app, to send you proof and do testing? PM me in case it's needed.

 

[Klinge87NRW]

How do I apply another *.cxi file in the Quick-Switcher-Menu? I got one for widescreen and another one for the normal aspect ratio. The normal one is just shown as red text and the widescreen one as white text. When selecting them nothing really happens and the screen stays at the standard aspect ratio.

 

[Nutez]

Hi @Nutez! I'm having some bugs with that manual volume adjustment option.

In my N3DSXL, I once tried it and volume was adjusted fine. But now, every time I turn on the 3DS, the volume (bar?) acts strange. Like, I move it 50% and it sounds way quieter. Only in the highest 25% you see an abrupt change of volume, and sometimes it even glitches and jumps randomly from 80% to 14% or from 20% to 90%. It doesn't seems like a hardware fault, since it works as intented in TWL_FIRM and AGB_FIRM.

In my o2DS, trying to set a desired volume, it stops registering volume changes and gets stuck at 0% until resetting. Then it gets back to normal.

Do you have any other social media or Discord account, to mention some other app, to send you proof and do testing? PM me in case it's needed.

\Very sorry, I thought that I had already responded to your message. Thanks for letting me know about this. I've not had time to investigate properly yet but it's now top of my list. Do you get the volume range using the official Luma firm? I will say that the volume slider apparently isn't perfectly calibrated and the volume % shown on the main menu is an estimate, so the slider being physical at the halfway point doesn't guarantee 50% volume.

On the 0% issue, could you describe how you are trying to set the volume? With the slider or d-pad? When you enter the software volume control it intentionally disables the physical slider so that people with broken sliders will have their system muted. It's not really intended for people to use both the slider and d-pad to adjust volume.

I don't really use any other accounts for the homebrew scene, but you could send a PM on here with extra information if that would help? I maybe have an old discord I could try to find when I have more time to investigate.

How do I apply another *.cxi file in the Quick-Switcher-Menu? I got one for widescreen and another one for the normal aspect ratio. The normal one is just shown as red text and the widescreen one as white text. When selecting them nothing really happens and the screen stays at the standard aspect ratio.

I think the issue maybe that you need to have more than 1 *.cxi file (all not named TwlBg.cxi) in the folder. For example, one named redshift.cxi and one named normal.cxi, both in the "/luma/sysmodules/TwlBg".
For the widescreen, are you enabling it from TwiLight menu?

 

[MarioKartFan]

@Nutez Just curious: would it be possible to intercept calls to the Miiverse Icon on the Homescreen and redirect it to the Mii app? Since Miiverse is shutdown it's totally useless, whereas the Mii app is functional and in fact required for certain games/features/etc.

 

[Nutez]

@Nutez Just curious: would it be possible to intercept calls to the Miiverse Icon on the Homescreen and redirect it to the Mii app? Since Miiverse is shutdown it's totally useless, whereas the Mii app is functional and in fact required for certain games/features/etc.

The only attempt I have seen was this one, but it doesn't seem to have been successful... Perhaps someone could try launching a different applet from the Miiverse icon, instead of a proper application?
Unfortunately, I also don't see a notification for an Applet starting, just "A Regular application has started."...
So I would say probably not, unless someone else has some ideas for patching the applet launcher or maybe polling for the Miiverse applet launch?

Edit: reverse releases might also interest

 

[Klinge87NRW]

I think the issue maybe that you need to have more than 1 *.cxi file (all not named TwlBg.cxi) in the folder. For example, one named redshift.cxi and one named normal.cxi, both in the "/luma/sysmodules/TwlBg".
For the widescreen, are you enabling it from TwiLight menu?

Yea, I genereated one file with TwiLight menu for a widescreen CXI and one for the normal aspect ratio.But I did put them in each in a seperate folder inside /luma/sysmodules/TwlBG . The insctructions here are kinda unclear to me.

• TwlBg option displays ".cxi" files from "/luma/sysmodules/TwlBg" and persists selected file name to "/luma/sysmodules/twlbgName.txt"
  
• Widescreen option displays ".cxi" files from "/luma/sysmodules/Widescreen" and persists selected file name to "/luma/sysmodules/widescreenName.txt"

I'll try to just paste them in the TwlBG folder tomorrow.

 

[MarioKartFan]

@Nutez Would it be possible to make it so that Luma remembers per-game settings for CPU and L2 cache?

There are some games that benefit from overclocking. But on others I’d rather save a bit of battery life and go with O3DS speeds. I just hate having to do it each time I launch a game. Not sure if this functionality already exists and I just didn’t know it!

 

[Nutez]

@Nutez Would it be possible to make it so that Luma remembers per-game settings for CPU and L2 cache?

There are some games that benefit from overclocking. But on others I’d rather save a bit of battery life and go with O3DS speeds. I just hate having to do it each time I launch a game. Not sure if this functionality already exists and I just didn’t know it!

I don't believe the functionality already exists. It does seem doable with some effort though... New handle for notification "A Regular application has started" -> check isN3DS -> get titleId -> retrieve bin file using titleId -> apply N3DS settings. Plus the New 3DS menu would also need to be reworked to save settings for the currently running title. I wonder how many N3DS users would want this? I'll have a look into it when I have some free time, thanks.

 

[xzst]

hi,
i bought n3ds (small one) from japan now the screen brightness is unplayable and locked at 108 at lvl 5 (reading from 3dsident,lcd tweaker) , now i managed to rise it to 172 with your tweaked luma and the screen got brighter but not bright enough . now if i go to lcd tweaker and 3dsident again it tells me that my brightness is at 132 , now if i try to increase the brightness values from lcd tweaker i can see that i can get even brighter, but it wont save my changes.
i was wondering if its possible for you to uncap the 172 limit so i can rise the brightness even further?

 

[Sono]

hi,
i bought n3ds (small one) from japan now the screen brightness is unplayable and locked at 108 at lvl 5 (reading from 3dsident,lcd tweaker) , now i managed to rise it to 172 with your tweaked luma and the screen got brighter but not bright enough . now if i go to lcd tweaker and 3dsident again it tells me that my brightness is at 132 , now if i try to increase the brightness values from lcd tweaker i can see that i can get even brighter, but it wont save my changes.
i was wondering if its possible for you to uncap the 172 limit so i can rise the brightness even further?

Pretty sure either 172, 173, 192, or 193 (don't remember which one) is hardcoded inside gsp ("graphics server process" sysmodule, responsible for initializing the GPU and LCDs), and removing this cap would require a patch to gsp.

This is not a fault of anyone, but is an intended "feature" by Nintendo itself to prevent LED damage by heat stressing it with a high backlight value.

LCD Tweaker values don't stay on new3DS, only on old3DS, and even then it randomly resets like on new3DS, except less often.

Edit: to answer simply:
Yes, it is possible, but someone needs to make a code.ips (which you can just put into a specific folder name in the luma folder on your SD) which patches this limitation in gsp.
After that, any brightness level editor or config block editor should be enough to change all 7 levels (only 5 are used).