온누리070 플레이스토어 다운로드
    acrobits softphone
     온누리 070 카카오 프러스 친구추가온누리 070 카카오 프러스 친구추가친추
     카카오톡 채팅 상담 카카오톡 채팅 상담카톡
     라인으로 공유


   ◎위챗 : speedseoul



    before pay call 0088 from app


The IMEI is the 'MAC' for the telephony module - the unique ID that the telephone uses when it connects via GSM/GPRS/HSPDA/etc. The GSM network uses it to route calls and data from the phone over the GSM network right up to the gateway into the Internet (which is an IP network).

A telephony module is a chip or circuit board that handles the telephone network, either GSM or CMDA, and often has a slot for a removable SIM card. Some phones have more than one telephony module (active dual- or multi-SIM phones). Each telephony module has its own IMEI.

Manufacturers give each phone (strictly the telephony module) a unique IMEI during manufacturing. However the number can normally be rewritten if you have the right software. This is often done after a phone has been stolen to give the phone a new identity and bipass stolen phone blocking system.

The IMEI can be programmatically obtained using the TelephonyManager.getDeviceId() API.

CDMA phones have a ESN or MEID which are different lengths and formats, even though it is retrieved using the same API.

Android devices without telephony modules - for example many tablets and TV devices - do not have an IMEI. As Schlangi commented, some devices that do not have a telephony module fake the IMEI, so the presence of an IMEI does not (always) guarantee the device has a telephony module.


The ANDROID_ID is another unique number on the phone - this is automatically generated by the OS as it boots for the first time (doing it this way makes it much easier for the manufacturers by removing a step from the production line).

The ANDROID_ID can (and does) change, for example:

It is mainly used by developers (eg identifying and connecting to devices using adb)

ANDROID_ID can be used to identify an Android device given the caveats above, realistically meaning that it uniquely identifies the device over significant portions of the device lifetime, but cannot be relied on.

Also note that there was a bug in Froyo where many devices gave themselves the same ANDROID_ID. This is the bug

Other identifiers

There are a number of other things that can be used identify the device:

  • MAC address of the WiFi module: WifiManager.getConnectionInfo() -> WifiInfo.getMacAddress(). This can often be changed in software, but generally is constant over the device lifetime. Also it can only be read if the WiFi module is switched on.
  • MAC address of the BlueTooth module: BluetoothAdaptor.getAddress(). Like WiFi MAC, this can often be changed in software and may be off when you need it
  • The subscriber's telephone number. This may change if the user requests a new number from the telco, or if the user switches SIMs. It is obtained from TelephonyManager.getLine1Number(). This is only present for Android phone devices with a current SIM installed and a paid service with a telco.
  • The SIM contains its own identifying number (IMSI). This is obtained from theTelephonyManager.getSubscriberId() API. Obviously the SIM may not be present at any specific time, and it changes when the SIM is changed - and users can upgrade/replace their SIM while keeping the same number, so you can't say that this is one-to-one to a specific phone or user.
  • Related to the IMSI is the MSISDN. This functions as the identification of a subscription (your contract for a specific telephone number with your mobile provider) and therefore gives the device its telephone number. The MSISDN may be associated with several SIM cards, and therefore several phones. It comes with all the caveats for reading the SIM above. This may be retrieved withTelephonyManager.getSimSerialNumber(). Thanks Schlangi for the corrections and additions
  • Gingerbread and later has android.os.Build.SERIAL which many manufacturers set (but not all. Bugger).

Other notes

There are some approach to get unique identifier on android phone.

  1. Android ID It is a 64-bit hex string which is generated on the device's first boot. Generally it won't changed unless is factory reset.

    Secure.getString(getContentResolver(), Secure.ANDROID_ID);

The Android ID , considered unreliable because it can sometimes be null. The documentation states that it "can change upon factory reset". This string can also be altered on a rooted phone.

   String m_szAndroidID = Secure.getString(getContentResolver(), Secure.ANDROID_ID);

Returns: 9774d56d682e549c . No special permissions required.

2. The WLAN MAC Address string, is another unique identifier that you can use as a device id. Before you read it, you will need to make sure that your project has the android.permission.ACCESS_WIFI_STATE permission or the WLAN MAC Address will come up as null.

 WifiManager wm = (WifiManager)getSystemService(Context.WIFI_SERVICE);
 String m_szWLANMAC = wm.getConnectionInfo().getMacAddress();
Returns: 00:11:22:33:44:55 (not a real address since this is a custom ROM , as you can see the MAC address can easily be faked).
WLAN doesn't have to be on, to read this value.

3. The BT MAC Address string, available on Android devices with Bluetooth, can be read if your project has the android.permission.BLUETOOTH permission.

    BluetoothAdapter m_BluetoothAdapter = null; // Local Bluetooth adapter
    m_BluetoothAdapter = BluetoothAdapter.getDefaultAdapter();
   String m_szBTMAC = m_BluetoothAdapter.getAddress();

Returns: 43:25:78:50:93:38 . BT doesn't have to be on, to read it. 4. IMEI only for Android devices with Phone use:

 TelephonyManager TelephonyMgr = (TelephonyManager)getSystemService(TELEPHONY_SERVICE);
 String szImei = TelephonyMgr.getDeviceId(); // Requires READ_PHONE_STATE

This requires adding a permission in AndroidManifest.xml, and users will be notified upon installing your software: android.permission.READ_PHONE_STATE. The IMEI is unique for your phone and it looks like this: 359881030314356 (unless you have a pre-production device with an invalid IMEI like 0000000000000). For more info refer this link.

조회 수 :
등록일 :
12:27:44 (*.251.139.148)
엮인글 :
게시글 주소 :
List of Articles
번호 제목 글쓴이 날짜 조회 수
80 Desktop & Mobile VoIP Softphone Apps coding admin 2024-04-09 1781
79 발신번호 숨긴 전화 차단하는 방법 과 발신자 번호를 알 수 있는 방법 admin 2018-11-21 20932
78 특정번호 수신차단 서비스 집전화 유선전화 admin 2018-11-21 16618
77 발신자 표시 제한 부가서비스 가입 확인 이동통신사 고객센터 연락처 SK KT LG admin 2018-11-21 17589
76 새벽마다 울리는 '발신자표시제한' 전화, 범죄입증 안되면 추적도 불가? admin 2018-11-21 18910
75 전화걸때 발신할때 상대방 휴대폰 발신번호표시 제한 방법 (*23#) admin 2018-11-21 19882
74 이번에는 반대로 내 번호를 상대방에게 알리지 않고 통화를 할 수 있는 방법 발신번호 admin 2018-11-21 18028
73 발신번호표시제한 추적 발신자표시제한 방법 070 전화 아이폰 휴대폰 일반전화 * 155 admin 2018-11-21 22023
72 발신번호표시제한 전화가 계속 옵니다. 번호를 추적하거나 신고할 수 있나요? admin 2018-07-04 21612
71 KT올레 착신전환 서비스 안내사항 착신전환통화 서비스 이용방법 admin 2018-06-04 20065
70 아이폰 앱스토어 아이폰에서 결재 방법 admin 2018-04-28 19529
69 구글 플레이와 중국 스마트폰 admin 2018-04-23 20422
68 샤오미 홍미 노트 5 프로 사용방법 플레이 스토어 서비스 및 한글화 admin 2018-04-23 21514
67 샤오미 홍미노트4 구글 플레이스토어 설치 직구 방법 admin 2018-04-23 22017
66 휴대폰 착신전환 서비스 와 착신전환일반 서비스 상세 설명 정리 admin 2018-04-19 19513
65 휴대폰 착신전환일반 안내 이동전화 수신 통화 및 문자를 전송해 주는 서비스 admin 2018-04-19 18850
64 Pc 에서 USB 로 폰 인식 안될때 해결 방법 10가지 윈도우 10 admin 2018-01-12 37607
63 컴퓨터 작업 표시줄 얼음 프리징 먹통 윈도우 10 해결 방법 admin 2018-01-12 22038
62 usb PC 에서 인식 안됨 현상 삼성 스마트폰 통합드라이버 다운로드 설치 주소 링크 admin 2018-01-12 23033
61 스마트폰 을 피씨와 연결해도 인식이 안될때 USB 조치방법 admin 2018-01-12 21028
60 070인터넷 전화 활용하기 010휴대폰 해외 로밍요금 해결방법 SK LG KT admin 2017-12-28 22641
59 SKT 통화내역 조회 전화번호 와 발신 날짜 기록 확인 조회 하는 방법 admin 2017-09-02 25588
58 SKT 착신전화 방법 admin 2017-08-20 23195
57 FLEXJSON admin 2015-04-16 23253
56 삼성전자 무선사업부 개발실에서는 무슨 일을 할까요? admin 2015-03-16 23155
55 [인포그래픽] 삼성전자 휴대전화 통신기술의 진화 admin 2015-03-16 23236
54 통신사 포인트, 몰라서 안 쓴다 해 바뀌면 소멸… 영화관·편의점 등 사용처 다양 admin 2015-03-11 34398
53 ▣ 전화 수신거부 당하면 어떻게 될까? admin 2015-03-09 28381
52 통신3사의 무제한 요금제 뒤에 감추어진 꼼수 통화분수 분석 부가통화 꼼수 file admin 2015-01-04 25938
» android device id imei imsi wifi bluetooth simserial admin 2014-02-14 132579