yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] sparksco:
Dude seriously read a few pages back at least!
[HTC Sensation] BurnRubber90:
EDIT: I Didn't see your last post. ....
[HTC Sensation] sparksco:
If you can't even read a few pages back why you expect people to help you? :confused:
[HTC Sensation] BurnRubber90:
NVM...

10 chars
[HTC Sensation] rawdealer:
Jp I see this, but why this wasn't downloaded? What should I enter in terminal?
[HTC Sensation] sparksco:
Like I said it's Vorbeth's repo source ask him why.
[HTC Sensation] BurnRubber90:
Sorry for posting twice the same.. i didn't noticed your last post :)

You think you can point me the fix/info? I Can't find it :(
[HTC Sensation] sparksco:
No I can't teach people how to read a few pages back sorry.
[HTC Sensation] BurnRubber90:
Thanks for the help...

I Think i found it.. is it this? http://xdaforums.com/showpost.php?p=22766877&postcount=120
[HTC Sensation] seadersn:
http vs git...
[HTC Sensation] BurnRubber90:
? I'm confused :o :confused:
[HTC Sensation] rawdealer:
http://xdaforums.com/showpost.php?p=23058103&postcount=341

http://xdaforums.com/showpost.php?p=23057778&postcount=340
[HTC Sensation] BurnRubber90:
Thanks a lot! Now syncing!
[HTC Sensation] blahbl4hblah:
I guess everyone is still having issues with downloading repo. It's not all that hard as the guide is complete if the repo lags a little just so repo sync -f and it'll force the repo sync. No need to be change the default.xml.

If you don't know how to change the default.xml then don't mess with it. If you do then you have a better chance having to redownload the entire source all over again

On another note, cyanogenmod does not merge things if they are broken they make sure everything works before hand
[HTC Sensation] Vorbeth:
The http issue with github & also the broken vendor/qcom repo's say otherwise :P

Anyhow as OpenSensation now requires changes outside the device tree I have finally setup a repo to pull from.

Can you please update your guide accordingly

repo init -u git://github.com/OpenSensation/android.git -b ics

Also local manifest is not requited using the above repo as the device & vendor tree's are included for HTC Sensation.
[HTC Sensation] sparksco:
Well seeing how you said your repo was having issues compiling a build maybe some people should test it out before updating the guide first...
[HTC Sensation] blahbl4hblah:
Quite strange seeing as I don't need to change anything to have a complete repo sync
[HTC Sensation] Vorbeth:
Feel free to test it.

I am running a clean build from it now.

---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------

Yeah, it's not effecting everyone, but enough for it to be noted as a possible issue.
[HTC Sensation] blahbl4hblah:
Well if there's more success ill add it
[HTC Sensation] Vorbeth:
The repo I submitted above has been dropped back to use the git protocol and also only 2 threads at a time.

I can only assume that the issue is more related to trying to do 4 http requests in sync and those on slower connections are suffering time out's.

I have resolved the build issues I was having so if you would like to test the above repo and it succeeds for you it should help simplify the guide.

I am also compiling using GCC 4.6 without issue too, using

mka bacon
[HTC Sensation] blahbl4hblah:
Again, 4.4 is recommended so unless I see cyanogenmod recommend other wise ill keep it my guide the same.

Thanks for the feedback though
[HTC Sensation] gbzbar:
Nevermind.
[HTC Sensation] blahbl4hblah:
Upon further research, no longer need GCC 4.4. Feel free to use GCC 4.6

I have also changed this in the OP of the guide
[HTC Sensation] matt95:
in the step 4a when i type this command:

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

i get that curl is not installed...
[HTC Sensation] n1kon:
Isn't linux mint a kang of ubuntu? I'm more of an openSUSE man. Used it for years. Seems to provide a bit more power imo.
[HTC Sensation] blahbl4hblah:
You didn't install the required software in the very beginning of the guide.

Required Software to Install:

For 32-bit and 64-bit System

sudo apt-get install git-core gnupg flex bison python rar original-awk gawk 7za gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool

For 64-bit System

sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-multilib g++-multilib

Other Required Software:

sudo apt-get install libc6-dev ia32-libs x11proto-core-dev libx11-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils

Install GCC 4.4 (ICS requires GCC 4.4 instead of GCC 4.6)

sudo apt-get install gcc-4.4 g++-4.4 g++-4.4-multilib gcc-4.4-multilib

Link libx11

sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
[HTC Sensation] sparksco:
If you keep getting that error it means just that...You don't have curl installed on your machine which seems odd because I'm pretty sure Ubuntu comes with it pre-installed. Anyways try this, pic attached below.

$ sudo apt-get install curl
[HTC Sensation] matt95:
i did all of the steps man...now i'll try again
[HTC Sensation] sparksco:
Sometimes a simple reboot can fix the strangest issues
[HTC Sensation] matt95:
i have solved the previous problem but now i got a new one :(

step 4 when i type: repo init -u git://github.com/CyanogenMod/android.git -b ics

i get: Traceback (most recent call last):

File "/home/matt95/bin/repo", line 690, in <module>

main(sys.argv[1:])

File "/home/matt95/bin/repo", line 657, in main

_Init(args)

File "/home/matt95/bin/repo", line 189, in _Init

_CheckGitVersion()

File "/home/matt95/bin/repo", line 214, in _CheckGitVersion

proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)

File "/usr/lib/python2.7/subprocess.py", line 679, in __init__

errread, errwrite)

File "/usr/lib/python2.7/subprocess.py", line 1239, in _execute_child

raise child_exception

OSError: [Errno 2] No such file or directory

today isn't a good day at all :)
[HTC Sensation] sparksco:
Post a screenshot of the error and what type of linux your using
[HTC Sensation] arip:
Thanks for this. A few suggestions:

You shouldn't need to install the browser plugin for any of the compilation process.

This is definitely overkill and will probably break something if you remove stuff from /usr/lib/jvm without going through your package manager. Exporting JAVA_HOME should be sufficient, but if it's not, then either "sudo update-java-alternatives -s java-6-sun" or "apt-get purge" the openjdk packages.

A whole reboot shouldn't be necessary here. If this is just to reload the bash configuration from scratch, run "exec bash", and you should probably just do that after finishing all the bashrc edits.

There should be a slash before home here; or, to save on typing, replace /home/YOUR_USERNAME with $HOME.

Should this say elelinux or OpenSensation?

Setting CCOMPILE like this doesn't appear to be doing anything, since CROSS_COMPILE isn't set first, and CCOMPILE isn't used by anything else.
[HTC Sensation] blahbl4hblah:
Java doesn't cause any issues even if I have the java plugin so that's fine.

How is removing openjdk overkill? I've been doing it this way for a long time now and I never once had an issue as long as you delete the right folders your fine. Putting java home is NOT enough since it will give the icetea version which ISNT what we need.

I'll include that exec bash in the OP

Yes it should have a slash before hand, I did this kind of late so I didn't really focus on small typos.

Either elelinux or OpenSensation will be fine.

As for the toolchain path its been working fine for me.

What I say is this if it doesn't cause issues then don't mess with it.
[HTC Sensation] xXkingsromXx:
need help manifest not in repo help with where repo is bam im ready to compile

Which would you like? [full-eng] 18. cm_pyramid-userdebug

build/core/product_config.mk:209: *** No matches for product "18.". Stop.

Traceback (most recent call last):

File "build/tools/roomservice.py", line 9, in <module>

device = product[product.index("_") + 1:]

ValueError: substring not found

build/core/product_config.mk:209: *** No matches for product "18.". Stop.

** Don't have a product spec for: '18. cm_pyramid'

** Do you have the right repo manifest?

xxkingsromxx@xxkingsromxx-Inspiron-One-19T:~/android/system$

thanks!
[HTC Sensation] blahbl4hblah:
Go into android/system and do ctrl h. It will show you repo folder put the local_manifest.xml in there

And you shouldn't mess with manifest.xml at all. I didn't do anything to that file that gives an error and mine compiles. Did you add the fix if your compiling? Cause that may be why
[HTC Sensation] drewtang:
error

so I'm a total noob when it comes to this stuff, just to preface. When i get to the step ". build/envsetup.sh" i get the error "bash: build/envsetup.sh: No such file or directory" where am I going wrong?
[HTC Sensation] blahbl4hblah:
You have to cd ~/android/system

Then do this

. build/envsetup.sh

Yes there's a space before build
[HTC Sensation] sparksco:
This is good if you completely remove open jdk/jre using synaptic package manager which is what I did.

AAMOF I removed it with synaptic package manager and it didn't break anything at all lol. Exporting java home didn't do it for me though.

$ ~/.bashrc

I never use /home/username, "~/" does the same thing.

All good sugestions though thanks for pointing these out.
[HTC Sensation] drewtang:
Still getting the same error...
[HTC Sensation] blahbl4hblah:
Did you download source? Cause that's the only reason for why it could not be there.
[HTC Sensation] sparksco:
Did you look in the android/system/build folder to make sure the envsetup.sh file is there? Start in your home folder and find the android folder, then system folder ect in a file browser. For some reason it's not finding the file lol.
[HTC Sensation] drewtang:
well, that explains it, build folder was empty lol. Gonna start over.
[HTC Sensation] blahbl4hblah:
Be sure to go step by step and try not to skip any steps.
[HTC Sensation] mpmilestogo:
Hi. I was successful compiling a new build using the new repo source. I chose to start from scratch with the new repo. I think personally the HOWTO would be simpler without the local manifests file. My build is now running on my Sensation with no problems.

I recommend changing the HOWTO in the OP and remove the need for the local manifest file.

Thanks!
[HTC Sensation] blahbl4hblah:
Still not enough to change it.

If I don't have issues, I will not change it.

I have fixed the issue which pertains to the repo sync error in the very beginning.

It was simply in the wrong order.

With this I will not remove the local_manifest file.

CyanogenMod's android repo is good enough and won't run into any issues
[HTC Sensation] seadersn:
they're merging a lot of ics stuff atm ;)
[HTC Sensation] Vorbeth:
Well, as I said OpenSensation now requires changes to be made outside of the device tree, it now also requires changes to frameworks/base hardware/qcom and 2 additional repo's not yet available using cm's repo.

These are to enable HW Acceleration correctly and also to build the OMX libs.

Hence the need for OpenSensation to have it's own repo.
[HTC Sensation] blahbl4hblah:
If that's the case, why not try to add it to source?

And it's actually pretty easy to merge different sources that aren't merged yet or your own changes ;)
[HTC Sensation] blahbl4hblah:
Saw all of the changes, thank god no more patching for facebook and headset :P
[HTC Sensation] Vorbeth:
There is currently a discussion going on as to who's qcom patches to use, 2 sets have been submitted already, both using different file locations.

Also as I said OpenSensation now uses vendor/qcom, this requires 3 gerrit submissions that are awaiting approval, plus edit's that are not in gerrit.

Until CM decide what method they are going to use for qcom/omx I would prefer not to submit patches to gerrit.
[HTC Sensation] blahbl4hblah:
Why not just submit it? I mean the worst thing they can do is deny it so why not just take the chance. If it's already on github might as well submit it
[HTC Sensation] Vorbeth:
I give up.

Good luck supporting this guide.

I gave you info needed for OpenSensation to compile, use it or don't.
[HTC Sensation] sparksco:
You really should just submit your stuff to gerrit if there's issues instead of bickering here. USE THE ISSUE TRACKER ON GERRIT IT'S THERE FOR A REASON
[HTC Sensation] Vorbeth:
I AM NOT BICKERING, No wonder no one ever shares code!!

There is NO POINT in pushing fixes to gerrit, they are currently SPECIFIC to the pyramid and UNTIL Cyanogen get the qcom/omx code merged that is ALREADY submitted OpenSensation will NOT build using your current guide.

Stop treating me like a thick c**t, I will NOT flood gerrit with duplicate patches.

This guide is based using my OpenSensation git repo's. I am telling you what is NEEDED to get those repo's to compile to a working state.

I am now putting both you and blahbl4hblah on my ignore list.
[HTC Sensation] seadersn:
nothing to do with his stuff? don't know, it's just a duplicate line in Settings/....../strings.xml. just delete this line and done.

or just repo sync; it's fixed 3hours before. https://github.com/CyanogenMod/andr...a71254b063537e4ae122e903b8a2d215fa0d0c#diff-3
[HTC Sensation] blahbl4hblah:
I don't even believe anyone here is bickering at all, all I said was submit your code but if it's already there you could just give the link to the submitted code on gerrit so we can see the difference between the one that is submitted and the one that you have on github.
[HTC Sensation] blahbl4hblah:
Thanks for the link but I don't believe that's the right one pertaining to hw acceleration
[HTC Sensation] gbzbar:
I can kind of understand Vorbeth's point... he's not talking about a single commit or several commits, he's talking about two complete repos that are needed to make the changes he's been making work. All he's asking is that you include those two repos in the guide showing people how go compile his build, since they are needed.

If you want to make the guide "how to compile CM9", then you can leave it as is, and use CM manifests for everything, and all is well. But if you make the guide specific on how to compile Vorbeth's build, then you should include the repos that Vorbeth recommends. Its not really fair to him for you to pick and choose what you think is important or not with his build. It really should be one or the other.

....Just trying to help clarify. :)
[HTC Sensation] blahbl4hblah:
I do understand that in order see to get a functioning rom that I need to add his repos but my point is I don't have to since you can simply merge it with a simple command in terminal to merge his changes to the actual certain cyanogenmod repos. You could say that it takes more time to do since you have to clone the repo of your fork but it makes sure that you are always updated with everything that is merged to cyanogenmod source.

In point, I may be wrong as I have not looked at Vorbeth's github but if you wish to compile your own build with the most up to date source from both cyanogenmod and Vorbeth's github you don't necessarily need to use his source as the main source but a fork of his that is git cloned which is linked to a certain cyanogenmod repo. In doing this you get from a specific vorbeth repo and getting updates from cyanogenmod repo.

As for me I would rather just use this method since I don't have to wait for vorbeth to merge things which takes more time since you have to wait for him to merge things that have already been merged to cyanogenmod source
[HTC Sensation] blahbl4hblah:
I will add how to do this later today as I have school right now
[HTC Sensation] Vorbeth:
That I do understand. That's fine if you wish to do it like that.

In that case can you please update your guide to include the omx repos and how to merge, including how to resolve merge conflicts that may occur once Cyanogen start to commit more omx code.
[HTC Sensation] broncogr:
If needed, this can be further discussed by pm.

No need to spam the thread with demands and attitude towards the OP

Cheers
[HTC Sensation] sparksco:
Just a update koush was able to find a fix for repo syncing to their repos if you guys want to go back to using the old method. But you'll need to use the HTTP instead of GIT. This will also fix the repo syncing issue hanging up on 99% using -j

repo init -u https://github.com/CyanogenMod/android.git -b ics; repo sync -j1;
[HTC Sensation] superg81:
Is this still planned?
[HTC Sensation] blahbl4hblah:
Yes it is, be patient
[HTC Sensation] sparksco:
You might have to delete your entire repo source if your using a old version of repo. Download the latest version from HERE and place it in your ~/bin folder replacing your old one. Then:

chmod a+x ~/bin/repo

You'll probably want to reboot you pc if your still getting issues.

cd ~/android/system; repo init -u http://github.com/CyanogenMod/android.git -b ics; gedit .repo/local_manifest.xml; repo sync;

Add the device source tree for sensation and vendor htc to the local manifest when the file pops up in gedit.
[HTC Sensation] tangyiyong:
when I do the step:

cd ~/android/system

repo sync

I got a error:

tang@tang-hp-jstacc:~/android/system$ cd ~/android/system

tang@tang-hp-jstacc:~/android/system$ repo sync

fatal: Not a git repository: '/home/tang/android/.repo/projects/bionic.git'

Fetching projects: 12% (30/244) From git://github.com/CyanogenMod/android_external_blktrace

what's the error means?

thanks a lot!
[HTC Sensation] Jiggs82:
Hey blahbl4hblah or anyone of you guys can tell me what lines i have to put in the build prop to fix voice search? Thanks in advance
[HTC Sensation] seadersn:
pls remove the full quote of first post :)

one time your syncing went wrong, timeout or sth like that; type

rm -r /home/tang/android/.repo/projects/bionic.git

rm -r /home/tang/android/bionic

repo sync

and it should sync fresh and flawless.

is there one...? :D
[HTC Sensation] Jiggs82:
Haha i dont know someone told me i have to put edit something in the build prop , but im trying to do my own build but voice search aint working and i need it to work for an app that i use:( lol
[HTC Sensation] blahbl4hblah:
My build works, but that might just be me

That and I haven't updated in a long time
[HTC Sensation] rawdealer:
Here also :)
[HTC Sensation] Jiggs82:
Yeah I know it does work in y'all guys builds but I was bored and wanted to try to do my own with my little tweaks and stuff:D
[HTC Sensation] seadersn:
xD hmm, have to test this...?

not working on newest sources, not working on an older state of the trees. :(

did some edits, let's see...
[HTC Sensation] sparksco:
Why not lol?
[HTC Sensation] sparksco:
I'm syncing up to AOKP right now :) You have to use http with the latest "repo" script from my previous post. Download it, rename it to "repo" and put it in your bin folder.

chmod x+a ~/bin/repo

Next reboot

cd ~/android/system; rm -rf .repo; repo init -u http://github.com/CyanogenMod/android.git -b ics; gedit .repo/local_manifest.xml; repo sync -j1;
[HTC Sensation] banesi:
so is this guide outdated for OpenSensation builds?

htc@ubuntu:~/android/system$ repo sync

Fetching projects: 99% (244/246) fatal: https://github.com/OpenSensation/vendor_htc_pyramid/info/refs not found: did you run git update-server-info on the server?

fatal: https://github.com/OpenSensation/vendor_htc_pyramid/info/refs not found: did you run git update-server-info on the server?

error: Cannot fetch OpenSensation/vendor_htc_pyramid

error: Exited sync due to fetch errors

htc@ubuntu:~/android/system$
[HTC Sensation] Bastaerd:
Read the post above your post
[HTC Sensation] banesi:
Thanks, but read my post again.

Putting solutions in random posts here doesn't help much if initial post doesn't update.
[HTC Sensation] seadersn:
path is now

OpenSensation/android_vendor_htc_pyramid

no more

OpenSensation/vendor_htc_pyramid

change the corresponding xml file accordingly and it should work again.
[HTC Sensation] rawdealer:
I'm just syncing and found this between the lines....

error: The requested URL returned error: 403 while accessing https://android.googlesource.com/platform/external/liblzf/info/refs

fatal: HTTP request failed

but sync goes on....

what about this?
[HTC Sensation] blahbl4hblah:
I'll fix that right now since it's nothing too big
[HTC Sensation] superg81:
Is this working for anyone now?
[HTC Sensation] yozpalang:
Same here :confused:
[HTC Sensation] blahbl4hblah:
Could you provide me the entire error?

It'll help more
[HTC Sensation] gbzbar:
I encountered the same thing, and I fixed it by changing the https://android.googlesource.com to http://android.googlesource.com in the default.xml.

Hasn't happened since, and I sync with no problems.
[HTC Sensation] blahbl4hblah:
I will add this at the start of the guide for possible repo error fixes
[HTC Sensation] yozpalang:
is this where I have to make the change ?:confused: I can't find the default.xml
[HTC Sensation] blahbl4hblah:
No, try this:

cd ~/android/system
gedit .repo/default.xml

Just change the https to http, that should be what he means
[HTC Sensation] blahbl4hblah:
I have added a few more things to the guide,

As well as a section post for possible error fixes.
[HTC Sensation] gbzbar:
Small typo...

It's .repo/manifests/default.xml
[HTC Sensation] blahbl4hblah:
Actually yes it is a small typo, but I never changed manifests/default.xml

I actually used .repo/manifests.xml instead.

It's been working with me as of late, but the way you provided might be more stable

I just looked at both manifest.xml and default.xml, both are the same and changes done to either are saved
[HTC Sensation] gbzbar:
well, yeah, either way works, because manifests.xml looks like it's actually just a shortcut to default.xml.

But either way the typo could still have been confusing, since you wrote .repo/default.xml. Hopefully people will have enough know-how to be able to find what they are looking for. :)
[HTC Sensation] blahbl4hblah:
Yes that's true, it was a mistake on my behalf :)

I have fixed that in the OP.

It seems that Vorbeth has reverted his device tree files back from 3.30 to 3.25

Unsure why, but I have noticed this change
[HTC Sensation] yozpalang:
ashkan@lenovo:~$ gedit ~/.bashrc

ashkan@lenovo:~$ cd ~/android/system/ashkan@lenovo:~/android/system$ repo init -u git://github.com/CyanogenMod/android.git -b ics

Your Name [Ashkan]: Ashkan

Your Email [ashkan.man@live.com]:

Your identity is: Ashkan <>

is this correct [y/N]? y

repo initialized in /home/ashkan/android/system

ashkan@lenovo:~/android/system$ repo sync

fatal: Not a git repository: '/home/ashkan/android/system/.repo/projects/android.git'

Fetching projects: 60% (147/245) fatal: Not a git repository: '/home/ashkan/android/system/.repo/projects/android.git'

Fetching projects: 68% (167/245) fatal: The remote end hung up unexpectedly

Fetching projects: 99% (243/245) error: Cannot fetch CyanogenMod/android

error: Exited sync due to fetch errors

Any idea ?
[HTC Sensation] blahbl4hblah:
That's a strange error for me, did it ever happen before?

Reason why I ask is because you've downloaded most of the source already.
[HTC Sensation] sparksco:
It's because koush messed up the default.xml as Vorbeth said. Just change one simple thing where it says fetch=".." on the very top to fetch="https://github.com" and it worked fine for me.

gedit ~/android/system/.repo/manifests/default.xml; repo sync

"should" fix it...at least it fixed it for me :)
[HTC Sensation] yozpalang:
I kept trying but same results keeps going to 99% then fails :confused:

another question why do I get this

"fatal: Not a git repository: '/home/ashkan/android/system/.repo/projects/android.git' "
[HTC Sensation] yozpalang:
I'll give a try and report back
[HTC Sensation] sparksco:
Yeah my bad on the typo before where I said

gedit ~/android/system/.repo/manifest/default.xml; repo sync

manifest should be "manifests"

Edit: you guys really should try out AOKP repo I heard it has a ton more features. I have a fixed version of it on github and I can even add opensation repos to the default manifest if you want. Give me a little bit and I'll update it.