Develop Bugs

Can someone post .config file off your e4gt?

I am almost there so close and compiled a new kernel but stuck because the kernel won't boot. I forgot to pull the .config file off my phone before compiling, can anyone post their .config file?

How do we get access to it? I'll grab mine for you.

zedomax said:
I am almost there so close and compiled a new kernel but stuck because the kernel won't boot. I forgot to pull the .config file off my phone before compiling, can anyone post their .config file?
Click to expand...
Click to collapse
I'd be happy to... but I'm pretty new to all this. Where do I find it?

zcat /proc/config.gz >> config.txt
Sent from my sprint galaxy s2

thanks, if you can set your phone to USB debugging, Settings->Applications->Development
Then do this on adb:
adb pull /proc/config.gz
You can download adb here:
http://downloadandroidrom.com/file/sdk/adb.zip
and you need samsung kies installed:
http://www.samsung.com/ca/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
then post the config.gz here, thanks, my phone is bricked until then!

adb pull /proc/config.gz
remote object '/proc/config.gz' does not exist
?

odub303 said:
adb pull /proc/config.gz
remote object '/proc/config.gz' does not exist
?
Click to expand...
Click to collapse
ok, i think its in a different place, someone know where it is on the Epic 4g touch???

zedomax said:
ok, i think its in a different place, someone know where it is on the Epic 4g touch???
Click to expand...
Click to collapse
I can't locate that file anywhere on the device. Would it be called anything else on this device for whatever reason?

Damn guys, we need to help him find that .config file...I am digging around as well
Sent from my SPH-D710 using xda premium

man I haven't used ADB in so long... all the devs make it to easy to not learn the real way to do $hit!

find / -name config.gz sorry I'm busy or I'd check lol, there's always the possibility they didn't build it with that, isnt there a defconfig in the source
Sent from my sprint galaxy s2

File must be called something else as i can't find it.

bbedward said:
find / -name config.gz sorry I'm busy or I'd check lol, there's always the possibility they didn't build it with that, isnt there a defconfig in the source
Sent from my sprint galaxy s2
Click to expand...
Click to collapse
Right, see if you can find a file with defconfig in it.
or maybe something like c1_rev05_na_spr_defconfig
Just a hunch.

There's a /system/bin/ifconfig
Edit: nm thats network configuration
Sent from my SPH-D710 using xda premium

Screenshot of list of files with "config" in the name

config.gz is an optional addition to the kernel build looks like samsung left it out.
Check arch/arm/configs in the kernel source theres probably a defconfig in there
Sent from my sprint galaxy s2

bbedward said:
config.gz is an optional addition to the kernel build looks like samsung left it out.
Check arch/arm/configs in the kernel source theres probably a defconfig in there
Sent from my sprint galaxy s2
Click to expand...
Click to collapse
Well I have the defconfig, just not booting when I compile the kernel for some reason, thinking the one off a phone might be different from sources (and maybe make it work?)

zedomax said:
Well I have the defconfig, just not booting when I compile the kernel for some reason, thinking the one off a phone might be different from sources (and maybe make it work?)
Click to expand...
Click to collapse
Well the model number on mine is definitely SPH-D710, so unless someone at Samsung uploaded the wrong files, that should be it.
What's the high-level overview of what you're doing to build it? Following the instructions in the source download to build the kernel and then uploading it with odin to the phone?

timdorr said:
Well the model number on mine is definitely SPH-D710, so unless someone at Samsung uploaded the wrong files, that should be it.
What's the high-level overview of what you're doing to build it? Following the instructions in the source download to build the kernel and then uploading it with odin to the phone?
Click to expand...
Click to collapse
Yes, exactly, I've done exactly as samsung source files said, not working, I think something wrong with the released files otherwise i would have a working kernel by now, might be the config file.

He's BAAACK!!!
Nice ...Good to see your back at it!!! I take it u got ur NJew Phone already!!!??

Hint: AOSP 4.1.1 source and Toro not showing as a target under 'lunch'

In case anyone is having trouble finding toro as a device target when trying to build from the list of targets from the 'lunch' command... Toro didn't show up in the list but I was able to manually specify it rather than selecting a numeric option.
Devs probably know that works, but amateurs like myself might benefit from that tidbit. Jellybean seems to be building OK for me now.
EDIT: I was asked what I did, more specifically, so I'll put that here in op:
Rather than enter a numeric choice, I entered 'full_toro-userdebug'. Apparently this was a valid response and the build proceeded.

Mind explaining how you manually selected it?

keith.mcintyre26 said:
Mind explaining how you manually selected it?
Click to expand...
Click to collapse
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.

question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?

spunks3 said:
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
Click to expand...
Click to collapse
It's not as 'polished'. There are no gapps, the dictionary is not complete (need a version from a factory image/rom), there are extra keyboards (Japanese?), maybe a couple other oddities as compared to a stock ROM. It will certainly be more capable that porting a gsm rom to toro, that's for sure .

mmuzzy said:
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
Click to expand...
Click to collapse
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium

keith.mcintyre26 said:
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You're very welcome. Happy flashing.

I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2

phydo said:
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o

mmuzzy said:
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
Click to expand...
Click to collapse
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2

phydo said:
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was actually trying to pull it before Google was finished so it hasn't been that long.

Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?

anton2009 said:
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
Click to expand...
Click to collapse
Lol!
Sent from my Galaxy Nexus using Tapatalk 2

phydo said:
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this

Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?

cdrshm said:
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
Click to expand...
Click to collapse
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!

CPCookieMan said:
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
Click to expand...
Click to collapse
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.

i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
mwalt2 said:
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
Click to expand...
Click to collapse

cdrshm said:
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
Click to expand...
Click to collapse
For future reference, what he's referring to is the extract-files.sh script included in the CM source. If you cannot find the proprietary binaries for a certain device you wanna build for, plug in the phone via usb, cd to the directory with the script and execute the command.

anton2009 said:
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Click to expand...
Click to collapse
I also got version 4.0.9.99.999.9999.99999 when I synced to the master branch. Thanks for mentioning the workaround to sync with 4.1.1_r1 .
Did you figure out if it's a problem to sync 4.1.1 into a directory that's already synced with master (4.0.9.99...)?
--------------------------------
Update: I think I can answer this question based on JBQ's response:
https://groups.google.com/d/msg/android-building/rtH5ZbJC7qU/-N1lr9MqexYJ
"You can also switch in place: just run "repo init -b <new_manifest_branch>; repo sync" in your existing client."
Sounds like syncing to a new branch in the same working directory should work just fine.

[Q] Instructions for Compiling Source

I can't figure out what this step means in the LG open source readme:
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
Click to expand...
Click to collapse
Every search just brings me to the same instruction set so it's probably something obvious I'm missing....

Rocket_Science said:
I can't figure out what this step means in the LG open source readme:
Every search just brings me to the same instruction set so it's probably something obvious I'm missing....
Click to expand...
Click to collapse
Only thing worth compiling from lg source is kernel. The rest is fairly useless.
Sent from my LG-LS970 using xda app-developers app

[Q] Howto add a file from another ROM the right way on GitHub

I want to pull a single file over from CM's repo on GitHub to be added to another ROM that is also hosted on GitHub. What is the best way to go about this? To be specific, the file I want to add is android_device_samsung_toro / overlay / frameworks / base / core / res / res / xml / eri.xml. My plan is to fork the ROM that does not have this file, add it in the way that someone suggests, then issue a pull request to the ROM I forked... that is unless there is a better way. Thanks!

With all the devs on XDA, surely someone can answer this...
Sent from my Galaxy Nexus using Tapatalk 4

in your build environment you should be able to just cherry-pick that commit

Pirateghost said:
in your build environment you should be able to just cherry-pick that commit
Click to expand...
Click to collapse
Brilliant! I knew there was a clean way to do it. I will do some Googling, but do you happen to have a suggestion for learning how to do cherry picks?
Sent from my Galaxy Nexus using Tapatalk 4

https://www.kernel.org/pub//software/scm/git/docs/git-cherry-pick.html
http://gitready.com/intermediate/2009/03/04/pick-out-individual-commits.html
There is also a good guide here on XDA that explains a lot of this for you, specifically for building from source.
http://forum.xda-developers.com/showthread.php?t=1942338

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)