[CLOSED] Goto G3 Android Development

[EVR_PR]

Proof that it works with Slim based Roms.....

PS: Thats not a screen shot of my phone.. its a friends..

I don't doubt you. It just seems to hang with Tesla. Tried it twice already and the original 777jon kernel works just fine. Again, thanks for your hard work.

 

[Eliminater74]

This Kernel With Tesla​

Update: I told you it works with it. and I installed it as Secondary Rom. Which is way harder on it then as primary.. I have no problems at all.

I posted this, Only because some people are making False Claims that it doesnt work. I dont want people to think that.
So I took screen shots. To Prove to everyone that it does work with Tesla. and almost any other rom thats AOSP/CM based.. LP 5.1.X....

 

[Murtuoso]

Kernel Testing

Hi, I had to stop by and say thanks for the great Pacman rom, and also this kernel it all seems to run smoothly so far, keep up the good work!

 

[graphreak]

Here's Nebula running on another ROM on my phone.

 

[Eliminater74]

(*) I wasnt trying to be rude, But I dont think it was smart nor cool that, someone comes in here and says , that this kernel will not work on Slim based roms nor Tesla. Just because they couldnt get it to work.
That sends a message to others that it dont work. and People are less likely to try. What he should of done was, ask for help, show a log, like proc/last_kmsg or dmesg..........
And to make the false claim that Tesla only works with 777Kernel. which is based off of the CM kernel. and mine being based off of the 777Kernel. is Ridiculous.
And people wonder why im so good at guessing the age group. But age doesnt matter.. My daughter who is 16 now, was using a computer at 3.. And shes very good with them.
So it dont mater. But plz be careful of what you say and how you say it. Because it will effect others decision on trying this or not.

 

[graphreak]

(*) I wasnt trying to be rude, But I dont think it was smart nor cool that, someone comes in here and says , that this kernel will not work on Slim based roms nor Tesla. Just because they couldnt get it to work.
That sends a message to others that it dont work. and People are less likely to try. What he should of done was, ask for help, show a log, like proc/last_kmsg or dmesg..........
And to make the false claim that Tesla only works with 777Kernel. which is based off of the CM kernel. and mine being based off of the 777Kernel. is Ridiculous.
And people wonder why im so good at guessing the age group. But age doesnt matter.. My daughter who is 16 now, was using a computer at 3.. And shes very good with them.
So it dont mater. But plz be careful of what you say and how you say it. Because it will effect others decision on trying this or not.

Well said.

 

[parmar.saab]

Would this would with stock 20E?

 

[Sluggerz]

Would this would with stock 20E?

No this kernel isn't for stock ROMs....its an asop kernel.

 

[Eliminater74]

Would this would with stock 20E?

No this kernel isn't for stock ROMs....its an asop kernel.

Im glad someone answered this, because I wasnt planning on it.

 

[Eliminater74]

Update: Added another Update to the list People..

Changelog:

hotplug: Clean-up hotplug drivers and updates them …
 Introduce new flag WQPOWEREFFICIENT for power oriented … … 
added ElementalX Governor and fixed errors with Slim Governor … 
drivers: notifier: add state notifier driver …
 added BrickedHotplug by showp1984 … (Dont let the name Fool you) 
add makohotplug by franciscofranco
 added AlucardHotplug, MSMHotplug and MSMZENDecision Hotplug …
 msm: thermal: merged intelli thermal v2.0

PS: I personally test each and every Kernel before I post it up. I will not post it, if my phone wont boot, Or something is wrong.

 

[yanowman]

Just a question

Is anyone else getting Bluetooth and NFC turned on automatically after flashing the kernel? And then on reboot as well?

I wish I knew enough about CPU governers to actually put all this work to good use.... Like for example what's the benefits or cons of HYPER over elementalx or blu_active?


Thanks for the upload and development Eliminator

 

[marcdw]

Here you go...

http://androidmodguide.blogspot.com/p/blog-page.html?m=1


Sent from my LG-D851 using Tapatalk

 

[Eliminater74]

Update: I will have an update again soon, As I made a small mistake in my last build.
I forgot to save a fix that I made and it ended up in the build.

+<<<<<<< HEAD
 #define MPIDR_SMP_BITMASK (0x3 << 30)		 #define MPIDR_SMP_BITMASK (0x3 << 30)
 #define MPIDR_SMP_VALUE (0x2 << 30)		 #define MPIDR_SMP_VALUE (0x2 << 30)
+=======
+struct cpu_capacity {
+	unsigned long hwid;
+	unsigned long capacity;
+};
+
+struct cpu_capacity *cpu_capacity;
+>>>>>>> cbae7629... ARM: topology: Add efficiency coefficient for Krait

I fixed that after I already built the kernel.
as you can see the ==== and the <<<<<<<<<< and >>>>>>>>>>>>> dont belong........



PS: As you know, its a well known issue that the OC doesnt stick.. Thats in part so to Faux's cpufreq_limiter.. I came across a more updated version of that very same limiter done by someone else..
Side by side they are the exact same except the new one has extra features the one on dont. Better as a Enabler and disabler ...
Turning that off, allows for you to use the OC function.. with it on.. it wont stick.. I havent tested this out yet.. As I have added alot of new things.. and before I release anything I test it out.,
But I reverted the old faux cpufreq in favor of the new one. Lets see how that goes.. If its no better, Ill add the old back in.

I also updated with all new editions from the CM site on this kernel. So we are up2date with CM ...

 

[zoman7663]

Update: I will have an update again soon, As I made a small mistake in my last build.
I forgot to save a fix that I made and it ended up in the build.

+<<<<<<< HEAD
 #define MPIDR_SMP_BITMASK (0x3 << 30)		 #define MPIDR_SMP_BITMASK (0x3 << 30)
 #define MPIDR_SMP_VALUE (0x2 << 30)		 #define MPIDR_SMP_VALUE (0x2 << 30)
+=======
+struct cpu_capacity {
+	unsigned long hwid;
+	unsigned long capacity;
+};
+
+struct cpu_capacity *cpu_capacity;
+>>>>>>> cbae7629... ARM: topology: Add efficiency coefficient for Krait

I fixed that after I already built the kernel.
as you can see the ==== and the <<<<<<<<<< and >>>>>>>>>>>>> dont belong........



PS: As you know, its a well known issue that the OC doesnt stick.. Thats in part so to Faux's cpufreq_limiter.. I came across a more updated version of that very same limiter done by someone else..
Side by side they are the exact same except the new one has extra features the one on dont. Better as a Enabler and disabler ...
Turning that off, allows for you to use the OC function.. with it on.. it wont stick.. I havent tested this out yet.. As I have added alot of new things.. and before I release anything I test it out.,
But I reverted the old faux cpufreq in favor of the new one. Lets see how that goes.. If its no better, Ill add the old back in.

I also updated with all new editions from the CM site on this kernel. So we are up2date with CM ...

I had this problem also when the OC option first became available on AOSP/CM kernels. Until AICP merged in the thermal engine from the BACON. every since I've used that thermal engine (bin folder) and haven't run into frequencies not sticking since.

 

[Eliminater74]

Update: I had to revert back on the kernel. I went to deep without testing everything first. Reason was because my rom was building and I didnt want to build 2 things at once.
So I started out with a fresh master, then applied what I needed from that.. then little by little im trying to get it back up where I had it.
you all prob wont notice it, since I really never released all the updated stuff that I did add since last update.

 

[Eliminater74]

Update: I just wanted to show that OC now works. I did start all over on my kernel except from where I started on my master branch.
Here is some screen shots of cpu Freq's ..

Dont ask what I did, Because I really dont have any clue. It just started working correctly, But im sure its something I did; I have done so much that I wouldnt know what
caused it to work right. I havent released this version yet. I will post it when I get time...

PS: The temps are in the low 120's F or should I say 50C, because 30 secs before this screen shot I ran some benchmarks... The temps right now are 95F or 30 something C..

 

[Eliminater74]

Update: Posted Updated Kernel... Rev3

 

[aaanadie]

Update: Posted Updated Kernel... Rev3

NebulaKernel_MR_Rev3_20150629
exodus-5.1-20150629-NIGHTLY-d851
Kernel Adiutor 0.9.4.3: 300-1728, zzmoove

everything working perfect, fast, smooth, no lags, no FCs, ... thanks a lot

 

[Eliminater74]

Statement: I just have one request. Please Do not take this kernel and port it over to another G3 Family Device without first asking. Reason is, I appropriated some things from Mr @Fechinator, And as him and I agreed,
I will not release this kernel to other G3 Family Devices, Out of respect for his Kernel. (Since alot are the same, But only 20%) Still I will respect.
So please ask me before doing anything with this kernel outside from our Device.......

Thank you.

 

[selman.pelit]

Statement: I just have one request. Please Do not take this kernel and port it over to another G3 Family Device without first asking. Reason is, I appropriated some things from Mr @Fechinator, And as him and I agreed,
I will not release this kernel to other G3 Family Devices, Out of respect for his Kernel. (Since alot are the same, But only 20%) Still I will respect.
So please ask me before doing anything with this kernel outside from our Device.......

Thank you.

Thanks for everything. So you mean by this that this kernel is not compatible with any other G3 except T-mobile LG g3 device?

I have LG G3 D855TR (v20h) and wanna try your PacRom with this kernel