Database Info

Wifi not working cm9 based ics roms on international Sim(lg-p999dw)

Wifi not working cm9 based ics roms on international Sim(lg-p999dw)
Any one have this issues?
Any one have how to fix idea?
Wifi working us sim or not sim state
Logcat:
E/WifiStateMachine( 1597): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down broadcast running multicast]} failed with code 501 : {Flag unsupported}
03-12 00:00:22.926 I/wpa_supplicant( 7483): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
03-12 00:00:22.986 E/WifiConfigStore( 1597): Error parsing configurationjava.io.FileNotFoundException: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory)
Sent from my LG-P999 using xda premium

[Q] Tablet Help

Hi.
I need some help trying to fix WiFi on a tablet I was given to fix.
Its some chinese thing so off to a good start!
So its an A13 Allwinner based tablet.
I have re-flashed it with the same firmware that was on it when I got it and the wifi is still not working.
Wifi just wont turn on.
I have done some digging and found that the tablet uses an RTL8188ETV chip.
The module thats being loaded on the tablet is 8188eu.ko IS that right? Or should it be a 8188etv.ko module that I need?
Diagnostic wise, I can see some errors in the error log like:
E/WifiHW ( 159): insmod 8192cu ko failed!
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
E/WifiHW ( 159): timeout, register netdevice wlan0 failed.
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
E/WifiHW ( 159): timeout, register netdevice wlan0 failed.
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
I tried to manually load the 8188eu.ko but all i got was "file already exists"
Anyone got any ideas on how I can get this thing going again?

Seansmit17 said:
Hi.
I need some help trying to fix WiFi on a tablet I was given to fix.
[snip]
The module thats being loaded on the tablet is 8188eu.ko IS that right? Or should it be a 8188etv.ko module that I need?
[snip]
Anyone got any ideas on how I can get this thing going again?
Click to expand...
Click to collapse
This applies to something I'm working on right now. Did you ever find/figure out a solution?
Looks like Realtek supplies Linux (specifically Android-compatible) drivers on their website, but they don't have the ETV version explicitly: http://www.realtek.com/downloads/do...n=4&DownTypeID=3&GetDown=false&Downloads=true

[Q] WiFi connect possible, but no scanning?

Hi,
problem:
i can´t see any wifi networks, that im not connected to
i´m able to add manuelly any wifi network without problems.. wifi on those manually added networks, works perfect
notification of open networks is enabled.. and i got a notification that there is an open wifi network in range.. so scanning itself seems to work? but my device doesn´t show any network but the one im connected to.
EDIT: "MotoTool AIO" shows me at "SysInfo" -> "wifi" a wifi scan... so this seems really a problem on just displaying the wifi scan results on the device?!?!?
tools like "wifi analyzer" don´t show ANY network
what i tried/looked for, without a positive result:
wifi_display_on has still value 0 in settings.db
file WCNSS_qcom_wlan_factory_nv.bin is existing in /persists (http://forum.xda-developers.com/showpost.php?p=49656627&postcount=3)
flashed stock baseband (http://forum.xda-developers.com/showthread.php?t=2649763)
i did more.. but can´t remember everything.. im sorry...
im on latest gapps.. latest cm12 nightly.. (problem exists since some nightly in the summer of 2014)
im on moto g XT1032
i did not a clean install.. i just upgraded via adb sideload in TWRP (and i don´t really want to do a clean install)
after fixing systemUI Crash and launcher3 crash on myself (look: http://forum.xda-developers.com/showpost.php?p=58316659&postcount=768) i just have this problem (also no GPS Signal, tried to fastboot erasing modemst1 and modemst2)
im really really interested in finding the problem instead of just do a clean install..
so i also take a look at logcat.. and found those errors:
the errors:
I/wpa_supplicant(4981): CTRL_IFACE: Detach monitor /data/misc/wifi/sockets/wpa_ctrl_774-5\x00 that cannot receive messages
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
E/WifiHAL (774): wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-95
E/WifiHAL (774): wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
more details:
I/wpa_supplicant(4981): CTRL_IFACE: Detach monitor /data/misc/wifi/sockets/wpa_ctrl_774-5\x00 that cannot receive messages
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
I/wpa_supplicant(6513): Successfully initialized wpa_supplicant
I/wpa_supplicant(6513): rfkill: Cannot open RFKILL control device
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
I/wpa_supplicant(6513): rfkill: Cannot open RFKILL control device
D/WifiConfigStore(774): Loading config and enabling all networks
I/wpa_supplicant(6513): wlan0: CTRL-EVENT-SCAN-STARTED
D/WifiNative-HAL(774): Setting external_sim to 1
D/WifiStateMachine(774): Setting OUI to DA-A1-19
I/WifiNative-HAL(774): startHal
D/wifi (774): setting scan oui 0x977ece20
I/WifiHAL (774): ******HexDump len:0*********
I/WifiHAL (774): ******HexDump End***********
E/WifiHAL (774): virtual int WifiVendorCommand::create() ifindex obtained:29
E/WifiHAL (774): virtual int WifiVendorCommand::set_iface_id(const char*) ifindex obtained:29
I/WifiHAL (774): MAC_OUI - da:a1:19
D/WifiHAL (774): virtual int WifiVendorCommand::requestResponse(): request a response
E/WifiHAL (774): wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-95
D/RttService(774): SCAN_AVAILABLE : 3
D/WifiScanningService(774): SCAN_AVAILABLE : 3
D/RttService(774): DefaultState got{ when=-1ms what=160512 target=com.android.internal.util.StateMachine$SmHandler }
D/WifiScanningService(774): DefaultState got{ when=-1ms what=160006 target=com.android.internal.util.StateMachine$SmHandler }
I/WifiNative-HAL(774): startHal
D/wifi (774): getting scan capabilities on interface[0] = 0x977ece20
E/WifiHAL (774): wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
D/wifi (774): failed to get capabilities : -3
E/WifiScanningService(774): could not get scan capabilities
D/WifiMonitor(774): startMonitoring(p2p0) with mConnected = true
D/class com.mobisystems.wifi_direct.StartWifiDirectReceiver(6198): Wifi notification received.
D/class com.mobisystems.wifi_direct.StartWifiDirectReceiver(6198): WIFI State Changed.
Click to expand...
Click to collapse

added important info in first post!

[SOLVED][Q] WiFi won't turn on

All of a sudden, on Stock + Root TF700T, WiFi won't turn on. I highly doubt that this is related to my WiFi router ... the WiFi won't even enable on the tablet, and I can't even see a MAC address in About Tablet section.
I also did some digging and have some additional detail, but I cannot find a solution.
logcat:
Code:
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such file or directory)'
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2767): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2767): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2767): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2767): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 3ms+3ms, total 57ms
D/AsusBrightnessManager( 489): br transform : 35 -> 13
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '46 softap fwreload wlan0 STA' failed with '400 46 Softap operation failed (No such file or directory)'
E/WifiStateMachine( 489): Failed 6 times to start supplicant, unload driver
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '48 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 48 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2792): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2792): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2792): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2792): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 2ms+1ms, total 22ms
W/NvCpuClient( 489): Failed to bind to service
D/AsusBrightnessManager( 489): br transform : 35 -> 13
E/WifiHW ( 489): Supplicant not running, cannot connect
W/NvCpuClient( 489): Failed to bind to service
Also, output from netcfg:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 76:ad:93:6b:c9:b7
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
And here is output of my wpa_supplicant.conf:
Code:
[email protected]:/ # cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
And I searched the entire filesystem for "nl80211" and found nothing.
Does anyone have suggestions on where to go next? Did my driver somehow get deleted, or am I just not looking for the right thing?
Thanks.

I will use this question in the future as an example of how to ask for support properly. Unfortunately I don't have a solution for you, but you could check the files in your /data/misc/wifi, maybe you can find something unusual. Your MAC address should come from some file on the FAT filesystem on /dev/block/mmcblk0p5 - I'd recommend making an image of it as a backup and then analyze the image.

_that said:
I will use this question in the future as an example of how to ask for support properly.
Click to expand...
Click to collapse
I provide Enterprise-level support to software devs working in the Cloud and particularly on CentOS/RHEL Linux servers. This is why I know how to ask for help properly.
Well, since I can't find much, and there aren't any definitive answers here, my next thoughts are:
1) Something is seriously jacked up on the filesystem, possibly corrupted driver, possibly something worse. Hopefully, this is the case, because a software problem is possible to fix.
2) The WiFi radio is permanently damaged, or "burnt out".
In the hopes that it's something more like software, I'm going to reimage. I just need to decide what ROM to use. Not having network connectivity will make the prep for this a bit more challenging, but I can work through it using a MicroSD card.
If it's #2, well then I suppose I will have wasted my time reimaging and will be on the market for a new tablet ... and I need to get on that right away because I need to travel soon. Any suggestions are welcome ... I'd like a 9" or 10" tablet and it must have an HDMI out (micro preferred) and be able to handle 1080p video.
Thanks.

[SOLVED]
I am having a heckuva time even doing what I described above.
-I had never unlocked the bootloader before, so when I tried the ASUS unlock util v8, it gave error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE"
-I tried the ASUS unlock tool v7, and was finally able to install it but when I run and select Unlock I get an error that there is no network connection (FFS that's what I'm trying to resolve!)
-I can't get into recovery, I just get the Android guy with "ERROR!" when I enter fastboot and select "RCK".
My only option is to go back to Stock. So, I tried this:
http://forum.xda-developers.com/showthread.php?t=1833212
The steps in that post result in the same Android guy with the "ERROR!" screen ... not a very helpful error msg.
So, I tried this, and used the stock firmware from ASUS. (NOTE: I downloaded "ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)" directly from ASUS after I read their notes on where to check for which one you need ([Settings]-->[About tablet]-->Build number).):
http://www.transformerforums.com/fo...e-firmware-tf700-tf701-tf300-tf101-tf201.html
From that post ^^ I did Method B: Flash from MicroSD. I extracted the .zip I downloaded from ASUS, and renamed the new zip EP201_768_SDUPDATE.zip per the GUIDE linked above.
I put in my MicroSD, went back into fastboot, and selected "RCK". It was at this point that I began typing the above. Total time to get to this point was about 90 minutes!
-----
FINALLY, for the first time, I saw a progress bar under the Android guy, and he had gears turning in his belly.
*INSERT SIGH OF RELIEF HERE*
As I was typing out all the above, progress bars were moving, and a few reboots happened. I expected that I would be fully back on Stock ROM, and that my data would have been wiped. I never ran a data wipe, I just assumed the ASUS installer would do that by default.
Well, it didn't wipe data. But, what it did do: restore all my device drivers!! After about 10 minutes, and 2-3 reboots, Android loaded with my existing desktop and settings, and the WiFi connected right away!!
So, this fixed it. I documented the above so anyone (even me, months from now) having a similar problem might be able to use these steps.
WOO HOO!

lost root
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.

CaptainRewind said:
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
Click to expand...
Click to collapse
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

sbdags said:
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Yep, I had to do that anyway because I wanted to do a full Titanium Backup first. Still, I'm moving to CM now.

[ACKNOWLEDGED BUG] Android 5.1 Camera can't connect... ever

It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
Acknowledged bug by google https://code.google.com/p/android/issues/detail?id=160609

cthulu said:
It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?

zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes

cthulu said:
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes
Click to expand...
Click to collapse
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.

zagorteney said:
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
Click to expand...
Click to collapse
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?

PHPanos said:
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
Click to expand...
Click to collapse
And this was happening immediately after booting your phone? Then must be hardware. ?

It works fine everytime I reboot, for xx minutes. It's difficult to say for how long but not too long. I see that "Trusted face" unlock stops working and that's a signal the whole camera subsystem is gone. Everything else works just no camera access from any app is possible.

zagorteney said:
And this was happening immediately after booting your phone? Then must be hardware. ��
Click to expand...
Click to collapse
No. It works at first. Then after a few times of locking/unlocking the phone and opening the camera app and switching to front camera it shuts down. The problem goes away after a reboot but it comes back again after a while.
cthulu: We have both the same problem.

Same here for me since upgrading to 5.0 every now and then i must reboot my phone in order to fix it.This is really annoying maybe we should wait for a new camera app by google ?

Same issue
Hi guys,
This has been the problem for me since 5.0 . I thought maybe its just me. But after a while, the camera stops working. I assume this is a s/w issue since the phone was fine in Kitkat. Even in 5.1 the issue persists.

I am also getting frequent "can't connect to camera" since 5.1. Nexus 5.

Do you know if there's an issue for this in Google's issue tracker? I'm sure they won't check xda forums for bug reports.
I've clicked a few times to send the error to Google when starting the camera but I honestly don't think they're checking those...
I hoped full wipe will fix this but as it happens to the folks who did full wipe I'm rather not going to do it yet...

Already reported here https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609

zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.

THRUSTer said:
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.
Click to expand...
Click to collapse
You are on a right direction. Just start to read a little more careful.

Happens the same for me.
Some days ago i see that the face Trusted face have Stop. So, now i desible the Trusted face, clear data of camera app e until now (about 2 hours) the camera works fine, without any shut up.
Try you too, i think that the problems are in the Smart lock.

Many people have this issue since they moved to 5.1
'Hardware defect' and 'no full wipe' were told to be the culprit straight away, but looking at the bug report that seems unjustified, especially given the number of reports with exactly this issue.
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
zagorteney said:
Flash completely and it will fix it.
Click to expand...
Click to collapse
zagorteney said:
Then must be hardware. ?
Click to expand...
Click to collapse
So please be a bit more thorough in your advice....

Can't connect to camera error Nexus 5 Android 5.1
Hi gays, I am new here. I keep getting the ' can't connect to camera' error on my Nexus 5 Android 5.1, and I tried everything that is suggested here and it did not help. I turned off Face unlock, uninstall Viber and install again, cleared cache of the camera and force stop and everything else. Only help restart the device. I succeeded to catch the logcat with the error. Here is the logcat:
04-02 21:19:26.744 724-2687/? I/ActivityManager﹕ START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher bnds=[849,1532][1050,1784] (has extras)} from uid 10019 on display 0
04-02 21:19:26.747 724-2687/? V/WindowManager﹕ addAppToken: AppWindowToken{2498ae08 token=Token{83da7ab ActivityRecord{3a47c5fa u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher t32}}} to stack=1 task=32 at 0
04-02 21:19:26.751 724-819/? V/WindowManager﹕ Based on layer: Adding window Window{15bd6123 u0 Starting com.google.android.GoogleCamera} at 3 of 9
04-02 21:19:26.824 724-1360/? I/ActivityManager﹕ Start proc 22932:com.google.android.GoogleCamera/u0a42 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
04-02 21:19:26.837 1361-3270/? W/GsaThreadFactory﹕ Not creating another thread for Background Blocking because there are already 30
04-02 21:19:26.876 22932-22932/? W/ResourcesManager﹕ Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
04-02 21:19:26.935 22932-22932/? W/CAM_Log﹕ Tag SessionStatsCollector is 2 chars longer than limit.
04-02 21:19:26.989 22932-22932/? I/CameraManagerGlobal﹕ getCameraService: Reconnecting to camera service
04-02 21:19:27.254 22932-22979/? I/CAM2PORT_AndCamAgntImp﹕ Opening camera 0 with camera1 API
04-02 21:19:27.266 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 116
04-02 21:19:27.268 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.289 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 117
04-02 21:19:27.290 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.301 193-1682/? I/Camera2ClientBase﹕ Camera 0: Opened. Client: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.302 22932-22992/? W/CAM_PhotoData﹕ Zero dimension in ContentResolver for /storage/emulated/0/DCIM/Camera/IMG_20150402_180439.jpg:0x0
04-02 21:19:27.303 193-1682/? D/mm-camera-intf﹕ mm_camera_open: dev name = /dev/video1, cam_idx = 1
04-02 21:19:27.304 206-206/? I/mm-camera-sensor﹕ module_sensor_start_session:583 session 1
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ csiphy_open:126 VIDIOC_MSM_CSIPHY_IO_CFG failed
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:335 failed rc -1
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_close:2499 VIDIOC_MSM_SENSOR_CFG failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:500 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:612 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:617 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_get_capabilities:1632 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_query_mod:2421 failed rc -4
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_hardware_process_command:254: failed, subdev not opened
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_query_mod:268: failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_query_mod:1697] error in cpp query mod
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_module_set_session_data:2666 max delay 2 report dSelay 1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ isp_set_session_data: Session could not be found!
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_get_params_for_session_id:178, failed, session_id=0x1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_set_session_data:329, failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_set_session_data:1928] error in cpp set_session_data
04-02 21:19:27.307 206-206/? D/mm-camera﹕ module_faceproc_set_session_data:1836] Per frame control 2 1
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_sensor_stop_session:636 session 1
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_deinit_session:526 ref count 0
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:664 failed
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:669 failed
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:462, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:504, info: session 1 stopped.
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:322, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:361, info: session 1 stopped.
04-02 21:19:27.308 206-206/? E/mm-camera﹕ main: New session [1] creation failed with error
04-02 21:19:27.308 193-1682/? D/mm-camera-intf﹕ mm_camera_open: opened, break out while loop
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ camera_open: mm_camera_open err = -1
04-02 21:19:27.308 193-1682/? E/QCamera3HWI﹕ camera_open failed.
04-02 21:19:27.308 193-1682/? E/Camera3-Device﹕ Camera 0: initialize: Could not open camera: No such device (-19)
04-02 21:19:27.308 193-1682/? E/Camera2ClientBase﹕ initialize: Camera 0: unable to initialize device: No such device (-19)
04-02 21:19:27.308 193-1682/? E/CameraService﹕ connectFinishUnsafe: Could not initialize client from HAL module.
04-02 21:19:27.308 193-1682/? I/Camera2Client﹕ Camera 0: Closed
04-02 21:19:27.309 193-1682/? I/Camera2ClientBase﹕ Closed Camera 0. Client was: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.313 193-1682/? W/AudioFlinger﹕ session id 116 not found for pid 22932
04-02 21:19:27.317 193-1682/? W/AudioFlinger﹕ session id 117 not found for pid 22932
04-02 21:19:27.318 22932-22979/? W/CameraBase﹕ An error occurred while connecting to camera: 0
04-02 21:19:27.318 22932-22979/? E/CAM2PORT_AndCamAgntImp﹕ RuntimeException during CameraAction[OPEN_CAMERA] at CameraState[1]
java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.<init>(Camera.java:497)
at android.hardware.Camera.open(Camera.java:342)
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$CameraHandler.handleMessage(AndroidCameraAgentImpl.java:370)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
04-02 21:19:27.371 22932-23015/? D/OpenGLRenderer﹕ Use EGL_SWAP_BEHAVIOR_PRESERVED: true
04-02 21:19:27.377 22932-22932/? D/Atlas﹕ Validating map...
04-02 21:19:27.381 724-1360/? V/WindowManager﹕ Adding window Window{312f9c81 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 3 of 10 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.387 22932-22932/? W/CAM_CameraActivity﹕ Camera open failure: HIST_ID0_-1_1_HEND
04-02 21:19:27.387 22932-22932/? E/CAM_Util﹕ Show fatal error dialog
04-02 21:19:27.402 724-2689/? V/WindowManager﹕ Adding window Window{302ae167 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 4 of 11 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.406 22932-22932/? D/WearableClient﹕ WearableClientImpl.onPostInitHandler: done
04-02 21:19:27.431 22932-23015/? I/Adreno-EGL﹕ <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/14/15, ab0075f, Id3510ff6dc
04-02 21:19:27.432 22932-23015/? I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-02 21:19:27.444 22932-23015/? D/OpenGLRenderer﹕ Enabling debug mode 0
04-02 21:19:27.487 22932-22932/? I/CAM_UsageStats﹕ PlayLogger.onLoggerConnected
04-02 21:19:27.512 724-2689/? D/WifiService﹕ acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ onPreviewUIReady
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ attempted to start preview before camera device
04-02 21:19:27.518 724-851/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source 10007 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=10:fe:ed:4e:a3:ae RSSI=-47
04-02 21:19:27.574 724-819/? I/ActivityManager﹕ Displayed com.google.android.GoogleCamera/com.android.camera.CameraLauncher: +790ms
Please HELP, it's really annoying
Best regards.

meranto said:
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
So please be a bit more thorough in your advice....
Click to expand...
Click to collapse
Nope..
https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609
has a lot of people who didn't use face unlock and still experienced the issue.

Replay
Hi meranto,
thanks for the replay. I did not use face unlock and the issue still show up