Alright, this will be my last update on this topic for now. This is a very good post that explains what's going on. Thank you lgkahn for pointing this specific post out: http://forum.xda-developers.com/showpost.php?p=13247149&postcount=57
We're going to have to wait until this is fixed by Samsung.
If you read below here, you'll find a lot of information in this post regarding my research of FastDormancy. It is irrelevant to the Android OS bug.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
EDIT: Moving additional findings to the top as I'm having trouble determing a direct relationship between Android OS and data connection. There has been a decent amount of research in this thread regarding FastDormancy, what it is, and what determines it being on/off. Even if FastDormancy is indeed not at all related to Android OS, this isn't a bad thing. Rather, us being able to rule out things that are not the cause only helps us narrow down the list of things that could be the cause.
Request: Can someone with battery drain issues please send me a copy of their logcat file? I'd like to see if anything in it stands out like a sore thumb. By all means feel free to scan through it first to confirm no information exists that you don't want to share (sometimes text message data is in there, along with other crap).
Click to expand...
Click to collapse
I know there are other battery-related threads that exist, however I was hoping to focus on more in-depth research on specific topics. If you feel we should dig into a new area, please feel free to PM me and I'll make sure to add it to the list.
Current topics of discussion:
- FastDormancy
- Data connections (3G/Wifi)
- System resource usage (monitoring processes)
Findings so far:
- Disabling background data under "Accounts" does not cause getCapaDormancy() to return true.
- KE1 firmware seemed to call getCapaDormancy() every second (this could be skewed as it wasn't a factory reset).
- KE2 firmware is calling every 5 seconds (after factory reset).
- FastDormancy only invoked when a data connection exists. If toggled off, FastDormancy ceases to check getCapaDormancy() until toggled back on.
- FastDormancy is not invoked when a Wifi connection exists. If toggled off, FastDormancy resumes checking getCapaDormancy()
- Turning off the data connection dramatically reduces the Android OS usage (for me, haven't had anyone else confirm yet)
- German mobile networks appear to support Fast Dormancy (very small sample size at the moment however)
- With KE2, hourly idle CPU usage time (from Android OS) with data enabled and wifi disabled = 5min per hour
- With KE2, hourly idle CPU usage time (from Android OS) with data enabled and wifi enabled = 5min per hour
- After testing the data connection, I wasn't able to get any consistent results to prove a true relationship with Android OS usage
- Disabling all battery/process monitoring software has shown an initial decrease in Android OS usage (significant so far)
Click to expand...
Click to collapse
FastDormancy Research:
I hooked up my phone to my computer and started reading the LogCat in Debug mode and I see something that looks EXTREMELY suspicious. Take a look at this:
With KE1 Firmware
Code:
05-14 15:07:26.200: DEBUG/FastDormancy(2815): before ======= ENTER DORMANCY =======
05-14 15:07:26.200: DEBUG/FastDormancy(2815): [FD] ON default: true
05-14 15:07:26.200: DEBUG/FastDormancy(2815): Before mDormFlag: false in getCapaDormancy()
05-14 15:07:26.200: DEBUG/FastDormancy(2815): After mDormFlag: false in getCapaDormancy()
05-14 15:07:27.204: DEBUG/FastDormancy(2815): before ======= ENTER DORMANCY =======
05-14 15:07:27.204: DEBUG/FastDormancy(2815): [FD] ON default: true
05-14 15:07:27.204: DEBUG/FastDormancy(2815): Before mDormFlag: false in getCapaDormancy()
05-14 15:07:27.204: DEBUG/FastDormancy(2815): After mDormFlag: false in getCapaDormancy()
05-14 15:07:28.210: DEBUG/FastDormancy(2815): before ======= ENTER DORMANCY =======
05-14 15:07:28.210: DEBUG/FastDormancy(2815): [FD] ON default: true
05-14 15:07:28.210: DEBUG/FastDormancy(2815): Before mDormFlag: false in getCapaDormancy()
05-14 15:07:28.215: DEBUG/FastDormancy(2815): After mDormFlag: false in getCapaDormancy()
05-14 15:07:29.214: DEBUG/FastDormancy(2815): before ======= ENTER DORMANCY =======
05-14 15:07:29.214: DEBUG/FastDormancy(2815): [FD] ON default: true
05-14 15:07:29.224: DEBUG/FastDormancy(2815): Before mDormFlag: false in getCapaDormancy()
05-14 15:07:29.224: DEBUG/FastDormancy(2815): After mDormFlag: false in getCapaDormancy()
05-14 15:07:30.224: DEBUG/FastDormancy(2815): before ======= ENTER DORMANCY =======
05-14 15:07:30.224: DEBUG/FastDormancy(2815): [FD] ON default: true
05-14 15:07:30.229: DEBUG/FastDormancy(2815): Before mDormFlag: false in getCapaDormancy()
05-14 15:07:30.229: DEBUG/FastDormancy(2815): After mDormFlag: false in getCapaDormancy()
It would appear that approximately once every second, something regarding "FastDormancy" is checking a function getCapaDormancy(). Now, this may be something specific to an application I'm running, but to be honest I'm not sure.
Click to expand...
Click to collapse
With KE2 Firmware
Code:
05-14 18:49:44.031: DEBUG/FastDormancy(2942): before ======= ENTER DORMANCY =======
05-14 18:49:44.031: DEBUG/FastDormancy(2942): [FD] ON default: true
05-14 18:49:44.031: DEBUG/FastDormancy(2942): Before mDormFlag: false in getCapaDormancy()
05-14 18:49:44.031: DEBUG/FastDormancy(2942): After mDormFlag: false in getCapaDormancy()
05-14 18:49:49.046: DEBUG/FastDormancy(2942): before ======= ENTER DORMANCY =======
05-14 18:49:49.046: DEBUG/FastDormancy(2942): [FD] ON default: true
05-14 18:49:49.046: DEBUG/FastDormancy(2942): Before mDormFlag: false in getCapaDormancy()
05-14 18:49:49.046: DEBUG/FastDormancy(2942): After mDormFlag: false in getCapaDormancy()
05-14 18:49:54.067: DEBUG/FastDormancy(2942): before ======= ENTER DORMANCY =======
05-14 18:49:54.067: DEBUG/FastDormancy(2942): [FD] ON default: true
05-14 18:49:54.067: DEBUG/FastDormancy(2942): Before mDormFlag: false in getCapaDormancy()
05-14 18:49:54.067: DEBUG/FastDormancy(2942): After mDormFlag: false in getCapaDormancy()
05-14 18:49:59.087: DEBUG/FastDormancy(2942): before ======= ENTER DORMANCY =======
05-14 18:49:59.087: DEBUG/FastDormancy(2942): [FD] ON default: true
05-14 18:49:59.087: DEBUG/FastDormancy(2942): Before mDormFlag: false in getCapaDormancy()
05-14 18:49:59.087: DEBUG/FastDormancy(2942): After mDormFlag: false in getCapaDormancy()
And with this firmware, once every 5 seconds...
Click to expand...
Click to collapse
Fast Dormancy log on supporting network:
Code:
04-19 13:21:10.398 W/FastDormancy( 269): before ======= ENTER DORMANCY =======
04-19 13:21:10.398 D/FastDormancy( 269): [FD] ON default: true
04-19 13:21:10.441 D/FastDormancy( 269): Before mDormFlag: true in getCapaDormancy()
04-19 13:21:10.445 D/FastDormancy( 269): After mDormFlag: true in getCapaDormancy()
04-19 13:21:10.449 W/FastDormancy( 269): ======= ENTER DORMANCY =======
04-19 13:21:10.500 D/FastDormancy( 269): ======= FAST DORMANCY Enter =======
Click to expand...
Click to collapse
Notice how this one seems to actually enter dormancy where as on the SGS2 it just keeps attempting to do so? This seems like it would directly tie to the suspend/0 process chewing up a large amount of CPU time on people's devices. Every time it needs to do this function check it has to utilize the CPU.
Click to expand...
Click to collapse
Flagging to some guys with SGS2s to look at.
Slyydrr, I really think you found it! Seems as if it's trying to go into suspend, gets a "false" from the boolean and stays awake with it's eyes closed so to speak. Is there a way to see why the boolean is filled with false instead of true, using debugging modes/functions? Like seeing what happens when the sleep-button is pressed.
Let's hope so. I'm assuming getCapaDormancy() checks to see if the device is capable to go into dormancy mode (getCapableDormancy being the full name that is abbreviated). Obviously like you said, getting false all the time will prevent this. I'm currently digging through more of the debug logs to see if I can't see something else suspicious regarding the screen being turned on/off.
Brilliant stuff! Definite progress. Given that there's a theory that turning off background data helps, it might be worth checking the logs with that toggled and see if you get the "happy path".
Sent from my GT-I9100 using XDA Premium App
dan13l said:
Brilliant stuff! Definite progress. Given that there's a theory that turning off background data helps, it might be worth checking the logs with that toggled and see if you get the "happy path".
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Just tried it - even with background data disabled, the getCapaDormancy() method continuously returns false. Worth a try though!
So... the challenge is now to figure out WHAT is causing that message.
Frameworks?
pulser_g2 said:
So... the challenge is now to figure out WHAT is causing that message.
Frameworks?
Click to expand...
Click to collapse
Exactly my question - the next step for me is to try and figure out where this method resides. It might be in the kernel, or somewhere completely different. I'll be checking out the kernel source code sometime soon (today hopefully).
could u test it without any widget?
sent from my SGSII via T*patalk
i just made a logcat file and looked for the same lines you did, but on mine everything thats related to dormancy looks like this:
D/FastDormancy( 2822): before ======= ENTER DORMANCY =======
D/FastDormancy( 2822): [FD] ON default: true
D/FastDormancy( 2822): Before mDormFlag: true in getCapaDormancy()
D/FastDormancy( 2822): After mDormFlag: true in getCapaDormancy()
W/FastDormancy( 2822): ======= ENTER DORMANCY =======
D/FastDormancy( 2822): ======= FAST DORMANCY Enter =======
im on KE2 firmware.
The_Revenge said:
i just made a logcat file and looked for the same lines you did, but on mine everything thats related to dormancy looks like this:
D/FastDormancy( 2822): before ======= ENTER DORMANCY =======
D/FastDormancy( 2822): [FD] ON default: true
D/FastDormancy( 2822): Before mDormFlag: true in getCapaDormancy()
D/FastDormancy( 2822): After mDormFlag: true in getCapaDormancy()
W/FastDormancy( 2822): ======= ENTER DORMANCY =======
D/FastDormancy( 2822): ======= FAST DORMANCY Enter =======
im on KE2 firmware.
Click to expand...
Click to collapse
Was your phone hooked up to your computer, or did you run an app with logcat capabilities? Perhaps my phone being hooked up is the reason that the getCapaDormancy() == false, and therefore flush the entire theory down the drain
Also worth noting, I'm on KE1.
yes, my phone was hooked to the pc, i did logcat via adb
The_Revenge said:
yes, my phone was hooked to the pc, i did logcat via adb
Click to expand...
Click to collapse
Okay well that's good then. Aside from applications and frozen apps, the only other difference between our devices looks to be the firmware. How is your Android OS usage?
EDIT: FYI, I just confirmed that eclipse was not causing my devices to constantly return false. Closing eclipse and connecting through adb to dump the logcat still showed false.
Android OS is on 13% for me.
its been connected to my pc for about 5 hours now, with me playing a bit around a bit a few times, but most of the time it was idle.
actually i get a pretty good battery life, since yesterday to today it was disconnected from charging for about 12hours, and it dropped from 100% to ~80% in that time. (i did use it in that 12hours time with low/average use and all the syncing from social hub, facebook, twitter, talk, gmail enabled)
actually, i have no frozen apps, im even using social hub with sync etc...
I just flashed to the new firmware... And I'm almost certain that it fixed the drain issue! Used to get a fair battery usagegraph for several hours, then suddenly taking a more steep approach towards 0%, meanwhile seeing android—os taking up an ever increasing percentage of the powerconsumption, usually triggered by some general usage (turning wifi/gps on/off, etc).
Since the new firmware: Already for 7 hours pretty intensive usage (wifi, gps, apps), without the batterygraph taking the oh so familiar steep-creep line downwards! Just a steady line to 83%
...fingers still crossed...
Sent from my GT-I9100 using XDA App
The_Revenge said:
Android OS is on 13% for me.
its been connected to my pc for about 5 hours now, with me playing a bit around a bit a few times, but most of the time it was idle.
actually i get a pretty good battery life, since yesterday to today it was disconnected from charging for about 12hours, and it dropped from 100% to ~80% in that time. (i did use it in that 12hours time with low/average use and all the syncing from social hub, facebook, twitter, talk, gmail enabled)
actually, i have no frozen apps, im even using social hub with sync etc...
Click to expand...
Click to collapse
100% to 80% in 12 hours is how it's supposed to be. Good to have someone without the problem.
Did you install any apps from the market? Did you root your phone?
yeah, my device is rooted, and i have installed dozens of apps from market
like 10 full pages of apps in touchwiz
I'm on KE1 and have the same thing happening! But I got only like 10 of this messages and none incoming, and my Android OS is @ 7%.
EleCtrOx666 said:
I'm on KE1 and have the same thing happening!
Click to expand...
Click to collapse
I'm going to install a fresh copy of KE1 tonight, check the logs, and then do a fresh install of KE2 and also compare. Hopefully that should tell us something. Quick question - being that I'm new to Samsung devices, what is the proper way to do a full system wipe when installing a new firmware through Odin? The only option I can think of is to do a System restore before/after.
The_Revenge said:
yeah, my device is rooted, and i have installed dozens of apps from market
like 10 full pages of apps in touchwiz
Click to expand...
Click to collapse
Are you running the new firmware, or the old one?
Related
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
Here's how to use logcat..There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app..Here are two good examples are either aLogcat or CatLog I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb.
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Please do NOTE: : I am just sharing. Original post is Here.
Don't be a noob. Be a newbie..!!
Details here.
Great guide! I am glad that I can help you by logcat. Thanks.
Sent from my E10i using xda app-developers app
How long take the. Logcat?
Sent from my E10i using xda premium
ruben21 said:
How long take the. Logcat?
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Whatever you want.
Sent from my E10i using xda app-developers app
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
ruben21 said:
Well and how I finish the logcat because I leave them all the night and still run
Sent from my E10i using xda premium
Click to expand...
Click to collapse
Just press CTRL + C
Thanks bro.
☜ Sent from my X10 MP U20i ☞
Dear all,
I wish share my experience, with Supernexus 2.0 Build 4.0 on my gs3, more especially with the wifi tethering.
Like most of people, i encountered the issue with the last version where wifi tether did not work, although in the release note, it is indicated as fixed.
So, like others guys, second device was properly connected to the wifi hotspot (it had an IP adress).
Ping to gateway OK... For me, all should be ok to provide internet to second device, but never.... :crying:
I decided, after many tests, wipes, re-install, to check logfile with logcat tools, and i found this :
05-06 08:29:14.255 D/Tethering(2264): notifying tethered with iface =null
...
...
05-06 08:29:20.775 D/libgps (2264): agps_ril_update_network_state: Waiting for IPC connection - timeout
05-06 08:29:20.775 E/libgps (2264): GpsiClient: Can't write to closed pipe
05-06 08:29:20.775 E/libgps (2264): IPC Communication Error, /tmp/11980989/proprietary/deliverables/android/gps_interface/../gps_interface/gpsi_client/GpsiClient.cpp:1143 agps_ril_update_network_state
05-06 08:29:20.775 D/libgps (2264): proxy_agps_ril_update_network_state: called
05-06 08:29:20.775 D/libgps (2264): agps_ril_update_network_availability: Waiting for IPC connection...
05-06 08:29:21.780 D/libgps (2264): agps_ril_update_network_availability: Waiting for IPC connection - timeout
Where id 2264 is regarding the tether process in activity for my test.
So, when i read logfile, I found this very weird :
05-06 08:29:20.775 E/libgps (2264): IPC Communication Error, /tmp/11980989/proprietary/deliverables/android/gps_interface/../gps_interface/gpsi_client/GpsiClient.cpp:1143 agps_ril_update_network_state
So, by curiosity, i enabled GPS by the toggle, and a miracle appear, the wifi tethering has worked perfectly.....
My second device connected to the hospot, can browse and get data from internet.... :victory:
May be, someone (an expert) can explain this, but for the moment I wish share this workaround with all.
See you,
Manuxme.
May be relevant to us, don't know. But should be noted the ROM you mention is for the international, just in case someone gets eager and tries using it.
We have hotspot unlocked for the most recent builds of TW.
He is posting in the wrong g forum
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
He is posting in the wrong g forum
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You are right.... Sorry for that, it was my first ppost altough I follow many subject since few weeks....
DO not hesitate to move the post to the good one
Manuxme.
Is the post can be move to this area :
Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting (and not Sprint Samsung Galaxy S III > Sprint Galaxy S III Q&A, Help & Troubleshooting ).
Sorry for the inconveniences.
Manuxme.
Manuxme said:
Is the post can be move to this area :
Samsung Galaxy S III I9300, I9305 > Galaxy S III Q&A, Help & Troubleshooting (and not Sprint Samsung Galaxy S III > Sprint Galaxy S III Q&A, Help & Troubleshooting ).
Sorry for the inconveniences.
Manuxme.
Click to expand...
Click to collapse
You can report the thread (from the browser) and just say you want the thread moved, or PM a mod
CNexus said:
You can report the thread (from the browser) and just say you want the thread moved, or PM a mod
Click to expand...
Click to collapse
Done
Transmitted with a portable device using Xparent Blue Tapatalk 2
All,
About the workaround indicated yesterday by enabling the GPS, actually, it does not work !!!!
I do not why yesterday it works. When GPS turn UP wifi tether works when turn down, it does not works. A strange luck ??!!
BTW, I continu investigations, tests and founds the really root cause (already found by people on other forum) :
Code:
AccountRecoveryService$Receiver }
05-07 13:06:28.145 D/dalvikvm(2725): GC_CONCURRENT freed 360K, 5% free 9328K/9784K, paused 1ms+1ms, total 14ms
05-07 13:06:28.320 D/ConnectivityService(2268): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
05-07 13:06:30.230 D/ConnectivityService(2268): ConnectivityChange for mobile_dun: CONNECTED/CONNECTED
05-07 13:06:30.270 E/SecondaryTablController(1907): [B]ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 10.221.59.1 dev rmnet1 table 60[/B]
05-07 13:06:30.270 W/FrameworkListener(1907): Handler 'interface' error (No such device)
05-07 13:06:30.275 E/ConnectivityService(2268): Exception trying to add a route: java.lang.IllegalStateException: command '182 interface route add rmnet1 secondary 0.0.0.0 0 10.221.59.1' failed with '400 182 ip route modification failed (No such device)'
05-07 13:06:30.275 E/ConnectivityService(2268): Exception trying to remove a route: java.lang.IllegalStateException: command '183 interface route remove rmnet1 default 0.0.0.0 0 10.221.59.1' failed with '400 183 Failed to remove route from default table (No such process)'
05-07 13:06:30.295 W/NetworkPolicy(2268): shared quota unsupported; generating rule for each iface
05-07 13:06:33.300 D/Tethering(2268): TetherModeAliveState.processMessage what=3
05-07 13:06:33.300 D/Tethering(2268): chooseUpstreamType(true), preferredApn =4, got type=4
05-07 13:06:33.335 D/TetherController(1907): setDnsForwarders(0 = '192.168.10.110')
05-07 13:06:33.335 D/TetherController(1907): Sending update msg to dnsmasq [update_dns:192.168.10.110]
Everytime, Wifi tethering is enable; this issue apear :
05-07 13:06:30.270 E/SecondaryTablController(1907): ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 10.221.59.1 dev rmnet1 table 60
So, with a terminal emulator in root acces on the phone (example below in the screenshot), i launch exactly the same command line, and it works ?! :
Screenshot explanation:
1 - Check the new entry, added by the start of wifi tether process.
In orange, the exact command line launch on the terminal, in the history command line number 10.
Now, i sure, with this manual intervention, it works , the wifi tether allow other device to reach internet.
But why it failed everytime by the the normal way ? Is someone know ?
FOr the moment, i am going to try to write a shell script to add/remove the entry when necessary.
Thanks,
Manuxme.
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Sigosuuu said:
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Click to expand...
Click to collapse
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Davey126 said:
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Click to expand...
Click to collapse
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Sigosuuu said:
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Likely an app. You will need to use a tool like GSAM or BBS to identify the culprit.
My Apollo HDX behaves similarly, and has since I got it (refurbished) six months ago: very shortly after going into screen-off mode, a reboot occurs.
This happened under the stock 4.5.5.2 OS, but seemed to be mitigated if I set it to keep wifi on during sleep.
Under LineageOS 14.1, however, it reboots whether that option is enabled or disabled.
I've tried several times to see if anything interesting appears via wireless logcat, but nothing is terribly obvious. Here's the last attempt:
Code:
07-03 01:59:19.246 1157 1234 E WifiHAL : wifi_error acquire_supported_features(wifi_interface_handle, feature_set *): requestResponse Error:-95
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.248 1567 1567 E PhoneInterfaceManager: [PhoneIntfMgr] queryModemActivityInfo: Empty response
07-03 01:59:19.257 1157 1540 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
07-03 01:59:20.383 544 884 D audio_hw_primary: out_standby: enter: stream (0xb624ab00) usecase(1: low-latency-playback)
07-03 01:59:20.489 544 884 D hardware_info: hw_info_append_hw_type : device_name = speaker
After that, the device no longer pings as it has begun restarting.
Using Wake Lock (https://play.google.com/store/apps/details?id=eu.thedarken.wl), I found certain combinations that would prevent reboots when the screen goes off:
wifi on, wakelock WIFI_MODE_FULL_HIGH_PERF => ok
wifi on, wakelock WIFI_MODE_FULL (or less) => *restart on sleep*
wifi off, wakelock PARTIAL_WAKELOCK => ok
wifi off, wakelock WIFI_MODE_FULL_HIGH_PERF (or less) => *restart on sleep*
airplane mode, no wakelock => ok
Seems almost like some sort of hardware/driver issue.
Hi,
I am having issues with the Facebook application not letting me log in..
I am having this issue on both Oneplus 3 and a Oneplus 5.
On the logcat i get the the error:
Code:
09-19 14:36:16.343 9693-13345/? W/fb4a.BlueServiceQueue: Exception during service
com.facebook.tigon.tigonutils.TigonErrorException: TigonError(2): TigonLigerErrorDomain(2) AsyncSocketException: connect failed, type = Socket not open, errno = 111 (Connection refused)
at X.1e9.onError(:416738)
at com.facebook.tigon.tigonapi.TigonCallbacksIntegerBufferJavaHelper.onError(:417283)
at com.facebook.common.jniexecutors.NativeRunnable.run(Native Method)
at com.facebook.common.jniexecutors.PooledNativeRunnable.run(:308022)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at X.1Zd.run(:401648)
at java.lang.Thread.run(Thread.java:764)
Things I have already tried:
Delete app data and cache
Reinstall application
Factory reset device
If i use a proxy (using mitmproxy) it will go through and i get to the screen which says:
Is there anyway i can debug or fix this issue.
"We're sorry, we can't set up English (United Kingdom) at the moment"
Thanks