Database Users

CM10 JB Rom boot loop..

Anyone have experienced boot loop for the CM10 build?

wagnus said:
Anyone have experienced boot loop for the CM10 build?
Click to expand...
Click to collapse
Anyway this ROM is so fast and great and I really would like to flash it for daily use! :good:

Many issues with video playback as well as some audio problems, it may be fast but if video does not work then what is the point. I am waiting on a response as how to convert videos in order to play them back using CM10.
Sent from my GT-P6800 using xda premium

adinis78 said:
Many issues with video playblack as some audio problems, it may be fast but if video does not work then what is the point. I am waiting on a response as how to convert videos in order to play them back using CM10.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
I have reflashed this ROM again from stock HC, full data/cache wipe. Everything's seems smooth currently..

Setup a standard CyanogenMod 10 build environment (there are plenty of tutorials on the web already on how to do this). Then
Add add the following entries to your local manifest
Code:
<project path="device/samsung/XXX"
name="ohanar/android_device_samsung_XXX"
revision="jellybean"
remote="github" />
<project path="device/samsung/smdk4210-tab"
name="ohanar/android_device_samsung_smdk4210-tab"
revision="jellybean"
remote="github" />
<project path="kernel/samsung/smdk4210-tab"
name="ohanar/android_kernel_samsung_smdk4210-tab"
revision="ics"
remote="github" />
where you replace XXX with your device (i815, p6200, p6210, p6800, p6810, or t869).
Make sure that your device is running the newest build of CyanogenMod 10.
Make sure your device is plugged in and has debugging enabled.
Run the extract-files script from your particular device tree.
Run vendor/cm/get-prebuilts
Your sources are now ready, to build run
Code:
$ . build/envsetup.sh # this sets up the build environment
$ lunch cm_XXX-userdebug # this selects your device
$ mka bacon # this builds CM
Click to expand...
Click to collapse
Any know how to configure the local manifest ? I've been googled for this but still unable to understand..

wagnus said:
Any know how to configure the local manifest ? I've been googled for this but still unable to understand..
Click to expand...
Click to collapse
Copy and Paste the xml to
/path/to/your/build/directory/.repo/local_manifest.xml
e.g. /home/username/android/system/.repo/local_manifest.xml​
And beware of the typo, its make bacon​ not mka bacon​

lowtraxx said:
Copy and Paste the xml to
/path/to/your/build/directory/.repo/local_manifest.xml
e.g. /home/username/android/system/.repo/local_manifest.xml​
And beware of the typo, its make bacon​ not mka bacon​
Click to expand...
Click to collapse
Thanks a million! At least now I got some clues..:good:

Please I reflashed my p6800 to Stock HC and now it asks me for a password , Any clues what the password is ???

mayaco said:
Any clues what the password is ???
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showpost.php?p=12453585&postcount=1332
Keep us posted

Now Im On galaxy tab 7.7 screen and hanged in there , Tried to flash stock HC again , same issue , Tried to slash Stock ICS, same stucked galaxy tab 7.7 sceen nthng further , >>>>>> Wt shall i do now pleaseeeeeeeeeeeee?????
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
Astrix Ashburn said:
Try this: http://forum.xda-developers.com/showpost.php?p=12453585&postcount=1332
Keep us posted
Click to expand...
Click to collapse
I did bt Im still on the same password query screen (asking me to enter your password ?)
thanx alot though for ur efforts:good:

Help Camcorder resolution with custom roms

Alright I'm really stumped by this one. I've searched and searched and not found much so I'm down to asking for any kind of help.
I'll even be happy with " Hey it's right here. Search better."
So my My touch 4g is rooted and I'd been using CM7 nightlys then jumped to the ICS roms and had been using Dark Unicorn v2-5 with the default kernel that comes with the Rom. Gapps ICS 20120429-signed. Flashing process : Wipe data/factory --> Wipe cache --> wipe dalvik --> wipe battery --> install rom.
So what I've noticed is that when I start the camcorder it's defaulting to 320x 240 resolution even with 720/480 selected. Still it only records in that format and it looks horrible. It also defaults to a .mp4 format. So I searched and searched found in the media_profiles.xml file that all the formats were set to that resolution. I tried to change them with root explorer and it basically caused the recorder to FC. Went back to CM7 and was able to record at 720/480. Copied all the settings and reinstalled Dark Unicorn and I can get the preview to show in 720/480 but it will not record.
I've tried MIUI and same problem tried a different kernel to no avail. So what am I doing wrong??
Media_profile.xml from the zip \system\etc\
Code:
<EncoderProfile quality="720p" fileFormat="mp4" duration="30">
<Video codec="m4v"
bitRate="128000"
width="320"
height="240"
frameRate="15" />
<Audio codec="amrnb"
bitRate="12200"
sampleRate="8000"
channels="1" />
</EncoderProfile>
Taken from CM 8-19-2012 \System\ETC\
Code:
<EncoderProfile quality="hd" fileFormat="mp4" duration="60">
<Video codec="h264"
bitRate="6000000"
width="1280"
height="720"
frameRate="30" />
<Audio codec="aac"
bitRate="96000"
sampleRate="16000"
channels="1" />
</EncoderProfile>

Recording at 720p is a problem for all our ICS roms for the time being. Your solution is not going to be found in media_profiles, I can tell ya that much.

Synthetic.Nightmare said:
Recording at 720p is a problem for all our ICS roms for the time being. Your solution is not going to be found in media_profiles, I can tell ya that much.
Click to expand...
Click to collapse
Is there a solution other then going back to GB or I guess switching to another video app? media_profiles was my at work attempt to figure out what the problem was.
Thanks for the reply.

The problem is at the kernel level. We have no v3 AOSP kernel. Those ROMs are using a modified GB kernel with a custom HAL to make the camera function as well as it does.
Virtuous Infinity has a v3 kernel. Try that.
But thanks for searching and trying a few things before creating a thread
Oh, and you aren't performing a full wipe. You are missing several partitions. Try switching to 4EXT recovery.

estallings15 said:
The problem is at the kernel level. We have no v3 AOSP kernel. Those ROMs are using a modified GB kernel with a custom HAL to make the camera function as well as it does.
Virtuous Infinity has a v3 kernel. Try that.
But thanks for searching and trying a few things before creating a thread
Oh, and you aren't performing a full wipe. You are missing several partitions. Try switching to 4EXT recovery.
Click to expand...
Click to collapse
Turns out we didn't need a 3.0 kernel for 720p after all
Sent from my MyTouch 4G using xda app-developers app

Synthetic.Nightmare said:
Turns out we didn't need a 3.0 kernel for 720p after all
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
:applauds:
Kudos to you, my good man!
Sent from my HTC Glacier using xda app-developers app

[ROM][4.3][P7300/P7310][UNOFFICIAL] AOKP [2013-Sep-16]

WARNING: This is an experimental build!
Usual disclaimers:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working:
WLAN
What's broken:
HDMI output
Untested:
Everything else
Please report device specific issues here: http://code.google.com/p/tab89cm/issues/list
All credits go to pershoot, AAccount, epinter and the AOKP team who did most of the work.
Downloads:
GApps (2013-Aug-24):
http://www.mediafire.com/download/yka61uuw7g90s70/gapps-jb-mr2-noneon-20130824-signed.zip, credits to dreamcwli
AOKP:
https://code.google.com/p/tab89cm/downloads/list?q=AOKP+4.3

Sources:
https://github.com/AOKP
https://github.com/pershoot
https://github.com/cmorlok
Init AOKP tree:
Code:
$ repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2
My local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="https://github.com/" />
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" remote="github" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" remote="github" revision="refs/heads/aokp-jb-mr2" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" remote="github" revision="refs/heads/aokp-jb-mr2" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" remote="github" revision="refs/heads/aokp-jb-mr2" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="refs/heads/cm-10.2" />
<remove-project name="AOKP/vendor_aokp"/>
<project name="cmorlok/vendor_aokp" path="vendor/aokp" remote="github" revision="refs/heads/jb-mr2" />
<remove-project name="AOKP/build" />
<project name="cmorlok/cm_android_build" path="build" remote="github" revision="refs/heads/aokp-jb-mr2" />
</manifest>

Oh my. Such a good dev never stops working. Thanks
Gửi từ Nokia chạy iOS

Awesome!!!
Sent from my I9105P using Xda Premium 4

The main reason I tried this is because AOKP allows to switch to the old tablet UI without breaking the new notification panel. I hope you guys will test that stuff. I'll post a poll later to find out which ROM (CM10.1/10.2/AOKP) is the most desired. I don't have much time at the moment and I don't use my tab at all (only on vacances ), so I would like to concentrate on one ROM.

@C-o-M: Will test this later today! Thanx!
Edit: Had to try it right away, and it is smoother than the CM-versions. Big thanks.

I will try when im at home thanks
Sent from my I9105P using Xda Premium 4

Can't force portrait mode no matter what I try. System settings or launcher settings.
Edit: lol, rotation option in system bar.
Sent from my GT-P7310 using xda app-developers app

Idlekilla said:
Edit: Had to try it right away, and it is smoother than the CM-versions. Big thanks.
Click to expand...
Click to collapse
Smoother than CM10.1 or CM10.2? CM10.1 is in my opinion very smooth whereas CM10.2 is kind of laggy.
@C-o-M: Will there also be a P7300 build, what I could test? Thanks!

Typing from AOKP now it is awesome
Sent from my GT-P7310 using xda app-developers app

I've installed the ROM today, I works fine,looks smooth ,at the touch / Browser I see now lags
I've flashed over cm10.2, with all wipes/ factory reset
What works:
WiFi
Bluetooth
Camera both
Root after installing su app
Multi user and profile doesn't work , it was working on the last cm10.2
Reboot,and reboot into recovery doesn't works
Edit1 Screenshot doesn't work
GPS untested ,I will try it later
Edit 2:
GPS doesn't work
Tab crashed when I put in the keyboard dock
Sent from my GT-P7310 using xda app-developers app

shiko80 said:
Smoother than CM10.1 or CM10.2? CM10.1 is in my opinion very smooth whereas CM10.2 is kind of laggy.
@C-o-M: Will there also be a P7300 build, what I could test? Thanks!
Click to expand...
Click to collapse
Smoother than anything I've tried. And that without overclocking to the usual 1400 MHz.
Sent from my GT-P7310 using xda app-developers app

Keynoard dock not working tablet crashes when you put him in the dock i have this problem also on cm10.2
Sent from my I9105P using Xda Premium 4

Smooth Rom, I like it
Roms runs very nice. Smoother than CM10.2, indeed. No idea about the battery yet, too short to tell.
Am unable to reboot though, either normal or to recovery. The tab will hang at a black screen. Only solution is to long-press power, all is well after that. Already reflashed a stock Rom using Odin, tried some different CWM versions, all with no avail.
Really odd. Anybody has any idea why this is, or even better, how to solve it? Starting from a clean slate (already did this several times now) right now is doable as I haven't fully configured the tab yet. :good:

I tried to do a dirty flash from cm10.2, but just sits on the splash screen doing its fancy animation (about 2hrs now). Guess I'll have to try find some time to factory reset...

Brendo said:
I tried to do a dirty flash from cm10.2, but just sits on the splash screen doing its fancy animation (about 2hrs now). Guess I'll have to try find some time to factory reset...
Click to expand...
Click to collapse
A dirty flash between different ROMs always fails. The problem is in most cases the format of the SQLite dbs used to store system data. Many ROMs (and each new version) add additional stuff, giving the DB a new version. You will most probably see a lot of "version mismatch" errors when you start an adb logcat during the fancy boot animation.
(You can of course take a deeper look on which DBs are wrong and delete them manually from /data. This would just delete the data from affected apps. But it isn't recommended at all. Better is to start from scratch and restore app data only from apps where you really need it)

safariking said:
Keynoard dock not working tablet crashes when you put him in the dock i have this problem also on cm10.2
Sent from my I9105P using Xda Premium 4
Click to expand...
Click to collapse
Dock without keyboard (only audio) freezes the tablet too.

No problem with GPS here. Flashed over CM 10.2 HD (safarikings) with all wipes and format system.

Hello Com
now I'm testing this ROM 3 days, depent off all issues, I'm going back to the last version of cm 10.2 from you.
This ROM is smooth , I see no lags, but cm 10.2 works for me better, when we can one version what have all functions from both where are the best, but I think this is not possible
Sent from my GT-P7310 using xda app-developers app

Swapped to AOKP from 10.2 a couple of days ago. Can't say I notice any performance difference myself. Happy with either on my P7310.
Maybe there are some differences I just haven't discovered?!
Nice to know which ROM will be kept in development, though.

[Q] Blank screen after flashing self compiled OMNI ROM

Anyone else experienced this? I'm building for Mako and the build is successful although after flashing the screen is just black after the google logo.
Do I need to extract the N4 binaries for this or am I missing something else? Thanks!
Sent from my Nexus 4 using XDA Premium 4 mobile app

You don't have the proprietary blobs.
Put the following line into your /omni/.repo/local_manifests/whatever.xml, resync and do a clobber recompile.
Code:
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />

chasmodo said:
You don't have the proprietary blobs.
Put the following line into your /omni/.repo/local_manifests/whatever.xml, resync and do a clobber recompile.
Code:
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />
Click to expand...
Click to collapse
Warning: This isn't guaranteed for all devices, as for some we're probably going to be diverging from current blob repos over time.
That is admittedly a bit of a problem now - without nightlies or existing builds, extract-files isn't the most reliable, and right now the blob repos the developers are using are private until we can sort out how to handle them. (Blob repos are always a bit of a complex legal grey area, which is why none of the official CM documentation references the repos at TheMuppets anywhere.)
For nearly all devices where it's known that SOMEONE has it booting from the repos you're using, blank screen on boot usually means no blobs. (A good way to check is to see if your ZIP is much smaller than typical for builds for that device.)

@Entropy512
and as non dev its imbossible to get hands on your private blobs atm?

In the mako build it mentions getting the blob files from developers.google.com/android/nexus/drivers#makojwr66y and putting them in the correct vendor directory. Should this work or is it necessary that we use the muppets binaries still?

Never mind, I figured out what the problem was thanks to some help in the irc chat. I updated the wiki page for building mako too.

caspian154 said:
Never mind, I figured out what the problem was thanks to some help in the irc chat. I updated the wiki page for building mako too.
Click to expand...
Click to collapse
What was the problem? Cause I have the same problem when trying to build rom for HTC One S C2.

makkeonmies said:
@Entropy512
and as non dev its imbossible to get hands on your private blobs atm?
Click to expand...
Click to collapse
It's quite possible - Quite a few people found them within 5 minutes of the first push to those repos on github...
The repos are public, we just don't go out of our way to point to them for various reasons.
(blob handling has always been a mess and will always suck - keep in mind that blob handling was one of the primary contributors to JBQ's final burnout and departure from AOSP.)

[Q] Anyone wanna help me with this problem? (Compiling CM11)

target Prebuilt: (/home/'Username/android/system/out/target/product/hltexx/kernel)
make: *** No rule to make target '/home/'Username'/android/system/out/target/product/hltexx/obj/STATIC_LIBRARIES/libhealthd.qcom_intermediates/export_includes', needed by '/home/'Username'/android/system/out/target/product/hltexx/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.
So, apparently I don't have the Healthd_intermediates folder in my Static_Libraries or my Executables folder. Any idea what I should do?

Hi,
Did u mange to compile it? and overcome your issue?
Is there any CM11 (4.4) Working version for NOTE3 ? Please advise

Blancos4Lyf said:
target Prebuilt: (/home/'Username/android/system/out/target/product/hltexx/kernel)
make: *** No rule to make target '/home/'Username'/android/system/out/target/product/hltexx/obj/STATIC_LIBRARIES/libhealthd.qcom_intermediates/export_includes', needed by '/home/'Username'/android/system/out/target/product/hltexx/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.
So, apparently I don't have the Healthd_intermediates folder in my Static_Libraries or my Executables folder. Any idea what I should do?
Click to expand...
Click to collapse
Comment out
Code:
#BOARD_HAL_STATIC_LIBRARIES := libhealthd.qcom
in /device/samsung/qcom-common/BoardConfigCommon.mk. It has a default fallback. Kernel should compile then. I'm stuck at compiling webkit. Good luck
(btw. im also trying to build hltexx)

I'll try it soon thanks!!
Sent from my SM-N9005 using Tapatalk

ponglenis said:
Comment out
Code:
#BOARD_HAL_STATIC_LIBRARIES := libhealthd.qcom
in /device/samsung/qcom-common/BoardConfigCommon.mk. It has a default fallback. Kernel should compile then. I'm stuck at compiling webkit. Good luck
(btw. im also trying to build hltexx)
Click to expand...
Click to collapse
Quick question, how did you find out where the Quote was?

Blancos4Lyf said:
Quick question, how did you find out where the Quote was?
Click to expand...
Click to collapse
I just searched for the string 'libhealthd.qcom' as it was causing the error!
Several fixes were merged since yesterday, now you won't have to make that change! Just sync your repos and brunch!
I'm running another build as we speak! Let's see if data works this time!!

ponglenis said:
I just searched for the string 'libhealthd.qcom' as it was causing the error!
Several fixes were merged since yesterday, now you won't have to make that change! Just sync your repos and brunch!
I'm running another build as we speak! Let's see if data works this time!!
Click to expand...
Click to collapse
Wait, where did you search? I'm having problems with something else haha
Invalid context file found in /home/"Username"/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts
external/sepolicy/Android.mk:103: recipe for target '/home/"Username"/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts' failed
make: *** [/home/"Username"/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts] Error 5
make: *** Deleting file '/home/"Username"/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts'

kdisc98 said:
Hi,
Did u mange to compile it? and overcome your issue?
Is there any CM11 (4.4) Working version for NOTE3 ? Please advise
Click to expand...
Click to collapse
This is my first ROM so it'll take me a lot longer, some other people have managed to compile it for the TMO edition, to get it working with the International one it requires a small change to one file.

Blancos4Lyf said:
Wait, where did you search? I'm having problems with something else haha
Invalid context file found in /home/mahyar/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts
external/sepolicy/Android.mk:103: recipe for target '/home/mahyar/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts' failed
make: *** [/home/mahyar/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts] Error 5
make: *** Deleting file '/home/mahyar/android/system/out/target/product/hltexx/obj/ETC/file_contexts_intermediates/file_contexts'
Click to expand...
Click to collapse
Hmm, I'm not sure about that
All I can say is that with the latest commits, the build goes fine without errors.
Yesterday all went fine for me too (after i installed bison), the only issue being the one you originally posted about libhealthd.qcom.
This is my roomservice:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
All I do really is:
1. Init CM repo
2. Sync repo
3. run build/envsetup.sh
3. Add above device specific repos to roomservice.xml
4. sync again
5. breakfast hltexx (now using cm_hltexx-eng)
6. brunch hltexx (now using cm_hltexx-eng)
7. About 45 mins later -> flashable zip

ponglenis said:
Hmm, I'm not sure about that
All I can say is that with the latest commits, the build goes fine without errors.
Yesterday all went fine for me too (after i installed bison), the only issue being the one you originally posted about libhealthd.qcom.
This is my roomservice:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
All I do really is:
1. Init CM repo
2. Sync repo
3. run build/envsetup.sh
3. Add above device specific repos to roomservice.xml
4. sync again
5. breakfast hltexx (now using cm_hltexx-eng)
6. brunch hltexx (now using cm_hltexx-eng)
7. About 45 mins later -> flashable zip
Click to expand...
Click to collapse
My xml was slightly different to that one, hopefully that should fix it.

Yeah, I had the libhealthd error as well building for hltetmo yesterday but the patch that has been merged fixes it so you no longer have to comment out the libhealthd line. Make sure you are using openjdk 7 or oracle jdk as openjdk 6 didn't work for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

CalcProgrammer1 said:
Yeah, I had the libhealthd error as well building for hltetmo yesterday but the patch that has been merged fixes it so you no longer have to comment out the libhealthd line. Make sure you are using openjdk 7 or oracle jdk as openjdk 6 didn't work for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
My problem is just with Healthd not libhealthd
target StaticExecutable: su.recovery (/home/"Username"/android/system/out/target/product/hltexx/obj/RECOVERY_EXECUTABLES/su.recovery_intermediates/LINKED/su.recovery)
/home/"Username"/android/system/out/target/product/hltexx/obj/lib/crtbegin_static.o:crtbrand.c:function _start: error: undefined reference to 'main'
collect2: error: ld returned 1 exit status
build/core/executable.mk:70: recipe for target '/home/"Username"/android/system/out/target/product/hltexx/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd' failed
make: *** [/home/"Username"/android/system/out/target/product/hltexx/obj/EXECUTABLES/healthd_intermediates/LINKED/healthd] Error 1