slow att tilt - General Questions and Answers

ever since i added the manila program my tilt has been slow and the doesnt screen turn on every program when i open it.

i have the tilt with manila with no problems, just like many others, make sure you have enough space, and run some cleanup program to delete any temp files that might be eating up your phones memory.

try flashing a manilla rom

Related

HTC touch Today plugin - slowness

I searched around and haven't seen a thread about this yet but I think we should look at the slowness of the plugin. I know that on my G4 which was OS flashed to Crossbow it's totally bogged down now. Seen some reports of others. Is this a memory leak or conflict or just a case of code needing to be optimized? I've tried a few different configs so far but can't get past it.
ive noticed the same thing about mine. mines a g3 and it was very fast before but now its slow as heck after i installed the plug in. im not sure how to fix it. just confirming the problem on another phone.
It's fine on my HTC Touch
alanp23 said:
It's fine on my HTC Touch
Click to expand...
Click to collapse
Fine on my hermes too...
small lag on prophet,when i press the softkeys....But overall phone speed is ok!
Processors
Hermes has a 400mhz processor, so it should be ok on there!
However, I have a Wizard, which is only 200mhz, and it is absolutely crawling using this plugin!! But it's (as far as I know) the same processor as the Touch, so what is it that's causing it to run so slowly?
myk_83 said:
Hermes has a 400mhz processor, so it should be ok on there!
However, I have a Wizard, which is only 200mhz, and it is absolutely crawling using this plugin!! But it's (as far as I know) the same processor as the Touch, so what is it that's causing it to run so slowly?
Click to expand...
Click to collapse
I think the problem is with the access to \windows\ folder, try to open the folder and see how many time it takes...
The only problem I have with that theory, is that I assume the HTC Touch doesn't run this slowly all the time, yet that has the same processor as the Wizard and must have the same amount of files in the Windows foler?
Hermes has a faster processor, and Prophet is probably similar in design to the Touch, so they might mask the problems a bit better than the Wizard I guess. But there must be some way of making it run faster!
Already done it.Without HTC Home Plugin 5- secs,with the plugin 10+... I don't use the weather item,so i'm going to delete the weather pics.... and i will post results...
Same thing...lag... BUT i hard resetted,then installed HTC Home Plugin,and it was running full speed!then installed the HTC Touch pad and lag again....
Lagging on wizard G3
I have a G3 wizard and I'm having an incredible slowdown (both reboot and executions)
I installed the Home plug, comm man, dial pad (directly after the flash) and then installed spb pocketplus and netfront! That's all..
I can access the /windows folder in +/-13 secs
I reverted to my previous backup without the new HTC apps, and WOW!
Windows folder shows up almost instantly. Everything is alot smoother than with the Touch today plugin. But it is uglier as well.
What ROM is everyone using? Has anyone installed this on faria or most beautiful?
I know on Crossbow it slows down with just the today plugin installed.
Homeplug disgustingly slow on prophet here (latest Pdaviet rom, 234mhz), ....And then after I put the touch dialler on as well....Ugh! ...
ended up having to keep soft resetting just to stop unwanted dialling from tapping!
Interesting about the windows folder as for me, xp is taking forever to open this folder too. Looks like a hard reset is due....then I'll try again
triplejay said:
Homeplug disgustingly slow on prophet here (latest [...]....And then after I put the touch dialler on as well....Ugh! ...[...]
Click to expand...
Click to collapse
In fact, it seems every Touch application (dialer, htc home plugin, maybe even the sound manager?) slows the device a factor, but the home plugin is the worst.
I played with installing and uninstalling them after a hard reset. I agree it seems like the fuller the \Windows folder, the slower the device, but indeed that makes no sense.
Using Faria's latest, err, lets call it "10.1.0.811 WWE" on my Wizard. XM6?
Expander said:
In fact, it seems every Touch application (dialer, htc home plugin, maybe even the sound manager?) slows the device a factor, but the home plugin is the worst.
I played with installing and uninstalling them after a hard reset. I agree it seems like the fuller the \Windows folder, the slower the device, but indeed that makes no sense.
Using Faria's latest, err, lets call it "10.1.0.811 WWE" on my Wizard. XM6?
Click to expand...
Click to collapse
it has tons of pngs that it loads into the /window folder which lead to the explorer taking a lonfg time to open it
Just wanna report the same slowness on my MDA Vario [email protected] wonderfull XM6. But the looks are great, the slowlyness sucks. So does this mean that the plugins have to be optimized or can it be done through the registry?
After hard-reset I installed Dialer, and the phone was sluggish again, even without the today homeplug...
I guess it also has something to do, like already was said, with the graphical aspect of it. Many png's in the windows folder which are loaded for displaying everything that nice.
will one of you see if chabging the attributes of the png (to hidden,system,...) will change anything?
fallenczar said:
will one of you see if chabging the attributes of the png (to hidden,system,...) will change anything?
Click to expand...
Click to collapse
My windows folder is taking 31 sec to load up. I made all png files (about 1.4 meg worth) both hidden and system. Windows folder still takes 30 seconds to load. General responsiveness of the device did seem to get faster but I can't tell if it's that or the fact I flashed the official MS WM6 rom. Seems like since the plugin still references them it's taking up resources. Any way we can pack those into the plugin exe or would placing these in rom or extended rom speed up the process?
The plugin with official wm6 seems faster then xm6. Not talking smack, just an observation. I can't try NBD 7.0 since it won't flash properly but I've heard that's the fastest w/ plugin so far.

Today plugin and SIP memory

I'm having trouble with this shared memory. I can't get stuff like calligrapher to load up about half the time. I have using SKTools DELETED completely many today plugins, and all other SIPs from HTC. My today screen is also completely empty. Still I have trouble loading anything other than the keyboard. Even transcriber won't load sometimes. Any ideas how to find out what's taking up today memory? Or how to increase it?
Any luck on this?
I'm curious, too. Granted, Calligrapher, PCM keyboard, Ultimate Launch eith PhoneAlarm, Weatherpanel, and a bunch of other smaller plugins might be too much to ask, but I seem to get the best results when I ask just a bit too much. I'd gladly sacrifice some program memory to have all my sips at the ready. I'd even take a walk though a kitchen & build my own rom if i could increase this tiny memory pocket reserved for sips & today. Anyone care to be a hero & explain it?
Calligrapher only, load with lnk
but still empty today screen.

WCELOAD.exe during customization

Hi,
I am using in my ROM the normal process to start the customization after burning the ROM.
File \OEM\OperatorPKG\mxipupdate_zzPIED_101.provxml:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Comm" >
<parm name="AutoRunCFG" value="\windows\config_operator.txt" datatype="string" />
<parm name="AutoRun" value="\windows\AutoRun.exe" datatype="string" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
In my config_operator.txt I am installing some CABs - which works fine.
My idea was to delete all CABs after installation automatically. For that reason I have changed a *.rgu under \SYS\Shell:
from
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /delete 1"
to
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /nodelete"
In normal cases @="wceload.exe \"%1\" /delete 1" makes sure the a CAB will be deleted after installation.
If I install a CAB after customization the CAB is gone - so far so good - means the entry in the registry is fine.
Unfortunately, during the customization (which works fine) the CABs are still under \windows. It seems that the above change does not work with customization.
Question:
Does the autorun process (during the customization) after burning a ROM also using the wceload.exe to install a CAB ?
Regards
kuzco1
I was going to ask a very similar question, but I think I'll just bump yours instead
'Burn' the ROM
Yes, really like it rather than 'flash'.
If u want the cab deleted after autorun, just remove the read-only attributes & vice-versa. (if cabs in SD)
/nodelete switch wont work as it still delete the cab if the cab is not with read-only attr.
i think autorun doesnt use wceload but let the experts confirm it first. Just my guess.
So you want to delete a file from the ROM during customization (wont work) or off the MicroSD (would work), however I don't think I would include something from the SD in the customization XML I would use an auto installer first.
Thanks
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
bengalih said:
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
Click to expand...
Click to collapse
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
mbarvian said:
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
Click to expand...
Click to collapse
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
bengalih said:
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
Click to expand...
Click to collapse
wow, another good post
that is basically what I am trying to accomplish. I have my registry tweaks, files that don't get updated (Office, etc.) cooked in, but for some reason I cannot change the look of the dialer (I wanted to use poorlyduck's diamond dialer) by converting it to an OEM package with Ervius' Package Creator. Same with the comm manager skin. Therfore, I have resorted to installing these two through their default cabinet files during initial customization.
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
duttythroy said:
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
Click to expand...
Click to collapse
duttythroy said:
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
mbarvian said:
wow, another good post
....
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
Click to expand...
Click to collapse
Well dutty is by far a better cook than I... I'll stick to the scripting. I understand the basics of cooking...I just don't have the temperment for it.
However, I don't fully agree with all those points. I think his conclusions are correct, but I don't think the reasoning behind them are.
First off with space. Windows machines (be they PCs or WM devices) are basically made up of two things. File system and Registry (the registry just being a special file on the system). If I remove 2MB worth of an app from a ROM before I cook it, and then create a .CAB that contains those 2MB of files, the same amount of space is going to be taken up.
I have ripped quite a few apps to compile CABS from ROMs, and I know this to be the case.
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other point regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
bengalih said:
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other poing regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
Click to expand...
Click to collapse
can't argue with this post
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
hi,
yes you are right .. I have done the other wy. My fault in my first post. I have changed /nodelete to /delete.
But anyway, I understood that it is not possible to delete cabs during customization.
Many thanks to all
kuzco1

[ROM] Scripted Angel 6.1.20923 by RoryB

Scripted Angel 6.1.20923 - Nekid, Neat and Nearly everything versions
I say scripted because I have removed Autorun.exe and SDAutorun.exe to make room since these run once and never again until you hard reset.
I use MortScript to run my set up. This is very similar to Noonski's XDA_UC system. I also want to thank S.V.I for getting me hooked on his work.
I also removed as many files from the \windows folder as possible. This includes moving provxml file information to the rgu file when possible. Shortcuts that just get copied from \windows to other locations have been deleted and are created by my script. This is based on the idea that the fewer files you have in \windows folder, the faster your phone runs.
Do not worry. You can still have UC. My setup MortScript parses the SDConfig.txt as if it were SDAutorun.exe with some exceptions.
It does not do LOCK, HIDE, SHOW, or RESET. I have covered CPY1/CPY2, CAB, XML, TSK, and EXEC.
Since it does not support LOCK and HIDE settings you need to move the cabs you want to allow user input to the folder \Storage Card\SDAUTO\Manual.
Remove them from your SDConfig.txt file. Also, if you have registry files you use to change settings after these "manual" cab install, just place them in the Manual folder too.
The parser first installs all cab files then reg files, then xml files, then tsk files, and lastly any exe and mscr files.
You will need to respond to some OK boxes to keep setup running. Others are timed to default to my preferred choice. These are things like do you want ASyncKiller to run on your phone? Do you want BlueTooth Notification Icon to run on your phone? etc.
If you want to try to control the sequence which each file in a group (CAB, REG, etc) installs try putting 00_, 01_, etc as the first characters in the file name.
If like me you have some cabs that you have installed to your sdcard you can do the following. I have a folder \Storage Card\SDAUTO\Zip where I place zip files of the programs files I need on the phone like the shortcuts, etc.
I also place a reg file in the folder \Storage Card\SDAUTO\Zip that sets the registry for the program.
The parser unzips all of the zip files to the root of your phone and then runs all of the reg files.
Your zip files should have the folder hierchy in them.
I also have the ability to not use SDConfig.txt for silent cab install. Place any cabs in the folder \Storage Card\SDAUTO\Silent you want installed without response required.
This parser also first installs all cab files then reg files, then xml files, then tsk files, and last any mscr files.
Some other notes.
While my script is similar to Noonski's XDA_UC, it is not the same. He is working very hard on a system that is not language or device dependent. I on the other hand have written my script for my Wizard and for WWE. My script does not support XDA_UC or XDAS files, etc.
For Mort's sake: Please do not report any errors to the MortScript Forum but to the Forum Thread of the Rom you have just Flashed. Adding other user created or your own scripts can do serious damage to your device, only use installations from a trusted or confirmed source, but the responsibility and choice to use these, is always your own. Remove your SD Card if you want to prevent other than the phone's setup.
Page Pool is what it has always been 6 MB
DO NOT ACCEPT ANY REQUESTS FOR REBOOT. Phone will automatically reboot after you pick OK on finished notice.
Nekid Angel
I took out everything I thought I could. It still has Mobile Office and it has MortScript to run my setup.
Right after flash without running my User Customization.
Storage 44.34 MB free
Program 32.16 MB free
----------------------------------------------------------------------
Nearly Everything Angel
This is very close to S.V.I's typical Angel. It has everything he has typically put in it plus MortScript to run my version of setup.
You will need to install an adobe reader program if you want to read the manual for MortScript.
Right after flash without running my User Customization.
Storage 40.83 MB free
Program 26.52 MB free
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Neat Angel
This is the Angel I use.
It has the following removed:
OperaMini
SAP Settings - lets your car's bluetooth access you SIM card
1-Calc Lite - have my own calculator
Touch Response - decided I don't like the vibration
PIM Backup - I do not use this
BT Icon - I do not use this
I added:
Adobe Reader
Transcriber
Right after flash without running my User Customization.
Storage 42.24 MB free
Program 27.41 MB free
Neat Angel in 21054 Port
I took my neat scripted Angel and ported 21054 stuff to it.
My understanding is that 21054 is the last WM6.1 version out here.
Let me know what you think.
I had to take out Transcriber, and Adobe Reader
Right after flash without my customization
Storage 42.69 MB free
Program 26.40 MB free
dotfred's task manager is called dftaskmgr.exe to make it work with the WM version.
Fixed missing MMS, I accidentally removed the package. I managed to get Adobe Reader put in. I got weather working again.
Here's the new link http://rapidshare.com/files/284946281/21054_port_Neat_Angel_nk.nbf
MediaFire http://www.mediafire.com/file/ianqzukmyym/21054_port_Neat_Angel_nk.nbf
I did not put any of the package called Browsingie in the ROM above because it is so big. I put it in this ROM http://rapidshare.com/files/284946285/Browsingie_nk.nbf, but had to remove M2D and a lot more to get it to fit.
Now the bad news. I do not know what this Browsingie ROM looks like or does different because I bricked my phone. I was trying a new CID unlock method and messed it up. I won't be able to cook any more since I cannot test to see if any of the tweaks I do work.
Here are the kitchen files http://rapidshare.com/files/284957064/Port_21054_Angel_Kitchen.rar
Updated Kitchen: Neat Angel in 21054 Port with Extended_ROM
First, I was able to buy a lab rat from eBay to continue cooking.
I fixed up my kitchen to the latest implantxip.exe version. With this I was able to tryremove the ULDR and other things that has given me more room to fit stuff into the ROM.
This is the Browsingie version. I put back Transcriber and Adobe Reader. I also fit in Voice Command and Remote Desktop.
dotfred's task manager is called dftaskmgr.exe to avoid conflict with the WM version.
I think I have avoided the Extended_ROM problem I have seen mentioned before of battery drain if you flash a new Extended ROM. The extended ROM is still locked and hidden. I am using Extended ROM to install M2D and M2DC. The nice thing about this is you can use remove programs to get rid of them if you prefer a different home screen.
I also use zip files in the Extended ROM to hold files that just got copied over to other folders. This way there are not copies in the windows directory and now there are not even the zip files.
So if you use Extended ROM to hold files they will get overwritten by this ROM.
Here's the new link http://rapidshare.com/files/346929040/091112_Port21054_Ext_ROM_Browsingie_nk.nbf
MEGA Angel with 21056 Port and using Extended_ROM
I have two versions of MEGA Angel.
Based on version 23 Manila2D RapidShare MediaFire MegaUpload
Based on version 1917 Manila2D RapidShare MediaFire MegaUpload
version 1917 Manila2D with Extendir to see if it speeds things up RapidShare MediaFire MegaUpload
This is the older version of Extendir ver1.06 with 2MB cache
They both have everything in common except the version of Manila2D.
Both have working Album and Music tabs. Sound profiles does not work in the ver 1917 settings tabs, but I added a link to the program under \programs\tools in the start menu.
Still using Extended_ROM to fit everything. Mega is big. ROM setup takes a while as a result of so many files too.
Some things I have done:
Radio is off at the start. Reduces chance of call coming in while ROM is setting up. Turns on near the end and runs Network Wizard to set up phone service.
Took out ModemLink since it is the same as InternetShare and I doubt anyone uses the infrared method in ModemLink.
Took out Network Plugin since it requires a reboot every time you change it.
Added Total Commander for its features including the ability to have LAN and FTP connections, which replaces Network Plugin.
CommManager has nice feature. Select the text and you get the settings panel for that item. Select the on/off button and you start or stop the device.
BlueTooth settings allows start up of BlueTooth FTP and has a timeout settings for the radio.
USBtoPC is set to not be the enhanced feature setting by default.
Do not reset your phone while it is setting up. When Network Wizard says it is done and to reset, select cancel. ROM setup will reboot when it is done.
If I think of anything else I'll update.
you make me wish I still had my wizard.
is it still the same OS or have you updated?
It is still the same OS. 20923
I have been avoiding the 21xxx series of ROMs since Cracing has said they have memory drain or leaking issues.
I am trying to keep the strengths of your original Angel. I have just been playing with the clean up of what is in it.
Oops
Updated links for all three versions.
I removed debugging text messages to speed up setup.
thanx!!!!!!!!!!
Thank you for your work.Can I flash the rom as useal?
They are OS only nk.nbf files. You can flash your Wizard however you typically flash a nbf file to it. Since they are OS only they are G3 and G4 safe.
Nekid
Thanks RoryB.
I've always wanted the Nekid Angel. You had posted the source for it in your FFA thread. But I couldn't get it to compile. Too many errors and stuff.
Well, I will be installing the Nekid Angeld soon. I do not use any of the programs that you guys normally do. I just need a few small utils, which I have cabs to install.
So a big thank you for cleaning this up. Much appreciated.
A QQ -
Do I need to downgrade to install this? I have Final Final Angel installed.
Or can I just put it in soft IPL and load Nekid Angel?
You will be replacing the old Angel when you flash this one.
As far as downgrading is concerned. I have not done that for some time. I used to flash back to my original ROM and then flash a new one, but for me it does not seem to matter. I would say to just try flashing straight to your new ROM.
Thanks!!!
Today morning I installed Nekid Angel. I'm really loving it. Simple and fast. And allows a lot of space for what I want. Thanks a ton!!!
So far so good, no issues. Working like a charm.
SMS sent folder synch?
Guys,
I observed this in WM6.1. I've disabled threaded SMS and it does not store the SMS I sent in the sent folder. I really hate threaded SMS.
Is there a hack or way to store the sent SMS in the sent folder? I've tried a couple of things, but can not get it to work.
Hopefully someone that uses SMS/MMS can help you. Our company blocks them on our plan
Shift and symbol keys
Guys,
I'm facing problems with Shift and Caps keys on the keyboard. Is anyone else facing this problem?
Sometimes the shift key just wont work... have to press it hard or 2-3 times to get it to work. Not such a problem with Caps key.
But yes, sometimes these two keys in combination do irritate a lot when texting someone or when trying to type numbers.
My ELF might be dead but i stills got my Wizard .
Check the Forum for "MortScript HTML Manual" i'ts a bit lighter to include, but it might also be a bit outdated for some of the updates. (some prety faced Drunk posted it).
RoryB said:
Nearly Everything Angel
This is very close to S.V.I's typical Angel. It has everything he has typically put in it plus MortScript to run my version of setup.
You will need to install an adobe reader program if you want to read the manual for MortScript.
Right after flash without running my User Customization.
Storage 40.83 MB free
Program 26.52 MB free
Click to expand...
Click to collapse
Works great so far. I work out of town alot and roam alot as well...will post when i return how that all has worked for me. Lotsa room for the system to work. very little hesitation. Will keep you posted....Thanks
screenshots anyone ?
http://forum.xda-developers.com/attachment.php?attachmentid=201368&d=1246567845
http://forum.xda-developers.com/attachment.php?attachmentid=189290&d=1243429966
http://forum.xda-developers.com/attachment.php?attachmentid=189291&d=1243429966
Same as original Angel, but I removed Autorun and SDAutorun and use a mortscript ot parse the config and sdconfig files. Gains a (very) little more room in memory.

is there anyway to increase programs launching speed?

is there anyway to increase programs launching speed?
i ask this because every time i open up a program on my windows phone, it takes about 2 to 3 secs to load up something (there is just a rotating wait cursor), and the program appears then.
both my omnia ii and hd2 are suffering this problem.
i am wondering if the launching program speed could be increased by doing something? say changing some registry or increasing papepool size?
thanks!
You could use a task manager to see if your memory is not taken by some other process, you can also use overclocking, but don't forget that some programs need to cache or load database before starting.
Quite a lot of things can slow the launch down. Does it the program live in main memory or on a storage card? If it is the latter it has to be read out of the card into main memory before it can be launched.
If the application was written in .NET CF, VB C# etc., and especially if the application is quite large, there is a hit in performance while the JIT compiler converts the IL instructions in the executable to native ARM code in order to able to run it.
If the .NET executable is on a storage card then the delays above get combined.
I think cook rom with 12M pagepool would be good enough. I current running 6.5 with with config running like cham~
hungelt8 said:
is there anyway to increase programs launching speed?
i ask this because every time i open up a program on my windows phone, it takes about 2 to 3 secs to load up something (there is just a rotating wait cursor), and the program appears then.
both my omnia ii and hd2 are suffering this problem.
i am wondering if the launching program speed could be increased by doing something? say changing some registry or increasing papepool size?
thanks!
Click to expand...
Click to collapse
Open the program then go to the today screen. Open task manager and add the running program to the exclusive list. Now each time it is opened you should notice less lag. More ram will be in use however.

Categories

Resources