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: Peter D. <du...@hd...> - 2004-05-03 20:53:53
|
On May 3, 2004, at 4:05 PM, Roger Binns wrote: > LG VX4500: > > - Phonebook needs to be deciphered > - Calendar needs verification > - Complete list of media locations and index files (eg MMS) Hello Roger - I'm more than a little technically oriented and I just got a LG4500 and data cable as my son dropped my good 'ol star-tac in a cup of soda last week. A few months ago I used BitPim to set up my father-in-law's LG4400 with great success. Unfortunately, I'm pretty busy right now. That said, I'm more than happy to spend up to 1/2 hour in the morning and also up to 1/2 hour at the end of the day setting up bitfling experiments, reporting back results, doing well-defined tests, answering questions, etc. I've already installed the developer version and I'm cvs'ing each day (I'm in GMT+5). My usual working systems are OS X, FreeBSD, and reluctantly Win-XP, and all are on-line. I can boot up and work with Linux, but that will eat-up my Bitpim time budget. Given those restrictions, feel free to ask for any LG4500 help. I'll help out more when I can - Peter Peter Dufault HD Associates, Inc. |
From: Adit P. <apa...@ba...> - 2004-05-03 20:37:15
|
Good to hear. I did re-inspect my changes and found that the Quit command was showing up on the File menu. I made the necessary fix and it should now only show up on the Application menu (with the File menu command and separator removed). I was also wondering what would be the status for accelerator keys? Is that something to be implemented down the road? As to my CVS export code, it is coming along - I am currently trying to figure out how to write the phonebook dict to a list or lists. The exportDSV function expects a list and I was stepping through the existing code trying to figure out the best way to get the data out into a usable form. Adit |
From: Dale B. <bi...@da...> - 2004-05-03 20:27:22
|
On Mon, 2004-05-03 at 16:05, Roger Binns wrote: > If you own one of the phone models listed below and would like > to help BitPim better support your phone, then please read-on. > Oops, repost from the right address. Admin: please delete the other post if possible. I'll volunteer for the CDM8900. I'm guessing this needs to be more-real time than email and that we won't want to clutter the lists with info from individual phones, not to mention the privacy issue.... Where do we go from here? -Dale > Audiovox CDM8900: > > - The new phonebook code needs to be tested > - Information is needed about media locations and > index files > > Roger |
From: Roger B. <ro...@ro...> - 2004-05-03 20:23:56
|
Steven Palm wrote: > I was aware of that and at this point I was straddling the line > between having things be in the same place on each version and being > "Mac-like". I guess you've pushed me over to be more "Mac-like", so > I'll put the changes in. ;-) My preference is for the program to behave as the users on each platform expect and consider normal. For most, the fact that it is available for other platforms is irrelevant and I don't see much value in making it behave in a lowest common denominator fashion. That said, as a developer I prefer as little platform specific code as possible as it is more difficult to maintain. However the usability experience ultimately trumps the developer experience in my book. Roger |
From: Roger B. <ro...@ro...> - 2004-05-03 20:05:46
|
If you own one of the phone models listed below and would like to help BitPim better support your phone, then please read-on. You will need to have time to dedicate to this. You will need to be run the developer version of BitPim. The details to get up and going are at http://bitpim.sourceforge.net/developer.html You should be somewhat midly technical. In particular, you should be able to find your way around the protocol analyser. (Turn on protocol logging, do something, then press Ctrl-Alt-P in the protocol log pane). The expected method of progress is that a developer will make some changes, you do a cvs update and check to see if they work correctly. You may need to look in the protocol analyser to see if the various fields are being decoded properly and are the right size. Provide the feedback and repeat the loop. You may need to do things like create dummy phonebook entries and look at how they are being decoded, or add and remove ringtones, wallpaper and calendar entries. If noone steps forward for you model of phone, then progress will be very slow or non-existent. Having more than one person will be really great since that way we can better verify the code works correctly (having a sample of only one phone isn't too goood a test). LG VX4500: - Phonebook needs to be deciphered - Calendar needs verification - Complete list of media locations and index files (eg MMS) LG VX4600: - Phonebook needs to be deciphered - Calendar needs verification - The new media code needs checking Audiovox CDM8900: - The new phonebook code needs to be tested - Information is needed about media locations and index files Roger |
From: Roger B. <ro...@ro...> - 2004-05-03 17:45:45
|
Chris Poon wrote: > I believe if you have the latest files I have sent about a month ago, that > would be the latest updates where practically everything should work - the > only thing that doesn't was re-assigning the speed dial, as I couldn't get > the phone to change that without deleting and re-creating the entry. Can you email me the files you want re-instated? Roger |
From: Chris P. <dev...@te...> - 2004-05-03 17:03:38
|
I believe if you have the latest files I have sent about a month ago, that would be the latest updates where practically everything should work - the only thing that doesn't was re-assigning the speed dial, as I couldn't get the phone to change that without deleting and re-creating the entry. |
From: ray c. <bi...@ra...> - 2004-05-03 16:15:31
|
in the bitpim-devel archives, i see a message from Dustin Sacks (<http://sourceforge.net/mailarchive/message.php?msg_id=7118427>) from january of this year regarding development for the audiovox 9900. i was wondering if any progress had been made and what was left to work out. my cable is on its way and am excited to make bitpim work for yet another phone. any info would be helpful. thanks, /rayc |
From: Steven P. <n9...@n9...> - 2004-05-03 14:33:58
|
On May 3, 2004, at 1:07 AM, Roger Binns wrote: > I would really love it if someone who is familiar with wxWidgets/ > wxPython could complete the hexeditor. It is needed by several > bits of code. For ideas/etc, here is another hex editor in Python that is under the Python license: http://homepage.hispeed.ch/py430/python/ I have only looked at it briefly... It doesn't run quite properly under MacOS X, but I'm sure that it could be fixed, and if you use it to flesh out the current editor then maybe the bad bits won't come along with it. :-) (Actually, the initial error was due to the assumption that locale.getdefaultlocale() returned a valid set of languages, on the Mac it returns None, so it was easy to work around that, but visually it need a bit of TLC on the Mac). |
From: Steven P. <n9...@n9...> - 2004-05-03 14:08:34
|
On May 3, 2004, at 12:52 AM, Roger Binns wrote: > Adit Panchal wrote: >> Anyways, I think if this code is added, it would make the Mac build >> feel more conforming with the OS. > > Steven deals with the Mac side so we will get feedback from him soon. I was aware of that and at this point I was straddling the line between having things be in the same place on each version and being "Mac-like". I guess you've pushed me over to be more "Mac-like", so I'll put the changes in. ;-) |
From: Roger B. <ro...@ro...> - 2004-05-03 06:07:40
|
I would really love it if someone who is familiar with wxWidgets/ wxPython could complete the hexeditor. It is needed by several bits of code. The file is standalone in hexeditor.py, and what I need is an edit mode. The idea is that the current byte should be highlighted. Pressing tab should jump between the hex bytes side and the ascii side. It should be able to be in insert mode or overwrite mode. There is a status line at the bottom that is shown when the widget has focus, and the idea is that will tell you if you are in insert mode or overwrite mode, and potentially other information (eg decimal value of byte at cursor). Please let us know if you can work on this in the near future. Roger |
From: Roger B. <ro...@ro...> - 2004-05-03 06:00:57
|
> Sometimes the length byte is not adjacent to the > string, but after a whole bunch of other things, like it was added as an > afterthought. I think the firmware engineers could quite easily write a book called 101 Ways to encode a string! > The Sanyo is like this. Packets are 505 bytes, not including checksum > and framing byte. For the newer phones, the packet size went to over > 1000, although, in most cases the extra 500 bytes are never used. But > for these newer phones, the packet sent to the phone does not need to > match in size any more. The Audiovox has different sized packets depending on the command. I also did some experiments and it turns out I don't need to do the silly padding. The sync tool I sniffed did that so maybe it is a constraint only of the earlier phones. I also tried sending packets that were too small (eg used a one byte slot number instead of two) and you get back pseudo-valid junk. > > It also has no error codes. > Sanyo has an error code if you send it a packet that doesn't have the > right size or is otherwise bad. It sends back a small packet with Y (I > think) as the first character and a fragment of the packet sent to it. Packets begining with 'Y' (0x59) are Brew packets. The second byte is the command and the third byte is the error code. > For Sanyos, if the slot has been previously used, you get the old data, > otherwise zeros. So if you delete entries on the phone, you could > potentially recover them. (Or someone else could!) The PC-Sync software I am sniffing requires you to connect to the phone and supply the security code. Of course you don't really need it to read entries. If you are bored, try sending 0x26 0x52 as a packet and see what you get. I have also just renamed several pieces in the Audiovox code to use the same terminology as you (ie "slots"). > > It still boggles my mind > > how badly written the embedded software is in these phones. > At least all these phones share the same HDLC framing. They also all use LSB integers. Roger |
From: Roger B. <ro...@ro...> - 2004-05-03 05:53:00
|
Stephen Wood wrote: > On Sun, 2004-05-02 at 04:15, Roger Binns wrote: > > For those who are curious (eg Stephen :-) the phone has 300 slots > > available for phonebook entries. There is one request to get a listing > > of which slots are in use (with a byte per slot, a non-zero value in > > the byte). It also has yet another silly way of encoding strings > > for the phone numbers (other strings use a different mechanism). > > There is a count byte, followed by a fix sized buffer. The count > > says how many of the bytes make up the string. > The Sanyo strings are fixed length fields and most have a length byte. > I ignore the length on reading, because the strings are always null > padded if less than the field length. (Of course on writes, the length > has to be computed.) Sometimes the length byte is not adjacent to the > string, but after a whole bunch of other things, like it was added as an > afterthought. > > > > It also uses a > > scheme where if a response is 123 bytes, you have to send a 123 byte > > request (ie requests must be the same size as the expected response). > The Sanyo is like this. Packets are 505 bytes, not including checksum > and framing byte. For the newer phones, the packet size went to over > 1000, although, in most cases the extra 500 bytes are never used. But > for these newer phones, the packet sent to the phone does not need to > match in size any more. > > > It also has no error codes. > Sanyo has an error code if you send it a packet that doesn't have the > right size or is otherwise bad. It sends back a small packet with Y (I > think) as the first character and a fragment of the packet sent to it. > > > If you ask for a slot that has nothing > > in it, you get almost random data back. > For Sanyos, if the slot has been previously used, you get the old data, > otherwise zeros. So if you delete entries on the phone, you could > potentially recover them. (Or someone else could!) > > > The same is true of > > padding in the strings. (If it was actually using the buffer > > I sent, I would have expected nulls). > Fortunately, my strings are null padded. > > > It still boggles my mind > > how badly written the embedded software is in these phones. > At least all these phones share the same HDLC framing. > > I may have a Samsung phone to play with soon. We'll see how it's > weirdness compares to what we know so far. > > Stephen > > > > > Roger > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel |
From: Roger B. <ro...@ro...> - 2004-05-03 05:52:25
|
Adit Panchal wrote: > Anyways, I think if this code is added, it would make the Mac build > feel more conforming with the OS. Steven deals with the Mac side so we will get feedback from him soon. > I am currently trying to work on exporting the phonebook to a CSV. If > it is not necessary, please let me know. A lot of people have asked for it :-) I would love for someone to deal with all the import and export code. I would also prefer if you give us patches early and frequently. That way others can help and provide feedback. (My main rule is that the software should not be stupid. I also have an idea in my head as to how this stuff should work, but code rules over talk :-) Roger |
From: Adit P. <apa...@ba...> - 2004-05-02 20:21:46
|
I was tinkering around with the code and realized that on the Mac, that some of the standard menus aren't in the right places (i.e, About and Preferences). I wrote some additional code that fixes the About menu position and removes the separator bar if it is run on a Mac. I also tried doing the Preferences, but for the life of me, I couldn't get it to work on this code. I hacked up another Python script that just sets up menus and added the Mac specific code there and it worked perfectly. For some reason the Preferences setting does not work with the BitPim code. Anyways, I think if this code is added, it would make the Mac build feel more conforming with the OS. Attached is my diff. If anyone wants my test code, please let me know and I can send it. I am currently trying to work on exporting the phonebook to a CSV. If it is not necessary, please let me know. Thanks for the good work :) Index: gui.py =================================================================== RCS file: /cvsroot/bitpim/bitpim/gui.py,v retrieving revision 1.124 diff -u -r1.124 gui.py --- gui.py 1 May 2004 07:57:49 -0000 1.124 +++ gui.py 2 May 2004 19:41:21 -0000 @@ -407,7 +407,11 @@ menu.AppendSeparator() menu.Append(guihelper.ID_FV_ICONS, "View as Images", "Show items as images") menu.Append(guihelper.ID_FV_LIST, "View As List", "Show items as a report") - menu.AppendSeparator() + if guihelper.IsMac(): + wx.App_SetMacPreferencesMenuItemId(guihelper.ID_EDITSETTINGS) + print wx.App_GetMacPreferencesMenuItemId() + else: + menu.AppendSeparator() menu.Append(guihelper.ID_EDITSETTINGS, "&Settings", "Edit settings") menuBar.Append(menu, "&Edit"); @@ -427,10 +431,20 @@ menu=wx.Menu() - menu.Append(guihelper.ID_HELPHELP, "&Help", "Help for the panel you are looking at") + if guihelper.IsMac(): + menu.Append(guihelper.ID_HELPHELP, "&BitPim Help", "Help for the panel you are looking at") + menu.AppendSeparator() + else: + menu.Append(guihelper.ID_HELPHELP, "&Help", "Help for the panel you are looking at") menu.Append(guihelper.ID_HELPTOUR, "&Tour", "Tour of BitPim") menu.Append(guihelper.ID_HELPCONTENTS, "&Contents", "Table of contents for the online help") - menu.AppendSeparator() + if guihelper.IsMac(): + wx.App_SetMacAboutMenuItemId(guihelper.ID_HELPABOUT) + wx.App_SetMacHelpMenuTitleName("&Help") + wx.App_SetMacExitMenuItemId(guihelper.ID_FILEEXIT) + #print wx.App_GetMacAboutMenuItemId() + else: + menu.AppendSeparator() menu.Append(guihelper.ID_HELPABOUT, "&About", "Display program information") menuBar.Append(menu, "&Help"); |
From: Stephen W. <sa...@us...> - 2004-05-02 19:32:43
|
Great! The 7300 and 5400 are the two phones I am most anxious to bitfling to as they are the ones I broke for 0.7test9. I'll send you my IM names privately. Stephen On Sun, 2004-05-02 at 00:03, John Camin wrote: > >There are a number of details of Sanyo Phones, that I don't have, that I > >would like to work. I am looking for few volunteers to make their > >phones available to me via BitPim. The phones that I would like to > >BitFling to are: ... > > I'm swamped the next two-three days, but sometime after that we can try to > fling the 5400 & 7300 when your ready. Do you have an MSN account too? If > not I'll make a yahoo one. > > -John |
From: Stephen W. <sa...@us...> - 2004-05-02 19:32:27
|
On Sun, 2004-05-02 at 04:15, Roger Binns wrote: > For those who are curious (eg Stephen :-) the phone has 300 slots > available for phonebook entries. There is one request to get a listing > of which slots are in use (with a byte per slot, a non-zero value in > the byte). It also has yet another silly way of encoding strings > for the phone numbers (other strings use a different mechanism). > There is a count byte, followed by a fix sized buffer. The count > says how many of the bytes make up the string. The Sanyo strings are fixed length fields and most have a length byte. I ignore the length on reading, because the strings are always null padded if less than the field length. (Of course on writes, the length has to be computed.) Sometimes the length byte is not adjacent to the string, but after a whole bunch of other things, like it was added as an afterthought. > It also uses a > scheme where if a response is 123 bytes, you have to send a 123 byte > request (ie requests must be the same size as the expected response). The Sanyo is like this. Packets are 505 bytes, not including checksum and framing byte. For the newer phones, the packet size went to over 1000, although, in most cases the extra 500 bytes are never used. But for these newer phones, the packet sent to the phone does not need to match in size any more. > It also has no error codes. Sanyo has an error code if you send it a packet that doesn't have the right size or is otherwise bad. It sends back a small packet with Y (I think) as the first character and a fragment of the packet sent to it. > If you ask for a slot that has nothing > in it, you get almost random data back. For Sanyos, if the slot has been previously used, you get the old data, otherwise zeros. So if you delete entries on the phone, you could potentially recover them. (Or someone else could!) > The same is true of > padding in the strings. (If it was actually using the buffer > I sent, I would have expected nulls). Fortunately, my strings are null padded. > It still boggles my mind > how badly written the embedded software is in these phones. At least all these phones share the same HDLC framing. I may have a Samsung phone to play with soon. We'll see how it's weirdness compares to what we know so far. Stephen > > Roger > |
From: Roger B. <ro...@ro...> - 2004-05-02 08:15:10
|
The code in CVS can now read the CDM8900 phonebook. If you have a 8900, please try it out. (You won't hurt your phone). There are two fields whose values don't quite make sense. Turn on protocol logging, read your phonebook, and then press Ctrl-Alt-P in the log pane. Look for ones where the class ends in readpbentryresponse (they are of size 344) and come just before an entry saying "Read entry 9 - a name". In the middle pane, open the tree view. The two fields are the ones I marked as previous and next. They mostly seem to point to the previous and next entry/slot numbers on the phone display (ie control the sort order). They were perfectly in tune with the sort order for me until I started screwing with phonebook entries (adding/removing some, setting entries to secret) at which point many seemed to point to 0xffff. I would be interested in thoughts on what they could be. For those who are curious (eg Stephen :-) the phone has 300 slots available for phonebook entries. There is one request to get a listing of which slots are in use (with a byte per slot, a non-zero value in the byte). It also has yet another silly way of encoding strings for the phone numbers (other strings use a different mechanism). There is a count byte, followed by a fix sized buffer. The count says how many of the bytes make up the string. It also uses a scheme where if a response is 123 bytes, you have to send a 123 byte request (ie requests must be the same size as the expected response). It also has no error codes. If you ask for a slot that has nothing in it, you get almost random data back. The same is true of padding in the strings. (If it was actually using the buffer I sent, I would have expected nulls). It still boggles my mind how badly written the embedded software is in these phones. Roger |
From: John C. <ra...@ho...> - 2004-05-02 04:04:45
|
>There are a number of details of Sanyo Phones, that I don't have, that I >would like to work. I am looking for few volunteers to make their >phones available to me via BitPim. The phones that I would like to >BitFling to are: ... I'm swamped the next two-three days, but sometime after that we can try to fling the 5400 & 7300 when your ready. Do you have an MSN account too? If not I'll make a yahoo one. -John _________________________________________________________________ Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362ave/direct/01/ |
From: Alan G. <ago...@ya...> - 2004-05-02 00:02:44
|
I don't have a problem with the code going under the GPL. I thought the problem was it wasn't actively supported. I'm all for the GPL, so putting it bcak in the tree would be great. Alan --- Roger Binns <ro...@ro...> wrote: > Alan Gonzalez wrote: > > I've got the code for a prior version. I'll send them to you directly. > > The problem with the TM520 code was that it wasn't completed/kept up > to date, and it wasn't relicensed when we moved to the GPL. The > copyright on the code is jointly mine, yours and Scott Craig. I > have Scott's permission to "do anything I want". If you agree to > your bits going under the GPL, then I can put the code back in the > tree. I won't list it as supported or allow it to be selected > until someone actually brings the code up to date. > > Roger > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover |
From: Stephen W. <sa...@us...> - 2004-05-01 13:25:36
|
On Sat, 2004-05-01 at 04:16, Roger Binns wrote: > > There is no serial number like the LG phones. There is a slot number, > > 0-299. I put that slot number in the serial1 field. When writing out, > > I use that number as the slot, if it is in range. Otherwise I pick an > > unused slot. So, I think if I read "John Doe", edit it, and write it > > back out, it will go into the same slot. If I delete it in BitPim, then > > create a new "John Doe", it won't necessarily go back to the same slot. > > So if I understand this correctly the slots can be unused or have > an entry, and there can be holes. A seperate location lists what > order to show the slots in. Yes. (I call them slots because that what the qcplink code does.). These buffers that I read/write contain a list of which slots are active, the sort order, lists of what ringers/wallpapers are assigned to each slot, and a caller id index.. The phones can keep the phonebook sorted as you add and remove entries, but can't resort should you mess things by writing to the phone with a cable. (Once, long before my BitPim involvment, I messed up the caller id buffer using a commercial sync program. I had to delete and recreate entries until things were reasonably right again. BitPim won't let that happen.) > > > I read the speed dial information, but not the voice dial. > > Does the voice dial point to a particular slot, or is it more > deep and meaningful than that? > There are 30 slots/memory locations for voice dial. These slots are simple. (See voicedial packetdefs in p_sanyo.p) A slot contains a flag saying whether or not that voice slot is in use and a pointer to the specific phone number (slot, phone num type) that it goes to. I believe, but have not verified that the slot number corresponds to a file on the file system (VoiceDB/All/Tags/Tag000NN.tag) One thing I don't do is disable a voice dial slot when the phone number that it points to goes away. So if I my phone programed to dial work when I say "Work", then use BitPim to delete the entry to work, and then write back to the phone, saying "Work" will probably still dial the same number. (Because the slot containing the phone number doesn't get deleted, just turned off) Clearly, what BitPim should do is read the encoded speech, do untrained speech recognition on it and then display the speech as text next to the the phone number it goes to (insert appropirate smiley here). But it should at least handle deleted numbers OK. Can I put a voice dial attribute into numbers like speeddial. It doesn't have to be displayed by any GUI, but has to be saved until a number gets deleted. Stephen > Roger |
From: Roger B. <ro...@ro...> - 2004-05-01 08:16:35
|
> There is no serial number like the LG phones. There is a slot number, > 0-299. I put that slot number in the serial1 field. When writing out, > I use that number as the slot, if it is in range. Otherwise I pick an > unused slot. So, I think if I read "John Doe", edit it, and write it > back out, it will go into the same slot. If I delete it in BitPim, then > create a new "John Doe", it won't necessarily go back to the same slot. So if I understand this correctly the slots can be unused or have an entry, and there can be holes. A seperate location lists what order to show the slots in. > I read the speed dial information, but not the voice dial. Does the voice dial point to a particular slot, or is it more deep and meaningful than that? Roger |
From: Roger B. <ro...@ro...> - 2004-05-01 08:09:17
|
I have committed code that works for me when testing on the VX6000 (the phone just ignores it - I am using the directory structure). When reading from the phone, BitPim automatically adds an extension to the directory name to name the resulting file. When writing back again, the extension is stripped to come up with the directory name and the mime-type deduced from the extension. This basically means you can just use ordinary files with BitPim and the right thing happens. You need to do the following: - Test and verify things work for you. I tested adding, replacing and reading - Get a full complete listing of what the phone expects for mime-types. Some of these are not standard. This is what I use so far: __mimetoextensionmapping={ 'image/jpg': '.jpg', 'image/bmp': '.bmp', 'image/png': '.png', 'image/gif': '.gif', 'image/bci': '.bci', 'audio/mp3': '.mp3', 'audio/mid': '.mid', 'audio/qcp': '.qcp' } - Is there a maximum number of wallpapers or ringtones that can be made? [The code currently sets a limit of 30 which is the same as other LG phones, but they have a fixed sized index file] - In conjunction with the next bit, work out what number is added to a wallpaper or ringtone index to store it in the phonebook. For example, the builtin image 'Butterfly' will be stored as zero. If you have added a wallpaper with index value of 3, what is it stored as in the phonebook. On other LG phones, they add 50, so it would be stored as 53. - Start working on the phonebook. Add an entry where you fill out each field to the maximum possible length. Read the phonebook with protocol logging turned on. Find that entry in the protocol log, highlight the whole packet and press Ctrl-Alt-P. Check the decoding of the fields. The description is in pbentry in p_lgvx4600.p. That is what will need to be changed to get things right. When you get to this stage tell me and I will give more detailed instructions. Roger |
From: Roger B. <ro...@ro...> - 2004-05-01 05:35:29
|
> Can you please send me a single zip containing several wallpapers > and ringtones? Makes it a lot easier to test and work with. Also please include a variety of different types. I also need information on the longest filename lengths allowed as well as the correct image size. Also, what are the correct mime-types? The golf2 file says image/jpg, but the correct type for jpeg is actually image/jpeg. It also crashed the phone (VX6000) when I created the usr/Ringtone/Galaga directory on it. The phone refused to respond, and then I rebooted it. Somehow it had mapped the diag port elsewhere. I had to read the contents of a different directory before I could read the contents of the root directory. The code in these phones must just barely be functional. Roger |
From: Roger B. <ro...@ro...> - 2004-05-01 05:07:04
|
Dale wrote: > The location of the ringers is: > /usr/Ringtone/(name of folder) example /usr/Ringtone/Galaga > > The Location of the wallpapers is: > /usr/Wallpaper(name of folder) example /usr/Wallpaper/Golf2 Can you please send me a single zip containing several wallpapers and ringtones? Makes it a lot easier to test and work with. Roger |