29w ago - Following up on his previous updates, today Spanish PlayStation 3 developer MiralaTijera has updated his PS3 4.40 CFW to include System Manager 1.1 and Integrated Core 3.2.0 alongside QAFlag functionality.
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 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:
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
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)
The LEDs indicate the following:
Yellow Led Fixed: temperature below 70 degrees
Led yellow / green flashing temperature above or equal to 70 degrees
Led red / yellow / green flashing temperature above or equal to 75 degrees
Green LED remained two seconds every 10: led activity
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.
Copy the folder "flags" is inside the RAR to the device and restart with it plugged in USB000
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
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Following up on PS3 4.40 CFW and the PS3 v3.1.0 Core Update, today Spanish PlayStation 3 developer MiralaTijera has updated his PS3 4.40 CFW to include a ReActPSN RIF license bypass which allows users to run all PS3 DLC, PS1, PS2 Classic and PSN content that previously required RIF files without ReActPSN now.
To quote, roughly translated (via pastie.org/private/wlzfxhqdth8c9icqzkhjg):
Startup animation as PS1 PSX full
ReActPSN fixed (without copying or look or view of Rogero)
Rif license bypass, ie now the console will not care that the content is purchased or not, meaning that on a console without rif's not act.dat or milk should boot all content without complaining (PS2 classics for example) but that will give blackscreen fix that patching the ps2netemu to use a static klic
And a new way that I have called
Dcex, basically recharge the system mode WITHOUT changing eid dex or do to move it to the paraphernalia dex so if you ought to have enabled qa flags are nothing more ... all in a safe and have our kind of debugger to debug games and riding games manager network without any
Works well within the pack (counting we talk about that and you have the updated console with this update) I attached a file that is in a folder that says that you read this post... lv2ker.self call this what you have to manually load in the root of the dev_flash, in this case you can use the same dev_rewrite dev_blind or riding the core whenever you start, and then just change the flag ought anotherlv2 (notice this is temporary If for whatever reason fails and gives two beeps boot ay not no problem just put away the flag and return to usb boot.
Fine once started you'll see like a dex, you will see the special icons and quick sign up so far so good. pc to use tools, have the PS3 connected by network cable to your router, and Unzip the zip of the tools that associate to the root of a game, so that it looks like =
dtccons ..... ETC ..
And then you go into network settings, and see the ip info that you have assigned, you give it to right click and edit the MLTmountydebug.bat and inside you will see an ip 192.168.0.102, cambiadla for yours, keep changes and Execute... right then you will see in the game riding discless via network, and in one of the 4 windows that you open the dtccons of the debug output will see both the game and the system.
dtccons (Version 1.3 Thu Jun 08 17:05:26 2006)
Start agent ===== =====
VSH Agent Debug Version 4.3.0 (62) (Built - October 17, 2012 18:24:19)
And core 3.1.1 with updates and fixes to accommodate what was previously described in cfw.
To apply the update as usual, with the core with nosearch poneis OFF everything in the root of the pen and she will do the dirty work to be restarted and updated... and with this and a brazier to burn Rogero Enjoy with fruit donsimon
From Cyberskunk: I have been having a break but rest assured over the next day or two we will release our own 4.40
This does have some good stuff but the need to use a USB is something we are really not interested in.. We have played around with it before we released the first REX but decided against it and instead to try to achieve the same results without the need for it.
No DEX yet but having a look at the current released 4.40 cfw's we decided to add a new member to REBUG family.. LITE EDITION.
Finally, from haz367: Not the fasted way to mount but at least it works smooth, made a typo earlier about "lv2kernel" and TargetID" reporting DEX after loading "lv2ker.self" ofcourse it's only Lv2kernel = DEX and TargetID = CEX, one could flash the c2d converted dexflash.bin using the "flash" FLAG but that's a bit silly cuse there's a 4.30DEX p/p anyway.. anotherlv2 FLAG/lv2ker.self - stream game from PC test, nvm the crappy phonevideo.
So MiralaTijera has cracked the dongle and suggested the features would be implemented into his up and coming firmware. I am most interested in the feature of playback of BD iso movies from the hard drive, specifically 3D movies. Is this possible within this firmware?