Note to Moderators: I'm placing this thread in the Development section because it is based on my Evo 3D guide, which has been in the Development section of that forum for over a year. Please move if this is not the correct place.
-------------------------
Hey guys.
I've gotten many PMs and replies on here asking how to get everything working on our Galaxy S3s on MetroPCS.
Here is how I got everything working on two Sprint Galaxy S3s on MetroPCS. I didn't come up with any of this information, I just put different files and guides together over the last two years and it has worked for me on the Evo 4G, Evo 3D, and now the Galaxy S3. Hopefully it will work for you.
REQUIREMENTS:
1) ROOTED CDMA Galaxy S3 (I only tried Sprint version, I assume Verizon and international versions might work)
2) Phone must be already flashed with voice and text. NO GUIDE CAN EVER OVERCOME THIS STEP. You need retailer access to MetroPCS's ESN database, and not just some software. You'll need to find an authorized retailer that can do it and knows how to do it. Craigslist is your friend. Once you have voice and text messaging working, come back to this thread.
PROVISIONING
First start by following bloodykiller86's Provisioning Guide STEP BY STEP.
The settings are the same across all devices. Following the instructions on the guide (for the Evo 4G) will get you set up correctly on the Evo 3D (my last phone) and on the Samsung Galaxy S3 CDMA variant.
Note: BloodyKiller86 uses QPST...we have to use DFS (4.0.4 or 4.0.5 DEMOs work just fine). Try to follow his settings or wait until I can write my own little thing on how to do this part with DFS.
DO NOT DOWNLOAD METRODROID. That rom is only for Evo 4G. After you complete step 28, come back to this thread.
http://forum.xda-developers.com/showpost.php?p=8395950&postcount=1
Now you should have voice, text and internet working.
3G SPEEDS
MetroPCS has upgraded their towers in most areas of service to include 3G coverage. If your area doesn't have it yet, it probably will get it soon enough.
You need to have PRL 3022 or newer for this to work (i'm using 3031 as of today).
So here we go,
Latest MetroPCS PRL
1. Download the latest .prl file.
2. Copy the .prl file to the root of your internal SD card and name it test.prl
3. Open your dialer and dial ##3282#
4. Click on View
5. Click on PRL Write
6. Your phone will reboot and that's it. You got the latest PRL and access to 3G service if its available in your area!
NOTE: some roms do not correctly show the difference between 3G and 1X service. You will notice the speed difference between 3G coverage and non-coverage areas.
MMS
This is the biggest hurdle, which very few people have successfully gotten to work. It is not a perfect solution but it works very well for us.
Download the following Zip file (not flashable):
download
Follow these instructions carefully:
1. Download and install Titanium Backup. You will also need the PRO version, so you'll need to shell out a couple of bucks if you don't already own it. It's well worth it anyways.
2. Download and install APN Backup & Restore from the Market.
3. Open APN Backup & Restore, ignore the ICS warning, and click on "Backup APNs". Exit out of APN Backup & Restore.
4. Place this folder in your SD Card.
5. Copy MetroPCS_MMS_Send_APN.xml from this folder to the APN Backup folder in the root of the SD Card.
6. Open Titanium Backup, go under Backup/Restore, and find APN Backup & Restore, press and select "Make system app."
7. Open APN Backup & Restore, ignore the ICS warning, press menu, and disable ICS check. Exit APN Backup & Restore.
8. Open APN Backup & Restore again, and now there should not be an ICS warning!
9. Click on "Delete APNs."
10. Click on Restore APNs and select "MetroPCS_MMS_Send.APN.xml".
10a. Press Ok after selecting the above.
10b. Press No when you get the message asking Yes or No.
11. Using Root Explorer or a similar app, copy the SecMMS.apk file from this folder to your /system/app/ folder.
11a. Make sure you are in R/W mode and click Yes to overwrite existing file if you get the message.
11b. Make sure to delete/overwrite any existing SecMms.apk from the /system/app directory. You should only have one SecMms.apk file.
11c. Make sure to delete any SecMms.odex if you're on the stock or an odexed rom.
12. Set permissions to RW-R--R--
13. Reboot.
14. Open the Messaging app and under Settings make sure to check (enable) "SMS split".
VOICEMAIL NOTIFICATIONS
As far as I know, and from my personal experience, the Sprint VoiceMail app does not work with MetroPCS.
I use the free app Voicemail Notifier and it has always worked reliably. It is no longer in the market, but you can download my modded version here.
Not flashable, extract to your sd card and install as a normal app.
OPTIONAL
MetroPCS Jelly Bean Splash Screen - download the "flashthisimage.zip" file and flash it in recovery. Always safe to wipe Cache and Dalvik Cache.
MetroPCS Jelly Bean Boot Animation - coming soon!
MetroPCS carrier name (this replaces the carrier name in the drop-down and in the lockscreen) - download the "eri_donotflash.zip" file. Extract it, copy the eri.xml file to your /data/ folder and set the permissions to RW-R--R--.
DISCLAIMER
Please proceed with caution and at your own risk. I am only providing this information for your information. Anything you do and the resulting consequences are your own responsibility. I am not responsible for any damages you cause to your phone hardware, software, service provider account, any charges you may incur, or any other damages that might result from your usages of this guide. You have been warned. Proceed with caution.
THANKS
- bloodykiller86 for his amazing guide two years ago, that still works today!
- alipendier for the original working Mms.apk and APN solution.
- oakieville for the better and improved Mms.apk! his original thread is here
- everyone else who's helped me. I know i'm forgetting a couple of you. I will add your name as soon as I remember!
thanks for the tutorial.
it's kinda missing HOW to get internet working if whoever flashed it for you didn't do it right. I'm still learning what programs we can use with the Galaxy phones. I was very good with the Evo line of phones...but QPST doesn't recognize the Galaxy phones apparently....everything else should be solid and work, as it did fine for my two Galaxy S3s
figured out how to edit the DATA settings so you can set up your phone to have internet access if you didn't already have it. I will be updating the guide this weekend.
anyone on Metro able to use Pandora on 3G? mine keeps skipping from song to song (but never starts the song) and I can't use it unless i'm on WiFi. everything else works.
O god this makes me want to cry. I tried getting a Sprint Nexus S over to Metro and could never do it
confirmed that MMS are coming in and out while ON WiFI and OFF WiFi, so I removed that limitation from the OP. also tested with HandCent, GoSMS and the stock SMS app...so it should work with most other apps as well!
and as of today Pandora was updated and it now works with MetroPCS's 3G. At least it's working great for me where it wasn't working before.
What are usual 3G speeds on metro? I'm new to sprint been with tmobile. So its like a culture shock switching to sprint and their slow speeds. Thinking about switching to a prepaid carrier that has better speeds
Sent from my iPad using Tapatalk HD
I paid someone on ebay to add my Sprint Galaxy S3 ESN to the metropcs inventory. Problem is, that he states LTE phone's ESN's are not supported for metropcs. Is there anyone that can add this ESN?
unfortunately sounds like he's trying to just take you for a ride. if he can add the ESN, then he can add the ESN. i think it's obvious it can be done just fine since there's so many of us that got our ESNs added.
my best advice is to search on craigslist for a local independent retailer that will add it for you. then come back here and follow my instructions.
li2mn007 said:
I paid someone on ebay to add my Sprint Galaxy S3 ESN to the metropcs inventory. Problem is, that he states LTE phone's ESN's are not supported for metropcs. Is there anyone that can add this ESN?
Click to expand...
Click to collapse
Sent from my SPH-D710 using xda app-developers app
Max_Pain said:
Note to Moderators: I'm placing this thread in the Development section because it is based on my Evo 3D guide, which has been in the Development section of that forum for over a year. Please move if this is not the correct place.
-------------------------
Hey guys.
I've gotten many PMs and replies on here asking how to get everything working on our Galaxy S3s on MetroPCS.
Here is how I got everything working on two Sprint Galaxy S3s on MetroPCS. I didn't come up with any of this information, I just put different files and guides together over the last two years and it has worked for me on the Evo 4G, Evo 3D, and now the Galaxy S3. Hopefully it will work for you.
REQUIREMENTS:
1) ROOTED CDMA Galaxy S3 (I only tried Sprint version, I assume Verizon and international versions might work)
2) Phone must be already flashed with voice and text. NO GUIDE CAN EVER OVERCOME THIS STEP. You need retailer access to MetroPCS's ESN database, and not just some software. You'll need to find an authorized retailer that can do it and knows how to do it. Craigslist is your friend. Once you have voice and text messaging working, come back to this thread.
PROVISIONING
First start by following bloodykiller86's Provisioning Guide STEP BY STEP.
The settings are the same across all devices. Following the instructions on the guide (for the Evo 4G) will get you set up correctly on the Evo 3D (my last phone) and on the Samsung Galaxy S3 CDMA variant.
Note: BloodyKiller86 uses QPST...we have to use DFS (4.0.4 or 4.0.5 DEMOs work just fine). Try to follow his settings or wait until I can write my own little thing on how to do this part with DFS.
DO NOT DOWNLOAD METRODROID. That rom is only for Evo 4G. After you complete step 28, come back to this thread.
http://forum.xda-developers.com/showpost.php?p=8395950&postcount=1
Now you should have voice, text and internet working.
3G SPEEDS
MetroPCS has upgraded their towers in most areas of service to include 3G coverage. If your area doesn't have it yet, it probably will get it soon enough.
You need to have PRL 3022 or newer for this to work (i'm using 3031 as of today).
So here we go,
Latest MetroPCS PRL
1. Download the latest .prl file.
2. Copy the .prl file to the root of your internal SD card and name it test.prl
3. Open your dialer and dial ##3282#
4. Click on View
5. Click on PRL Write
6. Your phone will reboot and that's it. You got the latest PRL and access to 3G service if its available in your area!
NOTE: some roms do not correctly show the difference between 3G and 1X service. You will notice the speed difference between 3G coverage and non-coverage areas.
MMS
This is the biggest hurdle, which very few people have successfully gotten to work. It is not a perfect solution but it works very well for us.
Download the following Zip file (not flashable):
download
Follow these instructions carefully:
1. Download and install Titanium Backup. You will also need the PRO version, so you'll need to shell out a couple of bucks if you don't already own it. It's well worth it anyways.
2. Download and install APN Backup & Restore from the Market.
3. Open APN Backup & Restore, ignore the ICS warning, and click on "Backup APNs". Exit out of APN Backup & Restore.
4. Place this folder in your SD Card.
5. Copy MetroPCS_MMS_Send_APN.xml from this folder to the APN Backup folder in the root of the SD Card.
6. Open Titanium Backup, go under Backup/Restore, and find APN Backup & Restore, press and select "Make system app."
7. Open APN Backup & Restore, ignore the ICS warning, press menu, and disable ICS check. Exit APN Backup & Restore.
8. Open APN Backup & Restore again, and now there should not be an ICS warning!
9. Click on "Delete APNs."
10. Click on Restore APNs and select "MetroPCS_MMS_Send.APN.xml".
10a. Press Ok after selecting the above.
10b. Press No when you get the message asking Yes or No.
11. Using Root Explorer or a similar app, copy the SecMMS.apk file from this folder to your /system/app/ folder.
11a. Make sure you are in R/W mode and click Yes to overwrite existing file if you get the message.
11b. Make sure to delete/overwrite any existing SecMms.apk from the /system/app directory. You should only have one SecMms.apk file.
11c. Make sure to delete any SecMms.odex if you're on the stock or an odexed rom.
12. Set permissions to RW-R--R--
13. Reboot.
14. Open the Messaging app and under Settings make sure to check (enable) "SMS split".
VOICEMAIL NOTIFICATIONS
As far as I know, and from my personal experience, the Sprint VoiceMail app does not work with MetroPCS.
I use the free app Voicemail Notifier and it has always worked reliably. It is no longer in the market, but you can download my modded version here.
Not flashable, extract to your sd card and install as a normal app.
OPTIONAL
You can now uninstall APN Backup & Restore.
DISCLAIMER
Please proceed with caution and at your own risk. I am only providing this information for your information. Anything you do and the resulting consequences are your own responsibility. I am not responsible for any damages you cause to your phone hardware, software, service provider account, any charges you may incur, or any other damages that might result from your usages of this guide. You have been warned. Proceed with caution.
THANKS
- bloodykiller86 for his amazing guide two years ago, that still works today!
- alipendier for the original working Mms.apk and APN solution.
- oakieville for the better and improved Mms.apk! his original thread is here
- everyone else who's helped me. I know i'm forgetting a couple of you. I will add your name as soon as I remember!
Click to expand...
Click to collapse
are you guys using a stock rooted rom?
this worked both on my wife's stock rooted rom and on a few variations of Blazer's Rom with and without the JellyBomb theme. I just moved to an AOSP JB rom today, will be testing if everything works and will report.
what version of the stock rom is it? i have 4.0.4 on mine and installed the seMms.apk with the right permissons and everytime i try to go to pictures to send mms the app FC. i tried fix permissions on recovery but still same issue. also does the stock rom need to be deodexed.?
she has 4.0.4 and completely stock, meaning it's still odexed. but if you follow the instructions you won't have a problem. the instructions say to remove the .odex file that is there if you're still odexed. you can't expect to run a deodexed mms apk while the odex file for the old apk is still there!
I did all the steps and it works great but I get 1x speeds. In the grandfather plan. But other than that, I keep getting data loss or roaming symbol atop the bar signals. What can cause this? Should I use the newer prl? Using 3022. Any help? Just using stock rooted 4.0.4
i did those exact steps and the app keeps FC. and yes i deleted secodex thingy.. what else could it be?
uzumakinaruto28 said:
I did all the steps and it works great but I get 1x speeds. In the grandfather plan. But other than that, I keep getting data loss or roaming symbol atop the bar signals. What can cause this? Should I use the newer prl? Using 3022. Any help? Just using stock rooted 4.0.4
Click to expand...
Click to collapse
i'm always using the latest. right now it's 3031. get it from the link on the OP.
electropyro said:
i did those exact steps and the app keeps FC. and yes i deleted secodex thingy.. what else could it be?
Click to expand...
Click to collapse
honestly, I don't know. i'm telling you what worked for me. on my wife's stock, rooted 4.0.4 the mms apk works fine. on Blazer's Rom it works fine, and on Codename Android (non TW-based) it's also running fine. must be user error. what, i don't know.
on a side note. I have NOT been able to get MMS working on Codename Android (is this AOSP or AOKP? one of the two). The apk itself works fine, but mms won't come in). i'm pretty sure it's down an APN issue, i'll post if i can figure it out.
I have a question. I have a sprint s3 flashed to verizon. What are the steps to return it to sprint? Change to a sprint prl and then ##786# code and reset?
Sent from my galaxy s3
Would my Sprint s3 be fully functional on metro or should I buy the one metro offers?
Sent from my SPH-D710 using xda premium
radrian92 said:
Would my Sprint s3 be fully functional on metro or should I buy the one metro offers?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Only thing missing would be LTE. I have it flashed and everything works perfectly.
Sent from my SPH-L710 using xda app-developers app
Related
NOW WORKING
EOS V1.0 4G Xoom (Stingray4g) with SMS/MMS enabled
I decided to give it a go at getting SMS/MMS working on the Xoom (Stingray 4g) running ICS.
Prerequisites (You must have a Messaging Package with VZW)
Install Instructions
Download Zip here http://goo.gl/jQtQ3
Copy to SD
Boot in CWM Recovery
Wipe Data
Wipe Cache
Wipe Dalvik Chache
Install Zip from SD
Enjoy!!!
(Flash at your own risk. I'd recommended backing up your current ROM before flashing)
Please let me know if you encounter bugs/glitchs and I'll do my best to work them out.
Credits:EOS (EOS V1.0 Stingray 4g)
Rivendel (SMS/MMS/SIP Hack)
Build Version with Messaging 02/08/2012 V.01
Why didn't you post this in development?
Sent from my Galaxy Nexus
bwcorvus said:
Why didn't you post this in development?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I hadn't yet met the requirements to post in the DEV thread. I will post it there as soon as my account can.
No go for me.
Installed and tried it out. All messages end with "message not sent " code 97. I tried swapping the network pref. Lte/cdma to cdma with no luck. Also tried handcentnt and gosms no joy. Nothing incoming either.
I'm willing to test other options if you come up with something.
dtrud0h said:
Installed and tried it out. All messages end with "message not sent " code 97. I tried swapping the network pref. Lte/cdma to cdma with no luck. Also tried handcentnt and gosms no joy. Nothing incoming either.
I'm willing to test other options if you come up with something.
Click to expand...
Click to collapse
Same thing here...
Same here. Even called Verizon to see about how my account was currently setup. No luck error 97 every time.
Please hit THANKS button if I help you, I have low very self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
dtrud0h said:
Installed and tried it out. All messages end with "message not sent " code 97. I tried swapping the network pref. Lte/cdma to cdma with no luck. Also tried handcentnt and gosms no joy. Nothing incoming either.
I'm willing to test other options if you come up with something.
Click to expand...
Click to collapse
When I used the SIM card for my Xoom, txts would not send (No SMS package on data plan) and code 97 would appear. However I used the SIM from both a Bionic and Razr with a texting plan and sent/received SMS/MMS and could place calls (with the dreaded bug of no voice).
No, I don't have a VZW acct for phone,just tablet data. I guess I should have known that.
is this complitable for mz600?
kylelwalker1990 said:
NOW WORKING
EOS V1.0 4G Xoom (Stingray4g) with SMS/MMS enabled
I decided to give it a go at getting SMS/MMS working on the Xoom (Stingray 4g) running ICS.
Prerequisites (You must have a Messaging Package with VZW)
Install Instructions
Download Zip here http://goo.gl/jQtQ3
Copy to SD
Boot in CWM Recovery
Wipe Data
Wipe Cache
Wipe Dalvik Chache
Install Zip from SD
Enjoy!!!
(Flash at your own risk. I'd recommended backing up your current ROM before flashing)
Please let me know if you encounter bugs/glitchs and I'll do my best to work them out.
Credits:EOS (EOS V1.0 Stingray 4g)
Rivendel (SMS/MMS/SIP Hack)
Build Version with Messaging 02/08/2012 V.01
Click to expand...
Click to collapse
I'm no expert, but it should not hurt to try it if you have a backup.
Something I noticed this version though is that it contains many more files than the umts version. That kind of worries me, it almost seems as though the other version is a patch where this version looks more like an incomplete rom. The only .img in it is the boot .img but it contains a whole slew of files in the system/app folder.
Something an established packager might want to look at before too long to verify it's safety for general consumption. Not saying that I don't trust the OP, but it just doesn't add up when compared to the umts version.
I tried this, and it did not work. I upgraded from a galaxy tab yesterday, and asked VZW tech support to make sure that my Texting plan would not get taken off.
According to the various techs I spoke with, including Motorola on this, is that VZW blocks ability to text on a system level. So their system wouldn't even allow adding texting to my plan for this device.
Motorola, well the hardware is there to text inside this tablet, its a VZW thing.
Im using Gvoice right now, and sms works, just no MMS right now. Voice calls work using gvoice as well, as a vzw tech inadvertently called my tablet's phone number, and it rang.
Im still working VZW on removing the block on my account for this device.
brittoking said:
Same here. Even called Verizon to see about how my account was currently setup. No luck error 97 every time.
Please hit THANKS button if I help you, I have low very self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
Click to expand...
Click to collapse
@brittoking
You know what? I think this is the best post you've ever done. And you know what?
You deserve it! [turns to his mirror] Because You're good enough, You're smart enough,
and, doggonit, people like you!
Stuart Smalley - Daily Affirmations - YouTube
Enable Wifi & Native Blue Tooth Tethering on Galaxy S3
*****Disclaimer: This has only been tested on ATT's Version of the Galaxy S 3 if it works on other Galaxys S 3 providers please let us know. But be warned that this may not work on your device if not using an ATT Samsung Galaxy S3.
Special Thaks: I want to thank Clubtech for providing the framework that allows the Tethering in the first place. I only built the script to make it an easier install for everyone. Which was per a request of the community.
Original Post For Clubtech's Enabling Wifi Tethering Tutorial
Requirements:
-Rooted Samsung Galaxy S3 (ATT Version has only been tested)
-Busybox installed on your Phone
- ATT Android STOCK ICS 4.0.4 (To check this go to Settings-->About Device-->Android Version and you'll see version 4.0.4, If you do not have ICS 4.0.4 I do not recommend trying this mod unless you possibly want a bricked phone.)
-Ensure your Build Number IMM76D.I747UCALG1 (To check this goto Settings-->About Device-->Build Number under this section you will see IMM76D.I747UCALG1.)
Steps:
1. Download the Clockwork Mod Install Script Here! (You do not have to register to download the file just click the download button)
2. Copy the script to your Internal SDCard on your Samsung Galaxy S3 Phone (you may have downloaded this file on your phone already just ensure its in the root directory of the Internal SDCard (/mnt/sdcard)
3. Reboot Phone in to Recovery Mode (Remember you will need Clock Work Mod Recovery to Install This)
4. Scroll Down to Install .zip from sdcard and click either home or power button
5. Scroll Down to Install .zip from Internal SDCard and click either the home or power button
6. Scroll Down to the line that starts with Yes blah,blah,blah (This is ensuring that you want to apply this zip. Make sure this is what you truly want to do)
7. Once installation is finished reboot the device
8. Once device is rebooted goto: Setting-->More Settings-->Tethering and Portable Hotspots Now you see that your device has Bluetooth Tethering there as an option and you will now notice if you start the Portable Wifi Hotspot your phone does not tell you to call ATTs 611 to enable this service.
9. Have fun tethering with your Galaxy S3 but remember if you aren't Grandfathered into ATTs Unlimited Data Limit then this means you do have a Data Limit and at the moment the highest they offer I believe is 2GB so any tethering being done on your phone will use your allocated Data Usage in a month and you may incur overage charges at $10.00 for each GB over 2GB. Even if you go 1MB over the 2GB data plan you will be charged the $10.00 so you might as well use the rest of the 1023MB available to you.
If you have any questions on this script please let me know. If you like this and find it usefull give some thumbs up please.
In other words this allows free tethering right? How does this make ATT not notice it?
--Update---
Tested it works as advertised. BTW if you can reply to my Qs.
In a sense yes. This allow you to bypass calling ATT and paying to have the ability to tether. Tethering still uses your allotted Data Usage. So in a way it's free and not free. Well however Clubtech obtained the file to open up the Tethering I do not know. But most likely because removing the old framework-res.apk from the phone and installing the new one is essentially removing ATTs code from the framework-res.apk. They may have a backup somewhere in the system that will allow them to detect tethering this I'm not sure of because I don't have access to this info. But from what I understand is they have to block it immediately because the only way they can tell data is being used on there network by a specific device is through the IMEI number so they can't tell what's behind the device being tethered to because it still shows data is being streamed from the device with IMEI xxxxxxxxxxxxxx
I was thinking that the code that was in the old framework-res.apk allowed the phone to contact ATT somehow to see if this specific IMEI can have tethering enabled. That's only a thought though
DudeWatsThat said:
In other words this allows free tethering right? How does this make ATT not notice it?
--Update---
Tested it works as advertised. BTW if you can reply to my Qs.
Click to expand...
Click to collapse
linuxboxsolution said:
In a sense yes. This allow you to bypass calling ATT and paying to have the ability to tether. Tethering still uses your allotted Data Usage. So in a way it's free and not free.
Click to expand...
Click to collapse
Not much of a problem since I have 3GB for the month, tethering would be a once or twice a month kinda thing for a very short period. Thanks for answering my Qs!
Which framework?
Which framework did you apply the mod to?
This is very important, since this script can only be run for people running a ROM whose framework is identical to the one you applied the mod to. There are already recovery scripts around for applying this mod (with the cell standby power reporting fix, too) for UCALEM (here, in the thread you mentioned in your OP) and UCALG1 (here, in the mods section).
I have the latest stock Rom. Ucalg I think. Can I use this or do I need to wait.
Sent from my SAMSUNG-SGH-I747 using xda premium
mscott998 said:
I have the latest stock Rom. Ucalg I think. Can I use this or do I need to wait.
Click to expand...
Click to collapse
You can use the one in the "mods" section at the bottom of this post:
http://forum.xda-developers.com/showthread.php?p=28672465
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
My phone is updated to the most recent release from ATT 4.0.4 and the framework works fine for me. Sorry about not explaining that in my initial post i'll edit that now.
drothenberger said:
Which framework did you apply the mod to?
This is very important, since this script can only be run for people running a ROM whose framework is identical to the one you applied the mod to. There are already recovery scripts around for applying this mod (with the cell standby power reporting fix, too) for UCALEM (here, in the thread you mentioned in your OP) and UCALG1 (here, in the mods section).
Click to expand...
Click to collapse
mscott998 said:
I have the latest stock Rom. Ucalg I think. Can I use this or do I need to wait.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
drothenberger said:
You can use the one in the "mods" section at the bottom of this post:
http://forum.xda-developers.com/showthread.php?p=28672465
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
linuxboxsolution said:
My phone is updated to the most recent release from ATT 4.0.4 and the framework works fine for me. Sorry about not explaining that in my initial post i'll edit that now.
Click to expand...
Click to collapse
Thanks for updating the initial post, but there are two "stock AT&T 4.0.4" releases, I believe. I think both UCALEM and UCALG1 are 4.0.4. It might be good specify the Build Number (I747UCALEM or I747UCALG1) instead, just to be sure. I know they updated the framework as part of the LG1 update.
drothenberger said:
Thanks for updating the initial post, but there are two "stock AT&T 4.0.4" releases, I believe. I think both UCALEM and UCALG1 are 4.0.4. It might be good specify the Build Number (I747UCALEM or I747UCALG1) instead, just to be sure. I know they updated the framework as part of the LG1 update.
Click to expand...
Click to collapse
Taking Care of now thanks for the warning.
drothenberger said:
Which framework did you apply the mod to?
This is very important, since this script can only be run for people running a ROM whose framework is identical to the one you applied the mod to. There are already recovery scripts around for applying this mod (with the cell standby power reporting fix, too) for UCALEM (here, in the thread you mentioned in your OP) and UCALG1 (here, in the mods section).
Click to expand...
Click to collapse
I'm liking your suggestion since it includes both MOD's...
As far as I know, AT&T will still detect wireless tethering and will send you a nasty letter or else force you onto a tethering plan. Has anybody found a way to tether without being detected?
If I'm using my phone internationally without this installed, I can turn on hot spot on with no problem right?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
grkmaster said:
If I'm using my phone internationally without this installed, I can turn on hot spot on with no problem right?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Good question. I would install this just to make sure that you can tether wherever you are. That's what I did.
Worked Perfect
Thank You very much. It worked perfect on my AT&T Samsung Galaxy S III SGH-I747. You da man. :victory:
woody1 said:
As far as I know, AT&T will still detect wireless tethering and will send you a nasty letter or else force you onto a tethering plan. Has anybody found a way to tether without being detected?
Click to expand...
Click to collapse
I was tethering on my Atrix and gs2 quite often and I've never received anything from at&t. And that was on a 2Gb data plan.
Sent from my SAMSUNG-SGH-I747 using xda premium
I do have a question concerning busybox. How necessary is that? Should it just be on the device or should its scripts be installed? Or does it even matter?
Edit: got it working. I'm a tidbit weary of altering somethings as I'm still on stock and most root apps I've messed with have their own busybox to go with them.
But I've done a little homework now and got it all squared away.
Sent from my SAMSUNG-SGH-I747 using xda premium
Bad Link
Link is bad
Link working now
gompka said:
Link is bad
Click to expand...
Click to collapse
I just downloaded and it works great. Give it a try again
linuxboxsolution said:
Enable Wifi & Native Blue Tooth Tethering on Galaxy S3
*****Disclaimer: This has only been tested on ATT's Version of the Galaxy S 3 if it works on other Galaxys S 3 providers please let us know. But be warned that this may not work on your device if not using an ATT Samsung Galaxy S3.
Special Thaks: I want to thank Clubtech for providing the framework that allows the Tethering in the first place. I only built the script to make it an easier install for everyone. Which was per a request of the community.
Original Post For Clubtech's Enabling Wifi Tethering Tutorial
Requirements:
-Rooted Samsung Galaxy S3 (ATT Version has only been tested)
-Busybox installed on your Phone
- ATT Android STOCK ICS 4.0.4 (To check this go to Settings-->About Device-->Android Version and you'll see version 4.0.4, If you do not have ICS 4.0.4 I do not recommend trying this mod unless you possibly want a bricked phone.)
-Ensure your Build Number IMM76D.I747UCALG1 (To check this goto Settings-->About Device-->Build Number under this section you will see IMM76D.I747UCALG1.)
Steps:
1. Download the Clockwork Mod Install Script Here! (You do not have to register to download the file just click the download button)
2. Copy the script to your Internal SDCard on your Samsung Galaxy S3 Phone (you may have downloaded this file on your phone already just ensure its in the root directory of the Internal SDCard (/mnt/sdcard)
3. Reboot Phone in to Recovery Mode (Remember you will need Clock Work Mod Recovery to Install This)
4. Scroll Down to Install .zip from sdcard and click either home or power button
5. Scroll Down to Install .zip from Internal SDCard and click either the home or power button
6. Scroll Down to the line that starts with Yes blah,blah,blah (This is ensuring that you want to apply this zip. Make sure this is what you truly want to do)
7. Once installation is finished reboot the device
8. Once device is rebooted goto: Setting-->More Settings-->Tethering and Portable Hotspots Now you see that your device has Bluetooth Tethering there as an option and you will now notice if you start the Portable Wifi Hotspot your phone does not tell you to call ATTs 611 to enable this service.
9. Have fun tethering with your Galaxy S3 but remember if you aren't Grandfathered into ATTs Unlimited Data Limit then this means you do have a Data Limit and at the moment the highest they offer I believe is 2GB so any tethering being done on your phone will use your allocated Data Usage in a month and you may incur overage charges at $10.00 for each GB over 2GB. Even if you go 1MB over the 2GB data plan you will be charged the $10.00 so you might as well use the rest of the 1023MB available to you.
If you have any questions on this script please let me know. If you like this and find it usefull give some thumbs up please.
Click to expand...
Click to collapse
Tried this on my Sprint S3 and no luck… Got a red "SIGNATURE VERIFICATION FAILED"…
Can u help me understand what this meant and why i got this..?? Anyway to create a zip file to work on the sprint version..?? Willing to PayPal a few $$ to get a solution to rid my error 67 when i try to activate my HotSpot… Reason being is i want to tether over Bluetooth due to its lower power consumption vs WiFi tether which is a battery killer…
New phone, and I already feel like a n00b again. Flame on if you wish, but here goes:
So I have a shiny new G S3, and after futzing with it and finding it full of the normal carrier crapware, figure it is easier just to flash it to something custom. So I get Cyanogenmod all ready, clockwork recovery set, flash, all pretty much with no drama (besides the normal USB driver fight) and... I have no 4G.
Now I *DID* have 4G on the sprint ROM, so I know that I am both in the service area as well as activated. I get *NO* data unless I switch the moble networks option to "CDMA/evDO auto". Then 3G works just fine. Put it on "LTE/CDMA/EvDo" and nothing (I can still make calls though).
I've tried the stable 10.0.0-d2spr build, a few of the nightlies, and one particular one I found on another thread (the 20121226 nightly build) and none of these do 4G.
So on this phone, do I need a radio or something (coming from the HTC world) along with the ROM itself? Is there some type of activation or registration apk I should be seeing and am just missing? I see all kinds of posts from last year about this phone from people who don't seem to even have 4G where they are... but not a single screenshot from anyone that shows the 4G connection icon on any custom ROM.
I'm willing to try just about any ROM, although I'd like to keep it to ones I can flash from clockwork recovery.
If it is of any hint, I couldn't use heimdall... got "protocol error"... but was able to install Samsung drivers and install clockwork with Odin with no problem at all.
It works on every rom based on the official firmware. (Freegs, freezas rom, blazer rom, etc) almost anything in android development.
A prl and profile update would probably do you some good.
I believe even cm supports lte, but I'm not much an aosp guy. You could try updating to the latest radio, May help.
I wish I could be more help, but I'm not a pro in this area as I don't have lte in my town yet. Lol
Id also recommend using twrp through goo.im
Sent from my SPH-L710 using xda premium
xblackvalorx said:
It works on every rom based on the official firmware. (Freegs, freezas rom, blazer rom, etc) almost anything in android development.
A prl and profile update would probably do you some good.
I believe even cm supports lte, but I'm not much an aosp guy. You could try updating to the latest radio, May help.
I wish I could be more help, but I'm not a pro in this area as I don't have lte in my town yet. Lol
Id also recommend using twrp through goo.im
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Cm does support 4G, as I had it on the stable version. Worked just fine. Restore your stock version, update profile and PRL then restore or re flash cm10 and it should work just fine.
I will post a screenshot later on cm10 with 4G.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
I took this LTE speed test the day I downloaded and installed LiquidSmooth beta 3.2.1. Worked on LTE for me, flawlessly.
Sent from my SPH-L710 using xda app-developers app
Whiplashh said:
Cm does support 4G, as I had it on the stable version. Worked just fine. Restore your stock version, update profile and PRL then restore or re flash cm10 and it should work just fine.
Click to expand...
Click to collapse
This may be a dumb question, but if I did that prior to flashing (I activated the phone, and started the reflash about an hour after that, but with LTE working), wouldn't the restore and then reflash just overwrite it again? Is there some way to back up the profile/prl, or some aftermarket/Sprint app to do it on a custom ROM? (or some secret phone number sequence, which I can't seem to find?)
I'm now on Liquidsmooth 3.2.1, and although nice, it also seems not to like LTE mode (no data/Internet at all).
Here's another new thought, though: when I'm on LTE mode in "mobile networks", and then go into About Phone -> Status, it does say "Mobile network type: LTE:13" with "service state: in service" and "roaming: Not Roaming" and I can make calls... so it looks like possibly an activation problem or something? Is there a set of passwords or auth keys stored somewhere that may need updating?
SomeRandomGuy said:
This may be a dumb question, but if I did that prior to flashing (I activated the phone, and started the reflash about an hour after that, but with LTE working), wouldn't the restore and then reflash just overwrite it again? Is there some way to back up the profile/prl, or some aftermarket/Sprint app to do it on a custom ROM? (or some secret phone number sequence, which I can't seem to find?)
I'm now on Liquidsmooth 3.2.1, and although nice, it also seems not to like LTE mode (no data/Internet at all).
Here's another new thought, though: when I'm on LTE mode in "mobile networks", and then go into About Phone -> Status, it does say "Mobile network type: LTE:13" with "service state: in service" and "roaming: Not Roaming" and I can make calls... so it looks like possibly an activation problem or something? Is there a set of passwords or auth keys stored somewhere that may need updating?
Click to expand...
Click to collapse
I'm pretty sure updating PRL and profiles just updates your radios, so it doesn't effect it if you restore a ROM. But don't quote me on that. There is a good chance I am wrong. All I know is I see around that seems to fix the error a lot, stock updating prl then restoring to cm10.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Well... followed this wonderful post...
http://forum.xda-developers.com/showthread.php?t=1904099
... and got back a stock image (and recovery) just like promised (Billiard412, you, sir, rock!). And with it, my 4G, working Sprint tether app, (can you tell what the most important feature is to me?)... and briefly thought of leaving it this way and trying to live with the crapware.
But... for science... I reflashed CM stable as those above suggested... and back exactly to where I was before. No data coverage at all unless I put it in EvDo mode.
Poking at the settings tab while on Sprint ROM, if anyone cares, the PRL doesn't change (still 24010) but the Sprint image did give me a filled in ICCID (the CM had that blank) as well as a "username". The mobile network type was now "LTE:14" (rather than "LTE:13" like it was on CM before and after) .
Sigh.
Might ye gods of XDA have any words of wisdom (I'll even take sympathy, at this point). No Nelson laughs, please.
SomeRandomGuy said:
Well... followed this wonderful post...
http://forum.xda-developers.com/showthread.php?t=1904099
... and got back a stock image (and recovery) just like promised (Billiard412, you, sir, rock!). And with it, my 4G, working Sprint tether app, (can you tell what the most important feature is to me?)... and briefly thought of leaving it this way and trying to live with the crapware.
But... for science... I reflashed CM stable as those above suggested... and back exactly to where I was before. No data coverage at all unless I put it in EvDo mode.
Poking at the settings tab while on Sprint ROM, if anyone cares, the PRL doesn't change (still 24010) but the Sprint image did give me a filled in ICCID (the CM had that blank) as well as a "username". The mobile network type was now "LTE:14" (rather than "LTE:13" like it was on CM before and after) .
Sigh.
Might ye gods of XDA have any words of wisdom (I'll even take sympathy, at this point). No Nelson laughs, please.
Click to expand...
Click to collapse
The problem is with CM10. It does support LTE, but there was a problem with the APN settings that causes the problems you're experiencing. There is a file you can flash on CM10.0 that will fix your problem, but you may be better off looking for a nightly from 12/26 or later (I think that was the first nightly with the fix, but I don't remember), or just jump to CM10.1. All CM10.1 nightlies have the fix in place already.
SomeRandomGuy said:
Well... followed this wonderful post...
http://forum.xda-developers.com/showthread.php?t=1904099
... and got back a stock image (and recovery) just like promised (Billiard412, you, sir, rock!). And with it, my 4G, working Sprint tether app, (can you tell what the most important feature is to me?)... and briefly thought of leaving it this way and trying to live with the crapware.
But... for science... I reflashed CM stable as those above suggested... and back exactly to where I was before. No data coverage at all unless I put it in EvDo mode.
Poking at the settings tab while on Sprint ROM, if anyone cares, the PRL doesn't change (still 24010) but the Sprint image did give me a filled in ICCID (the CM had that blank) as well as a "username". The mobile network type was now "LTE:14" (rather than "LTE:13" like it was on CM before and after) .
Sigh.
Might ye gods of XDA have any words of wisdom (I'll even take sympathy, at this point). No Nelson laughs, please.
Click to expand...
Click to collapse
EndlessDissent said:
The problem is with CM10. It does support LTE, but there was a problem with the APN settings that causes the problems you're experiencing. There is a file you can flash on CM10.0 that will fix your problem, but you may be better off looking for a nightly from 12/26 or later (I think that was the first nightly with the fix, but I don't remember), or just jump to CM10.1. All CM10.1 nightlies have the fix in place already.
Click to expand...
Click to collapse
I searched the CM10 thread and was able to locate the LTE handoff update. Unfortunately, the link no longer comes up in dropbox. I do, however, have it on my computer, but as I am not the original creator of the ZIP, I'm not sure about sharing something I did not create, as well as I do not know who the original creator is. If anyone out there can give me the permission, of or from, the original owner of the zip, I'll add it here.
Vanakatherock said:
I searched the CM10 thread and was able to locate the LTE handoff update. Unfortunately, the link no longer comes up in dropbox. I do, however, have it on my computer, but as I am not the original creator of the ZIP, I'm not sure about sharing something I did not create, as well as I do not know who the original creator is. If anyone out there can give me the permission, of or from, the original owner of the zip, I'll add it here.
Click to expand...
Click to collapse
I also have the 12/26 nightly. It is okay to share I'm pretty sure as long as you don't take credit for it.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
SomeRandomGuy said:
Well... followed this wonderful post...
http://forum.xda-developers.com/showthread.php?t=1904099
... and got back a stock image (and recovery) just like promised (Billiard412, you, sir, rock!). And with it, my 4G, working Sprint tether app, (can you tell what the most important feature is to me?)... and briefly thought of leaving it this way and trying to live with the crapware.
But... for science... I reflashed CM stable as those above suggested... and back exactly to where I was before. No data coverage at all unless I put it in EvDo mode.
Poking at the settings tab while on Sprint ROM, if anyone cares, the PRL doesn't change (still 24010) but the Sprint image did give me a filled in ICCID (the CM had that blank) as well as a "username". The mobile network type was now "LTE:14" (rather than "LTE:13" like it was on CM before and after) .
Sigh.
Might ye gods of XDA have any words of wisdom (I'll even take sympathy, at this point). No Nelson laughs, please.
Click to expand...
Click to collapse
Download, but do NOT extract. Flash AOSP/CM rom first, then kernel of choice (if you don't use provided kernel for rom, and finally, flash the update. As always, prior to beginning a new rom install, always wipe data/factory reset/wipe dalvik cache.
Credit to the original creator of this file. CM10/AOSP LTE/3G handoff update:
** Got Verizon Note 4 Dev Edition to work with Alliance T-Mobile ROM!! Data, calling, sms, mms work ! I smell a daily driver! **
ATTENTION: Please be careful make a nandroid of your current Verizon ROM. I am not responsible if you break your phone or lose data on your device!
**This is using the BETA version of Alliance ROM for T-Mobile Note 4. Read this thread: http://forum.xda-developers.com/not...-0-1-allianceromn910t-18-themes-huge-t3085560 to get an idea of the features of this ROM. Give lacoursiere18 and hsbadr a thanks and donate to them for making this great ROM and kernel.
Follow these steps one after the other and don't stop**
1. Make sure you are on a stock OAF Lollipop ROM using Multisystem #1 kernel, I think I used Rick's OAF Lollipop ROM. I am on BOG modem so I'm pretty sure any Lollipop modem will work with this.
2. Make copies on your SD card of:
- system/buildprop.xml & cscversion.txt
- system system/etc/apns-config.xml
- system/etc/permissions/verizon_net_sip_library.xml & vzwapnlib.xml
- system/lib/libril.so & libsec-ril.so
- system/apps/VzwActivationAgent & vzwapnpermission folders
- system/framework/VZWAPNLib.apk
- system/privapp/VZWAPNService & secmms_candy folders
- system/csc folder
Reboot
4. Reboot into recovery and make a TWRP backup of everything
5. While in recovery dirty flash Alliance ROM BETA on top of stock lollipop ROM OAF that is using Multisystem #1 kernel (Wipe everything except data, and SD of course.)
6. Delete system/privapp/diagmonagent.apk and system/lib/libdiagmonagent.so because at startup it was sending some kind of diagnostics and thought it was messing with the data drop. Ever since these changes and a reboot data has been stable!
Reboot
7. Download root browser and swap those copied files in the appropriate file location. Change them to the correct permissions (the folders get 0755 and the files 0644, compare with other files and folders that are in place already. Make sure you change the permissions on all folders copied over and their contents). **Longest Step**
Reboot
8. Edit feature.xml in the system/csc folder and add:
<CscFeature_RIL_ForceConnectMMS>true
</CscFeature_RIL_ForceConnectMMS>
Above these tags on the bottom :
</FeatureSet>
</SamsungMobileFeature>
This enables auto download mms when data is toggled off !
Reboot
9. Make an backup in TWRP and you have your own custom ROM
I'm pretty sure this ROM is not compatible with xposed but it is very customizable, smooth, and it comes with a lot of features built in.
**READ ME**
Bugs:
- Silent mode is only available using the toggle. Volume down only goes to vibrate.
**
- Battery section in settings is missing
- No way to remove battery percentage in status bar
(Workaround: Download "Battery Usage Shortcut" from the Playstore to access the battery section and to remove battery percentage)
**
- No way to uninstall 3mint battery mod without messing the systemui up
- Now that the mobile network settings are correct the advanced calling option is avaliable but it force closes and messes up your data connection. A reflash of everything will be needed so don't click on it! (I have a feeling a Verizon app is missing but not going crazy about this)
Any suggestions or thoughts about these current bugs would be helpful.
I cannot guarantee all Alliance settings will work but most of them do, it's awesome.
This manual port is now stable ! All basic phone functions work. Let me know if you come across any bugs or issues not related to Alliance settings. I will try to help fix it.
Thanks Stedrocklp for taking the time to try and get this working. Jal3223 thanks for sharing that key porting info!!! Wouldn't be possible without your help! Thanks hsbadr for developing Multisystem kernel ! Thanks lacoursiere18 for creating this ROM !
I did the same thing with similar results. Unfortunately I don't have the knowledge needed to get it functioning on the VZW N4. I still faithfully run alliance on my N3 and am dying to have it on my N4. Maybe we should try to get one of our great devs to hook us up.
stedrocklp said:
I did the same thing with similar results. Unfortunately I don't have the knowledge needed to get it functioning on the VZW N4. I still faithfully run alliance on my N3 and am dying to have it on my N4. Maybe we should try to get one of our great devs to hook us up.
Click to expand...
Click to collapse
I hear you man I came from the Note 2 with Alliance. That would be nice hopefully one sees this thread. So I should be a little more descriptive with the process of getting it stable with just mms and sms failing. I am sure coming from any LP ROM without xposed preloaded will work. I dirty flashed from Ricks ROM and get a Play Services error and it keeps popping up. I went into the app info of Google settings app, clicked manage storage, and wiped all data and then cache. After that it seems stable. I also edited the build.prop using build prop editor and changed all the tmo entries with vzw, saved, and rebooted and got the Verizon data icon signals. The mms and sms issue I believe has something to do with APNS but idk how that works. There is no way to edit the APNs in the mobile network settings by the way. I'm dying to get this to work too lol
I actually went in and put in the Verizon apns in the apns-conf.xml and I still couldn't get sms to work. What's funny is that I did get MMS to work so when I sent a message to anyone, I would send a pic too. My friends and family were like why do you keep sending nonsense photos LOL. Would it be something with the kernel/boot.img you think?
stedrocklp said:
I actually went in and put in the Verizon apns in the apns-conf.xml and I still couldn't get sms to work. What's funny is that I did get MMS to work so when I sent a message to anyone, I would send a pic too. My friends and family were like why do you keep sending nonsense photos LOL. Would it be something with the kernel/boot.img you think?
Click to expand...
Click to collapse
What values do you replace in the apns-conf.xml ? Yeah it's probably the boot.img how do we replace that? I tried doing this in the past but couldn't find our boot.img in a ROM. And every time I zipped the ROM back it never flashes always an error. I think it needs to be signed but idk how to do that. We're almost there !
I am going to try to swap the APN's and the boot IMG from a working Verizon rom and see what happens. I got so close to having it work I just couldn't get sms to work no matter what edits or adjustments I made. Having the MMS work meant that there was hope there must just be something I am missing. Let me do some tinkering and see if I can come up with something functional. If there is a will there is a way. Right?
stedrocklp said:
I am going to try to swap the APN's and the boot IMG from a working Verizon rom and see what happens. I got so close to having it work I just couldn't get sms to work no matter what edits or adjustments I made. Having the MMS work meant that there was hope there must just be something I am missing. Let me do some tinkering and see if I can come up with something functional. If there is a will there is a way. Right?
Click to expand...
Click to collapse
What you taking about you don't know how to do this stuff lol. Yeah man there has got to be a way. We basically ported it lmao. Let me know what happens !
Maybe we should replace these files too? And what do you think this sentence means? That could be the problem, maybe? Lol
So far I have swapped the APNs and have copied the verizon specific apps that you mentioned. I am currently at the alliance boot animation but ? takes so long to load on the first boot I can't tell if it's stuck or I am impatient.
Sent from my SGP561 using Tapatalk
That's the worst wait ever lol
Well I have two failed attempts using the inernational version. Now I am going to try on the T-Mobile version with the same edits. I am going to get this going one way or the other.
stedrocklp said:
Well I have two failed attempts using the inernational version. Now I am going to try on the T-Mobile version with the same edits. I am going to get this going one way or the other.
Click to expand...
Click to collapse
I have my fingers crossed ! Did you do anything with the boot.img?
Yes I am using the boot.img from morom and it does get to the boot animation so we should be headed in the right direction.
stedrocklp said:
Yes I am using the boot.img from morom and it does get to the boot animation so we should be headed in the right direction.
Click to expand...
Click to collapse
Awesome! I'm saying my prayers haha :highfive:
jcip17 said:
That's the worst wait ever lol
Click to expand...
Click to collapse
Well I am getting closer to success. I got it to boot all the way though and go through the setup process. One problem; No Service! For some reason I am getting no service at all so I will have to recheck that all the Verizon BS is in place and working. Geesh Verizon sure does make this more difficult than it needs to be. Moving in the right direction though!
stedrocklp said:
Well I am getting closer to success. I got it to boot all the way though and go through the setup process. One problem; No Service! For some reason I am getting no service at all so I will have to recheck that all the Verizon BS is in place and working. Geesh Verizon sure does make this more difficult than it needs to be. Moving in the right direction though!
Click to expand...
Click to collapse
That's great that you got it to boot. Even though this may seem tedious, maybe try doing one verizon specific app by one? And maybe try replacing the T-Mobile mms-candy with the verizon one. I forgot lacoursiere18 recommended that when I was trying to make it work in the past. I tried doing it while I had Alliance installed and it messed up the app. The emoji kinda like this one was in place of the send button. It was actually pretty funny that that happens but idk maybe having it pre-installed will have better results? He also said something about the libs but I guess we should try one change at a time lol
I read the permissions of this application and it seems to deal with sending and receiving text messages and mms. Maybe this is the piece that was missing after editing the apns?
The T-mobile variant has two. Bin files the I removed thinking the we wanted to use the verizon modem but maybe they need to be there so I just added them back. I added the activation agent and all other verizon apps and libs. I couldn't find a lib file for mms_candy but I did swap them. Did you edit anything when you flashed or did you just flash as-is?
Sent from my SGP561 using Tapatalk
stedrocklp said:
The T-mobile variant has two. Bin files the I removed thinking the we wanted to use the verizon modem but maybe they need to be there so I just added them back. I added the activation agent and all other verizon apps and libs. I couldn't find a lib file for mms_candy but I did swap them. Did you edit anything when you flashed or did you just flash as-is?
Sent from my SGP561 using Tapatalk
Click to expand...
Click to collapse
So far I only flashed as is. What values did you change on the apn config to get mms working? I completely swapped it with the Verizon one but that didn't work.
Got mms to work using GoSms and manually configuring the APN the msmc whatever to http://mms.vtext.com/servlets/mms
And the mms port to 80.
Now if we can only get sms to send we have a fully functioning alliance ROM on Verizon !
When I navigate to the APN settings, no APNs are visible.
The following message displays:
Access Point Name settings are not available for this user.
Question: What type of user do I need to activate so I can see the APN settings?
(Or is this the wrong question to be asking? Need to see APN settings.)
My hardware, software and network:
Phone: Samsung Galaxy S III (Sprint) - SPH-L710
Software: cm-12.1-20150619-NIGHTLY-d2spr.zip
Network: Ting (Sprint)
themanwest2000 said:
When I navigate to the APN settings, no APNs are visible.
The following message displays:
Access Point Name settings are not available for this user.
Question: What type of user do I need to activate so I can see the APN settings?
(Or is this the wrong question to be asking? Need to see APN settings.)
My hardware, software and network:
Phone: Samsung Galaxy S III (Sprint) - SPH-L710
Software: cm-12.1-20150619-NIGHTLY-d2spr.zip
Network: Ting (Sprint)
Click to expand...
Click to collapse
Did you enable developer options and root?
lvpre said:
Did you enable developer options and root?
Click to expand...
Click to collapse
Yup. I have root access for apps and ADB from the Developer Options menu.
themanwest2000 said:
When I navigate to the APN settings, no APNs are visible.
The following message displays:
Access Point Name settings are not available for this user,
Click to expand...
Click to collapse
I am having this same exact issue! I been looking all over Google and XDA the last week or two without any luck.
Most sources say install APN Backup and Restore app, but it still doesn't work. It gives some other permission error. Then when using /system/mover app to move APN Backup and Restore to system, it fails and gives some other error in turn breaking the app, which then has to be reinstalled to be back in the same situation as before.
Some say install a flashable APN fix, if you are lucky to find one for your carrier. I am using this Sprint S3 flashed to Pageplus, and I can not find a Pageplus or Verizon APN file to flash anywhere. Perhaps you will get lucky and find one Ting? or a custom rom with a Ting variant? I have not seen any of these yet, but not sure if they exist somewhere. If not I think we are screwed? There has to be a way...
I have experienced this on all 5.x and some 4.4.x roms for this device, and I have not found a solution anywhere yet. I highly believe it is related to this: link If anyone is able to shed some light on this issue (or the solution) would be greatly appreciated.
Saafir said:
You don't HAVE to have a flashable zip. You can manually place your APNs. system>etc>apn-config.xml
Click to expand...
Click to collapse
I don't see the system folder or the file you mention (system>etc>apn-config.xml) Saafir.
I have created two APNs needed for Ting, but I need to remove any APNs that may cause any problems. Right now I don't see any APNs, even tho I have created and saved two APNs (which helped bring data to my phone).
So back to my original question, what type of user do I need to activate so I can see the APN settings? Thanks for your time and help.
themanwest2000 said:
I don't see the system folder or the file you mention (system>etc>apn-config.xml) Saafir.
I have created two APNs needed for Ting, but I need to remove any APNs that may cause any problems. Right now I don't see any APNs, even tho I have created and saved two APNs (which helped bring data to my phone).
So back to my original question, what type of user do I need to activate so I can see the APN settings? Thanks for your time and help.
Click to expand...
Click to collapse
The settings are only there if you already have apn installed. That setting doesn't allow you to create apn there, it only allows you to choose between installed APNs. If you have none, then it will say unavailable for this user.
Saafir said:
You don't HAVE to have a flashable zip. You can manually place your APNs. system>etc>apn-config.xml
Click to expand...
Click to collapse
I have them listed in system>etc>apn-config.xml, but it still not viewable in the APN section of settings. MMS definitely isnt working and mobile data isnt always working. Im using the 0714 nightly for on my Sprint GS3 that im using with boost.
MACscr said:
I have them listed in system>etc>apn-config.xml, but it still not viewable in the APN section of settings. MMS definitely isnt working and mobile data isnt always working. Im using the 0714 nightly for on my Sprint GS3 that im using with boost.
Click to expand...
Click to collapse
You have to flash the boost apn fix.
madbat99 said:
You have to flash the boost apn fix.
Click to expand...
Click to collapse
I thought someone said it wasn't required. I have flashed the universal boost fix r2 that I used with the nightly from about 2 months ago. Doesn't make a. Difference. Even re flashed it. I'm assuming that's e only way that setting xml got there in the first place. Is there another fix that I'm unaware of?
MACscr said:
I thought someone said it wasn't required. I have flashed the universal boost fix r2 that I used with the nightly from about 2 months ago. Doesn't make a. Difference. Even re flashed it. I'm assuming that's e only way that setting xml got there in the first place. Is there another fix that I'm unaware of?
Click to expand...
Click to collapse
Full wipe, flash rom, gapps and boost apn fix. Boot up fully once, then back to recovery and flash rom and gapps again (no wipe, no apn fix this time).
madbat99 said:
Full wipe, flash rom, gapps and boost apn fix. Boot up fully once, then back to recovery and flash rom and gapps again (no wipe, no apn fix this time).
Click to expand...
Click to collapse
Just reflashed the rom and gapps, no diff.