is there any way to wirelessly detect a cell phone's model number?

Ahh, OK. Unfortunately, I did not see anything in the list related to
extended inquiry. I'll keep digging....

thanks,
Isaac

"John Henderson" wrote in message
...
Isaac wrote:

not quite sure what that is a dump of. Seems like BT programming
function/device spec tags/switches. Can you clarify?

It's just a list of the Python attributes / "named entities"
available in the PyBluez Bluetooth module. If it doesn't have a
name listed there, it's not available.

Are they available without pairing?

Not necessarily.

John

After more digging, I came across something that made me think about this
post. That is, it turns out that the BlueZ open source Bluetooth stack
(which BTW the Android uses) supports the BT 2.1 EIR spec. It supported EIR
device names from as far back as version 3.6 (currently its at ver 4.6), so
this should be a well supported feature by now in BlueZ. Here are the
revision history snips I farmed wrt EIR fixes (got it at BlueZ in Maemo
Bluetooth):
=================
ver 4.28: Set the adapter alias only after checking the EIR data.ver 3.6:
Add initial support for device names via EIR.ver 3.21: Publish device id
information through EIR.ver 3.18: Add more detailed decoding of EIR
elements.ver 3.16: Set EIR information from SDP database.ver 3.14: Add
correct Simple Pairing and EIR interaction.===================Now, I came
across another bit of info that links BlueZ to Python, which is what you
mentioned before. An app called "Blueman " at:
http://linux.softpedia.com/get/Utili...0673.shtmlsays "Blueman is
a GTK+ bluetooth management utility for GNOME using bluez dbus backend. The
aim is to create a full featured graphical bluetooth manager for
Linux."Unfortunately, I do not have access to a unix machine so I cannot try
"Blueman" to see if it gives EIR data. Do you know of a windows
version?Also, among other things it requires "Requirements: · GTK+ = 2.8.x,
· python-bluez"So, it seems that "python-bluez" indeed might be what I'm
looking for to get phone model number info. However, pyblues is EXACTLY
what you sent me before! Maybe you can now better tell, based on the above
info, where I might look in pybluez to find functions that can get the
extended inquiry response (EIR) data elements?I'm real close now. I'm hoping
for some luck here.Thanks again!Isaac"John Henderson"
wrote in message
...
Isaac wrote:

I was thinking the same way, but it seems like an impossible task to keep
up
with constant and large # of new models always coming out from so many
different makers. Do you think the manufacturers would provide the
model's
BD_ADDR base digits to developers/companies for legitimate commercial
use,

I doubt it.

that could work if was just one BT device in range, however, how would
you
ID a particular owner from a list of BT names within range, which should
be
the common case since you'd have to go to dense cell phone areas to even
have a chance to efficiently catch new phone models.

Request a session with the new device, pair with it, and read off
and store the manufacturer and model info with the standard "AT"
commands. This requires the cooperation of the new device's
owner, of course.

I take it that Python is the best in your opinion. I looked at the
Python
bluetooth module you pointed to. I see a function named
"find_devices()".
It mentions "ADVANCED PARAMETERS". I wonder if there are any cool
options
there to dig deeper into a BT device's technical info. This site you
pointed to said that DeviceDiscoverer class is a "Skeleton class". Do
you
think maybe there are more in-depth BT device inquiry/discovery functions
available somewhere else?

Maybe. I simply don't know.

John

Isaac wrote:

After more digging, I came across something that made me think about this
post. That is, it turns out that the BlueZ open source Bluetooth stack
(which BTW the Android uses) supports the BT 2.1 EIR spec. It supported EIR
device names from as far back as version 3.6 (currently its at ver 4.6), so
this should be a well supported feature by now in BlueZ. Here are the
revision history snips I farmed wrt EIR fixes (got it at BlueZ in Maemo
Bluetooth):
=================
ver 4.28: Set the adapter alias only after checking the EIR data.ver 3.6:
Add initial support for device names via EIR.ver 3.21: Publish device id
information through EIR.ver 3.18: Add more detailed decoding of EIR
elements.ver 3.16: Set EIR information from SDP database.ver 3.14: Add
correct Simple Pairing and EIR interaction.===================Now, I came
across another bit of info that links BlueZ to Python, which is what you
mentioned before. An app called "Blueman " at:
http://linux.softpedia.com/get/Utili...0673.shtmlsays "Blueman is
a GTK+ bluetooth management utility for GNOME using bluez dbus backend. The
aim is to create a full featured graphical bluetooth manager for
Linux."Unfortunately, I do not have access to a unix machine so I cannot try
"Blueman" to see if it gives EIR data. Do you know of a windows
version?Also, among other things it requires "Requirements: · GTK+ = 2.8.x,
· python-bluez"So, it seems that "python-bluez" indeed might be what I'm
looking for to get phone model number info. However, pyblues is EXACTLY
what you sent me before! Maybe you can now better tell, based on the above
info, where I might look in pybluez to find functions that can get the
extended inquiry response (EIR) data elements?I'm real close now. I'm hoping
for some luck here.Thanks again!Isaac"

As far as I can see, EIR is what is giving us the
user-modifiable device name already. This is not the holy grail
you're looking for.

John

No. Those are the "friendly names" that BT Spec 2.0 (at least) supported.
EIR when available is a deeper set of technical data meant to enable BT
device Plug-and-Play and/or to help filter out BT devices before pairing.
The "friendly" BT names, as you remark, are pretty useless b/c most people
change them.

"John Henderson" wrote in message
...
Isaac wrote:

After more digging, I came across something that made me think about this
post. That is, it turns out that the BlueZ open source Bluetooth stack
(which BTW the Android uses) supports the BT 2.1 EIR spec. It supported
EIR
device names from as far back as version 3.6 (currently its at ver 4.6),
so
this should be a well supported feature by now in BlueZ. Here are the
revision history snips I farmed wrt EIR fixes (got it at BlueZ in Maemo
Bluetooth):
snip
info, where I might look in pybluez to find functions that can get the
extended inquiry response (EIR) data elements?I'm real close now. I'm
hoping
for some luck here.Thanks again!Isaac"

As far as I can see, EIR is what is giving us the
user-modifiable device name already. This is not the holy grail
you're looking for.

John

Isaac wrote:

No. Those are the "friendly names" that BT Spec 2.0 (at least) supported.
EIR when available is a deeper set of technical data meant to enable BT
device Plug-and-Play and/or to help filter out BT devices before pairing.
The "friendly" BT names, as you remark, are pretty useless b/c most people
change them.

I note your answer without agreeing with it.

John

I think the best way to approach this is to become more or less self-sufficient.Constantly or periodically scan for new visible devices. That will give you the Bluetooth addresses, the protocols, and possibly the names (although my experience is that reading the name requires the device to be "in view" for longer").If you find any addresses for which you don't have amanufacturer, approach the owner for that information .