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
Related
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
Hello
I have a problem with the phone dialer and the rom based on CM ie CM10, AOKP or AOSP.
Let me explain: When a call is received, the display is on, normal, when the approach of the ear, the screen goes to sleep, ok on stock rom and stock based custom rom
However I could not get out of sleepping the screen on the CM based rom during a call :crying: even if i press home button or power button !
I always flash the included kernel, so i don't know where is my mistake. Am I alone with this failing ?
In advance, thanks for any help.
Regards
Any suggestion
Some CM (or was it just CM10?) based ROMs have issues with proximity sensor. A bug in the ROM.
Someguyfromhell said:
Some CM (or was it just CM10?) based ROMs have issues with proximity sensor. A bug in the ROM.
Click to expand...
Click to collapse
This is what seemed to me : the proximity sensor :crying:
But do you think if I get hw_config.sh from the stock ROM and I paste into a CM based ROM, it will fix the problem ?
Thx
elshur said:
Hello
I have a problem with the phone dialer and the rom based on CM ie CM10, AOKP or AOSP.
Let me explain: When a call is received, the display is on, normal, when the approach of the ear, the screen goes to sleep, ok on stock rom and stock based custom rom
However I could not get out of sleepping the screen on the CM based rom during a call :crying: even if i press home button or power button !
I always flash the included kernel, so i don't know where is my mistake. Am I alone with this failing ?
In advance, thanks for any help.
Regards
Click to expand...
Click to collapse
Hello friend!
It would be the same case?
http://forum.xda-developers.com/showthread.php?t=2070438
http://forum.xda-developers.com/showpost.php?p=31452830&postcount=1
JSS³ said:
Hello friend!
It would be the same case?
http://forum.xda-developers.com/showthread.php?t=2070438
http://forum.xda-developers.com/showpost.php?p=31452830&postcount=1
Click to expand...
Click to collapse
Actually I had not yet tried this kind of response because I was looking for confirmation that it was a problem with the proximity sensor.
Thank you for the suggestion, i'll take a look and keep you informed
Q&A for [ROM][OFFICIAL][Lollipop 5.0][AMAMI] PAC-ROM LP Beta-1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][OFFICIAL][Lollipop 5.0][AMAMI] PAC-ROM LP Beta-1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
tini mc
does it have the issue with the black bars showing when the phone heats?
tinimc said:
does it have the issue with the black bars showing when the phone heats?
Click to expand...
Click to collapse
oh sorry for not answering till now!
The bars shouldn't show, because thermal management works ok now
Corrupted recovery?
The last build of your ROM that I flashed was from 12.03.2015.
Since then I have a problem with my recovery - When I want to reboot into recovery i only got a bugged and flickery screen.
Everything else works fine...
Is there an .img file I could flash with Flashtool or some other way to fix it?
Regards, Emanon_
Emanon_ said:
The last build of your ROM that I flashed was from 12.03.2015.
Since then I have a problem with my recovery - When I want to reboot into recovery i only got a bugged and flickery screen.
Everything else works fine...
Is there an .img file I could flash with Flashtool or some other way to fix it?
Regards, Emanon_
Click to expand...
Click to collapse
Sure there is
https://www.mediafire.com/?r4vohak51440i83
You can try this one and see if it fixes your issue
But i do recommend that you flash the latest nightly
Thank you for your answer,
I justed flashed the boot.img with Flashtool but I still only get this buggy screen when I try to reboot into recovery..
Is there anything else I can try or do I have to make a factory reset?
Emanon_ said:
Thank you for your answer,
I justed flashed the boot.img with Flashtool but I still only get this buggy screen when I try to reboot into recovery..
Is there anything else I can try or do I have to make a factory reset?
Click to expand...
Click to collapse
Hmmm, then maybe you should try flashing a separate recovery. They're here in the forum, just search for some
After that, just flash the boot.img
I assume it will not overwrite the new recovery, since it didn't overwrite the old one
QuickTiles missing
hoi
i did a clean install and i miss some quicktiles:
- network mode: 2G/3G/2G+3G
- sound mode: sound on/sound+vibration/vibration only/silent
any hints?
Tom Mix said:
hoi
i did a clean install and i miss some quicktiles:
- network mode: 2G/3G/2G+3G
- sound mode: sound on/sound+vibration/vibration only/silent
any hints?
Click to expand...
Click to collapse
Are you updating from PAC KK version? Or do you mean you had those toggles on PAC LP already, but now they're missing after clean install?
came from KK
right, i came from KK
VERY CLEAN WiPED ALL! then FLASHED LP!
so i very miss these quicktiles!
on PAC KK i pulled down the quicksetting and tapped on 2G/3G/2G+3G to change the noetwork mode!
how do i quick-set my network mode now?
on PAC KK i pulled down the quicksetting and tapped on the sound tile to change the sound-profile
how do i quick-set my sound mode now?
Tom Mix said:
right, i came from KK
VERY CLEAN WiPED ALL! then FLASHED LP!
so i very miss these quicktiles!
on PAC KK i pulled down the quicksetting and tapped on 2G/3G/2G+3G to change the noetwork mode!
how do i quick-set my network mode now?
on PAC KK i pulled down the quicksetting and tapped on the sound tile to change the sound-profile
how do i quick-set my sound mode now?
Click to expand...
Click to collapse
sorry to tell you that the tiles you mentioned are not included in PAC LP
however, if you get Xposed, you can install gravitybox and get the tiles you want back (it works, I tested it just now )
well...
thx 4 the xposed hint:good:
OpenVPN
hoi board
i did some further testing with my amami running pac-lp
unfortunately i am not able to install openvpn. neither openvpn connect nor openvpn for android or openvpn-installer
on the install screen it is not possible to press the install button. cancel button works though ...
it is the same strange behavior on all three apks. on an other device with CM12 nightly it works.
any suggestions?not PAC related:victory:
Tom Mix said:
hoi board
i did some further testing with my amami running pac-lp
unfortunately i am not able to install openvpn. neither openvpn connect nor openvpn for android or openvpn-installer
on the install screen it is not possible to press the install button. cancel button works though ...
it is the same strange behavior on all three apks. on an other device with CM12 nightly it works.
any suggestions?
Click to expand...
Click to collapse
can you please post a screenshot? I just tried installing "openvpn for android" and it got installed. Didn't try to set up a network though
thx 4 the response
actually i am flashing the latest nightly. on troubleshooting i found that i am on pac_amami-lp-Nightly-20150327
now i will upgrad to pac_amami-lp-Nightly-20150406 and report back.
just a minute.
UPDATE:
ok. it seems unrelated to openvpn as i cant install any apk anymore. damn!
a screenshot is not very helpfull because i just cant press the install button. no effect. cancel still works.
any idea?
Tom Mix said:
actually i am flashing the latest nightly. on troubleshooting i found that i am on pac_amami-lp-Nightly-20150327
now i will upgrad to pac_amami-lp-Nightly-20150406 and report back.
just a minute.
UPDATE:
ok. it seems unrelated to openvpn as i cant install any apk anymore. damn!
a screenshot is not very helpfull because i just cant press the install button. no effect. cancel still works.
any idea?
Click to expand...
Click to collapse
ah I see what's happening.
This is actually not a bug. You can't install apps because the device recognized you as a bad guy :good:
KIDDING! this is not the real reason
This happens when you have an app that puts an overlay on the screen, like HALO from Paranoid Android.
To solve this, check what apps you installed, and uninstall/disable the apps that put an overlay on the screen. Then it should work :victory:
well...
i will try tomorrow and report back.
good night!
report:
well it was too late yesterday i guess.
i made a restart today, tried again and it worked.
even the OVPN connection worked. and im on the latest PAC nightly
btw: BRiNG BACK PACK iN BLACK!
i dislike this CM12 light material stuff soooo much........
native QuickTiles in PAC
are there any plans to natively bring back the quicktiles to PAC rom LP as it was in PAC KK
i am not that happy with xposed LP yet
Tom Mix said:
i will try tomorrow and report back.
good night!
report:
well it was too late yesterday i guess.
i made a restart today, tried again and it worked.
even the OVPN connection worked. and im on the latest PAC nightly
btw: BRiNG BACK PACK iN BLACK!
i dislike this CM12 light material stuff soooo much........
Click to expand...
Click to collapse
Good to know it worked at the end
I don't think PiB will make a come back, because it's not needed anymore, due to the theme engine by CM. You should easily find good black themes in play store
Tom Mix said:
are there any plans to natively bring back the quicktiles to PAC rom LP as it was in PAC KK
i am not that happy with xposed LP yet
Click to expand...
Click to collapse
I'm not sure if the tiles will return, but I'll ask the team and report back
EDIT:
So i did some digging, and it seems that using profiles will allow you to set network mode and sound mode , so you can setup profiles for each data connection mode and sound mode you want, them switch between them easily with the profiles tile.
profiles and next Q
ah i see: set a bunch of profiles ... very clever :silly:
ok. will try that.
next question:
i guess it is not PAC related but: how can i TOTALLY DiSABLE/REMOVE this second user / guest thing?
and can one give a logic solution, why i have to have such an option by default WTF!
i hardly see the advantage for LP compared to KK
the only thing ist about: animations, animations, design, material, animations
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
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.