Develop Bugs

{Kernel-Source} GoDmOdE-2.6.29-GSM-HERO

i have pushed the board files to my github to compile a fully working kernel for the GSM Hero. i dont own the device, but Behnaam has been working with me testing and such. anyhow everything works. the link to my source can be found below:
GoDmOdE-KeRnEl-SoUrCe
anyhow enjoy i do this for the community and ask for nothing but in return. Devs have at it!!!

Behnaam already beat you to the punch, link.

gu1dry said:
Behnaam already beat you to the punch, link.
Click to expand...
Click to collapse
i seen but i can update this one plus i guess i forgot to add two files . btw they are there now and it will compile for sure. (i just did it) enjoy

will it say no more huge battery drain ?

Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
EDIT: Had a lapse and forgot to compile a new wlan module... will reupload after school today
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone

zjr8 said:
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
Click to expand...
Click to collapse
Here ya go mate
http://www.megaupload.com/?d=724NZ7Q1

Are the video drivers included?

MerXury13 said:
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn

Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)

Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Click to expand...
Click to collapse
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk

MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform

I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
It's too early for me^^ sorry

dipje said:
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.

MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
Again... getting boring

Can someone please compile this one with overclock patch?I have no idea how to compile from source else I would do it

l0st.prophet said:
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
Click to expand...
Click to collapse
Hence it got video drivers

Can anyone point me in the direction of a good write up on how to build a boot.img from this git repo please?im using ubuntu 10.4

so can we use this kernel on the vanilla roms?

anon2122 said:
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Click to expand...
Click to collapse
Do you have the latest commit? I believe initially there were some missing files. I know when I grabbed the source the first time i had wlan drive compile issues

I applied this to both cronos rom and to superhero rom and both got really sluggish after installing it (I used the boot.img posted among the first posts).

Android Dev. How-To Guide: Compiling the Android/Linux kernel for the Epic Touch 4G

Android Development How-To: Compiling the Android/Linux kernel for the Epic Touch 4G.
NOW INCLUDES ROOT!!!
Introduction: This guide is meant for people who want to get started with android development and don't know where to start. This thread can also be used as a reference place for android development on the et4g. This guide well first be on compiling the android kernel and flashing it to your phone and, I well update it on a regular basis for more complex mods and such to get you familiar with the android platform. If at anytime anyone would like to add more to this, pm me with what you would like to add or fix. Android is an open-source wonderland and I feel like more people should experience the fun of android development. Just remember I am not responsible if you do something stupid and break your phone!
First, we are going to get familiar with the android kernel by compiling a stock build and flashing it with Odin to your et4g.
What you need to download to compile the kernel:
Samsung open-source kernel and platform files. Available at: Samsung Open Source
Type in: Sph-d710 in the search bar in the link and download latest source.
initramfs files (More on this later) (includes cwm, busy box, and of course root! Thanks to chris41g for his help.) Files available at: Initramfs Files
Tool chain for compiling: Available at: Arm-toolchain
Preferably Ubuntu or another Distro. Of Linux running on a partition or Virtual machine.
Step 1: Were going to unzip the source you got from Samsung and take a short look around.
unzip the source and unzip the file that says, “SPH-D710_GB_Kernel.tar.gz” and, open it up. You are now looking at the kernel source for the Epic touch 4g! Okay I well not go over to much whats is here but, I well add a more in depth look in the kernel soon.
Scroll to the bottom of the source and you should see a document that says, "makefile". We are just going to add a name for your stock compile of the kernel, to make it a little more special. Open it and go to where it says Extra version and add your last name ,just make it all lower case letters or it wont compile correctly. When you flash it to your phone, the about phone panel in setting well say: Kernel version: 2.6 [last name you chose] now.
Step 2: Lets get started!
Open terminal in Linux and change your directory to the kernel. You do this by putting,
“cd” and then typing where your kernel source is then hit enter. My terminal looked like this:
cd /home/shane/Desktop/SPH-D710_GB_Kernel
Click to expand...
Click to collapse
Step 3: Tell terminal where your tool chains you downloaded are located.
The kernel is compiled using a tool chain, and the terminal needs to know where the tool chain is to compile. (The tool chain is the folder called “arm-2009q3” )Start by typing this in the terminal:
export CROSS_COMPILE=
Click to expand...
Click to collapse
Then after that put where your tool chain is located. Also when you are entering where it is at, you need to put a “/bin/arm-none-eabi-” at the end of the directory. This shows the terminal that the compiling tools are under the folder bin and starts with arm-none-eabi- and the android compilation adds the last word for the compiler program it needs. (you can see this if you go into the bin folder under the “arm-2009q3 folder.) For adding the tool chain I entered this:
export CROSS_COMPILE=/home/shane/Desktop/arm-2009q3/bin/arm-none-eabi-
Click to expand...
Click to collapse
Then hit enter.
Step 4: Clean the kernel, enter configuration files and make the modules.
Enter this command:
sudo make clean
Click to expand...
Click to collapse
Then enter password and hit enter.
Then it well say something like:
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
Click to expand...
Click to collapse
IGNORE THIS! It is just a fragment in a configuration file that says the toolchain is not in the default location. But, we changed the tool chain location in step 3 so it well compile correctly.
This cleans up and organizes the kernel for compilation.
Now enter this command in terminal:
make c1_rev05_na_spr_defconfig
Click to expand...
Click to collapse
This is the configuration files for the epic touch 4g and well compile the kernel based off what is in these files.
Now were going to compile all the modules so wifi,vibration... work.
Enter this in terminal:
make modules
Click to expand...
Click to collapse
Step 5: Moving the newly compiled modules to the initramfs/lib/modules folder.
We are now going to move the modules from the newly compiled modules to the initramfs files. So that wifi and vibration well be working in our kernel.
*Initramfs files are the root filesystem of the kernel and does processes the kernel can't do itself while its booting.
You can do this by terminal or by hand. We are just moving the modules to the initramfs to be used when compiling the kernel.
You can type this into terminal (Where it says “Path to initramfs” you need to replace with your own path to the initramfs folder + /lib/modules) :
cp drivers/samsung/j4fs/j4fs.ko Path to initramfs/lib/modules
cp drivers/scsi/scsi_wait_scan.ko Path to initramfs/lib/modules
cp drivers/bluetooth/bthid/bthid.ko Path to initramfs/lib/modules
cp drivers/net/wireless/bcm4330/dhd.ko Path to initramfs/lib/modules
cp drivers/samsung/vibetonz/vibrator.ko Path to initramfs/lib/modules
cp drivers/staging/westbridge/astoria/switch/cyasswitch.ko Path to initramfs/lib/modules
Click to expand...
Click to collapse
This copies the new modules out of the kernel source and puts them in the initramfs/lib/modules folder to be used later.
Now once you enter that press enter.
Step 7: Compiling the android kernel with initramfs.
Type this in terminal:
make -j5 CONFIG_INITRAMFS_SOURCE=Path to initramfs file
Click to expand...
Click to collapse
*Remember to replace the “path to initramfs file” with the path to the initramfs file.
Okay this well take anywhere from 5-15 mins. to compile depending on your system.
Step 8: Were done compiling, lets make something flashable for Odin!
Just type in terminal:
cd arch/arm/boot/
Click to expand...
Click to collapse
Then type:
tar cvf MyKernel.tar zImage
Click to expand...
Click to collapse
This well zip up the zimage (the kernel) you just compiled to something flashable in odin.
If you open up the kernel source file and go to arch/arm/boot you well see the zimage you compiled and, the Mykernel.tar file for Odin. Double check and right click on the zimage and make sure it is around 5-6 MB before flashing.
Step 9: Flashing to your phone.
Go to a windows computer and download Odin.(if you have rooted your phone using zedomax's method you should have it installed already)
Okay now open it up and place the Mykernel.tar file in the PDA section of Odin. Now download the drivers for your phone if you haven't.(I assume you already have.) Then put your phone in download mode (hold volume down button and power button on start up and push volume up button when the warning pops up) Now plug your phone into the computer and make sure “auto-reboot” is the only box checked in Odin. Hit start and your phone well be flashed with a kernel you compiled yourself! If you did this right your phone should start up. If it is stuck in a boot loop, immediately put back in download mode and flash to stock. Link available here to stock files:
http://forum.xda-developers.com/showthread.php?t=1409634
and, try to figure out what you did wrong while compiling and try again!
Good job you have finished!
Step 10: The future and your new phone!
I would like to include more android kernel mods and stuff in the future but, wanted to get this out there to get people familiar with the android compiling process. I want this guide to be something people reference as they start to develop, by using the methods here along with kernel and U.I mods on the platform being implemented in the future. My ultimate goal is to at least know I helped at least one person get into android development so, if I helped you please leave a reply or say thanks. If anyone has ideas to add to the post, please pm me.
Have fun developing!

I'll take this...

and this...

One more...

Awesome!!!! I have been patiently awaiting this. THANK YOU SOOO MUCH!!!!
Sent from my SPH-D710 using xda premium

Thank you! Definitely will be referring to this during my free time. Can't wait to see what else gets added
Sent from my SPH-D710 using xda premium

Awesome!! tyvm!!

Wow... How awesome is this? I have been looking for something like this for a long time. I will be watching for updates. Thank you very much.

all u need now is a video tutorial

My man!!! Thank you for this!!
Sent from this phone

Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?

dtm_stretch said:
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
Click to expand...
Click to collapse
It all depends if you wanted to flash a already made custom recovery (cwm) then we would just haved to root the kernel then build and flash the recovery. If you were to make a fully custom recovery with custom functions made by you then it could get a little more tricky but, I am guessing you just mean flashing a custom recovery like cwm. Which is not terribly hard but, not neccesary easy eather depending on how hard it is to obtain root.
I might update the guide in the future. Showing how to do something like this but, I have a few more ideas for the guide before I include this.

You nailed it, I was curious about adding root and CWM(or a variation of it). I am more than content with figuring out what you have posted so far.

Thank you so much. This is absolutely great!
Sent from my SPH-D710 using XDA App

Awesome guide. Thank u so much for this. Hope for many more.
Sent from my Nexus S 4G using xda premium

Very awesome thanks for the share!!
Sent from my SPH-D710 using XDA App

Great Guide!
Very informative and well put, Thank You.

thank you very much for this! Gives me something new to try out. Thanks again!!!
Sent from my SPH-D710 using Tapatalk

Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!

obelisk79 said:
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
Click to expand...
Click to collapse
I hope it helps!

Need help troubleshooting random reboots (kmsg and logcat provided)

Hi all, I would appreciate if someone can help me troubleshoot my logs to determine the cause for random reboots.
kmsg: http://www.mediafire.com/view/?pqrmk14laug8dq9
logcat: http://www.mediafire.com/view/?sk9nd4tye0b30ib
logcat (long format): http://www.mediafire.com/view/?bsdhnpah6as7mzp

CrazyRussianXDA said:
Hi all, I would appreciate if someone can help me troubleshoot my logs to determine the cause for random reboots.
Click to expand...
Click to collapse
What ROM/Kernel are you using? Have you customzied any values?

Running Codename Android 3.8 no customization except AOKP weather icons and the most recent Faux's kernel 21 but reboots happened on stock kernel as well. I installed the newest kernel to troubleshoot but reboots still occurring

can you please pastebin the logs?? mediafire sucks

I dont have an account there. Is there any other way I could get the logs to you?

Huh i dont think there's a need to register on pastebin.
Sent from my i9250

Well, I tried posting but got "You have exceeded the maximum file size of 500 kilobytes per paste" error when tried posting.
So, I trimmed the log to fit into requirements:
kmsg: http://pastebin.com/psNDbRAj
logcat: http://pastebin.com/fRjv0EmP
logat (long format, just in case time and date of events is needed): http://pastebin.com/sJGxrdmA

bk201doesntexist said:
Huh i dont think there's a need to register on pastebin.
Sent from my i9250
Click to expand...
Click to collapse
Posted to patebin.

Its a kernel panic alright
[21400.926086] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP
[21400.926116] Modules linked in:
[21400.926116] CPU: 0 Tainted: G W (3.0.45-tuna-faux123-jb-022+ #170)
[21400.926147] PC is at omap_rev+0x4/0x1c (... bunch of memory adresses)
which i believe to be human readable, needs a trace in the source and recompiled. Push this kmsg to faux?
Sent from my i9250

bk201doesntexist said:
Its a kernel panic alright
[21400.926086] Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP
[21400.926116] Modules linked in:
[21400.926116] CPU: 0 Tainted: G W (3.0.45-tuna-faux123-jb-022+ #170)
[21400.926147] PC is at omap_rev+0x4/0x1c (... bunch of memory adresses)
which i believe to be human readable, needs a trace in the source and recompiled. Push this kmsg to faux?
Sent from my i9250
Click to expand...
Click to collapse
How can I push this to Faux?
And THANK you for helping.

CrazyRussianXDA said:
How can I push this to Faux?
And THANK you for helping.
Click to expand...
Click to collapse
provide the pastebin you linked here to him (faux123), the dev of lean kernel. through one of his threads, pm wouldn't be the appropriate means to do it.

Compile of CM12.1 error

Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####

Same error here. Ask if they solved it.
http://forum.xda-developers.com/galaxy-s5/help/kltechnduos-compile-error-t3134865

Unfortunatelly, still no reply on linked thread
Sent from my HTC One X using XDA Free mobile app

I have the same error, see if someone can help us

Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?

teemo said:
Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?
Click to expand...
Click to collapse
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app

milda25 said:
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?

teemo said:
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?
Click to expand...
Click to collapse
All errors is in my initial post. First error is error 1. Don't know if this errors depends one on second ...
Sent from my HTC One X using XDA Free mobile app

milda25 said:
Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####
Click to expand...
Click to collapse
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!

Are you doing forced sync?
These days we sometimes need to
repo sync --forced-sync

@bigtor_gj, @teemo Thanks for the tips, will try ASAP and send a feedback.
Sent from my HTC One X using XDA Free mobile app

biktor_gj said:
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!
Click to expand...
Click to collapse
Code:
target Java: org.cyanogenmod.platform.sdk (/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /home/rafitcu/Android/Cm12.1/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (02:02:04 (hh:mm:ss)) ####
No solved for me

Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.

Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app

da_reeseboy said:
Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.
Click to expand...
Click to collapse
milda25 said:
Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
You have given me an idea, I am testing a solution and so far it seems to work, if the compilation ends successfully, the share here.

Unfortunately, git reset --hard and repo sync --force-sync doesn't solved the problem. Still same error on same position of building

What java version is everyone using? Run java -version and put the results here.
Code:
[email protected]:~$ java -version
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

I switched from OpenJDK to Oracle's JDK... no difference. I just found the vm I started building on in July, untouched with no updates done. I will resync and try a build on it to see if its an update to one of the packages installed for building that is causing the issue.
...This will take some time...

http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?

teemo said:
http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?
Click to expand...
Click to collapse
Thank you for the responses - those are both along the lines of the issue. The first post never mentioned what he deleted tho. The second one is definitely related as I can make it further in my build before failing when I revert that commit, but it still fails.
As few posts as there are online about having this issue, I don't think a commit is directly causing it, otherwise there wouldn't be any successful builds from anyone for the last couple weeks. I think its related to a security update that a few of us did, and most of the devs don't update if its not broken lol. I should know this afternoon...
Edit: I mean its an incompatibility between the changes to cmsdk and some security update I did.

Kernel android-msm-marlin-3.18-pie-qpr2 build failed

Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.

me too

Adlismon said:
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
Click to expand...
Click to collapse
ucantseeme said:
me too
Click to expand...
Click to collapse
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.

sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.

Adlismon said:
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Click to expand...
Click to collapse
The files are all outputted where they are meant to be (/out/android.../dist) already, and the image.lz4 is the normal output. If yours outputs elsewhere I would sync, delete the buildinfo line and rebuild in a new directory and see what happens.

sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
thank you, thank you
I solved it