Is anybody facing problems with NFC? I am on pure stock(ASJ2) with no root or something similar.
Is there a solution?
did you try restarting, clearing cache? What problem are you experiencing?
raul6 said:
did you try restarting, clearing cache? What problem are you experiencing?
Click to expand...
Click to collapse
i try everything except hard reset. not working , not even the icon dont appear at status bar
if you go into Settings/Connections do you have NFC and payment ? Do you have Goodlock and QuicStart installed, as the latter be used to hide/display icons?
The NFC icon never shows but it's still working here as long as it's enabled (notification panel or in settings).
raul6 said:
if you go into Settings/Connections do you have NFC and payment ? Do you have Goodlock and QuicStart installed, as the latter be used to hide/display icons?
Click to expand...
Click to collapse
Of course. I am using NFC payments for some years. I know what to do. I used it on my note 8- S9-mate 20 Pro. All working perfectly. Now I have my card linked, NFC, android beam on but still don't work
loizos250 said:
Of course. I am using NFC payments for some years. I know what to do. I used it on my note 8- S9-mate 20 Pro. All working perfectly. Now I have my card linked, NFC, android beam on but still don't work
Click to expand...
Click to collapse
There are only 2 things you can try
1. Do a factory reset
2. You have a hardware defect, and need your unit to get replaces
loizos250 said:
Is anybody facing problems with NFC? I am on pure stock(ASJ2) with no root or something similar.
Is there a solution?
Click to expand...
Click to collapse
I'm exectly in your situation on unrooted asj2 (sm975f)
Used to work before this firmware
SpideRMaN-17 said:
I'm exectly in your situation on unrooted asj2 (sm975f)
Used to work before this firmware
Click to expand...
Click to collapse
The only thing I have done is to unlock OEM. nothing else. I don't know if this is the problem
loizos250 said:
The only thing I have done is to unlock OEM. nothing else. I don't know if this is the problem
Click to expand...
Click to collapse
I did not even unlock OEM (but i believe it has nothing to do with NFC)
Also tried enabling all apps i have disabled but nothing
loizos250 said:
Of course. I am using NFC payments for some years. I know what to do. I used it on my note 8- S9-mate 20 Pro. All working perfectly. Now I have my card linked, NFC, android beam on but still don't work
Click to expand...
Click to collapse
Is android beem still working on yours? (on mine it still works and can pass eg pics frome n10+ to note 4 with no problems) but nothing when tapping an nfc tag
SpideRMaN-17 said:
Is android beem still working on yours? (on mine it still works and can pass eg pics frome n10+ to note 4 with no problems) but nothing when tapping an nfc tag
Click to expand...
Click to collapse
Same to me.
I have the same problem. I used to validate my bus card with an app on my phone, and it worked like magic; but now my phone doesn't recognize the card. I was curious if the problem was the card, so I tried to validate it with an old Galaxy I had lying around (can't remember if S4 or S5) and it worked flawlessly. I have tried a soft reset and wiping the cache to no avail, only thing left is a factory reset. Has anyone tried a factory reset? did it work? what could be causing this problem?
Also, I'm in Latin America. Could this be a lock from my provider company or a regional block?
carlosdayas said:
I have the same problem. I used to validate my bus card with an app on my phone, and it worked like magic; but now my phone doesn't recognize the card. I was curious if the problem was the card, so I tried to validate it with an old Galaxy I had lying around (can't remember if S4 or S5) and it worked flawlessly. I have tried a soft reset and wiping the cache to no avail, only thing left is a factory reset. Has anyone tried a factory reset? did it work? what could be causing this problem?
Also, I'm in Latin America. Could this be a lock from my provider company or a regional block?
Click to expand...
Click to collapse
Same problem here, my bus card is recognised on my note 4 but nothing on my note 10+,never tried a factory reset though
My phone is an unlocked/unrooted SM975F
carlosdayas said:
I have the same problem. I used to validate my bus card with an app on my phone, and it worked like magic; but now my phone doesn't recognize the card. I was curious if the problem was the card, so I tried to validate it with an old Galaxy I had lying around (can't remember if S4 or S5) and it worked flawlessly. I have tried a soft reset and wiping the cache to no avail, only thing left is a factory reset. Has anyone tried a factory reset? did it work? what could be causing this problem?
Also, I'm in Latin America. Could this be a lock from my provider company or a regional block?
Click to expand...
Click to collapse
I try factory reset but nothing. I believe it is software problem
loizos250 said:
I try factory reset but nothing. I believe it is software problem
Click to expand...
Click to collapse
I also tried a variety of nfc tags, which work fine on note 4 but nothing
Samsung, fix it
Any luck for answers on this forum or other venues?
carlosdayas said:
Any luck for answers on this forum or other venues?
Click to expand...
Click to collapse
No luck here, just got the android 10 update 2 days ago and still the same
Activating NFC
On your Android device, tap on “Settings.”Select “Connected devices.”Select “Connection preferences.”You should see “NFC” and “Android Beam” options.Turn both of them on.
I also faced the same problem in using my samsung mote 10. It worked after I tried the above. Give it a try?
Related
I have tried to use Android pay at several locations with no luck at all. Works fine at these locations with my other phones. NFC has been tested and working, just not with Android pay. Called customer service, but they said I should email, so that's what I did.
The phone vibrates as though it is working, but I then get a screen telling me to unlock to use Android pay. Even after using the fingerprint scanner again, it does not work. Android pay was a big reason why I chose this phone, hopefully there will be a fix.
arampapaz said:
I have tried to use Android pay at several locations with no luck at all. Works fine at these locations with my other phones. NFC has been tested and working, just not with Android pay. Called customer service, but they said I should email, so that's what I did.
The phone vibrates as though it is working, but I then get a screen telling me to unlock to use Android pay. Even after using the fingerprint scanner again, it does not work. Android pay was a big reason why I chose this phone, hopefully there will be a fix.
Click to expand...
Click to collapse
Looks the issue was with the fingerprint scanner. Android pay only works with a pin on this phone. Kinda lame.
Update: It does not work with a pin either. Had multiple failed attempts trying to unlock with a pin.
arampapaz said:
Looks the issue was with the fingerprint scanner. Android pay only works with a pin on this phone. Kinda lame.
Update: It does not work with a pin either. Had multiple failed attempts trying to unlock with a pin.
Click to expand...
Click to collapse
yesterday Google had a Android Pay update I have the same phone using Chase Bank cards it works on my blade V8 only after entering the phone unlock pin code then you have to place the phone to the pay terminal again or you can press the power button and unlock your phone pin code before taping the pay terminal fingerprint reader don't work on Android Pay now I already have call ZTE to fix this problem:crying::laugh:
I tried again last night and could not get it to work no matter what I did. Finally took out my card after 5 failed attempts.
arampapaz said:
I tried again last night and could not get it to work no matter what I did. Finally took out my card after 5 failed attempts.
Click to expand...
Click to collapse
Try a MC Donald's or a Duanereade store sometimes that one pay terminal is not working in the store
matthewtech770 said:
Try a MC Donald's or a Duanereade store sometimes that one pay terminal is not working in the store
Click to expand...
Click to collapse
I've tried in lots of locations. Locations where I have successfully used Android pay with other phones. The issue is definitely with this phone. I've had lots of phones and have never had an issue with Android pay with any of them.
arampapaz said:
I've tried in lots of locations. Locations where I have successfully used Android pay with other phones. The issue is definitely with this phone. I've had lots of phones and have never had an issue with Android pay with any of them.
Click to expand...
Click to collapse
:laughK Android operating system can be a monster sometimes strange your phone is not working properly well you can try this before trying to return your phone boot phone into recovery mode holding the volume up + power button and do a factory reset and set up again and see if that works maybe the factory firmware on your phone got corrupted:laugh:
matthewtech770 said:
:laughK Android operating system can be a monster sometimes strange your phone is not working properly well you can try this before trying to return your phone boot phone into recovery mode holding the volume up + power button and do a factory reset and set up again and see if that works maybe the factory firmware on your phone got corrupted:laugh:
Click to expand...
Click to collapse
Thanks for the suggestion, but I had to reset the phone already to fix the DND issue, and android pay didn't work before or after the reset. I am going to try with the Capital One app and see if the issue is with the phone or Android Pay.
Am I the only one having this issue? Does everyone have success with Andrid Pay?
Thanks!
So yesterday I used my phone to pay at 2 terminals with the Capital One app set as my default app and I had success both times. Unlocked with my fingerprint and the payment went through instantly. It appears the issues are with Android Pay and not the phone. I am going to change the default pay app to Android Pay today and see if I have any luck, if not I will stick with the Capital One app.
Mine works
Sounds like the app compatibility was the problem. I have an LG G Stylo that refuses to work in a food store no matter what. My ZTE Blade V8 Pro worked with no problem EVERYWHERE that I went that Accepted Android Pay
Hi,
I have noticed suspicious activity on my google account which shows the device is being used in somewhere in Europe. I changed my password and did a factory wipe on the phone but I still see same behavior on this device being simultaneously being used in Canada and Europe.
Has anyone noticed such behavior from the device and what's your advice on to fix/track the issue?
Thanks
rocky272727 said:
Hi,
I have noticed suspicious activity on my google account which shows the device is being used in somewhere in Europe. I changed my password and did a factory wipe on the phone but I still see same behavior on this device being simultaneously being used in Canada and Europe.
Has anyone noticed such behavior from the device and what's your advice on to fix/track the issue?
Thanks
Click to expand...
Click to collapse
How did you find out what do you go to
stestesteste said:
How did you find out what do you go to
Click to expand...
Click to collapse
Google > Security > Recently used devices - Shows me location and time of the device used last
Mine is doing the same. I'm in the United States. But it shows my phone in China. Weird
CCJ22 said:
Mine is doing the same. I'm in the United States. But it shows my phone in China. Weird
Click to expand...
Click to collapse
Thanks. Anyone who can help with what can be done? Is the phone IMEI clonned?
rocky272727 said:
Thanks. Anyone who can help with what can be done? Is the phone IMEI clonned?
Click to expand...
Click to collapse
No suspicious event with my Google account.
rocky272727 said:
Thanks. Anyone who can help with what can be done? Is the phone IMEI clonned?
Click to expand...
Click to collapse
No problems with mine but I do have two step verification enabled with google - not known if that makes any difference.
I also have the two step verification enabled and didn't get notified by google that my phone was being used in Europe as the same time it was being used in Canada.
I did change my google account passwords but still the same issue.
Post which retailers you got them from if you are having this issue. There may be a common theme ....
Got it from ngp_store_usa from Ebay ebay.ca/usr/ngp_store_usa
rocky272727 said:
Got it from ngp_store_usa from Ebay ebay.ca/usr/ngp_store_usa
Click to expand...
Click to collapse
I think you have your answer. It pays to do a bit of due diligence before buying:
Fairly young account. 97.4% feedback rating which is actually really low.
This gem, also:
Untrustworthy! Sold STOLEN IMEI phone as a good one. Tried to shift blame to me. Buyer: d***s ( 259) During past 6 months
Reply by ngp_store_usa (17-Oct-18 01:46):
BUYER REPORTED PHONE AS STOLEN GOT MONEY FROM INSURANCE AND FROM US! FRAUD BUYER
Follow-up by d***s (17-Oct-18 13:56):
Intentionally malicious or unaware of status of phones he sells. Do not risk it!
Used Huawei P20 Pro (CLT-L04) 128GB/6GB, Black (Noir) Single-SIM Open Accessoris (#173556435227) US $659.00 View Item
I got mine from splendor
SmartPhonesFan said:
Did you had phone factory reset...?
Just wipe phone.. Factory reset..
Don't sing to anything yet after reset phone
Check your stuff emails mainly Google maps sharing etc.. On laptop and change passwords.. Remove all device app links clean your Gmail account/s and then sign in to phone..
Click to expand...
Click to collapse
Thanks will try this option.
CCJ22 said:
I got mine from splendor
Click to expand...
Click to collapse
Have you spoken to them about this? They are *supposed* to be reputable.
Mine was also from Splendor, but I have checked my google connected devices and where they are connected from and have 2 step verification on. My phone is not mysteriously connected elsewhere. I would start looking at 3rd party apps that you guys might have installed.
AngelDeath said:
Mine was also from Splendor, but I have checked my google connected devices and where they are connected from and have 2 step verification on. My phone is not mysteriously connected elsewhere. I would start looking at 3rd party apps that you guys might have installed.
Click to expand...
Click to collapse
I have 2nd step verification enabled as well and removed all 3rd party application which can access my Google account. I haven't noticed anything suspicious recently but will continue to monitor.
Thanks
AngelDeath said:
Mine was also from Splendor, but I have checked my google connected devices and where they are connected from and have 2 step verification on. My phone is not mysteriously connected elsewhere. I would start looking at 3rd party apps that you guys might have installed.
Click to expand...
Click to collapse
Same here...only the one device and all stuff connecting in USA.
rocky272727 said:
Thanks will try this option.
Click to expand...
Click to collapse
wipe the phone mught not be enough, if somehow the seller unlocked, flashed it, and lock the bootloader, the only way to get it clean is doing the same thing: unlocking bootloader and flashing the factory image. that's what i would do, and that's what i always end up doing to root the phone
I'm curious if anyone has tried the 7t on the visible Network by Verizon. I got my Sim in the mail yesterday and there were some issues with the app. The phone recognized the Sim but I could not activate because the app didn't recognize that the Sim was inserted and therefore could not proceed. I currently have a case being worked by visible. I checked my IMEI before ordering the Sim and visible said it was compatible. I'm curious about others experience with visible using the 7T. If anyone else has had a similar experience and has a workaround it would be greatly appreciated.
7T works fine here. Followed their instrutions for provisioning (reboots etc)and works fine. Default voicemail password is 1234.
(My carrier tag on XDA says "Verizon" because there's no Visible tag)
Skripka said:
7T works fine here. Followed their instrutions for provisioning (reboots etc)and works fine. Default voicemail password is 1234.
(My carrier tag on XDA says "Verizon" because there's no Visible tag)
Click to expand...
Click to collapse
I followed the instructions too, just a different result sadly.
khuttha said:
I followed the instructions too, just a different result sadly.
Click to expand...
Click to collapse
One thing I found, was that the Visible SIM fit very loose in the tray--it kept wanting to push itself out as I was closing the tray and needed held in. Barring that--there have been a few app updates--could try rolling back versions via apkmirror etc.
For people whom it works--it is quite great....but people with issues find Visible support generally useless, unfortunately .
Skripka said:
One thing I found, was that the Visible SIM fit very loose in the tray--it kept wanting to push itself out as I was closing the tray and needed held in. Barring that--there have been a few app updates--could try rolling back versions via apkmirror etc.
For people whom it works--it is quite great....but people with issues find Visible support generally useless, unfortunately .
Click to expand...
Click to collapse
Update....I was able to activate on the OnePlus 6t using the app and swap the SIM back to the 7t and it worked. I would have tried this much earlier but visible said they didn't support the 6t.....go figure.
Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.
Tried uninstalling and installing the hp print app, no matter what any time I try to print from any app it crashes? Any ideas? Running the lastest BVA9 Android 12
Can you print from the native Print function? Might be the HP app doesn't work on 12. I have Epson, so can't test it for you.
I'm pretty sure I've tried that with the same result, I've been through so many combinations! I'll remove the hp app and try again just using the android one.
frogdr1ver said:
I'm pretty sure I've tried that with the same result, I've been through so many combinations! I'll remove the hp app and try again just using the android one.
Click to expand...
Click to collapse
Did it work for you?
ButterflyFlutterflyMyOhMy said:
Did it work for you?
Click to expand...
Click to collapse
No it didn't, removed the Samsung print app and the hp print app so only the android stock one left, cleared cache, tried to print and got the same crash
frogdr1ver said:
No it didn't, removed the Samsung print app and the hp print app so only the android stock one left, cleared cache, tried to print and got the same crash
Click to expand...
Click to collapse
That's frustrating! I assume you will trying to print different documents and not just the same one? Sometimes, files get corrupted. I had to help a family member recently who received a PDF from work that somehow always stopped printing at the same page and told the printer the paper was jammed (it was not), no matter how many times it was printed and what device it was printed from. I'd never seen anything like it! I told them to request a brand new scan of the document.
Yep it's a pain in the ass alright, I don't even get as far as printing, whenever I ask it to print anything using any app it has a think then crashes.
frogdr1ver said:
Yep it's a pain in the ass alright, I don't even get as far as printing, whenever I ask it to print anything using any app it has a think then crashes.
Click to expand...
Click to collapse
That sucks. You haven't disabled any services that would affect printing? Have you tried clearing cache and data for the print service? Were you ever able to print with this phone, or did it happen after the update or installing an app or?
I've not had the phone long tbh, I think this is the first time I've tried to print. Don't think I've disabled anything, and not sure what to look for there. Cleared cache on the apps, and on the phone.
frogdr1ver said:
I've not had the phone long tbh, I think this is the first time I've tried to print. Don't think I've disabled anything, and not sure what to look for there. Cleared cache on the apps, and on the phone.
Click to expand...
Click to collapse
Okay. Have you Googled the problem to see if anyone else had a solution? I did that the other day when my Always-On calendar suddenly was on the wrong date (happened after keeping the phone in battery-saving mode during a two-day power outage), and found the solution from years ago where going into the Samsung calendar app (which I don't use) and telling it to lock the time zone worked.
Yeah that was the first port of call, tried a few things and nothing made a difference. I'll keep fiddling away