PS3 Webman MOD switching back to SYSCON after a few seconds of using Dynamic Fan control

[CodaCM]

Hello,

This is my first post, and I wanted some help with this. It also says SYSCON 8 is disabled, so I can't log in to PSN most of the time. To fix It, I have to turn COBRA off and then back on, which I find very annoying as I have to do it almost every time I turn my PS3 on. I also have Evilnat CFW 4.91 on a PS3 Slim 20XXB.

Thanks,

Coda

 

[aldostools]

I guess your mistake could be that you're not saving the settings after change them in /setup.ps3

Try deleting /dev_hdd0/tmp/wm_config.bin then reboot to restore the default settings in webMAN MOD.

It by default selects dynamic fan control. After reboot, go to /setup.ps3, check "Disable content scan on startup" and SAVE the settings.

 

[LuanTeles]

I guess your mistake could be that you're not saving the settings after change them in /setup.ps3

Try deleting /dev_hdd0/tmp/wm_config.bin then reboot to restore the default settings in webMAN MOD.

It by default selects dynamic fan control. After reboot, go to /setup.ps3, check "Disable content scan on startup" and SAVE the settings.

Aldo, do you have any idea what might be happening? On PS3 Pro mod, my webMAN PS2 settings are being overwritten by Cobra's. No matter what i set, the values are being loaded from cobra

 

[CodaCM]

I guess your mistake could be that you're not saving the settings after change them in /setup.ps3

Try deleting /dev_hdd0/tmp/wm_config.bin then reboot to restore the default settings in webMAN MOD.

It by default selects dynamic fan control. After reboot, go to /setup.ps3, check "Disable content scan on startup" and SAVE the settings.

and how do I do that?

 

[aldostools]

and how do I do that?

Use a file manager or simply uninstall webMAN MOD and reinstall it.

 

[aldostools]

Aldo, do you have any idea what might be happening? On PS3 Pro mod, my webMAN PS2 settings are being overwritten by Cobra's. No matter what i set, the values are being loaded from cobra

Please open an issue in github and include screen captures of before and after the issue.