PRS+: Enhanced firmware for Sony Reader, Folders, Games & more

[Mark Nord]

Originally Posted by minty95

will this firmware work on a PRS500 ?,

Hi, and welcome to MR minty,

no PRS+ supports only this models: 505/300/600/350/650/950 (the last 3 often refered as x50).
Not supported are/ and will be models: 500/700/900

[minty95]

Hi again

Thanks for your answer, anyone want to by a cheap PRS500 ?

[quisvir]

Somehow I doubt you'll find a buyer in this topic

[DoctorOhh]

Originally Posted by minty95

Thanks for your answer, anyone want to by a cheap PRS500 ?

If you are serious there is a Flea Market forum in which to offer your device for sale.

[Japes]

Any idea when v2.0 will be released?

[BenChen]

Originally Posted by Japes

Any idea when v2.0 will be released?

kartu is taking a break at the moment. Once he is back, I would think the first thing he does is release 2.0. The most recent release candidate seems to be working fine.

Sincerely,
Ben.

[albogango]

I need help removing the PRS+ from my reader (PRS-650). The Uninstaller isn't working. It freezes during the process. What are some other ways to remove this?

[BenChen]

Originally Posted by albogango

I need help removing the PRS+ from my reader (PRS-650). The Uninstaller isn't working. It freezes during the process. What are some other ways to remove this?

Hi albogango,

I have not actually tested this, but I understand it should work.

There is a way to uninstall PRS+ using the PRSPInstaller folder, that is inside the zip file you downloaded to install PRS+ in the first place. Open the installer zip file using 7-zip (or whatever archive program you use) and then double-click on "update.zip". Now extract just the "PRSPInstaller" folder. You will need to copy this folder to the root directory of your reader using a PC.

Now, while your reader is still connected to the PC, browse the PRSPInstaller folder and locate "installer.sh" and open it in a text editor like Notepad++.

There is a comment in this file telling you how to uninstall PRS+: simply comment out line 5 by putting a '#' symbol at the start of line 5. Save the file.

Now disconnect the reader from the PC and restart your reader. You should find that PRS+ no longer starts up. So connect the reader to the PC again and remove the PRSPInstaller folder and PRS+ will be gone for good.

Note, though, that the firmware has not been re-flashed. You will still need to run the latest Sony firmware updater to overwrite the non-standard firmware. (If you get an error message saying "Your device is up to date", the instructions in the first post of this thread - here - while for the 600 should also work for the 650.)

IF ANYTHING HERE IS WRONG, CAN SOMEONE PLEASE CORRECT ME!

Sincerely,
Ben.

[Analogus]

Question:

Is there any progress/research in making the 2 left outer buttons (page left, page right) user-assignable?

PRS+ in recent CB's does content a bunch of functions waiting for beeing assigned to a button or gesture. I'm running out of 'free buttons'! ;-)

A.

[BenChen]

Originally Posted by Analogus

Question:

Is there any progress/research in making the 2 left outer buttons (page left, page right) user-assignable?

PRS+ in recent CB's does content a bunch of functions waiting for beeing assigned to a button or gesture. I'm running out of 'free buttons'! ;-)

A.

Hi Analogus,

Unfortunately, no, it is not possible to assign functions to the PREV/NEXT buttons. They are handled differently by the Sony firmware.

Sincerely,
Ben.

[snarkophilus]

Can anyone explain how exactly User CSS works on PRS+? I've tried looking at the PRS+ source code, but must admit that I don't see how it works. The code to select which User CSS is obvious, but I don't see how that User CSS is used by the reader.

Is the core code of the reader itself modified, or is there some magic done externally to allow the User CSS code to be loaded?

The reason I'm asking is that I'd like to try to do something like User CSS on the PRS-T1. There's no simple way (yet!) to load CSS there to (for example) let you override fonts in a single place. Some discussion about this is on this thread

Cheers,
Simon.

[jackie_w]

Originally Posted by snarkophilus

Is the core code of the reader itself modified, or is there some magic done externally to allow the User CSS code to be loaded?

Yes. If I remember correctly, on the PRS505/300/600/x50 the Sony default css is stored in the non-visible location
res:///adobe/pxf/userStyle.css.

PRSPlus uses a firmware hack (originally by pepak, I think) to change the location to user-visible
res:///Data/database/system/PRSPlus/epub/style.css

I'm a little confused by this because at one time it was considered important that the 2 path lengths be EXACTLY the same so as not to mess up the firmware. I'm sure someone more knowledgeable will correct me if I'm wrong.

Edit: I just found this quote from kartu in an old thread

PS
I've changed path filename, hope you don't mind. In prs+ it looks like:
/database/system/PRSPlus/epub/style.css ("///opt/prps/epub/style.css" in so file, /opt/prsp is a symlink)

res:///opt/prps/epub/style.css would satisfy the identical path length requirement.

I hope you can do something with this info. I'm sending you Pommie good vibes to make my PRST1 even better

[quisvir]

Originally Posted by Analogus

Question:

Is there any progress/research in making the 2 left outer buttons (page left, page right) user-assignable?

PRS+ in recent CB's does content a bunch of functions waiting for beeing assigned to a button or gesture. I'm running out of 'free buttons'! ;-)

A.

You convinced me... support for paging buttons now added for 600+

Let me know if there are any issues, and if original behaviour still works as it should.

[BenChen]

Originally Posted by quisvir

You convinced me... support for paging buttons now added for 600+

Let me know if there are any issues, and if original behaviour still works as it should.

Well done, quisvir! I hadn't worked out how to do it, but I am very glad you were able to!

Sincerely,
Ben.

[sengian]

Hello all,

I have a little problem with my 650, which is summarize at the end of this thread
Basically, setting read/unread flag with calibre is leading to a nasty crash so any idea will be appreciated.

Thanks