Homebrew [Release] 3DSident

[MistWisp]

Side by side Username (ID)
would be nice

 

[Halvorsen]

Of course, it'd be best for the name itself.

Also, a problem since the first version I'm only now reporting. If you hold the powerbutton to force the system to shutoff while in 3DSident, the system will reboot, then trigger a fatal error. Luma's errdisplay displays something on the top screen.

 

[Joel16]

Of course, it'd be best for the name itself.

Also, a problem since the first version I'm only now reporting. If you hold the powerbutton to force the system to shutoff while in 3DSident, the system will reboot, then trigger a fatal error. Luma's errdisplay displays something on the top screen.

Lol well why would you want to use the power button when you can literally press any other button to exit the app (apart from the home button, which I still need to fix).

By the I'll go with what @Lilligant said, better to have both rather than just one.

 

[Halvorsen]

Lol well why would you want to use the power button when you can literally press any other button to exit the app (apart from the home button, which I still need to fix).

By the I'll go with what @Lilligant said, better to have both rather than just one.

I mean, nobody closes an app then turns the console off

 

[Joel16]

I mean, nobody closes an app then turns the console off

Guess I'm that 1% then
Anyways its still an issue, so I'll try looking into it.

 

[Halvorsen]

Guess I'm that 1% then
Anyways its still an issue, so I'll try looking into it.

Haha, it's not that big of a deal, I'll usually catch myself before I can press it (new 3DS problems lmao) but it isn't too problematic.

I wonder why it happens, though.

 

[Darkestnoir]

Hey,

here is a screenshot from my N3DS XL:

The "Battery percentage", "Battery voltage", "WiFi signal strength" and "Volume slider state" looks wrong.

3DSident 0.6.1 looks also wrong:

 

[Sono]

Hey,

here is a screenshot from my N3DS XL:

The "Battery percentage", "Battery voltage", "WiFi signal strength" and "Volume slider state" looks wrong.

3DSident 0.6.1 looks also wrong:

You must be using the 3dsx then... the battery and volume slider stuff only works in the cia version, because *hax doesn't have access to `mcu::HWC`.

@Joel16 I can't look at the sooscode now, but it looks like you aren't checking if you have successfully initialized some services.

EDIT: yup, you aren't checking if the functions are successful or not. You can't init `mcu::HWC` in *hax

 

[Darkestnoir]

But the rest like "Screen info" is right ?
How to use the *.cia version? Do i have to downgrade the console?

 

[Roomsaver]

Not sure about the other things, but even when I have my volume off in 3DSident and CTRaging it shows as 13-14%.

 

[Sono]

Not sure about the other things, but even when I have my volume off in 3DSident and CTRaging it shows as 13-14%.

Umm... that's not the percentage, that's why Those are the *raw* values returned by the MCU

 

[Roomsaver]

Whoops, my bad. I figured it was a bug.

 

[elBenyo]

So this does display the console serial number? I've been afraid to paint over it for a while.

 

[Darkestnoir]

If I replace the upper screen by an IPS display, 3DSident shows me this then?

 

[Sono]

If I replace the upper screen by an IPS display, 3DSident shows me this then?

I have a feeling screen types are hardcoded somewhere when the 3DS is made, so I guess it won't change.

Edit: that may be the reason why GetVendor errors out, since *all* old3DS units (iirc even XL ones too, and prolly 2DS too) have TN-only screens, so it would be pointless to implement it.

 

[Joel16]

You must be using the 3dsx then... the battery and volume slider stuff only works in the cia version, because *hax doesn't have access to `mcu::HWC`.

@Joel16 I can't look at the sooscode now, but it looks like you aren't checking if you have successfully initialized some services.

EDIT: yup, you aren't checking if the functions are successful or not. You can't init `mcu::HWC` in *hax

Im aware the Mcu services don't have access when using homebrew launcher lol. I assumed most people would use .cia and so I didn't bother checking if the functions can be initialized successfully. I guess I should since people are getting weird results.

 

[MelonGx]

Still no A9LH support.....

 

[OrGoN3]

Still no A9LH support.....

Why would it?

Edit: Also, OP, might want to update OP to read 0.70 as current version.

 

[MelonGx]

Why would it?

HBL's stability sucks & cannot display correct serial number.
CIA always imports invalid ticket.

If it has A9LH support, then I don't need to mess up ticket.db (or spend much more time to set up a new EmuNAND to not to mess up current ticket.db) for CIA, or messing with the f__king unstable HBL.

WARNING:

DO NOT SHARE YOUR 3DSident 0.7 SCREENSHOT!

022-2812 users may copy your Device ID for unbanning!

If they use your Device ID to do anything illegal, Nintendo will ban that Device ID which also bans your console!

 

[OrGoN3]

HBL's stability sucks & cannot display correct serial number.
CIA always imports invalid ticket.

If it has A9LH support, then I don't need to mess up ticket.db (or spend much more time to set up a new EmuNAND to not to mess up current ticket.db) for CIA, or messing with the f__king unstable HBL.

WARNING:

DO NOT SHARE YOUR 3DSident 0.7 SCREENSHOT!

022-2812 users may copy your Device ID for unbanning!

If they use your Device ID to do anything illegal, Nintendo will ban that Device ID which also bans your console!

Please fill me in. How does this mess up your ticket.db? And being open source, you could make your own A9LH version if you really cared to.