Develop Bugs

[Q] Screen Problem NEXUS GSM

Hello. I have a problem whit my galaxy nexus maguro device. When i install something different then stock google images 4.1.2 or stable "cm-10.0.0-maguro.zip" i have a problem whit screen when i'm during my phone call. Every time i install something different for exp: stock 4.2.1 or 4.2.2 or every custom rom (xylon,pa,xenon,slim bean etc. etc. ) and when i starting a conversation my screen of course is off but when i geting off my phone from ear screeen whant to turn on and it is almost every single time i having a phone call.I was trying every basband,rom, kernel and always i the same result -screen issue. Of corse when i'm on 4.1.2 or cm-10.0.0-maguro.zip there is no problem. so my question is WTF ? Please try to forgive me for my english - this is not my thing

?
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?

?
ryza666 said:
I've tried auto-brightness off and on etc. there is no solution .... fuc.... any sugestion ?
Click to expand...
Click to collapse
And i've changed animation window to 0.5 and it's not working. PLS help MEEEEEEEEE !

Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S

irizwan said:
Ok so from what i understand you mean that the screen doesn't turn on after you hang-up a call? or during a call? if it's during a call make sure you aren't covering the sensor on the right side of the ear piece .. also if thats not that problem it might be highly possible that your proximity sensor is broken :-S
Click to expand...
Click to collapse
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?

ryza666 said:
So if my proximity sensor is broken why i don't have a problem whit this on CM 10 ( stable realese ). Screen doesn't turn on if the person from the other side hang-up me first. An update of my screen problem : i'm on Paradigm 3.1 right now and diamond044 kernel from AK and so far my screen doing great ( the autoBrightness is turn on ). Xylon, Xenon HD,Puity etc - every kernel, clean install bla bla bla thre is a screen issue... I don't get it ?
Click to expand...
Click to collapse
And sorry for your "quick" response:angel:

Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus

bk201doesntexist said:
Are you using stock dialer?
Try: Upgrade to 4.2.2.
And paste a logcat (people need to start doing this before opening a thread)
Sent from my Nexus
Click to expand...
Click to collapse
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case

ryza666 said:
I always use stock dialer. Before I've done a lot of up pure upgrade to stock 4.2.2 and downgrades to 4.1.2. and I've installed every coustom rom on stock 4.2.2 or 4.2.1 and result is the same. Like as I said only Cm 10 stable i out of screen issue. I've installed yesterday CM 10.1 M3 and try some thing with another dialer from market and there is a chance of success. And what about catlog - i will try but as you see I don't have a lot of time to solve my problem.... work work work. I'm grateful for your interest of my case
Click to expand...
Click to collapse
Is your screen protector covering the proximity sensors? My screen protecter once covered them and I had the same issues but when i removed it, it worked again

If you are using a custom kernel, try up-ing you min screen off setting in trickster mod.
I used to get a lot of these problems. But not any more since I am on Diamond series of AK kernel.
I am using these settings: http://forum.xda-developers.com/showpost.php?p=38030897

[Q] AOSPA black screen issue on find 7 QHD

I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?

I have same issue with CyanogenMod in all versions include M8
some discussion about this problem is here http://forum.xda-developers.com/find-7/find7-development/tutorial-how-to-install-cyanogenmod-t2801982 but I still can't find solution

All the CM11 based ROM has the black screen issue. Only Gummy ROM doesn't at the moment. I'm not discouraging anyone to use CM11, but for now, use Gummy ROM if you really don't want to use ColorOS and also don't want the black screen issue.

Same Issue on PA 4.4.2
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?

... it would help if someone could give me a last_kmesg and logcat

ayysir said:
... it would help if someone could give me a last_kmesg and logcat
Click to expand...
Click to collapse
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg

Gummy rom does not have this issue.

Sebring5 said:
Gummy rom does not have this issue.
Click to expand...
Click to collapse
thats swell

Entropy512 said:
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg
Click to expand...
Click to collapse
my mistake

dmesg: http://pastebin.com/XVEszqrJ
logcat: http://pastebin.com/SDH7FXQv
I think it has something to do with thermal throttle and screen dim.
This logs are from CM.

rroohh93 said:
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?
Click to expand...
Click to collapse
http://www.oppoforums.com/threads/rom-aosp-find7a-find7-team-gummy-rom.15593/

Problem Fixed!
mestermagyar said:
I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?
Click to expand...
Click to collapse
So CM pushed some fixes to address this black screen issue, a friend of mine already compiled them into a kernel, this kernel is compatible with any CM based ROM like PA or Cyanogen.
Just flash it and goodbye to black screen issue.
http: // aospal.hostingsharedbox. com/ayysir/find7/ kernel/ParanoidAndroid-find7-kernel-signed. zip

Problems with CM 11

Hi xda!
I'm writing this thread because in those days, after flashing the latest cm11 nightly, I found some HUGE problems and basically all of them are related to the dialer.
Dialer's Problems:
- when the call starts i'm unable to see the dialer screen, the phone seems to be locked but when i press the ac button nothing happens, so re-pressing it is the solution but instead of the dialer screen it pops out the lock screen, then if i want to come back to the dialer i have to swipe down the notification bar
- while calling i'm unable to shut down the call and also i can't use the speaker, the dialer and so on
I've made a little video, you can see it here-> on yt /watch?v=NbAmJefyRZ8
(inverted colors lel)
Really need some help, thanks in advance!
(the model is the n7100)

Have you tried a KK AOSP ROM? How about a stock-based KK ROM?

audit13 said:
Have you tried a KK AOSP ROM? How about a stock-based KK ROM?
Click to expand...
Click to collapse
Nope, never tried an AOSP just because i didn't need to, let me explain everything.
So it started with me flashing the blisspop rom because I wanted to give back life to my phone, which was stock samsung KK with root. Everything was working really fine, a super smooth ROM (with lollipop woooaaaah) but i found a super huge bug(?) i really don't know what was going on, basically there were not a storage, so the camera, whatsapp media and so on were not working.
So i started googling for a solution, which doesn't exist at all.
And so here we go with cyano.
Please do not make me flash a samsung stock, i really hate their ROMs, they are super heavy with thousand of useless applications

screen flickering or glitches on custom Roms (LOS & AOSP )

screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?

A logcat sent to the ROM dev might be an idea.

Kaleem_qadir said:
screen flickering or glitches on custom Roms like OMNI,PIXEL, Resurrection remix etc have same issue.... any solution?
Click to expand...
Click to collapse
Wrong firmware

XDRdaniel said:
Wrong firmware
Click to expand...
Click to collapse
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?

Kaleem_qadir said:
thanks for reply
i have oneplus 3 (A3003) .... which rom you suggest?
Click to expand...
Click to collapse
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.

tnsmani said:
You can have any ROM so long as you have the matching firmware. Check in the ROM's thread.
Click to expand...
Click to collapse
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?

Kaleem_qadir said:
flashed 3/3T lineage and AOSP Roms. any difference between and 3T roms?
Click to expand...
Click to collapse
Unless it says Unified or 3/3T, they are different and flashing the wrong one can brick your phone.

Still not solving
I am still having issues. My nav bar gets a mirror effect on the uperside of the screen
I have a Oneplus A3000

Hello i have the same issue have you got any solution ?

I replaced my crack screen last month and last night I tried flashing AOSIP rom (From latest Open Beta) and got screen flickering and glitches to the point it was unusable. Wiped my phone clean again and tried RR rom and got the same flickering and glitches. Now I'm back to latest Open Beta. I wonder wether my new screen is the problem that caused me unbale to flash aosp roms? Because before my screen cracked I tried almost every rom and it's fine. Any idea guys?

I have the same problem, and I do too had my screen replaced, but some folks on OnePlus forum said that never replaced the screen
I tried many diferent versions of the firmware, and nice looking none fix for me

I have the same problem too, I've tried many kernels and many ROMs, it seems that only Sultanxda's ROM and Official ROM can be used. I've tried to compile MoKee with Sultanxda's Kernel source, it worked perfectly too. So I think that there maybe something kernel related is broken, and only Sultanxda fixed that. Maybe you could try it.

Thanks for reply . Los 14.1 and miui 9 are also ok

I've the same issue, and I think for the same cause because I replaced my cracked screen also, maybe OnePlus 3 have something like knox on samsgung where it'll be broken when rooted, Waiting to see if there's some kind of a solution because if the OOS (or OOS Beta) works fine it could be a kernel or firmware issue.

So it looks like the problem is with the replacement screen. Funny, because this is the 2nd time I replaced the screen (dont ask) but I didn't have flickering problem with the first one. Hopefully any talented devs can figure out the issue and resolves it, will gladly help however I can.

The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.

Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
thanks a lot .. i wil try this weekend for sure

Lukedyue said:
The change was merged:
h t t p s://review.lineageos.org/#/c/208861/
Maybe you could try the next build of LineageOS to see if the issue was fixed.
Click to expand...
Click to collapse
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.

rsm23 said:
I've just installed it and still the same issue (The 2018-03-05 version)
N.B :
You can activate "Show surface updates" from the Developer Options Menu and the screen will not have those glitches anymore, because I realized that the glitches will go away whenever you update the screen.
Click to expand...
Click to collapse
Well, by "next" I mean builds from 20180309 onwards.

Tried the 12-03 release, it does fix the screen errors, touch stop working if the screen is turned off, I need to reboot to it work again

black display and unresponsive on pie roms

Hi, I'm facing this issue with my oneplus 3 on custom roms based on android pie..it still happens and has become very difficult for me to use. im very eager to use pie on my device :/ .I've tried Havoc 9.0, Nitrogen OS 9.0, Pixel Experience and even skydragon but it still happens. Whenever the phone goes to sleep or i lock it, and then when i try to wake it up from the lock using either fingerprint or power button, the screen lights up in black and the two capacitive buttons light up, i can hear a lock screen sound also, but the display stays black. but the rom works like it should until the display doesnt turn off.. i have to reboot the device completely to solve it.. currently im on oxygen os 5.05. someone please help

Is your display original or has it been replaced? I have same problem because i replaced broken original LCD with cheap one from eBay.

I agree too facing the same issue and it's seems to be because of the duplicate display panel. I too replaced my display panel with a duplicate one recently and facing this issue (pressing the power button, but screens turns to black but pressing the power button again and again turns it on) since then. Not only pie ROM but also on Oreo custom roms. Only pie ROM that seems to be working is Nitrogen OS. There may be some problem or mismatch with display drivers. Also the profiles like SRGB and others are not working.
No problem on OOS 5.0.6

yeah man.. its a duplicate display :/ is there any workaround for this?

I asked in a telegram group. A person said a commit is required for third-party display to work.
I am not too much in development thing. So if anyone from you can search for it. That could help.
---------- Post added at 06:04 AM ---------- Previous post was at 05:55 AM ----------
http://github.com/LineageOS/android...mmit/8e9f68f01764d96669f6040bf9ae0c8ea4ec55e1
A person on telegram gave me this link to the commit.

I forwarded the commit and the message to Dev of Havoc OS. He said he will ask the holy angel for what he can do.
Hope he looks after it.

@pantu99 @stepi1
The latest skydragon rom comes with the fix for the panic we are facing. You can test it. I can't test right now.
Let me know too, if it works or not.

Piyush lalwani said:
@pantu99 @stepi1
The latest skydragon rom comes with the fix for the panic we are facing. You can test it. I can't test right now.
Let me know too, if it works or not.
Click to expand...
Click to collapse
great ! i shall test it right away.. hope it works.

just installed the latest build of the rom.. nope still the same issue..
pantu99 said:
great ! i shall test it right away.. hope it works.
Click to expand...
Click to collapse

pantu99 said:
just installed the latest build of the rom.. nope still the same issue..
Click to expand...
Click to collapse
Seems some additional commits are required.
Can you ask developer of Franco kernel about the comitts maybe he can help.

Piyush lalwani said:
I agree too facing the same issue and it's seems to be because of the duplicate display panel. I too replaced my display panel with a duplicate one recently and facing this issue (pressing the power button, but screens turns to black but pressing the power button again and again turns it on) since then. Not only pie ROM but also on Oreo custom roms. Only pie ROM that seems to be working is Nitrogen OS. There may be some problem or mismatch with display drivers. Also the profiles like SRGB and others are not working.
No problem on OOS 5.0.6
Click to expand...
Click to collapse
So OOS 5.0.6. doesn't have any issues with cheap display replacements?

j03x2 said:
So OOS 5.0.6. doesn't have any issues with cheap display replacements?
Click to expand...
Click to collapse
Yes I am using it currently. And Franco kernel also doesn't has any problem.
Other kernel give problems.

NitrogenOS also works. Guys please find a workaround, very hard to find better displays in market

Installed NitrogenOS 8.1 with fk-r39-anykernel2.zip (Franco Kernel) and everything works just fine now.
Interestingly, the problem persists in TWRP (I cannot let the display sleep during backup or restore otherwise, I cannot switch the display back on).

j03x2 said:
Installed NitrogenOS 8.1 with fk-r39-anykernel2.zip (Franco Kernel) and everything works just fine now.
Interestingly, the problem persists in TWRP (I cannot let the display sleep during backup or restore otherwise, I cannot switch the display back on).
Click to expand...
Click to collapse
Nitrogen OS pie didnt had the problem with stock kernel too
Try it.
Fkr39 why not the latest?

Piyush lalwani said:
Nitrogen OS pie didnt had the problem with stock kernel too
Try it.
Fkr39 why not the latest?
Click to expand...
Click to collapse
There is no suitable version of Xposed framework for NOS 9 (pie).
Fkr44 (latest version of the kernel) showed more lag time before the screen turns on (like 2-3 sec).
Had the best experience with the older kernel.

Any fixes or working rom guys ? I really want pie in my OnePlus 3

Have you tried Resurrection Remix?
I had a similar issue with Havoc even with the original screen. So far, RR has been fine.