Database Users

Test your GPRS/WAP Connection speed!

http://www.texan.net/speed.htm
Be sure to clear the cache after each use.
I'm getting at 58.3kbps which is 7.1 k on my first try using Cingular GPRS Unlimited.
Second try 51.6kbps 6.5kbytes
Third try 51kbps 6.3 kbytes
Which is correct if I compare it to my SPB GPRS Monitor.
Please don't go off topic and ask question on how to setup the GPRS. Search the forum!

Very high resusts :-/
Strange....
I do the test many times (cleaning cache between test)
I have 136kbps / 16,7 ko/s !!!! (max)
but the average is 102 kbps / 12,5 Ko/s
I'am in France with Orange - GPRS, I put classe 10 in GPRS option.
the result are very hight, but when i use PoketIE the surf seems to be very slow... I want to say that a nokia show html page faster than my QTeK.
Maybe i download quick but the ping is very very bad...
and you ?
Thanks garou

I already have GPRS set up for (only) T-zones for T-mobile US. It only registers 7.6kbps and .9 K bytes/s. How do I clear the cache??? Just refresh?

Hello,
To clear Pocket IE cache.
Open PocketIE
In bottom select "Tools" // "Options" // clic on "delete files" in the bottom part Temporary Internet Files.
You may delete the cookies too, go to "advanced" and clic on "clear cookies".
Good test !
Your result is very low ... be sure that you do nothing else during test (receiving or sending mail, mms, ...)
bye
Garou

Cingular GPRS results
slower than I was expecting: 58.3Kbps / 7.1 K bytes.

vodafone UK result
I just ran the test on Vodafone UK and got 81.6 Kbps (10 K bytes/sec).
But I am currently in a low signal area if that affects the results at all :?:

O2 UK
40.8Kb/sec or 5KB/sec
Typical O2 - slowest of the bunch!
Nigel

T-Mobile USA, Free WAP going through a proxy server:
Class 8 GPRS
58.3 Kbps
7.1 K bytes/sec
Class 10 GPRS
51 Kbps
6.3 K bytes/sec
---
Cable Internet:
4080 Kbps
500 K bytes/sec
I can't wait to have these speeds on my cell

Orange UK
29.1Kb/s
3.6KB/s
Class 8
It always annoys me when they advertise GPRS as fast as dial-up. My experience has been around 60% of the speed. Though I am surprised at some of the speeds others are getting.

Orange NL
102 Kbps
12,5 K bytes / sec

jeeweebee said:
Orange NL
102 Kbps
12,5 K bytes / sec
Click to expand...
Click to collapse
After cleaning cache several times, I get:
Orange NL
Download: 134kbps (16.7K)
(sometimes even 204 kbps = 25K)

O2 Online Pay As You Go
31.4 Kbps (3.8KB/Sec)

FYI: http://www.spbsoftwarehouse.com/products/gprsmonitor/?en

408k/50k on Bluetooth Connection to my PC
Actual phone GPRS with Orange Contract:
68k/8.3k

O2
80.6
10.0 K

Maybe a dumb question, but how do you know what class GPRS you have?

Line speed
4080 Kbps
500K bytes/sec
am i doing it right? i got the same reading after clearing the cache

Spacetel
8.3Kbps
1K bytes/Sec

Sabafon
27.2kbps
3.3k bytes/sec

T-Mobile USA
class 8
45.3/kbps
5.6 bytes/sec
class 10
58.3/kbps
7.1 bytes/sec

[REF]Analysis of build.prop cellular speed tweaks

Introduction:
This thread suggests several build.prop entries that supposedly increase your 3g speeds:
[mod]Boosting Signal Strength (hspa/gprs)
After doing nearly 100 benches with the speedtest app, I have come to a couple conclusions:
The server your connect to for speedtest has the greatest impact on your speeds (network congestion)
The majority of the values given dont even exist by default on the device
Your battery charge might have more influence over speeds then any tweaks
Device defaults:
Code:
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hep=" "
ro.ril.enable.dtm=" "
ro.ril.hsdpa.category=" "
ro.ril.hsupa.category=" "
ro.ril.enable.a53=" "
where " " means that the value isnt defined.
ro.ril.hsxpa: Defines weither to use UMTS, HSPDA/UMTS, or HSDPA/HSPUA respectively.
ro.ril.gprsclass: Defines what class speeds to use with edge. (12 is maximum defined in standard?)
ro.ril.hep: unknown and undefined
ro.ril.enable.dtm: Dual transfer mode (only relevent for EDGE connections, likely always enabled for devices built after 2010)
ro.ril.hsdpa.category: class 8 matches the max download rate
ro.ril.hsupa.category: class 6 matches the max upload rate
ro.ril.enable.a53: supposedly related to GSM security, no actual info (may not even exist)
Anything not listed is completely irrelevent.
Test setup:
PC on wireless-n
Streak 5 on wireless-g
Streak 5 switched to HSPA
ROM: CM7.2-rc0
Kernel: Phoenix kernel for CM7.2
BB: 406-2 (407)
Testing methodology:
Test 5/10 times on control
Make change via terminal and setprop
Enter and exit airplane mode
Do run
Undo mod and do control
Repeat for all
Do again, but make change via build.prop edits
Restart 3 times
Do run
Do control tests
Controls:
PC over landline:
Code:
Ping Down Up
77 2.18 4.8
63 2.11 7.98
97 2.49 5.85
63 3.07 7.6
92 3.26 7.55
49 2.71 7.17
50 2.54 7.49
55 2.8 7.28
65 2.39 7
40 2.51 4.91
Phone over wifi over landline:
Code:
Ping Down Up
90 2.91 7.06
54 3.23 6.53
84 3.38 7.73
72 3.7 9.03
51 4.04 7.62
Phone over 3g while charging:
Code:
Ping Down Up
146 0.45 0.24
786 0.29 0.18
95 0.29 0.23
966 0.28 0.29
114 0.63 0.32
886 0.27 0.15
100 0.27 0.19
837 0.38 0.34
826 0.44 0.51
896 0.21 0.56
ro.ril.hsdpa.category=8
Code:
96 1.58 1.24
106 1.56 1.56
911 1.55 1.35
101 1.96 1.82
916 1.63 1.41
Control after testing above:
Code:
125 0.48 1.01
914 0.27 0.61
110 0.69 0.9
146 0.17 0.18
108 1.1 0.73
ro.ril.hsupa.category=6
Code:
118 0.86 1.45
807 0.73 1.23
116 0.94 1.16
896 0.95 1.12
102 0.93 0.94
Control after testing above:
Code:
778 0.8 1.24
792 0.79 1.36
124 0.75 1.28
828 0.72 1.21
109 0.72 1.31
ro.ril.hsdpa.category=8 and ro.ril.hsupa.category=6
Code:
97 1.16 1.42
932 0.81 1.42
98 0.86 1.41
876 0.88 1.33
829 0.8 1.21
Control after testing above:
Code:
778 0.8 1.24
792 0.79 1.36
124 0.75 1.28
828 0.72 1.21
109 0.72 1.31
ro.ril.hsdpa.category=8 and ro.ril.hsupa.category=6 and ro.ril.hsxpa=5
Code:
126 1.16 1.41
824 0.87 1.08
795 1.08 1.06
127 0.98 1.05
116 0.73 1.18
Control after testing above:
Code:
1019 0.56 1.19
789 0.75 0.64
117 0.46 0.92
895 0.68 1.27
916 0.31 0.46
Conclusion:
A google search shows that ro.ril.enable.a53 may not even exist besides self references to it's own speed tweaks, it may very well not even exist.
The same can be said about ro.ril.hep.
ro.ril.enable.dtm may be irrelevent as DTM allows you to use voice and data at the same time, and this technology only applies to edge.
This is likely implicitly always enabled for any device that supports it past 2010, as only the earliest 3g devices may not have had support for it.
ro.ril.hsxpa=2 and ro.ril.gprsclass=12 are likely already correctly definied for it (with it being a HSPA device)
Bar ro.ril.hsdpa.category=8 and ro.ril.hsupa.category=6, the rest of them are not valid to begin with.
I was able to achieve much higher speeds by switching servers, and all tests were intentionally done on the same server for consistancy.
Those values do canonically exist on other devices, but they're never defined on the S5.
Just as much my speeds varied wildly even from control to control, as much as doubling from the lowest common to highest common.
ro.ril.hsdpa.category and ro.ril.hsupa.category might potentially give an increase in speeds, but as they dont even have default values, they might not even be valid.
I cant even reproduce some of the results from enabling only ro.ril.hsdpa.category=8, as I restart the device after each change to be sure.
I may have inadvertantly connected to a faster server for that one instance.
tl;dr: you get as much speed increases from CHANGING THE THEME ICON TO DISPLAY 4G, you can also make stuff up and pretend it does something and let the placebo effect do all the work for you.
ro.ril.hsdpa.category=8 and ro.ril.hsupa.category=6, might do something, but they could very well be invalid.

thank you, great work
I'll get right on that! I'll make a sticker for my DS5 that says its 4G LTE+ ;P

Thankyou for the thorough testing, now what about vmheap?
Sent from my Dell Streak using Tapatalk 2

I dont intend on testing it, it's default size never changes for any device, regardless of ram size. I assume goog knows what they're doing in respect to that, as manus can and do add in their own optimizations into their roms, and they still leave those values alone more or less.

Nokia Lumia 810 Prototype

Hey guys I currently have a Nokia Lumia 810 Prototype but cannot perform the OTA update. Is there a way to manually update the OS? The specs are identical to my other 810.
Phone
Model: NOKIA RM-878_nam_usa_100
Time: Saturday, March 23, 2013 ● 3:53:56 PM
Time zone: UTC-08
Turned on since: Saturday, March 23, 2013 ● 10:40:08 AM
Operating time: 5 hours, 13 minutes and 47 seconds
Screen resolution: 480 × 800 (scaled)
Display language: English (United States)
Region format: English (United States)
OS version: 8.0.9903.0
.NET CLR version: 4.0.50829.0
Firmware version: 1532.2105.1241.1001
Hardware version: 1.0.0.0
Device ID:
Live ID:
Storage
Total memory: 898.39 MB
Available storage: 4.51 GB
Songs: 0
Number of pictures: 13
Pictures size: 5.19 MB
Music
# Time %
Songs: 0 00:00:00 100.0
Never played: 0 00:00:00 0.0
Rated: 0 00:00:00 0.0
Protected: 0 00:00:00 0.0
Total play count: 0 00:00:00
Genres # Time %
Hardware
Main camera: 8 MP (3,264 × 2,448)
Front camera: 1.2 MP (1,280 × 960)
Compass: Yes
Accelerometer: Yes
Gyroscope: Yes
GPS (Disabled on device)
Location: -
Accuracy (h | v): -
Altitude: -
Speed & course: -
Network
Cellular operator: T-Mobile
Cellular data roaming: No
Data enabled: Yes
Connection interface: WiFi
SSID: INDREMA
Bandwidth capacity: 286.1 Mbps
Ext. IP address:
Local IP address:

If your prototype device has the same hardware as the retail device, you can flash it with the retail firmware.
Of cause there's always a chance of a brick since you are using prototype hardware.
By the way, if your device is not experiencing any crashes/freezes, you are not missing much without Portico.

Constant rebooting when connected to car bluetooth

My S4 constantly reboots (every 10 minutes or so) whenever it is connected to a car bluetooth system. It happens with both a Parrot MKi9100 (fitted to a Mazda 6) and a JVC KD-R811 (fitted to a Honda S2000). I'm running Android 4.4.2 (Phoenix ROM v4.4.2). I've tried wiping the cache partition but it didn't help.
Has anyone else had this problem? Any ideas what I can try to fix it?

Seems like a kernel problem but without a logcat it's impossible to tell. Try a different kernel.

Lennyz1988 said:
Seems like a kernel problem but without a logcat it's impossible to tell. Try a different kernel.
Click to expand...
Click to collapse
I've been trying to reproduce it, with the car in the garage, while running aLogrec, but of course it refuses to reboot after 45 minutes.
I've never reflashed a kernel. Any recommendations for something stable? (I don't need bells and whistles/overclocking etc)

Could be the battery.
Bluetooth causes a little extra power usage. If the battery is shot it might not be able to handle the added load of bluetooth draw.
This has been the cause of reboots when using the torch or the camera before.
Of course this might not be the problem at all. But if you have access to a spare battery, its worth a shot to swap them out and see if it makes a difference.

Skipjacks said:
Could be the battery.
Bluetooth causes a little extra power usage. If the battery is shot it might not be able to handle the added load of bluetooth draw.
This has been the cause of reboots when using the torch or the camera before.
Of course this might not be the problem at all. But if you have access to a spare battery, its worth a shot to swap them out and see if it makes a difference.
Click to expand...
Click to collapse
Coincidentally, I was using my spare battery when I was trying (unsuccessfully) to get it to reboot in the garage. In any case I have now just tried again with the "normal" battery, but after an hour it also wouldn't reboot. In any case, the phone is usually (but not always) connected to the cigarette lighter power source in the car. At one point I thought that that might be the problem, but it still reboots frequently when running off battery.
It seems that the problem only arises while the car is moving. I tried turning off wifi while driving (thinking it might be caused by the phone hunting for wifi connections), but it didn't help. Now I'm running out of ideas.
???

The part where it only happens when moving is weird.
How about if the car is parked but you shake the phone?
I could see if there was something loose in the phone that the road vibrations could trigger it. The first thing I'd suspect is a loose battery. Bit shaking it would prove or disprove that theory real quick.

Skipjacks said:
The part where it only happens when moving is weird.
How about if the car is parked but you shake the phone?
I could see if there was something loose in the phone that the road vibrations could trigger it. The first thing I'd suspect is a loose battery. Bit shaking it would prove or disprove that theory real quick.
Click to expand...
Click to collapse
Hmm...interesting theory....so I just reconnected it to the car in the garage and bumped the phone around., including knocking it quite hard on the steering wheel a few times. It didn't bat an eyelid

Hmmmm....that's a tough one.
I am down to demonic possession as the most likely issue.
Did you try contacting an old priest and a young priest?
Seriously I am completely stumped on this one.
(I know most of xda is a younger crowd. This is a joke from the movie The Exorcist that many of you aren't even aware of)

Skipjacks said:
Hmmmm....that's a tough one.
I am down to demonic possession as the most likely issue.
Did you try contacting an old priest and a young priest?
Seriously I am completely stumped on this one.
(I know most of xda is a younger crowd. This is a joke from the movie The Exorcist that many of you aren't even aware of)
Click to expand...
Click to collapse
The more I analyse it the more your demonic possession theory seems to apply, so I'll see whether CheckaTrade can help with an exorcist.
In the meantime I might investigate trying a different kernel, although I have no idea where to start with that yet....

OK so the phone rebooted in the car while I had aLogRec running (within a few minutes of the phone connecting to the car's bluetooth), and I saved the log output (the last part is below). Can anyone see anything here that might give a clue as to what caused the reboot?
Code:
D/TextLayoutCache( 2679): Enable myanmar Zawgyi converter
D/TextLayoutCache( 2679): Enable myanmar Zawgyi converter
D/SSRMv2:Monitor( 905): SIOP:: AP = 520, Prev AP = 520, Duration = 10026, PST = 519
D/SSRMv2:AmoledAdjustTimer( 905): prevTemp = 297, currTemp = 298, prevStep = 4, currStep = 4
I/ActivityManager( 905): Waited long enough for: ServiceRecord{45216848 u0 com.amazon.venezia/com.amazon.mcc.crashreporter.android.CrashReportService}
D/HeadsetPhoneState( 1823): Signal level : previous=4 curr=4
D/STATUSBAR-NetworkController( 1257): onSignalStrengthsChanged signalStrength=SignalStrength: 24 -1 -1 -1 -1 -1 -1 99 2147483647 2147483647 2147483647 -1 2147483647 gsm|lte 0x4 level=4
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
D/EnterpriseDeviceManager( 905): ContainerId: 0
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
D/AlarmManagerService( 905): Kernel timezone updated to 0 minutes west of GMT
I/ServiceManager( 321): Waiting for service AtCmdFwd...
D/STATUSBAR-NetworkController( 1257): onServiceStateChanged voiceState=0 dataState=0
D/STATUSBAR-NetworkController( 1257): onServiceStateChanged mDataNetType=10
D/STATUSBAR-NetworkController( 1257): getUpdateDataNetType() - mDataNetType:10
D/HeadsetPhoneState( 1823): sendDeviceStateChanged. mService=1 mSignal=4 mRoam=0 mBatteryCharge=5
D/HeadsetStateMachine( 1823): Connected process message: 11
D/PopupuiReceiver(15367): onReceive() getAction : android.intent.action.NETWORK_SET_TIMEZONE
D/PopupuiReceiver(15367): NETWORK_SET_TIME prevMCCvalue : -111
D/PopupuiReceiver(15367): gsm.operator.numeric : 234
D/STATUSBAR-NetworkController( 1257): updateDataNetType()
D/STATUSBAR-NetworkController( 1257): Nothing, mRoamingIconId = 0
D/STATUSBAR-NetworkController( 1257): refreshSignalCluster - setNWBoosterIndicators(false)
D/STATUSBAR-NetworkController( 1257): refreshSignalCluster: data=2 bt=false
E/MP-Decision( 2130): num online cores: 2 reqd : 3 available : 4 rq_depth:3.300000 hotplug_avg_load_dw: 108
E/MP-Decision( 2130): UP cpu:1 core_idx:1 Nw:1.900000 Tw:140 rq:3.300000 seq:0.000000
E/MP-Decision( 2130): UP cpu:2 core_idx:2 Nw:2.700000 Tw:90 rq:3.300000 seq:98.000000
D/PopupuiReceiver(15367): MCC init : mccstrcmp
D/STATUSBAR-AirplaneModeQuickSettingButton( 1257): mPhoneStateListener - inAirplaneMode: false
D/STATUSBAR-IconMerger( 1257): checkOverflow(576), More:false, Req:false Child:6
D/WifiController( 905): SET_AP_BOOSTER_FLAG ignored due to state change
D/HeadsetPhoneState( 1823): sendDeviceDataStateChanged
D/HeadsetStateMachine( 1823): Connected process message: 20
D/WifiService( 905): onDataConnectionStateChanged: state -2, networkType - HSPA
D/STATUSBAR-NetworkController( 1257): onDataConnectionStateChanged: state=2 type=10
D/STATUSBAR-NetworkController( 1257): getUpdateDataNetType() - mDataNetType:10
D/STATUSBAR-NetworkController( 1257): updateDataNetType()
D/STATUSBAR-NetworkController( 1257): Nothing, mRoamingIconId = 0
D/MobileDataStateTracker( 905): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
D/PhoneApp( 1503): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED
D/FileWriteThread( 1503): FileWriteThread : threadType = 2
D/NotificationMgr( 1503): hideDataDisconnectedRoaming()...
I/BootupListener( 1503): mPendingNetworkManualSelection : false
D/MobileDataStateTracker( 905): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
D/StatusChecker(14637): onReceive : android.intent.action.SERVICE_STATE
D/StatusChecker(14637): Service state changed : 0
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
V/AlarmManager( 905): waitForAlarm result :4
I/wpa_supplicant( 1285): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00 SSID=
V/AlarmManager( 905): waitForAlarm result :4
I/wpa_supplicant( 1285): Scan requested (ret=0) - scan timeout 30 seconds
D/Sensorhubs( 293): readContextData: 1, 1, 7, 0
D/SensorHubManager( 905): onGetSensorHubDataLocked: library = 1, 1, 7, 0
D/CAE ( 905): onGetSensorHubData(SensorHubParserProvider.java:69) - onGetSensorHubData Event [event buffer len :4]
I/CAE ( 905): parse(SensorHubParserProvider.java:142) - buffer size = 4
I/CAE ( 905): parse(SensorHubParserProvider.java:153) - 1, 1, 7, 0,
D/CAE ( 905): display(ContextProvider.java:357) - ================= AUTO_ROTATION =================
I/CAE ( 905): display(ContextProvider.java:373) - Angle=[0]
D/SContextService( 905): updateSContext() : event = Auto Rotation
V/WindowOrientationListener( 905): mSContextAutoRotationListener.onSContextChanged, Rotation: 0
E/MP-Decision( 2130): num online cores: 3 reqd : 2 available : 4 rq_depth:0.600000 hotplug_avg_load_dw: 134
E/MP-Decision( 2130): DOWN cpu:2 core_idx:2 Ns:2.100000 Ts:240 rq:0.600000 seq:243.000000
W/EDMNativeHelper( 268): EDMNativeHelperService is published
W/ActivityManager( 905): destPackageName = null
D/HeadsetPhoneState( 1823): Signal level : previous=4 curr=4
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
D/STATUSBAR-NetworkController( 1257): onSignalStrengthsChanged signalStrength=SignalStrength: 24 -1 -1 -1 -1 -1 -1 99 2147483647 2147483647 2147483647 -1 2147483647 gsm|lte 0x4 level=4
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
W/GAV4 ( 2270): Thread[Thread-130,5,main]: Using destination https://ssl.google-analytics.com
D/PowerManagerService( 905): [api] release WakeLock flags=0x3000000a tag=SuperSU Receiver Wakelock uid=10162 pid=14704 (0x0)
D/PowerManagerService( 905): [api] applyWakeLockFlagsOnReleaseLocked : userActivityNoUpdateLocked is called : SCREEN_BRIGHT_WAKE_LOCK 'SuperSU Receiver Wakelock' ACQUIRE_CAUSES_WAKEUP ON_AFTER_RELEASE (uid=10162, pid=14704, ws=null) (elapsedTime=10001)
I/ServiceKeeper( 905): In getpackag

So it seems that the problem is wifi-related. I've taken a few journeys now with wifi disabled, and have had no reboots in over an hour of driving. I guess the reboots are happening as the phone hunts for new wifi signals?
Can anyone suggest anything I can try to fix this? (different kernel, ...?)

tab S2 wifi issue thread

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