Related
Hello everyone!
I'm currently on CM11 nightlies on my d800 and I'm a tad bit confused as to what is going on with the 4.4 kernels. What AOSP ROM's are currently using 4.4 and not the JB kernel?
Does that mean CM11 is falling behind because it's still using the JB kernel?
Any help would be appreciated! Thanks a bunch!!
Rom List
xxxrichievxxx said:
Hello everyone!
I'm currently on CM11 nightlies on my d800 and I'm a tad bit confused as to what is going on with the 4.4 kernels. What AOSP ROM's are currently using 4.4 and not the JB kernel?
Does that mean CM11 is falling behind because it's still using the JB kernel?
Any help would be appreciated! Thanks a bunch!!
Click to expand...
Click to collapse
There is a list that usually has [4.x.x] in the Roms description: [INDEX][REPO][AIO] LG G2 - ROMs | Kernels | MODs | Recoveries [NEW-UPDATED][5.5.14]
By the way, [4.x.x] is the ANDROID ROM version (Jelly Bean, Kit Kat etc), not the KERNEL version.
Compass.
I think the OP is confused.. Maybe he's trying to ask the same as i..
1- What are the AOSP ROMs that are actually using the 4.4 LG Sources?
2- We all know that PA is using the 4.4 LG Sources (at least, Houstonn has started to merge them).. So, what ROMs are using Houstonn's source code?
Anyone?
SnakeHaveYou said:
I think the OP is confused.. Maybe he's trying to ask the same as i..
1- What are the AOSP ROMs that are actually using the 4.4 LG Sources?
2- We all know that PA is using the 4.4 LG Sources (at least, Houstonn has started to merge them).. So, what ROMs are using Houstonn's source code?
Click to expand...
Click to collapse
This is exactly what I'm asking! I didn't know how exactly to type it out.
I don't have a direct answer. There is the XDA Kernels, but there isn't much there.
I guess searching would be the best thing to do.
Why the worry about the kernels anyway?
Compass.
Mahdi 2.5 release 1
Paranoid Android 4.3+ betas
Furnace kernel 2.2.x
Those are the only G2 ROMs/kernels that use the full 4.4.x source tree, drivers and binary blobs. You need to use the LG 4.4.x baseband with these ROMs.
All other ROMs and kernels for the G2 use the 4.4.x Android sources with the 4.2.x kernel sources, drivers, and binary blobs. You need to use either the LG 4.2.x baseband, or the 4.4.x baseband modified by dr87.
You cannot mix kernels between ROMs if they use different source trees for the kernels.
And is you use the wrong baseband for the ROM, you will lose sensors, GPS, and auto-rotate; or it will bootloop.
Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
phoenix_rizzen said:
Mahdi 2.5 release 1
Paranoid Android 4.3+ betas
Furnace kernel 2.2.x
Those are the only G2 ROMs/kernels that use the full 4.4.x source tree, drivers and binary blobs. You need to use the LG 4.4.x baseband with these ROMs.
All other ROMs and kernels for the G2 use the 4.4.x Android sources with the 4.2.x kernel sources, drivers, and binary blobs. You need to use either the LG 4.2.x baseband, or the 4.4.x baseband modified by dr87.
You cannot mix kernels between ROMs if they use different source trees for the kernels.
And is you use the wrong baseband for the ROM, you will lose sensors, GPS, and auto-rotate; or it will bootloop.
Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
Click to expand...
Click to collapse
Only those two ROMs?
So far, yes, those are the only two.
Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
Hello , im new user of lg g2 and i installed diferent version of androidand kernels on my previuosly phones but with lg g2 i m little bit confused. so i need help.
I'm now on cloudy g3 lp rom with baseband M8974A-AAAANAZM-1.0.190128.
So what i want to now, what is CAF, what is BOOTSTACK, and which BOOTLOADER goes with what BOOTSTACK AND ROM? i mean for AOSP and STOCK.
This is confuse and i dont want to mess up something.
Best regards
"CAF" is Code Aurora Forum (codeaurora.org). In this context, it means the "Android MSM" project, which is a custom Linux kernel branch for Qualcomm-based devices.
As for your other questions, see this post for most of them: http://forum.xda-developers.com/lg-g2/help/basic-stuff-t3072452
I've been mucking around with Android for a while but basically stay with a ROM and what it comes packaged (or recommended) with.
Recently I've been looking around at Custom Kernels and I see they offer different options and functionality, but I lack some basic information:
I am guessing that the Kernel and ROM have to be compatible?
Is, for example a Kernel like Blu Spark or Lighting (all for OP5 and Nougat) compatible with all OP5 Nougat ROMs or is it ROM by ROM?
I looked over the pages for both Kernels and also for xXx Freedom OS and didn't see any information concerning compatible ROMs or compatible Kernels, is there any place/list that shows the compatibility of ROMs and Kernels?
Any information, or guidance to where I can find it would be appreciated.
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues. Besides that, if you made a decision to flash a Different kernel, along with their ROM, you're on your own.
Sorry for being off-topic.
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
lekiaM said:
Very simple.
There are 2 types of kernels. One which only works on an OOS based (custom) Rom, and one which will only work on a LOS or AOSP based Rom. Most custom kernels will work on every LOS or AOSP based ROM. But... There's one negative thing about flashing custom or OOS based Kernels. You will never know how the Kernel and/or ROM will behave. There's no 100 percent guarantee if a custom Kernel or ROM are made for each other. Even if a Kernel which comes with the ROM is no guarantee for working properly. There's no such thing as "Stable" even with ROMs. Because stable doesn't exist in a Dev World. It will always be a never ending story.
Long story short, search for yourself an satisfying combination. If you found one combination you like, stick with it and motivate the Custom ROM Developer and or Kernel Developer.
Edit: as you can read i cannot give a proper answer to your questions. The reason why a Custom ROM Dev doesn't show a list in their OP for working Custom Kernels, is mainly based on the fact that they don't like if a user flash another Kernel that didn't came with their ROM. Mostly to avoid non related ROM issues.
Click to expand...
Click to collapse
@lekiaM You provided a great answer and thank you. I did notice that some developers (xXx NoLimits) provide the option to select various Kernel during the install. I pretty much expected that matching a Rom to Kernel was a crap shoot to certain degree. I am going to try a few out and see how it goes.
One final question, if a Kernel offers functionality that is not offered in the original Kernel, how do you go about taking advantage of the added functionality?
Will the Kernel add those selection to the settings or will I need a different app to access them? I was thinking in particular of the don't wake on plug/unplug. I utilized some ROMs (CM) that had this feature in the setting, I use Freedom OS now and don't see that in the setting, but I see that the Blu Spark Kernel offers access to that function.
Zombie said:
Each kernel needs to be build for each rom. Well not each rom. Each rom based on the top three. OOS, AOSP, and LOS. As each has their own kernel.
If you use LOS 14.1 or RR, then youll need a los kernel. If you run stock OOS. Freedom or xXx, youll need an oos based kernel
Not all devs build their kernels for los or aosp. Me as an example. I only have mine built for OOS and It wont work on los or aosp (well it may but you are 99.999% likely to run into a lot of problems)
I hope that clears it up a tad bit
Click to expand...
Click to collapse
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
noncomjd said:
It does thanks. Prior to selecting some ROMs to try, I read that AOSP required a specific ROM so I steered away from it, for now. Until I am able to become a little more familiar with the entire subject.
Click to expand...
Click to collapse
An aosp based rom will install and run like any other rom you decide to flash. It comes with the stock kernel built in
Each rom has their advantages and disadvantages. Currently Im running xXx 4.0 which is OOS based with extra features and then of course my own kernel for better performance and battery
@noncomjd Good question. And honestly I've been wondering that too (most of the time) i could gave you a simple answer on that, but i wont.
A Kernel can interfere with the ROMs behavior (for example manipulate the vibration, sounds, led light strength, button behavior and so on.) But a Kernel has their limits too and also the Kernel Dev in question. Besides that , i did saw some very strange things a Kernel Dev can do to manipulate a ROMs behavior. But i wont go further in that.
Answer to your question:
Yes. A good kernel dev can overwrite or add some tweaks in the ROM itself (you won't see it while flashing, but believe me after that, some things in settings are missing or added in the build.prop) . But as i earlier said it has their limits. A good Kernel Dev is aware of their capabilities. And they mostly play save. If a kernel Dev mentioned or added a feature or something in their changelog, than the feature is there. But to enable or disable that feature, you mostly need an 3rd party app(like a Kernel Manager) to activate or deactivate their added feature.
You need a kernel tweaking app in order to change kernel settings.
You can change those settings even if you run the stock kernel, but it won't offer as much features.
There are many kernel tweaking apps available and some kernels even provide their own apps.
Thanks all for some great information. Have a good base to set out exploring a little more.
Hi all.
Have noticed some terrible 4g speeds and wondered if the radio can be flashed on its own?
If so what would the preferred method be?
Calls are usually ok but messaging and internet speed could be better.
Update: just updated the kernel to version 15 (lightening)
May just be me but it seems to have made an impact, saw 4G+ for the first time in a while almost straight after flashing it.
I had it in my head that the radio was separate to the kernel has something changed since the older versions of android ? I also don't see a lot of talk of firmware versions? On my previous devices you had to update it yourself prior to a change of base otherwise certain things would fail.
Having the proper base firmware is more of a concern if you are running a custom AOSP or LOS ROM. OOS based custom kernels that are updated regularly are generally made to work with specific builds of OOS--when OnePlus releases a new build of OOS some commits in the stock kernel are usually changed and custom kernels are updated to also incorporate the changes. The custom OOS kernels generally assume that you are running the most up to date version of OOS. If you are running an old build of OOS with a kernel made for a newer build you might encounter some bugs or stability issues.
jhs39 said:
Having the proper base firmware is more of a concern if you are running a custom AOSP or LOS ROM. OOS based custom kernels that are updated regularly are generally made to work with specific builds of OOS--when OnePlus releases a new build of OOS some commits in the stock kernel are usually changed and custom kernels are updated to also incorporate the changes. The custom OOS kernels generally assume that you are running the most up to date version of OOS. If you are running an old build of OOS with a kernel made for a newer build you might encounter some bugs or stability issues.
Click to expand...
Click to collapse
Thanks for replying. I'm currently running pure fusion which is not OOS.
When I've been on OOS I've just been flashing the latest no limits ROM.. however as with past devices I've sometimes had to install newer firmwares to gain functionality and at times radios /baseband /modems. But have heard no talk about any of that on the Oneplus, is this something that's done when flashing a ROM? I'd have thought that phones may have different names but wouldn't be too dissimilar in that way.
Overall i just think that my device has had better data speeds and stability than it has before and I couldn't think of anything which would affect it more than flashing a different (potentially more efficient) baseband.
I've no idea how to even recognise the firmware I'm on on this phone.. or where to grab the firmware from, I know the command to flash it as I've done it a lot on my old devices.
Hey guys, hope you all are fine. I have recently rooted my f800l korean with dirty santa method. Now i want to try some custom rom on this, but no rom is booting up, even super rom is officialy listed on their website for f800 but does't boots up. alwasy stucks on lg logo. Some body tell me which step am i missing?
Sorry for my bad english.
as far as i know, theres no officially custom rom that espexially made fot F800L. but dont worry, you can flash 'SOME' VS955 rom in F800L
heres the lost that alreasybtesred by mw, and yes its working
1. VS955 extreme syndicate v1 <-- stock nougat based, no signal, wifi working
2. VS955 Lineage 15 <-- recomended by me, AOSP based
3. VS955 Weta rom <-- stock nougat based
and dont forget to flash custom kernel after flashing custom rom.
im using F800K M2000 (latest version)
AOSP based ROM works out of the box, stock-based doesn't because they're all using different device's stock ROM as a base. Stock-based custom ROM on this device for the most part is just stock + debloated + misc. mods and snakeoil. You can get most of them working by (re)flashing modem after you flashed the ROM, but ultimately its still the same thing. Its better just to root the latest Nougat/Oreo stock ROM for the device, install mk2000 kernel, then debloat it yourself. The korean text in dialer, as well as Korean ROM quirks (always roaming, missing menu options) can be dealt with using a build.prop edit.
crumbling9999 said:
AOSP based ROM works out of the box, stock-based doesn't because they're all using different device's stock ROM as a base. Stock-based custom ROM on this device for the most part is just stock + debloated + misc. mods and snakeoil. You can get most of them working by (re)flashing modem after you flashed the ROM, but ultimately its still the same thing. Its better just to root the latest Nougat/Oreo stock ROM for the device, install mk2000 kernel, then debloat it yourself. The korean text in dialer, as well as Korean ROM quirks (always roaming, missing menu options) can be dealt with using a build.prop edit.
Click to expand...
Click to collapse
Way to disparage the work done by the few devs left here who provide their time and effort for free.
Sent from my LG-H910 using XDA Labs
cnjax said:
Way to disparage the work done by the few devs left here who provide their time and effort for free.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
There's a big difference between actual development (kernel work, device tree for AOSP porting) and chucking whatever popular snakeoil is out there and repackaging it. There's a reason why Original Android Development got split into a separate category back in the days, so repacks 2468295 can be kept in its own containment forum. XDA hasn't changed much since the Blue Angel/Himalaya days in that regard.
crumbling9999 said:
AOSP based ROM works out of the box, stock-based doesn't because they're all using different device's stock ROM as a base. Stock-based custom ROM on this device for the most part is just stock + debloated + misc. mods and snakeoil. You can get most of them working by (re)flashing modem after you flashed the ROM, but ultimately its still the same thing. Its better just to root the latest Nougat/Oreo stock ROM for the device, install mk2000 kernel, then debloat it yourself. The korean text in dialer, as well as Korean ROM quirks (always roaming, missing menu options) can be dealt with using a build.prop edit.
Click to expand...
Click to collapse
i agree with you. lets take an example lesson in my experience while im using lineage, yes the rom is much lighter and faster than stock, but the camera result is not as good as when im using stock rom. the result from camera is very crappy (compared with while im using stock rom). so once again, im very agree the best rom for any device is stock rom+ custom kernel of our choice and of course debloat as our choice as well. this is the reason why im choosing extreme syndicate v1 rom because it just lite as AOSP rom because its extremely debloated and my camera working perfectly, the the DAC work as well.
does lineage-15.1-20181214-X86CPU-vs995.zip work on F800L Bro ......im using lineage-14.1-20180214-UNOFFICIAL-vs995.zip now on F800L
Anybody try to install LOS 17.1 and have the camera works? The camera work fine when 15.1 LOS installed. But soon after I dirty install the 17.1 its stopped working.
I'm haven't install any gapps or any custom kernel. Or should I?