Below are the details, roughly translated: UPDATE 3: Warning, this update if it is best installed first previous... I copy and paste the post of Estwald because of what you put on I have nothing more to add... Estwald wrote:

First of all, Miralatijera me that if they "saw" made ​​public the Core in its name and the rest is of my own by collaborating

On the other hand, the uniqueness of this, is that just your CFW offers the ability to launch applications in the background and these things, show that when the CFW provide useful ideas and instead locked away, are offered the possibility the dev, they can do things and are more likely to do so. In contrast, others, think that by taking out a CFW automatically have to give support... it will be no [poraki]

You try hard enough and you provide the info or you worry your porting (I mean Iris Manager), as did Miralatijera (in 4.31 gave us all the information he could and at 4.40, made the port it, and I then managed some little things: well if you do things), because if not directly rule and I stand so quiet [burla2].

And with that, let the matter:

The Core

The core novelty presents how the possibility of launching an application in the background, which is called "sm.self" and installed in root / dev_flash, which has advantages and disadvantages:

Disadvantages:

If the application in the background hangs the system, obviously, the system will not advance from that point. So the flag is provided removes, but obviously, if someone puts nosearch flag, the result would be a semibrick (have to reinstall CFW). So careful with this.

Access to the system is limited to exports of syscalls and basically liblv2.

That the application is in the background, does not mean you do not eat resources, obviously

Advantages:

The ability to control the temperature and fan without affecting other processes directly or maintaining "awake" USB devices tend to fall asleep, it seems a good start. The application runs on a separate plane to vsh.self, PSX emulator or PS3 game (obviously on the PS2 emulator, at least natively on the FATs, the LV2 ceases to exist and our application dies) and processes not stop LV2 how true alternatives.

The System Manager

The System Manager is how I called the application that will run in the background, basically consists of three separate parts:

1) The main: The main loop is enclosed in a 1 ms in duration to receive commands via address 0x450 of LV2 with which to configure the application (you can set the thread priorities, changing temperature tables, and mode time device activation and get some additional information)

2) FanCtrl_Thread: basically, this thread does the same as the payload that I developed for Fan Control Utility (Incidentally, the application has been updated to the 1.5 to work with this without problems)

The advantage is that unlike the payload, this does not affect directly the processes, so that should not happen reporting problems some users of the application. Basically, this is how I would have liked me to do from the beginning, but until now, there was no way.

Added a small payload that is housed in the direction of LV2 0xF70, like Fan Control Utility, but only to protect the syscalls sm_shutdown and provide compatibility with the previous system, so that it can be integrated in Iris Manager support.

3) UsbWakeup_Thread: This thread has 3 running modes and basically deals with "wake up" USB devices that tend to "sleep" for lack of use, causing problems in games.

The wake mode is to write in a file called "nosleep" we can create in root of the device (no matter that has length 0, just exists or not) for the SM know or not to use units. By default, it does every minute, but you can program steps of 10 seconds (2560 seconds maximum, to which we must add two seconds for the indicator).

USB storage devices, can be divided into hard drives and flash memory devices that are not as convenient to be writing all the time. This is the reason that is delegated to the user to create "nosleep". Indeed, in some games, you must set BD Emu and that makes the USB pass renamed as / dev_bdvd, which also supported.

The three modes are: 0 -> disabled, 1 -> enabled for a single device and 2 -> enabled for all devices (this is the default)

Default operation (autonomous)

Just load the SM, the settings are:

Temperature control / fan Fan Control Utility equivalent asset.

Wakeup writing on all devices, including / dev_bdvd (if a USB device allow writing) on, proceeding to write 1 time every minute or so. Obviously, writing only affects those devices with the file "nosleep" (elsewhere, could detect read access as much)

Leds off for two seconds: indicate a write access to USB device. This is important to know, because we should not unplug a USB device in a deed, obviously (we wait for the LED to turn off and unplug a few seconds later)

If you have the flag "nosearch" active, unset. Copy the Core (sys_init_osd.self) and root sm.self in a pendrive and expects the restarts (for many, to install the core and then to install the system manager)

If you want to uninstall sm.self then adds the flag "removesm"

If you want to prevent a USB device "sleep" create a file "nosleep" in root of the device (whether measured 0 bytes)

If you already have the previous version, simply copy sm.self in USB root, put it in USB000 (closest to the reader) and reboot.

If you have the core 3.2.0 then go here (elotrolado.net/hilo_update3-cfw-4-40-miralatijera-100-core-3-2-0-integrado-qaflag_1880798) and following the instructions, replaces the old sm.self by the new.

Uninstalling:

Copy the folder "flags" is inside the RAR to the device and restart with it plugged in USB000

USB Wakeup:

Create a file called "nosleep" (no extension, which I already see it coming XD ) In root of the device you wish that every so often, are accessed by writing to keep alert

Psmaniaco wrote: Estwald a question, in your Iris Manager I think you added the temperatures of Cell and RSX right? Are the temperatures of the sensors you mentioned further back? A greeting.

If put another application in the background... Yes and no. For starters, you can only be accessed through syscalls or liblv2 exportable functions in PSL1GHT. Make them the idea that this is pre-vsh.self and operates completely autonomously. Also, you need a series of special construction flags or not work (which I include in the Makefile to scetool).

If not done well, the best thing you can get, is to ignore your application By the way and for that matter, if you delete the sm.self you can do it directly (root is / dev_flash and just mount it in writing) or otherwise, add the flag "removesm" to do it for the core you: no need to remove the core.

And by the way, a recommendation mine: NEVER put no root any files that could be copied by the core unless it is that what you want: if you put a vsh.self in root, for example, automatically copies and going to care if it's a different version. So very careful with that, it can cause a semibrick

I am just wondering if there is a good thread around where you actually get a good break down of all the steps it takes to mod your ps3? I still have the ofw 4.40 and haven't bothered updating because it's sooo complicated to find the necessary information! It's like there is no clear path do do anything. i tried the newest 440 rogero but it stops after 71% says file corrupt.

I do appreciate that you can eventually find what you need but I would much appreciate it if someone could guide me to a thread or to the necessary files you need to update to the latest version that allows playing homebrew games.