Related
http://source.android.com/
Everything happens there.
OMG !!! ICS coming soon on our DS that's NIIIIIICEEEE
I hope the API switch is simple for our belovers developpers
Yes, with that all issues will be fixed soon.
great news. i hope i can use ICS on my DS soon.
Will DS be updated by HTC officially?
The official list only contail mobile with dual core.
We don't know yet, time will answer.
I'm pretty sad to break this to you, but the chances of an AOSP build are very low because of this - http://www.androidpolice.com/2011/1...he-heavy-artillery-this-is-what-it-will-take/
Barely anyone here can have this kind of stuff. The best chance we have is waiting for a build for Desire HD (It's the most likely HTC device to get one) and then superkid will port it.
Our Desire S will get the update prior to Desire HD.
Check out this link... Source
cheer!!!
I don't mean an official update from HTC, i mean a custom ROM built from source by XDA devs. That, DHD is sure to recieve first, the devs there are too many.
okay, but i guess Cyanogenmod will build it from the source
shrome99 said:
I'm pretty sad to break this to you, but the chances of an AOSP build are very low because of this - http://www.androidpolice.com/2011/1...he-heavy-artillery-this-is-what-it-will-take/
Barely anyone here can have this kind of stuff.
Click to expand...
Click to collapse
Sorry but why do you think so? This is not sooo extra ordinary... If you don't have such hardware you could also put the build to the cloud. Also these are recommendations! You can also build on lower resources it just takes longer
longer then 5 hours? wow xD
shrome99 said:
I'm pretty sad to break this to you, but the chances of an AOSP build are very low because of this - http://www.androidpolice.com/2011/1...he-heavy-artillery-this-is-what-it-will-take/
Click to expand...
Click to collapse
My laptop compiles Gingerbread fine. I doubt ICS will be a problem.
Well, mine compiles ginger bread too, but recommended was lot lower... anyways... its gonna be okay
Then, can we expect ICS within the next week? You're the only one i'm looking up to, you have the most experience in AOSP
a week?!!!! are u kiding?!!! i want it right now!!! give me that!!
jacob73 said:
a week?!!!! are u kiding?!!! i want it right now!!! give me that!!
Click to expand...
Click to collapse
Relax......
i waaaant iiiiiit!!
seriously guys! i cant wait anymore!how u can?!! tired , i have to connect charger to phone every 3 hours! and the only rom i liked is miui ,and it have some bug and not perfect, somtimes thev touch is going to lazy!!! and it doesn't work properly, and when i select a text in browser,it pass away! and show force close!
sorry i know i shouldn't tell these in here, but i guess superkid read this! and i want to say the google officialy roms, and other stock roms are the best roms!
sorry! know it's tribble to read my post! u must used to that!!!
The first port with sources on the galaxy s
Sent from my HTC Desire S using XDA App
Boom!
Cyanogen Mod Promise CM9 To All 60 Supported Devices In The Next Two Months:
http://blog.gadgethelpline.com/cyanogen-mod-promise-cm9-60-supported-devices-months/
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
Please keep all comments relevant to development status, beta testing, and resolving issues compiling I.C.S to avoid closure of thread.
This way if you are not developing you can read to keep up-to-date.
P.s: thank you to all our wonderdul devs working night and day to get us a stable build!
Sent from my HTC Sensation Z710e using XDA App
there is no current active ICS port on XDA mate
yes, unfortunately there is noc ICS Port on XDA...
So lets hope for CM9 soon
Stegerius said:
yes, unfortunately there is noc ICS Port on XDA...
So lets hope for CM9 soon
Click to expand...
Click to collapse
this probably shows how much of a loved device the Sensation is among XDA devs...
just had a look over on Samsung Galaxy S and they have already 2 working ICS ports...with camera, face unlock and stuff...
didn't bother checking GS2...
the mods keep closing all the threads for ics development
Sent from my TripNiCE Pyramid using XDA App
Sent from my Sensation using XDA App
you can download sensation ICS here MOD EDIT: NO EXTERNAL LINKS!!!!
I'm currently testing that version and i find it very stable but a lot of apps still doesnt work. Still good job for this alpha version
vladnosferatu said:
you can download sensation ICS here
Click to expand...
Click to collapse
Seriously people ... how many times should the mods say that external links to Trip's work is not allowed?
No wonder all the ICS' threads are being locked
this is a video of how far we have gone porting ICS on our device
youtu.be/yItyVGxlVgE
I guess it doesn't matter much.. This thread will be close or die out since there's nothing to discuss here about ics..
F4M0U569 said:
this is a video of how far we have gone porting ICS on our device
youtu.be/yItyVGxlVgE
Click to expand...
Click to collapse
that's the ICS port's name that cannot be spoken about here
it's like Sauron's ROM or something
I wont post a link to the page, but looking at Kmobs Google+, he posted a few pictures comparing his Sensation and Galaxy Nexus.
-In one picture he shows the 'about phone' screen on both phones. On Sensation, it looks like there is a color gradient, however its hard to tell. So MAYBE they have hardware acceleration working.
-Also if you read the 'mod version' it says CyanogenMod-9.0.0-RC0-Sensation-KANG. I'm a noob and Im not sure if the mod version will tell anything, but it says RC0 so maybe its Release Candidate status?
-One last thing I noticed is he has the same widget running when he compares homescreen, so he is kind or mirroring the two, but the Galaxy Nexus has the camera shortcut on the homescreen and Sensation does not. Not sure if that means its not working on Sensation, or if he just didnt put it there
Mods: if I posted anything I shouldnt have, please feel free to delete the post and contact me. Im familiar to the rules for the most part.
zerozoneice said:
that's the ICS port's name that cannot be spoken about here
it's like Sauron's ROM or something
Click to expand...
Click to collapse
Aaaaaand its working quite well I just had to test it...and stay on it
vladnosferatu said:
you can download sensation ICS hereQUOTE]
Have downloaded and am runnung/setting up as we speak, btw why aren't the xda devs working on a ICS port, seems bonkers to mw
Click to expand...
Click to collapse
zerozoneice said:
this probably shows how much of a loved device the Sensation is among XDA devs...
just had a look over on Samsung Galaxy S and they have already 2 working ICS ports...with camera, face unlock and stuff...
didn't bother checking GS2...
Click to expand...
Click to collapse
lol. should compare date released and prices for devices. the longer the date the device was released and the cheaper price it is, it should have many devs and support for it. as our devices is quite new (not that new lol) but its like a decisive thing for devs really, if they want to get the sensation and create ports there or just go to the newest device there is on the market. but needless to say, we have plenty of devs here. its just a matter of enjoying whats there and being patient. so, stay on and relax
nickclarke said:
Have downloaded and am runnung/setting up as we speak, btw why aren't the xda devs working on a ICS port, seems bonkers to mw
Click to expand...
Click to collapse
It seems like developement for the Sensation is slowly dying.Looks like all the good devs have jumped ship to newer phones It's kinda depressing since the phone is only 6 months old.I wish i could afford to buy a new phone every 6 months.
NYCguy2020 said:
It seems like developement for the Sensation is slowly dying.Looks like all the good devs have jumped ship to newer phones It's kinda depressing since the phone is only 6 months old.I wish i could afford to buy a new phone every 6 months.
Click to expand...
Click to collapse
Sadly, but true....
We have a good collection of roms though, and we will be getting ICS regardless from HTC. I don't mind if devs jump ship.
Yeah, TripNiCE ROM is now Alpha 7.5, quite perfect and very stable.
It seems that we could have a stable release (or two if CM9/Kang release something too) till Christmas !
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
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: