Database Users

Got a fascinate to mess around with

whats the better rom out there?
What modems have provided good results?
What kernels have provided the best battery life?

I love miui rom and glitch kernel!
Sent from my SCH-I500 using xda premium

hows battery with that combo

powerwashed ed05, pbj voodoo kernal, ec09 radio. Battery life avg. 2% per hr and very functional... Powerwashed gingerbread would be my next choice, but it still has the stock kernal. Shouldnt be long before a voodoo kernal becomes available for it.

droidstyle said:
powerwashed ed05, pbj voodoo kernal, ec09 radio. Battery life avg. 2% per hr and very functional... Powerwashed gingerbread would be my next choice, but it still has the stock kernal. Shouldnt be long before a voodoo kernal becomes available for it.
Click to expand...
Click to collapse
thanks. looks good. i need to learn the samsung way again.

Just got a fassy off Ebay. I'm excited to be back. Can't wait to get MIUI and glitch kernel back up and running. Anybody wanna buy my MIUI'd DX?
Sent from my Droid Charge 4G running Gummy Charged 2.0

Heres the Breakdown
AOSP roms
CM7 lots of customization/less speed
OMFGB middle ground
Vanilla GB fast / less customization
Pool Party = fast/sbrissens mods ftw
Kernels
JT's always up to date (he's the cm maintainer)
Glitch (head dev is sick so it is taking a little for them to catch up with new commits

+1 for miui and glitch. Right now, however, i'm using jt's 9/12 kernel because flashlight and light sensors are both working. Once the glitch kernel merges in these fixes I'll be back to running it.
Sent from my SCH-I500 using xda premium

Tried reading up on modems but got a little confused. The captivate used to allow direct modem flash through cwm or built directly into rom. Are there any specifics to worry about with modem flashing using odin?

I love CM7 With Glitch kernel v12.
But im currently trying out OMFGB while we wait for a new cm7 nightly.
as far as modems i dunno ive never had to change one

I guess my question about the modem is, when changing is there a progression change that needs to be done, or can I just choose one and flash via odin? When I had my captivate, the modems were built into the roms, so there was no reason for modem flashing.

davwman said:
I guess my question about the modem is, when changing is there a progression change that needs to be done, or can I just choose one and flash via odin? When I had my captivate, the modems were built into the roms, so there was no reason for modem flashing.
Click to expand...
Click to collapse
chose one and flash via odin. Although most roms for the fassy have a modem included... but give the ec09 or ed05 a try... the ec09 has been the best for me. I have tried every modem from dl09, ec01,ed01,ed03,ed04,ed05, and ec09.

ok so the modems do flash along with the rom the way the captivates do. thanks for the info.

EDO5 works perfect for me.
Sent from my SCH-I500 using xda premium

davwman said:
ok so the modems do flash along with the rom the way the captivates do. thanks for the info.
Click to expand...
Click to collapse
No not really. Usually the fully packed "ED05" or "EC09" (or any of those other older ones like that) roms do include the modem. But the cooked roms usually don't include the modem (I believe). Most definitely not CM7 or MIUI - those keep whatever modem you had before.
In which case, choose a modem (usually people are going between EC09 or ED05) and flash in Odin. It's super simple.

Talek said:
No not really. Usually the fully packed "ED05" or "EC09" (or any of those other older ones like that) roms do include the modem. But the cooked roms usually don't include the modem (I believe). Most definitely not CM7 or MIUI - those keep whatever modem you had before.
In which case, choose a modem (usually people are going between EC09 or ED05) and flash in Odin. It's super simple.
Click to expand...
Click to collapse
Yeah, thanks I understand. I didnt mean that they always come prepacked with a modem, but the ability to directly flash a modem built into a rom is there. My incredible required modems to be flashed through the bootloader on a more dangerous hardware level. I had the captivate and completely understand the methods, I just needed re-education in the samsung world. Thanks for the response.

Couldn't be happier with my decision and am currently running pwgb v.3. All it needs now is a voodoo kernel. What modem do you guys find works the best? I am currently running the ec09.

After bouncing around on just about all options, pw and ec09 turned out best for me in stability, function and battery with solid performance as well.
Would like a little voodoo though.
;-)
Sent from my SCH-I500 using xda premium

[Q] Wifi disabled on Goldeneye rom

Posting here because new account can't post in Goldeneye Rom thread. My wifi is disabled and won't turn on. I installed the jflteatt Faux 005m kernel, have no idea if that's the problem or not-- and I can't find the original Goldeneye kernel without flashing the entire rom. I've tried different modems, and un-doing all of the Nottouch Xposed stuff, and un-doing every other tweak or addition I've made on it. I have no idea what the problem is. Has anybody else had these issues? Do you know what the fix is?

I'm having a similar issue, wifi was working fine and now it WILL NOT turn on, no matter the rom or kernel

Hmm what version are you running of goldeneye? I have the 3.0 installed and then I flashed the GOLDENEYE-i337m-FiX-XXUBMF8 and it screwed my wifi up. Honestly idk what that was for but after reflashing without it made my wifi work.
Sent from my SAMSUNG-SGH-I337 using xda premium

kL7GtEd said:
Posting here because new account can't post in Goldeneye Rom thread. My wifi is disabled and won't turn on. I installed the jflteatt Faux 005m kernel, have no idea if that's the problem or not-- and I can't find the original Goldeneye kernel without flashing the entire rom. I've tried different modems, and un-doing all of the Nottouch Xposed stuff, and un-doing every other tweak or addition I've made on it. I have no idea what the problem is. Has anybody else had these issues? Do you know what the fix is?
Click to expand...
Click to collapse
if youre on att, flash this and try to see if it fixes your issue, its a stock kernel
http://www.androidfilehost.com/?fid=13858085825318748360

Try an different kernel, that will fix the wifi.
Good luck.

any follow up on this? does a new kernel work? i thought i was already on the stock kernel, but i am not entirely sure.

It is the correct fix.
Sent from my GT-I9505 using xda premium

Does Kernel Carrier really matter?

If im on an International Rom with an Auto Loki Recovery why do i have to use an AT&T Kernel? Is there an issue to using Ausdism's or Adam Kernel? Or even BroodKernel. It works fine so i dont know whats the big issue can anyone explain to me?, am i going to have any weird wake locks or abnormal battery drain?

Easton999GS said:
If im on an International Rom with an Auto Loki Recovery why do i have to use an AT&T Kernel? Is there an issue to using Ausdism's or Adam Kernel? Or even BroodKernel. It works fine so i dont know whats the big issue can anyone explain to me?, am i going to have any weird wake locks or abnormal battery drain?
Click to expand...
Click to collapse
Wrong forum...but
CANADIAN CARRIERS NEED NO LOKI!!!!!!!!!!!!!!!!!!!!!!
you need to use these...
Here is the Canadian stock Rom/Kernels Thread: (this should help you get started)
http://forum.xda-developers.com/show....php?t=2269304
Thanks

Easton999GS said:
If im on an International Rom with an Auto Loki Recovery why do i have to use an AT&T Kernel? Is there an issue to using Ausdism's or Adam Kernel? Or even BroodKernel. It works fine so i dont know whats the big issue can anyone explain to me?, am i going to have any weird wake locks or abnormal battery drain?
Click to expand...
Click to collapse
They for the most part work fine with loki BUT if any issues with data, etc show up running another carriers rom its a good bet its kernel related so switching to your carriers kernel at that point could help...
Personally I dont run any kernels but ktoonsez kernels.. thryve never let me down and have had the least problems by far with his kernels
Sent from my Omega AT&T S4

Easton999GS said:
If im on an International Rom with an Auto Loki Recovery why do i have to use an AT&T Kernel? Is there an issue to using Ausdism's or Adam Kernel? Or even BroodKernel. It works fine so i dont know whats the big issue can anyone explain to me?, am i going to have any weird wake locks or abnormal battery drain?
Click to expand...
Click to collapse
For me, with an ATT i337, it's been hit or miss using the kernels included with i9505 roms and auto-loki or in my case loki-doki.zip. While some lokied i9505 kernels seem to work just fine, others have had issues. Usually the issue is related to the modem or wifi, but sometimes I've had FC/Freeze/Reboot issues. To be honest, I think every kernel is different so at this point it's tough to say which i9505 kernels will work with auto-loki / loki-doki and which won't. Just have to try them for yourself at this point, which is why it's easier to just flash an i337 (ATT) specific kernel if you're using an ATT S4.
I will say that over the past couple weeks, my impression is that many of the i9505 kernels are getting better in terms of working with loki patch and the i337, but I'm not sure what's changed.

Ok, I am confused to why you guys would run a kernel made for another device. Different hardware, tweaked for another device...there has to be issues, no?
I know this is hard to believe, I use the SAME kernel for every rom I tested or run. 06/10 KT. Once I get the rom up and running, then I do the kernel changing to see if it has a better effect on lets say the battery and so on.

TheAxman said:
Ok, I am confused to why you guys would run a kernel made for another device. Different hardware, tweaked for another device...there has to be issues, no?
I know this is hard to believe, I use the SAME kernel for every rom I tested or run. 06/10 KT. Once I get the rom up and running, then I do the kernel changing to see if it has a better effect on lets say the battery and so on.
Click to expand...
Click to collapse
I always end up flashing the ATT KT Kernel, but often I try to boot the rom specific kernel with loki-doki patch just to see what I get. There really is no reason for it other than curiosity. However, as I mentioned, it seems that whatever kernel developers are doing has made many of their non-att specific kernels much more compatible with our att devices once patched with loki of course.
Heck, a day or so ago, I was running MIUI with the included loki pathced MIUI kernel and it was working pretty darned well. Some small issues with 2.4Ghz wireless, but 5Ghz wireless seemed to work ok. LTE seemed to work ok as well.
I guess you could say curiosity more than anything.

Ok, agreed, but it could run into issues correct? You guys know if it boot loops or hangs you can recover, but it could be disaster to a new person.

TheAxman said:
Ok, agreed, but it could run into issues correct? You guys know if it boot loops or hangs you can recover, but it could be disaster to a new person.
Click to expand...
Click to collapse
I like to boot up the first time or two and try it for a while with the stock kernel but always go back to kt.. havent had a probl3m yet (knock on wood lol) but yeah I see your point about noobs possibly running into issues and panicking.. ive run a few 9505 kermels as well too.. just for the hell of it.. I think like acura said its just curiosity amd seeing whats out there..
Sent from my Omega AT&T S4

Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

TheAxman said:
Ok, I am confused to why you guys would run a kernel made for another device. Different hardware, tweaked for another device...there has to be issues, no?
I know this is hard to believe, I use the SAME kernel for every rom I tested or run. 06/10 KT. Once I get the rom up and running, then I do the kernel changing to see if it has a better effect on lets say the battery and so on.
Click to expand...
Click to collapse
I literally have never had an issue with any i9505 kernel even to this day. No wifi issues no 4G issues. everything seems to be flawless. All of our hardware is 100% identical. If there is a difference its in the bootloader or radios and at that point its different software not hardware..

Easton999GS said:
I literally have never had an issue with any i9505 kernel even to this day. No wifi issues no 4G issues. everything seems to be flawless. All of our hardware is 100% identical. If there is a difference its in the bootloader or radios and at that point its different software not hardware..
Click to expand...
Click to collapse
Wow, really, thank you, I have not seen much on the use of other carriers kernels. Not a matter of crashing, I can recover from that. I just didn't know it was possible to run them perm.
Good to know.
Thanks again.

[DEPRECATED]--[AROMA][PATCH]MasterPatch Aroma for SGH-I537

ATTENTION: THIS INFORMATION IS DEPRECATED!
I am leaving the thread up for reference, but as I no longer have the device and haven't been keeping up on the development of the I537, many of these methods may not (and probably won't) apply any longer. Please search the subforums for recent information.
Standard Disclaimer: Flash this at your own risk. I am not responsible for any problems that this file may cause, up to and including bricking your device.
Current Version: MasterPatch v.0.92​
Choice of Kernel Modules for MF1, MF2, or MF3
Optional Add-Ons:
-Camera Fix - still no stock camera support
-Hardware Keys support for S4 ROMs
-Speaker-Phone Fix
-Edited "gps.conf" file for faster GPS fix in the United States
-I537 build.prop
-apns-conf.xml file - This may make it so that you do not need to manually input your APN on a ROM for another carrier
FOR NOW, ONLY FLASH AFTER A FRESH ROM INSTALL AND BEFORE FIRST BOOT
Introduction:
After making several MasterPatch zips combining patches and features (mostly to make regular S4 ROMs compatible with the S4 Active I537), things started getting tedious. I decided to make an Aroma Installer Zip which will allow for anyone to to pick and choose what he/she wants.
Note:
Immediately after installing a ROM in a new slot, flash the MasterPatch. Do not reboot in between.
PLEASE SUGGEST ANY OPTIONS THAT YOU WOULD LIKE TO SEE IN UPCOMING VERSIONS
Thanks:
Hashcode for SafeStrap
TreyLWalker & jrkruse for the S4_Active_Call_Record_Fix.zip which fixes Speaker Phone
Lejay for the Camera Fix
Darkman for the Hard Keys Fix
Ayush Singh for the incredible guide on Aroma
Devo7v for recommending I try my hand at Aroma
Instructions on editing the code:
If you want to add your own personal options to the installer, you will need to:
-Extract the zip
-Add code to /MasterPatch_v.XX/META-INF/com/google/android/aroma-config to give the option in the installer's UI
-Add code to /Masterpatch_v.XX/META-INF/com/google/android/updater-script to install the files if the option is chosen in the UI
-Place corresponding files in /MasterPatch_v.XX/AROMA/CHECKBOXx/ or /MasterPatch_v.XX/AROMA/WINDOWx/ depending on where the option is chosen in the UI
DOWNLOAD ON ANDROID FILE HOST:
MasterPatch_v.0.93
MasterPatch_v.0.92
CHANGELOG
Version 0.93 20Nov2013
- UI Improvements
- Removed APN option...still working on it
- Added Camera apk from KitKat
Version 0.92 19Nov2013
- Initial Release

reserved

Random reboots after flashing on the GPE ROM
Sent from my SAMSUNG-SGH-I537 using Tapatalk

dave5777 said:
Random reboots after flashing on the GPE ROM
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
Was it a fresh ROM install? What firmware version are you on? What options did you choose?
Sent from my GT-I9505 using Tapatalk

my-blue-snog-box said:
Was it a fresh ROM install? What firmware version are you on? What options did you choose?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
No dirty with Dalvik and Cache wipe mf1 speaker phone, GPS, cam
Sent from my SAMSUNG-SGH-I537 using Tapatalk

dave5777 said:
No dirty with Dalvik and Cache wipe mf1 speaker phone, GPS, cam
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
Are you able to re-flash the same ROM in a new slot, flash the MasterPatch, boot, and let me know if you have the same problem? I tried dirty flashes on a few different ROMs earlier and didn't run into the problem.
Sent from my GT-I9505 using Tapatalk

my-blue-snog-box said:
Are you able to re-flash the same ROM in a new slot, flash the MasterPatch, boot, and let me know if you have the same problem? I tried dirty flashes on a few different ROMs earlier and didn't run into the problem.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
OK made a new ROM slot installed GE ROM used Aroma Master Patch selected mf1, cam, and speaker phone. Then wiped cache before rebooting. No problems yet
Sent from my GT-I9295 using Tapatalk

dave5777 said:
OK made a new ROM slot installed GE ROM used Aroma Master Patch selected mf1, cam, and speaker phone. Then wiped cache before rebooting. No problems yet
Sent from my GT-I9295 using Tapatalk
Click to expand...
Click to collapse
Wonderful! I'll make a note in the OP to only flash after a fresh install for now. I will make kernel modules optional in the next build to try and rectify the problems you had.
Sent from my Nexus 7 using Tapatalk 4

You are going to single-handedly save this phone, and I appreciate all the time you're putting into this. I've installed the GPE ROM and then flashed the Aroma package and I've noticed a couple things:
On the welcome page (the page after selecting the theme) for some reason it mentions "Xperia MFPI Devices..." I'm not sure if this is hardcoded and needs to be changed or not.
The MasterPatch Changelog need a little formatting.
Under the patches, I would say somewhere (possibly in red) that the patches are required to be flashed on first boot. This way a new user will make sure those boxes are checked and won't have a reason to complain that the ROM isn't working. I would say something like "These patches are required to be flashed before the first boot of the ROM. Make sure all three boxes are checked." Another option would be to call them "Required Patches" rather than just "Patches". Or, and I don't know if this is possible, have the boxes checked by default so that the user has to uncheck them intentionally.
I don't know if it's worth it, but maybe the option for other gps regions? I know that this is for the i537 that was pretty much only sold in the US, but if you go on Sammobile there are i537 builds for Mexico and Uruguay.
I'm not sure the confirmation box for installation is needed since there's no way to cancel it.
On first boot of GPE there are no APN's listed. I did select the option in Aroma to flash APN settings, but for some reason it didn't take.
Default camera works fine, but that is to be expected since this ROM was built for the Active. I flashed the camera fix regardless.
I hope I'm not being too critical, I think you've done a great job with this and I think it will really help the community.
The only other thing I would add is the AT&T Compatibility Pack for Hyperdrive. The only trick with that is that you would have to make sure it is the last thing that is flashed in Aroma, otherwise it won't work and the APNs will be wrong. I took a look at the pack and noticed there were a ton of files in there which I'm guessing are there because it is based off a Verizon ROM. That said there may be a couple other things in there that are needed for the APN settings and might fix the problem with your patch.
Let me know if you need me to test anything or if I can help you out with anything.
EDIT: Just noticed the LTE MMS fix for Hyperdrive isn't an option. I'm not sure if this is still needed or not since I use Google Voice, but maybe under the optional patches there should be a Hyperdrive option that will flash everything needed for Hyperdrive.
I would also make sure things are being flashed in the correct order, if that makes sense. I'm thinking the APN settings might need to be flashed last, but I could be completely wrong about that.
---------- Post added at 09:42 AM ---------- Previous post was at 09:08 AM ----------
Two other options I thought could be added to this:
T-Moble AWS fix/APN settings
Google Wallet fix. I was able to get it working on my stock slot, I'll have to find the guide I used and post back here later with it. Here are the instructions, reading over them I'm not sure that it's possible to just flash something and get it to work, but it sure would be nice.
Thanks again for doing this.

@Devo7v:
All great suggestions and I really appreciate the feedback. I hope to get to it this afternoon--I just have a few things to take care of IRL and then I will see what I can do.

my-blue-snog-box said:
@Devo7v:
All great suggestions and I really appreciate the feedback. I hope to get to it this afternoon--I just have a few things to take care of IRL and then I will see what I can do.
Click to expand...
Click to collapse
There is absolutely no rush, when you have time you have time. Everybody can get ROMs up and running, this is just more of a convenience thing. Enjoy your real life.

OP updated with new version
Sent from my Nexus 7 using Tapatalk 4

Devo7v said:
I don't know if it's worth it, but maybe the option for other gps regions? I know that this is for the i537 that was pretty much only sold in the US, but if you go on Sammobile there are i537 builds for Mexico and Uruguay.
...
The only other thing I would add is the AT&T Compatibility Pack for Hyperdrive.
...
EDIT: Just noticed the LTE MMS fix for Hyperdrive isn't an option. I'm not sure if this is still needed or not since I use Google Voice, but maybe under the optional patches there should be a Hyperdrive option that will flash everything needed for Hyperdrive.
...
Google Wallet fix. I was able to get it working on my stock slot, I'll have to find the guide I used and post back here later with it. Here are the instructions, reading over them I'm not sure that it's possible to just flash something and get it to work, but it sure would be nice.
[/LIST]
Click to expand...
Click to collapse
-The gps.conf still has all the needed code to work anywhere. It just allows for a quicker fix in the US.
-I don't think I'm going to add the Hyperdrive compatibility patch or LTE fix because they are specific to one ROM and I want to keep the size down.
-I plan on working on Google Wallet in the future.
Thanks again for the suggestions.
Sent from my GT-I9505 using Tapatalk

Btw, the newest beta build is posted in the OP.
Sent from my GT-I9505 using Tapatalk

Hi, This a really good work. But as a user of the international version of the i9295 i cannot use this patch (but i tried )... Is it possible to make it work on a normal i9295 to use regular or custom S4 roms?
Thanks in advance.

dks21 said:
Hi, This a really good work. But as a user of the international version of the i9295 i cannot use this patch (but i tried )... Is it possible to make it work on a normal i9295 to use regular or custom S4 roms?
Thanks in advance.
Click to expand...
Click to collapse
So this is something that has been bugging me for awhile. I'm not the most knowledgeable person on the subject, but it seems like you should be able to flash an S4 ROM and then flash an S4 Active kernel on top of it. It would have to be a 4.2.2 kernel for 4.2.2 ROMs and a 4.3 kernel for 4.3 ROMs, but it seems that it should work. It was possible to do this when flashing Samsung i9000 ROMs onto the Samsung Captivate. The devices had very similar internals, but the Captivate didn't have a front facing camera. This is a very similar situation to what is going on with the S4 and the S4 Active.
If anybody is adventurous, extract the kernel from the S4A Google Play Edition ROM, flash a 4.2.2 S4 ROM, then flash the S4A kernel on top of it. Make sure to flash the keys fix as well and see what happens. I feel like it should work, but please don't hold it against me if something goes wrong. You can always Odin back to stock.
If this can't be done I would like to know why.
---------- Post added at 09:25 AM ---------- Previous post was at 08:54 AM ----------
my-blue-snog-box said:
Btw, the newest beta build is posted in the OP.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I just went and flashed 0.93 (well, I didn't flash it I just ran through the installer and then quit at the end). I only have a couple comments:
The "Welcome" screen needs some minor formatting:
"You are about to Installing" should say "You are about to install:"
"VERSION" is bold, which is fine but it should have the same formatting (bold/not bold) as "UPDATED" on the next line. I think it would also look better if "VERSION" was on its own line.​
Changelog looks much better, maybe include the day along with the month and year of each version.
On the System Information page, I would make the output text for Device Name, Board Name, and Manufacturer bold just like the output text below it.
Kernel Modules page looks good
On the Other Options page I would:
Make "Required before first boot!" all caps and bold to make it stand out. It is very important that users understand this.
For the descriptions of the mods, most of them are all caps except for the Camera patch description. Pick a format and stick with it.​
I'm not sure if you can change this, but on the About screen it says "ROM Name: MasterPatch" maybe change it to "ZIP Name: MasterPatch"
Like I said above I didn't actually complete the installation, and I can't imagine you changed the functionality so I assume that functionally it works the same as the last version. Again, thanks for doing this.
I was thinking more about the Hyperdrive AT&T Compatibility Pack and I think you're right, it would make the MasterPatch needlessly big. That said I definitely think there is something in there that corrects the APN. If and when you do get the APN setting working I would have an option for the T-Mobile APN as well.

@dks21, are you willing to try what @Devo7v recommended? If so, I am willing to work with you on a project for your device.
Sent from my Nexus 7 using Tapatalk 4

Devo7v said:
If anybody is adventurous, extract the kernel from the S4A Google Play Edition ROM, flash a 4.2.2 S4 ROM, then flash the S4A kernel on top of it. Make sure to flash the keys fix as well and see what happens. I feel like it should work, but please don't hold it against me if something goes wrong. You can always Odin back to stock.
If this can't be done I would like to know why.
Click to expand...
Click to collapse
I have already tried something like this. In a total freestyle manner, i tried to flash the cyanogen 11 kitkat for i9505 ( this one: http://forum.xda-developers.com/showthread.php?t=2521384 ) and
the kernel provided here (probably not suitable) http://forum.xda-developers.com/showthread.php?t=2395242... But It didn't boot at all

dks21 said:
I have already tried something like this. In a total freestyle manner, i tried to flash the cyanogen 11 kitkat for i9505 ( this one: http://forum.xda-developers.com/showthread.php?t=2521384 ) and
the kernel provided here (probably not suitable) http://forum.xda-developers.com/showthread.php?t=2395242... But It didn't boot at all
Click to expand...
Click to collapse
So I think I know what you're problem is, you are flashing the S4 ROM which is 4.4, but then on top of that you are flashing the S4A kernel which is 4.2.2. The ROM and kernel versions need to match, so you need to either get a 4.4 version of the kernel or you need to flash the 4.2.2 of the S4 ROM.
Do me a favor, flash this ROM and then flash LeJay's kernel on top of it. Since they are both based off CM10.1 hopefully it will work. If it does than that means you need a CM10.2 kernel from LeJay to flash CM10.2 based-ROMs and a CM11 kernel from LeJay to flash CM11-based ROMs. I searched through LeJay's threads to find newer kernels but I couldn't find anything other than CM10.1. I noticed he released a CM10.2 ROM so you may be able to extract the kernel from that, but this is pretty much where my knowledge stops.
EDIT: The important thing to remember is that the ROM version and the kernel version must match to even have a chance at this working.

my-blue-snog-box said:
@dks21, are you willing to try what @Devo7v recommended? If so, I am willing to work with you on a project for your device.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
;;;
I am OK to test things. But as far as my knowledge about how to " compile, program, extract kernel and so on", is limited, I am affraid that my role would only be beta-tester...

What is a baseband?? I honestly have no idea.

Sorry for such a noob question but I have no idea what a baseband is and I've been having this auto-rotate issue with my 5.0.2 ROM and its really annoying me and I would like to fix it.. But from my understanding I would have to flash a certain baseband BUT I've always thought that was risky business(?) and also I switch back from stock KK lg ROM and lollipop.. Wouldn't I run into same issue with stock ROM if I flash a new baseband?? Once again sorry for such a noob question. Thanks in advance.
Sent from my LG-D801 using XDA Free mobile app

The baseband is responsible for radio connection etc and the auto rotate. Depending on your variant you need a special one for each rom. For all cm roms the jb baseband they start with a 10 for kk roms with a 20 and stock lp will have 30

God bless you! Lol. Seriously though.. I have two more questions if you don't mind.. Is it true you cannot backup a baseband? And is it true if I were to flash a baseband for lollipop, whenever I would want to flash back down I would have to flash KK baseband or else I would run into same issues as before? Auto-rotate, connection issues etc? Thanks again!
Sent from my LG-D801 using XDA Free mobile app

Baseband is commonly referred to as "radio" and also "modem" as well, it just refers to the specific version/build of the firmware responsible for controlling the actual cellular radio (and ties into some other aspects of the overall operation of the phone).
Yes, you can back up baseband/radio/modem files relatively easily on most cellular devices these days and flash new(er) ones at will using custom recovery. Recovery tools like TWRP (in more current versions) allow you to back up most any aspect of the installation (baseband/radio/modem, EFS, etc).
With respect to the Lollipop question, well, it's not officially available yet so what we're dealing with are basically modified kernels to some degrees to get the actual builds functional on the G2. In time we'll have full stock Lollipop kernels, baseband/radio/modems, everything and then things will progress further.

Thanks, I appreciate your help! Question, how does one back up baseband and are you running lollipop on your g2? If so where did you get the kernel to fix auto-rotate? Thanks again.
Sent from my LG-D801 using XDA Free mobile app

The latest TWRP recovery (2.8.4.0) can easily do a baseband/radio/modem backup or restore operation, or flash a new one easily. It has its own thread here, just do a search in the G2 forum for TWRP (in the topic title) and you'll find it.
As for a kernel fix, I have no idea, I can't stand Lollipop and have no intentions of using it anytime soon but since all the current ROMs are basically ports (it's still not really official on anything but the Korean variant afaik) then all the development happening right now is just working with what they can, you might be "stuck' with the auto-rotate issue for a while unless such a kernel exists.
The specific thread(s) for a given Lollipop ROM or kernel would obviously be the place you should be asking such questions, just for the record.