Database Info

[Q] Honeycomb for nook color, why not for us?

Why are we not getting honeycomb to play with?

You really need to read some threads before posting a question that has already been answered many times.
Sent from my Viewsonic G Tablet running TnT Lite 4.2.2 w/ Pershoot's Kernel using Tapatalk Pro

And the honeycomb you are referencing has no practical use in the real world. Its a hacked together UI that does nothing but run the preview sdk

if it was worth it we would have it. our devs kick ass

Moved to general

I hate to sound like a jerk but what is it with all the people whining about honeycomb. The only version out so far is a hacked version built off the prelim sdk and in no way will work for the g tablet. Anyone who has been Modding for anytime knows the cardinal rule for android...
DON'T ASK FOR ETA'S.
When honeycomb is officially released by Google I'm sure it'll be like every other release and in a short time we'll have our own version. Until then have some patience please and do some research.

or if you want honeycomb straight away then get a xoom and pay the big bucks

What i dont get is why do people ask and ask...........
Doesnt your gtab do everything you need It to?
honeycomb... Hero cookie....danish....pop tart...soda cracker........flap jack or royal with cheese
Just names I dont see anything i cant wait for.
Now when they say the next android version will give my gtab the ability for it to make me samwiches and give me oral pleasure on demand that is when i will be all over the devs to build that $hit....

Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!

Really?
BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
Let me get this straight. You post in the wrong section, you ask for an ETA, and you obviously did not search, which also means you did not read any of the forum rules or stickies. Yet, somehow we are all assholes. You know if you just follow a few simple rules your experience with XDA will be much better. The rules here are no different than any other forum. I am going to assume you are new to this, so I will help you a bit. Search for what an SDK port is and you will quickly realize why you do not want this.

BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
I think you should flash the Nook Color ROM BilliamB, you obviously know what you're doing, I'm sure you can get it to work. I mean come on, the G Tablet has a Tegra 2 processor, it should totally work right? Although you may want to read a few threads.... oh wait, you obviously don't do that. Come on dude, the only one here being an AH (as you put it) is you.
Sent from my Viewsonic G Tablet running TnT Lite 4.2.2 w/ Pershoot's Kernel using Tapatalk Pro

Seriously.... You will not see Honeycomb on the G Tablet until another unit is released with Honeycomb and has the Tegra 2 chip. The issue is the instruction sets are different enough that its not a one for one port. The Nook, Dell Streak 5, Tegra 2, etc. are all based on the ARMv7 instruction set but there are difference in their implementation enough that make them incompatible. In addition the biggest differences lay in the I/O subsystem which makes these platforms completely different. With these major differences it makes porting from the emulator (which is how they are getting Honeycomb to work) a daunting tasking and nearly impossible on a Tegra 2 based device.
I am very confident after the first Honeycomb system image is posted it will be running on our tablets... It will be a race as to who gets props on Engadget for being the first to port to the G Tablet..
You would get less hostility if you read, learned and asked accordingly. Its a give and take community. Unfortunately the way you asked makes it seem your less inclined to contribute and just take...
BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse

Honeycomb is coming to the g-tablet in March, till then.
RERRRAAXXXX

BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
Seriously dude....This is about the 10th thread with this same topic started since the nook got the honeycomb sdk running. You ask questions without searching and then cause you dont get the answer you want you call us names. Don't worry, most of us won't answer your questions anymore.....ever.

BilliamB said:
Instead of anwers that are coherent and useful we get alot of mouthy folks that serve no purpose. What a bunch of AH's!
Click to expand...
Click to collapse
Whoa!!! Bad move man, bad move. You need realize that you can't call people who are willing to spend rediculous amounts of thier personal time to provide the community with amazing firmware AH's! Quite the contrary - They are saints (and, actually, you serve no purpose).
Swyped from my VEGAn-TAB-v1.0.0B5.1

deep_powder2012 said:
Whoa!!! Bad move man, bad move. You need realize that you can't call people who are willing to spend rediculous amounts of thier personal time to provide the community with amazing firmware AH's! Quite the contrary - They are saints (and, actually, you serve no purpose).
Swyped from my VEGAn-TAB-v1.0.0B5.1
Click to expand...
Click to collapse
Totally agreed. XD.

Hey Alpha06...
I'm just curious if that is a confirmed news or word of mouth that the G-tablet would have Honeycomb around the March?

I wouldn't guarantee that Honeycomb for the G-tab would be available for sure in March, however I wouldn't be surprised to see Alpha-versions of Honeycomb ROMs shortly after the first Tegra2 devices are released and rooted. Like everyone has been saying around here, don't ask for an ETA, because the people around here that do develop do it on their personal time. They have lives, work, and possibly kids, wives, or whatever that also wants their time as well.
Remember, porting a ROM is a lot easier if there is solid reference material to build from. As you may notice, TNT-Lite comes from his building on and improving the existing TNT version of Android that came with the G-Tablet. Vegan is a modification and improvement of the Vega OS. I don't believe that the developers of either package (and correct me if I am wrong) went to Google's GIT repository for Android and compiled their own versions of the OS specifically for the device - along with writing their own custom device drivers for all of the internal hardware. They built off of, and improved what was available.
IIRC, the Nook port of Honeycomb is only partially functional. The just released port for the Dell Streak (http://www.mytabletlife.com/2011/02/08/dell-streak-honeycomb-port/) is as well. Why, because they are essentially starting from scratch.
Which brings everything back to my original point. As soon as reference devices are out in the wild, I'm sure that will be the point where we will see Honeycomb ports start to pop up here as well.
BigJohn

march can not get here soon enough... heh.

[Q] Porting the Honeycomb sdk - am i on the right track?

I understand that the sdk is nowhere near full featured, but now there are system dumps of the xoom, maybe helpful, right?
Well, i have never ported nor built a ROM before (done some theming and have no problem learning code). I came across these 2 port how-tos:
http://forum.xda-developers.com/showpost.php?p=11546129&postcount=76
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Is that all i really need to get HC to boot? The instructions seem extensive but not impossible or difficult.
Has anyone attempted this or gotten HC to boot on the g-tablet? I'm willing to take a crack at it if a dev could tell me whether i'm on the right track with the tutorials or do i need more knowledge.
When it comes to ROM building/porting, i gotta start somewhere. I've been around these forums for years and its about time I attempt to return the favor (hopefully without bricking my device lol)
Thanks in advance.
If this post needs to be moved, i'm sorry mods, but i figured this is strictly a development question.

Feel free to attempt it. There are people working on it and have come to the conclusion that source is needed plus a couple files from nvidia.
IMO porting the sdk is a complete waste of time tho. You would be much better starting off with a rom that will compile like froyo rather than starting with something that doesnt work yet

thebadfrog said:
Feel free to attempt it. There are people working on it and have come to the conclusion that source is needed plus a couple files from nvidia.
IMO porting the sdk is a complete waste of time tho. You would be much better starting off with a rom that will compile like froyo rather than starting with something that doesnt work yet
Click to expand...
Click to collapse
thanks for the insight. You're right, maybe froyo would be a good place to start so i could get used to the process on something that will compile. I'll probably give it shot in the next couple of days.

jump on the irc channel. freenode channel #tegratab. Lots of help and a willingness to help those that want to learn. I've compiled cm7 several times myself. Not my cup of tea but it was interesting.

[Rom] Ics Nexus / Sdk Port [Alpha2]

Moved Here
Also a notice to the Admins, Mods, and various users at this site:
My personal email address is not to be used to mock, insult, or otherwise argue points made on this forum. The comments made here, despite how offensive they may be interpreted, do not hold a serious tone. If you feel it necessary to send things to my personal address, please have spine to use your own return address. Please respect the fact that I do not invade your personal life by keeping my comments restricted to this site, and I only request I am granted the same common decency.​

Wow, haven't seen you in a long time. Thank you for giving this a shot! : )

RjsShadows said:
Wow, haven't seen you in a long time. Thank you for giving this a shot! : )
Click to expand...
Click to collapse
It seems that in some alternate reality it is acceptable to assume that "in your spare time" means cancel all of your plans and get used to fluorescent lighting because daylight is just the glare on your computer screen. Either way, I am downloading some 2 gigs of random ICS stuff and finally received my replacement Macbook, so between projects I will try to get something moving on this.

You rock! Subscribing.

Right now all I have is the sdk version from RootzWiki, which appears was a post of just the modified boot. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk

twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Sick, i'm really looking forward to this. Don't overwork yourself though

twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
i am guessing these first ports will be very alpha due to no real software from google to work with?

Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...

the_scotsman said:
Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...
Click to expand...
Click to collapse
What did I miss? Did the angry beavers try to build another dam? I fell asleep waiting for the new mac to migrate from the old one. Now that everything is moved over I can actually load up what I have and at least move a little closer to posting actual files to play with.
Sent from my ADR6400L using Tapatalk

Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.

doug piston said:
Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.
Click to expand...
Click to collapse
I guess if you didn't see the previous thread, which was more or less a rick-roll youtube video that said it isn't possible to get anything running, then an understandable first reaction is to make rude comments...
But if you read the thread you are responding to, you would have seen that on the Nexus it is a working build, capable of being used as more than just a proof-of-concept. Then again, I don't expect people to read these days because they are too busy writing...
http://forum.xda-developers.com/showthread.php?t=1313337
http://forums.androidcentral.com/sprint-nexus-s-4g-rooting-roms-hacks/127806-rom-ics-sdk-port-wip.html
Best leave the developing to the developers and stop back when there is something to load up and complain about

So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".

doug piston said:
So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".
Click to expand...
Click to collapse
This is real ICS development, and not a prank so it is as the title says "ICS Development (Real Deal)"
And no, getting a port working on the Nexus S is not the same as getting it to work on the Thunderbolt, which is why there isn't a file in that first post yet. I think you are assuming that the only thing available is the SDK image, though, when the full system dump is out there also.
My previous statement still stands.. Why don't you go shake down some kids for their script source, and come back when there is something here to test.

thatdudebutch said:
Posting threads with no content seems ridiculous. Why not work on the port rather than type sentence after sentence of nonsense in here. Just saying.
Click to expand...
Click to collapse
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
I can just toss up every little edit I test and brick phones all day long, or I can document the process and release when it hits milestones. That way I can catch input along the way and prevent a lot of wasted time.
Just swapped the boot on the posted Nexus build, changed over all the apn info, and added in all the keylayout and hardware files. Going through and finding everything that needs to be swapped for a straight port, then if it runs I will post up the progress.
Sent from my ADR6400L using Tapatalk

twistedumbrella said:
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
Click to expand...
Click to collapse
Whether you get anywhere or not, good luck
Nothing wrong with doing something just for the challenge of having said you did it and the experience.

I am glad to see someone putting some real effort into getting an ICS port going. And appreciate you posting your progress here along the way. I'm interested in seeing how you get where you get.
Good Luck

As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probable lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warnings​If this goes off topic again then there will be repercussions​.

conantroutman said:
As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probably lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warnings​If this goes off topic again then there will be repercussions​.
Click to expand...
Click to collapse
Thanks. The good news is that I have a shopping list of what has been changed to go from sdk to working port. The bad news is that I also have a project due Thursday that I need to actually spend some time with.
For anyone with the sdk build, make sure before even trying to run it that you replace all the /system/bin files that just say toolbox with real files or set up symlinks for them. Busybox also needs to be added/replaced in /system/xbin
This will get that version to where you can run logcat and see the EGL errors, but it will also be in a condition to start tweaking files to get the touchscreen running.
Sent from my ADR6400L using Tapatalk

I can't waaaaiiiitttt!!
Take as much time as you need! Your life is more important than this.

I am uploading what I have, but not because it is a huge step forward. I fixed all the commands and added the files that should fix the touchscreen, but didn't on this device.
This is still a step forward from the base build we currently have. At least typing a command no longer results in "toolbox" being displayed instead of results. I reverted everything I tested to make sure the only test changes were absolutely necessary to provide a solid base. I will post a link as soon as it is up.
Sent from my ADR6400L using Tapatalk

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!

[Q] Tegra Zone Shield APK? The app that launches with the shield button.

Anyone got a copy of that? With a shield the app that launches when you hit the shield button I need that exact app.
Looking to try spoofing tegra in my nexus 4 to try streaming with a normal controller
Thanks!

I hope someone makes this happen, due to it streaming I can't see hardware being a limitation.

It could be like the Ouya framework though... Dependent on the actual device.
Sent from my TouchPad using xda app-developers app

I sure hope someone will be able to release the APK. I would be interested in using it on my Galaxy S3.

It's not the same as the TegraZone already on the Play store?

Furyus said:
It's not the same as the TegraZone already on the Play store?
Click to expand...
Click to collapse
No, it is not. And while I can't speak too much about it, it's not just a side-load onto any device. So don't be holding your breath about someone uploading the APK and getting all the features running this week.

right....because it sooo hard to make rudimentary changes to a launcher.

The APK is called Dashboard.apk. It resides in /system/app and can be launched as a normal app.

?? Then why did you say the opposite not 2 posts ago?

LegionTHEFecalExcretion said:
right....because it sooo hard to make rudimentary changes to a launcher.
Click to expand...
Click to collapse
Let me know when you get this working, since you love trolling. One of us has been helping everyone to the largest extent they can. The other is just demanding a bunch of stuff since he doesn't want to buy one himself.
I will personally post the full system image tonight if it isn't already uploaded by then. And you can go to town, I'm seriously curious about how much you can get working this week, since its obviously so easy.

LegionTHEFecalExcretion said:
?? Then why did you say the opposite not 2 posts ago?
Click to expand...
Click to collapse
It won't do anything. It will crash on another device.
Sent from my HTC One using XDA Premium HD app

You're the one going around posting false information. And asking for a system dump is not "demanding a bunch of stuff".
If you want to get into a pissing match about who's done more to help the XDA community, you're gonna lose. I've done alot more than post some roms for the EVO 3D. If anyone's a troll here its you.

And 20x more people have found my comments helpful. So you're still trolling. What false info have I given?

Unlike you i'm not a thanks whore, and the thanks meter wasn't even implemented when I started posting on XDA. I have released numerous firmware images and sbf files that would otherwise have not been obtainable, saving countless devices in the process(See the technician only Xoom recovery file that was the only way to restore a bricked Xoom for months after release). That's a little more important to me than some likes.
Oh and False info? You just said not a few moments ago it runs like a normal app.

Now now boys, calm down.
I must admit I am on legions side on most of his points so far. This is a community forum for the general public and what we do here is Share and Mod. I do believe "agrabren" that as you are part of the Nvidia team you don't want to see parts of your product ported and such, but the product is now in the hands of the user and so now it is up to us what we do with our purchases.
Sent from my C6603 using Tapatalk 2

LegionTHEFecalExcretion said:
Oh and False info? You just said not a few moments ago it runs like a normal app.
Click to expand...
Click to collapse
It didn't occur to me that I might need to explain that in more detail, but in hind-sight, it does need clarification. What I mean, and meant from the beginning, is that the framework doesn't issue any "magic" to launch that app. There's no special "back-door" entry into that APK which makes it work on the device, nor is the Intent anyway modified. My natural instinct is to distrust every aspect of a system app that doesn't sideload correctly. In this case, I gave extra insight into areas of attack on getting the APK to load on other devices by eliminating one method a company could use for an app that has a special method of launch (the center button on the device).
So my statement, properly clarified, is that the APK itself has nothing special about it in regards to Intent launching or its AndroidManifest.xml, but that without some efforts with other components, will not run directly on another device, especially one based on a non-Tegra device.

poo-tang said:
Now now boys, calm down.
I must admit I am on legions side on most of his points so far. This is a community forum for the general public and what we do here is Share and Mod. I do believe "agrabren" that as you are part of the Nvidia team you don't want to see parts of your product ported and such, but the product is now in the hands of the user and so now it is up to us what we do with our purchases.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Great, except I've actually been trying to help most people with most parts of ROM sharing and modding. I've already said that I'm going to post the OTA1 system and boot images, in their official entirety, as well as I'll probably post a rooted version as well. I've been helping people prevent bricking their devices.
If you'd rather I just go away, I'm happy to. But I wouldn't expect anyone else from NVIDIA to be reaching out to get CM10.2 up and running on this device, or to get a custom recovery up and running quickly. I've never objected to him getting the system image, I'm all for it being uploaded and even promised to do so. I'm trying to help clarify what will work easily and what won't. I even answered the question that nobody else had, the APK he's asking for (because he didn't know the name of it) is Dashboard.apk, and it resides in /system/app. His contributions right now to the SHIELD forums on XDA are: Give me the system image, give me some APKs that may be on the device! That rubs me the wrong way as a person who has spent plenty of time developing ROMs for different phones, helping fix kernels for multiple CM-supported devices, and who has *always* fought for companies to give to the community. Unlockable bootloader? Yeah, I was part of that push. I'm trying my best to get as much source as possible made public.
Maybe I came off poorly in this thread (because this was after the thread asking for an apk that has only been demoed at tradeshows and special press meetings). So I'm sorry if I came off wrong, but while everyone else is helping each other out, he's just demanding stuff.

I what world do you live in that posting a thread asking for a system image and a possibly pre-loaded app qualifies as "demanding stuff"? Why should I have to have done anything to be worthy of your approval to post such a thread?
There is a huge conflict of interest with you both working for Nvidia and unofficially releasing official firmware and hacks, so frankly no, I don't trust you being involved in this devices xda development.

LegionTHEFecalExcretion said:
I what world do you live in that posting a thread asking for a system image and a possibly pre-loaded app qualifies as "demanding stuff"? Why should I have to have done anything to be worthy of your approval to post such a thread?
There is a huge conflict of interest with you both working for Nvidia and unofficially releasing official firmware and hacks, so frankly no, I don't trust you being involved in this devices xda development.
Click to expand...
Click to collapse
So a guy who doesn't own the device is not going to trust ROMs I make for a device he doesn't own. Oops, no loss to me. You can go back to trolling, I'm done with your thread. You have your system image and boot image in either manner you want it.

Oops, my bad. It wasn't your thread, you just came into this thread to troll me. My mistake.
Raptor, if you check in the Android Development section, you'll find the system images. I'd suggest the ZIP version, because it's both smaller and already extracted. The system.img is an uncompress image to be flashed via fastboot in case someone messes up their system or boot partitions.