Hey guys and gals. I ordered a new G2 Sprint LGLS980 for my dad replacing his Galaxy Nexus (yeah I know about time). I want to put an AOSP 5.1 rom on it but Im new to this device. I have unlocked and installed custom recovery on many devices so im not a total noob to this. I have searched for how to do this but I cant seem to find an up to date best way to do this. Can some one help me out or point me in the right direction on the steps to take to get this done?
Also he will be using it on Sprints network so I want to use a rom that has all the Sprint LTE bands enabled. Will any of the AOSP roms work and how stable are the CAF roms? I run a CAF rom on my Nexus 5 and love how smooth it is, but its buggy at times. I would like to use a rom thats pretty stable he really doesn't need a real heavily customizable ROM either. CM12.1 would be great but I see its not on the device yet.
Any help would be appreciated. Thanks
I'm guessing you've been going to the G2 Sprint section. Not much there, you need to go to the generic LG G2 page and then to development from there. Here's the shortcut: http://forum.xda-developers.com/lg-g2/development
If you've got the recovery loaded, you should be ready to go. Just make sure to read the ROM requirements carefully, make sure you have the proper radio and bootstack. You'll find what you want in the link above, the most popular ROM's are mostly Cloudy for stock based, CM, BlissPop and Resurrection Remix for AOSP. I have the LS980 and the AOSP ROMs double tap to wake seems to take 5 taps, but other than that the features can't be beat. I run BlissPop now and have run 3 of Cloudy's ROMs, I like Bliss the best, just wish the DT2W could be fixed.
Hello guys, well the title says it all. It should be stable. I would like to go CM but than I read about this fingerprint problems.
Another question... is it possible to get full working shealth on that rom than?
Thank you :fingers-crossed:
- No (Not at this Moment, it isnt even fully stable yet)
- No. If you want Touchwiz Features stick with Touchwiz. Because CM and TW uses different frameworks.
So i want to root and flash a custom ROM on a stock GT-i9300i (S3 Neo) on Indian base-band, running 4.4.4
I want to go from this stock to AOSP based (or CM/RR) ROMs, for flashing Xposed framework and the likes.
I have done research looking for ROMs in this phones section.
I do not mind using android version 4.4.4/5.1/6.0 ROMs, I will flash whatever android version fulfills my requirements, which are:
Required is: Front+Rear camera should work, and Dual sim should be supported (still, for information, SIM2 will be rarely used, so audio in call issues on SIM2 can be ignored)
And so my question is: What ROM+kernel should i flash, as daily driver?
In advance, thank you for your help!:fingers-crossed::angel:
use cm12.1 offical
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.
Would like to flash my stock rom with a custom ROM but I have read I will lose VoWIFI and VoLTE if I do so. Is this true still? I am looking at Arrow OS or lineage OS.
Happy for other ROM suggests too but VoWIFI is essential for me.
It's still not possible with Custom Roms & GSIs.
1). There's no SDK or source code available to implement voLTE into these phones.
2). It's easier to just change some libraries and values and port roms for cheaper devices like A20. Not many people are going to use the ROM anyway so It's just not worth the headache.
But still, developers might try get voLTE working on their rom if the phone model is popular enough.
Thank you