Hey, there, guys...
It's me, little old Bruno, the Iolite and Mega Chef...
I just bought a Leo and I'm cooking for it, but the most advanced base I can have is a 1.80 based Kitchen...
If I have any other than that, for some stupid reason, I can't boot after the RUNCC reboots my device...
It hangs at the welcomehead screen with the light a little dimmed IF I HAVE THE SD CARD INSERTED...
Otherwise it will boot fine...
Obviously I have read many threads and used search, but it appears no one else is having this issue... Only the FM Radio and Wireless issues that come from using the 2.14 / 3.04 Drivers bundle.
I know this is a driver issue and I was wondering if you have got a working 2.14 or 3.04 based kitchen that I can have so I can start my cooking...
On a quick note:
I am using the 3.04 EXT Packages + 3.04 OEMDrivers, OEMDriversHigh, OEMMisc folders + 2.14 nk.exe only
Best regards,
billabongstaff said:
Hey, there, guys...
It's me, little old Bruno, the Iolite and Mega Chef...
I just bought a Leo and I'm cooking for it, but the most advanced base I can have is a 1.80 based Kitchen...
If I have any other than that, for some stupid reason, I can't boot after the RUNCC reboots my device...
It hangs at the welcomehead screen with the light a little dimmed IF I HAVE THE SD CARD INSERTED...
Otherwise it will boot fine...
Obviously I have read many threads and used search, but it appears no one else is having this issue... Only the FM Radio and Wireless issues that come from using the 2.14 / 3.04 Drivers bundle.
I know this is a driver issue and I was wondering if you have got a working 2.14 or 3.04 based kitchen that I can have so I can start my cooking...
On a quick note:
I am using the 3.04 EXT Packages + 3.04 OEMDrivers, OEMDriversHigh, OEMMisc folders + 2.14 nk.exe only
Best regards,
Click to expand...
Click to collapse
Hello.
Download that kitchen as base and add the 3.04 OEMDrivers, OEMDriversHigh, OEMMisc folders as is it.
http://www.vbnfiles.com/xda/birkoffsjunk/Chucky/ChuckyKitchen.July.23.7z
For the fm radio the solution is here:
http://forum.xda-developers.com/showthread.php?t=618787
For the MAC the solution is to replace the bcmsddhd.dll from 2.14 driver folder.
http://forum.xda-developers.com/showpost.php?p=7293946&postcount=2
That's it. If you have problem's after that then look at your EXT package's or post here.
Thank's.
ausdim said:
Hello.
Download that kitchen as base and add the 3.04 OEMDrivers, OEMDriversHigh, OEMMisc folders as is it.
http://www.vbnfiles.com/xda/birkoffsjunk/Chucky/ChuckyKitchen.July.23.7z
For the fm radio the solution is here:
http://forum.xda-developers.com/showthread.php?t=618787
For the MAC the solution is to replace the bcmsddhd.dll from 2.14 driver folder.
http://forum.xda-developers.com/showpost.php?p=7293946&postcount=2
That's it. If you have problem's after that then look at your EXT package's or post here.
Thank's.
Click to expand...
Click to collapse
Didn't work...
And my custom EXT package works both on Iolite and Mega, so that's not it...
Maybe it's the HTC EXT packages??? I used every EXT packages from 3.04 and only a couple from another build (like Task Manager)... Is there any package I should exclude for it to boot?
I'll upload the build_log.txt...
Build_log here.
Thank you for your help...
Best regards,
Might be notification enhancment. Did you recmod it?
Not sure what kitchen you are using but I would dump the ship ROM in to your kitchen first Recmod NTConfig.dll then try to rebuild the ROM. When successful replace SYS and try again.
I'm personally using 2.14 as a base with EXT from 3.04. Some people have reported problems with the 3.04 base. You can get it to work but as mentioned you have to change out some drivers etc.
What device are the kitchen for ?
Ext packs 3.04 are made for HD2 WVGA basically
I had problem with 3.04 OEMs with "normal" HD2 but did not spend time to investigate further or attempted to fix it, perhaps some of you may help.
Here are a few as I remembered...
The WiFi driver broke the MAC address (which file is it?)
The RAM/device storage size became way smaller.
However, most fo the EXTs are working except very few...
maesus said:
I had problem with 3.04 OEMs with "normal" HD2 but did not spend time to investigate further or attempted to fix it, perhaps some of you may help.
Here are a few as I remembered...
The WiFi driver broke the MAC address (which file is it?)
The RAM/device storage size became way smaller.
However, most fo the EXTs are working except very few...
Click to expand...
Click to collapse
if you use Leo S 3.04, you need to replace nk.exe from earlier rom, say 2.14. I had this prob where all the ram and storage is reduced, someone here pointed it out to me.
HD2Owner said:
to fix the fm-radio (3.xx)
replace oemextdll.dll and oem_misc.dll with the ones from 2.XX-rom
to fix asian wifi (3.04tw):
bcmsddhd.dll from 2.XX-rom
Click to expand...
Click to collapse
to fix the low memory issue:
use nk.exe from 2.xx-rom
to fix tmous-compatibility:
use nk.exe and os.nb.payload from 2.xx-rom
btw:
why did you open two identical threads in different sections???????
Got the same strange problems but only if I'm using OEMDrivers and OEMDriversHigh from ROMs newer than 2.13 ...! OEMXipKernel with patched nk.exe works great but no OEMDrivers! >.<
I have a kitchen out. It's a TMOUS with 2.13 OEM and upgraded EXT's to 3.04. It's an EVK kitchen, here's the link:
[Kitchen] [7-5-10] RSToyGuy's TMO.US EVK 2.07 /\ DIY 3.15 Kitchens
rstoyguy said:
I have a kitchen out. It's a TMOUS with 2.13 OEM and upgraded EXT's to 3.04. It's an EVK kitchen, here's the link:
[Kitchen] [7-5-10] RSToyGuy's TMO.US EVK 2.07 /\ DIY 3.15 Kitchens
Click to expand...
Click to collapse
EXT packages aren't that problem, the problem is OEMDrivers and OEMDriversHigh!
Related
Hi,
I've done research on the forum here and found that to unlock the full 576 RAM in HD2 you need two things from the TMOUS ROM. The Radio and nk.exe. I've managed to download the appropriate Radio to unlock the memory but cannot for the life of me understand how to get the nk.exe.
I am using osKitchen Kitchen v1.25 to cook my roms. It uses the following structure under the Sources folder:
EXT
MSXIPKernel
NK
OEM
Other
ROM
SYS
Replacing the NK folder in the TMOUK kitchen from the TMOUS ROM simply does not work the resultant ROM does not boot and just hangs the device.
Could one of our chefs please explain how to port the nk.exe from the US build to unlock the memory in the T-Mobile UK ROM 1.72.
Using the following 576-enabled Radio
RUU_Leo_Radio_15.34.50.07U_2.08.50.08_2
Many thanks in advance
Mod edit: SOLVED
thecrater said:
Hi,
I've done research on the forum here and found that to unlock the full 576 RAM in HD2 you need two things from the TMOUS ROM. The Radio and nk.exe. I've managed to download the appropriate Radio to unlock the memory but cannot for the life of me understand how to get the nk.exe.
I am using osKitchen Kitchen v1.25 to cook my roms. It uses the following structure under the Sources folder:
EXT
MSXIPKernel
NK
OEM
Other
ROM
SYS
Replacing the NK folder in the TMOUK kitchen from the TMOUS ROM simply does not work the resultant ROM does not boot and just hangs the device.
Could one of our chefs please explain how to port the nk.exe from the US build to unlock the memory in the T-Mobile UK ROM 1.72.
Using the following 576-enabled Radio
RUU_Leo_Radio_15.34.50.07U_2.08.50.08_2
Many thanks in advance
Click to expand...
Click to collapse
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Rom\XIP\OEMXIPKernel\nk.exe
OEM\OEMDrivers
OEM\OEMDriversHigh
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
patensas said:
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
Click to expand...
Click to collapse
Why ddi.dll ? mine works fine with new 2.13/2.11/2.10 ddi.dll
patensas said:
For the 576MB patch you need only to replace these folders from an 2.07 or 2.02 Stock-Rom:
Rom\XIP\OEMXIPKernel\nk.exe
OEM\OEMDrivers
OEM\OEMDriversHigh
Then you need to replace again with this folder
OEM\OEMDrivers\ddi.dll
with an older Base than 2.07/2.02 (1.72 in your case is recommended)
Click to expand...
Click to collapse
Thank you very much indeed for your kind help. It worked perfectly
Hi, I'm a newbie for ROM cooking, experienced cookers, please advise.
I'm using HD2/Leo phone, I learned how to use HSPL, flash a cooked ROM, so I'm start thinking of cooking the ROM my own, and what all I need is retain original 1.66 707.1 Asia WWE version of stock ROM, but only to enable 576MB RAM.
I found a kitchen, oskitchen zero 1.31, use the GUI and extracted the stock ROM, and stop here, because I don't know how to cook the ROM...
Experienced cookers, please advise, thanks in advance!!!
patensas posted like 2 posts up from yours which files you need to replace.
which means that i just copy all the folder need, then paste inside the osKitchen Zero folder, and finally click "Start building button" to cook my ROM...?
I also want to know why ddi.dll need to be remain old version?
OEM\OEMDrivers\ddi.dll
hello fellow chefs
i am trying to make a verry smooth rom in dutch for soem friends of mine
it is working out quite well but i want to enable the 576 ram tweak
in patensas his post he says i need to change things from a tmous rom
if i use the tmous 2.13.531.1 as base rom do i still need to change those folders?
thanks in advance
sorry to ask but coul some one upload the files to make the 576 mb tweak?
i have 2.13 tmous as base in the kitchen and it would save me a download and dump
thanks in advance
All you need is in the 2.13 TMOUS.
pkoper said:
All you need is in the 2.13 TMOUS.
Click to expand...
Click to collapse
then i dont get it:-o
i installed Leo_RADIO_15.34.50.07U_2.08.50.08 on the phone but no 576 mb tweak:S
Using 2.13 base you should have 576 anyway.
What did you change?
pkoper said:
Using 2.13 base you should have 576 anyway.
What did you change?
Click to expand...
Click to collapse
to be honest i have no idea why it aint working
when you got the settings tab and scroll down to device info
there you choose hardware info it should also say 576?
the thing i did is dump the tmous 2.13 rom with ervius
then i took out the 0409 folder in oem and replaced it with the the one i use for blackstone(maybe the fault is here) then i replaced the ext packages with the ones i use i blackstone kitchen(compared wich are unnesacary and left those out) and then recooked the rom
i also decided today that i am gonna rebuild the entire kitchen from scratch without copy pasting the 0409 folder in oem and set everything up from there and remake the initflash.dat the way i want it
i havent changed the ddi.dll so that might be the trick why it aitn working
on side note:
wish i whasnt in the middle of moving and had the actual device for a few days
that would definetly make things easier for me
ps: what do you think is the best base to use to build the kitchen on with ervius kitchen
tmous 3.14? it would sound logical that newer is better although there are differences between the american and european leo's
Hi all !
I'm trying to cook a personal custom rom I just want to change the build from 6.5 to 6.5.X of the official htc 3.14 italian rom. I would also like to enable the 576 mb of ram. I have already installed on the phone the 2.15 radio, what files I need to change inside the kitchen ( I use oskitchen ) ? I have a t-mobile.uk hd2 ( I have bought it from england.
so I think that it's the european version )
light_n_roses said:
Hi all !
I'm trying to cook a personal custom rom I just want to change the build from 6.5 to 6.5.X of the official htc 3.14 italian rom. I would also like to enable the 576 mb of ram. I have already installed on the phone the 2.15 radio, what files I need to change inside the kitchen ( I use oskitchen ) ? I have a t-mobile.uk hd2 ( I have bought it from england.
so I think that it's the european version )
Click to expand...
Click to collapse
Take the nk.exe(from oemxipkernel) from 2.13 tmous.I think also the nk.exe from 3.14 tmous should be ok but I havent try it.
Could someone just post an attachment with the modules needed to enable the extra RAM? I'm sure it would make it easier for everyone. I'd do it, but I don't have an hd2.
Farmer Ted said:
Could someone just post an attachment with the modules needed to enable the extra RAM? I'm sure it would make it easier for everyone. I'd do it, but I don't have an hd2.
Click to expand...
Click to collapse
The way that the European Leo device gets the 576 ram enabled is the following:
Replace the nk.exe with the nk.exe from TMOUS rom (in Sources\Devices\HTC Leo\Profiles\default\OEMXIPKernel folder for oskitchen, or \ROM\LEO\build number\OEMXIPKERNEL for ervius kitchen).
I attach the 2.13 tmous and 3.14 tmous nk.exe modules.Both do the trick or enable the 576 ram (for those who believe it).
Personally in my Leo I didnt see any difference with the 576 ram enabled.
I can't get any FM radio running on a rom with 3.04 base. The app will start, scan for stations then either crash or freeze.
Switching to 2.13 OEM with exactly the same EXT packages makes it all work.
Tried HTCFM.dll and FmRadioSdk.dll from 2.13 without luck.
Same happens with 3.02 base. FM radio just crashes.
(btw. I did use 2.13 nk.exe in all tests)
same problem !
I suppose problem is hiding in SPL, at the moment only 2.08HSPL is available, so maybe there are some changes that makes impossible to use FM-Radio drivers from 3.04 rom with SPL 2.08 ...
No one has an idea?
I suposed you did see this thread and want to have it working on 3.04 right?
http://forum.xda-developers.com/showthread.php?t=720937
Anyway, if you use 2.14 as base oemdrivers and swop wavedev.dll with the one in 2.13 the FM radio works.
pkoper said:
No one has an idea?
Click to expand...
Click to collapse
Laurentius26 said:
I suposed you did see this thread and want to have it working on 3.04 right?
Click to expand...
Click to collapse
Yes, 2.13 and 2.14 work fine. Just can't get it running on 3.04.
I have tried many ways to this problem...Maybe I found that,when 576MB RAM works,the fm radio can not work.(the same with you,2.14,2.10,2.13nk).But when RAM change to 448MB,the fm radio can work.(such as 1.73nk).
May someone solve this problem!
saintlyjinn said:
...when 576MB RAM works,the fm radio can not work...
Click to expand...
Click to collapse
Hi,
my Radio works with base 2.10/2.13/2.14 and 576MB Ram, but not with Base 3.04.
with friendly greet
starbase64
works for me too
Hi,
i have build many roms in the last hour and radio works now with base 3.04.
@saintlyjinn you were right, radio work on base 3.04 with 1.73nk
Thanks for this solution.
with friendly greet
starbase64
Thats great news.
The thing thats giving me headaches is that the CleanEx roms and the Waterbearv4 by Fab985 use 3.04 as base with 576MB ram enabled.
Just curious what one would need to do to make it happen.
alesscam has found a solution
http://forum.xda-developers.com/showpost.php?p=7142183&postcount=627
Hahaha...
pkoper said:
alesscam has found a solution
http://forum.xda-developers.com/showpost.php?p=7142183&postcount=627
Click to expand...
Click to collapse
I'm going on holiday tomorrow and my device touchscreen stopped functioning
so I needed to send it for repair (under warrantee) and I'm still waiting for return but.....
Did you guys try the new Huashan leaked rom with a new FM Radio?
http://forum.xda-developers.com/showthread.php?t=726095
Worth a try
Probably no Alkaline batteries needed.
Fingers crossed.
Hi,
FM Radio from Huashan 0.90 Rom works fine.
Base: 3.04
NK: 1.72
Build: 25012
with friendly greet
starbase64
pkoper said:
alesscam has found a solution
http://forum.xda-developers.com/showpost.php?p=7142183&postcount=627
Click to expand...
Click to collapse
sorry mate ..... but I'm crazy
is stronger than me
however
Fab985 soon explain the alternative
the exchange of nk.exe
will post the list of drivers to replace
Cool news mate, thanks a lot for sharing but it doesn't enable 576mb ram.
starbase64 said:
Hi,
FM Radio from Huashan 0.90 Rom works fine.
Base: 3.04
NK: 1.72
Build: 25012
with friendly greet
starbase64
Click to expand...
Click to collapse
Hello.
The solution is to replace OemExtDll.dll and OEM_Misc.dll from 2.13 or 2.14 Driver folder.
I allways replace and the two touch dll's with 3.4 base.
I upload it for you is untouched files from 2.13 rom if you bored to dumpit.
Thanks
http://dl.dropbox.com/u/2988853/Fm_Fix_Leo's.zip
Excellent!
Just tried it and all works fine.
Thanks
So, how can one build a rom that will work both on a T-Mobile HD2 and on the WWE HD2?
Should I try to work with the WWE stock roms and hope it will work with the T-MO or is there any specifics needs to be done?
I beleive my EVK Kitchen will do what you want...
rstoyguy said:
I beleive my EVK Kitchen will do what you want...
Click to expand...
Click to collapse
nice to point him in a ready to use kitchen but i think its handy if you type out what you have done to make it that way so other people can do it themselves as i think it are only a few files and its easier to change a few files then customize a entire kitchen to youre own liking
I take the OEMXIPKernel and OEMDrivers packages from a 2.1x ROM and use them as part of my ROM's base to make it 1024mb compatible. You could use the whole 2.1x OEM dir, but I find it unstable myself.
millski said:
I take the OEMXIPKernel and OEMDrivers packages from a 2.1x ROM and use them as part of my ROM's base to make it 1024mb compatible. You could use the whole 2.1x OEM dir, but I find it unstable myself.
Click to expand...
Click to collapse
Basically, you work on a WWE rom as the base but you take OEMXIPKernel and OEMDrivers from a T-Mo rom and install them instead of the WWE ones?
yosi199 said:
Basically, you work on a WWE rom as the base but you take OEMXIPKernel and OEMDrivers from a T-Mo rom and install them instead of the WWE ones?
Click to expand...
Click to collapse
The wording here can be a bit confusing - TMOUS ROMs are WWE anyway (2.13 being the last) but the latest 1024mb ROM is 2.14, which is CHS language.
You could use any base you like and just include the OEMXIP and OEMDrivers from a 2.1x ROM to make it fully compatible. I use a WWE 1.72 base (because I find it the most stable) and the OEMDrivers and OEMXIP from 2.14 (because it's the latest available). I then had to replace several bluetooth dll's and mui's in the OEMDrivers as they are in CHS and I want WWE - I just copied them over from the 1.72 WWE OEMDrivers package. If you used the 2.13 OEMDrivers they would already be WWE...
I also have the 2.10 touch.dll and touchgl.dll files copied to my OEMDrivers as these have better touch response.
The easiest way would be to just use the 2.13 base (it's 1024mb HD2 compatible and it's already WWE) and use x.xx.50.x series radios...
After reading the post that transplanting 2.14 nk,2.14 OEM_Misc.dll to 3.04 can solve the problem of FM-radio. But I find another problem that the WIFI MAC address change to xx-xx-xx-xx-xx-xx. Absolutely it's fake,and in some conditions it may do some trouble. So I want to know if there's some ways to solve this problem.
I have solved this problem by myself....
just replace the proper version of bcmsddhd.dll
Thanks xda-developers...
Hi,
which combination do you use?
Base ? and bcmsddhd.dll from ?
with friendly greet
starbase64
starbase64 said:
Hi,
which combination do you use?
Base ? and bcmsddhd.dll from ?
with friendly greet
starbase64
Click to expand...
Click to collapse
I would like to know this too. Thanks!
to fix wifi if you cook a non-asian rom:
take bcmsddhd.dll from a non-asian rom (for example 2.13.531.1 - NOT2.14 because it's asian).
to fix the fm-radio issue in the 3.xx-base you should be able to use the 2.14 asian files.
Thx , i didn't find for FM radio bug in my cook , now it's ok . Thx, Thx , Thx
Use 3.14 drivers as they are. and no need to mix anything.
They work fine for me..
c_shekhar said:
Use 3.14 drivers as they are. and no need to mix anything.
They work fine for me..
Click to expand...
Click to collapse
i think ur referring to Tmo-US leo rom 3.14 drivers..
the 3.14 drivers from original htc rom have issues when used with nk.exe from tmo-US rom (and you'd wanna use tht nk.exe to get rid of the low ram issue)
Only the nk.exe needs to be swopped to fix memory, oemdrivers work fine just as they come.
No problems with the FM radio, nothing needs to be fixed.
jjblaster3 said:
i think ur referring to Tmo-US leo rom 3.14 drivers..
the 3.14 drivers from original htc rom have issues when used with nk.exe from tmo-US rom (and you'd wanna use tht nk.exe to get rid of the low ram issue)
Click to expand...
Click to collapse
jjblaster3 said:
i think ur referring to Tmo-US leo rom 3.14 drivers..
the 3.14 drivers from original htc rom have issues when used with nk.exe from tmo-US rom (and you'd wanna use tht nk.exe to get rid of the low ram issue)
Click to expand...
Click to collapse
@lauretius26 is right. There absolutely no issues at all...
@Laurentius26 and c_shekhar:
i haven't tested but i guess you guys are right.. the only explanation going through my mind is that the 2.13/2.14 nk's from tmo-us were not compatible with the 3.14/3.04/3.02 oemdrivers from Leo S roms, but since there was a 3.14 tmo-us update (meaning a 3.14 nk) it now is compatible with those oemdrivers i guess
hello fellow chefs
since shortly i became aware that bluetooth isnt working on the hd2 rom i made:-o
the thing i did is download the 1.66 dutch rom and dump it with ervius kitchen(i use this ktichen for rom making)
i changed the ext packages to the ones i use for blackstone and changed a few packages with the original 1.66 packages like dshow, concurrence manager, camera, fm radio and comm manager
then i rebuild it and it looks the same as on my blackstone and almost everything works except bluetooth
when i go to start>settings>bluetooth i get the screen that bluetooth isnt on and if i want to turn it on
when i press yes i get the message that the bluetooth stack cant be started
when i flash a kwbr rom bluetooth works so it isnt a mailfunction of the device
also yesterday before the server crash i posted a thread for this and af974 posted that the bleutooth settings whas a package he had never seen in leo roms although i get it from the dump of the dutch leo rom 1.66 and 1.72 vodafone roms so whats up with this package:S
i atach my buildlog and want to thank for any tips on how to solve it
edit: i just checked with other leo roms i have stored and when i looked at 3.01 wwe rom the oemdriver and oemdriverhigh folders are in total 3 mb bigger then the ones i get from the dutch roms
you think i can change it with those? as i dont quite understand the differnece between the american and european leo's:S
And you also played with SYS.
Best to take a look at a SYS from a stock rom. The HD2 has a few things that are in OEM.
You can definatly removing following from your SYS:
Bluetooth Included -> is in OEM
IRDA -> Leo does not have infa red port
SMS_Providers
WinCENLS_WWE -> in XIP
and a few more, just compare an original with yours
pkoper said:
And you also played with SYS.
Best to take a look at a SYS from a stock rom. The HD2 has a few things that are in OEM.
You can definatly removing following from your SYS:
Bluetooth Included -> is in OEM
IRDA -> Leo does not have infa red port
SMS_Providers
WinCENLS_WWE -> in XIP
and a few more, just compare an original with yours
Click to expand...
Click to collapse
thanks mate
never thought there could be bluetooth there:-o
just took the entire sys/xip folders i use in my blackstone kitchen
hey, i had the same problem as you some time ago. it was because of my modifications in initflashfiles.ini, check if
"Directory("\Windows\AutoStart"):-File("BTTrayCE.lnk","\Windows\BTTrayCE.lnk")"
is in yours or any other app.dat
maybe this will help you
lauchi said:
hey, i had the same problem as you some time ago. it was because of my modifications in initflashfiles.ini, check if
"Directory("\Windows\AutoStart"):-File("BTTrayCE.lnk","\Windows\BTTrayCE.lnk")"
is in yours or any other app.dat
maybe this will help you
Click to expand...
Click to collapse
thanks for the tip
dont have this in the 0413 initflash but i do have it in the english one i have:S
will put it in to be sure
also deletd the files from the sys folder wich i compared to the one from the dumps i have from leo roms
only downside is i forgot to take out cmbluetooth so it didtn work
gues you guys dont use that in the leo rom?
didnt see it in the dumps
miniterror said:
thanks for the tip
dont have this in the 0413 initflash but i do have it in the english one i have:S
will put it in to be sure
also deletd the files from the sys folder wich i compared to the one from the dumps i have from leo roms
only downside is i forgot to take out cmbluetooth so it didtn work
gues you guys dont use that in the leo rom?
didnt see it in the dumps
Click to expand...
Click to collapse
Nope don't use it on the Leo and you need bttrayce to start at bootup to be able to enable bluetooth
hmmm
made sure that Directory("\Windows\AutoStart"):-File("BTTrayCE.lnk","\Windows\BTTrayCE.lnk") whas in the initflash.dat file and took out all bluetooth packages out of sys and ext packages but still no bluetooth:S
gonna try changing to 2.13 base
any one knows of fixes are needed there
What error are you getting when you try to start bluetooth?
EpiphanyNL said:
What error are you getting when you try to start bluetooth?
Click to expand...
Click to collapse
de bluetooth stack kan niet gestart worden
or in english the bluetooth stack cant be started
i am trying to make a dutch rom and i wha slooking at the iniflahs again yesterday and i saw i used the english lines in a dutch rom so that whas a little wrong
yesterday evening i changed base drivers to 2.13 and gonna flash it somewhere today as i dont have the actual device myself
edit:
used 2.13 as a base and bluetooth can start now but i cant make it visible
gonna say to my friends they need to wait and ill redo the kitchen again but with alot less copy pasting
and translate the entire initflash.dat(or use one from 1.66 nld base)
miniterror said:
(or use one from 1.66 nld base)
Click to expand...
Click to collapse
That's what I did
thanks
thnx a ton buddy ur trick worked... feeling so relaxed now....