Database Info

Wifi Calling issues

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

Lost Wi-fi, could be hardware, HBOOT, radio?

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.

[development]cyanogen mod camera

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/

[Q] Google Play updates, and all downloads type won't finish even after Factory Reset

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.

Random rebooting issues after the Android 10 update [Logcat inside]

Hello everyone, I hope that someone here can help me understand what is the culprit behind this issue, I know it's related to Wifi since the random reboots almost never happen when Wifi is turned of (regardless if it's actually connected to a network or not)
Logcat:
Error: AndroidRuntime
*** FATAL EXCEPTION IN SYSTEM PROCESS: ClientModeImpl
java.lang.IllegalArgumentException: ssid bytes size out of range: 64
at com.android.server.wifi.util.NativeUtil.decodeSsid(NativeUtil.java:278)
at com.android.server.wifi.WifiScoreCard.computeHashLong(WifiScoreCard.java:588)
at com.android.server.wifi.WifiScoreCard.access$100(WifiScoreCard.java:63)
at com.android.server.wifi.WifiScoreCard$PerBssid.<init>(WifiScoreCard.java:380)
at com.android.server.wifi.WifiScoreCard.lookupBssid(WifiScoreCard.java:530)
at com.android.server.wifi.WifiCandidates.add(WifiCandidates.java:374)
at com.android.server.wifi.WifiCandidates.add(WifiCandidates.java:393)
at com.android.server.wifi.WifiNetworkSelector.lambda$selectNetwork$0$WifiNetworkSelector(WifiNetworkSelector.java:911)
at com.android.server.wifi.-$$Lambda$WifiNetworkSelector$Z7htivbXF5AzGeTh0ZNbtUXC_0Q.onConnectable(Unknown Source:15)
at com.android.server.wifi.SavedNetworkEvaluator.evaluateNetworks(SavedNetworkEvaluator.java:279)
at com.android.server.wifi.WifiNetworkSelector.selectNetwork(WifiNetworkSelector.java:900)
at com.android.server.wifi.WifiConnectivityManager.handleScanResults(WifiConnectivityManager.java:342)
at com.android.server.wifi.WifiConnectivityManager.access$900(WifiConnectivityManager.java:73)
at com.android.server.wifi.WifiConnectivityManager$AllSingleScanListener.onResults(WifiConnectivityManager.java:425)
at android.net.wifi.WifiScanner$ServiceHandler.handleMessage(WifiScanner.java:1429)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:67)
PID: 28683
TID: 28862
The following error message says:
FATAL EXCEPTION: main
Process: com.google.android.gms.persistent, PID: 30417
DeadSystemException: The system died; earlier logs will point to the root cause
This is consistent and the same exact error I posted shows up everytime the system crashes/reboots.
Hope someone can help me out, thanks

Have you cleared your cache?

tech_head said:
Have you cleared your cache?
Click to expand...
Click to collapse
Yes I tried clearing cache using TWRP, the issue still persists.