Database Info

Nexus S NFC activation error (An error occurred)

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.

Samsung Galaxy S3 acting possessed

Lack of a better subject description the only thing I can describe it as is possessed. I've never had this problem before. Searched various different keywords and couldn't find anything. So if this is a repost then I apologize.
I have a Samsung Galaxy S3 from Verizon white 32gb. Never been rooted. Around the time Verizon pushed out the last update for the phone it's been acting strange since the update and it's progressively gotten worse. It's almost made purchases for me while I'm browsing google play it'll randomly press areas and randomly click buy at times. Or I'm trying to text someone and it'll either type something on it's own or start trying to delete/lock/resend, etc messages. It starts up s voice randomly too.
So basically it's like having a set of ghost fingers/hand trying to control my phone while I'm trying to control it and the ghost is winning and I'd rapidly hit the home button to exit out of whatever I was trying to do. If the screen is on and unlocked it'll do the same thing even if I'm not touching it but this is maybe 1 out of 5 times compared to the while I'm trying to actively use my phone it'll be 1 out of 2.
Temporary fixes have been to just restart the phone and at first it would only occur every couple days and then once a day and now every few hours to every few minutes. Anyone have any suggestions on what I can do? Any tips would be greatly appreciated. Thanks!

All you have available right now is factory data reset or refurb. If don't fix reflash the latest available stock software via Odin or root and unlock it and flash anything. Can even root stock and have access to better apps.

Try a factory reset if you haven't.
Sent from my SCH-I535 using xda premium

I have now tried a factory reset and while it took longer than just a few minutes to go all psychotic on me it still happened. Thanks for the tips! Any other suggestions? refurb is the last option I want to take I've received too many defective refurb phones and I don't think I can deal with anymore. I can try root I suppose but if there's any other suggestions I should try prior I'm open!
Thank you thank you!

If i were in your position I would try to Odin back to the stock rom you had before the update. There is a sticky in the development section that tell you how to do that and much more
Sent by one of my many Anthromorphic Personifications

elayn said:
I have now tried a factory reset and while it took longer than just a few minutes to go all psychotic on me it still happened. Thanks for the tips! Any other suggestions? refurb is the last option I want to take I've received too many defective refurb phones and I don't think I can deal with anymore. I can try root I suppose but if there's any other suggestions I should try prior I'm open!
Thank you thank you!
Click to expand...
Click to collapse
It sounds defective. I'd take it back.

What you are describing happened to my Droid Incredible a few times: it appeared that someone else was creating random tap events on my phone. Turned out to be a slightly dirty and/or stuck optical trackball - once that was cleaned (easy), everything was back to normal.
Now, the Galaxy S III does not have a trackball. I don't see a direct correlation with my Incredible, but the symptoms you describe are oddly similar: perhaps try cleaning your various pushable keys, just in case?
Might install and run Symantec Antivirus just for a final check, then call Verizon Support if it's still happening and perhaps see what they can offer.
- ooofest

Replace your device. The touchscreen encoder is bad. If your screen is clean, never got wet, and is pressing random areas - and a factory reset or Odin doesn't work - this is most likely the case. You could try to convince them to give you a new one at the store by telling them you don't want to wait or something.
Also download the app multitouch visualizer and run it when it's flaking out. You will be able to see the "screen press" activity.

adoublearonn said:
Replace your device. The touchscreen encoder is bad. If your screen is clean, never got wet, and is pressing random areas - and a factory reset or Odin doesn't work - this is most likely the case. You could try to convince them to give you a new one at the store by telling them you don't want to wait or something.
Also download the app multitouch visualizer and run it when it's flaking out. You will be able to see the "screen press" activity.
Click to expand...
Click to collapse
Because the device is so new you have a very good chance of getting a new replacement. I had something happen to my GNEX and they replaced it with a new phone no refurb.

Thank you all very much for your tips and advice! I stopped by the Verizon store today. Twice actually. It was a no go. First off they won't replace my phone with anything but a refurb (which is standard policy anyway) but the second part which is really irritating is that the phone was driving me insane till I went into the verizon store while waiting for a tech it kept acting odd then when the tech got my phone it functioned correctly. So since they couldn't replicate the problem they said they can't offer me a replacement. As soon as I got into the car it started happening again I ran into the verizon store and they said I had to wait for a tech again so I put my name in and waited had a different tech and of course as soon as he tested the phone it wasn't acting odd anymore so once again couldn't replicate.
Maybe my phone really is possessed.. but then again it's been my luck with past phones as well if they have issues they refuse to happen in store so I got my replacements via 611 tech support. So I called 611 and they said they never heard of the issue and that I should wait for update.

elayn said:
Thank you all very much for your tips and advice! I stopped by the Verizon store today. Twice actually. It was a no go. First off they won't replace my phone with anything but a refurb (which is standard policy anyway) but the second part which is really irritating is that the phone was driving me insane till I went into the verizon store while waiting for a tech it kept acting odd then when the tech got my phone it functioned correctly. So since they couldn't replicate the problem they said they can't offer me a replacement. As soon as I got into the car it started happening again I ran into the verizon store and they said I had to wait for a tech again so I put my name in and waited had a different tech and of course as soon as he tested the phone it wasn't acting odd anymore so once again couldn't replicate.
Maybe my phone really is possessed.. but then again it's been my luck with past phones as well if they have issues they refuse to happen in store so I got my replacements via 611 tech support. So I called 611 and they said they never heard of the issue and that I should wait for update.
Click to expand...
Click to collapse
Or Odin stock firmware instead of waiting. Can Odin without root.

prdog1 said:
Or Odin stock firmware instead of waiting. Can Odin without root.
Click to expand...
Click to collapse
I'll give that a try tomorrow morning and hope it works. I'll check in either way. Thanks!

Take a look at this, and look into this virus some more:
blog.lookout.com/blog/2010/12/29/geinimi_trojan/
I did some research and someone said those are the symptoms of the virus...
Sent from my SCH-I535 using xda app-developers app

It's Verizon, some tech there is having fun with the remote capabilities of the new OTA.

Alrighty, took longer than expected but I did manage to do Odin stock firmware. It fixed the problem or so I thought for 48 hours but then it returned. Now a new problem has come up and the battery is draining at alarming speeds.. I will have phone at 80% when I go to sleep and when I wake up 3 hours later the battery is completely dead. No new apps, nothing draining in the background. I'm at a loss. Anyone have any other advice? Or are my only options now to throw the phone out the window or try to root it.

elayn said:
Alrighty, took longer than expected but I did manage to do Odin stock firmware. It fixed the problem or so I thought for 48 hours but then it returned. Now a new problem has come up and the battery is draining at alarming speeds.. I will have phone at 80% when I go to sleep and when I wake up 3 hours later the battery is completely dead. No new apps, nothing draining in the background. I'm at a loss. Anyone have any other advice? Or are my only options now to throw the phone out the window or try to root it.
Click to expand...
Click to collapse
You wrote in a previous post that you went into the Verizon store... don't do that, ever... just call them.. tell them what it's doing and that you have tried a factory reset. They will overnight you a new/refurbished phone.
I had problems with mine as well and after fighting with the tool they call a manager I called 611 from the parking lot and after the hold time I had tech support on the phone and had a new replacement on the way 5 minutes later..
Just my 2 cents.

BiasedThunder said:
You wrote in a previous post that you went into the Verizon store... don't do that, ever... just call them.. tell them what it's doing and that you have tried a factory reset. They will overnight you a new/refurbished phone.
I had problems with mine as well and after fighting with the tool they call a manager I called 611 from the parking lot and after the hold time I had tech support on the phone and had a new replacement on the way 5 minutes later..
Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the tip but if you read through the whole post. I did default to calling 611 like I usually do and they wouldn't do anything about it. Yes, I did tell em I did the factory reset. It's not the first time I had a phone replaced through 611 I've gone through maybe 10+ replacements on one of my past phones because they kept sending me a defective one over and over again. I did call 611 again since you suggested it but I was told the same exact thing as last time.

I had this happen a few times with my phone before the update verizon pushed (stock, rooted). I would end up pulling the battery to get it to stop. Hasn't happened to me in a while though. Now i'm running JellyWiz RLS12

[Q] Moto G rebooting

My wifes Moto G occaisionally crashes and reboots. It hasnt happened very often but I would like to know if it is happening to anyone else and if they know the cause? Maybe it's a bug that will be sorted with a future software upgrade?

The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.

vrsk said:
The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.
Click to expand...
Click to collapse
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.

ahardie said:
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.
Click to expand...
Click to collapse
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
I'll report with the results later.

vrsk said:
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
Click to expand...
Click to collapse
That must be really annoying. Luckily ours isn't that bad.
vrsk said:
I'll report with the results later.
Click to expand...
Click to collapse
Cheers.

Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....

llyenn said:
Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....
Click to expand...
Click to collapse
So far I've had a single instant reboot in the camera app. Hope it doesn't get worse.

The phone is still rebooting sometimes. Is there any way I can check why it is happening like something that will create an error log? Or does anyone have any tips for stopping it happening? It is a very minor nuisance at the moment but I'm afraid it might get worse. Especially if it is a problem with the hardware rather than the software.

I have a UK moto g and it hasn't rebooted on me yet the past week I have had it
Sent from my XT1032 using xda app-developers app

I've got the International 8 GB version from Koodo and it hasn't rebooted since I started using it full time on Dec 28. It remains powered up 24/7.

Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.

I have same trouble. My device is crashing and rebooting sometimes at day. Is there any solution??
Moto g purchased in mexico, telcel.

Guys, return it to your phone dealer if you can. Waiting for a fix(that may or may not come) will just increase your pain. If the service center spots the restart, they should definitely repair/replace your phone.

gee2012 said:
Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.
Click to expand...
Click to collapse
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.

Kit kat seems to have fixed problem.
dankerk said:
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.
Click to expand...
Click to collapse
My wifes phone seemed to be getting worse. It rebooted four times the day before yesterday. It always seemed to be worst when we were travelling.
Yesterday morning the Kit Kat update became available. The phone hasn't rebooted since. Hope I'm not speaking too soon but fingers crossed it seems to be fixed.

We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?

creambyemute said:
We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?
Click to expand...
Click to collapse
If the Kit kat upgrade has cured the problem on my wifes phone then it must have been software related. Possibly an app I had downloaded was causing it. It's worth pointing out as well that most people didn't seem to have this issue.
BTW I spoke to Motorola chat a few days ago using the help app. on the phone. They told me it was probably an app I had downloaded causing it and a factory reset would sort it. Installing the upgrade seems to have done the same thing though.

Happy to hear it's not something hardware related.
I even had reboots with my nexus 5, 4 on random basis (not often). Must be some sort of app I've had installed on all my devices

I received mine in december (from Amazon [Retail.FR]) and experienced some crashes (almost every day).
I installed KitKat on it and did two factor resets to be sure it was not software related issues. Since then, a week ago, I experienced a crash every day and half (screenshot). Crash happened without any reason or specific context.
My serial number is: TA8900B6##
I decided to return my Moto G to Amazon and buy a new one.

I'm experiencing the same and I decided to try to run a constant logcat in the background to see what's going on. Also is there any way to have a constant recording with dmesg? I'm no linux commands expert.
For logcat (in terminal emulator) I used logcat > sdcard/logcat.txt which is growing in size as far as I can see. Hopefully this brings some news.
Good luck everyone.
Cheers

Problem with my OnePlus One's Screen!

Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!

I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.

welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases

I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?

Try going back to cm11s and then check...
Sent from Android (a google product)

Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.

Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!

One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?

naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?

Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.

donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/

vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.

I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.

donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..

vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.

Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!

Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk

anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.

donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk

G930F - crash bootloop issues

Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks

Sacher_Masoch said:
Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks
Click to expand...
Click to collapse
Hi
Do a factory reset , do not restore anything see if it works ok , if so then it maybe an app causing the problem
or you could flash a stock rom to test the phone and make sure there is no hardware issues

Thank you for your answer.
I'll take a try this weekend with a stock rom as I have the issue with 2 custom roms so far.
If anybody has other ideas until that, please let me know

Little feedback. I flashed the stock Samsung rom two days ago and it seems to work fine for now. But it was also quite fine with the custom rom at the beginning, so I will do another feedback after one or two weeks.

Well... The phone froze and rebooted 5 times in 10 minutes after trying to update some apps itself...

I had the same problem. At the end I was not able to boot Android. I had to claim my cell phone to seller. After one month it was repaired. The final verdict was SOFTWARE problem. They said that EFS was corrupted. One of Samsung firmware has bug which cause problem with EFS.

I also had that problem. I also had to send my phone to the repair center. In my case they replaced the mainboard.

I bought one early september and after two weeks it started doing just that. I tried everything, then sent it to the seller (ebay seller...) and the repair shop couldn't anything about it. I only got my money back yesterday. Back when I invesitgated the issue, nobody was talking about it. So since I liked the phone, I bought a new one from another place (less shady) yesterday... I now think I shouldn't have. Anybody knows more about this ?
Edit: I'm thinking that if I root the phone and backup the EFS and all sensitive partitions before starting using it (or even getting updates) I should be safe...

Yeah, that would be great, but your KNOX will be 0x1. So you will have problem to return this phone back with status 0x1.
Odoslané z SM-G930F pomocou Tapatalku

Hello everybody,
Sorry for the very late reply. I actually sent my phone to another shop here in Japan. But this week, they send me a mail to say that they were not able to fix the issue. But still they taker me 50$ for the time...
I was thinking about buying a new one, but now that some of you are talking about an EFS issue, I'll try to fix again. I will look for some tutorial for that, but if you know how to procede, just reply here
Merry Christmas guys !

hello, i've been having a similar issue.
My phone would be fine for 2 weeks, maybe a month then Suddenly it would reboot to no end, it even reboots from TWRP.
It doesn't reboot while in Download mode. Then what i do to fix it is flash a stock rom from ODIN, sometimes the first couple or 5 times it will reboot during initial first boot up of this stock Rom. I would leave it alone for a while like half day then try it again in the evening or the next day.
Today for example, it started boot looping late last night and I installed Stock ROM with PIT FILE and Nand ERASE and Repartition ticked, boot loop, again, boot loop, tried it again, also rebooted before it started up to stock recovery and factory reset. Then it started up fine and has not rebooted so far.
But this has happened many times and it'll happen after 2 weeks or 1 month. When it does, i first go and delete cache and delvic cache to see if that would fix it, but it doesn't.
Right now it works, but for how long i don't know, when it works, everything is fine with the phone, no imei or calling or heating issues.
I can't guess whats wrong, is it really EFS that got corrupted but not fully but eventually its finding a problem and causing boot loops or something if that makes sense??