I am trying to install the just released update from Verizon but I klept getting the message that the software failed. Do I need to unroot the device first?
You can keep root but make sure you have stock recovery otherwise the ota will fail.
Sent from my SGH-T999V using xda premium
shahkam said:
You can keep root but make sure you have stock recovery otherwise the ota will fail.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
If I am running an unrooted VRBLI5 will OTA work to update to VRBLK3? I keep trying to check for a software update and it says that there is no new software update available.
The OTA will not show up unless you downgrade to VRALHE. Since VRBLI5 was not an official version it won't offer you the OTA. You could also upgrade to VRBLK3 using one of the guides in the development section which would probably be a lot easier.
fromaap integrable
BigErnM said:
The OTA will not show up unless you downgrade to VRALHE. Since VRBLI5 was not an official version it won't offer you the OTA. You could also upgrade to VRBLK3 using one of the guides in the development section which would probably be a lot easier.
Click to expand...
Click to collapse
Thanks so much for the quick response and for the insight - very appreciated. I was bummed when my wife got the OTA and I didn't! I will probably just upgrade to the new stock rather than downgrade and upgrade.
My completely stock S3 is failing checking for updates saying that the update service is not available. It doesn't seem to ever have been able to successfully check for updates (last checked time is blank).
I noticed the following in adb logcat when I tried to check for updates:
Code:
E/SyncmlDMGenericExtHandlerConnector( 1913): Can not route to Mobile Admin Network 64.186.176.220
However, on the phone, I can ping that IP address just fine, at the same time as it's supposedly trying to check for updates:
Code:
[email protected]:/ $ ping 64.186.176.220
PING 64.186.176.220 (64.186.176.220) 56(84) bytes of data.
64 bytes from 64.186.176.220: icmp_seq=1 ttl=248 time=61.6 ms
64 bytes from 64.186.176.220: icmp_seq=2 ttl=248 time=58.4 ms
64 bytes from 64.186.176.220: icmp_seq=3 ttl=248 time=56.5 ms
This happens on wifi or mobile data. Any suggestions on how to make this thing check for updates?
Thanks.
---------- Post added at 12:04 PM ---------- Previous post was at 12:02 PM ----------
The rest of the error:
Code:
D/ConnectivityService( 650): requestRouteToHostAddress on down network (10) - dropped
I/ ( 1913): HTTP: http_socket_connect ret:-1 Errno:115
I/ ( 1913): connect wouldblock: EINPROGRESS
D/memalloc( 340): ion: Allocated buffer base:0x42f61000 size:630784 fd:62
D/memalloc( 1913): ion: Mapped buffer base:0x5e66b000 size:630784 offset:0 fd:77
D/KeyguardViewMediator( 650): setHidden false
I/Adreno200-EGLSUB( 340): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 340): <GetImageAttributes:1102>: RGBA_8888
D/KeyguardViewMediator( 650): setHidden false
I/ ( 1913): HTTP: SSL_CTX_load_verify_locations ret :0
I/ ( 1913): SSL_load_verify_locations failed
I/ ( 1913): HTTP: xaction 1574547464 ssl init error
I/ ( 1913): HTTP: status code 0
I/ ( 1913): [s]:[ERROR]:
I/ ( 1913): vendor/samsung/common/packages/apps/SyncMLSvc/native/syncmlcore/base/dm/src/tsldm_ses.cpp:Line:683 SesWaitForMsgSt:Error:9 happend while Recv Msg
I/ ( 1913):
I/ ( 1913): [s]:[ERROR]:
I/ ( 1913): vendor/samsung/common/packages/apps/SyncMLSvc/native/syncmlcore/base/dm/src/tsldm_ses.cpp:Line:788 Session Status :100663305
I/ ( 1913):
D/KeyguardViewMediator( 650): setHidden false
I/ ( 1913): shutdown Socket :50 return: 0
I/ ( 1913): HTTP: http_dispatch trans is already freed 5dd9b008
shahkam said:
You can keep root but make sure you have stock recovery otherwise the ota will fail.
As far as I know I have stock recovery. I did not flash a new ROM
Click to expand...
Click to collapse
I cant upgrade mine either, all I did was root
no unlocked bootloader, everything is stock
all stock apps are installed and running
Seems like lots of other Verizon customers are having the same problem. My phone is rooted, bootloader is unlocked and I have stock ROM
Please read forum rules before posting
Rule 15 tells you where to post if you are confused
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
And please search, this has been asked and answered several times
Related
I'm running Android Revolution XE 3.6.0 with the new wifi calling patch and I can't seem to get the Wifi Calling to work. I can open the app, it sees that I am on wifi, and it just sits at the "Wifi Calling: Enabling" "Please wait while connecting to T-Mobile Network". Any ideas?
Here is what I can see when doing logcat:
E/KINETO ( 4272): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 4272): onReceive Enter
I/Kineto::main( 4272): Kineto: SendAlarmEvent Enter
E/KINETO ( 4272): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 4272): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 4272): onReceive Exit
D/KIPCapp ( 4272): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 4272): Connecting... socket = 47, state = 0
D/KIPCapp ( 4272): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 4272): Connect failed 111
Click to expand...
Click to collapse
[/thread]
Wound up just doing a clean wipe and reinstall of the ROM since I ran into some other very weird issues after looking for why it was not working. Probably a bad install.
I don't see the wifi calling app after I flashed to 4.1.0. I also rooted, superCID, S-off my phone already. Is your Sensation superCID off too?
If you messed with your CID, WiFi calling won't be installed. Check out this thread on how to install it. Do NOT flash the file, you must follow the directions. You have to copy some files over, install an APK, and change the build.prop file.
http://forum.xda-developers.com/showthread.php?t=1193142
Sent from my HTC Flyer P512 using xda premium
Hi all,
I have been running a 2.3.x ROM for a few weeks (HyperSensation, an AOSP rom) very happily until a few days ago, I realized that it didn't connect to wifi anymore.
When I go to WiFi to turn it on, it think for a while and does revert back to unchecked. If I go look at the scan, it force closes after a while.
I don't believe this is ROM specific as I did wipes, Super-Wipes, installed the version of HS I had, a newer version, other ROMs, etc.
The same behavior happens every time I try to turn on Wifi.
I am running:
T-mobile HTC Sensation
10.56.9035.00P_10.14.9035.01_M
HBOOT-1.17.111
PYRAMID PVT SHIP S-OFF RL
eMMC-Boot
Clockwork Recovery v.5.0.2.0
Any idea? Diagnosis, tips, solutions?
Should I try to upgrade the hboot and radio, could it have gotten corrupted in some fashion?
Try installing the "first-time" kernel from the ARHD Rom thread.
What will that do? Reset my wifi hardware in some fashion? Should I flash just the kernel or the entire ROM?
I flashed the latest ARD and it didn't change a thing.
Through the Sense dialog, it tries to scan and then fails (Unable to scan for networks).
Logcat says things like:
Code:
E/WifiHW ( 309): Supplicant not running, cannot connect
V/WifiStateTracker( 309): Supplicant died unexpectedly
I/WifiHW ( 309): wifi_close_supplicant_connection
D/WifiStateTracker( 309): Reset connections and stopping DHCP
E/SettingsWifiLayer( 581): Unable to scan for networks
D/WifiService( 309): enable and start wifi due to updateWifiState
D/WifiService( 309): enable and start wifi due to updateWifiState
D/WifiStateTracker( 309): Reset connections and stopping DHCP
D/NetUtils( 309): ifc_get_info addr=0 !
D/NetUtils( 309): ifc_get_info addr=0 !
D/WifiStateTracker( 309): Disabling interface
D/WifiStateTracker( 309): Disabling interface
D/WifiService( 309): setWifiEnabledPersist false persist = true getCallingPid() = 309
D/WifiService( 309): setWifiEnabled =falsemAirplaneModeOverwridden =false
D/WifiStateTracker( 309): restart wifi at die
D/WifiService( 309): setWifiEnabledPersist true persist = true getCallingPid() = 309
D/WifiService( 309): setWifiEnabled =truemAirplaneModeOverwridden =false
D/WifiService( 309): setWifiEnabledBlocking:Disable Wifi
D/WifiStateTracker( 309): Reset connections and stopping DHCP
D/NetUtils( 309): ifc_get_info addr=0 !
I/NetSharing_NSReceiver( 581): customizedNS:true
D/NetSharing_NSReceiver( 581): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 581): wifi enabled change, state = false
...
D/WifiStateTracker( 309): Disabling interface
I/WifiHW ( 309): wifi_stop_supplicant enter
I/WifiHW ( 309): wifi_stop_supplicant end right 1
I/WifiHW ( 309): wifi_unload_driver enter
I/WifiHW ( 309): rmmod
I/WifiHW ( 309): check_driver_loaded
I/WifiHW ( 309): wifi_unload_driver end right 2
D/WifiService( 309): setWifiEnabledBlocking:Enable Wifi
I/WifiHW ( 309): wifi_load_driver enter
I/WifiHW ( 309): check_driver_loaded
I/WifiHW ( 309): insmod
I have the exact same problem after upgraded my ARHD 4.1.11 to 4.1.12. Everything worked well however I could not turn on the wifi
Seems, from a cursory search in these forums that this happens to quite a few people and I haven't found a definite solution. Seems the wifi adapter gets 'bricked' in some fashion and there is no way to revive it.
Can anyone suggest a way to diagnose, a more technical explanation of what's happening?
gnapoleon said:
What will that do? Reset my wifi hardware in some fashion? Should I flash just the kernel or the entire ROM?
Click to expand...
Click to collapse
i had a similar problem after upgrading to ARHD and my wifi wouldn't turn on at all. Then i tried the first_time kernel (i think from the same ARHD topic but i might be wrong). I just flashed the kernel and it fixed my wifi.
I agree,
flash the first time kernel then flash hypersensation 1.6 if u like cm7
check all md5 sums first
Did that once and it worked but then, after flashing another ROM which worked with Wi-fi for an hour or so, the same problem happened again.
Now I can't get it to work again, flashing ARHD 3.x. What is it supposed to be doing that other ROMs don't do and why doesn't it help (trying to understand why it didn't stick and why it doesn't help anymore).
I am at my wits end. I superwiped a few times, installed ARHD 3.x again, which got the wifi working. I then installed another rom (Virtuous Inquisition ICS), wifi worked for a few minutes then failed again.
Restore from ARHD 3.x backup and the wifi fails as well.
alireza_simkesh said:
Try installing the "first-time" kernel from the ARHD Rom thread.
Click to expand...
Click to collapse
Why are you telling him to flash a sense kernel for a aosp rom. It does not work and now he doesn't have wifi at all
gnapoleon said:
Should I try to upgrade the hboot and radio, could it have gotten corrupted in some fashion?
Click to expand...
Click to collapse
Just flash faux or showp kernel for AOSP/CM7 for the rom and your wifi should be back to normal. Wifi is a kenel related issue not rom
But why would a basic rom that works for everyone give me trouble with its built-in kernel?
I never flashed a kernel separately from a ROM in trying to get Wi-fi back. Why does a given rom/kernel combination that works for many not work for me?
I tried:
ARD 3.x
ARD 6.x
Hypersensation 1.5 & 1.6
Virtuous Inquisition
....
ARD 3.x is really the only one that gives me wifi for a short while before it fails again.
If I flash an ICS (not pure AOSP, but the ones with Sense removed), what should I expect to flash as a kernel?
At this point, I am ready to give up and ditch the sensation. I am thinking it might be a hardware issue. I have the latest firmware (HBoot 1.23) and have tried dozens of different roms. After Superwipes, and wipes, erasing the sdcard, re-partitioning and everything else I could think off, I can at best get wifi working on first boot for a few seconds.
GB or ICS, sense, senseless or real AOSP, it doesn't matter, I can never get it to work.
Does anyone have a last advice before I head to the Verizon store?
This is what my boot screen looks like. No ROM 2.3.x or ICS, sense, senseless or AOSP have a working wifi for me (T-mobile sensation):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some more logcat:
Code:
E/WifiStateMachine( 229): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
W/CommandListener( 119): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 119): Setting iface cfg
E/WifiStateMachine( 229): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
D/NetworkManagementService( 229): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 229): flags <[down]>
I/wpa_supplicant( 2785): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 2785): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 2785): WEXT: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2785): wlan0: Failed to initialize driver interface
blahbl4hblah said:
Why are you telling him to flash a sense kernel for a aosp rom. It does not work and now he doesn't have wifi at all
Click to expand...
Click to collapse
didn't notice he had aosp rom.
Just change ur rom to ARHD and flash first time kernel.
gnapoleon said:
At this point, I am ready to give up and ditch the sensation. I am thinking it might be a hardware issue. I have the latest firmware (HBoot 1.23) and have tried dozens of different roms. After Superwipes, and wipes, erasing the sdcard, re-partitioning and everything else I could think off, I can at best get wifi working on first boot for a few seconds.
GB or ICS, sense, senseless or real AOSP, it doesn't matter, I can never get it to work.
Does anyone have a last advice before I head to the Verizon store?
Click to expand...
Click to collapse
Did u try first-time kernel?
From what I understand, first time kernel is included in ARHD 3.x (GB) & 6.x (ICS) ROMs. Is that correct? If so, I have tried it as part of me trying to get Wifi working with those ROMs?
If it's not included in those ROMs, could you send me a link? Is it a kernel I just use once and then overwrite? Is it Sense 3.x only, does it apply to ICS Senseless ROMs or AOSP roms (GB or Tripp)?
Thanks for your help,
Erik
From what I could gather, at this point, my wifi is busted. I restored the tmobile RUU and it still exhibits that behavior. Dead sensation. Hello Gnex on Verizon.
cam's working now working now
thanks to cute_prince and liroka
give all the credits to them
here the download link : http://www.mediafire.com/?i7skgxn34s4is58
heres a logcat
heres a logcat of what happens when camera app is loaded :
Code:
I/ActivityManager( 169): START {act=android.intent.action.MAIN cat=[android.int
ent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera} from pid 3
27
I/ActivityManager( 169): Start proc com.android.camera for activity com.android
.camera/.Camera: pid=1078 uid=10032 gids={1006, 1015}
D/OpenGLRenderer( 327): Flushing caches (mode 1)
D/dalvikvm( 169): GC_EXPLICIT freed 2006K, 56% free 5011K/11207K, paused 5ms+13
ms
V/CameraHolder( 1078): open camera 0
E/CameraService( 107): Camera HAL module not loaded
E/CameraHolder( 1078): fail to connect Camera
E/CameraHolder( 1078): java.lang.RuntimeException: Fail to connect to camera ser
vice
E/CameraHolder( 1078): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 1078): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 1078): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 1078): at com.android.camera.CameraHolder.open(CameraHolder.jav
a:131)
E/CameraHolder( 1078): at com.android.camera.Util.openCamera(Util.java:321)
E/CameraHolder( 1078): at com.android.camera.Camera$4.run(Camera.java:1251)
E/CameraHolder( 1078): at java.lang.Thread.run(Thread.java:856)
I/Process ( 169): Sending signal. PID: 1078 SIG: 3
I/dalvikvm( 1078): threadid=3: reacting to signal 3
I/dalvikvm( 1078): Wrote stack traces to '/data/anr/traces.txt'
D/OpenGLRenderer( 327): Flushing caches (mode 0)
D/libEGL ( 1078): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1078): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 1078): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 1078): loaded /system/lib/egl/libGLESv2_adreno200.so
D/OpenGLRenderer( 1078): Enabling debug mode 0
V/camera ( 1078): surfaceChanged. w=320. h=427
I/ActivityManager( 169): Displayed com.android.camera/.Camera: +1s59ms
D/OpenGLRenderer( 327): Flushing caches (mode 1)
i think the problem is here : E/CameraService( 107): Camera HAL module not loaded
hope it helps
good news
camera is on the verge to get working plz give me some time
this was the life saver : http://forum.xda-developers.com/showthread.php?t=1427030
ayushrox said:
camera is on the verge to get working plz give me some time
this was the life saver : http://forum.xda-developers.com/showthread.php?t=1427030
Click to expand...
Click to collapse
Define "On the verge of working." I don't exactly want to end in a bootloop in the middle of the class.
on the verge means
AIndoria said:
Define "On the verge of working."
Click to expand...
Click to collapse
on the verge means - to get very near
well it seems that a camera worked but really bad :crying:
only preview app like night vision that too crashed after about 10 sec :crying:
when tried to fix it :silly: i messed with the whole boot.img and now its bootlooping :crying: :crying: :crying:
if i again get preview worked i'll upload it
i seriously need some dev help
i seriously need some dev help
ayushrox said:
i seriously need some dev help
Click to expand...
Click to collapse
the libs are for nexas 1, but the source can be added to our cm9 device tree and compiled, adjusted for screen size............well thats the plan anyway.......compiling now with the new camera source.......hopefully will work.....
thanks
LiVeRpOoL-FaN said:
the libs are for nexas 1, but the source can be added to our cm9 device tree and compiled, adjusted for screen size............well thats the plan anyway.......compiling now with the new camera source.......hopefully will work.....
Click to expand...
Click to collapse
thanks
hey did you try the link there ?
@ayushrox
Hey you can also add
https://www.codeaurora.org/gitweb/q...erry_rb3.4;hb=refs/heads/ics_strawberry_rb3.4
derefas posted this link in 4pda.. He told that this might help in fixing the camera..
This one looks interesting, worth studying a bit.
Will have a look at it when I got some free, But first must fix graphics problems.
Sent from my GT-P5110 using xda app-developers app
hal passed
hey 2 updates
good one- cute prince got past hal error
bad one - cam still not workin
result - maybe workin cam in few days/weeks
any one try this
hey i have made a some changes in source
plz some one compile it with ur rom and see if gets past the HAL
link (my github): https://github.com/ayushrox/ics-cam-HAL
LiVeRpOoL-FaN said:
the libs are for nexas 1, but the source can be added to our cm9 device tree and compiled, adjusted for screen size............well thats the plan anyway.......compiling now with the new camera source.......hopefully will work.....
Click to expand...
Click to collapse
Did u tried with plan u mentioned??
Sorry for asking question. Just wantd to keep this important thread active
Sent from my HTC Explorer A310e using xda app-developers app
this is active
the only prob we have no organized participation;
any way back to topic
camera HAL is now confirmed passed by cute_prince (donno how ? :silly: )
no new updates
Liroka made camera working))
He used htc golf files n succeeded:)
really ?
sbacham said:
Liroka made camera working))
He used htc golf files n succeeded:)
Click to expand...
Click to collapse
really where did he posted it ?
Link
http://forum.xda-develo
pers.com/showpost.php?p=3
0742590&postcount=558
that's really a gr8 news
that's really a gr8 news !
updates
liroka got cam working (yay :victory: )
see his post :
lirokoa said:
Got a piece of camera working
I can take picture, but can't record movie
To make it to work I backported camera driver from golf kernel (our sensor is supported by this kernel) and used all proprietary libs from golf.
Click to expand...
Click to collapse
Waiting for full camera support. Video and image capture both, for CM9. \m/
Hi All,
First of all apologies if i am in wrong forum.
My Objective ---
My objective is to access RIL layer of AOSP and try to access radio layer to know about Primary and Secondary PDP bearer creation by using "AT" command. Also i want to access ISIM authentication parameters of SIM card to handle AKA-v1 algo. I have Nexus-S and Galaxy S3 LTE phone but i am doing experiment on Nexus-S as AOSP is available. I am doing developing VoLTE application and embedding my application in AOSP/Custom ROM to access RIL/SIM access.
What i did---
I flashed AOSP on my Nexus phone and trying to use - OEM_HOOK_RAW to send some AT command to radio layer. I am able to send my "AT" command to RILC but RILC is treating it as error. Following is the error messages -
01-07 17:34:24.921 D/RILJ ( 541): [0096]> OEM_HOOK_STRINGS
01-07 17:34:24.924 V/RILJ ( 541): writing packet: 24 bytes
01-07 17:34:24.924 D/RILC ( 86): (processCommandBuffer, 379):: Command Request Code = 60
,, pStrings = AT24 D/RILC ( 86): (dispatchStrings, 470):: printBuf = (AT
)1-07 17:34:24.924 D/RILC ( 86): [0096]> OEM_HOOK_STRINGS (AT
01-07 17:34:24.924 D/RILC ( 86): (dispatchStrings, 478):: Command Request number = 60, Token = 96
01-07 17:34:24.924 D/RILC ( 86): [0096]< OEM_HOOK_STRINGS fails by E_REQUEST_NOT_SUPPORTED
I picked the Samsung RIL library from - /vendor/lib/libsec-ril.so and verified "requestOEMHookRaw" is available in Samsung RIL.
I am very much sure that i am doing some thing wrong. I am very thankful if some body send any reference document/post to help me.
Also i have Samsung Galaxy S3 LTE device based on Qualcom chipset and Qualcom exposed its GOBI based API to run "AT" command. Is it possible to use GOBI based API to access RIL etc. Has anybody worked on it?
Hi,
(First : I don't speak a lot of English and excuse me if I write some wrongs things on my posts )
I've got a big problem from some weeks, the Wi-Fi of my Xperia E3 doesn't work (he doesn't start and when he starts, he stops to find networks), sometime he works correctly and after sometime he stops with any reasons...
When I do
Code:
adb logcat
and I start Wi-FI by the notifications it's written :
Code:
D/WifiStateMachine( 1063): handleMessage: E msg.what=131083
D/WifiStateMachine( 1063): processMsg: InitialState
D/WifiHW ( 1063): Unable to unload driver module "wlan": No such file or directory
D/WifiService( 1063): setWifiEnabled: true pid=1178, uid=10026
E/WifiHW ( 1063): size = 6
E/WifiHW ( 1063): size = 29816
V/DexLibLoader( 5047): wrote 4968796 bytes to dex prog-a0af7cb08408279384aaa0ef36b024a6fdddb642.dex.jar
E/WifiStateMachine( 1063): Failed to load driver
D/WifiStateMachine( 1063): handleMessage: X
Thanks a lot for all the answers you will give me
toinedu27 said:
Hi,
(First : I don't speak a lot of English and excuse me if I write some wrongs things on my posts )
I've got a big problem from some weeks, the Wi-Fi of my Xperia E3 doesn't work (he doesn't start and when he starts, he stops to find networks), sometime he works correctly and after sometime he stops with any reasons...
When I do
Code:
adb logcat
and I start Wi-FI by the notifications it's written :
Code:
D/WifiStateMachine( 1063): handleMessage: E msg.what=131083
D/WifiStateMachine( 1063): processMsg: InitialState
D/WifiHW ( 1063): Unable to unload driver module "wlan": No such file or directory
D/WifiService( 1063): setWifiEnabled: true pid=1178, uid=10026
E/WifiHW ( 1063): size = 6
E/WifiHW ( 1063): size = 29816
V/DexLibLoader( 5047): wrote 4968796 bytes to dex prog-a0af7cb08408279384aaa0ef36b024a6fdddb642.dex.jar
E/WifiStateMachine( 1063): Failed to load driver
D/WifiStateMachine( 1063): handleMessage: X
Thanks a lot for all the answers you will give me
Click to expand...
Click to collapse
I have the same problem,
which rom are you using?
berni987654321 said:
I have the same problem,
which rom are you using?
Click to expand...
Click to collapse
Hey,
Before I was using the normal ROM, for the Xperia E3, and now I use this ROM : http://forum.xda-developers.com/xperia-e3/development/rom-t3067374
I'm still with this problem, but less than before (with the old ROM).
toinedu27 said:
Hey,
Before I was using the normal ROM, for the Xperia E3, and now I use this ROM : http://forum.xda-developers.com/xperia-e3/development/rom-t3067374
I'm still with this problem, but less than before (with the old ROM).
Click to expand...
Click to collapse
It seems to be a hardware issue even if the logcat(got the same) tells us it's a driver related thing.
Tried a lot of stuff and didn't give up yet, but if it is realy a hardware thing, I don't think I'll find a solution.
For me it started with not finding networks, then stoping to let me enable wifi from time to time and now
it's impossible for me to enable it.
berni987654321 said:
It seems to be a hardware issue even if the logcat(got the same) tells us it's a driver related thing.
Tried a lot of stuff and didn't give up yet, but if it is realy a hardware thing, I don't think I'll find a solution.
For me it started with not finding networks, then stoping to let me enable wifi from time to time and now
it's impossible for me to enable it.
Click to expand...
Click to collapse
Hey,
Do you try to enable the wi-fi (in the settings) and shutdown the phone, that work for me, when that don't work I enable the Wi-Fi, I open "Xposed" and I do a normal reboot of the phone, if the Wi-Fi is already enabled I just do a soft reboot.
Same if I resolve this problem, I've got a lot of others problem (I changed my display and I think I do some wrong things). I buy the Xperia E5 and I will receive him on the next week.
Try "wifi connection fixer" from Google play give it a try