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.

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.

same problem with my desire. I re-flash several ROM, but not change. May be the hardware fault. sadly

I have the same problem on Legend & it isn't rooted

Nexus 7 4.4.2- Boots To Lockscreen Then Reboots After Few Seconds

Boot problem
Hey guys
Since today I have this problem:
youtube/watch?v=CVQnRhazofk
I can still unlock it and use everything till it reboots.
Infos:
Android Version: 4.4.2
Kernel Version: 3.4.0-gac9222c
[email protected] #1
Wed Nov 20 14:50:44 PST 2013
Build Number: KOT49H
That's all I could find about my device.
I hope someone can help me fix this problem.

sasuke12096 said:
Hey guys
Since today I have this problem:
youtube/watch?v=CVQnRhazofk
I can still unlock it and use everything till it reboots.
Infos:
Android Version: 4.4.2
Kernel Version: 3.4.0-gac9222c
[email protected] #1
Wed Nov 20 14:50:44 PST 2013
Build Number: KOT49H
That's all I could find about my device.
I hope someone can help me fix this problem.
Click to expand...
Click to collapse
Is your bootloader unlocked? Have you rooted? Installed a custom Rom? Kernel? Recovery?

What do you mean by bootloader unlocked? I didn't change anything. So no custom rom , not rooted etc.

I have the same problem, running 4.4.4 (KTU84P)
I'm rooted with Xposed + GravityBox, Xprivacy, and a couple others, but disabling Xposed didn't seem to help at all.
---------- Post added at 07:47 PM ---------- Previous post was at 06:48 PM ----------
elbenny said:
I have the same problem, running 4.4.4 (KTU84P)
I'm rooted with Xposed + GravityBox, Xprivacy, and a couple others, but disabling Xposed didn't seem to help at all.
Click to expand...
Click to collapse
I flashed stock system.img and that didn't help either, so I can't blame root or Xposed.
Some googling found a few references to others with similar problems. One post mentioned quickly unlocking and disabling wifi (+ mobile data if you have it) stops the boot loops, and I was able to reproduce that. Unfortunately, a tablet with no internet access isn't very useful.
I've since tried flashing latest 5.1.1 (LMY48P) which did not boot loop. Maybe I will finally suck it up and move to Lollipop.

turning out the wifi really helped. It stopped to reboot but it's not really useful without internet

elbenny said:
I've since tried flashing latest 5.1.1 (LMY48P) which did not boot loop. Maybe I will finally suck it up and move to Lollipop.
Click to expand...
Click to collapse
Looks like I spoke too soon. 5.1.1 bootloops (earlier, though) if I restore my /data from 4.4.4 nandroid.
---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------
sasuke12096 said:
turning out the wifi really helped. It stopped to reboot but it's not really useful without internet
Click to expand...
Click to collapse
I agree, no wifi is pretty pointless and hopefully Google will come up with a proper fix.
I'd post the link but I can't yet, anyway you can search "Google product forums" for a thread called "Unable to start up nexus 7"
Maybe you can chime in over there too

This fixed it:
I haven't seen this on a Nexus 4 yet, but I had this happen last night on a Nexus 5 and got it fixed this evening. A call to T-mobile indicated that they haven't run across it yet either, but I found an XDA thread where they were seeing on a Galaxy S4. I'll post some steps for a somewhat tricky fix and then a write-up on what I think is happening based on what I found. Hopefully this will help.
1) Power off phone. Hold power button down until you see the Google logo come up and then disappear. That should stop the "boot loop" and keep the phone powered off. If it comes back on, try again and just hold the power button down a little longer than you thought you needed to.
2a) Steps 2-5 below can probably be replaced by putting the phone into airplane mode quickly while it's temporarily alive during the boot loop. If you put it into airplane mode and the boot loop stops, skip to step 6 and just disable airplane mode for steps 9/10.
2) Eject SIM card. You should have the little tool (round with a short, narrow point) that presses into a tiny hold on the side of the phone to eject the sim card. If you are uncertain on this step, get some help.
3) Power on phone. If you were connected to Wi-Fi when this started, it will still boot loop so we need to disable Wi-Fi as well. This is the tricky part. You may find it easy if you power off your wireless router before trying to turn off Wi-Fi on your phone.
4) Disable Wi-Fi as quickly as possible by swiping lock screen, pulling down the settings "drawer" at the top of the phone, clicking on wi-fi and click it off.
5) The phone should no longer reboot, but will start to reboot again if you give it a network connection (wi-fi or mobile) so don't reconnect it to the network until you are done with the next couple steps.
6) Go to Settings -> Apps and scroll over to ALL.
7) Scroll down to Google Services Framework and click it
8) Click on CLEAR DATA and hit Ok. I also hit CLEAR CACHE and while I'm not sure it's necessary, I recommend doing that as well.
9) Power off phone, re-install SIM card and power on phone.
10) Assuming you don't immediately go into a boot loop again, it's probably fixed. Re-enable wi-fi and go back to enjoying life
The trickiest part here is being fast enough to disable wi-fi before the reboot happens. It may be a non-issue if turning off the wireless router helps.
As a caveat, we haven't been running the phone for very long after clearing that data, but it's acting a little sluggish at times. I'm going to let it run for a day or two and then maybe do a full factory reset if it doesn't clear up. At the very least, the boot loop is gone.
------------------------------------------------
Now for the nerdy stuff in the hopes someone from the major providers and/or Google is watching this...
Late last night, I hooked up ADB to the phone after getting Wi-Fi disabled and USB Debugging enabled. A logcat dumped out a huge amount of data, but thankfully caught the reboot when I re-enabled Wi-Fi. Here's a partial dump from the log:
I/iu.SyncManager( 1201): NEXT; no task
I/CheckinRequestBuilder( 1201): Checkin reason type: 12 attempt count: 1
D/dalvikvm( 1087): GC_CONCURRENT freed 417K, 4% free 18384K/19056K, paused 2ms+2ms, total 19ms
W/dalvikvm( 744): threadid=13: thread exiting with uncaught exception (group=0x41564ba8)
E/AndroidRuntime( 744): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.bg
E/AndroidRuntime( 744): java.lang.NullPointerException
E/AndroidRuntime( 744): at android.content.PeriodicSync.syncExtrasEquals(PeriodicSync.java:150)
E/AndroidRuntime( 744): at android.content.PeriodicSync.equals(PeriodicSync.java:129)
E/AndroidRuntime( 744): at com.android.server.content.SyncStorageEngine.setPeriodicSyncTime(SyncStorageEngine.java:1625)
E/AndroidRuntime( 744): at com.android.server.content.SyncManager$SyncHandler.scheduleReadyPeriodicSyncs(SyncManager.java:2097)
E/AndroidRuntime( 744): at com.android.server.content.SyncManager$SyncHandler.handleMessage(SyncManager.java:1881)
E/AndroidRuntime( 744): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 744): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 744): at android.os.HandlerThread.run(HandlerThread.java:61)
I/Process ( 744): Sending signal. PID: 744 SIG: 9
I/ServiceManager( 176): service 'package' died
I/ServiceManager( 176): service 'batterystats' died
I/ServiceManager( 176): service 'usagestats' died
W/Sensors ( 1876): sensorservice died [0x7645fde0]
D/AndroidRuntime( 1087): Shutting down VM
many more services dieing
Note the null pointer exception in android.bg on a "PeriodSync" I don't know what that's supposed to do, but it clearly can only trigger with a valid network connection and it is very displeased with life. A search for some key words from the traceback led me to XDA (http://forum.xda-developers.com/showpost.php?p=62943303&postcount=2119). The symptoms matched what I was seeing and they mention going into Airplane mode to stop the boot loop which may be an even better approach than my somewhat heavy handed solution above. Speculation in that thread indicates a google apps update of some sort which I assume probably came through on my wife's phone last night with automatic updates.

Stuck on "Checking Network" setup screen on all non sense roms

Hi guys,
SO I have no idea how to solve this issue. I'm running Viper ROM and everything works perfect, if I switch to any other ROM Resurrection Remix, Dirty Unicorns, AIPC it installs fine and boots no problem, but in the initial setup when I pick a wifi Network (or LTE) it sticks on the "Checking Network - adding a few finishing touches, this may take a minute (or something)" screen.
If I choose don't use network and setup later, the ROM boots fine but all google services Play store, Gmail, anything it goes to a white screen that says "error contacting Google servers - Please try again later"
I have NO Idea what to do, I have used RR ROM for quite a while a few releases back with no issues and I have a hunch my trouble started after Linage OS became a thing, everything seemed fine before that. If anyone has had this issue or can offer any help it would be really really appreciated!
I'm using a International HTC 10 on the canadian Bell network. I'm still using the MM firmwear but multiple people have confirmed these ROMS work fine on MM Firmwear.
PLEASE HELP!!!
Thanks
John

I just installed Lineage OS, and have exactly the same problem. Can't complete "adding a few finishing touches" completing setup using network, if I skip that step and try to do anything needing a Google account I get the message about connecting to Google servers.
I did notice using adb logcat when I try to add a google account this message:
Code:
]02-02 18:13:48.903 5041 8347 E CheckinTask: Checkin failed: https://android.clients.google.com/checkin (request #0): java.io.IOException: Rejected response from server: invalid hardware identifier: "HTC 10 (unknown international)" is not a valid device

cumber said:
I just installed Lineage OS, and have exactly the same problem.
Code:
]02-02 18:13:48.903 5041 8347 E CheckinTask: Checkin failed: https://android.clients.google.com/checkin (request #0): java.io.IOException: Rejected response from server: invalid hardware identifier: "HTC 10 (unknown international)" is not a valid device
Click to expand...
Click to collapse
I've heard that different versions of Gapps will make a difference but I've tried them all... I have no Idea what to try. Are you on MM Firmwear?

Google apparently started rejecting devices with bogus device ids. I have changed, and will soon push, a change to fix that for lineage. Other ROMs will likely include all my changes in their next build.

b0rken touchscreen

Hi there,
I'm using an old lineageos 18.1 build.
I'm on hols, I just broke my screen, unfortunately it's not only the glass, it's the main touchscreen.
I'm still having access to the recovery and to the booting device with adb, but the device never finishes booting.
It keeps trying to setup the touch input.
08-12 18:23:26.171 10064 10064 I HidlServiceManagement: getService: Trying again for [email protected]::IGloveMode/default...
08-12 18:23:26.173 3960 10428 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IGloveMode/default": error code: 0x20
Click to expand...
Click to collapse
I'd like to use scrcpy from my computer to use the phone.
Any idea how to disable the touch input device init so the phone starts the main services ?

looks like removing vendor.lineage.touch from /etc/vintf/manifest.xml did the trick.
not very convenient to use a phone without a screen, that will do until I get back home