Database Info

Discussion for ICS G2x Port

Lets keep all discussion in this thread please.
Development thread : http://forum.xda-developers.com/showthread.php?t=1309620
Sent from my LG-P999 using Tapatalk

great work on the touch screen! you guys are awesome.

OK so the hold up now seems to be LG right? in search for lg device drivers?

I think its ready for a ALPHA test now.. touchscreen works 100% and so does the radio wifi etc.. hardware acceleration wont be coming anytime soon but i can live without it for now

There are a lot of things that will need to be ironed out before we can even consider a beta.
First hand, without hw acceleration the phone crawls.
Sent from my LG-P999 using Tapatalk

and hardware acceleration isn't possible without updated drivers correct?

regP said:
and hardware acceleration isn't possible without updated drivers correct?
Click to expand...
Click to collapse
Correct unless some kind of workaround is created.
Sent from my LG-P999 using Tapatalk

Hope you can get HW acceleration to work soon. Can't you do whatever other roms like cyanogen mod did?
Its not like they got exclusive access to tegra drivers...

The problem is the binary blob implements hw acceleration according to the way Gingerbread expects it which is different than how Honeycomb and ICS do it.
I've seen at least one person talk about rewriting the library from the android side to match how the nVidia blob works. Which would be a good backup plan if LG renegs on the ICS update for our phones.
Sent from my LG-P999 using XDA App

epicsquare said:
Hope you can get HW acceleration to work soon. Can't you do whatever other roms like cyanogen mod did?
Its not like they got exclusive access to tegra drivers...
Click to expand...
Click to collapse
Doesnt work like that. And cm doesn have android 4.0 for the g2x only gb 2.3.7

xile6 said:
Doesnt work like that. And cm doesn have android 4.0 for the g2x only gb 2.3.7
Click to expand...
Click to collapse
I understand it's not as easy as copy paste source code, but the strategy should be the similar. I've never done any low level development so I'm just shooting in the dark here.
Also cm9 is expected in 2 months and I assume it will support the g2x. I wouldn't count on lg for anything. So rewriting the library is probably the best bet.

Glad to see so many new people jumping on and helping out. I'm sure most people here would help if they knew how.
Thanks for the work, guys! Where can we donate?

I've been a lurker on these forums for a long time and never realized I had to have 10 posts to post in the developer forums, so at least I can post in this thread. I will be getting up to speed on the ICS source over the next couple days and hope to join the effort in development of the port to the g2x as soon as I have my dev environment up. I'll be sitting in the IRC channel to ingest the info on where you guys are at so that I can jump in and help with any parts (sound maybe?) that you guys need assistance with.
Great job so far, hopefully I can be of assistance.

babyinablender said:
I've been a lurker on these forums for a long time and never realized I had to have 10 posts to post in the developer forums, so at least I can post in this thread. I will be getting up to speed on the ICS source over the next couple days and hope to join the effort in development of the port to the g2x as soon as I have my dev environment up. I'll be sitting in the IRC channel to ingest the info on where you guys are at so that I can jump in and help with any parts (sound maybe?) that you guys need assistance with.
Great job so far, hopefully I can be of assistance.
Click to expand...
Click to collapse
There's never such a thing as too much help.
I'm sure you can provide something good to the already great team working on this!
Sent from my LG-P999 using xda premium

NEW video on the front page of the development thread!... although most will probably look at that thread before this one, lol.
But anyways, the touchscreen is fully working now!
The speed of this devving is amazing! I commented on the video already, but wow you guys are doing an amazing job! Thanks for all the effort you're putting into this!
Sent from my LG-P999 using XDA App

Well seeing as the O2x is getting ICS we should be seeing a fully functional ROM afterall

epicsquare said:
Also cm9 is expected in 2 months and I assume it will support the g2x. I wouldn't count on lg for anything. So rewriting the library is probably the best bet.
Click to expand...
Click to collapse
Thought I read somewhere that they weren't working it for the G2x? Or at least not any time soon?

Grooveoriented said:
Thought I read somewhere that they weren't working it for the G2x? Or at least not any time soon?
Click to expand...
Click to collapse
Actually, CM9 has been running on the G2x since Thanksgiving and according to a dev running well. They're still testing so aren't ready to release anything yet but we'll have it very, very soon.

I'm very curious to see it in action.do we know if it's accelerated graphics or framebuffer?
iswope said:
Actually, CM9 has been running on the G2x since Thanksgiving and according to a dev running well. They're still testing so aren't ready to release anything yet but we'll have it very, very soon.
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

[Q] How close is Paul Burton to Beta?

Paul (or anyone who knows)...
How close are you to a Beta version of your ICS port for the OG Transformer?
I think you have done more than anyone in trying to get this stable before Asus releases their version, and definitely offer a way to get Root on the TF101 ICS.
I really just wanted to start a thread that would allow for Version updates to your port, where people can see a status from the developer himself!​
Thanks!
Jeff
--
"I've donated to Paul...Have you??"

It's probably close. What's supposed to work, works.
Sent from my Transformer TF101 using Tapatalk

If you are a gamer stay clear for awhile yet or atleast till official comes and devs can kang some parts
Sent from my Transformer TF101 using xda premium

gVibeR said:
How close is Paul Burton to Beta?
Click to expand...
Click to collapse
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
gVibeR said:
How close are you to a Beta version of your ICS port for the OG Transformer?
Click to expand...
Click to collapse
Oh right, the ROM. Beta is a blurry line, I may not even use it and just keep incrementally improving it until it feels like RC time (and when I say RC I mean a build I actually consider suitable for final release, not the linux "release candidate but we'd never actually consider releasing this" terminology). I think once I get libsensors & libcamera written the hardware support will all be there at least in a basic form and then polishing and fixing smaller things will improve it quickly. I'm hesitant to put a timescale on it - I can't spend the time of a full time job on this and the time I do spend on it is a little sporadic. I'd hope to have sensors working within the next week or so, if that helps. I'm also planning to look at doing OTA updates of some sort now that it's basically usable for common tasks (for some people), to keep people updated easier and perhaps lighten the load on my web host by doing deltas.
I apologise for the terrible joke above...

Without access to the full source code for the drivers, any ROM based off of generic Android will never be Beta or better...
Paul's ICS port is from the standard Google ASOP tree, with lashed in binaries from other sources. What Asus deliver will be built for the specific platform.
There is a HUGE difference.
My experience of Paul's ICS was quite good, the biggest gripe for me, was the REALLY choppy sound playback, which was a deal-breaker for me, and I went back to honeycomb.

im not to sure about the binaries just being ported in i think paul is writting a whole lot of his own stuff, i could be wrong tho. i read a txt where he talked about writting his own drivers for everything cuz asus code is sloppy, he said he would prefer write his own than just plug in binaries.

CrazyPeter said:
Without access to the full source code for the drivers, any ROM based off of generic Android will never be Beta or better...
Paul's ICS port is from the standard Google ASOP tree, with lashed in binaries from other sources. What Asus deliver will be built for the specific platform.
There is a HUGE difference.
My experience of Paul's ICS was quite good, the biggest gripe for me, was the REALLY choppy sound playback, which was a deal-breaker for me, and I went back to honeycomb.
Click to expand...
Click to collapse
Umm, with all due respect - you're wrong. Asus aren't necessary. The only things remaining as binaries are the graphics drivers and they're from nvidia.

paulburton said:
Umm, with all due respect - you're wrong. Asus aren't necessary. The only things remaining as binaries are the graphics drivers and they're from nvidia.
Click to expand...
Click to collapse
So Asus have released the sources for ICS Wifi, Bluetooth, Audio, Camera and sensor drivers?
That's news to me, or are using using the honeycomb sources and patching them up with sticking plasters to work with ICS?

CrazyPeter said:
So Asus have released the sources for ICS Wifi, Bluetooth, Audio, Camera and sensor drivers?
That's news to me, or are using using the honeycomb sources and patching them up with sticking plasters to work with ICS?
Click to expand...
Click to collapse
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too

paulburton said:
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
Click to expand...
Click to collapse
Paul Burton, serving up wanton coding justice to non-believers like it ain't no thang.
Keep up the good work, but I do think you need to assign a cool name to this project.

paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
Click to expand...
Click to collapse
Too funny, lol. Keep up the good work, and thanks for the posts. Always informative.

paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
Click to expand...
Click to collapse
LMAO a good dev with a great sense of humor! Or great dev with good sense of humor, I can't tell which

paulburton said:
Well, I reflect on that often. I think I've developed a lot in my 22 years and am certainly close to feature complete. There have been a few big changes in the past couple years of life that make me a little nervous to apply the beta tag just yet, but it's close.
I apologise for the terrible joke above...
Click to expand...
Click to collapse
Don't apolgize, that's what i call the so famous british humour . Please keep developping and joking that way Sir Burton.

paulburton said:
People outside of asus can write code too
Click to expand...
Click to collapse
Awesome! !!!

You sir need a TARDIS. That was Brilliant.
paulburton said:
No they haven't. What I'm saying is that they don't need to - I can just write them myself. Some of those are open anyway (wifi, bluetooth) and don't come from asus. Little asus addons like setting up the MAC address are easy to reverse engineer and rewrite (and MAC for example is done like that). libaudio I've already written but obviously there's a bug in the buffer management somewhere which causes the skips, and input still needs doing. libsensors won't be too much work, and libcamera shouldn't be huge either.
People outside of asus can write code too
Click to expand...
Click to collapse

Just a side note (and I'm not I repeat not complaing about this thread) for those who are asking for updates (nobody asked for updates here) about Paul's releases you should find them when they appear. It does not make it easier for him to complete them if he has to answer a zillion posts about when it will be ready (still not complaining) for release. Think about this...... he could be watching tv or going to the pub or doing stuff that he really needs to do like school (still not complaining) instead of coding.
Again I would like to emphasize that I am not complaining about this.
Oh and Paul how were your exams?
Sent from my Infected Galaxy Y using Tapatalk

Dreamboxuser said:
Just a side note (and I'm not I repeat not complaing about this thread) for those who are asking for updates (nobody asked for updates here) about Paul's releases you should find them when they appear. It does not make it easier for him to complete them if he has to answer a zillion posts about when it will be ready (still not complaining) for release. Think about this...... he could be watching tv or going to the pub or doing stuff that he really needs to do like school (still not complaining) instead of coding.
Again I would like to emphasize that I am not complaining about this.
Oh and Paul how were your exams?
Click to expand...
Click to collapse
It's true, my life contains things other than writing this ROM. Fortunately for you guys I don't own a TV
Exams went well thanks, all are above 70% (so 1st class) and the one I thought went horribly turns out to be my best grade. Odd

What kind of student are you, Paul?

asdfuogh said:
What kind of student are you, Paul?
Click to expand...
Click to collapse
Read his profile.
http://forum.xda-developers.com/member.php?u=4421777

Hey Paul,
Just wanting to keep everyone up to date...
Could you give us a status of what still is not working with your latest release Spark?
Now that you have a name for your rom, and have replaced the original warning with your new one, would you say this release is usable for most things?
Thanks a ton for your work...who needs Asus, we got Paul !!

New Cyanogen Maintainer

jmhalder said:
Max Krivonos (Scepterr on XDA) has updated a old "Amaze is now amazing" post of his on Google+.
https://plus.google.com/106544349933037831956/posts/1SMW3eVKk1d
Max is the current maintainer for the Amaze and MT4G-Slide for CM9. He's had a number of small updates yesterday and today alone.
I'm quite optimistic with Max, I'm sure this will be a usable build before long.
Anyone else excited? I have been dying to run a AOSP rom on my phone since release of the device.
Click to expand...
Click to collapse
I found this in the htc amaze general section. If this holds true kornyone is no longer our maintainer. Just thought i would pass this on.

AndroidBotx said:
I found this in the htc amaze general section. If this holds true kornyone is no longer our maintainer. Just thought i would pass this on.
Click to expand...
Click to collapse
Kornyone is going through a row of personal issues, so he doesn't have much time for devving. Whomever works on our device doesn't matter much to me, I just hope we don't get left behind.

dung8604 said:
Kornyone is going through a row of personal issues, so he doesn't have much time for devving. Whomever works on our device doesn't matter much to me, I just hope we don't get left behind.
Click to expand...
Click to collapse
I know that. This was just a basic announcement saying "Hey guys, we got a new maintainer" thats all.

so who is our new maintainer

xmc wildchild22 said:
so who is our new maintainer
Click to expand...
Click to collapse
Read the first post.
Also, it's about time! Kornyone's work was amazing (especially since it happened relatively early-on), but he's gone dark on us for a while and is plagued with personal issues. Maybe now our phones can function the way they're supposed to.

that is both good and bad news for me.
anyway, many thanks to Kornyone for the work he has done and good luck with his personal issues (i lurk his google+ and can fully understand why he has really no time for developing anymore)

AndroidBotx said:
I know that. This was just a basic announcement saying "Hey guys, we got a new maintainer" thats all.
Click to expand...
Click to collapse
I just hope to god that wasn't a typo >_<

This is great news. Once it's stable, people will have a great ICS base to work off of when making ROMs.

Over on the CM7 thread there is a post with a screen shot of Max's G+ stating that he is not taking on the MT4GS.
Hastily spouted for your befuddlement.

Coug76 said:
Over on the CM7 thread there is a post with a screen shot of Max's G+ stating that he is not taking on the MT4GS.
Hastily spouted for your befuddlement.
Click to expand...
Click to collapse
Just saw that. It looks like we're never getting CM on our devices.

AndroidBotx said:
I found this in the htc amaze general section. If this holds true kornyone is no longer our maintainer. Just thought i would pass this on.
Click to expand...
Click to collapse
It was a mistake, I thought he was, must have just been my mind playing tricks on me, and assuming something I THOUGHT I read months ago was accurate, I'll edit the post referenced, sorry to burst your bubble guys.

We need a new developer for this device. We need CM.
Delivered via candygram for Mr. Mongo.

I don't understand the issues :3 Where going to have CM9. If you've noticed, CM9 hasn't been officaly released(Only 3, 4 devices on the mirror). Many phones lack the proper files to make the camera work. There's so many issues, there's just a lot of KANGs. We could have CM9 now, but there's no working camera with AOSP ICS. Otherwise TB would have had a AOSP/AOKP/CM9.
Sent from my HTC myTouch_4G_Slide using Tapatalk

AgentCherryColla said:
I don't understand the issues :3 Where going to have CM9. If you've noticed, CM9 hasn't been officaly released(Only 3, 4 devices on the mirror). Many phones lack the proper files to make the camera work. There's so many issues, there's just a lot of KANGs. We could have CM9 now, but there's no working camera with AOSP ICS. Otherwise TB would have had a AOSP/AOKP/CM9.
Sent from my HTC myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
The issue is that we could have at least had CM 7.0.3 by now instead of AOSP-like ROMs still built on the memory- and power-consuming Sense framework.

blackknightavalon said:
The issue is that we could have at least had CM 7.0.3 by now instead of AOSP-like ROMs still built on the memory- and power-consuming Sense framework.
Click to expand...
Click to collapse
Its not the sense framework that is a memory hog. Its all the system apps like sense widgets. Rosie launcher. Added bloatware. Etc etc. If you remove those memory hogs and use the sense framework it would do as well if not better then aosp. I ran undeads RubiX ICS and it had sense framework. But it was super stable and battery lasted crazy long. Sense framework also keeps the ability to use the sense camera. There are way more pros then cons.

AndroidBotx said:
Its not the sense framework that is a memory hog. Its all the system apps like sense widgets. Rosie launcher. Added bloatware. Etc etc. If you remove those memory hogs and use the sense framework it would do as well if not better then aosp. I ran undeads RubiX ICS and it had sense framework. But it was super stable and battery lasted crazy long. Sense framework also keeps the ability to use the sense camera. There are way more pros then cons.
Click to expand...
Click to collapse
You mean to tell me that nobody has the know-how to reverse engineer the drivers on this thing?
Delivered via candygram for Mr. Mongo.

blackknightavalon said:
You mean to tell me that nobody has the know-how to reverse engineer the drivers on this thing?
Delivered via candygram for Mr. Mongo.
Click to expand...
Click to collapse
I have the knowledge. But im all bout the money. Development of android shows no return for time invested. Long story short i dont want to dev unless the donations are guaranteed. I got my kernel code for cm7 up on my git for the most part. But i still have some "Unfinished Business" to attend to before making my git public for others to "Kang" from. There is still that nasty battery drain bug. Im going to put a second git together with a full device tree for doubleshot so other devs can put together better Aosp Roms. In the mean time I will compile cm7 from the htc glaciers git and merge it with doubleshot. Luckily the doubleshot has all the needed GB Drivers. Libs. Binaries. Etc etc to make it fully functioning direct from htc.

AndroidBotx said:
I have the knowledge. But im all bout the money. Development of android shows no return for time invested. Long story short i dont want to dev unless the donations are guaranteed. I got my kernel code for cm7 up on my git for the most part. But i still have some "Unfinished Business" to attend to before making my git public for others to "Kang" from. There is still that nasty battery drain bug. Im going to put a second git together with a full device tree for doubleshot so other devs can put together better Aosp Roms. In the mean time I will compile cm7 from the htc glaciers git and merge it with doubleshot. Luckily the doubleshot has all the needed GB Drivers. Libs. Binaries. Etc etc to make it fully functioning direct from htc.
Click to expand...
Click to collapse
DHD took 100's of hours to get a camera driver. Its understandable that you'd want money. I'm sure if you could prove to the community your good (your CM7/AOSP Gethub). We'd start up a bounty thread.
Sent from my HTC myTouch_4G_Slide using Tapatalk

AgentCherryColla said:
DHD took 100's of hours to get a camera driver. Its understandable that you'd want money. I'm sure if you could prove to the community your good (your CM7/AOSP Gethub). We'd start up a bounty thread.
Sent from my HTC myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
Yes but that means doing the work first (With zero guarantee) of return. The kernel source was super simple. I dont want anything for that git. But building a complete device tree your talking hundreds of hours as you stated. I will see what can be done.

AgentCherryColla said:
DHD took 100's of hours to get a camera driver. Its understandable that you'd want money. I'm sure if you could prove to the community your good (your CM7/AOSP Gethub). We'd start up a bounty thread.
Sent from my HTC myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
I second a bounty thread with a PayPal donation link. Devs should be compensated for their work.

[DEV/ROM][FROM SOURCE][CAF GB 2.3.6][build #20][3/21]

Here is my Skyrocket ROM built from Code Aurora Forum source. This is Android 2.3.6. It is not even close to a daily driver and probably never will be.
DO NOT INSTALL THIS UNLESS YOU ARE VERY EXPERIENCED IN DEBUG AND KNOW HOW TO USE 'adb'.
I am posting this to help with the effort to build a community ICS ROM. Perhaps my device tree will help. As such, I do not plan on spending any more time debugging the issues with the rom. I would rather focus on helping the community get an ICS build going.
Link to my device tree: https://github.com/dferg/android_device_msm8660_skyrocket
Link to build instructions: https://github.com/dferg/android_device_msm8660_skyrocket/blob/master/README.md
Link to Code Aurora Forum: https://www.codeaurora.org/xwiki/bin/QAEP
Link to the ROM (build #20): http://d-h.st/gU2
What works?
calls (no audio), sms, 2D graphics, wifi, bluetooth
What doesn't work?
cell data, audio, nfc, int+ext sdcards
Instructions for install:
In CWM, wipe factory
In CWM, install this zip
Reboot + wait up to 3 minutes
If you get the lock screen with no way to unlock, connect to your computer and run "adb reboot". You should then get the proper unlock slider.
Notes:
sdcard is detected incorrectly, so do NOT allow it to attempt a format (it will say 'damaged sdcard'--just ignore this)
Even though it says "No SIM Card" calls in and out will work, although no audio...

Updates: 3/21/12
Added link to build instructions on Github
Pushed commits to Github that simplify the build

reserved...........2

You should be more optimistic
It will work some day, don't think it won't ever be working.
Sent from my SGH-T989 using Tapatalk

kr3w1337 said:
You should be more optimistic
It will work some day, don't think it won't ever be working.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Agreed, and thanks for this
Sent from my SAMSUNG-SGH-I727 using xda premium

just for my understanding, what is the hurdle to getting data to work, seems like it is always the hardest thing to enable.

For gb builds on our phone I always see call audio being a hurdle
people who live in glass houses sink ships

nrm5110 said:
For gb builds on our phone I always see call audio being a hurdle
people who live in glass houses sink ships
Click to expand...
Click to collapse
Nrm is right. Audio seems to be the biggest hurdle.
This rom makes an LTE connection but the data connection just isn't used. Not sure why, but this problem seems easier than audio (which I have had no luck debugging so far)
Sent from my SAMSUNG-SGH-I727 using Tapatalk

Oh wow, if you get AOSP GB fully operational for the phone (other then call audio, dunno whats up with that), we could get CM7 working fully (with source), and get official!
I really hope you succeed.

Longcat14 said:
Oh wow, if you get AOSP GB fully operational for the phone (other then call audio, dunno whats up with that), we could get CM7 working fully (with source), and get official!
I really hope you succeed.
Click to expand...
Click to collapse
He stopped working in this for ICS.

Longcat14 said:
Oh wow, if you get AOSP GB fully operational for the phone (other then call audio, dunno whats up with that), we could get CM7 working fully (with source), and get official!
I really hope you succeed.
Click to expand...
Click to collapse
Thanks Longcat. Like alphadog pointed out, I'm not actively working on this one right now in favor of helping out the ICS efforts. But if someone else would like to collaborate or even pick up where I left off, please have at it. My reason for starting this ROM was to eventually get CM7 fully stable, as you suggested.

I wish someone would be able to pick this up I understand the importance of ics but the hurdles with gb seem far fewer than ics and would tide the masses over once I get my other hdd set up with Ubuntu I hope to take a peek
people who live in glass houses sink ships

Id love full cm7 made for this
Sent from my SAMSUNG-SGH-I727

droid512 said:
Id love full cm7 made for this
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Fyi code Aurora is different than cm lol
people who live in glass houses sink ships

FYI: I updated the OP with a link to the build instructions. I also pushed changes to my Github that simplifies and cleans up some of the build.

topprospect said:
FYI: I updated the OP with a link to the build instructions. I also pushed changes to my Github that simplifies and cleans up some of the build.
Click to expand...
Click to collapse
Just fyi. Eugen373 is working on aosp for t989. Apparently with good results.

billydroid said:
Just fyi. Eugen373 is working on aosp for t989. Apparently with good results.
Click to expand...
Click to collapse
Any links on him talking about status of it for us to follow? I checked 989 general and dev real fast. Didn't see anything.

R4INS said:
Any links on him talking about status of it for us to follow? I checked 989 general and dev real fast. Didn't see anything.
Click to expand...
Click to collapse
Yes, a link to his post would help. I searched XDA and Github, finding only stuff about Vibrant roms that he has done.

topprospect said:
Yes, a link to his post would help. I searched XDA and Github, finding only stuff about Vibrant roms that he has done.
Click to expand...
Click to collapse
It's from twitter, eugen373. Not sure if he has pushed anything to github. You can ask him, he is extremely helpful guy.
Sent from my SGH-I777

Eugene's Twitter Post
billydroid said:
It's from twitter, eugen373. Not sure if he has pushed anything to github. You can ask him, he is extremely helpful guy.
Sent from my SGH-I777
Click to expand...
Click to collapse
Check https://twitter.com/#!/Eugene373. Looks like he is very close,

Thunderbolt Development Activity (GITHUB)

The GITHUB public activity pages are a great way to get a general idea of the work that is going into building the Thunderbolt JB kernel.
Here is a listing of the developers that are working on the Thunderbolt according to their GITHUB public activity pages. I didn't list developers that don't have ICS/JB activity (assuming they have retired from the TB). Click on each link to view their GITHUB public activity.
elginsk8r
Flyhalf205
jblack248
liquid0624
LoungeKatt (TwistedUmbrella)
MongooseHelix
santod
sbryan12144
ziggy471
A GITHUB public activity page does not show all the activity, so keep that in mind.
The developer listing is in alphabetical order based on their GITHUB userID.
A big thanks to all of the DEVs, and please correct me if I missed anyone.
Thanks!

Hey, this is a cool list. It's nice to know people are keeping us honest.
We recently started an organization on github to collaborate easier, so that should be the main place you need to look if you want to stay updated.
https://github.com/LiquidMecha

jblack248 said:
Hey, this is a cool list. It's nice to know people are keeping us honest.
We recently started an organization on github to collaborate easier, so that should be the main place you need to look if you want to stay updated.
https://github.com/LiquidMecha
Click to expand...
Click to collapse
Very Cool! Thanks!

jblack248 said:
Hey, this is a cool list. It's nice to know people are keeping us honest.
We recently started an organization on github to collaborate easier, so that should be the main place you need to look if you want to stay updated.
https://github.com/LiquidMecha
Click to expand...
Click to collapse
Hi jblack, I've been following the liquidmecha development? It looks like you and liquid have been working on the RIL code for jellybean.
Is the RIL code the last major component in the jb development? Or are we talking about major hurdles across the board?
Thanks!
Sent from my ADR6400L using Tapatalk 2

blackshoes said:
Hi jblack, I've been following the liquidmecha development? It looks like you and liquid have been working on the RIL code for jellybean.
Is the RIL code the last major component in the jb development? Or are we talking about major hurdles across the board?
Thanks!
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
You're correct; the radio is the last major component left to get working on JB. Right now we're trying to get baseband to work. I've been pretty busy lately, so Liquid and Santod have been the main guys working on the radio. disconnecktie ha been an incredibly helpful tester thus far, and he also has his own kernel going. Everything else has been reported to work, including the camera and camcorder (not 720p, though). The radio has been especially difficult.

blackshoes said:
Hi jblack, I've been following the liquidmecha development? It looks like you and liquid have been working on the RIL code for jellybean.
Is the RIL code the last major component in the jb development? Or are we talking about major hurdles across the board?
Thanks!
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Whats wrong with the RIL is the ramdisk permissions. The RIL should work, but without the correct ramdisk permissions, the radio itself wont power on, which is the problem we are dealing with now. Think of it this way, you have a pin # to unlock your phone but you have forgotten it, and now you need to try every possible combination you can think of until you land on the right one, and then your phone will unlock. Thats how the problem has to be solved basically.

jacobmacek said:
Whats wrong with the RIL is the ramdisk permissions. The RIL should work, but without the correct ramdisk permissions, the radio itself wont power on, which is the problem we are dealing with now. Think of it this way, you have a pin # to unlock your phone but you have forgotten it, and now you need to try every possible combination you can think of until you land on the right one, and then your phone will unlock. Thats how the problem has to be solved basically.
Click to expand...
Click to collapse
Ouch! That doesn't sound good.
Sent from my ADR6400L using Tapatalk 2

jacobmacek said:
Whats wrong with the RIL is the ramdisk permissions. The RIL should work, but without the correct ramdisk permissions, the radio itself wont power on, which is the problem we are dealing with now. Think of it this way, you have a pin # to unlock your phone but you have forgotten it, and now you need to try every possible combination you can think of until you land on the right one, and then your phone will unlock. Thats how the problem has to be solved basically.
Click to expand...
Click to collapse
Jacobmacek, thanks for the info. How big of an obstacle are we talking about? Could this potentially prevent the DEVs from getting the radio to work with JB?

blackshoes said:
Jacobmacek, thanks for the info. How big of an obstacle are we talking about? Could this potentially prevent the DEVs from getting the radio to work with JB?
Click to expand...
Click to collapse
Meh, depends on how you look at it, it's really just a matter of time

blackshoes said:
Jacobmacek, thanks for the info. How big of an obstacle are we talking about? Could this potentially prevent the DEVs from getting the radio to work with JB?
Click to expand...
Click to collapse
Since you included the word "potentially", yes, potentially it could prevent it

hallstevenson said:
Since you included the word "potentially", yes, potentially it could prevent it
Click to expand...
Click to collapse
"So you're telling me there's a chance"

Don't think to much into it people. Data will work it will just take time and lots of testing. Be patient and it will come.
Sent from my ADR6400L using Tapatalk 2

disconnecktie said:
Don't think to much into it people. Data will work it will just take time and lots of testing. Be patient and it will come.
Click to expand...
Click to collapse
It was a joke... Geez... It's like someone asking "is it possible that 'x' will happen by tomorrow?" and responding, "yes, it's possible" is 100% true.

Sorry if I sounded like a jerk. I wasn't trying to. Lots of time is being put into getting them to work. I will say that it's close. The radios turn on but are turning themselves off during the boot process.
Sent from my ADR6400L using Tapatalk 2

I also wasn't trying to take away anything in regards to the efforts involved in that either. I was simply playing on the hypotheticals that the person included in their question. I couldn't resist answering hypothetically as well !

disconnecktie said:
Lots of time is being put into getting them to work. I will say that it's close. The radios turn on but are turning themselves off during the boot process.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
You know, I really appreciate updates like this. It is so much easier to avoid laying around whining like a kid in the back seat on a road trip when we hear progress reports once in a while.
Sent from my NuSenSex Sense 4 Bolt using Tapatalk 2

I agree, it's nice to see progress is being made.
Once they get the radio working and fully functional JB roms start hitting the Thunderbolt, I hope that XDA's portal page will display the news. I was sorta surprised that the XDA homepage didn't at least give a one-liner when the ICS source was released by HTC. We all waited for so long and there were so many articles about how HTC was delaying the release, and then when the source was released....not one article or blurb.
I'm just hoping that the XDA portal page will give the Thunderbolt a little love when JB is ready. That may spark other news outlets to follow the fact that this older device is still being supported by the DEVs.

blackshoes said:
I agree, it's nice to see progress is being made.
Once they get the radio working and fully functional JB roms start hitting the Thunderbolt, I hope that XDA's portal page will display the news. I was sorta surprised that the XDA homepage didn't at least give a one-liner when the ICS source was released by HTC. We all waited for so long and there were so many articles about how HTC was delaying the release, and then when the source was released....not one article or blurb.
I'm just hoping that the XDA portal page will give the Thunderbolt a little love when JB is ready. That may spark other news outlets to follow the fact that this older device is still being supported by the DEVs.
Click to expand...
Click to collapse
Agreed. It would be awesome to see an article, and also recognition of the hard work of liquid, santod, jblack, and twisted.

I added Flyhalf205 GITHUB activity to the list.

I'm not all that shocked about the lack of Thunderbolt love on the portal. When the Nexus S 4G got ICS, yes.. a developer phone, they didn't say much either. One of the DEV's for that phone managed to get a working version of ICS built for it based off the SDK, which technically shouldn't have worked, but it did. They didn't even show love for that.
No need to worry though, the Thunderbolt community know where our bread is buttered. :laugh: