Database Info

Extended Rom, BatteryStatus, Battery Life

Ok, I have been reading a lot about bad battery life using BatteryStatus, and wanted to let people know some observations I've made which might be helpful.
1) BatteryStatus is a nice program, but it's erratic. It has to be watched. Especially after a reset, or after recharging, you need to be careful that it's actually doing what you want it to. For example, if you use cpuscalar, it will turn off when you set the cpu speed and vice versa, especially if you access the settings from the Today screen. I recommend using the 1.x versions as you can monitor cpu utilization, and can see if the cpu speed is going up or down based on your settings.
2) On that subject, use cpu utilization and not battery load as your primary indicator. If you're getting above 10% cpu load "at rest", something is probably not right with your setup. Which leads me to ...
3) I have discovered that if one wipes the extended rom, you will have high cpu utilization rates (I got 20% at idle with the x-plore rom, vs 1-4% clean, with an extended rom) Apparently there is some process which checks for the Autostart.exe file in extended rom, and keeps checking if it does not find it. This can't be good for battery life.
Hope this helps someone,

edhaas said:
3) I have discovered that if one wipes the extended rom, you will have high cpu utilization rates (I got 20% at idle with the x-plore rom, vs 1-4% clean, with an extended rom) Apparently there is some process which checks for the Autostart.exe file in extended rom, and keeps checking if it does not find it. This can't be good for battery life.
Click to expand...
Click to collapse
True! Also found that this was causing the high CPU load. Maybe people experiencing fast battery drop are having this problem.

DUDE! my problems lead me to SAME conclusion! i mean ext rom wiping leads to 29-32% cpu utilisation and up to 340 mA DRAIN!
im glad that someone told same thing!
your observation seems to be true.and very useful.
yes,omg,yes, it will be nice day!
btw...xplore doesnt have ext rom.. i think, so it must be other one..

nothin said:
DUDE! my problems lead me to SAME conclusion! i mean ext rom wiping leads to 29-32% cpu utilisation and up to 340 mA DRAIN!
im glad that someone told same thing!
your observation seems to be true.and very useful.
yes,omg,yes, it will be nice day!
btw...xplore doesnt have ext rom.. i think, so it must be other one..
Click to expand...
Click to collapse
So what can we do who have the Xplore 1.1 Rom?

WizeMan said:
So what can we do who have the Xplore 1.1 Rom?
Click to expand...
Click to collapse
I think that they mean : Don't mess with the ExtRom ...

WizeMan said:
So what can we do who have the Xplore 1.1 Rom?
Click to expand...
Click to collapse
If you flash an official rom before a custom rom, you know you will have an extended rom left over from the official. When I was on NotTooSmart's rom, I checked out the extended rom area and saw all the T-Mo extended stuff was still there from when I flashed the TMo 2.26 Official.
The point is, don't go and delete everything in extended rom as that will cause issues.

mfrazzz said:
If you flash an official rom before a custom rom, you know you will have an extended rom left over from the official. When I was on NotTooSmart's rom, I checked out the extended rom area and saw all the T-Mo extended stuff was still there from when I flashed the TMo 2.26 Official.
The point is, don't go and delete everything in extended rom as that will cause issues.
Click to expand...
Click to collapse
Why?? After I had installed Xplore 1.0 and just had teh extended_rom from faria - I just flashed an own cooked extended_rom and I still had it after flashing Xplore 1.1. No problems. Now I have deleted everything in my extended_rom and it is empty. I even could unlock it and use it right from fileexplorer. But it doesn´t make sence when using total commander.

papamopps said:
Why?? After I had installed Xplore 1.0 and just had teh extended_rom from faria - I just flashed an own cooked extended_rom and I still had it after flashing Xplore 1.1. No problems. Now I have deleted everything in my extended_rom and it is empty. I even could unlock it and use it right from fileexplorer. But it doesn´t make sence when using total commander.
Click to expand...
Click to collapse
Read point #3 in the OP. Maybe the problem only comes after a hard reset, but you can have issues by removing the extended rom. If you replace it with your own cooked one, then you are fine (if its setup correctly to work like a regular one).
I have no direct experience with this, just have seen this in other posts and now this one.

mfrazzz said:
Read point #3 in the OP. Maybe the problem only comes after a hard reset, but you can have issues by removing the extended rom. If you replace it with your own cooked one, then you are fine (if its setup correctly to work like a regular one).
I have no direct experience with this, just have seen this in other posts and now this one.
Click to expand...
Click to collapse
It only works for me as "trouble-space" Just collecting important setup cab. And when I have done a hardreset I just enter extended_rom with TC and install teh cabs.

anichillus said:
I think that they mean : Don't mess with the ExtRom ...
Click to expand...
Click to collapse
You know, i think we "could" mess with EXTrom...but totalcommander method seems to make thing f up... i always get messy names, sizes, if i am trying to copy sometihng there....
is it locked or what...IDEAL thing, anichillus, would be making CLEAN ROM, as clean ,as it can be, then cook SOME extroms to make people happy AT LAST ....
rethink it, its method for makin everyone happy...(or not..?).
Strange, i have 42 mA idle, but battery still drops...maybe i just must discharge to max, then recharge... not sure 'bout it...
Xplore is just awesome, waiting for 2.0, but for gods sake, make it clean...
btw, with wizard's love ROM flashing method i have THAT extROM, when i flash xplore, so its rather useless(what is in that extrom inside), but that 35% CPU usage is gone... plz give some links to FLASHABLE ext ROMS here plz...

nothin said:
Y
plz give some links to FLASHABLE ext ROMS here plz...
Click to expand...
Click to collapse
I used this an extended_rom including this apps. I can post if wanted.

thanks, m8, i just used wizards love ext rom, and aborted autorun.exe after flashing x-plore..safe...at last.

I'm glad this has helped some people
I think what many of you are describing is the best way: Downgrade to a rom that includes an extended rom, then upgrade to x-plore, and abort the extended rom installation by soft reset at the "installing customizations" screen.
If you are sophisticated enough to be able to design and flash your own extended rom as per Faria's sticky in the upgrading section, that should work too. Then you could let the customizations run.
Resist the temptation to delete the extended rom with total commander because you're not using it. (Unless you just want to prove it to yourself, and don't mind reflashing and reinstalling!)

i am reconsidering making ext rom on my own.. but geez.. i must stop FLASHING for some time lol
any thing made by tottal commander on ext rom lead to battery problems - 30-35% cpu usage ALL the time etc...

edhaas said:
I'm glad this has helped some people
I think what many of you are describing is the best way: Downgrade to a rom that includes an extended rom, then upgrade to x-plore, and abort the extended rom installation by soft reset at the "installing customizations" screen.
Click to expand...
Click to collapse
Do you think it is safe to abort the extened rom installation by softresesting?

danik_iceman said:
Do you think it is safe to abort the extened rom installation by softresesting?
Click to expand...
Click to collapse
Sure, I do it all the time. In fact I recommend it unless you WANT the customizations and programs loaded in there to run. It saves memory and avoids conflicts between rom upgrades/changes. Some rom cookers do put things in there which they would like people to try and those should be considered as part of their package. Others take a viewpoint of putting everything they feel is important into the "Rom" itself. (i.e. x-plore) However, it is always "safe" to abort the extended rom loading, you just may have to do some customizations yourself. (Carrier settings, dial skins, stuff like that) Try it both ways and see what you prefer.

I too experienced just now some problems when messing with the extended rom.
Why the f** this thing happens ?
The only thing I did was to unlock the extended rom from the rgu's so it would be directly accessible without any other program, simple, with file explorer
First time it started, it was ok, I could browse the Extended Rom, no problems. I did a soft reset, and after that the Extended Rom changet it's name to Extended Rom2 and nothing was to be seen in it. After another soft reset, I could see files, but it was giberish ... and boom, the cpu stable at 20% ...
I need to fix this. My rom doesn't has the extended rom in the windows dir so G4 can use it and also seems easy for me to place cabs
The battery drain/Cpu usage issue anyway, i solved it. The first time I did this
I flashed the TMob 2.26 and after that I flashed again my rom(meantime I removed the settings unlock for ext rom). Now it's working great again.
Any thoughts ?

edhaas said:
Sure, I do it all the time. In fact I recommend it unless you WANT the customizations and programs loaded in there to run. It saves memory and avoids conflicts between rom upgrades/changes. Some rom cookers do put things in there which they would like people to try and those should be considered as part of their package. Others take a viewpoint of putting everything they feel is important into the "Rom" itself. (i.e. x-plore) However, it is always "safe" to abort the extended rom loading, you just may have to do some customizations yourself. (Carrier settings, dial skins, stuff like that) Try it both ways and see what you prefer.
Click to expand...
Click to collapse
Sorry for the double post,
Man, not every customisation should be aborted...not wise at all
You can skip those who you know for sure that do not affect the stability of your rom...those that don['t mess with registry and fixes.
I for example have put some fixes in the "ext rom" (the one in windows) with some important fixes.

No problem with the double reply. My experience is that the extended rom unlocker are not true unlockers, in that the extended rom cannot be written to reliably except by flashing. But you can delete files from them, or more likely corrupt files in them by trying. If you do attempt to write to the extended rom "on the fly", it will look like it has worked until you do a soft reset. Probably the files go into a temporary storage memory although I haven't researched it deeply. I think your extended_rom2 problem has to do with the "real" extended rom being corrupted, and inaccessable. If I remember, the device then creates another on the sd card or something like that. (There is a thread in the upgrade section about the extended rom unlocker where this stuff is discussed).
As far as skipping the customizations, I agree that if the cooker has placed settings, etc in there they should be run. However, many cooks leave the extended rom alone, which can cause confusion when say a T-Mobile rom is initially there, and the T-Mobile customizations get run on top of the custom rom, (or Cingular, or whatever) unless that is what the owner wants. It might be helpful if the chef is explicit about it during the initial posting of the download link.

Has anyone tried the new build yet? I just noticed it about a week ago.
I was using...
Ver. 1.04.201 beta3 build 0178​
The new one is...
Ver. 1.04.201 beta3 build 0182​
It has increased the battery life for me and is more accurate at updating the battery strength as well.
Thanx.

Post install script

Is there instructions on creating a post-flash (or hard reset) install script? I'd like to have it run the cingular WAP cab, and maybe a couple others. I think I've been all over, but haven't seen anything...
Thanks!

Also - does anyone have a package or cab for camera 3.3???

Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.

JoelC said:
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
Click to expand...
Click to collapse
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!

mattk_r said:
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
Click to expand...
Click to collapse
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"

notyourdaddy said:
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
Click to expand...
Click to collapse
I just found this link that has an extended rom in it. It makes a lot of sense, especially the txt file that directs the installation and then initiates a reset. Getting warmer!
http://forum.xda-developers.com/showthread.php?t=309922

So here's what I'm thinking - just initial thoughts:
Have a folder with the base applications that are used every time like AutoRun.exe.
The user places the cab(s) in the "add files to ext rom" folder.
They run an exe that reads the directory file contents, verifies file type, copies the files to the extended rom folder, and displays the list. I'd write it in VB, since I'm most comfortable with file system operations in that language...
They change the list based on the order they want them installed using up and down arrows to sort priority.
The click OK, and it creates the config.txt file, including all necessary commands such as reset and whatnot.
That way when they build, it's all good to go.
Any thoughts?

Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy

Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best

JoelC said:
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
Click to expand...
Click to collapse
That's really good info, because I'm climbing the learning curve as fast as I can here to get a good grasp on what the extended rom is, as well as how to use it. I appreciate the conditional warnings... better to know ahead of time than find out following a problem.
I'd rather use the true extended rom (as I understand it anyway), so I don't loose any additional space for the BuildOS programs. That is, assuming the extended rom is a seperate memory location than the base...
In another thread, someone is going to post that tool. I'm really interested in how it works.
If I can get all the concepts together, I hope to get a solid tool that will improve functionality in the ROM, without adding complexity or trouble... and I greatly appreciate the help!

Interesting thread...guys, you just gave me some new ideas.
Before that...there's one thing that's bothering me...
Can we use ExtendedRom on a G4 or not...lol I thought not, until me an Boto made a clean one from a G4 ExtRom and when Boto flashed it it worked , and he has a G4. Why we always say that we don't use an Extended Rom for G4 users ?
Normaly, a G4 should/would brick when flashing IPL/SPL not Extended Rom, am I right ?
We are shrinking the OS space to integrate features of the ExtendedRom in order to all people use it but is it that true ?
Ok, now back to my idea .. I want that in my next rom to include an extended rom, of course and make it that way so when you first start your PDA, it will act like when installing windows on the PC , asking you which apps or what options you want to use. I think i can manage to do that...still the question remains ...will G4 users be able to use it ?

Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!

JoelC said:
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
Click to expand...
Click to collapse
I took the Ext Rom from the Wizard Love Rom and i edited the config.txt and deleted cabs ...that's it

Well, if it flashed OK... sounds like it might be usable after all But tell me, is Boto's G4 CID locked or unlocked? It's all very uncertain, but some of the G4 posts lead me to believe this may make a difference

ADB100 said:
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Click to expand...
Click to collapse
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.

wizzzard said:
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
Click to expand...
Click to collapse
Thanks for that but it isn't what I was really after.... I am just trying to automate everything. I have flashed my ROM that many times recently and going through the install of TomTom each time is a bit of a pain. I have got a couple of .CABs in the Extended ROM OK and these work fine, I just thought it would be nice if I could get TomTom in there as well.
Andy

I didn't want this to turn into a "how-to" thread, but I'm still scratching for hard info on the extended rom, and as many questions out there, it might be a good one to clarify some details...
As I understand it now, there's two forms of "extended ROM":
1. The true extended rom "similar to the radio ROM"
There is some "trigger" that runs the contents of the extended rom, such as AutoRun.exe?
2. The 'psuedo' extended rom that is basically a post install script to run cabs.
The contents of the folder under windows are run from a trigger that resides in the startup folder - similar to a runonce in Windows on first boot?
Does this sound close?
Also, where does the 'true' extended rom reside? Does it use the portion of memory reserved for the OS, or is there another portion just for it? (so if by adding applications to the extended rom, your available storage memory will remain unchanged - less the installed application?)
I'm presuming then by the 'psuedo' extended rom, that it does consume ROM space, but simplifies post-flash cab installations - assuming you follow the rules...
From what I see, by using the 'psuedo' ER, you waste space by keeping the installation files in addition to the installed application files.
If I'm wasting space and time by asking these questions and you know of a good extended rom tutorial, please direct me to it. I have spend some time tonight searching, but a definitive guide still eludes me... Thanks!

Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).

mfrazzz said:
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
Click to expand...
Click to collapse
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.

mattk_r said:
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
Click to expand...
Click to collapse
Yeah, never figured out why that one was never made a sticky. I just know to go look at Faria's sig and it (and a few other good links) are in there

Why is cooked rom "FASTER"

newb question .. why would a "clean" rom, smaller rom, be any "faster" than the stock HTC Kaiser rom ?
I mean ACTUALLY, benchmark-able, FASTER. Aren't you just making more storage room ?
Thanks,
DLD

RacerX10 said:
newb question .. why would a "clean" rom, smaller rom, be any "faster" than the stock HTC Kaiser rom ?
I mean ACTUALLY, benchmark-able, FASTER. Aren't you just making more storage room ?
Thanks,
DLD
Click to expand...
Click to collapse
Because, for one thing, all the stupid microsoft registry ****ups have been removed. It just like have powerup XP or something running on your desktop. Microsoft Software can always be improved. That's a known fact

Maarten_0031 said:
Because, for one thing, all the stupid microsoft registry ****ups have been removed. It just like have powerup XP or something running on your desktop. Microsoft Software can always be improved. That's a known fact
Click to expand...
Click to collapse
Can you give me an example of these "****ups" ?
Thanks,
DLD

Well it's a little of both, actually. The storage advantage in ROM permits you to have more space for apps (a la kitchen or custom roms.) The other advantage being that any apps that run in the background or autostart with the device will no longer be present, freeing up more RAM for active applications.
Hope this helps.
MJB

plus the wm6 kernel has been updated, of course.

Question to Quentin - Q Mobile 1.2

I read the Wiki page for Q Mobile 1.2. I never flashed any ROM in my Tilt yet. I removed all the AT&T specific boltwares (Hard reset and after WM6 install, soft reset before AT&T Cingular boltware are starting to install). This gives me around 110MB free space.
I use Kaiser Tweak to stop the scroll sound and increase the touchflo sensitivity and other features. The usability is good and fast enough until i install anything on it.
I have a basic question. I see different versions of ROM, Radios floating around. I am guessing all the ROM's are the same windows mobile 6 with certain features removed / added. I assume every ROM maker aims for more free space and Ofcource some windows tweaks (compramise the feature - some people think certain features are crap).
Right now i have 110 MB free space in my Tilt. (Nothing loaded except WM6). Your ROM has 145MB free space. If I install your ROM and install 35MB of applications (say 15 applications) can i assume that the device will perform with the same speed like my current Tilt with 110 MB free space?
I am just trying to understand. Also, are you rewritting and compling certain codes of WM6 itself for performace. I am not even sure if SDK is available for WM6.
Thanks.

sundar_amn said:
Right now i have 110 MB free space in my Tilt. (Nothing loaded except WM6). Your ROM has 145MB free space. If I install your ROM and install 35MB of applications (say 15 applications) can i assume that the device will perform with the same speed like my current Tilt with 110 MB free space?
I am just trying to understand. Also, are you rewritting and compling certain codes of WM6 itself for performace. I am not even sure if SDK is available for WM6.
Click to expand...
Click to collapse
In no way will it perform the same as your Tilt currently does--it should be far better. The reasons for this are many--beginning with the fact that it has a much newer operating system core. Then there are MANY cache, registry, file, etc tweaks that go into my ROM.
In any case, there are clear instructions for going back to your ROM so what you should probably do is install HardSPL and try some custom ROMs and see what a difference there actually is. Cheers,

Thank you very much for your instance response. It gives more confidence. My first ROM flashing start with your Q-Mobile 1.2 ROM. I will read Wiki page for other instructions. couple more yes/no questions.
1) I see clear storage CAB in your WIki page. That will do the same job like it does in current tilt - reverting back to your factory setting?
2) The newer Radio is something released by AT&T itself for public?
3) "Compatible with 1.27.14.x Radios and includes the 1.27.14.09 radio". I assume this ROM comes with a reliable Radio.
4) Can i install any WM6 applications or are there any issues reported on any applications. (I saw the newer camera version has issues)
Thanks.

sundar_amn said:
1) I see clear storage CAB in your WIki page. That will do the same job like it does in current tilt - reverting back to your factory setting?
Click to expand...
Click to collapse
Yeah its the same as pressing the two soft keys and resetting the device...I don't include it by default because its redundant for that very reason. But people have requested it so I provide it as a CAB you can install.
sundar_amn said:
2) The newer Radio is something released by AT&T itself for public?
Click to expand...
Click to collapse
Yeah, it comes with the 1.60 and 1.61 ROMs from AT&T.
sundar_amn said:
3) "Compatible with 1.27.14.x Radios and includes the 1.27.14.09 radio". I assume this ROM comes with a reliable Radio.
Click to expand...
Click to collapse
Right, just remember that if you go to a non-Tilt rom someday to download one of the 1.27.12.x radios from the link in the Wiki. It is common for "Tilt" branded ROMs to include the 1.27.14.09 radio because currently its the only one in its class. But there are MANY versions of the 1.27.12.x series radios so ROMs compatible with those traditionally don't include a radio--you can use whichever suits you.
sundar_amn said:
4) Can i install any WM6 applications or are there any issues reported on any applications. (I saw the newer camera version has issues)
Click to expand...
Click to collapse
You can install pretty much anything you want. It is encouraged. You may find things that don't quite work, but thats why this forum isn't called "Kaiser Everything Works Upgrade At Will" Most apps do though.

Thank You So Much. You Are So Kind And Great!!

[PreRelease BigStorage] Just2Clean and Two New Kitchen [Updated:04.22.08]

Update: 04/22/08
This is a release for the ROM and the porting kitchen. It does not port XIP's, yet, just SYS folders, but it does what it needs to do. I haven't tested it in more than just one port, though. The one I did test came out perfect, though.
The ROM has 63.XXmb FREE storage and 31.XXmb free with SD RAM.
To flash it you MUST have a HardSPL'ed Herald or Wing and a microSD card. Just place the HERAIMG.nbh into the SD card's root directory. Do NOT rename it to anything else. Then hold the camera button down while you turn on the device and then press the volume down slider when it asks you to. Wait until it says it's done. I haven't tried to run any activesync other than to an exchange server so tell me if that isn't working.
I'll be done with finals this week and then I can finally work on the other kitchen.
I'll upload it when I come back from school.
Update #2: 04/14/08
Just added a screenshot. Mind you, this is WITH SD card AND after I installed my "troubleshooting" tools.
Update: 04/14/08
60mb of FREE storage space.
32mb RAM with no SD
30MB RAM with SD
No compression (I'll probably released a UPX'd version, as well...)
Fixed all bugs found so far except for two. Maybe you guys can help me figure them out... the sad part, I've fixed these same two bugs countless times in my other ROMs, but I just can't remember how I did it. lol
1. Comm Manager: It doesn't matter what comm manager I place in there, it still boots up the built in comm manager. (The one that Tmobile has anyways.)
2. The Vibrate button. I have all the files and I have it setup so that it vibrates when you hold down the comm button, BUT it keeps trying to open VoiceCMD even though I deleted all visible entries for it...
Update: 04/03/08
Ok guys. Here's some info on my current projects.
1. Just2Clean is almost done. I just have to fix some bugs. The OEM is from an unreleased Wing ROM, the SYS I ported over using... well keep reading.
2. My phone currently is running currently has 62.38mb total of storage... and I was able to shrink the extrom and use that ROM space for storage. Granted, you need to have HardSPL and a memory card for this to work, but it's awesome. This ROM is also so small and stripped that it's the fastest ROM I've ever used and I don't even have any tweaks on it, yet.
3. Kitchen 1: PPCBuildOS: Unfortunately, I haven't had time to work on porting it, but after I get Just2Clean fixed, I'll be working on it. AWESOME kitchen. The creator is so willing to help, too. Made me a developer of the Atlas section (Herald compatible so no worries for those Herald users.)
4. EasyPortKitchen. So far, I've got it porting SYS folders just fine. I haven't been able to setup XIP porting, but that's because I still don't understand the process behind it. If someone wants to explain it to me, I'll be able to finish this kitchen. So far, Just2Clean had its SYS folder ported in this way.
EDIT: 5: I plan to release the ROM with language packs for the kitchen. Then you can just check on the language you want the ROM to be in while building the ROM.
New Post
Ok, change of plans.... I'm currently working with the makers of PPCBuildOS to make an Atlas/Herald version of their kitchen. It's currently being developed with JustClean, but it will eventually be released with my Just2Clean. (That'll be the new name.) That kitchen is AWESOME, btw. ^_^ Makes my kitchen look like a pitiful script kiddy toy.
Just2Clean will be a WM6.1 stripped down better than JustClean was, more modulized and with its OEM based on an unreleased ROM.
I'll keep you guys posted but I'm not sure of how much I can talk about now that I'm helping develop the Atlas/Herald side of it...
Old Post
A few things that I've been thinking about on my "off" time... basically, the time that I'm just unbusy enough to have my own personal thoughts outside of work or school related ones. lol
All these ROMs would be compatible with my kitchen.
1. SuperClean - A ROM built with lots of compression and minimal programs. The point of this is to be the "bigstorage rom" where you can't even flash it normally because it doesn't meet the size requirements of the RUU/SPL.
2. JustClean2 - Based on an unreleased OEM from an unreleased ROM that I made before I switched to WM6.1. It's based on a Wing ROM... but it has potentials. It just feels faster and it seems to take less space than the current Herald base I'm using. Not to mention that some people are having issues with Herald based ROMs and some bluetooth enabled items.
3. OldClean/NewClean - SuperClean and JustClean2 may have both WM6.0 and WM6.1 versions... I find that, although WM6.0 is slower, it also takes up less space (and therefore can net more storage space) and some people don't seem to like a lot of the WM6.1 features.
What do you guys think? Which would you like to see first? If any? Any better ideas? (And no, no ideas about which programs should be in it, you already have my kitchen for that.) Oh, and the kitchen would become modular, the JustClean1 ROM would be released seperate from the Kitchen.
I'm itching for a ROM as quick as my old WM6.0 ROM, but I haven't had as much luck getting the Herald ROM to run as quickly.
BTW, has anyone ever used my old CleanROM with the Herald keyboard driver? Did you ever have any issues with it?

I vote for a newer WM6.1 built than the "old" 19xxx - there were newer ones outside before bepes kitchen ROM but thy had ActiveSync problems...
Maybe now there are new builts.
OR if not i vote for WM7...hahaha
ALLL the "clean" crap doesn´t make sence to me... why to have a clean rom and then install all by cab.
I ONLY cooked a rom because i was sick of installing all cabs
lol

Good to see ur back to cooking roms
Well i Love the functions of WM6.1 so just about and clean 6.1 rom you cook will be great
so i'd guess from ur descriptions that'd be SuperClean...
Edit: I also use the Office suit a lot but i can add that by a cab, since i know most clean roms dont have it since it takes quite a bit of space

papamopps said:
I vote for a newer WM6.1 built than the "old" 19xxx - there were newer ones outside before bepes kitchen ROM but thy had ActiveSync problems...
Maybe now there are new builts.
OR if not i vote for WM7...hahaha
ALLL the "clean" crap doesn´t make sence to me... why to have a clean rom and then install all by cab.
I ONLY cooked a rom because i was sick of installing all cabs
lol
Click to expand...
Click to collapse
These ROMs are meant to be used with my kitchen. That way they can add what they want and what they want only. Some people just don't use any programs and want the available storage space for other reasons. (Like photos.)
The SuperClean would attempt to create a lot more free space in the ROM. (For example, I have 54.93mb total (I've got a few files saved so I'm not sure how much I had free at first) currently in the ROM I'm currently using and it's no where near optimized and it's one of my fattest unreleased "SuperClean" ROM's that I have ever made.
Imagine being able to get 60mb free WITH all the apps that you use. It would be awesome.

Well at the moment i have a 4GB Memory Card, but reguardless i preffer to use cean roms as they tend to be faster and have more program memory available.
Especially since i use Point UI and dont rly care about today plugins

I vote for just a 6.1 Rom w/ good tweaks (and ready to go for tmo usa) and no extra programs.

BTW, has anyone ever used my old CleanROM with the Herald keyboard driver? Did you ever have any issues with it?
Click to expand...
Click to collapse
Yes I have, and no issues at all.

BTW, has anyone ever used my old CleanROM with the Herald keyboard driver? Did you ever have any issues with it?
Click to expand...
Click to collapse
I did, but there were some serious issues (I can't remember which though). I had reporeted them in CleanROM thread for sure.
BTW, when are you going release final of your oven? I need to fix several small issues in my custom ROM, but I'm too lazy to do so with current version

GiZZy said:
Well at the moment i have a 4GB Memory Card, but reguardless i preffer to use cean roms as they tend to be faster and have more program memory available.
Especially since i use Point UI and dont rly care about today plugins
Click to expand...
Click to collapse
And THAT is the problem ... even with 63MB program storage... we will NEVER get more than 32MB free RAM (memory)
to get more storage for apps or even cach is not the problem. BUT getting more RAM is not possible.
But as a clean rom for cooking - OK
but then:
- no skinning
- default looking
- only left what is needed for running system (phone, base apps)
and than we can cook....
thx
AND why don´t we have this OS "System 5.2.19202 (build 19202.1.0.0)"????
the kaiser people have it..

papamopps said:
And THAT is the problem ... even with 63MB program storage... we will NEVER get more than 32MB free RAM (memory)
to get more storage for apps or even cach is not the problem. BUT getting more RAM is not possible.
But as a clean rom for cooking - OK
but then:
- no skinning
- default looking
- only left what is needed for running system (phone, base apps)
and than we can cook....
thx
AND why don´t we have this OS "System 5.2.19202 (build 19202.1.0.0)"????
the kaiser people have it..
Click to expand...
Click to collapse
I took a look and found out the kaiser guys have 5.2.19716. How do I extract the OS from their roms? I gotta have that build!
Must... Cook... Rom...

papamopps said:
And THAT is the problem ... even with 63MB program storage... we will NEVER get more than 32MB free RAM (memory)
to get more storage for apps or even cach is not the problem. BUT getting more RAM is not possible.
But as a clean rom for cooking - OK
but then:
- no skinning
- default looking
- only left what is needed for running system (phone, base apps)
and than we can cook....
thx
AND why don´t we have this OS "System 5.2.19202 (build 19202.1.0.0)"????
the kaiser people have it..
Click to expand...
Click to collapse
I'm currently learning how to port properly for that specific reason. 19202.1.0.0.
As far as the skinning goes, the final should have the option to have no skin. I'll work on that. The base should have a few things disabled. I'm also working on that. As far as RAM goes, I've gotten up to 38mb free before, but it was missing a lot of items... I could always just modulize the whole ROM and let people choose EVERYTHING down to if they want bluetooth support or not. This can net some pretty nice amounts of free memory. It's just more work for me.
I am also thinking of modulizing the MUI's in the ROM, effectively allowing people to just download language packs. Doubleclick on the file, wait until it does its thing and then you have a French ROM, or a German ROM, or whatever...
It's not that I can't do it, it's that it takes time.... time I don't have.

ivanmmj said:
What do you guys think? Which would you like to see first? If any? Any better ideas? (And no, no ideas about which programs should be in it, you already have my kitchen for that.) Oh, and the kitchen would become modular, the JustClean1 ROM would be released seperate from the Kitchen.
I'm itching for a ROM as quick as my old WM6.0 ROM, but I haven't had as much luck getting the Herald ROM to run as quickly.
Click to expand...
Click to collapse
It seems to me that the 6.1 ROM is a bit faster when doing some things (like opening the windows folder using total commander) is involved - but I think the 6.0 can be tweaked to be just as fast? I would be very excited to try either your SuperClean or JustClean2 as long as the ROM is based on Wing.
I used your CleanROM for quite a while with NO problems but on a Wing.

Update on the first post.

ivanmmj said:
New Post
Ok, change of plans.... I'm currently working with the makers of PPCBuildOS to make an Atlas/Herald version of their kitchen. It's currently being developed with JustClean, but it will eventually be released with my Just2Clean. (That'll be the new name.) That kitchen is AWESOME, btw. ^_^ Makes my kitchen look like a pitiful script kiddy toy.
Click to expand...
Click to collapse
yay new kitchen!

wow, can't wait to try the superclean (superfast???) rom

Let us script kiddies get our toys!

Updates on the first page!

So it will come with the same kitchen like JustClean?
62 megs...sounds cool. I hope it will be possible to stuff the rom with office etc. and flash it as usual.

Not with the same kitchen. With a new GUI kitchen that the guys at PPCkitchen.org have made for other phones. I'm just helping them port it to the Herald/Atlas.
The EasyPortKitchen is something you would use to port a ROM.
You can install anything you want on it. All my ROMs are always minimal and allow you to install whatever you want on them.

You can install anything you want on it. All my ROMs are always minimal and allow you to install whatever you want on them.
Click to expand...
Click to collapse
That's the best of your releases. Just a clean package so everyone can add what he needs, noone has to have stuff on their phone that they don't like. It's simply a Good Thing (tm).