Database Users

Wi-Fi "Unable to start Wi-Fi"

Hi everyone,
I'm having a problem with my G1.
Each time i try to turn the Wi-Fi on, i follow this steps (spoil !!) :
- Settings -> Wireless controls -> and the i click on Wi-Fi,
wich changes the lower text to "Turning on..."
Ok, but this step take something like 1 minute and after all this time, i can read : "Unable to stop Wi-Fi" (or sometimes "Unable to start Wi-Fi"),
I got this problem 5 days ago, and this is really a pain in the arse, because the only way i can download applications is using Wi-Fi (I'm french) and i can't !
I have tried everything :
- Turn Off/On G1
- Remove/Replace battery
- Reset to factory data
- Back to RC29 (thx to you )
- Root my G1 with JF1.41 mod (Thx so much !!)
But the problem is still there,
And i can't get it back to T-Mobile, because i bought it on eBay and i live in France...
So... can anybody help ?
Thx

Hi,
Same problem here. Edit: It does this 4 times on 5. And even if if finally starts, it hangs some time after.
Additionally I've googled (almost) all night long to find some clues but nothing concrete
First, an issue is open here: http://code.google.com/p/android/issues/detail?id=1124
I get this line in logcat:
Code:
D/wlan_loader( 574): ConfigMge start rc = -1
that shows a problem. Normally it should be "rc = 0".
I've digged into the code but it is very complicated (state machine, etc...) so I could not figure where the problem resides.
I also have this in dmesg:
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
I don't know if this means a hardware problem.
I also suspect a bug in the proprietary file "/system/etc/wifi/Fw1251r1c.bin" but I've not found any other version on the net, even in "not so clean ways".
The size of the file on my G1 is 194188 bytes.
I have installed RC33 ADP1 by Jesus Freke but it did not solved the problem.
Can anyone look at the size of this file on his G1 and tell me if it is different? And if it is the case possibly send it to me?
The only solution I've seen on the net is to send back the phone to T-Mobile for a replacement but unfortunately I live in France and I got it from US by unusual ways so it is not a possibility for me .
Any clue / advice will be gladly accepted
Thanks in advance.
Mid'.

I have the same problem...
I was wondering if either of you figured out what to do to get around this. I'm in the US and am having the same problem. I was also working for about a week before this behavior started ("Unable to start Wi-Fi", "Unable to stop Wi-Fi").
I have seen other posts where this is intermittent. It isn't with me. Once it quit working, I haven't been able to get anything but the error messages.
If someone has found a way around this, I would appreciate any help you can provide.
Regards
Steve

You three should post what third party apps you have installed.

I am having this same issue after flashing the new google ION R2

I'm also having this issue after flashing Ion.

Same Issue
I started having this issue before the Ion rom. It wasn't intermittent, just stopped working.

Same problem here
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
CRB43, factory reset, nothing works.
Does anybody have an idea on how to solve this? It seems to be a known problem bij T-Mobile.

I'm running JF1.51 and WiFi is horribly flaky. It will work great for a few seconds then go deaf.
If I toggle it off and on it will work for a little bit again.
EDIT: I'm also getting the "low voltage" error message.

I've looked at this a little bit, and it looks like a ring buffer problem.
As I said before, my WiFi will work great for a while then go deaf.
Disabling/enabling through the Settings GUI will restore operation for a couple of minutes, tops.
Here's what I think might be relevant dmesgs:
Code:
<6>[88157.446136] request_suspend_state: sleep (0->3) at 88153591964926 (2009-06-27 20:57:10.146884034 UTC)
<4>[88157.467956] deinit sharp panel
<4>[88157.996398] select 4913 (app_process), adj 15, size 3053, to kill
<4>[88157.996734] send sigkill to 4913 (app_process), adj 15, size 3053
<4>[88158.236358] save exit: isCheckpointed 1
<6>[88282.505401] request_suspend_state: wakeup (3->0) at 88278651260580 (2009-06-27 20:59:15.206149170 UTC)
<6>[88282.615966] rev_crc_err_count 1, INT 23a001
<6>[88282.616332] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[88282.616851]
<6>[88282.617126] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[88282.620574] mddi: resetting rev ptr
<6>[88282.621154] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[88282.666717] init sharp panel
<4>[88287.779876] select 4943 (app_process), adj 15, size 2991, to kill
<4>[88287.780731] send sigkill to 4943 (app_process), adj 15, size 2991
<4>[88295.748840] select 4951 (app_process), adj 15, size 2992, to kill
<4>[88295.749694] send sigkill to 4951 (app_process), adj 15, size 2992
<6>[88298.065185] TIWLAN: Driver unloading
<4>[88298.066314] sdio_reset_comm():
<7>[88298.154388] TIWLAN: Releasing SDIO resources
<7>[88298.158172] TIWLAN: SDIO resources released
<4>[88298.160217] wifi_remove
<4>[88298.160552] trout_wifi_set_carddetect: 0
<7>[88298.160827] mmc0: card_present 0
<6>[88298.161346] mmc0: Slot status change detected (1 -> 0)
<4>[88298.161712] trout_wifi_reset: 1
<6>[88298.172302] mmc0: card 0002 removed
<4>[88298.233215] trout_wifi_power: 0
<6>[88298.996520] TIWLAN: Driver unloaded

Here's a little more that I'm getting when the WiFi stops. Is this driver OSS or a proprietary blob?
Code:
<3>[ 1097.459899] init: untracked pid 364 exited
<4>[ 1101.746643] wds: 0020 @ 01
<6>[ 1101.747192] qmi: wds: got handle 0x17aaafb0
<4>[ 1101.747711] wds: 0022 @ ff
<6>[ 1101.748168] qmi: wds: CONNECTED
<4>[ 1101.750244] wds: 002d @ 01
<4>[ 1101.750701] qmi: got network profile
<6>[ 1101.752502] rmnet_open()
<6>[ 1685.105285] request_suspend_state: wakeup (3->0) at 1679298966064 (2009-06-27 21:55:33.740494873 UTC)
<6>[ 1685.217498] rev_crc_err_count 1, INT 23a001
<6>[ 1685.218078] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[ 1685.218383]
<6>[ 1685.218658] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[ 1685.222137] mddi: resetting rev ptr
<6>[ 1685.222595] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[ 1685.288696] init sharp panel
<4>[ 1692.515502] wds: 0021 @ 01
<6>[ 1692.515838] qmi: wds: network stopped
<6>[ 1692.546508] rmnet_stop()
<4>[ 1693.342254] wds: 0022 @ ff
<6>[ 1693.342864] qmi: wds: DISCONNECTED
<6>[ 1704.187591] TIWLAN: Driver unloading
<4>[ 1704.188781] sdio_reset_comm():
<7>[ 1704.266632] TIWLAN: Releasing SDIO resources
<7>[ 1704.267944] TIWLAN: SDIO resources released
<4>[ 1704.270568] wifi_remove
<4>[ 1704.271057] trout_wifi_set_carddetect: 0
<7>[ 1704.272521] mmc0: card_present 0
<6>[ 1704.272979] mmc0: Slot status change detected (1 -> 0)
<6>[ 1704.276489] mmc0: card 0002 removed
<4>[ 1704.280487] trout_wifi_reset: 1
<4>[ 1704.332305] trout_wifi_power: 0
<6>[ 1704.543151] TIWLAN: Driver unloaded
<4>[ 1705.308166] wds: 0020 @ 01
<6>[ 1705.308715] qmi: wds: got handle 0x17aaafb0
<4>[ 1705.309234] wds: 0022 @ ff
<6>[ 1705.309661] qmi: wds: CONNECTED
<4>[ 1705.311370] wds: 002d @ 01
<4>[ 1705.311798] qmi: got network profile
<6>[ 1705.313690] rmnet_open()
<6>[ 1709.503326] TIWLAN: Driver loading
<4>[ 1709.504211] wifi_probe
<4>[ 1709.504486] trout_wifi_power: 1
<4>[ 1709.714965] trout_wifi_reset: 0
<4>[ 1709.766632] trout_wifi_set_carddetect: 1
<7>[ 1709.767303] mmc0: card_present 1
<6>[ 1709.767608] mmc0: Slot status change detected (0 -> 1)
<3>[ 1712.275085] mmc0: Command timeout
<4>[ 1712.282226] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1712.283081] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 1712.290405] mmc0: new SDIO card at address 0001
<6>[ 1712.296447] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 1712.302520] TIWLAN: Driver initialized (rc 0)
<4>[ 1712.303436] TIWLAN: 1251 PG 1.2
<6>[ 1712.303863] TIWLAN: Driver loaded
<4>[ 1721.950164] wds: 0021 @ 01
<6>[ 1721.950500] qmi: wds: network stopped
<6>[ 1721.976440] rmnet_stop()
<4>[ 1726.546569] select 151 (app_process), adj 15, size 3009, to kill
<4>[ 1726.547149] select 158 (app_process), adj 15, size 3081, to kill
<4>[ 1726.547454] select 311 (app_process), adj 15, size 3246, to kill
<4>[ 1726.547973] send sigkill to 311 (app_process), adj 15, size 3246
<4>[ 1730.936798] wds: 0022 @ ff
<6>[ 1730.937652] qmi: wds: DISCONNECTED

I had the problem, i redid everything. just flashing the phone didn't help. downloaded the jf1.51 and did it again. logs would say wifi drivers not found. and guess what i checked and there were not there... I don't know 'who' or 'what' deleted them...
The only thing II suspect is the Backup program available on market for root users...or the "Privacy for rooted phones" prog

Same problem
Experiencing the same problem with my UK T-Mobile G1 (JF v1.51). Tried wiping, reseting, turning device off and on and removing battery, nothing has worked.
Is there any solution yet? I don't have any new apps installed and it is a fresh update, the problem was there prior to updating to jf v1.51
Any help will be appreciated

Did anyone manage to fix this? could it be related to the SDCard you are using?
Does everyone with non-working wifi on a G1 have this?

3 days ago, after I apply a chinese character sorting patch, i met this problem. So I wiped my phone, repartitioned my sdcard, reflashed the CM404 rom. And finnally got my wifi back.
But today I had this problem back again. I'm thinking is it because the sdcard I'm using is taking up to much battery power, so that the wifi module could not acquire enough power? This recalls me that I changed my sdcard exactly 3 days ago, right before I met this problem for the first time.

I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.

bidhata said:
I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.
Click to expand...
Click to collapse
Thanks Bidhata ,
but it tried that application and initially at first run it worked . but then once i got dc , the problem came back. since then i am not able to have the wifi truned on .
so the issue remains ..

Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf

osoft said:
Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf
Click to expand...
Click to collapse
This gave me the idea of how to fix, and its relativley simple... please correct me if I have made a grave error, but it seems to work so meh:
enter your terminal emulator and type the following:
su
(allow the request when asked)
chmod 777 /data/misc/wifi/wpa_supplicant.conf
exit the terminal
try powering up your wifi, it seems to be pretty stable as of now. This began occuring after I left my home's wireless range without turning wifi off and having the Wireless Helper app installed from the market...needless to say I have uninstalled said app and done this mod.

Whats funny about my situation is that if i use the DREAIMG.nbh file to flash back to rc29 my wifi works fine if i then upgrade to jf 1.5 still works fine upgrade to the latest cyanogen stable still works fine. Then a couple of days later poof "Unable to start wifi" intermittently and then a few days later permanently. Even if i downgrade to jf again still no wifi until i re-flash rc29 again. Weird thing is before i downgrade to jf 1.5 i run a fastboot erase on all the pertinent partitions. The only one that doesn't get flashed or erased in the downgrade to 1.5 is the radio rom. This leads me to believe that either my hardware is on it's way out or something that gets set in the radio rom from cyanogen 4.0.4 gets carried over no matter what rom you flash until the radio is erased and re-flashed. Mind you the second one is a totally just a guess with no proof to back it up. I also tried to chmod 777 /data/misc/wifi/wpa_supplicant.conf like said in the last post but to no avail.

Flashed a kernel? Now your xoom is on fire...

I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.

upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?

MitchRapp said:
upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?
Click to expand...
Click to collapse
No i mean the files on your computer, not the xoom. People are extracting the files into the SDK directory. Then leaving them there to mix with the new files. The xoom will overwrite what it needs to.

bwcorvus said:
I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.
Click to expand...
Click to collapse
This is why I always copy my files into a temp directory as shown in this post

Or just use a different folder for each version, and cd to the directory before you flash.
Also, you can do adb push system /system, and it'll put them in the right folders if you have it mirrored in your PC's folders.

Mine doesn't power up after following the procedure, it stays in the Motorola Dual Core logo..
I guess no XOOM for me until tomorrow
dmesg output:
Code:
<4>[ 18.182391] Primary GPT is invalid, using alternate GPT.
<6>[ 18.182577] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpanic) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[ 18.567134] android_usb gadget: high speed config #1: android
<6>[ 18.572291] EXT4-fs (mmcblk1p8): INFO: recovery required on readonly filesystem
<6>[ 18.572602] EXT4-fs (mmcblk1p8): write access will be enabled during recovery
<6>[ 18.603790] EXT4-fs (mmcblk1p8): recovery complete
<6>[ 18.606421] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.682391] EXT4-fs (mmcblk1p10): recovery complete
<6>[ 18.683460] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.701587] EXT4-fs (mmcblk1p9): recovery complete
<6>[ 18.702643] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null)
<4>[ 18.740397] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
<3>[ 18.745288] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
<6>[ 18.844887] enabling adb
<6>[ 18.861463] adb_open
<6>[ 18.924122] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[ 18.928677] gps_brcm4750_ioctl: Setting gps gpio reset pin: 0
<6>[ 18.928769] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
<6>[ 18.928937] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 18.929026] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
<6>[ 18.930479] gps_brcm4750_ioctl: Setting gps gpio reset pin: 1
<6>[ 18.930572] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
<6>[ 19.003124] adb_release
<6>[ 19.003397] adb_open
<6>[ 19.028708] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 1
<6>[ 19.029017] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
<6>[ 19.261164] android_usb gadget: high speed config #1: android
<6>[ 19.577060] tear_down_dma
<6>[ 19.577183] setup_dma
<6>[ 37.780346] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 37.780512] stingray_gps_standby_gpio: setting GPS standby GPIO to 0

TWRP random reboots

I am not sure how to file a bug report or what all that entails, so I'll just post here.
TWRP randomly reboots. One minute, five minutes, whenever. Even if I just leave the screen on and touch nothing, it still happens. Rebooting has even happened while flashing, which is no good. Other's have confirmed this behavior in the i777 thread:
http://forum.xda-developers.com/showthread.php?t=2544790 I've tried wiping and reflashing the rom a few times (and just boot.img as well), but the behavior always exists.
i777 build. currently on 12/27 nightly. I am now using RenderBroken's kernel for Omni & the rebooting does not happen.
Thanks. :good:

bleggy said:
I am not sure how to file a bug report or what all that entails, so I'll just post here.
TWRP randomly reboots. One minute, five minutes, whenever. Even if I just leave the screen on and touch nothing, it still happens. Rebooting has even happened while flashing, which is no good. Other's have confirmed this behavior in the i777 thread:
http://forum.xda-developers.com/showthread.php?t=2544790 I've tried wiping and reflashing the rom a few times (and just boot.img as well), but the behavior always exists.
i777 build. currently on 12/27 nightly. I am now using RenderBroken's kernel for Omni & the rebooting does not happen.
Thanks. :good:
Click to expand...
Click to collapse
pull /proc/last_kmsg after a reboot please

ok. currently on renders omni kernel. after I flash the next nightly, I'll have twrp reboot itself & upload that log.
cat /proc/last_kmsg > last_kmsg.txt with a terminal emulator, correct?
Sent from my SGH-I777 using XDA Premium 4 mobile app

Here is one I prepared earlier, probably around Dec 20th: http://paste.ubuntu.com/6654443/
Code:
$ egrep ' 12[01]\.|kadapt' last_kmsg
<6>[ 120.185215] c0 sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<6>[ 120.185765] c0 smb328-charger 19-0034: smb328_get_charging_health : charging status A(0x02)
<6>[ 120.186305] c0 smb328-charger 19-0034: smb328_get_charging_health : charging status B(0x00)
<6>[ 120.186843] c0 smb328-charger 19-0034: smb328_get_charging_health : charging status C(0x05)
<6>[ 120.186889] c0 smb328-charger 19-0034: smb328_get_property: smb328_get_property (2,1)
<6>[ 121.005248] c0 sec-thermistor sec-thermistor: notify_change_of_temperature: uevent: TEMPERATURE=510
<6>[ 121.805308] c0 cpu1 turnning off!
<4>[ 121.811130] c1 IRQ112 no longer affine to CPU1
<5>[ 121.811478] c0 CPU1: shutdown
<6>[ 121.812313] c0 cpu1 off!
<3>[ 240.170095] c0 INFO: task kadaptiveup:1058 blocked for more than 120 seconds.
<6>[ 240.194448] c0 kadaptiveup D c0c436fc 0 1058 2 0x00000000
$
Regression seemed to happen for me between Dec 15 & 18, which coincided with gerrit saying there were some scheduler patches for smdk4412 around that time, along with the defconfig & dock patches. I haven't figured out enough about kernel building and what I need to insert where and how, to do any testing myself as yet.
I found this initially when I tried to enable compression for TWRP backups. With compression enabled I can usually trigger a panic.

Entropy512 said:
pull /proc/last_kmsg after a reboot please
Click to expand...
Click to collapse
updated to the 12/29 nightly.
omni version: 4.4.2-20131229-i777-nightly
kernel version: 3.0.64-CM-g1f99098
build number: omni_i777-userdebug 4.4.2 KOT49H 96 test-keys
went back into recovery & let sit without touching anything.
rebooted itself after 3 minutues.
attached is the last_kmsg. if there is anything else I can do, let me know.

Omni 1229 => panic @ 240 seconds as usual, cpu1 shutdown at 120 sec, cpu1 won't start by 240 sec, kadaptiveup kernel task hung still, seems just to be time based, don't need to do anything. I have last_kmsg if required.
Omni Asylum kernel 1227 from @chasmodo, cpu1 stop/start OK, no problem, @chasmodo said he rolled back to Dec 16.
@chasmodo build comment here: http://forum.xda-developers.com/showpost.php?p=48864227&postcount=11241
Kernel here: http://forum.xda-developers.com/showpost.php?p=35551986&postcount=2
Omni Asylum ROM 1229 from @chasmodo, OK too.

****. It's those extra governors.
I've seen this before.
Time to rip those ****ers out.

[Q] Wifi won't turn on after flashing

Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!

sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947

MAX 404 said:
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
Click to expand...
Click to collapse
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.

sven93 said:
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
Click to expand...
Click to collapse
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?

MAX 404 said:
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
Click to expand...
Click to collapse
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?

sven93 said:
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
Click to expand...
Click to collapse
Not sure about the log file ...
Here i found a thread , it talks about a solution but they use a SPT box, for what i see the problem is efs related, do you have an EFS backup?
http://forum.gsmhosting.com/vbb/f45...nlock-default-efs-imei-solution-here-1788263/

Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?

sven93 said:
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
Click to expand...
Click to collapse
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.

Joku1981 said:
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Click to expand...
Click to collapse
CSC Seems to match.
Tried flashing it 3 times in a row with the same (stock) ROM, still nothing.

sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.

ajax505 said:
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
Click to expand...
Click to collapse
Sad to hear you have the same.
Pretty strange, i haven't used the S4 since Wednesday, but the phone was still turned on, ten minutes ago i wanted to check something, turns out wifi is working again, until i decided to reboot, now its doing the same as before...
It does indeed smells software/firmware related.

Just made a dumpfile of the logs (bugreport > /mnt/sdcard/dump.txt) , and saw some interesting stuff in the kernel log:
<4>[ 9.717163] failed to power up wifi chip, retry again (5 left) **
<4>[ 9.717163]
<4>[ 9.733306] ## wifi_remove
<4>[ 9.733612] wifi_set_power = 1
<4>[ 9.733612] WiFi: trying to acquire BT lock
<4>[ 9.733612] ####btlock acquired cookie: WiFi
<4>[ 9.733642] wifi_set_power: btlock acquired
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] brcm_wlan_power Enter: power on
<3>[ 9.733642] brcm_wlan_power: WL_REG_ON failed to pull up
<4>[ 9.733734] wifi_probe: set_power failed. err=-5
<4>[ 9.733734] wifi_set_power = 0
<4>[ 9.733734] ####btlock released, cookie: WiFi
<6>[ 9.733734] ------------------------------------------------
<6>[ 9.733795] ------------------------------------------------
<6>[ 9.733825] brcm_wlan_power Enter: power off
<3>[ 9.733825] brcm_wlan_power: WL_REG_ON failed to pull down
Click to expand...
Click to collapse
Then after a bit:
<4>[ 11.727294]
<4>[ 11.727294] failed to power up wifi chip, retry again (4 left) **
<4>[ 11.727294]
<4>[ 11.743499] ## wifi_remove
<4>[ 11.743835] wifi_set_power = 1
<4>[ 11.743835] WiFi: trying to acquire BT lock
<4>[ 11.743835] ####btlock acquired cookie: WiFi
<4>[ 11.743835] wifi_set_power: btlock acquired
<6>[ 11.743835] ------------------------------------------------
<6>[ 11.743865] ------------------------------------------------
<6>[ 11.743865] brcm_wlan_power Enter: power on
<6>[ 11.743865] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<6>[ 11.754608] [email protected]: Start PackageManagerService
<6>[ 11.775604] [SSP] Updated 73599 bytes / 139282 bytes
<4>[ 11.977172] wifi_set_carddetect = 1
<4>[ 11.977172] brcm_wifi_status:267 status 1
Click to expand...
Click to collapse
For people who want to view the log: https://dl.dropboxusercontent.com/u/15503253/dumpfile.txt

I also get those kind of messages in my system logs:
<4>[ 1837.921936] failed to power up wifi chip, retry again (1 left) **
<4>[ 1837.921966]
<4>[ 1837.941497] ## wifi_remove
<4>[ 1837.941497] wifi_set_power = 0
<4>[ 1837.941528] ####btlock released, cookie: WiFi
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941589] brcm_wlan_power Enter: power off
<6>[ 1837.941619] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1838.182006] wifi_set_carddetect = 0
<4>[ 1838.182037] brcm_wifi_status:267 status 0
<6>[ 1838.182067] mmc1: Slot status change detected (1 -> 0)
<4>[ 1838.187591]
<4>[ 1838.187622] failed to power up wifi chip, max retry reached, exits **
Click to expand...
Click to collapse
I also get a lot of "mmc1: Data CRC error":
<3>[ 1826.574645] mmc1: Data CRC error
<3>[ 1826.577178] msmsdcc_data_err: opcode 0x00000035
<3>[ 1826.581542] msmsdcc_data_err: blksz 4, blocks 1
<6>[ 1826.586883] sps:BAM 0x12182000 enabled: ver:0x5, number of pipes:6dhd_detach(): thread:dhd_sysioc:392 terminated OK
<4>[ 1826.651245] dhd_detach(): thread:dhd_watchdog_thread:38f terminated OK
<4>[ 1826.651336] dhd_dpc_thread: Unexpected up_cnt 0
<4>[ 1826.651428] dhd_detach(): thread:dhd_dpc:390 terminated OK
<4>[ 1826.651733] dhd_detach(): thread:dhd_rxf:391 terminated OK
<6>[ 1826.670593] CFG80211-INFO2) wl_event_handler : was terminated
<4>[ 1826.670898] wl_destroy_event_handler(): thread:wl_event_handler:38e terminated OK
<4>[ 1826.682250] dhdsdio_disconnect : the lock is released.
<4>[ 1826.683807] ## wifi_remove
<4>[ 1826.683837] wifi_set_power = 0
<4>[ 1826.683868] ####ignore lock release, cookie mismatch: WiFi owner ˙˙˙˙
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683929] brcm_wlan_power Enter: power off
<6>[ 1826.683959] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1826.920593] wifi_set_carddetect = 0
<4>[ 1826.920623] brcm_wifi_status:267 status 0
<6>[ 1826.920654] mmc1: Slot status change detected (1 -> 0)
<6>[ 1826.928405] mmc1: card 0001 removed
<6>[ 1828.083618] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 1828.142578] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<4>[ 1828.178527] wifi_set_power = 1
<4>[ 1828.178558] WiFi: trying to acquire BT lock
<4>[ 1828.178558] ####btlock acquired cookie: WiFi
<4>[ 1828.178558] wifi_set_power: btlock acquired
<6>[ 1828.178558] ------------------------------------------------
<6>[ 1828.178588] ------------------------------------------------
<6>[ 1828.178588] brcm_wlan_power Enter: power on
<6>[ 1828.178588] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<4>[ 1828.411895] wifi_set_carddetect = 1
<4>[ 1828.411926] brcm_wifi_status:267 status 1
<6>[ 1828.411956] mmc1: Slot status change detected (0 -> 1)
<3>[ 1828.473205] mmc1: msmsdcc_switch_io_voltage: MCIDATIN_3_0 is still not all zeros
<3>[ 1828.480651] mmc1: CMD7: Command CRC error
<3>[ 1828.484039] mmc1: SDCC PWR is ON
<3>[ 1828.487426] mmc1: SDCC clks are ON, MCLK rate=400000
<3>[ 1828.492217] mmc1: SDCC irq is enabled
<3>[ 1828.495849] ===== SDCC-CORE: Register Dumps @phys_base=0x12180000, @virt_base=0xe337a000 =====
<3>[ 1828.504608] Reg=0x00: 0x00000001, 0x01209300, 0x00000000, 0x00000447
<3>[ 1828.510955] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.517120] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.523620] Reg=0x30: 0x00000000, 0x004c0000, 0x00000000, 0x408001ff
<3>[ 1828.529785] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.536285] Reg=0x50: 0x06000018, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.542633] Reg=0x60: 0x67356400, 0x00000000, 0x00000018, 0x00000000
<3>[ 1828.548797] ===== SDCC-DML: Register Dumps @phys_base=0x12180800, @virt_base=0xe3534800 =====
<3>[ 1828.557495] Reg=0x00: 0x00000000, 0x00010001, 0x00000000, 0x00000000
<3>[ 1828.563629] Reg=0x10: 0x00000000, 0x00001000, 0x00001000, 0x00020001
<3>[ 1828.570159] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.576477] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.582641] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.589172] ===== SDCC-BAM: Register Dumps @phys_base=0x12182000, @virt_base=0xe33d8000 =====
<3>[ 1828.597503] Reg=0x00: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.604003] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.610351] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.616516] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.623016] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.629180] mmc1: MCI_TEST_INPUT = 0x0000003e
<3>[ 1828.633697] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 1828.644012] mmc1: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 1828.650817] mmc1: RPM: runtime_status=0, usage_count=2, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<4>[ 1828.663024] mmc1: Skipped tuning.
<3>[ 1828.686431] mmc1: error -110 whilst initialising SDIO card
<4>[ 1830.421936]
<4>[ 1830.421966] failed to power up wifi chip, retry again (4 left) **
Click to expand...
Click to collapse
As long as I know mmc0 is internal memory and mmc2 is external sd card. Can anyone explain what mmc1 device is?

Bump...

[Q&A] [Kernel][4.3/4.4][GPL] Kang-aroo1.2(1/27/2014)(OC,otg+charge,DAC, usb wifi,EZc

[Q&A] [Kernel][4.3/4.4][GPL] Kang-aroo1.2(1/27/2014)(OC,otg+charge,DAC, usb wifi,EZc
Q&A for [Kernel][4.3/4.4][GPL] Kang-aroo1.2(1/27/2014)(OC,otg+charge,DAC, usb wifi,EZcap)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel][4.3/4.4][GPL] Kang-aroo1.2(1/27/2014)(OC,otg+charge,DAC, usb wifi,EZcap). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

[Q][Kernel][4.3/4.4][GPL] Kang-aroo1.2(1/27/2014)(OC,otg+charge,DAC, usb wifi,EZcap)
redeyedjedi said:
this project is not dead. It reached a high level of stability for android 4.4.4. There has some been frustration because of those who don't get what android is about ...but I have always done this as a hobby in my spare time because I want to learn more regardless. I was working on a new app for easycap devices, but without hardware accelerated encoding our 1.3 ghz ARM cannot handle simultaneous raw capture, encoding and compression, software decoding and simultaneous live streaming. I actually custom built an ffmpeg for our tablet and in my tests i got about 2 fps MAX. on my note 2 it was about 13fps, so it has come down to lack of hardware resources. There is a way to do it with hardware acceleration but it would require someone with hardcore libstagefright skills.
This kernel will be updated for android 5.0
otg while charging will still work, but all timur usb audio stuff will get removed in place of stock google lollipop which means working audio, and mics as well!!!! I need time, but it will get done. Im not sure about firm sleep, it may not even be needed anymore. lollipop introduces "batch wakeups" which means that instead of every app causing a wakelock whenever it wants, instead the system will queue wake requests into batches, and once there are enough requests, it wakes the device, runs them all as a batch, then goes back to sleep. this means there are minimal wakeups while device is in deep sleep, and standby times for lollipop have been as high as 300% over jellybean on some devices. Also, I am about to post some new drivers and detailed info for watching live tv on the nexus 7. It works great and can even pause/record. It is a complicated setup but worth the effort.
this uses new drivers which are practically bleeding edge from linuxtv.org there are also new drivers for all easycap devices.
Click to expand...
Click to collapse
Newbie here!
First thanks for your hard work and enthusiasm. I am new to the android dev scene (mostly used stock devices) but I've been using gnu/linux for quite long. Fortunately stopped compiling my own kernels back in the Slackware/Suse days when modules were slow but i have some idea about the process.
I'm currently trying to get stable running grouper with stk1160 mainly for gps and reversing camera. I've successfully made it work with your kernel (or timur + modules or stock + modules) but the picture seems a bit strange (interlaced) and carcam_1.4bbb is unstable as hell. Can you please post some tutorial for you easycap drivers workflow? I would like to compile my own kernel without the rest of the hacks. Imho for car usage we don't need all the overclocking or the different governors (easycap + otg/(possibly even slow)charging is enough for me).
Maybe the best approach (as you mentioned) would be to get lollipop as it has most of the things already there so we only need the easycap drivers.
The other topic - carcam_1.4bbb - this is practically unusable. We should be able to use some decent player (vlc has v4l2 support under linux but couldn't find anything for android apart from some patches which are disabling it under some conditions). The other option which i believe you are trying too is to get ffmpeg to stream the v4l2 so another player can be used however latency will build up even if streaming raw input.
From what i read franco kernel is quite popular, maybe it is better base kernel than 'bricked-grouper-3.x' ?

Autodroid with Kangaroo Kernel, external wifi
I keep reading without any answers.
Kangaroo Kernel supports the chipset in my USB wifi adapter. I can't figure out how to enable that over my internal wifi.

OTG charge and usb stick
Thank you very much, timurs kernel not work for me. i have nexus 7 2012, and all works well, as i wait! thank yoi very much!!
is it any plans to update 4.4.2 to 4.4.4?

Will be a version for a lollipop 5.1?

Current limited to 250mA in host mode
So, I've installed this kernel (V2), the power manager app, rooted (I discovered the power manager app didn't work without root) and have constructed a Y cable (currently powered by my bench power supply) and no matter what settings I choose, my power supply indicates that it's drawing about 250mA only.
The OTG Y cable was constructed from an existing OTG cable, basically as described here: http://forum.xda-developers.com/showthread.php?t=1828032
I've selected Fixed Installation mode and Fast Charging in Host Mode in the power manager app.
Any advice? The project I'm working on is a fixed installation and cannot operate on a 250mA cable since that will obviously not power the device for very long.
Any advice would be appreciated!
EDIT:
This is the kernel messages that I get when plugging in the Y cable. It APPEARS to be setting the charging limit to 1800mA.
<6>[ 9486.852896] -tegra_otg_irq(): ID=2 VBUS=0
<6>[ 9486.853203] -tegra_otg_irq(): ID=2 VBUS=0 DONE
<6>[ 9486.853408] tegra-otg tegra-otg: USB_ID_INT_STATUS
<6>[ 9486.853560] tegra-otg tegra-otg: set id_is_set, to = OTG_STATE_A_HOST (OTG PLUGGED)
<6>[ 9486.853832] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[ 9486.853979] tegra-otg tegra-otg: call smb347_otg_status()
<4>[ 9486.854252] smb347_otg_status from=10 to=9 hostmode=0 externalPowerState=0 usbhost_charge_slave_devices=0 fixed_install_mode=1
<6>[ 9486.854521] cable_type_detect()
<6>[ 9486.854665] INOK=H no power
<4>[ 9486.854809] ========================================================
<4>[ 9486.855071] battery_callback usb_cable_state = 0
<4>[ 9486.855215] ========================================================
<6>[ 9486.856608] elan-ktf3k 1-0010: Update power source to 0
<4>[ 9486.857807] smb347_otg_status allow battery to be charged
<4>[ 9486.859248] smb347_configure_charger accept external power
<4>[ 9486.860160] smb347_otg_status disableOTG, dont chargeSlaves, don't stopChargeSlaves
<4>[ 9486.860441] smb347_configure_otg otg=0 chargeSlaves=0 stopSlaves=0 lastOtg=0
<4>[ 9486.862044] smb347_otg_status make external power detectable2
<4>[ 9486.863707] smb347_otg_status DONE hostmode=0 externalPowerState=0 chargeSlaveDevicesState=0
<6>[ 9486.863989] tegra-otg tegra-otg: call tegra_start_host()
<6>[ 9486.865193] phy->instance = 0, phy->xcvr_setup_value = 57
<3>[ 9486.866175] couldn't get regulator avdd_usb: -19
<4>[ 9486.866363] tegra_gpio_enable : Invalid gpio ID - 260
<7>[ 9486.866780] gpio_request: gpio-260 (PMU_ACOK) status -16
<3>[ 9486.866929] Failed to request the GPIO260: -16
<6>[ 9486.867802] tegra_usb_phy_open instance 0 TI AC_PRESENT_GPIO = 260
<6>[ 9486.871897] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 9486.872255] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
<6>[ 9486.895555] tegra-ehci tegra-ehci.0: irq 52, io mem 0x7d000000
<6>[ 9486.915452] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 9486.915742] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 9486.916052] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 9486.916321] usb usb2: Product: Tegra EHCI Host Controller
<6>[ 9486.916467] usb usb2: Manufacturer: Linux 3.1.10-kangaroo ehci_hcd
<6>[ 9486.916730] usb usb2: SerialNumber: tegra-ehci.0
<6>[ 9486.918751] hub 2-0:1.0: USB hub found
<6>[ 9486.918935] hub 2-0:1.0: 1 port detected
<6>[ 9486.919847] Wake39 for irq=52
<6>[ 9486.919999] Enabling wake39
<6>[ 9486.920163] tegra-otg tegra-otg: done id_is_set=1 ##############
<6>[ 9487.750868] -tegra_otg_irq(): ID=0 VBUS=512
<6>[ 9487.751049] -tegra_otg_irq(): ID=0 VBUS=512 DONE
<6>[ 9487.751391] tegra-otg tegra-otg: !USB_ID_INT_STATUS but USB_VBUS_INT_STATUS id_is_set)1
<6>[ 9487.751544] tegra-otg tegra-otg: USB_VBUS_INT_STATUS
<6>[ 9487.751809] tegra-otg tegra-otg: USB_VBUS_STATUS && id_is_set: to=OTG_STATE_A_HOST
<6>[ 9487.751961] tegra-otg tegra-otg: HOST --> HOST
<6>[ 9487.752224] tegra-otg tegra-otg: call smb347_otg_status()
<4>[ 9487.752377] smb347_otg_status from=9 to=9 hostmode=0 externalPowerState=0 usbhost_charge_slave_devices=0 fixed_install_mode=1
<6>[ 9487.752649] cable_type_detect()
<6>[ 9487.752914] INOK=L
<5>[ 9487.753292] smb347_charger: [cable_type_detect] Reg39 : 0x10
<5>[ 9487.753673] smb347_charger: [cable_type_detect] Reg3F : 0x80
<5>[ 9487.753941] smb347_charger: [cable_type_detect] USB_IN
<5>[ 9487.754319] smb347_charger: [cable_type_detect] Reg3E : 0x0e
<6>[ 9487.754591] Cable: host mode charging ac
<4>[ 9487.754736] ========================================================
<4>[ 9487.755000] battery_callback usb_cable_state = 3
<4>[ 9487.755145] ========================================================
<4>[ 9487.755981] battery_callback cable_wake_lock 5 sec...
<4>[ 9487.755990]
<6>[ 9487.756295] elan-ktf3k 1-0010: Update power source to 1
<4>[ 9487.757439] smb347_otg_status allow battery to be charged
<4>[ 9487.759320] smb347_otg_status enableOTG, dont chargeSlaves, don't stopChargeSlaves
<4>[ 9487.759602] smb347_configure_otg otg=1 chargeSlaves=0 stopSlaves=0 lastOtg=0
<4>[ 9487.760120] smb347_configure_otg enable host mode
<4>[ 9487.762289] smb347_otg_status make external power detectable2
<4>[ 9487.766524] smb347_otg_status DONE hostmode=1 externalPowerState=1 chargeSlaveDevicesState=0
<6>[ 9487.766807] tegra-otg tegra-otg: call tegra_start_host()
<6>[ 9487.766955] tegra-otg tegra-otg: done id_is_set=1 ##############
<6>[ 9487.768260] healthd: battery l=24 v=3721 t=30.0 h=2 st=2 chg=a
<6>[ 9488.171069] call alarm, type 2, func alarm_triggered+0x0/0xa0, 68998832000000 (s 68998832000000) firm_sleep=1 suspended=0
<4>[ 9488.335465] inok_isr_work_function hostmode=1 externalPowerState=1 usbhost_charge_slave_devices=0
<6>[ 9488.335635] cable_type_detect()
<6>[ 9488.335901] INOK=L
<5>[ 9488.336345] smb347_charger: [cable_type_detect] Reg39 : 0x10
<5>[ 9488.336725] smb347_charger: [cable_type_detect] Reg3F : 0x81
<5>[ 9488.336995] smb347_charger: [cable_type_detect] USB_IN
<5>[ 9488.337369] smb347_charger: [cable_type_detect] Reg3E : 0x0e
<6>[ 9488.337636] Cable: host mode charging ac
<4>[ 9488.337778] ========================================================
<4>[ 9488.338039] battery_callback usb_cable_state = 3
<4>[ 9488.338181] ========================================================
<6>[ 9488.338972] elan-ktf3k 1-0010: Update power source to 1
<4>[ 9488.339331] inok_isr_work_function external power available hostmode=1
<6>[ 9488.344445] healthd: battery l=24 v=3720 t=30.0 h=2 st=2 chg=a
<6>[ 9488.590963] call alarm, type 2, func alarm_triggered+0x0/0xa0, 310670000000 (s 310670000000) firm_sleep=1 suspended=0

Please 5.1.1 lollipop version

I can't find a reliable download link for this kernel, no matter how hard I look.
Nexus 7 (2012), Stock KitKat 4.4.4 (but I'm thinking of installing SlimKat 9.0)