Related
So... I'm rather new here and I'm not 100% sure that this is the correct forum to post this in (since I know it says "xda developed apps/games only"). However, I have seen commercial Android apps discussed here before... so... *shrug*.
Let me first say that I am not the developer... I just think this app should get some attention.
Pixie Network Monitor by 9bitlabs (would post a link but my account is restricted. ;-) )
It is a network monitoring app similar to Wireshark, but for Android. It is $4.99 on the Android market, it requires root, and it does not work on all phones (since not all phones can have their wifi put into promiscuous mode). There is a companion app called "Pixie Probe" available on the market for free. Pixie Probe will determine whether or not your phone is compatible with Pixie.
I have tested it out on my Evo (running CM6.1 RC1) and it seems to work amazingly well.
Pixie does not contain all of the features of Wireshark/Kismet. This is from the Pixie FAQ:
Q: What's the difference between Pixie and a desktop tool like Kismet?
A: The biggest difference between the tools lies in how they interface with the network. Kismet interacts directly with the wireless adapter and places it in monitor mode, allowing it to hear any packet over the wifi, even if it is not associated with a network. This can be problematic with some hardware, but many of the newer wifi chipsets work great with Kismet.
Pixie, on the other hand, is constrained by Android. Rather than expose the wifi adapter as an 802.11b device, Android actually hides all of that functionality: the wifi connection actually appears to system processes as a plain old Ethernet device. This means that we don't get monitor mode and we also don't get to see wifi-specific data, such as beacons and associate/disassociate packets.
On the plus side, Pixie runs in your pocket and that's harder to do with Kismet, unless you have very large pockets. Pixie is also significantly easier to set up for folks without Linux experience.
Click to expand...
Click to collapse
The Pixie website gives very detailed information about the app, so I suggest you go there if you want more info.
In any case, I hope other people find it useful.
Hi all,
I spent a couple of days Googling around, trying to get Bluetooth DUN working on Cyanogenmod 7.1.0 on my Viewsonic GTablet.
After some hacking around with the source, I got it working. I can connect my GTablet to the internet through my Blackberry Torch on Rogers (in Ontario, Canada).
I've already posted my notes to the CM forums, but apparently since I'm a noob here I can't post the link to it, so here's my notes (direct copied from the CM forums):
Dial-up networking requires the chat binary, which is included in the standard Linux ppp package. For some reason, this binary was omitted from the Android ppp package, so I downloaded the Android 2.3.7 source, copied the chat source in to the Android ppp package and built it from scratch. The instructions for this were found at afewe DOT wordpress DOT com/android-arm-development/use-point-to-point-protocol-ppp-in-android/
Once the chat binary is installed in the proper location on the Android device (/system/bin/chat) it's just a matter of writing a pppd config and chatscript for your given provider. These configs can be found in the berry4all package at berry4all DOT com.
I copied the 'rogers' file from that package and put it in /etc/ppp/peers/rogers, then the rogers-chat file and put it in /etc/ppp/chatscripts/rogers-chat.
I modified the /etc/ppp/peers/rogers so that the last line, which calls the chat binary, reflected the proper locations of the binary and the chat script.
Finally, I removed the 'novj' option from the pppd config. Once the config was all up and ready to go, I went to the terminal and did:
$ su
# rfcomm bind /dev/rfcomm0 <BT MAC> <channel>
# pppd call rogers
And voila! A stable, bluetooth dial-up network connection through my phone.
I just wanted to throw out my notes first to make people aware that its possible and easy. If there's enough interest, I'll write a more detailed and specific step-by-step howto on getting it set up.
Hi,
I see that CM 7.1 includes "bluetooth tether" support now but it's not clear to me what this actually is. Does CM 7.1 include the DUN bluetooth profile? It sounds like you're using reverse tethering, i.e. you are using a Blackberry's data connection so you're using the DUN profile on the Blackberry and are using the CM device as a client?
I have a stock Desire S and am looking for DUN support so I can use the internet access in my car through the Desire's 3G connection. The car supports only DUN and PDANet doesn't work for some reason.
Thanks,
Tim
Looks like you're out of luck.... same story for my Benz with Comand Online Navcom system.
If you drive an MB like me, you'll have to wait for an update later this year (from MB that is)... or buy a BlackBerry.
Sent from my GT-P7500 using Tapatalk
Is it confirmed that mercedes benz are providing this update?
Sent from my GT-I9100 using Tapatalk
I very much doubt it (I'm also trying to get it working with Comand Online).
http://telematicsnews.info/2011/08/...connectivity-options-to-comand-online_ag2223/
Not great news.
tj80 said:
I very much doubt it (I'm also trying to get it working with Comand Online).
Click to expand...
Click to collapse
From the press release:
"An option for customers having phones without DUN support is the Mercedes-Benz “Bluetooth (SAP) telephone module - V4″, available early 2012. The new version (V4) offers UMTS capability, allowing fast data connection using customer SIM card or accessing SIM information from SAP (SIM Access Profile) enabled mobile phone."
and:
"... Furthermore Mercedes-Benz is in close talks with leading Android phone vendors to enable the DUN feature in their phones by default."
(I have Android 2.3 and Windows Phone 7.5 devices)
Yes, so we can pay £400 for a SAP module or buy a new phone if anyone actually launches an Android handset with DUN - remembering that Google appear to have zero interest so it will be manufacturer specific. Oh yes, I nearly forgot - Android doesn't have SAP profile support either!
I'd say the chances of Mercedes updating existing systems to work with phones which don't support DUN is virtually zero. Hardly ideal on a system which cost £2000...
Cheers,
Tim
I agree. It was a huge mistake of MB to go with this dead BT DUN protocol!
I thought Android phones do support SAP, isn't that why the car can dial a contact?
agupta80 said:
I thought Android phones do support SAP, isn't that why the car can dial a contact?
Click to expand...
Click to collapse
'fraid not, that uses PBAP (phone book access protocol).
I have a European 3G Xoom running EOS ICS 2. We also have an old HP450 Mobile printer that has a slot for a Compact Flash I Bluetooth card. My question is would we be able to set this printer up to print directly from the Xoom?
The details of the Bluetooth card read:
Serial Port Profile (SPP): Emulates a serial port to enable wireless printing from compatible Bluetooth serial sending device(s).
Hardcopy Cable Replacement Profile (HCRP): Provides the same printing experience (print quality and print speed) as when printing with a cable.
Object Push Profile (OPP): Enables printing from devices that use the OBEX (Object Exchange) protocol.
Basic Printing Profile (BPP): Extends the capabilities of the OBEX protocol and lets you print a variety of content from Bluetooth-enabled devices.
Does Android support any of those Bluetooth printing protocols?
Thanks.
Check bigrushdog's tegra 2 thread in Development. There are a ton of drivers available...maybe you'll find the ones you need.
okantomi said:
Check bigrushdog's tegra 2 thread in Development. There are a ton of drivers available...maybe you'll find the ones you need.
Click to expand...
Click to collapse
Thanks for the info but it looks to me as though I would need some programming knowledge to be able to try these out?
lesmorton said:
Thanks for the info but it looks to me as though I would need some programming knowledge to be able to try these out?
Click to expand...
Click to collapse
The easiest you download starprint app from google play and try it. If it works pay few bucks to remove the watermark. it is cool app.
Ray Maker of DC Rainmaker on Twitter reports ANT+ is coming to the Samsung Galaxy S4 through an October Firmware update and will be supported on all flagship devices going into the future
dcrainmakerblog
"We will support ANT+ in the Galaxy S4 in a firmware update coming in October" - Samsung (at the ANT+ Symposium)
dcrainmakerblog
"We do plan to support ANT+ on all of our flagship smartphone devices in the future" - Samsung (at the ANT+ Symposium)
Ray now has a blog post about this:
http://www.dcrainmaker.com/2013/10/samsung-mobile-devices.html
Particularly for anyone with sports data tracking devices this is huge news! Not to mention ANT+ is pretty simple to implement now with the new Plugin services they're bundling with the Note 3 right now
ANT also allows you to build really neat wireless topologies as well if your into that stuff, plus it supports full multicast as seen on DC Rainmaker:
http://www.dcrainmaker.com/2013/09/curiositysurvey-different-cycling.html
A little background on ANT and ANT+:
ANT is a mature ultra low power wireless protocol running on the 2.4 GHz band like WiFi and Bluetooth. Bluetooth Smart is a protocol similar to ANT but architected around Bluetooth style bonding/pairing with several connection layers and services.
ANT is a compact and flexible protocol, allowing virtually any type of wireless network topology to be created. ANT transmitters automatically manage coexistence and divide the RF channel they are transmitting on into timeslots, which means any number of receivers can listen to an ANT device, excellent for gyms, training areas, anything which requires a large number of transmitters, as ANT can handle potentially hundreds of devices transmitting to an infinite number of receivers.
ANT+ is a set of interoperability specifications called "Device Profiles" which means devices which use them are able to "talk" to one another. ANT+ has reportedly shipped in over 60+ million devices globally, predominantly in Sports and Fitness (Adidas miCoach, Garmin Watches, Running Sensors, Heart Rate Straps, etc).
Why does this matter?
Right now, it only matters if you're into any type of sports or fitness training, or if you have an idea which requires 600+ transmitters communicating to XXX number of receivers simultaneously. As a nice bonus, any ANT+ device is compatible with any app as long as it's certified.
For developers
The ANT+ API appears to be much simpler to implement than the BLE API. The ANT+ API already handles device discovery and decoding of data events from sensors into the useful data without even reading the Device Profile. You just request access to heart rate, cadence, etc, and then subscribe to the event handlers which pass the data to you decoded. The BLE API still requires a lot of work to do the decoding properly, handling characteristics, etc
ANT+ Plugin API - Supported from Android 2.1+
http://www.thisisant.com/APIassets/.../plugins/antplus/pcc/AntPlusHeartRatePcc.html
BLE - Officially integrated from Android 4.3+
http://developer.android.com/guide/topics/connectivity/bluetooth-le.html
Some Apps which include ANT+:
-Google My Tracks
-Endomondo
-Sportstracklive
-Garmin Fit™
-Run.GPS Trainer UV
-IpBike, IpWatts, IpPeloton, IpSmartHr
-Selfloops
-SportyPal
-MapMyFITNESS/RIDE/RUN/WALK+/HIKE/DOGWALK
Directory of Certified Devices
http://www.thisisant.com/directory
How will it help us exactly?
fuser1337 said:
How will it help us exactly?
Click to expand...
Click to collapse
Right now its used mostly in sports and fitness although some of those device profiles they've implemented are branching into things like remote control like the O-synce bike handle bar remotes. They submitted patches for Apollo but the developer's busy with other features ATM.
sounds like bloat..
dannyella said:
sounds like bloat..
Click to expand...
Click to collapse
It depends on how you use your phone.
For fitness addicts like me, that is good news.
In general, there are different protocols to transfer the data from your heart rate belt. Most devices for home use like spinning use the ANT+ - protocol. Others use the Bluetooth 3.o 0r 4.0 protocol.
BT 4.0 LE (Low Energy = battery saving) is implemented to Android 4.3. I am guessing that it is the same with ANT+.
Benefit for Android-users: You can use your heart rate belt that you use with your home device also with your Android phone
I use ant to build my projects.. lol..
Sent from my GT-I9500 using XDA Premium 4 mobile app
Great news! Any reference?
Sent from my GT-I9505 using xda app-developers app
it's an interesting move for Samsung to make. Considering they and their competitors are bringing out smart watches using bt4 and android 4.3 standardising bt4 api. It was starting to look like ant+ was going to lose the smartphone market. Perhaps they cut a deal with Samsung
Infy_AsiX said:
it's an interesting move for Samsung to make. Considering they and their competitors are bringing out smart watches using bt4 and android 4.3 standardising bt4 api. It was starting to look like ant+ was going to lose the smartphone market. Perhaps they cut a deal with Samsung
Click to expand...
Click to collapse
Honestly, Ill believe Ant+ inclusion when it actually happens. BT4 smart has started to catch on with cycling manufacters, both Topeak (currently) and Wahoo (soon) will be able to use bt4 smart sensors soon. I saw a S4 at Interbike hooked up to a BT smart heartrate monitor and speed/cadence sensor.
This was big news to me, as for a long time without a dongle (super annoying) there was no way to use an Android phone with speed/cadence sensors or heartrate monitors, unless you had a sony.
If Ant+ doesnt pick up soon, its going to be left behind. Android including BT smart in 4.3 is going to change the field for newer phones.
I too would like to see some documentation/references about Ant+ inclusion.
-Bicycle Industry Professional
After flashing the 4.3 leak i noticed some ANT library packages in the 'installed packages' list.
I found the app "ANT+ Demo" from the app store and it is reading my ANT device! It's already working!
It is working with an ANT+ development kit i have here on my desk, haven't tried it with any official devices yet.
I do have ant+ and some ant plugins installed on my note 3. Factory untouched android 4.3
Sent from my C6802 using XDA Premium 4 mobile app
Subscribing
jorgenmk said:
After flashing the 4.3 leak i noticed some ANT library packages in the 'installed packages' list.
I found the app "ANT+ Demo" from the app store and it is reading my ANT device! It's already working!
It is working with an ANT+ development kit i have here on my desk, haven't tried it with any official devices yet.
Click to expand...
Click to collapse
What "4.3 leak" did you flash? Can you tell us the rom? Can we have some links/references? Where do I get the packages so I can bribe some S4 cook to bake it into some rom? (or am I missusing the term?)
I use ANT+ to upload my running activities from my garmin watch to the garmin website. As the watch can only comunicate via ANT+, I either have to have a PC around or, when in holiday or somehting, I have to use a micro usb otg adapter and connect the ANT+ dongle to my samsung s2 using an app called garmin-uploader (along with a coupple of ant+ services found on google play).
There is something that I don't quite understand here.
Does this mean that these devices listed (s4 and s3 I believe) were already shipped with ANT+ capable hardware?
ANT+ was therefore already possible on them by using the ANT+ radio service available on google play without the need of an ANT+ dongle right ?
If not, and the hardware has to be enabled somehow with a propretary driver of Samsung, how about the Samsung S4 Google edition? Those don’t have a Samsung customized ROM but a google vanilla Android right?
Also, DCrainmaker wrote a post about the matter :
http://www.dcrainmaker.com/2013/10/samsung-mobile-devices.html
I see the lack of balls in Samsung to not include the S4 active to get ant+. It's worth pointing out amoled screens are organic and have their life degraded by heat as well as UV light.
there's some photos posted a couple times on xda forums where someone bought a store display s3 or note 2 that had the original screen sticker decals shadow burnt into the screen. In fact it was the rest of the screen that was exposed to the light that had degraded. The sticker decals had shaded the screen and not degraded some parts leaving their shape visible on a white screen.
I suppose it doesn't matter for indoor sports at least...
here's a couple of examples a quick Google search pulls up
forum.xda-developers.com/showthread.php?p=39910331
forum.xda-developers.com/showthread.php?p=34705628
?????? Galaxy S3 ??????
this thread needs a *BUMP* !!
Has anyone checked if ANT+ his working in the I9505XXUEMI8 leak?
http://forum.xda-developers.com/showthread.php?t=2465713
It is showing running for me under running processes. Doesn't seem to make any difference to me though
Sent from my GT-I9505 using xda app-developers app
bennetski said:
It is showing running for me under running processes. Doesn't seem to make any difference to me though
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Do you have any ANT+ equipment to test with an app? (Believe endomondo supports ant+ HRM)
Considering updating to the leaked firmware, but the whole KNOX thing is making me a bit reluctant...
Unfortunately I don't have any supporting equipment. I am one of the lucky ones to have got the leaked 4.3 without getting knox installed but I wasn't really bothered even if I did. It's just a warranty void. It's actually very hard to brick an S4.
Sent from my GT-I9505 using xda app-developers app
Great news. Another 10 or more MB spent on software which is dedicated to communicate with specific hardware, and if you do not have such, it will be silently running in background consuming the battery and memory.
I have advice foe Samsung: guys, please do not forget about the dedicated BT controller to very common equipment like Boeing 737 or Airbus series 3 (310, 319, 320, 330, 340 380 etc.).
These planes are really popular nowadays and each pilot would really appreciate if he could for example control the flaps while playing Jewels
This app simply shows WiFi chipset vendor from the WiFi MAC Address.
Download WiFi Chipset INFO: https://play.google.com/store/apps/details?id=org.vndnguyen.wifichipset
Enjoy!
v1.0.2: Minor bug fixes.
v1.0.1: Initial release.
All fine on Z Play with LOS14.1
Everything is fine for me. thanks for all
My Xperia S should have a BCM4330, but it's just reported as "Sony Ericsson Mobile Communications AB"
My Nexus 7 (2012) bas a BCM4330, too, but is reported as "Asustek Computer Inc" ... nevertheless as far as I know th BCM4330 should be secure.
Stock HTC U11 is save
Is this checking 43XX or only specific models? Based on the CVE my S8 is affected seeing as it's BCM43xx (S8 is BCM4361 )
My ZTE Axon 7 is fine! No worries there!
Is this app open source?
All fine on my Motorola Nexus 6 with latest Pure Nexus Rom :good:
Sent from my Nexus 6 using XDA Labs
I believe this app just looks at the MAC Address OUI of your wifi interface - which is not an accurate way of determining if your phone is potentially vulnerable to Broadpwn
WARNING TO ALL
Bogus results, do not trust this app at the time of this post! States my WiFi chip in my LG G5 is "made by LG Electronics" and I'm safe from BroadPwn. However, a physical teardown (https://www.ifixit.com/Teardown/LG+G5+Teardown/61205) clearly shows the motherboard using a vulnerable Broadcom BCM43xx series chip, namely Broadcom BCM43455.
LG's own Security Bulletin page also has not listed BroadPwn's code CVE-2017-9417 yet, so it is still not patched by the manufacturer and thus is vulnerable. (https://lgsecurity.lge.com/security_updates.html)
The information this app is pulling from the system is inaccurate. MAC Addresses tell you the manufacturer of the entire device, NOT the specific WiFi chip on the motherboard itself. Otherwise Samsungs and LGs and Apples would *all* be listed as "Broadcom" in router logs...
Many here actually have Broadcom chips and are now duped into a false sense of security as a result of this app. This needs to be removed from here and the XDA Portal ASAP before more are fooled. Users, please remain skeptical and investigate your hardware more closely than just this one app.
Please update the app to detect BCM4361 in S8/S8+. It should not be looking at the Murata packaging.
The app uses the wifi mac address and runs it again a mac address database.
That is not a working solution to detect the wifi chip in a smartphone.
The OnePlus 3 uses a Qualcomm QCA6174 chip. But it is detected as "OnePlus Tech (Shenzhen)Ltd" because they use their own mac address like nearly every smartphone vendor
It would be better to use other hardware IDs e.g. the one you get via lspci.
If you are not checking the patch level the Nexus 6 should be listed as vulnerable as it is listed in the original article.
MAC Addresses tell you the manufacturer of the entire device, NOT the specific WiFi chip on the motherboard itself.
Click to expand...
Click to collapse
Nope, the above quoted clause is not correct.
My Galaxy Note 4 comes with the WiFi MAC address 90:B6:86:1A:74:FE and it's from Murata Manufacturing Co. (a manufacturer from Japan), not from Samsung itself.
OnePlus 5 safe.
vndnguyen said:
Nope, the above quoted clause is not correct.
My Galaxy Note 4 comes with the WiFi MAC address 90:B6:86:1A:74:FE and it's from Murata Manufacturing Co. (a manufacturer from Japan), not from Samsung itself.
Click to expand...
Click to collapse
Let me clarify by revising that statement to be "MAC Address will tell you the network components' vendor (may or may not match manufacturer of the rest of the device), but NOT the specific chips used as part of the networking circuits."
That's why BroadPwn is a very scary exploit, the Broadcom 43xx chips are used as part of many different networking packages and rebrandings from vendors other than Broadcom itself. This chip family is so common it affects billions of mobile devices.
**Your rebuttal precisely shows yourself to be at risk.**
Murata Manufacturing Co. is sourced on many Smasung devices to provide networking components, but they source specific chips from others. If you look at their products pages you will find they list the specific chipsets used, many of which are Cypress brand chips. e.g. http://wireless.murata.com/eng/products/rf-modules-1/wi-fi-bluetooth.html
Cypress acquired Broadcom; all CYW43xx chips are direct renames of BCM43xx chips mentioned at the heart of the BroadPwn exploit. http://www.cypress.com/documentatio...wifi-ieee-80211ac-macbasebandradio-integrated (PDF link on that page explains the renaming of the chip series.)
To summarize: Samsung often uses Murata packages, which include Cypress, which includes Broadcom. In the case of your Galaxy Note 4, it has a BCM4358 chip in it.
http://www.anandtech.com/show/8613/the-samsung-galaxy-note-4-review/9
BCM4358 is specifically listed as a known vulnerable target of the BroadPwn exploit. It will be discussed in detail at Black Hat USA 2017.
https://nvd.nist.gov/vuln/detail/CVE-2017-9417
https://www.blackhat.com/us-17/brie...os-via-a-bug-in-broadcoms-wi-fi-chipsets-7603
If I may ask the exact method of your app, is it simply looking up the MAC Address against a vendor database? If so,1) Vendors not named Broadcom that use BCM43XX chips as a piece of their packages will erroneously show as OK, and 2) Broadcom's own networking products not including chips from the BCM43XX family may falsely be reported as vulnerable.
All of this said, please reconsider keeping your app published as it is; either take it down or revise the code ASAP. To reiterate it is dangerous to erroneously tell other device owners they are safe based on MAC Address info alone, just because it returns a vendor value other than "Broadcom". A vulnerable BCM43xx chip likely still lurks underneath the other names.
OK thank you all for your clarifications.
To avoid misunderstanding, I have removed the "BroadPwn check".
The app now only shows WiFi MAC vendor from the WiFi MAC address.
It does not check for the BroadPwn issue anymore.
Sorry for the inconvenience.
The app is up again in the Play Store.