PDA

View Full Version : A small problem with recent WM6.1 ROMs


HeroHP
31st May 2008, 06:44 PM
Yes, I found a small problem: the Beam button in Comm seems not to work properly. Is there any1 get this?

rondol1
1st June 2008, 01:57 AM
Yes, I found a small problem: the Beam button in Comm seems not to work properly. Is there any1 get this?

Can you explain please? What is it that isn't functioning?

varanusvincent
1st June 2008, 02:01 AM
which rom?

HeroHP
1st June 2008, 12:38 PM
I've tried various 6.1 ROMs (about 6 or 7 recent ROMs includes 203, 701, 212, 213 etc. of various authors like Cloudyfa, Lamson-PV, l3v5y) and found the same problem. My case is that the Beam button in Commanager doesn't work properly. When I press that button in Comm, it clearly turns into On position but if check its status in Start/Settings/Connections/Beam at once, the real position is Off (the item "Receive all incoming beams" is not checked). The same problem found when turning from On to Off. Any1 get that?

rondol1
1st June 2008, 04:22 PM
I never use this feature, so I didn't notice before but you are right. The beam setting is not responding to changes made in the Comm Manager.

myer
1st June 2008, 05:18 PM
Let me share my experience with Cloudyfa's ROM S4V.19701.01 fixed? by vv.
First I opened Comm manager screen and I turned ON BEAM (or I checked it was on, I couldn't tell you). Then I opened Start/Settings/Connections/Beam and the item "Receive all incoming beams" was checked. Then I unchecked it and I went back to Comm manager screen and it was still turned ON
So I did some tests, and the results are these:
Being Beam in Comm manager screen turned off, when I changed the value for the position to the item "Receive all incoming beams" from
Start/Settings/Connections/Beam (what it is from checked to unchecked or viceversa), in Comm manager screen beam turned on
Meanwhile the change of value (on/off) Beam in Comm manager screen didn't change anything to the item "Receive all incoming beams".

Only when the item "Receive all incoming beams" was checked I was able to receive an mp3 file by IRDA.

Consequently, beam comm manager selector is useless.
So, cooks of the world is up to you to find the solution;)

rondol1
1st June 2008, 05:21 PM
.....
Consequently, beam comm manager selector is useless.
So, cooks of the world is up to you to find the solution;)

I guess you are right!

HeroHP
2nd June 2008, 05:13 PM
So... I'm not alone in the dark with this tiny problem :) Any cook care about this 4 us, thx alot ...

!Aman!
2nd June 2008, 06:01 PM
guys, these 2 settings are separate.
1. comm manager Beam option En/Disable receiving of files over BlueTooth/IrDA according to following registry key:
HKLM\Software\Microsoft\Obex\IsEnabled, 0 for disabled, 1 for enabled.

2. start>settings>connections>beam setting changes the following key:
HKLM\Software\Microsoft\Obex\ObexServiceMask, whose value is 2 by default i.e. unchecked option and if u check the box, its value changes to 3.

i hope the things r clear now :)

rondol1
2nd June 2008, 06:55 PM
guys, these 2 settings are separate.
1. comm manager Beam option En/Disable receiving of files over BlueTooth/IrDA according to following registry key:
HKLM\Software\Microsoft\Obex\IsEnabled, 0 for disabled, 1 for enabled.

2. start>settings>connections>beam setting changes the following key:
HKLM\Software\Microsoft\Obex\ObexServiceMask, whose value is 2 by default i.e. unchecked option and if u check the box, its value changes to 3.

i hope the things r clear now :)

Thanks for explaining, I'm glad it makes sense afterall. But just curious, what is the difference between the two?

!Aman!
2nd June 2008, 07:06 PM
Thanks for explaining, I'm glad it makes sense afterall. But just curious, what is the difference between the two?
it doesnt make much sense to me (at least not yet) :D that why there are 2 settings for the same purpose (at least it looks like same to all of us). i'll try to figure it out from somewhere and let u know asap :)

rondol1
2nd June 2008, 07:13 PM
it doesnt make much sense to me (at least not yet) :D that why there are 2 settings for the same purpose (at least it looks like same to all of us). i'll try to figure it out from somewhere and let u know asap :)

The two different settings don't make sense to me either, but at least we know why they don't synchronize... that makes sense! We will try to figure out why the two setting. To be continued.....

myer
2nd June 2008, 07:14 PM
I'm sorry but it doesn't make sense to me, because the change of value in settings CHANGES the value in Comm Manager Screen.
And the comm manager screen is still useless unless the beam from settings is checked.
I am a little stubborn I know but I promise trying to understand it.;)
Besides I am a little slow writer and I began to write before the two previous posts.:eek:

rondol1
2nd June 2008, 07:24 PM
I'm sorry but it doesn't make sense to me, because the change of value in settings CHANGES the value in Comm Manager Screen.
And the comm manager screen is still useless unless the beam from settings is checked.
I am a little stubborn I know but I promise trying to understand it.;)
Besides I am a little slow writer and I began to write before the two previous posts.:eek:

I think the checkbox in Settings turns on/off the main layer of the service (OBEX?). The Comm Manager just switches on/off protocols that are using this service. I think it should be more understandable if the Comm Manager was to mention "IRDA" instead of "BEAM" . Afterall it names "Bluetooth" separate too!

!Aman!
2nd June 2008, 07:46 PM
I think the checkbox in Settings turns on/off the main layer of the service (OBEX?). The Comm Manager just switches on/off protocols that are using this service. I think it should be more understandable if the Comm Manager was to mention "IRDA" instead of "BEAM" . Afterall it names "Bluetooth" separate too!
i think the IsEnabled registry value (beam in comm manager) controls the main service of OBEX (object exchange). so, if its value is 0, the main service will not start at all and we will not be able to use other bluetooth facilities (like headphones etc, but i'm not sure as i've not tested it, pls someone test :D). "accept all incoming beams" setting is just for file transfer, for sure. so if u enable this option in control panel, this will automatically make the OBEX service enabled because accepting incoming beams is useless unless the main service is running. but the reverse is not true, if u uncheck the 'incoming beams' option, it will not stop the main OBEX service from running.

myer
2nd June 2008, 08:50 PM
I buy it.
But, anyway, what is quite absurd is that uncheking receiving beam in settings, TURNS ON beam in Comm Manager.

bigsilly
7th September 2008, 11:01 AM
Thanks for all of you :p

Now I can understand these two beam setting.

1) start->settings->beam in this I just Keep Check "Receive All..." it.

2) So, I can use Beam Button to turn On/Off File Transfer Service.

if I turn Beam in Comm manager Off, I can't receive file from other.

But if I turn it on then I can receive file from any other who send it to me.



Everything is clear now for me:D

Thanks for your information, I was annoy this setting for a long time:p
Dopod810:cool: