I did as well. It seems that even with the newest commits, it actually got slower for my N3DSI thinks I will return to Luma3DS v.6.1 for the moment.
Same here 6.1.1 just boots to black screen everytimeI thinks I will return to Luma3DS v.6.1 for the moment.
Did you update with StarUpdater?Same here 6.1.1 just boots to black screen everytime
Yes then after that manualyDid you update with StarUpdater?
And it still loads a black screen for you? That's strange because I've got 6.1.1 on 3 devices and they all load fine even after updating manually.Yes then after that manualy
I timed mine both with 6.1 and 6.1.1 and they're both coming in at approximately 9.6 seconds for me, so no change here. N3DS as wellThis new update is way slower:
9.98 with original
11.41 with new :/
You don't need that option checked afaikCan someone explain me in noobish terms why do I need to select "use sysnand firm when booting with R" when I'm autobooting into A9LH sysnand? I'm not booting with R since I autoboot...doesn't it already use sysnand firm by default? Should I hold R while booting sysnand to be sure it uses the firm even if I have no Emunand? Does it provide additional protection I don't know about?
It was my understanding at one point in time that Homebrew does not work well with the system in sleep mode. I'm not sure if that is your case but that's one possible answer.Sometimes, when I open the lid to wake if from standby, I find that the both screens are black and it does not react to anything, so I have to restart it. Does anyone have any idea why is this happening? I had my a9lh New 3DS on the latest SysNAND for a month or so. Been switching from hourly to stable all the time, either having the latest stable / hourly.
Can’t really say if this happened when closed the lid in-game, this time it happened when I closed the lid when a homebrew was open. The issue is not that critical since it happens so rarely, but it drives my perfectionism nuts.