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

[gabbythe1]

Originally Posted by wwjclemd

My guess is that it may be for the Imagio... It is however, officially my birthday... Soooooooooooooo...

A new rom would make it a very

I wish you a Merry B-Day and many more healthy and prosperous ones for the future bro.

[murducky]

Originally Posted by glenwill

Murducky, if you happen to notice this, it might be good to add instructions for putting the sashimi link your sdconfig.txt file creates in the startup folder into a deleteops.ini file, so it gets deleted after a full install.

Bsarlo, sounds like you are getting the hang of it, albeit with some painful lessons. I don't know much about using UC by itself. Someone, I believe NinjaDuck, is working on a UC instruction guide.

Regarding Opera settings, I don't set them myself, so I don't know what the reg entries are, but most likely it is doable. Murducky's guide has a lot of reg settings listed, so you could check there.

What I did once I got serious about getting Sashimi setup fully, is I spent a few hours doing hard resets and watching the setup. I'd tweak settings, hard reset and watch again. This really got me off to a good start, as I worked through all of my most important setup needs.

been meaning too!

[bsarlo]

Originally Posted by NinjaDuck

Yes, but it is just UC (use an SDCONFIG.TXT file).

If you are not farmiliar with the differences, this may help:
Learn UC / Registry / XML Provisioning / CAB Editing

What initializes the SDConfig.txt file's code? Does it run after every reset (soft or hard)?

**EDIT**
I'm reading up on this so I'll be ready to flash whenever the new ROM is released. I found that it only runs on hard reset unless you reg edit the AutoRunFlag value.

Could I just keep SDConfig.txt in my Storage Card Root? Is there a way to disable a line of code or turn a line of code into a comment like a " ' " will do in VBA or SQL? Or do I have to delete it?

**EDIT**
No need since it only runs after the hard reset, right? The PPC is basically looking for SDconfig.exe after the hard reset, whichvis cooked into NRG's ROMS?

Originally Posted by glenwill

Murducky, if you happen to notice this, it might be good to add instructions for putting the sashimi link your sdconfig.txt file creates in the startup folder into a deleteops.ini file, so it gets deleted after a full install.

Bsarlo, sounds like you are getting the hang of it, albeit with some painful lessons. I don't know much about using UC by itself. Someone, I believe NinjaDuck, is working on a UC instruction guide.
...

I am working on it. Anything I can learn to make flashing easier is good for me. Could you give me an example of what a deleteops.ini file should look like?

Originally Posted by glenwill

I see several responses, but just to clarify, deleteops.ini is just a text file named with an ini extension. You place it into the SASHIMI\Program\INI folder.

However, I wouldn't set it up to delete the SDConfig.txt file, just the link SDConfig creates in the windows startup folder. Otherwise, your next flash or hard reset will not run Sashimi if you don't recreate your SDConfig.txt.

Would this work:

[DeleteFile]
file1=\windows\startup\sashimi.lnkl

[wherestheanykey]

Originally Posted by locomariachi

Just started using the new lock cab that's pretty sweet have my tp2 running like a champ and also got android running on my TP2. so far best of both worlds.

Can you point me to where you got the android files and instructions? I have tried what I thought was the latest from XDANDROID and the phone service, data service and bluethooth wasn't working yet.

Thanks,

[wherestheanykey]

Originally Posted by princeofppc

i noticed since yesterday that once in a while if i navigate to couple of diff screens and then come back to the Settings tab, then click on the sound & display tab, the whole screen is empty other than the heading.

the only way to get the screen back is to restart the phone.

i don't have anyother cab files installed other than the march 13th nrg file.

I have seen this also from time to time on the Mar 13th 21xxx CHT ROM

[tyty1978]

i am sooooooooo ready for this new rom.... for some reason my mms just stopped working today

[Boushh]

Originally Posted by wherestheanykey

Can you point me to where you got the android files and instructions? I have tried what I thought was the latest from XDANDROID and the phone service, data service and bluethooth wasn't working yet.

Thanks,

HERE Android on TP2 has it's on sub forum now.

[powerplyer]

Hello switch over from MightRom to Cookie. This ROM is very stable and great. I have one issue that has been discussed in this forum is the +1 dialing. My phone is synced to the corporate network and all the phone numbers have a +1 (xxx) xxx-xxxx format. In the Mighty Rom I was able to goto CDMA services and disable the prefix dialing. However in the Energy Cookie Rom this option is not available. I have tried Global and CDMA only and I do not see the options. Is there a CAB to enable these option or a reg hack to disable prefix dialing.

Thanks in advance for the help. I sure hope I there is a fix.

[JustDavid]

Originally Posted by bsarlo

Yeah, I bet it's because I have 2010. Anyway, I do have Outlook 2010 installed and set as the default. I've been getting this error for months now, ever since we got the first 2010 to test. Maybe it's a bug and MS will work it out when they release it for real. Sorry I forgot about the fact that I've been getting MS Office products a little bit before they're released.

I think the 3/13 NRG ROM release fixed the File Explorer disappearing issue.

The 32 bit version of Office 2010 works fine. The 64 bit version will give you the message about not having Outlook installed when trying to sync. I had to uninstall the 64 bit version because of this.

[bsarlo]

Originally Posted by JustDavid

The 32 bit version of Office 2010 works fine. The 64 bit version will give you the message about not having Outlook installed when trying to sync. I had to uninstall the 64 bit version because of this.

Did you find this on any MS websites or has this same thing happened to you? I cannot find any documentation. Was your file explorer opening to the System32 folder as well?

I personally prefer 64-bit, so I guess I'll have to live with it until a fix is developed in the next release.