Ok guys - since my Molski.biz 2.26.10.2 rom has a few bugs (like the volume-control slider not working), I decided to reinstall a new rom. Ive seen already tons of threads including thousands of posts so it`s difficult to find out which rom is the best.
I heard of Faria released a cooked WM6-Rom but I m not sure if it`s working fine with the wizard and if there are still some bugs. In addition to that i don`t know if there are any incompatabilites with WM5 applications.
I`ve also seen a WM5 Rom tons auf WM5 Roms - but which one is working realy fine?
Oh forgot that: I`ve a G4 Device but it`s already CID unlocked.
LOL!!!!!!!
I haven't tried them all but Crossbow Reloaded 1.7 has been working great for me.
A couple of people, myself included had a problem where the built in phone dialer disappeared, but I fixed that by installing the Iphone dialer (can be found here by searching).
First Post.....
Yes, I as my post count would suggest I am new to flashing roms and setting up 3rd party softwares on my Wizard but I must say after hanging out on this forum for a couple of weeks I now feel somewhat like a veteran.
I first flashed with crossbow reloaded 1.7.1 I liked it and didn't notice any major problems at all.
But I was so impressed by XDA Mobile 6 that i had to try it and must say after about a week using it (since it was released) I'm much more impressed, wizard seems faster, i love the interface and the post offers great insight into problems and finding what configurations work for everyone.
I would suggest you try a few roms till you find what suits you best, here is the link to XDA Mobile 6
http://forum.xda-developers.com/showthread.php?t=310954&highlight=weather+panel
ok guys first i've installed core 2.0 what seems to work fine but, well u know, it's like a clean vanilla rom - too clean for me. So next i wanted Titanium but it's not released yet. After looking over the programs Faria delivers with his rom, i've decided not to have this much software and installed XDA Mobile 6. Seems to work fine and it looks nice.
Just one more question: where the heck is some difference to WM5? I mean everything looks like the same in WM6. Well ok, there is maybe a new skin, and some new tones, but in the end, i've could also use WM5 with wisbar and the Vista Skin.
For me it seems to be the same sh** like Windows XP and Vista - no real changes at all.
There's a page somewhere on Microsoft.com that details all of the new features in wm6 (Im sure if you do a google search for wm6 review you will find it). The most important one in my opinion is the ability to display HTML with in emails.
Hello All,
I purchased Touch Cruise (Polaris) from a reseller in middle east (came with windows mobile 6.0). I couldn't find the updates for my phone on HTC website.
After going thru the threads here, I found that doing a hard-spl I can install the WWE version of wm6.1
I used hard-splv2 olinex then installed wm6.1 (official), installed 3d drivers (htc-ca-Polaris-drivers.cab) everything worked smooth.
Then, I installed the TF3d cab found in one of the posts here, restarted and it worked good for 5 mins. Then, the phone became too slow and sometimes I had to remove the battery to restart as the screen freezes and I cannot even see the shutdown message (yes / No).
I haven't installed anything else besides the above mentioned cabs.
I have seen the videos of Polaris with TF3d in youtube and wonder why my phone doesn't work like that.
Please help.
regards
Niranjan
quick answer
you have some reading my friend
1. please read the R1 bug fixing list first - this will give you very good perspective on what might basically wrong with your setting
2. All developers as well as testers are saying that the 3D issue is not "Daily" use yet - so my recommendation for you go back to the 2D for now and watch closely after the progress of the great developers here
Yep, unfortunately you have to flash the ROM again and perform a HR 'cause something of the 3D drivers still stand and your device could remain very slow. I suggest to flash M-Amine's creation, best ROM with 3D drivers and Manila 2D till now
tf3d is not yet designe to work smoothly with Polaris. it's only the 2nd public release which something like prebeta
it consumes massive amounts of battery power and has some driver issues.
i'm sure that when the final release comes out you'll hear about it here.
Hi all,
Just after some advice.
I am useing dcd 3.4.3 and am enjoying it.
However, I kinda want to try something new. What is the best wm 6.5 rom out and why?
Hey there. Best 6.5 ROM? That's a matter of opinion. As far as stability is concerned, builds 21501 and 23017 lead the way. 23025 was the most recent build that I tried and it was hard to use. Windows moved the start menu icon and the "X" to the bottom. The GUI was either not user friendly or the version that I used was not made for our native resolution. I was unable to scroll far enough down in the notifications interface to be able to disable vibrate.
Tbonebtone has a nice light 6.5rom posted here in the Titan forum. R.Mogul makes a couple also, but I have never tried them and he uses a very early build.
I have been looking forward to trying the newer builds. I'm sure you have seen the more complete looking graphics and reskinned keyboards that are available in builds 23036 and 37. I am actually trying to familiarize myself with Ervius Visual Kitchen and Porting Tools just so I can try some of these newest builds. Seems support for the Titan device has really died in the past few months.
Hi there,
Thanks for the tip. i will give those to builds a go and report back. If you have anymore info on the latest ones that would be great.
LiamRutherford said:
Hi there,
Thanks for the tip. i will give those to builds a go and report back. If you have anymore info on the latest ones that would be great.
Click to expand...
Click to collapse
I should have more info on newer builds this weekend. The family is out of town and I have little better to do tomorrow.
In my search on how to accurately update my kitchen for unsupported builds, I came across this thread. It seems that this gentleman is updating us with new roms and providing us with the newest .nbh files. Of course, these are his ROMs, so he added his splash screens that say "WM7"... not sure why??, some games, etc. The buttons on the dialer are transparent with white font, so a darker bg is a must. Also he included the "honeycomb" start menu. Some people like it, but its not for me. Overall, despite the aforementioned, this rom seems stable and boots at a lovely 25.4 mb.
More here: http://forum.ppcgeeks.com/showthread.php?t=67673
I have a pair of bluetooth headphones by Sony (DR-BT21G) with media controls (AVRCP). This has always worked perfectly with the HTC Audio Manager throughout many ROMS (the default and Dutty's) but I upgraded to WM6.5 this weekend and it no longer works. Now, any time I try to use the controls, Windows Media Player fires up and takes over. Is there any way to change this or to manually set this back to the HTC Audio Manager? Listening to music is probably what I do most with my HD so this is probably reason enough for me to go back to a different ROM if I can't figure this out.
I've searched like crazy and it seems to happen to the WM6.5 Energy ROMs too, so it must be a general WM6.5/Manilla problem. So far, I've tried looking through all the settings in HD Tweak and Advanced Config, as well as changing the 0 and 1 keys in HKLM\Software\Microsoft\Shell\Rai\:WMPLAYER to point to AudioManager_Eng.exe, but none of that worked.
Does anyone have any other ideas?
Edit: Slowly, it seems to be becoming clearer that the Bluetooth Driver might be (part of) the solution. Any assistance in getting different versions of the BTHCI.DLL file or more insight would be great! If you have a Manila 2.5 ROM with working bluetooth control, please take a minute to share your driver with us!
I have exactly the same problem and I've posted about it here: http://forum.xda-developers.com/showthread.php?t=566157&highlight=AVRCP
elammertsma said:
I have a pair of bluetooth headphones by Sony (DR-BT21G) with media controls. This has always worked perfectly with the HTC Audio Manager throughout many ROMS (the default and Dutty's) but I upgraded to WM6.5 this weekend and it no longer works. Now, any time I try to use the controls, Windows Media Player fires up and takes over. Is there any way to change this or to manually set this back to the HTC Audio Manager? Listening to music is probably what I do most with my HD so this is probably reason enough for me to go back to a different ROM if I can't figure this out.
I've searched like crazy and it seems to happen to the WM6.5 Energy ROMs too, so it must be a general WM6.5/Manilla problem. So far, I've tried looking through all the settings in HD Tweak and Advanced Config, as well as changing the 0 and 1 keys in HKLM\Software\Microsoft\Shell\Rai\:WMPLAYER to point to AudioManager_Eng.exe, but none of that worked.
Does anyone have any other ideas?
Click to expand...
Click to collapse
Same here with Dutty R5.
A fix would be great.
I worked pretty hard at trying to find a solution but to no avail. I found that there's a key in the registry that refers to a bluetooth plugin for WMP, but deleting it had no effect and I don't think there's a simple way to get rid of the actual plugin. Doing so also still doesn't guarantee that AudioManager will take over. Maybe if someone takes the time to try swapping out files between (for example) Dutty's WM6.1 v4.3 and Dutty's WM6.5 Leo R5, it might work. Particularly, swapping out AudioManager_Eng.exe and all WMP files and registry settings might work. Just an idea! I'd do it myself, but considering crazy work hours, my need for a working phone and problems I've been having with 6.5 it will be a while before I can do more on this.
I was also using Dutty's Leo R5 but due to major stability issues which seemed to be primarily related to importing contacts and texts (through either PIM or "My Phone"). I'll miss the twitter tab and all the neat features of the new manila and WM6.5 improvements but for now Dutty's v4.3 Final is just so much faster, more reliable and doesn't have the bluetooth problem.
Unless some smart guy figures this one out, I think we can best just hope for it to be resolved in a future rom with a fix in the new Manila.
The question for me is: Is this problem on all 6.5 ROMs??? I thought I had tried a 6.5 ROM before without this issue... but I might be wrong...
Am I right in assuming you returned to Dutty's 6.1 ROM? Because then I would flash a 6.5 ROM and we could test replacing files: You upload them here and I try replacing them on my Blackstone!
Update: I just flashed PhamQuang's V67 (a 6.5 ROM with Manila 2.1) - and guess what: My BT-headset controls the TF3D music player!
So maybe this is not a 6.1 vs. 6.5 problem, but rather a Manila 2.1 vs. 2.5 problem? Or it just depends on what ROM you are using and if the cook has done his magic correctly?
Great news! I'm glad you have it working and it narrows the problem down a bit.
So it seems that for now, bluetooth music lovers should steer clear of M2.5. I'd think it's a Manila 2.5 problem considering it works on all Manila 2.1 versions I've tried so far and on PhamQuang's V67 ROM with WM6.5 that you're using. I still wonder if swapping files between Manila 2.1 and 2.5 would be possible, but after using WM6.1 and Manila 2.1 for a day I'm hooked on the speed and won't be going back to Manila 2.5 until some major speed improvements have been made. (Or am I mistaken and is WM6.5 the laggy culprit?)
Considering you have your headset working with PhamQuang's V67 and it runs WM6.5, I'd like to wander off topic a bit and ask how you like that one? Has it been fast and stable so far? I've been pretty happy and faithful to Dutty's work but if there's something better out there (with working bluetooth to HTC's AM) I'm definitely game! I especially miss the smoother kinetic scrolling of WM6.5 and the wonderful Twitter tab in Manila 2.5. I guess I'll just have to be patient for that last one considering it seems you can't have everything.
Fix. thx to Gooru from xda-developers.info
Awesome! Thanks NewFolk! I'm glad there's a solution and hopefully it will help anyone who's searching for it. I can't test whether it works on Dutty's Leo R5 at the moment but I'll take your word for it
At least this is one less reason to avoid WM6.5 + M2.5!
elammertsma said:
Considering you have your headset working with PhamQuang's V67 and it runs WM6.5, I'd like to wander off topic a bit and ask how you like that one? Has it been fast and stable so far? I've been pretty happy and faithful to Dutty's work but if there's something better out there (with working bluetooth to HTC's AM) I'm definitely game! I especially miss the smoother kinetic scrolling of WM6.5 and the wonderful Twitter tab in Manila 2.5. I guess I'll just have to be patient for that last one considering it seems you can't have everything.
Click to expand...
Click to collapse
PhamQuang's ROMs aren't the fastest ones out there, which is why I'll switch to a different 6.5 ROM or back to Topix (the best 6.1 ROM I've tried) as soon as I get my LCD replacement (I managed to break my LCD screen while attempting to exchange the touchscreen... )
NewFolk said:
Fix. thx to Gooru from xda-developers.info
Click to expand...
Click to collapse
Awesome! Thank you! Hopefully this fix enables every WM+Manila combination!
elammertsma said:
Awesome! Thanks NewFolk! I'm glad there's a solution and hopefully it will help anyone who's searching for it. I can't test whether it works on Dutty's Leo R5 at the moment but I'll take your word for it
At least this is one less reason to avoid WM6.5 + M2.5!
Click to expand...
Click to collapse
If you get around to trying a 6.5+2.5 ROM, please post some feedback!
NewFolk said:
Fix. thx to Gooru from xda-developers.info
Click to expand...
Click to collapse
Didn't work for me on Miri's V10, still launching WMP. Still looking for a solution.
Wow, sorry to hear about your screen, MAMeingast. I wouldn't dare attempt that with my dear HD, although I do wish it had a capacitive screen. I haven't touched my stylus in months.
If I can get Sashimi to do decent backups and automated installs, I might be able to experiment with ROMs more freely, but for now XML provisioning and other settings restorations don't seem to work well and reflashing and configuring still takes a few hours each time. I might try a full backup of my current setup this weekend and test a few Manila 2.5 ROMs. Maybe I can pinpoint what the differences are between the working and non-working BT configurations are and make a cab to fix it. Unfortunately, I'm not aware of a method to monitor file or registry key access so I can't see what's active during BT headset pairing. In other words, getting that together will have to be a pretty labor intensive process.
The cab file simply contains a version of the BTHCI.dll driver file. I haven't been able to find Gooru's original post (using Google translate considering the site's all Russian), so I don't know which ROM(s) the cab file is meant for, where the file comes from or which build of WM it is included in. A quick search turned up this post by Da_G from way back in May, noting that the 216xx WM6.5 build comes with a BTHCI.dll version that isn't bound to WMP. How the binding is done isn't clear to me, but it's possible that the currently running media player (usually AudioManager_Eng.exe) would accept the input without extra configuration. If people can grab that version (see below) and post results here (or any other versions for that matter... it can't hurt to try more!), we could see if it fixes the problem. It's starting to look like that file is indeed the culprit, so good news there!
Thinking out loud: If it turns out to be more than just the driver, I might try replacing the dll on Dutty's Leo R5 first, followed by others until I find a Manila 2.5 that the cab file fixes. If that works, I can dump the file system and registry before the fix, and the file system and registry of other uncabbed ROMs to see if a general fix can be made and hopefully pass that along to Dutty and the other cooks to add to future releases. If anyone is running a Manila 2.5, please try installing the cab and posting your results. It would be additionally helpful to let us know which version (or date and size) your original BTHCI.dll is.
mauriceheath said:
Didn't work for me on Miri's V10, still launching WMP. Still looking for a solution.
Click to expand...
Click to collapse
I'm sorry to hear that. Naturally, I hoped someone had come up with a general fix, but we'll keep looking. I changed the topic title back from [Solved] considering it didn't work for you. If you find out more, let us know! Maybe you can help with the dll questions, considering you're running a 2.5 ROM.
Edit: Found a download of the proposed older working BTHCI.dll! Try the cab from this post and let us know if it works for you: http://forum.xda-developers.com/showpost.php?p=3807872&postcount=114
It should be uninstallable, but I still recommend backing up your original. You can never be too careful, right?
neither #8, nor #12 can fix my problem, ROM udk Leo R3. still looking for solution...
elammertsma said:
Wow, sorry to hear about your screen, MAMeingast. I wouldn't dare attempt that with my dear HD, although I do wish it had a capacitive screen. I haven't touched my stylus in months.
If I can get Sashimi to do decent backups and automated installs, I might be able to experiment with ROMs more freely, but for now XML provisioning and other settings restorations don't seem to work well and reflashing and configuring still takes a few hours each time. I might try a full backup of my current setup this weekend and test a few Manila 2.5 ROMs. Maybe I can pinpoint what the differences are between the working and non-working BT configurations are and make a cab to fix it. Unfortunately, I'm not aware of a method to monitor file or registry key access so I can't see what's active during BT headset pairing. In other words, getting that together will have to be a pretty labor intensive process.
The cab file simply contains a version of the BTHCI.dll driver file. I haven't been able to find Gooru's original post (using Google translate considering the site's all Russian), so I don't know which ROM(s) the cab file is meant for, where the file comes from or which build of WM it is included in. A quick search turned up this post by Da_G from way back in May, noting that the 216xx WM6.5 build comes with a BTHCI.dll version that isn't bound to WMP. How the binding is done isn't clear to me, but it's possible that the currently running media player (usually AudioManager_Eng.exe) would accept the input without extra configuration. If people can grab that version (see below) and post results here (or any other versions for that matter... it can't hurt to try more!), we could see if it fixes the problem. It's starting to look like that file is indeed the culprit, so good news there!
Thinking out loud: If it turns out to be more than just the driver, I might try replacing the dll on Dutty's Leo R5 first, followed by others until I find a Manila 2.5 that the cab file fixes. If that works, I can dump the file system and registry before the fix, and the file system and registry of other uncabbed ROMs to see if a general fix can be made and hopefully pass that along to Dutty and the other cooks to add to future releases. If anyone is running a Manila 2.5, please try installing the cab and posting your results. It would be additionally helpful to let us know which version (or date and size) your original BTHCI.dll is.
I'm sorry to hear that. Naturally, I hoped someone had come up with a general fix, but we'll keep looking. I changed the topic title back from [Solved] considering it didn't work for you. If you find out more, let us know! Maybe you can help with the dll questions, considering you're running a 2.5 ROM.
Edit: Found a download of the proposed older working BTHCI.dll! Try the cab from this post and let us know if it works for you: http://forum.xda-developers.com/showpost.php?p=3807872&postcount=114
It should be uninstallable, but I still recommend backing up your original. You can never be too careful, right?
Click to expand...
Click to collapse
Hi elammertsma,
I've already tried the T-Back 6.5 BT Driver.cab, still launches WMP so I'm guessing there's more to this than just the version of BTHCI.dll. The BTHCI.dll included in Miri's V10 ROM is dated 01/10/09 16:31 (although that may be the date I installed the ROM, not sure) and is 63K in size. Hope this helps.
seems the bthci.dll is a rom file, and prevent copy? I try to copy the file from a rom which headset could interface with manila audiomanager, but fail - say the file in not allow to copy...
i-PDA2006 said:
seems the bthci.dll is a rom file, and prevent copy? I try to copy the file from a rom which headset could interface with manila audiomanager, but fail - say the file in not allow to copy...
Click to expand...
Click to collapse
You'll need to use another file manager like Total Commander or Resco File Explorer to copy the BTHCI.dll file
mauriceheath said:
You'll need to use another file manager like Total Commander or Resco File Explorer to copy the BTHCI.dll file
Click to expand...
Click to collapse
I'm using the Resco, but still same problem. Properties of the bthci.dll is checked for hide/ready/sys/rom. It can not be seen both in WM file explorer and Resco, but in Resco search for the name you can find it. I try to copy via Resco, it said copy fail...
mauriceheath said:
Hi elammertsma,
I've already tried the T-Back 6.5 BT Driver.cab, still launches WMP so I'm guessing there's more to this than just the version of BTHCI.dll. The BTHCI.dll included in Miri's V10 ROM is dated 01/10/09 16:31 (although that may be the date I installed the ROM, not sure) and is 63K in size. Hope this helps.
Click to expand...
Click to collapse
For mine:
1. BTfix.cab, still activate WMP, and seems no change at all.
- I try WMP, my headset is still interface with it, works well.
- Manila audio - sound was transferred to headset but interface no.
- CorePlayer - sound was transferred to headset but interface no.
2. T-Back 6.5 BT Driver.cab, not activate the WMP any more, and others unchanged.
- I try WMP, need manually open WMP first, and my headset is still interface with it, works well.
- Manila audio - sound was transferred to headset but interface no.
- CorePlayer - sound was transferred to headset but interface no.
being a bluetoth headphones ower to i ued the htc audio player too. im using nrgz photon rom 11.10.09 manilla 2.1. the default launched audio player from headphones is media player. tried this fix it dont fix it. yes i know its for m.2.5 i was just hoping it would work.
guess i will have to make playlists there instead. i remember there being issues with Wmp it wouldnt recognise all my content. like eminem album i got from play.com. all my own cd rips are good though lol. i will post a fix if i find one. i got a cab. the for s2p which is called tback but all that does is the opposite and unlocks the htc audiomanager and reverts to WMP or s2p. ive looked at nitrogen but unable to find anyway to make headphones work.
My Observations on this
Now my observations on this is that it was not happening on NRG Leo release 14092009 (think it may have been the last Genisis version). We know that NRG's rom platform on 23016 is rock solid as he has stated that many times so I'm suspecting it must be something in the lastest M2.5 version 1919xxx or another package addition as it seems to be effecting all the current Roms running this version of the Leo Manilla. I'm really suspecting that it is something in the way M2.5 HTC audio player is interfacing with WMP but that is just my humble non technical opinion
Can't find if BT stack has been updated in all of this. Bit of a bugger as I have the same issue in the my current version 23092009 release and it is also in the 11102009 release. Hope NRG can take a look at this as I use my BT headset constantly or my bit helps in some small way in finding a solution. In the meantime I'm falling way back to 14092009 NRG Leo version.
Would someone be willing to post a basic ROM that uses one of the newer flavors of 6.5? The older builds have problems with the alarm clocks (won't repeat correctly, and don't allow the use of MP3's) as well as use the 6.1 interface that isn't finger friendly.
This one is preferred without a whole lot of customizing but I'll take anything. The only one out there has problems freezing and I need something more stable.
Also, I've got $50 to anyone that can post said ROM that actually works with large (8GB) MicroSD cards and Windows Media Player. Since 6.0 and before Microsoft hasn't fixed the bug that causes songs to load slowly, switch slowly, and not pause ever few seconds to buffer.
travis.garrison said:
Would someone be willing to post a basic ROM that uses one of the newer flavors of 6.5? The older builds have problems with the alarm clocks (won't repeat correctly, and don't allow the use of MP3's) as well as use the 6.1 interface that isn't finger friendly.
This one is preferred without a whole lot of customizing but I'll take anything. The only one out there has problems freezing and I need something more stable.
Also, I've got $50 to anyone that can post said ROM that actually works with large (8GB) MicroSD cards and Windows Media Player. Since 6.0 and before Microsoft hasn't fixed the bug that causes songs to load slowly, switch slowly, and not pause ever few seconds to buffer.
Click to expand...
Click to collapse
Check this thread.
I've been using this ROM for quite some time, and other than the occasional freezing, which doesn't happen very often, it's quite good.
And it's it does work with 8GB MicroSD cards, as I've one, WMP works fine and flawlessly.
Travis, here is a 6.5 23549 rom I put together. It does have RealVGA 96dpi by default, but NO Manila 2D this time. Showcase is included along with PJohnDevelopments modified menu.....I love it! Thanks PJohn. Along with misc. other fixes for the 96dpi resolution. Let me know what you think.
6.5_23549_RealVGA.7z
imzkng said:
Travis, here is a 6.5 23549 rom I put together. It does have RealVGA 96dpi by default, but NO Manila 2D this time. Showcase is included along with PJohnDevelopments modified menu.....I love it! Thanks PJohn. Along with misc. other fixes for the 96dpi resolution. Let me know what you think.
6.5_23549_RealVGA.7z
Click to expand...
Click to collapse
Hi, do you have a thread open for this version ?, just for bugs etc, is it stable ?.
Thanks
PJon, thanks for the idea, but that lockup on Heechee's ROM is what prevents me from using it. If I didn't use the phone for an alarm clock then I would gladly use the ROM. He's got some family emergencies that he's sorting out now, so until he resumes working on this ROM I have to find a different one.
imzkng said:
Travis, here is a 6.5 23549 rom I put together. It does have RealVGA 96dpi by default, but NO Manila 2D this time. Showcase is included along with PJohnDevelopments modified menu.....I love it! Thanks PJohn. Along with misc. other fixes for the 96dpi resolution. Let me know what you think.
6.5_23549_RealVGA.7z
Click to expand...
Click to collapse
IMZKNG, thanks for the post. I tested an earlier version of your ROM and ran into several bugs that I posted on this thread: http://forum.ppcgeeks.com/showthread.php?t=108971&page=2
I just saw that you released another version so I'll download that tonight when I get home and see what we get. Thanks for your work.