So I was running eclipse .5, but wanted blur messaging back, and hadn't made a recovery for stock.. sorry for that, i know, i'm a dumbass.. but i thought it should be pretty easy.. more about that later. When i tried using SBF to get back to stock, i only get bootloops with the stock boot animation. re sbf. Same Thing. Boot into android recovery, do a factory reset. SUCCESS!! Thought this was going to be an SOS thread, but i guess not.
So now, onto getting stock blur messaging back onto my x2. When blur Sms was removed, it broke the bluetooth message access protocol. My lincoln sync, and other ford syncs, will use this protocol to notify the driver of text messages, and use sync's text to speech to read the message to you. With eclipse running, i can tell the car to download the messages and it will, successfully. With stock running i will actually get a notification from the car. etc. I was going to try sticking the stock messaging service in system/app/ and remove mms.apk
I'm sure there is something else i have to do as well, like make this initialize with everything else on boot. I think the problem is that Blur sms passed an event to the bluetooth framework, making it send the notification to the car, and vanilla sms does not do this. So assuming nitro didn't alter bluetooth, all i need back is blur sms. someone who is smarter than i, Am I right So far?
Related
when I get a text, I get double texts. One on the stock Messaging app, the other on the Vanilla.
I have
1. Gone to Settings> Apps and disabled all the defaults for both the stock and Vanilla messaging apps.
2. Gone to the stock app's settings and disabled notifications and "auto-retrieve" or whatever it's called. Still, I don't get double notifications now, but I do see double posts inside the Vanilla MMS conversation thread.
Is there anyone running this that has managed to make it stop?
Despite restarting a few times, still nothing. Is there not anyone using this? It was a big deal when it wouldn't install as an .apk at first, I'd like to think some people finally got it to work.
if you dont have root then you cant get access to the /system/app folder so you cant remove the other mms app. thats whats causing the "bug"
My Gmail has started acting up, and won't let me delete certain emails. I try deleting them on the NC, and the gmail app force closes!
Does anyone know how I can fix the problem?
silivrenion said:
My Gmail has started acting up, and won't let me delete certain emails. I try deleting them on the NC, and the gmail app force closes!
Does anyone know how I can fix the problem?
Click to expand...
Click to collapse
Are you trying to delete archived emails? That's when I had the problem. Had to delete from computer.
I'm trying to delete messages from the inbox. Some messages appear to sync once, but won't sync again ever, so if I try to delete, label, or archive one of these stuck emails, the app either quits or backs up. I can delete them from another device just fine, but those specific emails stay stuck and won't go away.
As a temporary fix, I'm using K9 until I can figure out how to fix it.
I'm having the same problem, rooted stock 1.1. I found that this only happens on emails that are marked as read. So if I mark the message as unread, then I can delete it just fine. This problem only occurs occasionally for me. Doesn't usually cause the app to quit for me, just fails to delete typically.
Hope this helps.
I've found Gmail to be very unstable on 1.1. I've switched to k9 and am happy with it.
I had this exact same problem on my rooted stock 1.1.
The issue did not appear until after I updated CWM from 3.0.0.5 to 3.0.1.0, including installing the kernel with ext2, 3, & 4 support. I was never able to determine with any certainty if the CWM update/kernel had caused the issue because even after restoring to a backup I had made prior to the update it didn't fix things.
I also tried uninstalling gmail and reinstalling it, but that didn't fix it either. I scoured the internet for a solution but couldn't find one. Eventually, I got so fed up that I completely restored to stock and took the opportunity to upgrade to Froyo. The problem did not carry over to Froyo, fortunately.
Nevertheless, this error shouldn't be happening on rooted stock 1.1 and it didn't for me for most of the time I used Eclair, so I'm not advising you to drop Eclair by any means. However, you might want to consider restoring to stock and starting over.
I noticed the same issue. Was not present when booted to Nookie Froyo on an SD card. I'm back to running the stock rooted OS, so I still see this GMail problem.
I'm just waiting for a good SD version of CM7 that has the market and soft keys preinstalled, preferrably that runs like it does on Nookie Froyo.
Anyone ever find a fix for this?
sent from my nook color using tapatalk pro
No, but the good news is that a stable release of CM7 (aka Gingerbread) is nearly upon us. I think pretty soon Eclair and Froyo will be obsolete as far as the Nook goes.
My solution to this was to mark as unread and then delete, the app no longer FCs if I delete that way.
However, not all emails seem to trigger this problem
Hi, I am a somewhat new user here starting originally with xtrsense 4.6.5. I am now using v 5.0.1 but I believe all the xtrsense roms use the original sense message app from stock 2.1.
My issue is that the messenger doesn't seem to split the messages up before sending them. From what I have read this isn't a problem for verizon users but I am not on verizon. I have set up my apn, prl, and everything else manually to get the phone to work, but this is the one last bug that I haven't been able to solve.
I know that I could use go sms or handcent, but I kinda like just sticking with htc's messenger. Does anyone know which files I could edit to help change this. I just downloaded the android sdk today so that I could poke around from the computer instead of just on the phone itself with a file manager. Also out of curiosity, where is the mms max message size stored? I think the default 1.2Mb is working fine but I want to play with some of the mms settings to see if I can get a better quality receiving/sending. I think it's just that my user agent isn’t really understood on this carrier, so I should change it to an android phone that they do have.
For the life of me I cannot figure out why this is happening. I have rerooted and re-odin'd froyo countless times and always have the same problem. After a while my texts stop sending, I will go to send a text and it shows a timestamp and says 'sent' then I'll exit messaging and won't receive a response from whoever I'm texting. I open up messaging again and I see the timestamp change to whatever the current time is and says sent, I've noticed if I put the phone down and watch that the sent timestamp changes with the time. The messages never send though, as no one receives them and also it is only with text messages because MMS works fine. Example: I'll send a text at 2:05 pm, I'll look at my phone again in 10 minutes and the text will say 'sent 2:15 pm'. This only happens after a certain amount of time has passed from a new flash, a day, a few days, even have gone a week or so before it starts happening. A data complete data/cache wipe will fix it temporarily, then I have to wipe and start over... Maybe I've been doing something wrong or have been flashing corrupted files?
I've never run into this, but since you say mms works I'd try an alternate mms.apk or try an alternate app such as handcent.
if you want to remain using a stock SMS app look at my previous posts for an alternate mms.apk and instructions on how to replace it over your existing mms.apk from your system/app directory.
if you decide to try handcent and it works whereas your stock SMS app fails, then signs point to the mms.apk.
I'll give it a try, although it seems no matter what sms app I use or no matter what rom I'm using the sms function breaks after a certain amount of time forcing me to do a complete wipe and reinstall/reflash.
so then you are saying you have tried other SMS apps like handcent?
Yes and always the sms breaks after some time :/ idk why but the only fix I have found is a clean wipe.
tapatalked from my KangBanged Fascinate
I want to revive this thread, because the EXACT same thing is happening to me!
Currently running EH03 radio, KGB_FA16 kernel, and Super Clean 3 Milestone 2 on my Fascinate.
The Problem seems to have started on March 28th, and at the time I was still running SC3 Milestone 1. It took me until yesterday to realize that none of my text messages were received by anyone I sent them to since March 28th. Same symptoms; messages appeared to have been sent, time stamp that changes, etc.
Last night I tried a few things to fix the issue:
- Disabled Voodoo and System Lagfixes via CWM
- Wiped Davlik Cache
- Flashed SuperClean 3 Milestone 2
- Updated roaming capability (*228, option 2)
- Just installed GoSMS
In GoSMS, all of the outgoing messages since March 28th have flashing green arrows next to them... What does that mean?
If someone could point me towards the android native mms.apk, I can try re-installing it.
I am running out of ideas... I am going to Odin the EC09 radio tonight and see if that fixes it. Otherwise, the only other option I can think of is to do a full wipe and start over from scratch...
Any thoughts??
Bump.... Thoughts anyone? Beuler?
Should I just bag my whole current config and just try a different ROM!?
Looking into CM7...
It's been a week now and I still can't send any text messages.
I receive msgs but unable to respond back...
I thought it was because I finally updated to Jellybean (I've had ICS for awhile so I thought I should just stick to that) but then I downgraded last night to ICS and I still can't send messages.
well today I tried fixing it but still no luck, although I tried sending an MMS instead, I sent myself a picture and it worked! even tried it to other numbers and they received it. I also tried adding a text with the picture and it did work. but it's still not working when I just type in a text...
so anyway in short, I can't send SMS but can send MMS (and receive messages as well)
also extra: I can call people but whenever they call me it comes up as unknown number...
Does anyone of you know what might be the problem? How can I fix it? Thanks
EDIT: and btw I already checked the message centre number and it has the right number in it so I don't think the issues w/ that
I suggest using titanium backup to store user apps and data, then using mr.cook's rom wipe script to allow you to start from a blank slate, then re-install the desired firmware (whatever version)
You could work at fixing this issue individually, but (to me) it's a sign that something more fundamental went wrong, and that other issues may be soon to follow.
It isn't clear whether you upgraded to a stock jellybean, or maybe a 4.1.2 custom jellybean, or maybe a 4.2.2 custom jellybean, or a 4.3 jellybean. The latter, a 4.3 upgrade from ICS has the highest potential for weird issues if a thorough rom-wipe isn't conducted... whichever path was taken, The i777 runs all versions of jellybean well, and something like this suggests that the "upgrade" was not conducted from a clean slate, hence the suggestion for a rom-wipe and re-install.
-Cyril
can't text
Are you unable to text because a keyboard won't open? My daughter couldn't text (never figured out why - she always had a keyboard appear) so she got a replacement, and when I inherited her phone because mine has battery issues, I go through periods when I can't text because no keyboard appears. I have to into settings and play around with assigning a default keyboard before it will finally appear. Doesn't matter if I'm using the stock keyboard or one I've downloaded from a VERY reliable source - I still have to reassign and reassign and reassign to make it work. Powering off the phone doesn't do a thing.