Menu
▾
▴
bitpim-devel
|
From: Roger B. <ro...@ro...> - 2004-04-30 06:14:15
|
> Spell beginning correctly. Gotta have standards :-) So the Sanyo really doesn't like duplicate names? BTW how do you identify entries. For example if you read in "John Doe" from the phone, change it to "Jane Doe" in BitPim and write back out again, do you do any correlation to the existing "John Doe"? (For the LG phones, each entry has a serial and the voice/speed dials are tagged to those. Consequently BitPim goes to great lengths to remember the serials and use them again on writing out. Note that the voice/speed dials are not part of the information you get when reading the phonebook). Roger |
|
From: Stephen W. <sa...@us...> - 2004-04-30 09:49:09
|
On Fri, 2004-04-30 at 02:14, Roger Binns wrote: > > Spell beginning correctly. > > Gotta have standards :-) I am now breaking the standard! > > > So the Sanyo really doesn't like duplicate names? No, the Sanyo is fine with duplicate names. It just needs to be told how to sort. When there was a duplicate, I would write N entries to the phone, but the tables that have the sort order would only have N-1 entries, causing the phone to do something funny when you try to look at entry N-1. I just didn't know how to sort lists with duplicates. > BTW how > do you identify entries. > For example if you read in "John Doe" > from the phone, change it to "Jane Doe" in BitPim and write back > out again, do you do any correlation to the existing "John Doe"? > 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. > (For the LG phones, each entry has a serial and the voice/speed > dials are tagged to those. Consequently BitPim goes to great > lengths to remember the serials and use them again on writing > out. Note that the voice/speed dials are not part of the > information you get when reading the phonebook). I read the speed dial information, but not the voice dial. Stephen |
|
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: 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-06 00:20:54
|
Stephen Wood wrote: > 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. Yes, can add something sensible to the spec at the top of phonebook.py. Also feel free to add your AI voice recognition wherever you want :-) It seems like the LG and Audiovox and even the Sanyos all use the same voice recognition code. I think the .tag files are actually just the data portion of a .qcp file. (The phone can play the voice dial back at you so it must be storing the full stream rather than a set of data points for recognition). If anyone is interested, I can point you at the relevant pieces to investigate this. Roger |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X