Results 1 to 13 of 13
Like Tree5Likes
  • 2 Post By MJKearney
  • 2 Post By mr_nobody
  1. Thread Author  Thread Author    #1  

    Default GooGle Nexus 7 32 GB HSPA+ wifi death grip

    hello all,
    I am new to android. recently moved from apple to android platform.
    I bought this device N7 with HSPA+ few days back.

    Also have updated with 4.2.1, I am seeing a weird issue, if I hold my tablet with my left hand touching the top left corner
    I see my wifi connection dropped off completely and just 1 bar is visible. I read online people mark it as "death grip" problem.

    if anyone else has experienced the same problem, please share with me and if someone is aware of any solution, please let me know.
    I don't want to give up right away, with this sweet device and such a nasty and frustrating issue.

    thanks.
  2. #2  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    I have the wifi-only model, and I notice that it drops off by one bar at the most with a normal, natural grip. If I try to cover the top left corner (in portrait orientation) tightly with both hands, I can get it to drop down another bar, but this will never happen in normal use.

    I don't know if the internal antenna layout is different with the HSPA+ model, but if it isn't, you shouldn't experience any problem in portrait orientation, since it is unlikely that you'd be holding it at the upper left. The only time when it would be a problem would be holding it in landscape orientation. Are you saying that it drops from full strength to only 1 bar, or was it only 2-3 bars to begin with?
  3. #3  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    The solution is to not hold it in that area. I don't mean to sound dismissive, but I think most devices lose signal strength when you cover the area where the antenna is located. So, as Apple said during the whole iPhone 4 antenna-gate hysteria, just don't hold it that way.
    dedduck0121 and mr_nobody like this.
  4. Thread Author  Thread Author    #4  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    guys thanks for replying back.
    yes, when I hold it with my hands ( are small ) it does touch the left top corner and boom, signal drops to just 1 bar.
    Now weird thing is, it is not only just touching the tablet G-spot :P when you hold it with your hands. I observed the same issue when it comes in contact with my body.
    for example laying down on my bed, I rested it besides my leg and signal dropped.

    I totally understand this, but when a person uses a tablet or a phone, he doesnot care much about from where he should hold it and frm where he should not.
    but with this scenario, it seems like user should not touch the device at all. for sure it is the antenna JUNK which ASUS sold to GooGle.

    not sure if they are going to fix it ..
  5. #5  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    Quote Originally Posted by Manish Pawar View Post
    hello all,
    I am new to android. recently moved from apple to android platform.
    I bought this device N7 with HSPA+ few days back.

    Also have updated with 4.2.1, I am seeing a weird issue, if I hold my tablet with my left hand touching the top left corner
    I see my wifi connection dropped off completely and just 1 bar is visible. I read online people mark it as "death grip" problem.

    if anyone else has experienced the same problem, please share with me and if someone is aware of any solution, please let me know.
    I don't want to give up right away, with this sweet device and such a nasty and frustrating issue.

    thanks.
    I wouldn't call that a death grip especially when it only drops 1 bar. that's normal for any device. signal travels through concrete walls but they lose signal strength.
    same when you cover your antenna with your hand it loses the ability to get good signal.

    Now, iphone's death grip was a different story. it dropped 3 bars when hold that way.
  6. #6  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    Quote Originally Posted by still1 View Post
    I wouldn't call that a death grip especially when it only drops 1 bar. that's normal for any device. signal travels through concrete walls but they lose signal strength.
    same when you cover your antenna with your hand it loses the ability to get good signal.

    Now, iphone's death grip was a different story. it dropped 3 bars when hold that way.
    The OP said it drops to one bar, not by one bar.

    Seems a bit much to me.
  7. #7  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    I have this model and have never noticed this issue. But maybe I don't hold it in a way to produce this problem.

    Sent from my Nexus 7 using Android Central Forums
  8. Thread Author  Thread Author    #8  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    guys, this device looks weird to me. it appears they haven't tested the most important part of a tablet, the Wifi.
    its so unstable. check this link . I will try this one and post the results.

    See the pic where I am holding my device you can see I just have 1 bar left, and I also pasted the ping results. man it is timing out.





    Pinging 192.168.0.222 with 32 bytes of data:
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=6ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=10ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=193ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=214ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=72ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=13ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=40ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=110ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=27ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=49ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=50ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=67ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=142ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=64ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=58ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=17ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=7ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=12ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=36ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=14ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=85ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Request timed out.
    Reply from 192.168.0.222: bytes=32 time=71ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=13ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=28ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=30ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=7ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=6ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=6ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=9ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=17ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=11ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=13ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=31ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=26ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=38ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=48ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=34ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=63ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=236ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=207ms TTL=64
    Request timed out.
    Request timed out.
    Reply from 192.168.0.222: bytes=32 time=393ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=120ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=15ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=39ms TTL=64
    Request timed out.
    Reply from 192.168.0.222: bytes=32 time=209ms TTL=64
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 192.168.0.8: Destination host unreachable.
    Reply from 192.168.0.8: Destination host unreachable.
    Reply from 192.168.0.222: bytes=32 time=2182ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=272ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=241ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=207ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=202ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=217ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=206ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=221ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=25ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=8ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=49ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=10ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64
    Reply from 192.168.0.222: bytes=32 time=4ms TTL=64

    Ping statistics for 192.168.0.222:
    Packets: Sent = 126, Received = 119, Lost = 7 (5% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 2182ms, Average = 60ms
    Control-C
  9. #9  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    No need to post the same thing in multiple threads...

    Honestly, is that really how you hold the device? It doesn't look very natural to me.

    If you are having wifi problems, you could try the trick where you pop the back off and bend the antenna bits upward/outward to better contact the case/back. If you search this forum, you should find some references to how this is done. Otherwise, I'd suggest returning the device.
    MJKearney and Dr. Guzzi like this.
  10. #10  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    Hold it lower.
  11. #11  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    The Nexus 7's Wi-Fi operates on the 2.4GHz band (like your microwave oven), this frequency is particularly well absorbed by water (of which there is a lot of in human flesh), so it isn't surprising that your hand does a good job blocking the signal. It is just simple physics and there isn't really anything that can be done about it, other than using an external antenna which most people don't like.
    Thanked by:
  12. #12  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    Position holding advice and jokes aside, I am curious if using a case on the N7, as was the solution for the iPhone 4, would help you.
  13. #13  

    Default Re: GooGle Nexus 7 32 GB HSPA+ wifi death grip

    Quote Originally Posted by Solutions Etcetera View Post
    No, it won't. The issue with the iPhone was bridging two antennas that made up the frame with your fingers. The bumper insulated the antennas to prevent that.
    THIS.

    Apple successfully deflected attention away from an engineering defect (play with a 4S and an old copper penny or a gold wedding band for REAL fun) by focusing on this issue, which is normal and happens to every radio. This is science -- it has to work this way.
    ಠ_ಠ
    제리

Similar Threads

  1. **32 GB Verizon Galaxy Nexus LTE plus Extras**
    By kxs783kms in forum Sold / Archived Marketplace Threads
    Replies: 2
    Last Post: 08-26-2012, 07:41 PM
  2. Google Nexus 7 and Wifi question
    By droidfroid in forum Google Nexus 7 Tablet (2012)
    Replies: 2
    Last Post: 07-05-2012, 11:45 PM
  3. Motorola Xoom WiFi 32 GB $250 OBO
    By rainman353 in forum Sold / Archived Marketplace Threads
    Replies: 7
    Last Post: 06-30-2012, 11:24 AM
  4. White 32 GB Samsung Galaxy 10.1 WiFi
    By gyroslice in forum Sold / Archived Marketplace Threads
    Replies: 8
    Last Post: 04-03-2012, 10:34 PM
  5. 32 gb Verizon galaxy nexus?
    By kevlars9 in forum Verizon Galaxy Nexus
    Replies: 5
    Last Post: 02-26-2012, 06:32 PM

Posting Permissions

B