My device needs config_useDevInputEventForAudioJack in order to detect a plugged in headset. I have been building lineage based on AndyYan's treble scripts (which are based on PHH). I can get my headphones working if I set the prop persist.sys.overlay.devinputjack to true (this triggers an overlay in PHHussons vendor_hardware_overlay). I have created an overlay using PHHussons guide for my phone (a Teracube 2e). The only value I am setting in the overlay is the config_useDevInputEventForAudioJack, so my res/values/config.xml looks exactly like the devinputjack overlay:
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<bool name="config_useDevInputEventForAudioJack">true</bool>
</resources>
I have given it a unique priority and name as laid out in PHHussons guide and I end up with an apk which has the correct contents. The overlay is correctly identified with the phone's build fingerprint and correctly gets put in /system/overlays
I cannot figure out why this does not allow the headphone jack to work.... I can still get it working (or stop it) by setting the persist.sys.overlay.devinputjack prop.
Here is my manifest and makefile... I would appreciate any help.
Code:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="me.phh.treble.overlay.teracube.tc2e"
android:versionCode="1"
android:versionName="1.0">
<overlay android:targetPackage="android"
android:requiredSystemPropertyName="ro.vendor.build.fingerprint"
android:requiredSystemPropertyValue="+Teracube/Teracube_2e*"
android:priority="221"
android:isStatic="true" />
</manifest>
Code:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := optional
LOCAL_PACKAGE_NAME := treble-overlay-teracube-tc2e
LOCAL_MODULE_PATH := $(TARGET_OUT)/overlay
LOCAL_IS_RUNTIME_RESOURCE_OVERLAY := true
LOCAL_PRIVATE_PLATFORM_APIS := true
include $(BUILD_PACKAGE)
sailorcampbell said:
My device needs config_useDevInputEventForAudioJack in order to detect a plugged in headset. I have been building lineage based on AndyYan's treble scripts (which are based on PHH). I can get my headphones working if I set the prop persist.sys.overlay.devinputjack to true (this triggers an overlay in PHHussons vendor_hardware_overlay). I have created an overlay using PHHussons guide for my phone (a Teracube 2e). The only value I am setting in the overlay is the config_useDevInputEventForAudioJack, so my res/values/config.xml looks exactly like the devinputjack overlay:
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<bool name="config_useDevInputEventForAudioJack">true</bool>
</resources>
I have given it a unique priority and name as laid out in PHHussons guide and I end up with an apk which has the correct contents. The overlay is correctly identified with the phone's build fingerprint and correctly gets put in /system/overlays
I cannot figure out why this does not allow the headphone jack to work.... I can still get it working (or stop it) by setting the persist.sys.overlay.devinputjack prop.
Here is my manifest and makefile... I would appreciate any help.
Code:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="me.phh.treble.overlay.teracube.tc2e"
android:versionCode="1"
android:versionName="1.0">
<overlay android:targetPackage="android"
android:requiredSystemPropertyName="ro.vendor.build.fingerprint"
android:requiredSystemPropertyValue="+Teracube/Teracube_2e*"
android:priority="221"
android:isStatic="true" />
</manifest>
Code:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := optional
LOCAL_PACKAGE_NAME := treble-overlay-teracube-tc2e
LOCAL_MODULE_PATH := $(TARGET_OUT)/overlay
LOCAL_IS_RUNTIME_RESOURCE_OVERLAY := true
LOCAL_PRIVATE_PLATFORM_APIS := true
include $(BUILD_PACKAGE)
Click to expand...
Click to collapse
Use this as a template. Priority should be 6.
https://github.com/phhusson/vendor_hardware_overlay/blob/master/DevInputJack/AndroidManifest.xml
Related
I am trying to build CM-11 but I keep getting stopped on
Code:
make: *** No rule to make target `/home/gakio12/cm11/out/target/product/hlte/obj/lib/libtime_genoff.so', needed by `/home/gakio12/cm11/out/target/product/hlte/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so'. Stop.
'
Everything was changed from hlte-common to hlte in device/samsung, but in vendor/samsung, it remains hlte-common. I'm not sure if this is the problem, but renaming the directory to 'hlte' did nothing.
This is in my hlte-common-vendor.mk file in vendor/samsung/hlte-common:
Code:
PRODUCT_PACKAGES += libtime_genoff
$(call inherit-product, vendor/samsung/hlte-common/hlte-common-vendor-blobs.mk)
Does anyone know how I can start to diagnose the problem? libtime_genoff.so is in vendor/samsung/hlte-common, but I have a feeling it is supposed to be elsewhere now that the devices are 'unified'.
gakio12 said:
I am trying to build CM-11 but I keep getting stopped on
Code:
make: *** No rule to make target `/home/gakio12/cm11/out/target/product/hlte/obj/lib/libtime_genoff.so', needed by `/home/gakio12/cm11/out/target/product/hlte/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so'. Stop.
'
Everything was changed from hlte-common to hlte in device/samsung, but in vendor/samsung, it remains hlte-common. I'm not sure if this is the problem, but renaming the directory to 'hlte' did nothing.
This is in my hlte-common-vendor.mk file in vendor/samsung/hlte-common:
Code:
PRODUCT_PACKAGES += libtime_genoff
$(call inherit-product, vendor/samsung/hlte-common/hlte-common-vendor-blobs.mk)
Does anyone know how I can start to diagnose the problem? libtime_genoff.so is in vendor/samsung/hlte-common, but I have a feeling it is supposed to be elsewhere now that the devices are 'unified'.
Click to expand...
Click to collapse
I'm trying to figure out the same issue as you
I figured out the problem; make sure you have revision="wip" at the end of the kernel and TheMuppets lines of your local_manifest.xml.
gakio12 said:
I figured out the problem; make sure you have revision="wip" at the end of the kernel and TheMuppets lines of your local_manifest.xml.
Click to expand...
Click to collapse
Awesome that worked
gakio12 said:
I figured out the problem; make sure you have revision="wip" at the end of the kernel and TheMuppets lines of your local_manifest.xml.
Click to expand...
Click to collapse
Hi I'm a noob, Can you please give me a little bit more details how to fix this problem please. I'm still learning. Thanks
HI thanks for give me some hints. Just figure it out.
gakio12 said:
I am trying to build CM-11 but I keep getting stopped on
Code:
make: *** No rule to make target `/home/gakio12/cm11/out/target/product/hlte/obj/lib/libtime_genoff.so', needed by `/home/gakio12/cm11/out/target/product/hlte/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so'. Stop.
'
Everything was changed from hlte-common to hlte in device/samsung, but in vendor/samsung, it remains hlte-common. I'm not sure if this is the problem, but renaming the directory to 'hlte' did nothing.
This is in my hlte-common-vendor.mk file in vendor/samsung/hlte-common:
Code:
PRODUCT_PACKAGES += libtime_genoff
$(call inherit-product, vendor/samsung/hlte-common/hlte-common-vendor-blobs.mk)
Does anyone know how I can start to diagnose the problem? libtime_genoff.so is in vendor/samsung/hlte-common, but I have a feeling it is supposed to be elsewhere now that the devices are 'unified'.
Click to expand...
Click to collapse
Hi, I meet the same issue as you, can you give me some advice on how to solve this problem?
I have this exact problem. I am building a jflte cm11 with no prior experience on linux or on compiling any big projects whatsoever. Can anyone explain for a starter what I need to do? I opened a local_manifest.xml and it said
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="koush/Superuser" path="external/koush/Superuser" remote="github" revision="master" />
<project name="koush/Widgets" path="external/koush/Widgets" remote="github" revision="master" />
</manifest>
I followed this tutorial to the word: http://wiki.cyanogenmod.org/w/Build_for_jflte
libtime_genoff.so.toc
PHP:
ninja: error: '/home/ost268/EmotionOS/out/target/product/kenzo/obj/lib/libtime_genoff.so.toc', needed by '/home/ost268/EmotionOS/out/target/product/kenzo/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so', missing and no known rule to make it
make: *** [ninja_wrapper]Error 1
Add to vendor/xiaomi/kenzo/Android.mk
PHP:
include $(CLEAR_VARS)
LOCAL_MODULE := libtime_genoff
LOCAL_MODULE_CLASS := SHARED_LIBRARIES
LOCAL_MODULE_OWNER := xiaomi
LOCAL_MODULE_PATH_64 := $(TARGET_OUT_VENDOR_SHARED_LIBRARIES)
LOCAL_MODULE_PATH_32 := $(2ND_TARGET_OUT_VENDOR_SHARED_LIBRARIES)
LOCAL_MODULE_SUFFIX := .so
LOCAL_MODULE_TAGS := optional
LOCAL_MULTILIB := both
LOCAL_PROPRIETARY_MODULE := true
LOCAL_SRC_FILES_64 := proprietary/vendor/lib64/libtime_genoff.so
LOCAL_SRC_FILES_32 := proprietary/vendor/lib/libtime_genoff.so
include $(BUILD_PREBUILT)
hi,
in different customization of the same device , we find some option in system configuration enabled in some and other no then we can do it by changing variable value in application files in system by decompiling and recompiling after modifying ( bools or arrays...etc ) it take a lot of time
so customization Sony has choose to make a little files for a region customization or enabling or disabling option in system app without modifying the original app file by using {real_application_name}-res.apk what will be adding in /system/vendor/overlay
in 4.0.4 and before sony ericsson used /system/etc/customization/ folder for enabling and parameterizing apps, so in JB 4.2 and 4.3or 4.4these files are incompatible only 4.3 and 4.4 are compatible (attached files)
for JB 4.2
4.3 and 4.4
How to use ??
example :
for enabling data traffic notification and status icon in status bar we must change in or semcphone.apk phone.apk this line after decompiling Phone.apk or SemcPhone.apk in res/value/bools/xml we find a default value of application :
Code:
<bool name="data_connection_except_mms_can_clear_icon">true</bool>
<bool name="data_connection_except_mms_show_icon_when_disabled">true</bool>
<bool name="data_connection_except_mms_show_icon_when_enabled">false</bool>
Click to expand...
Click to collapse
they must be change to :
Code:
<bool name="data_connection_except_mms_can_clear_icon">false</bool> ----->[COLOR="red"] icon always visible can't be removed[/COLOR]
<bool name="data_connection_except_mms_show_icon_when_disabled">true</bool>
<bool name="data_connection_except_mms_show_icon_when_enabled">true</bool>
Click to expand...
Click to collapse
then it can be inserted in com.phone-res.apk and injected in system/vendor/overlay and rebooting after that the options are activated.
just know what value to want be activated in the main application apk
Another exemple :
in this post http://forum.xda-developers.com/showthread.php?t=2703113 to have mod for activating low cost in conversations.apk but with decompiling main apk conversations.apk but the simple one is using -res.apk
default value are :
Code:
<bool name="character_conversion">false</bool>
<bool name="character_conversion_visibility">false</bool>
Click to expand...
Click to collapse
and must be changed to
Code:
<bool name="character_conversion">true</bool>
<bool name="character_conversion_visibility">true</bool>
Click to expand...
Click to collapse
then modifing com.sonyericsson.conversations-res.apk
after decomiling
we have
Code:
[CODE]
[/CODE]
res
|-------> bools.xml -------------> to be modified
|-------> public.xml ---------------important contains all variable defined
bools.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<bool name="three_digit_number_linkify">true</bool>
<bool name="delivery_report">true</bool>
<bool name="mms_retrieval_during_roaming_visibility">true</bool>
[COLOR="Red"]<bool name="character_conversion">true</bool>
<bool name="character_conversion_visibility">true</bool>[/COLOR]
</resources>
public.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<public type="bool" name="three_digit_number_linkify" id="0x7f020000" />
<public type="bool" name="delivery_report" id="0x7f020001" />
<public type="bool" name="mms_retrieval_during_roaming_visibility" id="0x7f020002" />
[COLOR="red"]<public type="bool" name="character_conversion" id="0x7f020003" />
<public type="bool" name="character_conversion_visibility" id="0x7f020004" />[/COLOR]
<public type="bool" name="enable_send_empty_message" id="0x7f020005" />
<public type="integer" name="max_recipients" id="0x7f030000" />
<public type="integer" name="mms_max_size" id="0x7f030001" />
<public type="integer" name="sms_max_segments" id="0x7f030002" />
<public type="integer" name="mms_trigger_sms_segments" id="0x7f030003" />
</resources>
and recompile, push it. and done.
the files contains :
For JB 4.2 taken from diffrent cutomization for xperial L (perhaps orange france)
android-res.apk
com.android.browser-res.apk
com.android.email-res.apk
com.android.internal-res.apk
com.android.phone-res.apk
com.android.providers.partnerbookmarks-res.apk
com.android.settings-res.apk
com.android.systemui-res.apk
com.sonyericsson.capabilities-res.apk
com.sonyericsson.conversations-res.apk
com.sonyericsson.customizedsettings-res.apk
com.sonyericsson.home-res.apk
com.sonyericsson.initialbootsetup-res.apk
com.sonyericsson.r2r.client-res.apk
com.sonyericsson.setupwizard-res.apk
com.sonyericsson.simcontacts-res.apk
com.sonyericsson.trackid-res.apk
com.sonyericsson.updatecenter-res.apk
com.sonyericsson.wappush-res.apk
SemcAlbum-Overlay-300.apk
SemcPhone-Overlay-285.apk
SystemUI-Overlay-285.apk
For 4.3-4.4 Tooken from Z1 customized T-mobile DE
android-res.apk
com.android.browser-res.apk
com.android.email-res.apk
com.android.nfc-res.apk
com.android.phone-res.apk
com.android.providers.partnerbookmarks-res.apk
com.android.providers.settings-res.apk
com.android.settings-res.apk
com.sonyericsson.android.omacp-res.apk
com.sonyericsson.android.socialphonebook-res.apk
com.sonyericsson.capabilities-res.apk
com.sonyericsson.conversations-res.apk
com.sonyericsson.customizedsettings-res.apk
com.sonyericsson.home-res.apk
com.sonyericsson.initialbootsetup-res.apk
com.sonyericsson.r2r.client-res.apk
com.sonyericsson.setupwizard-res.apk
com.sonyericsson.shutdownanim-res.apk
com.sonyericsson.simcontacts-res.apk
com.sonyericsson.textinput.uxp-res.apk
com.sonyericsson.trackid-res.apk
com.sonyericsson.updatecenter-res.apk
com.sonyericsson.wappush-res.apk
overlay-semcalbum-flickr-on.apk
ServiceMenu-Overlay-295.apk
SmartConnect-Overlay-295.apk
reserved For futur Use
Can you upload the modified for xperia M?
Sent from my C1904 using Tapatalk
icoolguy1995 said:
Can you upload the modified for xperia M?
Sent from my C1904 using Tapatalk
Click to expand...
Click to collapse
here is com.sonyericsson.conversations-res.apk attached, modified file compatible with JB4.3 and KK4.4
hi, i'm requesting devs who build cm 13 for bullhead to kindly share their roomservice.xml. i'm trying to build cm from source and the system generated roomservice.xml is as follows:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_bullhead" path="device/lge/bullhead" remote="github" />
<project name="CyanogenMod/android_kernel_lge_bullhead" path="kernel/lge/bullhead" remote="github" />
</manifest>
i think this does not contain bolbs, which are also required for building from source. i tried building without them and i get the following error:
Code:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/home/gururoop/android/cm13/out/target/product/bullhead/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so] Error 1
make: Leaving directory `/home/gururoop/android/cm13'
Can anyone help me with these errors?
gururoop said:
hi, i'm requesting devs who build cm 13 for bullhead to kindly share their roomservice.xml. i'm trying to build cm from source and the system generated roomservice.xml is as follows:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_bullhead" path="device/lge/bullhead" remote="github" />
<project name="CyanogenMod/android_kernel_lge_bullhead" path="kernel/lge/bullhead" remote="github" />
</manifest>
i think this does not contain bolbs, which are also required for building from source. i tried building without them and i get the following error:
Code:
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/home/gururoop/android/cm13/out/target/product/bullhead/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so] Error 1
make: Leaving directory `/home/gururoop/android/cm13'
Can anyone help me with these errors?
Click to expand...
Click to collapse
Vendor files? https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-13.0
I know the vendor stuff is different from everything else I've used/built for and I only had to "brunch bullhead" to build a different rom I tried.
Keithn said:
Vendor files? https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-13.0
I know the vendor stuff is different from everything else I've used/built for and I only had to "brunch bullhead" to build a different rom I tried.
Click to expand...
Click to collapse
did you extract blobs using extract-files.sh script? can you please share the roomservice.xml of the ROM that built successfully and booted?
gururoop said:
did you extract blobs using extract-files.sh script? can you please share the roomservice.xml of the ROM that built successfully and booted?
Click to expand...
Click to collapse
Nope I never had to do it that way and I usually just add the vendor files from the muppets git (linked above) instead.
What commands are you using to build?
Try just using ". build/envsetup.sh" then use "brunch bullhead". Downloaded everything I needed to build omni last I tried. My server/PC I use for building isn't connected or running right now so I can't directly pull the XML I used. I probably could later though.
Another thing is that you can add your own XML into the local manifests to sync files so you don't have to touch the room service.XML. Here is one I was using for an example https://github.com/Keith-N/local_manifests/blob/master/local_manifests.xml
Keithn said:
Nope I never had to do it that way and I usually just add the vendor files from the muppets git (linked above) instead.
What commands are you using to build?
Try just using ". build/envsetup.sh" then use "brunch bullhead". Downloaded everything I needed to build omni last I tried. My server/PC I use for building isn't connected or running right now so I can't directly pull the XML I used. I probably could later though.
Another thing is that you can add your own XML into the local manifests to sync files so you don't have to touch the room service.XML. Here is one I was using for an example https://github.com/Keith-N/local_manifests/blob/master/local_manifests.xml
Click to expand...
Click to collapse
I would really appreciate if you could share your roomservice.xml whenever possible. I did try to give commands as per your post and got the error mentioned in the OP. I'm trying to start with building CM and expand the base if I succeed.
I tried it out and it's missing the vendor files. You'll notice no vendor/lge in your cm13 directory. The way I talked about in the previous post will work. You need to get those vendor files. I could give you my roomservice.xml but it shouldn't look any different because I never touched it. I used an addition xml to add aditional files which is why my roomservice.xml was never changed. The easy way is to add this line into whatever xml you are planning on using to sync the files.
Code:
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-13.0" />
It grabs the files from https://github.com/TheMuppets/proprietary_vendor_lge and syncs them into vendor/lge
If you have troubles then let me know, but that is all I needed to do.
Does anyone have any tips/techniques for resolving "No rule to make target" errors?
I got the error:
Code:
make: *** No rule to make target 'libsrv_init', needed by '/home/buildbot/android/slim/out/target/product/maguro/obj/EXECUTABLES/pvrsrvinit_intermediates/pvrsrvinit.o'. Stop.
So to find the reference I did
Code:
find -type f -name "*.mk"|xargs grep pvrsrvinit
./device/samsung/tuna/BoardConfig.mk: pvrsrvinit.te \
./hardware/ti/omap4/common.mk: pvrsrvinit \
./hardware/ti/omap4/pvrsrvinit/Android.mk:LOCAL_SRC_FILES := pvrsrvinit.c
./hardware/ti/omap4/pvrsrvinit/Android.mk:LOCAL_MODULE := pvrsrvinit
~/android/slim $ find -type f -name "*.mk"|xargs grep libsrv_init
./device/samsung/maguro/self-extractors/imgtec/staging/device-partial.mk: libsrv_init \
./device/samsung/maguro/self-extractors/imgtec/staging/proprietary/Android.mk:LOCAL_MODULE := libsrv_init
./device/samsung/maguro/self-extractors/imgtec/staging/proprietary/Android.mk:LOCAL_SRC_FILES := libsrv_init.so
./hardware/ti/omap4/pvrsrvinit/Android.mk:LOCAL_ADDITIONAL_DEPENDENCIES := libsrv_init libsrv_um
It is clear here that a blob is missing.
Searching online suggested adding another local manifest (is this the right one?)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="android-5.1" />
</manifest>
I suppose if it was a new device I would have to search the filesystem of the phone for the file right?
Has anyone got any tips of better ways of dealing with this situation?
As a side note: How did SlimLP compile without this extra repo in the manifest?
Or is it common that even for big ROMs that people are doing "dirty" compiles with local manifests and/or locally extracted files in place?
P.S. I am using Lollipop still because my new Chinese phone is still on Lollipop and I thought I would start by building SlimLP for my old maguro as a starting point since the maguro was supported at that point.
I wasn't expecting to get compile errors!
opticyclic said:
Does anyone have any tips/techniques for resolving "No rule to make target" errors?
I got the error:
Code:
make: *** No rule to make target 'libsrv_init', needed by '/home/buildbot/android/slim/out/target/product/maguro/obj/EXECUTABLES/pvrsrvinit_intermediates/pvrsrvinit.o'. Stop.
So to find the reference I did
Code:
find -type f -name "*.mk"|xargs grep pvrsrvinit
./device/samsung/tuna/BoardConfig.mk: pvrsrvinit.te \
./hardware/ti/omap4/common.mk: pvrsrvinit \
./hardware/ti/omap4/pvrsrvinit/Android.mk:LOCAL_SRC_FILES := pvrsrvinit.c
./hardware/ti/omap4/pvrsrvinit/Android.mk:LOCAL_MODULE := pvrsrvinit
~/android/slim $ find -type f -name "*.mk"|xargs grep libsrv_init
./device/samsung/maguro/self-extractors/imgtec/staging/device-partial.mk: libsrv_init \
./device/samsung/maguro/self-extractors/imgtec/staging/proprietary/Android.mk:LOCAL_MODULE := libsrv_init
./device/samsung/maguro/self-extractors/imgtec/staging/proprietary/Android.mk:LOCAL_SRC_FILES := libsrv_init.so
./hardware/ti/omap4/pvrsrvinit/Android.mk:LOCAL_ADDITIONAL_DEPENDENCIES := libsrv_init libsrv_um
It is clear here that a blob is missing.
Searching online suggested adding another local manifest (is this the right one?)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="android-5.1" />
</manifest>
I suppose if it was a new device I would have to search the filesystem of the phone for the file right?
Has anyone got any tips of better ways of dealing with this situation?
As a side note: How did SlimLP compile without this extra repo in the manifest?
Or is it common that even for big ROMs that people are doing "dirty" compiles with local manifests and/or locally extracted files in place?
P.S. I am using Lollipop still because my new Chinese phone is still on Lollipop and I thought I would start by building SlimLP for my old maguro as a starting point since the maguro was supported at that point.
I wasn't expecting to get compile errors!
Click to expand...
Click to collapse
Did you find a solution? I'm facing the same problem, any clue would be appreciated.
grab (link disallowed since i have less than 10 posts and they ****ing think it's spam... google driver binaries and sources for maguro and it's the imagination technologies file) then extract and execute at root of your source, and it should shove some binaries and a makefile that declares the missing dependency
Skip the "Extract proprietary blobs" step and instead use "TheMuppets"
Skip the "Extract proprietary blobs" step and instead use "TheMuppets", meaning, add the following lines to the file .repo/local_manifests/roomservice.xml:
Code:
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" depth="1" />
<project name="TheMuppets/proprietary_vendor_ti" path="vendor/ti" revision="master" depth="1" />
Rerun "repo sync" and the rest of the steps, excluding the "extract proprietary blobs" step. That should fix it.
Hello,
I am trying to port LineageOS to the Samsung Galaxy S8 as my first LineageOS port. I know this is probably one heck of an undertaking for a first port but a rooted snapdragon-based S8 is currently the only device I have access to and I would like to have stock-ish android on this device.
In any case, I am running into errors while trying to build for the platform.
I am using this guide with this guide for reference to try to port.
I have followed the first guide basically to the tee so far.
These are all of the things (of interest) that I have done.
1. I executed these commands to clone the code base:
Code:
repo init -u https://github.com/LineageOS/android.git -b lineage-19.1
repo sync
2. I have created a file called "local_manifests.xml" in the directory ".repo/local_manifests/" that contains the following:
Code:
?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="android_device_samsung_dreamlte" fetch="https://github.com/TeamWin/" revision="android-9.0"/>
<project name="android_device_samsung_dreamlte" path="device/samsung/dreamlte" remote="android_device_samsung_dreamlte"
revision="android-9.0"/>
<remote name="android_kernel_samsung_msm8998" fetch="https://github.com/jesec/" revision="cm-14.1"/>
<project name="android_kernel_samsung_msm8998" path="kernel/samsung/msm8998" remote="android_kernel_samsung_msm8998" revision="cm-
14.1"/>
<remote name="vendor_samsung_dreamlte" fetch="https://github.com/AndroidBlobs/" revision="dreamltexx-user-8.0.0-R16NW-
G950FXXS4CRJD-release-keys"/>
<project name="vendor_samsung_dreamlte" path="vendor/samsung/dreamlte" remote="vendor_samsung_dreamlte" revision="dreamltexx-user-8.
0.0-R16NW-G950FXXS4CRJD-release-keys"/>
</manifest>
3. I have rerun the repo sync command to sync the blobs, kernel and architecture specific information from the local manifests.
4. I have added a file in the "device/samsung/dreamlte" directory called "lineage_dreamlte.mk" this file contains the following information based on the original "lineage.dependencies" file:
Code:
# Inherit from the common Open Source product configuration
$(call inherit-product, $(SRC_TARGET_DIR)/product/aosp_base_telephony.mk)
# Inherit from our custom product configuration
$(call inherit-product, vendor/lineage/config/common.mk)
PRODUCT_DEVICE := dreamlte
PRODUCT_NAME := lineage_dreamlte
PRODUCT_MODEL := Galaxy S8
PRODUCT_BRAND := Samsung
PRODUCT_MANUFACTURER := Samsung
5. I have added a blank file called "lineage.dependencies" in the same directory because the original omni.dependencies was also blank
6. I have modified the file called "BoardConfig.mk" in the same directory to read the following. This file was made based on a combination of the original file (which is for the Exynos-based model of the S8) and the board configuration for the Google Pixel 2 (available here) which has the same SOC as the Snapdragon-based S8.
Code:
Platform
DEVICE_CODENAME := dreamlte
DEVICE_PATH := device/samsung/$(DEVICE_CODENAME)
BOARD_VENDOR := samsung
TARGET_BOARD_PLATFORM := msm8998
TARGET_BOOTLOADER_BOARD_NAME := msm8998
TARGET_NO_BOOTLOADER := true
TARGET_NO_RADIOIMAGE := true
# Architecture
TARGET_ARCH := arm64
TARGET_ARCH_VARIANT := armv8-a
TARGET_CPU_ABI := arm64-v8a
TARGET_CPU_ABI2 :=
TARGET_CPU_VARIANT := cortex-a53
TARGET_CPU_SMP := true
# Secondary Architecture
TARGET_2ND_ARCH := arm
TARGET_2ND_ARCH_VARIANT := armv8-a
TARGET_2ND_CPU_ABI := armeabi-v7a
TARGET_2ND_CPU_ABI2 := armeabi
TARGET_2ND_CPU_VARIANT := cortex-a53
# File systems
BOARD_HAS_LARGE_FILESYSTEM := true
TARGET_USERIMAGES_USE_EXT4 := true
TARGET_USERIMAGES_USE_F2FS := true
BOARD_HAS_NO_REAL_SDCARD := true
# TWRP specific build flags
RECOVERY_VARIANT := twrp
ALLOW_MISSING_DEPENDENCIES=true
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
TARGET_RECOVERY_PIXEL_FORMAT := "ABGR_8888"
TW_BRIGHTNESS_PATH := "/sys/class/backlight/panel/brightness"
TW_MAX_BRIGHTNESS := 36600
TW_DEFAULT_BRIGHTNESS := 15300
TW_NO_REBOOT_BOOTLOADER := true
TW_HAS_DOWNLOAD_MODE := true
TW_INCLUDE_NTFS_3G := true
TW_EXCLUDE_SUPERSU := true
TW_EXTRA_LANGUAGES := true
TW_USE_NEW_MINADBD := true
LZMA_RAMDISK_TARGETS := recovery
# Kernel
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048
TARGET_PREBUILT_KERNEL := $(DEVICE_PATH)/kernel
BOARD_MKBOOTIMG_ARGS := --kernel_offset 0x00008000 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --dt $(DEVICE_PATH)/dtb
# Include
TARGET_SPECIFIC_HEADER_PATH := $(DEVICE_PATH)/include
7. I run the "source build/envsetup.sh" command
Up to this point there has been no errors.
8. I execute the "brunch lineage_dreamlte-eng" command and get the following
Code:
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:323:
build/make/core/board_config.mk:246: error: Building a 32-bit-app-only product on a 64-bit device. If this is intentional, set TARGET_SUPPORTS_64_BIT_APPS := false.
21:30:50 dumpvars failed with: exit status 1
Device dreamlte not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for dreamlte not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:323:
build/make/core/board_config.mk:246: error: Building a 32-bit-app-only product on a 64-bit device. If this is intentional, set TARGET_SUPPORTS_64_BIT_APPS := false.
21:30:51 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:323:
build/make/core/board_config.mk:246: error: Building a 32-bit-app-only product on a 64-bit device. If this is intentional, set TARGET_SUPPORTS_64_BIT_APPS := false.
21:30:51 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_dreamlte'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
I have looked up this error for multiple hours to no avail. I have no idea what could be the issue, it doesn't seem to me like the 32 bit error is fatal. It seems like it cannot find the product spec for some reason and that is the fatal error.
I am almost certain that I have made some sort of simple mistake that is causing the product spec to not show up. I am also almost certain I have made some sort of other error somewhere else in the process especially in step 6 (the one about the board config).
I would greatly appreciate someone looking over this for me and helping me to solve this issue. My apologies of this error can simply be chalked up to my own stupidity or carelessness.
If you want me to send the contents of any other files, results of commands, etc. I will be more than happy to send them.
Thanks,
sckzor
# Quick check to warn about likely cryptic errors later in the build.
ifeq ($(TARGET_IS_64_BIT),true)
ifeq (,$(filter true false,$(TARGET_SUPPORTS_64_BIT_APPS)))
$(error Building a 32-bit-app-only product on a 64-bit device. \
If this is intentional, set TARGET_SUPPORTS_64_BIT_APPS := false)
endif
endif
TARGET_SUPPORTS_64_BIT_APPS := true get you compiling again.