Team Inferno presents...
Zephyr-Nit3m0d
About:
Since elgin started working on bringing us the 3.0 kernel, I was inspired to try and learn a bit more myself. This thread is the process of said learning experience and me sharing the outcome with everyone here. Oh also, I waited for elgin to release before I did any releasing myself out of respect for him and the work he put into getting this working, which is why I never just raw built it from his repo for others to use. Congrats on the awesome release and thanks for all the work you've done for us.
Features:
/This kernel is heavily based on elgin's repo right now, I might start drifting away from it more and more as I progress on my own developments./
-Sweep2wake (sweep left>right across the bottom of the screen to wake, vice versa to sleep)
-Optimized a la KangBang7x30-3.0
-Bcmdhd enabled
-XZ compression
-optimized SLUB allocator
-2way call recording hack (thanks to flinny)
-more to come (hopefullly)
Enabling/Disabling SWEEP2WAKE:
terminal emulator:
cjoliver said:
echo '0' > /sys/android_touch/sweep2wake
This will disable the sweep2wake.
Other options are.
0 for disabled.
1 for enabled.
Click to expand...
Click to collapse
Not Working:
-Let's find out
-Everything in elgin's kernel for unofficial cm10(ie ffc, etc)
Thanks & Credits:
Elginsk8r
Flemmard
Virtuous Team
Flinny
Andromadus
synergye(KangBang)
amidabuddha
nk111
show-p1984
those who have been forgotten
and all of XDA, for being XDA
My Source: https://github.com/SyNtheticNightmar3/htc7x30-3.0
Download:[EDIT: Dev-Host has since removed this file]
(NOTE: for the time being this is only compatible with elgin's CM10 rom, may there be more soon)
Side-Note: I don't know how often I'll be updating this, but as I decide to just play around with the kernel source, this will be updated as I make new discoveries, etc.
(Also OP may be made over; might not. Enjoy having kernels to choose from)
Reserved
Important please readI. Appreciation
There are many ways to show your support to us. You can:
Press the "Thanks" button.
Hit the donation button and help support the team
Wear our specially prepared banner
Share your opinion about my work and write some feedback in our threads.
Advertise our work to your friends, family, anyone who owns this device.
Rate our threads with 5 stars.
We appreciate all the support you give us, but we don't expect anything
II. Sharing
XDA-Developers.com is all about sharing. If you would like to use any part of our work, please feel free to do so but remember to do the following beforehand:
Inform - Please send us a PM or email telling us
Permission - Please, if you do not have permission from us, don't use it. Most of the time, we will allow you to, but if you don't get our permission first, we will report.
Credits - No one wants their work stolen. Please remember to give proper credits when using our work.
III. Support
If you have any issues or questions, please feel free to post them in the our threads. However, because all of us have social lives outside of XDA, your questions may not always be answered right away. Members who are more experienced in our work, please help out the ones who don't.
If you want to get the fastest and the best answer - ask the question in our threads instead of PM'ing us. Chances are, other users will be able to help you when Team Members don't have the time to.
IV. Updates
We are a busy team! Every Team Member has lives outside of XDA. You cannot expect us to sit in front of the computer all day and develop Android. Please do not ask for ETA's. The update will come when we release it. Sometimes, there is a good reason for why we have not released an update in a while. Please be patient with us, we will do as we promise. Updates will come.
V. Responsibilities
We are not responsible for your device! We do not guarantee that everything will work the way it's supposed to. Not every device is created equal, what might work on our devices may not work on yours or vice versa. Please be a responsible person when it comes to flashing. This is a mature site, don't act immaturely when your device becomes problematic. If you cry and blame us for "destroying" your device, we will laugh at you. Your device is your responsibility, act like it.
Thanks for choosing Team Inferno, we hope you enjoy our works as much as we enjoy working with them.
-Team Inferno-
OSN!!!!!!!
ffc is not working, i am using elgin's CM10 rom, also the screen is flashing when the phone is asleep, i think its a bug in the kernel v3
Lazybumx said:
ffc is not working, i am using elgin's CM10 rom, also the screen is flashing when the phone is asleep, i think its a bug in the kernel v3
Click to expand...
Click to collapse
It's basically the same as elgin's AOSP JB kernel but with additional features. He put in the OP that FFC isn't working.
I haven't seen my screen flashing yet though, it might after I get everything set up.
no that is a bug in cm10 right now. Same goes with the sensation or any htc device using official ics camera libs.
Synthetic.Nightmare, thanks for giving us another option. Also, it was really cool of you to wait for elginsk8r to release so you didn't steal his thunder. I wish XDA had more community conscious devs like you two.
Also, flashing!
Edit: Sweep to wake/sleep is amazeballs!
i hope this kernel will end up working for other ROMs. its working fine, so far
This is awesome! Thanks for all your hard work Synthetic. I know this is gonna be big!
Sent from my MyTouch 4G using xda app-developers app
Awesome! Can't wait! Do ya have project butter ported yet?
The 3.x kernel will only work on jb correct?
THEindian said:
Awesome! Can't wait! Do ya have project butter ported yet?
The 3.x kernel will only work on jb correct?
Click to expand...
Click to collapse
No to the first question. And yes to the second. There's yet to be an ICS aosp based rom adapted to work with the 3.0 kernel. I started on adapting synthetic_aospx a while back but existz decided to stick with the 2.6 kernel after 720p was fixed and explained that it would be a step back now rather than progressing (also it was benchmarking worse than 2.6) so I just stuck with the aospx kernel as well.
Sent from my myTouch 4G using xda app-developers app
Synthetic.Nightmare said:
No to the first question. And yes to the second. There's yet to be an ICS aosp based rom adapted to work with the 3.0 kernel. I started on adapting synthetic_aospx a while back but existz decided to stick with the 2.6 kernel after 720p was fixed and explained that it would be a step back now rather than progressing (also it was benchmarking worse than 2.6) so I just stuck with the aospx kernel.
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
I flashed it on my PACman jb port and WiFi doesn't work its stuck at turning on.
Sent from my myTouch 4g using xda premium
cnote74 said:
I flashed it on my PACman jb port and WiFi doesn't work its stuck at turning on.
Sent from my myTouch 4g using xda premium
Click to expand...
Click to collapse
i have met the same qus
Synthetic.Nightmare said:
(NOTE: for the time being this is only compatible with elgin's CM10 rom, may there be more soon)
Click to expand...
Click to collapse
WiFi works. Until you fix your rom for it, it wont tho.
Sent from my myTouch 4G using xda app-developers app
This is the log as WiFi works with elgins 3.0 kernel
10-13 10:14:58.534 I/WifiService(284): WifiService starting up with Wi-Fi enabled
10-13 10:14:58.534 D/WifiService(284): setWifiEnabled: true pid=284, uid=1000
10-13 10:15:10.346 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:11.347 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:12.348 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:13.349 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:14.350 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:14.350 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:15:18.304 D/WifiService(284): New client listening to asynchronous messages
10-13 10:15:23.348 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:24.349 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:25.340 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:26.341 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:27.342 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:27.392 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:15:32.477 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:15:37.175 W/WifiNormalizer(522): No specific device detected. Offset set to -7.
10-13 10:15:38.445 D/MccTable(473): WIFI_COUNTRY_CODE set to us
10-13 10:15:38.465 I/WifiService(284): WifiService trying to set country code to us with persist set to true
10-13 10:15:43.881 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:44.882 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:45.883 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:46.883 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:46.883 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:15:57.984 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:58.985 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:15:59.986 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:00.987 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:01.988 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:01.988 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:16:08.374 D/PicasaUploader(1320): wifiOnlyPhoto changed to true
10-13 10:16:08.374 D/PicasaUploader(1320): wifiOnlyVideo changed to true
10-13 10:16:13.029 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:14.030 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:15.031 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:16.032 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:17.033 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:17.033 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:16:17.053 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:16:29.055 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:30.056 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:31.057 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:32.058 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:32.058 E/WifiStateMachine(284): Failed 6 times to start supplicant, unload driver
10-13 10:16:43.208 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:44.209 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:45.210 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:46.211 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:47.212 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:47.212 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:16:58.293 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:16:59.294 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:00.285 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:01.286 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:02.287 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:02.297 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:17:13.368 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:14.369 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:15.370 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:16.371 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:17.372 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:17.372 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:17:17.392 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:17:29.404 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:30.394 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:31.395 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:32.396 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:17:32.396 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:19:27.208 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:19:39.230 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:19:40.231 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:19:41.232 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:19:42.233 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:19:42.233 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:19:47.258 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:19:59.270 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:20:00.271 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:20:01.272 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:20:02.273 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:20:02.273 E/WifiStateMachine(284): Failed 6 times to start supplicant, unload driver
10-13 10:24:01.955 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:02.956 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:03.947 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:04.948 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:05.949 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:05.949 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:24:22.025 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:23.026 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:24.027 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:25.028 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:26.029 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:26.029 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:24:31.044 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:24:43.056 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:44.046 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:45.057 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:46.048 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:24:46.048 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:24:51.103 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:25:23.461 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:24.462 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:25.463 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:26.464 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:26.464 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:25:37.524 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:38.525 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:39.526 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:40.527 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:41.518 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:41.518 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:25:52.609 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:53.610 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:54.611 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:55.612 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:56.613 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:25:56.613 E/WifiStateMachine(284): Failed 6 times to start supplicant, unload driver
10-13 10:26:07.644 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:26:08.645 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:26:09.646 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:26:10.647 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:26:11.648 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:26:11.648 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:33:17.051 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:18.052 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:19.053 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:20.054 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:21.055 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:21.055 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:33:26.100 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:33:38.112 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:39.113 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:40.114 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:41.115 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:41.115 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:33:46.140 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:33:58.151 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:33:59.152 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:00.153 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:01.154 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:01.154 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:34:17.220 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:18.221 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:19.222 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:20.223 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:21.224 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:21.224 E/WifiStateMachine(284): Failed to setup control channel, restart supplicant
10-13 10:34:26.269 E/WifiHW (284): Unable to open connection to supplicant on "wlan0": No such file or directory
10-13 10:34:38.290 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:39.281 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:40.292 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:41.293 E/WifiHW (284): Supplicant not running, cannot connect
10-13 10:34:41.293 E/WifiStateMachine(284): Failed 6 times to start supplicant, unload driver
Sent from my myTouch 4g using xda premium
cnote74 said:
that
Click to expand...
Click to collapse
Pastebin that... Also, I see it now and I'm pretty sure it can be easily fixed
Edit: Lol I meant put it in a pastebin in your post. I can read it just fine here but I'd rather not have a wall of log
Synthetic.Nightmare said:
Pastebin that... Also, I see it now and I'm pretty sure it can be easily fixed
Edit: Lol I meant put it in a pastebin in your post. I can read it just fine here but I'd rather not have a wall of log
Click to expand...
Click to collapse
Doesn't it look like the rom that he has isn't capable of doing bcmdhd?
THEindian said:
Doesn't it look like the rom that he has isn't capable of doing bcmdhd?
Click to expand...
Click to collapse
No it likely is if it works with the elginmod kernel. Its just when I turned on bcmdhd I turned it on with the same fw_path as the kangbang kernel (directly to vendor/firmware) it could very well be the reason WiFi doesn't work on his rom. Though I haven't really looked at the way his rom is set up so it could be something else as well.
Sent from my myTouch 4G using xda app-developers app
0.0 said:
i hope this kernel will end up working for other ROMs. its working fine, so far
Click to expand...
Click to collapse
How about the heating issue with audio playback??
Related
Well suddenly wiring will not enable on my nexus. Everything else works, I cleared userdata davlik and cache reinstalled my rom and still no go. So I flashed cm9 thinking it was a rom issue but it still will not enable. Any ideas?
Anybody..?
justanothernoob said:
Well suddenly wiring will not enable on my nexus. Everything else works, I cleared userdata davlik and cache reinstalled my rom and still no go. So I flashed cm9 thinking it was a rom issue but it still will not enable. Any ideas?
Click to expand...
Click to collapse
connect device to pc, 'adb logcat >> logcat-1.txt', enable wireless. paste it here so people might try to help you.
Looks to me like its saying wlan0 doesnt exist...
W/CommandListener( 110): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 110): Setting iface cfg
E/WifiStateMachine( 211): 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]} failed with code 400 : {Failed to set address (No such device)}
D/NetworkManagementService( 211): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 211): flags <[down]>
I/wpa_supplicant( 2079): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2079): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2079): wlan0: Failed to initialize driver interface
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiStateMachine( 211): Failed to setup control channel, restart supplicant
D/SoftapController( 110): Softap fwReload - Ok
W/CommandListener( 110): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 110): Setting iface cfg
D/NetworkManagementService( 211): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 211): flags <[down]>
E/WifiStateMachine( 211): 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]} failed with code 400 : {Failed to set address (No such device)}
I/wpa_supplicant( 2128): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2128): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2128): wlan0: Failed to initialize driver interface
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiHW ( 211): Supplicant not running, cannot connect
E/WifiStateMachine( 211): Failed to setup control channel, restart supplicant
justanothernoob said:
Looks to me like its saying wlan0 doesnt exist...
E/WifiStateMachine( 211): 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]} failed with code 400 : {Failed to set address (No such device)}
I/wpa_supplicant( 2128): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2128): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2128): wlan0: Failed to initialize driver interface
Click to expand...
Click to collapse
Try flashing a custom kernel like franco or fugumod.
I did that didn't fix it. I just put it all back to stock and locked the bootloader. Guess ill send it back...
justanothernoob said:
I did that didn't fix it. I just put it all back to stock and locked the bootloader. Guess ill send it back...
Click to expand...
Click to collapse
yeah, i would do that, if reflashing stock doesn't solve it. if it still happens, lock your bootloader and turn it in.
sorry we couldn't be of more assistance.
Yeah I've reflashed stock and locked boot loader hopefully Negri will rma it for me.
So my wifi was working fine monday after noon.....come home that night and it will not turn on. The only thing i though could be the culprit was the kernel i just flashed. I installed a known working kernel and it still would not come on. Did odin to stock still same result. Searched for hours for a solution and could only find a few posts of the same type of issues on various forums. So was wondering was this ever found to be a known issue or is a occasional defect............below is my logcat for the wifi, which i get no matter what rom or kernel im on.
W/CommandListener( 108): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 108): Setting iface cfg
D/NetworkManagementService( 170): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 170): flags <[down]>
E/WifiStateMachine( 170): Unable to change interface settings: java.lang.Illega
lStateException: Unable to communicate with native daemon to interface setcfg -
com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0
.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
I/wpa_supplicant( 2221): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2221): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2221): wlan0: Failed to initialize driver interface
E/WifiHW ( 170): Supplicant not running, cannot connect
E/WifiHW ( 170): Supplicant not running, cannot connect
E/WifiHW ( 170): Supplicant not running, cannot connect
E/WifiHW ( 170): Supplicant not running, cannot connect
E/WifiHW ( 170): Supplicant not running, cannot connect
E/WifiStateMachine( 170): Failed to setup control channel, restart supplicant
D/SoftapController( 108): Softap fwReload - Ok
W/CommandListener( 108): Failed to retrieve HW addr for wlan0 (No such device)
D/NetworkManagementService( 170): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 170): flags <[down]>
D/CommandListener( 108): Setting iface cfg
E/WifiStateMachine( 170): Unable to change interface settings: java.lang.Illega
lStateException: Unable to communicate with native daemon to interface setcfg -
com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0
.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
Midday bump for freshness
Sent from my Galaxy Nexus using xda premium
criptix said:
So my wifi was working fine monday after noon.....come home that night and it will not turn on. The only thing i though could be the culprit was the kernel i just flashed. I installed a known working kernel and it still would not come on. Did odin to stock still same result. Searched for hours for a solution and could only find a few posts of the same type of issues on various forums. So was wondering was this ever found to be a known issue or is a occasional defect............below is my logcat for the wifi, which i get no matter what rom or kernel im on.
Click to expand...
Click to collapse
See http://code.google.com/p/android/issues/detail?id=28036. The only partial workaround I've found is rooting, installing https://play.google.com/store/apps/details?id=com.fardjad.android.wifixmanager and rebooting/power cycling only when the wifi has been turned off successfully.
I tried both ROM which using latest 4.1.2 JellyBean, but found bugs when connecting wifi. It's always obtaining ip address..
But sometimes, it can get ip.. toggling wifi on/off cannot success connecting.
Here's the logcat, hope some experts here can give me solutions
As I'm now very dissapointed why some people not getting this problem..
Code:
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
I/wpa_supplicant(29520): wpa_supplicant v2.0-devel-4.1.2 2012-11-26/18:22:02
E/wpa_supplicant(29520): Can't open default ap file
I/wpa_supplicant(29520): rfkill: Cannot open RFKILL control device
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
I/p2p_supplicant(29523): wpa_supplicant v2.0-devel-4.1.200
I/wpa_supplicant(29520): State: DISCONNECTED -> SCANNING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00
I/wpa_supplicant(29520): Scan requested (ret=0) - scan timeout 10 seconds
I/wpa_supplicant(29520): nl80211: Received scan results (2 BSSes)
I/wpa_supplicant(29520): Trying to associate with F4.7C.2A (freq=2412 MHz rssi=-50dBm)
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): ASSOC when wpa_state = 3, do_assoc = 0, reassociate = 0
I/wpa_supplicant(29520): State: SCANNING -> ASSOCIATING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=F4.7C.2A
I/wpa_supplicant(29520): Start Assoc status = [0] !!!!!
W/wpa_supplicant(29520): wlan0: Failed to initiate AP scan
E/wpa_supplicant(29520): wlan0: Not associated - Delay processing of received EAPOL frame !!!!
I/wpa_supplicant(29520): State: ASSOCIATING -> ASSOCIATED
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=F4.7C.2A
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): Associated with F4.7C.2A
I/wpa_supplicant(29520): State: ASSOCIATED -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): WPA: Key negotiation completed with F4.7C.2A [PTK=CCMP GTK=CCMP]
I/wpa_supplicant(29520): State: GROUP_HANDSHAKE -> COMPLETED
I/wpa_supplicant(29520): CTRL-EVENT-CONNECTED - Connection to F4.7C.2A completed (auth) [id=0 id_str=]
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=9 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/dhcpcd (29551): dhcp main start
I/dhcpcd (29551): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (29551): bssid match
E/DhcpStateMachine( 2529): DHCP failed on wlan0: Timed out waiting for DHCP to finish
I/dhcpcd (30384): dhcp main start
I/dhcpcd (30384): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (30384): bssid match
hendry said:
I tried both ROM which using latest 4.1.2 JellyBean, but found bugs when connecting wifi. It's always obtaining ip address..
But sometimes, it can get ip.. toggling wifi on/off cannot success connecting.
Here's the logcat, hope some experts here can give me solutions
As I'm now very dissapointed why some people not getting this problem..
Code:
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
I/wpa_supplicant(29520): wpa_supplicant v2.0-devel-4.1.2 2012-11-26/18:22:02
E/wpa_supplicant(29520): Can't open default ap file
I/wpa_supplicant(29520): rfkill: Cannot open RFKILL control device
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
I/p2p_supplicant(29523): wpa_supplicant v2.0-devel-4.1.200
I/wpa_supplicant(29520): State: DISCONNECTED -> SCANNING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00
I/wpa_supplicant(29520): Scan requested (ret=0) - scan timeout 10 seconds
I/wpa_supplicant(29520): nl80211: Received scan results (2 BSSes)
I/wpa_supplicant(29520): Trying to associate with F4.7C.2A (freq=2412 MHz rssi=-50dBm)
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): ASSOC when wpa_state = 3, do_assoc = 0, reassociate = 0
I/wpa_supplicant(29520): State: SCANNING -> ASSOCIATING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=F4.7C.2A
I/wpa_supplicant(29520): Start Assoc status = [0] !!!!!
W/wpa_supplicant(29520): wlan0: Failed to initiate AP scan
E/wpa_supplicant(29520): wlan0: Not associated - Delay processing of received EAPOL frame !!!!
I/wpa_supplicant(29520): State: ASSOCIATING -> ASSOCIATED
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=F4.7C.2A
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): Associated with F4.7C.2A
I/wpa_supplicant(29520): State: ASSOCIATED -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): WPA: Key negotiation completed with F4.7C.2A [PTK=CCMP GTK=CCMP]
I/wpa_supplicant(29520): State: GROUP_HANDSHAKE -> COMPLETED
I/wpa_supplicant(29520): CTRL-EVENT-CONNECTED - Connection to F4.7C.2A completed (auth) [id=0 id_str=]
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=9 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/dhcpcd (29551): dhcp main start
I/dhcpcd (29551): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (29551): bssid match
E/DhcpStateMachine( 2529): DHCP failed on wlan0: Timed out waiting for DHCP to finish
I/dhcpcd (30384): dhcp main start
I/dhcpcd (30384): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (30384): bssid match
Click to expand...
Click to collapse
Why are you posting this here when you've already posted it in the Omega 8 thread? This is not the place to be posting it. I'm not seeing any wifi problems.
I want some experts here can give me solutions on what's wrong with my device.. so everybody can see
My friend also never got problem using 4.1.2 based ROM. I think maybe the structure android files on my devices has invalid permission access or something else i dont know.. That's why i want to get any explanation on this..
Here i added more logcat debug data
Code:
I/WifiManager( 2820): setWifiEnabled : true
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): setWifiEnabled: true pid=2820, uid=10092
I/WifiHW ( 2529): module is semco
E/WifiHW ( 2529): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2529): Start Check B2 #######
I/WifiHW ( 2529): wifi_trigger_poke : Found 4334B3
I/WifiHW ( 2529): ==========[WIFI] SEMCO MODULE ===========
D/WfdService( 2529): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2820): Wifi onReceive(2)
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
D/WifiP2pService( 2529): P2pDisabledState{ what=131203 }
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
E/WifiHW ( 2529): supplicant_name : p2p_supplicant
D/WifiP2pService( 2529): Supplicant start successful
D/WifiP2pService( 2529): P2pEnablingState
E/WifiHW ( 2529): Unable to open connection to supplicant on "/data/misc/wifi/sockets/p2p0": Connection refused
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2820): Wifi onReceive(3)
D/WfdService( 2529): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/WifiP2pService( 2529): P2pEnablingState{ what=143378 }
D/WifiP2pService( 2529): DefaultState{ what=143378 }
E/WifiP2pService( 2529): Unhandled message { what=143378 }
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): startScan: false pid=31094, uid=10027
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): startScan: false pid=3240, uid=10031
D/WifiNative( 2529): callSECApiBoolean - ID [13]
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/WifiNative( 2529): callSECApiVoid - ID [50]
D/WfdService( 2529): intent recieved android.net.wifi.STATE_CHANGE
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
E/WifiP2pStateTracker( 2529): getNetworkInfo : NetworkInfo: type: WIFI_P2P[], state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.STATE_CHANGE
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiP2pService( 2529): P2pEnablingState{ what=147457 }
D/WifiP2pService( 2529): P2p socket connection successful
D/WifiP2pService( 2529): P2pEnabledState
D/WifiP2pService( 2529): sending p2p connection changed broadcast
I/STATUSBAR-QuickSettingButton( 2820): action: android.net.wifi.p2p.STATE_CHANGED
E/WifiStateMachine( 2529): BroadcastReceiver : WIFI_P2P_STATE_CHANGED_ACTION is : android.net.wifi.p2p.STATE_CHANGED
D/WfdService( 2529): intent recieved android.net.wifi.p2p.STATE_CHANGED
D/WfdService( 2529): intent recieved android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WfdService( 2529): onReceive << WIFI_P2P_CONNECTION_CHANGED_ACTION
D/WfdService( 2529): WIFI_P2P_CONNECTION_CHANGED_ACTION >> isConnected() false
W/WifiP2pStateTracker( 2529): WifiP2pStateReceiver : android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WifiP2pService( 2529): DeviceAddress: 3a:76:f1
D/WifiP2pService( 2529): InactiveState
D/WifiP2pService( 2529): InactiveState{ what=147462 }
D/WifiP2pService( 2529): P2pEnabledState{ what=147462 }
D/WfdService( 2529): intent recieved android.net.wifi.p2p.THIS_DEVICE_CHANGED
D/WfdService( 2529): WIFI_P2P_THIS_DEVICE_CHANGED_ACTION arrived
D/WifiP2pService( 2529): DefaultState{ what=147462 }
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.STATE_CHANGED
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive(), Action : WifiP2pManager.WIFI_P2P_CONNECTION_CHANGED_ACTION, isConnected() == false
D/WifiDirectBR( 5039): stopServiceTest : false
try installing this modem LJ2 http://www.mediafire.com/?9wfmm51c87b2bwn
I think the problem lies in the modem/router software, it only is a problem on specific routers. I haven`t had a issue yet so far.
Flash the official stock 4.1.2 polish release that must came out. Check it out, may solve your problem!
I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?
If this is the bugs on 4.1.2 ROM, we should report it to samsung, so they can fix this bugs on the next build of the ROM..
Also custom rom developer should patch their ROM to avoid this bugs..
I have same problem with 4.1.1 it is perfect, but with 4.1.2 it has same problems as yours.
---------- Post added at 02:33 PM ---------- Previous post was at 02:16 PM ----------
hendry said:
I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?
Click to expand...
Click to collapse
Can you please attach the /etc/wifi folder from 4.1.1 stock??? I want to fix my wifi problem.
Thanks
hendry said:
I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?
Click to expand...
Click to collapse
Yes your right . i am also facing wifi problem disconcerting in 4.1.2 .. in previous version 4.1.1 working fine
Well i dont have this problem as yours....have a stranger one lol
I have 50 mbits internet speed at home with speed of 5.2 MB/S while just on 4.1.2 speed dont cross 2 or 3 mbits out of 50 mbits while download speed is only 200 to 270 KB/S.....
Sent from my GT-N7100 using XDA Premium HD app
I've some problem with wifi on galaxy tab 3 7.0 (JB 4.1.2)
When connect using hotspot laptop or tethering via other device, my wifi always scanning every 7s. make my battery run out.
I was trying use advance setting (static IP) but still same.
How to solved this problem?
Hi everyone,
i'm try to resurrect a kf 1 gen.
WIFI module seams dead and seems that for the same problem u'll get a replacement.
I can't ask for replacement seen that got no warranty any more.
So i post my logcat cause maybe someone can help, causa i can't understand how a dead module can ignore protected network
Thanks in advance.
I/SystemServer( 366): Wi-Fi Service
E/CommandListener( 96): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
I/SystemServer( 366): Connectivity Service
E/WifiStateMachine( 366): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
D/ConnectivityService( 366): ConnectivityService starting up
E/ConnectivityService( 366): Ignoring protectedNetwork 10
E/ConnectivityService( 366): Ignoring protectedNetwork 11
E/ConnectivityService( 366): Ignoring protectedNetwork 12
D/BluetoothTethering( 366): startMonitoring: target: Handler (com.android.server.ConnectivityService$NetworkStateTrackerHandler) {4146c3a8}
D/BluetoothManagerService( 366): Message: 20
D/BluetoothManagerService( 366): Added callback: [email protected]:true
D/BluetoothPan( 366): BluetoothPan() call bindService
D/BluetoothManagerService( 366): Message: 30
D/BluetoothPan( 366): BluetoothPan(), bindService called
W/ApplicationContext( 366): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1437 android.bluetooth.BluetoothPan.<init>:141 android.bluetooth.BluetoothAdapter.getProfileProxy:1164
D/WifiWatchdogStateMachine( 366): Disabling poor network avoidance for wi-fi only device
I/WifiService( 366): WifiService starting up with Wi-Fi enabled
D/WifiService( 366): setWifiEnabled: true pid=366, uid=1000
I/SystemServer( 366): Network Service Discovery Service
D/NsdService( 366): Network service discovery enabled true
I/SystemServer( 366): Throttle Service
I/SystemServer( 366): UpdateLock Service
D/dalvikvm( 366): GC_CONCURRENT freed 329K, 12% free 4531K/5104K, paused 2ms+2ms, total 37ms
D/dalvikvm( 366): WAIT_FOR_CONCURRENT_GC blocked 2ms
W/CommandListener( 96): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 96): Setting iface cfg
E/WifiStateMachine( 366): Unable to change interface settings: java.lang.IllegalStateException: command '4 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 4 Failed to set address (No such device)'
E/WifiHW ( 366): unexpected - found 0 phys in /sys/class/ieee80211
E/WifiHW ( 366): could not add P2P interface: -19
E/WifiHW ( 366): Wi-Fi - could not create p2p interface
E/WifiStateMachine( 366): Failed to start supplicant!
D/ProfileService( 366): Found active: 14a743a1-e6c1-48a0-a191-b9b2bae8c7d9
I/SystemServer( 366): Profile Manager
HERE you find full log:
peciuz said:
Hi everyone,
BLA BLA BLA
Click to expand...
Click to collapse
Well.
I forgot to say that i've rooted and installed jellybeam
Let's say i'd like to connect it to internet...
First way would be buy a new chip Jorjin WG7310 WLAN/BT/FM Combo Module and resoldering
Second way would be via usb tunnelling / reverse tethering throug usb cable but until now i wasn't able to make it work.
Any ideas or advices?
Thanks in advance,
Mirco
up
From nothing my Note 2 (4.1.1 + RedPill) rebooted and now I cannot turn on either WiFi or BT.
I reflashed a couple of ROMs with ODIN, the last one Open Europe 4.1.2 and still no success.
WiFi always disabled, same correct for BlueTooth.
Any ideas?
Logcat show this:
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 2288): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2288): Start Check B2 #######
I/WifiHW ( 2288): Check rev file: No such file or directory
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): return of insmod : ret = -1, File exists
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): supplicant_name : wpa_supplicant
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 1920): Failed to open wlan fw path param (No such file or directory)
E/WifiHW ( 2288): supplicant_name : wpa_supplicant
E/WifiHW ( 1920): Failed to open wlan fw path param (No such file or directory)
E/WifiHW ( 2288): supplicant_name : wpa_supplicant
E/WifiHW ( 1920): Failed to open wlan fw path param (No such file or directory)
E/WifiHW ( 2288): supplicant_name : wpa_supplicant
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): Supplicant not running, cannot connect
E/WifiHW ( 2288): Supplicant not running, cannot connect
D/WifiHW ( 2288): Unable to unload driver module "dhd": No such file or directory
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 2288): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2288): Start Check B2 #######
I/WifiHW ( 2288): Check rev file: No such file or directory
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): return of insmod : ret = -1, No such device
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 2288): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2288): Start Check B2 #######
I/WifiHW ( 2288): Check rev file: No such file or directory
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): return of insmod : ret = -1, No such device
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 2288): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2288): Start Check B2 #######
I/WifiHW ( 2288): Check rev file: No such file or directory
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): return of insmod : ret = -1, No such device
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): ##################### set firmware type 0 #####################
E/WifiHW ( 2288): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 2288): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2288): Start Check B2 #######
I/WifiHW ( 2288): Check rev file: No such file or directory
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
E/WifiHW ( 2288): return of insmod : ret = -1, No such device
I/WifiHW ( 2288): invalid is written to (wlan.poke_helper.ret)
E/WifiHW ( 2288): Failed to read wlan.poke_helper.pid
E/WifiHW ( 2288): failed to read BT poke PID
I am no expert and may be wrong but looks like you fiddled with root explorer and deleted files related to info of hardware which is generally in /dev (not sure of this either)
Cuz you mentioned of trying different roms.
Have you tried a data and cache wipe as well ? Also wipe system rom before flashing.
Additionally try flashing another kernel.
Sent from my GT-N7100 using xda app-developers app
I tried all kinds of wipe.
Shouldn't the ODIN original ROM flash to clean all the filesystems?
Seems to me either radio software ruined or the hardware. The second is a problem to me...
How can I restore radio module? For my old Atrix 4G radio module is a separated flash...
Radio is bootloader I think. If you mean modem it can be flashed separately but is always included in a normal flash.
You tried different kernel ?
Sent from my GT-N7100 using xda app-developers app
I used stock 4.1.1 with RedPill. Everything worked. From nothing my phone rebooted and immediately after I lost WiFi and Bluetooth.
Sent from my Atrix which I bought drunk. Kill nVidia!
I installed my original ROM (Philippines 4.1.1).
Still the same crap.
People from S3 forums had the same issue. They believe it's the mainboard fault.
Now I'm in a deep hole...
Yep.
Service center.
Sent from my GT-N7100 using xda app-developers app