You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
(53) |
Apr
(48) |
May
(14) |
Jun
(3) |
Jul
(21) |
Aug
(11) |
Sep
(77) |
Oct
(67) |
Nov
(28) |
Dec
(163) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(112) |
Feb
(143) |
Mar
(114) |
Apr
(138) |
May
(173) |
Jun
(119) |
Jul
(119) |
Aug
(117) |
Sep
(187) |
Oct
(170) |
Nov
(254) |
Dec
(193) |
2005 |
Jan
(336) |
Feb
(284) |
Mar
(189) |
Apr
(100) |
May
(89) |
Jun
(52) |
Jul
(85) |
Aug
(138) |
Sep
(181) |
Oct
(137) |
Nov
(104) |
Dec
(98) |
2006 |
Jan
(76) |
Feb
(106) |
Mar
(224) |
Apr
(270) |
May
(103) |
Jun
(144) |
Jul
(77) |
Aug
(38) |
Sep
(37) |
Oct
(20) |
Nov
(14) |
Dec
(73) |
2007 |
Jan
(130) |
Feb
(68) |
Mar
(78) |
Apr
(60) |
May
(45) |
Jun
(63) |
Jul
(84) |
Aug
(45) |
Sep
(40) |
Oct
(12) |
Nov
(71) |
Dec
(56) |
2008 |
Jan
(44) |
Feb
(20) |
Mar
(25) |
Apr
(17) |
May
(33) |
Jun
(60) |
Jul
(97) |
Aug
(38) |
Sep
(10) |
Oct
(20) |
Nov
(13) |
Dec
(19) |
2009 |
Jan
(7) |
Feb
(5) |
Mar
(23) |
Apr
(10) |
May
(6) |
Jun
(5) |
Jul
(17) |
Aug
(7) |
Sep
(14) |
Oct
(27) |
Nov
(13) |
Dec
(12) |
2010 |
Jan
(37) |
Feb
(9) |
Mar
(13) |
Apr
(12) |
May
(8) |
Jun
(3) |
Jul
(1) |
Aug
(9) |
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
(4) |
2011 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(4) |
May
|
Jun
(2) |
Jul
(8) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(3) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
From: Stephen W. <sa...@us...> - 2003-11-09 16:44:45
|
As I prepare to get up the nerve to let my Sanyo 4900 modification to Bitpim write to my phone, I wonder how Bitpim should handle Speed dial indices. The speed dial index will be overwritten unless I explicitly write it out. OK, so I only have 8 speed dial slots on the phone which will take about 2 minutes to recreate by hand, but why not get it right? If bitpim can save a speed dial index along with the phone book, then this pretty much solves the problem. If it is not planned for bitpim to save a speed dial index (or if one is writing a phonebook to a phone where that phonebook doesn't have a speed dial index), I thought that the speed dial could be handled as follows. 1. Before writing to the phone, read the speed dial index. 2. Remove speed dial entries that don't have a corresponding number in the phonebook being written to the phone. 3. Write out the edited speed dial list. |
From: Roger B. <ro...@ro...> - 2003-11-07 03:35:53
|
Roger Binns wrote: > I would appreciate it if people can test 0.62 to ensure > it works before I announce it to the world. Forgot to mention the URL. Scroll down to bitpim-tests on http://sourceforge.net/project/showfiles.php?group_id=75211 There are both Windows and Linux releases. Roger |
From: Roger B. <ro...@ro...> - 2003-11-07 03:33:59
|
I would appreciate it if people can test 0.62 to ensure it works before I announce it to the world. (I've done my own testing - I just need some kind people to sanity check it). Please send a quick email (ro...@ro...) letting me know if all worked fine, or if you found any problems. The biggest improvement is a workaround a driver bug in the drivers from LG (which you get with the mobile office kit from Verizon). Changes in 0.62: - Scrolling in the log windows now always leaves text visible - Absurd dates on files in filesystem view no longer cause an exception - Work around the LGE buggy driver which has difficulty with the concept of timeouts - Updated to pySerial 2, wxPython 2.4.2.4 on all platforms and Python 2.3.2 on Windows Roger |
From: Roger B. <ro...@ro...> - 2003-11-05 00:22:07
|
> Since "data" is not in this list, should I convert Sanyo "data" numbers > to BitPim "none" numbers. If I ever use the Data field on my phone, > it's just going to hold some extra number for someone, not a modem > number. It seems like a valid type to me. Just add it as data. Other phones that don't have that type will have to convert it to something meaningful if they see it. Roger |
From: Stephen W. <sa...@ge...> - 2003-11-04 23:55:41
|
On Mon, 2003-11-03 at 18:55, Roger Binns wrote: > > 1. The Sanyo SCP-4900 can hold 7 phone numbers per name, up to one of > > each of the following types "Home, Work, Mobile, Pager, Data, Fax, No > > Label". In putting the data into Bitpim structures, should these types > > be normalized to a bitpim standard? I am guessing these would be "home, > > office, cell, pager, data, fax, none". > > They are documented in > http://cvs.sourceforge.net/viewcvs.py/bitpim/bitpim/phonebook.py?view=markup > Since "data" is not in this list, should I convert Sanyo "data" numbers to BitPim "none" numbers. If I ever use the Data field on my phone, it's just going to hold some extra number for someone, not a modem number. Steve |
From: Roger B. <ro...@ro...> - 2003-11-03 23:55:06
|
> 1. The Sanyo SCP-4900 can hold 7 phone numbers per name, up to one of > each of the following types "Home, Work, Mobile, Pager, Data, Fax, No > Label". In putting the data into Bitpim structures, should these types > be normalized to a bitpim standard? I am guessing these would be "home, > office, cell, pager, data, fax, none". They are documented in http://cvs.sourceforge.net/viewcvs.py/bitpim/bitpim/phonebook.py?view=markup One change I think I am going to make is removing the number suffix. This is because the list is ordered anyway, and so the second 'home' is already implicitly 'home2'. > 2. For the LGVX4400, phonize is called before writing a number to the > phone to remove all characters except digits, P, T, * and #. For the > 4900, the allowed characters are digits, dash, H, T, * and #. H is a > hard pause and T a two second pause. Is H the same meaning as P? > Should I convert H's to P's when going to bitpim structures, and P back > to H when writing to the phone? The 4400 will truncate the number written to it at the first non-acceptable character. The UI on the phone then tries to put dashes back in when displaying numbers (that was one of the fixes in the original firmware releases). BitPim doesn't place any meaning on the numbers and other characters in there. It will be somewhat relevant when "importing" entries since it will have to decide if two numbers each from a different source are the same. I will do that by just stripping out all non-digits while doing the comparison. > 3. When writing a bitpim phonebook to a phone, it seems that two > conversion steps are done to put the data into a format suitable for the > specific phone. First the convertphonebooktophone method of the Profile > class is done, and then makeentry is done to put the data into the > structure defined in the protocol definition file. Can you explain why > these two steps are done, and which conversions belong in each place. > (for example, why is phonize done in makeentry and not > converphonebooktophone?) All of the communication with the phone is done in a background thread. You can't do any GUI operations from that thread. The purpose of the first pass (convertphonebooktophone) is to do any preparations it wants and then have the ability to do some gui operations. On the 4400, it re-reads the wallpaper and ringtone index files. It could also check there is enough space for all the entries or similar things. The second stage (savephonebook not makeentry) then actually commits the data. Roger |
From: Roger B. <ro...@ro...> - 2003-10-31 10:18:17
|
For anyone who has the source code checked out, you now need python-dsv installed. It is used for the import of csv files. Grab the code from https://sf.net/projects/python-dsv It should end up as c:\python23\Lib\site-packages\DSV or /usr/lib/python2.2/site-packages/DSV Roger |
From: Stephen W. <sa...@us...> - 2003-10-31 02:07:16
|
On Thu, 2003-10-30 at 20:08, Roger Binns wrote: >... > > The 4400 uses the serials to index voice and speed dials. The Sanyo 4900 also does the same. They are also used in a big phone number -> Name index that the phone needs for caller ID. I think it is the responsibility of sync software to keep this index up todate when modifying the phone book. |
From: Roger B. <ro...@ro...> - 2003-10-31 01:08:11
|
>> Yes. Also note that the fields are in priority order. For example >> if saving to a device that only supports two numbers then the first >> two would be picked. > The priority could just be the order on the phone, > home/office/mobile/pager/data/fax/other, or will bitpim have a defined > or user configurable priority? The user will be able to change the order in the user interface. For phones such as the 4400 where it stores 5 numbers (each can be of any type) or the Palm desktop which stores 4 details (email or phone number), they will really care about the order. > The packet has two numbers. The first number is probably just parotting > back the slot number that was requested and the second is what the phone > fills in. The second number might be zero if that particular slot has > never been used, but I am not sure. The 4400 uses the serials to index voice and speed dials. Roger |
From: Stephen W. <sa...@ge...> - 2003-10-31 00:37:34
|
On Thu, 2003-10-30 at 18:00, Roger Binns wrote: > Stephen Wood wrote: > > Here is a sample record from phonebook/index.idx after import from a > > SCP-4900. Should I be supressing fields that are blank from this > > structure? > > Yes. Also note that the fields are in priority order. For example > if saving to a device that only supports two numbers then the first > two would be picked. The priority could just be the order on the phone, home/office/mobile/pager/data/fax/other, or will bitpim have a defined or user configurable priority? > Does the phone actually have two serial numbers? The 4400 has two > serials per entry which are always the same, but I currently export > both in case they are different one day. The packet has two numbers. The first number is probably just parotting back the slot number that was requested and the second is what the phone fills in. The second number might be zero if that particular slot has never been used, but I am not sure. Steve > > Roger > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel > |
From: Roger B. <ro...@ro...> - 2003-10-30 23:07:54
|
> When I try to read a packet with names less than 16 characters, it works > (the phone pads fields with nulls). But on the following packet, with a > 16 character name, I get an error. You can set raiseonunterminatedread to False. > Are there some attributes to STRING > that I can add that will help? The length of the string is available in > the packet, but is not located adjacent to the string itself. I guess the problem here is that the field has a length in bytes (including padding) as well as a length in characters. It even looks like the length in characters can be in a later field which makes things even nastier. If the raiseonunterminatedread doesn't work for you, you could derive a new string class (or add an argument to the existing one) that lets you truncate the characters to a certain size. It won't be much use when the length field is after the string field though. Roger |
From: Roger B. <ro...@ro...> - 2003-10-30 23:00:52
|
Stephen Wood wrote: > Here is a sample record from phonebook/index.idx after import from a > SCP-4900. Should I be supressing fields that are blank from this > structure? Yes. Also note that the fields are in priority order. For example if saving to a device that only supports two numbers then the first two would be picked. > 11: Incidentally the key is just a random number. If BitPim ever moves to needing a real database, then it will be used as the key for the record. Currently it is just decoration. > 'serials': [{'serial2': 11, 'serial1': 11, 'sourcetype': > 'scp4900', 'sourceuniqueid': > 'ffffffff955cb196e5dbc20be8029883ffffffff'}], Does the phone actually have two serial numbers? The 4400 has two serials per entry which are always the same, but I currently export both in case they are different one day. Roger |
From: Stephen W. <sa...@us...> - 2003-10-30 21:56:07
|
Here is a sample record from phonebook/index.idx after import from a SCP-4900. Should I be supressing fields that are blank from this structure? 11: { 'emails': [{'email': ''}], 'names': [{'full': 'Dodd Violin'}], 'numbers': [{'type': 'home', 'number': ''}, {'type': 'office', 'number': '1111111111'}, {'type': 'mobile', 'number': ''}, {'type': 'pager', 'number': ''}, {'type': 'data', 'number': ''}, {'type': 'fax', 'number': ''}, {'type': 'other', 'number': ''}], 'serials': [{'serial2': 11, 'serial1': 11, 'sourcetype': 'scp4900', 'sourceuniqueid': 'ffffffff955cb196e5dbc20be8029883ffffffff'}], 'urls': [{'url': ''}], }, |
From: Roger B. <ro...@ro...> - 2003-10-30 07:27:11
|
> It looks like the phonebook nvm file is composed of fixed-length blocks > of data. I think Stephen has those figured out in the sync protocol. If you follow the instructions on the web site on the developer page and get bitpim from CVS there is a snappy protocol analyser that makes things clear. What about the other nvm files you thought might be images? Roger |
From: Loren P. <mic...@us...> - 2003-10-30 06:52:29
|
Hi, It looks like the phonebook nvm file is composed of fixed-length blocks of data. Each one is 0x1d7 bytes long and starts with a three byte header, which includes a counter: 01 00 00 (first entry, starting at 0x0000) 01 01 00 (second entry, starting at 0x1d8 01 02 00 (etc...) 01 03 00 This header is followed by a 16 byte text field containing the name of the entry, an 0xA, and then the home phone number for the entry. The subsequent numbers are work, then mobile, each 48 bytes. Here's an example (nvm_0008): 00000000 01 00 00 41 61 20 4B 75-73 69 61 00 00 00 00 00 ...Aa Kusia..... <--------name of entry 00000010 00 00 00 0A 35 31 30 xx-xx xx xx xx xx xx 00 00 ....510xxxxxxx.. <--------home phone 00000020 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000030 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000040 00 00 00 00 00 0A 34 31-35 xx xx xx xx xx xx xx ......415xxxxxxx <--------work phone 00000050 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000060 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000070 00 00 00 00 00 00 00 0A-35 31 30 xx xx xx xx xx ........510xxxxx <--------mobile phone 00000080 xx xx 00 00 00 00 00 00-00 00 00 00 00 00 00 00 xx.............. 00000090 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000000A0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000000B0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000000C0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000000D0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000000E0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000000F0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000100 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000110 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000120 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000130 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 0F ................ 00000140 30 31 31 33 38 30 35 30-36 37 34 xx xx xx xx 00 01138050674xxxx. <------ "other" phone 00000150 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000160 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 00000170 00 0F 6B 75 73 69 61 40-xx xx xx xx xx 2E 6E 65 ..ku...@xx... <------ email 00000180 74 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 t............... 00000190 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000001A0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000001B0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000001C0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ 000001D0 00 00 00 00 00 00 08 00-01 01 00 4C 6F 72 65 6E ...........Loren <------ beginning of second 000001E0 00 00 00 00 00 00 00 00-00 00 00 0A 35 31 30 35 ............5105 entry -loren Roger wrote: >Just for comparison, here is a dump from a VX4400. There is considerably more than on your phone. Can you post the first line of a hex dump >from the nvm files since that should help show what the format is..... |
From: Roger B. <ro...@ro...> - 2003-10-30 04:29:48
|
> OS crashes). Not having to reboot the phone, combined with protocol log > and tracebacks on exceptions really make developing and debugging fun! I'll take that as a compliment :-) I am hoping that adding new phones should be very easy. I still need to deal with the UI side of it though where things (except the phonebook) map to how the 4400 does things with minimal abstraction. Roger |
From: Roger B. <ro...@ro...> - 2003-10-30 04:18:47
|
I thought I would let everyone know what I have been working on. I am doing the precursor work to importing phone number details. I have written code that reads Vcard as well as the Windows Address Book. I wanted to do that so I understand a lot better exactly how they model phonebook entries before trying to write code that will do imports. The programmer at Microsoft responsible for WAB has some apologising to do! Neither WAB nor the Palm Desktop handle Vcards correctly according to the spec - they work fine for most trivial cases, and the spec is somewhat disgusting anyway. I also tried interfacing to Palm Desktop using COM. Unfortunately it looks like you can only execute inside the Palm Desktop process, rather than using their code as a slave to manipulate the data. If there is anyone who has more experience at COM and wants to fight Palm Desktop a bit, let me know. I also looked at the CSV output from WAB and Palm, and they will be relatively trivial to deal with. Finally I also looked at Mozilla which didn't know about vcards at all! Of course none of the CSV exports bother putting in header rows to make it just that little bit harder to interoperate with. I also figured out how I am going to do the new UI for the phonebook. My next steps will be to write the CSV import code and gui. Roger |
From: Stephen W. <sa...@us...> - 2003-10-30 04:17:46
|
I have the following packet description: PACKET {'readwrite': 0x0d} sanyoheader: 1 UINT readwrite 1 UINT command 1 UINT packettype PACKET phonebookentry: 2 UINT slot 2 UINT slotdup 16 STRING name * LIST {'length': 7} numbers: 1 UINT number_len 49 STRING number 1 UINT email_len 49 STRING email 1 UINT url_len 49 STRING url 1 UINT secret 1 UINT name_len PACKET phonebookslotresponse: * sanyoheader header * phonebookentry entry 30 UNKNOWN pad When I try to read a packet with names less than 16 characters, it works (the phone pads fields with nulls). But on the following packet, with a 16 character name, I get an error. Are there some attributes to STRING that I can add that will help? The length of the string is available in the packet, but is not located adjacent to the string itself. Steve |
From: Stephen W. <sa...@us...> - 2003-10-30 02:33:39
|
Thanks for the explanations! I knew the thet _setmode methods were being called, but couldn't figure out how. >The 4400 phonebook does get confused if you keep reading it. Other >sync software actually reboots the phone after each read or write. I >found that forcing brew mode before going into phonebook mode solves >that problem. I just started trying out some snippets of code for my SCP4900. The forcing of brew mode really helped speed up the debugging cycle. When I was learning the protocol for the phone using C programs and Perl scripts, I had to reboot my phone a lot. (Which I am convinced let to OS crashes). Not having to reboot the phone, combined with protocol log and tracebacks on exceptions really make developing and debugging fun! |
From: Roger B. <ro...@ro...> - 2003-10-29 23:45:13
|
[Stephen asked this privately but I figured it should be documented for all to see] > For the existing phones in Bitpim, how does the code put the phone into > DM mode? I believe this happens when one clicks on get phone data in > the GUI and that _setmodebrew in com_brew.py actually does it, but due > to my lack of Python and OO understanding, I don't understand how it > gets from here to there. Multiple inheritance and introspection :-) Examine com_lgvx4400 and see how it inherits from generic phone, brew and lg. There is a function in generic phone called setmode. Generic phone also has defines the constants for MODENONE (which is how things start out) and MODEMODEM. brew defines MODEBREW, and lg defines MODEPHONEBOOK. vx4400 gets all of these because of the inheritance. Then what happens is that any code that needs the phone to be in a particular mode calls the setmode function. For example the sendbrewcommand function calls setmode(MODEBREW) The setmode function immediately returns if the desiredmode is the same as the current mode. It then removes the front MODE and lowercases the rest. It looks for function named _setmodeoldtonew where old and new are the old and new modes. If none is found, it looks for _setmodenew. This lets you write code for specific mode changes, or just a generic one ignoring the previous mode. > It seems that one of the first communications with the phone is to get > the ESN by retrieving the file nvm/$SYS.ESN. I read in some of your > comments on the devel list, that the phone can be confused switching > between brew commands and non brew commands. Should I avoid letting the > Sanyo code make the filesystem call to get the ESN? The 4400 phonebook does get confused if you keep reading it. Other sync software actually reboots the phone after each read or write. I found that forcing brew mode before going into phonebook mode solves that problem. The ESN is read because I wanted a unique identifier per phone. Each entry that is read in has a list of identifiers of the source device, as well as some sort of serial for that device. This makes it really easy to match up entries read in the future, especially if the user has altered the name and/or some of the numbers. Here is an actual test entry from my phone: { 'categories': [{'category': 0}], 'emails': [{'email': 'email1 adadadadadadbdadadadaebdadadadadbdadadada'}], 'flags': [{'secret': True}], 'memos': [{'memo': ''}], 'names': [{'full': 'Nnadadadadadadadadadad'}], 'numbers': [{'type': 'home', 'number': '111111111111111111111111111111111111111111111111'}, {'type': 'office', 'number': '222222222222222222222222222222222222222222222222'}], 'ringtones': [{'use': 'call', 'ringtone': 0}, {'use': 'message', 'ringtone': 0}], 'serials': [{'serial2': 234, 'serial1': 234, 'sourcetype': 'lgvx4400', 'sourceuniqueid': '1aadcbb3d92021e92b614f326e2de9f3cb1f77d2'}], 'urls': [{'url': 'www.jmjmjmjmjmjmjmjmjmjmjmjmjmkmjmjnjmjmjmjmjmjm'}], 'wallpapers': [{'use': 'call', 'wallpaper': 12}], } On the 4400, Brew mode is also needed to turn wallpaper and ringtone indices back into filenames. I haven't implemented that yet (as you can see above it still uses the index numbers) but I will be doing so. Roger |
From: Roger B. <ro...@ro...> - 2003-10-29 22:29:45
|
> "serial" package imported in commport.py. I tried to install both > pyserial-1.21 and pyserial-2.0b2 and got the following error: I am actually still on pyserial 1.20. 1.21 only has Windows fixes, and they don't apply to BitPim anyway. I actually do my Linux dev on a RH8 box. Anyway, all you need to do is copy the serial directory to /usr/lib/python2.2/site-packages Roger |
From: Stephen W. <sa...@ge...> - 2003-10-29 21:55:09
|
I am just getting ready to try out some rudimentary code to read the Sanyo 4900 phone book, and I discovered that I am still missing one piece in being able to run the CVS copy of Bitpim on linux. Namely, the "serial" package imported in commport.py. I tried to install both pyserial-1.21 and pyserial-2.0b2 and got the following error: # python setup.py install error in setup script: invalid distribution option 'classifiers' Obviously I don't know anything about python. Is there some other package that I need to install? (I am running Python 2.2.2 as include with Redhat 9.0 and I have python-devel installed). Thanks for any help, Steve |
From: Mr. M. L. <mai...@ya...> - 2003-10-29 14:01:03
|
i'm sorry, but how do you mean "uploaded to the sprint website"? can i upload midifiles and pictures straight to sprint's website, then have them be downloaded onto my 4900? --- loren <lo...@ne...> wrote: > Stephen, > > More on the photo question: > > I have 14 photos on my phone, which I just uploaded > to the sprint > website and then downloaded to my computer (very > cumbersome process!). > The total size for 14 photos is about 380K. That's > more than the total > size of all the files that we see in the whole phone > directory. More to > the point, the whole directory tree from my phone > compresses down to > about 78K, while the 14 jpeg files aren't, of > course, very compressible > and take up about the same 380K when zipped. > > It seems like the phone memory is in a separate area > -- maybe the whole > phone peripheral is separate from the rest of the > phone? - and so > probably has to be accessed via some special > commands. > > loren > > Stephen Wood wrote: > > > One question of interest to me (academic interest > since I don't have a > > > >camera phone) is whether or not Bitpim could easily > be used to download > >pictures taken with the SCP-8100 camera. Loren, do > you see any thing > >that looks like pictures you have taken in the > filesystem you downloaded > >from the phone? > > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback > Program. > Does SourceForge.net help you be more productive? > Does it > help you create better code? SHARE THE LOVE, and > help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ |
From: Roger B. <ro...@ro...> - 2003-10-29 08:43:54
|
Just for comparison, here is a dump from a VX4400. There is considerably more than on your phone. Can you post the first line of a hex dump from the nvm files since that should help show what the format is. C:\4400>\msys\1.0\bin\ls -alR .: total 4 -rw-r--r-- 1 rogerb Administ 206 Apr 23 2009 $SYS.FACTORY -rw-r--r-- 1 rogerb Administ 188 Apr 23 2009 $SYS_RMT -rw-r--r-- 1 rogerb Administ 436 Apr 25 2009 $USER_DIRS drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 38 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 34 Apr 23 2009 LG.cfg -rw-r--r-- 1 rogerb Administ 5 Apr 22 2009 RDM_PORT_MAP drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 VoiceDB drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 alarm -rw-r--r-- 1 rogerb Administ 219 Aug 9 07:15 appprefs -rw-r--r-- 1 rogerb Administ 4 Aug 9 07:15 appprefs.idx -rw-r--r-- 1 rogerb Administ 1 Apr 22 2009 bootefs.id drwxr-xr-x 6 rogerb Administ 0 Oct 29 00:39 brew drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 dloadindex drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 download drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 eri drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 nvm drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 pim drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 sch drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 sms drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 t9udb drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 up drwxr-xr-x 3 rogerb Administ 0 Oct 29 00:39 user ./VoiceDB: total 0 drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 All drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 Lang ./VoiceDB/All: total 0 drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 .. drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 Memos drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 Patterns drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 Tags ./VoiceDB/All/Memos: total 1 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 3 Apr 22 2009 NextMemo.int ./VoiceDB/All/Patterns: total 5 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 772 Apr 26 2009 CtrlWrd.int -rw-r--r-- 1 rogerb Administ 7576 May 30 2009 NameTag.int ./VoiceDB/All/Tags: total 2 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 3 Apr 22 2009 NextTag.int -rw-r--r-- 1 rogerb Administ 589 Apr 25 2009 Tag00007.tag -rw-r--r-- 1 rogerb Administ 2048 May 3 2009 uivrState.dat ./VoiceDB/Lang: total 0 drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 .. drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 English drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 Spanish ./VoiceDB/Lang/English: total 19 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 2908 Feb 13 2003 engdat_sd1.dtw -rw-r--r-- 1 rogerb Administ 34148 Feb 13 2003 engdat_sd1.prm ./VoiceDB/Lang/Spanish: total 24 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 4 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 2908 Feb 13 2003 spadat_sd1.dtw -rw-r--r-- 1 rogerb Administ 46008 Feb 13 2003 spadat_sd1.prm ./alarm: total 1 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 48 Apr 23 2009 alarm.dat ./brew: total 3 drwxr-xr-x 6 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 456 Apr 25 2009 appprefs -rw-r--r-- 1 rogerb Administ 16 Apr 22 2009 appprefs.idx -rw-r--r-- 1 rogerb Administ 3620 May 10 2009 caticons.bar drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 download drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 en drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 es drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 shared ./brew/download: total 11 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 6 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 221 Aug 17 15:19 dlc0.cat -rw-r--r-- 1 rogerb Administ 205 Apr 23 2009 dlc1244.cat -rw-r--r-- 1 rogerb Administ 3493 Aug 17 15:19 dlc1735.cat -rw-r--r-- 1 rogerb Administ 218 Apr 23 2009 dlc1737.cat -rw-r--r-- 1 rogerb Administ 1046 Apr 28 2009 dlc1738.cat -rw-r--r-- 1 rogerb Administ 421 Apr 24 2009 dlc1739.cat -rw-r--r-- 1 rogerb Administ 717 Apr 26 2009 dlc1740.cat -rw-r--r-- 1 rogerb Administ 586 Apr 25 2009 dlc724.cat -rw-r--r-- 1 rogerb Administ 755 Apr 26 2009 dlc726.cat -rw-r--r-- 1 rogerb Administ 3124 Jun 6 11:25 dlc727.cat -rw-r--r-- 1 rogerb Administ 215 Apr 23 2009 dlc729.cat -rw-r--r-- 1 rogerb Administ 581 Aug 17 15:21 dlc878.cat -rw-r--r-- 1 rogerb Administ 916 Apr 27 2009 dllog -rw-r--r-- 1 rogerb Administ 64 Apr 23 2009 dllog.idx ./brew/en: total 83 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 6 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 17619 Jul 19 2009 aeecontrols.bar -rw-r--r-- 1 rogerb Administ 3226 May 8 2009 appmgr.bar -rw-r--r-- 1 rogerb Administ 41456 Nov 14 2009 brewexiting.bmp -rw-r--r-- 1 rogerb Administ 41456 Nov 14 2009 brewstarting.bmp -rw-r--r-- 1 rogerb Administ 61258 Feb 21 2010 mshop.bar -rw-r--r-- 1 rogerb Administ 239 Apr 24 2009 oemmsgs.bar ./brew/es: total 63 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 6 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 17675 Jul 19 2009 aeecontrols.bar -rw-r--r-- 1 rogerb Administ 3264 May 9 2009 appmgr.bar -rw-r--r-- 1 rogerb Administ 41456 Nov 14 2009 brewexitinges.bmp -rw-r--r-- 1 rogerb Administ 61540 Apr 23 2009 mshop.bar -rw-r--r-- 1 rogerb Administ 232 Apr 24 2009 oemmsgs.bar ./brew/shared: total 264 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 6 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard0.bmp -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard1.bmp -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard2.bmp -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard3.bmp -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard4.bmp -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard5.bmp -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard6.bmp -rw-r--r-- 1 rogerb Administ 27702 Sep 8 19:52 clipboard7.bmp -rw-r--r-- 1 rogerb Administ 35334 Sep 8 19:53 clipboard8.bmp -rw-r--r-- 1 rogerb Administ 35334 Sep 8 19:53 dscn1237.bmp -rw-r--r-- 1 rogerb Administ 35334 Sep 8 19:53 dscn1439.bmp -rw-r--r-- 1 rogerb Administ 40014 Sep 8 19:53 garbage.bmp -rw-r--r-- 1 rogerb Administ 48354 Sep 8 19:53 ollie.bmp -rw-r--r-- 1 rogerb Administ 60464 Sep 5 11:08 pic01_gagin.jpg -rw-r--r-- 1 rogerb Administ 9766 Sep 8 19:53 plant.bci -rw-r--r-- 1 rogerb Administ 41094 Sep 8 19:53 shirley.bmp ./dloadindex: total 2 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 1262 Sep 8 19:53 brewImageIndex.map -rw-r--r-- 1 rogerb Administ 1262 Aug 28 02:32 brewRingerIndex.map ./download: total 35 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 23524 Aug 17 2009 poweroff.bit -rw-r--r-- 1 rogerb Administ 23524 Aug 17 2009 poweron.bit -rw-r--r-- 1 rogerb Administ 23524 Aug 17 2009 wallpaper.bit ./eri: total 1 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 127 Apr 23 2009 eri.bin ./nvm: total 2 -rw-r--r-- 1 rogerb Administ 97 Apr 23 2009 $SYS.ESN -rw-r--r-- 1 rogerb Administ 193 Apr 23 2009 $SYS.INVAR1 -rw-r--r-- 1 rogerb Administ 135 Apr 23 2009 $SYS.INVAR2 -rw-r--r-- 1 rogerb Administ 107 Apr 23 2009 $SYS.INVAR3 drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 nvm drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 prl drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 sms ./nvm/nvm: total 9 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 836 Apr 27 2009 nvm_0000 -rw-r--r-- 1 rogerb Administ 8119 Jun 2 2009 nvm_0001 -rw-r--r-- 1 rogerb Administ 802 Apr 26 2009 nvm_0002 -rw-r--r-- 1 rogerb Administ 990 Apr 27 2009 nvm_0003 -rw-r--r-- 1 rogerb Administ 2252 May 4 2009 nvm_0004 -rw-r--r-- 1 rogerb Administ 2561 May 5 2009 nvm_0005 ./nvm/prl: total 5 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 4102 May 13 2009 prl_0000 -rw-r--r-- 1 rogerb Administ 4102 May 13 2009 prl_0001 ./nvm/sms: total 1 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 5 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 61 Apr 23 2009 sms_0000 ./pim: total 16 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 44 Apr 23 2009 call_hist_nv.dat -rw-r--r-- 1 rogerb Administ 2065 May 3 2009 incoming_log.dat -rw-r--r-- 1 rogerb Administ 2065 May 3 2009 missed_log.dat -rw-r--r-- 1 rogerb Administ 2065 May 3 2009 outgoing_log.dat -rw-r--r-- 1 rogerb Administ 13950 Jul 1 2009 pbentry.dat -rw-r--r-- 1 rogerb Administ 240 Apr 24 2009 pbgroup.dat -rw-r--r-- 1 rogerb Administ 453 Apr 25 2009 pbmyvcard.dat -rw-r--r-- 1 rogerb Administ 2349 May 4 2009 pbnumber.dat -rw-r--r-- 1 rogerb Administ 200 Apr 23 2009 pbspeed.dat -rw-r--r-- 1 rogerb Administ 4 Apr 22 2009 record_id.dat ./sch: total 1 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 306 Jul 10 21:34 memo.dat -rw-r--r-- 1 rogerb Administ 482 Aug 28 02:34 schedule.dat -rw-r--r-- 1 rogerb Administ 0 Aug 28 02:34 schexception.dat ./sms: total 55 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 2748 May 6 2009 cbs00.dat -rw-r--r-- 1 rogerb Administ 2748 May 6 2009 cbs01.dat -rw-r--r-- 1 rogerb Administ 2748 May 6 2009 cbs02.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 18 19:54 inbox000.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 18 19:48 inbox001.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 20 14:11 inbox002.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 20 15:17 inbox003.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 21 15:27 inbox004.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 21 15:28 inbox005.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 21 15:34 inbox006.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 22 14:37 inbox007.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 27 13:31 inbox008.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 27 13:34 inbox009.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 27 14:09 inbox010.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 28 01:00 inbox011.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 28 01:02 inbox012.dat -rw-r--r-- 1 rogerb Administ 2624 Aug 29 17:58 inbox013.dat -rw-r--r-- 1 rogerb Administ 2624 Sep 3 23:29 inbox014.dat -rw-r--r-- 1 rogerb Administ 2624 Sep 3 23:35 inbox015.dat -rw-r--r-- 1 rogerb Administ 2624 Sep 3 23:38 inbox016.dat -rw-r--r-- 1 rogerb Administ 2624 Sep 7 15:59 inbox017.dat -rw-r--r-- 1 rogerb Administ 2624 Sep 7 16:12 inbox018.dat -rw-r--r-- 1 rogerb Administ 0 Apr 22 2009 info.dat -rw-r--r-- 1 rogerb Administ 28 Apr 22 2009 mediacan000.dat -rw-r--r-- 1 rogerb Administ 0 Apr 22 2009 outbox.dat -rw-r--r-- 1 rogerb Administ 3180 Aug 18 13:05 outbox000.dat -rw-r--r-- 1 rogerb Administ 3180 Aug 18 19:43 outbox001.dat -rw-r--r-- 1 rogerb Administ 3180 Aug 21 15:33 outbox002.dat -rw-r--r-- 1 rogerb Administ 3180 Aug 27 13:32 outbox003.dat -rw-r--r-- 1 rogerb Administ 3180 Aug 31 23:09 outbox004.dat -rw-r--r-- 1 rogerb Administ 3180 Sep 3 23:30 outbox005.dat -rw-r--r-- 1 rogerb Administ 3180 Sep 3 23:37 outbox006.dat -rw-r--r-- 1 rogerb Administ 3180 Sep 7 15:51 outbox007.dat -rw-r--r-- 1 rogerb Administ 3180 Sep 7 16:13 outbox008.dat -rw-r--r-- 1 rogerb Administ 0 Apr 22 2009 saved.dat -rw-r--r-- 1 rogerb Administ 3188 Aug 21 19:48 sf00.dat -rw-r--r-- 1 rogerb Administ 2624 May 5 2009 voice.dat ./t9udb: total 1 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 1024 Apr 27 2009 t9udb_eng.dat -rw-r--r-- 1 rogerb Administ 0 Apr 22 2009 t9udb_spa.dat ./up: total 36 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 5220 May 18 2009 aptable1.fil -rw-r--r-- 1 rogerb Administ 5220 May 18 2009 aptable2.fil -rw-r--r-- 1 rogerb Administ 1503 Apr 30 2009 bearerlist.fil -rw-r--r-- 1 rogerb Administ 273 Apr 24 2009 keytable1.fil -rw-r--r-- 1 rogerb Administ 273 Apr 24 2009 keytable2.fil -rw-r--r-- 1 rogerb Administ 11 Apr 22 2009 paramtable1.fil -rw-r--r-- 1 rogerb Administ 11 Apr 22 2009 paramtable2.fil -rw-r--r-- 1 rogerb Administ 120 Apr 23 2009 permanent.fil -rw-r--r-- 1 rogerb Administ 49152 Dec 23 2009 persist.fil -rw-r--r-- 1 rogerb Administ 2001 May 2 2009 sidlist.fil -rw-r--r-- 1 rogerb Administ 261 Apr 24 2009 wdptable1.fil -rw-r--r-- 1 rogerb Administ 261 Apr 24 2009 wdptable2.fil ./user: total 0 drwxr-xr-x 3 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 15 rogerb Administ 0 Oct 29 00:39 .. drwxr-xr-x 3 rogerb Administ 0 Oct 29 00:39 sound ./user/sound: total 0 drwxr-xr-x 3 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 3 rogerb Administ 0 Oct 29 00:39 .. drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 ringer ./user/sound/ringer: total 29 drwxr-xr-x 2 rogerb Administ 0 Oct 29 00:39 . drwxr-xr-x 3 rogerb Administ 0 Oct 29 00:39 .. -rw-r--r-- 1 rogerb Administ 2221 Sep 4 01:05 03 - only happy.mid -rw-r--r-- 1 rogerb Administ 1985 Sep 4 01:05 blank.mid -rw-r--r-- 1 rogerb Administ 18287 Sep 4 01:05 jamesbondtheme.mid -rw-r--r-- 1 rogerb Administ 3128 Sep 4 01:06 knightrider.mid -rw-r--r-- 1 rogerb Administ 3439 Sep 4 01:06 mi.mid -rw-r--r-- 1 rogerb Administ 12310 Sep 4 01:06 simpsons.mid -rw-r--r-- 1 rogerb Administ 5450 Sep 4 01:06 spiderwebs.mid -rw-r--r-- 1 rogerb Administ 2665 Sep 4 01:06 terminator.mid -rw-r--r-- 1 rogerb Administ 3477 Sep 4 01:06 whoopwhoop.mid |
From: Loren P. <mic...@us...> - 2003-10-29 08:23:39
|
Stephen, How do the phone commands that you're using to sync the phone book work? I'd be interested to hear about what you have figured out. Here's a listing of the files from my 8100. I haven't located any image files yet. I guess the nvm files seem like the most likely location. In particular, I have an nvm_0024, while your phone stops at 23. However, I uploaded some images from my phone, and tried to grep for patterns within the image file, and didn't find any matches. Perhaps the image files aren't stored as standard jpeg in the camera. loren $ ls -altrR .: total 11 -rw-r--r-- 1 Administ None 90 Oct 28 23:17 uivrState.dat drwxr-xr-x 4 Administ None 0 Oct 28 23:17 nvm drwxr-xr-x 4 Administ None 0 Oct 28 23:17 VoiceDB -rw-r--r-- 1 Administ None 6 Oct 28 23:17 RDM_PORT_MAP -rw-r--r-- 1 Administ None 44 Oct 28 23:17 POS_DB -rw-r--r-- 1 Administ None 1136 Oct 28 23:17 EPH_DB -rw-r--r-- 1 Administ None 64 Oct 28 23:17 CLK_DB -rw-r--r-- 1 Administ None 1056 Oct 28 23:17 ALM_DB drwxr-xr-x 3 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 4 Administ None 0 Oct 28 23:17 . -rw-r--r-- 1 Administ None 225 Oct 28 23:17 $USER_DIRS -rw-r--r-- 1 Administ None 188 Oct 28 23:17 $SYS_RMT -rw-r--r-- 1 Administ None 206 Oct 28 23:17 $SYS.FACTORY ./nvm: total 4 drwxr-xr-x 2 Administ None 0 Oct 28 23:17 prl drwxr-xr-x 2 Administ None 0 Oct 28 23:17 nvm drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 4 Administ None 0 Oct 28 23:17 . -rw-r--r-- 1 Administ None 107 Oct 28 23:17 $SYS.INVAR3 -rw-r--r-- 1 Administ None 135 Oct 28 23:17 $SYS.INVAR2 -rw-r--r-- 1 Administ None 193 Oct 28 23:17 $SYS.INVAR1 -rw-r--r-- 1 Administ None 97 Oct 28 23:17 $SYS.ESN ./nvm/prl: total 10 -rw-r--r-- 1 Administ None 4306 Oct 28 23:17 prl_0001 -rw-r--r-- 1 Administ None 4306 Oct 28 23:17 prl_0000 drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 2 Administ None 0 Oct 28 23:17 . ./nvm/nvm: total 379 -rw-r--r-- 1 Administ None 15668 Oct 28 23:17 nvm_0024 -rw-r--r-- 1 Administ None 29314 Oct 28 23:17 nvm_0023 -rw-r--r-- 1 Administ None 42208 Oct 28 23:17 nvm_0022 -rw-r--r-- 1 Administ None 41400 Oct 28 23:17 nvm_0021 -rw-r--r-- 1 Administ None 14234 Oct 28 23:17 nvm_0020 -rw-r--r-- 1 Administ None 1080 Oct 28 23:17 nvm_0019 -rw-r--r-- 1 Administ None 4115 Oct 28 23:17 nvm_0018 -rw-r--r-- 1 Administ None 6982 Oct 28 23:17 nvm_0017 -rw-r--r-- 1 Administ None 1765 Oct 28 23:17 nvm_0016 -rw-r--r-- 1 Administ None 6426 Oct 28 23:17 nvm_0015 -rw-r--r-- 1 Administ None 2100 Oct 28 23:17 nvm_0014 -rw-r--r-- 1 Administ None 10400 Oct 28 23:17 nvm_0013 -rw-r--r-- 1 Administ None 9888 Oct 28 23:17 nvm_0012 -rw-r--r-- 1 Administ None 4935 Oct 28 23:17 nvm_0011 -rw-r--r-- 1 Administ None 48200 Oct 28 23:17 nvm_0010 -rw-r--r-- 1 Administ None 48200 Oct 28 23:17 nvm_0009 -rw-r--r-- 1 Administ None 48200 Oct 28 23:17 nvm_0008 -rw-r--r-- 1 Administ None 3809 Oct 28 23:17 nvm_0005 -rw-r--r-- 1 Administ None 5 Oct 28 23:17 nvm_0004 -rw-r--r-- 1 Administ None 1524 Oct 28 23:17 nvm_0003 -rw-r--r-- 1 Administ None 716 Oct 28 23:17 nvm_0002 -rw-r--r-- 1 Administ None 31976 Oct 28 23:17 nvm_0001 -rw-r--r-- 1 Administ None 829 Oct 28 23:17 nvm_0000 drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 2 Administ None 0 Oct 28 23:17 . ./VoiceDB: total 0 drwxr-xr-x 4 Administ None 0 Oct 28 23:17 Lang drwxr-xr-x 3 Administ None 0 Oct 28 23:17 All drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 4 Administ None 0 Oct 28 23:17 . ./VoiceDB/Lang: total 0 drwxr-xr-x 2 Administ None 0 Oct 28 23:17 Spanish drwxr-xr-x 2 Administ None 0 Oct 28 23:17 English drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 4 Administ None 0 Oct 28 23:17 . ./VoiceDB/Lang/Spanish: total 32 -rw-r--r-- 1 Administ None 29320 Apr 10 2003 spadat_sd1.prm -rw-r--r-- 1 Administ None 2908 Apr 10 2003 spadat_sd1.dtw drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 2 Administ None 0 Oct 28 23:17 . ./VoiceDB/Lang/English: total 25 -rw-r--r-- 1 Administ None 21864 Apr 10 2003 engdat_sd1.prm -rw-r--r-- 1 Administ None 2908 Apr 10 2003 engdat_sd1.dtw drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 2 Administ None 0 Oct 28 23:17 . ./VoiceDB/All: total 0 drwxr-xr-x 2 Administ None 0 Oct 28 23:17 Patt drwxr-xr-x 4 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 3 Administ None 0 Oct 28 23:17 . ./VoiceDB/All/Patt: total 2 -rw-r--r-- 1 Administ None 0 Oct 28 23:17 NameTag.int -rw-r--r-- 1 Administ None 16 Oct 28 23:17 NameHdr.int -rw-r--r-- 1 Administ None 0 Oct 28 23:17 CtrlWrd.int -rw-r--r-- 1 Administ None 16 Oct 28 23:17 ComdHdr.int drwxr-xr-x 3 Administ None 0 Oct 28 23:17 .. drwxr-xr-x 2 Administ None 0 Oct 28 23:17 . Stephen Wood wrote: >On Tue, 2003-10-28 at 15:53, Loren Passmore wrote: > > >>Hi, >> >>Thanks to Roger's excellent help, I can report success in accessing the >>internal filesystem of the Sanyo SCP-8100. >>... >> >> > >Great News! > >I am working on adding support for the 4900 to Bitpim. The 4900, as far >as the phonebook, calendar, and call history appears to be identical for >both the 4900 and 8100. So far, the idea is to access the phone book >not through the nvm files, but rather through phone book commands (which >I understand is what the commercial sync programs use). But perhaps it >would be just as valid to read and write the nvm files (since Bitpim >supports that so well) instead of using the phone book commands. (Any >opinions on this Roger?) > >One question of interest to me (academic interest since I don't have a >camera phone) is whether or not Bitpim could easily be used to download >pictures taken with the SCP-8100 camera. Loren, do you see any thing >that looks like pictures you have taken in the filesystem you downloaded >from the phone? > >I have attached a listing of the filesytem from my 4900, I am curious >what differences there are in the filesystem between our two phones. I >would expect differences in the VoiceDB directory since I think that >directory contains voice dial phrases and memo. > > > >$ ls -alR >.: >total 40 >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 19 saw saw 8192 Oct 28 10:40 .. >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 nvm >-rw-rw-r-- 1 saw saw 5 Jan 18 2038 RDM_PORT_MAP >-rw-rw-r-- 1 saw saw 206 Jan 18 2038 $SYS.FACTORY >-rw-rw-r-- 1 saw saw 188 Jan 18 2038 $SYS_RMT >-rw-rw-r-- 1 saw saw 90 Jan 18 2038 uivrState.dat >-rw-rw-r-- 1 saw saw 219 Jan 18 2038 $USER_DIRS >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 VoiceDB > >./nvm: >total 28 >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 nvm >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 prl >-rw-rw-r-- 1 saw saw 97 Jan 18 2038 $SYS.ESN >-rw-rw-r-- 1 saw saw 193 Jan 18 2038 $SYS.INVAR1 >-rw-rw-r-- 1 saw saw 85 Jan 18 2038 $SYS.INVAR2 > >./nvm/nvm: >total 504 >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >-rw-rw-r-- 1 saw saw 595 Jan 18 2038 nvm_0000 >-rw-rw-r-- 1 saw saw 31976 Jan 18 2038 nvm_0001 >-rw-rw-r-- 1 saw saw 505 Jan 18 2038 nvm_0002 >-rw-rw-r-- 1 saw saw 1151 Jan 18 2038 nvm_0003 >-rw-rw-r-- 1 saw saw 5 Jan 18 2038 nvm_0004 >-rw-rw-r-- 1 saw saw 3168 Jan 18 2038 nvm_0005 >-rw-rw-r-- 1 saw saw 32770 Jan 18 2038 nvm_0006 >-rw-rw-r-- 1 saw saw 47200 Jan 18 2038 nvm_0007 >-rw-rw-r-- 1 saw saw 48200 Jan 18 2038 nvm_0008 >-rw-rw-r-- 1 saw saw 48200 Jan 18 2038 nvm_0009 >-rw-rw-r-- 1 saw saw 48200 Jan 18 2038 nvm_0010 >-rw-rw-r-- 1 saw saw 4935 Jan 18 2038 nvm_0011 >-rw-rw-r-- 1 saw saw 9888 Jan 18 2038 nvm_0012 >-rw-rw-r-- 1 saw saw 10400 Jan 18 2038 nvm_0013 >-rw-rw-r-- 1 saw saw 2100 Jan 18 2038 nvm_0014 >-rw-rw-r-- 1 saw saw 6426 Jan 18 2038 nvm_0015 >-rw-rw-r-- 1 saw saw 1287 Jan 18 2038 nvm_0016 >-rw-rw-r-- 1 saw saw 9749 Jan 18 2038 nvm_0017 >-rw-rw-r-- 1 saw saw 12081 Jan 18 2038 nvm_0018 >-rw-rw-r-- 1 saw saw 5386 Jan 18 2038 nvm_0019 >-rw-rw-r-- 1 saw saw 13854 Jan 18 2038 nvm_0020 >-rw-rw-r-- 1 saw saw 41400 Jan 18 2038 nvm_0021 >-rw-rw-r-- 1 saw saw 42208 Jan 18 2038 nvm_0022 >-rw-rw-r-- 1 saw saw 30295 Jan 18 2038 nvm_0023 > >./nvm/prl: >total 24 >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >-rw-rw-r-- 1 saw saw 4306 Jan 18 2038 prl_0000 >-rw-rw-r-- 1 saw saw 4306 Jan 18 2038 prl_0001 > >./VoiceDB: >total 16 >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 All >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 Lang > >./VoiceDB/All: >total 16 >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 Patterns >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 Tags > >./VoiceDB/All/Patterns: >total 20 >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >-rw-rw-r-- 1 saw saw 772 Jan 18 2038 CtrlWrd.int >-rw-rw-r-- 1 saw saw 4598 Jan 18 2038 NameTag.int > >./VoiceDB/All/Tags: >total 36 >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >-rw-rw-r-- 1 saw saw 4 Dec 21 2002 NextTag.int >-rw-rw-r-- 1 saw saw 555 Jun 29 08:27 Tag00005.tag >-rw-rw-r-- 1 saw saw 623 Aug 18 12:35 Tag00008.tag >-rw-rw-r-- 1 saw saw 589 Aug 18 12:36 Tag00009.tag >-rw-rw-r-- 1 saw saw 538 Aug 18 12:36 Tag00010.tag >-rw-rw-r-- 1 saw saw 708 Aug 26 22:17 Tag00013.tag >-rw-rw-r-- 1 saw saw 555 Aug 26 22:17 Tag00014.tag > >./VoiceDB/Lang: >total 16 >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 English >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 Spanish > >./VoiceDB/Lang/English: >total 36 >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >-rw-rw-r-- 1 saw saw 2908 Nov 11 2002 engdat_sd1.dtw >-rw-rw-r-- 1 saw saw 21512 Nov 11 2002 engdat_sd1.prm > >./VoiceDB/Lang/Spanish: >total 44 >drwxrwxr-x 2 saw saw 4096 Sep 30 00:11 . >drwxrwxr-x 4 saw saw 4096 Sep 30 00:11 .. >-rw-rw-r-- 1 saw saw 2908 Nov 11 2002 spadat_sd1.dtw >-rw-rw-r-- 1 saw saw 28968 Nov 11 2002 spadat_sd1.prm > > > > |