Related
Edit 30 dec 2010:
see my last post in page 4
GPS suc*s when tested in high roads density urban areas
Hi,
I see many debate here about Galaxy S issues, mainly lag and GPS.
I was scared when got one, but finally, becoming a fan boy too:
In answer to this topic:
DSF said:
1) Test Google search (press and hold option button in home). Press a leter, for eg N. Now you have to wait seconds. Just web, apps are in searchable items. Without web suggestions
2) Swype
3) Manage apps
4) List processes
5) Apps shortcut
6) TouchWiz app drawer
7) Browser (still on JP6 ATM)
And so many issues.
Click to expand...
Click to collapse
So I tested in my SGS, recently bought (3 weeks):
GPS driving on road behaves like my Sirf III module (but under Navigon, google maps not tested)
Google search is fine (lag less than 1sec)
Swype: really smooth
Manage apps: small lag, max 1 sec or less
Apps shortcut: first time just 1-2 sec, than instant
App drawer is fine, lag is really minimal to abscent, far less than 1 sec when it is there
Browser: no issues
It came with JM7 bundled, never updated firmware as I don't see the need. Bought it in october, just after an out of stock long period
I'm really thinking there are some hardware issues solved recently. My SGS seems to behave like the one from "fanboy"
I'm not going to become a fanboy, just maybe helping with my case. If it is really hardware dependent issues, a mass RMA would help samsung to admit the problems (that they look like have solved in newer devices?). After all, Apple, with their small antenna bug was finally more fair than Samsung.
I really open this topic to give a positive feedback. I also wonder why I have a "perfect" SGS, while many have a bad one? If it is not hardware, what can it be?
Maybe people that get new units, bundled stock with a new firmware (mine was JM7), should give a feedback here.
If it is hardware, why not RMA and put pressure on Samsung
jonny_ftm said:
Hi,
I see many debate here about Galaxy S issues, mainly lag and GPS.
I was scared when got one, but finally, becoming a fan boy too:
In answer to this topic:
So I tested in my SGS, recently bought (3 weeks):
GPS driving on road behaves like my Sirf III module (but under Navigon, google maps not tested)
Google search is fine (lag less than 1sec)
Swype: really smooth
Manage apps: small lag, max 1 sec or less
Apps shortcut: first time just 1-2 sec, than instant
App drawer is fine, lag is really minimal to abscent, far less than 1 sec when it is there
Browser: no issues
It came with JM7 bundled, never updated firmware as I don't see the need. Bought it in october, just after an out of stock long period
I'm really thinking there are some hardware issues solved recently. My SGS seems to behave like the one from "fanboy"
I'm not going to become a fanboy, just maybe helping with my case. If it is really hardware dependent issues, a mass RMA would help samsung to admit the problems (that they look like have solved in newer devices?). After all, Apple, with their small antenna bug was finally more fair than Samsung.
I really open this topic to give a positive feedback. I also wonder why I have a "perfect" SGS, while many have a bad one? If it is not hardware, what can it be?
Maybe people that get new units, bundled stock with a new firmware (mine was JM7), should give a feedback here.
If it is hardware, why not RMA and put pressure on Samsung
Click to expand...
Click to collapse
Many people still have release-day SGS's and they work just as good as yours; some people have the problem and some just do not. Was there a hardware update? We don't know and if there was, why would Samsung not announce something and try to put themselves in a terrible position?
We just don't know. I have a release-day SGS myself and the only problem I've had was the button's delaying (which is quite annoying) and "the Black Screen of Death" a few times (which was fixed by not putting on a hard-case from Bell).
hol17 said:
Many people still have release-day SGS's and they work just as good as yours; some people have the problem and some just do not. Was there a hardware update? We don't know and if there was, why would Samsung not announce something and try to put themselves in a terrible position?
We just don't know. I have a release-day SGS myself and the only problem I've had was the button's delaying (which is quite annoying) and "the Black Screen of Death" a few times (which was fixed by not putting on a hard-case from Bell).
Click to expand...
Click to collapse
Hi. Just a couple of questions for you if you dont mind.
1.) When you say "Black Screen of Death, do you mean the weird Coma/Crash syndrome? Mine from Bell as well just started doing this about 60 days into owning it and it has happened a total of 3 times in the last 5 days or so.
2.) What do you mean it was SOLVED by not putting on a Hard Case from Bell? I have one from Bell (looks like leather on the back) and you now have me wondering. I have had the case almost since day one though and my phone just started the Coma/Crash as mentioned above about 60 days after owning it. Please advise...
3.) A bit off topic but I see you are rooted on JH2. Can you please tell me how you rooted the device? I have tried the update.zip files I have found before but none of them ever work for me. Do you need to be sim unlocked for the root to work? Please advise...
Thank You...
@yiannisthegreek
1.) When you say "Black Screen of Death, do you mean the weird Coma/Crash syndrome? Mine from Bell as well just started doing this about 60 days into owning it and it has happened a total of 3 times in the last 5 days or so.
Click to expand...
Click to collapse
Yes; try to wake the phone and I just can not, no matter what I do and thats when...
SEGWAY
2.) What do you mean it was SOLVED by not putting on a Hard Case from Bell? I have one from Bell (looks like leather on the back) and you now have me wondering. I have had the case almost since day one though and my phone just started the Coma/Crash as mentioned above about 60 days after owning it. Please advise...
Click to expand...
Click to collapse
I'll break it down for you; my problem with the BSOD started to happen after I attached my cases I bought from Bell (the semi-clear hard grey case and the fake crocodile skin case). The cases felt VERY snug to my phone, almost 'death-gripped' (which meant the cases were difficult to take off, almost 'ripping-the-backplate-off' difficult) and I could feel heat through the case. After taking them off, I have never had the BSOD since, although my phone feels a bit naked. I had also UNROOTED my phone but the BSOD happened a few days later (with the case on).
3.) A bit off topic but I see you are rooted on JH2. Can you please tell me how you rooted the device? I have tried the update.zip files I have found before but none of them ever work for me. Do you need to be sim unlocked for the root to work? Please advise...
Click to expand...
Click to collapse
This is the post where I got my update.zip:
Code:
http://forum.xda-developers.com/showpost.php?p=7536130&postcount=11
The steps were guide-lined here:
Originally Posted by AllGamer
Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=7536130&postcount=11
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source http://developer.android.com/sdk/index.html )
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volumen up down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box
Click to expand...
Click to collapse
Hope that helps
I got mine also after the "outstock" period.
Got 2, first one had weird issue, rebooted for no reason and, in the end, USb would work and, everytime I pluged it in (PC or recharge) it would reboot in a loop :S
All of this in the first week
Got it exchange and since then, no reboot, no connection issue, no "lag" and GPS is more than decent (I use it to track jogging and it's right on the spot)
Manif. date of this one is 10.09.21 (specific date on the battery, on the device itself it's 10.09, no day)
I do wonder the same thing as you do, might be a good idea to note the manif. date and if user has issue or not...It might give help to some of us with unreliable SGS get it exchanged!
If the manufacturing date gives different hardware, I would definitely send it back again to get a latest one. My replacement didn't solve the GPS issue...will talk to orange uk again tomorrow...
I agree with thread creator. My SGS works fine right at the beginning (except the lag). I see a date on the battery which is 2010.08.03.
I also think it may be hardware-related issues.
Car navigation software such as Navigon accepts an enormous range of errors though. But the errors are exposed when using GPS for fitness purposes (because if the tracks swing wildly side to side then you do the 10km jog in 7km).
I think it might be hardware these days, but waiting for froyo official to see. After that I'll return my phone as many times as necessary
apart from the gps inaccuracy, there's nothing to complain about! the sgs is simply brilliant however, i'd be happy if they put in more ram on the device :|
the gps update frequency is bad, and sometimes is terribly inaccurate
Has anyone tested, one of these phones, with a bluetooth sirf 3 gps?
I would assume, to a certain extent, that it would help prove, if it is a hardware fault or not.
Are there other factors involved, however?
@jonny_ftm just try a Froyo build. I was pretty happy with Eclair in terms of performance (of course some issues where there too, but not that many).. but froyo has some nice additions (eg: input cursor, copy text from browser, flash support, etc) but it sucks in terms of performance. Even the latest builds (JPO, JPA) seems to suck as some realistic people report.
I have ~ 150 apps in app drawer
I will check the date of manufacture of my phone later and report back.
It could be a good idea to start with this to see if there's really a trend to better hardware with later manufacturing dates.
Sadely, it is not that simple. If in mobile phone industry it works just like in PC electronics, even manufacture date of phone won't help. I explain: intel chipsets on motherboards were often "buggy" in some extent on first production. Later, they enhance the product and produce new build versions of chipset correcting hardware issues. Now, it's upon to motherboard manufacture to use the last chipset build or not. Most time, motherboard manufacture will use old chipset stocks before moving to new one.
So, if we want to know this for sure, only SN and build dates on chipsets inside the phone will be the ultimate proof. Sadely, unlike in PC world, less people open their phones to check components unless they break the screen...
Anyhow, phone manufacturing date can help as early dates would have necessarly early components. Later built phones could or not have the last chipset though.
DSF said:
@jonny_ftm just try a Froyo build. I was pretty happy with Eclair in terms of performance (of course some issues where there too, but not that many).. but froyo has some nice additions (eg: input cursor, copy text from browser, flash support, etc) but it sucks in terms of performance. Even the latest builds (JPO, JPA) seems to suck as some realistic people report.
I have ~ 150 apps in app drawer
Click to expand...
Click to collapse
- I won't try Froyo. Until it is final, we can't say Samsung s**ks, it is just beta testing. My phone works great with original JM7 it came with, I don't need Beta Froyo features if they make the phone unusable. Now, I understand people that need these features getting frustrated. Hopefully, it is not my case, so can't help here
- I only have around 30 applications, I think I won't have more than 50-60 include stock apps. Even a PC with quadcore CPU, 16 Gigs of extreme fast RAM, RAID setup and tons of applications/processes installed will slow down. I don't expect a tiny smartphone to do a better job there. The only OS that was rock stable despite tons of applications is Palm OS, now dead :-(
Mine had 16 6 10 on the battery and I experience the gps issue.
Sent from my GT-I9000 using XDA App
Latest phone aren't struggling with lag out of the box anymore.
householddog said:
Has anyone tested, one of these phones, with a bluetooth sirf 3 gps?
I would assume, to a certain extent, that it would help prove, if it is a hardware fault or not.
Are there other factors involved, however?
Click to expand...
Click to collapse
I tried using my external holux bt gps (which really kicks ass)....but to my surprise i figured android doesn't support external bt gps devices natively! so, google maps or navigation does not bother picking up gps info from the external device. android still has no support....bottom line so we're pretty much stuck with what our sgs can do! sucks i know!
Actually, from what I was led to beleive from the test in the accesories, BT GPS seems to work with everything:
http://forum.xda-developers.com/showthread.php?t=818688&highlight=GPS
See post #10
nope....even in post#10 he mentions that "in theory"! it just wouldnt work and i did a serious amount of research only to realize android doesnt support external bt based gps devices. however, i havent tried in froyo....will do it tomorrow and post if i have any luck!
All working fine here - manufacturing date 25/08/2010
Very interesting, the date manufacture theory I stated seems not that wrong from the few feedback in this thread. If we have more feedback, it will become evident, for those doubting it, that Samsung is just making fun of his customers. They don't intend to admit any defect and won't recall phones unless forced by a massive customers action.
I'm happy I got mine only in October. When I receive my microSD card, I'll open it and add my contribution with manufacturing date for my working out of the box phone.
All this means it is very bad news for people with very laggy, battery consuming and bad GPS phones
dreamtheater39 said:
nope....even in post#10 he mentions that "in theory"! it just wouldnt work and i did a serious amount of research only to realize android doesnt support external bt based gps devices. however, i havent tried in froyo....will do it tomorrow and post if i have any luck!
Click to expand...
Click to collapse
Just install Bluetooth GPS Provider. It's simple.
I mean just from browsing here I am most likely not getting the 10.1. How come there is close to no good things being said? It's like everyone on here has problems with the SGT 10.1....
jamaicansolja said:
I mean just from browsing here I am most likely not getting the 10.1. How come there is close to no good things being said? It's like everyone on here has problems with the SGT 10.1....
Click to expand...
Click to collapse
Because it's in the human nature to whine about stuff that doesn't work right.
So the complaints you see here is not from the majority of Tab owners, just the few that are having some kind of problem with it. Don't read too much in to it.
zaphyr said:
Because it's in the human nature to whine about stuff that doesn't work right.
So the complaints you see here is not from the majority of Tab owners, just the few that are having some kind of problem with it. Don't read too much in to it.
Click to expand...
Click to collapse
The smartest way to purchase tech is to NOT read review's but to read review's from peer's like myself.
I am most likely buying one regardless but thinking closely of getting my Xoom back.
IDC About SD/HDMI Ports..
I do however care about the Lag I am seeing on YouTube vids
http://www.youtube.com/watch?v=Ho72WJVEaSg
Is your tab not laggy?
jamaicansolja said:
The smartest way to purchase tech is to NOT read review's but to read review's from peer's like myself.
I am most likely buying one regardless but thinking closely of getting my Xoom back.
IDC About SD/HDMI Ports..
I do however care about the Lag I am seeing on YouTube vids
http://www.youtube.com/watch?v=Ho72WJVEaSg
Is your tab not laggy?
Click to expand...
Click to collapse
I live in Europe, so I won't get mine until the end of June. Hopefully.
Like you, I don't think the SD/HDMI ports are imortant. I'm not worried about the lag either. I'll be fixed either in an official update, or by rooting and installing a custom rom.
laggy is only the damn honeycomb-sucker-launcher! On 3.0.1 laggy as ****... on 3.1 just laggy... but not so bad as 3.0.1.
Solution:
ADW-Launcher-EX!!!!
No Lags... and every widget... i mean every widget is now resizable. More space on screen... etc.
It completely changes the feel of honeycomb.
Try it out... its an honeycomb-issue not an tab-issue.
Super-S said:
laggy is only the damn honeycomb-sucker-launcher! On 3.0.1 laggy as ****... on 3.1 just laggy... but not so bad as 3.0.1.
Solution:
ADW-Launcher-EX!!!!
No Lags... and every widget... i mean every widget is now resizable. More space on screen... etc.
It completely changes the feel of honeycomb.
Try it out... its an honeycomb-issue not an tab-issue.
Click to expand...
Click to collapse
but does it fix the video-lag that you get on all the tabs? I like HC 3.1 but it treats me like a beta tester, same with all the apps.
jamaicansolja said:
The smartest way to purchase tech is to NOT read review's but to read review's from peer's like myself.
I am most likely buying one regardless but thinking closely of getting my Xoom back.
IDC About SD/HDMI Ports..
I do however care about the Lag I am seeing on YouTube vids
http://www.youtube.com/watch?v=Ho72WJVEaSg
Is your tab not laggy?
Click to expand...
Click to collapse
Live Wallpaper + 6 apps running?
Common guys, this videos was make for apple fã-boys... ridiculous....
I bought mine on Friday. I haven't noticed any lag to the degree in that video. In fact it seldom lags at all.
I did have a dead pixel. I exchanged the tab and this new one is perfect.
The only downer to this thing is that my macbook doesn't recognize it yet. Apple and Samsung not playing nice together. Can you imagine that?
actually there's more issues on the transformer forum. i'm on my 3rd due to quality control issues.
lag is a real issue on my gt101. the input seems to occur maybe a half second behind my finger. very annoying when scrolling web pages. this isn't a honeycomb issue as the xoom and tf don't exhibit this behavior.
also, the gt101 seems to randomly screw up xda bookmarks. i've turned off google sync and it's still screwing them up. neither the xoom or tf does this with syncing. and someone else pointed out that it does it on another samsung device. never had the problem with my gt7 since i've never used the stock browser on it. but hc stock browser is so nice that i prefer it over the 3rd party browsers.
You also have to consider different development teams. Maybe the xoom and asus developers found that bug before they released it. Most of the issues that you're seeing are software related. I wouldn't, not, buy the tablet because of that. When roms start rolling out, lag fixed kernels, etc its going to be a beautiful world. Samsung probably didn't spend too much time on the stuff launcher because they are spending their time on touchwiz. So would guess that's the reason that bug is still there.
X10D3 said:
You also have to consider different development teams. Maybe the xoom and asus developers found that bug before they released it. Most of the issues that you're seeing are software related. I wouldn't, not, buy the tablet because of that. When roms start rolling out, lag fixed kernels, etc its going to be a beautiful world. Samsung probably didn't spend too much time on the stuff launcher because they are spending their time on touchwiz. So would guess that's the reason that bug is still there.
Click to expand...
Click to collapse
You are right.
And generally speaking, don't forget that only the people who have bugs write in blogs. All the others are happy and we don't read about them.
jamaicansolja said:
I do however care about the Lag I am seeing on YouTube vids
http://www.youtube.com/watch?v=Ho72WJVEaSg
Is your tab not laggy?
Click to expand...
Click to collapse
I'm experiencing a small lag on my launcher aswell but my 3.1 Transformer was the same. I believe it's a HC related issue and hopefully it will be fixed in a future update
For what it's worth despite the lag I was experiencing in that video I made I still am enjoying the tab and would recommend it. It's noticeably smoother now after going into recovery and doing a complete wiPe. Not sure what the issue was but I can't seem to reproduce the same amount of lag anymore.
I get the keyboard lag and some issues with the market but nothing of any real significance. This reminds me exactly of the release of the Captivate. Amazing device that was absolute **** for the the first three or four months because of lack of accessories and mediocre performing 2.1 eclair. As soon as devs started ripping into the phone it was like night and day, phone was easily twice as responsive (obviously subjective) after some custom rom goodness. Then finally accessories, mainly cases, came out and by the four month mark the launch of the captivate was finally complete. SO yes Samsung are absolutely horrible at launching new devices, some may call it them trying to drum up hype but its really just them being the morons they are. That said, they usually make a great product that has one fairly sizable flaw but is still better than any of the products it competes with.
Like the galaxy, but will wait until bugs are worked out first, than decide on a purchase. Too many issues at launch, which is now the norm for all the tabs that are out, and that includes the IPad 2 with screen issues.
3.1 is still in need of lots of work, and 3.5 would be better if ever released this year. Too bad, was looking forward to this tab, but now I'll wait and read up on the users reviews for awhile longer.
Good luck early adopters
i have my 10.1v for about a month now. i don't have an problems or complaints, except for the poor battery life compared to an ipad (but battery ist still good though).
I have had a really good experience so far with my SGT 10.1. The keyboard lag is fixable by turning off haptic and changing my keyboard to either a SlideIT or Thumbs.
I will also say that the HC launcher in general is very laggy and I'm considering going with ADW or LauncherPro. For videos I use Freemake Video converter (free!) and Mobo Player and I have no issues at all. I got into the habit of converting all my media anyway because of my iPad not being able to play my avi's.
Also, live wallpapers kill this device... I wonder if the lag is an OpenGL issue?
X10D3 said:
You also have to consider different development teams. Maybe the xoom and asus developers found that bug before they released it. Most of the issues that you're seeing are software related. I wouldn't, not, buy the tablet because of that. When roms start rolling out, lag fixed kernels, etc its going to be a beautiful world. Samsung probably didn't spend too much time on the stuff launcher because they are spending their time on touchwiz. So would guess that's the reason that bug is still there.
Click to expand...
Click to collapse
Xoom update to 3.1 did come directly from Google, so i doubt Motorola had much to do with it. Looking at the GT10.1 videos, it seems to me that Samsung has made some small tweaks and this has caused some problems that the other 3.1 tablets don't have.
Be careful, only Xoom bought in US.
Non-US Xoom owners are still on 3.01 with promised to be updated in couple of months (Source: Moto forum).
poisike said:
Xoom update to 3.1 did come directly from Google, so i doubt Motorola had much to do with it. Looking at the GT10.1 videos, it seems to me that Samsung has made some small tweaks and this has caused some problems that the other 3.1 tablets don't have.
Click to expand...
Click to collapse
TheBigSaxon said:
I have had a really good experience so far with my SGT 10.1. The keyboard lag is fixable by turning off haptic and changing my keyboard to either a SlideIT or Thumbs.
...
Also, live wallpapers kill this device... I wonder if the lag is an OpenGL issue?
Click to expand...
Click to collapse
It could very well be an OpenGL issue. I noticed when I turned off OpenGL rendering in the browser my input lag disappeared. And Thumbs is pretty much the greatest keyboard for a tablet evar.
To the OP, I love the **** outa my GT. Played with a friends Xoom but disliked the bulky feeling of the device. The GT is svelte, smooth, and sexy.
im still debating this tablet, but i want reeeeallly bad. so heres my background, i get easily frustrated when something doesn't work the way it should, im on my 3rd Samsung Infuse with in a month... but anyways, i was browsing the all 135 some pages and i see people having well, a lot of issues, chargers, screens, speakers (pop... whatever that is, seems to be known around the threads.) i read about people sending them in for repair. so i need to know what are the serious issues with this tablet. issues that everyone has recognized as a known issue,
This mostly happens most with 1st/2nd/3rd/4rd batch/shipment. I think new batch with the serial no# b5xxxxxxx or higher doesn't have noticeable issues.
B5 still have issues, but keep in mind that this is still a minority of people. The majority are enjoying a near perfect experience hardware-wise. A very common issue is light bleed, though in most instances this is very minimal. Mine had, unfortunately, the major issue of having an unresponsive area on the screen, which is why I RMA'd it.
I'd still choose this tablet any day if I had to start over again. Hell, even with the defective touchscreen it was still an awesome tablet Can't beat this screen right now, and the dock is great!
Sent from my Atrix
I just got my Tf a few weeks ago (and hey, it is a B5) and the worst problem i've had is there aren't enough hours in the day to enjoy it. Nothing like firing up GOF2 THD for a little while then reading same Douglas Adams. Oh, and then watching Hulu. I do that whenever stuff whenever i see an ipad user.
Transformer27 said:
im still debating this tablet, but i want reeeeallly bad. so heres my background, i get easily frustrated when something doesn't work the way it should, im on my 3rd Samsung Infuse with in a month... but anyways, i was browsing the all 135 some pages and i see people having well, a lot of issues, chargers, screens, speakers (pop... whatever that is, seems to be known around the threads.) i read about people sending them in for repair. so i need to know what are the serious issues with this tablet. issues that everyone has recognized as a known issue,
Click to expand...
Click to collapse
Yes. The TF has reported problems. Nothing is perfect much less new products. I count myself fortunate that my TF works pretty well. From what I have read android itself can be frustrating especially when one tinkers with it but then that is part of the enjoyment of android. Learning. Reading your post my first thought would be to suggest you wait. The TF, as most android products, can be frustrating but also keep in mind that you're not reading about the majority of TF users who either haven't had problems or have dealt with them.
Even a new Porsche can have problems!
im okay with the light bleed. and i know about the speakers not being even. but whats this speaker pop thing about?
I don't have any problems, I can tell you that mine is perfect. I don't care if you believe it or not
Transformer27 said:
im okay with the light bleed. and i know about the speakers not being even. but whats this speaker pop thing about?
Click to expand...
Click to collapse
I can answer that question,
there are 2 kinds of popping sound from the speaker discussed in this forum,
the first one is with rooted user using overclock kernels.
occasionally the speaker would make a "pop" sound (when you get notifications)
but that does not happen to unrooted users, and in fact, the lastest kernel seems to get rid of that question already.
another popping sound issue if reported from people streaming music from the "google Music" app.
sometimes after a certain amount of time listening to music using the app, the speaker, actually the headphones, speaker doesn't have such issue, start to produce some kind of "impurity", a constant popping sound.
But the issue can be easily solved by unplugging the headphone and replugging it. I've tried jumping straight to Youtube app when I start hearing the popping sound, and it's not there in the youtube app. So i suspect its more of an software issue. Asus is already looking into it the last time I checked.
What about the dock issues?
This video sums up all the serious issues: http://www.youtube.com/watch?v=JmvCpR45LKA
seshmaru said:
This video sums up all the serious issues: http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
well some one doesnt get a thanks button click... ass....
There are a LOT of useless threads on this forum, but this one doesn't qualify. I can understand that, after a few months , it gets tough to know what issues are still relevant and which ones are a thing of the past. So this youtube noob reply was totally unnecessary.
Sent from my Atrix
My dock has zero issues. It charges, it registers the keys, mouse works great with USB ports, haven't tried the sd card. And the touchpad is amazing.
Sent from my Atrix
I promise you that 99% of the people complaining are just being the biological trolls that they were born as.
The TF is a great device and IT WILL do everything it was intended to do pretty damn well. The dock definitely takes some getting used to, especially if your not used to mini netbook type keyboard.
But it is really responsive and adds legitimate battery life and functionality to the device.
The few bugs that the TF does have are very minor and will be sorted out with time just like ever god damn piece of hardware in the world...For some reason people don't know how to do anything but complain on these forums. Don't be swayed by them, chances are they are very incompetent in real life and look to the internet to hear out there pathetic pleas for attention
I beg to differ @ previous poster. There are legitimate QC issues here. I've gotten 4 different units sent to me in the last two week and each had issues. The latest has a whole section of the x axis (in landscape) about a finger width wide unresponsive to touch all the way across the screen. Bull**** in my opinion. Also look at the beautiful RMA threads here. Really making me contemplate my decision. I love the device and its capabilities, but am discouraged by these shortcomings of the manufacturer.
Sent from my HTC Glacier using XDA App
This is hands down the best thing I have purchased in the last several years, I have to make myself put it down. Having said that, if you are picky then no tablet (android or other) will be good for you. Honeycomb is far from complete or polished and there are problems if you look for them. In my opinion non of them overshadow the experience.
My other devices are collecting dust.
PuerkitoBio said:
There are a LOT of useless threads on this forum, but this one doesn't qualify. I can understand that, after a few months , it gets tough to know what issues are still relevant and which ones are a thing of the past. So this youtube noob reply was totally unnecessary.
Sent from my Atrix
Click to expand...
Click to collapse
Yes it does qualify. This: http://forum.xda-developers.com/showthread.php?t=1041502, is a stickied thread and has a complete ordered list of noted issues with detailed information about the issues. Oh and its up to date since the dates for changes are noted right there and all.
I linked this thread here: http://www.facebook.com/ASUS/posts/209779482398791
I don’t have the dock, so cant comment on that. Instead I’ll comment on the tablet alone. I have the 16GB model with Honeycomb 3.1 (stock no mods, not rooted yet), had it for 6 days, so these are more like my first impressions:
Pros :
Beautiful screen (very little light leak on mine so I’m quite happy. But has one dead pixel though, but not noticeable)
Good battery life (I can easily go beyond 8hrs with moderate use)
Everything (I have tried so far) except web browsing works as it should
Cons:
Web browsing is very disappointing to say the least. The stock browser crashes and lags to the point of being unusable.
Flash video performance in the browser is poor, HD videos breaks up and low res videos are blocky when viewed fullscreen, deblocking filters don’t work properly or not at all.
Video Playback isn't the best But Theirs Work Around (HandBreak and Different Video Players)
Flash in my opinions is fine but It can be improved
Music is awesome especially with Volume+ App
Games are Very Good. I play Spectral Souls and Galaxy on Fire 2
Screen Is Beautiful (Some Light bleed but all IPS have this problem yes even Ipads)
Overall Performance is Good (A Little Laggy with Widgets but ADW EX can fix this)
Browser is my Main Gripe. It Looks amazing and Loads Fine but Theirs Typing Browser lag and it Kills the Experience. Its not a Hardware Problem its Software. Its eather Honeycomb or Asus Custom UI. Idk which but it should be fixed :x
All in All its an Amazing Device and if The Browser Typing Lag gets Fixed, Then this thing would be BEAST. Theirs a Rumored Android 3.2 that fixes alot of HC Issues coming out in the next few weeks so thats Might be what everyone is wishing for. until then we gotta wait on Asus/Google.
Edit: I Should Mention thats Their is ONLY typing Lag in Browser and Not Writing Documents/Apps. Strange..
I've seen a bunch of TF101s in the $260-280 range lately...do you folks think one of these is worth picking up? I see the processor is a bit outdated, but the Jelly Bean roms available look like they work well. I'm interested in the 10" size and SD-slot for this price range, both of which the Nexus 7 doesn't have.
Bump. Also wondering
Sent from my PG86100 using xda app-developers app
I think the TF for under $300 is a good deal especially if you're going to overclock it. With a little overclocking, Tegra 2 can still run almost anything very well.
Sent from my Nexus 7 using xda premium
The tf101 is a wonderful tablet. I just bought a tf700, mostly for the screen, otherwise my tf101 would have been more than good enough for a long time still. I'll be selling my tf101 soon, but it's,a great tab.
going to be trading for a tf101 tonight cant wait to root and play around with it.
RUN AWAY!!!
I'd like to hope this is just my experience....but I'd avoid this tablet. It was the WORST purchase I've ever made.
The performance was lake-luster from the start. the first ICS firmware update brought my tablet to a screeching halt...and while the additional updates have made improvements and fixed a few issues, I still have major performance problems. These issue were NOT related to rooting...as I was trying NOT to root unless I absolutely had to (which I ultimately did just to have the tablet for use...it was that bad. I've tried two ROMs that are better and make it actually useful, but the headaches and the HOURS spent just weren't worth it.
1. Constant and frequent reboots...often in the middle of working on something
2. The sleep issue (which has improved....). Often when you let it "sleep", it goes into a "deep sleep"...you can't power it back up and it's fully running (but you can't see it or do anything)...so it drains the battery fast. Only fix was a cold linux reboot.
3. About 3-5 times a week...the tablet simply slows down...and when I say slow...I mean that every thing you do...(press a button, open a menu, select an option...anything) takes from 50-seconds to 3 minutes to complete (I timed them)...just getting to the app settings or an app that can tell you what is going on takes 20 minutes or longer. Only solution has been to try the cold-reboot...but that doesn't work about half the time...seriously. Can't even reboot. All I can find is...the acore process is running....twice. Both using 100% of the processor and memory. I haven't a clue what is going on there.
4. Rooting issue as well. Difficult to do, had multiple problems booting into and recovery..then probelsm with regular rebooting. See the forum for all the issues
5. Surprised I don't hear more about this problem....the IDIOTIC engineers at ASUS decided to label the root directory for the internal memory as microSD (supposedly because the tablet uses one internally for its memory) and the actual external memory card as Removable\MicroSD\..... Why this is a problem? Many of my apps that write, save, or use the SD card can't tell the difference and default to internal memory instead...because the root path is the same as 90% of all Android devices. I can't tell the apps to change the location... Two apps couldn't even function...as they couldn't find where to save data. My "internal" memory is almost full, and the removable SD card has tons of room. This issue holds true for most of the apps that allow you to move apps to the SD card...all they do is move the app data to the other partition of the internal memory...not the actual external SD card.
6. many, many more.
ASUS service....I really don't know why people think they are great. It has been terrible.
1. the average response time to any email service requests has been 3 weeks. Most of the responses weren't related to my problem.
2. No phone call ever resulted in an answer. They always default to "send it in"...which I did once...
3. The tablet was in their possession for two months. When returned...the small pieces of tape I placed over the power and other ports were still in place (evidence that no one had done anything to it) and the issues were still there. ASUS still refuses to acknowledge that nothing was fixed.
If I could afford it, I'd be switching ASAP. Like I said..this has been my experience.
glange65 said:
I'd like to hope this is just my experience....but I'd avoid this tablet. It was the WORST purchase I've ever made.
The performance was lake-luster from the start. the first ICS firmware update brought my tablet to a screeching halt...and while the additional updates have made improvements and fixed a few issues, I still have major performance problems. These issue were NOT related to rooting...as I was trying NOT to root unless I absolutely had to (which I ultimately did just to have the tablet for use...it was that bad. I've tried two ROMs that are better and make it actually useful, but the headaches and the HOURS spent just weren't worth it.
1. Constant and frequent reboots...often in the middle of working on something
2. The sleep issue (which has improved....). Often when you let it "sleep", it goes into a "deep sleep"...you can't power it back up and it's fully running (but you can't see it or do anything)...so it drains the battery fast. Only fix was a cold linux reboot.
3. About 3-5 times a week...the tablet simply slows down...and when I say slow...I mean that every thing you do...(press a button, open a menu, select an option...anything) takes from 50-seconds to 3 minutes to complete (I timed them)...just getting to the app settings or an app that can tell you what is going on takes 20 minutes or longer. Only solution has been to try the cold-reboot...but that doesn't work about half the time...seriously. Can't even reboot. All I can find is...the acore process is running....twice. Both using 100% of the processor and memory. I haven't a clue what is going on there.
4. Rooting issue as well. Difficult to do, had multiple problems booting into and recovery..then probelsm with regular rebooting. See the forum for all the issues
5. Surprised I don't hear more about this problem....the IDIOTIC engineers at ASUS decided to label the root directory for the internal memory as microSD (supposedly because the tablet uses one internally for its memory) and the actual external memory card as Removable\MicroSD\..... Why this is a problem? Many of my apps that write, save, or use the SD card can't tell the difference and default to internal memory instead...because the root path is the same as 90% of all Android devices. I can't tell the apps to change the location... Two apps couldn't even function...as they couldn't find where to save data. My "internal" memory is almost full, and the removable SD card has tons of room. This issue holds true for most of the apps that allow you to move apps to the SD card...all they do is move the app data to the other partition of the internal memory...not the actual external SD card.
6. many, many more.
ASUS service....I really don't know why people think they are great. It has been terrible.
1. the average response time to any email service requests has been 3 weeks. Most of the responses weren't related to my problem.
2. No phone call ever resulted in an answer. They always default to "send it in"...which I did once...
3. The tablet was in their possession for two months. When returned...the small pieces of tape I placed over the power and other ports were still in place (evidence that no one had done anything to it) and the issues were still there. ASUS still refuses to acknowledge that nothing was fixed.
If I could afford it, I'd be switching ASAP. Like I said..this has been my experience.
Click to expand...
Click to collapse
Most of the reboot issues with ics were experienced by folks who refused to factory reset properly, that said some folks had issues, but I experienced almost none of these.
Rooting was a piece of cake, i was rooted day one. Installing ROMS is dead simple and the tab is unbrickable.
Performance compared to other tegra 2 was superior(still is).
Battery life is amazing
Customer support sucks across the board these days, but asus put out more useful updates than any other mainstream mfr.
NEVER rma a tablet unless its your last resort.
The preformance is allright for me -> office and internet surfing AND voodoo sound quality!
Size and display quality sucks ... not to mention in compare to never products.
Using this tablet in the summer? forget it.
What is the use of a mobile device when you have to avoid sunlight?
Anis108 said:
The preformance is allright for me -> office and internet surfing AND voodoo sound quality!
Size and display quality sucks ... not to mention in compare to never products.
Using this tablet in the summer? forget it.
What is the use of a mobile device when you have to avoid sunlight?
Click to expand...
Click to collapse
That's funny since the tf101 had one of the highest rated lcd displays both for quality and use in sunlight. The screen on mine is gorgeous(yes new infinity is better) and brightness was more than enough to use on sunny days.
I heard the TF series are one of the best android tablets out there. Maybe not the tf101 anymore...lol
Sent from my Inspire 4G using xda app-developers app
Well I decided to get a refurb'ed TF101 last night. It was well worth the price I think. Loving it so far. It had ICS out of the box but I rooted & installed Jelly Bean instantly. Rooting, etc. was a piece of cake. I went back to stock & then installed Revolution HD ROM because Jelly Bean is still a bit buggy for me (no fault of the devs, it's labeled Alpha). It runs great! Fast as can be, not seeing any lag anywhere!
It's only been a day but I've had 0 issues with this tablet.
just got mine love it thing flys and no problems except cant get cwm to install
nm got team rogue to work
Bump
Sent from my PG86100 using xda app-developers app
gottahavit said:
Most of the reboot issues with ics were experienced by folks who refused to factory reset properly, that said some folks had issues, but I experienced almost none of these.
Rooting was a piece of cake, i was rooted day one. Installing ROMS is dead simple and the tab is unbrickable.
Performance compared to other tegra 2 was superior(still is).
Battery life is amazing
Customer support sucks across the board these days, but asus put out more useful updates than any other mainstream mfr.
NEVER rma a tablet unless its your last resort.
Click to expand...
Click to collapse
As I stated, this was my experience. I do want to correct you on one thing.... you imply my reboot issues were the result of my carelessness or refusal to follow the correct procedures. I can assure you that this was not the case. I completed the required factory reset just as instructed (I've rooted 4 phones. and flashed ROMs as often as 2-3 times a week. This ain't my first goat rodeo.
I would have rather waited a few months longer for ASUS to update to 4.0 so they got it right the first time. The "useful" updates you refer to were to fix the poor 4.0 update. Seriously, the new features weren't worth this much hassle. Trust me, the only reason I sent it in was, I was too darn tired of dealing with it... figured it was their issue to fix. I sometimes think Android users are way to easy on the manufacturers... we just excuse it away and develop our own fixes, solutions, etc. We don't hold them accountable enough for serious problems and poor service. If/When Microsoft or Apple have these issues... you hear about. The consumer uproar is deafening. I wonder why that is? (I count myself in this as well)
Last thing... I mentioned the memory issue... this effects my nandroid backups as well. they take forever and weigh in 4 GBs each. They are having to back up all that "internal" data... which shouldn't be. beyond manually moving data to the removable card prior to back up and flashing .... still working on a better solution.
Enough... I've said my piece. Remember.... be good, or be good at it.
glange65 said:
I'd like to hope this is just my experience....but I'd avoid this tablet. It was the WORST purchase I've ever made.
...et cetera...
Click to expand...
Click to collapse
Never experienced any of these problems, expcept for #5 which is just a little design flaw.
If you don't need tegra3 quad core and FullHD resolution, the TF101 is still good to go. 720p is still a bit dodgy on stock kernel. JB is on its way, but is hardly a usable rom (for me). ICS is still good enough.
Update
Thread, but in case anyone goes looking for info about this tablet.....
The issues and bugs continued, some minor, and some VERY big, making the tablet almost unusable.
Finally, two weeks AFTER the warranty expired, the processor fried. Just set it down to get a drink, came back 5 minutes later to dead, nothing. Three experienced techs all independently diagnosed a dead processor.
So in a word...The ASUS Transformer Pad 101 was a worthless piece of garbage.
glange65 said:
Thread, but in case anyone goes looking for info about this tablet.....
The issues and bugs continued, some minor, and some VERY big, making the tablet almost unusable.
Finally, two weeks AFTER the warranty expired, the processor fried. Just set it down to get a drink, came back 5 minutes later to dead, nothing. Three experienced techs all independently diagnosed a dead processor.
So in a word...The ASUS Transformer Pad 101 was a worthless piece of garbage.
Click to expand...
Click to collapse
Wow, I had no idea worthless piece of garbage is one word.
My warranty has been out for 8 months and it is still running Android 4.2.2 just as smoothly as a Nexus 7 or Nexus 10. IMO, it is a solid device.
If I were buying today, I do not think I would spend more than $150 on the tablet, or $250 if it comes with a keyboard dock myself, I would get a newer tablet.
frederuco said:
Wow, I had no idea worthless piece of garbage is one word.
My warranty has been out for 8 months and it is still running Android 4.2.2 just as smoothly as a Nexus 7 or Nexus 10. IMO, it is a solid device.
If I were buying today, I do not think I would spend more than $150 on the tablet, or $250 if it comes with a keyboard dock myself, I would get a newer tablet.
Click to expand...
Click to collapse
Lol. Exactly... It was an amazing tablet when it came out, it's still a very good tablet 2 full years later. Yes, it was released 2 years ago (well, 21 months). I own 2, that I bought refurbished with the dock (also refurb), and haven't had a single hardware issue. I also know 2 other people that own one, and they also haven't had any hardware issues. Based on posts here on XDA, Asus will almost always blindly replace your defective parts even if you're rooted, rom'ed, etc as long as you're still under warranty.
As a contrast, I have 4 co-workers that bought the Nexus 7. Three of them had to RMA it within 2 months, and one of those had to buy a new one because Google/Asus kept throwing each other the ball and no one wanted to honor the warranty. Only one had a trouble-free tablet.
That being said, your CPU fried for a reason, CPUs don't simply "stop working". I've been working in IT for over 15 years and I have yet to see that happen. I'm not saying it's something you did, or didn't do, as I have no way of knowing. But there was an other problem that caused it to stop working (overvoltage, short, etc). I know at this point it's too little too late and I'm not here to do Asus PR, but chances are it would have happened eventually regardless of how long the warranty was. Just sucks it happened right when the warranty stopped...
Right now, as of March 2013, I don't see any tablet that can compare quality/price ratio to what this one was 2 years ago. Either all overpriced brands or cheap replicas.
i bought this tablet in Black Friday 2011 in an severely overcrowded and riot police-requiring Best Buy and I'm still happy as i can be with it. The hacking community still supports it and I find that there's frequently something new to update it with even if Asus itself has abandoned it. If anyone finds it on the REALLY cheap like $150 or so, i heavily recommend it. I haven't had any issues with it other than some Word-adaptation apps working weird sometimes.
According to Antutu benchmark, the tf300 only performs 50% above the tf101, just so you can have some comparative perspective.
Bought my TF101 back in 2011 when they first came out. I got lucky and found an "open box" unit at best buy with the dock included for $100 less than new (at the time).
It's worked great ever since, regardless of running Honeycomb, ICS or rooted with custom JB 4.2.2 ROM. It doesn't seem to care and has run consistently better with every upgrade. It still has enough hp to do all the things I use it for (games, youtube, HD movies, browsing, fb, the list goes on...). and I will continue to use it for a long time yet. Especially if it continues to receive support from dev's here on Xda with great/stable ROMs.
I love the full keyboard dock and love the crazy-long battery life. It's still a great tablet IMO and well worth $250 with a dock.
As someone who has been hunting for a good Android tablet for months now, I read a LOT of forums and user-reviews. One thing that I've noticed time and time again is that devices that are powered with Nvidia's Tegra processors have an unusually large amount of unhappy users, and the complaints are more or less the same.
- Poor wifi strength/speed
- Touch screen input problems
- Random shutdowns/reboots
- UI Lag
- Device heating up when doing things that are not traditionally intensive tasks.
It's not a Marshmallow (or even Android) problem guys. The combination of some/all of the above problems is comparatively unheard of on Exynos and Snapdragon powered devices. I'm not an engineer so I don't know whether it's a problem innate to the hardware or poor driver support or something else, but I'm enough of an Android fan to have seen a really obvious pattern emerging when looking to buy a device and comparing reviews. I've personally experienced these problems on the Nvidia Shield Tablet K1 and there's a whole giant army of unsatisfied Nexus 9 users out there, and now the Pixel C is sounding like a similar story. You'll recall similar stories about the Nexus 7 2012 as well.
I really wish Google would have waited a little longer and used a next-gen Snapdragon chip in this tablet, it would have been great.
Most of those issues would make sense because of poor software that doesn't utilize the Chipset properly. Not because of the CPU/GPU itself.
It would make sense if you were blaming the touchscreen controller and wifi chipset itself.
I myself have few issues with my Pixel C, and the issues I do have are across all my android devices.
All this speculation about the issues of this device are unnecessary. If you have the device then report your issues to Google for the benefit of all.
Sent from my iPhone using Tapatalk
sleepinlight said:
As someone who has been hunting for a good Android tablet for months now, I read a LOT of forums and user-reviews. One thing that I've noticed time and time again is that devices that are powered with Nvidia's Tegra processors have an unusually large amount of unhappy users, and the complaints are more or less the same.
- Poor wifi strength/speed
- Touch screen input problems
- Random shutdowns/reboots
- UI Lag
- Device heating up when doing things that are not traditionally intensive tasks.
It's not a Marshmallow (or even Android) problem guys. The combination of some/all of the above problems is comparatively unheard of on Exynos and Snapdragon powered devices. I'm not an engineer so I don't know whether it's a problem innate to the hardware or poor driver support or something else, but I'm enough of an Android fan to have seen a really obvious pattern emerging when looking to buy a device and comparing reviews. I've personally experienced these problems on the Nvidia Shield Tablet K1 and there's a whole giant army of unsatisfied Nexus 9 users out there, and now the Pixel C is sounding like a similar story. You'll recall similar stories about the Nexus 7 2012 as well.
I really wish Google would have waited a little longer and used a next-gen Snapdragon chip in this tablet, it would have been great.
Click to expand...
Click to collapse
thing is the nvidia tv device does not have the big lines of problems and it is the device closest to pixel c.. i'd guess the magnets are a source of havoc.
I did some digging today in open source repos - all the below are just assumptions, I don't want to be a smartass.
If issues seem to be hardware related, usually it's the kernel, not the actual HW. One thing is sure, Google/Nvidia guys are working hard to get things right.
Some examples:
There are even separate branches in the Chomium kernel repos to stabilize the Pixel C: https://chromium.googlesource.com/chromiumos/third_party/kernel/+refs - search for "stabilize-smaug" here.
This is almost surely the fix for the repeated key issues of the keyboard (was merged in mid-December): https://chromium.googlesource.com/chromiumos/third_party/kernel/+/5e09b5b68e2a09257cad69870989b7977797f09c
If you search for "touch" on the Chromium gerrit, there are literally dozens of fixes, most of them already merged. One that I think is related to the Pixel C, and might be a key one: https://chromium-review.googlesource.com/#/c/320202/
I've also found a change related to the Pixel C that is still under review, Nvidia guys were talking about a deadline of next Thursday (14th January), until they need to fix something: https://chromium-review.googlesource.com/#/c/314327/ - scroll down to the comments.
So, let's hope we'll receive an update by the end of the month. The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.
PS: This is a bit unrelated, but I've found out from the device tree that the Keyboard firmware can be separately updated (the above fix is actually for the keyboard FW). The FW update will be the part of the system update, and after the first boot once you connect the keyboard a notification will appear to ask you to confirm the update. Afterwards it will apply the update via Bluetooth. Code here: https://android.googlesource.com/device/google/dragon/+/marshmallow-dr-dragon-release/DragonKeyboardFirmwareUpdater/
sethyx said:
I did some digging today in open source repos - all the below are just assumptions, I don't want to be a smartass.
If issues seem to be hardware related, usually it's the kernel, not the actual HW. One thing is sure, Google/Nvidia guys are working hard to get things right.
Some examples:
There are even separate branches in the Chomium kernel repos to stabilize the Pixel C: https://chromium.googlesource.com/chromiumos/third_party/kernel/+refs - search for "stabilize-smaug" here.
This is almost surely the fix for the repeated key issues of the keyboard (was merged in mid-December): https://chromium.googlesource.com/chromiumos/third_party/kernel/+/5e09b5b68e2a09257cad69870989b7977797f09c
If you search for "touch" on the Chromium gerrit, there are literally dozens of fixes, most of them already merged. One that I think is related to the Pixel C, and might be a key one: https://chromium-review.googlesource.com/#/c/320202/
I've also found a change related to the Pixel C that is still under review, Nvidia guys were talking about a deadline of next Thursday (14th January), until they need to fix something: https://chromium-review.googlesource.com/#/c/314327/ - scroll down to the comments.
So, let's hope we'll receive an update by the end of the month. The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.
PS: This is a bit unrelated, but I've found out from the device tree that the Keyboard firmware can be separately updated (the above fix is actually for the keyboard FW). The FW update will be the part of the system update, and after the first boot once you connect the keyboard a notification will appear to ask you to confirm the update. Afterwards it will apply the update via Bluetooth. Code here: https://android.googlesource.com/device/google/dragon/+/marshmallow-dr-dragon-release/DragonKeyboardFirmwareUpdater/
Click to expand...
Click to collapse
i'm thinking if a few big issues do not get resolved by next weekend [1/15-1/17] google may experience a large volume of returns prior to the 1-22 deadline for holiday purchases. google may want to put out an ota in hopes a lot of the issues go away. very nice post, btw, i appreciate all the digging.
OP is correct in his assumptions on the tegra processors. There are always issues with devices that have them especially when the device is first released. Usually it takes about 6 months to get rid of the issues with software/UI updates. The tegra k1 devices did not become stable until July 2015; more than 8 months after there release.....
Sent from my iPad using Tapatalk
sethyx said:
So, let's hope we'll receive an update by the end of the month. The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.
Click to expand...
Click to collapse
Thanks for the digging but they have until around Jan. 22nd to get a fix out. I am not going to go on faith that the two major issues will be fixed. (wifi/touchscreen). The fact it was launched with these issues present on most of them is troubling.
dkryder said:
i'm thinking if a few big issues do not get resolved by next weekend [1/15-1/17] google may experience a large volume of returns prior to the 1-22 deadline for holiday purchases. google may want to put out an ota in hopes a lot of the issues go away.
Click to expand...
Click to collapse
That is what I am thinking as well. I think a lot of people do not notice the wifi download issue because they are either close to their router or are not comparing the speeds next to other devices. I noticed it on day 2 when I was viewing my imgur albums and noticed considerable slower page load compared to other devices. That opened up a can or worms right there.
The touchscreen issue is very noticeable though. Hope these get fixed asap.
For what it's worth i'm 2 floors away from my router and on my 2nd Pixel (first one had a dodgy touchscreen) and the speed is completely fine
atg284 said:
Thanks for the digging but they have until around Jan. 22nd to get a fix out. I am not going to go on faith that the two major issues will be fixed. (wifi/touchscreen). The fact it was launched with these issues present on most of them is troubling.
That is what I am thinking as well. I think a lot of people do not notice the wifi download issue because they are either close to their router or are not comparing the speeds next to other devices. I noticed it on day 2 when I was viewing my imgur albums and noticed considerable slower page load compared to other devices. That opened up a can or worms right there.
The touchscreen issue is very noticeable though. Hope these get fixed asap.
Click to expand...
Click to collapse
My speeds compared to my 6 p were virtually identical. Router on another floor some 25 yds away.
bill3508 said:
My speeds compared to my 6 p were virtually identical. Router on another floor some 25 yds away.
Click to expand...
Click to collapse
Must be nice. What router are you using? Are you on wifi AC or N ?
atg284 said:
Must be nice. What router are you using? Are you on wifi AC or N ?
Click to expand...
Click to collapse
This was my post a while back. 4000 sq ft 3 level home. Upstairs router is a Asus rt66, down stairs is a Actiontek or something like that. I have two different providers , one capped and the crappy dsl is not. I live out in the sticks.
http://forum.xda-developers.com/showthread.php?p=64460576
bill3508 said:
This was my post a while back. 4000 sq ft 3 level home. Upstairs router is a Asus rt66, down stairs is a Actiontek or something like that. I have two different providers , one capped and the crappy dsl is not. I live out in the sticks.
http://forum.xda-developers.com/showthread.php?p=64460576
Click to expand...
Click to collapse
Very odd. I have the same router and get noticeably slower download speeds abound 25-30ft from the router. On a different floor but still. I kind of live out in the sticks as well. Both units had the same exact issue. just wish this wasn't a problem.
atg284 said:
Thanks for the digging but they have until around Jan. 22nd to get a fix out. I am not going to go on faith that the two major issues will be fixed. (wifi/touchscreen). The fact it was launched with these issues present on most of them is troubling.
That is what I am thinking as well. I think a lot of people do not notice the wifi download issue because they are either close to their router or are not comparing the speeds next to other devices. I noticed it on day 2 when I was viewing my imgur albums and noticed considerable slower page load compared to other devices. That opened up a can or worms right there.
The touchscreen issue is very noticeable though. Hope these get fixed asap.
Click to expand...
Click to collapse
I love the tablet and really would like to keep it, wifi issues are a deal breaker though, but I'll be happy to wait till the end of the month provided Google officially accepts the issues, confirms they are not hardware related (not sure if the forum post will be enough) and commits to a fix by the end of the month or at the very least extends the return period sufficiently. Just one guy's opinion.
Mine acts weird with the speed test app. It shows slower download speeds than my service provides during a speed test but will max out my service when actually downloading.
rohmbd said:
Mine acts weird with the speed test app. It shows slower download speeds than my service provides during a speed test but will max out my service when actually downloading.
Click to expand...
Click to collapse
I thought the same until I did side by side comparisons with other devices and there is a web based speed test that you can do as well:
http://testmy.net/
I am a bit curious about the noveau driver. I read that its graphics performance isn't very good in comparison to nvidia's own linux driver when testing desktop gpus in Ubuntu. Why, given this information, would Google use noveau? Also, would Google have forked noveau for ryu?
jamesrick80 said:
OP is correct in his assumptions on the tegra processors. There are always issues with devices that have them especially when the device is first released. Usually it takes about 6 months to get rid of the issues with software/UI updates. The tegra k1 devices did not become stable until July 2015; more than 8 months after there release.....
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Did you mean 2016? I'm a Nexus 9 owner and bought it mostly to play Clash of Clans... Yeah, it can be a lame reason to buy a tablet but it is the truth.
When you reach TH8 (Clash of Clans players know what I'm talking about), CPU &/or GPU can't handle the graphics... Well, I guess that it's still missing something to be solved on kernel side or even the bionic for denver still hasn't been optimized enough since using a custom kernel and OCing CPU and GPU makes graphics somehow become more fluid (while in the game) and the constant stuttering that causes the touch screen input problems (huge problems on this part, I have to touch three of four times on the same place for it to recognize what I want to do) or the lags almost disappears.
Now you're gonna say "But Nexus 9 is a beast and I run X game with it and it's fluid!" Yeah, I hear ya and you're right, but something is going on with this tablet and I still can't figure it out what it is... Is it the non-optimized kernel or the non-optimized bionic? Who knows... OCing is just hiding something that needs to be fixed in my opinion... Oh... Did I mention that the kernel defconfig doesn't have multi-core scheduler support activated (CONFIG_SCHED_MC)?
sethyx said:
The only thing that I think can really be HW-related is the Wifi issue, but I hope I'm wrong.[/URL]
Click to expand...
Click to collapse
It seems that the WiFi issue was also caused by the kernel... https://chromium-review.googlesource.com/#/c/321155/4
sethyx said:
It seems that the WiFi issue was also caused by the kernel... https://chromium-review.googlesource.com/#/c/321155/4
Not cool, NVIDIA, not cool.
Click to expand...
Click to collapse
This is actually great news as hopefully it isn't the magnets or some other hardware related issue and can be fixed.
sethyx said:
It seems that the WiFi issue was also caused by the kernel... https://chromium-review.googlesource.com/#/c/321155/4
Click to expand...
Click to collapse
Just FYI that patchset has nothing to do with the WiFi