Related
I have a question to devs in connection with the nvidia drivers as we know it will be rolled out soon. So if Nvidia releases them and the needed bits whether we (the CM team and the other devs of O2X community) would be able to build a new kernel like 2.6.36 or even 3.0 or just complete the existing 2.6.32 kernel?
And if we build a new kernel what benefits will come with it?
Thanks in advance!
Sent from my Optimus 2X using Tapatalk
It's not really the kernel that is important, it's driver compatibility with the android layer. Kernel differences between 2.6 and 3 are not that great.
The new drivers would help us to access the hardware better without having to hack so much of the android framework
Hello!
This has been discussed to a large extend in the ICS threat...
Well if nvidia releases drivers compatible for ICS a working build will come fast(er).
And of course hardware support of all the shiny features of Tegra2 will be much easier and more readily available...
Sorry for reposting but I haven't read the ICS topics since they were spammed with requestions of ETAs.
Btw Thanks for the quick explenations!
Sent from my Optimus 2X using Tapatalk
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed
This topic is for other developers, not for users who are eagerly waiting for something that may never come
I know that upstream p970 development has stopped. However, I still find it a challenge to get JB4.3 running on the p970. Main reasons is that on the Samsung Galaxy Tab 10.1 (which has also been discontinued by CM-team due to the outdated tegra2 chipset) CM10.2 actually seems to run smoother than CM10.1 (possibly due to the code cleaning from JB4.2 -> JB4.3).
I have started by adding some missing variable to BoardConfig.mk and enabling SELinux in kernel, but already bumped into some compiling issues. Are there any others working on this, or interested in helping?!
Not going into technical part but I have heard and strongly believe that new version means not really a high-end hardware only. According to my knowledge KLP will run smoothly on a device having 512mb of RAM.
and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable
recl said:
and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable
Click to expand...
Click to collapse
????
JB is build based on pure android code from google. So that is the source code necessary...
Honestly,if I could choose from android 4.3 and android 5.0, I'll prefer to wait for android 5.0! Android 5.0 is designed to ensure the performance on old and low-end devices !
I am looking forward for developers to port android 5.0 into our device!!!
I'm willing to help in testing so ring me up anytime!
Sent from my LG-P970 using Tapatalk 4
kasper_h said:
This topic is for other developers, not for users who are eagerly waiting for something that may never come
Click to expand...
Click to collapse
What this mean for you guys?
It is booting already!
only running into some stagefright issues so the display isnt turning on, but i already get access to the logcat to debug.
our target is getting closer and closer
Nice job
This is Strictly Development i u know something plz share if don't then be slient
What is ION .?
Noob way :- It makes things awsome -by lauppenstepperwolf
there is awsome explaination on LX git Wiki
LX said:
#### What is Shared Memory?
Memory is usually private; an app takes a chunk and nothing else can access it.
Sometimes, it makes sense to share memory between processes; for example, an app writes to the screen buffer, while the gfx driver reads that same buffer to put it on the screen. You need a special memory system for that.
####PMEM vs. ION
Back with Gingerbread, every ARM chip maker (Qualcomm, TI, nVidia, Samsung, more?) had their own way of doing shared memory. The Qualcomm way was a system called **PMEM**.
Problem: when a vendor sells a chip to Sony and Samsung, he needs to write two drivers, one for each shared memory system.
To reduce maintenance efforts, Google introduced **ION**, a unified shared memory system, that all vendors use since ICS
Problem: from ICS forward, Qualcomm only provides graphics drivers for ION. PMEM is obsolete.
For a while, stuff still worked, but it is getting worse for us - see the Google Maps app for example.
####Move to ION
An option is to rework the kernel, replace the PMEM system with ION, and replace the old PMEM drivers with newer ION drivers. A common problem on several old devices is, that the camera chip is non-standard, and Sony (Samsung, HTC) never wrote ION drivers for the old cameras. Moving to ION then means you lose the camera completely.
A new solution is to move the kernel to ION, but have a PMEM system on top of ION so that the old camera libs can connect to it. As far as I know, this was pioneered by the Dev_Connection team that maintains the Samsung S+ i9001 (great team, hats off to Christopher83 especially).
Another implementation of an ION/PMEM hybrid was made by galaxyfreak for the HTC Explorer (Pico).
The i9001 and the Pico have similar hardware to our 2011 Xperias (2011, MSM, 512MB RAM, similar specs).
Feedback for the ION builds is very positive. Performance is good and it solves some graphics problems like the Google Maps flickering, and it solves the slow browser.
####ION on LegacyXperia
It would be the next big step after the 3.x kernel, but, it's a lot of work.
On the i9001, 8 devs work on 1 device, while on our side, 1 dev works on 8 devices.
The i9001 approach was to migrate 10.1 to ION, then 10.2, then 11; instead of directly doing 11-ION.
Click to expand...
Click to collapse
ETA :- Nowhere to release
============================================================================
THIS IS A REWORK ON nAa-kernel to use ION but with no video recording support ... until mike does spread his awsome magic with his new scratch ported kernel...
Source :- http://www.github.com/rebel-x/msm7x30-3.4.x-nAa
Current Progress : Intial Pushes done "yay" lets hope it boots
NOTE :- We need your help , i m not able to do alone since i have very limited knowledge about kernels , Please forgive me if my coding somewhere wrong cause
ok so thank you i will post progress as we all get step further ,
thank you
Credits :
Mike : we all know why
nAa : Awsome dev
szezso : always helpful
XDA:DevDB Information
ION-Kernel, a Kernel for the Sony Ericsson Xperia Arc
Contributors
officiallysonyrebel, szezso, Mike
Kernel Special Features:
Version Information
Status: Testing
Created 2014-01-08
Last Updated 2014-01-07
Don't ever give up!
you also need To build rom with ion accelator
offical
its offical jb kernel ?
mahsun72 said:
its offical jb kernel ?
Click to expand...
Click to collapse
Can you read? It's not even official. It could be also for CM11 since he mentioned browser lag, which is an existing bug in CM11.
To OP, I should be able to check the coding and whatnot. Only problem is I'm currently in the army and unable to access my computer on weekdays.
僕のLT18iから送られてきた
@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk
I should also be able to check the code as I'm proficient in C++. Let me know where I can help out, it's a good initiative.
ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
Boudin said:
ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
Click to expand...
Click to collapse
ion is different for every device i guess
Update :
finished initial kernel part (lets hope it boots know)
vishal_android freak said:
@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
im now focus on shool,also i give my arc to my sister i now have only idol mini
n1kolaa said:
im now focus on shool,also i give my arc to my sister i now have only idol mini
Click to expand...
Click to collapse
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak
vishal_android freak said:
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak
Click to expand...
Click to collapse
its idol mini form alcatel,how can i test new kernel with it explain it to me
n1kolaa said:
its idol mini form alcatel,how can i test new kernel with it explain it to me
Click to expand...
Click to collapse
Ohh.. My bad.. Sorry..
Sent from my Nexus 5 using Tapatalk
I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?
CedArctic said:
I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?
Click to expand...
Click to collapse
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
all the best bro.. Any improvements?
gpkumaran said:
all the best bro.. Any improvements?
Click to expand...
Click to collapse
yea its compiling know but no where Close to Boot ... i have changes locally purchased a XMP with screen destroyed only for kernel debugging purpose
rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
Thanks for your work! I love KK rom and im wait ion kernel :thumbup:
Regards
To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.
Dr.SAM88 said:
To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.
Click to expand...
Click to collapse
A better Kitkat .. lets summerize current kernel situation
1. nAa 3.4 full of hacks
2. using drivers and stuffs from 3.0.x
3. Stuck on Abandoned PMEM {with every increasing android version we are using patches more than before to maintain PMEM causing soo many graphic lags
4. msm_fb code /* lets not focus on it currently */
why this mess /* to bring 3.4 kernel faster */
i m trying on 3.0.x-nAa kernel cause it is Pure CAF and also mike is working on Pure CAF 3.4.x MHL enablin gis such a lot and lot of work we are not in fully stable stage to look at MHL and other workaround first..
our device is a 3 year old piece of hardware without camera and HDMI libs using outdated kernel and drivers what should be the main goal
1. To make kernel updated with current sources
2. then make things working
3. then wprkaround for all abandoned hardware(like HDMI)
hope u know why we are focus on kernels and roms know ... and to come at point of compeion in roms
there is no compeition we are not selling our products .. we are working cause we like it and more roms means more respect for developers who are working tirelessly on maintaining those roms @Marchinho6 please no these kinds of post ..!these will spam thread
NEXT RELEASE: 27 AUGUST 2014 GMT+8 0900
With the introduction of so many kernels in the forums, every user just wants his/her phone to enjoy the crisp experience of their device. With ASKP, you get to enjoy the brilliant works of all developers into one small kernel. ASKP, is a modified kernel that merges many tweaks together, just like P.A.C.
ASKP is only run by me and pattyboi for now. Please bear with the slow speed of updates. I'm working on 3.4 for the Galaxy Nexus and also for you guys at the same time.
I promised before, ALL ROMS WILL BE SUPPORTED. But when I say ASKP is fully released. For now, I'll be releasing slowly. So please bear with me.
Supporting Devices:
LG G2
Samsung Galaxy Nexus
Variants of ASKP released for per-ROM basis statuses: http://forum.xda-developers.com/showpost.php?p=53569650&postcount=6
READ THIS FIRST
- There's always a name in each file right? The word at the end is the most important. And of course, make sure the model number is correct.
ONLY TWO WORDS ARE GIVEN FOR SIMPLICITY. STOCK and CAF.
- CAF kernels are for AOSP ROMs. A N/CAF (Non-CAF AOSP) Kernel will also be present upon full release of ASKP.
- ASKP has just started venturing into G2's development, please be patient if there is no support for your ROM yet.
- I am not responsible for any problems incurred on your device. This kernel is not fit to be a daily driver YET. Still in pre-alpha stage.
Changelog To Be Released after Alphas.
Downloads: http://forum.xda-developers.com/devdb/project/?id=4678#downloads
Savoca's Mirror: http://savoca.co/Amperific
Source: https://github.com/AmperificSuperKANG/G2-Kernel.git
Credits:
Everyone. From XDA.
As well as savoca for his awesome file transfer access to me.
Special Thanks to Dorimanx for the help in packing up the boot.img.
Based on: Dorimanx's Stock v20D Source. (Pulled from him as the internet connection I have is incapable of pushing a 1GB+ Source). This is a CLEAN LG Source.
I also want to thank him for his own build script, without it, I couldn't have built kernels as fast as before.
If you'd like to donate to me, Please do so, It'll be used for creating a tracker and an FTP site.
So you're buying yourself a beer. Heheh.
I really thank you!
Donors Hall of Fame:
- nope
XDA:DevDB Information
Amperific SuperKang Project, Kernel for the LG G2
Contributors
Amperific, Dorimanx, pattyboi
Kernel Special Features: Advanced Memory Hotplugging System
Version Information
Status: Testing
Created 2014-06-21
Last Updated 2014-06-21
XDA:DevDB Information
Amperific SuperKang Project, Kernel for the LG G2
Contributors
Amperific, Dorimanx, pattyboi
Kernel Special Features: Advanced Memory Hotplugging System
Version Information
Status: Alpha
Created 2014-06-21
Last Updated 2014-08-26
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
reas0n said:
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
Click to expand...
Click to collapse
I don't care. Like I said. I'm a welfare guy, EVERYONE GETS THEIR ASKP DESSERT.
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
reas0n said:
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
Click to expand...
Click to collapse
Amperific said:
I don't care. Like I said. I'm a welfare guy, EVERYONE GETS THEIR ASKP DESSERT.
Click to expand...
Click to collapse
NEO2598 said:
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
Click to expand...
Click to collapse
I think that this is for stock roms as its based on dori's sources.
Sent from my LG-D801 using Tapatalk
NEO2598 said:
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
Click to expand...
Click to collapse
You're using Cloudy's G3 eh. You're on luck. That's the first one.
Releases In order for Stock G2 and Ported G3 ROMs,
D802 (Released)
D800 (Released)
D801 (Released)
D803
VS980
LS980
After this,
Releases for All devices for Paranoid.
Then,
Releases for All devices for CM.
Also,
Releases for All devices under Mahdi's Sources.
Finally,
Releases for the next MOST requested ROM.
After this, expect features to fly in.
@nimrodsv Go ahead and ask him.
Guys, once again. THIS IS NOT A COPY OF DORIMANX.
I only copied his RAMDisk with his permission. Without it, I wouldn't be able to boot on the majority of ROMs.
The kernel source itself will be different from his indefinitely.
Wow, I am so lucky ☺
I will test it and let you know how is it. Thanks for replying.
Sent from my G2 running CloudyG3 on ART
Can't wait for the d800 PA release. Going to flip my ****.
Sent from my LG-D800 using XDA Premium 4 mobile app
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Sorry to say that, but for now it looks like the Dorimanx Kernel with other name
EDIT: not only STweaks. Governors, Hotplugs, etc, everything is the same, I think You should delete it for now. I think that STweaks can be used by everyone, but well, for now it looks like u copied his kernel and changed the name lol
reas0n said:
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Click to expand...
Click to collapse
Sigh. STweaks is from his ramdisk. And I'm reverting all his commits. by r5, Whatever I don't want won't be there.
Sent from my LG-D802 using Tapatalk
Please read up guides on what comes with a ramdisk and a zImage itself. A boot.img is made from a ramdisk and a zImage. Even though the STweaks app exists, it doesn't mean everything works. I don't have Intelli features inside. so use your eyes please. I'm trying to be kind and patient.
reas0n said:
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Sorry to say that, but for now it looks like the Dorimanx Kernel with other name
EDIT: not only STweaks. Governors, Hotplugs, etc, everything is the same, I think You should delete it for now. I think that STweaks can be used by everyone, but well, for now it looks like u copied his kernel and changed the name lol
Click to expand...
Click to collapse
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
YoungDaddy said:
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
Click to expand...
Click to collapse
Thank you.
But if you really don't appreciate my work, It's fine. I'll stop.
Not like I don't have other plans.
Anyways, Every development has its start. I admit. I have some dorimanx's commits. I'm reverting them currently till r5. Once we go past r5, I'll start working on pushing commits in.
If you see my development style in tuna, I do things part by part, in a systematic way.
YoungDaddy said:
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
Click to expand...
Click to collapse
You guys misunderstood me, meh. I didn't even say anything about the THREAD. It's the first one. The second one is, I just report to the dev what I see, I didn't say that it's a steal or anything, I just said that situation like that exists. Because i saw that there's everything like in dorimanx kernel, than maybe something went wrong with making the kernel.
Oh and about Intelli features, i see there are Intellidemand/Intelliactive govs, EcoMode, Intelli HotPlug, I REPORT it, REPORT, not ACCUSE.
Dang i hate misunderstandings. I appreciate every work and never want to make someone stop his work. Duh.
If dorimanx allowed to share everything with features he added like this now, then it's alright, I just reported in case he didn't allow it and You wouldn't see that or something.
So @Amperific keep going and sorry that u understood me wrong
Finally. We need more kernel devs. Thanks for joining the party!
Amperific said:
Thank you.
But if you really don't appreciate my work, It's fine. I'll stop.
Not like I don't have other plans.
Anyways, Every development has its start. I admit. I have some dorimanx's commits. I'm reverting them currently till r5. Once we go past r5, I'll start working on pushing commits in.
If you see my development style in tuna, I do things part by part, in a systematic way.
Click to expand...
Click to collapse
Keep on doing what you do bro. Can't wait to try some askp goodness on my d800 [emoji1]
Sent from my LG-D800
Sorry. Apologies from me too.
Next few builds,
- Mitigate commits that are not needed
- Bring in ASKP's tweaks
Sent from my LG-D802 using Tapatalk
Amperific, please don't stop your build. Coming from a gnex us users know your kernels are gold. I can't wait to try it out. I'm sure once non gnex users install the kernel they will see the magic. My request for you is a kernel that works with vanir on my d800. I'm a flashaholic so I jump from vanir, aicp, mahdi ect but just can't wait to try this bastard out??????
Sent from my LG-D800 using XDA Premium 4 mobile app
Guys before I sleep,
All Stock variants are up.
And I apologise about the CAF guide.
I briefly scanned through the source and realised that there are different variations of CAF. CMs, and etc. Even LG.
So all variations will be made available as well.
Nights
Do I need to go back on dalvik before flashing this kernel?
Currently i am on ART. If I stay on ART installation is the same? (wipe cache and dalvik then flash the kernel).
Thanks.
Sent from my G2 running CloudyG3 on ART
I was told that dalvik /ART is rom related not kernel
Sent from my VS980 4G using XDA Free mobile app