Related
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.
Latest distro of RG2X MIUI installed... I can't seem to find any way to adjust or disable the LED notification when an Email/SMS/Call is received/missed. Anyone have any insight?
I like the LED notification, however it seems to destroy my battery life if I don't clear the notification in a reasonable amount of time. I wouldn't think it to be the problem, however if I go without getting notifications, my battery life is great.
TIA
searched the thread came up with this, courtesy of psychoace
Go to the home screen
Hit the search button
Hit menu
Go to search settings
Turn on settings search
Back out
Hit search again and type either trackball or led
You now have control of your capacitive button lights
and maybe next time search the thread or ask in there before making a whole new thread when you don't have to... that is an old solution and MIUI has been updated since so I don't know if it'll work or not... post your results if it worked.
mt3g said:
searched the thread came up with this, courtesy of psychoace
Go to the home screen
Hit the search button
Hit menu
Go to search settings
Turn on settings search
Back out
Hit search again and type either trackball or led
You now have control of your capacitive button lights
and maybe next time search the thread or ask in there before making a whole new thread when you don't have to... that is an old solution and MIUI has been updated since so I don't know if it'll work or not... post your results if it worked.
Click to expand...
Click to collapse
While I should have mentioned in my original post that I DID SEARCH for a solution, I don't see the necessity for the contempt.
I did try the method mentioned, PRIOR to posting this thread. Neither LED or Trackball shows up in the search after enabling the settings search.
In summary, the proposed solution does not work for RG2X MIUI 2.3.24
hmmm I didn't think it would, I don't know what to tell you hopefully someone can help out.
Ok, an update for anyone who may have a similar problem.
I could not get the above mentioned solution to work, at first. After getting a bit frustrated with the matter, I performed a completely clean flash of the ROM again, re downloaded, etc... and now the above solution does work.
Another inexplicable and random quark I suppose.
Thanks for the help, mt3g.
Interesting but glad it worked out
Sent from my LG-P999 using xda premium
Hi guys,
I tried searching for this but I keep running into very old threads.
I read on Android Central forum that there's a zip file to make Galaxy S3 CM10 have the same exact menu bar as Nexus devices and completely disable the capacitive buttons.
Could someone please point me to this zip file? Also, is it possible that this is already just an option in CM10?
This is honestly the only thing stopping me from getting this phone. Since I have Nexus 7, I don't like how I have to adjust to buttons every time I use my wife's Galaxy S3.
Thank you.
T-R said:
Hi guys,
I tried searching for this but I keep running into very old threads.
I read on Android Central forum that there's a zip file to make Galaxy S3 CM10 have the same exact menu bar as Nexus devices and completely disable the capacitive buttons.
Could someone please point me to this zip file? Also, is it possible that this is already just an option in CM10?
This is honestly the only thing stopping me from getting this phone. Since I have Nexus 7, I don't like how I have to adjust to buttons every time I use my wife's Galaxy S3.
Thank you.
Click to expand...
Click to collapse
you should definitely check out paranoid android and all its modes that are available.
ddurandSGS3 said:
you should definitely check out paranoid android and all its modes that are available.
Click to expand...
Click to collapse
Thank you! This is just what I need but it doesn't seem stable in this video I found (perhaps because it's outdated). I can't post a link since I'm a new member.
T-R said:
Thank you! This is just what I need but it doesn't seem stable in this video I found (perhaps because it's outdated). I can't post a link since I'm a new member.
Click to expand...
Click to collapse
I am running the 9/6 build and i havent had any issues with the ROM.
not one reboot, no screen flicker, everything works for me.
just do a nandroid prior so you can revert back.
if i remmeber correctly, there is a bug that causes the backlights of the keys to stay on. nto sure if its been fixed
ddurandSGS3 said:
I am running the 9/6 build and i havent had any issues with the ROM.
not one reboot, no screen flicker, everything works for me.
just do a nandroid prior so you can revert back.
if i remmeber correctly, there is a bug that causes the backlights of the keys to stay on. nto sure if its been fixed
Click to expand...
Click to collapse
Cool, thanks. I will definitely book mark the link to this ROM.
T-R said:
Cool, thanks. I will definitely book mark the link to this ROM.
Click to expand...
Click to collapse
I think most CM based Roms have the option to disable the capacitive buttons and enable the on screen navigation bar.
Unless it's been fixed now, when I was running Paranoid Android every time you reboot your phone you have to go back in to the settings and disable the lights on the capacitive buttons.
Hey Guys,
as CM10.1 posts are flooding the two CM10 threads I'm opening a new discussion Thread here so that you/we can keep the CM10 Threads for CM10.
Feel free to post videos & screenshots, I will add some of them to the OP if you want me to!
I also would encourage you to tell me what works & what doesn't, please use a proper listing method therefor.
As always all credit goes to intervigil, xkonni & the others behind CM10(.1)!
said/found to be working / not working:
Screen tearing (nearly unnoticeable)
Working: everything else
I'm looking forward to get CM 10.1
Thanks for the 10.1 thread!
So the first question I got the 10.1-20121210-experimental and got no developers and power options Besides the camera and this issue, it works great! Thanks to all developers!
Just tab 7 times on "Build name" to become developer,
gesendet von meinem HTC One S mit Tapatalk
All is allowed to contribute for a better clarity.
Voice search within apps won't work. (Any voice assistant) [Still able to make/recieve calls]
Lag spike once in a while
Screen tearing
No camera applications as all.
BT problem
No audio when connected headphones (From what I hear someone confirm this) a13xemz's quickfix from the playstore Playstore: SoundAbout
Quick setting menu can be a bit restless while downloading apps and trying access it. (Setting vanish and come back)
Hope GPS and Nav will work, hopefully some people can tests this out to make sure. While all of this is being resolved
For those expirencing issues with headphones not working this app/widget fixes the problem. https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix
Sent from my One S using xda app-developers app
I can confirm that the issues mentioned in post 6 cover everything I've noticed so far.
Fyi, I dirty flashed over CM10 and the camera app was present and had the new icon, it just didn't work. I thought it was odd that the new gallery didnt seem to sync to Picasa either (like the current cm10 gallery) because when i used the leaked 4.2 camera, the gallery sync worked great.
a13xemz said:
For those expirencing issues with headphones not working this app/widget fixes the problem. *removed URL, under 10 posts. See original quote*
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I can confirm that this workaround fixes (forces) headphone usage.
Also, attached some screenshot goodies for yall
i just did a dirty flash and flash the boot.img, and when it boots its stuck on HTC but then again when i hit the power button off, what it does is off but when i push the power back on, and hit the screen the buttons light up how come?
klutch said:
i just did a dirty flash and flash the boot.img, and when it boots its stuck on HTC but then again when i hit the power button off, what it does is off but when i push the power back on, and hit the screen the buttons light up how come?
Click to expand...
Click to collapse
Because dirty flash is not recommended. Try a full wipe and you will be fine.
well i did that and still the same bro, but now when i went to the previous backed up its looping
klutch said:
well i did that and still the same bro, but now when i went to the previous backed up its looping
Click to expand...
Click to collapse
What version of TWRP do you have? I had the same problem and had to get the latest to properly restore my backup.
el_smurfo said:
What version of TWRP do you have? I had the same problem and had to get the latest to properly restore my backup.
Click to expand...
Click to collapse
TWRP v2.3.1.0
and this is how it stays
well now i guess i have to find a way to take that loop of cM its not passing no matter wat cm10 dates or boot.img
Michael1101 said:
Thanks for the 10.1 thread!
So the first question I got the 10.1-20121210-experimental and got no developers and power options Besides the camera and this issue, it works great! Thanks to all developers!
Click to expand...
Click to collapse
To get developer options, tap the build date 7 or so times.
only issue after fresh install, full wipe
is remapping of hw keys--no issue on other roms
if i chose long press on recent app as voice leaving short press menu
and long press home screen as recent apps--I get voice for any press of recent apps and home key
i can get recent apps to be menu and home stays as home
then no recent apps
hope this is not confusing and mentioned before--did look around
did wipe caches and rebooted
maybe only option is too reflash, but no recent apps is not a big deal as rom runs very smooth and I have my voice turns in GMaps with street names spoken now. street names were not mentioned on other roms for me for a while now--
forget it i found the problem ill wait till the next CM10.1 arrives
klutch said:
forget it i found the problem ill wait till the next CM10.1 arrives
Click to expand...
Click to collapse
how did you fix it klutch
earched Google all over and couldn't find a solution for this. When I get an incoming call on my nexus 5, half of the screen goes black, and the main buttons disappear, and I can't do anything with the status bar. Basically, I can't do anything besides answer, hang up or text. Only after I answer the functionality returns. It's really annoying when I'm in the middle of something and than someone calls and I can't just ignore it, I have to wait until the caller hangs up (and then usually he will call again). The half black screen also bothers me but it's not the real problem, I just guess it's part of the bug. I tried using 3rd party apps for incoming calls but they don't solve this problem. This is how it looks like (I can't post a picture so copy the link):
img208.imageshack.us/img208/1973/919d.png
I'm surprised I didn't find a solution because it's a very annoying problem and I don't think it only happens to me. I'll be glad if you know how to fix this. Thanks
shahar4499 said:
earched Google all over and couldn't find a solution for this. When I get an incoming call on my nexus 5, half of the screen goes black, and the main buttons disappear, and I can't do anything with the status bar. Basically, I can't do anything besides answer, hang up or text. Only after I answer the functionality returns. It's really annoying when I'm in the middle of something and than someone calls and I can't just ignore it, I have to wait until the caller hangs up (and then usually he will call again). The half black screen also bothers me but it's not the real problem, I just guess it's part of the bug. I tried using 3rd party apps for incoming calls but they don't solve this problem. This is how it looks like (I can't post a picture so copy the link):
img208.imageshack.us/img208/1973/919d.png
I'm surprised I didn't find a solution because it's a very annoying problem and I don't think it only happens to me. I'll be glad if you know how to fix this. Thanks
Click to expand...
Click to collapse
That's exactly how its meant to be. If you flash a ROM like omni you can get a less intrusive dialer that looks something like this:
http://omnirom.org/wp-content/uploads/2013/11/UnobtrusiveCallNotify.png
If you've never installed a ROM before there are loads of tutorials to get you started, just don't take any shortcuts (like toolkits!)
//Nexus 5//Nexus 4//HTC WFS//
Tom540 said:
That's exactly how its meant to be. If you flash a ROM like omni you can get a less intrusive dialer that looks something like this:
(URL)
If you've never installed a ROM before there are loads of tutorials to get you started, just don't take any shortcuts (like toolkits!)
//Nexus 5//Nexus 4//HTC WFS//
Click to expand...
Click to collapse
But wouldn't flashing the device prevent me from upgrading my android version? I mean, one of the advantages in nexus is that it gets more upgrades and sooner than everybody else, isn't it?
shahar4499 said:
But wouldn't flashing the device prevent me from upgrading my android version? I mean, one of the advantages in nexus is that it gets more upgrades and sooner than everybody else, isn't it?
Click to expand...
Click to collapse
most custom roms get updated even before an ota is out. once google drops source into aosp, that day or next, most custom roms update. sometimes this happens a week before otas go out, sometimes its about the same time.
simms22 said:
most custom roms get updated even before an ota is out. once google drops source into aosp, that day or next, most custom roms update. sometimes this happens a week before otas go out, sometimes its about the same time.
Click to expand...
Click to collapse
So what you're saying it's that custom ROM is always better?
shahar4499 said:
So what you're saying it's that custom ROM is always better?
Click to expand...
Click to collapse
have u tried one of the full screen caller id apps ?
I tried this one on my Moto G with Android 4.3.
https://play.google.com/store/apps/details?id=tw.nicky.HDCallerID
see if it works for your phone.
same problem here, thanks god i'm not alone! I simply don't get why on incoming calls i cant hit the home button and go back on my stuff!!! annoying. hope in a solution, had tried many apps but didn't find the right one
I have the same problem in the last month I had this issue 5 or 6 times until now...any idea besides installing a custom ROM?
Similar problem here.
I have a similar problem. No black screen but I can't do anything and the nav bar disappears. N5 with 4.4.4 stock, Franco Kernel, root, xposed Framework. I found out that other phones have the same problem and in a moto x thread I found a thread that perfectly matches my problem.
I think it's an android bug.. like a file system or something.. not related to any customization.