Database Develop

Can we not squeeze a little more out of the wizard's memory?

Adding an explanation for starting this thread
I started this thread because when I search for ways to get more memory, all I find is how others have things like "Big Storage" etc., but somewhere it will say cannot be done on wizard. I do not find very much about what can be done or why it cannot be done. I have found things about unlocking and unhidng the Extended_ROM. I used that as a basis for my trials and trying to understand how memory works in the wizard.
I started this thread hoping someone with much more knowledge than me would be able to shed light on the issue and it would be on the forum for future users to understand the memory issues on the wizard.
-----------------------------------------------------------------------------------------------------------
In default.hv which I converted to rgu so I could read I saw the following:
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable][/FONT]
[FONT=Arial]"26"="BINARY"[/FONT]
[FONT=Arial]"25"="IMGFS"[/FONT]
[FONT=Arial]"23"="RAWFS"[/FONT]
[FONT=Arial]"22"="RAWFS"[/FONT]
[FONT=Arial]"21"="BINFS"[/FONT]
[FONT=Arial]"20"="BOOT"[/FONT]
[FONT=Arial]"0F"="FATFS"[/FONT]
[FONT=Arial]"0E"="FATFS"[/FONT]
[FONT=Arial]"0C"="FATFS"[/FONT]
[FONT=Arial]"0B"="FATFS"[/FONT]
[FONT=Arial]"07"="NTFS"[/FONT]
[FONT=Arial]"06"="FATFS"[/FONT]
[FONT=Arial]"04"="FATFS"[/FONT]
[FONT=Arial]"01"="FATFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles][/FONT]
[FONT=Arial]"Folder"="Mounted Volume"[/FONT]
[FONT=Arial]"PartitionDriverName"="MSPART"[/FONT]
[FONT=Arial]"DefaultFileSystem"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:0[/FONT]
[FONT=Arial]"AutoFormat"=dword:0[/FONT]
[FONT=Arial]"AutoPart"=dword:0[/FONT]
[FONT=Arial]"AutoMount"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV][/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"Name"="Microsoft Flash Disk"[/FONT]
[FONT=Arial]"PartitionDriver"="mspart.dll"[/FONT]
[FONT=Arial]"DefaultFileSystem"="IMGFS"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\IMGFS][/FONT]
[FONT=Arial]"XIP"=dword:0[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS][/FONT]
[FONT=Arial]"FatCacheSize"=dword:100[/FONT]
[FONT=Arial]"DataCacheSize"=dword:800[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"Flags"=dword:600014[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\Part00][/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS][/FONT]
[FONT=Arial]"MountHidden"=dword:0[/FONT]
[FONT=Arial]"MountAsROM"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\MSPART][/FONT]
[FONT=Arial]"Dll"="mspart.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\IMGFS][/FONT]
[FONT=Arial]"ShadowROM"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="imgfs.dll"[/FONT]
[FONT=Arial]"FriendlyName"="Image-Update Filesystem"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"CacheSize"=dword:2000[/FONT]
[FONT=Arial]"Flags"=dword:44[/FONT]
[FONT=Arial]"CacheDll"="diskcache.dll"[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
In boot.rgu I found
Code:
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager] [/FONT]
[FONT=Arial]"PNPUnloadDelay"=-[/FONT]
[FONT=Arial]"PNPUnloadDelay"=dword:5dc[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\IMGFS][/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC][/FONT]
[FONT=Arial]"Name"="DiskOnChip M-Systems"[/FONT]
[FONT=Arial]"Folder"="imgfs"[/FONT]
[FONT=Arial]"MountFlags"=dword:11[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS][/FONT]
[FONT=Arial]"Flags"=dword:1000[/FONT]
[FONT=Arial]"Index"=dword:1[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"BootPhase"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"="Extended_ROM"[/FONT]
[FONT=Arial]"MountHidden"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:14[/FONT]
[FONT=Arial]"FormatTfat"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:1[/FONT]
[FONT=Arial]"Bootphase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1][/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC1"[/FONT]
[FONT=Arial]"Index" = dword:2[/FONT]
[FONT=Arial]"Dll" = "TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix" = "DSK"[/FONT]
[FONT=Arial]"Order" = dword:1[/FONT]
[FONT=Arial]"Ioctl" = dword:4[/FONT]
[FONT=Arial]"Use8Bit" = dword:1[/FONT]
[FONT=Arial]"WindowBase" = dword:00000000[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode" = dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Comm][/FONT]
[FONT=Arial]"AutoRun"="\\Windows\\AutoRun.exe"[/FONT]
[FONT=Arial]"AutoRunCFG"=[URL="file://\\Extended_ROM\\Config.txt"]\\Extended_ROM\\Config.txt[/URL][/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2][/FONT]
[FONT=Arial]"DefaultFileSystem"="FATFS"[/FONT]
[FONT=Arial]"Name"=""[/FONT]
[FONT=Arial]"PartitionDriver"=""[/FONT]
[FONT=Arial]"Folder"=""[/FONT]
[FONT=Arial]"MountFlags"=dword:6[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS][/FONT]
[FONT=Arial]"Flags"=dword:00600014[/FONT]
[FONT=Arial]"FormatTFAT"=dword:1[/FONT]
[FONT=Arial]"CheckForFormat"=dword:1[/FONT]
[FONT=Arial]"MountAsBootable"=dword:1[/FONT]
[FONT=Arial]"MountAsRoot"=dword:1[/FONT]
[FONT=Arial]"EnableWriteBack"=dword:1[/FONT]
[FONT=Arial]"DataCacheSize"=dword:00000080[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS2][/FONT]
[FONT=Arial]"Index"=dword:3[/FONT]
[FONT=Arial]"Profile"="TRUEFFS_DOC2"[/FONT]
[FONT=Arial]"Dll"="TrueFFS.dll"[/FONT]
[FONT=Arial]"Prefix"="DSK"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"Ioctl"=dword:4[/FONT]
[FONT=Arial]"Use8Bit"=dword:1[/FONT]
[FONT=Arial]"WindowBase"=dword:0[/FONT]
[FONT=Arial]"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"[/FONT]
[FONT=Arial]"AutoDPDMode"=dword:1[/FONT]
[FONT=Arial]"SoftwareWriteProtect"=dword:0[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\TrueFFS2][/FONT]
[FONT=Arial]"DriverPath"="Drivers\\BuiltIn\\TrueFFS2"[/FONT]
[FONT=Arial]"LoadFlags"=dword:1[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
[FONT=Arial]"BootPhase"=dword:1[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS\Filters\fsreplxfilt][/FONT]
[FONT=Arial]"dll"="fsreplxfilt.dll"[/FONT]
[FONT=Arial]"order"=dword:1 ; must be loaded before other filters[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\FATFS][/FONT]
[FONT=Arial]"FriendlyName"="FAT FileSystem"[/FONT]
[FONT=Arial]"Dll"="fatfsd.dll"[/FONT]
[FONT=Arial]"Flags"=dword:00000024[/FONT]
[FONT=Arial]"Paging"=dword:1[/FONT]
[FONT=Arial]"EnableCache"=dword:1[/FONT]
[FONT=Arial]"CacheSize"=dword:0[/FONT]
[FONT=Arial]"Util"="fatutil.dll"[/FONT]
[FONT=Arial][HKEY_LOCAL_MACHINE\System\StorageManager\filters\HTCFSDSPY][/FONT]
[FONT=Arial]"Dll"="htcfsdspy.dll"[/FONT]
[FONT=Arial]"Order"=dword:0[/FONT]
Of course there is more than just the above in those files. What I wonder since I do not know enough to know what cannot be done is...
Can you change these settings to not define a region to be extended ROM?
Can you redefine the rest to use this left over space?
Can any of this space be used for program memory instead of storage memory?
I do not know if the dll files limit the size of the regions or is some of the settings determine the sizes.
As I said, I do not know enough to know the limitations, but the little boy saw all that was needed was to let the air out of the tires to get the truck unstuck from under the bridge.
Note: This work was done on my G4

Are you using LZX compression?
If not start reading form “HERE” post #877

I have been reading that and the Visual Kitchen Thread, but they leave me behind a little yet.
I am just now trying to go past using the HyperCore Kitchen and switch to CRBuilder 2. I am not sure what it does different. It seems to be less forgiving of my mistakes.
I also read the threads on porting XIP, etc. I am still trying to learn this stuff.
Since I am naturally lazy, I thought what if we could get more room by not defining ExtendedROM. Also, I did not know how program memory versus storage memory is set up and if it was possible to get more program memory available. This is going to become our limiting factor (M2D, WM6.5, etc.).

Everything i’ve read would suggest that we can’t use the extended ROM area for anything other then what it was designed for.
I don’t think you can gain any more memory without removing programs.

I have been doing a lot of reading. I have a G4 Wizard. I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I am beginning to think extended rom is coded in the chip and not set by our flashes. Has anyone tried something like DiskOnChip TrueFFS Uilities package or similar to redefine the spaces on the chip to not have extended rom? I know so little, I imagine there is something more that prevents this, but I thought I would ask. I did not know if this path would lead to more program memory in addition to storage memory.

Delete references to TRUEFFS_DOC1
I decided to do a separate post for each trial.
I have edited my boot.rgu, boot.hv and default.hv to remove references to TRUEFFS_DOC1 (the extended ROM). As expected, I cannot see extended rom in total commander. I did not notice a jump in total memory on the phone. I did not notice a change in battery consumption.

Change TRUEFFS_DOC1 settings to be more like TRUEFFS_DOC2
I basically changed TRUEFFS_DOC1 (changed to call it StoROM) settings to match TRUEFFS_DOC2 (regular memory) except I did not set it as "root".
It shows up as removable storage with 4.9 MB of space.
I suspect something in TRUEFFS driver or I am missing a setting to tell it that is is not external memory.
I tried again, but named it "My Documents"
Word and excel would see the template files in My Documents\Templates twice. I could not set word's default file type. No choices showed in the option. I tried moving the templates, but then they could not be seen by word or excel.
Tried sync with my PC. What was already on the phone would not copy to the PC. I added things to the folder on the PC and they would add to the phone. If I deleted it off the phone, instead of deleting it off the PC it would put it back on the phone. If I copy a file from my phone to the my documents folder on the phone it would not show up on the PC. So it seems I have one-way sync capability.
I tried again, but named it "Program Files"
It works, but whatever gets written there stays so I had problems when I did a hard reset. I solved by deleting contents of folder before hard resetting.
Currently testing named to "FileSafe"
I can put files there and they do not get lost in a hard reset.
I am currently testing battery consumption on this latest format. First day, but after 5 hours only down to 91%. Will need to wait because I have noticed battery goes down faster as the level gets lower.
I did a soft reset and ended up with Storage card as a folder in root and storage card2 as the storage card. Cannot delete it since I have reg settings made to locate internet explorer files to storage card.
I'll have to keep tweaking settings.

More about Trueffs driver
I came across a package called "DiskOnChip(R) TrueFFS(R) Uilities package"
This Package includes the TrueFFS Version 6.3.2 Utilities Package
Reading the documentation gives me the impression that the chip is formatted at the factory and we cannot change the partitions. I suspect (stating again) that we only tell the software what to do with the partition. I tried to run the utility, but it could not find the chip to even do a read function.
It also looks like you have to have a password to gain access to parts. I do not fully understand this stuff, but I was reading about locking partitions with a password.
This may be why even though I have the format flag set in TRUEFFS_DOC1 it does not get formatted and as a result the things stored there are still there after a hard reset. Also, why it shows up as removable media even though I do not see where I tell it that it is such. I think anything other than the root is considered "external" and shows up as a storage card.

Explanation added
I added an explanation for this thread to the first post

Updated post #7 about FileSafe.

I have tried every which way I can think and can only create a folder that the phone considers a removable storage device. I keep getting the storage card2 problem so I have gone back to regular settings and installed a blank Ext_ROM.
I am fairly sure of my theory that the partitions are formated at the factory and we are only telling the software what to call them and how to access them. We cannot change what they have been set to at the factory.
I welcome any clarification from someone who knows more.
Hopefully this will help others like me who come in late in the game and wonder why we cannot get things like BigStorage, etc. other than just seeing people saying it cannot be done.

I read about hiding and unhiding the Ext-ROM, too. Unhiding and reading was no problem but writing didn't work.
Converting Ext-ROM to program-memory may not be possible, because AFAIK program-memory is SD-RAM and the Ext-ROM is Flash-MEMORY. But there are more ways the memory of the Ext-ROM could be usefull.
More space for the ROM (max. 57MB for OS.nb is not much when cooking a WM6.5 ROM) would be nice.
OR
A storage-partion like Ext-ROM but with write access!
Only unhiding the Ext-ROM didn't do the job! I could read from the Ext-ROM but couldn't write. After a write attempt the file list got corrupted and I had to hide and unhide again to get read access back.
If I understand the posting right, RoryB was already able to write to the Ext-ROM. How did you do that?
There is one more Problem! Not the MiniSD-Card but the Ext-ROM should get the name "StorageCard 2" (or any other name which comes alphabeticaly after StorageCard). Why? The Camera can save to different locations but you can only choose from 2: Main memory and the alphabeticaly first storage card.
My questions:
1. How do I get read, write and delete access to the Ext-ROM?
2. How can I rename this "Ext-ROM-Storagecard"? Something like "StorageCard 2" or "StorageMemory" or ...
Update:
Answer for question 2 might be:
AbuYahya said:
To Rename EXT-ROM
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"Folder"=string:Storage
--- can call it anything you like instead of "Storage"
Click to expand...
Click to collapse
I didn't check it yet.

I have stopped trying to get Extended_ROM as storage space. I did use it as a filesafe location. I could not get access to all of the space even though I installed an empty Extended_ROM. Here is the part of boot.rgu I changed (best as I can remember)
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:0
"SoftwareWriteProtect"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="FileSafe"
"MountHidden"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I think the "Storage Card 2" problem comes about from the order in which the Extended_ROM and SD Card get recognized and for some reason it sees the Extended_ROM as a storage card.
I now use Extended_ROM that way Cingular did. I have files in it in the form of cabs and zips. These files are things like Adobe Reader as a cab, Template files as a zip, etc. I use my customization mortscript to install those files. This way I get more room in the ROM for things that have to be in the ROM. Here is the format I have for my boot.rgu
Code:
;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
; Does not seem right to me to be TRUEFFS_DOC1 when all others use the built in driver and not the profile
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS1]
"DriverPath"="Drivers\\BuiltIn\\TrueFFS1"
"LoadFlags"=dword:1
"Order"=dword:1
"Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS1]
"Profile"="TRUEFFS_DOC1"
"Index" = dword:2
"Dll" = "TrueFFS.dll"
"Prefix" = "DSK"
"Order" = dword:1
"Ioctl" = dword:4
"Use8Bit" = dword:1
"WindowBase" = dword:0
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"AutoDPDMode" = dword:1
"SoftwareWriteProtect"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"Folder"="Extended_ROM"
"MountHidden"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"FormatTfat"=dword:1
"EnableWriteBack"=dword:1
"DataCacheSize"=dword:00000080 ;128 sectors(128*512=64KB)
I use winimage to change the contents of my Extended_ROM.nb file. Now when I run nb2nbf I pick the OS and the Extended_ROM as files to write to the nbf.

G4 processors do not allow you to flash a custom extended ROM (IIRC).

jwzg said:
G4 processors do not allow you to flash a custom extended ROM (IIRC).
Click to expand...
Click to collapse
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.

RoryB's latest ROM that uses ExtRom for cabs and such works fine on my G4.
Ham3r's experimental ROM that provides ExtRom as a read/write filesystem works on G3.
I even installed apps onto ExtRom, with no problems.
I don't know about its relative speed.
It is marked "G3 only" so I have not tried it on my G4.
If someone is brave enough to show that the Ham3r rom's method works on G4, that would be a great feature.
I think that making the most of extrom as a filesystem is the best we can do.

Cyberdyne said:
That is just not true! In my WM6.5 ROM there is a custom Ext-ROM included and I have no problem flashing it to my G4 Wizard.
G4-Save means no IPL/SPL but Ext-ROM is not a problem.
@RoryB:
Thank you for the information. I will try it.
Click to expand...
Click to collapse
For some reason I was thinking it wouldn't flash. I haven't touched my Wizard in a while, and my XP computer with my kitchen on it is dead. I'll have to upgrade my WM6 ROM again.
Mods ain't gods. I stand corrected.

[UTIL] One Click Lag Fix 2.0 by RyanZA

i seen this in the Samsung Galaxy S I9000 and i tried it out on the vibrant and it works perfect, its probably the easiest way to partition your SD card and i can confirm it fixes the lag, i will post my scores shortly...... THANKS RYANZA you saved me weeks of research. go here for more info
http://forum.xda-developers.com/showthread.php?t=751864
[UTIL] One Click Lag Fix 2.0
This version (2-3) is now open for BETA testing! It is known to work on many devices, but still has known issues that could greatly affect you. Please read this whole post a few times until you understand!
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
/data/app
/data/app-private as a symlink to /data/app/app-private
/dbdata/databases is not supported. It appears to be ROM backed, and can cause problems if overwritten.
Benefits over version 1
1.5GB of application data available, with no data loss.
e2fsck of the EXT2 partition on each boot.
Correct busybox version included! YES!
/app and /app-private directory included in the fix for faster application installs.
/dbdata/databases included in the fix, expected to give a big performance boost for apps that use it.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
Benefits over other lag fixes
Open source, with full comments and ease of editing.
Works on any and all firmware versions, including any yet unreleased froyo versions (that don't change file structure).
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Big thanks to cyanogen mod for e2fsck
Requirements for One Click Lag Fix 2.0
Rooted phone - http://www.addictivetips.com/mobile/how-to-root-and-unroot-samsung-galaxy-s-i9000-with-a-single-click/
Windows computer with SGS Drivers (Samsung Kies), or the ability to read through the batch file and run it yourself.
(Beta Release) The ability to reflash your device if something goes wrong.
No other lag fix installed. If you installed One Click Lag Fix 1.0, then use the uninstall function which came with that lag fix before running this lag fix. (Untested but assumed to be working, please help out here.)
1.5GB of freespace on Internal SD Card for swap files while the fix is working (/sdcard).
"Internal phone storage" in Settings->SD Card must read greater than 500mb (0.5GB) of free space.
How to run One Click Lag Fix 2.0
Place your phone into USB debugging mode: Settings->Applications->Development
Attach your device to your computer. Do not mount the drives.
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat".
Don't double click "unlagfixme.bat".
Wait for it to complete.
You will need your phone to be unlocked when it runs the script, so that you can accept the permissions request that will appear on your device.
How to remove One Click Lag Fix 2.0
Double click "unlagfixme.bat"
Wait for it to complete.
Known Issues For All Versions
Some custom firmwares use up all available space in /system. This fix requires some libraries to be placed in /system/lib. These libraries are used to create the filesystem properly, and to check it for errors on every boot.
If your firmware does not have the available space (around 1mb) in /system, do not use this fix! Your phone will not boot and will have to be restored from backup / reflashed.
Current known firmwares with this issue: None yet. Please provide the firmware version+mods if you encounter this issue. It will show up as an out of space error in the log, under 'Copying libraries'.
Known Issues 2-1, 2-2
Paid apps from the market have issues.
Google maps and other pre-installed ROM-backed applications have issues.
2-3 Changes from 2-2
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
Alternate installation methods for similar fixes
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/show...&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513

I recommend starting from scratch to avoid any problems
my setup is
1.) True 2.1 Samsung T mobile Image http://tinyurl.com/2bc5b6r
2.)BETA OC 1.2Ghz (no added steps for now)
kernel-vibext4-oc1.tar.md5
MD5:d1e26f769406c5d368492855c7b5059e
...you can try his new version of the kernel if you like, my phone i runs fine on the beta , so i havent tried the new ones
more info on the kernal hack http://forum.xda-developers.com/showthread.php?t=744655
3.) RyanZAEXT2LagFix BETA 2-3.zip http://forum.xda-developers.com/attachment.php?attachmentid=384443&d=1282320979
this is the exact order in which i modded my phone and i have no ran into any problems, it was a smooth process , and yes it was my first time modding my samsung phone and i rate it as very easy to do.
Click to expand...
Click to collapse
Frequently Asked Questions
Q: My apps are force closing while this fix is running, and I can't use my phone!
A: By design. The script has backed up/copied your apps over to the internal SD card (remember the requirement about 1.5GB of free space on the SD card?). It is now overwriting them with a 1.5GB file. As the file overwrites an app that is trying to do something, it will probably force close. This is normal.
Closing all running apps, and removing widgets before running this fix can make the process much smoother, though.
Q: The script can't transfer files to my phone / The script can't run / Help help I'm dieing!
A: Read the first post again.
Q: My paid apps from the market don't show up.
A: I will hopefully have a fix for this sooner or later. Hold tight! It's in the known issues. I don't have access to paid apps, so I can't test this.
Q: Does this need busybox?
A: No, busybox is included.
Q: I only have 200mb of free space now! What gives?
A: The lag fix has made a 1.5GB file, and is storing all of the data inside there. The side effect is that the free space meter is now incorrect. Sorry, this can't be helped.
You can check real free space by using ADB like this:
Code:
adb shell
su
busybox df -h
Q: When I use a backup tool, the backup is now 1.5GB big! It's taking forever!
A: The backup tool isn't designed to work with this fix. It will work, it just won't work well. Hopefully this fix will be short lived, and either Samsung will give us a new update, or someone will give us a good custom firmware that can natively mount what we need, where we need it. Or someone might come out with a better backup manager. Until then, we suffer.
Q: Will a reflash wipe this fix?
A: Yes, a reflash will wipe everything this fix did.
Q: Can this brick my phone?
A: If you know how to get to the download mode from power off (hint: volumedown+home+power), then almost nothing short of throwing your phone off a tall building can actually brick it. If you can't do this though, or don't know someone who can, then you're better off waiting for samsung to release a fix. Anything that moves files around on your device has the potential to break things, and this fix has no QA department.
Q: Why is /dbdata not included in your fix, but other people have included it?
A: Other people have included it in the same way my 2-2 fix includes it. However, /dbdata is ROM backed. This means that the real files are on ROM, and only the changes appear in the /dbdata folder. When copying or moving files from this folder, you would need to specify each folder by exact name to ensure that it was copied across, and each firmware can have their own names. (This is because RFS wildcard will not catch an unused ROM backed file.) In some cases, you can get lucky and have this work perfectly because you have already used all the files in /dbdata. There is no fail safe method to do this though, and /dbdata does not make a big difference to performance. (It is already on NAND flash.) If you want to try your luck, v2-2 is still available.
Q: Why does this lag fix work? Is it slowly destroying my phone?
A: Let's say an application counts from 1 to 10, and writes the value each time to disk.
Stock:
1 -> App tells RFS to write 1 to disk -> RFS writes 1 to disk -> RFS writes journal saying to changed the value on the disk.
2 -> App tells RFS to write 2 to disk -> RFS writes 2 to disk -> RFS writes journal saying to changed the value on the disk.
..
9 -> App tells RFS to write 9 to disk -> RFS writes 9 to disk -> RFS writes journal saying to changed the value on the disk.
10 -> App tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 20. Speed: SLOW! Wear and tear on disk: HIGH!
Lag Fix:
1 -> App tells EXT2 to write 1 to disk -> EXT2 stores 1 in RAM.
2 -> App tells EXT2 to write 2 to disk -> EXT2 stores 2 in RAM.
..
9 -> App tells EXT2 to write 9 to disk -> EXT2 stores 9 in RAM.
10 -> App tells EXT2 to write 10 to disk -> EXT2 stores 10 in RAM.
..
EXT2 tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 2. Speed: FAST! Wear and tear on disk: LOW!
This isn't exactly what is happening, but it gives you the general idea.
Q: Can this mod work on other Android devices? Would we see a performance boost on them as well? If not why is it limited to the Galaxy S?
A: SGS has very very good hardware, but it has some parts of it's hardware poorly implemented. The filesystem that samsung chose to use is custom-built using FAT32 as a base, RFS. It has a lot of the problems that FAT32 has, and should have been left back in the 90s, or even the 80s.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your twitter app is busy writing a new tweat it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweat, it got 50 tweaks. It is busy writing the tweats one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This is mostly speculation based on experiments done on RFS -- RFS is closed source, and we have no idea if the problems are just badly set settings (such as a block size that is too small), coding bugs in the implementation, or if RFS is just really that badly designed.
This fix just grafts a buffer on top of the RFS filesystem, using a very very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
So no, this fix won't fix other devices, since they're already running quite close to maximum speed. The SGS at stock is running nowhere near maximum speed, and this lag fix takes it a bit closer. You could probably speed up other devices by tweaking the filesystem settings to give them a big buffer or similar, but it isn't really needed. (I haven't actually tried to put an EXT2 onto any other Android phone, as I don't have any other Android phone, so this is just speculation.)
Q: My phone is fast now!
A: Yeah.
Last edited by RyanZA; 18th August 2010 at 10:52 PM..

I used this yesterday. Works a treat! Just be patient when its running.
Texted While Driving

You need to fix the links if you reposted it

lqaddict said:
You need to fix the links if you reposted it
Click to expand...
Click to collapse
i fixed the links before i reposted it and re-added the attachments , is there a certain link i forgot to fix ?

===============================================================
===============================================================
One Click Lag Fix for Galaxy S I9000
===============================================================
===============================================================
__________________________________________________________
Pushing required files to /sdcard - Please wait.
* daemon not running. starting it now *
* daemon started successfully *
mkdir failed for /sdcard/lagfixtemp, File exists
cannot stat 'createlagfix.txt': No such file or directory
cannot stat 'playlogos1': No such file or directory
cannot stat 'userinit.sh': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'e2fsck': No such file or directory
cannot stat 'libext2_blkid.so': No such file or directory
cannot stat 'libext2_com_err.so': No such file or directory
cannot stat 'libext2_e2p.so': No such file or directory
cannot stat 'libext2_profile.so': No such file or directory
cannot stat 'libext2_uuid.so': No such file or directory
cannot stat 'libext2fs.so': No such file or directory
cannot stat 'mke2fs': No such file or directory
cannot stat 'resize2fs': No such file or directory
cannot stat 'tune2fs': No such file or directory
Now running lag fix. On your device, select allow root privledges!"
/system/bin/sh: Can't open /sdcard/lagfixtemp/createlagfix.sh
Script complete!
* server not running *
Press any key to continue . . .
any help?

did you unzip the files and put them all in the same directory ???
bobby915 said:
===============================================================
===============================================================
One Click Lag Fix for Galaxy S I9000
===============================================================
===============================================================
__________________________________________________________
Pushing required files to /sdcard - Please wait.
* daemon not running. starting it now *
* daemon started successfully *
mkdir failed for /sdcard/lagfixtemp, File exists
cannot stat 'createlagfix.txt': No such file or directory
cannot stat 'playlogos1': No such file or directory
cannot stat 'userinit.sh': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'e2fsck': No such file or directory
cannot stat 'libext2_blkid.so': No such file or directory
cannot stat 'libext2_com_err.so': No such file or directory
cannot stat 'libext2_e2p.so': No such file or directory
cannot stat 'libext2_profile.so': No such file or directory
cannot stat 'libext2_uuid.so': No such file or directory
cannot stat 'libext2fs.so': No such file or directory
cannot stat 'mke2fs': No such file or directory
cannot stat 'resize2fs': No such file or directory
cannot stat 'tune2fs': No such file or directory
Now running lag fix. On your device, select allow root privledges!"
/system/bin/sh: Can't open /sdcard/lagfixtemp/createlagfix.sh
Script complete!
* server not running *
Press any key to continue . . .
any help?
Click to expand...
Click to collapse

djkdawg said:
did you unzip the files and put them all in the same directory ???
Click to expand...
Click to collapse
i extracted all files to desktop and ran lagfix.bat from there

bobby915 said:
i extracted all files to desktop and ran lagfix.bat from there
Click to expand...
Click to collapse
do you have usb debugging enabled? do you have any other lag fix installed ?

djkdawg said:
do you have usb debugging enabled? do you have any other lag fix installed ?
Click to expand...
Click to collapse
Got it working thanks

bobby915 said:
Got it working thanks
Click to expand...
Click to collapse
no problem, download the quadrant standard app and run the test and post your score

I got 2072 quadrant score for the phone after the fix, how did the OP manage to get 2700+?

I'm still on version 1 with no issues. Any major differences or Improvements.

Uninstalled the Alpha fix and tried this one. upon reboot, I'm getting an error:
Memory Full
Internal phone storage is nearly full
Delete/Uninstall some applications or data
Didn't have this problem with the alpha fix.
Guess I shouldn't had played with the beta.
Any ideas?
Running Stock Kernel, just rooted.
I'm running Unlagfix now to remove.
Side note: I noticed that my custom font settings disappeared... Icons still appear to be in the same place.
Update:
I just re-read the FAQ. Storage reporting error... heh.. doh.
However, when running uninstall, it started streaming the following error message about 20-30 times over:
cp: write error: No space left on device.
Can't create directory 'data/bak/app': No space left on device
Update again:
Unlagfix didn't seem fully successful. All my application data/etc disappered. Looks like they are still in the /data/ directory, but not showing up on the device.
Here is a listing result
If I'm reading this correct, does that mean the Unfixlag didn't complete it's task? Looks like I still have a 1.5gb partition for data.

Tairen said:
I got 2072 quadrant score for the phone after the fix, how did the OP manage to get 2700+?
Click to expand...
Click to collapse
i started from scratch, i flash the true tmobile vibrant image to start from scratch, you dont have to do this but i did. Link is below
http://tinyurl.com/2bc5b6r <-- true tmobile vibrant image, it also includes odin
after that was done, i used the utility to format my card, you can get the one click utility below
http://forum.xda-developers.com/showthread.php?t=751864
after that i reboot, install the app and did a test and thats how i got my speeds.
edit: after installing all my apps back, i actually average about 2400-2500 , i havent seen the 2722 after installing all my apps

i would start from scratch like i did when i first tried it, because i think the other lagfixes actually jacked something up. follow the steps below
i started from scratch, i flash the true tmobile vibrant image to start from scratch, you dont have to do this but i did. Link is below
http://tinyurl.com/2bc5b6r <-- true tmobile vibrant image, it also includes odin
after that was done, i used the utility to format my card, you can get the one click utility below
http://forum.xda-developers.com/showthread.php?t=751864
after that i reboot, install the app and did a test and thats how i got my speeds.
Spiffywerks said:
Uninstalled the Alpha fix and tried this one. upon reboot, I'm getting an error:
Memory Full
Internal phone storage is nearly full
Delete/Uninstall some applications or data
Didn't have this problem with the alpha fix.
Guess I shouldn't had played with the beta.
Any ideas?
Running Stock Kernel, just rooted.
I'm running Unlagfix now to remove.
Side note: I noticed that my custom font settings disappeared... Icons still appear to be in the same place.
Update:
I just re-read the FAQ. Storage reporting error... heh.. doh.
However, when running uninstall, it started streaming the following error message about 20-30 times over:
cp: write error: No space left on device.
Can't create directory 'data/bak/app': No space left on device
Update again:
Unlagfix didn't seem fully successful. All my application data/etc disappered. Looks like they are still in the /data/ directory, but not showing up on the device.
Here is a listing result
If I'm reading this correct, does that mean the Unfixlag didn't complete it's task? Looks like I still have a 1.5gb partition for data.
Click to expand...
Click to collapse

Just a heads up!
A new version is available for people having trouble with this lag fix, check it out here:
http://forum.xda-developers.com/showthread.php?t=760571
It is designed to be easy to use and a lot safer.

Just wanted to say thanks to djkdawg for posting this and RyanZA for all the work!

im having font issues how about anyone else? i had choko cooky as my default and now it doesnt work anymore...
edit: no fonts work...

Code:
Making new directories to use as mount points for later.
We will now create a 1.5GB real EXT2 partition /data
Will take a long time.
dd: /data/linux.ex2: No space left on device
Linking loopback to the 1.5GB data file store
Creating the EXT2 filesystem
mke2fs 1.40.8 (13-Mar-2008)
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
Creating a mountpoint for files.
Mounting device
mount: Invalid argument
Copying data across. This could take a bit of time.
I keep getting this error when attempting to install. Not sure what's going on. I've got 8.5gb free on internal memory before beginning install. That should be plenty.

[Q] some .exe that could be removed from most himalaya rom's ?

i have found some .exe in most himalaya rom's "\Windows" folder that seem too be not needed so they could be deleted from future kitchens and stuff.
anyway here they are with screenshots..
1.sms_alert_fix.exe-pretty obvious.
2.SimLock.exe-i think something to do with unlocking sims (eventhough i've never used it).
3.cgacutil.exe-it shows you what version of NetFrameWork you are running (not sure if it gets installed as defult when NetFrameWork is installed.
4.hwhelp.exe-seems to be left from the keyboard option of character recognizer.
5.wrlsmgr.exe-maybe a part of the himalaya wireless driver.
can these be removed or deleted safely?
any ideas?

advanced15 said:
i have found some .exe in most himalaya rom's "\Windows" folder that seem too be not needed so they could be deleted from future kitchens and stuff.
anyway here they are with screenshots..
1.sms_alert_fix.exe-pretty obvious.
2.SimLock.exe-i think something to do with unlocking sims (eventhough i've never used it).
3.cgacutil.exe-it shows you what version of NetFrameWork you are running (not sure if it gets installed as defult when NetFrameWork is installed.
4.hwhelp.exe-seems to be left from the keyboard option of character recognizer.
5.wrlsmgr.exe-maybe a part of the himalaya wireless driver.
can these be removed or deleted safely?
any ideas?
Click to expand...
Click to collapse
SMS_Alert_Fix will revive your phone when you will get a sms.
Simlock is really weird.
cgacutil is funking needed.
hwhelp is not needed but I don't want to know what will happen when deleted
wrlsmgr is needed for people who have SDIO Wifi card which himalaya support.

thats it then SimLock.exe is getting deleted and i will see what happens!

Here is what I removed to get free sectors in My WM6.1. The only way to learn effectively is: trial and error. Next try to read and understand the registry. It's all in there.
http://www.mediafire.com/file/xonmumuhkmy/Removed.rar

muckelmaus said:
Here is what I removed to get free sectors in My WM6.1. The only way to learn effectively is: trial and error. Next try to read and understand the registry. It's all in there.
http://www.mediafire.com/file/xonmumuhkmy/Removed.rar
Click to expand...
Click to collapse
msim is keyboard right?
wisplite is totally unneeded, you can delete it but don't forget to delete registry entries in shell

also i know these can be deleted bcuz they are to do with error reporting and feedback-
DwXfer.dll
dw.exe
ceipui.exe
and also this-
BackPack.dll
hey muckelmaus these are needed for keyboard-
msim.dll
msim.96.dll
this for the 4 dots you have to tap when you first start up a new rom-
welcome.exe
and this is one of your splash screens-
welcomehead.96.png
and this is used for the search device for file function-
shfind.exe
otherwise i cannot see any problem with deleteing the rest of them...

i have also found this on a other part of xdadev-
*
Hd.dll
*
Aosaxst0.dll
*
Mencfilt.dll
Here Hd.dll and Aosaxst0.dll are used for M$ debug. Like some times on pc the apps close itself, and windows asks you to send the details to M$ (example. error number : 893647). We ( users) don’t know what it means, only the developer in M$ know. But I never saw these files report anything to us. SO!!! We don’t need them! they are trash!!
Now Mencfilt.dll is for storage card encrypt. If you don’t use it, you can delete it as well. Have you had this experience where after flashing a new Rom every thing in storage card can’t show any more!!!! but its still use the space in the card. Yes it's because of this file only.
**NOTE: There are some device in which removing these files causes system issues so be careful. But only a few devices

advanced15 said:
also i know these can be deleted bcuz they are to do with error reporting and feedback-
DwXfer.dll
dw.exe
ceipui.exe
and also this-
BackPack.dll
hey muckelmaus these are needed for keyboard-
msim.dll
msim.96.dll
this for the 4 dots you have to tap when you first start up a new rom-
welcome.exe
and this is one of your splash screens-
welcomehead.96.png
and this is used for the search device for file function-
shfind.exe
otherwise i cannot see any problem with deleteing the rest of them...
Click to expand...
Click to collapse
As I used a german 'qwertz' keyboard and a smaller splash screen, these files are just overwritten in my rom. These are backups.
I skip the Touchscreen alignment at first bootup (it doesn't work anymore after changing initflashfiles.dat)
Did you ever try to use * as a joker with the search program? Totally useless, so it is overwritten by a better app, renamed to: shfind.exe.

muckelmaus said:
As I used a german 'qwertz' keyboard and a smaller splash screen, these files are just overwritten in my rom. These are backups.
I skip the Touchscreen alignment at first bootup (it doesn't work anymore after changing initflashfiles.dat)
Did you ever try to use * as a joker with the search program? Totally useless, so it is overwritten by a better app, renamed to: shfind.exe.
Click to expand...
Click to collapse
You did something wrong if touchscreen alignment does not work after rewriting initflashfiles.

aeroflyluby said:
You did something wrong if touchscreen alignment does not work after rewriting initflashfiles.
Click to expand...
Click to collapse
It didn't bother, everything worked 'till I deleted some files in startmenue and rearanged the programs. But noone told me that he missed the feature. Approximately 300 users over all. Even if some of them only tested. For me it was OK, and I'm still running it from the very first day, without any need of a new hard reset 'till now.

muckelmaus, why do you have a smaller startup screen?

I reduced the size of the files to get some kB/sectors free, as my rom is full of third party apps.

muckelmaus said:
I reduced the size of the files to get some kB/sectors free, as my rom is full of third party apps.
Click to expand...
Click to collapse
As I remember you can put JPG file as welcomehead
there is 2 solutions:
Save as jpg file and then just rename into .png
Save as jpg and change registry entry in redist dpi 96
by the way:
look at this:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Splash Screen]
"MSBitmap"="\\windows\\welcomehead.96.png"
"MSTimeout"=dword:7530 ; 30000 milliseconds
"CarrierBitmap"="\\windows\\welcomehead.96.png"
"CarrierTimeout"=dword:7530 ; 30000 milliseconds
Click to expand...
Click to collapse
maybe we could have 2 splash screens and change their duration on screen
So, when combined with bootloader 2 splashes (as I post tutorial to change it easly) we can have 4 splashes.
Good for doing PC boot images as I did before hima died my work in attachment
(I know that hima does not have AMD Althon but it seems good)

simlock.exe
simlock.exe is all ok too delete...
no problems deleting in AK6.

advanced15 said:
simlock.exe is all ok too delete...
no problems deleting in AK6.
Click to expand...
Click to collapse
hwhelp.exe - is ok to delete as well
done in AK6 ,no problems !

[Q] un-deletable 0kb files HELP !

Greetings from sunny ??? nottingham
I have a folder with a bunch of files that all show as 0kb that i can not remove.
Does anybody have an idea how i can get rid of these?
The story so far....
I am/was on rocket rom v2, previously i had put the google currents app on, but that was a couple of roms ago and i have not put it back.
I started having a few odd problems and realized my int sd was full. i eventually narrowed it down to a google currents folder. this was not so easy as any app that tried to scan the int sd in any way would crash or freeze. Even in manage apps it would only show details of apps from a to c any after that hung on 'computing'. i managed to delete over 5 gb from that folder, all except one folder.
Now i am left with a folder on the int sd inside the android/data folder called 'com.google.android.apps.currents' inside that is a folder 'cache' inside that a folder 'blobs.120.1184434912' inside that a folder thats a bunch of letters and numbers, inside that a folder 'att' and finally inside that a bunch of files all with single letters, numbers or symbols as there filename and all 0kb in size.
These remaining files and folders i can not get rid of.
I have tried....
Delete with root explorer and a couple of other file apps crash's or locks
Cut and paste elsewhere fail
Connect to computer and...
Delete fail
Move fail
Erase fail
Unlock freezes pc
Change permissions blocked
Re-name fail
Scanned with virus and spyware progs clean
Delete with dos fail
Factory reset fail
Factory reset with format usb crash's or locks
Flash a pit file in pc odin Still there
I wouldnt mind just leaving them there, but as i say any app that in any way scans the int sd crash's or freezes this makes the note almost un-useable.
I'm sure I've missed a few things i have tried but you get the point.
I have searched xda and the web as best i can and tried pretty much every idea I've come across.
Help !!!
Please !

What an odd problem....

have you tried aroma file manager?

Thanx p107r0
I havent tried that particular file manager, many others though.
Downloading it now, very busy next couple of days so will give it a go as soon as i can.
many thanx
have fun
all the best
rich

Cant you try copying all your important information off the sd then formatting it?
Sent from my GT-N7000 using Tapatalk

Thanx Postmonkeh
Unfortunatly i have formatted it several times now and those files still remain.

Are you familiar with adb tools? You could try using adb to delete the files.
Ftb

Hi Postmonkeh
Unfortunatly abd is over my head, i wouldnt have a clue what i was doing.
Maybe i need to do some learning Do you know if theres a basic tutorial anywhere ?
Many thanx
all the best
have fun
rich

It's fairly simple once you get the hang of it, but i don't know any guides off the top of my head.
Not on my laptop at the minute but once I'm downstairs I'll give you a quick run through of what to do to delete that folder. Might not work, but then again it might
Ftb

Hey mate thank you very much.
Please dont rush as i am just leaving and will be away for a couple of days. I will get onto it as soon as i return.
Many thanx
Rich
Sent from my GT-N7000 using xda premium

it won't let you rename or delete because they reside on googles servers, that's why they are showing 0kb. u can't change permission because it's on sd card and w don't have the ability to do so on sd card. i promise a format got rid of them but u didn't notice it because google cache server put links back as your phone started. the explorer crashes because as fast as is trying to remove them the server is already putting them back. basically what im trying to say is just ignore them cause there not really there anyways.
Sent from my SPH-D710 using xda premium

veritasaequita said:
it won't let you rename or delete because they reside on googles servers, that's why they are showing 0kb. u can't change permission because it's on sd card and w don't have the ability to do so on sd card. i promise a format got rid of them but u didn't notice it because google cache server put links back as your phone started. the explorer crashes because as fast as is trying to remove them the server is already putting them back. basically what im trying to say is just ignore them cause there not really there anyways.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
dik64 said:
I wouldnt mind just leaving them there, but as i say any app that in any way scans the int sd crash's or freezes this makes the note almost un-useable.
Click to expand...
Click to collapse
as above, these files seem to be causing problems.
my google currents folder has a lot of these folders, but none of the files are empty.
although having said that, it may be an idea to deselect the option to have google back up your app data.
i'd also maybe try installing the currents app then (if you can) go into the app settings and clear the data.
---------- Post added at 01:16 PM ---------- Previous post was at 12:35 PM ----------
http://forum.xda-developers.com/showthread.php?t=1241935
that thread gives a good guide to getting adb installed, and gives a good grounding of what it can do. it's a bit more in depth than what you need though, all you need is to install it, add the path to the environment vaiables as described in that thread (that is an optional step but it makes things much easier)
the path you'll be looking for is /mnt/sdcard/Android/data/com.google.android.apps.currents
be sure to remember that the case of the letters in the linux (and therefore android) file systems is vital - ie mnt/sdcard/Android is an entirely different folder than mnt/sdcard/android.
so basically once you've your note connected (with the screen unlocked) open a command line and type (minus the quotes) "adb devices"
it should (hopefully) list your note in there.
then type these commands in order, being careful to observe the correct case when typing filenames or folder names.
adb shell
rm -r /mnt/sdcard/Android/data/com.google.android.apps.currents
it could take a while if there are a lot of files. once it's finished, you should be back to a line with a flashing cursor, then just type exit and it should take you back to your standard windows command line.
i would try taking off the "back up my settings to googles servers) and installing currents and wiping the data first though.

OK time for an update.....
Aroma file manager same as all the others, it either freezes or crash's out altogether.
I have already deselected back up to google, no effect.
I have already tried re-loading google currents and populating it with fresh downloads. Then clear data and un-install, no effect.
Finally took me a while to get adb set up and working, but............
wait for it............................................................................
No effect !!
It starts the process, and scrolls info very fast. I left it for about 20 mins and it was still going. eventually i clicked on the window and it said something along the lines of no such file or directory then endlessly scrolls att.
I appreciate the suggestions given, but i do hope there are some more.
I am completely lost with this now.
all the best
have fun
rich

Seems kind of similar to problems I used to have in the good old Palm OS days, sometimes due to some app errors 0b files would appear on SD card, and - to make long story short - the only thing that would help was taking the card out and formatting it on the computer.
Maybe flashing with repartitioning could help?
Sent from my GT-N7000 using xda premium

dik64 said:
Greetings from sunny ??? nottingham
I have a folder with a bunch of files that all show as 0kb that i can not remove.
Does anybody have an idea how i can get rid of these?
The story so far....
I am/was on rocket rom v2, previously i had put the google currents app on, but that was a couple of roms ago and i have not put it back.
I started having a few odd problems and realized my int sd was full. i eventually narrowed it down to a google currents folder. this was not so easy as any app that tried to scan the int sd in any way would crash or freeze. Even in manage apps it would only show details of apps from a to c any after that hung on 'computing'. i managed to delete over 5 gb from that folder, all except one folder.
Now i am left with a folder on the int sd inside the android/data folder called 'com.google.android.apps.currents' inside that is a folder 'cache' inside that a folder 'blobs.120.1184434912' inside that a folder thats a bunch of letters and numbers, inside that a folder 'att' and finally inside that a bunch of files all with single letters, numbers or symbols as there filename and all 0kb in size.
These remaining files and folders i can not get rid of.
I have tried....
Delete with root explorer and a couple of other file apps crash's or locks
Cut and paste elsewhere fail
Connect to computer and...
Delete fail
Move fail
Erase fail
Unlock freezes pc
Change permissions blocked
Re-name fail
Scanned with virus and spyware progs clean
Delete with dos fail
Factory reset fail
Factory reset with format usb crash's or locks
Flash a pit file in pc odin Still there
I wouldnt mind just leaving them there, but as i say any app that in any way scans the int sd crash's or freezes this makes the note almost un-useable.
I'm sure I've missed a few things i have tried but you get the point.
I have searched xda and the web as best i can and tried pretty much every idea I've come across.
Help !!!
Please !
Click to expand...
Click to collapse
If you cannot delete the folder with del or erase command in dos I think you have a bad block there. In this case you have to leave this folder alone.

Hi, thanx for the further suggestions
tknguyencsu leaving alone is not a good idea as it does affect how the note works. Anything that scans the int sd freezes or crash's out when it gets to that folder. for instance if i go to manage applications it will only give me detailed info on apps from A to C any after that it wont display the size of data etc, just stays on 'computing'. so i really need to get rid of this folder.
p107r0 Any idea how i try your suggestion of 'flashing with repartitioning' ?
I have done several full wipes inc usb storage, i have formatted usb storage from recovery several times also.
There are a couple of options in recovery i have not tried because i dont know what they really mean and so im a little scared to try with all the bricking thats been going on.
many thanx
all the best
have fun
rich

Lots of reading to be safe, but afair there is Dr ketan's guide on flashing LBF with repartitioning, which should be theoretically safe when performed from/over GB ROM. I'll look for the link later.
Here.
P.S. There's also app by chainfire which checks if your device is prone to superbrick: Got Brickbug
Sent from my GT-N7000 using xda premium

Thanx p107r0 i've had a quick look/search in that thread. Not much detail about re-partitioning, i am now assuming it is connected with pit file ?
If that is correct then i have tried that and unfortunatly it did not help.
I am out of my depth here, so if i have misunderstood please forgive me, and enlighten me.
many thanx
all the best
have fun
rich

Are you still on the same ROM? Maybe formatting int sd from other one would do the trick?

Hi p107r0
Yes i am on the same rom, but now a later version.
I am using Rocket Rom. the problem first came to light after upgrading from v1 to v2. since then i have been back to GB to RR v1, RR v2 and am now on RR v3.
I am out of time tonight, and on the road all day tomorrow, so will try a completely different rom as soon as i can.
many thanx
all the best
have fun
rich

File/Folder transfer from PC to Phone

Just wanted to see if anyone else has had this problem and might know of a fix. I didn't need a full data backup when formatting userdata to get rid of encryption so I just grabbed a few folders from the internal storage that I wanted to have to put back afterwards. When I tried to transfer them back from the PC most transferred with no problem, but there were some that would not transfer. They would either error out and I would get a popup saying something like Nexus 6 is busy or no popup and just a windows error sound with no attempt to even try to transfer. But I could go into recovery with the folders on a usb drive and copy them over with file transfer. Any ideas?? TIA

Yes. Try not to start another copy operation while you have one in progress, because from experience with this issue you will have the entire connection time out if you attempt it. It's also best to limit the number of folders you attempt to copy at one time.

Strephon Alkhalikoi said:
Yes. Try not to start another copy operation while you have one in progress, because from experience with this issue you will have the entire connection time out if you attempt it. It's also best to limit the number of folders you attempt to copy at one time.
Click to expand...
Click to collapse
Roger that....I did try one folder at a time after trying to move all at once. The ones that had no problem transferring in the bulk transfer went fine even by themselves, But the ones that would error out during that transfer would still not transfer by themselves...Mostly folders that were going back into the android folder. But there were some just going into the root directory that would error out also.

That could be because of path name limits in Windows. A single file in Windows cannot have its path plus its file name be more than 255 characters. I believe Linux also has such a limit, but theirs is much larger.

Strephon Alkhalikoi said:
That could be because of path name limits in Windows. A single file in Windows cannot have its path plus its file name be more than 255 characters. I believe Linux also has such a limit, but theirs is much larger.
Click to expand...
Click to collapse
Ahhh yes....Could be that, but usually it will put up an error saying so. But still could be the culprit....Any way around it that you have found?

@Jeffro64: Sorry for the late reply. The only thing to do in that instance is to drill down a level or two so you can get under the 255 character limit and copy files that way.

Strephon Alkhalikoi said:
@Jeffro64: Sorry for the late reply. The only thing to do in that instance is to drill down a level or two so you can get under the 255 character limit and copy files that way.
Click to expand...
Click to collapse
Not a problem at all thanks for trying to help. So are you saying go in a level or two and find the same folder (If it's there on a new install) on the phone and copy only the deeper levels?

Yes.

Strephon Alkhalikoi said:
Yes.
Click to expand...
Click to collapse
Roger that...I'll give that a try next time. Thanks again for your help!