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.
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
Hello!
I have LG Spirit 4G LTE H440N
Location is not working, when I turn off data or not being registered in any network after update to v6.0.1. With v5.0.1 things were kind of fine, laggy sometimes, but overall it was working and now with the same apps with preloaded maps it doesn't work at all. Here's what I've done:
- GPS test app locates good amount of satellites "In View" instantly, but it's always 0 "In Use" with no fix;
- This phone was already two times in warranty repairs (both only because of the problem described here), both times HW was changed. First time they changed some part, don't know what that was, but second time it was mainboard, I have a different IMEI now. Warranty is still ON.
- Tried to use GPS in offline with Samsung Galaxy phone, and it works there on Marshmallow.
Can anyone suggest a solution?
I been using NFC for mobile payment via Optus Pay which is a NFC enable SIM which integrates with the phone's NFC antenna; this worked most of the time. I also use NFC with Yubikey Authenticate and OpenKeychain and while getting the right spot for the antenna to pick up, it always worked.
I recently changed my battery and noticed that my nfc reception has weaken significantly. Thinking that it was a dodgy battery I've put the old battery back in my phone but I'm still getting weak or no signal. I know there have been several firmware updates and I'm wondering if anyone else has been noticing problems? I particularly trying to use Android Pay but Yubikey Authenticate and OpenKeychain have stopped working (being able to read my YubiKey Neo).
Regards
John
Samsung Galaxy S5
SM-G900i
Android 6.0.1
Build number: MMB29M.G900IZTU1CPK2
Kernal version 3.4.0-9647621
Factory reset didn't help
I just factory reset the phone and installed Yubikey Authenticator and it still cannot read it. While I know the Yubikey is working, I have no way testing the NFC other than with this device.
John.
I have this problem on a S9 after changing battery nfc started working weak also
Hi everyone,
I've got an Junsun V1 Pro head unit with the latest firmware (8259P_军灿UI02v1280x720-国外_v50_20221226) installed in my car. Now I‘m facing an issue with my sim card for the car. When I install the sim card the first time everything works as expected. Internet is working and connection is 4G (even VoLTE). But when I turn on the head unit after standby, the connection is reestablished only with 2G (at the exact same location). The sim card is from sim.de and is operating in the O2 network and as multi card.
Tested with klarmobile sim card (Vodafone network): Every time 4G
Tested sim.de sim card in Huawei Gigacube: No problems
Checked and adjusted APN settings: No effect
Disabled VoLTE: No effect
Changed setting between 2G / 3G / 4G: No effect
Are there any known issues with Junsun and the O2 network?
kind regards
Markus
the_moom said:
Hi everyone,
I've got an Junsun V1 Pro head unit with the latest firmware (8259P_军灿UI02v1280x720-国外_v50_20221226) installed in my car. Now I‘m facing an issue with my sim card for the car. When I install the sim card the first time everything works as expected. Internet is working and connection is 4G (even VoLTE). But when I turn on the head unit after standby, the connection is reestablished only with 2G (at the exact same location). The sim card is from sim.de and is operating in the O2 network and as multi card.
Tested with klarmobile sim card (Vodafone network): Every time 4G
Tested sim.de sim card in Huawei Gigacube: No problems
Checked and adjusted APN settings: No effect
Disabled VoLTE: No effect
Changed setting between 2G / 3G / 4G: No effect
Are there any known issues with Junsun and the O2 network?
kind regards
Markus
Click to expand...
Click to collapse
I'm using the same firmware and today I ordered an O2 SIM. I will let you know if I will run into the same problem.
You could try after sleep mode:
Disable and enable mobile data.
Enable and disable flight mode (maybe via search function in settings app).
Does it help to bring 4G back?
TorstenH said:
You could try after sleep mode:
Disable and enable mobile data.
Enable and disable flight mode (maybe via search function in settings app).
Does it help to bring 4G back?
Click to expand...
Click to collapse
No, unfortunately not.
Yesterday I tried to increase the pressure on the sim and added a small piece of cardboard. It worked the whole evening, even after standby. But today it stopped and is back to 2G.
the_moom said:
No, unfortunately not.
Yesterday I tried to increase the pressure on the sim and added a small piece of cardboard. It worked the whole evening, even after standby. But today it stopped and is back to 2G.
Click to expand...
Click to collapse
Unfortunately my SIM card still not arrived so I can't tell you if it works on my device / with my O2 SIM.
I can't imagine that it's a topic of bad electronically contact because the issue only occurs after sleep mode.
One possibly could be to compare the units processes before and after sleep mode.
1. Stop all apps to avoid unneeded programs occure in the list
2. List all processes running
3. Put the unit in sleep mode and wake it up
4. If you only have 2G list all running processes again
Maybe a service doesn't comes up after sleep mode which is relevant for 4G data connection.
I added the SIM card today and two reboots were required to get 4G.
I put the device into sleep mode (just a few minutes) and had still 4G.
Let's see how it is after a long sleep...
TorstenH said:
I added the SIM card today and two reboots were required to get 4G.
I put the device into sleep mode (just a few minutes) and had still 4G.
Let's see how it is after a long sleep...
Click to expand...
Click to collapse
Does it work?
the_moom said:
Does it work?
Click to expand...
Click to collapse
It works (not always).
This morning after wakeup the head unit displayed "no sim card" on the bottom of the mobile data icon in status bar.
After reboot it worked fine, so it was not a contact problem of the sim card holder...
I found this:
Post in thread 'Auto-toggle SIM card (e.g. with Tasker, adb shell)' https://forum.xda-developers.com/t/...g-with-tasker-adb-shell.3656963/post-73482775
This may be an approach to disable/enable the Sim. If you're willing to test I can write a small app doing the job.
After serveral days usage I have exactly the same issue:
After (longer) sleep only EDGE or even message "no Sim".
Changing mobile data settings or changing to flight mode not bringing back 4G. Reboot is the only way to get 4G again.
I don't think it's hardware related because it works after reboot without touching the Sim card dongle.
I will investigate the Android log. @the_moom you may want to do the same?! Four eyes may see more that two.
I compared the running system services after sleep and after reboot. Found no difference...
So next step is to check logcat...
It may help to restart the RIL daemon...
adb shell stop ril-daemon
adb shell start ril-daemon
I will test this tomorrow...
TorstenH said:
It may help to restart the RIL daemon...
adb shell stop ril-daemon
adb shell start ril-daemon
I will test this tomorrow...
Click to expand...
Click to collapse
Restart of vendor.ril-daemon-mtk isn't sufficient.
Is the SIM protected by PIN?
le_mi said:
Is the SIM protected by PIN?
Click to expand...
Click to collapse
I switched off the "pin required" setting. Or is there are way to remove the pin from the card?
TorstenH said:
I switched off the "pin required" setting. Or is there are way to remove the pin from the card?
Click to expand...
Click to collapse
I had put the SIM in the smartphone at the beginning and disabled the PIN.
le_mi said:
I had put the SIM in the smartphone at the beginning and disabled the PIN.
Click to expand...
Click to collapse
As it's done in this video? Or is there another way?
TorstenH said:
As it's done in this video? Or is there another way?
Click to expand...
Click to collapse
Correct in this way.
le_mi said:
Correct in this way.
Click to expand...
Click to collapse
I used this setting - but directly on the head unit.
TorstenH said:
I used this setting - but directly on the head unit.
Click to expand...
Click to collapse
Well then i think this is not the reason for the issue.