So, as you know, MANY tab s2 users are having issues getting Wifi to turn on. In @hga89's case, WiFi was working, and then overnight, it stopped working. Restoring the stock firmware didn't help at all. He managed to get some logs:
Code:
I installed CM 13 from August 21 on the tablet, used SysLog to save the various boot files and then searched for lines containing "wifi". I did find a couple of lines of interest.
In DMESG.LOG, around line 1838 forward:
[ 5.754582] pci_unregister_driver: Enter
[ 5.754645] [c5] dhd_wifi_platform_load_pcie: pcie_register_driver failed
[ 5.754793] [c5] unregister wifi platform drivers
[ 5.754804] [c5] dhd_module_init: Failed to load the driver, try cnt 3
[ 5.754988] [c5] dhdpcie_bus_register: dhdpcie initialize failed.
[ 5.754999] [c5]
[ 5.754999]
[ 5.754999] pci_unregister_driver: Enter
[ 5.755052] [c5] dhd_wifi_platform_load_pcie: pcie_register_driver failed
[ 5.755165] [c5] unregister wifi platform drivers
[ 5.755177] [c5] dhd_module_init: Failed to load the driver, try cnt 2
[ 5.755401] [c5] dhdpcie_bus_register: dhdpcie initialize failed.
[ 5.755410] [c5]
[ 5.755410]
[ 5.755410] pci_unregister_driver: Enter
[ 5.755448] [c5] dhd_wifi_platform_load_pcie: pcie_register_driver failed
[ 5.755565] [c5] unregister wifi platform drivers
[ 5.755577] [c5] dhd_module_init: Failed to load the driver, try cnt 1
[ 5.755740] [c5] dhdpcie_bus_register: dhdpcie initialize failed.
[ 5.755750] [c5]
[ 5.755750]
[ 5.755750] pci_unregister_driver: Enter
[ 5.755797] [c5] dhd_wifi_platform_load_pcie: pcie_register_driver failed
[ 5.755919] [c5] unregister wifi platform drivers
[ 5.755936] [c5] dhd_module_init: Failed to load the driver, try cnt 0
[ 5.755975] [c5] dhd_module_init: Failed to load driver max retry reached**
[ 5.755985] [c5] dhd_module_init out
[ 5.757355] [c5] Freeing unused kernel memory: 1036K (c0d00000 - c0e03000)
[ 5.758053] [c4] init: Service 'wifiloader' (pid 2570) exited with status 0
in LOGCAT.LOG on line 348:
08-24 09:33:35.733 W/PackageParser( 2903): Ignoring duplicate uses-permissions/uses-permissions-sdk-m: android.permission.ACCESS_WIFI_STATE in package: com.android.phone at: Binary XML file line #132
Further down:
08-24 09:33:37.054 D/WifiController( 2903): isAirplaneModeOn = false, isWifiEnabled = false, isScanningAvailable = false
08-24 09:33:37.055 I/WifiService( 2903): Registering wifi
08-24 09:33:37.056 I/SystemServiceManager( 2903): Starting com.android.server.wifi.WifiScanningService
08-24 09:33:37.056 I/WifiScanningService( 2903): Creating wifiscanner
08-24 09:33:37.056 I/WifiScanningService( 2903): Starting wifiscanner
08-24 09:33:37.057 I/SystemServiceManager( 2903): Starting com.android.server.wifi.RttService
And even further down:
08-24 09:33:37.251 D/WifiApConfigStore( 2903): 2G band allowed channels are:1,6,11
Going further down:
08-24 09:33:38.342 D/BluetoothManagerService( 2903): Bluetooth boot completed
08-24 09:33:38.343 I/WifiService( 2903): WifiService starting up with Wi-Fi disabled
08-24 09:33:38.347 I/WifiScanningService( 2903): Registering wifiscanner
And finally:
08-24 09:33:43.750 D/ConnectivityService( 2903): Got NetworkFactory Messenger for WIFI
08-24 09:33:43.750 D/ConnectivityService( 2903): Got NetworkFactory Messenger for WIFI_UT
08-24 09:33:43.750 D/WIFI ( 2903): got request NetworkRequest [ id=1, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 0
08-24 09:33:43.750 D/WIFI_UT ( 2903): got request NetworkRequest [ id=1, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN] ] with score 0
Not sure I am reading the above but it suggests that a driver is missing and possibly some permission mismatch. If correct, perhaps the other messages derive from those?
What do you think?
08-24 09:33:38.349 I/RttService( 2903): Registering rttmanager
@ashyx seemed to think that a hardware failure was possible, but he wasn't quite sure.
By the way, this is from a T810.
THIS ALSO EXPLAINS WHY some people had working WiFi on the CM12.1/CM13 threads and some didn't. (Also the camera...?)
Possible Causes:
Hardware Failure:
Seems likely. This is all off of memory, but according to @ashyx, the wifi driver uses "pcie_register_driver" to do 2 things:
- Initialize the PCIe device (in this case, the WiFi card)
- Initialize the driver (in this case, the WiFi driver)
According to him, the issue is in initializing the PCIe device, which is failing. This could explain the seemingly random issues people are having.
Another cause:
Different hardware revisions
This one actually seems somewhat likely to me. So, what if Samsung, halfway through production, decided to change their WiFi card model? So, people come from their working stock firmware designed for that hwrev, to a custom ROM, which doesn't work with that wifi device, back to the stock firmware, which could have been pulled from a device with a different hwrev. In theory, this would explain 2 things:
- People having WiFi break on a ROM, and restoring to stock doesn't fix the problem
- In the CM thread, I saw some people having a non-working camera/wifi, and some had a working camera/wifi. If the ROM was compiled for one hwrev, this would explain why.
THREADS OF INTEREST
My Lightning ROM thread - this thread is littered with people having broken Wifi, and people with working wifi.
TWRP thread - same story as above.
eMMC backup request thread - This is @hga89's case.
Possibly related thread?
http://forum.xda-developers.com/tab-s2/help/t813-wifi-flash-t3436494 - broken wifi thread
Possible hardware differences?
Wifi dropping randomly
And MANY more that I don't have time to include. Link any more interesting threads.
So, what do you think?
Am I just being crazy here, or is something seriously wrong here?
Please - dump all WiFi issue info here, including logs. I want to get as many logs as I can from different models. You can use Syslog to extract them.
Interesting! However, in my case, even reverting to a TWRP backup I made /before/ installing CM 12.1 did not restore WiFi functionality. I have suspected obsolescence where when a certain date passed, some software stops working although in my case setting the date on the tablet to an earlier date did not work.
Here is my original thread on my WiFi issue: http://forum.xda-developers.com/tab-s2/help/suddenly-lost-wifi-running-cm-12-1-t-810-t3428504
On my t813 I have the same problem. To solve it I swith on flight mode and next wifi on. In this configuration no wifi issue more present.
regards
Grzes
That was among the things I tried but this did not work for me.
I've had strange wifi issues (dropouts, lag for like 30sec at a time) with my 713 tablet. I saw some posts dealing with changing router settings to help the connection with N band in particular.
I've made a few adjustments, which seem to be much more stable now:
- moved N band to be only on 2.4ghz, not shared as mixed mode across both frequencies.
- changed 5ghz to be AC band only on a separate SSID, so I know I'm on it.
- disabled the default wifi on while in sleep mode setting on the tablet
I'm not sure why it is so picky, but the radio and drivers do seem to respond better with AC band and not having the sleep settings.
Sent from my SM-T713 using Tapatalk
I just received my tablet back from Samsung, warranty repair was very quick: I shipped it out on Monday and received it back on Friday. The Service Repair Statement says "charging failure" despite both my call to Samsung Support and the letter accompanying the tablet clearly stated that WiFi could not be turned on...
It seems they replaced both the Main board for a T810 (GH82-10739A), the Main window for a T815(!) (GH81-12965A) and something labeled GH39-01580H lacking description. There was no damage to the Main Window but it did have a screen protector it no longer has...
The unit I returned was model code SM-T810NZKEXAR but the unit returned has model code SM-T810NZKFXAR, the serial number, however, remains the same. Could it be that the change in model code represents the updated stock ROM?
Later today I plan to install TWRP, make a complete backup and again install CM 13 before reinstalling my applications and data.
hga89 said:
I just received my tablet back from Samsung, warranty repair was very quick: I shipped it out on Monday and received it back on Friday. The Service Repair Statement says "charging failure" despite both my call to Samsung Support and the letter accompanying the tablet clearly stated that WiFi could not be turned on...
It seems they replaced both the Main board for a T810 (GH82-10739A), the Main window for a T815(!) (GH81-12965A) and something labeled GH39-01580H lacking description. There was no damage to the Main Window but it did have a screen protector it no longer has...
The unit I returned was model code SM-T810NZKEXAR but the unit returned has model code SM-T810NZKFXAR, the serial number, however, remains the same. Could it be that the change in model code represents the updated stock ROM?
Later today I plan to install TWRP, make a complete backup and again install CM 13 before reinstalling my applications and data.
Click to expand...
Click to collapse
Like I said earlier, MAKE AN EMMC BACKUP before you mess with it. Root it first. how big is your microsd?
Sue them for the lost screen protector
Kidding, they have enough legal troubles with the note 7 for now.
hga89 said:
I just received my tablet back from Samsung, warranty repair was very quick: I shipped it out on Monday and received it back on Friday. The Service Repair Statement says "charging failure" despite both my call to Samsung Support and the letter accompanying the tablet clearly stated that WiFi could not be turned on...
It seems they replaced both the Main board for a T810 (GH82-10739A), the Main window for a T815(!) (GH81-12965A) and something labeled GH39-01580H lacking description. There was no damage to the Main Window but it did have a screen protector it no longer has...
The unit I returned was model code SM-T810NZKEXAR but the unit returned has model code SM-T810NZKFXAR, the serial number, however, remains the same. Could it be that the change in model code represents the updated stock ROM?
Later today I plan to install TWRP, make a complete backup and again install CM 13 before reinstalling my applications and data.
Click to expand...
Click to collapse
where are you from ?
Did your previous device have TWRP or knox0x1 ?
it's nice to see samsung from some country still do warranty.
ayamgoreng said:
where are you from ?
Did your previous device have TWRP or knox0x1 ?
it's nice to see samsung from some country still do warranty.
Click to expand...
Click to collapse
I think he's in the U.S.
His device had knox 0x1 before, but to my knowledge he flashed stock firmware before returning the device.
You will have to wait for him to answer your question for definite answers, though.
Lightn1ng said:
I think he's in the U.S.
His device had knox 0x1 before, but to my knowledge he flashed stock firmware before returning the device.
You will have to wait for him to answer your question for definite answers, though.
Click to expand...
Click to collapse
You are correct and I had flashed the latest stock before returning it. Rest assured, the very first thing I did - after installing TWRP - was to make another backup using TWRP. I did see that it seems to now backup more partitions than when I did my backup in January.
Seems mine is acting up now. I've got the 813 and for the first month and half I had no issues. I'm still running the original stock with root. It starts off with wifi slowing down then completely no throughput. I gotta hit airplane mode and then reenable and it works fine again.
I am having a bit of a problem with my wi-fi. I have a Tab S2 9.7in SM-T810 ROOT. A couple of days ago (Thursday) around 5:40am I have decided for the first time, to turned on airplane mode because it bothered me watching a movie when all of a sudden my movie pauses every time when connected to a network on the train. So later on that day, after work, around 6pm I turned off airplane mode and turned on wi-fi but the problem is the wi-fi is not connecting and stuck on "TURNING ON..." with a faintly dimmed wi-fi icon in the notification bar. Any ideas on how I can correct this?
EDIT (Saturday 10/1): I did a factory reset going into TWRP Recovery hoping that would help but no avail.
On my wifi only 8" tablet, the wifi disconnects and reconnects several times a day. Sometimes it tries to connect to the Xfinity wifi channel rather that my main channel. I just read about the airplane mode trick that has worked for some so I will try that. Running stock marshmallow.
Next day update: Turning on airplane mode seems to have reduced the occurrence of disconnects/reconnects. It's only happened once since I turned airplane mode on. Forgot to mention that on occasion after turning wifi off, it has refused to turn back on. I can move the slider to on and it moves back to off after a couple seconds. When this happens I have to restart the tablet.
Capnk said:
I am having a bit of a problem with my wi-fi. I have a Tab S2 9.7in SM-T810 ROOT. A couple of days ago (Thursday) around 5:40am I have decided for the first time, to turned on airplane mode because it bothered me watching a movie when all of a sudden my movie pauses every time when connected to a network on the train. So later on that day, after work, around 6pm I turned off airplane mode and turned on wi-fi but the problem is the wi-fi is not connecting and stuck on "TURNING ON..." with a faintly dimmed wi-fi icon in the notification bar. Any ideas on how I can correct this?
EDIT (Saturday 10/1): I did a factory reset going into TWRP Recovery hoping that would help but no avail.
Click to expand...
Click to collapse
Same here. Stuck trying to turn on. This is the 3rd time it has done this. The first time it seemed to fix itself after i removed the sim and sd cards and rebooted. The second time it also fixed itself afyer just sitting there on my table for 2 days as i waited for the battery to die. Its been a couple days now since it went out again but i havent checked it. Its very random and odd
Mine has wifi issues (T-813), but its not that it turns off, its that it just doesn't connect to some access points. My home router is fine, but with my phone (ironically a Galaxy S6E+) it just will not stay connected.
Often it wont even see the phone hotspot at all, other times it tries to connect but doesnt, or just keeps dropping the connection. Nothing I do has fixed the problem, and its persisted across different versions of the phone software and tab software. Other devices have no problem with my phone.
I got my SM-T713 last month. I also noticed that the wifi would disconnect and reconnect several times a day (little pop up says it is connecting with network).
I found a simple fix on some other thread. Just go to "Settings", "More connection settings" and turn "Nearby device scanning" to "off". I no longer have the wifi disconnects. When i turn it back on, the disconnects came back.
erase111
Here's my Wifi troubles, and how I fixed them: https://forum.xda-developers.com/showpost.php?p=71890964&postcount=323
Related
Hi guys, I need you to help me with my N4 because as it is said in the title, the wireless connection has left working (since yesterday).
I'll put you in situation: Yesterday just after touching the icon to open the navigator (waze) the device showed an "interference" on the screen and turned off. It was difficult (at least 10 tries before working) to restart the phone, and that interference was again on the screen at the begining of the first seen of the deskboard(you know, the main screen with the widgets and all this kind of things). When I came home 4h after this strange happening I realize that the Wi-Fi didn't work.
This morning I've been trying some things like shutting down the device for around and hour and try again, disabling the NFC or restoring the default settings but no one of these tries has worked so... I'm worried.
The device runs Android 4.2.2, never has been rooted or flashed or something like that.
Can you help me with this trouble?
You can't connect to a wifi network or you can't activate the wifi module?
fruity101079 said:
You can't connect to a wifi network or you can't activate the wifi module?
Click to expand...
Click to collapse
I can't activate the module. Anyway, I've been speaking with Google's support and it is possible that it has been caused by an short-circuit on the mainboard so they're going to change the device for a new one (thanks to the warranty).
Thank you very much for your interest.
Hi,
we have 2 pieces of Samsung Galaxy Xcover 2 phones at work. One is OK, second (tested using same networks), second one has problems with wifi connection. It always reported "authentication error" and asked again for password (I could enter the password 100x times again and again but always got same message). Even factory reset did not solve this.
As it was within the warranty we took it to authorized Samsung service center. They repaired it - said they replaced faulty part "swap unit" and did the factory reset - the protocol contains these items:
1) work - Sasung - Level 2 PBA
2) GH82-07142A - mobile unit
3) GH02-03143A - TAPE ETC-RF SHEET
I tested the phone yesterday and I am still not satisfied - even at home (have wifi router in a room next to mine), the phone reports "Strong" wifi signal but still has problems with connection. After first adding the network and entering the password it connected and worked for some time (no OS upgrade performed) but then reported problems with network and asked for reconnecting (could be "weak signal" it said - but it is nonsense).
Looks like I just had luck first time because after this I was almost unable to connect again - numerous removing and adding the network without success, phone often says that network was saved but does not seem to connect, then asks for password again and again. In fact from about 20 (or more) attempts to connect only 2 ones were successful.
As I do not experience the "authentication error" message now it does not look like the same problem. Do you think there is an other hardware problem or could this be software based?
The phone still has the original stock ROM, no root. Thinking about using Kies - maybe some official update could help.
What do you think?
PS: sorry I wanted to put this in Xcover2 section but for some reason ended in wrong one. May I kindly ask moderator to move this thread there? I am unable to do it thanks
--------------------------------------------------
--------------------------------------------------
Okay I have a Verizon Galaxy Note 3 and I keep having WiFi notification pop-up saying connected it's been doing this for the past year and a half. I have done multiple Factory resets with no luck my phone is all stock not rooted and latest available update
If anybody has a solution to this problem could you please tell me that would be much appreciated thank you....
--------------------------------------------------
--------------------------------------------------
teckynerd6249 said:
--------------------------------------------------
--------------------------------------------------
Okay I have a Verizon Galaxy Note 3 and I keep having WiFi notification pop-up saying connected it's been doing this for the past year and a half. I have done multiple Factory resets with no luck my phone is all stock not rooted and latest available update
If anybody has a solution to this problem could you please tell me that would be much appreciated thank you....
--------------------------------------------------
--------------------------------------------------
Click to expand...
Click to collapse
It's supposed to do that, you can try turning it off by going into WiFi settings, use the bottom menu key to select Advanced, and unchecking the notification. On my Note 3, even though that setting is off, I still get a quick popup showing when it connects.
It should only do it once when it connects to an access point. However if you have it set (also under advanced settings) to turn off WiFi after your phone goes to sleep for a certain period of time, when it wakes it will reconnect, and renotify you.
Sent from my SM-N900V using Tapatalk
donc113 said:
It's supposed to do that, you can try turning it off by going into WiFi settings, use the bottom menu key to select Advanced, and unchecking the notification. On my Note 3, even though that setting is off, I still get a quick popup showing when it connects.
It should only do it once when it connects to an access point. However if you have it set (also under advanced settings) to turn off WiFi after your phone goes to sleep for a certain period of time, when it wakes it will reconnect, and renotify you.
Click to expand...
Click to collapse
I forgot to mention it repeats itself over and over after saying connected annoying already told notification I do know how to disable it but that's not the problem it's repetitive even after saying it's connected on all WiFi networks
One possibility is that your connection actually is bouncing. (Continuously disconnecting/reconnecting)
If that were the case then the frequent messages are appropriate, but symptomatic of some other problem such as hardware (flakey antenna connection?) or a strange software stack incompatibility between your handset and WiFi AP.
(The latter is more likely if you observe the problem only on certain WiFi networks; the former if it happens on all of them)
while [ 1 -eq 1 ] ; do
_res=`ifconfig wlan0 | grep -c 'inet addr'`
if [ $_res -gt 0 ] ; then
echo 'wlan0 UP'
else
echo 'wlan0 DOWN'
fi
done
bftb0 said:
One possibility is that your connection actually is bouncing. (Continuously disconnecting/reconnecting)
If that were the case then the frequent messages are appropriate, but symptomatic of some other problem such as hardware (flakey antenna connection?) or a strange software stack incompatibility between your handset and WiFi AP.
(The latter is more likely if you observe the problem only on certain WiFi networks; the former if it happens on all of them)
while [ 1 -eq 1 ] ; do
_res=`ifconfig wlan0 | grep -c 'inet addr'`
if [ $_res -gt 0 ] ; then
echo 'wlan0 UP'
else
echo 'wlan0 DOWN'
fi
done
Click to expand...
Click to collapse
Thank for the info. It happens on any wifi network im debating on removing the os completely and reinstall it. Any more info would be awesome thanks
Completely useless information but just figured I'd share my story. My father just gave back my old Note 3 and said he was having issues with it. WiFi, WiFi Tether, & GPS were all broke and network connection would drop randomly throughout the day. He was on PL1 or whatever the latest firmware update was. I then flashed back to OB6 firmware which corrected ALL the issues. I let the phone download the OF1 or whatever the next firmware update was and it succeeded with everything still working properly. Overnight the phone downloaded the PL1 or whatever the most recent firmware is, which I updated to that morning. PL1 re-broke EVERYTHING on the phone that I spent a day fixing. I then reflashed OB6 and then rooted and unlocked the bootloader and am downloading an Android 6.0 ROM to try right now. LONG STORY SHORT, the most recent Verizon update SUCKS and breaks the functionality of the phone (at least for me).
teckynerd6249 said:
Thank for the info. It happens on any wifi network im debating on removing the os completely and reinstall it. Any more info would be awesome thanks
Click to expand...
Click to collapse
Try running that script (say in a terminal emulator) I posted in my reply. If you see the wlan0 interface bouncing up and down it suggests a hardware problem (given that you said the symptom is on all WiFi networks).
I suppose it could be software... but until you start digging for more information (e.g. dmesg output or logcat output) or trying some experiments, it's all guesswork at this point.
AntwonJenkins said:
Completely useless information but just figured I'd share my story. My father just gave back my old Note 3 and said he was having issues with it. WiFi, WiFi Tether, & GPS were all broke and network connection would drop randomly throughout the day. He was on PL1 or whatever the latest firmware update was. I then flashed back to OB6 firmware which corrected ALL the issues. I let the phone download the OF1 or whatever the next firmware update was and it succeeded with everything still working properly. Overnight the phone downloaded the PL1 or whatever the most recent firmware is, which I updated to that morning. PL1 re-broke EVERYTHING on the phone that I spent a day fixing. I then reflashed OB6 and then rooted and unlocked the bootloader and am downloading an Android 6.0 ROM to try right now. LONG STORY SHORT, the most recent Verizon update SUCKS and breaks the functionality of the phone (at least for me).
Click to expand...
Click to collapse
The OP failed to report what ROM, modem, or bootloader he is using so it's impossible to determine if were talking apples vs. oranges here.
That said, I am using the PL1 modem (most recent), the AryaMod ROM, and the NC4 bootloader and do not experience the mentioned symptoms. Both WiFi & GPS seem to behave correctly. That would seem to exonerate at least the baseband/modem firmware, but who knows.
Hi,
I just received the Oreo update for my S8 and everything seemed fine from the start. It didnt take long though when
I noticed that the WiFi was acting weird. Even though I had great connection to my modem, my WiFi performance
was extremely poor. The two arrows beside the WiFi logo in the status bar only showed upload and no download when I
tried to open a website. I tried forgeting the network but it only seemed to work momentarily. So I rebooted my modem and
hoped that it would solve the problem. Rebooting the modem only worked momentarily too. I will be checking later if this issue
continues with other WiFi networks.
Has anyone else experienced this?
Same problem with My S8 after Oreo. Occasionally the !-mark next to wifi-symbol and the connecton is lost. By restarting the wifi-router or renewing the wifi connection from the phone fixes this for some time, until it happens again.
This fixed it for me
Mine was doing the same but noticed I could stay connected to a older router I use as an extender so changed my wifi security on my main router from wpa2-aes to the older wpa and it's been fine ever since stays connected on 2.4 and 5 now
Is there a fix for this yet? I just downloaded the newest update they rolled out today, 4/3/2018 and I still cannot send email if I am connected to my wifi. It tells me "couldn't send" and it sits there until I turn off my wifi and use my data. This is ridiculous. My wifi connection is fine. I should not have to turn off wifi every time I want to send an email. So frustrated. Why roll out another update so quickly if not to fix the issues the March update caused????
I am also a an S8 user and noticed my wifi dropping connections throughout the day and reconnecting. This has occurred ever since Oreo update. I have tried all the possible fixes and none of them seem to work. I have sent my phone to Samsung for a repair and they have useless approved centres that lie about fixing the phone. I have sent it back. Lets see what happens. Worst case scenario I will have to install Nougat as it was working fine on this version.
Same here ! =(
Same problem
Sporadic exclamation mark on the WiFi icon
and poor performance .
Opened another thread on too many open ports.
Used sockstat and too many ports are listening.
Me too
(ROM France : XEF)
Did you guys notice this after the Oreo update or on Nougat as well?
I’m having this problem since the Oreo update too. I have to turn the WiFi off and on several times a day to fix it. When attempting to use WiFi, no pages etc will load and then eventually a ! Symbol appears next to the WiFi icon. Only fix is to turn WiFi on and off. It’s very annoying!
Exact same issue. Started occurring right after oreo update
Have you guys complained to Samsung about this? as making noise to them will rectify your faults eventually.
Same here, WiFi unreliable since Oreo. I need to restart the network to make a WiFi call and that isn't always a reliable fix. I started a chat with T-Mob on FB and gave up. They're clueless. Samsung S8+
Hello same issu, I'm from France an online the forum in France an Germany many people have this problem.
I read somewhere to delete the wireless connection from your device and then re-add. I'm not ready to say it fixed things but the WiFi does seem more stable.
UPDATE - Sorry to say there are still issues. Oh well, it gave me hope for a brief moment!
Go to settings- General management- Reset- Reset network settings- Then confirm and restart the phone. After re add your wifi networks. That fixed it for me
Update: It turned out that it didn't work for me... it looks like i may have to try and factory reset as it feels like i have tried everything else :crying:
John_169 said:
Go to settings- General management- Reset- Reset network settings- Then confirm and restart the phone. After re add your wifi networks. That fixed it for me
Click to expand...
Click to collapse
T-Mobile just had be clear the cache from the "boot level" menus. Let me see if that fixes anything before trying yet something further. THANKS!
PS - clearing the cache did fix the problem I was having with the TX Lottery app. After the OREO update it would no longer scan the ticket barcodes. It's working again!
John_169 said:
Go to settings- General management- Reset- Reset network settings- Then confirm and restart the phone. After re add your wifi networks. That fixed it for me
Click to expand...
Click to collapse
Thanks. Let me test a few days.
For me don't work ?
Same for me!!
Hi everyone,
about one year ago I dropped my phone and since than NFC is not working anymore. (I uses NFC in the morning to silence the alarm (Sleep as Android) so I use the NFC feature every day in the morning). The next day after I dropped my phone on the street NFC was not working anymore. I rebooted the phone with no success. When I try to activate NFC in the status bar the icon gets grayed out. And when activate it through the settings menue I see in logcat this
2021-07-08 22:50:09.272 7991-7991/? E/NFC: NFC service dead - attempting to recover
android.os.DeadObjectException
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(BinderProxy.java:511)
at android.nfc.INfcAdapter$Stub$Proxy.enable(INfcAdapter.java:759)
at android.nfc.NfcAdapter.enable(NfcAdapter.java:850)
at com.android.settings.nfc.NfcPreferenceController.setChecked(NfcPreferenceController.java:73)
at com.android.settings.slices.SliceBroadcastReceiver.handleToggleAction(SliceBroadcastReceiver.java:136)
at com.android.settings.slices.SliceBroadcastReceiver.onReceive(SliceBroadcastReceiver.java:75)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:3788)
at android.app.ActivityThread.access$1400(ActivityThread.java:219)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1870)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
2021-07-08 22:50:09.273 7991-7991/? E/NFC: could not retrieve NFC service during service recovery
Click to expand...
Click to collapse
When I adb into my phone and list the services I see this:
127|lucye:/ # service list | more
Found 181 services:
0 com.dolby.DolbyVisionService: [com.dolby.dolbyvisionservice.IDolbyVision]
1 gsiservice: []
2 sip: [android.net.sip.ISipService]
3 dpmservice: [com.qti.dpm.IDpmService]
4 nfc: []
......
Click to expand...
Click to collapse
Today I swapped the NFC module from a spare phone (where I checked that NFC is working) into my phone but also with no luck. NFC is still not working. And my NFC module in the spare phone is working properly.
Does anyone have any idea what could be the problem here? Maybe the loss of NFC function is not related to me dropping my phone but I did not updated the OS in between the 2 attempts to use NFC. I'm on a custom rom (HavocOS) but this should not really made any point because NFC was working with this rom the day before I dropped the phone.
Regards White
*push*