[Huawei Ascend G330]Come compilare il kernel Huawei v3.0.21

Quote:

---

Originariamente inviato da agd

Ok quindi se si riesce a compilare il kerbel del g510 non centra niente col baseband


Inviato dal mio HUAWEI U8825-1 usando Androidiani App

---

Non c'entra niente ma il problema sono i drivers. Se qualcuno manca devi portarlo nel kernel G510 dal kernel G330. Tuttavia se la diversa versione del kerne ha cambiato le interfacce verso il driver potrebbe non compilare o meglio compilare e non funzionare correttamente...

Quote:

---

Originariamente inviato da Ikon

Quote:

---

Originariamente inviato da agd
Ok quindi se si riesce a compilare il kerbel del g510 non centra niente col baseband


Inviato dal mio HUAWEI U8825-1 usando Androidiani App

---

Non c'entra niente ma il problema sono i drivers. Se qualcuno manca devi portarlo nel kernel G510 dal kernel G330. Tuttavia se la diversa versione del kerne ha cambiato le interfacce verso il driver potrebbe non compilare o meglio compilare e non funzionare correttamente...

---

Ok ho capito


Inviato dal mio HUAWEI U8825-1 usando Androidiani App

Quote:

---

Originariamente inviato da agd

Ok ho capito


Inviato dal mio HUAWEI U8825-1 usando Androidiani App

---

Ho detto una cazzata... probabilmente non hai i sorgenti del driver. Quindi non compili un bel niente! Sono stato troppo ottimista... :P Puoi solo piazzare un firmware vecchio in una ROM nuova e sperare che riesci a far andare la baracca...

Hey folks!

First of all a huge thanks to Ikon for your great tutorial! I followed all steps and was able to compile the kernel successfully. However my WiFi and Bluetooth are broken and I don't know what went wrong. I applied the kernel to a clean boot.img (version B958) and flashed it via CWM to the phone. All .ko-files have been copied to /system/lib/modules aswell and signatures of the files are correct.

Everytime I try to enable WiFi or Bluetooth I'm getting these errors in LogCat:

Spoiler:

D/MobileDataButton( 374): ----------------------------------------------------- D/MobileDataButton( 374): Data Connection: off D/MobileDataButton( 374): ----------------------------------------------------- D/PowerButton( 374): ----------------------------------------------------- D/PowerButton( 374): GPS: off D/PowerButton( 374): ----------------------------------------------------- D/ToolBox ( 600): isDoubleCardDevice false V/ToolBoxProvider( 600): simstatus : 5 phoneType : 1 D/ToolBox ( 600): numeric: 26202 ; CT_NUMERIC :46003 D/StateMachine( 289): handleMessage: E msg.what=131073 D/StateMachine( 289): processMsg: DriverFailedState D/WifiStateMachine( 289): DriverFailedState{ what=131073 when=0 arg1=2 } D/StateMachine( 289): processMsg: DriverUnloadedState D/WifiStateMachine( 289): DriverUnloadedState{ what=131073 when=0 arg1=2 } D/StateMachine( 289): StateMachine.transitionTo EX destStateWaitForP2pDisableState D/StateMachine( 289): handleMessage: new destination call exit D/StateMachine( 289): setupTempStateStackWithStatesToEnter: X mTempStateStackCount=1,curStateInfo: state=DefaultState,active=true,parent=null D/StateMachine( 289): invokeExitMethods: DriverFailedState D/StateMachine( 289): invokeExitMethods: DriverUnloadedState D/StateMachine( 289): moveTempStackToStateStack: i=0,j=1 D/StateMachine( 289): moveTempStackToStateStack: X mStateStackTop=1,startingIndex=1,Top=WaitForP2pDis ableState D/StateMachine( 289): invokeEnterMethods: WaitForP2pDisableState D/WifiStateMachine( 289): WaitForP2pDisableState D/StateMachine( 289): handleMessage: X D/StateMachine( 289): handleMessage: E msg.what=131083 D/StateMachine( 289): processMsg: WaitForP2pDisableState D/WifiStateMachine( 289): WaitForP2pDisableState{ what=131083 when=-2ms } D/StateMachine( 289): deferMessage: msg=131083 D/StateMachine( 289): handleMessage: X D/StateMachine( 289): handleMessage: E msg.what=143362 D/StateMachine( 289): processMsg: WaitForP2pDisableState D/WifiStateMachine( 289): WaitForP2pDisableState{ what=143362 when=-1ms } D/StateMachine( 289): StateMachine.transitionTo EX destStateDriverLoadingState D/StateMachine( 289): handleMessage: new destination call exit D/StateMachine( 289): setupTempStateStackWithStatesToEnter: X mTempStateStackCount=1,curStateInfo: state=DefaultState,active=true,parent=null D/StateMachine( 289): invokeExitMethods: WaitForP2pDisableState D/StateMachine( 289): moveTempStackToStateStack: i=0,j=1 D/StateMachine( 289): moveTempStackToStateStack: X mStateStackTop=1,startingIndex=1,Top=DriverLoading State D/StateMachine( 289): invokeEnterMethods: DriverLoadingState D/WifiStateMachine( 289): DriverLoadingState E/WifiService( 289): Invoking mWifiStateMachine.setWifiEnabled D/StateMachine( 289): moveDeferredMessageAtFrontOfQueue; what=131083 D/StateMachine( 289): handleMessage: X D/StateMachine( 289): handleMessage: E msg.what=131083 D/StateMachine( 289): processMsg: DriverLoadingState D/WifiStateMachine( 289): DriverLoadingState{ what=131083 when=-2m5s301ms } D/StateMachine( 289): deferMessage: msg=131083 D/StateMachine( 289): handleMessage: X D/WifiStateMachine( 289): setWifiState: enabling W/WifiHW ( 289): chip_type = 2.1 E/WifiHW ( 289): ensure_wlan_driver_config_file_exist is ok W/SignalStrength( 374): getLTELevel - rsrp:2147483647 snr:2147483647 rsrpIconLevel:-1 snrIconLevel:-1 W/SignalStrength( 374): getLTELevel - rssi:99 rssiIconLevel:0 W/SignalStrength( 374): getGsmLevel=4 W/SignalStrength( 374): getLevel=4 D/MobileDataButton( 374): ----------------------------------------------------- D/MobileDataButton( 374): Data Connection: off D/MobileDataButton( 374): ----------------------------------------------------- D/PowerButton( 374): ----------------------------------------------------- D/PowerButton( 374): GPS: off D/PowerButton( 374): ----------------------------------------------------- D/StatusBar.NetworkController( 374): refreshViews connected={ } level=4 combinedSignalIconId=0x7f03009e/com.android.systemui:drawable/stat_sys_signal_4 combinedActivityIconId=0x0 mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x7f03009e mDataDirectionIconId=0x0 mDataSignalIconId=0x7f03009e mDataTypeIconId=0x0 mNoSimIconId=0x0 mWifiIconId=0x0 mBluetoothTetherIconId=0x1080535 D/ConnectivityService( 289): getMobileDataEnabled returning false E/WifiHW ( 289): origin softmac: 0C:37C:E2:AF:0D E/WifiHW ( 289): ath_write_softmac is ok W/WifiHW ( 289): load modle :/data/misc/wifi/load/ar6000.ko suspend_mode=3 D/ToolBox ( 600): isDoubleCardDevice false V/ToolBoxProvider( 600): simstatus : 5 phoneType : 1 D/ToolBox ( 600): numeric: 26202 ; CT_NUMERIC :46003 E/WifiHW ( 289): insmod fail! E/WifiStateMachine( 289): Failed to load driver! D/WifiStateMachine( 289): setWifiState: unknown state W/SignalStrength( 374): getLTELevel - rsrp:2147483647 snr:2147483647 rsrpIconLevel:-1 snrIconLevel:-1 W/SignalStrength( 374): getLTELevel - rssi:99 rssiIconLevel:0 W/SignalStrength( 374): getGsmLevel=4 W/SignalStrength( 374): getLevel=4 D/StatusBar.NetworkController( 374): refreshViews connected={ } level=4 combinedSignalIconId=0x7f03009e/com.android.systemui:drawable/stat_sys_signal_4 combinedActivityIconId=0x0 mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x7f03009e mDataDirectionIconId=0x0 mDataSignalIconId=0x7f03009e mDataTypeIconId=0x0 mNoSimIconId=0x0 mWifiIconId=0x0 mBluetoothTetherIconId=0x1080535 D/StateMachine( 289): handleMessage: E msg.what=131076 D/StateMachine( 289): processMsg: DriverLoadingState D/WifiStateMachine( 289): DriverLoadingState{ what=131076 when=-9ms } D/StateMachine( 289): StateMachine.transitionTo EX destStateDriverFailedState D/StateMachine( 289): handleMessage: new destination call exit D/StateMachine( 289): setupTempStateStackWithStatesToEnter: X mTempStateStackCount=2,curStateInfo: state=DefaultState,active=true,parent=null D/StateMachine( 289): invokeExitMethods: DriverLoadingState D/StateMachine( 289): moveTempStackToStateStack: i=1,j=1 D/StateMachine( 289): moveTempStackToStateStack: i=0,j=2 D/StateMachine( 289): moveTempStackToStateStack: X mStateStackTop=2,startingIndex=1,Top=DriverFailedS tate D/StateMachine( 289): invokeEnterMethods: DriverUnloadedState D/WifiStateMachine( 289): DriverUnloadedState D/StateMachine( 289): invokeEnterMethods: DriverFailedState E/WifiStateMachine( 289): DriverFailedState D/StateMachine( 289): moveDeferredMessageAtFrontOfQueue; what=131083 D/StateMachine( 289): handleMessage: X D/StateMachine( 289): handleMessage: E msg.what=131083 D/StateMachine( 289): processMsg: DriverFailedState D/WifiStateMachine( 289): DriverFailedState{ what=131083 when=-2m5s467ms } D/StateMachine( 289): processMsg: DriverUnloadedState D/WifiStateMachine( 289): DriverUnloadedState{ what=131083 when=-2m5s467ms } D/StateMachine( 289): processMsg: DefaultState D/WifiStateMachine( 289): DefaultState{ what=131083 when=-2m5s467ms } D/StateMachine( 289): handleMessage: X D/ConnectivityService( 289): getMobileDataEnabled returning false D/MobileDataButton( 374): ----------------------------------------------------- D/MobileDataButton( 374): Data Connection: off D/MobileDataButton( 374): -----------------------------------------------------

Have you experienced similar issues?

Thanks in advance,
DemonFirefox

PS: Sorry for writing in english ;)

Have you tried to launch wifi and bluetooth modules manually from terminal emulator?

Hello Demon thank you and don't worry for writing in English. I think my patch is not changing anything important, since I just added some #pragmas to avoid errors using GCC 4.7. First time I compiled I used GCC 4.4 and I didn't need that #pragmas. Anyway in both cases I had to do a fix related to the bluetooth in /arch/arm/mach-msm/board-msm7x27a.c:

+#if (defined(HUAWEI_BT_BLUEZ_VER30) || (!defined(CONFIG_HUAWEI_KERNEL)))
msm7627a_bt_power_init();
+#endif

As you can see I conditionally removed the initialization of the bluetooth module. Usually BT and WIFI modules are on the same chip... and this could explain your problems. I don't know why, but in the other source files all the function calls to the msm7627a_bt stuff are under conditional compilation. In the makefile we should set HUAWEI_BT_BLUEZ_VER30=1.

I will make a try and let you know. If you find a solution before me tell me... I can't spend a lot of time on that since I'm quite busy.

P.S.: I remember that in a previous of the post #1 I wrote "check if the BT works aftere this change" :P

Quote:

---

Originariamente inviato da Ikon

Hello Demon thank you and don't worry for writing in English. I think my patch is not changing anything important, since I just added some #pragmas to avoid errors using GCC 4.7. First time I compiled I used GCC 4.4 and I didn't need that #pragmas. Anyway in both cases I had to do a fix related to the bluetooth in /arch/arm/mach-msm/board-msm7x27a.c:

+#if (defined(HUAWEI_BT_BLUEZ_VER30) || (!defined(CONFIG_HUAWEI_KERNEL)))
msm7627a_bt_power_init();
+#endif

As you can see I conditionally removed the initialization of the bluetooth module. Usually BT and WIFI modules are on the same chip... and this could explain your problems. I don't know why, but in the other source files all the function calls to the msm7627a_bt stuff are under conditional compilation. In the makefile we should set HUAWEI_BT_BLUEZ_VER30=1.

I will make a try and let you know. If you find a solution before me tell me... I can't spend a lot of time on that since I'm quite busy.

P.S.: I remember that in a previous of the post #1 I wrote "check if the BT works aftere this change" :P

---

I just launched:

ikon@virtualbox:~/Desktop/kernel$ grep -r HUAWEI_BT_BLUEZ_VER30 .

And I found:

./Makefile:KBUILD_CFLAGS += -DHUAWEI_BT_BLUEZ_VER30

This means the BT module will be initialized... moreover in my .config I found:

CONFIG_HUAWEI_KERNEL=y

I also found:

# CONFIG_HUAWEI_KERNEL_DEBUG is not set

You could try to set in .config "CONFIG_HUAWEI_KERNEL_DEBUG=y" and probably you will get further infos about your issue.

Quote:

---

Originariamente inviato da Ikon

I just launched:

ikon@virtualbox:~/Desktop/kernel$ grep -r HUAWEI_BT_BLUEZ_VER30 .

And I found:

./Makefile:KBUILD_CFLAGS += -DHUAWEI_BT_BLUEZ_VER30

This means the BT module will be initialized... moreover in my .config I found:

CONFIG_HUAWEI_KERNEL=y

I also found:

# CONFIG_HUAWEI_KERNEL_DEBUG is not set

You could try to set in .config "CONFIG_HUAWEI_KERNEL_DEBUG=y" and probably you will get further infos about your issue.

---

By the way, I don't believe that kernel is really ok. If you try to compile it (with GCC 4.4) you get an error in /arch/arm/mach-msm/board-msm7x27a.c. This means Huawei developers have never compiled it, so I'm not sure whether this kernel is the working one or not!!!

Quote:

---

Originariamente inviato da Ikon

By the way, I don't believe that kernel is really ok. If you try to compile it (with GCC 4.4) you get an error in /arch/arm/mach-msm/board-msm7x27a.c. This means Huawei developers have never compiled it, so I'm not sure whether this kernel is the working one or not!!!

---

Ok the problem is the following. Reverting the changes about the bluetooth I get again the following error:

arch/arm/mach-msm/board-msm7x27a.c: In function ‘msm7x2x_init’:
arch/arm/mach-msm/board-msm7x27a.c:1495:2: error: implicit declaration of function ‘msm7627a_bt_power_init’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[1]: *** [arch/arm/mach-msm/board-msm7x27a.o] Errore 1
make: *** [arch/arm/mach-msm] Errore 2

The function:

msm7627a_bt_power_init

Is declared in /arch/arm/mach-msm/board-msm7627a.h. Here we have:

codice:

---

#if (defined(HUAWEI_BT_BLUEZ_VER30) || (!defined(CONFIG_HUAWEI_KERNEL)))
/* ... */
void __init msm7627a_bt_power_init(void);
#endif

#if (defined(HUAWEI_BT_BTLA_VER30) && defined(CONFIG_HUAWEI_KERNEL))
/* ... */
void __init msm7627a_bt_power_init(void);
/* ... */
#endif

---

Using the #error directive I noticed that none of the declarations is compiled... it's so weird :/

Anyway we need a fix in the patch file I did it in the post #1... moreover I am going to test the configuration here: /arch/arm/configs/hw_msm8x25_defconfig (with some changes on the camera, I read our camera can work at 8Mpx... the problem is my autofocus sensor has broken when my phone fell down on the ground :()

Si potrebbe provare a compilare questi source del kernel 3.4 della cm10 per g510 http://link2.tapatalk.com/?id=11082X...26c9e0c&sref=4