Related
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:
For newer builds see http://forum.xda-developers.com/showthread.php?t=2687229
WARNING: This is an experimental build!
Usual CM 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
Audio
Rotation
Storage
Camera
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 CM 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
CM 10.2:
https://code.google.com/p/tab89cm/downloads/list?q=cm10.2
Sources:
https://github.com/CyanogenMod
https://github.com/pershoot
https://github.com/cmorlok
My local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" revision="refs/heads/cm-10.2" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" revision="refs/heads/cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" />
<remove-project name="CyanogenMod/android_build" />
<project name="cmorlok/cm_android_build" path="build" revision="refs/heads/cm-10.2" />
</manifest>
Known issues:
If you want to go back to CM10/9 or restore your backup, you'll have to do the following in recovery (do "install zip" and "choose zip from sdcard" first):
Code:
adb shell
# cd /sdcard/
# rm -rf legacy/
# rm -rf obb/
# mv -f 0/* .
# rm -rf 0/
Reserved for FAQ
Awesome! Looking forward to seeing where this build goes. Thanks for keeping this tab on the cutting edge, C-O-M!
Sent from my LG-VM670 using xda app-developers app
waiting P7300 ver..thx c-o-m to make my 8.9 update:laugh:~~
upconvert said:
Awesome! Looking forward to seeing where this build goes. Thanks for keeping this tab on the cutting edge, C-O-M!
Sent from my LG-VM670 using xda app-developers app
Click to expand...
Click to collapse
I agree! Thanks!
Great work! I'm so glad there are people like you around keeping our tab alive!
What about gapps? Included or just use 4.2-gapps?
Waiting for screen capture, thanks CyanogenMod
Idlekilla said:
Great work! I'm so glad there are people like you around keeping our tab alive!
What about gapps? Included or just use 4.2-gapps?
Click to expand...
Click to collapse
I tried the 4.3 GApps. I guess we will see a lot of errors than (like we did for 4.2, e.g. force close on Google Now, ..).
huynhson said:
Waiting for screen capture, thanks CyanogenMod
Click to expand...
Click to collapse
Why? You won't see any difference to 4.2...
E:Error in sd-card.. installation aborted (status 0) - and that unhealthy android. :/
bkk99213 said:
waiting P7300 ver..thx c-o-m to make my 8.9 update:laugh:~~
Click to expand...
Click to collapse
Here we go.
But I suspect 3G is broken like on CM10.1. Any log files are more than welcome since I don't own a 3G tab to test.
Status 0 error P7310
Sent from my GT-P7310 using xda app-developers app
Idlekilla said:
E:Error in sd-card.. installation aborted (status 0) - and that unhealthy android. :/
Click to expand...
Click to collapse
safariking said:
Status 0 error P7310
Click to expand...
Click to collapse
Sorry guys, I've uploaded the wrong file.
Please redownload and verify MD5sum (22b4f5b79243d884fe25a399aa5dd1df) or SHA1sum (c515e18bd78d5b3c62dc279c9d39e07f37325566).
Idlekilla said:
Great work! I'm so glad there are people like you around keeping our tab alive!
What about gapps? Included or just use 4.2-gapps?
Click to expand...
Click to collapse
C-o-M said:
I tried the 4.3 GApps. I guess we will see a lot of errors than (like we did for 4.2, e.g. force close on Google Now, ..)
Click to expand...
Click to collapse
Added link to GApps in first post. The only issue I had so far is force closes of "Google Text-To-Speech". Will look into that tomorrow.
Flashed so far smooth no issues
Flashed with twrp no problems
Sent from my GT-P7310 using xda premium
Mine turns off when charging reaches 100%. Sometimes if I let screen time out, it won't turn back on; have to restart. Several apps fc. Lost root. Updates through play store error out. Feels smooth and mostly working though. Settings sometimes exits out when loading list of installed apps
Loaded 4.3 gapps. Generally, looks good. Panorama in Camera app is great!
Problems:-
- lost root
- Youtube app no-go
- Google Play Music no-go
- Google Text to Speech prob as well
Thanks for work, C-o-M.
Font seems a little blurry also. Colors seem more vibrant though
-----
Sent from my GT-P7310 CM10 using XDA Premium HD app
Brendo said:
Mine turns off when charging reaches 100%. Sometimes if I let screen time out, it won't turn back on; have to restart.
Click to expand...
Click to collapse
My battery is always at about 20% Will charge later and see if I can reproduce that.
Lost root.
Click to expand...
Click to collapse
Root is fine. If you have trouble, disable it in developer settings, reboot and enable again.
Updates through play store error out.
Click to expand...
Click to collapse
There is some problem with the storage path if you so a (dirty) upgrade. I haven't figure out the root cause. Affects other apps as well. You might also get the warning that some Uids are wrong and your system will be unstable.
Probably deleting data for some android system apps will solve that, but I don't have the time to try.
Do a factory reset and you'll be fine. You can restore your apps later with TitaniumBackup or Helium, but ensure that you restore the app data only on selected apps if you really need it.
linw said:
Loaded 4.3 gapps. Generally, looks good. Panorama in Camera app is great!
Problems:-
- lost root
Click to expand...
Click to collapse
See above.
- Youtube app no-go
Click to expand...
Click to collapse
Will test today.
- Google Play Music no-go
Click to expand...
Click to collapse
Weil test today.
YouTube in HQ almost no lag (tested with gangnam style and gentleman)
Play store updates are fine after wiping
No turning off at 100% charging
Everything else is so smooth thanks!!!
Sent from my GT-P7310 using xda premium
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.
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
I am new to android rom development.
My rom is using Altaf-Mahdi's source code.
There are no any errors while compiling.
After I flashed the rom and reboot, my phone stuck at boot logo almost 15 mins.
But it can boot recovery or fastboot
Is there any way to fix or get some logs?
Here is the flashable zip.
https://drive.google.com/file/d/0B_b1LHjDUqHjUUpmVmhXZDZ6Zmc/view?usp=sharing
ayackmk said:
I am new to android rom development.
My rom is using Altaf-Mahdi's source code.
There are no any errors while compiling.
After I flashed the rom and reboot, my phone stuck at boot logo almost 15 mins.
But it can boot recovery or fastboot
Is there any way to fix or get some logs?
Here is the flashable zip.
https://drive.google.com/file/d/0B_b1LHjDUqHjUUpmVmhXZDZ6Zmc/view?usp=sharing
Click to expand...
Click to collapse
Read this, you might get a hint.
http://forum.xda-developers.com/oneplus-2/general/cyanogenmod-13-android-marshmallow-t3256275
ahahahahahah not booting huh? did you add to the build this https://github.com/CyanogenMod/android_external_sony_boringssl-compat
and this https://github.com/CyanogenMod/android_external_stlport
???
manups4e said:
ahahahahahah not booting huh? did you add to the build this https://github.com/CyanogenMod/android_external_sony_boringssl-compat
and this https://github.com/CyanogenMod/android_external_stlport
???
Click to expand...
Click to collapse
Hail! :good::cyclops:
manups4e said:
ahahahahahah not booting huh? did you add to the build this [/url]https://github.com/CyanogenMod/android_external_sony_boringssl-compat[/url]
and this [/url]https://github.com/CyanogenMod/android_external_stlport[/url]
???
Click to expand...
Click to collapse
Thank s:laugh:
I have this
<project path="external/boringssl" name="CyanogenMod/android_external_boringssl" groups="pdk" />
but no android_external_stlport
is it necessary?
What is these for?
Sorry I am really new to android rom development and bad English:highfive:
((But I tried to flash boot,system,userdata in fastboot directly, It can boot.
ok so.. boringssl-compat is a must if you want to build with lollipop blobs.
external_stlport is needed to build libs for qualcomm devices.
this is what you need to put into your local_manifest.xml
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" remote="github" revision="cm-13.0" />
<project path="external/stlport" name="CyanogenMod/android_external_stlport" remote="github" revision="cm-13.0" />
manups4e said:
ok so.. boringssl-compat is a must if you want to build with lollipop blobs.
external_stlport is needed to build libs for qualcomm devices.
this is what you need to put into your local_manifest.xml
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" remote="github" revision="cm-13.0" />
<project path="external/stlport" name="CyanogenMod/android_external_stlport" remote="github" revision="cm-13.0" />
Click to expand...
Click to collapse
Thx your help:fingers-crossed:
The zip can boot now.