Well, my streak on 2.1 was doing this for a while but not anymore after a reboot: When the screen time out kicked in, the screen would not turn off, instead it would dim the screen but I could still see the Beautiful Home Clock. You still need to hit the power button to unlock the phone. Anyone know how I can enable this feature again?
makanouchi said:
Well, my streak on 2.1 was doing this for a while but not anymore after a reboot: When the screen time out kicked in, the screen would not turn off, instead it would dim the screen but I could still see the Beautiful Home Clock. You still need to hit the power button to unlock the phone. Anyone know how I can enable this feature again?
Click to expand...
Click to collapse
I have the exact issue. I am running 2.1 on att dell streak.
At first I thought i fixed it, i turned the style lock feature off. it started to turn dark for a couple hours then reverted back to doing the dim on lock.
i sometimes have issues d/c calls because its dim and un-responsive.
I have dont alot of searching on this matter and dont know what to think.
I also have this problem... reading over at modaco, there's a bunch of other people with the same problem. They're saying if you turn off wifi before locking the phone, it doesn't occur. Mine only seems to have the problem every once in awhile though, so I haven't been able to test it myself yet. You might want to try it and see what happens.
Ah ok, i went back and searched and found the post you were talking about.
i would post the link but new users cant link, its under 2.1 bugs in modaco streak forums.
Too bad that turning wifi off for me isnt really an option because usually it wont let me turn it back on
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'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
I had this on bangsters 1.2, but haven't seen it on 1.3b, but only been running that build for a few days.
azzzz said:
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
Click to expand...
Click to collapse
i had this a few times before on a shubi build. I came to the conslusion that it is the screen not fully coming out of sleep. Seeing as it only happened when I put the phone to sleep and then tried to wake it immeadiately or got frustrated and impatient with it and tried tapping buttons repeatedly until the screen came on.
palosjr said:
i had this a few times before on a shubi build. I came to the conslusion that it is the screen not fully coming out of sleep. Seeing as it only happened when I put the phone to sleep and then tried to wake it immeadiately or got frustrated and impatient with it and tried tapping buttons repeatedly until the screen came on.
Click to expand...
Click to collapse
I had this same experience. Patience is a virtue with these phones. As long as I wait if its taking a bit to come out of sleep, I get zero problems.
Sent from my HTC HD2 using XDA App
thanks for the advice. I hope its just a software glitch. I will just have to be more patient when coming out of sleep.
My solution
azzzz said:
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
Click to expand...
Click to collapse
Here is my solution, i posted it in a similar thread, I think the key element here is the bsb tweaks part, hope it helps, thanks:
I solved this problem in my phone.
even turn on/off/on/off/on/off etc the screen, the devices wakes up correctly every time.
I don't really what exactly fixed but.
i installed Miris romm 20.0, then i turned off the auto screen off *start/system/power, so the screen nevers dims or turn off. I turned off the charge the device when it is connected to the computer, turned off quiet pickup, turned off 3g.
and now i think this is the key, installed bsb tweaks and turned off everything(even power savings), disable data connections and screen rotation, I only left use high glymp cache. reboot and run android, in winmo i dont have anything installed besides bsb1.6
in android i have the task killer on and set cpu at 768mhz ondemand. no profiles. battery last well over 24 hrs moderate use. by the way im using shubcraft, and the gsensor disabled kernel. thanks,
edit: also my auto sync is off in android and my wifi is always on.
I dealt with the problem by putting a widget to control screen brightness on my home page, if it goes dim I can find it ' blind'
Sent from my HD2 on mattc froyo sense.
Yeah it does happen to me if I'm being impatient and banging on the screen before it fully wakes up. Haven't found a real solution yet, but so far I would just try my luck by turning on/off/on/off several times, hoping that it get stucks momentarily again to let if "fully" wake up. Worst case scenario, reboot.
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
prerunnerseth said:
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
Click to expand...
Click to collapse
When I use the power button on the back of the phone instead of the knock-on, I had this same problem. I was rooted but on stock rom. I've read other posts about the same problem. I would try to put in my pattern and midway through the screen turns off. Sometimes it would be two seconds, sometimes like 10. Don't know what the problem was.
My knock-on feature was barely working. Some guy recommended getting this case: http://www.amazon.com/gp/product/B00FEQU1NG/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1
I needed one anyway so I got it. Haven't had an issue with the knock-on feature anymore. No idea why haha but whatever, it works. Kind of a ghetto workaround.
I'm having the exact same issue.
Factory reset several times, installing my usual apps or having just the default apps without updating them didn't make any difference.
After a factory reset I disabled the knock knock feature and still, when I try to bring my screen up and unlock, it immediately shuts off, preventing me from swiping.
Another side effect is, when I make a phone call, the screen immediately goes blank and it will never turn back on unless I restart by holding on to the power button, this is especially inconvenient when I need to dial some options (i.e.) voice mail options, corporate automated options.
All of the above happened while I had my Incipio feather shine case. (incipio.com/cases/smartphone-cases/lg-smartphone-cases/lg-g2-cases/lg-g2-cases-verizon/feather-shine-case-for-lg-g2-verizon.html) I took the case off and did another factory reset last night, and so far the knock-on rate has improved from 0% to at least 60-70%... Strangest thing.... If anyone else can shed some light onto what the hell happened/is happening, I'd really appreciate it! It's been a frustrating ride since this problem surfaced about a couple weeks ago. I had this phone for about 2 months now....
I'm having this problem too. It happens with both knock on and power button wake. I have noticed that the screen is not actually immediately turning off, though. In a completely dark room, I can still see faint outlines of my lock screen. Then, after the brief time out for dimming, the screen will go to its dimmed brightness (which is far brighter than what's concurring after waking the phone). I'm able to unlock, reboot, and usually that will solve the problem for a little while, but this is getting frustrating.
Stock rom, rooted, TWRP, Nova Launcher, and xposed. I'm not sure what's causing this.
I know it's been said many times but if you block the sensors with your fingers after waking the device, your screen will turn back off. Its a security feature/bug and I would assume this is what's happening here.
I ended up getting a certified-like new replacement from verizon... While I had the old one, I did a test with that sensor you're talking about and it didn't really make a difference. I made sure the sensor area was clean without anything covering it and the problems persisted. I really hope LG can find the root cause of this and fix it... Very frustrating.
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
yonba said:
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
Click to expand...
Click to collapse
exactly. the sensor in very sensitive to being covered. Because its hypersensitive and having undesireable effects I would consider this a bug since it is buggy.
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Having this issue with my G2, its very annoying. Knock on does not work and screen shuts off after about half a second that I press the power button. Had to reflash to stock the first time this happened and fixed it but after about a month the same problem occured. I could however open by pressing one of the volume button together with the power button.
Hoping to find permanent fix for this problem.
thirtynation said:
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Click to expand...
Click to collapse
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
bigiuly said:
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
Click to expand...
Click to collapse
Please tell me where to find these settings
taqikazmi said:
Please tell me where to find these settings
Click to expand...
Click to collapse
Settings / Led Control
bigiuly said:
Settings / Led Control
Click to expand...
Click to collapse
There is no option in settings like LED.
taqikazmi said:
There is no option in settings like LED.
Click to expand...
Click to collapse
In settings of Lightflow app
bigiuly said:
In settings of Lightflow app
Click to expand...
Click to collapse
I installed the app and fund the settings but all of them are already unchecked
I have a Galaxy Note 3 running stock firmware on TMobile. It is not rooted or anything special.
I'm running into an issue where whenever it boots up, it comes up quickly, but Bluetooth and Wifi are not enabled (even though they were before when it shut down). Also, the screen lock button doesn't do anything, so there's no way to lock the screen. If I hold down the screen button, it does bring up the Power menu, so I know the physical button is fine.
If I just sit and wait, Bluetooth and Wifi do eventually come on, but it could take hours. Alternately, if I just hit the home button and lock button a lot in no particular order, eventually the lock button will randomly work, and the screen will lock. When I unlock the screen, I can see Wifi and Bluetooth coming on. Somehow the lack of a functional lock screen button and the wifi and bluetooth not turning on are tied to eachother, but I don't really understand why.
Tonight my phone was being a little laggy, so I restarted it, and I wasn't thinking about this bug so I just put it in my pocket while it rebooted. It started up, but since I wasn't paying attention to it I didn't get the lock screen working and the wifi and bluetooth on. When I finally pulled my phone out about an hour later the battery was at 8%. I looked at battery stats, and the battery use is attributed to
Android OS 28%
Media Server 27%
Android System 12%
Screen 8%
Those stats make me think something is getting all hung up when it boots up and causing the OS to just spin and burn battery.
Any ideas? I don't even know where to start. I've googled a lot but it's hard trying to figure out what the right phrase is, since most of my googling results in people who don't like their lock screen or can't get their wifi to connect.
Thanks in advance
J
jeffderek said:
I have a Galaxy Note 3 running stock firmware on TMobile. It is not rooted or anything special.
I'm running into an issue where whenever it boots up, it comes up quickly, but Bluetooth and Wifi are not enabled (even though they were before when it shut down). Also, the screen lock button doesn't do anything, so there's no way to lock the screen. If I hold down the screen button, it does bring up the Power menu, so I know the physical button is fine.
If I just sit and wait, Bluetooth and Wifi do eventually come on, but it could take hours. Alternately, if I just hit the home button and lock button a lot in no particular order, eventually the lock button will randomly work, and the screen will lock. When I unlock the screen, I can see Wifi and Bluetooth coming on. Somehow the lack of a functional lock screen button and the wifi and bluetooth not turning on are tied to eachother, but I don't really understand why.
Tonight my phone was being a little laggy, so I restarted it, and I wasn't thinking about this bug so I just put it in my pocket while it rebooted. It started up, but since I wasn't paying attention to it I didn't get the lock screen working and the wifi and bluetooth on. When I finally pulled my phone out about an hour later the battery was at 8%. I looked at battery stats, and the battery use is attributed to
Android OS 28%
Media Server 27%
Android System 12%
Screen 8%
Those stats make me think something is getting all hung up when it boots up and causing the OS to just spin and burn battery.
Any ideas? I don't even know where to start. I've googled a lot but it's hard trying to figure out what the right phrase is, since most of my googling results in people who don't like their lock screen or can't get their wifi to connect.
Thanks in advance
J
Click to expand...
Click to collapse
Why you dont flash again your original firmware via odin ? If a software problem i think need be solved.
zelenko said:
Why you dont flash again your original firmware via odin ? If a software problem i think need be solved.
Click to expand...
Click to collapse
Well, I figured I'd ask to see if other people had seen this before first.
jeffderek said:
Well, I figured I'd ask to see if other people had seen this before first.
Click to expand...
Click to collapse
First try hard reset, then flash if that dont help.
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
LOL I have the same problem, which is extremely irritating to say the least, but I had no idea that it had to do with auto brightness! I am on latest AryaMod, which is stock TW based ROM, so I guess its a problem of all the TW releases?
Don't know! I will ask this in AryaMod topic and see whether dev will be more than kind to provide us a solution. Thanks for creating the topic, I had thought about it a lot of times, but was never intrigued enough.
neky92 said:
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
Click to expand...
Click to collapse
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
shchiam1978 said:
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
Click to expand...
Click to collapse
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
neky92 said:
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
Click to expand...
Click to collapse
I am using death note.
Now I am back to Arya to test the battery life.