Database Info

Samsung/XDA part2

I haven't forgot about you guys. Today we had a meeting with XDA owners via telephone. Were just getting everything ready before we make a huge announcement. I told you guys I'm NOT going to let you guys down. Just be a little patient.
Thanks
TwitterSamsungJohn

SamsungJohn said:
I haven't forgot about you guys. Today we had a meeting with XDA owners via telephone. Were just getting everything ready before we make a huge announcement. I told you guys I'm NOT going to let you guys down. Just be a little patient.
Thanks
TwitterSamsungJohn
Click to expand...
Click to collapse
I'm not sure there are a lot of expectations here to be let down. We know that in most cases you probably wouldn't be able to offer us beta, or even alpha firmware and software to develop with or on. RC firmware and software would be just as much out of the question so we're down to what is already out, or something that is leaked by people friendly to the development communities that take the chance of getting in to a lot of trouble. So I don't really know what you have to offer yet. I am curious to find out, though.

Dear john, you have sparked a lot of interest, we are drooling at the mouth do you have any gingerbread for us, or dare I speak of honeycomb? ;-)
Sent from my SCH-I500 using XDA App

"IF" this where to happen it would be a good thing for both samsung and xda for the simple fact that it would help us make better mods for the samsung community and would allow samsung to release things that are more open to modding and customizations that all of us around here love and enjoy making (or in my case learning to make)...hope all goes well with this.

I am a dubious person and do not have expectations as I am still uncertain as to your intentions and more importantly you identity.
But if all is as you say I would take back to the powers that be, many are obviously unhappy with having to run outdated software in the form of the OS on what was at the time of purchase cutting edge hardware.
Give us a option. Give us a way to open the phone up and flash a AOSP option. A more Nexus-ish approach would be fantastic.
The Mainstream will have what they require in a stock configuration and we the ones that know what the potential of the device is can help you in pushing it to its limits.

Well I'm trying to get my post count up so I can comment in development. Anywho kudos to samsung.

Thanks again John, I'm excited and look forward to hearing your announcement!
For those skeptics, he's been trying to prove that he's legit;
http://img602.imageshack.us/i/20110211164013.jpg/
http://img193.imageshack.us/i/20110211205159.jpg/
http://img46.imageshack.us/i/20110211205212.jpg/
http://img841.imageshack.us/i/20110211205219.jpg/
http://forum.xda-developers.com/showpost.php?p=11300099&postcount=78
He already posted these in the captivate forum, let's show him a better welcome while we wait for final details!

mesmerbelly said:
Dear john, you have sparked a lot of interest, we are drooling at the mouth do you have any gingerbread for us, or dare I speak of honeycomb? ;-)
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Honeycomb is made for tablets so I don't think that really helps us. And I highly doubt Samsung is going to release Gingerbread directly to XDA if at all.

akellar said:
Honeycomb is made for tablets so I don't think that really helps us. And I highly doubt Samsung is going to release Gingerbread directly to XDA if at all.
Click to expand...
Click to collapse
maybe samsung will use us for testing and maybe some tweaking...that would give us a chance to develop on it before its officially released and we would just plain out have it early, cause if you give the devs here like 2 weeks with just about anything it will be fully modded and running to its full potential!!!
props to xda devs!!!

Everyone please come over to this thread.
Thanks,
http://forum.xda-developers.com/showthread.php?p=11375386#post11375386
TwitterSamsungJohn

Hopefully their next approach works out better, they should have known better than to open a topic up to the entire forum
They should probably have moderator's from each device take questions from their users, then they could collaborate and get only the good questions answered. (and you wouldn't have to deal with trolls/flames/etc.)

SamsungJohn said:
Everyone please come over to this thread.
Thanks,
http://forum.xda-developers.com/showthread.php?p=11375386#post11375386
TwitterSamsungJohn
Click to expand...
Click to collapse
Thread Closed...
I suppose the question *since we can't ask specifics* is....
What can you do to help us and or what tools can you provide to the DEVs to help us get every bit of Awesome out of the device that we can.
Put the ball in your court.

Glad THIS thread is still open...
(Does SamsungJohn know how forums work?!?)
ANYhoo... I'm a give 'em enough rope to hang themselves kinda guy and I've actually been recommending the Mesmerize & Fascinate to friends that need new phones based solely on the great XDA community and what they can get those phones to do using only a bread tie, three pennies, and a jar of Cheez Wiz. Kudos to the devs once again!
I had no delusions that Samsung was a great manufacturer... my TV and DVD/home theater unit have had their share of problems... and I was also aware of the OS update delays in other product lines before I got my phone so that wasn't a big surprise either. BUT, I got in on the free phone thing through USCC and (if I EVER get my $80 rebate) I'll still consider being a Mesmerize owner/user a WIN.
What I see here is a classic example of a company that has the OBVIOUS solution within their grasp and they are actively choosing to find an alternative to it that will provide them SHORT TERM monetary gains. They have set themselves up for failure and they have only themselves to blame. Here's a vocabulary lesson for SamsungJohn et al... crowdsourcing

Guys if you haven't read through it, that topic was closed by a moderator because it was an experiment that failed miserably. (because the general XDA population isn't very good at reading and following instruction, and it turned into a huge flamefest.)
John has been confirmed by several sources to be who he says he is (at least works for samsung) and is here working with the XDA administration to (in an organized way) swap feedback with the developing community (on all samsung products).
On a side note Supercurio has been in correspondence with Korean Samsung and has been also pushing for this very thing to happen, but from what I've read i'ts pure coincidence that John arrived when he did.
Anyway, sounds to me like we need to be patient as information IS coming as soon as they figure out the best way to go about this whole thing. This is how I've taken things from what I've read today, don't quote me....

monthlymixcd said:
Here's a vocabulary lesson for SamsungJohn et al... crowdsourcing
Click to expand...
Click to collapse
In all fairness Crowdsourceing is what the whole AOSP is about. Android was and is developed to be Open Source. So if a company is reaching out to the community it can't be all bad.
I just think that for the most part a lot of us here are end users.
While I am sure that others like me want to, and strive to learn more, we simply will not be on a par with the current crop of DEVs as they progress as well.
I think the idea of a couple DEVs from each of the respective forums of the variations of the SGS platforms being in contact is a smart idea.
Dcows, Phidelt, and of course JT and many of the OPs in the Samsung Fascinate IRC channel would be obvious choices.
In fact a meeting of the minds in a channel of choice with only participants having voice would be nice as well.
I do understand and hope that SamsungJohn does know as well that most here are simply end users and just wanna know when we will get xxx or yyy ..
I will now go back to my corner get my Java Text out and see if I can learn, learn, learn....

If samsung really wants to get in good with the developement community, they would be wise to make it entirely official, and go to engadget or someone with a press release. If you want to gain our trust, give everyone the AOSP build.
Do I want sammy to be community-minded? Absolutely.
Am I going to trust one guy who says he works for our manufacturer? Well, let's get to the root of that. Do I trust the company who created out hardware? Not at all.

Sighcosis said:
Dcows, Phidelt, and of course JT and many of the OPs in the Samsung Fascinate IRC channel would be obvious choices.
Click to expand...
Click to collapse
Yeah I frequent the irc with those guys and we're always willing to help people... I think a lot of people come to forums just to get help and information rather than to develop and theme and stuff like we do. It would probably be more beneficial for Samsungjohn to maybe set up a date on the irc and say like "I will be on from x time to y time" and then people can get on and ask questions and talk about things, and more of the power users who use the irc regularly will get a chance to maybe learn some stuff or help out Samsung.
It would also make it much easier to control, if things get out of hand then the OPs can simply kick or ban the culprits.
Sent from my SCH-I500 using Tapatalk

Here is the Xoom build.prop thanks to thefredelement

Guys,
Have at it ! Here is the Xoom build.prop thanks to thefredelement... Give him a HUGE thanks for sharing this
Just download it; then extract the zip file and there you go!!!
Thanks again thefredelement !!!

Does this mean we will have honeycomb soon or do we still need the drivers from nvidia?

You still need a boot.img. Just so you know people have had access to the xoom for more than a week already and have been working on this.

Thanks, but based on the early indications this fingerprint will actually cause the market to shrink rather than expand. It is interesting to read though as it specifically states nosdcard, and does include the telephony stuff, if nothing else there is potential that once we have a honeycomb port 3G usb modem drivers may become available.

I just posted this so we could take a look at what was in it... it is a good read if nothing else ;-)

thebadfrog said:
You still need a boot.img. Just so you know people have had access to the xoom for more than a week already and have been working on this.
Click to expand...
Click to collapse
I would have thanked you but I've exceeded my max per didn't know there was a maximum. You learn something new everyday.
Anyways, it's also my understanding that to get the boot.img, the Xoom will need to be rooted. Is that correct? So, is that what we should be really looking for? Xoom has been rooted threads?

Look for "Rom based on Honeycomb". And yes it needs root. It will happen people. Posting endless honeycomb threads is not gonna make it any faster.

Ok I'm kind of a noob, please don't slam me 'frog. Since the whole purpose of Android and the whole Open Source thing is to make source available, don't either Motorola, nVidia or Google NEED to release this Honeycomb-Tegra 2 code at some point. I do realize that there may be proprietary pieces but I thought once you used open source code, you were obliged to release your resulting code to the community. Am I missing something here or is all this chatter just an attempt to get it faster?
I hate seeing all of the teaser threads as well, but I also try to keep an open mind and view it more as humorous than obnoxious. I'm sure the real dev's are quite adept at skipping and ignoring the stupid comments by people like me.
I'm just saying ...

thebadfrog said:
Look for "Rom based on Honeycomb". And yes it needs root. It will happen people. Posting endless honeycomb threads is not gonna make it any faster.
Click to expand...
Click to collapse
Lol. I shouldn't have posted the last two sentences. It's not like I was saying that I was being impatient. Just wanted to learn that's all.
I'm assuming we'll see a lot of the bits and pieces of the XOOM system posted in here and just wanted to know what's relevant or not.
Thanks again.

Its all good. I understand people wanna learn.
Yes they have to release anything that is open source but if you use linux you can use the nvidea and ati example. They don't release their proprietary libs for their cards and as a result its quite likely when you upgrade your kernel you break your video drivers. Its not so bad now but a couple years ago I couldnt keep an ati card working.
All the endless threads that are repeats make it nearly impossible for noobs to find good information and it makes it harder for me to link the correct posts for noobs to follow. Everyone was new at one time but you will never learn anything if you keep asking and not looking. This is a developer forum....xda DEVELOPERS.... not a customer service forum. Most devs here go out of their way to answer questions as do a few of us power users. My tirades are not directed at people like the 2 previous posts. Its the ones that dont want help. They want someone to hold there hand and type out each and every command for them and supply them a fix for every problem. And they want it now

sverbanic said:
Ok I'm kind of a noob, please don't slam me 'frog. Since the whole purpose of Android and the whole Open Source thing is to make source available, don't either Motorola, nVidia or Google NEED to release this Honeycomb-Tegra 2 code at some point. I do realize that there may be proprietary pieces but I thought once you used open source code, you were obliged to release your resulting code to the community. Am I missing something here or is all this chatter just an attempt to get it faster?
I hate seeing all of the teaser threads as well, but I also try to keep an open mind and view it more as humorous than obnoxious. I'm sure the real dev's are quite adept at skipping and ignoring the stupid comments by people like me.
I'm just saying ...
Click to expand...
Click to collapse
Typically one week is the lead time afforded the trail blazing device for each generation of Android, and then the plain vanilla source AOSP is posted at source.android.com (read about git first, where the kernel is posted). However none of the proprietary information in specific devices needs to be made available right away.

Will th devs that made the honeynook sdk preview be able to update that if they get a Xoom, amd in turn would that help the g tab devs?

I'm just curious about how much of a problem the fact that the XOOM has a Gig of system ram rather than 512 megs will be. I could see an easy way to protect some exclusivity under the guise of "ensuring compatibility" where one of the first boot steps is to check for enough available ram...

Good thing my Zpad has 1 gig ram then eh

boot img and tegra 2 aosp source here
http://android.modaco.com/content/advent-vega-vega-modaco-com/333138/xoom-rootboot-img/#entry1614605
I think.

Alpha06 said:
boot img and tegra 2 aosp source here
http://android.modaco.com/content/advent-vega-vega-modaco-com/333138/xoom-rootboot-img/#entry1614605
I think.
Click to expand...
Click to collapse
It's a Xoom boot.img, and the (tegra 2) kernel source for honeycomb (2.6.36).

Ok, per Engadget Xoom has been rooted... Next?

Here are the init files as well: http://forum.xda-developers.com/showpost.php?p=11615922&postcount=9
You can get a rooted boot image here: http://www.koushikdutta.com/2011/02/motorola-xoom-rooted.html

Love it when things start moving at nearly the speed of light,... uh oh, getting dizzy... frog, will you hold my hand?

MikeTheSith200 said:
Will th devs that made the honeynook sdk preview be able to update that if they get a Xoom, amd in turn would that help the g tab devs?
Click to expand...
Click to collapse
The Nook is so heavily supported because it's so god damn cheap for a tablet. (it's really an "e-reader")
there was no touch interface released with the version of honeycomb from the preview sdk.
With a real Honeycomb product (and full SDK) full development is possible.
If you wait, They will build it, we will come. =]

Development Coming Soon? (AndroidSpin Posted My Article, Skilled Dev Willing to help)

I've been trying my hardest contacting many people to get development started with this phone. Since not many Experienced Devs would be looking the way of this phone i've been trying to reach out.
I Contacted AndroidSpin as well and they are very well known android news site (which i check everyday) and managed to get an article out about helping with development with our phone (awsome, thanks AndroidSpin!) See the Article Here
Hopefully in the Near future we will have a working recovery and ROMs/Mods/Themes Rolling out. A Very experienced Dev has Contacted me Back Saying he is Willing to Help but nothing is promised as he doesnt have a Sidekick 4G at hand. But he is willing to make a working recovery for us so lets see what happens .
He will Definitely need testers.. i will be one ofcourse hope others are interested in seeing development stir up over here aswell !

nice to hear about.....i have been checked this 4rum everyday to looking for a news but still......hopefully something will come out soon....:x im willing to be the tester for this as well.....

I just want to say thank you to all of you working on this. As a former Hiptop user and open-source enthusiast, I took issue with the closed platform that Danger had installed on it and ended up ditching it. When I heard the new Sidekicks would be running Android I jumped at the chance to have one, only to find out that development was lacking interest due to the stigma of the old Hiptops as phones for teenagers. It's wonderful to see more people getting interested in this and I hope to help as much as I can in the future. Thank everyone again and happy hacking to you all!

willing to help
I'm very interested in getting development going for this phone as well, I don't have the time or the skill set to cook roms myself but I am more than willing to test and give feedback. I know a lot of devs aren't interested since they spent last year with the galaxy s line of phones and there are new dual cores to play with, but I think this phone is really unique and could definitely have a big following because of the fact that it is soo different than the sea of slabs out there. I hope development picks up, there are plenty of custom roms out there already built for the galaxy s line that would only need to be tweaked to work with this device so hopefully that picks up soon.

I'm very interested in helping with development, came from the G1 and had fun with that. I was trying to figure out how to compile ClockworkMod but because Samsung uses initRamFS rather than a regular makefile, I was unable to figure it out. I'm very open to testing and trying to help as best I can with developing on this phone, feel free to e-mail me if anyone has any need to test anything, I'm always checking my e-mail. sduvick AT gmail.com. For those who understand the compiling of clockworkmod, I would suggest working from the Vibrant version, as the buttons are all mapped right, we just need to add the storage driver so that the sdcard can be mounted.

I would love to be a tester please keep me posted.
Sent from my SGH-T839 using XDA Premium App

+Thanks.
I'm still stock and would be willing to help some dev's

Devs: A Bounty has Begun on the Cyanogen LG G2X Bluetooth Issue

Cross-posting this from the LG G2X Cyanogen forums.
In case you missed it there is now a bounty on issue 4105 aka "no bluetooth stereo". As of this writing it's over $100 and though that probably won't cover the hours it takes to track down the Bluetooth driver and port it, it will buy a few cases of beer to celebrate.
I'd post a link, but I can't yet because I'm a newb - so you'll have to trust me.

Is this even possible??? Would they have to make a driver from scratch??? If it is possible and legit im down for adding to the pot.

It was my understanding that nVidia needed to release the source code for their drivers to get this to happen? I'm not holding my breath on that happening. I would really like to see the Bluetooth issues worked out though.

DECIM8 said:
It was my understanding that nVidia needed to release the source code for their drivers to get this to happen? I'm not holding my breath on that happening. I would really like to see the Bluetooth issues worked out though.
Click to expand...
Click to collapse
..maybe NVidia wants the $100

Anything is possible. It's not easy, and very Time consuming, to reverse engineer drivers.
Sent from my LG-P999

dreggs said:
..maybe NVidia wants the $100
Click to expand...
Click to collapse
Lol that's awesome

That is the pretty ****ty thing about NVidia. If they are going to keep their doors closed then at least provide updated drivers frequently.
Maybe when Tegra 3 comes out they'll release Tegra 2.
I've seen so many devs so so many near impossible things here are XDA that I know someone will crack it. I think they are just being lazy now (which is smart) because why waste time and energy if NVidia will release it shortly? But now that we're finding out that it probably won't happen that hopefully they'll start crackin' on it.

I would add to the pot if someone can provide a link
Sent from my LG-P999 using Tapatalk

player911 said:
That is the pretty ****ty thing about NVidia. If they are going to keep their doors closed then at least provide updated drivers frequently.
Maybe when Tegra 3 comes out they'll release Tegra 2.
I've seen so many devs so so many near impossible things here are XDA that I know someone will crack it. I think they are just being lazy now (which is smart) because why waste time and energy if NVidia will release it shortly? But now that we're finding out that it probably won't happen that hopefully they'll start crackin' on it.
Click to expand...
Click to collapse
That will be next to impossible. Nvidia is not open source friendy.
I think this will work. If many are doubting, better check out hd2 android...
Sent from my Calculator with Android.

To write a driver, you need a register set. Apparently that is part of the IP NVidia isn't up-ing, at least not without an NDA. Without a register set, have fun...
So if you signed the NDA, get the register set description (which may come with sample code), wrote a lib, and posted the lib (but not the source code) here, would that violate the NDA?

I would add to the pot as well. I would LOVE to see this happen.

namklak said:
To write a driver, you need a register set. Apparently that is part of the IP NVidia isn't up-ing, at least not without an NDA. Without a register set, have fun...
So if you signed the NDA, get the register set description (which may come with sample code), wrote a lib, and posted the lib (but not the source code) here, would that violate the NDA?
Click to expand...
Click to collapse
No, that should not violate the NDA. The NDA covers the source code they provide to you to develop your products. The work product is okay to distribute as long as you don't disclose the source code.

I will donate of we find somone that is capable. Maybe we can drag another dev into a g2x as a result as well. Love this phone. Hopefully more will realize its superior smoothness to the crapsation.
Sent from my LG-P999 using XDA App

Ill trow down $30 on the pot.

I would definitely chip in for the bounty as well if someone could get a2dp/bluetooth to work. I've been pretty disappointed with my g2x and it's because of this.

CM_arcee tweeted it is working on 2x, i think we have a2dp thanks to the fine devs here!
http://tinyurl.com/66zc8un

fcisco13 said:
CM_arcee tweeted it is working on 2x, i think we have a2dp thanks to the fine devs here!
http://tinyurl.com/66zc8un
Click to expand...
Click to collapse
Ummmmmm...... wow.
If this is coming out in a CM7 rom soon then where do I sign up to donate!!!!

maciek82 said:
Ummmmmm...... wow.
If this is coming out in a CM7 rom soon then where do I sign up to donate!!!!
Click to expand...
Click to collapse
It will soon be in cm7! CM_arcee is the man to thank/donate.
This will make cm7 complete and my g2x perfect.

fcisco13 said:
It will soon be in cm7! CM_arcee is the man to thank/donate.
This will make cm7 complete and my g2x perfect.
Click to expand...
Click to collapse
In the next release list, a2dp workaround is aready there. Probably come out within the week, maybe tomorrow. Check out the CM7 changelog page of g2x p999.
Sent from my Calculator with Android.

jose makalolot said:
In the next release list, a2dp workaround is aready there. Probably come out within the week, maybe tomorrow. Check out the CM7 changelog page of g2x p999.
Sent from my Calculator with Android.
Click to expand...
Click to collapse
Already used it at work, thanks fits!

KERNEL source released

So exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
EDIT: http://dl4.htc.com/RomCode/Source_and_Binaries/doubleshot-gb-crc-2.6.35-f3a1982.tar.gz
Sent from my DoubleShot Lite using Tapatalk 2

ac3theone said:
so exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
sent from my doubleshot lite using tapatalk 2
Click to expand...
Click to collapse
yyyyyyyyyyeeeeeeeeeeeeeeeeeeeeeessssssssssssssssssssssssss
Soo.... Does anyone think we could see some pure AOSP action now? Or someone could update the kernel for CM7? As you will see in general someone -whom I suspect is not alone - would love an AOSP ROM on our HTC Doubleshot.

Maybe this kernel isn't that good as we suppose...

Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Well.... What did u expect? we don't have an ICS ROM in our future that we have been made aware of, and it is truly great news as this is something that has made many a dev stray away from this device - now we might be able to get CM7 stable - and others to work off of CM7 such as blahblah

Good news nevertheless
We need to get CM7 STABLE ASAP
We may be late in the running, but that doesn't mean we still can't get merged into the main tree

Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/

michaelmab88 said:
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
Click to expand...
Click to collapse
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.

Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha.......nope I fudged something in my toolchain It's broke....again.....LOL
Sent from my myTouch_4G_Slide using Tapatalk 2

strapped365 said:
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.

Blue6IX said:
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Click to expand...
Click to collapse
I might have my little one on Saturday night so that maybe a no go for then, the tool chain I currently have is 4.4.1, because anything newer for the speedy breaks a ton during the compile.....I changed some commands around for ****s and giggles and got a zimage in arch/arm/boot so I split it with the ota ramdisk and I'm just gonna try....if that goes south I'll setup your tool chain....thanks blue your like the DoubleShot dictionary....
Also I'm gonna grab one of your kernel zips for test flashes if that's ok
Sent from my myTouch_4G_Slide using Tapatalk 2

Blue6IX said:
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Click to expand...
Click to collapse
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer

michaelmab88 said:
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
Click to expand...
Click to collapse
Lol no worries my friend, was a general comment and not aimed at you in particular, just a perspective I wanted to put out there and you were the first opportunity to do so.
I still haven't found the time to get git set up and learn how to use it - that whole life getting in the way of living thing. Given you have git going that makes you a more responsible dev then I in my book -
@ strapped: all my work available is a contribution to the open source community at large, and the members of XDA in particular. If any of it can be useful, especially as a teaching tool, I wholeheartedly encourage it!
Sent from a digital distance.

Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...

gtmaster303 said:
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
Click to expand...
Click to collapse
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!

How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.

Kanerix said:
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Click to expand...
Click to collapse
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.

michaelmab88 said:
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
Click to expand...
Click to collapse
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking

Blue6IX said:
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
Click to expand...
Click to collapse
I've been trying to go through the dev reference that you posted and track down as much scattered information as I can, but I'm still not quite sure what I'm doing. Alas.
Regarding bluetooth: would the gingerbread stack be compatible with ICS?

gtmaster303 said:
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Click to expand...
Click to collapse
Well what I'm currently up to is making a stable version of cm7 for the doubleshot. I have made lots of progress as far as learning all the tools necessary to compile android from source, which is a relatively simple task. The not so simple part is trying to put together like a puzzle, the source code from other devices. I've hit some roadblocks and I'm currently asking some devs for help, but while I'm at it I guess I can ask for help here on xda.

michaelmab88 said:
Well what I'm currently up to is making a stable version of cm7 for the doubleshot.
Click to expand...
Click to collapse
Yeehaaa!