Related
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
...Awesome... said:
In case of emergency!
Click to expand...
Click to collapse
I dropped my s3 in some water and quickly grabbed it, and dried it off. Everything seemed to be working ok, but then i noticed that it's acting like i don't have my sd card in it when i do. My wifes card gets recognized right away when i put it in, so i think my sd card is no good. Any suggestions on how i can recover data from it?? Thanx
ryanallaire said:
I dropped my s3 in some water and quickly grabbed it, and dried it off. Everything seemed to be working ok, but then i noticed that it's acting like i don't have my sd card in it when i do. My wifes card gets recognized right away when i put it in, so i think my sd card is no good. Any suggestions on how i can recover data from it?? Thanx
Click to expand...
Click to collapse
So your SD card doesn't read but hers does? And yeah then just get a new SD card go on a computer take your files off of it and put em back on the new SD card
Sent from my SCH-I535 using Tapatalk 2
Hi,
New to the S3 and this rom. Root, flash went well, and so far, I'm loving this rom. One problem that is stumping me is this:
Using ADW launcher, have a direct dial short cut to voice mail. The voice mail contact is set up to dial *86 ,,xxxx, so with one tap, I can call vm and access messages.
However, the keyboard then becomes non responsive. I can't delete or save messages, and if I have multiple messages, can't get to the next one.
Any suggestions on how to work around this appreciated.
I'm running the 3.2 beta version of LS, and really only have this, and one other minor issue.
Thank you.
Still haven't solved this, but here's more clarification:
Phone is running LiquidSmooth 4.2.1m v2.1m beta 3.2
1. Using a 'direct dial shortcut. the rom dialer has a contact set up named voicemail, that is programmed: *86;,,XXXX. When I hit the direct dial shortcut, voicemail is dialed, xxxx is sent, and I can hear my first voicemail. The problem is the dialpad is non responsive. So, I can't save or delete the first voicemail, nor can I proceed to listen to the next one.
If I dial *86, and enter the password manually, then the dial pad works.
Even if I dial any contact withGoDialer, then, open keyboard to dial and extension, I get the stock dialer.
I drive a lot, and need as few distractions as possible. Any suggestions on how to fix this would be greatly appreciated.
Thank you.
Have u tried using a different launcher just to be sure its not hardware/ROM related it might be the launcher?
Sent from my HTC One S using Tapatalk 2
--------------If you like puzzle, tackle this---------------
I tried pretty much everything on the internet before posting here.
My stock/no root phone started bootlooping. So I used Odin and root66.tar to get it back. Everything seemed to be good. After I got 3 updates:1) 30mb, 2) 60mb and 3) JB updated OTA. After 60Mb update my phone said Samsung and shows unlocked lock. After JB update my phone bootloops again.
I though it it was a bad update and reflashed stock no root 4.0.4 and OTA did the same thing.
I tried the gs3 tool to flash the recovery and it always fails.
I would appreciate any help.... I have been dealing with this non sense for the past 24h.
...Awesome... said:
Have u tried using a different launcher just to be sure its not hardware/ROM related it might be the launcher?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Yes. I've been using ADW launcher, tried it with Nova, got the exact same result.
Alright, I'll try here. So, I'm on cleanrom 5.6. As far as I can tell everything is working, and there aren't any actual problems, but the phone doesn't know what the network is in settings and and when I drag down the notification bar it doesn't say it at the bottom. Anyone have an idea?
Sent from my SCH-I535 using xda app-developers app
MEID
does your cellular service connect? Also you are on verizon right? and did you do a dirty flash of cleanrom 5.6?
LtZKilla said:
Alright, I'll try here. So, I'm on cleanrom 5.6. As far as I can tell everything is working, and there aren't any actual problems, but the phone doesn't know what the network is in settings and and when I drag down the notification bar it doesn't say it at the bottom. Anyone have an idea?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
jwattt said:
does your cellular service connect? Also you are on verizon right? and did you do a dirty flash of cleanrom 5.6?
Click to expand...
Click to collapse
Yeah, my cell service connects and I can text and call. It just doesn't seem to have any idea that my carrier is verizon and it kinda seems odd.
Sent from my SCH-I535 using xda app-developers app
I am trying to install the stock systemui.apk file on my phone after I screwed up and flashed the wrong one, but installation always fails. I have moved the .apk to the /system/app folder and have changed the permission of the .apk but the file still won't install. What can I do?
carrier
Since you carrier wont load I believe following this tutorial with help fix your problem but check the conditions. Im not allowed to post links apparently so I attached it. I'll also flash cleanrom 5.6 and find out if its a software thing and get back to you. But it seems to me like its a MEID issue. So check the conditions in the link and if they are true I'd go that way. If not re-flash, clean install would be my suggestion. Yeah I run Cynagenmod 10.1 and it even knows I'm on Verizon. And Scott's roms always have the carrier.
LtZKilla said:
Yeah, my cell service connects and I can text and call. It just doesn't seem to have any idea that my carrier is verizon and it kinda seems odd.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
havy15 said:
So your SD card doesn't read but hers does? And yeah then just get a new SD card go on a computer take your files off of it and put em back on the new SD card
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
computer doesn't see the card at all..
I can't recall when I last had it working but my NFC completely stopped working. I have tried reverting back to absolute stock rooted nandroid. That didn't work so I Odin booted back to the original unrooted firmware. Still same problem. If I try to uncheck NFC from the more options it moves over and is immediately flipped back. I have gone into a Verizon wireless store to seek help but the guy made a sarcastic remark that his iPhone wouldn't have that problem...but I also as a few other notes I have tried hells ROM and also flashing the NFC file with the ROM which also didn't work and have tried the few NFC Google wallet fixes I have seen, also sadly no luck. I'm stubborn and don't want to give up if anyone knows if there is a possible fix, hope you can possibly help!
Sent from my SCH-I535 using xda app-developers app
replacement?
I think you may have a faulty chip. Also is your battery NFC capable? But to be honest Verizon will replace it for free if your under the 1 year warranty and don't have water damage or anything like that. Because if it doesn't work on the stock rom it's most likely a hardware problem in this case. So I would contact your carrier about that.
CeeMillz said:
I can't recall when I last had it working but my NFC completely stopped working. I have tried reverting back to absolute stock rooted nandroid. That didn't work so I Odin booted back to the original unrooted firmware. Still same problem. If I try to uncheck NFC from the more options it moves over and is immediately flipped back. I have gone into a Verizon wireless store to seek help but the guy made a sarcastic remark that his iPhone wouldn't have that problem...but I also as a few other notes I have tried hells ROM and also flashing the NFC file with the ROM which also didn't work and have tried the few NFC Google wallet fixes I have seen, also sadly no luck. I'm stubborn and don't want to give up if anyone knows if there is a possible fix, hope you can possibly help!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the stock battery and when I did call Verizon the first time they wanted me to contact Samsung first then get back to them so I figured i'd bring it here. It had worked before so I was wondering if maybe it fried somehow? Phone has never been dropped, no water damage, watch because I said that i'll drop it in 5 minutes and shatter my screen I guess I'll just try Samsung tomorrow and see what they have to say.
nfc
Actually I just thought of something else to try. Have you gone in and force quit nfc and cleared the app data? That may resolve the problem. Nfc will be under all apps and it is named nfc service.
CeeMillz said:
I have the stock battery and when I did call Verizon the first time they wanted me to contact Samsung first then get back to them so I figured i'd bring it here. It had worked before so I was wondering if maybe it fried somehow? Phone has never been dropped, no water damage, watch because I said that i'll drop it in 5 minutes and shatter my screen I guess I'll just try Samsung tomorrow and see what they have to say.
Click to expand...
Click to collapse
jwattt said:
Actually I just thought of something else to try. Have you gone in and force quit nfc and cleared the app data? That may resolve the problem. Nfc will be under all apps and it is named nfc service.
Click to expand...
Click to collapse
Good idea, just tried it and it didn't do anything. Also tried that, rebooted recovery, wiped dalvick and cache fixed permissions then tried again with no luck. =/
nfc
Are you using a non stock kernel? Also when you went back to stock did you erase everything on the phone?
CeeMillz said:
Good idea, just tried it and it didn't do anything. Also tried that, rebooted recovery, wiped dalvick and cache fixed permissions then tried again with no luck. =/
Click to expand...
Click to collapse
So I think they weren't working at all because my IMEI wasn't updated with AT&T when I got my replacement phone. Got that addressed.
Since then, I was able to receive old MMS, but even new ones sometimes get hung up on trying to retrieve them. exiting app and going back in doesn't fix it.
Starting the phone up again does though..
Made sure APN settings are good to go, unchecked 'mobile data' in sms settings and re-enabled within Hangouts.
I'm on stock rooted 4.4 (and franco kernel)
any idea whats going on? It seems like other people are having this problem too but I don't understand it. Thanks.
I am seeing the same issues here.. Stock play store purchased and rooted on Sprint, sometimes it works sometimes it doesn't, sometimes even SMS sits forever and wont send or receive until I restart the phone, trying to find someone with a Sprint purchased N5 to compare APNs with
Its almost 2014, you would think someone would be able to straighten out the massive amount of MMS issues with android phones :/ It should "just work" to the customer
I have a feeling it has something to do with Hangouts app itself..
I have issues with hangouts indefinitely, also with textra and handcent. Like OP said,sometimes it works sometimes it doesn't.
Sent from my Nexus 5 using xda app-developers app
Teczeus said:
I have issues with hangouts indefinitely, also with textra and handcent. Like OP said,sometimes it works sometimes it doesn't.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
That's interesting you're also experiencing it with other apps.
I haven't tried anything but Hangouts.
Maybe it's a Kit Kat issue? no clue.
Considering you have At&t and I have sprint, im guessing ruling out the carrier is OK.
Sent from my Nexus 5 using xda app-developers app
Teczeus said:
Considering you have At&t and I have sprint, im guessing ruling out the carrier is OK.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
This is true.
Running on metro pcs and my mms is perfect with hang out and sliding messaging pro. Metro runs gsm off T-Mobile towers.
Sent from my Nexus 5 using Tapatalk
Interesting, i wonder what the root of the issue is since it's selectively working.
Can't be hardware, because it selectively works whereas my data and nothing else has been on the fritz, and it seems like whenever I receive errors rebooting and going back into the app it loads the ones it was hung up on. Seems like it downloads it, but just shows an error instead of displaying the MMS.
Hmmm
And I had AT&T double check the IMEI I provided them was accurate..
Hopefully it just resolves itself eventually, either the network, or a software hiccup, or whatever it is.
Because this Nexus 5 I have right now is a perfect "copy" or whatever you want to call it, a perfect build.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
It makes sense that that would be the culprit too because it requires root access, and permissions don't seem to kick in until slightly after the phone boots up initially which would coincide with mms received and sent just for those first few moments.
Good luck all, found this advice somewhere else, and so glad it's not a hardware defect as I had suspected it wasn't.
tyrellcorpnexus said:
Interesting, i wonder what the root of the issue is since it's selectively working.
Can't be hardware, because it selectively works whereas my data and nothing else has been on the fritz, and it seems like whenever I receive errors rebooting and going back into the app it loads the ones it was hung up on. Seems like it downloads it, but just shows an error instead of displaying the MMS.
Hmmm
And I had AT&T double check the IMEI I provided them was accurate..
Hopefully it just resolves itself eventually, either the network, or a software hiccup, or whatever it is.
Because this Nexus 5 I have right now is a perfect "copy" or whatever you want to call it, a perfect build.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
It makes sense that that would be the culprit too because it requires root access, and permissions don't seem to kick in until slightly after the phone boots up initially which would coincide with mms received and sent just for those first few moments.
Good luck all, found this advice somewhere else, and so glad it's not a hardware defect as I had suspected it wasn't.
Click to expand...
Click to collapse
Thanks for the update! More knowledge into my brain housing group to share now lol.
FuMMoD said:
Thanks for the update! More knowledge into my brain housing group to share now lol.
Click to expand...
Click to collapse
No problem I hope it helps some of you guys out!
tyrellcorpnexus said:
Interesting, i wonder what the root of the issue is since it's selectively working.
EDIT: I FOUND THE ROOT OF THE PROBLEM!!!
adblock for me. Uninstalling didn't fix it either. Just resetting the phone (wiping everything in settings) nipped it in the bud.
Click to expand...
Click to collapse
In my case MMS started working after disabling Adblock in the app itself. Then I went ahead an uninstalled. Thanks for the head up!
jonzr said:
In my case MMS started working after disabling Adblock in the app itself. Then I went ahead an uninstalled. Thanks for the head up!
Click to expand...
Click to collapse
For sure! adaway had been working well for me.
Same issue here on Tmobile
tyrellcorpnexus said:
For sure! adaway had been working well for me.
Click to expand...
Click to collapse
I am having same issue on Tmobile with stock Nexus 5. Only restarting the phone helps.
jamjr74 said:
I am having same issue on Tmobile with stock Nexus 5. Only restarting the phone helps.
Click to expand...
Click to collapse
Same here but with hancent and hangouts
Hopefully someone can help me with this.
I am having an issue with my phone where the top left corner does not want to respond unless I restart the phone. This happens a completely random times and I am unable to pinpoint it. It all started the other day when the update came out. I have format my phone I have used Samsung smart switch to reinstall the OS and issue keeps coming back. I'm also having the same issue towards the bottom where are Google now application launcher is located. If you are using TouchWiz it is in the middle of the message app when I press the area it doesn't do anything unless I press to the right of it. I have turned on developer tools and selected show touches. I can see the touches and everything looks like it should work but the OS doesn't do anything. Once I reboot everything goes back to normal. When this happens I am unable to hit back on applications such as Gmail and I have to use a physical button to go back.
Phone is completely stock and had not been rooted.
Has anyone else had this issue?
Thanks for your help
Admin can you please move to Q&A thread please. I realized I posted in the wrong spot.
This has also happened to me and I'm on a custom rom. Mind you, my screen was replaced not long ago because of stuck pixels, and I thought this could be problem with the new screen. Not sure what is happening, though.
I found on another forum that it had to do with Samsung pay and when that corner stops working for me I force stop the pay and pay framework and it stays working again
Sent from my SM-N920T using Tapatalk
dcasey627 said:
I found on another forum that it had to do with Samsung pay and when that corner stops working for me I force stop the pay and pay framework and it stays working again
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Awesome, going to disable it all together for now. Hopefully they fix it. Only reason I haven't rooted yet is Samsung pay.
Thank you @dcasey627
laristech said:
Awesome, going to disable it all together for now. Hopefully they fix it. Only reason I haven't rooted yet is Samsung pay.
Thank you @dcasey627
Click to expand...
Click to collapse
I wasn't able to figure out how to disable it so I have to go in a couple times a day to stop it
Sent from my SM-N920T using Tapatalk
dcasey627 said:
I wasn't able to figure out how to disable it so I have to go in a couple times a day to stop it
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I use this https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro
It's less than 2 bucks and doesn't require root. (can't use with root anyways) It can disable any app including the Tmobile my account app.
Best 2 bucks I've spent.
Perfect! Thank you very much
Sent from my SM-N920T using Tapatalk
I'm actually currently having this same exact problem. The thing that confused me was that it's the top left corner, no matter your screen orientation. Meaning it MUST be something OS related. But now I'm hearing Samsung Pay is the culprit? It's never caused this before until today...
dcasey627 said:
I found on another forum that it had to do with Samsung pay and when that corner stops working for me I force stop the pay and pay framework and it stays working again
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Briankbl said:
I'm actually currently having this same exact problem. The thing that confused me was that it's the top left corner, no matter your screen orientation. Meaning it MUST be something OS related. But now I'm hearing Samsung Pay is the culprit? It's never caused this before until today...
Click to expand...
Click to collapse
Well, wasn't Samsung Pay. I had both disabled and the issue came up today. I tried to figure out which app it was but I couldn't figure it out. I went to my recent apps and forced closed each one but the left corner was still messed up. I couldn't get it back until I restarted.
Others are having the same issues on reddit.
https://www.reddit.com/r/tmobile/comments/3yd0k9/issues_with_note_5_do_i_go_to_the_store/
https://www.reddit.com/r/galaxynote5/comments/3y4fhm/after_update_on_tmobile_screen_partially_not/
https://www.reddit.com/r/galaxynote5/comments/3ydl9h/upper_left_hand_corner_of_screen_becomes/
laristech said:
Well, wasn't Samsung Pay. I had both disabled and the issue came up today. I tried to figure out which app it was but I couldn't figure it out. I went to my recent apps and forced closed each one but the left corner was still messed up. I couldn't get it back until I restarted.
Click to expand...
Click to collapse
When I force close them I also Uninstall the updates and clear the cache. That always seems to fix it for me.
Sent from my SM-N920T using Tapatalk
dcasey627 said:
When I force close them I also Uninstall the updates and clear the cache. That always seems to fix it for me.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I just uninstalled, clear cached, and and restarted. I'll see if it comes back. Thanks for your update.
Glad to know the problem is possibly a widespread one so Samsung has a better chance at fixing this.
Briankbl said:
Glad to know the problem is possibly a widespread one so Samsung has a better chance at fixing this.
Click to expand...
Click to collapse
Yeah hopefully. T-mobile said all updates come from Samsung so they can't do anything but exchange the phone. Someone on reddit said he exchanged his phone and the issue came back. Plus, they send you a refurbish sometimes.
laristech said:
Yeah hopefully. T-mobile said all updates come from Samsung so they can't do anything but exchange the phone. Someone on reddit said he exchanged his phone and the issue came back. Plus, they send you a refurbish sometimes.
Click to expand...
Click to collapse
It's an irritating problem, for sure, but not enough to go through all that. I'm just gonna wait it out for that Marshmallow update in January.
I'm having the same issue. I thought it was my phone and was about to contact tmobile about sending a replacement. Glad to know it's not just me. Looks like I'll just wait until the next update.
And I don't think it's Samsung Pay since I'm rooted and don't even have it installed
laristech said:
Hopefully someone can help me with this.
I am having an issue with my phone where the top left corner does not want to respond unless I restart the phone. This happens a completely random times and I am unable to pinpoint it. It all started the other day when the update came out. I have format my phone I have used Samsung smart switch to reinstall the OS and issue keeps coming back. I'm also having the same issue towards the bottom where are Google now application launcher is located. If you are using TouchWiz it is in the middle of the message app when I press the area it doesn't do anything unless I press to the right of it. I have turned on developer tools and selected show touches. I can see the touches and everything looks like it should work but the OS doesn't do anything. Once I reboot everything goes back to normal. When this happens I am unable to hit back on applications such as Gmail and I have to use a physical button to go back.
Phone is completely stock and had not been rooted.
Has anyone else had this issue?
Thanks for your help
Click to expand...
Click to collapse
I had the same issue. I called tmobile and they were useless. Phone is stock and not rooted. Mine would happen and id reset the phone, it would be good for a few hours and then happened again. At first I thought it may be my case touching a part of the screen since the phone has such thin bezels. It wasn't the problem. I decided to do a factory reset and I've been good for 5 days now. I used Samsung pay before the reset and still use it now.
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
Kirollos11 said:
I had the same issue. I called tmobile and they were useless. Phone is stock and not rooted. Mine would happen and id reset the phone, it would be good for a few hours and then happened again. At first I thought it may be my case touching a part of the screen since the phone has such thin bezels. It wasn't the problem. I decided to do a factory reset and I've been good for 5 days now. I used Samsung pay before the reset and still use it now.
Click to expand...
Click to collapse
Prior to the factory reset, I also tried clearing catch and didn't work.
Kirollos11 said:
I had the same issue. I called tmobile and they were useless. Phone is stock and not rooted. Mine would happen and id reset the phone, it would be good for a few hours and then happened again. At first I thought it may be my case touching a part of the screen since the phone has such thin bezels. It wasn't the problem. I decided to do a factory reset and I've been good for 5 days now. I used Samsung pay before the reset and still use it now.
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
Prior to the factory reset, I also tried clearing catch and didn't work.
Click to expand...
Click to collapse
Yeah, they were useless for me too. I'm chatting with Samsung support via FB but they don't have any idea either. I've tried everything as well. I'm really out of options at this point. Sometimes when I clear everything from recent apps it starts working again but when I clear the same apps via force quit it doesn't work. I cant' figure out which app is causing it.
Samsung support is having me run my phone in safe mode for a few hours to see if the issues comes back. They're trying to see if it's a built in app or third party one.
There was a new update today. The new version is N920VVRS2BPF2. Not sure what changed though.
I wouldn't download this yet guys/girls because it's looking like this is a security patch to stop us from downgrading from MM to Lollipop!! Once this has been accepted you can't even factory reset or it will render the phone useless!!
I don't know why people have an issue with Marshmallow. Runs flawlessly, I'm usually sitting at 1880MB of free space of RAM, no stuttering, looks and feels cleaner.
Sent from my SM-N920V using Tapatalk
ukemochi said:
I don't know why people have an issue with Marshmallow. Runs flawlessly, I'm usually sitting at 1880MB of free space of RAM, no stuttering, looks and feels cleaner.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Not everyone's phone is the same that's why. Some people like Lollipop over Marshmallow and depending on how you use it and what apps you have on there are also a determining factor in how the rom runs.
Took this update earlier this morning, phone runs like a dream on mm. Starting to notice some slight slowdown with battery saver on. Might be time for a full wipe and reinstall. I did one with the first mm update but there's been like three now since then.
Sent from my SM-N920V using Tapatalk
udis said:
Took this update earlier this morning, phone runs like a dream on mm. Starting to notice some slight slowdown with battery saver on. Might be time for a full wipe and reinstall. I did one with the first mm update but there's been like three now since then.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Good luck! Someone else who tried to do a factory reset and wipe caused the phone to get stuck and so far he hasn't been able to do anything at all to fix it!!
Yikes guess I'll be holding off then
Sent from my SM-N920V using Tapatalk
I accidently hit the install for this update. Ever since MM my battery life, screen on time, has been horrible (2.5-3.5 hours MAX). I've factory reset, wiped cache, tried the package disabler with extreme settings and it still is not right. I was thinking about going back to lollipop but if this update froze that I may dump this phone and look for another. that I can root.
b4u2 said:
I accidently hit the install for this update. Ever since MM my battery life, screen on time, has been horrible (2.5-3.5 hours MAX). I've factory reset, wiped cache, tried the package disabler with extreme settings and it still is not right. I was thinking about going back to lollipop but if this update froze that I may dump this phone and look for another. that I can root.
Click to expand...
Click to collapse
That sucks dude!! I've figured out that if you factory reset *before* you accept any updates, the battery and phone will work much better! I'm not sure what you can do at this point except maybe try to Odin the stock Lollipop rom and see if it works cause maybe the other guy's phone was just a fluke! You have to enable OEM unlock first and enable adb in developer settings.
MrMike2182 said:
Good luck! Someone else who tried to do a factory reset and wipe caused the phone to get stuck and so far he hasn't been able to do anything at all to fix it!!
Click to expand...
Click to collapse
I'm on MM and did a reset last week. I could not sign in to the phone using my Google account for 24 hrs.
If you do a Google search you can find out about this new "security feature".
Also you can reboot the phone by holding down the volume down, then home, then power in that sequence for 10 seconds.
lnjryan said:
I'm on MM and did a reset last week. I could not sign in to the phone using my Google account for 24 hrs.
If you do a Google search you can find out about this new "security feature".
Also you can reboot the phone by holding down the volume down, then home, then power in that sequence for 10 seconds.
Click to expand...
Click to collapse
You're trying to help the wrong person buddy, lol.
MrMike2182 said:
You're trying to help the wrong person buddy, lol.
Click to expand...
Click to collapse
When did they start doing that 24 hour hold?
jaydizman said:
When did they start doing that 24 hour hold?
Click to expand...
Click to collapse
They've been doing it for quite a while.. It's supposed to be a security guard against people stealing your phone and factory resetting it immediately so they can use it. The simple way to stop this is to activate developer mode and enable OEM unlock and USB debugging! Most people who don't bother to read nothing should be happy that it's only 24 hours instead of the 72 (3 days) that it used to be! All they need to do is research before doing anything to their phones.
MrMike2182 said:
They've been doing it for quite a while.. It's supposed to be a security guard against people stealing your phone and factory resetting it immediately so they can use it. The simple way to stop this is to activate developer mode and enable OEM unlock and USB debugging! Most people who don't bother to read nothing should be happy that it's only 24 hours instead of the 72 (3 days) that it used to be! All they need to do is research before doing anything to their phones.
Click to expand...
Click to collapse
So it just buys you time if your phone is stolen. Fine right do what exactly I would track it.. Or remote wipe it.. Just not seeing the benefit
jaydizman said:
So it just buys you time if your phone is stolen. Fine right do what exactly I would track it.. Or remote wipe it.. Just not seeing the benefit
Click to expand...
Click to collapse
Yeah it basically buys you time to track it or wipe the phone and lock it down. It also gives you time to change your password just in case. If people don't want it they can disable it as I said and you can enable it again later if you choose to. I don't see how it's going to hurt anyone so long as they read and learn about their phone before doing anything to it.
MrMike2182 said:
They've been doing it for quite a while.. It's supposed to be a security guard against people stealing your phone and factory resetting it immediately so they can use it. The simple way to stop this is to activate developer mode and enable OEM unlock and USB debugging! Most people who don't bother to read nothing should be happy that it's only 24 hours instead of the 72 (3 days) that it used to be! All they need to do is research before doing anything to their phones.
Click to expand...
Click to collapse
What? I've been using Android phones with Verizon for as long as there has been such a thing...and I've never waited three days after a reset or one day either. Personal experience here or rumor?
ratman6161 said:
What? I've been using Android phones with Verizon for as long as there has been such a thing...and I've never waited three days after a reset or one day either. Personal experience here or rumor?
Click to expand...
Click to collapse
Personal experience several times! Either it's on or off and the carrier can even hide the option so you don't even know it's there. Personally I think it doesn't happen when you're somewhere you normally use your phone but if you go to say another state it's going to know and activate it.
I've reset an lg g2 tons of times flashing it, s4 multiple times and my note 5 twice and I've never had to wait ever. Could it be because I use 2 step authentication?
Sent from my SM-N920V using Tapatalk
Stupid update has screen time like 6th on my list of battery consumption. Thanks for the security update Verizon. Google services seems to be my main drain. Then media server. Nothing like ruining my great battery life.
Sent from my SM-N920V using XDA-Developers mobile app
MrMike2182 said:
I wouldn't download this yet guys/girls because it's looking like this is a security patch to stop us from downgrading from MM to Lollipop!! Once this has been accepted you can't even factory reset or it will render the phone useless!!
Click to expand...
Click to collapse
This is totally false. I just upgraded my wife's Note 5 and then downgraded back to KK. All that is required is a factory data reset after the downgrade. You can do this by holding down the volume up, home and power buttons for 10 seconds. The phone will reboot into recovery and then you can reset and be on your way. Just keep your Google account and password handy if needed.
Have you guys successfully used Android Pay yet? Mine seems to be all setup fine but it never scans when I try. Where is the NFC chip in this phone?
mikecousins said:
Have you guys successfully used Android Pay yet? Mine seems to be all setup fine but it never scans when I try. Where is the NFC chip in this phone?
Click to expand...
Click to collapse
It's actually just under the camera, try it out next time, mine works 100% fine
Nice, thanks. I was trying more centered on the phone. I just tried it near the camera and it worked.
mikecousins said:
Nice, thanks. I was trying more centered on the phone. I just tried it near the camera and it worked.
Click to expand...
Click to collapse
1st few times I tried I didnt know the phone had to be unlocked. Been using iOS for far too long and it just worked regardless of the phone being locked or where I held the phone. had a few issues on the Razer phone however now that I know where the NFC chip is ill see how it goes.
---------- Post added at 10:59 AM ---------- Previous post was at 10:40 AM ----------
Just used it and it failed on me this morning in my local shop where its been fine for the past 2 days. Nice that the app/system noticed that I had an issue and wanted to know what happened. Was more than happy to pull out the physical version of the card and submit info to Android pay to find out what went wrong.
iStasis said:
Just used it and it failed on me this morning in my local shop where its been fine for the past 2 days. Nice that the app/system noticed that I had an issue and wanted to know what happened. Was more than happy to pull out the physical version of the card and submit info to Android pay to find out what went wrong.
Click to expand...
Click to collapse
Just tried using it an hour or so ago at a place where it did work with another phone and it failed. Tried 3-4 times then i just used the card.
godashram said:
Just tried using it an hour or so ago at a place where it did work with another phone and it failed. Tried 3-4 times then i just used the card.
Click to expand...
Click to collapse
My nfc chip is hit or miss too. Glad I'm not the only one.
Sent from my Phone using Tapatalk
android01 said:
My nfc chip is hit or miss too. Glad I'm not the only one.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
while I don't recommend ANYONE do this.... I dropped my razer the other day, and NFC has worked fine since.... which boggles my mind
godashram said:
Just tried using it an hour or so ago at a place where it did work with another phone and it failed. Tried 3-4 times then i just used the card.
Click to expand...
Click to collapse
Me too hopefully they sort in next update
I tried using it an hour or so ago at a place where it did work with another phone and it failed. I tried many times but I'm totally failed. May be worked using card.
Mine has worked every time I've used it at multiple stores.
mine started failing again. was able to test finally and mine is reading NFC tags and everything NFC multiple times. When using Android Pay, it causes the transaction to fail due to attempting to use multiple cards.
The chip is in the middle, not the top like in most phones, and it's a bit slower than say on a pixel phone. Hold the middle of the phone directly at the top of most terminals for 3 seconds and you should get a 100% success rate. I had the problem too, but since doing this is works good.
it is in the top, that I can verify (we have a spare NFC terminal at work, easy for testing, but I can also test on a live unit, and I have various NFC tags)
Also, mine acts as if it's rapid fire, the terminal (both test and live)reads multiple attempts from the phone, so the terminal thinks it's getting bombarded multiple times with NFC devices, cancelling the transaction.
Razer just sent me a return shipping label for an exchange, hopefully it doesn't take long
superostrich said:
Mine has worked every time I've used it at multiple stores.
Click to expand...
Click to collapse
Do you go straight to the scan ?
godashram said:
it is in the top, that I can verify (we have a spare NFC terminal at work, easy for testing, but I can also test on a live unit, and I have various NFC tags)
Also, mine acts as if it's rapid fire, the terminal (both test and live)reads multiple attempts from the phone, so the terminal thinks it's getting bombarded multiple times with NFC devices, cancelling the transaction.
Razer just sent me a return shipping label for an exchange, hopefully it doesn't take long
Click to expand...
Click to collapse
Small update... Before sending back via rma, I decided to test again with a factory restore. When talking to the bank to re-enable Android pay, I asked if they could delete all previous authorizations for Android pay. So far, I've used it twice today and it's worked so far.
Sent from my Phone using Tapatalk
Accerty said:
Do you go straight to the scan ?
Click to expand...
Click to collapse
I open up my wallet app, click on my card and just hold on the reader for half a second. Used it again today with no lag or problems
Used it at my local forbidden planet today worked fine
every other store after that was a nightmare, either didn't work or I had to stand there waving it about to get the chip to pick up. The weirdest one was tesco where it said I was trying to use 2 contactless cards at once...something is definitely wrong
Well, I think I solved my issue... Before sending it back to Razer, I tried reactivating Android Pay with my bank card, and since I have to call my bank to do so, I had them delete all previous authorizations before authorizing my phone again.
So far, it's batting 100! 4 attempts, and all 4 worked. Not sure why it matters, as it didn't on my LG,
godashram said:
while I don't recommend ANYONE do this.... I dropped my razer the other day, and NFC has worked fine since.... which boggles my mind
Click to expand...
Click to collapse
Are you sure you didn't drop it again and that's why it's working so well today?
The NFC is just legit crap on this handset. And like you say, probably some corrupt software bug that needs a nice patch. ( Or all info deleted and reinstalled / added until it corrupts it self again , which it probably will )
I don't think an RMA will work for a problem we are all experiencing equally. This is definitely a bug of some type. Otherwise it would not work ever. And only affect a single user.
Sent from my Phone using Tapatalk
android01 said:
Are you sure you didn't drop it again and that's why it's working so well today?
The NFC is just legit crap on this handset. And like you say, probably some corrupt software bug that needs a nice patch. ( Or all info deleted and reinstalled / added until it corrupts it self again , which it probably will )
I don't think an RMA will work for a problem we are all experiencing equally. This is definitely a bug of some type. Otherwise it would not work ever. And only affect a single user.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
pretty sure I didn't drop it again
But seriously, there is probably a bug. When testing at work (I can actually test android pay using a test and repair feature on a POS system here) I used to get 2-4 beeps when trying my primary card in Android Pay, which results in a failure due to multiple card attempts. After having the bank remove all previous authorizations, I am getting a single beep with a pass message. Now I did have 2 previous bank authorizations with my previous phone, and another 2 with the razer, which the bank did delete all previous authorizations before adding the new one.
Also used it again this morning and it worked (where it failed previously) So, since I just got paid, i'll test it EVERYWHERE this weekend and if it fails, I stil have an active RMA, but if it doesn't then I'll just have to remember to delete this authorization if I every hard reset the phone (unless Razer fixes the issue)