Related
Hi all - new to this forum so apologies if the question has been posed already. I couldn't find a similar thread.
I've been having consistent trouble since getting my VZW Droid 2 in September with the phone not delivering important things like emails, text messages, Google chat messages and WhatsApp messages after long periods of screen inactivity (ie. an hour).
I'll turn on the screen and unlock it, then it goes and fetches those important messages like "I'm on fire - please come put me out now!". Suddenly I'll go from zero notifications to 10 of each.
I am using K9 mail, WhatsApp, Handcent SMS, Gmail, Twitter and all seem to be affected by this.
I checked all my settings, and it's not set up to sync only on wifi or anything, and each application is set up so that it should be sync'ing in the background.
I thought 2.3.20 was supposed to fix this issue, so I made sure to update the phone. However, I'm still having issues. I know I did some things to optimize the paltry battery life when I first got the phone, but can't find anything that should be causing this - and can't remember everything I did.
VZW's answer was to do a full factory reset, but I'd like to avoid that if at all possible because I'm too lazy to put everything back the way I have it.
Advice?
Thanks
Try:
Settings > Battery Manager > Battery Settings and making sure its not set to anything other than performance mode as anything else will do exactly as you are describing.
I know custom ROMs may also cause issues.
Okay, i'm rooted and have been Running MIUI for a few months without issue.. Last Friday i did a FULL WIPE (factory reset, cache and delvik) and upgraded to the newest 1.7.15 MIUI ROM -- everything worked fine.. except for my text messages.. I wasn't receiving any.. I could send them out fine.. i just dont get any.. so after i tried to do EVERYTHING to fix it.. nothing worked, and i decided, oh well I'll flash back to Sense until next release.. Well i flashed back to sense (Did a full wipe, then a nandroid restore) and my Text messages STILL do not work.. I have never used Google Voice, but i was told that could be the cause, so i opened it and turned it on.. and i was able to get text messages to my google voice box) I do not like google voice, nor do i want to use google voice.. So i then went from my PC and disabled google voice from within my PC's browser, and i then uninstalled it. Now i'm back to not being able to receive text messages...
Does anyone have ANY idea what so ever could be the cause of this? I am completely stumped. I thought 100% it was an issue with MIUI, but i cant even get them on my Sense ROM.. All of my calls and sent text messages work fine, but i receive no incoming text, nor notifications or anything that i'm getting any texts... Yet if i use google voice, i can get my text messages..
Any help would be greatly appreciated
I have also Updated my Profile and PRL
if i go into HTC Software Updates it says there is a 2.3 Gingerbread update 4.24.651.1 (6.07MB)
but i am on the rooted stock gingerbread version of that i believe, unless another update came out after the original June 4th gingerbread release, because ever since then i've been on MIUI anyway
EDIT:
I just attempted a Full factory reset, and i still cannot get any text messages
I am chatting with sprint and he told me to try these codes in the phone dialer
##DATA#
##72786#
and they used to work, but now it just freezes my phone dialer and nothing happens...
What the hell is going on? EVERYTHING ELSE works just fine except for receiving text messages
google voice
if you have sprint with Google Voice Enabled on every time you install Google voice it disables incoming text to your number, click on the gear on the right top corner on your Google voice account page - Click Voice Settings - Click Edit on your phone number - make sure this is checked.
Text Settings:
X - Receive text messages on this phone (mobile phones only)
Question #2 --
The sprint guy i'm talking to said he will waive the $100 insurance fee and ship me a new phone if i want.. If i agree to this, will the new phone ship with a 2.3 gingerbread version that is unable to be rooted?
Or have they finally rooted that also? Last i checked i heard people who accepted the OTA update lost their root and there was no way to get it back
I actually just got a refurb a couple of days ago, they seem to all be coming with new hboot. So no root yet.
Well i did re-download google voice, but i never enabled it or even ran it for that matter, and i have sense enabled it and used it.. then disabled it and i still do not get any texts
pulazki said:
Question #2 --
The sprint guy i'm talking to said he will waive the $100 insurance fee and ship me a new phone if i want.. If i agree to this, will the new phone ship with a 2.3 gingerbread version that is unable to be rooted?
Or have they finally rooted that also? Last i checked i heard people who accepted the OTA update lost their root and there was no way to get it back
Click to expand...
Click to collapse
Not rooted yet but there are a few people working on it. A few days ago a leaked video from AlpharevX showed they unlocked the 3d and sensation, and according to them this method works for all current HTC bootloaders. So if you don't mind not having root for a while get one, if not then don't switch. Who knows how long before a root method actually gets out for the Evo with 2.3.3. Could be today or next month.
did you try what i mentioned above go to google.com/voice (on your computer) and make sure that option is on. This only happens when you Enable your sprint number with Google voice.
Yes i have been on google voice all morning, but when i click on the gear in the top corner now nothing happens, i cant get into settings ever since i disabled google voice, all that happens is a little blue bar appears on the same page.. are you suggesting that i re-download google voice, set it up again and then i'll be able to go back into the account settings? because so long as it's disabled i am unable to view any google voice setting page
pulazki said:
Yes i have been on google voice all morning, but when i click on the gear in the top corner now nothing happens, i cant get into settings ever since i disabled google voice, all that happens is a little blue bar appears on the same page.. are you suggesting that i re-download google voice, set it up again and then i'll be able to go back into the account settings? because so long as it's disabled i am unable to view any google voice setting page
Click to expand...
Click to collapse
That's weird... it might be your browser it should let you add a number even though you don't have any on there.
google.com/voice?pli=1#phones | to go directly to settings page |
I found this thread in the google voice and my issue has apparently happened to this person also and he was not able to resolve it, and actually had to get a new phone.. Which is what i think I'M going to have to do, but i DONT want to do that because i hate SENSE, and i want to run MIUI... but there is no root for the new OTA 2.3 gingerbread, does anyone have ANY IDEAS? how can i completely disconnect google voice?
http://www.google.com/support/forum/p/voice/thread?tid=7a4e7d5494abe0d9&hl=en
Panic Eye.. I have re-downloaded google voice, and i am using it now.. as it's the only way i can get text messages, after searching and searching i have found a plethora of people who are having my exact same issue.. and i have yet to find a single one who has found a fix for the problem.. all of them say that sprint just suggests new phones to them.. this is nuts.. it's obviously a google voice issue, but no matter how many times i disable google voice from my pc, or from my phone, it doens't fix it.. I've even done a full factory reset and didn't log into my gmail account.. which should definitely get rid of any google voice crap, but it doesn't .. so maybe it's a phone problem? i have no idea.. i'm completely stumped
pulazki said:
I found this thread in the google voice and my issue has apparently happened to this person also and he was not able to resolve it, and actually had to get a new phone.. Which is what i think I'M going to have to do, but i DONT want to do that because i hate SENSE, and i want to run MIUI... but there is no root for the new OTA 2.3 gingerbread, does anyone have ANY IDEAS? how can i completely disconnect google voice?
Click to expand...
Click to collapse
Honestly I doubt it's your phone, it has something to do with sprint/google integration. I would try to convince a Sprint rep to deactivate and reactivate your phone, can't really think of anything else you could do besides attempting to re-enable Google Voice with the Google Voice app and try to access the settings on the browser again.
Bump -- Any help at all? Has no one else ever experienced this
not receiving sms
I believe I have the same problem. It's pretty frustrating.
I am not able to set a default dialer on my Nexus 4 running the latest snapshot of CM11. This problem has persisted for a while, but I just finally got around to addressing it. Whenever I click a phone number in a text message or email, it asks me which app to use, Dialer+, stock dialer, or Skype. If I select the stock dialer and select "Always", I am still asked to choose the next time I try to click a phone number. I've tried the following to narrow down the issue.
I uninstalled Skype, but was still repeatedly given the choice between Dialer+ and Stock.
I uninstalled Dialer+, but was still repeatedly given the choice between Skype and stock.
I froze all user apps except for skype and dialer+ and still repeatedly got the choice between all three.
If I freeze the stock dialer, I AM able to set one of the other options as default and it sticks.
This suggests to me that there is a problem in the stock dialer app. Has anyone else had this sort of problem?
Hello All!
I've been having this problem for a few weeks now and im all out of ideas of what to do.
Carrier: T-Mobile
Wearable: S3 Rugged
Extra Service: DIGITS
Coming From: LGV20 which never had these issues with the same plans and accesories
So to start, when i got the phone inittially during setup of the google accounts i noticed that my OTP SMS Pushes were not being received, or auto filling the information. I skipped past all of that and noticed that anywhere that OTP text were suppose to autofill in different applications, it would not even when i received the text and got a notification.
So after a while of using TEXTRA which was working fine, one day i stopped receiving ALL text not just mms. I was able to send but never was I able to get anything from anyone. I ditched TEXTRA and went back to the stock Samsung app and noticed that all text were there, even though it was not default. After using the Samsung messages app i decided to go back to textra, heres whats funny. After Textra did it's initial setup, it only showed half of the recieved text from up to that day. Messages were incomplete, some just had one reply from a user and nothing else. So I also tried this with Android Messages and it had the EXACT same message log as textra. Both were not receiving the full logs from the server. Today Android Messaging was working for a good part of the day, then it just stopped all of sudden again.
Can someone help me with this, I've wiped the cache and factory reset the phone. Ive added and removed the multi-line settings in the samsung settings. I've tried the legacy settings on textra. I've called the DIGIT's customer service to see if they could fix it but they made and interesting point that it couldnt be digit because it wouldnt interfere with 3rd part messaging apps. When i switch apps i always make them default, i wipe the app cache etc.
I have a gut feeling this has something to do with something with the default Samsung Messages app and it somehow restricting use outside of it.
I just wanted to reply and say that I've been experiencing the exact same issue and haven't had any luck Google engineering my way around it. For me, I'm seeing the issue with Signal, so I don't believe it's the 3rd party app's problem. I can send messages (SMS/MMS), but the Samsung Messages app is the only one that "receives" them. A strange workaround I found was to download Android Messenger, set that as the default messaging app, then set Signal as the default messaging app again. This worked for a while, but I think the Samsung Messages app recently updated, and it broke this again until I repeated the above workaround.
It's annoying enough that, without a fix, I'll definitely be flashing a completely stripped ROM on this phone once we have the ability to do so to get away from all of the Samsung apps that I can't disable. And don't even get me started on Bixby...
wjm3982 said:
I just wanted to reply and say that I've been experiencing the exact same issue and haven't had any luck Google engineering my way around it. For me, I'm seeing the issue with Signal, so I don't believe it's the 3rd party app's problem. I can send messages (SMS/MMS), but the Samsung Messages app is the only one that "receives" them. A strange workaround I found was to download Android Messenger, set that as the default messaging app, then set Signal as the default messaging app again. This worked for a while, but I think the Samsung Messages app recently updated, and it broke this again until I repeated the above workaround.
It's annoying enough that, without a fix, I'll definitely be flashing a completely stripped ROM on this phone once we have the ability to do so to get away from all of the Samsung apps that I can't disable. And don't even get me started on Bixby...
Click to expand...
Click to collapse
I haven't had any issues with my At&t model...Been using Yaata since day one (about 2 months).
Also, there are some "package disabling" apps in the play store that will allow you to disable any app you want, you don't even need to be rooted. It cost me $1.99 (or around there), but was well worth it! You can even completely disable Bixby, so the button is even non-responsive.
Having the same issue and I may have fixed it. I logged completely out of Digits on the phone (settings/cloud accounts/multi line/hit the ... menu and choose log out.
I have this same issue. No matter which 3rd party SMS app I use I have missing text messages on the T-Mobile S8. Has anyone fixed this? It is driving me crazy. T-Mobile replaced my S8 and the new one does it (not as bad but it does it more than I'd like). How can I resolve this? My friend haf the same issue, he has an unlocked T-Mobile working on AT&T.
I don't use Digits or anything like that... any ideas?
hi guys
all you need to do
go to setings
device maintence
battery
scrool all the way down to unmonitored apps and add your 3rd party sms app
youre welcome
This still didn't work for me and I am having the same exact issues. I have tried installing 2 different 3rd party messaging (Textra and Mood) and both were not working properly. I can send messages out just fine but when I receive them they are delayed (like 5 minutes or longer). Sometimes, I don't get the messages at all. Of course, the Samsung Messaging app (which I hate) works just fine. I have even "Force Stopped" it! What to do?
go into the stock messaging app, and turn off advanced messaging
Has anyone found a solution? I've been using textra for years & suddenly in March I started having this problem but with sent messages. All incoming texts are displayed but my sent texts aren't. I did try the 2 suggestions above. On a note 8, Android 8.0.0,Samsung experience 9.0.
SOLVED. I had the same issues and found the solution. Before you install your 3rd party sms/MMS you need to disable the default messenger. I uninstalled signal, disabled the built-in messenger, reinstalled signal. Now I can receive texts. Also my phone is not a Samsung.
Hi
I'm trying to get Android messenger working on this. I have message+ disable and cellular also disabled.. I gave Android message permissions but when I click on watch face with message logo
says no app installed.
SimpyD said:
Hi
I'm trying to get Android messenger working on this. I have message+ disable and cellular also disabled.. I gave Android message permissions but when I click on watch face with message logo
says no app installed.
Click to expand...
Click to collapse
Yeah, the Verizon face sucks, not much customization but you should be able do it in the android wear app on the phone, works for me. Just remove the message app tab and re add it ( first install the android messanger)
Use different face, watchmaker is great
Hi, I was able to change faces and such, but still unable to send messages with the android app and message+ is disabled. Also my microphone seems to not work, ok google doesn't work and a voice call the other person could not hear me.
kinda a pain. thx
I struggled with it for a bit as well. so what i had to do was do a factory reset (after updating wear 2.0). then somehow, i paired it to my phone, but skipped the rest of the initial setup stuff it wants you to do like giving it your phone number and setting up vzw message. first thing i did was disable all of the system apps like "phone" and "vzw messages" and/or wear24 app. Never having opened vzw messages, i downloaded google messages from play store. It works great now. google now works perfectly. i don't try to make phone calls off of it so can't help you with that part. but make sure you turn the cellular radio off after every reboot (just to save battery).
this is an amazing whatch for someone like me who does not *want* to have an lte watch. I just wanted a bluetooth only watch with a high res screen, big battery, modern wear processor for $80 shipped. - nfc and heartrate and swappable bands would be nice, but oh well. It gives me all of my notifications so i don't have to take out a phone during meetings and it's much snappier than my urbane was. - nfc, heartrate, and swappable bands would be nice, but oh well.
I've disabled msg+ and installed android messenger.
I can receive texts, but the only way I can send a text is via google assistant because even though the app is installed, the icon wont show in the app drawer.
But after I go through the voice process (send txt to blah blah blah), it errors out on sending it.
I've granted all permissions
Since there are not many Wear24 threads here I will see if any of you can help.
I agree with mistermojorizin - for the price it is now if is a good watch. My issues is this:
I want to use LTE and have it working fine. I can send and response to messages from Message+ (ugh), but when I use google assistant to send a message - which I have done often with other watches - I says sending with watch and hangs on a spinning wheel.
Anyone else see this and have a suggestion? If I could change the app that Assistant uses to send the message to Message+ that might solve the issue, but I haven't see how to do that.
dragonash said:
I've disabled msg+ and installed android messenger.
I can receive texts, but the only way I can send a text is via google assistant because even though the app is installed, the icon wont show in the app drawer.
But after I go through the voice process (send txt to blah blah blah), it errors out on sending it.
I've granted all permissions
Click to expand...
Click to collapse
If you try and send text message but it says send from watch and just sits there spinning, you need to disable VZW from sim info. That will also help battery life too. Only thing not working on my watch is the mic in a call. I'm using it with BT/WiFi only with my P2XL on T-Mobile.
I have installed Android Messenger and it works for me with the voice to text, I like that one a lot.
The watch in general is great, I wish that the speaker was louder (as I thought that it will be) and the NFC to be working. I paid $94 CAD for it, you can't even get a used Moto360 first gen in good condition for this price, never mind a high end device.
The band could be replaced, if you don't have Verizon for a provider why would anyone care for the antenna anyway? I have a Moto360 first gen and this is better with the Android Wear 2.0 and bigger battery, after 11 hours of moderate usage I am at 51% of battery remainig which is pretty decent.
Happy so far
vwauditech said:
If you try and send text message but it says send from watch and just sits there spinning, you need to disable VZW from sim info. That will also help battery life too. Only thing not working on my watch is the mic in a call. I'm using it with BT/WiFi only with my P2XL on T-Mobile.
Click to expand...
Click to collapse
Thanks for the siminfo trick. I think that might have done the job for getting voice assistant to use android messages instead of Verizon messages+. Before that, I could respond to text messages but just couldn't initiate a message using voice.
I also disabled the Verizon apps where I could. And I "deleted" Verizon as a carrier altogether (in the siminfo area). The other things I did to get going (and not wait for the system/google updates) was to sideload android wear 2.8, google play services, and finally the google app using ADB on my iMac. It needed all three it appeared.
Here's the command for ADB:
adb connect [IP of your watchort] (I didn't use a port)
adb install -r [app.apk]
Liking the wear24 quite a bit so far as compared to my old Moto 360 1st gen which is still going strong after a battery replacement. Kind of wish the watch diameter was as wide as the Moto 360. I'll do a video comparison of the two soon (makethistechwork.com).
Unable to send text via assistant after following steps
vwauditech said:
If you try and send text message but it says send from watch and just sits there spinning, you need to disable VZW from sim info. That will also help battery life too. Only thing not working on my watch is the mic in a call. I'm using it with BT/WiFi only with my P2XL on T-Mobile.
Click to expand...
Click to collapse
Thank you for the info! I'm using this watch with a Pixel XL and Tmobile just like you. However, even after disable version from the sim info, it still doesn't work. I have the same issue as before where it says that could not connect to a phone. I've included some screenshots showing my sim-info to illustrate what I'm talking about. Kindly suggest anything else that I can do since I've tried everything including factory resets.Thanks!
After updating the wear app and android messages, I can see previews of all my text threads, but when I tap the threads, messages crashes. Has anyone else seen this with all the recent updates?
EDIT: After futzing with permissions for a few seemingly related apps, Messages no longer crashes on me. I could swear I had already tried all of the changes I made this last round, but maybe I missed one every other time. If anyone else runs into this, I'll be happy to share permission settings to see if it helps.
scooter1979 said:
After updating the wear app and android messages, I can see previews of all my text threads, but when I tap the threads, messages crashes. Has anyone else seen this with all the recent updates?
EDIT: After futzing with permissions for a few seemingly related apps, Messages no longer crashes on me. I could swear I had already tried all of the changes I made this last round, but maybe I missed one every other time. If anyone else runs into this, I'll be happy to share permission settings to see if it helps.
Click to expand...
Click to collapse
If You wouldn't mind sharing what You did/have set for Perms I would appreciate it.
iamtek7 said:
If You wouldn't mind sharing what You did/have set for Perms I would appreciate it.
Click to expand...
Click to collapse
Sure. First, I'll mention that I have removed all of the VZ carrier information, as suggested in this thread, as I don't use nor plan to use VZ, so that may or may not have anything to do with it.
I also disabled Message+, the default text app, in system app settings. I did not touch permissions there.
On to permissions... I pretty much went with all or nothing, looking through system apps and messing with anything that might have to do with messaging...
Android Messages: All on
Phone: All on
Wear OS: All on except storage
As I said, I had reset the phone a few times, and the last time, directly off of reset, my order was: update Google and WearOS system apps, disable Message+, install Android Messages, change permissions, open Android Messages. I didn't try to open Messages until after checking permissions.