Database Users

Interesting response to the whole "omg sms bugz"

http://code.google.com/p/android/issues/detail?id=9392#c1350
What proves that you lie? The next:
1) thread was created on June 28 and even was in search results 1 or 2 times for me or even on one tech website, but it is 6 MONTHS AGO, no EFFECT was then and during this period! FOLKS! 6MONTHS you keep your silence waiting? and now are yelling like sheeps?
2) all complaints appeared in OLD THREAD simultaneously on December 31, but you say that it was for a long time;
3) you name your devices every time without any detailes, the name of Device alone says nothing for bug fixing; this is ordered by your owner, TROLLS, to name all Android devices here to demonstrate the scale of your 'problem'; this addresses your claims to usual consumers, buyers, not to developers; you just need an attention of consumers, which buy devices, not developers who should find your INVENTED bug in REINVENTED thread;
4) you post here almost identical useless 3-4 words messages. DO YOU KNOW THAT THIS IS a developer's forum? detailes? logs? screens? descriptions? or you don't have a good another place from where you could scream?
5) you use the same words in all 3 places where ****storm should been created to make a feeling that these words are so obvious, but they are written down in your file on computer.
6) bugs are usually a result of updating or installing or some intrusions, you don't connect your complaints with any of your actions with Android OS or OS's changes on your devices.
7) nobody here don't try to really find a solution for 'his problem', because you just need a ****STORM, yelling, scandal; it says a lot about true your goals here;
8) those 2 resources from whose you came here are perfect for starting ****storms. theey are big and different to target different users- one is more glamorous and another one is more geeky;
9) you use term 'switch' and competitor's phones. Folks who experience a problem will not start their messages from the words 'I think about breaking my contract' or 'I'm switching'. You talk to customers/ buyers, saying this, NOT DEVELOPERS;
10) the idea for ****storm was found excellent, must agree: SMS is a basic feature as dropped calls during an important call, everyone sends millions of messages every day, half of them are so sexual and zesty that will cause firing and misunderstanding everywhere, even EMBARASSMENT!;
11) old retired idea about Google's privacy concerns is a very good sauce for such stories;
12) a slap into the face of openness- 'Look, Google, what we can do with your openness and your Open Handset Alliance!';
13) exactly before CES 2011;
14) tremendous growth of Android that needs ****storm to be able to compete better and to shine brighter;
15) just to create a proof for the words that you repeat on the internet as zombies about Android.
16) this thread was old,but once established and almost forgotten due to its uselessness, it just needed reinvention on December 31; this fact gave to this thread so bad-needed maturity to show that nothing is fixed from the 1st report; which also help push the theme 'Google doesn't care'.
17) if this bug was existing you wouldn't act as you act now
Click to expand...
Click to collapse
I don't agree with everything he says but the bolded are good points. [I don't think the guy speaks English]
Not saying that the issue shouldn't be resolved as fast as possible..
Just kinda funny that, as he points out, if it's such a "serious issue" why was it barely-if ever- talked about until RIGHT before CES?
Also kinda funny that every time this bug happens...the text is of a sensitive nature....
I call BS on that.
As I have said before, Engadget is a lot like "sexy action news" with their "the world is ending" article titles.
This issue, while it does need to be fixed, is not as serious nor is it as excessively occurring as claimed.
If so, then it would have been reported more often in the last six months than ONCE.

mattykinsx said:
http://code.google.com/p/android/issues/detail?id=9392#c1350
I don't agree with everything he says but the bolded are good points. [I don't think the guy speaks English]
Not saying that the issue shouldn't be resolved as fast as possible..
Just kinda funny that, as he points out, if it's such a "serious issue" why was it barely-if ever- talked about until RIGHT before CES?
Also kinda funny that every time this bug happens...the text is of a sensitive nature....
I call BS on that.
Click to expand...
Click to collapse
It's simple: A lot of people don't get to use the AOSP message app - how many stock Android phones are there? But if you go on AOSP ROM threads you'll get see SMS complaints pop up occasional. I guess it's a story because it still hasn't been fixed after all this time plus a HUGE stock phone just dropped - the Nexus S. Reviewers have taken notice.

Award Tour said:
It's simple: A lot of people don't get to use the AOSP message app - how many stock Android phones are there?
Click to expand...
Click to collapse
?
The "claim" by Engadget is that it is an issue in coding of Android and "will occur no matter what SMS program is used" [which is complete and utter bull****]
It DOES need to be fixed but the timing and "end all" nature of Engadget article screams attention whoring.

mattykinsx said:
?
The "claim" by Engadget is that it is an issue in coding of Android and "will occur no matter what SMS program is used" [which is complete and utter bull****]
Click to expand...
Click to collapse
Maybe I'm looking at the wrong article but where does it say that?
http://www.engadget.com/2010/12/31/android-still-has-horrible-text-messaging-bugs-thatll-get-you-f/

not sure if this is the same bug but me and my brother who both have had evo's since the launch had a problem with clicking on a conversation, starting to write a text and notice that we were actually sending it to a complete wrong person. It was few months ago, i actually sent few msgs to wrong people before i caught on.

Award Tour said:
Maybe I'm looking at the wrong article but where does it say that?
http://www.engadget.com/2010/12/31/android-still-has-horrible-text-messaging-bugs-thatll-get-you-f/
Click to expand...
Click to collapse
Sorry, it's actually not in that article, although it does kind of insinuate it.
It's been said on here and in other places though.
Android has been plagued with a couple extremely serious bugs in its text messaging subsystem
Click to expand...
Click to collapse
That seems to implicate that it is not SMS app specific.
But as I said, others have read this and made the claim.

This has happened to me numerous times on stock, custom sense, and MIUI ROMs. I'll send a text to someone, and both they and a random person that was already in my texting list (someone that I have texted before) will get the text. It has happened on all 3 of my EVOs. Also, sometimes when I click on a thread it takes me to a completely different thread. I have almost sent a text to the wrong person because of this many times.

I think I understand this. It has something to do with the way Android handles the "back" hard/softkey function. It's missremembering which tile is where in the stack. It seems to happen when the "stack" or remembered tiles is too large. Try spamming the back button sometime. Occasionally it will do some interesting things.
Fix may be as simple as a small routine that scrubs whatever cache is responsible for this behavior.
Sent from my PC36100 using XDA App

This happened to me, I thought it was me not paying attention, or that might have really been the case. I almost got caught up it something because if it Now I tend to delete all the other sms's in my inbox while having a sensitive conversation.

Guys, I don't question that this happens.
I know it does because it's happened to me.
Once or twice...
I DO question how it suddenly "happens all the time" and only when its a "sensitive message". I call complete BS on both issues.

phatmanxxl said:
This happened to me, I thought it was me not paying attention, or that might have really been the case. I almost got caught up it something because if it Now I tend to delete all the other sms's in my inbox while having a sensitive conversation.
Click to expand...
Click to collapse
Smart man. I do the same thing.
Sent from my PC36100 using XDA App

Happens to me maybe once a week, have never actually sent a text to the wrong person because of it.

The engadget article is the first I've heard of this. I've been with android since the launch of droid 1 and it never happened to me???

rican408 said:
The engadget article is the first I've heard of this. I've been with android since the launch of droid 1 and it never happened to me???
Click to expand...
Click to collapse
that you know of.....lol

So is the bug is that it merges your text with other threads and makes you send to wrong person right?
Sent from my PC36100 using XDA App

Success100 said:
that you know of.....lol
Click to expand...
Click to collapse
Maybe THIS is how I always get caught lol

Ep3n3wp said:
So is the bug is that it merges your text with other threads and makes you send to wrong person right?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No, say you open up your message app and click on the thread you have going with John, it will instead open the thread you have with Jane. So if youre not paying attention youll text the wrong person.

scooter185 said:
No, say you open up your message app and click on the thread you have going with John, it will instead open the thread you have with Jane. So if youre not paying attention youll text the wrong person.
Click to expand...
Click to collapse
Oh I sees..... I had a sms problem in my hero where i would click my wifes thread, then type, then realize it went to some one else and merged the whole thing together...
The reason it was doing it was... Sms email text alerts from my bank of america.. The @.... Email text
Only fix was factory reset...until the next message came in... I fixed it by turning the bank alerts off...
Sent from my PC36100 using XDA App

Not gonna lie, pretty hilarious things have happened to me because of this bug. I either send lots of awful text messages, or my phone is trying to mess with me.
One time I accidentally sent an old school friend a text meant for my girlfriend that was pretty mushy. Woke up to a text back going.. "..um wut".
The second time was more terrible; some less-than-politically correct stereotypes questions meant for a close friend that ended up sent to a (thankfully trustworthy but still awkward) co-worker. :B
I only noticed after sending the text (and sending it IN THE THREAD for the person it was meant for) and then being redirected back to my list of conversation threads only to find that the completely incorrect contact was now at the top of my list and was in fact the newly chosen recipient for my text message.

Alfred F. Jones said:
One time I accidentally sent an old school friend a text meant for my girlfriend that was pretty mushy. Woke up to a text back going.. "..um wut".
.
Click to expand...
Click to collapse
LOL @sexting.....
Is someone from Microsoft going to have to develop a SMS recall function? We all know how well it works in outlook.

Can someone make a video to demonstrate...

Can someone please make a video to demonstrate the random reboot and boot loop problem happening on a completely stock, factory resetted Transformer with no 3rd party apps?
Not saying you guys have to prove anything but if we have this kind of video and post it everywhere, it will garner much more attention and maybe Asus will do something quicker.

Just the fact that you are posting this tells me that NOBODY will be able to create a video that you would accept as "proof". Besides, how are we supposed to videotape a "random" reboot that may take up to 24 hours (or more) to show up (and again, at RANDOM). The video would have multiple cuts and would be impossible to authenticate.
I think we know what a reboot or a bootloop look like... And we've sent lots of logs to Asus as real "proof".
Trust me, Asus knows there is REALLY a problem. We don't need to spend countless hours trying to capture a random reboot on tape.
Give me a break.
And before anyone calls me an anti-asus troll, please don't get me wrong - I love their products and nobody else makes a comparable tablet/dock combo! They release very frequent firmware updates which I also love! However, their response to this particular issue has been less than stellar.

Sure, Ill record a ~78h long video (roughly the frequency of my random reboots so far).
Just buy me a bigass HDD and Ill email the recording to you. Then I want to you watch every second of it in one go, no fast-forwarding or skipping.
... seriously though, a clip of a random reboot doesnt help the developers ONE BIT.
"right, so the device restarted... lets fix it! *searches code for entry "random restart"* oh look at that, no hits..."
There is a reason software uses logfiles. If you'd ever looked at one you'd know they provide a million times more information than a video clip will ever do.
Theres a saying, "a picture says more than a thousand words". But in coding its the exact opposite, a picture is more or less useless.
ASUS knows about this issue. But fixing something thats completely RANDOM and doesnt even happen on ALL devices makes it a ***** to pin-point in the code.
If you want to help asus - send them your logcats. Not a 78h long, useless, video.

Actually, Asus has one (mine) at their repair facility. My Transformer died (endless reboot to the eeepad screen) which nothing would stop, not connecting to ac, not holding the power button, not holding power and volume down. It was rma'd and returned with a factory restored image of ics, nothing on it that didn't come from Asus. I turned it off, and it would not turn back on. This is a completely stock tablet, never rooted, no 3rd party apps, heck I never even entered my Goggle Account. And it was working fine before ICS. They've had it since March 11 and have asked me to describe what happened a couple of times. I told them to fix it, turn it off for an hour or 2, and try to restart it. So, a totally stock tablet, fresh ICS from Asus, no 3rd party apps, and it won't work. If I ever get it back I'll let you know what they claim they did.

jtrosky said:
Just the fact that you are posting this tells me that NOBODY will be able to create a video that you would accept as "proof". Besides, how are we supposed to videotape a "random" reboot that may take up to 24 hours (or more) to show up (and again, at RANDOM). The video would have multiple cuts and would be impossible to authenticate.
I think we know what a reboot or a bootloop look like... And we've sent lots of logs to Asus as real "proof".
Trust me, Asus knows there is REALLY a problem. We don't need to spend countless hours trying to capture a random reboot on tape.
Click to expand...
Click to collapse
Hm what makes you think you would have to record the entire duration.
It can be cut. You can start recording when it's boot looping. Just show your app drawer or list of apps in your settings afterwards.
Hah I can't believe some people in this thread thought you would have to show the whole duration. It can be cut. It can be fast forwarded.
Just needs to show the boot loop or random reboot happening AND show the list of apps afterwards, not before.
I remember seeing a similar video for Prime. Kinda surprises me that nobody posted a video yet and it's been over a month since we got ICS and all the issues.

horndroid said:
Hm what makes you think you would have to record the entire duration.
It can be cut. You can start recording when it's boot looping. Just show your app drawer or list of apps in your settings afterwards.
Hah I can't believe some people in this thread thought you would have to show the whole duration. It can be cut. It can be fast forwarded.
Just needs to show the boot loop or random reboot happening AND show the list of apps afterwards, not before.
Click to expand...
Click to collapse
Yeah, I'll get right on that for you! It serves NO purpose to do this! Go away....
Why do you think people need to (or would even want to) try and prove this to you????
I KNOW there is a problem, I don't need to prove it to you! You would never accept that as real "proof" anyway, and you know it!
Sent from my Transformer TF101 using Tapatalk

jtrosky said:
Yeah, I'll get right on that for you! It serves NO purpose to do this! Go away....
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
lol. why are you so defensive?
DON'T DO IT IF YOU DON'T WANT TO. I was just asking, and not even you specifically.

horndroid said:
lol. why are you so defensive?
DON'T DO IT IF YOU DON'T WANT TO. I was just asking, and not even you specifically.
Click to expand...
Click to collapse
Because it's a waste of EVERYONES time, just like this thread.
Enough said. See ya...
Sent from my Transformer TF101 using Tapatalk

jtrosky said:
Because it's a waste of EVERYONES time, just like this thread.
Enough said. See ya...
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Again, you are being overly defensive for no reason.
There were similar videos for Prime. I just wanted to see one for TF101.

horndroid said:
Again, you are being overly defensive for no reason.
There were similar videos for Prime. I just wanted to see one for TF101.
Click to expand...
Click to collapse
In case you haven't read your own thread, you are the only one who thinks this is a good idea.
Look, as I remember, you said that you reboot your device at least once a day, so how do you even know if you have the problem or not?
My problem is this - you come on here acting like everyone that has the problem, has the problem because they did something wrong. Since you don't believe you have the problem, you assume that everyone who does have the problem is doing something wrong and that full wipe will fix it when some of us have already done that many time to no avail.
Instead of leaving us be to resolve our issues, you ask folks to waste time making videos to prove it to you!
Why are YOU being so defensive? You are the one asking for proof - not me!!
I keep telling myself I'll ignore you, but your reasons are so lame, that I can't help myself!!!

jtrosky said:
In case you haven't read your own thread, you are the only one who thinks this is a good idea.
Look, as I remember, you said that you reboot your device at least once a day, so how do you even know if you have the problem or not?
Click to expand...
Click to collapse
lol I know I am not getting random reboots because I constantly monitor my tablet for random reboots. I run an app that displays uptime on my home screen and I never empty out my recent apps list.
jtrosky said:
My problem is this - you come on here acting like everyone that has the problem, has the problem because they did something wrong. Since you don't believe you have the problem, you assume that everyone who does have the problem is doing something wrong and that full wipe will fix it when some of us have already done that many time to no avail.
Click to expand...
Click to collapse
Nope. I've even said that factory reset doesn't work for everyone. I came to that conclusion long time ago. People are experiencing the problems in different ways. Factory reset is just one of the solutions that have been proven to work for some people. Wakelock is another solution but that also doesn't work for everyone. So what's wrong with suggesting what have been proven to work for the large majority of people who fixed their issues? Sounds like it's the logical step in troubleshooting. People can't know whether it will help them or not before actually trying it.
I suggest it depending on what the person has said in his post. If he said he had tons of apps and did OTA update without wiping, I suggest it because I genuinely believe it will at least alleviate the problems. Pretty sure any reasonable person would think the same.
I do have a hard time believing ridiculous claims though, such as the one by Knoxploration, who says both his and his wife's TFs have random reboots and boot loops even after factory reset, running on stock with no apps. What an amazing coincidence that they both have the most extreme version of the problem.

I think there is already enough attention on the issue from Asus.
There is even a thread created by Asus employee to sort this issue. Its sticky on this very forum.

linuques said:
I think there is already enough attention on the issue from Asus.
There is even a thread created by Asus employee to sort this issue. Its sticky on this very forum.
Click to expand...
Click to collapse
I am aware. But a lot of people have been complaining that Asus isn't giving enough feedback.

horndroid said:
I am aware. But a lot of people have been complaining that Asus isn't giving enough feedback.
Click to expand...
Click to collapse
Luckily I dont have the issue, so I haven't been following the thread.
You can try the new kernel for the tf101 3g (version 9.2.2.3), is said to adress the issue. You can flash guevor kernel test 7 on non-3g TFs.

Just accept the fact that we are quite many who has an RR/SoD'ing TF101 and then accept the fact that we are quite upset with Asus?
Oh crap... I just fed a troll...

Thiesen said:
accept the fact that we are quite upset with Asus?.
Click to expand...
Click to collapse
Im not
Compared to Ainol, Asus are gods
... But the RR/SOD is quite annoying nevertheless.

Video of reboot to freeze
Here is a video of a reboot to a freeze I cobbled together, on an B70 with ICS (4.0.3) :
http://www.youtube.com/watch?v=8LZ5Q-kUSq4&feature=youtu.be
[replaced original video(s) with a more stable video of reboot to freeze].

About the RR and SOD problems, a lot of people solved their issues using the lastest kernel from Asus (9.2.2.3). It was actually release for TF101G.
Its not official yet on TF101, but there is a build from guevor here (test8) http://forum.xda-developers.com/showthread.php?t=1565519
Reportedly is working very good.

They see me trollin'.

Better than a video, would be to show the logs. And there are logcats of the reboot event, there are a team of devs that had those logs.

Google taking a beating over Nexus 7 problems...

On Google groups people are upset, and rightfully so.
http://productforums.google.com/forum/#!category-topic/nexus/nexus-7/Tetp20r-REo
The Nexus 7 touchscreen problem has been ignored by google, Asus, the tech press......
Google has had a free pass long enough.
I'm glad I was able to return mine.
I hope you guys are paying attention to how they are handling this defect.....IGNORE IT.
I would advise to never buy from a company who ignores or runs from problems.

Mine works fine and most of the complaints are exaggerated as usual
Sent from my HTC One using Tapatalk

z0phi3l said:
Mine works fine and most of the complaints are exaggerated as usual
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sure they are......:good:

z0phi3l said:
Mine works fine and most of the complaints are exaggerated as usual
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Mine does have this annoying touch problems, and it's really annoying. Yours fine? Good, please don't disrespect others complaint if yours "fine".
This is the kind of thing I don't understand, someone does a thread of the issue/news on it and suddenly comes people with their "fine" product and post how "fine" theirs are or/and that they don't care.
If your Nexus is "fine", then no need to read about it, enjoy it, but there are a lot of us who got a bad unit, I can't return it because it started after the 15 days of return warranty, so I'm stuck with it.

z0phi3l said:
Mine works fine and most of the complaints are exaggerated as usual
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I don't have breast cancer so most of the complaints are exaggerated as usual.
See the flaw in your logic?

NekroWolfen said:
Mine does have this annoying touch problems, and it's really annoying. Yours fine? Good, please don't disrespect others complaint if yours "fine".
This is the kind of thing I don't understand, someone does a thread of the issue/news on it and suddenly comes people with their "fine" product and post how "fine" theirs are or/and that they don't care.
If your Nexus is "fine", then no need to read about it, enjoy it, but there are a lot of us who got a bad unit, I can't return it because it started after the 15 days of return warranty, so I'm stuck with it.
Click to expand...
Click to collapse
Yup, and the 15 day return period is a joke as well.
All defects should be covered by a free replacement warranty equal to the product warranty.....NOT REPAIR...and the customer should not pay a dime for shipping.
At least one year......after the way Google has handled this they should extend the free replacement warranty to 3 years. (Yeah right)

I'm not buying an Asus device again that's for sure, at least not until the product is well tested...

NekroWolfen said:
I'm not buying an Asus device again that's for sure, at least not until the product is well tested...
Click to expand...
Click to collapse
Same here.....Google could have kept me by taking care of the problem.
I'm done with them too. They gave me the run around so bad I'm still dizzy.....

NekroWolfen said:
Mine does have this annoying touch problems, and it's really annoying. Yours fine? Good, please don't disrespect others complaint if yours "fine".
This is the kind of thing I don't understand, someone does a thread of the issue/news on it and suddenly comes people with their "fine" product and post how "fine" theirs are or/and that they don't care.
If your Nexus is "fine", then no need to read about it, enjoy it, but there are a lot of us who got a bad unit, I can't return it because it started after the 15 days of return warranty, so I'm stuck with it.
Click to expand...
Click to collapse
Please don't disrespect us who have perfectly working products by only calling out those who have issues.
Mine works fine.

I'm not sure if 7 people in that thread is really Google taking a beating. Also, it really isn't Google's problem. It is Asus'. How many tablets were sold vs how many have the issue. I got mine on launch day and no issue. I've had to send a few different items back to Asus in the past and had to pay shipping every time, but then again, $7 for shipping vs having to buy a new item is ok in my eyes. What a gimme gimme gimme world we live in.

DaemonAshra said:
Please don't disrespect us who have perfectly working products by only calling out those who have issues.
Mine works fine.
Click to expand...
Click to collapse
Next time, read well before quoting something directed to another user. I was specifically quoting him for saying that most of the complaints were exagerated, were a touch problem on a touch screen device is definitely not exagerated, besides how could you know if your device is working "fine". My quote wasn't directed at you, not interested in continuing this.

johnomaz said:
I'm not sure if 7 people in that thread is really Google taking a beating. Also, it really isn't Google's problem. It is Asus'. How many tablets were sold vs how many have the issue. I got mine on launch day and no issue. I've had to send a few different items back to Asus in the past and had to pay shipping every time, but then again, $7 for shipping vs having to buy a new item is ok in my eyes. What a gimme gimme gimme world we live in.
Click to expand...
Click to collapse
ROFL!!
"A gimme gimme world!!" - You are a corporations dream come true!!!
I paid for a defective product and in my business, I take care of my customers who receive defects.
You are SO wrong.
Such a "gimme gimme world" that I just spent money on a new tablet that actually WORKS!!! Nobody gave it to me!! IMAGINE THAT. I spent my hard earned dollars and received a functioning product - WOW!! What a novel concept.
No need to be a prick.....and you were one.

I currently have a mild problem with the touch, it's not as bad as some but its still annoying. Has anyone who has rooted and installed a custom rom experience the touch problem go away?

JJbdoggg said:
I don't have breast cancer so most of the complaints are exaggerated as usual.
See the flaw in your logic?
Click to expand...
Click to collapse
You use the word "so" where he uses "and". Two very different words and uses. I'm sorry if someone close has developed some form of cancer but don't bring it to an Android forum...:good:
Edit: Google isn't taking near the beating as you nay sayers lol

Mine's been working fine with no issues *knocks on wood*. I got it at launch. I don't expect any device to launch without issues but maybe it's just me. I'm not seeing this as a common widespread issue.

Mandelbrot.Benoit said:
You use the word "so" where he uses "and". Two very different words and uses. I'm sorry if someone close has developed some form of cancer but don't bring it to an Android forum...:good:
Edit: Google isn't taking near the beating as you nay sayers lol
Click to expand...
Click to collapse
Okay replace and with so, my point still stands.
I also don't see how my analogy would be offensive to someone who knows someone with breast cancer so don't turn it into that, you also don't make the rules so I'll bring it up if I want to.

ilikeguitars said:
I currently have a mild problem with the touch, it's not as bad as some but its still annoying. Has anyone who has rooted and installed a custom rom experience the touch problem go away?
Click to expand...
Click to collapse
Yup.
My touchscreen was mildly effected also. Mostly the missing touch problem when not holding the device (ie: sitting on a table or such).
Rooted using the forum tutorials, installed sfhub's ts10 update and the touchscreen works fine now. No skips, no missing or ghost touches.
For the record, I've only been using android for about 2 weeks now so it's not that hard to learn how to apply the fix that worked on mine.
Now, should an end user have to do you this to their device? Nope, it should come this way. For mine it was such an easy fix, it would seem they have no excuse for not designing the software properly in the first place.
I quite like the rest of the devices features (ie: nice screen, battery life, speed, just right size for book reading and fitting in my coat pocket, etc) and it's quickly becoming a favorite device of mine.
As to those saying thiers works fine, I think they are valid comments. Not all the devices are effected and as is normal with human behavior, those that feel "screwed" are often the ones who are the loudest. Not that they're not justified in being upset with getting a "broken" product, they are.
But it is equally valuable to hear from those that get products that work.
How else are we going to know if there are more bad than good if we don't also hear from "the good"?

JJbdoggg said:
Okay replace and with so, my point still stands.
I also don't see how my analogy would be offensive to someone who knows someone with breast cancer so don't turn it into that, you also don't make the rules so I'll bring it up if I want to.
Click to expand...
Click to collapse
You're absolutely right: I don't make the rules and you can bring it up if you want to. I was simply suggesting that life and death disease analogies can always offend Someone and might be a little overboard on an Android forum.
You would need to replace so with and. He was making two separate points and connecting with the word and, while you are expressing cause-effect with so (should be used in conclusion). Though due to ambiguity I could be completely wrong. You brought up logic. I just thought it would be easier for two rational human beings to get to the same spot.
And my G2 screen is wonkier than my Nexus 7. Turning it off and back on seems to solve it though.

Guys, let's not argue about whether what's important to one is also important to you. Everyone has their own opinion. It looks like enough people are upset about the issues, and that is a fact.
I am one of those people. After devs here on XDA put together near perfect AOSP roms for my ThunderBolt, I expected stuff coming out of Google directly to be rock solid. N7 is my first Nexus device, and I am quite disappointed with regular random reboots that I still have, as well as intermittent touch screen issues. For example, I can't play Subway Surfers since N7 keeps ignoring some portion of screen touches (leading me to crash lol).
My HTC DNA, however, is rock solid on the stock rom. Why can't a Nexus device be the same? People typically complain of manufacturers adding stuff to android that makes it worse. Well, I am not so ready to say that now. As far as I am concerned, HTC is doing a better job with their devices than Google.
PS, TB was buggy when it came out, but all the bugs were subsequently fixed, even on Verizon!
Sent from my HTC6435LVW using Tapatalk

cowisland said:
Guys, let's not argue about whether what's important to one is also important to you. Everyone has their own opinion. It looks like enough people are upset about the issues, and that is a fact.
I am one of those people. After devs here on XDA put together near perfect AOSP roms for my ThunderBolt, I expected stuff coming out of Google directly to be rock solid. N7 is my first Nexus device, and I am quite disappointed with regular random reboots that I still have, as well as intermittent touch screen issues. For example, I can't play Subway Surfers since N7 keeps ignoring some portion of screen touches (leading me to crash lol).
My HTC DNA, however, is rock solid on the stock rom. Why can't a Nexus device be the same? People typically complain of manufacturers adding stuff to android that makes it worse. Well, I am not so ready to say that now. As far as I am concerned, HTC is doing a better job with their devices than Google.
PS, TB was buggy when it came out, but all the bugs were subsequently fixed, even on Verizon!
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Couldn't say it better, let's keep it a happy forum, and just to reflect what you just said, the same thing goes for me with Dead Trigger 2, I can't play it because of this, it's simply NOT fair, after I paid for this device.

Touch screen issue gone after recent update?

Anybody that had it now notice its gone after the recent otas that were released?

Could you explain a bit what touch screen issue did you mean, as I didn't notice any issue with the touchscreen even before the update?
20degrees said:
Anybody that had it now notice its gone after the recent otas that were released?
Click to expand...
Click to collapse

My touchscreen works absolutely perfect, don't know what you're talking about.

theres threads on the issue. those that had it will know what I mean.

20degrees said:
theres threads on the issue. those that had it will know what I mean.
Click to expand...
Click to collapse
Probably best to track this issue, and provide your feedback over on this thread:
http://forum.xda-developers.com/showthread.php?t=2521663

billykxda said:
Probably best to track this issue, and provide your feedback over on this thread:
http://forum.xda-developers.com/showthread.php?t=2521663
Click to expand...
Click to collapse
seems theres no updates from others there. I just want to know if its fixed cause I want to get this phone again.

20degrees said:
seems theres no updates from others there. I just want to know if its fixed cause I want to get this phone again.
Click to expand...
Click to collapse
Yeah - looks like I am the only one that has weighed-in so far.
Check over at AC
http://forums.androidcentral.com/lg-g2/
I believe other's have responded either at the main forum or within the VZW forum.
There's certainly no way of having any conclusive answer just yet, as it can take hours, days, weeks for this issue to surface. I am hopeful though.

billykxda said:
Yeah - looks like I am the only one that has weighed-in so far.
Check over at AC
http://forums.androidcentral.com/lg-g2/
I believe other's have responded either at the main forum or within the VZW forum.
There's certainly no way of having any conclusive answer just yet, as it can take hours, days, weeks for this issue to surface. I am hopeful though.
Click to expand...
Click to collapse
I had some freezing and unresponsive display, but it occured after i installed a game. After i removed it everything gone back to awsome:laugh:

Open letter to Nexus about defective screens

I have owned an original Nexus 7 since its inception. I have recommended it to everyone and I am responsible for several people purchasing them. However, when it comes to the 2013 model I have recommended to everyone NOT to purchase one for the obvious reasons.
It is difficult to understand why a company like Nexus is so reluctant to correct a known
problem with an otherwise fantastic product. A few people here have done all the work for Nexus and gone to the trouble of diagnosing the problem (grounding) and even correcting it on there devices, yet Nexus won't even admit there is a problem. I'm sure someone from Nexus monitors this site (or anywhere on the Internet for that matter) and they are completely aware of the problem. Why does a company go out of there way to create a device that appeals to people who love to work on them but when they receive valid feedback they ignore it.
For the individuals who believe there is nothing wrong you should be aware your screen should perform flawlessly (at least as well as the original 7) whether it is plugged in or not. You are doing a real dis-service when you say "sure it misses a few touches or has a few phantom touches its still better then most other devices". This might be true. But, would you accept a great car that occasionally when you turn the steering wheel it didn't respond or it randomly turned on its own.
The bottom line is the screen interface is DEFECTIVE. I wanted so badly to purchase a new one but, after 3 units all with the defect I'm not willing to void the warranty and fix it myself especially on a device that that the manufacturer won't even admit when there is a defect.
Sent from my Original Nexus 7 (because the 3 2013 models i tried were all defective)
using xda app-developers app

Nexus does not exist as a company.. They are licensed by Google and built by Asus.
Sent from my Nexus 7 using Tapatalk

That is exactly how I feel. I have told people on here, Google, Youtube, and other sites who asked about the issues to get there money back. I personally had 2 that had each major issues. I loved it but it's issues made me very disappointed. I showed the associates each time I returned them what was wrong and they had no idea they had problems. You could tell by them trying it themselves they truly had no idea. How many owners except it, don't realize there is issues like children using them. It is such a shame that a company can make a product that honestly needs to be recalled but it just gets swept under a rug. I will not buy another one and I will never buy an ASUS product again. I am getting the hp slate 7 extreme and will be happy with the slightly lower resolution screen but the screen actually working as it should automatically makes it superior to the N713.

I would have no issue recommending the current model to people, just because a vocal minority ate having issues does not mean the device is flawed, mine is perfect, bought the first weekend of availability, and used daily, so hard in that it's a perfect device, bit I would not actually day that
Sent from my One using Tapatalk

z0phi3l said:
I would have no issue recommending the current model to people, just because a vocal minority ate having issues does not mean the device is flawed, mine is perfect, bought the first weekend of availability, and used daily, so hard in that it's a perfect device, bit I would not actually day that
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Perfect...except for that keyboard.

It's what I get for trying to post between calls at work, sue me
Sent from my One using Tapatalk

z0phi3l said:
I would have no issue recommending the current model to people, just because a vocal minority ate having issues does not mean the device is flawed, mine is perfect, bought the first weekend of availability, and used daily, so hard in that it's a perfect device, bit I would not actually day that
Sent from my One using Tapatalk
Click to expand...
Click to collapse
You say vocal minority. When in fact if you google it there are over 28 million results of screen touch issues. That is no minority. You say yours is perfect then download the screen test apps an run the tests and post videos of the results both in your hands and propped up in a case or laying flat on a couch cushion. If you get phantom touches or missed touches anywhere at anytime it is a defect. It would be exactly the same as going to buy a new car that wont go into drive once in a while. If yours has no issues then consider yourself a lottery winner!

z0phi3l said:
It's what I get for trying to post between calls at work, sue me
Sent from my One using Tapatalk
Click to expand...
Click to collapse
:laugh:

Shrek77 said:
You say vocal minority. When in fact if you google it there are over 28 million results of screen touch issues. That is no minority. You say yours is perfect then download the screen test apps an run the tests and post videos of the results both in your hands and propped up in a case or laying flat on a couch cushion. If you get phantom touches or missed touches anywhere at anytime it is a defect. It would be exactly the same as going to buy a new car that wont go into drive once in a while. If yours has no issues then consider yourself a lottery winner!
Click to expand...
Click to collapse
Do you understand how search engines work? You simply cannot infer anything from such a search, which can bring up the same individual's multiple complaints across multiple forums, forum posts with "blank" instead of "problem" (because Google thinks it's a similar enough word), the same forum thread in regular as well as printer-friendly versions, and people saying, "no problem with this device."
A Google search for "Nexus 7 2013 screen problems" yields "About 96,100,000 results" for me. So what is that, 961,000 people complaining 100 times each? It surely isn't 9.61 million complaining 10 times each. This isn't to say there aren't units with problems, but do a Google search for your least-favorite politician's name along with "pedophile" and see what happens. Again, you simply cannot infer anything from such a search.
I've run test apps on mine, before and after. Initially my unit had poor sensitivity, alleviated by the ts10 file from this popular fix. Yes, I had to take a few minutes to do things that Google should have done, but in the end it can take less effort to make a quick fix yourself instead of waiting for someone else.

Pandae said:
Do you understand how search engines work? You simply cannot infer anything from such a search, which can bring up the same individual's multiple complaints across multiple forums, forum posts with "blank" instead of "problem" (because Google thinks it's a similar enough word), the same forum thread in regular as well as printer-friendly versions, and people saying, "no problem with this device."
A Google search for "Nexus 7 2013 screen problems" yields "About 96,100,000 results" for me. So what is that, 961,000 people complaining 100 times each? It surely isn't 9.61 million complaining 10 times each. This isn't to say there aren't units with problems, but do a Google search for your least-favorite politician's name along with "pedophile" and see what happens. Again, you simply cannot infer anything from such a search.
I've run test apps on mine, before and after. Initially my unit had poor sensitivity, alleviated by the ts10 file from this popular fix. Yes, I had to take a few minutes to do things that Google should have done, but in the end it can take less effort to make a quick fix yourself instead of waiting for someone else.
Click to expand...
Click to collapse
I do not have problem with normal use but when I display the test pattern I can see ghost touches or erratic touches.
I fact I think that is hardware problem, it look's like the digitiser A/D converter DC supply noisy (to low decoupling capacitors) or shielding/grounding issue.
The problem is that I was not abble to find any schematics to investigate more.
To be continued...

The touch test in the play store is bogus. I bought my device the day it came out and have never had any touch problems. Only with the app, it starts jumping, and that app is the only time its showed something. Take a screenshot of any pattern, try it with the screenshot. Nothing happens.
I'm not saying that some devices don't have issues, but the numbers not as much as some claim. If you have problems, use the ts10 fix.
Sent from my Nexus 7 using xda app-developers app

Try going to the Developer Options, and enable "Show Touches." That would show you if there are phantom touches or not.

aarsyl said:
Try going to the Developer Options, and enable "Show Touches." That would show you if there are phantom touches or not.
Click to expand...
Click to collapse
I do have it enabled. The apps the only thing that produces phantom touches.
Sent from my Nexus 7 using xda app-developers app

datallboy said:
I do have it enabled. The apps the only thing that produces phantom touches.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Have you tried this one? This is the one that I use, and I know that it isn't bogus.
https://play.google.com/store/apps/details?id=drvgames.multitouchtest
The touches that are registered reflect the behavior of the tablet.

Posting here does nothing for you. XDA isnt google. XDA isn't Asus. if you have a problem contact Asus and or google.. All this /waaa in a thread on a dev site is nothing but wasted kb.

aarsyl said:
Have you tried this one? This is the one that I use, and I know that it isn't bogus.
https://play.google.com/store/apps/details?id=drvgames.multitouchtest
The touches that are registered reflect the behavior of the tablet.
Click to expand...
Click to collapse
Nice app, no phantom touches.
People are being fooled with the Nexus 7 II Tester app in the play store. It has patterns which generate fake touches.
Sent from my Nexus 7 using xda app-developers app

tweaked said:
Posting here does nothing for you. XDA isnt google. XDA isn't Asus. if you have a problem contact Asus and or google.. All this /waaa in a thread on a dev site is nothing but wasted kb.
Click to expand...
Click to collapse
I agree. Also OP, if you really want a manufacturer to take you seriously you should probably do a bit more research before sending them a letter, you didn't even come close to getting the company's name correct as has already been said. Either google or asus, or both, but not 'nexus'.

lionelia said:
I do not have problem with normal use but when I display the test pattern I can see ghost touches or erratic touches.
I fact I think that is hardware problem, it look's like the digitiser A/D converter DC supply noisy (to low decoupling capacitors) or shielding/grounding issue.
The problem is that I was not abble to find any schematics to investigate more.
To be continued...
Click to expand...
Click to collapse
Asus or Google wouldn't release any kind of schematics for their proprietary electronics. Try the fix in the thread I linked to. It seems there are hardware variances among new N7s, for which the right software patch can compensate.

kingston73 said:
I agree. Also OP, if you really want a manufacturer to take you seriously you should probably do a bit more research before sending them a letter, you didn't even come close to getting the company's name correct as has already been said. Either google or asus, or both, but not 'nexus'.
Click to expand...
Click to collapse
so true, this thread is a good laugh
I do hope OP posts his reply from the "Nexus" corporation when/if it ever happens lololol Posting with abysmal ignorance yet expecting to be taken seriously? Priceless. Or a troll. Hard to figure out which.
Posted from my flawless N7 FHD.

mdamaged said:
Perfect...except for that keyboard.
Click to expand...
Click to collapse
Touché.