All of a sudden today, my screen turned off after like 4 seconds. I pressed power and it just flashed momentarily and turned off immediately. Every time I pressed power, it did the same thing.
I rebooted. The ASUS startup screen showed fine. Then as soon as it booted in, same thing.
I tried wiping all data, and then rebooted. Same problem.
Since it only does this when booted in, I'm thinking it's a software issue. But how the hell do I fix it if I can't get the screen to do anything more than flash on for less than 1 second?
When I'm plugged in, the screen works fine. I'm so confused...
UPDATE: For some reason, when I turn on automatic brightness, the problem goes away. But the second I turn off auto brightness, the screen immediately shuts off and the problem repeats. And auto brightness keeps the screen on a really low setting.
Urrghhh
Chief85 said:
All of a sudden today, my screen turned off after like 4 seconds. I pressed power and it just flashed momentarily and turned off immediately. Every time I pressed power, it did the same thing.
I rebooted. The ASUS startup screen showed fine. Then as soon as it booted in, same thing.
I tried wiping all data, and then rebooted. Same problem.
Since it only does this when booted in, I'm thinking it's a software issue. But how the hell do I fix it if I can't get the screen to do anything more than flash on for less than 1 second?
When I'm plugged in, the screen works fine. I'm so confused...
UPDATE: For some reason, when I turn on automatic brightness, the problem goes away. But the second I turn off auto brightness, the screen immediately shuts off and the problem repeats. And auto brightness keeps the screen on a really low setting.
Urrghhh
Click to expand...
Click to collapse
This is a well known and well documented issue that could have been easily found by searching. Your thread adds to the 3 or 4 that already exist regarding this issue.
Sent from my TF Decepticon
b1ackplague said:
This is a well known and well documented issue that could have been easily found by searching. Your thread adds to the 3 or 4 that already exist regarding this issue.
Sent from my TF Decepticon
Click to expand...
Click to collapse
I do recall reading similar reports earlier, but from my memory, there seemed to be some differences. If I'm wrong, I'm sorry for inconveniencing you for a whole 5 seconds
Side question: have you ever tried to get decent search results? It's extraordinarily difficult given that terms are used for multiple purposes, and not all the language is universal.
After going back, and reading a ton of threads through manual forum-browsing, it seems that I was correct about most other problems being distinction from this. Only really found one other mention of this (http://forum.xda-developers.com/showthread.php?t=1078331). So perhaps YOU should search before telling people they should search.
Anyone have thoughts?
Chief85 said:
After going back, and reading a ton of threads through manual forum-browsing, it seems that I was correct about most other problems being distinction from this. Only really found one other mention of this (http://forum.xda-developers.com/showthread.php?t=1078331). So perhaps YOU should search before telling people they should search.
Anyone have thoughts?
Click to expand...
Click to collapse
I do search and I am subscribed to other threads that I check daily regarding your same issue. Ill come back to this thread and post the links to those other forums so as to keep the TF general thread from being overpopulated. And even if your problem IS unique its still very closely related to others in the forum link you posted and would still be more appropriate to post there rather than creating another thread.
I have the same exact problem as you and I want it solved just as much as you but I would I also like the ability to easily navigate this forum and that's only possible by keeping related threads from happening.
Sent from my TF Decepticon
For now the only solution seems to be to keep hard resetting your device (hold power for 10+ seconds) several times and keeping a manual brightness. I had to hard reset my device 8 tines before the screwn would stay on. The reason that your backlight is shutting off when you turn AB off is because of where your manual brightness is set and chances are it's set too high which seems to be the common cause. Keep hard resetting your device until manual brightness is allowed then set MB to a lower level. This issue happens on AB as well when in a bright area and it sets the brightness to high on its own.
Sent from my TF Decepticon
I wonder if it can be fixed if you use the dock's brightness adjustment keys?
b1ackplague said:
I do search and I am subscribed to other threads that I check daily regarding your same issue. Ill come back to this thread and post the links to those other forums so as to keep the TF general thread from being overpopulated. And even if your problem IS unique its still very closely related to others in the forum link you posted and would still be more appropriate to post there rather than creating another thread.
I have the same exact problem as you and I want it solved just as much as you but I would I also like the ability to easily navigate this forum and that's only possible by keeping related threads from happening.
Sent from my TF Decepticon
Click to expand...
Click to collapse
Hate to jump in you but do you see the inherent contradiction in that statement? If the search tools are adequate then the number of similar threads should not matter as they can sorted by relevance. If they are not, as your desire for single threads suggest, then asking a new person to use them to find an answer is not appropriate as it isn't going to be successful. I've found that the bulk of the posts aren't technical so a search for the appropriate terms is pointless and a simple question is more likely to get results. For example, when calling on webcore, lcd brightness is being set to 0. This is in the logcat I took when testing and I get nothing when searching for it. If I search for 'black screen', I get something.
Let's remember we're here to help each other. Being inclusive and welcoming to newcomers is a much more positive way for us to find results.
Cheers,
Todd.
frosty5689 said:
I wonder if it can be fixed if you use the dock's brightness adjustment keys?
Click to expand...
Click to collapse
I have this problem and the dock is the only way I can get the screen back on. I have to press the auto brightness button then press the power button to get the screen on.
If I manually increase the brightness from 0 in steps I can get to half way but then the screen goes off. Similarly I can reproduce this by using the slider to increase the brightness. I am trying other ROMs to see if I can get rid of this issue but so far it happens on Stock & Paul O'Brian's with full resets on both. sigh.
After endless reviews of the logcat files, resets and roms, seems I can't find a solution. Going to rma it unfortunately!
Sent from my HTC Desire using XDA App
So RMA is the answer?
Yes I rmaed mine to Asus. Only took them a a few days to fix and ship it back to me.
Thanks. I better unroot mine and get it sent.
Having this problem.
How does one disable the button backlights? Screen filter isn't doing the job and ur can be annoying for night viewing.
Sent from my Infuse
what is a gas light?
also some of us have short attention spans (ADD) and cant remember the name of the link we just clicked on or why we clicked on it. it may seem odd but you should ask a direct question in the op just to make sure people dont get lost. (seriously, i see this alot on another forum and i have even done it myself finding myself confused when a thread only contains a sig or a smiley as i have already forgotten the title)
ahh i guess you are haveing auto correct issues and using a forum app. now my post sounds silly.
i dont know of any way to accomplish this without messing with the kernel, maybe could be done in the framework. this needs a dev im sure. but i never found the backlights very bright to cause a visability problem. the vibrant has way brighter backlights.
I at least attempted to edit the op. I meant backlight and yes it was auto correct
Sent from my Infuse
Keep the Lights On should be able to do this.
Back on Froyo and GB, you were able to add/edit the wifi_idle_ms string in order to change the value of how quickly the WiFi radio would go to sleep after the display turns off. However, modifying the same string (/datadata/com.android.providers.settings/databases/settings.db in the secure table) under ICS doesn't appear to have the same effect. WiFi remains connected for the default 15 minutes even after the screen is turned off.
Is there any working fix for this?
Please don't create double post about the same issue.
My post in Q/A is a completely separate issue.
My post in SlimICS was to ask if anyone else had the same problem (if it's a known issue).
My post here is asking if anyone has an alternate method of achieving this.
But your condescension and insight is greatly appreciated
It is the same question.... Live with it!
Sent from my SGH-I897 using xda premium
Thread closed
Refer to your other thread. As b-eock said, do not double post. In addition, this thread is a question, which is properly placed in Q&A, not in General.
I installed this Rom and I have a few glitches that I didnt see in the development thread but I dont have enough post to actually post in there. I cant find a bug report site so I'm curious hth Im supposed to find solutions or even address the issues.
1) Keyboard disappears while typing in Google chrome.
2) Status bar flickers and shows multiple images at times.
3)Notifications don't open for advanced options when long pressed.
4)First time booting the screen was distorted and couldnt read anything,had to press back a couple of times and then it went through setup fine
slacker1979 said:
I installed this Rom and I have a few glitches that I didnt see in the development thread but I dont have enough post to actually post in there. I cant find a bug report site so I'm curious hth Im supposed to find solutions or even address the issues.
1) Keyboard disappears while typing in Google chrome.
Click to expand...
Click to collapse
I just installed Chrome and couldn't reproduce the issue you mentioned. It seemed to behave properly during the brief testing I tried.
2) Status bar flickers and shows multiple images at times.
Click to expand...
Click to collapse
Yes (sort of a staggered effect).
3)Notifications don't open for advanced options when long pressed.
Click to expand...
Click to collapse
Not certain what you mean here. I get a few options (WiFi, BT, GPS & Vol) and an option to get to settings.
4)First time booting the screen was distorted and couldnt read anything,had to press back a couple of times and then it went through setup fine
Click to expand...
Click to collapse
Yup I had that as well. on the very first screen after installing it for the first time.
You must remember that CM10 is very much an Alpha and subject to a lot of change as the various bugs get ironed out. There seem to be quite a few issues in getting CM10 (from CM9) to run with JB. So far the devs have done a fantastic job.
Please also note that you'll get shouted at if you post questions like these in the Dev thread. It's being used almost exclusively by the CM10 Devs. I believe that there is a CM10 thread in General where it might be more appropriate to post questions like these.
EDIT: Found the thread in General.
http://forum.xda-developers.com/showthread.php?t=1802308
slacker1979 said:
I installed this Rom and I have a few glitches that I didnt see in the development thread but I dont have enough post to actually post in there. I cant find a bug report site so I'm curious hth Im supposed to find solutions or even address the issues.
1) Keyboard disappears while typing in Google chrome.
2) Status bar flickers and shows multiple images at times.
3)Notifications don't open for advanced options when long pressed.
4)First time booting the screen was distorted and couldnt read anything,had to press back a couple of times and then it went through setup fine
Click to expand...
Click to collapse
1.I am getting the issue with chrome, although this happened in ViperS also so it suggests to me that it is a particular chrome bug rather than CM10.
2.I only get this when I have a notification and only briefly.
3.Havn't tried sorry.
4.I didn't have this issue.
(sorry I couldn't be of any actual help )
So I wanted to flash MIUI 3.1.11 on my Galaxy i9300 S III and I have two rather annoying bugs:
1. I have no lock screen. The phone just wakes up into the home screen.
2. The home button only works for waking the device, after which it turns off.
Everything works on a Sammy rom, but on MIUI 3.1.11, it doesn't work. I'm going insane, because nothing I've tried helps, and I've been on miuiandroid's forum and no on there seems to know or care, and on en.miui.com forum, all they're giving me are the basic replies for noobs (i.e. full wipe, reflash, etc.) all of which I've done over and over again, without help. I've googled for hours on end without result as well.
I opened a topic about it in the i9300 forums, but now I'm turning to the general forum to see if this issue exists for you as well. I checked in the /efs/factoryapp folder but nothing is out of the ordinary there (says ON in both files there.
I have the same problem with my GSM Galaxy Nexus. Read this thread from miuiandroid and it should solve it. http://miuiandroid.com/community/threads/no-lockscreen-or-home-menu-i9300.19278/
thanks
ephung23 said:
I have the same problem with my GSM Galaxy Nexus. Read this thread from miuiandroid and it should solve it. http://miuiandroid.com/community/threads/no-lockscreen-or-home-menu-i9300.19278/
Click to expand...
Click to collapse
I am the OP of that thread. ^^