Database Develop

[DEV] LG P500 Sourcecode Release!

http://www.lg.com/global/support/opensource/opensource-detail.jsp
type LGP500

This will go nicely with the Gingerbread 2.3 SDK just released... I am done deving for the night though... too much of a headache.

Correct link is:
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP500

this is an original rom who can be flashed on phone?

What is the password of the zip file? thanks

fsangio said:
What is the password of the zip file? thanks
Click to expand...
Click to collapse
No pass and it's *.tar

Build instructions :
1. Android buid
- Download original android source code (froyo) from http://source.android.com
- Untar opensource packages of Thunder_Froyo.tar.gz into downloaded android source directory
- And, merge the source into the android source code(froyo)
- Run following scripts to build android
a) . ./build/envsetup.sh
b) choosecombo 1 1 generic 3
c) make -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/target/product/generic
2. Kernel Build
- Untar using follwwing command at the android folder
tar zxvf Thunderg_Kernel.tar.gz
- cd Kernel
- make thunderg-perf_defconfig
- make zImage -j4
3. After Build, You Can find the build image at arch/arm/boot
4. Compile environment
- gcc 4.4.1
- Ubuntu 9.10
Click to expand...
Click to collapse

Has anybody been able to build it successfully ???
I've tried it (following the README steps)...but it does not built.
Here I paste a chunk of the prompted errors:
Code:
target thumb C: liblgdrmwbxml <= device/lge/cappucino/modules/liblgdrm/WBXmllib/wbxml_tree_clb_wbxml.c
target thumb C: liblgdrmwbxml <= device/lge/cappucino/modules/liblgdrm/WBXmllib/wbxml_tree_clb_xml.c
make: *** No rule to make target `out/target/product/generic/obj/STATIC_LIBRARIES/liblgdrmexpat_intermediates/liblgdrmexpat.a', needed by `out/target/product/generic/obj/SHARED_LIBRARIES/liblgdrmwbxml_intermediates/LINKED/liblgdrmwbxml.so'. Stop.
make: *** Waiting for unfinished jobs....
target thumb C: liblgdrmport <= device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c: In function 'drmLibFsOpen':
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c:2108: error: 'AID_LGDRM' undeclared (first use in this function)
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c:2108: error: (Each undeclared identifier is reported only once
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c:2108: error: for each function it appears in.)
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c:2108: error: 'AID_LGDRM_ACC' undeclared (first use in this function)
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c: In function 'drmLibFsCreateDir':
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c:2861: error: 'AID_LGDRM' undeclared (first use in this function)
device/lge/cappucino/modules/liblgdrm/Adapt/Source/DRM_Port_Linux.c:2861: error: 'AID_LGDRM_ACC' undeclared (first use in this function)
make: *** [out/target/product/generic/obj/STATIC_LIBRARIES/liblgdrmport_intermediates/Adapt/Source/DRM_Port_Linux.o] Error 1
[email protected]:~/droidP509$
My environment is:
- java -version : java version "1.5.0_19" (I've tried with java 1.6 and it doesn't built either)
- gcc --version: gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5
- Ubuntu 10.10 (64 bits)
Any suggestion??? What could be failing?? I'm completely stuck :/
Note: I'm able to build the straight android code (without the P500/9 patch)
Thanks in advanced!!

Hello,
How can I merge lg source with google source?

Sorry,
how can I apply lg patch to android source code?
I have downloaded the source with repo
repo init -u git://android.git.kernel.org/platform/manifest.git
repo init -u git://android.git.kernel.org/platform/manifest.git -b froyo
and now? How can I merge lg patch with android froyo source?

I have the source code for p509. how do I install it?

maybe we can resolve the cpu lag when the touch screen is pressed?

cozydroid said:
Any suggestion??? What could be failing?? I'm completely stuck :/
Click to expand...
Click to collapse
It failed to build liblgdrmwbxml because liblgdrmexpat.a is missing. You can either ask LG for liblgdrmexpat.a or grab a copy of liblgdrmwbxml.so from your phone (it's in /system/lib/).

jtaylor63 said:
It failed to build liblgdrmwbxml because liblgdrmexpat.a is missing. You can either ask LG for liblgdrmexpat.a or grab a copy of liblgdrmwbxml.so from your phone (it's in /system/lib/).
Click to expand...
Click to collapse
and after that what should i do to make the whole think compile ?

jtaylor63 said:
It failed to build liblgdrmwbxml because liblgdrmexpat.a is missing. You can either ask LG for liblgdrmexpat.a or grab a copy of liblgdrmwbxml.so from your phone (it's in /system/lib/).
Click to expand...
Click to collapse
and after that what should i do to make the whole think build ?

Januka said:
and after that what should i do to make the whole think build ?
Click to expand...
Click to collapse
. ./build/envsetup.sh
choosecombo 1 1 generic 3
make -j4

irondevil said:
. ./build/envsetup.sh
choosecombo 1 1 generic 3
make -j4
Click to expand...
Click to collapse
this i know, but i mean what shall i do with liblgdrmwbxml.so
I already built the source without the lg code, how can i build it also after merging it?

p500 2.2.2 sources?

DookMatt said:
p500 2.2.2 sources?
Click to expand...
Click to collapse
froyo 2.2 sources but i think there aren't many differents

irondevil said:
froyo 2.2 sources but i think there aren't many differents
Click to expand...
Click to collapse
2.2 kernel and 2.2.2 kernel are different!

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!

[Q] Help Compiling with Camera Patches

I have tried to compile AOKP 4.1.2 with this Cherry Pick:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/85/13285/9 && git cherry-pick FETCH_HEAD
and I get this near the end of the build:
target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):frameworks/base/include/ui/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
I have build aokp before using camcory's prebuilt, and everything works fine but I want to be able to oc and use my own build, with working camera. I tried editing the cameraHAL.cpp, changing void to int, but it doesn't work, it just throws some other related error. I think, I am missing some makefile somewhere, but I'm not certain where. Thanks.

theAPANT said:
I have tried to compile AOKP 4.1.2 with this Cherry Pick:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/85/13285/9 && git cherry-pick FETCH_HEAD
and I get this near the end of the build:
target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):frameworks/base/include/ui/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
I have build aokp before using camcory's prebuilt, and everything works fine but I want to be able to oc and use my own build, with working camera. I tried editing the cameraHAL.cpp, changing void to int, but it doesn't work, it just throws some other related error. I think, I am missing some makefile somewhere, but I'm not certain where. Thanks.
Click to expand...
Click to collapse
I had this issue camcory never pushed the finished camera sources
Here
https://docs.google.com/file/d/0Bwu6jmegWBFQRXNpRFAwc2dZam8/edit
Also, if RIL (data) doesn't work pull the hardware/ril folder from cm10.
I don't have the sources for aokp atm but I think I had to do a few other things to get everything working but they broke camera
Sent from my Nexus 7 using xda app-developers app

Re awaking this thread, hopefully someone can help. OK i am having allot of problems building /hardware/qcom/display and surfacflinger on 4.2.2 liquidsmooth so far i have just removed the problematic things from the specific Android.mk but I'm stilling having lots of problems. Ill post specific error if that is helpful. What have you done to get it to build, I'm downloading aosp now to see if the loquidsmooth team hasnt pushed files but i doubt it. Thanks
Sent from my Nexus 7 using xda app-developers app

CM10.1 wpa problem
I'm getting this and don't know how to fix it. Hopefully one of you do, I had to try using cm10.1 sources instead of liquidsmooth because they haven't pushed changes yet. Any ideas? Thanks
/home/theapant/cm10.1/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_wext.o: in function wpa_driver_wext_ops:driver_wext.c(.data.rel.ro.wpa_driver_wext_ops+0x198): error: undefined reference to 'wpa_driver_signal_poll'
/home/theapant/cm10.1/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: /home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_wext.o: in function wpa_driver_wext_ops:driver_wext.c(.data.rel.ro.wpa_driver_wext_ops+0x1a0): error: undefined reference to 'wpa_driver_wext_driver_cmd'
collect2: ld returned 1 exit status
make: *** [/home/theapant/cm10.1/out/target/product/ancora_tmo/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant] Error 1
make: *** Waiting for unfinished jobs....

Well I deleted /external/wpa_supplicant_8 and renamed the wpa_supplicant_6 to 8 and compiled and I got it to build.
Package complete: /home/theapant/cm10.1/out/target/product/ancora_tmo/cm-10.1-20130301-UNOFFICIAL-ancora_tmo.zip
md5: e714e16988f891693df172e405be1b54
Unfortunately it doesn't boot (black screen) perhaps an issue with using the prebuilt kernel in device/samsung/ancora_tmo/prebuilt/zImage?
Any ideas anyone? I will add the TARGET_KERNEL_CONFIG := ancora_tmo_defconfig in boardconfig.mk and see if that works. Also hopefully someone could shed some light on the previous error that i didn't actually fix. Thanks
Edit: still no boot when i build the kernel

if i can ever get some time dude ill try and help but look for a cm10.1 release from me in a couple of days. i ahve it built and working just havent had time to do anything with it. been working on getting the team sites looking good

target SharedLib: camera.msm7x30 (out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so)
/home/theapant/aokp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/cameraHAL.o: in function camera_set_preview_window(camera_device*, preview_stream_ops*):device/samsung/ancora_tmo/camerahal/cameraHAL.cpp:494: error: undefined reference to 'android:verlay:verlay(void (*)(void*, int), void (*)(void*, unsigned int, unsigned int, unsigned int, unsigned int), void (*)(void*, void*), void*)'
collect2: ld returned 1 exit status
make: *** [out/target/product/ancora_tmo/obj/SHARED_LIBRARIES/camera.msm7x30_intermediates/LINKED/camera.msm7x30.so] Error 1
make: *** Waiting for unfinished jobs....
[email protected]:~/aokp$
I'm getting the same error that I got a long time before. I'm using camcory's device github. If i remove the camerahal.cpp from the android.mk it finishes the build fine and I think I have everything else working now. I built it with camcory's prebuilt 3.0.66 kernel, so is that the issue? Any suggestions are welcome. Thanks!

Using that prebuilt explains your kernel version. Comment out the prebuilt references, make a build, replace new zImage and use that as your prebuilt with new build.

jfbs said:
Using that prebuilt explains your kernel version. Comment out the prebuilt references, make a build, replace new zImage and use that as your prebuilt with new build.
Click to expand...
Click to collapse
Thanks I all ready knew why it is kernel version 3.0.66. I could swap out the zimage but i still cant get camerahal.CPP so i need to fix that first. Camcory built slimbean with camera and 3.0 kernel and i would like to do the same with aokp, however i have to take camerahal out of the make file so that the build finishes because of that error above. I have built plenty of kernels and i can just add kernel source and the target_kernel_config := ancora_tmo_defconfig to boardconfig and it would build the kernel that way too however camcorys kernels are much more stable than mine, so.... Any ideas on how i can fix the camerhal thing?
Sent from my Nexus 7 using xda app-developers app

That cherry-pick is for ICS. I believe Jellybean overlays are in frameworks/native and others in frameworks/av. Check arco's jellybean branches.
Edit: review.cyanogenmod.org/#/c/19964 and the fetch link is mid-page.

jfbs said:
That cherry-pick is for ICS. I believe Jellybean overlays are in frameworks/native and others in frameworks/av. Check arco's jellybean branches.
Edit: review.cyanogenmod.org/#/c/19964 and the fetch link is mid-page.
Click to expand...
Click to collapse
Thanks again, I made a really stupid mistake and only had Overlay.h when I also needed Overlay.cpp, your post made me go back and check my sources and I found the problem. Before I was racing around trying to modify camerahal.cpp with no c++ knowledge. I also fixed an issue I was having with turning wifi on in settings and now I think I have a fully working build of AOKP with 3.0 kernel. Once again thanks!!!

Boot fail from fresh AOSP Build

Hi,
i have a Problem with building a Hammerhead Rom from AOSP.
Buildin otapackage went fine.
running: java -Xmx2048m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpHi4Kxb out/target/product/hammerhead/aosp_hammerhead-ota-eng.androidenv.zip
done.
Click to expand...
Click to collapse
But if flash this zip with TWRP, my Nexus 5 stand still at Google boot logo.
how can I check what I have done wrong?

isRaZZe said:
Hi,
i have a Problem with building a Hammerhead Rom from AOSP.
Buildin otapackage went fine.
But if flash this zip with TWRP, my Nexus 5 stand still at Google boot logo.
how can I check what I have done wrong?
Click to expand...
Click to collapse
My guess would be that you are missing some (or all) proprietary vendor blobs.

upndwn4par said:
My guess would be that you are missing some (or all) proprietary vendor blobs.
Click to expand...
Click to collapse
Your right. Do you have a link for me where i get these vendor blobs and how to include them ?

isRaZZe said:
Your right. Do you have a link for me where i get these vendor blobs and how to include them ?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers

Lethargy said:
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
Thanks. :good:
How do i include them in a automatic process in building ?

isRaZZe said:
Thanks. :good:
How do i include them in a automatic process in building ?
Click to expand...
Click to collapse
You should check if the path on /device/lge/hammerhead/full_hammerhead.mk is correct
and if, when you extract the zip, the device-vendor.mk works....
btw, my advice is to use some working blobs like AOSPA or CM...some binaries aren't in the source zip
...You can check my source for have an idea...

Crostantin said:
You should check if the path on /device/lge/hammerhead/full_hammerhead.mk is correct
and if, when you extract the zip, the device-vendor.mk works....
btw, my advice is to use some working blobs like AOSPA or CM...some binaries aren't in the source zip
...You can check my source for have an idea...
Click to expand...
Click to collapse
This is considerably more complex than I had imagined before.
Can someone explain me in more detail as I insert the blobs and can build a functioning Images?

isRaZZe said:
This is considerably more complex than I had imagined before.
Can someone explain me in more detail as I insert the blobs and can build a functioning Images?
Click to expand...
Click to collapse
in my opinion, the best way is to clone this in your tree (or add it in a local_manifests)
https://github.com/ThankYouMario/proprietary_vendor_lge_hammerhead
and move files to this path: vendor/lge/hammerhead
then you should make this little modification:
https://github.com/BoostPop/android_device_lge_hammerhead/commit/616c559e9fcfbde0e4fb477c681bc36627d5eb00

Crostantin said:
in my opinion, the best way is to clone this in your tree (or add it in a local_manifests)
https://github.com/ThankYouMario/proprietary_vendor_lge_hammerhead
and move files to this path: vendor/lge/hammerhead
then you should make this little modification:
https://github.com/BoostPop/android_device_lge_hammerhead/commit/616c559e9fcfbde0e4fb477c681bc36627d5eb00
Click to expand...
Click to collapse
Thanks. Will try it this evening.
Another question i have...
My idea is to build my own AOSP-Rom with some little modifikation. One of these modifikation are to include the "Close all Tabs" in the system wide tab view.
Where i can find this Code ?
I need to understand first where the individual parts of code are and was hoping that some of you support.
But first I need an executable Rom.
Edit:
I had checkout from git and copy to working directory. Path is vendor/lge/hammerhead. edit full_hammerhead.mk and remove the line and add
$(call inherit-product-if-exists, vendor/lge/hammerhead/hammerhead-vendor.mk)
then:
source build/envsetup.sh .
lunch aosp_hammerhead-userdebug
make -j4 otapackage
end in error :
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/hw/gps.msm8974.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/hw/gps.msm8974.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libgps.utils.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libgps.utils.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libloc_core.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libloc_core.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libloc_eng.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libloc_eng.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/lib/libmmcamera_interface.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/lib/libmmcamera_interface.so'
build/core/Makefile:34: warning: overriding commands for target `out/target/product/hammerhead/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'
build/core/base_rules.mk:550: warning: ignoring old commands for target `out/target/product/hammerhead/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'
No private recovery resources for TARGET_DEVICE hammerhead
build/core/tasks/vendor_module_check.mk:56: *** Error: Product "aosp_hammerhead" cannot have overlay in vendor tree: vendor/lge/hammerhead/overlay. Stop.
Click to expand...
Click to collapse
Edit2:
Problem solved. Add the repo over local_manifest solution and build succesful and rom flash&boot are okay.
before build i need to set PRODUCT_RESTRICT_VENDOR_FILES := false in full_hammerhead.
soo... next step is to add some tweaks. from cm source... also over manifest?

isRaZZe said:
soo... next step is to add some tweaks. from cm source... also over manifest?
Click to expand...
Click to collapse
IMO best way to add features to your own build is get to know how to cherry-pick.
Then how to deal with conflicts etc.
So best way is to check google "how to cherry-pick" , its really easy when you get it.
Then you check CM github the commits you need.

Sick1 said:
IMO best way to add features to your own build is get to know how to cherry-pick.
Then how to deal with conflicts etc.
So best way is to check google "how to cherry-pick" , its really easy when you get it.
Then you check CM github the commits you need.
Click to expand...
Click to collapse
I now have posited me with cherry pick apart. This works so far very good.Thanks for that tipp !
Now I am facing a problem. I want to integrate Koush superuser settings, but the patch from Koush for this is very old (cm10.1) and does not work with cm12. Does anyone have a link to a patch with which I can integrate superuser in the Settingsapp?

nobody?

isRaZZe said:
I now have posited me with cherry pick apart. This works so far very good.Thanks for that tipp !
Now I am facing a problem. I want to integrate Koush superuser settings, but the patch from Koush for this is very old (cm10.1) and does not work with cm12. Does anyone have a link to a patch with which I can integrate superuser in the Settingsapp?
Click to expand...
Click to collapse
isRaZZe said:
nobody?
Click to expand...
Click to collapse
Every question you have asked, and will ask in the future, has been asked and answered many times. Xda alone has many threads on building from source, so creating this thread was pointless.
Google is your friend. Search, read, learn.
Since you want to cherry-pick CM, then the CM github is a great place to start. But I'll give you a hint...CM doesn't use Koush's superuser anymore.
https://github.com/CyanogenMod

Hello guys ...
Can someone tell me the whole process to compile pure AOSP for hammerhead ?? .. How to extract d blobs and everything ..
It would be great if someone helps me
Hope someone helps ..
Thanx

LineageOS 17 for suzuran?

Does its existence for devices like the Z3C make it more or less likely for us to see on suzuran? Would love to see a LineageOS 17 ROM for this device. Makes me wish I was a dev. Thanks to all those who continue to grind hours into porting and developing ROMs for the platform.

beflythis said:
Would love to see a LineageOS 17 ROM for this device.
Click to expand...
Click to collapse
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why

Berni-0815 said:
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why
Click to expand...
Click to collapse
Are you making any kernel changes? If not, that's probably why. You can't use the LineageOS 15.1 kernel on the PIE. Correct me if I'm wrong but Pie requires linux kernel 4.4x and greater while, Android 10 requires 4.9 and greater.

Apart from fixing compile-errors, no.
But I don't think that the kernel version is important. This project uses kernel 3.x too, if I'm not wrong...
Sure, there have to be changes, but I can't do so...

I've tried another kernel (this one) and I changed/added some files to avoid compile errors. But the result is the same:
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
...and so on until end of battery...

Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.

Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place)
Click to expand...
Click to collapse
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
I've tried to build pie with this kernel. Nearly the same result.

Berni-0815 said:
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
I've tried to build pie with this kernel. Nearly the same result.
Click to expand...
Click to collapse
Weird, I ran into some issues building pie yesterday, but didn't have any time to fix it. I'll try again tonight and see how it goes. If I still have issues, I'll have to wait till the weekend.

Joel16 said:
Weird, I ran into some issues building pie yesterday
Click to expand...
Click to collapse
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold

Berni-0815 said:
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold
Click to expand...
Click to collapse
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.

Joel16 said:
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building
Click to expand...
Click to collapse
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.
Click to expand...
Click to collapse
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?

Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.

You can do It!!!

Joel16 said:
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.
Click to expand...
Click to collapse
Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
The z5c is based on Qualcomm Snapdragon 810 MSM8994, like:
SONY XPERIA Z5 PREMIUM | MOTOROLA DROID TURBO | MICROSOFT LUMIA 950 XL | NUBIA Z9 MAX
Is there any source of a pie build availible where we can get some hints how get a pie build to run?
Here are some kernel sources from the Nubia Z9 Max (nx510j):
https://github.com/nubia-development/android_kernel_nubia_msm8994

I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
I'll have a look at this. :good:

Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
For my self I try slowly become deeper into that topic: building a rom.
So I did a little bit of research in github and gitlab and I found some interesting repos from this user:
https://github.com/Cyborg2017?tab=repositories
I ask him if he could help us a little bit and the first result is this.
@Joel16 & @Berni-0815 Perhaps this is useful:
https://github.com/Cyborg2017/android_kernel_sony_msm8994/tree/sony_msm8994_p-upstream
I hope it help us to come closer to an LineageOS 17 for suzuran.

I_did_it_just_tmrrow said:
I ask him if he could help us a little bit and the first result is this.
Click to expand...
Click to collapse
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...

Berni-0815 said:
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...
Click to expand...
Click to collapse
Yep, just try his source. He told that it could be useful to test this kernel with building twrp first.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg

I_did_it_just_tmrrow said:
Yep, just try his source.
Click to expand...
Click to collapse
I'm actually building a rom with that kernel. I'll see later if it's working.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
Click to expand...
Click to collapse
Right
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg
Click to expand...
Click to collapse
Ah! Nice. I'll try it later. Thank you very much! :good:

Berni-0815 said:
I'm actually building a rom with that kernel. I'll see later if it's working.
Right
Ah! Nice. I'll try it later. Thank you very much! :good:
Click to expand...
Click to collapse
Let me know how it goes, I'm more than certain kernel is what's preventing us from getting Pie/Q to boot up.