NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[[ACL]]

Originally Posted by Lmiller1708

WIFI works. Just need to make sure you have the androidupdate too. The modules need to be the same as the kernal.

maybe i effed up the autobuild. Someone mentioned the date was off in the update. The latest stuff should always match since its automated. I can re-run it if there are issues.

[Lmiller1708]

Originally Posted by m4f1050

I did install androidupdate.tgz from 3.17.11 when I reinstalled it. I even reflashed the 3.17.11 nbh just in case...instead of 3 files in andboot I had 4:

androidinstall.tgz
androidupdate.tgz
recoveryinstall.tgz
install-seq.sh

Did you do a restore of your data?

If so that is your problem.

Nate was working on a script to handle this but I'm not sure it was working just yet...

[[ACL]]

Originally Posted by m4f1050

I can confirm wifi can't scan.... here is my logcat..

when modules dont match. dmesg is more valuable than logcat. So hook me up

[m4f1050]

Originally Posted by Lmiller1708

Did you do a restore of your data?

If so that is your problem.

Nate was working on a script to handle this but I'm not sure it was working just yet...

I restored data but the data I restored was after the 3.17.11 install... But yeah, I will reinstall and test wifi after fresh install (without backup & restore in the mix...)

[m4f1050]

Originally Posted by [ACL]

when modules dont match. dmesg is more valuable than logcat. So hook me up

I'll send you the logcat and dmesg after a reboot and wifi enable... I will then reinstall and try again without backup & restore...


EDIT: uploaded logs. Question, should I wait for a new install with correct dates?

[[ACL]]

supporting mutiple is simple

on /data/modules we need a new directory with the uname of the kernel

Each kernel will use their own directory but mutiple an co-exist in there. So when we do a backup, we will always bakup the older modules in their old directories as well as leaving the new ones untouched. The final piece is to tell android to symlink /data/modules/uname to /data/modules . The uname gets filled in with the kernel info.

Now this has to run really early, even before the sysinit.sh, so it may need to be part of the initrd . I think we even have the command in there commented out.

I'm rerunning the autobuild. Hopefully that helps.

[[ACL]]

Originally Posted by m4f1050

I'll send you the logcat and dmesg after a reboot and wifi enable... I will then reinstall and try again without backup & restore...


EDIT: uploaded logs. Question, should I wait for a new install with correct dates?

Hmm.. i need it as you are trying to enable wifi. This dmesg is too early.

But you can prob tell since it will say on dmesg modules dont match
Edit: i checked the one online and the date is correct so i dont know why these modules would be bad. But im running it anyways.

[neopeek]

tried it out now several times (replaced sdcard too) but still have that bootloop issue on "waiting for sdcard" with 3-17 files. Seems like I have to wait for you to fix it as it works with older files

[m4f1050]

Originally Posted by [ACL]

Hmm.. i need it as you are trying to enable wifi. This dmesg is too early.

But you can prob tell since it will say on dmesg modules dont match
Edit: i checked the one online and the date is correct so i dont know why these modules would be bad. But im running it anyways.

I adb pulled that dmesg after I clicked on Wifi,waited for scan error, and saw that wifi was off... It would have the message if that was the case.

[natemcnutty]

Originally Posted by m4f1050

I'll send you the logcat and dmesg after a reboot and wifi enable... I will then reinstall and try again without backup & restore...


EDIT: uploaded logs. Question, should I wait for a new install with correct dates?

Here's your issue:

E/WifiHW ( 152): Supplicant not running, cannot connect

As for how to fix it, I think reinstalling the androidupdate.tgz should fix that.