Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
This is mostly a post about a specific problem with Google Play carrier billing.
Here is the problem:
I want to subscribe to a trial of Google Play Music All Access
I want to use carrier billing (with my Verizon Wireless phone)
When I select "Bill my Verizon Wireless account", I get a red message stating "Error processing your purchase"
Notes:
Carrier billing usually works for me with Verizon Wireless
I am NOT using WiFI while trying to make the purchase
I do not have blocks on messaging or web purchases with Verizon Wireless
Verizon Wireless support cannot find any reason why the purchase would fail
I am well below the $25/mo. cap for Verizon Wireless carrier billing (I've only spent $.99 this month so far)
Step by step:
I turned off WiFi on my android phone (mostly stock rooted Samsung Galaxy Nexus running JB 4.2.2 on VzW).
I plugged my phone into my PC with the USB cable.
USB debugging is on.
I fired up adb shell on my PC.
I used su to start a superuser shell in adb
I typed:
Code:
logcat | grep --color=auto -i -E 'play|market|store|carrier|billing|finsky|phonesky|vending'
I launched Play Music (version v5.0.1041J.689753)
I opened the menu (...)
I selected "Settings" from the menu
I selected "Try All Access for free" in settings
I was sent to a "Google play" screen titled "Try Google Play Music All Access"
I selected "Try it FREE"
A modal dialog box opened titled "Google Play Music All Access"
From logcat:
Code:
I/ActivityManager( 378): START u0 {act=com.android.vending.billing.PURCHASE cat=[android.intent.category.DEFAULT] pkg=com.android.vending cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity (has extras)} from pid 8403
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity: +121ms
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity (has extras)} from pid 1708
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity: +153ms
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I clicked "Free"
I clicked "Payment options"
I clicked "Bill my Verizon Wireless account"
From logcat:
Code:
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity (has extras)} from pid 1708
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity: +140ms
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
D/Volley ( 1708): [155] BasicNetwork.logSlowRequests: HTTP response for request=<[ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133> [lifetime=14351], [size=7526], [rc=200], [retryCount=0]
D/Volley ( 1708): [1] Request.finish: 14363 ms: [ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133
I get "Error processing your purchase." in red print
This line really got my attention:
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
I'm assuming "DCB" is "Direct Carrier Billing", and "DCB 2" might be something like a monthly subscription billed with carrier billing. I make purchases with carrier billling so I'm not sure why it would say "Carrier billing config is null."
To make sure carrier billing is working (still), I launched "Angry Bird Seasons", and went "shopping" for 80 power-up bundles for $4.99. I select the same options for "Payment Options" and "Bill my Verizon Wireless account" and "Buy" (bringing me to the "Confirm password" screen, where I canceled the purchase).
This line stood out from logcat:
Code:
D/Finsky ( 1708): [1] PurchaseFragment.runCompleteFlowAndContinue: Start complete flow for DCB3 instrument.
"DCB3" ???. Maybe another "Direct Carrier Billing" purchase type (for a one-time consumable purchase)?
Since Google Play is not open source, I have no way of looking at the code to see what these debug lines actually mean.
Can anybody give me any guidance on this?
Having the same problem with a rooted Droid RAZR. Does it on both the stock rom and CM10.1.
Edit: Called customer service. They are looking into it. Told me they should contact me back in 24/48 hours.
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
MasterAwesome said:
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
Click to expand...
Click to collapse
Hello again,
I've made logcat, here is an interesting part, I think:
I/SecurityManagerService( 671): SMS received security event: App[START/com.android.keyguard]
I/WindowState( 556): WIN DEATH: Window{26a85ad0 u0 Keyguard}
I/ActivityManager( 556): Process com.android.systemui (pid 622) has died.
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
W/ActivityManager( 556): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
D/InputMethodManagerService( 556): --- calledFromForegroundUserOrSystemProcess ? calling uid = 1000 system uid = 1000 calling userId = 0, foreground user id = 0, calling pid = 556dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
I/StatusBarManagerService( 556): binder died for pkg=com.android.keyguard
I/WindowState( 556): WIN DEATH: Window{269b48a8 u0 NavigationBar}
W/InputDispatcher( 556): Attempted to unregister already unregistered input channel '268ba8e8 StatusBar (server)'
D/dalvikvm( 3948): Try to disable coredump for pid 3948
D/dalvikvm( 3948): Process 3948 nice name: com.android.systemui
D/dalvikvm( 3948): Extra Options: not specified
Click to expand...
Click to collapse
I discovered also that when the battery level drops to 99% process starts to work properly.
I include also whole log file compressed to .zip.
Still need help!
I have the same problem, even after a factory reset.
me too having the same issue. Is it hardware failure or just android?
I found a solution in an other tread :
http://forum.xda-developers.com/android/general/review-teclast-x89-baytrail-tablet-dual-t3039961
My tasker app keeps getting killed after a while. Keeps closing on it's own. Can't figure it out what causing this. Tasker is running in foreground (Prefs / Monitor / Run In Foreground).
System is Cyanogenmod 11, Lenovo k910, Android 4.4. Any help please?
Here's excerpt from the log with the part when tasker get killed. Maybe this will help with identifying the problem.
Code:
com.google.android.location.fused.LOCATION_REQUESTS
I/Fitness ( 1918): WearableSyncHostService elapsedNanos: 8229
W/bt-btif ( 3206): bta_dm_pm_btm_status stopping timer if activesince sniff mode is enabled
I/ActivityManager( 985): Force stopping net.dinglisch.android.taskerm appid=10033 user=0: pkg changed
I/ActivityManager( 985): Killing 9354:net.dinglisch.android.taskerm/u0a33 (adj 2): stop net.dinglisch.android.taskerm
W/ActivityManager( 985): Scheduling restart of crashed service net.dinglisch.android.taskerm/.MonitorService in 1000ms
I/ActivityManager( 985): Force stopping service ServiceRecord{435bb5e8 u0 net.dinglisch.android.taskerm/.MonitorService}
W/Launcher.Model( 8920): Nobody to tell about the new app. Launcher is probably loading.
W/Launcher( 8920): setApplicationContext called twice! [email protected] [email protected]
I/InputReader( 985): Reconfiguring input devices. changes=0x00000010
I/ActivityManager( 985): Force stopping net.dinglisch.android.taskerm appid=10033 user=0: from pid 28752
I/cm.log.servpro( 5146): [AutoStart]/ AutoBgRepair : net.dinglisch.android.taskerm#net.dinglisch.android.taskerm.ReceiverStaticInternal#action:TIME_SET
D/PackageBroadcastService(28288): Received broadcast action=android.intent.action.PACKAGE_CHANGED and uri=net.dinglisch.android.taskerm
I/PackageManager( 985): Action: "android.intent.action.SENDTO"
I/PackageManager( 985): Category: "android.intent.category.DEFAULT"
I/PackageManager( 985): Scheme: "sms"
I/UpdateIcingCorporaServi( 2145): Updating corpora: APPS=net.dinglisch.android.taskerm, CONTACTS=MAYBE
I'm on my way on modifying some custom ROM (DUI)'s System UI custom features that currently are yielding some minor errors on my devices.
So, I build the ROM from source in eng variant, I can attach to the systemui process and start debugging. It works pretty well, but only for a little while. After this, the device's screen turns black and SystemUI restarts; the debugging session is lost.
On logcat there's this message of interest:
Code:
02-14 11:53:10.005: W/BroadcastQueue(5796): Timeout of broadcast BroadcastRecord{9b4c2d1 u-1 android.intent.action.TIME_TICK} - [email protected], started 10001ms ago
02-14 11:53:10.006: W/BroadcastQueue(5796): Receiver during timeout: BroadcastFilter{bf8a6f7 u0 ReceiverList{15542f6 6006 com.android.systemui/10035/u0 remote:f58e391}}
02-14 11:53:10.005: W/ActivityManager(5817): type=1400 audit(0.0:17499): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=process permissive=0
(...)
02-14 11:53:10.090: I/Process(5796): Sending signal. PID: 6006 SIG: 3
02-14 11:53:10.090: I/art(6006): Thread[3,tid=6024,WaitingInMainSignalCatcherLoop,Thread*=0x40484e00,peer=0x12c00670,"Signal Catcher"]: reacting to signal 3
02-14 11:53:10.543: I/art(6006): Wrote stack traces to '/data/anr/traces.txt'
02-14 11:53:10.558: E/ActivityManager(5796): ANR in com.android.systemui
I'm sorry because I'm quite new in Android Framework programming, so maybe this is quite obvious. But the problem is that there's a 10 secs timeout from android.os.BinderProxy and when it expires the ANR is raised. Am I right? Is it possible to avoid/extend this timeout to debug SystemUI?
I tried in Developers Options to set SystemUI as the debugged application, with no success.