Hacking cIOSX rev21: controller lag [FIXED!]

  • Thread starter Thread starter netspy
  • Start date Start date
  • Views Views 114,058
  • Replies Replies 395
davebaol said:
Xabby's mod works for me.
Tested with wiiflow, gx, and cfg
Davebaol, do you know much different or what was changed between your mod and Xabby's mod? Just wondering.
 
I believe he has changed the values for time and/or repeat_time when calling the function os_create_timer.

I'm just speculating, when he will post the modified source we will know for sure.
 
just to sum up...

xabby666's EHCI mod is superior to davebaol's, correct?
And this is the only module that needs to replace any of wanin's official rev 21 modules to fix the controller lag AND the wiiflow sync issue, correct?

Once confirmed, I'll try to put out another quick ModMii beta so more ppl can test.

Thanks goes out to xabby666 and davebaol, both of whom have worked very hard on troubleshooting this for everyone
biggrin.gif
 
XFlak said:
xabby666's EHCI mod is superior to davebaol's, correct?
And this is the only module that needs to replace any of wanin's official rev 21 modules to fix the controller lag AND the wiiflow sync issue, correct?
That's correct!

EDIT:
xabby, mi hai battuto sul tempo.

PS: Siamo troppo forti!!!
happy.gif



EDIT 2:
Posta i sorgenti prima che inizino a rompere.
smile.gif
 
Sorry to say this guys but I tried xabby666s new modded ehci.app with cios249 and base57 and the sync issue with wiiflow (latest) is still there. When using the forwarder syncing is slow as with the davebaols ehci.app (7-8 sec). Syncing when starting through HBC it is a little bit faster now (about 5 sec).

Since this happens only here, you can ignore this and use the new modded superior ehci.
laugh.gif


Games still run fine, lagfree.

So Xflak, use the new EHCI.app for ModMii.
 
davebaol said:
XFlak said:
xabby666's EHCI mod is superior to davebaol's, correct?
And this is the only module that needs to replace any of wanin's official rev 21 modules to fix the controller lag AND the wiiflow sync issue, correct?
That's correct!

EDIT:
xabby, mi hai battuto sul tempo.

PS: Siamo troppo forti!!!
happy.gif



EDIT 2:
Posta i sorgenti prima che inizino a rompere.
smile.gif
Viva la google translate, yeah better post the source code..

Note: i tested a bit too, my initial feeling is that the fix in other modules does nothing extra (nor does something worse).
So cheers to davebaol and Xabby666...for the effort of improving cIOS rev 21.
 
tueidj said:
So you're just going to ignore me and call os_restart_timer with 2 arguments, which could potentially crash IOS?
if you are able to share a better EHCI module, I think I speak for everyone when I say we'd be more than happy to use that instead. I bet it would only take all of 10 minutes for you to do... so why not?

edit:
Just think about it. If you were to do that, I'd have to add you to ModMii's credits and u can gloat about that as you point and laugh at my batch programming skillz, lol

Seriously though, I notice that you often tell people how to do something instead of doing it yourself. I've always wondered why you don't just do it yourself, especially when no one is able to follow your complicated instructions (not because you don't explain it well, but just cuz its over most ppl's heads to begin with). Anyways, I'm sure the advice your giving is sound... but I doubt some1 else from this thread is going to be able to implement your suggestion without some serious help... and u know what they say... if u want something done right, do it yourself!!
biggrin.gif
 
tueidj said:
So you're just going to ignore me and call os_restart_timer with 2 arguments, which could potentially crash IOS?
I'm confused now, if i read back, i see that davebaol looked at the rev 19 EHCI and corrected the REV21 EHCI.
Am i missing here something, or is this call also in rev 21?
 
I believe that tuedj is saying that os_restart_timer needs to be called with 3 arguments, rather than 2 arguments which is what the source code is currently doing. I think that someone else in this thread (can't remember who, sorry) tried doing this earlier, but it failed because they didn't use the correct values.

I agree with Xflak that this correction to the source code is probably a simple thing to fix for someone as experienced as tuedj, and that if he can help in any way that would be great.

EDIT: sorry for the double post.
 
xfcrowman said:
I believe that tuedj is saying that os_restart_timer needs to be called with 3 arguments, rather than 2 arguments which is what the source code is currently doing. I think that someone else in this thread (can't remember who, sorry) tried doing this earlier, but it failed because they didn't use the correct values.

I agree with Xflak that this correction to the source code is probably a simple thing to fix for someone as experienced as tuedj, and that if he can help in any way that would be great.

EDIT: sorry for the double post.
I agree too, and i read that part too, but i thought rev 19 EHCI was not used anymore, so really my question is: does rev 21 EHCI has the same amount of os_restart_timer arguments as rev 19?
 
@Etheboss, I haven't actually looked at the source personally, but from what I gather from this thread, both rev21 and rev19's EHCI module's os_restart_timer is called with 2 arguments, when instead it should be called using 3 arguments.

edit: incorrect
 
xfcrowman said:
I believe that tuedj is saying that os_restart_timer needs to be called with 3 arguments, rather than 2 arguments which is what the source code is currently doing. I think that someone else in this thread (can't remember who, sorry) tried doing this earlier, but it failed because they didn't use the correct values.
Yeah I confirm. It was me.
Anyway all hermes cios and waninkoko cios till rev20 excluded call os_restart_timer with just 2 arguments and nobody cares so far since it seems to be harmless.
But I believe that if waninkoko added the 3rd argument (actually the 2nd in positional order) there must be a reason.

QUOTE(xfcrowman @ Jan 28 2011, 08:00 PM) I agree with Xflak that this correction to the source code is probably a simple thing to fix for someone as experienced as tuedj, and that if he can help in any way that would be great.
And I agree too.
 
XFlak said:
@Etheboss, I haven't actually looked at the source personally, but from what I gather from this thread, both rev21 and rev19's EHCI module's os_restart_timer is called with 2 arguments, when instead it should be called using 3 arguments.
No XFlak, in rev20 and rev21 os_restart_timer is called with 3 arguments.
All other revs use just 2 args.
 
davebaol said:
XFlak said:
@Etheboss, I haven't actually looked at the source personally, but from what I gather from this thread, both rev21 and rev19's EHCI module's os_restart_timer is called with 2 arguments, when instead it should be called using 3 arguments.
No XFlak, in rev20 and rev21 os_restart_timer is called with 3 arguments.
All other revs use just 2 args.
So if xabby666 modded the rev21 EHCI module (which seems very logical to me), os_restart_timer is called with 3 arguments and all is good.

Test are already positive, so i think Xflak can publish a new Modmii beta with the latest EHCI mod.
 
Xabby has modified rev21 modified by me.
Actually in both fixed versions os_restart_timer is called using 2 arguments like it was in rev19.
So if this is really a problem it's still there.
However it seems nobody is reporting unexpected behaviors.
 

Site & Scene News

Popular threads in this forum