Develop Bugs

CyanogenMod 9 Development

I'm working on porting CM9 to HTC One X. I've made a lot of progress but there are still issues. I wanted to get the source out as soon as possible to get more people working on it.
See the wiki for more information.
Status
Working:
Radio (calls and 3G)
Audio
Hardware Acceleration
WiFi
Bluetooth
GPS
NFC
Camera
FM Radio
Echo/In call volume fixed
Wifi Tethering
Issues/TODO list:
Wifi Direct
Blank screen on rotation
Data connection occasionally fails
Camera focusing on face issue
Nightly Builds
Thanks to jangrewe for providing the nightly builds.
Downloads: http://mirror.faked.org/cm9/
Jenkins: http://faked.org/jenkins
Reporting issues
https://github.com/intermediaterepresentation/android_device_htc_endeavor/issues
Flashing ROM
Using CWM you can flash the ROM.
The kernel must be flashed manually unless you have S-OFF:
Extract the zip file.
Code:
fastboot flash boot boot.img
Building
Add the following to your .repo/local_manifest.xml:
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="github" revision="p-ics-mr1-release"/>
<project name="intermediaterepresentation/android_kernel_htc_endeavor" path="kernel/htc/endeavor" remote="github" revision="master" />
<project name="intermediaterepresentation/android_device_htc_endeavor" path="device/htc/endeavoru" remote="github" revision="master" />
Sync code.
Code:
repo sync
And compile:
Code:
add_lunch_combo cm_endeavoru-userdebug
lunch cm_endeavoru-userdebug
(cd device/htc/endeavoru && ./extract_files.sh)
make -j4 otapackage
Contributions
Please send me pull requests on GitHub if you want to contribute.
Sources
Device Configuration - https://github.com/intermediaterepresentation/android_device_htc_endeavor
Kernel - https://github.com/intermediaterepresentation/android_kernel_htc_endeavor
Change Log
5/19/2012 - Initial import of project
5/20/2012 - Bluetooth support added
5/20/2012 - GPS added
5/21/2012 - NFC added
5/28/2012 - Add build links
5/28/2012 - Auto brightness, ICS switcher for hardware key, and more (thanks gorbi) - https://github.com/intermediaterepresentation/android_device_htc_endeavor/pull/1
5/28/2012 - Camera is now working!
5/30/2012 -
akaspin - fix bug with editing custom backlight levels
tgascoigne - fix usb mass storage
gorbi - fix for chrome. system tweaks.
6/26/2012 - Update changelog and add wiki link

I guess someone from XDA (JDR0iD?) is also working on CM9 you might wanna ask them as well.

I thought its already out, but its only posted in the modaco forum
Sent from my HTC One X using Tapatalk 2

Good to see that someone who actually shares the open source work works on cm9 now! The guy over at modaco seems like a bit of a douche, cause he insist on not sharing his repo and as I think this shouldn't be supported because open source is about open source!
Keep up the work, I hope you can fix at least the heavy bugs like mobile connection so you can post a build
Sent from my HTC One X using XDA Premium HD app

Code:
error: revision refs/heads/ics in intermediaterepresentation/android_device_htc_endeavor not found
When syncing my repo.
Edit:
I fixed it by changing
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan-omapzoom" remote="github" revision="p-ics-mr1-release"/>
<project name="intermediaterepresentation/android_kernel_htc_endeavor" path="kernel/htc/endeavor" remote="github" />
<project name="intermediaterepresentation/android_device_htc_endeavor" path="device/htc/endeavor" remote="github" />
to
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan-omapzoom" remote="github" revision="p-ics-mr1-release"/>
<project name="intermediaterepresentation/android_kernel_htc_endeavor" path="kernel/htc/endeavor" remote="github" [COLOR="red"]revision="master"[/COLOR]/>
<project name="intermediaterepresentation/android_device_htc_endeavor" path="device/htc/endeavor" remote="github" [COLOR="Red"]revision="master"[/COLOR]/>
Edit 2:
Next error:
Code:
fh-mac:cm9 fh$ lunch cm_endeavor-userdebug
Looking for dependencies
Traceback (most recent call last):
File "build/tools/roomservice.py", line 150, in <module>
fetch_dependencies(repo_path)
File "build/tools/roomservice.py", line 127, in fetch_dependencies
dependencies = json.loads(dependencies_file.read())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 360, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 378, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
** Don't have a product spec for: 'cm_endeavor'
** Do you have the right repo manifest?

endursa said:
Good to see that someone who actually shares the open source work works on cm9 now! The guy over at modaco seems like a bit of a douche, cause he insist on not sharing his repo and as I think this shouldn't be supported because open source is about open source!
Keep up the work, I hope you can fix at least the heavy bugs like mobile connection so you can post a build
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
It is his choice, so get over it. Just be glad he is sharing his ROM with the community for free. He doesn't owe us anything. Seriously, you people are ungrateful brats

Sorry about that...looks like my cm.dependencies was empty. I put an empty JSON object in there and all is good. repo sync or pull the changes from android_device_htc_endeavor and lunch should work.
Edit 2:
Next error:
Code:
fh-mac:cm9 fh$ lunch cm_endeavor-userdebug
Looking for dependencies
Traceback (most recent call last):
File "build/tools/roomservice.py", line 150, in <module>
fetch_dependencies(repo_path)
File "build/tools/roomservice.py", line 127, in fetch_dependencies
dependencies = json.loads(dependencies_file.read())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 360, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 378, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
** Don't have a product spec for: 'cm_endeavor'
** Do you have the right repo manifest?
Click to expand...
Click to collapse

intrepresentation said:
Sorry about that...looks like my cm.dependencies was empty. I put an empty JSON object in there and all is good. repo sync or pull the changes from android_device_htc_endeavor and lunch should work.
Click to expand...
Click to collapse
Seems to work now, thanks!

I am so happy that you have stated this. I really miss cm9 since I sold my GN. And the nightly hours of compiling for myself... Lets hope that some geniuses will help you to get it running soon. CM9 is open and has to stay open. Otherwise he uses the wrong name for the ROM.

Next one...
Code:
fh-mac:cm9 fh$ make -j4 otapackage
============================================
<...>
============================================
build/core/base_rules.mk:166: *** hardware/ti/wlan/mac80211/config: MODULE.TARGET.ETC.wpa_supplicant.conf already defined by external/wpa_supplicant_8/wpa_supplicant. Stop.

Planet X said:
I am so happy that you have stated this. I really miss cm9 since I sold my GN. And the nightly hours of compiling for myself... Lets hope that some geniuses will help you to get it running soon. CM9 is open and has to stay open. Otherwise he uses the wrong name for the ROM.
Click to expand...
Click to collapse
exactly...same goes for other devs here as well which use normal HTC builds. they create something awesome, devs asks permission from the creators if they can use their tweaks or mods in their roms and like the divas they are most of the times they say no..so tell me what is open source then. same goes for the guy who is compiling the cm9 Trip whatever his name is...android is open. and if by doing the right procedure and giving the right credits people should be helping each other out to make the community better..not worse by acting like little divas.
@OP ask a mod if you can move this thread in development cause you guys are compiling a build from source so it makes more sense if it was there instead of general..you do not lose anything by asking.. i wish you all the best cause cm9 is by far the best ICS i tried

F4M0U569 said:
It is his choice, so get over it. Just be glad he is sharing his ROM with the community for free. He doesn't owe us anything. Seriously, you people are ungrateful brats
Click to expand...
Click to collapse
No, he doesn't owe us anything, but he has said things on the modaco thread that I dislike, whilst it is nice that he has released it to the community, he has not acknowledged that he is only modifying the work of other people, it is not just his work and so his attitude doesn't seem brilliant. He isn't selling his work, so releasing the source code wouldn't be detrimental to him and would help many people.

empyyy said:
Next one...
Code:
fh-mac:cm9 fh$ make -j4 otapackage
============================================
<...>
============================================
build/core/base_rules.mk:166: *** hardware/ti/wlan/mac80211/config: MODULE.TARGET.ETC.wpa_supplicant.conf already defined by external/wpa_supplicant_8/wpa_supplicant. Stop.
Click to expand...
Click to collapse
Let's try changing this in local_manifest.xml:
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan-omapzoom" remote="github" revision="p-ics-mr1-release"/>
to
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="github" revision="p-ics-mr1-release"/>
Remove the old one hardware/ti/wlan-omapzoom.
Code:
rm -rf hardware/ti/wlan-omapzoom
Now sync and you'll get hardware/ti/wlan updated and also I just changed something in device/htc/endeavor too.
See if that works.

intrepresentation said:
See if that works.
Click to expand...
Click to collapse
It works now and starts building, however, I'm getting the following error now:
Code:
external/zlib/x86/adler32.c: In function ‘adler32_MMX’:
external/zlib/x86/adler32.c:747: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’
external/zlib/x86/adler32.c:747: error: ‘asm’ operand has impossible constraints
make: *** [out/host/darwin-x86/obj/STATIC_LIBRARIES/libz_intermediates/adler32.o] Error 1
I think it has to do something with Mac OS...

empyyy said:
It works now and starts building, however, I'm getting the following error now:
Code:
external/zlib/x86/adler32.c: In function ‘adler32_MMX’:
external/zlib/x86/adler32.c:747: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’
external/zlib/x86/adler32.c:747: error: ‘asm’ operand has impossible constraints
make: *** [out/host/darwin-x86/obj/STATIC_LIBRARIES/libz_intermediates/adler32.o] Error 1
I think it has to do something with Mac OS...
Click to expand...
Click to collapse
Yeah it probably does. I am on Mac but I do my building on an Ubuntu VM. You can get VirtualBox for free if you need some VM software.

Hi, thanks a lot for sharing your sources!
I'm currently trying to build them, but the extract_files.sh already gives me a lot of missing objects - i'm trying to copy them off of a phone that's running an old build by TripNRaver.
here's the output: http://pastebin.com/vGS5gZq7
Is that "bad"? Should i go back to stock and try to copy them then?

cens0r said:
Hi, thanks a lot for sharing your sources!
I'm currently trying to build them, but the extract_files.sh already gives me a lot of missing objects - i'm trying to copy them off of a phone that's running an old build by TripNRaver.
here's the output: http://pastebin.com/vGS5gZq7
Is that "bad"? Should i go back to stock and try to copy them then?
Click to expand...
Click to collapse
Yeah run against stock. I may have some additional files that are not needed but run against stock to be safe.

intrepresentation said:
Yeah run against stock. I may have some additional files that are not needed but run against stock to be safe.
Click to expand...
Click to collapse
Thanks, i'll do that shortly. The compiling is running smoothly currently, good job so far!

Okay, mobile data is now working! Had to add this into build.prop:
Code:
ro.telephony.ril.v3=signalstrength,skipbrokendatacall

intrepresentation said:
Okay, mobile data is now working! Had to add this into build.prop:
Code:
ro.telephony.ril.v3=signalstrength,skipbrokendatacall
Click to expand...
Click to collapse
building now... got the proprietary files from the unbranded EU 1.29 RUU
EDIT: hitting an error:
in function wpa_driver_nl80211_ops:driver_nl80211.c(.data.rel.ro.wpa_driver_nl80211_ops+0x1c8): error: undefined reference to 'wpa_driver_nl80211_driver_cmd'
Code:
target Executable: wpa_supplicant (out/target/product/endeavor/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant)
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/endeavor/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_nl80211.o: in function wpa_driver_nl80211_ops:driver_nl80211.c(.data.rel.ro.wpa_driver_nl80211_ops+0x1c8): error: undefined reference to 'wpa_driver_nl80211_driver_cmd'
collect2: ld returned 1 exit status
make: *** [out/target/product/endeavor/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant] Error 1
make: *** Waiting for unfinished jobs....
EDIT 2:
add the following as line 57 in "device/htc/endeavor/BoardConfig.mk"
Code:
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_wl12xx
EDIT 3: built & booted! looking good for a first try!

Compiling CM 10.1 toro?

Hi, I was trying to compile CM 10.1 for toro and was following this guide http://wiki.cyanogenmod.org/w/Build_for_toro
I couldn't find extract-files.sh so I skipped it and used the blobs from https://developers.google.com/android/nexus/drivers#toro
It compiles all the way through and generates a zip file but it just causes a blank screen when it tries to boot.
Does anybody know where I can find extract-files.sh? I did repo sync a few times and even deleted my entire directory and started over. It never shows up in the directory stated in the guide.
I'm also using ubuntu 12.04

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Have you completed every step successfully before you are supposed to execute the extract-files.sh?
Also: which java version and toolchain do you use for compiling?

tbguy said:
Hi, I was trying to compile CM 10.1 for toro and was following this guide http://wiki.cyanogenmod.org/w/Build_for_toro
I couldn't find extract-files.sh so I skipped it and used the blobs from https://developers.google.com/android/nexus/drivers#toro
It compiles all the way through and generates a zip file but it just causes a blank screen when it tries to boot.
Does anybody know where I can find extract-files.sh? I did repo sync a few times and even deleted my entire directory and started over. It never shows up in the directory stated in the guide.
I'm also using ubuntu 12.04
Click to expand...
Click to collapse
you can get blob here: https://github.com/TheMuppets/proprietary_vendor_samsung

hiepgia said:
you can get blob here: https://github.com/TheMuppets/proprietary_vendor_samsung
Click to expand...
Click to collapse
If it still fails after that, just get the google android NDK and use the provided 4.6 toolchain. Also, do not use Java 7 for compiling, use Java 6 instead (oracle Java always worked good for me, dunno about openJDK).

BUMP, having the same problem with the blank screen after building. No problems with completing the guide. Everything is as it should be
just get the blank screen after the google splash.....

MaceBewley said:
BUMP, having the same problem with the blank screen after building. No problems with completing the guide. Everything is as it should be
just get the blank screen after the google splash.....
Click to expand...
Click to collapse
What Java and GCC toolchain are you using?

Java 6, not sure about the toolchain. Kinda of frustrating cause my grouper builds boot fine...

I'm also using Java 6. And when I enter "gcc --version", I get 4.6.3
I tried using the blobs from the link above and still getting the same black screen.
I had also tried manually running generate-blob-lists.sh in devices/common. it took forever but it created extract-files.sh. It didn't even compile after that so I deleted my source directory again and used the blobs from hiepgia's link.

lunch a eng build, then LOGCAT! You'll know why it's bootlooping. And you know you need to run extract-files.sh from a toro running CM right? 'make clobber', then brunch.
Sent from my Nexus

Looking at the source tree at github, I see an extract-files.sh for maguro, but, no such file exists in the toro branch.
https://github.com/CyanogenMod/android_device_samsung_maguro/tree/cm-10.1
https://github.com/CyanogenMod/android_device_samsung_toro/tree/cm-10.1
After my repo sync finishes I'm going to go thru the steps again, if there is still no extract-files.sh (which I'm sure will be the case, unless it get's generated somehow), I'll try copying the maguro one in (with requisite changes)...

crpeck said:
Looking at the source tree at github, I see an extract-files.sh for maguro, but, no such file exists in the toro branch.
*snip*
Click to expand...
Click to collapse
I assume it doesn't exist due to toro officially not being able to be above 4.1.1 with OTAs. Making CM10 and CM10.1 problematic with the older binaries...etc people potentially would be pulling from their device with the script.
https://github.com/TheMuppets <-- as mentioned previously that is what I use to get the proprietary stuff for my toro. You can make a local_manifest.xml in your .repo directory, then a repo sync with download them all for you.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_toro" path="device/samsung/toro" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" revision="cm-10.1" />
</manifest>

OH sweet - sorry I missed that before... Very nice fix..

[CM13] CM13 not building (libTimeService missing)

Hello,
I am trying to build CM13 for h815 myself, following the instructions from the CyanogenMod wiki.
When I execute brunch h815, after some time the build breaks with the message
make: *** No rule to make target 'vendor/lge/g4-common/proprietary/vendor/lib/libTimeService.so', needed by '~/android/system/out/target/product/h815/obj_arm/SHARED_LIBRARIES/libTimeService_intermediates/LINKED/libTimeService.so'. Stop.
Click to expand...
Click to collapse
I know that libTimeService was in the proprietary files list in CM12, but was removed in CM13 and is also not present on my device (I searched in each lib and lib64 folder I was able to find on the device running CM13).
Is there some option to disable libraries dependend on libTimeService being built or do I forget some other step? Obviously, it must be possible to build for h815 from source as there are nightly builds for the device, so I think there is some configuration missing on my machine, but I don't see which.
Kind regards
spainer

Did no one else have a similar problem when building for H815 yourself? Do you all have the library on your phone?
I would also be thankful for tips where to start trying to solve the problems or which components could be related to this...

you need to sync the proprietary files in vendor/lge
https://github.com/TheMuppets/proprietary_vendor_lge

This worked, thank you very much.
So, if I see it right, the build instructions in the CyanogenMod wiki are wrong I the section to extract the proprietary blobs. Instead of executing ./extract_files.sh in ~/android/system/device/lge/h815, one should
1. create a local manifest to sync vendor/lge to the repository given above and
2. execute repo sync.
When you confirm this fix for the build instructions, I can change the CyanogenMod wiki, so that others can benefit from your solution...

spainer said:
This worked, thank you very much.
When you confirm this fix for the build instructions, I can change the CyanogenMod wiki, so that others can benefit from your solution...
Click to expand...
Click to collapse
Works for me apparently. As as newbie, it's not obvious how to create the local manifest.
I went with this
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github />
</manifest>
in ".repo/local_manifests/mine.xml", leaving "roomservice.xml" alone. Not sure if that one would
be needed still.
Yours,
Kay

kayhayen said:
Works for me apparently. As as newbie, it's not obvious how to create the local manifest.
I went with this
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github />
</manifest>
in ".repo/local_manifests/mine.xml", leaving "roomservice.xml" alone. Not sure if that one would
be needed still.
Yours,
Kay
Click to expand...
Click to collapse
I ran into the same problem. I'm going to try your solution and see what happens. BTW I noticed your code has a couple of typos. This should work:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>
Thanks
---------- Post added at 08:32 AM ---------- Previous post was at 08:30 AM ----------
Also, does this mean we should throw out the proprietary blobs if we've already extracted them?

Got a successful build, gonna test it soon.

Is Anyone Building Other ROMs Not Posted?

The choice of ROMs has slowly been dipping since Lollipop as more and more ROMs no longer have Official support for Galaxy Nexus.
At the same time, newer ROMs are popping up for other devices and they look quite interesting.
Ones I have been looking at are Dirty Unicorns, Screw'd, AICP and OctOS.
However, building an unofficial ROM has been troublesome for me.
I have been focusing on Marshmallow since there are still some bugs with AOSP/Unlegacy nougat.
My main issue is that it isn't clear which gnex repos I should be adding after I have sync'd the main ROM source.
There are lots of different forks around and it isn't clear which one to choose.
Which repos do I need to add for AOSP based ROMs?
What is the recommended way to add them?
Does it make any difference if the ROM uses Cyanogenmod or Omnirom as a base instead of AOSP?
Has anyone built these (or any other ROMs) privately and would like to share all the commands necessary for a successful build?

Take a look at this backstage development
https://www.androidfilehost.com/?a=show&w=files&flid=18435
SAOSP has more nougat builds,
Then Dirty Unicorn and Pure Nexus.....
Thank him -> @voidz777

My present time is 5 o'clock in the morning.
In other words, it is before going to work.
So I can not write much.lol
Hi, opticyclic
I did not ignore you.
I have been working forever since I got your email.
Because I can not tell the right way unless I port it before telling you.
I was doing screwed work for a while.
https://github.com/voidz777-crewd
But I can not boot it.
Probably, I think it is due to more optimizing.
I got tired because I got tired.lol
After a while, delete https: //github.com/voidz777-crewd.
It is another addition.
<project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" revision="master" groups="pdk,linux,arm" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" revision="aosp-6.0" />
<project path="hardware/ti/omap4" name="android_hardware_ti_omap4" remote="unlegacy" revision="stable" groups="omap4" />
<project path="vendor/ti" name="proprietary_vendor_ti" remote="unlegacy" revision="stable" />
<project path="vendor/widevine" name="proprietary_vendor_widevine" remote="unlegacy" revision="aosp-6.0" />
I'm sorry, my English is not good.
If I could write in Japanese here, I can tell you a little more about the way of port.
There is no time now.
PS.Ah, oct could be pored immediately.

@voidz777 No apologies necessary!
Your posts about different ROMs on Google plus are actually what prompted me to try to build some myself!
Thanks for the info.
I'll post back after trying out a few different ROMs and give an update in the OP on any successes.

I tried to build octos with
Code:
repo init -u https://github.com/Team-OctOS/platform_manifest.git -b oct-mm
and this in .repo/local_manifests/roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<project remote="unlegacy" path="device/samsung/tuna" name="android_device_samsung_tuna" />
<project remote="unlegacy" path="hardware/ti/omap4" name="android_hardware_ti_omap4" revision="stable" groups="omap4" />
<project remote="unlegacy" path="vendor/samsung" name="proprietary_vendor_samsung" />
<project remote="unlegacy" path="vendor/ti" name="proprietary_vendor_ti" revision="stable" />
<project remote="unlegacy" path="vendor/widevine" name="proprietary_vendor_widevine" />
</manifest>
However, they are doing something funny with the build/envsetup.sh and it isn't picking up the vendorsetup.sh so the device isn't picked up by brunch/breakfast etc.
As far as I can tell, there is no specific info on GitHub, GooglePlus or any posts on xda on how to add a new device for their ROM.
On to AICP....

Check vendor / rom - name or device / other - device /.
If oct it will be platform_vendor_to.
Let's see the commit log.
Is there any device added?
For example, let's look for mako.
https://github.com/Team-OctOS/platform_vendor_to/commit/d30dd90c018ca521d458c939a2c56ffc5a97741d
Mako has been added by this commitment.
Create the tuna file in the same way.
Well, will you continue your way of thinking? Or do you want to know the answer quickly?

Thanks for the tip.
If they are going to use a different build structure, it should really be on the README or a FAQ somewhere.
It's bad programming practice in general to expect people to search through commit logs just to try to work out how a project works.
So instead of just adding a local manifest, OctOs requires the following:
to.dependencies (same as local manifest but in JSON instead of XML)
to.mk - same as the device board (aosp_tuna.mk)
extra line in vendorsetup_community.sh - it ignores your vendorsetup.sh
Then do lunch aosp_tuna-userdebug.
Then do mka bacon
However, the first time I did this, it overwrote my .repo/local_manifest/roomsevice.xml with a generated version that contained octos revisions instead of the aosp revisions, which obviously failed as there is no octos revision in unlegacy!
Weirdly, after reverting the roomservice.xml and running lunch again didn't overwrite it.
AICP was more straightforward.
I just added the roomservice.xml and ran lunch aosp_tuna-userdebug and mka bacon.
However, both failed with the following error:
Code:
build/core/base_rules.mk:157: *** packages/apps/Nfc//nxp/jni: MODULE.TARGET.SHARED_LIBRARIES.libnfc_jni already defined by packages/apps/Nfc/nxp/jni/. Stop.
What is weird about this is that it is the same module defining the library, however, the first one has a double slash in the path!

Probably revert this commit
https://github.com/Team-OctOS/platf...mmit/1b8ed2250fc89adce8e0b0dbb6c5ca4d82705ccb
Sent from my Nexus 5

Good catch.
I wonder how that didn't cause a build failure on the build servers.
The next failure in both was:
Code:
build/core/base_rules.mk:157: *** hardware/invensense/60xx/mlsdk: MODULE.TARGET.SHARED_LIBRARIES.libmlplatform already defined by device/samsung/tuna/libsensors. Stop.
That was resolved by removing the Cyanaogenmod project and using the unlegacy one instead, so the local manifest now looks like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Remotes -->
<remote name="unlegacy"
fetch="https://github.com/Unlegacy-Android/"
review="gerrit.unlegacy-android.cf"
revision="aosp-6.0" />
<remove-project name="CyanogenMod/android_hardware_ti_omap4" />
<remove-project name="CyanogenMod/android_hardware_invensense" />
<project name="android_device_samsung_tuna" path="device/samsung/tuna" remote="unlegacy" />
<project name="android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="unlegacy" revision="stable"/>
<project groups="omap4" name="android_hardware_ti_omap4" path="hardware/ti/omap4" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="unlegacy" />
<project name="proprietary_vendor_ti" path="vendor/ti" remote="unlegacy" revision="stable" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="unlegacy" />
</manifest>
I chose revision="stable" for android_kernel_samsung_tuna", although there is also "aosp-6.0-sound" but I just wanted any kernel to allow me to compile at this point.
The next error (both ROMs) is this (maven 3 is installed)
Code:
make: *** No rule to make target '/home/buildbot/android/aicp/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/aar/classes.jar', needed by '/home/buildbot/android/aicp/out/target/common/obj/APPS/messaging_intermediates/AndroidManifest.xml'. Stop.
This relates to this dir https://github.com/AICP/vendor_aicp/
Interestingly, ambientsdk dir existed all thoughout the n7.0 branch and only got removed recently in the n7.1 branch
https://github.com/AICP/vendor_aicp/commit/8f150895f8b361480ac91ef0ace941e06e9f548e
I also don't see any maven messages in the build log and com.cyngn.ambient/ambientsdk/ is not in my ~/.m2/repository which makes me wonder if I am missing a project.
The only similar errors I see online are if people don't have maven installed.
I tried removing the files like the 7.1 branch even though it felt wrong,
Code:
rm vendor/aicp/overlay/common/frameworks/base/core/res/res/values/cm_arrays.xml
rm -rf vendor/aicp/ambientsdk
Not surprisingly, it seems like something else is calling it as the same error pops up 25 mins into build.
repo grep ambientsdk shows ContactsCommon, Trebuchet and ContactsProvider using it in the Android.mk files and grepping for ambient shows lot of java imports.
So now I am stuck again.
To be honest, I wasn't expecting to have to deal with errors like this as they don't seem to be device specific.
i.e. there are builds for other devices so how did they compile?

i have posted nethunter rom here: https://forum.xda-developers.com/galaxy-nexus/development/rom-kali-linux-net-hunter-t3676472

Building OREO for the One M9 [booting, camera and gps broken]

Hi all,
I have been trying to boot LineageOS 15 on the One M9 as I think they have it booting on the M8.
By searching through github and looking at the M8 changes, I have managed to pull a bunch of trees together and complete a build, but it does not boot. It does not get past the bootloader to even get to the boot animation.
The roomservice.xml I am using is shown below:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_htc_himaul" path="device/htc/himaul" remote="github" revision="cm-14.1" />
<project name="me2151/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" revision="lineage-15.0" />
<project name="me2151/android_kernel_htc_msm8994" path="kernel/htc/msm8994" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.0" />
</manifest>
And I've had to change the .repo/manifest.xml a bit to include these revisions:
Code:
<project path="hardware/qcom/audio/default" name="LineageOS/android_hardware_qcom_audio" groups="qcom,qcom_audio,pdk" revision="lineage-15.0-caf-8994" />
<project path="hardware/qcom/display" name="LineageOS/android_hardware_qcom_display" groups="pdk,qcom,qcom_display" revision="lineage-15.0-caf-8994" />
<project path="hardware/qcom/media" name="LineageOS/android_hardware_qcom_media" groups="qcom,pdk" revision="lineage-15.0-caf-8994" />
I've also had to change a bunch of /vendor/cm/ to /vendor/lineage as said in this post. I might have changed some other things (I seem to remember there was an issue in framework/core/res/res/values.xml or something where some strings relating to rebooting weren't defined ...)
Anyway, any ideas as to how to proceed? None of the logs are showing any kernel activity, only when it boots into the bootloader do I get any kind of logs. I've gone through all the logs in /devlog and there's nothing =[
EDIT:
This build is currently bootlooping, but adb is working. The guide of how I got this far is in this post.
EDIT2:
This rom is currently booting, but camera is broken, selinux is in permissive, and there's probably a load of errors floating around in adb that I don't really have time to solve =[ The link for this build for LineageOS 15.0 GSM/himaul is in THIS POST.

Maybe you can post a link to the source? or the build?

lucyr03 said:
Maybe you can post a link to the source? or the build?
Click to expand...
Click to collapse
Yay, a reply!
So the sources I'm using are:
/me2151/android_device_htc_hima-common
/me2151/android_kernel_htc_msm8994
/TheMuppets/proprietary_vendor_htc
Then the normal LineageOS 15 sources, except the -caf-8994 ones for qcom_media, qcom_display, and qcom_audio.
I've noticed the generated boot.img is ~10mb smaller than the one I built from the LineageOS 14.1 sources. I'm thinking this might be the problem, but I don't hugely know where to go next. I unmkbootimg'd the boot.img, and the ramdisks are around the same size as in LOS 14.1 , but the zImage's are very different. I can upload the build if you want, but it doesn't boot or even boot the kernel in normal mode to log anything.

xangma said:
Yay, a reply!
So the sources I'm using are:
/me2151/android_device_htc_hima-common
/me2151/android_kernel_htc_msm8994
/TheMuppets/proprietary_vendor_htc
Then the normal LineageOS 15 sources, except the -caf-8994 ones for qcom_media, qcom_display, and qcom_audio.
I've noticed the generated boot.img is ~10mb smaller than the one I built from the LineageOS 14.1 sources. I'm thinking this might be the problem, but I don't hugely know where to go next. I unmkbootimg'd the boot.img, and the ramdisks are around the same size as in LOS 14.1 , but the zImage's are very different. I can upload the build if you want, but it doesn't boot or even boot the kernel in normal mode to log anything.
Click to expand...
Click to collapse
Can you post the rom or send it as pm? I want to test something if it's possible...

lucyr03 said:
Can you post the rom or send it as pm? I want to test something if it's possible...
Click to expand...
Click to collapse
Yeah no problem. I'll just try to revert some changes that didn't work before I upload (might take a few hours). I'm also going to try a clean rebuild tonight too.

xangma said:
Yeah no problem. I'll just try to revert some changes that didn't work before I upload (might take a few hours). I'm also going to try a clean rebuild tonight too.
Click to expand...
Click to collapse
Ok, let me know your progress, I want to test builds and help with what I can...
And about smaller zImage maybe it's just a compilation error or missing some things from kernel source...

lucyr03 said:
Ok, let me know your progress, I want to test builds and help with what I can...
And about smaller zImage maybe it's just a compilation error or missing some things from kernel source...
Click to expand...
Click to collapse
Yeah I'm thinking that's the case. Now I just have to learn how the kernel gets built to compare it to LOS 14.1 and the M8.
Sounds great. Here's the download link.
Though I would warn anyone downloading this - this build does not boot. I didn't do anything crazy to the code, but I'm not taking responsibility for other people using their devices to test. I haven't gone back to LOS 14.1 since this either.
With all that said, thanks for your offer to help! And thanks to anyone else that does too! Also thanks to the actual coders of the source =D
EDIT: Oh, and if for any reason I have to take this down, just let me know.

So I found a big problem and I'm rerunning the build now. I wasn't paying attention and hadn't properly updated the LineageOS device_htc_himaul branch. This meant the build was using the vendor_lineage/config/common_full_phone.mk instead of common.mk and missed a lot out.
I've made the changes locally for now while I test *crosses fingers*, then I'll eventually upload my changes to github if they work.
EDIT: I now realise that common_full_phone.mk calls common.mk eventually anyway, so I've just taken out the telephony packages. Oh well, doesn't hurt to make the problem simpler.

xangma said:
So I found a big problem and I'm rerunning the build now. I wasn't paying attention and hadn't properly updated the LineageOS device_htc_himaul branch. This meant the build was using the vendor_lineage/config/common_full_phone.mk instead of common.mk and missed a lot out.
I've made the changes locally for now while I test *crosses fingers*, then I'll eventually upload my changes to github if they work.
Click to expand...
Click to collapse
Good, I'll wait for the build.
Hope will boot

Any news?

lucyr03 said:
Any news?
Click to expand...
Click to collapse
Unfortunately it didn't boot either (nothing changed with the kernel), but I do feel I'm getting a bit closer. I found a new android_device_htc_hima-common and kernel which I'm going to try and build now.

xangma said:
Unfortunately it didn't boot either (nothing changed with the kernel), but I do feel I'm getting a bit closer. I found a new android_device_htc_hima-common and kernel which I'm going to try and build now.
Click to expand...
Click to collapse
How's with new kernel source?

lucyr03 said:
How's with new kernel source?
Click to expand...
Click to collapse
Not too good. I'm very lazy and unorganised so purged all the source and started again just to be sure about what's going into the build.
I have 'updated' the android_device_htc_himaul source to LOS15.0. When I say updated, I mean copy what I saw someone else doing for the himawl. I was using this updated version for the previous non working build, but I thought I'd share what I'd done.
Still battling to get this build completed without errors, it's at 5% at the moment and they take up to 5 hours on my PC

Woohoo! I have a bootanimation! Just waiting to see what it does next =D

Ok, amazingly adb is working, which is great news. Here's my bootloop error log.
Unfortunately, I can't work on this for a while, so I'll post up instructions of how I got where I am.
1. Install all the packages to build LineageOS as listed here and make a folder for your source and initialise the repo in that folder using 'repo init -u https://github.com/LineageOS/android.git -b lineage-15.0'
2. Run 'repo sync -c'.
3. Make a directory in the .repo folder called 'local_manifests' and add a file called 'roomservice.xml' containing this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xangma/android_device_htc_himaul" path="device/htc/himaul" remote="github" revision="lineage-15.0" />
<project name="Mirenk/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" revision="o8.0" />
<project name="Mirenk/chinomofu_kernel_m9" path="kernel/htc/msm8994" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.0" />
</manifest>
4. Force sync all these project paths by running 'repo sync --force-sync $path$'. For example for the first project it'd be 'repo sync --force-sync device/htc/himaul'
5. Comment out the 'TARGET_KERNEL_APPEND_DTB := true' line in device/htc/hima-common/BoardConfigCommon.mk
6. Make this change to hardware/qcom/audio-caf/msm8994/hal/audio_hw.c
7. Added system mount point
Code:
/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,barrier=1 wait
to this file: device/htc/hima-common/rootdir/etc/fstab.qcom
8. Run 'source build/envsetup.sh'
9. Run 'brunch lineage_himaul-eng'
10. In the created zip file, remove the assert at the top of the updater-script (spans 4 lines?) to avoid error 7 while flashing in TWRP.
That's it! That's the 10 steps you need to get to a bootlooping Oreo rom! =P
EDIT:
Looks like the error at the bottom of the logcat is looking for /system/vendor/firmware/image/keymaster.mdt when in fact it is stored at /firmware/keymaster/keymaster.mdt ...
And the mc_v2.mdt is in /system/etc/firmware/
Don't know about the others though. Maybe it'll get further into the boot if we point it to those files.
Looks like this might be a good fix ...

Can you upload the build? I don't have any good pc to build it and will take 10-12 hours I think on my pc.

Sadly not. I have no proper computer access at the moment. I'm actually now unsure the keymaster is preventing it booting as I've seen other logcats that get past this point.
I think the answer might be in /devlog but I've gone back to LOS14.1 until I can get back to this ...

xangma said:
Sadly not. I have no proper computer access at the moment. I'm actually now unsure the keymaster is preventing it booting as I've seen other logcats that get past this point.
I think the answer might be in /devlog but I've gone back to LOS14.1 until I can get back to this ...
Click to expand...
Click to collapse
Really!? My M9's logcat dosen't move from keymaster error…[emoji26]
Could you show me logcat if you still have it ?

Mirenk said:
Really!? My M9's logcat dosen't move from keymaster error…[emoji26]
Could you show me logcat if you still have it ?
Click to expand...
Click to collapse
It does after your edits! (I think). I'm just syncing your vendor/htc/ and rebuilding.
Thanks for all your work, seriously, I'm just mashing things together and fixing small problems I think I understand. I updated the proprietary-files.txt a little here: https://pastebin.com/SxSr56hi
And I also added another hidl definition in the manifest.xml so surfaceflinger would start:
Code:
<hal format="hidl">
<name>android.hardware.configstore</name>
<transport>hwbinder</transport>
<version>1.0</version>
<interface>
<name>ISurfaceFlingerConfigs</name>
<instance>default</instance>
</interface>
</hal>
EDIT: To answer your question though, the logcats I saw getting past the keymaster error were from other devices. So I thought it wouldn't be a problem. It's to do with qualcomm hardware encryption right? Always good to have that working though I guess haha =]
EDIT2: Now I'm just hoping your vendor/htc/hima-common updates will fix this error:
Code:
10-22 16:35:14.033 466 466 E QCOM PowerHAL: Unable to open prefetcher: dlopen failed: library "libqti-iop-client.so" not found
10-22 16:35:14.033 466 466 E QCOM PowerHAL: Failed to get prefetcher handle.
10-22 16:35:14.033 466 466 I QCOM PowerHAL: QCOM power HAL initing.

Ok, after installing your vendor/htc repo, the keymaster error is back. I think when using your latest device/htc/hima-common and the TheMuppets vendor/htc repo, the keymaster error went away.
I'm very confused ...
Code:
10-22 18:59:48.194 531 531 E [email protected]: Error opening keystore keymaster0 device.
10-22 18:59:48.195 531 531 E [email protected]: Could not get passthrough implementation for [email protected]::IKeymasterDevice/default.
10-22 18:59:53.194 532 532 I [email protected]: Fetching keymaster device name default
10-22 18:59:53.194 532 532 I vndksupport: sphal namespace is not configured for this process. Loading /vendor/lib64/hw/keystore.msm8994.so from the current namespace instead.
10-22 18:59:53.195 532 532 I [email protected]: Found keymaster0 module Keymaster QCOM HAL, version 3
10-22 18:59:53.195 532 532 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
10-22 18:59:53.195 532 532 D QSEECOMAPI: : App is not loaded in QSEE
10-22 18:59:53.195 532 532 E QSEECOMAPI: : Error::Cannot open the file /vendor/firmware/keymaster.mdt
10-22 18:59:53.195 532 532 E QSEECOMAPI: : Error::Loading image failed with ret = -1
This looks different now though. it was looking for them in /vendor/firmware/images before...