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:
Related
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
ICS ANDROID QUESTIONS GO HERE!!!!!
Quite frankly im sick of seeing a new thread or an old thread revised every 4 weeks. Basically from the point of a dev and a fan I am submitting this thread. I want to see every old or dev thread closed and all questions or suggestions pointed here.
I have personally exhausted most of my resources trying to fix the problems we have within our tegra g2x builds. This device is completely closed source rather like to admit it or not. blame it on all you want to.ether
The bottom line is lg and nvidia only releases source for their bottom line **** that makes tegra work, and we have done patched that in and made it work to some extents.
Yes Alot of us devs can make cm9 work and alot of us can make aosp4.0.3+ work. but they will not opensource their work. To the same extent we where stuck at with the vibrant and the gps issue.
All i can say is do not buy another lg device or another tegra device. Yes the transformer is bad ass, but if you protest to a level to where no one wants there work they will be forced as an oem to make there manufactures push their source and make it relevant to the point the oems do.....
Thanks for this, all the other ones seem really useless and never stay on track anyway. . I wonder how long it'll take before some guy trolls the hell out of this one. Lets try to keep this one only pertaining to AOSP ICS or CM9 development and/or progress.
This works...but at some point it will get off track...most of the people that are in the the other threads can't get a working build and since we don't have any builds to test anymore its tough to stay on topic with something you aren't using.
Sent from my LG-P999 using XDA App
Forget ics wheres the new weapon rom is wat im after!
kwes1020 said:
This device is completely closed source rather like to admit it or not.
Click to expand...
Click to collapse
Yea, that's crap, I mean, one of the things I like about Android is the open-sourceness. If only OEM's would realize that an open-source system will, in my opinion at least, get more and better support FROM THE COMMUNITY tahn a totally closed system. Take Windows for example, we all have have things to complain about and most can't do that much, even with third-party programs which can be used to correct problems or bugs or add features. On the other hand, there's a game series I follow where the Dev's explicitly made the games open for easy modification, the only "closed" part is the actual engine itself which was developed from scratch. And what resulted was a fan base who took initiative to correct bugs and add features, sure people didn't like the fact that the games had bugs initially but not only did the community take action but the devs even incorporated community fixes into official patches and credited the person who made the fix. Now the dev company has gone solo and publish their own games and are due to release a fourth in the series with a strong fan base. And here we have people who will refuse to ever touch, Nvidia and/or LG ever again, and not just because of bugs, but the fact that it's closed and we get crap for official releases and fixes and crap for support.
/end rant
Ok let's get on subject, what works and what doesn't work in the ics development for our phone? I don't have a twitter or facebook so I don't keep up with the news.
Sent from my LG-P999 using xda premium
moeahmad1995 said:
Ok let's get on subject, what works and what doesn't work in the ics development for our phone? I don't have a twitter or facebook so I don't keep up with the news.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
I just compiled the aosp 4.0.3 for G2x. I used the google's sources not CM9. However it doesn't boot. I was just wondering how did you guys got it to boot?
Also, the aosp source requires recovery as well to make the otapackage. Is there any way to make the otapackage without recovery? This is not a very big issue as i can manually make the otapackage.
booting up is the big hurdle. Any help is highly appreciated
Thanks
Mr. Apocalypse said:
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
Click to expand...
Click to collapse
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
PhantomRampage said:
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
Click to expand...
Click to collapse
Well CM has had perfectly working ICS build except camera since Thanksgiving. That was like 2+ months ago, maybe they've fixed camera by now who knows.
PhantomRampage said:
Even if the CM team let you know how to fix the sound issue, wouldn't you still be at a stand-still? (camera and data)
Seems odd to include the second half of that sentence.
Click to expand...
Click to collapse
Right, unless CM got camera and data to work. And if all this is going to be open source anyhow, why the secrecy and lack of sharing? As far as I understand no one is making or going to make money off this so, what is it? Is it some petty game of who's the biggest baddest dev?
People can remember CM for being the first to release ICS for the G2x but only because they kept their work secret and didn't share or because they shared their work with others and others with them and they came out on top because they are better or they didn't because they aren't better, etc.
@moeahmad1995
Back on subject? It's a general thread which is all inclusive: "Ok all g2x ics stuff goes here!!"
Волк said:
Right, unless CM got camera and data to work. And if all this is going to be open source anyhow, why the secrecy and lack of sharing? As far as I understand no one is making or going to make money off this so, what is it? Is it some petty game of who's the biggest baddest dev?
Click to expand...
Click to collapse
I'd guess that there are many reasons for CM to keep their source closed for now, not the least of which is reputation. Also competition is one of the things that drives development. Open source is not just about giving hard work away for free.
Here's a great article that helped me to better understand the nature of open source.
Mr. Apocalypse said:
On the old alpha builds, it was sound and camera that didnt work i believe. On my build, it was data, camera and sound. Don't know about kwes' build. CM supposedly fixed the sound issue, but aren't sharing sources yet. So we're kinda at a stand-still until LG releases some source, or CM lets us know how they fixed the sound issue.
Click to expand...
Click to collapse
yeah every build I've made has the same issues as yours which is no working data sound and cam.
Sent from my Galaxy Nexus using xda premium
If there's anything I can do, let me know. I can't help much with development, but I have access to a large audience. For those who don't know, I'm a writer for ACSYNDICATE.NET and will help any way I can. Thanks for sticking with it devs, and thanks for all the new roms!
Sent from my LG-P999 using xda premium
Apparently sound has been fixed over on the O2x.
http://forum.xda-developers.com/showpost.php?p=22231818&postcount=448
Could this mean progress for us?
SefEXE said:
Apparently sound has been fixed over on the O2x.
http://forum.xda-developers.com/showpost.php?p=22231818&postcount=448
Could this mean progress for us?
Click to expand...
Click to collapse
Dammit, I was going to post that
IRASadPanda said:
Dammit, I was going to post that
Click to expand...
Click to collapse
Post it anyways!
It's a joyous occasion!
Well we need to know what they did so we can see if the fix would work on the g2x
Sent from my G2x XDA app cuz I'm stalking your mom....
http://forum.xda-developers.com/showpost.php?p=22200247&postcount=385
"
marsgod
Yesterday, 09:47 AM
# 385
I hope this help fix audio problem...
--------------------------------------------------------------------------------
Here is my fix for SU660 ICS audio...and it work for my ICS AOSP 4.0.3 (SU660 = KR version P990)
I think currently, we must use the libaudio from CM7/Stock rom.......
SO...
1. Modify star-common/BoardConfigCommon.mk
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_AUDIO_LEGACY := true
# Use dirty hack to allow froyo libaudio
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
2. Add audio.primary.p990 audio_policy.p990 into your star-common/star.mk. (This will use hardware/cm/audio. DONT USE audio.primary.tegra audio_policy.tegra!)
3. Use my hardware_legacy.tgz , extract it into star-common/include. The code is mainly from VorkTeam's github, thanks. I only made some fix in it.
4. Copy from CM7/Stock rom : libaudio.so, liba2dp.so, liblvvil.so
Audio should work now...
--------------------------------------------------------------------------------
Attached Files
hardware_legacy.tar.gz - [Click for QR Code] (5.7 KB, 12 views)"
Sweet!!!! Well we should have everything working but the camera? Ill test if anyone need be!!! Would be nice to start seeing some new alpha builds
Sent from my LG-P999 using XDA App
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.
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,
To all the XDA Motorola Triumph fans we have arrived. We have packed our bags from Android Forums and this will be our new stomping ground. We took most of the dev's and formed a collaborative team
https://github.com/WX435
We will be working on making the Motorola Triumph a much better phone and all working together to fix many issues. Right now our main goal is working on rewriting our device files for CM7 and then moving those files into CM9 and AOKP. If we continue to have success we may also start working on AOSP flavors like Gingerbread and ICS as well. Stay tuned for some radical changes and fixes!
Now we just need to talk to B_randon and Austrie
Hey I'm all in over here!! So we jumped ship at androidforums lol!! ! I have to get my buntu install back up and running on my laptop and ill be back in the dev game!
Sent from my Triumph using Tapatalk
b_randon14 said:
Hey I'm all in over here!! So we jumped ship at androidforums lol!! ! I have to get my buntu install back up and running on my laptop and ill be back in the dev game!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
Wooot! Love to see you here brandon!
We need all the help we can from our main kernel guy
Ill do what I can for sure!
Sent from my Triumph using Tapatalk
I am going to hold you to that b_randon
Lol okay! I'm not promising I can do much! My Java skills are laaaammmmeeee! I'm not even that good with c and c++!
I can't promise that me helping wont make our code explode! Lol!
Sent from my Triumph using Tapatalk
Well you have the kernel skills that is for sure! And that sir is a big deal!
Yeah I wish I had time to mess with the 2.6.35 and 3.0 kernels more! There isn't any reaseon why our phone wont run its its just a matter of porting all the triumph changes in and getting them to play nice with the newer kernels!
Sent from my Triumph using Tapatalk
Sweet. Hoping to see great things for the triumph.
Sent from my Triumph using xda premium
<Comes blinking out into the bright holy light of Devs>
You mean... people will... continue dev for my phone?!?!
<looks down at his Triumph>
Woot!
Seriously though, great to see more dev work being done for this... I think some of us had felt a little abandoned
Good luck guys, looking foreword to following your progress and trying to pick up on as much as I can.
Everything is updated here than AF. Great Team Of Devs. Looking forward to this. Im just dying for a camera on any ICS based rom
b_randon14 said:
Hey I'm all in over here!! So we jumped ship at androidforums lol!! ! I have to get my buntu install back up and running on my laptop and ill be back in the dev game!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
We're counting on you. This is the 3rd site I've followed you to....
Even tho ill most likely see it cause i check so often, im just wondering if you's are going to have like a common name for all roms released from the team or team members??
Like should i keep my eye out for [ROM][TEAM WX435] in the titles?
Tokens210 said:
Even tho ill most likely see it cause i check so often, im just wondering if you's are going to have like a common name for all roms released from the team??
Like should i keep my eye out for [ROM][TEAM WX435] in the titles?
Click to expand...
Click to collapse
That is my plan once I release CM 7.2.0, however I will be posting on both sites XDA and AF.
Hi, G60, can you comment on this latest development here: http://androidforums.com/triumph-al...d-sharp-2-2-2-triumph-mms-now-working-5.html?
It seems that using this remodeled Sharp ROM, everything in HW (including AGPS) can be made to work. Is that something which can be leveraged for general development? If so, perhaps in the spirit of team building, everyone can pull together to get one ROM out to use as a basis. Sorry, I'm a dev IRL, but don't know much about how these ROMs are built (from source? provided binaries?). I can help if we're shorthanded doing such a thing.
Thanks.
agent00f said:
Hi, G60, can you comment on this latest development here: http://androidforums.com/triumph-al...d-sharp-2-2-2-triumph-mms-now-working-5.html?
It seems that using this remodeled Sharp ROM, everything in HW (including AGPS) can be made to work. Is that something which can be leveraged for general development? If so, perhaps in the spirit of team building, everyone can pull together to get one ROM out to use as a basis. Sorry, I'm a dev IRL, but don't know much about how these ROMs are built (from source? provided binaries?). I can help if we're shorthanded doing such a thing.
Thanks.
Click to expand...
Click to collapse
agent,
Right now our focus is CM7. I am currently reworking the device files for the phone, trying to make everything perfect. I have already downloaded the sharp ROM and will dive into it more to pull out the AGPS to see if I can make it work in CM7. Right now my focus has been on the video and it's getting much better but still needs some tweaks. b_randon is working on the kernel, we are hoping to upgrade that as well. Once I have the device files done will then be reworking them into CM9 & AOKP along with kernel. It's a slow process as we have completely started from scratch. Just know we are working it :good:
Ok, thanks. I just tried out the Sharp ROM, and another thing its seems to get right is deep sleep while wifi is on. I'm not sure if it's doing it correctly or just turning it on when screen is unlocked (not sure what's default on android), but I had auto-sync on. I've never had wifi deep sleep work before (Juicedefender has a bug here). That's kind of a big deal since we've previously had to trade off battery life for speed. Wifi-on is also instant whereas it takes a while in Juicedefender.