Related
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
I've seen similar issue with the screen staying awake, thought it's just the phone. Also not sure if it's related sometimes I'll click on a button for example, but it will almost not recognize the spot i'm clicking on and click something else on the screen.
These are the same problems I've been seeing on my phone. I imagine it is due to the multitouch hack, but I haven't gotten the motivation to downgrade my phone back to 1.31.
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Dharkaron said:
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Click to expand...
Click to collapse
Nope, I had installed Power Manager once a while back and didn't like how it worked so I uninstalled it. Don't have Locale installed either. I ran the task manager to see what was running and there was nothing that I could tell that would turn the wifi on.
The touch issues are rather widespread amongst 1.41 users. However, don't know what's up with ur wifi. I have a strange issue with my wifi as well though. Whenever I boot up my phone and wifi was enabled when it turned it off. I get 2 not responding errors. Everytime. Its like clockwork. With 3g? Never. It took me about 20 wipes and 10 or so hours to finally figure it out. Hopefully all these problems will be fixed with rc33
I have also noticed that Applications don't check for new updates anymore. even when I go to "My Downloads", It used to show "free" next to any application that has an update or has been uninstalled. Now it shows "Installed" next to all the applications but when I go to the application by category, It shows up as "Free" meaning that there is a new version.
the case in simple points:
1. when I open the Application..... It doesn't detect the update.
2. when I go to "My Downloads" in the market, It doesn't show "Free" next to any application that has an update.
But if I go to the application by category, It shows "Free".
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
i havnt had a problem with it staying on, i noticed that my phone was dimming to quickly. I know theres probably an adjustment somwhere (i think at least) but i havnt had any problems what so ever with it.
Very strange. I haven't had either problem (wifi or touchscreen). I have noticed that my battery drains more quickly than it used to, but I have been blaming this on the DroidSans autorotate feature always flipping the screen everytime I move the phone (I mess with the phone an awful lot).
Droidsan
I can not get auto rotate on JF RC-33. Does anyone have this problem???
another issue with with this version was that all my ringtones were changed for my contacts and stuff
pretty wierd.
i don't have any problems mentioned ATM.
JF RC30 to RC33
stonefurry said:
I can not get auto rotate on JF RC-33. Does anyone have this problem???
Click to expand...
Click to collapse
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
danguyf said:
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
Click to expand...
Click to collapse
What he said... But don't forget to enable auto rotate in your browser though. You don't need droidsans for that.
I use Froyo 2.1 build, after I press power key to turn off screen, if I press the power key again in short time, the device wakeup will take a long time (about 5 seconds), sometimes even not wakeup (due to timeout in the lockscreen and screen turns off again I guess), then I have to press the power key again and wait, normally it will take about 4 seconds to turn on the screen.
I tried to turn off setCPU and ATK completely, but not works, still long time to wake up.
is there a solution to this? everything works fine except this
thanks in advance!
I also have this issue. I tried many builds but there is always lag. No build will wake up so fast as WinMo but I think its the limitation of running OS from SD Card. Maybe I`m wrong but I think internal memory has lower latency so windows wakes up immediately and android always takes some time..
I want to know is there anyone do not have this long delay before wakeup? if there is, please tell me, thanks!
these are known issues and there is no fix , most of time things like this come
from human error
Yeah these are known issues with the Froyo builds. Will probablyget fix somewhere down the line.
The best thing to do now is to be patient with it. I find the more frustrated I get with it, the worse it gets. What I mean is if I keep hitting the hangup/unlock button to try to get it to wake, it takes longer to awake.
Also someone has posted that a possible problem is with Advanced Task Killer settings. If you have that program set to kill apps during sleep, it could cause a hang on wake. Also I believe auto screen rotate could have an effect.
I am sure that in time the situation will be resolved, as will every other minor bug and glitch.
The only solution I have foudn to this problem is to use shub 1.4c or d. It usualy turns on the first press, if it doesn't I press the button again(b/c usually the backlight goes on on the first press just nothing shows up on the lcd) then wiat a couple seconds and it goes on. I also have minimal TS freezes w. that build while with other builds they are common
disable autorotate. i had this even in shubcrafts builds, sometimes it woiult be within have a second, sometimes id see the screen power up but and go greyish, then a few seconds later id get the lock screen. from time to time, though i wouldnt get the lock screen and it just power down again.
since disabled auto rotate, its been pretty consistant at showing the lockscreen quickly.
The devs know about these problems, they are bveing worked on.
this is the major problem for me, but I still can not find it in any build's known bug/issue list, does the developer guys really know this? or it's only the problems shown in our devices?
If any of you have installed Battery Indicator, try to uninstall it and see if it help.
I used to have Battery Indicator to disable screen lock, after I uninstalled it, the problem is gone.
I have had the same issue with all the roms i tried ... but recently on shubcraft 1.5, i ve found out that when pressing the end key and that nothing shows on the LCD but the keyboard backlight is on, you can unlock as usual by doing the slide pattern on the black screen (you can feel it vibrate when you hit the spot before sliding).
Sent from my HTC HD2 using XDA App
I'm using FroyoStone 2.1 with kernel r9 and have the same issue.
I can confirm your finding that it's indeed the backlight that doesn't light up and unlock can be done anyway...
Dev's please fix this backlight issue...
BIG THANKS!
I had this annoying issue and tried almost all the builds and finally the build in the following link worked well. Note : This is a nexus ROM without sense and FM radio. Very snappy and no wakeup delay for me.
forum.xda-developers.com/showthread.php?t=773790
Yes, same here. Using mattc 1.1 clean
hate it.
I have this problem either , Shubcraft 1.5 , also during calls , sometimes it take more than 5 seconds to wake the screen after you take it off from your ear .
cecaa1030 said:
I use Froyo 2.1 build, after I press power key to turn off screen, if I press the power key again in short time, the device wakeup will take a long time (about 5 seconds), sometimes even not wakeup (due to timeout in the lockscreen and screen turns off again I guess), then I have to press the power key again and wait, normally it will take about 4 seconds to turn on the screen.
I tried to turn off setCPU and ATK completely, but not works, still long time to wake up.
is there a solution to this? everything works fine except this
thanks in advance!
Click to expand...
Click to collapse
Can you try waking up your phone with the YES/SEND key? (instead of power key)
Please provide feedback if this makes a difference.
memin1857 said:
Can you try waking up your phone with the YES/SEND key? (instead of power key)
Please provide feedback if this makes a difference.
Click to expand...
Click to collapse
Thx a lot.. The Call button wakes up the phone much faster than the default Power button.
Is is possible that a low memory situation can cause this? My HD2 was running perfectly then out of nowhere the long wake and wake screen freeze started to appear. I have been troubleshooting it for 2 days now. I just noticed that my available memory show in Taskiller was 109mb. I had seen that low memory situation before during a freeze period and not paid any attention to it. But I do know that after I reboot the phone its perfect again w/ 200+mb.
Anyone else notice this?
Has any progress been made on this matter in recent builds? Running shubcraft 1.5, and still having major troubles with it about 2 out 3 unlocks..
Try disabling any & all task killers, what I think is happening is that something gets killed when it shouldn't. I had the same issue to the point of going back to Winmo and as a last resort just disabled all those and then went with a static wallpaper (no live). The problem disappeared and now the battery last much longer.
Hello,
I recently noticed an issue with my wifi (stock 2.3.3), where an app that needs to update regularly didn't seem to be doing it when the screen was off. As the phone always sits on its dock when I'm at home, I "solved" the issue by making the screen never turn off.
However, today I decided to give SIPdroid another go, as I tested it when I first got my phone and it wasn't working properly. I found out why, the second I put the phone to my ear, the screen turns off and the sound cuts. If I take the phone away, I suddenly get all the audio high speed as it catches back up.
A bit of googling showed this to be a known issue, the wifi goes into power saving mode when the screen turns off - on SIPdroid there's an option to keep the screen off and it seems to work well, it just dims the screen instead. But that's still an unnecessary battery drain.
I had trouble finding any recent info on the issue (within the past 6 months), maybe I was just using the wrong keywords. So I thought I'd ask here. Does anyone know anything about this issue? Is it likely to be fixed in the next version of android if it ever comes to the desire HD? Maybe there's a fix out there already (preferably without rooting and/or installing custom rom, my phone is just right as it is now...).
Settings>Wireless & Networks>Wifi settings>Hit 'Menu'>Advanced>Wifi sleep policy>Never
That'll prevent the wifi turning off when the screen turns off.
Sent from my Desire HD using xda premium
I tried that before posting, it makes no difference whatsoever (besides, the sleep policy is either never or 15 minutes, this problem occurs the second the screen goes off).
If u re root: change radio... try anyone.
stock: mmm default reset to try. (i think)
No:
http://code.google.com/p/sipdroid/issues/detail?id=268
http://code.google.com/p/sipdroid/i...Status Priority Milestone Owner Summary Stars
Reading through the comments, it seems a more general android problem. A reset wouldn't fix it.
Also:
http://code.google.com/p/android/issues/detail?id=9781
Hello
I'm new to xda, so i couldnt post on the aurora 4.0.4 by dzo thread.
I couldn't read all replies but from what i've read many of those who have the aurora ics rom installed on their u8800 device seem to have noticed the grey wifi icon.
I found a easy way to turn it "blue" again, it seems to be working for me everytime.
You just need to lock your screen(when your wifi is grey), then to unlock try press and hold the lock button till the screen turn on, it should be blue again. I've seen many telling to reboot the device, reinstall the rom, but honestly none have worked, besides that, this is a simple solution.
By the way i have the latest version of aurora ics 4.1a, and i haven't experienced, till now, no bugs while i use the phone, besides the grey icon. Maybe the battery comsumption is a bit higher than the stock rom but no big deal for me.
hope it helped.
Closing wifi and opening after a few seconds works much easier.
Sent from my U8800
I tought so but for me just turning it off and on doesn't work, it stays with the grey icon, but with the procedure that i refer above everything seems to work great now. My first attempt to try to solve the problem was to turn off and turn on the wifi but it was the same...
Hi all,
I am experiencing the dreaded sleep of death on my Lenovo K1, I cant post in the android development section as I dont have 10 posts yet. I flashed the V2 CM10 via NVflasher and then updated to V6 via Clockword Recovery. I have checked that my Wifi is set to "Always on", I have not done a system restore so this is a clean device. This is now my 3rd flash of this image with the same problem(My previous JB AOSP worked fine). Does anyone have any idea what I can try next?
Thanks!!!
I'm having the same problem with my WiFi version of the K1. I have flashed krook1's build a couple of times and have tried setting the WiFi to Always on. I also have tried Better WiFi On Off and Soft Locker apps to manage the wifi and keep it out of deep sleep (both recommendations in the dev forum) but neither have helped. Every time my screen goes off, the device appears to continue functioning; I can hear notifications going off for emails or text messages. If I try to turn on the screen again using the power button, the two lights on either side of the home button will flash but the screen does not turn on. I then have to hold the power button down and boot up the device again. It doesn't matter if the screen times out or if I turn it off manually, it will always die immediately after.
Ne3M said:
Hi all,
I am experiencing the dreaded sleep of death on my Lenovo K1, I cant post in the android development section as I dont have 10 posts yet. I flashed the V2 CM10 via NVflasher and then updated to V6 via Clockword Recovery. I have checked that my Wifi is set to "Always on", I have not done a system restore so this is a clean device. This is now my 3rd flash of this image with the same problem(My previous JB AOSP worked fine). Does anyone have any idea what I can try next?
Thanks!!!
Click to expand...
Click to collapse
Hi,
I was experiencing the same issue, the Sleep of death, and would not wake up after turning the screen off or locking the device.
After a lot of testing without positive results, I found this app from the market:
https://play.google.com/store/apps/details?id=com.omd.autoscreenon
It allows to have a "Wake Lock" sensor on all the time, it drains battery a little faster (I haven't noticed much of a difference) which seems to have solve the wake up problem.
I've tried this app the whole day and I haven't had any SoD so far.
Hope this helps.