yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] kaijura:
I synced your repo, this is gonna take a bit to learn your folder structures.

This is neat and spread out than the everything bunched together in CM I am used to! haha

getting a bootloop with those 3 pushed, unfortunately...

not sure what happened, going to restore and push one by one.

Looks like pushing over the Camera.apk (and it creates a camcorder apk? :eek:) and camerahal is fine, but if I push media_profiles I get a bootloop. must be Ice cold's setup incompatability..
[Thunderbolt Android Development] twistedumbrella:
If you're pushing it to that then yes. It works on the newest build here because of the frameworks rebuild. I just didn't have the camera.apk done when it finished.
[Thunderbolt Android Development] kaijura:
Thanks, I'll try setting up my device with your configuration (oh joy) and try a build and see if this sucker fires off.
[Thunderbolt Android Development] twistedumbrella:
It shouldn't be hard. It was designed to just throw in some proprietary files, a few device specifics, and build almost any HTC. There is always a flag for any configuration and any method that might be needed. It was focused on easy compatibility.
[Thunderbolt Android Development] kaijura:
Yep, just finished, wasn't too bad. About to start a build now. I think I got everything but don't know how to modify your build script yet, so I'll try manually making the build.
[Thunderbolt Android Development] haliwa04:
I'm lovin the dev chat guys, nice to see folks being civil on here. I check hourly, trying to learn as much as.possible.

Posted from my 1.34ghz, Infected, Themed Out, Lightningbolt.
[Thunderbolt Android Development] kaijura:
hrmph, got a weird error after finalizing the build after leaving it running.

At first it was complaining upon zipping that it was out of memory:

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space

rebooted and tried continuing the build, I get this now:

target StaticLib: busybox_prepare (out/target/product/generic/obj/STATIC_LIBRARIES/busybox_prepare_intermediates/busybox_prepare.a)
Docs droiddoc: out/target/common/docs/doc-comment-check
Checking API: checkapi-last
frameworks/base/api/15.txt:10566: error 10: Removed field android.media.CamcorderProfile.QUALITY_QVGA
frameworks/base/api/15.txt:10574: error 10: Removed field android.media.CamcorderProfile.QUALITY_TIME_LAPSE_QVGA

******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************

make: *** [out/target/common/obj/PACKAGING/checkapi-last-timestamp] Error 38
make: *** Waiting for unfinished jobs....

/home/kaijura/twisted/frameworks/base/docs/html/sdk/android-4.0.3.jd:-506: error 101: Unresolved link/see tag "android.media.CamcorderProfile#QUALITY_QVGA" in [null]
/home/kaijura/twisted/frameworks/base/docs/html/sdk/android-4.0.3.jd:-506: error 101: Unresolved link/see tag "android.media.CamcorderProfile#QUALITY_TIME_LAPSE_QVGA" in [null]

Going to make clean and see if this resolves it.
[Thunderbolt Android Development] twistedumbrella:
Yeah, I change the API. That's like a CM crime lol.
[Thunderbolt Android Development] kaijura:
Welps, wiping clean solved the tainted api problems, but seems that memory error bug came back again after starting the ota zip.

device/htc/common/releasetools.py:20: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
import sha
building image from target_files BOOT...
running: mkbootfs /tmp/targetfiles-uSyepd/BOOT/RAMDISK
running: minigzip
running: mkbootimg --kernel /tmp/targetfiles-uSyepd/BOOT/kernel --cmdline no_console_suspend=1 --base 0x4400000 --ramdisk /tmp/tmp4ziKF2 --output /tmp/tmp8EgO4w
warning: no radio image in input target_files; not flashing radio
running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running: java -Xmx512m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmprquMte out/target/product/vivo/htc_vivo-ota-eng.kaijura.zip
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:161)
at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
at java.util.zip.ZipOutputStream.write(ZipOutputStream.java:272)
at com.android.signapk.SignApk.copyFiles(SignApk.java:422)
at com.android.signapk.SignApk.main(SignApk.java:490)

ERROR: signapk.jar failed: return code 1
make: *** [out/target/product/vivo/htc_vivo-ota-eng.kaijura.zip] Error 1

Any ideas what I could try? I'll try a sync then build again.
[Thunderbolt Android Development] twistedumbrella:
Revert https://github.com/ThePlayground/android_build/commit/bd8908d8fd65d9196a658d2601ab32820c6e1029 locally.
[Thunderbolt Android Development] kaijura:
Awesome, giving it another spin. Will report back after it is done hopefully.

That was it, build went through the ota part.

Well, got stuck on making the nightly now, doh:

Optimizing PackageInstaller.apk...
Optimizing DrmProvider.apk...
Optimizing VisualizationWallpapers.apk...
MODVERSION: nightly
Zipping package...
Signing package...Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:161)
at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
at java.util.zip.ZipOutputStream.write(ZipOutputStream.java:272)
at com.android.signapk.SignApk.copyFiles(SignApk.java:422)
at com.android.signapk.SignApk.main(SignApk.java:490)

Cleaning up...
md5sum: update-cm-nightly-signed.zip: No such file or directory

Gonna look back in that common.py for more.
[Thunderbolt Android Development] twistedumbrella:
I dont keep the nightly ota part updated. There were fixes but it never got used.
[Thunderbolt Android Development] kaijura:
Sounds good, flashing anyways. Time to try out Twisted playground. ;)

---------- Post added at 01:39 PM ---------- Previous post was at 01:32 PM ----------

Nice bootscreen. Reminds me of NGE - Neon genesis evangelion.

aaand we're in.
[Thunderbolt Android Development] twistedumbrella:
I never thought of that. There is a clock like that somewhere
[Thunderbolt Android Development] kaijura:
It's been running pretty well for the past day. I'm thinking of making a release for the vivo section with your approval, of course.

I still need to figure out a couple of things, I got that red square going on again, and I must've done something wrong in the config that wifi doesn't turn on. I noticed you had a wifihw configuration for the ace, not sure how it works, though.

Uploaded my configurations if you want to have a look or add them to your repo or something:

https://github.com/kaijura/playground_android_device_htc_vivo

https://github.com/kaijura/playground_vendor_htc_vivo
[Thunderbolt Android Development] twistedumbrella:
You using wlan0 or eth0?
[Thunderbolt Android Development] kaijura:
wlan0 for us here
[Thunderbolt Android Development] twistedumbrella:
In the local common board.mk you'll need to change the first eth0 to wlan no zero, and delete the custom interface flag. Should work then.
[Thunderbolt Android Development] kaijura:
cool, got it and building now.
[Thunderbolt Android Development] kaijura:
Working awesome. Thanks for this.

I'll probably put up a thread for them in vivo and explain playground's differences. I don't expect you to provide support or builds either, so I'll try to relay what I learn of progress/fixes etc from your other various playground threads.
[Thunderbolt Android Development] speedy2782:
How will Rezound ICS release help this build?
[Thunderbolt Android Development] twistedumbrella:
It won't
[Thunderbolt Android Development] Link_of_Hyrule:
Go Twisted GO! :P
[Thunderbolt Android Development] donnyp1:
Where are the other 49,999,999 posts your talking about? Or were you just being a jerk to someone who asked a legitimate question to which the dev had already responded? That really wasnt necessary dude.
[Thunderbolt Android Development] ijeenyus:
It's not really apparent on this forum, but there's plenty on Twisted's rootzwiki thread
[Thunderbolt Android Development] twistedumbrella:
It'll keep happening until it works without it. Not much to do but keep saying no.
[Thunderbolt Android Development] donnyp1:
Well i thought the question was legitimate, and not everyone has twisteds knowledge, or their would be more deving going on. But that kind of answer is what gives xda such a bad name. Sorry twisted for taking up a few slots with comments, i just wish people would be a little more considerate of others.
[Thunderbolt Android Development] Link_of_Hyrule:
Sorry didn't mean to be a jerk I've just seen a lot of those around. We all want to have a fully working ICS and hopefully we get our own leak soon. Right now just have to keep testing Twisteds builds and get the bugs out that we can until then.
[Thunderbolt Android Development] twistedumbrella:
Least it was somewhat reasonable. Read this and where it was posted:

http://xdaforums.com/showthread.php?p=23697051
[Thunderbolt Android Development] mrkite38:
I agree that we should be kind to n00bs, but that kind of post has no place in a dev thread. What those users would realize, if they thought for two seconds, is that a dev knows about a leak or rom release waaaaaay before they do, 99% of the time. If it would help, they'd already be using it.
[Thunderbolt Android Development] Link_of_Hyrule:
Well mods can come delete the past 5 posts now I guess. Let's get back to testing the ice cream goodness :P
[Thunderbolt Android Development] jellydroid13:
hey twisted i have kinda lost all hope of ics till we get a leak but curiously how long will it take once we get one? is it the kind of thing that will be done the day we get the leak or will it take time? whats involved in it? sorry but i have no experience in rils and want to learn a bit more about them.
[Thunderbolt Android Development] Link_of_Hyrule:
I think it really depends how close things are to what he is expecting the ril is completely different with ICS I mean yeah it could just be plop it in and it works but that's very unlikely I'd say it would at least take a few days if not a couple weeks to work all the bugs out. Hopefully we get it soon though :P
[Thunderbolt Android Development] haliwa04:
Have any of the DInc 1 devs moved on to the Thunderbolt or offered their help? They really seem to be able to cook up just about anything. Just asking
[Thunderbolt Android Development] twistedumbrella:
? We need help?
[Thunderbolt Android Development] mrkite38:
Ow.

I'm thisclose to purging this thread... with fire.

Folks, LTE is the problem. The inc is all but worthless in here. The rezound was probably our only hope and it hasn't panned out.
[Thunderbolt Android Development] 1454:
I thought the rezound radio was a good bit different than our so it wouldn't do us any good? Or that's what I had gathered, but I know very little about this, so I'm having to go by 3rd, 4th or 5th hand knowledge.
[Thunderbolt Android Development] mrkite38:
My point exactly (re: rezound.) It's the only other HTC 4g phone, so that's as close as we're going to get until they update us - and it didn't help.
[Thunderbolt Android Development] haliwa04:
I didn't mean to offend, and I wasn't talking about applying inc stuff to the tbolt. I was just saying as far as the devs go, like evervolv, I know protekk was working on it, just throwing in a mass of ideas to build a badass version of ics

Posted from my 1.34ghz, Infected, Themed Out, Lightningbolt.
[Thunderbolt Android Development] haliwa04:
And no need to purge, I wasn't asking about the stupid ril. I went and bought another DInc, rooted and slapped some ice cream on it. Come Monday, the Tbolts gonna be in the nightstand, Inc on my hip. So calm down, not trolling, or whining, just asking if the devs thought about having an Ice Cream gangbang

Posted from my 1.34ghz, Infected, Themed Out, Lightningbolt.
[Thunderbolt Android Development] twistedumbrella:
qsd8k is where they are focused with original stuff not already tested here.
[Thunderbolt Android Development] mrkite38:
Thanks for clarifying. It wasn't just you that prompted that post.
[Thunderbolt Android Development] kaijura:
are you guys getting forced reboots in random usage with tile rendering enabled with the latest Adreno ICS libraries? I turned it on last night and it seems to be causing lots of random issues.

I've had it happened in Playground vivo as well, one way I was able to replicate this issue is entering the superuser app and pressing the menu to bring up more options, when selecting "Preferences" it will fail and reboot.

This can also be replicated by going to the market and searching for something..

Turning it off seems to make it go away, at least for me.

On a side note, hopefully getting a mecha soon, this week. :cool:
[Thunderbolt Android Development] twistedumbrella:
Did you disable the force_cpu_upload from webkit? I haven't had a single issue so far, but I also threw that in before the last local build.

Also, the last build md5 should actually be fd5e0c0e7887b78c680debc6e2a430aa (hacked in a camera update not long after it became available)
[Thunderbolt Android Development] M..N:
Yeah I had the issue when I tried searching in the market. The phone just locked up and rebooted.

Edit : wrong device thread swoops.
[Thunderbolt Android Development] twistedumbrella:
Pretty sure it's webkit. That is the one thing I changed (literally the only one) between the live builds and the one I wanted to test and I haven't seen the issue. Looks like I should push that live. It went live here, but not any other phones.

BTW: Panorama is fixed in this build
[Thunderbolt Android Development] kaijura:
Nope, I don't think I enabled/disabled that.

Apologies for the newbie blunders, where can I disable that option in the webkit?
[Thunderbolt Android Development] twistedumbrella:
Should be disabled now in the board common. Just of matter of syncing.
[Thunderbolt Android Development] kaijura:
Yep, I saw it. Somehow I was short-sighted and I didn't think of looking in the changes in 8660 common to see where you mentioned that the mecha had it fixed earlier.

Built it and gave it a shot, no dice though, I guess something's just not playing right with the vivo for tilerender set to on. Everything is back to normal when I define it to false.

My kernel source is pretty kosher with the CM9 base, just a few patches like the videobuffer that enabled panorama, I'm out of ideas. Maybe tilerender was meant for the QSD chain?
[Thunderbolt Android Development] twistedumbrella:
On qsd the newer libs do not work right. They only really work for the msm ones.
[Thunderbolt Android Development] kaijura:
:/ at that.

In other news, you have a somewhat new cult that jumped ship from IceCold to Playground in IncS. I'm not surprised, I found playground superior in some aspects as well.
[Thunderbolt Android Development] twistedumbrella:
The settings are being added, just trying to keep it clean and completed as they are.
[Thunderbolt Android Development] Link_of_Hyrule:
Did the new gpu drivers fix netflix?
[Thunderbolt Android Development] twistedumbrella:
That is messed up in stagefright. I have yet to find an exact cause
[Thunderbolt Android Development] Link_of_Hyrule:
Obviously not top of the list to get fix but hopefully after camcorder and data.

The newest build doesn't match the MD5 posted. I'm guessing you just didn't update the notes or something.
[Thunderbolt Android Development] kaijura:
I sort of see it in an interesting way between AOKP and CM9, it seems like CM9 tends to be more slower, but tries to do professional work by moving one step at a time. AOKP meanwhile is really fast, but a lot of the stuff can be buggy if cherry picked before it's fully riped. It really seems like a lot of a turtle vs hare situation going on.

That's odd/interesting, does reverse engineering the OMX libraries not enable netflix for you guys?
[Thunderbolt Android Development] Link_of_Hyrule:
Why does the market turn black when you select an LCD density of 192? Do you think this will eventually be fixable?
[Thunderbolt Android Development] twistedumbrella:
Time to actually build all the garbage i've been stockpiling.
[Thunderbolt Android Development] Link_of_Hyrule:
LOL What garbage would that be?
[Thunderbolt Android Development] twistedumbrella:
Lots of cleanup and camera test results.
[Thunderbolt Android Development] Link_of_Hyrule:
Yes sensation source is out no it won't help get ril :) Have a nice day and thanks for playing the answer future questions game!
[Thunderbolt Android Development] twistedumbrella:
Source is worth at least a passing glance. It may help with other stuff. I take that back if it's just kernel though.
[Thunderbolt Android Development] Link_of_Hyrule:
Will it help with camera at all or is it completely different? I would guess since it's sense that it's mostly useless but who knows maybe there will be a fix for something just nothing for the ril I know that much.
[Thunderbolt Android Development] twistedumbrella:
Camera no. A general layout for when the right radio files are available maybe
[Thunderbolt Android Development] Link_of_Hyrule:
So you still working on that garbage clean up build lol?
[Thunderbolt Android Development] twistedumbrella:
Yup. Turned into like 5 features, cam changes and cleanup. Had to make changes to get merged to other roms because their dev won't do them first.
[Thunderbolt Android Development] Link_of_Hyrule:
Ok cool are you going to have another build out tonight?
[Thunderbolt Android Development] twistedumbrella:
If I get shooter fixed, yes.
[Thunderbolt Android Development] bamaredwingsfan:
When playing around with the ICS builds, would it be better to just delete the current ICS backup or restore the back up an install the new release over it?
[Thunderbolt Android Development] twistedumbrella:
Either way. I can't lie, it's been like 10 test builds since I wiped.
[Thunderbolt Android Development] twistedumbrella:
Looks promising...
[Thunderbolt Android Development] Link_of_Hyrule:
That sounds awesome! :) Looking forward for some new ICS sexiness :P

Edit: Why does the Play Store black out on 192 dpi? really my only problem with this dpi actually.
[Thunderbolt Android Development] kaijura:
Commonly known issue the store isn't friendly with higher dpi / LCD density, I just prefer to say DPI since it's easier to write.

You can try pushing a DPI-modded store apk, there are some floating around in android land.
[Thunderbolt Android Development] Link_of_Hyrule:
None of those fix the issue that I am having those only fix the fact that some apps don't let you install them. The problem is that the front page of the market is completely black. I tried LCD modder because it has a market fixer and that didn't fix it either.
[Thunderbolt Android Development] Jlewis894:
Link expired....anywhere i can d/l it? Thankss
[Thunderbolt Android Development] twistedumbrella:
Time to hack market again I guess
[Thunderbolt Android Development] Link_of_Hyrule:
yeah hopefully it works :)
[Thunderbolt Android Development] twistedumbrella:
Here is the market app itself to see if that works before I trade them off
[Thunderbolt Android Development] Link_of_Hyrule:
I used root explorer to replace it and it didn't seem to work. :(
[Thunderbolt Android Development] Jlewis894:
Is there somewhere i can d/l it to play with lol...clickin the link, dropbox says its expired or broken lol.....thanks guys
[Thunderbolt Android Development] twistedumbrella:
Currently, not yet. Shortly it will be updated and refreshed.
[Thunderbolt Android Development] Jlewis894:
Thanks again man...appreciate it!
[Thunderbolt Android Development] Link_of_Hyrule:
Looks like your going to need a new host or to make a new dropbox :(
[Thunderbolt Android Development] kaijura:
Just noticed you have a dpi-patched Phone.apk! Was calling and then I was like.. hey... aren't I on 190 dpi?
[Thunderbolt Android Development] kaijura:
Twisted, any idea what causes the settings fc on boot the latest builds?

I also tried turning on the legacy touchscreen flag, it didn't get past that unity issue I was talking about in ace section. :(

Every now and then, logcat shows some strange java crash/issue on the vivo, but somehow not on the mecha.
[Thunderbolt Android Development] twistedumbrella:
It shouldn't have an issue. Is there a log?
[Thunderbolt Android Development] knipp21:
Hey twisted. Any chance of making this available on dinc2
[Thunderbolt Android Development] twistedumbrella:
java.lang.RuntimeException: Unable to instantiate receiver com.android.settings.cmstats.ReportingServiceManager: java.lang.ClassNotFoundException

^ Fixed:

https://github.com/ThePlayground/an...mmit/746951981886935e9cd1c959dd7b65f46d2fa430
[Thunderbolt Android Development] twistedumbrella:
I would rather not invade with http://xdaforums.com/showthread.php?t=1478117, since he dumped all his source and guides for thunderbolt just to focus on that, but I would recommend http://xdaforums.com/showthread.php?t=1561816 as we have always been at about the same point in progress, and he is more hardware than customization similar to this.
[Thunderbolt Android Development] kaijura:
shoot, had me beat by over a day and all too.
[Thunderbolt Android Development] knipp21:
OK cool yeah I'm using aeros now. I know you're a good kernel guy and nit is working the sense 4 rom now.

Aokp looks good but needs the camera fix..I might have fixed mms..idk though.
[Thunderbolt Android Development] kaijura:
Latest camerahal updates still works fine with mecha, but causes corruption/glitches with front cam on vivo. From initial vivo build and pulled over .so from mecha as well, gave same results.

The thumbnails generated by desktop come out fine interestingly enough.
[Thunderbolt Android Development] dtoye:
Ok so I've been following this thread for a while since page 40 something to the developer I thank you for putting your time and effort into this build the potential of this is making me stick with the thunderbolt I'm currently running on liquid smooth rom I want to play around with this is it the same as just flashing any other rom?
[Thunderbolt Android Development] twistedumbrella:
Yes. If you are flashing it straight to the phone it is. Actually, even if you are flashing it to boot manager it is. The only thing I recommend coming from a Gingerbread ROM is to backup and wipe.
[Thunderbolt Android Development] twistedumbrella:
Hmm, well the relevant code for the front camera is:

#define HTC_SWITCH_CAMERA_FILE_PATH "/sys/android_camera2/htcwc"

char htc_buffer[16];
int htc_fd;

if (access(HTC_SWITCH_CAMERA_FILE_PATH, W_OK) == 0) {
LOGI("Switching to HTC Camera: %d", cameraid);
snprintf(htc_buffer, sizeof(htc_buffer), "%d", cameraid);
htc_fd = open(HTC_SWITCH_CAMERA_FILE_PATH, O_WRONLY);
write(htc_fd, htc_buffer, strlen(htc_buffer));
close(htc_fd);
}

Pretty much everything else is the same code as the back camera.
[Thunderbolt Android Development] twistedumbrella:
Yah. Another post that clearly states "we don't make this to provide anything meant to be tested because other developers should drop what they're doing and test my work"

No questions please. Just add it to your build...
[Thunderbolt Android Development] dtoye:
Downloading now
[Thunderbolt Android Development] twistedumbrella:
If the download link isn't working then for now no.
[Thunderbolt Android Development] twistedumbrella:
Should be good now. Brand new link
[Thunderbolt Android Development] twistedumbrella:
New kernel on the way as well
[Thunderbolt Android Development] kaijura:
Cool. Changed I/O scheduler?
[Thunderbolt Android Development] twistedumbrella:
Same default, just added BFQ from a 3.0 kernel haha
[Thunderbolt Android Development] Link_of_Hyrule:
What is Wireless firmware exactly?
[Thunderbolt Android Development] kaijura:
Your dropbox is on the radar.

Back to syncing and building.. ;)