Related
Hi Peeps,
For some strange reason my SGS has decided to stop sending sms. After hitting send the messages just get stuck on "sending"
I have checked the message centre number and the mms setting just in case. I have tried the sim in an old nokia and it texts just fine.
It was having intermittent issues with sms around a week ago, where it wouldnt send a message, so i would send the same one again and then both would send simultaneously. However now its not sending at all.
I am running Froyo.xwjp6 with kernel 2.6.32.9.
I have also tried instaling Handcent SMS but i just get the error "message not sent"
Thoughts on a postcard?
Same here, although trying handcent has allowed me to send, but strangely, will intermittently fail, im sure its a froyo bug.
tommyturbo said:
Same here, although trying handcent has allowed me to send, but strangely, will intermittently fail, im sure its a froyo bug.
Click to expand...
Click to collapse
I managed to fix it. Couldn't be bothered with trying to reflash the modem or even the os, so tried the Privacy-return to factory settings option just out of curiosity. Can't figure out what it did exactly but when it rebooted i had not lost any settings or applications, and all my home screen app shortcuts were still there. The only discernable difference was the lack of gadgets on the home screen, which I had to reinstall.
The important thing however is that messaging worked again. God knows why.
One susipicion I have is that this is due to my usage of Titanium Backup. I installed it when i was running Eclair, and each time i upgrade the OS i use it to restore my old system data and apps. Perhaps some change between Eclair and Froyo's messaging settings is being overwritten by and older version by Titanium. I suspect this as following the above factory restore I tried a Titanium restore and instantly it broke my messaging again. So I did the factory again and got them back. There wasn't really any need to use Titanium as I said before I didn't seem to lose any setting or apps, but did it anyway out due to that old cat's friend curiosity
Give it a go if u dare and see what happens
Let me know how u get on...
Ok so im still having the same problem.is there really noone out there with an idea?
Sent from my GT-I9000 using XDA App
Hello all,
My, I have done a lot of posting today in regards to various problems associated with the above title!
Here's what my conundrum is... I have been flashing a bunch of different custom ROMs over the last month because, well, it is is quite addictive. Perception, Paragon, Phoenix, Cognition, Firefly Serendipity, you name it. Here's where it gets very very interesting. Once I have flashed ANY of the above ROMs, so anything NOT stock, I lose the ability to receive phonecalls. I never hear the phone ring, I never see a missed call, I never get a record of that call on my phone log. HOWEVER, I do receive voicemails and all that happens when someone calls me is I hear a beep on my phone and watch the phone signal disappear COMPLETELY. So, I know I have received a phonecall but I have no way of knowing who it was unless they leave a voice message.
Now, what I have done is flash back to stock before trying each custom ROM using Odin, master cleared, etc etc etc. Thank god for Titanium Backup.
Where this leaves me is the inability to run on anything but stock if I want to have a phone that receives any calls. I can root but I obviously cannot theme or flash custom ROMs, etc. Here are my APN settings if it makes any difference:
Name: Rogers
APN: rogers-core-appl1.apn
MMSC: ://mms.gprs.rogers "add a http at beginning and a dot com at the end"
MMS Proxy: 10.128.1.69
MMS Port: 80
MCC: 302
MNC: 720
Everything else blank
Any ideas? It is quite perplexing indeed and the inability to customize as I see fit kind of defeats the Android purpose.
Thanks!
Make sure you are not restoring system data with titanium, only missing apps with data. I had that problem and that's what it was. It causes problems with different roms.
Sent from my SGH-I897 using XDA Premium App
jferg5 said:
Make sure you are not restoring system data with titanium, only missing apps with data. I had that problem and that's what it was. It causes problems with different roms.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the idea! I'm going it a show right now. Although, interestingly, I am running stock rooted and I used TB to restore system settings. Phone did not work and everytime I tried to receive a call same problem of dropped signal followed by Dialer crashing completely. I'll let you know once I try your strategy.
jferg5 said:
Make sure you are not restoring system data with titanium, only missing apps with data. I had that problem and that's what it was. It causes problems with different roms.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Wait...
Your usually suppose to NOT restore system data...
Btw since your Rogers you have to reenter all of the things when you reflash.
Because everyone else is on Att
@jferg5: No luck. Reflashed Serendipity 5.12, used TB to restore apps and data but NOT system data. This was all after an Odin Master Clear, reflash to stock, reflash to Serendipity 5.12. No luck, phone still crashes disastarously anytime someone tries to call in.
@comdei: Yeah, I have to manually reenter all the APN data each time I reflash. Kind of annoying to be honest. Haven't been restoring any data, just apps and their data.
Any other ideas anyone? I'm seriously baffled, frustrated and a touch of depressed by now. I was looking forward to Android so bad simply so I could customize it however I wanted. Alas.
Ive been running serendipity 6.4 for a few days now and love it.
Everything works great except when someone tries to call me I get a weird audio tone and then the person calling me gets forced to voicemail after one ring.
And on my end I never even see the call coming through, am thinking of flashing cognition if I cant get this resolved....
Any ideas?
deezdrama said:
Ive been running serendipity 6.4 for a few days now and love it.
Everything works great except when someone tries to call me I get a weird audio tone and then the person calling me gets forced to voicemail after one ring.
And on my end I never even see the call coming through, am thinking of flashing cognition if I cant get this resolved....
Any ideas?
Click to expand...
Click to collapse
Bad flash or you restored apps and system data. Never heard of that on 6.4.
Sent from my Samsung Captivate using Tapatalk
Yeah, I've been having a similar problem. When somebody calls me, my phone rings once or twice, then the signal inexplicably disappears. The caller gets some att message that the network is down, but I never had this problem before.
yeah it's a common occurrence if you restored system data
so when i did my titanium backup i should of just restored user apps but nothing else??
So is there any way to fix other than reflashing?
deezdrama said:
so when i did my titanium backup i should of just restored user apps but nothing else??
So is there any way to fix other than reflashing?
Click to expand...
Click to collapse
Missing apps+data only.
Reflash. Sorry.
Sent from my Samsung Captivate using Tapatalk
hmmm... I followed a vid on flashin cognition to a tee.
It was a 3 part video...cant find the link right now,
but several ppl said to follow it exactlly for flashing cog or serendipity, and in the vid im sure the guy said to restore all user apps and data which is what i did...
so next time just do missing apps and data?
I think i might just reflash and not restore anything backed up, if i dont restore backup files whats the worse that could happen? just have to setup apn,widgets,contacts and apps n crap again? or is it a step i must do?
just want to be able to receive calls again and not screw it up the second time, other than the one ring then dropped calls everything works great
Can I restore my contacts? I'd hate to have to find all those phone numbers and type them in again.
rabinabo said:
Can I restore my contacts? I'd hate to have to find all those phone numbers and type them in again.
Click to expand...
Click to collapse
Sync to google, then re-sync when you flash.
i reflashed serendipity and this time only used titanium backup for missing apps and data and my calls are now working fine.....
My contacts are gone tho, and i dont have them setup in google to sync with, is there a contacts file in titanium that i could restore???
thanks
deezdrama said:
i reflashed serendipity and this time only used titanium backup for missing apps and data and my calls are now working fine.....
My contacts are gone tho, and i dont have them setup in google to sync with, is there a contacts file in titanium that i could restore???
thanks
Click to expand...
Click to collapse
Ive never once had a problem with restoring contacts, just go into titanium, find contacts in the list and hit restore
should be called [CONTACTS/CALL STORAGE], just restore that part and all should be fine
Thanks, I synced my contacts from Google, and everything was fine. Now, for some reason, contacts crashes whenever I try to open it, and I get "android.process.acore stopped unexpectedly".
Hi, having SMS issue with my SGS on Remics-JB 3.0.1 - I receive no SMS. When I put SIM in another phone SMS are finally received. Sending SMS is OK, i can send messages and they are delivered to addressee so it is not problem with SMSC. Only no SMS are delivered to my SGS although I test sending from web or another phone. I had this issue with all ICS and JB roms I tested, sometimes after flash it was all right and problem started later and sometimes the issue appeared right after flash. Got back GB and it was fine but now I tested JB again and the issue is still here, although I did all wipes and clears before and after flash, had made no restore via TB or Go backup. I am getting really anoyed from this, tried another SMS app and no result. Could you advise me what will help, I had an idea to try another modem but dont know which
Really weird issue :what:
Is your IMEI ok?
Sent from my GT-I9000 using Tapatalk 2
amerkiller1995 said:
Really weird issue :what:
Is your IMEI ok?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I think so, in phone menu it is displayed, cant compare it now with box cause I am not at home. Flashing GB or Froyo resolves it and phone calls, logging in mobile network is OK.
Edit: Mean on ICS/JB phone calls and mobile network works, SMS sending works, SMS receiving NOT work.
On older android works everything.
daznael said:
I think so, in phone menu it is displayed, cant compare it now with box cause I am not at home. Flashing GB or Froyo resolves it and phone calls, logging in mobile network is OK.
Edit: Mean on ICS/JB phone calls and mobile network works, SMS sending works, SMS receiving NOT work.
On older android works everything.
Click to expand...
Click to collapse
check IF your phone number is listed in menu>settings>about phone>status or read this
xsenman said:
check IF your phone number is listed in menu>settings>about phone>status or read this
Click to expand...
Click to collapse
Yes its listed correctly
daznael said:
Yes its listed correctly
Click to expand...
Click to collapse
its odd, looks like you have something installed to block out sms reception like this maybe ...which I doubt
IMEI does match with the one on the box. I use Root call blocker pro (some older version), SMS blocking is off but will try delete it and test if there isnt some bug, after that I will let know. Although it is essential app for me because of my work Dont know about another one like that which is function and reliable
Sent from my GT-I9000 using xda app-developers app
xsenman said:
its odd, looks like you have something installed to block out sms reception like this maybe ...which I doubt
Click to expand...
Click to collapse
So.. deleted Root call blocker pro, wiped cache, dalvik, fixed permission and.. OK It was some incompatibility of older version with JB.
Do you know some other call blocking app, which is reliable and blocks calls before phone start to ring? So caller wont hear ringing tone but "not aviable" or "busy" tone?
daznael said:
So.. deleted Root call blocker pro, wiped cache, dalvik, fixed permission and.. OK It was some incompatibility of older version with JB.
Do you know some other call blocking app, which is reliable and blocks calls before phone start to ring? So caller wont hear ringing tone but "not aviable" or "busy" tone?
Click to expand...
Click to collapse
good you found the culprit, not too sure about other apps, but google is your best friend and helper, try it and you might get something that suits you
I have an XT1060 (Verizon) Moto X, unlocked and rooted with TWRP/SuperSU.
I need to restore my texts from a nandroid that was created while I was on 4.4.2. I am now on 4.4.4. I have Titanium B/U PRO and used it to restore the texts by:
1) Checking Migrate System Data in preferences; and
2) Extracting Data Only from Phone/Messanging Storage.
I did this b/c I read on other forums here on XDA that is what I need to do. However, when I do that I can't receive text messages any longer. I can send them but none get through to me.
One other thing - when I extract the texts from my 4.4.2 nandroid, they all show up fine and I can send and receive text but Titanium B/U says to reboot to complete the process. Once I reboot, that is when I can no longer receive texts.
Seems to me like even though I check data only, Titanium B/U is messing with the messaging app.
Any help would be appreciated!!!!!!
Ok so I returned back to the 4.4.2 system using my nandroid and all my texts are there but I don't see how to back them up using Titanium B/U. I was thinking I could do that and maybe restoring texts from a Titanium B/U instead of a nandroid would work better?
I eventually figured out how to make the Titanium B/U and did that while I was on 4.4.2. Then I restored from my 4.4.4 nandroid using TWRP and tried to restore just the Phone/Messaging Storage (data only) from my 4.4.2 Titanium B/U. The texts restored, but again, I can send texts but not receive them.
Can anyone help me with this or point me to a forum where I may be able to get help?
- maybe try solution here: http://android.stackexchange.com/qu...ssages-everything-else-about-phone-works-fine (plug sim in another phone, use texts, plug it back in this phone)
- experiment more. try backing up and restoring both app and data. try clearing app data before restoring stuff. you say everything works fine just before rebooting, maybe do another TB backup before rebooting (but after the first restore) and then restore this second backup after the restart. etc.
dtg7 said:
- maybe try solution here: http://android.stackexchange.com/qu...ssages-everything-else-about-phone-works-fine (plug sim in another phone, use texts, plug it back in this phone)
Click to expand...
Click to collapse
Thanks, I will try that and report back.
dtg7 said:
- experiment more. try backing up and restoring both app and data. try clearing app data before restoring stuff. you say everything works fine just before rebooting, maybe do another TB backup before rebooting (but after the first restore) and then restore this second backup after the restart. etc.
Click to expand...
Click to collapse
Good idea! Thanks for the suggestions, I will report back on what works.
UPDATE:
I returned to my 4.4.2 nandroid, disabled the Xposed Installer, flashed the stock recovery, unfroze all of the apps I had frozen, including Motorola OTA, and unrooted. Then I took the 4.4.4 OTA again and had all of my texts, woot!!
HOWEVER, I still can't receive texts!!!!!! I found this thread on AC and it seems like others have this problem too after taking the 4.4.4 OTA. Drats. At least now I know it isn't TiBU.
What could possibly be causing someone not to receive texts but able to send texts?!?!?!?!?!
dtg7 said:
- maybe try solution here: http://android.stackexchange.com/qu...ssages-everything-else-about-phone-works-fine (plug sim in another phone, use texts, plug it back in this phone)
Click to expand...
Click to collapse
Tried that after I took the OTA a second time and it didn't work :crying:
Wansanta said:
UPDATE:
I returned to my 4.4.2 nandroid, disabled the Xposed Installer, flashed the stock recovery, unfroze all of the apps I had frozen, including Motorola OTA, and unrooted. Then I took the 4.4.4 OTA again and had all of my texts, woot!!
HOWEVER, I still can't receive texts!!!!!! I found this thread on AC and it seems like others have this problem too after taking the 4.4.4 OTA. Drats. At least now I know it isn't TiBU.
What could possibly be causing someone not to receive texts but able to send texts?!?!?!?!?!
Click to expand...
Click to collapse
previously only heard of not being able to send texts, and that's usually a wrong service center number setting. even then you could always receive. From the link you mentioned and from further googling it seems this issue is exclusive to Verizon (are you on Verizon?) and as I have the T-Mobile xt1053 on 4.4.4 I can report no such issues. This suggests a network incompatibility bug. The weird thing is it seems that doing a factory data reset restores full SMS functionality for a while, until it stops suddenly. To me seems something to investigate.
Q: What happens if you use Hangouts as your SMS app? worth a try. if that doesn't work and you are on Verizon then as I see it your choices are:
- stick with 4.4.4 and investigate til the next update is released. L should be coming soon. To investigate you'll probably need root back.
- revert back to 4.4.2 and wait for L. BUT tread with caution here. I've read your other posts where you claim no problems nandroiding back and forth. just be sure the conditions are still the same.
dtg7 said:
are you on Verizon?
Click to expand...
Click to collapse
Yes, I am on Verizon.
dtg7 said:
This suggests a network incompatibility bug. The weird thing is it seems that doing a factory data reset restores full SMS functionality for a while, until it stops suddenly. To me seems something to investigate.
Click to expand...
Click to collapse
I don't suddenly stop receiving texts. I receive text fine until I try to restore my texts from a nandroid or titanium backup - then I stop receiving texts. If I restore the texts from an SMS Backup and Restore xml, then I never lose the ability to receive texts.
So it seems to me that whatever TiBU is restoring is more than just the texts. In the TiBU listing, what I am restoring is labeled as Phone/Messaging Storage (SMS/MMS/APN). I select data only as opposed to app + data and then in preferences I checked Migrate System Data, which I read on XDA and the TiBU site needs to be checked if you are restoring from an earlier version of the OS, which I am. From all I have read, APNs should only affect the ability to send MMS, not SMS, but I lose the ability to receive any texts at all when I restore my texts from the nandroid or TiBU. I will try next to select app + data and see what happens.
Also when I downgraded back to my 4.4.2 nandroid and then retook the 4.4.4 OTA, I never had the ability to receive texts. I will do that again and this time do a factory reset to see if I regain the ability to receive texts, which I should. Before I retook the 4.4.4 OTA what I was doing was switching b/t a 4.4.2 nandroid and a 4.4.4 nandroid.
Do you know the difference b/t upgrading via the OTA and upgrading via the Motorola Device Manager? IIRC the former is a patch and the latter is more like RSDLite? I think I will try the MDM next time I downgrade to 4.4.2.
dtg7 said:
Q: What happens if you use Hangouts as your SMS app? worth a try.
Click to expand...
Click to collapse
Still can't receive texts
dtg7 said:
if that doesn't work and you are on Verizon then as I see it your choices are:
- stick with 4.4.4 and investigate til the next update is released. L should be coming soon. To investigate you'll probably need root back.
Click to expand...
Click to collapse
I would be fine with not restoring my texts if there were some way to merge all of my texts. The problem with having multiple texts backups is that I can't go back to a text from an earlier version of android without backing up, restoring the old version, then restoring the newest version again.
IIRC, motorola migrate is the only way to merge texts but I need a 2nd motorola device to do it. I hope Verizon gets the Motorola Nexus and then I will have a 2nd Motorola device.
dtg7 said:
- revert back to 4.4.2 and wait for L. BUT tread with caution here. I've read your other posts where you claim no problems nandroiding back and forth. just be sure the conditions are still the same.
Click to expand...
Click to collapse
Thanks for all of your suggestions!
After I eventually give up on trying to restore my texts from 4.4.2, I will make screen shots of my downgrades. IME, Q9Nap has been correct 100% of the time. I think the reason the myth about unlocked bootloaders bricking when downgrading their systems became accepted as truth around here is b/c people were trying to downgrade their partition tables as well as their systems. Trying to downgrade your partition table will result in a blank screen on boot into system. You can recover from this, though and it doesn't brick your device. I think people would see the blank screen and not know how to get into bootloader mode and think they bricked.
dtg7 said:
The weird thing is it seems that doing a factory data reset restores full SMS functionality for a while, until it stops suddenly. To me seems something to investigate.
Click to expand...
Click to collapse
So I downgraded again to my 4.4.2 nandroid and took the 4.4.4 OTA again. Then restored my texts from my 4.4.2 nandroid and same problem. Then I did a factory reset and problem went away, but so did my texts (of course).
The problem - i.e., I can send but not receive texts - is the same whether I am using the native messaging app or hangouts. The one thing that will cure the problem is to wipe the data from the Phone/Messaging Storage, which of course wipes out all of my texts. So the source of the problem, whatever it is, is in the data that TiBU restores to my phone.
However, when I restore the texts from SMS Backup and Restore, I don't get the problem so whatever is causing the problem it is specific to using TiBU to restore my texts. SMSB/U&R though, not only can't restore all of my texts, it leaves some of them looking like they have the wrong date.
I think for now what I am going to do is wait until I get a 2nd Motorola device and then I will see if I can do a merge using Motorola Migrate.
My latest attempt was to downgrade back to 4.4.2 and upgraded every single app that wasn't on the latest version as well as installing the latest version of Hangouts and Google Voice. I consistently could send and receive texts using both the native messaging app and hangouts. And I could make calls using the native dialer, hangouts and google voice.
Then I made a nandroid, flashed stock recovery, unrooted and took the 4.4.4 OTA again. Still the same problem - I can make/receive calls and send texts, but I can't receive texts!!!!!
I am sure if I root and then wipe the texts from the Phone/Messaging Storage using TiBU the problem will be gone, but so will my texts!!!! Sigh.
Oh, and I just figured out that I am not getting my voicemail indicators on the status bar either!!
Edited - And when I dial my GV number, instead of routing it to Hangouts, the call gets routed to my Verizon number. Is that supposed to happen?
Wansanta said:
What could possibly be causing someone not to receive texts but able to send texts?!?!?!?!?!
Click to expand...
Click to collapse
That is the key question though, isn't it, and I couldn't help going back to it. I was thinking, what if it's being caused by something as idiotic as memory management. The only (simple) reason a phone would refuse to accept an SMS would be if it thought it didn't have enough space to accept it. This should never happen since SMS are so small, but googling my hunch I did find that there is a precedent for such a thing, although it was a few years ago ( https://code.google.com/p/android/issues/detail?id=4991 ). Maybe it's reared it's ugly head again with the 4.4.4 update for you guys on Verizon.
Here's how you can test this theory. While on 4.4.4 after you do the TiBU restore of all your SMS exactly like you've done many times so far, this time don't clear app data or anything but instead just go to the Messaging app and select the option to delete all threads. This should just delete the SMSs themselves while leaving other files system or otherwise untouched. Then try sending yourself a text.
If that doesn't work you can also try uninstalling some apps to clear space.
dtg7 said:
That is the key question though, isn't it, and I couldn't help going back to it. I was thinking, what if it's being caused by something as idiotic as memory management. The only (simple) reason a phone would refuse to accept an SMS would be if it thought it didn't have enough space to accept it. This should never happen since SMS are so small, but googling my hunch I did find that there is a precedent for such a thing, although it was a few years ago ( https://code.google.com/p/android/issues/detail?id=4991 ). Maybe it's reared it's ugly head again with the 4.4.4 update for you guys on Verizon.
Click to expand...
Click to collapse
First, thanks for your help again.
I am not clear what you mean by memory - do you mean RAM or internal storage? With computers, it is clear to me that memory = RAM but when it comes to cell phones, many people use memory to mean internal storage, which is equivalent to the hard drive of a computer.
Prior to restoring my old texts, I have close to 24GB of free internal storage. When I restore my old texts using TiBU, I have 17.1GB of free internal storage. TiBU says to reboot after I restore my old texts. Prior to rebooting, I can receive texts fine. After rebooting, I show 17GB of free internal storage, but cannot receive texts.
When I delete all of the threads, my free internal storage returns to 17.1GB, but I still can't receive texts. Then upon reboot, my free internal storage remains at 17.1GB and I still cannot receive texts.
When I go to settings, apps, messaging app and clear data and clear cache, still 17.1GB of free internal storage and can't receive texts. When I go into TiBU and wipe data from Phone/Messaging Storage, same thing. Upon reboot, still only 17.1GB of free internal storage but I can receive texts!!!!
Also, when I restore my texts using SMS Backup and Restore, I am able to receive texts but the texts do not restore fully.
If by memory you mean RAM, I know how to check the RAM available on my Windows PC, but idk how to check that for an android system.
Who at google would I report my problem to? They may not care if it doesn't affect Android L but it is still worth reporting IMO.
Yeah I was referring to internal storage not RAM. Of all the complaints in that link only one suggests having free storage in GB, most were around 20 MB. Despite the difference you saw between TiBU and SMS Backup, the peculiarity of not being able to receive texts had me convinced your issue was similar to all those people in that link.
if you want to continue this path of attack I'd suggest two more things. in the messaging app settings there is option to manage SIM messages. If you have anything in there you could try deleting them. Also maybe voicemail is in on it too, so you could try trimming that.
As for the TiBU/SMS Backup discrepancy, my original suggestion before all this storage talk was going to ask if you'd tried Not selecting the option to Migrate System Data in TiBU. if not, you could try that. system data can be finicky when restoring.
Aside from these things i'm at a loss at what else it could be. Sorry couldn't be more help. I wish some of the people complaining at the Verizon website could jump over here and share their experiences of what they've tried. There's quite of a few there https://community.verizonwireless.com/thread/832346?forceNoRedirect=true
dtg7 said:
Yeah I was referring to internal storage not RAM. Of all the complaints in that link only one suggests having free storage in GB, most were around 20 MB.
Click to expand...
Click to collapse
Right but did you see that even when I deleted the texts and wiped the data from the text messaging app it did not restore my free internal storage to 24GB - it remained at 17.1GB. It should have gone back to 24 GB since that is what it was before I restored my texts.
dtg7 said:
Despite the difference you saw between TiBU and SMS Backup, the peculiarity of not being able to receive texts had me convinced your issue was similar to all those people in that link.
if you want to continue this path of attack I'd suggest two more things. in the messaging app settings there is option to manage SIM messages. If you have anything in there you could try deleting them. Also maybe voicemail is in on it too, so you could try trimming that.
Click to expand...
Click to collapse
Says no SIM card messages.
dtg7 said:
As for the TiBU/SMS Backup discrepancy, my original suggestion before all this storage talk was going to ask if you'd tried Not selecting the option to Migrate System Data in TiBU. if not, you could try that. system data can be finicky when restoring.
Click to expand...
Click to collapse
Will do.
dtg7 said:
Aside from these things i'm at a loss at what else it could be. Sorry couldn't be more help. I wish some of the people complaining at the Verizon website could jump over here and share their experiences of what they've tried. There's quite of a few there https://community.verizonwireless.com/thread/832346?forceNoRedirect=true
Click to expand...
Click to collapse
Thanks - I will register over there and point them over here!!
Wansanta said:
Prior to restoring my old texts, I have close to 24GB of free internal storage. When I restore my old texts using TiBU, I have 17.1GB of free internal storage. TiBU says to reboot after I restore my old texts. Prior to rebooting, I can receive texts fine. After rebooting, I show 17GB of free internal storage, but cannot receive texts.
When I delete all of the threads, my free internal storage returns to 17.1GB, but I still can't receive texts. Then upon reboot, my free internal storage remains at 17.1GB and I still cannot receive texts.
When I go to settings, apps, messaging app and clear data and clear cache, still 17.1GB of free internal storage and can't receive texts. When I go into TiBU and wipe data from Phone/Messaging Storage, same thing. Upon reboot, still only 17.1GB of free internal storage but I can receive texts!!!!
Click to expand...
Click to collapse
I wiped cache and dalvik cache and the free internal storage went to 17.2GB. Then I did a factory reset and it went to 17.8GB, which I found strange since it should go back to 24GB.
I am going back to the 4.4.2 nandroid and will double check that what I posted before was correct.