[Q] [LOG] WiFi disconnect caught in log - Xoom General

I am running the Tiamat 1.1.5 kernel with the included WiFi drivers. However, it seems that at random my WiFi starts to disconnect. This behavior is not exhibited on my work's WiFi.
I ran dmesg and posted the output here to see if someone with more expertise than me could look it over.
Any ideas?
Code:
<4>[73245.510944] Restarting tasks ...
<6>[73245.548549] request_suspend_state: wakeup (3->0) at 11681922715135 (2011-03-16 00:09:19.591219000 UTC)
<4>[73245.552184] done.
<6>[73245.555053] suspend: exit suspend, ret = 0 (2011-03-16 00:09:19.597743000 UTC)
<6>[73245.557459] active wake lock main
<6>[73245.557807] active wake lock PowerManagerService
<6>[73245.558418] active wake lock ds2781-battery
<6>[73245.558757] active wake lock alarm, time left 454
<6>[73245.559369] active wake lock pwrkey, time left 1
<6>[73245.564819] suspend: abort suspend
<6>[73245.706436] qtouch_force_calibration: Forcing calibration
<6>[73245.736272] do_cmd_proc_msg: Self-calibration started.
<4>[73249.949667] mmc1: Starting deferred resume
<4>[73250.110962] mmc1: Deferred resume completed
<6>[73342.794986] binder: 27662:27663 refcount change on invalid ref 20
<6>[73342.843876] binder: 27662:27662 refcount change on invalid ref 20
<6>[73342.844016] binder: 27662:27662 refcount change on invalid ref 20
<3>[73342.844151] binder: transaction release 422754 bad handle 20
<4>[73800.295972] dhd_bus_rxctl: resumed on timeout
<4>[73800.297599] dhd_ioctl_entry: Event HANG send up
<4>[73800.298537] wl_iw_get_rssi: Fails -22
<4>[73805.295829] dhd_bus_rxctl: resumed on timeout
<4>[73805.296325] dhd_ioctl_entry: Event HANG send up
<4>[73809.861699] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 154
<4>[73809.863921] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 156
<4>[73810.166430] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 158
<4>[73810.167163] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 160
<4>[73810.295924] dhd_bus_rxctl: resumed on timeout
<4>[73810.296532] dhd_ioctl_entry: Event HANG send up
<4>[73812.297335] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 163
<4>[73813.753811] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 165
<4>[73813.755693] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 167
<4>[73815.295852] dhd_bus_rxctl: resumed on timeout
<4>[73815.296427] dhd_ioctl_entry: Event HANG send up
<4>[73820.295882] dhd_bus_rxctl: resumed on timeout
<4>[73820.296319] dhd_ioctl_entry: Event HANG send up
<4>[73820.369802] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 170
<4>[73820.370443] Return_dpc value is : -1
<4>[73820.370613] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 170
<4>[73823.366097] dhd_bus_rxctl: resumed on timeout
<4>[73823.367657] dhd_ioctl_entry: Event HANG send up
<4>[73828.365975] dhd_bus_rxctl: resumed on timeout
<4>[73828.367773] dhd_ioctl_entry: Event HANG send up
<4>[73830.367143] dhdsdio_readframes: got unlikely tx max 151 with tx_seq 174
<4>[73831.410569] dhdsdio_readframes: got unlikely tx max 152 with tx_seq 176
<4>[73831.411388] dhdsdio_readframes: got unlikely tx max 174 with tx_seq 176
<4>[73831.411985] dhdsdio_readframes: got unlikely tx max 175 with tx_seq 176
<4>[73831.419113] dhdsdio_readframes: got unlikely tx max 176 with tx_seq 178
<4>[73831.419828] Return_dpc value is : 0
<4>[73831.421579] dhdsdio_readframes: got unlikely tx max 176 with tx_seq 180
<4>[73831.538936] dhdsdio_readframes: got unlikely tx max 177 with tx_seq 182
<4>[73834.416210] dhd_bus_rxctl: resumed on timeout
<4>[73834.417837] dhd_ioctl_entry: Event HANG send up
<4>[73836.417316] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 185
<4>[73836.591004] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 187
<4>[73836.592985] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 189
<4>[73836.594556] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 191
<4>[73839.416171] dhd_bus_rxctl: resumed on timeout
<4>[73839.417757] dhd_ioctl_entry: Event HANG send up
<4>[73844.416125] dhd_bus_rxctl: resumed on timeout
<4>[73844.417725] dhd_ioctl_entry: Event HANG send up
<4>[73844.418363] Failed to get 'wsec'iovar
<4>[73846.490990] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 195
<4>[73846.492611] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 197
<4>[73848.877009] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 199
<4>[73848.879268] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 201
<4>[73848.880827] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 203
<4>[73849.486061] dhd_bus_rxctl: resumed on timeout
<4>[73849.487092] dhd_ioctl_entry: Event HANG send up
<4>[73849.487257] wl_iw_set_wpaauth: wsec_restrict -22
<4>[73849.590765] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 205
<4>[73849.592255] Return_dpc value is : -1
<4>[73849.593012] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 205
<4>[73850.307222] dhdsdio_readframes: got unlikely tx max 180 with tx_seq 207
<4>[73851.552147] dhdsdio_readframes: got unlikely tx max 181 with tx_seq 209
<4>[73851.552985] dhdsdio_readframes: got unlikely tx max 181 with tx_seq 209
<4>[73851.553726] dhdsdio_readframes: got unlikely tx max 181 with tx_seq 209
<4>[73851.556068] dhdsdio_readframes: got unlikely tx max 182 with tx_seq 211
<4>[73851.564076] dhdsdio_readframes: got unlikely tx max 212 with tx_seq 213
<4>[73852.746825] wifi_set_power = 0
<4>[73853.154081] wifi_set_carddetect = 0
<6>[73853.155063] mmc0: card 0001 removed
<4>[73853.205364] wifi_set_power = 1
<4>[73853.606420] wifi_set_carddetect = 1
<4>[73853.607993]
<4>[73853.607995] Dongle Host Driver, version 4.218.248.23
<4>[73853.663002] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[73853.663091] mmc0: new high speed SDIO card at address 0001
<6>[73853.687060] binder: 136:287 transaction failed 29189, size 360-0
<4>[73853.910926] wlan0: Broadcom Dongle Host Driver mac=40:fc:89:17:46:4e
<4>[73855.060899] wl_iw_set_country: set country for US as US rev 69 is OK
<4>[73856.347909] STA connect received 1
<7>[73864.265885] wlan0: no IPv6 routers present

Related

Increase phone hear volume

Dear everyone
The voice of my phone is not loud enough, any expert can tell me how to amend the registry in order to increase the phone volume when I am talking with others?
Thanks in advance
Would also love to know if this is possible....
Incoming voice calls is more often than not too soft on my HTC TyTN, especially in a noisy room, despite the sound being maxed out.
This Might Help
goto
WM5_Tweaks_Other
Miscellaneous
Improve Sound Quality of Speaker Phone...
You might have observed that when you turn on speaker while during a call, the other person has complained of too much disturbance on the line and can hear more of static then your voice. Here's a fix to improve mic sensitivity:
HKLM\Software\HTC\AUDIOGAIN(x)\RECEIVE_UPLINK_VOLUME = CC (DWORD hexadecimal)
HKLM\Software\HTC\AUDIOGAIN(x)\EARPHONE_UPLINK_VOLUME = CC (DWORD hexadecimal)
where (x) = none, 0, 1, 2
838 pro/Hermes does not have that registry. I am using 1.35 rom
WineCape said:
Would also love to know if this is possible....
Incoming voice calls is more often than not too soft on my HTC TyTN, especially in a noisy room, despite the sound being maxed out.
Click to expand...
Click to collapse
I would definitely also like to know if this is possible, because I have the exact same complaint... Even in slightly noisy environments like a coffee shop, the earpiece volume isn't loud enough.
peace
Found this... although I admit, I don't know how to access the registry, otherwise I'd try this right away...
http://wiki.xda-developers.com/index.php?pagename=Hermes_Registry
Fix low volume issue
The volume issue has 2 fixes, 1 permanent and 1 temporary.
If you disable the startup animation (see below) it permanently fixes the volume problem.
If you like the animation you can leave it, but you have to put your phone in sleep mode then bring it out of sleep mode after every reboot.
\HKEY_CURRENT_USER\ControlPanel\Volume
add: DWord value name = volume
value data = 4294967295then press power (sleep) wait 10 sec and press power again.
Disable/change the startup animation or sound
HKLM\SOFTWARE\HTC\StartupAnimationEnabled - change from 1 to 0 to turn everything off and permanently fix the volume issue.
You can also customize the animated boot up by deleting or changing 2 keys. (Doing this does not fix the volume issue)
Delete the WAVFile Key to remove the sound only.
Delete the GIFFile Key to remove the animation only.
Put your own .GIF file or .WAV file on the phone and rewrite the 2 keys (WAVFile GIFFile) to the new file location. i.e. \My Documents\Files\CustomAnimation.gif

Ringer Volume

I can't hear the ringer on my xv6800 is there a hack, program, or magic to increase the ringer? Yes I have done a search but have not found any help. Thanks
Sounds like a hardware problem or you haven't found the right volume slider. The Mogul is LOUD when it rings on high.
Ringer vol
Can someone tell me what the script string is for HKEY/cu/controlpanel/sounds/ringtone0/script what is the string? thanks
You can try this:
HKEY_CURRENT_USER/ControlPanel/Phone/"Vol"
Original value is 65535. Enter value of 95000 and that will increase the volume. Try it out...
xweaponx said:
You can try this:
HKEY_CURRENT_USER/ControlPanel/Phone/"Vol"
Original value is 65535. Enter value of 95000 and that will increase the volume. Try it out...
Click to expand...
Click to collapse
I tried this says acces is denied
Similar issue...
My ringer volume suddenly went to almost nothing... I could barely hear the ringer when I held my 6800 a foot away from my ear. I tried your suggestion but it failed to fix it, but I poked around and found
HKEY_CURRENT_USER/ControlPanel/SoundCategories/Ring and opened "InitVol". It was set to (DEC) of 4294967295 (hex) FFFFFFFF
I tried changing it to the (DEC) 95000 (hex) 17318 and saved, reset and tested it again. This time it worked like a charm and was even a bit louder than it had beem before!

waveOutSetVolume() on Raphael CDMA

I'm messing with an app for my own personal use that is dead simple with 3 buttons that will set the volume to high (when i'm out of the office), low (when i'm in the office), and off (when i'm in a meeting).
I've been able to successfully configure the ringer volume by dumping the registry in between changing the volume and the AudioUpdateFromRegistry() call.
But, when I use waveOutSetVolume() to set the "system" volume, it ends up being 0 no matter what value I supply (I've tried both hex 0xFFFF and decimal 65535 values). The call returns no error.
Anybody have experience with this call? If it makes any difference, I'm using C# w/ VS 2008 (.NET CF 3.5).

[Q] viber, nimbuzz issue on NAND android

hello all
i have a strange issue on my device, which is T-Mobile HD2.
Problem Details:
if i used Viber or Nimbuz to call someone after that i can not use my phone (GSM Service i mean).
for example, if i called a friend on Viber, and after hanging up with him, if i recieved a normal phone call andi answered it, the phone will freez and after a while a messege will appear (Activity Phone in process com.android.phone is not responding) and two options "Close, Wait" if i selected wait nothing will happen, if i selected close the dialar will close and i will lose the signal and it will come again after a while, but still i can not use my device as a phone, i have to reboot my phone to be able to use it again.
My Radio version is 2.15.50.14
Issue happened with CLK and MAGLDR on every android build i tried (i tried a lot of them)
please any one have this issue for viber or nimbuzz or any free calling application?
Thank you in Advance
Yamen
i have same issue with skype and nimbuzz. I use boyppc gingerbread v33. Have you a solution for that?
No and no one is even trying to help
Sent from my SGH-T959 using XDA App
have no idea gents. if I use skype I can call out no problem
I am having similar problem with Viber as well, and i've got a gut feeling this is audio-routing related, possibly Bluetooth routing related. Viber got no "test call" number, so i have to actually call someone in order to test this, produce some logs etc, meaning i can't really try looking deeper right now.
Anyway, hopefully i'll try doing the following tomorrow:
1) Try without the Bluetooth support enabled in Vipers and without the Bluetooth being on at the phone, just to see if i can still reproduce the issue or not without any Bluetooth audio routing involved at any level.
2) Reproduce the issue with a log cat, maybe i'll be able to spot something interesting in there.
PS: The nasty part is, the chances of me finding the problem are really low, and even if i do find it, i don't have the environment to recompile a thing, meaning i couldn't even try fixing it. I am not exactly an Android junkie/guru/etc :-(
EDIT: Just tried without bluetooth, still getting the issue. It isn't immediately clear what's going on here from the diffs between the good and the bad log either, at least, not for me. The logs are just kinda state the obvious - the good one ends up starting the voice, the bad one does not. Also, in the bad log the system starts killing unrelated services (not shown in the log part below), can be coincidence, but can also be the system running out of memory because of some dynamic stream buffer, too.
I really hope someone with proper knowledge and experience is going to notice this thread and helps us.
Good log:
Code:
I/phone ( 963): acceptCall: incoming...
D/AudioHardwareQSD( 103): Setting mic mute to 0
I/AudioService( 579): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface( 103): setMode(IN_CALL)
D/AudioFlinger( 103): setParameters(): io 1, keyvalue routing=1, tid 113, calling tid 103
I/AudioHardwareQSD( 103): Routing audio to Handset
D/AudioHardwareQSD( 103): skip update ACDB due to in-call
D/AudioHardwareQSD( 103): skip update ACDB due to in-call
D/AudioHardwareQSD( 103): Switching audio device to
D/AudioHardwareQSD( 103): Handset
D/AudioHardwareQSD( 103): Voice Started!!
D/AudioHardwareQSD( 103): Setting in-call volume to 100
Bad log:
Code:
I/phone ( 961): acceptCall: incoming...
I/AudioService( 579): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface( 103): setMode(IN_CALL)
D/AudioFlinger( 103): setParameters(): io 1, keyvalue routing=1, tid 113, calling tid 103
I/AudioHardwareQSD( 103): Routing audio to Handset
D/AudioHardwareQSD( 103): skip update ACDB due to in-call
D/AudioHardwareQSD( 103): Switching audio device to
D/AudioHardwareQSD( 103): Handset
I don't know if this is too late or not, but since I can't post in any development forums (low post count issue)
I'm using AmericanAndroid NAND Rom and I had this problem, where I can't make or receive normal GSM calls after using VIBER calls.
I used the other version of file libaudio.so from this post
http://forum.xda-developers.com/showpost.php?p=17900515&postcount=198
and replaced my existing file in system/lib .. changed the premissions(i did it with root explorer), rebooted the phone, and it seems that i solved the problem not being able to receive or make a call over GSM.
Phone application is a little bit slow on first call after using Viber ,.. but after that it functions normaly.
NOTE: Backup ur old libaudio.so from System/lib - don't delete it and make sure premissions are set to rw-r--r-- othervise u won't be able to boot up your phone after restart.
The best success I have had was with tytung 12.4 kernel and GPC's libaudio.so from 2.8E... But even then viber made me lose sound- though did not get a dialer FC. I have removed viber ever since, but the no sound issue is far from dead...
Swyped from my HTC HD2 running CM7 (Gingerbread 2.3.7)
I must reply on my self...
The problem seems to be resovled but only for a few seconds..
I tested a VOIP call over Viber for a few seconds and it was OK. Then i used normal phone, and also got full response, tried to make a call, tried to receive a call - all OK but my tests were few seconds long.
When I wanted to make an actual call that is supposed to last longer than few seconds I got another problem: Other side could hear me only on first 10-20 seconds, after that period, other side would hear just muble jumble from me (connection quality = excelent).
exactly same problem here with viber
I counducted one more test...
While making a call in viber i tried not to trigger "scheen shutdown sensor"... in vibers case Screen would't shut down but only go black...
and i managed to make call that lasted more than a few seconds. As soon as the sensor gets triggered and screen goes black (not off), my problem occures. (Othes side can't her what am I saying only rubbish, and i have to hang UP and make a call again).
As long as i keep the my display sensor from triggering everything is well...
I don't know is there a way to disable the sensor in Viber or not but other than that I'm able to make a Viber call, and GSM calls with the libaudio file from above post.
After few more tests I concluded that the Sensor might not be an issue...
I'm now puzzled more than ever
For all of you havin issues with VOIP apps like Viber try libaudio from this post:
http://forum.xda-developers.com/showpost.php?p=16016409&postcount=5967
It's an older version of libaudio.so and for now it showed best results with Viber on my ROM (AmericanAndroid NAND Version) .. Sometimes it gets a bit laggy but didt crash, and I can still answer incomming GSM calls.
Warning: this libaudio might have some other issues with other devices or something else ... but for for the purpose of using Viber and making GSM calls it showed best results..
and also don't forget to set the proper rights rw-r--r--
twoborg said:
and also don't forget to set the proper rights rw-r--r--
Click to expand...
Click to collapse
I would like to try,but i don t know what rw-r--r-- permission I have to set
Just one advice... do not overwritte your actual libaudio.so just rename it to libaudio_old or something else.
Copy the new libaudio.so in system/lib and tap and hold ond the file. You'll get a new menu ... choose premissions and enable read and write for owner... and just read for all other (user and group)
If all set as told you will get rw-r--r-- shown in root explorer (i'm using it and not sure how are premissions shown in other file managers...)
After and only after you set the premissions restart the phone
Issue with this lobaudio is that you cant use bluetooth headset when making a call...but you can use viber and gsm phone without issues ... if you need bluetooth go back to the libaudio_old rename it and restart the phone.....
ok i ve only installed the zip file,i don t need the bluetooth headset.Untill now seems to work
Axel85 said:
ok i ve only installed the zip file,i don t need the bluetooth headset.Untill now seems to work
Click to expand...
Click to collapse
yes but that libaudio.so has the dont remembering volume level problem in calling out...
some solution
check out my findings here

Volume Hack Help Please

Right I have done this for the earphone volume:
•Enter the phone dialer
•##634#, tap Call
•Enter code: *#0002*28345# > for Samsung Omnia 7
•Tap: Get under the Device Gain (max/min)
•For "device gain" leave number 5, set 1100 (max) and -1100 (low)
•Tap: Set
•Verify that AUDIENCE.CFG is ON
•Tap: Start
•Tap Home
•Restart your phone.
•After reboot, enter the same menu and just tab get to verify the settings
The problem is now the speaker volume is so high like its going to blow up. I have followed other posts and they dont seem to help with the speaker volume.
This is the issue I get:
http://forum.xda-developers.com/showthread.php?t=1183446
if it helps I have the 16GB Germany version

Categories

Resources