Database Users

Improve FM Radio Library Build 103.816

I think this FM Radio is improved as far as reception concerned. Less interference noticed overall. Back up the current library (just in case you don't like this one) from the Windows directory and replace it with the files in the zip.

Where does it come from ?

plopplop said:
Where does it come from ?
Click to expand...
Click to collapse
From udk's latest ROM

Is there a possibilitie to change the fm radio with a working wm6.1 rom already flashed because when i try to copy the files over the files on my device i get a error that i cant override them.

Ajacied410 said:
Is there a possibilitie to change the fm radio with a working wm6.1 rom already flashed because when i try to copy the files over the files on my device i get a error that i cant override them.
Click to expand...
Click to collapse
use total commander or resco explorer. Either will over-write the libraries.
It would be great to make a cab file out of it. Could anybody help with it?

mffu said:
use total commander or resco explorer. Either will over-write the libraries.
It would be great to make a cab file out of it. Could anybody help with it?
Click to expand...
Click to collapse
That depends - what are all the needed Registry entries ? It's simple enough to have all the files in the zip CAB'd to install in \Windows, but are there Registry entries needed beyond these ?

i tried it yesterday.Copy all files in Windows folder with resco,check version and see version number is ok.I listened to radio all night and havent a problem

ianl8888 said:
That depends - what are all the needed Registry entries ? It's simple enough to have all the files in the zip CAB'd to install in \Windows, but are there Registry entries needed beyond these ?
Click to expand...
Click to collapse
This library is complete. You can unzip it to the storage card, tap on the FM Radio.exe and it will work. I believe we need a cab maker. That type of program writes everything into the registry during the installation.

Thanks. I will try this one tonight ... ;-)

mffu said:
I believe we need a cab maker.
Click to expand...
Click to collapse
Here you go.
Tested. Works.
Sascha

The PDAViet rom also has version 1211.721 which also has better reception than the one on the stock rom. Now I can use my favourite headset which had poor reception, maybe due to shorter length than some crappy one I had

SaBo said:
Here you go.
Tested. Works.
Sascha
Click to expand...
Click to collapse
Doesn't work on my Cruise. Stock ROM. The App doesn't want to start.

Neither the cab not the zip works. I thought that my sprite backup would have the original Files from the rom,it does not. Does anyone have the stock radio files to get my radio working again?
TIA!
EDIT: It looks like I have lost the ability to launch the radio app. At this point, I really don't want to do a hard reset. Don't apply this update unless you are willing to lose this function.

victoradjei said:
The PDAViet rom also has version 1211.721 which also has better reception than the one on the stock rom. Now I can use my favourite headset which had poor reception, maybe due to shorter length than some crappy one I had
Click to expand...
Click to collapse
this is the default version that i have on my HTC Polaris/Cruise.

I'd like to backup my files before copying the new one but can't copy fms_api.dll, even using Resco explorer...

Doesn't work on my Cruise. Raramomo ROM. The App doesn't want to start.
Has somebody a cab of the original radio ?

LIPA said:
Doesn't work on my Cruise. Raramomo ROM. The App doesn't want to start.
Click to expand...
Click to collapse
What application doesn't start?
The CAB can only be installed if you turn certification off.
I don't know if this is possible with all stock ROMs.
Sascha

SaBo said:
What application doesn't start?
The CAB can only be installed if you turn certification off.
I don't know if this is possible with all stock ROMs.
Sascha
Click to expand...
Click to collapse
The FMRadio.exe does not start. The cab was installed properly without issue.

mffu said:
That type of program writes everything into the registry during the installation.
Click to expand...
Click to collapse
Yes, I know that - it was the point of my post.
But what I asked is: "Are there any other Registry entries that need updating ?"
The answer seems to be - apparently not, since another post reported it as working by just copying the unzipped files into \Windows ... but other posts reported this as not working.
Generating a CAB is easy of course, making sure it actually works may be harder.

E.Bonobox said:
this is the default version that i have on my HTC Polaris/Cruise.
Click to expand...
Click to collapse
The FM Radio I posted is better than the PDAViet's one. I have less interference or static after I upgraded to it. I am on PDAViets's 06 build and I get a clear and crisp signal off the stations I had the crappy static with the original build.
And YES, you got to have the security policies changed in order to overwrite some files in the Windows directory. Search for the SDA Application unlocker. That should fix the problem with upgrading.
In my first post I mentioned about backing up the original files. If you happened to fail doing so, try to find Dutty's FM Radio cab.
Thank you!

Flashing screw up

Hiya,
been having major issues with my HTC so thought it was about time to put a new rom and radio on it.
Was following this thread http://forum.xda-developers.com/showthread.php?t=505377
Got down to step (USPL5d) and just couldn't seem to get it to work. Trying to flash on Duttys HD WM6.5 Leo Holy Grail R0 WWE
Based Rom 1.59 ( CE OS Build 5.2.21869.5.0.82 )
Got lost where I was meant to be posting what, regardless keeps saying updating to version 1.54. Pasted stuff into rom folder, rom folder into wrapper folder, moved .nbh around but couldn't get it to work?
Also, where is BLACIMG.NBH?
Many thanks

Hi.
RUU_Signed.nbh is the BLACIMG.nbh.
If you want to upgrade the rom using the micro sd card you have to rename the
RUU_Signed.nbh to BLACIMG.nbh.
But you want to update using USPL so you do NOT have to rename the file.
And the tutorial is good but have to do exactly what is stated there.
I am using HSPL so this is all i can help.
Any problems i am sure someone is going to help.
Good luck.

Hi,
Many thanks for the info. It appears I may have downloaded an incomplete file. Have since tried again with a different file and seems to have worked.
I have managed to flash the radio as well, although haven't a clue how to check what version it was. Took me months to get the phone sorted when I first got it with Tom tom etc, seems like I gotta go through this all over again

Go to the device information in the settings-system
and there is a software information section were you can find rom ,radio and other info.

Rom not booting

I have made a rom using new ervious visual bepe's kitchen.
i dumped two stock roms
1:- 1.66 stock
2:- 1.72 t-mobile stock
i simply replaced some folders from 1.66 stock into 1.72 stock which were operator package and operater pt.
and i converted a manila document tab from cab into EXT and copied into the dumped EXT. whose Path is like this ( C:/ dump/ext/leo/21869/Leo_external_packages)
and then i opened the kitchen and clicked on Button " REAL WM 6.5 AKU and changed its pagepool to 18mb and and changed the value of modules to 1000 in other options.
clicked on create rom and rom created succesfully without any error..
I flashed the rom into my hd2. it completed with no error and i performed several times hard reset also.
Now when i am trying to start the hd2 it stucks on welcome screen setup. no hardware buttons working.
what i have done wrong????
what mistake i made in between making the rom???
Kindly help..!!!!!!!!!!!!!!

no one have the answer for this problem?????????
c'mon friends.. help me out...

By 1.72 Tmobile ROM I assume a NON USA Tmobile ROM. If that's the case then it should work fine.. however if you cooked up a Tmobile US ROM, your phone will not boot unless you also flash a TMO US radio. Try a different radio and see if your ROM boots.

mon_money said:
I have made a rom using new ervious visual bepe's kitchen.
i dumped two stock roms
1:- 1.66 stock
2:- 1.72 t-mobile stock
i simply replaced some folders from 1.66 stock into 1.72 stock which were operator package and operater pt.
and i converted a manila document tab from cab into EXT and copied into the dumped EXT. whose Path is like this ( C:/ dump/ext/leo/21869/Leo_external_packages)
and then i opened the kitchen and clicked on Button " REAL WM 6.5 AKU and changed its pagepool to 18mb and and changed the value of modules to 1000 in other options.
clicked on create rom and rom created succesfully without any error..
I flashed the rom into my hd2. it completed with no error and i performed several times hard reset also.
Now when i am trying to start the hd2 it stucks on welcome screen setup. no hardware buttons working.
what i have done wrong????
what mistake i made in between making the rom???
Kindly help..!!!!!!!!!!!!!!
Click to expand...
Click to collapse
i think he means the european tmobile uk rom..
this is a common problem..:
you have to change ntconfig.dll (from notification enhancement) from module to file.

HD2Owner said:
i think he means the european tmobile uk rom..
this is a common problem..:
you have to change ntconfig.dll (from notification enhancement) from module to file.
Click to expand...
Click to collapse
Ah! Didn't think of that... He wasnt really clear what the "welcome" screen means, I assumed that would have been the initial splash screen.
But if the ROM boots past the 'red letters" then yeah, recmodding the notification manager DLLs will fix that

HD2Owner said:
i think he means the european tmobile uk rom..
this is a common problem..:
you have to change ntconfig.dll (from notification enhancement) from module to file.
Click to expand...
Click to collapse
first of all thanks for your help..
HOw can i change the ntconfig.dll module into a file???????

rom which i am using is a branded rom from t mobile uk.. and have mix some content of generic 1.66 rom with this t mobile rom which i already mentioned above..

NRGZ28 said:
Ah! Didn't think of that... He wasnt really clear what the "welcome" screen means, I assumed that would have been the initial splash screen.
But if the ROM boots past the 'red letters" then yeah, recmodding the notification manager DLLs will fix that
Click to expand...
Click to collapse
thank you nrgz for your help..
kindly tell me how to do that??? how can i fix notification .dll modules??
Look for an exe called recmod.exe or reversemode.exe. For now. to see if this is your problem just exclude the notification manager form you rom

[Problem] [ERROR]Please check HTCLOG

I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch

millski said:
I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch
Click to expand...
Click to collapse
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.

TMartin03 said:
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.
Click to expand...
Click to collapse
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work

millski said:
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work
Click to expand...
Click to collapse
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.

TMartin03 said:
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.
Click to expand...
Click to collapse
Tried that, still wouldn't work. If I cook without RunCC the ROM will boot without error, but then the initial customisation doesn't run i.e. no SIM or operator settings are made.
I don't think I'm going to get to the bottom of this so I've started building a new kitchen. Does anyone know which packs from Leo 2.14 will make my ROM TMOUS HD2 compatible? I can't remember...

[Q] About to give up! Trying to load ANDROID on HTC HD2 Please Help!

Ok, every worked fine my Phone details are:
OS version 5.2.21864 (21864.5.0.81)
Manila version 2.5.19202525.0
Rom version 1.43.110.2 (70315) WWE
ROM date 10/28/09 Radio version 2.12.50.02_2
Protocol version 15.40.50.07U
HSPL3 installed
Have cleared all added apps, factory reset, formatted sd card but android won't start left for 30 mins each time once overnight tried 5 times so far, with 3 diffrent builds seems to be doing something has got some failed script e.g.: failed to allocate the storage and something to do with e2sck1.41.4 Seems to be liking the battery alot in the script a page worth.
Any ideas?

Try to install the new official 3.14 HD2 rom en put a folder on ur SD card called "Android" and in that folder all the correct files. Maybe that works for u

Downloading now will give that a try.

Your radio MUST have .50 in it, not .51. I would suggest making sure you have a compatible radio or you will be wasting your time...

Ok that rolled back the radio, so have tried to re-install custom RUU and won't let me install the radio again and it won't install...pants. (edit) have found tha HSPL need re-adding, have now installed custom RUU still not loading android....
gets too:
Superblock invalid / mount failed
loads of script about the battery
Any idea?
Oh yes happy to admit I am a n00b at this.

Traffic187 said:
Ok that rolled back the radio, so have tried to re-install custom RUU and won't let me install the radio again and it won't install...pants. Any one else got an Idea?
Click to expand...
Click to collapse
What HD2 do you have in the first place? Assuming you have TMO-US HD2 according to the radio version you described here is what you need:
HSPL3 installed (make sure that you chose 2.08 in the drop-down menu);
CustomROM based on 3.14WWE latest T-Mobile / HTC update;
Radio Version you should go with is 2.15.50.xx;
and depending on what Android Build you go with place "Android" folder on the root of your sd card. If it does not load, try to delete Android folder and then copy only the content of the Android folder into the root of the sd card... it really depends how devs make it to work...
I got HSPL3, Energy 2.5GTX 3.14, Radio 2.15 and HyperDroid 1.7 with mychprima's kernel OCd and UVd - and everythign works perfect.
If it still gives you problems you have probably messed up in the beginning with HSPL maybe or something...

Sorted, lol I am UK not use was install HSPL3 I needed 2 Thanks for your answer I am sure others will find it most useful. Cheers