|ROM|¯`·.¸¸.- Energy -.¸¸.·´¯ * |July 4| 21916|29022 * Sense 2021 + flavors

[1999TL]

Originally Posted by lgrulz

Yeah funny I'm up at 415 for work. I have my sd card organized with like 10 different roms on it and all customizations organized per rom. And they wonder what i do in the bathroom all day!

LOL. I have the same thing. Makes flashing a breeze. I'm using sashimi...

[mikedboyd]

Same here (organization by ROM on SD, plus Sashimi, not the bathroom hobby).

Originally Posted by 1999TL

LOL. I have the same thing. Makes flashing a breeze. I'm using sashimi...

[variance]

does the new one have the four rows back in favorites or is it still 3?

[auTONYmous]

That's awesome: Me and NRGZ28 have the same birthday!

[flyers2114]

Originally Posted by mikedboyd

Soft reset - hold down power till you get the option screen and then either turn off or reset. Or take off back cover and press stylus into little red recessed button.

Hard reset (caution, lose all non-ROM data in main memory). Use the 'Clear Storage' app or hold down 'send' and 'end', then also power key, all at same time.

Run one of the 'bootloader' programs, or hold down the 'down volume' and then power at same time.

To leave bootloader, take off back cover and press the reset button or take out battery.

Hard reset and clear storage are not the same.........they both clear data but clear storage is more effective to clear ALL data.....

[TheShade001]

Originally Posted by mikedboyd

I continue to find it very interesting how different folks have such varied results with these ROM's. I'm on the 2/16 Cookie ROM and (in spite of my best efforts) it is proving to be the MOST stable ROM I've loaded yet, and I've tried several of the chef's now. I am really liking this.

I completely agree. It is a mystery how the FEB 16th roms are absolutely flaswless, fast and stable for some of us while others report constant freezing or lockups. Logically, it would seem like it would have to be configuration settings or certain cabs installed, but some seemingly very capable people are reporting freezes. Who knows. I find it very odd that i have had so much success with the Feb 16 while others are complaining about the unstability. I have had no memory problems, no battery drain, no freezes, and it has been smooth as can be. In fact, i just thought long and hard to see if i can report an issue, but i can't. Everything, and i mean everything works as it should. It's an interesting phenomenon to say the least.

At any rate, i have enjoyed the Feb 16th roms and consider them to be the best to date. I think it SMASHES the Feb 7th roms. Thanks again NRG and friends!

[smu]

[QUOTE=TheShade001;1582178]I completely agree. It is a mystery how the FEB 16th roms are absolutely flaswless, fast and stable for some of us while others report constant freezing or lockups.QUOTE]

I do embedded hardware and software for a living and it's not too much of a mystery to me...but we have a saying: "If it was easy, then it wouldn't be embedded." Please let me qualify what I'm about to say by stating that I'm not casting aspersions against anyone or any particular products because I know that people on this forum work very hard to bring us the things that they do - and I appreciate them greatly. However, not everyone is imbued with the same ability to do embedded development as everyone else; some people have a compiler and very little development experience and are anxious to write code to solve problems, but having a compiler doesn't make you a good embedded devloper in much the same way that having a driver's license doesn't make you a good driver. I think that some cabs are rushed from idea to forum posting without much in the way of testing other than, "I've run it on my phone for 10 minutes and it hasn't hard reset yet!" Many of us have this cab to do this, that cab to do that, another cab to do this other thing, etc. and sometimes the cabs don't play nicely with one another. In general, we on this forum burn quite a few CPU cycles trying to figure out which cab we've installed makes our new ROM installation unstable, others blame the ROM and fiddle with settings on it to try to stabilize their system, etc. So to what do I attribute these mysteries of some people are rock solid and other have nothing but trouble out of a ROM? I think the issue lies squarely on the cabs that people are running.
The truth of the matter is that it's very difficult to do good app/cab development without access to MS developers and/or source code, but I think it's remarkable that some of you guys have the time (and NRG, if you'll pardon the pun) to code what you do. The problem with the testing of cab development is that the 6.5 ROMs are still a bit of a moving target for the cab developers to hit, so it makes development difficult and coordinated testing a nightmare.

[jmcourir]

I have Energy.RHOD500.23529.Leo_(Cookie_HomeTab_1.5.4).16 .Feb.2010.rar installed since Feb 16th and This is the best Cooked ROM I have seen so far.

Since November I test all Manila 2.5 Cooked ROM from ENERGY ROM and I really appreciate it !

Thanks

[Mazzakre]

Originally Posted by smu

I do embedded hardware and software for a living and it's not too much of a mystery to me...but we have a saying: "If it was easy, then it wouldn't be embedded." Please let me qualify what I'm about to say by stating that I'm not casting aspersions against anyone or any particular products because I know that people on this forum work very hard to bring us the things that they do - and I appreciate them greatly. However, not everyone is imbued with the same ability to do embedded development as everyone else; some people have a compiler and very little development experience and are anxious to write code to solve problems, but having a compiler doesn't make you a good embedded devloper in much the same way that having a driver's license doesn't make you a good driver. I think that some cabs are rushed from idea to forum posting without much in the way of testing other than, "I've run it on my phone for 10 minutes and it hasn't hard reset yet!" Many of us have this cab to do this, that cab to do that, another cab to do this other thing, etc. and sometimes the cabs don't play nicely with one another. In general, we on this forum burn quite a few CPU cycles trying to figure out which cab we've installed makes our new ROM installation unstable, others blame the ROM and fiddle with settings on it to try to stabilize their system, etc. So to what do I attribute these mysteries of some people are rock solid and other have nothing but trouble out of a ROM? I think the issue lies squarely on the cabs that people are running.
The truth of the matter is that it's very difficult to do good app/cab development without access to MS developers and/or source code, but I think it's remarkable that some of you guys have the time (and NRG, if you'll pardon the pun) to code what you do. The problem with the testing of cab development is that the 6.5 ROMs are still a bit of a moving target for the cab developers to hit, so it makes development difficult and coordinated testing a nightmare.

Agreed. Ive been saying for months now that its the customizations and cabs that are causing the problems that some are having and others arent. Sashimi and uc are very cool tools but I think its a double edged sword. Auto-Installing the same cabs and regedits across roms is going to lead to problems because none of the roms are exactly the same. Some conflicts are obvious like installing a task bar that makes things not align properly but some arent so obvious like how installing opera a few builds back caused youtube sound to not work.

Before I install anything I go through the basic settings and steps like updating quickgps, make sure everything works properly. I even test mms fresh out the box on every flash to see if it happens to work, if it doesnt I change the server settings to sprint specific to see it thatworks, then I install the necessary cabs. These steps ensure that if something breaks I know exactly where it went wrong. A little extra work goes a long way toward happy flashing.

[NinjaDuck]

Not that you really need it because the documentation on Cookie's registry settings is pretty complete, but he has created a settings editor.


See his thread:
http://forum.xda-developers.com/showthread.php?t=633590




Cookie is the Man!