Are there any ROMS out there that have working MMS ? I have tried a number of them and no luck. I know these are labors of love but it's such a vital part of the phone itself to be left on the back burner. The only ones it works for me are 2.1 v's 1,2 & 3 every other ROM i tried it's always the same thing, no soft button lights, no trackball lights, no MMS. I've tried every fix offered under the sun & it just doesn't work, OR it might work, 18 hours later.
From what i have read it looks like half the people have no problems & have are in the same boat as me.
any suggestions?
thanks
I use sense-able and have no issues sending or recieving mms msgs
the MMS fix is quite simple. What ROM are you using? I know that in the EE thread there is a link to ivans-apns and instructions on removing your current APNs and installing the APNs from ivans rom.
I have working MMS on every rom I have tried except for one .....
Thanks for the 411 and I must say that name gave me the first laugh for the day "Cornbreadfarts"
Fn Funny dude.
well last night i loaded ZenEXP-Eris_Rev6-fixed_mak, i hadn't seen that one before and it looked very stylish. The overclocking isn't so important but i like the apps2sd. Followed all the instructions including flashing the mms fix also cited in the thread. I should have tried it our right away but i began to get comfy with the rom then when i remembered, bingo, same thing. Attaching even a very small photo gets a generic network error, it'll try 4 times to send it then stop. With other roms, sometimes 18 hours later it'll suddenly go through.
before this I'd tried evil eris, lightning, Dvanilla2fast, vanilladroidv1, fresh 2.1 & aloysius, all with the same result.
every rom has their own little quirks, evileris would seem to stall for a while then suddenly go through all the motions of your frantic thumb presses while u thought there was something wrong. I tried all the solutions offered also with the apn's in the evileris thread but still the same thing
the zenexp seems to restart itself at random times and does not come out of landscape mode after taking a pic. I have to press settings, then back & it resets itself
I like the variety in the various roms and the little extra bells & whistles that the developers add it's just this 1 issue really for me. I don't make a lot of calls and i mostly text back & forth to my daughter in NYC. Recently a loved pet of 13years died but beforehand i couldn't send her any pics of the cat in the days previous.
I guess i'll look for this sense-able and try that. I just don't get it though, we are all using an eris, it should either work or be broken for everyone right ?
heywoood said:
well last night i loaded ZenEXP-Eris_Rev6-fixed_mak, i hadn't seen that one before and it looked very stylish. The overclocking isn't so important but i like the apps2sd. Followed all the instructions including flashing the mms fix also cited in the thread. I should have tried it our right away but i began to get comfy with the rom then when i remembered, bingo, same thing. Attaching even a very small photo gets a generic network error, it'll try 4 times to send it then stop. With other roms, sometimes 18 hours later it'll suddenly go through.
before this I'd tried evil eris, lightning, Dvanilla2fast, vanilladroidv1, fresh 2.1 & aloysius, all with the same result.
every rom has their own little quirks, evileris would seem to stall for a while then suddenly go through all the motions of your frantic thumb presses while u thought there was something wrong. I tried all the solutions offered also with the apn's in the evileris thread but still the same thing
the zenexp seems to restart itself at random times and does not come out of landscape mode after taking a pic. I have to press settings, then back & it resets itself
I like the variety in the various roms and the little extra bells & whistles that the developers add it's just this 1 issue really for me. I don't make a lot of calls and i mostly text back & forth to my daughter in NYC. Recently a loved pet of 13years died but beforehand i couldn't send her any pics of the cat in the days previous.
I guess i'll look for this sense-able and try that. I just don't get it though, we are all using an eris, it should either work or be broken for everyone right ?
Click to expand...
Click to collapse
ZenEXP-Eris doesn't restart itself at random times out-of-the-box, you must have installed or modified something that's causing that error. My releases go through a somewhat rigorous beta testing before they see the light of day - at least since Rev5 - and we've only seen minor issues upon release of them.
As for the accelerometer (the "not coming out of landscape" issue you refer to), that's a known bug in Rev6 that was found after releasing it. It is fixed in Rev7.
At the begining of my ZenEXP-Eris thread, I state that you should read the entire thread twice before flashing. This is so you know what you're doing, what to expect, how to make things work properly and what bugs are present in the ROM. Obviously you didn't read my entire thread, or you would have found the MMS-Fix, which is located about 6 lines below the ROM download
On a side note, Rev7 includes the MMS Fix built right into the ROM, no need to flash the MMS-Fix through Recovery like you do now for Rev5 and Rev6. You'll be able to enjoy Rev7 (hopefully) tomorrow (if not the next day).
-mak
Sorry, I thought I had been clear, I did read the whole thread and did dl & flash the mms fix zip u attached. I'm only reporting on the problems I'm having. This isn't a personal attack on you.
As I said, I understand these are labors of love and I wouldn't report something if it didn't happen. I have had 3 occasions where it restarted itself and all 3 times all I had installed was vignette, meebo, Google translate, shopper & barcode scanner.
Thank you for your reply
-------------------------------------
Sent via the XDA Tapatalk App
heywoood said:
Sorry, I thought I had been clear, I did read the whole thread and did dl & flash the mms fix zip u attached. I'm only reporting on the problems I'm having. This isn't a personal attack on you.
As I said, I understand these are labors of love and I wouldn't report something if it didn't happen. I have had 3 occasions where it restarted itself and all 3 times all I had installed was vignette, meebo, Google translate, shopper & barcode scanner.
Thank you for your reply
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I'm sure it wasn't a personal attack, but I'm not sure why you're telling me that?
Anyway, if you installed the MMS fix, you should have working MMS. The MMS fix hasn't failed anyone that I know of and I used it myself on Rev5 and Rev6. Did you boot into the phone and set it up after flashing the ROM, but before install the MMS fix? The file the MMS fix installs gets overwritten during the first boot, which is why you need to reboot before installing it.
I don't use any of the apps you've installed, so I can't attest to their compatibility with ZenEXP-Eris. What I recommend you do is backup your data, go into Recovery and wipe data/cache/dalvik/ext, then re-install the latest release of Rev6, boot into ZenEXP-Eris and set your phone up, reboot into Recovery and install the MMS fix. Before installing any applications test it all out for a few hours, the proceed to install them one-by-one, leaving an hour or so in between installs until you (possibly) find what is causing the issue.
I'm really sorry to hear this issue persists for you but, as I mentioned earlier, you're the first to report such issues, thus the reason I suspect something else as the culprit
Feel free to PM me for one on one support if you need it.
-mak
edit: Also, regarding your softkey lights, they only turn on in dark areas. Hold your finger over the light sensor to the left of the earpiece speaker to see them light up. In ZenEXP-Eris the jogball LED doesn't function, but I have mapped notifications to the charging/power LED in the upper-right-hand corner of the Eris as an alternative, for now.
heywoood said:
Are there any ROMS out there that have working MMS ? I have tried a number of them and no luck. I know these are labors of love but it's such a vital part of the phone itself to be left on the back burner. The only ones it works for me are 2.1 v's 1,2 & 3 every other ROM i tried it's always the same thing, no soft button lights, no trackball lights, no MMS. I've tried every fix offered under the sun & it just doesn't work, OR it might work, 18 hours later.
From what i have read it looks like half the people have no problems & have are in the same boat as me.
any suggestions?
thanks
Click to expand...
Click to collapse
Hey,
There are several out there that work. Ivans are typically good to go out of the box and most if not all the Sprint based roms will be good to go by using the apn fix. Its a trial and error thing just find a rom that you like and give the thread a good read.
Most all the posted roms now have an mms "fix" or are good out of the box. I know it gets a bit disheartening flashing, setting up, wiping, flashing etc...lol...but thats the joy of a rooted handset...trial and error till you find a rom and dev you like well enough to stick with.
.mak said:
I'm sure it wasn't a personal attack, but I'm not sure why you're telling me that?
Anyway, if you installed the MMS fix, you should have working MMS. The MMS fix hasn't failed anyone that I know of and I used it myself on Rev5 and Rev6. Did you boot into the phone and set it up after flashing the ROM, but before install the MMS fix? The file the MMS fix installs gets overwritten during the first boot, which is why you need to reboot before installing it.
edit: Also, regarding your softkey lights, they only turn on in dark areas. Hold your finger over the light sensor to the left of the earpiece speaker to see them light up. In ZenEXP-Eris the jogball LED doesn't function, but I have mapped notifications to the charging/power LED in the upper-right-hand corner of the Eris as an alternative, for now.
Click to expand...
Click to collapse
I actually did exactly what you said. I downloaded all the files first then i formatted the sd card, toggled, loaded the rom & the mms fix, wiped the handset (reset & dalvik), flashed the rom. When it loaded I set up the phone, power cycled & booted to recovery, flashed the mms fix and restarted the phone.
I wanted to make sure that apps2sd was working to i went to the market & installed vignette (excellent photo app) and the usual google made apps like translate, shopper etc
it was after all this I remembered the mms, so i tried it & nada.
I'm about to reformat & wipe now so i'll see what happens
Related
I was getting 15-20 second gps locks when I had radio .40 and DCD 3.2.6, but as soon as I upgraded the radio and DCD then it's taking like over 7-9 minutes to get a lock. Sometimes it won't lock at all anymore unless I do a hard reset on the phone. I'm not sure what happened. Does anybody have any ideas? Look at my signiture below for my current configuration.
What's the best Radio and ROM to use right now with the least amount of problems, etc.? I was looking at the V2.2 heavy and light, but I'm not sure if I really understand much about what they are about or the differences in what I have now. I think my biggest problem is with text messaging. If I do it a lot I have to keep restarting my phone because the memory goes down to zero in no time at all. Infact, I have to keep constantly clearing the memory if I use any programs at all. Thanks for your help and time!
Try either 3.3.4 or 3.2.6. I prefer 3.3.4
after all of my testing i ended up sticking with 3.2.6. did you do the aGPS fix? have you checked the QPST settings since your flash? generally, these settings should stick, but in some cases; such as when you need a new a-key, these settings are lost. my last flash removed all my QPST settings and i couldnt lock until i did the aGPS fix again with the updated IP address and port.
Well, in the past it kept all the information after I did the upgrade, so I just assumed it still did. I didn't need a new A-Key. I guess I'll check the QPST settings and do the aGPS fix again. It's been so long ago since I did all the GPS stuff I can't remember what I did and didn't do. I still do get locks but they take forever now and sometimes I don't get them until I restart the phone.
Why are you sticking with 3.2.6? Why don't you like 4.1.2 or 2.2 heavy or light? I've always had the memory problem where if I use programs it just eats up my memory and I don't get most of it back after exiting the software, and if I use my text messaging then my memory just goes down to zero in no time flat and I can't recover it unless I'm constatly restarting my phone. There must be some kind of fix for this. Please let me know. Thanks.. Steve
kflipproductions said:
after all of my testing i ended up sticking with 3.2.6. did you do the aGPS fix? have you checked the QPST settings since your flash? generally, these settings should stick, but in some cases; such as when you need a new a-key, these settings are lost. my last flash removed all my QPST settings and i couldnt lock until i did the aGPS fix again with the updated IP address and port.
Click to expand...
Click to collapse
the QPST settings have changed, so if you did it a while ago you probably just need to update it. youll be locking again after that. ive tested all of dcds roms quite a bit, and always ended up back at 3.2.6 or 3.2.5. im really happy with the speed and everything works exactly as it should. i have a pretty heavy today screen load as well as running several apps at the same time. i didnt like the 4.x.x roms for a couple of reasons. the unread text message thing bugged me alot. i also had a problem with random hard resets, which i was not a fan of.
kflipproductions said:
the QPST settings have changed, so if you did it a while ago you probably just need to update it.
Click to expand...
Click to collapse
Are the changes in the AGPS thread?
yes they are
Oh, really? Then that's probably part of the problem. I changed them maybe a year ago or longer. I tried running QPST to check and it's giving me an error message when I start it, so I'm going to have to try to reinstall it and see if that fixes it. Also, the links for the pictures are dead and they aren't coming up anymore, it makes it harder to figure it out.
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
I ran the Serf Telus aGPS Provisioning CAB file and that seemed to help. I sometimes get locks under 1 minute now, but sometimes it won't lock at all and I have to keep soft booting the phone to get it working.
Oh, so that's why my phone keeps resetting? It's not hard resetting I think it's just soft resetting. At first I didn't like the unread text message thing, but now I do because I get a lot of text messages and when I go to read them it doesn't mark them all as read in the group and I can read them when I get a chance.
I still had the memory issues with the 3.2.6 ROM with my memory going down to nothing, especually when I did text messages, I had to keep restarting my phone. That's been a problem I had with all my ROMs. I wonder why that is? Could it be the version of the MMS software I'm using? Is it the latest version?
Maybe I should go to the MR1 ROM? I still will be able to use the GPS and the WiFiRouter software with it right? Maybe that will solve all my problems? What about the 2.2 light and heavy ROMs? Does anybody know anything about those? Thanks for your help and time...
kflipproductions said:
the QPST settings have changed, so if you did it a while ago you probably just need to update it. youll be locking again after that. ive tested all of dcds roms quite a bit, and always ended up back at 3.2.6 or 3.2.5. im really happy with the speed and everything works exactly as it should. i have a pretty heavy today screen load as well as running several apps at the same time. i didnt like the 4.x.x roms for a couple of reasons. the unread text message thing bugged me alot. i also had a problem with random hard resets, which i was not a fan of.
Click to expand...
Click to collapse
Well, I uninstalled QPST and reinstalled it and it worked this time without any error messages. It seems if I don't use it for a while it gives me a error message if I try to use it again and I have to uninstall it and reinstall it and then it works OK. I don't remember the error message, but I think it's something about can't find a server or something.
Anyways, you were right about the information I had being old and not correct. I had 66.174.95.132 and 8888 instead of PDE IP Address: 216.198.139.92 and PDE Port Number: 8889. I corrected it and it still seems to take about 56 seconds to get a lock, but hopefully now it will be more reliable in getting the locks. I seem to remember in the past getting locks in less then 10-15 seconds, and I wonder why I can't get locks like that anymore.
Thanks for the help!
Well, I was wrong, I'm getting 15-20 second locks now and I'm getting twice the satalites, up too like 9 satelites and I was getting 1/2 that before and it's a lot more accurate now. Before when I was using Google Maps, I could see it was off like about 50-75ft, but now it's spot on, on my location. Hopefully someone knows the answers to some of my previous questions and can get back to me. Thanks..
I too was having this same exact problem and I had to update the QPST IP address and port again. Mine had reverted to the same thing that Apota's had, with the exception of my default port being 8888. All is working well now that I reset the QPST IP address. I get 6-8 sats and locks in about 10 seconds.
I had been experimenting with some of the RyanMogul's new ROMs when this broke for me. I tried 2.1 light and it stopped working. I'm currently running 1.1 light with it functioning after reusing QPST.
DustinEarnhardt said:
I too was having this same exact problem and I had to update the QPST IP address and port again. Mine had reverted to the same thing that Apota's had, with the exception of my default port being 8888. All is working well now that I reset the QPST IP address. I get 6-8 sats and locks in about 10 seconds.
I had been experimenting with some of the RyanMogul's new ROMs when this broke for me. I tried 2.1 light and it stopped working. I'm currently running 1.1 light with it functioning after reusing QPST.
Click to expand...
Click to collapse
I just upgraded to the v2.2 light. I think I'm going to have to get use to it because the interface is so different, but I got a GPS lock with my TomTom GPS software in about 4 seconds. I couldn't believe it. I haven't seen a lock that fast before. It's really awesome! LOL
I'm having a problem that has me stumped.
YouTube
Earlier in the week, I noticed that I was unable to stream YouTube videos over mobile data. I could launch YouTube and it would bring up the top videos. I could search and it would get me results. I could not however get anything to actually play, when I choose a video it will just sit at the loading screen, and my bars will turn grey. I will not get a mobile data connection back until I back out of Youtube. I confirmed this issue with several different videos while in different parts of the state, so it isn't limited to a certain video or tower.
Google Talk
If I am at the main screen that shows who is online/offline, usually this will display properly. However as soon as I pick a name and go to send a message, my bars will turn grey and I will lose my data connection. It will not come back until I back out of Talk. Sometimes after this happens I can reopen talk and it will sit at the main screen for a while, get mobile data back, and display who is online and who is not. Most of the time, Talk will not work again until I force close it.
Edit: Talk will not disconnect until I actually send a message. The message makes it through most of the time, but then I lose mobile data. This results in Talk saying "Lost connection to Server. Messages will be sent when online."
I am on CM7 Nightly 20 with the stock CM7 kernel since the day Nightly 20 was released. Just to be safe, I did a full wipe in Fastboot erasing the following partitions before re-flashing: userdata, cache, webtop, system, boot.
I am unsure when this problem started. I know that YouTube worked last weeks, but when I think back, I can't remember the last time Google Talk worked while I was on mobile data. Note though, that while on Wifi everything works just fine.
I'm at wit's end here. I'm going to wipe the phone again and install stable Ba2tF and just Google Apps, and see what happens (after I flashed Nightly 20 earlier today I had the Market start spam reinstalling my apps before testing Google Talk - though I did get to test it and have it lose data after just a few apps were installed).
I'm on 30P for the radio, AT&T, Western Massachusetts, any help would be greatly appreciated!!!
I was going to post the same exact problem. The problem only appears over cellular. Over WiFi, everything works fine. Also, I just reflashed stock and it works. So it would seem to be a problem with CM7 and/or AT&T.
I'm going to get a good logcat of what's going on after I narrow it down a bit more... my current log is 1MB, which as about 2 minutes of info. I'm going to try to narrow it down to just the few seconds from when I hit "send" to when I get disconnected.
Hopefully at that point someone smarter than I can figure out what's going on.
DK
DeathKoil said:
I'm going to get a good logcat of what's going on after I narrow it down a bit more... my current log is 1MB, which as about 2 minutes of info. I'm going to try to narrow it down to just the few seconds from when I hit "send" to when I get disconnected.
Hopefully at that point someone smarter than I can figure out what's going on.
DK
Click to expand...
Click to collapse
Just thought I'd chime in and give some feedback. Tested this out on Weekly #2 both with wi-fi and regular data and everything was working as it should. I've been through a few different versions of CM7 and have not run into this.
Have you been using the same gtalk .zip each time? Maybe try re-downloading it along with your fresh install? Also, have you re-flashed your radio?
And here is a logcat capture. I force closed Talk, started the capture, launched talk, connected, pressed on my roommate's name, and lost my connection. The part that says "<SNIP>" is where my email address was.
I'm going to upload it here, then start to go over it myself.
DK
ghost_og said:
Have you been using the same gtalk .zip each time? Maybe try re-downloading it along with your fresh install? Also, have you re-flashed your radio?
Click to expand...
Click to collapse
Yeah, the GAPPS package ROM Manager lists as newest is still 20110828, which is also listed as newest on the Cyanogen Wiki. I never re-downloaded it, I've always used the same .zip everytime I've needed it... which is since Pre-Beta1.
I didn't flash my radio up to 36P when it came out since some people reported issues with it, and 30P had been working fine for me since June/July.
I am going to try to re-flash Google Apps now, this time without using the new version of talk that supports the front facing camera... since I never used the functionality anyway. I will report back in a few minutes.
DK
I tried reflashing both AT&T radios and both versions of Talk (w/ and w/o video chat).
For me, I get disconnected as soon as I open Talk. Happens every time. I froze Talk and I was disconnected when I got a Gmail notification. Maybe it was a coincidence but either way I was disconnected so the problem isn't limited to Talk. Maybe it's a problem with the Google Services Framework.
Here is what I think is a better logcat of what happens. This time, I setup CM7 to have long press back kill the currently active process, so that I could kill Talk right away.
I started the logcat from killing Talk and hitting the home button while it was restarted. I sent one message that said "Son" to my roommate, and lost my data connection. I then waited 20-30 seconds, killed Talk, it restarted, I got data back, I sent another message to my roommate that said "disconnect", and I lost my data again.
NOTE: This is with the Talk from the newest GAPPS (fresh download with ROM Manager), but not the one with the camera support (camera crap was cluttering the logcat anyway).
Anyone who is smarter than I able to see what's going on here?
DK
Same problem with CM7 Beta so I'm guessing there's some problem between CM7 and AT&T. I'm on AT&T in NYC.
I have a list of ROMs this does NOT happen on. I went back and restored to several points trying to figure out exactly where the problem started, and while I didn't find that, I do have a list that it does and does not happen to.
Talk Works on:
Prebeta2
Prebeta3
Prebeta4
Stopgap
Ba2tF
Weekly1
Nightly8 (likely it works on Nightlies 1-8, I just never made a backup after that and went right to 20 so I dont know exactly where the issue started with nightlies)
Talk does NOT work in:
Weekly3
Nightly20
So at some point between Nightly9 and Nightly20 (which includes the commits for Weekly3), something happened with Talk that is causing it to drop your data connection when you send message or refresh the friend list.
If any Dev happen to stumble upon this thread, I did take a logcat dump and linked it above as a txt file called "betterlog.txt" which clearly shows two disconnects while using Talk without having a lot of other "noise" in the logs from other things happening on the phone.
DK
Same problem, only I have this in Ba2tF. Odd thing is, I was running Ba2tf for some time, then all of a sudden this issue just appeared. I couldn't get it to clear, even after wiping data, caches, re-flashing etc...
Looks like this is nothing new. Check out CyanogenMod issue 3557.
---------- Post added at 02:52 AM ---------- Previous post was at 02:38 AM ----------
Same problem in Ba2tF. I was running Ba2tF for several weeks, then this problem just popped up. Couldn't get it to clear.
Looks like an old CyanogenMod issue. Issue #3557.
I don't know if it's AT&T that changed or CM7 but the problem's gone since I started using weekly #4.
Both are running latest Energy as it seems to be the most stable rom. We are having two issues.
First issue, we can not view or send text messages from a specific person. We have to delete the history and then we can view/send messages.
Second Issue, Same as above except the stock or any other text messaging up stop working, only through a wipe and reload can this be fixed.
Third, Both phones would not go passed the start up animation. Had to wipe and reload.
4rth, Phone will be on then turn off without any notification. Need to pull battery then it works.
There are more issues.
I'm sure this is nothing hardware related, more software related.
Is development for the Amaze dead? Most roms either still need a lot of work while others have not been updated in months.
I had an atnt S3, I loved not having any issues. ;,(
Soff?
What bootloader.?
Did you double flash? (some say it helps)
Here is my process
Super wipe
Flash
Fix permission
Boot
Boot
Flash again
Fix permission
Boot
All boots are cold full boots not quick etc
If you want to flash app data etc from another rom your asking for problems
If your on tmobile there are mms issues that some roms need a fix flashed too. (dunno which tho.. I'm on wind)
If you swap mms apk's some just don't work well with our phones.. Get/use/keep the right one (as system) then add chomp or gosms or whatever
e-Sex.. All of the carpral none of the tunnel
there's been lots of new rom releases for the amaze recently since CM10 got data working, and id say speed rom or fourth bar infusion are among the most "stable" and "best" looking roms out... personally i would get a superwipe that krook6023 posted earlier somewhere in the Q&A section, flash super wipe and flash a rom or flash back to stock and start over again because it sounds like you did something wrong and what recovery are we using to flash these said roms?
F9zSlavik said:
Both are running latest Energy as it seems to be the most stable rom. We are having two issues.
First issue, we can not view or send text messages from a specific person. We have to delete the history and then we can view/send messages.
Second Issue, Same as above except the stock or any other text messaging up stop working, only through a wipe and reload can this be fixed.
Third, Both phones would not go passed the start up animation. Had to wipe and reload.
4rth, Phone will be on then turn off without any notification. Need to pull battery then it works.
There are more issues.
I'm sure this is nothing hardware related, more software related.
Is development for the Amaze dead? Most roms either still need a lot of work while others have not been updated in months.
I had an atnt S3, I loved not having any issues. ;,(
Click to expand...
Click to collapse
I've been on NRG since I got my Amaze, and I don't have these issues. The only problem I have is an occasional lock up when using BT, but that is very rare. One thing you might do is a reset from recovery, and then do not restore the phone - manually reinstall all programs. It is possible that your restore is putting problems back into the device.
This would include not using Google to backup your settings before reset.
So I really love this ROM, it's lightning fast..here I thought that android itself was just incredibly slow..I've tried a couple different roms including stock, and had the similar woes with my HTC desire hd.
So it all works beautifully, it's super stable..only 2 problems, one is that the HSPA/3g/signal icon is always at no bars, setting it to text mode shows -1. Not sure what's up with that, it was kind of scaring me at first, but now I guess I'll just assume I have signalnage and live with it.
However, I'm starting to revamp my security practices, including using encryption for everything b/w desktop, mobile and google sync crap, and using entirely random secure passwords..
Problem is, I wanted to enable encryption via the builtin kernel encryption support...however, I go into Settings->Security->Encryption, set a PIN, it says it'll reboot several times and prolly take an hour.
It shows an "encrypting" icon, reboots and i log in like nothing happens. I go to that same page and it acts like I never set it up. I tried this 10 times, tried wiping some cache, removing sdcard, rebooting many many times..nothing.
Any suggestions on how to fix this? I desperately want the added security in case someone finds my phone.
EDIT: could a mod rename this, fix the spelling error? that's really bugging me, I really need to set up firefox's handling of dark system themes..
I love this rom so much too. Hope , it'll continue
History:
I've been lurking in the shadows commiserating with those experiencing these issues with sms and mms after recent flashing. I'm in AZ, have been dealing with these problems for the past month or so.
Like others posting before, flashing to the stock rooted 4.4 Ota rom restored everything to normal, but trying to go back to gummy rom or Viper jacked everything up. I would be able to receive one or two sms, one of two mms, and then nothing else until I wiped cache and rebooted. This actually only worked intermittently, sometimes bringing on the recurring multiple previous delivered message issue. I had accepted my fate, my DNA forever doomed to a stock rom, but was experiencing the horrible sensitivity issue with the capacitive buttons (gag).
Anyway, I gave it one last ditch effort to try to fix the text problem (and ditch the stock rom and the button sensitivity crap) and seem to have stumbled upon something that actually has worked for me. I'm freaked that one small mistake could throw me back into the text problems, but for now, I'm running a fully functional Viper 4.1 without any of the aforementioned issues. If there are those out there still looking for a fix (and not a new phone, like I was considering for a while) let me know with a post in this thread and i'll do my best to explain what I did and why. I am a long time user and have no technical explanation for why it worked, but it did.
My rationale (flawed or not) was to try to get the "lock" from vzw that allows text messages to be sent from the stock rom and transfer it to a custom rom. I figured that possibly when a phone is activated or new rom flashed or when caches are wiped, possibly the custom rom information is sent at that time to vzw and they then activate the cripple on messaging. SO, I did the following to try to get around that possibility:
0. Pull sim card
1. full wipe (cache, davlik, system) and flash of the stock rom
a. reboot system
2. First boot of Stock Rom: skip all adding of accounts, wifi etc.
3. reboot to system
4. after system completely booted, add sim card
5. test sms, mms, group messaging (thereby acquiring "lock" or permission from vzw to text)
a. I sent a ton. just to confirm all was working well. my wifes phone now has a billion random texts from me. i also opened up a text plus account (app on play) to allow testing of sent and received sms.
6. reboot to system
7. test again
a. after testing confirmed, reboot to recovery and PULL sim card
8. DO NOT WIPE CACHE OR DAVLIK OR ANYTHING and install custom rom (Viper for me:highfive
9. after flash in recovery, DO NOT WIPE
10. First boot to custom rom: skip all adding of accounts, wifi etc.
a. system will be wonky, possibly not even boot due to lack of wipe. i may have been able to get away with this because i flashed from sense rom to sense rom. I've not tested this with any cm-based roms, only viper 4.1.0
b. as before skip all adding of accounts or wifi (NO CONNECTION WITH vzw during initial boot - this could be KEY)
c. REBOOT TO SYSTEM, and add sim card
11. test sms, mms, group messaging
a. i was beyond stoked to see that messaging worked. still does work. confirmed with multiple (over the last 24 hours now) sms, mms, group messaging.
b. my keyboard was totally non-functional and it only gave me option to type with voice or send emojii (used google hangouts for all my testing)
c. despite function of messaging, the whole installation was totally unstable due to lack of wipe. soooooooo....
12. reboot to system
13. test again
14. reboot to recovery
15. DO NOT WIPE CACHE OR DAVLIK, perform a "Factory Reset" under the wipe menu
16. reboot to system - cry tears of joy if you now have a bugless, functional custom rom that can message again.
I know there are likely redundancies in my methodology, and i dont know if my theory is in fact what has made this work for me now when everything else failed before, but, fact remains that it worked (is working) for me. I am very hopeful this is at least a way around the problem for those that have been plagued with it as I have.
I'll keep everyone posted with whether or not this sticks forever (i'm only about 24 hours deep), and of any other developments as I likely get stupid/courageous enough to perform additional wipes, etc. Anyone else that has dealt with this issue, your feedback (hopefully successes) and thoughts on the issue are very much welcome. Let's kick this thing.
Doh! Why do I have to go to work?! Stupid railroad... I will attempt tonight when I come home!
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Does this work for anyone else?
orangechoochoo said:
Does this work for anyone else?
Click to expand...
Click to collapse
Haven't been able to get it to stick but I've been starting from a daily driver stock Rom. I should probably begin with a clean install as described.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Thought I'd leave an update - things still working well. All messages still coming through and sending well. Anyone out there been able to recreate my success with this process?
Well, seems very conplex. Will this work on every phone?
Jungsoowu said:
Well, seems very conplex. Will this work on every phone?
Click to expand...
Click to collapse
works on every phone I've tested it with
Quick update on my end - I finally succumbed to the need to wipe cache on viper, and sure enough my old issues with sms and texting in general returned. I restored back to a nandroid made before the wipe and everything was OK again. I was emboldened to take a few risks since the ball was already rolling - I flashed Carbon Rom with all manner of wipes and with no particular consideration paid to the issue we've been discussing. Surprisingly, everything has been working perfectly with SMS and MMS. Really made me wonder what was going on back then - was it TWRP? was it the wipe? was it something solely on VZW's end that has now been cleared? Don't think I'll ever figure it out completely. Just glad that I seem to be past the issues. Has anyone else seen improvement?