yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] twistedumbrella:
Apps like rom manager, titanium, and others that are a personal preference.
[Thunderbolt Android Development] scook9:
Are you in touch with the CM devs for the TB (Slayher and CVPCS if I recall)? I thought that slayher had sort of abandoned the device, if that is the case (CVPCS never really contributed much I believe) maybe you should officially take over the TB?
[Thunderbolt Android Development] twistedumbrella:
Slayher is protecting the country and CVPCS is very involved in the Motorola side of things. In a manner of speaking I kind of have taken it on. I haven't figured out how to submit an entire project to CM9, but eventually I will push the thunderbolt to CM. I just don't want it to be as "experimental" when I do so I don't have to constantly push updates to review.
[Thunderbolt Android Development] scook9:
Got it. I was not trying to belittle Slayher's efforts. Did not realize he was deployed right now. I helped with a lot of testing over the summer last year to get 7.1 working.

Looking forward to the progress and "Official" CM work once you get the underlying stuff settled down. Do you operate an IRC channel? Slayher did that for the CM7 work and it was a good place to discuss tests and offer ideas, etc
[Thunderbolt Android Development] twistedumbrella:
I did, but honestly things got to a point where I was spending all my time helping other groups get their source to where I was so they could use theirs instead. I also got swamped with school and was being paged when I didn't answer.
[Thunderbolt Android Development] scook9:
That is too bad, people were pretty productive and helpful in slayhers channel :(

Maybe you can just go there? haha
[Thunderbolt Android Development] twistedumbrella:
Lol. I am all about helping out, but I mean once its been done its been done. I don't see a reason to get something fully up and running, then go around and fix it myself for a different source. I will gladly help fix an issue, port changes to a new device, and explain what I did. It's doing it for people without them wanting to be involved that gets frustrating because they form a dependance on you that is very hard to break.
[Thunderbolt Android Development] scook9:
Well, my offer is this, end of march I am up for upgrade at which time I can relegate my TB to full time testing purposes :D
[Thunderbolt Android Development] twistedumbrella:
I just found the stupidest error. Missing an endif for a composition file. Might make a huge difference, might not. It will however directly relate to the errors spamming logs when camcorder is launched...
[Thunderbolt Android Development] Link_of_Hyrule:
So does that mean you'll have less errors to filter through when you are trying to fix the camcorder?
[Thunderbolt Android Development] twistedumbrella:
And the display is a little quicker.
[Thunderbolt Android Development] raddacle:
Those are the improvements I love to hear. Thanks for all the hard work you've put into this. Unfortunately, I'm having problems with boot manager so I'm unable test the latest builds. But from what I can tell from other reviews, they're working really well. Hope I can get this fixed soon.
[Thunderbolt Android Development] Link_of_Hyrule:
Well that's good to hear hopefully we can get camcorder up and running soon :)
[Thunderbolt Android Development] danwguy:
Just a quick question, why doesn't the radion work? I understand that Ril (whatever that means) doesn't work, but wouldn't it be possible to pull some stuff out of an older rom and make it work, like pull out the stuff that allows cm7 make calls and put it in the ics builds to make the radio work? forgive my idiocy if that't not the case. I am a programmer, but never programmed for android, just seems like something that would be possible
[Thunderbolt Android Development] Link_of_Hyrule:
They have been able to get calling working before but the radio = the ril which is the radio interface layer on our phone you have to get 3G and 4G working together you can't have one working without the other but hopefully there will be a leak off the ics update or the devs will figure it out a couple seem to be getting pretty close so we will see what happens.
[Thunderbolt Android Development] kaijura:
The big issue has to do with the fact that there are no msm7x30 devices official released with ICS as of yet, and even less likely for a CDMA variant, so other than blindly trying to hack it out like zbwu86 did with the GB camera, there is little hope until there is a leak/ruu to base it off of. Basically as I understand it, you can't transfer code from GB to ICS in a cut and dry fashion. I do wonder if it's possible to work with what's in the vivow as that is a CDMA msm7x30.

I'd really like to hear twisted's explanation of this, as I'm always curious as to why something can work on one decided and not another, seems to be the common theme of kernels.
[Thunderbolt Android Development] twistedumbrella:
http://db.tt/4i4d3nVA
[Thunderbolt Android Development] Link_of_Hyrule:
The file that link downloads is corrupt unless it's not done uploading or something. it downloads in one second and has nothing in the file.

Sent from my HTC Thunderbolt!
[Thunderbolt Android Development] raddacle:
Same problem
[Thunderbolt Android Development] Link_of_Hyrule:
download seems to be working now. :)

Sent from my HTC Thunderbolt!
[Thunderbolt Android Development] murdocthc:
Lol I love that he just pops in to hit us with a db link and the he's GONE! Like a true super hero!
[Thunderbolt Android Development] Link_of_Hyrule:
Well camera doesn't connect any more but I'm sure you know that. Well keep up the good work though I know by the end of the week we'll have working Camcorder :)

Sent from my HTC Thunderbolt!
[Thunderbolt Android Development] thesandman2236:
What's in this release? I didn't see an update in post 1.
[Thunderbolt Android Development] twistedumbrella:
There wasn't one. It was a test of new code. Found some mistakes and the "official" test version will hit after it builds.
[Thunderbolt Android Development] what be up:
I'm still getting the server error on the market... I did notice it works when the wifi signal bars are blue not grey. After they turn blue the first time it works the entire time, the problem isgetting the wifi signal bars to turn blue in the first place, which idk how. speech-to- text is now working. Keep up the good work
[Thunderbolt Android Development] mrkite38:
The blue/grey in ICS is the new green/grey from GB. The color means you're signed into Google services, IIRC.

Edit: just realized I spelled gray/grey both ways in my original post. Spelling fail. :(
[Thunderbolt Android Development] scook9:
It should mean you are signed into google services but in reality it means you do or don't have internet connectivity it seems, at least that is what I have experienced
[Thunderbolt Android Development] what be up:
If it means that then how do I sign in?
[Thunderbolt Android Development] scook9:
Usually just access something like google talk or gmail and it authenticates you in when it loads the program
[Thunderbolt Android Development] what be up:
Alright I'll try it out
[Thunderbolt Android Development] raddacle:
The latest build is insanely smooth! Not one hiccup, except on first open some apps force close and you get a 101 error from trying to install an app from the market. Also, when I changed the LCD density in the build.prop the market turns black.
[Thunderbolt Android Development] xheavymetaldadx:
Don't know if it means **** but the rezound has a ice/sense Tom with working data :confused:
[Thunderbolt Android Development] twistedumbrella:
Next build won't have the close. It was from testing the rezound stuff for radio but it can be dropped. Ill double check market, haven't seen that error before but it has opened just to close again which fixes itself after opening a second time.
[Thunderbolt Android Development] raddacle:
Oh, and the pictures taken still have the green lines in the top. Is that from fixing the camcorder?
[Thunderbolt Android Development] xheavymetaldadx:
Answers my question lmao
[Thunderbolt Android Development] twistedumbrella:
It's a trade off. Either the camcorder connects and neither can show or camera works and we get overlay logs and green lines. Working on a way to get it all.
[Thunderbolt Android Development] Link_of_Hyrule:
Sounds like your getting close at least.

Sent from my HTC Thunderbolt!
[Thunderbolt Android Development] twistedumbrella:
Hoping to at least get panorama tonight.
[Thunderbolt Android Development] Link_of_Hyrule:
Sweet bro I really want to try that out it sounds cool!

Don't you love how I post in both of the threads on xda and rootzwiki lol!
[Thunderbolt Android Development] twistedumbrella:
And do you like the newest build where panorama camera works?
[Thunderbolt Android Development] Link_of_Hyrule:
Which build is it stable or experimental?
[Thunderbolt Android Development] twistedumbrella:
Experimental, but there is a new one that will be done in the next half hour as well with some fixes and updates.
[Thunderbolt Android Development] chuckbeasley:
Ok. I got the basics of the update.zip working. I used the updater-scripts from Current Base, but it's not booting either. So, there must be something wrong with the script. Did you generate your own script?
[Thunderbolt Android Development] twistedumbrella:
I used the one I had posted in the builds. I just haven't been home all day to do anything about a better explanation of how its laid out and where to make changes.
[Thunderbolt Android Development] chuckbeasley:
I was able to get adb working and took a look at logcat. I saw a lot of weird errors. I wonder if some have to do with the kernel.
[Thunderbolt Android Development] twistedumbrella:
Could be, I haven't updated that part in a while.
[Thunderbolt Android Development] chuckbeasley:
I have attached my logcat. This is a very interesting entry:

F/libc ( 3173): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
[Thunderbolt Android Development] twistedumbrella:
That happens when the gralloc and egl are very out of sync.
[Thunderbolt Android Development] chuckbeasley:
How can that happen when both are built in the same build?
[Thunderbolt Android Development] twistedumbrella:
Some of it is precompiled. It also isn't fully set up for this actual phone.
[Thunderbolt Android Development] twistedumbrella:
(wait for it...), it finally builds without having to bypass any errors! (Wee!)

Had to remove libaudio-qdsp5v2 from msm7k, import qcom gps 5000, remove redundant recovery functions, comment out webrtc, and swap the libGLES_andreno200 libs that are pulled from the phone, but finally it builds...

Current changes are available on GitHub https://github.com/TwistedUmbrella

common_msm_dirs := libcopybit liblights libopencorehw librpc libstagefrighthw
msm7k_dirs := $(common_msm_dirs) boot libgralloc libaudio
qsd8k_dirs := $(common_msm_dirs) libgralloc-qsd8k libaudio-qsd8k dspcrashd
# msm7x30_dirs := liblights libgralloc-qsd8k librpc libaudio-qdsp5v2
msm7x30_dirs := liblights libgralloc-qsd8k librpc

in hardware/msm7k/Android.mk was not documented as this is only a temporary fix.

Also applied the webrtc changes ONLY from https://github.com/TeamICS/ICS_Fixes
[Thunderbolt Android Development] chuckbeasley:
That's exactly what I had to do. Have you gotten yours to boot? I haven't yet. It'll be a couple days before I can get back to working on it.
[Thunderbolt Android Development] twistedumbrella:
Not yet. Shelnutt2 just went through and modified audio to get it to build. So far, it has been working, so I will know soon. I uploaded more to github so the changes should be easier tracked.
[Thunderbolt Android Development] kidhudi:
Update: Punk.kaos appaertly has the touchscreen fixed. hopefully all is smooth sailing from here :P
[Thunderbolt Android Development] twistedumbrella:
Don't have that kernel, but that's cool. Still working on fixing the source to get everything working here.
[Thunderbolt Android Development] Chopes:
Link to where he has this info?
[Thunderbolt Android Development] kidhudi:
@punkkaos on twitter
[Thunderbolt Android Development] twistedumbrella:
Unless he did some amazingly creative edits that the 6 of us just couldn't figure out, then I am assuming his test build is one of the SDK/Nexus/Other device ports. I tried the idc file and it was a one-hit wonder on the base. Far as the source build, I can finally get past the splash screen flashing an update, but I am still getting some libc errors. There have been a ton of edits, and it is all posted on github.

Tried porting audio from a CM review post, which didn't work. Used Shelnutt2's qsdp5v2 edits, but modified them for mecha instead of ace and it seems to have gotten that aspect working. Compiled using the make otapackage and found a bunch of edits that needed to be done to recovery.fstab and my device_mecha.mk files to actually use all of the modules and attempt to import that idc to see if it worked with a source build. Getting closer and closer.

It is always fun when someone posts that they have stuff working because unless you can look at the source or take apart the build, the only result seems to be pressure on everyone who doesn't have the same results to get them and pressure on the person who does to provide them. That is partially why I only explain what is currently available when it is being uploaded and then resources for what is currently being tested. While I can't control the hype that others create, I like to minimize the amount I do.
[Thunderbolt Android Development] kidhudi:
Bummer.. i was so optomistic. thanks for the update Twisted.

you guys are amazing.
[Thunderbolt Android Development] dc iz 2 legit:
Party pooper lol j/k
[Thunderbolt Android Development] twistedumbrella:
[YOUTUBE]UN_fmQLlR3s[/YOUTUBE]
[Thunderbolt Android Development] McLabia:
Lol.

Sent from my rooted, Dark Horse(hopefully soon) INFECTED Eternity bolt running Ziggys latest.
[Thunderbolt Android Development] Link_of_Hyrule:
I just took a picture with Panorama seems to work good awesome work bro!
[Thunderbolt Android Development] famester:
So I make it to the github page what file or link do I click on to try this have given it a go since you first got it to boot properly.
[Thunderbolt Android Development] twistedumbrella:
Click the picture of the thunderbolt, then the link to download experimental
[Thunderbolt Android Development] famester:
Night and day. This thing is refined
[Thunderbolt Android Development] twistedumbrella:
Rootzwiki went dead silent...
[Thunderbolt Android Development] donnyp1:
Why is that?

Sent from my tbolt using the very slow after fresh updated xda app
[Thunderbolt Android Development] twistedumbrella:
Don't know. Just haven't seen a post in days.
[Thunderbolt Android Development] Link_of_Hyrule:
That's cus after you closed the thread we all moved over here lol. Btw did you get my PM Twisted?
[Thunderbolt Android Development] what be up:
Is it just me or are the md5 sums different?I downloaded the same file like 3 times, and keep getting the same thing
[Thunderbolt Android Development] twistedumbrella:
They are different. Another update will clean that up before I do some camera testing that won't be uploaded it prevent breaking what we have.

I think my Pms are off. I wasn't checking them ever being on here through the phone.
[Thunderbolt Android Development] kaijura:
Twisted, I got a question for you, if you would be willing to give a few pointers.

Where or which folder structure would I navigate to edit the capacitive softkey brightness/functions?

There seems to be a minor griping bug in my build that the softkeys always stay off unless the brightness is toggled on, in an AOKP base. They stay off while auto-brightness is on too. It's sort of irritating they don't work the way they are intended to.

Wonder if it's patchable or if I would have to edit something in the source and rebuild.
[Thunderbolt Android Development] Link_of_Hyrule:
Oh ok that's what I thought cus I sent two and I looked in my sent box and they weren't in there lol. I just wanted to get your gtalk so I could help you test stuff better and what not.
[Thunderbolt Android Development] kaijura:
Just some playing around with panorama, seems pretty nifty with how accurate it is.

with twisted's msm7x30 code: http://i.imgur.com/cFHlO.jpg

native ICS device: http://i.imgur.com/zWurq.jpg
[Thunderbolt Android Development] twistedumbrella:
That picture looks amazing. Lot better than the ones I tried to take haha.

Once I get the overlay worked out it should fix the last of the color issues
[Thunderbolt Android Development] zenulator:
Did you get video recording working?
[Thunderbolt Android Development] raddacle:
Can someone create an RSS feed for the download page? Its becoming strenuous to refresh it every few hours.
[Thunderbolt Android Development] haliwa04:
Strenuous? Really? I find it slightly annoying. Strenuous is flipping through 150 pages of arguments to.find an answer to a question. Or repeatedly lifting a heavy phone.

Posted from my 1.34ghz, Infected, Themed Out, Lightningbolt.
[Thunderbolt Android Development] what be up:
U guys should be thankful that twisted is even still working on the tbolt..
[Thunderbolt Android Development] raddacle:
Are you kidding me? I'm extatic that we have this much work being done. I couldn't be any more thank full, but I'm still aware that most of work is done on the weekends. I just don't want to miss anything, but I still don't want to be refreshing the page every three hours.
[Thunderbolt Android Development] twistedumbrella:
I find it annoying as well. Having to click a button to see if hundreds of lines of code were changed and hours were spent linking them together for me. Lol.

I will make better use of the ota for ROM manager, but something a little more informative will have to wait until I can design a better update method. It's only 4 devices being hosted, i'm sure school and actual updates can wait ;)

? Most of the work is done between 10pm and 5am on weeknights.
[Thunderbolt Android Development] what be up:
Ya I know, I didn't really mean it like that..meant that we're lucky that twisted still has the will to keep updating the tbolt in the first place. :P
[Thunderbolt Android Development] donnyp1:
Dude, just take your time. Best thing about the xda app is easy navigation, and im yet to wear out a button. Some people just dont get it.
[Thunderbolt Android Development] twistedumbrella:
I honestly just laughed. I could probably have the script post something somewhere it just won't be until after I finish cleaning for omap and helping to get shooter up.
[Thunderbolt Android Development] Link_of_Hyrule:
I'm you could make it realtime auto refresh or something maybe make it tweet out when new builds finish LOL!
[Thunderbolt Android Development] paraplegicpanda:
Hey twistedumbrella, I'd be happy to help you out with the build page if you like. I've been a web designer for about a hundred years and I wouldn't mind playing around on a small project like that. I can set up the RSS feed, Automatic tweets, etc.

I'm actually fine with just updating the page and reading through the thread here on XDA but I saw an opportunity where I may be able to help so I decided to offer. If you're interested let me know, feel free to shoot me an email. Contact info is on my XDA profile.
[Thunderbolt Android Development] djsnake210:
Hey twisted... I posted this in liquid's thread as well at rootz, but i thought maybe I'd post here as well...

Question about the RIL (no not when is it coming... lol)... I am not hugely familiar with Android file structure, but I'm trying to learn. I see that the RIL files are located in the System>Lib folder.

The files I see are labeled:

libreference-ril.so

libril.so

libril_ims.so

libril-qc-1.so

libril-qcril-hook-oem.so

In doing some research on google I learned that .so files are compiled libraries like .dll files in windows. That being said I have these questions:

- Are these all of the files that make up the RIL?

- What all files access these files?

- Is the problem that the existing ril files will not work since they are from a different version of android or from a different device?

- Would disassembling the .so files using something like IDA Disassembler help?

Sorry if I'm asking a lot of questions.... just trying to learn so that hopefully I can contribute at some point.

Thank you for any insight you wish to provide.
[Thunderbolt Android Development] twistedumbrella:
There is one more, libreference-sms-cdma, but they could be disassembled and possibly hacked. It's been mentioned, but it was a matter of figuring out what to change I believe was the problem.
[Thunderbolt Android Development] Stoney 666:
Twisted, you should get a nice laugh out of this.... It had to be done, haha

http://db.tt/QcNKvwuc
[Thunderbolt Android Development] twistedumbrella:
Lol. I think what made me laugh is that he found a more direct way to make the general point I got so much crap about touching.
[Thunderbolt Android Development] donnyp1:
Damn! Dude went off! I must have missed something being a more recent tbolt user.
[Thunderbolt Android Development] twistedumbrella:
The new update is building, but in the meantime replacing settings with the one attached will unlock the options that got lost in the build
[Thunderbolt Android Development] xheavymetaldadx:
That happen on rootzwiki? I went to check on the thread and son of a ***** was gone lmao
[Thunderbolt Android Development] donnyp1:
Anyone know dv's twitter? Id love to read what he had to say after that multi page beat down on rw.
[Thunderbolt Android Development] mrkite38:
@paullie_vicious , I think.

Zenulator, long time no see...
[Thunderbolt Android Development] donnyp1:
Thanks
[Thunderbolt Android Development] twistedumbrella:
http://twitter.com/#!/Paullie_Vicious

[ROM] Vicious-ImAForumBitch-CryBaby-V1000 Updated! 9:55AM 3/6/2030 ...

rootzwiki.com › ... › HTC › Thunderbolt › Thunderbolt Developer Forum

10 posts - 10 authors - 3 days ago

Welcome back to YOU'RE a woman for the HTC Thunderbolt 4G LTE This thread will now be the centralized thread for all you whining female ...

If I had seen this coming when I got that first message planning to get involved with this whole thing, I would have just hit "Deny" but I guess social suicide is better than more messages on Rootz claiming I don't offer any help despite how much he has helped me :confused::eek::confused:

Edit: New update is now live. Hopefully it cancels out the bad kharma :cool:
[Thunderbolt Android Development] haliwa04:
Yea, I think he's done with the tb. On a lighter note, I flashed this for a go this past weekend, while fishing, pulling WiFi. Awesome

Posted from my 1.34ghz, Infected, Themed Out, Lightningbolt.
[Thunderbolt Android Development] kaijura:
Twisted, not sure if you are aware of this but video conferencing/chatting on front cam is working pretty much perfectly for vivo now as of your last push to CM like a week ago. I don't think the other devices like ace would know since they don't have front cams obviously.

Facelock preview is also working 100%, but it seems that for my build it's not recognizing the image. nk111 was able to get facelock working w/o preview on saga, he mentioned there was a parameter that needs to be enabled in the camerahal. Off I go to go hunting at your git.. :cool:
[Thunderbolt Android Development] Link_of_Hyrule:
Hey any way you can get the 180 dpi to fully work? It seems that the 160 has issues because it thinks the device is a tablet for example Google chrome and Google music Also the 240 dpi just seems too big. The 180 it thinks it's a phone but makes market black and when you try to launch chrome the phone restarts. Anyways would be great to see this get fixed keep up the good work!
[Thunderbolt Android Development] scook9:
Verizon plans to officially get ICS onto the TB (Mind=blown)

Maybe it will help with the dev work once it gets out/leaked.

http://www.anandtech.com/show/5634/verizon-wireless-announces-its-android-40-update-list
[Thunderbolt Android Development] METDeath:
That version will probably be sensed up... unless HTC does what they did with the Eris (I think), where they went AOSP for the upgrade to whatever was current then.