New BuildOS - Report Bugs Here

[tiermann]

Always hard-reset after a flash.

It's not a new step, it's a replacement for the RUU message which tells you to soft-reset. Not everyone's device ends up clearing the storage after a flash so you have a chance of old storage files remaining. You can end up with dead shortcuts, missing SMS sender, or a bunch of other side effects.

[Robtao]

Originally Posted by tiermann

Always hard-reset after a flash.

It's not a new step, it's a replacement for the RUU message which tells you to soft-reset. Not everyone's device ends up clearing the storage after a flash so you have a chance of old storage files remaining. You can end up with dead shortcuts, missing SMS sender, or a bunch of other side effects.

So a hard reset, of course, restores from serious system problems, but also can remove issues that could be left after a ROM flash.

What about, say its been a long time since a hard reset, making a full Spb backup, then hard reset, then full Spb backup restore? Advantages? Waste of time? If you correct any issues with a hard reset, does a backup restore also restore the issues?

I am looking for a better understanding of what a full or system backup does and how that relates to benefits gained by a hard reset. My assumption has been that the hard reset could serve a maintenance or "oil change" function, but don't want to turn around and pour the old oil right back in.

[bobonit]

Problem Solved !!!, thanks Guru !!!

[gguruusa]

Originally Posted by Robtao

So a hard reset, of course, restores from serious system problems, but also can remove issues that could be left after a ROM flash.

What about, say its been a long time since a hard reset, making a full Spb backup, then hard reset, then full Spb backup restore? Advantages? Waste of time? If you correct any issues with a hard reset, does a backup restore also restore the issues?

I am looking for a better understanding of what a full or system backup does and how that relates to benefits gained by a hard reset. My assumption has been that the hard reset could serve a maintenance or "oil change" function, but don't want to turn around and pour the old oil right back in.

A full backup, hard reset, restore is usually a waste of time.

A full backup backs up the registry, files, and PIM information. A hard reset clears all of those. A full restore restores everything to as close to the original backup state as can be had - about all that's different is temporary files might not be part of the backup, depending on how thorough the backup was in the first place. There's an OEM that clears temporary files that's probably equally effective, much less risky, and far less hassle.

The benefit of a hard reset is clearing junk out of the registry (which a full backup/restore eliminates any benefit of) and clearing out junk/temporary files (which a full backup/restore may, depending on how "full" it is, eliminate any benefit of).

BTW it's precisely this same reson why you shouldn't do a full restore when upgrading from one kitchen to the next: file and registry changes corrected by the new kitchen will be overwritten by the restore.

[sunny1974]

i downloaded the latest files and built a rom.. it worked good .. but i realised later on that the spb plus bug wasnt fixed in it.kept saying register.. so i downloaded the given oem and dragged n dropped it in the oem folder.. and refreshed the buildos it showed me the newly added spb plus 4 in 2 options- one complete and the 2nd safe mode part only.... is this the correct way of getting the new version to work? or i need to put it in patches or sumthing? how does the patch thing work? btw the new buildos rocks and makes it soooo easy..
thanks a ton guys..

[gguruusa]

Originally Posted by sunny1974

i downloaded the latest files and built a rom.. it worked good .. but i realised later on that the spb plus bug wasnt fixed in it.kept saying register.. so i downloaded the given oem and dragged n dropped it in the oem folder.. and refreshed the buildos it showed me the newly added spb plus 4 in 2 options- one complete and the 2nd safe mode part only.... is this the correct way of getting the new version to work? or i need to put it in patches or sumthing?

You shouldn't need or be using the patchesdir with this release, but it simply copies the files in it into the rom, overwriting files of the same name if they exist. Patches dir was the only way of making changes to core files prior to the 071117 kitchen release. With the 071117 kitchen, you should now be able to accomplish the same action, better, through an OEM.

When you say you "dropped it in the oem folder", I assume you mean User_OEM? If so, yes, that's the correct way to do it.

[avaya]

Gguru.. a question for you.

is there a need to have to select the PRJ file if you already select the provider? BuildOS could determine which PRJ file to use base on the provider selection. Unless there some other reason not to.

just a thought..

thanks for the updated version.. it's great...

avaya

[BlackDobe]

First off, great work guys. All of your hard work and dedication is greatly appreciated.

Secondly, has any else experienced with the latest kitchen (Helmi_WM6_Apache_Kitchen_071117_1.exe) that during a call the left softkey no longer responds to bring up the menu to enable speaker phone and the other objects? This functionality has worked in the previous kitchen ROMs and doesn't seem to work in this version.

Also an error pops when opening the new kitchen indicating the provider is incorrect. Once a provider is selected the kitchen functions as normal.

[luv2chill]

Originally Posted by BlackDobe

First off, great work guys. All of your hard work and dedication is greatly appreciated.

Secondly, has any else experienced with the latest kitchen (Helmi_WM6_Apache_Kitchen_071117_1.exe) that during a call the left softkey no longer responds to bring up the menu to enable speaker phone and the other objects? This functionality has worked in the previous kitchen ROMs and doesn't seem to work in this version.

Also an error pops when opening the new kitchen indicating the provider is incorrect. Once a provider is selected the kitchen functions as normal.

Please repost your first question in the kitchen bug thread. Include the selections.txt file with your selected OEMs in it.

The second issue you reported is a known bug and yeah it's no problem if you just select your carrier at the top and save your selections.

[gguruusa]

Originally Posted by avaya

Gguru.. a question for you.

is there a need to have to select the PRJ file if you already select the provider? BuildOS could determine which PRJ file to use base on the provider selection. Unless there some other reason not to.

Currently they do two very different things, so yes, you must select the carrier in the toolbar dropdown and also select your carrier in the carriers section of the OEMs.

Pre-selecting one based on the other is on the drawing board, but there are a multitude of things to implement/change before it'll be possible.