Database Develop

compiling error kernel

hi guys....i've downloaded the last kernel sources of franciscofranco 2.35.10 kernel....i've added the sippolo's workaround and then increase the HZ value of the kernel(set at 500) for my custom rom.....after i've done
Code:
make thunderg-perf_defconfig
make zImage -j4
it stuck at this error
Code:
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_ioctl_down’:
drivers/input/touchscreen/mcs6000_ts.c:430:6: error: implicit declaration of function ‘gpio_configure’
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_probe’:
drivers/input/touchscreen/mcs6000_ts.c:733:25: warning: unused variable ‘hw_ver’
drivers/input/touchscreen/mcs6000_ts.c:733:17: warning: unused variable ‘fw_ver’
make[3]: *** [drivers/input/touchscreen/mcs6000_ts.o] Errore 1
i don't understand why......i think it is a lib problem.....but seems that all libraries are imported!!!can anyone help me??? thnx in advice

Which toolchain?
Sent from my LG-P500 using XDA Premium App

lupohirp said:
hi guys....i've downloaded the last kernel sources of franciscofranco 2.35.10 kernel....i've added the sippolo's workaround and then increase the HZ value of the kernel(set at 500) for my custom rom.....after i've done
Code:
make thunderg-perf_defconfig
make zImage -j4
it stuck at this error
Code:
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_ioctl_down’:
drivers/input/touchscreen/mcs6000_ts.c:430:6: error: implicit declaration of function ‘gpio_configure’
drivers/input/touchscreen/mcs6000_ts.c: In function ‘mcs6000_ts_probe’:
drivers/input/touchscreen/mcs6000_ts.c:733:25: warning: unused variable ‘hw_ver’
drivers/input/touchscreen/mcs6000_ts.c:733:17: warning: unused variable ‘fw_ver’
make[3]: *** [drivers/input/touchscreen/mcs6000_ts.o] Errore 1
i don't understand why......i think it is a lib problem.....but seems that all libraries are imported!!!can anyone help me??? thnx in advice
Click to expand...
Click to collapse
.35 kernel have new GPIO library, you should code sippolo's workaround into new driver, do not replace whole file.

mik_os said:
.35 kernel have new GPIO library, you should code sippolo's workaround into new driver, do not replace whole file.
Click to expand...
Click to collapse
Aaaaa i don't know that thanks now it works ;-) now the next step i'm ttying to port the acer liquid multitouch fix thanks mik
Sent from my LG-P500 using XDA App

If you can fix also the tethering and the random bugs

use pdanet for tethering

now i'm stucking at this error...((
arch/arm/mm/built-in.o: In function `__flush_icache_all':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/arch/arm/include/asm/cacheflush.h:402: undefined reference to `swapper_space'
arch/arm/mm/built-in.o: In function `____atomic_set_bit':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/arch/arm/include/asm/bitops.h:46: undefined reference to `swapper_space'
arch/arm/mm/built-in.o: In function `spin_unlock':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/include/linux/spinlock.h:324: undefined reference to `swapper_space'
mm/built-in.o: In function `sync_page':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/mm/filemap.c:190: undefined reference to `swapper_space'
mm/built-in.o: In function `set_page_dirty':
/home/pasquale/Scrivania/Franco.Kernel/2.6.35/mm/page-writeback.c:1181: undefined reference to `swapper_space'
mm/built-in.o:/home/pasquale/Scrivania/Franco.Kernel/2.6.35/mm/page-writeback.c:1335: more undefined references to `swapper_space' follow
make: *** [.tmp_vmlinux1] Errore 1
Click to expand...
Click to collapse
seems another time a library problem... anyone can help me??

lupohirp said:
now i'm stucking at this error...((
seems another time a library problem... anyone can help me??
Click to expand...
Click to collapse
What have you patched?
It just says it's missing the swapper_space function header, it's not defined.

franciscofranco said:
What have you patched?
Click to expand...
Click to collapse
nothing franco....i've only added sippolo's workaround for base to port acer liquid multitouch fix and set kernel to 500hz i've worked only on mcs6000_ts......but it stuck at this error i don't know why!!! i think it is a library problem....something that is missing...but i don't know what are the libraries that i must install if it is this the problem!(

You downloaded the latest sources? Because I haven't compiled it, I just merged the patches, I might have forgot to apply something. In this case it says it misses the swapper_space reference.
http://lxr.free-electrons.com/source/mm/swap_state.c#L40
http://lxr.free-electrons.com/source/include/linux/mm.h#L771
http://lxr.free-electrons.com/source/include/linux/swap.h#L319
Add the swapper_space code to those files and compile again.

franciscofranco said:
You downloaded the latest sources? Because I haven't compiled it, I just merged the patches, I might have forgot to apply something. In this case it says it misses the swapper_space reference.
http://lxr.free-electrons.com/source/mm/swap_state.c#L40
http://lxr.free-electrons.com/source/include/linux/mm.h#L771
http://lxr.free-electrons.com/source/include/linux/swap.h#L319
Add the swapper_space code to those files and compile again.
Click to expand...
Click to collapse
yes franco i've downloaded latest sources! thanks now i'm going to add it and then try!

franco the swapper_space code that you posted is already there in the three files((

I dunno, I have to leave now, I'll look at it later.

I'm sorry to disappoint you, but there ain't a problem with the kernel, I just compiled it without any modification, just like it is in the sources and it compiles fine. Try to make clean and make distclean, then compile again.

franciscofranco said:
I'm sorry to disappoint you, but there ain't a problem with the kernel, I just compiled it without any modification, just like it is in the sources and it compiles fine. Try to make clean and make distclean, then compile again.
Click to expand...
Click to collapse
yeah franco i know.....i think it is a libraries problem on my linux distro.....but i have installe all the binutils and the header files yesterday also i have tried a dirty hack i tried to set CONFIG_SWAP=n in the thunderg_perf_defconfig configuration file....compiled succesfully but the phone doesn't started ...thanks anyway franco!

Cyanogenmod 7 (Think Tank, in progress)

Hello All,
So I´m all sorts of new at developing for android, and I wanted to open up my thoughts and efforts to the community. I am trying to port CM 7, (eventually 9), and am using the CM Compiler that was developed by LithidCM. I´ve gotten everything up and running, now I just need to figure out how to set up the proper files from the Holiday itself. As I said, this is a work in progress, and any suggestions are very helpful. Right now, the stumbling block is setting up a Holiday/Raider/Vivid repo with the necessary compilation files.
Lets get cooking!
CMCompiler (All credit goes to Lithid CM) http://forum.xda-developers.com/showthread.php?t=1415661

+1 i would love to see cm7 or 9 on my vivid

That CMCompiler wont work for the Vivid
Sent from my SGH-T989 using Tapatalk

Not until there is either a CM repo for the Vivid or I can set up the correct files locally, then I can modify the script for it to look there, rather than the CM repo. Iḿ looking for ways to make it WORK, so anything to that end is appreciated. Either that or work on another method if it looks more promising. I have time, a machine, a device, some knowledge, and the desire, I just want to get together with some other people who can contribute a bit on the knowledge end to HELP get this up and running.

XAviierG said:
That CMCompiler wont work for the Vivid
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
That was very insightful.... I'm sure the OP is very thankful for all your help.

I'm already taking care of this
If you're into it, you can download my repo for CM9 here: https://github.com/thecubed/android_device_htc_holiday
I make no promises on timeline, but I do expect to have a teaser video with a few things working at least here in a day or so.

thecubed said:
I'm already taking care of this
If you're into it, you can download my repo for CM9 here: https://github.com/thecubed/android_device_htc_holiday
I make no promises on timeline, but I do expect to have a teaser video with a few things working at least here in a day or so.
Click to expand...
Click to collapse
if you guys want i got a port booting with signal for the amaze almost same device

I too would love to see both CM7 and 9 on the Vivid, however from what i gather CMCompiler is not really going to be the way at it.
I follow alot of Team Haxsung and CM people and they all believe it to be not the best way to help the CM community, rather a way to re brand and take credit.
Further, CMCompiler requires there being a branch, which means that nightlies will be compiled quickly by build bots, if build bots are down or you want to make a nightly KANG you can install the dependencies via the CM wiki and build yourself, which might actually allow you to learn how to build and modify the source rather then having an application spit it out for you
Drew

thecubed said:
I'm already taking care of this
If you're into it, you can download my repo for CM9 here: https://github.com/thecubed/android_device_htc_holiday
I make no promises on timeline, but I do expect to have a teaser video with a few things working at least here in a day or so.
Click to expand...
Click to collapse
AH! I have been using your repo as my source on CMC, but it fails each time because I´m missing some files. which files, well, that´s the step I´m at now. Im stoked your working on this. I´d like to learn how to do this on my own as well, then I´d be happy to put together a step by step from scratch for building from a fresh install of Ubuntu, I think it´s needed.

drewdatrip said:
I too would love to see both CM7 and 9 on the Vivid, however from what i gather CMCompiler is not really going to be the way at it.
I follow alot of Team Haxsung and CM people and they all believe it to be not the best way to help the CM community, rather a way to re brand and take credit.
Further, CMCompiler requires there being a branch, which means that nightlies will be compiled quickly by build bots, if build bots are down or you want to make a nightly KANG you can install the dependencies via the CM wiki and build yourself, which might actually allow you to learn how to build and modify the source rather then having an application spit it out for you
Drew
Click to expand...
Click to collapse
And if you´ve read anything I have written (and what others have added) you would see that the purpose of this post is LEARNING. I´m not a linux guy, but I´m quickly figuring it out, not much help to individuals such as yourself who choose to distract and detract rather than assist and contribute, or at least keep your finger off the ¨submit¨ button.
I posted this thread because there is no working version of CM7 for this device. Lets drop the negativity/whatever and put our efforts and keystrokes to getting this booting.

Some of the amaze builds i have you should just have to have someone make a kernel and they will work
http://dl.dropbox.com/u/40288576/full_ruby-ota-eng.xboarder56_12-24-11.zip (ics 4.0.3 amaze should be easy to port to vivid almost same phone)
http://dl.dropbox.com/u/46431819/Amaze/update-cm-7.1.0-SelfKANG1-Amaze-4g.zip

MCreane said:
And if you´ve read anything I have written (and what others have added) you would see that the purpose of this post is LEARNING. I´m not a linux guy, but I´m quickly figuring it out, not much help to individuals such as yourself who choose to distract and detract rather than assist and contribute, or at least keep your finger off the ¨submit¨ button.
I posted this thread because there is no working version of CM7 for this device. Lets drop the negativity/whatever and put our efforts and keystrokes to getting this booting.
Click to expand...
Click to collapse
Ok we're just letting you know that the CMCompiler will not help. But try this.
http://forum.xda-developers.com/showthread.php?t=667298

My comment had no attitude as you speak of, like XAviierG i was just letting you know that if your intention is LEARNING the CMcompiler does not help with the process. Its an application that runs in a terminal window and you press numbers on screen to pull from the repos, again thats not learning and it wont help get the Vivid working any sooner.
I appropriate your eagerness to learn Linux, i am still learning alot aswell, and i too was excited when i read about the CMcompling application, however after reading about it and the stance of the dev teams i realized that its not the best for me and people looking to learn
Drew

thecubed said:
I'm already taking care of this
If you're into it, you can download my repo for CM9 here: https://github.com/thecubed/android_device_htc_holiday
I make no promises on timeline, but I do expect to have a teaser video with a few things working at least here in a day or so.
Click to expand...
Click to collapse
This just made my day
Sent from my HTC PH39100 using Tapatalk

CMC got me motivated to figure out how to get this working. Yes it´s a shortcut, no it doesn´t help anyone who can´t flash through rommanager already, and thus not us, right now. However, what gets people learning is a good thing, as far as I am concerned. I know far more about Linux now than I ever would have if it had worked beautifully from the start, including building everything through other means that it looks to do through invisible scripting.
As I said, I´m done talking about this.
Back on topic.
I am working on building a fresh CM7 Kernel through
Code:
[email protected]:~/android/kernel/cm-kernel$ adb pull /proc/config.gz /home/michaelcreane/android/kernel/cm-kernel/config.gz
cat config.gz | gunzip > .config
All goes well
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER oldconfig
make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
No problems.
But then
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
and I run into this:
Code:
[email protected]:~/android/kernel/cm-kernel$ make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
scripts/kconfig/conf --silentoldconfig Kconfig
#
# configuration written to .config
#
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CC scripts/mod/empty.o
cc1: error: unrecognized command line option ‘-mlittle-endian’
cc1: error: unrecognized command line option ‘-mapcs’
cc1: error: unrecognized command line option ‘-mno-sched-prolog’
cc1: error: unrecognized command line option ‘-mno-thumb-interwork’
scripts/mod/empty.c:1:0: error: unknown ABI (aapcs-linux) for -mabi= switch
scripts/mod/empty.c:1:0: error: bad value (armv5t) for -march= switch
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!
I just accepted all defaults in the RCU implementation, and I´m guessing that´s where the errors are starting. I got the same error when I ran
Code:
scripts/extract-ikconfig boot.img > .config
rather than extracting the .gz file from my device. Any ideas?

@MCreane and the cubed
I'm glad you guys are working on this. Very exited to see what you guys come up with. I also think it would be great to have a guide.
Sent from my HTC PH39100 using XDA App

I was able to build the Holiday kernel successfully after pulling config.gz and doing this:
Code:
make oldconfig
export CROSS_COMPILE=<path to android source>/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
make ARCH=arm -j2

michealw31 said:
I was able to build the Holiday kernel successfully after pulling config.gz and doing this:
Code:
make oldconfig
export CROSS_COMPILE=<path to android source>/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
make ARCH=arm -j2
Click to expand...
Click to collapse
Awesome, ill give that a shot after work. Much appreciated
Sent from my HTC Raider X710e using xda premium

Tease: we have a successful booting CM9 from source
Current problem: the kernel we're using (stock from source) is missing the proper USB stack for ICS, as well as GSL changes, so we either have to fork toastcfh's kernel, or fix tiamat's kernel which currently doesn't boot.
However, we were able to get it to boot with a stock kernel built from source. Gfx are skewed, but touchscreen worked, and the colors were right-- so we're on to something at least.
Anyway, I'll be pushing what I have to my github as "holidayics" instead of "holiday" until it's ready for primetime. (@ http://github.com/thecubed )

thecubed said:
Tease: we have a successful booting CM9 from source
Current problem: the kernel we're using (stock from source) is missing the proper USB stack for ICS, as well as GSL changes, so we either have to fork toastcfh's kernel, or fix tiamat's kernel which currently doesn't boot.
However, we were able to get it to boot with a stock kernel built from source. Gfx are skewed, but touchscreen worked, and the colors were right-- so we're on to something at least.
Anyway, I'll be pushing what I have to my github as "holidayics" instead of "holiday" until it's ready for primetime. (@ http://github.com/thecubed )
Click to expand...
Click to collapse
Good to hear about your progress. I'm willing to help test if you need any help in that department.
Sent from my Transformer TF101 using Tapatalk

[SOLVED] Problem compiling cyanogen mod 7 with subskype tass device

Hello I'm trying to compile cyanogenmod 7 with subskyper tass device to try to mantain this project update in line with the original philosophy: keep it 100% cyanogenmod without any tweaks
When I compile I face two errors that broke my compilation:
1-
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml:95: error: Resource at swap_volume_keys_orientation appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Errore 1
make: *** Eliminazione del file "out/target/common/obj/APPS/framework-res_intermediates/package-export.apk"
make: *** Attesa per i processi non terminati....
This one I commented out the line reguarding swap_volume_keys_orientation in file
device/samsung/tass/overlay/frameworks/base/core/res/res/values/config.xml
but when i continue...
2-
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/AndroidRuntime.o: in function android::gRegJNI:AndroidRuntime.cpp(.data.rel.ro+0x148): error: undefined reference to 'register_android_hardware_fm_fmradio(_JNIEnv*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/tass/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so] Errore 1
make: *** Attesa per i processi non terminati..
Someone faced same problems?
Any ideas?
thanks a lot

Send PM With The Error To Subpsyke

t-r-e said:
Send PM With The Error To Subpsyke
Click to expand...
Click to collapse
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.

mebitek said:
done. I hope he will answer me cause I'm able to sync repos in a couple of hours, so it will be easy to mantain pure cyanogenmod 7 for our sgm.
Click to expand...
Click to collapse
Best Luck Buddy Don't Give Up Early , We Look Forward To See Your Work As We Need To Keep Subpsyke Project Alive

prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld:
Click to expand...
Click to collapse
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.

coolsandie said:
Are you using 32-bit linux system ?
If yes, then I guess 64-bit is necessary to get things compiled properly without errors.
NB: Just sharing info.
Click to expand...
Click to collapse
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation

Now I have a signed zip to flash into my sgm.
It contains subskype cm7.2 tass device configuration and latest cm 7.2 sources update at 31-01-2012.
to check changes:
http://review.cyanogenmod.com/#q,status:open,n,z

It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?

mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
Great news. Glückwunsch (don't know the english word at the moment).
Supercharger would be possibly good. Subpsyke said something to it but i don't rember clearly.
Keep up your work.
Sent from my GT-S5570 using xda premium

mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
No not add anything. It s better. Completely clean
Inviato dal mio GT-S5570 usando Tapatalk

mebitek said:
Thanks for the reply but I think that this kind of error is a missing reference for the function register_android_hardware_fm_fmradio that is called from AndroidRuntime.cpp
32 or 64 bit it is no differnce in compile result. just speed....
However I've checked tass configuration and I see that fm radio is set to BCM2049 chip.
I checkd into frameworks/base/core/jni/ cm source tree directory and I found only fm hardware reference for :
bcm4325
si4708
si4709
wl1271
now I'm trying to compile again setting radio to bcm4325 just to see if something appens...
P.S. should be nice to have some tecnical ideas about the code error not only if the host system is well configured
P.P.S. changed values to bcm4325 let me not face errors no more. Now I'm compiling!!!!
I have checked some github projects and I see that a lot of device as sgm with bcm2049 fm chipset set it to bcm4325. I see that just subskype change that value to bcm2049. Should be nice to have some tip and tricks from him to understand well the point of the situation
Click to expand...
Click to collapse
For the radio, I used my patch to add support for the bcm2xxx devices with proper seeking. It's on gerrit here: http://review.cyanogenmod.com/#change,10358

mebitek said:
It works!!! finally compiled and booting successfully.
Now I'm trying to study the best way to mantain this kind of project (it's first time for me in android dev and I just have an android device by november).
first at all I was thinking to add V6 supercharge by default. what do you think?
Click to expand...
Click to collapse
no no...no v6.
Just vanilla cm7...and thanks for the initiative and ABT!
dont add scripts..but maybe something from cm gerrit if u wish..but then it'll not be vanilla.

[Q] Xperia SP Device Tree/ Proprietary Blobs

Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:

sarkar1990 said:
Hey guys,
I know the dev scene is pretty bleak here. I already had the android 4.3 jellybean source code synced on my laptop, since I was creating builds for my Nexus.
I tried for the SP, but then I realized that there is no device tree present. I found one by Krabappel but it was incomplete (or atleast I think so). It refers to 2 other extract-files.sh, but for the life of me I can't figure out which ones.
I know there are a few devs here, so can one of them help me out here? How to I get the blobs for the phone?
If I get that going, we can start with an AOSP build and then keep adding stuff to it.
Let me know. \
Cheers! :good:
Click to expand...
Click to collapse
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.

the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.

nil1511 said:
the extract-files.sh are in the below repo
"repository": "android_device_sony_common",
"target_path": "device/sony/common"
I have tried to build the recoveryimage but I am getting problem in builting kernel.elf as normally it is in kernel.img
I have tried to both method building kernel and using zImage.
Click to expand...
Click to collapse
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2

eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
Awesome. You can either upload them link me the git if its there

sarkar1990 said:
Did you try to convert the zimage to elf using the build tools?
Here's the link that you may try http://forum.xda-developers.com/showpost.php?p=43356450&postcount=2
Click to expand...
Click to collapse
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails

nil1511 said:
I mean that i tried to make write device files from scratch
as given here
[link]http://wiki.cyanogenmod.org/w/Doc:_porting_intro[/link]
as on method 3 i tried using zImage as kernel as stated there.
but make recoveryimage fails
Click to expand...
Click to collapse
If you want to learn. It would be best to clone the Doomlord git and then read the files and scripts that are present there. This will give you the knowledge you may need to proceed further.
the git for our processor msm8960t is already present on github. Also download the kernel sources and drivers provided by Sony themselves from their developerworld page

sarkar1990 said:
the git for our processor msm8960t is already present on github.
Click to expand...
Click to collapse
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.

eeehaw said:
You mean the kernel sources or the cm / aosp sources ? Can you provide a link.
Click to expand...
Click to collapse
Here is the link
https://github.com/DooMLoRD/android_kernel_sony_msm8960t.git

eeehaw said:
I tried building cm10.1 for the sp, but could not get past the kernel logo. Even the recovery didn't work.
If you want the blobs, I can upload them somewhere. I had extracted them from the current 4.1.2 implementation on the device.
Click to expand...
Click to collapse
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?

I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."

sarkar1990 said:
I am using the device tree: https://github.com/Krabappel2548/android_device_sony_huashan
I added CPU_TARGET_VARIANT according to JB 4.3 requirements. And loaded up the required gits.
But the thing is now I get an error:
Code:
Code:
make: *** No rule to make target `device/sony/huashan/zImage', needed by `out/target/product/huashan/kernel'. Stop.
Could you help me out a bit?
Click to expand...
Click to collapse
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.

eeehaw said:
I did not use krabappel's device files. I had based my stuff on the Xperia T. I'll try this probably tonight.
Click to expand...
Click to collapse
Can you push your device file on github

nil1511 said:
Can you push your device file on github
Click to expand...
Click to collapse
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.

eeehaw said:
I'm behind a very nasty proxy which makes it super hard to push/pull files from github. Instead of pulling i just download the zip archives.
I'll check out ways to push files though.
Click to expand...
Click to collapse
Man, I keep running into the error! Ahh.. I think we need a better device tree.

sarkar1990 said:
Man, I keep running into the error! Ahh.. I think we need a better device tree.
Click to expand...
Click to collapse
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
CallMeVentus said:
I recall CM10.1 needing a kernel build from scratch, along with building the ROM
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.

eeehaw said:
Try getting the yuga tree, and change yuga to huashan, and fusion3 to viskan wherever possible.
This should not be straightforward. You will have to make some tweaks also.
That *might* work.
You mean coping the kernel sources files to kernel/sony/huashan right ? I did the same thing.
Click to expand...
Click to collapse
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."

CallMeVentus said:
Hmm....and did you define the kernel building path in the boardconfig.mk?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.

eeehaw said:
yes. The kernel was getting built. I was able to see a boot logo on the screen. FreeXperia/Sony logo in this case. And then it would hang. Once I got a bootloop. I was messing around with the ramdisk to see if any hacks get it working.
Click to expand...
Click to collapse
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."

CallMeVentus said:
Did you implement the changes needed for a CM kernel from its stock sources? I'm not sure of the changes, though. Each kernel differs.
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Click to expand...
Click to collapse
No. I knew there were changes but I never knew what they were ? I asked a few people in a few threads but was not able to decipher.
Do you have any idea what sort of changes are required. ?

[Solved] ChameleonOS-janice compiled, but wifi issue!

Hi guys,
i'm a new member and i've read forum rules, this is my first post, i hope i'm posting to the right section. I'm trying to build ChameleonOS from source for our device, after 7 hours everytime i get two errors saying "vibrator.c:76: error: undefined reference to "sendit"" and "vibrator.c:81: error: undefined reference to "sendit"", then the build stops with Error 1. I'm using Lubuntu 13.04 with ChaOS repo and Team Canjica's repos: device, vendor, kernel, libhardware and libhardware_legacy, i followed this guide: http://forum.xda-developers.com/showthread.php?t=2351504. Seems that these errors are related to libhardware_legacy's vibrator.c, i attach the image of the error in this post. Thanks
P.S. Sorry for my bad english, i'm Italian
EDIT: For error I made post #5 instead of edit this, sorry! :angel:

No one can help me? Also only to ignore the errors and continue the build, if there's a way, instead of automatically stop it. In this case I can extract libhardware_legacy.so from CM10.1's flashable zip and put it in builded ChaOS's flashable zip.

Add ifdef to the original vibrator c file
Sent from my GT-I9070 using Tapatalk 4

Shaaan said:
Add ifdef to the original vibrator c file
Sent from my GT-I9070 using Tapatalk 4
Click to expand...
Click to collapse
In which part of file I have to add it?

[HELP] ChameleonOS-janice compiled, but wifi issue!
Now I have compiled ChameleonOS for janice, everything works fine but low incall volume bug, same as CM, and wifi doesn't turn on with compiled boot.img... I've tested it with CM10.1 build 20130923's boot.img and wifi works, but in this way loses the customizations and possibility to use integrated theme manager, which are the strong point of this rom. When this problem will be resolved I share the rom in devs section. Any help will be appreciated

Tesla-MADAL93 said:
Now I have compiled ChameleonOS for janice, everything works fine but low incall volume bug, same as CM, and wifi doesn't turn on with compiled boot.img... I've tested it with CM10.1 build 20130923's boot.img and wifi works, but in this way loses the customizations and possibility to use integrated theme manager, which are the strong point of this rom. When this problem will be resolved I share the rom in devs section. Any help will be appreciated
Click to expand...
Click to collapse
compile again with our updated sources
Sent from my GT-S5367 using xda app-developers app

frapeti said:
compile again with our updated sources
Sent from my GT-S5367 using xda app-developers app
Click to expand...
Click to collapse
Okay, sources updated, now I'm rebuilding
EDIT: Recompiled, now wifi works