Related
WiFi Track: A wardriving / wifi survey app
WiFi Track is an Android wardriving app - it collects data about wifi networks in range, plots them on a map and lets you search them and see details per each wifi access point. Together with that it can generate lots of interesting charts based on different security settings, channels, manufacturers, mode of operation, etc.
FEATURES
=========
* Real-time network data acquisition and plotting:
- Networks plotted according to basic security type (Open, WEP, WPA)
- Detailed context information available per each wifi network on the map on click
- 2.4GHz / 5 GHz bands supported (if hardware available)
- Scan configurable (wifi scan period configurable depending on moving speed - standstill, walking, driving). GPS scan period also configurable. Several profiles available (High accuracy, Normal, Battery Save)
* Per-network details
- Basic parameters (SSID,BSSID, channel, hardware manufacturer, operating mode (infrastructure vs ad-hoc), etc
- Security parameters (encryption, authentication, WPS, security rating based on a number of parameters)
- Frequency interference with neighbouring networks plus advice to switch to another channel if necessary
- Nearest networks
* Background service mode which is very flexible and configurable:
- Exit at certain battery level
- TTS reports at configurable interval
- Sound notifications on new networks in range
- Distance / new network reporting
- Configurable option to lock wifi and prevent it from disabling on sleep
* Network filters (affect map view and possibly statistics)
You can filter by many criteria.
* Statistics and charts
- Per security type (Open, WEP, WPA, WPA2, WPA/WPA2 Mixed mode)
- Per WPA encryption type (CCMP, TKIP)
- Per manufacturer
- Per frequency band (2.4 vs 5 ghz)
- Per channel (for both 2.4 and 5 ghz ranges)
- Per operating mode (adhoc vs infrastructure)
- WPS enabled charts
- WPA authentication type charts (PSK vs EAP)
- Most often occured SSIDs
- Country the manufacturer is headquartered in and more
- Statistics can be either global or per map view and either affected by filters or not
* SSID search
* Export to KML file (to use with Google Earth)
DOWNLOAD
==========
Available for free (ad-supported) at Google Play:
details?id=com.gat3way.wifitrack
(The forum prevents me from posting URLs before I have 10 posts. That's the reason I can't post screenshots either. Sorry for that)
ABOUT ME
=========
My name is Milen Rangelov and I am more of a UNIX guy, developing GPU hash cracking software and this is my first Android app ever (and the second time I write Java code hehe). I guess there are lots of things to improve. I am open to suggestions and critics. Hope it will get better and better with time.
Thanks let me give it a try
hillz said:
Thanks let me give it a try
Click to expand...
Click to collapse
Hope you'd like it
Why do we need google services for your app? I am running cyanogenmod 11 and have no need to install all the google services till now.
Would be nice if I can give your app a try...
With FreetzMobil you could control various features of Freetz. You could query the state of the memory, swap, mounted devices and log files. Also you could view the status of the daemons and change it. The internet connection could be reestablished and the box coul be rebooted.
Newest features: Status of SMARTmontools, OpenVPN and ppp-cgi, diversions, telephone answering machine, alarm clock, ring blocker, wlan (guest, 2.4 & 5 GHz), Lan4-guest, dect, capi, USB remote access, mediaserver, ftp-server, samba, night timer.
This app contains English and German localisations.
Requirements
You need a Fritz!Box by AVM which uses a firmware based on version 1.2, 2.0(rc) or trunk of Freetz.
The security level "0" has to be set, see http://tiny.cc/a4qzcw
The connection uses the Freetz web interface, which runs mostly at port 81. To use FreetzMobil via the internet you have to forware this Port and use DynDNS. To set up this forwarding use the AVM-Firewall: http://tinyurl.com/5whw56r
Speed
The processing speed depens on many facotrs. First the connection: UMTS has a higher latency than local WLAN. Also the Fritz Box itself could slow down. A FRITZ!Box Fon WLAN 7170 has a crucial slower cpu and only a quarter of memory than a AVM FRITZ!Box Fon WLAN 7390.
DONATE: If you encrypt the connection with SSL (via stunnel or lighttpd) it will a bit more slower.
Donation
No self-promotion in the app.
Access cia encrypted HTTPS is available
More than 2 devices could be created
You support this app and further development!
Play Store: http://tinyurl.com/k2d57sd
Changelog: http://tinyurl.com/ktzhcl3 (Google Tranlator bar on the top)
Included translations are german and english.
My personal intension to create this app:
I didn't like to use the Freetz web interface on my small cell phone. So i wrote this app
Hello,
I'd like to start with this as my first post on this wonderful forum, Because I'll still be sharing awesome contents henceforth.
I found this wonderful app and I thought I should share it with my friends.
It's about how you can simulate your phones connection speed to 4G(LTE).
We all know that in terms of connection speed, 4G is better than 3G, so for those that wants to have a fast speed connection, try this app.
I'll share the Download link at the end of this post.
3G to 4G converter provides multiple functionalities. Following features are included in one single app:
– Get Phone Details like IMEI Number, Service Provider Name, Android ID, Phone type like GCM or CDMA
– Get Sim Details Serial Number, Country details, Operator Name, Subscriber ID and Operator Code.
– Get WIFI connection details : Link speed, Frequency, IP Address, Network, RSSI, MAC Address and SSID
– Internet speed testing meter.
– Check if your mobile supports VoLte or not.
– 3G to 4G and 4G to 3G converter simulator.
> HACK: Don't Close the app after converting, let it run in the background.
Download Link
datafilehost*com/d/fe5a6f81
Change *com to dot(.com)
> Disclaimer: I am not in anyway promoting this app, neither am I an affiliate or neither do I receive commission for each download.
Hey,
Germany is implementing EU-Alert (ETSI TS 102 900 [1]) at the moment and referring to the local News, it is a huge mess [2].
But let's start at the beginning.
CellBroadcast is a core component of each mobile network generation (2G,3G,4G,5G,...) and part of the 3GPP spec. CellBroadcast basically allows the network to send a simple SMS to all mobile phones connected to a specific base station. Thes SMS-CB are sent with a Message Identifier (aka Channel, aka Topic) which gives them a special purpose by convention. e.g. ID / Channel 50 is often used for area related information [3], while channel 207 might broadcast local weather information. Since not all Channels are standardized, there is also the option to broadcast an Index that lists all channels with a description. And since users probably don't want any message broadcasted, users have to subscribe to these channels.
Since decades now, CellBroadcast is also used for public Emergency Warnings. This means that, by definition of a country, a specific channel is used to broadcast Emergency Warnings. Long time ago, in many countries it looks like Channel 919 was used for this purpose. For this to work properly, mobile phones were instructed to subscribe to channel 919 by default and also use a special ringtone (even if muted) to alert such a message.
Later - over 12 years ago - additional channels from 4370-4399 were standardized in ETSI TS 123 041 [4] for public warning systems like CMAS, EU-Alert, KPAS. All using the same channels which is beneficial for global roaming.
Android of course supports these public warning systems specified in ETSI TS 123 041 [4] since at least Android 4.2.2 [5]. And nations that use these systems already, like CMAS in the US, report very high and reliable coverage.
However, referring to German news [2] and government, not many phones that are currently on the market will actually support EU-Alert in Germany, despite already supporting EU-Alert in Netherlands or CMAS in the US.
How is this possible when exactly the same SMS-CB is broadcasted, just in a different country?
Golem [2] says that Samsung and Google already confirmed that EU-Alert is currently not supported in Germany, but updates will be rolled out to recent devices.
This strongly suggests to me that OEMs like Samsung and Google actually added country specific filters/configurations for these public warning systems to their phones without deploying a reasonable fallback. Public warning systems based on ETSI TS 123 041 [4] thus may only work in countries that were known to use these systems when the phone was released.
Isn't this an obvious issue?
Google said, starting with Android 11+ it will be possible to update the CellBroadcastReceiver App via Google Play. So devices with Android 11+ will likely receive an update to support EU-Alert in Germany. For Android 10 and older, OEMs will have to supply updates.
What also confuses me is the fact that all Android Phones I own (Nexus 4 with Android 5, Nexus 5X with Android 8, Pixel 3a with Android 12) here in Germany do actually offer the setting for Emergency Warnings and they are already enabled by default. So I assume they would work? Did Google actually deploy a sane default configuration here already?
But if they did - why isn't it working on ALL Android 11+ Phones already? I'm pretty sure my Pixel 3a uses Googles CellBroadcastReceiver App which is provided through the Play Store. So all Android 11+ phones should already use the exact same App?! Or am I wrong here? So what is this update Google actually needs to provide?
And does this also mean that with Android 11+ OEMs are not allowed / cannot implement their own Emergency Warning CellBroadcastReceiver?
This topic is really confusing to me
Shouldn't it be really simple?
All phones, regardless of the OEM, should have a proper SMS-CB Application which allows you to subscribe to custom channels, view the index, and manage your SMS-CB Messages.
Phones should also be aware of special channels to apply special ringtones etc if needed, but they should have a sane fallbacks!
A phone that knows about NL-Alert and CMAS may call messages on Channel 4370 received in the Netherlands "NL-Alert". But when it receives the same message in Germany, it shouldn't just drop it! It should display it as warning and call it whatever it wants. And if it doesn't know about CMAS / EU-Alert, it should just receive it as regular SMS-CB.
Can't be that hard?
Interestingly enough, Samsung phones allow you to subscribe to custom channels. Google phones do not :/
Should there be a better / more enforced standard, so that a country that wants to implement CMAS/EU-Alert in the future doesn't have to rely on OEMs help?
And finally some technical Questions:
I found zero Apps for Android that would allow me to subscribe to custom CellBroadcast Channels on my Google Android phones. Is this even possible?
Also, is it possible to test these CellBroadcasts somehow? Is it possible to write an App that can inject SMS-CB into the system?
Sorry for the long post, but I think this an important Topic.
Let me know what you think
Do you have experience with these Emergency Warnings already?
[1] https://www.etsi.org/deliver/etsi_ts/102900_102999/102900/
[2] https://www.golem.de/news/cell-broadcast-warum-es-am-warntag-ruhig-bleiben-koennte-2206-165822.html
[3] https://source.android.com/devices/architecture/modular-system/cellbroadcast#channel-50
[4] https://www.etsi.org/deliver/etsi_ts/123000_123099/123041/11.04.00_60/ts_123041v110400p.pdf
[5] https://cs.android.com/android/plat...ternal/telephony/gsm/SmsCbConstants.java;l=58
Hey! I was just researching something about this. Thanks for your detailed post.
I am from Chile and, in my case, my operator had subscriptions to two channels: 919 and 920.
In order to see the Cell Broadcast menu in the Messages app, I had to override a CSC setting (I use a Samsung device), particularly "CarrierFeature_Message_DisableMenuCBMessage") because it seems some Chilean operators ordered Samsung to hide it.
Even then, the Google Cell Broadcast app would not let me modify settings other than test alerts.
In my country these emergency alerts are quite unreliable and are often sent by mistake or to the wrong place (i.e. sending a tsunami alert to an area more than 100 km away from the coast).
Shooting Star Max said:
Hey! I was just researching something about this. Thanks for your detailed post.
I am from Chile and, in my case, my operator had subscriptions to two channels: 919 and 920.
In order to see the Cell Broadcast menu in the Messages app, I had to override a CSC setting (I use a Samsung device), particularly "CarrierFeature_Message_DisableMenuCBMessage") because it seems some Chilean operators ordered Samsung to hide it.
Even then, the Google Cell Broadcast app would not let me modify settings other than test alerts.
In my country these emergency alerts are quite unreliable and are often sent by mistake or to the wrong place (i.e. sending a tsunami alert to an area more than 100 km away from the coast).
Click to expand...
Click to collapse
Can you explain how you disabled this CSC setting and on what samsung phone/os?
You can see Googles/Androids latest default configuration for Chile (MCC 730) here:
https://cs.android.com/android/plat...apps/CellBroadcastReceiver/res/values-mcc730/
The config.xml really has some restrictive features enabled :/
Thanks for your reply!
Please note that all the following information assumes you have rooted your device. It's impossible to override this configuration otherwise.
My device is a Galaxy Note20 Ultra (Exynos version, SM‑N985F) running Android 12, One UI 4.1.
As you might know, Samsung devices include several packages named “CSC”, which define settings according to a sales code matching with a region. For example, a device sold in Chile without a carrier uses the sales code CHO, while one sold by operator Movistar uses the sales code CHT.
In the Galaxy Note20 Ultra, the CSC packages are stored in /optics/config/carriers/single (older Samsung devices might use /omc/).
Once you find the sales code matching with your current configuration, you can grab two files: cscfeature.xml and customer_carrier_feature.json. Taking CHO again as an example, the files would be /optics/config/carriers/single/CHO/conf/system/cscfeature.xml and/optics/config/carriers/single/CHO/conf/system/customer_carrier_feature.json.
These files are encoded, but OmcTextDecoder can take care of that.
In the case of CHO, customer_carrier_feature.json has the value "CarrierFeature_Message_DisableMenuCBMessage":"TRUE", which hides the cell broadcast menu in the stock Messages application. Just replace “TRUE” with “FALSE”, save the file and push it to its location. The next time you reboot your system, it will be applied.
Regarding the link you sent, I think we could get around that configuration by decompiling the GoogleCellBroadcastApp.apk through Apktool, modifying the restrictive values, and then pushing the APK to the device, replacing the original version.
Thank you!
Let me know if you managed to patch your original CellBroadcastReceiver.apk!
I actually tried using Runtime Resource Overlays (RROs) which is described on the official docu about CellBroadcast in Android.
You can find the result here: https://github.com/xsrf/android-de-alert
However, I didn't quite get these RROs. It looked like in Oreo you can use RROs to overlay any resource of any app without any permissions or matching signatures, which is quite a surprise to me?!
On my phones with more recent OS, I get signature mismatch errors and also it looks like apps now have to define what resources can be overlayed ...
Hello,
I bought my OP7Pro when I was living in Netherlands. Now that I live in Indonesia, I notice that my phone doesn't detect all WLAN 5GHz channels allowed in here, only channels 149-161.
Based on Wikipedia, channels 32-48 & 52-68 are also allowed though indoors only. I found out that channels 149-161 are allowed initially while the rest follow a few years later.
The problem is that my device only follows the initial regulation but not the latter one so it cannot detect nor join WLAN with channels 32-68 while in Indonesia.
Is there a way I can do that?
Thank you in advance!
I tested Wifi Codes app but it crashes probably because it's too old.
From this post and this post, it looks like Android sets the WLAN country based on the SIM card country data so that makes me think that the country rules DB used in Oxygen OS is out-of-date or something like that as other Android devices sold here can detect all proper channels.