Obsolete
Status Update
No update yet.
Comments
ti...@gmail.com
I'm experiencing the same issue with my Galaxy Nexus on JRO03C 4.1.1.
However I am noting a difference between bands used. If I set the phone to auto or '2.4Ghz only', network connection drops or becomes unreliable if signal strength drops below -60db, but if the phone is set to use '5Ghz only' speed and connection are maintained down to -90db. While I didn't perform direct testing, I did not experience any WiFi issues running 4.0.4.
Another observation, using an HTC One S running ICS 4.0.3 as a control sample, I note that with a WiFi signal app, both phones report similar signal strength in the app but what is displayed in the notification bar is significantly lower in Jelly Bean.
Router used : Cisco E4200v2
Apps used: ookka speed test, farproc WiFi Analyzer
However I am noting a difference between bands used. If I set the phone to auto or '2.4Ghz only', network connection drops or becomes unreliable if signal strength drops below -60db, but if the phone is set to use '5Ghz only' speed and connection are maintained down to -90db. While I didn't perform direct testing, I did not experience any WiFi issues running 4.0.4.
Another observation, using an HTC One S running ICS 4.0.3 as a control sample, I note that with a WiFi signal app, both phones report similar signal strength in the app but what is displayed in the notification bar is significantly lower in Jelly Bean.
Router used : Cisco E4200v2
Apps used: ookka speed test, farproc WiFi Analyzer
Description
Please put all the libs in attachment to Android "/system/lib64" like this:
“/system/lib64/”:
libOpenglSystemCommon.so
lib_renderControl_enc.so
libGLESv1_enc.so
libGLESv2_enc.so
“/system/lib64/egl”:
libEGL_emulation.so
libGLESv1_CM_emulation.so
libGLESv2_emulation.so
“/system/lib64/hw”:
There may be server ways to do it. But "adb push" is not OK. Because, after reboot, you may find all libs are gone.
If you're using linux, you can do it like this:
1. find the system.img in your SDK package.
It could be in "adt-bundle-linux.../sdk/system-images/android-L/default/x86_64/system.img"
2. mkdir temp
3. sudo mount -o loop system.img temp
4. Open "temp" folder, you may see "lib64". And then copy all the attachment files to the ".../temp/lib64/" folder.
5. Reboot the Android emulator.
6. you can umount temp now
sudo umount temp
If the system still cannot boot, please check the libs are in the right folder using adb shell command, like this:
“/system/lib64/”:
libOpenglSystemCommon.so
lib_renderControl_enc.so
libGLESv1_enc.so
libGLESv2_enc.so
“/system/lib64/egl”:
libEGL_emulation.so
libGLESv1_CM_emulation.so
libGLESv2_emulation.so
“/system/lib64/hw”: