yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] parleyp:
But I haven't been giving many bugs to find lately...ok...release time for Phoenix...tonight.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lufc:
Downloading now will let you know later tonight how it goes :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pastorphil:
Love to try

I would love to test your new ROM Count me in :cool::cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jax_boater:
Downloaded a few hours ago. Leaving this a.m. for work travel. Will try to load this evening. If not tonight then this weekend. Will advise.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kaiserII101:
sorry for the long delay all:o I had a project that I did on Fri & Sat. and then as my luck would have it our internet slowed down down to a crawl on Sun and Mon so it wasn't even reasonable to upload then. It sped back up today though so I uploaded the new version. The password is the same http://www.mediafire.com/?ynznywynytz

P.S. There is a new bug that doesn't allow you to place shortcuts in HTC home :x although all the settings shortcut files are there (thanks to parleyp ;) )
[G1 General] fastwanabe:
Looking for the actual circuit board that sits underneath the keyboard. Ive googled it but nothing. Thanks for any help.
[G1 General] fastwanabe:
well after some more searching I found one sit but its so dam expensive... not even free shipping. I guess I have to use the OSK from cupcake till I can find the part cheaper.

for any body else here where i found it.

http://www.iphonerepairparts.com/products.php?cat=513
[Touch Cruise ROM Development] adderz91:
​

Please note the camera does not yet work, im uploading in the hope that an experienced cook will lend a hand and help me overcome the camera issue.

I would be willing to make a donation if someone can fix the issue, and i will include their name on the splash screen as well.​

Download Links:

ROM Download Link

(Remember the camera doesnt work yet)

Keyboard Skin Download Link​

Main Feature

The main feature of this ROM is to "unite" all the programs. With the help of HTCtoucher im skinning some Windows components as well as some third party apps.

Thanks to:

HTCtoucher for 95% of the graphics and skins, hes incredibly talented, please visit his page and send him a donation for his hard work :-)

C_Shekha for his ROM. Its been alot of fun learning, frustrating too :-P

A_C for his S2U2 and S2P apps A_C's Website

Quentin Pouplard for his PocketCM COntact and Keyboard Apps PocketCM Website

Install procedure:

Due to the fact this ROM contains extensive theming and theres only so much cab editing i can do, there are a couple of little things you will need to do.

1. To enable PCMcontact skin go into it, hold down the "phone" icon, select "options" and select the "htctoucher gloss v4" theme from the drop down list.

2. To enable the PCM Keyboard skin download the .skin file. Copy it to the PCMKeybard folder in My programs. Then select the keyboard in sms or whatever, hold down the enter button, glide across to options and select "gloss smaller" as your theme, it will take a few seconds to load.

3. Radio 1.58.x is recommended

Included in Rom:

Manila Skin

Comm Manager skin

Opera Splash

Audio Manager

Fingermenu + skin

"All programs" skin

Calculator + skin

Startup Images

Dialer

Quickgps + Skin

S2P + Skin

S2U2 + Skin

PocketCM keyboard + Skin

PocketCM Contact + Skin

To do list for next release:

Finish Dialer graphics

Camera

Call History graphics

Fix PCM contact graphics glitch

Fix s2u2 graphics glitch when charging

Start Menu graphics

Add programs (browser?)

Volume background graphics

Sound profile graphics

Change Log

Beta 0.1 released

Beta 0.2 released
Updated drivers to 1.60 (increased program memory)
[Touch Cruise ROM Development] sanity65:
wow! that's looked great! when can we try it?
[Touch Cruise ROM Development] JeFFJuH:
I like it :)
[Touch Cruise ROM Development] 02xda2:
;) Hi addrez91,

Just waiting .. Take your own time.. Please do not rush things, we can wait for a good ROM and will wait.
[Touch Cruise ROM Development] Swifty:
Looks really nice, will be testing this out when its released.

Thanks for your effort ;)
[Touch Cruise ROM Development] adderz91:
Ill be releasing it in a couple of days.

It was based on C_shekas rom but im having a few issues. I cant get the camera to work at all which is a bit of a problem lol.

Anyway im going to start afresh on a clean rom so it should give me more program memory and less issues cropping up.

As it stands based on C_shekas rom, i like it. Its quite fast.

My internet speed has been cut to 32kb/s...yes im not kidding you. Australian ISP's are bastards. My maximum download speed it 3kb so it would take me a week to upload the 100mb rom. Thankfully it will be reset on the 18th back to normal speed.
[Touch Cruise ROM Development] tempme:
I like it, waiting for first release to flash :)
[Touch Cruise ROM Development] sagytb:
Please add video calls to this release.
[Touch Cruise ROM Development] djmattm:
Wow!!!!!!!! Amazing!! I want it:p:p:p:
[Touch Cruise ROM Development] adderz91:
Video calls will have to be for the next release.

Its possible, but the png files have to be edited one by one and theres lots....
[Touch Cruise ROM Development] sagytb:
Thanks for the effort, if I can help with the editing i will be happy...

Thanks.
[Touch Cruise ROM Development] alinescoo:
This ROM looks great. I always look for skins and stuff but I can never make my Polaris look the way I want. This ROM could make a difference. Grat job. Looking forward.
[Touch Cruise ROM Development] reyradi:
Great look , if Mr. Shekhar work on it , it will be a very good rom, the graphics are very cool, waiting to flash :cool:
[Touch Cruise ROM Development] adderz91:
Well ive managed to delete the Manila program shortcuts in the programs menu, and ive also managed to change the date on the home tab to white, ive also managed to change the left softkey to "phone" instead of the broken "new" link.

I had to revert the dialer back to the original one because you couldnt adjust the in call volume for what ever reason. In saying that, i have skinned some files so it will look pretty much the same. There are alot of dialer pngs to be skinned and ive done just the most basic ones, with the rest coming in due time.

Ive managed to fix the PCM keyboard bug which showed a line of distorted graphics, unfortunately it has introduced another bug. The W key has no label...its just a blank button lol.Manually inserting the .skin files however displays no issues. Ive investigated it and when i edit the cab and put in the .skin files they drop a kb...and when extracted the w png becomes unusable. Why? i have no idea...

The only problem left to fix before i release is the non working camera, this could be related to my radio however, i will download a new radio later tonight when my internet is abck to normal and test.
[Touch Cruise ROM Development] alinescoo:
May I suggest a program addition ? I really like Opera Mini for day by day browsing. It's much faster and easyer to use than Opera Mobile. Of course Opera mobile still remains. Skyfire, latest v9 beta also is verry interesting. It's pretty fast in showing streaming media. It could be usefull also an wifi on/off toggeler shortcut in Programs folder, so if anybody want's to use it can add it into manilla programs.

Great work. Looking forward into flashing it. Does it include Footprints ? I just wonder, if there are tabs dezactivated in Manilla, the RAM memory used remaind the same or is lowered ? I've been using Radio 1.58.32.33 with ROMs having 1.6 driver and Camera is working fine.
[Touch Cruise ROM Development] adderz91:
Ill add more programs in the next release but for now i might just leave it just Opera.

Ive reskinned the Calculator and i think it looks pretty good, matches the same buttons as the Dialer.

Still havent been able to download the new radio to see if it fixes the camera but in 2 hours exactly i will download a see, and if the camera works ill be uploading the rom.

Ill have to update the front page images to reflect the changes ive made.
[Touch Cruise ROM Development] dortyboy:
what is the memory like. because most roms loaded with eveything just runs slow. nice and slow
[Touch Cruise ROM Development] adderz91:
Memory isnt *that* bad, hangs around 35mb. Plenty for me at any rate but not sure about others.

Ive tried a new radio but the camera STILL doesnt work. This is starting to piss me off lol.

Ive tried different camera modules from different roms and still nothing. Im going to try installing the original rom and see.

*sigh*
[Touch Cruise ROM Development] adderz91:
Well im officially calling for some help lol.

I just cant get this the camera working, ive tried different file sets and none will work and i dont know why.

I think it *might* have something to do with the 3D drivers.

Im using UDK's kitchen and i dumped C_shekas OEM and SYS folders straight into it. I think the 3d drivers are still included somehow because i have a total of 84mb of program memory when simply using C_shekhas rom i have a little over 100mb.

If anyone could point me in the right direction that would be incredibly helpful because i dont want to release it without the camera working...

Whenever i open the camera it states "Unable to initialize camera. Failed to set up the camera device.

Its not the radio as ive tried both 1.58 and 1.59. SO im just stumped.
[Touch Cruise ROM Development] chavonbravo:
Do you have all dependencies for the camera there? I know it requires mHub (not same as mHubVO) and possible other things.
[Touch Cruise ROM Development] EZengin:
"Unable to initialize camera. Failed to set up the camera device.

Try with both following files:

Polaris Radio 1.64.08.21

http://depositfiles.com/files/4306606

HTC.Album.1.0.1030.720

http://rapidshare.com/files/74055736/HTC.Album.1.0.1030.720.cab

It's not the problemn with the 3D drivers, but with the driver that's activate both the camera in combination with the Radio ROM and the Album

Rgds

EZengin
[Touch Cruise ROM Development] EZengin:
"Unable to initialize camera. Failed to set up the camera device.

Try with both following files:

Polaris Radio 1.64.08.21

http://depositfiles.com/files/4306606

HTC.Album.1.0.1030.720

http://rapidshare.com/files/74055736...0.1030.720.cab

It's not the problemn with the 3D drivers, but with the driver that's activate both the camera in combination with the Radio ROM and the Album

Rgds

EZengin
[Touch Cruise ROM Development] adderz91:
Thanks for the tips, unfortunetly im still unable to get it working. Id be happy to check out any other leads people might have on the issue :-)

Im gonna try a different tactic and see what happens tonight.
[Touch Cruise ROM Development] pcarvalho:
what oem drivers are you using? check that 1st...its not 3d drivers...if you have 84mb free its 3.13 up if its 100mb its 1.60 down...so XIP and OEM have to be the same...your either forgeting something or coping something over that you must not...
[Touch Cruise ROM Development] adderz91:
Yep thats what im trying now. To dump the XIP from C_shekhas rom. But im still learning all the ropes and dumping the XIP is a real b*tch.

I found this tool that might work but ive had to register to download it, and the confirmation email hasnt come through AHHH!!!

Ive discovered the XIP lies within the .payload file, but it goes into hex editing which just confuses me :-P

i just want a tool i can put it into and out pops the XIP :-P

well ive read you can extract it with msflashtool which then splits the .nb file into parts, and then you can rename the appropriate file to xip.bin, then extract it with xiport...

that email still hasnt gone through, i tried searching all over but no one else had it.
[Touch Cruise ROM Development] prorak:
link download?

Link download?
[Touch Cruise ROM Development] pcarvalho:
all the tools you'll ever need are in this forum ;)
[Touch Cruise ROM Development] adderz91:
Well i had to download two kitchens to finallly find msflashtool.exe...and what was the result? nothing lol

got the error "the file is not msflsh50 format"

*sigh*

i remember seeing a thread by M-aime about XIP porting. i must check that out again.
[Touch Cruise ROM Development] adderz91:
This is hurting my brain.

Ive tried 3 different tools to try and extract the XIP and they all end up with errors.

The closest i came was when i renamed the .payload file to OS.nb and used that, but instead of boot.rgu it contained boot.hv and it was 44kb not 30kb.

I'm going to scream really really loud, really really soon :-P
[Touch Cruise ROM Development] pcarvalho:
extract boot.rgu from boot.hv...and read a bit more on how to cook a ROM :)
[Touch Cruise ROM Development] adderz91:
Im going to release this rom, im uploading now.

Im doing this in the hope that an experienced cook will lend a hand and help me overcome the camera issue.

I would be willing to make a donation if someone can fix the issue, and i will include their name on the splash screen as well.

As far as i know, everything else works on this ROM and im very happy with it.
[Touch Cruise ROM Development] 02xda2:
Hi,

Thanks for a nice release. It looks like though you have used master Shekar's Rom 'bCS' (1.60) you have used 3.13 drivers. There seems to be some inconsistency with the drivers and the camera application. 'Mix & Match problem'. If you use Nadavi's camera, camera works but without imaging. Try experimenting with a different set of drivers.
[Touch Cruise ROM Development] adderz91:
Hey yes i replaced the entire camera app with one extracted from another rom as one last try but the same message is still displayed.

When we work out why the camera isnt working ill revert back to the original camera app.

Yes the 3d drivers are still included but i ont understand why, i replaced the OEM and SYS folders with C_shekhas, i assumed the 3D drivers would of been in the sys folder.

But alas, the available program memory went down to 84mb which indicates 3D drivers are still there.

How do i remove them?

Are they related to the XIP?

This issue is frustrating me, i cant count how many times ived flashed this rom, my poor polaris :-P
[Touch Cruise ROM Development] 02xda2:
Hey could you look at this thread please http://xdaforums.com/showthread.php?t=296861
[Touch Cruise ROM Development] chavonbravo:
Adderz91, what rom did you extract the camera app from? Is it from another device? If it is, it should be msm based device, not omap. Also, you'd need to use HTCCamera1.dll and NULLCAM.dll from whatever other device rom you got it from (in oemdrivers). If I were you though, I'd stick with the stock polaris camera, so you don't have any issues such as autofocus not working or it being zoomed in too much, etc. Also, you need to make sure the dependencies for the camera app are there. Newer cameras from other devices use mHubVO, but the original polaris camera needs mHub.

As for you having only 84mb of ram, this is due to nk.exe in XIP. If you used 1.xx drivers, you'd need to use the XIP that go along with it. If you use 3.xx drivers, you need to use the XIP that went with that one. You shouldn't mix and match. It has nothing to do with 3d drivers.
[Touch Cruise ROM Development] 02xda2:
:D At last a master speaks, hope your troubles are over now Addrez91. Can we wait for a stable and complete release now?
[Touch Cruise ROM Development] adderz91:
Thanks chavon and 02xda2 for your help, much appreciated.

Changing the xip seems to be the most difficult part of all but im slowly getting there. Ive managed to dump the xip.bin from C_shekhas rom and i have a boot.hv but no boot .rgu which is a little frustrating. And according to another helpful cook i also need the coredll.dll and the 723.rgu file which the dumped XIP has. Apparently i have to extract the boot.rgu from the boot.hv but im yet to find a way how.

I had a feeling it was probably the XIP a couple of days ago and googled for hours, but there is a distinct lack of information, i had to piece little bits from here and there just to finally dump the .bin file.

There is also a OS.nb.payload file within the XIP folder in UDK's kitchen, which is around 8mb, im not sure wether this needs to be replaced.

Regarding the different camera it was extracted from a cooked polaris rom, i only tried it *just to be sure* but i will replace the original camera and drivers.

So hopefully there will be a 100% working release soon, i wanna get back to skinning things, i own macs so everything is in the looks! lol

Thanks for your help guys!
[Touch Cruise ROM Development] adderz91:
Well thanks to everyones help and input ive successfully fixed the driver issue.

We are now running the 1.60 drivers as it should, and program memory has gone up from around 36mb to 50mb.

Whoop whoop!

Unfortunetly the camera still doesnt work...but still...we're getting somewhere.

I tried including a package of mhub but it kept stopping because of duplicate files, indicating its already included in the rom. I also included an MhubVO package but still nothing.

Tried installing different cameras and albums via cab and still nothing.

urgh.

EDIT: Updated to beta 0.2 which includes the proper 1.60 drivers.

So any more ideas on the whole camera issue anyone? :-)
[Touch Cruise ROM Development] adderz91:
Well it seems whatever ROM I dump, the camera seems not to work.

Whenever i build a rom thats ALREADY been dumped or flash another ROM from another member straight away the camera works.

Im following UDK's instructions to the T so i dont know what the problem is. *frustration*

the xip is right, mhub and dshow are already in there, the radio is right, the drivers are right yet it JUST WONT BLOODY WORK.
[Touch Cruise ROM Development] bally3:
Shekkar, epimazzo and m-amine are your guides to enlightenment to the oriental mysteries of cooking my troubled friend

I am sure they will assist you if you ask them nicely. :)
[Touch Cruise ROM Development] chavonbravo:
Here's the OEM package I made for my kitchen for the original polaris camera. Hope it helps.
[Touch Cruise ROM Development] adderz91:
Thanks for your help, unfortunetly, although the .exe is there, it wont load, not even upto the "cannot initialize camera" error.

I will check its registry file for any in-congruencies.
[Touch Cruise ROM Development] pepo80:
Looks great!!! (real amazing style)

I hope you resolve camera problem...
[Touch Cruise ROM Development] adderz91:
Hey thanks, unfortunately i gave up on trying to fix the camera error. Ill leave the rom building up to more talented cooks.

There is so much work involved in cooking a rom i dont think people realize until they try it themselves.
[XPERIA X1 General] michaelthemage:
Since I have now R2A Generic_UK I get the following error when sending EMAIL, SMS, etc.

the Error pops up: Messaging does not recognize the address, its either invalid or ..... want to send anyways///

After that I press anyways and it goes out. But this is just not right. Anybody has the same or knows what this is? Firmware bug or something with the Outlook sync?

And of course, anybody knows how to resolve this?

Thanks

PS

This happens with addresses that are in the phone/address book and ones that are just put in the send field and are not in the book!
[XPERIA X1 General] yahya.hamid:
SMS Recepeient not Recognized

I have the same problem with Xperia. It happened after i installed the update from Sonyerisson. Initially I thought it was a problem with SMS security software i had installed. However uninstalling did not help.

Anbody, any ideas?

thanks
[Touch HD Accessories] Q2V:
Hi,

I have to use two screen protectors for my HTC HD, because i wrong to put it on the screen, so i decided dont use any screen protector.

Pls, tell me why we need to use a screen protector?, Very expensive PPC like HTC HD is make from poor material need to be protect?
[Touch HD Accessories] eaglesteve:
Of course you need it. Unless you want your screen scratched, and believe me it will without a protector, especially if you use your finger nail to tap on the screen. Even more expensive devices will scratch without taking proper care.
[Touch HD Accessories] linksix:
Have to agree with eaglesteve - exactly the same reason Photographers use a UV filter or the like on lenses, even though moderm coatings pretty much don't need it - its easier and way cheaper to replace a filter or screen protector than it is to replace a front element or touchscreen.
[Touch HD Accessories] dazza9075:
it will scratch, almost anything will scratch if miss used, its a fact, but by all means, dont stick a protector on, just be real carfull, in fact best not touch it at all.
[XPERIA X1 General] c_legaspi:
i installed the touch keyboard. i like it but it kind of makes my sliding keyboard limiting (symbol and ae button dont workk).

i would like a keyboard hardware button for an underscore, do you think this is possible with ae button plus?
[Touch Diamond, MDA Compact IV Themes and Apps] d12bn:
I'm trying the iphone theme and wondering how to setup the weather and is there a better option for weather using Throttle Launcher iphone theme?

Does it show a forecast?

Also can you change the buttons/icons on the home page?

Thanks
[General Questions and Answers] rob87:
soo im still a big noob been so busy with work and ****! ive downloaded a few themes and they are .tsk files.. my question is where to i put them!?!?!

thanks
[General Questions and Answers] nir36:
you can put them in your windows folder or in the root folder of your storage card

then go to start/settings/today and choose your theme
[Windows Mobile Development and Hacking General] gbm85:
OK, you guys have talked, and I have listened. Introducing a complete re-write of LocateCaller!

Release Candidate 2

* Works with HTC Phone Canvas!! (below screenshot is with Phone Canvas running)

* Fix Answer/Ignore softkeys not working sometimes

Release Candidate 1

* Fix caller info for call waiting

* Don't show in running programs after reboot

* Code cleanup

* Feature freeze for 2.0 release

* Will go Gold if no bugs are found

Beta 4

* Fix crash when called from known contact without picture

* Fix phantom "Answer" and "Ignore" keys on boot

Beta 3

* Fix crash when called from blocked number

Beta 2

* Fix exception when phone number is preceded by a 1

* Full-size caller picture

LocateCaller2 Beta 1

* iCaller completely gone! This is now a stand-alone app

* Call waiting ID now working

* No configuration necessary

What is LocateCaller2?

LocateCaller2 will show the area an incoming call originated from based on the area code. It currently works for US and Canada numbers. All information is self-contained. No data connection is used.

Beta 1 Screenshot

Installation

* Uninstall old LocateCaller if necessary

* If you have a third-party caller ID program, disable it.

* Install the attached CAB

* Soft reset

Tested on QVGA emulator, VGA emulator, and my Touch Pro.

Planned features

Optional Slide2Answer-type functionality

Option for non-fullscreen (i.e. default style) window

Technical Details

* Requires WM5+ and .NET CF 2.0+

* Written in VB.NET

* ~70kb CAB, 450kb memory usage

I have spent a decent amount of time rewriting this in order to implement requested features. If you would like to thank me, please consider buying me a coffee.
[Windows Mobile Development and Hacking General] sids911:
Wow! Good.....

This will definitely be on my phone once it starts using phone canvas!

Thanks for the effort!
[Windows Mobile Development and Hacking General] arcsvibe:
Looks great! Silly question but does it use data? Sorry for the noob question!
[Windows Mobile Development and Hacking General] tazzix:
Great app, is it possible to supply XML or text files with prefixes to supply custom text so that people in other countries can also use this app with other configurations. E.g. here in Pakistan we can not only identify the locations but also for most numbers can identify the network the person is using I have all the info but I am too lazy to write my own app and it does not make sense that the same app is re-invented by too many people if we could do it with configuration files. Thanks and best regards.