TuMa v1.4 - BETA - WM5 ROM (RELEASED ... but has problems)

[Tuatara]

Right ... I think I'd better "pull the plug" as they say on this ROM.
There are currently too many problems apparent, which can not be directly fixed.
The problems unfortunately run deep.

Known Issues:
Pictures & Videos Fails to Start
IE can lockup (randomly) on Images
Odd ActiveSync Behaviour & non-communications
Phone Settings Page failures
Button Page (strangely?) still present
Backlight Level/Flickering
Duplicate Items (bad decision on my part)
BT Profile not appearing in Startup (Profile Bug actually)
Power Manager Bug
Battery Polling/Timing & Reporting
UPX'd Applications may be causing failures
Eval Calc continually reports "Error"
Repllog fills the event reporting

These problems most likely stem from various sources:

Optimization features to improve speed (Data issues / PIM corruption)
Interaction of AKU2 elements with AKU0 (repllog.exe Errors / ActiveSync)
UPX compressed applications (Random 'odd' behaviour)
Filesystem Respecification (standard Directories instead of PermDirs)
Possible stability issues in vBar (Phone Application Restarting)
GWES subsystem / IE extensions (Images, Pictures & Video Failure)
Application resource allocation failures (Eval Calc Failing, & other failing installs)

I will be addressing these issues over the weekend. There WILL be a new ROM at the end of this time (called v1.5) which will be either one of two possible incarnations:

1). Returning to a prior Alpha Test version which proved VERY stable, but contained a lot less of the AKU2 elements from Himalaya (incl. updated BT for reliability *sigh*)
2). Moving even MORE of the Himalaya AKU2 ROM into the current Beta (and correcting the other issues) so as to have as few as possible AKU0 elements coexisting.

Until that time I STRONGLY recommend that everyone not use this ROM - except for further BETA testing and/or bug reporting and/or suggestions for improvement (which would be VERY appreciated!)

TuMa v1.5 WILL still have the SAME feature-set, and SAME feature-rich look, but this will also be working on ENABLING CABs, instead of being a complete 'out of the box' ROM.

Wherever possible everything will still be entirely contained in the ROM to save as much Storage Space as possible and be feature complete, requiring only shortcuts, or registry entries to enable the full 'power'.

Otherwise, in it's "AU NATURELLE" state, the v1.5 ROM will functionally operate as a 'base only' ROM - which can then be used to build from.

My sincere apologies for the troubles you've encountered so far ... however it has been INVALUABLE with all the feedback, and I will be addressing as many of the issues found as quickly as possible.

I'd gotten so close ... the "race" was almost won ... but, it just 'blew up' in the final 50 meters.

__________________________________________________ __________

TuMa v1.4 has been released now for public BETA testing.

As with any BETA, backup your important data ... only time will tell how well everything has been edited/fixed/corrected in this ROM.

NOTE: There could still be some issues with this ROM, in that the performance has been increased to 'appease' those craving it, and also the feature set of the ROM has been updated to encompass everything requested.

There have been FAR too many changes, and FAR too many updates from v1.3 to even begin describing it. The ROM is now composed of 60% Wizard (Core), 20% Himalaya AKU2 (Updates), 10% Blue Angel (Drivers), and features taken from 5% Jasjar, 3% of Atom, 1% Acer, and 1% Custom Hex Edited Modules. 8)

Battery life should be much improved, speed should be about equal to Ivan's, bugs should be squashed.

Known BIG issues:
1). Sim Toolkit doesn't seem to work 100% for me - I get the menus up, but can't access all the data.
2). Bluetooth disconnect is still in this ROM.
3). Pictures & Videos Application is not working (fix being researched).

Otherwise ... let me know if you find anything!

Needless to say it's been a laborious process to get this done. So rather than bore you with words - here are some pictures instead ...

Download from:

ftp://xda:xda@ftp.xda-developers.com/BlueAngel/BA_WM5/Shipped_Extracted_Updates/TuMa%201.4/

Remember ANY and ALL CABs which are in the EXTROM Folder are OPTIONAL to install. If you don't want that feature (MMS, Java Midlets, Camera, Intellipad Languages) ... then don't install it!

Use the SetOperator.bat file to set your operator for the ROM approproately.


NOTE: SX66 Users - use the SetOperatorSX66.bat file, and DO NOT install the Camera CAB.

EDIT MDAIIIUSer 02/05/06
Changed the ftp link

[Tuatara]

Since I love my Blue Angel sooooo much. I've made a few custom Boot Logos for you to use.

Download from:

ftp://xda:xda@ftp.xda-developers.com/Uploads/BlueAngel/WM5_TuMa/TuMa_Logos.rar

You can obviously also make your own one now ... just replace BootLogo.bmp in the /Windows directory with your own 8-Bit bitmap. Make sure that the file is the same size as the one there - then you know you have the right format. 8)

*** EDIT ***

Since I've had a couple of requests for the original artwork behind these Boot Screens, I've now prepared the PhotoShop Original Artwork file for ALL of these Logos. You can now readily make your own "Blue Angel" Logo, with or without the background, or using a solid colour, or just overlaying the Windows Mobile 5.0 elements overtop. I leave it entirely up to you! It's your BootLogo after all. 8)

ftp://xda:xda@ftp.xda-developers.com/Uploads/BlueAngel/WM5_TuMa/TuMa_Blue_Angels.rar

Enjoy!

[Tuatara]

Some Games which can while away the time ...

Download from:

ftp://xda:xda@ftp.xda-developers.com/Uploads/BlueAngel/WM5_TuMa/TuMa_Games.rar

Fun, fun, fun!

[ramram]

Gr8 work Tuma :D

[TheBeholder]

Flashing right now...

Will be back later with some news.

Thanks for all the amazing work!!

[candrat]

Nice Release Tuatara!
Going to try it on the weekend :)

Thanks

[efjay]

Great work Tuatara, thanks will be flashing tonight. And extra thanks for the Xmen Angel logo, that will be my logo from now on. Mutants Rule!

[snapper245]

got this version on my sx66. No major issues.

quick question: is there a way someone can extract the "shutdown" plugin for today. My friend with a sprint 6700 wants it.

AGAIN, Great job ! and I wish I had half the brains you did so I could contribute some coding/hack. At least I will be able to help report any issues in this Beta, to make the release version a better experience for all...

[pkfloyd]

i have instaled to this version, and for now now issues. :D to report (exept the bt :) )

thanks for this good work tuatara. :mrgreen:

[TheLastOne]

OK, I've messed around with this new rom for a bit, and I've actually gotta say I prefer Tuma 1.3. The speed increase isn't significant enough to be worth adding more problems I outline below, without actually correcting any of the problems that I disliked in 1.3.

Improvements:
1) Single, fully functional WLAN Manager is nice.
2) I like the category based Program list, but your choice in some instances is well, strange. (ex. Windows Media in Office folder)

New Problems:
1) Phone settings was missing the first page (ring tone/style selection) on my first boot. Seems to be there now though. Odd.
2) Pictures & Videos (Renamed...) does not work at all. Definately a big piss off for me.
3) Internet explorer just locked up my PPC. I used it alot in 1.3, and I never experienced that. I'll see if I can reproduce it.

Dislikes:
1) Renamed Programs. I don't really like that you chose to rename the shortcuts to many Microsoft Programs. Ex: Pictures & Videos to Picture Viewer, File Explorer to Windows Explorer. Since every copy of WM5 has all these programs named the same since they are core programs, I don't think you should be renaming the shortcuts.
2) Some hefty programs. I liked that in Tuma 1.3 there was a nice balance between what was already there, and how much was left up to user discretion. By adding large programs with many alternatives such as Total Commander and vBar, I can't help feel you've crossed the line.


Further updates will come as I keep testing. Thanks for working so hard on this.

[bins]

Going to flash tomorrow...
Thanks for all the precious work so far Tuatara!

[bins]

Going to flash tomorrow...
Thanks for all the precious work so far Tuatara!

[blackflagsvn]

I am going to test this ROM. I am still wondering whether this one is better than Ivan's. Anyone who has any ideas please let me know, for the reason that I just want to bring my Blue Angel into full play.

[jamex]

good job!!!
flashing it right now

[hycool]

Thanks,I do in now

[Juggles]

Hiya..

Had major problems getting it to sync :(

Have reinstalled the Activesync twice now.. It connects (at bloody last! 3 hours and multiple soft resets later!) , goes through the new device blah blah, and then just sits at the Activesync page! Says it is connected, with LOADS of datat flowing between the device and A/S.. bot not synchronizing!


Any ideas?

Nowt has changed since TuMa 1.3 or Ivan... I had both working!

[Juggles]

Make a post, and low and behold the little fairies jump out of the screen, and waving their wands and throwing fairy dust on my PPC, it does a little beep and starts working!!!


WTF! Problem solved... :) Ask the fairies what they did if you can catch them!

[Tuatara]

OK, I've messed around with this new rom for a bit, and I've actually gotta say I prefer Tuma 1.3. The speed increase isn't significant enough to be worth adding more problems I outline below, without actually correcting any of the problems that I disliked in 1.3.

Ok ... there were a few problems in v1.3 which are definately fixed in v1.4. The speed should be noticable, but isn't the biggest 'draw-card'. Stability, and integration should be ... but as always ... can't please everyone.

Improvements:
1) Single, fully functional WLAN Manager is nice.
2) I like the category based Program list, but your choice in some instances is well, strange. (ex. Windows Media in Office folder)

1). That was a bit of work ... required some 'artwork', 'hex-editor' and 'resource hacker' customization to achieve.
2). So, is "Windows Media Player" a "Tool" then? I couldn't decide either. Well ... in the end I wasn't quite sure 'where' to put that one ... you can move them easily y'know. Besides ... it is delibrately put into the main start menu as "Media Player" so you have direct access to it from there, but also have access through the Programs Menu.

New Problems:
1) Phone settings was missing the first page (ring tone/style selection) on my first boot. Seems to be there now though. Odd.
2) Pictures & Videos (Renamed...) does not work at all. Definately a big piss off for me.
3) Internet explorer just locked up my PPC. I used it alot in 1.3, and I never experienced that. I'll see if I can reproduce it.

1). Hmmm ... can't say I've ever seen that. Works fine on my device - so maybe something subtle is happening in the Radio Layer. Most of the RIL core is now from the Himalaya AKU2.
2). Now that's a BUG which MUST BE FIXED. Damn. It was working perfectly all the previous times I have tested and worked with it. I must have done something registry-wise which is now preventing load on my last build. I will find a fix/patch for this and post it as a CAB.
3). I've been using IE over WiFi for quite a lot of surfing - not one lockup to date - incl. having BT Stereo Wireless Headset playing (albeit a bit stutteringly) in the background. I will test further when I have more time.

So ... I'll add my own one ...
4). BT Wireless Stereo Profile has some (irritating) stuttering, but otherwise works quite reliably. Need to look at performance requirements and/or wave audio driver.

Dislikes:
1) Renamed Programs. I don't really like that you chose to rename the shortcuts to many Microsoft Programs. Ex: Pictures & Videos to Picture Viewer, File Explorer to Windows Explorer. Since every copy of WM5 has all these programs named the same since they are core programs, I don't think you should be renaming the shortcuts.
2) Some hefty programs. I liked that in Tuma 1.3 there was a nice balance between what was already there, and how much was left up to user discretion. By adding large programs with many alternatives such as Total Commander and vBar, I can't help feel you've crossed the line.

1). Well, you will notice that there are TWO copies of each of the applications you mention. FIRST in the Start Menu (for direct access - named as normal), and a SECOND time in the Programs folder. In order to NOT have naming conflicts for two shortcuts (if moved), they MUST be named differently. This is an unfortunate side-effect of how the Menu Manager works. You could just delete the copy you don't want. That's what Total Commander is for.
2). Again ... both of those apps can be readily 'hidden' if you wish. vBar can be quickly disabled (just turn it off in it's control panel), and similarly the icon for Total Commander can be removed. It costs NOTHING to have them in the ROM - all of your storage space is still 100% free for you to use however you wish, for whatever you wish.

Further updates will come as I keep testing. Thanks for working so hard on this.

No worries ... as said - the ROM is aimed at an audience to work "out of the box", not necessarily for the "power hacker" who needs to customize every last element.

But having said that - everything is READILY possible to disable in the ROM, either through checkboxes, or simply by removing shortcuts. Nothing is so 'entrenched' as to be necessary, and nothing is so necessary as to not be 'disabled' easily.

Anyways ... as before, this is BETA, and I welcome constructive feedback (and criticisms) such as this! I want to resolve the last few 'annoying' bugs and try to get to a robust and stable (feature-rich) ROM.

So ... speak your thoughts ... good / bad / ugly ... let me know!

[TheBeholder]

@Tuatara

Great job, Im using it for a couple of hours and until now everything is going very good. :D

I really like the idea of a custom build, with shortcuts names changed, lots of small softwares installed and a well tweaked registry.

I need to sleep a little. I will be using my device tomorrow as usual and will report in the end of the day.

Thanks again for the hard work :!: :!: :!:

[Tuatara]

Make a post, and low and behold the little fairies jump out of the screen, and waving their wands and throwing fairy dust on my PPC, it does a little beep and starts working!!!

WTF! Problem solved... :) Ask the fairies what they did if you can catch them!

Hmmm ... this is a bit ODD. There shouldn't be any 'fairies' dancing around in the OS. Maybe a few "Angels" ... but no "Fairies".

Please let me know if you're experiencing any 'odd' behaviour. Such as 'Phone Panels' not appearing, 'Active Sync' not working immediately, 'WiFi' issues, or otherwise. Maybe a 'Gremlin' has snuck into my 'Frankenstein' ROM Monster.

[efjay]

Pros

Rom is a bit faster, especially messaging, opens without as much delay as before

A2DP works and pairing with a SE HBH-200 also worked with no problems

Media player playes mp3's with no buffering issues

Activesync no longer closes when using WMP10 on the pc

More useful programs added

Wifi works ok connecting to WPA

Contacts stored on sim card display names on BT headset display

Cons

Backlight level seems to flicker when on battery

Mentioned before, program renaming not really necessary, also some duplication eg Word Mobile

Picture & Videos doesnt open

Music via A2DP has a scratchy quality to it

Have installed a few apps like O2 Plus, Double Launcher, Device Lock with no problems. Overall this is a definite improvement over 1.3 with only the Pics and Vids the most obvious bug.

Well done Tuatara and thanks agian for the hard work.

Edit: Didnt see your post Tuatara, you've answered most of my issues. Two things: there is a Startup Manager app here http://forum.xda-developers.com/viewtopic.php?t=47184 Maybe this can be added to the rom. Also is the push email part of AKU2 part of this rom? Thanks

[Tuatara]

Pros

Good news ... 8)

Cons

1). Backlight level seems to flicker when on battery

2). Mentioned before, program renaming not really necessary, also some duplication eg Word Mobile

3). Picture & Videos doesnt open

4). Music via A2DP has a scratchy quality to it

1). I think I've been too aggressive with the power manager settings. The device is probably (briefly) entering an 'idle' state, and I'm shutting down the backlight (to save as much power as possible). This is an 'over' correction of the battery usage issues which people mentioned. I'll look into this and post a fix.

2). Ok ... I'll make a CAB which either deletes and/or renames these items ... maybe out of existance for those users who want it. :D

3). BUG ... DEFINITE BUG. MUST BE FIXED. ARRGH. *sigh*

4). I've noticed this too ... there may be a slight incompatibility in the BT elements I've integrated for the Audio Gateway/Avcrp/A2DP profiles. Needs more testing and research.

Well done Tuatara and thanks agian for the hard work.

You're welcome. Like I said elsewhere ... it's for my own 'selfish' reasons too. ;-)

Edit: Didnt see your post Tuatara, you've answered most of my issues. Two things: there is a Startup Manager app here http://forum.xda-developers.com/viewtopic.php?t=47184 Maybe this can be added to the rom.

I've been LOOKING for something like this! I'll add this to the 'fixes' CAB for those who want to manage their startup elements (vBar, Batti, etc.).

Also is the push email part of AKU2 part of this rom?

No ... not yet. Not all AKU2 elements are compatible with the current coredll.dll we have embedded in the XIP section. I'm slowly identifying what can be moved and what can't. Hopefully I'll be able to add the AKU2 functionality in, without needing to 'hack' the XIP section. *fingers*crossed*

[borjok536]

Im here in school and Im downloading it now.. I cnt wait to test this ROM, Im using now the Ivan's ROM v4, and I like the Widcomm BT stack used.. In this TuMA v1.4, what is the BT Stack used? Still MS Stack?

[borjok536]

that you can release a TuMa version with Widcomm BT Stack separately? ... I dont have issues on Widcomm BT stack with Ivan's ROM (though I dit not try the BT headset, coz I dont use it at all)...

[snapper245]

first bug I've encountered:

Even with full charge (green LED), get Backup Battery low power alarm. Happens even when plugged in. specifically happened during last program install to device.
check to the power settings icon shows both main and backup batteries at 100%

anyone else seeing this?

[AndyInParadise]

I am not able to restore using Sprite Backup V5.0.1 Build 1332.
I have been changing Roms between Ivans and TuMa over the last few months and have been able to restore everytime. This is the first time I have not been able to restore..... Causing me a big problem as I do not use a PC (I use an Apple MAC and we all know that we cannot sync WM5 with Apple), so I do not have any other backup.
Thanks in advance.

[Thuanfx]

Thanks so much for your ROM
Now you can relax after the day work hard??/

I'm going to upgrade tonight

Best Regard

[laoshu]

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.

[cmairhof]

First of all I would like to say thanks for a great new version. I have not encountered any issues so far.

Only question: Where is the comm manager which allows me to enable push email

http://www.msexchange.org/tutorials/Exchange-2003-Mobile-Messaging-Part1-Microsoft-DirectPush-technology.html

thx for the info

cmairhofer

[bolopez]

It works on my car's handsfree kit!!! At last, it really works. As someone (sorry for forgetting your nick) suggested, it must have something to do with the MS BT stack and not with the phone, because now my HF can display the phone contacts.

There's something that I don't understand now. With previous versions (perhaps Ivan's) I could use the Spanish language kit developed for Himalaya att Buzz's site to get a Spanish interface. Now it just doesn't work. Nothing gets changed to Spanish :(

Anyway, thanks Tuatara (and everybody else) for your fine work. Having the HF working makes me very very happy (and I won´t give back th BA, I'll give back the Himalaya instead :))

[Tuatara]

that you can release a TuMa version with Widcomm BT Stack separately? ... I dont have issues on Widcomm BT stack with Ivan's ROM (though I dit not try the BT headset, coz I dont use it at all)...

Ivan has sent me the Widcomm Stack components, however I have not had the time/chance to make a Widcomm Stack Installer for TuMa and to test it. Also, I'd rather have Ivan's ROM properly evaluated and tested - especially for the BT Stack, so that we can 'trade notes' as it were, and build up better ROMs & support CABs for everyone.

first bug I've encountered:

Even with full charge (green LED), get Backup Battery low power alarm. Happens even when plugged in. specifically happened during last program install to device.
check to the power settings icon shows both main and backup batteries at 100%

Hmmm ... again, I've tried to be very aggressive in saving power on the device. I've changed the battery sampling time from every five seconds, to every 20 seconds. It's now possible that the application mistakingly (on startup?) reads a zero value since the battery poll has not as yet taken place. I'll either see if I can 'pre-charge' the result (registry value?), or maybe I'll need to put the battery poll time back to 5 seconds.

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.

Hmmm odd. I believe that KTamas has been using Wisbar Advance all the time on the TuMa v1.4 Beta. Although, there is an IMPORTANT POINT!

You WILL need to disable the vBar task bar in the ROM now if you install another task manager! vBar is based on WISBar, which uses the SAME hook/interface as Wisbar Advance! Disable the vBar one (through it's control panel), and I'm certain that Wisbar Advance will work flawlessly.

First of all I would like to say thanks for a great new version. I have not encountered any issues so far.

Cool ... well, there are some already. *sigh* ...

Only question: Where is the comm manager which allows me to enable push email

Well ... while this ROM is already making use of some AKU2 Himalaya ROM elements, it's still unable to use the FULL AKU2 support set - specifically the Push Email. In short ... I'm still working on it.

I'll try for a short while now, and see if I can sort out some of these initial bugs/issues.

[Tuatara]

I am not able to restore using Sprite Backup V5.0.1 Build 1332.
I have been changing Roms between Ivans and TuMa over the last few months and have been able to restore everytime. This is the first time I have not been able to restore..... Causing me a big problem as I do not use a PC (I use an Apple MAC and we all know that we cannot sync WM5 with Apple), so I do not have any other backup.

Additionally ...

Could the Bootlogo.exe be causing my restore problem in Sprite Backup as it needs to reboot to restore? Is there a way to stop it running?

Hi Andy, I was about to reply to your post, if only to say ... I don't know.

BootLogo.exe is a very simple application, which just loads in an 8bpp bitmap and writes it directly to the screen memory, and quits. There is no reason why this would interfere with Sprite Backup at all. It's also executed well before Sprite backup could/should even execute. There must be something else which is causing a problem ... but since I don't use Sprite Backup, I'd be at a loss where to start looking. I'll have to see (unfortunately later) if I can use Sprite Backup to backup the contents and/or what the issue could be.

There is also nothing special about the ROM/Registry settings or any protection ... all elements have been disabled (signed code, certificate requirements, etc.) ... so ... ?????

If there are other Sprite Backup users out there - please report your finding and/or if you've discovered any issues or workarounds?

[fadhelam2k]

Hi there Tuatara,

First, I wanna say great work on the ROM. I am really impressed, never imagined that it could be done and yet you are making it look so simple! Well done!

Second, I notice that you are preinstalling some applications taht maybe some users can do without. Is there a way you can build a ROM only with base models? As in when the user requires the programs, it is freely available for download and install them himself.

For example, you have a preinstalled pdf viewer, but it doesnt view Arabic files, and for that I will need to download and install the free Acrobat Reader from Adobe, but it willl just be somewhat annoying to have two applications serving the same purpose.

Plus some settings, such as BUTTONS under PERSONAL which does the same job as BUTTON LOCK, under SYSTEM. I understand setting can not be installed or anything, but do you think it can be done in a more neat way?

thanks again!

[Tuatara]

First, I wanna say great work on the ROM. I am really impressed, never imagined that it could be done and yet you are making it look so simple! Well done!

Heh ... Cheers! Well ... simple it's not. Call it a 'hobby', and a 'labour of love'.

Second, I notice that you are preinstalling some applications taht maybe some users can do without. Is there a way you can build a ROM only with base models? As in when the user requires the programs, it is freely available for download and install them himself.

Part of the goal of the ROM is to make an 'out of the box' fully functioning ROM which lets 75% of the people do pretty much everything they would need, without needing to do anything.

For the other 25%, everything which has been added can be easily disabled and/or even 'deleted' from the ROM (visibly). Having them there costs you (the end user) nothing in storage space, or functionality. It's just an extra (possibly annoying) icon.

The point behind having them installed in ROM space, is that they don't take away ANY of your precious Storage Space. This is VERY important for things like E-Mails, Contacts, Tasks, etc. If Storage is used up with 10Mb of applications ... that's 10Mb less email space. I like my Storage to be as BIG as possible. 8)

For example, you have a preinstalled pdf viewer, but it doesnt view Arabic files, and for that I will need to download and install the free Acrobat Reader from Adobe, but it willl just be somewhat annoying to have two applications serving the same purpose.

A valid point ... but tradeoffs have been made. Installing Acrobat into the ROM is VERY costly in terms of ROM space. Acrobat takes up a lot of memory space to perform the feature-rich functionality it has, and even just to get it into the ROM, I would need to remove most (if not all) other features to make space for it. For many, the ClearVue PDF Reader will meet their needs ... for those for whom it doesn't ... better install Acrobat. You would have needed to anyways.

Plus some settings, such as BUTTONS under PERSONAL which does the same job as BUTTON LOCK, under SYSTEM. I understand setting can not be installed or anything, but do you think it can be done in a more neat way?

You should NOT have any BUTTON LOCK functionality under the BUTTONS control panel in PERSONAL. This has been explicitly removed in TuMa v1.4 since this control panel extension did not correctly set the lock. At least in my ROM Flash it is not there.

Did you perform the FULL Hard-Reset (Setting NO / YES / YES) to ensure that the device contents were cleared and the registry properly rebuilt?

Did you try and RESTORE a previous set of registry settings over-top of the TuMa v1.4 ROM? If so, you're probably asking for trouble!!!

Does any one else have this panel available? *confused*

[Percz]

I'm not sure if it's a common bug with WM5 and I'm just doing something I shouldn't, but whenever I select a GIF image as the Today backround screen, it fails to load and the Today screen goes all screwy.
I see all the icons but no text on the today screen over then "Tap here to sing in to Pocket MSN".

Assuming it's not me being silly, maybe there is a GIF decoder fault (I have no idea what I'm taling about) that is also causing problems with loading the Album / Picture Viewer?

Haven't found any other faults, have noticed that this ROM can be down clocked and still seems to run as fast, which is excellent. 8)

[josaic]

upgrade successful from 1.3 to 1.4.
So far this ROM is much stable and faster than the previous one.

Thanks a lot

[Laurencesilvester]

Hi
I have noticed that when upgrading to versions 1.3 and 1.4 I seem to have a maximum call length of about 1 min. Any clues or am I missing something

thanks
Laurence

[jamex]

hey guys

here just find 3 problems in TuMa1.4

1.when i close all programs by vbar, the "phone" will flash about 4 times,

2. the wmplayer is still spending ram till playing music

3.when i sync with my desktop, it say my name was repeat, and force rename

somebody have the same problems on it

[Percz]

hey guys

here just find 3 problems in TuMa1.4

1.when i close all programs by vbar, the "phone" will flash about 4 times,

2. the wmplayer is still spending ram till playing music

3.when i sync with my desktop, it say my name was repeat, and force rename

somebody have the same problems on it

3. Unplug your BA, Open up ActivSync on your computer, "File -> Delete Mobile Device" I had the same thing but it's just because you are using the same name as your old ROM. You'll have to setup the sync options again but it won't take long.

1. Just to add, it only seems to happen once you open the phone. Something simular happens if you open up ActivSynv on the PDA, I guess because this is something blocking these aplications from being closed?

2. Too technical for me

[fadhelam2k]

I just finished installing TuMa 1.4

[You should NOT have any BUTTON LOCK functionality under the BUTTONS control panel in PERSONAL. This has been explicitly removed in TuMa v1.4 since this control panel extension did not correctly set the lock. At least in my ROM Flash it is not there.]

Well not only that, I have two SOFT KEY and SOFTKEY ADVANCED, SCREEN and SCREEN ORIENTATION, and probably some others didnt get to check.

[Did you perform the FULL Hard-Reset (Setting NO / YES / YES) to ensure that the device contents were cleared and the registry properly rebuilt?]

yes, i select first No, second Yes, third Yes, and then press MAIL

[Did you try and RESTORE a previous set of registry settings over-top of the TuMa v1.4 ROM?]

I do not backup anything except for my contacts on Outlook and my SMS messages on Jeyo Extender

Only thing I didnt do before upgrading to WM5 was the repartitioning, so basically I still have the EXTROM, do I have to delete files from that folder? I dont think its installing from it anyway!

*edit* I got rid of the extended rom by running Repart_DOC.exe on TuMa v1.4. resized to 128 kb, it gave me an error, but after hard reset the EXTROM was gone and I have increased size of program memory to 91.16, and storage memory remained at 43.26

Plus I noticed the pda vibrates when i am recieving a call on the cradle, not a good idea! Even if vibrate is enebaled it should never vibrate when it is connected to external power, safety reasons

*edit* Picture & Videos and Record are not running. The ROM hanged later in the day, and the phone wouldnt dtect network and I ws not even able to access the contacts. I had to hard reset the pda but now i lost all my contacts. I find it less stable than the previous version.


thanks

[efjay]

It seems I was wrong about Media player, I tried it again and the memory issue is still present. also PIE doesn't display all images, like the forum pm button. problem was in the very first WM5 rom.

Edit: How about adding this into the rom http://forum.xda-developers.com/viewtopic.php?t=45385

PS Did you get my pm?

[ascssmith]

Hey Tuatara, this site is great, quick question, when i setup my profile, it doesn't list my phone correctly, I have the new T-mobile MDA, here are current spec's:

Rom - 1.8.10.2, WWE 12/10/05
Radio - 1.09.10
Protocol - 4.0.13.20
ExtRom - 1.8.10.104

Cpu - OMAP850, 195 mhz
Flash Chip - M-systems 93
Model # - WIZA200, pocketPC

will your ROM update work on this phone?

AL

[nijhof]

rom is quite good.
have the feeling though Ivan's is much quicker.

main problem: BT. I believe this is the main reason for most to have switched from 2003 and the single most important issue to be dealt with.

but good work

[pkfloyd]

i again...

tuatara, i have to the button lock, on my device.( yes i put no/yes/yes to hard reset after install)

for now the ongly issues i found is:

1- the program pictures and videos its no running :(
2- bt
3- after use the phone, everytime i use a nother program and close, the phone apears and close , apears and close some times 4 times :)

tuatara, can i install the album in this version? i prefere album, becouse im pictures, it show the "exif" off the foto and histogram

this version it is very stabel, i am used for long time just open use and close programs, and some times the ba slow it down, but not crash, and this is very good, :) thanks
like you i prefere stability, that speed :)

[xsi]

I flash to this great new rom and i was quite of an impression until i install one program (memory pocket navigator) and it doesn't run at all. I had the same problem with v1.3.

This is an aplication that i really need, so i'm very sorry but i have to downgrade until this problem is solved. Holpefully very soon.

I must say that i experience memory pocket navigator with others wm5 rom's and did work very well.

I think i'm writing for all when i say great job you are doing.

Thanks a lot.

[thingonaspring]

Hi All,

Great new version Tuatara, much faster than 1.3, and the pre-installed applications have had a really good shake-up.

I just wanted to report that I too have seen the backup battery message. Not at bootup, but about 40 minutes after the previous reboot. The phone was charging at the time. Power applet shows 75% main battery, 100% backup battery.

This infrequent, intermittent message isn't a big deal in terms of using the ROM, but I thought you'd want to add it to the list for the next round of fixes.

[alinkwok]

Why there is no Windows Version upgrade on Tuma ROM?

[indra9110]

Why I cannot using Agile Messenger ??? I already intall Agile Messenger 3 BETA for Windows Mobile 5.0 PPC & Windows PPC 2003

When I run this progran always give error message

Win32 API Error. Error Code:6
(0X00000006)
Description: The handle is invalid.
C:\projects\AgMLib\src\Win32\agm_win_xsystem.cpp:8 7

[efjay]

Tuarara, a problem with the boot logo cab. I installed it but it doesnt replace the file already there so when booting one image is briefly displayed then the manually installed one is displayed.

[wynntrinh]

First of all this is a great ROM. Thank you for all the hard work.

Problem:

My Active Sync is a bit out of whack. Non of my Outlook data is syncing. The icon keeps spinning the status says "Synchronizing" but nothing is happening.

Any ideas? Thanks in advance.

[Percz]

As a few people have mentioned it, I would just like to add that the very first time you sync this device with a Microsoft Exchange Server after updating to 1.4 the ActiveSync will appear to connect but not do anything. All you need to is go into the Kitchen and make your self a cup of coffee, watch a few minutes TV and suddenly everything will be on there. Just the first time takes a very long time for some reason, and after that it's fine.
*DO NOT RESET* while you are waiting the first time.

Also, make sure that you delete the previous partnership in ActiveSync as upgrading the ROM counts as having a new phone in its settings, even though the phone has the same name.

[efjay]

Had an error message saying "Notification error, cannot execute repllog.exe" and checked the notification queue, it is showing duplicates of repllog.exe. Cleared them with Scarybear Check Notifications but they are building up again.

[wynntrinh]

As a few people have mentioned it, I would just like to add that the very first time you sync this device with a Microsoft Exchange Server after updating to 1.4 the ActiveSync will appear to connect but not do anything. All you need to is go into the Kitchen and make your self a cup of coffee, watch a few minutes TV and suddenly everything will be on there. Just the first time takes a very long time for some reason, and after that it's fine.
*DO NOT RESET* while you are waiting the first time.


I had the sync running for nearly 30 minutes and still nothing. Not sure what you mean by a "long time" but 30 minutes is extremely long if you ask me. The other thing i notice is when I set the device into my cradle another LAN icon popped up and connected to what I have no idea. i checked the settings and it is set for USB. so i am "syncing" it now again and will see if it will take this time around. thanks for the help.

[Percz]

I had the sync running for nearly 30 minutes and still nothing. Not sure what you mean by a "long time" but 30 minutes is extremely long if you ask me. The other thing i notice is when I set the device into my cradle another LAN icon popped up and connected to what I have no idea. i checked the settings and it is set for USB. so i am "syncing" it now again and will see if it will take this time around. thanks for the help.

Ok well 30 minutes is a bit long. Tried opening up ActivSync and checking if there are any error messages? Failing that, disable all the Sync's (email, contacts, etc) and then try syncing and then add them back one by one and see if it's one of the options. Worth a try.

The LAN thing just seems to be a WM5 thing, I'm sure others can explain it better then I can, but it's just a interface between your PDA and your PC that allows your PDA to access your local area network for accesing the internet (if you want to browse on your PDA for some strange reason) and also for doing a Sync to a exchange server without using wireless or GPRS. It's also quite handy for using the Microsoft remote device plugin.
I don't consider it a security risk in the slightest, and it's protected by the same firewall and anti-virus your laptop has.

[Rogero]

Hello, first of all Thx Tuatara for all ur time and effort..it really worth it :)
I was trying the rom for a while and it seems good enough, except minor bugs: Picture viewer, I found out that Vbar sometimes is reporting some programs to be running like the phone or activesync while these programs are not actually running,U can check this using "Running Programs" instead ! so I have removed Vbar from startup for now.
As for ActiveSync,for the first time synchronizing u should simply press "Stop" then try again and it will work fine.

Cheers..
Rogero

[Tuatara]

tuatara, i have to the button lock, on my device.( yes i put no/yes/yes to hard reset after install)

Ok .. this can't be right - it should NOT be there at all. Does ANYONE else have the Button Lock control panel in the BUTTONS settings?

1- the program pictures and videos its no running :(
2- bt
3- after use the phone, everytime i use a nother program and close, the phone apears and close , apears and close some times 4 times :)

#1 & #2 are known. #1 will be solved sometime soon, and #2/BT is impossible as of yet.

#3 though now appears to be an incompatibility with vBar. It is possible that vBar (which was a last & limited testing time addition) is the cause of a lot of problems.

*** RECOMMENDATION *** - Disable vBar for now until we/I can figure out where the source of the problems is coming from. They are all too RANDOM which points to something 'common' across all applications. Something like vBar which could be disrupting the processes somehow.

tuatara, can i install the album in this version? i prefere album, becouse im pictures, it show the "exif" off the foto and histogram

I believe so ... there shouldn't be anything which limits what you can install - other than software which was written PRIOR to this OS (i.e. don't try to install things made before 2004), or things which are for 2003SE only. That also includes many lanugage packs or CUSTOM language packs which were made for different devices. Maybe they will work, maybe not. Your mileage will vary.

Remember too ... this ROM is still functionally MORE A WIZARD ROM than it is a HIMALAYA. I'm working on getting more of the Himalaya AKU2 into this, but it is a slow process.

this version it is very stabel, i am used for long time just open use and close programs, and some times the ba slow it down, but not crash, and this is very good, :) thanks
like you i prefere stability, that speed :)

Well ... it is geared for long-term performance/reliability/etc. not "out of the box raw speed" (until things get full). Although, I'm beginning to doubt the stabillity and question it.

Maybe there really are GREMLINS in the machine.

[Tuatara]

I flash to this great new rom and i was quite of an impression until i install one program (memory pocket navigator) and it doesn't run at all. I had the same problem with v1.3.

Unfortunately then I have to say it's an incomaptibility with the Wizard ROM somehow. There is then little I can do - if it didn't work on v1.3, then it probably still won't on v1.4.

This is an aplication that i really need, so i'm very sorry but i have to downgrade until this problem is solved. Holpefully very soon.

If I knew more about what the problem is other than "does not run" ... maybe I could figure out more. Is it out of RAM, Temp Space, problems creating files, directory missing, registry incompatibilty, ???

I must say that i experience memory pocket navigator with others wm5 rom's and did work very well.

If you can let me know which ROM works, I can have a look at the differences and if you provide a bit more details as to the nature of the failure, then I might be able to figure out the reason.

I think i'm writing for all when i say great job you are doing.

Thanks a lot.

Cheers - although I think this is beginning to "eat" up all available free time. *sigh*

[Tuatara]

I had the sync running for nearly 30 minutes and still nothing. Not sure what you mean by a "long time" but 30 minutes is extremely long if you ask me. The other thing i notice is when I set the device into my cradle another LAN icon popped up and connected to what I have no idea. i checked the settings and it is set for USB. so i am "syncing" it now again and will see if it will take this time around. thanks for the help.

Ok well 30 minutes is a bit long. Tried opening up ActivSync and checking if there are any error messages? Failing that, disable all the Sync's (email, contacts, etc) and then try syncing and then add them back one by one and see if it's one of the options. Worth a try.

The LAN thing just seems to be a WM5 thing, I'm sure others can explain it better then I can, but it's just a interface between your PDA and your PC that allows your PDA to access your local area network for accesing the internet (if you want to browse on your PDA for some strange reason) and also for doing a Sync to a exchange server without using wireless or GPRS. It's also quite handy for using the Microsoft remote device plugin.
I don't consider it a security risk in the slightest, and it's protected by the same firewall and anti-virus your laptop has.

ActiveSync now works over TCPIP, and it creates a network connection to your PDA over USB. This is the same priciple as using TCPIP over Ethernet, Firewire, WiFi, Bluetooth, USB, or a Parallel Port! TCPIP is the communications protocol which is sitting on top of a physical medium of transfer - in this case the wires (or wireless!) methods of connecting your devices.

With the advent of firewalls, which CONTROL TCPIP traffic, you now MUST LET ACTIVESYNC through your firewall - otherwise you will NEVER sync.

Check out the plethora of threads on this site, just about this subject. :-)

[alijo]

Hi, is it possible make a cab to disable vbar, i have the 4/5 times that phone flashes issue too. I used magic button on TuMa V1.3 and it worked fine.

Great Job Thanks

[sgrbhtngr]

Right now I am using TuMa v1.3. The MAIN reason why I took the plunge to go to TuMa1.3 from WM 2003SE is to be able to use voice command over the BT headset. After a few tweaks, it is working for me.

Now, is it true that this is possible only on the MS bluetooth stack (in TuMa v1.3) and NOT on the Widcomm stack (on Ivan)?

Tuatara- we really apprecaite your work. It might be asking too much but is it possible for you to have MS Voice Command in the Rom next time? It is a real memory-eater and having it in the ROM will help us all.

Again, keep up the GREAT work. We are all indebted to your genius! :)

Sagar

[wynntrinh]

I had the sync running for nearly 30 minutes and still nothing. Not sure what you mean by a "long time" but 30 minutes is extremely long if you ask me. The other thing i notice is when I set the device into my cradle another LAN icon popped up and connected to what I have no idea. i checked the settings and it is set for USB. so i am "syncing" it now again and will see if it will take this time around. thanks for the help.

Ok well 30 minutes is a bit long. Tried opening up ActivSync and checking if there are any error messages? Failing that, disable all the Sync's (email, contacts, etc) and then try syncing and then add them back one by one and see if it's one of the options. Worth a try.

The LAN thing just seems to be a WM5 thing, I'm sure others can explain it better then I can, but it's just a interface between your PDA and your PC that allows your PDA to access your local area network for accesing the internet (if you want to browse on your PDA for some strange reason) and also for doing a Sync to a exchange server without using wireless or GPRS. It's also quite handy for using the Microsoft remote device plugin.
I don't consider it a security risk in the slightest, and it's protected by the same firewall and anti-virus your laptop has.

ActiveSync now works over TCPIP, and it creates a network connection to your PDA over USB. This is the same priciple as using TCPIP over Ethernet, Firewire, WiFi, Bluetooth, USB, or a Parallel Port! TCPIP is the communications protocol which is sitting on top of a physical medium of transfer - in this case the wires (or wireless!) methods of connecting your devices.

With the advent of firewalls, which CONTROL TCPIP traffic, you now MUST LET ACTIVESYNC through your firewall - otherwise you will NEVER sync.

Check out the plethora of threads on this site, just about this subject. :-)

Update: i fiddled with the firewall a bit and it all works now. Thanks for the help!

[indra9110]

oke what about BA as modem for pc .... stil not work ????

[efjay]

Tuatara- we really apprecaite your work. It might be asking too much but is it possible for you to have MS Voice Command in the Rom next time? It is a real memory-eater and having it in the ROM will help us all.

Again, keep up the GREAT work. We are all indebted to your genius! :)

Sagar

MS Voice Command is commercial software and cant be included in the rom. You have to purchase it yourself.

[mpman2k]

@ Tuatara

Thx for the release of TuMa v1.4

I can finally use my motorola HT820 headphones with AD2P and all buttons working. Sound is good and I can also hear ring tone and answer with no problem. I never find out how to change ringtone yet.
I had notice that after paring and connect with my BT headset, my BA wont turn off the screen while listening to mp3s. I had try using WMP10 or TCPMP and your Display Switch program but none of them can shut off the screen. When I try all those programs, the screen turns off for half a second and turns back on again. However, I had also try Ivan's v4R1 rom with same problem.

One more thing that I cannot backup data on your rom using Sprite Backup. It installs and runs OK but when I try to backup or restore data. My BA restarts and Sprite Backup didn't do anything. Since there is no xBackup in WM5, I cannot backup or restore data on TuMa 1.4.

[KTamas]

Okay, let me clarify this for those who are having problems with sprite backup and similar softwares.

DO NOT USE ANY BACKUP SOFTWARES WHEN UPGRADING ROMS (SPRITE BACKUP, SPB BACKUP etc.)

...and if you have to, backup only your PIM data (Appointments, Tasks, Contacts, Notes). These softwares backups and restores registry, and that is a disaster because you are mixing an older ROM's registry with a newer ROMs files and that is anything but right. So if you upgrade your ROM, you must re-install your software manually.

[TheLastOne]

Ok, so I got a day's testing out of it, and have a few things to add:

1) I definately think having an extra optional extrom cab to set the program shortcuts back to untouched form is a great idea.
2) The Startup manager program mentioned before would be a great addition.
3) Perhaps on top, it would be nice to make an app thats hides/shows programs that aren't windows integral (TC, vBar) at will. Kind of like an uninstall without actually removing anything but shortcuts and startup things ;).
4) I've also noticed the problem mentioned earlier with certain pictures not displaying in PIE. I think it had something to do with this that froze my PPC before, but I haven't been able to reproduce the freeze yet.
5) This one is more of a question: Where are you finding the space to add this 3rd party programs? Are you stripping out parts out of the OS, or is there already a little empty space?
6) I love BootLogo, but it doesn't seem to exit very cleanly (maybe due to the business of start up?)
7) Where did the EXTROM folder that was in 1.3 go? (I'm actually happy it's not showing up for me, I have it partitioned to have basically no space)

Oh, and I would suggest you leave Windows Media and the other uncategorizables out of folders altogether, like you did with PIE.

On the subject of naming icons, if you do want to keep the duplicate icons with different names, then I recommend you at least keep a common scheme. For example, in the Programs window you renamed the default File Explorer to Windows Explorer, leaving the Start Menu the default name, but or Windows Media, it was the start menu with the renamed one, and the Programs menu with the default.

[qureshi]

Installed new version….seem to be nice; Tautara u really deserve appreciation for so many efforts…..God bless U.
I was using different version of WM 2005 since the time its releasing on our forum, but every time downgrading to win 2003 just because of one reason only...that is to use Arabic software came preinstalled in original version. I am really fed up from this shuttle-cock. U seems to be great man. One thing if u can do for us just to extract arabizer version2.0 from Jasjar and let it enable to work on WM05. I think whole middle east and south Asian country will be really oblige to u...and pray for ur more success in future...thanking u in anticipation.

[xsi]

I flash to this great new rom and i was quite of an impression until i install one program (memory pocket navigator) and it doesn't run at all. I had the same problem with v1.3.

Unfortunately then I have to say it's an incomaptibility with the Wizard ROM somehow. There is then little I can do - if it didn't work on v1.3, then it probably still won't on v1.4.

It probably is. Bad luck for me :(

This is an aplication that i really need, so i'm very sorry but i have to downgrade until this problem is solved. Holpefully very soon.

If I knew more about what the problem is other than "does not run" ... maybe I could figure out more. Is it out of RAM, Temp Space, problems creating files, directory missing, registry incompatibilty, ???

I really don't know what the problem is. I tap the program icon after intall and there is no response from it.

I must say that i experience memory pocket navigator with others wm5 rom's and did work very well.

If you can let me know which ROM works, I can have a look at the differences and if you provide a bit more details as to the nature of the failure, then I might be able to figure out the reason.

Of course i can. Works in all old ROM for BA and in my Universal too.

I think i'm writing for all when i say great job you are doing.

Thanks a lot.

Cheers - although I think this is beginning to "eat" up all available free time. *sigh*

I understand this is not your life. You do it for the pleasure and i really am grateful.

I hope you can solve my problem. This is the best ROM i ever tryed.

again Thanks a lot

[Tuatara]

Installed new version….seem to be nice and Tutura u really deserve appreciation for so many efforts…..God bless U.

Thanks ... very appreciated all of the feedback. A bit more effort and testing, and we will get the right BA ROM together! And then we can be (finally) out of BETA!

... to use Arabic software ... if u can do for us just to extract arabizer version2.0 from Jasjar and let it enable to work on WM05.

If you could point me to a JasJar ROM (preferably pre-AKU2 for now) which has the Arabic Software you seek in it, I'm pretty certain I could extract it out, and make it an additional CAB installer for the BA ROM. Barring any VGA resource incompatibilities ... it should be possible.

[Tuatara]

Ok, so I got a day's testing out of it, and have a few things to add:

NOTE: I'd like to add a warning for the moment ... I believe vBar may be causing some problems, and there are two other issues I'm researching at the moment which could cause you to lose your PIM data. One has to do with PermDir() specifications in the file system (I removed them on suggestion for localization capabilities, but didn't research all issues). The Second has to do with UPX compressed elements in the ROM (to answer the questions as to 'how is he fitting in all this stuff' 8)). Remember - this is BETA, and thing can (and unfortunately will) go wrong.

1) I definately think having an extra optional extrom cab to set the program shortcuts back to untouched form is a great idea.
2) The Startup manager program mentioned before would be a great addition.
3) Perhaps on top, it would be nice to make an app thats hides/shows programs that aren't windows integral (TC, vBar) at will. Kind of like an uninstall without actually removing anything but shortcuts and startup things ;).

I think I'll attack all three of these points in a couple of EXTROM CABs. I'm seeing the 'error' of my ways (and stubbornness). My thoughts have been to make an 'out of the box' ROM ... when in fact the answer SHOULD be - make one which CAN work 'out of the box' ... but you just need a few registry entries and shortcuts to make it do EXACTLY what you want it to.

So ... hang on to your hats ... just like last time when 1.3 came out very quickly after 1.2 ... we probably will be seeing a 1.5 in very short order. :!:

4) I've also noticed the problem mentioned earlier with certain pictures not displaying in PIE. I think it had something to do with this that froze my PPC before, but I haven't been able to reproduce the freeze yet.

I think I'll try and update the wmpplayer and IE ocx components from the AKU2 Himalaya, and see where that gets me. This could solve those problems ... not sure though.

5) This one is more of a question: Where are you finding the space to add this 3rd party programs? Are you stripping out parts out of the OS, or is there already a little empty space?

Nothing has been removed, and more has been 'carefully' added. UPX was used to achieve better compression of some applications - but this now could be a source of problems. The only thing which was removed were the Intellipad Languages - which can easily be added in for those who need them (i.e. not WWE).

6) I love BootLogo, but it doesn't seem to exit very cleanly (maybe due to the business of start up?)

It necessarily 'quits' immediately after having written the bitmap image to the screen. It's then up to the OS (GWES) to repaint appropriately. It is a 'hack' ... but one which adds to the customization of the device.

7) Where did the EXTROM folder that was in 1.3 go? (I'm actually happy it's not showing up for me, I have it partitioned to have basically no space)

It's there but it's HIDDEN now. You can unhide it if you wish. There were too many problems with people trying to put things onto it, and/or to be able to specify an alternate storage location for their data.

Oh, and I would suggest you leave Windows Media and the other uncategorizables out of folders altogether, like you did with PIE.

Post-install CABs ... I think that should address it. :-)

On the subject of naming icons, if you do want to keep the duplicate icons with different names, then I recommend you at least keep a common scheme. For example, in the Programs window you renamed the default File Explorer to Windows Explorer, leaving the Start Menu the default name, but or Windows Media, it was the start menu with the renamed one, and the Programs menu with the default.[/quote]

[efjay]

Tuatara, nice work on the rom. Just had a full day with it and no problems (apart from those already reported). Browsing with PIE on the bus home was slightly faster; phone calls came in ok. I think the volume level of the rings is too loud though.

On the PIE images problem, it was working ok under 1.3, maybe that helps you narrow it down.

Nothing else to add apart from great work, and thanks to you and to Mamaich in the background.

[borjok536]

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.
Yesy, I encountered the same problem!!! I see alot of problems with this new ROM!!!I decided to go back to Ivan's v4 rom..

[borjok536]

that you can release a TuMa version with Widcomm BT Stack separately? ... I dont have issues on Widcomm BT stack with Ivan's ROM (though I dit not try the BT headset, coz I dont use it at all)...

Ivan has sent me the Widcomm Stack components, however I have not had the time/chance to make a Widcomm Stack Installer for TuMa and to test it. Also, I'd rather have Ivan's ROM properly evaluated and tested - especially for the BT Stack, so that we can 'trade notes' as it were, and build up better ROMs & support CABs for everyone.

first bug I've encountered:

Even with full charge (green LED), get Backup Battery low power alarm. Happens even when plugged in. specifically happened during last program install to device.
check to the power settings icon shows both main and backup batteries at 100%

Hmmm ... again, I've tried to be very aggressive in saving power on the device. I've changed the battery sampling time from every five seconds, to every 20 seconds. It's now possible that the application mistakingly (on startup?) reads a zero value since the battery poll has not as yet taken place. I'll either see if I can 'pre-charge' the result (registry value?), or maybe I'll need to put the battery poll time back to 5 seconds.

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.

Hmmm odd. I believe that KTamas has been using Wisbar Advance all the time on the TuMa v1.4 Beta. Although, there is an IMPORTANT POINT!


You WILL need to disable the vBar task bar in the ROM now if you install another task manager! vBar is based on WISBar, which uses the SAME hook/interface as Wisbar Advance! Disable the vBar one (through it's control panel), and I'm certain that Wisbar Advance will work flawlessly.

First of all I would like to say thanks for a great new version. I have not encountered any issues so far.

Cool ... well, there are some already. *sigh* ...

Only question: Where is the comm manager which allows me to enable push email

Well ... while this ROM is already making use of some AKU2 Himalaya ROM elements, it's still unable to use the FULL AKU2 support set - specifically the Push Email. In short ... I'm still working on it.

I'll try for a short while now, and see if I can sort out some of these initial bugs/issues.
With regards to Wisbar Advance, Yes the problem is there! You have no problems when you use the default themes, but when you try other themes, it doesnt work, some images dont appear.. The same with, when you applying new skin to your Resco Keyboard, it doesnt work!. This is a serious problem though............

[Tuatara]

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.
Yesy, I encountered the same problem!!! I see alot of problems with this new ROM!!!I decided to go back to Ivan's v4 rom..

TURN OFF vBAR USING THE CONTROL PANEL OR REMOVE THE SHORTCUT ... THIS TASK MANAGER IS USING THE SAME INTERFACE AS WISBAR ADVANCE AND THE TWO CAN NOT CO-EXIST

Thank you for your attention. ;-)

[borjok536]

[quote=laoshu]After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.
Yesy, I encountered the same problem!!! I see alot of problems with this new ROM!!!I decided to go back to Ivan's v4 rom..

TURN OFF vBAR USING THE CONTROL PANEL OR REMOVE THE SHORTCUT ... THIS TASK MANAGER IS USING THE SAME INTERFACE AS WISBAR ADVANCE AND THE TWO CAN NOT CO-EXIST

Thank you for your attention. ;-)[/quote
This will not solve the problem. Its not only on the wisbar advance. Like for example when you're on Pocket Artist, and open an image file to edit, when you browse a folder containing images, some images will appear, some are not.....

[laoshu]

I flashed to Ivan Ver 4 R1 today and checked compatibility with Wisbar Advance, but it seems the problem exists there as well. The default Theme is working, but as soon as I switch to my favourite Theme, the screen get's all messy.

Another thing i realized yesterday after I received an SMS and wanted to reply. The screen just turned white, no address bar, no topic, just plain white. This issue does not exist in the Ivan Rom.

[alexanderi]

Hello All,

I upgraded to this ROM, everything works fine and pretty smooth and perfect but keep receiving Backup Battery Low warning. In fact the battery is perfect. Is there away to disable this warning?

Thank you!

Alex

[KTamas]

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.
Yesy, I encountered the same problem!!! I see alot of problems with this new ROM!!!I decided to go back to Ivan's v4 rom..
Weird, I have the opposite, I'm running WA2 and it works well for me, wthout any issues...be sure to use the latest version, 2.6.0.2 beta!

[norbs888]

At first everything was ok. I synched using activesync, and i installed my usual programs.
I just went out for coffee and realized i couldnt get a GSM signal even after doing a few soft resets. And much to my dismay, i have lost all my PIM data. Putang ina!!! :x
I did a hard reset and got a GSM signal again. Im now synching and reinstalling programs again.


Im back again!
After installing Pocket Informant, i get the error "Cannot connect to Pocket Outlook database"
...oh, and I lost my GSM signal again.

[gothier]

formaly beeing a member of the "clean ROM" fraction, I now love the "out of the box" concept. The build in apps are well choosen.
Great work!!!

Has someone tryed the built in "Eval Calculator"? I am only getting "error" as a result.

The record button is hardwired to the voicedail app. I know there is a fix, but could this be removed out of the rom so you don´t need to run the fix after every reset?

thx

[IkeTurner]

first of all, thanks Tuatara far all of the hours put into bringing wm5 to BA. either i'm completely an idiot or i am having the worst luck. Just think the much anticipated 1.4 rom is available & i cannot get it to load baupgradeut starts and then magically model id error. how do i get around this? please help

[IkeTurner]

Sorry, forgot to state that i am currently using a cingular sx66. a step by step would be great! appreciate the help guys!

[ZaJules]

first of all, thanks Tuatara far all of the hours put into bringing wm5 to BA. either i'm completely an idiot or i am having the worst luck. Just think the much anticipated 1.4 rom is available & i cannot get it to load baupgradeut starts and then magically model id error. how do i get around this? please help

Hi I spent 2 days with this problem then this morning I removed my SD Card and everything worked 100%


Good Luck

PS All the usual thankyou's to the Brain Trust. You Know Who You Are :D

[borjok536]

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.
Yesy, I encountered the same problem!!! I see alot of problems with this new ROM!!!I decided to go back to Ivan's v4 rom..
Weird, I have the opposite, I'm running WA2 and it works well for me, wthout any issues...be sure to use the latest version, 2.6.0.2 beta!
Ktamas have you tried other skins with no problems? The problem we were refferring to was on skinning. The default skins worked, and there were other which worked good, but have you tried the Vista skin, there were other images that didnt appear. The same goes to Resco Keyboard skinning, all my skins dont work just the default.. I have not encountered this problem in TuMa v1.3.. Though this kind of problem appeared also in Ivans latest ROM (v4 r1). Is there a patch to get rid this problem? Thanks

[baniaczek]

Very tastefull ROM. Thanks again.

Issue:

I've got a problem connecting to internet via Activesync. It was not possible at all.
Solution:[HKEY_LOCAL_MACHINE\Comm\RndisFn1\Parms\T cpIp]
"EnableDHCP"=dword:00000001
"AutoCfg"=dword:00000001

T9:
Can anybody check, if attached T9 dictionaries are Ok?
If yes - could you include them in the future?

Pocket NotePad:
Two suggestions:
Consider to add tGetFile.dll (http://tillanosoft.com/ce/tgetfile.html). Pocket Notepad works better - menu File/Open and File/SaveAs
Consider to associate *.txt with notepad too.

Control Panel:
I think some shortcuts could be moved into \windows\StartMenu\Settings:New Menu
Battery Meter
Device Manager
Phone Pad Setup
Task Bar Setup
Reason: for example "New menu". After execution from softkeys "New menu" is added to "recent programs" list. Moving them into Settings directory [or playing with myCPL] should avoid this.

[b]StartMenu Manager:
Next release will be ready after weekend. I hope :)

Welcome.exe:
Does anybody know, what are the tasks performed by welcome.exe? There is ItsMe project (http://www.nah6.com/~itsme/cvs-xdadevtools/welcome/). May be worth of interesting?

Auto.exe:

Consider to use auto.exe from Wizards extended ROM. It runs automatically - doesn't ask for anything, just installs CABs listed in the config.txt. It's both PRO and CON.


Thanks again for your work.

[ZaJules]

Updated to 1.4 all seemed well

Installed Wisbar Advance (Latest Beta) ok
Installed Wisbar Desktop 1.0.0.5 ok
Installed PhoneAlarm 1.30.03 ok

Changed to my own Skin in Wisbar Desktop ok
Phonalarm Displays ok on wisbar desktop as per normal
Change skin of Phonealarm and only half the items appear?
Change back to normal skin ok
restart BA Wisbar Advance No wallpaper no PhoneAlarm
Icons not showing up
Restart BA with out Wisbar or PA
Contacts Crashes on open as does Calendar
Phone app wont open and signal display shows no network???
PShutdown app grays out screen but only a little dot appears where buttons should be?

Hard Reset (Options 2 and 3 to Yes)
All seems ok again

Will now reload same apps and see.

All these Apps worked 100% on Ivan(latest) and Tuma 1.3

Jules


EDIT TO ADD

After full reset all is fine
1st Program that I load is PhoneAlarm. Does Not Work.
only half the items load on screen

[ZaJules]

Ivan and Tuma seem to have sorted out the BT problems but not "together"

Ivan has the BT disconnect issue fixed on power down screen But none of my BT Audio devices work reliably.

Tuma, all my devices work 100% but the disconnect issue is a major pain.

The 2 of you should combine your current BT knowledge and we should have a perfect BA.


Jules

[qing84]

I dumped my O2xdaII because of the disappointment from WM5.0 (Both BA upgrade and O2 Atom) Bought a regular non pda phone until recently I picked up my PDA and got TuMa 1.3. Thanks for all the hard work!

So I've upgraded to 1.4 and it looks alot cleaner than 1.3.

I am encountering some issues:

- Backup battery critically low

- Cannot Synchronize (Activesync message Says: Sychronization cannot be completed sucessfully...) This is usually resolved by hard resetting but the problem comes back very soon. It still happens when I don't install anything extra.

-Picture viewer won't load.

The first two issues are kinda very important for me to get it fixed before I am confident of using the device again. Any ideas?

Thanks!! :D

[ZaJules]

Seems to me the major problem with 1.4 has something to do with loading images.

As soon as a 3rd party AP tries to load other images it causes problems
as per my posts above.PhoneAlarm now works but only with the default skin (not the one that loads after installation but the skin called default)

[borjok536]

and the problem is that some of the images will appear some will not... strange.........

[KTamas]

At first everything was ok. I synched using activesync, and i installed my usual programs.
I just went out for coffee and realized i couldnt get a GSM signal even after doing a few soft resets. And much to my dismay, i have lost all my PIM data. Putang ina!!! :x
I did a hard reset and got a GSM signal again. Im now synching and reinstalling programs again.


Im back again!
After installing Pocket Informant, i get the error "Cannot connect to Pocket Outlook database"
...oh, and I lost my GSM signal again.
I have no problems with GSM signal but it is good to know I'm not the only one who got his PIM data wiped out. It may have to do something with UPX and it is currently being researched.

[IkeTurner]

IkeTurner wrote:
first of all, thanks Tuatara far all of the hours put into bringing wm5 to BA. either i'm completely an idiot or i am having the worst luck. Just think the much anticipated 1.4 rom is available & i cannot get it to load baupgradeut starts and then magically model id error. how do i get around this? please help

ZaJules Wrote:
Hi I spent 2 days with this problem then this morning I removed my SD Card and everything worked 100%

Still no luck after i removed my sim
any other ideas!!!! Tuatara any insight? (cing sx66 unlocked w/ t-mob sim)

[ibisit]

NICE...

all appears to be working fine from my end..
activesync works ok..
battery pack works ok..

Q. there appears to be 2 lines missing from the top of the screen...
or should i say they are not rendered right ... is this a known issue ??

i have an O2 XDA IIs..

also, what effect does not resizing the ROM have ??
i can't see the EXTROM folder to be able to store programs.. how can i tell what is free and what is not.. (as i uploaded one of the earlier 05 roms, then went back to 03SE)..

the only issue i have is that my ACT database will not sync.. however that is not an issue with this rom, it's an issue with the sync software not being compatable with wm2005

[KTamas]

After flashing from 1.3 to 1.4 I realized that this version has some serious issues with Wisbar Advance. Actually, even just trying to change the today theme seems to be impossible now. I am using the latest WA version 2.6 and have tried with three different themes.
Yesy, I encountered the same problem!!! I see alot of problems with this new ROM!!!I decided to go back to Ivan's v4 rom..
Weird, I have the opposite, I'm running WA2 and it works well for me, wthout any issues...be sure to use the latest version, 2.6.0.2 beta!
Ktamas have you tried other skins with no problems? The problem we were refferring to was on skinning. The default skins worked, and there were other which worked good, but have you tried the Vista skin, there were other images that didnt appear. The same goes to Resco Keyboard skinning, all my skins dont work just the default.. I have not encountered this problem in TuMa v1.3.. Though this kind of problem appeared also in Ivans latest ROM (v4 r1). Is there a patch to get rid this problem? Thanks
I'm using Juni's SBSHDeluxe suite and it works well, I've also tried switching to other themes (merlin, the one that looks like WM2003SE) and it worked well.

[PoW3r]

Hi people, thanks for the realease Tuma 1.4
I have noticed do not work that program: Record e Pictures & Video.
Sorry for my english e thanks for all!

[jamex]

hey guys

here just find 3 problems in TuMa1.4

1.when i close all programs by vbar, the "phone" will flash about 4 times,

2. the wmplayer is still spending ram till playing music

3.when i sync with my desktop, it say my name was repeat, and force rename

somebody have the same problems on it

3. Unplug your BA, Open up ActivSync on your computer, "File -> Delete Mobile Device" I had the same thing but it's just because you are using the same name as your old ROM. You'll have to setup the sync options again but it won't take long.

1. Just to add, it only seems to happen once you open the phone. Something simular happens if you open up ActivSynv on the PDA, I guess because this is something blocking these aplications from being closed?

2. Too technical for me

hi Percz

thanks for your kindly answer
but you don't have the "2" problem??
it seems happen inTuMa1.3 also

and when i sync with my desktop, it not the first time, it's everytime let me rename, i really don't know what happen!!!

[Madog ap Rhys]

At first everything was ok. I synched using activesync, and i installed my usual programs.
I just went out for coffee and realized i couldnt get a GSM signal even after doing a few soft resets. And much to my dismay, i have lost all my PIM data. Putang ina!!! :x
I did a hard reset and got a GSM signal again. Im now synching and reinstalling programs again.

I'v got the same problem!! Contacts and calendar don't work, some lines from today screen disappear, after hard reset it's ok....

[KTamas]

At first everything was ok. I synched using activesync, and i installed my usual programs.
I just went out for coffee and realized i couldnt get a GSM signal even after doing a few soft resets. And much to my dismay, i have lost all my PIM data. Putang ina!!! :x
I did a hard reset and got a GSM signal again. Im now synching and reinstalling programs again.
I'v got the same problem!! Contacts and calendar don't work, some lines from today screen disappear, after hard reset it's Ok....
Known issue. Fix is being researched.

[ZaJules]

IkeTurner wrote:
first of all, thanks Tuatara far all of the hours put into bringing wm5 to BA. either i'm completely an idiot or i am having the worst luck. Just think the much anticipated 1.4 rom is available & i cannot get it to load baupgradeut starts and then magically model id error. how do i get around this? please help

ZaJules Wrote:
Hi I spent 2 days with this problem then this morning I removed my SD Card and everything worked 100%

Still no luck after i removed my sim
any other ideas!!!! Tuatara any insight? (cing sx66 unlocked w/ t-mob sim)


Not the Sim the SD Memory card that worked for me.

[khalilio]

Gr8 work Tuma, can't wait till the full release is out.
I am using Tuma 1.4 beta, on a PDA2K (Blue Angel), I faced the following issues with this beta release.
-No GSM signal after few hours of no activities.
-My contacts and tasks dissapeared too!
-The internet Explorer stopped showing animated GIF pictures (It was working fine with ver. 1.3)
-The phone button did not work after the signal dissapeared, I don't know if it is related to the GSM signal or not, but I failed to get the keypad even after a soft reset.
I hope these issues will be addressed in the next release, once again thanks for your time and hardwork.

[Snow_Elf]

Please, please can you help with this one Tuatara. I am another big fan of your ROMs and have been checking waiting for this next release.

The ONLY issue I have with 1.3 (and will have with 1.4 as well by the sounds of it) is this programme, which I am desperate to use as well but stopped working when I upgraded last time to 1.3. It has worked fine with every other ROM upgrade I have done previous to this one and I have tried installing it into TEMP/storage card/device etc.

I also have a log raised about this on their support forum (http://www.memory-map.co.uk/board/index.php?showtopic=3782) and they think it may be the regional/date settings...?

Specifically, when you select the icon from programms or from the exe file in file explore then nothing happens... at all... it is just like you never selected it! It will also fail to uninstall properly I have found.

Please please help!

A Fan!

EDIT: Forgot to say that I am using an XDAIIs


I flash to this great new rom and i was quite of an impression until i install one program (memory pocket navigator) and it doesn't run at all. I had the same problem with v1.3.

Unfortunately then I have to say it's an incomaptibility with the Wizard ROM somehow. There is then little I can do - if it didn't work on v1.3, then it probably still won't on v1.4.

This is an aplication that i really need, so i'm very sorry but i have to downgrade until this problem is solved. Holpefully very soon.

If I knew more about what the problem is other than "does not run" ... maybe I could figure out more. Is it out of RAM, Temp Space, problems creating files, directory missing, registry incompatibilty, ???

I must say that i experience memory pocket navigator with others wm5 rom's and did work very well.

If you can let me know which ROM works, I can have a look at the differences and if you provide a bit more details as to the nature of the failure, then I might be able to figure out the reason.

I think i'm writing for all when i say great job you are doing.

Thanks a lot.

Cheers - although I think this is beginning to "eat" up all available free time. *sigh*

[Tuatara]

Please, please can you help with this one Tuatara. I am another big fan of your ROMs and have been checking waiting for this next release.

The ONLY issue I have with 1.3 (and will have with 1.4 as well by the sounds of it) is this programme, which I am desperate to use as well but stopped working when I upgraded last time to 1.3. It has worked fine with every other ROM upgrade I have done previous to this one and I have tried installing it into TEMP/storage card/device etc.

I also have a log raised about this on their support forum (http://www.memory-map.co.uk/board/index.php?showtopic=3782) and they think it may be the regional/date settings...?

Specifically, when you select the icon from programms or from the exe file in file explore then nothing happens... at all... it is just like you never selected it! It will also fail to uninstall properly I have found.

Please please help!

A Fan!

Well ... I've read the topic, and all I can say is that YES, I have changed the Date/Time/Region settings in the ROM.

But it would be easy to set these back to defaults.

Start -> Settings -> System -> Regional Settings

Region Tab
- Choose "English (United States)"

Time Tab
- Choose "h:mm:ss tt", ":", "AM", "PM"

Date Tab
- Choose "M/d/yy", "/", "dddd, MMMM dd, yyyy"

That should now be entirely the default settings ... as long as on Hard Reset, when doing the Cut/Paste thing, you chose a US based Time Zone, I think that would be everything.

I hope this works/helps.

[PoW3r]

Why doesn't work Record e Pictures&video?

[xsi]

Please, please can you help with this one Tuatara. I am another big fan of your ROMs and have been checking waiting for this next release.

The ONLY issue I have with 1.3 (and will have with 1.4 as well by the sounds of it) is this programme, which I am desperate to use as well but stopped working when I upgraded last time to 1.3. It has worked fine with every other ROM upgrade I have done previous to this one and I have tried installing it into TEMP/storage card/device etc.

I also have a log raised about this on their support forum (http://www.memory-map.co.uk/board/index.php?showtopic=3782) and they think it may be the regional/date settings...?

Specifically, when you select the icon from programms or from the exe file in file explore then nothing happens... at all... it is just like you never selected it! It will also fail to uninstall properly I have found.

Please please help!

A Fan!

Well ... I've read the topic, and all I can say is that YES, I have changed the Date/Time/Region settings in the ROM.

But it would be easy to set these back to defaults.

Start -> Settings -> System -> Regional Settings

Region Tab
- Choose "English (United States)"

Time Tab
- Choose "h:mm:ss tt", ":", "AM", "PM"

Date Tab
- Choose "M/d/yy", "/", "dddd, MMMM dd, yyyy"

That should now be entirely the default settings ... as long as on Hard Reset, when doing the Cut/Paste thing, you chose a US based Time Zone, I think that would be everything.

I hope this works/helps.


Didn't work...

I did everything just like you told, however didn't solve the problem. :cry:

[Snow_Elf]

I have tried hard resetting with:
US time zone and setting region to US
UK time zone and setting region to UK

unfortunately neither worked :-(

Pleeeease help!

[taxist]

Tuatara

On all yours ROMs there is an error:
Frequently after soft reset are lost User name and Password in settings of GPRS connection .
In ROMs by Ivan all is normal.
Why?

[qing84]

Anyone knows how I can fix the "Synchronization cannot be completed sucessfully. Reconnect your device and try again..." ??? I can't get the unit to sync anymore but it can be connected (to transfer files etc.)

Thanks!!

[Real Ism]

Does this work on a Universal?

This is a custom ROM and i was looking for soem playable options ...

Or this a Angel only??

[Tuatara]

Very tastefull ROM. Thanks again.

And I have to thank you again for your excellent debugging/detective work (previously the Camera Bug in v1.3).

Also, another thank you for pursuing and developing the Startup Manager application! I have NO idea how I'd missed seeing your post in the forums. Maybe next time PM me, just to make sure I have my eyes open, and am not asleep or blinded by ROMs. ;-)

I presume therefore I have your permission to include this in the next ROM? :D

Anyways ... on to the good stuff!

Issue:

I've got a problem connecting to internet via Activesync. It was not possible at all.
Solution:[HKEY_LOCAL_MACHINE\Comm\RndisFn1\Parms\T cpIp]
"EnableDHCP"=dword:00000001
"AutoCfg"=dword:00000001

Ok ... this is odd. These settings have not changed since the Original Wizard Port, Tuma v1.3, and now v1.4. Very strange. I will apply the settings and see if/what changes they make. Cheers.

T9:
Can anybody check, if attached T9 dictionaries are Ok?
If yes - could you include them in the future?

Yes captain, my captain ... I will check right now to make sure they can be included. YES! They work! I've also added a few of my own. 8)

Languages which will soon be supported:
- Czech
- Danish
- Dutch
- English
- Finnish
- French
- German
- Hungarian
- Italian
- Norwegian
- Polish
- Portuguese
- Romanian
- Russian (* Yes, this one too, thanks to ValeraVi and mamaich)
- Slovak
- Spanish
- Swedish
- Turkish

Coming soon in the next updated EXTROM ... I just have to decide on the best method of installation to support everyone. At present I have ALL languages supported cleanly, although for Russian there exists new T9 Artwork which could be used instead. Could this artwork possibly be created as .mui files?

Pocket NotePad:
Two suggestions:
Consider to add tGetFile.dll (http://tillanosoft.com/ce/tgetfile.html). Pocket Notepad works better - menu File/Open and File/SaveAs
Consider to associate *.txt with notepad too.

Done and done. However, since tGetFile is NOT a DISTRIBUTABLE file, but it is a COPY-able file, I can only include this in the ROM by including the Copyright Notice with the ROM.

In fact, to address this very issue, I've just gone through everything added to the ROM and realized that I should include appropriate notices, licences or copyrights for everything which has been added.

It took a while, but I've done this now, and a licences.txt file will be included with the ROM. All software now has been confirmed that it may be copied into the ROM under the appropriate licences as granted.

Control Panel:
I think some shortcuts could be moved into \windows\StartMenu\Settings:New Menu
Battery Meter
Device Manager
Phone Pad Setup
Task Bar Setup
Reason: for example "New menu". After execution from softkeys "New menu" is added to "recent programs" list. Moving them into Settings directory [or playing with myCPL] should avoid this.

I will sort things out using myCPL instead. This is a much more elegant solution, and can avoid a LOT of the clutter - especially for System Configuration Elements. All other "System" elements though should and will remain in the System folder so that they may be assigned to hard buttons as appropriate.

[b]StartMenu Manager:
Next release will be ready after weekend. I hope :)

Cool ... we'll see how quickly the 'next' version of the ROM comes together to address the bugs found.

Welcome.exe:
Does anybody know, what are the tasks performed by welcome.exe? There is ItsMe project (http://www.nah6.com/~itsme/cvs-xdadevtools/welcome/). May be worth of interesting?

It does a LOT of housekeeping on the first initialization ... not sure of everything it does, but there is enough that it's not warranted to delete it.

Auto.exe:
Consider to use auto.exe from Wizards extended ROM. It runs automatically - doesn't ask for anything, just installs CABs listed in the config.txt. It's both PRO and CON.

CON unfortunately. If you're using a SX66 and don't know/wish to edit the Config.txt file, then you have the easy option to NOT install the Camera just by clicking "Cancel".

Having said that, I could provide BOTH Autorun files in the distribution, and give people the choice as to which one they would like to use.

Thanks again for your work.

It's quickly becoming a mission! :D

[hexus0]

hey awesome work, havnt installed yet... gonna wait till the patches are up... Have a quick question.. the whole reason i havnt upgraded to M5 is because of these "bluetooth disconnect" issues...

from more research, correct me if im wrong i have narrowed these issues to the following occurances...

1) When in sync with a device, and the power button is hit or the screen goes black, BLUE TOOTH WILL DISSCONNECT.

2) Bluetooth is having trouble SYNCing with newer headset devices and working correctly...

Originally i was under the impression that BLUETOOTH didnt work at all. That it always disconnected. But if that is not true and I will still be able to SYNC with my GPS for use of TOMTOM 5 then i would be upgrading right now....

Can someone please clarify for me? thanks in advance.

[Midget_1990]

bluetooth works just fine, however it disconnects when you power off the phone.

[baniaczek]

Also, another thank you for pursuing and developing the Startup Manager application! I have NO idea how I'd missed seeing your post in the forums. Maybe next time PM me, just to make sure I have my eyes open, and am not asleep or blinded by ROMs. ;-)
Its only alpha version. I would PM two releases later :)

I presume therefore I have your permission to include this in the next ROM? :D
Sure.

It's quickly becoming a mission! :D
:)))))

Active sync issue - may be this can help - after inserting BA into the cradle i ve got a lot of times message [PC side] - [translated from polish]"Not recognized USB device". [PC: win2k3, active sync 4.1.0 release 4841]. This never happens with previous TuMa

[hexus0]

thanks midget. ill just wait for a few patches and ill upgrade! thanks

[efjay]

Here are screenshots of the repllog.exe error im getting

[MOHDWADEA]

Installed new version….seem to be nice and Tutura u really deserve appreciation for so many efforts…..God bless U.

Thanks ... very appreciated all of the feedback. A bit more effort and testing, and we will get the right BA ROM together! And then we can be (finally) out of BETA!

... to use Arabic software ... if u can do for us just to extract arabizer version2.0 from Jasjar and let it enable to work on WM05.

If you could point me to a JasJar ROM (preferably pre-AKU2 for now) which has the Arabic Software you seek in it, I'm pretty certain I could extract it out, and make it an additional CAB installer for the BA ROM. Barring any VGA resource incompatibilities ... it should be possible.

Tuatara,

I have some Arabizer arabic components working on my blue angel using your rom...although it is not version 2 it is extremly stable and compatable with all WM5 roms as well...let me know if you require the cabs

Regards,

Mohdwadea

[Tuatara]

Here are screenshots of the repllog.exe error im getting

Right ... I think I'd better "pull the plug" as they say on this ROM.

I don't believe I can quickly correct any of these issues with a CAB installer fix. The problem is unfortunately going a bit deeper than that.

The problems most likely stem from various sources:

Optimization features to improve speed (Data issues / PIM corruption)
Interaction of AKU2 elements with AKU0 (repllog.exe Errors / ActiveSync)
UPX compressed applications (Random 'odd' behaviour)
Filesystem Respecification (standard Directories instead of PermDirs)
Possible stability issues in vBar (Phone Application Restarting)
GWES subsystem / IE extensions (Images, Pictures & Video Failure)
Application resource allocation failures (Eval Calc Failing, & other failing installs)

I will be addressing these issues over the weekend. There WILL be a new ROM at the end of this time (called v1.5) which will be either one of two possible incarnations:

1). Returning to a prior Alpha Test version which proved VERY stable, but contained a lot less of the AKU2 elements from Himalaya (incl. updated BT for reliability *sigh*)
2). Moving even MORE of the Himalaya AKU2 ROM into the current Beta (and correcting the other issues) so as to have as few as possible AKU0 elements coexisting.

Until that time I STRONGLY recommend that everyone not use this ROM - except for further BETA testing and/or bug reporting.

My sincere apologies for the troubles you've encountered so far ... however it has been INVALUABLE with all the feedback, and I will be addressing as many of the issues found as quickly as possible.

I'll now be updating the first post with this content as well, and also a 'BUG LIST' so that everyone knows.

Cheers!

[indra9110]

Hai Tuatara... very nice work....
what about USB modem ??? I really need this functions....


Tuatara Work for us

http://img365.imageshack.us/img365/816/o2hardcore4qv2th.gif

[Tuatara]

Hai Tuatara... very nice work....
what about USB modem ??? I really need this functions....

I'd like to have this 100% working as well. It's strange, since Serial, BlueTooth, and Irda all seem to work ... it can't be the manager or the service itself. Needs some more research ...

http://img365.imageshack.us/img365/816/o2hardcore4qv2th.gif
Heh ... It's beginning to feel like this ...

[efjay]

My sincere apologies for the troubles you've encountered so far ... Cheers!

Tuatara, no need to apologise. Your hard work is really appreciated by all of us. Thanks again.

[qing84]

No need to apologize! We are all here to support you.

How about a cleaner ROM that gives most of the basic functions with good battery and speeds?

We can get alot of the extras on the device after that.

Thanks for all the hard work!

[baniaczek]

Until that time I STRONGLY recommend that everyone not use this ROMOk, I'm back.My sincere apologies for the troubles you've encountered so farReally - no need. I like this sport. I don't have enough time to make such deep reengineering, but I can support you. Its my pleasure.

[bolopez]

My sincere apologies for the troubles you've encountered so far ...

Apologies??? You, who is working for us all just for the fun of it? Please Tatuara, forgive us for being so impatient. And a big THANK YOU VERY MUCH for your time and your work.

[Phreakazoidz]

Thanks ... so much tuatara....


Great Job....


:twisted: :idea:

[edgariu]

I can't add pictures to my contacts...

Thanks tuatara for your work.

[baniaczek]

I've got a problem connecting to internet via Activesync. It was not possible at all.
Solution:[HKEY_LOCAL_MACHINE\Comm\RndisFn1\Parms\T cpIp]
"EnableDHCP"=dword:00000001
"AutoCfg"=dword:00000001

Doesn't work with TuMa 1.3 :-o

[farehmani]

This is with great regret for all TuMa lovers, i upgraded my Xda IIs with newly released TuMa 1.4 WM5 ROM and was surprised to get this lowest speed and responsiveness on my device.

there are several other issues that pissed me off;

1, Slow responsivenes of the entire system
2, screen flickering constntly while switching between applications
3, Phones starts vibrating and ringing in call waiting. this doesn't stops untill a soft reset.
4, the biggest flaw, NO CAMERA APPLICATION - (What a skip....huh!!)

Please help me guys, i want to revert back to my O2 officially relaeased WM2003 ROM 1.40.00. How can i do that now?

Tautara! don't take this feedback for worst as i tried to help you out in making it further better.

Peace out buddy.

Farhaan.

Guys, don't forget to guide me in downgrading my Xda IIs to previous rom.

[qureshi]

Can anyone else also experiencing same problem which I am that after installing Tautara version 1.4, agile messenger is not working while it was quite good on version TuMa1.3. Now I installed old earlier version which I used to use in win2003se with ROM 1.2 ….MSN having same problem…as in versions 1.3. Can we do something else to have MSN and Yahoo messenger on TuMa 1.4 WM05 ROM.?

More over it’s really heart breaking that Tautara u r doing all this efforts u r asking 4 apologies.....we are really appreciating ur efforts....we R all with U...

[kennyen]

Great Works Developers,

I encountered below issue,

1.) Can not start Minesweeper game. i like the TuMa games very much. can let me fully utilize my waiting time...

2.) No GSM signal after restore "pim.vol" file a few hours. I always backup contact/calls history database by copy /device/pim.vol to SD card then restore it after format storage. i can't even start "Phone" after a few hours of restoration.

Regards,

[qureshi]

[quote]Tuatara,

I have some Arabizer arabic components working on my blue angel using your rom...although it is not version 2 it is extremly stable and compatable with all WM5 roms as well...let me know if you require the cabs

Regards,

Mohdwadea

Salam MohadWadea, can u plese let us know how we can get this arabizer, is this the same as "united arabic Cab arbizer"or something different....and what about prayer timings and hijri calnder can be installl on it....thanks in advance

[baniaczek]

2.) No GSM signal after restore "pim.vol" file a few hours. I always backup contact/calls history database by copy /device/pim.vol to SD card then restore it after format storage. i can't even start "Phone" after a few hours of restoration.
Me too. but without any problems.

[qing84]

You sure have done the installation inproperly.

The speed of this ROM is not the fastest but it is not very slow. You cannot compare 2003 and WM5 speeds because of the switch to use Flash ROM to store data.

The screen doesn't flicker for me.

Phone problem happens sometimes (rarely) but I don't it is just for this ROM.

You need to put the EXTROM files in your storage card to get the T9, MMS, Camera programs to install when you flash your device.

I have other issues with the ROM But yours are fixable.

Good Luck

This is with great regret for all TuMa lovers, i upgraded my Xda IIs with newly released TuMa 1.4 WM5 ROM and was surprised to get this lowest speed and responsiveness on my device.

there are several other issues that pissed me off;

1, Slow responsivenes of the entire system
2, screen flickering constntly while switching between applications
3, Phones starts vibrating and ringing in call waiting. this doesn't stops untill a soft reset.
4, the biggest flaw, NO CAMERA APPLICATION - (What a skip....huh!!)

Please help me guys, i want to revert back to my O2 officially relaeased WM2003 ROM 1.40.00. How can i do that now?

Tautara! don't take this feedback for worst as i tried to help you out in making it further better.

Peace out buddy.

Farhaan.

Guys, don't forget to guide me in downgrading my Xda IIs to previous rom.

[qing84]

Can anyone else also experiencing same problem which I am that after installing Tautara version 1.4, agile messenger is not working while it was quite good on version TuMa1.3. Now I installed old earlier version which I used to use in win2003se with ROM 1.2 ….MSN having same problem…as in versions 1.3. Can we do something else to have MSN and Yahoo messenger on TuMa 1.4 WM05 ROM.?

More over it’s really heart breaking that Tautara u r doing all this efforts u r asking 4 apologies.....we are really appreciating ur efforts....we R all with U...

I've tried the newest version of the agile messenger. It crashes after the splashscreen. Wondering why this is happening.

[sinensis]

@Tuatara

How much work is it to replace the MS stack with Widcomm? Is this something that could be done with a cab?

[MOHDWADEA]

[quote]Tuatara,

I have some Arabizer arabic components working on my blue angel using your rom...although it is not version 2 it is extremly stable and compatable with all WM5 roms as well...let me know if you require the cabs

Regards,

Mohdwadea

Salam MohadWadea, can u plese let us know how we can get this arabizer, is this the same as "united arabic Cab arbizer"or something different....and what about prayer timings and hijri calnder can be installl on it....thanks in advance

To an`yone who wants the Arabizer cabs. I will post the freeware cabs. However I have some additional cabs but they is large 8 mb which i install on my storage card. Can not uplooad on the server..times out due to the size...this is for prayer times quran hijri calender and so on...if someone has an idea of how i can uplaod please suggest.

[efjay]

Guys, please look again at the first post in this thread. This rom is not recommened, only for testing. Tuatara is working on 1.5 which should fix the known bugs so lets be patient and wait for the release.

[merps]

@Tuatara

Mate - I cannot say how much I appreciate you doing what the manufacture cannot. Just someone else giving another vote of thanks for all the work you have done to date. I look forward to version 1.5 of TuMa.

Again, thanks for everything and thanks in advance for all the work you wish to do.

[Tuatara]

@Tuatara

How much work is it to replace the MS stack with Widcomm? Is this something that could be done with a cab?

In theory ... well ... yes. I'm having an in-depth look at what Ivan and Midget have done with the Widcomm stack. They have been working with a number of versions now - one which I worked on extracting from the Acer ROM, and a later stack coming from an extract of the Dell X50/51 (I believe).

I will see what can be done w.r.t. the Widcomm stack as a CAB installer, but my predominant focus will still be on the Microsoft stack remaining in the ROM. I'm doing this for two reasons:

1). The Microsoft stack appears to have a much greater compatibility and reliability aspect to it. The only 'failure' we have on the BA is a failure to stay on when the device turns off.

2). The integration of the Widcomm stack has been frought with problems - primarily for headset operation. This is in my estimation the most useful profile of the device! Additionally conatcts, SIM Card, and handsfree profiles (carkit) have all had a number of comminications and configuration issues.

Since the Widcomm stack stays on now, there MUST be the correct configuration bitstream somewhere in there which is setting up the BT chipset properly. It may be possible to extract this, and insert/inject this into the Microsoft driver/initialization - thereby eliminating the problems.

But this is just a guess - and with v1.5 needing to be a stable ROM first and foremost - I'm focussing on that for now.

[Tuatara]

@Tuatara

Mate - I cannot say how much I appreciate you doing what the manufacture cannot. Just someone else giving another vote of thanks for all the work you have done to date. I look forward to version 1.5 of TuMa.

Again, thanks for everything and thanks in advance for all the work you wish to do.

Thanks ... as always, feedback and debugging of issues is MUCH appreciated! I can't possibly test every configuration, so ... unforutnately I have to leave it up to "you" for a lot of it. Maybe ... one day ... we can make a ROM and not call it "Alpha" or "Beta" ... maybe "Gamma" ... or "Omega?" ;-)

Anyways ... it's not entirely true, that we're doing what the manufacturers can not ... it's more that the manufacturers are focussed on 'newer' products, and are not going to try and upgrade or re-address older products. While the BA and other older devices are equivalently powerful and as functionality complete as any new device they are releasing, they just can not justify development on an old platform.

Part of this reason is cost, and the other is unfortunately 'intelligence'. How many 'generic' users out there do you think would be able to successfully repartition, flash, upgrade, and then utilise their new ROM? Especially without a support forum like XDA-Dev?

Mike Calligaro wrote an EXCELLENT article on exactly this reason. I myself understand this perfectly well, and am in a similar business with similar issues and responsibilities. Unfortunately the future of all devices and development is in BETA. Time to market is short, and quite often you have to make the most of the short 'lead-time' you have.

http://blogs.msdn.com/windowsmobile/archive/2005/10/06/477999.aspx

Having said that ... I like my BA. It's far better than a number of the newer 'true' WM5 devices out there, and best of all ... I have the ability to FIX almost anything and everything that's wrong with it now. 8)

[hexus0]

@Tuatara

keep up the good work! Merps took the words out of my mouth. All i can say to differ from his comments would be... umm i duno its a bit early in the morning to start thinking about what im going to say. Cant wait for the 1.5

Thanks mate.

[merps]

@Tuatara

Mate - I cannot say how much I appreciate you doing what the manufacture cannot. Just someone else giving another vote of thanks for all the work you have done to date. I look forward to version 1.5 of TuMa.

Again, thanks for everything and thanks in advance for all the work you wish to do.

Thanks ... as always, feedback and debugging of issues is MUCH appreciated! I can't possibly test every configuration, so ... unforutnately I have to leave it up to "you" for a lot of it. Maybe ... one day ... we can make a ROM and not call it "Alpha" or "Beta" ... maybe "Gamma" ... or "Omega?" ;-)

Anyways ... it's not entirely true, that we're doing what the manufacturers can not ... it's more that the manufacturers are focussed on 'newer' products, and are not going to try and upgrade or re-address older products. While the BA and other older devices are equivalently powerful and as functionality complete as any new device they are releasing, they just can not justify development on an old platform.

Part of this reason is cost, and the other is unfortunately 'intelligence'. How many 'generic' users out there do you think would be able to successfully repartition, flash, upgrade, and then utilise their new ROM? Especially without a support forum like XDA-Dev?

Mike Calligaro wrote an EXCELLENT article on exactly this reason. I myself understand this perfectly well, and am in a similar business with similar issues and responsibilities. Unfortunately the future of all devices and development is in BETA. Time to market is short, and quite often you have to make the most of the short 'lead-time' you have.

http://blogs.msdn.com/windowsmobile/archive/2005/10/06/477999.aspx

Having said that ... I like my BA. It's far better than a number of the newer 'true' WM5 devices out there, and best of all ... I have the ability to FIX almost anything and everything that's wrong with it now. 8)


Thank you for the points mate like everything this can be argued for and against. I, on the other hand, argue against the manufactures suggesting that the product should have a life cycle longer then twelve months and upgrade paths should be incorporated into development of the product.

But we really don't live in a perfect world then do we? ;-)

This is the reason that, I personal along with many others no doubt, appreciate all the work you are doing. :D

[Percz]

Great to hear how well this ROM is progressing. v1.4 does have it's bugs, but it certainly proves an excellent "proof of concept" ROM if nothing else! The fact that you have managed to mix so many functions and bits of other ROMs and put them put them all into one package that still boots is amazing.

The thing that I think will really set this ROM alight is just the option to be able to "turn on" built in fuctions using a CAB. There is clearly an advantage to building programs into the ROM, but sometimes you just dont need them and it's a pain not being able to remove them.

I've been jumping between ROM's the last couple of weeks, but looking forward to v1.5, something tells me it will be on my phone for awhle - at least as long as it takes 1.6 to come out. :-p

[Snow_Elf]

Hi Tuatara,

I know you said that you would look into this programme for me (us) and asked what ROMs it worked on, well I have just flashed my XDAIIs with Ivan's latest and it works with that - hope that is some help...?

SnowElf

[Tuatara]

Hi Tuatara,

I know you said that you would look into this programme for me (us) and asked what ROMs it worked on, well I have just flashed my XDAIIs with Ivan's latest and it works with that - hope that is some help...?

SnowElf

I believe the problem has to do with memory map and how they've (improperly) written their handling of internationalization. They're well aware of the problems and will be fixing this in the future. Granted, they only make maps of the US (principally), but they should be supporting world-wide internationalization settings correctly. I've had to 'correct' one or two apps now for perfect compatibility with the TuMa ROMs, and to be honest - it's just laziness on the developer's parts. *sigh*

I think I will leave the v1.5 more 'US default' centric - just because of bad programming practice by a LOT of developers - even the commercial ones who should know better.

[Snow_Elf]

Tuatara,

Many thanks for this, and thank you for everything you are doing here for all of us BA users. You are truly great! If I can help you at all, just PM!

Snow_Elf

[Tuatara]

I've been working on TuMa v1.5 in two 'incantations' ...

1). Fixing the bugs in TuMa v1.4 - which is proving interesting, since the bugs are so ... well ... esoteric.
2). Trying to come closer to the real 'TuMa v2.0' with AKU2 support.

For this I've identified all of the locations which call into the new support functions in COREDLL.DLL. There are actually only 2 applications, but they are ... well ... 'core' elements of AKU2 functionality.

lap_pw.dll: [CR ] 2515 (0x09D3) 870 (0x0366) LASSGetValue
rapiclnt.exe: [CR ] 2516 (0x09D4) 1356 (0x054C) VerifyUserAsync
rapiclnt.exe: [CR ] 2517 (0x09D5) 869 (0x0365) LASSGetResult
rapiclnt.exe: [CR ] 2518 (0x09D6) 868 (0x0364) LASSClose

Outside of these two elements though, there is nothing which calls into the COREDLL.DLL XIP functions, not by name, or by number. So special support was added just for these two elements.

I'll have to keep working on it to see if I can 'get around' these issues to have an AKU2, or I'll focus on an AKU0 with Headset/Handsfree/A2DP profiles and just stability. I'll see where my energies lead me.

Anyways ... nothing as yet - talk more later.

[sunnyd24]

Hey all,

I've been following this thread for a while but haven't had time to flash v1.4, and I'm glad I've been busy as it seems to be troublesome to most of you out there!

Well thanks Tuatara & KTmas & all other beta testers.

I think I may wait for v1.5 :) release or maybe if we're lucky then v2.0 release!! 8)

Thanks again all,
Sunny

[greatbal]

I have been using the Tuma v1.3 for a month now, and notwithstanding the bugs it has, i still love it just the same. Thanks Tuatara! :)

I have been waiting for the release of Tuma v1.4, but wasn't able to find time to download it. And it seems that you (Tuatara) don't recommend this rom for all its problems.

I'll be waiting for v1.5, or hopefully v2.0 :)

Great working Tuatara. It must be taking much of your time. We BA users really appreciate that. Good luck on v2.0 :wink:

[bolopez]

I will see what can be done w.r.t. the Widcomm stack as a CAB installer, but my predominant focus will still be on the Microsoft stack remaining in the ROM. I'm doing this for two reasons:

1). The Microsoft stack appears to have a much greater compatibility and reliability aspect to it. The only 'failure' we have on the BA is a failure to stay on when the device turns off.

2). The integration of the Widcomm stack has been frought with problems - primarily for headset operation. This is in my estimation the most useful profile of the device! Additionally conatcts, SIM Card, and handsfree profiles (carkit) have all had a number of comminications and configuration issues.


Just to let you know. I've tried several ROMswith MS and WidComm stacks, and, at elast in my case, only the NS stack is able to recognize the services in my Siemens HKW600 BT hands free car kit. And it's strange, because the original ROM used Widcomm stack and could!!! I wasn't able to browse my contact list, but at least it worked. I have an Himalaya with MS stack and the contacts can be browsed and besides it can work with two devices, the handsfree and the GPS mouse simultaneously. I have not been able to reproduce this with BA, WM5 and any stack. Very strange.

On the other hand, my experience with TuMa 1.4 has been quite good. For me it's been the most reliable and fast WM5 ROM I've tried. I hope you can go on with 1.5 and solve the problems that have arised. Again, THANK YOU VERY MUCH for your work!!!

[Percz]

Any one curious as to what this alpha 1.5 is like? I wanna flash. :twisted:

[siemens_sx66]

Hi,
I installed this new 1.4 rom on my BA (SX66) (for testing only) and it seems much faster.

However I get an error
Handsfree.exe
The file 'Handsfree' cannot be opened. Either it is not signed with a trusted certificate, or one of it's components cannot be found. You might need to reinstall or restore this file.

Is there some way for me to work around this problem?
TIA!

[snapper245]

Guys, please look again at the first post in this thread. This rom is not recommened, only for testing. Tuatara is working on 1.5 which should fix the known bugs so lets be patient and wait for the release.

I could not have said it better. I am still using 1.4, with the hopes of finding more problems so we can make 1.5 the best ever.

Thanks again Tuatara !

[RanDomIze]

Hi
I tested the two ROMS (TuaMA 1.4 and Ivan Ver 4), The ROM of the Ivan seemed me much more stable, but it seems me that having the TuMa collaborated with the Ivan, It would be good for casting the positive aspects of the two ROMS.

In the ROM of the Ivan, the BT already is not disconnect, but however does not have communication with the BT headset.
Joining all the positive parts of one and another ROM, I think that it will be come at a good solution for ours loved Blue_Angel

All the problems in the ROM TuMa 1.4, that I found, already they had been related here for that I do not go them to repeat.

I ask already forgives to all for my bad English :oops:

[Snow_Elf]

Sorry, but I am using the Ivan ROM at the moment and it communicates with my BT headset just fine...? I followed the instructions for pairing posted in teh Ivan topic and it works OK for me?

[sephardic]

Tuma

I see everyone having issues my experience 100% positive and I use my blue angel day and night.

I did have issue and reflashed and cleaned up registry the option before I let it boot up for the first time and all worked awesome

I think most people let it boot up without doing the two options and then do it afterwards.

This causes corruption in installation.

Thanks again for all your hard work

Stew

[deepakr]

I tried out the TuMa 1.4 and so far have not faced a lot of the issues that have been listed in the posts. Maybe because I use very little of other softwares. Anyhoo..I just bought the itech r-35 stereo bluetooth headset and tried to use the ROM with the stereo headset capabilities. The issue i am facing is that as soon as I set it as Wireless Stereo, there is a spurt of music that comes in (maybe 1 sec) and then blank..The stereo headset icon comes up and then disappears. The hands free works fine but the stereo part is coming up a cropper. I tried the stereo with my laptop bluetooth and it works fine so the device is OK..
Any tips, suggestions or someone facing similar issues..
On another note, heaps of thanks heading your way Tuatara and your able team of testers for all the commitment and deadication you guys have put into this task. I tried the Ivan ROM, but personally I prefer your ROM for the clean installs and the apps, grouping and general housekeeping done by you.

Deepak

[patcat007]

Hey Tuatara

You are doing some fantastic work. I have tried the Tuma 1.3 on my Blue angel and it works fine except for the issues mentioned about the ROM.

I had downloaded your 1.4 v but after i saw your mail requesting users not to flash the device with that version. I abstained.

You had mentioned that you will be ready with the 1.5 version over the last weekend either the Alpha one or the final beta on 1.5. when is it coming can't wait to get my hands on it

[Tuatara]

Any one curious as to what this alpha 1.5 is like? I wanna flash.

Keep your pants on, and keep that raincoat closed ... TuMa v1.5 is in HEAVY development, and will be ready sometime this weekend.

The testing of TuMa v1.4 so far has identified a few things which should not be done - i.e. trade speed for stability (stupid idea really), and I will therefore be going back to my original plans. Also TuMa v1.5 will be a more 'core' ROM with optional additionals (which are installed completely integrated), as opposed to fully integrated, with optional removal. Now ... it is therefore VERY important to consider the number of changes which will be occurring in this ROM ... however ...

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?

I installed this new 1.4 rom on my BA (SX66) (for testing only) and it seems much faster.

It is faster though it is more 'unstable' because of this. In truth the ROM is actually quite stable - but you have to be careful how you use it (which most people aren't). KTamas has now been running the very SAME v1.4 released to everyone since the release time, and has not experienced any PIM corruption again. This could just be luck - but most likely it is by NOT pushing limits on the filesystem/transactional capabilties and by NOT using multiple plugins, managers, toolkits, etc. - i.e. NOT installing additional "toy/cool" add-on software - AND doing a proper full HARD-RESET according to the instructions, and NOT restoring a registry or backup using some 3rd party backup manager ... but by keeping the device 'clean' as it was originally put together (by me).

As I said above, since most users aren't this careful, and restore registry backups, overwrite programs and settings, and install applications "without regard for their personal safety 8)" ... this is a problem, leads to instabilities, BUT ... as best as I can ... it will be addressed as best possible in TuMa v1.5.

However I get an error "Handsfree.exe". The file 'Handsfree' cannot be opened. Either it is not signed with a trusted certificate, or one of it's components cannot be found. You might need to reinstall or restore this file.
Is there some way for me to work around this problem?

Ummm ... you didn't do a Format Storage of your device (i.e. hard reset). TuMa v1.4 does NOT contain any file called "Handsfree.exe". This IS present in TuMa v1.3 though ... so it's quite probable (and the case IMHO) that the filesystem was not properly formatted and you've only upgraded the ROM instead. You're now running TuMa v1.3.5 (v1.3 and a half :oops:) ... ick. Your mileage WILL vary. :evil:

If you're running v1.4 ... simply delete the file. Also make sure that the "handsfree.lnk" file is NOT listed in /windows/startup. This was the source of the original 'handfree notification bug' in TuMa v1.3. As for the rest of the device/registry/settings ... ummm ... good luck? :?

Hey Tuatara

You are doing some fantastic work. I have tried the Tuma 1.3 on my Blue angel and it works fine except for the issues mentioned about the ROM.

I had downloaded your 1.4 v but after i saw your mail requesting users not to flash the device with that version. I abstained.

You had mentioned that you will be ready with the 1.5 version over the last weekend either the Alpha one or the final beta on 1.5. when is it coming can't wait to get my hands on it

Well ... last weekend I got really busy, and "real-life", which includes family (#1 priority), real-work (#2 priority), and taxes (#3 priority) got "in the way". I will be working on it this weekend, and do need to get something together - for a few reasons:

1). I now have a whole SUITE of Bluetooth devices:
- Jabra BT150 Headset
- Jabra BT330 Headset
- BlueTrek X1 Headset
- Motorola HT820 Stereo Headphones
- Sirf III GPS Receiver
("Those toys! Where does he get those wonderful toys!" - Jack)

And have access to:
- Plantronics Headphones
- Another BT Stereo Headphone
- Jabra JX10
- Jabra BT250v

2). I need a stable ROM for myself and our corporate users. They're getting "tired" of waiting for me to say that it's ready too. Perfection has it's price. 8)

So ... the answer is ...

TuMa v1.5 ... Coming soon to a Blue Angel near you!

[Percz]

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?

Personaly the only stuff I worry about is stored on my Exchange Server, one quick Sync and it's back, without the messy backup software I've seen other use, that just mess up registry settings.

Much as I would love to mess about with no end of Alpha's, I suspect that alot of people, with no disrespect, will download it and ignore the Alpha status and complain about things not working if it was their mistake or not. So it's proberly best to keep us all begging for a Beta. :roll:

Wait - You have a family? :shock: [/quote]

[KTamas]

Wait - You have a family? :shock:
Of course he has not. Tuatara is a lone warrior, the community's hero who works in a dark basement on the ROMs.

Am I right? ;)

:lol:

[KTamas]

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?
I'd even flash a pre-alpha :)

[odie3]

TuMa,

Seems you released 1.4 while I was @ Las Vegas for a week - good job.

I assume since 1.5 is somewhat near I should wait for it? Seems like the proper thing to do after reading through this thread.

Questions:
What will the battery drain be on 1.5 compaired to 1.3? As said in the 1.3 thread I believe and what I personally see 1.3, it really eats the battery. Currently my Battery Pack Pro (http://www.omegaone.com/batterypack/pro/default.htm) status on full charge I have 33 minutes and after my day(s) on the floor working at NAB (http://nab.org) I would be lucky to have 5 minutes left before getting to the hotel.

What about the registry settings about BT and it staying on that I saw from ArtZ? Are you finding the same thing?

Boot Screen for BA, does it not work for 1.3? I installed it on my BA and did not see it when I reset my device.

Also, very nice Game Pack!! Thank you very much for that game pack!!!! :)

[efjay]

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?

Well, if the Alpha is stable enough yes.

[splonker]

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?

I imagine that many people would be willing to try anything given to them, but maybe thats just me? :roll:

[KTamas]

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?

I imagine that many people would be willing to try anything given to them, but maybe thats just me? :roll:
Unfortunatelly, you are right.

[Tuatara]

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?

Well, if the Alpha is stable enough yes.

Ummm ... how do I answer this without stating the obvious? Ummm ... ALPHA? :lol: :D :lol:

Seriously though - it should be quite stable, since I'm addressing the issues which have been found in v1.4, reverting filesystem elements (mostly) to v1.3 settings, and won't be trying to PUSH in any more of the AKU2 elements which I haven't extensively tested myself for a release. (Pun Intended)

Personaly the only stuff I worry about is stored on my Exchange Server, one quick Sync and it's back, without the messy backup software I've seen other use, that just mess up registry settings.

Much as I would love to mess about with no end of Alpha's, I suspect that alot of people, with no disrespect, will download it and ignore the Alpha status and complain about things not working if it was their mistake or not. So it's proberly best to keep us all begging for a Beta. :roll:

That's a valid point - but I'm not sure if everyone subscribes to that (correct) viewpoint. A lot of the other backup software tries to do 'everything' ... registry, settings, the lot. This is GREAT if you're using the SAME device, but will blow up in your face, if you change your device. It should be obvious if you think about it - but people don't.

Your points are definitely food for thought ... not sure if I want to be 'villified' for losing people's PIM data ... although ...

I'd even flash a pre-alpha :)

Yeah - but you're a sucker for punishment.

*poof* PIM data gone again! *smile* 8)

I imagine that many people would be willing to try anything given to them, but maybe thats just me? :roll:

Sweet! Another sucker ... *ahem* ... I mean victim ... *cough*splutter* ... I mean ... *ummm* ... willing ROM testing participant. :lol:

Seems you released 1.4 while I was @ Las Vegas for a week - good job.

I assume since 1.5 is somewhat near I should wait for it? Seems like the proper thing to do after reading through this thread.

Yeah ... wait for v1.5 ... I'm either going to release it as ALPHA or as BETA. If it comes out in the next day or two ... it'll be ALPHA - meaning I've been the ONLY one testing it. Otherwise, BETA would mean others have had a go, and I've been able to fix the immediate issues.

But if you're keen - any feedback on v1.4 is appreciated!

Hmmm ... I think these TuMa ROMs are kind of like Star Trek - just opposite. Instead of only the EVEN numbered movies being worth watching ... maybe only the ODD Numbered TuMa ROMs are any good? It's the quick release - v1.2 -> v1.3 thing ... and I'm doing it again ... v1.4 -> v1.5. 1.5 should then be good. :D

Wait - You have a family? :shock:

Egads?!!? You mean you don't? OMG ... 'divine creation'? ;)

S'truth ... got a couple of lil' ones already, and another 'on the way'.

Of course he has not. Tuatara is a lone warrior, the community's hero who works in a dark basement on the ROMs.

Am I right? ;)

:lol:

*GRiN* ... you guys had better go out and figure out what a Tuatara is! Got a lot in common with them ... not just because I'm an old lizard living in sunny New Zealand.

[splonker]

TuMa v1.5 ... The only question I have is ... Does everyone 'trust' enough to flash ALPHA, or would you rather flash BETA?

I imagine that many people would be willing to try anything given to them, but maybe thats just me? :roll:
Unfortunatelly, you are right.

Hehe, I think it's perfectly fine as long as people know that if something goes horribly wrong that cannot be fixed then you have to live with it... If someone doesn't understand that concept then don't try an alpha or beta rom! Simple as!

[Tuatara]

Questions:
What will the battery drain be on 1.5 compaired to 1.3? As said in the 1.3 thread I believe and what I personally see 1.3, it really eats the battery. Currently my Battery Pack Pro (http://www.omegaone.com/batterypack/pro/default.htm) status on full charge I have 33 minutes and after my day(s) on the floor working at NAB (http://nab.org) I would be lucky to have 5 minutes left before getting to the hotel.

Battery life will be almost as good as the original BA, and should be just as good as any other BA WM5 ROM now. For TuMa v1.3 one of the BIG problems was the 3 ring delay time issue - for which I tweaked a number of power management settings to get the ring time as low as possible.

I've now been experimenting more, and have found that by tweaking them further I can get the ring time to be only slightly slower (we're talking sub 1/4 second here), and have the power management settings almost the same as originally set by HTC. I'm still experimenting with other tricks though - so who knows, it could be identical or even better if I'm able to reduce power in other areas!

Also looking at what you're installing/using ... it's all the more reason for me to make the ROM 'feature poor' by default, and provide a number of 'enabling CABs' to make a fully featured ROM.

What about the registry settings about BT and it staying on that I saw from ArtZ? Are you finding the same thing?

Well ... yes and no. "Yes", because BT is staying on. "No", because the BT is still not working properly. And another "No" because this is the Widcomm stack instead of the Microsoft one.

I'm still hopeful I will find a solution to the BA BT problem ... but it's not looking good for v1.5 as yet. But we'll see.

Boot Screen for BA, does it not work for 1.3? I installed it on my BA and did not see it when I reset my device.

Boot screen is a 'special feature' addition for TuMa v1.4. It was to try and comfort people with a nice boot screen since everyone panics with the colour bars. TuMa v1.4 was also designed to be a 'feature rich' out of the box solution ... but the feedback I've had has been to go the other direction.

Anyways ... if you want to have the bootscreen in ANY other ROM, all you need to do is the following:

You'll find the application and TuMa v1.4 Bootlogo attached in the ZIP.

To make it run at startup, just include the following registry entries, and place the files from the ZIP in /Windows directory.

[HKEY_LOCAL_MACHINE\init]
"Depend32"=hex:14,00,1E,00
"Launch32"="BootLogo.exe"
Once you've done that - any of the other CABs I created can then be used, or just replace the BootLogo.bmp file. You will need to ensure that the BMP file is in the SAME format as the example. 8 bpp, and same file size & resolution if you want to change it. That's all that is required.

Also, very nice Game Pack!! Thank you very much for that game pack!!!! :)

Hey - it's just some freeware games, which I enjoy and have tested. They work reliably and are stable - don't use up much (of any) Storage Space, and can be installed very cleanly. Just some fun - all the credit goes to the respective developers as appropriate.

[KTamas]

Yeah - but you're a sucker for punishment.

*poof* PIM data gone again! *smile* 8)
Must be some kinda e-masochism...

[xplode]

I have already made a CAB with boot screen from Treo w700
Thanks Tuatara for this great lil prog, now everyon can customize their bootscreen

This cab should work in all WM5 versions

[splonker]

*GRiN* ... you guys had better go out and figure out what a Tuatara is! Got a lot in common with them ... not just because I'm an old lizard living in sunny New Zealand.


Yeah - but you're a sucker for punishment.

Hmm... I got bored so read up on what a Tuatara is... and there is a disturbing link here...

The name "tuatara" derives from the Māori language, meaning "peaks on the back". Tuataras feature in a number of indigenous legends. They are held as ariki (God forms). Tuataras are regarded as the messengers of Whiro, the god of death and disaster.

Need I say anymore? :shock:

[Tuatara]

*GRiN* ... you guys had better go out and figure out what a Tuatara is! Got a lot in common with them ... not just because I'm an old lizard living in sunny New Zealand.


Yeah - but you're a sucker for punishment.

Hmm... I got bored so read up on what a Tuatara is... and there is a disturbing link here...

The name "tuatara" derives from the Māori language, meaning "peaks on the back". Tuataras feature in a number of indigenous legends. They are held as ariki (God forms). Tuataras are regarded as the messengers of Whiro, the god of death and disaster.

Need I say anymore? :shock:

"In Polynesian mythology (specifically: Māori), Whiro is a lizard-god of the dead and evil. He lives in the underworld and inspires people to do evil. He is the eternal nemesis of Tane."

So ... ahem ... is it not 'evil' what we're doing now? Creating our own "Frankenstein" monster rising up from the dead assemblage of other device ROMs, thus ascending out of the underworld to become our Blue Angels?

Then again ... I am, after all ... only the messenger. ;)

[Tuatara]

PM'd me about the new 'leaked' Atom ROM ...

I think I have a NEW TOY to play with ... :D ... the Atom ROM is AKU 2.2 (not AKU 2.0!) ... so there should be a number of other cool things I can slice out for the BA!

Bwahahahahaaaaahaha! ... *gleefully*rubbing*hands*together* ... where is my scalpel?

The doctor is IN.

[odie3]

Tuatara,

I do not know which I like better, your detailed replies to silly questions or your ROMs. I am pretty sure if you just worked on ROMs you would be on Version 2 by now! :lol:

Also looking at what you're installing/using ... it's all the more reason for me to make the ROM 'feature poor' by default, and provide a number of 'enabling CABs' to make a fully featured ROM.

Yes, for me install Option CABs would be best but there are many others on the other side of the fence that enjoy a "feature rich" install that they do not have to worry about. I can see both views, since not long ago I was on just give it to me in one package [less chance to mess stuff up]. But now my vote is less is better. ;)

I also install these packages by default right after any ROM update -
Journal Bar (http://www.omegaone.com/journalbar/),
Calc-1 (http://www.omegaone.com/calc/ppc/),
and Wi-Fi Companion (http://www.socketcom.com/product/SW1221-596.asp)

The above programs are my "core" programs since my SX 56 [the older version of the SX 66]

http://ghostdogs.net/Pictures/sx66/sx66wm5.jpg


Boot screen is a 'special feature' addition for TuMa v1.4. It was to try and comfort people with a nice boot screen since everyone panics with the colour bars. TuMa v1.4 was also designed to be a 'feature rich' out of the box solution ... but the feedback I've had has been to go the other direction.

Ah, you should have just told me to D/L the 1.4 ROM - which I should have done any ways. Looking back that was a noob question - but thank you very much for the information.


Hey - it's just some freeware games, which I enjoy and have tested. They work reliably and are stable - don't use up much (of any) Storage Space, and can be installed very cleanly. Just some fun - all the credit goes to the respective developers as appropriate.
Well, I agree the credit goes to the developers but you deserve the credit in packaging them up for easy access!

[odie3]

[HKEY_LOCAL_MACHINE\init]
"Depend32"=hex:14,00,1E,00
"Launch32"="BootLogo.exe"


Question about Depend32"=hex:14,00,1E,00

There is Depend50 that equals this same vaule but Depend50 is shell32.exe.

Does it matter that hex:14,00,1E,00 is the same vaule for Depend 32 and 50?

Edit:
I guess not since I just booted up with the new Screen loader! Woot - no more color bars!!

[vlestat123]

I just cant wait to get the TuMa 1.15.

[Tuatara]

I just cant wait to get the TuMa 1.15.

I know ... me too really ... I want to get this DONE! :D

Anyways ... "real-life" pressures are taking their toll, and I need to focus on those first. I am working on the issues and changing the ROM to suit. I would like to have an AKU2 (or AKU2.2 ROM), but this is probably NOT going to be the case - although I will look at what can be integrated appropriately.

I want to have a 'Beta' release quality ROM on the site (not Alpha - too much trouble), so will only post v1.5 on the XDA-Dev site once it's ready.

*** If there is anything I would like to or need to test before this, I'll get in touch with those who have expressed an interest in being an Alpha tester beforehand with a version of the Alpha ROM. I'll expect some detailed feedback from doing this though! ***

Until then ... hang on ... I'm trying to make this one as stable and robust as possible, and still keep the speed up to v1.4 standards.

[vlestat123]

Well we dont want to push you to do something your not satisfied with .. but we are tryin to let you know that we are interested and couragin you.

so Tuatara, take your time and thanks alot for the hard work

[HDuser]

I have moved the file to a safe place on the ftp site.

ftp://xda:xda@ftp.xda-developers.com/BlueAngel/BA_WM5/Shipped_Extracted_Updates

Somebody needs to correct the wiki link

[vlestat123]

thanks alot MDAIIIuser .. your helping almost everyone here ..

[Packetsniffer]

I have been using v1.3 for several weeks now. I keep my BA mostly stock in terms of apps since I really need the reliability. I don't use any of the Today plug-ins. I have loaded several benign apps such as Mapopolis, IP Toolkit, Pocket IP, Pocket RSS, RDCalc, and Pocket FTP. There are two Bluetooth devices partnered up as well and I have the extended battery pack.

Random Rebooting
Over the last week, I started to experience the following situation. When I go to turn on the device on, the colored bars appear indicating the device is rebooting. This happened for no apparent reason. Typically, the device hadn't been used for several hours or through the night. It seems like it was happening at least once a day and no more than twice a day. This did not happen after the fresh installation of v1.3 several weeks ago. My device is a 1.5 years old. So, I checked out the battery and discovered that the battery was losing contact with the electrical contacts thus causing the reboots. I could reliably make the device reboot by shifting the battery while in place. I fixed this by simply placing a folded post-it note under the battery before locking it down. I'm thinking that fixed the issue.

Phone Hangup is Slow
I can't remember now if this occurred right after the installation of v1.3 or not. But, the phone is quite slow on responding to hangup a call. I have tried both the soft and hard buttons. I think the soft button is a little faster. Upon hitting the hard button, it may take up to 10 seconds to actually kill the call and 30 seconds for the "phone call in progress" icon to disappear.

My preference would be to have a stripped down base version (i.e., basic apps) and let us install the extra desired apps via cab files.

I'm also looking forward to the Bluetooh issue being resolved. I hope a solution is found before the device craps out. LOL

Great work Tuatara! Looking forward to v1.5.

[ArtZ]

@Tuatara

I think I found the reason why the MS Stack version doesn't work and I'm not really optimistic about a forthcomming solution.

Let me try to explain.

The Widcomm version uses 3 BT scripts:

-Init_Rom_v316.bts: Initilization the BRF6100 v1.3 device for Firmware v3.16 - Device in ROM mode - Compatablity with BRF6100 1.3 ROM ONLY!, Support for Soft Gemini

-Soft_Gemini_Disable_for_P4.bts: Texas Instruments, Soft Gemini Disable script

-Soft_Gemini_Enable_for_P4.bts: Texas Instruments, Soft Gemini Disable script

-Init_Rom_v316.bts This software update is required to be executed after power up or reset of the BRF6100 v1.3 device for optimal performance and enhancement of the RF.
Script Improvements:
-RF robustness improvement over temperature and process,
-Decreased output power by 2db for added RF robustness for compliance with the 4db output limit throughout all conditions,
-Improvement of maximum input power level,
-Corrected VS_Set_Settling_Time behavior

I believe MS BT Stack cannot support by default BRF6100 1.3 ROM. Microsoft Stack is compatible with BRF6150 2.12 ROM on WM5 devices but our BA use BRF6100 1.3 ROM.

Maybe someone with better knowledge of BT connections than myself can do that, maybe my theory is false... but I do believe that the problem comes from communication between Windows ROM and Radio ROM.

Cheers :cry:

[sgrbhtngr]

I have been using MS bluetooth stach without any trouble. But, now I have started experiencing some problems. The symptoms are:

1. Bluetooth does not turn on. If I check the 'Turn on bluetooth on' box, it gets checked. However, when I close this window and re-open it, I find the box unchecked.

2. If I try ot click on 'new partnership', it gives me an error.

3. Even with the 'turn on buletooth' box unchecked, the blue LED flcikers as if the device is connected via bluetooh.

Please help me look into this issue.

[candrat]

@Tuatara

I think I found the reason why the MS Stack version doesn't work and I'm not really optimistic about a forthcomming solution.

Let me try to explain.

The Widcomm version uses 3 BT scripts:

-Init_Rom_v316.bts: Initilization the BRF6100 v1.3 device for Firmware v3.16 - Device in ROM mode - Compatablity with BRF6100 1.3 ROM ONLY!, Support for Soft Gemini

-Soft_Gemini_Disable_for_P4.bts: Texas Instruments, Soft Gemini Disable script

-Soft_Gemini_Enable_for_P4.bts: Texas Instruments, Soft Gemini Disable script

-Init_Rom_v316.bts This software update is required to be executed after power up or reset of the BRF6100 v1.3 device for optimal performance and enhancement of the RF.
Script Improvements:
-RF robustness improvement over temperature and process,
-Decreased output power by 2db for added RF robustness for compliance with the 4db output limit throughout all conditions,
-Improvement of maximum input power level,
-Corrected VS_Set_Settling_Time behavior

I believe MS BT Stack cannot support by default BRF6100 1.3 ROM. Microsoft Stack is compatible with BRF6150 2.12 ROM on WM5 devices but our BA use BRF6100 1.3 ROM.

Maybe someone with better knowledge of BT connections than myself can do that, maybe my theory is false... but I do believe that the problem comes from communication between Windows ROM and Radio ROM.

Cheers :cry:

I'm not an expert myself but I totally agree with Artz. Everytime I tried my BA with flight mode On, the device response alot faster, so I assumed there were something wrong with the Radio ROM, but after reading what Artz explained, it makes much more sense to me.

[Tuatara]

@Tuatara

I think I found the reason why the MS Stack version doesn't work and I'm not really optimistic about a forthcomming solution.

Let me try to explain.

The Widcomm version uses 3 BT scripts:

-Init_Rom_v316.bts: Initilization the BRF6100 v1.3 device for Firmware v3.16 - Device in ROM mode - Compatablity with BRF6100 1.3 ROM ONLY!, Support for Soft Gemini

-Soft_Gemini_Disable_for_P4.bts: Texas Instruments, Soft Gemini Disable script

-Soft_Gemini_Enable_for_P4.bts: Texas Instruments, Soft Gemini Disable script

-Init_Rom_v316.bts This software update is required to be executed after power up or reset of the BRF6100 v1.3 device for optimal performance and enhancement of the RF.
Script Improvements:
-RF robustness improvement over temperature and process,
-Decreased output power by 2db for added RF robustness for compliance with the 4db output limit throughout all conditions,
-Improvement of maximum input power level,
-Corrected VS_Set_Settling_Time behavior

I believe MS BT Stack cannot support by default BRF6100 1.3 ROM. Microsoft Stack is compatible with BRF6150 2.12 ROM on WM5 devices but our BA use BRF6100 1.3 ROM.

Maybe someone with better knowledge of BT connections than myself can do that, maybe my theory is false... but I do believe that the problem comes from communication between Windows ROM and Radio ROM.

Cheers :cry:

While the scripts do have an effect (mamaich believes that there is a power-down element within the default MS script we're using), they aren't the source of the problem either.

There are a few aspects to this which we can control. I believe that mamaich has already injected the Widcomm initialization scripts into the Microsoft stack, and while he has managed to get some productive results - this hasn't resolved the issue and isn't the entire problem.

Without the appropriate device support the device itself wouldn't even be initializing. Part of the issue is that we're using the WM2003SE driver initialization for the BT stack - under WM5 while this does work, it's not working entirely properly. The hardware initializes fine, but we have a power-down request occurring ... somewhere.

I'm not an expert myself but I totally agree with Artz. Everytime I tried my BA with flight mode On, the device response alot faster, so I assumed there were something wrong with the Radio ROM, but after reading what Artz explained, it makes much more sense to me.

With flightmode on, the device response _should_ be much faster, as there is no "coexistance" problem to deal with. This is especially true between WiFi and BT. Having WiFi OFF, your BT throughput will be much better, and much more stable. This is because BOTH wireless methods use the same frequency spectrum. The TI chipset has special 'frequency hopping' communications between the BT and WiFi elements - called 'coexistance'. In this way BT and WiFi can coexist and transmit and receive at the same time.

Additional Info:

bigmike has been testing the Microsoft BT stack as well and he's come to the following deductions:

1). Wakeup of device when manually using power button - TURNS OFF BT
2). Wakeup of device from 'sleep' mode for doing maintenance tasks - TURNS OFF BT
3). In both cases BT ICON (i.e. the OS) detection does not update. This implies it is software controlling things at a hardware level, and not controlled by the OS.

Following this methodolgy, bigmike has patched some DLL's and (he believes) managed to keep the BT stack ALWAYS ON. At least the LED is always blinking, and is not affected by power events. However there is now no way to report the BT state back to the OS (since it effectively has no control anymore). It believes that the stack is always OFF.

---

The answer may lie somewhere between these two extremes ...

1). Inject the 'best' initialization scripts into the Microsoft Stack from the Widcomm.
2). Disable or circumvent the power management signalling in the Microsoft Stack to prevent TURN OFF.
3). Provide the appropriate BT ON / OFF signalling/control back to the OS to indicate BT availability.

I'll have a look into things as well, and see what I come up with.

[ArtZ]

There are a few aspects to this which we can control. I believe that mamaich has already injected the Widcomm initialization scripts into the Microsoft stack, and while he has managed to get some productive results - this hasn't resolved the issue and isn't the entire problem.


Hi Tuatara,

I've been through all the original "default.hv" from namaich and I haven't seen any script on it and I have also checked all files included in the distribution but I couldn't find any script either. I have downloaded a few scripts for the Widcomm version (for BRF6100 and BRF6150) and I have applied the scripts for BRF6150 to BA's BRF6100... on my Widcomm version.

This is the conclusion:

If I use BRF6150 2.12 ROM Widcomm scripts on BRF6100 1.3 ROM, my WM5 Widcomm version will behave fairly similar to the MS Stack version (the blue light keeps blinking after turning off the BA, but all BT connections are lost and I get a problem with the Flight Mode).

Besides Soft_Gemini_Disable_for_P4.bts and Soft_Gemini_Enable_for_P4.bts are used together with Init_Rom_v316.bts for WLan coexistance. Both scripts are compatible avec BRF6150 2.12 ROM and BRF6100 1.3 ROM but they must have the appropiate launcher. I still think that Init_Rom_v316.bts works only with Widcomm BT Stack.

I found at MSDN you can address the variable RADIOinit() on MS Stack but I couldn't find the way of doing it. Maybe you're luckier than me, maybe someone with more experience on BT networks than me can find a solution. I found the cause but not the solution... well, it's a step forward to the solution ;-)

[filjedi]

1st of all, great work on the ROM tuatara! I'm currently using 1.4 and I found this interesting bug which isn't listed in the first post. No matter how much free Storage I have to begin with (eg. 10 MB), it always dwindles to less than 1 MB in a matter of days.

At first I thought it was the Notify Queue, but I clear it regularly using Check Notifications. Still, my free space slowly dwindles. Hope you can figure out what's causing this. Thanks!

[simonsalo]

No matter how much free Storage I have to begin with (eg. 10 MB), it always dwindles to less than 1 MB in a matter of days.

At first I thought it was the Notify Queue, but I clear it regularly using Check Notifications. Still, my free space slowly dwindles. Hope you can figure out what's causing this. Thanks!

I had the same problem using an original Maimach ROM and you won't believe what I found! (I am not saying this is happening to you but it is worth a look...)

For some reason my voice recorder started activating some times when my phone rang and didn't switch off. So what I ended up with was two or three huge sound recording files of 10 - 20 MB each which made it look like my storage was disappearing. The trick was these files did not show up when I searched for files over 64k in the on board search application and also didn't always appear in the on board file explorer.

However, when conected via active sync, exploring the pocket pc on my desk top revealed these large files sitting in my documents. I then deleted them & voila! my storage had returned. This happened several times and the only way I could stop this was by using the lowest quality record setting and changing my phone ring to anything else other than the default!

However since loading one of Artz's ROMs, I have not experienced the problem recently.

Good luck,
Simon J

[imatrix]

Hi Tuatara,

great work on your release.
anyway can u plz tell me what is upcoming feature in v1.5?

thx

[indra9110]

I thing we must be pation for TUMA 1.5 because we must understand TUATARA work very hard to make that ROM must beter than the old one

SO ....

@Tuatara....
I think you dont have to hurry woorking with the new ROM... and all of us will supporting you .....

[-KLOUN-]

I dont used BlueAngel 4 mounths...(Bye HTC Magican :) )
Heh... I see more ROMs on FTP. :shock:
I install this ROM on my BA-its great! Its a pitty that ROM is so slow...
This functionality is full!
Which ROM is more quickly?

[ranger1801]

Hello,

i´ve been tried every version of Mamaich WM5 and TuMa Versions.

Not the 1.4 - it´s me to buggy. But I will say:

Your work is very great an have brought WM5 to all BlueAngel-Users.
By the way Tuma 1.3 is a realy good work. Speed is acceptable, all tools work fine. No problems with the most of peripherie like Headset or other hardware. Wifi is good. Battery is also okay. Every night on the powercord, and one day with Navigating, Telephony and Office Work is possible.

If i could help u, i´ll do, but this programming isn´t my thing.

Isnt it possible that all others programmers like Ivan, Logout and Artz can work together with u?

I think every one will do the best for himself and say I´ve baked the best rom. But this seems to be working against.
If a user say I want this tool, the programmers are sitting in there rooms and take the tool to the rom. I think u can´t do it to all users right. I think the only possible way to get an realy usefull rom is to get more speed, a working bluetooth stack without power off/on bug, every installed hardware should work, (Camera, Wifi and so on) and all GSM tools like GPRS, SMS, MMS and GSM. All others things are secondary. If a user had an Anycom Headset and it doesn´t work but every Jabra Headset will work fine - it´ll be pitch for the anycom user. MS doesn´t work better. They say this is compatible and this not. They say to the hardwarebuilders how they have to build the hardware and not more.

Maybe a Tumaloivar Rom based on TuMa 1.3 can be a posibility.

Not everybody can do everything.

Never forgett - without Mamaich and Tuatara - we don´t have WM5.

And so i will never try another rom if there is no name like TuMa insert.

They know what they do. And all others make someone new. They used Mamaich WM5 ported from Magican, Wizard or someone other.

Okay enough honey for Mamaich and Tuatara - they work hard for no money. Maybe some "Donate Money" - but it is there freetime, when we work or lay on the couch.


Think Forward to TuMa v. 1.5 or 2.0 - the choice which operators will buy for all BlueAngel Users....

[-KLOUN-]

Think Forward to TuMa v. 1.5 or 2.0 - the choice which operators will buy for all Blueangel Users.... :lol: :lol: :lol:
HTC Close The BlueAngel platform in this mounth. :wink:

[Percz]

Really? BA dies before it's time if you ask me. The value of these babys is gonna skyrocket now.

Just to add, I'm led to belive that Logout's ROM is very much based on TuMa 1.4, but trys to add a few features that other ROM's had.
I'm sure Logout's, and indeed everyone elses ROM's will all have something that TuMa can learn from and add/use in TuMa 1.5, so from that view theres nothing wrong with people releasing their own ROM. :-)

[Tuatara]

i´ve been tried every version of Mamaich WM5 and TuMa Versions.
Not the 1.4 - it´s me to buggy. But I will say:

Yeah ... v1.4 was an attempt to do a LOT of changes all at once. And strangely, in my testing now the core of this ROM is very stable. There are just one or two things which need fixing, and I believe it'll be quite solid.

Isnt it possible that all others programmers like Ivan, Logout and Artz can work together with u?

Everyone is working together in a way ... by working on the ROMs and communicating our findings, we're trying to make things work. Solving bugs is a 'lonely' process ... the only way to do it is to step through each possibility and find out where it's going wrong. When one does find something of note, we post it here, and tell everyone about it. If we do manage to solve something, and put it in a ROM, Ivan, Logout and Artz (and anyone else) can decompose the ROM themselves, and see exactly what has been done too! The information is there ... sometimes it just needs a few tools to look at it though. :-)

I think every one will do the best for himself and say I´ve baked the best rom. But this seems to be working against.

Well ... everyone has their own "EGO's" to stroke. I've got mine, but it's already well established - even outside of all this ROM editing/hacking - so I don't need any more 'glory'. 8)

As before, I'd much rather help and spend the time to inform everyone of the details and intricacies of the ROMs which are created, so that everyone can see what has been done. That's why I spend the time and do the 'reviews' of the released ROMs. It teaches me things about how others improve the ROMs, and also gives the information to everyone else to make educated decisions about what the ROM actually fixes. Same goes for logout's work on the TuMa v1.4 base - he's proven that the base ROM (without the fruity filling ;-)) works very well, and it is fast. This means it's a great starting point, and a lot of things were fixed. Also, with integrating Widcomm BT Stack, he's created a version to further the BT development. All in all very good news, and I'm watching for constructive feedback for ANY and ALL of these ROMs.

Never forgett - without Mamaich and Tuatara - we don´t have WM5.

Actually ... it's if we didn't have mamaich ... without IMGFS, and the work on the original v3.1 BA, and Wizard Port ... it would be a rather bleak outlook for WM5 on BA. Not to mention all the hard work by the people before him ... itsme, gmap, etc. Lots of developers share in the credit. We can NEVER forget that.

---

Just to give you a progress update ... I've been trying to get AKU2 (or AKU2.2) onto the Blue Angel platform and to date I've been entirely unable to. There are too many interdependancies back to the boot XIP sections which I can not fix (at present) without a LOT of work and time (which I don't have).

However, I am working on an AKU 1.1 Port, and hope to have AKU 1.1 integrated into a NEW ROM base, with all the performance enhancements, and the AKU2 elements (like Avrcp, A2DP, etc.) which could be ported and integrated available in this ROM.

So ... I may release a v1.5 and a v2.0 at the same time. v1.5 will be a BETA (AKU 0.0) and v2.0 an ALPHA (AKU 1.1). This will still be a little while away, since I still need to focus on some other "real-world" things first.

Patience ...

[simonsalo]

Hello Tuatara.

I have successfully tried a few of these cooked roms & I am currently using Artz's earlier Microsoft BT Stack version with Ext rom on SD card. However, technically I am a Layman. So can we reflash various WM 5 roms and test them without choosing the yes / yes option at boot up so as not to delete anything? Will the new rom work then as intended?

I am working on an AKU 1.1 Port, and hope to have AKU 1.1 integrated into a NEW ROM base, with all the performance enhancements, and the AKU2 elements (like Avrcp, A2DP, etc.) which could be ported and integrated available in this ROM.

So ... I may release a v1.5 and a v2.0 at the same time. v1.5 will be a BETA (AKU 0.0) and v2.0 an ALPHA (AKU 1.1).

Can you explain what you mean by and what is the difference between AKU 0.0 & 1.1 from a layman's perspective?

Also Logout included the following files in his ext ROM. D3D_Driver_Addon.cab, DDraw_Acceleration.CAB, Running_Progs_Inst.CAB. What do these do & should we load them to improve performance in Artz's rom?

Last but not least how can we add the today plugin with the little padlock that locks the device? I have searched all Ba postings and can only find Armstrongs device lock enhancement which still needs the original plug in to work.

By the way your boot splash works fine in Artz's rom!

Regards,
Simon J.

[Phreakazoidz]

Thanks Tuatara for ur Hard work.. waiting for a new rom....


:twisted:

[Tuatara]

I have successfully tried a few of these cooked roms & I am currently using Artz's earlier Microsoft BT Stack version with Ext rom on SD card. However, technically I am a Layman. So can we reflash various WM 5 roms and test them without choosing the yes / yes option at boot up so as not to delete anything? Will the new rom work then as intended?

Well ... let's see ... how can I put this ...

Q). Can you flash ROMs without choosing NO/YES/YES on Hard Reset?
A). Yes, you can ... because I can't hit the right buttons for you. :D

The real answer is that if you don't do this, you're going to be working with a registry and configuration information from a DIFFERENT ROM! It's like trying to run Windows 98 using a Windows XP registry ... sure some of it is the same ... maybe a LOT of it is ... but it will have differences, and those differences will cause things to fail.

Basically ... you might be able to keep your apps and config, but your device is running off a different set of instructions, and I won't make any guarantees as to how well it will run. That's also why sometimes I don't (or can't) respond to some reported 'bugs' - I can't replicate them, and they make no sense. So I can only deduce it's the end-user who has created this problem themselves.

I sometimes wonder if those people who have the largest problems with ROMs just fail to read the instructions. It's there for your protection! ;-)

Can you explain what you mean by and what is the difference between AKU 0.0 & 1.1 from a layman's perspective?

AKU 0.0 is the original WM5.0 ROM which was released ... that's what we have available for the BA. Nothing more ... so ... I'm 'adding' what are the latest and greatest things to have. :D

Microsoft Bluetooth Stack in AKU 1.1 of WM5.0 added the following:
* Generic Access Profile (GAP)
* Generic Object Exchange Profile (GEOP)
* Serial Port Profile (SPP)
* Dial-up Networking (DUN) Profile
* Hands-Free Profile (HFP)
* Headset Profile (HSP)
* Human Interface Device (HID) Profile
* Object Push Profile (OPP)
* ActiveSync-Over-Bluetooth
* Bluetooth Car Kit Support
* OTA Remote Provisioning
* Other OS changes and cool stuff

Microsoft Bluetooth Stack in AKU 2.0 of WM5.0 added the following:
* Advanced Audio Distribution Profile (A2DP)
* Audio/Video Remote Control Profile (AVRCP)
* Direct Push Email
* Messaging and Security Feature Pack (MSFP)
* Remote device wiping
* Security policy enforcement
* Global Address List Lookup
* Communication Manager
* Battery Icon & Removed Clock from Today Bar
* More Bluetooth improvements

Microsoft Bluetooth Stack in AKU 2.2 of WM5.0 added the following:
* Repalces the Clock in Today Bar as Registry Option
* Enhanced Push Support (extended)
* Not sure what else ...

Also Logout included the following files in his ext ROM. D3D_Driver_Addon.cab, DDraw_Acceleration.CAB, Running_Progs_Inst.CAB. What do these do & should we load them to improve performance in Artz's rom?

D3D = Direct 3D. Since we don't have any hardware accelleration, this is the SOFTWARE reference driver for D3D support. Unless you're using D3D applications, you'll not need to have this installed.

DDraw_Accelleration = Direct Draw ... not sure what this does (haven't looked), but from a guess it probably installs the ddraw.dll DirectDraw support instead of just using GDIPlus. Unless you have a need for it, you won't need to install it.

Running_Progs = Quick access to the 'mini' task manager in WM5 already. It just brings up the running tasks control panel, so you can terminate things if needed.

NOTE: TuMa v1.5 will include CABs which will allow you to enable and disable D3D accelleration support as you see fit. This is because when enabled the device (overall) actually slows down. But, you get D3D support, so it will be up to the end user now to decide what they need.

Last but not least how can we add the today plugin with the little padlock that locks the device? I have searched all Ba postings and can only find Armstrongs device lock enhancement which still needs the original plug in to work.

This is because it's part of the ROM/OS core. There are a number of 'hooks' which need to be done to lock out the screen, keys, keyboard, buttons, etc. If that support is not present, it will crash. So ... in short, it's only available on those devices for which it was designed for and have the appropriate support elements.

By the way your boot splash works fine in Artz's rom!

It should! It's nothing special ... just something to make everyone a bit happier about the booting of their Blue Angels.

Besides ... I had some fun making some Blue Angels for TuMa v1.4. I got to dust off some artwork skills there ... ;-)

[fusedwire]

I encountered this error after a soft reset in logout rom. Since logouts rom is based on Tuma 1.4, I thght I should post it here.

Cannot open 'tmail'. A critical component is either missing or cannot start because program memory is unavailable. Tap Start > Settings > System Tab > Memory, stop programs that did not automatically stop, and try again.

Dont know if its S/W relate, or OS related. But this was immidiately after a soft reset after a bunch of replog.exe errors.

[Avinash75]

[quote="Tuatara"]

NOTE: TuMa v1.5 will include CABs which will allow you to enable and disable D3D accelleration support as you see fit. This is because when enabled the device (overall) actually slows down. But, you get D3D support, so it will be up to the end user now to decide what they need.

[quote]

Hi Tutara

Thanks a lot for all the hard work being put by you in developing all the ROMS and the splash screen (oh what a relief from the dreaded stripes :lol:

second i can see that 1.5 is on its way from your comments above and from your signature (you already using 1.5 Alpha)

wish to see it being relaesed soon so that i can lay hand on t o it :-)

[nijhof]

i cant wait for it either, any estimate time of arrival?

(having major problems with artz rom, so waiting for tuma 1.5 for reflash)

[cmairhof]

Tuatara - if you need beta testers for the exchange feature please let me know

cmairhof

[TheLastOne]

Can the process originally used by mamaich to convert the first Wizard Rom into a viable Blue Angel rom not be repeated on the newer AKU2.2 Rom to create a new viable AKU2.2 Blue Angel rom? I can imagine that such a process is in no way simple, but would that not provide us with a better end rom?

Now, I must say, I know close to nothing about the subject, so there very well may be a simple answer.

BTW, I'm glad to hear that 1.5 is in the works, but seriously, you've done more than your fair share for the community as it is. Slow down, deal with your personal issues first ;).

It's shame that we have to turn to these methods, and have a few good people spend more than their fair share of time on something that should've been provided to us by the companies that sold us these devices in the first place. At least you've all gone and proven that their claims that it was "technically impossible" was just a load of crap ;).

[Tuatara]

Can the process originally used by mamaich to convert the first Wizard Rom into a viable Blue Angel rom not be repeated on the newer AKU2.2 Rom to create a new viable AKU2.2 Blue Angel rom? I can imagine that such a process is in no way simple, but would that not provide us with a better end rom?

The answer to this is YES and unfortunately NO.

I've tried to port the Himalaya AKU2.0 ROM, and so has mamaich (and bepe I believe). We've all met with failure so far because of one fundamental issue. There are new functions required in the boot section (XIP) of the ROM, and we have no means to add these new functions in (at present). This would require a RECOMPILE of the boot portions and needs the BSP of the Blue Angel to do so.

At present I'm trying the 'opposite' approach, and that is to move as much of the newer ROMs into what is effectively an AKU 0.0 Blue Angel ROM. I'm working on AKU 1.1 elements, with as much of AKU 2.0/2.2 as I can merge in without causing compatibility issues. This isn't as easy as it sounds, and so far some substantial hex editing has been involved.

Also, I've been 'creating' new modules and relocating them, so that everything can fit into the ROM as an XIP module instead of as a reconstructed DLL. This has performance advantages and memory advantages, so I feel that the extra effort is really worth it.

BTW, I'm glad to hear that 1.5 is in the works, but seriously, you've done more than your fair share for the community as it is. Slow down, deal with your personal issues first ;).

Hey - I'm mostly doing this for selfish reasons y'know ... I want a Blue Angel which works the way _I_ want it to. But I'm also doing my personal stuff too ... believe me. But slowing down isn't in my nature. :D

It's shame that we have to turn to these methods, and have a few good people spend more than their fair share of time on something that should've been provided to us by the companies that sold us these devices in the first place. At least you've all gone and proven that their claims that it was "technically impossible" was just a load of crap ;).

Well ... we actually have Microsoft to thank for our BA's. If they hadn't developed WM5 on the BA, and there hadn't been a leak of an 'Alpha' ROM, then there wouldn't have been any chance to have WM5 running today.

Mostly the reasons that companies (like HTC) don't update their devices isn't because they couldn't afford the $50K ('real cost') to have a few programmers sit there and make a WM5 version for the BA ... but that the support and distribution of this would cost infintely more.

In theory ... if they could/would provide the public with the means to "do it themselves", they would still need a community like XDA-Dev to support it. And that would cost a lot of money, and would cost a lot in terms of "good will" and "perception" of the company. Think about all the (stupid) complaints like "IT DOESN'T WORK!" ... duh.

XDA-Dev provides this support for "free" ... but if HTC were to give us a new ROM for BA, the public would NEED to understand that HTC would NOT BE HELD LIABLE for anything done with their 'friendly' community release. We would be the instigators of this 'maelstrom' of support issues - because HTC has newer (better?) devices to make.

It's all a financial equation ... as Mike Calligaro has put it as well.

Anyways ... my BA is going to ROCK when I'm done with it. ;-)

[simonsalo]

Last but not least how can we add the today plugin with the little padlock that locks the device? I have searched all Ba postings and can only find Armstrongs device lock enhancement which still needs the original plug in to work.

This is because it's part of the ROM/OS core. There are a number of 'hooks' which need to be done to lock out the screen, keys, keyboard, buttons, etc. If that support is not present, it will crash. So ... in short, it's only available on those devices for which it was designed for and have the appropriate support elements.

Tuatara, Thanks for your responses. Because of you we will all be BA armchair experts eventually! Are you going to be able to install the Today lock plugin in your 1.5 release?

Regards,
Simon

[xdaradar]

Anyways ... my BA is going to ROCK when I'm done with it. ;-)

I'm sure it will, I can't wait :P and please keep alive the phone and bt-handfreeset quality I expierience today in your V1.3.

In the old wd2003-day's I had to wait for seconds to start talking when picking up the phone. In V1.3 there's an instant connection as soon as I pick up the phone.

Same goes for my jabra 250V BT headset. It works excellent. No noise, no echo's of any kind. People keep asking me (even when i'm in my car) if i'm still on the phone. Because of the total absence of noise they think the connection got lost.

And GPRS as well, never had the stable GPRS connection in wm2003 as in V1.3. It's always there and if it needs reconnecting it will do so. In wm2003 I very often needed a soft-reset to get GPRS back to work.

[xdaradar]

Tuatara - if you need beta testers for the exchange feature please let me know

cmairhof

same here,'I'm using it all day, every day via GPRS and security certificates, combined with a few pop3 email accounts. I stopped using activesync and WiFi because of the instability of those two.

Is there a way to build in a send/receive schedule in the pop3 email function, just as it is in the activesync/exchange function. I don't need a mail update during the night.

[Tonix]

I have installed TuMa 1.4 on I-Mate PDA2K and:

- "Picture & Videos" it doesn't work :cry:
- At times Item TomTom in the Today Screen disappears (installed TomTom is the version 5.21) :shock:

I attend the new version TuMa 1.5.... but when it will go out? :roll:

:idea: Compliments Tuatara for the job that are doing! :idea:

[TheLastOne]

Tonix, Tutara has already acknowledged the bugs within 1.4. Rest assured that 1.5 is in the works and that he'll get it to us when he can.

In the meantime, switch to 1.3 if those bugs are too much for you.

[Tonix]

OK :oops:

[Fredrick_Fredrickson]

Tuatara, have you considered UPXing the apps in the ROM?
http://upx.sourceforge.net/
You could cram a lot more apps in, and they load/run super fast (most seem to load about 1/3 faster)
Worth a thought. Keep up the amazing work - I'm looking forward to 1.5!

[Tuatara]

Tuatara, have you considered UPXing the apps in the ROM?
http://upx.sourceforge.net/
You could cram a lot more apps in, and they load/run super fast (most seem to load about 1/3 faster)
Worth a thought. Keep up the amazing work - I'm looking forward to 1.5!

Well ... TuMa v1.4 when released already HAS three core apps (and other bits) UPX'd! So ... we're already ahead of you on that one! ;-)

mamaich was the one who sorted out the issues for using UPX on WM5/WinCE, and then provided the source code update requirements to the developers of UPX for incorporation into the next release. So ... the apps in TuMa v1.4 have (indirectly) proved this concept already.

Powerpoint alone went from over 2Mb in size (uncompressed) to around 800K (compressed). Now the IMGFS filesystem is compressed as well, but this compression isn't as good as UPX. So, UPX achieves some 'additional' ROM space, but it's not as big as the difference from 2Mb to 800K ... it's more like around 300K or so ... but having 10-15% more compression on HUGE files is a LOT of additional ROM space. :-D

As always - the know-how is released 'to the world', so now the ability is available for everyone - but you have to VERY careful using it, in case other applications reference resource elements or need access into the applications for any reason - UPX'd versions will fail. YMMV.

[habibjamil]

Hi,

1) This is my first post.

2) I am a very happy camper with TuMa 1.3

3) My major complaint about it is the slide-out keyboard; when I use it to type, the screen flickers and the characters do not show; when I click on the soft keyboard, the characters all show at once.

Thanks a million for WM5 on BA... Anxiously awaiting TuMa 1.5...

[fr.ts]

couldn't wait for tuma 1.5........universal it is......but I will install 1.5

[icohen2002]

couldn't wait for tuma 1.5........universal it is......but I will install 1.5
1.4 is very fast and have a lot of new develop but still he is going crazy
so u must wait
Israe;

[terryd1980]

Hi Tuatara,

I know that you have done a massive amount of work on the WM5 ROMs but I was wondering if you can tell me something?

I've tried a couple of WM5 ROMs and although they're getting very good and close I just can't seem to get by with one, what I'd like to know is... Is it possible to make a WM2003se ROM with the persistant storage values of WM5?

As you can probably tell I have no idea of how to construct a ROM so I don't know if this is a possibility or not.

If it is possible do you think it would be hard to make?

Thanks for the work Tuatara, You Rock!!

Terry

[Tuatara]

I know that you have done a massive amount of work on the WM5 ROMs but I was wondering if you can tell me something?

Certainly ... I'll try ... :-)

I've tried a couple of WM5 ROMs and although they're getting very good and close I just can't seem to get by with one, what I'd like to know is... Is it possible to make a WM2003se ROM with the persistant storage values of WM5?

Well ... the short and simple answer is 'no'. WM5 was architected from the 'ground up' to store all information into the Flash memory, whereas WM2003/SE uses RAM for all storage requirements. In WM2003/SE you have a slider which controls how much RAM is used for storage, and how much is used for applications. This isn't present at all in WM5. WM5 stores all data into the Flash memory, which of course is much slower than RAM, but ensures that you keep all your valuable data.

In theory we 'could' make something which could 'COPY' the WM2003/SE RAM data into a FLASH file - but that would be a real nightmare of a task. It would effectively be a 'backup' program which ran continuously ... there is probably something like that out there already.

(An aside for more info ... since I feel like rambling on ...)

Because in WM5 the device now has 'so much RAM available' ... and correspondingly LESS flash storage space ... we try to make better use of it. This is part of the reason why we've done a few 'tricks' with the TuMa ROMs to improve performance.

TuMa ROMs use a RAMDisk of 32Mb size to handle all Volatile and Temporary requirements of the Operating System. This speeds things up quite a bit, and lets 'useless' information (like the Pocket IE Cache Files) to be put into RAM instead of FLASH - making it much faster, since we really don't care if we ever lose the cache data. It also saves a LOT of FLASH memory which would otherwise be 'wasted' on this data.

Also, I try to pack as MUCH as I can into the TuMa ROM (almost 32Mb space) as possible, since installing applications into FLASH now eats up your Storage Space - which is obviously better used to hold your data.

*** This is WHY the TuMa ROMs are 'feature rich' and not just base ROMs. A base only ROM would have all this 'unused space' in the FLASH, and you'd never be able to use it for storage. Why not fill it with 'useful' things? NOTE: TuMa v1.5 will use the 'enabling' metaphor though for these added features - so the 'deafult' ROM will be a 'base', but by adding a few registry entries and shortcuts, you get a 'fully featured' ROM without ANY storage/Flash cost.

As you can probably tell I have no idea of how to construct a ROM so I don't know if this is a possibility or not.

If it is possible do you think it would be hard to make?

So the answer would be 'no' ... can't be done. It's fundamentally a difference of architeture and implementation right in the OS itself. You could make a 'backup/copy' functionality for WM2003/SE ... but that's it. Similarly ... WM5 writes to FLASH, but uses the RAM to 'cache/buffer' the data before writing it to permanent storage.

Thanks for the work Tuatara, You Rock!!

Thanks Terry. :oops:

Anywho ... I'm off to California tonight (3 day whirl-wind business trip), so I'll be taking along my ROM development 'kit' and working on TuMa v1.5 while I'm there (and maybe on the plane - if I have the space to do so). Hopefully I'll have my evenings 'free' enough to get this next version 'FINALLY' done. Wish me luck!

TTYL ...

[rjbrown99]

If you are coming to Los Angeles, how about grabbing a beer? I'm buying if you're drinking. Thanks for the hard work on the WM5 ROM.

[Tuatara]

If you are coming to Los Angeles, how about grabbing a beer? I'm buying if you're drinking. Thanks for the hard work on the WM5 ROM.

"Mmmm Beer. My love for you will never die."

Could do ... I'm landing Wed mid-afternoon at LAX, and going to be in "Lake Forest" near Irvine for Thurs/Fri. So it might be possible - depending on how the meetings/work/time goes. PM me contact details and I'll get in touch once I'm there (and coherent after the 12 hour flight).

[terryd1980]

Wow!!!

In my wildest dreams I never thought I'd hear such an informative answer, thank you very much. :lol:

It's a shame it can't be done but I still think the work you're doing is fantastic, I'll look forward to playing with 1.5 soon.

Thanks Tuatara - (HTC God) :wink:

[borjok536]

Can someone here upload the bootlogo.exe, Im still using TuMa v1.3 and i want to also to get rid of that four-flashing colors everytime i soft reset my BA.

[xplode]

Here you go

[evgeny007]

Sorry guys, maybe there was an answer poseted here before, but i've missed it.
After ROM update from 2003 to Tuma 1.4

Bluetooth turns off when you press power button.

Is this a bug in Tuma 1.4 ? If it is, will it be fixed in 1.5?

Or is there a fix for it?

Would appreciate any help.

Thanks a lot

[Tommigrl_7o2]

The BootLogo.exe doesnt get rid of the 4 colors after a soft reset does it? If so how?

[xplode]

Boot screen is a 'special feature' addition for TuMa v1.4. It was to try and comfort people with a nice boot screen since everyone panics with the colour bars. TuMa v1.4 was also designed to be a 'feature rich' out of the box solution ... but the feedback I've had has been to go the other direction.

Anyways ... if you want to have the bootscreen in ANY other ROM, all you need to do is the following:

You'll find the application and TuMa v1.4 Bootlogo attached in the ZIP.

To make it run at startup, just include the following registry entries, and place the files from the ZIP in /Windows directory.


[HKEY_LOCAL_MACHINE\init]
"Depend32"=hex:14,00,1E,00
"Launch32"="BootLogo.exe"


Once you've done that - any of the other CABs I created can then be used, or just replace the BootLogo.bmp file. You will need to ensure that the BMP file is in the SAME format as the example. 8 bpp, and same file size & resolution if you want to change it. That's all that is required.

so short explaination:
1. Make a BootLogo.bmp or use default WM5
2. Copy BootLogo.exe and BootLogo.bmp to \Windows
3. Crete these registry entryes into registry
4. Reboot

[HiltonT]

Hi Tuatara,

Before 1.5 is finalized, I have a request about the "lock" function. Presently, when I lock the device, all the buttons remain active insofar as waking up the display and performing their functions, however the screen remains locked. Is there any way to actually have the "lock" feature, well, aaaahhh, actually "lock" the device properly?

As I keep my BA in my pocket, and aside from the ringtone power draining features, I think this dysfunctional "lock" feature is resulting in my BA TuMa 1.3 lasting well under 8 hours even without a phone call before resetting itself with the color bars and having a battery level in the red.

To my way of thinking, "lock"ing the BA should mean that no buttons are functional aside from the power button, and when a call comes in, the "accept/reject" buttons should also need confirmation so as not to automatically become active, meaning a lot of calls are answered or cancelled even before I know the call has been received (and the caller gets a "bugger off" message (if cancelled) or a nice conversation with a couple of coins and a USB key (if accepted). :)

[Tuatara]

Hi Tuatara,

Before 1.5 is finalized, I have a request about the "lock" function. Presently, when I lock the device, all the buttons remain active insofar as waking up the display and performing their functions, however the screen remains locked. Is there any way to actually have the "lock" feature, well, aaaahhh, actually "lock" the device properly?

As I keep my BA in my pocket, and aside from the ringtone power draining features, I think this dysfunctional "lock" feature is resulting in my BA TuMa 1.3 lasting well under 8 hours even without a phone call before resetting itself with the color bars and having a battery level in the red.

To my way of thinking, "lock"ing the BA should mean that no buttons are functional aside from the power button, and when a call comes in, the "accept/reject" buttons should also need confirmation so as not to automatically become active, meaning a lot of calls are answered or cancelled even before I know the call has been received (and the caller gets a "bugger off" message (if cancelled) or a nice conversation with a couple of coins and a USB key (if accepted). :)

That is so VERY strange. I've just checked it here on a TuMa v1.3 device (I'm comparing longevity/battery w.r.t the TuMa v1.5 I'm still working on) ...

Locking the device LOCKS all buttons, and prevents anything other than the power button from waking it up. This is using the 'stock' default settings of TuMa v1.3. Even the phone buttons don't wake up the device. Incoming calls can only be answered after unlock as well.

So, it's very strange that you do not have it locking your device fully.

*** Does anyone else have this issue? I can't seem to replicate it! ***

In other news, back from California - didn't have the chance to work on the ROM while there, and was too tired to pull out the laptop on the plane flights (watched some movies instead :-)). At present, TuMa v1.5 still has bugs which I need to fix, so I'm sorry, but I have no Alpha version to release yet. Hopefully VERY soon though ... I'm now down to having 7 bugs, which I have been able to find and need to still fix. No luck on the Bluetooth turn on/off issue as yet either. That will probably still be a known problem. *sigh*

[Chrischi]

Hi
I've installed Tuma V. 1.4 and the devicelock seems working well. Exept when phonecalls comes in, the phone-buttons get active to answer or reject the call. For me it's ok and I think it has to be that way?.
I use the Weis ScreenLock to turn display & buttons off. Also incomming calls can be picked up with the phone-buttons. But I use the ScreenLock to keep bluetooth alive when paired with the car-handsfree. Otherwise bluetooth turns off, when the Qtek powers off.
I'm using the version 1.4 a few days now. There are several problems (already listet in this forum), but bluetooth is working well. Activesync & Headsets over Bluetooth are functioning without problems.

Thanks for your great work to get wm5 running

Chris

ROM: 5.14TuMaWWE
Radio: 1.15.00
Protocol: 1337.45
ExtRom: Tuma v.1.4

[thingonaspring]

The screenlock app refered to above can be found here :-
http://www.freewareppc.com/utilities/screenlockforpocketpc.shtml

- and it's freeware ;-)

[xdaradar]

Done some stresstesting and this is what happened.

Walked for an hour with my dog starting with 40% battery warning:

All at the same time active for an hour:
- permanent GPRS active
- permanent BT GPS active
- Oziexplorer navigation via virtual GPS port
- TomTom 5.21 navigation active via virtual GPS port
- IGO 2006 navigation active via virtual GPS port
- Internet Explorer with moving weather satelite info running

TT and IGO did a lot of talking and route recalculating, since i directed them back home, while walking around in wrong directions

In the background pop3 mail sync kept working for 3 mailboxes
Activesync with certificates did some synchronising, very slow but working

Then I started the camera, made a picture and send it via MMS, with made it nescessary to show pictures to choose from, load the contactlist with > 200 contacts and send it via GPRS.

On the next synch my pop3 mail said there was a mail incoming (the MMS photo) wich i could look at with the pictureviewer.

Meanwhile I set up a call with my voicemail.

During the entire test, TT and IGO and OZI kept doing there job. All functions stayed at an acceptable performance, no hickups, no restarts nescessary.

And after that hour still 12% battery power remaining.

PS: The dog got some attention to offcource :D

[simonsalo]

Wow! Just started using Tuma 1.3 - fantastic! Originally used maimach rom, then Artz, this one is the fastest yet and the most comprehensively filled with features - from a flight mode that works and turns off the LED to a notepad so we can edit EXTROM config file 'on board'. There is also more storage because so much is in the ROM & a temp disk with yet another 30mb or so - amazing!

Congradulations - it seems hard to understand what more you can fit into 1.5? Ironically it is the BT fix that we all need. I cannot even run GPS & the hands free at the same time which is annoying.

OK so here come the questions:

What can we use the temp disk for? Can we load programs here?

One of the soft key applets allows you to select a tab. What is this for?

How do you use SIM messages?

Can we set up Pocket FTP to look at the xda developers FTP server? If so, how?

I have uploaded two cab files from 140 & 142 se2003 roms for blackberry usage and upgraded the versions in case anyone wants to load these in WM 5 on a BA.

I would love to use blackberry on my BA here in Australia as this application was not made available for Australian usage. However it needs to point at the server - srp.blackberry.net.au instead of the UK server, but there is no provision to change the blackberry server in either of the supplied applications. ANy ideas?

I am offering $100 US to anyone that can get this blackberry application working in Australia on a PH20 BA XDA IIs running Tuma 1.3 WM5 & above.

I have also uploaded to the FTP root directory the O2 Active Today plug in from 1.40.242 ROM. Would be great if we could customize the menu settings. Any ideas?? Sorry I couldn't attach it to this post but it wouldn't let me, but it is in the route directory on the ftp site...

Again, congradulations on a job very well done!

Regards,
Simon jacobs

[wzaatar]

I have uploaded two cab files from 140 & 142 se2003 roms for blackberry usage and upgraded the versions in case anyone wants to load these in WM 5 on a BA.

I would love to use blackberry on my BA here in Australia as this application was not made available for Australian usage. However it needs to point at the server - srp.blackberry.net.au instead of the UK server, but there is no provision to change the blackberry server in either of the supplied applications. ANy ideas?

I am offering $100 US to anyone that can get this blackberry application working in Australia on a PH20 BA XDA IIs running Tuma 1.3 WM5 & above.


Hi Simon,

Try this:

1. Extract the BBConnect_HTC_PocketPC_TMO_...CAB files using WinRAR or a compatible extractor.
2. Using a HEX editor, open the file BBREG~1.007
3. Replace all occurences of '2 0 6 . 5 1 . 2 6 . 1 8 9' with the following: '2 0 3 . 5 5 . 5 1 . 1 7 7'
4. Replace the modified BBREG~1.007 back in the CAB and try installing.

I couldn't test this: My Imate is dead and I posted a request for help but no one seems to have a fix for it, so I guess you have to try it.

Oh, and if it works... Please donate the $100 to xda-developers.

Cheers,

Wadih.

[mr_ding]

Some Games which can while away the time ...

Download from:

ftp://xda:xda@ftp.xda-developers.com/Uploads/BlueAngel/WM5_TuMa/TuMa_Games.rar

Fun, fun, fun!

Any more game pack for Tuma?

[yacyd]

Why is activesync so slow???? did anyone have a patch.

[imatrix]

hey guys,

is there a tutorial or program out there help to change the wm5 boot logo.
i know Tuatara has released it before. but i could not find it in the forum.

any help is appreciated.

imatrix

[Tuatara]

hey guys,

is there a tutorial or program out there help to change the wm5 boot logo.
i know Tuatara has released it before. but i could not find it in the forum.

any help is appreciated.

imatrix

Check out the details in this very thread! :-) (just back a page)

Key part is here ...
http://forum.xda-developers.com/viewtopic.php?p=291738#291738

[simonsalo]

[quote]
Hi Simon,

Try this:

1. Extract the BBConnect_HTC_PocketPC_TMO_...CAB files using WinRAR or a compatible extractor.
2. Using a HEX editor, open the file BBREG~1.007
3. Replace all occurences of '2 0 6 . 5 1 . 2 6 . 1 8 9' with the following: '2 0 3 . 5 5 . 5 1 . 1 7 7'
4. Replace the modified BBREG~1.007 back in the CAB and try installing.

I couldn't test this: My Imate is dead and I posted a request for help but no one seems to have a fix for it, so I guess you have to try it.

Oh, and if it works... Please donate the $100 to xda-developers.

Cheers,

Wadih.

OK I have changed the IP in the file you mention, but how do I now get the file back into the cab??!!

Simon

[imatrix]

Hey Tuatara,

does the logo have to be 8bit?

thanks,

imatrix

[TauRho]

....i can't find it? where's the zip file???
halpme!

[Tuatara]

Hey Tuatara,

does the logo have to be 8bit?

thanks,

imatrix

Yes, for the bootlogo it does need to be 8-bit. To verify that you've got it right, just check that the filesize is the same. If it is - then you have the right format for it.

[xsi]

Any news?

[thebombs12]

I loaded TuMa's v. 1.4 rom and it indeed is buggy but I love the new features and preloaded apps on there. I'm glad 1.5 is in the works! Take your time and thanks for the great release!

[baeshin81]

@Tuarara
Based on everyone wanting their own version of Windows as well as issues with software, will you be releasing a clean version of your Windows Mobile 2005 for those who want to install their own software?

I was hoping to use your base software and able to install items such as Microsoft Voice Command without having issues with other voice software or other software I won't be using?

Although the package was very nice, I have gone back and forth about Tuma and Ivan Versions due to this software issue...???

Thanks for all your hard work. I loved Tuma 1.3 but wanted to try a clean version who of course was faster because less bulk in software. Your version of Windows definately had more spunk in it! Just didn't need all of it. :lol:

[Chrischi]

Hi
I'm still using Tumas 1.4-Version. This version has several problems, but I can use it for my needs and keep looking on the WiFi:
When WiFi is enabled, then I've to take care, that I disable it manually. If the BA powers off automaticly or will be powered off manually, while WiFi is running, problems will occour after working again with the device.
I think, that the BA is very stable, if I'll take care about WiFi.
Since I installed bigmike's bthuart.dll also Bluetooth is working without the disabling-failure - big thanks to bigmike.

Then I removed some links in the startup-Folder (Camera, Init Tray, Screen Rotate, ShutXP and vBar). I also installed the a new version of batti (first cleaning up registry). But I wasn't able to remove the old batti-files (placed in rom). Perhaps anybody knows how to remove it?

When setting up the BA, it's important to prevent fast rebootings by a program. I looked to reboot manually (power off, wait and then reboot).

Thanks for your work

Chris

[Gudvin]

Greetings to all!
Glad to join to such a great community :)

I am sorry, but looks i've found solution for my question....
Yup, right here in the forum... 8(
here it is http://forum.xda-developers.com/viewtopic.php?t=45272

Cheers,
Gudvin.

P.S. impatient with 1.5 :) want to use album to see images....

[khsaleh]

Hello Every one
please i need a help with this rom ver i installed it but the camere is not working and each time i restat an error message appears to me (The file camera_Detect cannot be opened. either it's not signed with a trusted certificats or one of it's components cannot be found...)
please advice what to do

[_TB_TB_]

Read this: "TuMa v1.4 - BETA - WM5 ROM (RELEASED ... but has problems)" - do not use 1.4, get 1.3 instead (or wait for 1.5 ;) )

[SpikeyMonkey]

hey guys the bootlogo.exe doesnt work.... it shows my image sure.... but it shows it after the 4colours and after the wm5logo......is there anyway to get it to show instead of the 4colours??

[rauld28]

Great rom TuMa keep up the good work!
I like the look and the programs.
But i did got some anoyng bugs.
1. I noticed Wifi to be a mutch slower (8kbiti/s or less) the the org rom ( i got Ita vodafon ver) and i was in like 10 metters of Acces Point.
2. I did got some delay wen i answer phone calls i press the answer button and i can hear and speek afther a second or to!
3. Afther about 3 days of using my radio rom was gone and thus my phone did not work anymore.
4. It seems to be mutch more slower then the 2003se.

Bun over all i like it a lot. I can't w8 4 1.5

I now have latest 2003se in eng i will try your rom again and come back with more feedback!

[sayadil]

i can't get the boot logo to work either... as per my understanding the three files in the zip had to be copied to the windows directory... i did that but to no advantage. i don't get anything on startup except the 4 colors..
if anything has to be done to the registry file... before pasting it to windows directory (phone)... pls advice me.

[sayadil]

Posted: Sat May 20, 2006 22:51


--------------------------------------------------------------------------------

Quote:
Boot screen is a 'special feature' addition for TuMa v1.4. It was to try and comfort people with a nice boot screen since everyone panics with the colour bars. TuMa v1.4 was also designed to be a 'feature rich' out of the box solution ... but the feedback I've had has been to go the other direction.

Anyways ... if you want to have the bootscreen in ANY other ROM, all you need to do is the following:

You'll find the application and TuMa v1.4 Bootlogo attached in the ZIP.

To make it run at startup, just include the following registry entries, and place the files from the ZIP in /Windows directory.

Code:

[HKEY_LOCAL_MACHINE\init]
"Depend32"=hex:14,00,1E,00
"Launch32"="BootLogo.exe"



Once you've done that - any of the other CABs I created can then be used, or just replace the BootLogo.bmp file. You will need to ensure that the BMP file is in the SAME format as the example. 8 bpp, and same file size & resolution if you want to change it. That's all that is required.


so short explaination:
1. Make a BootLogo.bmp or use default WM5
2. Copy BootLogo.exe and BootLogo.bmp to \Windows
3. Crete these registry entryes into registry
4. Reboot


how do i do step 3 ... how do i create registry into registry as there r no steps mentioned.. pls advice.