yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 ROM Development] vipperdiver:
Hi again guys.

I'm not getting receive files by IR.

Beam is on. I already try turn on BT too, but don't works.

Any help or idea?

Thanks.

Note: I can send files by IR, only not receiving.
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
I can confirm this issue as well. I think that 28008 had a similar issue as well.

@d-two,

Have you thought about maybe rolling back the IrDA package to an earlier build? Keep in mind that since most of the latest device are not equipped with IR ports, M$ may be slacking off on the development of these. Just a thought.
[MDA III, XDA III, PDA2k, 9090 ROM Development] alangordon73:
Okay tried this ROM as was running XPLODES last ROM with an older version of Manilla. I like the 6.1 Manilla ROM and the fact the keyboard works wonderfully. :O)

I however hate the fact that there is no analogue clock.

Is the analogue clock part of the ROM or the Manilla skin?

Speaking of the skin I have had trouble updating and I do not recall having problems in the past.

Perhaps I am doing something silly?
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
Use M2DC. With it, you can change the clock from Analog to Digital (and back). The clock is part of Manila and not the rom itself.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
Can you check IR in the 21888 Rom ? Then port it in 28205 :D
[MDA III, XDA III, PDA2k, 9090 ROM Development] alangordon73:
Looks like it may be an issue with the ROM rather than the Manila 2D builds (tried TSparks Manila 2D 1.00 1911.1733) as I reflashed with 6.1+Manila and still no analogue clock is displayed, tried another skin WM7 which I know is good with Explodes last ROM builds; again no joy and then went back to TSparks Manilla again with no joy. So in short I know the TSparks Manilla and the WM7 skin are good on earlier ROMS so it looks like a bug in the ROM.
[MDA III, XDA III, PDA2k, 9090 ROM Development] Araviel:
Hi, in advance thanks for this release !

Ive installed in first the WM6.5 build 21888, but i'm trying now to install the wm6.1 + manila but at the boot the 4 coloured lines are stuck with the 3 versions wrote in red.

I can downgrade like that ?
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
I believe that the analog clock was removed in later versions of M2D. TSparks only has skins for Manila (he has not developed a version of the program). If your skin is meant for earlier versions, they might not work on newer ones. The rom has nothing to do with Manila. You are simply using (or trying to use) a skin that is not meant for that version.
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
Did you get 21888 to work or did it just get stuck on the screen that you are describing? If your answer is "no", then you did not unlock the device before upgrading. If that is the case, you need to go here and read the whole tutorial.

Good luck!
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
I could probably flash to 21888 test, but what do you mean by "then port it in 28205"? I guess I can dump your 28205, replace the IR module/file and lang package, and then recook it. Is that what you are suggesting?
[MDA III, XDA III, PDA2k, 9090 ROM Development] vipperdiver:
Hi folks..

D-two, are you active again?? Cooking roms???

And our project about a PT-BR Rom version? Send me a PM or e-mail with more details. Let's start this project. Please.

Thanks.
[MDA III, XDA III, PDA2k, 9090 ROM Development] Araviel:
WM6.5 build 21888 works fine but wm6.1 not at all :/

Ive a small intern disk space and I think its better too install an 6.1 clean with manila ^^
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
Can you explain why 6.1 is not working? What is it that does not work?

Manila occupies a tremendous amount of space and it cannot be installed to SD. This is not an issue for newer devices, but the BA has very limited internal storage, so you have to be willing to sacrifice this internal storage if you want Manila on your 6.5.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
ROM Update (23529)
[MDA III, XDA III, PDA2k, 9090 ROM Development] alangordon73:
Thanks for the posts regarding the skins and analogue clock. I thought at first it was an issue with M2DC not being compatible with the hardcoded Manila.

What I'm now seeing on any attempt at reskinning (even manually) is the digital clock area becoming corrupt - background & number positions are not where they are expected to be. I'm postive I have the respective skins for the Manila version.

So if we cant reskin this can we have a 6.1 ROM without the hardcoded Manila in order that an earlier version can be used?
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
You are welcome. Check into the Dev and Hacking section since you have quite a few threads with skins for M2D. As for a 6.1 with no M2D cooked in, that would be a question for d-two since he is the one with the kitchen here :)
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
Will try 23529 later...

It is supposed to be a little more stable than 23519 (from what I understand anyways)

Thanks...
[MDA III, XDA III, PDA2k, 9090 ROM Development] vipperdiver:
Hi D-two

Any correction about IRDA??

And you don't answear me about PT-BR Rom... I'm waiting your answear...

Thanks a lot..
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
I didn't change anything on IRDA!

Actually it's to much work - as you've maybe seen I didn't create a new Spanish rom. It already takes a lot of my free time to work with the German and English roms. Maybe later... Sorry!
[MDA III, XDA III, PDA2k, 9090 ROM Development] alangordon73:
Hi

I finally installed build 21888 and then used an older version of M2D and I've got my clock back.

I'll try and update the individual items such as HTC album yada yada...

What I have noticed on this build is that I have no GPRS Icon and I cannot connect to Facebook (Even when GPRS is connected) using either Facebook_v1.0.0.7p.CAB or Facebook 1.1.0.14.cab, However Google Maps, IE, Messenger all connect with no issues.
[MDA III, XDA III, PDA2k, 9090 ROM Development] egalus:
I am using 6.1 + manila atm - really great ui, but is there any way to make hardware keyboard inputs work in address line in opera? For me it seems like hitting any key will always result in reloading the current page.
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
Have not experienced that.... sorry.
[MDA III, XDA III, PDA2k, 9090 ROM Development] Araviel:
I'm trying to set this theme for manila but it seems not work : i dont have the clock in home tab, calandar and date are not set correctly

xdaforums.com/showthread.php?t=578700[/url]

I'm running the 6.1 with manila integrated. How can I install it ?
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
You can't. This theme is meant for a newer version of M2D than what you currently have.
[Touch Diamond, MDA Compact IV General] Deonix:
I'm a bit out of space on my Diamond with only 14. Mb of memory on the Main memory so i got tired of receiving Low memory notifications every 30 seconds whenever i browsed the internet ,so i went and looked what can be deleted and found under :My Device/Windows- a Tom Tom navigation install file 11.mb in size which must have been there since i got the phone .........which obviously i can't delete .

So my Question to you is what program should i use to delete that file and others (like PvP Player.exe which is useless....).
[Touch Diamond, MDA Compact IV General] djfuego:
Move Tomtom.

You should be able to run tomtom from storage. I copied to storage and run from there.

Shouldn't need to use the main memory storage for tomtom..
[Touch Diamond, MDA Compact IV General] Deonix:
Can't do that ,either the file is only copy/beam /send and it's stored as i said above . I can't cut it .

I WANT TO DELETE IT. please tell me a way/ or a program that can delete files from the Windows directory.
[Touch Diamond, MDA Compact IV General] Rudegar:
most files in windows dir are not located in storage but in the rom itself and can only be removed by cooking a custom rom but mind you storage space and rom space don't share MB's so freeing rom MBs don't add MBs to storage
[General Topics] NateReal:
is there a way to make a manila 2.5 for QVGA? or just an update with more features?
[General Topics] Reddog80p:
http://hothardware.com/News/Will-ATT-Lose-Their-iPhone-Exclusivity-On-Wednesday/
[myTouch 3G, Magic General] aidanbree:
I am trying to work out what is using all the memory on my Magic 32B. After rebooting I am left with only 15Mb which is causing it to run dog slow.

After rebooting I notice that apps I hardly use are running and consuming memory;

MP3 store, facebook, Tunewiki. Those together are using nearly 10Mb. Can I stop them running at startup?

What is the best application to use to manage RAM?

I cannot understand why there is so little RAM available? This device has 192MB? As I have moved my Apps2SD can I reallocate space from internal storage to be used as RAM?

How much free RAM should I be looking to have in order for the phone to run fast?

Should I be looking to use a Swap file? I have already moved by apps to SD...

Sorry if i am asking stupid questions. Relative Noob to Android
[myTouch 3G, Magic General] FoTwoZero:
First off, if you are rooted you should format your SDcard. Second of all what ROM are you using if your not running stock.
[myTouch 3G, Magic General] aidanbree:
I am running Cyanogen's current rom 4.2.13

I repartitioned my SD card to use App2SD. At that time I was able to reallocate space rather than format.

Cheers

Aidan
[myTouch 3G, Magic General] goff.caley:
Is there someone out there that may know where to download the Android 2.1 software? I would like to install it on my Mytouch, if thats possible... Correct me if I am wrong, but I should be able to just boot into CM's recovery console, and update it with the update.zip yes?
[myTouch 3G, Magic General] swissp:
Hi,

if you want to try 2.1, I'd suggest Manup456's ROM.

Be aware that a few things still don't work (read the ROM description for details).

and yes the flashing process is the same as usual :)
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
Hi,

After the success of the Diamond Version of this guide I decided to "BRING THE RAIN" over here!! I noticed a post about a rom having random hard resets so I knew my calling was up!!

After what happened in the Diamond thread with the Tourists Im going to try and remove all repeat questions BEFORE they get asked so READ THIS WARNING:

F.A.T.M.T.I.D.Q:

(Frequently Asked TOO Many Times Infuriating Damn Questions):

-------------------------------------------------------------------------

1: "After task 28, I get this output in MTTY: Total Bad Block in CE: x"

2: "After task 29, I get this output in MTTY:

ERASE block xxx FAIL !!!

ERASE block xxx FAIL !!!"

(where x is a random number)

This has been asked 100+ times in the Diamond thread so this is the final time I will answer:

IT MEANS NOTHING..NADA..ZIP! I have not experienced ANY problem with this output...Please stop asking!

-------------------------------------------------------------------------

As we all know MTTY is the key here, but I can say from personal experience that this small piece of software is a MASSIVE pain in the ass to get working, i must have tried 15-20 different “recommended” procedures to get it work and all failed.

But I managed to find a failsafe method of getting MTTY working on Vista AND Windows 7, also x86 AND x64!! (I have all 4 windows installations and the methods detailed below worked on all)

NOTE: WORKS WITHOUT DRIVER INSTALL ON XP

If for some reason you cannot got this to work on XP do the following: (Thanks kgerry!!)

Here is how this thread works:

Post 1: Description

Post 2: Driver Installation

Post 3: MTTY Instructions For FLASHING FROM INTERNAL STORAGE

Post 4: MTTY Instructions For FLASHING FROM YOU SYSTEM

THANKS to:

Reb0rn - for pointing me to the light!

l2tp - for the images

lunasea - for providing me with working drivers

and of course to anyone else I forgot.

I hope this helps people!!

MG

Donations

:

stokedanuk

Thanks VERY muchly!!!
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
Driver Installation

NOTE: Drivers only need installed ONCE. After this you can just connect in BOOTLOADER and use MTTY.

Pre-Cursor To Driver Installation – FOR EVERYONE (x64/x86 Vista/Win 7)

This will remove the need for users, x64 in particular, to use “Unsigned Drivers.” Also since in Vista SP2 (x64 & x86) they removed the “F8” options Completely!

Files Needed:

Driver Signature Enforcement Overrider

Remove Watermark V0.8

1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next

2: There will be a warning to REBOOT, Press “OK”

3: Go Back to Driver Signature Enforcement Overrider Select “Exit” then Click “Next”

4: REBOOT

5: Run the “Remove Watermark V0.8” for you OS type (x64 or x84)

6: In the Command Window type “Y” and wait for the process to complete

7: Once complete REBOOT your system and begin the driver install

NOTE: If you DO NOT complete the above, some users will need to press "F8" During Bootup - (ANOTHER NOTE FOR x64 USERS, EVERY TIME YOU NEED TO USE MTTY YOU MUST REBOOT YOUR COMPUTER, HIT F8 AND SELECT: "START WINDOWS WITHOUT DIGITALLY SIGNED DRIVER CHECK")

For Info See Post Below:

-----------------------------------------------------------------------

Big thanks to maybeme for providing a host for the images!!

1: Download the relevant drivers for your system attached to this post: these work for both Vista and Win7, all you have to choose is x86 or x64

EDIT: It has been found that with different versions of Windows 7 x64 need different Active Sync Drivers... If you are using Windows x64 please try x64 AS Drivers Win 7 Tested & Working.zip FIRST!!!

2: Connect Device to PC via Active Sync, Once Connected Uncheck USB Connections,DISCONNECT DEVICE then Reboot Computer

3: Bring device into bootloader (Reset + Hold Vol Down), This will show the Red, Blue, Green screen showing "Serial" - Once Computer booted, connect device in bootloader mode to USB, the word "Serial" will change to "USB"

4: Go to "Control Panel -> System -> Device Manager" and select Microsoft Usb Sync in Mobile Devices section (NOTE: This MAY say HTC USB Sync but as long as you select your device!!):

5: Right Click and Select "Properties" then go to Driver tab, then Select "Update Driver"

6: Choose to "Browse Computer For Driver" (the second option):

7: Select "Let Me Pick From A List...." (the second option):

8: Click "Have Disk":

9: Select the folder with downloaded driver From Step 1 and select "wceusbsh.inf" (this is the same file for x86 & x64):

10: You will get back to previous screen, then click Install

10a: WINDOWS 7 ONLY - The Below Warning will appear, Select "Install anyway":

11: The drivers will be successfully installed:

12: When you get back to "Driver Properties" check driver version. If the "Driver Date" has changed from 2nd step (2003 instead of 2007 - The year does not matter as long as it is not 2007!!), the installation has been a sucess:

13: Lastly leave the device connected and in "Bootloader" and reboot you system. Upon Rebooting an "Unknown Device" is installed, this is your HTC device.

Now the Active Sync Drivers are Installed
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
MTTY - Flashing From INTERNAL STORAGE

Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY

a: FULLY COMPLETE POST 1

b: Before you start grab: mtty1.42.zip

AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!

Procedure:

1: Download a ROM of your Choice, RENAME the *.nbh for your ROM to: LEOIMG.nbh

2: Copy LEOIMG.nbh to the "Storage Card" of your Device.

3: Bring device into bootloader (Reset + Hold Vol Down), at first your HD2 will attempt to flash the LEOIMG.nbh you just copied to your Storage Card, you will have 2 Options, Press Vol Down to CANCEL THE UPDATE!! (DO NOT FLASH NOW!!) after pressing Vol Down you will now see the Red, Blue, Green screen showing "Serial"

4: Connect device in bootloader mode to USB, the word "Serial" will change to "USB"

5: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1

6: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK

7: Run following commands:

7a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)

---------------------

MTTY OUTPUT:

---------------------

CMD>

---------------------

7b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:

---------------------

MTTY OUTPUT:

---------------------

Cmd>set 14 0

crc=0xD2C8DA7F.

HTCST ÚÈÒHTCE

Cmd>

---------------------

7c: type "task 29" to get your device formatted:

---------------------

MTTY OUTPUT:

---------------------

Cmd>task 29

Format BINFS start

Fill RSVD information for block 497 to 530

CE start start block=530, total block=3566

TAG NOT FOUND !!! NOT CLEAR STORAGE !!!

Format BINFS end

Cmd>

---------------------

7d: type "task 8" to ask your device reboot:

---------------------

MTTY OUTPUT:

---------------------

Cmd>task 8

Cmd>

---------------------

8: Immediately DISCONNECT your device and hold "Vol Down" to Initiate ROM Flash

9: After ROM flash Hard-reset (Pen Reset, then Press and Hold Vol Up and Vol Down) again, on completion "Press Vol Up To Boot" Is displayed, press "Vol Up" and allow the ROM to boot.
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
MTTY - Flashing From USB

Before you start:

a: FULLY COMPLETE POST 1

b: Before you start grab:mtty1.42.zip

AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!

Procedure:

1: Bring device into bootloader (Reset + Hold Vol Down), this will show the Red, Blue, Green screen showing "Serial" - Connect device in bootloader mode to USB, the word "Serial" will change to "USB"

2: Run mtty1.42.exe, You will se a box showing "COM1" from this list select "USB" - If USB isn't in the list, something has gone wrong in the "Driver Installation" Section of POST 1

3: Leave default parameters, (8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No) and Click OK

4: Run following commands:

5a: Press enter first to get prompt (Will Show as EITHER USB> or CMD> - Personally Mine Showed CMD>)

---------------------

MTTY OUTPUT:

---------------------

CMD>

---------------------

5b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:

---------------------

MTTY OUTPUT:

---------------------

Cmd>set 14 0

crc=0xD2C8DA7F.

HTCST ÚÈÒHTCE

Cmd>

---------------------

5c: type "task 29" to get your device formatted:

---------------------

MTTY OUTPUT:

---------------------

Cmd>task 29

Format BINFS start

Fill RSVD information for block 497 to 530

CE start start block=530, total block=3566

TAG NOT FOUND !!! NOT CLEAR STORAGE !!!

Format BINFS end

Cmd>

---------------------

5d: type "task 8" to ask your device reboot:

---------------------

MTTY OUTPUT:

---------------------

Cmd>task 8

Cmd>

---------------------

6: Immediately DISCONNECT your device then Press and Hold Vol Down to bring the device back to bootloader and connect to USB.

7: Run ROM Flasher and flash via USB. After rom flash is completed Hard-reset (Pen Reset, then Press and Hold Vol Up and Vol Down) then allow the ROM to boot.
[HD2 Windows Mobile 6.5 ROM Development] DaveShaw:
This is the second attempt at this thread.

Please try and keep it civil.

Thanks

Dave
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
Here Here and thanks a lot for re-opening!

Note: EVERYONE (Self Included) PLAY NICE!! This thread is for discussion of MTTY and not alternatives.

If you have an alternative post a thread for your own discussions

Thanks All

MG
[HD2 Windows Mobile 6.5 ROM Development] sonydesouza:
Thanks a lot MG !!!

As i told you,

A big thanks to you for your work here and your help by private message !

MTTY works like a charm !

Cheers my friend ! :)
[HD2 Windows Mobile 6.5 ROM Development] Noonski:
Driver Signature Enforcement Overrider has been a Life Saver on Windows 7 64 Bit, not just for the ActiveSync driver, also for using Open Source Audio Drivers.
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
I know, its brilliant, its in the second post!!

Love it!

MG
[HD2 Windows Mobile 6.5 ROM Development] sonydesouza:
Hi,

I did precursor thing but i have a last question :

After that :

1: Run the Driver Signature Enforcement Overrider and select “ENABLE TEST MODE” and Press Next

2: There will be a warning to REBOOT, Press “OK”

Have i reboot ? Or i have to go to point 3 directly ?

Thanks :)
[HD2 Windows Mobile 6.5 ROM Development] Noonski:
Reboot first, and you should then see the mention of this mode in the lower right corner of the desktop.

After that use Remove Watermark also from second post to keep your machine in this mode for ever and ever, without having the annoying Developer Watermark.
[HD2 Windows Mobile 6.5 ROM Development] sonydesouza:
Ok ! Understand ! that's why this "ONLY" point didn't work !

Thanks for help ! :)
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
yes Reboot, then step 3!

ill change so is clearer!

Thanks for pointing out.

MG
[HD2 Windows Mobile 6.5 ROM Development] sonydesouza:
Your welcome :)

Seems ok now ! Will tell you when i will flash another rom :cool:

See ya Dude ! :)
[HD2 Windows Mobile 6.5 ROM Development] ebliss:
Love this procedure. now, it is taking less than 30 seconds to format before I flash a new ROM. Much faster than flashing a stock ROM.
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
I thank you!! Finally people are seeing the light!

Welcome to the MTTY Crew!! 15 Minute Flashes for all (uning internal storage method anyway!!!)

MG
[HD2 Windows Mobile 6.5 ROM Development] SiliconSquirrel:
Glad you got a new thread man!!

Peace Out Bro!

Squirrel
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
Yeah! Thanks to Dave is clean again!

MG
[HD2 Windows Mobile 6.5 ROM Development] vr6only:
I had some trouble using MTTY on Win7 x64. Soooo, i switched over to my business laptop running WinXP.

First time run, worked perfectly! Thank you so much for this. I have flashed my HD2 over 30 times and it started showing some funny things that other users didn't experience with the same ROM.

Again. Thank you.
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
Follow POst 2!!

glad you found useful, but the main point of this thread is the Driver installation on Vista & Win7!

MG
[HD2 Windows Mobile 6.5 ROM Development] donalgodon:
Thanks for that. I was thinking that everything, including the Radio and Splash, got nuked in the process. I figured SPL, of course, but I just assumed about the others.
[HD2 Windows Mobile 6.5 ROM Development] tsttse:
hi thanks for the tutorial...

for the step below... where is the USB connections button found? ( i am using windows 7 so it is called windows mobile device center, which should be the same thing )

2: Connect Device to PC via Active Sync, Once Connected Uncheck USB Connections,DISCONNECT DEVICE then Reboot Computer
[HD2 Windows Mobile 6.5 ROM Development] 4D3:
in WMDC go to connection settings and remove the check from "Allow USB connections"

MG
[HD2 Windows Mobile 6.5 ROM Development] [★]:
Cheers thanks
[HD2 Windows Mobile 6.5 ROM Development] pablo11:
I used to use this stuff from your old thread in my Diamond days. Thanks for bringing it here.

Cheers
[HD2 Windows Mobile 6.5 ROM Development] tsttse:
one more question before i try this... will active sync and WMDC still work after installing the new drivers? do i have to uninstall anything when I am done flashing?