Database Info

Choosing an ICS/Jelly Bean ROM

Just sharing my experience in upgrading to Jelly Bean on the Captivate.
Before you begin:
Before you begin, back up your efs partition.
Some ICS and JB ROMS have issues where they will forget your IMEI. If this is the case you'll need to restore your efs partition. If you don't already have a back up, you'll have to reflash to stock (pain in the butt) so that you can back up your efs so that you can restore it on your shiny new ROM. Without an IMEI, you won't be able to make calls or access wireless networks.
How to Backup/restore EFS: http://forum.xda-developers.com/showthread.php?t=859914
General Process
ICS and Jelly Bean are too big to put the entire rom in /system, so the current practice is to break up the ROM into 2 or more zip files (the ROM itself and a second zip that has essential apps like the Market). Both have to be flashed.
The ROMs have upgraded CWM (Recovery Modules) so you have to flash the ROM twice. The first time installs the CWM, the second time installs the ROM.
My journey
I had been using Mosaic, which is now defunct. When I started seeing posts from Studacris (former Mosaic developer) from several months ago saying "Gingerbread? What is this the stone age?" I decided perhaps is was time to upgrade to ICS.
Of course when I started looking at ICS ROMS, it turns out that now there are Jelly Bean ROMS available as well. Some people say the JB ROMS solve several problems with ICS. Others say the ICS are more stable for now.
Moral of the story. Your Captivate is unique. You won't know which is which until you try them, but my journey may help you.
1. I want to try Slim Bean, but coming from Gingerbread, it's recommended to start on Cynanogen (CM)
2. So I might as well try CM, but do I try CM9 (ICS) or CM10 (JB)?
3. Ah what the heck, let's go CM10!!!
4. Okay, there's at least four versions. The official, three unofficials of varying "v" releases, the Devil version with datadata (what the heck is datadata?), some guy's custom rolled ROM which he says is likely to brick your phone.
5. Okay, I'll try the latest V8 version with the Devil kernel (note, you should use the version with datadata).
6. Flash goes fine, but now it hangs on black screen with the word Android. After 30 minutes, I figured it really was hanged. Reflashing and rewiping solved that problem.
7. I had a lot of issues with it (see below), so I decided to try Slim ICS.
8. I had other issues with SlimICS (see below), so what the heck, let's try Slim Bean.
9. Slim Bean seems like a keeper to me: Fast; great feautures; decent launcher (vastly better than SlimICS). Only real problem I'm finding is that the Market won't let me install (or even see) Astro Player, which is one of my absolute must have apps. Still trying the dev's workaround.
CM 10 Issues:
Outdated:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Update CM10
Everything works fine in CM10 Helly Bean (29.07.2012). Faster than Slim.
http://forum.xda-developers.com/showthread.php?t=1783064.
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Update:
1. Market issue resolved after about 36 hours of following the fix on the website.
2. Internal card and sdcard were reversed, (/sdcard and /emmc)
Conclusion
I hope my journey helps someone out there.

patrokov said:
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Click to expand...
Click to collapse
Apps still aren't showing up in the market, but the TiBu restored apps work fine.

patrokov said:
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Click to expand...
Click to collapse
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.

Ravenmtx said:
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.
Click to expand...
Click to collapse
Which modem did you end up flashing?

CM 10 Issues:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Click to expand...
Click to collapse
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER

CheesyNutz said:
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER
Click to expand...
Click to collapse
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.

patrokov said:
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.
Click to expand...
Click to collapse
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.

patrokov said:
Which modem did you end up flashing?
Click to expand...
Click to collapse
I tried most of them. I live in the Washington DC area and I found the latest XXJVU worked best for me. You'll just have to find out which one works best for you.

takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)

takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
Exactly
Sent from my SGH-I897 using Tapatalk 2

CheesyNutz said:
Exactly
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
This is what I originally flashed and had all the issues with. Is this the wrong one?
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/v8/
Tonight I flashed this one, and everything works perfectly.
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/20120729/
The reason I ask is that I'm trying to find out whether it was my error or some weirdness on my cappy's part.

patrokov said:
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)
Click to expand...
Click to collapse
I don't personally recommend that page because it was not actually tested yet by porters it means that the file in that site was raw JB. Recently derteufel uploaded a version that is "busted". So I would suggest to pay a visit to the HellBean thread and test a version that has already ported.

I just installed the stable CM9 and I don't really like what I am seeing. The lag on the home screen is unbearable and sometimes the notification bar splits into two when I am pulling it down. I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.

droyd666 said:
I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.
Click to expand...
Click to collapse
I'd definitely recommend Helly Bean first, in that case.

helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.

I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2

Definitely Helly Bean. Make sure to do a solid master clear and format of your phone first, then flash the latest helly bean. Long time user of slimics then slimbean and just switched over.
Only jellybean rom I've found that works FAST right out of the box, and even better when changing a few settings with devil kernel config. Only rom in which devil config settings actually stick after reboot as well!

VashTS said:
helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.
Click to expand...
Click to collapse
Not if you flash the add-on like you are supposed to...
Sent from a jelly bean

So far the latest cm9 nightly is the only ics that has worked well for me. All the jb roms I tried have me a lot of issues (sd card switch, no modem-couldn't even flash a modem, etc) so I haven't built up the confidence to try again.
My problems aren't with ROM behavior, but rather the newer versions of system apps. The phone app on gb had a feature at the end of a phone call to redial or text the person you just called. Miss that. Also the clock app doesn't have the world clock. Not a fan of that one. Over all everything is smooth but a lot of features I had with apex 12 are greatly missed.
Sent from my SGH-I897 using xda premium

simple man said:
I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
I also applaud jellybro on my phone and flash each day with new builds as they come. Remeber to have a quick read thro the cherry picks to see what was changed/added/fixed. Runs great!
I do use the devil kernel with it tho - http://rootaxbox.no-ip.org/derteufel/jellybean/Cappy/113/. I use the CMC one.
Matt/eg.

[Q] GS3 Running CM10 Keeps Force Rebooting

Hey so when I update my phone from a nightly from August to a nightly in September I keep on getting random force reboots. I managed to flash to the experimental M1 nightly and i'm stable there, but anything past that and I get force reboots (my phone randomly shuts off).
Any help would be greatly appreciated! Thanks!

Are you sure it is due to CM? I have the same issue with the stock Rom rooted.

Well it only happens on any nightly past the experimental M1.

Have you tried a clean flash? Or have you just been doing dirty flashes over and over?

Yeah, I tried a full wipe then install last night.. didn't get a force reboot for about an hour but then after that it went back to "normal" and happened like every five minutes.

Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks

kevin2005 said:
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
Click to expand...
Click to collapse
Same here I had tested e different rom and mostly reliable I found was DarthStaker v7. But looks like samsung did something with the new s3 hardware because before my phone replacement my first s3 was smooth as a butter with any rom but now is a pita toget it shorted out with new rom. Stock+root works way better that any rom.
Sent from my SGH-T999 using xda premium

S3 rom wifi issue help please

hey im new to the forum and i rooted my s3 and have the r420 senergy rom installed but the wifi dooesnt work! uhhhhh i cant post in the development section till i have 10 posts. so any one who can help that would be great. ive been doing a lot of reading and what is the differnce between nightly and and regular roms? and i read that the wifi wont work on the nightly rom with out a kernel flash?>?>? Is this right? im going to try the v1.6 senergy any way .....my model is the i535 but yall probably already know that because you hacked my ip address and seen my phone plugged in J/K ha thanks in advance

First off, Synergy r433 is the latest version. And a new release is scheduled to drop any minute now.
A nightly is an experimental build that gets updated nightly. Whereas a stable build is less frequent but as the name suggests is stable. Nightly you must really know what you're doing and are be okay with occasional bugs, otherwise use the stable releases. (fyi SynergyROM stopped releasing nightlies)
As for your Wifi problem, reflash but the make sure you do a full factory reset, and then a super wipe within the AROMA installer. *This will wipe internal storage, make sure to have the ROM zip on external storage* Wifi is not bugged, I'm suggesting the was a flashing error.
Sent via SGS3 using Tapatalk

Thank you so much for replying. i was thinking the same about the nightly "name" but thanks for clarifying. i have tried several times. in clockworkmod recovery(or whatever the name is) i factory reset and in the installer i wipe everything. (on the internal sd) and then install cleanly. but my kernel doesnt flashed it says its not unlocked.?!?! how do i unock it? i unlocked the bootloader and once more so i knew for sure. and my phone says custom with a padlock unlocked symbol below. but same thing everytime...wifi is buggy. i like this rom and just want it to work...thanks!!!!!!!!!!!!! is there a special "better" kernel unlock method? my paitients are getting low...lol well my girl wants her phone stock ...F**CK THATT!!!!!!!!!! thanks man

Bump please someone plesase help.. I need this phone working asap

Check out this link
seems to work for some.
http://forum.xda-developers.com/showthread.php?p=40531554
Mine has always been good.
I also use an app called Opensignal
https://play.google.com/store/apps/details?id=com.staircase3.opensignal
When on the OpenSignal app select > wifi then select the > refresh then the > refresh network.
I do this every week or so. I have no issues with wifi, ever.
Some say tightening the screws
help check out rhe link below
http://gs3.wonderhowto.com/how-to/s...-gps-problems-your-samsung-galaxy-s3-0145332/
I hear it's just some phones. Anyways
good luck
Sent from my Smoking smooth
Synergy r484
Mods by gunthermic,
Theme by jbeitel

I am experiencing the same issue.
I rooted, flashed CWO, and then installed synergy. Nothing worked... then I read that you need to unlock the bootrom so I did that, rebooted and got the same... no wifi. After unlocking the bootloader I reinstalled synergy (R484) and still WiFi will not turn on.
I followed they synergy thread for flashing and This thread for bootloader unlocks.
Provider: Verizon
Phone: GS3
ROM: SynergyROM (r484)
Recovery: ClockworkOrange

Got it fixed!
So... I only used odin... no romloader apps or any of that crap...
1: Reinstalled stock ROM
2: Reinstalled CWO
3: Reinstalled Root+Bootloader
4: Reinstalled SynergyROM
5: Enjoy! Wifi works, all applications work!
Chris

[Q] Strange Rom Issues

Alrighty, this is one of the weirdest things I've had happen with a phone since I started doing this on the original Droid. Lately I've been using Jellybeans Rom, its been great and my longest running ROM so far, but like a lot of people here I have to try out new stuff quite often just to try it. Well anymore I cant seem to try much else, I wanted to run the newest Liquid Smooth 2.3 ROM that just hit and it wont work at all really, before I redid the whole phone every time I flashed LS 2.3 I couldnt even hit the start button when the ROM first installed, when I did it wouldnt do anything and then the screen would go black and I would have to hard reset or battery pull. Next boot up seemed to go fine, got my gmail up and running and titanium downloaded and then after that, hitting settings options would lock up the phone in just about any app I had, never even got around to trying to restore anything with titanium.
Re-flashed LS 2.3 three or four times and nothing changed, tried fixing permissions, fully wiping, etc. didnt matter. So naturally I figured it was simply the ROM on my phone (mind you LS 2.2 worked fine before) so I went and decided I would try out Avatar ROM, CM based with MIUI themes, this ROM did pretty much the same thing. No idea why...
Next I figured something maybe was wrong with my phone so I went back to the drawing board and started from factory with ODIN, I redid my ROM with stock/root, unlocked the boot loader again and redid custom recovery and all the same thing with LS 2.3 happened all over again, Stock ROM worked great for the bit of time I used it before I tried to reflash LS 2.3 again, Now I'm back running Jellybeans v.15 and it runs perfectly fine as well.
I really have no idea what the problem is, both of those ROMs I've tried are CM based original development, so I'm wondering if its something in there thats causing an issue over the TW ROMs I've used. I've used other TW ROMs with decent success, but I've had some issues with those too that you wouldnt think should happen but it wasnt anything worth noting, just like Jellybeans the best, but even some of those would give me slow down problems and occasional lock ups when Jellybeans doesnt.
Anyone have any clue as to what could be causing this? I used to be able to run non TW roms just fine and its only been in the past month that this has started happening that I've noticed, I've had the phone since January and have been flashing away this whole time and now I cant seem to try out any more ROMs without having major issues......ugh

Your situation is a very random situation but I have something similar happened to me involving TW ROMs in that some of them froze on me. I had to flash the stock ROM.

Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium

Vidfreek said:
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you've only had these issues in the last month, it could be attributed to the Linux 3.4 kernel that every AOSP rom has moved to. I wouldn't let that stop you though. Are you downloading these rom zips over WiFi or mobile data? Were your downloads taking awhile as well? I know either GOO or AFH was having server issues recently which may have coincided with your downloads. I'd suggest using WiFi if you aren't already and trying again?
Sent from my SCH-I535 using xda app-developers app

Yeah its only been fairly recent and all roms I've tried have been updated since the very end of april, if my phone has major problems with that linux kernal am I going to be able to flash anything again? Everything I downloaded was over wifi but I can try all the downloads again but I'm thinking that won't fix anything, just weird stuff
Sent from my SCH-I535 using xda premium

[Q] SMS won't send. Can receive/send MMS calls and Data

The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.

This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already

It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899

Just looking for more info
Sent from my SCH-I535 using Tapatalk

Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.

I'm 717
Sent from my SCH-I535 using Tapatalk

I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.

I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk

Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658

DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.

Anyone try aosp to see if fixed yet?

Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.

capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...

What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app

capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app

I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.

capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.

I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.

Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,

Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.