Related
Hello to every xda members...
I'm a newbie to android world.. was planning to buy nexus one so I just wondered if I could ask you guys about any hardware issues with this phone...
I was going through the forum and some of the things that worried me a little was the "bleeding" problem and the 3g issue... couldn't understand what the poster meant by the "bleeding" ... I'm just worried about hardware issues coz firmware are constantly updated to fix common problem... and I have a lot of faith in cyanogen and other devs....
Had no problems at all with mine, you've got to remember this is where people come when they have problems so youre bound to see a lot of posts like that here, but of the several hundred thousand Nexus's out there right now I think youll find that these events are fairly isolated. This is just a place a lot if people come to share them.
The only problem that i have noticed is the reception issue when you hold the phone, it has been discussed alot on these forums. Hope its just a software issue but who knows
JoshHart said:
Had no problems at all with mine, you've got to remember this is where people come when they have problems so youre bound to see a lot of posts like that here, but of the several hundred thousand Nexus's out there right now I think youll find that these events are fairly isolated. This is just a place a lot if people come to share them.
Click to expand...
Click to collapse
Thats true...
but still waiting for more replies
Hi,
Mine works OK, after flash radio from ERE36B the UMTS/GSM stability is slightly improved. In fact, on old ERE27 was also not bad - in my place the signal is really weak (-103dB)
Besides, battery lasts for ~10 hours (yes, massive playing with the phone .
Today spotted, that the icon descriptions were moved from center to the right of the icon, what caused lost of readability. After reboot problem was gone.
I also considered if to choose HTC desire, but finally decided to buy N1 - first of all because it was already available
greetz
mati.
So i guess it wud be a gr8 phone... coz i don't care about the video call that is the only drawback.... thanks...
Orangeandblue302 said:
The only problem that i have noticed is the reception issue when you hold the phone, it has been discussed alot on these forums. Hope its just a software issue but who knows
Click to expand...
Click to collapse
this is a non-issue with a bluetooth headset like my jawbone earcandy.
Orangeandblue302 said:
The only problem that i have noticed is the reception issue when you hold the phone, it has been discussed alot on these forums. Hope its just a software issue but who knows
Click to expand...
Click to collapse
may have something to do with the antennae being at the bottom of the phone...
bluetooth headsets remedy that, same with the stock headset that came with the phone.
about the bluetooth headset,
this may be true but I am not a fan of handfree stuff unless i am in my car, but I dont need to talk on my phone while driving. Id rather it just work when I use it like a normal phone..
Fine people of xda. today, my screen showed obvious separation from my beloved HTC. how many of you are seeing similar issues?
SilverStone641 said:
Fine people of xda. today, my screen showed obvious separation from my beloved HTC. how many of you are seeing similar issues?
Click to expand...
Click to collapse
exchange it. its why we have a warranty
oh yeah, no doubt. i was just wondering how many people were seeing the same problem
A few other threads here about this issue. But be careful because we do have a lot of folks here who get hot and bothered over posts like yours. If you go by the guess, some of those same folks made; it would appear that 1 to 5 percent of us are having the issue. I believe the number is higher and will become even higher after enough use, but I do hope I'm wrong.
Well being a noob in rom cooking, i have hard bricked my tab. It doesnt even turn on.
Im new to sammy stuff, so would appreciate some pointers, is this: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-7-7-jtag-brick-repair/ the only way?
me and others flash the room from the stupied idiot guy in this post and got brick our devices, BTW i think he is working with the company you mintioned in web site, if like that he and the company are dirty.
any way, you are developer so try to recognize how flashing rom could make such problem. please.
the device have little hot in left side so maybe some hardware working ??thinking
jamaljmys said:
me and others flash the room from the stupied idiot guy in this post and got brick our devices, BTW i think he is working with the company you mintioned in web site, if like that he and the company are dirty.
any way, you are developer so try to recognize how flashing rom could make such problem. please.
the device have little hot in left side so maybe some hardware working ??thinking
Click to expand...
Click to collapse
I did not flash anyones rom. I was trying to build my own. Which thread are you referring to?
This One!!!
http://forum.xda-developers.com/showthread.php?t=1497916
jamaljmys said:
me and others flash the room from the stupied idiot guy in this post and got brick our devices, BTW i think he is working with the company you mintioned in web site, if like that he and the company are dirty.
any way, you are developer so try to recognize how flashing rom could make such problem. please.
the device have little hot in left side so maybe some hardware working ??thinking
Click to expand...
Click to collapse
Definitely not working for any company, and I have developed many Android ROMs and never had this problem. I've been here since 2005, for crying out loud. This is my first Samsung ROM, so I admit to being new there. I will even accept your "stupid idiot" comment, as I guess I deserve it. Although, I wonder why 150 people have downloaded it and only two or three people that I can see have been bricked. Something must connect those with issues. We need to find what it is.
Also, I am happy to pay for the de-bricking of those who are legitimately bricked i.e., followed instructions, have a receipt from JTAG, or whatever it is). Just PM me.
Steve
For reference, I am the only one who does anything for/with MobileTechVideos from a business stand point and two, I have successfully reverse engineered the world's (currently) only hard brick solution for this model as you will see above...
connexion2005 said:
For reference, I am the only one who does anything for/with MobileTechVideos from a business stand point and two, I have successfully reverse engineered the world's (currently) only hard brick solution for this model as you will see above...
Click to expand...
Click to collapse
Thanks for the info. I am dying to find out what caused these users to have this problem, and no one else seems to have.
Steve
Moved To General
I have to apply the same rules for all. As the first post contains no development, it does not belong in said section
sk806 said:
Definitely not working for any company, and I have developed many Android ROMs and never had this problem. I've been here since 2005, for crying out loud. This is my first Samsung ROM, so I admit to being new there. I will even accept your "stupid idiot" comment, as I guess I deserve it. Although, I wonder why 150 people have downloaded it and only two or three people that I can see have been bricked. Something must connect those with issues. We need to find what it is.
Also, I am happy to pay for the de-bricking of those who are legitimately bricked i.e., followed instructions, have a receipt from JTAG, or whatever it is). Just PM me.
Steve
Click to expand...
Click to collapse
let us dry the tears and look forward to solve the problem.
steve, please pass the words came from reaction, it was chock as you seen. sorry for harming.
iam in middle east and not confidant to ship my device to unknown address because he mentioned in web page that he has solution, i mean JTAG and its not subject of who to pay steve.
supposedly that web site is true, and they didn't mention that they will change any part of device, what they will do to fix? the problem happened because we flashed non compatible files i think.
let us figure out the problem and try to find solution. right?
jamaljmys said:
let us dry the tears and look forward to solve the problem.
steve, please pass the words came from reaction, it was chock as you seen. sorry for harming.
iam in middle east and not confidant to ship my device to unknown address because he mentioned in web page that he has solution, i mean JTAG and its not subject of who to pay steve.
supposedly that web site is true, and they didn't mention that they will change any part of device, what they will do to fix? the problem happened because we flashed non compatible files i think.
let us figure out the problem and try to find solution. right?
Click to expand...
Click to collapse
Absolutely. I understand. I have gotten into many messes since i started developing, and know that panic. I just need to know everything you.and the other user who had this problem can tell e about your device so i can find out what the common denominator is. So, confirm it is the wifi and 3g version you are using, and what build you are coming from, if you would. Are you using a sim card? Have you tried pressing power and volume up for a while? Thanks. Also, does your tablet feel hot at all?
Steve
sk806 said:
Absolutely. I understand. I have gotten into many messes since i started developing, and know that panic. I just need to know everything you.and the other user who had this problem can tell e about your device so i can find out what the common denominator is. So, confirm it is the wifi and 3g version you are using, and what build you are coming from, if you would. Are you using a sim card? Have you tried pressing power and volume up for a while? Thanks. Also, does your tablet feel hot at all?
Steve
Click to expand...
Click to collapse
thank you steve
in your original topic i gave all info
sk806 said:
Absolutely. I understand. I have gotten into many messes since i started developing, and know that panic. I just need to know everything you.and the other user who had this problem can tell e about your device so i can find out what the common denominator is. So, confirm it is the wifi and 3g version you are using, and what build you are coming from, if you would. Are you using a sim card? Have you tried pressing power and volume up for a while? Thanks. Also, does your tablet feel hot at all?
Steve
Click to expand...
Click to collapse
Well I used yours as a base, just chopped the usual crap out, resigned, flashed, everything seemed OK. Initiated reboot, bam, doesn't turn on.
Charged all night, tab is hot along left edge, so I'm guessing still charging. 8600.
ftgg99 said:
Well I used yours as a base, just chopped the usual crap out, resigned, flashed, everything seemed OK. Initiated reboot, bam, doesn't turn on.
Charged all night, tab is hot along left edge, so I'm guessing still charging. 8600.
Click to expand...
Click to collapse
let us exchange the ideas
first we need to get the device powered so maybe remove and return battery could do something?? but how?
any external way to use it throw usb slot while charging ?
I would try pulling the battery but have no idea how to get the case off.
Steve, just wondering out loud whether those who have the hard-brick issue be because there are on pre-production hardware, so they have a slightly different hardware SKU. Hence your ROM does not work for them.
pinkowl said:
Steve, just wondering out loud whether those who have the hard-brick issue be because there are on pre-production hardware, so they have a slightly different hardware SKU. Hence your ROM does not work for them.
Click to expand...
Click to collapse
That seems to be the case for one of them. I am not positive about the others. I am having a hard time getting people to just tell me what build they were using prior to the flash...There seem to be 3 people who have had this porblem, and there must be something linking them, although it may be something random. Need to figure it out.
Steve
sk806 said:
That seems to be the case for one of them. I am not positive about the others. I am having a hard time getting people to just tell me what build they were using prior to the flash...There seem to be 3 people who have had this porblem, and there must be something linking them, although it may be something random. Need to figure it out.
Steve
Click to expand...
Click to collapse
I came from P6800ZSKL2. Dont know if it was from the very first production line, but judging by the quality (i bought three, all with crap displays) they probably were.
Also, i believe the device is on and trying to unpack something because it is indeed warm.
This of course means that there may be hope of getting into download or recovery yet... i will drain it for 34 hours and then attempt to turn it back on.
ftgg99 said:
I came from P6800ZSKL2. Dont know if it was from the very first production line, but judging by the quality (i bought three, all with crap displays) they probably were.
Also, i believe the device is on and trying to unpack something because it is indeed warm.
This of course means that there may be hope of getting into download or recovery yet... i will drain it for 34 hours and then attempt to turn it back on.
Click to expand...
Click to collapse
Please see sk806 original thread- we have been "discussing" why you might be having "problems".
ezynow said:
Please see sk806 original thread- we have been "discussing" why you might be having "problems".
Click to expand...
Click to collapse
Uh, not sure about the quotes, but yes, I am about to try something that might answer the question of why some bricked. If the answer is affirmative, however, the only solution likely is JTAG...
---------- Post added at 09:33 AM ---------- Previous post was at 09:10 AM ----------
ezynow said:
Please see sk806 original thread- we have been "discussing" why you might be having "problems".
Click to expand...
Click to collapse
BTW, his "suggestion" was "incorrect." Still not sure what's up. Will keep posted, and like I said, I'll work something out with JTAG for those who got bricked yesterday and posted about in in the original thread before I responded.
Steve
For the record hard bricks on the Exynos 4210 will occur generally in one of 3 ways:
1) Mis-matched boot.bin and sbl.bin
2) Incompatible boot.bin and sbl.bin combo
3) Invalid PIT file flash from an earlier generation TAB or Galaxy S device
Anything else causing a black screen is simply hardware failure.
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.
So I was having the multitouch issues.. putting two or more fingers closely together caused major freakouts, and some swipes would just count as taps, as well as phantom taps happening. I RMA'd. got it back, only to find out all they did was a factory reset, which I had already done. Obviously this did nothing to fix the problem. I was very angry. I went to Asus support and did a chat with a support guy ( trying to remember this is not his fault ) and politely stated that the RMA had done nothing. I set up a new one, explaining that it is a hardware issue and that I wanted the screen/digitizer to be replaced. I'm sending it tomorrow, so I'll let you guys know how that goes. Has anyone else RMA'd for this and gotten it back in perfect working condition?
WackyClash said:
So I was having the multitouch issues.. putting two or more fingers closely together caused major freakouts, and some swipes would just count as taps, as well as phantom taps happening. I RMA'd. got it back, only to find out all they did was a factory reset, which I had already done. Obviously this did nothing to fix the problem. I was very angry. I went to Asus support and did a chat with a support guy ( trying to remember this is not his fault ) and politely stated that the RMA had done nothing. I set up a new one, explaining that it is a hardware issue and that I wanted the screen/digitizer to be replaced. I'm sending it tomorrow, so I'll let you guys know how that goes. Has anyone else RMA'd for this and gotten it back in perfect working condition?
Click to expand...
Click to collapse
Yes, me too, my N7 was returned to Amazon yesterday :crying:
unfortunately, I couldn't find any tablet like N7 spec and price.
sauofee said:
Yes, me too, my N7 was returned to Amazon yesterday :crying:
unfortunately, I couldn't find any tablet like N7 spec and price.
Click to expand...
Click to collapse
My device only exhibits some multitouch jumpiness when not grounded. I decided to wait for Asus and Google to sort it out internally and then I will send it for repair. Now from what I heard they only replace one faulty units with another. Mine seems to be one of those better ones even though it has serious problems with basic pinch to zoom gestures when ungrounded. I keep it for now because I do not want to risk replacement with a worse one.
One question to the those of you who got a replacement. When you got your replacement devices what was the manufacturing date? Did anyone get a device from September production batch? Was it any better?
I just mailed mine in for repair yesterday. I was hoping this would resolve my screen issues but I'm getting the impression that I will be very lucky if it does.
Plan B will be to buy another one and return the first one with that receipt. Rinse repeat until I get one that works.
Sent from my Nexus 7 using Tapatalk 4
gadzooks64 said:
I just mailed mine in for repair yesterday. I was hoping this would resolve my screen issues but I'm getting the impression that I will be very lucky if it does.
Plan B will be to buy another one and return the first one with that receipt. Rinse repeat until I get one that works.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
So annoying that's what you have to do just to get one that works. Asus..... I don't know why they didn't just go samsung or htc, as badly as asus fudged up QC on the 2012 N7
I just mailed mine in for repair today, I don't know if I did right. Mine is also from the best ones between the bad ones and I don´t want to get one in worst conditions. I know a guy who send it to asus and got it back with the screen, front and gps changed, they did not even talk about the gps or gps problems at all, so we thought it was solved because they knew what to change. When he got it back at first it was perfect, he use to had a realy faulty unit, but the next day he came saying that it was failing again, much less than before but not perfect at all. He keeps talking with the people on asus and they told him to send it back, that may be an app... ???? I guess they don't have any idea on what the problem is.
bokoy said:
He keeps talking with the people on asus and they told him to send it back, that may be an app... ???? I guess they don't have any idea on what the problem is.
Click to expand...
Click to collapse
Yeah, the app is called JSS15* OTA update.
sfhub said:
Yeah, the app is called JSS15* OTA update.
Click to expand...
Click to collapse
There is a problem with that solution, I have the grounding issue, how could just a software problem do that? Mine works nearly perfect in my hands but if you put it over a sofa... Could be a software problem with some apps but not all.
The 15x updates contained firmware (which effects the hardware) as well as software.
Sfhub's firmware patches have been 80-90% successful in minimizing or eliminating the touch problems for those who've tried them.
He knows what he's talking about.... :thumbup:
gadzooks64 said:
Plan B will be to buy another one and return the first one with that receipt. Rinse repeat until I get one that works.
Click to expand...
Click to collapse
So in essence, commit fraud?
Apparently.
Sad that the sellers have to take it in the shorts because Google/ASUS are so clueless and unable to provide anything remotely resembling customer service.
They'll end up with a bunch of money tied up in defective stock that they'll have to sit on until they get credit.
Next time, how many Google/ASUS tablets do you think they'll be ordering?
goofball2k said:
So in essence, commit fraud?
Click to expand...
Click to collapse
Are you from the police? Is that fraud? So how would you call what asus/google are doing...
I think people that buy a device and return defective units to the place of purchase are heroes. Especially if they return 3-5 or more. They beta test the devices, and take out the bad ones for the rest of us.
Is it fraud to buy model ABC and return model ABC to the same store? The stores have a ASUS wonderful warranty program where they can return the devices for a full year for repair and resell them to unsuspecting customers. For example, I noticed Best Buy selling a Google device recently at full price that had an extra small sticker - Bug Fix A. Isn't that fraud? LOL
Seriously, it should be fraud to sell a consumer faulty devices and expect thousands of customers to deal individually with the known problems.
Even if you buy one in one shop, then buy another in another, or the same shop, and return the first one as the second, that is what the user said. If that's the way to get a good one working... but be careful with bar codes, they will know you are not returning the same item.
There's no damage for any shop as Bob said, they just return the unit and gets new one. The biggest problem is for the user, Google is just lucky for not having more returns.
They are are all screwed up I think. Some more then others. It can be fixed with Sfhub's patches for the most part. Mine still gets strange when I play extended periods of Terraria but it is only for a second or two. I don't even think it is the device at this point but rather the game itself.
Best thing to do is go into Dev options and turn on show touchscreen inputs. Before it would skitz out and I could see like 5 touch inputs randomly on the screen. Now after Sfhubs fix, I don't see any, even when the game gets wonky.
This is why everyone knows it can be corrected via a proper patch from Google. Whether they adjust the sensitivity to touch or grounding or whatever. If Sfhub can do it, Google can. Plus it is a tiny download, his directions are precise, you don't have to be unlocked or rooted to do. There is absolutely no harm to just patch it yourself until Google makes with a fix.
Touchscreen Patch Fix:
http://forum.xda-developers.com/showthread.php?t=2428133
player911 said:
They are are all screwed up I think. Some more then others. It can be fixed with Sfhub's patches for the most part. Mine still gets strange when I play extended periods of Terraria but it is only for a second or two. I don't even think it is the device at this point but rather the game itself.
Best thing to do is go into Dev options and turn on show touchscreen inputs. Before it would skitz out and I could see like 5 touch inputs randomly on the screen. Now after Sfhubs fix, I don't see any, even when the game gets wonky.
This is why everyone knows it can be corrected via a proper patch from Google. Whether they adjust the sensitivity to touch or grounding or whatever. If Sfhub can do it, Google can. Plus it is a tiny download, his directions are precise, you don't have to be unlocked or rooted to do. There is absolutely no harm to just patch it yourself until Google makes with a fix.
Touchscreen Patch Fix:
http://forum.xda-developers.com/showthread.php?t=2428133
Click to expand...
Click to collapse
Correction - "Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies"
That is extracted from his post.
So no one's had a positive experience RMAing the nexus? Do the majority of units have the multitouch problem?
Sfhub's fix helped but I still get the "grounding issue" where the touchscreen goes insane if I place the nexus on certain materials. It sometimes exhibits the same problem when connected to the charger.
Other than that, the tablet works great when I hold it in my hand, no other issue to report... so I'm worried about RMAing my N7 and getting back one that not only has the same multitouch issue but now also randomly reboots or has dead pixels or dust or whatever. My warranty applies to north america only because I bought it off ebay and I don't live in the US so shipping it off to get replaced will get costly if I can't guarantee I get a working replacement back. Can I be sure that like, the newest batch of nexus 7 has been fixed and the replacement will be of that batch?
Since they're not sure what the problem is (one Google groups poster states that ASUS has had his for a month with no ETA on a fix, or when he'll get it back) I'm not sure how they can fix anything , or be certain that what they've been shipping is 'good'.
https://productforums.google.com/forum/#!topic/nexus/mG4JXaT-SHs[1-25-false]
Come and join in the fun.... :/
Looks like loads of fun. Seems I should be grateful I was lucky enough that my touch-based tablet only has a malfunctioning touch screen.
danvee said:
Since they're not sure what the problem is (one Google groups poster states that ASUS has had his for a month with no ETA on a fix, or when he'll get it back) I'm not sure how they can fix anything , or be certain that what they've been shipping is 'good'.
https://productforums.google.com/forum/#!topic/nexus/mG4JXaT-SHs[1-25-false]
Come and join in the fun.... :/
Click to expand...
Click to collapse
Dude, that forum is almost like spam. I reported my issues early, 3 weeks ago or more.
Since then I get from 10+ to 20+ reports (of multiple posts) per day of people reporting issues in email. People might be worrying about me when I get two or three reports in one meeting and I'm chuckling at the comments. LOL
Seriously, it is a good idea to report your issues at that location. But, think twice about subscribing to the topic.