*update* the latest update from AT&T this month seems to have fixed the auto-rotate function. I have had no issues regarding this problem since applying the update!
Trying to see who else has had this problem and has been able to find any common occurrences behind this mysterious issue.
I can sometimes go quite awhile before the auto rotate stops working but I don't normally turn the phone to landscape unless I'm viewing photos or looking at a video or maybe some websites that aren't mobile optimized.
Toggling the portrait rotate icon from the drop down does not fix the issue. So far the only way to get rotate working is to reboot android completely. I've had a theory that maybe my magnetic car mount is somehow messing with the sensor in the phone or the calibration of the unit but I've used the same magnet mount with my G3 and never had these issues. also sometimes when navigating GPS it will ask me to calibrate the phone and fly it thru the air in a figure 8 but I'll do that like an idiot and the calibration screen never goes away. I've also used the built in diagnostics inside the settings that check all the sub functions of the phone and everything is apparently working without issue!
..... starting to wonder why I even got this phone.
at&t hasn't even started my 50% off bill credits yet for this device...
undivide said:
Trying to see who else has had this problem and has been able to find any common occurrences behind this mysterious issue.
I can sometimes go quite awhile before the auto rotate stops working but I don't normally turn the phone to landscape unless I'm viewing photos or looking at a video or maybe some websites that aren't mobile optimized.
Toggling the portrait rotate icon from the drop down does not fix the issue. So far the only way to get rotate working is to reboot android completely. I've had a theory that maybe my magnetic car mount is somehow messing with the sensor in the phone or the calibration of the unit but I've used the same magnet mount with my G3 and never had these issues. also sometimes when navigating GPS it will ask me to calibrate the phone and fly it thru the air in a figure 8 but I'll do that like an idiot and the calibration screen never goes away. I've also used the built in diagnostics inside the settings that check all the sub functions of the phone and everything is apparently working without issue!
..... starting to wonder why I even got this phone.
at&t hasn't even started my 50% off bill credits yet for this device...
Click to expand...
Click to collapse
You are not alone. Mine did this yesterday. I had to reboot it to fix it. I do not use a magnetic mount but I do use wireless charging stations and I think they have a small magnet. I have done this for months though and so far the auto-rotate glitch has only happened 2 times.
I have had the same issues. But a reboot won't always fix it me.
problem resolved
latest update patch from AT&T seems to have fully resolved the issue of auto screen rotation not functioning. it now works 100% of the time and is even faster at recognizing when the device has been tilted to and from landscape/portrait
Related
I'm not rreally a fan of auto rotation since my old phones made this so painful.
Enabled it on my Vibrant, and found it interesting enough to keep it on.
Try hard not to let it rotate when I just held it sloppy, so I didn't snap that it hasn't been rotating in a while...
Which sucks when a media player goes landscape and nothing auto rotates back.
While I have adw, lp and lh installed, they all three are set to rotate.
Wondering what else might be gone I went to sensors test in *#*#1472365#*#* and all sensors showed "false".
Not sure I saw anything else un past there I installed some compass app, nothing moves, since it also does gps compass I saw it lock in 3-4 secs even showed me my address, but the while time the compass showed only "Loading...."
Wondering if there is a file if gone kaputt, affects those sensors, that could be removed to force some sort of default, kind of like deleting a file to reset battery meter, at least gps works fine. ....
Any ideas before I call customer service for yet another replacement?
Thanks,
Daniel
Sent from my Vibrant.
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
mattsolberg said:
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
Click to expand...
Click to collapse
check your time-out settings for screen and lock?
I have it set to time out after 10 minutes but my understanding was the screen should automatically shutoff and stay off when docked and closed. Am I wrong? Could it be a kernel issue? I'm using the Clemsyn kernel. OC'd to 1.4
mattsolberg said:
I have it set to time out after 10 minutes but my understanding was the screen should automatically shutoff and stay off when docked and closed. Am I wrong? Could it be a kernel issue? I'm using the Clemsyn kernel. OC'd to 1.4
Click to expand...
Click to collapse
In Applications -> Development. Is the option that says "Stay on when charging" turned on? That'll explain why. Since the dock is technically charging the tablet.
frosty5689 said:
In Applications -> Development. Is the option that says "Stay on when charging" turned on? That'll explain why. Since the dock is technically charging the tablet.
Click to expand...
Click to collapse
I was excited for a minute, hoped that might be it. But no, I don't have that option enabled. You're using the Netformer kernel? Maybe I will try flashing that. At worst it could rule out the kernel causing the problem.
mattsolberg said:
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
Click to expand...
Click to collapse
Check your tablet is properly docked?
The magnet under the "+=" key on the dock will turn off the screen on the tablet ONLY when the tablet is properly docked. When the tablet is loosly docked (hard to describe but has happened to me) the magnet will have no effect on the tablet screen dimming. For example, if you disconnect the tablet and dock and place a magnet over the tablet (same area above "+=" on keyboard) nothing happens.
All sorts of dock issues happen to me when I force stop services or delete data related to dock services. Nothing has recovered the dock for me, except a complete factory reset. For example, I force stopped and deleted data on three services related to android & asus keyboard and the top row of keys no longer functioned until factory reset (e.g. wireless, bluetooth, pad disable, etc. through settings key and some audio controls). This might be a related issue if you are not on stock OS/ROM.
Good luck!
my tablet is docked properly but is still got the issue that the screen turns on even when the lid is closed .. it turns off first but recovers a few seconds later ..
Mine is exactly the same--the stay awake option is not checked, the tablet is docked correctly (slider is all the way to the right), and the tablet comes on while docked and charging. However, it does charge. I haven't timed it to see how long it takes vs undocked, or docked being used. I'm running unrooted, latest updates.
Bob Smith42 said:
Check your tablet is properly docked?
The magnet under the "+=" key on the dock will turn off the screen on the tablet ONLY when the tablet is properly docked. When the tablet is loosly docked (hard to describe but has happened to me) the magnet will have no effect on the tablet screen dimming. For example, if you disconnect the tablet and dock and place a magnet over the tablet (same area above "+=" on keyboard) nothing happens.
All sorts of dock issues happen to me when I force stop services or delete data related to dock services. Nothing has recovered the dock for me, except a complete factory reset. For example, I force stopped and deleted data on three services related to android & asus keyboard and the top row of keys no longer functioned until factory reset (e.g. wireless, bluetooth, pad disable, etc. through settings key and some audio controls). This might be a related issue if you are not on stock OS/ROM.
Good luck!
Click to expand...
Click to collapse
It was exactly what happened to me! Check if the dock button go until the end. This is made by docking well, not forcing the button. After that the screen went off has supposed.
Good luck.
no .. ich checked it twice .. i can't push it harder to dock it .. the switch is all the way to the right.
Is there any known app that can handle the switching forced by opening and closing the lid ?
I think this happened to me one time and caused a huge scare.
I had been shutting the lid of the TF and putting it in it's case...and having no problems.
But one time I did that, and it came back on and got VERY HOT and ran the battery to 0%!
I got lucky and just recharged it, but now, I shut it off everytime I'm going to put it in the case...you can't trust the shut-off-feature.
Got the exact same issue, screen is initially turning off but when you fully close the lid it turns on. It's got something to do with the touchpad (for me at least), because I've got no problems at all when you turn the touchpad off!
Can you guys try this too? Just turn the touchpad off and see wether the screen will turn on or not. Might get us closer to a fix.
Gibeon said:
Got the exact same issue, screen is initially turning off but when you fully close the lid it turns on. It's got something to do with the touchpad (for me at least), because I've got no problems at all when you turn the touchpad off!
Can you guys try this too? Just turn the touchpad off and see wether the screen will turn on or not. Might get us closer to a fix.
Click to expand...
Click to collapse
Same for me, i also had the feeling that it depends on the touchpad because when you reopen it you can see the cursor somewhere on the screen. Will try it later when i'm at home! Maybe we have to use something like a script to deactivate the touchpad when closing the lid.
greetings
Awesome ! this seems to work (tested it several times now).. i think there might be a way to react to the intents fired by closing and opening the lid so we can use them to turn off the touchpad.. ill check it out later but im not that experienced in android so maybe someone wants to help
EDIT: There is a status change in LogCat made by the WindowManager. Its called notifyLidSwitchChanged but there is nothing in the log while enabling or disabling the touchpad...
Maybe this related to problem?
I killed a few application services and deleted their data, while in settings. Afterwards my dock was not working correctly, e.g. keys were disabled and other strange effects.
I copied the 3.1 update from the web to flash and re-updated but this did *not* fix the problem. Next I did a factory reset and this solved my dock problems.
Maybe your tablet is missing some ASUS control bits for the dock? If you can afford a factory reset it might help. Good luck.
I'll try, I'm rooted so I'll just nandroid and revert to stock 3.1. I'm glad the touchpad "fixes" it atleast, means we all have the same issue.
Fixed
Thanks for posting this question as I thought I was the only one experiencing this issue.
The fix for me was found when Gibeon mentioned the touch pad. Once I read that I realized that the cursor was always displayed when I would open the case. Not sure of the reason. All I have to do is turn the touch pad off and it works fine.
I will try a factory reset/data wipe when I am ready but for now this works fine for me. Perhaps there is a away to fix this in the kernel (I have used both clemsyn/blades and netformer and had the issue with both) Thanks for the info!
I made a thread about this too a few days ago, I still have this problem and it drains my dock battery in only 3-4 hours. (and that's WITHOUT using the TF at all for those 3-4 hours)
Tested on mine and it is definitely the touch pad. Thanks for the help everyone. At least we've got a work around to use until a more permanent fix is achieved.
Would tasker be able to automatically shut down touch pad when screen is closed?
Sent from my GT-I9000 using XDA App
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
Noticed recently in Gsam that my proximity sensor is pretty much on all the time. The sensor itself is working fine, when making calls. I don't use it for any gestures (have all the stuff turned off besides knock-on). I am on xdabbeb's 3.1.0 and smart cover option is removed from it. Even before, on micromod's extreme 1.1 I noticed this but disregard it. All I could find was that the viber could be an issue, tried uninstallin it, didn't help. As I said, sensor works just fine with phone calls and it's not covered, dirty or anything. How could I locate whatccould be triggering it? Going through all the apps is kinda waste of time, probably most of them are not even using it. Gsam always shows like the system is using it. There are no wakelocks to go with it, the phone sleeps just fine. All the other sensors are acting normal. I wish someone could help me figuring this one out because I don't think this is normal. Maybe app or lollipop related? Maybe rom? How to get a log or something to see what triggers it when I turn of the screen. Btw, it happens only when the screen is off.
Update
I think I figured out what causes this (but not why). If anyone else is having this issue, this might help. I know sensor doesn't use as much battery, but still. Why it should be working when not in use.
So apparently, proximity sensor in Gsam shows sensor working when phone is idle and the phone is placed with it's rear cover down. When you place your phone screen down, thus making your sensor covered, there is no proximity sensor battery usage registered in Gsam.
Had the BEST VR experience to date last night using the bundled Gear VR and playing Gunjack/Lands End until phone ran out of juice...
However that experience was marred when I fired the phone back up this morning and found that all the applications have suddenly starting rotating into landscape and despite rebooting twice, I cannot change the behaviour (it was fine yesterday). Ran some sensor checks which appear to be OK. I don't even seem to have a rotation lock button available as I did on my Note 3 as a workaround.
Adding to this, I have also noticed that the fingerprint unlock feature seems to have disabled itself, even though it's still enabled in settings together with stored fingerprints. I know this is a new device, but this is pretty basic stuff that should be working... Not impressed!
Any others having similar issues?
Thanks,
G
Fixed... kinda
I since discovered that the rotate lock had become enabled and is still available on the settings icons (didn't recognise the icon in the locked portrait state). It actually did it again this morning and appears to be defaulting to this state after a cold boot - weird)...
The fingerprint issue appears to have been caused by loss of the screen timeout/instant lock with power button settings; however I hadn't changed these values, so there do seem to be some software glitches that need ironing out...
G