Hi - notice many having problems with country ID's and provider codes in XDA II images. The common complaints inexperienced people trying to use hex editors etc. I decided I would write a nice win32 GUI replacement for the er2003edit and the nbf2 tools to roll them into one easy to use application. I have also addressed the second prov/country in the ms.nbf so I think would be usefull to many less experienced users on the forum trying to flash new roms into there XDA II's
It so far will open and display the rom file as hex or ascii - and automatically works out the 'key' to decrypt the actual file (if its an nbf) etc - and all is funtional.
Have got it substantially finished - but am needing some feedback from other developers on a couple of technical issues.
Issue 1 is that I have noticed that the padding bytes in the older nk.nbf files are 00's - as opposed to FF's in newer nk's. Is this consistant across most images based on vintage etc (need this for auto calculate key).
Issue 2 is I have not yet worked out the checksum algo - which I am happy to experiment with - but I can assume seeing as both the apps I am trying to roll into one 'know' how to re-checksum the files etc - that someone here could explain to me how (if they see fit)
Not and issue - so Question 3 - are there any other functions that anyone here believes would be a good addition to this tool - speak up now (I am short of ideas here).
I will post app as soon as I egt the checksum working (which should be fairly soon if I can get the basic algo without too much work) as all the other bitsa and pieces are already functional.
cheers
^lave
Good Idea brother....
Waitng for it....
I have prgressed on application - have written the CRC algo now and working (better way to learn) - but am still lokking for some advice from the more knowledgable people on this board.
So far I can now re-checksum both nk and radio rom - but for some reason algo is failing on the ms_ roms - do I need to delve into structure a little further (ms being different to the rest as far as checksum goes) - or have I simply got a bug which only appears on ms roms (not too likely as working on multiple other roms).
Am able to decrypt the ms roms like the other but just not correctly CRC it - any clues anyone ????
cheers
^lave
See PM I sent you.
Sounds like a great project.
As I remember correctly, itsme also tried to calc CRC...not sure if he ever succeeded.
Personally, I can not help you.
@HappyGoat - yes thanks for the PM - that advice gave me some pointers and let me find a description of the algo which allowed me to write my existing work so far - I am perusing the source of xda2nbf to try to find answer for the ms_.nbf's as they definately seem to follow a slightly different format (ie I think either more header - or datablocks start at different point) with reguards the CRC therefore is different.
I did try to reply with thanks in PM but xda.developer was so slow at the time I gave up waiting for reply page after a few minutes. Thanks a lot for your input
cheers
^lave
OK - at last some progress - I finally worked out my bug crc'ing the ms_.nbf - was a silly assumtion that I had mada re the file sizes (ie radio 4MB + header) - (nk 32mb + header) - (ms 16mb + header - WRONG) - how about I check the filesizes - was missing 210 odd KB off the end in the crc - derrr.
Never mind - next question is an easy one and simply to prevent having to DL lots and lots of images - are all the MS_.nbf's a consistant size ??? - I have download 3 so far and they have been - but without download many many 40MB+ bundles - someone must know the answer to this one ????
cheers
^lave
PS what I am really looking for is a reliable method to identify one type of nbf from the next - trying to identify if filesize is the obvious answer.
Hi everyone - this is a totally useless version of app - from perspective has no write functionality yet and is very alpha. Idea is if anyone wans to have a play am interested in suscess or failure at opening different rom files. Is only design to handle XDAII images atm. Also interested in getting feedback on if the calculated checksum matches the one in the file. If anyone does get a chance to try out let me know.
cheers
^lave
More progress - a less useless version of the editor. Still treat with caution as is still beta and not a lot of feedback on compatibility wth a variety of NB10 roms yet.
Changelog:
several bugfixes
speed improvement in CRC
Write functionality
Plain to XOR and XOR to plain conversion
2nd details in ms_.nbf now working and editable
Allows changing the XOR key
If you save a file from the app with no extension or a non .nbf extension will save out plaintext rather than re-encrypting with the XOR key etc.
Again - if you download to play - consider giving some feedback on bug and features additions.
Cheers
^lave
good work!!!
Just an email to say good work as you don't seem to be getting much feedback for your program. The problem is that those who most need the program (noobs) are the least able to help, and those who can help don't need the program so are less inclined to help. There are some real whizzes lurking around here, some of them should be able to give you a bit more support.
Good Luck,
JJ
oh and the other thing is, if you want more coverage post this program as a news article on the main pageas it tends to stay up for a few weeks!
Thanks!!!!
Hi ^lave,
It's a very nice tool. Is this a alpha version, right? Will you are going to add more features, ie make change to the ROM content to prevent Authentication Check. etc.
I think you may need to change some label wording:
Provider ID ----> Country ID
Country ID ----> Language ID
Am I right?
Hello
Do you plan to adapt tools to 2020i (PH10C) Alpine ??
It will be greater to have tools to manage ROM on this PDA
Thank's for reply
Yes - is very early code still and I intend more features as I work things out. I only got my first PDA at Christmas just past (a bottom end iPaq - enough to catch the bug though)- and the O2 a few weeks ago so its still all new to me (yep I am a newbie).
Most of my more recent coding for past few years has been satellite related - so my terminology certainly has that bent at the moment and needs some serious work.
I certainly intend the app to be more universal as far as PDA models go - but of course that will rely somewhat on availability of hardware to test with (or alternatively people with other hardware to test for me).
Thanks for feedback and suggestions (I certainly need them at this stage of things).
cheers
^lave
Thank's
I can be tester for you on Qtek 2020i (PH10C) Alpine.
The extended ROM do work different than 9090, S100, 2020.
I have new registry entry and TRUEFFS_DOC that was for Extended ROM is now for Storage and EXTENDED ROM Profile is VDISK that use vdisk.dll.
Related
03/09/2004
ExtendedPhone has gone Cemercial.
You can download a trial version from the leading PPC software sites.
There is still an old free version on page 4 in this thread but keep in mind that this is an old version and there and will be are many improovements in the comercial one.
I have developed a T9 like dialer using .NETCF.
(That means you need Pocket 2003 ,or Pocket 2002 with .NETCF SDF installed)
The dialer works very nicely on my device.
I plan to extend the features but first i need some feedback from you people.
They both work fine on my SX56. (May be the XDA II needs the ARMV4.)
If you have other processors i'll upload the appropriate files by request.
Any feedback or suggestion is welcome.
P.S For now it works only on Latin Alphabet
Anyone?
Whats the matter people .
No one is coming in here.
May be this is not the right forum to release a new software?
I'm interested, but was waiting for someone else to try it first! (You could be anybody releasing a virus or something )
Have you mapped the green 'Answer' button to your program like PhonePlus2 does?
Not yet
The software is still in alpha stage.
I just need some feedback on what i did so far.
(search algorithm, performance bugs etc...)
PhonePlus2 is a commercial software and has been around for a while.
I don't have the time to work full time so go easy on me.
i installed it & it says could not read service provider, getservice bla bla, so looks like its not made for us, what could be the prob;em?
Xda I
Rom: 4.05
Radio 4.01
wm 2003
Tried it on my SPV M1000, WM 2003, ROM 1.72.
Works, but, as you said, it's definitely in its alpha phase. Here are my initial thoughts:
- not very responsive, slow.
- no possibility to scroll through contacts if more than 3 options are available.
- same very mediocre (I'd say ugly, but it's a matter of taste) design, from the interface to the buttons.
- Operater doesn't show up
- What's with the 'Cool Stuff'?
Anyway, thanks for your efforts. Will definitely stay tuned on the developments.
- not very responsive, slow.
Click to expand...
Click to collapse
is that not just the bane of .net ?
First of all thanks for the feedback.
i installed it & it says could not read service provider, getservice bla bla, so looks like its not made for us, what could be the prob;em?
Click to expand...
Click to collapse
I have uploaded a version without the "Service Provider" although it works on my sx56.
Works, but, as you said, it's definitely in its alpha phase. Here are my initial thoughts:
- not very responsive, slow.
- no possibility to scroll through contacts if more than 3 options are available.
- same very mediocre (I'd say ugly, but it's a matter of taste) design, from the interface to the buttons.
- Operater doesn't show up
- What's with the 'Cool Stuff'?
Click to expand...
Click to collapse
As for the design I'll support skins later.
If you have more than three contats starting with the same Letter then press another button and if still have more yet another,
I could add another one or two options for contacts but then you could say why 5 , why not more?
Cool stuff is just a logo.
As for the speed i'm trying to optimize and i think this version is a little less slow (you are right Rudegar) but untill the next release of .NET CF the one we have bundled with windows is no match for NATIVE code hence the slow startup.
There is a newer version (1.1BETA) on later post.
its working good you first need to work on the speed then on the interface & would be grate if you link it to the messages since we can use it as a keyboard layout also, sorry i don't have much time to write a full description but i will do that tomorrow
since you are a programmer why don't you develop a sw for sending scheduled sms's, i would defenatly be intrested & make no mistake such sw has never been made for PPC yet so make & sell it
new dialer
looks great but is very slow it would be great if it was faster also could you add on some thing to make it easier to send sms,s when you are busy.
well done keep up the good work
regards kevin :lol:
new dialer
looks great but is very slow it would be great if it was faster also could you add on some thing to make it easier to send sms,s when you are busy.
well done keep up the good work
regards kevin :lol:
Thanks guys .
I'm working on the speed problem but for now all solutions make the size a lot biger with not much improvement.
As i see there are two problems:
1 Loading time:Loading time is a bit of a problem in .NET (because of it's nature)
I'm trying different techniques but with no significant improvement.
So in the mean time just minimize the program and don't close it.
2 The first letter of the contact:
I'm working on that and i'm geting somewhere.
As for the SMS i'll have to resolve the speed problem first but i'm thinking about it.
Stay tuned
elir,
Found some issue.
- USSD code not supported. E.g. press **21*xxxxxxxxxx# to make call forwarding but it's not support in your software.
- Only 3 slots in the searching result. Maybe I have 10 contacts match the result but fail to show the 4th to 10th
- Unable to enter "+" to dial a IDD call.
Cheers,
Paul
Source code?
Elir, what about releasing this piece of nice work under any open source licence? I'm a developer in .NET for 4 years, so maybe I can help you.
Is it in C# or VB.NET?
Suggestion for faster searching:
What about creating tree from Contacts in memory on the start of program? If my assumption your dialer searches in Contacts directly is right...
Found some issue.
- USSD code not supported. E.g. press **21*xxxxxxxxxx# to make call forwarding but it's not support in your software.
- Only 3 slots in the searching result. Maybe I have 10 contacts match the result but fail to show the 4th to 10th
- Unable to enter "+" to dial a IDD call.
Click to expand...
Click to collapse
I'm working on international and ussd calls but as i said before want to resolve the speed issue first.
As for contacts slots , the whole point for an application like this is dialing one handed when bussy(driving etc...) , so adding slots will not help on that.
The only problem i see with this design is when you have more than three contacts with exactly the same first name.
This can be solved by adding search by last name but again i'm having speed problems as it is.
Elir, what about releasing this piece of nice work under any open source licence? I'm a developer in .NET for 4 years, so maybe I can help you.
Is it in C# or VB.NET?
Suggestion for faster searching:
What about creating tree from Contacts in memory on the start of program? If my assumption your dialer searches in Contacts directly is right...
Click to expand...
Click to collapse
I don't know yet about open source but i can tell you thats written in c# with a lot of native code (.NET CF lacks all the phone and outlook functions)
Thanks for the suggestion but If i copy the entire phonebook to memory at startup :
It will add another 2 seconds (and i have only 180 contacts) and it is slow as it is.
It will allocate a big chunk of memory and as you probably know we don't have a lot of it.
More than that if you add or change a contact you'll have to restart the program for it to appear.
How about bugs?
Nobody has reported any.
What do you not know about open source?
Or you mean, that you are thinking about releasing final version as commercial software? Com'on man...
In C#? Nice one brother...
Hm... In my QTek 2020 is about 80MB of free memory, so what is problem? :wink:
About refresh of tree: Isn't possible to add some event handler on changes at Contacts database?
Bugs will follow very soon...
Hm... In my QTek 2020 is about 80MB of free memory, so what is problem?
Click to expand...
Click to collapse
Most of us have XDA I so the memory problem is real.
About refresh of tree: Isn't possible to add some event handler on changes at Contacts database?
Click to expand...
Click to collapse
As far as i know (and i have done some research) that is not possible.
Re-write in in C++ (or even with MFC) for much better speed. .NET sucks ass on a PC let alone a poor ikkle PPC!
New version
Hi all!
New version 1.0.3
Fixes:
1 International dialing
2 Now you can use pound key just for #
3 Less slower (at least in my xda)
Added a module to send SMS .
A little clumsy but .... .
I didn't check the Sms module thoroughly but for some reason it doesn't dial international numbers ( i think is the "+")
PS The sequence of characters can be changed( for now i just went by the abc)
There is a newer version (1.1BETA) on later post.
SMS
I found out that numbers begining with "+" cannot be used to send SMS.
I'll fix this bug tomorrow so wait for the next version.
Any suggestions for my qwerty keyboard are welcome.
Has anyone noticed a speed increase?
is it true that xda2 has very strict restrictions on wat is allowed to be installed on it?
if so is it then possible to unlock that feature so i can write my own c programs for it?
maybe even write a new browser that has jvm say ?
Dave
No. You can write and install whatever you like. Where did you hear that rumour?
Surur
Dave,
So youre a programmer.
I am still looking for someone who can contribute the following software to this community:
Today pluging that makes ot possible to toggle Bluetooth & TomTom GPS being switched on / off. If youre interested, let me know, I can supply you with more exact specs. It seeems to me quite simple: just reading / updating some registry values.
programming
sure ill give it a go.
email me with specs and sourcecode
[email protected]
this would be my first xda2 programming experience tho, so it ight take me a little while to get fammiliar with xda2 programming first. im mostly a pc proammer good in c++ and opengl graphics, however im fast learner.
there are enoug forums for PPC programmers where u can read how to modify registry:
www.devbuzz.com
www.pocketpcdn.com
amd of course www.msdn.com
etc
flashing the phone rom what does that do for u practicaly?
flashing the phone rom what does that do for u practicaly?
flashing means to upgrade the s/w (firmware) that is stored in (flash) "rom".
Normally you only flash the device when
- You suffer from bugs in the old'rom
- The new rom has specific benefits
There are 3 types of rom on the device that can be flashed:
OS- the operating system
Phone (aka Radio)- the gsm/gprs radio functionality
ExtendedROM- add-on and customisation s/w (usually put together by the service operator)
Flashing the rom on the xda 1 since the developers got their hands on it is a whole new ball game, they discovered that the autoconfig program was taking up acres of space and wasnt really needed, there was also some unused space. They devised a way of writing complete programs to this space and my xda has numerous programs in rom that would normally be taking up precious ram when installed. These guys are brilliant in adding value and funcionality to a brilliant device.
Hi all,
As I tried to contact Niels Thomsen a couple times without answer and not being sure at all he is going to update his software and databases, finally I came back to program again.
Firstly I'll say the databases have the same origin, the files writen by George Spanellis that can be found in PocketGPS web site.
I took the full monty, joined in a single file and then started to delete those were repeated. So from a scratch of more than 2.5 millions postcodes the final database has 1.678.621 postcodes in a file of 40 Mb..
Then they were indexed and compressed (don't ask how) to get a final file of 13 Mb.
Personally I'm very happy with results. It's quick, no more than 1 second in a XDA II, to find the farest postcode in the database and the program that was made with NSBasic is 16 Kb.
I work as courier and testing it every day without problems with a lot of postcodes.
I don't want people selling my job in eBay taking benefits of my job, so I intend to sell it and to have registered customers. On return it will be updated on basis of customers corrections and adds and crossing my database with any other I can get.
Of course any comments or sugestions are very welcome.
At the moment I use the TTN SDK 2.0, but if there are enough customers I will buy the new 3.0 to get more interactions. For those that have already installed the TTNcontrol 3.0 in their PDA is not problem to have too the earlier control. I have myself. At the end of the day they are OCX controls that work or not if they are needed and they have similar but different names.
That's why I use the built-in keyboard instead to design a new one: To have more room in the screen for future new buttons. The second reason and no less important is to get a quick and small program.
I know you're tired reading my broken English so here are the CAB's you need. Copy them to your PDA and execute them. It will create a shortcut to the program.
This version has a expiration period of 15 days, I think is enough to try it and to get your comments. Thanks.
Hi all,
As some people reported to me some issues with the installation, possibly due to the way some PDA refer to the "Storage Card" I decided to separate the files to allow a "hand made" installation.
There is now 4 files to be downloaded. if some of you already have some of them skip it.
Data: http://homepage.ntlworld.com/j.adell/ukpc/data.zip
Library http://homepage.ntlworld.com/j.adell/ukpc/library.zip
Program http://homepage.ntlworld.com/j.adell/ukpc/program.zip
TTN library http://homepage.ntlworld.com/j.adell/ukpc/TTNControl.arm.CAB
Data contains the database
Library contains the needed OCX controls and runtimes
Program contains the program itself and a How2install.txt file with instructions
And finally the TTN library contains the TTN OCX controls. If you have already installed Checkpoint (last version) you don't need it.
I hope this workaround will eliminate the installation problems. The instructions file I think is enough clear, but if someone needs more help let me know. Also it will be a better way to introduce new releases or modifications just downloading one or two files instead the full lot.
BTW, the program has corrected a flickering effect when starting and a bug in the search process that affected postcodes with 6 digits or less.
Nomada
Hi all
A new release, now with a function to create Itineraries from Postcodes. And you don't need even to have TomTom running in your device. It works only for TTN 3.xx
You will see now two new buttons: "Send to itinerary" and "Finish itinerary"
After you get the coordinates for your 1st point (departure) tap on Send to itinerary. Use the second button for your last point.
The itinerary wil be saved as ukpc2ttn. So now you only need to open TTN, go to itinerary an open that file. It will show you the itinerary naming each point with the correspondent postcode and a flag with the position, so you can identify the point in the map. You will notice that the 1st point is not in the list. Don't worry, when you tap on "Plan" you will be asked to use that point as start.
To download just the program use the link: http://homepage.ntlworld.com/j.adell/ukpc/program.zip
Nomada
yes, but based on a flexible set of methods
-Using RIL (GSMTestMode)
-Using RIL_GetCellTower
-Using RIL Notifications
-Using RIL (fieldtest) -> reply structure has to be found
-Using offset method (few structures included)
-Using COM port
The project is based on:
-cellguardian.dll and cellguardian.xml : How to get CELLID on devices
-cell2latlon.dll and cellDb.xml : Calculate lat/lon using CELLID
-gsmcelluloz.exe : the main exe
-gsmcellulozCF.exe : the same, as PoC, in CF, but very simple
http://usuc.dyndns.org/tv/gsm/gsmcelluloz/
DEBUG mode creates a lot of log in \Temp
The device method configuration is in a file called "cellGuardian.xml"
Offset version works only with the "ALL" parameter (I don't know what defines the offset, which component version?)
Many things should be incomplete (like documentations )
Here is a google map (result from logging) made using a GSMTestode compatible device:
http://usuc.dyndns.org/tv/gsm/releve_poly.php
I'll write a quick documentation on how using cellguardian.dll (the brain from the cellid-getting), and cellguardian.xml.
I'm also working in antenna position interpolation but it's an harder process... (for now the cell2latlon works but uses a very simple barycentric algorithm)
Sample walk:
http://usuc.dyndns.org/tv/gsm/testParcours.php
Have fun, I hope to have some fieldtest compatible device log in order to decrypt the structure
If your device is still not working... Tell me!
The source will be released as soon as the modaco challenge will be finished (I hope to win a device with cellguardian.dll... or a sticker )
Did not work for me Tornado with Crossbow-Rom, i think you may ask maniac for the Offsets, he created CellProfileSwitcher, an very useful SmartPhoneTool with a huge list of compatible devices.
In Combination with your Tool it may be useful to create my own "CellMap", to see my Homezone or some other kind of zones, switched by CPS,yea.
But the Screenshots looks nice,...
Thank your for another nice way to waste my time with my lovely Phone,hehe...but i need the offsets...dont know how...
Have you tried "Find offset" in the 8FFB0000-8FFC0000 range?
8FDC0000-8FDD0000
8F1D0000-8F1E0000
8A3B0000-8A3C0000
8A4B0000-8A4C0000
8C0D0000-8C0E0000
Are other possible ranges.
The result will be contained in a file located on \Temp
Possible structures (if you define your configuration in cellguardian.xml)
TORNADO
TYPHOON
IPAQ
MPX220
WIZARD
Offset method will be activated once you'll have removed other options (COMPORT...) from the config file.
Remember that as long as I don't know what defines the offset, the only version that works is "ALL". This field will be used once I'll be quite sure the component version defines really the offset.
I hope to improve it, but also to let a chance to the user to configure it by himself.
Quick help page
I made a quick help page to help ppl finding the offset until I find some cleaner way to find it...
http://usuc.dyndns.org/tv/gsm/help/
After this, just modify \Program Files\cellguardian.xml
and replace
<device name="HTC Tornado">
<OEMID>Qtek 8310</OEMID>
<method type="RILHTC1"></method>
<method type="RILTOWER"></method>
<method type="COMPORT"><port>COM9:</port></method>
</device>
Click to expand...
Click to collapse
by
<device name="HTC Tornado">
<OEMID>Qtek 8310</OEMID>
<method type="OFFSET">
<offset version="ALL" structure="TORNADO">YOUROFFSET</offset>
</method>
</device>
Click to expand...
Click to collapse
Where YOUROFFSET is the offset you found (try the adresse ranges I suggested above)
Let me be your tester
Hello!
I have found your excellent project and I am going to test it and share with you results. My phone is smartphone - HTC S310 (know also as HTC Oxygene, SPV C100).
When I am launching the application I get error:
Cannot load \Program Files\GSMCelluloz\CellGuardian.dll:0x7e126
Is your app suitable for smartphones? I have downloaded the
GSMCelluloz_SP5_R.CAB.
Maybe I should use:
GSMCelluloz_WM5_R.CAB?
What offsets sould I put to test my phone and which method?
Best greetings and congratulations for your job!
RA
Solved
abramq said:
When I am launching the application I get error:
Cannot load \Program Files\GSMCelluloz\CellGuardian.dll:0x7e126
Click to expand...
Click to collapse
Hi again!
The problem was because I've installed app on card, not on device memory.
Cell searching works excellent, on my phone works GSMTestMode method (I am going to find out the differences between methods, but don't know where).
By the way - user interface for smartphone (non-touch display) looks like not fnished - 'backspace' keys doesn't work and it is difficult to leave edit mode too.
Will test it more and make some enhancement
Best greetings and please keep working
JA
P.S.
What Compact Framework needs the CellulozCF? I have the 2.0 and the app doesn't work (I get the unexpected error: Microsoft.AGI.CommonMISC.HandleAr() in System.Windows.Forms.Control._InitInstance.
I think the best cell id application from all times ever would be that which can change phone profile depending from location. I saw someone here is trying to do it, but will not be free, so no use. An app like that will eclipse all other... it will be like the next step in mobile evolution. Probably japanese already have it.
You are outDated...this idea is really old...lookat maniacs Homepage;
Maniacs SmartPhoneTools
...but for now not useable on devices without TiOmapProcessor
But PhoneAlarm by PocketMax supports different [email protected],too.. but cost money and hard to configure,no learningfunction,no neighbourcells and you have to add every Cell one by one...
but youre right,too; Actions by Locations are always missed in Apps with Notifications or ProfileChangingFunction.
Dear all,
I read the forum since some months now, and I thank you all for the awesome things I learned there, now I would like to know whether something I have in mind is achievable or not.
I own an Ubiquio 501, a very thin qwerty PDA (with touchscreen, wifi and all) which works very well. However:
-With the AKU 3.3 ROM (released around february) it suffered from very bad graphic/video performance, but everything else was working pretty well.
-With the last WM6 upgrade (released in august) the maker fixed the graphic issue, but for me the keyboard behavior is nothing but unacceptable. It seems like I am the only one having problems with the keyboard, however a downgrade (to AKU 3.3) fix the keyboard bit, so I guess the problem is not in the hardware.
What I would like to achieve is to put the keyboard drivers in the WM6 ROM, what do you think, is this feasible? I was able to unpack the ROMs with the kitchen tools, but am not sure of which module the actual keyboard driver is, the relevant files and dirs (find dump/ -iname "*key*") in the
AKU3.3 ROM :
Code:
./KeyBDState_service.dll
./KeyBDState_service.dll/KeyBDState_service.dll
./KeyIcon.dll
./KeyIcon.dll/KeyIcon.dll
./keypad.dll
./keypad.dll/keypad.dll
./keysifter.dll
./keysifter.dll/keysifter.dll
./devauthkey.dat
and in the WM6 ROM:
Code:
./KeyBDState_service.dll
./KeyBDState_service.dll/KeyBDState_service.dll
---> same file as in WM5 (md5sum match)
./KeyIcon.dll
./KeyIcon.dll/KeyIcon.dll
--> different
./keypad.dll
./keypad.dll/keypad.dll
-->different
./keysifter.dll
./keysifter.dll/keysifter.dll
--> different
./devauthkey.dat
-->same file as in WM5 (but I guess it doesn't have anything to do with the keyboard!
Should I look for other files? (I think so
Thank you all in advance!
Regards,
DAniele
I have had the 503g for a few weeks now and love it. If there is anything I can help you with please let me know.
Hi maevro, thanks for joining
I just found (using a task manager) that stopping the "key sifter" service yields to a complete stop of the hardware keyboard (only things that keep working are the keyboard backlight and some "special" buttons: the comm-manager activator, the mode switcher (alpha, num), the shift key).
However, overwriting the keysifter.dll file with the wm5 version I was only able to reach a non-working state (the service does not start automatically and will refuse to start manually).
So, keysifter.dll is definitely (one) culprit, but additional testing may be needed to see its dependencies (I guess) in order to replace it with a (better) working version.
Regards,
DAniele
--
gdaniele said:
Hi maevro, thanks for joining
I just found (using a task manager) that stopping the "key sifter" service yields to a complete stop of the hardware keyboard (only things that keep working are the keyboard backlight and some "special" buttons: the comm-manager activator, the mode switcher (alpha, num), the shift key).
However, overwriting the keysifter.dll file with the wm5 version I was only able to reach a non-working state (the service does not start automatically and will refuse to start manually).
So, keysifter.dll is definitely (one) culprit, but additional testing may be needed to see its dependencies (I guess) in order to replace it with a (better) working version.
Regards,
DAniele
--
Click to expand...
Click to collapse
Is the graphicproblem totally gone, so you can play games and watch movies without any problems?
Also, do you have any problems with network on this device?
Keep us updated if you find any solution to the keyboard-delay problem!
Thanks
Well, I kind of sorted it out. The solution ain't optimal, but at last I can write my sms & mails as I was used to.
After many tries and file swap between wm5 and wm6 rom dump, I stopped the keyBDState service and... kaboom, everything worked as expected Yes, it was _that_ simple
Please note that there are still some issues (shift + arrow keys does not highlight) but I made this mod a few days ago and have noted no instability whatsoever.
The only thing that ceased to work after the mod is that I can no longer compose phone numbers from today screen (but in the phone app everything works, so I am not that disappointed).
If you want to try it by yourself, I can only advice for a prior full backup, and can take no responsibility for whatever damage may occur to your data, phone, sim card... blah blah blah ...
So long for my first post, although I really would like to investigate the thing a little bit further (and get highlighting back as it was in wm5).
To answer uggugg, I only tried a (mandatory ) Zoolander sample and it worked well (re-encoded to fit screen size, 20 fps, don't remember the bitrate, should check) as for the games... I really ain't into gaming (not on my phone, at least) so I'm sorry I couldn't tell you anything.
Regards,
DAniele
--