nokia 7230: getnetworkinfo: unhandled frame

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

nokia 7230: getnetworkinfo: unhandled frame

Raphaël Droz
Using bluetooth with a Nokia 7230-1c, here is the log of the failing
getnetworkinfo command:


$ gnokii --phone nokia --getnetworkinfo

> GNOKII Version 0.6.30
> LOG: debug mask is 0x1
> Config read [...]
> phone instance config:
> model = series40
> port = [...]
> connection = bluetooth
> initlength = default
> serial_baudrate = 19200
> serial_write_usleep = -1
> handshake = software
> require_dcd = 0
> smsc_timeout = 10
> rfcomm_channel = 0
> sm_retry = 0
> Connecting
> Forcing rfcomm_channel = 14 for FBUS connection
> Serial device: opening device [...]
> Channel: 14
> Channel: 14
> Using channel: 14
> Getting model...
> Message sent: 0x1b / 0x0006
> 00 01 00 07 01 00                               |                
> Message received: 0x1b / 0x003a
> 01 42 00 08 00 01 58 34 00 30 56 20 31 30 2e 38 |  B    X4 0V 10.8
> 31 0a 32 38 2d 30 32 2d 31 31 0a 52 4d 2d 35 39 | 1 28-02-11 RM-59
> 38 0a 28 63 29 20 4e 6f 6b 69 61 20 20 20 20 20 | 8 (c) Nokia    
> 20 20 20 20 20 20 20 0a 4c 00                   |         L      
> Received message type 1b
> model length: 6
> Received model RM-598
> Getting network info ...
> Message sent: 0x0a / 0x0005
> 00 01 00 00 00                                  |                
> Message received: 0x0a / 0x000a
> 01 97 00 f0 01 00 00 00 00 00                   |                
> Received message type 0a
> Unknown subtype of type 0x0a (240)
> UNHANDLED FRAME RECEIVED
> request: 0x0a / 0x0005
> 00 01 00 00 00                                  |                
> reply: 0x0a / 0x000a
> 01 97 00 f0 01 00 00 00 00 00                   |                
> Please read Docs/Bugs and send a bug report!
> Error: The current frame isn't handled by the incoming function.
> Serial device: closing device


I don't see in this trace any fact that the device would *not* support
that, but I don't understand why it failed.


Here in comparison:

$ gnokii --phone nokia --identify

> GNOKII Version 0.6.30
> LOG: debug mask is 0x1
> Config read from file [...]
> phone instance config:
> model = series40
> port = [...]
> connection = bluetooth
> initlength = default
> serial_baudrate = 19200
> serial_write_usleep = -1
> handshake = software
> require_dcd = 0
> smsc_timeout = 10
> rfcomm_channel = 0
> sm_retry = 0
> Connecting
> Forcing rfcomm_channel = 14 for FBUS connection
> Serial device: opening device [...]
> Channel: 14
> Channel: 14
> Using channel: 14
> Getting model...
> Message sent: 0x1b / 0x0006
> 00 01 00 07 01 00                               |                
> Message received: 0x1b / 0x003a
> 01 42 00 08 00 01 58 34 00 30 56 20 31 30 2e 38 |  B    X4 0V 10.8
> 31 0a 32 38 2d 30 32 2d 31 31 0a 52 4d 2d 35 39 | 1 28-02-11 RM-59
> 38 0a 28 63 29 20 4e 6f 6b 69 61 20 20 20 20 20 | 8 (c) Nokia    
> 20 20 20 20 20 20 20 0a 4c 00                   |         L      
> Received message type 1b
> model length: 6
> Received model RM-598
> Identifying...
> Message sent: 0x1b / 0x0005
> 00 01 00 00 41                                  |     A          
> Message sent: 0x1b / 0x0006
> 00 01 00 07 01 00                               |                
> Message received: 0x1b / 0x001a
> 01 42 00 01 00 01 41 14 00 10 [...]             |  B    A   [...]
> Received message type 1b
> Received imei [...]
> Message received: 0x1b / 0x003a
> 01 42 00 08 00 01 58 34 00 30 56 20 31 30 2e 38 |  B    X4 0V 10.8
> 31 0a 32 38 2d 30 32 2d 31 31 0a 52 4d 2d 35 39 | 1 28-02-11 RM-59
> 38 0a 28 63 29 20 4e 6f 6b 69 61 20 20 20 20 20 | 8 (c) Nokia    
> 20 20 20 20 20 20 20 0a 4c 00                   |         L      
> Received message type 1b
> Received revision V 10.81
> model length: 6
> Received model RM-598
> IMEI         : [...]
> Manufacturer : Nokia
> Model        : RM-598
> Product name : RM-598
> Revision     : V 10.81
> Serial device: closing device



Any hint ?



regards

_______________________________________________
gnokii-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/gnokii-users
Reply | Threaded
Open this post in threaded view
|

Re: nokia 7230: getnetworkinfo: unhandled frame

Daniele Forsi-2
2014-09-07 21:22 GMT+02:00 Raphaël:

>> Getting network info ...
>> Message sent: 0x0a / 0x0005
>> 00 01 00 00 00                                  |
>> Message received: 0x0a / 0x000a
>> 01 97 00 f0 01 00 00 00 00 00                   |
>> Received message type 0a
>> Unknown subtype of type 0x0a (240)
>> UNHANDLED FRAME RECEIVED
>> request: 0x0a / 0x0005
>> 00 01 00 00 00                                  |
>> reply: 0x0a / 0x000a
>> 01 97 00 f0 01 00 00 00 00 00                   |
>> Please read Docs/Bugs and send a bug report!
>> Error: The current frame isn't handled by the incoming function.
>> Serial device: closing device
>
>
> I don't see in this trace any fact that the device would *not* support
> that, but I don't understand why it failed.

the fact is hidden in the firmware, only the phone knows why it
doesn't support that, that 0xf0 (decimal 240) in 01 97 00 f0 01 00 00
00 00 00 means "not supported" or something like that, it's a generic
erorr code

>> Manufacturer : Nokia
>> Model        : RM-598
>> Product name : RM-598

> Any hint ?

as always we must start adding to misc.c that 7230-1c is a RM-598 (may
I add your full name to the ChangeLog?), then if someone finds out if
your phone supports the get nework info command with a different frame
we can add a special case for it

what you can do is running gnokii --monitor and from you phone's menu
activate and deactivate flight mode to see if any unhandled frame is
received, if nothing is printed then you should modify
NK6510_Subscribe() and guess the number to use instead of
NK6510_MSG_NETSTATUS which is 0x0a (and that's why the error message
refers to 0x0a "Unknown subtype of type 0x0a (240)") this is somewhat
safer than sending random data as I've done in the past all the
numbers known so far are in include/phones/nk6510.h see NK6510_MSG_*

--
Daniele Forsi

_______________________________________________
gnokii-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/gnokii-users
Reply | Threaded
Open this post in threaded view
|

Re: nokia 7230-1c: getnetworkinfo: unhandled frame

Raphaël Droz
On Sun, Sep 07, 2014 at 10:02:20PM +0200, Daniele Forsi wrote:
> 2014-09-07 21:22 GMT+02:00 Raphaël:
> as always we must start adding to misc.c that 7230-1c is a RM-598 (may
> I add your full name to the ChangeLog?), then if someone finds out if
> your phone supports the get nework info command with a different frame
> we can add a special case for it

ack', but just add "+floss" suffix to email @' LHS
(Gmail supports receiving such suffixed emails, although their out-SMTP
strips the said suffix)


Please note that 7230 (no the "1c" may very well be a RM-604)
(but I'm note sure if a given model number could have been distributed under
different RM numbers)


> what you can do is running gnokii --monitor and from you phone's menu
> activate and deactivate flight mode to see if any unhandled frame is
> received...

I tried that, but seems like flight mode disable bluetooth too (!),
thus --monitor only showing:
> CALL0: IDLE
> CALL1: IDLE
Worse, returning to the "normal" phone profile doesn't re-enable
--monitor to receive original "normal" infos (battery, messages, ...


> ... if nothing is printed then you should modify
> NK6510_Subscribe() and guess the number to use instead of
> NK6510_MSG_NETSTATUS which is 0x0a (and that's why the error message
> refers to 0x0a "Unknown subtype of type 0x0a (240)") this is somewhat
> safer than sending random data as I've done in the past all the
> numbers known so far are in include/phones/nk6510.h see NK6510_MSG_*

I'll try that one of these days.


many thanks for the insights !

_______________________________________________
gnokii-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/gnokii-users
Reply | Threaded
Open this post in threaded view
|

Re: nokia 7230-1c: getnetworkinfo: unhandled frame

Daniele Forsi-2
2014-09-22 18:34 GMT+02:00 Raphaël Droz:

> On Sun, Sep 07, 2014 at 10:02:20PM +0200, Daniele Forsi wrote:
>> 2014-09-07 21:22 GMT+02:00 Raphaël:
>> as always we must start adding to misc.c that 7230-1c is a RM-598 (may
>> I add your full name to the ChangeLog?), then if someone finds out if
>> your phone supports the get nework info command with a different frame
>> we can add a special case for it
>
> ack', but just add "+floss" suffix to email @' LHS
> (Gmail supports receiving such suffixed emails, although their out-SMTP
> strips the said suffix)
>
>
> Please note that 7230 (no the "1c" may very well be a RM-604)

I did't put the email, just a line in the ChangeLog text file

> (but I'm note sure if a given model number could have been distributed under
> different RM numbers)

it's possible, according to our misc.c several phones it is happened
several times in the past

> I tried that, but seems like flight mode disable bluetooth too (!),

indeed it affect all radios

> thus --monitor only showing:
>> CALL0: IDLE
>> CALL1: IDLE
> Worse, returning to the "normal" phone profile doesn't re-enable
> --monitor to receive original "normal" infos (battery, messages, ...

unfortunately, like all the frames its a trial and error process and
still we don't know much about monitoring

--
Daniele Forsi

_______________________________________________
gnokii-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/gnokii-users