Hi, I'm using a Nexus S I9020A with Cyanogenmod 9 v1.1 with the Google Apps v10 package. I have Android beam enabled, but have no one with another Nexus to try it with, but yesterday I tried it with my friends BlackBerry curve that has an NFC chip in it and the Blackberry worked to transfer smart tags to another blackberry of the same kind, but when I touched my Nexus to it, nothing happened.
Does Android Beam only work with other Android devices running ICS?
Also, I noticed the Tags app from Gingerbread is installed but I can't find it anywhere.
I think its for ambroid based only s there is no open standard for nfc yet every phone is having out now...
Sent from my Nexus S using xda premium
does it only ICS have Android Beam ...?
besides , i have not yet encountered any other phones with NFC ...
I had the same problems between 2 Nexus Ss. Saw the following somewhere else on XDA which cured it:
Go to Manage Apps, All, Nfc service.
Clear data and cache. Force stop.
Turn phone off and on
Related
Hello everybody,
I just want to give my opinion about my new Nexus S.
I started on android long ago on my HTC Hero. I liked this mobile a lot, but we waited so long to get our update to 2.1, so I used custom rom like everybody. But custom rom are never stable as the original one.
that's why, when I decided to change my mobile, I choose the nexus S. To be sure to always get the google update.
Even I don't like samsung so much compare with HTC, the update part was too important for me.
So I bought the Nexus S two weeks ago. I expected that the hardware and the software match perfectly together.
But now I discover several problem which make me very disapointed.
First, the volume level for call is really too low. I can not hear what people say if I'm in the street.
second point, I can not open the youtube application.
Third point, google sky map doesn't work well, as well as google street view. There is a problem with the gyroscope.
The Nexus S is the mobile 100% google. It's should be a reference for everybody. I can not accept these kind of problems. These 3 points works very well on my old HTC Hero...
I should not be oblige to instal a custom rom just to let my mobile work normally! This it's the minimum we can expect for a google phone of this generation!
Do a lot of people have these problems?
Thanks for your answer.
Sent from my Nexus S using XDA App
Im on stock youtube works for me so does maps and every other map the volume used to be loud but went low i agree on that
Sent from my Nexus S using XDA App
My incall volume is to low as well pisses me off no way to fix it yet either Google needs to step it up and all these other phone makers
Sent from my Nexus S using XDA App
I agree. Kinda disappointed. Still like my HTC Magic and works well with custom ROM. Can't get my YouTube running and the hardware design is not that great. Only thing that makes up for the hardware us pure Google.
Sent from my Nexus S using XDA App
Some ppl here don't Even know how To root. I myself know but those who updated OTA and aren't Techies are stuck... think Google should Seriously give us an ETA ... =\
Sent from my Nexus One using xda premium
The major problem of the i9020A is the capacitative search button firing on its own. They tried to fix it, but:
with GRK39C
wireless tether broke
search button bug still present
with GRK39F
wireless tether broke still (for me and others on AT&T). There are people on Bell/Rogers reporting it works again.
search button bug still present
The search button bug is present in low 3G areas and I can repeat the bug at will at a couple locations.
I'm fully aware of how to root/unlock flash ROMs, etc but I made a decision that this particular device would stay completely stock so I could have a frame of reference for my other phones.
Google didn't sell many Nexus phones and they are currently doing what they have done on several other projects in leave stuff broke while they attend to the next greatest thing (ICS & Honeycomb/tablets). As for a guess about when they fix this, perhaps Q1 2012 when the NS gets OTA Ice Cream Sandwich.
Telus 9020A user with rooted stock ota'ed to K39F and my tethering both USB and hotspot are fine. Never saw the search button bug myself.
Sent from my Nexus S using xda premium
slimdizzy said:
Telus 9020A user with rooted stock ota'ed to K39F and my tethering both USB and hotspot are fine. Never saw the search button bug myself.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
same here.
On Rogers had mine since it became available in April. Also never had the search problem and 39f working fine.
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.
I've been cruising on cyanogenmod 7.1 for about 2 years now, and since the auto store no longer reads OBD II codes for customers, I decided to purchase one of the $10 Bluetooth ELM 327 devices off ebay, and use the Tourque app to read the data from my car.
The app works great, but it only works if you have a notification pop up asking to pair with the device, and I've only been able to get BT to work with this device so far with a 4.2.2 ROM --> http://forum.xda-developers.com/showthread.php?t=2204963 (only JB one I've tried). The other ICS ROM's I've tried so far along with CM 7.1 just won't connect. Has anyone else found a good ROM that works, or a way to trigger a bluetooth notification?
Basically, I turn on Bluetooth in all the ROMs, it detects the device, I select the device, and it says "Paired but not Connected" If you long press or hit the gear symbol, the only option is to "unpair". Pairing with other phones works perfectly fine, but with this device the option/notification to connect never comes up.
Anyone know of any ROMS prior to Jellybean that work with similar BT devices? .. Dunno if there is a way to trigger a notification; I do like JB, but once everything I need is working, my #1 goal is then responsiveness.
Any ideas/insights/experiences are much appreciated.
Have you tried any Sense roms?
Well, as it turns out, after I did a complete wipe, and was trying cyanogenmod 7.2 out, I was able to connect..... in fact, I'm able to connect on good ole 7.1 as well, and mytouchUXv3... which I didn't want to uninstall- seemed to have a snappier ui. I have no idea why I was unable to connect yesterday, but on whatever ROM i've tried today, if I start bluetooth, then run the torque app, then go back to the bluetooth app with the torque app running, and select pair/unpair/pair/unpair, it connects pretty soon. *scratches head*
One reason I stick to cm 7.1 is that I've read of many users experiencing diminished battery life with cm 7.2
1LordAnubis said:
Well, as it turns out, after I did a complete wipe, and was trying cyanogenmod 7.2 out, I was able to connect..... in fact, I'm able to connect on good ole 7.1 as well, and mytouchUXv3... which I didn't want to uninstall- seemed to have a snappier ui. I have no idea why I was unable to connect yesterday, but on whatever ROM i've tried today, if I start bluetooth, then run the torque app, then go back to the bluetooth app with the torque app running, and select pair/unpair/pair/unpair, it connects pretty soon. *scratches head*
One reason I stick to cm 7.1 is that I've read of many users experiencing diminished battery life with cm 7.2
Click to expand...
Click to collapse
Yeah I've read the battery life thing too.
What do we lose if we stick to 7.1 instead of 7.2
Sent from my myTouch 4g using xda app-developers app
I've been using CM10.1 for the past year and have had sucess with my Bluetooth OBD II reader.
Here is the ROM I have been using. The camera is a bit slow on this ROM but other than that I love it:
http://forum.xda-developers.com/showthread.php?t=2204963
Just to confirm, it ALSO works well with Vipertouch 2.1.4.
Buddy of mine passed me his cheap ELM ODB II Bluetooth unit, (he could not connect to it, since he had some chinese S3 knockoff phone).. Worked perfectly first time.
Paired no problem, and connected using Torque Pro and read quite a few of the sensors on my honda without an issue.
Thanks to all the devs for keeping these older phones alive..
NFC appears to be broken on my new Nexus 5. Is anyone else experiencing the following:
If I turn NFC on in the settings (ticking the NFC box), the NFC setting greys out every 4 seconds, staying greyed for about half a second, as though the phone were repeatedly trying to turn on NFC but is failing.
NFC does not work at all and ignores tags and other NFC phones.
I am hoping this is a firmware glitch (baseband version M8974A-1.0.25.0.17, Build KRT16M) and not a hardware defect. Can anyone confirm whether they have this problem too?
familyhousing said:
NFC appears to be broken on my new Nexus 5. Is anyone else experiencing the following:
If I turn NFC on in the settings (ticking the NFC box), the NFC setting greys out every 4 seconds, staying greyed for about half a second, as though the phone were repeatedly trying to turn on NFC but is failing.
NFC does not work at all and ignores tags and other NFC phones.
I am hoping this is a firmware glitch (baseband version M8974A-1.0.25.0.17, Build KRT16M) and not a hardware defect. Can anyone confirm whether they have this problem too?
Click to expand...
Click to collapse
My NFC is working fine. The NFC box was already checked with a blue tick when I went to the menu, and then I successfully sent beams back and forth between my N5 and S3 (which is currently running CM 10.1).
My N5 baseband and build are exactly the same as yours.
I think its best to get a replacement. It seems like its defected for whatever reason.
Sent from my Galaxy Nexus using xda app-developers app
shencez said:
I think its best to get a replacement. It seems like its defected for whatever reason.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I've requested an RMA this morning. Google apparently have not heard of this problem so it would seem to be an isolated problem.