Related
The topic says it all, we NEED developers for the SGH-I897 or we will never get official CM support for our phones. So get out there and finish what coolya and codeworkx started for us. Fork these git trees and get coding!
Kernel: https://github.com/coolya/android_kernel_samsung
Device Tree: https://github.com/coolya/android_device_samsung_captivate
Vendor Tree: https://github.com/coolya/android_vendor_samsung_captivate
Build information (and how pull the repos): http://code.google.com/p/cyanogenmod7-for-samsung-galaxys/wiki/HowToBuild
Official Thread:
http://forum.cyanogenmod.com/topic/15169-sgh-i897-cm7-work-in-progress/
it doesn't sound like official support will ever come. Maybe the i9000 build can be reoriented once released
SkitchBeatz said:
it doesn't sound like official support will ever come. Maybe the i9000 build can be reoriented once released
Click to expand...
Click to collapse
I'm running the i9000 build, with the headset jack fix, it's perfectly fine.
I don't understand why it is so good. I looked at it and doesn't look that special. But what do I know? Im perfectly happy with my phone with what we currently have available.
Sent from my Captivate running Cezar's Continuum v.2.0 with SuckerPunch 1280mhz kernel.
jjtitus098 said:
I don't understand why it is so good. I looked at it and doesn't look that special. But what do I know? Im perfectly happy with my phone with what we currently have available.
Sent from my Captivate running Cezar's Continuum v.2.0 with SuckerPunch 1280mhz kernel.
Click to expand...
Click to collapse
Some of us love aosp, and cm is probably the best soap build out there. Oh, and that screen off animation is glorious.
Sent from my Captivate using XDA App
uberushaximus said:
The topic says it all, we NEED developers for the SGH-I897 or we will never get official CM support for our phones. So get out there and finish what coolya and codeworkx started for us. Fork these git trees and get coding!
Click to expand...
Click to collapse
What a better way to get Dev's NOT to do a project, demand they get coding. Here's a thought, you found your way there, do it yourself!
BTW, I'm no Dev and don't plan to be.
about coding
I would love to code and work on this rom and i have the time. But I dont know how to code. If anbody wants to message me or reply or create a post i would love it to learn.
sorry i suck at spelling
squishy5 said:
I would love to code and work on this rom and i have the time. But I dont know how to code. If anbody wants to message me or reply or create a post i would love it to learn.
sorry i suck at spelling
Click to expand...
Click to collapse
*facepalm* Okay, first off, you most certainly cannot learn C from a single forum post, you certainly can't become fluent in it without a couple of months put into it, and kernel deving is probably one of the hardest types of programming.
By all means, learn, but don't think it's something you can just look at and immediately know what you're doing.
jjtitus098 said:
I don't understand why it is so good. I looked at it and doesn't look that special. But what do I know? Im perfectly happy with my phone with what we currently have available.
Sent from my Captivate running Cezar's Continuum v.2.0 with SuckerPunch 1280mhz kernel.
Click to expand...
Click to collapse
I completely agree with you CM is nothing special
TheEscapist said:
I'm running the i9000 build, with the headset jack fix, it's perfectly fine.
Click to expand...
Click to collapse
So what exactly do you have to modify in the kernel to get the proper orientation or the headset jack fix?
And is your vibration extremely weak too?
Moosehunter said:
So what exactly do you have to modify in the kernel to get the proper orientation or the headset jack fix?
And is your vibration extremely weak too?
Click to expand...
Click to collapse
To get proper headset logic, just replace you /path/to/cm/kernel/samsung/2.6.35/drivers/misc/sec_jack.c with the attached one (renamed to sec_jack.c, obviously). Alternatively, add the lines
Code:
#if defined(CONFIG_SAMSUNG_CAPTIVATE)
pdata->det_active_high = 1;
#endif
to the file between dev_set_drvdata(&pdev->dev, hi); and return 0; (near the bottom).
Orientation has not been fixed yet, someone just needs to port over xcals reorient. Whether that's me or someone else doesn't really matter.
And yeah, weaker than stock, for sure. Not unusable, by any means though.
TheEscapist said:
To get proper headset logic, just replace you /path/to/cm/kernel/samsung/2.6.35/drivers/misc/sec_jack.c with the attached one (renamed to sec_jack.c, obviously). Alternatively, add the lines
Code:
#if defined(CONFIG_SAMSUNG_CAPTIVATE)
pdata->det_active_high = 1;
#endif
to the file between dev_set_drvdata(&pdev->dev, hi); and return 0; (near the bottom).
Orientation has not been fixed yet, someone just needs to port over xcals reorient. Whether that's me or someone else doesn't really matter.
And yeah, weaker than stock, for sure. Not unusable, by any means though.
Click to expand...
Click to collapse
Adding that line makes the headset work, but it kills wifi.
Edit: Actually, some changes that I made to the kernel yesterday also killed wifi. I don't know what's up there.
Moosehunter said:
Adding that line makes the headset work, but it kills wifi.
Edit: Actually, some changes that I made to the kernel yesterday also killed wifi. I don't know what's up there.
Click to expand...
Click to collapse
Yeah, latest captivate kernels kill wifi. I'm going to do some digging when I get home tonight, cause galaxys kernels work fine.
TheEscapist said:
Some of us love aosp, and cm is probably the best soap build out there. Oh, and that screen off animation is glorious.
Sent from my Captivate using XDA App
Click to expand...
Click to collapse
This --^ I'm with you 100% on that.
TheEscapist said:
Yeah, latest captivate kernels kill wifi. I'm going to do some digging when I get home tonight, cause galaxys kernels work fine.
Click to expand...
Click to collapse
But the weird thing is that if I make any changes, even a single line, wifi breaks. If I go back and delete that line, wifi works again. So I guess for now it's either headset fix + voodoo sound w/o wifi, or no headset fix or voodoo sound, but with working wifi.
If there isn't a working captivate based rom/kernel for cm7 after about 2-3 weeks I will have some time to get working on this.
ytt3r is gonna be building a kernel in the next couple of days. he is asking for testers i believe.
I just reoriented and fixed headset jack. I'm going to compile tomorrow and see what's up. Since coolya's repo is broken, I still don't have source and I haven't compiled the rom, just the kernel. #cm7oncappy on freenode.
ytt3r said:
I just reoriented and fixed headset jack. I'm going to compile tomorrow and see what's up. Since coolya's repo is broken, I still don't have source and I haven't compiled the rom, just the kernel. #cm7oncappy on freenode.
Click to expand...
Click to collapse
Is this based on I9000?
ytt3r said:
I just reoriented and fixed headset jack. I'm going to compile tomorrow and see what's up. Since coolya's repo is broken, I still don't have source and I haven't compiled the rom, just the kernel. #cm7oncappy on freenode.
Click to expand...
Click to collapse
I can test the kernel if you post the changes.
Could somebody thats gotten this working with the Mesmerize help me. I've switched out the apns xml file, added the cdma xml, and edited the build.prop. I have yet to get data working, though, I've flashed everything, back and forth, several times each. Anybody that could help would be greatly appreciated.
KillKount said:
Could somebody thats gotten this working with the Mesmerize help me. I've switched out the apns xml file, added the cdma xml, and edited the build.prop. I have yet to get data working, though, I've flashed everything, back and forth, several times each. Anybody that could help would be greatly appreciated.
Click to expand...
Click to collapse
We are currently working on this right now. It should be posted sometime soon.
dfgas said:
We are currently working on this right now. It should be posted sometime soon.
Click to expand...
Click to collapse
Thanks, can't wait. You are the man when it comes to the "other" i500 phones.
KillKount said:
Could somebody thats gotten this working with the Mesmerize help me. I've switched out the apns xml file, added the cdma xml, and edited the build.prop. I have yet to get data working, though, I've flashed everything, back and forth, several times each. Anybody that could help would be greatly appreciated.
Click to expand...
Click to collapse
Have you gotten issues worked out that JT still has? IE: are you basically trying to convert JTs build only for mesmeriize, or are you going above and beyond and fixing issues like camera, bt, etc?
I just still haven't gotten data working with anything I've tried, I am by no means a real dev like dfgas and jt. So, I am just trying to get it ported for awesomeness.
I am just trying to get it ported for awesomness
Click to expand...
Click to collapse
thats too much man... quote of the day right there!
kallell said:
Have you gotten issues worked out that JT still has? IE: are you basically trying to convert JTs build only for mesmeriize, or are you going above and beyond and fixing issues like camera, bt, etc?
Click to expand...
Click to collapse
Those issues exist on all AOSP builds. Just something you have to deal with until they can figure out fixes for them.
I wonder if the mms patch from the comrom would work? Or is that just ridiculous!?!
Sent from my SCH-I500 using XDA Premium App
ssgtrod said:
I wonder if the mms patch from the comrom would work? Or is that just ridiculous!?!
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
No, comm rom is Touchwiz based, that only replaces the mms app. I think it would only further break mms in an AOSP rom. The problem is deeper in AOSP roms. That sure would be nice, though!
ssgtrod said:
I wonder if the mms patch from the comrom would work? Or is that just ridiculous!?!
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
If your thinking that it would fix mms, it wouldn't, all aosp roms have this problem for us.
Darn, got ninja'd.
The issues with MMS/Camera on AOSP rom's are very difficult, there is no easy fix or it would have been done already . From what we have gathered, the problem with MMS lies in WAP (among other things) - we can get it to locate the correct server (and i believe it even connects) but then we get errors referencing WAP not being enabled, therefore not getting the push from the server. One suggestion was that maybe something in the kernel needed to be tweaked, but we haven't gotten any further with testing that theory. Keep in mind most of us putting up ROM's and such in here are not "real" developers, meaning we haven't built anything from source (as far as for the android OS) and therefore we don't really have the capability of fixing such issues. Most of us have been self teaching and learning from others how to "kang" (port) ROM's that have been developed for other phones, that's why you're seeing these drops, so please keep that in mind .
Some developers, such as jamezelle, jt1134, and adrynaline, have been looking at the issues since the beginning, and if they haven't had any luck with current resources - then chances are until we locate certain source or come up with a work-around that they haven't thought of - things will remain as is.
here is an update on the rom, its not looking good, when L3ttuc3 makes the necessary edits to the framework we get a fc when we receive a sms and try to send one.
If there is anyone on EC01 radio then it will work perfect, however EC01 radio only works on mesmerize.
dfgas said:
If there is anyone on EC01 radio then it will work perfect, however EC01 radio only works on mesmerize.
Click to expand...
Click to collapse
Would it be possible to upload the fix files for anyone on a Mes with ec01?
KillKount said:
Would it be possible to upload the fix files for anyone on a Mes with ec01?
Click to expand...
Click to collapse
We haven't done his most recent release but here is his official 4/21 drop with the appropriate fixes for mesmerize; remember this requires EC01 radio already installed and follow jt's instruction's
Download CM7 Mesmerize for ED01
bdemartino said:
We haven't done his most recent release but here is his official 4/21 drop with the appropriate fixes for mesmerize; remember this requires EC01 radio already installed and follow jt's instruction's
Click to expand...
Click to collapse
Thank you guys so much, I am going to take a look at it and see if I cant get data working for me on the 4/26 build, after that it will be on par with jt's.
KillKount said:
Thank you guys so much, I am going to take a look at it and see if I cant get data working for me on the 4/26 build, after that it will be on par with jt's.
Click to expand...
Click to collapse
If you pull up the build.prop in the link i posted and compare to his and make the same changes - your data should work. We haven't had to tweak anything to get data working so i'm thinking an incorrect change in build.prop could be the case - or you could just be unlucky
bdemartino said:
If you pull up the build.prop in the link i posted and compare to his and make the same changes - your data should work. We haven't had to tweak anything to get data working so i'm thinking an incorrect change in build.prop could be the case - or you could just be unlucky
Click to expand...
Click to collapse
That's going to be step 2, right now I'm making sure data works for me on yours.
Btw, account setup gets really annoying after about 100 login attempts.
KillKount said:
That's going to be step 2, right now I'm making sure data works for me on yours.
Btw, account setup gets really annoying after about 100 login attempts.
Click to expand...
Click to collapse
I always just skip the setup, all you need to do is log in to google but yea that's annnoying.
Once I have electricity again (some time next week ), I'll fix the framework so you can add a variable to build.prop that will fix SMS instead of having to make jar edits every time.
Sent from my SCH-I500 using XDA App
Ok, I flash the fixed zip, wiped everything, reboot, and... still no data. So, I odin'd back to stock, thinking I may have screwed something up, reflash... and still no data, so yeah.
The only other thing I can think of is a different radio, but I've had data on all the other ec01 mes fixed roms I've tried.
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
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,
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: