Hello,
Thank you all for responding so promptly. I really didn't mean for this
to turn into a "please help me find my phone" -post. Just trying to
uncover any bugs, before code integration... *sigh*
Some answers:
I don't have an SD card in this 8300 & I don't think the 5300's are
equipped to use them.
I encountered the Wallpaper problem on a vx5300 phone, which was
manually set to use the 8300 code. I was attempting to "Send Data To
Phone" to "Add" several wallpaper images to its existing ones.
When I first grabbed the new wallpapers into BitPim from my harddrive,
the program forced me to resize them. Could this have been a factor?
It's not something I'd encountered before. (I now know how to bypass
that "feature," btw...)
It's also possible that my troubles were due to user error. See below.
Below:
I had a chance to exercise the VX8300 code today. One thing I noticed
was that sometimes BitPim didn't do what I wanted it to on the first try.
For example, when I first pulled data from the phone, the sizes on about
half of the existing ringers showed "0 Kb" and I had to "Get Data" a
second time for them to appear correctly. (Data cable problem?)
Another example: when I tried to "Add" several new ringtones onto the
phone at once, BitPim only uploaded *one* of them, and then indicated
that it was finished. Since I was familiar with USB upload times, it
was obvious that something was off and I had to "Send Data To Phone" a
second time for all of the new ringers to transfer correctly.
This is where 'user error' may have come into play. When I checked the
ringtone pane in BitPim, that single ringer from the first attempt was
still highlit. However, I didn't expect the program to restrict the
Send Data/Add operation to the selected file(s) only.
The reason I bring this up is that my earlier troubles with Wallpapers
may have been due to similar problems--the program not responding as
expected. Guess I need to Re-read The Fine Manual...
And since the 5300's here, happen to belong to family members and
they're not exactly rushing up to the "brick my phone, please" -queue, I
don't really have a chance to experimentally recreate that error's
conditions.
So, I'm going to have to restrict testing to the single 8300. At least
there were no database corruption errors, this time. (Previously, I had
a VX7000, which transferred everything flawlessly thru BitPim with an
older vx6000 cable. I'm using that same cable with these newer phones,
if that makes a difference?)
Thanks again,
--Logan
Post by Michael C.Logan,
I cannot speak for the 5300, but I have done some of the development of
the VX8300, with a lot of help from a former guru, Simon. I know that
the code is not 100% correct, but I am not familiar with any issues with
uploading wallpaper images to the phone; in fact, it works 100% for me.
I do know that the code as written right now does not support direct
downloading/uploading directly from/to the micro SD card. Are you
saying there is a problem with the VX8300 and images, or using the
VX8300 code with a VX5300, there is a problem?
Due to family issues that I have to deal with, and a whole list of other
problems I have had to face these past couple of months, I will be
unable to look at finishing the VX8300 code before the beginning of
February. The only outstanding issue with the VX8300 is getting the
wallpaper assignment to phone number working correctly.
Regards,
Michael C.
Post by Logan GravesHas this "5300 Patch" found its way into the latest build? I now have
access to a couple of these phones, along with an VX8300.
I updated to the most recent BitPim release (0.9.09), but it couldn't
detect either one of the VX5300's & this model still didn't show up in
the Big List o' Phones.
the contacts & sounds seem to have transferred fine, but I think this
model uses a slightly different scheme for its Pix database (which you
probably already knew...)
The added Pix failed to show up in the phone once it was disconnected
from the PC, even though BitPim showed them being slowly transferred to
the phone. This resulted in database corruption to the existing images,
during renaming operations (renamed image displayed 'Pix not Found'
graphics).
Rebooting the phone rebuilt the database index & restored the original
image names, but the added ones were still absent. Subsequent renames
worked correctly.
Thanks,
-Logan
Post by Steve BrownHi folks --
I've been tinkering on the trunk with support for the VX5300, based on
a tutorial at http://fob.po8.org/node/254 . The phone architecture is
almost identical to the 8100 / 8300 series, just a few trivial changes
and I have a nice, clean interface to this phone. Mainly I have
removed features that Verizon broke in their software. The thing is
a great cheapie bluetooth phone, now I just wish BitPim had a clean
interface to the OS Bluetooth layer. Also, it may be worth having the
"OMG I can't find it on the list MY PHONE IS TEH BRICKED!"
The vx5300-init.patch should be applied against __init__.py, the other
two files go in /src/phones/ and then run protogen. If you are
familiar with the codebase then I hope you can get this to work
easily.
Please let me know if anyone has success with this. Hope I've helped
someone. I will continue work on this if youze'all can send me bugs.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BitPim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel