MK2000 Kernel crashing? - LG V20 Questions & Answers

I noticed the official MK2000 Kernel by @askermk2000 is closed, so I hope its OK to discuss here. There's a CLANG compiler edition of them floating around somewhere that actually is a great deal better (faster/smoother) that I don't see being mentioned around here much.
Only issue is that I've noticed my phone started rebooting randomly with it. I've suspected a hardware issue for a while so I picked up an additional H918, installed a different rom to test performance, and am now finding that it, too, occasionally reboots when coming out of sleep.
The only thing these two handsets have in common is that they are both H918 variants and are both running the latest 2.2 CLANG compiled edition of the MK2000 kernel. They are otherwise running different oreo firmwares (one stock, one Alpha Omega) and are both started fresh (no restore). I have to believe something is up with that kernel, but as we have a lack of Oreo kernels with Kcal currently, I'm hesitant to give it up. Has anyone had a similar experience, especially with the H918 variant?
Seems like a Kernel panic- the phone doesn't completely reboot (doesn't show the yellow warning screen) but starts back up from the T-mobile (in my case) loading screen.

Looks like you're getting soft reboots for some reason if it's starting at the boot animation screen (well, not much moving on the pink T-Mobile screen).
I haven't had such issues so far on my H918 running a data-only SIM card on Alpha Omega Oreo, using the latest mk2000 2.2-based kernel uploaded by Phoenix591 over here (no idea why there's also an LS997 version of the kernel as that variant's stock Oreo is unrootable) on Aug. 6. Are you using that exact same kernel?

C D said:
Looks like you're getting soft reboots for some reason if it's starting at the boot animation screen (well, not much moving on the pink T-Mobile screen).
I haven't had such issues so far on my H918 running a data-only SIM card on Alpha Omega Oreo, using the latest mk2000 2.2-based kernel uploaded by Phoenix591 over here (no idea why there's also an LS997 version of the kernel as that variant's stock Oreo is unrootable) on Aug. 6. Are you using that exact same kernel?
Click to expand...
Click to collapse
I've been using the CLANG editions. I had the regular 2.2 previously, but someone recommended trying the Clang ones as they are superior in performance. Device didn't heat up, seemed pretty responsive and snappy, but man would it just **** the bed sometimes when we needed it most (usually happened upon wake up from sleep- imagine wanting to wake up to see the notification you just got and suddenly having the device reboot).
Good news is that I dirty reflashed AO rom and this time chose to leave stock Kernel intact and did NOT flash MK kernel on top of it, and now it seems to have eliminated the rebooting. It was definitely the kernel. I lose some things like KCAL, so I hope screen retention doesn't start happening on this model, but otherwise the phone seems much better now!

Screen retention will show up sooner or later, especially if you move between very light and very dark backgrounds. Once you see it, then you may want to look into some screen filter apps (non-rooted users do this, and you'll need to make sure that the app has an 'enable on boot/reboot' function) or try some of the other mk2000 Oreo kernel versions. All of askermk2000's kernels, including older versions, are still available over here in lots of subfolders.

Related

[Q] OmniRom 4.4.2 Kernel

Ok guys, the rom is awesome. Installed it on my HTC One... But: Changing the Kernel is really hard and you cant enjoy it... cause of one bad bug.
First, i installed the ElementalX Kernel for 4.4.2... jep, not usable... graphic-bugs whilst opening apps. Also the start-menue (reboot, power off, etc...) doesnt display itself.
There are black stripes all over the lower part of the display...
Okay, restored the default kernel: Everything good.
Installing all other 4.4.2 HTC One kernels: Same bug every time...
Is there any way to install kernels without this damned bug?
Greets: Reavie
FunDaReav said:
Ok guys, the rom is awesome. Installed it on my HTC One... But: Changing the Kernel is really hard and you cant enjoy it... cause of one bad bug.
First, i installed the ElementalX Kernel for 4.4.2... jep, not usable... graphic-bugs whilst opening apps. Also the start-menue (reboot, power off, etc...) doesnt display itself.
There are black stripes all over the lower part of the display...
Okay, restored the default kernel: Everything good.
Installing all other 4.4.2 HTC One kernels: Same bug every time...
Is there any way to install kernels without this damned bug?
Greets: Reavie
Click to expand...
Click to collapse
Kernels other than the one included with omni are not supported, as the team can't test every kernel in existence.
If there's a specific feature from a kernel you want, it can be submitted to code review: http://docs.omnirom.org/Main_Page - read the items under Development

[Q&A] [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***

Q&A for [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***
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 [Kernel]***[D80*/LS/VS980/F320x] B14CKB1RD AOSP [1/18/15]***. 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!
4 cores working with the screen on... battery life....
stuck at logo after kernel flash
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
DT2W double tap to wake
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Hear myself in the phone... rom or kernal problem?
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
asustweaker said:
I am on the liquid milestone 3.2. I saw that this is the same kernel but updated version that came in the rom so i wanted to update. No matter
Now i am stuck in a boot loop. phone powers on, stays at the LG logo, goes no further. I can get to Download mode, but no recovery.
Is there a way to recover this thing with out having put a locked stock rom on it??
Click to expand...
Click to collapse
did you flash kitkat version or lollipop version? Sounds like you flashed lollipop version
Nicholi85 said:
I love the Kernal so far however i've got a question about the double tap to wake features. Is there a way to have the screen turn off by double tapping somewhere OTHER than the notification bar at the top of the screen? Also it takes me about 4 or 5 double taps to get the screen to actually wake up, any ideas on any of this ? Thanks!
Click to expand...
Click to collapse
Update the touch screen firmware....there's an echo call via android terminal emulator or in my updated version in synapse
Nicholi85 said:
hello love the work you guys do its exciting and interesting. Ive relatively recently started playing with custom roms and kernals etc. love this one because i get excellent battery life as well as a solid LTE signal (two things ive had trouble finding with lollipop so far.. might just be me). Anyway ive got an issue with hearing myself in my phone when im on the phone... its like everything i say approx half a second after i say it.. needless to say its rather annoying, is this a rom or kernal problem? volume settings issue? not sure.. Also my proximity sensor occasionally wont register that my ear is near it.. baaically the screen stays on if im say checking my voice mail or on the phone.. not sure why this happends.. Everything else works great.. some info: d801 lg g2, lastest rr build for lp and i have the lasest blackbird for lollipop. its a really solid combo and im loving it.. thanks for any information you may have
Click to expand...
Click to collapse
These are ROM related errors...the call echo especially... Depending on ROM I could help....also see if it still persists in my latest update
Love this kernal, and I flash when installing a new LP build, but I've been having problems lately. After initial setup or reboot I get the" NO UCI SUPPORT " message. I'm running LiquidSmooth's latest build for the LS980, is anyone else having this issue.
Run om g3 based roms?
VictorAKAx said:
Run om g3 based roms?
Click to expand...
Click to collapse
No. This kernel is for AOSP-based ROMs. G3 ROMs are stock-based.
Typos courtesy of my Ice Cold LG G2 (D803).
just flashed your kernel, got stuck in a boot loop.
VS980, liquidsmooth 3.2 milestone.
what can i do? was excited to try out your update
Great kernel, running super smooth on AICP.
Thanks!
He's working on the fix for cm 12.1.
I sent my files on hangouts, just wait
edit: figured it out
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
perforatedpaper said:
does anyone have a dt2w fix for vs980? i just flashed liquidsmooth 4.0 and everything was working fine, flashed the kernel and it broke my knock on support. i found the zip posted in the main kernel thread (this one) and twrp tells me the file is corrupted
Click to expand...
Click to collapse
Use the 0 init method:http://forum.xda-developers.com/showpost.php?p=56948464&postcount=73
I'm using F320K with BlissPop v2.3 rom, when flash this kernel for lp 5.0.2, it cause loopboot. Pls up kernel fix for lolipop 5.1. Hope to see it soon. Thanks u
llamas612 said:
I'm assuming that those are 5.0 based, since they're from January, right?
Click to expand...
Click to collapse
I think they're KitKat based. I tried already and it caused my d800 to go in a boot loop.
I wonder if anyone has got, perhaps, the 5.1 d800 version? I'm getting kinda desperate since my fav rom switched to a kernel that makes my phone really really hot.
Really need a link to latest 5.1 B14ckB1rd kernel for D800 :/
Pls...

What ROM should I get to keep now-defunct Nexus ! running?

I suppose this is a reasonable place to ask this sort of thing and hopefully avoid 'how-long-is-a-piece-of-string?' replies.
I have two of them - a 16 and a 32 GB - and they seem to be OK for the most part. They are used for usual non-commercial stuff including video watching and some mild games. I just want the Nexii to be as stable, efficient and hassle-free as possible.
My options seem to be to run:
stock 5.1.1
A marshmallow ROM (which one?)
A nougat ROM (ditto)
Any of above with Franco kernel for efficiency and maybe Xposed, if available, for tweaks and 'upgrades' e.g. 'N-ify'.
I currently have PureNexus 7.1.1 on one (no camera) and Cyanogen 13.0-20161031 nightly on the other (some freezing and crashing).
Any suggestions re what I could use that is as stable, efficient and hassle-free as possible?
BUMP. (does one need to do this on XDA?)
I might be at the wrong forum sub-group. Any suggestions where I might find folk who know about mods and Nexus 10?
Ultimately, _no_ 7.x ROMs have working cameras, and I don't think any of them have working DRM binaries either (although I could be wrong).
CM is no longer being maintained, so any issues you do have there are not going to be fixed.
There is the LineageOS 6.x (https://forum.xda-developers.com/nexus-10/development/rom-t3556116) but whether it works well I don't know. It appears to be the closest to a 'maintained' 6.x ROM though.
I was just given a 10 last weekend and went with the latest lineage build https://download.lineageos.org/manta
Assuming you have a custom recovery just wipe, flash lineage, then a small gapps package, and finally SuperSU and you are rocking and rolling. Just give it a few minutes to settle after the first boot. My only complaint so far is the lockscreen is only in landscape mode.
Many thanks for your reassuring replies,vo4LG and someguyatx.
Once I get over my current f#up - I upgraded TWRP to 3.1.0 not to recovery, leaving me only able to boot to TWRP in recovery - I'll be going to Lineage MM. Somewhere else Resurrection was suggested. Maybe I'll put that on Nexus no.2 afterwards.
Sent from my Nexus 10 using Tapatalk

Lenovo A6000+ Automatically Shuts Down [DISCUSSION]

I recently bought a used Lenovo A6000+. Using it for the first few hours did not reveal any major flaws. However, shortly afterwards I realized that the Phone used to switch off by itself when left unattended.
After verifying that my assumption is true, I proceeded to flashing the stock Lollipop ROM. I did so because I thought the problem was due to a flaw in the firmware. Plus, the 'About Phone' section in the Settings app showed clearly that my phone is a Lenovo A6000, with 8GB internal storage and 1GB RAM, while CPU-Z said that there is 16GB internal and 2GB of RAM, which tells that it is an A6000+.
The Lollipop ROM is worse than what I had anticipated. It lags like hell on the device, and is filled top to bottom with bloatware. Plus, the problem didn't get rectified even a bit. Worst, it started switching off even more regularly, and it wouldn't start unless I took out the battery and put it back in again.
If someone has devised a way of getting past this problem, be kind enough to mention it below.
@techfreak13, I don't know what's causing this issue but I can tell you that the stock Lollipop was a nightmare. Either you stay with stock KitKat or you can flash any of the other various ROMs available for this device. But, do note, that if you want to move from Lollipop (or Marshmallow or Nougat) based to KitKat based ROMs or vice versa, you'll first need to flash the stock ROM only. Then only you can flash the custom ROMs. Also different versions of TWRP are needed to work with the Kitakt and the other Lollipop/+ ROMs. TWRP 2.8.6 no image is for Kitkat while the latest verion 3.1.0 can be used for Lollipop+ Android versions. Since there is no unified thread for all the mods and roms. You'll have to dig deep into the forums to get the links. Good Luck to you. I hope you'll be able to solve the problem.

Moving to LineageOS worth it (and possible) from Cloudy G2.2?

I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I
So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?
From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.
ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.
i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]
S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.
I think you need hybrid bootstack for android 7.
WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.

Categories

Resources