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: Dale <dri...@te...> - 2004-05-12 16:50:04
|
Hi Roger, I started looking into the phone book stuff. I did what you said and looking at the protocal logging I get an error after reading the first entry in the phone book.The error is 'pbentry' object has no attribute '_pbentry__field_serial2' -----Original Message----- From: bit...@li... [mailto:bit...@li...] On Behalf Of Roger Binns Sent: Wednesday, May 05, 2004 4:58 PM To: bit...@li... Subject: Re: [Bitpim-devel] Fw: VX4600 support > > - 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-12 15:48:01
|
Dale wrote: > How do I find out which types are available? Just by trying the different > extensions out? BY scoouring the web and by trying them. > Here is a site that uses bitpim to add custom wallpapers and ringtones > manually. http://24.83.225.6/html/modules.php?name=Content&pa=showpage&pid=1 That is pretty much what I worked from and what BitPim now does, but I still need all the other information. You may want to join those forums and ask other people there to help. The other part of my message that you quoted is the remaining information I need. Roger |
From: Dale <dri...@te...> - 2004-05-12 14:41:47
|
Hi Roger, I just want to confirm what the information that you are looking for: How do I find out which types are available? Just by trying the different extensions out? Here is a site that uses bitpim to add custom wallpapers and ringtones manually. http://24.83.225.6/html/modules.php?name=Content&pa=showpage&pid=1 - 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. -----Original Message----- From: bit...@li... [mailto:bit...@li...] On Behalf Of Roger Binns Sent: Friday, May 07, 2004 8:01 AM To: bit...@li... Subject: Re: [Bitpim-devel] VX4600 support Dale wrote: > I don't think that will happen, I am at work and they have a strict > policy on that also I don't have a yahoo messenger account. I would expect it to happen when you are at home, not at work. Anyway, I do need the information requested to make any further progress. Roger ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ Bitpim-devel mailing list Bit...@li... https://lists.sourceforge.net/lists/listinfo/bitpim-devel |
From: Steven P. <n9...@n9...> - 2004-05-12 13:51:45
|
Or I get this: (I may be going blind, but I can't determine what port it's using here either, should I be able to?) An unexpected exception has occurred. Please see the help for details on what to do. Traceback (most recent call last): File "/usr/local/src/bitpim/bitpim/gui.py", line 152, in run res=call() File "/usr/local/src/bitpim/bitpim/gui.py", line 92, in __call__ return apply(self.method, self.args+args, d) File "/usr/local/src/bitpim/bitpim/gui.py", line 1106, in getdata results=self.getfundamentals() File "/usr/local/src/bitpim/bitpim/gui.py", line 1100, in getfundamentals self.commphone.getfundamentals(results) File "/usr/local/src/bitpim/bitpim/com_lgvx4400.py", line 89, in getfundamentals results['uniqueserial']=sha.new(self.getfilecontents("nvm/ $SYS.ESN")).hexdigest() File "/usr/local/src/bitpim/bitpim/com_brew.py", line 221, in getfilecontents res=self.sendbrewcommand(req, p_brew.readfileresponse) File "/usr/local/src/bitpim/bitpim/com_brew.py", line 300, in sendbrewcommand self.setmode(self.MODEBREW) File "/usr/local/src/bitpim/bitpim/com_phone.py", line 100, in setmode res=getattr(self, func)() File "/usr/local/src/bitpim/bitpim/com_brew.py", line 262, in _setmodebrew self.sendbrewcommand(req, respc, callsetmode=False) File "/usr/local/src/bitpim/bitpim/com_brew.py", line 348, in sendbrewcommand if data[0]=="Y" and data[2]!="\x00": # Y is 0x59 which is brew command prefix IndexError: string index out of range Variables by last 8 frames, innermost last Frame getdata in /usr/local/src/bitpim/bitpim/gui.py at line 1106 self = <WorkerThread(BitPim helper, started daemon)> req = <guiwidgets.GetPhoneDialog instance; proxy of C++ wxDialog instance at _6f400e0_ Frame getfundamentals in /usr/local/src/bitpim/bitpim/gui.py at line 1100 self = <WorkerThread(BitPim helper, started daemon)> results = {} Frame getfundamentals in /usr/local/src/bitpim/bitpim/com_lgvx4400.py at line 89 self = <com_lgvx6000.Phone instance at 0x8636fa8> results = {} Frame getfilecontents in /usr/local/src/bitpim/bitpim/com_brew.py at line 221 self = <com_lgvx6000.Phone instance at 0x8636fa8> req = <p_brew.readfilerequest object at 0x8633d90> start = 1084369769.946929 file = 'nvm/$SYS.ESN' data = <cStringIO.StringO object at 0x83855e0> desc = 'Reading nvm/$SYS.ESN' Frame sendbrewcommand in /usr/local/src/bitpim/bitpim/com_brew.py at line 300 callsetmode = True request = <p_brew.readfilerequest object at 0x8633d90> self = <com_lgvx6000.Phone instance at 0x8636fa8> responseclass = <class 'p_brew.readfileresponse'> Frame setmode in /usr/local/src/bitpim/bitpim/com_phone.py at line 102 desiredmode = 'modebrew' self = <com_lgvx6000.Phone instance at 0x8636fa8> strmode = 'none' strdesiredmode = 'brew' func = '_setmodebrew' v = 'writefile' Frame _setmodebrew in /usr/local/src/bitpim/bitpim/com_brew.py at line 265 baud = 0 self = <com_lgvx6000.Phone instance at 0x8636fa8> req = <p_brew.memoryconfigrequest object at 0x8633db0> respc = <class 'p_brew.memoryconfigresponse'> Frame sendbrewcommand in /usr/local/src/bitpim/bitpim/com_brew.py at line 348 origdata = 'Y\x0c\xc4\xc1~' d = 0 responseclass = <class 'p_brew.memoryconfigresponse'> buffer = <prototypes.buffer instance at 0x8393f30> request = <p_brew.memoryconfigrequest object at 0x8633db0> callsetmode = False firsttwo = 'Y\x0c' crc = '\xc4\xc1' data = 'Y\x0c' self = <com_lgvx6000.Phone instance at 0x8636fa8> |
From: Steven P. <n9...@n9...> - 2004-05-12 13:38:04
|
I haven't *used* BitPim for a while, but I wanted to test out the prlbme reported with the window sizing so I fired it up and tried to read in my VX6000: An unexpected exception has occurred. Please see the help for details on what to do. Traceback (most recent call last): File "/usr/local/src/bitpim/bitpim/gui.py", line 152, in run res=call() File "/usr/local/src/bitpim/bitpim/gui.py", line 92, in __call__ return apply(self.method, self.args+args, d) File "/usr/local/src/bitpim/bitpim/gui.py", line 1105, in getdata results=self.getfundamentals() File "/usr/local/src/bitpim/bitpim/gui.py", line 1099, in getfundamentals self.commphone.getfundamentals(results) File "/usr/local/src/bitpim/bitpim/com_lgvx4400.py", line 89, in getfundamentals results['uniqueserial']=sha.new(self.getfilecontents("nvm/ $SYS.ESN")).hexdigest() File "/usr/local/src/bitpim/bitpim/com_brew.py", line 221, in getfilecontents res=self.sendbrewcommand(req, p_brew.readfileresponse) File "/usr/local/src/bitpim/bitpim/com_brew.py", line 300, in sendbrewcommand self.setmode(self.MODEBREW) File "/usr/local/src/bitpim/bitpim/com_phone.py", line 100, in setmode res=getattr(self, func)() File "/usr/local/src/bitpim/bitpim/com_brew.py", line 281, in _setmodebrew if self.comm.readsome().find("OK")>=0: File "/usr/local/src/bitpim/bitpim/commport.py", line 227, in readsome b=self.ser.inWaiting() AttributeError: _usbdevicewrapper instance has no attribute 'inWaiting' Variables by last 8 frames, innermost last Frame getdata in /usr/local/src/bitpim/bitpim/gui.py at line 1105 self = <WorkerThread(BitPim helper, started daemon)> req = <guiwidgets.GetPhoneDialog instance; proxy of C++ wxDialog instance at _703f840_ Frame getfundamentals in /usr/local/src/bitpim/bitpim/gui.py at line 1099 self = <WorkerThread(BitPim helper, started daemon)> results = {} Frame getfundamentals in /usr/local/src/bitpim/bitpim/com_lgvx4400.py at line 89 self = <com_lgvx6000.Phone instance at 0x687cf80> results = {} Frame getfilecontents in /usr/local/src/bitpim/bitpim/com_brew.py at line 221 self = <com_lgvx6000.Phone instance at 0x687cf80> req = <p_brew.readfilerequest object at 0x86ad6d0> start = 1084368887.4033 file = 'nvm/$SYS.ESN' data = <cStringIO.StringO object at 0x86ada40> desc = 'Reading nvm/$SYS.ESN' Frame sendbrewcommand in /usr/local/src/bitpim/bitpim/com_brew.py at line 300 callsetmode = True request = <p_brew.readfilerequest object at 0x86ad6d0> self = <com_lgvx6000.Phone instance at 0x687cf80> responseclass = <class 'p_brew.readfileresponse'> Frame setmode in /usr/local/src/bitpim/bitpim/com_phone.py at line 102 desiredmode = 'modebrew' self = <com_lgvx6000.Phone instance at 0x687cf80> strmode = 'none' strdesiredmode = 'brew' func = '_setmodebrew' v = 'writefile' Frame _setmodebrew in /usr/local/src/bitpim/bitpim/com_brew.py at line 284 baud = 0 self = <com_lgvx6000.Phone instance at 0x687cf80> req = <p_brew.memoryconfigrequest object at 0x86ad490> respc = <class 'p_brew.memoryconfigresponse'> Frame readsome in /usr/local/src/bitpim/bitpim/commport.py at line 227 res = '' self = <commport.CommConnection instance at 0x687cee0> log = True |
From: Peter D. <du...@hd...> - 2004-05-12 12:56:50
|
I wanted to go further with the calendar on the VX4500 based on the=20 hexdump I posted yesterday of the calendar entry file. I copied the schedule section from the vx4400 to the vx4500 .p file and=20= then modified scheduleevent as follows: from: PACKET scheduleevent: 4 UINT pos "position within file, used as an event id" 4 LGCALDATE start 4 LGCALDATE end 1 UINT repeat 3 UINT daybitmap "which days a weekly repeat event happens on" 1 UINT alarmminutes "a value of 100 indicates not set" 1 UINT alarmhours "a value of 100 indicates not set" 1 UINT changeserial 1 UINT snoozedelay "in minutes" 1 UINT ringtone 39 STRING {'raiseonunterminatedread': False} description to: PACKET scheduleevent: 4 UINT pos "position within file, used as an event id" 4 LGCALDATE start 4 LGCALDATE end 1 UINT repeat 3 UINT daybitmap "which days a weekly repeat event happens on" 1 UINT alarmminutes "a value of 100 indicates not set" 1 UINT alarmhours "a value of 100 indicates not set" 1 UINT changeserial 1 UINT snoozedelay "in minutes" 1 UINT ringtone 35 STRING {'raiseonunterminatedread': False} description 2 UINT foo1 2 UINT foo2 2 UINT foo3 I then ran: python protogen.py p_lgvx4500.p p_lgvx4500.py and ran bitpim, but got what appeared to be the exact same problem with=20= the same count as last time, namely: IndexError: trying to read one byte beyond end of 66 byte buffer I wasn't sure if I'd fixed anything or not, but I expected the count to=20= change since the scheduleevent is now 2 bytes larger and I assumed=20 those "self" references would change things. I don't know python=02=02=02. Peter Peter Dufault HD Associates, Inc.= |
From: Stephen W. <sa...@us...> - 2004-05-11 23:59:52
|
On Tue, 2004-05-11 at 19:24, Roger Binns wrote: > Stephen Wood wrote: > > OK, the problem was that the last p_sanyonewer.py that I checked in > > ended up being a null file. > > Any idea how that happened? (I am also curious as to why you get a > CRC error since such checking should happen before It might have been that I was checking in the file at a time when my wireless connection was flaking in and out. The packet coming back is 0x13 followed by 16 bytes of the request packet followed by the checksum. The 0x13 is in the checksum. The code, interprets the 0x13 as junk, strips it, then checks the checksum. I'll catalog the various error responses (Other bad packets return the brew "Y" followed by a fragment of the request packet) and see if I can improve the Sanyo sendpbcommand to give more meaningful errors. Do the LG phones do anything similar in response to packets they don't recognize? Why do the brew exceptions work? Do brew errors not echo back a fragment of the packet, thus not fooling "d=date.find(firsttwo)". > > > Roger, can you do a new build? It will keep the noise level on the > > lists from being to high for the next two weeks. > > Steven, can you redo the Mac build? > > > Can we do something reduce the problems of out of date p_*.py files, or > > even elinate them from the CVS? > > The reason they are in CVS is so that we can get back exactly an > earlier release. Whenever you have "built" files, and don't save > them, it can get quite difficult knowing what went on. Also > rebuilding them automatically could also result in unintentional > differences. Arguably I am being overly cautious, but I wanted > to be in a situation where I know for sure that the Mac, Linux and > Windows builds are all using exactly the same code. How about a check in makedist that the p_*.py files are not out of data (and not null) that aborts if anything is wrong. I'll code it if you'll use it. > > I had also hoped that having the releases available for day to > bitpim-devel folks would mean they get some double checking. Not to mention some single checking! I'll do that next time. Stephen |
From: Roger B. <ro...@ro...> - 2004-05-11 23:24:30
|
Stephen Wood wrote: > OK, the problem was that the last p_sanyonewer.py that I checked in > ended up being a null file. Any idea how that happened? (I am also curious as to why you get a CRC error since such checking should happen before > Roger, can you do a new build? It will keep the noise level on the > lists from being to high for the next two weeks. Steven, can you redo the Mac build? > Can we do something reduce the problems of out of date p_*.py files, or > even elinate them from the CVS? The reason they are in CVS is so that we can get back exactly an earlier release. Whenever you have "built" files, and don't save them, it can get quite difficult knowing what went on. Also rebuilding them automatically could also result in unintentional differences. Arguably I am being overly cautious, but I wanted to be in a situation where I know for sure that the Mac, Linux and Windows builds are all using exactly the same code. I had also hoped that having the releases available for day to bitpim-devel folks would mean they get some double checking. Roger |
From: Peter D. <du...@hd...> - 2004-05-11 18:14:53
|
On May 10, 2004, at 10:24 PM, Roger Binns wrote: > > It looks like they have made each record one byte longer. Please > delete the calendar files as detailed in my earlier message > http://article.gmane.org/gmane.comp.mobile.bitpim.devel/229 > and reboot the phone. Then make some events where the name is > as long as possible. > > See if you can figure out where the extra byte(s) went. > The existing description is in p_lgvx4400 as > scheduleevent. > I've attached a hex dump of the sch/schedule.dat file. I'll look at this more later, but this shows some of the ways it has changed. The description is only 35 bytes long now. Hopefully the earlier fields are the same. I'll decode this when I have some time. Peter |
From: Roger B. <ro...@ro...> - 2004-05-11 02:23:55
|
Peter Dufault wrote: > First thing I noted is that though the entry I created at bitpim the > other day is sent back and forth to the phone, the phone doesn't see > it. Yes, that is because the calendar file is in a different format. There is no sync protocol for the calendar. BitPim just reads and writes a file on the filesystem. Being able to do so doesn't mean the file is valid for the phone. > Secondly I created a simple entry on the phone (Text "test" from 2:00 > to 3:00 PM today) and then tried to get the calendar using BitPim. I > received this message on the startup terminal screen: > FutureWarning: x<<y losing bits or changing sign will return a long in > Python 2.4 and up > res|=buf.getnextbyte()<<shift Ignore all warnings like that. They are very annoying but it is not a bug in the code. It looks like they have made each record one byte longer. Please delete the calendar files as detailed in my earlier message http://article.gmane.org/gmane.comp.mobile.bitpim.devel/229 and reboot the phone. Then make some events where the name is as long as possible. See if you can figure out where the extra byte(s) went. The existing description is in p_lgvx4400 as scheduleevent. Roger |
From: Roger B. <ro...@ro...> - 2004-05-11 02:13:22
|
From this release onwards, I will be announcing new versions here first, and then a day later to bitpim-announce. That lets y'all try it out first, and also report any gotchas that may exist. http://sf.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=237331 The list of changes is at http://bitpim.sf.net/testhelp/versionhistory.htm LG users remember to re-read the phonebook from the phone before writing to it. This is so that the speed dial information is read. (If you don't do that, you will lose your speed dials). Roger |
From: Peter D. <du...@hd...> - 2004-05-10 17:16:52
|
BitPim CVSd at 13:00EST Mac OS X 10.3.3 LG VX4500 I tried the calendar today, it is indeed under the Voice menu for some reason. First thing I noted is that though the entry I created at bitpim the other day is sent back and forth to the phone, the phone doesn't see it. Secondly I created a simple entry on the phone (Text "test" from 2:00 to 3:00 PM today) and then tried to get the calendar using BitPim. I received this message on the startup terminal screen: calendar 2 wallpaper not requested ringtone not requested /Users/dufault/work/bitpim/prototypes.py:188: FutureWarning: x<<y losing bits or changing sign will return a long in Python 2.4 and up res|=buf.getnextbyte()<<shift And this exception: An unexpected exception has occurred. Please see the help for details on what to do. Traceback (most recent call last): File "/Users/dufault/work/bitpim/gui.py", line 152, in run res=call() File "/Users/dufault/work/bitpim/gui.py", line 92, in __call__ return apply(self.method, self.args+args, d) File "/Users/dufault/work/bitpim/gui.py", line 1126, in getdata i[1](results) File "/Users/dufault/work/bitpim/com_lgvx4400.py", line 399, in getcalendar sc.readfrombuffer(buf) File "/Users/dufault/work/bitpim/p_lgvx4400.py", line 2391, in readfrombuffer self.__field_events.readfrombuffer(buf) File "/Users/dufault/work/bitpim/prototypes.py", line 676, in readfrombuffer x.readfrombuffer(buf) File "/Users/dufault/work/bitpim/p_lgvx4400.py", line 2119, in readfrombuffer self.__field_start.readfrombuffer(buf) File "/Users/dufault/work/bitpim/prototypes.py", line 188, in readfrombuffer res|=buf.getnextbyte()<<shift File "/Users/dufault/work/bitpim/prototypes.py", line 855, in getnextbyte raise IndexError("trying to read one byte beyond end of "+`len(self._data)`+" byte buffer") IndexError: trying to read one byte beyond end of 66 byte buffer Variables by last 8 frames, innermost last Frame __call__ in /Users/dufault/work/bitpim/gui.py at line 92 self = <gui.Request instance at 0x5a4ddf0> args = () d = {} kwargs = {} Frame getdata in /Users/dufault/work/bitpim/gui.py at line 1126 count = 1 i = (<bound method GetPhoneDialog.GetCalendarSetting of <guiwidgets.GetPhoneDialog i self = <WorkerThread(BitPim helper, started daemon)> req = <guiwidgets.GetPhoneDialog instance; proxy of C++ wxDialog instance at _4939dc0_ willcall = [(<bound method GetPhoneDialog.GetCalendarSetting of <guiwidgets.GetPhoneDialog results = {'sync': {'calendar': 'OVERWRITE'}, 'wallpaper-index': {1: {'origin': 'builtin', sync = {'calendar': 'OVERWRITE'} st = 0 Frame getcalendar in /Users/dufault/work/bitpim/com_lgvx4400.py at line 426 res = {} self = <com_lgvx4500.Phone instance at 0x5c42878> sc = <p_lgvx4400.schedulefile object at 0x5c470d0> result = {'sync': {'calendar': 'OVERWRITE'}, 'wallpaper-index': {1: {'origin': 'builtin', exceptions = {} buf = <prototypes.buffer instance at 0x5c42bc0> ex = <p_lgvx4400.scheduleexceptionfile object at 0x5c47450> Frame readfrombuffer in /Users/dufault/work/bitpim/p_lgvx4400.py at line 2391 buf = <prototypes.buffer instance at 0x5c42bc0> self = <p_lgvx4400.schedulefile object at 0x5c470d0> dict = {'elementclass': <class 'p_lgvx4400.scheduleevent'>} Frame readfrombuffer in /Users/dufault/work/bitpim/prototypes.py at line 676 x = <p_lgvx4400.scheduleevent object at 0x5c47bd0> self = <prototypes.LIST object at 0x5c477f0> buf = <prototypes.buffer instance at 0x5c42bc0> Frame readfrombuffer in /Users/dufault/work/bitpim/p_lgvx4400.py at line 2119 buf = <prototypes.buffer instance at 0x5c42bc0> self = <p_lgvx4400.scheduleevent object at 0x5c47bd0> dict = {'sizeinbytes': 4} Frame readfrombuffer in /Users/dufault/work/bitpim/prototypes.py at line 188 shift = 0 self = <prototypes.LGCALDATE object at 0x5c47c50> dummy = 0 buf = <prototypes.buffer instance at 0x5c42bc0> res = 0 Frame getnextbyte in /Users/dufault/work/bitpim/prototypes.py at line 855 self = <prototypes.buffer instance at 0x5c42bc0> Peter Dufault HD Associates, Inc. |
From: Roger B. <ro...@ro...> - 2004-05-09 22:31:45
|
Everything is ready for the build ... Roger |
From: Peter D. <du...@hd...> - 2004-05-09 01:46:50
|
On May 8, 2004, at 8:49 PM, Roger Binns wrote: > You don't need to a phone to run the test data generator. > True, but when working on the phone stuff I'd rather have the phone so I can try things out. Peter Peter Dufault HD Associates, Inc. |
From: Roger B. <ro...@ro...> - 2004-05-09 00:49:17
|
> I meant on the phone. I don't have the phone here, but I do have the > User's Guide and I don't see anything there about "Schedule" on the > menu tree other than "Voice Scheduler". That is the right thing. The user interface is identical to the VX4400 and VX6000 except there is a voice field. You can see this stuff online. For example the VX4500 demo is at http://www.verizonwireless.com/multimedia/mim/lg_vx4500/VX4500.swf Compare with the VX6000 one at http://www.verizonwireless.com/multimedia/mim/lg_vx6000/VX6000.swf > But it did send and receive > the calendar with the entries I created on BitPim, and I saw the Ascii > going by in the log so I know it was transferred. That doesn't mean anything. The calendar is just two files, there isn't a protocol. Consequently it would work with any phone. We need to verify the data file location and format has remained the same. Given the additional voice field they aren't likely to be. The files used for the calendar on the other phones are sch/schedule.dat and sch/schexception.dat. I recommend deleting the files and then rebooting the phone. It will recreate them empty. Add some events and check to see if BitPim reads them correctly. There is one field labelled changeserial which is actually wrong and controls how the UI on the phone shows the repeat. (Its a nice little project for someone to fix if they want :-) > > That narrows down in the code where it is happening. Try the following > > change (which I also just committed)... > > > > Will do next time I have the phone by the computer. You don't need to a phone to run the test data generator. Roger |
From: Steven P. <n9...@n9...> - 2004-05-08 22:30:10
|
On May 7, 2004, at 5:06 PM, Peter Dufault wrote: > I've found a few places that Python segfaults on the Mac with BitPim, > but I can't find the core dumps. ~/Library/LogsCrashLogs/ They're note coredumps, but rather Apple's debug logs. To have these generated, make sure it's turned on by the following line in /etc/hostconfig: CRASHREPORTER=-YES- The system should use /cores to store core dumps in, but by default they are turned off (set to 0 as the maximum size via ulimit -c). If you put the following line in /etc/hostconfig, they will be activated again: COREDUMPS=-YES- The above is referenced by /etc/rc.common to set `ulimit -c unlimited` on bootup. Of course, you could just do that manually when you wanted to enable them and `ulimit -c 0` when you wanted to disable them. |
From: Peter D. <du...@hd...> - 2004-05-08 21:00:22
|
On May 8, 2004, at 2:19 PM, Roger Binns wrote: > >> Too bad I can't figure out how to look at the calendar entries on the >> phone. If there is anyone else out there with a VX4500 who isn't new >> to both BitPim, modern cell phones in general the VX4500 in particular >> feel free to join in the testing. > > By this do you mean you can't figure out the user interface on > the phone, or that BitPim is getting something wrong? The UI on > the VX4400 is Menu - Organizer - Schedule. On the VX6000 it is > Menu - Tools - Schedule I meant on the phone. I don't have the phone here, but I do have the User's Guide and I don't see anything there about "Schedule" on the menu tree other than "Voice Scheduler". But it did send and receive the calendar with the entries I created on BitPim, and I saw the Ascii going by in the log so I know it was transferred. > So just to confirm, you can't find any flaws in the reading and writing > of phonebook, calendar, wallpaper or ringtones? Correct. All worked today. ... > That narrows down in the code where it is happening. Try the following > change (which I also just committed)... > Will do next time I have the phone by the computer. Peter Dufault HD Associates, Inc. |
From: Roger B. <ro...@ro...> - 2004-05-08 18:19:55
|
Peter Dufault wrote: > First a Mac note: first thing I did was "Edit->Settings" and changed > the phone type from LG4400 to LG4500 and nothing was logged, either on > the startup terminal screen or the log screen, so maybe that isn't > being saved. Nothing is logged to screen or terminal. Look at ~/.bitpim which is what should be changed. > Too bad I can't figure out how to look at the calendar entries on the > phone. If there is anyone else out there with a VX4500 who isn't new > to both BitPim, modern cell phones in general the VX4500 in particular > feel free to join in the testing. By this do you mean you can't figure out the user interface on the phone, or that BitPim is getting something wrong? The UI on the VX4400 is Menu - Organizer - Schedule. On the VX6000 it is Menu - Tools - Schedule > Where do you view or set speed dial settings from BitPim? The speed dial field is part of the editor for each phone number. I suppose at some point we'll need some new UI that shows all the speed dials together and lets you change them. > When I have more time I'll go over things more, but at the basic level > things are working well. So just to confirm, you can't find any flaws in the reading and writing of phonebook, calendar, wallpaper or ringtones? > I'll try to work through the "test" directory next. The data it generates is more of a "stress" than a useful test. (Actually the midis and wallpapers are fine - the phonebook and calendar are a little extreme :-) > #5 0x01088fe4 in _wrap_delete_wxDC () That narrows down in the code where it is happening. Try the following change (which I also just committed). Move the following lines out of the wallpaper generation and put them immediately after if __name__=='__main__' # Move wx stuff here import wx app=wx.PySimpleApp() If that still causes trouble, add the following two lines after the above two. frame=wx.Frame(None, -1, "Nothing") frame.Show(True) It will cause a window to appear on the screen. Roger |
From: Peter D. <du...@hd...> - 2004-05-08 15:32:28
|
On May 7, 2004, at 11:32 PM, Roger Binns wrote: > I still need more info about the VX4500 like what actually > works. The internet came back up, so here are a few notes. First a Mac note: first thing I did was "Edit->Settings" and changed the phone type from LG4400 to LG4500 and nothing was logged, either on the startup terminal screen or the log screen, so maybe that isn't being saved. Essentially I did "Get/Send phonebook", "Get/send wallpaper", "Get/Send midi files", and "Get/Send Calendar entry" without any problems, no segfaults at all today. Too bad I can't figure out how to look at the calendar entries on the phone. If there is anyone else out there with a VX4500 who isn't new to both BitPim, modern cell phones in general the VX4500 in particular feel free to join in the testing. Where do you view or set speed dial settings from BitPim? When I have more time I'll go over things more, but at the basic level things are working well. I'll try to work through the "test" directory next. I tried to generate the tests while running under GDB, here's the stack traceback. I doubt this helps much, I'll try to track down where it is happening in gentestdata.py. Reading symbols for shared libraries . done Reading symbols for shared libraries . done Generating 8 midi files ... generation complete Generating 60 wallpaper files Reading symbols for shared libraries . done Program received signal EXC_BAD_ACCESS, Could not access memory. 0x98c5a1d0 in CopyRgn () (gdb) where #0 0x98c5a1d0 in CopyRgn () #1 0x98c67e8c in GetPortVisibleRegion () #2 0x025d7a94 in wxWindowDC::~wxWindowDC() () #3 0x025d801c in wxPaintDC::~wxPaintDC() () #4 0x025d82d8 in wxMemoryDC::~wxMemoryDC() () #5 0x01088fe4 in _wrap_delete_wxDC () #6 0x95fa94a8 in PyEval_GetFuncDesc () #7 0x95fa6c64 in PyEval_EvalCode () #8 0x95fa7e30 in PyEval_EvalCodeEx () #9 0x95f5f354 in PyFunction_SetClosure () #10 0x95f4a8d0 in PyObject_Call () #11 0x95f529e8 in PyMethod_New () #12 0x95f4a8d0 in PyObject_Call () #13 0x95fa91ec in PyEval_CallObjectWithKeywords () #14 0x95f4e13c in PyInstance_New () #15 0x95fa4e30 in PyEval_EvalCode () #16 0x95fa7e30 in PyEval_EvalCodeEx () #17 0x95fa97dc in PyEval_GetFuncDesc () #18 0x95fa9580 in PyEval_GetFuncDesc () #19 0x95fa6c64 in PyEval_EvalCode () #20 0x95fa9728 in PyEval_GetFuncDesc () #21 0x95fa9580 in PyEval_GetFuncDesc () #22 0x95fa6c64 in PyEval_EvalCode () #23 0x95fa7e30 in PyEval_EvalCodeEx () #24 0x95fa4734 in PyEval_EvalCode () #25 0x95fc85f0 in PyRun_FileExFlags () #26 0x95fc7668 in PyRun_SimpleFileExFlags () #27 0x95fd1ec0 in Py_Main () #28 0x00003c78 in ?? () #29 0x00003aec in ?? () (gdb) Peter Dufault HD Associates, Inc. |
From: Peter D. <du...@hd...> - 2004-05-08 14:46:43
|
On May 7, 2004, at 11:32 PM, Roger Binns wrote: > The sections of Phones, BitFling and About BitPim and > everything within them should be up to date. If there > is stuff missing, badly worded etc please post about it. > I still need more info about the VX4500 like what actually > works. The only thing I know works perfectly is the phone book. The wallpapers can be sent fine and show up in the phone properly, but when I try to get them back python segfaults. I haven't tried ringtones yet. I'll look at that this PM and test your speed dial support assuming my internet connection comes back up (I'm accessing email via backup dialup) and I can CVS your latest changes. Peter Peter Dufault HD Associates, Inc. |
From: Roger B. <ro...@ro...> - 2004-05-08 03:31:24
|
I have committed code that does speed dial reading and writing for the LG VX phones. It is fully tested on the VX4400 and VX6000. I would appreciate reports for the VX4500. The VX4600 has the code disabled as noone has come forward with information. The documentation also needs updates. Start at http://bitpim.sourceforge.net/testhelp/ The sections of Phones, BitFling and About BitPim and everything within them should be up to date. If there is stuff missing, badly worded etc please post about it. I still need more info about the VX4500 like what actually works. Roger |
From: Roger B. <ro...@ro...> - 2004-05-07 22:24:06
|
Peter Dufault wrote: > Specifically, reading back wallpapers or trying to generate the test > stuff with "python experiments/gentestdata.py tests" will segfault. I don't have a Mac so I don't know. However you should be able to run Python under gdb or equivalent. $ gdb /usr/bin/python (gdb) run experiments/gentestdata.py tests That should dump you into the debugger at the point of the seg fault. Roger |
From: Peter D. <du...@hd...> - 2004-05-07 22:06:48
|
I've found a few places that Python segfaults on the Mac with BitPim, but I can't find the core dumps. Specifically, reading back wallpapers or trying to generate the test stuff with "python experiments/gentestdata.py tests" will segfault. Phone: Vx4500 O/S: OS X 10.3.3 BitPim: 0.7test10 latest Peter Dufault HD Associates, Inc. |
From: Roger B. <ro...@ro...> - 2004-05-07 20:28:29
|
> > - How many speed dials does the phone have? The answer is > > most likely 100. > > I'm not sure since they are only numbered 1 to 99, see next answer. That will tie in with the actual speed dials being 0 thru 99 (ie 100 of them). The user interface just hides 0 and 1. > Shouldn't that be 0x0015 to correspond to read entry 21? The data is right and I was just taking a short cut. Each phonebook entry has an entry number. If you just create 20 in a row, they will be numbered 0 thru 19. If you delete 12, the BitPim log will show 0 thru 18, but the actual entry numbers inside each entry remain the same (ie a hole at 12) and the speed dials are pointing to the entry numbers. You can see this in the protocol log. But good catch and I will double check the code is really doing the right thing and using the right entry number. Roger |
From: Peter D. <du...@hd...> - 2004-05-07 20:19:45
|
On May 7, 2004, at 4:06 PM, Peter Dufault wrote: > 15:51:20.685 LG-VX4500: Read entry 21 - Brother Dufault > > Now I hexdump pim/pbspeed.dat: > > 00000000 ff ff ff ff ff ff 17 00 00 ff ff 02 ff ff 03 ff > ................ > 00000010 ff 04 ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ................ > (Balance are 0xff) > > Interpreted: > > SD #0 0xffff 0xff > SD #1 0xffff 0xff > SD #2 0x0017 0x00 > > Shouldn't that be 0x0015 to correspond to read entry 21? > There appears to be an offset of 2. I just added speed dial entry #3 for my wife's second phone. She is at read entry 47. Now I get this for the hexdump: 00000000 ff ff ff ff ff ff 17 00 00 31 00 01 ff ff 03 ff .........1...... 00000010 ff 04 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ SD #2 0x0017 0x00 SD #3 0x0031 0x01 0x17 = 23 = read entry 21 + 2. 0x31 = 49 = read entry 47 + 2. Peter Peter Dufault HD Associates, Inc. |