Related
Order of what's happened:
2nd or 3rd day after I received the phone, I set up Wallet. Had no issues, it loaded up all my cards and I used the phone to make a purchase at a Rite Aid. $10, went fine.
Couple days later I tried to use it at a Wawa. The app itself opened but the payment portion wouldn't work. Didn't think much of it. Paid for my purchase with my CC instead.
Couple days after that, went to open Wallet and it doesn't get past the "Setting up Wallet" screen. Let it go a good 15 minutes then it FCd.
So far I've tried:
-contacting Google Wallet support. CSR advised I try clearing data and cache for Wallet. Did nothing.
-T-Mobile said it's a 3rd party app and to contact Google (this was a 2nd tier CSR telling me that)
-I tried disabling Wallet on my Nexus 4 through the browser. Wallet then opens up on my N4 and it gets about 96% done removing payment cards and then never finishes. I even let it go for the better part of an hour.
-Yesterday I went to my T-Mobile store and got a new micro SIM. Did nothing. I'd heard that Isis micro SIMs can interfere. New SIM did nothing.
-Removed the SIM and tried opening Wallet while connected to my wireless network at home. Nothing.
-Did a factory reset earlier this morning. Nothing.
Every solution I've tried ends with the same result. Wallet gets stuck at the "Setting up Wallet" screen.
I'm at my wits end. I used Wallet on my Nexus S for 2 years with no problems. I was able to use it once with my N4 and now nothing.
Any ideas that I haven't tried? Help or feedback is much appreciated. Thanks.
Edit: Not rooted. Haven't tinkered with the N4 in that regard at all yet.
Sent from my Nexus 7 using xda app-developers app
- If you're rooted, try wiping all caches.
- go to google.com/wallet and see if there's anything bad there.
- try re-entering your creditcard
Shemploo said:
- If you're rooted, try wiping all caches.
- go to google.com/wallet and see if there's anything bad there.
- try re-entering your creditcard
Click to expand...
Click to collapse
****. Need to edit to say I'm not rooted.
Nothing bad at google.com/wallet
I can't re-enter my credit card since I can't get past the "Setting up Wallet" screen.
Sent from my Nexus 7 using xda app-developers app
I believe you can enter your CC info into google.com/wallet (I doubt it, but this could help you advance past the part you're stuck on)
Also, there's no reason why not to root, try a different ROM and see if this resolves your issue.
Try doing Android Beam, make sure NFC is on and put the phone back to back to another smartphone that has Android 4.1 (I believe that's the minimum required) see if you get an option to beam stuff.
Shemploo said:
I believe you can enter your CC info into google.com/wallet (I doubt it, but this could help you advance past the part you're stuck on)
Also, there's no reason why not to root, try a different ROM and see if this resolves your issue.
Try doing Android Beam, make sure NFC is on and put the phone back to back to another smartphone that has Android 4.1 (I believe that's the minimum required) see if you get an option to beam stuff.
Click to expand...
Click to collapse
The Beam works. Tried it yesterday using the N4 with my N7.
I have nothing against rooting. I'll probably end up trying that but it bothers me that Wallet is broken while I'm NOT rooted, ya know?
Sent from my Nexus 7 using xda app-developers app
If you are sure your new sim is not an isis Sim then just get a replacement phone
Sent from my Nexus 4 using Tapatalk 2
furlonium said:
The Beam works. Tried it yesterday using the N4 with my N7.
I have nothing against rooting. I'll probably end up trying that but it bothers me that Wallet is broken while I'm NOT rooted, ya know?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My experience was actually backwards. I initially cut down my old sim to use in the N4 and everything worked from what I could tell. Data, wifi, bt, etc but when I tried loading up google wallet, it would time out.
I figured it was because of my ghetto rig sim, so I ordered one online for 1.08 shipped to me. About a week later, I tried that sim card and loaded google wallet.
Same issue, it would time out. I then for the heck of it tried to beam between the N4 and the N7 and at first that timed out as well. So I rebooted both phone and tablet to try again. This time pics transferred back and forth without an issue.
After closing out the gallery, I saw that google wallet loaded up, and I didn't even hit the app to open it. I found it weird but I think it was because wallet was probably loading on the reboot.
Tried it out at McD's and worked fine. I find it kinda odd that I had to jumpstart the app in this way. I had to do something similar when pairing my bluetooth devices. I had to pair and unpair and pair again to get bt pairing to stick. Weird but since then everything has been working.
And to preface, I was unlocked all that time but not rooted. I just rooted a few days ago after everything was working, from what I can tell.
Info about Google wallet from support.
I like many of you have experienced issues with Google wallet using T-mobile. Please refer to the thread of emails from wallet support. It appears that they are aware of the issue, and there is some fix coming from tmobile or google, I am a bit confused. I have tried wallet on two different Nexus 4 one was a RMA replacement, and still haven't had success.
Hopefully someone can figure this out, because Wallet worked well on my Galaxy Nexus.
Apologies for the confusion, we were given the impression that this was a fix on the back-end that meant you wouldn't require to perform a manual update. Unfortunately, when asking for further information, the team has confirmed that it will need a manual update. Unfortunately, due to the holiday season and complexity of the issue, it may be a few weeks before this is pushed out.
I'm terribly sorry about the inconvenience this has caused you and the amount of back and forth it has taken to get to what isn't really an immediate solution. If you would like to continue to use Google Wallet, we suggest you try using a different SIM card, one that does not contain a secure element.
I'm also happy to keep track of this issue and send you an email as soon as it's resolved so you can use the application with your current setup.
Thanks
Fred
The Google Wallet Team
On 12/12/12 16:00:51 "SP" <[email protected]> wrote:
Thanks Fred,
I am a bit confused. I didn't receive any pushed fixed (was that with t-mobile or Google?). I did do as you asked and went to the local CVS and received the same error. I will do it again, and try another store tomorrow.
On Wed, Dec 12, 2012 at 2:42 PM, <[email protected]> wrote:
Hello ,
Thanks for bearing with us on this issue. I'm happy to report that our engineering team was able to identify your issue and your hypothesis was correct in that it was an issue with how it was interacting that your new T-Mobile SIM. They have informed us that they have now pushed a fix for this issue.
Please reset the application and clear data and try again.
If you are still having problems, please don't hesitate to contact us.
Thank you very much for flagging this issue and we hope you continue to use Google Wallet.
Fred,
The Google Wallet Team
On 12/07/12 15:13:49 "SP" <[email protected]> wrote:
Thanks I look forward to your inquiry. I'm starting to believe I have a defective phone.
Sent from mobile device.
Thanks,
Shawn
On Dec 7, 2012 6:12 PM, <[email protected]> wrote:
Hello ,
First off, I'd like to apologize for the delay in responding to your inquiry, there were technical issues preventing us from getting to your email. I have reviewed the details of your case and can confirm that this is not an issue we have seen before. I have forwarded the details and the screenshot (thanks for the proactiveness!) to our engineering team to investigate and I'll get back to you as soon as I hear back from them.
Thanks,
Fred
The Google Wallet Team
On 12/07/12 14:54:51 "SP" <[email protected]> wrote:
Wallet still not working. Attached is what happens
Sent from mobile device.
Thanks,
On Dec 5, 2012 7:27 AM, "SP" <[email protected]> wrote:
Any ideas on my issue. Wallet is still not working.
Sent from mobile device.
Thanks,
On Dec 2, 2012 6:18 PM, "SP" <[email protected]> wrote:
Thank you.
Sent from mobile device.
Thanks,
On Dec 2, 2012 6:16 PM, <[email protected]> wrote:
Hello ,
Thanks for your quick response. I highly appreciate your input. I'll make sure to relay this information to the specialist where I escalated your case to. I do apologize for the inconvenience. I will keep you informed once I got an answer from the specialist reviewing the issue.
Thanks,
John
The Google Wallet Team
On 12/02/12 18:06:28 "SP" <[email protected]> wrote:
I have been reading things on the Internet. Other user reporting that the new Tmobile Sim card may have NFC chip which can be causing an issue. I am not sure if my Sim is one. I will continue to research.
Sent from mobile device.
Thanks,
Shawn
On Dec 2, 2012 6:03 PM, <[email protected]> wrote:
Hello ,
Thank you for contacting Google. Based on the complexity of the issue, I have forwarded your case to a specialist for review. I appreciate your patience with this issue.
In the meantime, if you have any more information to add about this issue, feel free to reply to this email. Your replies will automatically go to the specialist working on your case.
Sincerely,
John
The Google Wallet Team
On 12/02/12 08:34:43 "SP" <[email protected]> wrote:
I have done all of these steps and recently removed all of my cards from my wallet and reset it again. It is not working on this Nexus 4. I'm sorry if you can look into other things rather than sending me the trouble shooting that I have looked at online. Thank you
Sent from mobile device.
Thanks,
On Nov 27, 2012 6:35 PM, <[email protected]> wrote:
Hello Shawn,
Thanks for your response. Let's try to set a default card to your mobile app.
To change/set your default payment card, follow these steps:
1. Touch the Payment Cards icon from the main menu to go to the payment card carousel.
2. Navigate to the appropriate card by swiping left or right.
3. Touch the Disabled box below the card. The icon will turn green and the words "Default card" will appear, indicating that this is now the default payment card for your Google Wallet mobile app.
Please note that you need a wireless or network connection to change your default card.
If you have other questions, please reply to this email and I'll be happy to help.
Thanks,
John
The Google Wallet Team
On 11/27/12 17:54:30 "SP" <[email protected]> wrote:
I am using the current version.
Sent from mobile device.
Thanks,
On Nov 27, 2012 5:46 PM, <[email protected]> wrote:
Hello ,
Thanks for your response. I'm sorry to hear that the reset did not fix the problem. At this point I suggest we update the version of your Mobile app.
To update Google Wallet, follow these steps:
1. Touch the Home button on your phone.
2. Launch Google Play by touching the Play icon.
3. Touch the Menu button.
4. Touch My Apps.
5. Touch Google Wallet to install the latest version.
Please reply to this email on the results of the troubleshooting.
Thanks,
John
The Google Wallet Team
Weird that the version that comes on the Nexus 4 is newer than the version in the Play Store.
furlonium said:
Weird that the version that comes on the Nexus 4 is newer than the version in the Play Store.
Click to expand...
Click to collapse
the playstore wallet wouldnt work on my tmo n4 sim which came from my gnex which had a working wallet. i had to uninstall clear data cache the playstore wallet and install the 4.2 wallet(stock was gone within 5 minutes of opening the box, hehehe)
well my wallet is working now(still on tmobile) - i dont think my sim was ISIS since my gnex had a working wallet. all the store manager did was cut my regular size sim into a micro. in and out the door in 30 seconds.
Postal Psycho said:
the playstore wallet wouldnt work on my tmo n4 sim which came from my gnex which had a working wallet. i had to uninstall clear data cache the playstore wallet and install the 4.2 wallet(stock was gone within 5 minutes of opening the box, hehehe)
well my wallet is working now(still on tmobile) - i dont think my sim was ISIS since my gnex had a working wallet. all the store manager did was cut my regular size sim into a micro. in and out the door in 30 seconds.
Click to expand...
Click to collapse
TMO store? had no idea they cut sim cards for customers now. Always had the thought that they were just going to replace ur original sim with a microsim
t-mobile used a cutter to cut down my sim for my prepaid plan
i'm wary of wallet because i've had it double-charge me more than once at a register and despite emailing customer support and trying to get resolution on the charges resulted in no communication back
catpunt said:
t-mobile used a cutter to cut down my sim for my prepaid plan
i'm wary of wallet because i've had it double-charge me more than once at a register and despite emailing customer support and trying to get resolution on the charges resulted in no communication back
Click to expand...
Click to collapse
Contact the credit card company and explain your situation to decline being billed if the store is refusing to refund your money.
So I rooted my phone earlier, and the SIM is out. Only connected to my wireless network.
Still stuck at "Setting up Wallet, this may take up to 5 minutes."
It's been at this screen for a good 30 minutes. <--- okay it just FC'd while I was typing that sentence.
I don't know why Wallet worked once and now is seemingly broken. FFS I don't feel like requesting an RMA and waiting 8 weeks for a replacement. Do I get to keep my phone until I get the replacement?
edit: Got off the phone with Google Play support who just transferred me to Wallet support. Couldn't help with my problem and I was told that my issue was escalated and to expect an email within 24 hours. I just want a replacement phone. (Guess I better flash back to stock and lock the bootloader!)
furlonium said:
So I rooted my phone earlier, and the SIM is out. Only connected to my wireless network.
Still stuck at "Setting up Wallet, this may take up to 5 minutes."
It's been at this screen for a good 30 minutes. <--- okay it just FC'd while I was typing that sentence.
I don't know why Wallet worked once and now is seemingly broken. FFS I don't feel like requesting an RMA and waiting 8 weeks for a replacement. Do I get to keep my phone until I get the replacement?
edit: Got off the phone with Google Play support who just transferred me to Wallet support. Couldn't help with my problem and I was told that my issue was escalated and to expect an email within 24 hours. I just want a replacement phone. (Guess I better flash back to stock and lock the bootloader!)
Click to expand...
Click to collapse
Can you beam to another nfc device back and forth? I assumed you cleared the data from the app to start over again?
kpjimmy said:
Can you beam to another nfc device back and forth? I assumed you cleared the data from the app to start over again?
Click to expand...
Click to collapse
Yes Beam works just fine. I can transfer pictures, web pages etc. all back and forth between my N7 and my N4. I've also tried clearing the cache and data. Nothing.
I have a replacement N4 in its way within the week.
Works fine for me. I'm stock and not rooted. I'm using a cut sim card from my galaxy nexus.
Sent from my Nexus 4 using Tapatalk 2
(Incase xda won't show the picture)
SIM card removed
Unable to detect your SIM card. Your device will restart to check for your SIM card
Restart (button)
Anyone else get this error? I can't do ANYTHING when this pops up. Can't pull down my status bar, no where to dismiss the message, can't bring up the app switcher, nothing. Only things i can do is hit the sleep button to turn off the screen or hit restart.
A few months ago, i'd get it maybe once a week. Then it got progressively worse to once a day, a few times a day, then eventually it would pop up 15-20 times a day, making my phone essentially useless. Went to an at&t store, and got a new SIM card, hoping that was the problem. That solved the problem for about a week, and it started getting progressively worse again. I'm now getting this error message about once or twice a day again.
I cracked my screen (not huge, just 2 long cracks) a few weeks after getting the phone back in august, so i'd have to replace the screen ($150 locally) before sending my phone into samsung, so i was hoping there was maybe a more simple fix and the SIM reader wasn't physically bad :-\
At&t Samsung Galaxy S4 32gb stock ROM, fully updated firmware, non rooted (can't figure out how)
The sim card issues Is a know issue. I would have samsung fix the screen and the sim card error.
They should fix the sim card issue under warranty but if you try to do the screen your self they may chard for the repair. Most likely like mine it was the main system board that needed to be replaced.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
shamelin73 said:
The sim card issues Is a know issue. I would have samsung fix the screen and the sim card error.
They should fix the sim card issue under warranty but if you try to do the screen your self they may chard for the repair. Most likely like mine it was the main system board that needed to be replaced.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had my main system board go bad on my s3, and they told me if the screen is cracked, the warranty is automatically void. So i had the glass repaired locally ($130) and then shipped it out to samsung to get looked at. Unfortunatly they completely whiped the entire phone (internal memory) to replace the board, obviously. I'm really hoping they wouldn't have to do that with this phone, since it's just a piece on the board and not the board itself.
Are there any threads that talk about this issue? I'd like to do more research before spending the money to have it repaired
Vinnie_Madrox said:
I had my main system board go bad on my s3, and they told me if the screen is cracked, the warranty is automatically void. So i had the glass repaired locally ($130) and then shipped it out to samsung to get looked at. Unfortunatly they completely whiped the entire phone (internal memory) to replace the board, obviously. I'm really hoping they wouldn't have to do that with this phone, since it's just a piece on the board and not the board itself.
Are there any threads that talk about this issue? I'd like to do more research before spending the money to have it repaired
Click to expand...
Click to collapse
Why not just buy a Sim tray for 10$ and replace it yourself??
SaHiLzZ said:
Why not just buy a Sim tray for 10$ and replace it yourself??
Click to expand...
Click to collapse
because that doesn't fix it nor does a new sim card it's a known Samsung problem and one I've been battling for months I believe it's a software problem that Samsung is aware of. Here's the other thread.
http://forum.xda-developers.com/showthread.php?t=2375982
"No soup for you! Come back one year!!"
Sent from my VisionX ATT SGH-I337 rocking CCC
---------- Post added at 01:06 AM ---------- Previous post was at 01:05 AM ----------
Vinnie_Madrox said:
I had my main system board go bad on my s3, and they told me if the screen is cracked, the warranty is automatically void. So i had the glass repaired locally ($130) and then shipped it out to samsung to get looked at. Unfortunatly they completely whiped the entire phone (internal memory) to replace the board, obviously. I'm really hoping they wouldn't have to do that with this phone, since it's just a piece on the board and not the board itself.
Are there any threads that talk about this issue? I'd like to do more research before spending the money to have it repaired
Click to expand...
Click to collapse
Here's the other thread and I've been fighting this bug for months and so far there's no easy fix I've tried them all
http://forum.xda-developers.com/showthread.php?t=2375982
"No soup for you! Come back one year!!"
Sent from my VisionX ATT SGH-I337 rocking CCC
You can also search for my username here and on android central. I was part of a few threads about this.
I also have a couple threads on AT&T support forums too.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I haven't been able to confirm it yet but I think I might have a solution. I was going to wait a couple of days before posting but then I figured that I can post and collectively we can get a better sample size of data to come to a conclusion. I had long suspected that this was somehow due to location services as the problem first began for me when I downloaded Find my Friends and Glympse. I tried everything under the sun, factory reset, new roms, disable xposed, adding apps back one by one to find the cluprit (over 400!), paper in the sim tray to improve connection, everything!
The other day I had just freshly restored my phone from a Nandroid backup as I had noticed that when first restoring the phone would seem to remain problem free for a couple of days before I started getting the messages again. Well yesterday I was problem free until about 20 minutes after I first downloaded an application from the playstore following the reset. Then it hit me, all the other times the problem starting popping up again was always right after downloading all the of the application updates that piled up since my last backup. Initially I always thought that one of the application being updated was the problem (thus the adding of them one by one!) but in that moment I also realized that my Playstore app on the backup was the older version and would get updated when I made my first download. The problem must be with either The Play Store or Google Play Services! I used my trusty Rom Toolbox to go check the latest update for play services and, sure enough, play services had been updated maybe 5-10 minutes prior to the problem, probably receiving the prompt when I first tried to download something, or in the original cases, when I started the updates!
The Solution!
I froze Google Play Services as a test and low and behold, no pop up for over two days! But Google Play services is so engrained in our phones that suddenly my playstore didn't work, maps was acting wonky, and Google Now wasn't playing nice anymore. So I went back to Rom Toolbox and defrosted Play Service but turned off all location based intents, receivers, and services. Since then I'm almost 1 day error free and haven't seen any adverse effects in maps or navigation resulting in the disabled receivers, intents, or services. The answer seems to have something to do with Google Now's Location services which are constantly pinging your location. I haven't seen this fix recommended anywhere (and I've checked!) so hopefully this helps some of you out. I'd love to hear back about your results one way or the other.
Unfortunately for those of you who are not rooted, this fix does require root access and an root application manager that can manipulate receivers and intents. If you are not rooted you can try deleting the data from play services and removing updates. It may help temporarily but you may end up needing to do it regularly. You can also just disable play services all together if you can do with Google Apps.
Did anyone ever find a solid fix for this? I've been plagued with this problem and would really enjoy a solution.
DKOMofo said:
Did anyone ever find a solid fix for this? I've been plagued with this problem and would really enjoy a solution.
Click to expand...
Click to collapse
The same thing happened to me. Unfortunately for me I had to send it in to sing for it be get fixed. They replaced the pcb board along with many other things that fixed the issue. So if I'd have to say. Call samsung and have them fix it for you. Took a week to get it back.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
androidfine16 said:
The same thing happened to me. Unfortunately for me I had to send it in to sing for it be get fixed. They replaced the pcb board along with many other things that fixed the issue. So if I'd have to say. Call samsung and have them fix it for you. Took a week to get it back.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not an option, I don't have a warranty on the device seeing as it was purchased through a 3rd party. I am very tech savvy and have plenty of resources (tool wise) at my disposal. Just can't figure out what is going on here.
---------- Post added at 08:56 PM ---------- Previous post was at 08:18 PM ----------
DKOMofo said:
Not an option, I don't have a warranty on the device seeing as it was purchased through a 3rd party. I am very tech savvy and have plenty of resources (tool wise) at my disposal. Just can't figure out what is going on here.
Click to expand...
Click to collapse
And it seems as though it expired on August 6th of 2014
There might be a fix here give it a try it couldn't hurt
http://forum.xda-developers.com/showthread.php?t=2375982
"And on that bombshell it's time to end the show!"
Sent from my G900A powered by VisionX Rom Rockin XKRome
DKOMofo said:
Not an option, I don't have a warranty on the device seeing as it was purchased through a 3rd party. I am very tech savvy and have plenty of resources (tool wise) at my disposal. Just can't figure out what is going on here.
---------- Post added at 08:56 PM ---------- Previous post was at 08:18 PM ----------
And it seems as though it expired on August 6th of 2014
Click to expand...
Click to collapse
I bought it through a third party too. From a local cell phone shop. But it wasn't tampered with inside so they gladly fixed it. Of you want I can send you the log report of the fix and you can see what you need to fix in order to get it working again.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 04:59 PM ---------- Previous post was at 04:52 PM ----------
DKOMofo said:
Not an option, I don't have a warranty on the device seeing as it was purchased through a 3rd party. I am very tech savvy and have plenty of resources (tool wise) at my disposal. Just can't figure out what is going on here.
---------- Post added at 08:56 PM ---------- Previous post was at 08:18 PM ----------
And it seems as though it expired on August 6th of 2014
Click to expand...
Click to collapse
I bought it through a third party as well. From a local cellphone guy. I didn't have warranty and they still gladly fixed it for me, bring that the device wasn't water damaged or tampered with. Here's the full log of their documentation of the fix. See if you can find out what exactly to repair.
*10/21/2014//18:17:33//STAFL2240//Telephone//Customer*
1) Inquiry:
Ibrahima Barry
Bps device is Carrier locked after repair.
2) Resources used:
4126952233
Fastlink>Policy>Unlocki
ngsamsungDevices>DeviceLocks
3) Steps taken:
sent phone to us.. Sim would not read... bp received phoneback from RSI... Bp say
s device was unlocked prior to sending it in device is no longer unlocked.. gave unlock code before. advised bp that samsung doesnt
access to unlock codes, and that he will need to speak to the devices cariier AT&T because they are the only people that can provide
carrier unlock assistance for that device.
4) Additional comments/Requirements:N/A
5) Outcome:
Bp disconnected the line
to call AT&T
*10/14/2014//18:41:26//0001773863//Telephone//ASC*
IBI PROCESS
*10/14/2014//18:41:25//0001773863//Telephone//ASC*
10/14/2014 5:40 PM-Monica Angon: The unit is shipped.
*10/14/2014//18:41:24//0001773863//Telephone//ASC*
10/14/2014 5:40 PM-Monica Angon: No hold amount
*10/14/2014//18:30:15//0001773863//Telephone//ASC*
IBI- PROCESS
*10/14/2014//17:42:19//0001773863//Telephone//ASC*
10/14/2014 4:42 PM-Melisa Salinas: QC Pass.
*10/14/2014//08:57:02//0001773863//Telephone//ASC*
10/14/2014 7:56 AM-Liodan Ortega: The unit has left the technician. SOLUTION: Replaced Cosmetic - Replaced Component - Replaced PBA
*10/14/2014//08:55:45//0001773863//Telephone//ASC*
10/14/2014 7:55 AM-Liodan Ortega: The Unit did not pass Quality Assurance Check.
*10/13/2014//12:34:31//0001773863//Telephone//ASC*
10/13/2014 11:34 AM-Liodan Ortega: The unit has left the technician. SOLUTION: Replaced Cosmetic - Replaced Component
*10/13/2014//10:37:11//0001773863//Telephone//ASC*
10/13/2014 9:36 AM-Beatriz Malagon: The unit has been received. Pack Condition: Fair Packaging (Box & Cushion)
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Rocksolid77 said:
I haven't been able to confirm it yet but I think I might have a solution. I was going to wait a couple of days before posting but then I figured that I can post and collectively we can get a better sample size of data to come to a conclusion. I had long suspected that this was somehow due to location services as the problem first began for me when I downloaded Find my Friends and Glympse. I tried everything under the sun, factory reset, new roms, disable xposed, adding apps back one by one to find the cluprit (over 400!), paper in the sim tray to improve connection, everything!
The other day I had just freshly restored my phone from a Nandroid backup as I had noticed that when first restoring the phone would seem to remain problem free for a couple of days before I started getting the messages again. Well yesterday I was problem free until about 20 minutes after I first downloaded an application from the playstore following the reset. Then it hit me, all the other times the problem starting popping up again was always right after downloading all the of the application updates that piled up since my last backup. Initially I always thought that one of the application being updated was the problem (thus the adding of them one by one!) but in that moment I also realized that my Playstore app on the backup was the older version and would get updated when I made my first download. The problem must be with either The Play Store or Google Play Services! I used my trusty Rom Toolbox to go check the latest update for play services and, sure enough, play services had been updated maybe 5-10 minutes prior to the problem, probably receiving the prompt when I first tried to download something, or in the original cases, when I started the updates!
The Solution!
I froze Google Play Services as a test and low and behold, no pop up for over two days! But Google Play services is so engrained in our phones that suddenly my playstore didn't work, maps was acting wonky, and Google Now wasn't playing nice anymore. So I went back to Rom Toolbox and defrosted Play Service but turned off all location based intents, receivers, and services. Since then I'm almost 1 day error free and haven't seen any adverse effects in maps or navigation resulting in the disabled receivers, intents, or services. The answer seems to have something to do with Google Now's Location services which are constantly pinging your location. I haven't seen this fix recommended anywhere (and I've checked!) so hopefully this helps some of you out. I'd love to hear back about your results one way or the other.
Unfortunately for those of you who are not rooted, this fix does require root access and an root application manager that can manipulate receivers and intents. If you are not rooted you can try deleting the data from play services and removing updates. It may help temporarily but you may end up needing to do it regularly. You can also just disable play services all together if you can do with Google Apps.
Click to expand...
Click to collapse
I've been getting the error for a couple of weeks on my stock AT&T GS4. I've had it since release from May 2013 so about 18 months old, and out of warranty. I just recently got the OTA update for 4.4.4 so I thought maybe it had something to do with that but looks like this has been an issue for a while, and not with just the GS4 (or just Samsung phones, but HTC and others also). So your solution made the most sense....something that is common on all the phones would be the Google Play services. After reading, I turned on the location services on my phone and it immediately got the SIM error. So after the reboot, I cleared the data for the Play services and am hoping this will take care of it. Pretty big issue if its caused by Googles apps/services.
Other solution I saw was this: http://forum.xda-developers.com/showpost.php?p=56806072&postcount=238
That is too involved for me to try out so I'm really hoping this Play Services thing will work. But the way he describes the issue is very similar to mine...seems to be the worst when I have the phone in my pocket walking around (although it does happen when the phone is just sitting there on the desk too). I've also noticed its a little better with wifi off.
msheikh25 said:
I've been getting the error for a couple of weeks on my stock AT&T GS4. I've had it since release from May 2013 so about 18 months old, and out of warranty. I just recently got the OTA update for 4.4.4 so I thought maybe it had something to do with that but looks like this has been an issue for a while, and not with just the GS4 (or just Samsung phones, but HTC and others also). So your solution made the most sense....something that is common on all the phones would be the Google Play services. After reading, I turned on the location services on my phone and it immediately got the SIM error. So after the reboot, I cleared the data for the Play services and am hoping this will take care of it. Pretty big issue if its caused by Googles apps/services.
Other solution I saw was this: http://forum.xda-developers.com/showpost.php?p=56806072&postcount=238
That is too involved for me to try out so I'm really hoping this Play Services thing will work. But the way he describes the issue is very similar to mine...seems to be the worst when I have the phone in my pocket walking around (although it does happen when the phone is just sitting there on the desk too). I've also noticed its a little better with wifi off.
Click to expand...
Click to collapse
Hope it works! I ended up getting the messages again anyways though I do find that whenever the message pops up, if I delete Play Services Data it seems to last a little while before the next message. I'm still not totally convinced that it's not a software problem, as you said, it's an issue that happens on a couple of devices though it does seem to be epidemic on the S4. I've since given up on my S4 and just got my OnePlus One today! Personally, I've given up on Samsung. I've been a diehard Samsung fan for many years but my experience with my S4 has totally soured me on them; it's a piece of crap! They're becoming everything I've ever hated about Apple. I'm jumping ship to OnePlus; same specs, half the price. Except the lack of an SD card which really bothers me... But not enough to pay 300 bucks for it!
solved by switching filesystem to f2fs
I have been experiencing 'sim card removed' problem for almost 5months but recently when i switched filesystem from ext4 to f2fs i have not encountered the problem anymore, counting, 3days.
Here's what i did. I just installed cyanogenmod 12 for s4 i9505 by AntaresOne and just followed all steps from the link below including switching from ext4 to f2fs using TWRP. http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934
Im sure that it has nothing to do with changing my rom from touchwiz4.4.2 to cyanogenmod 12[5.0.1 lollipop], which required wiping my data,cache and formatting my system, because i still encountered the problem with new the rom with the existing/default ext4 file system.
This is just pure observation, i cannot explain the mechanism with the use of f2fs in relation with sim card functionality. It has worked for me so far and the cyanogenmod12 in the link works really smooth. Please proceed with caution!
Just started getting this problem last week. Like the rest of the posters in this thread, I've tried a plethora of troubleshooting ideas to no avail. Pretty sure my phone is out of warranty but I will check...but the number of major and minor annoyances experienced with this phone and Samsung as a company ensure that I will never buy a Samsung phone again.
My i717 needed rebooted several times a day because of the SIM Card Removed error. After a few months, my charging port started going and ultimately broke. I've ordered two new ones, but they affect my cell reception, so I'm waiting on a third. Point is, after getting a battery wall charger and re-installing the old charging port board, the SIM Card error has stopped happening. Leads me to believe it has something to do with the charging port or the board it's connected to. Just my two cents.
Could you try liquidsmooth 3.2milestone. I had this issue as well but using this ROM i have no problems? Software vs hardware who knows!!
Sent from my SGH-I337M using Tapatalk 2
Hi,
Have same problem for while,and have tried many thing. In the end, I found that as long as I keep the NFL feature on. The phone seem to be OK. People try it out,hope it work out for you.
Ryan
I've had this issue since last year and posted in this thread back in November 2014 when it first started. Living with this for almost a year but it hasn't been too bad once I realized how it works. Basically every time I have to reboot the phone, the issue starts up. It'll last anywhere from a few days to a week or so but eventually it stops on its own. Those few days can be frustrating because it can literally reboot on you every couple of minutes at times. Obviously you have to reboot your phone every time you get the SIM error, but the trick is not to restart your phone otherwise because you never know which time it will finally be stable. I have gone months without rebooting my phone once I figured this out. Only time I reboot is when its forced because I can't get to a charger in time and the battery dies.
Hi all,
Got a major problem here, so I upgraded the firmware via OTA (no Odin, Kias, etc) and as soon as I unlocked the phone and started the decrypting process as normal the SD card went through the same process.
However, not the card can't be read! It just keeps saying it is being encrypted in the notification bar as normal but doesn't actually complete.
The card is a Samsung 64GB Evo card that I've had for maybe a year or 2 now. Worked perfectly until the firmware update.
Please help!
Really, 50 views and nothing? ...
O and O said:
Really, 50 views and nothing? ...
Click to expand...
Click to collapse
sorry, I do not use my sd slot...
I guess so do many...
Sent from my SM-G935F using XDA-Developers mobile app
Have you tried formatting the card?
The card is detected just that the content is gone. I rather not lose the content to me honest.
Plus, I'm quite concerned that if this could be done via an update rather than factory reset then it should be stated before clicking to update
In my S7E I have a 64GB Samsung Pro microSD formatted and filled of files when it was used in my previous non-Samsung smartphone (also running Marshmallow) and after the update I have no problems at all accessing the microSD content.
Sorry, I think there is some confusion.
I have a SD Card, it was reformatted and only ever since then used in my S7 Edge, since then it has always been encrypted.
Yesterday I updated the version via the normal Google update and somehow the card can't be decrypted anymore. I can be detected but doesn't appear to have content in gallery etc.
Have you tried to connect the microSD to a PC and check the content?
And what about this:
O and O said:
as soon as I unlocked the phone and started the decrypting process as normal the SD card went through the same process.
Click to expand...
Click to collapse
Did you previously encrypt your SD card?
On a computer the content is not viewable.
The card has never been previously encrypted on another phone. Surprisingly for since release day the card was in this phone encrypted no issues working perfectly. Only after yesterday's update did it stop working.
The usual notification of "Encrypting SD Card ..." was what I was referring to. The notification comes up as it always did but this time it doesn't actually allow me to access the content.
O and O said:
The usual notification of "Encrypting SD Card ..." was what I was referring to.
Click to expand...
Click to collapse
I OTA updated yesterday with the microSD still into the S7E and never saw that message after the reboot and also subsequently... maybe others could confirm if they normally see that notifcation...
themissionimpossible said:
I OTA updated yesterday with the microSD still into the S7E and never saw that message after the reboot and also subsequently... maybe others could confirm if they normally see that notifcation...
Click to expand...
Click to collapse
My experience is exactly the same: no msg ab encrypting anything after the OTA update. I suggest to re-format the SD Card
Meh, I guess it's screwed and I've got no choice but to reformat.
O and O said:
Hi all,
Got a major problem here, so I upgraded the firmware via OTA (no Odin, Kias, etc) and as soon as I unlocked the phone and started the decrypting process as normal the SD card went through the same process.
However, not the card can't be read! It just keeps saying it is being encrypted in the notification bar as normal but doesn't actually complete.
The card is a Samsung 64GB Evo card that I've had for maybe a year or 2 now. Worked perfectly until the firmware update.
Please help!
Click to expand...
Click to collapse
I work for Samsung as Costumer Service Support, we had received a lot of reports about this issue, for the moment we recommend a hard reset or wait until a new firmware release.
rayvallejo3k said:
I work for Samsung as Costumer Service Support, we had received a lot of reports about this issue, for the moment we recommend a hard reset or wait until a new firmware release.
Click to expand...
Click to collapse
Thanks, at least I know it wasn't just me.
I've reformatted the card anyway. Which is a major shame, I expect better for what in essence should protect my phone.
Galaxy S7 Edge Encryption/Decryption FAILURE
Experienced the exact same issue on my Galaxy S7 Edge with 64GB Samsung class 10 SDHC card back in March right after buying the phone. Reset, restored, wiped to factory setting. Would work for awhile, then when phone is restarted problem returns. Would have to reformat card and restore to factory before it would work temporarily. Contents of card could be seen when in SD slot on computer or in other phone, but encrypted files (of course) couldn't be opened.
Phone connected to computer and card contents couldn't be seen at all. Notification center shows "Encrypting/Decrypting SD card" all the time until pressed then it disappears, but when in Settings > Storage, portable storage just shows SD card "Ready," but when tapped nothing happens like it's not even mounted.
Called Google, transferred to Samsung. Samsung escalated issue. Update patch was pushed out within a few days. Applied and everything working no problems.
2 months later and everything has been working fine without hiccups, then new update 6.0.1 is released. Waited a day, then applied. Restart phone, same Encryption/Decryption problem returns!
Called Google, transferred to Samsung. Given support run around. Have to demand to escalate to upper level support. Guy says he'll escalatate; call back in a week, hasn't been forwarded. Have to demand to speak to tier 2 support AGAIN explained things at least 3 times and finally get guy to agree to escalate and says he'll send "email." Suggested he recommend engineering consider pushing another update like they had before to correct problem the first time, even gave previous case number. Calls me back in couple days after supposed escalation and says I have to format card and restore to factory. Let him know I wouldn't be doing that, because I've already had to lose too many pictures and documents!
Tried emailing Samsung Executive Customer Support, but haven't heard anything yet and couldn't confirm email. It didn't bounce back as undeliverable, so I'm hoping someone looks into it right away! This is insane! Why offer expandable storage if there's the potential for such a fatal failure. It's eerily critical this gets corrected!
Model: SAMSUNG-SM-G935V
Baseband: G935VVRU2APE1
SD Card: Samsung 64GB Class 10 SDHC
UPDATE: Galaxy S7 Edge Encryption/Decryption FAILURE
Androidlee said:
Experienced the exact same issue on my Galaxy S7 Edge with 64GB Samsung class 10 SDHC card back in March right after buying the phone. Reset, restored, wiped to factory setting. Would work for awhile, then when phone is restarted problem returns. Would have to reformat card and restore to factory before it would work temporarily. Contents of card could be seen when in SD slot on computer or in other phone, but encrypted files (of course) couldn't be opened.
Phone connected to computer and card contents couldn't be seen at all. Notification center shows "Encrypting/Decrypting SD card" all the time until pressed then it disappears, but when in Settings > Storage, portable storage just shows SD card "Ready," but when tapped nothing happens like it's not even mounted.
Called Google, transferred to Samsung. Samsung escalated issue. Update patch was pushed out within a few days. Applied and everything working no problems.
2 months later and everything has been working fine without hiccups, then new update 6.0.1 is released. Waited a day, then applied. Restart phone, same Encryption/Decryption problem returns!
Called Google, transferred to Samsung. Given support run around. Have to demand to escalate to upper level support. Guy says he'll escalatate; call back in a week, hasn't been forwarded. Have to demand to speak to tier 2 support AGAIN explained things at least 3 times and finally get guy to agree to escalate and says he'll send "email." Suggested he recommend engineering consider pushing another update like they had before to correct problem the first time, even gave previous case number. Calls me back in couple days after supposed escalation and says I have to format card and restore to factory. Let him know I wouldn't be doing that, because I've already had to lose too many pictures and documents!
Tried emailing Samsung Executive Customer Support, but haven't heard anything yet and couldn't confirm email. It didn't bounce back as undeliverable, so I'm hoping someone looks into it right away! This is insane! Why offer expandable storage if there's the potential for such a fatal failure. It's eerily critical this gets corrected!
Model: SAMSUNG-SM-G935V
Baseband: G935VVRU2APE1
SD Card: Samsung 64GB Class 10 SDHC
Click to expand...
Click to collapse
Forwarded this discussion to The Office of the President of North America and this was their response:
Thank you for your inquiry. We certainly understand your concern regarding the functionality of your phone and SD card.
Please note, software updates for phones using the Android operating system are produced by Google and distributed by the service provider, such as Verizon, T-Mobile, Sprint or AT&T. However, we will forward your feedback along to the appropriate parties for further review. Unfortunately, we are unable to speculate when/if a new software update may become available, but will provide you with feedback when/if it becomes available.
Thank you,
Samsung Electronics America, Inc.
Phone number: 1-888-987-4357
Fax number: 469-241-4774
resolving sd card not able to decrypt/encrypt
Hi guys,
I've been following up with this thread waiting for an answer but I found something that works for me.
1) Set lock screen security to none, keeping fingerprint data.
2) Start encrypting the sd card AGAIN. It may fail, doesn't matter.
3) Restart phone and it will state SD Card was successfully encrypted.
4) Check your apps/gallery/images which was stored on the SD card. It should be there.
5) Decrypt your SD card.
For now I'll not encrypt the SD card till I'm confident it'll not cause any further problems. You may also wish to keep it encrypted and backing it up offsite.
Hope it works out for you guys.
I'm not able to post external links as I registered solely to inform of the solution. This is the best I can.
Credits to weslexcore:
http: // forums.androidcentral.com/samsung-galaxy-s7/688255-android-sd-card-showing-ready-but-not-usable-applications-not-showing.html
Thanks to you! Worked like a charm!
I won't re-encrypt my SD Card until Samsung addresses the issue.
Just got the phone a few days ago, was super excited as I was tired of using my old 2013 Moto X w/a cracked screen after my iPhone 6 stopped recognizing any SIM card (no service). But I digress....
There was an Android Pie update which I downloaded since I've heard how people enjoyed the phone more with it, plus it was still fresh so I updated. Spent the past few days tweaking things here and there, downloading my usual apps. Excited to try Google Pay via NFC as I was used to Apple Pay (which seems to have more banks supporting it, my Cash App card and my credit union card both don't work on Google Pay but they do on Apple Pay).
Tried it at a Staples earlier with a back to school rush and lines down the entire wall of the store, and it wouldn't work! With the app open or not. Had to pull out my iPhone to finish the transaction (embarassing...).
Got home, tried it again on my Square NFC/chip reader, NOTHING. Read up on how the sensor is on the bottom of the device, no go. Go to Google Pay options, says "to use Google Pay, you need to turn on NFC. Click settings, NFC isn't listed in Connected devices, nor does anything but an NFC Services show up when I search "nf" in the settings app.
I'll be highly disappointed if I can't use Google Pay on this phone. I didn't get a chance to try on Android 8.1 as I updated to Pie pretty much immediately. Help please!?
Press connection services in the connected devices page... That should give you this
kboya said:
Press connection services in the connected devices page... That should give you this
Click to expand...
Click to collapse
Nope, still doesn't show up....this is what I get
What do you get in the nfc service app?
kboya said:
What do you get in the nfc service app?
Click to expand...
Click to collapse
Nothing.
That's the same as mine (which works). For info, I'm on 9.0 (stock original, August), rooted, with adaway and an always on vpn.
Until someone else suggests another fix, I recommend an essential website fastboot reinstall of a full image. That's what I've done every time an I don't have the issues that others report.
kboya said:
That's the same as mine (which works). For info, I'm on 9.0 (stock original, August), rooted, with adaway and an always on vpn.
Until someone else suggests another fix, I recommend an essential website fastboot reinstall of a full image. That's what I've done every time an I don't have the issues that others report.
Click to expand...
Click to collapse
To have to do all of this on a brand new phone (literally got this last saturday) that I already had frustrations with due to Amazon's shipping partner is even more frustrating. Not sure how to do a reinstall. Wonder if amazon or essential would send a replacement phone.
Then return it to Amazon for a replacement! You're within the return period and the longer warranty.
kboya said:
Then return it to Amazon for a replacement! You're within the return period and the longer warranty.
Click to expand...
Click to collapse
In a chat now with them
Good, but I think you should have done that first
kboya said:
Good, but I think you should have done that first
Click to expand...
Click to collapse
True, wasn't sure if it was an issue specific to this copy of the phone or a setting I inadvertently changed. Should be getting a replacement tomorrow so hopefully there aren't any issues - I'll still upgrade to Android 9 Pie if it doesn't have it already. I'll update the thread if so.
Same issue
Fwiw, I'm on a pixel 2 and have the exact same issue after the Pie update. Trying to use a Daydream headset and get the same NFC issues (says it is not enabled, not listed in Connected Devices but running). Hope there's a fix in the pipeline.
Hi folks,
I'm on a stock 6T, not rooted. I use Google Pay on my phone at approximately 5 places routinely. Or at least, I used to...
This week, both terminals at my lunch cafeteria now give me the "Your phone moved too fast" error when I try to use my phone to tap-and-pay. They worked fine last week (both terminals). Never had a single problem at that site, ever, or with the phone anywhere else, ever, in the four months I've had it.
Four other stores I go to and use Google Pay all still work fine. So, it's not a general problem disabling Google Pay that is going on. I figured it was a problem with the terminals at the cafeteria, since I don't see the problem elsewhere.
But, others were able to use those terminals from THEIR phones, just fine. So the cafeteria staff tell me it's something on my end; nothing new happening on their end.
I haven't done anything special to the phone in the last week; it worked fine after the .13 OOS update, for a week or so.
I've tried rebooting the phone shortly before paying. No joy.
What else can I try? I always get the phone moved too fast error at those terminals no matter how fast/slow I move the phone or even if I have the phone next to the terminal already when it activates the NFC reader.
This is driving me nuts.
Help!
curious if OP6T works with gpay and magisk after 16.0.91
Please let's keep this thread on topic, unrooted 6t stock OS, "Phone moved too fast" error. Lots of other threads for other situations.
Sent from my ONEPLUS A6013 using Tapatalk
Did you swap cases? I had that issue in the past where the case was too thick for some terminals.
esjames said:
Did you swap cases? I had that issue in the past where the case was too thick for some terminals.
Click to expand...
Click to collapse
Thanks for the idea. My case has been the same since December so probably is not the problem.
Sent from my ONEPLUS A6013 using Tapatalk
Based on hints elsewhere I tried clearing the Google Pay app's cache, removing the card, clearing the cache again, then re-adding the card back into the app. Despite this process I still encounter the error, specifically at the two terminals in my cafeteria, but not other locations. Others swipe their phones without errors at these locations.
This is a real stumper.
Sent from my ONEPLUS A6013 using Tapatalk
At lunch today I added a MasterCard to Google pay, and was able to use this card to pay at the cafeteria just fine. The card that hasn't been working here is an American Express. That same Amex works fine when used in the chip reader there at the same terminal.
Sent from my ONEPLUS A6013 using Tapatalk
Did an experiment this morning at the cafeteria: since my Amex card has a NFC contactless function, I figured I would try it on the terminals where the Amex in Google Pay doesn't work.
The contactless card failed to read, giving an error on there terminal. I inserted the card to use it in the normal chip manner and the transaction went through.
I will try using the card in contactless fashion at other places and see what happens.
Sent from my ONEPLUS A6013 using Tapatalk