I have just modified and built Mms.apk and CellBroadcastReciever.apk for any SoftBank Mobile SIMs.
The feature of this Mms.apk is as follows:
1. User-Agent Switcher: Available to select useragent, including "iPhone (3.0)" for Black SIMs, "SoftBank MyrMMS" for Gray and/or Light Blue SIMs.
Useragent customised by user him/herself is also available for any other SIMs.
2. Emoji support for both Unicode 6.0 and SoftBank's original emoji encoding - (with 471 emoticons)
3. Added ability to change message font size.
4. Added the ability to select recipients (phone numbers only, no email addresses) from a checkbox list
Although this Mms.apk is AOSP based, modified part of source code is referred from Cyanogenmod or other sources on GitHub. It can display both English and Japanese language as menu. When the display language is other than these two, only modified part of the menu is displayed in English. The origial part of menu is displayed in your selected language (I am sorry that I am not familier with other laguage than English and Japanese.)
Reception of Cell Broadcast will be also available if you install CellBroadcastReciever.apk
Brief Instructions for installation
Prior to installation, you must install both Oracle Java and Android SDK (and also Sony PC Companion in some case) on your Windows PC in order to use "adb" command.
This procedure is applicable only for 14.1.G.1.534 or older. Use another method for 14.1.G.2.257.
There is Wi-Fi disabled issue with 14.2.A.0.290, described later on this thread.
1. Root your handset (Xperia Z1 C6903, or whatever) by using Kingo Root
Unable to root with 14.1.G.2.257 firmware. Flash 14.1.G.1.534 or older by using FlashTool before trying to root (at 7th Dec. 2013).
2. After rooted, install BusyBox. BusyBox installer is available on Google Play.
3. Download and execute "Remount Reboot Fix". This is necessary in order to prevent reboot after execute "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system" later, stopping SONY RIC.
4. Open console and type "adb shell".
5. Type "su" in order to be SuperUser.
6. Type "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system" in order that /system directry become writable.
7. Type "cd [any directory where both Mms-Android_4.2.2.apk and CellBroadcastReceiver-Android_4.2.2.apk exist]"
(For example: "cd /sdcard")
8. Type "cp Mms-Android_4.2.2.apk /system/app/Mms.apk" and "cp CellBroadcastReceiver-Android_4.2.2.apk /system/app/CellBroadcastReceiver.apk
9. Type "chmod 644 /system/app/Mms.apk" and "chmod 644 /system/app/CellBroadcastReceiver.apk" in order to change file permission.
10. That's all!! It is up to you to unroot your own handset or do else with root permission.
Remark: It is not necessary to delete Conversations.apk under /system/app. Instead Conversations.apk can be deactivated in "Settings" Menu. If Conversations.apk is deleted, it will be unavailable to back up SMS/MMS with Sony's backup tool on Xperia. I recommend that Conversations.apk should be left.
-
APN Settings - Each type of SIMs (contracts) has its own APN
1. Confidential APNs - Not open to the public, closed by SoftBank Mobile
1-1. SIMs for iPhone - Black SIMs: Recommended to use with your own SIM unlocked handset
1-1-1. Black SIM (Normal SIM or MicroSIM for iPhone monthly plan 3G contract - iPhone 4s or earlier - 3G ONLY, User-Agent: iPhone(3.0))
(Default)
Name: SoftBank iPhone (or whatever you like)
APN: smile.world
Proxy: (Not set)
Port : (Not set)
Username: dna1trop
Password: so2t3k3m2a
Server: (Not set)
MMSC: (Not set)
MMS proxy: (Not set)
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: CHAP
APN type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
(MMS)
Name: SoftBank iPhone MMS (or whatever you like)
APN: smile.world
Proxy: (Not set)
Port : (Not set)
Username: dna1trop
Password: so2t3k3m2a
Server: (Not set)
MMSC: http://mms/
MMS proxy: smilemms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: CHAP
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
1-1-2. Black Nano-SIM (for iPhone monthly plan LTE contract, iPhone 5 or later - LTE and 3G, User-Agent: iPhone(3.0))
(Default)
Name: SoftBank LTE iPhone (or whatever you like)
APN: jpspir
Proxy: (Not set)
Port : (Not set)
Username: sirobit
Password: amstkoi
Server: (Not set)
MMSC: (Not set)
MMS proxy: (Not set)
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: PAP
APN type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
(MMS)
Name: SoftBank LTE iPhone MMS (or whatever you like)
APN: jpspir
Proxy: (Not set)
Port : (Not set)
Username: sirobit
Password: amstkoi
Server: (Not set)
MMSC: http://mms/
MMS proxy: smilemms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: PAP
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
1-2. SIMs for Android or other smartphones (windows phone etc.) - Gray and/or Light Bule SIMs
1-2-1. Gray SIM (for android 3G Contract, excluding recent SIM which can use AXGP compatible with TDD-LTE, for monthly plan, Normal Size - SoftBank Smartphone - 3G ONLY, User-Agent: SoftBank MyrMMS) - This type of SIM is not issued for new contract anymore.
(Default Name: SoftBank Android (or whatever you like)
APN: open.softbank.ne.jp
Proxy: (Not set)
Port : (Not set)
Username: opensoftbank
Password: ebMNuX1FIHg9d3DA
Server: (Not set)
MMSC: (Not set)
MMS proxy: (Not set)
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: (Not set)
APN type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
(MMS)
Name: SoftBank Android MMS (or whatever you like)
APN: open.softbank.ne.jp
Proxy: (Not set)
Port : (Not set)
Username: opensoftbank
Password: ebMNuX1FIHg9d3DA
Server: (Not set)
MMSC: http://mms/
MMS proxy: mmsopen.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: (Not set)
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
1-2-2. Gray and/or Light Bule SIM (for android AXGP contract, SoftBank Smartphone - AXGP("SoftBank 4G") and 3G, User-Agent: SoftBank MyrMMS)
(Default)
Name: SoftBank AXGP Android (or whatever you like)
APN: fourgsmartphone
Proxy: (Not set)
Port : (Not set)
Username: (Depending on your own SIM, generated from your own phone number, IMEI and IMSI)
Password: (Depending on your own SIM, generated from ICCID)
Server: (Not set)
MMSC: (Not set)
MMS proxy: (Not set)
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: (Not set)
APN type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
(MMS)
Name: SoftBank AXGP Android MMS (or whatever you like)
APN: fourgsmartphone
Proxy: (Not set)
Port : (Not set)
Username: (Depending on your own SIM, generated from your own phone number, IMEI and IMSI)
Password: (Depending on your own SIM, generated from ICCID)
Server: (Not set)
MMSC: http://mms/
MMS proxy: andmms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: (Not set)
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
1-3. SIMs for fearture phones (including previous Nokia's Symbian handsets) - Silver SIMs
WARNING!!! - NEVER USE this type of SIMs with feature phone contract for smartphones ABSOLUTELY. IT WILL DEFINITELY LEAD TO UNLIMITED MEASURED RATE OF MONTHLY CHARGE (PAYMENT). - JPY1,500,000 (=about USD15,000) or more per a month, in the worst case. The amount enables us to purchase a car such as NISSAN MARCH (MICRA) or second-hand HONDA ACCORD in cash. Can you pay this amount of monthly charige at once?
2. Open APN - the APN SoftBank opens to the public offcially - disclosed by SoftBank Mobile
2-1. "Access Internet Plus" (User-Agent: SoftBank MyrMMS)
Not available for SoftBank 4G AXGP contract (Gray and/or Light Blue SIMs)
Not available for LTE connection, 3G only.
Prohibted to use tethering.
NEVER USE this APN with Silver SIMs with featue phone contract ABSOLUTELY.
(Default)
Name: Access Internet Plus (or whatever you like)
APN: plus.softbank
Proxy: (Not set)
Port : (Not set)
Username: plus
Password: softbank
Server: (Not set)
MMSC: (Not set)
MMS proxy: (Not set)
MMS port: (Not set)
MCC: (Not set)
MNC: (Not set)
Authentication Type: (Not set)
APN type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
3. Confidential MMS APN for feature phones - not open to the public - closed by SoftBank Mobile (User-Agent: Type "SoftBank/2.0/301SH/SHJ001" in Custom User-Agent field)
Name: SoftBank MMS (or whatever you like)
APN: mailwebservice.softbank.ne.jp
Proxy: (Not set)
Port : (Not set)
Username: softbank
Password: qceffknarlurqgbl
Server: (Not set)
MMSC: http://mms/
MMS proxy: sbmmsproxy.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: (Not set)
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
WARNING!!! - Misconfiguration of APN settings may lead to UNLIMITED MEASURED RATE OF MONTHLY CHARGE (PAYMENT), NOT FLAT RATE (or dual flat rate). I am not responsible for any damages due to misconfiguration of settings. Use at your own risk. You must read and understand the following contents CAREFULLY as long as you try to use APNs and MMS in Japan at least. otherwise you have no qualification to do so. Do not disturb and impinge on others' rights at all. Your stupid and selfish behaviour may lead to "countermeasure" by SoftBank in near future. Mind and respect the manner and moral at least, and you must have responsibility. It is duty of users who try to use my Mms.apk. Of course, you are not allowed to leave Japan without payment of the cost due to unlmited measured rate. The person who try to escape from monthly payment is not qualified to use my Mms.apk
DO NOT ASK SoftBank shop staff about APN setting ABSOLUTELY AT ALL. BE CAREFUL!! Unlike overseas mobile carriers, Japanese carriers including
SoftBank Mobile do not disclose any information about APNs. APN settings are "CONFIDENTIAL" in Japan, which is so
strange for foreigners who are used to disclosure of APNs. Therefore Japanese mobile phone system is like the eco-system of "GALAPAGOS ISLANDS" different from the rest of the world in certain meanings.
I do not reccomend that you would use recent Gray and/or Light Bule SIMs for SoftBank's android smartphones which can use AXGP (so called "SoftBank 4G", Advanced eXtended Global Platform, compatible with TDD-LTE) as Username and Password of APN are different on each SIM (contract). you will need SoftBank STREAM 201HW handset (by Huawai) in order to obtain information of Username and Password dependng on your own SIM through LogCat. Configuration of APN setting is elaborating too much.
"SoftBank 4G" (=AXGP) is different from "SoftBank 4G LTE" (=FDD-LTE)
On AXGP (SoftBank 4G) contract APN, Username is generated from your own phone number, IMEI and IMSI, and Password is generated from ICCID.
In this case, DO NOT USE other APNs (APN for iPhone, etc) .If you use any other APNs than SoftBank AXGP android smartphone's, your monthly charge will be unlimted measured rate (NOT FLAT RATE), whose amount enables us to purchase a car such as NISSAN MARCH (MICRA) or second-hand HONDA ACCORD. CAN YOU PAY THIS AMOUNT OF MONTHLY CHARGE AT ONCE? NEVER DO THIS ABSOLUTELY. Instead you should contract SoftBank iPhone in order to change your own SoftBank SIM to black at SoftBank shop. It is impossble to obtain black SIM only, and SoftBank will decline new black SIM's contract, unless you have iPhone which you bought through SoftBank or Apple Store in Japan. iPhone bought outside Japan is unacceptable on SoftBank iPhone Contract.
In all cases, APN you are trying to use must be the one suitable for your type of contract, in order to prevent from UNLIMITED MEASURED RATE (NOT FLAT RATE) OF MONTHLY CHARGE (PAYMENT).
The safest way (the least dangerous way) to use you own SIM-unlocked handset is to use SoftBank's genuine iPhone's contract (black SIMs, black Micro-SIMs or black Nano-SIMs) with SoftBank's SIM-locked iPhone handset and APNs ("smile.world" or "jpspir", depending on your contract (3G or LTE)). If your contract is iPhone 4s or earlier (= 3G only, black Normal or Micro-SIM), you must use "smile.world" APN, and if your contract is iPhone 5 or later ( = LTE, black Nano-SIM), you must use "jpspir" APN. DO NOT USE the other at all, which may lead to unlimited measured rate (not flat rate) of monthly charge (payment).
The number of SoftBank APNs is so many and different on each type of SIM (contract), as SoftBank (and also other Japanese carriers such as NTT docomo and KDDI(au), to certain extent) dislike or even hate SIM-Unlocked handsets basically. Especially the case of SoftBank is most exclusive.
Japanese mobile operators generally consider the existence of SIM unlocked handesets as obstacle against their mobile business, unlike the mobile operators in the rest of the world such as Vodafone, O2(Telefonica), T-Mobile and Orange. For example, NTT docomo wants to pre-install unnecessary docomo's original bloatware in /system/app directory on its SIM-locked handsets, in order to let the customers use docomo's charged services. Although NTT docomo even tried to force Apple to pre-install its own original bloatwares into iPhone during the negotiation before introduction, Apple, of course, declined NTT docomo's proposal, because Apple hated to unstabilise its iOS due to bloatware.
It is, of course, impossible to pre-install, into /system/app directory on SIM-unlocked handsets, mobile operator's original bloatware in order to let customers to use operator's original charged services. Therefore Japanese mobile operators want to alienate SIM-unlocked handset from their contract, thus SoftBank (and also NTT docomo and KDDI) do not want to accept SIM-Unlocked handsets. This is why many APNs and types of SIMs exist on SoftBank Mobile. you must use your own SIM free handset on SoftBank at your own risk.
SoftBank's APNs are harmless and safe as long as you use SoftBank's SIM-locked handsets, like the eco-system of Galapagos islands. In the case of SoftBank's SIM-locked handsets, APN information is hidden and handset is locked to the APN suitable for the contract. We cannot see, modify or delete the content of APN information on the SIM-locked handset at all. Once you try to use with your own SIM-unlocked handset, they will be harmful and dangerous.
Selection or configurtion of MMS useragent suitable for your contract (SIM) is vital and indispensable to use MMS on SoftBank, as SoftBank MMS server try to exclude any other handset including SIM-unlocked than SIM-locked ones which SoftBank sells, in order that SoftBank binds users to enforced 2-years contract with 2-years monthly payment loan of SIM-locked SoftBank handset. Exclusion of SIM-unlocked handsets is made with the judgement by MMS useragent in accordance with "White List" on SoftBank MMS server, where the mms useragent list of SoftBank SIM-locked handsets is described.
The list of MMS User-Agent which SoftBank MMS Server accept
User-Agents which SoftBank MMS server accept
(Smartphones)
Apple iPhone - "iPhoneOS/3.0 (7A341)"
Google Nexus 5 - "Nexus5"
SoftBank Mail client: SoftBank MyrMMS - "SoftBank/1.0/Smart/MyrMMS" - (*1)]
(Feature phones)
SoftBank X01T by Toshiba - "SoftBank/1.0/X01T/TJ001"
SoftBank 301SH by Sharp - "SoftBank/2.0/301SH/SHJ001"
SoftBank 202SH by Sharp - "SoftBank/2.0/202SH/SHJ001"
SoftBank 301P by Panasonic - "SoftBank/1.0/301P/PJP10"
SoftBank 103P by Panasonic - "SoftBank/1.0/103P/PJP10"
SoftBank 705NK (Nokia N73) - "SoftBank/1.0/705NK/NKJ001 Series60/3.0 NokiaN73/3.0650 Profile/MIDP-2.0 Configuration/CLDC-1.1" - (*2)
SoftBank X02NK (Nokia N95) - "SoftBank/1.0/X02NK/NKJ001 Series60/3.1 NokiaN95/20.0.273 Profile/MIDP-2.0 Configuration/CLDC-1.1" - (*2)
and other SIM locked handsets SoftBank Mobile has sold
User-Agents which SoftBank MMS server refuses
Sony Xperia (including C6903, C6833, LT26i and others)
Samsung Galaxy
HTC (including One, Desire, Butterfly and others)
NOKIA (both symibian and windows phone) - (*2)
MOTOROLA
and other SIM unlocked handsets
(*1) SoftBank Mail client is useless with iPhone's black SIM, Micro-SIM and nano-SIM, as its MMS user-agent is refused. In addition, user interface (displayed menu language) is Japanese only. It is only acceptable and available to use SoftBank Mail client when using with Gray and/or Light Bule SIM This is the consequence of "internal operator SIM-lock"
(*2) User-Agent of Nokia handset that SoftBank has sold is different from the one that Nokia has sold directly.
Example: SoftBank X02NK and Nokia N95
SoftBank X02NK (Nokia N95) handset sold by SoftBank - SIM Locked - accepted by SoftBank MMS Server
"SoftBank/1.0/X02NK/NKJ001 Series60/3.1 NokiaN95/20.0.273 Profile/MIDP-2.0 Configuration/CLDC-1.1"
Nokia N95 handset sold by Nokia directly - SIM Unlocked - refused by SoftBank MMS server
"NokiaN95/11.0.026; Series60/3.1 Profile/MIDP-2.0 Configuration/CLDC-1.1"
If you cancel contract during 2 years, you will have to pay expensive fine (Not only fine for cancellaton but also outstanding debt of SIM-locked handset, about 10,000 yen to 70,000 yen depending on contract and SIM-locked handset, 1 US dollar = about 100 JP yen at 9th of Dec., 2013. Here is a currency converter.). This way of sales is common in Japan. Not only SoftBank but also NTT docomo and KDDI do the same.
For Reference : This is good information about configuration of APN (the case of Google Nexus 5).
http://www.japandroid.info/2013/11/using-softbank-iphone-5-lte-sim-with.html
If you have any questions about SoftBank APNs, do not hesitate and feel free to ask me before you
have "tragedy".
Read "Understanding the Japanese mobile background to use your ownSIM-Free handset" for more detail.
I added MMS useragent of Google Nexus 5 to Android 4.2 and 4.3 version, as it was added to SoftBank's Whitelist.
Nexus 5 (SIM-Unlocked) is dealt with by Google and EMobile (eAccess) in Japan. To use Nexus 5 (SIM-Unlocked) in Japan, contract is made with EMobile, which becomes MVNO on SoftBank Mobile in this case.
CONCLUSION (This is why Japanese mobile environment is like the eco-system of Galapagos Islands.)
1. SIM-unlocked handsets are not common in Japan, unlike the rest of the world. 99% of handsets is SIM-locked in Japan.
2. Japanese mobile operators prefer to provide not what customers really want, but what operators want, like "brainwashers". - operators own original bloatware in /system/app directory, SIM-locked handsets with enforced 2 years monthly payment loan. Cancellation is not allowed during 2 years period.
3. Existence of confidential APNs and "internal operator SIM-lock" (especially in the case of SoftBank) with so many SIMs and APNs depending on the type of contract - It may lead to the danger of unlimited measured rate monthly charge due to APN misconfiguration, as it is unofficial way on SoftBank Mobile contract.
4. Proper configuration of MMS useragent is vital and indispensable to use MMS with your own SIM unlocked-handsets, due to "internal operator SIM-lock" in the case of SoftBank.
EXTERNAL DOWNLOAD LINKS
For Android 4.4 Kitkat (API level 19)
Mms-Android_4.4.2.apk
CellBroadcastReceiver-Android_4.4.2.apk
For Android 4.3 JellyBean (API level 18)
Mms-Android_4.3.1.apk
CellBroadcastReceiver-Android_4.3.1.apk
For Android 4.2 JellyBean (API level 17)
Mms-Android_4.2.2.apk
CellBroadcastReceiver-Android_4.2.2.apk
Source Code for Android 4.4 Kitkat and 4.3 JellyBean is available here
Source Code for Andoir 4.2 is here.
Mms_4.2.2_Source_Code_Rev13.zip
Revision_History_4.2.2.txt
For Android 4.0.4 (ICS) and 4.1.2 (JB), check this out.
Credit; See this page
Swimmer.jp,
Thanks for your work!
Most of the features you listed here should be included in CM's official MMS app, especially the UA chooser... Where can we see your code (you're on github)?
Zgembo said:
Swimmer.jp,
Thanks for your work!
Most of the features you listed here should be included in CM's official MMS app, especially the UA chooser... Where can we see your code (you're on github)?
Click to expand...
Click to collapse
Zgembo
Thanks for your comment.
Source code is, of course, available on GitHub. Source code itself is not mine, but others and open-source.
Therefore copyright belongs to them.
I just preferred to arrange AOSP-based Mms.apk for SoftBank black SIM on my Xperia Z1, in order to save
monthly charge within 4000 or 5000 yen. Using my iPhone 4 costs expensive monthly charge.
Nowadays my iPhone 4 becomes "iPod Touch" for car-audio use, instead of "CD multi-changer", which used to be luxuary in Japan previously.
Custom user-agent option
(ICS or later)
github.com/rdgate/packages_apps_Mms/commit/0e2d2adce334cd77d07f57ffdfb9dc92b42df536
(GB or earlier)
github.com/JakeJP/android_packages_apps_Mms_SBM/commit/e2fca403edcead20330dc5ea38c7bce4b91763a5
Emoji patch from CM9 for the MMS app
github.com/rdgate/packages_apps_Mms/commit/9d6a362d3dd179682cb93746b8cb79f208525747
review.cyanogenmod.org/#/c/21231/2
@Swimmer.jp, please check your PM
Zgembo said:
@Swimmer.jp, please check your PM
Click to expand...
Click to collapse
Zgembo,
Excuse me, what does my "PM" abbreviation means?
Swimmer.jp said:
Zgembo,
Excuse me, what does my "PM" abbreviation means?
Click to expand...
Click to collapse
Now I've got the meaning of PM. It is abbreviation for "Private Message". I will read your message from now on.
Thanks indeed.
I have S3 with Android 4.3. Unfortunatelly this SecMMS.apk crashes on my phone. The app GUI appears for a brief moment, than goes blac, reapperas, than desktop appears again and there is a message that Unfortunately messaging has stopped. Do you think that this may be due to the fact that I have android 4.3 not 4.3.1?
lewhoo said:
I have S3 with Android 4.3. Unfortunatelly this SecMMS.apk crashes on my phone. The app GUI appears for a brief moment, than goes blac, reapperas, than desktop appears again and there is a message that Unfortunately messaging has stopped. Do you think that this may be due to the fact that I have android 4.3 not 4.3.1?
Click to expand...
Click to collapse
I do not think that it is due whether you have Android 4.3 or 4.3.1, as both 4.3 and 4.3.1 belong to the same API level 18. Check this out for more details.
I do not know the cause of error with SAMSUNG Galaxy S3, as I do not have Samsung handset at all, and I am not interested in any Samsung products. I am sorry that I cannot help you this time, but thank you for your information anyway.
My series of Mms.apk work fine on Sony Xperia Z1 (C6903, for Android 4.2.2 and 4.3) and Xperia S (LT26i, for Android 4.0.4 and 4.1.2), except Android 4.3 Wi-Fi disabled case.
Swimmer.jp said:
I do not think that it is due whether you have Android 4.3 or 4.3.1, as both 4.3 and 4.3.1 belong to the same API level 18. Check ... out for more details.
I do not know the cause of error with SAMSUNG Galaxy S3, as I do not have Samsung handset at all, and I am not interested in any Samsung products. I am sorry that I cannot help you this time, but thank you for your information anyway.
My series of Mms.apk work fine on Sony Xperia Z1 (C6903, for Android 4.2.2 and 4.3) and Xperia S (LT26i, for Android 4.0.4 and 4.1.2), except Android 4.3 Wi-Fi disabled case.
Click to expand...
Click to collapse
Thank you for your answer. Well, so I need to find another apk, this time for S3, or decompile, change the user agent and recompile, which I wanted to avoid. Somehow I had more luck with previous Androids.
lewhoo said:
Thank you for your answer. Well, so I need to find another apk, this time for S3, or decompile, change the user agent and recompile, which I wanted to avoid. Somehow I had more luck with previous Androids.
Click to expand...
Click to collapse
If you have time, you can build Mms.apk by yourself. Procedure is as follows. Although this is time-consuming and elaborating work, it is worth trying!!
1. Download and install Ubuntu 12.04.4 LTS (64-bit) in Oracle VirtualBox on Windows PC (Windows 7, 8 or 8.1 (64-bit)).
2. Log on to Ubuntu on VirtualBox
3. Initialising the Build Environment
4. Downloading the Source
5. Building the System
Original (unmodified) AOSP Mms.apk and Mms.odex are built
in "/home/(USERNAME)/WORKING_DIRECTORY/out/target/product/generic/system/app/"at this moment.
(USERNAME) is replaced by your login username on Ubuntu.
6. Modify the MMS source code
in " /home/(USERNAME)/WORKING_DIRECTORY/packages/apps/Mms/" on Ubuntu
See Revision_History_4.3.1.txt or Revision_History_4.2.2.txt for modification.
7. After modification, execute "mmm packages/apps/Mms" in "/home/(USERNAME)/WORKING_DIRECTORY/" in terminal on Ubuntu.
8. Modified Mms.apk and Mms.odex are built
in "/home/(USERNAME)/WORKING_DIRECTORY/out/target/product/generic/system/app/", replacing original (unmodified) AOSP Mms.apk.
9. Copy or transfer both Mms.apk and Mms.odex to Windows environment (outside Oracle VirtualBox).
10. Archive (Pack or ZIP) "/home/(USERNAME)/WORKING_DIRECTORY/out/target/product/generic/system/framework" directory to "framework.zip"
11. Copy or transfer "framework.zip to Windows environment (outside Oracle VirtualBox).
12. Download and install "xda AutoDeodexTOOL" on Windows.
13. Unzip framework.zip on Windows and place unzipped the JARs and corresponding ODEX files in the directory "_framework".
14. Place both Mms.apk and Mms.odex in the directory "_app".
15. Run AutoDEOToolMain.bat and choose "1 DEODEX ALL (Stock Rom)"
16. De-odexed Mms.apk is generated in the directory "deodexed_APK"
17. Copy the Mms.apk in the directory "deodexed_APK" to "/system/app" in your own handset as system application.
File permission of Mms.apk must be 644 (rw-r--r--). Chenge permission by "chmod 644 Mms.apk" in adb console.
(End of procedure)
Swimmer.jp said:
If you have time, you can build Mms.apk by yourself. Procedure is as follows. Although this is time-consuming and elaborating work, it is worth trying!!
(End of procedure)[/HIDE]
Click to expand...
Click to collapse
Well, I sort of stopped when the build system on my Fedora still claimed that I am using Open Java SDK when I already uninstalled it and installed the Oracle one.
Fortunately I found an app: Go SMS Pro, which allows for setting user agent. It is not ideal, but... works!
lewhoo said:
Well, I sort of stopped when the build system on my Fedora still claimed that I am using Open Java SDK when I already uninstalled it and installed the Oracle one.
Fortunately I found an app: Go SMS Pro, which allows for setting user agent. It is not ideal, but... works!
Click to expand...
Click to collapse
Go SMS Pro can also be an option. It seems no problem as long as you use in English. If you use in Japanese, you will find the expression of Japanese is so strange on the menu and not precise like automatic-translation.
Ubuntu 12.04 LTS (64-bit) rather than Fedora is recommended, and it is also recommended to use Oracle JDK 6 instead of Open JDK, by AOSP, in order to build Android including Mms.apk.
not mirroring
hello there
I have been trying to install the Mms.apk for my HTC One m7 4.4.2 kitkat for softbank black sim
I tried any type of installations, but although it seems to succeed, the Mms.apk doesn't show up in my app drawer
when I go look inside system/app, Mms.apk does exist, (and CellBroadcastReceiver.apk too btw), with the right permission and so on
I don't know what to do
do you have any idea of what is going on?
is it the original Mms.apk which is not tailored for HTC One?
I guess that is not the point???
also, I thought that Mms.apk and CellBroadcastReceiver.apk on kitkat were supposed to be installed on system/priv-app
looking forward to hearing from you
lostshun said:
hello there
I have been trying to install the Mms.apk for my HTC One m7 4.4.2 kitkat for softbank black sim
I tried any type of installations, but although it seems to succeed, the Mms.apk doesn't show up in my app drawer
when I go look inside system/app, Mms.apk does exist, (and CellBroadcastReceiver.apk too btw), with the right permission and so on
I don't know what to do
do you have any idea of what is going on?
is it the original Mms.apk which is not tailored for HTC One?
I guess that is not the point???
also, I thought that Mms.apk and CellBroadcastReceiver.apk on kitkat were supposed to be installed on system/priv-app
looking forward to hearing from you
Click to expand...
Click to collapse
Thanks for your report, and I am sorry to be late for replying you. I am just checking what you have experienced, but I cannot answer you immediately without further invesitigation. Please be patient until I confirmed the "phenomenon" and answer you.
Swimmer.jp said:
Thanks for your report, and I am sorry to be late for replying you. I am just checking what you have experienced, but I cannot answer you immediately without further invesitigation. Please be patient until I confirmed the "phenomenon" and answer you.
Click to expand...
Click to collapse
Yay
so, some news
I could install!! I made it!
I tried first by downloading through my device, and choose install
it didn't work
then through TWRP, and nothing
and then finally push it through Terminal, and nothing either
but strangely, when I received a new sms, hangout took over, and then, shifted to MMS.apk, which became visible
so strange
so for now, emoji is working
but sending pictures is not available…..
any ideas? I installed the UserAgent package, but no changes
other questions :
I can't listen to "rusu-den" (voice message)
sometimes, I do have the antenna coverage, but people can't reach me on phone.. why?
no tethering / wifi-hotspot ???
did it happened to you too?
lostshun said:
Yay
so, some news
I could install!! I made it!
I tried first by downloading through my device, and choose install
it didn't work
then through TWRP, and nothing
and then finally push it through Terminal, and nothing either
but strangely, when I received a new sms, hangout took over, and then, shifted to MMS.apk, which became visible
so strange
but
so for now, emoji is working
but sending pictures is not available…..
any ideas? I installed the UserAgent package, but no changes
other questions :
I can't listen to "rusu-den" (voice message)
sometimes, I do have the antenna coverage, but people can't reach me on phone.. why?
no tethering / wifi-hotspot ???
did it happened to you too?
Click to expand...
Click to collapse
Today I confirmed my Mms.apk has no problem on Android 4.4 KitKat, after I updated my Xperia Z1 C6903 to 14.3.A.0.681 Generic Australia firmware. What you have experienced can occationally happen not only to your HTC One but also to my Sony Xperia Z1 C6903. I don't know either why it happneds. What I came to know at least is that Mms.apk can be displayed after reinstalling or reflashing firmware.
You will know the differece between successful installation of Mms.apk and failed case if you see the Mms.apk icon through "ES File Explorer" file manager. Displayed Mms.apk icons are different.
By the way, I need your help. I am trying to disable mobile data except MMS. Previously (until Android 4.2 - 14.1.G.2.257 or earlier), I was able to send/recieve MMS without mobile data checkbox (toggle switch) on by using following settings.
(Default)
Name: SoftBank iPhone (or whatever you like)
APN: smile.world
Proxy: (Not set)
Port : (Not set)
Username: dna1trop
Password: so2t3k3m2a
Server: (Not set)
MMSC: (Not set)
MMS proxy: (Not set)
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: CHAP
APN type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
(MMS)
Name: SoftBank iPhone MMS (or whatever you like)
APN: smile.world
Proxy: (Not set)
Port : (Not set)
Username: dna1trop
Password: so2t3k3m2a
Server: (Not set)
MMSC: http://mms/
MMS proxy: smilemms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: CHAP
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
But it came to be unavailable to send/recieve MMS without mobile data checkbox (toggle switch) on after Android 4.3 - 14.2.A.0.290 or later on my Xperia Z1.
Alternatively I tried APN settings like this on O2 UK (Telefonica UK) website
Create a broken APN
Name: O2 Dummy APN
APN: dummy
Proxy: Not Set
Port: Not Set
Username: dummy
Password: dummy
Server: not set
MCC: 999
MNC: 999
Authentication: PAP
APN Type: default,supl,internet
APN Protocol: IPv4
MMS (Correct working settings)
Name: O2 UK MMS
APN: wap.o2.co.uk or payandgo.o2.co.uk
Proxy: Not set
Port: Not Set
Username: o2wap or payandgo
Password: password
Server: Not set
MMSC: http://mmsc.mms.o2.co.uk:8002
MMS Proxy: 82.132.254.1
MMS port: 8080
MCC: 234
MNC: 10
Authentication: PAP
APN type: default,supl,mms
APN protocol: ipv4
I configured APN settings for SoftBank Mobile in accordance with the settings for O2 UK as follows.
Create a broken APN
Name: SoftBank Dummy APN
APN: dummy
Proxy: Not Set
Port: Not Set
Username: dummy
Password: dummy
Server: not set
MCC: 999
MNC: 999
Authentication: PAP
APN Type: default,supl,internet
APN Protocol: IPv4
MMS (Correct working settings)
Name: SoftBank iPhone MMS (or whatever you like)
APN: smile.world
Proxy: (Not set)
Port : (Not set)
Username: dna1trop
Password: so2t3k3m2a
Server: (Not set)
MMSC: http://mms/
MMS proxy: smilemms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: CHAP
APN type: default,supl,mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
In this case, Not only MMS but also other mobile data traffic occured after mobile data check box on unlike the case of O2 UK, thus the APN settings are useless.
I have also tried another settings like this:
Create a broken APN
Name: SoftBank Dummy APN
APN: dummy
Proxy: Not Set
Port: Not Set
Username: dummy
Password: dummy
Server: not set
MCC: 999
MNC: 999
Authentication: PAP
APN Type: default,supl,internet
APN Protocol: IPv4
MMS (Correct working settings)
Name: SoftBank iPhone MMS (or whatever you like)
APN: smile.world
Proxy: (Not set)
Port : (Not set)
Username: dna1trop
Password: so2t3k3m2a
Server: (Not set)
MMSC: http://mms/
MMS proxy: smilemms.softbank.ne.jp
MMS port: 8080
MCC: 440
MNC: 20
Authentication Type: CHAP
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
In this case, it was able to stop other mobile data traffic than MMS, but I cannot use mobile data except MMS when needed.
There is, of course, the reasion why I prefer to use MMS without other mobile data traffic. I strongly want to save my monthly charge on SoftBank with the lower side (1029 JPY) of dual flat rate, not higher side (4410 JPY). If I use single flat rate, this may be useless.
(1 USD = about 100 JPY, 1 EURO= about 120 JPY)
Another reason is that I want to save battery consumption in my Xperia Z1 handset by cutting background mobile data traffic except MMS.
Currently I have no choice but to come back to Android 4.2, in order to send/recievd MMS without mobile data checkbox on.
Do you have any good ideas or solutions?
I am sorry that I forgot to check whether attachment photo or image can be sent/recieved properly or not while I use Android 4.4 Kitkat (Xperia Z1 C6903 4.3.A.0.681 Firmware) on my handset. As I flashed Android 4.2 (14.1.G.2.257) back again, I have no means to check what you say now. I need to know APN settings or other alternative solutions which can make mobile data disabled except MMS, in order to install Kitkat (14.3.A.0.681) again. In other words, I do not want to pay 4410 JPY just for waste of back ground mobile data traffic irrevalant to MMS (and also other mobile data traffic which is valuable for me), and I want to pay just 1029 JPY, the lower side of dual flat rate, unless I am under the special situation to use mobile data traffic.
I am also sorry that I am not familier with "Rusu-Den (留守電) - abbreviation for Rusuban-Denwa (留守番電話)" (voice message), as I do not use it at all.
hum,
I think I would use only one APN setting, and in APN Type, just put MMS
then only MMS will be allowed to bypass the APN
Or,
there seem to be an app called シュパッと, which controls how your device should react which APN to use, a kind of like FIREWALL
(the app is available in the playstore)
give them a try
so, back to 4.2, you still can use your MMS.apk to send pictures, and plus tether wifi hotspot if needed? in the worst case, I can downgrade, coz I really do need these two options for my job, but I don't wanna do it if I can't...
lostshun said:
hum,
I think I would use only one APN setting, and in APN Type, just put MMS
then only MMS will be allowed to bypass the APN
Or,
there seem to be an app called シュパッと, which controls how your device should react which APN to use, a kind of like FIREWALL
(the app is available in the playstore)
give them a try
so, back to 4.2, you still can use your MMS.apk to send pictures, and plus tether wifi hotspot if needed? in the worst case, I can downgrade, coz I really do need these two options for my job, but I don't wanna do it if I can't...
Click to expand...
Click to collapse
lostshun
Thank you for your advice. I have tried "シュパッと" (Syupatto) and any other firewall such as "No Root Firewall". Thiese are quite effective although some packats are still leaked.
Eventually I was abile to use MMS without mobile data enabled after my handset was flashed with Sony Update Service.
But I have another problem now My Sony Xperia Z1 C6903 handset came to have malfunction on LCD touchscreeen panel. To make the matters worse, I need to use FedEX in order to ship my handset to Hong Kong, and to be repaired, as C6903 itself is not sold in Japan and SO-01f (NTT Docomo, sim locked) and SOL23 (au, KDDI, sim locked) are sold instead. FedEX staff will pick up my phone tomorrow.
For me, SIM unlocked C6903 is definitely much better than SO-01f or SOL23 full of rubbish bloatware. Especially NTT docomo version SO-01F is worst and is almost crap.
Thus I cannot check or examine my Mms.apk on my handset for a while until it comes back from Hong Kong. It will take 2 to 6 weeks.
I installed both apps after forever trying to get it working (im new to this so I suck at it) BUT i cant seem to get them working.
I have been using my galaxy note 3 for some time now on softbank for calls texts and data, But I haven't been able to receive picture messages or mass/group text messages. It was my hope that downloading these apps would allow me the use of these MMS features but when I try to send or receive a MMS the messaging app fails. Im not sure if there is something else I am doing wrong that Im just missing. Can anyone help?
Laboratoryrat said:
I installed both apps after forever trying to get it working (im new to this so I suck at it) BUT i cant seem to get them working.
I have been using my galaxy note 3 for some time now on softbank for calls texts and data, But I haven't been able to receive picture messages or mass/group text messages. It was my hope that downloading these apps would allow me the use of these MMS features but when I try to send or receive a MMS the messaging app fails. Im not sure if there is something else I am doing wrong that Im just missing. Can anyone help?
Click to expand...
Click to collapse
well, installing the new ROM for my phone (MaximusHD ones) kinda sorted this out
I didn't do anything, but at some point, it just went well..
and then, strangely enough, the one that seemed working over the time, MMS.apk stopped working for me, and HangOut seems to be the one that made it work
try to get the modified ROM for your phone first
then get the modified MMS.apk for your rooted phone, with the right version
get RootBrowser.apk, then go to the app folder, find the original messaging app and add in the original messaging app with .bak at the end
the MMS.apk will be the then the working app for messages
and don't forget to set the right APN spots for your phone and your career
aw, well, and then my USB internet sharing stopped when the MMS started to work
maybe having both of them is not possible..
good luck
Related
I have made another modded Version from JF 1.42 RC33 Lite Edition
This ROM dont have any ringtones, alarms or notifications so get the Stock Tones Pack and Unzip it into SDCard so you can change it after Installation.
The Image have Following Feature.
Google Activation Process / Signup Process can be bypassed (ADP1.1 Style)
Activation also dont require SIM Card (ADP 1.1 Style)
Date Settings Defaulted to DD-MMM-YYYY
All Indian Carriers GPRS / EDGE Settings Includes
As Data is major Problem in India Activating Android G1 always require a Borrowed SIM which have Data Plan. so Wipping Android Setting Become Headache in this version you can also Activate and Link your Google or Google Apps A/c by clicking to any Google Apps. giving user name and password over GPRS or WiFi also.
To link your Google A/c Just make Wifi or GPRS Ready and then click to Gmail Icon and Signing by User Name Password then go to Setting / Data Syncronysation and Press Meny and Sync the Desired options u selelcted.
APN Added
Canada Fido MMS
Canada Fido Web
Canada Rogers MMS
Canada Rogers Web
EU-Belgium Mobistar MMS
EU-Belgium Mobistar Web
EU-Belgium Proximus MMS
EU-Belgium Proximus Web
EU-Norway Netcom MMS
EU-Norway Netcom Web
EU-Norway Telenor MMS
EU-Norway Telenor Web
EU-Norway Telenor03 MMS
EU-Norway Ventelo MMS
EU-Romania Orange
EU-Sweden 3 Web
EU-UK O2 PAYG
EU-UK Orange MMS
EU-UK Orange Web
India - Airtel
India - BSNL
India - Idea
India - Reliance
India - Vodafone
Mexico Telcel Web
US ATnT
as per Maharashtra, India all other state people have to search for Respective Setting in APN and change MNC (Mobile Network Code) by seeing Network information. Generally IMSI are like 404xx1234567890 Here First 3 Character is MCC and Second 2 are MNC and Last Ten Digit is true IMSI.
Geeks / Hackers Please share Information that how can i make Default time zone, Default Ring Tones, Volumes etc using init.sh or some other Logic
We can make a Kitchen Software to to do all this Stuff Automatically.
The File is at
http://64bit.in/download/HP-JF142-33L.zip - APN and Activation bypass for JF1.43 RC33 Lite (English)
http://64bit.in/download/HP-JFv1.43_RC9.zip - APN and Activation bypass for JF1.43 RC9 Lite (English and German)
http://64bit.in/download/HP-Lucid_JFv1.43_RC9.zip - APN and Activation bypass for JF1.43 RC9 Lite (English and German) (With Lucid SDCard EXT Partition Hacks)
Mods Done in build.prop
ro.com.android.dateformat=dd-MMM-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=12
ro.config.notification_sound=TaDa.ogg
ro.url.legal=http://www.google.com/intl/%s/mobile/android/g1-legal.html
ro.config.ringtone=Glow.mp3
persist.sys.timezone=Asia/Kolkata
ro.config.sync=yes
ro.setupwizard.mode=OPTIONAL
keyguard.no_require_sim=true
Some Information
GPRS / Edge Class 8 = 3 Slot Download 2 Slot Upload
GPRS / Edge Class 10 = 4 Slot Download 1 Slot Upload and also 3/2
GPRS / Edge Class 12 = 4 Slot Download 1 Slot Upload and any Combination upto 1 Download and 4 Slot Upload
hey thanks alot ............. i live in india and am really proud to be owner of g1 except for its bad battrey life............................ whr do u live in india..... mumbai???
I live in Nashik, Maharashtra
so i did the update,
take out my sim card, and guess what.....
it WORKS 100% no bug it umm rely cum
If you have a Phone which is already Activate then any ROM will work fine without SIM or GPRS / EDGE / Data but if you Wiped the Phone in Normal ROm it will not work without SIM and also Require Activation by Signing into Google A/c
This ROM can be used to over such thing and directly go to Android without Worrying
If Any buddy Realy want to Add his APN Setting into ROM
Please Share your Operators Setting
Name of Operator - Country - MCC - MNC - APN is least thing which is required
hetaldp said:
If you have a Phone which is already Activate then any ROM will work fine without SIM or GPRS / EDGE / Data but if you Wiped the Phone in Normal ROm it will not work without SIM and also Require Activation by Signing into Google A/c
This ROM can be used to over such thing and directly go to Android without Worrying
Click to expand...
Click to collapse
oooooooooOOOOoooo ic, is still cool...
I want APn Settings from the Following Network so i can buld AON-Conf.xml so all future version of JF May contains it
AT&T
Rogers
British and Europian GSM Networks.
hetaldp said:
Google Activation Process / Signup Process can be bypassed (ADP1.1 Style)
Activation also dont require SIM Card (ADP 1.1 Style)
QUOTE]
So how would we apply these settings to our own update? I don't need the date or indian settings but it would be nice to set up my wifi & then start setting up my phone?
Click to expand...
Click to collapse
You just have to Rename the attached ZIP as
update.zip
and put it in sdcard root directory and go to Recovery mode and flash it
You require rooted phone to do that.
hetaldp said:
You just have to Rename the attached ZIP as
update.zip
and put it in sdcard root directory and go to Recovery mode and flash it
You require rooted phone to do that.
Click to expand...
Click to collapse
I should have been more clear... I would like to know how you made that change? I wanna make the changes myself to learn
i live in the US so i dont have a need for this but it looks really cool!
I updated my phone. Thanks for that but i can't find any of the indian APN. I use idea here in Amritsar, Punjab but i have no luck. Can you post APN's for amsterdam, London, Canada, Switzerland, Australia, Italy and some other european countries because i have to go there every year for my business. If not european please add For Punjab Idea or Spice whatever they call it. Really like the skip activation method and really appreciate that. Now don't need to root again after a wipe.
Sounds great, I live in Romania and my orange credit card is empty so its great to flash without activating it later again.
now two questions.
can you also deactivate that myfav sends automatic emails to t-mobile?
Thats nerving also here in romania.
and for settings apn. if you like and make it also romanian confirm
just add APN:
Name: Orange
APN: internet
thats it.. quiet easy
Chris
Here is the APN settings for some European Network Providers
Where blank = Not Applicable
Type of settings: Web/MMS
Country: United Kingdom
Provider: O2 (Pay as you go)
Name: O2 PAYG
APN: payandgo.o2.co.uk
Proxy:
Port:
Username: payandgo
Password: password
Server:
MMSC: http://mmsc.mms.o2.co.uk
MMS Proxy: 193.113.200.195
MMS Port: 8080
MCC: 234
MNC: 10
Type:
Type of settings: MMS*
Country: Norway
Provider: Netcom
Name: Netcom MMS
APN: mms.netcom.no
Proxy:
Port:
Username:
Password:
Server:
MMSC: mms
MMS Proxy: 212.169.66.4
MMS Port: 8080
MCC: 242
MNC: 02
Type:
Type of settings: Web*
Country: Norway
Provider: Netcom
Name: Netcom Web
APN: internet.netcom.no
Proxy:
Port:
Username:
Password:
Server:
MMSC:
MMS Proxy:
MMS Port:
MCC: 242
MNC: 02
Type:
Type of settings: MMS*
Country: Norway
Provider: Telenor
Name: Telenor MMS
APN: telenor
Proxy:
Port:
Username: std
Password: 1234
Server:
MMSC: mmsc
MMS Proxy: 10.010.010.011
MMS Port: 9201
MCC: 242
MNC: 01
Type:
Type of settings: Web*
Country: Norway
Provider: Telenor
Name: Telenor Web
APN: telenor
Proxy: 10.010.010.010
Port: 9021
Username: dj
Password: dj
Server:
MMSC:
MMS Proxy:
MMS Port:
MCC: 242
MNC: 01
Type:
Type of settings: MMS*
Country: Norway
Provider: Ventelo
Name: Ventelo MMS
APN: mms.ventelo.no
Proxy:
Port:
Username: ventelo
Password: 1111
Server:
MMSC: mmsc
MMS Proxy: 010.010.010.011
MMS Port: 8080
MCC: 242
MNC: 10
Type:
Type of settings: MMS*
Country: Norway
Provider: Telenor
Name: Tele2 MMS
APN: mms.tele2.no
Proxy:
Port:
Username: wap
Password: wap
Server:
MMSC: mmsc.tele2.no
MMS Proxy: 192.12.40.14
MMS Port: 8080
MCC: 242
MNC: 03
Type:
Please note that in order to get settings marked by an asterisk (*) in the "Type of settings" field to work, you need to disable the other APN setting for that provider. Example: Telenor have two APN settings, one for MMS and one for Web. Due to restrictions in Android, only one setting can be used simultaneously, so if you want to use Web you need to edit the APN: field so that that pair of settings become useless. Ex. APN: "telenoredited" will not work and hence make the MMS settings work.
You can try to edit some of these settings so that you have all settings in one APN, but I have not tried this and do not know if it will work, but in theory it should, if the two different settings have the same APN fields in common.
Also note that I have only verified the O2 PAYG settings, as this I currently live in the UK. I will however verify the Telenor and perhaps the Netcom settings during Eastern in the beginning of April. These settings have however been reported working by other users of the internet.
Hope these settings will help
You can use 2 Different Setting in Android for Web as well for MMS, Just Create 2 Different APN Settings with Same MCC and MNC.
Just keep following
For APN of Web
type = default
and for APN for MMS
type=mms
Proxy Connection really dont work good for Android and iPhone as sony many Google Application may not work
So Please give me APN Setting for Telenor which dont use Proxy Address
hey ....... this firmware is really good .....the best thing i liked is skipping the reg process and that too in rc33. firmware i can apply themes that are cool ........ i could no tdo that earlier coz i had adp1.1 and there were no good themes ........ i plan to buy bulk of phones from US and sell it here in india at about 450-500$ with root and this firmware............ ppl did no tbuy it earlier coz of the reg process for which they had to buy data plans
@hetaldp
Can you answer this Q: In side your build or ADP builds where are the files that allow you to skip activation and the sign in?
manup456 said:
@hetaldp
Can you answer this Q: In side your build or ADP builds where are the files that allow you to skip activation and the sign in?
Click to expand...
Click to collapse
Yes! Thats what I was asking the first time! I wanna know how to change it manually
I've been lurking around the forums for weeks now, and much as I hate to be the new n00b on the block, I'm seriously at my wits end with this phone.
I have root access, the stock Froyo ROM, busy box, and I went through the same hell most of us with the SGS4G seemed to go through to get it unlocked (at which point I caved and called T-Mobil) and now that it's finally unlocked, it won't recognize the SIM card (China Telecom) it says 'no service' and claims that my phone number is unknown. I have a good signal though... OTL
I've used the SIM card in the (Android) phone it came with (a Chinese model, of course; it was hell to navigate.) So I know the card is fine.
I wanted to actually be able to use this phone as a phone before messing around with it, so if anyone has some ideas for me, I'd be much obliged. And while I'm on my knees I'll ask, do any of you know of a decent (free) VPN I can use to get over the Great Firewall of China? (youtube and fb aside, it'd be nice to get some real news without having Big Brother watching (and blocking) my every move)
TL;DR:
rooted SGS4G on stock Froyo ROM.
SIM unlocked but not acknowledged; can't send messages or make calls.
Not a SIM or signal problem.
Sent from my SGH-T959V using XDA App
Check your IMEI.
Is there is APN setting you need to enter manually for that SIM?
eksasol said:
Is there is APN setting you need to enter manually for that SIM?
Click to expand...
Click to collapse
Ah, it's an APN problem.
Looks like China Telecom uses the CDMA/EvDo rev, and whereas the SGS4G is made specifically for T-Mobile, which uses GSM/WCDMA. It's not acknowledging the China Telecom network, and won't even let me save the APN settings when enter them manually.
It looks like the difference is in the MNC value. I don't know much about it, but it only accepts '99' (for CDMA it's '03')
Well then... is it possible to even get my phone to use the China Telecom network?
APN settings for China Telecom
Most APN lists don't have China Telecom included (why? because it's CDMA? or is there some other conspiracy?), so I'm posting the settings for whoever need them, though I don't think this is the right place
Note: Under "Network Settings/Mode" you want "CDMA/EvDo" or "CDMA only" selected. if you don't have this option, sucks for you... and me D: (unless you know a fix???)
Name: CTWAP (or whatever you want to call it)
APN: #777
Proxy: 10.0.0.200
Port: 80
User name: [email protected] mycdma.cn [with no spaces]
*Password: vnet.mobi
Server: <not set>
MMSC: http : // mmsc.vnet.mobi [with no spaces]
MMS proxy: 100.0.0.200
MMS port: 80
MCC: 460
MNC: 03
Authentication type: PAP or CHAP
APN type: default,mms,supl
(There are two APNs, the above is for MMS, and other for data, I assume)
Name: CTNET
APN: #777
Proxy: <not set>
Port: <not set>
User name: [email protected] mycdma.cn [with no spaces]
*Password: vnet.mobi
Server: <not set>
MMSC: <not set>
MMS proxy: <not set>
MMS port: <not set>
MCC: 460
MNC: 03
Authentication type: PAP or CHAP
APN type: default,dun
* The password is from here: http : // code.google .com/p/cyanogenmod/issues/detail?id=1826 If for some reason it's wrong... sorry...
Hey all, Moto G US version owner here, and having trouble getting MMS working on at&t. I spent some time on the phone with them earlier and was more or less told that the phone wouldn't work right on network, or something to that effect. This was frustrating since everything else worked fine, and it is supposedly tailored for US networks after all. So I tried several different APN settings from online but to no avail. I even copied over the APN settings from my unlocked GS3 (which has no problems at all on at&t's network) and it still wouldn't work. I've contacted Moto's customer service as well and they've given me the number for Level 2 support, will be speaking to them soon.
I'm at a loss here.. yes, it is a new device and all, but is anybody else having this problem?
Try Handcent
boogalah said:
Hey all, Moto G US version owner here, and having trouble getting MMS working on at&t. I spent some time on the phone with them earlier and was more or less told that the phone wouldn't work right on network, or something to that effect. This was frustrating since everything else worked fine, and it is supposedly tailored for US networks after all. So I tried several different APN settings from online but to no avail. I even copied over the APN settings from my unlocked GS3 (which has no problems at all on at&t's network) and it still wouldn't work. I've contacted Moto's customer service as well and they've given me the number for Level 2 support, will be speaking to them soon.
I'm at a loss here.. yes, it is a new device and all, but is anybody else having this problem?
Click to expand...
Click to collapse
I was able to sent text messages just fine, but not MMS photos. I installed Handcent and set the photo size to 100k and the messages went through. I'll be calling Tmobile tomorrow to make sure it's not a provisioning issue.
I'll update if a solution is found.
oldcrow66 said:
I was able to sent text messages just fine, but not MMS photos. I installed Handcent and set the photo size to 100k and the messages went through. I'll be calling Tmobile tomorrow to make sure it's not a provisioning issue.
I'll update if a solution is found.
Click to expand...
Click to collapse
Would this help with receiving MMS messages though? I have issues sending and receiving them currently. Have not had an opportunity to speak with Motorola's level 2 support yet.
boogalah said:
Hey all, Moto G US version owner here, and having trouble getting MMS working on at&t. I spent some time on the phone with them earlier and was more or less told that the phone wouldn't work right on network, or something to that effect. This was frustrating since everything else worked fine, and it is supposedly tailored for US networks after all. So I tried several different APN settings from online but to no avail. I even copied over the APN settings from my unlocked GS3 (which has no problems at all on at&t's network) and it still wouldn't work. I've contacted Moto's customer service as well and they've given me the number for Level 2 support, will be speaking to them soon.
I'm at a loss here.. yes, it is a new device and all, but is anybody else having this problem?
Click to expand...
Click to collapse
I'm on AT&T Gophone, not AT&T postpaid, so your experience may be different, but I've had no problem sending MMS to other phones (android + iphones) or receiving them.
The AT&T rep set up two APN that I can see, including them here for you to try out if you want:
Name: AT&T Phone
APN: phone
Proxy: not set
Username: not set
Server: not set
MMSC: not set
MMS proxy: not set
MMS port: not set
MCC: 310
MNC: Not set
APN type: default, supl, hipri, dun
APN protocol: IPv4
APN enable/disable: APN enabled
Bearer: unspecified
MVNO type: none
MVNO value: not set
AT&T US MMS
Name: AT&T US MMS
APN: phone
Proxy: not set
Username: not set
Server: not set
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net
MMS port: 80
MCC: 310
MNC: 410
Authentication type: not set
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
APN enable/disable: APN enabled
Bearer: unspecified
MVNO type: none
MVNO value: not set
FWIW I've also used this AT&T APN Suggested from ATT forum and it also works with MMS after a reboot.
NAME: AT&T Phone
APN: wap.cingular
Proxy: (not set)
Port: (not set)
Username: [email protected]
Password: CINGULAR1
Server: (not set)
MMSC: http://mmsc.cingular.com
MMS Proxy: wireless.cingular.com
MMS port: 80
MCC: 310
MNC: 410
Authentication Type: (not set)
APN type: (not set)
APN protocol: IPv4
APN: enabled (may need to check this, not sure about your model)
Bearer: unspecified
angomy said:
I'm on AT&T Gophone, not AT&T postpaid, so your experience may be different, but I've had no problem sending MMS to other phones (android + iphones) or receiving them.
The AT&T rep set up two APN that I can see, including them here for you to try out if you want:
Click to expand...
Click to collapse
Prepaid? Last I remember prepaid doesn't support 4G devices for data. And MMS uses data, not wifi. And while I'm aware the MotoG can use 3G(I have mine on Verizon)...AT&T tends to lock down their better phones to 4G only to get users on the contract.
I could be mistake and that phone is supported, but I don't believe they run 4G on prepaid/gophone and hence you might not be able to run data.
As of 2012 they had an inner memo to their call centers saying that 4G devices, Rimms, and iPhones wouldn't be supported for Data any further.
Having same problem as original post
I'm having the same problem as original post, except I'm using StraightTalk. My Moto G is the US version - GSM (uses AT&T network). I've set it up to use the APN that StraightTalk provided. Browser works OK, so I know data services are working, but I can't send or receive MMS messages. I've also tried Handcent that was mentioned in this thread, but it still doesn't seem to be sending. I've also tried the AT&T APN settings from this thread, but no go. Not sure what else to do...
I just wonder this issue.
here are two cases of APN settings -EXAMPLE A and EXAMPLE B
EXAMPLE A
(Default)
Name: APN DEFAULT
APN: apn.jp
Proxy: (Not set)
Port : (Not set)
Username: username
Password: password
Server: (Not set)
MMSC: (Not set)
MMS proxy: (Not set)
MMS port: (Not set)
MCC: 440
MNC: 55
Authentication Type: CHAP
APN type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
(MMS)
Name: APN MMS
APN: apn.mms.jp
Proxy: (Not set)
Port : (Not set)
Username: username
Password: password
Server: (Not set)
MMSC: http://mms/
MMS proxy: mms.proxy.ne.jp
MMS port: 8080
MCC: 440
MNC: 55
Authentication Type: CHAP
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
EXAMPLE B
(Common to both Default and MMS)
Name: APN DEFAULT AND MMS
APN: apn.jp
Proxy: (Not set)
Port : (Not set)
Username: username
Password: password
Server: (Not set)
MMSC: http://mms/
MMS proxy: mms.proxy.ne.jp
MMS port: 8080
MCC: 440
MNC: 55
Authentication Type: CHAP
APN type: default, mms
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
I have just checked other threads, websites, etc, and some descriptions about "MMS without mobile data enabled", and I wondered.
Here is an interesting thread. According to it, we can send/receive MMS even when mobile data is disabled on some customised environment (not pure Android) such as MIUI, HTC, Sony, but we cannot send/receive MMS when mobile data is disabled on pure Android or Samsung Galaxy series.
I really wonder we must turn on mobile data toggles on APN settings EXAMPLE A. If APN setting is like EXAMPLE B, it may be true that we must turn on mobile data toggle in order to send/receive MMS.
On previous Synbian OS (Nokia), jailbreaked iOS (Apple), Windows Mobile, and fearture phones, we can send/receive MMS without mobile data toggle switch enabled. Why cannot only Android do the same if it is true that mobile data toggle must be swtiched on just for MMS.
There is another problem related to battery consumption. If we must always turn on mobile data toggle, the battery consumption will increase so rapidly, due to other background data tnansaction than MMS. The "packet filtering for MMS only" is vital and indispensable feature in terms of saving battery consumption, which is normal on any other mobile OS.
It is so easy to say on "APS Setting EXAMPLE B", "We must turn on mobile data toggle when sending/receiving MMS"
What I want to know is which case is correct on "APN settings EXAMPLE A"
Case 1:
Even on pure Android (nexus, etc), we must turn on mobile data toggle when sending/receiving MMS,regardless of SAMSUNG or Non-SAMSUNG handsets. MMS without mobile data enabled is only available on some manufacturer's customised Android handsets such as HTC and SONY.
Case 2:
Even on pure Android (nexus, etc), MMS without mobile data enabled is available as long we use any handsets except SAMSUNG.
It is just bug on SAMSUNG handset that we must turn on mobile data toggle even when we send/receive MMS only.
Which is right answer ? - Case 1? or Case 2? oe else?
I would like to know your answer, opinion and experience as much as possible. Thank you for your co-operation in advance.
References
Android Open Source Project - Issue Tracker
Issue 17329: Unable to send/receive MMS without first connecting to internet via APN
XDA Deveopers - Samsung Galaxy Nexus > Galaxy Nexus Q&A, Help & Troubleshooting
Auto connect data on sending/receiving MMS on non-MIUI ROMs. Possible?
Vodafone Community - Vodafone Australia
Why does Galaxy S4 need Mobile Data Switched on to send and receive MMS?
Sony Xperia Z1 > Xperia Z1 Q&A, Help & Troubleshooting
Any mms changes between firmware C6903 14.1.G.2.257 and 14.2.A.0.290?
Sony Xperia care - Support forum
Any mms changes between C6903 14.1.G.2.257 and 14.2.A.0.290 when mobile data disabled ?
what is your opinion?
Let me know your case.
Questionnaire Survey Form is here.
1. Your handset: (Samsung? or Non-Samsung?)
2. Pure Android (Nexus) or manufacturer's customised Andiroid?
3. Android OS version
4. Your Country
5. Your mobile operator
OKAY. So. The problem, in fact, had nothing to do with SIMlocking. It was trying to use a preinstalled T-mobile APN instead of the Ting APN.
One might think this would be the end of the problems, but it was not. I went in and manually selected the Ting APN. At this point I'm getting a normal LTE data indicator, and mobile data and SMS work, but phone calls still aren't. There are two separate Ting APNs, one for data and one for MMS. The one for MMS looked correct, but the one for data was missing information. Ting was supposed to send an automatic update to the phone to fix this, but although I was sent the message saying that they were sending it, it was not actually sent. So I went in to manually edit the APN according to these instructions:
APN settings for an X1 SIM cardNameTing DataAPNwholesaleMMSC
http://wholesale.mmsmvno.com/mms/wapenc
APN type*default,admin,fota,mms,supl,hipri,internet,dunMCC310MNC260APN protocolIPv4 / IPv6APN roaming protocolIPv4 / IPv6
Except I can't edit the Ting data profile. I can edit the SMS profile (though I don't want to, because it's not broken), and I can create a new profile, but I can't edit this one. So I think, okay, I'll make a new one and switch to that one. When I try to save it, it says my carrier doesn't allow profiles with the dun type, which is odd given it's in the default but I don't see why I'd actually need dial-up networking anyway, so I take that one out and save. It saves. I switch to that one. It switches.
I still cannot make calls.
Does anyone know why editing the data APN profile is locked, and how I can unlock it? Has anyone else had issues getting their carrier recognized by the new 19.1 LineageOS? What can I do to try to fix this? As much as I love the idea of never getting an actual phone call again, they are occasionally necessary.
_________________________________________________________________________________________________________________________________________
ORIGINAL TITLE AND POST:
H830 relocking (? maybe something else?) sim when LineageOS 19.1 is installed. Is there a fix?
I know there are already a million threads about trying to unlock H830s without access to the official app/with an ineligible phone/with a bad IMEI, etc. I have access to the official app and my IMEI clears just fine with my phone service provider. I'm... not hopeful, but given it is a different situation I thought it wouldn't hurt to ask.
Bought a phone sold as unlocked, then went through a convoluted process mostly following this guide (see my notes at the end) to get the bootloader unlocked and get Lineage 19.1 on there. At the stage with 15.1 unofficial lineage, it recognized my Ting sim card but seemed a little buggy, with fluctuating, mostly poor signal (as, honestly, one might expect from an early unofficial build). I didn't stay there long enough to investigate much further, but will do so later. At the stage with 19.1, it was locked to T-mobile again, though it also seemed to think my sim card was a T-mobile card, and allowed MMS but not calls. Knocked it back to stock 20A and used the app to "permanently" unlock it, which went without a hitch. Repeated the process, same result.
Is there any way to get this phone properly unlocked?
EDIT: The more I poke at this, the more I think the device really is unlocked properly now and something else weird is going on here. If it was just locked, my Ting SIM card shouldn't work at all and I should get some kind of alert about it, right? Instead the phone's listing T-mobile as my carrier and letting me send SMS, but not phone calls. Ting registers its existence as well, and I get signal on the signal indicator, just with a little "something is wrong" type exclamation point on it.
Here's some APN settings I found by setting my phone back on stock 20A (again) and going through the whole process of getting Lineage 19.1 on there (again).
From stock LG G5 on 20A
WAP service prompt successful
calls working, texts working
not set unless specified
Name: T-mobile LTE
APN: fast.t-mobile.com
MCC: 310
MNC: 260
APN type: default, xcap
APN protocol: IPv6
APN roaming protocol: IPv4
Name: Ting (primary)
APN: wholesale
MMSC: http://wholesale.mmsmvno.com/mms/wapenc
MCC: 310
MNC: 260
Authentication type: PAP
APN type: default, mms
APN protocol: IPv4
APN roaming protocol: IPv4
Name: EPDG MMS/XCAP
APN: tmus
MCC: 310
MNC: 260
Authentication type: PAP
APN type: xcap
APN protocol: IPv6
APN roaming protocol: IPv6
From stock LG G5, after recowvery exploit, TWRP, root
(no WAP service prompt, probably because I forgot to swap the card back and forth between another phone this time. Will try that and report back.)
calls working, texts working
not set unless specified
Name: T-mobile LTE (primary)
APN: fast.t-mobile.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MCC: 310
MNC: 260
APN type: default,supl,mms,xcap
APN protocol: IPv6
APN roaming protocol: IPv4
Name: EPDG MMS/XCAP
APN: tmus
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MCC: 310
MNC: 260
APN type: mms,xcap
APN protocol: IPv6
APN roaming protocol: IPv6
from Lineage 15.1 unofficial
no WAP service prompt after swapping card back and forth
calls not working, texts working
Not set unless specified
too many to go through in detail, presumably preloaded to work with many different carriers. will go through primary and Ting, and list any others enabled
Name: T-Mobile US LTE (primary)
APN: fast.t-mobile.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MCC: 310
MNC: 260
APN type:default,supl,mms,ia
APN protocol: IPv6
APN roaming protocol:IPv4/IPv6
Name: Ting Data
APN: wholesale
MCC: 310
MNC: 260
APN type: default,admin,fota,mms,supl,hipri,internet,dun
APN protocol: IPv6
APN roaming protocol: IPv6
Brightspot, multibrand
CellOne WAP, wap.cellular1.net
GIV Mobile, wholesale
GoSmart, multibrand
I-Wireless, i2-wireless.com
Net10, wap.tracfone
PTel, wholesale
Red Pocket, wholesale
Simple, simple
Solavei, solavei
StraightTalk T-Mobile, wap.tracfone
T-Mobile IMS, ims
Telcel America, wap.tracfone
Tracfone. wap.tracfone
US Mobile, pwg
Walmart Family Mobile, web.omwtoday.com
LineageOS 19.1 official
no WAP service prompt after swapping card back and forth (do get text saying update will be sent to phone, but that's it)
calls not working, texts working
Not set unless specified
Name: Ting Data
APN: wholesale
MCC: 310
MNC: 260
APN type: default,admin,fota,mms,supl,hipri,internet,dun
APN protocol:IPv6
APN roaming protocol:IPv6
MNVO type: GID
MVNO value: 6135
Name: Ting MMS
APN: wholesale
MMSC: http://wholesale.mmsmvno.com/mms/wapenc
MCC: 310
MNC: 260
APN type: mms
APN protocol: IPv4
APN roaming protocol: IPv4
MVNO type: GID
MVNO value: 6135