|
Originally posted by StrataG NOTE: You must have the data cable to do what I'm going to explain. With a little examination I've found you can store up to 70 images and ringtones on the vx6000. 20 for mms(pix msging), 30 for brew (downloaded from get it now), 20 for drm (haven't found a source for downloads, but it's supposed to allow for copyrighted material... Digital Rights Management). Here's how to do it: Brew(supposed to be from get it now apps like myseenz and modtones): Image Folder: /brew/shared Image Map file: brewImageIndex.map Ringer Folder: /user/sound/ringer Ringer Map file: brewRingerIndex.map MMS (supposed to be from pix messaging): Image Folder: /brew/shared/mms Image Map file: mmsImageIndex.map Ringer Folder: /mms/sound Ringer Map file: mmsRingerIndex.map DRM images (no source for appropriate usage that I know of, I'm assuming there may be a source in the future for having copyrighted materials sent via pix messaging): Image Folder: /brew/shared/mms/d Image Map file: mmsDrmImageIndex.map Ringer Folder: /mms/sound/drm Ringer Map file: mmsDrmRingerIndex.map I won't get into editing the map files as there have been many threads explaining this. This is merely to explain the possibilities. Notes: -It appears the drm files have an icon in the ringer and image list that denotes it as copyrighted (or at least different than the others), but they will accept normal ringers and images. -If you send jpg's (this includes the conversion pix messaging does) there will be white space. -If you send bitmaps you will not have that padded spacing. -No need for my conversion program to have borderless wallpapers if you use bitmaps. -Best bet as of now seems to be to load up the drm sections since it's not in use now, then go to brew (unless you use myseenz or a ringtone app a lot), then save the mms ones for friends sending you data. |
|
Originially posted by Darnoc Here's how to upload midi ringers directly to phone: 0) If you want to save any ringers you already have, do this from BitPim now and save to your HD before going onto step 1. 1) From Phone: Menu-7-2, manually delete any ringers you added (you can leave dreamsequence, ode_to_joy, rainforest, and train as these are in a different directory and map file pointer. 2) Turn phone off/on and double check Menu-7-2 to delete anything that appears. (this is possible if you add ringers ontop of current ones, the phone will not see them until you wipe out the current ones. The phone will then look back in the directory and recreate the map pointer file). 3) From BitPim: go thru filesystem tab and go down to /user/sound/ringer, right click ringer and new file then add your midi files. 4) Turn phone off/on. 5) From Phone: Menu-7-2, viola your ringers have appeared and no map editing was needed. To add additional ringers, start back from step 1 unfortuantely (for now...) |
|
Originally posted by Darnoc I figured out how the map files work in /download/dloadindex for similiar to the VX4400. The VX6000 can hold 30 ringers and pics in these map files, there other map files I believe we can use as well to add even more (you'll have store the additional files in different directories.) The good part about HEX editing the map file is that you won't need to power cycle the phone to see the ringers/pics and won't have reload everything from scratch, just add additional and HEX edit. brewImageIndex.map and brewRingerIndex.map look like this when blank: Quote:
Then look like this when populated: Quote:
The first byte (10 - incase of the populated one) indicates how many ringers/pics are loaded, each time you HEX edit and add ringers, you must update the first byte to reflect the # of ringers/pics. If you look at the blank example, everytime there is two bytes of FF FF is where the next record will be. So add your first ringer make FF FF to 00 00 followed by the name of your file. Second will be 01 00 followed by the name of your file, and so on, and so on... Just don't forget to update the index byte at the beginning of the file. So if starting off blank and you wanted 1.mid added it would look this from start to finish: 01 00 00 00 31 2E 6D 69 64 (31 2E 6D 69 64 is 1.mid in ASCII hex). Note, I cannot use the mapeditor that VeXeD posted, the VX4400 map file is still different somehow from the VX6000. |
vBulletin Copyright ©2000 - 2008,
Jelsoft Enterprises Limited.
vB Easy Archive Final ©2000 - 2008
- Created by Stefan "Xenon" Kaeser