Since Cyanogen ported over the WPA Enterprise support from the donut branch, I have been eagerly wanting to get onto my corporate network.
With 3.9.5 running on my phone now, I can see the SSID of my network
show up in the list of available APs. It is listed as secured with WPA-EAP.
When I click the AP, I can set the EAP method (PEAP), the Phase 2 authentication (MSCHAP2),etc...
When I try to connect, it fails and gives a Disconnected status. When I
enter the following in Terminal:
Code:
su
cat /data/misc/wifi/wpa_supplicant.conf
I can scroll to the bottom and see the following:
network={
ssid="____"
key_mgmt=WPA-EAP
group=CCMP TKIP
priority=23
}
It does not appear to keep the settings for PEAP or MSCHAP2...
I manually edit the entry to the following:
network={
ssid="___"
key_mgmt=WPA-EAP
group=CCMP TKIP
eap=PEAP
identity="xxxxx"
password="xxxxx"
phase2="AUTH=MSCHAPV2"
priority=19
}
When I push the changes back into the /data/misc/wifi directory and restart,
it now tries to obtain an address... unsuccessfully... lol...
Here is the output from wpa_cli:
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>Trying to associate with 00:13:60:d4:e5:70 (SSID='___' freq=2462 MHz)
<2>CTRL-EVENT-STATE-CHANGE id=4 state=3
<2>CTRL-EVENT-STATE-CHANGE id=4 state=4
<2>Associated with 00:13:60:d4:e5:70
<2>CTRL-EVENT-EAP-STARTED EAP authentication started
<2>CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
<2>CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
<2>CTRL-EVENT-STATE-CHANGE id=4 state=5
<2>CTRL-EVENT-STATE-CHANGE id=4 state=5
<2>CTRL-EVENT-STATE-CHANGE id=4 state=6
<2>CTRL-EVENT-STATE-CHANGE id=4 state=6
<2>WPA: Key negotiation completed with 00:13:60:d4:e5:70 [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-STATE-CHANGE id=4 state=7
<2>CTRL-EVENT-CONNECTED - Connection to 00:13:60:d4:e5:70 completed (auth) [id=4
id_str=]
<2>CTRL-EVENT-STATE-CHANGE id=4 state=8
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=8
<2>CTRL-EVENT-STATE-CHANGE id=-1 state=2
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
<2>CTRL-EVENT-SCAN-RESULTS Ready
.
.
.
I am still reading up on all of this and will post anything I find, but I wanted to throw it out there for others too...
Any help would be greatly appreciated...
L8r,
Vermithrax
Solved
K.. Apparently all I needed to do was reboot after I made the changes above... Came into work this morning and I can now connect to my company network...
Go figure...
L8r,
Vermithrax
All, wanted to say thanks for all the helpful posts. I bought a Viewsonic G-Tablet two days ago and I'm well on my way to making this a bad habit.
So... to my question. Has anyone had experience getting the g-tablet with TNT 4.2.5 [haven't picked up 4.3.0 yet] and the SonicWall NetExtender app? I rooted the device prior to trying NetExtender, but it fails with a series of service errors:
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
03-23 08:37:31.495 D/sysHelper( 2183): Check Root Permission: Exit-Value ==> 0
03-23 08:37:36.315 E/NetExtender.nxclient( 2183): Unable to communicate with service - No such file or directory
03-23 08:37:41.005 D/NetExtender.nxclient( 2183): action button clicked
03-23 08:37:41.015 E/NetExtender.nxclient( 2183): Unable to stop backend service - Transport endpoint is not connected
03-23 08:37:54.035 D/sysHelper( 2245): Check Root Permission: Exit-Value ==> 0
03-23 08:37:58.965 E/NetExtender.nxclient( 2245): Unable to communicate with service - No such file or directory
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
03-23 08:41:05.305 D/sysHelper( 1420): Check Root Permission: Exit-Value ==> 0
03-23 08:41:14.945 E/NetExtender.nxclient( 1420): Unable to communicate with service - No such file or directory
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
03-23 22:42:35.224 D/sysHelper( 5824): Check Root Permission: Exit-Value ==> 0
03-23 22:42:41.115 E/NetExtender.nxclient( 5824): Unable to communicate with service - No such file or directory
I'm going to try dropping into a root shell before executing and see if that helps...
any thoughts are greatly appreciated.
Hi evilquim.
I'm getting the same issue with my G-Tab running VEGAN 5.1. I was wondering if you ever figured this out.
If I manage to get it working I'll post here.
Try the Sonicwall Mobile Connect application in the market if you are running Android 4.x
Hi everybody. I was stupid and I installed Linux installer on my phone. I don't know why I did this, but I tried to install Linux Ubuntu on Milestone. Because milestone's kernel doesn't support loop mode, I tried to install with chroot method(I made a nandroid backup before I started installing Ubuntu). While the app was downloading things needed for Ubuntu to work, the internal memory became full and my phone started to act very wierd(A lot of FCs, one after another), so I restarted my phone. But after restart my milestone started to bootloop(The CM7's boot animation is still shown). I tried to restore my backup, but it didn't help. I tried to flash stock ROM(2.1 and also 2.2) with RSD Lite and also with sbf_flash, I also tried full wipe and I also tried to flash vulnerable recovery only but I am still getting the bootloops. With stock ROM the phone restarts on 'M' logo, with CM7 it restarts on boot animation and with CM9 it stucks on bootanimation. I can access bootloader, I can flash everything ok without any errors, I can access recovery mode, I can charge turned off phone, but can't secusseful boot my phone. How to fix that?
Any help would be appreciated.
CM7:
boot to recovery and enable logger from OpenRecovery console or adb shell
Code:
echo 1 > /data/property/persist.service.aplogd.enable
let the phone boot and when it starts looping, reboot to recovery
fetch the logs to pc via usb
Code:
adb pull /cache/logger
post the logs for inspection
Wow..doesn't this looks like kernel panic?
AOL_kernel.ap.bin
Code:
03-22 07:46:36.426 D/kernel ( 0): [ 16.526306] [<c0035b24>] (unwind_backtrace+0x0/0xd8) from [<c005d15c>] (warn_slowpath_common+0x48/0x60)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526336] [<c005d15c>] (warn_slowpath_common+0x48/0x60) from [<c005d1ac>] (warn_slowpath_fmt+0x24/0x30)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526367] [<c005d1ac>] (warn_slowpath_fmt+0x24/0x30) from [<c009137c>] (__free_irq+0x98/0x1dc)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526397] [<c009137c>] (__free_irq+0x98/0x1dc) from [<c00914fc>] (free_irq+0x3c/0x5c)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526458] [<c00914fc>] (free_irq+0x3c/0x5c) from [<c02a5948>] (sim_ioctl+0x3e8/0x138c)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526489] [<c02a5948>] (sim_ioctl+0x3e8/0x138c) from [<c00c8720>] (vfs_ioctl+0x70/0x8c)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526519] [<c00c8720>] (vfs_ioctl+0x70/0x8c) from [<c00c8d8c>] (do_vfs_ioctl+0x558/0x5c4)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526550] [<c00c8d8c>] (do_vfs_ioctl+0x558/0x5c4) from [<c00c8e2c>] (sys_ioctl+0x34/0x54)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526611] [<c00c8e2c>] (sys_ioctl+0x34/0x54) from [<c0030f40>] (ret_fast_syscall+0x0/0x2c)
03-22 07:46:36.426 D/kernel ( 0): [ 16.526641] ---[ end trace 1b75b31a2719ed1e ]---
AOL_main.ap.bin
Code:
03-22 07:46:51.700 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:51.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:52.700 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:52.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:53.707 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:53.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:54.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:54.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:55.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:55.762 W/AudioSystem( 2120): AudioPolicyService not published, waiting...
03-22 07:46:56.262 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:56.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:57.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:57.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:58.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:58.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:59.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:59.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:00.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:00.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:01.270 W/AudioSystem( 2120): AudioPolicyService not published, waiting...
03-22 07:47:01.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:01.770 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:02.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:02.770 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:03.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:03.770 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:04.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:04.778 I/ServiceManager( 2120): Waiting for service media.audio_policy...
I hope this is not hardware failure.
P.S.: All logs are attached.
I'm afraid that you erased your pds partition. Have you made a backup of it in the past by any chance?
To list content of your pds block, boot to OR and in console or adb shell do:
Code:
mkdir /pds
mount /dev/block/mtdblock5 /pds
ls -lR /pds
In the current state, you should be able to boot the system if you disable the panic daemon (comment out the lines 496-501 in /system/etc/rootfs/init.mapphone_umts.rc - https://github.com/nadlabak/android...rebuilt/etc/rootfs/init.mapphone_umts.rc#L496 ). But your radio won't work.
It looks like it's everything ok with pds partition. After mounting pds partition I got this:
Code:
# ls -lR /pds
/pds:
drwxrwx--- 1 radio radio 2048 Mar 22 07:22 bp_nvm
drwxrwx--- 1 radio radio 2048 Mar 21 09:15 comm_drv
drwxrwx--- 1 root root 2048 Jan 1 1970 lost+found
drwxrwx--- 1 radio shell 2048 Mar 21 09:15 opprof
drwxrwxr-x 1 9000 9000 2048 Mar 21 09:09 public
I now disabled panic deamon and now my phone stuck at boot animation.
If the listing above is complete, then the state of your pds partition is far from OK.
It has been obviously erased and now contains only empty folders created during boot.
Your boot is currently stalled at "Waiting for service media.audio_policy" - the successful audio driver initialization depends on some files in /pds...
The problem with pds content is that some files there are unique for each phone. Namely e.g. /pds/bp_nvm/File_PDS_IMEI (each phone has to have unique IMEI) and also e.g. /pds/wifi/nvs_map.bin (contains unique wifi MAC address). Wile the wifi MAC is not a big issue, I'm afraid that no one will be willing to give you his file with his encoded IMEI number. I'm also not sure if the IMEI files can be actually used on a different phone other than the one for which they've been generated.
Woops, this is the whole output of ls -lR /pds
Code:
# ls -lR
.:
drwxrwx--- 1 radio radio 2048 Mar 22 09:51 bp_nvm
drwxrwx--- 1 radio radio 2048 Mar 21 09:15 comm_drv
drwxrwx--- 1 root root 2048 Jan 1 1970 lost+found
drwxrwx--- 1 radio shell 2048 Mar 21 09:15 opprof
drwxrwxr-x 1 9000 9000 2048 Mar 21 09:09 public
drwxrwx--- 1 system system 2048 Mar 21 09:15 security
drwxrwx--x 1 wifi wifi 2048 Mar 21 09:15 wifi
./bp_nvm:
-rw-rw-rw- 1 radio radio 1517 Mar 22 06:37 NVM_Daemon_MD5
./comm_drv:
-rw-rw---- 1 radio radio 2964 Mar 21 09:15 mmins_settings.cfg
./lost+found:
./opprof:
./public:
drwxr-x--- 1 9000 9000 2048 May 26 2011 battd
./public/battd:
./security:
./wifi:
A lot of folders are empty...and the only backup I have is nandroid backup. But nandroid doesn't backup pds partition.
So...that means I can't bring my phone back to life?
I have the same problem:
Milestone-Recovery:/
# ls pds/ -R
pds/:
bp_nvm lost+found public wifi
comm_drv opprof security
pds/bp_nvm:
NVM_Daemon_MD5
pds/comm_drv:
mmins_settings.cfg
pds/lost+found:
pds/opprof:
pds/public:
battd
pds/public/battd:
pds/security:
pds/wifi:
Milestone-Recovery:/
I don't have the file: /system/etc/rootfs/init.mapphone_umts.rc
# ls /system/etc/
01_Vendor_ti_omx.cfg location.cfg
NOTICE.html.gz media_profiles.xml
apns-conf.xml motorola
bluetooth nuance
bluez permissions
cameraCalFileDef5M.bin photoworkshop
cameraCalFileDef8M.bin ppp
dbus.conf pvasflocal.cfg
dhcpcd pvplayer.cfg
event-log-tags pvplayer_mot.cfg
excluded-input-devices.xml security
firmware updatecmds
gpsconfig.xml vold.conf
hosts vold.fstab
init.d wifi
init.goldfish.sh
Milestone-Recovery:/
My phone is now garbage? can i utilize it for gps navigation?
can i clone pds directory from an low cost android phone?
Qwewq!
When checking for the sake of precaution I found that while the system is running my pds is mounted at mtdblock0, not mtdblock5. Latest unofficial/nightly cm7 rc1 posted on xgraphs a few days ago.
Just wondering if this is ok and if pds can be backed up by using
Code:
dd if='proper mtdblock' of=/sdcard/pds.img
while the system is running and restored by reversing input and output files. Because in OR pds can be mounted by mtdblock5 while mtdblock0 gives error (invalid argument). A bit odd.
Unlike the normal running system that shows only subset of mtd blocks, OpenRecovery makes all mtd blocks accessible, that's why the numbers are different.
Use
Code:
cat /proc/mtd
to see the list of available mtds.
In OR, mtdblock0 is mbmloader - that mtd block does not contain any filesystem, so it can't be mounted.
I simply use tar to backup already mounted pds
Code:
tar -cf /sdcard/pds.tar pds
dd should work as well.
i also have this problem recently.. i just swipe data.. it fixed it.. every time that it bootloops.. i always swipe the data.. it it will boot up normally..
honestly i really new to this andriod thing and i dont understand that the codes are..
but it works..
But this is not the same problem I have. I don't have some files needed to work and only motorola can replace it with original files. I sent my phone to service center two weeks ago and this friday I got my phone back. They said that my phone was in water and they can repair it for 240€. What the hell?! They also destroyed the power button and wolume down button. The phone doesn't charge anymore. If I connect it to wall changer it stucks on Motorola logo and flash turns on(the light, where you connect wall charger into phone, is off). If I connect my phone to usb the light, where you connect wall charger into phone, turned on, but phone itself doesn't. The service center additional broke my phone instead of repairing it. I will send my phone back to service center and if they won't repair it to at least that state, as it was before, I will kick their asses.
i almost got the same prob now..
tried to update my milestone to 2.2.1
after the flash and during the reboot..
there's a message on the black screen telling that it is BP panic..
tried to reflash the same sbf and other sbf still the message still remains..
what is the reason for this??
how to fix this..?
i could restore from nandriod back up but resorting to unknown baseband and imei..
hopless.. poor milestone
I have similar problem. I tried flash official sbf, CM 7, Gingerbread MIUI and CM9.
Logs are attach to post.
Those are logs of the system booting up and your phone charging. If you were having a bootloop problem, I doubt the charging log would be as easy to read as it is.
Also, are you using a Milestone, or an XT?
This is Milestone A853.
I only asked because I see a few extra modules loading (compared to my device) and they say XT in their names.
I honestly don't know what's wrong. Hopefully someone more knowledgeable than I can help you.
The "xt" in module names stands for xtables, the firewall implemented in the Linux kernel.
Sent from my Milestone
Maybe try to flash only bootloader? Have you tried it?
TapaTalked from MotoStone
Moving to general section
Sent from my X8 using xda premium
I have a RAZR i with the standard UK 4.1.2 ROM. Sometimes I've had low memory problems or periods where the battery runs down unexpectedly. I recently started experiencing severe memory shortage after running with data disabled and poked around a bit. What I discovered was a large number of app_process instances taking 8M each.
From what I can tell, I should not see these. Android runs this process but it loads Java code into itself and changes personality. So while there's plenty of app_process instances running, they don't show up as such when you do a ps.
I found this out the hard way running killall app_process :/
But I can use this to kill off any of these "zombie" app_process instances: ps | grep app_process | busybox awk '{print $2}' | xargs kill
Running with data disabled seems to make these happen fairly reliably. Made me suspect something was being spawned to look for something on the network but failed due to a lack of data and then... got stuck instead of exiting?
I've disabled a few things on this ROM before. I think ModemStats or similar was a problem once before (chewing up CPU).
Has anyone seen this?
Is there something I can capture that would help diagnose the cause (I've heard of a logcat? maybe ps output?).
a1291762 said:
...Is there something I can capture that would help diagnose the cause (I've heard of a logcat? maybe ps output?).
Click to expand...
Click to collapse
sure, setup ADB and plug your device with a micro-usb cable on pc. Now you can logcat and also grep your favorit process.
Did you try limiting your backgroundprocesses under Developer-Options > backgroundprocess-limit ?
I use all the time a limit of 4 processes and have no memory problems (fyi: it will fall back to standard-setting after reboot)
Use the app Greenify to hibernate the apps you dont use daily
Enviado desde mi XT890 mediante Tapatalk
So... Greenify and limiting background "apps" can't help here because app_process isn't an app, it's a system process.
And it seems logcat isn't very useful when run after-the-fact? Oh it seems you can't run it except as root from Android 4.1 onwards. I've now got catlog recording so maybe next time I'll get something useful - assuming my SD card doesn't fill up first.
And of course now that I'm trying to _look_ at the problem, it's happening less frequently >:|
Amm app process are services, with the greenify app kills the services.....
If you havent root, well, remove the task on recent app list, force detention of the apps manually, and so on
Enviado desde mi XT890 mediante Tapatalk
Please don't spread misinformation. app_process is a system process. It is not even visible at the Android layer. Every app starts as an app_process instance. Greenify cannot even see it, let alone control it.
The good news is I have a logcat. The bad news is it's a 37Mb file and both the system ui and logcat app died due to lack of memory. I have second logcat fr when I noticed but the end of the first one if probably more useful. Having trouble reading the file on my phone. Will investigate more when I get home tonight.
bug2go is evil???
So app_process is AndroidRuntime. I see various AndroidRuntime START messages. Looks like normal starting of apps. Until 16:24 on 03-22.
Code:
03-22 03:30:04.822 D/AndroidRuntime(29699): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:35:03.670 D/AndroidRuntime(31593): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:35:03.670 D/AndroidRuntime(31592): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:38:03.542 D/AndroidRuntime(31650): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:38:03.552 D/AndroidRuntime(31651): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:23:10.850 D/AndroidRuntime( 1024): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:23:10.850 D/AndroidRuntime( 1025): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:41:29.170 D/AndroidRuntime( 2245): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:27:38.730 D/AndroidRuntime( 4879): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:41:39.630 D/AndroidRuntime( 5729): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:41:39.630 D/AndroidRuntime( 5730): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:30.350 D/AndroidRuntime( 6042): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:35.710 D/AndroidRuntime( 6064): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:35.910 D/AndroidRuntime( 6074): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.050 D/AndroidRuntime( 6079): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.320 D/AndroidRuntime( 6098): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.340 D/AndroidRuntime( 6087): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.400 D/AndroidRuntime( 6102): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.620 D/AndroidRuntime( 6105): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.690 D/AndroidRuntime( 6111): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.860 D/AndroidRuntime( 6133): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.950 D/AndroidRuntime( 6136): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
...
03-22 16:24:48.350 D/AndroidRuntime( 6650): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.350 D/AndroidRuntime( 6654): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.530 D/AndroidRuntime( 6744): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.610 D/AndroidRuntime( 6670): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
Something is running com.android.am.Am over and over again.
Code:
2014-03-20-08-45-47.txt|417176| 03-22 16:24:38.060 D/AndroidRuntime( 6111): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417215| 03-22 16:24:38.380 D/AndroidRuntime( 6133): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417216| 03-22 16:24:38.410 D/AndroidRuntime( 6136): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417225| 03-22 16:24:38.620 D/AndroidRuntime( 6140): Calling main entry com.android.commands.am.Am
Am seems to be an android tool to run shell commands. What's being run?
Code:
03-22 16:24:48.440 D/su ( 6756): su invoked.
03-22 16:24:48.440 D/su ( 6756): Allowing shell.
03-22 16:24:48.440 D/su ( 6756): 2000 /system/xbin/su executing 0 showmap using binary showmap : showmap 129
03-22 16:24:48.440 E/su ( 6756): exec failed with 2: No such file or directory
Hm... Running a binary that doesn't exist lots and lots of times? That can't be a coincidence. Looks like app_process doesn't properly clean up in this case.
But what is causing all this in the first place? I found this.
Code:
03-22 16:24:29.600 I/bug2go-bugreport( 6037): bugreport started
03-22 16:24:29.610 I/bug2go-bugreport( 6037): reportId=2014-03-22_16-24-29.000+1000
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Available space in /storage/sdcard0/bug2go is 1227 MB
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Required space is 50
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Storing report to /storage/sdcard0/bug2go/[email protected]_16-24-29.000+1000
...
03-22 16:24:30.690 W/ActivityManager( 384): Unable to start service Intent { act=motorola.intent.action.BUG2GO.BUGREPORT.START typ=text/plain (has extras) }: not found
Now that's odd. The bug2go apk is something I had previously removed. But the 2 bug2go binaries in /system/bin were still there. I can't see what triggered this (unless it's that last line, some kind of period attempt to run the now-missing bug2go app). Scrolling up in the logs I see... nothing but wifi scanning. My phone was suspended at the time so nothing was happening.
I've removed the bug2go binaries from /system/bin. That seems to be the source of the problem so maybe that'll fix things?
I also got a log after I noticed my phone was bad. It shows the last showmap error.
Code:
03-22 16:25:33.300 D/su (8732): su invoked.
03-22 16:25:33.300 D/su (8732): Allowing shell.
03-22 16:25:33.300 D/su (8732): 2000 /system/xbin/su executing 0 showmap using binary showmap : showmap 28103
03-22 16:25:33.300 E/su (8732): exec failed with 2: No such file or directory
And then, bug2go either gives up or finishes.
Code:
03-22 16:26:16.850 I/dumpstate(6054): done
03-22 16:26:16.850 I/bug2go-bugreport(6037): Dropping from root user to log user
So that at least explains why the phone doesn't ground to a permanent halt and why I can kill off these processes and have the phone continue to work.
Aha! It's actually dumpstate that causes the bug. It's run by bug2go but also by 'adb bugreport'. It tries to run showmap on... each running process? But since I don't have that binary, it leaves behind all the app_process instances. I ran 'adb bugreport' just now and it caused my phone to reboot!
So removing the bug2go binaries should stop this from being a problem but I'm kind of stumped as to why I have 'dumpstate' but not 'showmap' on my phone...
Hi,
Since about 4.4.3 (possibly 4.4.2?) wifi-tethering broke.
logcat says:
Code:
D/AFWall ( 3615): OS reported AP state change: 11 -> 12
D/AFWall ( 3615): isWifiApEnabled is false
E/SoftapController( 1320): Cannot update "/data/misc/wifi/hostapd.conf": Permission denied
E/WifiStateMachine( 1837): Exception in softap start java.lang.IllegalStateException: command '79 softap set wlan0 AndroidAP broadcast 6 wpa2-psk [scrubbed]' failed with '400 79 SoftAP command has failed'
E/SoftapController( 1320): SoftAP is not running
D/SoftapController( 1320): Softap fwReload - Ok
D/SoftapController( 1320): Softap fwReload - Ok
D/dalvikvm( 3615): GC_CONCURRENT freed 390K, 11% free 12321K/13772K, paused 4ms+1ms, total 18ms
I/AFWall ( 3615): Now assuming 3G connection (non-tethered)
E/SoftapController( 1320): Cannot update "/data/misc/wifi/hostapd.conf": Permission denied
E/WifiStateMachine( 1837): Exception in softap re-start java.lang.IllegalStateException: command '83 softap set wlan0 AndroidAP broadcast 6 wpa2-psk [scrubbed]' failed with '400 83 SoftAP command has failed'
D/AFWall ( 3615): OS reported AP state change: 12 -> 14
D/AFWall ( 3615): isWifiApEnabled is false
This bug is reported on code.google.com but the only suggested solution is deleting /data/misc/wifi and reboot which didn't work for me.
I even chmoded 777 /data/misc/wifi and hostapd.conf but without any success.
I'm running a very recent nightly (a few days old).
Any thoughts?
Thank you.