Don't tell me what I should do. The bug should be noticed, I can solve the problem with complex method,I'm not sure what point you're trying to get at.
but the homebrew is not designed to act as it
Don't tell me what I should do. The bug should be noticed, I can solve the problem with complex method,I'm not sure what point you're trying to get at.
um... okay? I'm pretty sure this "bug" has been around for a while. Not everyone has the ability to use anything but .3dsx versions.Don't tell me what I should do. The bug should be noticed, I can solve the problem with complex method,
but the homebrew is not designed to act as it
um... okay? I'm pretty sure this "bug" has been around for a while. Not everyone has the ability to use anything but .3dsx versions.
Ninjhax 1.x is a kernel exploit, meaning it has full control of the 3DS. Ninjhax 2.x are user land only, so chances are it's the best that it can do.The bug even doesn't exist under ninjhax 1.1. So no one talk about it means it's not a problem?Ridiculous.
New comers with Ninjhax 2.0 may accept it ,but it is malfunction
The reason is just no one reported that.The full function was there before Kernel exploit was implented.Ninjhax 1.x is a kernel exploit, meaning it has full control of the 3DS. Ninjhax 2.x are user land only, so chances are it's the best that it can do.
I'm sorry but I have no idea what kind of point you're trying to make anymore.The reason is just no one reported that.The full function was there before Kernel exploit was implented.
Also Ninjhax 1.1itself isn't kernel exploit, the kernel exploit is libhax/ memchunhax...
I'm sorry but I have no idea what kind of point you're trying to make anymore.
Aren't workarounds very common? This bug has existed for a while. Why should people need to wait for a bug to be patched when they can use a workaround in the meantime? I never said you can't report a bug.DON'T TELL OTHERS WHAT THEY SHOULD DO TO AVOID A BUG WHEN THEY ARE REPORTING BUGS.
It is not the right way to help develop a software
A while? 1.5.1 came up just today,didn't it? At least I can't fix it myself ,but what I can do is bug report.Aren't workarounds very common? This bug has existed for a while. Why should people need to wait for a bug to be patched when they can use a workaround in the meantime?
Stop acting like a moron toward people who helps other, will yah?DON'T TELL OTHERS WHAT THEY SHOULD DO TO AVOID A BUG WHEN THEY ARE REPORTING BUGS.
You mean when something is broken ,just say ok ,not to use it?
I DO NOT NEED WORKAROUND ,THANKS.Stop acting like a moron toward people who helps other, will yah?
Its a small bug and when people cant figure out how to solve it, people help them by telling the workaround.
Not happy with that? Too bad. Make your own bugfree homebrew based on ninjhax2.1 and thats it. Imagine if you make a homebrew that aint perfect, wouldnt you like if people would help others to use your homebrew? Or would you tell those people to stop telling others what to do?
..think..
You could simply say you don't need the help.I DO NOT NEED WORKAROUND ,THANKS.
I HAVE ALREADY KNOWN HOW TO SOLVE IT MYSELF BEFORE HIS ANSWER.
YES,WITH SETTING BACK DEFAULT THEMES.
BEFORE HELPING ME .PLEASE UNDERSTAND WHAT I AM DOING.
I AM TALKING TO THE DEVELOPER.
THAT IS ALL THANK YOU
I am not asking for a help, that is obvious.That is why I quoteYou could simply say you don't need the help.
I mean when I told you a simple workaround, you could have simply stated it.I am not asking for a help, that is obvious.That is why I quote
Rinnegatamante
The developper already knows it. And you're not talking to the dev, you're talking to us, saying ''dont tell me what to do!'' and whining about a bug that you seem to take personal, you're like 'omg its a bug its a bug! It cant be there!'I DO NOT NEED WORKAROUND ,THANKS.
I HAVE ALREADY KNOWN HOW TO SOLVE IT MYSELF BEFORE HIS ANSWER.
YES,WITH SETTING BACK DEFAULT THEMES.
BEFORE HELPING ME .PLEASE UNDERSTAND WHAT I AM DOING.
I AM TALKING TO THE DEVELOPER.
THAT IS ALL THANK YOU
Yes,thank you ,But that is not my purpose.I just want to help with the next version,I mean when I told you a simple workaround, you could have simply stated it.
Already? Oh?With 1.5.1?Could you please have a look what I said?The developper already knows it. And you're not talking to the dev, you're talking to us, saying ''dont tell me what to do!'' and whining about a bug that you seem to take personal, you're like 'omg its a bug its a bug! It cant be there!'
Please stop acting like an ass..just let it go.
Yup, because its been a bug for a while, even before 1.5.1 if using ninjhax2,1, what dont you understand?Already? Oh?With 1.5.1?Could you please have a look what I said?
I think I've found a bug ≠ I need a hand
Yup, because its been a bug for a while, even before 1.5.1 if using ninjhax2,1, what dont you understand?
Btw, the real problem here is that you talk to people like an ass, please stop acting like this and re-read all your last messages..you're not reporting a bug, you're complaining to someone who was only giving you advice, if you dont need advice its okay, but dont reply as a moron.
Not the sharpest pen in the box, aint you?..here.s another one who didnt learn to respect others, and yet he comes on public forums..pathetic..Ah?Can‘t you see the deference between 1.5 &1.5.1 when installing a theme?
Also, don't tell me what I ought to do/should do/be supposed to do.
And I'm not asking to be taught how to solve some issues with informal methods.
If you get a black screen because of a wrong theme, you can solve it by deleting the cache of the theme in the right folder..a couple of pages ago i helped someone with the same issue (wich i once had ) but i dont remember exactly the name of the file..i think the folder was something like 00000002c or something..I can't win....I finally got CHMM to work...but why would it soft brick my console? Grrrr