ok....
here's the deal:
I've been using an OEM-package in mylast roms for tomtom version 7.915.
This has been working without troubles.
Now I cooked a new ROM based on new 21018 XIP/SYS
The device really flies and everything seems to working flawless....EXCEPT tomtom.
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
I did not change anything to the OEM-package. So I guess it has something to do with the new SYS.
Do more people have this problem and/or does somebody now the fix....
Thnx all in advance for your help!!
Greetz Merten
p.s. I used the search function of course and saw a lot of similar errors but no sollutions.....
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
crazyC said:
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
Click to expand...
Click to collapse
I got the exact same oem-package working in M-rom v1.71!
So it really beats me why I get the error.
I tried cooking the rom again but still the error....
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
crazyC said:
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
Click to expand...
Click to collapse
Ok OEM can be found here in the map: packages
Package looks OK at first glance - hope to be able to try it tonight and will post back tomorrow with results.
If this doesn't work - you could try simply using the cab via UC etc as I do - I have checked and the cab of the same version in your OEM DOES work for me.
In fact, I think I might leave it in my UC, (but will flash tonight anyway with it just to see)
merten3000 said:
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
Click to expand...
Click to collapse
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
GenghisZ said:
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
Click to expand...
Click to collapse
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
merten3000 said:
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
Click to expand...
Click to collapse
Nope, did not help...
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
crazyC said:
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
Click to expand...
Click to collapse
I always change my roms pp to 32mb...can that make a difference? I did it in v1.71 and tomtom worked fine...
I don't know - I have been around here long enough to know that your skills far outweigh mine. If it used to work then I see no reason for the change.
All I know is that my rom is based on Da_Gs really clean latest (ie 5.08) from his simple kitchen thread (from his post near the end not the first post) plus Eras2rs package updates.
The only other packages I add are a few utilities and personal tweaks. I import an advanced config xml as part of the UC process but that just ensures the various settings in Advanced Config are set to advised etc.
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Harikoss said:
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Click to expand...
Click to collapse
Maps work(ed) fine..
btw I bypassed the error by removing the OEM-package and made it a cab which is installed during system configuration. It takes more system space but this way it is uninstallable....but it remains a mistery to me why the OEM does not work in this SYS and does in 21014 SYS...
Related
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
8-11-2004 20:57 GMT: New version V2 uploaded.
I added a small archive containing the changed ExtROM files to solve the earlier reported errors (not updating ExtROM version and not making IIWPO un-installable).
Comment on IIWPO and making it un-installable: After having customized & installed IIWPO, you will have to do one of the following to make it un-installable if youre using the 1.72.902 ExtROM:
a. Another hard-reset
b. Running Version_172_902.cab from the ExtROM
NOTE: This thread is being replaced by
http://forum.xda-developers.com/viewtopic.php?p=68652#68652
Thank You!!!!!!!!!!!!
I am d/l'ing right now and will be installing shortly...
One request... You might want to include the cab for setting up IIWPO in case someone is installing it into the phone.
edsub Thanks.
Question tho. Can I use this for T-Mobile USA and does it fix the MMS problem ?
asking because the version says NL, isnt that the Netherlands country code ?
Thanks again
Well from first look everything seemed ok.
THese are a few of the things I have noticed since loading.
1. The ext rom version # doesn't show up in the info
2. If you use the IIWPO then it still shows in the remove list
3. The new apps from the 187 version will not install no matter what you do. (I have tried adding the ver # in the Reg, both 902, and 187 (not at same time)) Niether worked.
These are the few things that I have found since loading. If I find any more I will loet you know. Other than these I think you havea winner here!
I was wondering about the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 packages, and why you didn't include or update to them? Was there some incompatibality issue?
Thanks and great job!
Re: Home-cooked 1.72.902 upgrade package (1.72.00/1.17.00) T
edsub said:
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
Click to expand...
Click to collapse
Is SRS included?
SRS is not included due to the fact that I don't see any use for it personally. Since it is an ExtROM installer, you could add it yourself.
The NL is only there because some sdetting are more or less specific to the Netherlands. I had feedback on my earlier 1.72.901 package that it worked for other countries (incl USA) as well. Be prepared that the date format will be dutch by default (easy to change via settings though).
Also MMS is suposed to be working (but I have not tried it due to lack of interest in MMS)
The ExtRom# is not showing because some bug in the Version_172_902.cab. Working on that now.
IIWPO not showing in the remove programs list is a bit more difficult than it seems if you install for the first time. Normally you would boot up the device with new rom. IIWPO is NOT installed at this point. Once you have customised & installed IIWPO, you will have to do ANOTHER hard-reset (ie run the ExtRom contents again) to disable the uninstall. You could force this by hand first time to re-run Version_172_902.cab after installing the customised IIWPO. BUT as this cab is not OK, it wont work anyway. Working on that now.
I did not find the time to look into the new O2 apps. If someone finds a solutiuon here, I am more than happy to includew it in a new version.
For the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 the basic reason is lack of time. I dont know what 'extra' new there is on bluetooth in the O2 builds? OS Rom 1.72 allready has an updated BT stack that fixes most open issues. I have no experience (& interest) in MMS / streaming MMS . . .
I suppose the issue with TomTom locking up without GPS enabled is not solved with this rom ?
I know: wishful thinking..........
@Pleun: Nope. I WISH I would have solved that one!!! FYI: I tested he new TomTom GPS 3.07. It doesnt solve any locking issue and next to that makes my Headset react very slow. Also the 'Bluetooth GPS' option that is supposed to solve the locking has gone, at least with my installation. Not advisable. I reverted back to TomTom GPS 3.03.
@all: I solved the issue of not setting the Ext Rom version and making IIWPO non-uninstallable. New version V2 will be up in 10mins (incl. incremental fix for all that downloaded the version from yesterday).
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
edsub said:
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
Click to expand...
Click to collapse
I feel like my MDA2 is a little bit slower to respond not sure why! I added PocketMVP, Belkin Bluetooth GPS, Resco Explorer 2003 V5.0 and .NET Compact Framework 1.0 SP2 for Pocket PC 2003.
I am having problem with Belkin BT GPS; I got it to bond, detect the COM port (COM5) and baud rate(4800) to use but my MDA2 hangs up and had to soft reset. Any idea why?
I will try to install one by one and see what's causing it and report here.
edsub thanx for me it works great its a great improvement!
machine seems faster and no more lock-ups.
Keep up the good work (ill be following you)
p.s only one thing my battery seems to give me no more than 4 hours of on-time
4 hours is very different from my (and others!) experience. The 1.72 rom should even improve battery life.
My battery lasts for about 1,5 days (not measured but recalled from my memory) with approx 1-1.5 hours on the phone and bluetooth permanently switched on . . .
were can I download this rom from?
from the first msg in this thread : RUU172902WWE_eDsuBsofT V2.exe
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Anonymous said:
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Click to expand...
Click to collapse
You cannot download it as a guest! If you are a member of this forum you have to log-in before you can see the file you want to download. That's what I encountered before so just try logging in first.
Good luck!
THank you very much superperry. Should have registered before but was always too lazy.
I have put together rom upgrade 1.72.903
This thread can be closed. See http://forum.xda-developers.com/viewtopic.php?p=68652#68652 for the new one
Edit: The new upgrade files are now available (see refered post)
An error need help please
I downloaded the files then followed the instruction below but now I get error
the flashing process
first the devicedata is obtained from the device, with HimaGetDeviceData.exe, this gets the operatorname, and language/country code from the extended rom, sector 2 of the BDK.
Then a tool 'HimaClearJumpCode' is executed, which erases the jump at the start of the kernel. causing the bootloader to start at next reboot.
the upgrade tool then connects to the bootloader of the xda, via serial over usb. ( port \\.\WCEUSBSH001 )
warning do not just run the 'HimaClearJumpCode' program, it will erase part of your OS rom, after which you will have to repair your device by running an entire upgrade again.
This is essentially the excellent Korand 3.1, but with UC compatibility, enabling easier switching between ROMs.
UC info
UC allows customization using a storage card, and so allows for completely individual customization of any UC compatible ROM.
Without a storage card, this should run as it normally does.
For info on UC look here!
I'm currently working on a Touch Edition. I have a beta version I'm uploading. If anyone wants to test it, I'll post the link here.
Upgrade guide:
README
Dowload:
rapidshare
SkyDrive
TE beta 1
Thanks to:
Korand for the base ROM here
Sleuth255 for UC here and here
good to make UC compatible..
Good job ..
yup thanx for this useful post
i was wondering if i could find the wm6 uc compitable rom
Thanx
If you get any problems with UC please tell me so I can sort them... Or at least try to.
Thank you very much!
does this work for G3 and G4?????
I am interesting in the Touch ROM! Is this also based on the Final version of WM6.1?
does this work for G3 and G4?????
Click to expand...
Click to collapse
Should do. You need to download the update utilities linked in the How To.
I am interesting in the Touch ROM! Is this also based on the Final version of WM6.1?
Click to expand...
Click to collapse
It will be based on the same ROM, but with extra features like the cube.
l3v5y..
What here is, is not final version from Cloudyfa..
He has already dump the other one from kaiser.. And solved this WPA 2 problem..
But need to fixed something on SD Card bugs..
I downloaded the Touch ROM and I flashed it succesfully.
But during the ROM customization progress it is stuck on 'running SDautorun.exe' and does not continue anymore. I waited for about 30 minutes and soft resetted my device. The device starts, but now I have a very clean ROM (no sign off any Touch items).
Can anybody help me with this problem?
There are two reasons for this:
I didn't add a security pack that allows certain (unsigned apps) to be used.
The initflash file (what places shortcut files in the right place) was not edited properly and so shortcuts to apps are not in the correct place/not there at all.
hi l3v5y,
Happened to me the same thing. I can confirm that the shortcuts in my case are correct.
Questions:
1 - can I choose diferent folders for the cabs?
2 - Is the program case sensitive?
best regards
RP
For info on UC, see this http://forum.xda-developers.com/showthread.php?t=366337 if that fails to answer your questions I shall try to answer them myself.
I've been trying for more then a week now to get my next rom UC but it just will not work so any info on how you got it to work would be grate
does anyof it work? does sdautorun.exe start?
l3v5y said:
does anyof it work? does sdautorun.exe start?
Click to expand...
Click to collapse
yes it starts but does not end installing I tried putting the SDautorun on my sdcard and run it gives an error that it's not signed
gullum said:
yes it starts but does not end installing I tried putting the SDautorun on my sdcard and run it gives an error that it's not signed
Click to expand...
Click to collapse
It might need to add a key setting in reg:
SDAutoRun is not signed so security must be relaxed in HKLM\Security\Policies\Polices by setting the value 0000101C to a 1
check:
http://forum.xda-developers.com/showpost.php?p=1896885&postcount=1
ufriendxda said:
It might need to add a key setting in reg:
SDAutoRun is not signed so security must be relaxed in HKLM\Security\Policies\Polices by setting the value 0000101C to a 1
check:
http://forum.xda-developers.com/showpost.php?p=1896885&postcount=1
Click to expand...
Click to collapse
I did that but might have goten it lost again because I've changed lost of stuff I'll check it again and thanks
I had that happen, but at some point when importing a package, the error stopped.
If you take the SD card out, and then wait after a hard reset, it should reset.
M-ROM v1.1
ROM Language: Dutch
Based on shipped NLD rom 1.90.404.1
But ROM updated to build 20755.1.4.0 (XIP/SYS ported)
and this has been done...
Updated:
- Net CF v3.5
- GoogleMaps (NLD) v2.2.0.19
Added:
- UC
- Alternate sliding sounds (transformers, star trek, etc)
- Advanced Config v3.3
- TF3D config v6.7
- TomTom Navigator v7.451.903
- Klaxon 2.0.19
- Lightsaber v1.0
- MS Voice command v1.6.19209
- WMRegOptimizer
Removed:
- removed introduction video
- removed customers feedback
- removed autoupdate
- removed Cyberon speeddial
- removed sample music / wallpapers
- removed MP3 Cutter
Tweaks:
- Disabled SMS-threading
- Disabled Security warnings when installing non-certified applications
- Many speed improving tweaks...
!! UPLOADED NEW VERSION (23/10/2008) !!
Working on M-Rom v1.2 (build 20924.1.5.0) Be patient....
Download DOWN! ! updated !
RAR-password: XDA-Forever
notes:
- I'm still deployed in Afrika without my TP so no chance for testing the rom myself!
- This ROM is UNprotected and maybe tweaked by everybody to fit their own needs! background discussion found here
Looks like I've wasted my entire Saturday morning by doing the exact same thing!
Well done though merten3000 - much appreciated!
Great
Good work.... many thanks for the contribution mate...
Anyone feel like adding this to the wiki?
mrvanx said:
Anyone feel like adding this to the wiki?
Click to expand...
Click to collapse
Wait for some reactions first...like I noted I could not test the ROM myself...unfortunatly
Maybe it is full of errors or does not even boot...still a cook no chef...
Excellent. I'm gonna try it tomorrow just to see if I can teach it to speak Czech.. big tu.
And? How the ROM? Anybody tested him?
mattcrow said:
And? How the ROM? Anybody tested him?
Click to expand...
Click to collapse
My thoughts exactly...
i will givde it a try 2morrow. i'll post back here.
I just flashed your ROM but I cant get over the first screen - The one that says the versions in the bottom. Have been waiting to get the phone booted for over 5 mins already.
Back to my Pdaviet ROM I think.
Edit: Yep, flashing previous ROM (Pdaviet) from card.
crocodile010 said:
I just flashed your ROM but I cant get over the first screen - The one that says the versions in the bottom. Have been waiting to get the phone booted for over 5 mins already.
Back to my Pdaviet ROM I think.
Edit: Yep, flashing previous ROM (Pdaviet) from card.
Click to expand...
Click to collapse
So the flashing went well, but after that the reboot did not work? Damn!
It's sh*tty that I can't flash myself to test.
Maybe another cook can take a look as it is unprotected...
tbh it sounds like a symptom of not porting the XIP across correctly, i'll take a look and see if theres some overlap errors.
EDIT:: I see no overlaps in the maps list however i cant be sure the XIP is a functional one. Im wondering did you port the XIP across using the normal technique or was it just a straight copy and paste from the doner device?
mrvanx said:
tbh it sounds like a symptom of not porting the XIP across correctly, i'll take a look and see if theres some overlap errors.
EDIT:: I see no overlaps in the maps list however i cant be sure the XIP is a functional one. Im wondering did you port the XIP across using the normal technique or was it just a straight copy and paste from the doner device?
Click to expand...
Click to collapse
I extracted xip.bin from a functional Raphael 20755 build and merged it in the payload using write2 option in xiptools. Because it was a working Raph rom I thought I did not need to change the device-specific OEMkernel? Maybe I thought wrong?
p.s. When I was looking for the problem myself yesterday I noticed that in boot.rgu (in ROM folder) the the MUI values keep changing back to 409 instead of 413. I changed them many times, but when I build the rom and dump it again, it is changed back to 409??? I already went through the hives and boot.ms.rgu but can not find those entries there...
The only thing you need to do is to put the .nb (which you want to use the XIP from) into the ROM folder, the build process will take the nb and replace only the OEM and SYS components in it, so aslong as you port the SYS across correctly then the XIP will be in the nb correctly.
Just to make sure though did you write the xip into the os.nb.payload?? (you cant write it into os.nb, it must be the payload section of it, also make sure the address is 03200000 instead of 03100000).
mrvanx said:
The only thing you need to do is to put the .nb (which you want to use the XIP from) into the ROM folder, the build process will take the nb and replace only the OEM and SYS components in it, so aslong as you port the SYS across correctly then the XIP will be in the nb correctly.
Just to make sure though did you write the xip into the os.nb.payload?? (you cant write it into os.nb, it must be the payload section of it, also make sure the address is 03200000 instead of 03100000).
Click to expand...
Click to collapse
Thnx again, I will look into it and repost if I succeed..
I did use the payload, but will check the adress to be sure!
! UPDATED FIRST POST !
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
karloe said:
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
Click to expand...
Click to collapse
Thnx for testing man...but WTF is wrong woth this rom??
Need some expert help I think:
- 1) I used a 20755 XIP whitch I manually changed to raphael (Kept original raphael Oemkernel). Used xipport to dump the XIP.bin files, made packages etc. But when recompiling the xip_out.bin each time I got errors that .txt files where missing for some of the package maps. But I did not touch those files. Anyway no luck with recompiling a working xip.bin
- 2) Almost same as above but did not make packages. In dump folder replaced all the right files (kernel + kerneltk) and again kept original OEMkernel files. Then I was able to recompile a XIP.bin but xipport created a file witch was 4/5 the size compared with the original one...that's no good I think also. So no luck this way
- 3) Extracted a xip.bin from a WORKING raphael 20755 rom using the raph kitchen. Merged it into the payload file using xiptools (but could not input adress there 003200000....?) That was the first version I uploaded.
- 4) Yesterday I used the extracted xip.bin again. But this time I merged it directly into the os.nb file to the right adress (003200000 instead of 003100000) using XIPPORT. That is the version I uploaded yesterday
Can somebody tell me what I'm doing wrong?? I'm getting quite desperate right now...
Any help is appreciated!
karloe said:
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
Click to expand...
Click to collapse
Again after some tips (thnx MrVanx) I spent a whole night working at the ROM.
I revised the XIP and SYS totally and I think it maybe will work this time (it would be about time!)
Will upload tonight as I will not be around during the day
Karloe: I wil use rapidshare again, but pm about your privat upload space, thnx
What do you mean with unprotected rom btw
Like rome os with tweaks,other software and stuff,or something special?
Thx in advanced,greetings martijn from the netherlands also
http://www.htc.com/www/SupportDownload.aspx?p_id=133&cat=0&dl_id=538
It's for the Diamond, but assuming it works on the Raph, Da_G, can you work your magic and integrate whatever's needed from here into your kitchen(s)?
OEM_Misc.dll
Extracted Diamond_audioplayback.exe contents, verified _Setup.xml, Platformxxx.reg and CM_Entries.xml:
- No registry changes
- Attached file is copied to .\Windows folder on device
Place file in .\OEM\OEMDrivers if cooking in kitchen.
Cheers,
Thanks -- trying it in my own ROM now ...
hilaireg is way ahead of me
ill check it out when i get home from the hospital! sounds good
Super-newbie question: What did you use to extract it from the EXE?
@Da_G:
Figured your queue was full enough as it is
@Wordsmith9091:
I used WinRAR 3.3 (IZArc 3.81 couldn't open the .EXE). Once it was extracted, I had a look at _setup.XML as it contains the short-to-long filename conversion details.
I renamed the pertinent files (previous post) and had a look at the content in those to ensure that there were no special requirements.
I used IZArc 3.81 to .ZIP up the file so that it could be posted here.
Thanks -- I learn a new trick every time I come to this site
Just tried building my ROM with it, all seems well so far, though I havne't played enough audio to test yet ...
... but I lost the ability to set button assignments other than Button-1-hold in the buttons panel -- it's like the stock behavior. Is that also controlled by this DLL?
Edit: Never mind, I'm a moron, this issue had nothing to do with this DLL
I don't think so ... the Stock HTC ROM only included "Button 1" which drives me crazy.
I've got a task on my list to deal with that I soon as I'm done some other kitchen related stuff.
I'll post up - unless someone beats me to it - once I figure out how to get button mapping.
Cheers,
I can't be 100 percent sure it's what interfered with button mapping, but it's the only thing I can think of that i've done different between builds.
Since this fix only requires a single DLL copied to the \Windows folder, I was able to cab it up using ChainFire's DriverWiz tool, and install it. I stream music via A2DP during every car ride, so I'll be able to test this on my ride home. I'll attach the cab if anyone else wants to try it as well.
You make me proud Captain
Following your lead, I have attached a .ZIP that can be used in a kitchen; to use:
Extract the .ZIP to the PACKAGES folder.
Verify that the <GUID>'s on the .DSM don't collide with ones you are currently using.
Remove the OEM_MISC.DLL from the .\OEM\OEMDrivers folder.
Cook away.
Note:
Tested on Da_G's (ERAS2R/Me) 21042 kitchen.
HTH,
HTC Diamond Hotfix..
Many thanks Captain_Throwback for the CAB, am testing Music Player now. The HTC version will not install on the Orange Diamond says 'Not Compatible'.
... 25mins in..clean as a whistle!!
....3 albums in, job done.
Never mind on the button-mapping question. I realize what I did (I think). HAd nothing to do with this dll.
Any info you can pass my way?
hilaireg -- PMed you.
Well, I drove around for a bit after cooking this in and reflashing, and I still got some skips listening to music in Kinoma Play. Don't know if that's Kinoma's fault or if it's a symptom of the problem this is meant to address. I wasn't getting any skipping with the TF3D player even before applying this.
improvement?
I saw a noticeable improvement in the length of pauses in between my songs while streaming over A2DP (though it did get stuck on me after about 20 minutes). Its better than it was . . . I think. I don't know if there's really a scientific way to test this, really. Maybe the problem this is supposed to address isn't that at all. Maybe we need to find someone who actually KNOWS they have this problem, so we can see if the fix really helps.
Hotfix for Diamond..
I have a Diamond on the Orange Network with the stock HTC 1.93 ROM. It used to skip every 5 mins but after installing your CAB it is now perfect, not a glitch. I am a very happy bunny. Thanks for your work Captain..
looby said:
I have a Diamond on the Orange Network with the stock HTC 1.93 ROM. It used to skip every 5 mins but after installing your CAB it is now perfect, not a glitch. I am a very happy bunny. Thanks for your work Captain..
Click to expand...
Click to collapse
All I did was make the cab. Wordsmith found it, and hilaireg extracted it. Its a team effort. That's what a community is all about .
Captain_Throwback said:
All I did was make the cab. Wordsmith found it, and hilaireg extracted it. Its a team effort. That's what a community is all about .
Click to expand...
Click to collapse
And if he has a diamond, he could probably just install the hotfix directly from HTC
Wordsmith9091 said:
And if he has a diamond, he could probably just install the hotfix directly from HTC
Click to expand...
Click to collapse
He already tried that . . .
looby said:
Many thanks Captain_Throwback for the CAB, am testing Music Player now. The HTC version will not install on the Orange Diamond says 'Not Compatible'.
Click to expand...
Click to collapse
So I am trying to get Album 3 to work with my ROM. I have tried many different packages with the same results. The menu text is way too small and now the screen just turns red. I have checked everything I could think of, was actually working on it for a good part of the day and I am so stuck. If I install it via cab it works fine.
Any ideas...anyone?
Can catch me on AIM, Yahoo or MSN. Use the same screen name as here and/or add live.com or yahoo.com
Thanks!
At0mAng, been a while since I made Legacypackages, but can you give this one a try? If you are having problems you may need the Album package to be introduced to the ROM at the end of the process. I forget with Legacy, but does OEM run last? might need to make it an OEM instead of Package with option(which I am attatching). Good luck
jmckeejr said:
At0mAng, been a while since I made Legacypackages, but can you give this one a try? If you are having problems you may need the Album package to be introduced to the ROM at the end of the process. I forget with Legacy, but does OEM run last? might need to make it an OEM instead of Package with option(which I am attatching). Good luck
Click to expand...
Click to collapse
Thanks I will try. I am thinking it might be one of the OEM packages in my OEM folder causing a problem somewhere. Since I have been not cooking for awhile I am not sure what packages I can safely remove from OEM folder since TF3D2 and some other stuff have different dependecies. Tried a few things but nothing works. Does Album 3.X work on 6.1? I am running 21051.
At0mAng said:
Thanks I will try. I am thinking it might be one of the OEM packages in my OEM folder causing a problem somewhere. Since I have been not cooking for awhile I am not sure what packages I can safely remove from OEM folder since TF3D2 and some other stuff have different dependecies. Tried a few things but nothing works. Does Album 3.X work on 6.1? I am running 21051.
Click to expand...
Click to collapse
I believe it does. I seem to recall having it working on a 6.1 ROM. But I think I had that font issue when I didn't have Media Toolkit (photopicker) included. Or maybe you just have an incompatible version? (or maybe I don't know what I'm talking about)
Captain_Throwback said:
I believe it does. I seem to recall having it working on a 6.1 ROM. But I think I had that font issue when I didn't have Media Toolkit (photopicker) included. Or maybe you just have an incompatible version? (or maybe I don't know what I'm talking about)
Click to expand...
Click to collapse
I gave up on Album 3. I thought photopicker had to be included. I tried many versions...
If it installs from CAB, it works well so everything that it needs is in ROM. The packages I tried must be missing a file. I thought it was the mui file, tried a few but with no luck. If you are anyone has the mui that works properly with it please post it
The only file that was missing was the mui so I am guessing it is that or a combo of things...
Try mine my friend, i found these ones with 0409 mui files, these ones always worked fine on my kitchens.
Cheers.
ark666 said:
Try mine my friend, i found these ones with 0409 mui files, these ones always worked fine on my kitchens.
Cheers.
Click to expand...
Click to collapse
Thank you very much! Will give them a shot and see what happens.
I am rebuilding my kitchen from scratch to try to find what the issue is
I believe that the issue is to do with an xml file in the album package, ha_skin_*.xml these need replacing or deleting. I cant remember which now. Do a search and this should bring this answer up