Related
Hey all.
I've had my atrix since before we got our BL unlocked. I've been following the scene and flashing with no problems for a long time.
After flashing "insert rom name here", a CM7 based rom, my wifi has stopped working. It is a known serious issue where the atrix wifi says "error" when you try to even turn it on. It doesn't activate at all. As soon as you tap it, it says error, and unchecks the wifi box. Paired with that is the fact that it reboots once every five minutes. I've tried everything to fix it(other roms, lots of different flashing methods and whatnot), and nothing has worked.
****ty part is, this is actually the first time I flashed without a backup. I wasn't planning on flashing another rom for a very long time.
What I'm asking from you guys is some help. It is a bell atrix, BL unlocked, custom recovery, all that jazz.
I don't know where to go from here. Is there any way one of you guys could send me a nandroid backup of your own? I don't want to resort to flashing .sbf as I will then lose my unlocked BL. I suspect that it is a software issue as it reboots every god damn 5 minutes. If you guys have a better suggestion I'm all ears.
Magnetox said:
Hey all.
I've had my atrix since before we got our BL unlocked. I've been following the scene and flashing with no problems for a long time.
After flashing "insert rom name here", a CM7 based rom, my wifi has stopped working. It is a known serious issue where the atrix wifi says "error" when you try to even turn it on. It doesn't activate at all. As soon as you tap it, it says error, and unchecks the wifi box. Paired with that is the fact that it reboots once every five minutes. I've tried everything to fix it(other roms, lots of different flashing methods and whatnot), and nothing has worked.
****ty part is, this is actually the first time I flashed without a backup. I wasn't planning on flashing another rom for a very long time.
What I'm asking from you guys is some help. It is a bell atrix, BL unlocked, custom recovery, all that jazz.
I don't know where to go from here. Is there any way one of you guys could send me a nandroid backup of your own? I don't want to resort to flashing .sbf as I will then lose my unlocked BL. I suspect that it is a software issue as it reboots every god damn 5 minutes. If you guys have a better suggestion I'm all ears.
Click to expand...
Click to collapse
As you're having lots of reboots have you tried a factory reset/dalvik wipe first? If that fails then a fresh install of the Rom (either fastboot or CM recovery methods) that you're having issues with. Also, another thing I would try is to 'forget' your wifi settings, turn wifi on/off at the mains and then try again.
I know you've tried lots of different flashing methods (and not forgetting the 'whatnots' as well!) but I'm just wondering what you'd think about installing another rom (either go for CM 7.2 or a CM9/10 one) with a full system wipe (format data,system.osh.preinstall and cache before flashing) and see where you go from there.
Magnetox said:
Hey all.
I've had my atrix since before we got our BL unlocked. I've been following the scene and flashing with no problems for a long time.
After flashing "insert rom name here", a CM7 based rom, my wifi has stopped working. It is a known serious issue where the atrix wifi says "error" when you try to even turn it on. It doesn't activate at all. As soon as you tap it, it says error, and unchecks the wifi box. Paired with that is the fact that it reboots once every five minutes. I've tried everything to fix it(other roms, lots of different flashing methods and whatnot), and nothing has worked.
****ty part is, this is actually the first time I flashed without a backup. I wasn't planning on flashing another rom for a very long time.
What I'm asking from you guys is some help. It is a bell atrix, BL unlocked, custom recovery, all that jazz.
I don't know where to go from here. Is there any way one of you guys could send me a nandroid backup of your own? I don't want to resort to flashing .sbf as I will then lose my unlocked BL. I suspect that it is a software issue as it reboots every god damn 5 minutes. If you guys have a better suggestion I'm all ears.
Click to expand...
Click to collapse
Remove the /system/lib/modules/dhd.ko. This is the wifi kernel module, if your reboots are related to wifi, your phone will not reboot anymore. Try to look logcat and dmesg.
Unfortunately, I think your wifi/BT module may have died.
http://forum.xda-developers.com/showthread.php?t=1946667
barry_ said:
As you're having lots of reboots have you tried a factory reset/dalvik wipe first? If that fails then a fresh install of the Rom (either fastboot or CM recovery methods) that you're having issues with. Also, another thing I would try is to 'forget' your wifi settings, turn wifi on/off at the mains and then try again.
I know you've tried lots of different flashing methods (and not forgetting the 'whatnots' as well!) but I'm just wondering what you'd think about installing another rom (either go for CM 7.2 or a CM9/10 one) with a full system wipe (format data,system.osh.preinstall and cache before flashing) and see where you go from there.
Click to expand...
Click to collapse
Yes of course, i've tried all of these things. I will try a full fastboot wipe if the other suggestions don't work, but I have tried all of those steps.
epinter said:
Remove the /system/lib/modules/dhd.ko. This is the wifi kernel module, if your reboots are related to wifi, your phone will not reboot anymore. Try to look logcat and dmesg.
Click to expand...
Click to collapse
Cheers, will try this and will update. Will post logcat later if it still is not working. Do you know what the BT kernel module is too?
upndwn4par said:
Unfortunately, I think your wifi/BT module may have died.
http://forum.xda-developers.com/showthread.php?t=1946667
Click to expand...
Click to collapse
Yep, I looked at this already. I do think this might be the case, but what I'm trying to fix right now is the reboots every 5 minutes. I'm ok without my wifi as long as everything else works properly.
Edit: did not find the tool page before, nvm and thanks!
Ok here is logcat AFTER deleting wifi driver dhd.ko(during logcat I tried turning wifi and BT on). Seems like reboots are fixed (for now).
I will try a full fastboot wipe (preinstall , boot, radio, system, etc.) and then reflash and post a new logcat BEFORE deleting wifi driver. I will then delete the driver to keep my phone from rebooting.
Here is a portion from it:
02-20 14:00:27.995 1599 1849 I WifiService: setWifiEnabled enable=true, persist=true, pid=2307, uid=1000
02-20 14:00:28.005 1599 1688 E WifiService: Failed to load Wi-Fi driver.
02-20 14:00:28.015 1719 1719 E WifiSettingButton: onReceive()-S:2
02-20 14:00:28.045 1719 1719 E WifiSettingButton: onReceive()-S:4
02-20 14:00:28.075 5708 5708 I WifiToggle: OnReceive
02-20 14:00:28.075 5708 5708 I WifiToggle: getServiceState.INTERMEDIATE_STATE
02-20 14:00:28.075 5708 5708 I WifiToggle: UpdateWidget - currentState=INTERMEDIATE_STATE
02-20 14:00:28.075 5708 5708 I WifiToggle: updateButtons
02-20 14:00:28.085 5717 5717 I HomeSyncReceiver: onReceive. WifiState= 2
02-20 14:00:28.115 5708 5708 I WifiToggle: OnReceive
02-20 14:00:28.125 1599 2306 W libgps : recv_command_nmea_gsa() : missing GSV command(s) since last GSA
02-20 14:00:28.125 5708 5708 I WifiToggle: getServiceState.INTERMEDIATE_STATE
02-20 14:00:28.125 5708 5708 I WifiToggle: UpdateWidget - currentState=INTERMEDIATE_STATE
02-20 14:00:28.125 5708 5708 I WifiToggle: updateButtons
02-20 14:00:28.125 5717 5717 I HomeSyncReceiver: onReceive. WifiState= 4
02-20 14:00:28.395 1599 2306 E libgps : recv_command_status() : fix returned error code 15
02-20 14:00:28.395 1599 2306 E libgps : numsats histogram: 0,1,57,95,73,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
02-20 14:00:28.395 1599 2306 E libgps : sats histogram: 0,0,0,0,0,0,0,0,0,0,0,0,0,225,131,0,0,110,0,0,0,226,0,0,0,0,0,0,0,0,0,0
02-20 14:00:29.715 1599 1816 D BluetoothService: Bootcompleted so turning on Bluetooth
02-20 14:00:29.715 1599 1816 D BluetoothService: Bluetooth state 10 -> 11
02-20 14:00:29.735 1719 1719 E BluetoothSettingButton: onReceive()-S:11
02-20 14:00:29.805 2307 2307 V BluetoothEventRedirector: Received android.bluetooth.adapter.action.STATE_CHANGED
02-20 14:00:29.875 1599 1849 I ActivityManager: Start proc com.android.bluetooth for broadcast com.android.bluetooth/.opp.BluetoothOppReceiver: pid=5815 uid=10027 gids={3003, 3002, 3001, 1015}
02-20 14:00:29.945 1440 1440 D dalvikvm: GC_EXPLICIT freed 11K, 50% free 2599K/5123K, external 2357K/2773K, paused 63ms
02-20 14:00:30.015 1440 1440 D dalvikvm: GC_EXPLICIT freed <1K, 50% free 2599K/5123K, external 2357K/2773K, paused 41ms
02-20 14:00:30.055 1440 1440 D dalvikvm: GC_EXPLICIT freed <1K, 50% free 2599K/5123K, external 2357K/2773K, paused 41ms
02-20 14:00:30.185 5815 5815 I ActivityThread: Pub com.android.bluetooth.opp: com.android.bluetooth.opp.BluetoothOppProvider
02-20 14:00:30.205 5708 5708 I BluetoothToggle: OnReceive
02-20 14:00:30.205 5708 5708 I BluetoothToggle: getServiceState
02-20 14:00:30.205 5708 5708 I BluetoothToggle: getServiceState.INTERMEDIATE_STATE
02-20 14:00:30.205 5708 5708 I BluetoothToggle: UpdateWidget - currentState=INTERMEDIATE_STATE
02-20 14:00:30.205 5708 5708 I BluetoothToggle: updateButtons
02-20 14:00:30.215 1599 1941 I ActivityManager: Start proc com.motorola.bluetooth for broadcast com.motorola.bluetooth/.map.BluetoothMapReceiver: pid=5825 uid=10074 gids={3002, 3001, 1015}
02-20 14:00:30.215 1599 1941 I ActivityManager: No longer want com.android.calendar (pid 2803): hidden #21
02-20 14:00:30.225 1599 5814 I bluedroid: Starting bt_start
02-20 14:00:30.445 5825 5825 V BluetoothMapReceiver: MapReceiver onReceive: android.bluetooth.adapter.action.STATE_CHANGED
02-20 14:00:31.355 1424 1458 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-20 14:00:31.355 1426 1493 E NetlinkListener: ignoring non-kernel netlink multicast message
02-20 14:00:31.355 1424 1458 E NetlinkListener: ignoring non-kernel netlink multicast message
02-20 14:00:32.765 1424 1458 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-20 14:00:32.775 1426 1493 E NetlinkListener: ignoring non-kernel netlink multicast message
02-20 14:00:32.775 1424 1458 E NetlinkListener: ignoring non-kernel netlink multicast message
Here is the log from before I deleted wifi and bluetooth driver. Once again, it didn't work. There are a few modules with dhd.ko, namely aev.ko, evfwd.ko, scsi_wait_scan.ko, vpnclient.ko. Would deleting any of those along with dhd.ko help?
Here is logcat, can we confirm my wifi is truly kaput? I think so(neither BT or wifi driver were deleted yet):
02-20 14:27:47.018 1776 2275 D WifiService: setWifiEnabled: true pid=2149, uid=1000
02-20 14:27:47.018 2051 2051 D BluetoothAdapter: 1088533408: getState() : mService = null. Returning STATE_OFF
02-20 14:27:47.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
02-20 14:27:47.018 1776 4965 E WifiStateMachine: Failed to load driver!
02-20 14:27:47.018 1776 1944 E WifiStateMachine: DriverFailedState
02-20 14:27:47.018 2051 2051 D BluetoothAdapter: 1088533408: getState() : mService = null. Returning STATE_OFF
02-20 14:27:47.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
02-20 14:27:49.018 1776 1776 D dalvikvm: GC_FOR_ALLOC freed 300K, 25% free 7929K/10572K, paused 60ms, total 60ms
02-20 14:27:49.018 1776 1776 I dalvikvm-heap: Grow heap (frag case) to 8.122MB for 214528-byte allocation
02-20 14:27:49.018 1776 1776 D dalvikvm: GC_FOR_ALLOC freed 0K, 25% free 8139K/10784K, paused 44ms, total 44ms
02-20 14:27:49.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
02-20 14:27:49.018 2149 2149 W System.err: Removed 2131231229
02-20 14:27:49.018 2149 2149 W System.err: Removed 2131231243
02-20 14:27:49.018 2149 2149 D BluetoothAdapter: 1087624032: getState() : mService = null. Returning STATE_OFF
Magnetox said:
There are a few modules with dhd.ko, namely aev.ko, evfwd.ko, scsi_wait_scan.ko, vpnclient.ko. Would deleting any of those along with dhd.ko help?
Click to expand...
Click to collapse
No. Don't touch them.
ravilov said:
No. Don't touch them.
Click to expand...
Click to collapse
Great, I didn't :angel:
The same problem exactly is a frequent guest of Galaxy Note 2. The only cure is the hard reset.
In Note 2 you have to remove the battery, press power button and hold it for 30+ seconds. Without the battery!
The Q is how to do hard reset to the Atrix.
Sent from my Atrix which I bought drunk. Kill nVidia!
I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!
There could be 3 causes for this...
1. Kernel WIFI modules doesn't match the kernel.
2. Hardware problem
3. Not sure about this since I'm just new to samsung but it could also be from a corrupt EFS partition.
But to further troubleshoot this problem can you do this for me?
1. Install terminal emulator from playstore.
2. execute this command from there
Code:
svc wifi enable
See if it shows some errors, warnings or whatever text it will print.
if not type logcat and paste here the last 100 to 150 lines of the output.
htimsxela said:
I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!
Click to expand...
Click to collapse
I believe, (Don't quote me on this), if the EFS partition was corrupted or lost, the phone would not have any radio functionality including voice and text etc
Also I 'think' the IMEI is also included on that partition, so *#06# should come up blank if it was the EFS partition causing the problem
But again, this is just what I've also picked up in the short time I've been with my S5 so could be missing something
[Solved], but the hard way
I took the device to Samsung and they said there was a problem on the main board (?), so they replaced it for a new one. I don't think I'm going to complain about it. Although I think that could be fixed somehow, replacing was probably easier. I said "the hard way" on the title, meaning it was a "brute force" fix. It is a pity I wasn't able to keep the old board for experimentation...
Thanks for your replies, guys. I didn't even expect replies and got yours and so complete! Thanks a lot!
My PH-1 reboots randomly, sometimes frequently, and it is accompanied with sudden surge of heat on the in almost the direct center of the phone, on both the front and back sides. This has happened on stock Oreo (from .010 to current stock builds), RR, Lineage OS, AOSiP, and Carbon ROM. I've had it occur while rooted/unrooted, with or without xposed, and have thoroughly wiped device in between new ROMs. And though the device does suddenly get quite hot it can happen when im in a dark cold place or outside in the sun. The only correlation is that it seems to only occur while talking on the phone but length of call is not a factor in that scenario. It could happen 5 times in an hour or in a week.
I'm new to modification, and although green I've made my way through it pretty well thanks to the great forums and tips offered here. Rooting/modding is now much simpler now but this problem has been persisting for almost two months. I've got a logcat from boot to crash taken via ADB (about 2-3 minutes real time) but don't know how to interpret it enough to discover the cause of the problem . Thanks in advance for any help provided. I will post the logcat but I'm not sure of how much to post or how for that matter haha.
Thanks again
That really sounds like a hardware problem if its persisting across ROMs.
Warranty for sure. Most definitely a hardware fault.
jhs39 said:
That really sounds like a hardware problem if its persisting across ROMs.
Click to expand...
Click to collapse
I've taken quite a few logs and there are two consistent segments that I can't get figured out. Any help would be great. The second one has way more variations on the theme and they're grouped. Also, my phone was brand new but NOT purchased from a retailer. I'm assuming I'm outta luck for warranty?
A) 05-17 20:58:36.979 1518 1877 E Diag_Lib: [IMS_FATAL]| 1877 |ims_qmi_register_client : Failed
B) 05-17 20:59:11.372 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getAuthFrequency []
05-17 20:59:11.373 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getUserHasFop []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getFingerprintValid []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getDesiredAuthMethod []
05-17 20:59:11.374 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got an exception trying to get proto method: java.lang.NoSuchMethodException: getAuthFrequency []
05-17 20:59:11.375 3949 6262 W Finsky : [102] com.google.android.finsky.billing.a.j.a(48): Got
crixley said:
Warranty for sure. Most definitely a hardware fault.
Click to expand...
Click to collapse
Thank you for the response. Please look at my reply to user below your post. Is any information gathered just from those logs?
It looks like it's constantly polling to register you on the network and failing. What company are you with? Try two things just to satisfy my curiosity:
1) go into mobile network> advanced and change automatically select network to off. Click below and choose your provider yourself from the list.
2) double check the access point name (APN settings)
crixley said:
It looks like it's constantly polling to register you on the network and failing. What company are you with? Try two things just to satisfy my curiosity:
1) go into mobile network> advanced and change automatically select network to off. Click below and choose your provider yourself from the list.
2) double check the access point name (APN settings)
Click to expand...
Click to collapse
I'm on Verizon and step 1, done. It was active so I switched off. Step 2 it lists 2 APN... Verizon (VZWINTERNET) **checked** and Straight Talk Verizon (TRACKFONE.VZWENTP)**not checked**
Now im curious so I'll run logcat and see if similar codes persist. It seems like I'm on the phone nearly every time it happens, don't know if there is a correlation.
Thanks!
KingBeefy said:
I'm on Verizon and step 1, done. It was active so I switched off. Step 2 it lists 2 APN... Verizon (VZWINTERNET) **checked** and Straight Talk Verizon (TRACKFONE.VZWENTP)**not checked**
Now im curious so I'll run logcat and see if similar codes persist. It seems like I'm on the phone nearly every time it happens, don't know if there is a correlation.
Thanks!
Click to expand...
Click to collapse
Would be registering on the network when you make a call, it registers with the nearest tower to you. Let me know if that helps!
crixley said:
Would be registering on the network when you make a call, it registers with the nearest tower to you. Let me know if that helps!
Click to expand...
Click to collapse
So went a few hours with the changes you recommended and it was doing ok so far. The reboots are randomized. Might be 1 time in 36 hours and others its 6 times in an hour. Phone activity, battery life, etc seem to have a wide deviation too. BUT, so far so good. Much of the logcat did look like nothing was throwing a fail code, but this one still popped up enough to notice .
05-21 06:53:19.972 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:20.335 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:21.982 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:21.984 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:22.330 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:23.991 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:23.993 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:24.348 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:26.000 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:26.002 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
KingBeefy said:
So went a few hours with the changes you recommended and it was doing ok so far. The reboots are randomized. Might be 1 time in 36 hours and others its 6 times in an hour. Phone activity, battery life, etc seem to have a wide deviation too. BUT, so far so good. Much of the logcat did look like nothing was throwing a fail code, but this one still popped up enough to notice .
05-21 06:53:19.972 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:20.335 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:21.982 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:21.984 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:22.330 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:23.991 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:23.993 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:24.348 1050 2263 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-21 06:53:26.000 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
05-21 06:53:26.002 1553 1897 E Diag_Lib: [IMS_FATAL]| 1897 |ims_qmi_register_client : Failed
Click to expand...
Click to collapse
Hmmm. Have you flashed any other modems? Might be worth a shot.
crixley said:
Hmmm. Have you flashed any other modems? Might be worth a shot.
Click to expand...
Click to collapse
Teach me master!!!! What resource will you point me to?
KingBeefy said:
Teach me master!!!! What resource will you point me to?
Click to expand...
Click to collapse
Lol
What I would do is full wipe and fastboot flash the latest full file. Seems like OTAs haven't been updating the modem and ROMs wouldn't either I doubt.
You could probably just fastboot flash the modem.img from from the latest fastboot release if you really didn't want to full wipe.
The full wipe doesnt scare me off. I took my lumps teaching myself from scratch and the nuances of the way dual partition devices function has been an interesting learn. I prefer using ADB/fastboot/twrp instead of doing and OTA because of the learning opportunity so I have the latest modem.img from the current Firmware from essentials site. I also use @invisiblek builds. I sent Essential the log and they offered a suggestion as well, saying
I am sending you two troubleshooting steps that.... One of the reasons we need to do this is that when you factory reset your phone you restored backed up information and you signed back into you google account....
Click to expand...
Click to collapse
One of the first things I learned in forums like this one was that until you are ready to go, don't sign in to anything. So I will try and do that. Thanks again for suggestions @crixley
I was having this issue a while back. Every custom rom/kernel caused the processor to lock up at Max frequency randomly thus causing quick overheating no matter how small the load. Performance is amazing through this, but overheating is very annoying. I fixed mine by sticking to stock rooted and not touching the governors or thermal throttling. Maybe I would suggest monitoring your processor with a kernel manager and/or trying to play around with governors and thermal options for now, if you in fact have the same issue, to see if you get something thats stable and sticks. Good luck
I had an issue with mine where it was constantly locking up and rebooting, mostly during multimedia activities like watching YouTube, gaming and even browsing chrome. I never monitored the temperature and it never felt hot to the touch but it just kept happening constantly. I bought it as a refurbished on eBay and was crashing out of the box. It was completely stock Android 8.1.1. Most of the time it would just constantly non stop crash after 30seconds-10minutes of being turned on,. Would just freeze, sit for 30 seconds and then reboot itself. A couple times it lasted sitting idle for 14 hours before crashing and then constantly do it again.
Anyways even though it was a refurbished unit and the seller was not the original owner, it was still under warranty period and was able to be replaced. Just open warranty rma with essential is what I would do. If the serial/imei you provide them is still under warranty they will probably honor it.
Also they gave me that troubleshooting steps too,. Factory reset, start fresh and don't login to your, it's bogus. Still had the same issue on my phone and I actually had to send my phone back twice before they replaced it. The first time I sent it in they said they ran diagnostics that didn't detect any issue, but when I got the phone back it crashed within 10minutes and I never logged into Google. Just a bad hardware issue.
KingBeefy said:
The full wipe doesnt scare me off. I took my lumps teaching myself from scratch and the nuances of the way dual partition devices function has been an interesting learn. I prefer using ADB/fastboot/twrp instead of doing and OTA because of the learning opportunity so I have the latest modem.img from the current Firmware from essentials site. I also use @invisiblek builds. I sent Essential the log and they offered a suggestion as well, saying One of the first things I learned in forums like this one was that until you are ready to go, don't sign in to anything. So I will try and do that. Thanks again for suggestions @crixley
Click to expand...
Click to collapse
I am seeing the same errors. What did Essential say? Did it resolve the errors?
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Code:
01-08 17:48:26.818 2890 2890 E Sensors : sns_main.c(447):Timeout waiting for SMGR service. Exit sensors daemon!
01-08 17:48:26.819 2890 2890 W Sensors : sns_main.c(355):sns_main_exit called unlock daemon to exit
01-08 17:48:26.819 2890 2890 E Sensors : sns_main.c(561):Exiting! Err 0
01-08 17:48:26.848 2909 2909 W sensors.qcom: type=1400 audit(0.0:74): avc: denied { read write } for name="diag" dev="tmpfs" ino=717 scontext=u:r:sensors:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0
01-08 17:48:26.858 2909 2909 E Diag_Lib: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
01-08 17:48:26.858 2909 2909 W Sensors : sns_debug_main.c(442):Diag_LSM_Init failed: log packets and messages will not be available
01-08 17:48:26.861 2909 2911 E Sensors : sns_fsa_la.c(84):realpath failed for directory name2
01-08 17:48:26.861 2909 2911 E Sensors : sns_reg_la.c(289):Error creating registry file
01-08 17:48:26.861 2909 2911 W Sensors : sns_reg_mr.c(367):File init failed 5
drizzle123 said:
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Click to expand...
Click to collapse
Use lenovo moto smart assistant to flash the stock firmware
skoar said:
Use lenovo moto smart assistant to flash the stock firmware
Click to expand...
Click to collapse
Will try this when I get to a PC - thank you!
Hello firends,
i have a head unit with android 9 ( Geely Car ) , i can adb with root i checked the drivers for wlan0 and its loading during th boot , the issue is when ever i start the wifi it turn it self off automatically when i checked the dmesg there is nothing about wifi during boot , but in logscat it says
i can bring the wlan0 up with su but still i cant turn it on from the settings
[email protected]: Wifi Hal is booting up...
01-01 00:00:02.870 948 948 I wificond: wificond is starting up...
11-24 01:58:10.576 1633 1633 I SystemServiceManager: Starting com.android.server.wifi.WifiService
11-24 01:58:10.600 1633 1633 D ConnectivityService: wifiOnly=false
11-24 01:58:11.961 1633 1778 E BatteryExternalStatsWorker: no controller energy info supplied for wifi
11-24 02:28:05.719 1633 1778 E BatteryExternalStatsWorker: no controller energy info supplied for wifi
11-24 02:58:05.721 1633 1778 E BatteryExternalStatsWorker: no controller energy info supplied for wifi
11-24 03:28:05.721 1633 1778 E BatteryExternalStatsWorker: no controller energy info supplied for wifi
11-24 03:28:42.768 2605 2605 D PowerSomeIPServiceImpl: onReceive: wifiState=2
11-24 03:28:42.768 2605 2605 E PowerSomeIPServiceImpl: other wifi state, do nothing
11-24 03:28:42.768 4070 4070 D wifitracker: action==>android.net.wifi.WIFI_STATE_CHANGED
11-24 03:29:07.400 4070 4070 D wifitracker: action==>android.net.wifi.WIFI_STATE_CHANGED
11-24 03:29:07.400 2605 2605 D PowerSomeIPServiceImpl: onReceive: wifiState=1
11-24 03:29:51.030 2605 2605 D PowerSomeIPServiceImpl: onReceive: wifiState=2
11-24 03:29:51.030 2605 2605 E PowerSomeIPServiceImpl: other wifi state, do nothing
11-24 03:29:51.030 4070 4070 D wifitracker: action==>android.net.wifi.WIFI_STATE_CHANGED
11-24 03:30:15.662 4070 4070 D wifitracker: action==>android.net.wifi.WIFI_STATE_CHANGED
11-24 03:30:15.662 2605 2605 D PowerSomeIPServiceImpl: onReceive: wifiState=1
any help would be appreciated or at least point me where to start digging and troubleshooting , so ican unlock it
BR
Is this a Chinese origin aftermarket headunit
Yea its a Chinese car and Not aftermarket , its original HU ( OEM )
i succeeded bring the wlan0 up with ( su -0 ifconfig wlan0 up ) and i can see its info in ifconfig but still no luck turning it on from the setting ( after press toggle to turn on automatically turn off ) , im not sure if its a third party app or could be selinux preventing that ...
Is it Android auto or Android Automotive