i just installed this Rom on my Nexus:
FRF83-update-nexusone-rooted-signed.zip
i wiped everything before installing and everything is running smooth.
i love the Rom, but i started noticing that ppl kept texting me back ? marks
or saying what was i talking about. i guess texts are scrambling and sending to diff ppl, and im receiving text's under ppl that didnt originally send the text if that makes any sence.
is any one else experiencing this? i remember reading an article about it i think on engadget or gizmodo. but im wondering if its a ROM or Google thing.
in all fairness i did use the search button, no flaming or being rude or else u get a stick trown at you
this has been reported long time ago on 2.1 when the nexus first came out. then other phones reported it like the droid. google never figured out what exactly caused it, it was baffling. i've always used handcent insstead just because of this "possible" glitch. i could get in a lot of trouble if i sent a text to the wrong person.
Weird this is the 1st time its happend to me or any one telling me about it. i rebooted hopefully it wont happen, cause i can also get in trouble sending wrong texts to the wrong person. The GF was already asking ?'s because the text she got wasnt related to anything we talked where texting about.
Android Phones Play “Chat-Roulette” With Your Text Messages
I have always been a big fan of Google Android phones. Sure the user interface may not be as polished as the iPhone. I admit the Exchange support might not be as tightly integrated as it is on the Blackberry. But, I’m a geek and I’m willing to put up with some annoyances as a trade-off for speed and flexibility and customization. And I’m not alone. Market researchers Canalys and NPD Group both recently published reports stating Android was running on > 40% of all smart phones in the United States. It would seem Android is destined for dominance.
Except somewhere along the way, Google seems to have forgotten first and foremost Android phones need to be phones. And that is why I’m seriously considering making the move to Blackberry or Windows Phone 7. For the last six months now I’ve been dealing with a huge flaw that makes my phone unusable for SMS texting. From what I’ve been able to tell using analytics provided by Google’s developer site, as many as 77% of Android phone users are at risk of having their text messages sent to a random contact.
That sounds unlikely right? I mean you pay upwards of $200 for a smart phone, and next to making phone calls, sending SMS text messages is probably the most used feature of the phone. But it’s true, and if you don’t believe me just type “android SMS wrong contact” into Google’s search engine and see how many hits you get. It’s astounding. It’s happening. And Google seems to be ignoring it altogether.
The first time I responded to a text message from recipient A, and it went to recipient B, I just wrote it off to user error. I was in a hurry. I fat fingered it. Who knows, right? In time though I’ve begun to qualify and quantify this serious bug and disaster waiting to happen. The worst part is you don’t even know your text message went to the wrong person until you get a call or new message from someone in your contact list asking “what was that last message all about?”
On the sender’s phone, the text message actually shows as sent to the correct recipient, yet I’ve been able to get all three parties with their phones to sit down in one room and verify that in fact the intended recipient did not receive my text, and a random contact did. I will put up with a lot of minor issues for a cool phone, but having my privacy threatened is not one of them.
What irks me the most is that owners of these phones, me included, have no recourse. The bug is part of the core operating system, and has been since Android 2.1, (though it seems worse with 2.2). Phone model doesn’t matter. Using a third-party SMS application won’t help. Contact your phone carrier and you will be told to do a factory reset then call the phone manufacturer. Contact the manufacturer and you will be told to do a factory reset then get in touch with your carrier. This is a flaw with Google’s code so how is it they managed to slip out of the support loop altogether?
Ah, I think now we have reached the heart of the problem haven’t we? By making it an open source solution, Google isn’t really accountable. Or are they? I guess that depends on you and me. Google has a vested interest in fixing any flaws that are impacting their continued effort for world smart phone dominance. If those of us who have made this platform so successful for them draw a line in the sand perhaps someone at Google will take notice.
The issue at hand has been logged in the Google forums for some time now. Sadly, it’s rated as only having a priority of “medium” and I’ve yet to see anyone from Google comment on the current state. I would urge any of you who have Android phones to log into the Google forum and star the issue. You can find the link in the code google forums. In the mean time, I’m going to continue evaluating some of the new Windows phone offerings. Just in case Google decides new UI bounce effects on widgets are more important than where my SMS text messages end up.
I've never had a text message go astray, personally.
I just had this about two or three times.
The chosen recipient didn't got my text message. But to be honest, noone contacted me, that he got my message, and the reciplient has a very bad mobile network coverage. So hopefully noone is laughing his ass off about my stupid messages
Related
Do you guys have issues with sometimes not receiving a text?
I have an HD7 with Tmobile USA
and I've had ppl saying they text
me yet they never did
At first i thought it was just lies that
guys tell but i've gotten the same
story for certain friends.
Just wanted to know if it is isolated
or if someone else was having the
trouble i am
Check the number in messaging settings and make sure you haven't changed it, otherwise I can't think of any other reason, assuming you have not added message blocking or some other feature that limits usage
maybe a network issue in your area. I would talk to t-mobile about it and they can check it out.
I haven't had any problems with texts.
The odd thing is that I have had a vibrant, g2, and mytouch 4g with Tmobile in th same area and those never had an issue
tj
It seems like it only happens like 20% of the time but i feel bad for fussing at ppl for not texting back when it is my phone
and i've noticed this is on both HD7
But it is not a MAJOR problem...just a minor annoyance
lol and i refuse to call tmobile's customer service until next month. I finally can transfer to postpaid instead of being on flexpay aka hell. Trying to explain a problem to them is murder. The language barrier alone will make this whole situation worse...
Another issue that pops up
I decided to use the feature of sms confirmation to let me know when it is sent to the users i send the text or pic mail to(which is annoying) because if i send my usual 1,000-2000 msg daily i will get the same amount of texts from my phone telling me that it has sent the text to the recipient.
Anyway, a new issue pops up that when i send a text, it will say it can't be sent and it will resend later. Even if i have full service, it sends me the message and i literally can't text anyone
then after about 10-15 minutes, it will send it automatically with no issues then sporadically pop back up.
This is shocking because i really have had no issues with WP7 or my hd7 aside from this and now randomly that pink hue on the camera started appearing
the pink on camera seems to be fixed with the ..10u.. rom for a lot of people
i can't say anything on the sms delivery reports, but i know tmo on the east should have way better reception than west
missing texts
I have T-mobile as well. My HD2 would drop most inbound texts. I had to do a hard reset to get it to start working reliably again.
Haven't had the issue since I switched to the HD7.
It is working great now. Idk what was going on with my phone.
So, I have a really annoying telemarketing company who is calling me on a semi-regular basis. I've already asked them to stop calling me, twice. I'm not really the kind of person to be stirring the pot and reporting them (too much work)...instead I would rather screw with them.
Since Google Voice allows me to have custom greetings for certain phone numbers, I would like seriously mess with whoever is calling me.
Does anyone have any ideas for what my greeting should say/be for my pests?
Inform them that they have lost the game, and proceed with a rick roll
Tell them that they've inherited £12,000,000 and you're a Nigerian prince that only needs their name, address and bank account details to send it to them.
Sent from my GT-I9100
Play a recording of a previous conversation with them?
I ran across this one which sounds good.
"Another good one is to start your answering machine message with the phone company phone number error/disconnected tones and then continue the message. It tricks the computer doing those auto-dial/automated message calls to delete your number from the list and stop calling you."
"Hello, you have reached the Transgender hotline. We're sorry we're not able to take your call at this time, but one of our agents will call you back on this number as soon as they are available. We see that you are a regular customer so you will be given priority over other callers. In the meantime you are welcome to browse our gallery of escorts at www.transgenderplaythings.com where we guarantee you will find a 'friend' who can meet all your needs!
Thank you for calling, goodbye."
Let them explain that to their boss when it comes up in a routine review of their recorded calls.
As I have no sense of humour tonight I'm going to suggest that next time they call, demand a supervisor/manager and then tell them, very politely that they are ++++'s and you have no interest in their piss poor service. If they don't stop calling you despite your numerous requests then you will be left with no option but to take matters further.
Did I ruin the mood?
Good.
Carry on.....
Sent From My Fingers To Your Face.....
You guys are genius!
Seriously, there are some good ideas in here. Keep them coming! Maybe I will put each of the messages on rotation and switch them out every once in awhile.
I am curious about the trick with playing the message of "this number has been disconnected...etc," I will use that one after I have tried out some of the others in case that one actually does the trick!
"Hello, 911 emergency, which service do you need?"
"errr, sorry i think i have the wrong number.."
"Sir, are you aware that it is a federal offence to misuse the emergency service line? Do you have an emergency to declare...?"
"..****, so sorry...i think i misdialled...bye.."
Attackers could force phones from Google's Nexus line to reboot or fail to connect to the mobile Internet service by sending a large number of special SMS messages to them.
The issue was discovered by Bogdan Alecu, a system administrator at Dutch IT services company Levi9, and affects all Android 4.x firmware versions on Google Galaxy Nexus, Nexus 4 and Nexus 5. Alecu is presenting the vulnerability Friday at the DefCamp security conference in Bucharest, Romania.
Class 0 SMS, or Flash SMS, is a type of message defined in the GSM specification that gets displayed directly on the phone's screen and doesn't automatically get stored on the device. After reading such a message, users have the option to save it or dismiss it.
On Google Nexus phones, when such a message is received, it gets displayed on top of all active windows and is surrounded by a semi-transparent black overlay that has a dimming effect on the rest of the screen. If that first message is not saved or dismissed, and a second message is then received, the latter is placed on top of the first one and the dimming effect increases.
When such messages are received, there is no audio notification, even if one is configured for regular incoming SMS messages. This means that users receiving Flash messages won't know about them until they look at the phone.
Alecu found that when a large number of Flash messages—around 30—are received and are not dismissed, the Nexus devices act in unusual ways.
The most common behavior is that the phone reboots, he said. In this case, if a PIN is required to unlock the SIM card, the phone will not connect to the network after the reboot and the user might not notice the problem for hours, until they look at the phone. During this time the phone won't be able to receive calls, messages or other types of notifications that require a mobile network connection.
According to Alecu, a different behavior that happens on rare occasions is that the phone doesn't reboot, but temporarily loses connection to the mobile network. The connection is automatically restored and the phone can receive and make calls, but can no longer access the Internet over the mobile network. The only method to restore the data connection is to restart the phone, Alecu said.
On other rare occasions, only the messaging app crashes, but the system automatically restarts it, so there is no long term impact.
A live test at the conference performed on a Nexus 4 phone with the screen unlocked and running Android 4.3 did not immediately result in a reboot. However, after receiving around 30 class 0 messages the phone became unresponsive: Screen taps or attempts to lock the screen had no effect. While in this state, the phone could not receive calls and had to be rebooted manually.
A second attempt with the screen locked also failed to reboot the phone because only two of over 20 messages were immediately received. This may have been caused by a network issue or operator-imposed rate limiting. The messages did arrive later and the phone rebooted when unlocking the screen.
Alecu said that he discovered this denial-of-service issue over a year ago and has since tested and confirmed it on Google Galaxy Nexus, Nexus 4 and Nexus 5 phones running various Android 4.x versions, including the newly released Android 4.4, or KitKat.
Around 20 different devices from various vendors have also been tested and are not vulnerable to this problem, he said.
This doesn't exclude the possibility that some devices from other vendors are vulnerable, but so far it has only been confirmed on the previously mentioned Google Nexus phones.
Alecu claims he contacted Google several times since he found the flaw, but mostly got automated responses. Someone from the Android Security Team responded in July and said the issue would be fixed in Android 4.3, but it wasn't, Alecu said, adding that this contributed to his decision to disclose the problem publicly.
"We thank him for bringing the possible issue to our attention and we are investigating," a Google representative said via email.
via PCWorld
Click to expand...
Click to collapse
What is your intake on this?
Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
TLDR
joke, Well since I can't achieve the effect (reboot and unusual behaviour) I am saying this doesn't affect my life & the way my nexus works.. so..
Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
My ... ummm, intake ... on this is that I never cease to be amazed at the lengths that a corporate security weenie will go to in order to justify his salary.
I recently retired from a large IT services firm in the US, and this is exactly the kind of far-fetched crap our corporate security people cited to justify taking away my Android connectivity to our Exchange servers. Grrrr...
JM2¢
Last I checked, only the provider can send class 0 messages.
This. No one can send them, and almost no carriers... at least in the U.S. use them. I have never seen a single one. The chances of getting 30 at one time is zero. It's a non-issue IMO.
If you want a crash bug, look to the iOS bug that caused any iOS phone or app to crash when a certain string of characters is displayed by it.
Unfortunately there is software out there that allows a user to send an anonymous class 0 sms messages, so I guess this bug needs looking at by the Google techies
Sent from my Nexus 5 using Tapatalk
I don't have a take on this
Sent from my Nexus 5 using Tapatalk
I award you no points & may God have mercy on your soul.
Lol but seriously, is this REALLY an issue?
Sent from my Nexus 5 using Tapatalk
cbutt said:
I award you no points & may God have mercy on your soul.
Lol but seriously, is this REALLY an issue?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not really concerned about this, just thought I'd create a discussion about it. Don't worry about my soul, my friend.
Sent from my Nexus 5 using Tapatalk
If anyone is that worried, ... https://play.google.com/store/apps/details?id=com.silentservices.class0firewall
Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
Meh... It's just a bug. Can be inconvenient if you reboot and don't connect to your network until you insert your PIN, but there are no security issues mentioned.
I'd be more worried about the bug in many american cell subscriptions that share SMS cost between sender and receiver. But fortunately I live in a sane country where only the sender pays for the messages
Hi everyone; I bought the LG G Watch R on Monday and, since then, I have been becoming increasingly frustrated with it: it seems that the only thing the smartwatch is good at is telling the time. Thus I am posting here, hoping that some of you may have had the same issues I'm having, and may know a solution to any of them.
First: I understand the watch is supposed to turn on when I move the wrist to look at it; however, it only does so ~5% of the times, while in other cases a violent shake is necessary to wake it up (most often, though, the only way is to tap the screen or press the button)...
Second, connection issues: when I'm speaking to the watch, it often happens that it starts recognizing words, but at some point stops and complains of being "offline" (while, instead the, phone it's connected to is on a very good WiFi connection); other times it says it's not connected to the phone (while the Android Wear app on the phone says it's connected). This may also happen after it has recognized all of the voice input: for example, after I tell it to set up an alarm, it shows it has recognized the correct input, but then goes "offline".
Third, inconsistency between what's displayed and what's really happened: after asking it to do a certain task (be it send an sms, answer a WhatsApp message or whatever), the watch often says that it was not able to contact google, or that I should try again "on the phone", while instead the action has actually been performed correctly! For example, I once sent the same SMS 4 times in a row, because it kept saying it hadn't worked.
Fourth, voice recognition: as of now, I have not been able to send one SMS without repeating it at least three times... Actually, this is probably not related to the watch itself, but rather to the google voice recognition software: I am Italian, thus the voice recognition language is set to Italian (I would gladly issue commands in English, but if I suddenly started to send all of my messages in English, most of those I know would think I've gone crazy: it would be nice to have the option to distinguish between a "commands" language and a "content" language); this means that, first of all, I have to say everything at once: for example, I must say (the italian equivalent of) "Send SMS to [contact] hello", because if I only say "Send SMS" or "Send SMS to [contact]", it doesn't work (I was excited about the new feature of 5.1.1, which has a list of contacts: it should theoretically be possible to choose the contact, hit "Send SMS" and send the message, but unfortunately, this causes the "Android Wear" app on the watch to crash unexpectedly).
Then, I have friends whose surname is made of multiple words, some of which may also be "first names" (for example, "Fabio" is a first name and "Di" is a preposition, but "Di Fabio" is a surname): this completely breaks the voice recognition algorithm, so that when I try to send an sms to "Alessandro Di Fabio" saying "ciao", I get an SMS sent to some other "Alessandro", and the text of the SMS is "Fabio ciao".
Punctuation is not always understood as such: for example, saying (the Italian equivalent of) "dot dot dot" sometimes results in the expected "...", but other times it is transcribed literally.
Finally, odd things can happen: if I try to send an SMS saying "ok, grazie!" (i.e. "OK, thank you!"), the text that gets sent is only "ok" (maybe the voice recognition thinks I'm thanking it?), and sometimes, even though the input is correctly parsed as "Send SMS to [contact] [text]", a Google Search starts...
I understand that voice recognition, after only 50+ years of development, may still be in its infancy, but it seems odd to me that the release of a device which nevertheless completely relies on it may be allowed or even conceived, given the current state of the art (if this is the current state of the art).
I know this may seem a rant (and it partly is, since I feel that I have wasted 200€ on a glorified toy watch), but I'm posting here for three main reasons: first of all to understand if I'm alone (maybe I got faulty hardware, even if I don't think so); second, to advice those who may come here still undecided not to buy the device; and finally because sending feedback to google or posting in its "community support" forums didn't have any effect (not even an automated mail saying "thank you, we got your feedback!"): is there someone else I should try complaining to?
1. Change to always on, accelerometer is a little buggy sometimes even on the moto watch same issues.
Connection issues and voice recognition, if I was having those I would return the watch for a exchange unit could just be a bad watch.
Hope that helps some
Need help diagnosing and solving a bizarre problem: S10 doesn't receive texts from a specific sender, except after restarting, retroactively receives all texts sent by that sender. Supernatural powers might be involved, given the sender's phone is mine, and the fickle S10 is my wife's.
I'm including a lot of info below, b/c this seems to be a tough problem to diagnose, so I'm erring on the side of completeness.
Specs: My phone is an LG V35, rooted with Magisk, Android 9. Her S10 is not rooted, running Android 9. Her phone is logged in to the same Google account I use on the Play Store, so that she can use any of my paid apps without paying again. (This has never caused any SMS problems in the past, just annoyances like her getting my reminders, which I then turned off on her phone.)
The problem started on 10/26/22 (about three weeks ago). I know this b/c I sent her a long text that day, which her phone received immediately, followed by another text that same day, which she didn't receive until eight days later on 11/3/22. There were several other texts I sent btw 10/26 and 11/2 that she didn't receive until 11/3. However, we did not catch this problem until yesterday (11/17), when she discovered that I had not, in fact, been ghosting her, but that her phone was not getting my texts. We found this out b/c some other app on her phone wasn't behaving normally, so I restarted her phone -- and BAM, all my unreceived texts suddenly arrived on her phone. Since then, I've tried texting her phone, and it receives nothing from me until a restart, and then her phone receives all my texts retroactively.
As far as we can tell, neither of our phones has any problem with SMS communications with anyone else's phone (except some iPhones -- don't get me started). Other people receive my texts normally, and her phone receives other people's texts normally.
I tried texting her from two different Google Voice accounts I have (both different from the Google account our phones share), and her phone received both G-Voice texts immediately.
I tried changing my SMS app (from Pulse to Textra). No effect (her S10 didn't receive texts until restarting). I tried changing her SMS app. No effect. I did a Samsung software update (thru Settings) on her phone. No effect.
I have an old S10e, my last phone before I switched to the LG. As an experiment, I popped her phone's SIM card into my old S10e. I installed an SMS app neither of us has ever used before, Handcent Next, on the S10e. Without doing anything else (i.e. w/o transferring her S10 data or settings to the S10e), I texted her number from my LG. The text arrived immediately in Handcent. I thought, Eureka!
I promptly factory-reset my S10e, and used Samsung's Smart Switch to transfer "Everything" from her S10 to the S10e. After all her data, apps, & settings were transferred to the S10e, I texted her number, and… NOTHING. The S10e did not receive my text, until I restarted it.
So, my question to all Android sleuths out there is: What the hell?
Excellent detail and info.
My initial guess may be because you're sharing the Google account. Yes, I know you said this didn't cause problems before, but now with Google Messages (I know you're not using that, but still) doing lots of RCS and background stuff, I imagine there may be some behind-the-scenes interaction that is causing problems. I'm not saying this is a fault of RCS or anything like that, but I think the sharing may be the issue?
I would suggest trying to create a new Google account, and keeping the phones on separate accounts... it's a free and easy test, I figure... and you seem quite skilled in more difficult things, so this should be easy enough?
Also note, some apps support family sharing, so if you setup a "family" between the two accounts, you may get the purchased apps on both accounts without too much issue. My wife and I do this and it has worked pretty well for our apps. (FWIW, we both have S10+ and use GMessages on separate google accounts, family shared, and don't have any issues with texts, etc.)
schwinn8: I liked your idea & reasoning, and I implemented it -- new personal Gmail account for her, added to my G-family. Restarted her phone, and sent her a text which did not arrive. (I texted her from a Google Voice account, and that SMS arrived instantly.) I then restarted her phone again, and, for the first time, the initial text still did not arrive. That's new, at least.
What setting could possibly delay a text from coming in?
Well, that's not the direction I wanted things to go either!
Not sure what else could delay texts from coming in... not aware of any delay mechanisms in most cases.
Are both on Wifi during this process? Is the LG running a ROM with working VOWIFI? Yes, I am grasping at straws...
Well, recalling my old Windows 3.x experiences, I factory-reset the S10e (my old phone), and installed all of my wife's apps and recreated all her settings on it from scratch -- i.e. no transferring apps or settings from her phone. A labor-intensive solution, to be sure, but it is working so far. The S10e receives my texts normally.