Develop Bugs

Building CM 10 using the Linaro tool chain

Hi, I've set up a Linux box at home and set up a build system on it. It's working great so far. I just saw in the CM nightly thread that GCC 4.7 and Linaro should now be supported with some recent nice commits. Could somebody please point me in the right direction on how to build CM 10 using that compiler/tool chain instead of the default one?
Big thanks!
Sent from my HTC One X using xda app-developers app

ViperFred said:
Hi, I've set up a Linux box at home and set up a build system on it. It's working great so far. I just saw in the CM nightly thread that GCC 4.7 and Linaro should now be supported with some recent nice commits. Could somebody please point me in the right direction on how to build CM 10 using that compiler/tool chain instead of the default one?
Big thanks!
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
dont know if this helps mate but here are a few links...apologies if they are not the ones you are looking for
http://forum.xda-developers.com/showthread.php?t=1846651
http://www.kernel-xp.net/index.php/en/guide/25-android/32-build-cm10

Goku80 said:
dont know if this helps mate but here are a few links...apologies if they are not the ones you are looking for
http://forum.xda-developers.com/showthread.php?t=1846651
http://www.kernel-xp.net/index.php/en/guide/25-android/32-build-cm10
Click to expand...
Click to collapse
Hi,
thanks, but those guides seems to be regarding setting the build system up (which I allready got working).
I'm wondering about how to use the GCC 4.7 compiler instead of the default one.
Thanks anyways!

No one else with some ideas? Was planning on building my own Linaro 9.12 builds and sharing them, but I'm to much of a noob when it comes to building CM...

ViperFred said:
Hi,
thanks, but those guides seems to be regarding setting the build system up (which I allready got working).
I'm wondering about how to use the GCC 4.7 compiler instead of the default one.
Thanks anyways!
Click to expand...
Click to collapse
If you're using ubuntu and its variants, you can try the following(should work for any debian based ones)
Code:
rm /usr/bin/gcc
rm /usr/bin/g++
ln -s /usr/bin/gcc-4.7 /usr/bin/gcc
ln -s /usr/bin/g++-4.7 /usr/bin/g++
To change back to your original compiler, you can just repeat the steps but change the version of the gcc and g++(4.7 to your version)

wcypierre said:
If you're using ubuntu and its variants, you can try the following(should work for any debian based ones)
Code:
rm /usr/bin/gcc
rm /usr/bin/g++
ln -s /usr/bin/gcc-4.7 /usr/bin/gcc
ln -s /usr/bin/g++-4.7 /usr/bin/g++
To change back to your original compiler, you can just repeat the steps but change the version of the gcc and g++(4.7 to your version)
Click to expand...
Click to collapse
Thanks! Will try that out!
:good:

Hm...seems the kernel is build using gcc 4.6 anyways. Will look into some CM buildscripts and try to find where to change compiler...

Could it be that CM10 buildsystem is using the prebuild and prebuilds directories for gcc?

Yeah prebuilt is where it's found.
When the Linaro toolchain was experimented with in CM9 you had to cherrypick it.

Rusty! said:
Yeah prebuilt is where it's found.
When the Linaro toolchain was experimented with in CM9 you had to cherrypick it.
Click to expand...
Click to collapse
So...do you know how I could use my system gcc (4.7) instead of the prebuilt one?
Thanks!

You have to edit your envsetup.sh to point to the chain you want to use.

Rusty! said:
You have to edit your envsetup.sh to point to the chain you want to use.
Click to expand...
Click to collapse
Ok, is it the ARM_EABI_TOOLCHAIN that should be set?
Big thanks Rusty! for helping me out here... :good:

Yeah that rings a bell. There might be two of them to set.

I don't know if this will be any help to you?
http://forum.xda-developers.com/showthread.php?t=1759007

[Kernel] SuperSick for GSM & CDMA

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is the SickleKernel for the HTC One V (primoc and primou). The source code has been modified to support both devices in a unified development environment. To assist in the development, simply checkout the source code, add a feature, test it and push the changes to my gerrit with the included gerrit script in the kernel's root. All changes will be reviewed and tested, and if the code is up to spec, will also be accepted. All contributions are greatly welcome.
The current goal of this kernel is to get the MSMFB from the jb_chocolate branch of CAF to boot fully on this device. Currently the goal of this project is to get past the black screen currently encountered so that we can have proper msm_fb drivers in jellybean and more easily port a 3.4 kernel. The current URL for the work (and booting caf drivers is here NOTE: Booting drivers means booting with a black screen.) We must properly initalize the panel of this device, but as soon as that is accomplished there will not be any problems with jellybean vsync.
Major Changes:
Code:
Add gerrit script to allow others to contribute to kernel code
compiled with cfx 3.8.1 toolchain
Fix Makefile flags so that kernel compiles on 4.8 GCC toolchains
Add google snappy
add -fno-pic flag for some compilers to fix wifi module
fix jb-4.2.2 no booting issue with MSMFB
Add XZ compression
patch to 3.0.67
Fix multitouch issue
Add cflags to optimize the code such as cortex9 and funloop
add primou board files
fix wakelock of bluetooth (caused bad battery life)
add new KGSL drivers for jellybean
fix compile warnings in 3.0.56 for gcc 4.6 (google prebuilt)
patch to 3.0.56
fix bluetooth in kernel
add overclock
fix warnings
Installation guide:
Use this awesome guide by the helpful cybervibin
How to compile:
1) download this tested toolchain
2) get kernel source here (Current branch is "jellybean-4.2")
3) put the toolchain in your $HOME directory
4) be sure your system has all the dependencies to build a kernel (system-devel, gcc, ect)
5) cd to the kernel source
6) issue the command `make ARCH=arm primoc_defconfig` NOTE: If building for gsm, primou_defconfig should be used
7) issue the command `make -j4 ARCH=arm CROSS_COMPILE=`echo "$HOME/prebuilts_gcc_linux-x86_arm_arm-eabi-4.8/bin/arm-eabi`"`
8) grab the kernel from arch/arm/boot/zImage and the modules from drivers/net/wireless/bcmdhd/bcmdhd.ko
9) create a boot.img with either mkbootimg and mkbootfs or android kitchen (Android kitchen is reccomended)
NOTE:
mkbootimg flags:
primoC base is 0x14300000 and ramdisk is 0x15300000
primoU base is 0x13f00000 and ramdisk is 0x14f00000
command line for both is console=ttyHSL0,115200,n8
Source:
here Current branch "jellybean-4.2"
Any bug reports should be posted here
Downloads:
Primoc V42 for 4.2.2 roms (ION) -> Here
MD5: fa0e631d340f06e67ebfeed5f2ed99f7
Primou V42 for 4.2.2 (PMEM) -> Here
MD5: d275623756c850b0936323d90292f9b4
Thanks:
maxwen
jmztaylor
synergy (CFX 4.8.1 toolchain)
lloir
tehwafflez (for buying me a wonderful bus pirate)
BeyondExistence

Great job simon!
Sent with my HTC One V+ with super slick jan 3rd kernel

Wafflez asked all the questions I'm wondering, lulz.
Let's see where this goes. :thumbup:
Sent from my HTC One V using Tapatalk 2

Tehwafflez said:
So just making sure here, is this kernel is for 4.0 or 4.1?
And it will not work with sense roms
So aka stock 4.0 or cm10/ pa/ akop right?
I am really looking forward to improved battery life and sleeker performance ^_^
Sent from my 4.1 PACman 15.3 with sick kernel 2.0.0 One V using xda app-developers app
Click to expand...
Click to collapse
when he said AOSP m guessing 4.1.X
its just a guess,
so simon whats new, i mean the changelog?

Improved for jellybean. I'm working on the commit for sysfs vsync and that will make us ready for 4.2.. video cam will be added eventually its just a matter of messing with it enough
Sent from my One V using Tapatalk 2

simonsimons34 said:
Improved for jellybean. I'm working on the commit for sysfs vsync and that will make us ready for 4.2.. video cam will be added eventually its just a matter of messing with it enough
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Ohhh I see..good luck
Sent from my One V using xda premium

version one released. Should be the same as sick kernel with a little better performance with lionheart governor
http://files.simonsickle.com/?dir=htc/primoc/kernels

How about Multi Touch fixes? One thing I noticed about Jelly Bean is that using 2 fingers cancels both touch gestures.
I play Minecraft on my One V, and when playing, I can't because I can barely move due to multi-touch not be liable.

Multi touch is in the ROM. Not the kernel drivers. The drivers have comments that state multi touch support exists
Sent from my One V using Tapatalk 2

I noticed it works fine in things like launchers, but not games. It cancels all touches.... Any ideas?
Sent from my HTC One V using Tapatalk 2

Contact that app developer
Sent from my One V using Tapatalk 2

I just went back to stock sense lol. Ill have to try it out next week with jmz rom
Sent from my HTC One V using xda app-developers app

I'll also be taking over CM10 for a bit. Jmz lent unlimited io his phone to get us all soff
Sent from my One V using Tapatalk 2

Curiousn00b said:
I noticed it works fine in things like launchers, but not games. It cancels all touches.... Any ideas?
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
if ur talking about JB, maybe cause its still in beta stage!
---------- Post added at 08:26 AM ---------- Previous post was at 08:25 AM ----------
simonsimons34 said:
I'll also be taking over CM10 for a bit. Jmz lent unlimited io his phone to get us all soff
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
s-off ???? really?,yay!

cybervibin said:
s-off ???? really?,yay!
Click to expand...
Click to collapse
The guys there are amazing. It probably won't be long at all
Sent from my One V using Tapatalk 2

simonsimons34 said:
The guys there are amazing. It probably won't be long at all
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Woah who is Jmz working with to get us soff? I am looking forward to this and hopefully it won't be crazy tricky to get it either
Sent from my One V using xda app-developers app

he donated to unlimited.io there's no promises but these guys are good. Also team blueridge, which lloir me and kalaker belong to (I'm one of the two founders ) has found a hopeful method for one v CDMA. It is the same way as the wildfire s. We just need the proper diag bin... but back on track. Create a general thread else please
Sent from my One V using Tapatalk 2

cybervibin said:
if ur talking about JB, maybe cause its still in beta stage!
Click to expand...
Click to collapse
I always figured it was the kernel until Simon just taught me something. I can't use CM10 because of reboots and that touch glitch. That's all that keeps me away. xD
Sent from my HTC One V using Tapatalk 2

simonsimons34 said:
The guys there are amazing. It probably won't be long at all
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
so i dont know if its just me but your links to download are not working it just reports that it has "problems loading page" if anyone has already gotten this kernel plz pm me with link so i can get hooked up really want to try this out thx

Its back again. Server issues earlier
Sent from my One V using Tapatalk 2

[Kernel Base][3.4.55][Dev]Bare Repositories of TW/AOSP Kernel (4.3 Sammy Sources!)

Up-to-Date Bare Repositories for TW/AOSP 4.2.2 Kernel​samsung-kernel-jfltexx​
Short Info:
I've made this repository to have a central place for everyone to fork their kernel base from. The advantage of this repo is that it is always up-to-date (as in the latest linux kernel version). Imagine the difference from starting at a 3.4.0 kernel base and 3.4.52 kernel base, there are thousands of new patches in that patch range. :good:
Repository Url:
Code:
https://github.com/broodplank/samsung-kernel-jfltexx
Repository Info:
Name: samsung-kernel-jfltexx
Description: Bare repositories for jfltexx (i9505)
Branches: tw-4.2.2 and aosp-4.2.2 (aosp 4.3 coming when 4.3 kernel sources are released)
tw-4.2.2 = Stock i9505 TouchWiz Kernel from Samsung sources patched until latest linux kernel version
aosp-4.2.2 = i9505g Google Edition Kernel (for AOSP 4.2.2 Google Edition and TouchWiz 4.2.2) (for i9505)
Getting the sources:
If you want to compile the kernel directly without much changes it's advised to clone it:
Code:
git clone [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url] -b branchname
If you want to make your own kernel it's advised to fork the kernel:
- Login at github
- Go to https://github.com/broodplank/samsung-kernel-jfltexx
- Click Fork at the right top of the page
Click to expand...
Click to collapse
Usage Info:
Initializing first config:
Code:
make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
Configuration:
Easiest variant (QT based GUI, needs libqt4-dev libqt4-core and libqt4-gui)
Code:
make xconfig
Default variant:
Code:
make menuconfig
Other less popular variants:
(GTK based, doesn't need any special packages)
Code:
make gconfig
(Ncurses based, needs libncurses5, libncurses5-dev and libncursesw5)\
Code:
make nconfig
Building Kernel:
Code:
export ARCH=arm
export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
make -jx (where x is the amount of cpu cores + 1)
Toolchains:
Toolchains that are suited for building the sources are:
arm-eabi-4.6
Click to expand...
Click to collapse
Building boot.img:
Code:
./build_bootimg
(Choose the rom type you will be using and it will be created in build/output)
Flashing boot.img and modules:
Code:
./flash_bootimg
(This is a process that pushes boot.img to your phone and then to the kernel partition, after that you can choose whether to push modules or not, and finally you can choose to wipe dalvik-cache or not and it will reboot.
Updating Info:
If you have forked the repository do this to fetch the updates from this repository:
First add it to the remote:
Code:
git remote add bare [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url]
git fetch bare
Then search for the commit(s) that you want to merge
For 1 commit:
Code:
git cherry-pick [commit hash here, this is the last part of a commits url]
(for example: https://github.com/broodplank/samsung-kernel-jfltexx/commit/612bbea08b67f16dd5628cb8cd8406973f8fe821 would be: 612bbea08b67f16dd5628cb8cd8406973f8fe821)
For a range of commits:
Code:
git cherry-pick [commit a hash]^..[commit b hash]
Where commit a is the oldest commit and commit b the newest.
for example:
Code:
git cherry-pick 0bff3bdba64c58ea6100d72763f2be3acc9659db^..612bbea08b67f16dd5628cb8cd8406973f8fe821
This would patch the sources from 3.4.40 to 3.4.52

Latest Repository Changes:
3-08-2013
- Switched to real samsung 4.3 sources
29-07-2013
- Updated aosp-4.2.2 and tw-4.2.2 to 3.4.55
25-07-2013
- NEW BRANCH: AOSP-4.3
- NEW BRANCH: TW-4.3
- Added MSM8960 Headers from Google!
23-07-2013
- Update to 3.4.54
14-07-2013
- Update to 3.4.53
- Merge sensor fix from faux123
13-07-2013
- Updated defconfigs for proper building
09-07-2013
- Update to 3.4.52
- Sensor fix by ausdim
- Large update to readme
06-07-2013
- Add samsung sources
- Patch to latest version 3.4.51
- add boot.img creator
05-07-2013
- Initial commit, make repository

Thanks, I just forked it.
I'm a noob at this but am learning fast. I've modified and compiled the 3.0.31 kernel for the 9210T but I'd like to now try 3.4. Appears none of the celox changes for board_msm8x60.c source came across from 3.0 to 3.4 so I think I've got my work cut out for me.
m0tter

This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?

harise100 said:
This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?
Click to expand...
Click to collapse
InitRamfs??
Permisions of initramfs?

ausdim said:
InitRamfs??
Permisions of initramfs?
Click to expand...
Click to collapse
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks

ausdim said:
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks
Click to expand...
Click to collapse
Thank you for trying to help me... but it still doesn't work. Same result.

harise100 said:
Thank you for trying to help me... but it still doesn't work. Same result.
Click to expand...
Click to collapse
Tonight Ill do a little research on this and tell you the solution.

I remember when I started to make my first kernel, I had similar problems with the Samsung sources.
Wanam gave me his jf_defconfig file and it worked. He said that the config file by Samsung is crap. But I forgot to ask for details.
If I use my config file on your sources, it results in a bootloop, whereas they work fine with Samsung update 2 sources.
Does that make sense?
Sent from my GT-I9505 using xda app-developers app

Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2

.c0dy said:
Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
What is your problem?
Sent from my GT-I9505 using xda app-developers app

harise100 said:
What is your problem?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I hate it -.- xD
Now it worked. And I do not know why... As I am pretty new to this, as already said, - could this be the problem? :
I think I made this:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ make xconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
Click to expand...
Click to collapse
instead of:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig
Click to expand...
Click to collapse
So I used xconfig before setting ARCH and CROSS_COMPILE.
Could that be the problem?
Atm i can not paste the error. The first one had something to do with a buffersize. Could "fix" that by setting "CONFIG_FRAME_WARN=1024" higher. Because it said it was 1032.
Second error was something like "‘ret’ may be used uninitialized in this function [-Wuninitialized]".
---------- Post added at 08:08 PM ---------- Previous post was at 07:32 PM ----------
Will add a new post for this, if it's okay.
And i hope it's okay to ask in here
So, first, as wrote in my previous post the compiling worked.
Now, i did the following:
1. Changed in the config: "kernel compression mode -> LZO
2. Removed "Optimize for size"
3. And changed the flag in the makefile to O3.
kernel/workqueue.c: In function 'freeze_workqueues_begin':
kernel/workqueue.c:483:11: warning: array subscript is above array bounds [-Warray-bounds]
error, forbidden warning: workqueue.c:483
make[1]: *** [kernel/workqueue.o] Error 1
make[1]: *** Waiting for unfinished jobs....
While writing this I reset "Optimize for size" and restart compiling. Now it does seem to work.
So i guess there is a problem with the flag. Where is the right place of the flag?

If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ah okay, thanks. Will see if I can find a few more infos about that

broodplank1337 said:
Tonight Ill do a little research on this and tell you the solution.
Click to expand...
Click to collapse
Did you find anything?
I do have a working build environment and I can compile and install a kernel that is better than stock kernel.
Only these sources don't work. How is that possible?
Sent from my GT-I9505 using xda app-developers app

.c0dy said:
Ah okay, thanks. Will see if I can find a few more infos about that
Click to expand...
Click to collapse
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b

broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
It will work if you have the right toolchain, I use this one:
http://www.mediafire.com/download/i...linaro_4.7.4-2013.07-build_2013_07_12.tar.bz2
It's an optimized Linaro toolchain (http://forum.xda-developers.com/showthread.php?t=2098133)

broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
Thanks Will try that.
I already compiled a kernel, but it just booted until the samsung logo.. after that instant reboot... :/

Ls970-zvc kernal tar

Here ya go some goodies for u ....
Kernal tar text :
1. Android Build
- Download original android source code ( jelly bean 4.1.2 ) from http://source.android.com
- Unzip opensource packages of LS970_OptimusG_Android_JB_LS970ZVC_Android.tar.gz into downloaded android source directory
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo 1 geehrc4g_spr_us 1
c) m -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
- After build, you can find output at out-geehrc4g_spr_us/target/product/geehrc4g
2. Kernel Build
- Untar using following command at the android folder
tar zxvf LS970_OptimusG_Android_JB_LS970ZVC_kernel.tar.gz
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- make j1sp-perf_defconfig ARCH=arm
- make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
3. After build, you can find the build image(zImage) at arch/arm/boot/
New upload of Kernal zvc :
https://docs.google.com/file/d/0B1DGsUzId7AHdXl1RWNNYXFGcHc/edit?usp=docslist_api
Lg ls970_zvc license link : https://docs.google.com/file/d/0B1DGsUzId7AHN2NuUXBnd3c1SnM/edit?usp=docslist_api
Sent from my LG-LS970 using Tapatalk 4

Built date submit * Fri Jul 13 2013 Crutcher Dunnavant * - changed to provide snprintf and vsnprintf functions
Sent from my LG-LS970 using Tapatalk 4

bigfdaddy2 said:
Built date submit * Fri Jul 13 2013 Crutcher Dunnavant * - changed to provide snprintf and vsnprintf functions
Sent from my LG-LS970 using Tapatalk 4
Click to expand...
Click to collapse
Is this what the guy was talking about in the post about the Optimus G software update?
Sent from my LG-LS970 using xda premium

This is the kernal for that software update coming ...
Sent from my LG-LS970 using Tapatalk 4

Sent from my LG-LS970 using Tapatalk 4

bigfdaddy2 said:
This is the kernal for that software update coming ...
Sent from my LG-LS970 using Tapatalk 4
Click to expand...
Click to collapse
Ok. That's what I thought, I was just too lazy to read.
Sent from my LG-LS970 using xda premium

_dannyboy said:
Ok. That's what I thought, I was just too lazy to read.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Lol it all good
Sent from my LG-LS970 using Tapatalk 4

Phone appman is set at test server and so is the bau server .... hopefully lets me get a lil sooner ... unsure whether appman and bau needs to be test server or staging server ....
Sent from my LG-LS970 using Tapatalk 4

bigfdaddy2 said:
Here ya go some goodies for u ....
Kernal tar text :
1. Android Build
- Download original android source code ( jelly bean 4.1.2 ) from http://source.android.com
- Unzip opensource packages of LS970_OptimusG_Android_JB_LS970ZVC_Android.tar.gz into downloaded android source directory
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo 1 geehrc4g_spr_us 1
c) m -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
- After build, you can find output at out-geehrc4g_spr_us/target/product/geehrc4g
2. Kernel Build
- Untar using following command at the android folder
tar zxvf LS970_OptimusG_Android_JB_LS970ZVC_kernel.tar.gz
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- make j1sp-perf_defconfig ARCH=arm
- make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
3. After build, you can find the build image(zImage) at arch/arm/boot/
Kernal DL : https://docs.google.com/file/d/0B1DGsUzId7AHVXlVN2tBWXRYUE0/edit?usp=docslist_api
Lg ls970_zvc license link : https://docs.google.com/file/d/0B1DGsUzId7AHN2NuUXBnd3c1SnM/edit?usp=docslist_api
Sent from my LG-LS970 using Tapatalk 4
Click to expand...
Click to collapse
Nicely done, did you see anything new building the kernel from source.
Sent from my LG-LS970 using xda app-developers app

I haven't done any building with it to test ....I just was able to pull the kernal from the new update heading our way .... I know evoloutionmods,neighborhood hacker have put it into some builds and are testing it out ....
Sent from my LG-LS970 using Tapatalk 4

bigfdaddy2 said:
I haven't done any building with it to test ....I just was able to pull the kernal from the new update heading our way .... I know evoloutionmods,neighborhood hacker have put it into some builds and are testing it out ....
Sent from my LG-LS970 using Tapatalk 4
Click to expand...
Click to collapse
Nice, Hopefully this will fix the bug issues, I think they are doing this too prepare the phone at the end of year for android 4.3

tommyjoesanders said:
Nice, Hopefully this will fix the bug issues, I think they are doing this too prepare the phone at the end of year for android 4.3
Click to expand...
Click to collapse
I don't believe we will receive 4.3 I know we will get 4.2 but they say it will be by end of year .... Lg seems to usually do 4-5 updates to their top tier phones .. We have had two major updates and know this minor update thats coming and the first minor update for ICS equals our 4 updates lol...
Sent from my LG-LS970 using Tapatalk 4

Posted new upload of zvc kernal ... I messed up last night while uploading ....
Sent from my LG-LS970 using Tapatalk 4

bigfdaddy2 said:
I don't believe we will receive 4.3 I know we will get 4.2 but they say it will be by end of year .... Lg seems to usually do 4-5 updates to their top tier phones .. We have had two major updates and know this minor update thats coming and the first minor update for ICS equals our 4 updates lol...
Sent from my LG-LS970 using Tapatalk 4
Click to expand...
Click to collapse
We've had one major update. 4.1.2. We started with zv7, zv8 and 9 were bug fixes. ZVB is the only major one I can think of. Zvc seems fairly minor.
Sent from my LG-LS970 using xda app-developers app

Sorry to resurrect a dead thread but this is the only one that I saw that talks about compiling from LG kernel source.
I think I did everything like your instructions say but the output folder for my kernel doesn't have a zImage file. The closest name is Image but it's 14.4MB (way bigger than viper kernel, for instance) and it doesn't boot via fastboot boot Image. I'd appreciate it if anyone could give me some pointers.
EDIT: looks like I hadn't installed lzop, never mind.

VoluntaryMan said:
Sorry to resurrect a dead thread but this is the only one that I saw that talks about compiling from LG kernel source.
I think I did everything like your instructions say but the output folder for my kernel doesn't have a zImage file. The closest name is Image but it's 14.4MB (way bigger than viper kernel, for instance) and it doesn't boot via fastboot boot Image. I'd appreciate it if anyone could give me some pointers.
EDIT: looks like I hadn't installed lzop, never mind.
Click to expand...
Click to collapse
I tried it using toolchain 4.6.3, among many others, and at best, the error was with the tsp.drv. When I removed it it compiled fine. But no boot.
How did you get past that error? Also, I have issues getting the modules to compile. How'd you fix that?
I'm trying to learn in my spare time so that's probably my problem. TIA
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
I tried it using toolchain 4.6.3, among many others, and at best, the error was with the tsp.drv. When I removed it it compiled fine. But no boot.
How did you get past that error? Also, I have issues getting the modules to compile. How'd you fix that?
I'm trying to learn in my spare time so that's probably my problem. TIA
Click to expand...
Click to collapse
I just started with the source of Viper Kernel, it's ZVC based and already have some good fixes.
You can also see the source I'm working on at bmos/JB_LS970ZVC_Adder, although mine isn't booting right now (although I'm about to try toolchain 4.7 which it says it is optimised for)

[KERNEL][LINARO] Modded stock kernel - d802 [G2 + G3 ROMs][v0.41]

Modded Stock kernel - d802
Features
Based on latest LG source
Built with Linaro 4.8 stable toolchain
Optimised with -O3 compiler flags
Various other optimisations to make it very fast and stable
Updated GPU drivers from Code Aurora
Updated CPU drivers from Code Aurora
3 phase thermal control (temporarily disabled)
rgb screen colour adjustment
faux sound control
CPU voltage control
Compatible with G3 ROM ports (tested on Cloudyfa and Optimus)
Please see changelog for more features and updates.
I will not be adding overclocking and extra goveners as I really don't see the need for it on a device that performs as well as the G2 does already.
Download
here.
I have a D802 on 3 in the UK and it works fine for me, just flash in recovery and enjoy.
As always, I accept no responsibility for loss or damage.
Changelog
26-4
Compile kernel with linaro using -o3 compiler flags
Added support for CyanogenMod DSP Manager (this broke LG's audio effects)
Added DSP Manager apk and supporting files
27-4
Merged in the latest changes from LG kernel source
This includes Knock Code and LG's audio fix
Fixed support for both DSP and LG's audio effects
29-4
Just a rebuild after cleaning up source and commiting to github
30-4
SCHEDULER: Autogroup patch
lib/memcopy: use glibc version
lib/string: use glibc version
Optimized ARM RWSEM algorithm
jbd2: Fix use after free after error in jbd2_journal_dirty_metadata()
msm: Fix high load average from uninterruptible waits
vfp - compile with neon
vfp: hardfloat
vfp: since we use hardfloat, change the modifer accordingly
Update Makefile cflags for unaligned-access and unroll-loops
defconfig: remove a lot of debugging, stats, logs and tests
03-5
Switched toolchain to linaro 4.8
Updated kgsl from CAF
04-5
Readded KnockCode to kernel and ramdisk
Only compatible with Roms based on D80220D (may work with others, not tested)
16-6
n_tty: Fix n_tty_write crash when echoing in raw mode
futex-prevent-requeue-pi-on-same-futex.patch
futex: Validate atomic acquisition in futex_lock_pi_atomic()
futex: Always cleanup owner tid in unlock_pi
futex: Make lookup_pi_state more robust
25-6
arm: Add option to skip buffer zeroing
ion: Skip zeroing on secure buffers
30 commits to kgsl (GPU driver)
Upgrade gpu ion from caf
Update cpufreq from caf (CPU driver)
Remove SECUREBOOT from ramdisk (fixes boot on G3 port)
v0.2
Added 3 phase thermal control
Get rid of __cpuinit calls from whole kernel
Fix storage settings on G3 port
Fix user adjustable rgb in kcal
v0.3
Added faux sound control
Added CPU voltage control
v0.4
Disabled thermal control for now to fix camera lag
fixed exfat support (untested)
v0.41
Reduced min voltage to 750000
Donations
Donations are always wlcome and appreciated, I've put a lot of my free time into this project.
If you would like to donate please follow this link.
Thank you.
Source
Click here to view my kernel source on github.
I WILL SUPPORT OTHER MODELS WHEN I GET THE TIME

LG released a kernel that fixes the issue and adds knock code
Sent from my LG-D801 using Tapatalk
---------- Post added at 10:51 PM ---------- Previous post was at 10:51 PM ----------
Never the less, great find!
Sent from my LG-D801 using Tapatalk

osmosizzz said:
LG released a kernel that fixes the issue and adds knock code
Sent from my LG-D801 using Tapatalk
---------- Post added at 10:51 PM ---------- Previous post was at 10:51 PM ----------
Never the less, great find!
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I didn't know that, have they released the source?
Sent from my LG-D802 using Tapatalk

bruce2728 said:
I didn't know that, have they released the source?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Yeah they released it about 24 hours ago or so. I believe they do. I never look at it, but I remember someone mentioning the release of the code
Sent from my LG-D801 using Tapatalk

Thanks ill edit the thread title tomorrow to kernel with dsp manager or something. I've turned the pc off now and I'm going to bed.
Sent from my LG-D802 using Tapatalk

Can confirm that the hiss bug is finally totally fixed with lg's update!

@bruce2728 !!! I know You from Sensation Development, nice to see You here! Will we see some good stuff for G2 from You?
Damn, it's good too see that dev community is getting bigger.
Oh and I can confirm - for example dorimanx used 20B source in His kernel update, and dr87 will use it in upcoming Mahdi Rom beta update.
Btw, it would be nice to see a nice AOSP kernel, just an advice

reas0n said:
@bruce2728 !!! I know You from Sensation Development, nice to see You here! Will we see some good stuff for G2 from You?
Click to expand...
Click to collapse
Maybe. I've only had the phone since Wednesday, i didn't know lg had fixed this bug already so i did it myself.
This replaces the lg sound effects with CM's dsp manager.
Sent from my LG-D802 using Tapatalk

OMG bruce the Sensation Awesome Developer is Joining Us
I think I will stick around to see another awesome kernel and custom build from you
I love your kernel on sensations man

the legendary developer from sensation, nexus 4 and now on g2

Hello,
Thank's for this mod.
Does the kernel is also patched for booting on the 4.2.2 bootloader ?

6ril1 said:
Hello,
Thank's for this mod.
Does the kernel is also patched for booting on the 4.2.2 bootloader ?
Click to expand...
Click to collapse
I used AutoRec to install recovery which downgrades the bootloader and it works for me.
I added the patch to dts with the dummy strings.
Sent from my LG-D802 using Tapatalk

bruce2728 said:
I used AutoRec to install recovery which downgrades the bootloader and it works for me.
I added the patch to dts with the dummy strings.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Ok thank's for your answer.
For understand well, if we have a d802 4.4.2 with custom recovery and we install your mod, we'll keep custom recovery ?

6ril1 said:
Ok thank's for your answer.
For understand well, if we have a d802 4.4.2 with custom recovery and we install your mod, we'll keep custom recovery ?
Click to expand...
Click to collapse
Yes, this only flashes a boot.img and puts a few files in /system
It will not touch the recovery partition.
Sent from my LG-D802 using Tapatalk

New version coming in a minute with knock on fix as the knock code seems to break knock on if you don't have KC installed.
Sent from my LG-D802 using Tapatalk

That is by design I think. I had the same impression. Knock code disables knock on.

albsat said:
That is by design I think. I had the same impression. Knock code disables knock on.
Click to expand...
Click to collapse
Actually my touchscreen is faulty, nothing to do with the kernel though. I talked with lg because I would tap on a link for example and it would select one about a centimetre below it.
I've got to sent it back to 3uk for replacement.
Sent from my Nexus 7 using Tapatalk

bruce2728 said:
Actually my touchscreen is faulty, nothing to do with the kernel though. I talked with lg because I would tap on a link for example and it would select one about a centimetre below it.
I've got to sent it back to 3uk for replacement.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
can I now flash your kernel or not ?

gamal001 said:
can I now flash your kernel or not ?
Click to expand...
Click to collapse
Yes, I have put all touch screen stuff back to stock, there is just the audio fixes in there.
Sent from my Nexus 7 using Tapatalk

I see from goo that 150 people have downloaded the kernel.
Any feedback?
Sent from my Nexus 7 using Tapatalk