Database Users

ICS just dropped to AOSP

Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Click to expand...
Click to collapse
http://groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f

Just read this on AndroidPolice. Very excited!!!

Game.....on!
Sent from my PG86100 using XDA App

Developers make some rom's!!!!!! (Please)

this thread should make its way over to the development section. Thanks for the find op
Update: Already there

I'm actually curious about how long it will take for someone to make an A500 ICS ROM based on this. There is bound to be someone to do it, but who gets the #1 spot?

Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1

They're not necessarily requirements, but more or less just recommendations. A more average computer could still compile ICS, but it will just take a lot longer. And I'm betting Thor will be the first to cook us a ROM. Hopefully soon
Sent from my HTC Glacier using xda premium

FloatingFatMan said:
Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1
Click to expand...
Click to collapse
Those are only recommendations for developer workstations. It is certainly possible to compile it even on a low-grade office PC if you give it a week.

Hence my saying it won't be soon...

FloatingFatMan said:
Hence my saying it won't be soon...
Click to expand...
Click to collapse
Your still not understanding my friend. Unless your definition of soon is in 30 minutes. Peter Alfonso that develops for the OG Droid and a few other devices compiled his in about 1 hour and 45 minutes. That was a laptop core i7 and 8gb of ram.
Thats not whats going to be time consuming. The hard part will be finding/getting the hardware inside our devices to work. I asked THOR on his forum about ICS on the iconia, his response:
done know for now... depends how many proprietary stuff the a500 uses....
I'm worried the camera, sensors and battery as these seam to be tampered with...
for the moment I'm busy with other stuff will see when I get some time to sneak a peak at the code...
Click to expand...
Click to collapse
Time will tell.

I'm sure FFM understands that. As you say, the hard part is getting the hardware to work, but with a slower machine, how many test builds can you do in a day? With a big fast machine that can build in a few hours vs a laptop that might take a few days can make a huge difference of when you get to your final release.
But hey.. i don't know anything, so why don't I just shut up...

It takes about 3.5 hours for me to build a new version of ICS. I'm on a 3 year old laptop which is why it takes so long. It would be great to have a much newer machine to build with as it would help to make things go faster.

So I guess that Google engineer was taling out of his butt then.

SE Android - ROM for Thunderbolt

So it seems the NSA has released their source code for SE Android (previously they built SELinux as well). This is a more sandboxed and secured version of Android based on the work they did in Linux.
This is the basis for Government grade secure Android devices that they are intending to deploy.
The build instructions list using AOSP as the basis and building from there, as it's primarily kernel compiling. That being the case you could (theoretically) kang almost any rom by recompiling and repackaging. I have not released any rom's or anything like that, so this (for now) would be nothing more than a packaged release of vanilla AOSP + SE Android kernel. As I get my feet under me I might tinker with some customizing, but wanted to see if there was an interest, otherwise I will just knock it out for me and skip updating.

i'm interested to see what you can come up with. Develop is slow here so anything is greatly appreciated. I came from the hd2 and development there is still awesome.

Interested. Have any links for code information as to what they did to implement security?
Sent from my ADR6400L using Tapatalk

Sure thing:
Turd Furguson said:
Interested. Have any links for code information as to what they did to implement security?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
http://selinuxproject.org/page/SEAndroid
Looks like mostly they ported the SE linux stuff over.

I'm also interested in this, I'm planning on releasing a build of this spliced with CM7 on Rootzwiki, since nobody else had started it yet.
They've mostly only made the major pieces of SELinux working with the Android kernel, and have a few userspace modifications on top of that. It'd be alot more C/C++ work than Java I'm afraid if specific tweaks need to be built.
I'm planning on beginning work when I get back to the U in a few days. Will you have a repo we can pull from for building? I have distributed compiling capabilities and we're on a shared 300meg link, I can build/upload if you'd like from your base?

At a workshop I attended to present a research paper of my own back in October there was discussions of building hypervisors into Android to separate out normal app space & business(secure) app space such that even if you had an evesdropping bit of malware it couldn't listen in on the business phone app as it was separated from the normal app space where the malware would live. But tie that into a SELinux style android kernel would likely make it significantly more beneficial.
I wonder how hard it would be to put the two together? Or if SEAndroid would defend against such threats on its own w/ out needing to build in hypervisor level security as well? Guess it might be worth investigating but definitely interesting and excited to look at further. Thanks for posting!!

I'm interested!

I wonder if the CM team would consider merging this into their builds, that would put it in a league of its own...a powerful ROM with many enhancements and exceedingly secure...just awesome.

I'd be interested in this. I just stumbled upon the whole SEAndroid thing while looking for ways to secure Android from some (seemingly?) legitimate apps that nevertheless ask for massive permissions (i.e., Juicedefender). It's just extremely difficult these days to tell, as often these sensitive permissions may actually be needed by the app to conduct its business.
I've actually been waiting on taking the plunge to root my phone (yes, overcaution, I know)...a strong, secure ROM based on SEAndroid would make me do it!

I would be interested in this also.

any development for the tbolt here is welcome. id be interested to see how this plays out. thanks for the hard work im sure your putting into it

Future updates

What do you guys want to see in future updates? There are a lot of features missing that should have been implemented earlier, like multitouch.
Personally I would like to see better wifi options, such as being able to use a proxy server and a different DNS server.
Any other thoughts?

I think we'll see very little improvements from B&N. They are standing firm on this only being an E-Reader. I think they missed the boat since our NST makes a great daily planner. I think any "real" upgrades will come from the talented developers have here.

Now, hypothetically, if someone was to obtain the source code for the version of android that the nook runs, hypothetically speaking of course, would they be able to make changes to that code and then deploy it to the nook?
Hypothetically speaking, of course.

brendan10211 said:
Now, hypothetically, if someone was to obtain the source code for the version of android that the nook runs, hypothetically speaking of course, would they be able to make changes to that code and then deploy it to the nook?
Hypothetically speaking, of course.
Click to expand...
Click to collapse
Quit using 'hypothetically' So much or I can't take you seriously.
But not exactly, it's basically gotta be ported & pieced together.
You can give it a go if you're not an Android n00b but it's mostly in the hands of a Dev who's familiar with Source Code and packing things together.
Sent from P920G 2.3.5

brendan10211 said:
Now, hypothetically, if someone was to obtain the source code for the version of android that the nook runs, hypothetically speaking of course, would they be able to make changes to that code and then deploy it to the nook?
Hypothetically speaking, of course.
Click to expand...
Click to collapse
Another thing, if there's a Nook running it then yes, I would recommend looking up flashing a baseband.
If you're trying to get to GB or ICS or something more, you're gonna need to flash a KDZ & Base band so that version of Android could be ported onto your device.
Sent from P920G 2.3.5

Oh, the hypothetically thing... umm... yeah

brendan10211 said:
Oh, the hypothetically thing... umm... yeah
Click to expand...
Click to collapse
I'm not sure what you mean at this point. Are you trying to allude to something? Or is this an Office Space reference?
The NST is on Android 2.1. If we're getting into "wants" and not "expects", it sure would be golly-gee-wonderful to at least be up to 2.2. Hell, ICS for that matter.
Realistically, if it doesn't relate to core B&N reader functionality on the device, I'd be very surprised to see much at this point. They need some bug fixes, definitely. The network enhancements, plus the ability to handle more complex wifi portals, would be reasonable (though, I suspect, not likely, since it opens up the "browser" hole they obviously want to squelch).
What core B&N reader functionality requires multitouch? It would be great, of course, for OTHER software to make use of.
It is encouraging that 1.1.2 seems to have fixed some wifi incompatibilities, so the device is getting some love. There are still core reader functions such as last-read and book page count errors that need to be fixed. Hopefully, we'll at least see those someday.

Sorry for being so stupid. I have never seen Office Space before in my life.

brendan10211 said:
Sorry for being so stupid. I have never seen Office Space before in my life. (
Click to expand...
Click to collapse
It's worth a watch. You'll enjoy it.

Maybe once I fix my nook.

Compiling Android sources on the Pi

Hi Folks
Recently I helped Adam Outler get adb compiled for his Pi This was not as simpe as it first sounds because as we learnt adb on the host is subtlety different from the one compiled for the target and the AOSP source tree does not support compiling androids host tools for arm out of the box.
However You can add the armv6l host support by creating the file
Code:
<aosp source root>/build/core/combo/HOST_linux-armv6l.mk
The contents of which should look something like this
Code:
# Configuration for builds hosted on linux-armv6l.
# $(1): The file to check
define get-file-size
stat --format "%s" "$(1)" | tr -d '\n'
endef
HOST_SDK_TOOLCHAIN_PREFIX :=
ifneq (,$(strip $(wildcard $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc)))
HOST_CC := $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc
HOST_CXX := $(HOST_SDK_TOOLCHAIN_PREFIX)/g++
HOST_AR := $(HOST_SDK_TOOLCHAIN_PREFIX)/ar
endif # $(HOST_SDK_TOOLCHAIN_PREFIX)/gcc exists
HOST_GLOBAL_CFLAGS += -fPIC
HOST_GLOBAL_CFLAGS += -include $(call select-android-config-h,linux-x86)
HOST_GLOBAL_CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
HOST_NO_UNDEFINED_LDFLAGS := -Wl,--no-undefined
You can now use the native pi toolchain to build with the aosp sources, at the very least you'll be able to compile the host tools such as fastboot , adb natively on the Pi. Whether you'll want to go about compiling a full android build using the Pi and whether that is even remotely sensible is a discussion for another day! :laugh:

Hey, thanks for your work on this. Sensible or not, it would be pretty cool to run an AOSP or even a CM build on your phone that was compiled on your Pi.
I tried compiling Boot2Gecko for my SGS2 on my Pi as well, but that kept dying about 6 hours into the build .
I got really lost (just learning all this stuff now), but learning it all while building a project you really like would be far more interesting that learning it while building "nano" or "Vim".

fewesttwo said:
Hey, thanks for your work on this. Sensible or not, it would be pretty cool to run an AOSP or even a CM build on your phone that was compiled on your Pi.
I tried compiling Boot2Gecko for my SGS2 on my Pi as well, but that kept dying about 6 hours into the build .
I got really lost (just learning all this stuff now), but learning it all while building a project you really like would be far more interesting that learning it while building "nano" or "Vim".
Click to expand...
Click to collapse
Yes or compile on the Pi for the Pi, If you want to try do that there's the beiginings of the other side, i.e armv6 target files on my github, It actually targets armv5te because that is already present as a valid target in the AOSP build system, a throwback to pre gingerbread and the HTC Dream ( G1 ) etc.
Thinking about it though, The build system may need a little more adding as I think only x86 based cross compilers will be currently selected for target compilation. I'm yet to get my Pi, there's currently a 6 week lead time on them and I'm thinking about holding out for the 512MB version. Until then it's QEmuPi for me!
The Android build system is pretty forgiving and will let you compile things piece-meal which is good because I don't think it would make it all the way to the end in one go no matter how many hours you give it.

Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.

AdamOutler said:
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.
Click to expand...
Click to collapse
Indeed, it's at https://groups.google.com/forum/?fromgroups=#!forum/android-contrib

AdamOutler said:
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.
Click to expand...
Click to collapse
Hi Adam, Thanks for that, I never really considered it, Last time I read, which admittedly was a long time ago now, they were a little more averse to submissions from the random punter. Maybe they've soften up, or maybe I've just made the whole thing up in my mind It would look alright on my c.v ( resume to you guys ) . However It's far from ready for that. There's some more tweaks to add to it, maybe commands like "make host" to just build the host platform would make sense on a device with limited resources like the Pi
pulser_g2 said:
Indeed, it's at https://groups.google.com/forum/?fromgroups=#!forum/android-contrib
Click to expand...
Click to collapse
You're the second person to do that to me! Someone drops a "google groups link bomb" on me and I lose an hour of my life reading all the posts, It's like low rent alien abduction! LOL :silly:

AdamOutler said:
Trevd, I asked JBQ on G+ and he said you should contact android-contrib for how to submit your work to be integrated to AOSP. . I'm pretty sure its a mailing list.
Click to expand...
Click to collapse
I was bored waiting for my board so thought I ask if google want an hand, well more of a full arm than just an hand.
Me On Google Groups said:
https://groups.google.com/forum/?fromgroups=#!topic/android-contrib/w5UWtdSTwSg
Hi
I've recently added linux-armv6l to the android build system as a HOST_ARCH so I could build adb natively on the raspberryPi. Is this something you would be interested in adding to the official build system?
Let me first explain why you wouldn't want to accept this.
1. Adam Outler from XDA-developers.com suggested I make this enquiry, Initially, I refrained, given the limited scope of the change I had make which focuses on armv6l specifically and although I would be Interesting to see just how long an AOSP build would take on the RasPi soley from a technical view, I don't think there would be anything to be gained from officially supporting such a device as I made the code publicly available through GitHub.
However upon further consideration this feature can have a much broarder appeal if it was changed to a more general linux-arm HOST_ARCH. Given Arms' current "March" into the server market plus the availability of higher end fast multicore processors such an addition may have a practical real-world application soon then rather than later.
I look forward to hearing your thoughts on this.
Thanks
Click to expand...
Click to collapse
As I pointed out, Arm is getting more desktops now-a-days so they might do this one themselves
[EDIT] Here's the Big Man's Reply
JBQ From AOSP said:
I think we could consider it in principle.
However, I'm not convinced that building all of Android on an ARM host
will be practical any time soon. Because of that, I'd rather avoid
extensive changes much beyond adding HOST_linux-arm.mk. For now, I'll
also want to rely on the distribution's host compiler, to avoid having
to deal with the weight and licensing issues of prebuilt toolchains.
What scope do you have in mind?
BTW, I suggest that you wait until the source release of Android 4.2.
We've been tweaking the build system such that it's easier to control
what gets built, and that might be helpful in your case.
JBQ
Click to expand...
Click to collapse
Looks like a goer then. Because thats the only file I had to add to strart with..

[ZEN-KERNEL] 3.10-zen for nexus 9 - testers

Call me crazy but the best kernel for the nexus 6 is coming to the nexus 9, a device I don't have
Zen kernel is pretty sane and doesn't have changes like SuperMegaIOBlastFrequency5Million, but somehow it manages a bigger improvement than all those changes put together primarily through better CPU scheduling for the light-numa workloads of our mobile devices (in other words, BFS)
I have a BFS port from v461 (minus SMT nice )for 3.10 android/msm along with most of Alfred Chen's -gc branch includes as well.
Anyway, the effects are noticeable in the nexus 6 (no more google now launcher lag, no more big list lag, no more 3 second clear all recent delay, better power consumption through better frequency scaling by design of sticky tasks)
I think it will be just as good on the nexus 9, however I don't have one of these devices in my possession so I'm not gonna ask for people to buy me one instead I'm just going to ask for testers.
I'd like to see the effects of BFS on arm64 and I'm sure everybody else would like to see the benefits -zen kernel brings.
PM me if you would like a weekend build. I need at least 3 but the more the merrier.
Zen kernel for nexus 6
Thanks,
B

Also if you ask for a build tell me what ROM and existing kernel you are on if applicable.

Will you be getting a N9 in the future?
Sent From Capsule Corp.

Ace42 said:
Will you be getting a N9 in the future?
Sent From Capsule Corp.
Click to expand...
Click to collapse
Probably not, I graduate next month and plan on expanding my open source endeavors then but I'd like to support the nexus devices + 1 or 2 other flag ships with zen at all times.
People are happy over at N6, they were happy back on gnex and evo 4g I'm sure they will like nexus 9 version too
The custom kernel landscape has changed since the old days because there's less problems with new devices, but zen still finds a way
I'm really looking to change issues as I see them here. I don't want to bolster big names, give me money, this project is mine, etc. I want to bolster the community effort in a way that aids in learning, growth , etc. Zen is all about real kernel improvements. in time there is an app I've had on the shelf for 3 years with a brilliant framework among other things that I want to GPL-ize and release.

bbedward said:
Probably not, I graduate next month and plan on expanding my open source endeavors then but I'd like to support the nexus devices + 1 or 2 other flag ships with zen at all times.
People are happy over at N6, they were happy back on gnex and evo 4g I'm sure they will like nexus 9 version too
The custom kernel landscape has changed since the old days because there's less problems with new devices, but zen still finds a way
I'm really looking to change issues as I see them here. I don't want to bolster big names, give me money, this project is mine, etc. I want to bolster the community effort in a way that aids in learning, growth , etc. Zen is all about real kernel improvements. in time there is an app I've had on the shelf for 3 years with a brilliant framework among other things that I want to GPL-ize and release.
Click to expand...
Click to collapse
At some point in time years ago I was a know nothing, figure out how to apply a patch, compile a kernel amateur. But through a great Linux, gentoo, arch , etc . community I have now become a proficient programmer, graduating with computer science + engineering degree in a few weeks.
the XDA community hasn't been about helping people learn or grow in any form. Its become a pit of protecting private property and don't take my work, don't ask dumb questions, just give up. I want to see more community efforts rather than private all mine type of stuff.

I've always wanted to develop a ROM or kernel, but the steps to just get Linux on my laptop is too much let alone driver support. If there was a simple way to use just windows 8 I would like to contribute to the N9 community.
Also I commend you for your studies, neither of those fields are easy from what I've heard. :good:

bbedward said:
At some point in time years ago I was a know nothing, figure out how to apply a patch, compile a kernel amateur. But through a great Linux, gentoo, arch , etc . community I have now become a proficient programmer, graduating with computer science + engineering degree in a few weeks.
the XDA community hasn't been about helping people learn or grow in any form. Its become a pit of protecting private property and don't take my work, don't ask dumb questions, just give up. I want to see more community efforts rather than private all mine type of stuff.
Click to expand...
Click to collapse
I was like you a know nothing about kernels
I started kernel development knowing nothing
I still don't know much but, I'm learning slowly
Im vary interested in the source code
Also to test

Ace42 said:
I've always wanted to develop a ROM or kernel, but the steps to just get Linux on my laptop is too much let alone driver support. If there was a simple way to use just windows 8 I would like to contribute to the N9 community.
Also I commend you for your studies, neither of those fields are easy from what I've heard. :good:
Click to expand...
Click to collapse
Thanks, many linux distributions nowadays make it incredibly easy to get started though I'd venture to say most of them will work out of the box with your hardware.
USBhost said:
I was like you a know nothing about kernels
I started kernel development knowing nothing
I still don't know much but, I'm learning slowly
Im vary interested in the source code
Also to test
Click to expand...
Click to collapse
Probably will have a test Friday, just going to use AnyKernel2 for the N9 probably (only replace fstab with f2fs support and no force encryption).
The N6 tree is here:
https://github.com/bbedward/ZenKernel_Shamu
The BFS branch is here (I split everything into individual branches on Zen):
https://github.com/bbedward/ZenKernel_Shamu/commits/sched_upstream_bfs_gc
Some of the stuff from my N6 kernel is a drop in for the N9 since they are both 3.10 based.

https://www.dropbox.com/s/uekphwlxvm2pya9/v3.10-zen0_anykernel_N9.zip?dl=0
Please make sure you have a backup plan if it doesn't work
It has almost identical to Zen-nexus 6 stuff:
- My sched_upstream_bfs_gc branch pretty much identical to the N6 kernel branch
- Not identical to the N6 branch because nvidia has a bunch of nonsense sched stat stuff I added into BFS also
- Fiops/BFQ in addition to the default stuff
- ext4 from v3.10.y stable
- newest f2fs
- usb fast charge support
- 2A charging
- fsync toggle
- upstream MM stuff from v3.10.y
- Several race condition fixes, memory leak fixes from upstream
- flar2 wake gesture support
- overclock support whatever elementalX has up to 2.5GHz
- USB fast charging
No idea if it works, please have a backup ready.
There's lots of compile warnings in the tegra kernel and I had to build myself an aarch64 compiler because I didn't have one.

bbedward said:
https://www.dropbox.com/s/uekphwlxvm2pya9/v3.10-zen0_anykernel_N9.zip?dl=0
Please make sure you have a backup plan if it doesn't work
It has almost identical to Zen-nexus 6 stuff:
- My sched_upstream_bfs_gc branch pretty much identical to the N6 kernel branch
- Not identical to the N6 branch because nvidia has a bunch of nonsense sched stat stuff I added into BFS also
- Fiops/BFQ in addition to the default stuff
- ext4 from v3.10.y stable
- newest f2fs
- usb fast charge support
- 2A charging
- fsync toggle
- upstream MM stuff from v3.10.y
- Several race condition fixes, memory leak fixes from upstream
- flar2 wake gesture support
- overclock support whatever elementalX has up to 2.5GHz
- USB fast charging
No idea if it works, please have a backup ready.
There's lots of compile warnings in the tegra kernel and I had to build myself an aarch64 compiler because I didn't have one.
Click to expand...
Click to collapse
Will test tomorrow
How did you update f2fs?

USBhost said:
Will test tomorrow
How did you update f2fs?
Click to expand...
Click to collapse
I will push the source up once I can later tonight. It's quite hefty so it will take awhile to push up the first time
The way I did everything is almost the exact same as the N6 kernel. Some nvidia garbage had to be implemented into BFS but that's it. And the device specifics like OC, 2A charging, etc.
https://github.com/bbedward/ZenKernel_Shamu/commits/f2fs_upstream
everything is exactly the same except the first f2fs commit "Sync with kernel/f2fs.git linux-3.10 branch"
There I basically just delete everything in fs/f2fs. copy/paste fs/f2fs from that branch, copy include/linux/f2fs* include/trace/events/f2fs (maybe? I forget where all the headers are exactly) and also update the Documentation/filesystem/f2fs.txt
The only reason I do that is because the f2fs/linux-3.10 branch is oddly based on linux-4.0. So simply merging or cherry picking won't work too well, and things like the msm and tegra kernel have different versions of f2fs already. So i just clear it all out and sync with that.
After that I pulled in all the newer commits from the f2fs/dev branch.

bbedward said:
I will push the source up once I can later tonight. It's quite hefty so it will take awhile to push up the first time
The way I did everything is almost the exact same as the N6 kernel. Some nvidia garbage had to be implemented into BFS but that's it. And the device specifics like OC, 2A charging, etc.
https://github.com/bbedward/ZenKernel_Shamu/commits/f2fs_upstream
everything is exactly the same except the first f2fs commit "Sync with kernel/f2fs.git linux-3.10 branch"
There I basically just delete everything in fs/f2fs. copy/paste fs/f2fs from that branch, copy include/linux/f2fs* include/trace/events/f2fs (maybe? I forget where all the headers are exactly) and also update the Documentation/filesystem/f2fs.txt
The only reason I do that is because the f2fs/linux-3.10 branch is oddly based on linux-4.0. So simply merging or cherry picking won't work too well, and things like the msm and tegra kernel have different versions of f2fs already. So i just clear it all out and sync with that.
After that I pulled in all the newer commits from the f2fs/dev branch.
Click to expand...
Click to collapse
O so thats how you did it
I was scratching my head with all the problems of cherry-picking I was having lol

Source is up:
https://github.com/bbedward/ZenKernel_Flounder
The real glory lives here:
https://github.com/bbedward/ZenKernel_Flounder/commits/sched_upstream_bfs_gc

bbedward said:
Source is up:
https://github.com/bbedward/ZenKernel_Flounder
The real glory lives here:
https://github.com/bbedward/ZenKernel_Flounder/commits/sched_upstream_bfs_gc
Click to expand...
Click to collapse
Thanks man

bbedward said:
https://www.dropbox.com/s/uekphwlxvm2pya9/v3.10-zen0_anykernel_N9.zip?dl=0
Please make sure you have a backup plan if it doesn't work
Click to expand...
Click to collapse
Could you provide a boot.img, to be used as in
Code:
fastboot boot boot.img
I tried with the zImage but that did not boot at all and I don't dare to flash it - yet

taronas said:
Could you provide a boot.img, to be used as in
Code:
fastboot boot boot.img
I tried with the zImage but that did not boot at all and I don't dare to flash it - yet
Click to expand...
Click to collapse
Did you flash it through recovery? This is where it needs to be flashed.
I plan on only providing AnyKernel version for the N9 though, so it requires existing ramdisk.

Somebody has to be willing to try this for me. All you have to do dirty flash your ROM or flash another kernel if it doesn't work.

bbedward said:
Somebody has to be willing to try this for me. All you have to do dirty flash your ROM or flash another kernel if it doesn't work.
Click to expand...
Click to collapse
Will do in a few hours
Ps I tryed what you did with f2fs
it built but data did not mount
I was encrypted also

Didn't boot for me. Tried on a 32gig encrypted n9, running cm12.1, wifi

dictionary said:
Didn't boot for me. Tried on a 32gig encrypted n9, running cm12.1, wifi
Click to expand...
Click to collapse
Maybe because CM12.1 is 5.1 based? This is all based on stock kernel.
I will look to see if there's compatibility issues.