Related
I think everyone now knows about the wifi country code problem in ICS roms ( its a row in setting provider database that set every time we try to enable wifi and it read the value from sim card. if its not US or EU or... you can not use some features like wifi, face unlock,.... )
I have done many searches please dont say its already done :-" I know there is a simple script which runs with script manager every time the wifi status changed and it works fine for aosp roms but the problem is with sense 3.5 ICS. in aosp roms the phone says wifi is turning on and after a sec script manager does the work and your good to go but in sense rom it says turning on and the phone hangs so script manager does not work for that! i found another solution for this problem here: http://forum.xda-developers.com/showthread.php?t=1372074 but its for nexus s i tried the file in that thread also other firmwares from sensation sense 3.5 gb roms ... and i can not find an answer ( noob )
can some one plese help and make a similar solution for sensation
this is what they said in that thread:
avostrik said:
Update:
created update.zip file with Broadcom firmware 4.218.248.18.
This update.zip will run only on "crespo", i.e. Nexus S.
Should work for non-rooted device via boot recovery, if someone could test and provide results, it would be great.
Disclaimer: use this update on your own risk.
------
I had connection problems with 802.11n router in WPA2-PSK configuration. According to log authentication timeout occurred on every try to connect.
Here is snippet of typical error (used 'adb shell su -c "wpa_cli log_level 0"' to enable verbose wi-fi logging):
Code:
D/wpa_supplicant(11118): RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
D/wpa_supplicant(11118): Wireless event: cmd=0x8c02 len=33
D/wpa_supplicant(11118): WEXT: Custom wireless event: 'Conn ConfigMismatch 01 00'
D/wpa_supplicant(11118): wpa_driver_wext_driver_cmd SCAN-ACTIVE len = 4096
D/wpa_supplicant(11118): wpa_driver_wext_driver_cmd SCAN-ACTIVE len = 0, 11
D/wpa_supplicant(11118): Ongoing scan action - reject new request
D/wpa_supplicant(11118): wpa_driver_wext_driver_cmd SCAN-PASSIVE len = 4096
D/wpa_supplicant(11118): wpa_driver_wext_driver_cmd SCAN-PASSIVE len = 0, 12
I/wpa_supplicant(11118): wlan0: Authentication with <AP MAC ADDRESS> timed out.
On my Nexus S it was solved by rolling back wi-fi firmware to version used in Gingerbread.
Wi-Fi firmware version that have problems (integrated into ICS) 4.218.248.20, 4.218.248.23.
fw_bcm4329.bin file can be obtained from AOSP sources:
$git clone https://android.googlesource.com/platform/hardware/broadcom/wlan
$cd wlan
$git checkout android-2.3.7_r1
Firmware ver. 4.218.248.18 file located at ./bcm4329/firmware/fw_bcm4329.bin
It is needed to have rooted device to change firmware. Steps:
Turn OFF wi-fi on the device.
>adb push fw_bcm4329.bin /sdcard/
>adb shell
$su
#mount -o,remount rw /system
#cp /sdcard/fw_bcm4329.bin /system/vendor/firmware/
#mount -o,remount ro /system
enable wi-fi.
----
Cyanogen 9 (ICS) Alpha 18 on Nexus S
Radio: I9020XXKF1
Click to expand...
Click to collapse
thanks in advance
I used script and its working on sense 3.5... just do the following..
1- Turn wifi off
2- set script to run on boot + SU
and reboot
everytime u reboot, wait to see that scriptmanager got permissions (means it ran) then turn on Wifi,, it works..
I ll give more info and post file later i hope. goodl uck
Thank you fearkillerr it works even for sense roms!
welcome bro
fearkillerr said:
I used script and its working on sense 3.5... just do the following..
1- Turn wifi off
2- set script to run on boot + SU
and reboot
everytime u reboot, wait to see that scriptmanager got permissions (means it ran) then turn on Wifi,, it works..
I ll give more info and post file later i hope. goodl uck
Click to expand...
Click to collapse
Would you please post the link to the file?
Thanks.
For the guys that this script worked for does wifi calling now work?
wifi problem
omar302 said:
Would you please post the link to the file?
Thanks.
Click to expand...
Click to collapse
here is the script
http://forum.xda-developers.com/showthread.php?t=1403801
haririan said:
here is the script
http://forum.xda-developers.com/showthread.php?t=1403801
Click to expand...
Click to collapse
Thanks, but now there is a full guide here.
omar302 said:
Thanks, but now there is a full guide here.
Click to expand...
Click to collapse
THANK YOU
IT WORKED 90% I DONT NEED TO RERUN THE SCRIPT
another method for doing this but it is so much easier
Sent from my HTC Sensation Z710e using xda premium
Final Fix
A permanent fix to this problem is to fake the provider mcc, to do so,
1. your phone has to be rooted
2. install SQLite Editor from aptoide
3. open SQLite Editor
4. goto /data/data/com.android.providors.telephony/databases
5. select carriers
6. find your gsm providor
7. change the mcc value of your provider to 310 which is US
8. close, and check if it works
whenever the phone get the mcc (after reboot, airplane mode, network disconnect) the value of mcc=310 and the wifi_country_code = us
Hope it works for everybody
Regards,
Ali
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.
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
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?
Hello everyone,
I'm facing a quite strange and annoying issue on a TF700T.
No matter which ROM I'm running with, Google Play tells me updates need to be done, which is normal. When I start the updates, the downloads pause at 4% for most of them, and will never end, even after 4 days of activity.
A tablet on which you cannot download content to, or install apps is not very usefull.
The problem is the same with other download types (if I browse on the navigator, to download a ROM.zip, download starts and stops at 4%)
A friend gave me this tablet with Cromi-X insttaled on it. I first thought it was a ROM issue, so I flashed CM11 stable version, just to see.
Problem is the same.
I tried with different google accounts, I cleared Google Play cache services.
No effect.
I also flashed the ASUS original firmware using the SD card mthod, and problem is still there.
I'm short on ideas now, I've looked in XDA forum, but never found a thread with similar issues.
Tablet is currently running Android 4.1.1 WW10.4.4.25-20121228 A03 and unlocked
Thank you very much for your help or advices,
Nicolas
Hi again,
I have made progress on this strange issue.
I finally managed to get google play and downloads to work, but I have to use a vpn client so it can work.
I tried VPN Hideninja.
And, I have the issue no matter which rom/ android version I use.
So, it's a workaround, but at least it allows the tablet to be "usable".
Does someone has any ideas where the problem could come from? (bad kernel version?...)
Or, maybe someone knows a tool to check Android configuration issue, network configuration (I've searched but didnn't find something yet, but I keep trying )
Thank you for your help
Nicolas
Hi,
I installed cromi-X on the tablet and combi-kk as rom2Sd. Bith rom start, but I still have the issues with the playstore.
Does anyone know a tool to perform a hardware check?
If I want to completely clean the tablet, what would you advise ? Right now I'm trying to figure out if the problem is hardware or software.
Thank you for your help
Nicolas
nvuillem said:
Hi,
I installed cromi-X on the tablet and combi-kk as rom2Sd. Bith rom start, but I still have the issues with the playstore.
Does anyone know a tool to perform a hardware check?
If I want to completely clean the tablet, what would you advise ? Right now I'm trying to figure out if the problem is hardware or software.
Thank you for your help
Nicolas
Click to expand...
Click to collapse
Search how to do a logcat over adb and post the resulting text file. Do it after you attempted to download something.
sbdags said:
Search how to do a logcat over adb and post the resulting text file. Do it after you attempted to download something.
Click to expand...
Click to collapse
Hi Sdbags, first of all thank you for your interest.
I've made 3 logcatfiles:
#1 on the rom2sd crombi-kk before downloading. logcatkkStartUp.txt
#2 after stopping downloading as it was frozen. logcatkkDLFails.txt
#3 same as #2 but running on cromi-X on the internal memory of the pad logcatX.txt
I believe this is not looking good:
W/NetworkManagementSocketTagger( 1280): untagSocket(94) failed with errno -22
I/qtaguid ( 1280): Failed write_ctrl(u 56) res=-1 errno=22
I/qtaguid ( 1280): Untagging socket 56 failed errno=-22
Thanks again for your help,
Thank you
Nicolas
nvuillem said:
Hi Sdbags, first of all thank you for your interest.
I've made 3 logcatfiles:
#1 on the rom2sd crombi-kk before downloading. logcatkkStartUp.txt
#2 after stopping downloading as it was frozen. logcatkkDLFails.txt
#3 same as #2 but running on cromi-X on the internal memory of the pad logcatX.txt
I believe this is not looking good:
W/NetworkManagementSocketTagger( 1280): untagSocket(94) failed with errno -22
I/qtaguid ( 1280): Failed write_ctrl(u 56) res=-1 errno=22
I/qtaguid ( 1280): Untagging socket 56 failed errno=-22
Thanks again for your help,
Thank you
Nicolas
Click to expand...
Click to collapse
Well there are some hints in there. As this happens on every rom I'm going to stick my neck out and say it's nothing to do with the ROM you in stall
The below appears to be trying to update Google Street View.
Code:
I/GoogleHttpClient( 832): Falling back to old http client 0 java.lang.NoSuchMethodException: <init> [class android.content.Context, class java.lang.String, boolean]
D/SurfaceControl( 622): Excessive delay in blankDisplay() while turning screen off: 107ms
W/ActivityThread( 832): ClassLoader.loadClass: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());
I/auditd ( 9847): Starting up
E/auditd ( 9847): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9847): Exiting
I/auditd ( 9850): Starting up
E/auditd ( 9850): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9850): Exiting
I/auditd ( 9853): Starting up
E/auditd ( 9853): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9853): Exiting
I/auditd ( 9858): Starting up
E/auditd ( 9858): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9858): Exiting
I/auditd ( 9863): Starting up
E/auditd ( 9863): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9863): Exiting
D/Finsky ( 2075): [1] DownloadQueueImpl.notifyProgress: com.google.android.street: onProgress 185420/264451 Status: 192.
D/MarketUpdateReceiver( 9689): market is downloading (0%): com.google.android.street
I/DownloadManager( 1842): Download 22 starting
D/MarketUpdateReceiver( 9689): market is downloading (0%): com.google.android.street
I/auditd ( 9871): Starting up
E/auditd ( 9871): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9871): Exiting
I/auditd ( 9876): Starting up
E/auditd ( 9876): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9876): Exiting
I/auditd ( 9879): Starting up
E/auditd ( 9879): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9879): Exiting
I/auditd ( 9882): Starting up
E/auditd ( 9882): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 9882): Exiting
D/MarketUpdateReceiver( 9689): market is downloading (0%): com.google.android.street
W/DownloadManager( 1842): Aborting request for download 22: Failed reading response: java.net.SocketTimeoutException
I/DownloadManager( 1842): Download 22 finished with status WAITING_TO_RETRY
auditd is the Selinux logging facility... Protocol not supported means Linux kernel is missing the SELinux protocol...
So possibly you are on an older bootloader that doesn't support the right kernel ....
What bootloader and version of TWRP are you on exactly?
AH WE HAVE A WINNER
Tablet is currently running Android 4.1.1 WW10.4.4.25-20121228 A03 and unlocked
You need to update your bootloader and TWRP. Flash my update package from the CROM-X first post and then follow the instructions to move to a later TWRP if you want to try a CM11 base
Hi Sdbags,
upon startup, bootloader version shows "WW_epad-10.6.1.14.4-20130329" A03, and TWRP is v2.6.3-that3.
I can atach pictures if you want.
Ciould it be that a part of the tablet has the right bootloader version, and another part d not have that correct version?
Thank you for your help
Nicolas
nvuillem said:
Hi Sdbags,
upon startup, bootloader version shows "WW_epad-10.6.1.14.4-20130329" A03, and TWRP is v2.6.3-that3.
I can atach pictures if you want.
Ciould it be that a part of the tablet has the right bootloader version, and another part d not have that correct version?
Thank you for your help
Nicolas
Click to expand...
Click to collapse
Do me a favour and flash my package and then upgrade to TWRP 2.6.3-that3. There is flashable version of that in my CROMBi-kk thread. Then we know you are on the latest bootloader and recovery.
Also you seem to be using bluetooth at the same time. That doesn't work well on these devices. Turn off bluetooth as well and let's get the wifi working.
51189868998
sbdags said:
Do me a favour and flash my package and then upgrade to TWRP 2.6.3-that3. There is flashable version of that in my CROMBi-kk thread. Then we know you are on the latest bootloader and recovery.
Also you seem to be using bluetooth at the same time. That doesn't work well on these devices. Turn off bluetooth as well and let's get the wifi working.
Click to expand...
Click to collapse
Hi,
So I went to recovery, wiped everything except external SD. transfered using adb :
cm-4.4-20140309-CROMBikk4.4.2-tf700t_Signed.zip
install it, restart to crombikk (normal installation, not in rom2SD)
restarted to Android, and made a logcat.
Rebooted to recovery and flashed twrp-2.6.3-that3_Signed 1.zip
Rebooted to android and made a logcat
Finally, rebooted to recovery, installed crombi_kkgapps_20140312_Signed.zip and reboot to Android system, connected a google account and tried to download an app from Google. Bluetooth is off (I never switched it on in my previous logcats.)
I then started the playstore application, and Android Terminal Emulator installed correctly.
I then wanted to install a Google product, Chrome Browser in the logcat attached. Download starts and freezes at 9% for 2 minutes then increases to 24% and freezes again. The download is still pending.
I'll post the logcat of the tablet when download stops by itself or it completes. (let's hope it does but it is hanging for 10 minutes now)
Try clearing data and cache on the Play Store and Google Play Services and reboot.
nvuillem said:
Hi,
So I went to recovery, wiped everything except external SD. transfered using adb :
cm-4.4-20140309-CROMBikk4.4.2-tf700t_Signed.zip
install it, restart to crombikk (normal installation, not in rom2SD)
restarted to Android, and made a logcat.
Rebooted to recovery and flashed twrp-2.6.3-that3_Signed 1.zip
Rebooted to android and made a logcat
Finally, rebooted to recovery, installed crombi_kkgapps_20140312_Signed.zip and reboot to Android system, connected a google account and tried to download an app from Google. Bluetooth is off (I never switched it on in my previous logcats.)
I then started the playstore application, and Android Terminal Emulator installed correctly.
I then wanted to install a Google product, Chrome Browser in the logcat attached. Download starts and freezes at 9% for 2 minutes then increases to 24% and freezes again. The download is still pending.
I'll post the logcat of the tablet when download stops by itself or it completes. (let's hope it does but it is hanging for 10 minutes now)
Click to expand...
Click to collapse
Are you sure it's not your router?
sbdags said:
Are you sure it's not your router?
Click to expand...
Click to collapse
Hi,
I tried to download from 3 different locations, with 3 different ISP and modems, and the problem is the same.
I also tried to Clear cache and data of Google services and PlayStore. I still have the problem.
Yesterday, when I flashed everything to reinstall the Rom and the recovery on proper basis, I noticed that some directories are not wiped.
Maybe some files are missing?
Is there any way to restore those directory? (maybe doing a wipe data from the bootloader, but I read at many places that it is not advised...
I also tried to find an application or a thread to test the hardware of the tablet without any success
Thank you for your help
Nicolas
nvuillem said:
Hi,
I tried to download from 3 different locations, with 3 different ISP and modems, and the problem is the same.
I also tried to Clear cache and data of Google services and PlayStore. I still have the problem.
Yesterday, when I flashed everything to reinstall the Rom and the recovery on proper basis, I noticed that some directories are not wiped.
Maybe some files are missing?
Is there any way to restore those directory? (maybe doing a wipe data from the bootloader, but I read at many places that it is not advised...
I also tried to find an application or a thread to test the hardware of the tablet without any success
Thank you for your help
Nicolas
Click to expand...
Click to collapse
You could try a full internal sd card format from inside twrp - warning it can take up to 2 hours to complete. Make sure you have everything you want to keep and rom.zips on external sd as well.
sbdags said:
You could try a full internal sd card format from inside twrp - warning it can take up to 2 hours to complete. Make sure you have everything you want to keep and rom.zips on external sd as well.
Click to expand...
Click to collapse
Hi,
I did the full wipe from the factory (took 90 minutes )
I reinstalled the rom, and I stil have the problem (erro 495 most of the time)
I then downloaded and installed a VPN client and it works. ( I attached the logcat.txt)
There is still something I can't figure out, as it works using a VPN, the issue is probably not related to hardware, but software, and it is not related to the Rom or recovery.
Do you know if Google checks something like device ID when apps are dowloaded from the store?
Thanks
Nicolas
nvuillem said:
Hi,
I did the full wipe from the factory (took 90 minutes )
I reinstalled the rom, and I stil have the problem (erro 495 most of the time)
I then downloaded and installed a VPN client and it works. ( I attached the logcat.txt)
There is still something I can't figure out, as it works using a VPN, the issue is probably not related to hardware, but software, and it is not related to the Rom or recovery.
Do you know if Google checks something like device ID when apps are dowloaded from the store?
Thanks
Nicolas
Click to expand...
Click to collapse
If it works on a VPN then it is more likely related to your country and / or ISP and Google servers.