I've read a few posts regarding the device ID changing from OS to OS flashes. I've been using Black from the beginning and it didn't seem to change the Device ID. Slingmedia and other programs installed OK.
I recently flashed LVSW ROM and it changed the ID. I had to get new registration codes from my programs because of this. I am afraid to flash new ROMS often now because of changing the device ID. These companies probably won't continue to change the codes for us forever.
I thought that the device ID is static based on the hardware itself. How can this change with a new OS? Can it be changed back without flashing another ROM? Can it be prevented from changing with a new flash?
The device ID is generated dynamicly after every hardreset.
http://blogs.msdn.com/jasonlan/arch...card-wipe-and-encryption-what-s-the-deal.aspx
Very interesting, but I wonder if other apps are using ( and used in WM5 ) the "same" ID ... In any case, there's gotta be a way to see and change it one way or another. "The doors are everywhere, you just have to know how to open them"
doedoe said:
The device ID is generated dynamicly after every hardreset.
http://blogs.msdn.com/jasonlan/arch...card-wipe-and-encryption-what-s-the-deal.aspx
Click to expand...
Click to collapse
I don't believe this at all. I think it's more likely the device is taking a one-way hash to the manually input device ID (see below) and SIM ID, plus some randomizer to create a unique identifier for the storage card encryption. My guess is this process runs when you check the box to encrypt the card. If anyone knows this to be different, please share how to locate the unique device ID.
Some ROMs has the Device ID (Settings -> System -> About -> Device ID) pre-populated with things like TyTn, or other text. I think the differences in some of the earlier ROMs was screwing everybody up because close attention wasn't paid to this. The first thing I've done each time I re-flash is change this to WM_[my-windows-logon], because when the device syncs with Activesync the first time, it goes with some combination of what's there plus your logon. Anyway, I've manually set this to WM_[myname] (yes, this is an example, 'myname' is not my logon) before syncing with Activesync. I've done this on Black 2.5, 3.0.1, one of LVSW's ROMs, and Custel's 2.5. I have yet to need a new sling code or tomtom code.
Maybe I didn't do such a great job of explaining this, but all you have to do is look at Activesync and see what it thinks your device ID is. If you've registered software, pay attention to this name and simply enter it after a re-flash. Multiple flashes means you need to delete the device partnership in Activesync each time, and when you manually code it to WM_(yournamehere) or whatever you have now, I bet you have no problem with sling or tomtom.
If anyone can confirm this, we should place it in the wiki.
Device ID
The device ID does not change after every hard reset, however with certain roms it can change the ID, at this time there is no fix for the changing ID problem. I also have a few programs that are teathered to the device ID instead of the IMEI.
My advice is, Keep track of which roms you load and on what dates you load them. Do like I do, before you install a new rom, run a Sprite backup (or whatever program u use) on your device (do a full, including storage card) backup. Then if your ID changes, you can reinstall the rom that worked with all your apps and run the backup app, I have had to do this several times and all of my apps are still working and registered.
You just have to decide what is more important, the rom, the working (registered) app, or continuing to ask for a replacement registration key.
100Tbps said:
Maybe I didn't do such a great job of explaining this, but all you have to do is look at Activesync and see what it thinks your device ID is. If you've registered software, pay attention to this name and simply enter it after a re-flash. Multiple flashes means you need to delete the device partnership in Activesync each time, and when you manually code it to WM_(yournamehere) or whatever you have now, I bet you have no problem with sling or tomtom.
Click to expand...
Click to collapse
It may work for those apps, but it isn't that easy for Infogation Odyssey (TomTom competitor), to name one. Has to be some deeper hashing algorithim in the ROM or whatnot. It changed around the time the 17xxx builds started appearing and I've always wondered if it could have a "dogfood" link.
Here are some MSDN articles on the issue:
http://blogs.msdn.com/jehance/archive/2004/07/12/181116.aspx
http://blogs.msdn.com/jehance/archive/2004/07/12/181067.aspx
http://blogs.msdn.com/windowsmobile/archive/2006/01/09/510997.aspx
We need a good programmer to figure this out
My Experiences
I have suffered from this very problem. My device ID stayed the dame from WM5, to XDA 0.1 > XDA 0.2 > Black 2.0 > Black 2.5
I then went to Black 3.0.1 and my device id changed. Infact, after getting a new licence string, the program that needed it (PocketHeroes) would bomb out whenever it tried to verify the new licence. This problem persisted in LVSW 3.3.
Now I am on Black 3.5 and my device id has reverted. My origional licence works fine and the app is 100% stable. My only guess is that a certain build of the kernal had a flaw with the deviceid and this has been naturally replaced by a newer version.
Device ID
The device ID (name) that is used for activesync is not the same as the device ID used for certain programs. The device ID that we are refereing to is a 12 digit code that looks like XXXX-XXXX-XXXX where X = the ID for each device.
lewnetoons said:
The device ID (name) that is used for activesync is not the same as the device ID used for certain programs. The device ID that we are refereing to is a 12 digit code that looks like XXXX-XXXX-XXXX where X = the ID for each device.
Click to expand...
Click to collapse
How can I see this 12 digit code?
Anybody going to write a program to change this? if legal!
lewnetoons said:
...clip...
My advice is, Keep track of which roms you load and on what dates you load them. Do like I do, before you install a new rom, run a Sprite backup (or whatever program u use) on your device (do a full, including storage card) backup. Then if your ID changes, you can reinstall the rom that worked with all your apps and run the backup app, I have had to do this several times and all of my apps are still working and registered.
You just have to decide what is more important, the rom, the working (registered) app, or continuing to ask for a replacement registration key.
Click to expand...
Click to collapse
I say, that is a great suggestion. :thumbsup
What's happening here is the platform ID portion of the Device ID is changing. This is because many roms here (including mine) use IMGFS components from the Universal. When this occurs, the platform ID portion of the Device ID changes from Hermes to Universal as well.
It appears that even the Official WM6 released today does indeed change the Device ID for instance with Tomtom Traffic.
I am having to take this original wm6 off now and stick with a development version of wm6 until i can convince tomtom to change my device id which they wont do. They are so useless....
just so other users are aware.
Related
Does anyone know if you can take a piece of software that you have purchased in CAB format, with a Licence Key and change it into a package?
Since the software isn't OEM is it still the same method to create a package?
Any Takers?
This cant be to much of a hard question!!! can anyone answer? please
Tried it with Phone Alarm. sort of worked at the second attempt. But not quite. If I spent more time on it I reckon I could have got it to work but just don't have the time.
crazyC said:
Tried it with Phone Alarm. sort of worked at the second attempt. But not quite. If I spent more time on it I reckon I could have got it to work but just don't have the time.
Click to expand...
Click to collapse
but you can actually do it? what do you do about the activation codes etc?
The code is probably just stored in the registry or a config file after you enter it, in which case just make an RGU in the package putting the right data into the right place.
Some software might encrypt the code.. but even then usually putting the right encrypted string in the right place will work.. You may have to have the owner information set exactly the same each time (as this may be hashed into the generated key) but this isnt a problem as you can set the owner information in the RGU as well.
If you get a program where you cannot track the installation to see what happens when entering serials etc.. try SKTracker.. you can use it to watch the ppc for changes to files, databases and registry and dump those changes for analysis... so you install it.. make a reference dump.. then install/register the app.. then dump again.. then compare to see what has changed.
Some apps it wont work with of course.. but i'd imagine for most it will be possible yes. The worst that happens is you have the app installed in trial mode.. and a text file burned to the ROM with the serials you have bought in it to re-register it when needed after a hard reset.
Yeah - SK tracker is fantastic. Generally it just involves exporting a reg key from your PPC and then putting it into the cab/package along with your owner name (in some cases).
All my licensed software has been set to install via cabs including the keys. Not found any that cannot be done this way.
Problems arise with more complicated installs that involve interfacing with the system. Just using the normal conversion process with the PA cab did not work, needed to run SK tracker and fix a load more reg entries that were changed by the instll prcess. Improved it but still had issues with no sounds etc. I must have missed something, and have temporarily given up. The cab only takes a minute to install anyway.
On CodePlex I have published my app for tracking working time.
It is based on the SenseUI SDK.
SenseTimeTracker
For furter feature development either this thread can be used or the discussions in CodePlex.
After getting some feedback according to installation problems, I figured out, that the deployed .cab file does not contain the SQL Server Compact 3.5.
This has to be installed manually until I do not provide a msi-setup.
Explanation on how to install the .NET Compact Framwork 3.5 and/or the SQL Server Compact 3.5 has been added on the CodePlex page.
Version history:
Version 1.3
* Length checking of input fields
* Bug fixed with reports when first time card has date in january
* Issue with localization fixed
* Category edit form localized
* Creating new category did throw an excexption
* Default category is hidden in category list
Version 1.2
* cab file now creates a shortcut
* new version detection added
Version 1.1
* Initial release after UI redesign
Installation Procedure
Hi, Could you explain the Installation procedure, other than download and install is there any other additional requirement to get this program up and running?
Thanks
Download the cab file, copy to your mobile device and run it from there.
This shall install SenseTimeTracker on you mobile device.
Let me know if it doesn't, since it is my first publishing. I only installed it on my device or the emulator.
Test
OK! I downloaded you app, installed and found the following problem, btw I am on a Blackstone using G10 Dusk Ultimate 2 v 8.31
1) There is no icon present for your apps in the programs menu.
I went to programs found the your app and try starting it from there, I got the following error
Ok, SQL server was not deployed. I will try to fix this and provide an update.
On my devices there has been SQLCE installed, so I didn't recognize it.
Thanks for the hint.
wesch00 said:
Ok, SQL server was not deployed. I will try to fix this and provide an update.
On my devices there has been SQLCE installed, so I didn't recognize it.
Thanks for the hint.
Click to expand...
Click to collapse
No problem was glad to help, I was looking for a program like that for sometime now , I will test again when you update
You have to install the SQL Server Compact manually, sorry.
See my explanation in CodePlex.
zjxpot said:
OK! I downloaded you app, installed and found the following problem, btw I am on a Blackstone using G10 Dusk Ultimate 2 v 8.31
1) There is no icon present for your apps in the programs menu.
I went to programs found the your app and try starting it from there, I got the following error
Click to expand...
Click to collapse
wesch00 said:
You have to install the SQL Server Compact manually, sorry.
See my explanation in CodePlex.
Click to expand...
Click to collapse
Hi I downloaded and follow your instructions regarding the installation process and got the top half of the error I posted above when I tried starting the apps also no icon was installed in programs menu I tried it on G10 Ultimate 2 v8.40 release today
The icon issue I couldn't check yesterday, will do that asap. Did a lot of research how to deploy SQL Server Compact.
But could you run the app?
wesch00 said:
The icon issue I couldn't check yesterday, will do that asap. Did a lot of research how to deploy SQL Server Compact.
But could you run the app?
Click to expand...
Click to collapse
No, its not running, when I try runnunig it I get the same error box but only the top half of the message the bottom half is gone.
That makes no sense since allways an explanation of the exception is displayed.
If you installed the SQL Server Compact, can you try to delete the whole SenseTimeTracker folder in the program as well as in the documents directory (if there is one) and reinstall the cab again.
I checked this yesterday on a clean emulator and it worked. So without any further hints I cannot guess the problem.
Are you familar with developing smart device aps. Then I can send you the project for visual studio and you can try to deploy it from within VS. That shall work. Let me know.
I suggest to contact me via pm, I will help you to fix your problem.
wesch00 said:
That makes no sense since allways an explanation of the exception is displayed.
If you installed the SQL Server Compact, can you try to delete the whole SenseTimeTracker folder in the program as well as in the documents directory (if there is one) and reinstall the cab again.
I checked this yesterday on a clean emulator and it worked. So without any further hints I cannot guess the problem.
Are you familar with developing smart device aps. Then I can send you the project for visual studio and you can try to deploy it from within VS. That shall work. Let me know.
I suggest to contact me via pm, I will help you to fix your problem.
Click to expand...
Click to collapse
Hi, I flashed an orginal HD rom, installed net, sql and then your apps went to programs and started timetracker and it worked, I reflashed a cooked rom did the installation and it also worked I tried entering some information I got some error that require me to restart timetracker one of the error is attached, I will flash G10 rom again as this is my rom of choice and I will let you know how that went
I must say thanks for what I have seen so far if I get it working on G10 rom I will do some more in dept testing.
Thanks again for sharing
Ok, I see, it has nothing to do with your ROM.
I think there is a bug with the categories which only occurs on an empty/fresh database. On my tests I've had everytome a filled one, since I implemented category support later on.
I had some minutes to try it on a fresh installtion. Unfortunatly I cannot reproduce this bug. Can you plz provide more info, what in which order you entered for getting this error. I first created a user which is mandatory. Then created a client, then a project for that client and then a task for that project. Now entering a timecard did work, since the default category ("unknown") was used. The error you've got is a key violation between task and category. This should not occour, but I need to know in what order you entered the data.
wesch00 said:
Ok, I see, it has nothing to do with your ROM.
I think there is a bug with the categories which only occurs on an empty/fresh database. On my tests I've had everytome a filled one, since I implemented category support later on.
I had some minutes to try it on a fresh installtion. Unfortunatly I cannot reproduce this bug. Can you plz provide more info, what in which order you entered for getting this error. I first created a user which is mandatory. Then created a client, then a project for that client and then a task for that project. Now entering a timecard did work, since the default category ("unknown") was used. The error you've got is a key violation between task and category. This should not occour, but I need to know in what order you entered the data.
Click to expand...
Click to collapse
Sorry for not replying sooner, I was trying some other roms but no luck getting this app to work on those other roms that I flash, for me its only working on stock and Energy GTX I am presently downloading a 6.5 rom to test all others has been 6.5.x.
I have been able to reproduce the error again and again, try this
Go to category select new and create a new category everything should be ok, create another one and it should crash, also I am unable to edit the category "unknown"
More Crashes
Hi, I did some more test and I got more errors I have attach one picture, let me try to explain
1) If I try to copy the TimCard it crashes
2) TaskName is to long it crahes
I got a couple more crashes but I forgot where in the apps they occour however it seems that is not handling user input error well maybe a dialog box should appear and tell the user that the TaskName is to long or something like that I also think you should try and test if all but most of the option like copy, remove, edit, maybe it my rom related but you could still check just to be sure.
Thx again for the responses.
Couls get it allready run with the other ROMs? I have no opinion about these ROMs. I do not use any special functiuons, it is only .Net-code. The only explanation I have would be that there are problems with drawing. Bit this is done by the SenseUI framework which I cannot modify or debug.
Now to the issues.
The Category issue I could allready fix for me, will update it soon. Dont use categores for the mean while, use only "Unknow". You can change it later when it works. The "Unknow" category should not be editable, I will hide it in the next release.
The issue with the task names beeing too long is a bit more difficult to fix, I'll try to find a solution (need a common one since this will be happen with all inputs).
For the issue with copying a time card, I need a screendum of the error. I use copying of time cards allmost every day and never had problems. So it should be some special in your entries. If I have the error output, I hope to have an idea.
wesch00 said:
Thx again for the responses.
Couls get it allready run with the other ROMs? I have no opinion about these ROMs. I do not use any special functiuons, it is only .Net-code. The only explanation I have would be that there are problems with drawing. Bit this is done by the SenseUI framework which I cannot modify or debug.
Now to the issues.
The Category issue I could allready fix for me, will update it soon. Dont use categores for the mean while, use only "Unknow". You can change it later when it works. The "Unknow" category should not be editable, I will hide it in the next release.
The issue with the task names beeing too long is a bit more difficult to fix, I'll try to find a solution (need a common one since this will be happen with all inputs).
For the issue with copying a time card, I need a screendum of the error. I use copying of time cards allmost every day and never had problems. So it should be some special in your entries. If I have the error output, I hope to have an idea.
Click to expand...
Click to collapse
Hi, I have flashed back to my rom of choice as I need it for work, I also used an apps name Pocket Time, I was hoping to get your working as your is mor mordern and has more options, anyway I will be able to test your program again this weekend and I its working for me I will change my rom and start using your apps I like it.
I have attach the detail section or the Task Name error for you to look at also I have attach the error and the error detail section of G10 rom maybe from those pictures you can figrue why it dosent start
The last five is from G10
Thanks
Thx for the dumps.
As I allready wrote, the problem with the length of the description is a common problem. I did know, that it wasn't checked. I will release a new version today (1.3) which supports those checks.
The other problem has something to do with the serialisation/deserialisation of the user settings. These are stored in an XML-file in the application directory. And it seems, that the existing date time format has problems.
Is the language of your G10 ROM a different than the default ROM? I assume, you have created the XML the first time with on ROM and now trying to read it with another on. And the DateTime format of both are different and cannot be parsed.
Try to delete the xml-file in the app directory and start the app again with the G10 ROM. Let me know, if this solved the problem. May be I can then find a solution therefor. If you delete the xml-File, you will be asked for selecting a user. Select you previous eneterd user. If you navigate away from the user panel, you will be asked for the password you entered previously.
If you not allready entered sensitive data, you can send my the database (sdf-file) and the xml-file. Then I can try to debug it. I've had a lokk into the xml-file and saw there are only two time fields where the time is entered as 8:00:00 and 17:00:00. If this format is not valid on your ROM due to another culture, then this may cause the error you posted. What is the usual time format on your country?
Then I have a question according this ROM. The error occurs in Deserialize while reading a DateTime value. I have a try-parse in the deserializing section. So no exception should be thrown by the app. If there is an error in the XML file, defaults are used. I did try this on my device and ti worked that way. So I really do not know, why the exception is thrown. Ist there any special in your ROM handling exceptions?
wesch00 said:
Thx for the dumps.
As I allready wrote, the problem with the length of the description is a common problem. I did know, that it wasn't checked. I will release a new version today (1.3) which supports those checks.
The other problem has something to do with the serialisation/deserialisation of the user settings. These are stored in an XML-file in the application directory. And it seems, that the existing date time format has problems.
Is the language of your G10 ROM a different than the default ROM? I assume, you have created the XML the first time with on ROM and now trying to read it with another on. And the DateTime format of both are different and cannot be parsed.
Try to delete the xml-file in the app directory and start the app again with the G10 ROM. Let me know, if this solved the problem. May be I can then find a solution therefor. If you delete the xml-File, you will be asked for selecting a user. Select you previous eneterd user. If you navigate away from the user panel, you will be asked for the password you entered previously.
If you not allready entered sensitive data, you can send my the database (sdf-file) and the xml-file. Then I can try to debug it. I've had a lokk into the xml-file and saw there are only two time fields where the time is entered as 8:00:00 and 17:00:00. If this format is not valid on your ROM due to another culture, then this may cause the error you posted. What is the usual time format on your country?
Then I have a question according this ROM. The error occurs in Deserialize while reading a DateTime value. I have a try-parse in the deserializing section. So no exception should be thrown by the app. If there is an error in the XML file, defaults are used. I did try this on my device and ti worked that way. So I really do not know, why the exception is thrown. Ist there any special in your ROM handling exceptions?
Click to expand...
Click to collapse
Hi, I am using the original G10 WWE Ultimate 2 v8.31 rom out of the box in fact all the ROM I have tried this app on has been out of the box, will try flashing and trying your app again this weekend.
Are you using your app on an original stock rom or a cooked rom?
I'm using the app on the updated but original HTC ROM. But it did also work on the nonupdated.
The description of you exception shows me, that the problem has something to do with the localized date time format. What localizaion do you use. And I think you've got it allready running with another ROM. What localization do you have there?
What I totally do not understand, in my opinion there should not be thrown an exception, since serialization is done within a try/catch block. If there is an deserialization error, it should be catched and defaults should be used, which I have testet.
Hi all - want to know what the status is on a hspl for wp7 and if can help and wondering how live pvk and id goes to phone in hd2-wp7 situation where no real device provisioning partition exists?!?!?!??! This leads me to think that maybe:
Perhaps with Cotulla's partition layout over 4 seperate nand areas it would be an option to modify this and his wp7 spl because the activation thing happened AFTER (live activation hack around etc) he had finished leo70 release and then..........
-whilst jtag/usb or eth/debug happening- (obviously Da_G etc thought of this b4- im just extrapolating further on this now live done after dft released- let me know if way off)- to take a HTC HD2 (LEO70) that HAS BEEN ACTIVATED ON LIVE and see where/how/when/with/which partitions, filesys, regkeys, etc, have pvk for live or the ffu and then insert a test cert like ur own xbmod/chevron. or whatever is in sdk for 7 or ce. and then utilize this to diff and comp. I dont see why not. Then .ffu then self signature.
If anyone is looking at doing this and needs hardware or I can help let me know thanks. Also:
Anyway to DUMP the newly-activated after-hack after-key after-ms-call hd2 wp7 contents completely? Any news on this unknown filesystem and sd jbod with nand? If a way to extract device provisioning partition etc. Not interested so much in live but more HSPL-for-WP7 creation to allow custom roms. Can not seem to find much on this. Anyone got ideas on own signature or other method using pre-existing leo70 nand parts as workaround maybe?
For the record - I have used a singled live key from Microsoft activation phone call more than 4 times on 2 devices and it works fine over and over: you have to consider fact that if vendor or product id was misflashed at factory onto DPP then every hardreset would not wipe this (unsure)? causing you to call microsoft again and ask for another key? eitherway:
does ne1 know what the key over the phone from microsoft is actual doing? is this key taken with say imei or serial of phone and maybe your @live.com unique GUID and seeded or used with hash or some algorithm to produce a pvk for device provisioning partition? or it simply override and enable live? are there only one type of activation key over phone? seems there could be ones maybe based on your live address+guid and ones that completely allow model and oem identification to be cleanly changed?
I am just theorizing here from what I have been reading. Finally: Is it true that uk/etc MS stopped giving out keys and referring ppl to HTC etc for
live? Any press release or official reaction?
Noticed leaked documents in another thread here marked Microsoft Confidential!
This app is designed so that you can keep track of any medications you take on a regular basis.
When you last ordered a particular drug, how many you currently have to hand, which surgery the repeat was requested from and which pharmacy filled the prescription.
It is designed to be used for multiple patients, surgeries, pharmacies and doctors.
It was initially an Access database but I thought that migrating it to my PPC was a challenge I might be able to complete.
There will also be the ability to log doctor's appointments as well, hopefully.
All data is currently stored in an SQL-CE database.
For reasons I am currently trying to solve, when you open any secondary form with a data table and then return to the main menu you are unable to go back into any other form again.
Changed to a tabbed layout, screen shots attached.
09/02/2011
New version attached with new format SQLCE.
17-Mar-2011
Latest version attached
All data entry and editing working - I hope.
08-Apr-2011
Latest version, autoscroll and popup SIP.
Possible dependant files.
I am coding for CF2.
[Reserved] - For Comments
deedee said:
[PROJ] Prescription Medicines Manager
...medications you take on a regular basis.
When you last ordered a particular drug, how many you currently have to hand, which surgery the repeat was requested from and which pharmacy filled the prescription...
Click to expand...
Click to collapse
Thank you!
These records can be life-saving if you have them with you at the right time. I have tried many systems of keeping track, but rarely managed to have anywhere close to this much information on hand.
I have not had time to try it out properly so I do not yet have any comments or suggestions. For now, I just wanted to say THANKS!
Glad it's going to be if use to someone.
Hopefully by the end of tonight I will have a new version up with the ability to add records to each of the tables. No interlinking yet and at the moment editing is also broken but I am getting there.
deedee said:
Glad it's going to be if use to someone.
Hopefully by the end of tonight I will have a new version up with the ability to add records to each of the tables. No interlinking yet and at the moment editing is also broken but I am getting there.
Click to expand...
Click to collapse
Don't feel rushed on my account. It's great that you're interested in this project, whenever you finish will be soon enough.
Meanwhile, I'll play with it and start planning how to "feed" it my information.
Have you considered some sort of encryption? It just occurred to me that it will hold a lot of very personal information.
Again, thank you.
deedee said:
...at the moment editing is also broken...
Click to expand...
Click to collapse
I know next to nothing about programming, but would the PC editor you wrote for the W Watcher calc work for this project? That might make it easier for the user to input the information AND save you some programming...
(BTW: I was very impressed with how quickly you developed those applications! Very usable and no charge for fast delivery!)
Jesterfell said:
I know next to nothing about programming, but would the PC editor you wrote for the W Watcher calc work for this project? That might make it easier for the user to input the information AND save you some programming...
(BTW: I was very impressed with how quickly you developed those applications! Very usable and no charge for fast delivery!)
Click to expand...
Click to collapse
Unfortunately the WW editor is designed for an XML file and this app keeps everything in an SQLCE database. I am trying to find a nice, useable and, more importantly, free desktop app to edit these files and am trying a couple out at present.
While a purely PC based editor would be easier from a WM coding point it would stop the app being completely mobile and standalone.
New version added to post 1.
You can now add records.
For desktop managemnent try
SQLCE Desktop Manager
FlyHoward SDF viewer
Neither of these seem to be free though the second one does have a 14 day trial.
deedee said:
... While a purely PC based editor would be easier from a WM coding point it would stop the app being completely mobile and standalone...
Click to expand...
Click to collapse
Of course!
Sorry, I got tunnel vision and forgot the project's purpose.
What am I missing?
I have been unable to run Prescription Medicines Manager on my HTC 8925 (Kaiser) with WM 6.5.x.
When I run the EXE all that happens is that the WM wait animation plays indefinitely until I switch to another application.
Since I play with this phone a lot, I hard reset it to clear any lingering results of my modding (it's a spare phone, so no great loss). Before installing other programs, I ran PMM again, but the same thing happened.
I got the same results with an even older HTC phone running WM 6.1.
SQL desktop applications
I found some free SQL desktop apps. I was only able to get one, SdfBrowser, to read MedicalRecords.sdf and all it allowed was viewing the structure and creating a query.
I'll keep looking, but I agree with you that being totally portable is very important for this project.
LINKS: SdfBrowser --- Resources link
Jesterfell said:
I have been unable to run Prescription Medicines Manager on my HTC 8925 (Kaiser) with WM 6.5.x.
When I run the EXE all that happens is that the WM wait animation plays indefinitely until I switch to another application.
Since I play with this phone a lot, I hard reset it to clear any lingering results of my modding (it's a spare phone, so no great loss). Before installing other programs, I ran PMM again, but the same thing happened.
I got the same results with an even older HTC phone running WM 6.1.
Click to expand...
Click to collapse
Completely forgot to say, you will need to install SQL CE on your HTC.
I do not usually resort to smileys, but my lack of knowledge is frustrating!
deedee said:
Completely forgot to say, you will need to install SQL CE on your HTC.
Click to expand...
Click to collapse
I installed SQL CE with no errors but got the same lack of results. The phone did become VERY sluggish and Task Manager still showed "prjMedicalRecords" running as a process.
Does prjMedicalRecords.exe need to be installed?
I just executed it from the SD card, and then tried it from the device memory. I placed MedicalRecords.sdf in the same directory each time.
Update: After about 5 min of the WM wait animation spinning, got the following error message:
"File or assembly name 'System.Data.SqlServerCe,Version 3.0.3600.0, Culture=neutral, PublicKeyToken=3BE235DF1C8D2AD3', or one of its dependencies, was not found."
I opened the SQL CE .CAB file and it DOES contain "system.data.sqlserverce.dll" it is meant to be installed to "%InstallDir%" and the rest of the DLLs go to "%InstallDir%\v3.5". I used file explorer to look in those directories (%InstallDir%="Microsoft SQL Server Compact Edition") but did NOT find "system.data.sqlserverce.dll" in either dir.
I copied the DLL to "%InstallDir%\v3.5" and ran the program again. The same results occurred.
After soft reset, copied the DLL to "%InstallDir%" and ran PMM again. The same thing happened, long wait, then error msg.
I am falling asleep now, but will try re-installing .NET 3.5 and running PMM again. I'll let you know what happens.
I had gotten the same error before installing SQL CE but did not connect the error to PMM so I ignored it. This time nothing else was happening on the phone.
Apologies for not giving the initial steps, I am new to development and forget others need to be given the assumptions.
SQLCE needs to be installed, as you have done. PMM is just an exe, copy it to the device.
PMM and the SDF file need to be placed in \Program Files\prjMedicalRecords on the device itself. At the moment this location is hard coded and is on my list of things to do to make it "moveable". HTH
New version in post 1 that is now independent of location, just make sure both exe and SDf are in thhe same place.
deedee said:
New version in post 1 that is now independent of location, just make sure both exe and SDf are in thhe same place.
Click to expand...
Click to collapse
Sorry, Deedee. It still does the same thing.
.1. I put both files in device memory (just in case): \Program Files\prjMedicalRecords\
.2. Tried to re-install NET framework 3.5--it refused to install in either device or card memory, saying the same version was already in ROM.
.3. Re-installed sqlceppcwce5armv4i.cab
.4. Ran prjMedicalRecords.exe
After the same delay, it gave the same error.
It also gave a NET error that, because of the delay between program launch and errors, I did not associate with Medical Records before, but it only occurs after I have launched prjMedicalRecords.exe:
"The application failed to load required components. If the .NET Compact Framework is installed on a storage card, please ensure that this card is in place and launch the application again. If this fails, a re-installation of .NET compact Framework is recommended. Support info: -2147483643 (80000005)"
Thank you for your continued interest.
Not sure what the error is pointing to but I am coding for .Net CF v2, CAB in post 2, try installing this.
OK, finally tried this on a virgin device, without using the "debug" option in VS2005 to copy the files and discovered that .NET CF2, along with SQLCE 3 and SQL CE 3 replication is needed.
All CABs are in post 2.
There is a new version hopefully out this weekend with the ability to log patient medications and doctors appointments.
Editing is still on the road map, as is deletion.
New version in post #1, CAB format as well.
Make sure all the dependencies are installed, for me this has been .NET CF2 and the SQLCE cabs.
There are bugs I am aware of but please list anything and everything. As this is my first real App any feedback is welcome.
UPDATE 274/2012
Okay. So, Nokser's FFUPartTool extracts the IMGFS partition from the FFU.
Barin's OSBuilder (here) can be used to dump the contents of the IMGFS.
The registry files can then be edited in HVEdit (link), and the IMGFS can be recreated using OSBuilder.
FFUPartTool can then be used to replace the IMGFS partition in the FFU.
This FFU now needs a Mazaa to be flashed on.
If anyone out here is brave enough to flash their phone, please report the results!
UPDATE 17/4/2012
So, as we all know we have a stock mango FFU for the Mazaa (see here if you don't).
And due to recent developments, we also have this: FFUPart Tool v1.3.1
What this means is, we can create a custom FFU for the Mazaa. Now, personally, I have never created WP7 CFW before, but Nokser, the creator of the tool above assures me the creating CFW with this tool is quite possible.
So, what are you guys waiting for? Race to the finish line?
My list of things to be done starts and ends with this: get htc connection setup to run.
That's literally all we need to kickstart the Mazaa scene. Once we have that, we can do the whole shebang.
We need a ROM image for the Mazaa before anything at all can happen.
-------------------------------------------------------------
Here are the ROMs being used by people:
7.1.7649 - Test Rom. Has lots of interesting Microsoft applications (the zApps). But lacks quite a few features and stability.
7.1.7661.wp7_5_trial(mojobld).20110607-1657 - Similar Test Rom.
7.1.7720.68 - Locked bootloader. Phone is recognized as an HTC Device, but Connection Setup doesn't run.
7.1.7720.500 - Is basically the same as .68 but with an unlocked bootloader. Phone is not recognized as an HTC Device.
7.1.7740.16 - Updated via the official CAB [WP7 Cab sender tool]
7.1.8107.79 - via the official CAB [WP7 Cab Sender Tool]
7.10.8773.98 - via the official CAB [WP7 Cab Sender Tool] - 28/06/2012
Firmware revision number: 1600.1502.7720.68
Hardware revision number: 112.1410.2.0
Radio software version: 1.6.00.15.02
Radio hardware version: 8655/DDR2
Bootloader version: 7.27.00
Chip SOC version: 0.75.2.1
If anyone has different details, please post them.
-------------------------------------------------------------
The major problem with all ROMs is the lack of drivers.
1) LED lights don't function
2) SD Card slot
3) Connection Setup drivers
4) Internet Sharing doesn't work
Secondarily, because of the lack of connection setup drivers, there's no interop unlock. Which means no homebrew. Which means this device is pretty much what a technophobe buying a smartphone for the first time needs.
-------------------------------------------------------------
Does anyone know how to edit FFU (full flash update) files? They seem to be .cab files with a signed xml .blob in them.
Is there any way to edit these files?
Alternately, has anyone been successful at obtaining a stock ROM for the Mazaa? Because otherwise the device is extremely crippled.
Once we obtain a stock ROM, it's merely the point of identifying what drivers are missing, appealing to the DFT team to test the Mazaa to check whether HSPL/RSPL works, testing whether HTC Trophy drivers (and maybe other phones' drivers) work, cooking a rom, and flashing it. Once we get the ball rolling, it should all materialise.
-------------------------------------------------------------
Finally, what other problems are people having with their Mazaas?
Here's a list of problems I've noticed across the net:
Low battery life (4 - 6 hours at most).
Inability to connect to CDMA networks
Can't use HTC Connection Setup - hence no 3g/mms on certain networks
Inability to connect to certain GSM networks - lack of a valid IMEI
Frequent restarts/hangs [2 - 3 per day in some cases]
Each of these are frustrating faults.
Here' to hoping that the hundreds of DEVELOPERS with Mazaas can put in a concerted, collective effort and get this going. EVERY other phone has been unlocked/tweaked/improved upon, so why not a limited edition developer-exclusive device?
Thanks for summarizing the various versions. As developers, with a concerted effort, we should be able to resolve the issues and make it work for us.
I think most people sold the device, even if this wasn't allowed, at least for the first batch (not those won, but those requested for mango/gyro dev)
I had hopes battery problems where in a faulty battery...
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
abhilaksh said:
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
Click to expand...
Click to collapse
That's right, but they're probably not in dev hands anymore, so chances are not very helpful hands at this, especially since there's no more access to official updates.
All summed up, since not even the gyro works correctly on mine, it's a paper weight for which I'm still waiting for import taxes refunding
As far as issues, in addition to the above:
- I cannot send/receive MMS (SMS works, though)
- No 3G (DO or 2x only)
- 2-3 crashes per day
My build is 7.1.7720.68
Sent from my Mazaa using XDA Windows Phone 7 App
I have HTC Mazaa
I have the HTC Mazaa device that exactly matches all the details given in the original post in this thread.
For me, its working perfectly, no battery problems (works for 2-3 days), no crashes at all, I can't say about 3G support problems because we don't have that in our country. The phone works perfectly fine.
I have dev unlocked the device from App Hub but would love to remove the interop lock as well...in fact thats what I came here for.
Please guide me.
Thanks.
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Please guide me on I can interop-UNlock the device.
How can I update my Mazaa to 7.1.7740.16 build?
Mike48236 said:
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Hello there,
Currently I'm using a Mazaa sent from MS with the 7720.500 fw, It has all the zApps and the internal MS apps like FindSomeone, it has battery issues (but it's not worse than an Omnia 7 with Mango), and there are four annoying things experienced:
- volume is always a bit too loud and MP3 playback is sometimes faltering
- when you press the ON/OFF button, sometimes the screen comes back immediately after turning it off
- when you place a call, sometimes the screen turns off immediately, which can be brought back using the proximity sensor (hold close to head, then move it away)
- cannot receive MMS messages
Exact details:
OS: 7720.WM7_Main(mojobld).20110723-1640
FW: 1600.1502.7720.500
HW rev: 112.1410.2.0
Radio SW: 1.6.00.15.02
Radio HW: 8655/DDR2
Bootloader: 7.27.0.0
Chip SOC: 0.75.2.1
I'm no expert in messing with phones (only using homebrews once they become 99.999999999% safe) but if I can help in any ways I'm not breaking this phone, I can surely do my part provided I'm given step by step instructions.
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
abhilaksh said:
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
Click to expand...
Click to collapse
I'm sorry but I'm not going to be of any help in getting an updated ROM, since we are low on the supply chain. Also, the way we get each new build is by getting a new phone. (Send back old one, get one with newer software.)
I have an HTC Mazaa, running 7720. Everything is ok for a dev phone, I have no serious problems with it, except EDGE/GPRS not working and speaker emitting a loud tone when I'm calling a number outside my network. I'm thinking of installing the new updated build. How should I proceed exactly? Should I use the cab sender tool? I also want to mention that the phone is not dev unlocked, I'm still waiting for a student unlock. Thanks.
download the cab sender.
download the cab.
place the cab in the same folder as the cab sender.
run the cab sender.
send the cabs to the phone.
you're done.
I tried to update my HTC Mazaa and I got an error at the first restart. But, after that I typed *#06# on the Phone hub and I get this IMEI: 00A100000794C***.
I did it again, but this time, with my SIM card inside the phone. Unfortunately, I got the old IMEI message: Failed.
***
Even after all could not update my smartphone:
Verificando o status do telefone: Completed in 2,01 seconds
Verificando requisitos do sistema: Completed in 0,11 seconds
Fazendo o download de atualizações: Completed in 2,87 seconds
Verificando requisitos do sistema: Completed in 0,01 seconds
Transferindo atualizações: Completed in 24,65 seconds
Preparando para instalar: Completed in 46,16 seconds
Reiniciando o telefone: Completed in 231,04 seconds
Instalando atualizações: Completed in 70,15 seconds
Verificando o status do telefone: Completed in 0 seconds
Reiniciando o telefone: Completed in 34,28 seconds
Concluindo atualizações: Completed in 20,04 seconds
Error:
Update device 53d261df - cd29c761 - 4fe43c2f - 733020be Complete with error code
: 80180048, error message: Falha ao instalar IU (Image Update) devido a um erro.
■
╚══════» Done
Is there anyone on xda-devs to help us update our HTC Mazaa and also do the interop-unlock?
Mazaa ROM
Hmm...
Here.
http://hotfile.com/dl/135477621/ed2186c/FlashClean.zip.html
That's an FFU.
Which cab should I use? Or which is the recommended one? Thanks.
Thankyou for that FFU
@abhilaksh Thankyou for that FFU file it saved me from alot of messing around. So happy to get my Mazaa back in working order. It broke on me a few months ago and ive been though hell trying to get the bugger fixed. It just got stuck on the mobile operator screen.
imgur(dot)com/oBH9M
Even had it sent off to UK repair center for them to send it back in the same condition (Idiots). I was just about to send it off to a US repair center when i did some more searching. It worked a treat, really straightforward as well.
If anyone else is a noob in the same situation as i way id recommend these simple instructions:
1. Install Zune Beta Client (beta includes the UpdateWP tool)
2. Install the SetupUpdateWp.exe to get the tool
3. Follow these instructions to flash your phone
mobilitydigest(dot)com/ms-instructions-on-how-to-flash-a-windows-phone-7-device/
Thanks again, Rob