Fix for Wifi Issue on Acqua with Blade III ROMs

[Guest mrjujas]

I found a way to fix the wifi problems on my Acqua. (TMN Version, bought in December 2012)

You just have to replace the proprietaries for wifi with the ones on your stock rom.

bin/hostapd

etc/firmware/ath6k/AR6003/hw2.1.1/athtcmd_ram.bin

etc/firmware/ath6k/AR6003/hw2.1.1/bdata.bin

etc/firmware/ath6k/AR6003/hw2.1.1/fw-3.bin

etc/firmware/ath6k/AR6003/hw2.1.1/nullTestFlow.bin

etc/firmware/ath6k/AR6003/hw2.1.1/utf.bin

wifi/ath6kl_sdio.ko

wifi/cfg80211.ko


# From KonstaT's sources (https://raw.github.com/KonstaT/android_device_zte_atlas40/cm-10.2/proprietary-files.txt)

Method 1

1. Boot into ClockWorkMod
   
2. Make a nandroid backup
   
3. Install wifi_patch-signed.zip
   
4. Reboot
   

Method 2 (use if Method 1 didn't work)

1. Get your stock rom from http://www.modaco.co...qua-stock-roms/ (or a backup you made before installing CyanogenMod)
   
2. Extract these binaries from /system (from update.zip or from the backup of your system partition)
   
   bin/hostapd
   etc/firmware/ath6k/AR6003/hw2.1.1/athtcmd_ram.bin
   etc/firmware/ath6k/AR6003/hw2.1.1/bdata.bin
   etc/firmware/ath6k/AR6003/hw2.1.1/fw-3.bin
   etc/firmware/ath6k/AR6003/hw2.1.1/nullTestFlow.bin
   etc/firmware/ath6k/AR6003/hw2.1.1/utf.bin
   wifi/ath6kl_sdio.ko
   wifi/cfg80211.ko
   
   
3. Download a CyanogenMod ROM for Blade III
   
4. Open it on 7zip (or other archive manager)
   
5. Go to /system
   
6. Replace the files listed in 2. with the ones you extracted
   
7. Put the modified CyanogenMod ROM on sdcard
   
8. Follow the instructions on the thread where you got the rom (always make a backup)
   

Please report if this works on your device.

If it doesn't work, restore the backup you made.

Thanks to KonstaT for his great roms :)

wifi_patch-signed.zip

[Guest KonstaT]

Great, I think I suggested that someone should try this at some point. :)

I did a quick diff and only system/etc/firmware/ath6k/AR6003/hw2.1.1/bdata.bin is different between Blade III and Acqua (but seems to be the same in every Acqua update).

Wifi modules (/system/wifi/*) are different even in every Blade III update because they are always (re)built in line with the kernel. Source code for Atheros wifi modules is also released under GPL license but guess again if you think ZTE is willing release the source even though they are legally obligated to do so. :P /bin/hostapd is for wifi tethering only.

[Guest mrjujas]

I did a quick diff and only system/etc/firmware/ath6k/AR6003/hw2.1.1/bdata.bin is different between Blade III and Acqua (but seems to be the same in every Acqua update).

Does that mean that the zip I uploaded just needs bdata.bin?

Edited September 2, 2013 by mrjujas

[Guest KonstaT]

Does that mean that the zip I uploaded just needs bdata.bin?

Yeah, and both wifi modules (/system/wifi/*) are likely necessary as well. I was just saying that even though they might have different checksums still doesn't mean that there are some actual differences (and there's no way of knowing even if there was). Huh, quite a complicated sentence. :P Doesn't hurt to have them all either...

[Guest mrjujas]

Doesn't hurt to have them all either...

Ok, I won't change it. Now we just have to wait until someone tests the fix.

About the source, I've found this. Would it work on Acquas without porting/changes? Or is it compatible at all?

[Guest KonstaT]

Ok, I won't change it. Now we just have to wait until someone tests the fix.

About the source, I've found this. Would it work on Acquas without porting/changes? Or is it compatible at all?

Yeah, it is a compatible driver for our wifi hardware but in practice it wouldn't work. Ath6kl driver is merged to linux mainline kernel from 3.4 onwards (or at least it is to CAF's msm-3.4). Porting it to our 3.0 kernel, and porting any other network dependencies, would be very difficult. On top of that it would require changes to make it work with ZTE wifi implementation just like below.

Easier solution would be to build ath6kl driver using compat-wireless driver. It's super easy to build (already done it) but it would still need to be modified to match any ZTE changes in our kernel. Even in the best case scenario it might be difficult make everything work as well as it does with the prebuilt binary modules.

http://wireless.kern...Download/stable

[Guest mrjujas]

Easier solution would be to build ath6kl driver using compat-wireless driver. It's super easy to build (already done it) but it would still need to be modified to match any ZTE changes in our kernel. Even in the best case scenario it might be difficult make everything work as well as it does with the prebuilt binary modules.

http://wireless.kern...Download/stable

If prebuilt binary modules work well, there is no need to mess around with that stuff.

Especially now, while porting CM 10.2, if I can help you with anything, including testing, please tell me. :D

[Guest papars]

IT WORKS!

Now it connects to my test Belkin router. I will tell friends to check.

BTW I have tried this solution in the past (earlier CM10.x builds) and it didn't work.

I'm on CM10.1 30/8/2013

Edited September 2, 2013 by papars

[Guest Skinz1984]

This works on mine too!

You're absolute legends mrjujas and KonstaT

[Guest alijnav]

Thank you very much!!!

[Guest KonstaT]

BTW I have tried this solution in the past (earlier CM10.x builds) and it didn't work.

It would have worked since the day one. It's safe to say that you just didn't do it correctly. :P

Unfortunately there isn't many people to test ideas and I have to rely on the feedback I get from the ones that do...

[Guest papars]

It would have worked since the day one. It's safe to say that you just didn't do it correctly. :P

When first started working with CM10 in acqua wifi was not connecting at all.

One of the first steps was to replace all the /etc/firmware directory in the CM10 builds with the one from the official ROM. I was modifying the CM10 .zip files.

It didn't work, so then I started playing with the mmc partitions and build.prop. This gave me part working wifi and I was happy since it worked in my home & office routers without problem.

Never thought to test again the firmware directory files.

@KonstaT Will you include this file in the next builds or we shall use the patch?

[Guest KonstaT]

@KonstaT Will you include this file in the next builds or we shall use the patch?

No, not going to change it and potentially break wifi for all Blade III's.

[Guest harusame]

I did set your patch. With the connection to the Wi-Fi problems are now gone, but the internet and I can `t get out. And connection icon is gray.

[Guest mrjujas]

I did set your patch. With the connection to the Wi-Fi problems are now gone, but the internet and I can `t get out. And connection icon is gray.

I see your device is an Acqua variant, so I got a stock rom for your device and the only wifi binaries which are different are the ones at /system/wifi/. So I got you a zip with those files (ath6kl_sdio.ko and cfg80211.ko). Make a backup and flash it. (I'm not sure it solves your problem, because these are built in line with the kernel, and they may be different but not actually make a difference)

In case that doesn't work, you can make a backup and reinstall CM 10.1 following the instructions at KonstaT's thread, then install the fix from the main post and then install the fix in this post. After that connect to your wifi network and test your internet connection with the browser instead of the Play Маркет (btw change your system language to English when sharing screenshots).

If nothing works, restore your backup. :)

PS : Test whether that wifi network is connected to the internet with other device (like a laptop)

wifi_patch_v880e-signed.zip

Edited September 3, 2013 by mrjujas

[Guest harusame]

I see your device is an Acqua variant, so I got a stock rom for your device and the only wifi binaries which are different are the ones at /system/wifi/. So I got you a zip with those files (ath6kl_sdio.ko and cfg80211.ko). Make a backup and flash it. (I'm not sure it solves your problem, because these are built in line with the kernel, and they may be different but not actually make a difference)

In case that doesn't work, you can make a backup and reinstall CM 10.1 following the instructions at KonstaT's thread, then install the fix from the main post and then install the fix in this post. After that connect to your wifi network and test your internet connection with the browser instead of the Play Маркет (btw change your system language to English when sharing screenshots).

If nothing works, restore your backup. :)

PS : Test whether that wifi network is connected to the internet with other device (like a laptop)

Thank you for your contribution from your side. Internet without any problems dealt modem via Wi-Fi to other device and the PC.

Next time I will consider your remark about the screenshots. I will try to set your file with the patch.

[Guest harusame]

mrjujas,

Flashed the patch that you threw off me .. And praise be to programmers! Internet working! =))) I hope now it's forever, and will not disappear after the first reboot device.

But here's the icon has remained small gray instead of little white which indicates a successful connection. But I think the little things =)

[Guest mrjujas]

Flashed the patch that you threw off me .. And praise be to programmers! Internet working! =))) I hope now it's forever, and will not disappear after the first reboot device.

But here's the icon has remained small gray instead of little white which indicates a successful connection. But I think the little things =)

I'm not really a programmer, I just searched some stuff on the internet and replaced some files.

Anyway, I'm glad I could help you. :D

[Guest MJonMoDaCo]

I see your device is an Acqua variant, so I got a stock rom for your device and the only wifi binaries which are different are the ones at /system/wifi/. So I got you a zip with those files (ath6kl_sdio.ko and cfg80211.ko). Make a backup and flash it. (I'm not sure it solves your problem, because these are built in line with the kernel, and they may be different but not actually make a difference)

In case that doesn't work, you can make a backup and reinstall CM 10.1 following the instructions at KonstaT's thread, then install the fix from the main post and then install the fix in this post. After that connect to your wifi network and test your internet connection with the browser instead of the Play Маркет (btw change your system language to English when sharing screenshots).

If nothing works, restore your backup. :)

PS : Test whether that wifi network is connected to the internet with other device (like a laptop)

Hello mrjujas,

Thanks for your fix. It's worked on CM 10.1.3, and, me being me, I decided to install it manually (injecting all files/folders into the ROM zip). That was fine. But now I've gone and installed KonstaT's newest 4.3 update. I can browse the internet with any of my browsers (Built-in, Opera and Dolphin), and they work... But not the Play Store. I can't connect to it unless I do it in the web browser... Have you heard of this situation, and what may be causing it? Just to clarify... I tried it without the fix the first time around (that's when I noticed the problem) and then I tried it with the fix - and it's still occuring! Any ideas?

[Guest mrjujas]

Hello mrjujas,

Thanks for your fix. It's worked on CM 10.1.3, and, me being me, I decided to install it manually (injecting all files/folders into the ROM zip). That was fine. But now I've gone and installed KonstaT's newest 4.3 update. I can browse the internet with any of my browsers (Built-in, Opera and Dolphin), and they work... But not the Play Store. I can't connect to it unless I do it in the web browser... Have you heard of this situation, and what may be causing it? Just to clarify... I tried it without the fix the first time around (that's when I noticed the problem) and then I tried it with the fix - and it's still occuring! Any ideas?

I've just upgraded to CM 10.2 (4.3), and the Play Store works fine. :)

Did you wipe data and format /system before installing CM 10.2?

[Guest MJonMoDaCo]

I've just upgraded to CM 10.2 (4.3), and the Play Store works fine. :)

Did you wipe data and format /system before installing CM 10.2?

Yes i did. Might be a bad download. I'll try again.

[Guest fcm123]

It was cool to do a tutorial to install the rom and the wifi fix in acqua for noobs like me, do not mess up, and can take advantage of this wonder. I and others would appreciate a lot ...
Best regards!

[Guest killerofshadows]

Sorry to bump an old topic guys.

I ran the WiFi patch that was part of the Blade III to Acqua patch that KonstaT had up on this board. However after running the patch I started noticing issues with WiFi.

Phone Model, OS, Settings
Unofficial CyanogenMod 10.2 KonstaT 20131220 and Unofficial CyanogenMod 11 KonstaT 20140114

Telecom (ZTE) R22

 

Keep WiFi on during sleep only when plugged in.

Avoid poor connections.

WiFi Optimization.

Problem Description
After about 3+ hours the WiFi doesn't connect back to the wireless access point again after waking up the device. Any applications that use WiFi also have issues accessing it. I notice that when I attempt to open the WiFi screen (to view a list of access points in range) nothing seems to happen (it just sits at the WiFi screen and the list is blank and the Off/On toggle does not appear). When I turn off and on the WiFi via the Quick Settings Panel everything seems to start working again.

 

This has occurred on new flashes of KonstaT's Blade III CM builds I've done over the past few days. Yet they never used to have this problem before which leads me to the next point...

 

Possible Cause
Installing the Blade III to Acqua patch. Before this I didn't really notice any issues for WiFi. Apparently according to MJonMoDaCo our regions (New Zealand) WiFi modules are pretty good?!? I never noticed an issue with it before applying this patch.

Unfortunately, I tried applying the wifi_patch-signed.zip patch on this forum, the phone still does the same thing. Now I tried uncompressing the firmware update file for the Telecom R22 in another post on this sub forum to follow the instruction in this thread, yet the wifi/ath6kl_sdio.ko and wifi/cfg80211.ko files are missing from the update.zip file.

Conclusion
I am going to sound like a noob here, so can uhhh anyone point me into the right direction here on how to progress forward? I am considering installing stock again, but because its lacking the two ko files, I am uncertain if this will effect anything - but hey, I'm posting here to rake the minds of the more experienced, if they so be inclined.

Thanks all.

 

Logcat

Excerpt of logcat pulled from Eclipse: note errors with the wlan0 - no such device!?! Might have to run on stock and see what happens.

01-23 16:53:27.087: D/AccelerometerListener(854): enable(false)
01-23 16:53:27.207: E/wpa_supplicant(14865): Could not read interface wlan0 flags: No such device
01-23 16:53:27.207: I/wpa_supplicant(14865): wlan0: CTRL-EVENT-DRIVER-STATE STARTED
01-23 16:53:28.108: D/PowerManagerService-JNI(491): Excessive delay in autosuspend_disable() while turning screen on: 549ms
01-23 16:53:28.108: D/SurfaceFlinger(110): Screen acquired, type=0 flinger=0x40bda478
01-23 16:53:29.799: I/PowerManagerService(491): Going to sleep by user request...
01-23 16:53:30.400: D/LightsService(491): Excessive delay setting light: 76ms
01-23 16:53:30.440: D/SurfaceFlinger(110): Screen released, type=0 flinger=0x40bda478
01-23 16:53:30.690: D/PhoneApp(854): mReceiver: ACTION_SCREEN_OFF / ACTION_SCREEN_ON
01-23 16:53:30.690: D/AccelerometerListener(854): enable(false)
01-23 16:53:31.051: V/KeyguardHostView(491): hide transport, gen:32
01-23 16:53:31.051: V/KeyguardHostView(491): music state changed: 0
01-23 16:53:31.327: I/Choreographer(491): Skipped 56 frames!  The application may be doing too much work on its main thread.
01-23 16:54:15.100: E/WifiStateMachine(491): Driver start failed, retrying
01-23 16:54:15.100: E/wpa_supplicant(14865): Could not read interface wlan0 flags: No such device
01-23 16:54:15.100: I/wpa_supplicant(14865): wlan0: CTRL-EVENT-DRIVER-STATE STARTED
01-23 16:54:32.741: E/WifiStateMachine(491): Failed to start driver after 2
01-23 16:55:13.897: I/PowerManagerService(491): Waking up from sleep...
01-23 16:55:14.027: I/WindowManager(491): Lock screen displayed!
01-23 16:55:14.087: D/PhoneApp(854): mReceiver: ACTION_SCREEN_OFF / ACTION_SCREEN_ON
01-23 16:55:14.087: D/AccelerometerListener(854): enable(false)
01-23 16:55:14.147: E/wpa_supplicant(14865): Could not read interface wlan0 flags: No such device
01-23 16:55:14.147: I/wpa_supplicant(14865): wlan0: CTRL-EVENT-DRIVER-STATE STARTED
01-23 16:55:14.587: D/PowerManagerService-JNI(491): Excessive delay in autosuspend_disable() while turning screen on: 585ms
01-23 16:55:14.617: D/SurfaceFlinger(110): Screen acquired, type=0 flinger=0x40bda478
01-23 16:55:22.685: D/AudioHardwareMSM76XXA(114): Bufsize 4800
01-23 16:55:22.685: D/AudioHardwareMSM76XXA(114): SampleRate 44.1k
01-23 16:55:22.685: D/AudioHardwareMSM76XXA(114): Bufsize 4800
01-23 16:55:22.685: D/AudioHardwareMSM76XXA(114): SampleRate 44.1k
01-23 16:55:22.685: I/AudioHardwareMSM76XXA(114): Routing audio to Speakerphone
01-23 16:55:22.705: D/AudioHardwareMSM76XXA(114): SampleRate 44.1k
01-23 16:55:22.705: D/AudioHardwareMSM76XXA(114): Bufsize 4800
01-23 16:55:22.725: D/PhoneStatusBar(746): disable: < expand icons alerts ticker system_info BACK HOME recent* CLOCK search >
01-23 16:55:22.775: D/PhoneStatusBar(746): disable: < expand icons alerts ticker system_info back* home* recent clock* search >
01-23 16:55:22.895: W/InputMethodManagerService(491): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@42485440 attribute=android.view.inputmethod.EditorInfo@41ba19a0, token = android.os.BinderProxy@41e8e408
01-23 16:55:22.965: D/AudioHardwareMSM76XXA(114): Bufsize 4800
01-23 16:55:22.965: D/AudioHardwareMSM76XXA(114): SampleRate 44.1k
01-23 16:55:22.975: D/AudioHardwareMSM76XXA(114): Bufsize 4800
01-23 16:55:22.975: D/AudioHardwareMSM76XXA(114): SampleRate 44.1k
01-23 16:55:22.985: D/AudioHardwareMSM76XXA(114): Bufsize 4800
01-23 16:55:22.985: D/AudioHardwareMSM76XXA(114): SampleRate 44.1k
01-23 16:55:23.005: D/AudioHardwareMSM76XXA(114): Bufsize 4800
01-23 16:55:23.005: D/AudioHardwareMSM76XXA(114): SampleRate 44.1k
01-23 16:55:23.015: W/IInputConnectionWrapper(30784): getTextBeforeCursor on inactive InputConnection
01-23 16:55:23.256: V/TAG(491): bug 7643792: fitSystemWindows([0,38][0,0])
01-23 16:55:23.646: D/Mms:app(30784): cancelNotification
01-23 16:55:23.666: D/Mms:app(30784): cancelNotification
01-23 16:55:23.866: D/Mms:app(30784): cancelNotification
01-23 16:55:23.896: D/Mms:app(30784): cancelNotification
01-23 16:55:23.916: D/Mms:app(30784): cancelNotification
01-23 16:55:23.966: D/Mms:app(30784): cancelNotification
01-23 16:55:24.166: E/WifiStateMachine(491): Driver start failed, retrying
01-23 16:55:24.166: E/wpa_supplicant(14865): Could not read interface wlan0 flags: No such device
 

Edited January 23, 2014 by killerofshadows

[Guest MJonMoDaCo]

G'day!

Did you manage to try here:

ZTE Support Centre

Pick NZ in first box and smartphone in 2nd box. There is probably still 3 entries for the R22 like when I last got it, but only 1 of those entries had the zip.

I personally didn't bother with the WiFi patch myself, as it seemed not to be a problem (ain't broke, why fix it, right?), hence my opinion of the WiFi modules. You'll probably want to flash that stock ROM I just pointed you to, and replace all relevant files in the patch with the ones from the stock ROM... But, I would try flashing stock, then CyanogenMod, then (and only if you have troubles) the patch. My CM10.2 ROM is unpatched (4.3).

Haven't tested CM11 enough to consider it needing the patch yet, but I'm going back soon. Will let you know the results.

Best,

MJ

Edited January 24, 2014 by MJonMoDaCo

[Guest Jo Mo]

Hi all. Same wifi problem here on my ZTE Skate Acqua aka TMN Smart A15. Since I'm an old "newbie" guy, I don't have the knowledge to come up with a fix for this issue, but nevertheless I found an app that solved my problem and maybe you guys could check it out, in order to understand how it does what he does. I just installed it, ran it, followed some procedures and instructions and let it do its stuff. It took a while, but in the end... Success! The app it's called wifi fixer and you can get it on the play store. I would really appreciate if this post could help anyone out. BOA SORTE!