archive-org.com » ORG » B » BITPIM.ORG

Total: 282

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Cables
    BitPim Other straight through USB cables for Sanyo phones may also work RPI Wireless charging cable This cable available from RPI Wireless will charge the phone as well as act as a data cable Futuredial cable The cable from FutureDial has the product ID CSAYM03 03 Drivers Windows These cables require a driver Some cable vendors will supply drivers but some cables may not be supplied with drivers or the drivers may not support the most recent phones The Sprint PCS Connection Manager for Phone as Modem USB Cables package includes drivers for many Sanyo and other Sprint phones To download this package visit Sprint s download page select your version of Windows and look for 3 07 044 or later of the Connection Manager software Some users may wish to avoid installing the whole Sprint Connection Manager package This can be done by using an archive extractor such as Universal Extractor to extract filesCommon FilesSprintSanyo USBSANYO InstallerUS UsbDriver exe from the msi file Linux Older Sanyo phones use the Linux acm driver with this cable This driver will automatically install with most modern Linux distributions will show up as the device dev usb ttyACM0 If the acm driver does

    Original URL path: http://bitpim.org/help/phones-sanyo-cables.htm (2016-02-14)
    Open archived version from archive


  • What phones do the developers want?
    that are not available accessible to the BitPim developers are unlikely to be supported We would appreciate any loans and donations of these and other phones Manufacturer Model Carrier LG AX 355 LG LX 550 LG VX 8600 Verizon Wireless LG VX 9400 Verizon Wireless LG VX 9900 Verizon Wireless Samsung SCH A790 Samsung SCH A900 Samsung SCH U620 Verizon Wireless Sanyo SCP 200 Sprint Sanyo SCP 2400 Sprint Sanyo

    Original URL path: http://bitpim.org/help/phones-requested.htm (2016-02-14)
    Open archived version from archive

  • Other Phones
    the main authors only have a limited subset of phones Support for other phones depends on others contributing I believe that most recent CDMA phones will work for the filesystem view but none of the other features will Previous Cables

    Original URL path: http://bitpim.org/help/phones-other.htm (2016-02-14)
    Open archived version from archive

  • Access has been blocked
    directory There is nothing BitPim can do to get access as the block is on the phone itself These blocks are usually because the carrier wants customers to update content via their services rather than using a program like BitPim

    Original URL path: http://bitpim.org/help/errors-access-blocked.htm (2016-02-14)
    Open archived version from archive

  • Where do I download cell phone specifications?
    way phones are brought to market is that the phone manufacturer picks target features they hope the carrier wants such as colour displays cameras multi media voice commands and get a chipset from Qualcomm Look here for a selection of CDMA 3G ones They also have GSM UMTS chipsets The chipsets also come with reference software modules for the various features available The phone manufacturer then integrates some of their own customised modules typically the phonebook with the reference modules The LG VX4400 amusingly has a mostly complete MMS module that is present in various menus but wasn t actually used over the air in the end The manufacturers usually have their own phonebook modules that they have been dragging from phone to phone However it usually requires updating on each phone due to to new features such as allowing phonebook entries to bring up a camera image on incoming calls Various files in the embedded filesystem usually nothing more than an array of C structures are referenced by the manufacturer modules as well as the reference software modules and have various sized length fields which will be different than earlier chipsets They work out how to manufacture the whole lot including other parts such as batteries The whole package goes through FCC certification Work continues with the carriers as the firmware usually has to be customised per carrier because of features available on each carrier as well as terminology differences For example Verizon Wireless call their Brew implementation Get It Now whereas US Cellular call it EasyEdge which requires different server configuration information menu entries and logos Six to nine months after certification by the FCC the phone becomes available on carriers The manufacturers don t make much money on the phones but do try to make up for it on volume and accessories This whole process gives little consideration to sync protocols and there is certainly no intention of allowing random programs at the end of a data cable to have complete access to all internal features as well as being robust against invalid data overflows and other out of bounds behaviour The phonebook sync protocol is usually the same across the manufacturers phones It pretty much consists of transferring memory binary images of the internal phonebook data structures with some extra commands to move backwards and forwards There may be other structures as well such as buffers to lookup callerid on an incoming call instead of scanning the whole phonebook The internal phonebook data structures are different on every model and even between firmware variations for example Brew firmware is different than J2ME firmware Sometimes the commercial sync software companies manage to license the protocol field description information from the manufacturer But often they and the BitPim developers just work it out That involves changing entries in the phone and seeing how the layout of the structures change inputting maximum data lengths guesswork and experiments For features other than the phonebook there is rarely a protocol Instead

    Original URL path: http://bitpim.org/papers/phonespecs/ (2016-02-14)
    Open archived version from archive

  • BitPim versioning scheme
    new features The release is incremented when there are minor changes and bug fixes Releases There is a new BitPim release approximately once a month It incorporates new phone model support new functionality and bug fixes In between official BitPim releases there are incremental test releases that are available approximately once a week These test releases offer an opportunity for users and developers to try and test the upcoming bug

    Original URL path: http://bitpim.org/help/versionscheme.htm (2016-02-14)
    Open archived version from archive

  • License and Warranty
    that it will be useful but WITHOUT ANY WARRANTY without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE See the GNU General Public License for more details There are no warranties as stated above ie this software may damage your phone This software is in no way associated with Audiovox LG Electronics Qualcomm Samsung Sanyo Sprint Verizon Wireless or any other handset manufacturer or wireless carrier

    Original URL path: http://bitpim.org/help/licenseandwarranty.htm (2016-02-14)
    Open archived version from archive

  • Upgrading
    older versions do not understand the newer data formats default My Documents BitPim Linux Install newer and older RPMs as you see fit When downgrading to older versions you must also delete the contents of the data directory as the older versions do not understand the newer data formats default HOME bitpim files Mac You can run whichever version of the dimg you want If you run an older version

    Original URL path: http://bitpim.org/help/upgrading.htm (2016-02-14)
    Open archived version from archive



  •