PRS-500 Sony Reader hacks collection

[diabloNL]

Originally Posted by Nogg

I'm still trying to get the hang of the way things are set up in the reader (I got a nice infinite loop last night), but couldn't you create a stub function to replace one of the mutes in applicationstart and then add the functionality in main by overriding that function?

Tried that and it didn't work.

Originally Posted by Nogg

I'm doing something similar with my testing where I override doLeft and doRight in main.xml to produce the joystick page flip functionality there, instead of remapping it in applicationStart. The only difference is that I'm relying on their built-in functions.

I'm using that a lot. So by using for example this in main.xml:

<function id="doLeft">
{Some code}
</function>

With that you can use your own code that starts when the joystick left is pressed. The PROBLEM here is that I haven't figured out how to call the original function. For example:

<function id="doLeft">
if (a == 1) {
this.doRight();
}
else {
this.doLeft();
}
</function>

This won't work because it will call it's own function that it's in. Creating a loop. So it's not possible to do the original joystick left function when a !=1 We need to find out how to listen to the keys itself rather then the function they do.

[Nogg]

Hm, that's indeed a tricky one.

Just for reference, is the original main.xml available somewhere? I wouldn't mind taking a look at that to see what our actual base is.

[diabloNL]

Originally Posted by Nogg

Hm, that's indeed a tricky one.

Just for reference, is the original main.xml available somewhere? I wouldn't mind taking a look at that to see what our actual base is.

You will have to ask to Igorsk. Don't mind a copy as well myself.

[Nogg]

Ok, I poked him.

[JSWolf]

Originally Posted by diabloNL

I have to get back to you on this one Jon. I thought the volume button worked different but now I see that the holding the volume + and - both do the exact same command (doMute). So to create history back and forward with that one function that listens if the button is pressed is a little hard to do.

The boolean key for + and - is different (0x40 and 0x41) but right know I have no idea how to listen for a pressed button other than the numeric keys by listening to their key instead of their function. This is one I have to try and find out. Could be very useful for another hack that has been sitting on my computer to be finished a while now but has a similar problem.

I will keep you posted!

EDIT: I can make it with the normal volume buttons because they use two functions. Let me know if you would like that for now.

We have now the big silver button pressed and held go page forward/page back. Can you change that to do the 10 pages forward/back instead. It semms kind of sill to have to hold for just one page turn. The history for the silver button works very well though.

[diabloNL]

Originally Posted by JSWolf

We have now the big silver button pressed and held go page forward/page back. Can you change that to do the 10 pages forward/back instead. It semms kind of sill to have to hold for just one page turn. The history for the silver button works very well though.

Unfortunately it also gives problems. If I would do that then also the joystick and small buttons page flip would do ten pages at once. I hope to find a solution because it will open new possibilities.

I will try to work it out if it is possible at all.

[JSWolf]

I hope so. Thank you for your efforts.

[ns66]

Originally Posted by diabloNL

Tried that and it didn't work.




I'm using that a lot. So by using for example this in main.xml:

<function id="doLeft">
{Some code}
</function>

With that you can use your own code that starts when the joystick left is pressed. The PROBLEM here is that I haven't figured out how to call the original function. For example:

<function id="doLeft">
if (a == 1) {
this.doRight();
}
else {
this.doLeft();
}
</function>

This won't work because it will call it's own function that it's in. Creating a loop. So it's not possible to do the original joystick left function when a !=1 We need to find out how to listen to the keys itself rather then the function they do.

just a thought, create a new method with a different name like doLeft2, in there you call this.doLeft(), so you avoid the recursive loop, and map the key to call doLeft2

[Nogg]

Originally Posted by ns66

just a thought, create a new method with a different name like doLeft2, in there you call this.doLeft(), so you avoid the recursive loop, and map the key to call doLeft2

I believe diablo already tried that and using a custom-named function didn't work.

[diabloNL]

Originally Posted by ns66

just a thought, create a new method with a different name like doLeft2, in there you call this.doLeft(), so you avoid the recursive loop, and map the key to call doLeft2

Originally Posted by Nogg

I believe diablo already tried that and using a custom-named function didn't work.

I did try it but I have probably done something wrong because it now works!

I just renamed doMute (x2) to doMuteB (back) and doMuteF (forward).
Thanks ns66!

Jon, I've made your hack thanks to ns66. It is number 16.

[diabloNL]

I found a small bug with the direct page control and basically all hacks that work with the setPage() function. The bug is that pages flipped through this function don't get logged into history. So let's say you flip from page 1 to 2 and then use the direct page control to jump to page 10 then it will not record page 10 into history. I need to find out if this can be solved or not.

[NatCh]

If nothing else, you could tack next & prev page calls onto the end of the routine. It'd be a bit brute force, but it'd work.

[diabloNL]

Originally Posted by NatCh

If nothing else, you could tack next & prev page calls onto the end of the routine. It'd be a bit brute force, but it'd work.

That could work. I could do setPage() -1 and then give the doNext function. Have to try that and if it works update the hacks catalog.

Thanks for the tip NatCh!

[Nogg]

Originally Posted by diabloNL

I found a small bug with the direct page control and basically all hacks that work with the setPage() function. The bug is that pages flipped through this function don't get logged into history. So let's say you flip from page 1 to 2 and then use the direct page control to jump to page 10 then it will not record page 10 into history. I need to find out if this can be solved or not.

Haha, I just noticed that last night, but I thought it was because I was screwing around with other stuff. Then again, maybe that was true, too. 0_o

[NatCh]

Originally Posted by diabloNL

Thanks for the tip NatCh!

Hah! I finally contributed something to the hacking effort!

That pretty much sums up my programming style, if it won't work the way it's "supposed" to, find a way that it will work.