yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] scy1192:
The step with "wget http://download.oracle.com/otn/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin" isn't working. If I cat the file it downloads, it's a web page with something about an unauthorized request and accepting the license.

I just grabbed it from http://www.oracle.com/technetwork/j...ownloads-javase6-419409.html#jdk-6u45-oth-JPR

edit: also, executing the jdk binary won't seem to work without sudo

edit2: last command in step 5, you mistyped jdk1.6.0_45 as jdk1.7.0_45

edit3: curl command in step 6 is missing the android subdirectory
[HTC Rezound] drhile:
I'm making the changes now thanks! I appreciate any assistance I can get.
[HTC Rezound] _litz:
drhile - need to tweak some things ...

hybrid ion/pmem building is likely now going to be the "preferred" cm11 build for vigor

To that end, there is a new script for initializing this in the android project in the vigor github : https://raw.github.com/vigor/android/cm-11.0/initrepo_hybrid.sh

This will pull down the appropriate local_manifest.xml (customized for the ion/pmem hybrid build), then initialize the cm11 repo.

It should be pulled to wherever the source root will be, then executed.

The "new" method of doing things mounts the "android" project in /vigor of the build root, so all build scripts can be found there, then copied to hte build root for execution.

Handy scripts in the "Build Scripts" folder are :

fixrepo.sh <-- re-initializes the cm11 repo, but does NOT pull the local_manifest (use this to "reset" the source tree)

cherrypick.sh <-- can be customized for pulling cherrypicks, applying patches, etc.

make.sh <-- use for "automated" makes ... use "./make.sh clobber" for a clobber make

when builds are done with make.sh, all output is logged to "build.log", and all error msgs are logged to "build.err"

IMPORTANT ... the (ugly) new boot animation must be reverted for our vigor build to work properly. something in the new animation causes memory issues after boot. The command is simple (and it's already in the cherrypick.sh script in Build Scripts) :

pushd vendor/cm

git revert --no-edit b71b47d72b129915327f41653b06edaea5008534

popd
[HTC Rezound] Chucktr:
Just to get clear on this...

I am presuming that IF I have dir: ~/android.cm11/system with all the "grabbed" dirs under it, that would be what is being called the root and it would be where these scripts would be executed from. Including the "cherrypicks" which takes care of that animation problem??? Also it would take care of that "Metadata" problem??

Thanks,

Chuck
[HTC Rezound] _litz:
Correct ... by "build root", what we mean is the root directory for all the source code. This is whatever directory "repo init" was executed in.

In your case, that would apparently be ~/android.cm11/system.

All scripts must be executed from this directory, which means if you want to use any of the "Build Scripts" scripts, they must be copied to this location.

initrepo_hybrid.sh is the hybrid replacement for initrepo.sh.

It pulls down "local_manifest_hybrid.xml", places it in .repo/local_manifests, then changes the name to "local_manifest.xml".

With this in place, when you repo init, and repo sync, it pulls all the vigor projects in automatically.

The difference between "initrepo" and "fixrepo" is very basic ... the former initializes from scratch (or re-initializes).

the latter takes whatever repo information you currently have, resets/refreshes the source tree.
[HTC Rezound] Chucktr:
Just to be sure...

I have "cleaned out" my area. Gona go at this from a clean slate. Neo and you were responsible for getting me straight the last time and I thank you both very much. My concern is the "cherrypicks". Following the initrepo.sh... one was executed from the "build" dir and the other from "frameworks/native". Will this be required with initrepo_hybrid.sh?? -Or- are they to be executed from my ~/android.cm11/system dir??? Then after the "cherrypicks" we are to execute "make.sh" from my ~/android.cm11/system dir... correct??

Thanks,

Chuck
[HTC Rezound] _litz:
Whenever you use a cherrypick script, you always execute it from the build root.

the script is supposed to handle any directory changes to/from the target directory for you.

for instance, this particular script, you can specify a CM patch by number for cherrypicking ... e.g. getcherrypick XXXXX

(note : we don't currently have any of these, but the functionality is there)

The script will take that patch #, look it up on CM's Gerrit archive, find the latest revision, find the project folder, and then change directories to the project folder, pull/apply the cherrypick, then change back to the build root. Then move to whatever's next in the script.

The only item actually IN the cherrypick script, currently, is the code to revert the boot animation.

In this case, it changes to that particular directory, does the revert, then changes back.
[HTC Rezound] Chucktr:
It didn't work...

Once again we are having difficulties with the "cherrypicks"

$ cd ~/android.cm11/system <-- 'Build root'
$ . build/envsetup.sh
$ time ./cherrypick.sh auto | tee CherryPick-1-8-14.txt

We have the whole shebang recorded IF you would like to see it -but- we are only including the tail end in this message.

Done with 53434 (retval = 1; merged = 1)

Done with CM Cherrypicks, current result value : 1

>>> revert new boot animation
~/android.cm11/system/vendor/cm ~/android.cm11/system
[detached HEAD 8ca25d5] Revert "Bootanimation by Dima Skvarskyi"
12 files changed, 0 insertions(+), 0 deletions(-)
rewrite prebuilt/common/bootanimation/1080.zip (67%)
rewrite prebuilt/common/bootanimation/1200.zip (64%)
delete mode 100644 prebuilt/common/bootanimation/1600.zip
rewrite prebuilt/common/bootanimation/240.zip (94%)
rewrite prebuilt/common/bootanimation/320.zip (91%)
rewrite prebuilt/common/bootanimation/360.zip (90%)
rewrite prebuilt/common/bootanimation/480.zip (85%)
rewrite prebuilt/common/bootanimation/540.zip (83%)
rewrite prebuilt/common/bootanimation/600.zip (81%)
rewrite prebuilt/common/bootanimation/720.zip (78%)
rewrite prebuilt/common/bootanimation/768.zip (76%)
rewrite prebuilt/common/bootanimation/800.zip (75%)
~/android.cm11/system
>>> done; current result value : 1
Script result value : 1

real 1m42.761s
user 0m30.162s
sys 0m7.635s

Now then, according to the README, a return of '1' means an error. There are a number of (retval = 1; merged = 1) in the previous items during this execution. And this final one, which looks like the important animation change has a return value of '1'. Prior to this we had executed "initrepo_hybrid.sh"... copied the scripts to "our build root"... made them executable and then continued on. Can you see anything that is 'broke'?? We have the habit of breaking things. That is how I made my living ... testing. Cause I could seem to break things. Sorry.

Thanks,

Chuck
[HTC Rezound] _litz:
If you are building CM11 Hybrid, please comment all of the getcherrypick lines.

CM11 requires no cherrypicks. Just the single revert for the boot animation.
[HTC Rezound] Chucktr:
Oh Darn...

This is the same thing that happened the last time. We were told to use the 'initrepo.sh' and then to use the "cherrypick.sh" that was contained within it AFTER commenting everything but the 'one pick', which I believe was the METADATA problem. It didn't work. Neo finally gave directions to run two different scripts from two different directories and then everything was ok. We compiled it and got something to work on our phone.

Now we are told to use 'initrepo_hybrid.sh' and then use the 'cherrypick.sh' that it contains. Nothing was said about commenting anything out... till now. How would we know that??? -And- IF we comment out everything except it... how are we gona know that was enough... until we spend 4hrs plus or minus compiling and then finding out the script was in error??

I am not trying to be difficult... just trying to get in the correct "circle of friends" so that we can keep up-to-date on the latest changes. You mentioned something about running "cherrypick.sh check". Will that tell me what can and/or should be commented out without having to complain to you or Neo?? Would like to be able to do this without a baby sitter... if you know what I mean.

Thanks for your help,

Chuck
[HTC Rezound] _litz:
You wouldn't ... we forgot to comment those out of the cherrypick.sh script. This has now been fixed.

Sorry about that ...
[HTC Rezound] Chucktr:
Allllllrighty now ...

That's ok. A minor technicality.:o Now then, since you have "fixed it", I would be able to test the "fixrepo.sh" script by using it now and then the "new" "cherrypick.sh auto" supplied by the fix ... correct??

Thanks,

Chuck
[HTC Rezound] _litz:
yes.

presuming you "inited" with initrepo_hybrid.sh, then doing a fixrepo.sh following by "./cherrypick.sh auto" should have you all ready to build.

You can use the provided "make.sh" to do your build if you want. "./make.sh" or "./make.sh clobber"

This will run the build and capture output to build.log, and errors to build.err.
[HTC Rezound] _litz:
This makes me think that the initrepo_hybrid.sh failed to completely execute.

The error is that there is no manifest.xml in ./.repo ... that comes from the repo init command.

Can you re-run initrepo_hyrbid.sh ?
[HTC Rezound] Chucktr:
Repo ??

Sure... I'll do it now. Actually... a question first... do you desire the area to be wiped first -or- just over-write?? -But- then again... has repo changed?? Do I need -or- do you want another curl on the repo??

Thanks,

Chuck
[HTC Rezound] _litz:
You don't need to wipe anything. The repo sync will take care of that.

Please try and capture the output of initrepo_hybrid.sh if it still fails to work.

(the fact that you have no manifest.xml says something didn't work right)
[HTC Rezound] _litz:
if you look in there, it seems like the repo initialized.

You can manually check in ./.repo and ensure there is a manifest.xml.

Seems like you just happened to hit a github outage. If you check the status page referenced in your logging, there was one.
[HTC Rezound] Chucktr:
It is NOT Free Format...

Evidently there are places in these scripts that want - no they demand - a certain directory structure.

~/Android/cm11.0-rezound

IF that is not the case ... it won't work. That is all I did to 'fix' it. Renamed my dirs. Now I can get return values of '0' up and through the cherrypicks. So, this needs to be added to the initial instructions -or- someone needs to go through all the code and make changes. I do believe, that it is easier to just say, have the aforementioned directory structure and be done with it.

On to the build...:p

Thanks,

Chuck

P.S.

Sorry... IF I would have taken the time to read your README I would have known that. Apologies for wasting your time.
[HTC Rezound] Chucktr:
The Build was not successful...

Ran into a problem that I could not track down. Not even sure where else to look. the 'error' file contained this:

find: `src': No such file or directory
build/core/base_rules.mk:134: *** system/core/adb: MODULE.HOST.EXECUTABLES.adb already defined by cm11.0-rezound/core/adb. Stop.

Any ideas???

Thanks,

Chuck
[HTC Rezound] _litz:
Now that's bizarre ...

You can try doing a rm -rf on system/core and core, then re-running fixrepo.sh (to redownload those directories) in case something got mangled.

the "find 'src'" line is normal. The adb error is not.
[HTC Rezound] _litz:
Well, sure ... that's why you got the error.

any time you see the "missing manifests" error in fixrepo.sh, you can try just running it again.

All that means is that for some reason, the "repo init" command failed to execute.

Network issues often block that, just like they can cause issues in repo sync.
[HTC Rezound] Chucktr:
Preliminary success...

Don't know how those dirs got duped ... but they did. At any rate, we wiped the area, did an initrepo_hybryd.sh, then cherrypick.sh and now a make.sh -and- it is going. So, hopefully four hours, plus or minus, we will have a working system.

"repo init" failed... hmmmm I'll have to make a note of that. Thanks. I'll let you know in a few hours -but- thanks for your patience and help. IF anyone else has similar problems double check with them that they have the correct directory structure. They may be like me and don't read!!

Chuck
[HTC Rezound] _litz:
it's a matter of "what does what" ...

all repo init does, is pull down manifest.xml and start seeding the information in the .repo directory.

repo sync is what actually goes to each and every project listed in either manifest.xml or local_manifest.xml, and pulls the actual code down, project by project by project. The reason you use "-j 8" or "-j 16" is to allow it to pull multiple projects in parallel, thus speeding up the process.

Remember, manifest.xml = all of the CM projects, android OS projects, etc.

local_manifest.xml = all of the device specific stuff that makes a Rezound a Rezound (and makes android actually work on a Rezound)
[HTC Rezound] Chucktr:
Joy and disappointment...

Thanks for the above info. It helps. However, the final compiled project did NOT work properly. Most of it is ok -but- the Bluetooth operations for phone calls are the pits. Just after I got it installed I received a phone call from one of my customers. All you could tell on either end was that someone was there. Had to turn off the Bluetooth in order to complete the call. Voice communication was ok via just the phone. My Bluetooth headset is a Plantronics Pro.

Thanks,

Chuck
[HTC Rezound] _litz:
Actually,

Your build is working correctly.

BT calling is one of the known issues that is not working.

Btw, thanks for the donation!
[HTC Rezound] _litz:
FYI, if you want to re-run "fixrepo.sh", and do a new build, we think BT is fixed ...
[HTC Rezound] Chucktr:
Thanks

Ok, it will be another test of "My" setup. See IF I get that double dir again...:p Oh, and you are welcome. Thanks for your help.

Thanks,

Chuck

P.S.

Do I need to run the "cherrypick.sh" again after a "fixrepo.sh"??? OR is that conditional and how would I know??
[HTC Rezound] _litz:
Oh, you don't need to wipe.

Once things are "settled", repo will fix things for you.

wiping just wastes time re-downloading 15gb of source code.

Try changing this line in initrepo.sh and fixrepo.sh :

repo init -b cm-11.0 -u git://github.com/vigor/android.git

to

repo init -b cm-11.0 -u https://github.com/vigor/android.git

also,

In lieu of running initrepo.sh again, you can apply the following change to your local_manifest.xml file :

change

<remove-project path="packages/apps/Camera2" name="CyanogenMod/android_packages_apps_Camera2" />

<project path="packages/apps/Camera2" name="vigor/android_packages_apps_Camera2" revision="cm-11.0_hybrid" />

to

<!-- <remove-project path="packages/apps/Camera2" name="CyanogenMod/android_packages_apps_Camera2" />

<project path="packages/apps/Camera2" name="vigor/android_packages_apps_Camera2" revision="cm-11.0_hybrid" />-->
[HTC Rezound] Chucktr:
Too late...

Already wiped and redid the initrepo.sh whilst I was at church. I have performed the cherrypick and now doing the build. IF your fix was in this "load" then we'll be ok when I try the fixrepo afterwards. I'll look at the code after the build.

thanks,

Chuck
[HTC Rezound] _litz:
When you capture your logs of the initrepo or fixrepo scripts, please try this :

scripts.sh 2>&1 | tee log.txt

That'll redirect the error console to the main console, before it goes to tee and is written to the file.

Then we can see the errors in the log, too.

That manifest.xml missing thing is very strange. I use these scripts every day, and never have that issue.
[HTC Rezound] Chucktr:
Sorry...

... but the initrepo was already performed ..-unless- you are referring to my tests -after- the build. After the build I'll collect all the stuff I have saved and put them in a dir up on my web site. The text files are getting kinda large, especially the build one.

At this time I have only performed a:

time script | tee xxx.txt

on all the stuff. After the build -IF- it doesn't work on the Bluetooth, I'll try your fixes -and- use your way of recording.

Thanks,

Chuck
[HTC Rezound] _litz:
Yeah, that's what I mean ... next time it misbehaves.

Note that you don't have to do this for make.sh ... the make.sh script already captures output (and error) and does the time command.
[HTC Rezound] Chucktr:
Allllllrighty now ...

IF you will go to the following WebPage you will see the results of my testing. The file "AndroidNotes.txt" is a description of my steps. AFTER the "build" a "fixrepo.sh" --- broke.

http://www.trcompu.com/AndroidTS/

Oh yeah, I called a Non-existent number and the Bluetooth receive worked. Need to wait for others to 'rise' before I call anyone to check the send.

Take care,

Chuck
[HTC Rezound] _litz:
Chuck,

Please change the repo init line in fixrepo.sh from:

repo init -b cm-11.0 -u git://github.com/vigor/android.git

to

repo init -b cm-11.0 -u https://github.com/CyanogenMod/android.git

That should solve your issues running that script.
[HTC Rezound] _litz:
Cool!
[HTC Rezound] Chucktr:
Some git questions...

Mr or Mrs _litz,

I/we am/are trying to learn this as quick as possible -before- all of you move on. My biggest question is how the sources are coordinated. Yes, I know there are tutorials and descriptions -but- I thought a couple of questions answered could help get me started faster.

Now in working with this, we have found that the following directory structure is created:

ctaylor@dusty-tr2:~/Android
> lsd cm11.0-rezound/
abi/ CherryPick-1-11-14.txt FixRepo-1-12-14.txt libcore/ prebuilts/
android/ cherrypick.sh* FixRepo-1-14-14-2.txt libnativehelper/ sdk/
AndroidNotes.txt* cherryresult.txt FixRepo-1-14-14.txt Makefile* system/
art/ cts/ fixrepo_litz.sh* make.sh* tools/
bionic/ dalvik/ fixrepo.sh* MemNote.txt vendor/
bootable/ developers/ frameworks/ ndk/ vigor/
build/ development/ hardware/ out/
Build-1-11-14.txt device/ InitRepo-1-11-14.txt packages/
build.err docs/ initrepo_hybrid.sh* pdk/
build.log external/ kernel/ prebuilt/

Now then, how much of the above is from the CM Team and how much of it needs to be modified for the ReZound?? Is it just the "vigor" dir?? I would like to be able to do what Neo, Flyhalf and you are doing. Update the Rez to the latest CM ... on my own. Don't expect you to tell me everything, but hopefully point me in the proper directions. There is a "key" or "spark" that I am missing and once that is gained I know that I will be able to continue. You know, there is always something that all of a sudden says, "OhYeah!! That's how it works!!"

Thanks,

Chuck
[HTC Rezound] _litz:
Ahh, that's the magic of "repo" ...

Look in the .repo directory.

In there, you'll see a manifest.xml file. This contains all the projects supplied by CM.

This is generated by the repo init command, using CM's android.git file and selecting the "cm-11.0" project in the repo init command line.

e.g. : repo init -b cm-11.0 -u git://github.com/CyanogenMod/android.git

You'll also note, there is a directory called local_manifests, and inside this directory is local_manifests.xml.

This is the directory (and file) that contains all the device specific projects. In our case, everything specific to "vigor".

This is downloaded either directly by the user and placed in place, or the "initrepo.sh" script achieves the same thing via wget and some other shell commands.

e.g. : wget https://raw.github.com/vigor/android/cm-11.0/local_manifests/local_manifest_hybrid.xml

(in the case of initrepo.sh, it grabs the above file, then renames it to "local_manifest.xml")

If you have done this before the repo init command, repo will automatically grab manifest.xml, and then use BOTH manifest.xml and local_manifest.xml to download and maintain all the required projects ... both CM's and the device specific projects in local_manifest (e.g., all our vigor projects).

Now, as for the "vigor" specific items ... if you look inside the local_manifest.xml file, you'll see each project listed line by line.

"path=" tells where in the source tree the project is to be placed

"name=" is the actual name of the project (github and repo use this)

"revision=" is the branch of the project. In our case, in vigor, it's either "cm-11.0" or "cm-11.0_hyrbid".

revision merely denotes which actual "tree" of code to use. There are trees for each version of cm (9, 10, 11. etc), for instance.

- litz
[HTC Rezound] Chucktr:
I'm a little late...

Had to repair a PC ... but thanks for the info. May I use this info on one of my WebPages -with- credit to you of course. It is at:

http://www.trcompu.com/MySmartPhone/AndroidKitchen/AndroidKitchen.html

They are not finished ... but I am working on a "ReZound" site. Your info is not there yet -and- IF you have any suggestions they will be greatly appreciated.

Thanks,

Chuck
[HTC Rezound] _litz:
Sure ... or if you want, you can link directly to that post. Long as credit is given.
[HTC Rezound] Chucktr:
Thanks,,.

Thank you muchly. I will be placing it in the GtiHub section of my page. Links can go away and I try to get everything I can in my pages so they are there when I, or someone else, needs them. Your name, and the link to your post will be there. Contrary to what I said. I do include the links along "with" the info.

Look forward to conversing with you more...

Chuck

... and yes, I like the little guy with the glasses.:o
[HTC Rezound] _litz:
FYI,

something new to add to the cherrypick list ...

http://review.cyanogenmod.org/#/c/58461/
[HTC Rezound] Chucktr:
Hmmmm....

Ok now, IF I understand this correctly that new item should be in the cherrypick list that I would get with an initrepo or a fixrepo... correct?? I was just about to start a whole new build ...like I said I would when there was a change. Since Neo has produced an 01/27 build ... I assume that there is some new stuff and more than just a cherrypick. -But- cause of the "build time", I will wait for your reply on this cherrypick status.

Which brings up another point. IF you and I were not conversing ... how would I know about this latest cherrypick. I presume that we are to check the build directory to see if Neo has produced anything new. Which is what I have been doing. Is there a place to find this out?? Ah, I'll answer that myself. Probably the forum.?.?

Thanks,

Chuck
[HTC Rezound] _litz:
You add this in the cherrypick.sh script, which you run after a fixrepo.sh. There should be a commented example in there.

Just change the number to 58461 ... e.g. getcherrypick 58461

As for cherrypicks, just browse review.cyanogenmod.org

All of CM's pending changes are there.

This particular fix comes from here : http://xdaforums.com/showpost.php?p=49806666&postcount=746
[HTC Rezound] Chucktr:
Ok. I 'was' gona do the full wipe and build -but- this time I'll just try out the fixrepo way. This 'should' be faster IF it compiles like all the other 'C' programs that I have built. Should only compile the changed.

By the by... I installed Neo's 1/27 build and it was ok ... except; When entering a "name" NOT a number in the phone to get a contact I was getting numbers instead of letters. After a few deletes and retries I was able to get letters and the names. This was pretty consistent on the very first try. Later tries were sporadic. Sometimes it would work fine and sometimes I would have the number versus letter problem.

Annnnd I broke the Camera!! Was messing with the "Controls" to see what did what and it crashed. Got the message:

Unfortunately, Camera has stopped.
ok

Neither a Re-Boot NOR a Power Off Restart fixed it. Any ideas or suggestions??? I'll try again with my build and your cherrypick and let you know more about what I did to "break" it.:o

Thanks,

Chuck
[HTC Rezound] _litz:
Correct, the way this is "supposed" to work, is fixrepo updates the source.

Then you can either make or make clobber (the make.sh script takes "clobber" as an argument). Clobber rebuilds everything.

The contacts thing is likely an upstream issue with CM.

Camera ... well, it works ... there are some unsupported modes, probably.

To recover it, just go into Apps under Settings, find "Camera" under the "All" tab, force stop, and delete data.