Problem: Screen Blackout - Buttons/Keyboard Unresponsive - Epic 4G General

The only thing I have done to this phone is root.
My phone several times today has had it's screen blacked out and cannot be awoken or used because all buttons on the phone become unresponsive. However, I know the phone is still working because it still receives notifications and I can hear it.
I have to take out the battery to fix this. Has happened about 5 times today.
Anyone else with this issue?

That certainly isn't normal. I would return it.

Also noticed that when using adb that it kicks my phone out after a certain time... something like 1 minute. Does this happen to anyone else?
I often have to do adb kill-server in order to see my device again.

I too have the same problem (though less frequently).
I have a rooted Epic using Joey Krim's method (raidagainstthecage-arm5.bin). I attributed it to the Overclock Widget which I have uninstalled to see if it gets any better. I like that widget for throttling down the CPU while the screen is off.
I guess it is best to start collecting data on this.
Phone was purchased at BestBuy.
Hardware version: D700.0.5
Anyone else seeing similar behavior? How about on a non-rooted Epic?

I was running SetCPU but uninstall the application and it was still happening to me. I have a feeling it has to do with the root method. My girlfriend's phone doesn't have root and it hasn't happened to her at all.
@jspielberg did you root via the one click method or manually with adb?

I rooted via adb.
Other root required apps installed:
Titanium Backup
Wireless-Tether Experimental (adhoc mode only working currently on the Epic it looks like)
Overclock Widget (now removed)
I think that is it for SU needed apps.

jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.

This happened to me not 30 minutes ago. And I'm 100% sure its root.
Sent from my SPH-D700 using XDA App

volcomjerk said:
jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.
Click to expand...
Click to collapse
I did indeed use my mac also for root via ADB...
I can't see how that would matter, but it is good data nonetheless.

Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.

antidelldude said:
Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.
Click to expand...
Click to collapse
Yeah everything is working fine. But I went to pick up the phone to make a call and it was dead. Complete blackout screen, not lights. Nothing.

@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.

I rooted Tuesday morning using Windows 7 32 bit mode, ran cmd as Administrator and followed Joeykrim's manual instructions.
I have had no problems with the screen being able to be turned back on and I have been on my phone performing various tasks for hours at a time.

volcomjerk said:
@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.
Click to expand...
Click to collapse
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App

ImSoHungry said:
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I rooted with One Click Root. Windows 7 32bit.

I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery

Is there a way to undo the "one click root" I did from the instructions here on XDA yesterday?

I rooted last night via OSX 64bit and have not experienced this issue. But now i am very afraid...

killahkosha said:
I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery
Click to expand...
Click to collapse
Wow, after doing a full reset without root I am not seeing problems yet but this post makes me worried that it's not just related to root or unrelated to root at all.

I did a full reset through the menu on the phone, I haven't tried doing one through the holding volume down while booting method but I will after work

Related

VISIONary and Temp Root Question

If I use the current version of VISIONary (r14) and ONLY temp-root my MT4G, will ANY residual effects be left once I reboot?
I remember when using VISIONary on my MT3G, it seemed to cause permanent changes even though I only used "temp" root.. eventually my phone seemed to have conflicts with apps and it never really "unrooted"
It's my understanding that VISIONary should be completely safe as it does not write to the system partition..?
Please move this to q&a......
From my don't talk about changelog CM7 Glacier
Anyone?? Need some advice here.
$pitacular1 said:
Anyone?? Need some advice here.
Click to expand...
Click to collapse
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
$pitacular1 said:
In the modaco forum I read earlier today that someone was having constant reboots from using VISIONary for temp root.
You said your wife's phone "had zero usability problems after a reboot". What about after temp-rooting, but before rebooting? Any issues there?
Click to expand...
Click to collapse
Nope she uses it all day everyday.
Thank you, much appreciated.
Temp-Root here I come!
Btw, is she using the latest version (r14) ?
Noticed no problems
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
ecdy said:
I've seen no problems after a reboot with Visionary r14. On another point, I had it originally set to automatically temproot after every reboot, but once I discovered that the programs that Titanium Pro freezes stay frozen after a reboot even if you're not temprooted, I no longer temproot. Have to use it, though, if I want to add/subtract frozen programs.
Click to expand...
Click to collapse
I wonder if that's normal. It was residual root-like effects like that I was wondering about.
neidlinger said:
VISIONary.apk was designed to only be used on the HTC Vision and the HTC Glacier.
Nandroot was designed to be use on the HTC Magic and HTC Dream. and later came the desktop client SuperOneClick.
If i didn't know any better the reason your Magic went FUBAR is because you used the wrong method and installed something that didn't belong.
But to answer your question my wife's phone is temp rooted with VISIONary.apk and she has had zero usability problems after a reboot.
Click to expand...
Click to collapse
On another note, I had previously experimented on my MT3G with Universal Androot which worked perfectly.. it was only later after the 2.2 update that I needed a root alternative as they had patched the exploits Universal Androot used to get root.. VISIONary was a perfect solution. The only problem is it resulted a permanent "partial" root instead of a temporary root or a full perm root. It was still an excellent tool to use for the job though.. nothing went "FUBAR" lol I was still able to SAPPIMG and then manually update to the official Froyo.
I was just curious if I was going to get the same perm root issue with the MT4G, as I have not yet familiarized myself with the process of restoring the 4G to stock although I am aware of PD15IMG.. just haven't read through the specifics. I swear I'm not a total noob I promise.. I've written tutorials on root for the MT3G
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
$pitacular1 said:
Ok, so last night I used VISIONary for temp root only..
Immediately after temp rooting, my phone started acting weird.. syncing extra long, everything was slow (even after the syncing).. it just seemed to be severly affecting the performance of my device.
I don't know if perhaps I have an active app it was having issues working with or what, all I know is without temp root my phone flies 24-7.
Once I rebooted, everything went back to normal. Don't think I'll be using VISIONary anymore
Click to expand...
Click to collapse
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
neidlinger said:
i guess you are one in a million who have experienced problems with VISIONary.apk.
I guess if you are that bent on rooting you can do it the old fashioned way.
Click to expand...
Click to collapse
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
$pitacular1 said:
Well last night when I first tried it, I had not enabled USB debugging..
So this morning, I tried it again, but made sure it was enabled the FIRST time lol..
and it's working flawlessly. I guess my initial idiocy caused something.. but it's fine now!
Click to expand...
Click to collapse
That's cool. Glad to hear it is working.

[Q] Phone won't turn on.

So I updated some apps on my phone, handcent and flash and my phone was having a lot of FC issues. Handcent was FCing for a lot of things and I couldn't open almost any app. So I figured lets do a quick reboot....chose the reboot option and the phone turned off but never came back on.....pulled the battery and I've left it out but still no go. Even pulled the memory card and SIM card but the phone won't do anything. Won't show charging when I plug it in but my computer does make a noise when it plugs in but the device doesn't show up on the computer anywhere.
Am I toast and do I need to get a new phone or is there something that I can do?
Wow never heard of that happening.. hmm try going to the bootloader... get a new battery maybe... this beats me
mytouch 4g
S-off
gfree method
running: royal ginger 1.6
How do I get to the boot loader from hardware keys? I can't for the life of me find that.
Never mind, located how to get to the bootloader......doesn't work...the phone won't do anything.
Spectral8x said:
Never mind, located how to get to the bootloader......doesn't work...the phone won't do anything.
Click to expand...
Click to collapse
If you are certain your battery is good and your phone does not respond to anything AKA brick then I think somehow you have ended up with a corrupted bootloader if that is the case you'd need a RIFF box or call HTC. I'm in the same boat as you i won't be buying the JTAG cable for that phone only so i'll be sending mine in.
I highly doubt it's the battery it was fully charged and never had any issues and then I updated these apps, got some FC issue and then the phone wouldn't turn back on after a reset.
Spectral8x said:
I highly doubt it's the battery it was fully charged and never had any issues and then I updated these apps, got some FC issue and then the phone wouldn't turn back on after a reset.
Click to expand...
Click to collapse
is adb recognizing your device? you did mention you heard a noise on your pc. The usb drivers should be kicking then (pray its not the qualcomm modem drivers kicking in lol)
you still have hope if you can get adb up and running.
Also were you on the stock bootloader or eng bootloader?
1. What was the state of your phone before those app updates? (Rooted? Custom ROM / kernel? Engineering bootloader?)
2. Do you remember specifically which apps you updated? Anyone else who updated the same apps recently, have you noticed anything?
3. Do you have ADB set up on your computer? Have you tried using 'adb devices' to see if your device is recognized?
Happen to me once due a battery pull then reinsert the battery should be able to boot back up. When you do a battery pull wait a few minutes like 5.
Sent from my HTC Glacier using XDA Premium App
That happened to me everything got messed up except bootloader and even that was freezing so I loaded pd151img.zip and pulled battery when updating bootloader to hide s-off
Sent from my HTC Glacier using XDA Premium App
So before updating the apps I was running CM 7.0.2 with Faux123 2.5.2 Gingerbread Kernel. The only 2 apps I remember for sure were Handcent and Flash. I think there may have been one other tho. I don't know how much abd is recognizing the device because I just got this lap top and my other one I used to root it and had abd on won't boot up....just my luck right? I am going into work today and my buddy has it on his laptop so we will see if we can recognize it there.
And as far as just pulling the battery...that isn't working I life it out for 6 hours and it still wouldn't boot up, normally or into download mode.
Spectral8x said:
So before updating the apps I was running CM 7.0.2 with Faux123 2.5.2 Gingerbread Kernel. The only 2 apps I remember for sure were Handcent and Flash. I think there may have been one other tho. I don't know how much abd is recognizing the device because I just got this lap top and my other one I used to root it and had abd on won't boot up....just my luck right? I am going into work today and my buddy has it on his laptop so we will see if we can recognize it there
And as far as just pulling the battery...that isn't working I life it out for 6 hours and it still wouldn't boot up, normally or into download mode.
Click to expand...
Click to collapse
Well if it wont boot it won't be recognized I don't think.. and I just corrupted the bootloader by pulling the battery so they wouldn't see I had rooted and I wouldn't have to pay the fee (bad karma and all I know) so if you don't have insurance your sol. But on some other thread a Guy had this issue and held both volume keys and power while plugging it in and his comp recognized it as qualcomm cdma device or something like that. That maybe recognizable via adb not sure though..
Sent from my HTC Glacier using XDA Premium App
Well I should be fine under warranty tho since the device won't do anything. I'm going to try to see if I can get the device to show up in adb and if not i guess i'm getting a replacement phone and starting from scratch UGH! Lol.

[Q] Random restarts: how to tell cause?

Hi all,
My MS2 has been randomly restarting and was wondering if it (or Android in general) has a way to see what happened directly before the restart, or more helpfully, what actually caused it to restart?
It hasn't restarted on me while I use it, but seems to restart when it's just sitting around and hasn't been used for a while (ranges from 10 mins or a couple hours) - I know it restarts only by the vibrator going off a little as it boots back up.
The phone is running the stock ROM, and I don't recall installing any new apps recently that may be causing it (such as system apps or anything etc, but NFI really).
Any and all help much appreciated!
Edit: "vBulletin Message Sorry, search is temporarily unavailable. Please try again in 20-30 minutes." in before flames.
So I'm not going to read through pages and pages of posts to find one specific issue which may/may not have been asked etc.
mine restarts 4 out of 5 times i reboot, its really annoying
still dont know the cause, does it with both stock and argen2stone, so it seems like hardware
normally it boots properly when its cold
dont know if this has any relevance... but yeah
weird. im using stock 2.2 AsiaRetail firmware and i have never experienced such a problem - random reboots. perhaps you have some sort of very buggy software that you installed, or perhaps you tampered with something after rooting your phone (if you did)? in any case this is very odd, as it should not just reboot out of the blues. do check each and every downloaded software to see if that is the cause.
I don't have the same problem with UK 2.2.2 running on it.
But random restarts do exist when I was using Argen2Stone 1.8, so I don't think this is hardware problem?
agent008my said:
weird. im using stock 2.2 AsiaRetail firmware and i have never experienced such a problem - random reboots. perhaps you have some sort of very buggy software that you installed, or perhaps you tampered with something after rooting your phone (if you did)? in any case this is very odd, as it should not just reboot out of the blues. do check each and every downloaded software to see if that is the cause.
Click to expand...
Click to collapse
actually, my phone was being pretty stubborn when i tried to root it. had to do a few battery pulls cos it never finished rooting, just kept spinning and spinning. Ive done factory restores with sbf's too, didnt seem to fix it?
I had reboots, but only very few. Not worth mentioning but it occured when I restarted the phone once. It seems to be faulty software.
Sent from my MotoA953 using XDA App
scottyn said:
actually, my phone was being pretty stubborn when i tried to root it. had to do a few battery pulls cos it never finished rooting, just kept spinning and spinning. Ive done factory restores with sbf's too, didnt seem to fix it?
Click to expand...
Click to collapse
what do u mean by stubborn when you tried rooting it? if your phone is still rooted, try unrooting it and see if the problem still exists
agent008my said:
what do u mean by stubborn when you tried rooting it? if your phone is still rooted, try unrooting it and see if the problem still exists
Click to expand...
Click to collapse
stubborn in that z4root wouldnt finish no matter how long i left it. took forever, so i had to reset or batterypull. had to do that about 3 times before the process actually finished
might try unrooting it, such a hassle *sigh*
ill get around to it when exams finish
scottyn said:
stubborn in that z4root wouldnt finish no matter how long i left it. took forever, so i had to reset or batterypull. had to do that about 3 times before the process actually finished
might try unrooting it, such a hassle *sigh*
ill get around to it when exams finish
Click to expand...
Click to collapse
I couldn't root stock 2.2 asia retail with z4root. Try superoneclick. It worked for me
Sent from my MotoA953 using Tapatalk
scottyn said:
stubborn in that z4root wouldnt finish no matter how long i left it. took forever, so i had to reset or batterypull. had to do that about 3 times before the process actually finished
might try unrooting it, such a hassle *sigh*
ill get around to it when exams finish
Click to expand...
Click to collapse
u should have used one click when z4 didnt work. i tried z4 several times, and when it just didnt root i tried one click instead. btw it really is no hassle unrooting. just click unroot on z4 if that does solve the problem, try re-rooting it, but use one click instead. i believe ur set has the RageAgainstTheCage loophole sealed too
agent008my said:
weird. im using stock 2.2 AsiaRetail firmware and i have never experienced such a problem - random reboots. perhaps you have some sort of very buggy software that you installed, or perhaps you tampered with something after rooting your phone (if you did)? in any case this is very odd, as it should not just reboot out of the blues. do check each and every downloaded software to see if that is the cause.
Click to expand...
Click to collapse
Yeah I suspect it might be a downloaded app (hoping so anyway) but I dont want to have to uninstall everything or try a trial'n'error uninstallation process as that will take forever.
I was hoping someone would know if there are logs that show kernel panics or last processes run prior to the reboot...
Sent from my Milestone 2 using XDA app
Bump
Sent from my Milestone 2 using XDA app
I was experiencing some stuck and random reboots when I was using 2.2 with my class 10 sd card, so I decided to try the 2.2.2 sbf, and it kept the same behavior, them i saw the thread about problems with high speed cards, and since i saw it i'm using the original card and experiencing no more stuck or reboots.
Sent from my A953 using XDA Premium App
lucasdss said:
...i'm using the original card and experiencing no more stuck or reboots.
Sent from my A953 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the reply, but im still using the SD card that came in the phone
Sent from my Milestone 2 using XDA app
cobo_ said:
Thanks for the reply, but im still using the SD card that came in the phone
Sent from my Milestone 2 using XDA app
Click to expand...
Click to collapse
try using lookout security (free)...just to see if any apps you have downloaded are contain malwares. i also heard such reboots can be caused by external wifi scanning/searching apps.
Thanks I might try lookout and see what it says...is itself trustworthy tho?
Also I dont use wifi and have it disabled.
Can anyone else offer any further suggestions?
Sent from my Milestone 2 using XDA app
bump...anyone know if MS2 has kernel logs or sth to help me narrow down these random restarts?
I didn't meet with random restart problem at all. using uk 2.2. only once it restarts again and again, and that turned out to be caused by my battery.
sometimes when my tombstone is too hot (above 48℃), it will shut down automaticly to cool down itself. and my battery reports a wrong value of current temperature to system sometimes, then cool down mode will be startup and shut down my phone.
Sent from my Milestone 2
cobo_ said:
bump...anyone know if MS2 has kernel logs or sth to help me narrow down these random restarts?
Click to expand...
Click to collapse
Type dmesg and logcat on terminal.
Also, download live dmesg and live logcat from market, they are bootanimations with live logs apearing on the screen. Pro version suports both at the same time.
Sent from my Milestone 2 XDA App
dangpzanco said:
Type dmesg and logcat on terminal.
Also, download live dmesg and live logcat from market, they are bootanimations with live logs apearing on the screen. Pro version suports both at the same time
Click to expand...
Click to collapse
Awesome thanks for this! I wasn't sure what stuff came with android re unix utils so these will come in handy
Sent from my Milestone 2 using XDA app

Acer Solution for WiFi Issue

Anyone experiencing the endless loop WiFi situation, here is the solution from Acer level 2 support.
The resolution is to do 2 hardware resets in a row. While the tablet is on, and you are at the homepage, use a paperclip and push it into the hole under the full sized USB socket to reset the tablet. Allow the tablet to boot up and when it is completely restarted and you are back at the homepage press the reset button one more time.
When the tablet comes back up again you will have WiFi again and you should not have any problems going forward.
BTW, this has only been tested and verified on a STOCK tablet.
I have stock 100%. This did not work for me nor several others.
Sent from my A500 using XDA Premium App
I'm trying this right now as this problem just reared its ugly head... I'm not exactly stock, but I'm back to a stock Acer ROM after dabbles with VirtuousGalaxy (loved it) originally in hopes of getting the official OTA update. I'm so mad too, cuz I was just about to finally buy Titanium Backup so that I could play with ROMs more easily and not have to reinstall 100+ apps one-by-one...
Luckily, I took so long to ramble that all out that I'm almost done with both resets...
Survey says... no go... it's still just looping from Obtaining IP Address back to reconnecting, and I've tried connecting to multiple networks, even a mobile hotspot, even totally reconfiguring my router and to no avail... amazing how useless this thing becomes once it's severed from the net.
What the hell i have the same issue. This morning perfect tablet. This afternoon while at work turned into a POS...
Question?
If i hit the reset button do i loose all apps and stuff? I really dont want to loose anything since i have SOOO many apps I cant get back for free (amazon) and or all the 4-5 weeks of game play... yes constant game play including my kids.
update...just googled and YEP loose it all. Looking for other solution. WTF... Soo pissed right now
dasudevil said:
update...just googled and YEP loose it all. Looking for other solution. WTF... Soo pissed right now
Click to expand...
Click to collapse
You are mixing up a factory reset with the normal hardware reset.
The hardware reset by using the reset "button" on the bottom right of the tablet just reboots the hardware, very much like the reset button on a standard PC. Your apps and data will not be touched.
if you could get hold of the .40 update, it contains a file called fixwifi which could possibly help you.
Or, if you are rooted,
- Switch off wifi in the settings.
- open a shell and remove those two files:
$ su
#rm /data/misc/dhcp/dhcpcd-wlan0.lease
#rm /data/misc/dhcp/dhcpcd-wlan0.pid
- and switch wifi on again.
It might help. :-/
why dont you just root and back up your games and apps with titanium...than un-root it...
why not
dasudevil said:
What the hell i have the same issue. This morning perfect tablet. This afternoon while at work turned into a POS...
Question?
If i hit the reset button do i loose all apps and stuff? I really dont want to loose anything since i have SOOO many apps I cant get back for free (amazon) and or all the 4-5 weeks of game play... yes constant game play including my kids.
update...just googled and YEP loose it all. Looking for other solution. WTF... Soo pissed right now
Click to expand...
Click to collapse
why dont you just root and back up your games and apps with titanium...than un-root the tablet..if you want im just saying
_tachy_ said:
You are mixing up a factory reset with the normal hardware reset.
The hardware reset by using the reset "button" on the bottom right of the tablet just reboots the hardware, very much like the reset button on a standard PC. Your apps and data will not be touched.
Click to expand...
Click to collapse
Thanks and i could be. I always thought when hitting reset like that was resetting the device back to stock. I trust you guys at this stuff. I went technology stupid a few years back.
zoubidou said:
if you could get hold of the .40 update, it contains a file called fixwifi which could possibly help you.
Click to expand...
Click to collapse
would i not need to be rooted to apply this update?
caz70 said:
Or, if you are rooted,
- Switch off wifi in the settings.
- open a shell and remove those two files:
$ su
#rm /data/misc/dhcp/dhcpcd-wlan0.lease
#rm /data/misc/dhcp/dhcpcd-wlan0.pid
- and switch wifi on again.
It might help. :-/
Click to expand...
Click to collapse
I seen that, I am not rooted and the adb thing scares the crap out of me. I had issues back in the day with a MyTouch 3G (gold card crap)
youngv408 said:
why dont you just root and back up your games and apps with titanium...than un-root it...
Click to expand...
Click to collapse
To be honest I have lost all faith in my rooting ability. See above post on why.
Would love to get back into rooting things (MT Slide, MT4G, A500) but knowing my past experiences i would mess things up so bad its not save able. I was out of a phone for a week and had to pay someone to fix it. I dont think i can go through that again
Update: Cool it worked I had to turn off the lock screen first and after 6 resets I still have everything. Thank you for your patience and time.
caz70 said:
Or, if you are rooted,
- Switch off wifi in the settings.
- open a shell and remove those two files
$ su
#rm /data/misc/dhcp/dhcpcd-wlan0.lease
#rm /data/misc/dhcp/dhcpcd-wlan0.pid
- and switch wifi on again.
It might help. :-/
Click to expand...
Click to collapse
So weird to see this thread... I had this exact problem last night. I did a wipe and reinstall,and everything fixed itself. I'm glad you posted this because I figured it was a software problem. I'll give it a shot the next time it happens.
i Can confirm this worked after the second reset.... rooted using virtuous Picasso 1.0.8
All I have to do is forget the network and then just connect again...works every time for me
Sent from my A500 using XDA Premium App
caz70 said:
Or, if you are rooted,
- Switch off wifi in the settings.
- open a shell and remove those two files:
$ su
#rm /data/misc/dhcp/dhcpcd-wlan0.lease
#rm /data/misc/dhcp/dhcpcd-wlan0.pid
- and switch wifi on again.
It might help. :-/
Click to expand...
Click to collapse
I ran into the wifi scanning loop a couple of days ago.
It seems a bit extreme to go the hardware reset route.
I suspect most of us following the dev forum are already rooted and can do something similar to what I did.
I poked around with root explorer, blew out the dhcpd files, and hot booted.
Wifi is fine now.
Sent from my A500 using XDA Premium App
bleez99 said:
I poked around with root explorer, blew out the dhcpd files, and hot booted.
Wifi is fine now.
Click to expand...
Click to collapse
rebooting isn't necessary if you turn off wifi before deleting the files. in the process list there are two dhcp related processes
$ ps | grep dhcp
root 177 2 0 0 ffffffff 00000000 S dhcp_sysioc
dhcp 22869 1 900 444 ffffffff 00000000 S /system/bin/dhcpcd
i guess the dhcp_sysioc is controlled by android and that process in turn starts and stops the unix dhcp process. both are stopped when wifi is switched off in the settings.
when it's stopped the dhcp files are left. so either the dhcpcd process is killed with -9 or it doesn't handle the signal properly...
Hardware rebooting twice worked for me. I am running Picaso version 1.1.0 HC3.1
Thanks for all the suggestions everyone!
caz70 said:
Or, if you are rooted,
- Switch off wifi in the settings.
- open a shell and remove those two files:
$ su
#rm /data/misc/dhcp/dhcpcd-wlan0.lease
#rm /data/misc/dhcp/dhcpcd-wlan0.pid
- and switch wifi on again.
It might help. :-/
Click to expand...
Click to collapse
This worked great. Also you can use root explorer to navigate to same folder and remove thase files without adb
Sent from my SCH-I500 using XDA Premium App
I have tried this out on 2 machines we have an it has worked and I have not looked back since. I don't understand why someone with a stock unit would have an issue but you never know.
I just got this tablet yesterday. I flashed Acer_A500_4.010.22_COM_GEN1 from http://forum.xda-developers.com/showthread.php?t=1159443.
Last night and today WiFi worked great. Today out of nowhere I cannot connect to WiFi. It loops from obtaining IP address to reconnecting etc.
I tried to 2x reset method, this did not work.
I did root last night, but i didn't install terminal emulator or root explorer yet. dammit. so i'll have to get the APK's from my phone and put them plug the tablet into my desktop to get them.
Hopefully manually deleting the dhcp file fixes it.
I would really love the latest OTA that fixes the wifi issue
EDIT:
I got term.apk and pushed it, ran it, manually deleted the 2 files as mentioned, all working...for now.
caz70 said:
Or, if you are rooted,
- Switch off wifi in the settings.
- open a shell and remove those two files:
$ su
#rm /data/misc/dhcp/dhcpcd-wlan0.lease
#rm /data/misc/dhcp/dhcpcd-wlan0.pid
- and switch wifi on again.
It might help. :-/
Click to expand...
Click to collapse
That worked, with Root Explorer i didn't even have to terminal it. thanks hombre.

[Q] CM7: Wireless off on boot - how to fix?

I searched and found nothing like this.
When I boot my Nook Color, running Cyanogenmod 7, any recent nightly, wireless is off, even though it was on before booting.
I open Notifications, tap the wireless, it turns on and works fine. I've checked, airplane mode is not on.
Updating to newer nightlies doesn't work. I'm pretty sure this used to work. My glacier doesn't have this behavior.
Any thoughts on how to fix this so the wireless state is retained over boots?
I have the same thing but I actually prefer it this way since I use it so much for reading.
I think those lately night builds have screwed up a few things such wireless OFF on boot. Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.
votinh said:
I think those lately night builds have screwed up a few things such wireless OFF on boot.
Click to expand...
Click to collapse
Ah, thanks. I suppose I can't file a bug since it is a nightly, I'll mention it on the appropriate thread and hope.
Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.
Click to expand...
Click to collapse
Press the menu key, then "Reset term".
Yeap, that's another less painful way to close T.E.
Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Click to expand...
Click to collapse
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.
excarnate said:
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.
Click to expand...
Click to collapse
It should not be blue. Tap on it and it should turn gray. Problem solved.
Sent from my LG Optimus V using Tapatalk
Is there an actual answer for this issuer? Is this designed by the CM7 team?
thereddog said:
Is there an actual answer for this issuer? Is this designed by the CM7 team?
Click to expand...
Click to collapse
It's an Android problem. Something to do with missing radios. Happens on the touchpad too.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Definitely not a nightly problem, it's that way in the official release too.
Sent from my NookColor using xda premium
Some smart CyanogenMod users fixed this problem. Perhaps their methods would work for you as well as they worked for me.
I guess we just have to avoid accidentally enabling airplane mode.
I actually prefer wifi off on boot as I don't need it most of the time and it just drains the battery.

Categories

Resources