Develop Bugs

HTC Desire Wi-Fi Problem

Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
Setting a static IP fixed it temporarily but now it doesn't work again.

I have the same problem, wait for a solution.

I also have the same problem

Can you post what rom and radio versions you are using?
Usually this happens because the driver cannot be loaded.

I use :
for radio : 32.43.00.32u_5.09.00.20
for kernel: 2.6.32.15-gf9c0527 [email protected] #1
build: 2.09.405.8 CL218634
soft: LeeDroid_v1.8
I also try: Pays Desire Froyo Sense v1.9

Had the same problem. Wi-Fi starts fine, but if switched off, was unable to start again with the "Unable to start Wi-Fi" error.
Tried flashing different stock roms/radios, updating to Froyo, all sorts, in the end, I sent it back to HTC, they repaired it and I had it back within 4 days.

I just installed
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe and the wifi problem seems to be solved

dunno, if it really helps. but I had the same problem with all custom roms which used to have wifi-n support. at first, I tried anything starting with wiping, reinstalling and using roms without wifi-n. none of it really helped. but then I changed one single setting on my wifi access point and everthing worked fine with ANY rom and ANY kind of wifi-bandwith.
just a guess, but at least you could try setting your wireless-channel from fixed (mine was fixed to 5) to automatic. there should be an option within your wireless-config on your router called "enable auto channel scan" or something like that...
unless your router is not a really old or crappy one, this could be a solution
edit: PS. I used tested almost every custom rom out of this forum. ALL roms with wifi-n support had the same issues. even newest radio didnt help much. maybe there is something about wifi-n which causes these issues

After two days using "RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00. 32U_5.09.00.20_release_140022_signed" rom, my wifi continue to work like a charm.

[Q] No Wifi broadcasting when in Hotspot mode

I'm having an interesting issue with my AT&T Galaxy Nexus.
At some point, most likely after an update, Wifi tethering stopped working. Because this is a feature I use irregularly, I cannot say for certain when it stopped working. I'm currently using 4.2, but the error persisted into 4.2.1. I know that tethering was working in the past, perhaps in 4.1 or 4.1.2.
The symptom is that when I activate the tethering hotstop, the phone does not turn on the wifi radio (specifically in AP mode). There is no indication of problems on the handset, all of the icons are correct for being in hotspot more, no error message are given. However no other device such as my laptop, Nexus 7, daughters iPod, etc, etc, shows an available wifi network. Tethering and IP forwarding are working because I can correct to the Galaxy Nexus's bluetooth for internet sharing. The problem seems confined to just the Wifi radio.
I did some digging into the logs and discovered the following:
E/hostapd ( 6484): Configuration file: /data/misc/wifi/hostapd.conf
E/hostapd ( 6484): HT (IEEE 802.11n) in 11b mode is not allowed, disabling HT capabilites
I/hostapd ( 6484): rfkill: Cannot open RFKILL control device
E/hostapd ( 6484): nl80211: Failed to set interface wlan0 into AP mode
as well as:
E/hostapd ( 6484): nl80211 driver initialization failed.
All of the log entries for Tethering and TetherController seem correct when I turn off and on the hotspot service.
My /data/misc/wifi/hostapd.conf is pretty basic and has not been hand modified:
interface=wlan0
driver=nl80211
ctrl_interface=/data/misc/wifi/hostapd
ssid=tcgmobile
channel=6
ieee80211n=1
(i have the network open for now during my testing)
The WIFI works fine in normal client mode.
Can anyone shed any light on this? Perhaps there is a driver bug in 4.2?
My next move will be to start wiping and flashing various older ROM versions to try and diagnose this further if no one has any suggestions.
Thanks

mckinleytabor said:
I'm having an interesting issue with my AT&T Galaxy Nexus.
At some point, most likely after an update, Wifi tethering stopped working. Because this is a feature I use irregularly, I cannot say for certain when it stopped working. I'm currently using 4.2, but the error persisted into 4.2.1. I know that tethering was working in the past, perhaps in 4.1 or 4.1.2.
Click to expand...
Click to collapse
I can confirm the issue, seeing the very same behaviour my Nexus S with 4.2.1. It worked with 4.1.1, not sure with 4.1.2
DMESG shows this when trying to enable thetering:
<4>[ 4001.586766] wl_android_wifi_off in
<6>[ 4001.587047] wake disabled for irq 164
<4>[ 4001.587205] wifi_set_power = 0
<4>[ 4001.587275] =========== WLAN placed in RESET ========
<4>[ 4001.601863] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 4001.601970] CFG80211-ERROR) wl_cfg80211_change_virtual_iface : WLC_SET_INFRA error (-1)
<4>[ 4001.602190] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 4001.602345] CFG80211-ERROR) wl_cfg80211_change_virtual_iface : WLC_SET_INFRA error (-1)
<4>[ 4001.602515]
<4>[ 4001.602518] Dongle Host Driver, version 5.90.195.75
<4>[ 4001.602522] Compiled in drivers/net/wireless/bcmdhd on Sep 10 2012 at 14:10:03
<4>[ 4001.602758] wl_android_wifi_on in
<4>[ 4001.602889] wifi_set_power = 1
<4>[ 4001.808894] =========== WLAN going back to live ========
<4>[ 4001.809548] sdio_reset_comm():
<4>[ 4001.827717] F1 signature read @0x18000000=0x9934329
<4>[ 4001.829946] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 4001.874294] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
<6>[ 4001.927125] wake enabled for irq 164
<4>[ 4001.928275] wifi_get_mac_addr
<4>[ 4001.931207] Firmware up: op_mode=2, Broadcom Dongle Host Driver mac=02:1a:11:f6:58:92
<3>[ 4001.937722] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23

the default wireless tether is working fine here, but third party tether apps do not work until updated for 4.2.X. are you using the default wireless tether with security? try leaving the network open.

Fixed... In a mannor of speaking.
Being somewhat inpatient I went ahead and started experimenting with reflashing ROMs on my device. I didn't actually get very far because it worked on my first attempt.
I did a complete factory reset and reflashed the ROM I had on the device to start with. The ROM is located here: http://forum.xda-developers.com/showthread.php?t=1737849
It would seem that the factory reset did the trick. I went back and confirmed the log files and config files on the new flashing and they are essentially identical to the old flashing. Ergo whatever was preventing the driver from loading was not related to my previous post.
I did have to spend a fun 90 minutes reinstalling all of my software and restoring a manual backup of the SD card data but that needs to be done periodically anyways to clear all the stuff I don't use. So all's well that ends well.

simms22 said:
the default wireless tether is working fine here, but third party tether apps do not work until updated for 4.2.X. are you using the default wireless tether with security? try leaving the network open.
Click to expand...
Click to collapse
I tried the default wireless tethering with various options including secure, open, and different permutations of the network SSID.

Tab Pro 8.4 + TWRP 2.7.0.2 + CM11 = wrong date & time

Hi, I have some weird behavior with date and time in CM11 - I can set it through settings (I can`t use network time, I do it manually), but after reboot it reverts back to 2nd January 2014 It is not frozen though, it changes in time. Another strange thing that in TWRP time is total different from actual and that reverted in CM11. So I have three "times": original we live in, for CM11 after reboot and for TWRP
As I can`t find anything about it, I suppose everyone`s time is fine. So can someone with CM11 and TWRP please try to set some wrong time manually and check whether it is changes on reboot? Thanks.
EDIT: While researching, I find this line on dmesg output:
"alarm_set_rtc: Failed to set RTC, time will be lost on reboot"
Found this topic
http://forum.xda-developers.com/showthread.php?t=2480713
So, maybe crpalmer could confirm that all is needed is to recompile kernel with `rtc_write_enable` to `true` flag?

Zero-V said:
Hi, I have some weird behavior with date and time in CM11 - I can set it through settings (I can`t use network time, I do it manually), but after reboot it reverts back to 2nd January 2014 It is not frozen though, it changes in time. Another strange thing that in TWRP time is total different from actual and that reverted in CM11. So I have three "times": original we live in, for CM11 after reboot and for TWRP
As I can`t find anything about it, I suppose everyone`s time is fine. So can someone with CM11 and TWRP please try to set some wrong time manually and check whether it is changes on reboot? Thanks.
EDIT: While researching, I find this line on dmesg output:
"alarm_set_rtc: Failed to set RTC, time will be lost on reboot"
Found this topic
http://forum.xda-developers.com/showthread.php?t=2480713
So, maybe crpalmer could confirm that all is needed is to recompile kernel with `rtc_write_enable` to `true` flag?
Click to expand...
Click to collapse
My time is correct (via network time services). Why (and how) are you unable to use them?
Can you provide specific steps to reproduce the problem that you are seeing?

crpalmer said:
My time is correct (via network time services). Why (and how) are you unable to use them?
Can you provide specific steps to reproduce the problem that you are seeing?
Click to expand...
Click to collapse
I`m not surprised that your time via network sync is correct. About why - I`ll make long story short: I have no wifi now and will not have for some times in future.
Specific steps are easy enough: set manually time&date in settings, then reboot - time&date are far from what you have set (without network syncing of course).
Can you go to terminal or adb shell and see if that rtc message is there? E.g.
dmesg | grep time
or
adb shell su -c dmesg | grep rtc

Zero-V said:
Hi, I have some weird behavior with date and time in CM11 - I can set it through settings (I can`t use network time, I do it manually), but after reboot it reverts back to 2nd January 2014 It is not frozen though, it changes in time. Another strange thing that in TWRP time is total different from actual and that reverted in CM11. So I have three "times": original we live in, for CM11 after reboot and for TWRP
As I can`t find anything about it, I suppose everyone`s time is fine. So can someone with CM11 and TWRP please try to set some wrong time manually and check whether it is changes on reboot? Thanks.
EDIT: While researching, I find this line on dmesg output:
"alarm_set_rtc: Failed to set RTC, time will be lost on reboot"
Found this topic
http://forum.xda-developers.com/showthread.php?t=2480713
So, maybe crpalmer could confirm that all is needed is to recompile kernel with `rtc_write_enable` to `true` flag?
Click to expand...
Click to collapse
I finally got a chance to try this out for you and I think that the reason that the write is disabled is that our hardware PM hardware doesn't have an RTC that can be set.
When I enable the write, it tries it and fails:
Code:
<6>[ 7.226332] qcom,qpnp-rtc qpnp-rtc-e1946600: Seconds value to be written to RTC = 1392714221
<3>[ 7.226437] qcom,qpnp-rtc qpnp-rtc-e1946600: SPMI write failed
<3>[ 7.226443] qcom,qpnp-rtc qpnp-rtc-e1946600: Write to RTC reg failed
which means that there isn't much that I can do to fix it.

crpalmer said:
I finally got a chance to try this out for you and I think that the reason that the write is disabled is that our hardware PM hardware doesn't have an RTC that can be set.
When I enable the write, it tries it and fails:
Code:
<6>[ 7.226332] qcom,qpnp-rtc qpnp-rtc-e1946600: Seconds value to be written to RTC = 1392714221
<3>[ 7.226437] qcom,qpnp-rtc qpnp-rtc-e1946600: SPMI write failed
<3>[ 7.226443] qcom,qpnp-rtc qpnp-rtc-e1946600: Write to RTC reg failed
which means that there isn't much that I can do to fix it.
Click to expand...
Click to collapse
Strange, so there is no way to change hardware clock from OS? Even from stock Samsung`s Android? Maybe from recovery? I mean I think it has to be a way to set it somehow...
EDIT:
Wait, are you saying there is no hardware RTC of any type? I doubt it! Because when rebooted, tablet`s clock is not set to specific date&time, it is go back by some N seconds. And anyway not having RTC in such device is almost impossible imho.

Messaging crashing repeatedly on upgrade from CM 12.1 to CM 13 - Permissions? SOLVED

Code 14: Could not open database. Some sort of permissions problem?
I have had CM 12.1 on a Nexus 5 for a while. Every time I upgraded to CM13 everything would work fine EXCEPT messaging would keep throwing "Sorry, messaging has stopped" message. So I Stayed on CM12.1. I just upgraded to a Nexus 5X and there is no CM12.1 for it so I tried Cm13 (Latest Nightly 6-18) and it seemed to work fine, just on WiFi and setting it up. I loaded what I always do, Android Firewall, checked all my permissions in Privacy Guard, used SU2.95 so I would have root. It still worked fine connected to my WiFi. I just got back from TMobile where I had to switch from MicroSIM to NanoSIM. put the sim in and the same messaging error shows up. So, working backwards, I unchecked ALL privacy guard, turned OFF the firewall, and rebooted. Still gives me the messaging error. So, I finally read the error message and its SQLite Error 14 on some database. Any ideas what I could try next? I suppose I can reload CM and set it all up again, and see where it starts to fail but that would be throwing away 4 hours from yesterday. I'm also not certain that the native App permissions aren't involved somehow. The phone IS encrypted but I have tried it both ways in the past.
I know there are all sorts of geniuses on here, and I am not smart enough.
Code:
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: android.database.sqlite.SQLiteException: unknown error (code 14): Could not open database
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:179)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:421)
at android.content.ContentResolver.query(ContentResolver.java:493)
at android.content.ContentResolver.query(ContentResolver.java:435)
at com.android.messaging.util.f.oH(SourceFile:53)
at com.android.messaging.util.f.doInBackground(SourceFile:34)
at android.os.AsyncTask$2.call(AsyncTask.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
... 4 more
EDIT : so i got into App permissions (new to MM?) and made sure the messaging service had storage and read and write on SMS. still looking deeper and searching the net...
EDIT : APN issue? reset to default TMobile settings and rebooted. still fails.
EDIT : could it be that I used the PICO version of OpenGAPPS? anyone had a problem with that? been searching still...
SOLVED : I'm such an idiot. I have been moving my blacklist.db database from version to version so I dont have to put all the numbers in again (wouldn't it be nice if there was a blacklist manager? I have all these spam numbers attached to a contact but you still have to choose them one by one) and of course between CM 12.1 and CM 13 they changed the database format or something so thats why it was crashing. Just one of the many steps I took getting my new phone set up.

If you pull SIM card out of the phone, does the crash still happen?

seetings keeps stoping when i try to change unlock password

Recently was installing an app that required permissions that need the password to give - a VPN (a trusted one) - and when I inputted my pin it lagged for a moment and then said settings has stopped. so I tried just changing my password which I had done just a few days before and it also crashed. so I tried a few times and restarted a few times and checked for updates and I cleared settings cache and I uninstalled the VPN and I tried all of the above again but still, it kept stopping no matter what I tried. I looked at the summary and it seems that it is trying to verify on a null object reference or something like that - I will copy it below. any suggestions on how to fix this?
error summery
------------------
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:353)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int com.android.internal.widget.VerifyCredentialResponse.getResponseCode()' on a null object reference
at android.os.Parcel.readException(Parcel.java:2022)
at android.os.Parcel.readException(Parcel.java:1962)
at com.android.internal.widget.ILockSettings$Stub$Proxy.checkCredential(ILockSettings.java:642)
at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:370)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:422)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:409)
at com.android.settings.fj.doInBackground(LockPatternChecker.java:133)
at com.android.settings.fj.doInBackground(LockPatternChecker.java:130)
at android.os.AsyncTask$2.call(AsyncTask.java:333)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more

Facing same issue. Any fixes on this?

viveksuryavanshi said:
Facing same issue. Any fixes on this?
Click to expand...
Click to collapse
Or any suggestions on why this happened.