yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
yeah, should be roomservice. But I'm also suspecting...did you ADD to your roomservice, or did you just use

<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />
<project name="TeamChopsticks/hercskytools" path="hercskytools" remote="github" revision="master" />
<copyfile src="build.sh" dest="build.sh" />
</manifest>

as your only roomservice?

You need also:

<manifest>
<project name="CyanogenMod/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_hercules" path="device/samsung/hercules" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.2" />
</manifest>

That could be made more clear.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'd hold tight on that thought .... :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I wish I could say I am waiting patiently... but I'm trying... :) I wouldn't be surprised if official 10.2 nightlies came out before I get my ish together.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'm not saying that something is going to happen maybe today, but I'm also not saying there isn't. I guess what I'm saying is exactly what I just said if you catch my drift.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Snoop05:
Okay than tell me how to make skyrocket perform at least so good as device with 2x slower hardware.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Linero is not going to give you a massive boost in performance that you truly notice. There are some advantages and some disadvantages to both toolchains. You really need to know how the assembly piece of compiling works to understand the major differences.

Bottom line, if you get linero to work - good for you. But there are some really deep differences that may cause you odd issues down the road unless you update your code and makefiles appropriately.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] holeindalip:
I'm leaning towards you guys because you are the developers, but why does almost everybody in the herc thread use linaro ?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Honestly, the primary reason people do it is to take advantage of using a newer compiler toolchain (and to simply make a change for sake of making changes). The newer versions enforce stricter programming rules, which is actually a good thing. It makes you write cleaner code as a result. It's the under the covers stuff that I don't think a lot of people really understand and that's where you can get into trouble. I certainly don't understand all of it myself, so I stick with the version that Google uses for each version of android to ensure compatibility and not introduce problems because of the build.

Pretty much this .. if you can get a dev to explain exactly what the advantage of them changing the toolchain is, and exactly why - with proof, then you have a good developer. But I doubt very many people can give you a real solid answer on why they changed it and what the specific, measured and documented advantages are.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
On mako I've used 4.4.3, Google's 4.6, Google 4.7 Linaro 4.7 and Linaro 4.8 and I've never seen any difference in performance. The most performance difference seen, and honestly almost none on mako but noticeable (felt more difference on cappy) was -O3 flags vs - O2 or -Os. I use Linaro just to say I use it and people tend to prefer it. This has been my experience at least.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] holeindalip:
Are we getting a newer tool chain than the 4.6 that was used in 4.2.2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
We are using Google's 4.7 toolchain for 10.2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Since no one here has that phone and not very many projects have the huawei device trees for it, it would help if you stated which ROM you are building and provide a link to the repos for the device trees you're using. I'm guessing your device trees (specifically the device/huawei/msm7x30-common) is not up to date for cm-10.2/Android 4.3.

---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------

So, what you're saying is, placebo (and some flashaholic n00bs fall for it).

:p

---------- Post added at 01:54 PM ---------- Previous post was at 01:50 PM ----------

Do you work for JP Morgan ? :laugh:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I'd never not always ask for an ETA, I wouldn't never do that sometimes. I'm not even sure what I just said, but you can catch my drift... :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jobankler:
Any updates on 10,2? Heard sound was fixed, so what other bugs we have left now?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
No, you said it, not me!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Snoop05:
i didn't said that Linaro will double the performance, but it can a part ... and ... its not linaro like linaro ... also depend how you set it up.

Don't be a hater dude :good:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Can someone translate this to English?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] AndroidGee209:
Dude, its not Linaro like Linaro. . .
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Error....

Here are the lines. Does it mean a "/" when it says separator?

LOCAL_MODULE:= libdashplayer

LOCAL_MODULE_TAGS := eng

include $(BUILD_SHARED_LIBRARY)

[COLOR=Red]<<<<<<< HEAD[/COLOR] [COLOR=SeaGreen](line 56)[/COLOR]

#endif
=======
>>>>>>> 0b66c18... DashPlayer: make jb_mr2 compatible
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
did you edit the file? Missing separator normally means there is white space instead of a tab.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ya I did. But just because of the error. I read it could mean a missing ":" or spaces where there should be a tab. I removed the whole line with <<<<<HEAD. You answered so fast I can't tell if that was bad or not...lol

I'm also getting about 200 lines worth of error on this....Bahhh! lol

This is on cm10.2....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
I just did a fresh sync and started a build of 10.2, we will see how mine goes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
It did the same thing to me earlier I had to remove two of the commits I think they were already merged try just running the celox sh when I did that it showed me the ones I needed to take out
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
on my latest sync, that file isn't even 56 lines now to error out there. So I just recommend a resync and try again. Also latest cm-10.2-celox.sh is up to date on cherry picks, nothing to edit.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Really? Cuz I find at least 2 in that cm-10.2-celox.sh that fail.

I'll keep trying...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
We are rebasing the kernel ... again ...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
they must have been merged within the last hour then (lord knows CM10.2 is flying, it's possible.) But when I started this build it didn't die on any commits
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'll be updating tools in a few minutes ... lots of movement tonight in all the projects.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hahaha weeeee! lol

That said, by kernel you mean the strait CM 10.2 branch?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
I just double checked, nothing in the current 10.2 celox is merged. Maybe try deleting your hercskytools directory and resyncing. Almost sounds like yours is not getting updated for some reason. (Possible if you told it to ignore it because of your changes)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Tools is clean, no updates needed.

As far as kernel goes, check CM github for the next branch. That's what we are testing now and that will merge into 10.2 when ready.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
What is current known issues with 10.2-new compared to 10.2?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ya, this is the strat of my probs. Everytime I try to get around this here, everything goes sideways with omx_vdec

EDIT: I just did a freshy fresh... deleted tools resynced then

Should I just wait for the kernel rebase?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Delete your frameworks directory and resync it, you have something wrong with your repos if tools is failing. Either local changes, or you aren't in sync with git.

Also, I'm likely going to be posting a lot less going forward on the forums. I am always on IRC though, so you can ping me there if you want a faster response on things.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
what was the error?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Sorry, I hit post before pasting it

---------- Post added at 12:41 AM ---------- Previous post was at 12:11 AM ----------

Ya, I don't really get it. I deleted from both projects and build dir kernel, frameworks, hardware, tools, device. resynced. applied tools and these three fail.

If in doubt,.......wait. lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
never mind.http://d-h.st/1Yw
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Deleted.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Rpr69 - sent u a message, we are not ok with unofficial nightlies. I explained to you guys how tools works so you can have personal builds fpr testing. Releasing nightlies or ROMs before we have gone official is not good man ...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bps119:
[MENTION=4685003]car vs driver[/MENTION] did you remove you r upload of 4.3 gapps? The link posted in this thread a few days ago with your test build had disappeared
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kaymmm:
wanted to say thanks in here to everyone for all of the support they've provided in helping me to get builds for my skyrocket.

i just picked up an lg ogp and will be moving over there, and hopefully building roms in the near future. but this thread has been a great resource, so thanks again!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I could use some help with this one...I have searched cm gerrit and don't see anything??I also looked for -Werror in the bmp180.c file and the make files, and there's nothing there. I still have not had a clean build yet??

/home/patchadams/bS43/kernel/samsung/msm8660-common/drivers/input/misc/bmp180.c:308:36: error: 'raw_pressure' may be used uninitialized in this function [-Werror=maybe-uninitialized]

/home/patchadams/bS43/kernel/samsung/msm8660-common/drivers/input/misc/bmp180.c:276:25: error: 'raw_temperature' may be used uninitialized in this function [-Werror=maybe-uninitialized]

cc1: all warnings being treated as errors

make[5]: *** [drivers/input/misc/bmp180.o] Error 1

make[4]: *** [drivers/input/misc] Error 2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Open kernel/samsung/msm8660 common even open the makefile and search werror
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Or .. better yet ... open the bmp180.c file and fix the error. It's telling you that you have uninitialized variables, just initialize them in the code and rebuild.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Should be coming soon!! The only bug I have found so far is with Focal. Aosp camera works great as long as Focal hasn't crashed.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] AndroidGee209:
Yeah I noticed that if focal FCs then you have to reboot to fix either camera.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Snoop05:
View attachment 2180739

CM 10.2 built without problems, but when i want sync repo again i got this

xxx@xxx:/media/xxx/WORK/cm-10.2$ repo sync
[COLOR="Red"]error: .repo/manifests/: contains uncommitted changes[/COLOR]

edit: gapps
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Got tools to finish finally. Then I get this one. Guess it's new?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Is that regarding "CM10.2" only? What about other derivatives?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I haven't been able to get a build since yesterday, it keeps failing here:

hardware/qcom/display-caf/libhwcomposer/hwc_utils.cpp: In function 'int qhwc::hwc_sync(hwc_context_t*, hwc_display_contents_1_t*, int, int)':
hardware/qcom/display-caf/libhwcomposer/hwc_utils.cpp:749:10: error: 'struct mdp_buf_sync' has no member named 'retire_fen_fd'
make: *** [/recordings/cm-10.2/out/target/product/skyrocket/obj/SHARED_LIBRARIES/hwcomposer.msm8660_intermediates/hwc_utils.o] Error 1

Any thoughts? It's strange because the hwc_utils files have not changed since the 7th, and there are no cherry picks affecting it. On the surface, it doesn't seem to make sense.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
I would imagine it technically applies to cm but since you are using the exact same device tree it would probably be kind to respect the wishes of tc and hold off until they deem the code ready for public use.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Thanks.

The key reason here is that we want to make sure that when it goes public for the SR and Herc, it is a good experience for all the users. No critical issues, etc. We have been working very hard for the past month to achieve that, it hasn't been easy, believe me. I will say that we are close, very close to publishing something for the community.

For those that cannot run their own builds, this is really critical. For those that can, well you guys know that you're always on your own :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
You might be missing this:

http://review.cyanogenmod.org/47492
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] holeindalip:
Sorry to burst your bubble, but there has been an unofficial cm 10.2 thread/builds in the Hercules forums for over a week
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
So that makes it OK? God forbid we have some respect and standards, I know it's such a strange and foreign concept.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
We're aware of that. It's good to see that people know how to use our work to publish their own stuff and take credit without even asking if it's OK.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] holeindalip:
I'm not saying its OK, but you guys don't want any builds posted because you want a great product. I was just letting you guys know....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
It's in the Team Chopsticks celox script, so I doubt it. Just triead another build which failed, but you may be on to something. I've removed it from the celox and trying a rebuild.

...and that seems to have done it, the build finished and flashed fine. Maybe 47492 has some dependencies?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Cool, that's the way I feel too. The reason I asked is because on other devices around xda, they definitely do not feel that way. In fact, I am getting pressure to get Beanstalk 4.3.00 out.

Quote:

Me.

Original developer.

I guess he feels that he has put a ton of work into it as well. I will hold off for now. I have had now a good solid build and have been running it for 12 hours. I also have a bunch of volunteers (Unsolicited) lined up for testing.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I've been following this conversation and just wonder how it applies to the I717? For instance, I know CM does not have an official release for the Note. And I also don't know what TeamChopsticks affiliation with the note either?

God forbid I get a 4.3 build to complete....but what would I wait for to release my beanStalk as 4.3 and whose permissions? I know the rom creator has released his 4.3 version.

Anyway, I am all about thanking the right people and getting the right permissions, so I would like to understand all this more. And thanks.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Well I guess it really doesn't apply if you don't have an official device maintainer for your phone/tablet. It's really up to cyanogen himself at that point, and I'm sure he probably doesn't mind. Really, if there's no official maintainers (other than cyanogen himself), you may be good to go there just credit Cyanogen in your thread and such ...

It really applies to the devices with official maintainers. It's really just a respect thing for those developers to at least ask before posting something up before they do. After nightlies start, it's really fair game at that point as long as proper credit is given in the threads.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I remember asking awhile back about Marla-Moretz/CM10.2 compatibility. You said that they should be at the time. Testing the stock kernel, it seems better then I thought it would be but falls short under load or feature rich apps like games. Can I go ahead and compile with your kernels?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Absolutely ... although, we're moving up to 3.0.89 for CM10.2 and there are tons of KGSL changes among other things in the 10.2 version. So i'm not so sure how compatible it will be at this point.

In the very least, I'd fork my kernel into your own repo - revert the BLN changes because they're f**ked and then start merging in changes from 10.2 to bring it up to speed.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
My build last night failed, but I see there was a ton of stuff merged, so there were likely many conflicts. I tried to restart another build this morning but I think I just missed the TC repo update, and I had to leave. I'm hopeful for tonight though, looks like we are close to official!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Guys, please stop flashing 10.2 builds. Theres a major bug causing file system corruption and possible bricks. I'll keep this thread updated accordingly.

You've been warned.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Now you tell me. I've been going nuts. Video is way out of wack. No brick but trouble for sure. What version of recovery is this tested on and don't say twerp
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I dont have the details yet, just want to get some notice out for you. I'll be back online this evening, hopefully with more information.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I know tools went sideways last night. I've been learning what "Broken pipe" means

Applying change number 47297 ...
WARNING: Skipping 47297 since there is no project directory for: CyanogenMod/android_frameworks_av
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_av refs/changes/97/47297/2 && git format-patch -1 --stdout FETCH_HEAD

Traceback (most recent call last):
File "/home/wantowan2/bs2/.repo/repo/main.py", line 414, in <module>
_Main(sys.argv[1:])
File "/home/wantowan2/bs2/.repo/repo/main.py", line 390, in _Main
result = repo._Run(argv) or 0
File "/home/wantowan2/bs2/.repo/repo/main.py", line 138, in _Run
result = cmd.Execute(copts, cargs)
File "/home/wantowan2/bs2/.repo/repo/subcmds/info.py", line 68, in Execute
wantowan2@wantowan2:~/bs2$ self.printDiffInfo(args)
File "/home/wantowan2/bs2/.repo/repo/subcmds/info.py", line 88, in printDiffInfo
self.headtext(p.worktree)
File "/home/wantowan2/bs2/.repo/repo/color.py", line 126, in f
s._out.write(c(fmt, *args))
IOError: [Errno 32] Broken pipe
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I thought my build environment got borked somehow last night, glad it's not just me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I finally got a build completed! And wanted to thank everyone here who has put up with me and my rookie questions!! I really appreciate the learning over the last week that I've done in this forum :good:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Ok, here's the detail so far ...

First, you need to be using the CM10.2 branch on the kernel now. Steve merged the next branch over late last night.

Second, the corruption bug. Not sure what's causing it yet, but here's what happens ... your first flash will go fine, apps will install, everything works. Any subsequent reboot after the first, the device will either not reboot or will eventually after 5-15 minutes boot up. The problem is a file system corruption that occurs on /data when the device shuts down (or boots) - now we aren't sure the exact cause yet, but are working on a couple possibilities.

So far, no bricks have been reported that I am aware of, but file system corruption is not something you want to take a chance on because it can cause hard bricking.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Crackmaggot:
Thanks for the heads up. Curious to see when the bug was introduced so I know if Rogers Carbon build is affected. No issues so far.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] desalesouche:
hi here my last error compiling beanstalk 4.2.2 for huawei u8800pro

device tree here https://github.com/Herna-u880pro?tab=repositories

http://pastebin.com/73Qdnv5V

any help please?

thank you...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
This sounds like something plaguing t0lte devices (t0lte,t0ltetmo and t0lteatt) it's rare though, about 30 total downloads 2 reports both of which with early build #. Not sure what's causing it though.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Was there any change, even slight, in partition sizes? updater-script? I asked before, what recovery has 10.2 been tested on? The error happens before shutdown on reboot shut down. I was getting a weird wobble in animation opening closing screens.

My first build is close to perfect (Sun.,11th,08:14:03am) . Whatever changed was yesterday afternoon/evening.

If somebody has an SR that isn't there primary device. A log would be good.

---------- Post added at 10:00 PM ---------- Previous post was at 09:54 PM ----------

What? You? I thought you would have received 30 logcats by now....lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Problem is boot loop shows error bit hard to get a error of it corrupting it lol.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
That part true but there were all sorts of obvious other probs. like this warbly screen glitch
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
So far my build from about 7pm EST last night has been running fantastic. No reboot or lock screen issues yet. Although on my way to work this morning I was having issues connecting to the bluetooth in my car.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
My build from around 11 last night has been working well also, no bluetooth issues for me. Honestly, I have not noticed any issues since the audio was fixed a few days ago.