MathewWi / dop-iosmod

Automatically exported from code.google.com/p/dop-iosmod
0 stars 0 forks source link

Press A to continue, but wont init Wii Remote #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Load the apps
2. Pick an IOS that does not allow fakesigning

What is the expected output? What do you see instead?
It says to press A to continue, but the wii remote wont initialize, thus I 
cannot press A.

What version of the product are you using? On what operating system?
v8, Wii 4.2U

Please provide any additional information below.

Original issue reported on code.google.com by jtp10...@gmail.com on 8 Nov 2009 at 3:55

GoogleCodeExporter commented 9 years ago
Uhm, wait for like three seconds for it to come back on? Dont use the wii 
remote from
a really far away distance? No one else has this problem.

Original comment by castleva...@yahoo.com on 8 Nov 2009 at 4:21

GoogleCodeExporter commented 9 years ago
I just tried it again, same result. It only does it when you pick a bad IOS, 
for 
example my IOS 60 is original newest version and that's the default choice. So 
when 
I pick that it says "ERROR: Choose an IOS that allows fakesigning! Press A to 
continue" (or something very similar to that). At this point when I press 
buttons on 
the wii remote the four lights just flash and it wont sync up to the wii. No 
buttons 
will do anything. I have to hold the power button on the wii and shut it off. 
Now if 
I try again and pick something like IOS 249 it loads up and I get a "Press A to 
continue" which works at this screen.

It did this on previous versions also, but since it was still doing it on this 
v8 I 
decided to report it.

Original comment by jtp10...@gmail.com on 8 Nov 2009 at 4:49

GoogleCodeExporter commented 9 years ago
Okay, thank you for clarifying your report. I will look into it immediately.

Original comment by castleva...@yahoo.com on 8 Nov 2009 at 6:53

GoogleCodeExporter commented 9 years ago
This seems to have been resolved now in v9. If not, it is certainly resolved in 
the
latest svn build.

Original comment by castleva...@yahoo.com on 13 Dec 2009 at 8:21