Jump to content

wes58

Members
  • Content count

    442
  • Joined

  • Last visited

Community Reputation

2 Neutral

About wes58

  • Rank
    Diehard

Previous Fields

  • Your Current Device(s)
    I900
  1. Disabling media scan?

    I found on xda-developers the way to disable media scanning: 1. Download application Startup Manager from the Market. 2. In Startup Manager go to System tab. 3. Click on Media Storage to uncheck it and this will disable media scanning. If you want to enable it again you can do the same steps Edit: I found xda-developers post that I referred to: http://forum.xda-developers.com/showthread.php?t=732462 post #5
  2. Why the TouchWiz hate?

    Well, I know it is not probably what you want, but if you switch to list view in TouchWiz you will have all applications listed in alphabetical order. For me, what I don't like it, is that if you have 3 or 4 pages of shortcuts to application you have to remember where the shortcut is for application you want. Going back to Omnia 2, the first rom versions have pages that you could assign the name to and put the shortcuts that you want - this way you could group you programs depending on the function like games, music etc. Then Samsung changed it to the same setup that we got in Galaxy S. At least with WM, if you didn't like TouchWiz, you could create folders in Start Menu (give them any names you want, games, music etc) and put shortcuts in those folders. Android is hopeless with that - there is no such thing as part of the OS.
  3. I am not sure what you mean. I have installed update.zip to root the phone on three different firmwares that I had: original JF4, then upgraded through Kies to JG4 and the last one I tried was JM5 and rooting with update.zip worked fine. If you want to try on Android 2.2, there are only unofficial firmwares released so far - I haven't tried them.
  4. Done. Although if you are using Root Explorer it doesn't matter, because you are browsing like in file manager. If you are using adb - yes it is important.
  5. It will work but first you have to root your phone. Check this post for how to do it: http://forum.xda-developers.com/showthread.php?t=728754
  6. I don't know if anyone else is annoyed by the startup and shutdown sounds. For me, they are much too loud, and the best for me is not to have them at all. So, to remove those two sounds I used silent .wav and .ogg files. Using RootExplorer I copied: PowerOn.wav to system/etc Shutdown.ogg to system/media/audio/ui. If you still like having some sounds during startup/shutdown, you could make your own files (.wav for startup and .ogg for shutdown) and copy them to the folders as above. I have attached the silent files that I use if anybody wants to use them. SilentSounds.rar
  7. When you port XIP from different version of OS, sometimes we get XIP partition smaller in size. Although it is smaller in size, but because of the insertion addresses of XIP and IMGFS (which are defined in the partition table), there is a gap between end of XIP & start of IMGFS which is filled with FF. By reducing this gap you can gain some storage space. I haven't tested it well so I can't tell you if you gain much and whether you won't have any problems. If you want to try it, go ahead, I think the worst thing that can happen is that the phone won't boot after flashing - than you just flash it again with different rom. I am not sure if it is really worth it, it was something I read about and wanted to try it. I don't think anybody has a problem with not sufficient storage space on the phone? By the way, I have moved to Galaxy S now so won't be checking this thread too often.
  8. I'm glad to hear that it is working. You could check in Control Panel-Add Remove Programs which versions of .NET framework you have on both computers and install the one that is missing.
  9. I used buildOS in romTool because that was the only application that worked without any problems when we started with building roms for Omnia2. What else I like in BuildOS is that if something is wrong with the rom that you are building it gives you some information of an error. Other applications that romTool is using (xipPort, extReloc) also have some settings that you can modify for you rom build. I tried platformrebuilder a few times in the past but it always failed without giving you a any information about cause of an error. Then I found out that someone found that the problem was with Samsung xip (or nk.exe module). There were also some solutions to it, as you already now. But because I have already had romTool working I didn't see a reason for spending any more time trying to get it working with platformrebuilder and re-write it all. It's not something that you can do in a couple of hours.
  10. The warning message that you get during dump is not important. It just tells you, that because you are dumping a .bin fine it doesn't have a header which .nb0 file has. I think that you may have a problem with the version of Microsoft.NET framework on your computer. I am not sure which version is used by BuildOs - I think it is 2. Maybe you can try and google "Microsoft.net buildos" and see if you can find any information.
  11. It is hard to help you if you don't provide any information what you are doing? What is your folder structure? Where do you have all the files? What rom are you building? If you have a look in a guide for version 2.0, first two pictures show an example of the kitchen folder structure (first picture) and how the paths are set (top part of the second picture). I have attached this file again here. RomTool_Guide_2.0.pdf
  12. I am not sure what can be wrong. The only time I got the message 'buildos.exe has stopped working' when I tried to run (double click) buildos.exe directly from the Tools folder (not through romTool) - and it doesn't work because it doesn't have paths set properly. The only suggestion that I would make is start from the beginning: 1. Create a copy of a _template folder. 2. Rename this new folder to what ever you want. 3. Put any rom.bin file in this new folder. 4. Start romTool and select your new folder in 'ROM:' list box. 5. Dump the rom.bin file. 6. If the 'SYS' list box is empty you have to change to a different folder in 'ROM' and then go back to the folder that you were using - you should have [sys] shown in 'SYS' list box. Then try to build the new rom and see if buildOs starts.
  13. It all depends on which bat file you drag your imgfs.bin. If you drag it on Dump_PKG__IMGFS.bat you will get sys and oem folders in IMGFS folder of xidump. If you drag it on Dump_FILES__IMGFS.bat you will only get files/modules not split into oem and sys. One other thing, if the rom was built having "All packages to one" option checked, you won't be able to convert to sys and oem folders because there are no dsm files in the dumped rom!
  14. Yes, imgfs.bin is where sys and oem parts are and what is lzx compressed (if lzx compression is selected during build). What romTool does first is, it splits rom into xip and imgfs part and then extracts files from them. As I wrote before ImgfsToDumpxxx.exe fails during dumping imgfs.bin which are lzx compressed - the extracted files are corrupted. That's why you can use imgfs.bin with xidump and it should work.
  15. When you dump the rom with romTool it creates imgfs.bin. Use this file to dump pda files with xidump - just drag imgfs.bin over one of the .bat files in xidump folder. By the way, I thought you will have a look at the sense cab file created by rapid to workout what you need for your rom?
×