Develop Bugs

[Q] CyanogenMod 11 M7 - Screen very dim during Restart/after Shutdown?

I recently installed CyanogenMod 11 M7 on my LG G Pad 8.3, almost everything is working perfectly.
Whenever I restart or shut down/turn back on (i.e. Cold Boot) the screen is very dim, you can barely see the CyanogenMod boot animation. Then the lock screen is barely visible. If I enter my pin, then turn on/off the screen 1 or maybe two times it's normal brightness and the problem is fixed.
I need to do this every time after a cold boot though. I'm living with it because how often do you restart phones/tablets? But it's an odd one.
Any ideas how to fix this would be appreciated? Thanks.

bradavon said:
I recently installed CyanogenMod 11 M7 on my LG G Pad 8.3, almost everything is working perfectly.
Whenever I restart or shut down/turn back on (i.e. Cold Boot) the screen is very dim, you can barely see the CyanogenMod boot animation. Then the lock screen is barely visible. If I enter my pin, then turn on/off the screen 1 or maybe two times it's normal brightness and the problem is fixed.
I need to do this every time after a cold boot though. I'm living with it because how often do you restart phones/tablets? But it's an odd one.
Any ideas how to fix this would be appreciated? Thanks.
Click to expand...
Click to collapse
Try AIC Kernel, that fixes gamma...
on every ROM flash, GAPPS, also i flash AIC, so its normal...
see the thread: http://forum.xda-developers.com/showthread.php?t=2741405

Thanks Jhon998. Just a few quick questions please:
* What is AIC Kernel exactly?
* Will it interfere with CM11 M7's operation?
* Will it interfere with CM11 OTA monthly updates?
I'm a bit worried about breaking something adding third party code into the mix.
* I presume I need to flash aickernelinstaller.zip and not AIC_kernel_flashable.zip? The instructions say to use AIC_kernel_flashable.zip but I think it's aickernelinstaller.zip that supports CM11 coming from stock 4.4.2.

the installer have an option to choose from whether you have a stock or aosp, and if you choose aosp it just fix the gamma (brightness), but the problem that you have to flash it on every ROM flashing, like monthly, not like gapps, in my hand it is not a problem, but I am using stock with aic kernel on top...
Sent from my LG-V500 using Tapatalk

Jhon998 said:
the installer have an option to choose from whether you have a stock or aosp, and if you choose aosp it just fix the gamma (brightness)
Click to expand...
Click to collapse
Got it. Thanks.
Jhon998 said:
but the problem that you have to flash it on every ROM flashing, like monthly
Click to expand...
Click to collapse
That sounds like a pain. To be clear, if I were to install a CM Milestone Over-the-Air update I'd need to re-run AIC Kernel?
Thanks again.

bradavon said:
Got it. Thanks.
That sounds like a pain. To be clear, if I were to install a CM Milestone Over-the-Air update I'd need to re-run AIC Kernel?
Thanks again.
Click to expand...
Click to collapse
As i noticed it flashes a kernel within the ROM... obviously..

bradavon said:
I recently installed CyanogenMod 11 M7 on my LG G Pad 8.3, almost everything is working perfectly.
Whenever I restart or shut down/turn back on (i.e. Cold Boot) the screen is very dim, you can barely see the CyanogenMod boot animation. Then the lock screen is barely visible. If I enter my pin, then turn on/off the screen 1 or maybe two times it's normal brightness and the problem is fixed.
I need to do this every time after a cold boot though. I'm living with it because how often do you restart phones/tablets? But it's an odd one.
Any ideas how to fix this would be appreciated? Thanks.
Click to expand...
Click to collapse
Maybe it helps to flash 4.4.2 compatible TWRP from here http://forum.xda-developers.com/showthread.php?t=2551499. Did you try that?

nsmart said:
Maybe it helps to flash 4.4.2 compatible TWRP from here http://forum.xda-developers.com/showthread.php?t=2551499. Did you try that?
Click to expand...
Click to collapse
Thanks for the heads up on a new compatible TWRP release Nsmart. I just have. It didn't make a difference unfortunately. I was already running TWRP 2.7.0.1. I guess 2.7.1 hasn't fixed this.
Hopefully Cyanogenmod will fix it. I've decided not to try AIC Kernel. I'm wary of installing third party code into third party code.

Done!
That worked for me! Thank you. I had some problems with rooting the v50020D, when i got it, i got the dim screen problem. Now it fixed. Ty very much.

If you're on cm11... flash Mani kernel.
Worked for me ^^
Unfortunately it's laggy when compared w/ dynkernel.
I only reboot if problem, I can do w/o the lag
Sent from my Kin[G]_Pad ™

bradavon said:
Thanks for the heads up on a new compatible TWRP release Nsmart. I just have. It didn't make a difference unfortunately. I was already running TWRP 2.7.0.1. I guess 2.7.1 hasn't fixed this.
Hopefully Cyanogenmod will fix it. I've decided not to try AIC Kernel. I'm wary of installing third party code into third party code.
Click to expand...
Click to collapse
It's safe, it won't touch anything other than fixing that gamma issue if you haven't flashed the 4.2.2 base before...

Thanks.
How do you mean "flash the 4.2.2 base before"? I was on LG stock Android 4.2.2 then OTA to 4.4.2 and now CM11 M8 (pretty sure it's M8, would need to check).

The 4.4.2 OTA updates the firmware on the device. This firmware is what causes the dimming issue on most of the AOSP based roms (like CyanogenMod). So if you want to avoid the dimming issue and run CM you should flash the following rom first (warning it will take quite a while and make sure to double check the md5 since this is a really big file). The 4.4.2 firmware update also gets rid of the 7 lights bug, so that issue will reappear on your tablet when you go back if you had it before.
Here is the thread detailing the 4.2.2 base rom:
http://forum.xda-developers.com/showthread.php?t=2719411
Basically backup any files you care about, flash the 4.2.2. base rom and then flash CM again. This will solve the screen dim issue on AOSP based roms.

AIC kernel fixed that problem for me

Bill_windows said:
AIC kernel fixed that problem for me
Click to expand...
Click to collapse
Yes, this could fix the problem as well...

Im completey stock no root....and i have this problem
Sent from my LG-V500 using XDA Premium 4 mobile app

Oneplus 3 Problem after unbrick

Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!

Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once

RiskTaker10 said:
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Click to expand...
Click to collapse
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..

Puddi_Puddin said:
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Click to expand...
Click to collapse
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?

RiskTaker10 said:
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
Click to expand...
Click to collapse
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.

hrishikeshgramani said:
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
Click to expand...
Click to collapse
Unfortunately that is out of the question, there is no Service Center for Oneplus where I live so I cant get it checked ASAP

Puddi_Puddin said:
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
Click to expand...
Click to collapse
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?

RiskTaker10 said:
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
Click to expand...
Click to collapse
You can always try..

Puddi_Puddin said:
You can always try..
Click to expand...
Click to collapse
Okay thanks good citizen of XDA I'll try to flash a custom rom and I'll try to report back here ASAP

Random shut down/black screen after around 5 seconds on Oreo firmware

Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justin

Cry_Cry said:
Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justinhttps://www.youtube.com/watch?v=
Click to expand...
Click to collapse
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately

yldlj said:
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately
Click to expand...
Click to collapse
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?

Cry_Cry said:
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?
Click to expand...
Click to collapse
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.

yldlj said:
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.
Click to expand...
Click to collapse
So basically there is no fix for my problem?

Cry_Cry said:
So basically there is no fix for my problem?
Click to expand...
Click to collapse
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.

yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?

Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Are you SOFF? What's your CID?

yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?

Cry_Cry said:
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?
Click to expand...
Click to collapse
Nope flash RUU and that's it.

I get a lot of random crashes and power offs since I've upgraded to Oreo. It's really been driving me nuts.
Can't wait for the OP6 or U12+ to come out - I really need a new phone.

Persistent app running in background

Running VPN in background and that irritating power notification won't go away and I don't want to block notification from Android system.
I am rooted and new to Oreo and Motorola so what do I need to do to stop that notification?

Josh McGrath said:
Running VPN in background and that irritating power notification won't go away and I don't want to block notification from Android system.
I am rooted and new to Oreo and Motorola so what do I need to do to stop that notification?
Click to expand...
Click to collapse
I only found a way using an app. This one is decent and open source. Luckily in Oreo 8.1 you can hide those notifications natively. So if you're on Tmo or Sprint and feel adventurous check out Aosip, it's 8.1, runs like a champ, and isn't bloated.

41rw4lk said:
I only found a way using an app. This one is decent and open source. Luckily in Oreo 8.1 you can hide those notifications natively. So if you're on Tmo or Sprint and feel adventurous check out Aosip, it's 8.1, runs like a champ, and isn't bloated.
Click to expand...
Click to collapse
I was actually considering that rom. Thanks for the link, the z2 has some really bad bugs in sms that drive me insane so I'm welcoming the change in roms.

Josh McGrath said:
I was actually considering that rom. Thanks for the link, the z2 has some really bad bugs in sms that drive me insane so I'm welcoming the change in roms.
Click to expand...
Click to collapse
Something happened when I flashed that aosip rom. Very wrong. It 9008 bricked me ??

41rw4lk said:
I only found a way using an app. This one is decent and open source. Luckily in Oreo 8.1 you can hide those notifications natively. So if you're on Tmo or Sprint and feel adventurous check out Aosip, it's 8.1, runs like a champ, and isn't bloated.
Click to expand...
Click to collapse
Did you not have any issues with that rom?

Josh McGrath said:
Did you not have any issues with that rom?
Click to expand...
Click to collapse
Not anything that isn't listed in the bug section, which honestly doesn't affect me much anyway. I'm on TMO so LTE works fine for me, and I think they might have a handle on it for Sprint users. I like the rom, and I'm anxious for an update honestly. I just installed the Pantheon kernel on top of that. Considering that when my phone was stock I had random reboots for no apparent reason, and wifi connectivity drops as well, Aosip solved those issues. I'm quite happy with the whole setup now.

Josh McGrath said:
Something happened when I flashed that aosip rom. Very wrong. It 9008 bricked me
Click to expand...
Click to collapse
Are you on TMO or Sprint? Did you flash the 27.1 prep zip?

I am tmo and I was already on the 27.1 stock cause I had to flash it cause I lost imei and baseband.
After flashing the aosip zip, it said completed in twrp and then said "no os installed do you want to reboot" and I hit yes thinking worse case I could boot into twrp and start over thinking maybe the aosip was wonky and maybe not showing an os if there was one.
Tbh the phone was giving me hell with numerous things like Bluetooth would refuse to play through the bt headphones and starting the same day, it would not turn off speaker phone on calls.
I am nervous but I really want to flash this but I don't want a brick again either

Josh McGrath said:
I am tmo and I was already on the 27.1 stock cause I had to flash it cause I lost imei and baseband.
After flashing the aosip zip, it said completed in twrp and then said "no os installed do you want to reboot" and I hit yes thinking worse case I could boot into twrp and start over thinking maybe the aosip was wonky and maybe not showing an os if there was one.
Tbh the phone was giving me hell with numerous things like Bluetooth would refuse to play through the bt headphones and starting the same day, it would not turn off speaker phone on calls.
I am nervous but I really want to flash this but I don't want a brick again either
Click to expand...
Click to collapse
The prep zip is down towards the bottom of the OP in the Aosip thread, also in post #2 it is a must in order to flash Aosip. If you didn't flash that, regardless of whether you were on stock 27.1 then that is where you went wrong.

41rw4lk said:
The prep zip is down towards the bottom of the OP in the Aosip thread, also in post #2 it is a must in order to flash Aosip. If you didn't flash that, regardless of whether you were on stock 27.1 then that is where you went wrong.
Click to expand...
Click to collapse
Thanks, it actually looks like I missed 2 steps, including the fastboot -w. I've never installed any aosp rooms so I guess I'll chalk this up to a learning experience.

has anyone tested this?

What are your thoughts? does it boot for you too? I work on a lot of stuff for various devices in the background and behind the scenes..
Just curious if other people are having success with some of my projects as well.
Unofficial pie RR
Edit: link removed

AnierinB said:
What are your thoughts? does it boot for you too? I work on a lot of stuff for various devices in the background and behind the scenes..
Just curious if other people are having success with some of my projects as well.
Unofficial pie RR
https://androidfilehost.com/?fid=11410963190603910079
No gapps included
Click to expand...
Click to collapse
Hey brother,
just seen your RR-Rom on AFH and found this thread. I will try in a bit to see if it is booting. Thanks for for this...
EDIT: forgot to ask, i assume this is built on faygi's LoS build? I am downloading now to test. RR is my favorite and glad to see this...

_Sherrif said:
Hey brother,
just seen your RR-Rom on AFH and found this thread. I will try in a bit to see if it is booting. Thanks for for this...
EDIT: forgot to ask, i assume this is built on faygi's LoS build? I am downloading now to test. RR is my favorite and glad to see this...
Click to expand...
Click to collapse
Yes, it's built with the same trees and dependencies so expect the same device side bugs.
I also built XenonHD pie but I accidentally set it to only include common.mk which resulted in missing latinIME (aosp keyboard).
I totally spaced out and forgot that common_full_phone.mk inherits common_full and common_full.mk inherits common.mk ?
I'll recompile XenonHD tonight with the fix tonight and make a thread for it on this forum as long as someone else doesn't already have plans to maintain it.

@AnierinB,
OK, i just installed the ROM and it would not boot. I wipe and factory reset, not boot. Then i wiped, factory reset and FORMATED data, still no boot. I only tried to install and boot without any gapps, ROM only. Not sure. I get to the RR logo and it tries to boot for about 2-3 minutes then re-boots back to TWRP.
Also, i found your HAVOC-OS build, i think it was yours anyway, if i remember correctly. I tried as above with HAVOC-OS and had the same result. The only thing i have not tried is to RUU back to the latest OREO build, then install the ROM(S). If there is anything i can do to assist in trouble shooting let me know, and i can re-install later today and get the log, or whatever is needed for ya! I use my phone for work so i can't go long during the day with service.

_Sherrif said:
@AnierinB,
OK, i just installed the ROM and it would not boot. I wipe and factory reset, not boot. Then i wiped, factory reset and FORMATED data, still no boot. I only tried to install and boot without any gapps, ROM only. Not sure. I get to the RR logo and it tries to boot for about 2-3 minutes then re-boots back to TWRP.
Also, i found your HAVOC-OS build, i think it was yours anyway, if i remember correctly. I tried as above with HAVOC-OS and had the same result. The only thing i have not tried is to RUU back to the latest OREO build, then install the ROM(S). If there is anything i can do to assist in trouble shooting let me know, and i can re-install later today and get the log, or whatever is needed for ya! I use my phone for work so i can't go long during the day with service.
Click to expand...
Click to collapse
Interesting, I'll have to take a look when I get off work tonight. I apologise for that. XenonHD is still planned as it works flawlessly with no boot issues

AnierinB said:
Interesting, I'll have to take a look when I get off work tonight. XenonHD is still planned as it works flawlessly with no boot issues
Click to expand...
Click to collapse
Noted and Tahanks.
Also, I would like to give XENON-HD a try but i do not see it on AFH any longer. I saw it the other day when i seen the HAVOC upload, but was uncertain as to what android flavor it was and could not find any posts anywhere about it so i passed on it. If you could provide a link to XENON-HD i would be happy to give it a test run.

_Sherrif said:
Noted and Tahanks.
Also, I would like to give XENON-HD a try but i do not see it on AFH any longer. I saw it the other day when i seen the HAVOC upload, but was uncertain as to what android flavor it was and could not find any posts anywhere about it so i passed on it. If you could provide a link to XENON-HD i would be happy to give it a test run.
Click to expand...
Click to collapse
I have to recompile it tonight with the keyboard fix. I already have all the source on @holofractals server so when I get off work I'll get right on that. The previous build was deleted from Android file host because of the missing aosp keyboard.

i cant get xenon to boot. tried pico gapps from today and pervous days what gapps you recommend?

voodooline said:
i cant get xenon to boot. tried pico gapps from today and pervous days what gapps you recommend?
Click to expand...
Click to collapse
Mind the gapps

AnierinB said:
Mind the gapps
Click to expand...
Click to collapse
I tried without gapps and couldnt get it to boot not sure whats up

voodooline said:
I tried without gapps and couldnt get it to boot not sure whats up
Click to expand...
Click to collapse
Try the latest build. I compiled two last night and they retained the same package name since the date was the same. I deleted the previous one in favor of the new one so download everything from the links in xenonhd thread (mindthegapps, and ROM). advance wipe everything in TWRP before flashing so make a backup prior and store it on sdcard or PC