Will my Canadian phone work in Russia? - General Questions and Answers

OP MemberThanks: 1
For those who know about network bands etc, I am going to send my phone to a friend in Russia - I think I've done all the research on this as my brain can take, can someone help me verify if the Canadian variant of the A5 2017 work in Russia on MTS. My device is carrier UNLOCKED
Is there anything I'm missing, because it was pretty complex and there were terms like cat6 - I don't know what that means, but here is the info I came up with. Do all of these check boxes mean it will work?
Also, I checked and it appears that all versions of the A5 support the same networks, so I'm quite confused - why would they have different versions of they all support the same bands ?
---
Here are the MTS bands I've found on their website:
✓ means the A520W supports those bands
means A520W bands not supported.
*2G GSM*
bands
900 ✓
1800 ✓
*3G UMTS*
B1(2100) ✓
B8(900) ✓
*4G/LTE*
B1(2100) ✓
B3(1800) ✓
B7(2600) ✓
B20(800) ✓
B38(2600) ✓
B40(2300) ✓
B46(5200)
I really super appreciate any help that comes my way.

zarlydoug said:
OP MemberThanks: 1
...
*2G GSM*
bands
900 ✓
1800 ✓
*3G UMTS*
B1(2100) ✓
B8(900) ✓
*4G/LTE*
B1(2100) ✓
B3(1800) ✓
B7(2600) ✓
B20(800) ✓
B38(2600) ✓
B40(2300) ✓
B46(5200)
I really super appreciate any help that comes my way.
Click to expand...
Click to collapse
So first of all, compatibility following the country vary most of the time because of antennas (but also sometimes NFC or other thing but that's very rare).
As specified in this website ( https://www.frequencycheck.com/countries/russia ), Russia uses B3,B7,B20 (LTE), B1,B8(3G UMTS) and 900, 1800 for GSM.
So I'd say yes, this device is indeed compatible with Russia.

Related

[PROJ] Library of operator USSD commands

Hello!
I have an intersting project in mind that should help many people once it gathers steam - a list of USSD commands for all operators around the world.
You can help us by posting in this thread your operator name, country and useful USSD codes.
Also, if you know of any ready-to-use databases around the internet, please post a link here and we will add that info.
Best regards, Fahrbot team.
reserved for later
reserved for later 2
Just to get the ball rolling:
US
Cingular - *777# - balance
Sweden
Tele2 - *111# - balance/ timestamp
Ireland
Meteor - *#100# - balance
Belgium
PROXIMUS - #121# - balance/ timestamp
Germany
Vodafone - *100# - balance
eplus - *100# - balance
Portugal
UZO - *#123# - balance
Poland
Simplus - *100# - balance
Romania
Orange - *133# - balance/ sms/ timestamp
Mexico
Telcel - *133# - balance/ timestamp
Suriname
Digicel - *120# - balance/ timestamp
Malaysia
Digi - *128*1*1# - balance
bumping, still interested
Bump proj still active atm
T-Mobile USA USSD list
Here is the current T-Mobile USA USSD code as of 3/24/11
#225# (#BAL#) is for the balance on your account
#646# (#MIN#) displays the minute usage
#674# (#MSG#) displays the messages used in the cycle
#932# (#WEB#) displays the web usage on the line
#686# (#NUM#) displays your mobile number
#793# (#PWD#) will reset your voicemail password
#796# (#PWO#) will turn on or turn off your voicemail password
#763# (#ROF#) disables international roaming
AT&T
*3282# - Data Usage/Text Message Usage
*777# and tap Call. Account balance for prepaid
*225# and tap Call. Bill Balance. (Postpaid only)
*646# and tap Call. Check minutes. (Postpaid only)
Is this a GSM thing? I can't find any info for Sprint USSD codes..
Thanks for your replies!
wintrxtrem said:
Is this a GSM thing? I can't find any info for Sprint USSD codes..
Click to expand...
Click to collapse
yep, it's a GSM thing.
PCCW PREPAID SIM, HONG KONG
##122# - Remaining credit
Nepal:
Ncell:
*101# Balance Inquiry
*103# Phone no and registration inquiry.
NTC:
*400# Balance Inquiry
South Africa
Vodacom
*111# - balance
mtc touch Lebanon
*220# Remaining Balance-credits for calls/sms
Vodafone Egypt USSDs
*868*1# -- Balance inquiry.
*100# -- Date & Timestamp.
*150# -- Last caller & Call timestamp.
*878# -- Displays yoor phone number.
*888*5# -- Activate The Roaming Service.
*888*MobileNumber# -- PUK code request.
Thanks all for posting.
Some fresh meat
Vodafone UK
*#1345# - Check balance
Proximus Belguim
#121# - Check balance
Verizon US
#225 - Check balance
Poland - Play
*102# - Check balance
Poland - 36 i 6
*121# - Check balance
Country: South Africa
Network: Vodacom
Code: *111# : main menu for checking balances
then
option 1: balance enquiry
then
option 1: airtime balance
option 2: SMS balance
option 3: MMS balance
option 4: data bundle balance
MTN South Africa Codes
*141# - Balance Enquiry
*141*<PIN># - Recharge Request
*141*4# - Tariff Analyser and Priceplan Migrations menu
*141*4*0# - Tariff Analyser
*141*4*<Price Plan Option># - Priceplan migration
*141*6*<BundleSize># - Data bundle purchase
*141*6*0# - Data bundle cancellation
*141*6328*<MSISDN># - Me2U Top Up Request
*141*6328*<MSISDN>*<AMOUNT># - Me2U Transfer
*141*7*<BundleSize># SMS bundle purchase
*141*7*0# - SMS bundle cancellation
b3er said:
Poland - Play
*102# - Check balance
Click to expand...
Click to collapse
For me it is not for Balance but for extra minutes. I have Play Mixtura plan. For see full balance I use *101#, it works for display cash left. It also show time and date when balance is available to use. When I want to setup that, is shows 0.0. Date is in YYYY-MM-DD format, time HH-MM-SS.
Hey Her from thailand 3biggest operators USSD
AIS *139# Balance
Truemove #123# Balance
Dtac *121# Balance
btw , I use DTAC so I I know little more about them
Dtac *121*1# will be have a lot more detail for Balance

Question for owners/request for help - Google CellID API support on Mate9 Android 7

Hello, could any lucky owner of Huawei Mate 9 confirm one exciting feature of android 7 (atleast for me) that it works on this phone software.
As of Android 7.0 phone can read 2G/3G/LTE frequency without ROOT. Easiest way is to install app Cellmapper(mapping cell towers to map) https://play.google.com/store/apps/details?id=cellmapper.net.cellmapper
Could anyone run this app(enable "Use new Android 4.2 Cell ID API" in settings) and post screenshot while connected to LTE only(no wifi)? Also, maybe send debug report from settings menu to developer([email protected]) with screenshot.
Thank you.
Mate 9 is very interesting device regarding mobile LTE band support and speed
http://www.anandtech.com/show/10871/the-huawei-mate-9-review/10
The Kirin 960 includes a brand new HiSilicon LTE UE Category 12/13 modem that achieves speeds of up to 600 Mbps on the downlink and 150 Mbps on the uplink (2x20MHz carrier aggregation with 64-QAM). This new modem, which drops HiSilicon’s ‘Balong' branding, supports up to 8 data streams on the downlink using a combination of quad carrier aggregation (4x CA) and 4x4 MIMO (only for 2x CA). It also supports up to 256-QAM but not on all 8 streams. This gives it some flexibility in how it achieves its maximum throughput: (2x20MHz CA + 4x4 MIMO at 64-QAM) or (4x20MHz CA + 2x2 MIMO at 64-QAM).
Screenshot from app
https://www.dropbox.com/s/wnwj68sprurpz32/Screenshot_2017-01-27-22-48-56.jpg?dl=0
Debug file
https://www.dropbox.com/s/gw4mrca9v06do1g/debug.html?dl=0
dancrow said:
Screenshot from app
https://www.dropbox.com/s/wnwj68sprurpz32/Screenshot_2017-01-27-22-48-56.jpg?dl=0
Debug file
https://www.dropbox.com/s/gw4mrca9v06do1g/debug.html?dl=0
Click to expand...
Click to collapse
Thank you very much.
It seems with new cellular modem Huawei has implemented RIL properly. Good device for travelling and cellmapping.

[REQ] ROM compatibility patch for Telstra Australia.

Hi,
Looking for a ROM patch to have better carrier capability with carrier Telstra Australia telco so advanced 4G capabilities can be used on this network.
Goals are...
- VoLTE Compatibility
- VoWifi Enablement
- High Speed 4GX services
Let me know what you need. I can test on a 5T. Friends can test on a 6.
Unlikely unless Telstra supports it directly (which they don't)… So don't get your hopes up!

The specification of all cellular networks is now available on IMEI.info

In our database, we provide the information about more than 600 mobile networks from over 200 countries. Our pages contain the information about:
Country - you may read here such data as Country Name, Country Code, Country ISO
Carrier website - the official website of a mobile network operator. You can use that link to read more about the carrier.
Bands - here you can check out all bands provided by the operator. The mobile network specification contains such bands as GSM, UMTS, LTE, CDMA.
Protocols - the information about all protocols used by the carrier. You may get access to GSM, UMTS, LTE and CDMA protocols.
​
How to use carriers database
1. Open the Carriers Database section.
2. Find your desired carrier. You can search the mobile network by using the operator name, country or carrier code.
3. Afterwards, let’s open the page with your operator. Here you can check all details information.
Click here to read the article about Carriers Database and find out more information about mobile operators.

CellBroadcast and Emergency Warnings on Android - is it a mess?

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 ...

Categories

Resources