Develop Bugs

BA Screen Resolution Hack (960 X 1280 dpi) at 268288 colors

Oh **** ... it didnt get in ....
sorry folk i forgot to zip it up before attaching.
there you go ...
btw ... i'm already using the hack ... no side effects at all ... just a more beautiful screen !!!!

Tis is how i got the numbers
16 bit = 64K = 65536 colors
1 bit = 65536/64 = 1024 colors
18 bit = 262K = 268288 colors (262 X 1024)

Does it work for Blue Angels

Re: Does it work on Blue Angels ?
The answer is "YES !"
I am using a Blue Angel with This Hack and I'm very happy about the result !!!
Try .... If u wanna revert just jot down the values so u can key them back in.
I never thot it was possible but by heaven's will I chanced upon the genius who discovered it .... i lost the link but lucky i saved it as mht. file.
Now i want u all Blue Angels out there to have the same beautiful screen i am enjoying !!!
Cheers Mates
One for all and all for One !!!

Danger !
Please don't try going above resolutions more than 18 Bit
Although it is possible to do it ... there's no guarantee that the hardware can support resolutions that high .... if your pixels start dying it's your own fault.
18 Bit is safe and good enough .... don't kill the screen by overdosing it !!!
___________________________________________________
One for all and all for one

Would someone be kind enough to post a guide on how to do this in their own words?
I've tried both apps suggested and also replaced the files but nothing seems to work.
ozVGA's files already exist in /windows and wont let me overwrite them, and when I start up SE_VGA it opens a dialog box without any text and when you close it the closes the app.

Biohead said:
Would someone be kind enough to post a guide on how to do this in their own words?
I've tried both apps suggested and also replaced the files but nothing seems to work.
ozVGA's files already exist in /windows and wont let me overwrite them, and when I start up SE_VGA it opens a dialog box without any text and when you close it the closes the app.
Click to expand...
Click to collapse
I agree with Biohead, instead of reading long info from the link on you rar file, why don't you just give us step by step how you make it worked on yours.
TX

here it goes .....
HKEY_LOCAL_MACHINE\Drivers\ Display\Active\Built In LCD
In "LCDcolors" Enter Decimal Value 268288
HKEY_LOCAL_MACHINE\Drivers\ Display\Citizen
In "CxScreen" Enter Hexadecimal Value 30
In "CyScreen" Enter Hexadecimal Value 30
Install OzVGA
These are the settings I use ...
ozVGA
MEnu&Bar Font 650 (Checked)
System Font 700 (Checked)
Hor. Scrollbar 10
Ver. Scrollbar 10
Min Scrl Thumb 10
Fonts Arrays :
SEvga : 500,600,650,800,1000
SEvga : 750,900,975,1200,1500
oz=SE* Ratio 2
Soft Reset
Goto Start/Settings/System/Screen
Set the font size to (Smallest)
As has already been pointed out, a lot of applications don't take into account the system-level font sizes in the Registry. Also, the vast majority of them doesn't check for the actual size of the screen to give you exactly the same view in VGA and in QVGA. (The most notable exception is the excellent document reader application, µBook , which offers the same resolution in both QVGA and VGA modes.)
View the screenshots below for an idea of wat it'll look like.

:shock: Can Someone please tell me why my screenshots don't show up in this page ?????
:shock:
:?: :shock: This Page Does Not support JPG files ????? :shock:

Today Screen

hardware?
friends, do our blueangels' lcd hardware support that resolution? Or is it just a programm tweak and is not a real resolution enhance?

i have no idea at all whether the hardware supports the resolution ... but the OS definitely allows for different resolutions.
Does anyone have any idea how to check if it is real ???
The only way i know how is to compare the same screen with same brightness settings against another device which is 18bit screen ... like the BenQ P50.
If anyone can do it ... please post your findings Thanks
I can only afford 1 device ... I am Poor

Thanks for the setp by step info...Iam going to try it...so it is safe to modify all the setting right?

yes it is absolutely safe ... just remember your original settings so you can key them back in if you want.

Hi Ivan, I have try it, not working so good, and the text are mixed up, even after changing the setting to the smallest, and the resolution remain the same, yes I follow your step by step, Thanks anyway.

Oh dear ... Sorry about that ... But the prospect of having an 18bit resolution blue angel would really have been a dream cum true ...
I'll experiment some other settings and post it for u guys can try ...

Will it work with a Blueangel running WM5?
Thanks.

I got no Guts to flash my ROM ... So I dunnoe if it work on WM5
But it seems quite safe to change the values back and forth ... it only affects how your screen displays stuff ... if you don't like still can go back to original settings ... I'm still experimenting

Need someone with WM5 to have the guts to try it and tell us his views.

I'll do it, but someone will REALLY have to create a really basic guide. I've never really gotten into modifying the Windows Mobile thing so I'm not 100% whether I'm doing it right.
If someone creates a 100% step by step guide then I'dbe more than happy to try it out. I understand WHAT I have to do, its just HOW to do it.

Change Calendar interval

Hello guys,
does any one know how to change the calendar interval in outlook PPC?
I would like it to show 15 minutes intervals
I believe it can be done through regedit (hopefully)
thank you for your help
PS: I have a "prophet" QTEK S200

Don't think you can do that. The built-in calendar program seems to have a minimum of half-an-hour slot. If you look at the wiki
http://wiki.xda-developers.com/index.php?pagename=WM5_Tweaks_Other
at the section "Change Calendar 'working hours'", the registry uses 1/2 hour can a unit for its working hours.

Thank you hanmin,
that was helpful, but I faced a new issue while doing this.
the regedit program that I'm using does not write DWORD key in hexadecimal values, only decimal.
any link to a good regedit program?
I appreciate your help

i use total commander
it dont matter if you cant write it in as hex you can just write it as the dec value the hex is

For a good and free reg editor I recommend PHM:
http://www.phm.lu/Products/PocketPC/RegEdit/
And in any case like Rudegar said, DWORD is just a number (4 bytes long, ranging 0 - 4'294'967'295) so you can convert hexadecimal values using desktop windows calculator.

selimlb said:
Thank you hanmin,
that was helpful, but I faced a new issue while doing this.
the regedit program that I'm using does not write DWORD key in hexadecimal values, only decimal.
any link to a good regedit program?
I appreciate your help
Click to expand...
Click to collapse
Probably you've got my message wrongly. You want 15 mins intervals, right? My previous post said that it is not (seemingl) possible. The minimum is 30 minutes.
If you want 30 mins interval, just open your Calendar, at the `Day` view, then Menu->Option->Show ahlf hour slots
You don't need to reg edit your phone.

it seems that it's impossible to change it to 15' intervals
but the view of 1/2 hour interval is a satisfying option
Thank you guys! a lot

WM6 contact lookup key mappings

Hello fellow T-mobile Dash users running WM6 beta...
As you all know, there is a bug (if that's indeed what it is) in the "smart dialing" capability that inserts "A,B,C" for numeral 2, "D,E,F" for numeral 3, and so on. Numeral 1 is a metacharacter (i.e. typing 1 repeatedly will just select all of your contacts).
I was looking in the registry and found a few keys that look interesting.
They are:
1) HKLM/Security/Phone/PhoneKeyMatch
2) HKLM/Software/Microsoft/Shell/PhoneKeyMatch
There could be others, possibly relating to the keyboard driver being used, or the keyboard layout itself.

it does look interesting....i hope someone is able to do something with it...

I wish someone would be able to look into this and let us know how to fix this issue. thx

i don't think its a big deal. just hold the down key.
i'm sure it will be fixed in the final release. you can't wait a few weeks?

SOLUTION
Here's the fix to the problem... attached to this post (contained inside a zip file)
The registry settings were exported using Resco Registry. You should have that installed to import the settings back to your APP UNLOCKED phone.
I'm pretty sure this problem will be fixed in the final version, as it was a terribly simple solution. Just a few key mappings that needed to be changed.
If you don't have Resco Registry on the smartphone, you can edit the registry with whatever editor you have, and just open up the .reg file in notepad, and make the entries match.
Note that the # key also acts as the wildcard key, so if you type in the first couple of the letters of the first name and then # and then the first couple of the last name, like JO#SMI, it will match John Smith as well. Also, if you are trying to search for something like Ralph using Ra, it will bring up all of the R's, since # also acts as the wildcard character.

Thanks a bunch. Worked like a charm.
Don't forget to reset your phone after you change the keys.

kmattoo said:
Thanks a bunch. Worked like a charm.
Don't forget to reset your phone after you change the keys.
Click to expand...
Click to collapse
Sorry, forgot to mention that part Kind of an important step.

Works like a charm, thanks!

Excellent, Merwin. Well done.

Agh, you beat me to it, I wanted to post the answer first!
Well good job! Not sure if this has been covered yet but you can get rid of the BETA text on the Today Screen by modifying the following registry key"
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"Today"="Beta"

afrim said:
Agh, you beat me to it, I wanted to post the answer first!
Well good job! Not sure if this has been covered yet but you can get rid of the BETA text on the Today Screen by modifying the following registry key"
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"Today"="Beta"
Click to expand...
Click to collapse
Yeah, I did that one a while ago... I routinely go through the entire registry when i get a new firmware

Hey - great post! Would you happen to know how to add an additional keyboard layout to WM?

I have not done it my self but it looks like you can easily add a new keymap. Look at the file \windows\eT9.Excalibur.0409.kmap.txt. You can't replace that file but you can copy it and save it with a new name. Then go into the registry and find references to that file then change them to match the new file name.
Be prepared to hard reset your device if you screw up, you may loose functionality of your keyboard.

Thanks so much! Made life much easier!

afrim said:
I have not done it my self but it looks like you can easily add a new keymap. Look at the file \windows\eT9.Excalibur.0409.kmap.txt. You can't replace that file but you can copy it and save it with a new name. Then go into the registry and find references to that file then change them to match the new file name.
Be prepared to hard reset your device if you screw up, you may loose functionality of your keyboard.
Click to expand...
Click to collapse
I've tried that with no luck. Looks like the keyboard driver needs to support additional languages...

merwin said:
Here's the fix to the problem... attached to this post (contained inside a zip file)
The registry settings were exported using Resco Registry. You should have that installed to import the settings back to your APP UNLOCKED phone.
I'm pretty sure this problem will be fixed in the final version, as it was a terribly simple solution. Just a few key mappings that needed to be changed.
If you don't have Resco Registry on the smartphone, you can edit the registry with whatever editor you have, and just open up the .reg file in notepad, and make the entries match.
Note that the # key also acts as the wildcard key, so if you type in the first couple of the letters of the first name and then # and then the first couple of the last name, like JO#SMI, it will match John Smith as well. Also, if you are trying to search for something like Ralph using Ra, it will bring up all of the R's, since # also acts as the wildcard character.
Click to expand...
Click to collapse
OK I have tried to import the registry and I have even tried to manually update the entries but they alwas go back to what they were before any help would be great. I do have Resco installed.
Thanks,
Steve

mario430 said:
OK I have tried to import the registry and I have even tried to manually update the entries but they alwas go back to what they were before any help would be great. I do have Resco installed.
Thanks,
Steve
Click to expand...
Click to collapse
Merwin: Thanks a lot for the fix!
Mario: I'd recommend using a free desktop app called Mobile Registry Editor: http://www.breaksoft.com/Blog/Utilities/2005/1/Mobile_Registry_Editor.aspx
This lets you edit your phone's registry using your desktop PC. Replace each of those keys (23, 2A, 31, 32, 33 .. 39) in HKLM\Security\Phone\PhoneKeyMatch\KeyboardMappings with the values found in the .reg file Merwin provided.

christophsky said:
Merwin: Thanks a lot for the fix!
Mario: I'd recommend using a free desktop app called Mobile Registry Editor: http://www.breaksoft.com/Blog/Utilities/2005/1/Mobile_Registry_Editor.aspx
This lets you edit your phone's registry using your desktop PC. Replace each of those keys (23, 2A, 31, 32, 33 .. 39) in HKLM\Security\Phone\PhoneKeyMatch\KeyboardMappings with the values found in the .reg file Merwin provided.
Click to expand...
Click to collapse
Using that other registry editor worked Thank you very much!!!!!

mario430 said:
Using that other registry editor worked Thank you very much!!!!!
Click to expand...
Click to collapse
Same here. Thanks

Does anyone else thing the matching is slower than in WM5?

[PRJ]Lighting PhoneCanvas

Stupid situation, when the skin eat so much phone memory.
Tried convert big *.bmp files from PhoneCanvas & PhoneCanvas_0409.
To png, gif, jpg... (size about 10 times smaller)
Funny, the dialpad is invisible, but it works
And the memory consumption smaller about 4M.
I'm not the programmer and can't find solution for this problem.
Just one thing - use compressed graphic files.
Is it possible, anybody knows?
And little trick for skin: reversed dialpad. (only)
More interesting for black diamond, I think

screenshots maybe?

wrong place
i think so this post belongs to Diamond Forum inspite of diamond rom development.
Request moderator is i m right then move it please.

simpleparab said:
i think so this post belongs to Diamond Forum inspite of diamond rom development.
Request moderator is i m right then move it please.
Click to expand...
Click to collapse
I'll leave it here for now, as it can be usefull in gaining some more space while cooking ROMs.
We'll see how it develops!

tnyynt said:
I'll leave it here for now, as it can be usefull in gaining some more space while cooking ROMs.
We'll see how it develops!
Click to expand...
Click to collapse
I think same
But I'm talking about OPERATIVE memory at first. Not only rom size.
Effect is similar for "HKLM\Security\Phone\Skin" Enable=0
And interesting, that another part of skin's images - "png".
So question - how to hack PhoneCanvas package for use "png" images for ALL.
About screenshots... hm, nothing special, just reversed:

mondilv said:
I think same
But I'm talking about OPERATIVE memory at first. Not only rom size.
Effect similar for "HKLM\Security\Phone\Skin" Enable=0
And interesting, that another part of skin's images - "png".
And question - how to hack PhoneCanvas package for use "png" images for ALL.
About screenshots... hm, nothing special, just reversed:
Click to expand...
Click to collapse
I know what you are talking about.
And here is your solution: save to png and rename to gif.

tnyynt said:
And here is your solution: save to png and rename to gif.
Click to expand...
Click to collapse
Wow, thanks!
Going to try.

Pity, the trick doesn't work
Same result - invisible dialpad.
May be any special parameters for png or gif?

Interesting idea!
We have to work for this...
I'm starting to work on it too!

For the image, it's work for me (dialpad is visible!)
With these images: http://rapidshare.com/files/137260968/Canvas_Remani__ZeuBug.zip.html
But no memory is saved..
I think we have to change all files: L_bg.bmp, EdBtnUp_Land.png, TkBtnUp_Land.png, etc...
So we know it's not these images who make problem...

ZeuBug said:
So we know it's not these images who make problem...
Click to expand...
Click to collapse
I only convert .bmp images (it's enough - png have compression already)
Memory consumption change from 49 to 42 %.
No bad, isn't it?
I took a look to the original skin now
It use gif/lzw, so...
May be this route? Change skin directly.
SYS\Phone_dpi_192_resh_480_resv_640

mondilv said:
I only convert .bmp images (it's enough - png have compression already)
Memory consumption change from 49 to 42 %.
No bad, isn't it?
I took a look to the original skin now
It use gif/lzw, so...
May be this route? Change skin directly.
SYS\Phone_dpi_192_resh_480_resv_640
Click to expand...
Click to collapse
I have not this difference of memory consumption. (no change!)
I have converted bmp to jpeg with a big compression setting.
I have missed something...

All *.bmp to compress in folders PACKAGE_Diamond_TaskManager & PACKAGE_Diamond_TaskManager_0409 -> about 4M economy.
But another way - make something to MS original skin.
I don't like it. Even not know why.
May be the buttons too small - will try edit a bit .
Gradient background take about 1M of memory - out.
Monocolor.
Work for evening

Sure, using jpg as bmp - visible dialpad.
But memory consumption didn't change.
If canvas invisible - economy of memory.
When bitmap loaded... Same result jpg & bmp.
So just rom size smaller. No bad too, but...
I'll use original skin, may bit changed.

mondilv said:
Sure, using jpg as bmp - visible dialpad.
But memory consumption didn't change.
Click to expand...
Click to collapse
It is only that I want...
I have disabled phonecanvas and maybe I will enable it when I will need video telephony! (one click on a reg file and soft reset! )
Maybe someone will find a solution in the future!
There is too much work for not a lot of things... I'm very happy with phonecanvas disabled (could be enabled!)

Resources in the PACKAGE_Diamond_PhoneCanvas\phcanOverbmp.dll looks nice (start dialpad for PIN enter, while use PhoneCanvas).
Will try to change standard MS bitmaps. Need be patience - long work
Or anybody can do it faster? Photoshop is not my favorite route.

I guess the effect of no difference in memory consumption despite JPG compression is that the application still needs the bitmaps in uncompressed format to display them...
So instead of making things better in terms of memory requirement that factor doesn't change at all - things get even worse since you add the overhead of JPEG decompression to the whole process of loading the dialpad...
This is just a theory however I'd love to see the memory consumption of the dialpad to decrease significantly!
Cheers,
Alex

dajudge01 said:
I guess the effect of no difference in memory consumption despite JPG compression is that the application still needs the bitmaps in uncompressed format to display them...
So instead of making things better in terms of memory requirement that factor doesn't change at all - things get even worse since you add the overhead of JPEG decompression to the whole process of loading the dialpad...
Click to expand...
Click to collapse
I think the same. So now want to try change "light" default MS phone skin.
(look the post upper)

Someone's done it:
http://forum.xda-developers.com/showpost.php?p=2365614&postcount=16
This takes around 5MB RAM and looks exactly the same as the 10MB version.

*nice* Looks pretty real and indeed seems to require less RAM!

Caller ID (7 digit) FINALLY FIXED

Hi All,
Quite a newbie and just rooted the Desire a couple of days ago, so bear with me…
Not sure if this is still a problem for many of us out there, but it’s been a problem for me for years, and I never found a solution to it (on the web or elsewhere), so I thought of sharing it.
For those of us who need “7 digit” (not 8 digits) Caller ID Matching, for both Phone and SMS/MMS, I think I have it working now
The problem comes from how your operator provides the caller id; in my country it’s +CCC x yyyyyy for SMS, and 0x yyyyyy for phone calls; CCC being the country code, in my case 961, but I’ve seen posts from other countries as well.
For Windows Mobile it was just modifying the registry, but for Android, I’ve seen many posts, blogs, etc. about libsqlite.so needing to be changed. I believe I found (actually stumbled across) a much simpler and more “correct” solution:
In the file “/system/build.prop” just add a line at the beginning “ro.phone.min_match=7”. Then use the normal recovery flash method and you should be good to go.
Update (thanks to luckyjay):
Or you can use Root Explorer, long press the file and open with text editor and just do it that way Reboot to apply changes
Click to expand...
Click to collapse
(I used ES File Explorer instead)​
I’ve tried it with several ROMs, including RCMixS and AceSMOD007, and it worked for me. (And WOW those are some really excellent ROMs)
Hope this helps, and let me know if I need to elaborate some more. (It's my first post after all)
!! MANY THANKS TO XDA, THE TUTORS, THE MODDERS AND EVERYBODY MAKING OUR PHONES BETTER THAN THEY ARE !!​

Not relevant for my country. But looks like a good catch. Well done!

Thanks jan, nice to see a reply
And I totally agree with you, but the "GENIUSES" over here decided on (and look at that):
+961 a 123456 or 0a 123456 (landlines)
+961 3 123456 or 03 123456 (original GSM lines)
+961 70 123456 or 70 123456 (newer GSM lines)
+961 71 123456 or 71 123456 (newer GSM lines)
… I mean people can’t get this straight how about phones (granted, some phones might be more “aware” than some people, but who am I to say)
The problem has been around for a long time (http://forum.xda-developers.com/showthread.php?t=606728 just one post of the MANY I’ve looked at), and we never got an answer.
I even emailed HTC for months on end about this, and never got a half-way decent reply! And I have been a loyal HTC customer for a long time: HTC P3300 (the first HTC, I think), Touch Diamond, TyTN, TyTN 2, Desire, HD2, Sensation
So I was really expecting a bit more from them, especially if the answer is as easy as I mentioned;
they’re statements “your s/n is for an HTC Hero” (hello! I'm sorry, the phone looks like the Desire, has the right software,firmware, th box says Desire, the phone says Desire etc.etc.)
or
“to edit the registry as it is considered illegal” (again hello! there is no registry in Android)
All this wasn’t really productive. One support tech (after being bounced back and forth) was actually trying to help, but eventually I just gave up.
After getting the HTC Sensation, I started rooting the Desire, and guess what, it just took the “ro.phone.min_match=7” to fix it. This could have been done even without rooting.
AND GUESS WHERE I GOT THE “ro.phone.min_match=7” FROM?? ... the HTC Sensation !!!!!

nkk71 said:
In the file “/system/build.prop” just add a line at the beginning “ro.phone.min_match=7”. Then use the normal recovery flash method and you should be good to go.
Click to expand...
Click to collapse
Or you can use Root Explorer, long press the file and open with text editor and just do it that way Reboot to apply changes

Thanks luckyjay, that works even easier. I'll update the post.

SO i See ur from lebanon and have the same problem i have and u found a solution ill give it a try and see if that works it only happens with me with phone numbers that start with 03 but all numbers that start with 70 or anything other than 03 works so ill check it and tell u if it works to me

well i gave u two thanks coz it worked my friend great job well done fixed my problem to i love the way u thought about it and at the end u did it amazing 5 starts for me

finally a solution... i am using prefixer to fix the prob but not very convenient! thx for the solution!

Thank you guys! for your comments & support !!
This thing has been driving me crazy for years, and Prefixer (nice BTW) or duplicating all phone numbers twice is just, is just INSANE for a "smartphone"
Yep, in Lebanon we have this problem, but I've seen many posts including Italy, Spain, and more countries, all of which have the same issue.
Anyway, glad I was able to contribute something, and appreciate your feedback.

I can't find
ro.phone.min_match
in build.prop of reflex gingerbread sense rom

yeahman45 said:
I can't find
ro.phone.min_match
in build.prop of reflex gingerbread sense rom
Click to expand...
Click to collapse
I would think you just need to add the line if it is not already there.

yeahman45 said:
I can't find
ro.phone.min_match
in build.prop of reflex gingerbread sense rom
Click to expand...
Click to collapse
It's usually not there ;most contries don't need it. Just add the line using ES File Explorer or similar to the build.prop (somewhere towards the beginning) "ro.phone.min_match=7" then save and reboot.
Should work then... let me know. (worked for me a lot on several MODS)

Great find.. I used to have that problem with my HTC Desire. But switching to CM7+ Handcent SMS was a solution to me in the past. But i think this is better

nkk71 said:
It's usually not there ;most contries don't need it. Just add the line using ES File Explorer or similar to the build.prop (somewhere towards the beginning) "ro.phone.min_match=7" then save and reboot.
Should work then... let me know. (worked for me a lot on several MODS)
Click to expand...
Click to collapse
ok will try it this evening thx

SMS was not really the big problem (for me), rather the Dialer: when you're in your home country the numbers arrive in local format (0a xxxxxx) but when you're roaming the phone calls arrive in international format (+CCC a xxxxxx). That's why I had to duplicate everything. And this for both incoming and outgoing calls.

yeahman45 said:
I can't find
ro.phone.min_match
in build.prop of reflex gingerbread sense rom
Click to expand...
Click to collapse
can confirm it works, just flashed Reflex_S_2.1.7
original build.prob:
Code:
ro.ril.oem.ecclist=911,112,999,110,191,113,117,15,1122,115,16,118
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.enable.sdr=0
........
this doesnt recognize Caller ID (7 digit)
changed build.prob using ES File Explorer (don't forget to activate root permission in ES File Explorer settings):
Code:
ro.phone.min_match=7
ro.ril.oem.ecclist=911,112,999,110,191,113,117,15,1122,115,16,118
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.enable.sdr=0
........
save & reboot.... now working Caller ID

ok added the line.. seems to be working!! will keep prefixer just in case and test a bit more!! man thx for the solution!!!! finally proper caller id recognition!!!

hey thank you , but its not working on my htc sensation revolution hd rom any ideas

hey
im lebanese as well
so i tried editing from rootexplorer but file didnt open, it says " you cannot edit this file system is read only "...
then tried it in S file explorer.. i edited it but i cant save after finishing
im using cyanogen mod 7 2.3.4
any help please ?

thanks inadvance