Related
Hello,
I puchased a Tmobile MDA USA (Wizard) over a week ago.
I have noticed the extremely slow boot up time of the device.
Mine takes 3.11 mins to boot up to a useable today screen after a soft reset.
I have SPB Pocket Plus and Phone alarm loaded as today plugins.
How long does yours take ?
Any way to improve that that ?
--------------------------------------------------
It's Ok I have just flashed with the K-Jam rom. Now boots up in 1min 10 secs.
Please keep telling your times. Might help Others
Thank you
65 secs
I have many more startup programs than you.
Do you have the latest ROM?
I am not sure if I have the latest ROM. I have 1.8.10.2 WWE dated on the 12/10/05
I have found this page ftp://xda-developers.com/Wizard/Roms/Tmobile/ but I am not sure what all the numbers are and if they are right for my phone.
Thank you
I cannot help you there, cause I use a totally diff ROm, a Greek one.
Someone with similar ROM as yours should answer
BTW, the link you posted is dead...not working
Regards
SPB Pocket Plus is what is killing your phone. After about 10 minutes I uninstalled it. It's way too much of a resource hog.
As for rom flashes, I'm still trying to figure out everything about it before making the jump. The iMate rom package will update everything, but you need to install some TMO extended rom bits by yourself (since the iMate flash will put an iMate extended rom on the device, which won't configure everything for USA TMO settings), but you also have to watch out as a few of the TMO Extended rom cabs will kill your wifi connection.
Also, AFAIK, the extended rom for the iMate flash is locked, so once you flash to it, you can't flash back. For a person that wants to go back to 100% bone stock when they want to, this worries me. Until I have definitive proof that the extended rom can be overwritten, I won't flash to the iMate rom.
I have the spb pocket plus + 4 other startup programs and the phone has no problem.
fuzzycuffs said:
Also, AFAIK, the extended rom for the iMate flash is locked, so once you flash to it, you can't flash back. For a person that wants to go back to 100% bone stock when they want to, this worries me. Until I have definitive proof that the extended rom can be overwritten, I won't flash to the iMate rom.
Click to expand...
Click to collapse
Its locked but it doesn't matter. Save an image of your ROM to a 128MB SD card before you dork around - you can always go back to the T-Mobile one (exception: the SPL loader, which will remain at the newer version) at any time by restoring off the SD card. This only takes a couple of minutes - its considerably faster than an RUU update as well.
I've verified that this works and leaves you with a T-Mobile load that, other than the splash screen version number for the SPL, is indistinguishable from a "fresh from box" load.
Genesis3 said:
I've verified that this works and leaves you with a T-Mobile load that, other than the splash screen version number for the SPL, is indistinguishable from a "fresh from box" load.
Click to expand...
Click to collapse
There could be an issue with this if you ever need to send the device in for a warranty service. As you state that the splash screen spl version number does not revert back to the original T-Mobile setting its possible that T-Mobile could recognise this as previously having an illegal ROM installed therefore voiding the warranty.
Mine starts in ~50-60sec and I have removed most of /Startup files, Today Items and Unused Services (DialPad)... :-(
What version of Pocket Plus? I'm told that there is a big speed difference between 3.0 and 3.1.
It's Ok I have just flashed with the K-Jam rom. Now boots up in 1min 10 secs.
Please keep telling your times. Might help Others
Thank you
Cingular 8125
Voice Command
Smart Key
Magic Button
80 Seconds
The wizard has always seamed slow to me. Howver I am coming from a Blue Angel that was 500mhz and 2003, plus I had to reboot the BA all the time... not so with the Wizard.
Later; Lew
Since I am using the Jasjar I know I should not be posting in this thread but I thought that a comparsion of the boot time will be helpful for wizard owners.
On my Jasjar I have pocket plus 3.1 and PhoneAlarm installed. Apart from this I also have Hudson Mobile Phone Dashboard and Hudson Mobile IP Dashboard on the today screen. For me the Jasjar takes 1 minute and 40 seconds to fully bottom up to the time when all items on the today screen have stabelized.
Yes Pocket Plus does takes its toll. If I remove both Pocket Plus and PhoneAlarm my boot up time improves to 1 minute and 10 seconds.
Sorry again for posting in this thread but you may find this information useful
Kind Regards
Czech T-mobile ROM 1.6.2.3
102 seconds
BTicon
CapNotify
elatepushservice.ink
GPRS monitor
SPB Pocket+
Init_Tray
PhotoContacts Pro
pooutlook
sddaemon
Services
ShutXP
Smarskey
(of course it include some default programs,like-sddaemon,pooutlook etc.)
USA, Cingular 8125, 1.8.11.1 WWE
SmartSkey 0.4
SPB Pocket Plus 3.0
Pocket Breeze 5.0
95 seconds.
T mobile MDA (UK)
About 1minute 9seconds or just over to get to the today screen..
I've only unlocked the phone..nothing else...
NO problems smrz its alwaysgood to have something to compare with.
Thank you
I have put an omapclock link in the autostart folder: But be carefully: If it is not a stable frequency you may have a dead lock. The link boost the CPU to 264 MHz. Unfortunately a lot of stuff is loaded before in the RAM (from the Flash) before the CPU is boosted. I have asked at the developers (in the development and hacking section) if it is possible to start the overclocker much earlier but some stuff (from OS point of view) has to be loaded before. Maybe one from you has a solution to start the overclocker much earlier...
Nevertheless: I have not edited the services section and have some apps to be loaded in the autostart folder (i havent got my wiyard with me, but i will report it to you). My loading time is 52 sec.
In my opinion it would first be helpful to control when which program from the autostart folder is been loaded....
At a second step it would be nice if the overclocker may be loaded via registry before all other services are loaded...
56 sec here
55 sec..!!! Got the record.
Nothing installed though
Hi,
I searched the forum to get the solution but no luck.
Hope someone can help me with the following:
My problem is that if my i-mate JasJar screen is in closed position it will not ring when somebody calls me and they get my voicemail.
When the screen is open and somebody is calling it rings and I can answer.
Can anybody tell me how to set the JasJar, so when the screen is closed it will ring when I get a call and I can pickup with the phone buttons on the side.
Regards
ber00469
You have to check version of your Radio Rom . For me it's look that you have version 1.06 or earlier. It happens often with this version. Try to change - actualy the best is v 1.09 or newest 1.11
imate blows...
Hi,
I've had my jasjar (what a name) for just a little over one month and despite having updated the unit to the latest ROM, I still experience missed calls. This occurs whether the unit itself is open or closed.
I contacted imate and got nothing but grief and extreme agravation while attempting to speak with their "live" online help. Useless.
Wish you luck.
edved.
Well thats unfortunate for the above person, however you will find like 90% of users that a Rom upgrade will correct the problem and it will generally ring on the end of the first ring or end of the second ring.
In any case since the upgrade I havent missed anycalls when ive had the device near me so.
Hopefully it will work for you too.
Osir1s said:
Well thats unfortunate for the above person, however you will find like 90% of users that a Rom upgrade will correct the problem and it will generally ring on the end of the first ring or end of the second ring.
In any case since the upgrade I havent missed anycalls when ive had the device near me so.
Hopefully it will work for you too.
Click to expand...
Click to collapse
I upgrade my rom from xda to latest qtek 9000 and radio 1.11.
The problem is again there
What's happen ? Have some idea ?
ok, some suggestions:
1. extended the ring period from 10 seconds to 30 seconds (via phone settings, or via your phone provider)
2. Make sure your ring tones are in windows\rings not on an sd card
3. Use smaller ring tones, that run less than 30 seconds and start up quickly
4. Disable the video call feature and use the original phone pad if you can do without video calls and the "nice" phone pad
5. Ensure that anyting tying that runs at startup is installed to the device, so when it does start, it doesnt need to start loading dlls and apps when it wakes up.
Rule of thumb, if its needed at startup, or needed on the today screen install to the device.
If none of these work, please provide more details of your device. It is highly unlikely to be the device, and more likely to be what you have done to it. So we would need a summary of answers to the above, plus details of what is installed to what location (device or card).
Simon
simon_darley said:
ok, some suggestions:
1. extended the ring period from 10 seconds to 30 seconds (via phone settings, or via your phone provider)
2. Make sure your ring tones are in windows\rings not on an sd card
3. Use smaller ring tones, that run less than 30 seconds and start up quickly
4. Disable the video call feature and use the original phone pad if you can do without video calls and the "nice" phone pad
5. Ensure that anyting tying that runs at startup is installed to the device, so when it does start, it doesnt need to start loading dlls and apps when it wakes up.
Rule of thumb, if its needed at startup, or needed on the today screen install to the device.
If none of these work, please provide more details of your device. It is highly unlikely to be the device, and more likely to be what you have done to it. So we would need a summary of answers to the above, plus details of what is installed to what location (device or card).
Simon
Click to expand...
Click to collapse
1. was done
2. was done
3. use just the original ringtones
4. was done
5. I've done HR and then there was no problem. So I,ve reinstalled just the Hack performancetweackhighresource and the problem come again.
So, I think the problem is on the use of cache from the hack.
Thank's a lot for suggestion.
Filippo
We found in Poland that sometimes it happens on the edge of network coverage ( ie UMTS). Radio unit is checking signal every few second and change band from GSM to UMTS - it can create problems. So if you are on the edge turn off UMTS plz.
jas_pik said:
We found in Poland that sometimes it happens on the edge of network coverage ( ie UMTS). Radio unit is checking signal every few second and change band from GSM to UMTS - it can create problems. So if you are on the edge turn off UMTS plz.
Click to expand...
Click to collapse
I think about this but I'm in a full covered umts area.
Looking at the hack i've seen it use half cache size and so, I think, it freeze rings from memory.
i also had a problem with that performance tweak and never used it again after my last hard reset.
i find the device with the latest rom runs pretty well with minimal amount of tweaks.
try to undo the performance tweak manually, and see how you go. if necessary HR (painful i know) and rebuild it without.
i would also suggest backup software at the stages through the rebuild so that it can all be repaired and rebuilt.
simon_darley said:
try to undo the performance tweak manually.
Click to expand...
Click to collapse
Sorry to be thick but are we talking about the fatfs cache size?
Am sure mine (m5000) came with this enabled and set to 4096 - is this the default?
or are we talking about the font cache tweak?
thanks
matt
matt1971 said:
simon_darley said:
try to undo the performance tweak manually.
Click to expand...
Click to collapse
Sorry to be thick but are we talking about the fatfs cache size?
Am sure mine (m5000) came with this enabled and set to 4096 - is this the default?
or are we talking about the font cache tweak?
thanks
matt
Click to expand...
Click to collapse
The performancetwekhighresources do that for i.e.:
In HKLM-SYSTEM-STORAGE MANAGER change cache size and daata cache size in 0x00004000 (16384)
hi everyone, i would like to know why the hell everytime i insert my SD card i lose about... 10MB of RAM? and when i remove it, they come back, this is really annoying, and no i don't have anything running @ startup from the storage card.
Thanks in advance everyone
I too have been experiencing a memory leak but didn't know whats causing it. Now that you mentioned this, i pulled out my Mini Sd and Ram to 15mb free, i plug it back in now there is 5.7mb free. I just hard reset this morning
What rom are you using? I'm on Summiter's customized 2.17 w/a2dp
and the apps installed on device mem is as follows:
Opera Browser
SPB Pocket +
Resco Explorer V5.40
Skype
Micro. Voice Command
and a bunch of reg edits.
Now i just got some error with "relprog.exe" and i sent the error report and now its down to 4.9MB free..
---------update-----------
I just soft reset and when it turned on it reported 10mb free, took out mini sd and now its at 18 free....
Nothing strange about that. It simply memory reserved for running the SD. card data, working space etc. It's the same thing on your PC. Though you might not notice it since you probably have about 2GB of RAM like me
like someone said i guess we are still beta testing this windblows mobile 5, and alabij, that makes sense but since i have a nokia 6630 too which is on a symbian platform and that does not happen, i really thought this was very strange
we are beta testing(and paying 500bucks)
for wm5
this things gonna happen
double post...
the problem is i don't remember this happening on my Jam(magician) sp3, sp3i or sp5... started recently(within this month) on my kjam(wizard) and i don't think its normal for a storage card to take 10mb of ram to be accessible. My device is basicly crippled with this BS! i can't run anything with 4mb of ram. I think i'm gonna hard reset next week and run my device barebone(nothing installed) and see if it does it just to prove taht 10mb ram is not needed to read a miniSD card.
I've had a lot of headaches over wm devices but this is by far the worst because for every other problem there is a solution. there may be a solution for this, but so far no ones reported one yet.
yes, no way should it take that much to run a memory card. i just tested mine and it takes less than a third of a megabyte. not sure if this helps, but i had a bad card which often brought my mda to its knees trying to cope with it and all its bad sectors. maybe try formating it or trying another.
so is it really just devilboy1488 and I that are experiencing this?
SOLVED
fone_fanatic said:
so is it really just devilboy1488 and I that are experiencing this?
Click to expand...
Click to collapse
i upgraded to Cingular Official AKU 2.2 ROM and this stopped happening
Thanks All
Normal load - card in - 13.7 free
Normal load - card out - 17.9 free
Using the newest summiter rom.
try using the official rom
Re: SOLVED
devilboy1488 said:
fone_fanatic said:
so is it really just devilboy1488 and I that are experiencing this?
Click to expand...
Click to collapse
i upgraded to Cingular Official AKU 2.2 ROM and this stopped happening
Thanks All
Click to expand...
Click to collapse
mine did not it uses 4/5 mb.
cinguler 2.2?
where did you get the Cingular Official AKU 2.2 ROM? I have the Cingular 1.8.11.1 right now, I got my phone off of ebay and it was unlocked. If I install the official Cingular ROM will it relock the phone?
What is a normal memory? I was running close to 20, before but I had to hard reset, and now I am down to 14-15. Is that OK? I am using the 2.17 rom, havent updated to the latest yet. It is so much hassle, to keep upgrading.
I'm running the 2.21 ROM and use a 512Mb miniSD. When I eject it my program RAM drops from 17.74Mb to 17.50Mb. It is consistant with every eject and insert. The storage RAM doesn't change at all.
i think i found the problem. Last night i reflashed my device with the official imate rom and after installing all my regular apps and all the reg edits, i was back to square one. From 21mb free to around 10mb after i insterted my memory card. so i undid a few reg edits such as increase font cache, glyph cache, and the 2 enhanced perfomance reg edits which increase storage manager cache sizes. So basicly all the cache increase reg edits were causing this, or so i noticed from my little test. Now i've got 21.95 free without card and 19.65 free with the card in which is a lot better than before
Hay,
I'm using i-mate jasjar, and since day 1 (bought it sep 2005) i've had the problem of slow wakeup and generally slow response. I've run suggested apps such as pocket mechanic etc to remove duplicate wake-up hooks etc, with only slight effect. I've tried several ROMs, none better than the other... I have no extra software installed (i don't want to make it slower than it already is!)
*From i hit a button till the device is (awake) accepting commands takes 10-20 secs...
*From someone starts ringing till my phone is awake enough to start ringing takes 8-10 seconds. clicking the answer button takes another 5+ seconds.
*Dialing is slow (pressing numbers), i suspect it's the DTMF .wav files that take time to load. If i dial too fast, the order of keys pressed are messed up! (say i dial 1-2-3-4, phone takes 4-5 seconds to react, then types 1-2-4-3)
*When i have the usb on, and screen is on, from i click start button, it takes 5-10 seconds before it's displayed. I've tracked this down to a problem reading the icons of certain programs.. any fix for this?
I'm using rom 1.30.76(ext .164), radio 1.09.
This is the latest i-mate rom.
Is my device faulty or is this normal behaviour? Should i try another ROM? Is there any unbranded *good* ROMs out there?
please help,
Michael
VERY abnormal! I had same issue. Solved it here:
http://forum.xda-developers.com/showthread.php?t=281735
Hope it's the same thing for you. If not, work HARD on ID'ign what's on the SD card - and do my test I descroibe with the SD card removed - I bet you see an immediate improvmeent.
Try this
"HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\"
Change "CacheSize" value from "0" naar "4096".
"HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\CacheSize=0x1000(4096)"
Change "EnableCache" value to "1"
"HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt\"
Change "ReplStoreCacheSize" value to "4096"
disable the 3D phone skin and use the default one it dont has the feature where when typing in a number thats already in the phone book will show . it also looks flat . but its fast .check wiki registry hacks for it . if that dont work install the latest o2 rom with out o2 crap apps then get sktools use sktools and config divise to proformance. trust me it will make your divice fast as wip.
faster than all cooked roms on here
Hi again,
cragiecragie4, I tried removing SD card, no improvement whatsoever on speed.
niketkumar, I tried the cache registry changes, no improvements.
tattootroy, I've run several performance optimizing programs but none make it for the better. What makes this app different?
I still suspect my device may be faulty or bugged, since my friend's device appears faster...
The old I-mate rom was alot faster than the current one, but i don't want to downgrade radio and functionality etc...
Any ROM suggestions?
I'm using the ROM covered here - seems good.
http://forum.xda-developers.com/showthread.php?t=279258&page=1
Done a LOT of installation and work after basic re-flash, but overall I havn't found any bugs at all (despite what others complain about). Sorry, except that the .NET CF2.0 is badly installed.
Did you run my test? Remember that if you remove SD it will still be slow once, then fast thereafter. Did you work thro it properly. I SOOO had your symptoms, and was so pissed with the whole thing I was about to reflash - then I found that this was definitely the issue.
bheam said:
niketkumar, I tried the cache registry changes, no improvements.
Click to expand...
Click to collapse
Did u waited for 10 secs and after dat did the soft reset if not try again .
hi, i had the same pb. i didn't find any solution on french forums and as i suspected my radio upgrade (from 1.09 to 1.13) and my downgrade to 1.13: i decided to hard reset and re install every app on my qtek 9000. Since then it works perfectly. hope it will help...
for info, i got version rom 1.30.97 FRE radio 1.13.00 and extROM 1.30.186 FRE
My Touch became progressively slow to the point where it hardley runs and storage mem is down to .04MB for some reason. Without installing anyting or making any huge changes to the phone what sort of things can cause it to suddenly become slow? I'm hoping there is a quick fix so I don't have to perform a hardboot. I noticed that the mxip_notify file is about 4.5MB but maybe this is normal. Here is what I am also noticing:
- mxip_notify file 4.5MB
- clock on HTC home screen doesn't change
- softboot does not improve performance
- low memory warning message constantly pops up informing me that I need
to free some memory.
This is the original ROM.
Thanks in advance.
In my experience is that you need to do a hard reset, I know its a hastle, but it helps speed it up loads.
my touch used to run out of memory as well, then i connected it to my pc, and browsed to computer\htc touch\application data\info feed\cache and cleared all the data that was there, it freed about 6 MB, also cleared the feeds folder, and freed another 2 MBs, the performance seems to have improved and i no longer get the out of memory error. i dont know if this is the culprit in ur case, but it worked for me, so u can give that a try . or try opening each and every folder in ur Touch through windows and see what files are taking lots of space. also i recently installed Home Screen ++ with which OCd my processor to 266MHz and in certain apps the performence boost is amazing. u can try that as well.
I was really hoping I would not have to hard reset my Touch since installing applications can be a pain and I have a lot of SMSs I would not like to loose. I have seen applications out there that back up SMSs and allow you to restore the SMSs back on the phone but I am not confident it will work.
And while hard resetting will solve the problem, it does not ultimately answer why my Touch suddenly ran out of space.
I'm wondering what the size of most user's mxip_notify file is.