I've only been experiencing this problem ever since i started using a MIUI rom, every version i use i still get the same problem of when sending a message and say someone just texted me and its coming through my message i just sent will automatically fail but then i still get the bar saying "message sent". Just wanna know how to fix this because its annoying have the little box pop up all the time saying "message failure". Is it a problem to where i should flash a new radio that will work better with the rom? Thanks in advance!
Brad4891 said:
I've only been experiencing this problem ever since i started using a MIUI rom, every version i use i still get the same problem of when sending a message and say someone just texted me and its coming through my message i just sent will automatically fail but then i still get the bar saying "message sent". Just wanna know how to fix this because its annoying have the little box pop up all the time saying "message failure". Is it a problem to where i should flash a new radio that will work better with the rom? Thanks in advance!
Click to expand...
Click to collapse
try from recovery to wipe cache+dalvik and see if it works
You can also try downloading the Rom again with a FULL wipe and clean installation like above post says wipe cash wipe dalvik, also try wipe data factory reset and clean install. Hopefully this will take care of the issues. If issues still persist perhaps it's a "bug" of sorts in the Rom? Are others expirencing this issue using this Rom ? Or just you? Does your mms work correctly using other roms? If so and clean install does not work you might have to try a different Rom until issue is solved. Have you tried mms fix? I believe in either android development or themes and apps they have a application called mms fix? I believe I remember seeing it. That's also worth a try. Best wishes .
sent from HTC sensation, soff, 3.33 firmware, viper Rom, sense 4.1, mugen battery. please press thanks if I helped in anyway.
whorso chanced
rzr86 said:
try from recovery to wipe cache+dalvik and see if it works
Click to expand...
Click to collapse
well i did that and now when i rebooted i get the "unfortunately, Systems UI has stopped" and my status bar is gone, and this always happens!!!! Sick of this i always have to reflash because i dont know how to fix.
Brad4891 said:
well i did that and now when i rebooted i get the "unfortunately, Systems UI has stopped" and my status bar is gone, and this always happens!!!! .
Click to expand...
Click to collapse
this is the first time for me at least to see something like that.really sorry i can't help you more.if you have patience wait for someone else to help otherwise reflash the rom again
Related
For those who are using this new ROM are you having clock issues?
Everything I access the clock it gives me a force close. Any help will do.
Thanks!
Do a full wipe.
I did a full swipe and cleared cache, still having the same issue.
To expand on foxcompany's post. If you don't do a full wipe when installing a custom Rom you will, almost garuanteed, experience issues. These issues include anything and everything from WiFi and GPS issues to random force closes on random applications.
So, if you experience issues; OS, App, or Widget issues and didn't do a full wipe that is the reason 99.9% of the time. If you're a noob (no worries, everyone was or is in some areas) I can post the full-wipe.zip that I use when I switch roms.
Another note... Typically upgrading roms, for example, upgrading from Android Revolution 5.x to 5.1.x you don't need a full wipe unless explicitly stated by the OP.
Long post for a simple question but hopefully it will help you or others with similar issues.
Sent from my InspireDesire 4GHD
Downloaded FULL-WIPE-1.3.zip from the sticky post, ran it and still have the same issues.
Maybe I downloaded the wrong one? I tried the fullwipe 1.2 and Vision and only 1.3 was successful.
Full wipe 1.3 is the one. If you flashed full wipe and reflashed the rom the issues should have resolved. If not, you'll have to wait for some more ideas cause that's all I got lol.
Sent from my InspireDesire 4GHD
Try redownloading android revolution, do a full wipe and install. If u are still having problems after that, try downloading and installing a completely different rom. Of course..wipe first. See if the issue persists. If it doesn't persist with a different rom, I would get in contact with android rev developer for further assistance.
Sent from my Inspire 4G using XDA App
dohtemz said:
For those who are using this new ROM are you having clock issues?
Everything I access the clock it gives me a force close. Any help will do.
Thanks!
Click to expand...
Click to collapse
I don't know if anyone has specifically stated they are also running Rev 5.1.3...but...
I'm running Revolution 5.1.3 and my clock works fine. Try redownloading the ROM, doing a full wipe, then flashing again. It's possible you got a corrupted file when downloading the ROM - Did you check the md5 of the ROM's .zip after it was on your SD?
I will download the ROM again when I get home and see if it's still there. Funny thing is I ran AR 3.7 and the clock worked file.
Will report back later.
[edit]
Ok so I re-downloaded the ROM and everything is working again. It appears that I installed the wrong no-sense patch which cause the clock to not to work.
Thanks everyone for the help.
[/edit]
Why is it that I always get FC message every time I start up my Nexus S or opening Android Market which makes Market inaccessible. The start up message would show something like android.media has stopped unexpectedly. Only on Oxygen ROM, 2.3.2 and 2.3.3 (newest).
I've done wiping data, cache and even dalvik cache.
I've tried on different ROM and it works flawlessly. Oxygen is my only problem so is there any solution?
Did you try fixing permissions in recovery?
Source-X said:
Why is it that I always get FC message every time I start up my Nexus S or opening Android Market which makes Market inaccessible. The start up message would show something like android.media has stopped unexpectedly. Only on Oxygen ROM, 2.3.2 and 2.3.3 (newest).
I've done wiping data, cache and even dalvik cache.
I've tried on different ROM and it works flawlessly. Oxygen is my only problem so is there any solution?
Click to expand...
Click to collapse
Welcome to XDA!
I have never had this problem. Do you only get this FC when opening market, or other apps? You should try to repair permissions.
Thanks .
Yes, I forgot to mention I did the permission fix through CWM and it did not fix. Am I supposed to fix it before flashing?
Source-X said:
Thanks .
Yes, I forgot to mention I did the permission fix through CWM and it did not fix. Am I supposed to fix it before flashing?
Click to expand...
Click to collapse
Not really....
I did not fix permission after flashing oxygen, but the rom working fine for me...
maybe you can try fresh install oxygen again maybe??
you forgot wipe /boot....that is how i fixed my problem before and it worked perfect
Help I'm having Error 921.Help I'm having Error 921.
I can't seem to download anything from the Market. It says Error 921.
It was working fine. I was on ARHD 6.5.2. I flashed a Set of theme. tHen i decided to go back to what I did is I restored my Nandroid Backup to my Previous ARHD 6.5.2.
I really need help
try cleaning data and cache of market app. Reboot and try again. It should work
As of the Moment it Seems to be fine. I'll be reporting again if i encountered it. But if anyone has an idea what happened and wouldn't mind to explain ^^, I would be very glad. Least I'll know where I went rwrong.
kualmente said:
try cleaning data and cache of market app. Reboot and try again. It should work
Click to expand...
Click to collapse
Thank you very much. I tried that before I read your response. But thanks for responding ^^, It got me worried at the moment. Like on my Sig "Im noob at the moment "
I am new to xda. I haven't ran into a problem yet that i couldnt find a solution to....UNTIL NOW!!!
I have an incredible 2. It is rooted, and DID have a cm7 OS. Today, differentPps on my pho.e kept opening and then being foreclosed. Naturally, I rebooted my phone to see if that would fix the foreclosing problem. However, THE REBOOT MADE PROBLEMS WORSE. Now, my phone shows "no service." It shows "unknown baseband," "unknown phone number" and won't receive/send texts/calls. I can only use WiFi to use the internet. I tried factory reset, (through cm7 and the phone itself) I also tried downloading a new radio and cm9. Help NEEDED ASAP!!!! WHAT ELSE CAN I DO?!!
ladyjager said:
I am new to xda. I haven't ran into a problem yet that i couldnt find a solution to....UNTIL NOW!!!
I have an incredible 2. It is rooted, and DID have a cm7 OS. Today, differentPps on my pho.e kept opening and then being foreclosed. Naturally, I rebooted my phone to see if that would fix the foreclosing problem. However, THE REBOOT MADE PROBLEMS WORSE. Now, my phone shows "no service." It shows "unknown baseband," "unknown phone number" and won't receive/send texts/calls. I can only use WiFi to use the internet. I tried factory reset, (through cm7 and the phone itself) I also tried downloading a new radio and cm9. Help NEEDED ASAP!!!! WHAT ELSE CAN I DO?!!
Click to expand...
Click to collapse
Have you tried RUU'ing back to stock?
_MetalHead_ said:
Have you tried RUU'ing back to stock?
Click to expand...
Click to collapse
If you're referring to restoring back to stock Rom, I already have.
ladyjager said:
If you're referring to restoring back to stock Rom, I already have.
Click to expand...
Click to collapse
But did you try it with a RUU?
_MetalHead_ said:
But did you try it with a RUU?
Click to expand...
Click to collapse
Yes, I've tried a couple times.
Try
Try hard resetting, which means clearing all data, and wiping cache (if it is that bad)
or
Try doing some of the previous steps again....
Hope It helps
I have same type of problem but after trying these instructions, I found the solution of the problem. Simply try them step by step and you will get results.
pure.noob said:
Try hard resetting, which means clearing all data, and wiping cache (if it is that bad)
or
Try doing some of the previous steps again....
Hope It helps
Click to expand...
Click to collapse
Tried hard resetting, wiping dalvik cache and cache partition. Still nothing.
However, slight change- after setting it back to stock, switched it over to cm7.2. Now, I have the roaming indicator flashing, but still cannot make calls or send texts. Before, while trying a new Tom, it would bring me to the same point, ^ but when I would select regular reboot, it would put me back with "no service."
It may happens.
Restart your phone and try then.
rayanlee said:
I have same type of problem but after trying these instructions, I found the solution of the problem. Simply try them step by step and you will get results.
Click to expand...
Click to collapse
What instructions are you referring to? And I've tried, the most simple and generally harmless to extreme wiping and resetting everything I had. Let's say I'm just fit to be tied. This is a nightmare!!!
erolapy said:
It may happens.
Restart your phone and try then.
Click to expand...
Click to collapse
Tried and it didn't work.
Well, after many, Many MANY attempts to fix this, finally switched SIM cards with another phone and found out my SIM card blew!!! How often does that happen?!
ladyjager said:
Well, after many, Many MANY attempts to fix this, finally switched SIM cards with another phone and found out my SIM card blew!!! How often does that happen?!
Click to expand...
Click to collapse
It happened to my sim card..no idea why..I was flashing different rooms and modems but finally swapped sim just to test ( I didn't really think that sim would be the culprit) but it worked on different..no idea as to why sim stopped working.
Sent from my Nexus S using xda app-developers app
Any ROM i put in my phone, the dialer will always FC on me with the message "android.htcdialer has stopped. I can't use my phone...what does xda suggest i do?
Try to RUU back to stock, maybe your dialer is corrupted
I did do an RUU back to 1.85 and it still does the same thing, both the dialer and contacts will fc. I'm out of options.
Did you try formating system and then flashing a ROM? If not then try that. And if that don't work I suggest you re-download 1.85 ruu return to stock.
Sent from my One X using xda premium
What do you know, I'm getting the same problem now, i can't access my dial, contacts and the messaging app crashes on me.
Tried to go back to stock 1.85 but it still gives me the problem. I think I'm going to try 1.82 stock instead.
If anyone can shed some light into this issue, it'd be a great help.
rayoubi said:
I did do an RUU back to 1.85 and it still does the same thing, both the dialer and contacts will fc. I'm out of options.
Click to expand...
Click to collapse
It happened to me too and now I have a solution.it happened to me when I installed a rom(don't want to mention the name).ok do this
Root ur phone unlock bootloader and install cwm not twrp.now clear cache,data,system everything and install any rom(even stock)using TARP(dont forget to clear everything in twrp also).
It worked seriously for me and believe me.if I helped u please hit thanks button