Develop Bugs

General Kernel Discussion: Linux,AOSP,Samsung

I just wanted to start a discussion about kernels for our phone. Obviously the stock kernel for our phone is the .35 kernel. Before I traded in my EVO I was running the .38 kernel. I know that Linux was releasing new kernels every so often and the developers such as Toast would port them over and make them compatible with the EVO. I thought I read somewhere that Linux was not going to develop new kernels anymore, possibly someone could confirm that. So if thats the case what happens? Will android use the same kernels forever? What would be the possobility of our phones being able to use some of the newer kernel versions? As I write this Bybby323 is getting really close to having a fully functional AOSP kernel for our phones and I think development is really going to pick up. Maybe this will open the door for some different kernel versions for our phones.

All I know is that the Linux kernel isn't going to stop any time soon.
http://www.kernel.org/
Too many operating systems/devices (such as Android) use, or better yet, depend on the Linux kernel. Remember, it's an open source thing - not just one guy behind a desk. Many multi-million dollar companies use Linux for everything, from storing data to government websites and so on, they would be willing to invest if Linux needed money (this probably wouldn't happen, but you get me.)
In regards to ETAs, I have no clue. But just know that support for neither Android, or the Linux kernel isnt stopping anytime soon.

stangdriverdoug said:
I just wanted to start a discussion about kernels for our phone. Obviously the stock kernel for our phone is the .35 kernel. Before I traded in my EVO I was running the .38 kernel. I know that Linux was releasing new kernels every so often and the developers such as Toast would port them over and make them compatible with the EVO. I thought I read somewhere that Linux was not going to develop new kernels anymore, possibly someone could confirm that. So if thats the case what happens? Will android use the same kernels forever? What would be the possobility of our phones being able to use some of the newer kernel versions? As I write this Bybby323 is getting really close to having a fully functional AOSP kernel for our phones and I think development is really going to pick up. Maybe this will open the door for some different kernel versions for our phones.
Click to expand...
Click to collapse
the reason is Android 2.3 shipped with 2.6.35, similarly Android 2.1, 2.2, and 4.0 ship with 2.6.29,2.6.32,3.0 respectively.
I dont see the point in doing all of that work when ICS should ship on the GS2 soon with Linux 3.0
And no, Linux is far from dead
Sent from my SPH-D710 using xda premium

[Q] Kernel 3.0 - why is it so important?

I have used Linux (Ubuntu, Debian, Fedora - currently having an Ubuntu Server) and I pretty much know what a Kernel is and what it does.
I also know that the 3.0 Linux kernel is a pretty big improvement overall.
But, regarding Android, what does it bring that makes it so important? Also, why would it improve the speed of ICS on our devices? I can't get my head around this.

Well one thing to keep in mind is that Android isn't just another 'flavor/distro' of linux. So there's quite a bit of difference than say Ubuntu running a 3.x kernel and Android/Dalvik running 3.x
I don't know the technical details of it, but that's generally how it's been in my layman views of it.
PS: The ICS rom I'm using has 2.6.35.14 for the kernel version (based off CM9's kernel), so unless Jelly Bean is supposedly upgrading the kernel version to 3.x I'm not sure where you're getting that info at.

Well, I see in the Andromadus thread discussions regarding kernel 3.0 and how it will bring camera and speed improvements to ICS on HTC Desire Z/G2. Also, in Sense 4 ROM threads the kernel is referred nothing short of a lifesaver.

bogdan5844 said:
Well, I see in the Andromadus thread discussions regarding kernel 3.0 and how it will bring camera and speed improvements to ICS on HTC Desire Z/G2. Also, in Sense 4 ROM threads the kernel is referred nothing short of a lifesaver.
Click to expand...
Click to collapse
The camera issue is more a driver issue since there are no official ICS roms for the G2/Vision yet, it's not going to be solved simply by a kernel version.
By the way which threads were those?
---------- Post added at 11:11 AM ---------- Previous post was at 11:07 AM ----------
By the way I noticed that some like CM9RC1 (unofficial) which is the kernel EliteMod is based off of, that there's a lot of "from 3.0" but nothing seems to be running 3.0 as a whole rather 2.6.x with bits and pieces from the 3.0 kernel. Kind of back-porting features etc basically.

Apart from the Andromadus thread, this one: http://forum.xda-developers.com/showthread.php?t=1679962 regarding speed.
I know that we are waiting for the Desire HD update in order to fix the camera, and that is supposed to have a Kernel 3.0 which can be easily ported to the DZ

bogdan5844 said:
Apart from the Andromadus thread, this one: http://forum.xda-developers.com/showthread.php?t=1679962 regarding speed.
I know that we are waiting for the Desire HD update in order to fix the camera, and that is supposed to have a Kernel 3.0 which can be easily ported to the DZ
Click to expand...
Click to collapse
Funny how the DHD is older than the G2/Vision yet seems to get more attention.
I assume they mention that possibly because the DHD uses the same camera hardware as the DZ, as such if a driver source were made available it could be ported. Same would be true if they made the source available via the 2.6.x kernel, so not 3.0 specifically just that 3.0 is likely what the DHD will get, and that'll be the source for getting the camera working.

Wasn't the Desire HD released at the same time as the DZ ? I think it's favored because it's easier to develop on a non-QWERTY phone.

bogdan5844 said:
Wasn't the Desire HD released at the same time as the DZ ? I think it's favored because it's easier to develop on a non-QWERTY phone.
Click to expand...
Click to collapse
As I recall it was about a month prior to the DZ... and the non-QWERTY shouldn't have anything to do with it since that's a system-level thing.

A 3.0 kernel will likely bring no speed improvements or camera fixes. At this point speed is mostly limited due to hardware, not software. 3.0 offers a variety of features and power saving options discussed elsewhere by people more knowledgeable on the topic than myself.
Sent from my HTC Vision using xda premium

kbeezie said:
As I recall it was about a month prior to the DZ... and the non-QWERTY shouldn't have anything to do with it since that's a system-level thing.
Click to expand...
Click to collapse
Desire HD has more RAM and technically a better CPU (though thats not really the case, as the Vision has pretty much the same CPU just underclocked). Believe it was stated by HTC that devices with 512MB of RAM and less would not officially get ICS.
Thats why the Desire HD is favored over the Desire Z/G2; its probably not helped by the fact that the G2 was discontinued by Tmobile.

actually, kernel 3.0 has nothing special about it. Linus Torvalds got bored of the 2.6.XX names, and the kernel was nothing like it was as 2.6 scheme started, so he renamed it. You can read the mail about renaming at this address:
https://lkml.org/lkml/2011/5/29/204

HTC said 512 ROM not RAM.

stranded.eu said:
HTC said 512 ROM not RAM.
Click to expand...
Click to collapse
Yea that makes more sense, gota have room for the whole 'stock' system and then some. (though sd-ext helps for anyone who are right on the 512MB ROM size )

[WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started

[WIP/DEV] I've got a "booting" 3.4 kernel, looking to get a dev team started
~ # cat /proc/version
Linux version 3.4.24-00010-g001648b-dirty ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #15 SMP PREEMPT Fri Dec 28 16:17:09 EST 2012
Howdy folks, for the last week or so I've been trying to get a response out of a 3.4 kernel for my Galaxy Nexus (Toro), and today I finally got a response from the USB so we can debug via USB, which makes the job 100x easier now that we can see what's failing via dmesg in adb shell. I was pumped for a 3.4 kernel like the other two new Nexus devices received in this awesome Android release (Nexus 4, 10), but sadly, our kernel version was left at 3.0 (and probably will be forever since the OMAP program was killed at TI)
Literally nothing works, the Google screen shows, then disappears, but we have USB debugging!!! I have a .zip that extracts the recovery.img that's currently on my device, and swaps out the old 3.0 kernel for the new 3.4 the kernels and installs it into the recovery partiton, so I'm currently in TWRP Recovery staring at a black screen, but with a working USB port
It's build off the vanilla 3.4 kernel sources from kernel.org (we have to implement the Android stuff). I tried to get the 3.4 branch from omapzoom working, but I couldn't get the USB to initialize (it "booted" by going to the aforementioned black screen but the USB wouldn't initialize, so without USB debugging, that was a no-go). What I did was I went to the earliest commits for the tuna kernel back when Google && Samsung first started working on the board (this was way back in April of 2011 for a device that was released in November 2011) and cherry-picked like 5 of those those patches for the Tuna board/config in its infancy, then applied those very early patches to the 3.4 kernel, added a few Android USB drivers from the Nexus 10 (just because they too, were built the 3.4 kernel) (remember this is the vanilla 3.4 kernel), and basically rolled with the punches of build errors from obsolete definitions and features that were from the 3.0 kernel bits that were killed off or modified in the last year and a half for the 3.4 kernel. It's not much right now, but getting the USB to initialize has taken me a week+ (although I got it on my first try with the vanilla 3.4 kernel from kernel.org), but now, I can say that there's a 3.4 kernel for the Galaxy Nexus with infinite potential
So I'm asking for some help in assembling a dev team to work together in getting this 3.4 kernel working 100% on the Galaxy Nexus (remember we have over a year features that must be added to this kernel like the screen, touch screen, LITERALLY EVERYTHING that came after USB debugging)
A big thank you to:
Texas Instruments for great documentation on every TI board
Google (for the Android open-source project)
The CM Team and every Android ROM contributor for that matter
Samsung (for an awesome device in the Galaxy Nexus)
Everybody who has ever contributed to the Linux kernel
Lastly, Linus Torvalds, for the Linux Kernel itself (Today's his birthday, too!)
If you want to try out this 3.4 kernel for yourself (I don't know why anybody would want to) but if you feel like booting into a black screen as your recovery, for some killer ADB shell access, here's a .zip
http://www.mediafire.com/?qj9acb3366lf3d7
374c83b07d673922ee7d486246629e8b 3.4KernelRecovery.zip
If you want to get your recovery back, you'll have to boot into fastboot mode and fastboot flash recovery
I'll upload the source to my github hopefully tonight or tomorrow morning, so respond in this thread if you're in to help with this 3.4 kernel!
12-29: Source is up at the my github, there's a link in my signature. I've merged all the Android 3.4 bits, and is now buildable with the tuna_defconfig and using the ARM Android 4.6 toolchain from the prebuilts directory of the root of the Android source tree. I've merged all the Tuna-related code up to his commit: https://android.googlesource.com/kernel/omap/+/c8d41a7c8be56fcb8699d8eb4536020901646111 which is from a year and seven months ago, at that point way back then (on the 3.0 kernel of course), the screen displayed and the touchscreen worked. (I was in TWRP recovery when I tested that out so I can't elaborate further on where they were, but it has sensor and input code) My goal is to get the display to initialize so I can see if the touch panel works and buttons and whatnot. After that, it's just merging the latest Tuna-related code from Google/Samsung so that the Tuna drivers are where the current mr1 release is.

:thumbup:
Sent from my Galaxy Nexus using xda app-developers app

I'm impressed, great work! Are you sure there will be no need of some proprietary stuff to get it to work? :thumbup:
Sent from Vega gnex

JackpotClavin said:
~ # cat /proc/version
Linux version 3.4.24-00010-g001648b-dirty ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #15 SMP PREEMPT Fri Dec 28 16:17:09 EST 2012
Howdy folks, for the last week or so I've been trying to get a response out of a 3.4 kernel for my Galaxy Nexus (Toro), and today I finally got a response from the USB so we can debug via USB, which makes the job 100x easier now that we can see what's failing via dmesg in adb shell. I was pumped for a 3.4 kernel like the other two new Nexus devices received in this awesome Android release (Nexus 4, 10), but sadly, our kernel version was left at 3.0 (and probably will be forever since the OMAP program was killed at TI)
Click to expand...
Click to collapse
Great work !!!
Don't lose hope regarding TI, however, as the OMAP program has not been killed off. OMAP 5 is due to be released some time during Q1 2013 and they're refreshing OMAP 4 with the 4470. I think they're going to see how they do next year before deciding their future.

Good work. Now we will see who of the GNex kernel devs are really up to the hype...

WOW! Good luck,i can't code but i can be a good tester when the kernel is ready

hope to see morrific or franco getting to help you out very soon

Morfiiiicccc and franco to the rescue please!!!
Sent from my Nexus Prime

I've got some more recent commits merged for the Tuna, like the input (touchscreen and buttons) as well as the panel, but the display still fails to initialize. I also merged all the necessary Android kernel bits. When the display finally initializes I can check to see if the touchscreen works and buttons as well. The commits I've merged so far had a working display and touchscreen on the 3.0 kernel, but something broke while porting it up to the 3.4 kernel; but once that's fixed, we should have those things working again just as if this were the 3.0 kernel. From then on, it'll just be merging all the newer Tuna-related code from where we stand now to that the latest Tuna-code from Google and Samsung on the mr1 branch.
Here's the latest dmesg where the display is failing (line 272): http://pastebin.com/5nCMCgQd
Sent from my Galaxy Nexus using xda app-developers app

If you want help by developers the right way is a git with a group of master chief .... Please post the link if exist
Sent from my Galaxy Nexus using xda app-developers app

Great work and :good: AK , hoping for a new release .
Just out of my curiosity the 3.7 Linux version does have the ARM patches inbuilt right , so why 3.4 ?

Ashtrix said:
Great work and :good: AK , hoping for a new release .
Just out of my curiosity the 3.7 Linux version does have the ARM patches inbuilt right , so why 3.4 ?
Click to expand...
Click to collapse
Good question. Because that's what the the latest Android 4.2.1 Nexus devices use (Nexus 4, 10) and using 3.4 Android kernel drivers on 3.6+ is uncharted and undocumented territory
Sent from my Galaxy Nexus using xda app-developers app

Hawkw1nd said:
Great work !!!
Don't lose hope regarding TI, however, as the OMAP program has not been killed off. OMAP 5 is due to be released some time during Q1 2013 and they're refreshing OMAP 4 with the 4470. I think they're going to see how they do next year before deciding their future.
Click to expand...
Click to collapse
No, TI has killed all their mobile efforts. They are only into the automotive industry at the moment.

franciscofranco said:
No, TI has killed all their mobile efforts. They are only into the automotive industry at the moment.
Click to expand...
Click to collapse
Yes they said omap5 is alive and coming in '13 after that

franciscofranco said:
No, TI has killed all their mobile efforts. They are only into the automotive industry at the moment.
Click to expand...
Click to collapse
Frank, I think you may be wrong. This was the last news I heard from them:
http://www.gsmarena.com/clarification_ti_not_giving_up_on_its_chipsets_omap_5_on_track-news-4866.php
Not only that, but the OMAP5 section is still on TI's website regarding development.
I love how people post these rediculous claims with nothing to back it up.

Very good work .... Go to your goal :thumbup:
Sent from my Galaxy Nexus using xda app-developers app

akira02rex said:
Frank, I think you may be wrong. This was the last news I heard from them:
http://www.gsmarena.com/clarification_ti_not_giving_up_on_its_chipsets_omap_5_on_track-news-4866.php
Not only that, but the OMAP5 section is still on TI's website regarding development.
I love how people post these rediculous claims with nothing to back it up.
Click to expand...
Click to collapse
No reason to be disrespectful.
Sent from my Galaxy Nexus using Tapatalk 2

I'll look at your source tomorrow
Sent from my Sprint Galaxy Nexus using xda app-developers app

Would be awesome to have some of kernel devs that already replied on this thread, working on this kiss a** v3.4 kernel.
Our GNex would feel so good with the vitamins :fingers-crossed:

eng.stk said:
Would be awesome to have some of kernel devs that already replied on this thread, working on this kiss a** v3.4 kernel.
Our GNex would feel so good with the vitamins :fingers-crossed:
Click to expand...
Click to collapse
The developers of ZenX and AK have commented. Franco even commented in here and got shot down by someone. I don't see what more are you asking for.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Questions about Galaxy Nexus slowdowns and Linaro...

Howdy,
I'm new here, so go easy on me.
So I just upgraded my stock Galaxy Nexus to CyanogenMod 10.1 and I noticed that the kernel was still at version 3.0.x. At the same time, I see that there are newer Android kernels, and my understanding is that Texas Instruments had some folks working on that 3.0 kernel that made it work well on the OMAP chip in the GNex, but TI has given up on phones, leaving the Galaxy Nexus' OMAP architecture somewhat abandoned when it comes to phones. Everyone keeps saying that TI abandoned OMAP and that the Galaxy Nexus is stuck at 3.0 forever.
In particular, support for SSD 'TRIM' on dm-crypt volumes was added in kernel 3.1. That's a big deal if you encrypt your phone and it starts crawling sooner than it should because your slack can't be trimmed.
So, being not a stranger to Google and git trees, I went searching around. I have a few questions:
1. It appears that the OMAP magic lives on and gets updates in the form of Linaro's offerings. Could their kernel be brought into CyanogenMod (or any other modded ROM)?
2. Are the Linaro Galaxy Nexus builds actually usable on its own? Can I just follow their instructions and have a working usable system in a few hours?
3. Assuming that the Linaro builds are mostly development or barebones, and that their kernel works on the Galaxy Nexus, are there any fully-polished ROMs out there that run Linaro-based kernels?
4. Assuming 'no' to 3 and 4, can I pop ONLY a new kernel into an existing CM install, or will that Break Things Horribly?

I've learned from your question that The makers of our chipset has stopped supporting it ,and for me ,this news would make me upgrade to another phone
Thanks

tarekh020 said:
...The makers of our chipset has stopped supporting it ,and for me ,this news would make me upgrade to another phone
Click to expand...
Click to collapse
But why should that matter? If the source for the 3.0.31 kernel with the 'tuna'-specific stuff is out in the open, and Linaro is keeping the ball running witht he overall OMAP subarchitecture, then shouldn't it be relatively simple to keep pushing the customizations from 3.0.31-tuna up into newer kernel versions?
There are also some binary bits and pieces available from Google for this phone, but I think it would be worthwhile to see 'how far they go' as far as kernel versions.
I mean, normally I'd understand leaving the Galaxy Nexus at 3.0.x, but there's a BIG BUG with regards to the dm-crypt layer not passing TRIM commands to the flash that turns the phone into a slug after a while, and the bug is fixed in kernel 3.1 and up.

mangeek said:
But why should that matter? If the source for the 3.0.31 kernel with the 'tuna'-specific stuff is out in the open, and Linaro is keeping the ball running witht he overall OMAP subarchitecture, then shouldn't it be relatively simple to keep pushing the customizations from 3.0.31-tuna up into newer kernel versions?
There are also some binary bits and pieces available from Google for this phone, but I think it would be worthwhile to see 'how far they go' as far as kernel versions.
I mean, normally I'd understand leaving the Galaxy Nexus at 3.0.x, but there's a BIG BUG with regards to the dm-crypt layer not passing TRIM commands to the flash that turns the phone into a slug after a while, and the bug is fixed in kernel 3.1 and up.
Click to expand...
Click to collapse
Most kernels out right now like ASKP, Franco etc...are based on 3.0.8X. The Gnex isn't stuck on 3.0 either. One of the kernel devs has gotten 3.4 working but a kernel was never released, and there are also apps and scripts that force TRIM so I don't think it's much of an issue but I don't know much about kernels and stuff anyways...
Sent from my Galaxy Nexus using Tapatalk 4 Beta

bmg1001 said:
Most kernels out right now... are based on 3.0.8X. The Gnex isn't stuck on 3.0 either. One of the kernel devs has gotten 3.4 working but a kernel was never released, and there are also apps and scripts that force TRIM so I don't think it's much of an issue but I don't know much about kernels and stuff anyways...
Click to expand...
Click to collapse
It's simple to overlay 3.0.31+ on top of 3.0.x to get 3.0.85, etc., but those only provide minor bug fixes. The part that needs to get into the Galaxy Nexus is from 3.1 or newer, where dm-crypt has a 'discards' option that allows encrypted volumes to TRIM.
As it stands now, encrypted volumes can't TRIM, not even with third-party utilities. TRIM exists to free-up large contiguous blocks of zeroed writeable space, and the dm-crypt in 3.0.x writes encrypted gobbledygook to the entire volume, even empty space. That means that write performance on an encrypted Galaxy Nexus is -always- bad and can't be trimmed.
As for the 3.4... There are Google experimental 3.4 and 3.8 kernels, but they're for newer devices and don't seem to include the various bits-and-pieces that the TI OMAP team added to get the Galaxy Nexus running.
Someone needs to either backport newer versions of dm-crypt to 3.0.x and enable discards by default, or they need to move the Galaxy Nexus-specific code up to newer (3.1+, not 3.0.31+) revisions of the kernel. I prefer the latter, as it would yield many other benefits as well.

[KERNEL][WIP][BOOTS] CAF Linux 3.10.40 kernel

This is a booting CAF 3.10 kernel for none other than our shiny OnePlus One. Personally, I'm satisfied with my phone as it is with a 3.4 kernel (and 3.10 is a lot of work without proper firmware), so I've given up on developing this 3.10 kernel. This thread is just a free-for-all for anyone who wants to have a crack at developing 3.10.
I threw this kernel together pretty sloppily 2 months ago, so I apologize for the lack of full git history from CAF and some messy code from me. The kernel is based off of the LA.BF.2.1_rb1.xx branch from CAF. The kernel should boot as-is on the official CM nightlies, and it is confirmed to boot on my CM12.1 builds. All it requires is updated WCNSS configuration binaries to boot (flashable zip available in the downloads tab of the thread). The kernel currently only supports JDI command-mode panels, and I compiled the kernel with Google's GCC 4.8 toolchain.
Source code: https://github.com/sultanxda/android_kernel_oneplus_bacon-3.10
What works:
It boots (woo)
Display
Touchscreen
Modem (no mobile data though)
WiFi
Charger (not from wall outlets though)
Battery percentage/health reporting
Volume keys
Sensors
USB
Assume everything else doesn't work. Here's a fun screenie: http://imgur.com/H1UERfr
Good luck with haxing 3.10!
XDA:DevDB Information
CAF Linux 3.10.40 kernel for Bacon, Kernel for the ONEPLUS ONE
Contributors
Sultanxda
Kernel Special Features: It boots
Version Information
Status: Testing
Created 2015-07-05
Last Updated 2015-07-06

@Sultanxda Awesome work bro now if only the Cyanogen.org devs supported devices like Sony
arm: qcom: Add SONY Shinano platform, msm8974pro family - https://github.com/sonyxperiadev/kernel/commit/193c3345565d0c3a202f8feac62a21842b06e347
http://developer.sonymobile.com/kno...sh-a-linux-kernel-for-aosp-supported-devices/
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/
http://developer.sonymobile.com/201...ny-presentation-at-embedded-linux-conference/
http://developer.sonymobile.com/201...-xperia-devices-in-sonys-open-device-program/

Awsome work mate. Where can i find the original CAF branch? Somewhere at codeaurora cgit?
Sent from my A0001 using XDA Free mobile app

DerRomtester said:
Awsome work mate. Where can i find the original CAF branch? Somewhere at codeaurora cgit?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yep. https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/?h=LA.BF.2.1_rb1.39

Sultanxda said:
Yep. https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/?h=LA.BF.2.1_rb1.39
Click to expand...
Click to collapse
Thank you. I am gonna create a full git history with that + your commits. If anyone wants access to it to push some code feel free to ask.
Gesendet von meinem A0001 mit Tapatalk

any inherent benefits of having linux 3.10 over 3.4?

_ASSASSIN_ said:
any inherent benefits of having linux 3.10 over 3.4?
Click to expand...
Click to collapse
http://kernelnewbies.org/Linux_3.10
https://github.com/sonyxperiadev/ke...UX_ANDROID_LA.BF64.1.2.1_RB1.05.00.02.019.067

_ASSASSIN_ said:
any inherent benefits of having linux 3.10 over 3.4?
Click to expand...
Click to collapse
Tons!
One I would love to mess with is Heterogeneous Multi-Processing. Also some of the other upstream scheduler commits. For one, they are what make the N6 a true quad core in that it doesn't use any hotplugging, just CPU C states while maintaining pretty decent battery life. It changes how threading works and how workloads are transferred to other cores. At least this is the main thing I would love to see and mess with. Almost makes me want to get an N6. I love my OPO though.

RenderBroken said:
Tons!
One I would love to mess with is Heterogeneous Multi-Processing. Also some of the other upstream scheduler commits. For one, they are what make the N6 a true quad core in that it doesn't use any hotplugging, just CPU C states while maintaining pretty decent battery life. It changes how threading works and how workloads are transferred to other cores. At least this is the main thing I would love to see and mess with. Almost makes me want to get an N6. I love my OPO though.
Click to expand...
Click to collapse
possibly collab with @DerRomtester?

_ASSASSIN_ said:
possibly collab with @DerRomtester?
Click to expand...
Click to collapse
man, that would be cool but it would be a massive undertaking then you would need a road map for other rom Devs to use to even use the work you have done let alone to even be accepted officially from major Roms out there like CM. This is something I have thought about alot but the work needed to put in doesn't match anything near what I would get out of it. This doesn't mean money necessarily but time, time away from family, etc.
This is still something I will take a look at. I wouldn't mind any input from @DerRomtester at all.

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up

First I was excited then I read that this is no longer in development and I'm sad now
P.S. I'd love to see a small group of kernel devs gather around and work on this, surely at first it would be buggy, having even less performance than any kernel for our 1+1 but in the end we'll have a sweet little kernel

evronetwork said:
First I was excited then I read that this is no longer in development and I'm sad now
P.S. I'd love to see a small group of kernel devs gather around and work on this, surely at first it would be buggy, having even less performance than any kernel for our 1+1 but in the end we'll have a sweet little kernel
Click to expand...
Click to collapse
Pretty sure that most devs would use this as a base if it had the proper driver support as it would provide quite the bump for security

evronetwork said:
First I was excited then I read that this is no longer in development and I'm sad now
P.S. I'd love to see a small group of kernel devs gather around and work on this, surely at first it would be buggy, having even less performance than any kernel for our 1+1 but in the end we'll have a sweet little kernel
Click to expand...
Click to collapse
Facts. We need way more collabs man. Unity gets a lot done. I personally know nothing about developing, but I'm a great tester. I'm willing to brick my phone.. Test, bootloop and brick it again lol. Everyone can play a part in the grand scheme of things.

@Sultanxda can you share your kernel with me?
I compiled it but i don't get it booting. You have made some ramdisk changes ? You added an dtb file ?

DerRomtester said:
@Sultanxda can you share your kernel with me?
I compiled it but i don't get it booting. You have made some ramdisk changes ? You added an dtb file ?
Click to expand...
Click to collapse
No ramdisk changes, no missing dtbs. Just ran a mrproper and compiled it exactly as it is on my GitHub, and it boots. Compiled with GCC 4.8 from Google using almost the exact same script I use to compile my 3.4 kernel, with the only change being that the dtb path for the dtbtool is arch/arm/boot/dts/, not arch/arm/boot/ (though you probably already figured that out).

Sultanxda said:
No ramdisk changes, no missing dtbs. Just ran a mrproper and compiled it exactly as it is on my GitHub, and it boots. Compiled with GCC 4.8 from Google using almost the exact same script I use to compile my 3.4 kernel, with the only change being that the dtb path for the dtbtool is arch/arm/boot/dts/, not arch/arm/boot/ (though you probably already figured that out).
Click to expand...
Click to collapse
Thank you mate. I think i know the problem

_ASSASSIN_ said:
Pretty sure that most devs would use this as a base if it had the proper driver support as it would provide quite the bump for security
Click to expand...
Click to collapse
If companies released the drivers we would have 3.10.x, 3.18.x and even 4.2.x kernels(someone would try to do it even if it turned out a failure)
Released drivers also would have better optimised roms and would make a 5 year old device to live forever (new android e.g. android 7? no problem)
OmegaBlaze said:
Facts. We need way more collabs man. Unity gets a lot done. I personally know nothing about developing, but I'm a great tester. I'm willing to brick my phone.. Test, bootloop and brick it again lol. Everyone can play a part in the grand scheme of things.
Click to expand...
Click to collapse
I'm the worst kind of programmer, I mean I do own a degree but the programming language was my weakest link, so I can't help and kernel is one of the hardest parts it needs big ..knowledge to do it :silly:
Now lets not go off topic and wish for someone to work on 3.10.x I mean even if it's buggy and a bit unstable it will bring some new stuff and when it gets stable well then the fun will start

RenderBroken said:
Tons!
One I would love to mess with is Heterogeneous Multi-Processing. Also some of the other upstream scheduler commits. For one, they are what make the N6 a true quad core in that it doesn't use any hotplugging, just CPU C states while maintaining pretty decent battery life. It changes how threading works and how workloads are transferred to other cores. At least this is the main thing I would love to see and mess with. Almost makes me want to get an N6. I love my OPO though.
Click to expand...
Click to collapse
I wasn't exactly interested in 3.10 until i read yours comment. If this kernel can also make opo work like N6 i.e. running always on quad core mode and still maintain good battery lyf, man i would pray that either opo or cm releases 3.10 kernel.
Sent from OnePlus One

abhibnl said:
I wasn't exactly interested in 3.10 until i read yours comment. If this kernel can also make opo work like N6 i.e. running always on quad core mode and still maintain good battery lyf, man i would pray that either opo or cm releases 3.10 kernel.
Sent from OnePlus One
Click to expand...
Click to collapse
This will never happen. From a business perspective, it costs too much for little benefit, and only introduces the potential for more bugs.
However, here is a hint: Bacon's TrustZone firmware does not check metadata when loading firmware images, so you can technically load firmware from any device (ex: you can use Venus firmware from a totally different device).
If you know what you're doing and you have 3 months of your life to burn on this, then it should be possible to get everything working with the LA.BF.2.1_rb1.xx kernel branch.
Sent from my A0001 using XDA Free mobile app