Related
Hello everyone:
I don't set my expectations too high. I know that this is a new phone, and it is not without it's bugs, but it is an awesome phone and from reading others who were having issues, I wanted to get a Nexus S working right for me!
I purchased my first Nexus S at a local Best Buy.
Everything about the phone was fine, the battery life seemed good, it ran quickly, did not notice any lag or any other major problems. However, I did begin to notice the back-button being unresponsive, as many others have stated experiencing. From reading threads on XDA, the jury is still out on whether this is a software or hardware issue, but that some people were able to get a phone without the issue by returning it for a replacement.
So I did...
I exchanged for my second Nexus S at a local Best Buy.
This one was kind of odd. Took a little while the for the 'important system updates' notice to come up, so I had already synced with my gmail and had also manually updated google maps and a few other apps.
When I finally did install the system update and the phone booted, I got a systemcore process FC error off the bat. Not good news. Later on, all seemed well, but I noticed a lot of lag with using the GB keyboard (unresponsive at times), and also having difficulty with the end-call button to end a call in progress (again, unresponsive so I had to press it a bunch of times before it would respond). Also, the battery life did not seem to be nearly as good as the first Nexus S.
So... I turned it back to Best Buy, but they did not have another replacement. So I turned it in for a refund.
I called Best Buy toll-free number, told them about the trouble that I was having, and they waived the overnight shipping fee, took my order for a new Nexus S, and I got it via UPS the next day (just at the 24 hour mark)
With this phone, I booted the phone and chose skip to login/create a gmail account. Phone loaded up completely, and I was just signing into my gmail account when I got the 'important system updates' message.
I updated immediately. Everything went smoothly.
I have not noticed any problems so far. The phone runs smoothly. It had no FC upon first boot after the system update. The back button works as it should. I don't notice any lag with the keyboard. I pulled up engadget.com full site and did not notice any lag out of the norm, apart from it being slow to load as I'm working with the crappy Edge network here (who cares if there are 4G phones out when my area doesn't even have 3G yet and that is where I am mostly). I have also tested the ringtones. I moved some music to my SD Card. I downloaded/installed Ringdroid. I created a ringtone. I set the ringtone. I have rebooted my phone three times and my ringtone still works. I mounted and unmounted my SD card (even moved some files to it), and I still have my ringtone.
So, what was it? Was it three times the charm? Was it there was a bad batch at the local Best Buy? Was it that because of the volume of Best Buy over phone and online sales, you'll get a newer and better Nexus S going through that route? Was it because I installed the system update before doing anything else, including syncing my gmail? I'm not sure...
But I do know that I love this phone, and *knock on wood* it continues to work the way that it should, I'll be happy with it for a long time to come.
My advice for those who are experiencing the issues that I had with my first two Nexus S to try try again. I know it's disappointing that a customer would have to do that in the first place as it is time consuming and stressful, but in the end, there might be a happy ending with you and your Nexus S.
Glad everything is working out for ya. Luckily my first nexus s has been great from day one.
Sent from my Nexus S using Tapatalk
I have my second phone and it feels like the screen is less sensitive as on my first one. Unfortunately I cannot say if this is a problem with 2.3.1 because my first phone never got the 2.3.1 update and got stuck with 2.3. I have the feeling that 2.3 was much faster and less laggy than 2.3.1. I probably will return the phone again to see if this is a phone problem or if this was introduced with 2.3.1.
Does your front camera worK?
cyc1120 said:
Does your front camera worK?
Click to expand...
Click to collapse
Yours does not?
cyc1120 said:
Does your front camera worK?
Click to expand...
Click to collapse
Just took a picture... it works. But I haven't tried video calling with Tango yet
Sent from my Nexus S using XDA App
Camera works but weird thing is it does not allow zoom...it does work on tango though....
Sent from my Nexus S using XDA App
ankit.subs said:
Camera works but weird thing is it does not allow zoom...it does work on tango though....
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There is no zoom yet for gingerbread stock camera app.
mr mystery said:
Yours does not?
Click to expand...
Click to collapse
it force closes if i use it in the default app.
it's just black if I use it in Tango.
I'm from Canada and bought the phone off someone from craigslist
Just got my G2x yesterday, activated it to T-Mo and I haven't yet rooted/ROM'd (mainly b/c I want to see how the GB stock build will be) and I have the old Android Market (from 6+ months ago) app and it's not updating to the current version. I have rebooted the phone, FC'd the Market, everything short of doing an annoying factory reset and starting over after one day of use - still no new Market.
Anyone else having this problem? Any fixes?
Thanks in advance!
Give it a day at least mine usually automatically updates itself after a while once I'm logged in my account and connected to servers
Sent from my LG-P999 using XDA App
Are you synced? Try logging to to gtalk.
While the G2x is awaiting for patch, went out & bought the Sensation yesterday. So far everything is working as it should except for the B/T. I can pair it and use it on a 06 BMW 750i, but it simply gets stuck in downloading phone book, however, the sensation pairs well with a 11 Lexus and the phonebook gets transferred.
Just wanted to see if anyone has similar issue. The 06 BMW paired well with my G2 and G2x and the phonebook transfer was never an issue.
sclui56 said:
While the G2x is awaiting for patch, went out & bought the Sensation yesterday. So far everything is working as it should except for the B/T. I can pair it and use it on a 06 BMW 750i, but it simply gets stuck in downloading phone book, however, the sensation pairs well with a 11 Lexus and the phonebook gets transferred.
Just wanted to see if anyone has similar issue. The 06 BMW paired well with my G2 and G2x and the phonebook transfer was never an issue.
Click to expand...
Click to collapse
With my 2010 3series it is working...
Where have you stored your contacts in?
- Phone
- Google Sync
- mwie -
Good to hear it works on the 2010 3. I store my contacts under Google sync. I thought about the location as well, but it it were looking for "phone", then I would expect the download process to return zero entry rather than stalling.
I had the same issue with my Mustang and Sync. I was staring at it for like 5 minutes when my Nexus One took like 10 seconds to download. I finally looked at my phone and noticed I had to confirm it was OK to let my car access it. Is that maybe what's in the way?
Kitinas said:
I had the same issue with my Mustang and Sync. I was staring at it for like 5 minutes when my Nexus One took like 10 seconds to download. I finally looked at my phone and noticed I had to confirm it was OK to let my car access it. Is that maybe what's in the way?
Click to expand...
Click to collapse
OK, that may be the case, will check when I leave work later. Thanks!
Kitinas said:
I had the same issue with my Mustang and Sync. I was staring at it for like 5 minutes when my Nexus One took like 10 seconds to download. I finally looked at my phone and noticed I had to confirm it was OK to let my car access it. Is that maybe what's in the way?
Click to expand...
Click to collapse
No such luck with me, there was no pop-up on the Sensation requesting access. Unpaired & repaired multiple times and no go, could be the issue w/ the i-Drive.
Thanks for the suggestion though.
I'm having the same problem in my '09 135i. It can download the phonebook for all my old phones, but not for my Sensation.
Apparently I have been having trouble since this morning with connecting to my google account. It has been saying that I can't sign into my gmail account. I am on Paranoid Android build on Sep 2. It was working before, I tried a reboot but nothing has worked. Should I just update Paranoid Android or is there something else I can do?
I'm on CM10 and I have this issue, too. Is this across most/all devices or only a select few?
I'm getting the same error on synergy r73, my google services work fine but its telling me that i'm having issues signing in. Even tried changing passwords to try and trick it into thinking it was syncing fine but still pops up.
Yes, same here
It seems its a global thing, I too get the error on my Galaxy SII with CM10
Might be a bad route somewhere, because I've been logged in all day from home and then from my phone.
EDIT: Seeing later posts, I don't have or use Google Now - this is a stock, unrooted phone.
- ooofest
I just started seeing the same thing on my phone as well. GSM Galaxy Nexus.
Good to know its not just my phone. Wish i had known that before i changed my password =/
im not getting it on my GS3... maybe only some people are?
Ive been having this problem too. Im running stock rooted 66. All my normal Google apps work fine and my options in account sync across the board. The issue, with my device at least seems to be the google "now" search i flashed to my phone. Trying to get to that and see my cards initiates that error.
Did a little googling and the gnex users are having problems too. It seems like its connected to the google maps update. Google said they were changing some stuff to have sync across devices like when you search on your comp, the search history will show up on your phone. Im guessing google search card trying to pull maps is the issue for me? Can anyone confirm if you also have google now and having these issues because of it?
I wonder what is causing it? Especially if it is happening on multiple devices.
jeffyh said:
Ive been having this problem too. Im running stock rooted 66. All my normal Google apps work fine and my options in account sync across the board. The issue, with my device at least seems to be the google "now" search i flashed to my phone. Trying to get to that and see my cards initiates that error.
Click to expand...
Click to collapse
i dont have google now... could that be the issue?
I'm getting it too, everything syncs fine except for Google Now
Sent from my SCH-I535 using xda premium
Edit: Running CM10
Just started for me also paranoid 2.13
Sent from my SCH-I535 using xda premium
I can confirm google now on synergy r73 is now broken.
I'm from the Sprint Galaxy S3 and we are getting this to across all roms.
Sent from my SPH-L710 using xda premium
JohnnyEpic said:
I'm from the Sprint Galaxy S3 and we are getting this to across all roms.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I went ahead and hinted engadget about this thread. we will see if they have any more info on it.
is around the world and also around a lot of devices so calm down, if dont believe read this http://forum.xda-developers.com/showthread.php?t=1895790
Same issue here on my gnex
Sent from my Galaxy Nexus
Same issue here. Gnex, cm10. Been driving me crazy.
Sent from my Gnex
Most likely a Google Now issue. Go to settings, apps, all, open "Google Account Manager" and disable notifications. Its a temp solution till Google fixes
Sent from my billion dollar GalaxiPhone S3.
Hello Everybody
I am unable to use Google Chrome browser in my mobile phone.
I heard that the blank page issue in Google Chrome only dogged the nVidia Tegra based devices.
But even i am facing the very same issue and the work around mentioned where not useful.
I had to kill the application and re-open it to use it.
I can't use more than one tab in Google Chrome.
I have upgraded my mobile phone to a powerful HTC One X from Google Nexus S to use Google Chrome too.
As Google Chrome functioned very slowly in Google Nexus S.
But now Google Chrome in my HTC One X is unusable.
Can anybody suggestion solutions ?
I will explain my problem in depth now.
1 --> Open Google Chrome
2 --> Visit www.slashdot.org or any website
3 --> Open new tab and visit altavista.com or any website
4 --> Click the tab number button and switch to first tab.
Expected behavior
First tab should be loaded now.
But instead of that, first tab would reload into a blank tab.
Then i can switch to second tab either.
Even if i close all the tab, i won't be able to visit any sites in new tab there after.
So, i have quit Google Chrome by pressing the running application button.
Running 2.20 version of stock software.
This issue has been reported to Google and is known, star these issues so Google will work on them.
http://code.google.com/p/chromium/issues/detail?id=130607
http://code.google.com/p/chromium/issues/detail?id=113204
Also, if you look at the reviews of the Google Chrome reviews on the Play store written by HTC One X users you will see many people are having the issue.
I'm having the issue on a stock One XL 2.20, I've simply gone back to using the stock HTC browser for now.
As above, I have noticed this behavior as well with Evita on stock ROM.
Here are some more details :
The blank tab appears to indicate a crash in Chrome. Once the blank tab appears, you cannot close tabs or close Chrome without the application manager.
How I avoid the issue:
Always close all tabs before leaving Chrome to use other apps.
Use ES Task manager to clear all cache before starting new Chrome session. I do not suggest using task manager for any other purpose.
The issue appears to be a memory issue. If I forget to clear cache and Chrome crashes, the only way to get Chrome operational again is to restart my Evita.
Hope this helps.
Sent from my HTC One X using Tapatalk 2
Same problem here, just popped up today for the first time though.
I've had this issue with Google Chrome on my stock AT&T One XL for at least 2 or 3 months. I got sick of it very quickly and switched back to the HTC browser. I still use Chrome at least once a day or so but it crashes too often to be my main browser now.
you would think chrome browser would be the BEST for our Google phone by now, like it but thats the reason why i stack on stock browser too
I experienced the Chrome issue on my AT&T HTC One X with the 2.20 ROM since day 1. I rooted the phone and unlocked it, then installed CyanogenMod 10, and the problem seems to be fixed.
Zoide_ said:
I experienced the Chrome issue on my AT&T HTC One X with the 2.20 ROM since day 1. I rooted the phone and unlocked it, then installed CyanogenMod 10, and the problem seems to be fixed.
Click to expand...
Click to collapse
Running CleanROM now, so we'll see if the issue persists...
Sent from my HTC One X using Tapatalk 2
WookieFan said:
Running CleanROM now, so we'll see if the issue persists...
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
WAs the issue fixed on cleanROM? i recently rooted and went to cleanROM and the chrome issues have been bothering me from day one but havent' tried it yet since I rooted.
Hello Everybody
Thanks to everybody for sharing their thoughts.
I am not interested in rooting / modding my mobile phone as of now.
Even though i am not new to this, i just find it too cumbersome and provides less incentive.
I thought the issue in question happens only because of nVidia Tegra Drivers.
Experiencing the same issue even in Qualcomm Snapdragon S4 based mobile phone, frustrates me.
I am not sure whom to blame for this.
It would have been great if HTC put a work around for the Google Chrome's incompatibility issue in it's flagship mobile phone.
I hope Samsung Galaxy S3 users would happily be using Google Chrome in their large screen mobile phone.
The issue is still piggy back in elavate Jelly bean build is unacceptable.
style2burn said:
WAs the issue fixed on cleanROM? i recently rooted and went to cleanROM and the chrome issues have been bothering me from day one but havent' tried it yet since I rooted.
Click to expand...
Click to collapse
I have only been running CR 4.5 for about 36 hours, but it looks good so far. I had five tabs open last night, left browsing for a while and all tabs refreshed properly. I'll check in again in a few days.
Sent from my Nexus 7 using Tapatalk 2
WookieFan said:
I have only been running CR 4.5 for about 36 hours, but it looks good so far. I had five tabs open last night, left browsing for a while and all tabs refreshed properly. I'll check in again in a few days.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The browser works great on cleanROM EXCEPT for chrome has horrible horrible battery drain. Even with "scroll tilting" off, it still uses 10+%. I suspect because its constantly refreshing and syncing with the desktop..which is a shame because its what I WANT it to do.
Also, makes my HTC one x very warm, i haven't had that issue since I first got it, and disabled GPS
phishie said:
This issue has been reported to Google and is known, star these issues so Google will work on them.
http://code.google.com/p/chromium/issues/detail?id=130607
http://code.google.com/p/chromium/issues/detail?id=113204
Also, if you look at the reviews of the Google Chrome reviews on the Play store written by HTC One X users you will see many people are having the issue.
I'm having the issue on a stock One XL 2.20, I've simply gone back to using the stock HTC browser for now.
Click to expand...
Click to collapse
If this bug is caused because of Tegra driver issue, then why this issue occurs in our Snapdragon based HTC One X?