Cracked by BiNPDA

Archive for October, 2008

Those who are still having problem changing fonts on your E65 phone, here is the solution….

[ad#chi60]

Tested and works nicely on E65 (using Verdana font) with this firmware:
1.0633.18.01
11.01.07
RM-208

Note: To get your phone firmware, press *#0000# on Idle screen

What you need:
-PC
-PC card reader
-Y-Browser or F-Explorer programs in your phone

Steps:
1. Using Y-Browser or F-Explorer, go to directory “z:” (of your phone memory). If you do not have these program, go search the forum
2. Under the “z:” folder, go to folder named “resource”
3. go to folder named ”fonts”
4. you will see list of fonts file used by your phone. Note down name of each file. Most likely you will see;

S60SC.ccc
S60TCHK.ccc
S60ZDIGI.ttf
SWABIU.ttf
SWABRU.ttf
SWARIU.ttf
SWARRU.ttf

5. Take out your phone memory card and put it into your PC card reader
6. In your PC, go to folder C:/Windows/Fonts or download fonts from websites
7. Copy the “verdana.ttf” font file (or any other font file you prefer)
8. Duplicate font file you copied above (in this case you have to duplicate 7 times) and rename them exactly as mentioned under step 4
9. Access your memory card and find folder named “resource”. If there is no such folder, create one.
10. Under the “resource” folder, create a folder named “fonts”
11. Copy all files you created under step 8, and paste under the “fonts” folder you just created under step 10
12. Put back your memory card into the phone and turn on the phone

Your phone should now have new fonts

If you want to revert back to original font, just delete all files you created under step 11 and remove the “fonts” folder (in your memory card “resource” folder)

Good luck.

Having problems when installing .ttf fonts on  N95 8GB? Now i have finally found the solution.

[ad#chi60]

1) Install FontRouter in your memory card sd, or mass storage in N95 8GB

2) using the x-plore app, make a folder in PHONE (C:/) named fonts

3) move the fontrouter.ini and paste in c:\data\fonts

4) edit the fontrouter.ini file with x-plore like this

5) search at:
;Extra font files to be loaded
ExtraFontFile=\Data\Fonts\*.*

and change to
;Extra font files to be loaded
ExtraFontFile=C:\Data\Fonts\*.*
exit and save the file

6) Copy your *.ttf font to c:\data\fonts

7) restart the phone, and now it should be free to use in (Multimidia Reader)
this option can access the memory card, then its free to be used by computer!!!

if you afterwards want to change your font
edit the fontrouter.ini file again and change
Enable=1 to 0
restart and change the fonts, then Enable again to 1 and restart new fonts are displayd now.

Good Luck!

S60 3rd Edition requires all Symbian applications to be signed, that’s one of the bigger changes that came with Symbian 9.1 operating system. This has led to some confusion among developers, who think they need to apply for a certificate (which costs money and takes time) even to be able to show a ‘Hello world’ on the screen. This was very confusing for me too for some time, but now I got it. Hope this helps somebody out there.

[ad#chi60]

Self signing with own certificate
To sign an application you can create your own private certificate, with the tools and instructions that come with S60 SDK. For step-by-step instructions, look for “How to Sign .sis files” on SDK docs folder (no online link, sorry). The catch is that even though your application will be installable, it’s still treated as ‘untrusted’ and has some limitations applied by the platform security. One limitation is that the application cannot get any capabilities other than those which are user grantable (ie. ReadUserData, WriteUserData, NetworkServices, LocalServices and UserEnvironment). I don’t really know how limiting those 5 capabilities are for real-life applications. What I do know is that some s60 apps are signed with a self-created certificate, and that application does stuff like read files and access network.

There are also some usability issues with self signed applications. The user will get an intrusive security warning (pictured below).

If you chooses to take the risk and Continue, he will be asked to confirm the capabilities that the application wants to use (pictured below). To me this dialog is not really understandable. Its purpose is to ask from the user, but I guess on the sake of usability there is no question but just Continue/Cancel choice. I don’t think an average user will understand what he just did after pressing Continue.

This was the default case for self signed applications. On some S60 devices (at least Eseries) there might be one additional step to make. There is a setting on Application manager that controls whether untrusted applications can be installed at all. If this setting is ‘Signed only’, there will be an error dialog shown and application won’t install (see below). The user needs to change the setting to ‘All’ to allow self signed apps to install.

That’s it about self-created certificate and signing. To make the picture full, I’ll mention the other options that lead to a ‘trusted’ application that can have more capabilities, and doesn’t ask anything from the user.

Freeware certification
Special route for freeware applications, that doesn’t cost anything but can take some time. More at Symbian Signed.

Symbian Signed certification
The “default” way of signing a commercial application. See more here. Cost is $350 /year for ACS Publisher ID and testing cost starting from 185€/round.

Self certification
The heaviest option for bigger developers, cost $10000 /year.