Active Topics
-
Porting apps to Leste (29)
to Maemo 7 / Leste by Arno_11 - 2 days, 15 hrs ago -
Install Fonts in N900 (68)
to Maemo 5 / Fremantle by teroyk - 3 days, 18 hrs ago - more...
| The Following User Says Thank You to cddiede For This Useful Post: | ||
|
2012-01-24
, 14:26
|
|
Posts: 1,320 |
Thanked: 915 times |
Joined on Feb 2010
|
#42
|
Originally Posted by cddiede
If you read the email they sent, they have said this will be made to work for the N9.
I'll go right ahead and admit that I was wrong on this one. Really does look like it's full on NFC only with no bluetooth.
Wow. Cool.
But still it's proprietary since there's no open or established protocol for this type of peripheral device input.
What does that mean to us? Simple:
It means that this devices requires a hardware specific closed source binary drivers to function since no open protocol could be used by a third party to develop for us.
That means no automatic inclusion in the kernel, and no third parties writing a driver or app to make this work on platforms not directly supported by the keyboard maker.
That equals a bunch of sad N9 owners.
Meaning they are creating a method of this working on our N9's
__________________
Well Nokia do at least know how to build a decent phone, just apparently don't know how to support it..
N900 Died
Replaced with N8, Requested E7, "Accidentally Broke E7", Now rolling with an N9 and im loving it!
My Contributions
N900 Conversations Wiki Page
Well Nokia do at least know how to build a decent phone, just apparently don't know how to support it..
N900 Died
Replaced with N8, Requested E7, "Accidentally Broke E7", Now rolling with an N9 and im loving it! My Contributions
N900 Conversations Wiki Page
|
|
2012-01-24
, 14:44
|
|
Posts: 2 |
Thanked: 2 times |
Joined on Jan 2012
@ Norway
|
#43
|
Originally Posted by cddiede
When first time use press the "driver install key" on the keyboard and the driver is - of course - installed on your phone.
I'll go right ahead and admit that I was wrong on this one. Really does look like it's full on NFC only with no bluetooth.
Wow. Cool.
But still it's proprietary since there's no open or established protocol for this type of peripheral device input.
What does that mean to us? Simple:
It means that this devices requires a hardware specific closed source binary drivers to function since no open protocol could be used by a third party to develop for us.
That means no automatic inclusion in the kernel, and no third parties writing a driver or app to make this work on platforms not directly supported by the keyboard maker.
That equals a bunch of sad N9 owners.
It's Only NFC (But I Like It)!
|
|
2012-01-24
, 15:11
|
|
Posts: 3,074 |
Thanked: 12,960 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#44
|
Originally Posted by damaltor
Well, NFC is not some emulation of serial device or such, so "transmit arbitrary data" is slightly incorrect. Also there is a specialized NFC chip in compatible devices, which strictly follows the specification, and that specification does not support HID. Which means that keyboard/drivers in quesion should follow the same specification, i.e. RFID tag reading/writing and HID emulation.
NFC can transmit arbitrary data, too (which is done on bt pairing, as the two devices exchage a bluetooth passkey).
As the data rate is (relatively) slow, there is no sense in transmittig big amounts of data (like directly sharing an image via nfc).
but as a keyboard has to send a minimal amount of data, nfc is fast enough. there is no standard for this though, there will be a special driver needed, which is polling nfc and emulates the keypresses for the os.
You are most probably right that keyboard emulation is done by polling, can't imagine how that would affect battery life.
|
|
2012-01-24
, 15:50
|
|
Posts: 34 |
Thanked: 46 times |
Joined on Jan 2012
@ Germany
|
#45
|
nobody actually needs HID for this. It would be nice of course, no driver messing and such, but if they provide a driver, that is enough for most people.
NFC can transmit arbitrary data in a way of bulk transmit. this is kind of like USB, which has a very strict protocol (which does NOT include device specifications such as HID, but doess include endpoints of communication and communicaton specs), and can transmit data via bulk. so, if there is a program at the device (== driver) which recognises the keyboard (e.g. by some kind of nfc id? i dunno, in USB world it is Vendor ID and Device ID), and somehow manages to read the communcation (probably via polling, as said), it will work with nfc only.
....would be interesting to use a "normal" nfc tag reader before installing the driver. i guess (!) that it would read another "tag" everytime you push a button on the keyboard.
NFC can transmit arbitrary data in a way of bulk transmit. this is kind of like USB, which has a very strict protocol (which does NOT include device specifications such as HID, but doess include endpoints of communication and communicaton specs), and can transmit data via bulk. so, if there is a program at the device (== driver) which recognises the keyboard (e.g. by some kind of nfc id? i dunno, in USB world it is Vendor ID and Device ID), and somehow manages to read the communcation (probably via polling, as said), it will work with nfc only.
....would be interesting to use a "normal" nfc tag reader before installing the driver. i guess (!) that it would read another "tag" everytime you push a button on the keyboard.
 |
|
2012-01-24
, 16:54
|
|
Posts: 134 |
Thanked: 247 times |
Joined on Sep 2009
@ Spain, EU
|
#46
|
Does anyone know if the N9 supports NFC P2P mode? If not, that keyboard is never going to work with it.
Last edited by kevloral; 2012-01-24 at 17:01.
Last edited by kevloral; 2012-01-24 at 17:01.
|
|
2012-01-24
, 17:02
|
|
Posts: 3,074 |
Thanked: 12,960 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#47
|
Originally Posted by damaltor
Yeah, I was thinking the same, that way you don't need messing up with lower-level protocols. But it will mean polling lots of times per second, a battery killer.
....would be interesting to use a "normal" nfc tag reader before installing the driver. i guess (!) that it would read another "tag" everytime you push a button on the keyboard.
|
|
2012-01-25
, 12:02
|
|
Posts: 1,320 |
Thanked: 915 times |
Joined on Feb 2010
|
#48
|
Originally Posted by freemangordon
I think as for battery life, the device can simply initiate the NFC Tap To Connect we are all familiar with, and then simply poll at intervals
Well, NFC is not some emulation of serial device or such, so "transmit arbitrary data" is slightly incorrect. Also there is a specialized NFC chip in compatible devices, which strictly follows the specification, and that specification does not support HID. Which means that keyboard/drivers in quesion should follow the same specification, i.e. RFID tag reading/writing and HID emulation.
You are most probably right that keyboard emulation is done by polling, can't imagine how that would affect battery life.
Then have a time that if there is no data transmitted our N9's will stop polling until there is another NFC Tap To Connect initiation
Let me know if this hasn;t been explained well :P
__________________
Well Nokia do at least know how to build a decent phone, just apparently don't know how to support it..
N900 Died Replaced with N8, Requested E7, "Accidentally Broke E7", Now rolling with an N9 and im loving it!
My Contributions
N900 Conversations Wiki Page
Well Nokia do at least know how to build a decent phone, just apparently don't know how to support it..
N900 Died
Replaced with N8, Requested E7, "Accidentally Broke E7", Now rolling with an N9 and im loving it! My Contributions
N900 Conversations Wiki Page
|
|
2012-01-28
, 07:49
|
|
Moderator |
Posts: 5,320 |
Thanked: 4,464 times |
Joined on Oct 2009
|
#49
|
Originally Posted by kevloral
As mentioned earlier in the thread, it most likely doesn't use any open standards.
Does anyone know if the N9 supports NFC P2P mode? If not, that keyboard is never going to work with it.
That doesn't mean it's never going to work....
Last edited by jalyst; 2012-01-28 at 07:57.
|
|
2012-01-28
, 10:50
|
|
Posts: 9 |
Thanked: 19 times |
Joined on Jan 2012
|
#50
|
Originally Posted by kevloral
Yes, N9 does support LLCP (both connectionless and connection-oriented); application developers can use the Qt Mobility API to create LLCP servers and clients.
Does anyone know if the N9 supports NFC P2P mode? If not, that keyboard is never going to work with it.
There is no restriction to how much data you can transfer over LLCP; as long as you keep the two devices together data can flow between the two. For a keyboard you'd need an app to convert from data coming over LLCP to keyboard events at some suitable level (X? kernel? something else? dunno)
For anyone interested in LLCP, have a look at the NFC Forum LLCP and NFC-DEP specs, as well as the Qt Mobility NFC API LLCP socket documentation.
However, LLCP is just a communication protocol -- from an application point of view "LLCP support" is about the same as saying that N9 supports TCP and UDP -- necessary but useless by itself. You have to have some application protcol talking on top of LLCP to get any use out of it.
There's also the issue of latency. The LLCP p2p operation is asymmetric, one device is a master while the other one is a slave, and the slave cannot send data except as a response to a PDU from the master. For the cases where the master doesn't have anything to send it sends empty frames to which the slave can reply with data, but I can't now recall what is the default interval for N9 implementation. (it is trivial to make a LLCP "ping" application and I have made one in the past, but I don't currently have two devices so I can't make any measurements now). Dunno what kind of latencies would make keyboard use irritating, but I guess we're talking a couple hundred milliseconds at most.
I won't comment on the battery claims, because I don't have any real understanding on the radio side of matters. NFC tags work only on the current induced from the active device's signal, but I can't say if it would be possible to make a p2p device acting always in the target (slave) role without a power source. I'll leave that to someone else
| The Following 5 Users Say Thank You to hmallat For This Useful Post: | ||
Wow. Cool.
But still it's proprietary since there's no open or established protocol for this type of peripheral device input.
What does that mean to us? Simple:
It means that this devices requires a hardware specific closed source binary drivers to function since no open protocol could be used by a third party to develop for us.
That means no automatic inclusion in the kernel, and no third parties writing a driver or app to make this work on platforms not directly supported by the keyboard maker.
That equals a bunch of sad N9 owners.