Jump to content

Recommended Posts

Guest Amphoras
Posted (edited)

When I try to install this in clockworkmod 5.0.2.0 it sais "can't open <file> (bad)" I've checked the md5. Any ideas? what versions of clockworkmod has it worked on?

It worked for me on Clockwork 5.0.2.0.

About the wifi, in the logcat I get errors like this:

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

and

E/wpa_supplicant( 831): Unsupported driver 'awext'.

Does that mean the driver for the wpa supplicant isn't there/isn't correct, so it can't run meaning the hardware can't connect?

Is this one of the this you took out KonstaT or does it just need fixing.

Edit: about the sdcard, I get this in the logcat:

I/Vold ( 94): Filesystem check completed OK

I/Vold ( 94): Device /dev/block/vold/179:1, target /mnt/sdcard mounted @ /mnt/secure/staging

E/Vold ( 94): Failed to move mount /mnt/secure/staging -> /mnt/sdcard (No such file or directory)

E/Vold ( 94): Failed to move mount (No such file or directory)

D/Vold ( 94): Volume sdcard state changing 3 (Checking) -> 1 (Idle-Unmounted)

D/MountService( 157): volume state changed for /mnt/sdcard (checking -> unmounted)

E/MountService( 157): Boot-time mount failed (-1)

Edited by Amphoras
Guest t0mm13b
Posted (edited)

wireless-tools is missing from AOSP... copy it from CM7's repo into AOSP and compile it?

Edit:

wpa_supplicant driver needs to be patched up to include awext driver support... in external/wpa_supplicant.

Edit 2:

Have added the necessary files to the ics4blade github repo, in external/wpa_supplicant :)

Edited by t0mm13b
Guest Amphoras
Posted

The alarm works ok, just no sound. It vibrates though.

Guest Racerboy
Posted (edited)

@t0mm13b the vold in bin folder is part of mounting system for sdcard along with kernal? we had problem with racer mounting sdcard a while ago with newer builds of cyanogen for blade, the vold file was ammended and fixed the issue, just a thought :)

Edited by Racerboy
Guest t0mm13b
Posted

I have set up an irc channel on freenode.net for this if you need instant responses.

Check it out @ #ics4blade on freenode.net :D :)

Guest KonstaT
Posted (edited)

Does that mean the driver for the wpa supplicant isn't there/isn't correct, so it can't run meaning the hardware can't connect?

Is this one of the this you took out KonstaT or does it just need fixing.

Edit: about the sdcard, I get this in the logcat:

So for some reason /mnt/sdcard doesn't exist.

I haven't removed any wifi related stuff from my ICS source. What I have removed is:

libaudio completely, from blade device tree and from hardware/msm7k/Android.mk


common_msm_dirs := libcopybit liblights libopencorehw librpc libstagefrighthw
msm7k_dirs := $(common_msm_dirs) boot libgralloc
# libaudio
qsd8k_dirs := $(common_msm_dirs) libgralloc-qsd8k libaudio-qsd8k dspcrashd
msm7x30_dirs := liblights libgralloc-qsd8k librpc libaudio-qdsp5v2
[/code]

webrtc, removed whole /external/webrtc folder

audiopreprocessing, renamed Android.mk in frameworks/base/media/libeffects/preprocessing/

libril is removed from my zte blade device tree

edit. removed something stupid...

Edited by KonstaT
Guest t0mm13b
Posted (edited)

Just a FYI on something... (have recompiled the wpa_supplicant) but failed...

Went into adb shell


255|root@android:/system/wifi # insmod /system/wifi/ar6000.ko                  

insmod: init_module '/system/wifi/ar6000.ko' failed (Exec format error)

255|root@android:/system/wifi # 

:huh:

(Kernel/modules from CM7 nightly 255 build, anyone explain that?)

Edited by t0mm13b
Guest KonstaT
Posted (edited)

wireless-tools is missing from AOSP... copy it from CM7's repo into AOSP and compile it?

Edit:

wpa_supplicant driver needs to be patched up to include awext driver support... in external/wpa_supplicant.

Edit 2:

Have added the necessary files to the ics4blade github repo, in external/wpa_supplicant :)

Wifi is working! :D

Attached patched wpa_supplicant. Unzip and replace the one in /system/bin/.

wpa_supplicant.zip

Edited by KonstaT
Guest Amphoras
Posted

Wifi is working! :D

Attached patched wpa_supplicant. Unzip and replace the one in /system/bin/.

Pushed it to system using adb push wpa_supplicant /system/bin/wpa_supplicant

Its definitely there as I get the same file back it I then do adb pull. However wifi still isn't working. When I turn it on, it just sits at "Turning WiFi on..." Tried a full wipe before pushing the file and I get the same. Is that the right command to put it there or do I need to do anything else like permissions?

Logcat still gives E/WifiStateMachine( 139): Failed to start supplicant!

Posted

Wifi is working! :D

Attached patched wpa_supplicant. Unzip and replace the one in /system/bin/.

Not working for me.

Did you modify any other file?

Guest Racerboy
Posted

Wifi is working! :D

comfirmed working here on Racer, thx :)

Guest skywave
Posted

Adb push didn't work, so i replace the file in the flashable zip and flashed again. Confirm it sees my network :)

Guest dream smile
Posted

sry for late reply:

with the latest hero alpha4 i have full screen without the virtual soft keys imposed on the main screen, sound works (had to modify the vold.fstab to mount sdcard to play music) also changed the build.prop slightly and changed the libhtc_ril.so

no network but i kinda expected that....

This is tested on Racer not Blade

你好~~~~~~~~~~
Guest Racerboy
Posted

你好~~~~~~~~~~

best place would be to ask in the Racer forum as this thread is for the devs that are working on ICS for the Blade

Guest LordMeltdown
Posted

Wifi is working! :D

Attached patched wpa_supplicant. Unzip and replace the one in /system/bin/.

it worked for me!

thanks

Guest t0mm13b
Posted

Wifi is working! :D

Attached patched wpa_supplicant. Unzip and replace the one in /system/bin/.

To confirm, that was from the repo pushed earlier? :)

Guest KonstaT
Posted

To confirm, that was from the repo pushed earlier? :)

Yep, patch from your github. :)

Guest skywave
Posted

On a sidenote, i had to wifi turn off and on again before it saw my network. But it works :)

Great progress

Guest Amphoras
Posted

Pushed it to system using adb push wpa_supplicant /system/bin/wpa_supplicant

Its definitely there as I get the same file back it I then do adb pull. However wifi still isn't working. When I turn it on, it just sits at "Turning WiFi on..." Tried a full wipe before pushing the file and I get the same. Is that the right command to put it there or do I need to do anything else like permissions?

Logcat still gives E/WifiStateMachine( 139): Failed to start supplicant!

Unzipped the rom and put it in there then flashed it and now it works.

Guest KonstaT
Posted

pulled latest code from https://github.com/t0mm13b/ics4blade and AOSP master and this is what happens when I compile:

You still need to add resources to config.xml.


<!-- Regex array of allowable upstream ifaces for tethering - for example if you want
tethering on a new interface called "foo2" add <item>"foo\\d"</item> to the array -->
<add-resource type="string" name="config_tether_upstream_regexs">
<string-array translatable="false" name="config_tether_upstream_regexs">
<item>"rmnet\\d"</item>
<item>"wlan\\d"</item>
</string-array>
</add-resource>
<!-- List of regexpressions describing the interface (if any) that represent tetherable
Wifi interfaces. If the device doesn't want to support tethering over Wifi this
should be empty. An example would be "softap.*" -->
<string-array translatable="false" name="config_tether_wifi_regexs">
<item>"athap0"</item>
</string-array>


<!-- Boolean indicating if we require the use of DUN on mobile for tethering -->
<add-resource type="bool" name="config_tether_dun_required">
<bool translatable="false" name="config_tether_dun_required">false</bool>
</add-resource>
<!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap -->
<integer-array name="config_keyboardTapVibePattern">
<item>30</item>
</integer-array>
</resources>
[/code]

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.