Ive had a rooted Alcatel One Touch Fierce for about a month. Just recently a Tmobile update downloaded and i installed it. My phone rebooted and ever since then my screen turns off or goes black everytime i turn the screen on. For example when i press the lock button to wake my phone it will display for at least a second then go black but the touch is still functional so id have to navigate by guessing where everything is then pop the screen on for a second to see where i am. The only exception is when i bring up my keyboard or edit settings like when a slider pops up for brightness. I can see the android startup screen until its fully rebooted and i can see the recovery mode. Ive reformatted my data and cache. It is also not the timeout setting. I cant find anything about this issue anywhere. Pretty soon i will be taking it to walmart to replace it but until then i want to try and fix it. Anyone know whats wrong?
Go to developers option and disable hw overlays
Sent from my XT890 using Tapatalk
jony5534 said:
Go to developers option and disable hw overlays
Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
I have the same issue and disabled HW overlays but my screen keeps turning off.
I am running Droid Ultra 4.4 Kitkat rooted.
Related
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Fanbayer said:
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Click to expand...
Click to collapse
i updated mobile phone to android versiopn 4.1.2. this morning. Unfortunately the problem still appears.
Maybe its a hardware defect?
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
d0hn said:
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
i disabled auto brightness and set the brightness to the highest level. But its still same: very dim and after a while a black screen; after a few times of unlocking, the display works normally
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Sorry for the necrobump, but I only found this thread. I have this problem too since about a week back. It makes my phone useless at times. I first thought it was a software issue. I have an app (called Twilight) for dimming the screen more than normal settings and also toning it, for nightime use, and I thought that was the culprit first, but nope. I have flashed rom, recovery, wiped all caches I can think of. Still happens, just now I was in the middle of installing android revolution hd, and the screen ultradimmed on me so I can't finish the process
Thing is, a few months ago I managed to crack my screen by way of gravity and concrete. I let the samsung brand service centre in Stockholm repair it for me (it is out of warranty) and this issue with the dimming never happened before that. Then again, it didn't happen directly afterwards either... but still. So, I am thinking: either me dropping it caused more damages and this is because of that. Or the service center did a bad install of the new screen. Or, the replacement screen that was installed has a defect in itself. I am leaning a bit towards the third explanation... maybe different batches of screens?
Does anyone have any ideas? If I am to contact the service center and complain about their work I would like to be able to point towards a "known problem"...
8Fishes said:
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Click to expand...
Click to collapse
Take it back, if it didn't happen before then the new screen is most likely.
It isn't a common problem
I recently updated my i9300 to paranoid android to 3.97 and I'm having two issues... First one is that apps that have border ads down the bottom.. Facebook.. Cheeseburger.. Astromanager etc if you take your finger Off the screen the screen turns black with only the ad showing..... The other issue is that the screen brightness can't decide if it's full of low. You press the power button the lock screen comes on Instantly dims.. Doesn't matter if light Meter is covered or light shining on it.. Disabled all power options.. Auto brightness is off... Tried lux app set all to 100% still dims.. When you run it after the screen dims it shows still being 100% touch the maximum and it comes back again.... Anyone have ideas. Googled ads but came up with nothing for black screen issue... Tried other solutions for the brightness issue still no luck.
Sent from my GT-I9300 using Tapatalk 4
akoli said:
I recently updated my i9300 to paranoid android to 3.97 and I'm having two issues... First one is that apps that have border ads down the bottom.. Facebook.. Cheeseburger.. Astromanager etc if you take your finger Off the screen the screen turns black with only the ad showing..... The other issue is that the screen brightness can't decide if it's full of low. You press the power button the lock screen comes on Instantly dims.. Doesn't matter if light Meter is covered or light shining on it.. Disabled all power options.. Auto brightness is off... Tried lux app set all to 100% still dims.. When you run it after the screen dims it shows still being 100% touch the maximum and it comes back again.... Anyone have ideas. Googled ads but came up with nothing for black screen issue... Tried other solutions for the brightness issue still no luck.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Go to PA Q&A thread next time: http://forum.xda-developers.com/showthread.php?t=1887819
Due to lack of graphic driver on 4.3, the black screen thing could appear. There are two+ solutions:
1. follow this step by dontwannabehere
dontwannabehere said:
The fix is the following:
On your build prop file
There should be a line that says something like this " hwui.render dirty regions = false "
Just add the word debug at the beginning of the line "debug.hwui. render..... "
Sent from my Paranoid GT-I9300
Click to expand...
Click to collapse
2. Install PA 3.99 Unofficial build.
Download @ G+ Paranoid Android i9300 unofficial Nightly builds
https://plus.google.com/communities/118377552590341742680
akoli said:
I recently updated my i9300 to paranoid android to 3.97 and I'm having two issues... First one is that apps that have border ads down the bottom.. Facebook.. Cheeseburger.. Astromanager etc if you take your finger Off the screen the screen turns black with only the ad showing..... The other issue is that the screen brightness can't decide if it's full of low. You press the power button the lock screen comes on Instantly dims.. Doesn't matter if light Meter is covered or light shining on it.. Disabled all power options.. Auto brightness is off... Tried lux app set all to 100% still dims.. When you run it after the screen dims it shows still being 100% touch the maximum and it comes back again.... Anyone have ideas. Googled ads but came up with nothing for black screen issue... Tried other solutions for the brightness issue still no luck.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
for your first problem: the glitches should have been solved with newest cm sources. But look in your build.prop if you have the entry "hwui.render_dirty_regions=false" if yes then change it to "debug.hwui.render_dirty_regions=false" without the " " )
for the second problem I cannot help you, as I am not using paranoid. Look if there is an update or ask in the paranoid Q&A thread http://forum.xda-developers.com/showthread.php?t=1887819 (you could also have asked there your questions )
EDIT: sorry. I am ALWAYS to slow in writing aaargh
Appreciate the quick response... I tried the build.prop editing and this is where it got interesting... I cant edit it ... I've tweaked in the past with ES file explorer or root explorer but on this occasion the apps wont allow it ...does not allow the changes to be saved.... checked the root and thats fine, busybox is installed and working fine... my workaround was to tweak build.prop of the 3.97 rom of PA and apply it it from recovery.... this seems to have fixed the black screen in apps... so thanks for that.
I also just grabbed the 3.99 nightly of PA and build.prop already has the change applied, applying now.... result seems the brightness quirk is still there ... I tried the android sensor app and the lux settings seem to be correct so the light sensor is performing as expected the brightness is just not doing what its told... even if I set it to automatice brightness change the sensitivity and apply 100% to all different lux settings it just ignores it and dims the screen regardless... !!
I am trying to set up a new user on the rooted Note 2 I sold them. They have experienced a crash when using the ripple effect on the lock screen and now when restarting, the JB startup screen hangs and is intermixed with a dropbox login prompt, but screen input/buttons do not work. They can get to TWRP, so I am leaning towards asking them to just reinstall the ROM (JellyBeans v22).
Has anyone else had experience with this issue and how to get around such a situation?
If you can get the phone booted to the lock screen, don't touch it and call that number from another line and try answering it, might take a few tries. Once connected in call, hit the menu button get into phone settings and disable the lock screen and should be good to go. I have been lucky with this before.
Deuce booted Note 2
jeremiahEJ54 said:
If you can get the phone booted to the lock screen, don't touch it and call that number from another line and try answering it, might take a few tries. Once connected in call, hit the menu button get into phone settings and disable the lock screen and should be good to go. I have been lucky with this before.
Deuce booted Note 2
Click to expand...
Click to collapse
Thanks for the tip! Unfortunately the phone will not reboot so the user can't even get to a lock screen anymore.
What is the advised method to start from scratch in this situation through TWRP?
Sent from my SM-N900V using Tapatalk 2
I stupidly allowed the update while rooted causing some interesting damage. It seems the device works properly except that the screen blacks out instantly. I can access power up/down and recovery screen with no issue, but the home screen will not stay active. Any suggestions? I tried T Mobile and Alcatel but only gained a headache.
I had the same thing happen even though I first unrooted my phone. Not sure what the exact cause is and even a factory reset did not solve the issue. What I have is a workaround (probably not very efficient)-
1. Despite the screen being black, it is still responsive. Use the power button to get your bearings on the screen and work in the dark to get to the Setting page.
2. Since you are rooted already, you should have access to the developer options. Go to Developer Options.
- if not, click on Build Number in About Phone 7 times and then retun to settings and you will see Developer options
3. Check off Disable HW overlays
- As per my reading, this causes the phone to lag more, but you get your screen back
- I also activated Show touches (which I found first) that allows you to temporarily see the screen as the touch appears (which made it so I can continue trying different options without using the power button to get my bearings)
If anybody can explain to me why this works and if there is a better way to fix the problem, I would greatly appreciate it. I tried also cleaning the proximity sensor and using apps that force the screen to stay on, but neither of these options worked.
hang in there
my guess is the only fix left is a custom rom the only issue is there are none for this phone if anybody knows of any custom roms for the alcatel onetouch fierce it would be greatly appreciated!
Secure settings app and E-robot app. Just set it to turn off overlays when the device is shaken.. Need to be rooted for it to work.. "Tasker" app works too I think .
Sent from my ALCATEL ONE TOUCH Fierce using xda app-developers app
Hi all..
I have a problem with my DNA. Sometimes, like maybe once every few weeks or so, the touch screen will not respond correctly.
Here's what happens:
1. I turn on the display while the phone is already running. (meaning, I'm not booting up when it happens)
2. I try to slide the unlock widget up but it doesn't respond.
3. I hold the power button, and it says to continue holding it for 3... 2... 1.. seconds. However, at 1 seconds, it never does anything. I've held it for 2 or 3 minutes at times, and no reboot.
4. I swipe randomly around the screen and notice that some of my quick launch icons or the unlock slider bump up momentarily, but not enough to unlock the phone.
5. I continue swiping randomly, with a random number of fingers, and eventually the stars align and the phone is unlocked.
6. Once the phone is unlocked, tons of random touch presses occur. Random apps will open, messaging, etc. Sometimes, it opens the phone app and randomly presses things. It does this at a very, very rapid rate. I usually panic and turn off the display so it stops.
7. I manage to unlock it and hold the power button until the "Reboot/Shutdown/Airplane Mode" window appears and STAYS on the screen long enough for me to tell it to reboot.
8. After it reboots, the problems are gone and the touch screen returns to its proper functionality.
Has anyone had this problem before or know why it's happening? Or what can contribute to it?
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Huongnv said:
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Click to expand...
Click to collapse
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Garmy said:
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Click to expand...
Click to collapse
Flash a clean rom
U can use stock img with latest 4.4.2 sense 5.5 official or viper 4.4.2 sense 6
Sent from my HTC Droid DNA using Tapatalk
My screen started doing this, for me it is hardware failure. When you enable "show touches" from developer options, does it show 3-7 ghost touches? Mine is doing this (shattered screen and that is the only side effect, ha)
Sent from my HTC6435LVW using xda app-developers app