Related
Has anyone successfully got phonealarm working on a Titan or under WM6.1?
I have a new work VX6800 and dont want to get woken up for status emails at 3am, but do want to know if there is a problem. So I set up phonealarm to sound only for specified email addresses.
So far the different profiles have only got me a phone that alerts for every mail or no mails! not quite what I was after.
I can go in to more detail of my config if anyone can help. I also have a test case open with phonealarm, and will update if I get a reply if anyone has the same issues.
Thanks
Yes, I have it working
I have it working and my trial just expired so I need to go buy it. It seems to be the best app to accomplish the goal, I'm in the same boat and use it as you described.
I was hoping it would also work with Pocket Informatn but it looks like the other app they sell will do that so I think I need to buy both.
If you get me more details on what you setup I can tell you what I did. My alerts are based on different subject messages / priorities on my inbound txt (SMS). I've not yet worked on different times (can't recall if it does that) but do notice that different profiles do in fact impact the sounds played.
-Scott
Thanks for the reply, at least I know that there is not a hardware issue now. PocketMAX support also replied and said it was something to do with the repeating alarms that I set to "no alert".
I will test this later and see how I get on.
PA
I have been using phone alarm since it was in its 1.0 state.
I have my phone updated to 6.1 and it works fine.
I've been reading about this bug for awhile now and it finally hit me. What happens is if contact A sends you a txt message and you respond. The message thread will show that your response went to contact A, but the reality is that A may not have received the response, however C,D,E,F, Z,Y and X did! It seems to be totally random, will happen regardless of the SMS app or ROM you use and can be quite dangerous. This bug renders my N1 virtually useless. Anyone else experience this or has an update on the fix for this dangerous bug?
I recommend anyone with an Android phone to be use extreme caution when sending txts or mms messages as you never know who may actually get it
Have read about it, but it's never happened to me.
Can you reproduce the bug reliably?
Can you dump the logs (/proc/kmsg and logcat, or bugreport) immediately after it happens?
Any pattern connecting recipient A and the rest?
Nightmare!
Sent from my Nexus One using XDA App
How come that not even one person from those reporting having "this bug", wants to help find out, what it is? Very interesting.
I have found that using handcent resolves this problem for me.
Sent from my Nexus One using XDA App
My wife have experienced the problem twice with Galaxy S, I haven't have similar troubles with my N1, although every now and then it takes time for some messages to go through. That is probably due the carrier, not the device.
Sent from my Nexus One using XDA App
The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!
cymru said:
The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!
Click to expand...
Click to collapse
I have this too in a pre 6.1 nightly...
But it's not the first time i hear the bug that SMS are sent to everyone, so it definitely exist
Sent from my Nexus One using XDA App
I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.
Jack_R1 said:
I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.
Click to expand...
Click to collapse
I can assure it is a bug and a major one. It is well documented if you google it. It appears to be across many different hardware platforms and therefore is most likely a source code issue written incorrectly in the android OS. And just because the 15 people you know aren't having the issue does not mean the rest of the world isn't. This is my 3rd android phone and this is the only one that does it and from I've been reading there are many others who are also having this random issue...I assure you, this isn't something that someone can do by mistake or accident...
In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?
It's happened to me.
I receive certain friend's facebook updates as sms. One time I got the facebook sms. I closed it then replied to another friend's sms. Guess what happened.... what I sent to my friend got sent as a comment to my friend's facebook status.
Looking back at the sms log, I definately wrote my reply to my friend, not the facebook sms, but somehow it was replied to the facebook sms.
This bug has been around since Android existed.
There's really no way to debug this I don't think, unless you only have a few contacts that will text u if you write something weird... cuz having a phone full if phone numbers, your text can be sent to any number, even non mobile phones, you wont know since you thought u texted the right person.
Sent from my Nexus One
There's a ton of ways to debug everything, including even specifically modified SMS app for dumping debug data - it's an open OS, yes? If I got some beta application versions for debugging from app devs to test things, I'm sure Google wouldn't do less to debug it.
For starters, the next SMS I'll check the records in kernel log and see if there's any useful data to start from there.
Jack_R1 said:
In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?
Click to expand...
Click to collapse
Well I think you bring up two entirely non-related issues... First, if you google it, you will find a vast amount of people all having that same issue, which in my mind establishes the "well documented" part of my statement. Secondly, as far as me or anyone else participating in debugging, I would love to, but it's a little out of my sphere of knowledge. If you could give me a little insight into what needs to be done, I would be more than happy to do what I can to help solve the problem. This $500 phone is totally useless to me if I can't be certain who will be receiving my txt messages. Mainly, I've been waiting and watching in the hopes that google would get involved and resolve this issue without my having to get involved. It would appear that this goes back a considerable amount of time.
Can you list out a step by step process to go about this so that all who are having this issue can also participate? What should be my next step
To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.
It never happened to me, and I've sent 12000 sms from my Nexus. Try using Handcent until this is officially fixed. Handcent is free and many people say it's not affected by the bug.
Jack_R1 said:
To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.
Click to expand...
Click to collapse
This is why I haven't, as you say, participate in resolving the issue...the level of of debugging required to get to the source of the problem is deeper than a non-developer like myself can go. And for the record, this is NOT related to the facebook app in anyway as I do not even have that app installed. This is 100% an Android code issue...
Are all your contacts Gmail-synced contacts?
Does it happen frequently enough to try to debug?
This is what happens with my N1:
I get a new text message, alerted in my notification bar
Rather than open it from the notification bar, I open the messaging app and tap the first message (just a habit, I guess)
The ninth message opens instead of the first one
I'm not sure if this happens every single time, but it does happen frequently.
I'm wondering if it might be a bug in CyanogenMod instead, I've only started noticing it recently.
PS: I do not have a Facebook account nor any accounts synced with it. The only contacts I sync are my Google contacts.
I am very new to Android coming from Palm Pre and I purchased Droid Pro and activated it with Page Plus everything seems to work fine except I can't receive or can't send any plain text messages any kind. I haven't been able to receive or send any ever since I got this activated. I have tried everything I could.
I did activation multiple times and still no luck! I am very frustrated at this point and don't know what to do. I really love this phone and it works great including web data, calls but the stupid text messages will not work at all.
As soon as I send a text message I get an instant error message saying text message not sent and it does that for every message. This is just driving me insane since I text more than I talk.
I am getting close to my last resort is the reset this phone to factory which I don't know how to do. My brother uses Droid 2 Global and Fascinate on Page Plus Wireless with no problems. I tried calling multiple sources and no one is willing to help me.
Please help me if you can.
When this happened to me on Verizon, I would have to reboot my phone to get messages to send. I would suggest trying a 3rd party messaging app, such as HandCent, GOSMS or one of the other, reputable ones on the market.
There is a communication error in the Pro with the Verizon servers that will get 'backed up' from time to time and messages will not go through. Motorola is aware of this problem and is supposed to of sent out an update for this to help avoid this problem.
Being on Page Plus, I would hope that it's a similar issue.
Another thing I would suggest is to make sure Wifi is turned off on your phone. The Pro's have a different set of protocols for messaging when Wifi is active.
I hope that this helps you get your phone squared away ^.^
I send out the same text to a group of people quite often and I get a message saying messenger is sending a large amount of messages do you want to allow this? I have to click on it for each message that goes out. Is there any possible way to change the limit? I know you used to be able to set it to anything you want in settings/security but it's not there anymore. Any help would be greatly appreciated...this is so annoying.
Have you tried GoSMS Pro?
Maybe I've never sent to as many as you, but I've never encountered that warning or behavior. I've used GoSMS for several years.
I've only seen this when I send many messages in quick succession (either with Google Messenger or something like Tasker). There should be a checkbox that says to always allow.
I'm also looking for a solution. I was using ResurrectionRemix (a CM based ROM) and it has an option to set the text restriction. So, it CAN be done. We just need to know WHERE the code is so that it can be changed. I can't find any search results explaining how to accomplish this. That SMS Limit Unlock app doesn't work on later ROMS.
After hours of searching today - it appears that the setting has been moved into the framework?
com.android.internal.telephony
https://android.googlesource.com/pla...geMonitor.java
I hope I'm wrong as I'm no Android dev.... But, if I'm correct the only way I know of to "fix" it is to make the change in a custom Android build/ROM.
This SUCKS as I use mass texting for business purposes (communicating with many individuals who sign up for contract work). I really like Android N (along with AndroidPay) - but, looks like I'll be going back to M (on a custom ROM)...
If anyone locates/determines a way to alter that file using RootExplorer/Sqlite or some other way - please let me know.
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.