I've tried several stock KK roms and every single one is giving me same issue.
The rom itself boots up just fine. However, once the screen turns off and I turn it back in, it slowly turns on and it's just white or colored lines. The touch screen is still responsive, I can hear the sounds but I can't see a Damn thing unless I hard reset.
There are others like me, in Cloudy's roms, even Smiley's but we just get ignored or I believe I was told that since its just me and a few others it's not worth addressing.
So has anyone had this problem and have you fixed it? Can we get some TMO users to flash one of these roms so people know what I'm talking about? I need help guys.
You're my only hope.
Related
Ok so my hero keep turning off by itself. This is not the first time it happen, it'll be on then it will just turn off by itself. Even worse sometimes the led light will be flashing for a new message and when I press the menu button to unlock it, it restart automatically. It mostly restarts itself when the screen is dark and i always press menu to bring up the light or to unlock it. Is this mean my phone is now defective ? I mean this happened before on some other 2.1 ROM too so idk what it is. Can someone tell me how to fix this????? I've tried almost all 2.1 Roms Aloysius, DC 2.07.2, Trevs Damage, ZenHero , RegawMod (themed) and Fresh 2d. the only rom that didnt restart my phone was the Fresh 2d with the very first audio fix by Avalaunchmods but i already erased that out of my computer.
Hmmm, not much to go on. I had experienced a similar issue back on early ROMs, but it was so infrequent I never really cared.
Try a Nandroid Backup and then flash to a 1.5 ROM and see if it continues, if so then yes the phone may be defective.
Also try different 2.1 ROMs here, and let us know if anything changes.
Dude, seriously do you need to have such a big font? Its not necessary....
i didn't catch that, what did you say?
lol mr big font
this happened to me last night, i wasnt even touching the phone and this happened, but its been the only time and ive been using 2.1 roms for a while now...i think this even happened once or twice when i was on stock...
coming from windows mobile, im used to things like this.
This happens on my sisters stock phone frequently I don't really care to look at it though.
Big fonts aren't nice. Stop using them
Try a different ROM. You may even want to revert to stock for awhile, if it keeps rebooting you should return the phone for a non-defective handset.
LOL @ RTessi
danknee said:
Try a different ROM. You may even want to revert to stock for awhile, if it keeps rebooting you should return the phone for a non-defective handset.
LOL @ RTessi
Click to expand...
Click to collapse
My sis's is on stock, and she has the problem
Funny thing is my phone is the only one without problems, and it's the only one that's rooted.
i don't know what we're yelling about loud noises
i got it fixed now, i think, i've had Fresh 2.0d for a few days and this problem is gone. oh and sorry for the big font lol i did this post in class on my phone and i didnt preview or look at what font i was using
Apparently there were some issues with it so they took the rom upgrade down.
It's been working fantastic for me on par with most of the custom roms i've run.
I have noticed a slight decrease in sensitivity but i actually was happy for it. it made typing easier for me and i'm not always accidentally opening apps...
At least it seems like they're not turning a blind eye to the issues that people still have.
Huh, isn't that weird? I wonder what issue is so bad that they suddenly decide that they must fix it? Maybe the aformentioned sensitivity? I agree, OP, I like the stock ROM just as much as a custom ROM. Nearly everything seems to work right. The only issue I have is Sense freezing a few times when I go to a someone's message to respond to it. Though, I have never had it freeze so bad I had to take the back cover off.
In another thread they are saying it was taken down temporarily because of downloading problems people are having. Not anything to do with the actual rom itself. They will be putting the same rom back up.
I have a pretty big problem that started about a week ago. Basically, my phone suddenly stopped showing anything on screen. From when I start it, to when the OS boots, to fastboot, to recovery....all it shows is a black screen, occasionally with three vertical red lines. The touch screen is working completely fine, though.
I'm still learning when it comes to custom OSes, but at first I thought it might be some problem with CM6 RC1. However, since every single thing on the phone shows a black screen, I worry that it's actually more of a hardware issue. Hopefully the collective knowledge of the internet can help me figure out and possibly solve this issue.
I guess to see if it's the OS, I'd like to know if there's a way to make a nandroid backup and flash a new rom through adb? And if that doesn't work, what should I do?
MyTouch3G/Sapphire 32B
CM6 RC1
shoekyou said:
Basically, my phone suddenly stopped showing anything on screen ....all it shows is a black screen. The touch screen is working completely fine, though.
Click to expand...
Click to collapse
Explain to me how you know that the touchscreen works if you have no video.
It sounds like a hardware issue to me.
Did you try another ROM?
Maybe cm6 just didn't install right, it is still a release candidate, for a replacement ROM I would suggest cyanogenmod RC2 if you're really into FroYo, but if you want stability, cyanogenmod 5.0.8 is a great, you might also want to try Chromatic 3.9.1, based on cm 5.0.8
Binary100100 said:
Explain to me how you know that the touchscreen works if you have no video.
It sounds like a hardware issue to me.
Click to expand...
Click to collapse
I can feel it vibrate when I unlock the phone (which I can still do because I've done it so many times). I know the OS is running, and it still receives calls and texts fine. Just showing absolutely no video.
And I haven't tried another ROM because there's no video in recovery or fastboot either, which makes me think it's a hardware issue sadly. If there's a way to flash a ROM through the PC I'd give it a shot though.
There is a way to do it through recovery but I can't remember how at the moment. Until I do, have you considered using ddms.bat and use the screen capture (constantly refreshing) to navigate and use ROM Manager with Clockwork Recovery to flash your rom?
I'm about 90% certain that it's a hardware issue though.
Hi,
many people still claim there isn't such a problem but there IS:
After ending a call the screen stays off and can't be turned on again. Hardwarekeys don' t do anything.
Only option: Hold the phone in bright light or take battery out -.-
I tried the most popular roms here (NAND&SD)
In WinMo everything works fine.
So here i want to show that not only i but many others suffer by this issue.
Hopefully some real CHEFS/Devs realize this.
Making tons of senseless customisations and graphics tweaks isn't enough to be a real Dev...
Here are some of the threads concerning this issue so far:
http://forum.xda-developers.com/showthread.php?t=1061481
http://forum.xda-developers.com/showthread.php?t=965123&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=735906
http://forum.xda-developers.com/showthread.php?t=946012
http://forum.xda-developers.com/archive/index.php/t-946012.html
srmemnoch2 said:
gsm.proximity.enable=false
you can include this in your build.prop file, locate in /system and reboot.
this never turn off screnn during calls..
but i think only run in froyo
im desperate i want update to gingerbread but this code do not run on ginger.
ragards
Click to expand...
Click to collapse
this really helps! But now the screen stys on all the time, must be careful not to end the call by touching the screen XD... But it's better than having a blocked phone.
But still the issue itself isn't solved ...
You could try http://www.xda-developers.com/android/proximity-sensor-re-calibrator-for-desire-hd/ this?
yes tried this already before, thanks, but didn't work.
I know this problem sounds weird to those who don't have this issue but it's real (i'm not crazy XD) The hardware is also working correctly as on WinMo everythiong's fine
I'm been having this problem since my first rom. I actually thought it was just my phone. It drives me crazy, as I found that plugging it in gets the screen to return. Very annoying!
Sent from my HD2 using XDA App
Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.