Database Users

Galaxy S: is it all about hardware issues solved in recent manufacturing?

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.

Screen freezing after update.

Wasn't sure which section to put this in. Did a search but nothing came up. Ever since update screen has been freezing when going to lock screen. Acer_A500_1.139.05_COM_GEN1 uk version 32GB. Wondering if anyone else has this problem? Could be an app maybe? Thanks
Sent from my HTC Desire using XDA App

OK found another topic about this Sleep of Death issue. Apparently turning off all forms of lock screen solves the problem. Ill try it and see if that helps. It seems to have made a difference already though because mine was doing it almost every time I turned off the display.
Sent from my A500

kebsood said:
OK found another topic about this Sleep of Death issue. Apparently turning off all forms of lock screen solves the problem. Ill try it and see if that helps. It seems to have made a difference already though because mine was doing it almost every time I turned off the display.
Sent from my A500
Click to expand...
Click to collapse
I'm starting to believe this whole sleep thing is a tegra issue. I'm just looking at trends here. This happened on the Gtablet in every ROM I used though very, very rarely with TnT Lite or the newest stock VS had on there before I sold it. Still, it happened. It happens currently on the LG G2x, on the Zpad, Advent Vega and more recently, Asus Transformer and Xoom - so seemingly on most if not all Tegra 2 systems.
Each user experience may be different, but for proof simply google [name of tablet] sleeps and won't wake up. You'll find hits on EVERY Tegra 2 based tablet and also the G2x.
I never saw the issue frequently in my A500, maybe once a week at most. I haven't seen it since the update, so I'm crossing my fingers. I feel 99% that I'll see it again, just hoping it's few and far between.
Obviously this is all speculation, I've based this opinion on observation, research and as I mentioned, trends. I'm not saying it's happening to EVERY Tegra 2 based device owner, but it is happening to many.

Neoprimal said:
I'm starting to believe this whole sleep thing is a tegra issue. I'm just looking at trends here. This happened on the Gtablet in every ROM I used though very, very rarely with TnT Lite or the newest stock VS had on there before I sold it. Still, it happened. It happens currently on the LG G2x, on the Zpad, Advent Vega and more recently, Asus Transformer and Xoom - so seemingly on most if not all Tegra 2 systems.
Each user experience may be different, but for proof simply google [name of tablet] sleeps and won't wake up. You'll find hits on EVERY Tegra 2 based tablet and also the G2x.
I never saw the issue frequently in my A500, maybe once a week at most. I haven't seen it since the update, so I'm crossing my fingers. I feel 99% that I'll see it again, just hoping it's few and far between.
Obviously this is all speculation, I've based this opinion on observation, research and as I mentioned, trends. I'm not saying it's happening to EVERY Tegra 2 based device owner, but it is happening to many.
Click to expand...
Click to collapse
although I can appreciate your attempt to make a connection with this issue and some deficiency lol, google searches of "PENIS VAGINAS" WILL in fact give you search results of PENI and VAGINAS..... so I really don't know how valid your query is.
None the less I will say I have and work with a handful of tegra 2 devices and have never heard on the support end of things about this issue with the exception of the Transformer which, apart from the shoddy build quality issues, is very prone to this issue.

seven2099 said:
although I can appreciate your attempt to make a connection with this issue and some deficiency lol, google searches of "PENIS VAGINAS" WILL in fact give you search results of PENI and VAGINAS..... so I really don't know how valid your query is.
None the less I will say I have and work with a handful of tegra 2 devices and have never heard on the support end of things about this issue with the exception of the Transformer which, apart from the shoddy build quality issues, is very prone to this issue.
Click to expand...
Click to collapse
Well as I said, I owned a GTablet, I've played with a Zpad, Advent Vega and I have been reading up on several forums; pretty much every Tegra 2 device has this problem. It all boils down to the tablet's hibernation mode. It's either turning off, sleeping or freezing when it's not used for a long time and it's affecting these tabs (and phone) to different degrees.
Insofar as the search I mentioned, if you plug in most devices, you'll see they don't have an issue with waking up.
If you plug in the Xoom, TF, Iconia, GTablet, G2x, Avent Vega, Zpad...etc. you'll see they all have users reporting the issue - that was my point
I'm also hard pressed to find other android devices plagued with this issue. They have their quirks but waking from sleep and freezing on wake is distinctly Tegra 2.
Of course, it could just be some giant coincidence and the lowest common denominator is not in fact Tegra 2. I could be way off the bat.

I came from else where in search of a fix for this or at least to find the source of the problem. It's been suggested to do a factory reset, or might be weatherbug app or to use airplane mode with wifi and a few other things. So far it's only conjecture and guesswork it seems. Anyone able to confirm the problem is the tegra2 or perhaps the update? I thought it might be the device itself but according to other forums with the tegra2 it's a recurring issue regardless of device. Hope we get a fix soon, it's rather annoying.
Sent from my A500 using Tapatalk

Just to update. Screen still freezing. Its getting almost unusable now. I thought this latest update was specifically aimed at fixing this. I don't know of this is a honeycomb specific bug or what but it seems not everyone is suffering so I assume it must be hardware. Getting highly annoyed with Acer not taking my enquiries seriously. Anyone else frustrated to the limit yet?
Sent from my HTC Desire using XDA App

kebsood said:
Just to update. Screen still freezing. Its getting almost unusable now. I thought this latest update was specifically aimed at fixing this. I don't know of this is a honeycomb specific bug or what but it seems not everyone is suffering so I assume it must be hardware. Getting highly annoyed with Acer not taking my enquiries seriously. Anyone else frustrated to the limit yet?
Click to expand...
Click to collapse
I also recently updated to the 1.139.04 firmware and the screen has been freezing about 50% or more of the time when waking up even if I just put it to sleep a few minutes prior. I can barely use it all now. If the 3.1 update doesn't fix all these issues it's getting sold. I just don't have the time to fool around with a tablet that half works. I've also been having a lot of issues with the browser and market crashing or not responding at all. I'm starting to feel like I should have just waited for the 3.1 update before even buying it. =/

azraeljarah said:
I also recently updated to the 1.139.04 firmware and the screen has been freezing about 50% or more of the time when waking up even if I just put it to sleep a few minutes prior. I can barely use it all now. If the 3.1 update doesn't fix all these issues it's getting sold. I just don't have the time to fool around with a tablet that half works. I've also been having a lot of issues with the browser and market crashing or not responding at all. I'm starting to feel like I should have just waited for the 3.1 update before even buying it. =/
Click to expand...
Click to collapse
Just to let you know the latest. I upgraded to using 1.1.41.05 and it has solved all of the screen freezing problems. I've been using this patch for 3 days now without any problems/freezing at all. Guide is here
http://forum.xda-developers.com/showthread.php?t=1113878
Thanks a lot all.
Sent from my A500

Nexus 10, is it that bad?

I've been reading for quite awhile because I got myself one (it's still on the way to me, so no hands on yet). I got it mainly because it's a Nexus and I'm done with those 3rd modifications on top of vanilla.
However, I'm getting really mixed comments from all of you guys. Some said it's really nice, some said it's the worst tablet. Although things are always going back to people's own preference but from what I read, 4.2.2 did give lotsa headaches to users mainly because of leaked memory and so.
So users, can you give me your truthful comments from both pros and cons? I can only get the device by next week and after that, it will be my time to list out my very own pros and cons.
Thanks and cheers!
Nexus4 modded with cyanogen.

Yeah, you better cancel your order because some random a holes on the internet did not like something.

Well, the problem is, I can't. Plus, I'm still quite skeptical about the reboots and I have faith that it will be fixed with the update soon.
Are you one of the users?
I'm definitely ok with a bit of problems and it gives me perfect reason to root and tweak it on myself although some do claim that, it should work perfectly fine out of the box.
Nexus4 modded with cyanogen.

I'm running stock and can definitely say that the surfaceflinger memory exists. It becomes obvious when you play multiple videos (streaming or video files). When you do other activities this bug is not readily apparent.
I also from time to time get random WiFi disconnects, which are easily fixed by toggling the WiFi off/on. With that being said I really like my N10 and am using it for more than I expected when I bought it. The display resolution, I/O speed and CPU are all outstanding.
At least the memory leak can be fixed and I read that the surfaceflinger driver developer already has it ready. This gives me hope that Android 4.3 will include the fix. The N10 used as a media consumption device is very good/excellent. I am not disappointed with my purchase.
My laptop at the about same price point (after including N10 accessories) has not been turned on in over three months. All my news reading has move from my desktop PC to the N10. I was surprised at how smooth that transition went.

The only thing that really bothered me about the Nexus 10 is how it could throttle and lower CPU clocks under general usage (general being like playing a game). But then again, the Nexus 4 also does this...
Aside from that though, I find the N10 pretty awesome

The light bleed at the bottom right is the only thing that has bothered me much, but that's because the threads here pointed it out and turned on an OCD switch in me. After almost a month, I had my first two reboots last night, both while watching an hourlong streaming video from a TV network site (using Firefox with Flash). Other than that, couldn't be happier with my N10.

3DSammy said:
I'm running stock and can definitely say that the surfaceflinger memory exists. It becomes obvious when you play multiple videos (streaming or video files). When you do other activities this bug is not readily apparent.
I also from time to time get random WiFi disconnects, which are easily fixed by toggling the WiFi off/on. With that being said I really like my N10 and am using it for more than I expected when I bought it. The display resolution, I/O speed and CPU are all outstanding.
At least the memory leak can be fixed and I read that the surfaceflinger driver developer already has it ready. This gives me hope that Android 4.3 will include the fix. The N10 used as a media consumption device is very good/excellent. I am not disappointed with my purchase.
My laptop at the about same price point (after including N10 accessories) has not been turned on in over three months. All my news reading has move from my desktop PC to the N10. I was surprised at how smooth that transition went.
Click to expand...
Click to collapse
espionage724 said:
The only thing that really bothered me about the Nexus 10 is how it could throttle and lower CPU clocks under general usage (general being like playing a game). But then again, the Nexus 4 also does this...
Aside from that though, I find the N10 pretty awesome
Click to expand...
Click to collapse
JasW said:
The light bleed at the bottom right is the only thing that has bothered me much, but that's because the threads here pointed it out and turned on an OCD switch in me. After almost a month, I had my first two reboots last night, both while watching an hourlong streaming video from a TV network site (using Firefox with Flash). Other than that, couldn't be happier with my N10.
Click to expand...
Click to collapse
Here's the thing that I always talk about. It's a nexus and all problems will be solved for sure by Google itself. With such a good display as well as the A15 architecture proc, it's really a beast and let alone the pure vanilla android.
People are a little bit over exaggerated about the bug, IMO. We receive the newest version and bugs are bearable with me. At least buyers should be aware of the firmware is always the latest which might be a little big buggy. Few positive comments over here are really making my day.

Another thing that bothered me is available RAM. Google states the tablet has 2GB of RAM, which is true (there is 2GB worth of RAM chips installed on the motherboard technically). Before 4.2.2, about 400MB was reserved specifically for the GPU, which is the largest amount of RAM I've seen on any Android device, so that left 1.6GB usable. Not that bad, and it still rounded to 2GB (most other devices though to be fair take like 200-300MB; but the N10 is driving a pretty beefy resolution)
WIth 4.2.2, the RAM reserved for the GPU doubled to 800-some MB (836?). So now the total RAM that the user can use on their own is 1.2GB. No longer nearly close to 2GB.
I guess nothing can really be done about it now, but I don't understand why there just isn't dedicated memory just for the GPU, or why Google doesn't just advertise how much RAM is actually available to use. This isn't an issue at all on most other devices, since the missing memory is usually a small amount, but when almost half of the advertised RAM is missing and not even user-configurable (most computers with IGPs sharing system memory at least let you specify how much you want to dedicated to it)... I find that pretty shady :/
On the other hand, I don't have any out-of-memory problems though (aside from the surfaceflinger thing), so it doesn't seem to be an "actual" issue.

I haven't really noticed anything wrong with my nexus 10 I think its great and fast. Also 4.3 is going to be released soon which should fix any software related issues and make it even smoother . I don't use my tablet as much as others might so maybe that's why I don't notice anything wrong. I generally use it 2-3 hours a day and the only thing I hat is the charging time which feels like forever and that it has a phablet ui rather than tablet look which wastes a little screen space. What they should do is get rid of notification bar and combine it with Nav bar like other tablets
Sent from my Xperia Play (r800x)

abdel12345 said:
... What they should do is get rid of notification bar and combine it with Nav bar like other tablets.
Click to expand...
Click to collapse
Use full!screen and LMT/PIE and get all the screen resolution back (full 2560x1600). full!screen gets rid of both bars and provides a notifications pop-up while LMT/PIE can be configured with all the navigation buttons plus much more. I've been using that combination on rooted stock for months now and would never go back to the waste of space that either bar takes.
I like the clean AOSP browser in fullscreen mode plus thumb controls but it does not always paint properly when used with full!screen (artifacts where the navigation bar used to be). I switched to Ocean browser which is really AOSP with a new UI and that fixed the fullscreen paint issue.

3DSammy said:
Use full!screen and LMT/PIE and get all the screen resolution back (full 2560x1600). full!screen gets rid of both bars and provides a notifications pop-up while LMT/PIE can be configured with all the navigation buttons plus much more. I've been using that combination on rooted stock for months now and would never go back to the waste of space that either bar takes.
I like the clean AOSP browser in fullscreen mode plus thumb controls but it does not always paint properly when used with full!screen (artifacts where the navigation bar used to be). I switched to Ocean browser which is really AOSP with a new UI and that fixed the fullscreen paint issue.
Click to expand...
Click to collapse
Awesome thanks a lot man I'll try that out
Sent from my Xperia Play (r800x)

billy_overheat said:
Here's the thing that I always talk about. It's a nexus and all problems will be solved for sure by Google itself. With such a good display as well as the A15 architecture proc, it's really a beast and let alone the pure vanilla android.
People are a little bit over exaggerated about the bug, IMO. We receive the newest version and bugs are bearable with me. At least buyers should be aware of the firmware is always the latest which might be a little big buggy. Few positive comments over here are really making my day.
Click to expand...
Click to collapse
If you can deal with random reboots don't worry about it. It really is something that depends on use. Watching YouTube via chrome will exacerbate the reboots. The actual app doesn't seem to eat the memory. However for my use I can't have it rebooting in the middle of a meeting or trying to dial into work so it has become something of a paperweight. I know how to consume the memory and how to avoid it but it will still eventually reboot. If your using it for goof off purposes instead of productivity you'll be fine. Also, please don't be an Android/Google apologist. They've had 6 months to fix the issue. And they don't market it as a device with buggy firmware that will reboot. If they called it Nexus 10 developer edition I'd agree with you.
Sent from my Nexus 4 using Tapatalk 4 Beta

billy_overheat said:
So users, can you give me your truthful comments from both pros and cons? I can only get the device by next week and after that, it will be my time to list out my very own pros and cons.
Click to expand...
Click to collapse
Pros:
- Highest resolution tablet on the market, nobody else comes close, even latest iPad has 25% less pixels. I had a Thunderbolt display at work last year and loved working with so much screen real-estate, well, this tablet has even more pixels in 10" than that display had in 27".
- First Android device with beefy Cortex A15 CPU, the Exynos 5 Dual, still the only tablet on the market with A15.
- I actually like the build, fairly thin and I like the sticky material on back.
- For $500 for 32 GB, the one I got, you won't find any device with such high-end specs.
- Android 4.2.2 is usually fairly snappy, sometimes I go back and forth between the home screen and the application drawer just to see the snazzy zoom-in/zoom-out animation and how fast it is.
Each one of these comes with drawbacks however.
Cons:
- You want a high resolution, you have to pay for it with power draw. The display consistently accounts for about 60% of battery usage, even though I keep the brightness at about 30% under light and dial it down to the lowest setting in a dark room. The colors are good but a bit washed out, particularly when compared to an iPad. I wish it had a matte display like my Zenbook, as the glossy display does catch reflections, but I'm not sure that's possible for a tablet.
- The Exynos 5 CPU takes more power than it should and runs somewhat hot. Not as hot as the Tegra 3 in my HOX+, but fairly warm.
- I was surprised how heavy 1.3 lbs felt from the first time I held it. The battery in this thing is huge, 9Ah, compared to 2-3 Ah in most current flagship phones, like the One or S4. It probably had to be so big with that power-sucking display and CPU, but it adds weight.
- The build is a bit creaky and sometimes feels like you have to snap particular pieces back into place, probably to be expected at this cheap price.
- Android still has times when it starts lagging and everything you do takes a second or two to register. These slowdowns often come out of the blue and you're never sure what's going on. This is a mobile OS, so prepare to be frustrated when apps are backgrounded and cached data is lost, particularly if you're expecting something closer to desktop performance because of the specs. The known memory leak in 4.2.2 exacerbates this problem.
I'm happy with my Nexus 10, as I enjoy the high resolution and don't use it anywhere as much as my ultrabook. Now that I know about the memory leak, I may start trying to use it for web reading again, which I had to give up on because it was unusable when Chrome would start reloading every page for no reason. Now I know to reboot when that starts happening, so I at least have a workaround till they fix it.

I love the tablet, for the way I use it - which may be considered light use by most here - it is perfect. The memory issue is real there is no doubt about that. But it is also easily avoided. I reboot my N10 with a tasker profile once during the night and that is that. However I game on it very rarely and use it mostly for streaming movies or just browing the web. One reboot each night seems to be enough to not make these issues appear.
Having said that I have none of the other reported issues, no random reboots or whacky Wifi - I turn Wifi off when the tablet is not in use - but I am also running SentinelRom which seems to be ironing out a lot of the smaller issues. With this ROM scrolling for example has become a silky smooth affair.
Battery life is excellent, much better than the boards make it out to be. I rarely use the N10 with brightness above 25% because it is already so bright on that setting there is no need for it. There may be light bleed - hey it's an LCD after all! - but I never notice any the way I use it. The display is gorgeous in every way, shape and form and I really really like the fact that putting it on lowest brightness makes it really dark. This is perfect for using it in bed at night without getting eye cancer.
With the POGO charger the tablet even has decent charging speed.
Regarding build quality I cannot complain at all. My tablet is not creaky in the least. I had a TF101 which was way worse. I mostly use it with a Poetic smart cover and couldn't be happier. The weight is of course noticeable, but then again this is 10 inches of hardware, it will never feel light as a feather.
Still there are some undeniable software issues still present. The memory leak being one, some issues with scrolling (except when using SentinelRom) being another. But I have yet to see the "perfect" android device which so far does not exist. Google still has a lot of work to do.

rxnelson said:
If you can deal with random reboots don't worry about it.
Click to expand...
Click to collapse
Not getting the random reboots you speak of. Use my tablet 3-4 hours per day, sometimes more, and do not recall having 1 reboot. AOSP browser closures, yes, though with newer versions not as much. Have 2 Nexus 10 tablets, one stock, one sw display itching between SaberMod and Buttered AOKP.
Had both theTF101 and TF700. Went with the ASUS because of it's IPS+ display and SD card slot. 5 weeks after receiving, had to send it in for charging issues..oneof my main problems with the TF101. For the slight amount of money more for the Nexus 10, it is a much better option. Check out Swappa.com-can typically get a slightly used Nexus 10 for a really good price

mpicasso said:
Not getting the random reboots you speak of.
Click to expand...
Click to collapse
You left out my next sentence. It depends on use. I can duplicate the surfaceflinger issue with eventual reboot on stock CM, buttered AOKP, and rasbean. Obviously we use the tablet differently.
Sent from my Nexus 4 using Tapatalk 4 Beta

rxnelson said:
You left out my next sentence. It depends on used. I can duplicate the surfaceflinger issue with eventual reboot on stock CM, buttered AOKP, and rasbean. Obviously we use the tablet differently.
Click to expand...
Click to collapse
I also left out the statement that got me to post originally: "However for my use I can't have it rebooting in the middle of a meeting or trying to dial into work so it mass become something of a paperweight." As the OP was curious about the reliability of this tablet, I wanted to offer a different perspective.
As a tablet for business, I use it for surfing (quote obtained from website, along with any needed client info), note taking, power point and excel, E-mail, along with a few other things. In a given day, I may spend 3-4 hours, while in client homes, using my tablet. So yes, we may use these differently, but for any "business" function I have thrown at it, it works fine. I also do not do many video presentations, which may explain why I do not experience the same issues as you.

Stuttering, lag on internet

Does anyone encounter any serious stuttering or lag when they are scrolling a page on the internet. If anyone has any tips on how to fix it than I'd greatly appreciate it. I'm up to date so I'm hoping there is a quick fix I can do.

mikeakanice said:
Does anyone encounter any serious stuttering or lag when they are scrolling a page on the internet. If anyone has any tips on how to fix it than I'd greatly appreciate it. I'm up to date so I'm hoping there is a quick fix I can do.
Click to expand...
Click to collapse
Depending on the web page, it doesn't scroll as smoothly as an iPad if thats what you were hoping for. But this is the case I find with most android devices. Although, it has been reported that rooting the device and turning off, some of the Samsung Bloatware such as Knox applications, improves it significantly. I personally won't do that because I do like some of the samsung apps and don't want to mess up the tablet's S-Pen functionality, even though the rooting supposedly doesn't mess with that.

A friend of mine recently bought the wifi version and together with my lte variant we started doing some everyday performance comparisons.
One of the things we noted immediately was the stuttering when scrolling in the browser or when pulling down the notification bar. It was nonexistent in the wifi version , but the lte version (even though rooted and free of bloatware) was constantly stuttering. I just hope it was the effect of the performance updates the wifi version received, else I have to say the exynos is superior. What do I want with a snapdragon that can't even handle smooth scrolling..?

mikeakanice said:
Does anyone encounter any serious stuttering or lag when they are scrolling a page on the internet. If anyone has any tips on how to fix it than I'd greatly appreciate it. I'm up to date so I'm hoping there is a quick fix I can do.
Click to expand...
Click to collapse
noctisk said:
A friend of mine recently bought the wifi version and together with my lte variant we started doing some everyday performance comparisons.
One of the things we noted immediately was the stuttering when scrolling in the browser or when pulling down the notification bar. It was nonexistent in the wifi version , but the lte version (even though rooted and free of bloatware) was constantly stuttering. I just hope it was the effect of the performance updates the wifi version received, else I have to say the exynos is superior. What do I want with a snapdragon that can't even handle smooth scrolling..?
Click to expand...
Click to collapse
Thats surprising as I thought for sure the snapdragon would be superior. I have read the speed comparison tests and it gets better benchmarks than the wifi version. The only surprise down the road is the rumored patch that samsung is working on that will allow all eight cores to work simultaneously together which would make the enynos version faster.

noctisk said:
A friend of mine recently bought the wifi version and together with my lte variant we started doing some everyday performance comparisons.
One of the things we noted immediately was the stuttering when scrolling in the browser or when pulling down the notification bar. It was nonexistent in the wifi version , but the lte version (even though rooted and free of bloatware) was constantly stuttering. I just hope it was the effect of the performance updates the wifi version received, else I have to say the exynos is superior. What do I want with a snapdragon that can't even handle smooth scrolling..?
Click to expand...
Click to collapse
My device is the wifi version. Yet still horrible choppiness, stuttering, lagging when I scroll. It is starting to feel like a game breaker to me which would be ashame because the S pen feature is the most wonderfully polished feature ever. I'm a student of course though.

abacus0101 said:
Depending on the web page, it doesn't scroll as smoothly as an iPad if thats what you were hoping for. But this is the case I find with most android devices. Although, it has been reported that rooting the device and turning off, some of the Samsung Bloatware such as Knox applications, improves it significantly. I personally won't do that because I do like some of the samsung apps and don't want to mess up the tablet's S-Pen functionality, even though the rooting supposedly doesn't mess with that.
Click to expand...
Click to collapse
I find it really curious though that with 3 gigs of ram and the type of processor this device has that it shouldn't be running as smoothly as the ipad. I mean spec wise this thing is a monster. Is it just bad software optimization? I'm also afraid of rooting because I've never done it and the term is pretty new to me. I know I'm a noob

mikeakanice said:
I find it really curious though that with 3 gigs of ram and the type of processor this device has that it shouldn't be running as smoothly as the ipad. I mean spec wise this thing is a monster. Is it just bad software optimization? I'm also afraid of rooting because I've never done it and the term is pretty new to me. I know I'm a noob
Click to expand...
Click to collapse
im also scared of rooting.
pretty bad when you have to do something drastic and invalidate your warranty on a £450 tablet just to get it to work properly...

mikeakanice said:
Does anyone encounter any serious stuttering or lag when they are scrolling a page on the internet. If anyone has any tips on how to fix it than I'd greatly appreciate it. I'm up to date so I'm hoping there is a quick fix I can do.
Click to expand...
Click to collapse
Are you using the stock browser? I'm using Dolphin HD. I also downloaded Flash. I found that switching flash to on demand vs always on seemed to help. I occasionally get a slight freeze or crash but overall I'm pretty happy with the Web browsing.

Redline80 said:
Are you using the stock browser? I'm using Dolphin HD. I also downloaded Flash. I found that switching flash to on demand vs always on seemed to help. I occasionally get a slight freeze or crash but overall I'm pretty happy with the Web browsing.
Click to expand...
Click to collapse
I've used puffin, chrome, and stock. In fact, the stock browser has the least issue. Also, has anyone noticed that youtube videos that say HD don't look very good. Sorry, it's my first time with a tablet.

abacus0101 said:
Thats surprising as I thought for sure the snapdragon would be superior. I have read the speed comparison tests and it gets better benchmarks than the wifi version. The only surprise down the road is the rumored patch that samsung is working on that will allow all eight cores to work simultaneously together which would make the enynos version faster.
Click to expand...
Click to collapse
Actually seems like Samsung have nipped that in the bud by saying the wont be doing that.
http://www.phonearena.com/news/Note...Exynos-performance-patch-says-Samsung_id47977

Redline80 said:
Are you using the stock browser? I'm using Dolphin HD. I also downloaded Flash. I found that switching flash to on demand vs always on seemed to help. I occasionally get a slight freeze or crash but overall I'm pretty happy with the Web browsing.
Click to expand...
Click to collapse
Where did you get the flash from..adobe's site says that flash isn't supported anymore since on all devices after july 15th i believe. if you could provide that link it would be great..thx

mikeakanice said:
I've used puffin, chrome, and stock. In fact, the stock browser has the least issue. Also, has anyone noticed that youtube videos that say HD don't look very good. Sorry, it's my first time with a tablet.
Click to expand...
Click to collapse
To be honest, I believe this might be an issue with youtube. I noticed on my note 2014 that I'm only able to play 720p youtube videos. I've tried Tubemate as well as other 3rd party youtube apps that allow you to download videos and I never get any options above 720p quality. Why google/youtube would impose this restriction I have no idea.
The problem with this is that on a tablet with 2560x1600 resolution, content shot at 1280x720 resolution can look less than impressive. However, when you get a hold of quality 1080p content the screen is downright amazing.

abacus0101 said:
Where did you get the flash from..adobe's site says that flash isn't supported anymore since on all devices after july 15th i believe. if you could provide that link it would be great..thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1907606&highlight=dolphin+flash

Geordie Affy said:
Actually seems like Samsung have nipped that in the bud by saying the wont be doing that.
http://www.phonearena.com/news/Note...Exynos-performance-patch-says-Samsung_id47977
Click to expand...
Click to collapse
I already think this tablet gets way too hot for doing normal stuff. I'm not touching octa even if somebody figures out how to hack it. It would probably melt my precious plastic leather.
I'll patiently wait for Samsung to optimize the software. I know this hardware is capable enough, damn it. It's a freaking pull down. That can't be that intensive as to bring a 1.9GHz quadcore to its knees unless somebody coded it wrong.

I think performance is decent enough for this tablet without the octa patch. That is once you tinker with it and optimize everything. My rooted, customized galaxy s3 runs smoother than the beast of a note sometimes. But anyway, that's the fun part.
As for lag or stutter, I do get it, but I think after rooting and cleaning up Samsung's touchwiz, it will get much better.

abacus0101 said:
Thats surprising as I thought for sure the snapdragon would be superior. I have read the speed comparison tests and it gets better benchmarks than the wifi version. The only surprise down the road is the rumored patch that samsung is working on that will allow all eight cores to work simultaneously together which would make the enynos version faster.
Click to expand...
Click to collapse
It wouldn't make it faster anyways....it would just increase battery life as the four cores that become available to you when you need high performance and have high cpu load is the slow, low speed, but power efficient chips. This is with the rumored patch of course. If you already have the a15 based chips all on and ruining at max freq then you will get nothing g, or next to nothing, from turning on 4 lower power ones.
It would be like driving a Ferrari 150mph down a race track and saying you are going to give yourself a speed boost by pushing with your feet....just ain't gonna happen
But in the case of the exynos, you will at least have the option of saving fuel (battery power) by pushing with your feet (using the low power cores) so it would be nice, but it's also been stated by mire than a few people, not sure how reliable these sources are but it's been said by mire than a couple sources, that there will be no patch for the note 3 or the note 10.1 2014 as this functionality will be savedfor a next generation device. Sad but also makes a little sense as these current devices are already basically top of the line and best I'm class, or at least right up there, as far as hardware specs go. Software may not be considered top notch by all but that isn't the point here as if these devices were patched or the functionality was released on the next generation, they both will still come with touch wiz software and thus the software part of it is a moot point. The point is, with or without this functionality, the people who would want to buy it are not concerned about it having touchwiz and thus they are getting the top end device either way. Why would Samsung push this generation device that much farther ahead when they still have a top end device and can save that "trick" for the next iteration....
/end rant

Anandtech in depth WiFi testing of the Pixel C ..... It's bad

http://anandtech.com/show/10081/wifi-testing-with-ixia-wavedevice/4
Anandtech just got a really fancy, manufacturer-grade WiFi testing setup and did some initial testing with the iPad Pro and the Pixel C.
In the case of the iPad Pro and Pixel C, we found that WaveDevice was able to show a number of notable interesting data points from both an end user perspective and an engineering perspective. With the rate vs range test, it was possible to clearly see how well a device would perform in response to worsening reception from a user experience perspective. From an engineering perspective, it was possible to identify the root cause for the Google Pixel C’s poor Wi-Fi performance by using WaveAnalyze and an RF analysis blade in WaveDevice. While determining the root cause is still beyond what we can do with limited information on the hardware, an OEM would be able to act on the information provided by WaveDevice to improve their product before it reaches mass production.
In addition to the rate vs range test, the roaming latency test was quite illuminating. While root cause analysis is more difficult and best left to actual engineers, it’s quite obvious that the iPad Pro passed this test with flying colors while the Pixel C shows some serious deficiencies. If you regularly encounter large Wi-Fi networks with multiple access points all under a single SSID/name like eduroam, it’s obvious that the Pixel C will be an exercise in frustration if you’re hoping to keep a working Wi-Fi connection on the move. Even when the device roams successfully, the time that the device spends moving from one access point to the next is long enough on average to result in noticeable connection interruptions. When it doesn’t roam successfully, it seems to get stuck on a single access point and basically drops off the network entirely without manual intervention or has to re-authenticate and acquire a new IP address, which is guaranteed to cause most traffic to be dropped.
Click to expand...
Click to collapse
In a nutshell, we might need to file a class action lawsuit.

I'm not very technically minded, so just wondering in simple terms, does the article suggest this might be a hardware issue? Something that can't be fixed with future software updates? Thx

aalin13 said:
I'm not very technically minded, so just wondering in simple terms, does the article suggest this might be a hardware issue? Something that can't be fixed with future software updates? Thx
Click to expand...
Click to collapse
From the article:
It may be that we're looking at something like improper impedance matching somewhere in the system, amplifiers that are either poorly selected or poorly integrated, and/or a phase-locked loop somewhere that isn’t set up or designed properly for this task.
Click to expand...
Click to collapse
Basically, they said they are not familiar enough with the hardware in the Pixel C to say if the problem is hardware or software related. Google probably knows, but good luck getting them to admit to anything.

oRAirwolf said:
Basically, they said they are not familiar enough with the hardware in the Pixel C to say if the problem is hardware or software related. Google probably knows, but good luck getting them to admit to anything.
Click to expand...
Click to collapse
Thanks, so there is still hope. This wifi concern is the only thing holding me back from buying one right now, my Nexus 10 has started to have issues with random reboot and extremely slow charging (20 hours to go from 20% to 100%), so I'm thinking of buying a Pixel C as a replacement

aalin13 said:
Thanks, so there is still hope. This wifi concern is the only thing holding me back from buying one right now, my Nexus 10 has started to have issues with random reboot and extremely slow charging (20 hours to go from 20% to 100%), so I'm thinking of buying a Pixel C as a replacement
Click to expand...
Click to collapse
For the record, I have absolutely no problems with WiFi with my Pixel C. I live in a 2 bedroom apartment with a highly saturated WiFi environment. I think the WiFi is unquestionably bad, but my usage scenario generally revolves around reading the news while pooping and watching media in airports/airplanes. In my scenario, none of the problems have even remotely affected me.

oRAirwolf said:
For the record, I have absolutely no problems with WiFi with my Pixel C. I live in a 2 bedroom apartment with a highly saturated WiFi environment. I think the WiFi is unquestionably bad, but my usage scenario generally revolves around reading the news while pooping and watching media in airports/airplanes. In my scenario, none of the problems have even remotely affected me.
Click to expand...
Click to collapse
Haha, sounds like how I use my tablet as well, and I also live in an apartment with saturated WiFi. Guess I can always buy it and return it if the WiFi is an issue. When you say WiFi is unquestionably bad, do you mean that it is slower and has weaker signal than other devices? Given that my home internet is still on DSL, I think I might not even notice the difference in WiFi speed

aalin13 said:
Haha, sounds like how I use my tablet as well, and I also live in an apartment with saturated WiFi. Guess I can always buy it and return it if the WiFi is an issue. When you say WiFi is unquestionably bad, do you mean that it is slower and has weaker signal than other devices? Given that my home internet is still on DSL, I think I might not even notice the difference in WiFi speed
Click to expand...
Click to collapse
I just mean that the problems are widely reported and backed by the test data in that article. I have never had any noticeable issues myself, though.

No surprise here.
IPad Pro is a $1000+ real product with the full forces of Apple R&D, manufacturing and Q&A behind it.
Pixel C is more like a prototype made by a small team inside a big company whose core business isn't to build and sell devices.
It's borderline silly to compare these 2 without comparing the budgets, the staff and the marketing/sales "intentions".
That's been said there is no doubt the Pixel C has room for wifi optimizations but then is this really necessary ? it's not meant to be widely sold at a huge scale. Its purpose is not to have the best wifi possible. I'd rather have Google staff working on next gen Android & Chrome OS features for the Pixel C rather than wasting their time fine tuning & optimizing its wifi...
People should stop considering the Pixel C as a real product. It's more like a dev kit / prototype / experimentation device. Not a real device that you can find in a shop next door like an IPad or a Samsung tablet. It's meant for Googlers to work on new features, for 3rd party apps devs to prepare their next gen apps and for tech enthusiasts to preview stuff.
So, in that context, thinking about a class action is just plain silly.

No problems at all with WiFi. How can ortople be sure it's not an external factor at play? I wouldn't trust Anandtech. They take bribes from anyone with deep edbough pockets. No better than paid for survey companies.
Until they post an ethics and gifting policy, you should disregard anything they have to say.

What exactly is the wifi issue? I got a Pixel C recently, knowing about the issue roughly; but I've never had any issues. I just ran a Speedtest connected to a 5Ghz network and pulled down 106Mbps (down) and 25Mbps (up); this is about the same I get on a wired connection (actually better on average, for some reason).

i've had absolutely no issues, either, but i also have a device from the newer batch (612300) and i'm running n. it actually works better than my nexus 10 in some cases, though i have yet to test it in an area with saturated wifi.

CrazyPeter said:
I wouldn't trust Anandtech. They take bribes from anyone with deep edbough pockets. No better than paid for survey companies.
Until they post an ethics and gifting policy, you should disregard anything they have to say.
Click to expand...
Click to collapse
I am not saying you are wrong, but I have never seen anything to give me the impression that their objective testing is skewed in any way. They clearly have subjective opinions about products and it is no secret they tend to lean towards iOS devices. That being said, they generally have, by far, the most thorough, quantifiable testing and results of any mobile device review site.
Do you have any sources or examples to back up your claims? I would definitely like to know, as I do consider them to be a trusted source for thorough, numbers based, and high level reviews. I tend to leave the subjective opinions up to myself, though.

Proved my deep suspicions from Day 1 and yes there is absolutely ground for a class action here since this product is being sold as the Android tablet , not an experimental product with a disclaimer that core features like wifi may be seriously broken.

undertaker2k14 said:
Proved my deep suspicions from Day 1 and yes there is absolutely ground for a class action here since this product is being sold as the Android tablet , not an experimental product with a disclaimer that core features like wifi may be seriously broken.
Click to expand...
Click to collapse
ROFL so what's a class action gonna do? Get you like $300 cash or $500 of Google play, after 3-4 years.
If you don't want the tablet, sell it, and give it someone who wants it

May be nudge Google's hardware team towards better QAand something is always better than nothing.

No issues with wifi, either using my home router or tethering. So I don't know what the issue is as a practical matter.
Sent from my Pixel C using Tapatalk

I would be interested to know what scenario people are reporting good Wi-Fi performance in. I know that my c definitely has a problem as soon as the Wi-Fi signal drops below -75dB. This happens when trying to use when in the garden. The main issue is that it drops the connection and refuses to connect to it again without the Wi-Fi being switched on & off. It reminds me of the behaviour that I used to get with the 'don't connect to connecting with poor Wi-Fi signal' - except that -75dB isn't really a low signal. All my other android devices (oneplus 2, hudl2 & Nexus 5) all give reliable performance at the same distance (20m).

boboskins said:
I would be interested to know what scenario people are reporting good Wi-Fi performance in. I know that my c definitely has a problem as soon as the Wi-Fi signal drops below -75dB. This happens when trying to use when in the garden. The main issue is that it drops the connection and refuses to connect to it again without the Wi-Fi being switched on & off. It reminds me of the behaviour that I used to get with the 'don't connect to connecting with poor Wi-Fi signal' - except that -75dB isn't really a low signal. All my other android devices (oneplus 2, hudl2 & Nexus 5) all give reliable performance at the same distance (20m).
Click to expand...
Click to collapse
Only had this tablet a week but I have had no Wifi issues and I live in an apartment with metal studs that cause problems for many of my other devices. As a matter of fact I write this sitting in a garden with a -80db signal. I am on N so that may (I hope) have something to do with my lack of wifi issues.

here is a comparsion of my Pixel vs my phone 10 feet from the router. My phone saturates my link, while the pixel comes up 100mbps short. It is still fast enough...but at further ranges it gets worse fast.
https://goo.gl/photos/NdC3KG4186xuifDW6

oRAirwolf said:
For the record, I have absolutely no problems with WiFi with my Pixel C. I live in a 2 bedroom apartment with a highly saturated WiFi environment. I think the WiFi is unquestionably bad, but my usage scenario generally revolves around reading the news while pooping and watching media in airports/airplanes. In my scenario, none of the problems have even remotely affected me.
Click to expand...
Click to collapse
Same here, I live in a tiny, packed city (1.3 square miles, about 50k people) across the river from NYC and I have easily 15-20 WAPs showing up on any wifi device and while I did have wifi problems, turns out it was my sh!tty verizon router and the overly packed 2.4 GHz band. Once I got an AC router and hopped on the 5 GHz band I've had no problems at all!
natezire71 said:
What exactly is the wifi issue? I got a Pixel C recently, knowing about the issue roughly; but I've never had any issues. I just ran a Speedtest connected to a 5Ghz network and pulled down 106Mbps (down) and 25Mbps (up); this is about the same I get on a wired connection (actually better on average, for some reason).
Click to expand...
Click to collapse
I've only seen problems connecting with very poor wifi signals. The only time I ever really had problems connecting was in a hotel where it would see the WAP, try to connect and then fail, even with the "only connect to strong WAPs" option turned off. I have no problems at my apartment or at my parent's house.
undertaker2k14 said:
Proved my deep suspicions from Day 1 and yes there is absolutely ground for a class action here since this product is being sold as the Android tablet , not an experimental product with a disclaimer that core features like wifi may be seriously broken.
Click to expand...
Click to collapse
I'm sorry but people like you are the reason why we need labels on everything warning someone about every possible thing that could happen, just so they can cover their a$$es in case some idiot attempts to sue for something ridiculous (e.g. a warning on a jar of peanuts that says "warning: contains peanuts!"....yes, Planter's peanuts actually has that warning on the jar lol). I think you're using a bit of hyperbole there, the wifi is not "seriously broken" because it obviously works fine for most people, including myself and it seems like largely a software issue since Cheep5k8 has largely fixed most of the issues with his kernel. There's probably not even a large enough amount of people that even on the Pixel C, I wouldn't doubt that less than 50k have it. It's a pretty expensive device that wasn't really marketed at all, not many people outside of Android/Tech geeks know about it.
beardymcgee said:
ROFL so what's a class action gonna do? Get you like $300 cash or $500 of Google play, after 3-4 years. If you don't want the tablet, sell it, and give it someone who wants it
Click to expand...
Click to collapse
More like $3.00 or $4.00 :laugh: Have you even been involved in a class action lawsuit? I've gotten the emails before that says I could claim a payment if I wanted to but the payouts are hysterically laughably low, I think for the Amazon e-book price fixing scandal, I could claim about 10-30 cents because I bought like 5 books from them over the course of a few years. I think the biggest payout I've ever received was a few bucks and that maybe have been on a few hundred dollar purchase, hell even class action lawsuits on cars that cost $30k+ receive payouts of maybe a few hundred dollars hahahaha Instead of selling it and getting something that works better he'd rather keep the tablet then ***** and complain about how the wifi sucks and he deserves to be repaid for buying something with sub-par wifi