Hey folks,
I just installed Duttys HG V1.7 2.10 based rom with 576mb enabled. Radio is 2.08.50.08_2.
I switched back to non-576mb roms few weeks ago since the poor call quality with the background noise issues was still present.
I thought I'd give it another try especially after reading on HTCPedia that a guy installed a HTC Hotfix which made the noise issues go away.
So I tried it too, and well it seems promising. Can't test real calls yet, but a direct comparison, calling my voicemail box, directly before and after applying the fix, showed that after the fix, voicemail didn't show ANY background noise anymore. Which was present before ...
So if anyone wants to try the fix with a 2.10 576mb rom ... here you go:
Update: Smaberg pointed me in a priv msg to this cab, that he also provides for his roms ... I guess it does the same, replacing that .dll. Here is the link to the .cab.
http://forum.xda-developers.com/attachment.php?attachmentid=303583&d=1270329627
Will give it ago, was just about to flash energys new rom
Seems to fix it for me.
boba23 said:
Hey folks,
I just installed Duttys HG V1.7 2.10 based rom with 576mb enabled. Radio is 2.08.50.08_2.
I switched back to non-576mb roms few weeks ago since the poor call quality with the background noise issues was still present.
I thought I'd give it another try especially after reading on HTCPedia that a guy installed a HTC Hotfix which made the noise issues go away.
So I tried it too, and well it seems promising. Can't test real calls yet, but a direct comparison, calling my voicemail box, directly before and after applying the fix, showed that after the fix, voicemail didn't show ANY background noise anymore. Which was present before ...
So if anyone wants to try the fix with a 2.10 576mb rom ... here you go:
Click to expand...
Click to collapse
is this applicable to LEON Rom as well?
also is there more info on this?
If it fixes it have you thought about contacting Dutty and getting him to include it in the ROM so that its automatically cooked in...?
I tried it on Miri v11 with radio 2.08.50.08_2 but it seems to be exactly the same as before...
Thanks, that seemed to have made the call quality much "cleaner". I use to hear static and some sort of compression (or like in echo cancelling) but now, those same numbers when i call seem to be much clear.
Thanks again.
boba23 said:
Hey folks,
I just installed Duttys HG V1.7 2.10 based rom with 576mb enabled. Radio is 2.08.50.08_2.
I switched back to non-576mb roms few weeks ago since the poor call quality with the background noise issues was still present.
I thought I'd give it another try especially after reading on HTCPedia that a guy installed a HTC Hotfix which made the noise issues go away.
So I tried it too, and well it seems promising. Can't test real calls yet, but a direct comparison, calling my voicemail box, directly before and after applying the fix, showed that after the fix, voicemail didn't show ANY background noise anymore. Which was present before ...
So if anyone wants to try the fix with a 2.10 576mb rom ... here you go:
Click to expand...
Click to collapse
same here, just tested it, it does seema to improve call quality
boba23 said:
Well then Miris V11 must be somehow different. I am talking about Com2 Roms, not Com3 as Miris V11 is I think.
I just did some more testing. My background noise/static problems are definately gone with that fix on Duttys HG 1.7, 2.10 based, 2.08 radio, 576mb enabled. Just had a crystal clear conversation with my GF
boba
Click to expand...
Click to collapse
it works just fine on miri's latest v11 for me.
Maybe someone can just post the .dll file so we can just replace the one in the ROM with the new one.
Works for me too! WOOHOO!
Problem?
Hi,
this fix sounds good.
but i can´t install it.
i am testing RTT RTM 1 at the moment and when i try to start the fix it says "This hotfix is not compatible with your device".
Any Idea´s?
Thanx
MAD242
thank you mate! working great on chucky's 3.10 23112 rom!
me too,
This hotfix is not compatible with your device
me also,please post the dll file alone,so we can self replace it
bobsbbq said:
Maybe someone can just post the .dll file so we can just replace the one in the ROM with the new one.
Click to expand...
Click to collapse
Wavedev extracted from fix pack.
hi guys, just a quick noob question..is it safe for me to install these t-mobile us rom with 576 ram enabled on my uk vodafone htc hd2?...wud i still be able to make calls and use my 3g dataplan?...thanks in advanve guys
texture said:
Wavedev extracted from fix pack.
Click to expand...
Click to collapse
thank you for the extracting.
Works for me! one tiny .dll file!
Thanks or sharing boba23!
best regards
MAD242
boba23 said:
Ehm, man. That's what the hotfix does obviously. Why replace it manually?
boba
Click to expand...
Click to collapse
Because if you are cooking ROM's it makes sense to add it in for your users. If you are just a user then the hotfix is good for you.
can i upgrade to this t-mobile rom with 576 ram radio on my uk vodafone hd2 and stil make calls and use the 3G services?..thank guys
Related
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.
Hi all,
anybody experienced the same issue with a not-startin fring? So far I installed fring (version for Xperia and "other WM") but tipping the icon won't start fring, just the icon gets enlighted and nothing more happens.
Has anybody got an idea how to get to work with fring?
Thanks, Bluiecharge
Looking at fring here im seeing no mention of 6.5, i cant really tell you how much changed between 6.1 and 6.5 (to me id say just the design) but i guess theres something there.
Your best bet would be to email fring support (or something, contact fring) asking if they are working on a wm6.5 version
From previous reports, it seems there is some issues with htc message in manila 2.5.
Its currently not supported.
You could still run it if you turn off sense from Today's items
taiseer999 said:
You could still run it if you turn off sense from Today's items
Click to expand...
Click to collapse
I have tried that in my 1.43(70124 WWE ROM) but not working.
Anything else can solve?
Iam also badly in need of it
On 1.48 ROM fring is not working as well.
skr_xd said:
I have tried that in my 1.43(70124 WWE ROM) but not working.
Anything else can solve?
Iam also badly in need of it
Click to expand...
Click to collapse
I have had it working on the 1.43 rom but before i tried it i had disabled manila and also disabled the HTC messaging app (with a cab posted on xda)
Not working for me either. Shame, as Fring was one of the best things about my Kaiser (and yes, the audio DID correctly re-route to the earpiece!).
have any one found a STABLE ROM that thay used for 2-3 days without soft reset ?
im trying to find most stable ROM possible, preferably 6.5.3 or above, but the one i can trust not to hang for 2,3 days of hard core use as Music Player, Web Browser and Online connection to MSN/Skype for 24Houers.
with or without HTC Sence.
at the moment im not that concern about performance as any rom is still faster then my old treo pro lol
yup, a stock one.
I´m using the official one and no problems.
1.48 or 1.66 ? if 1.48 then why not 1.66 ?
vladimir2989 said:
1.48 or 1.66 ? if 1.48 then why not 1.66 ?
Click to expand...
Click to collapse
You should try the Official 1.66.405.2 WWE ... it's most stable ROM for daily usage... it's included all the fixes from HTC ... so there is no problem... try it
just installed 1.66 ... installing all the soft i use, just installed Smaberg White 1 percent battery thing that makes % appear above the battery, now i have little black square next to it... but i guess that a different issue
vladimir2989 said:
just installed 1.66 ... installing all the soft i use, just installed Smaberg White 1 percent battery thing that makes % appear above the battery, now i have little black square next to it... but i guess that a different issue
Click to expand...
Click to collapse
In my opinion.... if you use the official ROM... just install BsB Tweaks and then it's fine...
Hi,
Where can I find "Install BsB Tweaks"
Thanks
vladimir2989 said:
have any one found a STABLE ROM that thay used for 2-3 days without soft reset ?
im trying to find most stable ROM possible, preferably 6.5.3 or above, but the one i can trust not to hang for 2,3 days of hard core use as Music Player, Web Browser and Online connection to MSN/Skype for 24Houers.
with or without HTC Sence.
at the moment im not that concern about performance as any rom is still faster then my old treo pro lol
Click to expand...
Click to collapse
my own preference....freyberry barebone 6.5.5 latest ms build 23xxx running on base 1.66leo....stable....not a single softrest is needed for 2weeks for now....
devil_82 said:
my own preference....freyberry barebone 6.5.5 latest ms build 23xxx running on base 1.66leo....stable....not a single softrest is needed for 2weeks for now....
Click to expand...
Click to collapse
will try that soon prob on Monday, i been using freyberry Premium_nomess V6 or whatever the latest one is, for a while (i hate HTC messaging) but it hangs occasional especially over night, i have to do a soft reset every morning for some reason which make it useless as alarm clock (although i have suspicion it maybe due to someting i install or combination of stuff i install coz no one else seems to have that problem)
but i kinda need HTC Album (facebook uploading) i guess its not in bearbone so i will try WMPhone version or something
richsark said:
Hi,
Where can I find "Install BsB Tweaks"
Thanks
Click to expand...
Click to collapse
here http://forum.xda-developers.com/showthread.php?t=589305
next time do a search
Dutty's HG V.08. actually in HD2 i never get stuck..
Two weeks without a softreset that's thruly amazing especially
if you consider that WM 6.5.5 is not official and beta.
No mather which rom I use but everyday I do a softreset, kind of a habbit.
Currently I'm using the 2.07 T-Mob.
@Vladimir, no offence but I don't think you can open a thread like this and pick a rom based on the experiences people tell you here.
I think you need to test yourself as everyone has a different use/experience with a rom.
Just my 2 cents
devil_82 said:
my own preference....freyberry barebone 6.5.5 latest ms build 23xxx running on base 1.66leo....stable....not a single softrest is needed for 2weeks for now....
Click to expand...
Click to collapse
I'm using MIRI's 6.5 ROM.
I have found it to be completely stable. I have to avoid 6.5.x ROMs 'cos Memory Map doesn't work properly on them.
The stock ROM is stable, but it's a mess! They should have included a way to tidy the cluttered start menu. Things are improved by installing BSB Tweaks.
IMHO there is no such thing as the perfect ROM!
There are number of factors to consider that can effect the overall stabilty of a ROM be it stock or cooked, a ROM that one person might find it to be flawless, the other might have issues, remember not all bugs are ROM related so consider the following points:-
- The 3rd party apps you use
- The network you are on
- The radio version you use or combination of the radio & rom
I'm currently using stock 1.66 ROM not that it's the best but it's been the most stable for my apps and daily use!
One thing that frustrates me is the lack of constructive feedback you get from people flashing various stock or cooked ROM's it's allways comments like "This ROM is very fast and stable" or "this the best ROM I've tried" what's funny is that you get these comments when they've only used the ROM for couple of hours or in some cases just 5 minutes!!!!
IMHO you must use the ROM for at least couple of days if not a week and once you've installed all your apps then you can establish how good the ROM is in your daily use only then you should give your feedback so that others can have a better idea of how the ROM really performs!!!
Notification Delay FIX
--------------------------------------------------------------------------------
Ok, I decided not to wait til tomorrow, well technically for me it is (4am). Here is the long awaited fix.
*DISCLAIMER*
I am in no way responsible for damage to your phone, software breakages, Temper flares, or Hiccups, or Brain Farts. You are freely attemping to fix the notification relay delay based on what is being attached to this post knowing the risks.
Compatible with: HD2/Leo & Touch Pro 2/Tilt 2
Notification Enhancement Build 2011.3730.
Nothing has been added nor removed. This will fix the HTC notification, especially for SMS delay. This Build is only for HD2/Leo Roms 1.72 or Higher, & Touch Pro 2/Tilt2 Roms 2.07 or Higher Do not know if this will work on lower build roms, but see no reason why not.
I have removed the option to choose where to install so there is no mistake. There is the option of uninstalling this fix should it not work, or renders anything possibly to lock up or not work properly. I would suggest to make sure messaging client is not running when instaling.
If for some reason the cab fails to install claiming you dont have permissions, copy the cab to your device and run it from there, this seems to resolve the permission issue for some reason.
This fix does not remove the Msg Sent notification that seems to be default, if you wish to not have this notification, edit this line in the registry:
[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging]
"DisableSMSSuccess"=dword:1
Known Bugs:
None Known or detected.
Known Issues:
May not work with Arcsoft Messaging system, has not been tested. Only has been tested with HTC/Jayaayu (AKA: Commviva) Client.
All comments welcome, Good, Bad, or Ugly.
Enjoy everyone.
159 Views, 9 Downloads, and no feedback?
Does it work?
Does it not?
Go F! myself?
wat delay are u talking about my dear??.....is it the message loading delay in HTC MESSAGE??
yea please confirm what issue this is fixing? cheers
Agreed, clarification on exactly what this fixes is needed.
+1 for clarification, cuz if this will fix the lag caused when a message is coming in i would love it!
not the same lag issue i was thinking of. i hope it works for those guys though they seem very irritated!
http://forum.xda-developers.com/showthread.php?t=641902
Explains all.
Thanks for the explanation, didn't even know that problem exsisted . I hope your fix works for people suffering from this problem.
i've been getting that on 1.66 but it's a bit intermitant. i'll download and test it over a few days and report back
Personnally i've this "lag" after sent message slow to return to home...
You think your cab can help me?
http://www.youtube.com/watch?v=HJTXefa9PPE
some how i doubt it because that is caused by the messaging application itself. I have this too and i also have the slow load issue when a contact has more than 20 messages associated with it (i have one that has 2364+ (growing even as we speak))I installed netripper's LCS app which improved it but it's still not as fast as my diamond with the default 6.1 messaging app. I've also got the slow to allow typing problem and none of the tricks i've seen help with that one.
Ok lol
So waiting a proper HTC messaging client
G-ThGraf said:
Personnally i've this "lag" after sent message slow to return to home...
You think your cab can help me?
Click to expand...
Click to collapse
I've just installed this onto my HD2 and i think that this cab doesnt solve that problem, but improves the ability to type faster when messaging thread reaches a higher number, as before typing would have been laggy for me, when the message thread reaches 50+ messages. Well, thats what i've experienced anyway.
Didn't i say that without even installing it? Yeah, i did, in post 11. This is for the notification system only i.e the sound that plays when you get a text message or mms. This patch doesn't fix any of the many other problems there are with HTC's - frankly ****ty - messaging program. Why HTC found what microsoft found good enough for the last 2 versions of WM wasn't good enough for them i have no idea because that works well and now includes exchange synchronisation support for sms messages (if you have exchange 2010 and outlook 2010) and almost all the other WM 6.5 partners are using it.
In fact i think i just convinced myself to install the hack that allows Sense to use the WM default (outlook style) messaging UI instead but i will try this first.
G-ThGraf said:
Personnally i've this "lag" after sent message slow to return to home...
You think your cab can help me?
http://www.youtube.com/watch?v=HJTXefa9PPE
Click to expand...
Click to collapse
Looking at your video, that doesnt look like a stock rom. After sending a sms I dont have that problem with the home screen freezing.
Again This is for the notification problem only. Depending on your rom, the Newest Msg client that works best so far is: HTCMessaging_Client_SKT_1_5_20143724, but its in Korean, which isnt a big deal either. The lag is still there, but allows you to type without having to wait for the msgs to load. So far no magic bullet has been found yet.
Sadly it isn't working for me
tested on
Touch HD:
Blackstonhenge 1.5 Hyper WM 6.5.5 Manila 2.5 - HTC Messaging (Client 3625,2622, modified Client by Wajk - i guess it's 3625) with Radio 1.14 / 1.15 / 1.17
Blackstonhenge 1.6 Hyper WM 6.5.5 Manila 2.5 - HTC Messaging (Client 3625 (?) edited by Wajk, new Version)
Notification in Standby (Screen off):
- on Batteryusage: no Textmessage Notifications (but MMS/E-Mail/... will work)
- while plugged into Charger: Notifications work
But as far as you did this cab, you must have an Idea what the Reason for this Bug is, can you please tell me what exactly your Cab-file does change? Im also looking for a Solution to fix this Bug, would be good to know your Suspicion. I wont take any Credit if i will find something usefull, just wanna get this working
apsis said:
Sadly it isn't working for me
tested on
Touch HD:
Blackstonhenge 1.5 Hyper WM 6.5.5 Manila 2.5 - HTC Messaging (Client 3625,2622, modified Client by Wajk - i guess it's 3625) with Radio 1.14 / 1.15 / 1.17
Blackstonhenge 1.6 Hyper WM 6.5.5 Manila 2.5 - HTC Messaging (Client 3625 (?) edited by Wajk, new Version)
Notification in Standby (Screen off):
- on Batteryusage: no Textmessage Notifications (but MMS/E-Mail/... will work)
- while plugged into Charger: Notifications work
But as far as you did this cab, you must have an Idea what the Reason for this Bug is, can you please tell me what exactly your Cab-file does change? Im also looking for a Solution to fix this Bug, would be good to know your Suspicion. I wont take any Credit if i will find something usefull, just wanna get this working
Click to expand...
Click to collapse
Okay the cab really is nothing special, I have 3 rom builds, HD's 1.72 (Telstra), 2.13 ToMoUS and the TP2 2.07. The ToMoUS Rom has the Notification problem, which seems to be with the Notification Enhancement Package. The TP2 2.07.401 didnt have this issue, and the Telstra 1.72 doesnt seem to have this issue, so I tested changing this package alone, and found that the 2.13 rom has this problem. But take note, that this was tested on the TP2 on a stock 2.07.401 TP2 rom. I was taking the HD2 packages and putting it into the TP2 rom, thats how I found this to be the cause. I first installed all the packages from the 2.13 rom into the TP2 and it started happening, thats when I went searching for what it could be, and for me, the Telstra 1.72 rom and TP2 2.07.401 Notification Enhancement packages works.
Also note, I do not know if this will work with custom roms, due to the fact that alot of custom roms use the arcsoft messaging program, not the htc. Again mine is stock rom interchanging the packages.
Yea i was looking at your Cabfile. I also think that my Problem is the cause from HTC Settings Enhancement. Setting something within the Notificationsetting under the Manila Settingstab, doesnt affect my Windows Mobile Sounds and Notification Setting...
Under HKLM -> Software -> HTC -> HTCSettings_Imrovement i found some strange things:
Current_DisplayTime : shows a wrong time
DefaultSound_NewTextMsg : there was something different than i had selected
NotifySound_SupportFilterSound : dont know what it does, but is set to 1
SoundOption_AllEnableEvent : is dissabled ...
SoundOption_Intialized : enabled
and under HKLM -> Software -> HTC -> HTCSettings_Imrovement -> DisabledSoundFile : there are a few Entries, but why are they disabled?
edit.
solved now,i removed HTC Messaging and installed the HTC Messaging Client from NRG and his NRG-Roms, this one works for me, now my Notifications are back
Well guys, after a couple weeks with the stock TMOBILE rom I conclude that it's just USELESS.
I can't even use the phone... It's getting stuck when I'm trying to call someone, stuck when viewing images, stuck stuck stuck, at least 5 times a day.
Plus a million SOD's a day... I tried everything, from losing all apps, to modifying the registry.
I NEED A NEW ROM
But there are so many over there, I do not know what to choose.
I need:
1. As little visual tweaks as possible, i'd like to take care of that myself (CHT Cooked in is fine though)
2. Maximum system stability and performance, I DON'T WANT HANGS FROM SIMPLE OPERATIONS SUCH AS CALLING SOMEONE
3. No bloatware
4. Not much bugs (ie good support, constantly worked on, not a 1 time "job" )
Basically If it can resemble the stock one, but with more stability, tweaks and performance boosts, then i'm happy.
I have the sticky flashing manual in hand, so all I need is a recommendation.
Looking forward to flashing this thing today, thank you very much XDA.
Energy ROM Cookie's Reference ROM
this is a custom rom close to stock as you're going to get, please make sure you read loads before flashing.
http://forum.xda-developers.com/showthread.php?t=612580
chaoscentral said:
Energy ROM Cookie's Reference ROM
Click to expand...
Click to collapse
Or the standard sense reference or full. I recommend using the 23569 builds as well. more finger friendly and slightly quicker. Also there is an advantage with the full version in that if you wish to update the rom in future you can backup your settings using the energy settings exporter and then reimport them.
regarding the builds mentioned - can you expand ? links ?
thanks !
Exporter sounds GREAT.
Basically there are two builds of almost all the custom roms. One build will be the latest 6.5 build (21907, same WM version as the stock roms but with some bug fixes) then there is the 23569 (or higher) builds. These are WM 6.5.5. Some big changes here to the way the start menu works and also to the UI to make it more finger friendly. It's also a little quicker than WM 6.5 but (apparently. i've not found any yet) more buggy then WM 6.5. Also as i said (and i've now checked this) custom roms also include newer, less buggy, versions of sense (AKA manilla)
I suggest EnergyROM
Great, I think I will go for Energy.Leo.23569.Sense2.5.Cookie.Reference.Jun.26.7z
Is that OK for me ? (well, is it better than what i have now )
Is there a settings exporter in Energy.Leo.21907 ?
If you have the T-Mobile US HD2, make sure you use the right radio for your device.
That would do nicely although i don't know if it includes the exporter tool. You may want to look at the full cht version.
Good point about the radio. I have a UK version so i can use whatever i want. The right radio roms for the TMOUS devices have verison numbers that look like this: 2.xx.50.xx. the 50 bit is important as radios with the 50 in it have the unlock code for the extra ram in them and are compatible with the 1024MB rom chips. Also never ever use a radio with a version number like this: 2.xx.51.xx. The 51 radios will brick your phone and they can not be recovered as far as i am aware.
And yes afaik there is a setting exporter in the WM 6.5 builds
My radio is 2.10.50.26
Is that OK ?
Just how much faster is the 6.5.5 over the regular one ? I'm not liking that lower start button anyway so if it's not really faster i'll pass.
Looks kinda like an iPhone.. Less " serious "
m3ph - what ROM have you had in mind with the Exporter build in and the upper start button and CHT ?
I thank you for all the help... I am feeling positive about my HD2 again.. Can't wait to flash it !
Just making sure I get everything right about all the different Energies so I don't reflash and reflash a thousand times... Making a concious decision
Silencer23 said:
My radio is 2.10.50.26
Is that OK ?
Just how much faster is the 6.5.5 over the regular one ? I'm not liking that lower start button anyway so if it's not really faster i'll pass.
Looks kinda like an iPhone.. Less " serious "
m3ph - what ROM have you had in mind with the Exporter build in and the upper start button and CHT ?
I thank you for all the help... I am feeling positive about my HD2 again.. Can't wait to flash it !
Just making sure I get everything right about all the different Energies so I don't reflash and reflash a thousand times... Making a concious decision
Click to expand...
Click to collapse
the radio will be fine.
The difference in speed is not massive so i wouldn't worry about it.
The rom i'm thinking of will be at this link: http://hotfile.com/dl/50755734/bde591c/Energy.Leo.21907.Sense2.5.Cookie.Jun.26.Take2.7z.html
Sorry if i'm being a little slow. i'm trying to eat my din, while texting the mrs, getting nfs world beta to work and figure out why sense will not show around 3500 of my messages and thinks my sister is my best mate
Deal, I will burn that ROM then, in the 21907 version and settle down.
Does it have the exporter for future upgrades ?
Looks like i'm fixed then ! Thanks ! What version is the faulty Sense that thinks your sister is your best mate ? hahah
Sorry to hear that... my stock ROM still works fine... I did not even update it yet - this one was right from the get-go
Well, I'm on Energy CHT now and IT'S A DIFFERENT PHONE !
WOW.
Thanks guys. You saved my phone and my money !
Now install chainfires 3D driver patch v2 on it and leocpuspeed v4 you'll be shocked.
Wooo Hoo ! This phone is ON FIRE now
Now we're talking !!
Thanks man ! Any more tips ? hehe
What a coincidence. I'm also having lots of problems with my TMobile UK Rom, same freezing, etc.
I have seen quite a few Roms that I'd be interested, but most of them don't mention whether they will work with a locked T-Mobile handset, and if they do, it only refers to TMobile US version.
Will any Rom work on a T-Mobile UK locked handset, or would I also have to flash a new radio. I have 2.07.50 at the moment.
Like I said, I've seen quite a few Roms that I like, but just concerned in case I flash a Rom that's not compatible.
Any advice would be greatly appreciated!
Silencer23 said:
Wooo Hoo ! This phone is ON FIRE now
Now we're talking !!
Thanks man ! Any more tips ? hehe
Click to expand...
Click to collapse
if you have a wifi router in your house get wifi remote access. It allows you to transfer files to and from the phone using a web interface over the wifi. It also allows you to edit the registry "remotely". Really handy little tool that.
Also have a look at omarket. some handy tools can be got from there but be careful not everything is Leo compatible.
Coreplayer is handy if you wanna watch tv shows or movies. just set the video mode to raw frambuffer if the picture looks scrambled. This one isn't free but is definitely worth paying for coz tcpmp (it's free cousin) isn't as good. I also use srs WOWHD with this to improve the sound. look for 1.5 V2.
The only more i can say is use a PIM backup tool regularly. something like MS myphone or PIMBackup. Saves some time if you don't have an exchange server to store you contacts, mail etc
s32bauer said:
What a coincidence. I'm also having lots of problems with my TMobile UK Rom, same freezing, etc.
I have seen quite a few Roms that I'd be interested, but most of them don't mention whether they will work with a locked T-Mobile handset, and if they do, it only refers to TMobile US version.
Will any Rom work on a T-Mobile UK locked handset, or would I also have to flash a new radio. I have 2.07.50 at the moment.
Like I said, I've seen quite a few Roms that I like, but just concerned in case I flash a Rom that's not compatible.
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
My advice to you would be to stick to a rom that says it is tmous compatible. that way it will work on any leo but the phone will still be sim locked. so if you wanted to sim unlock it you would need to get an unlock code from TMOUK