[I didn't realize there is this HTC Desire specific subforum, so I'm copypasting my question from General Q&A forum].
I've been running Miui happily for over a year on my HTC Desire, just to notice last week that wifi works only right after power-up (not reboot!) and until switched off. After that, it won't start again. I've tried different things, roms, clean installs, just to confirm the same behaviour, regardless of the rom installed. Detailed explanation is available here:
[EDIT: Being a new member, I'm not allowed to post links. So here it is, 'unlinked': http is.gd slash pZ1TDo ]
(includes logs and everything).
Please help, what to do next?
Thanks,
MB
When you have the error, open a terminal and type dmesg.
Please paste the output here.
You can redirect the output by typing "dmesg > /sdcard/file.txt" ( Without quotes )
dqb said:
When you have the error, open a terminal and type dmesg.
Please paste the output here.
You can redirect the output by typing "dmesg > /sdcard/file.txt" ( Without quotes )
Click to expand...
Click to collapse
Hello, thanks for reply.
Here's the output (too big for copypaste here):
http ge.tt (slash) 3nqEYdF/v/0?c
Sorry, still not allowed to paste links.
The bcm4329 module seems ok.
Sometimes when i use the widget to power on/off wifi, it won't connect.
To get wifi working, I go into wifi settings and power on the wifi here.
Could you try like this and tell us if this working ?
dqb said:
The bcm4329 module seems ok.
Sometimes when i use the widget to power on/off wifi, it won't connect.
To get wifi working, I go into wifi settings and power on the wifi here.
Could you try like this and tell us if this working ?
Click to expand...
Click to collapse
I tried all of the combinations - settings/wireless, status bar, specific widgets - nothing works. At least I have consistent behaviour
This is my original post on miui forum (when I thougt it was miui related). It explains what actions I performed while trying to nail the problem. Still no luck.
Code:
Hello,
Recently I've noticed that wifi on my HTC Desire is acting very strangely - it connects just the first time after reboot, every other time I get "Error" message in Wifi settings. Where I can check what actually went wrong?
After looking in the logs, I hope to have more information on this issue, but for now I believe it's hardware related, since the same problem appears even with the fresh install of the latest MIUI or after restoring a backup.
Thanks.
mblenton, Monday at 9:59 PM Edit Report
#1 Reply
Google Adsense
Pele
Admin
Message Count:
278
You can use the MIUI Android Logcat miuiandroid.com / community/link-forums/logcat.82/
Or you could try a fresh download install again : reboot into cwm, factory reset > wipe dalvik > clear cache partition install rom
But try the logcat and also check you router etc and other things that may influence.
Regards
If you require more help speak to ibotpeaches as he is a HTC expert : join the miui irc chat :)
MIUI Android Logcat System
MIUI Android Statistics
...Im all about the end user
Samsung Galaxy S I9000 & I9100 Expert
Black Android Theme Developer Website & Twitter
Pele, Monday at 11:34 PM Report
#2 Like Reply
mblenton
Members
Message Count:
7
Hello Pele,
Thanks for the reply.
I've tried already clean install with wiping everything, even restored an old bkp which for sure is correct, but all without luck. I don't think it's a router thing, since the same problem appears regardless of my location (at home, at work... all the same). I'll join the miui irc chat, good idea, thanks!
Regarding the logcat - the link you sent is just a form for pasting logs - am I seeing it correctly?. Is there some specific miui logcal app? I've installed 'aLogcat' which seems good, but I couldn't find anything on *wifi* or *wpa* which could indicate some sort of error in any of the logs aLogcat is displaying.
Cheers,
mblenton
mblenton, Tuesday at 9:30 AM Edit Report
#3 Reply
Pele
Admin
Message Count:
278
Hi,
Try to restore your back up without wifi settings. Failing that yes come to irc chat for about 12pm GMT+0 and chat with ibotpeaches
Regards
MIUI Android Logcat System
MIUI Android Statistics
...Im all about the end user
Samsung Galaxy S I9000 & I9100 Expert
Black Android Theme Developer Website & Twitter
Pele, Tuesday at 10:31 AM Report
#4 Like Reply
mblenton
Members
Message Count:
7
Hello Pele,
I've tried several combinations of rom/backup flashing, titanium backup restore etc. but the problem persists, even on a clean installation with just one accesspoint defined.
mblenton, Tuesday at 3:09 PM Edit Report
#5 Reply
mblenton
Members
Message Count:
7
Update: I've updated to the newest radio, but the problems are still there.
mblenton, Tuesday at 3:51 PM Edit Report
#6 Reply
iBotPeaches
Admin
Message Count:
569
Yes, you need a logcat to further figure this out.
developer.android.com / guide/developing/tools/logcat.html
Freenode #miuiandroid
iBotPeaches, Tuesday at 6:51 PM Report
#7 Like Reply
mblenton
Members
Message Count:
7
Hello iBotPeaches, thanks for the link, I didn't realize Pele's refering to that logcat. I'll have to set up abd, though.
In the mean time, I've tried the following (plus the actions described earlier):
- Format system and boot partitions (since Wipe Data/Factory Reset doesn't do that) and clean latest miui install
- Clean Cyanogenmod install
Nothing's changed, I still can connect to wifi network the first time after power up, and then all I get is 'Error' msg. Interesting, but reboot doesn't actually help, just power off/power on.
mblenton, Tuesday at 9:04 PM Edit Report
#8 Reply
mblenton
Members
Message Count:
7
Hello again,
I've installed adb and used logcat to generate this file: ge.tt /9UkgUaF/v/0?c
I'm not quite sure what would be interesting for debugging purposes, so I performed the following procedure:
0. Wifi is enabled, but not working; power down the device; start adb logcat - waiting for device -
1. Power on (wifi will be enabled and connected to SSID Hotspot)
2. Open browser, open google (everything works)
3. Close browser, turn off wifi (via status bar, but it doesn't make any difference)
4. Open settings, try to turn on wifi
5. Wifi couldn't be turned on, 'Error' message is displayed
6. Power down the phone
Thanks in advance!
mblenton, Yesterday at 10:36 AM Edit Report
#9 Reply
mblenton
Members
Message Count:
7
Yet another update, not I'm pretty sure this issue is not miui related.
I've installed Gingerbread RUU and performed the power-on/wifi-on--works/wifi-off--won't-start-anymore procedure with the same results. Here are the logs: ge.tt /9sOVXbF/v/0?c
Where I should look for help?
Ok, after you got the error, go in a terminal and type lsmod ( list loaded modules )
If you see the bcm4329 loaded ( wifi module ), go in a terminal and type modprobe -r bcm4329 ( unload module )
Verify with lsmod if the module is unload.
After that, try to activate the wifi in settings/wireless. Twice if the first gives you an error, it should "unload" the first time, and the second time it should load.
I just tested by inducing an error.
Tell us is this work !
Hello again,
I've tried what you suggested, and this is the result:
Issuing lsmod while wireless is OK:
bcm4329 200131 0 - Live 0xbf000000
After turning off wireless, lsmod doesn't display anything.
After trying to turn wireless back on, lsmod also doesn't display anything, regardless of the times I tried to turn wireless on (and getting Error every time is Settings)
modprobe bcm4329 returns
modprobe: 'bcm4329.ko': invalid parameter
insmod bcm4329 or bcm4329.ko says it can't open bcm4329 (.ko)
So, the linux system under the android seems to be working ok.
Hi,
Ok, after power off/on wifi, the driver doesn't load :/
With some tests and by inducing an error, it works on my side
When you have the error, try this as root :
Code:
su
lsmod ( if bcm4329 is loaded then rmmod bcm4329 )
svc wifi enable ( it's to turn on wifi manually, I waited a few seconds, and everything was properly unloaded ! And wifi off.. idk why )
svc wifi enable ( if the first time it didn't work, it worked for me, it might work for you )
svc wifi disable
but I've intentionally caused an error, not you. And i think that svc is the same as widget/settings..
BTW, for insmod you need to give the full path of the module : /system/lib/modules/bcm4329.ko and the fw path, but it will not work like that you need to set/config interface etc.. I'll try to do it manually.
I just looked quickly one of your old logcat because i'm tired and i'm going to sleep, I'll look more in detail this night if we can find the most important thing : what causes this problem.
dqb said:
Hi,
Ok, after power off/on wifi, the driver doesn't load :/
With some tests and by inducing an error, it works on my side
When you have the error, try this as root :
Code:
su
lsmod ( if bcm4329 is loaded then rmmod bcm4329 )
svc wifi enable ( it's to turn on wifi manually, I waited a few seconds, and everything was properly unloaded ! And wifi off.. idk why )
svc wifi enable ( if the first time it didn't work, it worked for me, it might work for you )
svc wifi disable
but I've intentionally caused an error, not you. And i think that svc is the same as widget/settings..
BTW, for insmod you need to give the full path of the module : /system/lib/modules/bcm4329.ko and the fw path, but it will not work like that you need to set/config interface etc.. I'll try to do it manually.
I just looked quickly one of your old logcat because i'm tired and i'm going to sleep, I'll look more in detail this night if we can find the most important thing : what causes this problem.
Click to expand...
Click to collapse
Hello,
Thank you for attepts to help me, unfortunatelly none of your advices haven't succeeded to turn on wifi once it was turned off. I don't know what to do next. I actually keep it turned on all the time, and it works OK. Not quite happy with that
Hi mblenton,
Ok
I just found how to really turn on the wifi manually.
First, in a root terminal run : getprop wifi.interface, I have eth0, if you have another interface, replace the following by yours.
After error, make sure your eth0 interface is down by running in a root terminal "netcfg" you'll not find eth0 interface, or "ifconfig eth0" must return " eth0: No such device " same for "iwconfig eth0".
If eth0 is up, run as root : "ifconfig eth0 down" and retry to turn on wifi as usual.. maybe it will work.
If not, make sure bcm4329 module isn't loaded ( lsmod ), make sure eth0 is down and try this :
Code:
su
modprobe bcm4329 firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin
start wpa_supplicant
dhcpcd -BKL eth0 &
If "modprobe bcm4329 firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin" return you an error, try this :
Code:
insmod /system/lib/modules/bcm4329.ko firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin
But it's better to load a module with modprobe.
What the commands do :
1) Be root
2) Is for loading module and firmware properly
3) Start wpa_supplicant as service with right user, and load your wireless config
4) Run dhcpcd on background for getting an ip by dhcp ( which implies not have configured the ip manually )
If the wireless icon is not activated in notification bar, it's normal.
ping -c2 google.com or open a browser and try a google search, it worked for me..
If it work for you, cool, we can make a bash script to get the wifi works temporarily, the time to found the cause of the malfunction !
A guy that I helped had a problem with bluetooth, it was a permission problem.. he found a fix :
Daiksi said:
with rom manager i did fix permission and IT WORKED!!!!!!!!YATTA!!!
Click to expand...
Click to collapse
Try that, it can only do good things !
Hello,
I've tried what you suggested, including permission fixing, and the situation remained the same. I'm surprized there's nothing in the logs, though.
Thank you once more.
I know my phone is deepsleeping, but for some reason, when i try to wake it, it would take up to a minute for any response, on top of that I found that android OS is using about 40% of my battery, used Android tuner( the one that requires xposed framework) to see, and it turns out that the battery drain was caused by the android os, "sh" thread.
Any ideas to fix this?
MinChains said:
I know my phone is deepsleeping, but for some reason, when i try to wake it, it would take up to a minute for any response, on top of that I found that android OS is using about 40% of my battery, used Android tuner( the one that requires xposed framework) to see, and it turns out that the battery drain was caused by the android os, "sh" thread.
Any ideas to fix this?
Click to expand...
Click to collapse
"sh" = shell
It seems that something installed on the phone is starting shell (it's a text terminal) in a background and not stopping it. It may be a broken script installed in /etc/init.d or some app that is broken. The worst case scenario is a malicious program that resides in background to do something (not very probable). It will be hard to find the cause as "sh" is a part of the system - please try to correlate the beginning of the problem to installation of some program. Try to use Teminal Emulator and issue the command "su", press enter, write "top -n 3" and enter, to list all tasks running in the system. Scroll up to check column headers, find CPU% and by that locate this rouge "sh" process. Look in column UID to find who has started it (user id). Post your search result.
Found it pid 32444 bu doesnt really help as i can lt find it activitymanager.runningappprocessinfo
Any idea what this is?
32444 2 24% R 1 896K 428K root /system/bin/sh
Rebooted, pid changed to 4790
Update:
After i killed this prpcess, swapoff takes over and causes an i/o storm for abour 2 mins then system ui and surfaceflinger uses about 30% and 20% cpu respectively it doesnt go down even after 5 hours.
Using agni kernel for 4.3 btw patched to fix network error
What cpu governor are You using?
Try to set ondemand.
Sent from galaxy n7105
Hi, i've got the following problem with my oneplus 3:
The phone is rooted! When i have to grant the permission for an app to acces the storage, i always geht the message "display overlay detectet". I have to disable the overlay off ALL apps to grant the access. I do not have lux installed, which causes this problem on many other phones. i have already wiped the device, which did not solve the problem. the problem is, that some apps need the overlay (facebook messenger). i have no idea how to solve it... maybe you guys can help
wow.... it just worked out, by deleting super user and rebooting the phone. i'll keep you guys updated, if the problem accours again