ok so i have been searching far and wide i am using a sprint galaxy s3 running wicked sensations 5.0 and i am having issues with the boot sounds i put in they start late when the phone is almost done with the boot animation and i can not figure out what to do to make it start when it is suposed to like with the stock os if anybody could help me with this issue that would be great also i am having issues using aosp roms when it comes to sending and receiving mms i have replaced the apns with the correct sprint apns via apn back up and restore but still nothing and i have tried go sms pro also i need to note on this that i am also using a sprint prepaid company called expo wireless and i have changed the mmsc url to the correct one again this works on tw based roms but not on aosp roms and there are a ton more aosp roms that i love the features to compared to the one i am using but this rom is a great rom dont get me wrong help please any one!?!?!?!
Related
I have a problem receiving MMS pictures, they come in as thumbnails instead of the full intended size. I'm not a Sprint customer I flashed my phone to nTelos and have no other problems besides MMS.
My typical procedure is to use Titanium Backup then convert APN Backup & Restore as a system app on ICS roms. After restoring APN I use Build Prop Editor to change the mms numeric ID and name to nTelos. I also edit the data profile changing the mms from Sprints server to nTelos. This works for some roms but not others, mainly OTA rooted releases and some custom roms seem to have issues downloading the message. I'd be happy to get a custom rom to work but mainly the ones that do are in alpha or beta which have too many bugs to be a daily driver.
Anyone have an idea why this happens, is it the mms.apk? If so can I replace the mms.apk with another rom developers apk?
I've found a great rom that's stable with good battery life and great performance, but the MMS problem is killing me so any help would be greatly appreciated!
bump.... I'm surprised I haven't received a response yet.
Mms issues in stock based roms
The stock ROMs are the issue. DEODEXED ROMs may help. The MMS.apk is tied to framework and is needed for sms in any fix for MMS I have tried. I use Cricket. Gingerbread was the only way people got MMS working in the stock MMS app on most ROMs. Try googling for Cricket universal MMS apk. And post back here if it worked for you. From what I have read it worked for metropcs and boost users.
I also have ntelos. I'm on Hyperdrive 16.1 w an s4. I like s stock and prefer it. I'll work with you on it if you want. I've been trying for awhile now and came get it right yet.
http://forum.xda-developers.com/showthread.php?p=54918790
I tried to port several AOSP CM based roms from the Galaxy Nexus and the Nexus 4. with these guides. http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=2069850
When I use HERO guide the phone never boots more than the boot logo and when I use the other guide I get error status 7.
Im using CM nightly as a base.
Also I tried to port TW roms from the Verizon forums using HERO guide and this guide http://forum.xda-developers.com/showthread.php?t=2104604 But the only issue I have is the it says ''SIM NOT SUPPORTED, NONE VERIZON SIM''
Although the ported rom works fine with data,calls but that non verizon sim gets stuck on the notification bar.
I have ported all the libs and set up build.prop and cant seem to find the issue.
The rom I ported was PLASMAVIII.
Somebody with more experience can take a look at the rom I ported and see what is wrong? It's not going to brick your phone I have flashed it several times and it works.
Anybody interested in helping me can PM me for the link
gypsy214 said:
I tried to port several AOSP CM based roms from the Galaxy Nexus and the Nexus 4. with these guides. http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=2069850
When I use HERO guide the phone never boots more than the boot logo and when I use the other guide I get error status 7.
Im using CM nightly as a base.
Also I tried to port TW roms from the Verizon forums using HERO guide and this guide http://forum.xda-developers.com/showthread.php?t=2104604 But the only issue I have is the it says ''SIM NOT SUPPORTED, NONE VERIZON SIM''
Although the ported rom works fine with data,calls but that non verizon sim gets stuck on the notification bar.
I have ported all the libs and set up build.prop and cant seem to find the issue.
The rom I ported was PLASMAVIII.
Somebody with more experience can take a look at the rom I ported and see what is wrong? It's not going to brick your phone I have flashed it several times and it works.
Anybody interested in helping me can PM me for the link
Click to expand...
Click to collapse
for the one that gets stuck on the boot animation, you could try to take a logcat to see what the issue is.
The non verizon sim thing should be easy to fix. Upload it and ill try to look at it tomorrow after work
Sent from my SGH-T999 using Tapatalk 2
ziggy46 said:
The non verizon sim thing should be easy to fix. Upload it and ill try to look at it tomorrow after work
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
It sure is. It had something to do with the setupwizard.apk He had the samsung setup wizard and not the stuck google one.
as soon I clear the data of the app it went off. rom runs great, Also it doesnt have tether. Will look into the framework-res.apk with Jovi's tethering mod
Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
re: 4.2.2 roms
jdsung said:
Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
Click to expand...
Click to collapse
That's an easy questiion, like I have been saying all along none of the cm10/aosp/aokp or ported roms
are ready for prime time, they are good for those who want to experiment with a few features not found
in stock t999 4.1.1 Touchwiz Jellybean roms. None of the cm/aosp/aokp roms even have the Wifi calling feature.
That's why after trying all the aosp/aokp/CM and ported roms I have come to the conclusion above.
So unless you like experimentation only flash T-Mobile T999 stock 4.1.1 Touchwiz Jellybean roms
or any of the custom roms which are based on T-Mobile T999 Touchwiz v4.1.1 Jellybean stock rom.
The best custom T999 T-Mobile Touchwiz Jellybean 4.1.1 based rom in my opinion
is the Wicked v9.1 custom rom, check it out you won't be disappointed.
Good Luck!
You could always try to flash your 4.2.2 Tim of choose and choose not to restore Google backup, Google backs up settings. If it works without setting up your account then go from there.
Sent from my SGH-T999 using xda app-developers app
Hello all. I recently came back tothe s3. I have a tmobile s3 and I am running a cm rom. I am able to tehter using tw roms but cannot get it to work on any aosp roms. I've searchedand found nothing so I'm hoping someone can help.
sent via note 8.0
So I've done some searching in the forum (on phone) and wondered if anyone else is having an issue flashing roms other than stock rooted.
I've tried all kinds of other roms cm, miui, liquid smooth, et cetera, and they all get stuck at boot. This is a new thing because I've run all these roms in the past.
I'm on moar 6.1 and it's a great Rom, but I'd like the option to change roms at some point...
You are naming AOSP roms. If you have a newest S3, please try with an updated version. Start with SlimBean build 2( exactly that one) because it's confirmed to work with newest models.
Sent from my SPH-L710
csmasn said:
You are naming AOSP roms. If you have a newest S3, please try with an updated version. Start with SlimBean build 2( exactly that one) because it's confirmed to work with newest models.
Sent from my SPH-L710
Click to expand...
Click to collapse
Dude....it wasn't the ROM's fault at all, nor the phone's....it was the loose nut behind the wheel....me.
I forgot (have been forgetting) to format data. For whatever reason, I was manually formatting just the minimums. DANGIT! Works like a charm now...or rather I'm working like a charm now.
Thanks anyway.