• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [KERNEL] Plague Overclock Kernel for LG Esteem MS910 - UPDATED!

Hey guys I was wondering has there been any work arounds or fixes for the hdmi? I know this kernel is in GingerSteem and what not.
 
Newbie here looking over clock my LG Esteem, I'm using a MacBookPro. Is there an Issue using this platform or can the mods to handheld be done on handheld alone?
 
Ok folks, as we know have CWM working I can now post my custom overclocked kernel. :D

Its build from LG source and modified by myself with assistance from mtmichealson. It has a max oc of 1804Mhz (1.8Ghz) with scaling inbetween and even some lower settings added.

Its been running and very stable @1.8Ghz for all I know who are running it. It has 2 additional governors added, smartass2 and interactive. Smartass2 has been reported to revert back to ondemand or performance. I will correct this in a future build or make sure thats what its suppose to be doing.

Added a link for the 2016Mhz (2Ghz) Plague Extreme kernel. I revert the versioning back to perf so to aviod any module comflicts. But the HDMI out still seems not to work. :\

I would like to thank our team of testers, they been a great help to me and mt, thanks guys!!!

The goods:

1.8 Plague Kernel

2Ghz Plague Extreme

Download and copy to your sdcard and install with CWM or RZR. No wipes needed. Get SetCPU or similar app to set overclocking.


icon4.gif
USE AT YOUR OWN RISK!!!! I am not responsible for anything you do to your phone!


I am trying to get a grasp on what the difference between smartass2 and ondemand is, and what the phone will have as a result, when using each one.
also, i am curious about how your kernal interacts with it, since you mentioned smartass2 is not yet working properly

Thanks!
 
I'm not denying the possibility when I say this, I'm just trying to determine a motive. But if LG did do something to the kernel source, why would they only make it so that mods break HDMI support? I think itd make more sense( especially if the intent is to stop hacking) to disable more important files that could render the device useless or depreciate the value to the customer. Like for instance, why not have it disable radio signal? 4G? Wi-Fi? Bluetooth? Hinder web browsing? Maybe overload ram by disabling the android application manager? Because in my view, not many of the buyers of metro would have the opportunity to buy this phone, and have an hdtv with the hdmi cable just to pop up the phone's screen on the tv for whatever reason; therefore I see it pointless to hinder an option that a small percentage of consumers will even utilize as punishment for Modding the phone. Know what I mean?

I see, thank you for you opinion it does make more sese to do that with something more important...
 
I see, thank you for you opinion it does make more sese to do that with something more important...


Thank you for reading my opinion and being open-minded on the topic. And if any dev is willing to, maybe you could try pulling the original stock kernel and search through the coding for an hdmi enable/ disable that might not have been added to the source by mistake?
 
Haven't tried the HDMI but if anything its probably a driver module or service not being loaded in the startup scripts. Just compare to stock. In / there are .rc files with all that stuff. Maybe the source isn't the same as the B version found on phones.
 
Haven't tried the HDMI but if anything its probably a driver module or service not being loaded in the startup scripts. Just compare to stock. In / there are .rc files with all that stuff. Maybe the source isn't the same as the B version found on phones.
those havent been changed, but easy test on that is sumone flash back to stock n just flash the kernel and then test hdmi out. I even reverted back to the stock kernel prefix so thats not a conflict issue.

I will dig into the hdmi driver src n see if there is sumtin in there causing it not to work.
 
Haven't tried the HDMI but if anything its probably a driver module or service not being loaded in the startup scripts. Just compare to stock. In / there are .rc files with all that stuff. Maybe the source isn't the same as the B version found on phones.


That's my hunch, that there's something missing in the source from the zvb version.
 
yea am serious my esteem can take it , it has never rebooted on 2.0ghz and it can go higher it would be great if some1 can put a 2.1ghz or 2.2ghz kernel so i can test it
 
yea am serious my esteem can take it , it has never rebooted on 2.0ghz and it can go higher it would be great if some1 can put a 2.1ghz or 2.2ghz kernel so i can test it


Lol. That's just overkilling it. But then again , its fun to see our phones go beyond imagines.
 
Wow PG! 2.2Ghz? Damn, that's HOT! I would try it myself but, um my phone kinda freaks out anything over 1.8Ghz. lol. Keep pushing it to the limit PG! :D
oh mine dont even handle it lol. I can set 2.1, but then just opening the app drawer freezes n it reboots, 2.2 it does it soon as its set. lol

I'm gonna try undervolting it some on the 2 new settings n if its handles it, run a benchmark n see if the scores increase or decrease.
 
Back
Top Bottom