Issues Compiling CM 11 from Source - Android Q&A, Help & Troubleshooting

I'm trying to compile CM-11 from source and it's taken forever to get this far but I'm learning. I have the source downloaded 100% no errors and I did the step by step guide on how to get to brunch dlx for the "HTC DNA" build and I get this error.
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:396: undefined reference to `icu_46::RBBINode::findNodes(icu_46::UVector*, icu_46::RBBINode::NodeType, UErrorCode&)'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:399: undefined reference to `icu_46::RBBINode::findNodes(icu_46::UVector*, icu_46::RBBINode::NodeType, UErrorCode&)'
/media/ubuntu/developer/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/third_party_icu_icuuc_host_gyp_intermediates/third_party_icu_icuuc_host_gyp.a(rbbitblb.o): In function `icu_46::RBBITableBuilder::build()':
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:78: undefined reference to `icu_46::RBBINode::flattenVariables()'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:93: undefined reference to `icu_46::RBBINode::RBBINode(icu_46::RBBINode::NodeType)'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:94: undefined reference to `icu_46::RBBINode::RBBINode(icu_46::RBBINode::NodeType)'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:98: undefined reference to `icu_46::RBBINode::~RBBINode()'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:99: undefined reference to `icu_46::RBBINode::~RBBINode()'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:114: undefined reference to `icu_46::RBBINode::RBBINode(icu_46::RBBINode::NodeType)'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:122: undefined reference to `icu_46::RBBINode::RBBINode(icu_46::RBBINode::NodeType)'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:126: undefined reference to `icu_46::RBBINode::~RBBINode()'
/media/ubuntu/developer/android/system/external/chromium_org/third_party/icu/source/common/rbbitblb.cpp:136: undefined reference to `icu_46::RBBINode::flattenSets()'
collect2: ld returned 1 exit status
make: *** [/media/ubuntu/developer/android/system/out/host/linux-x86/obj/EXECUTABLES/v8_tools_gyp_mksnapshot_arm_host_gyp_intermediates/mksnapshot.arm] Error 1
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
I'm guessing it has something to do with mksnapshot.arm which I've checked and that file don't exisit so I do repo sync and it finishs and the file is still not there... Any tips on how to fix this issue?

Related

Questions

Not the best title for the thread, but I couldn't get better.
So, I have a few questions:
If I copy for example, init.qcom.sh to the root of my phone, does it start next boot? How to make it so?
How are virtual keys handled in Android? Is there a special surf_keypad.kcm.bin? How to make virtual keys work in recovery?
I have an answer for the second question: The keys should be provided by kernel in /sys/board_properties/virtualkeys.<touchscreen-name>.
I can see why they don't work in recovery, the new 5.5.0.4 version of CWM doesn't have virtual key input :S. It's included in gingerbread-release, but not in ics. Is it supphosed to be like this?
I've got a question too... I've just downloaded your device tree for U8800 ICS from github, can I use the extract-files.sh (and maybe other files - still new at this!) to get the proprietary files to build CM7? Or are they ICS specific? Cheers!
dsmenzies said:
I've got a question too... I've just downloaded your device tree for U8800 ICS from github, can I use the extract-files.sh (and maybe other files - still new at this!) to get the proprietary files to build CM7? Or are they ICS specific? Cheers!
Click to expand...
Click to collapse
My tree is still very basic, but you should be able to do that.
The things that may conflict are releasetools, but on CM7 it should be pretty much same. And you should use stock kernel, it has different input methods etc so that may conflict too.
Sent from my U8800
Thanks for that - I've finally got it starting to compile, but you were right about the recovery tools conflicting. I've solved most of my problems with the help of my friend google, but do you have any idea where I should start with this one? I'm sure I can find the problem, I just need to know where to start!
First, you should find the default init.rc from bootable/recovery. Then, copy it and modify it to have the same services as mine (rmt_storage, charge).
The releasetools is pretty much same, search where the default files are, then copy them and seek which changes have I made and add it to yours. I changed two things in releasetools, added function WriteRawImage with a fourth parameter, the actual location of the image and then used that function instead of default when it copiies boot.img.
I hope you understand me, but ask me if you have problems.
About question 1: I believe the .sh files should be added as service, then it should run. The problem why I did not understand was that the ROM I had was using a different init process, which ran that automatically.
Thanks for that! I did as you said and also had two change to lines in the BoardConfig.mk
BOARD_EGL_CFG := $(LOCAL_PATH)/egl.cfg --> BOARD_EGL_CFG := device/huawei/u8800/egl.cfg
TARGET_RECOVERY_INITRC := $(LOCAL_PATH)/recovery/init.rc --> TARGET_RECOVERY_INITRC := device/huawei/u8800/recovery/init.rc
Don't know why it didn't like it, but it's happily compiling now!
Unfortunately it got stuck further on.
I'm getting the following errors:
Code:
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function wipe_data:bootable/recovery/recovery.c:681: error: undefined reference to 'device_wipe_data'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function prompt_and_wait:bootable/recovery/recovery.c:707: error: undefined reference to 'device_perform_action'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function prompt_and_wait:bootable/recovery/recovery.c:761: error: undefined reference to 'MENU_HEADERS'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function prompt_and_wait:bootable/recovery/recovery.c:761: error: undefined reference to 'MENU_ITEMS'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function main:bootable/recovery/recovery.c:851: error: undefined reference to 'device_recovery_start'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function main:bootable/recovery/recovery.c:920: error: undefined reference to 'device_wipe_data'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread:bootable/recovery/ui.c:346: error: undefined reference to 'device_reboot_now'
collect2: ld returned 1 exit status
make: *** [out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1
make: *** Waiting for unfinished jobs....
It's obviously linked to the recovery again which is a pain as I'll be replacing it with ClockworkMod anyway!
I didn't quite understand what you meant by "adding .sh files as a service" so it could be related to me not doing that?
Any help is greatly appreciated!
dsmenzies said:
Unfortunately it got stuck further on.
I'm getting the following errors:
Code:
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function wipe_data:bootable/recovery/recovery.c:681: error: undefined reference to 'device_wipe_data'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function prompt_and_wait:bootable/recovery/recovery.c:707: error: undefined reference to 'device_perform_action'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function prompt_and_wait:bootable/recovery/recovery.c:761: error: undefined reference to 'MENU_HEADERS'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function prompt_and_wait:bootable/recovery/recovery.c:761: error: undefined reference to 'MENU_ITEMS'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function main:bootable/recovery/recovery.c:851: error: undefined reference to 'device_recovery_start'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function main:bootable/recovery/recovery.c:920: error: undefined reference to 'device_wipe_data'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread:bootable/recovery/ui.c:346: error: undefined reference to 'device_reboot_now'
collect2: ld returned 1 exit status
make: *** [out/target/product/u8800/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1
make: *** Waiting for unfinished jobs....
It's obviously linked to the recovery again which is a pain as I'll be replacing it with ClockworkMod anyway!
I didn't quite understand what you meant by "adding .sh files as a service" so it could be related to me not doing that?
Any help is greatly appreciated!
Click to expand...
Click to collapse
The question 1 (.sh files) was part of the original topic .
ClockworkMod is built from source aswell when you build CyanogenMod, but if you already have CWM on your device, might aswell leave that out "TARGET_NO_RECOVERY := true" in the BoardConfig.mk . That should stop recovery from building.
But the error is probably because some header files are missing.

[Q]CM9-HUAWEI-ASCEND-G300-U8815/U8818--build--error

Hello every body
I build CM9 for Huawei ascend G300/U8815, but some errors 。who can help me
thank you
env:mac os x 10.7.4
sorry my english
prebuilt/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/u8818/obj/EXECUTABLES/rild_intermediates/rild.o: in function s_rilEnv:rild.c(.data.rel.s_rilEnv+0x4): error: undefined reference to 'RIL_onUnsolicitedResponse'
collect2: ld returned 1 exit status
make: *** [out/target/product/u8818/obj/EXECUTABLES/rild_intermediates/LINKED/rild] Error 1
make: *** Waiting for unfinished jobs....
prebuilt/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/u8818/obj/SHARED_LIBRARIES/libmedia_intermediates/IMediaRecorder.o: in function .LTHUNK2:frameworks/base/include/binder/IInterface.h:44: error: undefined reference to 'android::ICameraRecordingProxy::asInterface(android::sp<android::IBinder> const&)'
collect2: ld returned 1 exit status
Click to expand...
Click to collapse
我也遇到这个问题了,找不到解决办法,不知道楼主解决没有?
http://www.modaco.com/topic/354238-ics-cyanogenmod-9-for-the-ascend-g300-link-up/
Modaco seems more active at the moment with dev for this device.
Wow that's amazing. I hope you can overcome those errors. Good luck with you attempt to port the cyaongen 9 to the awesome Huawei Ascend G300.

[Kernel 3.0.8] Kernel compiles, but does not boot (stuck at LGE logo, no logcat)

I stuck with these reference errors.
Is someone here able to help me?
Code:
arch/arm/mach-msm/built-in.o: In function `get_nand_partitions':
lge_pwrsink.c:(.text+0xc140): undefined reference to `msm_nand_data'
lge_pwrsink.c:(.text+0xc154): undefined reference to `msm_nand_data'
arch/arm/mach-msm/built-in.o: In function `display_panic_reason':
lge_pwrsink.c:(.text+0x3eb68): undefined reference to `msm_pm_flush_console'
lge_pwrsink.c:(.text+0x3ebc0): undefined reference to `get_ram_console_buffer'
arch/arm/mach-msm/built-in.o: In function `panic_report':
lge_pwrsink.c:(.text+0x3f430): undefined reference to `get_ram_console_buffer'
arch/arm/mach-msm/built-in.o: In function `lock_dependencies_report':
lge_pwrsink.c:(.text+0x3f618): undefined reference to `get_ram_console_buffer'
arch/arm/mach-msm/built-in.o: In function `camera_power_off':
lge_pwrsink.c:(.text+0x3fbe4): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fbfc): undefined reference to `aat28xx_ldo_enable'
lge_pwrsink.c:(.text+0x3fc3c): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fc54): undefined reference to `aat28xx_ldo_enable'
lge_pwrsink.c:(.text+0x3fc6c): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fc84): undefined reference to `aat28xx_ldo_enable'
lge_pwrsink.c:(.text+0x3fc9c): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fcb4): undefined reference to `aat28xx_ldo_enable'
arch/arm/mach-msm/built-in.o: In function `camera_power_on':
lge_pwrsink.c:(.text+0x3fd6c): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fd84): undefined reference to `aat28xx_ldo_enable'
lge_pwrsink.c:(.text+0x3fdc4): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fddc): undefined reference to `aat28xx_ldo_enable'
lge_pwrsink.c:(.text+0x3fdf4): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fe0c): undefined reference to `aat28xx_ldo_enable'
lge_pwrsink.c:(.text+0x3fe24): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x3fe3c): undefined reference to `aat28xx_ldo_enable'
arch/arm/mach-msm/built-in.o: In function `thunderg_vibrator_power_set':
lge_pwrsink.c:(.text+0x40550): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x40568): undefined reference to `aat28xx_ldo_enable'
lge_pwrsink.c:(.text+0x4059c): undefined reference to `aat28xx_ldo_set_level'
lge_pwrsink.c:(.text+0x405b4): undefined reference to `aat28xx_ldo_enable'
arch/arm/mach-msm/built-in.o: In function `p****_tag_msm_partition':
lge_pwrsink.c:(.init.text+0x137c): undefined reference to `msm_nand_data'
arch/arm/mach-msm/built-in.o: In function `msm7x2x_init':
lge_pwrsink.c:(.init.text+0x2974): undefined reference to `msm_acpu_clock_init'
lge_pwrsink.c:(.init.text+0x2a30): undefined reference to `msm_device_uart3'
arch/arm/mach-msm/built-in.o: In function `lge_add_mmc_devices':
lge_pwrsink.c:(.init.text+0x2ba0): undefined reference to `msm_add_sdcc'
lge_pwrsink.c:(.init.text+0x2be8): undefined reference to `msm_add_sdcc'
arch/arm/mach-msm/built-in.o: In function `lge_add_lcd_devices':
lge_pwrsink.c:(.init.text+0x2c78): undefined reference to `msm_fb_register_device'
lge_pwrsink.c:(.init.text+0x2c88): undefined reference to `msm_fb_register_device'
lge_pwrsink.c:(.init.text+0x2c98): undefined reference to `msm_fb_register_device'
arch/arm/mach-msm/built-in.o: In function `msm_device_i2c_init':
lge_pwrsink.c:(.init.text+0x33a4): undefined reference to `msm_device_i2c'
arch/arm/mach-msm/built-in.o: In function `msm_add_usb_devices':
lge_pwrsink.c:(.init.text+0x3410): undefined reference to `msm_device_gadget_peripheral'
lge_pwrsink.c:(.init.text+0x3418): undefined reference to `msm_device_otg'
arch/arm/mach-msm/built-in.o:(.init.data+0x108): undefined reference to `msm_device_smd'
arch/arm/mach-msm/built-in.o:(.init.data+0x10c): undefined reference to `msm_device_dmov'
arch/arm/mach-msm/built-in.o:(.init.data+0x110): undefined reference to `msm_device_nand'
arch/arm/mach-msm/built-in.o:(.init.data+0x114): undefined reference to `msm_device_i2c'
arch/arm/mach-msm/built-in.o:(.init.data+0x118): undefined reference to `msm_device_uart_dm1'
arch/arm/mach-msm/built-in.o:(.init.data+0x170): undefined reference to `msm_device_otg'
arch/arm/mach-msm/built-in.o:(.init.data+0x174): undefined reference to `msm_device_gadget_peripheral'
drivers/built-in.o: In function `display_table':
clkdev.c:(.text+0x31a00): undefined reference to `mddi_host_register_cmds_write8'
drivers/built-in.o: In function `kgsl_pwrctrl_init':
clkdev.c:(.text+0x58b80): undefined reference to `internal_pwr_rail_mode'
drivers/built-in.o: In function `kgsl_pwrctrl_pwrrail':
clkdev.c:(.text+0x58cfc): undefined reference to `internal_pwr_rail_ctl'
clkdev.c:(.text+0x58d48): undefined reference to `internal_pwr_rail_ctl'
drivers/built-in.o: In function `flash_onfi_probe':
clkdev.c:(.text+0x832ac): undefined reference to `msm_nand_data'
drivers/built-in.o: In function `isx005_sensor_release':
clkdev.c:(.text+0xd2624): undefined reference to `mdp_load_thunder_lut'
drivers/built-in.o: In function `isx005_sensor_init':
clkdev.c:(.text+0xd2684): undefined reference to `mdp_load_thunder_lut'
drivers/built-in.o: In function `CPLD_LED_probe':
clkdev.c:(.text+0xf77c4): undefined reference to `led_classdev_register'
clkdev.c:(.text+0xf78c4): undefined reference to `led_classdev_unregister'
drivers/built-in.o: In function `msm_pmic_led_resume':
clkdev.c:(.text+0xf7934): undefined reference to `led_classdev_resume'
drivers/built-in.o: In function `msm_pmic_led_suspend':
clkdev.c:(.text+0xf7960): undefined reference to `led_classdev_suspend'
drivers/built-in.o: In function `msm_pmic_led_probe':
clkdev.c:(.text+0xf7988): undefined reference to `led_classdev_register'
drivers/built-in.o: In function `adp8860_probe':
clkdev.c:(.devinit.text+0x4e4): undefined reference to `led_classdev_register'
clkdev.c:(.devinit.text+0x5dc): undefined reference to `led_classdev_unregister'
drivers/built-in.o: In function `adp8860_led_remove':
clkdev.c:(.devexit.text+0x2c): undefined reference to `led_classdev_unregister'
drivers/built-in.o: In function `CPLD_LED_remove':
clkdev.c:(.devexit.text+0x3ac): undefined reference to `led_classdev_unregister'
drivers/built-in.o: In function `msm_pmic_led_remove':
clkdev.c:(.devexit.text+0x408): undefined reference to `led_classdev_unregister'
net/built-in.o: In function `hci_le_connect':
activity_stats.c:(.text+0xe2c04): undefined reference to `l2cap_sock_le_params_valid'
make: *** [vmlinux] Fehler 1
Sources
Sorry, cant help you with kernel errors...
Sent from my LG-P500 using Tapatalk 2
When back home I will take a look
RockR172 said:
Sorry, cant help you with kernel errors...
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thatnextdoorboy said:
Click to expand...
Click to collapse
Wanna prove me dumb?
Continue my AOSP ICS project, fix the compile errors you get, fix the bugs, and il salute you...
End of OT.
Sent from my LG-P500 using Tapatalk 2
He probably doesnt understand why u replay if you cant help.
Its a linker error!!
If the functions are part of another static library, you need to tell the linker to link that library along with your object file.
Here my latest findings:
- internal_pwr_rail_*: missing entry in Makefile -> fixed
- board-msm7x27 is used for our phone (default is devices-msm7x27) -> fixing the compile error resulting from this change
That is (I hope) the last one I have to fix:
Code:
net/built-in.o: In function `hci_le_connect':
activity_stats.c:(.text+0xd7390): undefined reference to `l2cap_sock_le_params_valid'
make: *** [vmlinux] Fehler 1
Code:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: »include/generated/mach-types.h« ist bereits aktualisiert.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CHK kernel/config_data.h
Kernel: arch/arm/boot/Image is ready
Building modules, stage 2.
Kernel: arch/arm/boot/zImage is ready
MODPOST 1 modules
But its not booting
Any log? Sometimes logcat work even when it's stuck on lg logo.
Roqu3 said:
Any log? Sometimes logcat work even when it's stuck on lg logo.
Click to expand...
Click to collapse
I haven't tried till now, because when using linux adb does not connect.
Will start windows and try again.
Stupid me, I used my server (ssh) and stared adb there.
Its impossible to connect to my phone when its connect to my Notebook.
Stuck at LGE logo, no logcat. ADB does not connect.
DJNoXD said:
I haven't tried till now, because when using linux adb does not connect.
Will start windows and try again.
Stupid me, I used my server (ssh) and stared adb there.
Its impossible to connect to my phone when its connect to my Notebook.
Stuck at LGE logo, no logcat. ADB does not connect.
Click to expand...
Click to collapse
It only stucks at lge logo and adb can not connect to the phone.
If have tried to use the same config for 3.0.8 like for the 2.6.35.14 kernel.
I thought the size should be near to, but its ~300kb smaler.
That is smaler is not problem (only necessary drivers are included), but I think ~300kb is to much.
Has someone an idea how I can solve the problem without logs?
Some question:
If I flash am using a gingerbread rom and flash kernel 3.0.8.
What will happen.
Ok 3.0.8 is not campatible with gingerbread, but should the log show something?
Or would nothing work (even log)? I always believed that the log will tell about boot problems.
I think if this would be the case, I know my fault.
DJNoXD said:
That is (I hope) the last one I have to fix:
Code:
net/built-in.o: In function `hci_le_connect':
activity_stats.c:(.text+0xd7390): undefined reference to `l2cap_sock_le_params_valid'
make: *** [vmlinux] Fehler 1
Click to expand...
Click to collapse
Anyway,I dont know if i told you about this already but "recoll" application can help you to index files and make searching for text in kernel source easier this can help to fixed "undefined" error
I guess rom needs modification too if it is about 3.0 in gb.try kernel with ics rom
Sent from my LG-P500 using xda premium
aspee said:
Anyway,I dont know if i told you about this already but "recoll" application can help you to index files and make searching for text in kernel source easier this can help to fixed "undefined" error
I guess rom needs modification too if it is about 3.0 in gb.try kernel with ics rom
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Thanks, I will try that tool. Searching is always to slow.
Yesterday I triey cm9 with my 3.0.8 kernel, but its the same problem.
It's maybe something realy simple that I forgot to change.
get some help from here
http://www.xda-developers.com/android/the-new-development-cycle-starts/
I am no expert, but maybe get some help from one of those XDA-TV unboxers.
If one can connect to the tty/uart that is on the phone's board, maybe a normal Linux bootup sequence will be available and one can see where the thing hangs up.
Dovidhalevi said:
I am no expert, but maybe get some help from one of those XDA-TV unboxers.
If one can connect to the tty/uart that is on the phone's board, maybe a normal Linux bootup sequence will be available and one can see where the thing hangs up.
Click to expand...
Click to collapse
Good suggestion.
UART requires db9 connectors.. do we have those ports on our thunderg board??

[Q]Help building CM9

Hey guys I'm having some issues here
I'm apptempting to port CM9 to the HTC Thunderbolt.
I used ICS device-specific files picked from ProTekk's and liquid0624's githubs.
I attempted to compile many times, and got mixed errors.
Now every time I try to compile, I get this same error.
Code:
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6/libstdc++.a when searching for -lstdc++
out/host/linux-x86/obj/EXECUTABLES/grxmlcompile_intermediates/grxmlcompile.o: In function `std::list::_M_erase(std::_List_iterator)':
/usr/include/c++/4.6/bits/stl_list.h:1532: undefined reference to `std::__detail::_List_node_base::_M_unhook()'
out/host/linux-x86/obj/EXECUTABLES/grxmlcompile_intermediates/grxmlcompile.o: In function `std::list::_M_insert(std::_List_iterator, int const&)':
/usr/include/c++/4.6/bits/stl_list.h:1516: undefined reference to `std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*)'
out/host/linux-x86/obj/EXECUTABLES/grxmlcompile_intermediates/grxmlcompile.o: In function `std::list::_M_transfer(std::_List_iterator, std::_List_iterator, std::_List_iterator)':
/usr/include/c++/4.6/bits/stl_list.h:1508: undefined reference to `std::__detail::_List_node_base::_M_transfer(std::__detail::_List_node_base*, std::__detail::_List_node_base*)'
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/grxmlcompile_intermediates/grxmlcompile] Error 1
make: *** Waiting for unfinished jobs....
[email protected]:~/android/system$
Any help is greatly appreciated!

[Q] error whiling compiling libmedia.so

my device is HTC LEO
i am compiling CM jellybean now
i got this error while compiling libmedia.so
Code:
in function construction vtable for android::IDirectTrackClient-in-android::AudioTrack:AudioTrack.cpp(.data.rel.ro._ZTCN7android10AudioTrackE0_NS_18IDirectTrackClientE+0x18): error: undefined reference to 'android::IDirectTrackClient::getInterfaceDescriptor() const'
in function construction vtable for android::IDirectTrackClient-in-android::AudioTrack:AudioTrack.cpp(.data.rel.ro._ZTCN7android10AudioTrackE0_NS_18IDirectTrackClientE+0x40): error: undefined reference to 'virtual thunk to android::IDirectTrackClient::~IDirectTrackClient()'
frameworks/native/include/binder/IInterface.h:44: error: undefined reference to 'android::IDirectTrack::asInterface(android::sp<android::IBinder> const&)'
collect2: ld returned 1 exit status
any one can help me to fix this issue
do i need to keep my device connecting to computer insure it can collect info from device
i also check android google developer reference and did not find getInterfaceDescriptor() Method
all error above are come out in file frameworks/native/include/binder/IInterface.h
please help
help me please
any one can help
Add IMPLEMENT_META_INTERFACE( your_service_class).

Categories

Resources