Hacking System Settings/Activity Log bug after system transferring

[Quantumcat]

Does anyone know how to fix this bug? I kind of actually like knowing how much time I have played for each day :-(

 

[The_Meistro]

Whats wrong with it? You dont need an excuse for playing that much everyday!
Here at GBATemp we understand!

 

[Quantumcat]

Whats wrong with it? You dont need an excuse for playing that much everyday!
Here at GBATemp we understand!

The problem is it says I have been using Settings all day and can't see what I have actually played.

 

[The_Meistro]

The problem is it says I have been using Settings all day and can't see what I have actually played.

Are you on New 3DS?

 

[Quantumcat]

Are you on New 3DS?

Yes

 

[The_Meistro]

Yes

What firmware u on?

 

[Quantumcat]

What firmware u on?

9.0 sysNAND and emuNAND.

 

[wsquan171]

I remembered that someone had the same problem showing mset as the title played all the time. I use CN as the entry point to emunand, so I have CN played all the time in sysnand. However, the activity log in emunand is working properly as long as I don't launch NTR via that cia. If I do so the activity log would consider I'm playing bootNTR all the time... I suppose this bug involves in some kernel exploit not being handled properly. I don't think as a user we have any method to solve the problem, but if you only need to know how long you have played on each title, maybe just check activity log in unlinked emunand.

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

Whats wrong with it? You dont need an excuse for playing that much everyday!
Here at GBATemp we understand!

Actually it's not even showing the playtime. It will consider you're playing even if you put the system in sleep mode.

 

[Just3DS]

Have you unlinked sysNAND and emuNAND? Unlink by system formatting sysNAND (remove console sd card before performing that) and then reloading the exploit from scratch.

 

[Quantumcat]

Have you unlinked sysNAND and emuNAND? Unlink by system formatting sysNAND (remove console sd card before performing that) and then reloading the exploit from scratch.

I remembered that someone had the same problem showing mset as the title played all the time. I use CN as the entry point to emunand, so I have CN played all the time in sysnand. However, the activity log in emunand is working properly as long as I don't launch NTR via that cia. If I do so the activity log would consider I'm playing bootNTR all the time... I suppose this bug involves in some kernel exploit not being handled properly. I don't think as a user we have any method to solve the problem, but if you only need to know how long you have played on each title, maybe just check activity log in unlinked emunand.

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


Actually it's not even showing the playtime. It will consider you're playing even if you put the system in sleep mode.

Thanks that's quite useful info. I'll make sure my NANDs are unlinked once I get home (no screwdriver at work).

 

[bowser]

Thanks that's quite useful info. I'll make sure my NANDs are unlinked once I get home (no screwdriver at work).

I hope you're joking.

 

[Garro]

Oh the same thing has happened to me ever since Gateway released its Omega firmware, I got a new o3DS and did a System Transfer from my old o3DS to the new o3DS Emunand and I have had that problem ever since, even when I changed to rxTools, I though that was a side-effect of using Emunand. I didn't know this was a bug xD

 

[wsquan171]

Oh the same thing has happened to me ever since Gateway released its Omega firmware, I got a new o3DS and did a System Transfer from my old o3DS to the new o3DS Emunand and I have had that problem ever since, even when I changed to rxTools, I though that was a side-effect of using Emunand. I didn't know this was a bug xD

Only until you mentioned I got noticed that this is a problem not only limited to n3DS. Just checked my 2DS and astonished by thousands of hours of record on using browser.

 

[bowser]

Guys pretty sure this is a side effect of using hax. Even in DS mode activity log shows that I'm always playing Alex Rider when I use my flashcart.

 

[Monty Kensicle]

I remembered that someone had the same problem showing mset as the title played all the time. I use CN as the entry point to emunand, so I have CN played all the time in sysnand. However, the activity log in emunand is working properly as long as I don't launch NTR via that cia. If I do so the activity log would consider I'm playing bootNTR all the time... I suppose this bug involves in some kernel exploit not being handled properly. I don't think as a user we have any method to solve the problem, but if you only need to know how long you have played on each title, maybe just check activity log in unlinked emunand.

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


Actually it's not even showing the playtime. It will consider you're playing even if you put the system in sleep mode.

That was me! I guess multiple threads will get more exposure=a better chance it's solved?

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

Guys pretty sure this is a side effect of using hax. Even in DS mode activity log shows that I'm always playing Alex Rider when I use my flashcart.

No it's not, I've been using mset since March and before I did my first system transfer it kept track of my play time.

 

[wsquan171]

That was me! I guess multiple threads will get more exposure=a better chance it's solved?

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


No it's not, I've been using mset since March and before I did my first system transfer it kept track of my play time.

You're right. People don't care much about the activity log, not to mention the log in sysnand. However, it's true that probably this bug involves in how emunand works on FW>4.5. The difference between ds flashcard and emunand in this case is that the activity log assumes you're still playing that game even if you turn off the console, which is quite horrible.

 

[Monty Kensicle]

You're right. People don't care much about the activity log, not to mention the log in sysnand. However, it's true that probably this bug involves in how emunand works on FW>4.5. The difference between ds flashcard and emunand in this case is that the activity log assumes you're still playing that game even if you turn off the console, which is quite horrible.

Okay, just setup a 2nd emuNAND on another SD card, unlinked from 4.5 sysNAND, Booted via mSet, emuNAND updated to the latest firmware and it's keeping track of the titles I play.

The reason internet browser has 43 minutes on it was because of RAM dumps I was doing for AR Codes.

 

[Quantumcat]

I hope you're joking.

Why? How do you normally get the back plate off? With your teeth?

Thanks for the suggestion to try unlinkibg NANDs, but it didn't work :-(

 

[bowser]

Why? How do you normally get the back plate off? With your teeth?

Thanks for the suggestion to try unlinkibg NANDs, but it didn't work :-(

For some strange crazy reason, I thought you wanted a screwdriver to open up your 3DS and literally unlink the NAND chip from the motherboard
I forgot you need to take off the back plate to get at the microSD. Stupid design Nintendo!

You don't need a screwdriver to get the back plate off, you can use the back of the stylus. That's the reason for the weird shape. I don't know if you can use the stylus for the non-XL n3DS.

 

[Quantumcat]

For some strange crazy reason, I thought you wanted a screwdriver to open up your 3DS and literally unlink the NAND chip from the motherboard
I forgot you need to take off the back plate to get at the microSD. Stupid design Nintendo!

You don't need a screwdriver to get the back plate off, you can use the back of the stylus. That's the reason for the weird shape. I don't know if you can use the stylus for the non-XL n3DS.

I did have the screws tightened, so couldn't just lever it off. I can see why you thought it was a bit crazy :-p