So I got my Nexus 4 yesterday, and I received the consumer update of 4.2. I proceeded to load up Google wallet and it stays on the "setting up wallet, this may take up to 5 minutes." It never loads and I end up just force stopping it. I've tried clearing the data, and restarting the phone and nothing works.
Has any one had any luck or run into this same issue?
djmomar said:
So I got my Nexus 4 yesterday, and I received the consumer update of 4.2. I proceeded to load up Google wallet and it stays on the "setting up wallet, this may take up to 5 minutes." It never loads and I end up just force stopping it. I've tried clearing the data, and restarting the phone and nothing works.
Has any one had any luck or run into this same issue?
Click to expand...
Click to collapse
I setup Google Wallet after downloading the OTA, and again after unlocking and rooting. In both cases, it worked fine, although after rooting you get the message that the device is "unsupported," but it still operates without issue. It did take a few minutes to setup, but it didn't crash.
It took a few minutes for mine to setup, you probably just need to wait a bit longer.
I let it sit for about 10 mins, but I'll try again.
Thanks for replies.
On a side note I've noticed that NFC is eating 23% of my battery. -_-
I suppose this could possibly still be a software bug. I've determined that letting Google Wallet sit open doesn't remedy the original issue. And if I try to back out or force close Wallet and try to go into the "More" menu in Settings to disable NFC it locks up the Settings app. I'll just leave NFC off so it doesn't eat my battery, and hopefully a fix will be made in the upcoming 4.2.1 update.
djmomar said:
I suppose this could possibly still be a software bug. I've determined that letting Google Wallet sit open doesn't remedy the original issue. And if I try to back out or force close Wallet and try to go into the "More" menu in Settings to disable NFC it locks up the Settings app. I'll just leave NFC off so it doesn't eat my battery, and hopefully a fix will be made in the upcoming 4.2.1 update.
Click to expand...
Click to collapse
Go to settings then applications. Clear the data for Google Wallet and try it again.
Stryder5 said:
Go to settings then applications. Clear the data for Google Wallet and try it again.
Click to expand...
Click to collapse
I have. I've tried clearing the data. Disabling the app and restarting the phone. No change.
thanks for the reply though.
djmomar said:
I have. I've tried clearing the data. Disabling the app and restarting the phone. No change.
thanks for the reply though.
Click to expand...
Click to collapse
Yep I have the exact same problem. I have wiped everything, flashed the imgs but nothing works. Settings also's freezes up. I hope there's a fix soon.
djmomar said:
I have. I've tried clearing the data. Disabling the app and restarting the phone. No change.
thanks for the reply though.
Click to expand...
Click to collapse
I had exactly the same problem and I think I found the solve. You should go to wallet.google.com, login your account, go to devices, and disable your Nexus 4. Your Wallet app on the phone will say removing card, and then it goes back to the add account menu. Now on your Wallet app, add your choose your google account again, and you should be able to register the account, and then add your card.
Hope it helps.
Wallet worked fine for me pre-rooting. I made sure to clear the settings / disable device in the Wallet app before rooting. But post-root, I can't get Wallet to add my card. The same card added fine on my Nexus 7 running Paranoid Android 2.99.
The N4 will sit at that "adding card" for 20 min and then error with a "Add card failed. Try again".
The sad thing id the Galaxy Nexus I had before this ended up with the same "add card failed" error which I never resolved. I've had a ticket open with Google Wallet support for 6 weeks, but despite my constant emailing for an update, I haven't heard back.
I thought buying the N4 would finally get around this. Guess not.
jeffreyzf said:
I had exactly the same problem and I think I found the solve. You should go to wallet.google.com, login your account, go to devices, and disable your Nexus 4. Your Wallet app on the phone will say removing card, and then it goes back to the add account menu. Now on your Wallet app, add your choose your google account again, and you should be able to register the account, and then add your card.
Hope it helps.
Click to expand...
Click to collapse
Thanks for the idea. Although since the app on the phone never sets up there isn't any device on the web page. It seems that it really is a bug in the app since my replacement N4 has the same issue.
djmomar said:
Thanks for the idea. Although since the app on the phone never sets up there isn't any device on the web page. It seems that it really is a bug in the app since my replacement N4 has the same issue.
Click to expand...
Click to collapse
I have the same issue. Just spins trying to set up. A friend of mine had the same issue last night but today, it worked fine. Hopefully clears up for us soon.
Ok a question for you guys. If your having problems do you have a Isis t-mobile sim card?
I removed my sim card and it worked and setup just fine. Inserted my sim card and its causing problem with wallet again.
winner00 said:
Ok a question for you guys. If your having problems do you have a Isis t-mobile sim card?
I removed my sim card and it worked and setup just fine. Inserted my sim card and its causing problem with wallet again.
Click to expand...
Click to collapse
Hmm I hadn't considered that possibility. I do have a secure T-Mobile Sim card.
Yes the ISIS Sim cards disable to onboard NFC therefore Google wallet no longer is functional
Sent from my Nexus 4 using Tapatalk 2
Vanhoud said:
Yes the ISIS Sim cards disable to onboard NFC therefore Google wallet no longer is functional
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hmm interesting. So how does Isis work if it relies on the NFC as well?
Went and got a non-Isis sim card and wallet is working fine.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
djmomar said:
Hmm interesting. So how does Isis work if it relies on the NFC as well?
Click to expand...
Click to collapse
They have there own nfc chip on them I believe.
winner00 said:
Went and got a non-Isis sim card and wallet is working fine.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
They have there own nfc chip on them I believe.
Click to expand...
Click to collapse
This kinda explains it...well more why it doesn't work
https://support.t-mobile.com/message/198991?tstart=0&noredirect=true
Sent from my Nexus 7 using Tapatalk 2
---------- Post added at 11:48 PM ---------- Previous post was at 11:45 PM ----------
So I'm guessing you can get the non Isis sim cards from T-Mobile?
Sent from my Nexus 7 using Tapatalk 2
bigbeerdrinker said:
This kinda explains it...well more why it doesn't work
https://support.t-mobile.com/message/198991?tstart=0&noredirect=true
Sent from my Nexus 7 using Tapatalk 2
---------- Post added at 11:48 PM ---------- Previous post was at 11:45 PM ----------
So I'm guessing you can get the non Isis sim cards from T-Mobile?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yea I went in and they traded it with no hassle.
winner00 said:
Yea I went in and they traded it with no hassle.
Click to expand...
Click to collapse
So how do you know without having the phone to test it on if the sim card is an ISIS sim card or not? The reason that I ask is because I just got back from my T-mobile store and asked for a non ISIS sim card and he brought out a micro sim card but couldn't tell me if it was an ISIS card or not. I looked it over and couldn't see any markings that would indicate either way.
I don't have the phone yet (it's ordered) but I'm just trying to get all of my ducks in a row.
Thanks
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
I had a working google wallet on my rooted phone prior to upgrading to MF9, however I just realized that wallet is broken again. I haven't been able to find a solution that works now with my rooted MF9. Anyone have a solution?
DarqAnshin said:
I had a working google wallet on my rooted phone prior to upgrading to MF9, however I just realized that wallet is broken again. I haven't been able to find a solution that works now with my rooted MF9. Anyone have a solution?
Click to expand...
Click to collapse
What happens when you try to use it? Did you try going online and deactivating the device then setting it back up on the phone?
DarqAnshin said:
I had a working google wallet on my rooted phone prior to upgrading to MF9, however I just realized that wallet is broken again. I haven't been able to find a solution that works now with my rooted MF9. Anyone have a solution?
Click to expand...
Click to collapse
I'm on MF9 and rooted, and I can use Google Wallet without issue. All it does is place a little nag bar about your device being unsupported because it's rooted. It still functions, but if you have a problem they technically won't "support" you. If you didn't do a clean install (update to MF9, factory reset), there may be a software issue. Try this if you haven't, in this order. App manager -> Clear cache, delete data, uninstall, go to Market, reinstall.
Darnell0216 said:
I'm on MF9 and rooted, and I can use Google Wallet without issue. All it does is place a little nag bar about your device being unsupported because it's rooted. It still functions, but if you have a problem they technically won't "support" you. If you didn't do a clean install (update to MF9, factory reset), there may be a software issue. Try this if you haven't, in this order. App manager -> Clear cache, delete data, uninstall, go to Market, reinstall.
Click to expand...
Click to collapse
I did do that. It keeps telling me the device is unsupported, but no matter how many times I try waving the over the NFC contact on the reader it does not detect a device transaction. I thought that it may be a a problem with the reader (7-11), so I brought a buddy and had him test it. The reader instantly picked up his unrooted MF9.
Now if I go home, do a factory reset; downgrade; unroot; do a factory reset; OTA MF9; and try it, the device instantly works. The moment I hit with root it states unsupported and then I spend 3 minutes waving my phone like a magic wand over the reader while the guy behind the counter looks at me as if I've lost my mind. Granted he has seen me buy items with the wallet before, but still I would rather figure out what I may be doing wrong that is causing the issue than to just not using it.
DarqAnshin said:
I did do that. It keeps telling me the device is unsupported, but no matter how many times I try waving the over the NFC contact on the reader it does not detect a device transaction. I thought that it may be a a problem with the reader (7-11), so I brought a buddy and had him test it. The reader instantly picked up his unrooted MF9.
Now if I go home, do a factory reset; downgrade; unroot; do a factory reset; OTA MF9; and try it, the device instantly works. The moment I hit with root it states unsupported and then I spend 3 minutes waving my phone like a magic wand over the reader while the guy behind the counter looks at me as if I've lost my mind. Granted he has seen me buy items with the wallet before, but still I would rather figure out what I may be doing wrong that is causing the issue than to just not using it.
Click to expand...
Click to collapse
You're not crazy. I knew I left this thread somewhere. Sometime after the 15th and before the 20th, Google changed rooted MF9 from a nag bar to a full block. I tried to launch Wallet later that evening after that post and was met with the full denial message. I contacted them on Twitter and during trouble shooting they eventually asked about being rooted and I admitted to it, while also noting it worked previously. I am waiting to see if this was an intentional server side change or they cut my support off right here, LoL
I'll have to try mine, I'm rooted stock mf9 and when I start wallet I don't get the unsupported message that I used to see. I'll have to try a purchase and see if I get denied.
cruise350 said:
I'll have to try mine, I'm rooted stock mf9 and when I start wallet I don't get the unsupported message that I used to see. I'll have to try a purchase and see if I get denied.
Click to expand...
Click to collapse
If you get it to launch, you're already one step ahead. This is what you'll see if the app has been fully blocked. I haven't gotten further contact from GoogleWallet. I'm guessing they've cut my support off for rooting, lol.
Darnell0216 said:
If you get it to launch, you're already one step ahead. This is what you'll see if the app has been fully blocked. I haven't gotten further contact from GoogleWallet. I'm guessing they've cut my support off for rooting, lol.
Click to expand...
Click to collapse
That message is because of root. You modded your build prop or something and now your phone is showing up as a phone that isn't supported. Are you running a mod to allow an app from another phone to run?
Sent from my SPH-L720 using Tapatalk 4
It lives!
cruise350 said:
That message is because of root. You modded your build prop or something and now your phone is showing up as a phone that isn't supported. Are you running a mod to allow an app from another phone to run?
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
It worked while rooted before. Just a small banner appeared above a "working" app. I did, however, edit my build.prop to change my 4G symbol to Verizon's 4GLTE because Sprint's is well, ugly. You mean to tell me that little thing pissed off Google Wallet? -_- Great.
...
.....
.......
And just like that Wallet is launching and functional again with the nag bar instead of a full blocking. Thanks for the tip, although I still want to kick Google in the shin for making that 3 letter edit disable the app.
Actually, I'm running that same mod for the Verizon symbols. I can't remember if one of the xposed modules gets rid of the unsupported nag or not since I'm not getting the nag.
Sent from my SPH-L720 using Tapatalk 4
Xposed? Seen the name thrown around but haven't looked into it. Guess now is as good a time as any. And yes, the "4G" irks me that much, lol. Hopefully an update will come along and change the symbol as more LTE locations come online.
(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.
I'm not sure if i ever saw this problem somwhere else and search didn't give any results so i decided to create a new topic. Currently I'm on att galaxy s4 complete stock 4.4.2 NC1 version, rooted. No other mods (like xposed frames ) are installed. So here is the problem. From time to time my network signal gets stuck (so far i noticed that when i have a low signal, 1-2 bars) and no internet or a network signal are available. 4g icon is still there with outgoing signal animation, but that's about it. I can't make calls, can't browse internet and flight mode is not working (network icon won't change to the airplain icon). The only thing that can bring my phone back to being an actual phone and not a tablet is a reboot.
Please ask if any additional information is required to detect the problem.
Thank you.
P.s. sorry for any grammatical mistakes.
Same here but no root. I have gotten a new sim, been on with att tech support and had them do a factory reset and gone so far as to get a replacement device from att but still the same thing. My wife tells me that sometimes her calls go straight to voice mail. I don't know its happening unless i try to do a search or use an app that needs data. A reboot fixes it right up, until it loses connection again. I've been using an app called "att mark the spot" but it's hard to use if you don't have a data connection.
Today i went to the att device support center (not att, a contractor) on Powers Ferry Rd in Atlanta and they did a flash of the rom. They said it replaced the rom from scratch...not just a factory reset. My instructions were to add apps back slowly over time and to read the permissions and not add apps that wanted permissions that i wasn't comfortable with.
We'll see what happens...
Any help would be greatly appreciated.
I thought the recommendation to check the permissions was bunk but as I add apps back I'm finding that it might not have been a bad idea. So far I've added back Google Finance and Pocket Casts and there were no permissions that I thought were over the top. When I got to Yahoo Mail I was shocked at the permissions that they wanted. Maybe I've found the culprit.
---------- Post added at 06:40 AM ---------- Previous post was at 06:35 AM ----------
BTW - last night I rooted with towelroot and installed titanium backup. Time to get rid of some att and samsung bloat and maybe try a rom or 2.
Kevasaki said:
I thought the recommendation to check the permissions was bunk but as I add apps back I'm finding that it might not have been a bad idea. So far I've added back Google Finance and Pocket Casts and there were no permissions that I thought were over the top. When I got to Yahoo Mail I was shocked at the permissions that they wanted. Maybe I've found the culprit.
---------- Post added at 06:40 AM ---------- Previous post was at 06:35 AM ----------
BTW - last night I rooted with towelroot and installed titanium backup. Time to get rid of some att and samsung bloat and maybe try a rom or 2.
Click to expand...
Click to collapse
I got all unnecessary app frozen (like yahoo, att and samsung stuff) so i don't think that problem is in permissions.
P.s. you should check facebook permissions, that's where it gets scary.
So my phone locked up a time or 2 again today and had to be rebooted. The new rom didn't fix the problem. I'm going to put one of the custom roms on and see what that does. Haven't decided which one yet. I still have 45 days left on the 90 day warranty on this replacement device but who cares at this point...
Both my wife and I have unrooted AT&T GS4s and have had the exact same issues ever since the NC1 update was pushed out. We have both gotten updated SIM cards and the problem has not gone away. The only thing that I have found that helps is to reboot in the morning when I wake up and again as I leave work.
Which firmware are you guys using? Since my problems started when NC1 came out I think that is causing the problem.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Kevasaki said:
So my phone locked up a time or 2 again today and had to be rebooted. The new rom didn't fix the problem. I'm going to put one of the custom roms on and see what that does. Haven't decided which one yet. I still have 45 days left on the 90 day warranty on this replacement device but who cares at this point...
Click to expand...
Click to collapse
I had my phone changed yesterday by ATT and as they did it, they told me that some phones have a bad sim card slot. Let's hope that this was a problem. I will try to report everyday if it's acting out again or not.
MikeStroh said:
Both my wife and I have unrooted AT&T GS4s and have had the exact same issues ever since the NC1 update was pushed out. We have both gotten updated SIM cards and the problem has not gone away. The only thing that I have found that helps is to reboot in the morning when I wake up and again as I leave work.
Which firmware are you guys using? Since my problems started when NC1 came out I think that is causing the problem.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Before i went to ATT and re flashed my phone back to NC1, coz i had some GPS problems that i couldn't fix, I had a custom NB1 rom ( i had a few different ones). Before my samsung phone i had LG Thrill 4G, and i faced a similar problem. After an official update to 2.3.5 my phone wouldn't receive any messages or calls, until i unlock the screen. I really do hope they didn't **** up the NC1 update like this and it was just a faulty sim card slot as they told me.
MikeStroh said:
Which firmware are you guys using? Since my problems started when NC1 came out I think that is causing the problem.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
NC1. Maybe thats the problem...the NC1 update. Thanks for posting!
I may try to go back to NB1.
http://forum.xda-developers.com/showthread.php?t=2674223
Ok, I am half way into my night shift at a place where I had these network freezes. I am on a new phone, not rooted, complete nc1 stock. There hasn't been a single incident so far. I'm starting to believe that it was indeed a faulty sim card slot. You might want to try to exchange your phone again. And if they don't believe you, just wait while your network freezes again and bring your phone to the store.
I'll keep reporting for a few nights more.
I upgraded and got this phone on launch day. All in all I'm pretty happy with it. It's definitely a premium phone.
The thing that confuses me, is the 12Gb of RAM and I'm seeing apps like Imgur and Netflix freeze while trying to use them.
The only thing I can think may have been an issue was that I recovered a Google based backup (which was backed up from my OP7Pro) during install.... But that shouldn't affect these apps?
I have deleted these apps. Cleared the apps cache and data. Etc etc
Anyone have any thoughts on a solution? Thanks in advance
@AlphaKoi
Go to display options and switch to 60Hz, see if this problem occurs in these applications. Not all applications are suitable for 90 Hz.
I know that this device was just released but do you guys believe that it will be rootable very soon. Thanks In advance!!!
Sent from my [device_name] using XDA-Developers Legacy app
I read that TMobile replaced the Dual SIM Tray with a single sim tray and locked out dual sim function. Can you confirm?
tivoking said:
I read that TMobile replaced the Dual SIM Tray with a single sim tray and locked out dual sim function. Can you confirm?
Click to expand...
Click to collapse
Yes. There is only one sim card slot.
I hope we can enable dual SIM soon.
I already ordered dual sim tray . Let's see who can come up with firmware changes needed for dual sim
For those following.....I cleared app cache and rebooted. Haven't had any issues since but I will update as necessary
AlphaKoi said:
For those following.....I cleared app cache and rebooted. Haven't had any issues since but I will update as necessary
Click to expand...
Click to collapse
Almost every app freezes followed by a soft reboot. Clearing cache didn't resolve. Trying 60Hz and will report back
---------- Post added at 10:37 PM ---------- Previous post was at 10:01 PM ----------
kemoti said:
@AlphaKoi
Go to display options and switch to 60Hz, see if this problem occurs in these applications. Not all applications are suitable for 90 Hz.
Click to expand...
Click to collapse
Problem solved. I was beginning to fall in love with the 90 Hz display. 60 Hz looks so dull now.
Just to add, I do not have this problem.
i had problems qhen i restored my google backup, like bluetooth didnt want to work, so i just rebooted, might want to reset and try netflix without the backup restore
I would like to add I had some battery issues as well from a brand new out of the box phone and said fudge it, factory wiped.
All issues dissipated.
Anyone of you have the ghost touch issues while charging yet? I got the issue on the 2nd day. happens when using whatsapp mostly.
The only issue I've run into was just out of the box. It would not recognize my SIM card for more than a second. Kept going back and forth between being detected and no SIM. I did a factory reset, and that took care of it. No issues so far, super fast. I came from a 6T, very simple switchover, and I'm definitely loving the Mclaren.
Chrome is crashing every time. I also tried Yuzu browser and that crashed also. Anybody using Chrome can tell me if they had any issues with Chrome?
isildursheir said:
The only issue I've run into was just out of the box. It would not recognize my SIM card for more than a second. Kept going back and forth between being detected and no SIM. I did a factory reset, and that took care of it. No issues so far, super fast. I came from a 6T, very simple switchover, and I'm definitely loving the Mclaren.
Click to expand...
Click to collapse
I had the same issue too, It wouldn't detect any sim card. I that to factory reset the device twice before it eventually detected it.
Mine did not come with screen protector. Is it suppose top come with screen protector installed?
justthefacts said:
Mine did not come with screen protector. Is it suppose top come with screen protector installed?
Click to expand...
Click to collapse
Mine didn't either. The regular OnePlus 7T did. As to your other question about Chrome crashing, I have had no issues with it or Firefox, which is my preferred browser.
justthefacts said:
Chrome is crashing every time. I also tried Yuzu browser and that crashed also. Anybody using Chrome can tell me if they had any issues with Chrome?
Click to expand...
Click to collapse
Haven't had any issues at all.
Sent from my HD1925 using Tapatalk
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
Does anyone know if there is a good Google camera port for this phone yet?
Sent from my HD1925 using Tapatalk
justthefacts said:
Chrome is crashing every time. I also tried Yuzu browser and that crashed also. Anybody using Chrome can tell me if they had any issues with Chrome?
Click to expand...
Click to collapse
Chrome is my main browser and I have 0 issues.
Have you tried clearing chrome cache and data or reinstall?
jonesj198 said:
Does anyone know if there is a good Google camera port for this phone yet?
Click to expand...
Click to collapse
Nothing yet. There's some out there, but none of them are good.