I am experiencing a very annoying problem with my Samsung Google Nexus S GT-i9023 (pearl white). Everything works fine except the NFC chip.
Every time, I try to turn on the NFC chip in the wireless menu, immediately the message "An error occurred" appears. So the NFC chip won`t turn on at all. No reboot, stock recovery (wipe internal storage etc.) could solve the issue.
Background information:
My Nexus S is 3 days old. It came out of the box with Android 2.3.3. I updated immediately after the first boot to 2.3.4 via OTA! I didn't check it with 2.3.3. Around the net are a lot of people experiencing the same(!) problem. No matter if it is a i9020 or a i9023. Also some people say, that it worked before with 2.3.3 and after updating to 2.3.4 NFC stopped working. I not able to verify this information.
Well meanwhile my Nexus S is at Samsung Germany service partner, called Bitronic Service Line. The guys called me some days ago, to inform me, that they don't know how to fix it. The placed an issue at Samsung Germany itself, so Bitronic is awaiting now reply from Samsung.
My question to xda-developers forum users:
Are you invovled in such a problem? Do you know a working fix? Probably sb. heard something about a defective production lot or maybe about udapting problems via OTA?
By the way, for more information, my and other Nexus S users story, can be read in the android forum. Just search via google for "Nexus S NFC error". It is issue nb. 13581. Sry but since I have only a few posts, the board rules does not allow me to post external links. Sry for that.
Attached a screenshot of the error msg.
Thx for information or any help.
Regards.
Same problem here. Sent my nexus s i9023 also to bitronic germany a week ago. Still waiting for a reply.
I tried alot ROM's (cyanogen, MIUI, nscolab etc.) and kernel's. Nothing helped. So I think this is a hardware problem.
According to a callback of Bitronic (Samsung Germany's contractual Service Partner), my problem could be identified as an hardware bug. They told me, that they replaced a specific part. Which exactly, I don't know.
I´ll get my phone back in around 2-3 days. Then I will post an final statement.
just got my nexus s back. everything is working properly again, so it was definitely a hw bug. From my side the problem is solved.
If someone is experiencing further problems with de- and activating the NFC chip, keep going on with reporting here.
Cool story bro.
Just kidding. Sending it out and getting it back in 2 days is pretty great turnaround. Sounds like quality service. Glad it got sorted.
Got my SNS back today. NFC is now working. Seems so that samsung has found the bug.
Related
Hi all!
Been all over the forum looking for a solution. From what I understand I think I have a faulty handset but it's just come back from from repairs (for other problems) with updated rom/radio. Seems a little strange as it was working before I sent it, now its not.... Same handset...
When I run Google maps and Waze they both see the GPS but it wont pick up any satellites...
Before you say it, i've tested this on the road, in a field .ect so it isnt the signal, tried setting it up manually in google maps, still no joy.
Am I going to have to be without my baby for another week?
Any advice would be welcome, thanks in advance
Hi mate...
I offer no helping hints.. but I got mine back from HTC HK for a shattered screen and had the same problem. I had to return it to HTC to fix, its been about 2-3 weeks and still no answer. They initially told me that its may be just the GPS or associated chip set wasn't plugged in properly... So they will fix it with out charge (incl. freight chargers)
So your not alone with this problem
Try gpstest free fom this page to just test your gps inpriciple excluding any other apps:
http://www.chartcross.co.uk/
Thank you
why_999 said:
Hi mate...
I offer no helping hints.. but I got mine back from HTC HK for a shattered screen and had the same problem. I had to return it to HTC to fix, its been about 2-3 weeks and still no answer. They initially told me that its may be just the GPS or associated chip set wasn't plugged in properly... So they will fix it with out charge (incl. freight chargers)
So your not alone with this problem
Click to expand...
Click to collapse
Thanks for the reply mate. Was beginning to think it was something i had done,
The main thing that baffled me was its the same even after a Hard reset and standard settings.
At least I know what I have to do. Cant believe I've got to send it off again..
Last time was for a faulty board, what next?
Back to the old Nokia 9500 then... Sigh...
Hello people. I searched for info on this issue, but nothing for the Captivate came up. Intermittently I'll wake my phone up and there will be a little circle with a line through it where there should be network info. Anything I try to do with the network pops up a "Not registered on network" (or something like that) message. Usually rebooting the phone will solve the problem, but last weekend after three reboots it was still doing it. I left my house and an hour later checked it and no circle/line icon. This happens every several days, so not a chronic problem yet. Still very annoying. Any solutions? Thanks.
Stock Captivate.
I would consider warranty return if it were me I havent seen or heard of this before your post. good luck.
I have a stock captivate and let's just say I am incredibly disappointed and annoyed with it and at&t in general I'm tired of all the run around and hold up concerning froyo, but this isn't the thread for that.
My phone has been glitchy since the get go. The newest is the issue with "not registered on network". It has happened off and on, but a couple days ago, after I had turned the phone off for the night and back on, the phone screen blanked out while the bottom touch panel stayed lit and everything became totally unresponsive. After several reboots by removing the battery, my screen finally came up again, but so did that little blue circle and line...voila..."not registered on network"
The guy in tech support from at&t tried to help me out. He stayed on the phone with me for over 2 hrs trying to correct the issue, but even after a factory wipe...nada. Lost all my apps, free and purchased... if we would have froyo like promised, all my apps would have been backed up...UGH...
This is actually my third captivate in as many months. My first phone bricked itself after 2 days. No one could ever figure out why. I am waiting on a replacement as we speak. Of course my "new" phone is being replaced with a refurbished one. I hate that considering my current phone was only 3 months old and didn't have a mark on it, but what can I do?
because you don't mention if you're running stock or a custom ROM, I'm going to assume custom ROM. and if you are, then you must have not searched very hard because this is already a semi-known issue: http://forum.xda-developers.com/showthread.php?t=864903
it happens to me ANY time I use a modem newer than JK3... when I use UGJK3 or older, no problems... but if I use UGJK4 or newer, random "no service" on the lock screen with the "circle with a line through it" in the notification bar. as of right now (I believe) there's no known issue why some modems fail on only some hardware. I have a batch 1006 and it works fine right up until the UGJK3 modem, while some people seem to have absolutely no issues with modems (even the newest ones like UGJL2 and TLJL3). basically, if you're running a JPY based ROM, flash JK3 and see if that helps... if that doesn't, go back to a stock captivate ROM of some sort with a stock modem so you don't have these issues (never happened to be me on JI6/JJ4)
Try changing ur SIM card. That could solve the issue.
In my case, it is original stock all the way. The SIM card is fine because I switched it into two different at&t phones and had no issues at all. Right now my Captivate is a gloried camera and MP3 player.
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
NvigR8 said:
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Happened to me a year or so ago on a different phone. Turned out they were upgrading the tower closest to me with new hardware and were shutting it down intermittently to work on it.
Hello all,
Just bought a the 7.0 Plus tonight and am already having some issues. Out of the box, I was having problems with it dropping wifi connection. I was in range and it showed signal, but the only way to get internet connection with it was to cycle the wifi on to off. Its probably happened 4 to 5 times already in my first night.
Anyways, I used it until the battery was near dead and then plugged in to charge. Now the market place will not load. I get an error saying "No Connection". Cycled it off then back on, nothing. Deleted my google account thinking maybe re-sinc the account and I'll get it back. Now, I can't even get the google account back on it. It only says an error something along the lines of failed to establish a connection. Facebook app, nothing. Picasa web albums, nothing. More or less all the apps that need a connection, nothing. The only exception to this is I can go all over the internet all I want. I am getting a "Security Warning" saying "There are problems with the security certificate for this site". I get this on more or less every site I visit.
I am fairly baffled. Rooted Evo's, GSII's, ect. This is my first tablet though. Only thing search turned up was off a Thrive tablet someone did a full factory reset and got it all back. I'm thinking that might work for me, but its not even a day old and for the price these 7.0 Plus' cost it shouldn't be doing this. Should I be looking to exchange it for another? Maybe I just got a bad one. I'm close to just swapping for an Acer A100. I wanted the 7.0 Plus for the newer hardware because I tend to keep them for a while, but dang this is not working well. Oh, its fairly laggy too. I mean, my original 2 year old Evo on CM7 with a Tiamat kernal isn't this laggy. Its actually smooth, lol.
Sorry for the book I just wrote too. Just fairly upset at this point and looking for help.
Download samsung kies on a pc and update the tab
I tried that, but it didn't help. I forgot to mention I have Kies installed an updated everything when I first started it up.
I returned it. Not willing to deal with features that don't work as well as they should, wifi dropping, and issues out of the box. I'll probably just pick up an A100, but who knows. I also just got a Galaxy Nexus so that'll keep me busy for a bit.
Hello,
I realize this thread is almost a year old, but has anyone else had this connectivity issue with their Galaxy Tab 7.0 Plus? I have the Wifi Only tablet (GT-P6210) and this is the second time for me to have an issue similar to what Bill3753 posted above. The first time this occurred I did a factory reset and the problem was resolved. I really don't want to do that again and mess with having to reload all my documents and downloading all of my apps again.
So, after almost a year does anyone know a fix for this issue? Or can someone share a link to the right info?
Thanks in advance!
BPS1254 said:
Hello,
I realize this thread is almost a year old, but has anyone else had this connectivity issue with their Galaxy Tab 7.0 Plus? I have the Wifi Only tablet (GT-P6210) and this is the second time for me to have an issue similar to what Bill3753 posted above. The first time this occurred I did a factory reset and the problem was resolved. I really don't want to do that again and mess with having to reload all my documents and downloading all of my apps again.
So, after almost a year does anyone know a fix for this issue? Or can someone share a link to the right info?
Thanks in advance!
Click to expand...
Click to collapse
Ok my problem is fixed now! The problem was with my Google account. I removed it from the tablet and then tried to add the account again. I kept getting an error that said "can not establish reliable connection" and after doing a search for the 50th time I came across a post that said make sure date and time are correct. I changed my date and time, then tried to log in and it worked that time! Now my Play store is connected fine and the browser doesn't constantly give a certificate warning message.
Hope this saves someone else a headache.
Hello guys! I have owned the OnePlus for a month now and I am more than happy with it! A couple weeks ago I ordered a second one for a friend but this one is acting up from the moment it was pulled out of the box :crying:
Since I was unable to fix it myself, I am RMAing the device but while I'm waiting for OnePlus support I wanted to post here as well for some feedback (maybe I'm missing something) and in order to update you with the process. So this is my ticket's text, it pretty much says everything in it.
The device reboots itself at random, I was unable to pinpoint the problem.
Completely randomly the device freezes up and automatically reboots after 5 seconds. At times it may work for up to a couple or more hours before it does this, other times it may reboot twice in 10 minutes...
The first time this happened was actually out of the box, before I even completed the setup wizard! At the time I thought it was an Android hickup since I've since random software crashes before. Then I updated to XNPH33R but it happened once more before I unlocked the bootloader and rooted the phone (notice that I am an experienced android user, I even have another OnePlus One that works perfectly fine and had done this before).
It kept on doing this so I googled and found a couple of similar cases online. However mine seems different as it happens completely randomly (wifi on/off, airplane on/off, various battery levels), nothing seems to prevent it. As I was rooted, I have kept some "/proc/last_kmsg" copies from various restarts but I was unable to understand something out of them. I also waited for a reboot with a logcat running in the background so I have a pair of a logcat and a last_kmsg that you might find useful.
To isolate the problem as a hardware fault, I tried the following but nothing helped, it is still acting up exactly the same:
-Factory reset, no luck
-Run a stability test (https://play.google.com/store/apps/details?id=com.into.stability), no errors
-Installed TWRP (custom recovery) and cloned my other OnePlus on it by means of a nandroid backup, it kept on restarting
-Factory reflashed EVERYTHING through fastboot using the "cm-11.0-XNPH25R-bacon-signed-fastboot.zip" I had downloaded from CM's website in case something was not correctly flashed in the factory, but it reboot on me again.
Finally, I want to notice the fact (and this seems very strange to me) that it usually happens while the device is not stressed at all! Every time it happened I was doing very light and simple stuff, like chatting or moving around launcher icons or checking an application's settings. During the above mentioned stability test, it run for 10-20 minutes with constant load on the CPU and RAM with no problem, I then stopped the test manually, and the phone crashed a couple of minutes later when I was browsing through the app drawer! I also tried a game (Riptide) for a while and it run fine. This means it's not a temperature problem either.
Taking all the above into consideration, I am positive that this is a hardware issue I am unable to fix myself and I would like to request a replacement unit. I must mention I am currently in Greece and I want to know if you can send me the replacement directly to Greece, as it's not a new buy so you shouldn't be facing any law-related problems, to spare me the hassle and cost of sending it to my German address and forwarding it to Greece.
I have attached a ZIP archive of the various "last_kmsg" copies I have kept and a second one containing a "last_kmsg" AND a logcat of the same freeze/reboot, hoping they can help you in troubleshooting the problem. I am available for any other needed information.
Thank you for your support, please do not forget to answer my question about shipping to Greece.
Regards,
Spyros
Click to expand...
Click to collapse
The above ticket was submitted as of 2014-09-18 00:30 UTC
Since I have zero experience with the linux kernel, is anyone able to get something out of the attached logs?
Thorough...
Thorough, as always...
I've got same problem with my one. But for me it usually happens when my battery is fully charged. Wanted to figure out the reason too, so it would be nice if you'll keep writing about the situation. Good luck!
I will update here with any news but I suggest you open an RMA ticket with OnePlus as most probably this is not going to solve itself and it will take them some time to respond to you anyway.
MasterMind33 said:
I will update here with any news but I suggest you open an RMA ticket with OnePlus as most probably this is not going to solve itself and it will take them some time to respond to you anyway.
Click to expand...
Click to collapse
I'm using Chinese version of OPO and I'm absolutely sure that they're not gonna help me
ThoughtfulDroid said:
I'm using Chinese version of OPO and I'm absolutely sure that they're not gonna help me
Click to expand...
Click to collapse
That's bad
Tech support replied today. Apparently, they did not get the attachments and I was asked to resend them, but it was pretty impressive that I got a reply next day after everything I have read about them being so slow to react.
On a side note, I got a new last_kmsg that shows an "AHB bus error" coming from the graphics driver right before the disaster and noticed on a previous one an error coming from "qup_i2c" so it's probablt a faulty processor... (I'll include the log in the OP, it's #9)
Was anyone able to solve problem with reboot loop?
I am having the same thing only that my log is this:
Code:
38.142516] SMSM: Modem SMSM state changed to SMSM_RESET. [ 38.142819]
Fatal error on the modem. [ 38.142992] modem subsystem failure reason: :Excep :0:Exception detected. [ 38.143159] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED. [ 38.143312] Notify: start reset
51.374367] Kernel panic - not syncing: [ed777000]: Timed out waiting for error ready: modem! [ 51.374852] CPU1: stopping
Update: The tech support guy replied the next day saying he escalated my request. However, after all these days (we are close to 2 weeks now) I got no response. I even sent a message asking for a reply on the 7 day mark but was ignored...
Anybody else that has already dealt with their service center? How long did they take to grant you a replacement?
Sent from my OnePlus One
Here comes yet another update. I am quite disappointed by their service. I was forced to open a PayPal dispute for the phone since I got no answer, a nerve-breaking phone and the dispute period was ending. It's been a couple of days now since I did it and still no response
Ok, just an update for future reference.
The problem was resolved December 13, 2014 (they sent out a new device).
I absolutely hated the experience of dealing with their support. That said this is still a great phone and having bought or supplied invites to friends for more than 10 more devices all of which worked flawlessly, I still recommend this as good buy.
Hope their support has gotten better by now that they don't have such a long queue.
Sent from my OnePlus One
Hello,
My step history for previous days does not show on the watch. I can only see the bars in the graph, but the numbers are 0. Current day is shown ok.
S Health on the phone is fine.
Tried resetting the watch and reinstalling S Health - doesn't help. Is this a known issue?
Hai,
I have the same problem. Resetting does not help.
How can solve this problem?
Same problem too since 2 days. I saw other people having the same problem on some other forums but no clue on how to fix this issue.
I spoke to Samsung support. They told me that this is how it's supposed to be, and steps history will only be visible in S Health. I call this bullsh*t...
dadonev said:
I spoke to Samsung support. They told me that this is how it's supposed to be, and steps history will only be visible in S Health. I call this bullsh*t...
Click to expand...
Click to collapse
It is BS. I'm currently looking at history on my S2 going back to 3/12. Nearly 3 weeks of history.
Why does it only go back to 3/12? Because that's the day all previous history was erased somehow. No idea how, but on 3/12 I was going through the same motions as the OP and other posters here: What happened to my step history? It's all still there on the S6. I tried resetting too, no dice.
It's a bug, folks. And Samsung is simply unwilling to invest ANY money in fixing bugs on the S2. They're working on the S3.
Guess I'm lucky as mine shows everything back to the day I bought it. Wonder what is different? I have the 3g version on Verizon.
Sent from my SM-G930V using XDA Premium HD app
Firmware probably. I'm still on XXU2BOKK which was issued in December (no airplane mode etc.). Wonder when the update will hit me as well...
I have the problem with R720 model on XXU2CPB7, so it must not be related to the firmware version. My feeling is that it's related to recent S-Health update I got last week-end.
i had the same problem a few days ago, tried everything even factory resets. today with the new firmware update it is fixed. (R720xxu2cpc5)