Develop Bugs

[REF] Source code: Unified git repo for GT-I9000 Gingerbread kernel source

Here we go
Common gingerbread-samsung git branch for all of us
This branch contains the fixed Gingerbread source (compiling and working) everyone of us may use as reference git repository.
Fixed in this source:
- all cleaned up gitignores
- missing FSR in Makefile
Take also a look at the updated README.txt that will explain you how to compile and get it working with modules
Also: makes sure you disable, in .config:
[*] Automatically append version information to the version string in menuconfig or CONFIG_LOCALVERSION_AUTO in .config
It will help each developer to exchange patches easily because of the common starting point.
bilboa1 said:
What supercurio means, is that he's offering to have a common GIT repository for the official Samsung kernel of the GT-I9000 (and similar phones).
The GIT tree would contain only Samsung drops and possible other upstream fixes/changes (the kernel being loosely based on the Nexus S kernel, there's at least Samsung and Google as different upstream), as well as bug fixes. No new features etc except maybe Voodoo.
The advantage of that is that the ones not using GIT yet could fork it and make their own kernel variation on a STABLE base. They could also issue pull requests for fixes they made, which would profit everyone. That's the open-source spirit and way of doing things efficiently by the way.
Note that the current GIT already contains fixes for compiling and using Samsung's GB sources with Samsung's firmwares (and binary modules).
I certainly support this idea.
Click to expand...
Click to collapse
How you can fork this repository:
- clone it via github directly
or, if you prefer keeping only this gingerbread branch directly, on your dev computer:
Code:
git clone git://github.com/project-voodoo/linux_gt-i9000.git -b gingerbread-samsung
cd linux_gt-i9000
git remote rm origin
git remote add origin git://your-new-remote-repository.git
git remote add common git://github.com/project-voodoo/linux_gt-i9000.git
This way, for people re-using Vodooo sound for example, it will be as easy as:
Code:
git fetch common
git merge gingerbread-voodoo-sound
If you have more idea of collaboration like that, express yourself
FAQ:
Q: Bleh! I hate this Kernel/ directory.
A: Yes, this was the case for the original commits but now it's a standard Linux repository with everything on its root.
But it didn't worked as expected, so I had to make the change, sorry for the inconvenience to the early adopters.
Q: What happens when Samsung update their source code tarballs
A: I'll update the common git repository accordingly (hopefully fast enough for you)
On your side, all you'll need to do will is.
Code:
git fetch common
− or git fetch git://github.com/project-voodoo/linux_gt-i9000.git
git merge gingerbread-samsung
Say good bye to messy tarballs!
PS: if you're looking to initramfs, take a shot at https://github.com/project-voodoo/samsung_initramfs − contribution welcome.

Good idea, I second that, it will be easier

wrong link
Github reads http://project-voodo.org/

What supercurio means, is that he's offering to have a common GIT repository for the official Samsung kernel of the GT-I9000 (and similar phones).
The GIT tree would contain only Samsung drops and possible other upstream fixes/changes (the kernel being loosely based on the Nexus S kernel, there's at least Samsung and Google as different upstream), as well as bug fixes. No new features etc except maybe Voodoo.
The advantage of that is that the ones not using GIT yet could fork it and make their own kernel variation on a STABLE base. They could also issue pull requests for fixes they made, which would profit everyone. That's the open-source spirit and way of doing things efficiently by the way.
Note that the current GIT already contains fixes for compiling and using Samsung's GB sources with Samsung's firmwares (and binary modules).
Forking in git hub is VERY VERY easy btw.
I certainly support this idea.

Awesome! - I also support this idea

United Galaxy S Developers
Nice idea! Perfect spirit of open source

I hope good things come out og this.

Great move Supercurio - once again !

Simply awesome men

Will the github include the multitouch fix(SGS only using two fingers rather than multiple fingers) that affects Google Maps rotation?

pikachu01 said:
Will the github include the multitouch fix(SGS only using two fingers rather than multiple fingers) that affects Google Maps rotation?
Click to expand...
Click to collapse
The gingerbread-samsung branch promoted here will only contain Samsung kernel sources and won't interfere with other developers modifications.
Only exception is if this source is broken and needs something to work, like nikademus's patch: https://github.com/project-voodoo/linux_gt-i9000/commit/6c8f989f58999770d23236bb172c3a4e1c80586b

It seems that JVK and JVB was pulled from Kies because of an update problem. Looks like we're going to have new ROMs to play with in a week or two (maybe less)
Edit: What about the SSL fix (http://forum.xda-developers.com/showthread.php?t=1040005)

Great, good idea. That's how community development should work!

zorxd said:
Great, good idea. That's how community development should work!
Click to expand...
Click to collapse
Agreed! Thanks for getting things started Supercurio! Now I have to start making a Vibrant branch.

Any chance this code will boot with preempt enabled? Does the MTD driver work with the OneNAND partitions like the NS code does? I'd kind of like to get away from FSR/RFS and such....
Still cloning...

ttabbal said:
Any chance this code will boot with preempt enabled? Does the MTD driver work with the OneNAND partitions like the NS code does? I'd kind of like to get away from FSR/RFS and such....
Still cloning...
Click to expand...
Click to collapse
The code has many similarities with Nexus S one (build from it IMO) and is preempt too

Just a note, I had to edit the Makefile to set the crosscompile variable to the right path
Question: is the generated zImage flashable through ODIN? Don't we need to add the initramfs?

supercurio said:
The code has many similarities with Nexus S one (build from it IMO) and is preempt too
Click to expand...
Click to collapse
Excellent! I just did a defconfig to check it out and saw the preempt in there.. Nice to see Samsung fixing things up a little. Now I need to get a GB ROM to install so I can try to boot.
Thanks again. I'll send a pull request when I have a Vibrant branch ready. Going for minimal modifications, fix touch button mapping and such. People can add whatever they want after that. Now I need to learn the new code tree... wheee! Hopefully the basics are the same, getting the changes into an i9k froyo kernel is pretty easy.

zorxd said:
Just a note, I had to edit the Makefile to set the crosscompile variable to the right path
Question: is the generated zImage flashable through ODIN? Don't we need to add the initramfs?
Click to expand...
Click to collapse
You will need an initramfs... anyone have a default one we can start with for 2.3?
zImage will have to be in a TAR file to flash with Odin. Heimdall can flash a bare zImage, as can the SGS Kernel Flasher tool for Android.
Oh... think I saw a setting in "make menuconfig" for the cross-compiler prefix. Might be able to avoid Makefile mods....

Sorry for the newb question, but how do we generate the initramfs? I guess we could take the one from stock JVB. But how do we extract it and how do we combine our compiled kernel with it?
On a side note, I noticed that CFQ is the default scheduler. Isn't it better to use No-op for flash memory?

[LINK][KERNEL][SOURCE] Boost FL24 + Agat's tREC_v0.2.2

Well source dropped for Boost FL24 so here's the start of the kernel thread!
Source Repo:
https://github.com/garwynn/D710BST_FL24_Kernel
Link to updates, changelog, etc:
http://www.sxtpdevelopers.com/showthread.php?t=119
I'm hoping that keeping these up to date will be easier. If we're lucky we can just change Sprint's kernel and then merge the changes onto this one.
Enjoy!

Thank you. You really hook it up for us

I'm compiling v0.2.0 now after completing a patch application. It's a git diff output that applies all of the changes that Agat63 has been making to Sprint's FL24 kernel to this one. Ideally it should mean that you'll get all of the changes with no ill effects as I wouldn't be compiling it if the apply command listed any significant issues.
When it comes out I really need feedback on this please. Try it out, let me know if it's working okay. Thanks!

0.2.0 released.
So long as there are no issues this should be a fairly easy process to keep all 3 on the same page.

[KERNEL][4.3.x] Kernel755 | PIE | 16/12/2013

A day may come when the courage of men fails, when we forsake our friends and break all bonds of fellowship.
But it is not this day! Today, we PIE!
Kernel755​Let the adventure begin!​
KEWL FEATURES:
1,7 GHz OC!
Lots and lots of governors!
3 extra schedulers!
-O3 optimized!
Moar to come!
AWESOME DOWNLOADS:
The newest release (release, not alpha): http://bit.ly/1jccQXY
More downloads, including alphas and old releases in the changelog in the 3rd post!
FUNNY DISCLAIMER!
Code:
You are free to use this software, but it's not my fault if (when) you mess something up.
Please be careful and beware of being late to work, exploding cows and eating radioactive pie.
Kernel sources: https://github.com/someone755/Kotato/tree/jb_mr2_chocolate_rmfx
XDA:DevDB Information
Kernel755 - PIE, Kernel for the Sony Xperia S
Contributors
someone755
Kernel Special Features:
Version Information
Status: Abandoned
Current Stable Version: N/A
Current Beta Version: a1
Beta Release Date: 2013-12-16
Created 2013-12-16
Last Updated 2014-07-30

And now, a FAQ. @franciscofranco's FAQ, updated to fit our device.
F.A.Q. - Read this before complaining!
1. My phone exploded, HALP!
A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Paste it on pastie.org and link it on your post. Logcats are useless for Kernel purposes, don't bother posting them.
2. OMG BETTARY SUCKZ, IT DEAD IN 45 MINUTAS, HALP!
A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.
3. How do I flash this?
A: Since it's an .elf file, it's only flashable through fastboot. The general command is "fastboot flash kernel.elf"
4. OP is arrogant, I'm gonna call the Internet Police?
A: Deal with it.
5. Touch Control doesn't work in rXXX release, you suckas, fix plixe!
A: I don't know who you are. I don't know what you want. If you are looking for a fix, I can tell you I don't have the solution. But what I do have are a very particular set of skills; skills I have acquired over a very long career. Skills that make me a nightmare for people like you. If you leave now, that'll be the end of it. I will not look for you, I will not pursue you. But if you don't, I will look for you, I will find you, and I ignore you.
6. What's up with the kernel's name?
A: Well I have '755' in my name. So there's that...
7. I'm on stock/CM10/CM9/GB and this kernel doesn't work.
A: This kernel is ONLY for CyanogenMod 10.2 and any ROMs that came of it (like AOKP, for example). Don't flash on anything else unless you are SURE the ROM is based off of OpenSEMC's CM10.2.
8. My Locked-bootloader phone won't boot with this/I can't flash it.
A: This is a custom kernel. It requires an unlocked bootloader.
9. What app do you recommend for dealing with CPU settings?
A: Use TricksterMod. For 2D GPU OC and setting the 2nd core's governor, I recommend Kernel Tuner. Both are feature-packed and free, and if you don't mind an extra icon in your drawer, I say get both.
10. What is the difference between releases marked as a# and r#?
A: The r# releases are considered the most stable, but do not pack all the features. Because my work is rather slow, I'll add an alpha, an a# release, every time a minor change is introduced. But even if they look and feel stable, do not consider them as such. Most of them are dirty builds!!! Meant for advanced users only, so distributed in fastboot-flashable format ONLY!
11. I want to support you and your work!
A: Putting a subtle sign in your signature that you're using my kernel (or like it or have used it). Please, no big banners or anything, just the name of the kernel. That would be appreciated the most.
And now, thanks!
@RaymanFX -- helping me with nearly all issues and, of course the kernel sources. Also for an old project from which I learnt how proper GPU OC is done.
@abcdjdj -- writing a neat tutorial on how to compile kernels, and telling me about the -w flag
@letama -- adding a few new words into my dictionary (initramfs=ramdisk, did you know that!? )
@hei1125 -- for the NOVA kernel, and its' sources
@Forzaferrarileo -- for his kernel, Forzaferrarileo
@IAmTheOneTheyCallNeo, @fusionjack and @DJLamontagneIII -- for detailed toolchain and compiler flags explanation
@franciscofranco -- for inspiring me to get this done
@Wendigogo -- for SCSI and USB fixes help
@cronot -- for new logo and bringing in .96 fixes
@aebob -- for awesome logo idea
@thicklizard -- for helping with -O3
Sony and Google -- Android rules
HTC -- Inventing S-ON, forcing me to buy a Sony phone :3
@all -- for being an awesome community! C:

Changelog!
Code:
a1: [URL]http://bit.ly/1jccQXY[/URL]
-initial release
--O3
-CPU OC
-All governors from POTATO (4.2.x) kernel (lots of 'em)
-All schedulers from POTATO (4.2.x) kernel (zen, fifo, fiops)

I'll give it a try in Letama's dual boot as soon as I have time

I trust you know what you're doing, Wise one.
Still, it is dangerous to go alone. Here, take this. *Hands free pie*

Hey someone755,where are the potatoes??

Well I gotta change something from release to release

many people are moving to a cm11 based rom...
will you make a kernel for that as well?

No, not just yet.
I see 4.3 more stable, while KitKat is still in its early stages.
Also, I see KitKat will be updated more frequently, but I'm lazy, so no.

someone755 said:
No, not just yet.
I see 4.3 more stable, while KitKat is still in its early stages.
Also, I see KitKat will be updated more frequently, but I'm lazy, so no.
Click to expand...
Click to collapse
I see Kitkat gotten more stable than 4.3.. Since video recording and other issues from 4.3 are solved in it.. So probably its best either if Rayman releases a BETA version of 4.3 fixing the bugs or u switch to 4.4 kernel.. :silly: Just an opinion..

I tried your potatoes 4.2.2 kernel and it was great
Waiting for your kitkat kernel since I'm running cm11
Sent from my LT26i using xda app-developers app

Hi,
Just to be sure : this is a kernel for CM10.2 or JB-4.3 roms right ?
You ask it's an optimized -O3 built kernel. Did you solve your problem with /cache size and -O3 optimisations ? Will you build a potatoe kernel (for JB-4.2) including these optimisations ?
Cheers

Yes, it's for CM 10.2/Android 4.3 (OpenSEMC, of course),
Potatoes already have -O3
And just saw that KK is in Beta stage. Might give that a shot, Pie isn't all that popular, as it would seem.
Just need to hang in there for another week, my last part for my custom rig is just around the corner (hopefully).

Thank you for your kernel and for smooth video recording.
I very like OmniROM with your kernel.
I have only two small problems:
- TWRP is little slower than with other kernel (backup taken about 20 minutes)
- I'm not able to select "smartass v2" governor (I thik you have typo in your script, because there are two names in one row (see screenshot)

Lol sorry, I must've derped the Makefile. It'll run nightmare, not smartassv2 if you select it...
About TWRP, I don't have a clue, I never even used CM10.2...
I'll look into fixing it tonight, if I find the time.

Possible Custom Kernel for LG E980 CM11

I want to create a custom kernel for the LG E980.........what do I need to learn to do so.......I have never made a kernel before so any help would be appreciated.....Thanks In advance

This belongs in general not development
Sent from my LG-E980 using Tapatalk

justin860 said:
This belongs in general not development
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
Sorry I'm new to XDA

rjmxtech said:
I want to create a custom kernel for the LG E980.........what do I need to learn to do so.......I have never made a kernel before so any help would be appreciated.....Thanks In advance
Click to expand...
Click to collapse
read. lots and lots of reading. and be patient.
search around xda for the how-to threads on kernel building and customizing.
i started work on a 4.3 kernel a while ago before we had stable cm-10.2 official builds, but abandoned it after the switch to the lge-kernel-gproj sources because i just don't have the time.
my suggestion is to check out the sources for other devices' custom kernels, such as those for the lge mako/optimus g, htc one/m7, and samsung gs4/jflteatt. you can probably cherry pick batches of commits from some of those kernels, but be sure you have a sense of what the changes do, or at least which modified files do what. also, it's worth noting that not all kernel sources are structured the same way even though they're all linux kernels. so cherry pick with caution.
be sure that you update the defconfig for the correct device in arch/arm/config (or create a new one for your custom kernel). if you're forking the lge-kernel-gproj sources from cyanogenmod (which i highly recommend as your base), there is already a defconfig for the e980.
um...other things...as far as over clocking and undervolting, when you browse other kernels' sources, you'll want to look at the commits involving cpufreq and/or acpuclock-8xxx (don't recall the specifics off the top of my head). iirc, start by looking in arch/arm/mach-msm and see which files were most recently modified.
good luck, and if you need help, i suggest checking out the project rookie threads (search xda). as long as you ask nicely and keep a courteous attitude, folks in those threads are extremely helpful.

Question regarding kernel patcing/updates

I kind of feel as if this should be a very basic topic and that I should not be having to post a new thread on it... but, out of curiosity, does anyone know whether or not the Android kernel-- which as we all know is a flavour of the Linux kernel-- can be updated through "patching" as the regular Linux kernel can? The reason I am asking is that I greatly prefer to run my device with a custom kernel that has extra features over the stock kernel, however, it seems like every custom kernel that is released is released as a one-shot deal, and that the only way to have a kernel that continues to be updated with fresh source is to run the kernels that are provided with the nightly ROM builds.
Of course, I could go the route of learning how to build my own kernels and add features to them.. but I guess my basic question is, does there exist any form of "general patch" that is periodically released by Google, or the Linux Kernel foundation, etc., that will bring your current kernel up-to-date with the latest system-wide changes (secuturity & stability fixes, etc), while leaving the bulk of the kernel and the kernel configuration in place? Or is that a totally unrealistic and impractical concept? I do build my own kernels from source for my laptop, but I know very little about compiling a kernel for android.. anyway, if there are any kernel devs still on this device's forum, what do you guys think?
Any feedback from knowledgeable individuals much appreciated.. thank you!

No. You would have to build the kernel and flash it yourself. You can usually find HTC's kernel source on their website for each device. You take that kernel and manually patch the updates yourself.