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.
Related
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
So i updated my phone to CheckRom and kernel to NEAK and then Syhia.
For some reason, some of my calls keep going straight to voice mail since then. I thought maybe it was an issue with some app, so i did a wipe install of Checkrom and installed the NEAK kernal. But still same issue.
I then changed the kernal to Syhia and still some calls go straight to voicemail.
Anyone have any clue why? Any suggestions? Would greatly appreciate the help.
I had a similar problem. go to menu, settings, call, and turn off call rejection.
Hopefully its a similar issue u are having.
Whatever the issue is it's not kernel or rom related. It's purely a network setting issue. And these vary from carrier to carrier. Call your carrier.
Thanks for the reply guys. Sorry took me this long to post back.
Well i wanted to stay on the custom rom, so i did try installing it again, and i thought that since it is a full wipe, it will fix the issues. I also did a wipe cache/dalvik chache manually.
Any hows getting no where, i resotred using my original backup and everything seems to be fine. No one has complained about it, so i am guessing its all well now.
I had restored it before mrwarlock43's suggestions, but i do remember making sure that the blacklist was empty. So i never turned call rejection off.
All running now i guess. Just going to wait until ICS or the next rom before i reflash again.
Cheers and thanks for the help guys.
Hi all,
I'm using a GSM Razr XT910 with the CyanogenMod 9 customised ROM by J.Y. Daddy (RAZR-CM9-12.05.17-UNOFFICIAL-GSM-J.Y.Daddy) and I keep receiving duplicate SMS messages. I've changed to "Original timestamp" in SMS settings to see what's going on, and it seems I'm getting the same message up to 9 times.
It happens with multiple contacts, and I'm not sure how to fix it. I'm in the UK on O2 - does anyone have any ideas for how to fix, or has anyone else experienced a similar issue?
I had this issue too.
I live in Australia and have been using J.Y.Daddy's CM9 builds pretty much since he started porting them over to GSM. I tried to narrow the issue down to a few factors and the main causes I suspected were:
1) Different kernel version to your phone's "natural" one. Have you used RSDLite to flash any different fastboot files? Or are you on rooted stock initially?
2) Handcent. I began using this app after making the switch from GOSMS a while back and shortly before the duplicate message problem began. They have actually confirmed that there is some compatibility issues with some Motorola handsets, and this is reflected by Handcent's changelog. Are you by any chance using Handcent?
3) Finally, the last cause I come up with was a network issue which is refusing to send an 'acknowledgement' packet to the provider, essentially meaning the message is never marked as received and therefore, it keeps sending the message in an attempt to correct this.
In my experience, the problem was #3. I was on Optus for a long time (The 'second place' Australian telco), and recently made the switch to Telstra (#1 telco) and the issue has been resolved. If you are on stock kernel and do not use Handcent, then unfortunately I think it may be a network issue.
Don't take my word on this though, I'm not an expert. Just speaking from experience.
Thanks Mr. Ektid, I think in my case it's probably #1. I installed a different 2.3.6 rom over RSD in order to get the Bluetooth working without causing a bootloop, so I guess that must have messed things up. I don't use or have installed any SMS apps other than stock, and I don't think it's a network issue as texts were working fine before installing ICS.
I've rolled back to Arctic for now, seems to have sorted things again. I suppose the way to fix the issue in CM9 would be to RSD a stock UK 2.3.6 rom and then flash CM9 over that - but I'm not sure if that would mean I would still get Bluetooth bootloops, as it seems like a fairly specific 2.3.6 rom is needed for that to work.
Ah well. Back to Gingerbread for a while.
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?
So I recently flashed OctOS on my LG-LS990 and I am having this very annoying thing happening where I keep getting notifications that I have 1 voice mail when there aren't any. I've gone into the phone app and cleared cache, which makes the notification go away but then it comes back within a few minutes. This seems to happen quite frequently when I am at work and the signal is spotty. I've also called myself from a different number, left a vm, and then checked it from my G3 and deleted it and the icon doesn't clear. Also rebooted the phone numerous times, but it still comes back.
I was using youmail after I flashed the ROM, but have deleted it hoping it would resolve this issue. Which it has not.....
I was using Resurrection Remix ROM prior to this and initially had the same issue, but it cleared up when I did what I listed above. Anyone out there have any other ideas for how to fix this problem?
I have had the same issue and have asked but no answers yes. It is not a huge issue but really annoying. I have flashed Resurrection and OctOS and never could get it to stop showing up. I would get the VM notification EVERY time I got off of a phone call.
79 views and still no solutions
Go back to stock. Fix it. Then you might need to reflash CM instead of restore.
That's probably your best option
I have gone back to Stock several times using the Flash tool. When I do I have no more Phantom VM's. Root and flash a stockish ROM and still no phantom VM. But Everytime I flash any CM based ROM and get off of a phone call it comes back. after EVERY call. Aggravating more than anything.
engine95 said:
Go back to stock. Fix it. Then you might need to reflash CM instead of restore.
That's probably your best option
Click to expand...
Click to collapse
reedsammy7 said:
I have gone back to Stock several times using the Flash tool. When I do I have no more Phantom VM's. Root and flash a stockish ROM and still no phantom VM. But Everytime I flash any CM based ROM and get off of a phone call it comes back. after EVERY call. Aggravating more than anything.
Click to expand...
Click to collapse
Same here. May look at trying a different ROM. Such an annoying issue.....
Maybe try to just hide the notification. That is what I did. This is an old issue with sprint. If you really want to get rid of it, you have to find an old flip phone or something before android. Activate it and then go and clean out old voicemail's. I have been dealing with it since HTC EVO days. I have never gone back and done the real fix. If you really searched google there is info on this annoying issue.