yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
I promise to get around to it at some point, but mainline patches are typically a set of very tiny alterations to code to prevent esoteric bugs, and a large proportion of the patches don't actually affect what gets compiled into our kernel.

Here's the changelog for .64: https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.64

Files affected:

drivers/char/virtio_console.c

drivers/isdn/gigaset/capi.c

drivers/net/loopback.c yes

drivers/net/r8169.c

drivers/net/tg3.c

drivers/net/wireless/rtlwifi/usb.c

drivers/net/xen-netback/interface.c

drivers/net/xen-netback/netback.c

fs/splice.c yes

kernel/resource.c yes

net/bridge/br_netfilter.c

net/core/pktgen.c

net/ipv4/ip_sockglue.c yes

net/ipv4/tcp_input.c yes

net/ipv6/route.c yes

net/mac80211/offchannel.c

net/mac80211/scan.c

net/mac80211/work.c

net/packet/af_packet.c yes

net/sctp/endpointola.c

net/sctp/outqueue.c

net/sctp/socket.c

...so out of 22 files only 7 affect what goes into the kernel, and we're talking about a few lines here and there. For example, in socket.c only one line changes:

kfree(authkey);

changes to

kzfree(authkey);

Now that's in a file that's got nearly 7000 lines of code in it. I'm not saying an unnecessary fix, but it's not a particularly big deal either. All this one does is improve the security of a temporary key by zeroing out the bits in memory before freeing it, rather than just freeing it by allowing it to be overwritten. The chances of someone exploiting your information due to this issue are negligible. And in our case, this code is not even compiled.

Here's an interesting article: http://www.techradar.com/news/software/operating-systems/inside-the-linux-kernel-3-0-1035353

...stating that as of 3.0, the kernel has around 15 million lines of code. With the mainline patches, just very tiny sections of the code are tweaked, and you would probably never notice the effect. Let's for argument say that the nexus kernel uses just 1% of the available code for compilation. That's 150000 lines of code. Let's say 1500 lines of code have been changed in mainline updates, that's 1%. And lets be generous and say that the 1% of code that was changed was code that affects things we do all the time. So the difference between no mainline patches, and all the mainline patches up until this point has a 1% impact on what you see your device doing. Would you notice it? Probably not.

I know it's nice to have them, to know they are there just-in-case, but realistically, it's not going to affect anything in a noticeable way.
[Nexus S Android Development] jabdulk:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Does this Kernel support FUSE File Systems? Trying to test GmusicFS.
[Nexus S Android Development] ciaastek:
Odp: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Just noticed that stock 4.2.2 on GNex has 3.0.31 kernel right? So we're few mainline updates ahead anyway. Only N4 uses 3.4 kernel?
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

All phones have 3.0.31 kernel version, there are few htc and xperia devices which have greater kernel mainline. I think .31 is considered fully stable or something.

Sent from SpeedMachine i9100
[Nexus S Android Development] ciaastek:
Odp: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Oh, didn't knew that. Anyway, if someone is on cm based rom and still want newer(?) mainline, there is devil kernel recommended before by bedalus :)
[Nexus S Android Development] kalinusa:
This Kernel is almost perfect version 7.3.1

Too bad support true testing is over. The main two problems I am having are:

1. Screen rotation has bizarre activity. One time it is totally normal (meaning rotation in apps but not the launcher or the lock screen). Next thing you know the launcher and lockscreen start rotating (which i hate). And then I reboot in order to refresh somehow the system and after the reboot the rotation does not work at all. So I end up rebooting twice.

2. USB mounting simply does not work everytime. For example I just plugged the phone to transfer something and I get no recognition of the USB mounting option. If I reboot the phone it will come back I know.

Those 2 problems happen on this kernel. I am running Jellyshot 3.0. Other kernels act fine overall on those two things.

Any idea anyone?
[Nexus S Android Development] zephiel:
Ohhh! Thank you. Finally. XD
[Nexus S Android Development] treesurf:
Could someone please point me to the default color settings for this kernel?
[Nexus S Android Development] ciaastek:
R: 174xxx

G: 184xxx

B: 250xxx
[Nexus S Android Development] KrisMurdrum:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

I had the same setup on my NS, although I never had any bugs that weren't hw related. Have you tried backing everything up, double check that you have the CM version, the latest gapps, and any mods you use; then go into your recovery and wipe every option (except sd card of course) and to be sure wipe everything thrice (or alternatively if you feel comfortable with adb, use that to wipe everything) before flashing ROM, gapps, kernel, (reboot), mods, reboot and restore apps.

Sent from my Nexus 4 using Xparent Red Tapatalk 2
[Nexus S Android Development] LOVE ME PLEASE:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Do you have a Nexus 4 kernel? You have done great works for my Nexus S...thanks!
[Nexus S Android Development] :
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

I'm using the htc one x+ now. I'm working on a kernel for that.
[Nexus S Android Development] LOVE ME PLEASE:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Well, at least my Nexus S has the smooth and fast power of your kernel, but I know that you One X+ guys out there are going to be pleased.:)
[Nexus S Android Development] noobiekins:
If you ever decide to make a nexus 4 kernel, I'll be GLAD to test it out
[Nexus S Android Development] kalinusa:
I have been planning to do a clean install but it does take sometime no matter how much everything is backed up. It takes me 3h to get it back to speed. But those screen rotation bugs are killing me!!!! Out of the blue the launcher and lockscreen start rotating. It is sooo annoying. I just rebooted and things are back to normal.
[Nexus S Android Development] Pumpino:
It would be great if you did get around to it. I think it's a psychological thing - having a current kernel on an ageing device breathes new life into it. :)

---------- Post added at 09:45 AM ---------- Previous post was at 09:39 AM ----------

That's not accurate. The Nexus 4 has 3.4.0 and the Nexus 7 has 3.1.10. :)
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

I was talking about older phones like nexus s.

Sent from SpeedMachine i9100
[Nexus S Android Development] DerTeufel1980:
AW: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

I honestly don't know why they build a 3.1.10 kernel for it. This mainline of the kernel does not get any further updates since one year now.

I was using it as base in the beggining, but because of 3.0.y still gets (more or less needed) updates, i switched back to this line.

Updating the 3.1.10 kernel is no fun, because one always needs to forward port or back port the commits from 3.0 or 3.4
[Nexus S Android Development] Pumpino:
Yeah, they should have gone with a long-term kernel such as 3.0, 3.2 or 3.4. The kernel devs have said they don't plan to make more recent kernels long-term, as it creates too much work for them, so 3.4 is as good as it's going to get for a couple of years until support for these other versions ceases. That said, I don't know why Google stuck with 3.0.31 for Jelly Bean on the Galaxy Nexus, and 3.4.0 on the Nexus 4. They could at least update them to the latest version of that branch.
[Nexus S Android Development] polobunny:
3.1 is the mutant child nobody really likes, apparently. :p
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

On s2 developer dorimanx has its kernel updated to 3.1 and he is backporting some 3.4 stuff. Its like most popular kernel there. And there is no much difference between that and 3.0.31.
[Nexus S Android Development] polobunny:
Yeah, exactly. Backporting everything from 3.4. That's what DerTeufel was getting at. 3.1 isn't kept and you need to take pieces from 3.4 and 3.0.x :p
[Nexus S Android Development] DJBhardwaj:
I want a little advise here, it will be really appreciated.

A while back, I was using Marmite 7.3 on PA but certainly after every few minutes of reboot, the sensors would stop working (No automatic backlights and screen-rotation. This problem came up with both PA 3.10 and 2.54, pretty much sure that it is a kernel issue because, if I use other kernels like Airkernel or matrix, no such issues come up.

Is their a previous version of this kernel which doesn't suffer from this bug (issue) ? I want to use it very desperately, works far more better than Matrix or Airkernel, in every term. :good:
[Nexus S Android Development] polobunny:
Can't say I've ever had this bug, don't use PA though. Did you re-install the rom over itself without wipe then install kernel?

Kernels that use the anykernel installation script "technically" shouldn't be installed one over the other over and over because they take some part of the setup and recreate it. That can, still technically, create bugs if the part that they take isn't completely compatible.

Usually, re-installing the rom over itself then the kernel fixes most problems cause by that situation. Don't need to wipe anything. If the problem occurs even on a clean slate though, then something else is up.
[Nexus S Android Development] :
cheers alen, I'll have to check that out... the one x+ kernel is 3.1 based
[Nexus S Android Development] andrei1015:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

My current habit is everyday I install the latest cm 10.1 nightly then install this kernel. Today however after installing the kernel my battery dropped from around 50% to 11%. This has never happened before. Any ideas as to what might have caused it? I'm sorry but it didn't occur to me to make a log about it..

Sent from my Google Nexus S
[Nexus S Android Development] polobunny:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Yes, the reboot. Reboot again, you might see your battery jump back to 50%. It's an android bug, not a marmite one.
[Nexus S Android Development] Nexus HAL:
It happens when you reboot your phone with charger connected. No worries.. the battery meter will come back to normal after a few charge discharge cycle.
[Nexus S Android Development] VTL:
I have the same issue with cm and marmite too. Recently I also have changed my battery to new one and now after something around 50% my phone can just power off without any signs or warning… No ideas how to fix it. Maybe just wrong non-linear battery % indication.
[Nexus S Android Development] leap_ahead:
Bedalus look here from facebook page :

Marmite Kernel From Bedalus XDA

173 likes · 10 talking about this
[Nexus S Android Development] polobunny:
And the Nexus S reign ends, as I purchase the SGH-i747M (AT&T Galaxy S3). I'll miss you guys, but I got some money on the side & my carrier is offering me a sweet deal without signing up or anything. I'll see ya on the other side!
[Nexus S Android Development] Basche:
have fun with your new phone :D
[Nexus S Android Development] bravo04:
Hello bro. Want to ask.

If i oc-ing my phone should i raise the voltage too?

Cause sometime i got freeze and reboot while i try to oc my phone with default voltage.

Thanks.
[Nexus S Android Development] anshumandash:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Enjoy your new toy. Hope to see you some day in the next Nexus threads. ;)

Sent from my Nexus S
[Nexus S Android Development] :
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Aww, farewell polobunny, thanks for fielding countless user questions! Thanks for keeping me honest :p I sincerely hope your presence on xda will continue. Hope you find good threads in your new section to help out in. Caliban2 didn't get an s3 did he... Seriously, thanks for all your help! :D
[Nexus S Android Development] polobunny:
I don't recall what Caliban got. Might get a Nexus 4 instead... j/k :p

The S3 doesn't seem as fun to flash compared to the Nexus S (ODIN meh!). First thing I do tonight is root, install a custom recovery and CM10.1. Or try to find a vanilla-ish build of 4.2 instead of the Samsung interface. Never liked OEM customizations.

Edit: Oh and I'm not entirely quitting xda, obviously. This place is THE place for android.
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

There are great debloated and aosp themed roms there, i bet. You have NeatRom Lite i think. Dunno for which s3 version it is. But that rom is beast. Coupled with aosp theme, freeze some apps, use autostart app and greenify. Your phone will fly and it will be awesome. Better than cm10.1 where there is no true project butter. :P

Sent from SpeedMachine i9100
[Nexus S Android Development] polobunny:
There's some CM features I haven't been able to part with. No other rom has decent sound profiles that go as far as CM for one. If one can find something to replace, I will be forever in debt. I once made a thread, but it gave no good result. That's mostly it. Notification toggles most roms will have (even more so with JB), and theming I don't really mind basic AOSP if I can get my hands on blacked out apps (mostly blacked out MMS). :/
[Nexus S Android Development] :
I tried CM and even helped build Slim Bean for the one x+, but it's just difficult when things don't work properly. Like, no proper support for the camera. I bought the phone for it's screen and camera, so I had to go back to sense. Hopefully with the S3 being such a big hit, the developers will be more numerous and will have been able to work around the issues quicker.
[Nexus S Android Development] polobunny:
I think most if not all issues with the multiple S3 variants were long worked out. Just confusing because unlike crespo, there's a billion variants (like 10 wtf) and they have very different specs (quad core 1gb vs dual core 2gb + different frequencies). Excited to get to play with something new though.

Edit: 6:30pm, S3 is rooted. Adios! :P
[Nexus S Android Development] Nexus HAL:
Hi Alen... can you shed some more lights on CM not having project butter? i heard about it several times here n there.. but not sure exactly whats going on. Is it because their custom IOCTL doesn't have ASOP's input boost feature (not entirely sure about that too).. or there's more?

btw, farewell polobunny! enjoy your new device n keep in touch :)
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Well, samsung doesnt want to release exynos sources, so cyanogenmod is using open source drivers (from team hacksung i believe) for gpu (current version is mali v2 for galaxy s2). So there is no true project butter, if samsung releases exynose sources, which is zero chance, cyanogenmod could use them and their roms would have true project butter.

Sent from SpeedMachine i9100
[Nexus S Android Development] polobunny:
Are you sure about all that though? Not that I don't believe you specifically, but there's a bunch of clever people in this world who could work around many things.

All project butter does is enable a more aggressive vsync and enable triple buffering when needed.

Both are good, but not always necessary. The later takes a lot of memory, too.
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

I have galaxy s2, so i read forums a lot. They use open source drivers, so, that drivers cant be any better. Maybe in future, but not right now. UI isnt smooth enough, animations stutters etc. Why do you think there were words that cyanogenmod will abandon galaxy s4. Its because of exynos. They have alot of problems with samsung devices (exynos). Also i had galaxy 3, old one, and devs made their own gpu drivers, but it was easier because of less coding. That drivers made UI to be really smooth, but videos had strange artifacts, some games didnt have color or didnt work etc. There will allways be a problem with samsung because they are not friendly turned to developers. And when i compare cm/aosp roms with sammy roms on s2, sammy roms beats the hell out of cm/aosp roms in terms of smoothness and i would say every other thing you can imagine, maybe except modding, but sammy roms have that too.

Sent from SpeedMachine i9100
[Nexus S Android Development] ABD EL HAMEED:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

Hell ya you're right but what about the G model which uses TI OMAP

Thanks in advance:)
[Nexus S Android Development] polobunny:
Fair enough, but the issue, if any, becomes much less noticeable as phone computing power increases. Frames don't get dropped even with a double buffer, everything is drawn in time, and project butter or not it doesn't really show.
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

If you have quad core device ofcourse its not that noticable. But you can see that when navigating UI its not that silky smooth, its just ok smooth. Also in some more resource demanging games or apps you can notice that its not really top level.

And for post about tiomap, you are talking about s4? If so, there are snapdragon with adreno 320 and exynos with powerVR. Sure snapdragon version will have better development community i bet.

Sent from SpeedMachine i9100
[Nexus S Android Development] mixtapes08:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

TricksterMod integrated BLN and BLD to there settings. Grab it here https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod :D

-3StarsAndaSun
[Nexus S Android Development] ABD EL HAMEED:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

No I meant the TI OMAP for the s2 i9100G

Thanks in advance:)
[Nexus S Android Development] alen1901:
Re: [GUIDE] Build a Kernel! + [KERNEL] marmite_v7.3 MTP

I really wouldnt know, i have i9100. But i think G version doesnt have butter problems, i didnt bother to check that. :)

Sent from SpeedMachine i9100
[Nexus S Android Development] :
Without warning, here comes v8: http://goo.gl/HvUrp

More details later when I've got time. Briefly, I've rebuilt from scratch, but I think I forgot some things, please let me know!
[Nexus S Android Development] leap_ahead:
welcome back !!!

ok I test it ...

that thing is no there : fast charge,bld dimmer,battery 100%, row , smartassv2

also is 403mb ram

pls make it with 412mb ram !!
[Nexus S Android Development] JerryPi:
Hy did a quick test run. Missing is high big mem, only 402mb of reported ram in cm. And bld is also missing, can't set it up neither with nstools, neither in cm settings. If you need anything tested let me know :)

Sent from my Nexus 7
[Nexus S Android Development] alen1901:
Update to 3.0.72 mainline? I think its .72

Sent from SpeedMachine i9100
[Nexus S Android Development] :
For v8.0 apart from the things I've missed, I've added two tweaks, one is ticket based rwsem backported from the 3.8 kernel, which has been working fine in the hox+ kernel for a while. The other is an asynchronous io tweak that ought to improve storage operations a smidgen.

I haven't yet merged in the android/common branch, so I will do that at some point. So far, things are pretty vanilla, so stability should be good. What I like about starting again from the ground up, is that I'm a lot more experienced now, so hopefully this time everything will be just that little bit cleaner.
[Nexus S Android Development] alen1901:
While you are here. About htc. You mentioned they are weird about camera sources or something. Im interested, does htc has true project butter on aosp/cm based rom, is something broken?

Sent from SpeedMachine i9100
[Nexus S Android Development] :
As far as I know, it's working perfectly. It's just when you build aosp, which is a big hack, the camera doesn't work well. The main problem with the hox+ kernel is the hotplugging. It's a horrible lag inducer! I've disabled it completely and written an app to control how many cores are active, which is brutal, but better than lags.
[Nexus S Android Development] alen1901:
Oh, then i guess i wont buy htc device. I was aiming to htc one, but nexus 4 is more likely to be mine :D

Sent from SpeedMachine i9100
[Nexus S Android Development] sidnoit22:
Now that's awesome
[Nexus S Android Development] :
Can we get some cm users on this one: http://d-h.st/muy

Is it still working? What's still missing?
[Nexus S Android Development] rip_noob:
Booting normally, BLN is working.
[Nexus S Android Development] ttakacs:
Same here. So far so good.
[Nexus S Android Development] JerryPi:
Hey i have installed it on my phone. Bld is now working. What i noticed that's still missing is row scheduler, and no voltage control. Otherwise it's working smooth as always :)

Sent from my Nexus S
[Nexus S Android Development] xxxMADxxx:
Just ROW Scheduler and custom Voltage is missing..Running great on MIUIv5..:good:
[Nexus S Android Development] :
v8.1 is here: http://goo.gl/HvUrp

-I've added all the bits I forgot, and updated ROW to the latest available, which also meant updating elevator to handle urgent requests, which is nice.

-Still to do, custom voltage, which I forgot about! :p

It probably won't take me long to get custom voltage back, so if you're not feeling the need to crackflash, it'll probably be available later today. If you don't OC, you might as well use v8.1 though.

EDIT: okay, v8.2 is up, hopefully with custom voltage fixed. Let me know!
[Nexus S Android Development] JerryPi:
V 8.1 is working great on my ns I'm running latest cm monthly and set up bln with init.d script. I saw on your kernel list site that you are planning 412mb kernel. I will eagerly wait for that version ;) On another note, what is the status on user configurable memory? As i recall there was talk about it in the beginning of this year, but then it all went quiet? :)

Sent from my Nexus 7
[Nexus S Android Development] yihtang:
Wow what an unexpected surprise! Thanks for the update, flashing now

EDIT: missing voodoo colour... The washout colour scheme is back now
[Nexus S Android Development] BenHeng:
It's really nice of you to build again for us. Once again I wish we could buy you a beer...

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] fleischbanane:
Works great here with JellyShot 3.3 :)

No problems so far.

Thanks for your work. :)

I use 8.2 CM version.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Nexus S Android Development] leap_ahead:
bedalus on 8.2 not battery 100%,,also u can do it 412 mb ram ?
[Nexus S Android Development] CommanderDuplex:
thx for the awesome Kernel =), i have to ask you if you can add zRam , the nexus s suffers on Ram deficiency so a little bit more "ram" will help ?

i enable zRam on my Galaxy Nexus too and i notice that it helps with "big games" like NFS or Vector may it does on Nexus S too ?
[Nexus S Android Development] leap_ahead:
No bt fix on 8.2
[Nexus S Android Development] :
Hey, thanks for checking.

I'll figure out about bluetooth asap. Voodoo is done. When everything is added correctly I'll do the version with the 412MB ram.

For those wondering, zram is only worthwhile with a swap partition on the flash drive. You don't want paging on the flash drive because it'll wear it out (flash memory has a limited lifespan). You can't get something for nothing.

Edit: bluetooth fix is done

Edit: battery 100% is fixed hopefully! Also voodoo
[Nexus S Android Development] :
Anyone who wants to donate can give a little to slim bean, as it was krarvind who was able to provide mtp