I was on a rooted Epic 4g EI22 and it worked well. Received the OTA EL30 update a few days ago, wouldn't install due to being rooted. Returned phone to stock EI22, did the EL30 update, then rooted the EL30. Phone works fine for the most part in the short time it's been on EL30.
The problem I experience is after choosing either 'sender' or 'all' when you choose to reply to an e-mail, the phone returns back to the mail inbox and I am unable to reply to e-mails. Has anyone else experienced this or have a solution to it?
With EL30 I also experienced a problem with not being able to answer incoming calls (could hear ringer) but no visible notification other than a force close button for the phone would appear. Quickly found a remedy on here which was to reduce the quantity of 'Reject With Message' options to less than five in the call settings menu.
Did you restore data to get your account info back? Clear data in the emal app and re-enter your account info manually.
Sent from my SPH-D700 using XDA App
Through the update process I made my phone return to a 'stock' setting with none of my personal data or user installed apps on it (same condition as if the phone was just purchased from a store). After rooting the EL30 I used Titanium Backup to put all of the apps and data back onto the phone.
EDIT: I just tried the suggestion of removing the e-mail account from the phone and setting the same account up again on the phone. In doing this, the reply function seems to work as normal now. Thanks for the help.
SlobbaTech said:
Through the update process I made my phone return to a 'stock' setting with none of my personal data or user installed apps on it (same condition as if the phone was just purchased from a store). After rooting the EL30 I used Titanium Backup to put all of the apps and data back onto the phone.
EDIT: I just tried the suggestion of removing the e-mail account from the phone and setting the same account up again on the phone. In doing this, the reply function seems to work as normal now. Thanks for the help.
Click to expand...
Click to collapse
You restored system data with Titanium. Don't do that..lol.
Related
Ok i have searched and searched and searched some more and can not find an answer. Hopefully i am placing this in the correct place.
I am currently running Synergy. I am having issues with receiving and sending pictures via messaging app (stock and I've also tried Handcent). I guess I can't even say its an issue, it just does not flat out work. I can not send or receive pictures.
When I receive a picture message, it comes through with a click able download button. Click it, and nothing happens for a few minutes. Them shortly after, I receive a notification stating, "Message not downloaded, Generic network failure"
Pretty much same goes for when trying to send one. It attaches fine and compresses for MMS but then I get pretty much the same notification a few minutes later, "Unable to send message after multiple attempts, Generic network failure."
I have attempted numerous ways of fixing this to no avail. I tried turning off WiFi, that didn't work. Re-flashed Rom, no go. I was thinking perhaps I need to update radios, pri,prl ect? I am trying to avoid a hard reset as i don't want to lose root. Any ideas on a fix?
I recently had this problem too. I found the fix here on the forum. If you have titanium back up you need to start it up. Click backup/restore then scroll down to [SMS/MMS PREFS] Messages 1.00. Click on that and then click wipe data. You will lose all your messages so back them up if you need them. Reboot your phone afterwards. This is what I did and it fixed this problem.
Sent from my PC36100 using XDA App
Thanks for the reply. That sure sounds like it would do the trick. I tried and it didn't work when I scroll down to mms preference in TB mine is 3.xxx (something) not 1.0 like you had said. Not sure what that's all about. I went ahead and cleared data anyway and rebooted. When I opened TB after restarting it still said I had 1 backup. So I'm thinking for some reason it didn't wipe it. Getting so frustrated.
Try this...post 5635, point number 4
http://forum.xda-developers.com/showthread.php?p=14607370#post14607370
TB seems to bring issues when restoring text messages from older versions of texting apps. The new stock version has a backup feature within...give it a shot and good luck!
Sorry it didn't work.
Sent from my PC36100 using XDA App
dpilcher said:
Try this...post 5635, point number 4
http://forum.xda-developers.com/showthread.php?p=14607370#post14607370
TB seems to bring issues when restoring text messages from older versions of texting apps. The new stock version has a backup feature within...give it a shot and good luck!
Click to expand...
Click to collapse
@Orion1222
I tried the same thing and it didn't work at first. When following the post I didn't see any SMS/MMS/APN dialer that the post mentioned. I didn't see it because TB said the apps were ordered by name, but the sms/mms pref and apn dialer don't follow that rule.
Carefully look through and find both of them, then wipe the data and follow the rest of the #4 in the post.
I hope that helps!
How do I get rid of that icon in my notification bar? Does anyone know which program causes it? I checked the settings for Handcent and ADW Launcher and I don't see anything about it there. Help please?
Running CM7.1.0_RC1 on HTC EVO 4G hardware version 002.
Getting Rid of the Phantom Voice Mail Icon (The one that shows up in the top left corner, NOT the text message issue.) Source
MAKE A NANDROID just in case, (though you may want to flash your preferred ROM from scratch)
Obtain/find/borrow/buy a second non-Android Sprint phone (old, new, ugly, doesn't matter but must have a clean ESN)
Take your EVO back to a stock rooted ROM such as RUU SuperSonic EvO 3.70.651.1 OTA - Stock - Sense or Version 4.12.651.1
Log on to mysprint.sprint.com (or call Sprint if you are more comfortable and have them do the following)
On the main page scroll down to your device
Select "Activate a new phone" from the "Manage my device" pulldown
Follow the instructions and activate the non-Android phone on your account (temporarily removing the EVO from your account)
Once the non-Android phone is activated, follow all the steps to activate your voice mail account.
Call your phone from a land line and leave yourself a message
Open voice mail on your old phone and delete the new message and any others. Check it thoroughly to ensure no messages are saved in VM.
Log back on to mysprint.sprint.com (or call Sprint back) and reactivate your EVO following steps 5-6 above
Once your EVO is reactivated it should automatically re-provision your VM account.
Follow the instructions to get your VM account setup again. If you get a "Data Call Failure: Error Code 67" message when you reactivate your Evo, you need to update your Profile
Boot into recovery (this would be a great time to update the radios, PRI and PRL and make sure you update your profile (see link in Post #1))
Wipe everything using both recovery and a FORMAT_ALL type zip of your choice (links in Post #1)
Flash the ROM of your choice (you can try a nandroid, but it may or may not work cleanly, YMMV)
Make sure to keep an eye on your bill after you do this fix as some have reported billing errors. A call to Sprint should clear things up.
There IS an easier fix, I'm just trying to find it....
Thanks for the reply, but it's actually not a VM icon. My VVM is working just fine.. It's an SMS icon. It comes up every single time I get a text message (saying "from: [phone number of person that texted me]") so basically I get two SMS notifications.
Clearing the mail or sms messaging app's cache may help in this matter. Rebooting into recovery and wiping the cache and dalvlik can also do wonders.
Posting & replying from my EVO 4G
My bad, I misread. If you're using handcent, go to stock messaging app and turn off notifications.
@HipKat - I've used Handcent for a while, so I always know to turn off the notifications on the stock messaging app. So yeah. the stock messaging app notifications are off. I know what the icon for that notification looks like anyway. This is different. Some other program is causing this. Thanks for the suggestion though.
@dougjamal - I actually recently re-flash CM7.1.0_RC1 on this phone, so I went through the process of clearing all the caches in the recovery. Also as I said in my reply to HipKat, this doesn't seem like a notification from the stock SMS app or the Handcent app, it's some other app doing this. Also it kinda seems to me from reading your reply that maybe you think that the icon on my notification bar is like stuck there. It's not. I can clear it with no problems. It just keeps coming back every time I get a text message. It basically acts as a duplicate notification of any SMS that I get, sort of like having my notifications on the stock messaging app turned on in addition to the Handcent notifications. But that's not the case. Like I said, I know what the stock messaging notifications look like. This is something different. Again, thank you for the suggestion but that's not it.
Here's some more info to see if maybe it juggles someone's memory so they can help me: The last time this happened to me I went roaming the internet until I found this post on some other Android forum and it turns out what was causing a notification like this one wasn't even a messaging app. It was a launcher/home replacement app of some kind, IIRC. This is why I mentioned in my first post that I went through my ADW Launcher settings and had no luck.
Do you guys have any other ideas by any chance? Thanks in advance.
Anyone got a solution for this? Still having this issue. :-\
This is what I did on MIUI
If you didn't make a Nandroid of your phone, Stock/Rooted, find on on here and flash it, after you make a nandroid of your current setup.
Once you're in Stock/Rooted, open market and make sure VVM is updated. Then d/l Titanium Backup and make a backup of VVM.
Now, nandroid back to MIUI, and extract the app from the Titanium .apk backup.
The actual name is com.coremobility.app.vnotes-6334abeb61350a3ac2629cb6dc18c56e.apk.gz
Unzip that and extract com.coremobility.app.vnotes-6334abeb61350a3ac2629cb6dc18c56e.apk to your sd card. Using Root Explorer, or whatever you use, install the apk.
Open TB, and restore data.
Open VVM, compose a message to yourself.
Done
Funny...
So what happens when you press the icon?
Sent by Supersonic!
@HipKat Don't you remember you already replied to this thread with that same message? It's not a VVM icon, my VVM is working fine. It's a SMS icon.
@imheroldman It asks me what messaging app I want to use, Messaging or Handcent. Whichever one you click just opens up that app and shows me the text message I just received.
Maybe check your running apps next time it comes up
Sent by Supersonic!
It was RedList. Thanks for the tip
Nice glad I could help!
Sent by Supersonic!
So i rooted my phone last night and before doing so i used sms backup restore to back up all my texts. Once i got rooted, i attempted to restore my SMS messages. The process got interrupted twice, then i ran it a third time and it finished when i woke up. After everything was said and done i wasn't able to open or delete any messages. Trying to open any thread caused my message app to freeze. i had 29000 messages. I use the stock ICS messaging app. Rooted with AOKP toro milestone 3
Anybody had issues like this? I'd really like to get my messages back! halp!
I had a similar issue when using CM7 on my OG Droid. I hadn't backed up my messages using any application so I manually moved the sqlite database from the nandroid backup I had made. Upon moving the messages Handsent stopped working completely and the default messaging app would 'freeze'.
My best guess at that time (I didn't research the issue at all, so if I'm wrong please correct me) was that the messages are indexed/cached in some form and when I moved the messages the index/cache did not come with it. IIRC the issue corrected itself after I left the messaging application open/idle for some time. This idle time would have allowed the messaging application to reindex/cache the messages and function as anticipated.
Again, this is complete conjecture so if I'm completely off base do not be surprised...
Cool thank you for the reply. What i think i am going to try is backup my ROM, then right before i go to bed i'll try to run the restore process again. I'm really hoping the whole issue is that i accidentally cancelled the process two times before. If this doesn't work i'll try opened the messaging app and letting it sit for a while to 'sync' or whatever it would be called.
Hello there,
I'm relatively new to XDA but I've heard that pretty much any problem can be solved through you guys. So here we go. I have an original HTC Incredible (hence the title) which is rooted and has the Android Business Gingersense 2.3.5 ROM installed. My problem is hard to explain, yet may be very simple. I simply cannot send or receive text messages to my knowledge.
So here are the details. Whenever I compose a text message in the native "Messages" app, I click send and the "Loading..." little window with the spinny circle pops up for a split second, disappears and nothing happens. It doesn't show me that the message was sent, nor does it give me an error message saying that it didn't send. Nothing. I have heard, however, from the people I sent the messages to that some of them did in fact go through, but I just didn't know they did cause it didn't show up on my screen. They also said they texted me back multiple times trying to get a hold of me to no avail, which is the other problem. I also cannot receive any messages. It may be that these issues are connected in some way but I am not sure.
Another problem. My native email app has the same sort of issue, only when I compose a message and hit send, it force closes the app saying, "an unexpected problem has occurred." Therefore I cannot send or receive emails as well. Quite inconvenient as many of you probably know.
One last issue involving the texting problem. May not have anything to do with the native sms app, but I believe there is still a possibility. I mainly text with Pinger's TextFree application, which not surprisingly has the same problem as the native app. Every time I try to send a message, NOTHING happens, yet I get reports from the people I "sent" the message to that they actually got the message and tried to get back up with me multiple times. Still, I didn't receive anything. But I did go on the web based version of the app and saw both of our messages between each other and the web app worked fine.
Any help at all is greatly appreciated and I hope I can get this resolved.
Thanks alot!
Almost sounds like a data/mms config problem. Are you able to receive any messages or emails at all?
Sent from my ADR6300 using xda premium
Well, the weird part is, it goes on and off... like one minute I could receive SMS and email another minute I'm back to where I've been
Sent from my Droid using xda premium
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
ousuxndallas said:
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
Click to expand...
Click to collapse
Have you tried a complete wipe and reflash?
Shano56 said:
Have you tried a complete wipe and reflash?
Click to expand...
Click to collapse
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
ousuxndallas said:
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
Click to expand...
Click to collapse
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Open the stock messaging app then hit menu - settings - connection settings, there will be 5 settings greyed out in there. What are the current settings for those 5?
Edit: Nevermind i forgot were talking about cm9, might not the same settings as sense. Better yet go to the market and download "apn backup and restore", do a backup and then go to the sdcard then the apn backup folder and then open the xml backup with a text editor and copy and paste its contents to here. You are on verizon correct?
Shano56 said:
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Click to expand...
Click to collapse
Radio: baseband version 2.15.00.07.28
ousuxndallas said:
Radio: baseband version 2.15.00.07.28
Click to expand...
Click to collapse
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Shano56 said:
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Click to expand...
Click to collapse
Okay, I think I have figured it out. Before I reflashed, I deleted my Google account. Then, reflashed C9 and when prompted on reboot to sign into Google, I clicked "later".
So, now I received several test text messages I had sent the past 2 days.
So far, so good.
Also, when I restore from Titanium, I am only going to restore Apps, but not the System Data.
I think Google is somehow interfering with things. Maybe something funky with how my Google Voice is interacting with my phone. Who knows. Anyway, I will be sure to report back here to help others that may have similar problems.
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
ousuxndallas said:
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
Click to expand...
Click to collapse
haha yes. its never a good idea to restore system data
Hester topeico
One more follow-up. I now Restored all data for the apps separately through Titanium.
Texting still works.
I think when I flashed the new C9 ROM, when I restored Apps+Data in Titanium, something got screwed up and thus the texting function got screwed up.
Now able to send SMS texts but NOT receive them
I'm reviving this thread.
I have checked out a few other threads, and this comes the closest to describing my issues with my rooted unlocked (SEC OFF) HTC Droid Incredible (version 1).
I did NOT change ROMs -- right after getting the DINC, I installed a rooted stock deodexed GB 2.3.4 ROM from DINC.DOES-IT.NET, and I have not touched the ROM since.
BTW, the ROM build is 4.06.605.3 CL 140944 release-keys
Ditto baseband radios, no change. Version: 2.15.10.07.07
I did recently update the kernel to a version of gingertiny that allows apps to record phone conversations without the speakerphone being turned on.
Old version: 2.6.35.14-gingertiny-v2+ Feb 2012
New Version: 2.6.35.14-gingertiny-v2 Nov 6 2012
It is POSSIBLE that the problems started with the change of kernel, because I don't use texting very much at all, but that was still a few weeks ago.
Based on what I have read on XDA, I went into Clockwork Mod 5.x Recovery, deleted and reformatted the data cache, and rebooted.
After that, I could SEND but NOT RECEIVE text SMS.
I had some doubts about whether all my calls were ringing through properly. I am still not entirely sure, but test calls from a landline and mobile phone did ring the phone, so maybe that is no longer (or maybe was not ever?) a problem.
I have seen suggestions to do everything from reinstalling ROM (being sure to restore only apps+data, NOT system data) to flashing a new radio to running *228 over-the-air update to manually upgrading the PRL list.
And then there is the question I have about the kernel change somehow being the culprit...
EDIT: One other thing I did right before changing the kernel was run Convert2Ext4 v2.0 using the "no data limit normal dalvik" version. My reason for running this was to get rid of the low memory/no memory warnings, lockups and crashes I was expriencing despite having over 300MB left out of 775MB on internal memory.
How should I go about trying to restore the ability to receive SMS without totally bricking or otherwise disrupting my DINC and causing more harm than good?
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Some more details
tiny4579 said:
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Click to expand...
Click to collapse
Thanks for having a look in, Tiny.
I use PagePlus running off VZW towers. PagePlus service rep sent me an SMS while I was in contact with her by phone, she said it got deducted from by cash balance. The only thing is, it did not actually reach my phone!
I have only used the stock SMS app until just yesterday, when I installed Handcent SMS. That did not help. Will uninstall, but I doubt that will make a difference.
Will go back to the old gingertiny kernel and see what that does, and report back here.
If that doesn't do it, maybe it's time for a Touch of Blue ROM, with which many seem to be doing so wiell...
i cant send my emails but i can receive them with no problems.
i tried logging out and relogging but still doesnt work.
tried on wifi and data
only started today and i have not done anything to the phone prior to this problem.
i am using stock touchwiz email app wicked rom.
help please?
bstylz911 said:
i cant send my emails but i can receive them with no problems.
i tried logging out and relogging but still doesnt work.
tried on wifi and data
only started today and i have not done anything to the phone prior to this problem.
i am using stock touchwiz email app wicked rom.
help please?
Click to expand...
Click to collapse
Check with your email provider to see if anything has changed. This happened to me not long ago and they had updated their security and I had to adjust a single setting to make it work again.
Alternatively, backup your email if needed. (Id use Titanium to backup the app and data) then in Application Manager, clear data on the email app. Reboot the phone and re-setup your email and see if it works again.
It does sound to me like it may be a problem on the provider side though.